fastboot problems? - Xiaomi Redmi Note 5 Pro Questions & Answers

edit3: managed to flash orangefox back(MTP now works in recovery) i should be able to flash a stock rom now
recently tried to upgrade my rom to lineage 17.1 when doing that i accidentally wiped everything(including os)
i have the newest official twrp installed so i thought i could sideload the stock rom but when i tried that turns out sideloading is not working for some reason(stuck at "Starting ADB Sideload feature..." and after about 10 minutes it fails)
then i tried flashing the stock rom with fastboot but any command i try disconnects my phone from my pc("press any key to shutdown" also appears in the top left corner of my phone)
also when i tried following this guide h t t p s://c.mi.com/oc/miuidownload/detail?guide=2
i get this error in the flash tool:
Code:
$fastboot -s 5ed0da1f getvar product 2>&1 I findstr /r /c:"`product: •whyred" II echo Missmatching image and device
edit: i don't have access to an intel machine nor an usb hub(i have a ryzen cpu)
edit2: for some reason i have 3 different errors i can get
Code:
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (status read failed (Too many links))
finished. total time: 1.911s

You haven't downloaded proper fastboot file..
What's your device name ?? Does it have dual camera ? If so it is redmi note 5 pro or redmi note 5 global codenamed whyred
If your phone has single camera then it is Redmi 5 plus global or Redmi Note 5 india codenamed Vince
Download proper package and flash it

SunilSuni said:
You haven't downloaded proper fastboot file..
What's your device name ?? Does it have dual camera ? If so it is redmi note 5 pro or redmi note 5 global codenamed whyred
If your phone has single camera then it is Redmi 5 plus global or Redmi Note 5 india codenamed Vince
Download proper package and flash it
Click to expand...
Click to collapse
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp

ijheaven said:
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp
Click to expand...
Click to collapse
ijheaven said:
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp
Click to expand...
Click to collapse
Check the error message, it's says -- mismatch image and device
Download latest fastboot image for whyred from below link
https://bigota.d.miui.com/V11.0.3.0...XM_20191108.0000.00_9.0_global_f128798d03.tgz

SunilSuni said:
Check the error message, it's says -- mismatch image and device
Download latest fastboot image for whyred from below link
https://bigota.d.miui.com/V11.0.3.0...XM_20191108.0000.00_9.0_global_f128798d03.tgz
Click to expand...
Click to collapse
that's the file i downloaded and tried

ijheaven said:
recently tried to upgrade my rom to lineage 17.1 when doing that i accidentally wiped everything(including os)
i have the newest official twrp installed so i thought i could sideload the stock rom but when i tried that turns out sideloading is not working for some reason(stuck at "Starting ADB Sideload feature..." and after about 10 minutes it fails)
then i tried flashing the stock rom with fastboot but any command i try disconnects my phone from my pc("press any key to shutdown" also appears in the top left corner of my phone)
also when i tried following this guide h t t p s://c.mi.com/oc/miuidownload/detail?guide=2
i get this error in the flash tool:
Code:
$fastboot -s 5ed0da1f getvar product 2>&1 I findstr /r /c:"`product: •whyred" II echo Missmatching image and device
Click to expand...
Click to collapse
Which platform are u using to flash.Is it Amd/intel
If it's amd then amd breaks support for fastboot as i also have amd ryzen 2500u and whenever i flash the same i get the same errror.
Buying USB hub solved the problem

Sidgup1998 said:
Which platform are u using to flash.Is it Amd/intel
If it's amd then amd breaks support for fastboot as i also have amd ryzen 2500u and whenever i flash the same i get the same errror.
Buying USB hub solved the problem
Click to expand...
Click to collapse
i'll try that thanks!

or you can try this
flash twrp or orangefox recovery with fastboot and boot into it
then get recovery rom zip and flash that zip using recovery
link is here if you need it.

gursewak.10 said:
or you can try this
flash twrp or orangefox recovery with fastboot and boot into it
then get recovery rom zip and flash that zip using recovery
link is here if you need it.
Click to expand...
Click to collapse
i have tried this already but i can't flash/boot with fastboot
Code:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
and im also getting this error
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s

ijheaven said:
i have tried this already but i can't flash/boot with fastboot
Code:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
and im also getting this error
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s
Click to expand...
Click to collapse
try changing fastboot+adb files
and try this command fastboot getvar all
check if bootloader is unlocked properly

gursewak.10 said:
try changing fastboot+adb files
and try this command fastboot getvar all
check if bootloader is unlocked properly
Click to expand...
Click to collapse
bootloader is unlocked and reinstalled adb still no luck

ijheaven said:
bootloader is unlocked and reinstalled adb still no luck
Click to expand...
Click to collapse
Its working , but khmmm use miui flash tool... stop using adb, becouse you don't know what are you doing..You gonna brick it and than you'll cry again.??
Tip: dummy file. ?
Good luck.
Sent from XDA Labs

Related

can't unlock bootloader

Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem
amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?
Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here
Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk
tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.

Completely Bricked?

All know is I can only boot into Fastboot Mode and Stock Recovery mode, but every way I try to get the flash the stock rom or TWRP won't work.
Device state is unlocked.
Reinstalled Google Drivers.
I will use taimen-opm1.171019.013-factory-6d9954c3
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
fastboot version eac51f2bb6a8-android
Unified Android Toolkit:
Booting TWRP recovery-twrp-3.2.1.0-taimen.img ..
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.007s
Click to expand...
Click to collapse
Cannot flash TWRP
PS C:\adb> fastboot devices
711KPVH0902199 fastboot
PS C:\adb> fastboot flash recovery twrp.img
sending 'recovery' (40960 KB)...
FAILED (remote: Requested download size is more than max allowed)
finished. total time: 0.009s
Click to expand...
Click to collapse
ADB sideload
PS C:\adb> adb sideload C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip
loading: 'C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip'
* cannot read 'C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip' *
Click to expand...
Click to collapse
If I use flash-all.bat:
sending 'bootloader' (36344 KB)...
FAILED (unknown status code)
finished. total time: 343.328s.
Click to expand...
Click to collapse
If I use flash-all command in cmd:
PS C:\Users\tiger\Desktop\tamien> flash-all
error: cannot load 'bootloader-taimen-tmz10n.img'
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.007s
error: cannot load 'radio-taimen-g8998-00122-1708311414.img'
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.007s
W/ ( 9820): Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory
error: failed to open zip file 'image-taimen-opd1.170816.025.zip': I/O Error
Click to expand...
Click to collapse
Do you have the latest adb downloaded from Google?
Also, there is no recovery partition any longer, it's built in to the boot partition.
You can try the command "fastboot boot TWRP.img" to boot to TWRP.
azntiger said:
All know is I can only boot into Fastboot Mode and Stock Recovery mode, but every way I try to get the flash the stock rom or TWRP won't work. Device state is unlocked.
Unified Android Toolkit:
Cannot flash TWRP
ADB sideload
If I use flash-all.bat:
If I use flash-all command in cmd:
Click to expand...
Click to collapse
First, have you read this? https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Second, are your SDK platform-tools up to date??
Have you taken an OTA?
Your twrp command is wrong like the post after yours stated.
Did you give both bootloader unlock commands?
fastboot flashing unlock
And
fastboot flashing unlock_critical
ilal2ielli said:
Do you have the latest are downloaded from Google?
Also, there is no recovery partition any longer, it's built in to the boot partition.
You can try the command "fastboot boot TWRP.img" to boot to TWRP.
Click to expand...
Click to collapse
Yes. I reinstalled Google Drivers. I'm using taimen-opd1.170816.025-factory-907c4030.
I tried boot twrp.img, but it just hangs during the downloading boot.img.
PS C:\adb> fastboot devices
711KPVH0902199 fastboot
PS C:\adb> fastboot boot twrp.img
downloading 'boot.img'...
Click to expand...
Click to collapse
azntiger said:
Yes. I reinstalled Google Drivers. I'm using taimen-opd1.170816.025-factory-907c4030.
I tried boot twrp.img, but it just hangs during the downloading boot.img.
Click to expand...
Click to collapse
Why are you trying to flash the November build?
Badger50 said:
Why are you trying to flash the November build?
Click to expand...
Click to collapse
8.1 causes my proximity sensor to malfunction. The screen wouldn't turn on back on after a call. Alway-on didn't work because it thought the proximity sensor was blocked.
azntiger said:
8.1 causes my proximity sensor to malfunction. The screen wouldn't turn on back on after a call. Alway-on didn't work because it thought the proximity sensor was blocked.
Click to expand...
Click to collapse
That's a phone app problem. Either uninstall the phone app update, or find the phone app 16.0 on apk mirror. However, if you want to downgrade, look here.
https://www.google.com/amp/s/forum....-2-xl/help/downgrade-8-1-to-8-0-t3726641/amp/
Badger50 said:
That's a phone app problem. Either uninstall the phone app update, or find the phone app 16.0 on apk mirror. However, if you want to downgrade, look here.
https://www.google.com/amp/s/forum....-2-xl/help/downgrade-8-1-to-8-0-t3726641/amp/
Click to expand...
Click to collapse
I'll take a look if I can get my phone working again lol.
Badger50 said:
First, have you read this? https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Second, are your SDK platform-tools up to date??
Have you taken an OTA?
Your twrp command is wrong like the post after yours stated.
Did you give both bootloader unlock commands?
fastboot flashing unlock
And
fastboot flashing unlock_critical
Click to expand...
Click to collapse
SDK is up to date.
Not sure what you mean by "taken" an OTA.
So now I have a device null, but fastboot devices is seen.
"fastboot flashing unlock" hangs, but I imagine that's because no device was found?
PS C:\Users\tiger\Desktop\Pixel> fastboot devices
711KPVH0902199 fastboot
PS C:\Users\tiger\Desktop\Pixel> adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
PS C:\Users\tiger\Desktop\Pixel> fastboot flashing unlock
...
Click to expand...
Click to collapse
azntiger said:
I'll take a look if I can get my phone working again lol.
SDK is up to date.
Not sure what you mean by "taken" an OTA.
So now I have a device null, but fastboot devices is seen.
"fastboot flashing unlock" hangs, but I imagine that's because no device was found?
Click to expand...
Click to collapse
You may have to use this to get back on track my friend.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
I'm not entirely sure what the issue is (it could be a couple of things), but here are some issues that I see to help you troubleshoot:
1. Adb commands don't work in bootloader mode, only fastboot commands, which is why your device is visible to fastboot and not adb.
2. The file that you tried to adb sideload was a factory image, not an OTA. Adb sideload can only be used with OTA images. And even if you were using an OTA image, OTA images cannot be used to downgrade to a previous firmware version.
3. The latest version of adb is 1.0.39. You are using an older version. That fact itself doesn't really matter since adb will not help you in this situation, but fastboot will and if your adb is obsolete, I'd be willing to bet that your fastboot is too. Pixel 2 support was added in the October 2017 release of adb and fastboot. If yours is older than that, you're gonna have a bad time.
4. "Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory." Fastboot can't find your firmware files. Try placing the entire contents of the factory image, including the .zip file listed here, into the same directory as fastboot.exe (based on your post, it seems like the folder you want is C:\adb). Then rerun flash-all.bat. The script is assuming that fastboot.exe and all of the firmware files are in the same folder and if they're not, that could be a problem.
5. You do not have driver issues. The fact that fastboot devices worked means that your drivers/connection are/is working fine.
PS: Get the latest adb and fastboot here: https://developer.android.com/studio/releases/platform-tools.html
UPDATE: I did a Google search for adb/fastboot version eac51f2bb6a8-android. I found a reference to it in a forum post dated mid-2016. There's your problem. Or one of them, anyway. If you do adb --version or fastboot --version on the latest releases, they will tell you that they are version 0.0.1-4500957.
TheSt33v said:
4. "Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory." Fastboot can't find your firmware files. Try placing the entire contents of the factory image, including the .zip file listed here, into the same directory as fastboot.exe (based on your post, it seems like the folder you want is C:\adb). Then rerun flash-all.bat. The script is assuming that fastboot.exe and all of the firmware files are in the same folder and if they're not, that could be a problem.
Click to expand...
Click to collapse
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Code:
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.395s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
azntiger said:
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Click to expand...
Click to collapse
Open up your SDK and look for a file named "platform-tools" that is where all your files should be placed.
Badger50 said:
Open up your SDK and look for a file named "platform-tools" that is where all your files should be placed.
Click to expand...
Click to collapse
All the platform-tools and the stock rom are together in folder.
azntiger said:
All the platform-tools and the stock rom are together in folder.
Click to expand...
Click to collapse
Did you extract the factory image first, or just put the whole zip file in platform-tools?
azntiger said:
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Code:
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.395s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
Click to expand...
Click to collapse
Hmm. Fastboot is definitely having issues communicating with your phone. "Failed to identify current slot" is a bad sign. If I were you, I would try flashing the most recent factory image (not the November 8.0 image you're trying to flash) first just to see if you can get everything up to date again and clear out any mismatched files that may have been flashed during your attempts. Once you manage that, then try to downgrade. If you can, try a different computer too, preferably one with a type C input that you can use the stock USB cable with.
---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------
Badger50 said:
Did you extract the factory image first, or just put the whole zip file in platform-tools?
Click to expand...
Click to collapse
The fact that he's not getting "not found" errors means that all the expected files are found by fastboot.
The fact that he's not getting "not found" errors means that all the expected files are found by fastboot.[/QUOTE]
Thanks man. I learned something new today :good:
Wonder if his transfer cable. I've seen that cause headaches as well ?
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
azntiger said:
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
Click to expand...
Click to collapse
Oh nice! Glad you got it figured out. This stuff can be a bit tricky at times. I know I've lost some hair from pulling it out when things didn't go right! ?
azntiger said:
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
Click to expand...
Click to collapse
I was on edge just reading this! I would also look into Deuce's script. It can save the 'device can't boot' issue once and for good.
Kudos on not having a faulty device~!

Mi Mix 2 won't accept TWRP

Hi all,
I am getting a headached with my mix 2 ......
Bootloader is unlocked (shown in Developer Settings and as little text when entering Backup/Fastboot).. I tried different Versions of fastboot from an old version 1:7.0.0+r33-2 to an new one -> fastboot version 28.0.0-4797878.
MIUI Version: 9.6.1.0(ODEMIFD) (Stable)
And yes I did it like the manual here on xda for this mobile ...
I also changed the System from Windows 10 to an Kali....
There isn't a single line of output.
Trying to directly boot the TWRP Image stucks at the first line telleng me: Downloading 'boot.img'
Someone can help me?
Friend here who helped him:
Even just listing the variables didn't yield any output (download got stuck on the "getvar: stuff, too)
I´m getting the same, i have latest global beta 8.7.5, its working fine but i wanted to flash LOS and for some reason no fastboot command works, only fastboot devices. Please someone help
ernesto.ulloa said:
I´m getting the same, i have latest global beta 8.7.5, its working fine but i wanted to flash LOS and for some reason no fastboot command works, only fastboot devices. Please someone help
Click to expand...
Click to collapse
Maybe we should really trying Step 1. Disable driver signature enforcement in Windows from the all in one user guide .... (i didn'T tried it actually)
techler said:
Maybe we should really trying Step 1. Disable driver signature enforcement in Windows from the all in one user guide .... (i didn'T tried it actually)
Click to expand...
Click to collapse
Tried it....... no progress
Done in Windows:
.\fastboot.exe devices
9476f4d3 fastboot
and trying to flash
.\fastboot.exe -v flash recovery twrp-3.2.2-1-chiron.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "GetVar Variable Not found"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "536870912"
fastboot: verbose: target reported max download size of 536870912 bytes
Sending 'recovery' (26360 KB)
fastboot: verbose: sending command "download:019be000"
stucks there ........
and live boot too ...
.\fastboot.exe -v boot .\twrp-3.2.2-1-chiron.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:019be000"
techler said:
Tried it....... no progress
Done in Windows:
.\fastboot.exe devices
9476f4d3 fastboot
and trying to flash
.\fastboot.exe -v flash recovery twrp-3.2.2-1-chiron.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "GetVar Variable Not found"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "536870912"
fastboot: verbose: target reported max download size of 536870912 bytes
Sending 'recovery' (26360 KB)
fastboot: verbose: sending command "download:019be000"
stucks there ........
and live boot too ...
.\fastboot.exe -v boot .\twrp-3.2.2-1-chiron.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:019be000"
Click to expand...
Click to collapse
EDIT:
It worked, i changed to my laptop(win 10). I used a git bash(random used this), no usb devices are connected and no internet.
Just typed .\fastboot.exe flash recovery twrp.img
It worked
Warning: Only reboot to Recovery and install the .img with the "temporary" again, if you don't Xiaomi will place it's own bootloader again there.

[Help] Pixel 3 xl stuck in twrp

i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Update: solved. I had to run the command window and admin and it flashed just fine. Thanks spotmark!
superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
Download whatever build you're on and extract the boot image. Then fastboot flash the boot image.
superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
Try flashing Magisk again in TWRP.
spotmark said:
Download whatever build you're on and extract the boot image. Then fastboot flash the boot image.
Click to expand...
Click to collapse
Code:
c:\adb>fastboot flash boot bl.img
Sending 'boot_a' (8489 KB) OKAY [ 0.310s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5034669
FAILED (remote: '(boot_a) No such partition')
Finished. Total time: 0.564s
thats what it doesn when i try to flash boot image
superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
.
Plz read line #1 on post #1 for twrp . . . ( hint ) it'll tell you that the twrp team has "not" yet got adb sideload working. . We all have to be patient !
.
And the good News is . . . if you use the usb-C adapter in the box and plug in a usb-A thumb drive into the pixel when running twrp . . . . you can see and grab stuff off that thumb drive. . . . . it worked for me 1
superbean83 said:
Code:
c:\adb>fastboot flash boot bl.img
Sending 'boot_a' (8489 KB) OKAY [ 0.310s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5034669
FAILED (remote: '(boot_a) No such partition')
Finished. Total time: 0.564s
thats what it doesn when i try to flash boot image
Click to expand...
Click to collapse
You need to flash the boot.img not the bootloader.
superbean83 said:
thats what it doesn when i try to flash boot image
Click to expand...
Click to collapse
Fastboot flash boot --slot all boot.img
airmaxx23 said:
You need to flash the boot.img not the bootloader.
Click to expand...
Click to collapse
Do you have the latest sdk platform tools?
Sent from my [device_name] using XDA-Developers Legacy app

The System has been destroyed - only fastboot possible

Hello,
I bricked my Redmi Note 8T and I have no idea how to save my phone!
What did I do?
I unlocked my phone with XiaomiTool V2 and added Magisk, installed TWRP and trieed to add LineageOS.
So I tried to restart but the system stocked in a "boot - shutdown - boot - shutdown..."
I read in a description, that I have to delete in TWRP-mode some folders in WIPE so I deleted "System", "Data", "Cache", and maybe some other folders! I'm so stupid!
So there is only "The System has been destroyed", after around 30 seconds the system starts again and the bad massage comes again...
It is just possible to start the fastboot mode!
So I tried again to flash and boot TWRP:
sudo fastboot flash recovery twrp.img
target reported max download size of 804274176 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.617s]
writing 'recovery'...
OKAY [ 0.349s]
finished. total time: 1.967s
sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.615s]
booting...
FAILED (status read failed (No such device))
finished. total time: 37.120s
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Blasmuskant said:
Hello,
I bricked my Redmi Note 8T and I have no idea how to save my phone!
What did I do?
I unlocked my phone with XiaomiTool V2 and added Magisk, installed TWRP and trieed to add LineageOS.
So I tried to restart but the system stocked in a "boot - shutdown - boot - shutdown..."
I read in a description, that I have to delete in TWRP-mode some folders in WIPE so I deleted "System", "Data", "Cache", and maybe some other folders! I'm so stupid!
So there is only "The System has been destroyed", after around 30 seconds the system starts again and the bad massage comes again...
It is just possible to start the fastboot mode!
So I tried again to flash and boot TWRP:
sudo fastboot flash recovery twrp.img
target reported max download size of 804274176 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.617s]
writing 'recovery'...
OKAY [ 0.349s]
finished. total time: 1.967s
sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.615s]
booting...
FAILED (status read failed (No such device))
finished. total time: 37.120s
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Click to expand...
Click to collapse
Doesn't sound so bad. And of you had searched the forum before panic posting, you would have easily found at least 3 similar threads already started.
Not knowing what you had wiped from twrp before, leaves the best option for you is to flash the factory fastboot ROM, and then start over.
There is a thread here about fastboot ROM i beleive.
just miflash
Blasmuskant said:
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Click to expand...
Click to collapse
in fastboot rom there must be a file vbmeta.img....if you don't want to download the fastboot rom then download vbmeta.img from here or here..
then download latest platform tools.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd/terminal in this folder path and flash vbmeta with phone in fastboot mode by this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Thank you for your fast answers! I tried already the search function but it seemed to me beeing different problems!
wsdyleon said:
just miflash
Click to expand...
Click to collapse
How can I do it in fastboot mode with Linux?
the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....if you don't want to download the fastboot rom then download vbmeta.img from ...
then download ...
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd/terminal in this folder path and flash vbmeta with phone in fastboot mode by this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
I tried it with the vbmeta.img from the fastboot Redmi Note 8 – Global Stable ROM (V11.0.9.0.PCOMIXM | MIUI 11 | Android 9.0) and the platform-tools for linux from xiaomifirmware.com.
sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
< waiting for any device >
On the phone then is "Press any key to shutdown"
After trying again I got:
target didn't report max-download-size
sending 'vbmeta' (4 KB)...
But then nothing happens...
What is wrong?
Blasmuskant said:
I tried it with the vbmeta.img from the fastboot Redmi Note 8 – Global Stable ROM (V11.0.9.0.PCOMIXM | MIUI 11 | Android 9.0) and the platform-tools for linux from xiaomifirmware.com.
sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
< waiting for any device >
On the phone then is "Press any key to shutdown"
After trying again I got:
target didn't report max-download-size
sending 'vbmeta' (4 KB)...
But then nothing happens...
What is wrong?
Click to expand...
Click to collapse
Was your phone connected in fastboot?
the_weird_aquarian said:
Was your phone connected in fastboot?
Click to expand...
Click to collapse
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Blasmuskant said:
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Click to expand...
Click to collapse
Is it working now? Why don't you try flashing the stock firmware again?
Blasmuskant said:
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Click to expand...
Click to collapse
Download the latest platform tools and try again once
It works!
[email protected] said:
Is it working now? Why don't you try flashing the stock firmware again?
Click to expand...
Click to collapse
It worked, I installed the Stock recovery and then TWRP (all with fastboot) and so it was possible for me to install LineageOS!
Thank you very much for your support!

Categories

Resources