My sensation had to go for repairs to the htc center so i relocked the phone (fastboot oem lock) and now it won't unlock...
Code:
C:\ext>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.160s
It is the same file that i used the first time and redone the whole dev thing again but that did not help..
Just s-off using ganeshps thread. Root it then use no HTC unlock juopunutbear s-off tool
Sent from my HTC Sensation using xda app-developers app
It won't wiretrick.. just black screen after "good tricking" after booting it says s-off failed..
ThaOdie said:
It won't wiretrick.. just black screen after "good tricking" after booting it says s-off failed..
Click to expand...
Click to collapse
if motherboard is replaced then forget htcdev method
it won't work for you this time
only wire trick is your option
Related
Hi all, first of all, sorry for being a complete noob to all this.
I was wondering if I could have some help installing Cyanogen mod on my HTC sensation as I find the stock ROM to be far to slow and bloated.
I have downloaded KGS Utility for all rooting/ S off purposes, my main issue at the moment is unlocking the bootloader,
I have got a unlock token from HTCdev but when I try and flash it, I get the following error:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.159s
I have followed all the instructions to the letter and tried multiple times.
Does anyone know what could be causing this. The device is definitely in bootloader USB mode with fastboot off and USB debugging enabled (though I have tried different combinations of these settings with no luck).
My next question is when it comes to flashing the ROM what order do I need to do everything. From what I can gather, once the bootloader is unlocked, I need to root, S-off and then install a new recovery in that order before flashing cyanogen. Is this correct?
Thanks for any help in advance.
Tom
there is no need to open a second thread
i answered you to the other one
It said the key was invalid, get another one and make sure you don't type it incorrectly
Sent from my Galaxy Nexus using xda app-developers app
i just got my phone back today and everything for rooting i find is for gingerbread and so i tried to use ruu on the stock phone i just got and for some reason the set up froze..
anthonyly said:
i just got my phone back today and everything for rooting i find is for gingerbread and so i tried to use ruu on the stock phone i just got and for some reason the set up froze..
Click to expand...
Click to collapse
Hi,
Look HERE
malybru said:
Hi,
Look HERE
Click to expand...
Click to collapse
Step 1 | Pre-requisites:
Be on the Stock RUU and be rooted (have superuser flashed). No other ROMs are supported, Fresh ROM will not work regardless of what you have read elsewhere.
How am i suppose to have it roooted with superuser flashed...?
nvm it said exception but... i did parts of it and then i ran controlbear exe
and its comming out like
Waiting ADB.... (41/60)ADB server didn't ACK
* failed to start daemon *
and lastly
Waiting ADB.... (60/60)
Test 2: Booting FAILED
Reboot device manually
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit.....
I tried with htc dev and then i got stuck on step 12... it said mine failed
http://www.htcdev.com/bootloader/unlock-instructions/page-4/
anthonyly said:
I tried with htc dev and then i got stuck on step 12... it said mine failed
http://www.htcdev.com/bootloader/unlock-instructions/page-4/
Click to expand...
Click to collapse
do you have adb and fastboot files installed?(sdk tools)
if yes go to the folder where you have adb and fastboot
put there the unlock token.bin code
open the command window there and then do the command
C:\AndroidSDK\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.167s
C:\AndroidSDK\platform-tools>
still not working...
anthonyly said:
C:\AndroidSDK\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.167s
C:\AndroidSDK\platform-tools>
still not working...
Click to expand...
Click to collapse
make sure that you have htc sync and htc drivers installed
Hi,
Windows 7 & 8 drivers are HERE
Sometimes it takes more than one go.
Keep trying.
I thought you're supposed to un install htc sync... Okay I'll try again
Sent from my HTC-Z710a using xda premium
malybru said:
Hi,
Windows 7 & 8 drivers are HERE
Sometimes it takes more than one go.
Keep trying.
Click to expand...
Click to collapse
how do you install drivers?
anthonyly said:
how do you install drivers?
Click to expand...
Click to collapse
Hi,
Plug the phone into the USB socket.
On the PC ,go to Device Manager.
Right click Either the "Android" or the MyHTC ,and go to update drivers.
Manually lead it to the Windows 7 & 8 drivers,and update.
Reboot, and go to the terminal..
malybru said:
Hi,
Plug the phone into the USB socket.
On the PC ,go to Device Manager.
Right click Either the "Android" or the MyHTC ,and go to update drivers.
Manually lead it to the Windows 7 & 8 drivers,and update.
Reboot, and go to the terminal..
Click to expand...
Click to collapse
I tried and it goes like
Android USB Devices>Android Composite ADB interface
then i press update so then i browse for the windows 7 driver
and in the end it comes out as "Window has determined the driver for your device is up to date."
Android Composite ADB interface
and for the HTC dev one, i have a sensation with Virginmobile Canada
So im suppose to click on all other supported devices right?
edit`````
well i uninstalled htc sync and everything else
then reinstalled htc sync (FULL)
no matter what i try i still get
C:\AndroidSDK\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.167s
hello, earlier today i had to downgrade from the rogers jb software to the 2.20 ICS ruu and when trying to re unlock the bootloader it will not re unlock.
Steps:
i ran the xfactor exploit result > CID already changed
in fastboot i reflash my unlock code result> unlock bootloader screen comes up i select yes, it reboots.
when device boots up i skip setup go and enable usb debugging then reboot to bootloader via adb
when the bootloader comes on it still says *** RELOCKED*** am i doing something wrong or....
Device: HTC One X (EVITA)
Hboot: 1.14.0002
Radio: 0.19as.32.09.11_2
Rom: 2.20.... 710 RD
any help is appreciated
fastboot erase cache
then unlock it again
absolutelygrim said:
fastboot erase cache
then unlock it again
Click to expand...
Click to collapse
alright, i will try that, i will report back and let you know how that goes
Update: I Tried that command and to no avail... heres the output on the CMD
C:\Users\Development PC\Downloads\adb_fastboot_and_other_tools\Android>fastboot
erase cache
erasing 'cache'... OKAY [ 0.125s]
finished. total time: 0.125s
C:\Users\Development PC\Downloads\adb_fastboot_and_other_tools\Android>fastboot
flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.140s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.140s
C:\Users\Development PC\Downloads\adb_fastboot_and_other_tools\Android>
any ideas?
fastboot flash unlocktoken Unlock_token.bin
Or whatever you have the filename as. I think its case sensitive
Sent from my One X using xda app-developers app
Factory reset then unlock
DvineLord said:
Factory reset then unlock
Click to expand...
Click to collapse
Nope that didn't work either
Sent from my HTC One X using xda app-developers app
USB debugging is enabled?
absolutelygrim said:
USB debugging is enabled?
Click to expand...
Click to collapse
yes, for all intents and purposes it does everything it is supposed to even shows the Unlock Bootloader screen where it says the warranty disclaimer and asks to choose yes or no, i choose yes the phone resets i speed thru the setup enable usb debugging then adr reboot bootloader and it still states "RELOCKED" if i could i would do a logcat but i dont know how or if it's even possible to logcat the unlock process or any fastboot process for that matter...
So i dont know what happend, i succesfully make my hox S-OFF, use the phone and everything was working fine, then a try to downgrade my bootloader with Jet but everything went wrong from there, the process didnt finish, i try to relocked my bootloader to install the 2.20 RUU thinking it would fix it but know the RUU procesos finishes with a 131 error because my cid is diferent, this is what i have:
******tampered*****
******relocked******
jewel pvt ship s-off rl
cid-spcs_001
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendsp-v29.1.0.45.0622
emmc-boot
I can put fastboot commands but its shows FAILED (remote: not allowed), i cant go into recovery, also on jet i cant go into QHSUSB_DLOAD anymore.
You really didn't need to downgrade being you were s-off.............
Sent from my HTC One X using Tapatalk 2
Did you try this command to unbrick?: sudo ./jet -u
Edit: hmm just noticed your cid changed to stock. Sorry idk where to go from there
Sent from my HTC One X using xda premium
Yes i did try the ./jet -u command but i cant get in to QHSUSB_DLOAD anymore that is the stock cid for the one x ? if thats the case maybe i can run de 1.85 RUU?
pikul said:
i cant get in to QHSUSB_DLOAD anymore
Click to expand...
Click to collapse
Did you try the hardware key way? Same as bootloader, but power and vol +
Practically gave myself a heart attack yesterday. Someone here was having trouble getting into bootloader, and mentioned power and vol +. I couldn't remember what that did (knew it wasn't bootloader) so I did it, and put the phone in Qualcomm download mode!
I was able to get back to bootloader, recovery, and reflashed the ROM that happened to be on my phone.
No. What I meant was your cid isn't supercid anymore. And I wouldn't use that RUU since your hboot is 1.14; wait till someone more experienced helps you out
Sent from my HTC One X using xda premium
redpoint73 said:
Did you try the hardware key way? Same as bootloader, but power and vol +
Practically gave myself a heart attack yesterday. Someone here was having trouble getting into bootloader, and mentioned power and vol +. I couldn't remember what that did (knew it wasn't bootloader) so I did it, and put the phone in Qualcomm download mode!
I was able to get back to bootloader, recovery, and reflashed the ROM that happened to be on my phone.
Click to expand...
Click to collapse
I guess i could run the ./jet -u command and press those keys, its that what you mean?
panda_mode said:
No. What I meant was your cid isn't supercid anymore. And I wouldn't use that RUU since your hboot is 1.14; wait till someone more experienced helps you out
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
ooooooooo :good: at least i can get into bootloader and put fastboot commands, i guess thats something
pikul said:
I guess i could run the ./jet -u command and press those keys, its that what you mean?
Click to expand...
Click to collapse
I've actually never used JET, and not quite sure how it works.
But power and vol + will put the phone in QHSUSB_DLOAD in most situations (nothing to do with JET), if that is all you are trying to do. Similar to how power and vol - boots into bootloader. Just curious if it would still worked in your "bricked" condition.
Are you able to get into fastboot? If so just use stock RUU to get back to stock,
thats the thing, i can get in to fastboot, try to run the 2.20 RUU starts and maybe 1 minute later it fails, and gives a ERROR [131] i google it and it seems to be because the cid its not the correct one anyone knows if there its a way to bypass the cid verification?
pikul said:
thats the thing, i can get in to fastboot, try to run the 2.20 RUU starts and maybe 1 minute later it fails, and gives a ERROR [131] i google it and it seems to be because the cid its not the correct one anyone knows if there its a way to bypass the cid verification?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/HTC_One_X
Try this thread. I think there is a way to use the stock recovery and the cid you used to unlock it. May give you some ideas.
AT&T HTC OneX
Andriod 4.1.1
ViperXL
i check all of them, but i just cant get to unlock my bootloader again or flash a different cid, not even flash the recovery, y guess its because i relock my bootloader
pikul said:
i check all of them, but i just cant get to unlock my bootloader again or flash a different cid, not even flash the recovery, y guess its because i relock my bootloader
Click to expand...
Click to collapse
Have you tried to get a new identifier token and unlock the phone to get TWRP again?
http://onexroot.com/one-x-root/how-to-unlock-bootloader-and-root-att-htc-one-xhtc-one-xl/
AT&T HTC OneX
Android 4.1.1
ViperXL
is it posible to get it in bootloader mode? cause thats all i can access :/
Everytime i try to flash a file in fastboot it shows FAILED (remote: not allowed)
pikul said:
is it posible to get it in bootloader mode? cause thats all i can access :/
Click to expand...
Click to collapse
download a ROM.. put it in your fastboot folder,
boot into fastboot and try this
fastboot flash zip name_of_rom.zip <-- this works with HTC RUUs, may work with an actual ROM.. Use at your own risk, I have never tried it with a custom ROM.
mirGantrophy said:
download a ROM.. put it in your fastboot folder,
boot into fastboot and try this
fastboot flash zip name_of_rom.zip <-- this works with HTC RUUs, may work with an actual ROM.. Use at your own risk, I have never tried it with a custom ROM.
Click to expand...
Click to collapse
I took the .img files from the rom.zip that you get from the RUU, but it doesnt work.
C:\Programas\Fastboot>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.966s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.000s
C:\Programas\Fastboot>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.309s
pikul said:
I took the .img files from the rom.zip that you get from the RUU, but it doesnt work.
C:\Programas\Fastboot>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.966s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.000s
C:\Programas\Fastboot>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.309s
Click to expand...
Click to collapse
If you have the RUU.zip, do this then:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip rom.zip
see if that works..
This is what i get:
C:\Programas\Fastboot>fastboot flash zip rom.zip
sending 'zip' (576544 KB)...
OKAY [ 24.368s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 26.975s
this sucks, i have to go to work and i dont have another cellphone :/
pikul said:
this sucks, i have to go to work and i dont have another cellphone :/
Click to expand...
Click to collapse
You can try to find the cidnum for the htc onexl and see if you can trick it by editing android-info.txt file to match cid num.
Example:
edited android-info file
modelid: PG3213000
cidnum: KT___901
cidnum: HTC__004(this edited file only)
mainver: 2.32.1010.1
hbootpreupdate:13
boot again into fastboot
AT&T HTC OneXL
Android 4.1.1
ViperXL
So I'm in the process of getting my phone back to original to so I can edge up my phone. I accident relocked the bootloader with oem relock, and now I'm stuck with S-OFF and "relocked." I'm not quite sure what to do now, as I also uninstalled SU. How do I go about getting "Locked" and S-ON. I tried the sdb shell and all that stuff, but when you type SU I can't since it is no longer installed. Also if I try to push a recovery it fails.
Code:
C:\ADB>fastboot flash recovery cwm_v6.0.4.8_m8vzw-3.img
target reported max download size of 1830612992 bytes
sending 'recovery' (12564 KB)...
OKAY [ 1.175s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.193s
CinemaGFX said:
So I'm in the process of getting my phone back to original to so I can edge up my phone. I accident relocked the bootloader with oem relock, and now I'm stuck with S-OFF and "relocked." I'm not quite sure what to do now, as I also uninstalled SU. How do I go about getting "Locked" and S-ON. I tried the sdb shell and all that stuff, but when you type SU I can't since it is no longer installed. Also if I try to push a recovery it fails.
Code:
C:\ADB>fastboot flash recovery cwm_v6.0.4.8_m8vzw-3.img
target reported max download size of 1830612992 bytes
sending 'recovery' (12564 KB)...
OKAY [ 1.175s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.193s
Click to expand...
Click to collapse
So what you need to do is. Supercid your phone to 11111111 an go to htcdev.com an unlock your bootloader. Then once that is done. You need to downgrade to 1.55 so then you can lock your bootloader turn s-on an ruu the encrypted ruu that posted. Do NOT TURN S-ON till you find this ruu that's posted an understand it completey an ask dottat any question in that thread. Once you r downgraded locked an s-on an run the encrypted ruu your phone should be all stock an lock an s-on no tampered no nothing.
I was able to get back to stock except I have the tampered flag. I did this last night so I was unable to follow your steps. What should I go about now, as I have S-ON, locked bootloader, no root and a tampered flag?
CinemaGFX said:
I was able to get back to stock except I have the tampered flag. I did this last night so I was unable to follow your steps. What should I go about now, as I have S-ON, locked bootloader, no root and a tampered flag?
Click to expand...
Click to collapse
I think he specifically said do NOT turn s on. You cannot do anything unless you s off again. What Rom do you have loaded? Turning s off is the LAST step because it's like locking the door and throwing away the keys
I actually did that stuff before I saw his message, I followed: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Guess now I'm going pay to get the s back off...
CinemaGFX said:
I actually did that stuff before I saw his message, I followed: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Guess now I'm going pay to get the s back off...
Click to expand...
Click to collapse
Well. We got something else to try. What version os are you on?