Related
Disclaimer
I am not responsible for bricked devices or anything like that. YOU are choosing to make these modifications, and if you point your finger at me for messing up your device, I will laugh at you.
Here are the current fastboot links for the Xiaomi Mi A2 (jasmine):
Fastboot Images:
Android 10.0 [V11.0.15.0.QDIMIXM]:
https://bigota.d.miui.com/V11.0.15.....QDIMIXM_20201019.0000.00_10.0_3ea0b7a69b.tgz
Android 10.0 [V11.0.12.0.QDIMIXM]:
https://bigota.d.miui.com/V11.0.12.....QDIMIXM_20200724.0000.00_10.0_79e67f3105.tgz
Android 10.0 [V11.0.11.0.QDIMIXM]:
https://bigota.d.miui.com/V11.0.11.....QDIMIXM_20200610.0000.00_10.0_512a1978b3.tgz
Android 10.0 [V11.0.10.0.QDIMIXM]:
https://bigota.d.miui.com/V11.0.10.....QDIMIXM_20200521.0000.00_10.0_fc90551230.tgz
Android 9.0 [V10.0.18.0.PDIMIXM]: - removed!
https://bigota.d.miui.com/V10.0.18....0.PDIMIXM_20191211.0000.00_9.0_33e3d9a287.tgz
Android 9.0 [V10.0.17.0.PDIMIXM]:
https://bigota.d.miui.com/V10.0.17....0.PDIMIXM_20191108.0000.00_9.0_94629a1855.tgz
Android 9.0 [V10.0.13.0.PDIMIXM]:
https://bigota.d.miui.com/V10.0.13....0.PDIMIXM_20190807.0000.00_9.0_9083804c9e.tgz
Android 9.0 [V10.0.12.0.PDIMIXM]:
https://bigota.d.miui.com/V10.0.12....0.PDIMIXM_20190712.0000.00_9.0_1e580ee45b.tgz
Android 9.0 [V10.0.10.0.PDIMIXM]:
https://bigota.d.miui.com/V10.0.10....0.PDIMIXM_20190611.0000.00_9.0_9e6473956a.tgz
Android 9.0 [V10.0.9.0.PDIMIXM]:
https://bigota.d.miui.com/V10.0.9.0...0.PDIMIXM_20190513.0000.00_9.0_bbaa8993fe.tgz
Android 9.0 [V10.0.8.0.PDIMIXM]:
https://bigota.d.miui.com/V10.0.8.0...0.PDIMIXM_20190411.0000.00_9.0_bacce1f2bd.tgz
Android 9.0 [V10.0.7.0.PDIMIXM]:
https://bigota.d.miui.com/V10.0.7.0...0.PDIMIXM_20190323.0000.00_9.0_b92b08b636.tgz
Android 9.0 [V10.0.2.0.PDIMIFJ]:
https://bigota.d.miui.com/V10.0.2.0...0.PDIMIFJ_20181206.0000.00_9.0_02b8deeb6d.tgz
Android 8.1.0 [V9.6.17.0.ODIMIFE]:
https://bigota.d.miui.com/V9.6.17.0...0.ODIMIFE_20181108.0000.00_8.1_1c60295d1c.tgz
Android 8.1.0 [V9.6.16.0.ODIMIFE]:
https://bigota.d.miui.com/V9.6.16.0...0.ODIMIFE_20181030.0000.00_8.1_5e098a2c1a.tgz
Android 8.1.0 [V9.6.14.0.ODIMIFE]:
https://bigota.d.miui.com/V9.6.14.0...0.ODIMIFE_20181010.0000.00_8.1_94929604f8.tgz
Android 8.1.0 [V9.6.13.0.ODIMIFE]:
https://bigota.d.miui.com/V9.6.13.0...0.ODIMIFE_20180913.0000.00_8.1_fbd1120565.tgz
Android 8.1.0 [V9.6.10.0.ODIMIFE]:
https://bigota.d.miui.com/V9.6.10.0...0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz
Android 8.1.0 [V9.6.9.0.ODIMIFE]:
https://bigota.d.miui.com/V9.6.9.0....0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Use
Code:
fastboot flashing unlock
to unlock the bootloader.
You may also need to unlock the critical partitions by typing:
Code:
fastboot flashing unlock_critical
You can flash factory images using the batchfile in the firmware archive or using MiFlash. You can also flash in Snapdragon EDL-(Emergency Download) Mode (bootloader unlocked is necessary) by typing:
Code:
fastboot oem edl
(Instructions about flashing and download links can be found here [PC only!]) https://c.mi.com/oc/miuidownload/detail?guide=2
Reserved
Reserved
sorry guys, trying to flashing stock rom with mi flash tools and relock bootloader but it says me that critical partition flashing is not allowed, what i have to do ?
Ivan93tm said:
sorry guys, trying to flashing stock rom with mi flash tools and relock bootloader but it says me that critical partition flashing is not allowed, what i have to do ?
Click to expand...
Click to collapse
Try this: http://en.miui.com/a-232.html
I haven't tested anything yet.
Niktendo said:
Try this: http://en.miui.com/a-232.html
I haven't tested anything yet.
Click to expand...
Click to collapse
Thanks, i'll give it a try, for the moment i will keep 9.6.5 version , i reflashed stock boot and everiting is fine with relocking bootloader but for now i can't have camera api enabled
Ivan93tm said:
sorry guys, trying to flashing stock rom with mi flash tools and relock bootloader but it says me that critical partition flashing is not allowed, what i have to do ?
Click to expand...
Click to collapse
Use this fastboot command by default to unlock bootloader:
Code:
fastboot flashing unlock_critical
error flashing
i got this error flashing latest fasboot image using mi flash tools
DeeditTotoi said:
i got this error flashing latest fasboot image using mi flash tools
Click to expand...
Click to collapse
Try again with more available RAM (eg. close Google Chrome).
I got the same error even with only miflash open and 8gb ram.
Hi I have a MI6X can I flash this rom??
Thanks
abefre said:
Hi I have a MI6X can I flash this rom??
Thanks
Click to expand...
Click to collapse
In theory - yes http://en.miui.com/thread-3439864-1-1.html But you can break your phone very easily doing it.
Cagixxx said:
I got the same error even with only miflash open and 8gb ram.
Click to expand...
Click to collapse
Did you install all Xiaomi drivers using MiFlash and disabled driver signature?
Did you also unlock the critical partitions?
Try one of the batch files from the stock rom via command prompt. E.g. flash_all.bat, which worked for me as MiFlash did not want to do the job, too. Unlock critical is needed though.
The only way to flash was in EDL/Test Point mode. I opened the phone but you can use a Xiaomi deep flash cable (EDL cable).
Cagixxx said:
The only way to flash was in EDL/Test Point mode. I opened the phone but you can use a Xiaomi deep flash cable (EDL cable).
Click to expand...
Click to collapse
You can also boot into EDL mode from fastboot (needs bootloader unlocked) by typing the following command:
Code:
fasboot oem edl
So did anyone flash fastboot ROM with success using MiFlash or not?
pianistaPL said:
So did anyone flash fastboot ROM with success using MiFlash or not?
Click to expand...
Click to collapse
Yes, my flash succeeded sucessfully after the second try. I got an error (system_b flashing failed), I closed Chrome to free up more RAM and the flash finished.
To unlock the bootloader, do I need to create a xiaomi account and request a token to unlock it or can I use the usual
>fastboot oem unlock
?
cbrunos said:
To unlock the bootloader, do I need to create a xiaomi account and request a token to unlock it or can I use the usual
>fastboot oem unlock
?
Click to expand...
Click to collapse
You can unlock the bootloader for the Xiaomi Mi A1 and A2/Lite (Xiaomi Android One smartphones) by typing:
Code:
fastboot flashing unlock
OR
Code:
fastboot oem unlock
You also need to unlock the critical partitions by typing:
Code:
fastboot flashing unlock_critical
rom unbrick Mi6x LINK : drive.google.com/file/d/1fZyJ2orTrMpsNzWbhKGR8kvSYf-8KGRS/view?usp=sharing
link : drive.google.com/file/d/1dyaJr1IgS8Rwk0GI-BJJ-SaKdWWVnk8o/view?usp=sharing
mrdamnguyen said:
link : drive.google.com/file/d/1dyaJr1IgS8Rwk0GI-BJJ-SaKdWWVnk8o/view?usp=sharing
Click to expand...
Click to collapse
Guys does this actually unbrick a converted mi 6x wayne locked bootloader arb 4???
Quantumkk123 said:
Guys does this actually unbrick a converted mi 6x wayne locked bootloader arb 4???
Click to expand...
Click to collapse
the thing is that if it is a rom.zip, with yr situation how can you flash it when yr bootloader is locked and no twrp.
Or u try first and let people know
I want to unbrick on pie, need developer version for 9.0
jaggyjags said:
I want to unbrick on pie, need developer version for 9.0
Click to expand...
Click to collapse
You don't need it your gonna have to downgrade back to Oreo it's same arb so nothing bad will happen XD
Quantumkk123 said:
You don't need it your gonna have to downgrade back to Oreo it's same arb so nothing bad will happen XD
Click to expand...
Click to collapse
then why do I get this message with oreo MIUI 10.2 rom?
View attachment 4727603
jaggyjags said:
then why do I get this message with oreo MIUI 10.2 rom?
Click to expand...
Click to collapse
If your bootloader is locked that's the reason why ,if it's not then you haven't put your phone into fastboot oem edl
Quantumkk123 said:
If your bootloader is locked that's the reason why ,if it's not then you haven't put your phone into fastboot oem edl
Click to expand...
Click to collapse
Code:
C:\Users\jags1\Desktop\wayne\ADB>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
Finished. Total time: 0.011s
this is weird
jaggyjags said:
Code:
C:\Users\jags1\Desktop\wayne\ADB>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
Finished. Total time: 0.011s
this is weird
Click to expand...
Click to collapse
its because your doing it via fastboot and because you have arb it won't permit what your gonna do now is go on to your cmd or whatever type this command
.\adb fastboot oem
then hit refresh on mi flash then click flash if that still doesnt work then i am afraid you need to open up your device mate
Quantumkk123 said:
its because your doing it via fastboot and because you have arb it won't permit what your gonna do now is go on to your cmd or whatever type this command
.\adb fastboot oem
then hit refresh on mi flash then click flash if that still doesnt work then i am afraid you need to open up your device mate
Click to expand...
Click to collapse
opening up my device is not a problem. Can you guide me on what to do with the mainboard?
HTML:
C:\Users\jags1\Desktop\wayne\ADB>.\adb fastboot oem
adb: usage: unknown command fastboot
C:\Users\jags1\Desktop\wayne\ADB>.\adb fastboot oem
adb: usage: unknown command fastboot
C:\Users\jags1\Desktop\wayne\ADB>fastboot oem
fastboot: usage: empty oem command
C:\Users\jags1\Desktop\wayne\ADB>
your command was correct?
thankyou for your help
jaggyjags said:
this is weird
Click to expand...
Click to collapse
Ok you seems to be lost lol ? emm chat to this group on telegram and I will guide you ... https://t.me/A2_6X
password
mrdamnguyen said:
link : drive.google.com/file/d/1dyaJr1IgS8Rwk0GI-BJJ-SaKdWWVnk8o/view?usp=sharing
Click to expand...
Click to collapse
give mepassword
After install to EU dev. 9.7.18
NO recovery more and no access to the System, only bootloop, just Soft bricked my phone.
So I decided to install into fastboot mode the global stable 10.3.6 tgz and modified the anti rollback error.
here the rom
https://mifirm.net/model/davinci.ttt#fb-mif
here the anti rollback tutorial
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
Flash then with MiFlash (choose an older version and don't flag lock bootloader)
https://www.xiaomiflash.com/download/
regards
stefano alegnini said:
After install to EU dev. 9.7.18
NO recovery more and no access to the System, only bootloop, just Soft bricked my phone.
So I decided to install into fastboot mode the global stable 10.3.6 tgz and hacked the anti rollback error.
here the rom
https://mifirm.net/model/davinci.ttt#fb-mif
here the anti rollback tutorial
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
Flash then with MiFlash (don't flag lock bootloader)
https://www.xiaomiflash.com/download/
regards
Click to expand...
Click to collapse
fastboot Rom when checked flash-all.bat CURRENT_ANTI_VER=0 , but my current device is Anti 1. Can i proceed install through Miflash tool?
what did you mean by hacked the antirollback error?
DtoD said:
fastboot Rom when checked flash-all.bat CURRENT_ANTI_VER=0 , but my current device is Anti 1. Can i proceed install through Miflash tool?
what did you mean by hacked the antirollback error?
Click to expand...
Click to collapse
If your device is 1 (anti rollback enabled) the TGZ rom must be 1 or major.
Open flash-all.bat in a text editor like Notepad++ and look for the following line: set CURRENT_ANTI_VER=#
That number (#) is the rollback index of the MIUI version you want to flash. If that number is equal to or greater than your current rollback index, then it’s safe to flash in TWRP, Mi Flash, etc. If that number is less than your current rollback index
what did you mean by hacked the antirollback error?
modified...
stefano alegnini said:
If your device is 1 (anti rollback enabled) the TGZ rom must be 1 or major.
Open flash-all.bat in a text editor like Notepad++ and look for the following line: set CURRENT_ANTI_VER=#
That number (#) is the rollback index of the MIUI version you want to flash. If that number is equal to or greater than your current rollback index, then it’s safe to flash in TWRP, Mi Flash, etc. If that number is less than your current rollback index
what did you mean by hacked the antirollback error?
modified...
Click to expand...
Click to collapse
Friend, I also have the same question ... Is something concrete modified? My software was the global version 10.3.9 and now I can not repair with the fastboot version 10.3.6 ...
What I can do?
How did you solve it?
I did something different, easier in my opinion:
• Downloaded a fastboot rom and uncompress it
• extracted the files: system.img, recovery.img and boot.img
• Flashed them with CMD/Terminal
• Erased data
• Rebooted
menphis said:
Friend, I also have the same question ... Is something concrete modified? My software was the global version 10.3.9 and now I can not repair with the fastboot version 10.3.6 ...
What I can do?
How did you solve it?
Click to expand...
Click to collapse
I just flashed fastboot rom , everything is alright. My Anti was 1 but the rom's Anti was 0. I flashed it through Miflash tool. Everything seems to work well
DtoD said:
I just flashed fastboot rom , everything is alright. My Anti was 1 but the rom's Anti was 0. I flashed it through Miflash tool. Everything seems to work well
Click to expand...
Click to collapse
can you explain a little more details, please?
or from which versions you have successfully flashed?
cmoegele said:
can you explain a little more details, please?
or from which versions you have successfully flashed?
Click to expand...
Click to collapse
I was on Developer beta, bootlooping without recovery, Only fastboot continue was working
I flashed this fastboot rom from the OP https://mifirm.net/model/davinci.ttt#fb-mif
Download fastboot rom > Extract > use Miflash( Download here https://www.xiaomiflash.com/download/ ) > flash Fastboot rom
I have mi9t and i use OSX, dont have windows. when installing xeu dev 9.7.18 twrp gone, i downloaded 10.3.6 stable global fastboot rom. i unpack rom and edited flash_all file as in osx comad for fastboot is not as on windows in os x is ./fastboot
so in any fastboot writen on flash_all i had to put prefix ./ and in terminal i flash fastboot rom, no problems about antiroll back.
Any way on how to change the Region? it got locked to China
solved by flashing cust.img
stefano alegnini said:
After install to EU dev. 9.7.18
NO recovery more and no access to the System, only bootloop, just Soft bricked my phone.
So I decided to install into fastboot mode the global stable 10.3.6 tgz and modified the anti rollback error.
here the rom
https://mifirm.net/model/davinci.ttt#fb-mif
here the anti rollback tutorial
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
Flash then with MiFlash (don't flag lock bootloader)
https://www.xiaomiflash.com/download/
regards
Click to expand...
Click to collapse
So basically there is anti rollback protection concerning EU rom and global rom?
Pheggas said:
So basically there is anti rollback protection concerning EU rom and global rom?
Click to expand...
Click to collapse
yes, from weekly EU to global stable
stefano alegnini said:
yes, from weekly EU to global stable
Click to expand...
Click to collapse
One of users told me there is no anti rollback protection.
Odoslané z Mi 9T pomocou Tapatalku
There is no anti roll-back in our phone. You can safely flash everything for our davinci I think. I flashed 10.3.7.0 and all was working fine.
DtoD said:
I was on Developer beta, bootlooping without recovery, Only fastboot continue was working
I flashed this fastboot rom from the OP https://mifirm.net/model/davinci.ttt#fb-mif
Download fastboot rom > Extract > use Miflash( Download here https://www.xiaomiflash.com/download/ ) > flash Fastboot rom
Click to expand...
Click to collapse
Does developer rom released on davinci?
rEsonancE_0404 said:
Does developer rom released on davinci?
Click to expand...
Click to collapse
Yes it did https://forum.xda-developers.com/mi-9t/how-to/rom-miui-10-xiaomi-eu-t3949848
But you will lose your recovery after flashing the Developer version.
Guys I need help I flash the latest ue developer ROM got boot loop and the I flashed the global ROM via mi flash but I my phone doesn't boot up pls help me
Benfatica said:
Guys I need help I flash the latest ue developer ROM got boot loop and the I flashed the global ROM via mi flash but I my phone doesn't boot up pls help me
Click to expand...
Click to collapse
Sometimes the unlock text disappear leaving the mi.com logo but it just turns it self off
stefano alegnini said:
After install to EU dev. 9.7.18
NO recovery more and no access to the System, only bootloop, just Soft bricked my phone.
So I decided to install into fastboot mode the global stable 10.3.6 tgz and modified the anti rollback error.
here the rom
https://mifirm.net/model/davinci.ttt#fb-mif
here the anti rollback tutorial
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
Flash then with MiFlash (don't flag lock bootloader)
https://www.xiaomiflash.com/download/
regards
Click to expand...
Click to collapse
The mi flash.zip gives me error
Benfatica said:
The mi flash.zip gives me error
Click to expand...
Click to collapse
Try an older version
Hi!
First off: I'm new to this forum, so if this is not the right place to post or is in the wrong format or whatever, please point me in the right direction.
I'm trying to install LineageOS on my Xiaomi Mi 9T and have gotten stuck in fastboot. I am currently trying to flash the recovery image for Lineage so that i can sideload the Lineage zip, but the phone just boots back to the fastboot mode no matter what I do.
One single time I managed to enter the custom recovery I flashed onto there, but after formatting all partitions, my attempt to sideload the LineageOS zip failed.
I thought I'd just reboot to the recovery and repeat my steps, but since then I have not managed to come back into the recovery mode.
Now I am frantically trying to flash the recovery image onto my phone with no success. The fastboot tool on my PC just says this (which seems fine):
Code:
fastboot flash recovery lineage-17.1-20210327-microG-davinci-recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.446s]
Writing 'recovery' OKAY [ 0.148s]
Finished. Total time: 1.600s
After that I've tried:
Holding power off + vol up
Holding power off + vol down
Holding power off
Holding power off + vol up + vol down
After some searching I have also tried:
Code:
fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
Which SHOULD have booted it into recovery mode, bur nope. Whatever I do I find myself back in fastboot mode.
I have also tried flashing TWRP recovery image (never used it before), just to try something else, but with no success. Same results as with the Lineage recovery image.
How do I get out of this loop and back to installing LineageOS?
I've done this once before with a OnePlus2, but that was painless compared to this.
I appriciate any help. Thanks in advance.
Just found this thread: https://forum.xda-developers.com/t/mi-9t-stuck-in-the-fastboot-menu.4089181/
I'll be looking into it
Hi, same problem here. Flashed TWRP in 1.932 seconds or something but never was able to boot into TWRP. I found a thread on here saying to oem reboot-recovery. Tried that, didn't work. Found some message by the guy who wrote the TWRP saying to flash some other file, but I don't understand what he means. Have you been able to solve the problem ?
Okay, I have solved this for my phone.
I found this soulution on some forum, but do not remember where exactly, so credit is not mine.
I am new to all of this, so proceed on your own risk with this "guide". It worked for me and got me a running install of MIUI (chineese version).
Download the zip from here. There are two buttons to do so. This zip contains a set of scripts and resources to fix your phone.
Extract the zip to a folder somewhere.
Connect your softbricked phone with USB and make sure it is in fastboot mode and that your computer see it as a fastboot device (run "fastboot devices" in cmd and make sure the device shows up).
Run "flash_all.bat" from the extracted zip, if the script finishes successfully, skip to step 7.
For me the following lines failed when running the script:
Code:
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist error" && exit /B 1
Delete or comment these lines from the script.
Run the script again. If it didn't work the first time, it hopefully worked now.
Reboot the phone if it does not do so itself. MIUI (chineese version) should now boot.
From here you should be able to enable developer options and ADB or boot into fastboot and flash new recovery images or whatever you want to do.
What caused the soft brick initially remains unclear to me, but this solved my problem and I am now running the ROM I wanted to run initially (Lineage for microG).
I hope this helps.
a
hannesknutsson said:
Run "flash_all.bat" from the extracted zip, if the script finishes successfully, skip to step 7.
For me the following lines failed when running the script:
Code:
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist error" && exit /B 1
Delete or comment these lines from the script.
Click to expand...
Click to collapse
Hey, thanks for that. I tried that but I got some other error :
davinci_images_V12.1.1.0.RFJCNXM_20210221.0000.00_11.0_cn_c268db27f4\davinci_images_V12.1.1.0.RFJCNXM_20210221.0000.00_11.0_cn>fastboot flash sparsecrclist C:\Users\cbkra\Downloads\davinci_images_V12.1.1.0.RFJCNXM_20210221.0000.00_11.0_cn_c268db27f4\davinci_images_V12.1.1.0.RFJCNXM_20210221.0000.00_11.0_cn\images\sparsecrclist.txt ||
target reported max download size of 805306368 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.011s]
writing 'sparsecrclist'...
FAILED (remote: update sparse crc list failed)
finished. total time: 0.016s
"Flash sparsecrclist error"
It does not look like you deleted the lines I specified from the script. Are you sure you have deleted the lines:
Code:
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist error" && exit /B 1
I hadn't, but now I have. It seemed to worked fine until it got an unknown error.
sending sparse 'system' (774312 KB)...
OKAY [ 23.168s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (774312 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 83.881s
"Flash system error"
From here I have no idea how to solve your problem.
I would just try running the same script a couple of more times, but that's just because I can't come up with something better to do.
hannesknutsson said:
From here I have no idea how to solve your problem.
I would just try running the same script a couple of more times, but that's just because I can't come up with something better to do.
Click to expand...
Click to collapse
Thank you for your help. I took it to a shop and that yielded the same result. They suggested the motherboard may have become faulty. I'll try again, thanks !
Yeah. If your anti rollback protection has triggered your phone may be bricked. I'm not sure how all that work, but that's what I understand of it.
Yeah the fix is actually to have the ROM and the MiFlash tool both on your C: drive for whatever reason.
Did work for me afterwards, without the Anti Rollback error
Only the path to the ROM is important : I always copy mine to C:\ but something simple like C:\TEMP\ should work too!
Avoid :
- Spaces in your path.
- Very long paths.
And you are good to go!
Also note that deleting lines in scripts can be dangerous and you should always tick the right options in the tool you are using!
Only Flash Custom ROMs via TWRP and Stock ROMs via the Mi Flash Tool
EDIT: I mistakenly thought this thread was talking about the Redmi 9T but it's for the Xaomi Mi 9T. So ignore all the links I pasted below as they are for the wrong phone.
Thanks so much for posting this I managed to recover my redmi 9t. I had to use the lime version of the firmware https://mifirm.net/download/6391 as opposed to the davinci version. Also I used official xiaomi flashing tool MiFlash20210813.zip from windows. It reset my phone to stock. I attempted to flash OrangeFox recovery again via OrangeFox-R11.1_2-Unofficial-avicii.zip and OrangeFox-R11.1_0-Unofficial-garden.zip as well as the latest beta from https://orangefox.download/device/garden and they all result in a fastboot loop.... I'm not really sure how to avoid it. Luckily it's easy to recover by flashing back just the recovery.img from the stock image, now that I've fully flashed the whole phone so I know which stock image to use.
UPDATE:
I just used twrp in the end as orangefox wasn't working for me, i would have liked to have used the "juice" version mentioned here https://forum.xda-developers.com/t/...t-r11-1-juice-lime-citrus-unofficial.4257459/ as the newer garden version wasn't working for me, but the files seem to have all disappeared in favor of the newer ones that don't work for me.
peter64 said:
Thanks so much for posting this I managed to recover my redmi 9t. I had to use the lime version of the firmware https://mifirm.net/download/6391 as opposed to the davinci version. Also I used official xiaomi flashing tool MiFlash20210813.zip from windows. It reset my phone to stock. I attempted to flash OrangeFox recovery again via OrangeFox-R11.1_2-Unofficial-avicii.zip and OrangeFox-R11.1_0-Unofficial-garden.zip as well as the latest beta from https://orangefox.download/device/garden and they all result in a fastboot loop.... I'm not really sure how to avoid it. Luckily it's easy to recover by flashing back just the recovery.img from the stock image, now that I've fully flashed the whole phone so I know which stock image to use.
UPDATE:
I just used twrp in the end as orangefox wasn't working for me, i would have liked to have used the "juice" version mentioned here https://forum.xda-developers.com/t/...t-r11-1-juice-lime-citrus-unofficial.4257459/ as the newer garden version wasn't working for me, but the files seem to have all disappeared in favor of the newer ones that don't work for me.
Click to expand...
Click to collapse
To avoid any confusion. Your post is about Redmi 9T (lime) - but this thread here is about Mi 9T/Redmi K20 (davinci)
Phones are different: firmwares, recoveries for one do not apply to the other
Different size, design, chipset, display, everything:
Compare Xiaomi Mi 9T vs. Xiaomi Redmi 9T - GSMArena.com
www.gsmarena.com
The corresponding XDA forum for your Redmi 9T:
Redmi 9 Power / 9T
The Redmi 9 Power is a 6.53" phone with a 1080x2340p resolution display. The Qualcomm SM6115 Snapdragon 662 chipset is paired with 4GB of RAM and 65/128GB of storage. The main camera is 48+8+2+2MP and the selfie camera is 8MP. The battery has a 6000mAh capacity.
forum.xda-developers.com
zgfg said:
To avoid any confusion. Your post is about Redmi 9T - this thread here is about Mi 9T.
These are totally different phones: firmwares, recoveries for one do not apply to the other
Different size, design, chipset, display, everything:
Compare Xiaomi Mi 9T vs. Xiaomi Redmi 9T - GSMArena.com
www.gsmarena.com
XDA Redmi 9T forum:
Redmi 9 Power / 9T
The Redmi 9 Power is a 6.53" phone with a 1080x2340p resolution display. The Qualcomm SM6115 Snapdragon 662 chipset is paired with 4GB of RAM and 65/128GB of storage. The main camera is 48+8+2+2MP and the selfie camera is 8MP. The battery has a 6000mAh capacity.
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, I totally missed that. It's good I noticed davinci wasn't the same as lime. I'll edit my comment to ensure I don't confuse anyone else unecessarily.
Hi everyone. I've already rooted my Huawei P9 lite and now I'd like to update it to Android Nougat.
I tried to install different versions of firmware through OTA, but none of them worked out well. I'm starting to think that this is due to the firmware which are not compatible with my device, and considering that my build number is quite uncommon, that could also be the case. I read from some threads that I have to unroot and lock the bootloader again in order to perform the update, but honestly I'm too lazy right now and I'd prefer to keep my device rooted if it's possible.
Does anybody know what could I do in this case?
OEM Build Number: VNS-L31ITAC555B160
OEM Product Model: HUAWEI VNS-L31
Vendor Country: h3g/it
xXRobyXx said:
Hi everyone. I've already rooted my Huawei P9 lite and now I'd like to update it to Android Nougat.
I tried to install different versions of firmware through OTA, but none of them worked out well. I'm starting to think that this is due to the firmware which are not compatible with my device, and considering that my build number is quite uncommon, that could also be the case. I read from some threads that I have to unroot and lock the bootloader again in order to perform the update, but honestly I'm too lazy right now and I'd prefer to keep my device rooted if it's possible.
Does anybody know what could I do in this case?
OEM Build Number: VNS-L31ITAC555B160
OEM Product Model: HUAWEI VNS-L31
Vendor Country: h3g/it
Click to expand...
Click to collapse
Hi,
you have to rebrand to the Global version (IMO) :
1. install TWRP 3.0.2.0 , Link
2. In TWRP flash C432 oeminfo.zip Link
3. Go back to TWRP's menu without reboot
4. Follow instructions (from step 3.).
-Alf- said:
Hi,
you have to rebrand to the Global version (IMO) :
1. install TWRP 3.0.2.0 , Link
2. In TWRP flash C432 oeminfo.zip Link
3. Go back to TWRP's menu without reboot
4. Follow instructions (from step 3.).
Click to expand...
Click to collapse
Thanks for your help. Is the VNS-L31C432B370 firmware compatible with single sim?
xXRobyXx said:
Is the VNS-L31C432B370 firmware compatible with single sim?
Click to expand...
Click to collapse
No, that's why I gave you the link to oeminfo dual Sim. If that's a problem for you, try looking for the B371, I didn't find one.
-Alf- said:
No, that's why I gave you the link to oeminfo dual Sim. If that's a problem for you, try looking for the B371, I didn't find one.
Click to expand...
Click to collapse
It's not a problem for me. What problems could I encounter if I use a dual sim firmware?
M
xXRobyXx said:
It's not a problem for me. What problems could I encounter if I use a dual sim firmware?
Click to expand...
Click to collapse
It has no effect on the phone's functionality.
Btw, there's B371 Link ,but it may be password protected . For Single SIM firmware use this Oeminfo.zip
-Alf- said:
M
It has no effect on the phone's functionality.
Btw, there's B371 Link ,but it may be password protected . For Single SIM firmware use this Oeminfo.zip
Click to expand...
Click to collapse
I tried to flash the C432 oeminfo, but after rebooting a black screen with red text appears and I can't unlock my phone because it's unable to decrypt the internal archive. Same thing with the singlesim oem info.
Also I can't mount the Internal Storage from TWRP because it results as 0 MB.
The only way I found to solve this issue is by restoring the original oeminfo from a previous backup.
xXRobyXx said:
tried to flash the C432 oeminfo, but after rebooting a black screen with red text appears
Click to expand...
Click to collapse
-Alf- said:
Go back to TWRP's menu without reboot
Click to expand...
Click to collapse
-Alf- said:
4. Follow instructions (from step 3.).
Click to expand...
Click to collapse
I've installed the с432b370 update correctly, but I can't flash the data package (update_data_full_VNS-L31_hw_eu.zip).
xXRobyXx said:
I've installed the с432b370 update correctly, but I can't flash the data package (update_data_full_VNS-L31_hw_eu.zip).
Click to expand...
Click to collapse
it happens sometimes...
Just to be sure - reboot to fastboot mode and run command:
fastboot oem get-build-number
and post result.
-Alf- said:
it happens sometimes...
Just to be sure - reboot to fastboot mode and run command:
fastboot oem get-build-number
and post result.
Click to expand...
Click to collapse
Now it is NRD90M test-keys, before it was VNS-L31ITAC555B160
xXRobyXx said:
Now it is NRD90M test-keys, before it was VNS-L31ITAC555B160
Click to expand...
Click to collapse
Okay, now read carefully:
1. Download TWRP for Nougat Link
2. Flash it over eRecovery (!)
using command:
fastboot flash recovery2 twrp3102.img (recovery2 , not recovery!)
3. Flash stock Recovery Nougat
Link use:
fastboot flash recovery xxxxx.img
4. Reboot, when yellow warning appears, press and hold Volume Up for 3-4 seconds, you should boot into TWRP
5. In TWRP select Wipe - Format data - yes - confirm. Go back - Reboot - System
6. And again, after yellow warning Volume Up and reboot TWRP. Now you can try install second .zip file hw_eu.
7. Reboot into Recovery and do factory reset.
Good luck!
-Alf- said:
Okay, now read carefully:
1. Download TWRP for Nougat Link
2. Flash it over eRecovery (!)
using command:
fastboot flash recovery2 twrp3102.img (recovery2 , not recovery!)
3. Flash stock Recovery Nougat
Link use:
fastboot flash recovery xxxxx.img
4. Reboot, when yellow warning appears, press and hold Volume Up for 3-4 seconds, you should boot into TWRP
5. In TWRP select Wipe - Format data - yes - confirm. Go back - Reboot - System
6. And again, after yellow warning Volume Up and reboot TWRP. Now you can try install second .zip file hw_eu.
7. Reboot into Recovery and do factory reset.
Good luck!
Click to expand...
Click to collapse
Code:
target reported max download size of 471859200 bytes
sending 'recovery2' (24462 KB)...
OKAY [ 0.713s]
writing 'recovery2'...
FAILED (remote: Command not allowed)
finished. total time: 0.713s
I'm sure that Phone and FRP are unlocked.
xXRobyXx said:
Code:
target reported max download size of 471859200 bytes
sending 'recovery2' (24462 KB)...
OKAY [ 0.713s]
writing 'recovery2'...
FAILED (remote: Command not allowed)
finished. total time: 0.713s
I'm sure that Phone and FRP are unlocked.
Click to expand...
Click to collapse
In other words, my instructions are wrong?
Okay, have a nice evening!
-Alf- said:
In other words, my instructions are wrong?
Okay, have a nice evening!
Click to expand...
Click to collapse
Hey, I'm not doubting your instructions! Hahaha.
I'm just asking, what should I do now? I can't flash TWRP to recovery2 if it doesn't allow me to commit any command.
xXRobyXx said:
doesn't allow me to commit any command.
Click to expand...
Click to collapse
And you are sure that Phone and FRP are unlocked? Hahaha.
-Alf- said:
And you are sure that Phone and FRP are unlocked? Hahaha.
Click to expand...
Click to collapse
Yeah
xXRobyXx said:
Yeah
Click to expand...
Click to collapse
Restart your phone, if the BL is really unlocked, after restart appears on screen yellow warning. Fastboot sometimes lies...
-Alf- said:
Restart your phone, if the BL is really unlocked, after restart appears on screen yellow warning. Fastboot sometimes lies...
Click to expand...
Click to collapse
Okay, finally I flashed TWRP. After restart, I pressed Volume Up key but it remains on the yellow warning screen with the text "Your device is booting now...".
Edit:
I solved this by installing Venus TWRP for P9 lite. Then, I followed all the instructions and updated to B416 through dlaod, and later to B418 through OTA. Additionally, I had to unlock the bootloader again and root.
Now I have a fully-functional P9 lite updated to Android Nougat
xXRobyXx said:
Hi everyone. I've already rooted my Huawei P9 lite and now I'd like to update it to Android Nougat.
I tried to install different versions of firmware through OTA, but none of them worked out well. I'm starting to think that this is due to the firmware which are not compatible with my device, and considering that my build number is quite uncommon, that could also be the case. I read from some threads that I have to unroot and lock the bootloader again in order to perform the update, but honestly I'm too lazy right now and I'd prefer to keep my device rooted if it's possible.
Does anybody know what could I do in this case?
OEM Build Number: VNS-L31ITAC555B160
OEM Product Model: HUAWEI VNS-L31
Vendor Country: h3g/it
Click to expand...
Click to collapse
Which process did you follow for the root?