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
Related
Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.
You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium
Thanks sir, I'll try.
sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.
See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command
sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA
Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!
Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.
Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!
I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?
All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?
When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
Nobody can help me?!! ((
I've been trying to update my HOX to JB since yesterday but to no avail:
Im on everything stock (ROM, Recovery etc) and phone is un-rooted. I relocked the bootloader too. but when the update downloads and the phone restarts after a few while, a red triangle with exclamation marks appear and phone restarts.
I've tried to do this 3 times now with no avail.
alternately i've been trying to follow this and when i reach the flashing firmware part, it fails after 2 tries and after the 3rd it just stucks:
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
OKAY [ 1.683s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.886s
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
after 3rd attempt it just stays in sending 'zip' state
anyone got a clue how i can solve either problem?! :/
note my camera app is a modified version. rest all ROM is stock. could this be the issue?! if so, then any way to resolve this other than RUU method?
The last method you tried will not work if the bootloader is still locked !
The red triangle is normally an indication that you do not have the stock recovery. Try to reflash recovery and then fastboot erase cache before trying again, You would need to unlock bootloader in order to fastboot flash recovery. As pointed out in my other reply to you, you would probably need to revert to the stock camera app as well.
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.
Ah like that ! Thanks clyde :thumbup:
I did not read carefully... was kinda busy with my mac & cheese !!!
MarcelHofs said:
Ah like that ! Thanks clyde :thumbup:
I did not read carefully... was kinda busy with my mac & cheese !!!
Click to expand...
Click to collapse
ClydeB1 said:
Click to expand...
Click to collapse
LOL !
ClydeB1 said:
The red triangle is normally an indication that you do not have the stock recovery. Try to reflash recovery and then fastboot erase cache before trying again, You would need to unlock bootloader in order to fastboot flash recovery. As pointed out in my other reply to you, you would probably need to revert to the stock camera app as well.
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.
Click to expand...
Click to collapse
thanks, will try the OTA method 1st by installing the RUU. if that works then brilliant! otherwise try the 2nd
ClydeB1 said:
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.
Click to expand...
Click to collapse
worked like a charm, thnx mate! :good:
Didnt work for me
Asad_612 said:
worked like a charm, thnx mate! :good:
Click to expand...
Click to collapse
I get to the rebootRUU step and that works, but when I try to flash the firmware.zip it always comes up with "error: cannot load "fastboot.zip" : Unknown error" do you know what the problem might be?
mewazhere said:
I get to the rebootRUU step and that works, but when I try to flash the firmware.zip it always comes up with "error: cannot load "fastboot.zip" : Unknown error" do you know what the problem might be?
Click to expand...
Click to collapse
Fastboot.zip ..... Yeah that's wrong
Fastboot flash zip firmware.zip
And the firmware file need to be named firmware.zip !
i neded to flash stock 3uk romy (any) and lock bootloader
i have customn rom and custom recovery
INFODEBUG: cid: H3G__001
version-main: 1.28.771.9
i found solution but maybe its wrong
1.fastboot oem lock
then i have message in bootloader:
https://www.dropbox.com/s/oq8e5ko9p3zexbl/20130213_032052.jpg
and then i downloaded:
RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.1204.103.14H_release_256494_signed
im in fastboot but i have error 170 problem with connection.
can someone please help me...
lukers said:
i neded to flash stock 3uk romy (any) and lock bootloader
i have customn rom and custom recovery
INFODEBUG: cid: H3G__001
version-main: 1.28.771.9
i found solution but maybe its wrong
1.fastboot oem lock
then i have message in bootloader:
https://www.dropbox.com/s/oq8e5ko9p3zexbl/20130213_032052.jpg
and then i downloaded:
RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.1204.103.14H_release_256494_signed
im in fastboot but i have error 170 problem with connection.
can someone please help me...
Click to expand...
Click to collapse
so you have fastboot up and running, if you give the fastboot command
fastboot devices
it gives a serial back in the command window ? (your bootloader says fastboot usb, so i guess it should be fine)
how did you execute the RUU, did you execute the RUU with admin rights (right click the ruu.exe and select run with admin rights)
Mr Hofs said:
so you have fastboot up and running, if you give the fastboot command
fastboot devices
it gives a serial back in the command window ? (your bootloader says fastboot usb, so i guess it should be fine)
how did you execute the RUU, did you execute the RUU with admin rights (right click the ruu.exe and select run with admin rights)
Click to expand...
Click to collapse
fastboot devices - back
SH24XW111133 fastboot
ruu as amin
after if have this message relocked security warning if i want use phone i have to:
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
and unlock bootloader ant then my old rom is working but because i want unlock my phone i have from network unlock pin but not working i someone said that i have to back to stock with lock bootloader.
and i cant find answer
why i have this error 170 in fastboot?
this ruu is ok: RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.12 04.103.14H_release_256494_signed?
the only thing i noticed that radio its diffident in ruu then in bootloader. and im using Windows 7 and when im in fastboot windows see phone as fastboot.
The main version matches so that should be fine. What you can try is this :
Flash the stock recovery 1.28 and the stock boot.img back first. Then relock the bootloader and run the ruu again.
Mr Hofs said:
The main version matches so that should be fine. What you can try is this :
Flash the stock recovery 1.28 and the stock boot.img back first. Then relock the bootloader and run the ruu again.
Click to expand...
Click to collapse
i reinstalled drivers and connect to diffrent usb and ruu start but now during process error 155??? The flash fails at checking mid/cid and before that there is image version 1.28.771.0 to image version 1.28.771.0
so i will try
Flash the stock recovery 1.28 and the stock boot.img back first???
i did unpack ruu and from rom.zip recovery and boot from (RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.12 04.103.14H_release_256494_signed)
i did:\
C:\fastboot>fastboot flash boot boot.img
sending 'boot' (4282 KB)... OKAY
writing 'boot'... INFOFormat partition LNX done
OKAY
C:\fastboot>fastboot erase cache
erasing 'cache'... OKAY
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (5790 KB)... OKAY
writing 'recovery'... INFOFormat partition SOS done
OKAY
then
C:\fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
C:\fastboot>fastboot erase cache
erasing 'cache'... OKAY
this time no security warning
ant then in fastboot ruu again and error 155 again
thanks for your help
Download this one
http://androidfiles.org/ruu/securek...adio_1.1204.105.14H_release_260888_signed.exe
Try again
Mr Hofs said:
Download this one
http://androidfiles.org/ruu/securek...adio_1.1204.105.14H_release_260888_signed.exe
Try again
Click to expand...
Click to collapse
now its look good
i flashed recovery and boot from this fresh downloaded rom
its stock 3 android 4.0.3
wowwwwwwwwww
can now upgrade to jelly bean?
i checked ota update but is not available from phone,
lukers said:
now its look good
i flashed recovery and boot from this fresh downloaded rom
its stock 3 android 4.0.3
wowwwwwwwwww
can now upgrade to jelly bean?
i checked ota update but is not available from phone,
Click to expand...
Click to collapse
Yeah you should be able to update the phone, try to check a couple of times manually for ota's.
hey guys i just wanted to update hboot and now im stuck -.-
im german and my english is not the best...sry for that
but i hope one of you guys is able to help me with my phone:good:
phone is a One X brandet O2 ger
Cid is O2___102
Hboot is 0.94
radio 1.1204.90.13
i had a venom rom viper x (from oct 2012)
i wanted to update hboot and there was a step which said relock the device. yeah that was done no prob..
now i´ve a locked device (but i´ve got the unlock token from htc)
how to use that? already tried to put that into my phone via fastboot but there comes a error message
sending 'unlocktoken' (0 KB)... OKAY [ 0.009s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.224s
Click to expand...
Click to collapse
i think im not able to figure that out without any help
first i think to unlock the device again and after that just update hboot and then flash cm 10.1
thx for your help
To upgrade your Hboot... You first need to lock your device and then flash the firmware.zip!
After than unlock your device and then flash custom recovery and then install CM10.1
Post the result of the following code:
Code:
fastboot getvar version-main
If there's a RUU for your device, then you can go back to stock and then update to JB via OTA update if you want..?!
sending 'unlocktoken' (0 KB)... OKAY [ 0.009s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.224s
Click to expand...
Click to collapse
Generate a new unlock_code.bin file from htcdev.com and then try again!
vin4yak said:
To upgrade your Hboot... You first need to lock your device and then flash the firmware.zip!
After than unlock your device and then flash custom recovery and then install CM10.1
Post the result of the following code:
Code:
fastboot getvar version-main
If there's a RUU for your device, then you can go back to stock and then update to JB via OTA update if you want..?!
Generate a new unlock_code.bin file from htcdev.com and then try again!
Click to expand...
Click to collapse
+1 .. Here's the firmware thread >> http://forum.xda-developers.com/showthread.php?t=1957376 <<
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