Related
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
Ok, I just started experiencing an issue. I suddenly can't get into recovery. Here is a little back history. My N7 was running CNA 3.6.6 (I know, but...), and I was bored so I decided to try ParanoidAndroid. Well, I have that gotta try something else feeling again, and when I try to get into recovery, it will go to the google screen, then go black for about 10 seconds, then go back to the Google screen and boot up. This happens if I reboot to recovery through the power menu, or getting into recovery from the bootloader. I even tried Quick Boot, in hopes it had some magic I didn't. No luck. The same crap. I even switched from TWRP to clockwork recoveries, and the same crap happens (I tried the same things I did originally).
Also tried through other apps too, like Rom Manager, Rom Toolbox, and TiBu. Everything works, but I am bored with this rom... I have tried turning it off, plugging the N7 into a PC and trying to get into recovery. Again, I can get into the bootloader, but as soon as I select recovery, it goes black, then fully reboots...
Anyone have any ideas? Any help would be greatly appreciated.
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
BillGoss said:
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
Click to expand...
Click to collapse
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
MetalWych said:
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
Click to expand...
Click to collapse
Scheiße, I reflashed TWRP in fastboot, and I am getting the same result. I think my N7 forgot it has a recovery!? I will try flashing clockwork through fastboot and see if this works. Thanks for your help...
Edit: Clockwork does not help. There is no recovery for me. I am now at a loss. Hopefully someone will have some suggestions...
Finally got my recovery back...damn latest bootloader!
Yeah, this has sucked. I have spent several hours figuring out what the hell went wrong. It turns out its the latest bootloader. Others are having this issue. So, I had to go back to stock (which will erase EVERYTHING) and then had to re-root. Now that my bootloader is back to JRO03D, I am back up and running.
So, the first time I did this route, I decided to take the update and re-root my N7, and ran into the same issue. I could not get into recovery. So, I had to do it all over, this time not taking the update and not updating the bootloaders, and I am now back and already have a ROM running and everything installed.
If you want to go this route, here are a couple of links that will help...
http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764328 and go to the Back To Stock section. The next part is for rooting (if you wish to do this yourself)...
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
I will post this in case anyone has a need for this info...
Unable to get into Recovery after 4.1.2 upgrade... - xda-developers
Any help?
I installed CM10.1.3 using Odin and TWRP. Well, I didn't have my contacts so I'm trying to restore it to the backup I made so I can save those to the SD card and reload CM. Therein lies the problem. I cleared the caches, restored the backup and all went well until I tried to reboot. My phone has been stuck on the Sprint screen for over half an hour and won't boot. I know the first boot takes longer but not 30+ minutes right?! What's going on?
JL-KA said:
I installed CM10.1.3 using Odin and TWRP. Well, I didn't have my contacts so I'm trying to restore it to the backup I made so I can save those to the SD card and reload CM. Therein lies the problem. I cleared the caches, restored the backup and all went well until I tried to reboot. My phone has been stuck on the Sprint screen for over half an hour and won't boot. I know the first boot takes longer but not 30+ minutes right?! What's going on?
Click to expand...
Click to collapse
Try a battery pull and start from scratch.
El Shaddai's Wrath said:
Try a battery pull and start from scratch.
Click to expand...
Click to collapse
Start from scratch as in reload the backup? Or just try to power on?
Trying both. Pulled battery and tried to turn it on with the same result. Stuck on the Sprint screen. I'll try restoring the backup again and report back.
Not looking good. Restored the backup again and clicked Reboot. 10+ minutes on the Sprint screen so far.
Didn't work. Gonna try reinstalling cyanomod. Hopefully I can end up with at least something that will fully boot.
Nothing is working. I can't even figure out how to get cyanogenmod back on the divice. Last time I downloaded that from the phone.
JL-KA said:
Nothing is working. I can't even figure out how to get cyanogenmod back on the divice. Last time I downloaded that from the phone.
Click to expand...
Click to collapse
Which build are you on? MDC, MDL,MF9, MJA? Just curious?
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget,8SMS(Stock Messaging,KitKat)
Simply try a factory reset in your recovery.
I would also recommend a factory reset, either through recovery or from ODIN. Worth noting that, if you back your contacts up to your Google account, you can import them from there when you reload, without having to reflash, export to SD, flash again. This could also work for you in the unfortunate incident that you have to factory reset without a functioning backup (like now).
Also, Titanium will of course back up contacts and MMS/SMS, for future use once you get through the soft brick.
Hey Bud, just got your PM. One thing I Noticed with the S4 is that restoring nandroids can be a real pain. I struggled with mine for hours before I came up with a way to get it done AND get root back, which was my problem.
Granted, I'm on US Cellular, but it should work the same way
The first thing you need to do is make sure you're using Odin 3.07 As Administrator
Get into D/L mode (Power + Vol Down, then hit Vol up when the screen appears - works better if you're not connected to your computer yet)
Connect your phone and open up Odin, then check Reboot, PDA and flash the stock ROM for your phone.
I THINK the .tar file is in THIS Thread
Click start, once it loads into Odin, which could take a minute so don't freak if you get Odin (Not Responding)
If it boots back up into stock, you're golden. Then you can try and re-root as normal.
Now, the problem I had, was getting Root back. It just wouldn't take, even though it showed Success, using CF Auto-Root, Klingo, etc. All of them. SU got installed, but binaries would not install, SO, here's the procedure to get Root back.
You'll need the Chainfire SuperSU Update on your SDCard and you'll need the .Tar file for either CWM (I recommend) or TWRP for the Sprint S4. Not sure where to find those but someone will know on here
Put the SU Update on your sdcard
Boot to Recovery (Power +Volume Up)
Do a Factory Reset then reboot. Skip over the setup
Power down then reboot to Download Mode
In Odin, Use PDA to browse to the CWM.tar and run it - Now you have Custom Recovery
After Phone boots up, power down and reboot to recovery.
Flash the Chainfire SU Update
Done! Just like that.
Power up and check root
Hope this helps, neighbor
All good guys. Thanks for the help.
Hi,
My i9505 Intl (Australian Telstra LTE) SGS4 has been rooted for a year at least now, and recently (a few months) had TWRP recovery and CM13 installed and everything was going great. I loved CM!
Anyway I had done a few nightly patches of CM and all seemed good and then a week ago I installed the most recent nightly (possibly this one cm-13.0-20160819-NIGHTLY-jfltexx-recovery.img ). Well the subsequent reboot put the phone into a boot loop. So I thought no problem just boot to recovery and install my recent Nandroid back up. So did that but in my haste didn't clear cache or data. The nandroid reinstall seemed to go ok but a subsequent boot hung at the CM logo (I think it was a while ago now) and I couldn't boot to recovery, just hung with the blue text.
So I fired up Odin and booted to download and reflashed with TWRP. Boot to recovery still didn't work however I could still boot to download.
Tried different USB ports, different versions of Odin, re installed drivers to no avail. Also tried CWM, TWRP and Philz recovery and once I did get it to boot to recovery with Philz. THIS TIME cleared cache and data and loaded a good copy of CM that I had on my SD card. Again stuck in boot. Couldn't get back to recovery.
Tried loading the orginal samsung firmware and they I was stuck with a Samsung logo boot looping. Ditto recovery just hung at the logo and the blue text "recovery booting".
Rinse and repeat a few times and now the phone has started to become difficult to get into download or recovery. If I leave it with the battery out for a while it seems to come good again.
Odin when flashing a new recovery either hangs half way though or completes and says everything is OK. Full blue bar on the phone.
Rebooting however still leaves me in the boot loop.
There is no mention on Odin of any issues with the partition however I have d/l a PIT file from one of samersh72's posts but am not sure if it is the correct one for my Int phone or indeed if I need to use it as Odin doesn't seem to report any partition errors.
If any one has any suggestions I am very receptive to ideas right now.....
Thanks
Did you perform a factory wipe after flashing stock before booting the rom for the first time?
audit13 said:
Did you perform a factory wipe after flashing stock before booting the rom for the first time?
Click to expand...
Click to collapse
I did a factory wipe and then installed CM from my SD card but that is the only time I have able to get into recovery since the first time when I reloaded my nandroid backup
Did you try flashing recovery without selecting auto reboot? Once flashed, remove USB cable, remove battery, replace battery, try to boot into recovery.
audit13 said:
Did you try flashing recovery without selecting auto reboot? Once flashed, remove USB cable, remove battery, replace battery, try to boot into recovery.
Click to expand...
Click to collapse
Yup tried that, as I realised that the auto boot might be overwriting the custom recovery...........however as a new development I haven't been able to boot to download or even the stuck recovery since yesterday.
I think it has now moved to a full hard brick
Is still turns on? You have a USB jig to try?
audit13 said:
Is still turns on? You have a USB jig to try?
Click to expand...
Click to collapse
No I don't have one but I have all the makings of one so i'll put one together and give it a go. Though I have to say that I am not that hopeful as I can't even get a peep out of it now.
A jig may be the last solution before sending it for repair or replacing the motherboard.
audit13 said:
A jig may be the last solution before sending it for repair or replacing the motherboard.
Click to expand...
Click to collapse
Thanks Audit, Ill let you know how I get on. Just looked at some replacement motherboards and they don't seem too common for the LTE version used here in Australia AND USD60......pretty much get a working phone locally here on ebay for that and I get the rest of the parts too.
Have you tried already flashing a stock rom as a tar file from sammobile?
justgamer01 said:
Have you tried already flashing a stock rom as a tar file from sammobile?
Click to expand...
Click to collapse
Yup did that as well!
Ghostdog1 said:
Yup did that as well!
Click to expand...
Click to collapse
I'm not sure if it will work! But try emergency recovery with Smart Switch!
justgamer01 said:
I'm not sure if it will work! But try emergency recovery with Smart Switch!
Click to expand...
Click to collapse
With Smartswitch I get the same outcome as with Kires
"GT-I9505 does not support initialising. Please contact our service centre."
But on the plus side it is actually responding to button presses today. I will pick up some 100K resistors tomorrow and finish off my USB jig. See how that goes.
Well it appears to have finally died fully. No response to any button or combination of button presses. Made up a USB jig but without some response to a boot that won't work either.
Thanks to Audit and Justgamer for your advice. Think it is time to draw a line under this one and move on. Maybe a new Nexus when they drop?
Heads up, this is a bit of reading
Ok so two nights ago, I was messing with the phone a little bit attempting to put Google Assistant on the phone. I had gotten a new cable from Amazon which enabled me to finally plug my 6P into the computer and my bootloader was already unlocked as I did so before but the issue was that I didn't have twrp yet on my phone. After I got it all set up with adb/fastboot etc. I tried to flash twrp. It didn't work, I kept getting stock recovery to come up so I ended up chalking it up for another day. As I was watching my beloved school lose in the Rose Bowl, I realized that the phone was rebooting. Not sure why but it just started doing it. After that, the phone turned on after rebooting for about 45 mins and it stood on for about 10 mins. After that, it went back to bootlooping and did so without getting to the android boot up screen all night.
Pissed, I decided to try to fix it myself but after I woke up, I found the recovery to be inaccessible through the bootloader which I could previously enter even through all of the bootlooping. After the bootlooping started, I couldn't flash a recovery so figuring it was the new cable, I switched to the older one. Well after doing that, I was able to flash the stock recovery and get adb working again. Using a guide, I flashed the newest factory image that was just released which is N4F26J (my phone was on the NMF26F update), and after a few bootloops, the phone turned on!
Ecstatic, I skipped past all the setup screens and went immediately to developer options and I activated usb debugging. Shortly after this, the bootlooping restarted and I wasn't able to get it to get back to the phone. Using the Wugs toolkit, I continued to use that to get the factory images on the Nexus and usually after I would use it to flash the ota, it would reboot a few times and get to the welcome screen where I could use the phone for about 5 mins. before it started bootlooping again. Fearing it was just Google's OTAs, I switched ROMs using twrp and adb to this ROM https://forum.xda-developers.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600 (All Credit For The Rom Goes To Him), and after a few reboots, I got it up and running but after a few mins, the bootlooping started again. I noticed that when I use the toolkit to get into the twrp recovery, it constantly says in Red Letters about it not being able to mount storage.
If anyone please can help me figure this out, I would really really appreciate it. I can't send it to Huawei because it has a very slight crack on the screen and with me being a college student, I can't afford the $160 that they want to replace it. Somebody please give me any type of insight so I can try to fix this on my own. Please
btw before every flash, I followed all steps you should with wiping cache, dalvik, etc. Not sure if that would make a difference
Exbruce said:
Heads up, this is a bit of reading...
Click to expand...
Click to collapse
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
v12xke said:
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
Click to expand...
Click to collapse
Ok I'll give it a shot and let you know how it goes.
Exbruce said:
Ok I'll give it a shot and let you know how it goes.
Click to expand...
Click to collapse
I think the problem you had with TWRP not sticking on Nougat is that you need to flash SuperSU after or the phone will revert back to stock recovery. Not that it helps with your boot loop issue.
v12xke said:
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
Click to expand...
Click to collapse
Tried it and no dice. Hasn't stopped bootlooping for the past hour
I think you have the issue aoy of us are having which after three or four days I have not been able to fix. RMA with Huawei maybe the only way out of it.
Sorry man it doesn't look good.
v12xke said:
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
Click to expand...
Click to collapse
galakanokis said:
I think you have the issue aoy of us are having which after three or four days I have not been able to fix. RMA with Huawei maybe the only way out of it.
Sorry man it doesn't look good.
Click to expand...
Click to collapse
Yeah it sucks simply because I've managed to get it from not booting to recovery to booting to the Rom but it just won't stick. This is hands down the worst experience I've ever had with a phone. The fact that Huawei wont replace it without that $160 is ridiculous to me because I've really done nothing wrong with it, it just konked out leaving me without a phone. Wow
Its probably google trying to force us into a pixel phone. If my 6p eats it, im done with Google phones. I love this phone. Its the best ive ever had. I'd definitely pay 160 for another if they could assure me no more bootloops. It sucks for people that can't afford it.
Exbruce said:
..... After the bootlooping started, I couldn't flash a recovery so figuring it was the new cable, I switched to the older one. Well after doing that, I was able to flash the stock recovery and get adb working again. Using a guide, I flashed the newest factory image that was just released which is N4F26J (my phone was on the NMF26F update), and after a few bootloops, the phone turned on!
Ecstatic, I skipped past all the setup screens and went immediately to developer options and I activated usb debugging. Shortly after this, the bootlooping restarted and I wasn't able to get it to get back to the phone. Using the Wugs toolkit, I continued to use that to get the factory images on the Nexus and usually after I would use it to flash the ota, it would reboot a few times and get to the welcome screen where I could use the phone for about 5 mins. before it started bootlooping again. Fearing it was just Google's OTAs, I switched ROMs using twrp and adb to this ROM https://forum.xda-developers.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600 (All Credit For The Rom Goes To Him), and after a few reboots, I got it up and running but after a few mins, the bootlooping started again. I noticed that when I use the toolkit to get into the twrp recovery, it constantly says in Red Letters about it not being able to mount storage.
Click to expand...
Click to collapse
There well may well be a hardware problem with your device BUT I read your post again and I see a few possibilities. One is that you may have been using an unreliable data cable, and you didn't mention hash checking files before flashing. Second, it sounds like you had installed a factory image, and afterwards applied an OTA to the phone (and then a custom rom). Once you apply the full N4F26J image, there is no need use any OTA! Start with the latest image. Lastly, your data became encrypted when you booted the first time so you are getting mounting errors in TWRP. My advice would be to reformat again as above, manually download the full factory image N4F26J and use NRT to install it. NRT has not updated the toolkit yet, so you will have to d/l manually. NRT should hash check the file you downloaded. Use the bricked mode to Unroot+Flash Stock. You never mentioned running unencrypted, so I assume the default encryption is what you want. The idea is to attempt to get you back to stock with a device free from bootloops. If this doesn't work, then you'll need to use ADB.
v12xke said:
There well may well be a hardware problem with your device BUT I read your post again and I see a few possibilities. One is that you may have been using an unreliable data cable, and you didn't mention hash checking files before flashing. Second, it sounds like you had installed a factory image, and afterwards applied an OTA to the phone (and then a custom rom). Once you apply the full N4F26J image, there is no need use any OTA! Start with the latest image. Lastly, your data became encrypted when you booted the first time so you are getting mounting errors in TWRP. My advice would be to reformat again as above, manually download the full factory image N4F26J and use NRT to install it. NRT has not updated the toolkit yet, so you will have to d/l manually. NRT should hash check the file you downloaded. Use the bricked mode to Unroot+Flash Stock. You never mentioned running unencrypted, so I assume the default encryption is what you want. The idea is to attempt to get you back to stock with a device free from bootloops. If this doesn't work, then you'll need to use ADB.
Click to expand...
Click to collapse
Ok I'll give it a shot and let's see how this goes *fingers crossed*
UPDATE: Gave it a shot and it booted up to the welcome screen for about 2 mins and then started the bootloop all over again. Looks like the only option is to RMA the device at this point
Exbruce said:
Ok I'll give it a shot and let's see how this goes *fingers crossed*
UPDATE: Gave it a shot and it booted up to the welcome screen for about 2 mins and then started the bootloop all over again. Looks like the only option is to RMA the device at this point
Click to expand...
Click to collapse
Your phone is worth a lot more than 160.00 so it's probably best to RMA even if the charge seems unfair. You could always sell the RMA phone for a lot more than 160.00 if you've had enough of the 6P.
Exbruce said:
UPDATE: Gave it a shot and it booted up to the welcome screen for about 2 mins and then started the bootloop all over again. Looks like the only option is to RMA the device at this point
Click to expand...
Click to collapse
Sorry to hear that. Not ready to throw in the towel?
Have you tried doing a factory reset after the latest bootloop?
Any errors when formatting the 3 partitions, or during the flash process?
It could be looping for some reason during the initial encryption process which happens during first boot. I would try using a "no force-encrypt" modified boot.img before booting the first time to prevent the encryption process. If you prevent encryption, you may prevent the bootloop. You can find the boot.img on this forum, or use Wug's from the previous build, or even flash SU 2.79 to modify your boot.img.
If that doesn't work, you could try extracting files you need from the factory image, fastboot format and flash img files manually, including the modified boot.img.