Database Users

Stuck on Google screen after updating to 4.2

I have an unlocked and rooted stock Nexus 7 with the stock rom. I Just performed an OTA update to Android 4.2 and now the Nexus is stuck on the Google splash screen with the unlocked padlock symbol. I have tried booting to recovery with the Wugs Rootkit and it shows a an android with a red warning triangle above it. Please can anyone help me to fix this.
I have a PC with Wugs Toolkit 1.5.5 and I have the Google Nexus 7 Root Toolkit 3.2.0.
Please anyone know how to the fix this as I have no idea.

Exact same problem
randomvector said:
I have an unlocked and rooted stock Nexus 7 with the stock rom. I Just performed an OTA update to Android 4.2 and now the Nexus is stuck on the Google splash screen with the unlocked padlock symbol. I have tried booting to recovery with the Wugs Rootkit and it shows a an android with a red warning triangle above it. Please can anyone help me to fix this.
I have a PC with Wugs Toolkit 1.5.5 and I have the Google Nexus 7 Root Toolkit 3.2.0.
Please anyone know how to the fix this as I have no idea.
Click to expand...
Click to collapse
I have the exact same problem. For the record I had the very latest version of SuperSU Pro that got updated today (0.98, I think) with survival mode activated. Don't know if that's the cause of the problem or just the fact that it's rooted.

Dang. Same thing here. And I also just installed the new SuperSU before applying the OTA.

Try the two posts right above this one.
I know the thread Stuck on Google Screen has some solutions that may help.
Sent from my Nexus 7
Clean ROM 2.0 - leankernel .5

ezas said:
Try the two posts right above this one.
I know the thread Stuck on Google Screen has some solutions that may help.
Click to expand...
Click to collapse
Well, since you replied, this thread is now at the top of the stack, so there's nothing above it. I'm getting old and blind, but I don't see a thread and can't find one with search called anything like "Stuck on Google Screen". Except this one, of course.
Edit...Eh, nevermind. I just flashed the full 4.2 from Google instead of mess with this any more. Restoring apps now.

CSX321 said:
Dang. Same thing here. And I also just installed the new SuperSU before applying the OTA.
Click to expand...
Click to collapse
I did exacty the same thing the app had already updated before I could do the Android 4.2 update. I fix the isue. I had to do restore to stock Rom 4.1.1 then update to 4.1.2 and then to 4.2 then recovered some of the stuff I lost with an old Titanium Backup I did a few weeks ago.

Recovered mine
Hi all,
(I'm the second poster)
I managed to get my Nexus 7 back, although losing all the data, which I think cannot be avoided.
Here is what I did, for dummies:
- Reboot into fastbood mode. For this, hold the power, volume up and volume down button.
- Use the Nexus 7 Toolkit (I donated to get the latest version) or the Nexus Root Toolkit (which I guess works as well) and flash the google factory stock rom.
- If using the Nexus 7 toolkit, at the beginning I selected that I had Android 4.2 installed.
- After flashing, my tablet was as if just taken out from the box (but still unlocked). All my old apps got downloaded automatically, although the settings / game progress were not saved. Fortunately I have some Titanium Backup backups from a little while ago.
- After all apps got downloaded, I put the tablet in fastboot mode again, and I rooted it with the Nexus 7 toolkit via option 4 and then sub-option 2.
Sorry if I said some obvious stuff, but I am not an expert, and wanted to help other non-experts
Good luck to everyone.

aran80 said:
Hi all,
(I'm the second poster)
I managed to get my Nexus 7 back, although losing all the data, which I think cannot be avoided.
Here is what I did, for dummies:
- Reboot into fastbood mode. For this, hold the power, volume up and volume down button.
- Use the Nexus 7 Toolkit (I donated to get the latest version) or the Nexus Root Toolkit (which I guess works as well) and flash the google factory stock rom.
- If using the Nexus 7 toolkit, at the beginning I selected that I had Android 4.2 installed.
- After flashing, my tablet was as if just taken out from the box (but still unlocked). All my old apps got downloaded automatically, although the settings / game progress were not saved. Fortunately I have some Titanium Backup backups from a little while ago.
- After all apps got downloaded, I put the tablet in fastboot mode again, and I rooted it with the Nexus 7 toolkit via option 4 and then sub-option 2.
Sorry if I said some obvious stuff, but I am not an expert, and wanted to help other non-experts
Good luck to everyone.
Click to expand...
Click to collapse
Can you advise which toolkit you used, was it Wug's Toolkit? Can you possibly provide the link?
Thanks,
JBIRD
---------- Post added at 09:49 AM ---------- Previous post was at 09:44 AM ----------
aran80 said:
I have the exact same problem. For the record I had the very latest version of SuperSU Pro that got updated today (0.98, I think) with survival mode activated. Don't know if that's the cause of the problem or just the fact that it's rooted.
Click to expand...
Click to collapse
I installed the latest SuperSU version but have not updated yet, what do you recommend I do, remove the SuperSU software or not uprgade at all at this time?
Thanks,
JBIRD

jbird92113 said:
Can you advise which toolkit you used, was it Wug's Toolkit? Can you possibly provide the link?
Thanks,
JBIRD
Click to expand...
Click to collapse
Before doing all that, plug your Nexus in and make sure USB Debugging is enabled, and also its set to camera mode, not MTP.
Goto command prompt, and use:
adb reboot recovery
You will then see the Android with a red triangle, at the same time quickly tap power and volume up, you'll then be taken to a blue screen.
Choose wipe cache.
Also you could factory reset?
Then reboot
Hope this helps.

Nexus 7 toolkit
jbird92113 said:
Can you advise which toolkit you used, was it Wug's Toolkit? Can you possibly provide the link?
Thanks,
JBIRD
Click to expand...
Click to collapse
Sure First I thought about using Wug's Toolkit, but I saw it was not updated yet to handle Android 4.2 stuff, whereas the Nexus 7 Toolkit was.
You can download it from http://forum.xda-developers.com/showthread.php?t=1809195, but only version 3.2.0 which does not have Android 4.2 stuff. To get the latest version (3.8.2, updated yesterday 14 november), you have to donate and wait until the developer sends you a key. I donated 5 pounds but the developer says any amount is OK. I got my key 1-2h after donating.

aran80 said:
Sure First I thought about using Wug's Toolkit, but I saw it was not updated yet to handle Android 4.2 stuff, whereas the Nexus 7 Toolkit was.
You can download it from http://forum.xda-developers.com/showthread.php?t=1809195, but only version 3.2.0 which does not have Android 4.2 stuff. To get the latest version (3.8.2, updated yesterday 14 november), you have to donate and wait until the developer sends you a key. I donated 5 pounds but the developer says any amount is OK. I got my key 1-2h after donating.
Click to expand...
Click to collapse
Thanks. Do you recommend that I remove SuperSU prior to running the OTA or even for that matter just hold off on upgrading for now?

jbird92113 said:
Thanks. Do you recommend that I remove SuperSU prior to running the OTA or even for that matter just hold off on upgrading for now?
Click to expand...
Click to collapse
Well, I can only tell you the situation that I had before installing the 4.2 OTA:
- Unlocked
- Stock Android 4.1.2
- Rooted with SuperSu 0.98 and survival mode activated
Maybe the problem was to be rooted; or to have SuperSU; or to have specifically SuperSU 0.98; or to have survival mode active... I don't know.
If you want to be fairly sure to not have any problems, I would uninstall SuperSU. There is an option to do a full unroot inside SuperSU itself. Maybe before that to be even safer, you could even uninstall all the root-requiring applications?
Then, reboot, apply the OTA, and cross your fingers
Then you can root again with Nexus 7 toolkit, it was done very fast, and you will have supersu again.
Rooting or unrooting should not wipe your data.
From now on I think I will not have the survival mode activated before an OTA, just in case, as I now know how to unroot / root quite fast.
Good luck

randomvector said:
I had to do restore to stock Rom 4.1.1 then update to 4.1.2 and then to 4.2
Click to expand...
Click to collapse
I didn't bother with reverting to stock. I just booted into fastboot mode, which I was still able to do, and installed the factory 4.2 image from https://developers.google.com/android/nexus/images. I develop apps, so I already had a full development environment and the needed tools installed.

aran80 said:
Well, I can only tell you the situation that I had before installing the 4.2 OTA:
- Unlocked
- Stock Android 4.1.2
- Rooted with SuperSu 0.98 and survival mode activated
Maybe the problem was to be rooted; or to have SuperSU; or to have specifically SuperSU 0.98; or to have survival mode active... I don't know.
If you want to be fairly sure to not have any problems, I would uninstall SuperSU. There is an option to do a full unroot inside SuperSU itself. Maybe before that to be even safer, you could even uninstall all the root-requiring applications?
Then, reboot, apply the OTA, and cross your fingers
Then you can root again with Nexus 7 toolkit, it was done very fast, and you will have supersu again.
Rooting or unrooting should not wipe your data.
From now on I think I will not have the survival mode activated before an OTA, just in case, as I now know how to unroot / root quite fast.
Good luck
Click to expand...
Click to collapse
Thanks. I didn't purchase the pro version so I don't have the survival mode feature . I may just wait and see if there are any other folks running into the same issue. Thanks again

Has anyone figured this out yet? I'm also stuck on the Google boot screen after installing the 4.2 OTA on my stock, rooted Nexus 7, and I've tried the following:
- Wiped cache.
- Re-flashed the 4.2 OTA (build JOP40C) from stock recovery via adb.
- Flashed TWRP (via Wug's Root Toolkit) and renamed Superuser.apk, assuming that was the issue.
- Re-flashed the 4.2 OTA (build JOP40C) from custom recovery via WugFresh's Nexus Root Toolkit v1.5.5.
Nothing worked -- it's still locked up on the Google screen at boot. How do I fix this (ideally without wiping my user data)?

rcs408 said:
Has anyone figured this out yet? I'm also stuck on the Google boot screen after installing the 4.2 OTA on my stock, rooted Nexus 7, and I've tried the following:
- Wiped cache.
- Re-flashed the 4.2 OTA (build JOP40C) from stock recovery via adb.
- Flashed TWRP (via Wug's Root Toolkit) and renamed Superuser.apk, assuming that was the issue.
- Re-flashed the 4.2 OTA (build JOP40C) from custom recovery via WugFresh's Nexus Root Toolkit v1.5.5.
Nothing worked -- it's still locked up on the Google screen at boot. How do I fix this (ideally without wiping my user data)?
Click to expand...
Click to collapse
Same here, didn't try all you did.
I'll try to descibe what I did to see similarities,
I had my N7, Rooted 4.1.2, unlocking via face-lock, , I has just installed last update from super su, had root protection enabled,
I'm willing to pay 2.7 Bitcoins, (~31$) to someone helping me fix it without reinstalling everything.

Just an update on my situation: Since adb still worked from the Google boot screen, I managed to batch pull my TitaniumBackup folder down onto my PC. I went ahead and flashed back to stock (good guide here, for anyone who needs it: http://forum.xda-developers.com/showthread.php?t=1781250), updated, re-flashed SuperSU and Busybox, and restored all my backups without any issues.
First time I've actually had to do that, but I'm happy to see that my daily TiBu backup schedule paid off, and I'll probably feel much more confident repeating the process in the future.
Anyway, I'm assuming the issue had something to do with the SuperSU apk, as others here have guessed. I, too, had SuperSU's survival mode enabled (which I've disabled) -- and I also had OTA RootKeeper installed (which I've now ditched), In the future, I'll probably just err on the side of caution and fully unroot before applying an OTA; it's easy enough to just re-root, rather than rolling the dice with any sort of survival mode.
And if SuperSU ISN'T the issue, I'd sure like to know what is!

Hi guys, my girlfriend updated to 4.2 yesterday, and it was fine up until her battery died. so she charged it and then tried to turn it on, and it was in an endless boot loop first starting with the google logo coming up, then itll go kinda staticy and go to the X (and sorry for my future description) but then the screen will look like its in the matrix? If that makes sense. I can provide a picture if needed, but then itll just reboot and do the same thing over and over again. We went to Virgin and called samsung and they both said the same thing that the system would have to be recovered. Virgin, however directed me over to use Odin. I've never really used Odin before and am not sure what to do, so would someone mind helping me out with this issue? i've tried going into recovery menu as well, but it doesn't work. I really appreciate the answer in advance!!!!! Her phone is the galaxy nexus.

AdmiralAqbar said:
Hi guys, my girlfriend updated to 4.2 yesterday, and it was fine up until her battery died. so she charged it and then tried to turn it on, and it was in an endless boot loop first starting with the google logo coming up, then itll go kinda staticy and go to the X (and sorry for my future description) but then the screen will look like its in the matrix? If that makes sense. I can provide a picture if needed, but then itll just reboot and do the same thing over and over again. We went to Virgin and called samsung and they both said the same thing that the system would have to be recovered. Virgin, however directed me over to use Odin. I've never really used Odin before and am not sure what to do, so would someone mind helping me out with this issue? i've tried going into recovery menu as well, but it doesn't work. I really appreciate the answer in advance!!!!!
Click to expand...
Click to collapse
AdmiralAqbar, if you need to return your Nexus 7 to stock, follow this guide: http://forum.xda-developers.com/showthread.php?t=1781250
You could also boot into recovery (hold Volume Up and Down keys while you power on, then select Recovery from the list), and then try to return to stock from there (in Recovery, press Power and Volume Up at the same time, and there should be an option in the resulting list).

rcs408 said:
AdmiralAqbar, if you need to return your Nexus 7 to stock, follow this guide: http://forum.xda-developers.com/showthread.php?t=1781250
You could also boot into recovery (hold Volume Up and Down keys while you power on, then select Recovery from the list), and then try to return to stock from there (in Recovery, press Power and Volume Up at the same time, and there should be an option in the resulting list).
Click to expand...
Click to collapse
I didn't even realize this was a nexus 7 thread i'm sorry! I just noticed the same problem so i clicked into this thread haha, she has the Galaxy Nexus i9250. And i tried that, and then it'd just reboot. I'm assuming the recovery menu is corrupt maybe? Would i be able to follow the same steps in that guide for her phone?

[Q] Failed OTA update help?

I just got the OTA update to Android 4.4, and being eager to get it installed, hit the install button right away. I told a few people I was going to be a few minutes while installing the update... and tapped the button.
That was three hours ago, roughly.
I'm on a rooted nexus 4 with CWM Touch edition installed as a recovery. I don't know exactly what version right now but it was the latest when I installed it a few months ago.
The install launched CWM, and I waited as the loading bar filled. Right at the end it gave an error message - in a panic I didn't take note of what it was, hit the onscreen buttons and went through a window telling me I might have lost SU permissions - which I told it to fix. The startup animation (with four dots, the new 4.4 animation I guess?) started... and continued for more than five minutes.
I was still panicking and instantly launched back into CWM, downloaded a (I think correct, checked it multiple times, as on does...) update zip from the web, and flashed it via adb sideload. This gave me an "Error 7" and a failed install. I tried again, same result. Then gave up and hit the restart button in the hope that one of the attempts had indeed worked...
I now have a Nexus 4 sitting on my desk playing a nice dotty animation, and it's been doing that for fifteen minutes as of now. I'm intending to leave it as such hoping that it will actually turn on and it's just having a very long boot.
So, the question. Anyone have any ideas how to save my Nexus?
I'd rather like to end up with the data on the device intact (stupidly did not back up before installing and can't get any files off it until an install works) and possibly with Android KitKat running on it, as was the original aim of tonight, but if neither are possible, I'd at least like to end up with a functioning phone... just with any stock rom.
Thanks in advance.
P.S. I'm not new to flashing ROMs manually - my last phone was a ZTE Blade which never ran any ROM well, so I must have flashed on that phone at least ten times, including via ADB.

Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD

totally-not-me said:
Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD
Click to expand...
Click to collapse
Your post saved me from a complete wipe and reinstall, so thank you for sharing your fix. I had a very similar issue but my Status 7 appeared to be because of my previous root and the new install not being able change the permissions on some /system files.
Now I just need to re-enable root via the NRT.

at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk

dethrat said:
at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.

I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.

thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
Not blaming you xda has almost become useless in terms of finding real info in the past week. Bombardment of repeated posts about 4.4
Sent from my Nexus 4 using Tapatalk

Lokitez said:
I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.
Click to expand...
Click to collapse
Sideloading is only for flashable zip packages, not official factory images that required using fastboot. Use the guide links in my signature for instruction to flash factory image.
Or you can use sideload to flash flashable stock roms: http://forum.xda-developers.com/showthread.php?t=2527806
Unless your wife is really into flashing, I suggest just leaving it everything stock.

thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user

RickyBO89 said:
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user
Click to expand...
Click to collapse
It will softbrick the device, or atleast fail. I don't even have to try CWM, but with TWRP, if I make any changes to the /system partition it failed. I suggest you just flash a stock 4.4 rom: http://forum.xda-developers.com/showthread.php?t=2010887

[Q] Nexus 7 (2012) forced to bootloop due to 4.4.2

This is the third time trying to write this without my computer blowing up, so I'll be short. After five months of not using my N7 for certain reasons, I came home to update it to Kitkat as I was unable to do so before I came out. The OTA downloaded fine and, like updates before, I clicked install. Sadly, this time the installation did not work correctly, and I stupidly forgot to grab the error code that was thrown. After the failed installation, it went into a bootloop using the new boot screen, and with the boot screen graphic glitch I've seen other people complain about. I can get into Recovery Mode easy enough, which is running ClockworkMod Recovery v6.0.2.3. The bootloader is also unlocked. I've tried to do a factory reset from CWMR, but it hasn't helped.
I've gotten quite rusty with my skills in this work (as if I had any in the first place), so I thought coming here would be a good idea. Any thoughts on how to get Kitkat on working and proper?

nexus root toolkit
Download nexus root toolkit or unified android toolkit to your PC .Install drivers etc and do a factory restore using the KitKat factory image or the restore options in the toolkit

mrchaos429 said:
Download nexus root toolkit or unified android toolkit to your PC .Install drivers etc and do a factory restore using the KitKat factory image or the restore options in the toolkit
Click to expand...
Click to collapse
Thank you so much! Took a few minutes to figure it out, but my N7 is back up and running!

Nexus 7 (2012) WiFi Soft-bricked

Hi,
I have an old Nexus 7 (grouper on completely stock KTU84P, unrooted) that I gave up on a long time ago and recently found it again. I charged it up and the Google logo came up. And then the 'Start' in green with a arrow around it appeared. It was stuck. I could use the volume buttons to power off or enter recovery but that was it. Once in recovery, I tried wiping cache but that got stuck on 'Formatting /cache'.
Now, I do remember it got very sluggish when I last used it a long time ago to a point that it just used to freeze up on me every few minutes. Maybe, i hope not, but maybe it's got something to do with the notorious flash emmc(or whatever it was called) that this device has. If not, I'd love to be able to use it again in any way possible.
TIA.

geforceonline said:
Hi,
I have an old Nexus 7 (on completely stock, unrooted) that I gave up on a long time ago and recently found it again. I charged it up and the Google logo came up. And then the 'Start' in green with a arrow around it appeared. It was stuck. I could use the volume buttons to power off or enter recovery but that was it. Once in recovery, I tried wiping cache but that got stuck on 'Formatting /cache'.
Now, I do remember it got very sluggish when I last used it a long time ago to a point that it just used to freeze up on me every few minutes. Maybe, i hope not, but maybe it's got something to do with the notorious flash emmc(or whatever it was called) that this device has. If not, I'd love to be able to use it again in any way possible.
TIA.
Click to expand...
Click to collapse
Is it possible to connect via USB?
If so, then try a clean flash.

Boldie90 said:
Is it possible to connect via USB?
If so, then try a clean flash.
Click to expand...
Click to collapse
It is possible. I tried sideloading a stock OTA package (using just adb) called '4939a9ff6d10c495beaed26ac96228246f724272 signed-nakasi-LRX21P-from-KTU84P 4939a9ff' but that failed. Then I tried the Nexus Root Toolkit's flash stock feature. It connects and goes well until it reboots to unlock the bootloader. The display doesn't turn on but the computer recognizes a new device called 'APX' with hardware id 'USB\VID_0955&PID_7330&REV_0103'. I've tried booting it into custom recovery using NRT but that didn't work either.
According to the current '3e' stock recovery I remembered that it used to run KTU84P (4.4 Kitkat) and never ran Lollipop which it seems caused some trouble too.

Please try Wugs Toolkit.
That is an easy program to do all kind of repairs.
It never failed me.

Boldie90 said:
Please try Wugs Toolkit.
That is an easy program to do all kind of repairs.
It never failed me.
Click to expand...
Click to collapse
'Nexus Root Toolkit' or NRT IS Wugs toolkit.

Anyone?

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.