Database Users

Can't install CWM or TWRP

So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat

It looks like it's flashing correctly, but since you can't reboot into recovery, I would be willing to bet you're flashing the wrong file. What file are you using? Once you flash recovery, you need to boot straight into it so the install completes.
Sent from my HTC6525LVW using Tapatalk

ozeyguy said:
So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat
Click to expand...
Click to collapse
Flashify works pretty well, maybe give it a shot. Also, make sure you have the correct versions.

RikRong said:
It looks like it's flashing correctly, but since you can't reboot into recovery, I would be willing to bet you're flashing the wrong file. What file are you using? Once you flash recovery, you need to boot straight into it so the install completes.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I am using the right files.

Works like a charm. Thanks!

i am having the same problem even with flashify i am using recovery-clockwork-touch-6.0.4.4-xt907.img
after flashing with either flashify or adb i boot into recovery and it hangs at the unlocked bl screen, unlocked bl screen again, then it boots.

deathwithafi said:
i am having the same problem even with flashify i am using recovery-clockwork-touch-6.0.4.4-xt907.img
after flashing with either flashify or adb i boot into recovery and it hangs at the unlocked bl screen, unlocked bl screen again, then it boots.
Click to expand...
Click to collapse
i was having the exact same problem. if you check out this post (http://forum.xda-developers.com/show....php?t=2785214) they suggest using CWM 6.0.4.9 recovery for KK bootloader. i did a fastboot with this and haven't had any problems since.

chuck solid said:
i was having the exact same problem. if you check out this post (http://forum.xda-developers.com/show....php?t=2785214) they suggest using CWM 6.0.4.9 recovery for KK bootloader. i did a fastboot with this and haven't had any problems since.
Click to expand...
Click to collapse
Thank you i will try that
That link goes to 404 error
i found it and it works. thank you

deathwithafi said:
Thank you i will try that
That link goes to 404 error
i found it and it works. thank you
Click to expand...
Click to collapse
Where did you find it? I'm having the same issue, but I can't locate it.
Thanks.

drenze said:
Where did you find it? I'm having the same issue, but I can't locate it.
Thanks.
Click to expand...
Click to collapse
Second link
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
Second link
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Thanks!

ezknives said:
Second link
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Link is dead... is there another? TIA!

ozeyguy said:
So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat
Click to expand...
Click to collapse
Im having the same exact problem. I cannot get into recovery. I've tried mfastboot to load CWM (recovery-clockwork-6.0.4.4-xt907.IMG) and TWRP (XT901-XT907-TWRP-2.6.3.0-recovery.img) as well as TWRP Manager and Flashify on the phone. My bootloader is UNLOCKED and This is my config:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does it have something to do with the version of KK? TIA

I believe the TWRP built for this phone is still unofficial, so you probably can't flash it with the app. When you flash with fastboot, do you power off after flashing, and then reboot straight back into recovery? If you don't do this, the stock recovery will over write.
Sent from my Nexus 5

When you flash with fastboot, do you power off after flashing, and then reboot straight back into recovery?
Click to expand...
Click to collapse
I did. I would get a (I dont know how to describe it) but a small "blip" at the bottom of the screen then it boot normal. I tried it several times and the same thing happened, like it was "trying" to get into recovery then just simply boots. I tried different IMG's thinking maybe they were corrupt. Also different USB ports and cables (motorola). NADA. Does it have something to do with the stock KK (I have a verizon phone) is there something in there that is keeping it from "sticking"?

UPDATE: Problem Solved... found in another post that someone was having a similar issue and they used xt926-KK-CWM-6048.img (which is compatible with xt907) I flashed it and CWM came up like normal! Thanks for all your efforts...I hope this helps someone in the future! Cheers!~

Update on the update!
KarmaKid said:
UPDATE: Problem Solved... found in another post that someone was having a similar issue and they used xt926-KK-CWM-6048.img (which is compatible with xt907) I flashed it and CWM came up like normal! Thanks for all your efforts...I hope this helps someone in the future! Cheers!~
Click to expand...
Click to collapse
So I was having issues with that version of CWM ... I found the version of TWRP that works with xt907 and now I get this?!
the screen is not sized properly. Thoughts? TIA

KarmaKid said:
So I was having issues with that version of CWM ... I found the version of TWRP that works with xt907 and now I get this?!
the screen is not sized properly. Thoughts? TIA
Click to expand...
Click to collapse
Though that version will flash to the 907, it's still designed for the 926's screen. You need to find the correct file.
Sent from my Nexus 5

I got the same thing before - It happens when using the wrong version of TWRP
I believe the correct versions are here : http://downloads.blissroms.com/Recovery/Recovery/xt907/

beeewell said:
I got the same thing before - It happens when using the wrong version of TWRP
I believe the correct versions are here : http://downloads.blissroms.com/Recovery/Recovery/xt907/
Click to expand...
Click to collapse
FIXED: THANKS! TWRP 2850...no issues!

Findings after unlocking bootloader

So as far as I know, I am one of the first people to have the bootloader unlocked on the Chinese Mate 9.
I have some unfortunate findings. Mainly, you cannot flash large files over fastboot. Here's what happens:
target reported max download size of 471859200 bytes
sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.869s
We can flash small files, can flash recovery, etc. So we need someone to make TWRP in order to do anything with the unlocked BL. Since there's no source out for the Mate 9, I'm worried about that, but hopefully @raimondomartire can get it done!

Update: I've built a preliminary TWRP, but I don't understand TWRP well, and the mount points are incorrect. However, I believe we will have a working TWRP very soon.

Solid info. Thanks. Once more developers start hopping on, I'm sure we'll get to this faster especially after the fact that you managed to already get the bootloader unlock.

Ahh, progress. Almost there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Good job !!!!

Congrats
أرسلت من HUAWEI NXT-L29 بإستخدام تاباتلك

duraaraa said:
I have some unfortunate findings. Mainly, you cannot flash large files over fastboot. Here's what happens:
target reported max download size of 471859200 bytes
sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.869s
Click to expand...
Click to collapse
I don't think, that it can stop xda community
http://forum.xda-developers.com/showthread.php?t=2749797

Job well done!

5[Strogino] said:
I don't think, that it can stop xda community
http://forum.xda-developers.com/showthread.php?t=2749797
Click to expand...
Click to collapse
Thank you for the idea. Unfortunately, when I tried this tool, it required that the image size is a multiple of 4096 bytes. So I appended null bytes to the end until it was a multiple, split, and flashed all the files, but it doesn't boot.

An update. I hate TWRP mounting /system, /data, /cache, and so on. The only one that doesn't mount is 3rdmodem (I can't even find it in the filesystem.) The data partition and /sdcard partition seem to be encrypted. USB doesn't work (yet)
When I try to flash supersu, the phone crashes and reboots just after the message that it's trying to do a systemless install and creating space...
I tried flashing the zip from Huawei's google services download. That flash worked.
I can't flash any regular huawei updates without a lot of work, so I haven't made an honest effort at unpacking the update.app's partitions and making them into flashable zip files.
So we're kind of stuck unfortunately, with not very much we can do, despite the bootloader being unlocked.
That's all I've got for you all for now.

How do you do to unlock the bootloader once you got the code

playa77176 said:
How do you do to unlock the bootloader once you got the code
Click to expand...
Click to collapse
If you don't know how to do it you might be better off not doing it because there is some risk involved with it at this point.
If you want to try anyway turn off the phone and plug in a USB cable while holding volume down key.
Then run the command on your computer
fastboot oem unlock CODE
Replace code with your code.

Update. I just figured out how to flash a rom via fastboot. Going to try flashing European newest rom on Chinese mate momentarily.

Update: The error I mentioned in my previous post (sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
)
This error doesn't occur if I'm flashing the Chinese firmware. Only if I flash the European firmware.
Something is not quite right. I'm download other version of Euro firmware to check.

Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.

duraaraa said:
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
Click to expand...
Click to collapse
Maybe you need an updated fastboot files?

It's possible to unlock With srktool ?

playa77176 said:
It's possible to unlock With srktool ?
Click to expand...
Click to collapse
I think it's best you stick to the regular fastboot commands. SRKTool is for the older Mate, so it might want to flash an incompatible TWRP or something like that.

gm007 said:
Maybe you need an updated fastboot files?
Click to expand...
Click to collapse
I've tried every version of fastboot I can find, on every platform. That's not the issue. I'm going to try and find a way though!

duraaraa said:
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
Click to expand...
Click to collapse
The problem is that fastboot does not allow flash very big files.
Solution is to divide file on chunks.
Unfortunately, i don'y have Mate 9.
Try this:
Code:
fastboot -S 256M system path_to_system.img
p.s. You should use actual fastboot version (SDK version)

[guide] root le x626

First, Unlock Bootloader
Install TWRP for Le X626
Download Magisk or SuperSU
Put Magisk or SuperSU in internal storage
Reboot to TWRP
Install from zip
Choose Magisk (Recommended) or SuperSU
Reboot
source : tickernel.tk

Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.

How to install TWRP for x626 according to the site the OP recommends.
From the same website, only without the adlinks. No guarantees from me, if you go through the instructions from the OP you will end up getting the same information.
– Make sure your Bootloader is Unlocked, if you don’t know how to Unlock the Bootloader then please go to here and Unlock the Bootloader of your Device.
– Download the Latest TWRP Recovery Image from https://dbr.ee/TKKC
– Reboot into Fastboot/Bootloader Mode.
– Run The Following Command from a Command Prompt in the Same Folder in which you downloaded the TWRP Recovery Image (Change twrp le x626.img to recovery.img):
fastboot flash recovery recovery.img
fastboot boot recovery.img
Click to expand...
Click to collapse

onlytanmoy said:
Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.
Click to expand...
Click to collapse
I can't, because it's have different chipset

okay, thanks for your response and clarification...cheers to that.

Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>

tomfoley said:
Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>
Click to expand...
Click to collapse
Unlock bootloader first
What rom do u use?

Hi Tickernel, and thank you for replying
I unlocked the bootloader as per Step 1 above and that completed successfully.
Moving on to Step 2 I got the recovery image following your links which led me to 'twrp le x626.img' (20MB), which I renamed to recovery.img.
There are two commands to execute in step 2, the first went ok, the second did not succeed
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse

Please see screenshot...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse

tomfoley said:
Please see screenshot...
Click to expand...
Click to collapse
Have u tried boot to recovery?
Press vol up + power

Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??

tomfoley said:
Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??
Click to expand...
Click to collapse
After you flash the twrp, then boot into recovery by pressing vol up + power
You don't need update.zip

Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.

tomfoley said:
Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.
Click to expand...
Click to collapse
I'm not suggesting to erase all your data, i'm just suggesting after you flash the twrp but don't straight go to recovery then press vol up + power. That's it

Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'

tomfoley said:
Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'
Click to expand...
Click to collapse
Command 'fastboot boot recovery.img' is going boot to twrp. If you fail to do that, then just press vol up + power

Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !

tomfoley said:
Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !
Click to expand...
Click to collapse
Yeah, you're welcome

Don't suppose kingroot or similar works? I'm very lazy lol

I also have this problem were it fails in "fastboot boot recovery.img" but not in commanding "fastboot flash recovery recovery.img"
what to do?? :crying:
thanks for the help

Unable to unlock bootloader on my Asus Zenfone Max Pro M1

So, I bought a new Asus Zenfone Max Pro M1 3 GB variant today. I was really excited for it to arrive. Obviously, I wanted to install custom recovery and flash magisk on it. However, now that I'm trying to unlock the bootloader, I'm getting a message saying 'Press any key to shutdown.' What might be the problem guys? I've installed all the drivers and my OS is Windows 10 64bit with an AMD Ryzen CPU.
Help would be greatly appreciated.

Utsav_vats said:
So, I bought a new Asus Zenfone Max Pro M1 3 GB variant today. I was really excited for it to arrive. Obviously, I wanted to install custom recovery and flash magisk on it. However, now that I'm trying to unlock the bootloader, I'm getting a message saying 'Press any key to shutdown.' What might be the problem guys? I've installed all the drivers and my OS is Windows 10 64bit with an AMD Ryzen CPU.
Help would be greatly appreciated.
Click to expand...
Click to collapse
Try launching from your C drive

jide1 said:
Try launching from your C drive
Click to expand...
Click to collapse
I am launching it from my C drive. I have unlocked the BL successfully but I am unable to flash any recovery or anything now.

Utsav_vats said:
I am launching it from my C drive. I have unlocked the BL successfully but I am unable to flash any recovery or anything now.
Click to expand...
Click to collapse
Initially you said u were not able to unlock, so after unlocking why can't u flash recovery, what exactly is the issue, can u be more specific ?

jide1 said:
Initially you said u were not able to unlock, so after unlocking why can't u flash recovery, what exactly is the issue, can u be more specific ?
Click to expand...
Click to collapse
I unlocked the bootloader successfully. But now that I'm trying to flash recovery it shows error saying target didn't report max-download-size.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Utsav_vats said:
I unlocked the bootloader successfully. But now that I'm trying to flash recovery it shows error saying target didn't report max-download-size.
Click to expand...
Click to collapse
To flash recovery do the following.
Fasboot devices. (your serial number will show up)
Fastboot flash recovery ( after this command hit the space key on keyboard, then drag the .img file to the command window and hit the enter key on keyboard)

jide1 said:
To flash recovery do the following.
Fasboot devices. (your serial number will show up)
Fastboot flash recovery ( after this command hit the space key on keyboard, then drag the .img file to the command window and hit the enter key on keyboard)
Click to expand...
Click to collapse
PS C:\unlock> .\fastboot flash recovery C:\unlock\recovery.img
target didn't report max-download-size
sending 'recovery' (60364 KB)...
FAILED (command write failed (No error))
finished. total time: 0.002s

Utsav_vats said:
PS C:\unlock> .\fastboot flash recovery C:\unlock\recovery.img
target didn't report max-download-size
sending 'recovery' (60364 KB)...
FAILED (command write failed (No error))
finished. total time: 0.002s
Click to expand...
Click to collapse
Try putting the recovery.img file on desktop.

jide1 said:
Try putting the recovery.img file on desktop.
Click to expand...
Click to collapse
Okay

Utsav_vats said:
Okay
Click to expand...
Click to collapse
Thanks Sir. It worked

jide1 said:
Try putting the recovery.img file on desktop.
Click to expand...
Click to collapse
C:\adb>fastboot devices
J8AAGF056032PP7 fastboot
C:\adb>fastboot flash recovery C:\adb\twrp-3.2.2-1-20180727-X00TD.img
sending 'recovery' (58328 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
And then the phone asked me to press any key to shut down.
---------- Post added at 06:27 AM ---------- Previous post was at 06:24 AM ----------
jide1 said:
Try putting the recovery.img file on desktop.
Click to expand...
Click to collapse
This is what happened when I added the file from desktop
C:\adb>Fastboot flash recovery C:\Users\Bubai\Desktop\twrp-3.2.2-1-20180727-X00T
D.img
sending 'recovery' (58328 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.002s
My max pro m1 is 6 gb variant. Any help?

Utsav_vats said:
So, I bought a new Asus Zenfone Max Pro M1 3 GB variant today. I was really excited for it to arrive. Obviously, I wanted to install custom recovery and flash magisk on it. However, now that I'm trying to unlock the bootloader, I'm getting a message saying 'Press any key to shutdown.' What might be the problem guys? I've installed all the drivers and my OS is Windows 10 64bit with an AMD Ryzen CPU.
Help would be greatly appreciated.
Click to expand...
Click to collapse
Use windows 7. work 100%. I have same issue .that problem solved

Utsav_vats said:
I unlocked the bootloader successfully. But now that I'm trying to flash recovery it shows error saying target didn't report max-download-size.
Click to expand...
Click to collapse
How did you unlock bro? I have 4gb variant and I am having the same issue.
---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------
razisafe said:
Use windows 7. work 100%. I have same issue .that problem solved
Click to expand...
Click to collapse
I have windows 10. Same problem as the OP.

jide1 said:
Try launching from your C drive
Click to expand...
Click to collapse
I am trying, but could not unlock bootloader, please help.

Pran K. said:
C:\adb>fastboot devices
J8AAGF056032PP7 fastboot
C:\adb>fastboot flash recovery C:\adb\twrp-3.2.2-1-20180727-X00TD.img
sending 'recovery' (58328 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
And then the phone asked me to press any key to shut down.
---------- Post added at 06:27 AM ---------- Previous post was at 06:24 AM ----------
This is what happened when I added the file from desktop
C:\adb>Fastboot flash recovery C:\Users\Bubai\Desktop\twrp-3.2.2-1-20180727-X00T
D.img
sending 'recovery' (58328 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.002s
My max pro m1 is 6 gb variant. Any help?
Click to expand...
Click to collapse
Yeah i have same problem, too. Also have the 6gb variant.

Wmateria said:
Yeah i have same problem, too. Also have the 6gb variant.
Click to expand...
Click to collapse
i have same problem with you, i have the 4/64 devices, i try to flashboot in windows 10.. everytimes i found that FAILED (command write failed (Invalid argument). can anybody give a suggestion to solve this problem?

baikhaqi said:
i have same problem with you, i have the 4/64 devices, i try to flashboot in windows 10.. everytimes i found that FAILED (command write failed (Invalid argument). can anybody give a suggestion to solve this problem?
Click to expand...
Click to collapse
Have you tried with a USB 2.0 adapter? That should solve the problem.

Pran K. said:
C:\adb>fastboot devices
J8AAGF056032PP7 fastboot
C:\adb>fastboot flash recovery C:\adb\twrp-3.2.2-1-20180727-X00TD.img
sending 'recovery' (58328 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
And then the phone asked me to press any key to shut down.
---------- Post added at 06:27 AM ---------- Previous post was at 06:24 AM ----------
This is what happened when I added the file from desktop
C:\adb>Fastboot flash recovery C:\Users\Bubai\Desktop\twrp-3.2.2-1-20180727-X00T
D.img
sending 'recovery' (58328 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.002s
My max pro m1 is 6 gb variant. Any help?
Click to expand...
Click to collapse
Use usb 2.0 port and windows 7
---------- Post added at 06:26 PM ---------- Previous post was at 06:22 PM ----------
Wmateria said:
Yeah i have same problem, too. Also have the 6gb variant.
Click to expand...
Click to collapse
I also have 6gb variant. Try using usb 2.0 port and windows 7/ linux.
I installed linux on my old laptop (this also worked for some users) and instead of installing windows 7 (bc i know i will run into drivers issues) i installed linux mint.

Try following my guide here. If it didnt work, post your problem there and I will see what I can do

[T-Mobile] Enable dual SIM OOS 13 or COS 13

1. Download F10 abl.img
2. Reboot to fastboot and flash F10 abl
adb reboot fastboot
fastboot flash abl abl.img
3.. Reboot fastboot reboot and you can use dual SIM.

Worked like a charm!

I am running OOS13 KB2003 converted from T-Mobile
I got:
FAILED (remote: 'Flashing is not allowed for Critical Partitions.')
running
Code:
fastboot flash abl abl.img
I tried to run
Code:
fastboot flashing unlock_critical
But got :
FAILED (remote: ' Device already : unlocked!')
Is there a work around?
Thanks in advance!

Stylishly said:
I am running OOS13 KB2003 converted from T-Mobile
I got:
FAILED (remote: 'Flashing is not allowed for Critical Partitions.')
running
Code:
fastboot flash abl abl.img
I tried to run
Code:
fastboot flashing unlock_critical
But got :
FAILED (remote: ' Device already : unlocked!')
Is there a work around?
Thanks in advance!
Click to expand...
Click to collapse
As far as i remember, you need to be in fastbootd to flash critical partitions.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
fastboot reboot fastboot
fastboot flash abl abl.img

Does this require bootloader unlock? Would someone be able to provide more step by step confirmation on this? Also what does the updated abl.img do in order to enable dual-sim?

raven911 said:
Also what does the updated abl.img do in order to enable dual-sim?
Click to expand...
Click to collapse
It's taken from OOS13 F.10 beta release, where sim-lock is not present.

C:\adb>fastboot flash abl abl.img
target reported max download size of 268435456 bytes
sending 'abl' (220 KB)...
OKAY [ 0.009s]
writing 'abl'...
FAILED (remote: No such file or directory)
finished. total time: 0.014s
try on op 8t t mobile original firmware kb2007_11_F46 not working on it

Can you flash this in custom recovery like Orange Fox?

amine tenes said:
C:\adb>fastboot flash abl abl.img
target reported max download size of 268435456 bytes
sending 'abl' (220 KB)...
OKAY [ 0.009s]
writing 'abl'...
FAILED (remote: No such file or directory)
finished. total time: 0.014s
try on op 8t t mobile original firmware kb2007_11_F46 not working on it
Click to expand...
Click to collapse
You forgot to reboot to fastbootd.
Code:
fastboot reboot fastboot

kevinco1 said:
Can you flash this in custom recovery like Orange Fox?
Click to expand...
Click to collapse
As far as i remember in recovery you can flash .img to boot or recovery partition directly.
So you'll have to pack in update.zip where in script it will be specified which partition should abl.img be flashed to.

Excellent! Thanks Jookean !
Now my (originally) TMo 8T has been converted to a dual SIM KB2003 that works better (in the US) than my old (dual IMEI) KB2003 that I hard bricked (in FastbootD) trying to get an A12 OTA working right.
I rarely got 5G indicated on my Euro original, but now mostly 4G and low-ish signal strength issues are history! No longer being tied to T-Mobile's software updates and being able to have 5G options on my device from Verizon and Tmobile was my goal.
My eBay bargain Pixel 6 Pro will have to wait a while longer. I prefer flat screens and lighter devices. Guessing Oneplus anticipated fumbling of Android 14 may entice me to switch. Wish it had two physical SIM slots.