Hey everyone,
I'm sorry if this question has been asked before. I have looked but can't find a definitive answer.
I needed to unroot my Nook because I could no longer download books which I purchased online. First, I did the factory reset. I was successful but could not complete the registration process. I got to the part where it asks for my email and password, and I always get 'Sorry we're having trouble setting up your NOOKcolor. Please shutdown the device and try again.'
I called Customer Service- what a joke. They determined, after almost an hour on the phone, that it was a deregistration issue on their end (I did it on my end as the 2nd step of the factory reset).
I thought that maybe it wasn't competely unrooted, so I did another reset by flashing the latest version of CWM and a stock zip file (followed Huskermania's video). I ended up having to use 1.0.0 stock because CWM determined that 1.0.1 and even 1.3 stock files were 'bad'. I got a boot loop at first and then it automatically downloaded updates. The Device Info screen says it's 1.1.0.
Still can't reregister after chatting with a 3rd rep online and 5+ attempts to deregister on their end. Has anyone successfully gotten BN to replace their device while having this problem? I did not tell them I was unrooting, just that my device froze during use. I hope I don't end up with a paperweight!!
Hello,
I have a Asus zenfone 6 however my problem also occurs on the zenfone 5 phones.
The poblem is as follows,
After updating from stock to latest android (v1,18 at the time) the phones battery display became incorrect making the Phone unreliable at bestand nothing seems to help fixing the problem.
I have tried a million calibratnig apps with zero success as suspect the phones software doesnt actualy understand that it has a 3230 mah battery.
I have found and compared files with a working zenfone6 where the file displays 2070mah for me and 3230 for the working Phone.
I then tried to manualy change this file had no acces even with root but every reboot or unplug it just resets the file anyway as it gets its data elsewhere.
I have tried a factory reset but not everything was actualy reset it just deleted my data but roo and all othr crap that the update screwed up was still there.
I tried ADB sideload but that didnt work and udupdates as ota so will not factory reset and remove root anyway.
I contaced asus but they are as clueless as a goats rear and just say a future update will adress it...Which we al know isnt going
to happen as this has bin a issue for some users for over half a year and they didnt fix it.
So as a final attempt to fix this Phone im planning on unlocking the botloader which i really didnt want to do as im new to all that and just want a rooted stock rom...
So to my question.
If i unlock the bootloader i know the Phone will be wiped. Will i just be able to flash any version of the stock rom via ADB or is there other things i need to do to either the Phone or the rom?
I cant go screw up my Phone without knowing how to fix and flash it again directly.
And do apps like the one asus provide usualy also allow relocking of he bootloader again after flashing the rom as i dont want to leave it open if there is no need to?
Any other ideas are welcome aswell but i have bin trying to solve this for over a month.
Heres a screenshot of the error i get when i try to reflash current rom with ADB.
http://oi60.tinypic.com/2eefzuv.jpg
But as long as that doest a full clean rom install its not helping me anyway.
i really hope someone has a easy and quick way to do a fresh install that will really make the Phone like it was just out
of the box software wise. no root no changes or anything as factory reset is not doing that for me.
Thanks in advance.
Hutjeflut.
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 ?
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?
Oh guys, I badly need your experties. Just as I have in the title, I have a rooted Meizu M5 Note. I rooted the phone believing that I can do much more if it is rooted. But in 6 months of trying to understand what I can do with this said rooted phone, I realized now that there are not much to do with it... Probably because of the brand, so I decided to unroot
The rooting process was from here: giving me error so if requested, i'll give the link.
I have an Android build 7.0.0.0
So here is my issue:
In the same site, I found that I can unroot.. yes, UNROOT the rooted model of phone using superSU by going to its Settings and clicking unroot (or Unroot all something..). It took a bit while, so I decided to restart the device. Yes, while SuperSU was trying to unroot my phone.
Upon restart, it now could not boot.
I allowed 30 minutes, the screen only shows Flyme logo with a spinning circle. So from here, I made up my mind to perform the factory reset/restore:
Turned off Phone > Press and hold Power key + Volume Up... until I reach the screen with options to:
-Update system.
-Wipe data.
I selected Wipe data, for it will reset the system settings. It will now show the
"Wiping data.
Please dont turn off the phone, or it may fail to boot"
It will only last for 2 seconds - and will then again reboot and stop in Flyme logo with a never ending spin below.
_________________
It was already the factory reset, which I thought should help, but it wont work.
_________________
Things I tried:
- Used ADB to flash an offcial update rom from the flymeos.com, but the ADB Flashtool would not read the device because the USB Debugging is turned OFF.
- Googling any possible solutions, but cannot find any - nor any known programs that will allow me to read the not booting phone.
- Fast boot or safe mode, which only wont proceed.
- The Recovery Menu (the un-clickable one) must be locked by the manufacturer.
Can anyone please tell me:
- Is there anyway I can access the phone's drive so I can put the Update zip folder, which will help me to use the 1st recovery option "Update system"??
- Do you have any software that can help me enable the USB debugging when the phone wont boot at all??
Thanks guys..
All the help I can get will be best appreciated.
I tried posting this to forum.FlymeOS, but no one seems to have any interest on helping.
It is now you, that i think can help.
This is my Only phone, and cant afford to lose it...
Same issue with my Meizu M5 Note. I tried a tutorial on how to unlock it's bootloader. But after going through the first step, the SP Flash tool showed some error on how it does not turn on our go recover mode or anything... In really sad
Somebody please help!
RogueDiamond195 said:
Same issue with my Meizu M5 Note. I tried a tutorial on how to unlock it's bootloader. But after going through the first step, the SP Flash tool showed some error on how it does not turn on our go recover mode or anything... In really sad
Somebody please help!
Click to expand...
Click to collapse
Looks to me that you've bricked the phone.
jwoegerbauer said:
Looks to me that you've bricked the phone.
Click to expand...
Click to collapse
Yeah... Well, atleast I can ask for new phone now! LMAO