Database Users

Meizu PRO 5 bootloop no recovery locked bootloader

Hi all,
I am in trouble with the PRO 5.
Actual situation:
No recovery mode available
The phone boots but when is time to go in the home screen, the screen becomes black and only the power button response so I only turn it off or restart.
Fastboot mode available but the bootloader is locked
I tried many time with the Multiupgrade tool and TestPCTool but the answer is "Token sign failed"
Could someone help me before to put the phone in the trash

Upppppp!!!!!

You could try to unlock it using "fastboot oem unlock", but if it works it probably wipes the userdata partition, and it may fail. If you manage to unlock it, just reflash the stock image, but without the bootloader.
If this doesn't work, there is a similar thread in a different forum which may help you:
https://forum.meizufans.eu/topic/5376/meizu-pro-5-have-rooted-rom-but-lost-recovery-phone-can-boot-pls-help

Daniel Abrecht said:
You could try to unlock it using "fastboot oem unlock", but if it works it probably wipes the userdata partition, and it may fail. If you manage to unlock it, just reflash the stock image, but without the bootloader.
If this doesn't work, there is a similar thread in a different forum which may help you:
https://forum.meizufans.eu/topic/53...rom-but-lost-recovery-phone-can-boot-pls-help
Click to expand...
Click to collapse
I know the italian guy of this 3D and I can tell u, "fastboot oem unlock" doesn't work unfortunately :crying:

Thanks Pycon.
He is right, no way to unlock the bootloader, at the moment

just try this. good luck man. http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678

tzzzz said:
just try this. good luck man. http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678
Click to expand...
Click to collapse
Thanks but tried many times: Token signature fail...

Have you tried flashing the whole system (20150923195421_demo_prd_stable) as described in the M86 firmware upgrade tutorial.pdf ?

st0rm77 said:
Have you tried flashing the whole system (20150923195421_demo_prd_stable) as described in the M86 firmware upgrade tutorial.pdf ?
Click to expand...
Click to collapse
Where is that tutorial?

DarginMahkum said:
Where is that tutorial?
Click to expand...
Click to collapse
It resides in the Meizu Tools post, but never mind that. I dove into the security and fastboot uses secure boot so unless there is an exploit your stuck.
Are you able to flash the boot partition ?
If so, you might be able to flash the recovery.img onto the boot (bootimg) partition. Then drop an update.zip into the root of userdata and reboot.
Good luck.

Hey Grumpy,
I extracted the kernel and ramdisk from the recovery image (flyme_5.6.1.19_daily). Unpack these files into a directory, then run
# fastboot boot kernel ramdisk
If it boots you can:
- erase to factory default
- maybe ?? flash /sdcard/update.zip ??
Good luck :good:

st0rm77 said:
Hey Grumpy,
I extracted the kernel and ramdisk from the recovery image (flyme_5.6.1.19_daily). Unpack these files into a directory, then run
# fastboot boot kernel ramdisk
If it boots you can:
- erase to factory default
- maybe ?? flash /sdcard/update.zip ??
Good luck :good:
Click to expand...
Click to collapse
Nope...
creating boot image...
creating boot image - 15699968 bytes
downloading 'boot.img'...
FAILED (remote: permission denied!)
finished. total time: 0.000s

how to recover?

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]

can only get into fastboot or TWRP

I am trying to flash Lineage OS, and from TWRP it appears to flash but now this Storm Kipper will not boot into Lineage.
From TWRP if I select power off it goes straight into Fastboot.
From Fastboot:-
Start: reboots and goes straight into fastboot
Restart bootloader: reboots and goes straight into fastboot
Power off: reboots and goes straight into fastboot
Recovery mode: goes to Team Win Recovery Project 3.1.0-0
I have a number of lineage-14.1-2017xxyy-nightly-kipper-signed.zip on a microSD card, and I have checked the SHA256 hashes and they match the ones on the website
Another oddity is that if I try and flash open_gapps it says wrong architecture, I have tried arm and arm64 and it makes no difference.
I have tried using the repair feature on System, Data and Cache and it seems to complete without issues but lineage still won't boot.
Can anyone advise? thanks

also I just tried the ADB sideload feature in TWRP (just to rule out the microSD card)
it appeared to work with a progress bar and at the end said "script succeeded", but when you select reboot it says "No OS installed! Are you sure you wish to reboot?"

ok people.
If I extract the boot.img from the LineageOS zip file and flash that using fastboot is that likely to make things better or worse?

Did you have success? I have the same problem...

Possible solution found!
dieselnutjob said:
ok people.
If I extract the boot.img from the LineageOS zip file and flash that using fastboot is that likely to make things better or worse?
Click to expand...
Click to collapse
I got my wf storm up and running again!
Look here -> reddit-forum for LineageOS

android_paul said:
I got my wf storm up and running again!
Look here -> reddit-forum for LineageOS
Click to expand...
Click to collapse
Thank you for this. I now also have Lineage 14.1 working.
The back button still doesn't illuminate though. I'm not sure if it's a bug or a hardware fault.
Anyway, as per the reddit post.
Download cm-13.1.5-ZNH2KAS7EC-kipper (fastboot).zip
unpack the zip file into a new folder
follow these instructions (I am using Linux)
Code:
cd ~/cm-13.1.5-ZNH2KAS7EC-kipper-fastboot/
fastboot flash aboot emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
This got it back to a working CM13.1
From here I went to bootloader mode and had a play with CM Recovery but didn't get on with it.
So I flashed on TWRP+3.1.0-0.img again.
This time it wouldn't pick up the microSD card, but adb sideload worked and that is how I installed lineage, su and gapps.
Thanks again.

Now that Lineage 14.1 is on TWRP can now see the microSD card.

dieselnutjob said:
...
The back button still doesn't illuminate though. I'm not sure if it's a bug or a hardware fault.
Click to expand...
Click to collapse
My led of the back button is off too. I'm afraid, it's a hardware issue. If my phone gets cold (using as a navigation tool on bike in winter....), the led begins to shine - until it's warm again. So this looks like an electrical (dis)connection problem.
There are bigger problems to imagine.

Can't flash twrp to Wileyfox Storm!
I can't install twrp of my Wileyfox Storm (I've tried several times)!
* I've unlocked the bootloader.
* I change to the directory where the twrp image is stored.
* I do <adb reboot bootloader>
* I do <fastboot flash recovery ./twrp-3.2.1-0-kipper-20180110.img>
I then get the message:
target reported max download size of 268435456 bytes
sending 'recovery' (26676 KB)...
OKAY [ 0.923s]
writing 'recovery'...
OKAY [ 0.339s]
finished. total time: 1.262s
* I then do <fastboot reboot>
The phone then reboots OK, but if I try to reboot to recovery I just get the 'vanilla' boot menu.
I'd be grateful for any help, please.
Jim

How can oem unlock leEco le pro 3 x722

Hi guys
I destroyed my leEco le pro 3 x722
After passing the custom rom
Now the device is locked on fastboot only
There is no system and no recovery
The problem I have now is the decryption. If the oem unlock is I can update it. Please help oem unlock
The device does not respond to commands
Everything is written
PS C: \ adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (39337 KB) ...
OKAY [0.895s]
writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.940s
How can oem unlock in another way ????

What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.

sk8223 said:
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
Click to expand...
Click to collapse
You installed Batyan's 20s developer ROM
In the past I opened the boot loader but when I tried Rum Miwi did not work
I wanted to go back to the official 26s Rom
Unfortunately everything has lost and the device is ruined
I did not see the warning of testing
How is the solution now

The official 26s ROM locks the bootloader down. If you try to flash anything through it, you'll end up with a bricked device. I'm sorry.
Did you say that you tried to install MIUI? I don't know what "Miwi" is. All I know is, that's something you shouldn't have done.
I'm not sure if you successfully flashed the official 26s ROM or not, and then tried to flash something else... that would cause a brick for sure, AFAIK.
Again, post to the thread about bricked phones that I linked. There are quite a few people with bricks here. Hopefully a solution will present itself soon. Until then, hold onto your phone and hope. :/

sk8223 said:
The official 26s ROM locks the bootloader down. If you try to flash anything through it, you'll end up with a bricked device. I'm sorry.
Did you say that you tried to install MIUI? I don't know what "Miwi" is. All I know is, that's something you shouldn't have done.
I'm not sure if you successfully flashed the official 26s ROM or not, and then tried to flash something else... that would cause a brick for sure, AFAIK.
Again, post to the thread about bricked phones that I linked. There are quite a few people with bricks here. Hopefully a solution will present itself soon. Until then, hold onto your phone and hope. :/
Click to expand...
Click to collapse
Yes, unfortunately, the device is locked
Updated 26s
The manufacturer must find us a solution
Thank you for the kind word

sk8223 said:
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
Click to expand...
Click to collapse
So your fastboot works just flash the boot loader .
Nice. I finally able to unlock and root. Although I just wished, the first page gets updated with the current method. I have to go through all the pages to fully understand what to do.
So basically a quick roundup:
go in fastboot
flash emmc_appsboot.mbn inside the zip.
reboot
it will ask for a password, just ignore it and reboot back to fastboot
unlock the bootloader
flash twrp
boot into twrp
format phone
then you're done!
Sent from my LEX727 using xda premium

mchlbenner said:
So your fastboot works just flash the boot loader .
Nice. I finally able to unlock and root. Although I just wished, the first page gets updated with the current method. I have to go through all the pages to fully understand what to do.
So basically a quick roundup:
go in fastboot
flash emmc_appsboot.mbn inside the zip.
reboot
it will ask for a password, just ignore it and reboot back to fastboot
unlock the bootloader
flash twrp
boot into twrp
format phone
then you're done!
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Unfortunately I do not know how to scroll
Our Lord is wrong
PS C:\adb> fastboot devices
7b61ab59 fastboot
PS C:\adb> fastboot flash emmc_appsboot.mbn
unknown partition 'emmc_appsboot.mbn'
error: cannot determine image filename for 'emmc_appsboot.mbn'
PS C:\adb> fastboot flash emmc_appsboot.zip
unknown partition 'emmc_appsboot.zip'
error: cannot determine image filename for 'emmc_appsboot.zip'

That file has to be in adb main file.
Sent from my LEX727 using xda premium

mchlbenner said:
That file has to be in adb main file.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
If you have a file please give me the link
Or where I find it

I think you talk about different terminals.
The X722 with 26S strock brick CAN NOT FLASH FOR FASTBOOT.
Greetings.

fastboot flash emmc_appsboot.mbn <- that command is not correct, that's why it errors saying partition not found. The partition to flash is missing, not sure what partition is supposed to be specified, but the command should look like this...... fastboot flash 'thecorrectpartition' emmc_appsboot.mbn

meangreenie said:
fastboot flash emmc_appsboot.mbn <- that command is not correct, that's why it errors saying partition not found. The partition to flash is missing, not sure what partition is supposed to be specified, but the command should look like this...... fastboot flash 'thecorrectpartition' emmc_appsboot.mbn
Click to expand...
Click to collapse
Explain more please
What should i do
Put the file in disk c
Show me this message
PS C:\adb> fastboot flash thecorrectpartition emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'thecorrectpartition' (791 KB)...
OKAY [ 0.034s]
writing 'thecorrectpartition'...

toufik_d said:
Explain more please
What should i do
Put the file in disk c
Show me this message
PS C:\adb> fastboot flash thecorrectpartition emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'thecorrectpartition' (791 KB)...
OKAY [ 0.034s]
writing 'thecorrectpartition'...
Click to expand...
Click to collapse
Your terminal is blocked. It does not have a solution.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
What they say is for x720 and x727 NOT FOR X722.
The command they say is:
fastboot flash aboot emmc_appsboot.mbn
but as I say, it's NOT GOING TO WORK.
Greetings.

how you wiped everything?
do you have recovery?

F.J.V said:
Your terminal is blocked. It does not have a solution.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
What they say is for x720 and x727 NOT FOR X722.
The command they say is:
fastboot flash aboot emmc_appsboot.mbn
but as I say, it's NOT GOING TO WORK.
Greetings.
Click to expand...
Click to collapse
That command work for me.
Lex 727 21s.
Sent from my LEX727 using xda premium

mchlbenner said:
That command work for me.
Lex 727 21s.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Of course.
That's what I say, for X720 and X727.
For X722 DOES NOT WORK
Greetings.

danielpinto8zz6 said:
how you wiped everything?
do you have recovery?
Click to expand...
Click to collapse
I wanted to restore the official order
The device is running on fastboot only

Flash this If you stuck on fastboot or soft brick

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.