I flashed the magisk uninstaller which puts the original stock boot image on. However doing this has also removed my twrp recovery (my phone is now on stock recovery image). Are the partitions now directly linked in nougat?
Sent from my Nexus 6P using XDA-Developers mobile app
Guitarboarder28 said:
I flashed the magisk uninstaller which puts the original stock boot image on. However doing this has also removed my twrp recovery (my phone is now on stock recovery image). Are the partitions now directly linked in nougat?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
No. Nougat automatically overwrites your recovery. If you want TWRP, then you either need a modified boot image, or after you flash TWRP on stock boot image, immediately boot into recovery and root your phone with Super SU.
ultyrunner said:
No. Nougat automatically overwrites your recovery. If you want TWRP, then you either need a modified boot image, or after you flash TWRP on stock boot image, immediately boot into recovery and root your phone with Super SU.
Click to expand...
Click to collapse
Ah thank you!
Sent from my Nexus 6P using XDA-Developers mobile app
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!
So I just installed TWRP 3.0.2-0 on my Nexus 4 with the twrp installer app and it installed fine. When I rebooted from recovery to go back to the regular phone, it booted straight back into twrp again... So I flashed stock android with Nexus root toolkit and it successfully flashed it so it said and it still only boots into either bootloader or twrp recovery... Powering on with just the power button goes straight to recovery. Why is this? How can I fix it?
I don't think twrp should be on the phone if the phone was successfully flash to a stock rom unless you didn't flash stock recovery.
Managed to fix it... My Nexus 4 lives for another day!
Sent from my Nexus 4 using XDA-Developers mobile app
Please tell us how you fixed it ?
So i installed Android N via OTA update. Now I think my want my root back. Is it possible to flash TWRP now that im on Android N? Do I have to go back to marshmallow and flash the android N zip?
You can flash TWRP on android N but you will also decrypt you phone or you won't be able to access TWRP. It does not work on N if your phone is encrypted you will be stuck on the TWRP splash screen. You will have to wipe userdata and then flash unencrypted boot image, then flash TWRP, then su and you will be good.
Sent from my Nexus 6P using XDA-Developers mobile app
sounds like wayyyy to much work. ill downgrade lol
If you flash all the .IMG files in fastboot with the exception of recovery, and the format userdata and cache and reflash twrp you can stay encrypted and have twrp. Then just shellac side load adb and flash su.
Sent from my Nexus 6P using XDA-Developers mobile app
3r0k said:
If you flash all the .IMG files in fastboot with the exception of recovery, and the format userdata and cache and reflash twrp you can stay encrypted and have twrp. Then just shellac side load adb and flash su.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Have you done this?
I dont want root, I want to keep the ability to continue having updates whenever they come out. But I'm uber annoyed at the hotspot restriction I have. There's a way to remove it with twrp but I was never able to boot into twrp because of encryption.
Yes, this is how I have my phone setup, I am Fully encrypted and have TWRP booting and able to flash. This is how I root N and don't need to decrypt.
3r0k said:
If you flash all the .IMG files in fastboot with the exception of recovery, and the format userdata and cache and reflash twrp you can stay encrypted and have twrp. Then just shellac side load adb and flash su.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Can you pls give a step by step guide? Thanks.. Would we erase internal data as well?
3r0k said:
Yes, this is how I have my phone setup, I am Fully encrypted and have TWRP booting and able to flash. This is how I root N and don't need to decrypt.
Click to expand...
Click to collapse
Can u give step by step method for flashing TWRP on N ??
This is not a step by step for flashing twrp on N there are plenty of those just use search.
This is how I flashed twrp without flashing any kind of modified boot.img on N.
Start on stock MM. Flash twrp.
Download N build and extract all images. Flash all partitions except for recovery. Reboot. See if you can boot to recovery. If it hangs at twrp logo Format userdata and format cache and reflash twrp. Optional: adb side load latest SU for root.
Sent from my Nexus 6P using XDA-Developers mobile app
3r0k said:
This is not a step by step for flashing twrp on N there are plenty of those just use search.
This is how I flashed twrp without flashing any kind of modified boot.img on N.
Start on stock MM. Flash twrp.
Download N build and extract all images. Flash all partitions except for recovery. Reboot. See if you can boot to recovery. If it hangs at twrp logo Format userdata and format cache and reflash twrp. Optional: adb side load latest SU for root.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Ihave installed twrp for 6.x for my p9 android 7 and its not booting into twrp ok then from where can i install the N build and how can i flash everything except recovery
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
Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem
Make sure you're following the exact steps from this post. Every step is crucial (except #3, because you have to disable your screen lock before booting twrp.
You shouldn't have to manually mount anything in TWRP either. The magisk installer might give you an error about mounting system but it doesn't seem to make any difference.
[QRCODE][/QRCODE]
yellk20 said:
Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem
Click to expand...
Click to collapse
You cannot have TWRP installed with 8.x.
TWRP is not compatible.
You must flash the original boot image, then install magisk.
TWRP cannot remain.
You will boot loop.
Please read the instructions on rooting carefully.
Ok thank you
Why can't TWRP replace recovery instead of boot?
RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
No one has created a bit image with TWRP as the recovery.
Sent from my PH-1 using XDA Labs
RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
Because the partition layout of the Essential does not have a recovery partition.
Recovery is contained in the boot image.
So to have TWRP resident/permanent, the boot image must be patched.
It has been done for 7.x, but sense 8.x is still beta, there is no official TWRP for Oreo.
Once Oreo is final, I expect we will get a TWRP that works.
The current limitation, means you can't flash without a computer handy.