Sending 'unlock' (1 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
it shows this when i want to unlock
Please don't post the same thing in multiple threads.
I assume you're using the WTF instructions? If so, read further down the instructions as this issue has many troubleshooting steps already detailed. In most cases, this failure is due to a newer computer... older computers seem to work better for this unlock process. Specifically, newer Ryzen computers tend to have this problem due to an issue with the USB drivers in them.
Related
I recently had my Evo 3D replaced by HTC. Here's the error I get when attempting to unlock the device:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.160s
I've tried it many times, rebooted my computer, rebooted the phone, gotten the unlock token and unlock_code.bin about a dozen times to no avail. I believe the problem occurs due to a mismatch in the IMEI/serial of the replacement motherboard. I've searched for workarounds to this problem, but haven't found anything applicable to the Evo 3D. Here's a similar thread for the HTC Sensation. My understanding is that if there's a temporary root, I could use the jbear wire trick and get S-OFF; is anyone familiar with a solution applicable to the Evo 3D?
I came across this thread as well and ramjet73 suggests there isn't a workaround (special thanks to ramjet for his contribution to the community, you've been a great help as I've spent hours reading through these forums). He recommends contacting HTC support. Unfortunately, from what I've read from of others with this problem on other devices, HTC support is of no help...sending them in circles. If this is my only option, I'll give it a shot, but I'm curious if there's a temporary root available that I've overlooked or an alternative solution to work around this issue.
Thanks.
Unfortunately, I do not know of any method of gaining temp root. As you have stated before. I know that temp root only works when the phone is on and disappears when you turn off your phone. I believe your phone has to be in fastboot to do the wire trick so that defeats the whole purpose to begin with. My suggestion to you, if you have insurance on your phone is to "accidently" drop your phone a few times until it don't work no more and get a replacement from asurion. Hopefully if you go this route the phone you get will not have a motherboard replaced in it. Retry the unlock method then. Hopefully that works for you. All in all its only a one day wait if you do this on a weekday. Sorry I couldn't help you out in another way you intended for.
I just bought a Redmi 3S and I am not fond of the software. So I want to root it and put CM on it.
So I am trying to do like this guy: http://forum.xda-developers.com/showpost.php?p=66990194&postcount=36
but I cannot get the USB / adb to work. When I connect it to my computer a folder called "RedmI 3S" pops up but I cannot copy any files to it and I cannot see the device from adb. I tried to install the Mi PC suite but it says to update my device before connecting (which seems to be a bug in the suite: http://en.miui.com/forum.php?mod=viewthread&tid=96111&highlight=update+your+device+before+connecting)
I tried to click settings->about phone->build no 7 times but cannot get it into developer mode
So, can anyone please give me a step by step guide on how to root my Redmi 3S?
...and just after posting I found a tutorial on youtube
But now I am stuck on flashing twrp. It says:
fastboot.exe flash recovery twrp-3.0.2-0-ido.img
target reported max download size of 536870912 bytes
sending 'recovery' (13934 KB)...
OKAY [ 0.440s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.447s
So now my question is: how do I allow flashing?
I guess I need to unlock the device. Have created a MUI account and logged in to:
http://en.miui.com/unlock/
but everything is in chinese... Any suggestions?
Found an english page and logged in. Went back to the unlock page and requested permission to unlock my phone. Now I have to wait for 10 days for them to reply...
Others who wants to root their Redmi 3 may want to look at these videos to unlock and root:
https://www.youtube.com/watch?v=OFCig10fW9E&feature=youtu.be
https://www.youtube.com/watch?v=4Rv67v55h2w
Im on the Oct 1 security update.
I ran the Nokia unlock apt I side loaded. There app gives me a error message of device not supported.
When I got into Developer Options turn on OEM unlocking Allow the boot loader to be unlocked I still get the message Device not supported, When I run there app
I know the boot loader is still locked because when I try to flash TWRP recovery I get this message
fastboot boot twrp.img
Sending 'boot.img' (38732 KB) OKAY [ 0.902s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
So it very much seems like the boot loader is still locked.
Any suggestion thanks
raven.warsong said:
Im on the Oct 1 security update.
I ran the Nokia unlock apt I side loaded. There app gives me a error message of device not supported.
When I got into Developer Options turn on OEM unlocking Allow the boot loader to be unlocked I still get the message Device not supported, When I run there app
I know the boot loader is still locked because when I try to flash TWRP recovery I get this message
fastboot boot twrp.img
Sending 'boot.img' (38732 KB) OKAY [ 0.902s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
So it very much seems like the boot loader is still locked.
Any suggestion thanks
Click to expand...
Click to collapse
Sigh,
1. There is absolutely no official bootloader unlock for this phone.
2. Though there is no official bootloader unlock, you can still Bloader unlock your phone using a paid service by TechMesto @Singhsk ...
usernamedoesnotexist said:
Sigh,
1. There is absolutely no official bootloader unlock for this phone.
2. Though there is no official bootloader unlock, you can still Bloader unlock your phone using a paid service by TechMesto @Singhsk ...
Click to expand...
Click to collapse
I did see a tread about that thanks for the info.
my guess is its most likely not worth doing I dont see very many roms listed for the phone.
I guess its not very popular for that reason. Its a shame it seems like a nice phone. But the market is flooded with phones I dont see any thing that makes this one stand out
thanks for answer my question
raven.warsong said:
I did see a tread about that thanks for the info.
my guess is its most likely not worth doing I dont see very many roms listed for the phone.
I guess its not very popular for that reason. Its a shame it seems like a nice phone. But the market is flooded with phones I dont see any thing that makes this one stand out
thanks for answer my question
Click to expand...
Click to collapse
Yeah, not much dev for this device. Probably because of no official bootloader unlocks and popularity of the device.
Good morning,
I'm trying to root this Huawuei Y6 II 2017 l_21 factory resetted but it's becoming very very hard, cause i've try every single method and nothing work.
The device is debug USB and OEM unlocked, and even bootloader unlocked and FRP unlock.
I've installed USB drivers on my window 7 ( and some of them didn't install correctly ).
The device connected correctly to hi suite but it's full upgraded android 6 emui 4.1.x.x Kirin620
-I've tried kingoroot both pc and apk
-I've tried Manual rooting with mini adb and fastboot plus TWRP 3.0.2 of this guide ( https://forum.xda-developers.com/android/general/rooting-huawei-y6-ii-cam-l21-t3501162 ) and TWRP 3.1.1-0
but when i'm launching the command fastboot flash recovery TWRPxxx.img it gives me that:
target reported max download size of 471859200 bytes
sending 'recovery' (25152 KB)...
OKAY [ 0.736s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.743s
Actually i've asked for a new unlock bootloader code to huawuei, but i have even tried to get the code with dc-unlocker following this guide ( https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code ) and even in this case my PC didn't find the mobile phone.
So Actually i have 2 major issues:
1) Why i got the error in ADB ?
2) why my pc even with USb drivers didn't find correctly the device in order to let dc unlocker find the bootloader code?
My objective is to root the Phone and recover deleted data by factory reset, but i don't know what to do now.
help!
jackielong said:
Good morning,
I'm trying to root this Huawuei Y6 II 2017 l_21 factory resetted but it's becoming very very hard, cause i've try every single method and nothing work.
...
1) Why i got the error in ADB ?
2) why my pc even with USb drivers didn't find correctly the device in order to let dc unlocker find the bootloader code?
My objective is to root the Phone and recover deleted data by factory reset, but i don't know what to do now.
help!
Click to expand...
Click to collapse
This is weird to me, because the error message in fastboot it what you get when you've not unlocked the bootloader (allowed to read, not write).
And the fact that fastboot and ADB recognized your device means that on the USB drivers side, you've a correction set up...
So I'd say that the bootloader isn't unlock at first glance. And unfortunately I don't know any ways of unlocking Huawei phones now...
I didn't know DC unlocker and I can't certify if this software is legit or not, nor provide you help regarding the software.
So I don't think you'll be able to successfully root your device. But that's just what I think, maybe someone more experienced will find the solution.
Have a good day
Even if one finds a TWRP image that at 100% matches his/her device, it's not a good idea to flash it: instead boot into it
Code:
fastboot boot twrp.img
BTW: Doing so has the additional advantage that TWRP doesn't get detected.
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11. Many guides online seem to gloss over needing the bootloader unlocked before root. TMALSS; I'm not sure if the non-international version can be bootloader unlocked and/or if I can root without needing this. Long version of what I've tried is below:
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Thus to unlock the bootloader, I am following a guide from TWRPupdate:
It says to perform 'adb reboot bootloader' and then 'fastboot oem device-id':
Code:
C:\adb-platform-tools>fastboot device-id
fastboot: usage: unknown command device-id
My phone only reboots into normal mode whenever running reboot bootloader command within ADB.
I can run fastboot commands when I run 'adb reboot fastmode' but I don't believe this is true fastmode. As I have tried everything mentioned here, such as cables or different computers. Essentially most fastboot commands I've tried do not work except for showing my device as listed / connected.
I have also tried the drivers from LG / Google / ADB separately. And on 2 computers.
Is it possible that I don't have rescue mode or a bootloader still? As I get a black screen when entering recovery mode (but my computer recognizes A device), but adb nor fastboot does. I used to see the recovery screen logo, but I stopped seeing this screen either after updating to Android V11 or reading/backing-up the partitions in QFIL.
In last resort, I have tried rooting via patching the boot image using Magisk v23. I downloaded the firmware for my carrier, converted the KDZ to DZ via Python, and extracted the boot.img_117638 file. Given the file is 0 bytes with nothing in text edit, I still converted it to an img file. But in the kdztools android app, when I select this image file and run, I get:
Code:
!Invalid input file
!Installation failed
I'm guessing the boot.img file should have some data in it. But I'm not sure this method would even work due to the fastboot issues, especially with 'download to device' errors.
-------
I'm just at a standstill on what to even try next. I don't see many people having this much trouble unlocking/rooting their v60. Did the OTA Android v.11 break the root-ability?!
PS: Debugging and OEM unlock are both set in developer options. I can also list drivers used if need.
Thanks for the help in advance!
While digging I also found a post by alexenferman whom managed to use QFIL to root many older ZTE smartphones. They state it may but likely won't work on newer flagship phones. It's a great tutorial I'll have to try soon, but is there a reason it likely won't work here?
kyij said:
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11.
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
NGOwner said:
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
Click to expand...
Click to collapse
Haha, I remember reading that and still continued
I am on Verizon myself using this TM model. I know the phone was unlocked to the point where I could use it with Verizon. I even got 5g using my old 4g sim card.
Anyhow.. I have tried using that command already, and get the same 'command not supported issue'.
Code:
C:\adb-platform-tools>fastboot devices
LMV600TMc40cxxxx fastboot
C:\adb-platform-tools>fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Again have tried different computers and cables as I've read fastboot can be pretty picky too.
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
NGOwner said:
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
Click to expand...
Click to collapse
Yes I do, I have turned it off and back on as well.
Well then at this point, I'm tapped out. Smarter folks than me will need to step in and take up the mantle.
[NG]Owner
I ended up posting a form to reddit where about 10 people insisted I did something wrong, and with little surprise -- I did.
I did not flash the engineering bootloader after saving a copy.
Makes a lot more sense since it seemed like a lot of steps to backup without actually doing anything
Thanks NG for the help too!
are you success to unlock bootloader yet. if no i will show you
adb reboot fastboot> select reboot bootloader on your phone> fastboot oem unlock