Hi
After sitting on xiaomi.eu for a while I decided to change things up and go back to Paranoid Android Quartz 4. I flashed Global fastboot rom (V11.0.6.0.QFBEUXM which I had from a while ago) via MiFlash, booted the phone, went back to fastboot, flashed twrp and booted into it. Twrp didnt decrypt data on the phone, but I didn't think much of it and just formatted data. Then I flashed shrp, formatted cache, dalvik, system, data and internal storage, and using shrp I flashed firmware that was included with the rom, and then the rom itself. After that I tried booting the system, but after showing Mi logo it justs boots info fastboot. Even if I try to flash recovery and boot into it, it still reboots to bootloader. I don't really know what am i doing wrong.
Does anyone know what might be wrong?
Thanks in advance
fejlip said:
Hi
After sitting on xiaomi.eu for a while I decided to change things up and go back to Paranoid Android Quartz 4. I flashed Global fastboot rom (V11.0.6.0.QFBEUXM which I had from a while ago) via MiFlash, booted the phone, went back to fastboot, flashed twrp and booted into it. Twrp didnt decrypt data on the phone, but I didn't think much of it and just formatted data. Then I flashed shrp, formatted cache, dalvik, system, data and internal storage, and using shrp I flashed firmware that was included with the rom, and then the rom itself. After that I tried booting the system, but after showing Mi logo it justs boots info fastboot. Even if I try to flash recovery and boot into it, it still reboots to bootloader. I don't really know what am i doing wrong.
Does anyone know what might be wrong?
Thanks in advance
Click to expand...
Click to collapse
Hi
Try flashing vbmeta it might help you to boot
Sounds like you will have to start from scratch and flash the fastboot ROM and proceed from there.
However, after formatting data in TWRP, reboot into recovery before flashing SHRP and PA.
If after this it reboots into recovery rather than system, you can try flashing vbmeta.
Peace
---------- Post added at 01:37 PM ---------- Previous post was at 01:32 PM ----------
Also, TWRP won't ask for a password to decrypt data if you went straight back to fastboot after flashing the stock ROM as you won't have set up a decryption password without setting up the phone.
Also, I'm not sure that you have to format any other partition other than data, just a wipe should be enough. But definitely reboot recovery after formatting data. The PA thread should say whether partitions need to be formatted or simply "wiped"
Peace.
I tried doing it again a few more times but with no luck. So instead I tried to flash xiaomi.eu weekly rom, but that also doesn't work for me. I downloaded newest Global Fastboot Rom (V12.0.1.0.QFBMIXM), flashed it with MiFlash and then proceeded to set up the phone as a new device. After setup I turned on usb debugging, went into fastboot and flashed redispade TWRP 3.3.1 (rebooted into TWRP and got asked for decryption password). Then I wiped data, cache and dalvik and flashed xiaomi.eu. After I flashed the rom, I installed magisk (without rebooting the device). Then when I tried to boot into system I got stuck in recovery bootloop (files where encrypted, did not get asked for password). I also tried to flash vbmeta after that but the phone was still bootlooping. I honsetly have no clue what I am doing wrong at this point
Edit: I tried it again this time without flashing magisk and the results are exactly the same - twrp bootloop even after flashing vbmeta
I personally don't use miflash to flash fastboot ROMs, I prefer to do it via fastboot. Could miflash be causing issues? Have you replicated the steps you took to originally flash xiaomi.eu ROM?
Peace.
Related
Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
goatlad said:
Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
Click to expand...
Click to collapse
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
crzykiller said:
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
Click to expand...
Click to collapse
tried official twrp 3.1.1-0, did these steps only, maybe I've missed something:
installed twrp 3.1.1-0 then went into fastboot and typed fastboot format userdata
rebooted into TWRP, i was promted whether to keep system read only, I tried first swiping to allow mods, and also keep read only then proceeded:
changed data to F2FS (didn't wipe or factory reset anything else)
rebooted system
copied lineage and gapps zip files to phone
installed latest lineage then gapps 7.1 arm64
rebooted system, back into twrp
Used the search, used google, couldn't find any concrete answers
I am on Android N - unlocked bootloader - rooted via magisk, One Plus 3.
Could I do the following?
use TWRP to make a Nandroid Backup (System+Data+Boot) of my current set-up
then, manually flash (using twrp) Android O
find out I don't particularly like it
Go back to TWRP and Nandroid Restore back to Android N, as if no update ever happened
Or will there be issues?
Thanks
I do that with freedomos. 2.17(N)>3.1(O)>2.17. I restore nandroid and reflash rom
xGOGI said:
I do that with freedomos. 2.17(N)>3.1(O)>2.17. I restore nandroid and reflash rom
Click to expand...
Click to collapse
Should have mentioned I'm using stock rom.
So I'd restore the nandroid via twrp, and I should be good to go?
arthritis said:
Used the search, used google, couldn't find any concrete answers
I am on Android N - unlocked bootloader - rooted via magisk, One Plus 3.
Could I do the following?
use TWRP to make a Nandroid Backup (System+Data+Boot) of my current set-up
then, manually flash (using twrp) Android O
find out I don't particularly like it
Go back to TWRP and Nandroid Restore back to Android N, as if no update ever happened
Or will there be issues?
Thanks
Click to expand...
Click to collapse
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Thank you for the detailed procedure.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Thank you
Hi @maxs8007
thanks for the instructions. I did all that to get back to my nougat rom (PureFusion) and all seem good and phone booted fine. But i am stuck on login screen after booted up. I tried my correct password several times but to no avail. anyway reset my password without factory resetting again?
Thanks for the advise.
sqlpro said:
Hi @maxs8007
thanks for the instructions. I did all that to get back to my nougat rom (PureFusion) and all seem good and phone booted fine. But i am stuck on login screen after booted up. I tried my correct password several times but to no avail. anyway reset my password without factory resetting again?
Thanks for the advise.
Click to expand...
Click to collapse
Go to twrp - advanced - file manager - go to root folder - data - system - and delete files with .key extension. There will be 2 files delete both and reboot.
maxs8007 said:
Go to twrp - advanced - file manager - go to root folder - data - system - and delete files with .key extension. There will be 2 files delete both and reboot.
Click to expand...
Click to collapse
Thank you very much and that worked. I am back in the system.
BTW in your original instructions I had to re flash rom after restoring twrp backup otherwise it didn't boot and stuck at rom animation.
sqlpro said:
Thank you very much and that worked. I am back in the system.
BTW in your original instructions I had to re flash rom after restoring twrp backup otherwise it didn't boot and stuck at rom animation.
Click to expand...
Click to collapse
Thanks for pointing out, I must have forgot to add it. I'll update again.
Hi @maxs8007
I ran into this issue again today! after unlocking as per instructions yesterday and am back into phone and re-set the pin and all good. But today i had to reboot the phone and same issue again , cant login on the lock screen!! i tried deleting those files again but to no avail!!
any ideas before factory reset and loose my data ? Thanks.
sqlpro said:
Hi @maxs8007
I ran into this issue again today! after unlocking as per instructions yesterday and am back into phone and re-set the pin and all good. But today i had to reboot the phone and same issue again , cant login on the lock screen!! i tried deleting those files again but to no avail!
any ideas before factory reset and loose my data ? Thanks.
Click to expand...
Click to collapse
This should not have happened, anyways delete all those files which I've highlighted in the image below. This will reset the lock settings.
Oh sorry I forgot to attach the file. Here it is.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Hi, OP here. Thanks for this guide.
Unfortunately, it did not work out for me.
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Done
Do factory reset(wipe everything except internal storage)
Wiped fine although I got an error of not being able to wipe 'USB-OTG' or whatever it's called. I ignored it and moved on.
then flash oreo twrp image.
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Then I rebooted and went back to recovery.
Flash oreo stock zip
flash oreo twrp image
Done
reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu.
This is where it ends. I get stuck at the OnePlus loading screen and forced reboot into twrp and flashed magisk. Once I boot up the OS, I get stuck at the OnePlus logo and that's it.
I actually re-did ALL of the steps again (in case I made a mistake) and still, the same issue. No progression.
Once I gave up on Oreo, I decided to go restore my nandroid
Reboot to recovery. Perform factory reset as mentioned above.
Wiped
Restore everything except bootloader, cache and dalvik cache
Here's the issue:
I press Restore (I uncheck both bootloader and cache, but there's no option for a specific dalvik cache- unless I'm not looking hard enough?) and I get the 255 Error.
Flash nougat twrp recovery. Reboot to system.
I tried to ignore that error and flash the twrp recovery.
Rebooted and it took me to fastboot. Regardless of I keep trying to reboot system it won't work.
I actually made two separate nandroid backups (the same 'everything except system image' as you've described) in case one of the backups was corrupted. Both backups ended up with the same error.
I got too tired of all these errors and just found a stock recovery and ROM and flashed it back. Now, all my apps and settings are gone. To be honest, I just want my phone back to where it was with Nougat.
Can anyone assist me?
@maxs8007, Like I said I did that already but nope still same issue. It wouldn't let me do matter what I did.
---------- Post added at 04:59 AM ---------- Previous post was at 04:54 AM ----------
arthritis said:
Hi, OP here. Thanks for this guide.
Unfortunately, it did not work out for me.
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Done
Do factory reset(wipe everything except internal storage)
Wiped fine although I got an error of not being able to wipe 'USB-OTG' or whatever it's called. I ignored it and moved on.
then flash oreo twrp image.
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Then I rebooted and went back to recovery.
Flash oreo stock zip
flash oreo twrp image
Done
reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu.
This is where it ends. I get stuck at the OnePlus loading screen and forced reboot into twrp and flashed magisk. Once I boot up the OS, I get stuck at the OnePlus logo and that's it.
I actually re-did ALL of the steps again (in case I made a mistake) and still, the same issue. No progression.
Once I gave up on Oreo, I decided to go restore my nandroid
Reboot to recovery. Perform factory reset as mentioned above.
Wiped
Restore everything except bootloader, cache and dalvik cache
Here's the issue:
I press Restore (I uncheck both bootloader and cache, but there's no option for a specific dalvik cache- unless I'm not looking hard enough?) and I get the 255 Error.
Flash nougat twrp recovery. Reboot to system.
I tried to ignore that error and flash the twrp recovery.
Rebooted and it took me to fastboot. Regardless of I keep trying to reboot system it won't work.
I actually made two separate nandroid backups (the same 'everything except system image' as you've described) in case one of the backups was corrupted. Both backups ended up with the same error.
I got too tired of all these errors and just found a stock recovery and ROM and flashed it back. Now, all my apps and settings are gone. To be honest, I just want my phone back to where it was with Nougat.
Can anyone assist me?
Click to expand...
Click to collapse
Buddy from my experience the whole thing too finicky and am thinking just factory reset and stick with stock rom. I wasted so much time already. Everytime I get different error, probably recoveries still not fully compatible with Oreo.
sqlpro said:
@maxs8007, Like I said I did that already but nope still same issue. It wouldn't let me do matter what I did.
---------- Post added at 04:59 AM ---------- Previous post was at 04:54 AM ----------
Buddy from my experience the whole thing too finicky and am thinking just factory reset and stick with stock rom. I wasted so much time already. Everytime I get different error, probably recoveries still not fully compatible with Oreo.
Click to expand...
Click to collapse
Could you please tell me what error you get on the lock screen? Could you post an image so that I can get a better idea of what's happening with your device? Also could you please confirm which files have you deleted? This time you need to delete 5 files which are related to lock screen setting and those are the only files responsible for lock settings on the device. I'm somewhat confused because I never ran into such issue while I did the oreo thing
If you have decided to flash stock then just make a backup of data partition so that you won't loose your data and you can easily restore it via twrp.
---------- Post added at 01:06 AM ---------- Previous post was at 12:42 AM ----------
arthritis said:
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Click to expand...
Click to collapse
I read the entire post and here what I've to say. The above quoted steps is where you went wrong. The recovery needs to to be flashed as a recovery and not as system.
In your case the nougat recovery was never replaced with the oreo recovery because you flashed it as a system. This is where it went wrong. Sorry for the dalvik cache and USB - otg, I didn't mentioned about them. Those are the least important points in flashing though I should have mentioned that already
The next thing you mentioned is you went back to recovery which at that moment was nougat recovery and not oreo recovery. I'll link the modded recovery I used for oreo below
The next thing you did is you flashed oreo zip and again flashed the oreo recovery but as you flashed the recovery as system, the oreo stock rom was automatically replaced with recovery because you flashed it as system and the device didn't boot because there was no android OS to boot up
You got stuck on oneplus boot up screen. (this was going to happen because of the same flashing error at your end).
You were unable to boot back to nougat as well because of the same issue.. Never flash the recovery as system. This won't let you boot the device.
To restore your nandroid backup just follow the steps below
As you confirmed you booted to stock rom with a stock recovery.
Flash nougat twrp via fastboot
Boot back to the twrp recovery and restore the nandroid backup and you are good to go
---------- Post added at 01:18 AM ---------- Previous post was at 01:06 AM ----------
I'll make a video in my free time to help you guys with the steps that I've followed to flash oreo rom and how i came back to nougat successfully.
Hello @maxs8007
Sorry I didn't have any screen shots of the prompt and finally I was fed up with the whole process and had to switch back to oreo stock rom.
Login prompt I was referring to was standard pin required load android. Black background with only pin entry.
BTW I tried blu twrp recovery oreo version and nougat version.
What's interesting is, after several failed attempts it said I got 10 more tries before phone wiped out but after 10 attempts it started counting backwards from zero, - 1,-2 etc., finally I had to flash stock recovery via fastboot and selected forgot password option which reset my phone.
BTW I have deleted all those files from data/system I found another thread but no dice.
Thank you for trying to help us all.
@maxs8007 followed your steps. Booted to oreo, didn't felt as stable as nougat then booted back to nougat. You saved me. Thanks.
sqlpro said:
Hello @maxs8007
Sorry I didn't have any screen shots of the prompt and finally I was fed up with the whole process and had to switch back to oreo stock rom.
Login prompt I was referring to was standard pin required load android. Black background with only pin entry.
BTW I tried blu twrp recovery oreo version and nougat version.
What's interesting is, after several failed attempts it said I got 10 more tries before phone wiped out but after 10 attempts it started counting backwards from zero, - 1,-2 etc., finally I had to flash stock recovery via fastboot and selected forgot password option which reset my phone.
BTW I have deleted all those files from data/system I found another thread but no dice.
Thank you for trying to help us all.
Click to expand...
Click to collapse
I'm sorry that I was unable to help you. The thing is I never used the pin prompt to load android because I reboot too often to flash things via recovery and its too much of a hassle to enter the pin everytime the device is booted and I think it's too much to a security for a android device when there's already a lock screen present once booted to secure the device.
Please don't put the pin entry to load android next time if you flash stuff regularly. It will save you the hassle of going back to stock rom and recovery when something like this ever happens again. The files which I told you to delete in the image I posted above remove the lock screen protection completely
The login pin at the boot to load android was implemented to avoid unauthorized access to the device in case it gets stolen or lost.
maxs8007 said:
I'm sorry that I was unable to help you. The thing is I never used the pin prompt to load android because I reboot too often to flash things via recovery and its too much of a hassle to enter the pin everytime the device is booted and I think it's too much to a security for a android device when there's already a lock screen present once booted to secure the device.
Please don't put the pin entry to load android next time if you flash stuff regularly. It will save you the hassle of going back to stock rom and recovery when something like this ever happens again. The files which I told you to delete in the image I posted above remove the lock screen protection completely
The login pin at the boot to load android was implemented to avoid unauthorized access to the device in case it gets stolen or lost.
Click to expand...
Click to collapse
Frankly no clue why deleting those files didn't reset my pins and I even deleted gatekeeper files too.
Maybe these are lock screen key files and android boot prompt stored somewhere else. Not sure though.
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
Hey everyone. Tried to flash a custom ROM for the first (and maybe last time) on the Mi5s from China Stable V10.2 to Lineage OS16. I think i did everything correctly at first
Unlocked the bootloader with Mi Unlock, put the SDK tools into ADB folder, flashed TWRP with command prompt, made a backup, wiped data, disabled force encryption, MAGISK root, flashed Mi5s firmware (although I could only find Oreo), LOS16 (Pie), and OpenGApps
I did all of that and got stuck on the LOS boot animation. Then I wiped data + cache partitions and tried again (didn't work). I quit trying with LOS but instead tried to flash the MIUI Global Stable recovery ROM with TWRP, also only made it to the boot animation. I then did a factory wipe on TWRP and tried to restore my backup but now it would only boot to the fastboot (not even trying to load the ROM)....... I can still access TWRP so maybe I'm not so screwed but what do I do? I just want a functioning device and don't mind if I go back to China Stable although advice on trying to flash a custom ROM would be appreciated. Thanks!
After flashing MIUI 11 beta I decided to go back to crDroid. Restored backup via twrp but it wouldn't boot, just booted into recovery, but twrp wouldn't decrypt data. I've seen this before and solved it by adb sideload crdroid rom (maybe because it includes vendor?). I tried this and now it just boots straight into fastboot. I tried fastboot boot twrp.img and that says "failed to load/authenticate boot image". What should I do?
Edit: After using miflash I can get back to stock, and then use fastboot to flash twrp. Twrp still doesn't ask for password to decrypt data. Every time I try to adb sideload crdroid.zip i end up stuck with fastboot again and have to miflash!?
Full wipe in TWRP and format data partition
reboot in recovery
flash crdroid and flash magisk
flash vmbeta after rom
I tried full wipes including data and flashing crdroid. I've also tried flashing vbmeta at multiple points.
Even after flashing back to stock miui with miflash android wouldn't boot, instead it just loaded miassistant (miui recovery). I'd have to flash twrp again, try flashing a new system and it would always reboot to fastboot.
The only solution has been to flash back to miui 11 beta (android 10) which boots fine. I'm still not sure whats going on but I'm ok with miui for now.
Deleted due to double post
briandarrel said:
I tried full wipes including data and flashing crdroid. I've also tried flashing vbmeta at multiple points.
Even after flashing back to stock miui with miflash android wouldn't boot, instead it just loaded miassistant (miui recovery). I'd have to flash twrp again, try flashing a new system and it would always reboot to fastboot.
The only solution has been to flash back to miui 11 beta (android 10) which boots fine. I'm still not sure whats going on but I'm ok with miui for now.
Click to expand...
Click to collapse
Solution mil kya bhai