Related
I installed CM 11 on my Xiaomi redmi 1s,everything was working fine except for 2 or 3 little things but a major problem occurred when I thought of flashing another ROM and now I CANT ACCESS RECOVERY MODE no matter what I try. I tried the button combination(power switch+volume up), tried adb and even tried apps like ROM Manager and, TWRP Manager and quick boot but haven't found any luck. Whenever I try to boot into recovery the phone gets stuck on the MI boot logo. I need to flash another rom and can't seem to find any other way to wipe y phone data, cache and dalvik cache and so I need help to counter this issue.
Please help me.
Dishagra said:
I installed CM 11 on my Xiaomi redmi 1s,everything was working fine except for 2 or 3 little things but a major problem occurred when I thought of flashing another ROM and now I CANT ACCESS RECOVERY MODE no matter what I try. I tried the button combination(power switch+volume up), tried adb and even tried apps like ROM Manager and, TWRP Manager and quick boot but haven't found any luck. Whenever I try to boot into recovery the phone gets stuck on the MI boot logo. I need to flash another rom and can't seem to find any other way to wipe y phone data, cache and dalvik cache and so I need help to counter this issue.
Please help me.
Click to expand...
Click to collapse
Flash any custom recovery via fastboot mode
Download .img format of custom recovery
Boot into fastboot mode n run this command on CMD
fastboot flash recovery <filename>.img
Filename can be anything depending on name of image file you download
Not Working for me
RajGopi said:
Flash any custom recovery via fastboot mode
Download .img format of custom recovery
Boot into fastboot mode n run this command on CMD
fastboot flash recovery <filename>.img
Filename can be anything depending on name of image file you download
Click to expand...
Click to collapse
I am afraid this solution doesn't work for me. My thoughts are that I have somehow lost my recovery partition. I accidently installed CM 11 without first installing a custom recovery. My bad! but have yet to find a solution that works.
Try flashing a recovery using Rashr-flashtool
And boot to recovery (Vol up + Power , for 10s even after screen is on )
Solved
Shahi00 said:
Try flashing a recovery using Rashr-flashtool
And boot to recovery (Vol up + Power , for 10s even after screen is on )
Click to expand...
Click to collapse
I solved my problem by using Flashify app but I had to use it every time as recovery would not stick. I flashed trwp and installed stock (english version) rom and stock recovery and everything is working fine again. I will not make the same mistake again. I have since installed CWM recovery through stock recovery so now I can flash roms in peace again.
Waxwrong said:
I solved my problem by using Flashify app but I had to use it every time as recovery would not stick. I flashed trwp and installed stock (english version) rom and stock recovery and everything is working fine again. I will not make the same mistake again. I have since installed CWM recovery through stock recovery so now I can flash roms in peace again.
Click to expand...
Click to collapse
i have the same problem how to solve it please describe it briefly ^^
Hi
While flashing CM13 on my redmi 1s, I did a clean install, meaning wiping everything, and then when I went to flash CM13, TWRP just reboots the moment I swipe to install. This happens with any .zip file.
I installed CWM using fastboot, and that gives me the same problem. The moment I try to flash/install anything using a recovery, that recovery reboots and doesn't flash anything. My device is now useless since it doesn't have an OS installed and no way of doing so..
From what I can tell the system partition is bad because when I boot into recovery it isnt mounted
When I take out the battery now it just goes straight to the fastboot screen. I can take it into recovery but it goes to fastboot by default
Please help
Hi dude,
i guess you have checked the integrity of your cm13 ROM file and (winrar>test archive) , your best bet would be flashing a fastbootrom and then come back to cm. Head over to miui and download latest fastboot rom applicable to you.
And its usual booting into fastboot when there is no OS installed atleast for our device so chill dont loose hopes..!
vbvn said:
Hi dude,
i guess you have checked the integrity of your cm13 ROM file and (winrar>test archive) , your best bet would be flashing a fastbootrom and then come back to cm. Head over to miui and download latest fastboot rom applicable to you.
And its usual booting into fastboot when there is no OS installed atleast for our device so chill dont loose hopes..!
Click to expand...
Click to collapse
Flashing the fastboot rom doesn't work.. My recovery is broken too, because I can't flash anything.. In either MiRecovery 2.0.1, CWM or twrp.. When I flash the MIUI rom via fastboot it just boots into recovery..
EDIT, I just got it into MIUI but the 4.3 version from china, without Google, and I can't download google via the MI market. So i'm downloading an international version now and will try to flash using MiFlash.
Does anyone know how I can fix the recovery? It still won't flash anything and reboots the moment I try to.
Edit: solution added
problem:
after flashing a rom (in my case OP3lite or FreedomOS) you can't get past the boot logo
you have access to TWRP, so you can restore nandroid or flash flashable stock OxygenOS packages (tutorial here)
solution:
wipe: Dalvik /ART Cache, Cache, Data, System
flash your rom
try to boot (most likely will get stuck at boot logo)
boot into TWRP > Advanced > Fix Contexts, and swipe to Fix Contexts
Reboot
(wait a while, it might take a few minutes till it boots)
___________________________________________
original post:
hi,
I'm running official OxygenOS 3.1.3.
Rooted (systemless) , TWRP installed.
I don't have any problems on my rom, but everytime I flash a rom I get stuck at the boot logo.
I can just force reboot, goto twrp and restore my nandroid backup, and my phone works fine again.
But I can't flash any rom.
tried this:
Dirty flash OP3Lite rom - stuck at boot logo
wipe and install OP3Lite rom - stuck at boot logo
Restored nandroid backup, factory format, wipe and install OP3Lite rom - stuck at boot logo
wipe and install FreedomOS - stuck at boot logo
Restored nandroid backup, factory format, wipe and install FreedomOS - stuck at boot logo
wipe, Format userdata throught fastboot, install FreedomOS - stuck at boot logo
update to OxygenOS 3.2.1 (flashable zip throught twrp)
wipe and install FreedomOS - stuck at boot logo
Both roms I tried are OxygenOS 3.2.1 stock based, my problem is most likely not due to the rom I want to flash.
Anyone knows a solution for this?
is it possible that systemless root causes this problem?
are you encrypted? that might be the issue.
backup your internal sd data then go to fastboot and fastboot format userdata then flash the rom you want
Abaddon said:
are you encrypted? that might be the issue.
backup your internal sd data then go to fastboot and fastboot format userdata then flash the rom you want
Click to expand...
Click to collapse
I never did format my userdata throught fastboot, so I might be encrypted.
I'll try tomorrow and let you know if that was the solution.
@Abaddon I format my userdata throught fastboot (fastboot format userdata), but still roms wont go past the Logo . any other idea?
did you full wipe?
wiped /system too before flashing a rom then u go and flash the rom + gapps if needed
how long was it at the boot logo? no animation correct?
did u advance wipe - data, caches, system instead of factory wipe, try it 3 times
I did a few wipe 3 times, still stuck at logo.
I get stuck on this logo, never reboot, just get stuck there.
I noticed that it does flash the rom, cause if I restore my nanodroid backup layers and adblock is added.
I also get zero error while flashing in twrp.
I fixed it .
did a fill whipe, then flashed feedomOS, then tried to boot, didnt get past the logo, booted into recovery, selected "fix Contexts" and then rebooted, started without any problem .
doesent work for me..!! any help
Same here this issue keeps occuring again and again. then i always have to follow mega unbrick guide
Resurrection ROM 7.1.1 stuck at logo after every restore
nikhilsnigam said:
Same here this issue keeps occuring again and again. then i always have to follow mega unbrick guide
Click to expand...
Click to collapse
Faced this issue every time I restore any nandroid on one plus 3. It stucks at rotating resurrection logot . Even tried fix contents from TWRP, no output. Please help without a functional TWRP backup and restore - phone is useless. Only everytime mega unbrick guide needs to be repeated with painful reinstall of apps
hello guys. sorry if I'm a bit slow on this topic. I'm using the the op3t A3010 version (not dure whether I'm at the right forum or not lol) Recently I updated my phone to the new 4.1.7, in which I had already rooted the phone before with magisk v12. But right after the update, as usual, the phone will unroot and yes I did root the phone back by using the magisk v13.0 version. But it failed the safety net. So after a few 'research', I installed the superuser just in case that the safety net will work this time. But this is when it all went wrong. The phone did restart back to factory settings, but the phone is not rooted (checked by using the rootchecker app) So again, I'm back to the twrp recovery, clean wipe all the data, with hope that I can start from scratch which is from installing the magisk all over again. But after this step, it stuck at the boot logo for like more than half an hour. Than at this moment, I restart my phone back to recovery mode by long pressing the power button, and when I try to install both the magisk 12 and 13 version, there is a line of error code on the screen. There's a site that says simply go to the advance setting on the twrp interface, check fix contents and ur phone will be as good as new. After done doing that, I'm now stuck with a phone with no os installed and about 38% battery left. Can anyone help me here? This is the only phone that I had :crying: Urgent help needed here guys
Unless your original installation is without storage encryption (no dm-verity) this will happen. So next time install custom rom after flashing OB22 firmware+modem, then boot patch for dm-verity followed with custom rom and gapps then boot without wipe
i have the same problem but with p9 lite : when i tried a flash lineageOS or ResurrectionRemix my phone stucks at boot logo and when i flash the original os my phone works perfectly
sorry for my english
washichi said:
I fixed it .
did a fill whipe, then flashed feedomOS, then tried to boot, didnt get past the logo, booted into recovery, selected "fix Contexts" and then rebooted, started without any problem .
Click to expand...
Click to collapse
How long did you wait?
washichi said:
Edit: solution added
boot into TWRP > Advanced > Fix Contexts, and swipe to Fix Contexts
Reboot
(wait a while, it might take a few minutes till it boots)
Click to expand...
Click to collapse
What is the work around for CWM v6.0.5.1 Philz Touch6; it does not have Fix contexts under Advanced Functions
My issue: Tecno Spark K7 stuck at boot logo after flashing with ported ROM from Infinix XOS Chameleon . Both kernels match
This is EXACTLY my issue with the galaxy s9 plus. Gonna try the solution you wrote tommorow.
i have the same problem with galaxy s5 and the solution mentioned in the thread did not work with me.
im having the same issue but in lenovo z5 pro gt
PauloVillaflor said:
im having the same issue but in lenovo z5 pro gt
Click to expand...
Click to collapse
Search for answers HERE and if not successful, create a thread in the Q&A forum there.
You may not get any help here since this is the OP 3 forum.
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
My bootloader is unlocked.
After installing PIE update to MIUI Global 10.3.1.0 Stable, when I try to boot OrangeFox recovery ver. R9.0-2 for Whyred using fastboot command "fastboot boot recovery.img" in CMD ( the result is shown below), the phone does NOT boot in OrangeFox recovery. It just remain stuck on MI logo after booting ...
C:\platform-tools>fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.951s]
booting OKAY [ 0.157s]
Finished. Total time: 1.158s
Kindly advise on how to resolve the issue
Did you temporarily deactivate the Anti-Rollback-Feature with
>fastboot flash antirbpass dummy.img
where you will find the dummy.img in the official download of the Xiaomi firmware before trying to boot into recovery?
This needs to be done in the same fastboot-session that you want to boot into recovery.
NOTE 5 PRO Soft Bricked recovery bootLoop after MIUI Pie 10.3.1 Global Stable update
One more!! Hello i have a note 5 pro, yesterday it received automatic OTA update of miui 10.3.1.0.PEIMIXM with android 9.0, after install it soft bricked saying this miui version cant be installed on this device.
it lets me wipe data, which didnt help, also i connect with mi assistant using my pc suite nothing works, pc suite wont even recognize the phone on windows 10,.
PLEASE HELP! !
Kindly advise on how to resolve the issue[/QUOTE]
JosephusQuint said:
Did you temporarily deactivate the Anti-Rollback-Feature with
>fastboot flash antirbpass dummy.img
where you will find the dummy.img in the official download of the Xiaomi firmware before trying to boot into recovery?
This needs to be done in the same fastboot-session that you want to boot into recovery.
Click to expand...
Click to collapse
Many thanks for the advice. Worked like a charm. :good:
No, I did NOT deactivate the Anti-Rollback-Feature which was causing the problem.
In the past, whenever I installed custom recovery on my device including the first time, I did NOT have to flash dummy.img as my device booted into custom recovery without flashing dummy.img.
P.S.: I used dummy.img from this thread:
Everything About Anti Roll-back [Whyred]
ExoticPoint said:
One more!! Hello i have a note 5 pro, yesterday it received automatic OTA update of miui 10.3.1.0.PEIMIXM with android 9.0, after install it soft bricked saying this miui version cant be installed on this device.
it lets me wipe data, which didnt help, also i connect with mi assistant using my pc suite nothing works, pc suite wont even recognize the phone on windows 10,.
PLEASE HELP! !
Kindly advise on how to resolve the issue
Click to expand...
Click to collapse
ONLY IF you have Unlocked-Bootloader, then you can use this MIUI Flashing Guide- Method 2: Fastboot Update to unbrick your device.
Please carefully chose the firmware version (Global / India) to download the fastboot stock ROM for your device.
Lahoria said:
Many thanks for the advice. Worked like a charm. :good:
No, I did NOT deactivate the Anti-Rollback-Feature which was causing the problem.
In the past, whenever I installed custom recovery on my device including the first time, I did NOT have to flash dummy.img as my device booted into custom recovery without flashing dummy.img.
P.S.: I used dummy.img from this thread:
Everything About Anti Roll-back [Whyred]
Click to expand...
Click to collapse
Great that it solved your problem!
As addendum: The Anti-Rollback (afaik) has to be disabled every single time the recovery is changed/updated. This caught me off guard as I wanted to update TWRP from within the offical TWRP app. This failed and made my recovery unusable (Although I could still normally boot into system).
So let this be a cautionary tale to people.
I can't boot to my custom recovery in my redmi note 5. it is booting to the original recovery. I tried TWRP and REDWOLF recoveries . It will boot in the first time, then I reboot my phone after that when I reboot, it is booting to the original recovery. Same happened when I tried RED WOLf recovery. Pls help me.
Ayyappadas said:
I can't boot to my custom recovery in my redmi note 5. it is booting to the original recovery. I tried TWRP and REDWOLF recoveries . It will boot in the first time, then I reboot my phone after that when I reboot, it is booting to the original recovery. Same happened when I tried RED WOLf recovery. Pls help me.
Click to expand...
Click to collapse
After flash twrp, just flash magisk zip through twrp recovery...