So tried to update when the HBOOT 1.20 firmware leak came out and the update failed. I panicked and did something stupid, while trying to revert to stock I managed to remove SuperCID and put S-ON back on. For awhile I was stuck in bootloader loop. Finally I used htcdev to unlock bootloader and now I have custom recovery and able to flash custom ROMs.
One problem, no WIFI with latest ROMS and I absolutely cannot flash anything that seems to touch HBOOT.
RUUs do not work (black HTC screen, show security failure, update failed after USB is disconnected). RUU log shows unknown failure.
P58IMG.zip (with older or newer HBOOT, or repackaged RUU, does not matter) simply return to the bootloader with no messages.
Fastboot flash attempts fail with error 99.
modelid: PG5810000
cid: T-MOB010
bootloader shows UNLOCKED HBOOT 1.20 S-ON
Please help ! I need either a solid idea how to downgrade so I can revolutionary or at the very least an idea on how to fix WIFI.
I did the same thing, semi-bricked in until I went to htcdev.....as far as your wifi goes, that may be fixed with a new radio...but your is the same as mine and my wifi is working fine, it takes a L O N G time to connect after finding a network though...no clue how to fix your wifi my friend. I have been and still am searching all day for a solution, I think if we can figure out how to get our HBOOT back to 1.18 or below we can use Revolutionary and start from scratch...but this seems to be a problem no one has come up with a fix for. If you find anything let me know and I will do the same.
Hello,
I think the problems that you are facing are due to "S-ON" and the Radio. Try flashing a new radio and try attaining S-Off from HERE
The problem is due to S-ON and mismatched kernel. I cannot however flash radio as 1.20 does not support partial flashes. I guess I am stuck waiting for either official ICS or revolutionary update.
silverion said:
RUUs do not work (black HTC screen, show security failure, update failed after USB is disconnected). RUU log shows unknown failure.
Click to expand...
Click to collapse
Can you try again using your original RUU, which part does it stop or says fail?
silverion said:
The problem is due to S-ON and mismatched kernel. I cannot however flash radio as 1.20 does not support partial flashes. I guess I am stuck waiting for either official ICS or revolutionary update.
Click to expand...
Click to collapse
Have you tried downgrading the RUU to 1.17?
Here is the snippet of the RUU log (TMOUS 1.27.531.2). On the HBOOT screen it says Security Fail! Update Fail!
<T100344><DEBUG><OUT>sending 'zip' (388341 KB)... OKAY</OUT>
</DEBUG></T100344>
<T100344><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T100344>
<T100345><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T100345>
<T100345><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T100345>
<T100345><DEBUG><OUT>FAILED (remote: 99 unknown fail)</OUT>
When attempting to downgrade to 1.17 via P58img.zip it simply returns to the menu after "parsing".
Wow. Have u tried the img from a diff source?
Sent From My steak using A1 steak sauce app (Sensation)
Try using the ruu.exe to downgrade all the way to 1.17. There will be at one time you will get stuck with some error(i forgot, but i do get that), so simply just follow what the the guide asked you to. Remember there will be one time where it will asked you to removed the battery, do remove and put in back but instead of turning on as per normal what you need to do is to enter your phone to fastboot and then bootloader and resume again by pressing next. I manage to get the ruu.exe to complete its full restoration.
Edit: i cant replicate that right now as im on sense 3.0, I have to get back to where my siggy in order to do so.
I am in the same boat.. Same situation and Same Results.. To the poster above doing the RUU 1.17 does not work even after you follow the trouble shooting. I have spent at least 20 hrs working on my phone and nope, I have started threads and nope, I have even tried to disect the RUU and tweak security files to allow it to by pass the fact that it finds a newer image than what i'm trying to put on there, It went further but still nothing.
I believe we must wait until a newer RUU comes out that is newer than the 1.72 image we have. Or until Revo updates to 1.20HBOOT support.
Remove the SD card and try again
Thats weird. I had couple of times switched from s-ons to s-offs and vice versas, from all firmwares and even back to the native firmware without issues. Sorry not much else I can help with.
I ran an RUU that was a higher image than what I have, and still no luck there, and no luck booting the phone up into fastboot and restarting the RUU either. If I could find a way to flash a new radio to match my ROM (revo hd 3.6.13) I would settle for s-on until somebody comes out with something to s-off 1.20 and up.
silverion said:
When attempting to downgrade to 1.17 via P58img.zip it simply returns to the menu after "parsing".
Click to expand...
Click to collapse
Minor point, assume you mean PG58IMG.zip ......
Saxman6699 said:
I ran an RUU that was a higher image than what I have, and still no luck there, and no luck booting the phone up into fastboot and restarting the RUU either. If I could find a way to flash a new radio to match my ROM (revo hd 3.6.13) I would settle for s-on until somebody comes out with something to s-off 1.20 and up.
Click to expand...
Click to collapse
Just because the RUU is a higher image doesn't mean it will work if you don't have SUPER CID, and you can't obtain SUPERCID in this state.
You have to have the RUU from your carrier/country and it must be newer than your image. So me, I am waiting for the official Tmobile RUU ICS
---------- Post added at 03:45 PM ---------- Previous post was at 03:44 PM ----------
johnerz said:
Remove the SD card and try again
Click to expand...
Click to collapse
Remove the SD card and try what again? Try the RUU again? Which one? Any of them? What would the SD card have to do with not passing the Security check put in place regarding the image file?
If you downgrade the hboot back to 1.17 doesn't that break functionality of ics roms? Just curious.
Sent from my HTC Sensation 4G with Beats Audio using XDA App
If you are able to downgrade to 1.17 yes it will break ICS. But who cares as it would allow me to S-OFF again and do everything properly.
Correct, our issue is we cannot even downgrade due to the S-On.
Related
Right, had desire s from three, alpharevx'd it installed clockwork mod, flashed eng hboot. Tried to flash RUU 1.47 europe on it, and it started to work and go through process, updated radio fine, then came up with CID error. No option to do anything but exit. Now I have a desire s that will boot into Bootloader, which has now s-on'd itself and upgraded to 0.98.0002.
Only method of comms seems to be via fastboot.
Now i cant flash the h3g one cos its too low a bootloader version, and i cant upgrade to a newer version cos one don't exist. Can anyone come up with a solution please??
Cheers.
What does HBOOT screen say (in full)?
Are you still able to get into recovery? If yes, then have you tried loading a custom ROM onto the SD card and simply flashing that using the flash zip from sd card option of CWM (clock work mod)?
Unfortunately I am unable to get into recovery, only bootloader, nothing else works. Hboot is displaying a security error at the top highlighted in pink, followed by the version number as described
You should have stuck with the alpharev hboot, which does not allow itself to be overwritten by RUU installs.
Anyway, you need to:
- install hboot 0.980000 (so you can run alpharevx again and get S-OFF)
- run alpharevx and reinstall CWM at the end
- DO NOT install the eng hboot
- flash whatever rom whichever way you want. Your hboot is safe
Follow the instructions on:
http://forum.xda-developers.com/showthread.php?t=1187231
How can I run alpharevx when I can only boot into bootloader tho?
Try running it while in bootloader. Never tryed it that way, but I'm pretty sure it only needs the USB comms to be up, same as adb. Which they should be anyway in bootloader...
Have you tried to re-setup your phone by executing one of the RUU.exe?
k, as i expected, with no access to adb in bootloader mode, i am unable to do anything. Remember, i only have bootloader to work from. I don't eve3n have a recovery partition installed, it just comes back to bootloader whatever i choose, well, bootloader and fastboot anyway.
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
If all else fails s-off with xtc clip then flash custom rom
Sent from my HTC Desire S using XDA Premium App
Have you tried to use the original RUU for your phone/network? I'm not sure if it would take care of the CID error.
Any of these:
http://forum.xda-developers.com/showthread.php?t=1002506
Clivectmob said:
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
Click to expand...
Click to collapse
I do not expect this to work, but you said you are able to get into recovery, correct?
Well, I would try to enter fastboot mode and try to flash cwm via fastboot -> fastboot flash recovery XXXXXXXX.img
Correct (windows) drivers installed?
Edit:
lowveld said:
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
Click to expand...
Click to collapse
Good suggestion! Try this one first.
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
I haven't run a RUU in years, but I think that when you run it on a windows machine, it extracts a bunch of files to a directory. Cancel the process, find the directory, find th PG88... in the directory... You get the drift.
Clivectmob said:
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
Click to expand...
Click to collapse
It is not relevant which network you are using !!! Just try newest RUU to get control over your phone again in the first place!
Even if you don't get any network access after setup newest RUU you will definitely be abte to execute alpharevx again, flash cwm and flash any stuff you want to.
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Clivectmob said:
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Click to expand...
Click to collapse
I guess that means you tried flashing recovery via fastboot?
Then concentrate on our RUU-suggestions.
Yes, as i said, flashed via fastboot, and i already explained that i cant up/down grade via ruu method because of bootloader version. I can't think of a way out of this as it stands. The only thing that may work is doing it via the p88img method with my original 3uk rom, but i cant find it in my temp files, searched everywhere for it. I've seen it's location posted on here before now, and i've searched it to death and can't seem to find it now
I'm going to extract and upload your 3GUK-PG88*.img although I think you'll need an newer one. Just a few minutes of patience.
My problem is a little complicated.
It dates back to last night. Suddenly i just want to try ICS so i download the firmware and rom from this thread(http://forum.xda-developers.com/showthread.php?t=1408351). I met with a problem, after i flash the firmware, the system stuck but i pulled the battery out then problem solved. The next step is just as usual and nothing unusual happened. It's not so smooth and perfect as CM7, which i think it's just a problem of maturity.
After i restore the apps and finish setting the phone, i check the bootloader and find that the bootloader shows it's locked. There wouldn't be a problem if i just accept that. But i decided to do something, unfortunately, i messed up.
The bootloader shows "locked" and "Security warning" and the phone can't boot into system by any means. I tried a lot of methods and finally i unlock the bootloader by official method. Result seems to be good. The bootloader shows "unlock" but "s on" and the phone can boot into recovery. It seems i just wake up from a nightmare.
but the nightmare never ends. Although i can wipe or install any rom, but the phone just stuck at the splash screen. I tried but i faild. Is there anyone has some suggestions? And how to s off?
The hboot version is 1.23.0000 and it doesn't install any PG58IMG files no matter it is radios or else.
Thank you in advance
You need to Soff again.
Its normall for the latest firmware hboot 1.23 to show locked. Its not really locked
big_sw2000 said:
You need to Soff again.
Its normall for the latest firmware hboot 1.23 to show locked. Its not really locked
Click to expand...
Click to collapse
Could you tell me how to s off please? Or downgrade the hboot? It seems that hboot 1.23 isn't supported by revolutionary?
Have a look
http://forum.xda-developers.com/showthread.php?t=1192300
big_sw2000 said:
Have a look
http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
I have read the thread, if relotionary is the only way to s off, i don't think it help because it requires hboot is under 1.18, but the hboot of my phone is 1.23, is not in the supported list. Besides, my phone can't boot into system, the revolutionary is always waiting for device
Revert to 1.17 and S-off using revolutionary
I hope it is possible, don't know exactly what is possible to be flashed with s-on, but since your phone is unlocked you can use fastboot commands, so I think it wont be a problem.
akos.szekacs said:
Revert to 1.17 and S-off using revolutionary
I hope it is possible, don't know exactly what is possible to be flashed with s-on, but since your phone is unlocked you can use fastboot commands, so I think it wont be a problem.
Click to expand...
Click to collapse
In this thread, it mentions that how to revert to 1.17(http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22), on the condition that the hboot is 1.20,but my hboot is 1.23. I'm trying the zip from the thread, hope it works
It remains usless. The bootloaders shows "PG58IMG.zip" is a wrong image.
My Sensation XE came with HBoot 1.2.000, so i installed at ROM from here with HBoot 1.18.000 and then got S-OFF.
jkolner said:
My Sensation XE came with HBoot 1.2.000, so i installed at ROM from here with HBoot 1.18.000 and then got S-OFF.
Click to expand...
Click to collapse
And which ruu? I tried ruu too, but it didn't work.
i know that 1.20 can be reverted to 1.17 and then s off. But my hboot is 1.23 rather than 1.20. And i have another problem: the bootloader can't update by PG58IMG.zip, it always shows no file or wrong image.
I have a couple questions.
I am on the 1.16 hboot with cid111111 and s-off unlocked tampered. twrp and maximus rom.
I finally did super cid and s-off on my one-s. Shortly after I recieved a notification that ota update 3.16.401.8 (612.27 mb) was available.
I was wondering if it would even work if i attempted to update. or would i have to update manually. Or would it brick it.
The main reason i would want to update is because the JB Sense roms just dont seem to run smoothly on my phone.
I was thinking this would update everything so the custom roms run smoother.
And Should i even update my hboot. does it make a difference.
I would usually be against it(ive had to downgrade other phones before).
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
impostle said:
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
Click to expand...
Click to collapse
Ok. ill look into that. sounds easy enough. last time i tried to update, i couldnt because of my cid. now i guess since there is an official t-mob i can do it?
You cant flash an ruu with super cid?
Oh and also, Once i update my hboot am i able to install the older ICS roms like maximus. thats just the most stable one i have found for my particular phone.
One more. Will i be able to restore my cid with s-off
ruu update
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
myphonesbetter said:
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
Click to expand...
Click to collapse
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
impostle said:
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
Click to expand...
Click to collapse
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
real187 said:
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
Click to expand...
Click to collapse
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
EDIT: Thats what I get for watching too many threads, I miss stuff.
impostle said:
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
Click to expand...
Click to collapse
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
real187 said:
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
Click to expand...
Click to collapse
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
impostle said:
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
Click to expand...
Click to collapse
I have seen the tread. But im scepitical, because if it really was only because of the s-off more people should have it. Might be hardware related.
Eh you do not have tot change back your Cid to original (if its a branded Cid the ruu still wont run), just a valid HTC Cid.
Verstuurd van mijn One S met Tapatalk
He could flash from recovery or fastboot flash any hboot he wants with s-off. No RUU needed for downgrade or upgrade. That's only needed to go back to stock for warranty purposes.
@myphonesbetter
If you want the red warning text overlay to be gone as well choose any of the files here and flash it within recovery. S-Off needed to do so!
To remove ***Tampered*** as well download hboot 1.140004. You will need to come from a lower hboot version so if you're already on >1.140004 flash one <1.140004 first.
--- edit ---
You can lock/unlock your phone as well by flashing. Read more in [how to] reset your lock status flag. Also it's in the Droid DNA forums it's valid for One S. Remember: You need s-off for this to work.
--- and one more ---
You can change your CID pretty simple on rootet devices. Just enter fastboot mode and type:
'fastboot oem writecid HTC__001'
Reboot bootloader then. You can find a collection of HTC ONE S CID's here
^^^^^Very helpful post. thank you. I wouldve never found that.
When you run the ruu .exe, do you have to be in fastboot or in android? The install app told me just to turn the phone on so i figured it would automatically go into bootloader. but it did nothing at all to my phone and gave me an error 115.
When i tried the ota it tells me that I am runnning an altrered OS and i will have to install it a different way.
Sorry for the easy questions. but i just cant seem to find any threads that say how to. I found the ruu and a zip of the ruu. but not how to install it.
The best sense rom has instructions on flashing a newer hboot. .but i want to install a completely stock rom.
myphonesbetter said:
^^^^^Very helpful post. thank you. I wouldve never found that.
.
Click to expand...
Click to collapse
guess you run out of thanks, no?
Never even noticed the thanks meter. I have more of a direct thank you approach.
I tried to flash the ruu .exe in fastboot. and it actually rebooted into the black htc screen, so i figure thats the way to do it.
Unfortunately I got another error. image error (159) use the correct rom and flash again.
I am attempting to flash 3.16.401.8 onto hboot 1.16 (relocked) i am s-off and i changed my cid to HTC__001 via fastboot.
Is there another way. or can i flash the zip in twrp or cwm? Again i just want an oem jelly bean with the proper hboot and radio and everything that the OTA would change. so i can be up to date before i move on to the JB roms.
Ive tried all of the custom ones, and the wifi cuts in and out. i used the wifi partition fix. and i flashed the latest radio. nothing helped for more than a few hours.
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
ultimul said:
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
Click to expand...
Click to collapse
Yah thats usually how it works for me. if it works for 99% of people with one step. ill have to do it manually with 20 steps. I guess its made me learn alot about adb and fastboot. I could never get adb to work untill i upgraded to windows 7 recently. until then i had to exract everything to my sdcard via terminal emulator and then drag it to my computer form the card and modify things. but ive been forced to learn quite a bit.
Its weird. I bought my phone off of craigslist from someone who had no idea how to root. But when i opened it into hboot it said Tampered and locked. with no signs of ever being unlocked. completely stock rom and no red warning text on the splash screen.
The reason i want to be stock it so i know all the correct partitions and everything are set up right. (that part i dont understand yet).
I know that a normal system wipe in twrp or cwm doesnt wipe everything. If i wipe and install the same rom i am using(just to clear it up and start over) it doesnt even wipe the app data. (at least on my phone)
Im thinking that its because i am installing a euro rom with a HTC__001 cid and mine was originally TMUS T-MOB010 .
one thing i noticed also is that windows could not verify either of the ruus i downloaded from shppied roms
How do i flash the ruu.zip that i downloaded? Do i need to rename it update.zip like the older phones? Its been a while.
Ok so i know im pretty much helping myself here but i hate when i come across threads with no conclusion.
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Any help would be appreciated.
Ahh, things go on here! Nice! :laugh:
It's not quite clear if the RUU is the right one on this phone as many people report problems... So let's go OTA.
To flash the 3.16 OTA update your hboot needs to be < 2.15, your recovery needs to be the HTC stock one , your device needs to be relocked (not totally shure as mine wasn't at that time and it worked, but please remember that) and you need to have HTC stock system/ and stock data/ (ICS) files on your phone (you'll have to unroot as well, if rootet), as the OTA seems to check if certain files are present before working.
All that is quite a pain in the ass, isn't it?! So do one the following:
- Just make shure your bootloader version is lower 2.15, else flash a lower one.
- Click here and you'll have access to one of my google drive folders.
- Download the 2.31 zip. Unpack and copy these nandroid backup files into the appropriate TWRP folder on your phone, reboot into recovery and restore. Once done, you'll be able to flash the 3.16 OTA update after reboot. Remember to change CID before if you're on 11111111.
- Or download the 3.16 zip, unpack and restore. You'll have stock htc sense JB without the OTA. You don't even need to downgrade your bootloader in case. CID doesn't matter here.
- To root simply download SU_Bbox file and flash in recovery.
Important: With the JB update HTC invented disk write protection by default. This simply means that files deleted within stock sense JB will be back after rebooting the phone, also root was granted and working (still grats to htc for this one!!!). Check out for elemental x kernel at this point, as flar2 is the one offering additional modules for the stock kernel working around this. So you can be on stock JB as close as possible with write protection disabled.
--- edit ---
I nearly forgot: If you're experiencing WiFi troubles afterwards search for flashing wifi partitions.
--- and one more ---
myphonesbetter said:
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Click to expand...
Click to collapse
Cause you're on 2.35 US. You need to be on 2.31 EU before, because 3.16 is EU and there is still no JB update to 2.35 US. 3.16 OTA will work with htc__001 (htc worldwide).
The OTA determined my OS was modified.
I could not restore the folder i took directly out of the zip.
There was a folder inside the folder that contained the same files. I was able to flash this.
My hboot is still at 1.14 my cid is not htc--001 relocked. the update was 650 mb of which i could not use wifi for becauese it just said error.
so 650 mb through tmobile. only took a few minutes but used almoast half of my months dl limit.
IDK. i found instructions on how to update the hboot in best sense roms thread. i will try that.
Edit: the restore for 3.16 worked in twrp. shouldve tried that first.
I may still update my hboot. I cant really find any instructions. Apparently the search just finds every thread and lists it.
If you are on the latest TWRP 2.4.3.0 go back to 2.4.1.0 (the latest one seems to have restore problems).
The folder contained in the zip needs to be copied to /TWRP/BACKUPS/HT23whatever/
You should be able to restore then.
--- edit
hehe, ok then.
You can flash any of these hboots from within TWRP. Up or down, it doesn't matter - you're s-off.
---------- Post added at 10:43 AM ---------- Previous post was at 10:32 AM ----------
CID should be HTC__001 not htc--001. Maybe a typo.
Hello everybody,
I just changed my rom (first time) to put the Revolution HD 7.3 on my HTC Sensation ( http://forum.xda-developers.com/showthread.php?t=1098849)
I followed this tutorial http://forum.xda-developers.com/showthread.php?p=25593366 in order to change the rom as I do not have any wires (or paperclip or anything ...) to S-off my phone following the Juopunutbear method as I have a hboot 1.27
So I unlock the bootloader on the HTC website, I still have S-on.
Then as I was expecting once the rom fully installed, I do not have much networks ... So I have tried to flash the radio recomended in the Revolution HD thread. (11.76A.3504.00P_11.24A.3504.31_M radio). Even though the link is dead I have found some other link.
Everywhere I have read I need to be S-off to flash the rom, but is it possible to do it s-on anyway ?
Anyway I have tried to change it :laugh: Maybe it was not clever.
I have tried few methods, first by putting the zip in the sdcard, then rebooting the bootloader, the installation seems to go find, and when I go to the scpecification of the phone the right radio do appear. Except that i still have low network or none ...
So i have tried using the commands fastreboot flash radio radio.img, and i obtain this error :
sending 'radio' (22229 KB)...
OKAY [ 3.973s]
writing 'radio'...
(bootloader) signature checking ...
FAILED (remote: signature verify fail)
finished. total time: 8.867s
Click to expand...
Click to collapse
I think I have said everything ...
I mostly find solution were people advice to change the firmware which has the radio. Except that I am S-on I guess it will not work ?
Maybe the radio I am trying to put is corrupted ?
Or my last option is to define somewhere this famous wire to do the S-off ?
Aroeris said:
Hello everybody,
I just changed my rom (first time) to put the Revolution HD 7.3 on my HTC Sensation ( http://forum.xda-developers.com/showthread.php?t=1098849)
I followed this tutorial http://forum.xda-developers.com/showthread.php?p=25593366 in order to change the rom as I do not have any wires (or paperclip or anything ...) to S-off my phone following the Juopunutbear method as I have a hboot 1.27
So I unlock the bootloader on the HTC website, I still have S-on.
Then as I was expecting once the rom fully installed, I do not have much networks ... So I have tried to flash the radio recomended in the Revolution HD thread. (11.76A.3504.00P_11.24A.3504.31_M radio). Even though the link is dead I have found some other link.
Everywhere I have read I need to be S-off to flash the rom, but is it possible to do it s-on anyway ?
Anyway I have tried to change it :laugh: Maybe it was not clever.
I have tried few methods, first by putting the zip in the sdcard, then rebooting the bootloader, the installation seems to go find, and when I go to the scpecification of the phone the right radio do appear. Except that i still have low network or none ...
So i have tried using the commands fastreboot flash radio radio.img, and i obtain this error :
I think I have said everything ...
I mostly find solution were people advice to change the firmware which has the radio. Except that I am S-on I guess it will not work ?
Maybe the radio I am trying to put is corrupted ?
Or my last option is to define somewhere this famous wire to do the S-off ?
Click to expand...
Click to collapse
Hi,
You are s-on
You need to be s-off to change firmware/radio
If you want to s-off,look HERE
What does your bootloader say?
You need to be s-off for the radio to function properly. Having s-on is a problem as it does not guarantee that your current custom rom will boot properly. Even if it does, you'll be experiencing minor glitches now and then. Now if you want to flash asop roms, s-off becomes a compulsion.
So I'd recommend you to use the juopunutbear method for s-off.
P:S- The famous wire trick is worth trying...makes you feel like a hacker
abachhd said:
Now if you want to flash asop roms, s-off becomes a compulsion.
Click to expand...
Click to collapse
why is it a compulsion?
rzr86 said:
why is it a compulsion?
Click to expand...
Click to collapse
Hi,
I think he means "Necessary"
But it is not 100% necessary.
rzr86 said:
why is it a compulsion?
Click to expand...
Click to collapse
I mean you'll have to s-off as the ASOP JB roms have different booting parameters than the ICS roms and if you're s-on, there may be chances of a boot loop, the main reason being the official HTC hboot module resetting the rom's boot configuration and you'll have to go through the pain of reflashing the original boot.img via adb to restore back your device. S-off turns off the hboot security and thus allows unofficial rewriting of boot.img file, causing any 3rd party rom to boot successfully.
abachhd said:
I mean you'll have to s-off as the ASOP JB roms have different booting parameters than the ICS roms and if you're s-on, there may be chances of a boot loop, the main reason being the official HTC hboot module resetting the rom's boot configuration and you'll have to go through the pain of reflashing the original boot.img via adb to restore back your device. S-off turns off the hboot security and thus allows unofficial rewriting of boot.img file, causing any 3rd party rom to boot successfully.
Click to expand...
Click to collapse
smartflash from 4ext does this job
Two years ago I had this phone and I wanted to flash. I did. I don't remember all the details of it, but I do know that someone on here helped me flash it and it ended up with a European(?) flash on it and I remember he helped me do something with the radio in order that it would take the flash. I also remember that the reason for the flash was so that TMO wouldn't charge me for tethering. In any case, here's the current situation. I sold the phone and the person came and said they were having issues... so I was trying to restore it to a TMOUS ROM. Eventually, I bricked it, and got the qualcom download mode issue. I found the thread on that on how to fix it, and I did. Now the phone boots to the recovery screen and does nothing else. I am unable to flash ANY of TMO's RUU's, some of the PG58IMG.zip files that I've been able to find all fail... very frustrating.
I followed another thread that talked about how to unlock the bootloader, which involved copying the Identifier Token and sending it in to HTC. I received the response, and ran the command and was successful in unlocking it. When the device rebooted, it even showed the Tmobile animated logo. When I go back into the boot loader, it now reads:
My bootloader screen reads as follows:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.27.0000
eMMC-boot
JAN 13 2012.17:33:34
Software info shows:
Android Version: 4.0.3
HTC Sense Version: 3.6
Software number: Blitz_2.0.0
Kernel: 3.0.16-gda3fdfc
[email protected]#1
Baseband version: 11.76A3504300U_11.24A.3504.31_M
Build Number 3.33.401.106 CL391535 release-keys
Browser version: WebKit/534.30
At this point, I would try any flash, any rom, any thing to get this phone working for the guy again. I am skittish about flashing anything from this point so I don't mess up and have to start all over somewhere. Can I flash something working from this point? Can I flash a TMO RUU from here?
I have the RUU_Pyramid_TMOUS_1.27.531.2_RADIO_10.42.9007.00P_10.11.9007.15_M_release_192098_signed.exe as well as several others. Id' rather put this phone onto something stock from tmo but will do a custom as long as the phone is restored to working order.
I won't say I'm a newb... but having been away from flashing for a while, I could really use some step by steps to get going again.
The computer I am using to flash with is a Windows XP machine with all the HTC drivers working etc.
**** UPDATE ****
The phone now boots up as it did when this all started. After I did the token thing and got the bin file from HTC, I applied it and the result was the boot loader info above. It got past the tmobile animated logo and actually into the phone starting up as new including applying all the settings I want. Awesome that the phone now functions like a phone again, but I would still like to flash an official TMO Rom to it to restore it back to like out of the box condition. Any help is appreciated.
read this thread
http://forum.xda-developers.com/showthread.php?t=1672425
rzr86 said:
read this thread
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
I actually have read that... like 6 times to make sure I'm not missing anything. I do remember having to flash the radio back when I did my original flashing, and I think that process is preventing me from using any of the RUU's that I find. Are there any posts/files/resources that will help me flash the radio back to its default, so that I can then flash the RUU?
Also, I am S-ON already, but ANY RUU that I try to flash fails. Do I need to go to S-OFF and then RUU, then back to S-ON?
sc.lord said:
I actually have read that... like 6 times to make sure I'm not missing anything. I do remember having to flash the radio back when I did my original flashing, and I think that process is preventing me from using any of the RUU's that I find. Are there any posts/files/resources that will help me flash the radio back to its default, so that I can then flash the RUU?
Also, I am S-ON already, but ANY RUU that I try to flash fails. Do I need to go to S-OFF and then RUU, then back to S-ON?
Click to expand...
Click to collapse
no you don't need S-OFF
post your cid
rzr86 said:
no you don't need S-OFF
post your cid
Click to expand...
Click to collapse
CID is 11111111
I think I have it licked now.
Used the universal firmware and the viper 5.2.1 flash and it loaded just fine. Never got S-OFF on it, but the viper flash so far is working excellent.
sc.lord said:
CID is 11111111
I think I have it licked now.
Used the universal firmware and the viper 5.2.1 flash and it loaded just fine. Never got S-OFF on it, but the viper flash so far is working excellent.
Click to expand...
Click to collapse
how do you have supercid with S-ON?
also how did you flashed the universal firmware while on S-ON?
those two things can be done only on S-OFF
rzr86 said:
how do you have supercid with S-ON?
also how did you flashed the universal firmware while on S-ON?
those two things can be done only on S-OFF
Click to expand...
Click to collapse
Wish I could tell you.... hence the reason for the original help request.
I can tell you that I hit softbrick on it once and had to unbrick in linux.
Then I got the LOCKED with Security Warning. Then I got the unlock bin file from HTC Dev, used that and got back to UNLOCKED, with no security warning. Then I tried Rumunner without any success at all, stayed S-ON.
in any case, after trying just about everything I could think of, I found the viper post, saw that you said you don't need S-OFF to flash new rom... so i gave it a shot. Updated EXT, flashed the firmware, then the rom and it all went very smoothly. Phone's been working fine since. <shrug>