This will save you 8-12 hours of your time if you are lucky. This means that it also includes the meaningful links of 8-12 hours of searching. Sentences in italic are important. 1 link is for the Odin official website, the rest are re-links back into XDA.
The device in question is a SM-925T Tmobile S6 Edge.
The problem was this. I rooted my phone and messed around with Greenify and the Play store. To prepare for rooting, I allowed unknown downloads, unlocked the bootloader, and turned my security lock off (I had set it to a finger print lock). After I was done rooting, I immediately locked the bootloader again(<--A mistake that caused my bootloop/ soft-brick). After I was finished messing with the above apps (Greenify, etc), I wanted my phone to restart. So I held the Power button and selected restart, while I was on the lock screen (may not be important). I noticed that it took a long time to restart, and upon closer examination, I noticed another error under the "kernel is not seandroid enforcing" (which appears to be natural for rooted phones). The error was "Custom Binary blocked by FRP Lock". It was a new error. I investigated this new problem using the internet , and this dude was panicking like hell, but he didn't appear to fix his problem. He did hint that returning to the bootloader to its locked state was a mistake. Looked a bit more and this guy pointed to another thread, which introduced me to flashing and more importantly his fix, which was to flash the stock 5.1.1 image through odin. He used this link, which contains all the stock firmware for the majority of the new Samsung S6 and S6 edge versions. To make a long story short, most of these fixes involved flashing your firmware to the stock version. So I went to the Odin Website, and downloaded every version, as a couple threads have said that different versions worked for them. Here is a thread with everything you need for Odin. Now, after sorting through and finding micro USB cables that are detectable by Odin, an important step because Odin might develop a pattern of detecting then failing to detect your device through that cable, and testing all the usb 2.0 ports, I was ready, and had Odin with my stock firmware. Odin kept saying "NAND Write", then in the next line "FAIL". This was annoying as Odin wouldn't detect my device again unless I unplugged it, restarted it to download mode, then restarted Odin before plugging it back in. I got confused and found links for somehow fixing the .tar files, stock roms, .pit files (DO NOT MESS AROUND WITHOUT KNOWING WHAT THOSE THINGS DO), and other threads/websites that say to boot into recovery mode , factory reset, then wipe your cache. I could only do that once. After me messing around with all of the above file variants and supposed fixes to help with my issue, I couldn't boot into recovery mode, it got stuck on the "Samsung Galaxy S6 Edge" logo. It did not fix the NAND write failing. There however, are a lot of websites allowing you to download stock software for your phones, and I don't think I can link them as it might break a rule. Surprisingly, some have claimed that using a stock file for another device worked to fix their problem. This thread, which convinced me to use Smart Switch when it failed for everyone else, was very useful, although I recommend downloading Smart Switch from the official website of Samsung. None of the Odin flashing had worked so far, including the Roms and .pit files so I tried Smart Switch. I opened it, and upon selecting the "more" tab on the upper right corner, a bunch of tabs drop down. One should be "Emergency Software recovery and initialization". I had to find my S / N (Serial) number, and I was very confused on how to obtain that number as I was locked out. But to obtain it, do the same process to boot into download (hold volume down, home key, and power key), but stay on the prompt and don't go to the screen that has the word download in the middle. Don't do anything other then reaching the prompt confirming if you want to install a custom ROM. Then, press the home key and it should show your S / N number along with your IMEI number. Once I imputed the code I saw on my phone into Smart Switch, it told me to connect the device. Now, by this time, I realized that Odin only detects my device if it is actually in the download screen. Why shouldn't my computer? I booted into Download on my phone and followed the steps on my computer, making sure that the computer can recognize my phone while it is using a valid USB port and Cable. And after some waiting, for me, my problem was fixed and I could use my phone again, it reverted to it's out-of-box state. I hope this drawn out but very specific explanation helps you guys. It's my first post And also, this thread confirms that you can use a USB hub for flashing(at least for ROMS), Smart Switch, and for rooting.
Thank you for this detailed account, however nothing of the above has worked for me. Odin won't flash the firmware of 5.0.2 (and I tried 5.1.1) and Smart switch does not recognize the device to do anything. BTW phone has been rooted for months and last night decided to turn on its FRP lock randomly and now I'm stuck. Any help would be greatly appreciated.
Explain throughly what you have tried. Especially different ports, cables, and computers. Did you have the right device drivers? Did you do anything else?
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Xalmey said:
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Click to expand...
Click to collapse
press vol down home keys and power key once you get to the first blue screen release vol and power keep holdind home but I already tried smart swich didn't help
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
EsperaKing said:
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
Click to expand...
Click to collapse
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
callumbr1 said:
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
Click to expand...
Click to collapse
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
EsperaKing said:
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
Click to expand...
Click to collapse
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
callumbr1 said:
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
Click to expand...
Click to collapse
Thank you for you reply.
Please can you tell me where I can find such software or how to do it clearly! I know how to use Odin but I don't know how to exclude user_data to be wiped. Thank you
Bonafid3 said:
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Click to expand...
Click to collapse
Thank you thank you thank you!!! This is exactly what I was looking for I had just rooted my note 4 running 6.0.1 and had no idea what the oem option was as no rooting method talked about it at all so naturally as soon as i added my Google account phone restarted and locked up.
Kies was the answer I needed as frp lock was active in download mode and my factory reset in recovery failed everytime but running Kies firmware upgrade and entering my model and serial number it installed perfectly in download mode with frp lock still active saved me alot of hassle ?
Hi guys. Sorry if this is in the wrong section. I have rooted several phones a few years back such as HTC's etc. However i have been running into a problem with the J5. I believe I have installed the samsung drivers, i have rooted the phone on the software itself via kingroot, however when I try to run ODIN it detects the phone COM/USB port however when I try to flash any of the recovery files it looks as if its going to start to do it then says 'FAIL' and when I look at the phone nothing happens (when its in blue recovery mode) it just says Custom Binary (Recovery) Blocked by FRP Lock - I have tried to search this on the forums but cant find many solutions for it with regards to the J5 - Does anyone have any suggestions? I dont mind the phone and would like to install custom kernel on it to allow for slight overclocks etc as its quite a nice bang for buck phone. but I have spent hours and can't seem to find a solution. There was one post that seemed to suggest if you downloaded a 'CROM Services' APK whilst in android and run that it might work, however this is a new J5 on the latest android and the CROM Services APK file in that link doesnt seem to want to run when i install + try to run it on this android
Any suggestions are welcome! Really wrecking my head over this one
FRP lock means that you have to enable OEM Unlocking in Developer options and/or remove the Google account. FRP is Factory Reset Protection, introduced with Android 5.1.1. Prevents someone from just grabbing your device and wiping it and using it easily. Also, you need to be in Download Mode, not recovery to flash custom kernels and recoveries. You aren't wanting to or trying to install a custom bootloader. That is a whole nother thing.
Thanks for the info! That one option has solved it for me! I will go from here and see how it goes. Thanks alot!
Hey,
So I was trying to root my phone (been trying for ages now) and I've been following loads of guides because each one never seemed to work. Now, I know I haven't bricked my phone, but I've somehow managed to lock myself out of it instead. I can't use the fingerprint lock, and the password that I use doesn't work (it says I've put in the wrong password, but if it isn't that, then what is it?).
I tried hard resetting my phone but it didn't work either (I have an unlocked bootloader btw). I tried looking it up and all the guides I followed ended up taking me to recovery mode (which also doesn't work - it doesn't connect to my computer because it defaults to "usb for charging" instead of MTP).
This is really stressing me out and I don't know how to fix it. I've been trying for hours and it will not unlock, no matter what I do. I even tried to do that Google account unlock thing, but there's no "Forgot password?" on the lock screen.
I feel like I'm screwed. Please help.
- Roisin.
You don't need MTP for usb debugging, if you previously enabled it.
Use step 5 from here to delete the gesture.key from your device.
If you have TWRP installed you could also use it's file manager to delete the keys.
Thanks for the quick reply
Does it need to be rooted for this? I never actually managed it. Also, I don't think I have ADB on my computer, how do I do this?
@WizardyNinja Get [TOOL]Minimal ADB and Fastboot [10-22-16].
Don't know if the 'adb shell rm .....' needs root.
How where you trying to root with out the above tools?
Once you have fastboot, use it to boot TWRP: -
Code:
fastboot boot <nameofTWRP.img>
And then use it's file manager to delete the file, if the 'adb shell rm.....' does not work.
I don't know actually, I saw ADB mentioned around a few times but it was really just a "download these few things and it should work" kind of thing. I've rooted devices before but Xiaomi devices are so much more awkward, it really confused me. By the end I didn't know what I was doing. :/
I'll try this out tomorrow and I'll update you on if it worked or not. Thank you.
If you can enter recovery then go to /data/system and delete all the *.key files.
Sent from Note 3, Xiaomi Redmi Note 3.
I can't get into recovery, that's the problem :crying:
I haven't tried the other thing yet, still in school
Okay, so I managed to fastboot TWRP because the other thing didn't work, but now TWRP itself is asking for a password to decrypt data? As far as I'm aware, I never encrypted my data purposefully on my phone.
(Couldn't get a clear picture, but the buttons say "cancel" and "select language". On the top, it says "Mount" with "Decrypt Data" under it).
@WizardyNinja
Just select cancel, in your screenshot.
Then format your data partition (unfortunately losing data and apps).
Then reboot and you should have access to your device, plus have to set it up again.
Would a factory reset be fine, or would it have to be an advanced wipe?
Nevermind, I wiped it. Thank you!
Do you think you could tell/link me a way of rooting this phone? It's so confusing and I haven't found any instructions that I can follow clearly. :/
WizardyNinja said:
Nevermind, I wiped it. Thank you!
Do you think you could tell/link me a way of rooting this phone? It's so confusing and I haven't found any instructions that I can follow clearly. :/
Click to expand...
Click to collapse
Now that you have cleared your locking problem, search for SuperSU and flash it on TWRP.. Voila, you are rooted.
Sent from my Xiaomi Mi 5 using XDA Labs
Htc M9
unlocked
S-ON
os 3.38.502.31
Hello. i am very lost, very confused, and yeah much help appriciated.
i fix phones for a living, but have never dipped into the development side of things, so i gave it a shot by trying to root my m9.
i installed the android studio ADB thing and of course the htc drivers from htc-sync manager needed to do this.
i unlocked the bootloader with no issue and was able to use the OS just fine after that. after that it was onto rooting my device.
i was unaware of Nanadroid backups or similar programs so theres that
i used superSU 2.64 and TWRP 2.8.7.1a-CTB1-B1 for the custom recovery
when flashing superSU i was prompted it was successful and would now boot into the OS and a few reboots is normal. after waiting a while i knew it wasnt going to go through and that i had screwed myself.
i tried a couple different SuperSU versions with no luck, perhaps the TWRP is too outdated? could not find a way to update TWRP.
eventually after trying multiple different things, on the bottom of the download screen it prompt the 0PJAIMG.zip file was missing, searched for the right one but could not find it.
found an older one and it now gives me an option as soon as booting into the downloader to flash /mnt/media_rw/ext_sd/0PJAIMG.zip or cancel.
selecting cancel puts it intodownload mode.
when selecting "flash" it prompts "RU_MODELID_FAIL modelid in android info mismatched" flash fails, and then turns off.
the phone will reboot continously until power and vol down are held and put into download mode
Can anyone tel me where i need to go from here? What adb/fastboot do i need to be using?
Can anyone spell it out for me? im seriously so lost.
TIA
So, for Christmas my daughter's mom got her an A33 Q88H QuadCore Softwinner tablet, and we discovered the OS it came with had some very strange issues related to a lack of compatibility with Google Play, so I tried to get around that with software, but I needed to be rooted. However, I had bizarre difficulties with SuperSU, unlocking the bootloader, rooting, and even more difficulties trying to flash a custom recovery that I could use to ROOT-- the obscure china tablet had no TWRP or CWM support. I finally tried a very convoluted method of flashing what appeared to be a ROM for the A33 Allwinner tablet, which hadTWRP already installed, so I could use TWRP to root it, and then finally fix the software issues.
However, the process didn't work, and when I rebooted the phone, I found it stuck on a black screen with a tiny android symbol, and that's how it's been since. Holding volume and power button only reboots it to the same screen -- no bootloader or anything, so I can't find any way to try to flash a factory ROM to get it back to regular settings. When I plug it into my computer, it makes the input noise, and shows up in Device Manager as "Android Device" with "Android ADB Interface" drivers successfully installed, but ADB doesn't recognize it as a device, and I can't get it into any sort of download mode -- it isn't recognized in My Computer as a hard drive. So, I can't find a way to interface with the tablet to reflash a stock ROM. :frown:
It's her Christmas present, so I don't want to admit that I've broken it; I've been trying to solve it all night for 12 hours straight, but I just can't find anything that works! Is there any way you guys can help me? :crying:
I tried to attach some pics but the uploader isnt working.
bump