I have now tried to install the latest RR and Omnirom builds and the problem remains the same.
I've been very particular about wiping data before the installs.
Here is what I have done,
Performed data wipe by typing "yes" when requested. Used advance wipe to wipe everything.
Installed Rom, Stock Gapps and Magisk zip files.
Wiped Cache.
Reboot
The phone will not boot and only returns to recovery.
Can anyone help?
Here is my TWRP log if this helps - https://pastebin.com/ghpXkt3t
Not sure if this is relevant, but every time I try to flash a ROM it always fails on the first attempts and needs a second try to succeed.
TylerDurdenK said:
I have now tried to install the latest RR and Omnirom builds and the problem remains the same.
I've been very particular about wiping data before the installs.
Here is what I have done,
Performed data wipe by typing "yes" when requested. Used advance wipe to wipe everything.
Installed Rom, Stock Gapps and Magisk zip files.
Wiped Cache.
Reboot
The phone will not boot and only returns to recovery.
Can anyone help?
Click to expand...
Click to collapse
If you only get to the mi logo and not the ROM boot screen then format data "yes 3-4 times in a row.
If that doesn't work then wipe the system and data and retry
I was only getting the Mi logo, so I did the format data 4 times in a row and rebooted.
I then saw the Omnirom logo for the first time!
unfortunately 2 seconds later I'm back in TWRP.
I have now tried for the 5th time to perform a fresh install.
Formatting data multiple times, wiping system and data multiple times.
The result is the same.
I see a flicker of the Omnirom logo and I get booted back into recovery.
TylerDurdenK said:
I see a flicker of the Omnirom logo and I get booted back into recovery.
Click to expand...
Click to collapse
Please try this:
1. Wipe: Dalvik / Art Cache; System; Data; Cache;
2. Go back to main TWRP screen and install the rom, install Google Apps, install "addonsu-15.1-arm64-signed.zip" (in case of Lineage) or the latest Magisk (in case of other rom)
3. Wipe Cache
4. Reboot
If this doesn't work and the device restarts in twrp, then pls download the twrp flashable Xiaomi rom from here: http://en.miui.com/download-334.html
1. Wipe: Dalvik / Art Cache; System; Data; Cache
2. Go back to main twrp screen and install the Xiaomi rom. Do not reboot.
3. Go back to main twrp screen and Wipe: Dalvik / Art Cache; System; Data; Cache
4. Go back to main twrp screen and install the rom (Lineage or OMNI or RR), install Google Apps, install "addonsu-15.1-arm64-signed.zip" (in case of Lineage) or the latest Magisk (in case of other rom)
5. Wipe Cache
6. Reboot
I had the same problem and this method worked for me, maybe it will work for you too. :fingers-crossed:
If it doesn't then maybe you have to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (bootloader might relock), flash twrp and then flash new custom rom.
No idea what happened but I have the same issue atm.
I was running a recent Omnirom for a few weeks. System got unstable, so decided to flash the newest version. Got me stuck in a bootloop. I tried everything, short of relocking and unlocking the bootloader.
- Full wipe, including storage
- Reflash Global Dev through TWRP.
- Flash stock Global Dev over flashboot
- Flash Omni, wipe, flash omni again.
All the same. Global Dev runs, all AOSP roms just go into bootloop. No idea what went wrong, I've flashed tens of custom roms over the past months without issues.
Firipu said:
No idea what happened but I have the same issue
All the same. Global Dev runs, all AOSP roms just go into bootloop. No idea what went wrong, I've flashed tens of custom roms over the past months without issues.
Click to expand...
Click to collapse
Then maybe the right solution to get out of bootloops would be to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (as bootloader will relock), flash twrp, do a full wipe and then flash new custom rom.
senerex said:
Then maybe the right solution to get out of bootloops would be to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (as bootloader will relock), flash twrp, do a full wipe and then flash new custom rom.
Click to expand...
Click to collapse
I have reflashed the original Xiaomi ROM (running it atm ) using the official Xiaomi Flash Tool.
I just did not relock my bootloader doing that (there's an option to leave it unlocked). Will relocking and then unlocking the bootloader really make a difference?
Firipu said:
I have reflashed the original Xiaomi ROM (running it atm ) using the official Xiaomi Flash Tool.
I just did not relock my bootloader doing that (there's an option to leave it unlocked). Will relocking and then unlocking the bootloader really make a difference?
Click to expand...
Click to collapse
Not really. You ev. save yourself a waiting time of 72h....
Not sure what happened. I set up MIUI completely. Then, getting frustrated after using it for 10 minutes, decided to try one more time. Same thing.
1) Fastboot flash TWRP.
2) Wipe
3) Flash Rom
4) Flash GAPPS
Worked this time. No idea what went wrong the first 4 times. Only difference is that I went through the trouble to set up the entire phone this last time before trying again.
Anyhoo, so if anyone has the same issue. Set up phone in MIUI, only then wipe/flash
I got mine working by not installing Magisk. I just flashed Omnirom and GApps and it worked.
After setting up my phone I have since rebooted into recovery and installed Magisk and it works.
Can't system boot after install TWRP, Lazy Magisk on MIX M2S
Hello,
I have this problem, the phone does not boot after TWRP, Lazyflasher and Magisk being installed all fine.
I have re-installed the official ROM on my Xiaomi MI MIX 2S, then TWRP is fine too, then Lazy and Magisk fine.
When I reboot, it is stocked on MI logo whatever I do.
I have tried most of the advise posted but still stocked.
I restarted from scratch, installing again the official ROM, then fastboot flash recovery twrp, then lazy and Magisk, but still stocked on MI.
Thanks a lot in advance
Did you wipe system by any chance.. If you did you need to flash miui again with fastboot.. Or boot into fastboot and type this command 'fastboot format userdata' and press enter. You are facing this issue because of encryption
goxthak0 said:
Did you wipe system by any chance.. If you did you need to flash miui again with fastboot.. Or boot into fastboot and type this command 'fastboot format userdata' and press enter. You are facing this issue because of encryption
Click to expand...
Click to collapse
Gratitude for your reply. What do you mean by "wipe system". I installed the rom and then TWRP etc...
I flashed the ROM again and went into bootloader
I typed "fastboot format userdata" and the system replied:
"/usr/local/bin/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Can you advise.
Thanks a LOT
Did you use the correct rom ? Mi mix 2 or mi mix 2s?
fotocreaman said:
Did you use the correct rom ? Mi mix 2 or mi mix 2s?
Click to expand...
Click to collapse
I used MI MIX 2D:
As in en.miui web site
https://en.miui.com/download-343.html
Author: MIUI Official TeamVersion: V10.0.9.0.PDGMIFH (MIUI10) Size: 1.7G
My mobile is:
MI MIX 2S, Android 9PKQ1
MIUI Global 10.0
Thanks a lot for your advise as always stock, despite different attempts
Did you try to flash using mi tools?
fotocreaman said:
Did you try to flash using mi tools?
Click to expand...
Click to collapse
NO, I followed the usual process with ADB tools.
However, I have no boot "stuck at MI logo (bootloop)" problem when I flash the ROM.
It happens only when use TWRP and flash Magisk and Lazy.
Then, when I restart it got stuck at MI Logo.
Do you suggest I try to flash with MI logo (I don't have a PC though).
If so, should I just flash the ROM and then, what about TWRP, should I use MI flash or ADB?
I just want to make sure that the problem is with the ROM instal?
Thanks a LOT
I tried aosp extended, pixel experience and several other pie treble roms. They don't even enter the boot screen. They are stuck in the screen where it says your device has been unlocked. I used the arm64 a only images. The openkirin roms work otherwise. Help regarding this will be appreciated. BTW I used twrp to flash. I even tried using magisk but it didn't work. Can you guys check and let me know your results. Guidance regarding this issue will also be helpful.
Edit- only LOS16 unofficial treble boots.
you've got to flash using fastboot and then right after, without booting to the OS, flash GApps if the ROM doesn't already have it.
steven360 said:
you've got to flash using fastboot and then right after, without booting to the OS, flash GApps if the ROM doesn't already have it.
Click to expand...
Click to collapse
What if the entire reason we're using an AOSP/etc ROM is to avoid Google integration (to use MicroG, etc)?
Is there a way to use this phone without Gapps? If not, what is the bare minimum to let it boot successfully, and can they be disabled/removed later?
UPDATE: This AOSP ROM w/ MicroG integrated boots and runs successfully on the Honor 7X. Stock recovery, flashed via fastboot. (I did fastboot format system & fastboot -w to be safe).
awoolf said:
What if the entire reason we're using an AOSP/etc ROM is to avoid Google integration (to use MicroG, etc)?
Is there a way to use this phone without Gapps? If not, what is the bare minimum to let it boot successfully, and can they be disabled/removed later?
UPDATE: This AOSP ROM w/ MicroG integrated boots and runs successfully on the Honor 7X. Stock recovery, flashed via fastboot. (I did fastboot format system & fastboot -w to be safe).
Click to expand...
Click to collapse
I see. My apologies for not knowing that you do not want Gogole applications on your system. If that is the case, then you would definitely 100% want to use fastboot to flash the ROM. Then, you can just boot it up after doing a factory reset from the stock EMUI recovery. No need to do anything else since you want to avoid GApps. Again, sorry for not reading thoroughly.
How to install custom ROMs in Mi A2 Lite? When I try to install any zip in TWRP, it gets "Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)", and if I install a GSI ROM by flashing system.img, it bootloops. Is there a tutorial of how to install TWRP and flash custom ROMs?
I suggest you to install Crdroid for our phone. It´s official and gets weekly ots´s.
Follow instructions on op and you are good to go!
Important: You need to use offrains twrp to get it installed:
Bootable: https://androidfilehost.com/?fid=1395089523397933315
Installer: https://androidfilehost.com/?fid=1395089523397933316
If you stuck in bootloop on Crdroid bootscreen, you might need to decrypt your phone by formatting data (all your data will be lost - incl. internal sdcard) and installing this
Hello Everyone
I felt this section will be more appropriate for this query as it can also help many others who might be seeking an answer to the same question after Pie OOS (Community Beta) came out. This can also act as a guide for all future queries regarding force encryption. So, I have a really simple query, for which I have searched before posting but no concrete information came up.
Query:
How to prevent OOS from force-encrypting my internal data on first boot after a fresh ROM flash? I have tried flashing Magisk before first boot but that doesn't prevent force encryption. I am also using a custom kernel so patching stock boot image and flashing it won't be a viable option too.
Does anyone know of any zip or method which would prevent OOS from triggering force encryption (both Pie open beta and Oreo 5.0.8)?
I have tried to flash Oreo on an decrypted partition as follows but it still encrypted it.
1. Factory Reset
2. Flash OOS 5.0.8 zip on decrypted storage
3. Flash TWRP
4. Reboot to recovery
5. Flash Magisk
6. Flash custom kernel
7. Reboot
8. Rom takes 10 minutes to boot and storage is encrypted when booted up.
Look at this thread:
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
jeffrey268 said:
Look at this thread:
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Click to expand...
Click to collapse
The doubt i have is for the patched boot image. I always flash a custom kernel and i assume it will replace the bootimage as well.
My device forum doesn't have instructions how to do it, i've posted asking there but better to ask here also. I found this post for the Mi A2 that isn't my device mines the Mi A3 https://forum.xda-developers.com/mi-a2/how-to/guide-discussion-aio-gsi-thread-mi-a2-t3933356
The device is A/B arm64 has slots a and b i dunno how that effects flashing here, flashing custom roms will install into the inactive slot then you gotta change your active slot to be the the slot it installed into, then install rest of files there, does this apply with gsi .img files also?
When i tried using flashing the .img file i used orangefox recovery wiped all partitions flashed to system, just says no os installed i will probably try doing that again and flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip however who noes if that will help.
If someone can list the correct steps to flash using both fastboot method and twrp/orangefox recovery methods i would appreciate it. If it matters i was trying to flash android 10 gsi. I've seen many different methods listed depending on the device, so i guess that makes it harder to work out.
Thanks.
I've flashed it twice via TWRP with flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip. Plus TWRP.
1st time it was into A slot. After 1st flashing I've restarted TWRP and booted into B slot. And then flashed slot B.
After rebooting and seeing Logo in 15 minutes - I've got Android.10
xVM said:
I've flashed it twice via TWRP with flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip. Plus TWRP.
1st time it was into A slot. After 1st flashing I've restarted TWRP and booted into B slot. And then flashed slot B.
After rebooting and seeing Logo in 15 minutes - I've got Android.10
Click to expand...
Click to collapse
Thanks for the feedback, are you able to tell me the exact steps? like lets just say twrp is already installed and you factory reset, cleared all data.
Do you flash DM-Verity before you flash the rom? or after you flash the rom and what you just flash Forceencrypt Disabler and permissiver_v2.zip after installing the rom?
What i see with regular roms not gsi when you flash the rom if your on slot a it's actually installing it into slot b when you reboot that's where it is so you need to restart before flashing Magisk and other stuff. So i assume with the gsi maybe you need to reboot after installing as system image before flashing the other files?
Alister. said:
Thanks for the feedback, are you able to tell me the exact steps? like lets just say twrp is already installed and you factory reset, cleared all data.
Do you flash DM-Verity before you flash the rom? or after you flash the rom and what you just flash Forceencrypt Disabler and permissiver_v2.zip after installing the rom?
What i see with regular roms not gsi when you flash the rom if your on slot a it's actually installing it into slot b when you reboot that's where it is so you need to restart before flashing Magisk and other stuff. So i assume with the gsi maybe you need to reboot after installing as system image before flashing the other files?
Click to expand...
Click to collapse
Your better of using fastboot if flashing a gsi .img you dont need twrp really unless the rom is in a .zip format, or your wanting to add extras like magisk and such, or take a backup
Android 11
Did anyone tried Android 11 gsi??