Related
Hello, for the first time I used Flashfire to update my phone to the latest security update. This did install the system properly, but now if I try to boot into TWRP it will ask for my password to decrypt. I have tried entering both my Google password and my PIN key and neither are accepted. I have also tried changing my PIN key in the Android system settings but this still does not allow TWRP to decrypt my data. Am I missing something?
Same issue! I don't want to factory reset....
Edit: For now, I just flashed my kernel and SuperSU through the USB-OTG feature in TWRP... Fine for the moment.
Having the same issue as well. I updated to MHC19I through fastboot and everything went well. Installed TWRP 3.0.0 and it installed without any problems, but when I attempted to decrypt with my pattern it doesn't work. Booting to Android after decrypting it with the pattern works fine though. I wonder if this is just a TWRP issue?
I am having this same issue as well. However, I have noticed that whenever I boot into the system then try to go back into TWRP recovery it appears that the recovery is missing. The only way I have found to get back into recovery is to re-flash through fastboot.
dkflint723 said:
I am having this same issue as well. However, I have noticed that whenever I boot into the system then try to go back into TWRP recovery it appears that the recovery is missing. The only way I have found to get back into recovery is to re-flash through fastboot.
Click to expand...
Click to collapse
When you flash a boot and system image, if you dont root and patch it with SuperSU, the moment you reboot to android, it will replace recovery. Thats why after flashing is important to boot straight into TWRP, flash the SUperSU zip to patch and root and it wont revert it
But i am on the same boat... went to 19I version... saw the password message from TWRP... i even tried back 29V and took off security, reflashed 19I and still... So i figured it was TWRP needing update... So i flashed 29V and will wait a day or so
chaco81 said:
When you flash a boot and system image, if you dont root and patch it with SuperSU, the moment you reboot to android, it will replace recovery. Thats why after flashing is important to boot straight into TWRP, flash the SUperSU zip to patch and root and it wont revert it
But i am on the same boat... went to 19I version... saw the password message from TWRP... i even tried back 29V and took off security, reflashed 19I and still... So i figured it was TWRP needing update... So i flashed 29V and will wait a day or so
Click to expand...
Click to collapse
So, if you look over at the TWRP thread it is mentioned that it is possible to sideload SuperSU as well as kernels. I was able to do this just fine myself. I think TWRP just needs to be updated by the dev.
I can confirm I have Root access (Flashed SuperSU v2.68 zip) via OTG. Also flashed Xposed Framework v80 and ElementalX Kernel via the same method. I had to download v1.14 zip manually to my OTG as the auto flash method via ElementalX Kernel Manager saves the downloaded zip file to Data and TWRP has no access to it. Bit annoying
What's worse is that TWRP doesn't save any of its' own settings (Time Zone, Haptic Feedback, Display Brightness etc). Guessing this would've normally been saved on Data partition as well. So everytime you boot into recovery, its' like the first time you flashed TWRP Anyway, all working well now and I didn't have to wipe anything.
Confirmed that after the mhc19i TWRP can't decrypt.
adb sideloaded twrp again(for fun), supersu, francokernel v12.
Just getting a ton of app crashes now. Might need to format system and start over :-/
*edit* was able to transfer my /sdcard/ to computer while apps were crashing.
Rebooted to fastboot and did as follows
fastboot update -w image-angler-mhc19i.zip to format everything and start over.
fastboot flash recovery twrp-angler-3.0.0.0.img
reboot to recovery
Enable twrp to write to system
adb sideload franco kernel r12 and supersu
Now everything is decrypted (i have nothing to hide), I ahve root, I have kernel I want, and TWRP is happy because it doesnt' have to decrypt anything
I use WugFresh NRT to root my phone. I unrooted it this morning to get the OTA March update. Everything went fine until I tried to reroot. I can't get past the TWRP screen asking for a password. How can I reroot without TWRP or will this encryption problem always crop up? I do not want to factory reset.
Hey Guys, on Reddit a user suggested flashing the previous builds Vendor image. That should allow twrp decrypt.
flashcity90 said:
Hey Guys, on Reddit a user suggested flashing the previous builds Vendor image. That should allow twrp decrypt.
Click to expand...
Click to collapse
What if I'm already decrypted and using systemless root?
Sent from my Nexus 6P using Tapatalk
brianjking said:
What if I'm already decrypted and using systemless root?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
TWRP 3.0 works as normal if you are already decrypted. The issue, which is in the process of being resolved, only pertains to people using encryption.
Sent from my Nexus 5X using Tapatalk
TWRP 3.0.0-1 is out now. The issue is fixed. You can download from here: https://dl.twrp.me/angler/
Sent from my Nexus 6P using Tapatalk
dkflint723 said:
TWRP 3.0.0-1 is out now. The issue is fixed. You can download from here: https://dl.twrp.me/angler/
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks for posting this info - saved me a headache updating CM today!
Hello everyone,
i just flashed the newest Pure Nexus Rom and everything went fine.
I forgot to flash the SuperSU Zip so i tried to got back into TWRP, but now it stuck.
The System boots normally, only TWRP wont boot.
Anyone had that problem too?
if anyone else has the same issue, here is the answer:
I forgot to erase the userdata or cache.
If you have the same problem use fastboot!
fastboot format cache
fastboot format userdata
Then it should work again.
(Everything on your own risk)
If you dont flah SuperSU asap, TWRP will not stick on reboot (w nougat). That was the issue.
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
Exactly. It happened before you flashed SuperSU zip. Not flashing SuperSU caused your problem. It needs to be flashed the first time you go into TWRP or you won't be able to boot back into TWRP. The previous poster is correct.
Maybe we talk about different problems
Ive formatted cache and userdata yesterday,
now i can go back into twrp.
(SuperSU is not flashed now).
Just tried it, works perfectly!
kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
I never, ever flash userdata, and never had an issue.
We can agree to disagree. Either the other poster and I arent understanding your question, or you arent understanding our reply. It's cool, it happens.
But TWRP not sticking is due to not running SuperSU at the end of the install process. It wont stick.
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
kaufikauf said:
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
Click to expand...
Click to collapse
You should take a look at this post in the official TWRP thread for a clearer reason why.
SlimSnoopOS said:
You should take a look at this post in the official TWRP thread for a clearer reason why.
Click to expand...
Click to collapse
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
USFguy said:
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
Click to expand...
Click to collapse
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
USFguy said:
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
Click to expand...
Click to collapse
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Tried that, ended up going down an update in TWRP and it worked, weird....
I had a similar issue and I had to go back in and reflash Recovery image to recovery partition and all was well
Already been unlocked and running pure nexus for a while, during flashing paranoid android I ran into some trouble and tried to reboot into TWRP, it did not load into TWRP because I forgot to flash the recovery again the last time before rebooting, no biggie.
I fastboot boot TWRP.img from my PC and then flashed rc2 zip from my internal storage, restore my backup and reboot. No luck, I get sent right back to TWRP every time and it never ask me to decrypt my partition.
So now I'm stuck with and encrytpted partition that I can't access, and even trying to fastboot boot TWRP and then flash rc2 from OTG is not fixing the issue, sends me right back to TWRP without decrypt prompt no mater if I choose power off, reboot, bootloader.
I can get to boot loader running adb bootloader from cli.
I'm not sure what to do from here, am I really bricked?
Any help is really appreciated.
Thank you.
Just try to flash TWRP, reboot recovery only, then go to wipe, advanced, and format internal storage, wipe everything once more and restore and boot your nandroid. RC2 has issues with restoring nandroid by the way, use RC1. You probably just have corrupt storage.
It's not possible to fastboot boot twrp and install twrp when you are not on stock boot on both slots. This will always leeds you to a twrp bootloop.
Just fastboot stock boot to slot a and b and then install twrp again and you should be fine.
mikaole said:
It's not possible to fastboot boot twrp and install twrp when you are not on stock boot on both slots. This will always leeds you to a twrp bootloop.
Just fastboot stock boot to slot a and b and then install twrp again and you should be fine.
Click to expand...
Click to collapse
I just did the same darn thing. I was trying to flash PN July update and I always knock it out no problem. However, for some reason, I rebooted right after flashing the July PN and forgot to reflash twrp. I'm rebooted into the ROM, but how do I get twrp recovery back on the device?
whodatfan said:
I just did the same darn thing. I was trying to flash PN July update and I always knock it out no problem. However, for some reason, I rebooted right after flashing the July PN and forgot to reflash twrp. I'm rebooted into the ROM, but how do I get twrp recovery back on the device?
Click to expand...
Click to collapse
The same way you got it on there the first time....
I booted RC1 and flashed RC2. I mistyped fastboot an it failed first go. Lol
Sent from my Pixel XL using Tapatalk
boostedduece said:
Already been unlocked and running pure nexus for a while, during flashing paranoid android I ran into some trouble and tried to reboot into TWRP, it did not load into TWRP because I forgot to flash the recovery again the last time before rebooting, no biggie.
I fastboot boot TWRP.img from my PC and then flashed rc2 zip from my internal storage, restore my backup and reboot. No luck, I get sent right back to TWRP every time and it never ask me to decrypt my partition.
So now I'm stuck with and encrytpted partition that I can't access, and even trying to fastboot boot TWRP and then flash rc2 from OTG is not fixing the issue, sends me right back to TWRP without decrypt prompt no mater if I choose power off, reboot, bootloader.
I can get to boot loader running adb bootloader from cli.
I'm not sure what to do from here, am I really bricked?
Any help is really appreciated.
Thank you.
Click to expand...
Click to collapse
Just flash a factory image and start over.
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Thunderjew said:
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Click to expand...
Click to collapse
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
kekistaneerefugee said:
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
Click to expand...
Click to collapse
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Thunderjew said:
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Click to expand...
Click to collapse
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
kekistaneerefugee said:
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
Click to expand...
Click to collapse
Thank you very much for helping understand this. I will give it another go at some point, hoping I'll get it to work then. Thanks again.
Hello guys,
sorry for archeology but I got exaclty just the same problem.
Yesterday I decided to flash 34.3.A252 onto my XC. SO the soft itself works fine - later I decided to flash newest twrp for Kugo, 3.2.3-0.
So exactly as Thunderjew has said - after I enter TWRP once I got stuck on Sony logo.
So whats the right order of things here?
I flash stock rom -> then I flash kernel -> and then TWRP?
What about the Encryption - should I apply any? I'd very much like to have my device encrypted. Is it even possible?
But - anyone knows wher I can find working Kernel file for this firmware? Or which version from ggow would work?
I purchased a used Nexus 6p from ebay. I've unlocked the bootloader and installed TWRP. When I boot into recovery, I get a screen that's titled, "Mount Decrpt Data". It wants me to enter a password. I don't have the password. What are my options?
I want to root the phone and install custom ROMs.
@msmcintosh- The 6P defaults to data encryption on first boot. You need to do a factory reset and before booting to the OS install TWRP and then boot back into TWRP (reboot recovery). If you want to keep your data unencrypted you now have to either flash SuperSU or a custom kernel. Either of these will disable the force encrypt flag. Also make sure you are installing v3.1.1.0.
v12xke said:
@msmcintosh- The 6P defaults to data encryption on first boot. You need to do a factory reset and before booting to the OS install TWRP and then boot back into TWRP (reboot recovery). If you want to keep your data unencrypted you now have to either flash SuperSU or a custom kernel. Either of these will disable the force encrypt flag. Also make sure you are installing v3.1.1.0.
Click to expand...
Click to collapse
I managed to screw it up. I'm stuck at the Google screen. I can boot into TWRP. I had tried to install Pure Nexus, GApps, Magisk and Franco kernel, but obviously didn't do it correctly. How can I recover my phone?
Uppdate: I download and installed the Oreo factory image and flashed it. Then TWRP. Now to figure out what went wrong flashing Pure Nexus. I'm coming from a nexus 6.
msmcintosh said:
I managed to screw it up. I'm stuck at the Google screen. I can boot into TWRP. I had tried to install Pure Nexus, GApps, Magisk and Franco kernel, but obviously didn't do it correctly. How can I recover my phone?
Uppdate: I download and installed the Oreo factory image and flashed it. Then TWRP. Now to figure out what went wrong flashing Pure Nexus. I'm coming from a nexus 6.
Click to expand...
Click to collapse
I keep screwing this up. I have TWRP, factory Oreo, rooted with Magisk. I made a backup in TWRP. I per Pure Nexus instruction, I installed the Vendor image, Pure Nexus ROM, GApps and Magisk. The system won't boot. Gets stuck at the Google screen. Can't boot into TWRP either. I can reflash TWRP, but the backup is no good (gets stuck at Google screen). I end up reflashing the factory image and TWRP. Then it will boot into Android.
I'm not sure what I'm doing wrong. It was easy to do this on my Nexus 6.
msmcintosh said:
I keep screwing this up. I have TWRP, factory Oreo, rooted with Magisk. I made a backup in TWRP. I per Pure Nexus instruction, I installed the Vendor image, Pure Nexus ROM, GApps and Magisk. The system won't boot. Gets stuck at the Google screen. Can't boot into TWRP either. I can reflash TWRP, but the backup is no good (gets stuck at Google screen). I end up reflashing the factory image and TWRP. Then it will boot into Android. I'm not sure what I'm doing wrong. It was easy to do this on my Nexus 6.
Click to expand...
Click to collapse
Not sure what you are doing wrong with the clean PN install, but you can't downgrade from O to N by flashing an older PN ROM. You may get more specific help in the dedicated PN install thread by nathanchance.
v12xke said:
Not sure what you are doing wrong with the clean PN install, but you can't downgrade from O to N by flashing an older PN ROM. You may get more specific help in the dedicated PN install thread by nathanchance.
Click to expand...
Click to collapse
I ended up flashing Nitrogen O, which worked. Thanks.