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 ????
Folks,
Seeing alot of comments about bootloops, etc after trying to install the new stable OOS Oreo release.
I went through the same issue myself and found the following method to work best.
PLEASE NOTE: I'm not responsible if this does Any type of damage or issues to your device.
Be sure to backup all you need to back up to your PC.
1. Complete wipe of phone.
2. Flash the stock recovery that was used for reverting from Oreo Beta to Nougat. http://oxygenos.oneplus.net.s3.amazonaws.com/OP5_recovery.img
3. Wipe everything again.
4. Sideload new Oreo release. (Credit @HatRiGt, https://drive.google.com/open?id=1NW5zyUOL6bWgUWozFGLiutzud203npKp)
5. Reboot to bootloader and flash the Chinese TWRP. https://drive.google.com/open?id=1AKbC4HB0h4rEldQUowWGdyM4iYBVV--7
6. Reboot to recovery and flash Magisk. I flashed the 14.6 version and haven't found any issues yet. (https://forum.xda-developers.com/attachment.php?attachmentid=4366826&d=1513897917)
7. Boot phone.
I cannot promise this will work for you, but it has done the job for me.
Running Oreo Stable with Magisk 14.6 and restored all apps from Titanium Backup that I saved on my PC.
I highly suggest blu_spark TWRP instead of chinese one, and i think this method is ONE of the other working way
Couldn't get mine to work with blu spark, hence why I had to use chinese
Link for Chinese twrp please
Thank you very much, work for me
Make a video of it please
New Magisk v.15.
Thanks to topjohnwu.
joecaesar said:
Link for Chinese twrp please
Click to expand...
Click to collapse
Added to OP.
All is well. And with google Drive almost all data is back.
Nice & easy workaround..
Step 5 has to be : install TWRP on fastboot mode...
@hallo dare
Any chance you can make a very detailed video about this process?
cultofluna said:
Nice & easy workaround..
Step 5 has to be : install TWRP on fastboot mode...
Click to expand...
Click to collapse
Yes, sorry. Amended text now.
lvints said:
@hallo dare
Any chance you can make a very detailed video about this process?
Click to expand...
Click to collapse
No real need for a video mate, just follow the post step by step and you're golden!
I can not sideload Oreo zip, it says can not read
Lvsitano said:
I can not sideload Oreo zip, it says can not read
Click to expand...
Click to collapse
You should try changing the TWRP
If you have problems with adb sideload:
Boot into fastboot and install stock .
Unlock/Lock your Phone and unlock it again. Locking will wipe the whole phone.
After this you can make a clean installation.
Reboot to bootloader and flash the Chinese TWRP and boot to Recovery.
Install the oreo.zip file.
Reboot to System.
Make your Setup: WLAN, GMail Account aso.....
After all boot to Recovery and install Magisk
Very easy, put oreo zip file in the root folder, backup all data, flash stock recovery, boot with stock recovery, wipe cache, upgrade internal..., Select oreo zip file and flash it, then back and select wipe, select erase every thing and reboot. Done.
Thank you so much! I finally got it working. I needed to do a factory wipe and skip the magisk installation but it worked!
Cheers!
nikoeuren said:
Thank you so much! I finally got it working. I needed to do a factory wipe and skip the magisk installation but it worked!
Cheers!
Click to expand...
Click to collapse
Magisk won't flash on stock recovery, if that's the reason you had to skip installing it.
hallo dare said:
Magisk won't flash on stock recovery, if that's the reason you had to skip installing it.
Click to expand...
Click to collapse
No I installed the TWRP and flashed magisk. It refused to boot so I factory swiped it and all was good. Now I have to figure out how to install magisk without getting into bootloop.
Sent from my ONEPLUS A5000 using Tapatalk
Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Step 1/2
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Havoc-OS-v2.4-20190502-jasmine_sprout-Official.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
Anyone can help me?
Thanks
nnexuss said:
Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Anyone can help me?
Thanks
Click to expand...
Click to collapse
Try to use twrp 3.2.3 and follow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
mma_1494 said:
Try to use twrp 3.2.3 and follow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
I already tried this version but not the guide...
I'll try when I arrived at home
nnexuss said:
Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Anyone can help me?
Thanks
Click to expand...
Click to collapse
Their is only one way to recover your phone just follow this step
1. Flash stock firmware(stock rom) vie fastboot using MI Flasher
this is bring back you phone and if you want to install custom rom then follow this
1. boot twrp
2. wipe all the data from slot A and B partition(internal storage as per you choice )
3. boot to slot B and copy past the custom rom file in slot B
4. flash that rom and boot to slot B and then flash Gaaps and other staff you want
5. reboot and enjoy.
NOTE: changing the slot require reboot twrp in simple words every time you change the slot you have to reboot the phone and boot again to twrp..
i hope this will work for you..:good:
If you don't have stock flash file then try from step 2. see whether it will work or not otherwise follow from beginning.
facing the same issue
i tried the same and getting the same error. even the twrp3.2.3.0 never worked while tried to flash that one more than 20 times, after flashing 3.2.3.0 my phone either boots normally or it gets completely power off. and if i try to boot into recovery using volume keys and power key , it boots in stock recovery. please help
Mine its ok now... i don´t know whats happen but suddenly it flash withou any problem.
See if it helps...
Make sure you're running a proper working Recovery
Flashing instructions:
Dirty flash (assuming you have rom on slot A):
1. Download all required files and place them to internal memory (ROM, twrp installer, gapps, magisk, ..)
2. Boot twrp to slot B and flash ROM and twrp installer
3. Reboot twrp to slot A and flash gapps (optional magisk)
4. Now reboot to system
Clean flash (assuming you have rom on slot A):
1. Download all required files and place them to internal memory (ROM, twrp installer, gapps, magisk, ..)
2. Boot twrp to A slot and wipe everything except for internal
3. Reboot twrp to B slot and flash ROM and twrp installer
4. Reboot twrp to slot A and flash gapps (optional magisk)
5. Now reboot to system
If you are coming from stock:
1. Download latest TWRP installer and image
2. Open cmd and type fastboot boot twrp.img (change twrp to its actual name)
3. You should be on slot A in twrp, if not change it and reboot to bootloader and repeat step 2.
4. Format data
5. Now follow instruction for clean flash
Click to expand...
Click to collapse
Credits: Fullbustah
I have this issue and none of the steps worked.
I got my device 2 days back and it was in Oreo. I tried to update to pie but the update keep failing. I unlocked the phone and flash latest official fastboot rom using mi_flash and installed magisk using this guide:
https://forum.xda-developers.com/mi-a2/how-to/unlock-bootloader-n-root-magisk-easy-t3856800
Everything went smooth.
Today I tried to go further and instal PE rom using this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Everything goes smooth until I boot to TWRP and try to flash the rom. It gave the error posted by OP. I have tried the following things since:
1. Try another two roms, same issue
2. Flash stock Pie using mi_flash then temp boot to TWRP latest version from 'a' partition, wipe everything, then boot from 'b' partition, wipe everything, try to flash. Same issue.
3. Install TWRP (it installed without any issue), reboot to installed TWRP, flash rom, same issue.
4. Try to flash with 'a' as active. Same issue.
5. All other possible combos (i think) of the above. In all cases everything goes as expected until I try to flash the rom.
Currently I have flashed the factory image back. Any help will be greatly appreciated.
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
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
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.
Hi all,
I was on xiaomi.eu MIUI 11 ROM for some time, but wanted to switch to either Evolution or Syberia ROM.
I did a complete wipe and installed evolution os trough twrp... but i forgot to remove encryption so i bricked my device...
So then, I flashed the latest stock rom (11.05)with Xiaomi flash tool, but then i was stuck with the chinese ROM so...
1. I went back to bootloader and flashed mauronofrio's TWRP recovery .
2. completely wiped phone; Cache,System,Data,Internal storage
3. copied Evolution OS 4.1 to my phone
4. installed zip trough TWRP, all successfull
5. but then when rebooting, TWRP says:"No OS installed, do you wish to continue"
6. i tried other ROMs like xiaomi.eu and syberia, but these would either give me the same problem, or just bootloop until iam back in the fastboot screen...
Anyone any idea what iam doing wrong?
dev-DaT said:
Hi all,
I was on xiaomi.eu MIUI 11 ROM for some time, but wanted to switch to either Evolution or Syberia ROM.
I did a complete wipe and installed evolution os trough twrp... but i forgot to remove encryption so i bricked my device...
So then, I flashed the latest stock rom (11.05)with Xiaomi flash tool, but then i was stuck with the chinese ROM so...
1. I went back to bootloader and flashed mauronofrio's TWRP recovery .
2. completely wiped phone; Cache,System,Data,Internal storage
3. copied Evolution OS 4.1 to my phone
4. installed zip trough TWRP, all successfull
5. but then when rebooting, TWRP says:"No OS installed, do you wish to continue"
6. i tried other ROMs like xiaomi.eu and syberia, but these would either give me the same problem, or just bootloop until iam back in the fastboot screen...
Anyone any idea what iam doing wrong?
Click to expand...
Click to collapse
This works for me every time.
1 Flash the latest fastboot ROM.
2 Flash TWRP (same one you used)
3 Boot into TWRP (use the vol+ button when booting)
4 In format menu swipe to factory reset, then format data (VERY IMPORTANT this must be FORMAT not just wipe)
5 In reboot menu boot into recovery, this ensures TWRP correctly accesses the newly formatted data partition.
6 Copy over the ROM (and GApps, if needed and/or Magisk)
7 Flash the ROM, (then GApps if needed)
8 Boot into system and do the initial setup
9 If installing Magisk, boot back to TWRP and install Magisk.
There is no need to wipe anything else. There is no need to wipe anything again after installing. There is no need to disable encryption or dm-verity.
Robbo.5000 said:
This works for me every time.
1 Flash the latest fastboot ROM.
2 Flash TWRP (same one you used)
3 Boot into TWRP (use the vol+ button when booting)
4 In format menu swipe to factory reset, then format data (VERY IMPORTANT this must be FORMAT not just wipe)
5 In reboot menu boot into recovery, this ensures TWRP correctly accesses the newly formatted data partition.
6 Copy over the ROM (and GApps, if needed and/or Magisk)
7 Flash the ROM, (then GApps if needed)
8 Boot into system and do the initial setup
9 If installing Magisk, boot back to TWRP and install Magisk.
There is no need to wipe anything else. There is no need to wipe anything again after installing. There is no need to disable encryption or dm-verity.
Click to expand...
Click to collapse
thanks, i always thought that a wipe was sufficient, or at least equal to a format... anyways will report back later when i have time to try it. lets hope it works because i can't handle this chinese rom
dev-DaT said:
thanks, i always thought that a wipe was sufficient, or at least equal to a format... anyways will report back later when i have time to try it. lets hope it works because i can't handle this chinese rom
Click to expand...
Click to collapse
The format is needed to temporarily remove encryption
I've just remembered that I missed an important step. Call it step 1.5
If you going to flash immediately after flashing official MIUI you must boot into MIUI once before doing anything else. You don't need to go through the set-up, you can boot immediately into fastboot after you get to the initial set-up page. The first boot finalises the install and is needed before you flash over the top of it. That may be the cause of your issue if you had missed this before.
Robbo.5000 said:
The format is needed to temporarily remove encryption
I've just remembered that I missed an important step. Call it step 1.5
If you going to flash immediately after flashing official MIUI you must boot into MIUI once before doing anything else. You don't need to go through the set-up, you can boot immediately into fastboot after you get to the initial set-up page. The first boot finalises the install and is needed before you flash over the top of it. That may be the cause of your issue if you had missed this before.
Click to expand...
Click to collapse
Ok so i flashed TWRP again, rebooted to stock rom and then rebooted into recovery, but the stock recovery is still there.
When i flash TWRP and reboot into recovery immediately i can enter TWRP, but if i reboot the phone to MIUI and then reboot again, TWRP is gone again...
It seems like TWRP does not persist... now iam stuck again on fastboot screen because i wiped + formatted everything.
Edit:
When i want to flash recovery it says "OKAY" but it is unable to boot:
Sending 'recovery' (65536 KB) OKAY [ 1.562s]
Writing 'recovery' OKAY [ 0.333s]
Finished. Total time: 1.989s
Sending 'boot.img' (65536 KB) OKAY [ 1.547s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
dev-DaT said:
Ok so i flashed TWRP again, rebooted to stock rom and then rebooted into recovery, but the stock recovery is still there.
When i flash TWRP and reboot into recovery immediately i can enter TWRP, but if i reboot the phone to MIUI and then reboot again, TWRP is gone again...
It seems like TWRP does not persist... If i wipe all data trough TWRP and then reboot, i don't have OS but i do reboot back into TWRP, because well, there is nothing else...
Click to expand...
Click to collapse
This is normal, MIUI will restore stock recovery of the recovery partition changes. In order to persist TWRP you need to either install Magisk, disable dm-verity or install a custom ROM.
If you are going to flash a custom ROM, then you should do so immediately after flashing TWRP.
After formatting data, TWRP has an issue seeing the data partition, so go to the reboot menu in TWRP and select to reboot to recovery.
Then you can immediately install the ROM of choice. You cannot boot back into system as you'll lose TWRP.
Robbo.5000 said:
This is normal, MIUI will restore stock recovery of the recovery partition changes. In order to persist TWRP you need to either install Magisk, disable dm-verity or install a custom ROM.
If you are going to flash a custom ROM, then you should do so immediately after flashing TWRP.
After formatting data, TWRP has an issue seeing the data partition, so go to the reboot menu in TWRP and select to reboot to recovery.
Then you can immediately install the ROM of choice. You cannot boot back into system as you'll lose TWRP.
Click to expand...
Click to collapse
Ok, it appears that everytime i wipe system, i am not able to boot anymore into TWRP... Am i supposed to wipe System? or only wipe data & format data
dev-DaT said:
Ok, it appears that everytime i wipe system, i am not able to boot anymore into TWRP... Am i supposed to wipe System? or only wipe data & format data
Click to expand...
Click to collapse
There is no need to wipe system. You only need to wipe cache and dalvik and format data. (I choose to factory reset because it's easier in TWRP, but you could do advanced wipe and select cache and dalvik, then format data. Follow the steps exactly, but include my later step 1.5
I've just followed this myself today, as I've moved from LOS to the latest unofficial Havoc build.
In theory you could start by booting to fastboot and flashing TWRP again, then follow the steps from that point. You probably don't need to install MIUI.
Robbo.5000 said:
There is no need to wipe system. You only need to wipe cache and dalvik and format data. (I choose to factory reset because it's easier in TWRP, but you could do advanced wipe and select cache and dalvik, then format data. Follow the steps exactly, but include my later step 1.5
I've just followed this myself today, as I've moved from LOS to the latest unofficial Havoc build.
In theory you could start by booting to fastboot and flashing TWRP again, then follow the steps from that point. You probably don't need to install MIUI.
Click to expand...
Click to collapse
Ok thanks a lot! So no need to wipe system partition after stock rom install. just wipe cache/dalvik/data, got it.
Most ROM install guides tell you to wipe /system when coming from stock rom. I guess this requirement has changed? or depends on what ROM you're coming from?
Use can use my guide
https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
it has how to flash roms, and fastboot fix. (which tells why the Recovery isn't staying)
Robbo.5000 said:
This works for me every time.
1 Flash the latest fastboot ROM.
2 Flash TWRP (same one you used)
3 Boot into TWRP (use the vol+ button when booting)
4 In format menu swipe to factory reset, then format data (VERY IMPORTANT this must be FORMAT not just wipe)
5 In reboot menu boot into recovery, this ensures TWRP correctly accesses the newly formatted data partition.
6 Copy over the ROM (and GApps, if needed and/or Magisk)
7 Flash the ROM, (then GApps if needed)
8 Boot into system and do the initial setup
9 If installing Magisk, boot back to TWRP and install Magisk.
There is no need to wipe anything else. There is no need to wipe anything again after installing. There is no need to disable encryption or dm-verity.
Click to expand...
Click to collapse
I need help... The reason why I'm flashing custom rom is, when the latest update came MIUI 12.5 android 11, all sensors of my phone stopped working like (Gyroscope, accelerometer, proximity sensor) I tied to flash the rom by fastboot method but still the problem persists. because of that I unlocked bootloader and flashed twrp. After flashing custom rom when I tried to boot it, it stuck on booting screen and when I tried to reboot into recovey it is showing fastboot mode. I'm unable to boot into custom rom.
dev-DaT said:
Hi all,
I was on xiaomi.eu MIUI 11 ROM for some time, but wanted to switch to either Evolution or Syberia ROM.
I did a complete wipe and installed evolution os trough twrp... but i forgot to remove encryption so i bricked my device...
So then, I flashed the latest stock rom (11.05)with Xiaomi flash tool, but then i was stuck with the chinese ROM so...
1. I went back to bootloader and flashed mauronofrio's TWRP recovery .
2. completely wiped phone; Cache,System,Data,Internal storage
3. copied Evolution OS 4.1 to my phone
4. installed zip trough TWRP, all successfull
5. but then when rebooting, TWRP says:"No OS installed, do you wish to continue"
6. i tried other ROMs like xiaomi.eu and syberia, but these would either give me the same problem, or just bootloop until iam back in the fastboot screen...
Anyone any idea what iam doing wrong?
Click to expand...
Click to collapse
Bro I have one doubt, I installed pixel os successfully then I roll back into stock os(miui) with locking bootloader, the. Again I unlock bootloader successfully, but the problem is I am unable to install os, i tried wipe data, catch. But the stock rom was not removed. What can I do?
Using orange fox in resmi note 10 pro