Hello guys can you help me, i cant unlock the bootloader of HTC Desire 10 PRO cos the command "fastboot flash unlocktoken Unlock_code.bin" is not working getting this message below again n again. i have checked usb debugging & OEM Unlock options too in Developer options too. i really don't understand why is this happening. Also there is not much help from this device available here on XDA or other sites too.
M:\HTCRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.042s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.132s
need help guys..
here is more info if required.... guys plz help
C:\Users\Desktop\platform-tools>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC73XZ9*****
(bootloader) current-slot:
(bootloader) imei: 35**520********
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA10000
(bootloader) cid: HTC__060
all:
finished. total time: 0.037s
Same error here. Tried Desire* and other supported devices from the HTCdev site.
Kindly help which device to choose from dev site.
D:\HTC Desire 10 PRO\ADB-Windows> fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1602400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.009s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.033s
princepavs said:
Hello guys can you help me, i cant unlock the bootloader of HTC Desire 10 PRO cos the command "fastboot flash unlocktoken Unlock_code.bin" is not working getting this message below again n again. i have checked usb debugging & OEM Unlock options too in Developer options too. i really don't understand why is this happening. Also there is not much help from this device available here on XDA or other sites too.
M:\HTCRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.042s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.132s
need help guys..
Click to expand...
Click to collapse
Are you still able to unlock? I have the same issue too. Stuck here
I don't know if this one helps you too but I was unable to unlock bootloader from bootloader mode and I tried it from download mode. It was successfully done with fastboot.... command. Root? I used Magisk. only problem is it takes 5 minutes to start up every time I reboot.
carlochiefsg said:
Are you still able to unlock? I have the same issue too. Stuck here
Click to expand...
Click to collapse
naaa never worked.. so gave this phone to my dad as he's a normal android user... must say MTK processors r the worst
princepavs said:
naaa never worked.. so gave this phone to my dad as he's a normal android user... must say MTK processors r the worst
Click to expand...
Click to collapse
to be exact HTC MTK processor is the worst, HTC lied about all HTC phones boot loader is unlockable.... BS!
Related
Hey folks,
I already searched on XDA and the web, but found nothing helpful, so I decided to start an new thread:
I got my new ONE X PLUS just a few weeks ago and now I wanted to start with unlocking the bootloader and rooting it.
I already got some experience in unlocking, rooting and flashing with an HTC Incredible S and SE Xperia X8.
Prerequisites my Computer(win7 x64) fulfills:
Latest Android SDK installed
HTC Divers installed
Folder on HDD: C:\android\onexplus containing all necessary files.
So I followed all the steps on htcdev.com like I did with my Incredible S.
I´ve got my Unlock_Code.bin and wanted to flash that on my ONE X+.
So I executed
Code:
fastboot flash unlocktoken Unlock_code.bin
prompted the dialog on the phone with "YES" and got:
Code:
C:\android\onexplus>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.126s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Unknown error))
finished. total time: 49.707s
When I boot into bootloader again, it displays "unlocked" (see attached picture),although fastboot displayed an error.
So I tried to root it via rootboot, like mentioned in a whole lot of tutorials.
This is, what rootboot.bat returns to me:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
mount: Operation not permitted
failed to copy 'Tools/su' to '/system/xbin/su': Read-only file system
failed to copy 'Tools/Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Press Enter
That seems to me like unlocking has failed and the phone is still locked.
When I want to lock it again via
Code:
fastboot oem lock
, fastboot displays the same error, but the bootloader again says locked!
Problem sources that I kicked out already:
Changed USB Cable and Port
Phone was always charged at least 90%
Reinstalled latest HTC Drivers and Android SDK & restarted the PC
Submitted my OEM_Identifier_Toeken again and got a new Unlock_Code.bin
Deleted all my old Files from rooting and flashing the IncS & X8
got a new folder (C:\android\onexplus) with all necessary files
Tested whole procedure also on a x64 Linux Box(latest Archlinux release): Same result: fastboot displays error code, but the Bootloader says "UNLOCKED". Interesting fact: The error on linux differs from the one on windows:
Code:
[email protected]:~/android: sudo ./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... INFOunlock token check successfully
FAILED (status read failed (Cannot send after transport endpoint shutdown))
I am at my wit's end, obviously I did something wrong, but what ? Or is the device correctly unlocked and I just failed on rooting it ?
Is there another way to check if the device is correctly unlocked?
I don´t know if it´s useful, but here´s the result of "fastboot getvar all":
Code:
C:\android\onexplus>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.35.0000
(bootloader) version-baseband: 3.1204.168.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.17.401.1
(bootloader) serialno: FA2BRW103800
(bootloader) imei: 353567051431246
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3817mV
(bootloader) devpower: 48
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.448s
Thanks in advance for your answers
Roman
Attached Pictures:
-HTC ONE X + Incredible S in HBOOT (to compare)
-HTC ONE X + in FASTBOOT USB
After reinstalling the whole HTC Drivers and software pack, to have a clean base; Now I encounter another error when I execute
Code:
fastboot flash unlocktoken Unlock_code.bin
This time fastboot reports the following error:
Code:
C:\android\onexplus>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.078s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 41.211s
And also the lock command gives me:
Code:
C:\android\onexplus>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.104s
Another thought: Could this be a problem with the bootloader and fixed by installing an new RUU by HTC ?
And, like mentioned above, is there any way to check if the device was unlocked correctly ?
TIA
Roman
leuprechtroman said:
After reinstalling the whole HTC Drivers and software pack, to have a clean base; Now I encounter another error when I execute
Code:
fastboot flash unlocktoken Unlock_code.bin
This time fastboot reports the following error:
Code:
C:\android\onexplus>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.078s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 41.211s
And also the lock command gives me:
Code:
C:\android\onexplus>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.104s
Another thought: Could this be a problem with the bootloader and fixed by installing an new RUU by HTC ?
And, like mentioned above, is there any way to check if the device was unlocked correctly ?
TIA
Roman
Click to expand...
Click to collapse
I'm no expert but on the past 4 HTC phones I've unlocked and the several I have unlocked for friends this error with "to many links" always comes up and says failed. It has never stopped any device I have from functioning.
Kraizk said:
I'm no expert but on the past 4 HTC phones I've unlocked and the several I have unlocked for friends this error with "to many links" always comes up and says failed. It has never stopped any device I have from functioning.
Click to expand...
Click to collapse
Thanks a lot man :good:
TIA
PS: Edited, I really missed the forest for the trees
The too many links error, is usually cause you have more than one android device connected, or running the android emulator.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
The too many links error, is usually cause you have more than one android device connected, or running the android emulator.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Never had more than one plugged in and never had emulator running. Either way it sounds fixed.
Absolutely fixed
Thanks a lot for the tips you two, great job! :good:
HOX+ running perfectly rooted.
Thank you
Roman
I see a little old but how did you fix this issue leuprechtroman? I am running into the same type of error.
Yes, I'd like to know too what was the way out of this?
leuprechtroman said:
Absolutely fixed
Thanks a lot for the tips you two, great job! :good:
HOX+ running perfectly rooted.
Thank you
Roman
Click to expand...
Click to collapse
Hey bro how can u fix this problem same error taken ..
Hi,
Unlocked my wife's Legend using the HTC-Dev method. Installed CM7 and she was happy... Now she is missing the HTC weather animations and wants to go back to the stock Froyo.
I have the correct RUU for her phone, carrier, and region, extracted from:
RUU_Legend_BellMobility_WWE_2.02.666.3_Radio_47.37.35.09_7.08.35.05_release_130094_signed.exe
First I tried to flash by renaming the rom.zip to LEGEIMG.zip. The bootloader saw it and chewed on it for a while, but the RUU ended up not being applied and the phone booted back into CM. Confusing.
Next attempt: fastboot, with bootloader unlocked.
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.795s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
[B]FAILED (remote: 99 unknown fail)[/B]
finished. total time: 18.643s
Did some more reading, found that RUUs only apply when the bootloader is locked. So I relocked the bootloader with fastboot oem lock and tried again:
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
< waiting for device >
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.874s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
[B]FAILED (remote: 43 main version check fail)[/B]
finished. total time: 44.062s
And trying the LEGEIMG.zip method after relocking:
Code:
Main version is older!
Update Fail!
Do you want to reboot device?
Here are my bootvars:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0000
(bootloader) version-baseband: 7.13.35.13
(bootloader) version-cpld: None
(bootloader) version-microp: 0816
(bootloader) version-main: 3.30.0.0
(bootloader) serialno: HT05NRA07XX
(bootloader) imei: XXXXX
(bootloader) product: legend
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PB7611000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-39ec9098
(bootloader) hbootpreupdate: 11
Apparently this means that I'm trying to flash an RUU that is older than what is on the device. The problem is, the RUU update that I last applied was the HTCDev one to allow unlocking. So the most recent "full" RUU is older than the HTCDev RUU and I can't seem to downgrade.
Am I missing something? I must be missing something. Please help, or the wife will have one up on me. Can't allow that
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
When I remember right, there was no version check during installation, you can install it with Clockwork mode Recovery.
alligator_asl said:
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
Click to expand...
Click to collapse
Thanks, that's an acceptable workaround for now. I ended up going this route. Since CWM 5.X doesn't like "amend" scripting, it took some doing though. :highfive:
If anyone knows of a way to downgrade to a stock RUU after applying the HBOOT 1.02 RUU to the Legend, that would be a help.
I'd suggest if you really need to go back stock froyo it can't be done with hboot 1.02, I have tried various different methods with no success.
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Sent from my Legend using xda app-developers app
ranger4740 said:
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Click to expand...
Click to collapse
Yeah, that sounds right.
So for anyone reading this thread in the future, if you've unlocked your bootloader using HTC-dev you will be unable to return to stock Froyo using an official RUU without first downgrading to HBOOT 1.01 or older.
The HBOOT downgrade process is pretty involved. You need a goldcard and the hack4legend kit. See this thread for details.
And for good measure, here's a thread with someone else working out the same problem we just worked out here... :silly:
At the end of the day, if you ran a nandroid backup of your stock ROM before blowing it away, you won't need all this jazz.
ariaxu said:
Since CWM 5.X doesn't like "amend" scripting, it took some doing though.
Click to expand...
Click to collapse
You can take an older Versin of CWM ( recovery-clockwork-2.5.0.7-legend.zip ), ther are no problems with scripting, a google search brings several results.
If necessary, you lan load the old version of CWM from the new version and then you can flash this ROM !
Hi all,
Excuse my poor english.
I want to upgarde my firmware with 1.17.401.3.zip and I have no Wifi, no signal, nothing.
I try to swipe all and I want install (I think) the true firmware: 1.17.401.1.zip
At this time, I have nothing, no system and I cannot boot.
I have access at recovery TWRP, I can send files with adb push and that's it.
I'm blocked now. I want to install the firmware 1.17.401.1.zip with
Code:
fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.101s
D:\HTC One X+>fastboot oem rebootRUU
...
(bootloader) Save data from original MSC...
(bootloader) Save data from SIF...
(bootloader) Update partition data to SIF partition
(bootloader) Update partition data from original MSC...
(bootloader) [MSG] OKAY
OKAY [ 0.193s]
finished. total time: 0.194s
D:\HTC One X+>fastboot flash zip firmware.zip
sending 'zip' (13262 KB)...
OKAY [ 1.658s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
[B]FAILED (remote: 43 main version check fail)[/B]
finished. total time: 2.600s
D:\HTC One X+>fastboot reboot
I receive "FAILED (remote: 43 main version check fail".
Do you have a solution for me ?
Thanks a lot.
Jack
Hi to all, thank you for your support there is a lot of information of Android system is this forum, I need help.
I just buy a HTC M9 and I'm trying to unlock the bootloader but i can't, I recive this message in CMD
C:\Users\Kevin\AppData\Local\Android\android-sdk\platform-tools>fastboot flash u
nlocktoken Unlock_code.bin
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.013s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.118s[/B][/B][/B]
And the download mode change
Says 100% and don't do anything does not show the image of HTC DEV Unlock bootloader?
Could you help me please, thanks in advance.
Hi,
I have XT1635-03, when i try to unlock bootloader got following message
fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found ...
(bootloader) Unlock data:
(bootloader) cid_get_cid_data: Version 0 datablock
(bootloader) Failed OKAY [ 0.012s] finished. total time: 0.014s
How to fix it? want to install custom rom, its chinese set without playstore, tried couple of methods to install
playstore put also they fail. any help plz?
thx
XT 1635-03 is a moto z play. Better ask in the moto z play forum.
kami2k said:
Hi,
I have XT1635-03, when i try to unlock bootloader got following message
fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found ...
(bootloader) Unlock data:
(bootloader) cid_get_cid_data: Version 0 datablock
(bootloader) Failed OKAY [ 0.012s] finished. total time: 0.014s
How to fix it? want to install custom rom, its chinese set without playstore, tried couple of methods to install
playstore put also they fail. any help plz?
thx
Click to expand...
Click to collapse
Man, if your 1635-03 are from Gearbest or Banggod - it`s already with unlocked BL.
Just run
"fastboot oem get_unlock_data "
twice ))