Hello sir, i tried to install xiaomi.eu rom or other rom available from XDA but my twrp always shown error 7, sometimes error 11.
IDK Why, I tried every possible solution available but none of them working. I tried to flash global rom miui 10 or china rom miui 11, it's working, but I'm not satisfied with that rom.
any idea how to fix it?
findwalter said:
Hello sir, i tried to install xiaomi.eu rom or other rom available from XDA but my twrp always shown error 7, sometimes error 11.
IDK Why, I tried every possible solution available but none of them working. I tried to flash global rom miui 10 or china rom miui 11, it's working, but I'm not satisfied with that rom.
any idea how to fix it?
Click to expand...
Click to collapse
I faced similar problem. I ve flashed Los 16 last year, so I wanted to refresh device and tried to flash same latest Los 16, but With twrp 3.3... I got error 7, so I flashed latest miui 11 Dev and it worked. But when I be tried to flash Los 17 - same error 7. Solution- twrp 3.4.... But I got error 7 with twrp 3.4 when tried to flash los 16... So it is mess )
So it is a bit tricky, because there are no requirements in Rom's threads...
bot1987 said:
I faced similar problem. I ve flashed Los 16 last year, so I wanted to refresh device and tried to flash same latest Los 16, but With twrp 3.3... I got error 7, so I flashed latest miui 11 Dev and it worked. But when I be tried to flash Los 17 - same error 7. Solution- twrp 3.4.... But I got error 7 with twrp 3.4 when tried to flash los 16... So it is mess )
So it is a bit tricky, because there are no requirements in Rom's threads...
Click to expand...
Click to collapse
do you solved this problem cause same with me
Related
I am facing a “Status 7″ error in CWM 6.0.2.8 and 6.0.4.5 while trying to flash CM 11 to my GT-I8160:
Finding update package…
Opening update package…
Installing update…
Error in /sdcard1/Android/Cyanogen Mod 11/Rom/cm-11-20131210-UNOFFICIAL-codina.zip (Status 7)
Installation aborted
I tried flash with CM 10.2, stock I8160XXMG2 Jelly Bean, MIUI v5 Beta 3. I always faced with this error. I never faced an error like this. Other roms (CM 10, 10.1, 10.2, Kyrillos Rom v9, v8, MIUI v5 Beta 3) install correctly. How can I fix this problem?
Flash older version and then new...
Or wait next build with incldued fix for olde recoveries...
Yes me too, today I tried to flash this ROM to my device but it appears the same error, can it be the recovery? I am just using CM10.2 with 4.3.0
I hope this can be fixed.
Regards
Ok. I will wait for the next build. Unless it work, I will flash older version and then new.
Lirimaer said:
Ok. I will wait for the next build. Unless it work, I will flash older version and then new.
Click to expand...
Click to collapse
try
I'm planning on updating my Mi 5s to Lineage OS16 but I would first like to flash the latest firmware for the device. To do this I first need to flash the developer firmware and ROM from here. This however is not possible. To flash the ROM requires a previous version of MIUI to be installed since no "fastboot version" exists yet. In the past, a "fastboot version" of the ROM could be flashed using their XiaoMiFlash tool but since that version does not yet exist for MIUI 10, I'm forced to use the other method of flashing from the device itself. This would usually be fine, however, since I am on LineageOS, I am unable to flash MIUI from the device. Does anyone know how to flash MIUI 10 when their Mi 5s is using LineageOS? Any help is appreciated.
Rom flash procedure: https://forum.xda-developers.com/mi-5s/how-to/fastest-android-9-0pie-rom-xiaomi-mi-5s-t3929174
MIUI 10 download link: https://sourceforge.net/projects/xi...s/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/9.5.9/
candemir2005 said:
Rom flash procedure: https://forum.xda-developers.com/mi-5s/how-to/fastest-android-9-0pie-rom-xiaomi-mi-5s-t3929174
MIUI 10 download link: https://sourceforge.net/projects/xi...s/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/9.5.9/
Click to expand...
Click to collapse
This is exactly what I was looking for. Thank you very much!
Hey!
I too am having some troubles, but the linked XDA thread does not give an answer.
I want to install the MIUI 10 Global Stable form xiaomi eu (based on Oreo) (https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-10-3-10-4-stable-release.47170/), but after installation it does not boot.
I have tried the following:
I am coming from official LOS 16, and had my storage encrypted. Before installation of LOS16 I updated the firmware using xiaomifirmwareupdater.com to version 10.2.3.
Now, I wipe cache, dalvik, system and data and then install the zip from xiaomi.eu (https://androidfilehost.com/?fid=11410963190603906104), which does not throw an explicit error, but returns a [0] in TWRP. Then, when I reboot, TWRP gives the message "No OS installed"'. I continued anyways, and let the phone sit for 30 minutes, but it is stuck on a boot screen (different boot screen than I had with LOS though). I checked the MD5 hash, which is correct. Also, I performed exactly the same procedure another time.
Does anyone know how to solve this problem?
I though it might had to do something with the following:
- going from AOSP to MIUI?
- Having encrypted through LOS16?
- Having updated the firmware to 10.2.3, and the installing a 10.2.1 ROM (although the xiaomi eu roms have their required firmware baked into the zip right?)
Any help would be much appreciated!
my a2 lite got the awful 10.0 update, and I tried to install a custom rom.
the only one that worked was the Avenger MIUI rom.
I'm using dees-troy's twrp 3.3.1
tried to reflash the stock img, it got me into booting only to fastboot mode.
I'm tired of the MIUI, can anyone explain to me step-by-step how to install any aosp-like rom?
back then, I had error number 7, and on my last try, after trying to flash back and such, it couldn't mount the storage correctly.
right now I have an error:
E:recv error on uevent
UduBobo said:
my a2 lite got the awful 10.0 update, and I tried to install a custom rom.
the only one that worked was the Avenger MIUI rom.
I'm using dees-troy's twrp 3.3.1
tried to reflash the stock img, it got me into booting only to fastboot mode.
I'm tired of the MIUI, can anyone explain to me step-by-step how to install any aosp-like rom?
back then, I had error number 7, and on my last try, after trying to flash back and such, it couldn't mount the storage correctly.
right now I have an error:
E:recv error on uevent
Click to expand...
Click to collapse
You need:
twrp-installer-daisy-3.2.3-0-offain (or higher)
Also when you install AOSP based rom you'll have to change A/B slots before rebooting. Most of the roms have step by step guide on the first page / post.
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
So, i tried to install a custom ROM on my Redmi Note 8 pro (begonia model).
I used a LR-TWRP somewhere from this forum (I can link it later, currently on mobile),
It boots, but if I try to install MIUI 12.5, it just bootloops (not system, recovery), rooting bricks the phone (restored with SP FLASH).
Installing preloaded, lk and lk2 (from megathread) kinda bricks the phone, I can boot to MIUI, but can't to fastboot and recovery. (I also restored it)
Installing Pixel Experience 11 (my target ROM is Pixel Experience 12, but I would need to update MIUI, which breaks TWRP) also bricks the phone.
I am currently on MIUI 10, Android 9.
What can I do?
Sorry for my English.
Your TWRP version is incompatible. Flash the Android 11/12 version of TWRP after you flash the ROM.
MIUI 12.5 A11:https://sourceforge.net/projects/be...rp-3.5.2_11-0-UNOFFICIAL-begonia.img/download
A12:https://sourceforge.net/projects/be...ic/Dynamic-TWRP-Begonia-23-12-21.img/download
Canny1913 said:
Your TWRP version is incompatible. Flash the Android 11/12 version of TWRP after you flash the ROM.
MIUI 12.5 A11:https://sourceforge.net/projects/be...rp-3.5.2_11-0-UNOFFICIAL-begonia.img/download
A12:https://sourceforge.net/projects/be...ic/Dynamic-TWRP-Begonia-23-12-21.img/download
Click to expand...
Click to collapse
Okay, so i installed MIUI 12.5 and Begonia Recovery Project.
Pixel Experience 11 Plus works fine, but i can't install the 12 one.
It shows ERROR 1,
and assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))
From other threads, I formatted data and install latest MIUI (12.5.7), but it still errors.
Sorry for not replying, it was a night time in my country
Begonia Recovery Project is based on Android 10 version of TWRP.
Flash the latest MIUI using fastboot then flash this version of TWRP:https://sourceforge.net/projects/be...ic/Dynamic-TWRP-Begonia-23-12-21.img/download
Then sideload or direct install the zip and format data.
The guide says don't worry about red line errors.