Related
Hello people. Recently i got my first qualcomm device redmi-4x (v8.2.12.0) global (previously i used/worked-for mtk devices), and from past few days i have been reading/learning about this qualcomm device.
I have checked almost all redmi-4x forums (miui, xda, 4pda etc) and still have some questions in my mind.
Q1:
I want to backup my redmi-4x before unlocking/rooting/FlashingTWRP. I know in mtk devices, even if the device is unrooted/untouched we can easily backup firmware/complete-emmc (each and every partition) by readback methods using SP-FlashTool/Miracle-Box etc...
i read somewhere, we can do same thing, i.e readback qualcomm device's emmc in edl-mode but unfortunately, xiaomi has disabled fastboot edl mode in new devices and the only way left to open edl mode is test point method which requires disassembly. though i can but i don't want to disassemble it (warranty will be void). Another solution i saw was Deep Flash Cable, which isn't working either, personally tested... Now, having no other option, i decided to unlock it to make stock rom backup using TWRP. Actually i wanted to make backup with minimum changes to original firmware, so if anyone here knows any other solution to make backup without unlocking bootloader, (or unlocked_bootloader + no_other_changes, i.e without TWRP) please share... Thanks!
Q2:
From what i have learned so far, i think MiUI bootloader unlock tool doesn't work with non-miui firmwares, right? so the question is, if we manually relock our redmi 4x using fasboot when there is some non-miui rom installed in the device. what can be the possible solution to unlock it again? (except reflashing miui by test point method and then unlocking bootloader). Thanks!
EnerJon said:
i wanted to make backup with minimum changes to original firmware, so if anyone here knows any other solution to make backup without unlocking bootloader, (or unlocked_bootloader + no_other_changes, i.e without TWRP) please share... Thanks!
Click to expand...
Click to collapse
Hi, I do it this way:
- unlocked bootloader
- copy http://www.mediafire.com/file/pj0qh1ccj4h2a2a/p0.zip to FAT32 flash drive
- fastboot boot twrp.img (TWRP is not flashed, boots from RAM, not eMMC, so no_other_changes)
- attach the flash drive to R4X on OTG adapter
- in TWRP "install" p0.zip
- entire eMMC will be compressed and saved on the flash drive
My new R4X 32GB was compressed down to 2GB within around half an hour. Later I mounted the disk image on a PC and erased OS/data partitions: system, cache, userdata, cust, recovery, boot, and now the entire 32GB with bootloader, support and firmware is 80MB compressed.
Have you tried QPST backup in EDL mode?
k23m said:
- unlocked bootloader
- copy http://www.mediafire.com/file/pj0qh1ccj4h2a2a/p0.zip to FAT32 flash drive
- fastboot boot twrp.img (TWRP is not flashed, boots from RAM, not eMMC, so no_other_changes)
- attach the flash drive to R4X on OTG adapter
- in TWRP "install" p0.zip
- entire eMMC will be compressed and saved on the flash drive
My new R4X 32GB was compressed down to 2GB within around half an hour. Later I mounted the disk image on a PC and erased OS/data partitions: system, cache, userdata, cust, recovery, boot, and now the entire 32GB with bootloader, support and firmware is 80MB compressed.
Click to expand...
Click to collapse
Thanks for The Guide, it Will Surely be Helpful for New R4X Users :good: Just Wondering Why No One Made Such a Guide For R4X Earlier... Or Did i Missed it Somewhere?
k23m said:
Have you tried QPST backup in EDL mode?
Click to expand...
Click to collapse
No, But i Used another Tool Which i Think Uses Same Technique as QPST in EDL Mode. i Unlocked My R4X and Then Booted into EDL Mode, Used This Tool (With "prog_emmc_firehose_8937_ddr.mbn" From R4X Fastboot Firmware) To Take Complete EMMC Backup, it Also Converted The Backup into Fastboot ROM...
EnerJon said:
Thanks for The Guide, it Will Surely be Helpful for New R4X Users :good: Just Wondering Why No One Made Such a Guide For R4X Earlier... Or Did i Missed it Somewhere?
Click to expand...
Click to collapse
I made the guide and script for Nexus 7'13 but it works well on R4X too. There is no known method of QPST backup on the Nexus but Xiaomi always had more options thanks to freely available "firehose" files. Thank you for the emmcdl link, it is a very simple and convenient tool.
We could use emmcdl for unlocking. I found some pre-patched "persist" partitions here http://blog.regenerationmm.com/2017/03/emmc-dl-အသုံးျပဳျပီး-mi-account-bypass-ျပဳလုပ္/
:highfive:
k23m said:
I made the guide and script for Nexus 7'13 but it works well on R4X too. There is no known method of QPST backup on the Nexus but Xiaomi always had more options thanks to freely available "firehose" files. Thank you for the emmcdl link, it is a very simple and convenient tool.
We could use emmcdl for unlocking. I found some pre-patched "persist" partitions here http://blog.regenerationmm.com/2017/03/emmc-dl-အသုံးျပဳျပီး-mi-account-bypass-ျပဳလုပ္/
:highfive:
Click to expand...
Click to collapse
Hello. Do you have more information on this? I have a Redmi 4x that I really want to unlock the bootloader, but the official method doesn't work for me.
I found this site showing a method for the redmi 4a that uses the emmcdl tool:
Rolex Instant UBL (Unofficial Unlock Bootloader for Redmi 4A) Tested! - OmBob Opreker
Complete Tutorial how to bypass your Redmi 4A (rolex) lock bootloader, the unofficial way. tested And Work for all rolex version
ombob.my.id
Is this what you mentioned?
unluckyuser said:
Hello. Do you have more information on this? I have a Redmi 4x that I really want to unlock the bootloader, but the official method doesn't work for me.
I found this site showing a method for the redmi 4a that uses the emmcdl tool:
Rolex Instant UBL (Unofficial Unlock Bootloader for Redmi 4A) Tested! - OmBob Opreker
Complete Tutorial how to bypass your Redmi 4A (rolex) lock bootloader, the unofficial way. tested And Work for all rolex version
ombob.my.id
Is this what you mentioned?
Click to expand...
Click to collapse
Hi, I have files from the defunct link, but never tested them as my R4X is unlocked officially.
The R4A is indeed using the unlock method I speculated about.
k23m said:
Hi, I have files from the defunct link, but never tested them as my R4X is unlocked officially.
The R4A is indeed using the unlock method I speculated about.
Click to expand...
Click to collapse
I would like to have the files and experiment, thank you.
I already messed up my phone and I'm trying to flash the stock rom via edl first.
Similar to the previous threads for OnePlus 5, OnePlus 5T or OnePlus 6, here are the necessary packages to unbrick/revive a hard bricked OnePlus 7 Pro.
The following hardware revisions are supported:
GM1910: China
GM1911: India
GM1913: Europe
GM1917: Global/US Unlocked
Download: https://www.androidfilehost.com/?w=files&flid=294744
guacamole_21_H.04_190416_unlocked.zip
After using it, the phone will be restored to HydrogenOS aka Chinese firmware.
Click to expand...
Click to collapse
guacamole_21_E.08_190515_unlocked.rar
After using it, the phone will be restored to OxygenOS 9.5.4.GM21BA aka European firmware.
Click to expand...
Click to collapse
guacamole_21_O.07_190512_unlocked.zip
After using it, the phone will be restored to OxygenOS 9.5.3.GM21AA aka global firmware.
Click to expand...
Click to collapse
In every case, it is possible to upgrade to latest OxygenOS by using full signed zip from this thread via Local Upgrade.
With the device powered off, hold Volume Up & Volume Down buttons to force it to boot to Qualcomm download mode.
Use the most updated signed driver (2.1.2.2 at this moment) to avoid potential issues..
For detailed procedures, please consult the linked threads above. There is no reason to repeat the same thing again.
Make sure the path of the extracted files doesn't contain any non-English character. The tool isn't unicode aware.
Source:
HydrogenOS package: 人艱不拆 (OnePlus China forum thread), @trollavin & @Some_Random_Username for the help in mirroring
OxygenOS (EU) package: @MrVoshel
OxygenOS (global) package: @Lucifer6
Reserved for future.
Thank you for this!!
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
LLStarks said:
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
Click to expand...
Click to collapse
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
jkyoho said:
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
Click to expand...
Click to collapse
Well, that's the perfect explanation.
:highfive:
Can you turn TMobile to int'l with this ?
HtcOnekid said:
Can you turn TMobile to int'l with this ?
Click to expand...
Click to collapse
What he said
When i start MsmdownloadtoolV4.0.exe it says :
Packet image not exist!
Take out the Chinese characters in the file name and then try
joemossjr said:
Take out the Chinese characters in the file name and then try
Click to expand...
Click to collapse
Yep that's i though, but i finaly looking for EU version. Because i think with OTA upgrade to GMBA EU modem will not contain the good modem right ?
---------- Post added at 12:59 AM ---------- Previous post was at 12:27 AM ----------
failed to install on EU model : param preprocessing and stop at 5 ou 7 sec before flashing. I tryed using anothere patched tool and not working :s
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
what is your device OOS 9.5.3/4/5/6 ?
flash the co-responding stock boot.img from twrp with magisk zip together, and see if you can boot
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
thebigtross said:
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
Click to expand...
Click to collapse
Thanks for your replies! I was on OOS 9.5.5 and I tried flashing the twrp/magisk zips but that didn't work either. I also tried applying the stock boot.img to the active slot, but still got the recovery bootloop.
So as my last hope, I wiped all data in recovery mode, rebooted to fastboot and sideloaded the complete stock image from here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
I reconfigured my phone from scratch, rooted with the patched boot image like before and everythings works now. Guess I will not bother with TWRP any time soon.
Added global and EU packages.
Titokhan said:
Added global and EU packages.
Click to expand...
Click to collapse
Will global work for 1911 (India)
Mr.Crucial said:
Will global work for 1911 (India)
Click to expand...
Click to collapse
Yes, the packages are interchangable.
[/COLOR]
Titokhan said:
Yes, the packages are interchangable.
Click to expand...
Click to collapse
But I think that these packages will not work on T-mobile 1915!
When I reboot into edl mode, it recognizes the "Qualcomm HS-USB QDLoader 9008", but then 10 seconds later, the phone automatically boots the the battery display, which disables edl. The same this happens whether I use the vol up+down and plug in, or `adb reboot edl`.
Edit: "How I learned to stop worrying and risk a brick"
Selecting the right COM and hitting start in MSMtool in that 10 second window kept it in edl mode for the duration of the flash.
I have a xiaomi mi 9 but it does not pass the logo of home, it stays there, I do not have the bootloader unlocked so I wanted to know another way to flash it
If flashing is no option for you, you might have to send it in for warranty.
Try XiaoMiTool v2
Same problem here; and this tool says fastboot unbrick is not supported yet ... So even though I can flash different twrp builds, it wont get out of reboot to fastboot and no recovery works
futiless said:
Same problem here; and this tool says fastboot unbrick is not supported yet ... So even though I can flash different twrp builds, it wont get out of reboot to fastboot and no recovery works
Click to expand...
Click to collapse
Did you've tried this lr team twrp:
http://files.mi-room.ru/files/twrp/cepheus/3.3.1-0601/recovery.img
And after flashing twrp, directly with volume up and power reboot in twrp?
Search for vbmeta.img file for mi 9 and flash it
What worked is cepheus_global_images_9.6.27_20190627.0000.00_9.0_global_d1aa19c208 ; then MANUAL usage of flash_all.bat ; then I was able to boot... I think (and don't take my word for it !!) what this is, is encryption lockout. Most XiaomiFlash offical tools were practically useless for the Mi 9 and only finding that exact build (which I figured out wasn't an upgrade like the others with no flash_all.bat, actually ran and it flashed stock and booted me to pincode decryption. After than I was able to use twrp-3.3.1-35-cepheus.img, and get TWRP ... granted it wiped everything. But I booting twrp-3.3.1-35-cepheus also asked for my decrypt key. I think the other TWRP's that don't ask for this while I am encrypted actually corrupted this data... (again maybe i'm wrong) but all in all ... I had a couple hours of slowly building up stress.. cause every recovery I flashed rebooted direct to fastboot. And i'm still not sure why..
Everyone needs to make sure that you can see your full file directory tree before utilizing TWRP commands as if the TWRP install doesn't detect decryption it doesn't discriminate and just overwright and corrupts files... THIS IS WHAT IT SEEMS AT LEAST ...
ALSO big word of warning Global users have to play it safe as it seems our variants is not the one the devs are releasing for ATM. and most things you attempt to flash will cause problems. (AGAIN just my 2 cents not to be taken as fact.) Just a warning... that is it...
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
emprazol said:
Search for vbmeta.img file for mi 9 and flash it
Click to expand...
Click to collapse
OK what is that file updating over ?
link to the rom you used to fix fastboot brick?? please
I have 9008, can you help me?
I am using the Indian model. I wanted to go back to 103.5 from 11.0.1 so I flashed the 10.3.5 zip but then I got stuck in a recovery loop and all the folders were encrypted. TWRP didn't ask for the pattern. I then flashed fastboot rom with the save user data option but the phone now is stuck rebooting to stock recovery.
Please tell me what to do, I don't want to lose my data. If I can somehow decrypt I can use my twrp backup to restore but if I wipe everything then I will lose that too. What to do
I don't think you have a chance of getting the backup back. But wait for others to tell you of there is a way
Sent from my Redmi K20 Pro using Tapatalk
ishaqtkr said:
I don't think you have a chance of getting the backup back. But wait for others to tell you of there is a way
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
how do I know if the fastboot rom I downloaded is ok, it paused a couple of times during downloading, does it give an error if its not ok. Is it certain that the phone will work if I select clean all? I don't want to do it if there is any other option
gwenmillett said:
how do I know if the fastboot rom I downloaded is ok, it paused a couple of times during downloading, does it give an error if its not ok. Is it certain that the phone will work if I select clean all? I don't want to do it if there is any other option
Click to expand...
Click to collapse
Yes it should bring error if the file is corrupted. Regarding if it will work with fastboot clean all, YES it will, if that's the only solution then get the fastboot ROM and flash it with mitool, as you may know, don't select CLEAN ALL AND LOCK, only CLEAN ALL
Sent from my Redmi K20 Pro using Tapatalk
---------- Post added at 05:42 PM ---------- Previous post was at 05:42 PM ----------
From where did you get the fastboot ROM?
Sent from my Redmi K20 Pro using Tapatalk
ishaqtkr said:
Yes it should bring error if the file is corrupted. Regarding if it will work with fastboot clean all, YES it will, if that's the only solution then get the fastboot ROM and flash it with mitool, as you may know, don't select CLEAN ALL AND LOCK, only CLEAN ALL
Sent from my Redmi K20 Pro using Tapatalk
---------- Post added at 05:42 PM ---------- Previous post was at 05:42 PM ----------
From where did you get the fastboot ROM?
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
I used http://bigota.d.miui.com/V10.3.3.0....FKINXM_20190711.0000.00_9.0_in_a1c0a15dec.tgz
Do they do anything different at the service center, will they be able to save my data?
Your data is gone. Even Service Center can't help you.
Use miflash tool to flash official recovery rom.
gwenmillett said:
I am using the Indian model. I wanted to go back to 103.5 from 11.0.1 so I flashed the 10.3.5 zip but then I got stuck in a recovery loop and all the folders were encrypted. TWRP didn't ask for the pattern. I then flashed fastboot rom with the save user data option but the phone now is stuck rebooting to stock recovery.
Please tell me what to do, I don't want to lose my data. If I can somehow decrypt I can use my twrp backup to restore but if I wipe everything then I will lose that too. What to do
Click to expand...
Click to collapse
If you have the same 11.0.1 recovery rom somewhere, then try to remove the compatibility.zip from it and flash it from flash drive after mounting it in TWRP. I think that way, you'll get back to Miui where you can take your data back up.
rajumack07 said:
If you have the same 11.0.1 recovery rom somewhere, then try to remove the compatibility.zip from it and flash it from flash drive after mounting it in TWRP. I think that way, you'll get back to Miui where you can take your data back up.
Click to expand...
Click to collapse
you're a life saver! this worked. but the data is still encrypted, all the files are gibberish
gwenmillett said:
you're a life saver! this worked. but the data is still encrypted, all the files are gibberish
Click to expand...
Click to collapse
Try adding a security pin in miui and then go to twrp, it should ask for the same pin and then after you get in, you should see your files (just guessing) . But to keep your data encrypted, AFAIK, only way to flash another rom is through flash drive.
rajumack07 said:
Try adding a security pin in miui and then go to twrp, it should ask for the same pin and then after you get in, you should see your files (just guessing) . But to keep your data encrypted, AFAIK, only way to flash another rom is through flash drive.
Click to expand...
Click to collapse
Tried that, didn't work. Had to factory data reset in the end
gwenmillett said:
Tried that, didn't work. Had to factory data reset in the end
Click to expand...
Click to collapse
Share all the steps you're doing considering you are in miui and wanted to flash.
rajumack07 said:
Share all the steps you're doing considering you are in miui and wanted to flash.
Click to expand...
Click to collapse
I flashed 10.3.5 over 11. 0.1 but didn't wipe data. That made it bootloop to recovery
gwenmillett said:
I flashed 10.3.5 over 11. 0.1 but didn't wipe data. That made it bootloop to recovery
Click to expand...
Click to collapse
When you want to revert back to an earlier major version of MIUI, it is recommended to flash a fastboot ROM using the Mi Flash Tool and using the 'clean all' flash option.
Hi,
I bought a new phone and thought I would get in to custom ROMs again. Mostly to get rid of bloatware. However, after following multiple guides I'm still no where closer to achieving my goals. The phone is a MI 9.
I found there's a lot of different steps depending on guide but most of the once I've tried does the following:
* Unlock bootloader, working
* Installing twrp via fastboot, working
* Deleting data in twrp, working
* Transfering a rom.zip file (depending on rom), working via usb cable
* Some guides recommends to install disable force Encryption via another zip file transferred from the computer, however, that seems to not be necessary, tried i few times
* Installing rom via twrp, seems to work
* In some guides you then need to remove cache, working
* Rebooting from twrp, working
After these steps I find myself in one of three different cases,
1. Phone is stuck in fastboot, have to reflash it with MIflash and global MIUI rom to get phone to work again
2. Phone in boot loop, logo shows up, phone waits for awhile, phone reboots, logo shows up
3. Phone boots up, logo is shown, phone reboots into twrp
I've also tried both XiaoMiTool and XiaoMiTool V2,
XiaoMiTool seems to write the global ROM to the phone whatever I choose (Have tried Xiaomi.eu and LineageOS 17)
XiaoMiTool V2, fails in second to last step, it wants to remove some cache before the installation in twrp is done.
Things I've not tried:
* Moving file to twrp with adb instead, should not make a difference
* Installing magisk
Now, I'm a bit afraid my phone will get hard bricked, have reinstalled the OS 20 times the last day to test different approaches and steps. Nothing seem to work. Does anyone have a proven method working in 2020?
Another way to go might be to just get rid of the commercials, run a different launcher to get app list and get rid of the bloatware. This is not really what I want but I can live with it.
As you can hear I'm about to just throw in the towel and give up. But I've heard a lot good about the xda forums so I thought it might be worth a try even though I do understand if no one has time or energy to help out a newbie.
Help please!
Edit: I do realize I've accidentally put this under Guides and not Q&A. I find no way of moving it nor deleting the thread so I guess some moderator will have to come help. Sorry for this.
Do you use latest TWRP for Mi9? TWRP from Mauronofrio works fine for me.
When you say "Deleting data in twrp", does this mean you did Format Data (confirm by typing "yes")? Or just wipe?
Poslano z mojega MI 9 z uporabo Tapatalk
mxxt01 is right. You have to format the data partition or else you will run into a bootloop.
I followed the guide here but I did not flash magisk since I don't need root.
Basically what I did was;
1. Unlock bootloader
2. Reboot to load the OS but skip the initial setup
3. Reboot to fastboot/bootloader
4. Flash TWRP (use the latest beta from Mauronofrio)
5. Immediatly press Vol Up + Power button to boot TWRP
6. Sideload the firmware to /tmp/
7. Format the data partition and type yes to continue
8. Factory reset
9. Flash firmware from within TWRP
10. Factory reset again (you can skip this if you don't want to)
11. Reboot
And that is how I did it.
mxxt01 said:
Do you use latest TWRP for Mi9? TWRP from Mauronofrio works fine for me.
When you say "Deleting data in twrp", does this mean you did Format Data (confirm by typing "yes")? Or just wipe?
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
I have tried both Formatting data, this generally makes all folders have gibberish names and by going to advanced wipe, choosing data, some guides also wants you to delete Dalvik, Cache and System. I have tried both in the same go and one or the other. Does not seem to make a difference. But from the response below I get that it's formatting the data and typing yes that is the way to go(?)
TWRP version 3.3.1-0
sangbuana said:
mxxt01 is right. You have to format the data partition or else you will run into a bootloop.
I followed the guide here but I did not flash magisk since I don't need root.
Basically what I did was;
1. Unlock bootloader
2. Reboot to load the OS but skip the initial setup
3. Reboot to fastboot/bootloader
4. Flash TWRP (use the latest beta from Mauronofrio)
5. Immediatly press Vol Up + Power button to boot TWRP
6. Sideload the firmware to /tmp/
7. Format the data partition and type yes to continue
8. Factory reset
9. Flash firmware from within TWRP
10. Factory reset again (you can skip this if you don't want to)
11. Reboot
And that is how I did it.
Click to expand...
Click to collapse
Could you describe step 6 in more detail please?
This is what I get if I try sideloading my phone:
adb push xiaomi.eu_multi_MI9_V11.0.5.0.QFACNXM_v11-10.zip /tmp/
adb server is out of date. killing...
* daemon started successfully *
I guess it's important to not get the firmware in the SD-card folder since that will be wiped if I format the data, this might be where I fail.
Step 6 is to type adb push rom.zip /tmp/
I renamed the zip file to rom.zip so that I don't typo when typing.
Sent from my MI 9 using Tapatalk
In any case you should flash a current (11.0.6.0 or younger) fastboot ROM (.tgz extention). Recovery ROMs (.zip extention) don't reset the phone as deep as fastboot ROMs do.
After that you'd best flash vbmeta.img before TWRP, see #1 for more details.
Cheers
Toscha
From personal experience of using xiaomi.eu's ROM, I never did install vbmeta.img or dmverity, since that particular rom is based on the official beta Chinese MIUI ROMs, and the latest TWRP from Mauronofrio supports decryption. Not sure about other ROMs though.
Just to be safe, just download the stock fastboot ROM as a backup just in case anything goes wrong. Always remember to NOT lock your bootloader when flashing back to stock, in case your persist partition gets corrupted, you can flash it to recover.
ZevSwe said:
I have tried both Formatting data, this generally makes all folders have gibberish names and by going to advanced wipe, choosing data, some guides also wants you to delete Dalvik, Cache and System. I have tried both in the same go and one or the other. Does not seem to make a difference. But from the response below I get that it's formatting the data and typing yes that is the way to go(?)
TWRP version 3.3.1-0
Could you describe step 6 in more detail please?
This is what I get if I try sideloading my phone:
adb push xiaomi.eu_multi_MI9_V11.0.5.0.QFACNXM_v11-10.zip /tmp/
adb server is out of date. killing...
* daemon started successfully *
I guess it's important to not get the firmware in the SD-card folder since that will be wiped if I format the data, this might be where I fail.
Click to expand...
Click to collapse
Like written by toscha42 you should flash the latest fastboot stock rom (tgz) for your phone first, as after all the attempts you have made your phone is probably kind of ****ed up... Do not lock bootloader.
What I do and it works for me, starting from stock ROM.
1. Unlock bootloader (you already done that)
2. Flash in fastboot latest TWRP for your device (I use Mauronofrio)
3. After flashing disconnect the phone and push VOLUME UP + POWER to enter from fastboot directly to TWRP recovery
4. Format data with yes
5. Reboot to recovery
6. Flash xiaomi.eu custom rom for your device with USB OTG (usb otg is the easiest way I guess as you don't need to move the rom to internal storage)
7. Reboot to recovery
8. Wipe cache and dalvik cache
8. Reboot to system
And that's all.
Poslano z mojega MI 9 z uporabo Tapatalk
toscha42 said:
In any case you should flash a current (11.0.6.0 or younger) fastboot ROM (.tgz extention). Recovery ROMs (.zip extention) don't reset the phone as deep as fastboot ROMs do.
After that you'd best flash vbmeta.img before TWRP, see #1 for more details.
Cheers
Toscha
Click to expand...
Click to collapse
Can't seem to find any fastboot ROMS, neither of xiaomi.eu or LineageOs 17. Where can I find this? https://xiaomi.eu/community/threads/20-1-16.54300/
If I understood correctly vbmeta.img unlockes secure boot. Not sure why that is needed or what problems it might create. Did some googling but found nothing. What is this used for? If it's important, why is it not in any guides I found?
ZevSwe said:
Can't seem to find any fastboot ROMS, neither of xiaomi.eu or LineageOs 17. Where can I find this? https://xiaomi.eu/community/threads/20-1-16.54300/
If I understood correctly vbmeta.img unlockes secure boot. Not sure why that is needed or what problems it might create. Did some googling but found nothing. What is this used for? If it's important, why is it not in any guides I found?
Click to expand...
Click to collapse
Fastboot STOCK Xiaomi ROM.
To be flashed with MiFlash. Do not lock bootloader.
http://c.mi.com/oc/miuidownload/detail?device=1700361
Poslano z mojega MI 9 z uporabo Tapatalk
Fastoot ROMs are only available for official MIUI ROMs and has tgz as their filename extensions. They are flashable only using Mi Flash tools or equivalent. Custom ROMs has zip and they are flashable using recovery.
Correct me if I'm wrong, vbmeta.img is for verified boot. I was running on official MIUI ROM and I wanted to have TWRP recovery, but stock recovery would come back after every reboot. So I flashed a modified version of vbmeta.img available on the web, to disable verified boot, and TWRP would persist in the recovery partition. Have a read on Verified Boot here.
mxxt01 said:
Fastboot STOCK Xiaomi ROM.
To be flashed with MiFlash. Do not lock bootloader.
http://c.mi.com/oc/miuidownload/detail?device=1700361
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
Hmm okay, but the phone is already working with the stock ROM, my whole idea is to switch to something else. What do you mean with do not lock bootloader?
sangbuana said:
Fastoot ROMs are only available for official MIUI ROMs and has tgz as their filename extensions. They are flashable only using Mi Flash tools or equivalent. Custom ROMs has zip and they are flashable using recovery.
Correct me if I'm wrong, vbmeta.img is for verified boot. I was running on official MIUI ROM and I wanted to have TWRP recovery, but stock recovery would come back after every reboot. So I flashed a modified version of vbmeta.img available on the web, to disable verified boot, and TWRP would persist in the recovery partition. Have a read on Verified Boot here.
Click to expand...
Click to collapse
Right, well I wish to switch to another ROM so installing MIUI Global ROm will not help.
I'm able to install TWRP without touching verfiedboot at all and get it to work even after reboot so that is not a problem. If that is what verifiedboot does I believe I can skip that?
ZevSwe said:
Hmm okay, but the phone is already working with the stock ROM, my whole idea is to switch to something else. What do you mean with do not lock bootloader?
Click to expand...
Click to collapse
than try once again by following my steps in post #8
You can skip flashing vbmeta and just follow mxxt01's steps.
Sent from my MI 9 using Tapatalk
sangbuana said:
You can skip flashing vbmeta and just follow mxxt01's steps.
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
That seems to have made the trick! Thanks so much!
I've been following this thread because I was having the same problems as ZevSwe, multiple attempts at installing roms with no success. I've been using phones/tablets with custom roms for years so I have some experience but not with this device.
I'll be trying the steps in post #8 later today but I have a question about twrp that's buggin me. I have been taking full twrp backups to a usb stick before installing and just reinstalling when the custom rom didn't work but the last few times the reinstall failed at about 98% complete and I've had to reinstall stock from scratch.
Any idea why a twrp backup would fail on reinstall? Is there something I could have inadvertantly done to cause this issue? Playing with roms is fun and easy when you've got a twrp backup to fall back on but a pain in the $#^ when it doesn't restore. Any thoughts would be appreciated before I give it another go.
thecdn said:
I've been following this thread because I was having the same problems as ZevSwe, multiple attempts at installing roms with no success. I've been using phones/tablets with custom roms for years so I have some experience but not with this device.
I'll be trying the steps in post #8 later today but I have a question about twrp that's buggin me. I have been taking full twrp backups to a usb stick before installing and just reinstalling when the custom rom didn't work but the last few times the reinstall failed at about 98% complete and I've had to reinstall stock from scratch.
Any idea why a twrp backup would fail on reinstall? Is there something I could have inadvertantly done to cause this issue? Playing with roms is fun and easy when you've got a twrp backup to fall back on but a pain in the $#^ when it doesn't restore. Any thoughts would be appreciated before I give it another go.
Click to expand...
Click to collapse
Since you noted that you have been doing a backup to a USB stick, it could be the USB stick is failing.
Honestly, all the installation guides for custom Roms i came across on XDA in the recent years are complete garbage. It fills like copy pasted from a guide that has been copypasted from a copypasted thread which has been copypasted and never worked.
For me, this guide works just fine. I just had to find the files for my Mi 9 instead of the k20 Pro. I would upload them for you but my upload speed is garbage.
https://www.youtube.com/watch?v=w_u_w6SrTDY&t=249s
I have flashed a lot of ROMs custom and official, fastboot and recovery. Never had any problems, the steps is here in thread.
Just remember 2 thing:
1. If you have ROM which using encryption, you must format data, because wipe will not remove encryption and you will see gibberish names
2. If you wipe system (which is mean less, because every ROM flash will do that, when you flash it, but many people insist in wiping it) then you must flash a ROM without reboot or you will stuck in fastboot and only option to repair is to flash official fastboot ROM (Non official fastboot ROMs, don't exist).