Related
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium
irrelephant said:
wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I'm on my 3rd one going strong :/ with bad screen and chip but I call every once in awhile to see if I can get a mt4gs. Good luck teejay! As for none booting just run pd15img and do a battery pull while it's updating until it won't turn on anymore
Sent from my HTC Glacier using xda premium
This is one of the reasons I had to jump ship on this phone. Was scared it might take a **** on any given time.
But I always love the MT4G, hopefully TJ can get something viable from TMO.
TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?
saranhai said:
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?
Click to expand...
Click to collapse
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.
TeeJay3800 said:
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.
Click to expand...
Click to collapse
yeah, worth a shot lol
but well, like i said before, unless you try the PD15IMG file and it gives you Fail-PUs, you don't know if it's dead eMMC. but if your phone still works, then i doubt the chip died...
Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).
I heard awhile back that there was a way to enter some commands through terminal emulator to the hboot partition that will brick the phone. dont know which partition it is though.
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Had the exact same thing happen to me yesterday.
Mine went belly-up recently too. No Failed-PU message but it would not flash or boot properly. Powered it on and got a 7 to 8 vibrates in a row on the splash screen before it powered itself off. Recovery (4EXT) failed to restore a nandroid (couldn't mount data) and shortly thereafter couldn't boot recovery. Flashing recovery (and original splash) through ADB fastboot claimed to be successful but didn't actually work. Flashing PD15IMG from bootloader also failed, shortly into it. T-Mobile sent a warranty replacement MT4G (it was just under 1 year). Bad screen and eMMC, but I'll live with it. Will find out if they notice the engineering bootloader and custom splash...
Jack_R1 said:
Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).
Click to expand...
Click to collapse
my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem. I was hesitant doing that initially thinking that would aggravate the problem and make the phone unusable. The question now is what caused it. Last week I flashed the newest radio. I knew that in some cases a cache wipe was necessary after flashing a radio to prevent freezing at the slash screen, but my phone booted normally after the radio flash and worked fine for days after. This is the first case I've heard of where I radio flash caused cache errors in recovery. In any case, it all seems fine now so thanks all for the kind words and input.
If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed
Jack_R1 said:
If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed
Click to expand...
Click to collapse
I only flash radios via fastboot commands from the computer, but I think you're right about something not unmounting or a CWM bug. There were something like half a dozen CWM bug-fix releases after the original version 5, so it wouldn't be too surprising. And yeah your last statement is exactly correct!
TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.
jr_718 said:
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.
Click to expand...
Click to collapse
Thanks, but did you read the rest of the thread? No replacement for me, at least not yet.
TeeJay3800 said:
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem.
Click to expand...
Click to collapse
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too
my2sense said:
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too
Click to expand...
Click to collapse
I hadn't had to either. There's definitely something different about this latest radio.
Help me XDA, you're my only hope...
First, background: I bought my Nexus 4 over the internet, because it was never officially released in Belgium. I had to have the screen replaced, and let a 3rth party do it. Glass damage isn't covered by the warranty and it would mean sending my phone by international mail if i used the official warranty people. They told me that the also had to replace the proximity sensor.
My phone worked perfectly afterwards. Until I tried to install the automatic upgrade to 4.3.
First it stopped at the X-logo screen and became very hot. I contacted play support and did all the things they advised (including a factory reset, rebooting in safe mode), none of it works. I found someone with the same problem who managed to get past the X-screen by flashing back the 4.2.2 radio version. And that worked: the phone booted and the update started.
However, since that moment I got a lot of problems:
- random shutdowns
- random locking of the SIM card
- phone not starting unless plugged in charger.
Worst of all, reflashing stock images for 4.2 and 4.2.2 or AOKP does nothing to solve these problems. I also tried a new SIM card, and still nothing.
I'm at my wit's end now. Could there be a driver issue? Any other things I can try?
TIA
Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Click to expand...
Click to collapse
any suggestions for a good kernel that can run stock android?
If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.
BobWalker said:
If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.
Click to expand...
Click to collapse
Well, I tried again. (For the 6th time this month) No different as before: it's been stuck on the X screen for 20 minutes now and getting warmer.
EDIT: I finally managed to get into the recovery menu. No idea why it wouldn't let me use volume up + power...
As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?
Joenr76 said:
As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?
Click to expand...
Click to collapse
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Click to expand...
Click to collapse
I never did that before: do I flash the kernel first or the Rom first? Are there any guides?
EDIT: I just read that Paranoid Android comes with the halfbreed kernel included. Is that the one you linked too?
Before jumping into the kernel thing (also because i wanted to be able to work with a device that can actually boot), I reinstalled the 4.2.2 factory image. It took about 5 minutes for the first shutdown to happen. *sigh*
And without plugging it in, it goes into a boot loop (going to x screen for a while, then restarting.) When I plug it in, it starts immediately, but shows the battery as empty. It was 63% when it shut itself down.
It's a clean install, I just don't understand...
Okay so, I'm assuming you have a custom recovery like TWRP. Open it and flash the newest boot loader and radio. Then flash Paranoid Android and GApps. Then try flashing Faux kernel and clearing cache/dalvik. If you still have problems, then I have no idea
Sent from my Nexus 4 using xda premium
Open up your phone to see the battery is securely checked and to see if all the components are okay. Then look do a full wipe of cache,dalvik,system,data,and sd (internal storage). Then use wugs toolkit to a upgrade on a clean flash. Double check to make sure you wipe everything!
Sent from my Nexus 4 using Tapatalk 4
TheNerd:] said:
Open up your phone to see the battery is securely checked and to see if all the components are okay.
Click to expand...
Click to collapse
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...
Joenr76 said:
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...
Click to expand...
Click to collapse
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.
tykate said:
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.
Click to expand...
Click to collapse
Tried that before. I did some research and I guess this is relevant: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/ Especially since I ordered my Nexus from the Netherlands.
I'll have to wait until that bug gets fixed until I can upgrade my radio.
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.
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.
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.