Related
So I downgraded my Oneplus 3 from 3.5.2 to 3.2.6 and this was kind of a painful process, so I decided to share my experience with you.
If you follow this guide you will successfully downgrade from the latest Community Build to the newly released stable.
Note: Just because this worked for me, doesn't mean that it will work for you! Use this guide on your own risk and always use backups!
You'll need:
- Oneplus with OOS 3.5.2 and modified TWRP
- OxygenOS 3.2.6 Full ROM
- Latest official TWRP
- AndroidSDKSlim (needs Oneplus 3 USB drivers installed)
- SuperSU 2.78 SR1
- Xposed Framework (optional)
- Debloat Script (optional)
Downgrade:
Before you start, please create a COMPLETE backup of all your data.
You will factory reset your phone during the process.
1. Copy OOS 3.2.6 Full ROM, SuperSU, Xposed, Debloat Script to your Oneplus
2. Flash modified TWRP if you haven't already
3. Boot into modified TWRP
4. Select Wipe -> Advanced Wipe -> Select all but internal storage -> Swipe to Wipe
5. Install OOS 3.2.6 Full ROM
6. Reboot into system and use the installation wizard to setup your phone (do not setup fingerprints, or any device PIN)
7. Reboot into bootloader
8. Connect your phone to a PC/Notebook
9. Extract AndroidSDKSlim to your Desktop and copy twrp-3.0.2-1-oneplus3.img into \AndroidSDKSlim\android-sdk-windows\platform-tools
10. Run CMD with admin rights and navigate to \AndroidSDKSlim\android-sdk-windows\platform-tools
11. Run "fastboot flash recovery twrp-3.0.2-1-oneplus3.img" to revert to official TWRP recovery
12. Disconnect your phone and boot into recovery
13. Dirty flash OOS 3.2.6 again (this might sound stupid but it's mandatory)
14. Still in recovery, flash SuperSU, Xposed and Debloat Script
15. Wipe Dalvik & Cache
16. Reboot into system and setup your phone
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
darkbash said:
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
Click to expand...
Click to collapse
You're welcome.
Unfortunately, I can't provide guides for procedures I never went through.
But I asume that you could just flash any Custom ROM after you completely wiped your phone in step 4. So instead of flashing OOS 3.2.6 afterwards, just flash a custom ROM. Be sure that you have all zips you need on your internal storage and a backup to revert back to, if anything goes wrong. Otherwise you will have to use ADB sideload to install a ROM.
Ok, so I have a Modified TWRP installed already. Question is If I want to flash other ROMS after wiping system,dalvik/cache,data etc. Do I have to Flash official TWRP first followed by firmware,ROM, etc?
or firmware first then ROM and lastly official TWRP?
it's quite confusing.
I made a mistake and I installed the modified recovery installed the 3.5.2 rom and before booting I decided to restore my nand backup so I flashed the official twrp recovery and now I can't go to recovery anymore and the phone doesn't boot.
I imagine I have to sideload the modified twrp again but how do I do that? How do I reboot to bootloader ?
This is the only sign of life
gigeaky said:
I made a mistake and I installed the modified recovery installed the 3.5.2 rom and before booting I decided to restore my nand backup so I flashed the official twrp recovery and now I can't go to recovery anymore and the phone doesn't boot.
I imagine I have to sideload the modified twrp again but how do I do that? How do I reboot to bootloader ?
This is the only sign of life
Click to expand...
Click to collapse
Flash modified TWRP, and the recovery will return. then, follow the guide. it happened to me too.
darkbash said:
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
Click to expand...
Click to collapse
First flash modified TWRP than install official 3.2.4 than flash CM ROM or custom ROM
uniQ191 said:
So I downgraded my Oneplus 3 from 3.5.2 to 3.2.6 and this was kind of a painful process, so I decided to share my experience with you.
If you follow this guide you will successfully downgrade from the latest Community Build to the newly released stable.
Note: Just because this worked for me, doesn't mean that it will work for you! Use this guide on your own risk and always use backups!
You'll need:
- Oneplus with OOS 3.5.2 and modified TWRP
- OxygenOS 3.2.6 Full ROM
- Latest official TWRP
- AndroidSDKSlim (needs Oneplus 3 USB drivers installed)
- SuperSU 2.78 SR1
- Xposed Framework (optional)
- Debloat Script (optional)
Downgrade:
Before you start, please create a COMPLETE backup of all your data.
You will factory reset your phone during the process.
1. Copy OOS 3.2.6 Full ROM, SuperSU, Xposed, Debloat Script to your Oneplus
2. Flash modified TWRP if you haven't already
3. Boot into modified TWRP
4. Select Wipe -> Advanced Wipe -> Select all but internal storage -> Swipe to Wipe
5. Install OOS 3.2.6 Full ROM
6. Reboot into system and use the installation wizard to setup your phone (do not setup fingerprints, or any device PIN)
7. Reboot into bootloader
8. Connect your phone to a PC/Notebook
9. Extract AndroidSDKSlim to your Desktop and copy twrp-3.0.2-1-oneplus3.img into \AndroidSDKSlim\android-sdk-windows\platform-tools
10. Run CMD with admin rights and navigate to \AndroidSDKSlim\android-sdk-windows\platform-tools
11. Run "fastboot flash recovery twrp-3.0.2-1-oneplus3.img" to revert to official TWRP recovery
12. Disconnect your phone and boot into recovery
13. Dirty flash OOS 3.2.6 again (this might sound stupid but it's mandatory)
14. Still in recovery, flash SuperSU, Xposed and Debloat Script
15. Wipe Dalvik & Cache
16. Reboot into system and setup your phone
Click to expand...
Click to collapse
worked like magic. Thankyou for this education. it didnt work when i followed other folks. Much appreciated.
So it seems I have booted with 3.5.2 and modified recovery. Now my question is: can I reboot in recovery at step 7 and install the original twrp recovery? Or can I use flashify? As I don't have access to a pc
I did ok but cant use adaway do you have a fix for it?
Enviado do meu ONEPLUS A3003 através de Tapatalk
I'm trying to return to 3.2.6 after trying 3.5.2.
However, after flashing and booting 3.2.6, I boot into fastboot mode and the official TWRP refuses to flash. It reports that it's failed and then I'm left with no recovery until I reflash the modified TWRP.
I could try restoring my Nandroid backup of 3.2.6 with the modified TWRP, but I'd prefer to return to the official TWRP before doing this.
Any suggestions?
Edit: Fixed it. I downloaded the official TWRP again and it flashed. The first download must have been corrupted.
I followed a different method and successfully downgraded today to a former nandroid. I was rooted without xposed.
3.2.6 to 3.5.2 dirty flash
- installed modded twrp
- performed backup on 3.2.6
- installed modded 3.5.2 (the only that flashes in twrp)
- installed root SR1
- wiped caches only
- reboot
3.5.2 to 3.2.6 restore
- downloaded 3.2.6
- boot to modded twrp, wipe both caches, data, system
- flashed 3.2.6 stock and root SR1
- restored 3.2.6
- wiped caches
- reboot
- enjoying my LTE again
Without first installing stock, after a restore my phone was boot locking right after the oneplus white logo (capacitive buttons would light up, but it would not boot to red logo). Had to press vol down and power to force it to boot menu to select recovery and get back to twrp
Hope this helps someone, it's a bit easier than swapping twrps and no need to boot up/flash 3.2.x twice.
So if I am on the CB and want to go back to 3.2.6
I can flash 3.2.6 with the modded TWRP
Then flash Official TWRP and boot?
If I have official recovery, no root, and locked bootloader, can I downgrade from 3.5.3 to 3.2.6 without any problems, just by sideloading the zip in ADB? Thankss
popab said:
If I have official recovery, no root, and locked bootloader, can I downgrade from 3.5.3 to 3.2.6 without any problems, just by sideloading the zip in ADB? Thankss
Click to expand...
Click to collapse
i would also like to know this please
bigup7 said:
i would also like to know this please
Click to expand...
Click to collapse
I did it and it does work perfectly. Just make sure to wipe data from recovery after flashing.
I was on Comunity Build v.3.5.4. I want it back FreeDom v.1.6.
I did:
1. Flash Twrp-3.0.2-19-oneplus3.img.zip. Somebody sugested original twrp 3.0.2.1 from twrp site. For me did NOT work. Phone not booting in recovery with 3021.
2. Advanced wipe. Wipe dalvik cache/cache/system/data
3. Flash Freedom v.1.6. Clean Flash it's safer & better.
Done. System works. Recovery works.
null0seven said:
I was on Comunity Build v.3.5.4. I want it back FreeDom v.1.6.
I did:
1. Flash Twrp-3.0.2-19-oneplus3.img.zip. Somebody sugested original twrp 3.0.2.1 from twrp site. For me did NOT work. Phone not booting in recovery with 3021.
2. Advanced wipe. Wipe dalvik cache/cache/system/data
3. Flash Freedom v.1.6. Clean Flash it's safer & better.
Done. System works. Recovery works.
Click to expand...
Click to collapse
I am on CB Freddom os
I want to go back either to stock or to op3lite.
I cant reboot to recovery.
But adb works yet.
What to do plz suggest.
Sent from my ONEPLUS A3003 using Tapatalk
1. If system don't boot. Reboot to fastboot.
- Flash recovery.img. If PC don't see youre phone option 2.
2. If system boots, open phone like normal.
- Extract recovery img. Put it on the TWRP file on phone sd card.
- Download Flashify from play. Open it, flash img of recovery. Open recovery to chech if it works.
Try with both recovery (3.0.2.0 or modified 3.0.2.-19). One of those will work.
Im getting system partition has unexpected contents after OTA update after installing step 5 ????
Hello out there,
my problem is a bit annoying. Everything is fine if I use my OP3T with Oxygen (4.0.3) and TWRP (3.0.3-1). But I want to use LineageOS with TWRP and cant, because my TWRP isnt working after flashing lineage.
"Normal"-Setup:
- TWRP 3.0.3-1
- Oxygen 4.0.2 or 4.0.3 (doesn't matter)
- supersu 2.79
- Encrypted Device
"Lineage"-Setup:
- TWRP 3.0.3-1
- lineageOS (lineage-14.1-20170214-nightly-oneplus3-signed.zip OR lineage-14.1-20170208-nightly-oneplus3-signed.zip - tried both, doesnt matter)
- supersu 2.79
- openGApps for 7.1 nano
- Encrypted Device
My Problem is, that I can boot up lineage and use it, but if I reboot into my TWRP to flash something or make some Backups, it asks for my encryption-passphrase, it says it is okay and boots into the twrp main-windows. After that I can't touch anything (stuck in mainmenu) and after a few seconds it results into a black screen (plus white LED) and I am forced to reboot the device. After that reboot I have to reconfigure lineage (seems to loose data).
Does anyone have an idea how to fix this annoying "bug"?
Thank you very much!
Atomique
EDIT: I found that Thread after searching for a issue like that in the lineageOS official Thread - I will try this and report! - Thank you! https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
I had the exact same problem when I hab LineageOS installed! It would always lose all its data. After flashing and reflashing a hundred times, I ended up reverting my OP3T back to stock using a OnePlus forum guide (I'm a new user, so I can't post the link). I am now back to OOS 4.0.3 but can't even get SuperSU to work. Whenever I flash it (with or without the dm-verity fix) the phone is stuck booting forever.
I found the post you linked to aswell but haven't tried flashing LineageOS using the new TWRP. But I can tell that the new version doesn't help rooting OOS...
Did you have any luck flashing LineageOS by now?
Edit: With the newest Lineage Version I always get an error when trying to flash it. Do you have the same problem? The nightly from two weeks ago seems to work better.
Use latest TWRP 3.0.4.1
nitinvaid said:
Use latest TWRP 3.0.4.1
Click to expand...
Click to collapse
That's what I'm doing... Could the dm-verity be a problem? There are two versions, one with opt and one with force in the name.
Thank you for your replies! The link (TWRP 3.0.4-1) worked like a charme!
@Tafelbomber: I would recommend you to start from scratch. But please be warned: you will loose your data! Make a backup first!
1. Delete everything with fastboot -w
2. Flash the recovery noted in my first post with fastboot flash recovery <twrp-filename.img>
3. Optional: Restart into the TWRP and flash the OOS 4.0.3 to make sure that you have a clean OS installed befor flashing lineage
4. Flash lineage OS + additional ZIPs (like supersu, betterbatterystats, Gapps etc)
5. Clean Dalvik and Cache!
6. Reboot and have fun. --> Sometimes you get problems with the encryption chain (Red Error --> in my case the fastboot -w did it for me)
Good luck - I will close this thread - thanks again for your help!
Atomique
EDIT: I want to close this thread, but I don't know how.
Hello,
I've installed twrp 3.4.0.1 via fastboot, but after I select yes when i'm asked about erasing my data, the phone just boot up normally without deleting any of my data, but does not enter twrp either. Tried 3.4.0.0 too, no luck. Only 3.3.1.0 worked, but when I try to backup it says something like 'can't mount system partition' and some other errors. I think that version is too old for my rom, so I'm afraid to use it for backup/flash. My phone is LG G6 H870, Android 9, software version V30b. The phone is not rooted, the bootloader is unlocked. Tried to erase cache partition and install twrp 3.4.01 again, didn't work. I can't install Skyhawk or Orangefox becuase I can't use twrp.
Is anybody facing this problem too?
Thanks!
Bootloader unlocked?
Mendoo said:
Bootloader unlocked?
Click to expand...
Click to collapse
Yes
Thelock1 said:
Hello,
I've installed twrp 3.4.0.1 via fastboot, but after I select yes when i'm asked about erasing my data, the phone just boot up normally. Tried 3.4.0.0 too, no luck. Only 3.3.1.0 worked, but when I try to backup it says something like 'can't mount system partition', I think that version is too old for my rom. My phone is LG G6 H870, Android 9, software version V30b. My phone is not rooted.
Is anybody facing this problem too?
Thanks!
Click to expand...
Click to collapse
HI You need to use OrangeFox recovery or SkyHawk. If you plan to go to 10, then you need SkyHawk. And I think SkyHawk is maintained but OrangeFox not.
Links:
SkyHawk https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/H870/
OrangeFox https://forum.xda-developers.com/lg-g6/development/recovery-orangefox-recovery-project-t3943594
jis251 said:
HI You need to use OrangeFox recovery or SkyHawk. If you plan to go to 10, then you need SkyHawk. And I think SkyHawk is maintained but OrangeFox not.
Links:
SkyHawk https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/H870/
OrangeFox https://forum.xda-developers.com/lg-g6/development/recovery-orangefox-recovery-project-t3943594
Click to expand...
Click to collapse
So can I install SkyHawk via fastboot over stock recovery without installing twrp beforehand? I see there are multiple files in the shyhawk zip, should I only extract the recovery img and install it via fastboot? I'm kinda new to this, thanks!
Thelock1 said:
So can I install SkyHawk via fastboot over stock recovery without installing twrp beforehand? I see there are multiple files in the shyhawk zip, should I only extract the recovery img and install it via fastboot? I'm kinda new to this, thanks!
Click to expand...
Click to collapse
HI. It is made to flash in TWRP (same as OrangFox) So I really don't know if that recovery.img flashing through Fastboot works. Never tried, sorry.
Maybe someone knows though.
jis251 said:
HI. It is made to flash in TWRP (same as OrangFox) So I really don't know if that recovery.img flashing through Fastboot works. Never tried, sorry.
Maybe someone knows though.
Click to expand...
Click to collapse
Ok, thanks, I'll try to find a solution, or maybe I'll just wait for the next version of twrp.
You should try installing the recovery and immediately installing any custom rom, when i flashed twrp the first time i had to do it several times cause somehow it got "erased" every time i noot the stock OS.
Ig you don't want to install a custom rom try right after installing twrp and on the fastboot screen to reboot to recovery with (Volume - ) button and power.
I think the idea is not letting the Stock os boot
Also that error. i have the same problem, the only moment it doesn't appear is when you wipe all data with the "Format Data" option inside "Wipe" menu in twrp.
After you boot to the OS once and go back to recovery it will come again everytime you flash something.
Not sure if its a problem or not, because i've dirty installed some updates and also installed gapps and magisk even with that error.
Im currently in A10 using Havoc and NikGapps.
TWRP 3.2.3-0
AlejandroMota said:
You should try installing the recovery and immediately installing any custom rom, when i flashed twrp the first time i had to do it several times cause somehow it got "erased" every time i noot the stock OS.
Ig you don't want to install a custom rom try right after installing twrp and on the fastboot screen to reboot to recovery with (Volume - ) button and power.
I think the idea is not letting the Stock os boot
Also that error. i have the same problem, the only moment it doesn't appear is when you wipe all data with the "Format Data" option inside "Wipe" menu in twrp.
After you boot to the OS once and go back to recovery it will come again everytime you flash something.
Not sure if its a problem or not, because i've dirty installed some updates and also installed gapps and magisk even with that error.
Im currently in A10 using Havoc and NikGapps.
TWRP 3.2.3-0
Click to expand...
Click to collapse
Yes, I know I have to install twrp again every time I let the stock rom boot, but the only version of twrp working is 3.2.3 and I think that was released before the G6 received official Android 9 update, so that's why I'm not very confident using it. I've tried to enter recovery immediately after I've installed it, so I don't think that's the problem.
I have the same problem on the LG G6 H870. I won't get to TWRP. I tried several versions of TWRP and nothing.
Edit.
This twrp is functional:
https://androidfilehost.com/?w=files&flid=289997
After installation using fastboot, restart directly to twrp using power+vol. down.
Finally i've successfully flashed Skyhawk using TWRP 3.3.1, so thanks everyone for advice!
Still couldn't make official TWRP 3.4.0/3.4.0.1 work.
Update TWRP 3.1 to 3.4 problem
Thelock1 said:
Finally i've successfully flashed Skyhawk using TWRP 3.3.1, so thanks everyone for advice!
Still couldn't make official TWRP 3.4.0/3.4.0.1 work.
Click to expand...
Click to collapse
Hi, I don't know if this goes here, I hope you can help me, I update twrp from version 3.1 to 3.4 and now I can't access twrp, how can I fix it?
Hello again, I answer myself, and if it helps someone else, using adb fastboot with twrp 3.2 Melina solves it and twrp works perfectly again.
Hi,
I have the following problem.
I was able to install the custom ROM properly on my Mi9t pro. Unfortunately my Orangefox Recovery was deleted After the installation.
If I want to install Magisk now, I have to reflash the recovery first.
Do you have any idea why the recovery is deleted? Is there a way to prevent that?
Thanks in advance.
der_andi01 said:
Hi,
I have the following problem.
I was able to install the custom ROM properly on my Mi9t pro. Unfortunately my Orangefox Recovery was deleted After the installation.
If I want to install Magisk now, I have to reflash the recovery first.
Do you have any idea why the recovery is deleted? Is there a way to prevent that?
Thanks in advance.
Click to expand...
Click to collapse
Your (custom) Recovery was really deleted?
Or replaced by stock Recovery
Who says that installation of Magisk requires custom Recovery?
Magisk documentation (Installation Instructions) - please find it on Magisk Github - certainly not.
Patch the boot.img and flash (it can be flashed by Fastboot, hence custom Recovery is not a must to have)
Hi,
it really gets deleted. My cell phone is then only in fastboot mode.
I am not interested in flashing Magisk either, but rather that recovery after an installation is no longer available. This makes installing updates more cumbersome.
I only have the problem when I flash a custom ROM. when I flash a MIUI ROM from xiaomi.eu Beta, the recovery is retained.
Title, because I've faced issues with ROM not booting after I flashed TWRP on the ROM, for clarity I'll demonstrate the steps I did
1. Boot to TWRP 3.6.2
2. Flash MIUI 13.0.5 Android 12, ticked flash TWRP after the ROM flashed
3. Boom, throws me back to TWRP
What's worse is that wiping options (format data, factory reset and advanced wipe) doesn't work and always fails, so I had to boot another TWRP img (specifically 3.7.0) to wipe the whole internal storage and install a ROM
The error code is this:
init fs_mgr_mount_all
Going back to the title, is it possible? Or it really was possible and just the procedure was wrong?
Use 3.7.0 by dblenk9 instead
NeoSDAP said:
Use 3.7.0 by dblenk9 instead
Click to expand...
Click to collapse
I take it you tried this once and succeeded. Thanks for the reply, currently on EU. Might as well try that next time