A lot of people in these threads seem to think Nougat is to blame for the boot loop issues. I know people on custom ROMs have encountered the issue--but if those ROMs are based on Nougat that doesn't disprove the blame on N. I'm curious if anyone running Marshmallow or Marshmallow based ROMs have encountered either boot loop issues or the boot loop of death?
One person in another thread said after they downgraded to MM a week later it looped. Several questions I have would be, does the nougat install actually trip some condition? Was this users problem the same as the nougat loops? With only one example, it's too soon to really know. The 6P seems to be a bootloop magnet anyway so to answer your question, yes bootloop have happened but they can be corrected. The problem with the bootloop of death is even after flashing a full stock image (of any version) it's still boned.
Sent from my Nexus 6 using XDA-Developers Legacy app
CyberpodS2 said:
One person in another thread said after they downgraded to MM a week later it looped. Several questions I have would be, does the nougat install actually trip some condition? Was this users problem the same as the nougat loops? With only one example, it's too soon to really know. The 6P seems to be a bootloop magnet anyway so to answer your question, yes bootloop have happened but they can be corrected. The problem with the bootloop of death is even after flashing a full stock image (of any version) it's still boned.
Click to expand...
Click to collapse
I actually think a lot of bootloops of death could have been corrected but they are on stock phones with the bootloader locked and Allow OEM Unlock not selected in Developer's Menu. I've come across a lot of people in the threads in that situation. The only option then is RMA or paperweight.
jhs39 said:
A lot of people in these threads seem to think Nougat is to blame for the boot loop issues. I know people on custom ROMs have encountered the issue--but if those ROMs are based on Nougat that doesn't disprove the blame on N. I'm curious if anyone running Marshmallow or Marshmallow based ROMs have encountered either boot loop issues or the boot loop of death?
Click to expand...
Click to collapse
If MM users are immune, then wouldn't flashing back to their old rom (or factory MM image) cure the loop? I don't know the answer, but just throwing that out for discussion. I think this has been tried on some affected devices but did not work. How could a loop in N prevent you from going back to MM? I honestly don't know. I'm very surprised that simply restoring a solid backup doesn't get a device right back on track, unless there is some kind of hardware defect causing the loop.
None of my Nexus devices are encrypted, and I'd be interested to know if the initial encryption process can be ruled out as a trigger for the bootloop. I wonder if the use of a no force-encryption modified boot.img to prevent encryption would prevent the looping. There's no way to know unless someone with a bootlooping device has already tried this and failed. Anyway, I'd like to hear from (and offer help to) anyone who would like to take things one step further and possibly find a way out of the looping.
v12xke said:
If MM users are immune, then wouldn't flashing back to their old rom (or factory MM image) cure the loop? I don't know the answer, but just throwing that out for discussion. I think this has been tried on some affected devices but did not work. How could a loop in N prevent you from going back to MM? I honestly don't know. I'm very surprised that simply restoring a solid backup doesn't get a device right back on track, unless there is some kind of hardware defect causing the loop.
None of my Nexus devices are encrypted, and I'd be interested to know if the initial encryption process can be ruled out as a trigger for the bootloop. I wonder if the use of a no force-encryption modified boot.img to prevent encryption would prevent the looping. There's no way to know unless someone with a bootlooping device has already tried this and failed. Anyway, I'd like to hear from (and offer help to) anyone who would like to take things one step further and possibly find a way out of the looping.
Click to expand...
Click to collapse
In my case, I was running pure nexus 7.1.1 , dynamics gapps, elementalx and supersu. Unencrypted. The install was running for a week and then while it was sleeping on my recliner arm I saw it reboot and that was it. No matter what I tried, it never recovered.
Sent from my Nexus 6 using XDA-Developers Legacy app
Ok, thanks for responding. My theory was that during the initial encryption process the phone locked up and started to bootloop. Just to clarify, how were you modifying the boot.img? Just running SU before first boot? I would usually queue up SU and then EX in TWRP and run before first boot. Now I just use FlashFire and it takes care of that on the fly. Glad you are back up and running. Wonder how long you will stay on 6.0.1? ha ha ha
Followed the Heisenberg tutorial to get to the point where I was running unencrypted, rooted with twrp. Then was just flashing like normal.
Sent from my Nexus 6 using XDA-Developers Legacy app
---------- Post added at 05:02 PM ---------- Previous post was at 05:01 PM ----------
No I am not back up yet. RMA was my only option. Waiting for it to return.
Sent from my Nexus 6 using XDA-Developers Legacy app
CyberpodS2 said:
Followed the Heisenberg tutorial to get to the point where I was running unencrypted, rooted with twrp. Then was just flashing like normal.
Click to expand...
Click to collapse
Are you running Marshmallow or Nougat?
It was on nougat 7.1.1 I'm back on my N6 now until the 6P is back from RMA. I'll be installing 6.0.1 on it what it returns unless someone has answers.
Sent from my Nexus 6 using XDA-Developers Legacy app
CyberpodS2 said:
It was on nougat 7.1.1 I'm back on my N6 now until the 6P is back from RMA. I'll be installing 6.0.1 on it what it returns unless someone has answers.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm going to try bumping this thread before starting a new one. Anyone who got into the "bootloop of death" and had to RMA, can you please list what Rom and what circumstance brought on the loop. Maybe we can find a common thread. If this has already been tried, no harm no foul but I'll start. Pure Nexus 7.1.1 with elementalx and super su. It was just sitting there sleeping in front of me when I saw it reboot. Never got it back up again.
Sent from my Nexus 6 using XDA-Developers Legacy app
I managed to get back from bootloop. Dont know if just luck but my phone was totally locked, no OEM Unlock or Root. I did a wipe for no good, flashed latest OTA from stock recovery and nothing. Than I put my phone in my wife's Moto Z charger and wiped everything again. Boom. Booted.
Stock rooted, about a week or so after updating to 7.0, while on a YouTube video phone froze, rebooted and the rest is history. Without being able to get into recovery mode and trying about everything there was to try ,I just finally gave up and had it rma'd.
This happened back on October.
CyberpodS2 said:
I'm going to try bumping this thread before starting a new one. Anyone who got into the "bootloop of death" and had to RMA, can you please list what Rom and what circumstance brought on the loop. Maybe we can find a common thread. If this has already been tried, no harm no foul but I'll start. Pure Nexus 7.1.1 with elementalx and super su. It was just sitting there sleeping in front of me when I saw it reboot. Never got it back up again.
Click to expand...
Click to collapse
Stock rom and flash kernel. I was Just playing around the settings and started to bootloop. Huawei replaced the Logic board in a month here
DU 7.1.1 latest weekly on J vendor. a week after i got the battery replaced! had the flashlight on and went to take a pic. phone froze. booted into recovery once and it just died. Out for repair now. the only saving grace is Huawei ships to and from with Overnight.
Wickidmasshole said:
DU 7.1.1 latest weekly on J vendor. a week after i got the battery replaced! had the flashlight on and went to take a pic. phone froze. booted into recovery once and it just died. Out for repair now. the only saving grace is Huawei ships to and from with Overnight.
Click to expand...
Click to collapse
who replaced your battery, was it an oem battery?
I am on stock unrooted. Was updating permission for Greenify and the bootloop started. I have Wugfresh flashed stock image and still bootloop. I can get into bootloader but not recovery. I have flashed stock image 3 times and everything loads properly but still bootloops. Never seen this before on any phone. A fresh stock flash always brings it back. Not this time. Any help would be great????
flemorj said:
who replaced your battery, was it an oem battery?
Click to expand...
Click to collapse
im under warranty so i sent it back to huawei directly and they put it in. It was marvelous having true 100% and not s h i t t i n g out randomly during they day. But once again they have it bc of this damn bootloop issue.
rndchef said:
I am on stock unrooted. Was updating permission for Greenify and the bootloop started. I have Wugfresh flashed stock image and still bootloop. I can get into bootloader but not recovery. I have flashed stock image 3 times and everything loads properly but still bootloops. Never seen this before on any phone. A fresh stock flash always brings it back. Not this time. Any help would be great????
Click to expand...
Click to collapse
When you say you cannot get into stock recovery, exactly what do you mean? Do you not see the dead Android guy? Have you tried formatting recovery and re-installing stock recovery or even TWRP? I'd focus on getting a working recovery before moving forward. Then, in NRT>> advanced utilities, try formatting cache, system, and userdata and then use the toolkit again to "flash stock + unroot" , using the soft-brick status option.
If a phone has the true boot loop of death, boot loader is the only screen you can do anything in. Oh besides the barcode screen. There is no recovery available, stock or twrp. Also any flashing with fastboot goes without error but fixes nothing.
Sent from my Nexus 6 using XDA-Developers Legacy app
CyberpodS2 said:
If a phone has the true boot loop of death, boot loader is the only screen you can do anything in. Oh besides the barcode screen. There is no recovery available, stock or twrp. Also any flashing with fastboot goes without error but fixes nothing.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is unfortunately correct. I spent endless time trying to push a stock recovery file and still no access to recovery. Tried everything in the NRT arsenal and nothing. Huawei is replacing it after 1 year. Since it takes 2 weeks, I am getting the Mate 9 tomorrow and selling the 6P. Been a good year but time to move on.
Related
For everyone interesting into upgrading to Android 7 be warned that are some issues going around right now and no one really knows what is causing the problems or what the fix is. So I was running the latest Pure Nexus rom and upgraded to Android 7 using the OTA file and the boot.img provided. Everything went fine and the system boot correctly. Well I decided to flash Pure Nexus back and the system was stuck in a boot loop between the white google logo and the "The system can't be checked for corruption" screen (unlocked boot loader). Well the good man Heisenberg got involved and recommend his full system stock restore guide (without locking the boot loader; don't do it or you will be completely out of luck). I used his guide and flashed 6.0.0 (MDA89D) and also 6.0.1 (MTC20F). The phone continued to boot loop and never boot. I was still able to boot into TWRP, so I tried a manual flash of Pure Nexus and MTC20F Vendor, no luck... Then I tried reflashing the Android 7 OTA update and boot.img, still a boot loop... There was an earlier thread about this issue, but I felt led to make sure this news and warning gets out!!! I ended up contacting google and project fi and I am getting a replacement phone.
While this issue seems to be rare I want to list my conditions in hoping preventing the issue for you!
- I was on MTC20F Vendor (with Pure Nexus)
- I flashed the Android 7 OTA update from the latest Pure Nexus build
- I did a semi dirty flash (could be root of problems) (I did this due to a recommendation, that was meant for a stock android 6 to 7 upgrade)
- The root of the issue could be going from a custom rom to the stock Android 7
- My system was rebooting and restating just fine with Android 7
- I wiped my system and flashed Pure Nexus back and the issues started
- This issue for now has no fix; Heisenberg (really thanks man) was a big help but didn't know what to do about it
Hey anyone who sees and reads this; would super appreciate answering the poll so we as a community can collect data about this problem to help prevent it in the future. Currently there is no fix for this weird semi(can access recovery)/hard(never boots into system) brick
Thank you!
Sounds like you should have just flashed stock before flashing the N OTA.
dratsablive said:
Sounds like you should have just flashed stock before flashing the N OTA.
Click to expand...
Click to collapse
same thing happened to me, i cant return to stock or 7 or backup, nothing
An important warning to all upgrading to Android 7 right now!
I currently find myself stuck on the boot animation (the colored circles) after trying to flash 7 then going back to Pure Nexus. I did a full data and system wipe before trying to install 7, but it still hung on the boot animation. Now after restoring my nandroid and reflashing Pure Nexus I'm still stuck on the boot animation.
Edit: Whew, reflashing Pure Nexus then restoring just the vendor image seem to have gotten me back to M.
Sent from my iPad using Tapatalk
I am stuck like this as well. I can't figure out how to fix this.
---------- Post added at 11:09 AM ---------- Previous post was at 11:08 AM ----------
TheBiles said:
I currently find myself stuck on the boot animation (the colored circles) after trying to flash 7 then going back to Pure Nexus. I did a full data and system wipe before trying to install 7, but it still hung on the boot animation. Now after restoring my nandroid and reflashing Pure Nexus I'm still stuck on the boot animation.
Edit: Whew, reflashing Pure Nexus then restoring just the vendor image seem to have gotten me back to M.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
My computer is not even detecting my phone with ADB... You know anything I might not?
UPDATE: Just had to unplug and replug my phone when in Recovery/Apply UPdate from ADB
stuck in bootloop as well....having google rma my device...flashed the aosp build of nougat just to test it out, then restored my backup of official noougat and got the bootloop...no clue what else to do in this case
I updated to 7 and then downgraded to 6.01. Boot loop city. I've spent 10 hours trying everything I could to fix it.
Hey guys, my nexus 6p (no root, but bootloader is unlocked) is stuck in a bootloop, where it doesnt go past the white google logo. I have flashed factory images 3+ times but it doesnt seem to be doing anything. Does anybody have any possible ideas on what to do?? I am on 6.0.1 MTC20F. Thanks.
Are the fastboot commands completing? Are they throwing any errors? How long does each step take? Can you try the latest 7.0.0 factory image and see if that works?
Honestly if you've flashed a factory image and it still won't boot, you may have a corrupted emmc and in that case contact Google for an RMA.
Or possibly borked your EFS if u tried restoring a backup with older TWRP
Sent from my Nexus 6P using Tapatalk
AndroidReider said:
I am on 6.0.1 MTC20F. Thanks.
Click to expand...
Click to collapse
It's known by now, that after the Nougat OTA phones started to die a horrible death, and some, including me, suspected it was the NPDxxx kernel. But if it died on Marshmallow, maybe it's the NAND dying.
Here's the other thread:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
RoyJ said:
Are the fastboot commands completing? Are they throwing any errors? How long does each step take? Can you try the latest 7.0.0 factory image and see if that works?
Honestly if you've flashed a factory image and it still won't boot, you may have a corrupted emmc and in that case contact Google for an RMA.
Click to expand...
Click to collapse
Most of the time it works. Only sometimes it doesnt recognize my device is plugged in and a lot of the time went flashing the system it fails. It is all relatively quick but the system usually takes 2+ minutes. I can get into the bootloader and I am definitely flashing the stock images and its working. It just keeps getting stuck in a bootloop.
Forced to get an iPhone tomorrow but I would love to revive my 6p within the 14 day return period if possible.
Nexus 6p running PureNexus suddenly shut off and started boot looping. I can only get into the bootloader, no recovery or hard factory reset possible.
I manually flashed the newest factory image as well as an older Marshmallow one without any luck (./flash-all.sh gave me a space allocation error, so I did each step manually). Flashing the latest TWRP also does not work and I'm out of ideas. I even tried NRT on an old Windows laptop I had laying around without any luck.
Is there a way to check whether my eMMC has **** the bed?
Thanks for any help guys!
doron07 said:
Forced to get an iPhone tomorrow but I would love to revive my 6p within the 14 day return period if possible.
Nexus 6p running PureNexus suddenly shut off and started boot looping. I can only get into the bootloader, no recovery or hard factory reset possible.
I manually flashed the newest factory image as well as an older Marshmallow one without any luck (./flash-all.sh gave me a space allocation error, so I did each step manually). Flashing the latest TWRP also does not work and I'm out of ideas. I even tried NRT on an old Windows laptop I had laying around without any luck.
Is there a way to check whether my eMMC has **** the bed?
Thanks for any help guys!
Click to expand...
Click to collapse
Have you had a look at this thread? Hope it helps..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page1
BIGSAMDA1ST said:
Have you had a look at this thread? Hope it helps..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page1
Click to expand...
Click to collapse
Thank you, I have. The issue is that after installing any factory image, regardless of version, my phone will continue to boot loop and refuse to boot into recovery.
doron07 said:
Thank you, I have. The issue is that after installing any factory image, regardless of version, my phone will continue to boot loop and refuse to boot into recovery.
Click to expand...
Click to collapse
That was basically what had happened to mine a few weeks ago. I tried everything possible with no luck. Just gave up, flashed stock images, relocked boot loader and off to Huawei it went. About two weeks later I had a replacement.
BIGSAMDA1ST said:
Have you had a look at this thread? Hope it helps..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page1
Click to expand...
Click to collapse
BIGSAMDA1ST said:
That was basically what had happened to mine a few weeks ago. I tried everything possible with no luck. Just gave up, flashed stock images, relocked boot loader and off to Huawei it went. About two weeks later I had a replacement.
Click to expand...
Click to collapse
I spoke to both google and huawei...was basically told to F off and find some third party repair store.
Wow should of just bent the phone in half and said you sat on it need a replacement. I had some issue switching to pure Nexus but I fixed it by doing fastboot boot twrp.img instead of flashing then from there deleted everything then followed there flashing making sure not to flash user data just partition it.
Sent from my Nexus 6P using Tapatalk
I went through the same thing on the same ROM, luckily though I had a week of warranty left and got its main board replaced by FutureTel. Sorry for your loss man, hope you get this resolved somehow..
Same issue, just sent it for replacement since it was hard bricked. It's an issue with rooting in 7.0 and above. I'd gladly donate to have someone look into it and see what the issue is with rooting and 7.0
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.
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.