[Q] Going back to stock from ICS? - HTC Sensation

Hi guys!
Sorry another n00b question but just wanted to make sure...
So I am one of those that got tired to waiting for the OTA and finally decided, at least for now, to try one of the ICS ROMs. I've done some on GB so I'm vaguely familiar with flashing and all that but since it's my first time with ICS I'd like to ask you experts out there.
Basically I just want to make sure that if/when TMo finally pushes out the "official OTA", I can give that a try also. I guess my fear is that I've been reading how it's difficult...or impossible?...to go back to stock since I have to flash my firmware.
Can you go back to 100% Stock TMo GB from ICS?
I currently have already S-Off, root (superuser), and S Cid to 11111111 in preparation. I figure while I wait for TMo, at the very least, I can run my phone rooted to let apps like AutoKiller Memory help my phone run better. I also did a backup using 4EXT.
My next step is to take the plunge but before I do, I'd like to know that I can go 100% back. I've done it with GB ROMs but wasn't sure about ICS because of the whole firmware thing.
Can someone LMK if it should be no problem? Much appreciated for guiding a n00b like me! You guys are awesome!!!

It's not hard...
http://forum.xda-developers.com/showpost.php?p=21989089&postcount=2
This is how I do it:
1. Place firmware on root of sdcard.
2. Use 4ext recovery control to reboot to recovery (power menu).
3. Restore my stock nand from 4ext recovery.
4. Use 4ext recovery to reboot into bootloader (power menu).
5. Select "bootloader" from fastboot menu and let hboot detect the firmware. (volume up for "yes")
6. Let it complete and press power to reboot when prompted...
All my roms, nands, firmwares, radios, etc... are backed up on my sdcard. As long as I've got a good charge on the battery I can go back and forth between BG and ICS multiple times without ever connecting to a PC or pulling my battery...
If you don't have a nand of your stock rom then just flash the 1.50.531.1RUU... And restore your CID.

Thanks for the info GROGG88! So this will restore my firmware too? So basically using the RUU should get me back to full stock including the firmware? Or do I need to downgrade the firmware manually first?
Also noticed that in the link you gave, it has Hboot 1.17. Does it matter that my original is 1.18?
Again apologies for new n00b questions! Thanks for all your help!!!

If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
It really depends on whether or not you backed up an unmodified version of your stock GB...
I'm going to post download links for the 1.50.531.1 RUU and a PG58IMG.zip version of it in the General section. You can use the PG58IMG.zip to restore individual components by extracting the files, removing whatever you don't want, and archiving the files you do want back into a zip...

GROGG88 said:
If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
It really depends on whether or not you backed up an unmodified version of your stock GB...
I'm going to post download links for the 1.50.531.1 RUU and a PG58IMG.zip version of it in the General section. You can use the PG58IMG.zip to restore individual components by extracting the files, removing whatever you don't want, and archiving the files you do want back into a zip...
Click to expand...
Click to collapse
Thanks again GROGG!!!

GROGG88 said:
If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
It really depends on whether or not you backed up an unmodified version of your stock GB...
I'm going to post download links for the 1.50.531.1 RUU and a PG58IMG.zip version of it in the General section. You can use the PG58IMG.zip to restore individual components by extracting the files, removing whatever you don't want, and archiving the files you do want back into a zip...
Click to expand...
Click to collapse
Can you LMK when you post those files as well as the link! Much appreciated!!!

Files can be found here: http://forum.xda-developers.com/showpost.php?p=25561199&postcount=1

GROGG88 said:
Files can be found here: http://forum.xda-developers.com/showpost.php?p=25561199&postcount=1
Click to expand...
Click to collapse
Thanks GROGG88!
Also wanted to ask...I know you mentioned that after the procedures I will have everything stock but still with S-Off. Do you know if I can receive OTA with S-Off or will I have to adb and make it S-On again making the phone COMPLETELY stock.
Thanks again for all your help! I might have to follow these procedures sooner than I thought with the latest announcement about the OTA ICS!

GROGG88 said:
If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
Sorry another related question...why is it good to keep s-off? Advantage?
Sorry again for all the questions! Hoping to expand my knowledge!
Click to expand...
Click to collapse

You can use the OTA with s-off. You want to keep s-off so that you can flash a custom recovery and re-root after the update. You can s-off the new bootloader, but it involves a new procedure that involves jumping a wire from a terminal to ground that many are not comfortable with.
It is much better to keep s-off...

GROGG88 said:
You can use the OTA with s-off. You want to keep s-off so that you can flash a custom recovery and re-root after the update. You can s-off the new bootloader, but it involves a new procedure that involves jumping a wire from a terminal to ground that many are not comfortable with.
It is much better to keep s-off...
Click to expand...
Click to collapse
Good to know! Thanks! So the new procedure requires you to do something physical to your phone? That sounds just wrong...I guess they really don't want s-off, huh?
I'll definitely keep s-off so I won't have to jump through these hoops!!!

Related

Trying to revert to stock hboot

I tried following this guide:
thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2849-how-restore-stock-rooted-non-rooted-users.html
I successfully flashed MR1, now when I go to flash the bootloader using the same PG05IMG.zip method it says bypassed. I checked the md5 hash, it checked out okay. What would cause this?
This is for a warranty replacement, I just need the phone to be stock again!
Just find the latest unrooted gingerbread rom that leaked and flash it, it will go back to stock. check here or android police for the download....
Jrocker23 said:
Just find the latest unrooted gingerbread rom that leaked and flash it, it will go back to stock. check here or android police for the download....
Click to expand...
Click to collapse
Thanks, I will give that a shot.
If you originally used the Revolutionary root method, its not just flashing a new hboot, as its a hboot that doesn't allow it to be easily overwritten. This stops you from accidentally flashing a s-on hboot at a time you didn't mean to (most likely through ruu). If you did that, you have to adb some files to your phone to put a stock s-on hboot on. If you did the old downgrade root method, i would try downloaded the files from somewhere other than where you did this time, and try again.
nbdysreal said:
If you originally used the Revolutionary root method, its not just flashing a new hboot, as its a hboot that doesn't allow it to be easily overwritten. This stops you from accidentally flashing a s-on hboot at a time you didn't mean to (most likely through ruu). If you did that, you have to adb some files to your phone to put a stock s-on hboot on. If you did the old downgrade root method, i would try downloaded the files from somewhere other than where you did this time, and try again.
Click to expand...
Click to collapse
This is exactly what I needed to know.
For people in the same boat this is what I did (sorry for the links, apparently I don't have enough posts)
Follow this guide to flash a different hboot:
thunderboltforums.com/forum/htc-thundebolt-hacking-guides/5427-rs-guide-how-return-stock-revolutionary-root.html
Then flash the PG05IMG from here:
droid-life.com/2011/09/27/finally-the-htc-thunderbolt-gingerbread-update-appears-to-be-ready-as-build-2-11-605-3/
so to get back to stock, if you didnt use the rev root method, what exactly do you flash? could someone link me?
shawnn218 said:
so to get back to stock, if you didnt use the rev root method, what exactly do you flash? could someone link me?
Click to expand...
Click to collapse
What I outlined above should get you to stock.
even if i rooted the normal way and not rev?
http://forum.xda-developers.com/showthread.php?t=1310014&highlight=return+to+stock
2/3 of the way down under this section "Putting current stock firmware and s-on back onto the phone"
This will put you back to STOCK / S-0N from the old downgrade root method. If you just want a stock rooted rom, flash one. Unless you are taking it in for service or returning it, there really isn't a need to unroot it just to put a stock rom on.

[Q] Unrooting back to stock

Hi. So this is what I have done so far..
1. Unlocked my bootloader using HTCDEV which unlocked my bootloader but kept S-On.
2. Then I flashed my recovery with 4Ext recovery.
3. Installed SU using that. Now I have super user privilages.
In the end, I have unlocked, rooted bootloader with HBOOT 2.00.0002 and S-On. I have taken back up of my current ROM.
From what I understand,
1. My phone is completely rooted.
2. To install a new ROM, I need to go to recovery in booloader and install from SD card.
3. I can revert to my old stock ROM using the back up I took earlier.
Please let me know whether I have got it right till here.
I went through beginner's guides and needed few things to clarify.
1. Will installing new ROM overwrite RUU ?
2. If yes, how do I back up RUU or Rom.zip before I flash with new ROM ?
3. Even though I restore back to my stock ROM. Will my super user privilages remain ?
4. If yes, how to remove them ? How to unroot ?
5. Can I restore to stock's recovery ?
In other words, can I COMPLETELY restore it back excluding unlocking? Please guide me with respect to Desire S.
Installing RUU will comletely restore your phone to stock, removing root as well. So basicly there is no point in backing it up.
Please note that when you unlocked with htcdev.com you will have to flash boot.img separately after installing any custom rom for the phone to boot.
Anyway, there are so many guides on this forum that unswers all your questions, don't see a point to start the new one here.
Sent from my HTC Desire S
dmatik said:
Installing RUU will comletely restore your phone to stock, removing root as well. So basicly there is no point in backing it up.
Please note that when you unlocked with htcdev.com you will have to flash boot.img separately after installing any custom rom for the phone to boot.
Anyway, there are so many guides on this forum that unswers all your questions, don't see a point to start the new one here.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Thank you. And sorry for the new thread. I went through the guides. Just needed to confirm. These RUUs, are they fixed for a particular model and country? For example, this link provides some RUUs for Desire S for different countries. So RUUs for all the Desire S phones in that region are same, officially ?
Aah, this thread solved the problem that I've been thinking!
When I am going to sell my DS, only need to install correct RUU and it is fully stock again?

[Q] Sensation Newb- Locked Bootloader 1.23 CM9 Woes

Yes, I am a newb to the Sensation, but not flashing in general. I have previously had hacked SamVibrant, HD2, and most recently, the G2x, so I know from a constant flasher's POV generally what Im doing.
I've been searching for answers to this for days now, and nothing really seems to work, so let me just start with what is going on.
CURRENT STATS:
-PHONE-TMO Sensation 4g
-S-OFF
-ROOTED
-BOOTLOADER-1.23.0000
-RADIO-10.14.9035.01_M
At the top of the bootloader screen it says ****LOCKED**** Which I am guessing is obviously in refrence to the bootloader itself.
Also I currently have the latest 4EXT recovery flashed. When I got the phone it had CWM 5.00.2 or whatever the latest was.
Just bought a Sensation from a guy on Craigslist, and when I got it, it had a CM7 AOSP ROM running on it. I definitely wanted ICS, so I started reading and trying to get it.
So I started here:
http://forum.xda-developers.com/showthread.php?t=1192300&highlight=hboot+1+23
I tried the PG58IMG.zip install via the bootloader, but kept getting errors and security fails. So I researched more and found a post about how to fix that, but the problem is that there is almost always a need to use Revolutionary, and I can't because it doesn't support the 1.23 bootloader.
I have also tried the PG58DIAG via bootloader, and still got mismatch and security errors.
I also just recently tried flashing back to the "REALSTOCKEXPERIENCE" stock ROM which was successful, but it didn't fix my bootloader or unlock woes. Lastly I tried the HTC dev Unlock, and it would not work, because When I got to the part where it attempts to connect to the phone via USB to do get the identifier token it would not connect. It just kept waiting. I tried resetting my phone and reloading the BL but it would not work.
Also I have noticed that I cannot get my phone to connect VIA USB to the PC when in FASTBOOT or Bootloader. Is that normal?
Please help a brother get some ICS on my new phone! I loved my HD2, although it was a bi#$% to flash sometimes, I loved it, and that is why I went with HTC again. This all makes me miss my Vibrant, where you could flash all day long and root without a computer... Good times....
You're already s-off, so most of the work has already been done for you. Make sure you have fast boot unchecked in power options in your current rom. After that, all that's left to do is check your cid. If you're supercid, then grab any 3.32 base firmware from one of the many rom threads in our dev forum, install it via bootloader, remove the firmware file from sd card (do it from pc after you power down the phone), then flash a rom. This will also upgrade your bootloader to 1.27 unlocked and change your radio to the latest. Don't forget to check md5!
If you're not supercid, then you'll need to find kohr-ah's firmware thread because he has corresponding firmware for all cids. Then grab any rom and enjoy.
As for connecting fastboot via USB, you need the htc sync drivers installed on your PC.
Sorry for lack of links. I'm on mobile and searching is a PITA on the phone.
/edit
Make a nandroid backup before you do any of this.
Thanks a bunch. I will give it a go a third time, but that is one of the problems that I am having, is that I can't flash anything via bootloader. I just get tons of errors...
Lets see if the third time is a charm.
EDIT: I still can't use revolutionary for Super CID because the bootloader is 1.23, but I used a Terminal window and the getprop ro.cid/mid and got this:
Cid-T-MOB010.... is this super CID'd?? I was looking for a reference post, but cant remember where I found it before.
no you are not super cid, it would say 111111. But your good everything is already done really.... Go to kor ah's noob friendly firmware thread, find the 3.32 firmware from T-Mobile with the tmobo10 included. Put it on the root if your SD and there you go flash an ics rom. Just remember to delete it after.
Sent from my HTC Sensation Z710e using xda premium
delete this please
wadill said:
no you are not super cid, it would say 111111. But your good everything is already done really.... Go to kor ah's noob friendly firmware thread, find the 3.32 firmware from T-Mobile with the tmobo10 included. Put it on the root if your SD and there you go flash an ics rom. Just remember to delete it after.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
^^ This. Kohr-Ah's thread is the way to go then.
On a side note, you might be able to write supercid after flashing the 1.27 bootloader because the one floating around is already unlocked by revolutionary. Why bother? Because it'll make things easier if we have to upgrade our firmware again in the future.
antiparadigm said:
Thanks a bunch. I will give it a go a third time, but that is one of the problems that I am having, is that I can't flash anything via bootloader. I just get tons of errors...
Lets see if the third time is a charm.
EDIT: I still can't use revolutionary for Super CID because the bootloader is 1.23, but I used a Terminal window and the getprop ro.cid/mid and got this:
Cid-T-MOB010.... is this super CID'd?? I was looking for a reference post, but cant remember where I found it before.
Click to expand...
Click to collapse
Forget Revolutionary. You are already S-OFF so you don't need the tool any more. All you need to do is flash the 3.32 firmware (it comes with HBOOT 1.27, ICS won't boot on 1.23) from >here<, and SuperCID (look here at step 4: http://forum.xda-developers.com/showthread.php?t=1192300).
Okay, I am on the right track now. I hunted and hunted, and finally found a PG58IMG that would flash on my bootloader. That put me on the 1.27 bootloader which allowed me to flash the unlocked 1.17 Bootloader which previously would not flash. now I am trying to get the RUU to flash me back to a non-Rooted ROM so I can reflash the 3.32 and then ICS... Once again, I miss my Vibrant's flashing simplicity... but it will all be worth it.
Thanks for your assistance, everyone with positive non-flaming comments. Expect your thanks buttons to get some love!
Someone else correct me if I'm wrong here due to misunderstanding that last post...
But if you're on the 1.17 bootloader unlocked and everything is smooth there, you should be able to flash the 3.32 firmware right not, then flash whatever ICS ROM you want. The current ROM should have no bearing on this. There is no reason to flash to a non rooted ROM just so you can immediately flash a new ROM.
You just need to have either Clockwork or 4EXT recovery installed to flash the ROM. (And you'll need 4EXT to flash a couple of them. Not all will work with Clockwork)
antiparadigm said:
Okay, I am on the right track now. I hunted and hunted, and finally found a PG58IMG that would flash on my bootloader. That put me on the 1.27 bootloader which allowed me to flash the unlocked 1.17 Bootloader which previously would not flash. now I am trying to get the RUU to flash me back to a non-Rooted ROM so I can reflash the 3.32 and then ICS... Once again, I miss my Vibrant's flashing simplicity... but it will all be worth it.
Thanks for your assistance, everyone with positive non-flaming comments. Expect your thanks buttons to get some love!
Click to expand...
Click to collapse
Thanks for the thanks.
Though once you had the 1.27 revolutionary bootloader, you could've just flashed an ICS rom right then and there and been done with the whole thing. The 1.27 bootloader that's floating around actually comes from the 3.32 (rom base) firmware so you would have been good to go. You really didn't need to revert to 1.17 hboot and flash a non rooted rom.
Don't worry, it really is easy flashing a Sensation, you'll see. It's just that a lot of our guides are outdated and end up confusing people who come into the scene post gingerbread.
/edit
Skipjacks is right. You can go from 1.17 hboot to 1.27 hboot (3.32 rom base firmware) without worrying about your current rom.
I had tried to flash the ICS Rom several times, only to have Boot loops and get stuck. I was following several guides posted here that say that you have to be on a non-rooted rom. I will give it another go to see if there is any change.
That's really weird. Which ICS rom are you trying to flash?
Did you get the T-MOB010 3.32 firmware from here and make sure md5 was correct? This firmware is really the only prerequisite for flashing a 3.32 base ICS rom.
Just keep in mind that 3.32 firmware only works for ICS and will bootloop a gingerbread rom.
There's a really good and simple step by step on how to flash ICS in the first post on the link. Check it out.
OMG It Works! I was boot looping like crazy and could not get anything to boot!
I am not sure but I think the problem may have been the radio, or the wrong Firmware for my CID. My phone would not work with the adb Radio.imgthough so I left it alone.
Correct me if I am wrong on the radio idea, but I flashed the 3.32 and I would get stuck at the White HTC screen. Tried SuperWiping and Flashing three different Roms and no-go.
Then I found this thread:
http://forum.xda-developers.com/showthread.php?t=1459767
I downloaded the right one per my TMO CID and was able to flash it, which also updated the Radio. After another superwipe and Rom Flashing, it worked!
THanks again for all of the help. You are all really appreciated. ALong with this whole community.
Haha that's Kohr-Ah's thread where we were telling you to go to for 3.32 firmware.
Honestly, I'm not really sure what was causing your bootlooping. There's so many little things that could cause a bootloop, it's hard to pinpoint. But hey you've got it running now so it's all good.
Welcome to ICS and welcome to the Sensation community.

[Q] OTA Updates on rooted, 111111, s-off, custom rom devices?

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.

[Q] Stock HBoot to replace JB HBoot

Hello all,
So finally, I have managed to S-OFF my phone using JuonoputBear (I never get this spelling right!). Downloaded the latest version for Ubuntu and can't believe I only did the wire trick once and it was done.
But anynow, to my surprise, the JB tool went on installing the JB hboot itself. Initially I thought it would ask me to install it or not and I would refuse it but... it didn't even give me the option. So now I am stuck with the JB hboot which I dont want.
So the questions is, is there any way I can revert back to the stock hboot?
Thanks guys, all your help made it possible for me to S-OFF my phone.
Regards
just to know that with patched hboot you are fully unlocked and you can use all fastboot commands
i don't find a reason to return to official hboot
rzr86 said:
just to know that with patched hboot you are fully unlocked and you can use all fastboot commands
i don't find a reason to return to official hboot
Click to expand...
Click to collapse
Thanks for the reply. The reason I wanted to go back to stock hboot was that its highly unlikely that I would be using those extra fastboot commands. Besides, I dont like the Juoponutbear logo on top of the hboot.
Also, now that I am S-OFF, I am kind of gone sensitive to installing any ROM. I intend to install Android Revolution HD ROM but I dont want to flash anything wrong on my device like Radio etc. I only want to flash whats need to run that new custom ROM. I guess that doesn't include the kernel as I already have ICS stock ROM.
Can anyone point me to the right direction? Where I can find the steps to install custom ROM without any risk of flashing something wrong?
Thanks.
Jeanz Sensation said:
Thanks for the reply. The reason I wanted to go back to stock hboot was that its highly unlikely that I would be using those extra fastboot commands. Besides, I dont like the Juoponutbear logo on top of the hboot.
Also, now that I am S-OFF, I am kind of gone sensitive to installing any ROM. I intend to install Android Revolution HD ROM but I dont want to flash anything wrong on my device like Radio etc. I only want to flash whats need to run that new custom ROM. I guess that doesn't include the kernel as I already have ICS stock ROM.
Can anyone point me to the right direction? Where I can find the steps to install custom ROM without any risk of flashing something wrong?
Thanks.
Click to expand...
Click to collapse
Hi,
There is no way you can "Accidently" install a radio.
You are not in bootloader for any length of time normally,so ,it should not matter what is written at the top.
That is just the way Juoponutbear operates and leaves it's mark.
It is the only way to s-off for you,so ,you are stuck with it.
Unless you s-on again.
As for flashing ROMS,put it on the root of your sd card,choose zip,install zip.
That's it.
EDIT:
Someone correct me if I am wrong.
If you flash Kohr-Ah's Universal 3.33 firmware,does it say Universal at the top?
malybru said:
As for flashing ROMS,put it on the root of your sd card,choose zip,install zip.
That's it.
Click to expand...
Click to collapse
Is that all? I thought that once you have flashed the zip package, you have to extract the "boot.img" from that zip package of the ROM and flash it separately?
Jeanz Sensation said:
Is that all? I thought that once you have flashed the zip package, you have to extract the "boot.img" from that zip package of the ROM and flash it separately?
Click to expand...
Click to collapse
Hi,
That is the beauty of s-off.
No separate flashing.
malybru said:
Hi,
That is the beauty of s-off.
No separate flashing.
Click to expand...
Click to collapse
Ahh I get it now. Thanks mate.
malybru said:
Hi,
There is no way you can "Accidently" install a radio.
You are not in bootloader for any length of time normally,so ,it should not matter what is written at the top.
That is just the way Juoponutbear operates and leaves it's mark.
It is the only way to s-off for you,so ,you are stuck with it.
Unless you s-on again.
As for flashing ROMS,put it on the root of your sd card,choose zip,install zip.
That's it.
EDIT:
Someone correct me if I am wrong.
If you flash Kohr-Ah's Universal 3.33 firmware,does it say Universal at the top?
Click to expand...
Click to collapse
if i remember well last time kohr-ah said that it it says firmware 3.33(i am not sure)
malybru said:
Hi,
That is the beauty of s-off.
No separate flashing.
Click to expand...
Click to collapse
Sorry I had to come back on this one. I was checking the Android Rev. HD thread and in the download section it said it is necessary to flash new firmware package before flashing this ROM/ And the firmware package also contains radio flashing.
Since I am on Stock ICS at the moment and my firmware is 3.32. Do I still need to flash my firmware?
Jeanz Sensation said:
Sorry I had to come back on this one. I was checking the Android Rev. HD thread and in the download section it said it is necessary to flash new firmware package before flashing this ROM/ And the firmware package also contains radio flashing.
Since I am on Stock ICS at the moment and my firmware is 3.32. Do I still need to flash my firmware?
Click to expand...
Click to collapse
it is not necessary
the rom will boot with that firmware too:good:

Categories

Resources