Hi,
Like, it seems, plenty of others, I messed up my phone by trying a custom ROM and then screwing up the "return-to-stock".
I have a T-Mo UK Sensation which was running GB 2.3.4 until I put Android Revolution HD 6.5.5 XE on it.
Basically I fell into the S-ON trap, and bricked the device. Wouldn't power on at all.
With help from Dexter from the unbrick project, I have managed to get the phone to load into Bootloader, but it won't load the Android OS, nor will it go into recovery.
I think the usual next step is to use latest RUU to flash a new ROM. Thing is, my phone is now S-ON and thinks it's a T-Mo UK phone again (CID T-MOB005, I think). And T-Mo UK's last released upgrade is ancient (RUU_Pyramid_TMO_UK_1.34.110.1). So there isn't a ROM that is new enough AND compatible with my CID number. I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2, but even that sounds like it'll be too old (I'm guessing it probably doesn't have HBOOT 1.27)
Could anyone advise if there's a way I can get my phone back?
Bootloader text as folows:
Code:
*** LOCKED ***
*** Security Warning ***
Pyramid PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17.33.34
Then the usual Vol Up, Vol Down instructions, and
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I go into Bootloader these options change to:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
But if I choose Recovery, it just reboots to Bootloader.
Would be really grateful if anyone can help me. I'm not v popular at home having spent hours trying to fix this mess (and getting pretty stressed about it!)
jezash said:
Hi,
Like, it seems, plenty of others, I messed up my phone by trying a custom ROM and then screwing up the "return-to-stock".
I have a T-Mo UK Sensation which was running GB 2.3.4 until I put Android Revolution HD 6.5.5 XE on it.
Basically I fell into the S-ON trap, and bricked the device. Wouldn't power on at all.
With help from Dexter from the unbrick project, I have managed to get the phone to load into Bootloader, but it won't load the Android OS, nor will it go into recovery.
I think the usual next step is to use latest RUU to flash a new ROM. Thing is, my phone is now S-ON and thinks it's a T-Mo UK phone again (CID T-MOB005, I think). And T-Mo UK's last released upgrade is ancient (RUU_Pyramid_TMO_UK_1.34.110.1). So there isn't a ROM that is new enough AND compatible with my CID number. I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2, but even that sounds like it'll be too old (I'm guessing it probably doesn't have HBOOT 1.27)
Could anyone advise if there's a way I can get my phone back?
Bootloader text as folows:
Code:
*** LOCKED ***
*** Security Warning ***
Pyramid PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17.33.34
Then the usual Vol Up, Vol Down instructions, and
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I go into Bootloader these options change to:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
But if I choose Recovery, it just reboots to Bootloader.
Would be really grateful if anyone can help me. I'm not v popular at home having spent hours trying to fix this mess (and getting pretty stressed about it!)
Click to expand...
Click to collapse
Hi,
I am not sure where exactly you want to end up.
But if you wanted to get an ICS ROM on your phone,try THIS THREAD
thanks for the suggestion. At the moment I just want a working phone. Don't really mind if it's ICS or not.
Just gone through the HTC Dev procedure. Was sceptical as adb devices didn't return any connected devices. But it got the code and I was able to get the token via email.
I sent the command fastboot flash unlocktoken Unlock_code.bin and it appeared to succeed. However, I didn't see the message in Step 13. The phone still shows bootloader and it still says ***Locked***.
The Step 13 message looks like an android OS thing - I wonder if I can't see it unless I can boot to Android?
Anyway, I pressed onto the section about flashing a recovery. Again, no device shows up in adb devices.
When I tried to flash the 4EXT recovery, I got an error message:
sending 'recovery' (6116 KB)... OKAY [ 1.507s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.298s
Does this mean that the unlock hasn't actually worked then?
jezash said:
thanks for the suggestion. At the moment I just want a working phone. Don't really mind if it's ICS or not.
Just gone through the HTC Dev procedure. Was sceptical as adb devices didn't return any connected devices. But it got the code and I was able to get the token via email.
I sent the command fastboot flash unlocktoken Unlock_code.bin and it appeared to succeed. However, I didn't see the message in Step 13. The phone still shows bootloader and it still says ***Locked***.
The Step 13 message looks like an android OS thing - I wonder if I can't see it unless I can boot to Android?
Anyway, I pressed onto the section about flashing a recovery. Again, no device shows up in adb devices.
When I tried to flash the 4EXT recovery, I got an error message:
sending 'recovery' (6116 KB)... OKAY [ 1.507s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.298s
Does this mean that the unlock hasn't actually worked then?
Click to expand...
Click to collapse
Hi,
Have you got the necessary drivers installed to use ADB.
Try using THIS TOOLKIT
It has the drivers,and an unlock section.
first of all confirm your CID
fastboot getvar cid command will give you cid
if its supercid (unlikely) or any other which has ICS ROM for it ..then you are lucky
other wise try the HTCdev method again...no need to get the unlock_code again
just use the one you got previously ...then reboot and see..hopefully it works
hi, thanks for various suggestions.
have tried the HTCDEV method a couple of times without success. I never see the Confirmation Screen shown in step 13 on the HTCDEV bootloader unlock procedure.
Definitely have the HTC drivers installed, have previously used adb successfully from this PC. Plugged in my old HD2 (running Android) and adb devices finds it ok.
Checked my CID as suggested, it's T-MOB005.
Tried downloading the toolkit suggested by malybru and didn't get any further - I think it just does the same thing (runs the HTCDEV unlock process).
One thing that's odd. I tried flashing 4EXT Recovery from command prompt. A "loading" bar showed up on the right side of the screen of the phone like it was working, but then I get the "signature verify fail" shown above.
I guess I can't use Revolutionary S-OFF as I can't boot to Android.
What can I do? Should I try this: http://forum.xda-developers.com/showthread.php?t=1469296 - Edit - actually it seems like that still needs the HTC DEV unlock to work ... which seems to be my problem :-(
have tried the HTCDEV unlock method quite a few times now. In the command prompt it appears to work successfully, but I never get the Android-like confirmation screen (I think this must be because my phone will not currently boot to Android).
As I think I need to unlock before I can flash anything else, I am stuck. :-(
Does anyone have a suggestion for another way to unlock it?
Given that T-Mobile UK have not given any date for releasing ICS, I have no notion of when I can fix my phone. Hence considering sending for repair - presumably replacing CPU or something would fix it? Any idea how much this would cost? (Using my old HD2 running a somewhat unstable version of Android is starting to drive me crazy).
jezash said:
Given that T-Mobile UK have not given any date for releasing ICS, I have no notion of when I can fix my phone. Hence considering sending for repair - presumably replacing CPU or something would fix it? Any idea how much this would cost? (Using my old HD2 running a somewhat unstable version of Android is starting to drive me crazy).
Click to expand...
Click to collapse
Can you pop in the irc? We can do some last tries before you send it for repairs
Sent from my pyramid.. Through blazing fast sonic waves
hi ganesh - am in the IRC now. only for the next 15 minutes or so. if you think there is something remaining that is worth trying i can come back tomorrow.
thanks for your reply.
jezash said:
hi ganesh - am in the IRC now. only for the next 15 minutes or so. if you think there is something remaining that is worth trying i can come back tomorrow.
thanks for your reply.
Click to expand...
Click to collapse
EDIT:based on these values ..seems like something can be done..remember ..this is all to avoid extra money to get it repaired
can you post some more details?
fastboot getvar all (except IMEI and SERIAL NO )
Hi Ganesh,
Thanks for your reply. Here are the details from my phone:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: 11.22.3504.07_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.34.206.1
INFOserialno:
INFOimei:
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: T-MOB005
INFObattery-status: good
INFObattery-voltage: 4032mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.480s
Cheers
now that we know that the stock rom flashed .(before brick)
get the 1.50 RUU and try to RUN it
how you do that
phone in fastboot ...connect it to pc and run the RUU.exe
if it still dint worked
then extract the rom.zip form RUU
http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/
then keep the rom.zip in adb folder and flash it manually
manual flash steps
1.fastboot erase cache (if its failing ...ignore it)
2.fastboot oem rebootRUU (black screen with silver HTC)
3.fastboot flash zip rom.zip (pastebin the output if failed)
4.fastboot reboot-bootloader (check the bootloader there ..changed or not )
hi ganesh,
latest rom available that i can find (for t-mo uk) is 1.34. That ok?
cheers
EDIT: ok, so trying to run the RUU, it looks like it's going ok, starts sending the ROM to the phone, and then aborts with a ERROR [155]: UNKNOWN ERROR.
Will try the manual steps you gave.
jezash said:
hi ganesh,
latest rom available that i can find (for t-mo uk) is 1.34. That ok?
cheers
Click to expand...
Click to collapse
yes try that first if it fails (both ways )
get the updated RUU
I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2
Click to expand...
Click to collapse
from football ^
and use that and repeat the rom flash again
hi ganesh,
ok, here's what came back when i tried to flash manually.
C:\adb>fastboot flash zip rom.zip
sending 'zip' (381007 KB)... OKAY [ 51.085s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 103.934s
EDIT:
when I disconnected USB from phone, it also displayed error message: Hboot version is older / Update fail!
will contact football again as you suggested.
2nd EDIT:
my bootloader displays HBOOT-1.27.0000 ... isn't the problem still that even 1.50 has an older HBOOT than this, and hence the rom flash fails?
jezash said:
hi ganesh,
ok, here's what came back when i tried to flash manually.
C:\adb>fastboot flash zip rom.zip
sending 'zip' (381007 KB)... OKAY [ 51.085s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 103.934s
EDIT:
when I disconnected USB from phone, it also displayed error message: Hboot version is older / Update fail!
will contact football again as you suggested.
Click to expand...
Click to collapse
yeah thats expected ...can you try one more thing ..can you just remove the hboot.nb0 file from the rom.zip (have a copy of it somewhere safe ..so that you can add later when required)
EDIT: also you need to edit the android-info.txt file ..change the HBOOT inside with te one you have i.e. 1.27.0000 then make the zip again then try flashing it sorry my bad there wont be HBOOT in the android-info.txt ..just cidnum ,modelid etc etc
then do the flash of rom.zip again
weird. I couldn't find that file in the rom.
the contents are as shown here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT - oh, duh, the longer file name that ends as you said. sorry. will try now.
ok, tried this. unzipped, removed the hboot_Pyramid_8x60_1.17.0011_20110602_signedbyaa.nb0 file, rezipped. followed the four manual flash steps that you suggested, and got the following message in cmd:
C:\adb>fastboot flash zip rom.zip
sending 'zip' (375099 KB)... OKAY [ 50.217s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 100.357s
Football can get me a TMO-UK RUU 1.50. There is a cost, apparently. Hence wondering if there's a reason why 1.50 should work when 1.34 doesn't, give - if i understand correctly - that neither is HBOOT 1.27.
Related
I'm stuck
I got my Sensation back from repairs with 1.18 and pressed on and rooted. I now run rooted stock 2.3 with S-On but unlocked using HTC method (Revolutionary didn't work for some reason) and ClockWorkMod with SuperCID
This is where the problems started
I can't get S-Off
I have tried everything I can find (literally been on this for hours). I've tried:
Revolutionary 0.4pre4 (which fails to gain root - possibly because I've already got root)
HTCSuperTool (v3 of which appears to be broken, btw)
Downloading various firmwares and flashing them (using the PG58img.zip/bootloader method)
I've even tried running the RUU exe and pulling the rom.zip, renaming that and dropping that in the SD card
Running the RUU (both the latest T-Mobile UK and the latest ICS version)
The weird thing is that it reads the PG58img.zip files, loads them, starts to parse them then goes back to bootloader and doesn't read them again unless I reboot the bootloader
Update: Re-locked the bootloader and still can't run the RUU for ICS
Any ideas?
Anyone? Please help!
I've just been through all this after getting my phone back from repair. Mine came back with t-mobile branded rom version 1.50.110.2 and wouldnt s-off with revolutionary. Luckily the phone still had supercid so i flashed RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.9035.00U_10.15.9035.02_2_release_228602_signed.exe and revolutionary finally worked. You can read my thread here http://forum.xda-developers.com/showthread.php?t=1538324
Thank you, I'll try that (if I can ever get a slot on the FileFactory download server...)
I've got a 1.17 hboot.img from Kohr-Ar (used in one of the PG58IMG.zips), could I use fastboot flash hboot hboot.img to flash that or would i be left with a brick?
Ok, got the ROM and tried to flash but I forgot that I put the CID back to the T-Mobile CID. Now, I can't change the CID, I always get:
>fastbooot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.079s]
finished. total time: 1.080s
Any ideas now?
pnlrogue1 said:
Ok, got the ROM and tried to flash but I forgot that I put the CID back to the T-Mobile CID. Now, I can't change the CID, I always get:
>fastbooot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.079s]
finished. total time: 1.080s
Any ideas now?
Click to expand...
Click to collapse
did u find any solution , i am exactly in same situation i also did exactly same thing now stuck
Try to run ruu ???
Sent from my HTC Sensation 4G using xda premium
Afraid not. I tried all sorts of things - best I can say is do NOT try to flash your bootloader using the fastboot method - found that out the hard way...
I think flashing an alternative ROM may help but I'm not sure. Maybe contact the devs of Revolutionary - it just wants a way of skipping the Zerging Root stage in V0.5...
Find my post and do it step by step run ruu then change cid
Sent from my HTC Sensation 4G using xda premium
My phone is not rooted. I tried to update to ICS but after updating process completed it is now stuck at beats logo. Help please
Since this is the official OTA, I don't really know what would have went wrong. I guess all I could think of doing is rebooting the phone and waiting a while. Considering new ROMS take a long time on first boot. If that doesn't work, I guess call your carriers tech support.
You can download and run the 3.32.401.105 RUU to restore it to a factory state with ICS.
Sent from my HTC Sensation 4G
GROGG88 said:
You can download and run the 3.32.401.105 RUU to restore it to a factory state with ICS.
Sent from my HTC Sensation 4G
Click to expand...
Click to collapse
This should be the right solution for you.
And if you want to do this, all required info can be found here.
If you are S Off, I recommend you keep S Off & don't do the last step.
Problem
When i runn RUU on pc it shows error 132 saying signature write error.
If I extract the zip file and run through bootloader the setup aborts after the yellow bars fills up.
When I go to recovery it says cannot open e:cache ........
alirana90 said:
When i runn RUU on pc it shows error 132 saying signature write error.
If I extract the zip file and run through bootloader the setup aborts after the yellow bars fills up.
When I go to recovery it says cannot open e:cache ........
Click to expand...
Click to collapse
Plash the PG58IMG like this: http://forum.xda-developers.com/showpost.php?p=26673647&postcount=12
kgs1992 said:
Plash the PG58IMG like this: http://forum.xda-developers.com/showpost.php?p=26673647&postcount=12
Click to expand...
Click to collapse
again signature error C:\and>fastboot flash zip PG58IMG.zip
sending 'zip' (427312 KB)...
OKAY [ 58.032s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 114.945s
alirana90 said:
again signature error C:\and>fastboot flash zip PG58IMG.zip
sending 'zip' (427312 KB)...
OKAY [ 58.032s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 114.945s
Click to expand...
Click to collapse
dude get the RUU based on your country/carrier
or first get the cid
to get it keep the device in bootloader connect it to pc
and type "fastboot getvar cid" without quotes
that should give you the cid and based on that get the corresponding RUU
repost the cid here..ppl might find it for you
ganeshp said:
dude get the RUU based on your country/carrier
or first get the cid
to get it keep the device in bootloader connect it to pc
and type "fastboot getvar cid" without quotes
that should give you the cid and based on that get the corresponding RUU
repost the cid here..ppl might find it for you
Click to expand...
Click to collapse
HTC__001, he has the right RUU.
Anyway, helping him through it.
kgs1992 said:
HTC__001, he has the right RUU.
Anyway, helping him through it.
Click to expand...
Click to collapse
then the only other thing that can cause signature fail is modelid...
may be he is trying to flash XE RUU on normal one or vice versa
What a mess I've made. I've searched everywhere on xda and google with every combination of words I could think of and no answer yet...
Symptoms:
Can't re-unlock bootloader through HTCDev
Prior to relocking I was unable to install roms after a failed miui install attempt
Specs:
S-ON
HBOOT 1.14.0005
T-Mobile US
now running 4.04 with sense 4.1 software 2.35.531.12710RD
History:
Was rooted, bootloader unlocked, running cm10.1 smoothly and many roms before it smoothly
decided to try miui 3.4.5 for fun and install failed and phone stuck on boot screen
was able to start up CWM recovery but would loop back to boot screen too fast to use
used an ruu to go back to stock and start over - installed successfully. even able to ota update so did it
tried to run CWM and reinstall cm10.1 and install failed as did install of any roms
then tried to pursue s-off to be able to install roms again
did super cid successfully
tried s-off but messed up and fashed both zip files instead of flashing PJ4010000-OneS.zip and then unpacked soffbin3 (if that makes sense)
i did get the correct errors though but the install failed to perform the last shell command likely due to no su files installed
at some point i locked the bootloader and now cant unlock it even after flashing cid back to T-MOB010 so i cant reroot
I keep getting the error 150 at htc dev when i put in my token
The phone runs fine on stock rom but after all the changes my old unlock token no longer works and htc wont let me unlock so i cant flash roms. Does anybody have any advice on how to pursue to allow me to go back to CM10.1? Antheor way to unlock bootloader without htc or even another way to s-off?
Thank you
Camboozle said:
...The phone runs fine on stock rom but after all the changes my old unlock token no longer works and htc wont let me unlock...
Click to expand...
Click to collapse
A long shot but did you issue the fastboot get_identifier_token command again after all this mess? Could be a different Unlock Token now that you've done all these changes....?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes I did pull the new identifier. Still no go. Thanks for the reminder though.
I did find an article mentioning something about HTCDev blocking supercid but I read another article dated months later that contradicted the first article and see people are still using supercid and unlocking so I'm not sure what to believe.
I've also read of people having similar errors with the site. And some of them gave there token serial to someone else to try from another computer, and it worked.
I'de give it a try for you if you want. :fingers-crossed:
bmb1983 said:
I've also read of people having similar errors with the site. And some of them gave there token serial to someone else to try from another computer, and it worked.
I'de give it a try for you if you want. :fingers-crossed:
Click to expand...
Click to collapse
Sorry I ended up buying a new phone and didn't see your response. It sounds feasible it may work on another computer. Here is the token and thanks for the help.
<<<< Identifier Token Start >>>>
1700AFDC35C0F82BDA1C7D4E2DA1701C
D6CA28DD3B33DCB09D4250509789B86D
4C7BFF879A3CA0BA463E620CCEE9BE8D
A7203AB6C13F99932FD0CA9B9E2E2373
550463EFED6DF4D329000585DB278470
A753C1F674C0969BD5E3229DF526FBEC
C949BA53604319420CE0441874446C78
7B3356AB59746E140A1FD50207A45BF6
93A3F204FB111045DD77379E930FD675
667463DCCDDFA1400761799EF37144ED
1EA59F82CACA2022AD20F5342658F891
8EFFE8CAC5A619F7CA1F47CF22BD6B30
8FA33533B08831B1ECEB012B55D11955
21293A0337576353E621CCA6D5A50CE8
16353F9F2B0EEE1A66D62E6D336A790E
D4C6B64A99889BC3CF66367451564F84
<<<<< Identifier Token End >>>>>
Well, that didn't work. I tried several times and a couple different computers. Error code 150. Not sure what else to try. Sorry Mate!
EDIT: Reading more into this, there may be something else going on. You said your stock, so have you applied the latest update? To get the most recent HBOOT? If you haven't, the try it. That would change your Token. If you have already done that, then try finding an RUU for your provider that has a different or lower HBOOT.
Just a thought. Its peaked my curiosity now. LoL
definitely don't upgrade. the ota blocks supercid. one thing I've read is to try 222222 or however many instead of 111111 when getting the unlock token.
or are you the step before? still locked and s-on? how did you change your Cid after relocking? can you check your Cid in fast boot and tell us what it says? perhaps you're not in the exact situation you think.
jamus28 said:
definitely don't upgrade. the ota blocks supercid. one thing I've read is to try 222222 or however many instead of 111111 when getting the unlock token.
or are you the step before? still locked and s-on? how did you change your Cid after relocking? can you check your Cid in fast boot and tell us what it says? perhaps you're not in the exact situation you think.
Click to expand...
Click to collapse
i'm having the same problem, and managed to change the cid 4 times when the phone was relocked and on ICS, with write cid commend in adb
jamus28 said:
definitely don't upgrade. the ota blocks supercid. one thing I've read is to try 222222 or however many instead of 111111 when getting the unlock token.
or are you the step before? still locked and s-on? how did you change your Cid after relocking? can you check your Cid in fast boot and tell us what it says? perhaps you're not in the exact situation you think.
Click to expand...
Click to collapse
hes not supercid any more and he has a new phone now anyway. just trying to help more out of curiosity. thanks though!
bmb1983 said:
hes not supercid any more and he has a new phone now anyway. just trying to help more out of curiosity. thanks though!
Click to expand...
Click to collapse
I'm still working on it out of curiosity too and to learn. The new phone is just to keep me from going crazy after all my failures
Here's what I see:
*** RELOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14, 2012 .........
Android 4.1.1
Sense 4+
Software 3.14.531.11 710RD
Attempt to change supercid:
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>fastboot
oem writecid 22222222
...
(bootloader) ville_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) sdhw_7xxx_open: id=0ard already power onn
FAILED (unknown status code)
finished. total time: 1.038s
Then it locks up and needs a reboot in to bootloader
Read CID
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>fastboot
oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.010s]
finished. total time: 0.010s
Attempt superuser - which fails likely because ruu removed superuser
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Attempt to flash a recovery - which I didnt expect to work without bootloader unlock
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>fastboot
flash recovery recovery-clockwork-touch-5.8.3.1-ville.img
sending 'recovery' (6616 KB)...
OKAY [ 0.975s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.631s
Attempt to flash original boot.img
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>fastboot
flash bootloader boot.img
sending 'bootloader' (16384 KB)...
OKAY [ 1.795s]
writing 'bootloader'...
(bootloader) signature checking...
(bootloader) signature checking...
FAILED (unknown status code)
finished. total time: 2.814s
That's just a few things just so you get the idea of what I'm seeing. I have no clue what unkown status code means and it seems the ruu has stopped me form doing what little I could do after relocking the bootloader (like an idiot).
Thanks a ton for the comments though everyone and thanks for trying the token bmb1983. I thought it sounded feasible.
Aaaahhhhh.....NOW I see what your up against. Seeing you can't unlock your bootloader you need another way to gain root, so you can superCID again so you can S-OFF. THEN your back in business!
Have you tried gaining root manually with linux? Might work.
Check out this link. ---> http://www.erodov.com/forums/how-root-any-android-device-manually/43325-page2.html
If you can get root that way, then you should be able to superCID again to get S-OFF. You don't need to be unlocked to get superCID.
Camboozle said:
Attempt to flash original boot.img
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>fastboot
flash bootloader bit.img
sending 'bootloader' (16384 KB)...
OKAY [ 1.795s]
writing 'bootloader'...
(bootloader) signature checking...
(bootloader) signature checking...
FAILED (unknown status code)
finished. total time: 2.814s
Click to expand...
Click to collapse
Not that it would make a difference at this point, but fastboot flash bootloader bit.img is the wrong command, it is fastboot flash boot boot.img
Now, the first thing you need to do is unlock the bootloader...that outdated technique above will not work on this phone. I do believe if you changed your cid at some point, you will need a new unlock code...have you tried to get a new one?
The OTA should not affect the bootloader unlock, but what it would affect is writing to 0p4 in order to change to super cid, so if you can't do that, S-OFF is out of the question. Focus on getting that bootloader unlocked.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
ryanshew said:
Not that it would make a difference at this point, but fastboot flash bootloader bit.img is the wrong command, it is fastboot flash boot boot.img
Now, the first thing you need to do is unlock the bootloader...that outdated technique above will not work on this phone. I do believe if you changed your cid at some point, you will need a new unlock code...have you tried to get a new one?
The OTA should not affect the bootloader unlock, but what it would affect is writing to 0p4 in order to change to super cid, so if you can't do that, S-OFF is out of the question. Focus on getting that bootloader unlocked.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Click to expand...
Click to collapse
we can't get it unlocked since htcdevs is giving an error every time we send the token. one thing that i have noticed on my phone that when it is fully discharged and i plug it on my pc it gets on qhsusb mode, and i tried to enumerate the partition with ubuntu but it can only see 4 partitions
Sent from my HTC One S using xda app-developers app
alexskin said:
we can't get it unlocked since htcdevs is giving an error every time we send the token. one thing that i have noticed on my phone that when it is fully discharged and i plug it on my pc it gets on qhsusb mode, and i tried to enumerate the partition with ubuntu but it can only see 4 partitions
Click to expand...
Click to collapse
Have you tried getting a new unlock token?
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
yes and htcdevs delivers error 150 every time I send the token
Sent from my HTC One S using xda app-developers app
alexskin said:
yes and htcdevs delivers error 150 every time I send the token
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
You got a new one attached to a new email?
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
I can't get a new one, I'll post a token and maybe you could try to get unlock code
Sent from my HTC One S using xda app-developers app
---------- Post added at 04:22 PM ---------- Previous post was at 04:10 PM ----------
<<<< Identifier Token Start >>>>
36F7AEAEE0591D136A4C76B3D2A329C6
2536D2947D59CE93E5B637F375103AFD
F648CCE2C65FECF579097E4CE1A2BF65
98D64B61F3697F0A03655D69A05F1B88
F3A39DEAA5EC86F7321524A4C2ED6F21
D2AC158C2F72A43775A3B0FA97A01167
7017033684CF338B1FF9A183138D13F2
B3EF7DD6199F1D059E21580F55A4AD15
1A896179350B66E09A8DB53095300114
9B941B097FBC400DCF5CEF8E13C335D2
A646B5BC23DD4C51384858F564E2916B
8105AD42213017D2B84C8253446FC15E
9905DD2BDB11257D4F78B6674B4E2292
ED02FFF3000E3857C6C4801915A7B30A
328A09B29A5E9BA293421BF7F288B083
E9E8331AA1A1CA3290B4732B71AF831B
<<<<< Identifier Token End >>>>>
alexskin said:
I can't get a new one, I'll post a token and maybe you could try to get unlock code
Sent from my HTC One S using xda app-developers app
---------- Post added at 04:22 PM ---------- Previous post was at 04:10 PM ----------
<<<< Identifier Token Start >>>>
36F7AEAEE0591D136A4C76B3D2A329C6
2536D2947D59CE93E5B637F375103AFD
F648CCE2C65FECF579097E4CE1A2BF65
98D64B61F3697F0A03655D69A05F1B88
F3A39DEAA5EC86F7321524A4C2ED6F21
D2AC158C2F72A43775A3B0FA97A01167
7017033684CF338B1FF9A183138D13F2
B3EF7DD6199F1D059E21580F55A4AD15
1A896179350B66E09A8DB53095300114
9B941B097FBC400DCF5CEF8E13C335D2
A646B5BC23DD4C51384858F564E2916B
8105AD42213017D2B84C8253446FC15E
9905DD2BDB11257D4F78B6674B4E2292
ED02FFF3000E3857C6C4801915A7B30A
328A09B29A5E9BA293421BF7F288B083
E9E8331AA1A1CA3290B4732B71AF831B
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
Your token gave a 150 error as well. I really think that your only option is to try and root manually through LINUX, then SuperCID, then S-OFF and then change your HBOOT. That will give you a different token to try and unlock your Bootloader. Worth a shot! :good:
bmb1983 said:
Your token gave a 150 error as well. I really think that your only option is to try and root manually through LINUX, then SuperCID, then S-OFF and then change your HBOOT. That will give you a different token to try and unlock your Bootloader. Worth a shot! :good:
Click to expand...
Click to collapse
Nothing to lose so I'm installing linux now and trying it. Cool how I can install linux to a microsd card!!! Thanks for the link btw
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>
Hi, i have a htc sensation with the following details its S-on , htc dev relocked bootloader because of going to stock ..
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.53 (before flashing the ruu it shoes 1.24.0)
INFOserialno: SH19WV803357
INFOimei: 3583..............
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 3784mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.484s
i had cm9 installed on it but it was eating a lot of battery i switched to other versions.. i tried other cm 10 ,10.1 and 10.2 , ciper 3.12, 1.6.3, and hd revoloution 7.5 i gues.. and it all started after flashing the viper rom ..
i installed various roms .. and i always did smartflash enabled before installing my rom, and then fastboot the img file to it.. but after removing the viper 3.1.2 rom .. i got stuck in serious bootlop..
I flashed other roms but still bootloop..
now i tried to go back to stock following this guide here http://forum.xda-developers.com/showthread.php?t=1672425 i flased the RUU for my HTC_001 RUU file name is ((RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed)) .. but even with this RUU file i get bootloop..
HTC screen comes and then the htc splash screen and it reboots .. and it continues.. " .. (before flashing i did fast oem lock thing)
i am stuck with this phone here need a working one again .. please help me .. i dont want to spent extra 1000buks here.. already spent 4.5k(rupes) to get this mobile from my last one .. which was a htc desire c (screen prob) .. now please help me get this thing working
i am already having sleepless nights
no one here to help
dxbboy said:
no one here to help
Click to expand...
Click to collapse
I`m a noob but, heck...erase everything from root of your SD card...some files can force loop cycle (when you are in bootloader)
Can you boot into Fastboot and Recovery ?
silentvisitor said:
Can you boot into Fastboot and Recovery ?
Click to expand...
Click to collapse
as i tried to go back to the stock ... i had to locked my boatloader.. but yes i can get into fastboot but when i go into recovery i see blackscreen with mobile pic in center with an arrow above it + a bar loading at the bottom with a sdcard like sign..
At this point to get your phone operational I would download the appropriate RUU for your phone and reimage it to get it working again.
I know you flashed the 3.33 RUU. What I mean is try the 3.32 RUU
Sent from my HTC One using xda app-developers app
Kohr-Ah said:
At this point to get your phone operational I would download the appropriate RUU for your phone and reimage it to get it working again.
I know you flashed the 3.33 RUU. What I mean is try the 3.32 RUU
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
yes i am currently downloading the 3.32.401.1 RUu to give it a try .. as my cid is htc_001 and wwe :xx.xx.401.x
do i have to flash a new rom after this or with this RUU the phone will boot ? :S
i relocked the bootloader for RUU ..but when type my token number in htc dev it gives error now lets just wait to see what this RUU does
dxbboy said:
yes i am currently downloading the 3.32.401.1 RUu to give it a try .. as my cid is htc_001 and wwe :xx.xx.401.x
do i have to flash a new rom after this or with this RUU the phone will boot ? :S
i relocked the bootloader for RUU ..but when type my token number in htc dev it gives error now lets just wait to see what this RUU does
Click to expand...
Click to collapse
see if it will boot
i tried RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed
but it gave error 140 bootloader version error and on my device it shows ruu main version is older update fail
dxbboy said:
i tried RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed
but it gave error 140 bootloader version error and on my device it shows ruu main version is older update fail
Click to expand...
Click to collapse
What about reunlocking the bootloader (Can always relock it right?),then run the 3.33 RUU again or flasha cyanogenmod rom again and see if it boots?
Usually boot loops are simple. Like wiping dalvik and cache solves it but that is on a rom basis not a stock RUU Basis.
Kohr-Ah said:
What about reunlocking the bootloader (Can always relock it right?),then run the 3.33 RUU again or flasha cyanogenmod rom again and see if it boots?
Usually boot loops are simple. Like wiping dalvik and cache solves it but that is on a rom basis not a stock RUU Basis.
Click to expand...
Click to collapse
about reunlocking .. i visited the htc dev site.. i entered my token number.. it gave error ..that i cannot be unblocked blabla.. how do i reunlock it ? locking is ya its done with a single command... plus
i wanted to know if i flashh 3.33RUU which i did earlier, do i have to flash a rom just after this or does the RUU have a rom inside the exe, i am asking because when you go to temp folder you see a rom.zip file which many ppl suggest to flash via fastboot if normal ruu flash isnt working ?
i am trying to flash the rom.zip from 3.32 now .. hope it doesnt give the bootloader error here
nops its a negative result
C:\Documents and Settings\Muffi\Desktop\ADB_Fastboot_Windows>fastboot flash zip
rom.zip
sending 'zip' (430184 KB)... OKAY [ 63.031s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 141.625s
((FAILED (remote: 43 main version check fail)
Your device is S-ON & you are trying to use an RUU that has software number less than your current software number.))
i guess the error is there because i flashed the 3.33 RUU ?? am i stuck with it .. how to start this phonee(
dxbboy said:
i am trying to flash the rom.zip from 3.32 now .. hope it doesnt give the bootloader error here
nops its a negative result
C:\Documents and Settings\Muffi\Desktop\ADB_Fastboot_Windows>fastboot flash zip
rom.zip
sending 'zip' (430184 KB)... OKAY [ 63.031s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 141.625s
((FAILED (remote: 43 main version check fail)
Your device is S-ON & you are trying to use an RUU that has software number less than your current software number.))
i guess the error is there because i flashed the 3.33 RUU ?? am i stuck with it .. how to start this phonee(
Click to expand...
Click to collapse
the ruu.exe contains a rom.zip too
extract the one from 3.33 and flash it manually from bootloader or via fastboot command
tried that already, thats why you are seeing the firmware in my log as 3.33.. but i notiches the baseband is unavailable.. might that be a problem ?
none of the given instruction helps :S what should i do ? i flashed the 3.33 rom from RUU + from fastboot just after RUU still the bootlop, it reaches htc splash and restarts .. n goes on n on n on..
UPDATE : i relocked my bootloader via htc dev, i installed 4ext again .. i cleard factory reset, cache dvlkcache, format partition expt sdcard... this time i installed ((rmk-pyramid-stock_ics_3.32.401.3-v1)) with the smartflash enabled .. i installed, booted back to fastboot , flashed the boot.img.. and it still get stuck on the htc splash screen .. a tone come and it restarts .. ..
Update 2 : i installed cm-10.2-20130929-Sultan-pyramid , flasht boot.. now cyanagebnod circles spins and its booted .. i didnt receive a bootloop yet but inside the settings it shows unknown baseband and i dont have my phone signals
update 3 : still those bootloops as i can sometime bootup.. i am going to try to get S-off using juopunutbear ..
dxbboy said:
none of the given instruction helps :S what should i do ? i flashed the 3.33 rom from RUU + from fastboot just after RUU still the bootlop, it reaches htc splash and restarts .. n goes on n on n on..
UPDATE : i relocked my bootloader via htc dev, i installed 4ext again .. i cleard factory reset, cache dvlkcache, format partition expt sdcard... this time i installed ((rmk-pyramid-stock_ics_3.32.401.3-v1)) with the smartflash enabled .. i installed, booted back to fastboot , flashed the boot.img.. and it still get stuck on the htc splash screen .. a tone come and it restarts .. ..
Update 2 : i installed cm-10.2-20130929-Sultan-pyramid , flasht boot.. now cyanagebnod circles spins and its booted .. i didnt receive a bootloop yet but inside the settings it shows unknown baseband and i dont have my phone signals
update 3 : still those bootloops as i can sometime bootup.. i am going to try to get S-off using juopunutbear ..
Click to expand...
Click to collapse
for S-OFF you need the stock rom.link in my signature.i don't know if it works with other rom
and something else.when you are enabling smartflash don't flash after that the boot.img
you are doing the same step twice
just downloaded the file from your signature.. Sensation_3.33.401.53_deodexed : flashed it ok it booted after a couple of heartbeating bootlops ..first time it took alot of time to load.but it booted atleast but then again stuck there with bootloop, and now i got my signals again.. but bootloop is killing me .. 20,.30 times bootlop then a single start then again bootloop
+ i wanted to know ,, if the joupnutbear will work on 3.33 ?
any way .. couldnt get though the process.. just got fedup.. so gave it in a market to repair.. hope they fix it
no that guy in the market was a noob .. he just installed the stock that i installed earlier and send the mob back... ill have to do it ... i wana ask .. how can i run jupunetbear if i cant bootup.. alot of bootloping is there
hey mate... .. i was able to make it s-off using the jp windows guide.. but i still have those loops.. some time.. like , 3, 4 times a day ..