[SOLVED] Mi flash error (Length cannot be less than zero) - Xiaomi Mi A2 Lite Questions & Answers

Hi everyone;
I'm on MIUI11 hybridOS now, and want to get back to the stock rom.
My bootloader is unlocked (by "fastboot oem unlock" command), the drivers are installed on my PC, I'm using mi flash tool 20191206 (i think it's the latest version), i copied mi flash on drive C, and there is no space in the directory of the rom, and i run mi flash as administrator;
but when i connect my phone (in the bootloader mode) to the computer, mi flash doesn't detect it and shows the error "Length cannot be less than zero. Parameter name: length"
Even i tried EDL mode, when in fastboot mode typed "fastboot oem edl", but after that the phone turns off and led light blinks and nothing happens and PC doesn't detect the phone, then i have to restart it by holding the power button.
Could anyone help me?
Thank you

pourya_fa said:
Hi everyone;
I'm on MIUI11 hybridOS now, and want to get back to the stock rom.
My bootloader is unlocked (by "fastboot oem unlock" command), the drivers are installed on my PC, I'm using mi flash tool 20191206 (i think it's the latest version), i copied mi flash on drive C, and there is no space in the directory of the rom, and i run mi flash as administrator;
but when i connect my phone (in the bootloader mode) to the computer, mi flash doesn't detect it and shows the error "Length cannot be less than zero. Parameter name: length"
Even i tried EDL mode, when in fastboot mode typed "fastboot oem edl", but after that the phone turns off and led light blinks and nothing happens and PC doesn't detect the phone, then i have to restart it by holding the power button.
Could anyone help me?
Thank you
Click to expand...
Click to collapse
Pleaaaase! Anybody can help me??

You need to be in fastboot mode for miflash. Xiaomi geek has instructions.

bonzoe said:
You need to be in fastboot mode for miflash. Xiaomi geek has instructions.
Click to expand...
Click to collapse
I am in fastboot mode, however it doesn't detect my phone

The alternative way! (My solution )
Finally I found a way to flash my phone without Mi flash tool!
It's so simple,
You boot into fastboot mode and connect the phone to your PC, in the ROM folder (after extracting) there are some files in .bat format (flash_all.bat , flash_all_lock.bat , etc), you just need to double click the appropriate file to run and flash your phone! No need to Mi flash tool!

The Mi flash tool provides the drivers and then basically does what you have done (as I read Xaiomi geek)

bonzoe said:
The Mi flash tool provides the drivers and then basically does what you have done (as I read Xaiomi geek)
Click to expand...
Click to collapse
Yea you're right, but despite i installed the drivers it gave me the error, so i installed the rom manually!

For fastboot oem edl , you need to have installed Qualcomm drivers, and if u are in miui is more safe edl mode, that is why mi flash don't flash the rom.

Os_Herdz said:
For fastboot oem edl , you need to have installed Qualcomm drivers, and if u are in miui is more safe edl mode, that is why mi flash don't flash the rom.
Click to expand...
Click to collapse
Thank you so much
I'll try it next time

pourya_fa said:
The alternative way! (My solution )
Finally I found a way to flash my phone without Mi flash tool!
It's so simple,
You boot into fastboot mode and connect the phone to your PC, in the ROM folder (after extracting) there are some files in .bat format (flash_all.bat , flash_all_lock.bat , etc), you just need to double click the appropriate file to run and flash your phone! No need to Mi flash toSounds
Click to expand...
Click to collapse
pourya_fa said:
Hi everyone;
I'm on MIUI11 hybridOS now, and want to get back to the stock rom.
My bootloader is unlocked (by "fastboot oem unlock" command), the drivers are installed on my PC, I'm using mi flash tool 20191206 (i think it's the latest version), i copied mi flash on drive C, and there is no space in the directory of the rom, and i run mi flash as administrator;
but when i connect my phone (in the bootloader mode) to the computer, mi flash doesn't detect it and shows the error "Length cannot be less than zero. Parameter name: length"
Even i tried EDL mode, when in fastboot mode typed "fastboot oem edl", but after that the phone turns off and led light blinks and nothing happens and PC doesn't detect the phone, then i have to restart it by holding the power button.
Could anyone help me?
Thank you
Click to expand...
Click to collapse
The same problem!!!

Os_Herdz said:
For fastboot oem edl , you need to have installed Qualcomm drivers, and if u are in miui is more safe edl mode, that is why mi flash don't flash the rom.
Click to expand...
Click to collapse
But how to solve it? I think I have installed drivers both by pressing Drivers button in Mi Flash and separately.

pourya_fa said:
The alternative way! (My solution )
Finally I found a way to flash my phone without Mi flash tool!
It's so simple,
You boot into fastboot mode and connect the phone to your PC, in the ROM folder (after extracting) there are some files in .bat format (flash_all.bat , flash_all_lock.bat , etc), you just need to double click the appropriate file to run and flash your phone! No need to Mi flash tool!
Click to expand...
Click to collapse
I want to try this and manually have found both the .bat files for Windows and .sh files of the same name for Android, but I need to know, from which location of them did you flash the phone: I have downloaded stock ROMs both on my phone SD card and on my PC, both in zip and unzipped. Even with developer mode unlocked, the update function from Settings sees only zipped versions on SD, but only tries to get file info and stops. Tapping on either bat or sh files in the phone's File Explorer opens them for reading as text files instead of executing either. In fastboot mode, the phone attached over usb to my laptop is reflected in Device Manager of Windows as Android Adb Device, if I remember correctly, but no files on it are visible in computer's File Explorer or Total Commander or MiFlash or MiPCsuite, the latter in usual work mode of the smartphone shows its internal memory folders all right, but not the SD as such in its File Explorer, though it opens the phone's media, set to be stored on the SD. The original problem is that despite storage of media and downloads on the external SD card and use of CleanMaster frequently, even after deinstallation of all external apps my Redmi says it has only up to 23 mb of disk space. I was recommended resetting to factory settings, but this function says if fails to switch off device search even after I log out of my Mi account and switch off Google device search as an administrator in Privacy settings. I then tried Recovery button in MiPCsuite,, but it did not work, requiring to back up the device on the PC , but saying backup is impossible when I press its Backup button, and Update\Flash buttons on the suite don't give any results either, as update says there are no updates, which is false. Redmi 3, if it is necessary to know, xiaomi.eu , never changed. So my question is, where from did you flash your phone? Where were the ROM\bat files? On th phone or computer?

pourya_fa said:
The alternative way! (My solution )
Finally I found a way to flash my phone without Mi flash tool!
It's so simple,
You boot into fastboot mode and connect the phone to your PC, in the ROM folder (after extracting) there are some files in .bat format (flash_all.bat , flash_all_lock.bat , etc), you just need to double click the appropriate file to run and flash your phone! No need to Mi flash tool!
Click to expand...
Click to collapse
Please, please, I want a video, because of the shoes, the same problem mentioned above and it has not been solved so far

Related

Phone bricked, only acces in fastboot mode

Hi,
My phone is bricked, cause i used twrp temporaly, to install a new rom, but after an unexpected wipe my phone lost OS files so i'm just able to use adb & fastboot with the fastboot mode, so lock & unlock oem principaly. Please help me it's very very important cause i need to use this phone ...
Thanks.
Is your bootloader (still) unlocked and do you have access to fastboot?
Veran125 said:
Is your bootloader (still) unlocked and do you have access to fastboot?
Click to expand...
Click to collapse
Yes, bootloader's still unlocked and i have acces to fastboot.
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse
Thanks for your magic answer, but i can't find your toolkit, BUT i found this https://forum.xda-developers.com/mi...ol-tool-one-driversunlocktwrpfactory-t3866191. Is it good also ?
You can just get newest fastboot rom, and then flash with Miflash
Veran125 said:
You can just get newest fastboot rom, and then flash with Miflash
Click to expand...
Click to collapse
If it was too simply ... I think i did that already, But fastboot room, what do you mean with that ?
I just want, now, to be sure, can i save my phone ? It's not dead ?
Cause it's a very good phone and i don't want to loose it, really.
Nope, it's not dead, even with locked bootloader it wouldn't be. But now that you've got an unlocked bootloader, it's very easy to restore
I'm more happy so, 5 hours ( no fake really ) i search a solution .... SO
I found a global rom without .bat files in this folder so i got an error with Mi Flash Tool .. Tell me more about your idea
What's the error if I may ask?
Veran125 said:
What's the error if I may ask?
Click to expand...
Click to collapse
Can not found ( don't remember the file name).bat
FamosoFT said:
Hi,
My phone is bricked, cause i used twrp temporaly, to install a new rom, but after an unexpected wipe my phone lost OS files so i'm just able to use adb & fastboot with the fastboot mode, so lock & unlock oem principaly. Please help me it's very very important cause i need to use this phone ...
Thanks.
Click to expand...
Click to collapse
-Tente isso:
Download this official rom: https://en.miui.com/download-354.html
Download this Mi Flash Tool: http://api.en.miui.com/url/MiFlashTool
*I'm assuming you already have the ADB drivers installed on your PC
*Remember to check the CLEAN ALL option
-If the above method does not work, do the following:
* It will only work if you do not have TWRP installed, if it is with twrp installed, I recommend reinstalling the original recovery *
1-Turn off the device and press (POWER BUTTON + VOLUME UP). At that point, the android doll will appear and spelled 'NO COMMAND'
2-Press only (POWER BUTTON) and click quickly (VOLUME UP BUTTON). In this screen you will see the recovery options, use the volume buttons to go to the WIPE DATA/FACTORY RESET option, confirm with YES and restart the device.
3- Wait patiently for 3/5 minutes.
-If none of this works and you can still access twrp, I recommend you try installing a GSI rom using this method: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-functional-twrp-magisk-pie-gsi-t3900119
I recommend this GSI rom (I'm using this now): https://get.resurrectionremix.com/?dir=gsi (choose 'arm64-ab')
This will give you a working system and make it easier to return to stock.
Hope one of these methods helped!
Hi all,
The problem was my PC i had not the .bat files so it couldn't work ...
Thanks @Bruno_Designer for your message, but i hate RROS but you're solution was good
FamosoFT said:
Hi,
My phone is bricked, cause i used twrp temporaly, to install a new rom, but after an unexpected wipe my phone lost OS files so i'm just able to use adb & fastboot with the fastboot mode, so lock & unlock oem principaly. Please help me it's very very important cause i need to use this phone ...
Thanks.
Click to expand...
Click to collapse
If u alredy used twrp den u have adb.
U need mi flash tool.
Download any one of the full fastboot roms for Mi A2 Lie below:
9.6.4.0: https://xiaomifirmware.com/download/10399/
9.6.10.0: https://xiaomifirmware.com/download/10867/
10.0.3: https://xiaomifirmware.com/download/11586/
So to revive ur fone, u do dis. Dis was how i did mine.
1. After downloading a rom of choice, u extract on ur pc using winrar, 7zip or izarc. U basically open the archive using any of these software n copy out the folder contained. The name usually starts with "daisy global ...."
2. U open the extracted rom folder. U will see a bunch of files including "flash_all.bat" etc and a folder called "images".
3. Click on the address bar of d rom folder and copy the address. Den open "mi flash tool" and paste d copied address in the mi flash tool address bar n click on refresh.
4. Boot ur phone to fastboot mode, using "power" & "volume down" buttons together.
connect d phone to ur pc via usb cable.
5. Open ur adb folder and open the adb command window.
Type in the following, one after the other n click enter:
" fastboot devices " dis to confirm the adb connection
" fastboot oem edl " dis to enter edl mode. Ur fone led starts blinking at 1sec intervals.
6. Back to mi flash tool, u click on "refresh". After a second ur fone should be seen as a COM port "COM 10"
7. At d bottom right, u shd find 3 options. Selct "clean all". This shd leave ur bootloader unlocked after the process.
8. U click on "flash" button at the top right. All things going well, within 10 mins the process shd be done and u will see "green" indicator with "success".
9. Hold ur fone n press d power botton for 10 secs. Then ur fone shd power up. Give ur fone exactly about 5 mins to come up "look at the clock & dnt assume"
Dis is an edit of others tutorials. But this is exactly how it worked for me. As long as u use any of the 3 roms i linked u.
Unless i use edl mode, it jus doesnt work for me.
Good luck. Leta know how it goes. And pls click thanks if i helped u.
Problem solved
Thread closed at OP request

[RMN8Pro][Global] Bootloop fix

Evening guys, let's fix the Bootloop of our RMN8Pro if we have installed a menu Recovery TWRP faulty/unsuitable or we have installed a ROM that does not belong to our smartphone.
This method is valid for China to global or Global to global.
NOT FOR INDIAN (sorry about that)
You'll need:
ADB files
Fastboot ROM V10.4.5.0.PGGEUXM
Download both files and unzip them in C:/ADB (if you don't have that folder... just create it)
You will need to rename the file extension of the file <<begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.0000_9.0_eea_f796762f8a.tgz>> from .tgz to .rar
Let's go!!
Turn the phone off, turn it on in fastboot mode (by pressing both POWER and VOL- ) and connect the phone to the PC with its USB cable.
Open a CMD command console (in administrator mode) in C:/ADB and type this (press enter when finished typing):
Code:
fastboot devices
If you have the drivers installed and everything goes well, a series of alphanumeric characters will appear, such as for example:
Code:
a6ghfxfv6 fastboot
Perfect, we can go on.
Next we will flash one by one the files needed to revive the phone.
Write the following lines and press enter at the end of each of them (wait for the files to be installed between line and line):
Code:
fastboot boot boot.img
fastboot flash system.img
fastboot flash vendor.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
When you're done, restart the phone with:
Code:
fastboot reboot
Congratulations, you have your RMN8Pro fixed.
klurosu said:
Evening, let's fix the Bootloop of our RMN8Pro if we have installed a menu Recovery TWRP faulty/unsuitable or we have installed a ROM that does not belong to our phone.
This method is valid for China to global or Global to global.
NOT FOR INDIAN (sorry about that)
You'll need:
ADB files
Fastboot ROM V10.4.5.0.PGGEUXM
Download both files and unzip them in C:/ADB (if you don't have that folder...create it)
You will need to rename the file extension of the file <<begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.0000_9.0_eea_f796762f8a.tgz>> from .tgz to .rar
Let's go!!
Turn the phone off, turn it on in fastboot mode (by pressing both POWER and VOL- ) and connect the phone to the PC with its USB cable.
Open a CMD command console (in administrator mode) in C:/ADB and type this (press enter when finished typing):
If you have the drivers installed and everything goes well, a series of alphanumeric characters will appear, such as for example:
Perfect, we can go on.
Next we will flash one by one the files needed to revive the phone.
Write the following lines and press enter at the end of each of them (wait for the files to be installed between line and line):
When you're done, restart the phone with:
Congratulations, you have your RMN8Pro fixed.
Click to expand...
Click to collapse
So, this is basically a guide of how to flash the images through fastboot, right? Why not just use MiFlash when we are in fastboot mode?
polfrank said:
So, this is basically a guide of how to flash the images through fastboot, right? Why not just use MiFlash when we are in fastboot mode?
Click to expand...
Click to collapse
Because it doesn't work???
Don't believe me?, Just try
send from an RMN8 Pro (xiaomi.eu custom rom)
Miflash will work if in fastboot and have an MI account had requested to unlock BL.
Don't believe me? You try.
idog8818 said:
Miflash will work if in fastboot and have an MI account had requested to unlock BL.
Don't believe me? You try.
Click to expand...
Click to collapse
You still need authorized account Sherlock.
(Omg this guys...)
send from an RMN8 Pro (xiaomi.eu custom rom)
klurosu said:
You still need authorized account Sherlock.
(Omg this guys...)
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
if you don't apply for the Mi account to unlock BL, how will you able to flash anything? Only 2 mins for a new account.....What the problem will be?
idog8818 said:
if you don't apply for the Mi account to unlock BL, how will you able to flash anything? Only 2 mins for a new account.....What the problem will be?
Click to expand...
Click to collapse
Read again (this time read well please) 2 posts above
send from an RMN8 Pro (xiaomi.eu custom rom)
klurosu said:
Read again (this time read well please) 2 posts above
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
Read again but didn't get it. What do you mean ....
idog8818 said:
Read again but didn't get it. What do you mean ....
Click to expand...
Click to collapse
That you still need an Authorized Xiaomi's Account to do that with the old method dude.
send from an RMN8 Pro (xiaomi.eu custom rom)
klurosu said:
That you still need an Authorized Xiaomi's Account to do that with the old method dude.
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
What do you mean by Authorized Xiaomi's Account?? As far as I know, there're 2 types of Mi accounts we commonly talk here.
1. Normal Mi account: used to unlock BL and this can be used in miflash to flash rom, I've tried 100 times in fastboot, and works every time. I registered this account I guess 5 years ago when I need to request unlock BL on note 3 . As I said above, it needs 2 mins to register.
2. Authorised service account: This is not we can easy to register, It's for Mi service center or developers for repair/develop purposes. If no rec, no recovery, blank screen, it can be recovered by SP flash tool, which will need this type of account. This is also why users in following post looking for unbricking.
[GUIDE] [begonia] UNBRICK - stuck on DA mode / Authorised Service Account required
https://forum.xda-developers.com/re...a-mode-authorised-t4000433/page7#post81175069
---------- Post added at 01:20 AM ---------- Previous post was at 01:17 AM ----------
I can prove this by my bricked redmi note 8 pro.
I used my mi account to unlock BL, flashed global rom, but I cannot use it in SP FLASH TOOL to restore because my MI account is not an Authorised Service Account
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
nutellamarco said:
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
Click to expand...
Click to collapse
At the moment you only can do a deep flashing in EDL mode, and need an authorized account... You need to contact someone with this type of account and flash... ( And give some money...)
nutellamarco said:
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
Click to expand...
Click to collapse
Some people are saying they managed to bring to life a phone without rocovery without fastboot mode.search and maybe you find a way. As i remember they said with phone turned off you press volume - and power and you have about 5 seconds to flash. I don't know more details.i wish you success
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
Click to expand...
Click to collapse
as far as I know spflash tool should be ready to flash,. it means with all the files selected, the combination is keeping vol+ and connect the USB cable to PC port, I recommend you search in Google about flashing mediatek devices... Good luck
Literally this guide is really about just how to flash with fastboot instead of Mi Flash(tool which can use anyone with Xiaomi Phone - doesn't require Authorized Service ACC)
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
Click to expand...
Click to collapse
I had this problem at the weekend(Stuck at EDL mode - tried to flash with SP tool but without success(needed service acc - brom error)), you can use SP flash tool with authorized service acc - fastest way, maybe there will be some cracked security file in the future as one for redmi 6. Or do battery trick. You are stick at EDL mode and cannot reboot from it. You can wait to discharge your phone(Tooks ~2 day with pushed power button) then connect into computer and when the led turn less bright use vol - + power to get into fastboot or disconnect battery and reconnect with pushed vol - to get into fastboot(I have used this three times because of installing wrong recovery).
Aglik-x said:
Literally this guide is really about just how to flash with fastboot instead of Mi Flash(tool which can use anyone with Xiaomi Phone - doesn't require Authorized Service ACC)
I had this problem at the weekend(Stuck at EDL mode - tried to flash with SP tool but without success(needed service acc - brom error)), you can use SP flash tool with authorized service acc - fastest way, maybe there will be some cracked security file in the future as one for redmi 6. Or do battery trick. You are stick at EDL mode and cannot reboot from it. You can wait to discharge your phone(Tooks ~2 day with pushed power button) then connect into computer and when the led turn less bright use vol - + power to get into fastboot or disconnect battery and reconnect with pushed vol - to get into fastboot(I have used this three times because of installing wrong recovery).
Click to expand...
Click to collapse
Thanks a lot for your reply
I will do that. But How I can know that phone is on to discharge battery? Best regards
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.[/QUOTE
My oneplus 6 I used to do kind of the same thing... With the phone plugged and everything ready to flash... I used to press - plus power button and it would starting the process..
Click to expand...
Click to collapse
petenoni said:
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.[/QUOTE
My oneplus 6 I used to do kind of the same thing... With the phone plugged and everything ready to flash... I used to press - plus power button and it would starting the process..
Click to expand...
Click to collapse
I try this method, the spflash does not start
I tried all touche combinaisons.
I will wait until the battery were empty and try again.
Thanks for your reply
Click to expand...
Click to collapse
bootloop fix worked for me
I try to post this yesterday but nothing happened so what i did was...
i installed TWRP and in twrp i wipe all data , system, vendor and reboot phone. that was wrong and i stuck in bootloop. so i go back to fastboot and type commands as u say....
fastboot boot boot.img
fastboot flash system.img
fastboot flash vendor.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img - nothing worked
maybe u forgot some commands.... so i use...
fastboot boot boot.img -dont use, it didnt work
fastboot flash system system.img -ok
fastboot flash vendor vendor.img -ok
fastboot flash cust cust.img -ok
fastboot flash recovery recovery.img - but instead of official recovery i used TWRP.img and after reboot a finally boot into TWRP and i flash xiaomi.eu rom and after reboot magisk and all works fine. im not developer but this method worked for me and excuse my english i have global device

system destroyed, when in fastboot mode and plug to the pc (device not recognised)

So, a few months ago I rooted my device with twrp and then installed magisk manager... A few days later the manager stopped working and I got tired of not being able do do nothing so I tried to unroot. I used mi flash to flash the daisy rom and it didn't work so I tried to load to the twrp app and flash through there. Didn't work either. From then on every time I boot the device it shows the message "the system has been destroyed" and Bc of that I searched for solutions. I kinda found one. I boot to fastboot mode and with the platform tools I write on the command line ". /fastboot devices" and then it shows my device. After I write ". /fastboot boot continue" and it starts booting the device and it has worked for like 2 months but 2 days ago I had to reboot my device Bc it started to freeze but when I load to fastboot mode and plug it to the pc it show a prompt saying "the device is not recognized" and the device reboots to the message "system has been destroyed". Pls help, I've searched everywhere and didn't find any solution
Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.
Os_Herdz said:
Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.
Click to expand...
Click to collapse
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode
0flip3 said:
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode
Click to expand...
Click to collapse
you are trying to get to edl mode by typing command "fastboot oem edl" when phone is in fastboot?

Recovering data on a DEAD Redmi Note 8 PRO

Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5

Question no access to phone

when trying to install a new ROM, I completely locked out myself
- fastboot leads to (new ?) orange FASTBOOT screen but
- device will not be recognized via adb/fastboot
- TWRP leads to screen teamwin Recovery Project 3.7.0_12-0 and then goes into bootloop to the same screen
any ideas?
last thing I tried was changing the filesystem inside twrp
gartmann said:
when trying to install a new ROM, I completely locked out myself
- fastboot leads to (new ?) orange FASTBOOT screen but
- device will not be recognized via adb/fastboot
- TWRP leads to screen teamwin Recovery Project 3.7.0_12-0 and then goes into bootloop to the same screen
any ideas?
last thing I tried was changing the filesystem inside twrp
Click to expand...
Click to collapse
Would be nice if you can share a photo of the "new Fastboot screen".
You mean TWRP doesn't function properly?
Did Fastboot work before? What have you done exactly?
If you need more direct help I can give you my Telegram or Discord
It doesn't properly start. These are the pics of the three possibilities I have now.
Fastboot was working before.
Last thing before was the changing the filesystem to (i thing) ExFat
gartmann said:
It doesn't properly start. These are the pics of the three possibilities I have now.
Fastboot was working before.
Last thing before was the changing the filesystem to (i thing) ExFat
Click to expand...
Click to collapse
Orange fastboot is fastbootd, first somehow get your pc to recognise the phone , then to reboot to normal fastboot you gotta use "fastboot reboot bootloader"
From there miflash
Fastbootd can only flash certain partitions - if you run miflash from it , it'll fail I think
gartmann said:
It doesn't properly start. These are the pics of the three possibilities I have now.
Fastboot was working before.
Last thing before was the changing the filesystem to (i thing) ExFat
Click to expand...
Click to collapse
If the Windows installed drivers are the problem, this will fix it:
Boot Windows with Driver Signature Enforcement disabled by doing this:
Open Windows' Power Menu, and while holding SHIFT-key, click Restart.
Select "Startup Settings" > Restart.
Screenshot
Click 7 for Disable Driver Signature Enforcement.
Screenshot
Get Mi Flash, extract the folder, and run Mi Flash.
Click "Driver" in the top-bar and click Install.
Screenshot
After doing this, the drivers are correctly installed and Fastboot and ADB commands should work.
Then you can proceed to temporarily boot a TWRP or OrangeFox that actually works.
"fastboot boot twrp.img"
I recommend OrangeFox.
You can install a recovery with "Install RamDisk" (both have this option).
If you want to flash MIUI or a Custom ROM, flashing the Recovery-flashable ZIP for MIUI or for the Custom ROM, should suffice.
My problem is, that (even after new driver installation with Mi Flash) the PC doesn't recognise the Poco F3 (but recognises without any problem my old Mi Mix 3).
So I concluse that the problem is on Poco side but I have ho idea what I can do it the phone isn't recognised.
gartmann said:
My problem is, that (even after new driver installation with Mi Flash) the PC doesn't recognise the Poco F3 (but recognises without any problem my old Mi Mix 3).
So I concluse that the problem is on Poco side but I have ho idea what I can do it the phone isn't recognised.
Click to expand...
Click to collapse
Does device show up in device manager ? Did you setup adb tools and issue "fastboot reboot bootloader" command ? If this doesn't work, what about "fastboot devices"
Come back when you do this , don't use mi flash untill you reboot phone into bootloader ( blue fastboot )
Maybe even check if adb commands work through twrp as a last resort ... "adb reboot bootloader"
Rstment ^m^ said:
Orange fastboot is fastbootd, first somehow get your pc to recognise the phone , then to reboot to normal fastboot you gotta use "fastboot reboot bootloader"
From there miflash
Fastbootd can only flash certain partitions - if you run miflash from it , it'll fail I think
Click to expand...
Click to collapse
The Orange Fastboot isnt fastbootd, its normal fastboot. The icon changed from the doll miui 12.5 to this orange fastboot on miui 13
gartmann said:
My problem is, that (even after new driver installation with Mi Flash) the PC doesn't recognise the Poco F3 (but recognises without any problem my old Mi Mix 3).
So I concluse that the problem is on Poco side but I have ho idea what I can do it the phone isn't recognised.
Click to expand...
Click to collapse
Download mi unlock tool and run it. Click on the settings icon on the top right corner and download its drivers, it'll ask you to connect the phone to the pc. (connect it on fastboot mode)
If I connect the phone I get the message, that the usb-device isn't recognised, no problem with poco f1 and poco f3
mi unlock tool gives (also after driver installation) this
gartmann said:
If I connect the phone I get the message, that the usb-device isn't recognised, no problem with poco f1 and poco f3
mi unlock tool gives (also after driver installation) this
View attachment 5737887
Click to expand...
Click to collapse
try changing the cable and also try changing the usb port on pc
if still no problems, then the phone port could be faulty
btw, i only meant to say is to download the drivers from mi unlock tool, after that, you can try and flash the stock rom in mi flash tool
gartmann said:
My problem is, that (even after new driver installation with Mi Flash) the PC doesn't recognise the Poco F3 (but recognises without any problem my old Mi Mix 3).
So I concluse that the problem is on Poco side but I have ho idea what I can do it the phone isn't recognised.
Click to expand...
Click to collapse
Did you do my steps including the Driver Signature Enforcement part?
I'm asking because otherwise I'm out of ideas lol
Kinda fked up that Fastboot isn't working for you...
Since Recovery isn't booting for you. Only Fastboot may be your last chance. So try and see if it works with other PCs... other cables... whatever. You gotta make Fastboot to work.

Categories

Resources