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.
Related
I have a two phones.
Mi Max 3/32 : Global 8.1.6.0. I recieved OTA to 8.2.1.0. Start downloading, on 40%+- phone freeze and reboot. Stuck on MI logo and dont boot. Dont show powered by android. Just mi logo.
Then i flash 8.2.1.0 trough MiFlash, bootloader locked, and... Same situation. Stuck on bootlogo. I Flash china rom, i flash global, flash older version. Come on Xiaomi! What wrong with you?!
Okay. Story #2
Mi max pro 3/64. Global 8.0.3.0. I downloading OTA, press instal, phone reboot and go install update. Ok. After this process, phone boot and... Cycle reboot. Again and again. On launcher, on setup wizards, on mi logo. Everywhere. Hmmm, okay, i open miflash repeat all as in story #1. Not effect. Zero. Cycle reboot. How?!
I dont know.
Both phones not bricks. But and dont work.
Debugging on usb is a necessary? I dont activated bcaz my phones dont booted. Funny, yeah.
Can it connect via adb?
Sent from my MI MAX using Tapatalk
RAMBO29 said:
Can it connect via adb?
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
yes
If it can connect via adb, flash via EDL mode and see.
If you are on miu you must check developer settings cause miui time to time unchecks option oem unlocking (in my case two times) for this reason ever i look at this and allow usb debugging always must be allowed and look at dev options is absolutely necessary to correct flash of roms, may be you are rooted when you tried to update and system cannot update by this way (device itself or autoupdate). to solve try first installing same version through fastboot, probably yet you don`t loose your data. but you must select option "flash_all_except_storage" from your unpacket zip rom
IndDoc said:
If it can connect via adb, flash via EDL mode and see.
Click to expand...
Click to collapse
hmm, for this it is necessary unlock boot?
SubwayChamp said:
If you are on miu you must check developer settings cause miui time to time unchecks option oem unlocking (in my case two times) for this reason ever i look at this and allow usb debugging always must be allowed and look at dev options is absolutely necessary to correct flash of roms, may be you are rooted when you tried to update and system cannot update by this way (device itself or autoupdate). to solve try first installing same version through fastboot, probably yet you don`t loose your data. but you must select option "flash_all_except_storage" from your unpacket zip rom
Click to expand...
Click to collapse
okay,
I did so. flash firmware and immediately bootloop. no root.
Dark_Eyes said:
hmm, for this it is necessary unlock boot?
Click to expand...
Click to collapse
Not required if you're going to flash the stable version.
IndDoc said:
Not required if you're going to flash the stable version.
Click to expand...
Click to collapse
sorry my mistake, i try but fastboot devices comand work (see device), adb ... not.
flash via fastboot
FAILED (remote: device is locked. Cannot erase).
need to unlock, yep?
That's not EDL, that's fastboot. See here for a guide how to use EDL mode.
IndDoc said:
That's not EDL, that's fastboot. See here for a guide how to use EDL mode.
Click to expand...
Click to collapse
i know about that. but my phones flashing via miflash (edl mode, Qualcomm HS-USB QDLoader 9008) and no boot (mi logo or mi logo plus powered by android stuck 5-10-15-55 mins)
why? i dont know.
upd. It's a MIRACLE. one phone (3/32) is ALIVE
Dark_Eyes said:
i know about that. but my phones flashing via miflash (edl mode, Qualcomm HS-USB QDLoader 9008) and no boot (mi logo or mi logo plus powered by android stuck 5-10-15-55 mins)
why? i dont know.
upd. It's a MIRACLE. one phone (3/32) is ALIVE
Click to expand...
Click to collapse
Good! Make sure you are flashing the right verison. If your phone is stuck on 'powered by android' screen, it's a good sign. It means your phone will eventually boot up.
IndDoc said:
Good! Make sure you are flashing the right verison. If your phone is stuck on 'powered by android' screen, it's a good sign. It means your phone will eventually boot up.
Click to expand...
Click to collapse
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Dark_Eyes said:
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Click to expand...
Click to collapse
Sounds like you have a hardware problem. Take it to a service center.
IndDoc said:
Sounds like you have a hardware problem. Take it to a service center.
Click to expand...
Click to collapse
agree, it seems. thank you.
Dark_Eyes said:
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Click to expand...
Click to collapse
Well, let me tell the way that I flash exactly, for me works perfectly, EDL never work for me. Flash for fastboot couldn't work properly if you place files in any side of your PC. I place adb folder in main disk, in my case c:, unpack all the files of you rom beside the 4 files of adb in same folder (adb has created a path in system environment) then in mode fastboot with usb plugged device (how you loosed your data) right click on "flash_all" for rom can repair your partitions. (I don't remember now if appears with right click option to execute like an administrator better) don't use meanwhile your pc. may that help you
SubwayChamp said:
Well, let me tell the way that I flash exactly, for me works perfectly, EDL never work for me. Flash for fastboot couldn't work properly if you place files in any side of your PC. I place adb folder in main disk, in my case c:, unpack all the files of you rom beside the 4 files of adb in same folder (adb has created a path in system environment) then in mode fastboot with usb plugged device (how you loosed your data) right click on "flash_all" for rom can repair your partitions. (I don't remember now if appears with right click option to execute like an administrator better) don't use meanwhile your pc. may that help you
Click to expand...
Click to collapse
correct me:
you reboot to fastboot (vol- + power), rabbit logo, connect usb w\out pressing any buttons
create folder adb (4files adb + all files of firmware w\out folder image)
and run flash all
unlock boot required?
Dark_Eyes said:
correct me:
you reboot to fastboot (vol- + power), rabbit logo, connect usb w\out pressing any buttons
create folder adb (4files adb + all files of firmware w\out folder image)
and run flash all
unlock boot required?
Click to expand...
Click to collapse
Yes, mode fastboot in device with any trick like EDL, just connect to pc, no unlock bootloader required but must be an stock rom, fastboot image rom
SubwayChamp said:
Yes, mode fastboot in device with any trick like EDL, just connect to pc, no unlock bootloader required but must be an stock rom, fastboot image rom
Click to expand...
Click to collapse
after i click flash all, window appears 1 sec and all. no effect. what wrong?
Dark_Eyes said:
after i click flash all, window appears 1 sec and all. no effect. what wrong?
Click to expand...
Click to collapse
Recogniced device?, type first fastboot devices to be sure
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
try upgrade your android sdk on your pc
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful
i am trying to flash twrp there is no folder called adb i have installed the 15 second adb and all so i have got this minimal adb flashboot and i tried with that and got this ---- FAILED (remote: Flashing is not allowed in Lock State). i have granted all usb and oem unlocking. please help with this
Phone shows unlocked during the boot?
I had the same Problem,after a Factory Reset works for me.
I am on Miglobe-Rom Miui10 8.6.28.
Minimal ADB is enough.
Or use this from Attachment.
Unpack with Win.zip and copy Twrp in this Folder.
Conect the Phone with your Pc ,boot into Bootloader and click "cmd-here.exe"
Use this Command
fastboot flash recovery twrp-3.2.1-3-whyred.img
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
gamebenchjake said:
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
Click to expand...
Click to collapse
Have you fixed your app to run on Magisk-SU ?
otonieru said:
Have you fixed your app to run on Magisk-SU ?
Click to expand...
Click to collapse
Hey Otonieru,
Not yet, but I've got one of the engineers working on it - hopefully it'll be up in the next 30 days or so
Same problem here after updating my gcam was not working was enabling hall again but it is not booting into twrp
Redmi Note 5 pro
So my Bootloader is locked,
My phone stuck in MI recovery idk how.
I cant install MIUI via fastboot. Im stuck ..
Can anyone please help me here not sure how to proceed further.
If you have made sure that you have all the drivers installed and still have not solved, you need to use an Intel-based PC / notebook and use a usb 2.0.
”Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful”
i did that but it is showing failed(too many links)and "press any key to reboot" showing on my phone's fastboot screen
Fastboot boot recovery.img flashing problem on Redmi note 5 pro
My bootloader is unlocked and my oem as well as usb deb is on. After i connect my phone in fastboot mode to my pc. The cmd shows fastboot devices but when it comes to fastboot boot recovery.img flashing device get disconnected. Plzzzzzz let me know a solution for this. A solution for this will be highly appreciateable.
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?
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
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