[Huawei P8 Lite 2017] Brick PRA-LX1 europe help me please - P8lite Q&A, Help & Troubleshooting

Hello everyone
I came to you because I root my p8 lite 2017, but impossible to put a code, deleted an app, etc .. so I looked for a solution to put my original phone back, and so I tried A back up by TRWP, then I tried to restore the original recovery to make a factory reset. I followed this tutorial
[How to unbrick]
The procedure of rescue is risky.
Without appropriate knowledge, I advise.
It is only successful if the instructions are executed exactly.
This TWRP backup rom is not suitable for normal use. It was created for the following purpose:
- Rescue of bricked phones.
- Force an OTA update.
Do not root this rom!
Unzip the download 2017-08-11-RESCUE.ROM.PRA.OTA.B164.to.170.rar (1.05 GB).
This creates the TWRP backup:
2017-08-11-RESCUE.ROM.PRA.OTA.B164.to.170
installation:
Copy my backup to the TWRP backup path to the Ext Sd.
Boot into the Bootloader.
Stock Recovery flash by adb.
In the recovery start
Perform a factory reset.
Boot into the Bootloader.
TWRP flash by adb.
To start TWRP.
There data wipe
And restore my backup.
In the Bootloader start and
Flash by adb the Stock Recovery.
There then again a factory reset.
reboot
When the boot process is finished,
Go to Settings> Update program> New version> Update.
Will not be offered, in the Stock Recovery again perform a factory reset.
The upgrade to the B170 succeeds only with sim-card.
You have a firmware update and a new firmware up-to-date.
Congratulation!
https://forum.xda-developers.com/p8...-to-root-huawei-p8-lite-2017-android-t3582179
Problem, now I am stuck on erecovery, or fastboot, but I do not know anything else, when I wanted to restore the original recovery, here is what it puts me:
Download free download size 471859200 bytes
Sending 'recovery' (35550 KB) ...
OKAY [0.961s]
Writing 'recovery' ...
FAILED (remote: Command not allowed)
finished. Total time: 0.968s
I do not know what to do .. When I try with update.app on the sd card, it puts me an error after 5%.
I have the impression that the bootloader is relock, how to recover the product id to get the unlock code?
Thank you very much to all those who will help me!
PS; Sorry for my bad english i use google translate
SEB

I can provide full service firmware for recovery. Indicate your region. PRA-L**C***B***

Hi @5261979, i would need 1 full firmware recovery for PRA-LX1C432B125 or PRA-LX1C432B175. It's possible? Thank you
P.S Alternatively you can have an OEMINFO file twrp backup for Single Sim to make an update for PRA-LX1C432B125 or PRA-LX1C432B175.
I have the two firmware complete (UPDATE.APP + HW_EU) But I can not flash them from the "dload" folder .............. Thank you

Related

P9 Lite cannot flash stock firmware

I have a Huawei P9 lite. (VNS-L31 dual sim) . I tried to install medrom 3 and after flashing, phone didn't boot up. So I flashed b161 firmware again using 3 button method and phone booted up. Then I realized I couldn't add my google account. After searching on xda I found a method to fix that.(flashing oem info ). But after doing that, when the phone boots up after the huawei logo the error message which says "your device has been unlocked" has become red.( Usually it's yellow). And in about phone my model number has been changed to something like hi6250 or hi650.( Can't remember the exact thing). Then I tried to reflash my b161 firmware using 3 button menu and voila. It says incompatible version. I can't flash it. Then I replaced my build prop with my friend's phone's build prop. But unfortunately it has the B151 version. Though I have B161 version installed, my about phone says it has B151 version. And I can't flash stock firmware using twrp or dload method od any how. Please help
Nemeroz said:
I have a Huawei P9 lite. (VNS-L31 dual sim) . I tried to install medrom 3 and after flashing, phone didn't boot up. So I flashed b161 firmware again using 3 button method and phone booted up. Then I realized I couldn't add my google account. After searching on xda I found a method to fix that.(flashing oem info ). But after doing that, when the phone boots up after the huawei logo the error message which says "your device has been unlocked" has become red.( Usually it's yellow). And in about phone my model number has been changed to something like hi6250 or hi650.( Can't remember the exact thing). Then I tried to reflash my b161 firmware using 3 button menu and voila. It says incompatible version. I can't flash it. Then I replaced my build prop with my friend's phone's build prop. But unfortunately it has the B151 version. Though I have B161 version installed, my about phone says it has B151 version. And I can't flash stock firmware using twrp or dload method od any how. Please help
Click to expand...
Click to collapse
That's normal if the message is red, it means that the bootloader Will be relocked.
Now for the build prop, download b161 version, use huawei firmware extractor , extract boot.img system.img and cust.img
And by fastboot type :
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot reboot
And voila, b161 is installed in your phone !
Sent from my HUAWEI VNS-L31 using XDA Labs
I can ont flash the boot.img. I get this error:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\161_entpackt>Fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13998 KB)...
OKAY [ 0.300s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.322s
Schrotty35 said:
I can ont flash the boot.img. I get this error:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\161_entpackt>Fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13998 KB)...
OKAY [ 0.300s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.322s
Click to expand...
Click to collapse
If fastboot say "FAILED (remote: Command not allowed)", its because your bootlaoder is locked, reunlock it !
In TWRP it says unable to mount Data :/
Ax3noX_ said:
If fastboot say "FAILED (remote: Command not allowed)", its because your bootlaoder is locked, reunlock it !
Click to expand...
Click to collapse
I noticed that in TWRP it says unable to mount data :/ What can i do now
I don't know what is "mount data", i cant help you with that ?
Ax3noX_ said:
I don't know what is "mount data", i cant help you with that
Click to expand...
Click to collapse
Its okay. Still looking for a help dude. Any help is highly appreciated :good:
Nemeroz said:
Its okay. Still looking for a help dude. Any help is highly appreciated :good:
Click to expand...
Click to collapse
Code:
fastboot oem unlock XXXXXX
fastboot flash recovery recovery_stock.img
Unable to read/mount data says your encryption key got changed by something, whatever. You need to Wipe Internal storage and flash twrp again ( I recomment matic`s ) Reboot to recovery again, if you got one, flash a flashable fw via twrp. I Dont know if the stock recovery Accepts a fully wiped intern storage, i guess not and it declines the update.app method.
In the best case for sure you recover an older backup to get the Same enc. Key back
WieserZ1C said:
Unable to read/mount data says your encryption key got changed by something, whatever. You need to Wipe Internal storage and flash twrp again ( I recomment matic`s ) Reboot to recovery again, if you got one, flash a flashable fw via twrp. I Dont know if the stock recovery Accepts a fully wiped intern storage, i guess not and it declines the update.app method.
In the best case for sure you recover an older backup to get the Same enc. Key back
Click to expand...
Click to collapse
Try to hold Vol+ and the power button and if you enter in Huawei recovery, select wipe data / Factory reset
Ax3noX_ said:
Try to hold Vol+ and the power button and if you enter in Huawei recovery, select wipe data / Factory reset
Click to expand...
Click to collapse
Tried that. But didnt work mate 😔
Nemeroz said:
Tried that. But didnt work mate 😔
Click to expand...
Click to collapse
Flash oeminfo (dowbload in the ultimate guide of nougat) and put the update.app of the marshmallow version in the dload folder then hold Vol+, vol- and power.
Its worked for me
Tell me if it work
(Sorry for my bad english, im french
I'd recommend using SP Flash tool. It's saved my ass multiple times.
Where you got the Scatter File for the p9 lite
Nantonix said:
I'd recommend using SP Flash tool. It's saved my ass multiple times.
Click to expand...
Click to collapse
Spflash tool is flash tool only for mtk devices... And p9 lite doesnt have a mtk soc !
---------- Post added at 08:47 PM ---------- Previous post was at 08:46 PM ----------
hanzox5 said:
Where you got the Scatter File for the p9 lite
Click to expand...
Click to collapse
It doesn't exist !
i wanted to convert the device to dual sim, so i tried to restore the backed-up partitions using meticulus' TWRP. But it says unable to mount /data every time i try to format it.
I know i made a big mistake, but that's how i learn..
this thread has worked for me
https://translate.google.co.uk/tran...m/showthread.php?t=1261335&edit-text=&act=url
Hello I went back the MN when startups is only then the logo after screen dark
please help me !!!
sorry for my english
pinhpongk said:
Hello I went back the MN when startups is only then the logo after screen dark
please help me !!!
sorry for my english
Click to expand...
Click to collapse
do a factory reset..if doesn work reflash stock marshmallow b160

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]

Screwed up phone while rolling back Android 7 - help?

So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.

VNS-L21 TIFU - wrote wrong cust.bin and oeminfo - what to do?

So... I tried to get the P9 lite to custom Nougat ROM.
Unlocked bootloader using SRKtool (found here ) and flashed TWRP using the same tool.
Installed SuperSU. Made TWRP backup of all partitions (including cust and oeminfo).
The post suggested that stock Nougat ROM should be installed first, and then the custom ROM. But my model was different than the generic EU, so I thought I should update it, right?
Without much thinking I used the SRKtool again to flash oeminfo/custom.bin, and didn't even make backup of the files
Now my phone thinks it is hi6250 VNS-C432B140.
After boot message "Your device has failed verification and may not work properly." was displayed and boot was interrupted with "Type your password to decrypt storage" prompt. After formatting data partition system boots.
I can't boot into TWRP recovery.
I can't flash any partition with fastboot (Error: FAILED (remote: Command not allowed)).
Any ideas how to get oeminfo back to VNS-L21 and/or restore TWRP backups?

Phone stucks in fastboot

Hi guys,
i was on Miui Global 10.xxxx (dont know exactly)
bootloader was unlocked.
Rollback protection target was 1
my recovery was Orangefox recovery (https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899)
I have made a full backup of all partitions before.
I wanted to flash Miui 11.0.4.0 global to flash a custom rom.
First i flashed recovery and installed the recovery.zip.
That worked fine.
Then i wanted to flash Miui 11.0.4.0 with this instructions for a clean flash:
1. If you're coming from another ROM or need to perform a clean flash:
Boot into Recovery
Wipe Data/Cache/System
Flash vendor/firmware (Global 11.0.4.0 recommended)
Flash ROM
(Optional) Flash Gapps (not included!)
(Optional) Flash the latest Magisk
Reboot
Enjoy
This instructions are from here: https://forum.xda-developers.com/mi-9t/development/rom-stagos-t4072637
So, i was in recovery, and deleted data, cache and system.
Then i restarted the phone to go to recovery, but that didnt work.
It stucked in bootloop.
I now reinstalled Adb and fastboot, and erased recovery and System partition.
There were much errors in time due old adb and fastboot version etc....
But now iam at this point here again.
wait for your answers how to continue.....
It looks like just flashing or booting recovery is not possible without system partition.
It's now too late and sorry I don't want to risk to give you the wrong instructions how to unbrick
But for the others to avoid similar brick:
1) You say you were on Global MIUI 10 and you wanted to update to MIUI 11.
If so, why didn't you simply update by OTA?
2) If for some reason you were not able to apply OTA, but if you were really on Global (not on custom ROM, Indian ROM or so) and wanted to update also to Global (not switching to EU weekly or so), then you shouldn't wipe anything
You had to flash the stock Recovery back, to download the Global recovery/zip package you wanted to update to, and to force update from System Update: (so called Local Update):
https://c.mi.com/oc/miuidownload/detail?guide=1
Now, once you wiped things and bricked, I don't know but you could check the Fastboot method:
https://c.mi.com/oc/miuidownload/detail?guide=2
If reading from mobile phone, force Desktop site in browser for the two links anove
1. When you make format data, than reboot in twrp again
2.when boot second time, wipe data, dalvick, cache, system...and flash new rom.
If you wipe system partition and reboot in twrp again without system, you get fastboot.
zgfg said:
It's now too late and sorry I don't want to risk to give you the wrong instructions how to unbrick
But for the others to avoid similar brick:
1) You say you were on Global MIUI 10 and you wanted to update to MIUI 11.
If so, why didn't you simply update by OTA?
2) If for some reason you were not able to apply OTA, but if you were really on Global (not on custom ROM, Indian ROM or so) and wanted to update also to Global (not switching to EU weekly or so), then you shouldn't wipe anything
You had to flash the stock Recovery back, to download the Global recovery/zip package you wanted to update to, and to force update from System Update: (so called Local Update):
https://c.mi.com/oc/miuidownload/detail?guide=1
Now, once you wiped things and bricked, I don't know but you could check the Fastboot method:
https://c.mi.com/oc/miuidownload/detail?guide=2
If reading from mobile phone, force Desktop site in browser for the two links anove
Click to expand...
Click to collapse
Sooo....after hours of reading with errors over errors and fixing, it still doesnt work.
First i tried to flash everything via mi flashtool.
There was an error: Antirollbackcheck Error.
https://www.reddit.com/r/Xiaomi/comments/d0xmbp/what_on_earth_is_miflash_antirollback_check_error/
https://xiaomi.eu/community/threads...nd-flashing-recovery-fails-please-help.51349/
To fix this i had to move the Tool and the rom into my C hard drive next to program etc folders...
Then i editet the flashall.bat file and removed the rollbackcheck lines.
Now after doing this, it flashed for 100 seconds, and then there was this error: Failed to flash dtbo.img
sooo....Then i tried to flash the dtbo.img and all the other ones via Minimal adb and fastboot.
https://forum.xda-developers.com/mi-9t/help/flash-stuck-fastboot-soft-brick-t3962662/page3
And this didnt work for me too. Everytime if i try to flash dtbo.img, this error comes:
target didnt report max-download-size
sending dtbo (32768KB)....
FAILED (command write failed (no error))
finished.
Now everything is like before....
Flash twrp and boot in twrp. After phone boot in twrp, make format data. After format, make reboot to recovery.
When booot in twrp, wipe data, dalvick, cache, system , copy Miroom to internal and flash ROM.
Use this twrp...
https://app.box.com/s/8lkfbft44vldtt0y8kwhe6un87b5ebzx
And this rom.
https://sourceforge.net/projects/mi...edmiK20_MIUI_20.3.26_MiRoom_10.0.zip/download
Sent from my MI 9T using Tapatalk
Kidence said:
Flash twrp and boot in twrp. After phone boot in twrp, make format data. After format, make reboot to recovery.
When booot in twrp, wipe data, dalvick, cache, system , copy Miroom to internal and flash ROM.
Use this twrp...
https://app.box.com/s/8lkfbft44vldtt0y8kwhe6un87b5ebzx
And this rom.
https://sourceforge.net/projects/mi...edmiK20_MIUI_20.3.26_MiRoom_10.0.zip/download
Sent from my MI 9T using Tapatalk
Click to expand...
Click to collapse
C:\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-12-davinci-mauronofrio.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.914s]
writing 'recovery'...
OKAY [ 0.151s]
finished. total time: 2.065s
C:\Minimal ADB and Fastboot>fastboot boot recovery
error: cannot load 'recovery': No such file or directory
C:\Minimal ADB and Fastboot>fastboot boot twrp-3.3.1-12-davinci-mauronofrio.img
downloading 'boot.img'...
OKAY [ 1.891s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.900s
When you flash recovery, hold volume up and type in adb
fastboot reboot
After that, phone will be boot in twrp
Sent from my MI 9T using Tapatalk
FINALLY it worked YES
FIRST: The Story for everybody who has the same problem like me:
Device: Xiaomi Mi 9T
Firmware: MIUI 10 GLOBAL
Antirollbackprotectioncounter: 1
Bootloader: Unlocked
Story:
At the beginning, everything was working, but i wanted to install a custom rom (STAGOS)
For this step, i had to Update my Miui firmware on 11.0.4.0.
But this step didnt work so well via device OTA (error), then i decided to install it via custom recovery.
I still had the stock recovery on my device, so i went in fastboot mode, and installed Orangefox recovery via ADB and Fastboot on Windows. That worked without problems.
In Orangefox, i wiped as sayed in instructions data, cache and System. then i rebooted.
But before realised that was the wrong way, i stucked in fastboot.
No tools helped. ADB and Fastboot didnt work as seen in screenshots.
I tried everything via fastboot....
fastboot flash recovery XXX.img
fastboot boot XXXX.img
Fastboot format.....etc
But NOTHING worked. Everytime there were the following errors:
Target didnt report Max download size
Error: Cannot load recovery
No such file or directory
Error: Download size is higher that allowed
Failed to load boot image (Load error)
Command write failed (no error)
and some other ones too.....
It looked like, some flashes worked and some not. Sometimes it worked, sometimes not.
After some new tries it just showed via the command: Fastboot devices
????????? fastboot
That problem has been solved. Just unplug the device and wait for 10 minutes until it shuts down automatically.
If that doesnt work, you can try to replug it to pc some times again.
It looked like replugging and using different USB Port (one user solved the problem via USB 2.0) helps to get a better connection and prevent errors.
Then i tried some tools, for example android all in one tool, but no one worked.
After this, i reinstalled the driver and installed MI Flash tool (https://mi-globe.com/download-xiaomi-mi-flash-tool-all-versions/)
It looks like there are some mi flash tools around here which are not working right, but THIS one worked for me.
After installing, i connected my device, choosed the fastboot firmware (.tgz), unpacked it and choosed the right location in mi Flash tool.
Firmware files are find here: https://c.mi.com/oc/miuidownload/detail?guide=2
(You should check you Antirollback counter before to avoid a brick. Here you find some informations: https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/)
DONT FORGET TO CHOOSE IN THE RIGHT DOWN CORNER: CLEAN ALL !!! (normally, clean all and lock is choosen, but that bricks your device)
After doing this, i started flashing, but there was an error: Antirollbackcheck error.
I solved it via moving the mi flashtool directly into my C hard drive, and deleted some lines in the flashall.bat, as seen in post history here.
Then....it worked for some seconds longer, but than: Error: Failed to flash dtbo.img
So i tried it via ADB and Fastboot. But nothing changed.
Then i tried flashing via mi Flash tool again, and this time the following error comes: Failed to flash system.img.
After this is thought: hmmm....something is very wrong with this device....lets try again, after a device restart.
So i tried again, let it running for ~360 seconds, and IT WORKED!
At the End: there was the following error: Error: Not catch checkpoint.
But this error (you can also see in a screenshot) it not necessary.
This is the result of removing some lines in flashall.bat.
After this my phone successfully booted im Miui 11.

Categories

Resources