Develop Bugs

How to "un-brick" from Recovery

Using "CWM-based Recovery v5.0.2.7 FULL".
I can't get my device to boot. I'm running the previous version of Energy's ROM (not most recent). However, I can get into recovery and fastboot easily.
All I have tried is to factory reset, wipe caches, and re-install Energy, but it still will not boot. It's gotten close - can see the splashscreen, but no further.
Battery is at 100.
What do I need to do get this baby going again!
P.S. The original problem is that I let the battery drain too low for it to fully boot.

Always read the OP for the ROM before you flash...
http://forum.xda-developers.com/showthread.php?t=1528024
NRGZ28 said:
...
How to Flash this ROM:
- Root your device
- Install TWRP custom recovery
- Install the downloaded ROM .zip found in post #3
- Make sure to do a Factory Reset / Wipe before installing ROM
Click to expand...
Click to collapse
The 3.0 Kernel discussions also mention the the symptoms you will encounter if you do not follow instructions...
http://forum.xda-developers.com/showthread.php?t=1591869
Hashcode said:
PLEASE use TWRP to flash this ROM. You will probably bootloop if you don't. If you experience a really long boot animation, double check your recovery (change if necessary) and try it again.
Click to expand...
Click to collapse

Oddly enough I used TWRP to flash. Somehow it reverted me back to CWM. I don't have a clue.
It's currently trying very hard to boot. Once I get there what should be my first steps?
If it doesn't boot, should I try and push TWRP through fastboot?
Edit: pushed TWRP (latest). Wiped and reinstalled. Still won't get past boot animation.
Can I transfer a new ROM file using fastboot or will I need to use 'fastboot update' to install a different ROM?
Should I try reverting to stock image?

Anyone having trouble installing TWRP on build NBD90W?

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.

DM Verity on Boot OnePlus 3 OB9

since OB8 i keep get message the DM-Verity isn't started like that, i don't know why this happened anyone can tell me what must i do? i already back to stock recovery from twrp. thanks

francise said:
since OB8 i keep get message the DM-Verity isn't started like that, i don't know why this happened anyone can tell me what must i do? i already back to stock recovery from twrp. thanks
Click to expand...
Click to collapse
same prob i also faced then
sideload OB9 full zip and booted to system. and again booted to stock recovery
sideload OB10 full zip and booted to system and after setup finished
booted to bootloader and flashed TWRP28 (fastboot flash) and booted to twrp recovery.
flashed SU2.79 and booted to system.
profit
no DM-Verity .

phanipk said:
same prob i also faced then
sideload OB9 full zip and booted to system. and again booted to stock recovery
sideload OB10 full zip and booted to system and after setup finished
booted to bootloader and flashed TWRP28 (fastboot flash) and booted to twrp recovery.
flashed SU2.79 and booted to system.
profit
no DM-Verity .
Click to expand...
Click to collapse
thanks after sideload ob10 i'm not face it again because i don't need supersu again i think

I cannot sideload zips. The phone is detected via adb devices. But when I try to flash via adb sideload zipname nothing happens. What might be the problem?

Does this work when i want a Locked Bootloader and the dm-verity thing away ?

ali.jujara said:
I cannot sideload zips. The phone is detected via adb devices. But when I try to flash via adb sideload zipname nothing happens. What might be the problem?
Click to expand...
Click to collapse
Linux or Windows? Try using admin / su rights
---------- Post added at 05:15 PM ---------- Previous post was at 05:08 PM ----------
francise said:
thanks after sideload ob10 i'm not face it again because i don't need supersu again i think
Click to expand...
Click to collapse
Okay. If you need superuser. You can try this :
1. Remove any decryption/ encryption.
2. Flash twrp ( hoping you're stock ).
3. Now it will give you dm-verity error.
4. Dirty Flash CB10.
This worked for me.
If not. You can flash stock recovery after twrp.
Then flash CB10. Then again twrp. This worked for me at CB9.
Hope it helps. Thanks!

My OnePlus 3 wont update

Hi,
I just got OnePlus 3, it is brand new but the guy who owned it has TWRP installed, I received notification that OnePlus3Oxygen_16_1706101914 System update was available, downloaded it and it wont install.
Once it starts installing it goes back to TWRP reboot page after the restart saying Android is updating. Then once I restart it is says the Update is available again. I tried to download the zip file through xda and selected it through TWRP not it says :
E:unknow command [log]
Updater process ended with ERROR 7
Error installing zip file' /sdcard/TWRP/
OnePlus3Oxygen_16_OTA_054_all_1706101914_1ab24f4be6e74def.zip.
I wiped cache/dalvik, re-downloaded the zip file and it still did not work.
Havent done this for awhile and have no idea what to do.
Thank you very much in advance.

I would recommend flashing TWRP again and then trying to install the update.
Personally I use Blu_spark TWRP as it has always worked on my end. When on the install section of TWRP there should be a button to install images. Install the img file to the recovery section, reboot back to the recovery and then try install the file.
Another way of flashing TWRP is via PC using ADB.
File here:
https://forum.xda-developers.com/devdb/project/dl/?id=25294
---------- Post added at 02:53 AM ---------- Previous post was at 02:52 AM ----------
Also, make sure you are downloading the FULL zip, not the OTA zip. full zip should be 1.3-1.4GB. Download the full zip here if you haven't got it.) http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.1.6/

You cannot flash ota from twrp. But if your bandwidth is limited, what you can do, is to flash stock recovery, then update with ota, then flash back twrp

Thank you very much for your responses. Sorry for the delay had no internet access.
Downloaded both files, TWRP and Oxygen zip, still the same error 7. Installed the drivers successfully. Have no idea what else to do.

When I am in TWRP, I go down to the folder and select the zip that I downloaded from oneplus site but it doesnt say install it says flash.
FriendWithin said:
I would recommend flashing TWRP again and then trying to install the update.
Personally I use Blu_spark TWRP as it has always worked on my end. When on the install section of TWRP there should be a button to install images. Install the img file to the recovery section, reboot back to the recovery and then try install the file.
Another way of flashing TWRP is via PC using ADB.
File here:
https://forum.xda-developers.com/devdb/project/dl/?id=25294
---------- Post added at 02:53 AM ---------- Previous post was at 02:52 AM ----------
Also, make sure you are downloading the FULL zip, not the OTA zip. full zip should be 1.3-1.4GB. Download the full zip here if you haven't got it.) http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.1.6/
Click to expand...
Click to collapse

Thank you very much all, finally was able to flash everything.
Appreciate all your help.

Updating to Android O / Nandroid Restore back to Android N?

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.