I flashed LiquidRemix but when I went to reboot into TWRP to flash gapps and magisk my phone just booted straight to OOS.
So I tried again but instead of rebooting to TWRP I just went to boot up and again my phone booted to OOS.
I only did a factory reset first time. Second time I wiped system as well but ended up with no OS so had to use fastboot to get OOS back on my phone.
I've tried switching slots in TWRP but it makes no difference. I always boot to OOS.
I'm guessing it's something to do with the a/b partitions but I've no idea what's happening.
I'm on the latest stable OOS Pie build.
You have to boot into trwp first then flash the latest Official Stable OOS Pie then reboot trwp then flash it again. If you don't do that (flash it twice in twrp) you'll end up having the issue you're having. It happened to me too until someone posted the correct flash procedure in another thread. The devs rarely update the flash instructions in their OP's.
ajsmsg78 said:
You have to boot into trwp first then flash the latest Official Stable OOS Pie then reboot trwp then flash it again. If you don't do that (flash it twice in twrp) you'll end up having the issue you're having. It happened to me too until someone posted the correct flash procedure in another thread. The devs rarely update the flash instructions in their OP's.
Click to expand...
Click to collapse
I'll try that. Cheers.
*edit*
It worked! Nice one.
Related
Hi there,
Yesterday I thought it was a good idea to flash a new rom (I bought my 2S early so I had a chinese rom I wanted to get rid off for a while).
My device is already unlocked and TWRP worked like a charm, that is, until today and last night. I first tried to flash lineageOS (https://forum.xda-developers.com/xi.../rom-lineageos-16-0-xiaomi-mi-mix-2s-t3862712) and to my surprise it didn't boot after that, it just straight went back to fastboot.
So I flashed to the original rom (https://en.miui.com/download-343.html) using the fastboot method and the MiFlash program. My phone booted up again, but when I tried to flash Magisk to have root it got stuck and went straight to Recovery this time (as opposed to fastboot).
Next I tried to flash again using fastboot and then flash the rom I wanted (lineageOS). This time, lineageOS showed the boot screen from that rom, but it got stuck there for almost 5 minutes and then I decided to give up. Now, no matter which twrp or rom I try I either end up not being able to boot it and if I do I cannot flash Magisk for root. Is there anyone who has a solution? Everyone seems to be able to install lineageOS just fine... Thanks!
Here's what I tried so far:
- Flashing original roms (older versions too)
- Using fastboot format data, system, cache to remove all data instead of just using TWRP
- Flashing 3 different unofficial roms (neither worked, all were stuck in their respective bootscreen for at least 5 minutes)
When flashing magisk try this method from NOS_bzone
Hope this helps
Seems like I'm having a quite similar problem.... https://forum.xda-developers.com/xiaomi-mi-mix-2s/help/boot-installing-custom-rom-t3868623
I managed to flash the global official rom + Magisk by these steps:
Download official rom (from: https://en.miui.com/download-343.html) (I used the fastboot method, clean all, NOT clean all and lock)
Download magisk
Download MiPa kernel: https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/kernel-mipa-kernel-t3831437
Flash the rom first using fastboot and MiFlash, then go to TWRP, then magisk and then MiPa (it will retain magisk)
After that I was able to boot and retain a successful root. I don't know about custom roms at the moment, but at this point after working on it for more than 12 hours, I don't feel like trying
I was going to flash Pixel Experience rom so I updated to the latest TWRP by Peter via fastboot because it did not flash. Upon flashing PEX successfully, I can't boot into the system. Every time I reboot, I get taken to recovery. Any help?
whatsmyname25 said:
I was going to flash Pixel Experience rom so I updated to the latest TWRP by Peter via fastboot because it did not flash. Upon flashing PEX successfully, I can't boot into the system. Every time I reboot, I get taken to recovery. Any help?
Click to expand...
Click to collapse
Try wiping out the OS partition (through TWRP) and then flash the ROM .
whatsmyname25 said:
I was going to flash Pixel Experience rom so I updated to the latest TWRP by Peter via fastboot because it did not flash. Upon flashing PEX successfully, I can't boot into the system. Every time I reboot, I get taken to recovery. Any help?
Click to expand...
Click to collapse
Flashing PE needs MIUI v10.x (PIE Based) for successful flash, flash the stock miui rom (pie) using twrp and then flash the PE. Also try Orange Fox Recovery than twrp.
How to solve this problem
whatsmyname25 said:
I was going to flash Pixel Experience rom so I updated to the latest TWRP by Peter via fastboot because it did not flash. Upon flashing PEX successfully, I can't boot into the system. Every time I reboot, I get taken to recovery. Any help?
Click to expand...
Click to collapse
Bro can you solve this problem and how
I'm also facing this same issue.
Were you able to fix it?
If yes, then how?
whatsmyname25 said:
I was going to flash Pixel Experience rom so I updated to the latest TWRP by Peter via fastboot because it did not flash. Upon flashing PEX successfully, I can't boot into the system. Every time I reboot, I get taken to recovery. Any help?
Click to expand...
Click to collapse
The issue is the latest twrp it is broken. I don't know why they ever put that on the official site flash
twrp-3.3.1-0-violet.img from the official site
https://dl.twrp.me/violet/
or orange fox
https://forum.xda-developers.com/redmi-note-7-pro/development/official-orangefox-recovery-project-t3973647
then do a clean system installation.
Dear op7p xda community,
A few months ago, I rooted my device and flashed TWRP succesfully. After a stock OTA (still Pie), I lost both. Today, I wanted to re-root and re-flash TWRP. I used mauronofrio's Tool All In One 2.0.0.7 for this. I didn't flash TWRP, but booted it and used that to flash Magisk 19.4. Now, I wanted to see if the rooting process was successful, so I booted the OS. Unfortunately, once it boots and reaches the lockscreen, the "shutting off..." prompt immediately shows and reboots me into the stock recovery.
Edit: I now flashed TWRP after booting TWRP again and ran Magisk to root it again. Unfortunately, the problem persists (only now reboots to TWRP instead of stock recovery). Help is much appreciated!
Can someone help me get my phone to work again? Thanks a lot in advance!
Regards,
Wouty
What version TWRP? Maybe try a different one?
redpoint73 said:
What version TWRP? Maybe try a different one?
Click to expand...
Click to collapse
Thank you for your reply. I am now on TWRP 3.3.1-4 (latest). I have tried to factory reset and wipe the phone in hopes of getting it to start properly again, but now the OS doesn't even boot and immediately reboots me into TWRP. I have now tried to flash 3 different stock, official ROMs, both International and Europe, like OnePlus7ProOxygen_21.O.14_OTA_014_all_1907281611. I used the recommended flashing instructions (flash ROM, flash TWRP, reboot TWRP, flash Magisk) But none of them boot at all. Only TWRP is usable now. I don't know what to do
Wouty said:
Thank you for your reply. I am now on TWRP 3.3.1-4 (latest). I have tried to factory reset and wipe the phone in hopes of getting it to start properly again, but now the OS doesn't even boot and immediately reboots me into TWRP. I have now tried to flash 3 different stock, official ROMs, both International and Europe, like OnePlus7ProOxygen_21.O.14_OTA_014_all_1907281611. I used the recommended flashing instructions (flash ROM, flash TWRP, reboot TWRP, flash Magisk) But none of them boot at all. Only TWRP is usable now. I don't know what to do
Click to expand...
Click to collapse
When it reboots back to TWRP try to format data if that doesn't work then you need to use MSM tool.
boybkol said:
When it reboots back to TWRP try to format data if that doesn't work then you need to use MSM tool.
Click to expand...
Click to collapse
Thanks for your reply. I had indeed wiped data, but that worsened the situation (not booting at all, instead of rebooting once booted). I have now tried this https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424 and it now seems to be booting (booting animation on-going for quite some time now, though). I will keep you posted. If it doesn't work, I'll look into the MSM tool. Thanks for the suggestion!
Wouty said:
I am now on TWRP 3.3.1-4 (latest).
Click to expand...
Click to collapse
That is the latest official TWRP for this device. The official builds don't support Android 10, as decryption is not supported, so that may be part of your problem. The latest unofficial is -70, and I believe you need to use build -65 or later for Android 10.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
Wouty said:
Thanks for your reply. I had indeed wiped data, but that worsened the situation
Click to expand...
Click to collapse
Wipe is not the same as format. In TWRP, go to Wipe section, and you will see a button "Format data".
If you are now stuck on a boot loop, try booting into twrp and clearing cache. If you still can't boot, then i recommend downloading the full official rom and flashing it via fastboot. This will remove twrp and u'll end up with stock recovery and everything. Then after that follow proper instructions to install twrp first, then clear cache. Then magisk, and clear cache.
milindpatel63 said:
If you are now stuck on a boot loop, try booting into twrp and clearing cache. If you still can't boot, then i recommend downloading the full official rom and flashing it via fastboot. This will remove twrp and u'll end up with stock recovery and everything. Then after that follow proper instructions to install twrp first, then clear cache. Then magisk, and clear cache.
Click to expand...
Click to collapse
Trying to flash an official ROM via fastboot for a second time did indeed solve the problem for me. Now able to boot. Now backing up everything to make sure I'm able to solve these issues faster in the future. Thanks to all for your input!
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
First Time Install / Clean Flash
- Have OOS 10.3 flashed to both slots!!
- Boot to recovery
- Flash BUILD.zip (TWRP built-in)
- Wipe Cache
- Format data
- Reboot to recovery (optional)
- Flash Magisk.zip (optional)
- Reboot to system & #KeepEvolving
Click to expand...
Click to collapse
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
roel1976 said:
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
Click to expand...
Click to collapse
Hi!
I had this exact same problem a couple months ago. Rebooting to recovery used to change slots for me, but then it stopped.
What you can do is change active slot manually on Reboot section. By doing this, you don't even have to reboot to recovery in other to flash the other slot (altough I do it just to be safe).
And remember: the rom is flashed on the inactive slot, so after the final flash you gotta change slots one more time.
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Thanks for the info, it really helps.
One question: in your experience can you wipe your phone and then installl OOS on the wiped phone?
So I just booted into TWRP, did standard wipe action: Data, Cache, and Dalvik. I then try to flash the latest OOS zip and I then get this error:
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
Updater process ended withL ERROR: 1.
Error installing zip file: '/usbstorage/00, INSTALL/OnePlus6Oxygen_22_OTA_044_all_2002220042_a46425f1bfe43d2.zip
FIXED: I was using TWRP 3.3.1.11 and I then found out there was a newer version: 3.3.1.18 which you can get here: https://sourceforge.net/projects/mauronofrio-twrp/files/Enchilada/
I am now able to install OOS from scratch (ie wiped phone).
remewer said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
harshybar said:
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
Click to expand...
Click to collapse
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
remewer said:
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
Click to expand...
Click to collapse
When you say local update you mean while I am running the rom, go to settings then do update from local source?
harshybar said:
When you say local update you mean while I am running the rom, go to settings then do update from local source?
Click to expand...
Click to collapse
Exactly
GuestD2559 said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
@Cypher_01, Try this guide. This worked for me. I did not reinstall Nikgapps. Maybe that's where the problem lies? Don't forget to change the update slot at the end before you restart.
Hello,
i have a question about getting into Recovery or maybe i have to install it again?
So i installed twrp following this guide
Install LineageOS on walleye | LineageOS Wiki
wiki.lineageos.org
At first i installed the Lineage OS recovery but wasnt able to flash a ROM with that so i switched and installed twrp.
It was installed to slot A.
I then went ahead and installed an ASOP ROM.
Now the ROM is working fine and i wanted to go into TWRP and do a Backup.
However i cant get into TWRP. Not with key combos nor with adb reboot recovery.
All i get is the fallen Android Robot picture.
I guess i wrote the image to Slot A as well and now have no recovery left.
Do i have to flash TWRP again and this time to Slot B?
I dont wanna brick anything by accident as i have seen some posts where people switched Slots and got bricks / semi bricks.
Thanks for any help or clarification.
Kind Regards
Hello mate, i never reinstalled twrp on my pixel 2 after catching a bootloop after installing it and then flashing magisk so stuck with using fastboot to fastboot boot twrp when I wanted to flash a ROM/mod.
Sounds strange that twrp was only on 1 slot as the twrp installer zip should flash both slots when flashed?
With regard to losing twrp you'll probably find that the new ROMs recovery has overwritten your twrp recovery during the flashing process giving you a stock recovery again (Fallen android). When I was using a 6T which is an A/B slot device you always had to reflash the twrp installer after a ROM flash to keep twrp installed.
I'd check the official twrp thread re backing up with twrp as it did have problems either backing up or restoring last I used it.
Hope that's some help.