Phone automatically updated to 12.0.1.0 last night, and I can not get it to boot back to TWRP, LR LWRP or Orangefox.
When it wants to boot to the recovery after holding power and up, it just black screens for a few seconds and reboots, then boots back into MIUI.
Am I doing something wrong or has something changed with this version, and the recoveries need to change something?
Thanks
So i found that only 1 version on LR TWRP actually boots
TWRP-3.3.2B-0305-REDMI_NOTE8PRO-CN-wzsx150.img
https://androidfilehost.com/?fid=8889791610682889486
After this, just follow all the normal steps, like format all data and close AVB, and you are up and running
Related
My phone was a bit erratic and I decided to reboot it. Before that I installed a new Magisk Manager version, updated a module and uninstalled another (I should've had done one step a time, I never learn). After all this I rebooted and my phone no longer booted. the HTC logo shows up and then the screen becomes blank and nothing shows up.
I can reboot it pressing the Power + Volume Down buttons for 10-15 seconds, I can boot to bootloader, dowload mode and and recovery. The phone charges just fine in recovery or powered down. If I let it try to boot for a while and attempt "adb devices", nothing shows up, so I can't invoke "adb logcat" and see if it's in a boot loop or something. It's hard to debug and understand what's wrong.
Flashed Magisk Uninstaller, still doesn't boot. Another mistake is that I don't have a backup, yes, I'm an idiot. I don't understand why I keep living on the edge like this...
I use MaximusHD ROM and I'm now thinking of reinstalling this on top of my current installation to see if it fixes anything, as a last resort because I can't think of anything else. Thoughts?
rfgamaral said:
My phone was a bit erratic and I decided to reboot it. Before that I installed a new Magisk Manager version, updated a module and uninstalled another (I should've had done one step a time, I never learn). After all this I rebooted and my phone no longer booted. the HTC logo shows up and then the screen becomes blank and nothing shows up.
I can reboot it pressing the Power + Volume Down buttons for 10-15 seconds, I can boot to bootloader, dowload mode and and recovery. The phone charges just fine in recovery or powered down. If I let it try to boot for a while and attempt "adb devices", nothing shows up, so I can't invoke "adb logcat" and see if it's in a boot loop or something. It's hard to debug and understand what's wrong.
Flashed Magisk Uninstaller, still doesn't boot. Another mistake is that I don't have a backup, yes, I'm an idiot. I don't understand why I keep living on the edge like this...
I use MaximusHD ROM and I'm now thinking of reinstalling this on top of my current installation to see if it fixes anything, as a last resort because I can't think of anything else. Thoughts?
Click to expand...
Click to collapse
I can't speak to your specific issue with Magisk but you should easily be able to return to stock by flashing Maximus, or by running an RUU from your sdcard. The ruu will wipe your phone completely
Tarima said:
I can't speak to your specific issue with Magisk but you should easily be able to return to stock by flashing Maximus, or by running an RUU from your sdcard. The ruu will wipe your phone completely
Click to expand...
Click to collapse
Tried to reflash Maximus, didn't work, still didn't boot. Backed up everything I could and wiped everything, I'm now on Lineage OS 16.0. Thanks for your reply.
So I recently changed my Xiaomi Mi MIx 2 screen (the one before was broken) and I wss using LineageOS 16 with TWRP.
The problem is that, after I changed the screen, I could not boot back to LineageOS because I was stuck in a grey screen (after booting the phone I am able to see the Mi logo and the LineageOS loading animation, but after that nothing).
I tried to do a Wipe from the TWRP, but whenever I try to open the recovery I get stuck again with a grey logo... (and in the recovery it does not even shows the TWRP logo, just straight the grey screen). I am still able, however, to go in Fastboot mode and I do have an unlocked bootloader
So my question was... does anyone encounteredd the same problem? And does anyone know how to fix it?
Can I perhaps just use the Mi Flash tool from fastboot to go back to stock MIUI without first wiping from TWRP things like Dalvik cache, cache, System ecc... or would this method fail/brick my phone?
Thank you a lot to anyone that would spend time to help me (and sorry for my bad English, I am trying to improve it).
Have a nice day!
The mi mix2s rewrites a new recovery after every boot, so to get TWRP to work you have to flash it from fastboot every single time. So the next time you boot, reflash TWRP, then you can boot into recovery 1 time and flash the rom of your choice
Hi Guys,
Recently i'm changed my broken display of Mix 2 after that when i'm entering to recovery it showing a gray screen also the phone is detecting on PC.
some TWRP worked but after flashing custom ROM same as showing gray screen after finished boot also doing second try the touch not working on TWRP.
Now i'm using Global version of MIUI11, when flashing custom TWRP via FASTBOOT MODE its booting up but after that restarting the phone revert back to the stock Recovery. Earlier i'm used the final version of MIUI12 Weekly EU ROM
Guys if you know any workaround for this please help me to get rid out of this
Thanks in Advance
Well, I will be straightforward... I'm probably pretty much f**ked.
I have a Xiaomi Redmi 5A which was never tampered with, ever. It had Android Oreo 8.1, MUIU 10, never rooted, never unlocked. It was my wife's. She bought a new phone and now I wanted to use this Redmi 5A.
So I intended to flash a custom ROM on it. I did my research and picked Ancient OS for the custom ROM (https://forum.xda-developers.com/t/rom-10-0-0_r39-official-ancientrom-civilization.4113993/).
I started all the work. First, unlock bootloader. I used MIFlash unlock provided by Xiaomi itself. Followed all the steps and unlocked the bootloader. After this it was time to flash a custom recovery. I chose TWRP. Tried to use their own TWRP riva image (twrp-3.5.0_9-0-riva.img) but it didn't worked. Whenever I flashed, after rebooting, the stock recovery would overwrite TWRP. This was supposedly because this version of TWRP was based on Nougat and my phone was on Oreo, so I searched a bit more and found a guy who has modified TWRP to work with Oreo. I flash his version and flashed lazyflasher afterwards et voilà! The TWRP installed correctly and was no long overwritten by stock recovery.
After this I made a FULL backup of the stock ROM using TWRP (System, Cust Vendor, Data, Boot, Bootloader, EFS, Persist, Logo) and stored the backup on my computer.
Then I proceed to flash the Ancient OS ROM. First I went to wipe on TWRP > format data > yes. After this I went to wipe again > advanced and selected to wipe Dalvik, Data, System, Cust Vendor, Cache. And finally then, to install and flash the ROM. Things were a bit weird here because when I tried to flash TWRP threw Error 7 which is related to a script protection to determine if the ROM is compatible to your phone. The thing is... the ROM was compatible. I checked the "updater-script" inside the ROM file the code lines to check for the device were correct, it displayed riva as the model, which is my phone. One of the solutions to Error 7 was to eliminate these lines from the script, which I did and so I was able to flash the ROM. Everything went well and reboot to system.
System boot up, splash screen, main screen. All were good. Device timed-out and the screen locked. After the screen lock the only thing appearing were bizarre vertical red lines. Phone was still responsive, but screen was not being rendered properly. Forced reboot, splash screen... and main screen again, all normal. Tested to lock to notice the screen error again, and there it was: red lines just after I locked. Rebooted once again... only this time I went stuck on bootloop (on logo). Decided to boot to recovery to restore things, but, for my astonishment TWRP didn't started. The TWRP logo appeared as if it was loading, but nothing happened and if I leave it like this for some minutes, it just reboots to recovery once again but without TWRP being able to initialize and keept stuck on this reboot to recovery loop.
I don't have the slightest idea how can the recovery be affected by a ROM flash, seriously... I never saw this. It is a completely different partition. Worst of all, everything on TWRP was working before flashing the Ancient OS ROM.
I have no idead what to do. Can't enter system, can't access TWRP and can't use fastboot (most likely because USB debugging was disabled after OS was flashed). If some one can shed some light... it would be truly appreciated.
Auto-reply... Solved this issue flashing the original Stock ROM (I mean the Stock ROM that came with the phone back in 2017; before ANY updates.) with the own Xiaomi Mi Flash.
Be advised: This Xiaomi tool only works with devices that have unlocked bootloader.
/EDIT:
Alright, the thread can be closed. I somehow managed it.
In case someone faces the same issue, I used twrp to dd the sdf files back on the phone which stopped the reboots. After that, just wiped and formatted everything again and reinstalled the ROM.
Hello guys,
I hope you can help me with this issue since I've tried everything I know to fix this problem.
The plan:
Unlocking bootloader, installing TWRP and xiaomi.eu ROM on a new device.
Changing its IMEI with QPTS/QFIL afterwards.
What happened:
Unlocked successfully. Installed TWRP, xiaomi.eu ROM and Magisk.
After pulling the QCN backup and editing the file I pushed it back to the phone what seemed to work.
After rebooting, I noticed that the phone rebooted 5 seconds after showing me the "Enter PIN" screen.
Booted up again and the same thing happened.
I booted into TWRP, wiped and formatted "data", installed the ROM again. The phone started up normally and there was no reboot.
I went back to TWRP and flashed Magisk, the phone crashed again and everytime I boot it up, it immediately reboots after some seconds. Installing Magisk somehow triggers the phone to reboot on its own.
I thought to start over, flashed everything from stock using Mi Flash Tool and the newest China Rom.
After starting up the phone, the issue still exists. This time with this rom there is no difference between installing Magisk or not, the phone always reboots after showing up the miui welcome/setup screen.
Current situation:
The phone boots up Android, reboots after some seconds and goes into fastboot automatically. After the fastboot timeout it again reboots automatically, goes into the OS and crashes again and on and on.
No matter what I do, I can't keep the phone from rebooting.
And since I can't flash Magisk, I have no root.
This means that I can not use root to put the phone into diag mode to restore the original qcn file.
I have backups of the EFS partition and also sdf7/8/9/10 files. I just don't know how to restore them given the current situation.
Thank you very much in advance for your support!
Cheers
My telephone keeps booting to fastboot after trying to update TWRP.
I am trying to restore the original ROM (apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea) and I can get the rom installed through fastboot but the phone enters a boot loop cycle. It starts up, vibrates shortly then reboots.
If i press volume up it goes into the original recovery menu. I have tried clearing everything and even entering safe mode but the phone will not boot.
Am i screwed?
Thanks in advance.
I installed the Pixel Experience recovery and side-loaded the zip and at least have a working OS.
I must be doing something wrong with the stock mi10t
Now i sided the miui zip and its working agian. I think i have misunderstood the procedure. I thought you only need to install the rom with flashboot and that was it.