Hey there,
just today I got my Phone back from HTC for repairing the Display.
On the delivery paper was a notice that the mainboard was replaced and the phone now has a different IMEI.
As I now tried to gain an unlocked bootloader by using the HTCDev Method, I get the same error everytime:
Code:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.153s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.164s
I am 100% sure, that I didn't make a mistake while unlocking.
Do you have any suggestions?
Niklas
As far as I know if htc has changed your motherboard, the unlocking method on htcdev website is not going to work. You need to follow Ganeshp's guide to achieve S-OFF. It is in GENERAL section.
Yes after you get your motherboard changed HTC DEV meathod will not work
Hit thanks button if you find me helpful
sent from amazing HTC sensation using xda premium
above users are right
motherboard replaced
which means different imei
so htcdev method won't work for you anymore
EDIT: Problem solved
Ok, thanks, finally got S-OFF and root working
I also installed 4ext Recovery, but my last backup was made using TWRP-Touch-Recovery.
When I now try to flash TWRP using Goomanager it doesn*t work, now i tried flashing it via fastboot and i also get an error
Code:
C:\Users\***\Desktop\Sensation\toolkit\Data>fastboot flash recovery recovery.i
mg
sending 'recovery' (5472 KB)...
OKAY [ 1.402s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.721s
Can I either convert my backups to 4ext format, or is there another possibility to flash twrp?
niklas1407 said:
EDIT: Problem solved
Ok, thanks, finally got S-OFF and root working
I also installed 4ext Recovery, but my last backup was made using TWRP-Touch-Recovery.
When I now try to flash TWRP using Goomanager it doesn*t work, now i tried flashing it via fastboot and i also get an error
Code:
C:\Users\***\Desktop\Sensation\toolkit\Data>fastboot flash recovery recovery.i
mg
sending 'recovery' (5472 KB)...
OKAY [ 1.402s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.721s
Can I either convert my backups to 4ext format, or is there another possibility to flash twrp?
Click to expand...
Click to collapse
you have that error because probably you don't have a patched hboot version
that's why the fastboot command fails
actually post the bootloader details to confirm it
rzr86 said:
you have that error because probably you don't have a patched hboot version
that's why the fastboot command fails
actually post the bootloader details to confirm it
Click to expand...
Click to collapse
Code:
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012,17:33:34
What do I need to do to solve this issue?
niklas1407 said:
Code:
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012,17:33:34
What do I need to do to solve this issue?
Click to expand...
Click to collapse
i dont know why your trying to unlock with HTC DEV your already S-OFF :s Download the Hboot i attatched its from unlimited.io and put it on the root of your sdcard and reboot into bootloader accept the flash and then flash any recovery and your away
do as above user said
that is the patched hboot version
Related
Hi,
I have a Desire S with the following information
Code:
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011,14:58:38
FASTBOOT USB
...
When I tried to install CWM, I got the following error:
Code:
C:\>fastboot flash recovery cwm-4.0.1.4-saga.img
sending 'recovery' (4346 KB)...
OKAY [ 0.735s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.757s
Please help. Thanks!
=========================
Solution: I successfully changed to ENG with the HBOOT downloaded from http://forum.xda-developers.com/show....php?t=1113820
After that, successfully flashed the recovery from revolutionary's page using
Code:
fastboot flash recovery <recovery_file_name.img>
(*) remember to remote the <> sign
If I recall correctly you need to upgrade to the ENG bootloader first
Swyped from my Desire S using xda Premium
ben_pyett said:
If I recall correctly you need to upgrade to the ENG bootloader first
Swyped from my Desire S using xda Premium
Click to expand...
Click to collapse
Could you please help tell how to do that?
Thanks a lot!
The same way You were doing the recovery install.... Search for the hboot 0.98.2000 the rename the img to hboot.img (for simplicity) and place it with your fastboot flies, then boot your phone into fastboot and run the command;
fastboot flash hboot hboot.img
I'm unsure if this will help you, I'm just explaining how to change your hboot, but it shouldn't do any harm.
As you are soff you should be able to simply update to the ENG 98.2 using the following method
1) Copy the ZIP file containing hboot ENG to PG88IMG.zip into root of SD card
2) reboot into Bootloader, and answer yes when prompted where the PG88IMG will be updated.
Swyped from my Desire S using XDA Premium
ben_pyett said:
As you are soff you should be able to simply update to the ENG 98.2 using the following method
1) Copy the ZIP file containing hboot ENG to PG88IMG.zip into root of SD card
2) reboot into Bootloader, and answer yes when prompted where the PG88IMG will be updated.
Swyped from my Desire S using XDA Premium
Click to expand...
Click to collapse
Hi,
Where can I download that hboot ENG?
===========================================
Thanks, I successfully changed to ENG with the HBOOT downloaded from http://forum.xda-developers.com/showthread.php?t=1113820
After that, successfully flashed the recovery from revolutionary's page.
But, when I enter RECOVERY from HBOOT, it is still same - blackout, then vibrate, then the white screen with HTC - forever
Anyone help
hello everybody
I send my sensation back for waranty and now i have it back completely stock.
Is it possible to unlock the sensation without using the htcdev's method?? and if this isn't possible can somebody help me with using the htcdev's method because when i presse the begin to unlock button on there site nothing happened.
S-on
hboot: 1.27.0000
Latest stock rom (4.0.3)
I cant start on the htcdev.com/bootloader page the 'begin unlock bootloader button' when i press this button nothing happened
can somebody help me!! :'(
darretje said:
hello everybody
I send my sensation back for waranty and now i have it back completely stock.
Is it possible to unlock the sensation without using the htcdev's method?? and if this isn't possible can somebody help me with using the htcdev's method because when i presse the begin to unlock button on there site nothing happened.
S-on
hboot: 1.27.0000
Latest stock rom (4.0.3)
I cant start on the htcdev.com/bootloader page the 'begin unlock bootloader button' when i press this button nothing happened
can somebody help me!! :'(
Click to expand...
Click to collapse
Hi,
Have a go with THIS TOOLKIT
You can't unlock your Sensation "hboot: 1.27.0000" by HTC Dev method, nor by Revolutionary. Still no working solution. Same happened to me, nothing useful found till now.
freec1 said:
You can't unlock your Sensation "hboot: 1.27.0000" by HTC Dev method, nor by Revolutionary. Still no working solution. Same happened to me, nothing useful found till now.
Click to expand...
Click to collapse
Hi,
Check the post above yours.
The toolkit will allow this ,if you want.
malybru:
"Check the post above yours.
The toolkit will allow this ,if you want."
Revolutionary Does not support HBOOT 1.27.0000, so the toolkit won't help.
I have 1.27.0000 s-on.
I'm stucked at first step of S-OFF: HTCdev does not work, tried many times. Ends with failure message:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.141
So I can't unlock bootloader with JuopunutBear. First requirement is to unlock with HTCDev. So I think it won't work for me.
Idk if unrevoked works whit this device??
Sent From My Sexy Sensation.
shahkam said:
Idk if unrevoked works whit this device??
Sent From My Sexy Sensation.
Click to expand...
Click to collapse
Unrevoked does not support Sensation. Tried.
I found this in Android Development section, maybe helps someone to root HBOOT 1.27.0000 device:
[Guide] Root Official ICS ROM HBoot 1.27.000 Easely without S-Off
---------- Post added at 03:48 PM ---------- Previous post was at 03:37 PM ----------
In that section guys wrote that it worked for them.
I tried this method, but failed at first step again: HTC DEV onlock bootloader does not work!
C:\TEMP\a\HTC S\OneX root\One_X_All-In-One_Kit_v1.0\data>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.157s
I was told just keep trying, but no luck.
Anyway tried to flash recovery:
C:\TEMP\a\HTC S\OneX root\One_X_All-In-One_Kit_v1.0\data>fastboot flash recovery Recoveries/CWM5827.img
sending 'recovery' (4876 KB)... OKAY [ 1.195s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.826s
Will Revolutionary support HBOOT versions over 1.18.0000 ?
Hello,
I have a Desire S, I think it has been first S-OFF with Alpharev (hboot 6.98-1002), and then a RUU has been patched (14.01.401.2). From now, the phone isn't able to boot anymore, I only have access to fastboot/bootloader
I've tried to flash the official hboot using fastboot flash hboot hboot.img
but it has not been flashed :
sending 'hboot' (1024 KB)...
OKAY [ 0.207s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.028s]
finished. total time: 0.239s
I've tried with ENG HBOOT, also tried by puting PG88IMG.zip on my SD card, fastboot detect it, tried to flash it but again, bypassed.
I'm a bit lost now, maybe someone could help me
petoulachi said:
Hello,
I have a Desire S, I think it has been first S-OFF with Alpharev (hboot 6.98-1002), and then a RUU has been patched (14.01.401.2). From now, the phone isn't able to boot anymore, I only have access to fastboot/bootloader
I've tried to flash the official hboot using fastboot flash hboot hboot.img
but it has not been flashed :
sending 'hboot' (1024 KB)...
OKAY [ 0.207s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.028s]
finished. total time: 0.239s
I've tried with ENG HBOOT, also tried by puting PG88IMG.zip on my SD card, fastboot detect it, tried to flash it but again, bypassed.
I'm a bit lost now, maybe someone could help me
Click to expand...
Click to collapse
I think this post is in the wrong section, you should post it on the Q/A section
oups my bad !
Don't repost. I've 'reported' your thread asking for it to be moved.
The problem is that the hboot version (6.98.x) is higher than 2.02.0002. Either flash the official hboot with the dd if= of= method, or flash an eng hboot with a lower version (0.98.x or 2.00.2002) (also with the dd method, instructions can probably be found in the hboot threads) and flash the RUU again.
Edit: another option would be to flash hboot 7.00.1002 by the PG88IMG.zip method, and then flash the PG88IMG.zip version of the Ics RUU (search the dev section).
Problem is, using the dd if= of= method requiere adb, which is not possible in my case, I only have fastboot.
edit : i'm trying with 7.00.1002 by PG88IMG.zip
Ok so 7.00.1002 using PG88IMG had worked, but my phone does not boot.
I'm trying to reflash RUU, see if it solves the problem. Or maybe I'm not flashing the correct RUU ?
Reflashing RUU and the phone is booting again !
Is there any way to get back to stock S-ON hboot ?
petoulachi said:
Reflashing RUU and the phone is booting again !
Is there any way to get back to stock S-ON hboot ?
Click to expand...
Click to collapse
I think the only way would be the dd method (probably best flash a lower version number eng hboot, then flash the RUU again and it should overwrite everything).
Hi guys, first off I searched all over to find anyone who had the same problem, alas no luck so I decided to post this up if anyone can help. If my dumb ass missed or searched wrong to find the correct link please post it and remove this post. So I have been hacking and modding video game consoles for 5 years, with no problems whatsoever, until I decided to go to phones XD I wanted to root and flash my htc one x which is:
RE-LOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
originally a telus canadian phone. I flashed the phone to cyanogen and the flash took 3 seconds, as soon as I saw it take 3 seconds I knew what I had just done. I've been searching desperately for a RUU or OTA, called into HTC and Telus and they were of no help of course, HTC helped me clear my cache, restore system settings, and all this other fancy work but without any luck. I have tried going into recovery mode but it does not work from bootloader, my phone turns on, goes past the HTC logo then a phone with a little green arrow pointing at the phone appears for a couple mins before being replaced with a red triangle with an exclamation mark inside of it. I have downloaded the OTA and RUU for my phone, neither come with .exe files when I extract them, only boot.img files which I have tried to flash using a hex downloaded from this website but everything keeps failing. If anyone has any advice or a link to a step by step guide too fixing this it would be greatly appreciated, thanks,
Sam.
Once again if there is already a post like this go ahead and remove this I do not mean to spam the website!
How do you expect to flash anything with a locked bootloader?
Sent from my HTC One X using xda app-developers app
exad said:
How do you expect to flash anything with a locked bootloader?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
As I said its been RELOCKED, I can easily unlock bootloader again, when I flashed it was unlocked, only after messing up I decided to relock it
spikypsn said:
As I said its been RELOCKED, I can easily unlock bootloader again, when I flashed it was unlocked, only after messing up I decided to relock it
Click to expand...
Click to collapse
What you're going to want to do is flash the stock recovery and then run the ruu. Then go through the unlock process. I am not sure what exactly your problem is, but this should fix it.
RollTribe said:
What you're going to want to do is flash the stock recovery and then run the ruu. Then go through the unlock process. I am not sure what exactly your problem is, but this should fix it.
Click to expand...
Click to collapse
I ran the RUU and it comes up with this error XD, would you happen to know what the problem is? I tried reflashing Telus stock RUU and rogers RUU with the same radio, both came up with the same error, I also ran the OTA;S one for telus and one for rogers and they both did not work
sending 'zip' (644729 KB)...
OKAY [ 29.539s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 99.287s
K:\One_X_ATT_All-In-One_Kit_v3.0\data>
spikypsn said:
I ran the RUU and it comes up with this error XD, would you happen to know what the problem is? I tried reflashing Telus stock RUU and rogers RUU with the same radio, both came up with the same error, I also ran the OTA;S one for telus and one for rogers and they both did not work
sending 'zip' (644729 KB)...
OKAY [ 29.539s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 99.287s
K:\One_X_ATT_All-In-One_Kit_v3.0\data>
Click to expand...
Click to collapse
Hmm, while the toolkit should do it for you, that is the error encountered when your bootloader is not unlocked.
RollTribe said:
Hmm, while the toolkit should do it for you, that is the error encountered when your bootloader is not unlocked.
Click to expand...
Click to collapse
Awesome, did exactly that and I got 1 step closer but not exactly there yet =)) it gives me this error when i flashed the .zip file now, I am using the 3.17 telus OTA to flash with, btw I cannot figure out a way to mount my phone to my computer so I cannot install the zip or recovery on the phone, any tips would be great, thanks once again guys
sending 'zip' (644729 KB)...
OKAY [ 29.587s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 40.802s
C:\Users\Yahya\Downloads\One_X_ATT_All-In-One_Kit_v3.0\data>
Some info
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot getvar version-main
version-main: 2.20.502.7
finished. total time: 0.026s
And I have HBOOT-1.14.0002
I show
TAMPERED
RELOCKED
I can not seem to flash back to stock using htc_one_x_RUU_2.20.502.7_att_us_08022012.exe, it fails.
So then I get the rom.zip file from htc_one_x_RUU_2.20.502.7_att_us_08022012.exe and run...
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.983s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.433s
Im guessing this is because I followed the instructions (to relock the bootloader) before I ran htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
What would you recommend as my next step?
Im following this guide http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
I was able to unlock the bootloader... Now Im stuck here...
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.981s]
writing 'boot'...
OKAY [ 1.548s]
finished. total time: 2.531s
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.016s
"Please note that this method isn't 100% reliable and should be considered a last resort; there have been various reports of this not working due to system.img file being to large."
The error that you are getting seems to be indicative of a known issue. I am sure someone who knows whats up will be along shortly. At least you can take comfort in knowing you are not the only person with this issue. That is when things get scary lol.
Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.
Sent from my Evita
timmaaa said:
Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.
Sent from my Evita
Click to expand...
Click to collapse
I am S-ON and I do not have SuperCID.
LanceM said:
I am S-ON and I do not have SuperCID.
Click to expand...
Click to collapse
fastboot oem readcid
...
(bootloader) cid: HTC__621
OKAY [ 0.010s]
finished. total time: 0.010s
fastboot getvar cid
cid: HTC__621
finished. total time: 0.003s
When I try and flash
1.85 or 1.83
I get this error
<T111504><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
You can't RUU backwards unless you're s-off.
Sent from my Evita
timmaaa said:
You can't RUU backwards unless you're s-off.
Sent from my Evita
Click to expand...
Click to collapse
Ok Tim... So what do I do to get 2.20 on the phone, stock...
If you're wanting to run the at&t RUU you'll also need the at&t CID. Otherwise you need to run the RUU that corresponds with the HTC__621 CID. Why is it the 2.20 in particular that you want?
Sent from my Evita
Im not stuck on 2.20. I just want the phone back to stock.
Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.
Sent from my Evita
timmaaa said:
Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.
Sent from my Evita
Click to expand...
Click to collapse
Well, that is my question... What RUU is compatible with my CID? And can I change the CID to work for an AT&T RUU, because it seems like 621 is a tawian RUU. If I can, what do I need to change the CID too?
Did you change the CID to HTC__621? It doesn't look like an Evita CID.
Sent from my Evita
timmaaa said:
Did you change the CID to HTC__621? It doesn't look like an Evita CID.
Sent from my Evita
Click to expand...
Click to collapse
No, when I got the phone a while ago, I rooted and superCID'ed it. It was changed to 1111111, but now for some reason it has changed to 621, which I dont quite understand and has caused quite an issue for me trying to go back to stock.
The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?
Sent from my Evita
timmaaa said:
The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?
Sent from my Evita
Click to expand...
Click to collapse
I bought the phone in San Antonio at an AT&T store.... Way back when the phone just came out...
At that point, after XDA had root and SuperCID, I did those... And put CM10 on it... Through many upgrades and tinkering, somehow the phone got the CID 621. An Asian CID, I did NOT do this.
Regardless, it is fixed now. I followed the instructions in this thread to change the CID back to 1111111. It worked, then what I did was push the recovery and boot from 2.20 to the phone, then re-locked it.
At this point, I ran the 2.20 RUU and it took... Then I ran the 3.18 phone and now... QHSUSB_DLOAD
Off to http://forum.xda-developers.com/showthread.php?t=1966850
Now downloading linux...
I will fix this damn thing lol!
You pulled a classic megadoug. S on super Cid ruu strikes again. JTAG is the only way to fix it now
Sent from my HTC One XL
Yep. S-on + SuperCID + jb RUU = brick. So you'll need a jtag repair. It's worth tying the unbrick method but nine times out of ten it doesn't work.
Sent from my Evita