Database Info

Desire s stuck after 2.3.5 update

i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english

same problem here, help is needed!

A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM

Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?

I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.

But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?

Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device

Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...

Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.

@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers

Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!

Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.

[Q] Splash Screen Freezing on Custom ROMS? (S-ON Unlocked doubleshot)

With the kind assistance of Coug76 (who pointed me to Hasoon's fantastic rooting kit!) I was able to get SuperUser access to my unlocked S-ON Doubleshot. Hooray!
Now I'm trying to install a new ROM. I tried the latest CM9 and I also tried Pyr-o-ice 1.1.1. Both times everything seemed to be going well, but on reboot I just got the splash screen. Most recently I let it sit for 12 minutes (I timed myself, so I wouldn't be tempted to lose patience!) just in case... but it seems to be truly frozen.
The first two times I went through Clockwork, copying the .zip file to the sdcard and then choosing "install from sdcard". The most recent time I went through Recovery, making sure to wipe the data first.
After that didn't work (splash screen for twelve minutes) I vaguely remembered someone saying somewhere (I've read a lot of posts here over the last 48 hours!) that HTC users need to flash the boot image separately. I figured it was worth a try, although I'm not sure if Clockwork does that on its own or not, so after installing from the zip file and trying to boot, I copied the boot.img from the pyr-o-ice .zip file onto the sdcard and then I went into fastboot and typed "fastboot flash boot boot.img".
Same behavior--splash screen still frozen. I also see that the "Read Before Posting" thread says "people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based". I did use HTC's unlock tool, so maybe that's my problem? If so, could someone recommend a good gingerbread ROM for me?
Finally, after restoring from a good nandroid backup (I've used it before, earlier today) the screen is still frozen. Is there any chance that this is because I flashed the other boot.img? I would have thought that the nandroid restore would have fixed that?
Thanks!
-=Benjamin

Oh, I just realized that I wasn't flashing the boot.img on my sdcard, I was flashing whatever random boot.img was sitting in the same folder as fastboot. Ok, fair enough. But the rest is still a mystery, and my nandroid recovery still isn't booting.

silly noob

Oh, no question about it! I'm just glad that I knew enough to get the damn thing working again.
But in the future I do want to try custom ROMs, for sure. So, is it true, then, that before I load a ROM via Clockwork, I need to first flash the boot.img from that particular ROM? If so, it makes Clockwork's ROM Manager seem... not very useful.
Thanks!

whirr said:
Oh, no question about it! I'm just glad that I knew enough to get the damn thing working again.
But in the future I do want to try custom ROMs, for sure. So, is it true, then, that before I load a ROM via Clockwork, I need to first flash the boot.img from that particular ROM? If so, it makes Clockwork's ROM Manager seem... not very useful.
Thanks!
Click to expand...
Click to collapse
Clockwork being on your phone makes it much easier to boot into fastboot and recovery modes instead of using the power and volume down method. It's also good for backup and recovery purposes. I was too much of a chicken to try it but if you're feeling brave, you can use the juniptobear method (hope I spelled that right) to gain S-Off. The link below is for the all in one S-Off kit by Hasoon2000 and will take you where you need to go to do this. If you do this, you won't have to use that extra step (flashing the boot.img file) to load a new ROM.
http://forum.xda-developers.com/showthread.php?t=1696373

eparico said:
Clockwork being on your phone makes it much easier to boot into fastboot and recovery modes instead of using the power and volume down method. It's also good for backup and recovery purposes. I was too much of a chicken to try it but if you're feeling brave, you can use the juniptobear method (hope I spelled that right) to gain S-Off. The link below is for the all in one S-Off kit by Hasoon2000 and will take you where you need to go to do this. If you do this, you won't have to use that extra step (flashing the boot.img file) to load a new ROM.
http://forum.xda-developers.com/showthread.php?t=1696373
Click to expand...
Click to collapse
I have S-Off (as it says in hboot) and I got the splash screen freeze.
I have not yet flashed the boot, maybe it says S-Off even though something reset it to S-On? Anyway I am going to flash the boot.img to see if it fixes the splash screen freeze issue (If it does then maybe my hboot is wrong).
---------- Post added at 04:05 AM ---------- Previous post was at 03:55 AM ----------
UPDATE 1:
Flashing the boot.img did not seem to make a difference it did "Okay" but no difference in the splash freeze.
F:\Android\ROM\Unziped>fastboot flash boot boot.img
< waiting for device >
sending 'boot' (4058 KB)... OKAY [ 0.858s]
writing 'boot'... OKAY [ 7.424s]
finished. total time: 8.283s
I am making a n00b mistake some ware but I can't find it. The boot.img on my F: drive is the correct one, even though I should not need to do that since i have S-Off.
UPDATE 2:
FOUND IT, Ok the noob mistake was that I did the 'wipe' only on the cache and I needed to do the 'wipe' on the factory reset 'and' cache.
Ha ha stupid problems... Feels good though now its running. g-apps.... *worked like a charm! Its all working good now.

Need help regarding root and custom ROM's

Hi guys, I had a little play around with my phone a while back before ICS came out and was a bit unsuccessful. From what I can gather, it was the Super CID part of the guide that I missed out, and when I installed the custom ROM it got stuck in a bootloop.
I was unable to sort this out in the short space of time that I had, so I gave it to a friend and he changed the hboot to 1.17.2008.
Currently the phone says S-OFF but no root detected through Titanium Backup. I am a little unsure about what I need to do next to either get it back to stock or at least to a point of being able to install a custom ROM.
Also I do have Clockwork Mod installed.
I installed Android SDK, and HTC sync to find out my CID and after a lot of forum searching I came to a point where i'm stuck now on which RUU I need.
I think this is the one that I need as I am with Vodafone UK and have the normal Sensation
RUU_Pyramid_Vodafone_UK_1.24.161.1_Radio_10.39.9007.00P_10.11.9007.09_M2_release_190798_signed.exe
I also read that the software version part of the RUU could be anything higher than what I already have on my phone, in this case it being Android 2.3.4 Software Version 1.50.161.1
If I am wrong then please point me in the right direction.
Am I right in thinking that I can install using CWM and this should sort it out, or am I missing a ton of stuff?
Hopefully someone will be able to help me out with this one.
P.S I am not too good at understanding some of the abbreviations and slang that you guys use so could you dumb it down for me please :silly:

OK:
For root look up SuperSU then you can install it through ClockworkMod, "Install Zip from SDcard".
If you're on 1.24.161 (I had also installed that) it doesn't seem to let you apply OTA.
For some RUUs look at: http://shipped-roms.com/index.php?category=android&model=Pyramid
I found and installed 1.27.161 then went through the OTA updates to get to 3.32.161 (Vodafone UK with ICS). I only did this to get a backup just in case I need to send it back.
If you have SuperCID you can install 3.32.401 or 3.33.401 which are WWE RUUs, i.e. unbranded so no Vodafone crap.
fastboot getvar cid ------------------------- to find out what you have
fastboot oem writecid 11111111 ---------- to write SuperCID
fastboot reboot-bootloader ----------------- restart bootloader
fastboot getvar cid ------------------------- check it's been written correctly
x.xx.161.xxxx == Vodafone UK == CID "VODAP001"
x.xx.401.xxxx == WWE == CID "HTC__001"
Of course both can be installed with Super CID.
As you have S-OFF you can install a custom ROM, CID is not important. However a couple of points to note:
i) Get the Superwipe scrips from the ARHD thread, This ensures a completely clean phone prior to installing a new ROM. The RUU process automatically does this.
http://forum.xda-developers.com/showthread.php?t=1098849
ii) You need to ensure that the firmware has been updated to the version recommended by the custom ROM, There is a thread "User Friendly Firmware" that you can look at to help on that. So you'l need to read the custom ROM thread to ensure you have the right version installed.
http://forum.xda-developers.com/showthread.php?t=1459767
Note that installing an RUU or Custom ROM will NOT remove S-OFF from your phone. However, if you install a new RUU you'll need to reinstall your custom recovery, ClockworkMod, via a PG58IMG.zip file is easiest. I'm assuming you know about the generic file PG58IMG.zip and its various uses.

You should try reading this: http://forum.xda-developers.com/showthread.php?t=1192300
It's a very useful step-by-step guide!

Thanks for the hasty response, had to leave for work so I have only just got chance to look at this.
If I have read this right then I write the "su-2.3.6.3-efgh-signed.zip" to my SD card and follow the relevant steps to get root.
Then optionally go through the process to get Super-CID and then download:-
RUU_Pyramid_Vodafone_UK_1.27.161.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_191974_signed.exe
this should then enable me to receive the ICS OTA update that I have been getting the notification for, for ages
or
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
And then I can write any custom ROM after this?
Hope you can understand this.
P.S I have done a backup into CWM just in case this goes wrong

Spalding89 said:
Thanks for the hasty response, had to leave for work so I have only just got chance to look at this.
If I have read this right then I write the "su-2.3.6.3-efgh-signed.zip" to my SD card and follow the relevant steps to get root.
Then optionally go through the process to get Super-CID and then download:-
RUU_Pyramid_Vodafone_UK_1.27.161.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_191974_signed.exe
this should then enable me to receive the ICS OTA update that I have been getting the notification for, for ages
Click to expand...
Click to collapse
Yes
or
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
And then I can write any custom ROM after this?
Click to expand...
Click to collapse
You don't need to install either to install a custom ROM. However, If you install this you'll automatically get the 3.32 firmware and radio. Then as long as the custom ROM has that as a requirement you're fine. Just need to SuperWipe then install.
The x.xx.401..... RUU has less bloatware, i.e. NO Voda crap.
I also found the 3.33.401..... RUU at: http://htcfanboys.com/download/rawdealer/?action=browse&folder=4141
If you just want a custom ROM, install the appropriate firmware (as detailed in the custom ROM's OP) from the XDA forum I mentioned then SuperWipe and install it through CWM.
MAKE SURE that you take regular Nandroid backups with CWM, just in case !!!!
Hope you can understand this.
P.S I have done a backup into CWM just in case this goes wrong
Click to expand...
Click to collapse

Thanks for the help
I now have successfully move over to ICS using the RUU that you posted the 3.33.401.1 version.
The only niggle I have now is that after installing Titanium Backup to restore my apps and data it says that I have no root? no SuperUser, and I can't seem to get into recovery, as if its not even there.
So I went through the process of downloading the appropriate file from this thread "http://forum.xda-developers.com/showthread.php?t=1192300"
and trying to get the phone to install it itself through the Vol down + Power way but it did nothing.
I then tried doing it the cmd method and it still doesn't work.
When I type in the command - "fastboot flash recovery recovery.img"
it comes up with " OKAY [ 0.341s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.342s"
I'm sure everything that I have done is right but if not then could someone please shed some light into this problem please
Thanks

Spalding89 said:
Thanks for the help
I now have successfully move over to ICS using the RUU that you posted the 3.33.401.1 version.
The only niggle I have now is that after installing Titanium Backup to restore my apps and data it says that I have no root? no SuperUser, and I can't seem to get into recovery, as if its not even there.
So I went through the process of downloading the appropriate file from this thread "http://forum.xda-developers.com/showthread.php?t=1192300"
and trying to get the phone to install it itself through the Vol down + Power way but it did nothing.
I then tried doing it the cmd method and it still doesn't work.
When I type in the command - "fastboot flash recovery recovery.img"
it comes up with " OKAY [ 0.341s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.342s"
I'm sure everything that I have done is right but if not then could someone please shed some light into this problem please
Thanks
Click to expand...
Click to collapse
You'll need to install recovery via the PG58IMG.zip method. Do a search for "PG58IMG-CWM5020.zip" or some such term. It'll need to be renamed to be exactly "PG58IMG.zip" on the root of the SD card. Then the next time you go into the boot loader it'll ask you if you want to install it. When it's finished it will ask you to press power to reboot, at this stage you either need to have deleted the file, renamed it to something like PG58IMG-CWM5020.zip or removed the SDcard or it goes in to a bit of a loop.
You should then be able to get into recovery and install SuperSU.zip as before.
I tend to keep a copy of the CWM in the PG58IMG.zip format on my SDcard.
The Power Vol- possibly isn't working as you have FastBoot enabled in setting. To make sure just pop the battery out, wait a few secs and try again.
EDIT:
Found one for you: http://forum.xda-developers.com/showpost.php?p=28365583&postcount=4509
Just checked the MD5 with my copy of PG58IMG-CWM5020.zip and it's exactly the same.

Thanks again
This worked great first try, it must have been the file I downloaded because this is the exact way that I did it before.
Now I will try to open recovery an write superuser.

Followed Step 3 of this thread - http://forum.xda-developers.com/showthread.php?t=1192300
And after installing Titanium Backup so that i could restore my backup, it comes up with the error message that i have no root.
What have I done wrong this time?

Installing SU is a straighforward install zip from within the custom recovery.
Did it come back with any messages. Step 3 is a little muddled, confuses nandroid backup with installing the zip.
i) Do a Nandroid backup first.
ii) Install Zip from SDcard
choose zip from SDcard
Yes - Install xxxxxx.zip
Osh Bosh should have root.

{HELP} device is keep booting into recovey -- SOLVED --

To the Guru of this forum. After my last rom flashing my device is keeping booting into recovery :crying:. Is it briked ? If so my only hope is the unbricking project ? Thanks in advance.

What recovery are you running?
Can you use the power menu within recovery to boot into bootloader?
Also, please provide as much pertinent info as possible, ie: rom you flashed, firmware, s-off or s-on, locked or unlocked. With your description it's basically like saying, "my car makes a noise all the time. what is causing it?".

Its not bricked.If u can enter recovery
Sent from my HTC sensation

Sorry you are right:
What recovery are you running? 4Ext
Can you use the power menu within recovery to boot into bootloader? yes
The device is HTC unlocked with S-On.
Rom JBMIUI v4.1 2.8.31 R2.
HBOOT 1.27.0000
firmware 3.33.401.6
I've format everything but SD. Restored the most recent back up done today before flashing. Once it reboots HTC logo comes up once, black screen, HTC logo, 4Ext is coming up saying that smartflash it is set to update the boot partition on next system start asking if this should be removed.
I've downloaded and installed again PG58IMG *different files using bootloader
I've founded a 3.33.401.6-Unsecured-Boot.img,+Root+Busybox zip file that can be installed via recovery but it did not help.
At this point I need a bit of help to look into the right direction and I'm not sure that Unbrick_Pyramid is the right way.
Thanks again.

Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2

Hi. Manage to flash a stock 3.33.
It stopped to reboot straight into recovery.
Sits now on HTC logo now for about 10 mins. I plan to let him run for 1 hr and see what happens.
Was thinking to install CWM on the basis that could be a 4ext recovery issue, toughs?
GROGG88 said:
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse

If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app

Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Skipjacks said:
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse

DiscreteTask said:
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Click to expand...
Click to collapse
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.

CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Skipjacks said:
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh
version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
Click to expand...
Click to collapse

DiscreteTask said:
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Click to expand...
Click to collapse
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.

Hi.
I did not use any backup only fresh ROMs: ARHD, Elegantia, but also stock ROMs I could find.
I've tried also some PG58IMG with ROM included.
Cheers.
Skipjacks said:
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Click to expand...
Click to collapse

Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app

Hallo, after trying all option the following did work for me:
- re-lock bootloader via fastboot oem lock
- apply stock ROM founded in this list http://forum.xda-developers.com/showthread.php?t=1074559
- rebooted fine
I guess that HTC RUU had some superpower and erase and installed whatever file(s) were corrupted.
Now I'm on stock 3.6 - fw 3.33.401.106 - radio 11.76A.3504.00UU_11.24A.3504.31_M
HBOOT 1.29 - S-ON - Relocked.
Standard Recovery.
Now I'm reading how to return my device to S-OFF w/o damaging it again.
Many thanks to skipjacks & groog88 :good:
Skipjacks said:
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse

[HOW-TO] Revert to Stock ROM JB for user with new HBOOT

Hi to All,
I want to share my experience about revert to stock for users that have new HBOOT, unlocked bootloader and custom recovery; can't execute official RUU. ( This method i think is more safe that downgrade HBOOT )
Step ONE:
Install this custom ROM: MaximuS ROM ( read the thread for instruction about installation of this ROM )
( this ROM allow you to receive the message of OTA JB update, if you know another ROM that receive this message you can use as well i think )
Step TWO:
install the stock recovery of HTC One S via fastboot ( after flashing recovery erase cache )
Step THREE:
Reboot your phone in system, configure the rom for first use, go to settings, information, software update and press check now for update.
You'll receive the message for an update, download and install, and now you have stock JB ROM. after reboot you can do a reset ( go to setting => backup and restore ) to clean the application migrated from previous ROM ( MaximuS )
I hope this can help someone else.
p.s. Sorry for my English!

Thanks bro for this, but my problem is not resolved because this rom couldn't install on my HTC One S, i dont know why... Log show me: MD5 files not found

CybulPL said:
Thanks bro for this, but my problem is not resolved because this rom couldn't install on my HTC One S, i dont know why... Log show me: MD5 files not found
Click to expand...
Click to collapse
Witch recovery are you using at the moment? I installed this ROM ( MaximuS ) with Team Win Recovery ( TWRP ) v2.3.3.0 and it's works for me.
( after flashing ROM from recovery remember to flash boot.img by fastboot )

Maverick87Shaka said:
Witch recovery are you using at the moment? I installed this ROM ( MaximuS ) with Team Win Recovery ( TWRP ) v2.3.3.0 and it's works for me.
( after flashing ROM from recovery remember to flash boot.img by fastboot )
Click to expand...
Click to collapse
I use TWRP and CWM and the same. My mate told me that i have unmount 1 and 2 partition in recovery but i don't know how.

Hi everyone,
thanks a lot, this saved my ass ... I had upgraded my stock ICS to stock JB and then tried to go back to stock ICS with a CWM backup - with the result that I had a brick booting only to a black screen.
I still had access to CWM recovery and so could install the Maximus 2.5 ROM and also the update to stock JB ran through just fine.
I did a factory reset afterwards, is it 100% sure that I now have a pure stock JB or could there be some leftovers from the Maximus 2.5 ROM?
Cheers,
Tim

tim_h said:
Hi everyone,
I still had access to CWM recovery and so could install the Maximus 2.5 ROM and also the update to stock JB ran through just fine.
I did a factory reset afterwards, is it 100% sure that I now have a pure stock JB or could there be some leftovers from the Maximus 2.5 ROM?
Cheers,
Tim
Click to expand...
Click to collapse
Yes you have a stock JB, because with factory reset you've removed all extra application that there is inside MaximuS v.2.5.
All other unneeded file or executable ( like root executable and all other script in /system ect. ) was removed during installation of new ROM.
Remember just that you need to revert to stock to give your phone back to HTC for guarantee, I thinks you must leave on it the stock recovery.
tim_h said:
Hi everyone,
thanks a lot, this saved my ass ... I had upgraded my stock ICS to stock JB and then tried to go back to stock ICS with a CWM backup - with the result that I had a brick booting only to a black screen.
Cheers,
Tim
Click to expand...
Click to collapse
It's happened because from recovery the system was unable to flash the boot partition. So after you did the CWM restore, you have all the phone with ICS android, but JB kernel, this cause your black screen after boot!!!
If you have the boot.img ( with suitable kernel of your old ROM ) to flash after you did the CWM recovery, you can get back to your BACKUP without any problem.
Also if you don't have the exactly boot.img of your previous ROM of the backup, you can flash any boot.img by fastboot of ICS kernel and this is should be enough to keep your backup running again.

Thanks very much for the additional explanations. I do have the boot.img of my original CWM backup, so should be able to restore it via fastboot. Great!
But first I have to send in my phone to have the USB port fixed under warranty.

Holy ****, is working, thanks man...

zujko said:
Wait to see if i understood, i have now Custom ( Virtuous Ville+ RC-1) JB ROM, with hboot 2.15.0000... unlocked, root, twrp
1.install maximuS V2.5, wipe..
2. flash boot.img with fastboot
3.Check update for JB, and flash new update JB?
And that's it?
I guess we have to make relock bootloader, after flash ICS?
Tnx
Click to expand...
Click to collapse
You just forgot in the list to install the HTC Stock recovery before check the message of update, so:
1 => Wipe and install MaximuS V2.5 ROM
2 => flash with fastboot boot.img of MaximuS V2.5 ROM
3 => flash stock HTC Recovery via fastboot ( fastboot flash recovery ville_recovery_signed.img , then fastboot erase cache ) or get it from One_S_All-In-One_Kit_v1.0
4 => start the phone and check for the JB update
5 => after JB installation do a factory reset to clean up the ROM from the extra application that MaximuS ROM have.
You don't need to relock your bootloader, you just need to install the stock recovery, that's enough.

Hmm, wait, why need install stock recovery?
This JB will be working with custom twrp?
EDIT: I got it

I did it! I unmounted first 3 partitions in TWRP and installation successful.

I am on stock Rom now and used HTC offical update to get to jb...do u think I will have trouble rooting again?
Sent from my HTC One S using xda premium

k1llacanon said:
I am on stock Rom now and used HTC offical update to get to jb...do u think I will have trouble rooting again?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I will let you know if I can get it working and flashed it will be rooted in seconds just need stock recovery.

Rooted without a problem, recommend the attached superuser app.

Maverick87Shaka said:
You just forgot in the list to install the HTC Stock recovery before check the message of update, so:
1 => Wipe and install MaximuS V2.5 ROM
2 => flash with fastboot boot.img of MaximuS V2.5 ROM
3 => flash stock HTC Recovery via fastboot ( fastboot flash recovery ville_recovery_signed.img , then fastboot erase cache ) or get it from One_S_All-In-One_Kit_v1.0
4 => start the phone and check for the JB update
5 => after JB installation do a factory reset to clean up the ROM from the extra application that MaximuS ROM have.
You don't need to relock your bootloader, you just need to install the stock recovery, that's enough.
Click to expand...
Click to collapse
Will this work on a T-Mobile HOS with CID HTC__001?
I have followed all the steps from above
- installed the rom
- installed the stock recovery
- then I was able to start the update but when it finished downloading .. I was told that the HTC software on my device has been modified and please revert back and try the update again and it would not preform the update.
What am I doing wrong?
Thanks in Advance

Hi once more,
after going back to pure stock JB this way, can I relock the bootloader to get "RELOCKED" instead of "UNLOCKED/TAMPERED"? (That would be good for sending in my phone under warranty.) Or will the phone stop booting if I relock the bootloader?
As far as I understood, the "canonical" way to get "RELOCKED" would be to lock the bootloader and install the RUU, but since there is no RUU for the unbranded JB yet and downgrading with an older RUU is not possible, I cannot do this.
Cheers,
Tim

tim_h said:
Hi once more,
after going back to pure stock JB this way, can I relock the bootloader to get "RELOCKED" instead of "UNLOCKED/TAMPERED"? (That would be good for sending in my phone under warranty.) Or will the phone stop booting if I relock the bootloader?
Cheers,
Tim
Click to expand...
Click to collapse
You can do Relock bootloader, i think it will boot to system without problem(?)

blah blah blah said:
Will this work on a T-Mobile HOS with CID HTC__001?
I have followed all the steps from above
- installed the rom
- installed the stock recovery
- then I was able to start the update but when it finished downloading .. I was told that the HTC software on my device has been modified and please revert back and try the update again and it would not preform the update.
What am I doing wrong?
Thanks in Advance
Click to expand...
Click to collapse
+ 1
Sent from my HTC One S using xda app-developers app

The only word of caution that I think needs to be shared on almost all threads related to JB updates is to make sure you DO NOT have SuperCID... There have been numerous reports of phones bricking with the OTA JB update with a SuperCID... So if you had previously SuperCID your phone with 11111111, definately change it to something else.

AKToronto said:
The only word of caution that I think needs to be shared on almost all threads related to JB updates is to make sure you DO NOT have SuperCID... There have been numerous reports of phones bricking with the OTA JB update with a SuperCID... So if you had previously SuperCID your phone with 11111111, definately change it to something else.
Click to expand...
Click to collapse
I had to go supercid to run the euro ruu and changed it to HTC__001. Ota still didn't work
Sent from my HTC One S using xda app-developers app