I am running into the following error during the final step of unlocking the bootloader by entering 'fastboot flash unlocktoken Unlock_code.bin' :
Code:
target reported max download size of 1826414592 bytes
error: cannot load 'Unlock_code.bin': No error
The bin file is 256 bytes in case anyone is wondering. I have tried unlocking the bootloader on OS X as well but 'permission denied' is the result when attempting the same action. I also swapped two different USB cables and different ports on my MacBook Pro to see if it made a difference.
This is the method I followed to unlock in Windows 7 and this is what I followed for OS X.
Does anyone know of a solution or alternative method around this?
Thanks in advance, guys.
Related
I am trying to restore my Kindle HD to version 7.2.3 using Windows XP and when executing the fastboot command to flash the system.img I get the following error:
Code:
C:\temp\KFHD_SRT_v1.2.3>fastboot -i 0x1940 flash system system.img
load_file: could not allocate 929038336 bytes
error: cannot load 'system.img'
The system.img file is in the same directory as the fastboot.exe.
I get my Kindle into fastboot mode using a factory cable and to verify fastboot I get the product and it returnsTATE-PVT-08. I have checked the max-download-size and I get
Code:
max-download-size: 1006632960
finished. total time: 0.000s
i have tried flashing with both the factory cable and the regular USB cable and I keep getting the same error. Any thoughts on what the error means?
rjgonzalez73 said:
I am trying to restore my Kindle HD to version 7.2.3 using Windows XP and when executing the fastboot command to flash the system.img I get the following error:
Code:
C:\temp\KFHD_SRT_v1.2.3>fastboot -i 0x1940 flash system system.img
load_file: could not allocate 929038336 bytes
error: cannot load 'system.img'
The system.img file is in the same directory as the fastboot.exe.
I get my Kindle into fastboot mode using a factory cable and to verify fastboot I get the product and it returnsTATE-PVT-08. I have checked the max-download-size and I get
Code:
max-download-size: 1006632960
finished. total time: 0.000s
i have tried flashing with both the factory cable and the regular USB cable and I keep getting the same error. Any thoughts on what the error means?
Click to expand...
Click to collapse
There was another user a while back with the same problem, but I could never figure out why. Your system image is obviously smaller than the max-download size, so it doesn't make much sense to me.
From my perspective, if you can't get it to work, I would think you can (theoretically) boot into TWRP using the method found by Powerpoint45 and that would give you access to the adb shell so you can 'dd' the system image in place. I don't have an HD so I can't confirm that it will work, but I can't see any reason why it wouldn't.
That being said, I suggest you don't even attempt it unless you know exactly what you are doing.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
There was another user a while back with the same problem, but I could never figure out why. Your system image is obviously smaller than the max-download size, so it doesn't make much sense to me.
From my perspective, if you can't get it to work, I would think you can (theoretically) boot into TWRP using the method found by Powerpoint45 and that would give you access to the adb shell so you can 'dd' the system image in place. I don't have an HD so I can't confirm that it will work, but I can't see any reason why it wouldn't.
That being said, I suggest you don't even attempt it unless you know exactly what you are doing.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
I noticed there was an error in the command I copied and pasted. The 0x1940 should be 0x1949, however I still get the same error message. I am of the opinion it is an issue with the computer I am using. I will try with a computer with Windows 7 and see if I have better results.
UPDATE: It was an issue with my XP machine. I was able to flash the system.img using a Windows 7 machine and was able to downgrade to version 7.2.1.
rjgonzalez73 said:
I noticed there was an error in the command I copied and pasted. The 0x1940 should be 0x1949, however I still get the same error message. I am of the opinion it is an issue with the computer I am using. I will try with a computer with Windows 7 and see if I have better results.
UPDATE: It was an issue with my XP machine. I was able to flash the system.img using a Windows 7 machine and was able to downgrade to version 7.2.1.
Click to expand...
Click to collapse
Sorry to revive this thread, but I'm having the same issue and I'm a little desperate.
I'm running a Vista, as are all the computers in my household.
Hi, I got my HTC ONE yesterday and then I tried to unlock it on htc dev, I've installed the latest driver, but when I tried to get the identifier token, I got some problems..
Each time I run de command "fastboot oem get_identifier_token", I got a different token, I've copied every of them to the htcdev, but I got always the same error code:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
I've already checked what i've copied before submit,and made sure nothing more nor less..
So I wanna know if anyone has had the same problem? Anyone can help?
Thanks a lot
Check for leading or trailing space.
BenPope said:
Check for leading or trailing space.
Click to expand...
Click to collapse
checked, no space copied, and each time I run the command, I got a different token, is that normal??
ooxx said:
checked, no space copied, and each time I run the command, I got a different token, is that normal??
Click to expand...
Click to collapse
Yes, token changes every time, but once you receive Unlock_code.bin it can be used to unlock the same device many times (for example, after RUU to restore stock.)
No leading or trailing spaces, but include the token start and end lines:
Code:
<<<< Identifier Token Start >>>>
7CD5230E7C3E1ED5C132386E2C149626
1CA8294D666F66DB62FBB7DF18F0EAEE
4155FC51878338C8696401BEA9D76B2D
9DDB85BD5B7354AEC86B8F2D2DBBE2BF
FC17595FA5EA04F407AA484D58344663
28DF4BD7D545D5C68DF8CC2C617359E9
22F71FB57496DA100D7702315A8FFF99
ADC4063E7F5936CF3F58A0436F9615B2
027C3D6A4B40CB654043DF04D1EDB8F5
D10F80AA7D6E043666DC1B9658716902
E61C3187D5A90AD36F937D93934FC3F7
9276C03177F0965AFB88DF9E1A0FF032
1D5E38A3E7AAB6E9FA1447D0731DA115
726321DDAFA0D60A7255E58E30A22144
0BCF85A964A865D7E037D14C4705FA6D
C4519AF26EF6792717DE9CDE0CF24A81
<<<<< Identifier Token End >>>>>
cschmitt said:
Yes, token changes every time, but once you receive Unlock_code.bin it can be used to unlock the same device many times (for example, after RUU to restore stock.)
No leading or trailing spaces, but include the token start and end lines:
Code:
<<<< Identifier Token Start >>>>
7CD5230E7C3E1ED5C132386E2C149626
1CA8294D666F66DB62FBB7DF18F0EAEE
4155FC51878338C8696401BEA9D76B2D
9DDB85BD5B7354AEC86B8F2D2DBBE2BF
FC17595FA5EA04F407AA484D58344663
28DF4BD7D545D5C68DF8CC2C617359E9
22F71FB57496DA100D7702315A8FFF99
ADC4063E7F5936CF3F58A0436F9615B2
027C3D6A4B40CB654043DF04D1EDB8F5
D10F80AA7D6E043666DC1B9658716902
E61C3187D5A90AD36F937D93934FC3F7
9276C03177F0965AFB88DF9E1A0FF032
1D5E38A3E7AAB6E9FA1447D0731DA115
726321DDAFA0D60A7255E58E30A22144
0BCF85A964A865D7E037D14C4705FA6D
C4519AF26EF6792717DE9CDE0CF24A81
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
Thanks, I'll try again to see if today it works
People all over the XDA were facing many problems so i thought of making a tutorial on how to install the ANdroid M developer Preview on the Nexus 5.
Here's my tutorial video on the Same:
https://youtu.be/ye8ZbwlOwAo
I'd just like to add a link to this webpage - http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ because it shows the individual steps required (if you get the system.img not found error just use this).
I'm just going to start forwarding people to this thread or that link from now on... The amount of spoon-feeding required is getting out of hand around here.
Everything works except when I try to "fastboot flash system system.img" I get "target reported max download size of 1073741824 bytes error: cannot load 'system.img' ".
I worked it out. I used a different computer and it worked. (Scared me a little, I gotta say.) So, it might have been the laptop USB ports, or the ADB files, or even something else. Not sure. Great tutorials, though. Thanks guys!
I've updated to android 10 thinking it was gonna be fun but now I can't receive updates from the play store, my saftetynet is not valid (does not pass), I can't use my bank account apps and chrome cannot download any files (ending with download error)
Is there anyway to return to android 9 or am I doomed until I spend another 800$ cad?
Phone: WW_17.0210.1912.22_0
Tencent 8gb/128gb
Converted from CN to WW with guides from here
I've tried following this:
https://forum.xda-developers.com/rog-phone-2/how-to/rom-asus-rog-phone-ii-zs660kl-ww-t3971059
But get the following:
target reported max download size of 536870912 bytes
sending 'abl' (420 KB)...
OKAY [ 0.020s]
writing 'abl'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.031s
Send help
SirGoldenTaco said:
I've updated to android 10 thinking it was gonna be fun but now I can't receive updates from the play store, my saftetynet is not valid (does not pass), I can't use my bank account apps and chrome cannot download any files (ending with download error)
Is there anyway to return to android 9 or am I doomed until I spend another 800$ cad?
Phone: WW_17.0210.1912.22_0
Tencent 8gb/128gb
Converted from CN to WW with guides from here
I've tried following this:
https://forum.xda-developers.com/rog-phone-2/how-to/rom-asus-rog-phone-ii-zs660kl-ww-t3971059
But get the following:
target reported max download size of 536870912 bytes
sending 'abl' (420 KB)...
OKAY [ 0.020s]
writing 'abl'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.031s
Send help
Click to expand...
Click to collapse
If you want to go back to Android 9, flash the latest RAW
Welp it ended better than I thought, followed this guide:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042
And was saved by cyber Jesus: JazonX
Thanks for the assistance!
SirGoldenTaco said:
Welp it ended better than I thought, followed this guide:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042
And was saved by cyber Jesus: JazonX
Thanks for the assistance!
Click to expand...
Click to collapse
Hey, when you ran the flashall_AFT.cmd did it run forvere? Did you ever get a complete message or your phone to reboot? I am trying to downgrade just the same, and I cannot ever get that raw file to flash over. Now my image is corrupt and I cant boot the phone, thank goodness I made backups, but still I cannot seem to flash the phone no matter what.
MrKioFLow said:
Hey, when you ran the flashall_AFT.cmd did it run forvere? Did you ever get a complete message or your phone to reboot? I am trying to downgrade just the same, and I cannot ever get that raw file to flash over. Now my image is corrupt and I cant boot the phone, thank goodness I made backups, but still I cannot seem to flash the phone no matter what.
Click to expand...
Click to collapse
My phone was at android 10 beta when I did these steps:
Tried running the bootloader unlocker and it gave me an error (I ignored it and continued)
I activated devmode for usb debugging (tapping 5 times on build #)
Made sure I allowed my pc to use debug mode (by tapping the always allow porompt)
I already had the google drives installed
I downloaded this file (which is linked in the post)
https://drive.google.com/file/d/1Y1ey0TOWq0pW1Qid7yqy83i0TqLYgwKR/view
Extracted it on my pc desktop (anywhere in a fresh document)
Rebooted my phone in bootloader
Connected my rog 2 to my pc using the side usb (***Important to do not plug it in the bottom usb***)
Ran flashall_aft.cmd and after about 8m - 10m it rebooted, forced me to do a factory reset
Then the phone was all good
If you did all the steps above and it's still not working then sorry I'm more of a "follow guides" kinda guy so my knoledge on the matter is pretty limited
SirGoldenTaco said:
My phone was at android 10 beta when I did these steps:
Tried running the bootloader unlocker and it gave me an error (I ignored it and continued)
I activated devmode for usb debugging (tapping 5 times on build #)
Made sure I allowed my pc to use debug mode (by tapping the always allow porompt)
I already had the google drives installed
I downloaded this file (which is linked in the post)
https://drive.google.com/file/d/1Y1ey0TOWq0pW1Qid7yqy83i0TqLYgwKR/view
Extracted it on my pc desktop (anywhere in a fresh document)
Rebooted my phone in bootloader
Connected my rog 2 to my pc using the side usb (***Important to do not plug it in the bottom usb***)
Ran flashall_aft.cmd and after about 8m - 10m it rebooted, forced me to do a factory reset
Then the phone was all good
If you did all the steps above and it's still not working then sorry I'm more of a "follow guides" kinda guy so my knoledge on the matter is pretty limited
Click to expand...
Click to collapse
Thank you for your help, apparently the USB hub I was using was had horrible transfer rates, and so even in 45 minutes nothing was finished copying over. Went directly to the USB on my pc and everything ran wonderfully! Thank you again!
MrKioFLow said:
Thank you for your help, apparently the USB hub I was using was had horrible transfer rates, and so even in 45 minutes nothing was finished copying over. Went directly to the USB on my pc and everything ran wonderfully! Thank you again!
Click to expand...
Click to collapse
You should be really careful about using USB hubs, for anything flashing related or if you are transferring a file without a checksum I would highly recommend going direct to a normal USB port.
MiFlash ver: 2020.3.14.0 & 2019.12.6.0.
Latest platform-tools installed systemwide. I also tried some outdated but I got an even worse result.
Phone: Mi 9T Pro 6/64 Global with unlocked bootloader.
I softbricked my phone trying to flash a ROM but for some weird reason I can't flash MIUI on fastboot. I've tried to flash the following builds:
V12.0.1.0.QFKMIXM (downloaded from XiaomiFirmwareUpdater)
V12.0.2.0.QFKMIXM (downloaded from 3 different places: Xiaomi, XiaomiFirmwareUpdater and with XiaoMiTool V2)
I've also confirmed that the phone is indeed unlocked (that's what the MiUnlockTool tells me as you can see in the printscreen here).
The error I get is the following:
Code:
Sending sparse 'vendor' 1/2 (773888 KB) FAILED (Error reading sparse file)
Logs and printscreens here:
LOG
PRINTSCREEN
I've also tried other tools like MiFlashPro, XAFT (Xiaomi ADB / Fastboot Tools) and simply executing the script (in both Windows the .bat and Linux the .sh ) but to no success.
For Linux I used FWUL.
I also tried 4 different computers but the result was always the same. The computers where:
AMD Ryzen 1600 based (with both Linux and Windows)
AMD Ryzen 2600 based
AMD A8-7410 based (with both Linux and Windows)
Intel Core i7 3632QM based
I think I should also tell that for some reason fastboot only works if I connect a phone to a USB hub. I've tried many things but to no success. I've tried USB 2.0, USB 3.0 and USB 3.1 ports, still no success.
Only thing left is swapping the cable but as this is my first USB-C device I don't have a spare one. And I bought this phone used and it came with every factory accessory except for the cable. I'll try a new cable as soon as I can but maybe you guys know something that I don't.
On a side note, I also tried flashing manually vendor alone and got the same result. I also tried to do the same with system and got the exact same error, so I suppose it has something to do with the sparse thingy. I also tried to do fastboot flash:raw xx xx.img but instead got an allocation error.
I can provide more info if needed. All ideas are welcome.
EDIT: it was the cable all along. Have a nice day
Re down load fadtboot rom and fladh