Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
jerethi said:
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
Click to expand...
Click to collapse
You should be able to run twrp-2.8.7 without any problems. I believe if you want one higher you might need to format data (decrypt is what I do).
Also, here is what instructions on TWRP say to make it stick.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Tulsadiver said:
You should be able to run twrp-2.8.7 without any problems. I believe if you want one higher you might need to format data (decrypt is what I do).
Also, here is what instructions on TWRP say to make it stick.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Thanks for your response. I am following the directions on TWRP's website, so it must be another issue.
I will try the version you suggest to see if that works. Why would I need to format data to install a later version?
jerethi said:
Thanks for your response. I am following the directions on TWRP's website, so it must be another issue.
I will try the version you suggest to see if that works. Why would I need to format data to install a later version?
Click to expand...
Click to collapse
I believe it requires you to be decrypted. Formatting userdata will wipe your data so make a backup first.
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
jerethi said:
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
Click to expand...
Click to collapse
Flash TWRP from bootloader.
While within bootloader use vol down to select recovery and press power to boot into recovery.
Install SuperSU.
TWRP will stick.
If you boot with stock recovery even once, TWRP will get replaced.
sfhub said:
Flash TWRP from bootloader.
While within bootloader use vol down to select recovery and press power to boot into recovery.
Install SuperSU.
TWRP will stick.
If you boot with stock recovery even once, TWRP will get replaced.
Click to expand...
Click to collapse
Thank you. What is the difference between rooting and using the method that TulsaDiver suggests above?
Tulsadiver said:
I believe it requires you to be decrypted. Formatting userdata will wipe your data so make a backup first.
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
Click to expand...
Click to collapse
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Thanks again for your assistance!
jerethi said:
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Click to expand...
Click to collapse
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
jerethi said:
Thank you. What is the difference between rooting and using the method that TulsaDiver suggests above?
Click to expand...
Click to collapse
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
jerethi said:
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Thanks again for your assistance!
Click to expand...
Click to collapse
Listen to this guy. You can start with the old one if you want then upgrade to the new one later but Supersu modifies your boot.img for you. Like he said, after Fastboot flashing them, Fastboot reboot and before your phone boots up, boot right back into recovery. This will make TWRP stick.
Wow, this post was SO HELPFUL.... Haven't rooted in a while, recently replaced our Nexus 5's with 5x's (on NBD90W) and hadn't felt the need to root. Plus it's gotten so much trickier even with Nexuses.
Anyway totally familiar with ADB/fastboot etc to flash stuff.
I still need to oem unlock and wipe still (bleh).
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
sfhub said:
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
Click to expand...
Click to collapse
jb0ne said:
Wow, this post was SO HELPFUL.... Haven't rooted in a while, recently replaced our Nexus 5's with 5x's (on NBD90W) and hadn't felt the need to root. Plus it's gotten so much trickier even with Nexuses.
Anyway totally familiar with ADB/fastboot etc to flash stuff.
I still need to oem unlock and wipe still (bleh).
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
Click to expand...
Click to collapse
I've always decrypted but that is my personal choice. All I do to root afterwards is flash SuperSU-v2.7.8. That is it. You can adb sideload it (i use twrp for that) or flash it in twrp if you have it already on your phone).
jb0ne said:
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Click to expand...
Click to collapse
You must have a customized boot.img now for root. What customizations you absolutely need to have in boot.img is dependent on how you want root installed, but since you are modifying boot.img, you might as well just stick all the changes you need in boot.img and leave /system untouched.
The default install for SuperSU will make the required changes to whichever boot.img you currently have installed on your system. Generally that consists of disabling dm-verity (integrity check), making encryption optional (not absolutely required), making sepolicy security changes, and adding init script support to load SuperSU binaries later in the boot process.
There are configuration parameters you can feed into SuperSU install to force it to install root on /system instead of systemless, but I would just suggest systemless. It is a cleaner install IMO.
So install the stock boot.img and boot directly into TWRP from the bootloader menu, then install SuperSU and it will modify the boot.img you have installed (and back up original)
The only requirement to keep TWRP (and/or decrypted userdata) is to NEVER boot the phone using a stock boot.img. If you always immediately install SuperSU after flashing the stock boot.img that will satisfy that requirement.
jb0ne said:
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-5x/general/unencrypted-faster-real-world-usage-t3365660
for some reason, when i fastboot installed twrp (after usb debug/unlocking bootloader) I kept getting mount errors when starting twrp. I tried flashing purenexus rom, wipes dalvic, system, data. then my data partition was 0. couldn't mount data part. to copy purenexus or system stock image. I ended up having to use my windows pc to wugfresh it back to life. has been a crazy night. I need coffee.
On coast of SC here, in Charleston. Wishing everybody best of luck with the hurricane.
trentag1988 said:
for some reason, when i fastboot installed twrp (after usb debug/unlocking bootloader) I kept getting mount errors when starting twrp. I tried flashing purenexus rom, wipes dalvic, system, data. then my data partition was 0. couldn't mount data part. to copy purenexus or system stock image. I ended up having to use my windows pc to wugfresh it back to life. has been a crazy night. I need coffee.
On coast of SC here, in Charleston. Wishing everybody best of luck with the hurricane.
Click to expand...
Click to collapse
Did you reboot after unlocking or go ahead and install TWRP right after unlocking?
I tried, but I kept getting the " cannot check for corrupt system because bootloader is unlocked" message, and it never fully booted. I managed to fix the 0data partition by fastboot format userdata, but pure Nexus never worked. It tried to boot, but it stuck on the spinning Google logo thing
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step??
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from twrp then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step??
trentag1988 said:
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step?
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from twrp then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step?
Click to expand...
Click to collapse
What firmware are you on?
Latest nrd90w(?) I believe
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
NBD90W
sfhub said:
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
Click to expand...
Click to collapse
Thanks very much for the detailed assistance. If I wanted to install a custom ROM, do I have to decrypt my user data first? Or can I just install TWRP and then flash?
trentag1988 said:
Latest nrd90w(?) I believe
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
NBD90W
Click to expand...
Click to collapse
I do not believe Pure Nexus is a Nougat Rom. Try starting over and flashing a Rom compatible with your firmware.
Related
With modified twrp 28 i flashed ROM -> reboot to system -> system->reboot recovery -> flashed supersu 2.79 -> reboot to system gets stuck at the boot animation for about 20 minutes. i re flashed the ROM and using it without root. Followed the same for beta 9 without any issues(2.78 SR5 then).
Now, I tried with 2.79 and 2.79 SR1, both same issue. I see couple of people mentioning root is working with 2.79, so looks like i am have some issue with my phone or missing something
Try wiping cache/dalvik. If that doesnt work wipe system and reflash the rom and supersu. Good luck!
Are you on the latest firmware? Because I'm on the Sultan ROM, which requires the latest firmware, and I'm having a ton of issues with root and the supersu app. I finally got supersu to install, but it's just unstable
Working for me:
flash ROM
flash TWRP. img
reboot to recovery
flash supersu (and other system mod eg. Viper...)
wipe dalvik/art and cache
than reboot to system.
Use Phh superuser. For some reason other superusers break F2FS. I have no clue how you guys get TWRP 28 to work but it keeps asking for a pin even when my phone is decrypted.
papzi57 said:
Working for me:
flash ROM
flash TWRP. img
reboot to recovery
flash supersu (and other system mod eg. Viper...)
wipe dalvik/art and cache
than reboot to system.
Click to expand...
Click to collapse
So right
Sent from my ONEPLUS A3003 using Tapatalk
Puddi_Puddin said:
Use Phh superuser. For some reason other superusers break F2FS. I have no clue how you guys get TWRP 28 to work but it keeps asking for a pin even when my phone is decrypted.
Click to expand...
Click to collapse
I always use TWRP and SuperSU, when it comes to rooting.
But that sounds interesting !
Could you elaborate ?? Could you give all very steps you've done ? Any success rate ?
You should never flash OOS Rom with TWRP, you must restore the stock recovery before then after you can flash TWRP and SuperSU.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_10/
I just flashed SuperSU 2.79 SR1 on my Open Beta 10.
I followed the same procedure I did when I rooted Open Beta 9:
adb sideload SR1-SuperSU-v2.79-SR1.zip
Did this under TWRP mod28 (Advanced/ADB_Sideload), not OnePlus recovery.
And...
Yes ! I'm now rooted on Open Beta 10 !
That was successful... on my encrypted F2FS filesystem.
Does anyone know if xposed is working with open beta 10?
Skickat från min ONEPLUS A3003 via Tapatalk
nabeelio said:
Are you on the latest firmware? Because I'm on the Sultan ROM, which requires the latest firmware, and I'm having a ton of issues with root and the supersu app. I finally got supersu to install, but it's just unstable
Click to expand...
Click to collapse
You don't need the last one.
You need the 3.2.6 at least if I remember right.
I'm using the 3.2.7 because I plan to upgrade to OP3T's battery (incompatible with the last one, the 3.2.8) and all is fine for me.
I'm rooted with SuperSU too.
REiced said:
Does anyone know if xposed is working with open beta 10?
Skickat från min ONEPLUS A3003 via Tapatalk
Click to expand...
Click to collapse
Xposed isn't compatible with android nougat regardless of what ROM you are on
Fixed my bootloop issue - removed xposed and all modules, removed magisk and all modules. Removing magisk was also causing bootloops, so I had to reinstall supersu afterwards, which seemed to cure it. And woops, you're on Nougat, but cleaning everything out might help
It is not SuperSu that is unstable or an issue with TWRP that causes the problems, such as breaking root, but rather the boot image that comes with 10. After installing ten, my root was broken and then I noticed in TWRP that my data partition wasn't mounting. So I reformatted the data partition to f2fs from emmc that it formats it as. However, when I rebooted, it took an extra long time before starting up and when it did finally boot up, root was broken again. I then reasoned that the problem lies with the boot image as when one reboots, it will then reformat and encrypt your data partition and break root. I simply flashed and older boot image (both beta 8 or 9 work) and the data partition mounts and I have installed SuperSu, Greenify, Root Browser and Root Deleter. All root apps are working fine and when I reboot, I no longer have any issues. Steps I used. install Beta 10, boot to fastboot and flash older boot image (Don't forget to clear the cache/dalvick). Reboot to TWRP and wipe/reformat your data partition. Flash SuperSu and setup as normal, since you will need to go through the setup again after blowing away the data partition.
---------- Post added at 10:18 AM ---------- Previous post was at 09:27 AM ----------
BTW, I tested it by reflashing the boot image from Beta 10 again and it formatted and encrypted the partition once again. So the issue definitely lies in the boot image that is included with Beta 10. Flash an older boot image, such as the one from Beta 9, as a temporary workaround.
jim262 said:
It is not SuperSu that is unstable or an issue with TWRP that causes the problems, such as breaking root, but rather the boot image that comes with 10. After installing ten, my root was broken and then I noticed in TWRP that my data partition wasn't mounting. So I reformatted the data partition to f2fs from emmc that it formats it as. However, when I rebooted, it took an extra long time before starting up and when it did finally boot up, root was broken again. I then reasoned that the problem lies with the boot image as when one reboots, it will then reformat and encrypt your data partition and break root. I simply flashed and older boot image (both beta 8 or 9 work) and the data partition mounts and I have installed SuperSu, Greenify, Root Browser and Root Deleter. All root apps are working fine and when I reboot, I no longer have any issues. Steps I used. install Beta 10, boot to fastboot and flash older boot image (Don't forget to clear the cache/dalvick). Reboot to TWRP and wipe/reformat your data partition. Flash SuperSu and setup as normal, since you will need to go through the setup again after blowing away the data partition.
---------- Post added at 10:18 AM ---------- Previous post was at 09:27 AM ----------
BTW, I tested it by reflashing the boot image from Beta 10 again and it formatted and encrypted the partition once again. So the issue definitely lies in the boot image that is included with Beta 10. Flash an older boot image, such as the one from Beta 9, as a temporary workaround.
Click to expand...
Click to collapse
It looks like I am having the same issue.
Did you just extract the boot.img from the Beta 9 Rom zip and flash it like the following:
Code:
fastboot flash boot boot.img
Tybalt said:
It looks like I am having the same issue.
Did you just extract the boot.img from the Beta 9 Rom zip and flash it like the following:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Just extracted the image from the zip and flashed it in fastboot using method above.
So I was running stock 4.0.0 with twrp recovery just fine, and go to update via ota the 4.0.1. Now this failed, and so I decided I might as well clean install. After installation now, regardless of rom (even lineageos based) I cannot boot out of twrp. Every reboot leads back to twrp. I can access fastboot, but thats it. I've tried reflashing twrp also
Edit: This is ridiculous. Literally everything looks perfect but it refuses to boot. Tried every rom I can, even tried different recoveries and ****ing nothing. I can't find any rhyme or reason to this nonsense.
Shayded said:
So I was running stock 4.0.0 with twrp recovery just fine, and go to update via ota the 4.0.1. Now this failed, and so I decided I might as well clean install. After installation now, regardless of rom (even lineageos based) I cannot boot out of twrp. Every reboot leads back to twrp. I can access fastboot, but thats it. I've tried reflashing twrp also
Edit: This is ridiculous. Literally everything looks perfect but it refuses to boot. Tried every rom I can, even tried different recoveries and ****ing nothing. I can't find any rhyme or reason to this nonsense.
Click to expand...
Click to collapse
I'll tell you exactly the same as the last one...
First of all... YOU can NEVER try to install an official update having a custom recovery (like TWRP) installed in your device. Previously, you should have changed to stock recovery.
Having said that, you have to make the following....
1. If you have already the full room into internal memory, reboot into recovery. If not, copy the full rom to a pendrive an connect it by OTG.
2. Restart in recovery mode and click on wipe and then, advance wipe and select... davilk, cache, data and system partitions. then, slide the bar.
3. When it finish, go back to the main menu and click on install. Select the full rom from internal storage (or OTG) and install it.
4. When it finishs, you have two options from here...
4.1. First option. Try to install TWRP recovery before rebooting, because the rom will have installed stock recovery. After flashing twrp, theoretically you should get twrp installed but sometimes it fails. So, It is possible it is blocked when you try to reboot system and you can see a warming saying "there is not rom installed". Don't panic, turn off your phone from power bottom and restart the device. You will see the room installed but not the twrp. In this case, you will have to install TWRP from sideload and then, Supersu from recovery.
4.2. Second option. When the rom instalation has a finished, reboot system to check the rom is installed correctly. Then, restart again your device to fastboot mode and install recovery twrp from sideload. Finally, you can install Supersu from recovery.
This is all! Never settle!
Flash stock recovery? Does it boot?
I have the exact same problem and in stuck in a pickle
---------- Post added at 08:15 AM ---------- Previous post was at 08:12 AM ----------
Crazyhat said:
I'll tell you exactly the same as the last one...
First of all... YOU can NEVER try to install an official update having a custom recovery (like TWRP) installed in your device. Previously, you should have changed to stock recovery.
Having said that, you have to make the following....
1. If you have already the full room into internal memory, reboot into recovery. If not, copy the full rom to a pendrive an connect it by OTG.
2. Restart in recovery mode and click on wipe and then, advance wipe and select... davilk, cache, data and system partitions. then, slide the bar.
3. When it finish, go back to the main menu and click on install. Select the full rom from internal storage (or OTG) and install it.
4. When it finishs, you have two options from here...
4.1. First option. Try to install TWRP recovery before rebooting, because the rom will have installed stock recovery. After flashing twrp, theoretically you should get twrp installed but sometimes it fails. So, It is possible it is blocked when you try to reboot system and you can see a warming saying "there is not rom installed". Don't panic, turn off your phone from power bottom and restart the device. You will see the room installed but not the twrp. In this case, you will have to install TWRP from sideload and then, Supersu from recovery.
4.2. Second option. When the rom instalation has a finished, reboot system to check the rom is installed correctly. Then, restart again your device to fastboot mode and install recovery twrp from sideload. Finally, you can install Supersu from recovery.
This is all! Never settle!
Click to expand...
Click to collapse
Here is the problem tho, I can flash Roms but when I attempte to boot into said ROM it just goes straight back to recovery.
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
Puddi_Puddin said:
Flash stock recovery? Does it boot?
Click to expand...
Click to collapse
Tried that too through adb but didn't work for some reason, I forget. Either I messed up or the phone didn't allow it
urvianoob said:
I have the exact same problem and in stuck in a pickle
---------- Post added at 08:15 AM ---------- Previous post was at 08:12 AM ----------
Here is the problem tho, I can flash Roms but when I attempte to boot into said ROM it just goes straight back to recovery.
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
Tried that too through adb but didn't work for some reason, I forget. Either I messed up or the phone didn't allow it
Click to expand...
Click to collapse
You don't do that with adb but with Fastboot
Boot into fastboot > fastboot flash recovery-file name.img
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Hi
Puddi_Puddin said:
You don't do that with adb but with Fastboot
Boot into fastboot > fastboot flash recovery-file name.img
Click to expand...
Click to collapse
Yeah that is what I meant to say lol, I found something in another article on the same problem that worked for a guy, gonna try it soon
---------- Post added at 08:31 AM ---------- Previous post was at 08:22 AM ----------
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
OK I get all of it so basically I flash stock recovery from fast boot, boot into the new stock recovery via fast boot, then flash ROM and I'm done?
OTA works ONLY if you are on stock recovery, rom, kernel.
I suggest to format data in recovery (this will wipe ALL in youre phone),
flash modified recovery (.22, .23. 28 by eng.stk),
flash FULL rom,
flash SuperSU 2.79 stable, if you want root,
flash recovery,
reboot to recovery,
reboot to rom.
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
Where can I get the stock recovery download?
something like that happen to me when i try to go back from N to MM oxygen, i managed to fixed it by installing the stock recovery then install the 3.26 plus the 3.26 "modem" (if i didnt install this one, my touch screen wouldnt work) after that it just works, then i updated to 3.28
i havent install twrp and do the root for now because dont have time to tinker yet, but i can just do than whenever i have the time
I think ---- and my solution
I think some script is created as we click update...It's running on boot up and causing this problem...
I had this problem yesterday and it took me a lot of time to get my device to working...
SOLUTION: first backup the data(it backsup apps and such) from twrp and other files which are important for you...copy it to a PC.
follow the second step in this thread(it will wipe everything)
It's not allowing me to post link...It's the mega unbrick guide from Oneplus3 forums
It will take you to older version and then flash full zip(nougat build) from modded twrp..restore the backup..don't update until someone finds a solution...I did that and I'm waiting for a solution to continue...
hope it helps
This is how I solved mine.
1) Go back to stock recovery v2
2) adb sideload oos, flash magisk then flash systemless supersu.
Try this guys, found a way how to flash 36mb OTA file with latest modified TWRP by eng.stk here https://forum.xda-developers.com/devdb/project/dl/?id=22429
1. Download and dirty flash the full 4.0 zip https://drive.google.com/file/d/0BzS3nWITUqU_Sk5yQkRqWkhFY3c/view
2. Flash 4.0.1 OTA (36mb) https://drive.google.com/file/d/0B6FY-XKZtgn4R2d2Rk8xd3AzWVE/view?usp=drivesdk
3. Flash SuperSU
4. Reboot
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
eko_cahyono said:
Try this guys, found a way how to flash 36mb OTA file with latest modified TWRP by eng.stk here https://forum.xda-developers.com/devdb/project/dl/?id=22429
1. Download and dirty flash the full 4.0 zip https://drive.google.com/file/d/0BzS3nWITUqU_Sk5yQkRqWkhFY3c/view
2. Flash 4.0.1 OTA (36mb) https://drive.google.com/file/d/0B6FY-XKZtgn4R2d2Rk8xd3AzWVE/view?usp=drivesdk
3. Flash SuperSU
4. Reboot
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did it work for you? For me it keeps booting back to TWRP
---------- Post added at 03:45 AM ---------- Previous post was at 03:17 AM ----------
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
Where did you get new stock recovery? link please
paul369741 said:
Did it work for you? For me it keeps booting back to TWRP
---------- Post added at 03:45 AM ---------- Previous post was at 03:17 AM ----------
Where did you get new stock recovery? link please
Click to expand...
Click to collapse
Yes It works
You can grab the stock recovery in the OP3 toolkit here on xda
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Flash through fastboot, then flash/sideload a full stock zip. After that your phone should be back in working order and you can flash TWRP back.
Goodluck!
qyrus said:
You can grab the stock recovery in the OP3 toolkit here on xda
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Flash through fastboot, then flash/sideload a full stock zip. After that your phone should be back in working order and you can flash TWRP back.
Goodluck!
Click to expand...
Click to collapse
If my phone is rooted, flashing through fastboot the stock recovery will remove root?
Used the search, used google, couldn't find any concrete answers
I am on Android N - unlocked bootloader - rooted via magisk, One Plus 3.
Could I do the following?
use TWRP to make a Nandroid Backup (System+Data+Boot) of my current set-up
then, manually flash (using twrp) Android O
find out I don't particularly like it
Go back to TWRP and Nandroid Restore back to Android N, as if no update ever happened
Or will there be issues?
Thanks
I do that with freedomos. 2.17(N)>3.1(O)>2.17. I restore nandroid and reflash rom
xGOGI said:
I do that with freedomos. 2.17(N)>3.1(O)>2.17. I restore nandroid and reflash rom
Click to expand...
Click to collapse
Should have mentioned I'm using stock rom.
So I'd restore the nandroid via twrp, and I should be good to go?
arthritis said:
Used the search, used google, couldn't find any concrete answers
I am on Android N - unlocked bootloader - rooted via magisk, One Plus 3.
Could I do the following?
use TWRP to make a Nandroid Backup (System+Data+Boot) of my current set-up
then, manually flash (using twrp) Android O
find out I don't particularly like it
Go back to TWRP and Nandroid Restore back to Android N, as if no update ever happened
Or will there be issues?
Thanks
Click to expand...
Click to collapse
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Thank you for the detailed procedure.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Thank you
Hi @maxs8007
thanks for the instructions. I did all that to get back to my nougat rom (PureFusion) and all seem good and phone booted fine. But i am stuck on login screen after booted up. I tried my correct password several times but to no avail. anyway reset my password without factory resetting again?
Thanks for the advise.
sqlpro said:
Hi @maxs8007
thanks for the instructions. I did all that to get back to my nougat rom (PureFusion) and all seem good and phone booted fine. But i am stuck on login screen after booted up. I tried my correct password several times but to no avail. anyway reset my password without factory resetting again?
Thanks for the advise.
Click to expand...
Click to collapse
Go to twrp - advanced - file manager - go to root folder - data - system - and delete files with .key extension. There will be 2 files delete both and reboot.
maxs8007 said:
Go to twrp - advanced - file manager - go to root folder - data - system - and delete files with .key extension. There will be 2 files delete both and reboot.
Click to expand...
Click to collapse
Thank you very much and that worked. I am back in the system.
BTW in your original instructions I had to re flash rom after restoring twrp backup otherwise it didn't boot and stuck at rom animation.
sqlpro said:
Thank you very much and that worked. I am back in the system.
BTW in your original instructions I had to re flash rom after restoring twrp backup otherwise it didn't boot and stuck at rom animation.
Click to expand...
Click to collapse
Thanks for pointing out, I must have forgot to add it. I'll update again.
Hi @maxs8007
I ran into this issue again today! after unlocking as per instructions yesterday and am back into phone and re-set the pin and all good. But today i had to reboot the phone and same issue again , cant login on the lock screen!! i tried deleting those files again but to no avail!!
any ideas before factory reset and loose my data ? Thanks.
sqlpro said:
Hi @maxs8007
I ran into this issue again today! after unlocking as per instructions yesterday and am back into phone and re-set the pin and all good. But today i had to reboot the phone and same issue again , cant login on the lock screen!! i tried deleting those files again but to no avail!
any ideas before factory reset and loose my data ? Thanks.
Click to expand...
Click to collapse
This should not have happened, anyways delete all those files which I've highlighted in the image below. This will reset the lock settings.
Oh sorry I forgot to attach the file. Here it is.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Hi, OP here. Thanks for this guide.
Unfortunately, it did not work out for me.
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Done
Do factory reset(wipe everything except internal storage)
Wiped fine although I got an error of not being able to wipe 'USB-OTG' or whatever it's called. I ignored it and moved on.
then flash oreo twrp image.
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Then I rebooted and went back to recovery.
Flash oreo stock zip
flash oreo twrp image
Done
reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu.
This is where it ends. I get stuck at the OnePlus loading screen and forced reboot into twrp and flashed magisk. Once I boot up the OS, I get stuck at the OnePlus logo and that's it.
I actually re-did ALL of the steps again (in case I made a mistake) and still, the same issue. No progression.
Once I gave up on Oreo, I decided to go restore my nandroid
Reboot to recovery. Perform factory reset as mentioned above.
Wiped
Restore everything except bootloader, cache and dalvik cache
Here's the issue:
I press Restore (I uncheck both bootloader and cache, but there's no option for a specific dalvik cache- unless I'm not looking hard enough?) and I get the 255 Error.
Flash nougat twrp recovery. Reboot to system.
I tried to ignore that error and flash the twrp recovery.
Rebooted and it took me to fastboot. Regardless of I keep trying to reboot system it won't work.
I actually made two separate nandroid backups (the same 'everything except system image' as you've described) in case one of the backups was corrupted. Both backups ended up with the same error.
I got too tired of all these errors and just found a stock recovery and ROM and flashed it back. Now, all my apps and settings are gone. To be honest, I just want my phone back to where it was with Nougat.
Can anyone assist me?
@maxs8007, Like I said I did that already but nope still same issue. It wouldn't let me do matter what I did.
---------- Post added at 04:59 AM ---------- Previous post was at 04:54 AM ----------
arthritis said:
Hi, OP here. Thanks for this guide.
Unfortunately, it did not work out for me.
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Done
Do factory reset(wipe everything except internal storage)
Wiped fine although I got an error of not being able to wipe 'USB-OTG' or whatever it's called. I ignored it and moved on.
then flash oreo twrp image.
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Then I rebooted and went back to recovery.
Flash oreo stock zip
flash oreo twrp image
Done
reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu.
This is where it ends. I get stuck at the OnePlus loading screen and forced reboot into twrp and flashed magisk. Once I boot up the OS, I get stuck at the OnePlus logo and that's it.
I actually re-did ALL of the steps again (in case I made a mistake) and still, the same issue. No progression.
Once I gave up on Oreo, I decided to go restore my nandroid
Reboot to recovery. Perform factory reset as mentioned above.
Wiped
Restore everything except bootloader, cache and dalvik cache
Here's the issue:
I press Restore (I uncheck both bootloader and cache, but there's no option for a specific dalvik cache- unless I'm not looking hard enough?) and I get the 255 Error.
Flash nougat twrp recovery. Reboot to system.
I tried to ignore that error and flash the twrp recovery.
Rebooted and it took me to fastboot. Regardless of I keep trying to reboot system it won't work.
I actually made two separate nandroid backups (the same 'everything except system image' as you've described) in case one of the backups was corrupted. Both backups ended up with the same error.
I got too tired of all these errors and just found a stock recovery and ROM and flashed it back. Now, all my apps and settings are gone. To be honest, I just want my phone back to where it was with Nougat.
Can anyone assist me?
Click to expand...
Click to collapse
Buddy from my experience the whole thing too finicky and am thinking just factory reset and stick with stock rom. I wasted so much time already. Everytime I get different error, probably recoveries still not fully compatible with Oreo.
sqlpro said:
@maxs8007, Like I said I did that already but nope still same issue. It wouldn't let me do matter what I did.
---------- Post added at 04:59 AM ---------- Previous post was at 04:54 AM ----------
Buddy from my experience the whole thing too finicky and am thinking just factory reset and stick with stock rom. I wasted so much time already. Everytime I get different error, probably recoveries still not fully compatible with Oreo.
Click to expand...
Click to collapse
Could you please tell me what error you get on the lock screen? Could you post an image so that I can get a better idea of what's happening with your device? Also could you please confirm which files have you deleted? This time you need to delete 5 files which are related to lock screen setting and those are the only files responsible for lock settings on the device. I'm somewhat confused because I never ran into such issue while I did the oreo thing
If you have decided to flash stock then just make a backup of data partition so that you won't loose your data and you can easily restore it via twrp.
---------- Post added at 01:06 AM ---------- Previous post was at 12:42 AM ----------
arthritis said:
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Click to expand...
Click to collapse
I read the entire post and here what I've to say. The above quoted steps is where you went wrong. The recovery needs to to be flashed as a recovery and not as system.
In your case the nougat recovery was never replaced with the oreo recovery because you flashed it as a system. This is where it went wrong. Sorry for the dalvik cache and USB - otg, I didn't mentioned about them. Those are the least important points in flashing though I should have mentioned that already
The next thing you mentioned is you went back to recovery which at that moment was nougat recovery and not oreo recovery. I'll link the modded recovery I used for oreo below
The next thing you did is you flashed oreo zip and again flashed the oreo recovery but as you flashed the recovery as system, the oreo stock rom was automatically replaced with recovery because you flashed it as system and the device didn't boot because there was no android OS to boot up
You got stuck on oneplus boot up screen. (this was going to happen because of the same flashing error at your end).
You were unable to boot back to nougat as well because of the same issue.. Never flash the recovery as system. This won't let you boot the device.
To restore your nandroid backup just follow the steps below
As you confirmed you booted to stock rom with a stock recovery.
Flash nougat twrp via fastboot
Boot back to the twrp recovery and restore the nandroid backup and you are good to go
---------- Post added at 01:18 AM ---------- Previous post was at 01:06 AM ----------
I'll make a video in my free time to help you guys with the steps that I've followed to flash oreo rom and how i came back to nougat successfully.
Hello @maxs8007
Sorry I didn't have any screen shots of the prompt and finally I was fed up with the whole process and had to switch back to oreo stock rom.
Login prompt I was referring to was standard pin required load android. Black background with only pin entry.
BTW I tried blu twrp recovery oreo version and nougat version.
What's interesting is, after several failed attempts it said I got 10 more tries before phone wiped out but after 10 attempts it started counting backwards from zero, - 1,-2 etc., finally I had to flash stock recovery via fastboot and selected forgot password option which reset my phone.
BTW I have deleted all those files from data/system I found another thread but no dice.
Thank you for trying to help us all.
@maxs8007 followed your steps. Booted to oreo, didn't felt as stable as nougat then booted back to nougat. You saved me. Thanks.
sqlpro said:
Hello @maxs8007
Sorry I didn't have any screen shots of the prompt and finally I was fed up with the whole process and had to switch back to oreo stock rom.
Login prompt I was referring to was standard pin required load android. Black background with only pin entry.
BTW I tried blu twrp recovery oreo version and nougat version.
What's interesting is, after several failed attempts it said I got 10 more tries before phone wiped out but after 10 attempts it started counting backwards from zero, - 1,-2 etc., finally I had to flash stock recovery via fastboot and selected forgot password option which reset my phone.
BTW I have deleted all those files from data/system I found another thread but no dice.
Thank you for trying to help us all.
Click to expand...
Click to collapse
I'm sorry that I was unable to help you. The thing is I never used the pin prompt to load android because I reboot too often to flash things via recovery and its too much of a hassle to enter the pin everytime the device is booted and I think it's too much to a security for a android device when there's already a lock screen present once booted to secure the device.
Please don't put the pin entry to load android next time if you flash stuff regularly. It will save you the hassle of going back to stock rom and recovery when something like this ever happens again. The files which I told you to delete in the image I posted above remove the lock screen protection completely
The login pin at the boot to load android was implemented to avoid unauthorized access to the device in case it gets stolen or lost.
maxs8007 said:
I'm sorry that I was unable to help you. The thing is I never used the pin prompt to load android because I reboot too often to flash things via recovery and its too much of a hassle to enter the pin everytime the device is booted and I think it's too much to a security for a android device when there's already a lock screen present once booted to secure the device.
Please don't put the pin entry to load android next time if you flash stuff regularly. It will save you the hassle of going back to stock rom and recovery when something like this ever happens again. The files which I told you to delete in the image I posted above remove the lock screen protection completely
The login pin at the boot to load android was implemented to avoid unauthorized access to the device in case it gets stolen or lost.
Click to expand...
Click to collapse
Frankly no clue why deleting those files didn't reset my pins and I even deleted gatekeeper files too.
Maybe these are lock screen key files and android boot prompt stored somewhere else. Not sure though.
How can i Install TWRP in PIE v10.0.7 with Magisk root? please show me how ?
I'm also need to know what is the proper and right way to install twrp (offain ver.) There's so many conflicting and difference opinion in the thread...its so confusing which one is the right step...why do i need to fastboot twrp img first then flash the trwp installer zip? Do i really need to flash disable force encryption fix? Why is it necessary? Why can i just fastboot flash the twrp img like any other phone?
You can probably install in any order but I did Magisk first. You must have an unlocked bootloader.
Use the standard Magisk process:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
TWRP also has a standard process:
https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
I had a bootloop after installing TWRP that I fixed by reinstalling Magisk (fastboot the patched image and install again). Other people seem to have success flashing an older aboot image.
If you need more information you're going to have to be clearer about what you have now.
The phone seems reasonably brick-proof. If you can get to fastboot you can restore a fastboot ROM.
---------- Post added at 07:56 AM ---------- Previous post was at 07:49 AM ----------
secondkai said:
why do i need to fastboot twrp img first then flash the trwp installer zip?
Click to expand...
Click to collapse
TWRP lives in boot, not a separate recovery partition because this is an A/B phone.
TWRP installs by patching boot but you cannot do that from fastboot. So you boot into TWRP and patch boot from there.
secondkai said:
Do i really need to flash disable force encryption fix? Why is it necessary?
Click to expand...
Click to collapse
I didn't do it. But I'm on stock.
I think it's mostly a problem for custom ROMs and GSIs. With encryption on they cannot read the data partition.
No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,
Don't bother with twrp
Just use magisk.
Download the factory pixel image on your PC , unzip the boot.img file and transfer to your phone.
Open magisk manager and install magisk by patching the boot.img file U just transferred.
Copy that new patched boot img back to your PC.
Use ADB to ADB reboot bootloader
Type: fastboot flash boot patched_boot.img
That's it
mediaman123 said:
No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,
Click to expand...
Click to collapse
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.0-0.img; in twrp, flashed 3.3.0-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.
Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
My safety net passes in magisk, but I don't use any apps that I can verify that with.
jlokos said:
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.3-0.img; in twrp, flashed 3.3.3-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.
Click to expand...
Click to collapse
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks
docluv01 said:
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks
Click to expand...
Click to collapse
Sorry; an extra 3; I'm using TWRP 3.3.0.0.
---------- Post added at 07:58 AM ---------- Previous post was at 07:37 AM ----------
1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
I DL magisk hide module and use it for two apps, one for comcast business and the other which regulates my home thermostat.
Wow, thanks guys.....you have all laid out pretty well your processes which I will go through later on....
It's strange, as everything is installed and magisk believes it working it just doesn't pass thee root check..
I'll get back to you with my progress...??