Hi,
I have a Xiaomi Redmi 7 device. Originally, it used to have a Chinese Rom. A week after, I changed it a Global Rom. I got curious about Magisk, so I attempted to install it without having TWRP. I followed the tutorial that I've watched on how to do it. I was under the impression that I'm on the right track. After the installation, I reboot the device and that started the problem. I was stuck on Redmi Logo. I was told to flash a Rom using TWRP. So I installed TWRP and started flashing the Rom my device has. 1st attempt FAILED. 2nd / 3rd / 4th and until now, it's still the same, FAILED. No OS Installed... Error 7... E1001... Cannot flash any Rom's after. Tried the one where you need to edit the "Update-Script" using notepad++, still unsuccessful. Tried using other TWRP versions and flash other Rom's, no luck at all. Is there any other way to fix the issue? I badly need help. Thanks!
Related
So after more or less randomly trying different things, and fearing that I might only have made matters worse, I hope someone can help:
I have got a Huawei Honor 6 H60-L04 (bootloader unlocked and rooted) and was, until two days ago, running KitKat with the B114 build and cwm recovery. Since Marshmallow has officially benn available for the Honor 6 for a while now, I decided to finally update.
I flashed stock recovery and updated to Marshmallow build B820 via update.app on sdcard. Booting worked fine, however I was unrooted (ofc) so I decided to flash SuperSU (2.76 [latest stable]).
So I flashed twrp 3.0.2.0. and so far all good. Still no problems booting. Then I flashed SuperSU (according to twrp successfully) and rebooted, just to find myself stuck on bootscreen. That is not the first one you get in bootloop but the animated honor logo. Well ****.
Since then I tried many things, wiped multiple times (data is unimportant, but unfortunately I don't have a working twrp backup, please don't lecture me on this, i know -.-), flashed almost any stock ROM I could get my hands on. In twrp I get this Error:
Could not find 'META-INF/com/google/android/update-binary' in the zip file". >"Error installing zip file". "Failed"Somewhere on the way I got
error! Func NO : 9 (FUNC_BOOT_KERNEL) Error NO : 2while booting, that's gone though.
I'm at the point now where I can install B820 via update.app on sdcard, see the installation progress succeed to 100%, reboot, and again, find myself stuck on animated honor logo.
I honestly have no idea what I can do, I hope someone here does. I'll happily provide any further information you might need.
Try and wipe everything, then reflash TWRP. Good luck ?
Sent from my Samsung Galaxy S7 Red using XDA-Developers mobile app
I did that, I lost count how many times. I wiped everything, clean twrp flash, still get the "meta-inf" error message. Maybe someone can provide me with a clean twrp backup for B820? that might actually work.
Ok, after making a fool of myself, I finally found the culprit. Turns out I have to wait a couple of minutes after a new installation for my phone to boot. And all the time I thought it was soft bricked -.-
However, I does get soft bricked whenever I try to flash SuperSU. Root = bricked. Unroot = unbricked. Anyone got an idea how to get SuperSU to work? I really don't want to go back to unrooted...
I used supersu 2.62 with MM.
After install i update supersu with Google play.
Supersu update itself the binary to 2.76.
It works with B820 ans now with B860.
hagehagen said:
Ok, after making a fool of myself, I finally found the culprit. Turns out I have to wait a couple of minutes after a new installation for my phone to boot. And all the time I thought it was soft bricked -.-
However, I does get soft bricked whenever I try to flash SuperSU. Root = bricked. Unroot = unbricked. Anyone got an idea how to get SuperSU to work? I really don't want to go back to unrooted...
Click to expand...
Click to collapse
Haha, next time give the phone a couple minutes.
Sent from my Samsung Galaxy S7 Red using XDA-Developers mobile app
I have been using the Armani rom for my redmi 1s for quite some time.Recently, I started facing a problem of process lagging which isn't getting fixed on installing all the updates so i decided to install MIUI again.
I went to downloads and downloaded the global MIUI rom 'V7.5.1.0.KHCMIDE'(MIUI7) and placed it on my USB Drive, connected it and flashed it using TWRP recovery. It shows me an error "error executing updater binary in zip" . I had faced the same problem when flashing an older version of a MIUI rom. I also tried checking the verify zip before flashing in twrp menu but still no success. I want to get back to MIUI. Kindly help me in overcoming this problem.
Thanks
sar1097 said:
I have been using the Armani rom for my redmi 1s for quite some time.Recently, I started facing a problem of process lagging which isn't getting fixed on installing all the updates so i decided to install MIUI again.
I went to downloads and downloaded the global MIUI rom 'V7.5.1.0.KHCMIDE'(MIUI7) and placed it on my USB Drive, connected it and flashed it using TWRP recovery. It shows me an error "error executing updater binary in zip" . I had faced the same problem when flashing an older version of a MIUI rom. I also tried checking the verify zip before flashing in twrp menu but still no success. I want to get back to MIUI. Kindly help me in overcoming this problem.
Thanks
Click to expand...
Click to collapse
I don't think You can't flash stock ROM via twrp .twrp allow installing of custom things(custom ROM,kernel etc...) . if you want to get back to miui try something along the line of fastboot .
Hey everyone,
i usually don't post questions but i've been on pretty much every forum the web has to offer and am still stuck so i'll try my luck here.
i'm currently running lineage 7.1 on my mi4c, i've used another phone for a while but now that my mi4c has a new battery i wanted to start using it again, is also decided this would be the time to update it to android oreo or pie, this however seems to be impossible.
i can only use twrp up to 3.1.1.1, all higher (and unofficial versions) will not boot via fastboot 'dtb not found' or when flashed via older twrp will freeze on boot screen.
whenever i try to install a new rom it tells me 'error code 7', when i remove the 'assert' lines in the update it gives me 'error code 6'
my device is unlocked, i have checked this in fastboot.
do i have to install miui again before installing another rom? do i have to go back to the standard recovery? i'm currently running out of ideas and hope you guys might be able to help me. maybe i'm overlooking something simple.
kind regards,
Monstreys
Hi! I don't know if this is a coincidence or not, but I was about to start a similar thread.
I try to do exactly what you are doing. I want to install LineageOS 16, unofficial ROM.
For this you need a newer TWRP, like 3.2.3.0, but it doesn't work 'dtb not found' like you said. I found out that this doesn't work because you need to have nougat bootloader. Most probably you have lollipop bootloader like I have, and thats why newer versions of TWRP are not working. I think the only way to update your bootloader to a nougat one is to flash the latest MIUI ROM. But, unfortunately, when you do that the bootloader gets locked, and I can't unlock it via MiUnlock due to Error:20091 when I try to link the phone to the Mi account. In MiUnlock it gives me the "this account cannot unlock the phone" or something like that.
Now I removed the "assert" lines from my rom and flashed it without the error 7 or 6. Some error still apears, but it also apears when I flash LineageOS 14.1, and that version is working even with those 2 errors I can't remember during flash.
After I flashed LineageOS, I flashed gapps and then superSU, and now my mi4c is stuck on mi logo for about 20 minutes, and I think it will remain that way.
So, there are 2 things we need to solve. We need to find a way to install latest MIUI without relocking the bootloader because I can't unlock it via MiUnlock, or to find out why after I flashed LineageOS 16 it gets stuck on MI logo.
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
i
i was unable to install the patch file, this nonetheless fixed my problem, thanks!!
if above not working, another method to do it based on my method.
https://forum.xda-developers.com/showpost.php?p=81573941&postcount=199
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
My MI4C has been successfully flushed into lineage-17.1-20200220-UNOFFICIAL-libra.zip. It has been updated on TWRP 3.1.1 and keeps reporting error 7, and then abandoned TWRP3.1.1 and flashed into OrangeFox-R10.0-1-Stable-libra.zip After brushing libra-aqua_firmware_7.2.9.zip on this REC, you can flash lineage-17.1. I do n’t think it will be impossible to refresh because of partition problems. If you only need to upgrade lineage-17.1, you can refer to this method.:good::good:（Translation is not easy to use）
celrau said:
There is a 3.2.x around. If you don't want to bother go in the zip, /META-INF/com/google/android/ and delete the first lines (the ones starting with "assert") from updater-script, save and flash again.
Click to expand...
Click to collapse
rianawirawan said:
Right now, i'm using 3.1.1 -1 btw
It's latest twrp ver from official
Click to expand...
Click to collapse
TWRP-20190418-3.3.0.0-libra.img for the Xiaomi Mi 4c, by GuaiYiHu :
https://androidfilehost.com/?fid=1395089523397945946
Latest firmware for the Xiaomi Mi 4c libra :
https://github.com/XiaomiFirmwareUp...iui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0.zip
I wanted to know if someone successfully rooted Global MIUI with android 10. I tried flashing via twrp and patching boot.img (Magisk 20.3), but both failed, giving me bootloop.
Edit: https://github.com/topjohnwu/Magisk/issues/2492#issuecomment-593149828 This solved the issue.
Was this on miui 11.0.3.0. (QEEMIXM) I've been trying the normal way but the bootloop is happening.
Hello,
I am having a very big problem:
Yesterday evening I unlocked the bootloader of my Poco F2 Pro and I wanted to install a custom rom (I was thinking of installing One Os).
I followed the step by step but the installation did not work and I only had access to recovery.
I managed to reset the original rom via Mi Flash but having retried the same Mi flash procedure now blocks.
Since then I find myself without a phone, the recovery seems to work but it stops there, impossible by flashing it to launch a ROM, I have the impression that the system partion does not work
To be precise, this is an 8-256GB
Thank you in advance to the person who can help me relaunch it.
Actarus0013 said:
Hello,
I am having a very big problem:
Yesterday evening I unlocked the bootloader of my Poco F2 Pro and I wanted to install a custom rom (I was thinking of installing One Os).
I followed the step by step but the installation did not work and I only had access to recovery.
I managed to reset the original rom via Mi Flash but having retried the same Mi flash procedure now blocks.
Since then I find myself without a phone, the recovery seems to work but it stops there, impossible by flashing it to launch a ROM, I have the impression that the system partion does not work
To be precise, this is an 8-256GB
Thank you in advance to the person who can help me relaunch it.
Click to expand...
Click to collapse
so u cant flash with miflash? what errors gives miflash on flashing?
Good evening,
Thanks for trying to help me.
I managed to finally flash my F2 Pro via MiFlash.
So what is the precise method to flash a rom, I would like to install MiuiMix but I do not have a view on the system partition in TWRP and I am afraid of bricking my phone.
Small precision, I do not know if that changes anything but it is an F2 Pro 8-256Go
thank you in advance