Hello, today I unlocked my Redmi 7, installed custom TWRP and rooted it. Everything worked fine.
Then I wanted to install a custom ROM. The issue is that without noticing i went to the Redmi NOTE 7 forum. So I followed the instructions for the Lineage OS ROM.
I went till the fastboot --disable-verity flash vbmeta vbmeta.img steps. Then i noticed my phone couldn't boot anymore.
I tried flashing back the original TWRP, nothing is working so far.
I also tried using the MiFlash but it gives me an error flash_all_expect_storage.bat isn't found.
If anyone here has any idea, I would be really thankful.
Ok I managed to fix it by doing the same command --disable-verity flash vbmeta bvmeta.img but for the bvmeta inside the Firmware if bricked folder
Related
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...
After some time of sitting on ColorOS 6.1 I decided it was time to move to a Custom Rom.
I watched some tutorials and managed to unlock my bootloader and flash twrp recovery version 3.4.
Following the steps from the Evolution X guide I wiped cache/system/vendor/data/internal storage. Then copied over the rom via the "mount" option, after successfully copying the rom I went to install and flashed the rom with no issues. However, once I go to reboot I boot strait into fastboot mode (which keeps restarting until I select 'restart bootloader').
I have tried other Roms such as Covus and the pixel experience rom that was posted here and have the same issue.
Finally I tried 'fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img' with vbmeta provided in root tutorial...still nothing
As it stands I can still boot into twrp without issue so I wouldn't call the device bricked just a victim of (likely) user error.
Oh and I also tried different versions of twrp...3.3-19 and that also did not work.
Is it possible that trying to flash to an android 10 rom from android 9 is the issue?
Please let me know if you guys or girls have any ideas because I can't think of anything else
Finally thank you in advance all those who respond!
Edit: So uhhh yeah y'all make sure you update to android 10 before trying to flash an android 10 rom lol
update: I followed this guide if anyone has issues and booted successfully after a couple attempts into RealmeUI
https://forum.xda-developers.com/realme-x2/help/how-to-flash-q-firmware-based-roms-t4115987
Hello there,
I have bought a Redmi Note 8 Pro in Europe. My goal is to get a custom rom on it up and running.
The bootloader is successfully unlocked, and I tried to flash TWRP and Orange Fox recovery. To do so I followed the instructions on the TWRP home page to the letter, namely flashing vbmeta.img (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img) first and then the recovery image (
Sadly the TWRP and Orange Fox recovery never starts; the system just seems to be stuck in a boot loop for recovery, until I power it off and start it in a way that the stock ROM provided on it re-installs itself.
I have tried so far all suggestions I was able to find in this forum, but sadly no result.
What might I still do in order to get a recovery finally up and running on this device?
Thanks in advance!
vruhag said:
Hello there,
I have bought a Redmi Note 8 Pro in Europe. My goal is to get a custom rom on it up and running.
The bootloader is successfully unlocked, and I tried to flash TWRP and Orange Fox recovery. To do so I followed the instructions on the TWRP home page to the letter, namely flashing vbmeta.img (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img) first and then the recovery image (
Sadly the TWRP and Orange Fox recovery never starts; the system just seems to be stuck in a boot loop for recovery, until I power it off and start it in a way that the stock ROM provided on it re-installs itself.
I have tried so far all suggestions I was able to find in this forum, but sadly no result.
What might I still do in order to get a recovery finally up and running on this device?
Thanks in advance!
Click to expand...
Click to collapse
Are your flash sequence vbmeta>TWRP>reboot?
Try to flash vbmeta once more.
Also, for recovery, choose one of it.
All, I would like to get some help, on the above subject,
Background, I unlock my redmi not 8 pro and was trying to flash lineage recovery through fastboot command, I wasn't getting through, and I must have flash a wrong file, now my phone would not boot it goes to the redmi logo and back again, it does not boot to recovery but it boots to fastboot.
Any and all help is appreciated
Thanks in advance
zjxpot said:
All, I would like to get some help, on the above subject,
Background, I unlock my redmi not 8 pro and was trying to flash lineage recovery through fastboot command, I wasn't getting through, and I must have flash a wrong file, now my phone would not boot it goes to the redmi logo and back again, it does not boot to recovery but it boots to fastboot.
Any and all help is appreciated
Thanks in advance
Click to expand...
Click to collapse
Can you try to flash the stock firmware?
I downloaded and flash a global stock firmware, but I believe I messed something up in the boot section by issuing a wrong command from the cmd prompt, because the phone was booting fine even though the recovery files I flash didn't work until I issued a cmd with "flash boot recovery" in it.
Hmmm...what happens if you hard reset?
Hey thanks I got through by wiping using Al All-in-one app and flashing stock firmware,
Thanks for all your input
I'm looking for some help on a topic regarding my redmi 6 pro.
My redmi 6 pro one day out of the blue just froze, then never booted. Recovery also bricked itself and didn't boot past the mi splashscreen. I wiped userdata using fastboot -w and then tried to flash a recovery again, but all my partitions failed to mount.
I'm not quite sure how, but after that it's been stuck on fastboot with any reboot attempts just being stuck on fastboot. I have tried using stock firmware, but the file called sec.dat does not flash at all. The rest flash fine. I tried mi flash tool, but it had the same error. I tried EDL but I don't have an authorised account nor do I know how to flash the firehose patch. I then tried to boot into twrp using fastboot boot, but it got stuck on splashscreen. OrangeFox however worked fine.
Right now I feel like I should flash my default stock partitions but I don't know how at all.
FYI, I've already unlocked my bootloader and everything, I was using HavocOS, last Android 11 version.