I updated my Nexus 6p 32 GB via OTA MHC19I but after updating it the phone got stuck in a bootloop. I've already tried factory reseting the phone through recovery. After that didn't work I tried flashing the factory image using flash-all.sh and the manual procedure in Heisenberg's.
I haven't rooted or flashed a custom ROM on the phone. I wonder if there could anything that could be done or do I have to return it? I bought it last January btw.
Even if you return the phone then they will just flash the new software to it and will give it back. I think you should install yourself. Or else you have to wait until you get back the device from Google or huwaei
Sent from my Nexus 6P using Tapatalk
slashred said:
I updated my Nexus 6p 32 GB via OTA MHC19I but after updating it the phone got stuck in a bootloop. I've already tried factory reseting the phone through recovery. After that didn't work I tried flashing the factory image using flash-all.sh and the manual procedure in Heisenberg's.
I haven't rooted or flashed a custom ROM on the phone. I wonder if there could anything that could be done or do I have to return it? I bought it last January btw.
Click to expand...
Click to collapse
What factory image did you use and did it work or are you still bootlooping?
I used the factory image from Android Website filename: angler-mhc19i-factory-fb2128bf. I also tried N preview npc56w, mmb29v. All of those puts the device in a bootloop.
slashred said:
I used the factory image from Android Website filename: angler-mhc19i-factory-fb2128bf. I also tried N preview npc56w, mmb29v. All of those puts the device in a bootloop.
Click to expand...
Click to collapse
What process/sequence are you following to flash factory image?
DJBhardwaj said:
What process/sequence are you following to flash factory image?
Click to expand...
Click to collapse
I tried the procedure from https://developers.google.com/android/nexus/images#instructions which uses the flash-all.sh and I also tried the instructions from heisenberg's step #11.
slashred said:
I tried the procedure from https://developers.google.com/android/nexus/images#instructions which uses the flash-all.sh and I also tried the instructions from heisenberg's step #11.
Click to expand...
Click to collapse
Try the steps from here: http://www.droidorigin.com/install-android-n-developer-preview/
Completely manual. And let me know if it works.
DJBhardwaj said:
Try the steps from here: http://www.droidorigin.com/install-android-n-developer-preview/
Completely manual. And let me know if it works.
Click to expand...
Click to collapse
I think the only difference between that and Heisenberg's are these commands
fastboot erase recovery
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase system
fastboot erase vendor
Hopefully those steps would make a difference.
Unfortunately I don't have the device right now, I'll report back once I've tried that.
slashred said:
I think the only difference between that and Heisenberg's are these commands
fastboot erase recovery
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase system
fastboot erase vendor
Hopefully those steps would make a difference.
Unfortunately I don't have the device right now, I'll report back once I've tried that.
Click to expand...
Click to collapse
Sure. I just prefer erase every partition and write it from scratch. Re-writing partitions have given me issues too, during my earlier days with the Nexus S.
Hopefully it would work. But if it doesn't, could it possibly be a hardware issue? And do you have any idea why this might have happened? Also, thank you very much for helping me and responding quickly, I really appreciate it.
slashred said:
Hopefully it would work. But if it doesn't, could it possibly be a hardware issue? And do you have any idea why this might have happened? Also, thank you very much for helping me and responding quickly, I really appreciate it.
Click to expand...
Click to collapse
Could be. Well, I never came across such issue, during my complete history with Nexus. A simple factory reset, wiping cache using recovery, or flashing the factory image has always helped me out.
DJBhardwaj said:
Could be. Well, I never came across such issue, during my complete history with Nexus. A simple factory reset, wiping cache using recovery, or flashing the factory image has always helped me out.
Click to expand...
Click to collapse
I tried the steps from the link you gave me, it booted up fine the first time but when I restarted it, it got stuck in a bootloop again. Then after about 2 loops it started and showed the setup screen but then it crashed after about 2 minutes. Is there anything else I could try?
slashred said:
I tried the steps from the link you gave me, it booted up fine the first time but when I restarted it, it got stuck in a bootloop again. Then after about 2 loops it started and showed the setup screen but then it crashed after about 2 minutes. Is there anything else I could try?
Click to expand...
Click to collapse
This could or could not be a hardware glitch. I think it is, since you have already flashed the factory image, and that should have fixed it. Contact your nearest customer support, and get it replaced as soon as possible.
I talked to them over the phone and they said they aren't responsible for those "update glitches" however they are willing to check it and try to fix. Most likely I would have a hard time begging for them to replace this device. BTW, the only thing I should do to preserve warranty is lock the bootloader right?
slashred said:
I talked to them over the phone and they said they aren't responsible for those "update glitches" however they are willing to check it and try to fix. Most likely I would have a hard time begging for them to replace this device. BTW, the only thing I should do to preserve warranty is lock the bootloader right?
Click to expand...
Click to collapse
Do one thing. Flash the latest Marshmallow factory image, and relock the bootloader. Take it to them, and ask that you did a factory reset, and the phone is stuck on the Google logo since then. Do not mention anything else. If they ask more, tell them you updated the phone via OTA, then made the factory reset, and it stopped.
Related
Hi guys,
I tried to update my Nexus 4 to 4.4 when Google pushed the update out for it yesterday, I forgot I had unlocked the phone (I don't have any custom ROMs on it, just SuperSU.)
Every time I try and power it on, the loading screen is endless, although I can hold power and volume down to enter recovery mode, nothing seems to be working.
I am a bit of a novice so any help or suggestions would be really appreciated!
Thanks.
The first few pages of the forum is littered with posts like this, i was in the same situation.
What i did was download the 4.3 rom from google, and flash /boot and /system onto the phone. I suspect the 4.4 rom would also work.
This got the phone booting without harming (most of) my data, but much of the UI was mangled and didnt work properly. I tried to backup my images over USB but it didnt work, you might have a better result. I also wanted to backup my SMS but they had all vanished.
I rebooted the phone to recovery (TWRP) and used adb to backup the sdcard (adb pull /sdcard sdcard) then did a full flash using the 4.4 rom downloaded from google and that got it working again. Then i reflashed the latest version of TWRP recovery and SuperSU.
Hope that helps.
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
GeorgeAmodio said:
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
Cheers guys, a lot more helpful than the bloke from Google. Will try it in the morning!
This will surely help
If somebody is facing boot loop after kitkat update on nexus 4 and no data backup can try to go to safe mode and backup their data. To goto safe mode on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Yeah that is pretty much what I did to fix mine except that I did not flash the userdata (step 10 in chapter D) so that I would't loose my data.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
What did you end up doing for your PC to detect your phone?
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
I don't know what any of that means or how to do it...
iamj00 said:
I don't know what any of that means or how to do it...
Click to expand...
Click to collapse
This is sideload guide. And the is the rom I used to sideload before: Purity. After I had successfully booted into the system. I flashed 4.4 factory images using this awesome noob friendly guide for a clean kitkat update.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
Installing the driver. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1992345
Boot to bootloader and connect to your PC, usually Windows will find the driver automatically
Hi, I'm desperate today. I've been without my phone since a few days.
In the first place, I wanted to flash another custom ROM. I hadn't change anything to my N4, I was using AOSPAL. You know that F2FS has come, so I wanted to test it. After some fails, some resets, I succeeded to make my phone clean & fast (F2FS & custom kernel). Now I can tell you about my problem.
I noted that, after many tests/flashs, my phone can't boot after turning it off. I stuck at "Google" logo, the ROM apparently disappeared from my phone, or something else went wront. I don't know what.
Then I did a new factory reset, I flashed a ROM/Kernel without any changes to FS, but I got the same problem. If I reboot (reboot from adb, ROM...) my phone, it works. But if I turn it off, I'll stuck at "Google" logo the next boot.
I've actually no ideas, and Google gave me no results...
I'll try to make a new reset, or try another kernel... I don't know where I'm going.
Thanks for help and I wish you to have a nice day.
PS : I'm not a newbie, I already did more than hundreds flashes, some bricks, but I've never seen a similar problem.
Why don't you try flashing the factory image and start over. That should clean everything up
Sent from my Nexus 5
hi
try use nexus tool kit for restore fone bootloop flash rom stock
jd1639 said:
Why don't you try flashing the factory image and start over. That should clean everything up
Sent from my Nexus 5
Click to expand...
Click to collapse
I've already done that each time before flashing any custom mod, since I got that problem.
eltonpestana said:
try use nexus tool kit for restore fone bootloop flash rom stock
Click to expand...
Click to collapse
This isn't the problem... I flashed the factory image many times. It works, but when I turn my N4 off and I want to boot it, I stuck at "Google".. When I reboot from the ROM or adb, there's no problems...
Diaruga said:
I've already done that each time before flashing any custom mod, since I got that problem.
This isn't the problem... I flashed the factory image many times. It works, but when I turn my N4 off and I want to boot it, I stuck at "Google".. When I reboot from the ROM or adb, there's no problems...
Click to expand...
Click to collapse
I assume you've done a factory reset in the stock recovery too? If so I think something is wrong with your phone. Is it still under warranty.
Sent from my Nexus 5
jd1639 said:
I assume you've done a factory reset in the stock recovery too? If so I think something is wrong with your phone. Is it still under warranty.
Sent from my Nexus 5
Click to expand...
Click to collapse
Mhhh when I tried F2F2 and wanted to try something else, I've not done a factory reset in the recovery (did you mean the format partitions in ext4fs or the wipe data/cache/dalvik ?). I used fastboot in order to erase all my partitions, then I flash the factory image archive through fastboot command "-w update".
I don't know whether something is wrong with my phone or not, but I've never seen that problem. It appeared when I did some tests with F2FS. That's all, that's so weird...
Diaruga said:
Mhhh when I tried F2F2 and wanted to try something else, I've not done a factory reset in the recovery (did you mean the format partitions in ext4fs or the wipe data/cache/dalvik ?). I used fastboot in order to erase all my partitions, then I flash the factory image archive through fastboot command "-w update".
I don't know whether something is wrong with my phone or not, but I've never seen that problem. It appeared when I did some tests with F2FS. That's all, that's so weird...
Click to expand...
Click to collapse
I would definitely try to flash the factory image again, then boot into the stock recovery and do a factory reset. F2FS may have borked something. I've never tried it since it does mess with the positions
Sent from my Nexus 5
hi'
I'm not sure if this can work. But it never hurts to try. After flashing stock ROM with CWM. Enter recovery and make full format of all partitions. System and Data partitions and cache and all. After that reinstall the stock rom using nexus tool kit for flashing mode in bootloop. after that flashing custom recovery again and do cleanup, but not the only formates cleanings. I believe you are having trouble reading recognition, partition boot. Uncompensated You must have notice a conflict of partitions on the system format.
eltonpestana said:
Uncompensated You must have notice a conflict of partitions on the system format.
Click to expand...
Click to collapse
I was wondering the same thing...
Thanks guys for your help, I'll flash stock again, and then I'll format correctly the partitions. I hope that's the good way...
Next time its stuck on the Google logo just try plugging in you're charger.
I had the same problem but not down to using F2FS but it did hang on the logo during boot.
After plugging in the charger it booted and hasn't stuck since.
Don't ask my why as I haven't a clue but it worked.
Sent from my Nexus 4 using XDA Premium 4 mobile app
bladebuddy said:
Next time its stuck on the Google logo just try plugging in you're charger.
I had the same problem but not down to using F2FS but it did hang on the logo during boot.
After plugging in the charger it booted and hasn't stuck since.
Don't ask my why as I haven't a clue but it worked.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
FYI this could indicate a problem with your battery
@Diaruga did you ever find a solution?
Sent from my Nexus 5
I plugged my N4, then I tried to flash the factory image again. That was fine. After flashing a custom ROM + custom kernel, still no probems after turning my phone off.
I can't explain why...
Thanks to all, my problem has been solved.
Diaruga said:
I plugged my N4, then I tried to flash the factory image again. That was fine. After flashing a custom ROM + custom kernel, still no probems after turning my phone off.
I can't explain why...
Thanks to all, my problem has been solved.
Click to expand...
Click to collapse
Thanks, glad you got it working again
Sent from my Nexus 5
Last night my phone wanted to update to 4.4.4 because it's been wanting to for a while, but I know it wouldn't work because my phone is rooted. It had tried this at least 3 times before and everything was fine; download update, tries to install, fails, boots right back up. I wanted to get rid of the Update notification in the top bar, so I just ran it again thinking it'd be okay. Well, this time it bricked my phone, leaving me at a neverending loop at the boot animation. I first tried to wipe the cache and dalvik cache, which did nothing. Then I tried a factory restore, which also did nothing. Then I reinstalled the stock 4.4.3 rom I had been using, which did nothing. Then I wiped the SD card completely and reinstalled a stock 4.4.4 rom through sideload, which has done nothing. My phone just sits at the boot animation and taunts me. Worse yet, I have a 16-hour drive tomorrow and my phone was going to be the majority of my sanity during that time.
What should I do?? Is there anything I can do? Normally I would just contact Google to get a replacement (I've done this before when the 4.2 update was causing a lot of bricks,I think it was 4.2 anyway, I forgot) but I'd like to have a working phone for my 16 hour trip..... if possible. Any help would be greatly appreciated! Thank you.
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
CCody said:
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
Click to expand...
Click to collapse
I had a Vanir 4.4.3 rom on my phone that I tried to flash as well, but for some reason it went right into "Optimizing Apps" after the first boot, something I hadn't seen before. Then it got stuck at "Starting Apps...", then after a restart, it too was stuck at the boot animation.
I can boot into recovery luckily, but that's all I can do. I have CWMR v6.0.3.5. I've tried just about everything I can think of. [edit] I was able to contact Google for some live chat support and am now #2 in the queue. Hopefully they can either help me or get a replacement going. Either way, I'd still love any help you guys can give me, I'd really like to get it fixed rather than waiting for a replacement.
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
CCody said:
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
Click to expand...
Click to collapse
I've done that already, Factory Reset + wipe cache + wipe dalvik cache + format system/data/cache/sdcard/data/media. The phone was completely bare and that's when I sideloaded the stock 4.4.4 rom (otherwise it's stuck at the Google boot screen). I'll try it again, though.
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
RawrNate said:
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
Click to expand...
Click to collapse
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
CCody said:
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
Click to expand...
Click to collapse
Yeah haha, it's really really strange. I appreciate you trying to help me, though! Lucky for me I'm getting a "One-time exception replacement" since my warranty is expired but they must be super stumped with the issue as well xD
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
CCody said:
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
Click to expand...
Click to collapse
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Wait, how do I flash the binaries since they're .tgz files?
RawrNate said:
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Click to expand...
Click to collapse
This is really strange man. Flashing stock ROM is the last resort but even that seems to be failing for you.
Have you tried downloading the stockRom again (just to make sure it isn't corrupted). Also, maybe you can try using TWRP instead of CWM this time.
Good luck.
RawrNate said:
Wait, how do I flash the binaries since they're .tgz files?
Click to expand...
Click to collapse
No need to flash them, since you are on a factory image, sry.
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
RawrNate said:
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
Click to expand...
Click to collapse
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
CCody said:
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
Click to expand...
Click to collapse
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
RawrNate said:
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
Click to expand...
Click to collapse
Jesus!
What about custom ROM? Cyanogenmod maybe? Make sure to downlaod the M7-Release.
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
RawrNate said:
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=tZbvuikfnks
CCody said:
https://www.youtube.com/watch?v=tZbvuikfnks
Click to expand...
Click to collapse
Oh good that was easier than I thought xD
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
I had the same issue upon installing N with complete stock. My bootloader was unlocked. I had to boot into recovery, wipe everything (I did it multiple times to be sure) and then in recovery I powered off the device. With N still installed I setup the phone WITHOUT restoring ANYTHING from Google. Upon the initial setup menu I started like it was a brand new phone and I had no Google account. Set that all up later. That ended my bootloop problem.
Unfortunately Wi-Fi password backup was huge for me and now it's gone. Everything else while a hassle was manageable, I'm hoping when the factory image is released I can start over and sign into my account and have that data restored.
318sugarhill said:
I had the same issue upon installing N with complete stock. My bootloader was unlocked. I had to boot into recovery, wipe everything (I did it multiple times to be sure) and then in recovery I powered off the device. With N still installed I setup the phone WITHOUT restoring ANYTHING from Google. Upon the initial setup menu I started like it was a brand new phone and I had no Google account. Set that all up later. That ended my bootloop problem.
Unfortunately Wi-Fi password backup was huge for me and now it's gone. Everything else while a hassle was manageable, I'm hoping when the factory image is released I can start over and sign into my account and have that data restored.
Click to expand...
Click to collapse
what did you use to update to N?
I was on the beta. I never flashed anything else. Like a dummy I had my adb commands backwards (was using adb instead of fastboot). Otherwise I would have reflashed MM.
Some other person had the exact same issue when going from 7.0 to 6.0.1
I will have to get a replacement. :/
same here.... guess this is the first brickable nexus device... the only thing that gets me to boot is if I flash N then flash the MM F vendor image, but it does not detect the sim card and camera don't work.
Mgrev said:
Some other person had the exact same issue when going from 7.0 to 6.0.1
I will have to get a replacement. :/
Click to expand...
Click to collapse
Look in the other post about botched nougat install , some of us got phone working
yeah some but like most people say they got no backup available so it doesnt help @rbouza1
minidude2012 said:
yeah some but like most people say they got no backup available so it doesnt help @rbouza1
Click to expand...
Click to collapse
I have a twrp backup, but it doesn't help at all.
Mgrev said:
I have a twrp backup, but it doesn't help at all.
Click to expand...
Click to collapse
From that thread, my solution.
FragmentsOfLife said:
Okay, this is the method I used to fix my phone. The issue was the phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the lock.
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Click to expand...
Click to collapse
Mgrev said:
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
Click to expand...
Click to collapse
Please join this thread to help troubleshoot.
Hoping to find the answer for you!
Mgrev said:
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
Click to expand...
Click to collapse
Ur getting bootloops bcuz u didn't had cleared the dalvik and sys cache. try doing a sys format (along cleaning those ) and then do a fresh flash of android 6.0.1 then it'll definitely work. (Y)
-anidaniel
anidaniel said:
Ur getting bootloops bcuz u didn't had cleared the dalvik and sys cache. try doing a sys format (along cleaning those ) and then do a fresh flash of android 6.0.1 then it'll definitely work. (Y)
-anidaniel
Click to expand...
Click to collapse
I have already done that, and it does not work.
I have already contacted my retailer about getting a replacement.
Root just disappeared.
This is not a huge problem but when I go to TWRP to reinstall SuperSU, I can't get to the files so I can't install SuperSU.
I have now a MegaPixel ROM with EX kernel and I want to go back to stock. With no root, kernel and recovery... Just don't know how to.
Step by step here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page567
HeroPlane said:
Root just disappeared.
This is not a huge problem but when I go to TWRP to reinstall SuperSU, I can't get to the files so I can't install SuperSU.
I have now a MegaPixel ROM with EX kernel and I want to go back to stock. With no root, kernel and recovery... Just don't know how to.
Click to expand...
Click to collapse
Follow the guidelines on this page and download the factory image from Google server to return 100% stock.
https://developers.google.com/android/images
RoyJ said:
Step by step here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page567
Click to expand...
Click to collapse
therock3181 said:
Follow the guidelines on this page and download the factory image from Google server to return 100% stock.
https://developers.google.com/android/images
Click to expand...
Click to collapse
I tried to reinstall SuperSU but now its stuck on boot animation. How can I fix this?
I don't think you can do a factory reset if you are on a custom Rom. Power down your phone by holding down the power button until the phone shuts down. Go into bootloader mode by pressing power and volume down buttons at the same time. Flash complete factory image from Google site using flash-all.bat command. If you don't know how to do that follow the XDA/Heisenberg guide only to the point where it shows you how to flash. Do not flash all the pieces individually like in the guide. Just use flash-all.bat command like Google suggests.
HeroPlane said:
I tried to reinstall SuperSU but now its stuck on boot animation. How can I fix this?
Click to expand...
Click to collapse
Use the link I posted above. Read it and follow the return to stock section. Like I mentioned earlier, that's a step by step guide to all things 6P. How to root, how to return to stock and everything in between. It has (or at least links you to) all the tools you need. It's a lot more thorough than I am, quite frankly. Just do your best to follow the return to stock section of the guide and if you run into any issues quote me again and let me know where you're stuck and I'll see if I can help. But you're asking for a step by step on how to recover and I've already provided you with a link with those exact steps. Good luck. Specifically steps 10 or 11 depending on if you want to keep your data intact.
RoyJ said:
Use the link I posted above. Read it and follow the return to stock section. Like I mentioned earlier, that's a step by step guide to all things 6P. How to root, how to return to stock and everything in between. It has (or at least links you to) all the tools you need. It's a lot more thorough than I am, quite frankly. Just do your best to follow the return to stock section of the guide and if you run into any issues quote me again and let me know where you're stuck and I'll see if I can help. But you're asking for a step by step on how to recover and I've already provided you with a link with those exact steps. Good luck. Specifically steps 10 or 11 depending on if you want to keep your data intact.
Click to expand...
Click to collapse
I flashed back to stock like the guide told me. Now its bootlooping with the normal Nexus animation. It means that now I have stock ROM but still bootloop...
HeroPlane said:
I flashed back to stock like the guide told me. Now its bootlooping with the normal Nexus animation. It means that now I have stock ROM but still bootloop...
Click to expand...
Click to collapse
What were the exact steps you took? Also, how long has it been boot looping? First boot on a factory image flash can take a while. I've waited like 10 full minutes before boot.
RoyJ said:
What were the exact steps you took? Also, how long has it been boot looping? First boot on a factory image flash can take a while. I've waited like 10 full minutes before boot.
Click to expand...
Click to collapse
I did all the steps in part 10 with angler 7.1.2
It was bootlooping for 5 minute or so. I turned the phone off (While it was bootlooping) and now when I try to boot I get a "No Command" with a opened Android screen. What should I do now?
Maybe I can still flash TWRP and do stuff there?
HeroPlane said:
I did all the steps in part 10 with angler 7.1.2
It was bootlooping for 5 minute or so. I turned the phone off (While it was bootlooping) and now when I try to boot I get a "No Command" with a opened Android screen. What should I do now?
Maybe I can still flash TWRP and do stuff there?
Click to expand...
Click to collapse
The no command screen with an Android on its back is stock recovery. When you see that, hold volume up and while holding volume up, press the power button. That'll get you inside stock recovery. From there you can factory reset. This will likely wipe your internal storage. I'm not exactly sure on that, but assume it does. If that's not an issue, do it and try booting again, but wait longer this time. Leave in on the charger and wait 10 minutes or so. If it still won't boot, try again with 7.1.1 factory images. Also if you're using the flash all .bat file try manually flashing each partition using fastboot.
Edit: If you didn't already, don't lock the bootloader. You won't be able to use fastboot or flash TWRP (if that's what you want to do) with it locked.
RoyJ said:
The no command screen with an Android on its back is stock recovery. When you see that, hold volume up and while holding volume up, press the power button. That'll get you inside stock recovery. From there you can factory reset. This will likely wipe your internal storage. I'm not exactly sure on that, but assume it does. If that's not an issue, do it and try booting again, but wait longer this time. Leave in on the charger and wait 10 minutes or so. If it still won't boot, try again with 7.1.1 factory images. Also if you're using the flash all .bat file try manually flashing each partition using fastboot.
Edit: If you didn't already, don't lock the bootloader. You won't be able to use fastboot or flash TWRP (if that's what you want to do) with it locked.
Click to expand...
Click to collapse
Can't get to the recovery. Forgot to mention that the "No command" screen is flashing. Like, I can see it for less that a second, it turns black, and comes back again for less than a second. Is it looping too?
double
HeroPlane said:
Can't get to the recovery. Forgot to mention that the "No command" screen is flashing. Like, I can see it for less that a second, it turns black, and comes back again for less than a second. Is it looping too?
Click to expand...
Click to collapse
Sounds like it. That's not good, it sounds like a real issue here. How did this end up happening in the first place? You factory reset from TWRP and all this happened? That should have not made you boot loop. You should have been fine and booted and had to sign in again, etc.
Did you lock the bootloader?
RoyJ said:
Sounds like it. That's not good, it sounds like a real issue here. How did this end up happening in the first place? You factory reset from TWRP and all this happened? That should have not made you boot loop. You should have been fine and booted and had to sign in again, etc.
Did you lock the bootloader?
Click to expand...
Click to collapse
Didn't lock bootloader
I did the factory reset from system.
I hope it's not a big issue cause I just paid 150$ to fix the screen. I just wanted to give it to my mom fresh (with no root, custom ROM etc...)
HeroPlane said:
Didn't lock bootloader
I did the factory reset from system.
I hope it's not a big issue cause I just paid 150$ to fix the screen. I just wanted to give it to my mom fresh (with no root, custom ROM etc...)
Click to expand...
Click to collapse
Yeah if you're not on stock, don't factory reset from the system. Use TWRP. Try to fastboot flash TWRP back on the phone and see if you can boot to that.
RoyJ said:
Yeah if you're not on stock, don't factory reset from the system. Use TWRP. Try to fastboot flash TWRP back on the phone and see if you can boot to that.
Click to expand...
Click to collapse
TWRP works! OK that's a good sign (I think so...)
I wiped EVERYTHING (Dalvik/ART cache, cache, system, Data and internal storage)
I will probably try to flash stock now.
HeroPlane said:
TWRP works! OK that's a good sign (I think so...)
I wiped EVERYTHING (Dalvik/ART cache, cache, system, Data and internal storage)
I will probably try to flash stock now.
Click to expand...
Click to collapse
Flash stock minus recovery, leave TWRP. See if you can get it to boot. Try 7.1.1 if possible this time, though.
RoyJ said:
Flash stock minus recovery, leave TWRP. See if you can get it to boot. Try 7.1.1 if possible this time, though.
Click to expand...
Click to collapse
I think I know why 7.1.2 didn't boot
I have a EX kernel updated to march security. I should download a stock with march security or lower.
RoyJ said:
Flash stock minus recovery, leave TWRP. See if you can get it to boot. Try 7.1.1 if possible this time, though.
Click to expand...
Click to collapse
Wow man, thank you so much!
The phone is working after I flashed 7.1.1 march
You are the best!!! :victory:
HeroPlane said:
Wow man, thank you so much!
The phone is working after I flashed 7.1.1 march
You are the best!!! :victory:
Click to expand...
Click to collapse
Glad you got it sorted out!