[How-To] Restore OOS from Oreo 8.1 | Restore factory encryption | Re-lock bootloader - OnePlus 5T Guides, News, & Discussion

You need to do this if you've flashed an Oreo 8.1 ROM and find that you can't get back to OOS because...
The ROM can't read /data so it hangs on the boot animation or reboots to recovery, even on a clean flash.
TWRP won't recognize your PIN/password or "default_password".
You've tried re-formatting /data from TWRP several times and it doesn't solve your problem.
Here is how to get back to 100% stock and/or restore factory encryption, which is different than Oreo 8.1 encryption:
1. Back up /sdcard to your PC as it will be erased with all of your files, pictures, music, etc.
2. Flash the stock recovery from bootloader.
Code:
fastboot flash recovery [I]stock_recovery.img[/I]
Latest OOS official stock recovery
Latest OOS beta stock recovery
3. Restore system setting in recovery.
This step is necessary to restore factory formatting and encryption of /data.
If a password/PIN is set, click “I forgot my password.”
Boot into stock recovery. Once there, go to Wipe data and cache > Reset system setting and Erase everything(Music, pics, etc.).
Note: If you don't do the "Erase everything..." option, factory encryption will not be reset.
4. Boot TWRP from bootloader.
You could flash TWRP and reboot to recovery, but TWRP will get overwritten with the stock recovery when OOS boots anyway. It's faster just to boot TWRP from a command prompt. Use the command:
Code:
fastboot boot [I]twrp-recovery.img[/I]
I recommend using using:
[RECOVERY][dumpling] TWRP 3.2.1-0 for Oreo (8.0 and 8.1) by codeworkx
5. While in TWRP, move “OOS...ROM.zip” to the SD card.
In Windows File Explorer, copy OOS...ROM.zip to the device.
Alternately, you may use the following ADB command from a command prompt
Code:
adb push [I]OOS...ROM.zip[/I] /sdcard/
Since OOS is a very large file (1.6GB), this will take 5-10 minutes.
Latest OOS signed flashable zip
Latest OOS beta (Oreo) flashable zip
6. Flash OOS...ROM.zip from TWRP.
7. Reboot system.
Your device will be formatted, encrypted and loaded with the stock recovery and ROM as it came from the factory. You may need to find the OOS...ROM.zip you pushed to /sdcard and delete it from emulated storage (/storage/emulated) if you don't see it at /sdcard after booting the ROM.
8. Optional: To re-lock your your bootloader, follow these additional steps:
This can only be done from a factory-supplied OOS ROM (including Oreo) with no modifications or the phone will not boot!
Enable USB debugging under Developer options.
Reboot to bootloader.
Unlock the bootloader with the following command:
Code:
fastboot oem lock
Return to Developer options and turn off "OEM unlocking"

Thank you for the write up .. nicely done :good:
Sent from my OnePlus5T using XDA Labs

It gave me an error 1 in TWRP. I had to do the following:
1) Make sure the bootloader remains unlocked
2) Back your apps up in TitaniumBackup
3) Back your /sdcard partition up on your computer so you don't lose anything
4) Reflash stock recovery in the bootloader
5) Boot into stock recovery and hit "forgot password" when it asks for your lock code
6) Boot back into bootloader and reflash TWRP
7) Place stock OOS zip onto the /sdcard partition
8) While you're in TWRP, flash stock recovery through its image flasher then reboot into recovery
9) Flash stock OOS, reboot, and then mod however you want
Click to expand...
Click to collapse

blackknightavalon said:
It gave me an error 1 in TWRP. I had to do the following:
Click to expand...
Click to collapse
Will in 9th last step restoring from nandroid OB-1 work ?
It should I guess
Sent from my ONEPLUS A5010 using Tapatalk

Bump!
I made a big update to the OP today with more explanation, more detail and download links.

Thanks buddy, that tutorial worked perfectly!

The other way is to flash rollback image to Nougat in stock recovery.
https://goo.gl/YRyrt6

there are no other ways to revert back to stock OOS without affecting internal sd /sdcard ?
thanks for the guide above.

Ok I'm a bit Rusty. Flash from bootloader? Meaning adb? Then adb TWRP then boot to TWRP then flash stock room(s)?

Ippolito1971 said:
Ok I'm a bit Rusty. Flash from bootloader? Meaning adb? Then adb TWRP then boot to TWRP then flash stock room(s)?
Click to expand...
Click to collapse
Please do not quote the whole OP just to get someone's attention. A mention (@the Doctor) would suffice.
To answer your question, flash the stock recovery with the fastboot command:
Code:
fastboot flash recovery [I]stock_recovery.img[/I]
The only ADB command involved is "push" to get the ROM onto the sdcard in step 5.

Thx @the Doctor. My apologies.

Thanks for the writeup, I'll probably try soon and report back.

Thanks for this, may need it. Plan to flash DU 8.1 tomorrow. So you can't just restore an ob1 or ob2 nandroid from a custom ROM?

tcat007 said:
Thanks for this, may need it. Plan to flash DU 8.1 tomorrow. So you can't just restore an ob1 or ob2 nandroid from a custom ROM?
Click to expand...
Click to collapse
You can, but TWRP will not recognize your PIN or password while in OOS, so you'll have to set lockscreen security to none or swipe. Or you could do the procedure in the OP, then restore only data from your nandroid. You'll have to re-flash Magisk or any other mods after that.

I don't use a pin for backups or restores. Since I seem to have to format internal storage to get a custom ROM to boot, was just wondering if restore of oos nandroid works once on DU.
Sent from my OnePlus5T using XDA Labs

hello thanks for the guide just did this when i boot i cant connect to any wifi network thanks

How can I get my wifi back after reverting to 4.7.6? Ive tried EFS backup and everything possible but the only way to get wifi back is to flash an Oreo zip.

forty9er said:
hello thanks for the guide just did this when i boot i cant connect to any wifi network thanks
Click to expand...
Click to collapse
Did you restore to 4.7.6 or Oreo Beta 1/2?
Dazed No More said:
How can I get my wifi back after reverting to 4.7.6? Ive tried EFS backup and everything possible but the only way to get wifi back is to flash an Oreo zip.
Click to expand...
Click to collapse
Have you flashed OOS Oreo Beta? My theory is that the firmware won't downgrade back to OOS 4.7.6, but I'm not sure. I've only restored back to OOS OB1/2, and wifi has worked perfectly every time.

the Doctor said:
Did you restore to 4.7.6 or Oreo Beta 1/2?
Have you flashed OOS Oreo Beta? My theory is that the firmware won't downgrade back to OOS 4.7.6, but I'm not sure. I've only restored back to OOS OB1/2, and wifi has worked perfectly every time.
Click to expand...
Click to collapse
Flashing Oreo beta is the only way to get it back as myself and others have found in the thread that was started on the subject. I hadn't seen that initially when I posted in here.
I was hopeful that following your method to a T would get me my wifi back on 4.7.6 but it wasn't meant to be. Absolutely nothing I have tried in the last 24 hours has worked to get it working on 4.7.6 including multiple clean and dirty flashes of the full 4.7.6 zip, twrp, stock recovery, restoring multiple backups, restoring EFS, factory reset, wipes, etc.
You might want to add that to the OP that if you revert to 4.7.6 that wifi will not work.

Dazed No More said:
You might want to add that to the OP that if you revert to 4.7.6 that wifi will not work.
Click to expand...
Click to collapse
Thank you, and done. :good:

Related

Downgrading from Nougat to Marshmallow

I've been reading about bricked devices and want to downgrade from N to MM. I seen a thread in the 5X forum about it but want to be be sure before I attempt it with my 6P. Anyone have trouble downgrading? Can I just flash the factory image like usual? Thanks in advance.
Sent from my Nexus 6P using Tapatalk
Advice for now - Don't even bother unless your ready for a soft bricked device until the issue is resolved and considering we dont even have a factory image it could be weeks away.
its your descision but there are two threads now attempting to fix this and people have had mixed results, the only seemingly helpful thing is to back up 100% of your devices partitions / efs and absolutely everything from your MM build and store it safe on your PC for when your device eventually soft bricks.
just don't bother ! if your on MM stay for another month or so or lump it with stock rooted N, don't attempt to go back !
hutzdani said:
Advice for now - Don't even bother unless your ready for a soft bricked device until the issue is resolved and considering we dont even have a factory image it could be weeks away.
its your descision but there are two threads now attempting to fix this and people have had mixed results, the only seemingly helpful thing is to back up 100% of your devices partitions / efs and absolutely everything from your MM build and store it safe on your PC for when your device eventually soft bricks.
just don't bother ! if your on MM stay for another month or so or lump it with stock rooted N, don't attempt to go back !
Click to expand...
Click to collapse
Yeah, so many stories of expensive paperweights when trying the downgrade. I suspect they're having some major issues with the 6p factory image, since the 5x has been posted for nearly two weeks. I've got mine working pretty well, with really good battery and ARISE sound actually working system-wide. I suspect we may see the factory image when this month's security update is rolled out - at least I hope so, given we're already into September.
That's what I figured. Looks like I'm staying on N. Thanks!
Sent from my Nexus 6P using Tapatalk
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Great thanks! I'll give it a go
Sent from my Nexus 6P using Tapatalk
RoyJ said:
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Click to expand...
Click to collapse
Works fine, thanks!
RoyJ said:
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Click to expand...
Click to collapse
Okay, it's been a while for me and I don't want to mess my phone up.
I have a Nexus 6P and the bootloader is still locked, phone is not rooted, and running official 7.0 from the beta signup a couple weeks ago.
I'd like to go back to MM because my battery life has been atrocious. Now my questions:
1. Do I have to unlock the bootloader first before I attempt the steps above?
2. Where is the best place to extract the last MM factory image to use during fastboot?
srt4mn said:
Okay, it's been a while for me and I don't want to mess my phone up.
I have a Nexus 6P and the bootloader is still locked, phone is not rooted, and running official 7.0 from the beta signup a couple weeks ago.
I'd like to go back to MM because my battery life has been atrocious. Now my questions:
1. Do I have to unlock the bootloader first before I attempt the steps above?
2. Where is the best place to extract the last MM factory image to use during fastboot?
Click to expand...
Click to collapse
Yes in order to use fastboot, you need to unlock the bootloader. This will wipe all userdata off of the phone so backup to your PC first. I just unzip everything in platform-tools.
RoyJ said:
Yes in order to use fastboot, you need to unlock the bootloader. This will wipe all userdata off of the phone so backup to your PC first. I just unzip everything in platform-tools.
Click to expand...
Click to collapse
Thanks! I'll give it a shot here after I figure out this bootloader usb data cable issue.
EDIT:
Got back to 6.0.1 after following your instructions, thanks again!!
Worked like a charm. Thanks @RoyJ!
No problem, glad it worked for everyone.
I have been running Weta 7.1 for a week and went back to Pure Nexus using TWRP 3.0.2-3. I went into recovery, wiped everything except internal storage, flashed the vendor image, then flashed the rom and gapps,then flashed the vendor image again. The phone booted up just fine. I never back up or restore the EFS partition.
bmwkeith said:
I have been running Weta 7.1 for a week and went back to Pure Nexus using TWRP 3.0.2-3. I went into recovery, wiped everything except internal storage, flashed the vendor image, then flashed the rom and gapps,then flashed the vendor image again. The phone booted up just fine. I never back up or restore the EFS partition.
Click to expand...
Click to collapse
So your in PN MM with new nougat modem and bootloader ?
dutchy716 said:
I've been reading about bricked devices and want to downgrade from N to MM. I seen a thread in the 5X forum about it but want to be be sure before I attempt it with my 6P. Anyone have trouble downgrading? Can I just flash the factory image like usual? Thanks in advance.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hey so I actually bricked my first Nexus 6p doing this but I have been fine with my replacement. The Key is to update your twrp to 3.0.2-2 (make sure you do this). I then from Android 7 did a full backup in Twrp and then in the bootloader flashed the MTC20F factory image and it rebooted just fine. I guess in Twrp 3.0.2-1 there is an efs partition problem that is causing the bricks; my old bricked nexus 6p was on 3.0.2-1. So just please make sure you flash 3.0.2-2 twrp
ariefabuzaky said:
So your in PN MM with new nougat modem and bootloader ?
Click to expand...
Click to collapse
Yes, and everything is working fine.
ariefabuzaky said:
So your in PN MM with new nougat modem and bootloader ?
Click to expand...
Click to collapse
This is also how I downgraded mine. Also works on 3.0.2-0 if you were wondering.
rndll said:
This is also how I downgraded mine. Also works on 3.0.2-0 if you were wondering.
Click to expand...
Click to collapse
Yes. Already try it and everything is working fine.
What about downgrading a stock android 7.0 without TWRP and unlocked bootloader to MM?
Does anyone have a guidance for this, too?
Edit: Solved.
NedbuR said:
What about downgrading a stock android 7.0 without TWRP and unlocked bootloader to MM?
Does anyone have a guidance for this, too?
Edit: Solved.
Click to expand...
Click to collapse
Did you sideload 7.0 or upgrade from the beta program?
Sent from my Nexus 6P using Tapatalk

[Help] TWRP can't install stock rom and lost encryption. Phone no OS installed.

I was on beta 3 and decided to flash a new version of OOS. I flashed 9.0.11 -> reflashed TWRP and magisk but when I rebooted, it went straight back to TWRP.
I had to switch to a different slot and the phone booted to OOS beta 3 again. Tried to flash 9.0.11 and reflashed beta 3 again but the same thing happened.
Then i swiped everything except for USB storage and Internal Storage in TWRP and now the phone is without OS.
I rebooted to TWRP and now TWRP lost the encryption and I can't flash anything anymore.
Does anybody know how to recover from this?
I'm using the official TWRP build.
Dont panic just download a fast boot rom for version 9.0.11 and run it from fastboot using terminal. Then you will need to flash Magisk in order to have root access.
devam1995 said:
Dont panic just download a fast boot rom for version 9.0.11 and run it from fastboot using terminal. Then you will need to flash Magisk in order to have root access.
Click to expand...
Click to collapse
How do you do that using the terminal? I tried following this topic https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 but I got this error
https://imgur.com/wy1immW
TWRP still can't flash OOS
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
twistingthai said:
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
Click to expand...
Click to collapse
Flash a patched
Code:
boot.img
when I got the problem, I did that and it worked, booted me to system but if that doesn't work then you have to flash Magisk.
twistingthai said:
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
Click to expand...
Click to collapse
This phone has A/B partitions and is able to store a backup version of the OS so if a new installed version doesn't boot it will revert back to the old one.
When Flashing, you need to flash "BOTH" slots.
If you used the MSM tool to boot, you just booted and not flashed.
The MSM tool will flash your phone, restore the stock recovery and relic the bootloader. It will look like it came out of the box.
I don't know how to get you from wrapped around the axle except to tell you to run the MSM tool and let it wipe the phone and get you back to stock. You can then unlock the BL again and install TWRP, etc if you like.
twistingthai said:
I was on beta 3 and decided to flash a new version of OOS. I flashed 9.0.11 -> reflashed TWRP and magisk but when I rebooted, it went straight back to TWRP.
I had to switch to a different slot and the phone booted to OOS beta 3 again. Tried to flash 9.0.11 and reflashed beta 3 again but the same thing happened.
Then i swiped everything except for USB storage and Internal Storage in TWRP and now the phone is without OS.
I rebooted to TWRP and now TWRP lost the encryption and I can't flash anything anymore.
Does anybody know how to recover from this?
I'm using the official TWRP build.
Click to expand...
Click to collapse
You are booting into TWRP because you did not format your data partition. When flashing OOS, you need to not only wipe data, but also under the Wipe menu, select format data. It should prompt you to type "yes".
parker.stephens said:
You are booting into TWRP because you did not format your data partition. When flashing OOS, you need to not only wipe data, but also under the Wipe menu, select format data. It should prompt you to type "yes".
Click to expand...
Click to collapse
This! Thanks to you I was able to flash OOS again. But do I need to format the data everytime I flash OOS because it will be a pain . This is the first time I had to format data when updating OOS. Thanks alot.
twistingthai said:
This! Thanks to you I was able to flash OOS again. But do I need to format the data everytime I flash OOS because it will be a pain . This is the first time I had to format data when updating OOS. Thanks alot.
Click to expand...
Click to collapse
Glad to help. I was sick of having to put the device into Qualcomm mode just to get it to boot up, then I decided to try reformatting data and it worked.

Phone stuck at Decryption unsuccessful :crying:

I am stuck at encryption failed when I flash stock oreo rom. I tried formatting data using twrp and flashed no encryption file as well but nothing works.:crying::crying::crying:
I just want to use the stock oreo rom again with root.
Pls help:crying:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
jl10101 said:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
Click to expand...
Click to collapse
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Deadmeat03 said:
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Click to expand...
Click to collapse
Odd. If I had to guess anything, it would be that not all the partitions were flashed when going from Nougat to Oreo.
I once flash a Nougat ROM from an Oreo ROM and I had the same encryption issue and lost everything.
That was the last time I would trust myself again and not do a backup.
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Prowler_gr said:
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Click to expand...
Click to collapse
I tried that as well. With stock recovery is says data is corrupted and doesn't do anything. I think it might be a problem with patched lg up because when i use normal lg up to flash oreo it works. But I cant root then.
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
In the same boat as OP
scottyrick said:
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
Click to expand...
Click to collapse
Hi
Looking for a way to keep TWRP and root ... any help appreciated
I've got a US996 with the same issue as the op. I have the latest TWRP 3.3.1-0. The phone was working fine until I upgraded twrp but I might have done a mistake resetting phone outside of twrp.
I can still get back into twrp but I haven't been able to install zip files without getting that decryption unsuccessful message when booting to system.
When getting back into TWRP using hardware buttons sometimes there is a prompt asking "keep system read only?" which I never chose and swipe to allow modification. I think this happens after
I pull the battery after getting the decryption unsuccessful message. There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
...but if my phone is a us996 and is still
unlocked, would it matter if I did select it? Wouldn't I be able to reinstall twrp using adb again on a computer after Oreo is reinstalled?
To do Prowler_gr's suggestion which guide do I follow (sounds like I should do the second option)
"Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track... "
1-[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix) to use lgup
or this guide
2-Ultimate guide to unbrick LG V20(Only Variants with .KDZ)[No OS Firmware Update Loop]
Thank you for any guidance on this...
There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
Click to expand...
Click to collapse
Don't blame me if this goes wrong but I'm pretty much 100% certain that you mush press the rest button. This has happened to me a few times I'm sure. You won't loose twrp. Whatever resetting goes on in the background I don't think it's an actual Factory Reset.
Edit: Just to be clear you taking about a white screen with I think in dark blue or black text ENCRYPTION UNSUCCESSFUL and something like "reset phone" option directly under it, on the upper half of the screen?
Hi ezzony
Yes you are thinking of the right decryption unsuccessful page. I get it when booting to system
after installing Oreo and magisk 19 and having wiped everything (format data too). I will get the exact wording of it tonight
Thanks!
downgrade twrp i has same prob twrp 3.3.1 gives issues
ghet2rockuu said:
downgrade twrp i has same prob twrp 3.3.1 gives issues
Click to expand...
Click to collapse
Hi ghet2rockuu
I downgraded twrp and that got it working Thank You! see also Phoenix591 thread [Recovery][Unofficial for the moment]TWRP 3.3.1-0 : 2019-05-17 #625
Thank You !

Always boot in recovery mode after an update

Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Factory reset from TWRP?
yes
null0seven said:
yes
Click to expand...
Click to collapse
So, do you mean the classic Wipe data, cache and dalvik?
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
TWRP Users
1. Boot into TWRP and Flash the Latest Magisk Uninstaller
2. Flash the latest Full Oxygen OS Zip
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash the Latest Magisk to maintain root
6. Reboot System and Enjoy the latest firmware without any data loss
Click to expand...
Click to collapse
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk
Galeanatur said:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk
Click to expand...
Click to collapse
I don't have the OTA but the full rom, isn't simplier to update with the full ROM?
I think I'm going to try the null0seven's solution
null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Ok, I've done this and actually is even worse, the device started to boot in recovery again and TWRP doesn't recognize that the internal storage is crypted, so i can't even access the internal storage (it shows only strange folders), so, now I can't flash the nandroid backup anymore.
I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.
null0seven said:
I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.
Click to expand...
Click to collapse
So I've to Full wipe and then adb sideload the ROM? Because at the current state I can't even boot the device, it always starts in TWRP
Edit: I've also tried the blue_spark's version but nothing changed, TWRP can't recognize the encrypted storage
you can try this first.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
fuji97 said:
Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again
Click to expand...
Click to collapse
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.
ebproject said:
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.
Click to expand...
Click to collapse
No, I flashed the full ROM downloaded from the OnePlus server
Have you tried formatting data?
Cablespider said:
Format data.
Click to expand...
Click to collapse
So, full format data and flash rom + TWRP + Magisk?
fuji97 said:
No, I flashed the full ROM downloaded from the OnePlus server
Click to expand...
Click to collapse
You're best bet is to use the MSM tool
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread
fuji97 said:
Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread
Click to expand...
Click to collapse
Maybe it was a Magisk module that caused it. I removed pixel module from Magisk and it done the same to me.

After update to V11.0.4.0.QFJEUXM TWRP no longer available

Hi Guys,
yesterday the new update came out, great.
I of course immediately pulled the zip (source) and installed it with TWRP (source).
So far no problems.
After a while I realized that I no longer had root because the apps stopped working.
When I wanted to boot into the TWRP to reinstall Magisk, I unfortunately found that it was no longer available, but only stock recovery.
Well, I thought to myself and tried to reinstall TWRP (method-twrp-3.3.1-2-davinci-fix), which was fatal, because my cell phone only booted into the Fastboot.
Then I got my cell phone, set up again with the Fastboot method.
Now I'm back to 11.0.4.0 but unfortunately without TWRP and root.
Can someone please describe how I can get TWRP and root again on Android 10?
I am thankful for every help !!!
Same thing happening to me, no matter what I do, stock recovery keeps overwriting TWRP
Oh dear, that doesn't sound good.
I hope there will be a solution to the problem soon.
I don't want to do without TWRP and root.
I wanted to try it according to these instructions "https://miui.blog/redmi-k20/twrp-mi-9t-redmi-k20-vbmeta-mauronofrio/". But don't trust me, I'm afraid that it won't work and I can start all over again.
Flash official TWRP this morning with fastboot commands without problem.
1. reboot in fastboot mode
2. Flash recovery with this command "fastboot flash recovery yourrecovery.img"
3. Reboot in recovery with this command "fastboot boot yourrecovery.img"
Any problems here.
The fact that twrp is lost when flashing official rom (even thought twrp itself) is normal. You just have to reboot into bootloader and flash twrp again and it will be back.
Your problem here is that you are using an old and unofficial twrp build, that has problems on newer roms. Flash official twrp and you'll be fine
houbaba said:
Flash official TWRP this morning with fastboot commands without problem.
1. reboot in fastboot mode
2. Flash recovery with this command "fastboot flash recovery yourrecovery.img"
3. Reboot in recovery with this command "fastboot boot yourrecovery.img"
Any problems here.
Click to expand...
Click to collapse
Can u share the twrp file, im unnable to flash the one i have without causing a bootloop
hounter17 said:
Can u share the twrp file, im unnable to flash the one i have without causing a bootloop
Click to expand...
Click to collapse
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Oh sorry it works? I read somewhere that the original causes also bootloops :good:
Found something on a Russian website.
Обновление TWRP Recovery от LR.Team для устройств на Android 10
Does anyone dare to test this?
Here is the link to the TWRP for our Mi9t
> TWRP-3.3.1-1109-DX (полный комплект для установки) <
Check it out...
I finally got it
I did the following.
"V11.0.4.0.QFJEUXM" flashed in the TWRP and booted into the system, TWRP will be overwritten.
Now flashed TWRP "twrp-3.3.1-0-davinci.img" in Fastboot and booted into Recovery (TWRP).
To be on the safe side, I had the cell phone booted again into the TWRP in the TWRP.
Then I flashed Magisk "Magisk-v20.3.zip".
Booted cell phone into the system and everything works.
frank808 said:
I finally got it
I did the following.
"V11.0.4.0.QFJEUXM" flashed in the TWRP and booted into the system, TWRP will be overwritten.
Now flashed TWRP "twrp-3.3.1-0-davinci.img" in Fastboot and booted into Recovery (TWRP).
To be on the safe side, I had the cell phone booted again into the TWRP in the TWRP.
Then I flashed Magisk "Magisk-v20.3.zip".
Booted cell phone into the system and everything works.
Click to expand...
Click to collapse
Where did you get the twrp file from?
You can use OrangeFox Recovery if you want a TWRP that can survive after flashing MIUI ROMs or updates :
https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899
RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Ok, I am on global 11.0.4.0 (QFJMIXM) and I used this latest twrp-3.3.1-0-davinci.img and I can confirm its working without bootloop.
ShiningScias said:
You can use OrangeFox Recovery if you want a TWRP that can survive after flashing MIUI ROMs or updates :
https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899
Click to expand...
Click to collapse
To install TWRP, is it neccesary to wipe Data (or something else)?
And if Data must be wiped, does it mean that Data will no more be encrypted as originally by MIUI?
I have 11.0.4.0, rooted by Magisk (Magisk installed simply by patching and flashing boot.img, did not need TWRP for, did not wipe Data, etc) and I possibly want to have TWRP but don't want to loose encryption of Data, Widewine L1 and so
zgfg said:
To install TWRP, is it neccesary to wipe Data (or something else)?
And if Data must be wiped, does it mean that Data will no more be encrypted as originally by MIUI?
I have 11.0.4.0, rooted by Magisk (Magisk installed simply by patching and flashing boot.img, did not need TWRP for, did not wipe Data, etc) and I possibly want to have TWRP but don't want to loose encryption of Data, Widewine L1 and so
Click to expand...
Click to collapse
You don't need to wipe anything to install a custom Recovery (like TWRP).
TWRP can handle ROM encryption, you just need to install a correct TWRP, and version, for your current MIUI / Android version.
A custom Recovery doesn't change Widevine level.
And TWRP is useful in case of bootloop (because of an installed Magisk module, by example) or if you want to easily reinstall Magisk after ROM update.
RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Micdu70 said:
You don't need to wipe anything to install a custom Recovery (like TWRP).
TWRP can handle ROM encryption, you just need to install a correct TWRP, and version, for your current MIUI / Android version.
Click to expand...
Click to collapse
Ok thanks, so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Maybe I could test first by
fastboot boot twrp-3.3.1-0-davinci.img
zgfg said:
Ok thanks, so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Yes, it should work.
But I prefer OrangeFox Recovery.
zgfg said:
so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Maybe I could test first by
fastboot boot twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Micdu70 said:
Yes, it should work.
But I prefer OrangeFox Recovery.
Click to expand...
Click to collapse
Something is fishy. IMO, if that official TWRP is really ok for 11.0.4.0, then it should correctly boot by:
fastboot boot twrp-3.3.1-0-davinci.img
But phone rebooted into the dark.
TG, I didn't really flash with, so by long pressing Pow it rebooted to system.
Tried again, no avail
Edit:
Tried the same fastboot boot with
twrp-3.3.1-12-davinci-mauronofrio.img and also OrangeFox-R10.1_1-Stable-davinci.img (obtained by unzipping OrangeFox), but it also reboots to dark and I have to long press Pow to reboot to system
frank808 said:
Hi Guys,
yesterday the new update came out, great.
I of course immediately pulled the zip (source) and installed it with TWRP (source).
So far no problems.
After a while I realized that I no longer had root because the apps stopped working.
When I wanted to boot into the TWRP to reinstall Magisk, I unfortunately found that it was no longer available, but only stock recovery.
Well, I thought to myself and tried to reinstall TWRP (method-twrp-3.3.1-2-davinci-fix), which was fatal, because my cell phone only booted into the Fastboot.
Then I got my cell phone, set up again with the Fastboot method.
Now I'm back to 11.0.4.0 but unfortunately without TWRP and root.
Can someone please describe how I can get TWRP and root again on Android 10?
I am thankful for every help !!!
Click to expand...
Click to collapse
You can install twrp by All In One tool
You can find its thread here itself
I took the official TWRP. " Link "
Flashed in fastboat and then booted the phone with a key combination in TWRP.
With the Fastboot command it didn't work for me either, the cell phone remained black ...

Categories

Resources