Related
I was looking for a light 2.1 rom and found this one: http://forum.xda-developers.com/showthread.php?t=1038337 (Lite edition)
Being a beginner, i got a few questions.
Do i need my phone flashed to V20E using .kdz beforehand? My current is V20B + fastboot.
There is kernel img provided, but iam not sure how to use it.
Which clockwork recovery do i need? As i understand 2.1 roms can only be flashed with old recoveries, such as 2.5.x.x . My current version is 3.0.2.4.
Thanks.
Img files can be flashed via fastboot commands:
on your PC type:
fastboot devices (makes sure its recognized)
fastboot -w (wipes data, cache)
fastboot erase boot
fastboot erase system
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
You'll need the fastboot drivers to be installed of course
Tnx for fast reply.
But do i need V20E.kdz rom specifically and flash my phone with KDZ updater? I couldnt find working links for V20E.kdz, only A,B&C.
berins said:
Tnx for fast reply.
But do i need V20E.kdz rom specifically and flash my phone with KDZ updater? I couldnt find working links for V20E.kdz, only A,B&C.
Click to expand...
Click to collapse
nope thats not needed
When I try to flash TWRP (via "fastboot flash recovery twrp.img" then "fastboot boot twrp.img") I receive the following error:
Downloading 'boot.img'
OKAY [1.477s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.534s
I've tried manually booting it into recovery with power button and volume down but it just freezes on the oneplus logo where I have to turn off and on again.
Any help is greatly appreciated!
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
that link just saved me!
I tried this recovery (I had the same problem as the OP) but although I can boot into twrp, I get stuck on the oneplus logo if I try a normal boot?
Sent from my Nexus 9 using XDA-Developers mobile app
I managed to get it working by flashing CM after flashing the recovery.
Sent from my Nexus 9 using XDA-Developers mobile app
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
pitrus- said:
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
Click to expand...
Click to collapse
Actually, fastboot boot twrp.img boots the TWRP image without flashing it.
fastboot flash recovery twrp.img flashes the TWRP image to the recovery partition.
Both are valid commands and have their uses.
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Spannaa said:
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Click to expand...
Click to collapse
That's exactly what I meant to convey.
Similar problem while flashing recovery
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
bhanuodin said:
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
Click to expand...
Click to collapse
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
pitrus- said:
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
Click to expand...
Click to collapse
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
bhanuodin said:
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
Click to expand...
Click to collapse
The bootloader (also called fastboot) comes with the original ROM. In your case you're already on the newer bootloader since you flashed OOS3 which means you will have to flash recoverys and ROMs compatible with this newer bootloader.
This TWRP should be compatible
https://dl.twrp.me/oneplus2/twrp-3.0.2-1-oneplus2.img.html
Also you can't run ROMs not compatible with this newer bootloader (which means pretty much any ROM that's not using the official Cyanogenmod source tree for building). That is except for OOS3 or newest HOS of course since these are made for the newer bootloader.
However I would say the error message you get might be caused by bad cable, faulty driver setup, faulty fastboot tool version or in worst case damaged partition layout on phone. The last one can be fixed by the Qualcomm OOS2 factory restore solution.
Hi, i am having the same problem.
some background: I was on Oxygen OS 2.x.x, i wanted to upgrade to Exodus 6. I had the older version of TWRP. So I tryed to install the new twrp image within twrp. When i rebooted i couldnt boot into twrp, receiving the same error message as in OP title, when using fastboot.
Using the tool all in one toolkit I was able to flash stock recovery.
But I still cant flash Twrp.
I can still boot into system though.
Any advice? Thanks.
That explains why you're having problems. You're doing it the wrong way.
First you must upgrade the bootloader by either flashing the convert to Marshmallow zip file which also installs the correct TWRP for the new bootloader (easiest way). Or you could flash the latest official OOS3, then fastboot flash the latest TWRP and from there format system and flash the ROM that's using the newer bootloader.
Does that Link work with oneplus x also? Having same problem as Higgings when trying to install twrp and cyanogenmod.
thnx a lot for sharing
:good:
Higgings said:
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
Click to expand...
Click to collapse
Hi there,
sorry, if this was answered before, but I couldn't find the correct answer:
After trying to flash a custom ROM (CMOD) I'm stuck now at the Cyanogen Mod boot animation.
If pressing "Power" button for a while the phone reboots, but gives me again the same boot animation (after ZUK logo).
If pressing "Power" + "Volume +" + "Volume -" buttons for a while the phone reboots, but gives me again the same boot animation (after ZUK logo).
The phone is not recognized via USB on a computer.
Anybody has still an idea what I could do?
Many thanks in advance for hints
best regards
m
What are the steps you followed before you ended up in this situation? What rom were you previously on? Provide as much details as you can without being redundant.
KKaushal said:
What are the steps you followed before you ended up in this situation? What rom were you previously on? Provide as much details as you can without being redundant.
Click to expand...
Click to collapse
I was coming from latest stock. The attempt was to flash CM14.
1.) flash in the thread linked twrp
2.) flash CM14 and Nougat GAPPS micro
3.) reboot ok
4.) fingerprint didn't react, so went back to recovery and flashed both again, causing this loop
many thanks again for any help/hint
best regards
m
If the first time boot with the rom and gapps was okay, maybe you should try wiping /system, /data, /dalvik and /cache and reflash the rom again.. Since you were in stock cmos 12.1, I think it'll be better if you flash official cm13 first, and then jump to cm14 from there to minimize sensor issues such as with the fingerprint like you experienced.
meikelrix said:
any help/hint
Click to expand...
Click to collapse
Mate if you think you're done with everything and nothing seems to help, just search around here how to flash ZUI using QPST. That's the last resort which saves your device from the gravest issues.
However, let me know if you can or can't find that thread or anything else, I'll be happy to help. :good:
KKaushal said:
If the first time boot with the rom and gapps was okay, maybe you should try wiping /system, /data, /dalvik and /cache and reflash the rom again.. Since you were in stock cmos 12.1, I think it'll be better if you flash official cm13 first, and then jump to cm14 from there to minimize sensor issues such as with the fingerprint like you experienced.
Click to expand...
Click to collapse
thank you, but I did wiping and reflash => causing the loop
best regards
m
sahu.prashant said:
Mate if you think you're done with everything and nothing seems to help, just search around here how to flash ZUI using QPST. That's the last resort which saves your device from the gravest issues.
However, let me know if you can or can't find that thread or anything else, I'll be happy to help. :good:
Click to expand...
Click to collapse
many thanks for offering. Any chance to provide a link, in order to spare some time?
best regards
m
meikelrix said:
I did wiping and reflash => causing the loop
Click to expand...
Click to collapse
There are many reasons for a bootloop. Start from scratch once again. Flash stock cos12.1 (or restore if you have a backup), flash cm13 from there after you load twrp, go from cm13 to cm14. I think this should be the way to go to avoid sensor issues. Once in stock, you can go from there. Good luck.
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
This is the thread link right here explaining all the steps (although it's a little tricky to follow )
That was the good part....
The worst part is that the download links are dead
I'll try snooping around more and see if I can find anything else and you should try too since the thread will give you an idea what to look for.
If the search comes up empty, I'll upload the files tomorrow by all means
Fortunately found a link....
http://forum.xda-developers.com/showpost.php?p=64202059&postcount=14
sahu.prashant said:
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
This is the thread link right here explaining all the steps (although it's a little tricky to follow )
That was the good part....
The worst part is that the download links are dead
I'll try snooping around more and see if I can find anything else and you should try too since the thread will give you an idea what to look for.
If the search comes up empty, I'll upload the files tomorrow by all means
Fortunately found a link....
https://www.androidfilehost.com/?w=files&flid=40618
Click to expand...
Click to collapse
Heya
many thanks again for your much appreciated help!
I'll try to figure and provide the outcome...
best regards
m
KKaushal said:
There are many reasons for a bootloop. Start from scratch once again. Flash stock cos12.1 (or restore if you have a backup), flash cm13 from there after you load twrp, go from cm13 to cm14. I think this should be the way to go to avoid sensor issues. Once in stock, you can go from there. Good luck.
Click to expand...
Click to collapse
thank you, but I can't start from scratch, since the loop won't let me in
Happy to help and hopefully, outcome will be desirable.
meikelrix said:
thank you, but I can't start from scratch, since the loop won't let me in
Click to expand...
Click to collapse
Power button + volume up gets you into recovery mode.
(I think) Power button + volume down gets you into fastboot mode. Not sure about this one, you can search around for the key combo to get into specific modes. From fastboot mode, you can flash the stock cos 12.1 provided from the official support page of cyanogen. Make sure you download the zip compatible with fastboot mode. When you finally get to cos 12.1, you can install Twrp recovery (also available among the forum threads or from the official twrp website), then flash cm13, reboot to check if everything works and then finally move to cm14.
You can post here in case of problems/confusions in any step.
Alternately, in place of cos12.1, you can flash zui as suggested. Search in the 'help, q/a' section of zuk z1 in this forum. You can find the tutorial there. Good luck.
KKaushal said:
Power button + volume up gets you into recovery mode.
(I think) Power button + volume down gets you into fastboot mode. Not sure about this one, you can search around for the key combo to get into specific modes. From fastboot mode, you can flash the stock cos 12.1 provided from the official support page of cyanogen. Make sure you download the zip compatible with fastboot mode. When you finally get to cos 12.1, you can install Twrp recovery (also available among the forum threads or from the official twrp website), then flash cm13, reboot to check if everything works and then finally move to cm14.
You can post here in case of problems/confusions in any step.
Alternately, in place of cos12.1, you can flash zui as suggested. Search in the 'help, q/a' section of zuk z1 in this forum. You can find the tutorial there. Good luck.
Click to expand...
Click to collapse
Hi,
after draining the battery (and loading up a bit) I could get access to fastboot. From there I flashed latest twrp (3.0.2) and booted into twrp.
From twrp I wiped and then flashed latest Nuclear ROM & Gapps. After rebooting I'm still ending up in twrp, again?
PS: flashing the cos 12.1 via fastboot mode didn't work, due to below:
"
fastboot -i 0x2b4c update cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
target reported max download size of 1610612736 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(14844,0xa3181000) malloc: *** mach_vm_map(size=1585467392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1583882000 bytes
error: update package missing system.img
"
many thanks again for any help/hints
best regards
m
meikelrix said:
Hi,
after draining the battery (and loading up a bit) I could get access to fastboot. From there I flashed latest twrp (3.0.2) and booted into twrp.
From twrp I wiped and then flashed latest Nuclear ROM & Gapps. After rebooting I'm still ending up in twrp, again?
PS: flashing the cos 12.1 via fastboot mode didn't work, due to below:
"
fastboot -i 0x2b4c update cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
target reported max download size of 1610612736 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(14844,0xa3181000) malloc: *** mach_vm_map(size=1585467392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1583882000 bytes
error: update package missing system.img
"
many thanks again for any help/hints
best regards
m
Click to expand...
Click to collapse
Extract cos zip files and flash separately
Enviado desde mi ZUK Z1 mediante Tapatalk
acuicultor said:
Extract cos zip files and flash separately
Enviado desde mi ZUK Z1 mediante Tapatalk
Click to expand...
Click to collapse
That was it. I did the following sequence:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
reboot device
fastboot -i 0x2b4c flash system system.img
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata.img
fastboot reboot
Then I was back to stock. After that I started from scratch to flash twrp, Nuclear and Gapps.
Many thanks to all that helped!
best regards
m
Kinda stuck on Sending system. Help?
Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056
moriyaprateek said:
Kinda stuck on Sending system. Help?
Click to expand...
Click to collapse
AFAIR, I followed https://stackoverflow.com/questions/34299245/fastboot-flash-system-img-error
=> "fastboot flash –S 256M system PATH_TO_SYSTEM.img" (the -S switch did the trick)
Even i am in the same situation how to fix it bro
meikelrix said:
Heya
many thanks again for your much appreciated help!
I'll try to figure and provide the outcome...
best regards
m
Click to expand...
Click to collapse
stuck with same situation plz need help
Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.
algnerd said:
Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.
Click to expand...
Click to collapse
Boot.img , recovery.img , cust.img , system.img.
Claleale said:
Boot.img , recovery.img , cust.img , system.img.
Click to expand...
Click to collapse
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?
algnerd said:
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?
Click to expand...
Click to collapse
Yes
Claleale said:
Yes
Click to expand...
Click to collapse
Flashing cust and system returned failes
For cust: (failed remote: partition error)
For syst: (failed remote: sparse flash write failure)
Since I was running nougat before messing up the phone, it had to be System and Boot extracted from the nougat update
By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice... I would never flash that but okay, that's why we are here
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM / AICP?
Schlengge said:
By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice...
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM?
Click to expand...
Click to collapse
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )
algnerd said:
...
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
You have to use the report button on your own OP. In the report text box, just ask mods to close your thread. The mod who is assigned to this forum will handle your request.
algnerd said:
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers
thomasedwardbullen1986 said:
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers
Click to expand...
Click to collapse
May god have mercy on your soul.
For the downgrade, I didn't use the b161 directly. I flashed some oeminfo provided in the same folder as the TWRP. Then used b150 ans the three boutons method. Worked like a charm.
Hope it will help you downgrade your phone.
I have the same problem, someone could explain it to me step by step, please
ask help
Hello
My name is EL HADJI MODOU SOW.I request your help concerning a big problem that I meet with my phone huawei P9 lite vns-l31c113b364 (these is the serial number 4TE0216B08004097) .in fact I wanted to activate the second sim then j I made a mistake handling the shot the system is corrupt and now I can not use my phone. I tried to flash it but I can not find a good frimeware. All the flash files that I find are working except the cust.img , vendor.img and product.img. what happens when I flash the cust.img (H: \ SRKToolHuawei-Lod-Chong-V2.0-20161002> fastboot flash cust CUST.img
target reported download size of 471859200 bytes
sending 'cust' (435462 KB) ...
OKAY [10.711s]
writing 'cust' ...
FAILED (remote: partition error)
finished. total time: 10.729s).
please help me I'm really teriified
this is my email:[email protected]
Hi so I been seeing many people getting stuck on fastboot after flashing ROM so here is the method u can use if u can't boot to TWRP also.
I have tired on PA ROM and it works so idk about others ROMs ..
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix).. Russian one
And after those comands do run TWRP auto installer.
U can find those files from fastboot stock ROM. This will save ur data and u won't needed to flash Stock ROM ..
Hope I explained everything if anything else needed comment down below.
Hi, i'm stuck in this fastboot limbo but can't find some of these files you mentioned: logo.img and misc.img
Where do i get them?
edit: nevermind, solved flashing fastboot miui with miflash pro.
EDIT 2: after flashing a rom i get stuck in fastboot everytime. How to avoid this?
Also tried flashing those files in that exact sequence but still stuck in fastboot.
My persist.img is shown not writable in cmd if I try to flash it. If I flash a rom using TWRP an error pops up saying "failed to mount /persist' (Invalid Argument).
SOLVED- Flashing persist.img from twrp "Install Image" works.
farhan20 said:
Hi so I been seeing many people getting stuck on fastboot after flashing ROM so here is the method u can use if u can't boot to TWRP also.
I have tired on PA ROM and it works so idk about others ROMs ..
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix).. Russian one
And after those comands do run TWRP auto installer.
U can find those files from fastboot stock ROM. This will save ur data and u won't needed to flash Stock ROM ..
Hope I explained everything if anything else needed comment down below.
Click to expand...
Click to collapse
Could you (or anyone) please provide these files.
Reep1324 said:
Could you (or anyone) please provide these files.
Click to expand...
Click to collapse
Hi, this u can get from fastboot stock Rom, download fastboot stock Rom and extract them u will find.. if need help just tag me ..
farhan20 said:
Hi, this u can get from fastboot stock Rom, download fastboot stock Rom and extract them u will find.. if need help just tag me ..
Click to expand...
Click to collapse
i got the .img file but i cant install it via twrp or fastboot cause this partition is unmountable
do you have any idea? i flashed stock rom via fastboot but the error insists
Dr.Dinel said:
i got the .img file but i cant install it via twrp or fastboot cause this partition is unmountable
do you have any idea? i flashed stock rom via fastboot but the error insists
Click to expand...
Click to collapse
Hello, seems u need to repair ur partition from TWRP.
Also what u did that cause this ?
PS: I'm not expert or anything but I will try to help if I could.
farhan20 said:
Hello, seems u need to repair ur partition from TWRP.
Also what u did that cause this ?
PS: I'm not expert or anything but I will try to help if I could.
Click to expand...
Click to collapse
thanks for replying
i finally solved it, used a chinese twrp that has the option to install on persist partition and the rest was easy
My k20 bricked after install miui 11 Chine version i try to flashing with flash tool but after processing not working "error antirolback check error" please someone help me
hamidezat20 said:
My k20 bricked after install miui 11 Chine version i try to flashing with flash tool but after processing not working "error antirolback check error" please someone help me
Click to expand...
Click to collapse
Hi, please follow this setups and it should be fine .
If you run into errors flashing fastboot images to your device, edit the .bat files that came with it. Usually you want to edit "flash_all.bat"
For "Missmatching image and device":
Remove the lines highlighted in the screenshot from the file, save and try flashing it again.
For Antirollback Error:
Remove ALL lines ABOVE the highlighted lines in the screenshot from the file, save and try flashing it again.
Always make sure that you got the right image for your device. Removing check lines from these files can permanently brick your device if you use the wrong fastboot image.
farhan20 said:
Hi, please follow this setups and it should be fine .
If you run into errors flashing fastboot images to your device, edit the .bat files that came with it. Usually you want to edit "flash_all.bat"
For "Missmatching image and device":
Remove the lines highlighted in the screenshot from the file, save and try flashing it again.
For Antirollback Error:
Remove ALL lines ABOVE the highlighted lines in the screenshot from the file, save and try flashing it again.
Always make sure that you got the right image for your device. Removing check lines from these files can permanently brick your device if you use the wrong fastboot image.
Click to expand...
Click to collapse
like me please help me after installing miui 11 Chine version
hamidezat20 said:
like me please help me after installing miui 11 Chine version
Click to expand...
Click to collapse
U r stuck on fastboot right and u said u can't flash fastboot rom because u r getting anti roll back error so I gave u solution
How to fix this problem
Hello same me how to fixed step by step
First you need fastboot rom extract fastboot rom on your pc after extract find 3 file
1-boot
2-recovery
3-system
Flash with fastboot
Turn off your phone and going to fastboot
Type
Fastboot devices
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Done device can't boot but you can install twrp China version link ?
https://www.lanzous.com/i6ahykh
after installation you can go to twrp
Download fastboot miui install from twrp
Sorry for me English
Oh my god, you saved me!
HI guys i flashed my mi 9t with twrp-3.3.1-2-davinci-fix it worked with miui.eu 9.8.15 after trying to flash miui 11 for about 6 hrs lol, anyway my phone is working but i would like to go back to stock and relock the bootloader but i cant find the mi 9t fastboot rom
timbook2 said:
HI guys i flashed my mi 9t with twrp-3.3.1-2-davinci-fix it worked with miui.eu 9.8.15 after trying to flash miui 11 for about 6 hrs lol, anyway my phone is working but i would like to go back to stock and relock the bootloader but i cant find the mi 9t fastboot rom
Click to expand...
Click to collapse
You're able to flash miui 11 after such long time or just 9.8.15?
farhan20 said:
Hi, please follow this setups and it should be fine .
If you run into errors flashing fastboot images to your device, edit the .bat files that came with it. Usually you want to edit "flash_all.bat"
For "Missmatching image and device":
Remove the lines highlighted in the screenshot from the file, save and try flashing it again.
For Antirollback Error:
Remove ALL lines ABOVE the highlighted lines in the screenshot from the file, save and try flashing it again.
Always make sure that you got the right image for your device. Removing check lines from these files can permanently brick your device if you use the wrong fastboot image.
Click to expand...
Click to collapse
hey i am getting file missmatching image and device error so i deleted those lines from .bat file but still getting the same error
lucifer said:
hey i am getting file missmatching image and device error so i deleted those lines from .bat file but still getting the same error
Click to expand...
Click to collapse
Hi, u deleted from flash all. Bat right and what's the error u r getting?
farhan20 said:
Hi, u deleted from flash all. Bat right and what's the error u r getting?
Click to expand...
Click to collapse
well it worked after i moved the file to c:/ drive but after flashing i lost widewine L1
When I got 9.8.15 working I stopped at least I got a working phone now, I will try and flash stock later.
I got anti rollback error trying to flash stock with miflash tool.