I was on Pixel experience. wanted to flashed MIUI 10 PIE build its successfully installed but stuck on MI logo also installed lazy flasher.
Changed many Recoveries but stuck on mi logo. what to do?
Haxnainalee said:
I was on Pixel experience. wanted to flashed MIUI 10 PIE build its successfully installed but stuck on MI logo also installed lazy flasher.
Changed many Recoveries but stuck on mi logo. what to do?
Click to expand...
Click to collapse
install miui 10.3.1 oreo based first after that install miui 10.3.1 pie based.
Sent from my Redmi Note 5 Pro using Tapatalk
Install via Mi-Flash not TWRP.
kind of same thing happend to me
i was on havos os decided to switch to miui.eu was not satisfied with battery performance so decided to flash citrus-caf errors pop up all over the place .....bricked the phone .flashed miui via edl then flashed the latest miui global ROM as I needed the phone urgently
Fee days later when I flash any custom ROM thrust zone error pops up in recovery and I am not able to format my /cust partition I can't even flash the miui Oreo ROM it goes for an infinite boot animation
I am able to flas custom roms if I flash the miui pie firmware files but it won't boot up infinite boot animation .....
If anyone can understand why this is happening please help me
Thanks in advance
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo
Click to expand...
Click to collapse
I think that i figured out something, I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Did you try reflash twrp latest version?
Hello,
i'm stuck in a particular situation: i can use fastboot and i can flash recoveries but none of them can succesfully flash a rom. i want to go back to the stock Realme UI, my device is RMX1993.
i tried to follow the guide (https://forum.xda-developers.com/realme-x2/how-to/to-stock-rom-howto-t4014773) but the last recovery (rmx1993-sde20-stock_recovery-c05) can't flash neither RMX1993EX_11_OTA_1040_all_tSZ3Sf5A77NS nor RMX1993EX_11_OTA_1050_all_loALrMDyMrbs.
tried to flash trough orangefox or the last twrp that support ozip decription but the result is a "succesful flash" but a phone that does not go over the boot screen and it reboot.
i succesfully installed color os trough the proper old stock recovery and it said the installation was succesfull, but the problem was the same.
someone know where could be the problem?
You need to successfully flash Android 10 (Realme UI 1.0) before you can flash custom Android 10 roms.
Have you tried this guide: https://forum.xda-developers.com/realme-x2/help/how-to-flash-q-firmware-based-roms-t4115987
As for why your colorOS back up is not working i'm not quite sure...have you wiped your cache before booting to the color os backup?
I have a strange and weird behavior with flashing custom rom by twrp
I have two RN8 Global phones
- batch 07-2020 64GB A9 Miui 11.09
- batch 11-2020 128GB A9 Miui 11.011 board ID 3.29
The first one I have flashed without problems with RR official in august and updated till the last from DqrKn3Zz.
The second flashed without any error in twrp, but refuses to boot in twrp or system,
Screen went black, pushing powerbutton does lcd backlight only short flashing. usb isn't recognized.
Only solution is testpoint, edl flash with qfil.
What are the differences with flashing:
- Miui version
- Board ID, I think
- Storage 128Gb vs 64GB
- Twrp 3.5 vs 3.4
- Twrp flashing rom from external SD card vs internal storage
- FW and RR version are for both devices the same, the FW 12.01 Global and last RR 8.6.4 from DqrKn3Zz
- The first one I started with RR8.5.8 and FW 20.8.27 CN, but don't dare to flash CN FW anymore
I followed the instructions for unlocking, twrp and FW and RR flashing, but get always a flashing screen and fastboot isn't possible anymore.
In the past I haved flashed about 12 different Xiaomi phones, but this is the first time I am out of ideas how to solve this.
My suspicion is that something is or isn't changed in the booting process with flashing FW.
Tried different scenarios like, partly flashing and starting to twrp again.
I can flash and start twrp, flash magisk, decrypt etc. but if I flash FW and Rom that ended it.
I have formatted data, wipe system, caches and vendor etc. but no succes
Testpoint/EDL I have used 5 times to recover Miui 11 again, without problems or sahara error
With starting Miui, my account is still there, I only have to activate it and bootloader is still unlocked.
The last thing I can try is flash only RR and no FW, but I don't know if it is possible to flash A10 custom on A9 FW
Or official update to Miui 12 - A10 and try to flash custom rom only.
But I am afraid that if there is again a brick, the EDL solution won't work.
Has anybody some other ideas what I can do?
Answer my own question:
The headache is over
At last I found the reason of this brick.
It is impossible to flash Miui 12.0.1 with recovery on Miui 11.0.11
Only with Miui 11.0.11 you must flash Miui 12.0.1 with fastboot
The first version which you can flash with recovery is Miui 12.0.2
I didn't know this because I never intended to use Miui.
After a search I found a source for this information
Installed RR8.6.7 with FW 12.03 without problems
Elinx said:
I have a strange and weird behavior with flashing custom rom by twrp
I have two RN8 Global phones
- batch 07-2020 64GB A9 Miui 11.09
- batch 11-2020 128GB A9 Miui 11.011 board ID 3.29
The first one I have flashed without problems with RR official in august and updated till the last from DqrKn3Zz.
The second flashed without any error in twrp, but refuses to boot in twrp or system,
Screen went black, pushing powerbutton does lcd backlight only short flashing. usb isn't recognized.
Only solution is testpoint, edl flash with qfil.
What are the differences with flashing:
- Miui version
- Board ID, I think
- Storage 128Gb vs 64GB
- Twrp 3.5 vs 3.4
- Twrp flashing rom from external SD card vs internal storage
- FW and RR version are for both devices the same, the FW 12.01 Global and last RR 8.6.4 from DqrKn3Zz
- The first one I started with RR8.5.8 and FW 20.8.27 CN, but don't dare to flash CN FW anymore
I followed the instructions for unlocking, twrp and FW and RR flashing, but get always a flashing screen and fastboot isn't possible anymore.
In the past I haved flashed about 12 different Xiaomi phones, but this is the first time I am out of ideas how to solve this.
My suspicion is that something is or isn't changed in the booting process with flashing FW.
Tried different scenarios like, partly flashing and starting to twrp again.
I can flash and start twrp, flash magisk, decrypt etc. but if I flash FW and Rom that ended it.
I have formatted data, wipe system, caches and vendor etc. but no succes
Testpoint/EDL I have used 5 times to recover Miui 11 again, without problems or sahara error
With starting Miui, my account is still there, I only have to activate it and bootloader is still unlocked.
The last thing I can try is flash only RR and no FW, but I don't know if it is possible to flash A10 custom on A9 FW
Or official update to Miui 12 - A10 and try to flash custom rom only.
But I am afraid that if there is again a brick, the EDL solution won't work.
Has anybody some other ideas what I can do?
Click to expand...
Click to collapse
i flashed over 250 rom on my 128gb variant without a single problem
i always flash rom + dfe + format sometimes if required
about 100 rom with twrp
and the rest with orangefox
i was on OFox when i flashed miui12 but the phone booted normally
maybe because i have "Aggressive stock recovery deactivation" option enabled ...
i don't like to flash FW a lot
they seem to be N1 problem source for ginkgo ...
I too have a lot of experience with flashing (not 250+), but becasue I stay far away of Miui I didn't know of this incombabilty with Miui 11.0.11 and recovery-flash of 12.0.1 Firmware. Older versions of Miui 11 hadn't this problem.
For me this was the first time I had such a problem.
If I had flashed the latest RR ZhanTech version immediately, I wouldn't even have noticed this problem.
But the first RN8 is in use by my wife and isn't completely flawness.
With the second one I had planned to experiment first with some solutions for that,, because I could always back to base.
Luckely I choose always a Xiaomi which has a lot of development for it, so mostly is this an older type and never the newest.
In this case it was very easy to flash back with EDL and patched firehose file.
Elinx said:
I didn't know of this incombabilty with Miui 11.0.11 and recovery-flash of 12.0.1 Firmware.
Click to expand...
Click to collapse
maybe because it "patch" the custom recovery ???
anyway, i will never back to miui unless i want to sell it
and i think the best way is flash a custom rom based on miui
loopypalm said:
maybe because it "patch" the custom recovery ???
..
Click to expand...
Click to collapse
No, with Miui OTA you flash with Xiaomi recovery, but before you get a warning 12.01 is incompateble and recovery doesn't start.
Directly with twrp, you don't get this warning and also you don't get any flashing error.
That is why I didn't expect that it was of incompatiblity of the FW.
One of the last things I did was flashing rom, magisk etc and started between to system.
As last I flashed 12.01 FW and got a brick.
After this I was searching for this problem and there where complains about a brick with flashing the new Miui 12 with twrp.
I was afraid that I couldn't flash new FW, but then I found that it is only with FW 12.01....... flashing 12.02 and 12.03 give no problems.
Elinx said:
flashing 12.02 and 12.03 give no problems.
Click to expand...
Click to collapse
with twrp you mean ?
loopypalm said:
with twrp you mean ?
Click to expand...
Click to collapse
Yes, only 12.01 FW or Miui12.01 with twrp gives a brick.
12.02 and higher is possible with twrp.
it is only possible to flash Miui 12.01 entirety with Miflash/fastboot
Elinx said:
Yes, only 12.01 FW or Miui12.01 with twrp gives a brick.
12.02 and higher is possible with twrp.
it is only possible to flash Miui 12.01 entirety with Miflash/fastboot
Click to expand...
Click to collapse
ow, i see
thx for the informations
Hi everyone,
I followed this forum to change My CN BS3 to global rom (using beta rom), i followed the method, unlocking, flashing twrp and flashing rom. Flashing success (via twrp), but its bootloop. Then i did factory reset. Yeah! Its entering the rom, but its stuck and restarting suddenly. So, i flashed the other cn rom but still same. Any solution? Im newbie here. Thank you.
My BS kle-a0 (joy ui 12.5 android 11) before flashing