Database Users

Samsung Galaxy A8 (A-800I) Stuck on Logo Screen with red Custom Binary blocked by FRP

Hello all!
First of all i want to thank this site (and the people behind it) that makes everything android possible.
I feel privileged to be a member of this forum specially on rough times like what i am facing right now.
I rooted my Galaxy A8-A800i the other day and everything went great. I followed the instructions that i found here. Unfortunately, yesterday i turned off the OEM Unlock on my phone. Now, as the thread title says it. it is stuck on the Logo Screen with the annoying " Custom Binary blocked by FRP Lock ". i read a guide that ashyx made and i felt stupid. I didn't know that turning the OEM Unlock will do that to my Phone.
Right now, I am digging deep on this forums to try and revive my phone that is currently in Brick state.
i am downloading a firmware from sammobile for my phone, the problem i have is... i don't know how to use it. I don't know much about my phone but I do want to learn a lot and i know that this is the right place. I would like to ask assistance on how to use the firmware that I am downloading right now, and also, can i make the Knox Counter go "0" again?
Thanks for everything guys. I highly appreciate everything i've learned here so far.
EDIT: Sorry this post wasn't supposed to be here. Please delete it. i moved it to Troubleshooting.

i hade same issue which a800iz , download rom for your phone , and flash boot and recovery , it must working

Sorry for the late reply. Yes, my phone is working now. I installed the official stock firmware to correct the problem.

amm sir good day i have a SM-A800iz i been try to odin to install stock rom but did't work theirs another way to recover my phone? thank you...

[Hardbrick] Oneplus 2 Only fastboot, OEM and device locked.

So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
Nevertheless, i will state my problem here:
Right now, my phone and my limited knowledge about it have come to an dead end. with the help of online tutorials and so on, (I have downloaded almost 40 gigabytes worth of space to do stuff to my phone), i was able to only get the fastboot mode to work again.
It started with me uninstalling a system app from google (I don't know which one exactly, but i had the resurrection remix 5.69 or something like it, and in that ones system app remover it was one of the lowest google apps). I don't know if this is important, but at the time i did that i was in plane mode.
After some time i ran into some loading issues with games and restarted my phone. the first time i got in, i booted up normally and could do my pattern normally, but then there was only a black screen and i could pull that info bar thing down. as soon as i wanted to open the settings, everything froze and i decided to restart the phone. Once it was shut down i then got greeted by a bootloop which i aborted by shutting down after about 3 minutes. then nothing was working anymore, so i wanted to see if the fastboot mode was still available. it was, but after shutting down from that and trying again ( just to be sure) even that was gone.
so i went online and downloaded basically everything you can find online to recover a harbricked op2.
turns out, after i got my fastboot working again, the OEM and the device were locked (still not sure if those are different things or the same) and because i couldnt get in the android system, i could not enable it.
the ADB commands do not work at all because there is no device detected for it, though it is detected for fastboot. the command fastboot OEM unlock does not work because OEM unlocking is disabled...
so far i have been able to connect my phone in 3 modes and names for those, them being:
Android Bootloader interface (Fastboot)
Qualcomm HS-USB Diagnostics 900E (Connected while holding VolUp)
RELINK HS-USB QDLoader 9008 (Connected while holding VolUp + VolDown)
I am also unable to flash anything on the phone because the OEM is locked
I will not be able to answer for some time (probably 2-3 weeks) but i wanted to start this thread so I could already have an answer when i come back home again (traveling with fam, and its somewhat hard to take a PC tower with you on trips)
Thanks for helping me! :fingers-crossed:

I'm having the exact same issue as OP.
I'm not sure exactly what I did, but I can only boot to fastboot. Typing fastboot continue does not work, I can't flash ANYTHING or use any of the recovery tools, because my device is locked, and there's no system to boot to so I can run fastboot oem unlock (have to turn on debugging, which I can't do). I have read just about every guide there is, and also downloaded a boatload of purported "fix" tools/drivers/packages. My phone remains able to boot only into fastboot, and I can't get anything working.
Installing the device drivers did work for me, so I'm about half a step ahead of some other people with this issue, but none of the tools or scripts I've found, or manual methods, have brought my OP2 back to life.
I'm really, really hoping someone here is able to help with this.

Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk

Coolmfarshard said:
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.

http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449

Lonemaster said:
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
Click to expand...
Click to collapse
Its working bro tried several phones with this tool
You cant know its working or not without trying

Coolmfarshard said:
Its working bro tried several phones with this tool
You cant know its working or not without trying
Click to expand...
Click to collapse
Ok, Thanks. Don't know what i was thinking back then.
I will reply again when i am Home and tried it. (Currently i am just using Internet cafes.)

MickyFoley said:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
Oh, it is that one. I had already tried this one, in all listed modes posted above. The problem with that one is that everytime I hit the start button, the green progress bar does not show up and it does not a single thing... because I am staying at a place with a internet café for 3 days, I can download some stuff and try it again.
EDIT: I don't know if that was the reason It didn't work, but I may or may not have forgotten to install the driver because it was deleted off the onedrive page and I just forgot about it afterwards. if I can find a replacement for it, I will ink it here for future users with the same problem. otherwise, I would be GLaD if someone would do that for me...

Have you tried flashing a stock ROM with the qcom download tool

abdur10567 said:
Have you tried flashing a stock ROM with the qcom download tool
Click to expand...
Click to collapse
I am not sure if it is that one (it gets pretty messy wehen you have downloaded 50 gigs), but i think it wouldn't let Me because of the locked OEM.

Lonemaster said:
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
etc. etc.
Thanks for helping me! :fingers-crossed:
Click to expand...
Click to collapse
For some reason, after doing it for the what felt like the billionth time whith the restore tool it finally worked (I have NO ****ING IDEA why tho.)
Thanks for everybody who helped me.

How to unlock the bootloader of the SM-N910F (Samsung Galaxy Note 4)?

Hey guys!
At first, this is my first post here so please be lenient if I posted this in the wrong section or whatever. I still need to get used to this forum.
Second, English is not my native language so it could become some gibberish from time to time. I also have to mention that my Android skills are somewhere between newbie and advanced, so please keep that in mind.
But let's get ahead to my problem:
Some days ago, I decided to install Linage OS 14 on my SM-N910F because I don't like the Stock Android 6.0.1 of it.
As you know, a custom ROM requires an unlocked bootloader an that's where my struggle starts.
I simply can't find any tutorial or similar for my phone. The only one I found didn't work (It was with adb fastboot, the process got stuck at "<wating for device>" after the command "fastboot unlock oem" which was described in the tutorial).
I retried it about three or four times before I gave up. It feels like I searched the entire internet, including this forum, but I couldn't find anything useful.
Maybe it's my fault because I didn't look properly, but yeah, know I'm here to ask directly:
Do you guys have any tricks, tipps, ideas or tutorials for me to try?
If it helps you, my phone is already rooted. (chainfire's CF Autoroot)
It'd make me really, really happy and already thank you for your (hopefully) incoming answers.

Vygravlil said:
Hey guys!
At first, this is my first post here so please be lenient if I posted this in the wrong section or whatever. I still need to get used to this forum.
Second, English is not my native language so it could become some gibberish from time to time. I also have to mention that my Android skills are somewhere between newbie and advanced, so please keep that in mind.
But let's get ahead to my problem:
Some days ago, I decided to install Linage OS 14 on my SM-N910F because I don't like the Stock Android 6.0.1 of it.
As you know, a custom ROM requires an unlocked bootloader an that's where my struggle starts.
I simply can't find any tutorial or similar for my phone. The only one I found didn't work (It was with adb fastboot, the process got stuck at "<wating for device>" after the command "fastboot unlock oem" which was described in the tutorial).
I retried it about three or four times before I gave up. It feels like I searched the entire internet, including this forum, but I couldn't find anything useful.
Maybe it's my fault because I didn't look properly, but yeah, know I'm here to ask directly:
Do you guys have any tricks, tipps, ideas or tutorials for me to try?
If it helps you, my phone is already rooted. (chainfire's CF Autoroot)
It'd make me really, really happy and already thank you for your (hopefully) incoming answers.
Click to expand...
Click to collapse
Pretty certain your bootloader isn't locked, you just need to install twrp with odin and then you are good to flash lineage

sawdoctor said:
Pretty certain your bootloader isn't locked, you just need to install twrp with odin and then you are good to flash lineage
Click to expand...
Click to collapse
Thank you for your fast reply. I'll try it once again, moreover I'll let you know if it worked.

It's me again. Flashing the ROM worked, my phone now runs under Linage OS 14.1. But now I've got another problem: Gapps. Somehow I can't flash the Gapps package, TWRP always tells me that the file is corrupted. I downloaded both the Pico and the Nano package for ARM Android 7.1* devices. Both don't work. I also tried the Android 7.0.* version, but that didn't work ofcourse. (Error 20: Wrong Android version installed on the device.) Is it my fault because I downloaded the wrong packages or what's the issue?
It'd be awesome if you could help me again.
Vygravlil
EDIT:
Okay, now it works. TWRP was right, the file was corrupted. I figured out that my PC kinda messed up the download of the package. I downloaded it with another computer and now everything works fine.

Asus Zenpad 10 (Z300M) Boot Loop after update

Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you

Same problem. When WiFi is ON.
When I put WiFi OFF - the tablet works fine.
Last firmware doesn't help, reset too. I think there is no solution at this moment, except maybe to flash an old firmware with Android 6.
I'll replace it in store. No idea about Asus control quality of their firmware... but this problem is pretty common.

???
Belnadifia said:
Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you
Click to expand...
Click to collapse
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach

coolbeans2016 said:
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach
Click to expand...
Click to collapse
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.

I'll give you that
diplomatic said:
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.
Click to expand...
Click to collapse
The link on the Z380M is what threw a flag for me because that Asus tab isnt rootable. If this is some combo of slipups between tools & devices that lines up just right to get TWRP on its not described very well in the OP. Using the 5.132 (?) you can not readback with that option.ini file.... so what am I missing? The bootloader unlock app isn't written for this tablet is it? written for the zenphone 2 (3)?

Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.

Just want to mention for anyone else struggling with this issue, what fixed it for me:
I found the reboot would only happen when wifi was turned on, and even more weird, it would only happen when connected to specific wifi networks. After doing a factory reset I was able to set it up again by tethering to the wifi on my phone. I then found that I actually was able to connect to the problematic wifi network but only by setting a static IP! This has completely resolved the issue for me.

Thaniks
diplomatic said:
Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.
Click to expand...
Click to collapse
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls

coolbeans2016 said:
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls
Click to expand...
Click to collapse
Ohhh... ok. No problem man. Just please get your facts straight before posting next time. Good luck. BTW, I'm not sure if you saw this post on the TWRP thread from 2 weeks ago. You didn't reply.
diplomatic said:
What is the error that you got when trying to flash it? Can you post a screenshot of the Download tab along with the Help/About dialog box?
Click to expand...
Click to collapse

How I rooted my P8Lite 2017

I have rooted countless phones accross all different manufacturers but never found one as stupid to root as this phone!
There isn't an up to date thread about rooting the phone so I thought I'd share how I did it and got through various things that were not supposed to happen but did!
Firstly, unlocking the Bootloader - as Huwai don't provide a code anymore, I went down the https://www.dc-unlocker.com/ route. It is cheap at £4 and they take PayPal. The unlock code video is out of date which didn't help and I presse3d the wrong button first and got a unlock network code by mistake, so had to pay another £4 to do it again. I used this tool (minimal adb) from this thread (https://forum.xda-developers.com/showthread.php?t=2317790) to put the code in the phone but noticed that my phone wouldn't keep the USB Debugging active and had to slide it on each time I connected to the computer (even had to revoke the computer at one point and reconnect).
From an unlocked bootloader the biggest problem I had was finding a way to put TWRP on the phone. All the threads I could see contained the wrong code to flash and so it always failed. However Dru79 showed the correct form which was to connect in fastboot then use minimal adb (on windows 10, open from the start menu, not left shict right click and 'open window here') and use " fastboot flash recovery_ramdisk TWRP-3.2.3-0-Hi6250-Askuccio-v1.0.img " - the correct TWRP is here (https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959)
HOWEVER - my phone would not keep TWRP and more often (over 75% of the time) would boot to stock recovery, SO after I flashed the TWRP I typed in "fastboot reboot" and as I pressed ENTER, I took the power cord out from the phone and used the volume UP and the Power key to get into TWRP. I don't know why my phone wouldn't keep TWRP but it didn't.
Getting root through SuperSU was IMPOSSIBLE no matter how I tried, eventually I downloaded Magisk from (https://www.xda-developers.com/how-to-install-magisk/) and flashed it through TWRP.
Once rooted, I downloaded the PixyOS from https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-pixysos-huawei-hi6250-t3852152 and flashed it...perfect!
Hope this helps someone.

The funny thing is, I actually wanted to post a thread about it in General Section as I had the same frustration as you whole trying to root and install custom ROM on this phone (I've done countless Root's, flashes, unlocking before on couple of phones) and just couldn't find a thread that explains this properly.
Anyway since you already done this, this should be moved to General Section so people can see this properly.
I've flashed Pixy's OS on my phone about 4 weeks ago and just one thing you didn't mention is that if you're on 7.1 nougat then you need to upgrade to Oreo and then install TWRP (I found that out when I tried getting it on nougat and then got errors while flashing and realised the TWRP was developed to work on Oreo). Just get a stock image of Oreo and flash it, the link for it it's somewhere around in the forum, I think it's some kind of Russian website but works well.
Anyway great job, if we can just ask Mod to move this to General section so that this guide can aid new users in rooting their phones properly and efficiently so that they can minimize their changes of encountering errors (as me and OP did).

proadi96 said:
The funny thing is, I actually wanted to post a thread about it in General Section as I had the same frustration as you whole trying to root and install custom ROM on this phone (I've done countless Root's, flashes, unlocking before on couple of phones) and just couldn't find a thread that explains this properly.
Anyway since you already done this, this should be moved to General Section so people can see this properly.
I've flashed Pixy's OS on my phone about 4 weeks ago and just one thing you didn't mention is that if you're on 7.1 nougat then you need to upgrade to Oreo and then install TWRP (I found that out when I tried getting it on nougat and then got errors while flashing and realised the TWRP was developed to work on Oreo). Just get a stock image of Oreo and flash it, the link for it it's somewhere around in the forum, I think it's some kind of Russian website but works well.
Anyway great job, if we can just ask Mod to move this to General section so that this guide can aid new users in rooting their phones properly and efficiently so that they can minimize their changes of encountering errors (as me and OP did).
Click to expand...
Click to collapse
I have asked