My brand new Nexus 6P was working fine until last night when I asked it to reboot in safe mode (after a normal reboot yielded the message "home won't start"). After a very long time of staring at the animation I booted into TWRP and wiped the delvik and regular caches ... still no dice. This morning I wiped the partitions all together and did a restore including the system and data from my back up from a week ago. Still no dice. The phone partially loads the restore and then reboots. Even a raw factory reset has failed. Phone is obviously rooted, has TWRP and has elemental X 1.16 on it. How do I fix this? Can it be wiped and fully reset with my computer like I used to do the Samsung S5? Does ODIN work on these (I am almost certain that is a no answer). Thanks!
Just attempted another full wipe and restore. It reboots out of restore as soon as it hits the part about writing system image.
ODIN will not work, you will need to use fastboot & adb.
I'd recommend following Heisenberg's guide here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
and resetting to factory image
I ended up loading from scratch with ADB and Fastboot after I found the factory kernel and firmware online for it. No more screen filters for me.
Sent from my Nexus 6P using XDA-Developers mobile app
Related
I cant make any changes to my phone. Every time I reboot it reverts back to the state it was this morning. I'm on CM7.
My phone was crashing today, so I decided to do a wipe, however on reboot everything reverts back to the state it was this morning.
I tried doing a nandroid restore using TWRP. Restore completed successfully, but everything reverts back to today's state on reboot.
I tried wiping everything in TWRP, but on reboot everything is reverted as if i had not done anything
Thinking TWRP was the problem i installed clockworkmod and did multiple wipes, but on reboot everything reverted
I have tried doing a Format system, data, etc and no matter what everything reverts back on reboot
I tried re-installing CM7, but again everything reverts back
I tried installing CM9 and it would not boot at all. I then re-installed CM7 and when i rebooted everything reverted to today's state.
Even if i uninstall an app, remove widgets, or anything, on reboot everything reverts back
When I try to wipe using system settings, I get the following error message "Invalid Path: null"
At this point I'm out of ideas. I want to do a full wipe and do a fresh rom flash. Any thoughts would be appreciated.
One more detail. I set the alarm on the phone for 7:00am last night, however the alarm went off at 6:30am which was the time I set it to the night before. I assume the phone rebooted on its own during the night and set the alarm back to what it was the day before. Thanks in advance if anyone has some insight.
No idea what the hell is going on with the phone.
Full wipe and flash the official factory images onto your phone with fastboot. They are here. https://developers.google.com/android/nexus/images
Guides on how to do it are on these forums....
albundy2010 said:
No idea what the hell is going on with the phone.
Full wipe and flash the official factory images onto your phone with fastboot. They are here. https://developers.google.com/android/nexus/images
Guides on how to do it are on these forums....
Click to expand...
Click to collapse
I didn't try fastboot yet. I'll try that when I get home. Thanks
I just performed a wipe via fastboot and tried installing a rom via fastboot. I got successful messages, but open reboot everything reverted back. At this point I don't know what to do.
Installing a ROM via fastboot? What exactly did you do?
albundy2010 said:
Installing a ROM via fastboot? What exactly did you do?
Click to expand...
Click to collapse
I actually just did the wipe via fast boot then installed the rom via clockwork. I performed the fastboot -w command.
I also just flashed Twrp again. Mounted the SD card, deleted all files on the SD card. SD card showed full capacity. I then unmounted and remounted and all files returned. I dont get any errors in clockwork or twrp yet they are unable to do anything and have it stick.
Within the rom i mounted The SD card and deleted all my files in windows. I took about 15 seconds and everything looked clear. I then unmounted and mounted again and all files appear. Its almost like i don't have write access to the phone, but there are zero error messages during deletes and wipes
Only thing left to try is stock screwing around with a ROM / cmw etc and flash factory images with fastboot.
Sounds like it may not work but try it. Was your device encrypted?
Can try a fastboot OEM lock and unlock and flash back all factory images. If that don't work you're Sol I suppose. Could try odin but if fastboot flash factory images dont work I don't see that working either.
It sounds like the sd card becomes read-only
Hi guys,
That is the situation: i was running Purity ROM + ART on my new Nexus 10. I've got the lastest TWRP installed.
Few minutes ago I've decided to flash KT Manta, in order to make some undervolt... but something went wrong...
The flash seems to have been successful, but later, during the chace wipe, the device suddenly turned off. I tried to turn it on, but I was stuck at the loading screen of the rom.
Then I went into recovery, I've tried to wipe chace again, but TWRP fails, and is one of the messages of error "unable to mount /chace."
Fortunately, before flash the kernel, I did a nandroid backup (of evrything except cache, unchecked by default). The restore seems to be successful (success, 135sec time), but I'm still stucked on Purity Loading screen.
So THAT is what can I do:
1 - I can enter fastboot menu
2 - I can enter recovery
3 - My tablet charges normally
But I can not load the ROM. Seems to be a soft brick, but I need your help. Pls: ((
Just flash the factory image. This will wipe the entire device. If you want to backup anything just adb pull fron recovery..
Sent from my Galaxy Nexus using xda app-developers app
Woooh i've finally solved it
That's what I've done:
1- Turned off the device for a while
2- Made a factory reset
3- Wiped Chace ---> no errors this time!
4- Wiped Dalvik chace --> no errors here too!
5- Restored the nandroid Backup
[unnecessary background information] A while back I decided to encrypt my OnePlus 2 - mostly to compare its performance with my Nexus 6P, which is also (obviously) encrypted. Today I decided I was tired of Oxygen OS and wanted to install CM13 since Grarak had gotten the fingerprint scanner working properly. I went ahead and unlocked the bootloader, installed TWRP 3.0.0.2, and excitedly flashed the shiny new OS (without making a backup, like an idiot)[/]
After booting up into CM13 the system asks me for my encryption key (sure, whatever) and then I get this big screen that says "Decryption Unsuccessful....The password that you entered is correct but unfortunately your data is corrupt" and goes on to say that a factory reset will fix the problem and any lost data can be re-downloaded from the cloud. I said "great!" and hit the "reboot now" button that reboots back into TWRP, runs a short script, and sends me back to where I started (presumably not on purpose).
Now, I tried doing a full wipe of the entire device via TWRP, which sent me into a new panic mode when I couldn't manage to get any files to transfer over when I tried to send them over MTP - I finally went about using the ADB Sideload feature in TWRP to once again install the same (and a different) ROM all of which garnered the same result.
Finally, the point of the story: Is there a way for me to fully remove encryption from the system from within TWRP? If not, am I totally hosed or does someone have another idea? Frankly, I'd be happy to just have a booting phone at this point.
Thanks in advance!!
So following up on my own thread, I found the setting in TWRP that specifically allows you to erase the data partition (something that I thought I had done when I did a standard wipe and/or when I did the advanced wipe and specifically told it to wipe everything) and rebooted and it finally booted happily into Android. I'm not sure if this is a bug in TWRP or a bug in CM's script that is causing issues but something isn't quite right.
I'm having issues with restoring the factory image of stock Android 6.0.1, I'm using
@Heisenberg guide to create the fresh back up image on TWRP-3.0.2-0. Once I create
the back up, I boot into the OS and perform a factory reset, when i do that the phone resets
into TWRP, and performs the wipe to the device, when i go to do the restore, it freezes
at about 39%, and reboots fully trying to enter the OS, but its corrupt due to TWRP restarting
in the middle of the recovery.
I did at one point upgrade to Android N, but reverted back to android 6.0.1 if that makes a difference.
TL;DR - Created a fresh factory image of 6.0.1 using TWRP, cannot recover with it, TWRP freezes at 39% every time.
What options are you selecting to backup/restore?
Heisenberg said:
What options are you selecting to backup/restore?
Click to expand...
Click to collapse
I'm doing a back up selecting the system/data/boot/vendor boxes, leaving everything else unchecked, and a second back up with only the EFS,
When i go to restore, I'm just using the first back up, leaving the EFS alone unless ever needed, and am selecting the system/data/boot/vendor boxes
DeathSentinels said:
I'm doing a back up selecting the system/data/boot/vendor boxes, leaving everything else unchecked, and a second back up with only the EFS,
When i go to restore, I'm just using the first back up, leaving the EFS alone unless ever needed, and am selecting the system/data/boot/vendor boxes
Click to expand...
Click to collapse
I can only think that your backup is corrupt. Also, instead of booting into Android and performing a factory reset that way, just go into the advanced wipe section of TWRP and wipe only data. Maybe you'll just need to flash the factory images to get the phone booting up fresh again.
That's where it gets interesting, I've flashed the factory 6.0.1 image, then flashed twrp, created the back up again, did the advanced wipe as you said, did the restore again, and same result, at around 39% of the recovery the phone reboots and the back up gets corrupt. My main goal is to make sure this back up absolutely works before I root and start playing around with flashing xposed modules, but I'm unable to do a successful restore for the life of me.
DeathSentinels said:
That's where it gets interesting, I've flashed the factory 6.0.1 image, then flashed twrp, created the back up again, did the advanced wipe as you said, did the restore again, and same result, at around 39% of the recovery the phone reboots and the back up gets corrupt. My main goal is to make sure this back up absolutely works before I root and start playing around with flashing xposed modules, but I'm unable to do a successful restore for the life of me.
Click to expand...
Click to collapse
I'm stumped, I really don't know why it wouldn't be working if you're performing the backup the way you say you are. Sorry I can't be more helpful. If it's any consolation, a backup probably isn't strictly necessary because you can always get back to stock by flashing the factory images.
Heisenberg said:
I'm stumped, I really don't know why it wouldn't be working if you're performing the backup the way you say you are. Sorry I can't be more helpful. If it's any consolation, a backup probably isn't strictly necessary because you can always get back to stock by flashing the factory images.
Click to expand...
Click to collapse
I'm stumped too, I've been able to do this effortlessly in the past with this phone, my Nexus 9 and m8 GPE, it wasn't until I upgraded to N and reverted back to 6.0.1 this started to happen. I've even gone as far as trying different versions of twrp, but have had the same result.
I'm just worried in a worst case scenario I'm away from a comp, something crashes and I can't do a restore via twrp, I could be SOL until I get to a comp with adb.
i had a similiar problem , but when i got into the stock image , i went into settings and did a factory reset from there , no worries your BL stays unlocked , once thats done get whatever apps you want back , disable fingerprint /security junk , then boot into bl just like the guide says , youll be able to fastboot install recovery , (boot back into bl, then scroll to recovery and start a gain) then make your backups yor OG & EFS , then reboot , get su reboot into recovery install and yould be be fine , i think you can also try fastboot format userdata , as well
DeathSentinels said:
I'm stumped too, I've been able to do this effortlessly in the past with this phone, my Nexus 9 and m8 GPE, it wasn't until I upgraded to N and reverted back to 6.0.1 this started to happen. I've even gone as far as trying different versions of twrp, but have had the same result.
I'm just worried in a worst case scenario I'm away from a comp, something crashes and I can't do a restore via twrp, I could be SOL until I get to a comp with adb.
Click to expand...
Click to collapse
Just keep a ROM zip + gapps on your phone at all times, if you run into trouble you can flash that.
That definitely makes sense , i always dk that
Sent from my Nexus 6P using XDA-Developers mobile app
I installed Naptime (rooted phone). Put my 6P into standby. Worked for 15 minutes. I went away and came back and the device was in a bootloop. Can't believe naptime could be the cause of this, but things were fine before this was installed. Symptoms sounds like the bootloop others are complaining about.
Wiped the Davlik cache. Made no difference.
Tried to restore my TWRP backup and that reboots after about 90MB. If I choose verify the MD5 backup, TWRP reboots after about 30 seconds of verification. So it seems like any I/O attempt on the system partition is causing the 6P to reboot. Is there anything else I can try before resorting to an RMA w/Google?
mrlad said:
I installed Naptime (rooted phone). Put my 6P into standby. Worked for 15 minutes. I went away and came back and the device was in a bootloop. Can't believe naptime could be the cause of this, but things were fine before this was installed. Symptoms sounds like the bootloop others are complaining about.
Wiped the Davlik cache. Made no difference.
Tried to restore my TWRP backup and that reboots after about 90MB. If I choose verify the MD5 backup, TWRP reboots after about 30 seconds of verification. So it seems like any I/O attempt on the system partition is causing the 6P to reboot. Is there anything else I can try before resorting to an RMA w/Google?
Click to expand...
Click to collapse
Wipe everything except internal, and not only the cashes, and try your restore again.
You can also try to install a full factory image from the Google website using flash-all.bat command.
jhs39 said:
You can also try to install a full factory image from the Google website using flash-all.bat command.
Click to expand...
Click to collapse
Tried a full factory install of 7.1.2 (was on 7.1.1). Didn't help. Shows the Google boot logo and then reboots.
What is interesting is fastboot was able to write the system image for 7.1.2.
coremania said:
Wipe everything except internal, and not only the cashes, and try your restore again.
Click to expand...
Click to collapse
I'm on TWRP 3.1. Just noticed its crashing wiping any of the items (cache, Dalvik cache etc.). The reboot happens after it shows updating partition table.
Was finally able to get a clean Dalvik cache wipe. I noticed that in all cases, there are three TWRP errors about mounting the cache partition before it does the wipe. Is this normal?
mrlad said:
Was finally able to get a clean Dalvik cache wipe. I noticed that in all cases, there are three TWRP errors about mounting the cache partition before it does the wipe. Is this normal?
Click to expand...
Click to collapse
I don't know if it's normal but I've seen the same errors on my device after installing the 7.1.2 factory images and wiping the cache in TWRP 3.1. I assumed it might have to do with no cache partition being included with 7.1.2.
Sent from my Nexus 6P using XDA Labs
mrlad said:
Tried a full factory install of 7.1.2 (was on 7.1.1). Didn't help. Shows the Google boot logo and then reboots.
What is interesting is fastboot was able to write the system image for 7.1.2.
Click to expand...
Click to collapse
I still get a constant reboot too.
I also have naptime but this issue wasn't an immediate problem after any form of installation. I was just scrolling through facebook and then phone freezes and reboots and then gets stuck in reboot lol.
HELP
jono0402 said:
I still get a constant reboot too.
Click to expand...
Click to collapse
What does your reboot loop look like? I see the Google logo for a few seconds then the device reboots. I never see the animation start.