Related
when i get to the last step on htcdev.com to unlock the bootloader. i type "fastboot flash unlocktoken Unlock_code.bin" but when i got back to my phone i dont have the disclaimer to unlock the phone. im following directions correctly and everything says on computer that it went through. any ideas??
C:\android>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ -0.000s]
finished. total time: 0.156s
i get this but nothing on my phone....
Same problem.
This is also happening to me. I unlocked my own Evo 3D with this method and had no problems, but ran into this same issue trying to unlock my son's, which he just got for Christmas. I've confirmed Hboot version is 1.5. Any help with this would be much appreciated.
*Update* Fixed!
I did some research and found the solution! I've confirmed that this works for me. Basically, you have to install the old RUU version 2.08.651.2 because something in 2.08.651.3 borks the HTC unlock. Here is the original post I found:
http://htcevohacks.com/htc-evo-3d-cheat-sheet/#comment-31513
...and here is a link to a thread with the RUU 2.08.651.2 download:
http://forum.xda-developers.com/showthread.php?t=1225737
OK this is not the answer but I can confirm that htc dev unlocking method is working perfectly for hboot 1.53.0007
Hello. I was following a video tutorial named: How To change Hboot + Install Jelly Bean on Your HTC One X - JB on HOX
at the stage where I use flash zip firmware.zip I can not get out of the bootloader. Please can someone guide me on how to recover my phone from this.
******RELOCKED*****
******Security Warning******
ENDEAVOUR PVT SHIP S-ON RL
HBOOT-0.43.0000
CPLD-None
MICROP-None
The commands are below which have lead to this disaster. Please can someone assist me. Thanks.
c:\htc>fastboot-windows.exe flash boot boot.img
sending 'boot' (4974 KB)... OKAY
writing 'boot'... INFOFormat partition LNX done
OKAY
c:\htc>fastboot-windows.exe erase cache
erasing 'cache'... OKAY
c:\htc>fastboot-windows.exe oem lock
... FAILED (command write failed (Unknown error))
c:\htc>fastboot-windows.exe oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
c:\htc>fastboot-windows.exe oem rebootRUU
... INFOSave data from original MSC...
INFOSave data from SIF...
INFOUpdate partition data to SIF partition
INFOoffset = 0
INFOUpdate partition data from original MSC...
INFOoffset = 0
INFO[MSG] OKAY
OKAY
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... FAILED (remote: (00030003))
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... ^C
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... FAILED (remote: (00120000))
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... OKAY
writing 'zip'... FAILED (remote: not allowed)
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... FAILED (unknown status code)
I have unlocked my bootloader again (frrom the HTCDEV website). I can now get into recovery. I have restored my backup which i made before.
I then copied an old boot.img from my original rom
c:\htc>fastboot-windows.exe flash boot boot.img
< waiting for device >
sending 'boot' (4290 KB)... OKAY
writing 'boot'... INFOFormat partition LNX done
OKAY
Then thankfully my phone booted ok back to how it was originally.
You can't flash the 1.36 hboot,
coz your hboot is to low, with version 0.43.
The easiest way would be, to flash the 2.17 ruu,
and after that, you could Update your hboot.
Gesendet von meinem HTC One X mit Tapatalk 2
thanks for the reply. so where can i find the 2.17 ruu
Also can you explain a bit on the steps that I need to complete with the 2.17 ruu
uk_network said:
thanks for the reply. so where can i find the 2.17 ruu
Click to expand...
Click to collapse
htcruu.com
Searching would have got you the answer quicker.
BenPope said:
htcruu.com
Searching would have got you the answer quicker.
Click to expand...
Click to collapse
ok thanks. I should add im from the UK. Will this RUU do the job?
tcruu.com/Endeavor/RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
uk_network said:
ok thanks. I should add im from the UK. Will this RUU do the job?
tcruu.com/Endeavor/RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Click to expand...
Click to collapse
If your phone was destined for the UK, yeah.
fastboot get version-main
Will tell you which ROM you had originally, so the 401 needs to match.
I can't get that command to work with my fastboot.
c:\htc>fastboot-windows.exe fastboot get version-main
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
The same also happens if i type.
c:\htc>fastboot-windows.exe get version-main
Sorry
fastboot getvar version-main
BenPope said:
Sorry
fastboot getvar version-main
Click to expand...
Click to collapse
For him it's 'fastboot-windows.exe getvar version-main'
version-main: 1.26.206.2
c:\htc>fastboot-windows.exe getvar version-main
version-main: 1.26.206.2
When I check on htcruu.com/?dir=Endeavor
I can find:
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed.exe
This has matching 206 version.
But this doesn't have 2.17 as mentioned previously.
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_sined.exe
Any ideas on which one to choose?
The one that matches. Hopefully you'll get OTA updates to 2.17.206.x
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.120 4.90.13_release_251230_signed.exe
I do notice in the title that it says 02_UK im not on 02 im on three.co.uk would this be an issue? if so its the only RUU that has 206 in the title. Also Is this the only way to update hboot versioin?
Thanks to all who are contributing and for your continued support in this matter. I had a shock when I almost originally bricked my one x.
Well where did you get the phone from?
That's the right RUU.
You can update the firmware by locking it, flashing the updated firmware and unlocking it. Either way your phone is gonna get wiped.
I bought the phone from ebay.co.uk from the UK
I am a little confused by this picture it says 1.29.401.11
Should i go ahead with the upgrade?
When i origianly did the below command i got a different version.
fastboot-windows.exe getvar version-main
version-main: 1.26.206.2
There is a discrepancy between 401 and 206 or does this not matter? or can i now use this ruu??
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
And to confirm the next step, after this update i will need to relock the boot loader and then perform the update and then unlock it.
fastboot-windows.exe oem lock
fastboot-windows.exe oem rebootRUU
fastboot-windows.exe flash zip firmware.zip
then perform the unlock from the htcdev site.
Hey guys, dont know really where else to post this, but i need help upgrading my hboot.
Im currently on hboot 1.12 S-ON, cid VODAPO21
i tried flashing 1.36 firmware and it didnt work, gave an error remote:not allowed
i assume i need to go up in increments.
Trouble is , not sure which ones i should flash first and also where to find it. Ive downloaded RUU for my cid versions 1.26 and 1.29...not sure if you can extract the firmware from them, or how its done. Tried opening it in winrar/7-zip and could open em.
Still not there yet.
Still no luck I am afraid. I have tried both of the below RUU's and receive the error in the attached screenshot.
The RUU's that I have tried both give the same error. They are:
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed
Thanks so much to the person who can help get me upgraded to Jelly Bean.
Anyone ?? Im still wanting to update to jellybean and can't yet. Can someone please help me out this this.
You did getvar version main and it said you have a '206 ROM, if a new enough RUU can't be found, you'll have to flash a backup. If you don't have one, check the backups thread for somebody else's. It has to be '206.
BenPope said:
You did getvar version main and it said you have a '206 ROM, if a new enough RUU can't be found, you'll have to flash a backup. If you don't have one, check the backups thread for somebody else's. It has to be '206.
Click to expand...
Click to collapse
I have a backup of my stock rom. But i rooted it and then backed it up. Would this work?
YEsterday i have bought my htc one x and as all te other phones i wanted a custom rom,to simunlock it , so i unlocked the bootloader , put CWMR, Root and did a nandroid backup , Then i used this guide http://forum.xda-developers.com/showthread.php?t=1920060http://
But now my phone dont want to boot and i have forgotten to put the rom on my phone either XD i did a restore already and cleaned the cache but it isn working.. who can help me ?
At wich point you are?
For put the rom into sd you can use the mount sd from recovery
I was at the poit where you put the command,fastboot oem rebootRUU, and i got straight away the silkver HTC letters and i tried to flash firmware but that didnt worked .:/
VivaLaPascal said:
I was at the poit where you put the command,fastboot oem rebootRUU, and i got straight away the silkver HTC letters and i tried to flash firmware but that didnt worked .:/
Click to expand...
Click to collapse
What was the error you got?
Dis you lock the bootloader?
Sent from my HTC One X using xda app-developers app
What is the error?
hej guys he's talking about simunlocking....that's not going to work by unlockng the bootloader ! totally different
but.....
you only need to do this :
lock the bootloader (like stated above)
fastboot oem lock
then
fastboot oem rebootRUU
then
Fastboot flash zip firmware.zip (with the firmware.zip in the fastboot folder)
that's all.....
the problem is that i cant flash the firmware, yes i locked it again , at the moment its unlocked and now hen i turn on my phone it gets stuck at the o2 screen, you are simlock free when you change your rom as far as i now:laugh: ps where is my fastboot folder?
The firmware.zip must be in the folder where you have fastboot.
Because if the zip isn't in this folder, fastboot can't flash this.
No you are not simlock free when changing Rom !
I don't know where you left it do a search for fastboot.exe file or adb.exe file it should pop up somewhere
Mr Hofs said:
No you are not simlock free when changing Rom !
I don't know where you left it do a search for fastboot.exe file or adb.exe file it should pop up somewhere
Click to expand...
Click to collapse
lol i unlocked my sensation that way XD so i put the firmware in the folder and try to push it to the phone ?
I Tried to flash the firmware again, the first two times it failed and the third time it is gets stuck at sending frimware ... C:\Users\Home\Desktop\One_X_All-In-One_Kit_v2.3\data> fastboot flash zip C:\firm
ware.zip
sending 'zip' (13033 KB)...
OKAY [ 1.747s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 3.245s
C:\Users\Home\Desktop\One_X_All-In-One_Kit_v2.3\data> fastboot flash zip C:\firm
ware.zip
sending 'zip' (13033 KB)...
FAILED (remote: (00030003))
finished. total time: 0.000s
C:\Users\Home\Desktop\One_X_All-In-One_Kit_v2.3\data> fastboot flash zip C:\firm
ware.zip
sending 'zip' (13033 KB)...
I know because you had a S-OFF device. The HTC oke X is S-ON so you will not get it simunlocked this way !
And yes you put the firmware.zip inside the fastboot folder and then execute the commands i wrote earlier
Did you download the corresponding firmware for your CID ?.
VivaLaPascal said:
I Tried to flash the firmware again, the first two times it failed and the third time it is gets stuck at sending frimware ... C:\Users\Home\Desktop\One_X_All-In-One_Kit_v2.3\data> fastboot flash zip C:\firm
ware.zip
sending 'zip' (13033 KB)...
OKAY [ 1.747s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 3.245s
C:\Users\Home\Desktop\One_X_All-In-One_Kit_v2.3\data> fastboot flash zip C:\firm
ware.zip
sending 'zip' (13033 KB)...
FAILED (remote: (00030003))
finished. total time: 0.000s
C:\Users\Home\Desktop\One_X_All-In-One_Kit_v2.3\data> fastboot flash zip C:\firm
ware.zip
sending 'zip' (13033 KB)...
Click to expand...
Click to collapse
Fastboot oem readcid
Then download the proper firmware from mike1986 firmware post.
Sent from my HTC One X using xda app-developers app
Mr Hofs said:
I know because you had a S-OFF device. The HTC oke X is S-ON so you will not get it simunlocked this way !
And yes you put the firmware.zip inside the fastboot folder and then execute the commands i wrote earlier
Did you download the corresponding firmware for your CID ?.
Click to expand...
Click to collapse
AAh lol ok XD sending the firmware still doesnt work , my cid: O2___001 , that is equal to cidnum: HTC__001 right? i have downloaded my firmware from here http://d-h.st/users/baadnewz/?fld_id=3041#files
Nooo ow god ! They are different......O2 - HTC ....VERY DIFFERENT !
Go here and download the EXACT matching firmware
http://forum.xda-developers.com/showthread.php?t=1957376
O2__001 firmware to hboot 1.36 !
Mr Hofs said:
Nooo ow god ! They are different......O2 - HTC ....VERY DIFFERENT !
Go here and download the EXACT matching firmware
http://forum.xda-developers.com/showthread.php?t=1957376
O2__001 firmware to hboot 1.36 !
Click to expand...
Click to collapse
so i flash this and then flashthe rom ? thank you very much! feel so stupid xd
VivaLaPascal said:
AAh lol ok XD sending the firmware still doesnt work , my cid: O2___001 , that is equal to cidnum: HTC__001 right? i have downloaded my firmware from here http://d-h.st/users/baadnewz/?fld_id=3041#files
Click to expand...
Click to collapse
Hi Mate,
02__001 is not the same in anyway as HTC__001. HTC__001 is unbranded uk, 02__001 is then obviously 02 branded, do not confuse the two. Right if you have made a nandroid back up and still have custom recovery installed, have you extracted a copy of your boot image from your nandroid if so, flash the boot image using fasboot command, when phone is connected to PC, then boot in to recovery and restore nandroid.
If this is not the case you need to supply some more info about your phone, what base it was on when you got it, what HBOOT you are currently on, because if your are on a lower HBOOT than a JB firmware then you will not be able to do a JB RUU, you may have to do a ICS RUU.
So for starters
is your bootloader ***unlocked***
are you using international HOX ie ENDEAVORU
what is HBOOT ...
once the community know exactly what you are working with and what you have done people will be best placed to help you. Please bare in mind the HOX is not fully unlocked like previous HTC devices ie no "S-OFF" unless you are very lucky, so it is not as easy as just flash, there are a lot of fastboot commands to be aware of a little reading prior to actioning anything on your phone will go a long way.
Qball
qball11 said:
Hi Mate,
02__001 is not the same in anyway as HTC__001. HTC__001 is unbranded uk, 02__001 is then obviously 02 branded, do not confuse the two. Right if you have made a nandroid back up and still have custom recovery installed, have you extracted a copy of your boot image from your nandroid if so, flash the boot image using fasboot command, when phone is connected to PC, then boot in to recovery and restore nandroid.
If this is not the case you need to supply some more info about your phone, what base it was on when you got it, what HBOOT you are currently on, because if your are on a lower HBOOT than a JB firmware then you will not be able to do a JB RUU, you may have to do a ICS RUU.
So for starters
is your bootloader ***unlocked***
are you using international HOX ie ENDEAVORU
what is HBOOT ...
once the community know exactly what you are working with and what you have done people will be best placed to help you. Please bare in mind the HOX is not fully unlocked like previous HTC devices ie no "S-OFF" unless you are very lucky, so it is not as easy as just flash, there are a lot of fastboot commands to be aware of a little reading prior to actioning anything on your phone will go a long way.
Qball
Click to expand...
Click to collapse
Please read the thread next time queball
We know what he is doing ..... he just got the wrong firmware. And i already gave him the link to the right one so......
And yes flash the right firmware, flash a custom recovery, flash the boot.img from the desired rom, full wipe in recovery and a clean install of the new Rom.
hello,
I own a 32 GB HOX and I need to completly stocked my phone using the RUU
I just dont know which one I have to choose
my CID is : HTC_044
Thank you !
Stop making threads with different stories. Its confusing.
Who wins a hox that does not work. Return it and get a new one !!!
http://forum.xda-developers.com/showthread.php?t=2374320
Mr Hofs said:
Stop making threads with different stories. Its confusing.
Who wins a hox that does not work. Return it and get a new one !!!
http://forum.xda-developers.com/showthread.php?t=2374320
Click to expand...
Click to collapse
I meant 'own'
I just noticed it .
That clears things up !
Fastboot getvar version-main
That will tell you the number of the ruu you need
Mr Hofs said:
That clears things up !
Fastboot getvar version-main
That will tell you the number of the ruu you need
Click to expand...
Click to collapse
Ok than
I already used the right RUU and Run it
Now after using in the RUU the HOX immediately boots into bootloader
I tried to flash a new boot with no success
C:\Users\Shavit\Desktop\One_X_All-In-One_Kit_v2.3\Data>fastboot flash boot boot.
img
sending 'boot' (5200 KB)...
OKAY [ 0.651s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.854s
Click to expand...
Click to collapse
But what is now exactly your goal, i see so many different things everywhere....
But to answer this question :
A boot.img (the kernel) can't be flashed with a locked/relocked bootloader, after you ran the ruu your bootloader is either locked or relocked and you need to unlock it first to be able to flash anything !
Mr Hofs said:
But what is now exactly your goal, i see so many different things everywhere....
But to answer this question :
A boot.img (the kernel) can't be flashed with a locked/relocked bootloader, after you ran the ruu your bootloader is either locked or relocked and you need to unlock it first to be able to flash anything !
Click to expand...
Click to collapse
First of all thank you !
my goal is just to be able to use the DAM PHONE
Currently my bootloader is LOCKED and I can't manage to unlock it
C:\Users\Shavit\Desktop\One_X_All-In-One_Kit_v2.3\Data>fastboot flash unlocktoke
n Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.130s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Unknown error))
finished. total time: 4.747s
Click to expand...
Click to collapse
THis happens after choosing the 'YES' option in the HOX
And it stays relocked after a reboot ?
Then get a new code at the HTC dev site ....maybe that helps
Mr Hofs said:
And it stays relocked after a reboot ?
Then get a new code at the HTC dev site ....maybe that helps
Click to expand...
Click to collapse
Even after a reboot it stays ***LOCKED***
I tried to get a new code
A different error this time
C:\Users\Shavit\Desktop\One_X_All-In-One_Kit_v2.3\Data>fastboot flash unlocktoke
n Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.011s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 3.501s
Click to expand...
Click to collapse
I tried agagin with another Unlock_Code.bin and I get a different every time
FAILED (status read failed (Unknown error))
FAILED (status read failed (Too many links))
every time a different one
Any help with that ?
Well actually no ! If the token get flashed to the phone and you see the unlock screen its all correct. If it stays unlocked like yours do then i can't do anything unfortunately
Hi,
I've relocked my HOX (1.72 HBOOT, 4.18.401.4 mainver, and HTC__Y13 CID) but now I'm not able to unlock it to install cwm. When I try to unlock via fastboot I get the following error:
C:\Users\XXX>fastboot flash unlocktocken c:\Unlock_code.bin
sending 'unlocktocken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktocken'...
FAILED (remote: not allowed)
finished. total time: 0.354s
How should I proceed? Thanks guys
Get a brand new one via the HTC dev site and try again. But why on earth did you relock it to begin with ?
Mr Hofs said:
Get a brand new one via the HTC dev site and try again. But why on earth did you relock it to begin with ?
Click to expand...
Click to collapse
I followed some "back to stock" guide (from h t t p s://w w w.youtube.com/watch?v=SZuAjz4PIjU) for HOX that included installing a stock recovery and relocking the phone. However, I couldn't find the correct RUU. I tried using a new unlock token from HTCdev but obviously it didn't work as it's identical. Thanks for the help though!
Lesson learned....never do something before you gathered all the files needed !
Are you flashing the token correctly, is the phone connected to the pc on a usb 2.0 port (not a usb hub or other in between connection) ?
You were unlocked, what does the bootloader say now ?
Locked or relocked ?
Mr Hofs said:
Lesson learned....never do something before you gathered all the files needed !
Are you flashing the token correctly, is the phone connected to the pc on a usb 2.0 port (not a usb hub or other in between connection) ?
You were unlocked, what does the bootloader say now ?
Locked or relocked ?
Click to expand...
Click to collapse
The phone is connected directly to the USB and it is Relocked, occassionally showing the "security warning" under it. I downloaded the correct nandroid backup for the phone, but as I don't have a custom recovery I'm not able to use it. I tried to flash a stock recovery (again) but I keep getting the same "FAILED (remote: not allowed)" whenever I try to do any changes to the phone.
Why it is btw that we can't have a RUU for a certain version? No way to downgrade ?
S-on devices cant downgrade,only s-off devices can. But you need to find a shop that can offer that specific service, can't do it in anyway at home.
But i see you flash the unlock code from a specific folder. Try it like this :
Open the command prompt directly from the fastboot.exe folder and place the unlock code.bin file in that specific directory too ! Then perform the unlock fastboot command again
Mr Hofs said:
Open the command prompt directly from the fastboot.exe folder and place the unlock code.bin file in that specific directory too ! Then perform the unlock fastboot command again
Click to expand...
Click to collapse
Unfortunately that didn't work. It seems there's not much I can do now.
you did fastboot flash unlocktocken instead of fastboot flash unlocktoken.
trying to flash to a non existing partition gives this error.
I had same problem when I did fastboot flash unlock instead of unlocktoken
so unlock with ck and token without ck
jjgittes said:
Hi,
I've relocked my HOX (1.72 HBOOT, 4.18.401.4 mainver, and HTC__Y13 CID) but now I'm not able to unlock it to install cwm. When I try to unlock via fastboot I get the following error:
C:\Users\XXX>fastboot flash unlocktocken c:\Unlock_code.bin
sending 'unlocktocken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktocken'...
FAILED (remote: not allowed)
finished. total time: 0.354s
How should I proceed? Thanks guys
Click to expand...
Click to collapse
man all credits goes to @vastloper and next time it will be good to copy the command from the HTCdev site not to write it manually use the right command
@vastloper it will be good to quote him to see your comment. when you quote him he will receive the notification and will see his mistake with sure:good:
vastloper said:
you did fastboot flash unlocktocken instead of fastboot flash unlocktoken.
trying to flash to a non existing partition gives this error.
I had same problem when I did fastboot flash unlock instead of unlocktoken
so unlock with ck and token without ck
Click to expand...
Click to collapse
Thanks a lot! :victory: I did indeed make a typo on that, and used the same command over and over again without rewriting it.
I was able unlock and recover back to stock. However, I'm not still able to use my phone due to the blank/black screen issue, and will be further investigating that.
Does anyone have a O2__001 CID Stock Rom??
jjgittes said:
Hi,
I've relocked my HOX (1.72 HBOOT, 4.18.401.4 mainver, and HTC__Y13 CID) but now I'm not able to unlock it to install cwm. When I try to unlock via fastboot I get the following error:
C:\Users\XXX>fastboot flash unlocktocken c:\Unlock_code.bin
sending 'unlocktocken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktocken'...
FAILED (remote: not allowed)
finished. total time: 0.354s
How should I proceed? Thanks guys
Click to expand...
Click to collapse
Are you have battery take new unlocktoken and try again