Database Users

Unable to boot to CWM

So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7

Okaay said:
So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Click to expand...
Click to collapse
root the tablet
then install ROM manager and flash the official recovery from there
works perfect

The bug is that you cannot boot into any recovery (cwm/twrp/stock) from bootloader unless you are plugged into you computer via a usb cable. The only other way to boot is to use a script but that requires a working system partition.
Sent from my Nexus 7

I have the same problem and I flashed the official CWM from Rom Manager. I made a nandroid before I messed with it and when I went to change the LCD Density, I don't know what happened but now it won't boot. I can't get into CWM either. I figure I'll use ADB when I get home to try and reboot into recovery, if not I'll search the forums for the stock image and reflash. If there is a HW workaround to get booted into it from the device itself that would be awesome. I had to do a battery pull to keep it from rebooting itself and killing the battery.

I've always had Rom Manager Pro and immediately after rooting, used it to flash backups, update to 6.0 cwm, etc. If your rooted you must have that or Goo Manager for TWRP flashing anyway. Might as well start immediately.
There is a thread somewhere here dealing with changing density. The Nexus7 has problems when you simply use a density changing app.. You must change density by modifying prop.build. You can do this using a root explorer app, or by using Rom Toolbox Pro. I use Rom Toolbox and it worked perfect.

Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?

chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.

I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.

jmhalder said:
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
Click to expand...
Click to collapse
Will that command allow me to access recovery to restore my backup?
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
yeahthatsme said:
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
Click to expand...
Click to collapse
I believe you need to be on the bootloader screen? I haven't flashed anything from Asus in a while, not since my original Transformer.

chrisjm00 said:
Will that command allow me to access recovery to restore my backup?
Click to expand...
Click to collapse
Code:
fastboot boot recovery.img
where recovery.img is a CWM image, should allow you to get into the recovery to fix whatever you messed up. Note that ADB is only functional if you already have CWM or Android booted... in the bootloader, fastboot is all that's available.

I have the same issue. Stuck at the Google logo with a padlock at the bottom. I didn't flash anything with ROM Manager just the recovery.img through fastboot, then did a fastboot reboot. Now I'm lucky if I can get the thing to stay off when I hold the power button it just pops back up to the padlock with Google logo.

When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?

CooLoserTech said:
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
Click to expand...
Click to collapse
Has anyone figured a way to access recovery using the buttons only? I've tried TWRP 2.2 and the newest cwm, and on a cold start from power off, it sticks at the Google logo. During a bootloop you are screwed unless you have a laptop within arms reach. Until this is rectified I'm leery of flashing anything. The whole point is being able to restore a nandroid in a crisis. I haven't found that ability yet. If anyone knows a way, please educate me!

Guess we can just wait. Besides there's not much development yet anyways. Would love to use AdFree and root explorer though.
Sent from my Nexus 7

chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
Recommend downloading quickboot. It is a paid app but it boots you to recovery no hassles with the buttons
Sent from my Nexus 7 using Tapatalk 2

Ya i have tried several version of CWM and TWRP and manually reinstalled cwm via adb. but all of them don't let me boot from the bootloader, i get the google logo like everyone else. Not sure what else to try, need to not take any risks until there is a fix i guess ^_^ hope someone gets some ideas

Stuck in bootloop after N7 reset on it's own

My N7 is rooted and stock... I used the N7 Toolkit method... My N7 is 32gb non-3G version...
It's been working fine, no problems. I thought that it was a little laggy since I installed a 2nd account on it ... so a day ago I deleted the 2nd account hoping to get rid of the lagginess that started after installing the 2nd account.
Today I came home with the N7 and I heard some notifications when it logged into my Wifi... And about 30 mins later I went to use it and the wall paper that is usually showing went black, the screen did some funny things and the tablet reset.
Now it's stuck in a boot loop...
I can get into the bootloader and recovery, but whenever I exit, it goes back into the boot loop.
Since I hadn't installed anything custom when rooting, do I even have Nandroid? Can I back it up and connect to USB before wiping?
Does wiping erase the SD portion of the memory?
Any ideas for troubleshooting? Would love to know what happened here...
Thanks...

What did you come up with by searching the forums or Google?

Hemidroids said:
What did you come up with by searching the forums or Google?
Click to expand...
Click to collapse
As with many things, the info that I found is conflicting. Since I had been burned by trying things before verifying what I was doing, for once, I decided to reach out for advice BEFORE I erased something that isn't recoverable.
Yes, I know that many on XDA hate users who ask for help before researching on their own. The problem for me is that I couldn't find a clear answer.
Since I made my post, I tried a few things...
Details and questions are here: http://forum.xda-developers.com/showthread.php?t=2089144
Thanks for your response, although I get the feeling that you had expected me to know the answer to my question...

OldDogEyes said:
My N7 is rooted and stock... I used the N7 Toolkit method... My N7 is 32gb non-3G version...
It's been working fine, no problems. I thought that it was a little laggy since I installed a 2nd account on it ... so a day ago I deleted the 2nd account hoping to get rid of the lagginess that started after installing the 2nd account.
Today I came home with the N7 and I heard some notifications when it logged into my Wifi... And about 30 mins later I went to use it and the wall paper that is usually showing went black, the screen did some funny things and the tablet reset.
Now it's stuck in a boot loop...
I can get into the bootloader and recovery, but whenever I exit, it goes back into the boot loop.
Since I hadn't installed anything custom when rooting, do I even have Nandroid? Can I back it up and connect to USB before wiping?
Does wiping erase the SD portion of the memory?
Any ideas for troubleshooting? Would love to know what happened here...
Thanks...
Click to expand...
Click to collapse
First if you have a custom recovery, boot into that, wipe cache, then dalvik, and try rebooting. See if that works.
Nandroid would be the backup of your entire ROM that you made either using ROM Manager or manually initiating a backup in recovery.
Wiping using ClockworkMod Recovery or TWRP Recovery will leave the /sdcard area (/data/media) alone, however it'll remove your ROM. At that point, you'll need to re-flash a custom ROM to your device. If you reload the stock N7 images from Google, it WILL erase your /sdcard section!
You can push files to your device while in recovery using the adb push command. You can also pull files from your device using the adb pull command.
adb push <name of file> <location on device you want to push to>
EXAMPLE: adb push ROM.zip /sdcard/
adb pull <location of file on device>
EXAMPLE: adb pull /sdcard/ROM.zip
Research adb, adb push, adb pull commands.

Help needed guys :(

My Nexus 6P is stuck in boot loops. I got it back from one of the repair centers and same thing again. It worked for like 5 mins and looping at the Google screen. I can't get into Recovery. I used the Nexus Root Toolkit to do everything possible and nothing. It seems to send the files fine but it will not boot. It just loops no matter what I try to do. Even tried sending TWRP recovery and can't get into that either. Is there any method that can do a complete format and start fresh? what do I do? If I can't fix his I am probably sending back to one of the repair centers again and using my S4 for another 3 weeks. If there is any method to wipe this thing 100% and get a clean install across the board like a computer Hard drive would that even work?

What do you mean by "send the files fine"?
Can you get bootlader? If you can, you can try flashing Nougat IMG.
Enviado de meu Nexus 6P usando Tapatalk

When I use anything on the Nexus Root Toolkit it goes though the process fine with no errors but it won't boot. Even if I try to send the stock recovery or TWRP it still can't boot into recovery. CMD says it went "ok" I tried so many processes of sending any OS to it and nothing. Loops on the Google screen. SO annoying.

LiquidAlloy said:
When I use anything on the Nexus Root Toolkit it goes though the process fine with no errors but it won't boot. Even if I try to send the stock recovery or TWRP it still can't boot into recovery. CMD says it went "ok" I tried so many processes of sending any OS to it and nothing. Loops on the Google screen. SO annoying.
Click to expand...
Click to collapse
Time to learn some fastboot dealings. In this General section, go to the sticky thread for rooting and returning back to stock.
Edit: here's the thread link: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Just please read and take your time, you will be able to fix your device if it's just a software issue.

Very specific bootloop issue

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.

Stuck in bootloop - doesn't reach boot animation, and can't access recovery.

Hi All!
I seem to be stuck in a bootloop on my 6P. I was running the latest Pure Nexus build, and I was having a bit of trouble with some apps, so I decided to reboot into TWRP and wipe the cache. After booting up again, everything seemed normal. The phone was running for a minute or so, and it just shut off. After that, it just keep rebooting. It's not a normal bootloop. I do not reach the animation, I only get to the screen where it says "google" and has the unlocked padlock symbol on the bottom. After that, it starts all over again with the "cannot check for corruption screen."
To be very clear: I can't boot anything at all, including recovery. I have tried flashing multiple versions of TWRP and multiple versions of the stock recovery.
Here is what I've tried so far:
I have flashed back to the latest 7.1.1 release both manually and using the flash all command
I used fastboot to erase the system, cache, boot, and userdata. I ran the commands normally and also with -w.
I've tried to flash an older version of android - 6.0, I think.
Nothing seems to work. I haven't made it to the boot animation once since it shut down.
I also left it on the charger all night just to be sure. The battery was at about 75% when it shut down.
Thanks!

RMA bro.

mtpease said:
Hi All!
I seem to be stuck in a bootloop on my 6P. I was running the latest Pure Nexus build, and I was having a bit of trouble with some apps, so I decided to reboot into TWRP and wipe the cache. After booting up again, everything seemed normal. The phone was running for a minute or so, and it just shut off. After that, it just keep rebooting. It's not a normal bootloop. I do not reach the animation, I only get to the screen where it says "google" and has the unlocked padlock symbol on the bottom. After that, it starts all over again with the "cannot check for corruption screen."
To be very clear: I can't boot anything at all, including recovery. I have tried flashing multiple versions of TWRP and multiple versions of the stock recovery.
Here is what I've tried so far:
I have flashed back to the latest 7.1.1 release both manually and using the flash all command
I used fastboot to erase the system, cache, boot, and userdata. I ran the commands normally and also with -w.
I've tried to flash an older version of android - 6.0, I think.
Nothing seems to work. I haven't made it to the boot animation once since it shut down.
I also left it on the charger all night just to be sure. The battery was at about 75% when it shut down.
Thanks!
Click to expand...
Click to collapse
Can you get to the bootloader?

I'm going to go out on a limb and say if you flash a factory image and get no errors but it's still boned the way you described then RMA if your answer. Your in an every growing boat!!
Sent from my Nexus 6P using XDA-Developers Legacy app

jhs39 said:
Can you get to the bootloader?
Click to expand...
Click to collapse
Yeah, I can get in to the bootloader just fine. I can flash anything I want wit no errors. I just can't boot anything.

CyberpodS2 said:
I'm going to go out on a limb and say if you flash a factory image and get no errors but it's still boned the way you described then RMA if your answer. Your in an every growing boat!!
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah, google agrees with me. They've sent me a new phone. I wish I could have found a solution, though.

mtpease said:
Yeah, google agrees with me. They've sent me a new phone. I wish I could have found a solution, though.
Click to expand...
Click to collapse
Glad your warranty worked for you. Pure Nexus seems to be a recurring factor in several threads. I've never used it myself. Over in this thread, an experienced user ran into a bootloop that would not clear with a fresh wipe and installation with flash-all.bat or even flashing partitions manually. Flash-all.bat finished with no errors but still looping. As a last resort he used Skipsoft's Toolkit to re-install stock and it worked. The toolkit script formats userdata and cache and this appears to be what solved the problem. Interestingly, he was able to reproduce the problem with PN. After installing it, he went into a bootloop again and the toolkit again got him back to stock. So, others that are stuck in a bootloop especially after running or updating PN should try formatting userdata and cache, or use the toolkit.