Hello everyone.
Currently I'm running OxygenOS 9.0.9 with Franco Kernel, rooted with Magisk and with the official TWRP recovery.
In preparation for the release of stable OxygenOS 10 I decided I wanted to go fully stock but how can I do that?
I've found some OOS recoveries but they seem kind of old.
And if possible, I'd like to know the steps needed to go back to stock
Like, what partitions to wipe, in which order do I flash stuff, *what* stuff should I flash in the first place, all of that
Thanks in advance
Hiya,
2 ways you can achieve this.
01. Full clean, with locked bootloader (internal wiped)
02. Full clean with unlocked bootloader (internal may get wiped partially)
Or else, using Magisk Uninstaller, but that will not be clean wipe. However, as you are already on stock rom, you will not face issues to just unroot via magisk uninstaller. Please ensure to use the latest uninstaller or the uninstaller which was available with the release of magisk.
01. Install Latest OOS (9.0.11 - for Pie, OB2 for Android Q).
02. To install you can use local upgrade while booted, or any TWRP, like codeworkx/bluspark and install from recovery.
N.B.: From Pie to Android Q, you will have to do full clean wipe, as it anyways will get wiped out.
If you want to lock bootloader, the system will automatically format data, and you will lose internal storage data.
Let me know if this explains a bit, and rest I can assist per your further query.
Related
I decided to upgrade to the latest Oxygen OS yesterday.
I had root, and TWRP Custom Recovery(3.2.1-0) and unlocked bootloader.
I unrooted, relocked bootloader and installed the latest full zip from oxygen os.
Then I unlocked bootloader and rerooted again and installed TWRP Recovery again.
Everything was working fine.
After everything was installed/restored I figured it would be good to take a nandroid backup, I took one and on reboot I get a bootloop to recovery.
I was able to reproduce this twice.
I think this has to do with something with fingerprint setup.
I'm a bit a loss on how to fix this without going trough a full wipe again.
I already tried wiping cache and dalvik, but no solution.
i had the same kind of issue. were you decrypted before?
If you are decrypted you need to flash the no verify zip. If you are encrypted try a dirty flash of OOS and Magisk. If you aren't using the most up to date version of Magisk that could have caused your problem. I've had no issues with Nandroid backup problems caused by fingerprint or pin security when using Codeworks or Blu Spark TWRP.
I was encrypted before and I am still encrypted.
I don't understand that taking a backup renders the phone unusable.
Restore fails with createTarFork() process ended with ERROR=255.
I made a clean flash(and locked bootloader) as it is a requirement for the latest OOS due to the upgrade to oreo.
Would it be possible to do a dirty flash with the full zip (I used: OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5.zip) and unlocked bootloader?
Secondly, I think I will try one of the suggested recoveries and see what it brings.
Hi everyone,
I have been happy with the Marshmellow version the OS since I bought my phone when it came out (Unlocked, Encrypted). I have performed one update since I had the phone. Today, after seeing the latest posts after not being on this site for a year, I decided to make the move to upgrade to OOS 5.1.0!! Why not, nothing else going on this weekend. I upgrade TWRP to 3.2.1-1, I make a full backup, I follow the upgrade instructions... it fails with the continuous spinning balls on reboot. I Do some research... oh, it is "challenging" to upgrade but possible. No big deal, I will just restore my backup and try again at some other time. My backup restore fails Error 255, I try the fixeS I found such as unmounting data... No Luck). Can not restore the data partition. I guess I should have decrypted everything prior to backing up based on what I read later.
I at least backed up my SD card using adb prior to all this, so I decided to just reinstall ANY OS to get my phone running again for tonight. Well I have not had much luck. I downgraded TWRP to 3.2.1-0, I have tried installing:
OnePlus5Oxygen_23_OTA_033_all_1804110400_eb1766 - Originally installed with not errors but phone reboots back into TWRP after a failed 1st reboot. (I do get a "failed to mount /vendor")
lineage-15.1-20180423-nightly-cheeseburger-signed with Gapps (Gapps failed with I think a error 7)
I was messing with the data partition, wiped, formatted, etc. I am sure this is some of the issues. One other thing is that TWRP always boots to the "keep System Read only" I find this strange and had never seen before. I select to allow modification, but it seems like nothing changes on reboot.
At this point I would just like to get a stock OS image on the phone. IS there something I am missing?
https://forum.xda-developers.com/oneplus-5/how-to/guide-mega-unbrick-guide-hard-bricked-t3698370
Sounds good, let me give it a try.
I've been thru this already. Here is the simplest way to get your 1+5 back to work, while having the latest LineageOS installed. It takes a bit of time and patience, but it works:
Using fastboot, reinstall TWRP 3.2.1-1 (or newer, if any)
Wipe all partitions, namely Dalvik/ART cache, Cache, System, Data and Internal storage
Sideload the latest OOS (version 5.10 or later, if any) with Android 8.1. This version will be OK for LineageOS 15.1 and you will no longer have that stupid error 7 when installing LOS 15.1
If OOS boots into recovery and asks for passwords or PIN or schema ... click on the "forgotten" link. OOS Recovery will then remove encryption and wipe out any data that was left.
Reboot phone, and start OOS session. Do not use any security stuff (PIN or schema or whatever) that would encrypt the phone. At least not now - If necessary, you will add it at the end of this whole process.
Once OOS is working, reboot to Bootloader. Since TWRP has been erased with OOS default recovery, you will have to reinstall it.
From TWRP, wipe Dalvik/ART cache, Cache, and Data partitions. This time, do not touch System or Internal storage
Sideload Lineage OS latest version. If you need to use Google Apps (e.g. Open Gapps), sideload it now before rebooting
Reboot (you might have to reboot twice, don't worry about that).
Once booted in LineageOS, do whatever you like - add accounts, root phone, etc.
Enjoy! (you may want to shout "Vive la France!", well ... don't hesitate!)
Sorry for my poor English. If anything here is unclear to you, please let me know.
I Have no idea what happened. I came home to start working on my phone, powered it up, and boom I have Android 8.1. Ok, Whatever...
Now I wonder if I should go for lineage or not.
kuhnto said:
Now I wonder if I should go for lineage or not.
Click to expand...
Click to collapse
It all depends on how important privacy is to you. If you don't care, then stick to the original OnePlus firmware. If you do, then switch to LineageOS.
Ok have a ZTE Axon 7 can't flash any thing because of it instantly encryption and I get recovery and then game over any one have a Cure for this......... thanks in advance.
You have to do a factory wipe, to remove encryption. Then when setting up the phone again when it prompts you to set a security pin or finger sprints skip that part.
chairmanmarv said:
You have to do a factory wipe, to remove encryption. Then when setting up the phone again when it prompts you to set a security pin or finger sprints skip that part.
Click to expand...
Click to collapse
Tried that and it didn't work.....it doesn't matter what I flash stock ROMs tell me my password is correct but memory is corrupt and need to be wiped and when I flash a custom ROM it doesn't boot just two flashes of the led and that's it.
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
chairmanmarv said:
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Click to expand...
Click to collapse
Just found out that the phone has bricked itself it would play any video or sound so did a hard reset now just getting a constant boot loop trying to get it in to EDL as we speak.....got EDL flashed stock ROM in miflasher now stuck on splash screen.......been on the splash screen for 10 minutes now.......
chairmanmarv said:
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Click to expand...
Click to collapse
Ok now got the thing back was able to reunlock the bootloader and installed recovery flashed candy rom with one issue could not mount system so now just flashed Oreo stock rom so all good again....... thanks for the help
The stock ROM encrypts by default, and formatting data partition in twrp is the only way to remove it. But to prevent the encryption before it happens, you have a few options:
1. If you dont plan to root, flash @jcadduono's no verity opt encrypt zip (Google it)
2. Magisk and SuperSU can optionally disable encryption before it happens. Magisk Manager has a config option if you're installing from the app. You can use Aroma SuperSU config if SuperSU is your root method of choice.
Hope that helped!
I would like to note that AOSP/Lineage/CM-based ROMs dont encrypt by default. though Im sure it could be enabled if you wanted to. This seems to be unique to the stock ROMs, mainly because Google insists that phone OEMs should go for higher security by enabling encryption as the default.
AnonVendetta said:
The stock ROM encrypts by default, and formatting data partition in twrp is the only way to remove it. But to prevent the encryption before it happens, you have a few options:
1. If you dont plan to root, flash @jcadduono's no verity opt encrypt zip (Google it)
2. Magisk and SuperSU can optionally disable encryption before it happens. Magisk Manager has a config option if you're installing from the app. You can use Aroma SuperSU config if SuperSU is your root method of choice.
Hope that helped!
I would like to note that AOSP/Lineage/CM-based ROMs dont encrypt by default. though Im sure it could be enabled if you wanted to. This seems to be unique to the stock ROMs, mainly because Google insists that phone OEMs should go for higher security by enabling encryption as the default.
Click to expand...
Click to collapse
Yep this is the problem I am having now....... can't find much info about it.
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
DrCow said:
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
Click to expand...
Click to collapse
Hi. Have you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Let us know about your phone's recovery, which magisk version you used, If you're using TWRP as your recovery let us know your TWRP recovery's version. Also did you dirty flashed your OTA or clean?
Ebeninyo said:
Hi. Have you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Let us know about your phone's recovery, which magisk version you used, If you're using TWRP as your recovery let us know your TWRP recovery's version. Also did you dirty flashed your OTA or clean?
Click to expand...
Click to collapse
Im not sure what instructions are you talking about but this isnt the first time i root my device.
Im using TWRP 3.2.1 since the last version giving me a little problems when trying to root. Im using the last magisk version.
About dirty or clean.. I first tried just flashing nornal from the OTA and then after it worked (no wifi or LTE) i tried to do factory reset and root again
Sent from my ONEPLUS A5000 using Tapatalk
DrCow said:
Im not sure what instructions are you talking about but this isnt the first time i root my device.
Im using TWRP 3.2.1 since the last version giving me a little problems when trying to root. Im using the last magisk version.
About dirty or clean.. I first tried just flashing nornal from the OTA and then after it worked (no wifi or LTE) i tried to do factory reset and root again
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
Try flashing this first https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
Download ota again and clean flash it from the recovery.
It might be because your TWRP isn't compatible to Pie. Most people here including me tried codework's TWRP and it solved any of our issues.
Edit: after flashing magisk reboot your phone once more. (i didn't knew it before. I booted into my os and checked magisk app to see if root was successfull but it didn't show me. I wiped everything down and flashed magisk again. Same thing happened. Rebooted my phone and saw root was on )
Ebeninyo said:
Try flashing this first https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
Download ota again and clean flash it from the recovery.
It might be because your TWRP isn't compatible to Pie. Most people here including me tried codework's TWRP and it solved any of our issues.
Click to expand...
Click to collapse
Will try it on the weekend.. I had some problems restoring my previous backup so i rather be home when i do it
Sent from my ONEPLUS A5000 using Tapatalk
Edit:
Wait the wifi and the LTE problem can be caused by the recovery?
DrCow said:
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
Click to expand...
Click to collapse
I would suggest do a complete clean install (wiping everything but USB OTG) and making sure you got the latest TWRP from blu_spark or codeworkx. Also flash it following these instructions:
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
- Download the full ROM zip from the downloads section above
- Transfer the zip to the root of your device's internal storage
- Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
- Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
- Flash Magisk Uninstaller (recommended)
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
- From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
- Flash the latest stable Magisk in case you want to root
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
- Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
- Reboot
Full instructions and downloads from -> https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
i ended up giving up..
im trying to do a clean flash
but the moment i flash the recovery and trying to go into the recovery
boom
black screen
i tried it multiple times both with codework 3.2.3 and blu_spark
Edit: Flash universal codework 3.2.1 does get me into recovery
im gonna restore my backup...for now
Z-Blade said:
I would suggest do a complete clean install (wiping everything but USB OTG) and making sure you got the latest TWRP from blu_spark or codeworkx. Also flash it following these instructions:
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
- Download the full ROM zip from the downloads section above
- Transfer the zip to the root of your device's internal storage
- Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
- Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
- Flash Magisk Uninstaller (recommended)
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
- From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
- Flash the latest stable Magisk in case you want to root
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
- Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
- Reboot
Full instructions and downloads from -> https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Click to expand...
Click to collapse
For the "Clean" Install given that OnePlus5 doesn't have external microSD storage, will ALL data (photos, documents etc) on the phone be erased in Step 6 above?
lorrdvader said:
For the "Clean" Install given that OnePlus5 doesn't have external microSD storage, will ALL data (photos, documents etc) on the phone be erased in Step 6 above?
Click to expand...
Click to collapse
No, it wont because all of that is stored in the Internal Storage. So as long as you don't check that, you will still have your data. However, I personally wipe everything including the internal storage when moving to a new rom. I prefer to start with a complete clean slate but it is optional.
Hi.
I am new to the Nexus 6p.
I want to install Magisk and backup my ROM via TWRP.
I am running stock Oreo 8.1.0 with a password and fingerprint.
I have just unlocked and installed TWRP 3.3.3-1. When I first loaded TWRP it asked me to decrypt data, but I just cancelled it as I thought it wasn't needed. I take it this is wrong?
I have now tried to go back into twrp but I get the Android on its back saying 'no data'. So the twrp flash never stuck.
I am under some confusion whether I need to format userdata or not. The guides I am following are old and don't mention Oreo only Developer preview N. I would prefer not to but if it needs doing it needs doing.
Would removing my fingerprint before flashing twrp help?
Thanks.
Warren_Orange said:
Hi.
I am new to the Nexus 6p.
I want to install Magisk and backup my ROM via TWRP.
I am running stock Oreo 8.1.0 with a password and fingerprint.
I have just unlocked and installed TWRP 3.3.3-1. When I first loaded TWRP it asked me to decrypt data, but I just cancelled it as I thought it wasn't needed. I take it this is wrong?
I have now tried to go back into twrp but I get the Android on its back saying 'no data'. So the twrp flash never stuck.
I am under some confusion whether I need to format userdata or not. The guides I am following are old and don't mention Oreo only Developer preview N. I would prefer not to but if it needs doing it needs doing.
Would removing my fingerprint before flashing twrp help?
Thanks.
Click to expand...
Click to collapse
You need to boot back into twrp and format data the reboot back to recovery again and advanced wipe system data cache dalvik/art and internal storage if necessary, then flash a custom ROM .