So I went ahead and started to root my Nexus 6P. I installed the systemless modified boot.img and TWRP, then I sideloaded the systemless SuperSU in TWRP. I am encrypted and TWRP can decrypt still, however when I try to boot the phone, I get the Decryption unsuccessful message and it wants me to reset the phone. I hit reset, it factory resets in TWRP, and it just comes to the same screen upon boot. Any ideas?
Just flashed the userdata.img and system.img parts of the factory image, upon boot I get a message saying there is an internal error in the device and to contact the manufacturer. I just flashed the stock bootloader, boot.img, radio, system, userdata and now it is just stuck on the boot animation. =(
Just used the flash-all.bat in the factory image and now it is working again. Not sure what caused the problem, I know others are using the systemless root method, so I have no idea.
gakio12 said:
Just used the flash-all.bat in the factory image and now it is working again. Not sure what caused the problem, I know others are using the systemless root method, so I have no idea.
Click to expand...
Click to collapse
Reflash vendor and it will fix error
Sent from my Nexus 6P using Tapatalk
Related
Hi,
I'm on latest M version, latest TWRP, systemless root and Despair kernel 3.1.
When I first installed TWRP it couldn't decrypt partitions, so I had to install a kernel that disables force encrypt and factory reset the phone. So I ended up with un-encrypted partitions.
Now, TWRP supports decryption so I thought to encrypt the partitions. I went to Security -> Encrypt phone. This has been hanging on Android animation logo for 2.5hrs and no indication when it will finish.
Has anyone had a similar problem ?
What are my chances that it will complete gracefully and I wont need to factory reset the phone once again?
jodvova said:
Hi,
I'm on latest M version, latest TWRP, systemless root and Despair kernel 3.1.
When I first installed TWRP it couldn't decrypt partitions, so I had to install a kernel that disables force encrypt and factory reset the phone. So I ended up with un-encrypted partitions.
Now, TWRP supports decryption so I thought to encrypt the partitions. I went to Security -> Encrypt phone. This has been hanging on Android animation logo for 2.5hrs and no indication when it will finish.
Has anyone had a similar problem ?
What are my chances that it will complete gracefully and I wont need to factory reset the phone once again?
Click to expand...
Click to collapse
Chances are very low. I had the same issue and the only way I was able to fix it was to use the Google factory image and completely wipe the phone. Then boot it before flashing anything including TWRP. It encrypts in about a minute. Setup the phone, and then flash TWRP, modified root boot image if you want, and the corresponding SU zip.
Sent from my Nexus 6P using Tapatalk
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
kunal_07 said:
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
Click to expand...
Click to collapse
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
kunal_07 said:
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
Click to expand...
Click to collapse
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Heisenberg said:
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Click to expand...
Click to collapse
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
kunal_07 said:
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
Click to expand...
Click to collapse
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Heisenberg said:
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Click to expand...
Click to collapse
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
the log says:
E:Unable to decrypt with default password, you may need to perform a format data.
E:unable to mount storage
E:unable to mount settings storage during GUI startup.
kunal_07 said:
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
Click to expand...
Click to collapse
That's odd, I can't think of why 3.0.0-1 wouldn't boot, but 2.8.7.2 definitely won't work as it obviously can't decrypt. You might not be able to backup.
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
kunal_07 said:
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
Click to expand...
Click to collapse
I think you're pretty much stuck, you could try disabling all security.
is it possible to sideload supersu somehow?
kunal_07 said:
is it possible to sideload supersu somehow?
Click to expand...
Click to collapse
Maybe, you could try adb sideload in TWRP, but SuperSU needs to access the data partition which TWRP can't decrypt.
I tried it and it got to
**Boot image patcher**
patching sepolicy.
Failure, aborting.
i seem to have the same issues too. unable to access recovery and lost root. phone cant be detected in fastboot.
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Great news
1. Yes.
2. I don't think such a command exists. You'd need to use the "fastboot format userdata" command instead if you want to decrypt anyway. Just remember to backup all your data first.
3. You'd need to flash a custom kernel today doesn't force encryption. Otherwise your data well will automatically encrypt on the first boot after formatting.
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
kauemelhado said:
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
Click to expand...
Click to collapse
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
kunal_07 said:
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
Click to expand...
Click to collapse
Tks,
I found it 2 seconds later I asked you. LOL
Anyhow, thank you bro.
I woke up this morning and in a daze decided to flash beanstalk6.17. For what ever reason it seemed to have made apps disappear and was lagging out my 6p. I was rushing out the door and in a state of panick I flash purenexus back on. This caused constant booklooping. I restored from a nandroid backup from earlier today but now I can pulldown my settings from the top and constantly have "Unfortunately, the process android.process.acore has stoppped. I reset all apps and it stopped for a while but as soon as I went into any app it began again.
Any help will be appreciated.
Clear the cache for Contacts and Contacts Storage. That should do it.
Sent from my Nexus 6P using XDA-Developers mobile app
Cleared contact cache and still get the notification when I open phone or messages. Also cant slide down to view my quick settings.
Have you tried doing a full wipe, and fresh install of a ROM?
https://www.youtube.com/watch?v=TlvKydE0EVA
pepsal said:
I woke up this morning and in a daze decided to flash beanstalk6.17. For what ever reason it seemed to have made apps disappear and was lagging out my 6p. I was rushing out the door and in a state of panick I flash purenexus back on. This caused constant booklooping. I restored from a nandroid backup from earlier today but now I can pulldown my settings from the top and constantly have "Unfortunately, the process android.process.acore has stoppped. I reset all apps and it stopped for a while but as soon as I went into any app it began again.
Any help will be appreciated.
Click to expand...
Click to collapse
Did you clean flash? Sounds to me like you didn't wipe properly.
Okay so I managed to resolve the issue but now have created a even greater one. I needed to update my vendor image and when installing I accidentaly chose boot image. Now my 6p boots straight to recovery and my twrp data is encrypted and it wont accept my unlock code so I cant access my data to recover. I have a copy of a backup on my pc if that helps. Any guidance would be apprieciated.
pepsal said:
Okay so I managed to resolve the issue but now have created a even greater one. I needed to update my vendor image and when installing I accidentaly chose boot image. Now my 6p boots straight to recovery and my twrp data is encrypted and it wont accept my unlock code so I cant access my data to recover. I have a copy of a backup on my pc if that helps. Any guidance would be apprieciated.
Click to expand...
Click to collapse
Taking a guess, but I think you need to flash proper Vendor img. Can you adb reboot bootloader while phone is in TWRP? If so then at boot loader, reflash the vendor.img.
pepsal said:
Okay so I managed to resolve the issue but now have created a even greater one. I needed to update my vendor image and when installing I accidentaly chose boot image. Now my 6p boots straight to recovery and my twrp data is encrypted and it wont accept my unlock code so I cant access my data to recover. I have a copy of a backup on my pc if that helps. Any guidance would be apprieciated.
Click to expand...
Click to collapse
dratsablive said:
Taking a guess, but I think you need to flash proper Vendor img. Can you adb reboot bootloader while phone is in TWRP? If so then at boot loader, reflash the vendor.img.
Click to expand...
Click to collapse
You'll need to flash the correct boot.img back to the device.
EDIT: Unless I'm misunderstanding you. Did you flash the boot.img to the vendor partition or flash the vendor.img to the boot partition?
Heisenberg said:
You'll need to flash the correct boot.img back to the device.
EDIT: Unless I'm misunderstanding you. Did you flash the boot.img to the vendor partition or flash the vendor.img to the boot partition?
Click to expand...
Click to collapse
I flashed the vendor.img to the boot partition.
Edit: Going to attempt flashing the boot.img now
Edit2: Worked! Thanks for your help
I had some complex issues flashing some roms and ended up having to format userdata. Now I am unencrypted and I have not been able to get the stock rom (from the official OTA zip) to boot. I was able to get all 3 of the custom OOS roms in the development section to boot, however when i go into settings and start encryption the green android logo flashes on the screen and the device does a hot reboot without starting encryption. I have tried countless things to boot the stock rom and/or get encryption to work including flashing the stock recovery on a custom rom, and the stock recovery asks for a pattern and mine doesn't work. I am totally out of ideas so if anyone has any please help.
solved: i previously did fastboot format userdata and it didn't work. I just did fastboot format userdata, system, and cache and the full ota zip installed, the security settings say it's encrypted, and i was able to decrypt with the stock recovery. Time to flash twrp and break more stuff!
Encryption
I believe the phone encrypts when you put a screen lock on.
I put a pin on mine booted in to recovery and it was encrypted, rebooted phone, removed pin, rebooted recovery everything back to normal.
hibby50 said:
solved: i previously did fastboot format userdata and it didn't work. I just did fastboot format userdata, system, and cache and the full ota zip installed, the security settings say it's encrypted, and i was able to decrypt with the stock recovery. Time to flash twrp and break more stuff!
Click to expand...
Click to collapse
Flashing stock boot.img in bootloader mode should encrypt the phone too.
gee2012 said:
Flashing stock boot.img in bootloader mode should encrypt the phone too.
Click to expand...
Click to collapse
Where or how can one extract/get the stock boot.img?
going to twrp wipe Then format data and typing yes will re-encrypt the device
Watch this
hibby50 said:
solved: i previously did fastboot format userdata and it didn't work. I just did fastboot format userdata, system, and cache and the full ota zip installed, the security settings say it's encrypted, and i was able to decrypt with the stock recovery. Time to flash twrp and break more stuff!
Click to expand...
Click to collapse
Thanks for sharing your solution. I found myself in this precarious position today. Solved with fastboot format... Thanks!
So I was using a certain root app and it told me to enable Magisk Core mode and reboot. I did that, and my phone was in a bootloop. So I wen't to TWRP and flashed stock ROM zip. Rebooted and it was still bootlooping.
So I took a TWRP Backup of all partitions, and then wiped system fully and flashed stock ROM. Still bootlooping. So I did a factory reset and wiped system as well, keeping internal storage. Then I flashed stock ROM zip and rebooted - it fixed it, but was factory reset. So I went back into TWRP and restored the data partition. Unfortunately, I got the TarFork Error 255 when restoring. I saw on google that you need to setup Android first to restore. Rebooted to go into Android but it took me to TWRP, and this time didn't ask for decryption password. I went to internal storage and everything was encrypted. I don't remember exactly what I did next but now I'm in fastboot with no TWRP recovery, and when I do fastboot boot twrp.img I get this error: "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')"
Can anyone help me recovery from this and possibly get my internal storage back, or at least installed apps. I can provide TWRP restore log as well: https://del.dog/ivugupemeq
NateDev said:
So I was using a certain root app and it told me to enable Magisk Core mode and reboot. I did that, and my phone was in a bootloop. So I wen't to TWRP and flashed stock ROM zip. Rebooted and it was still bootlooping.
So I took a TWRP Backup of all partitions, and then wiped system fully and flashed stock ROM. Still bootlooping. So I did a factory reset and wiped system as well, keeping internal storage. Then I flashed stock ROM zip and rebooted - it fixed it, but was factory reset. So I went back into TWRP and restored the data partition. Unfortunately, I got the TarFork Error 255 when restoring. I saw on google that you need to setup Android first to restore. Rebooted to go into Android but it took me to TWRP, and this time didn't ask for decryption password. I went to internal storage and everything was encrypted. I don't remember exactly what I did next but now I'm in fastboot with no TWRP recovery, and when I do fastboot boot twrp.img I get this error: "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')"
Can anyone help me recovery from this and possibly get my internal storage back, or at least installed apps. I can provide TWRP restore log as well: https://del.dog/ivugupemeq
Click to expand...
Click to collapse
Have you tried the MSM Download Tool to restore the device yet? I'm leaning towards that honestly.
---------- Post added at 01:44 AM ---------- Previous post was at 01:42 AM ----------
NateDev said:
So I was using a certain root app and it told me to enable Magisk Core mode and reboot. I did that, and my phone was in a bootloop. So I wen't to TWRP and flashed stock ROM zip. Rebooted and it was still bootlooping.
So I took a TWRP Backup of all partitions, and then wiped system fully and flashed stock ROM. Still bootlooping. So I did a factory reset and wiped system as well, keeping internal storage. Then I flashed stock ROM zip and rebooted - it fixed it, but was factory reset. So I went back into TWRP and restored the data partition. Unfortunately, I got the TarFork Error 255 when restoring. I saw on google that you need to setup Android first to restore. Rebooted to go into Android but it took me to TWRP, and this time didn't ask for decryption password. I went to internal storage and everything was encrypted. I don't remember exactly what I did next but now I'm in fastboot with no TWRP recovery, and when I do fastboot boot twrp.img I get this error: "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')"
Can anyone help me recovery from this and possibly get my internal storage back, or at least installed apps. I can provide TWRP restore log as well: https://del.dog/ivugupemeq
Click to expand...
Click to collapse
(Double post, ignore this)
Got it fixed by flashing full stock ROM in fastboot without wiping, so userdata was recovered, and then restored app data from the TWRP nandroid backup in Titanium backup
NateDev said:
Got it fixed by flashing full stock ROM in fastboot without wiping, so userdata was recovered, and then restored app data from the TWRP nandroid backup in Titanium backup
Click to expand...
Click to collapse
mind sharing exactly how you did that? As i'm in pretty much the same boat
FullyCustom2 said:
mind sharing exactly how you did that? As i'm in pretty much the same boat
Click to expand...
Click to collapse
Damn don't even have this phone anymore lol
I think I used the fastboot ROMs from an xda post but when it asks you to wipe or not I clicked no, and then I booted to Android and apps data can be restored from a nandroid backup in titanium backup, just search to find that feature, instead of restoring the data backup in twrp