Hey Guys
First time poster here and not massively technical at all so be gentle with me
Ok so over the weekend I decided I wanted to see what all the fuss was about with these custom ROM's that you can download. So I did some research and decided to give it a go. Please bear with me dudes. So what I did was as follows:
1) Unlocked the bootloader following HTCdev.com guide. Success
2) Rooted the phone, now have super user and can grant SU permissions to apps. Success
3) Installed ROM Manager, latest version. Success
4) Attempted to Flash clockworkmod to recovery using ROM Manager. Stated success in the app.
5) In ROM Manager I attempted to make a backup of my stock rom, asked me to enter a backup name and click OK, device reboots and I see a red exclamation mark when it tried to reboot into recovery, suggesting that step 4 was actually a failure.
6)Downloaded latest clockworkmod image file from the clockworkmod site and using a tool called android flasher (I think) I was able to flash the recovery image to the recovery partition. Phone reboots and boots into recovery and boom I have the clockworkmod recovery available to me.
7) Immediately took a backup of my stock rom so can convert back if things go pear shaped. Success.
8) I downloaded 2 custom rom's, Cyanogenmod latest 7.1.0 build and MIUI custom rom, both for Desire S. Success
9) Put both rom's onto my 8GB sd card as instructed by a guide I was following and booted into clockworkmod and wiped cache, data and system. Success
10) In clockworkmod selected install zip from SD card, found the Cyanogen zip and selected it, it proceeds to install. Reports success.
11) Reboot phone and it hangs on the HTC logo screen, nothing doing. Failure.
12) I have to boot back into CWM and restore my backup which is a success.
So what I end up with is my stock rom with an unlocked bootloader, rooted as I have superuser app and can grant SU permissions to ROM Manager and titanium backup. But I don't seem to be able to get a custom rom on there. I have tried formatting sd card, putting a new rom on and then taking battery out for 15 mins but again nothing doing, everything I try I just get a hanging HTC logo after reboot and again I have to restore my backup that I made to get a working phone again.
Here are some details from the bootloader:
**** UNLOCKED ****
SAGA PVT SHIP S-ON RL
HBOOT - 2.00.0002
RADIO - 3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Sorry for the mahoooooossive post guys but its really bugging me that I cant get a custom rom on there, stock rom rooted just wasn't what I was looking for.
Really hope you guys can give some help/advice
Stewie
All yours steps seems fine to me.
The first time you flash a custom rom, it could takes MINUTES before boot (Once I waited 10 min with a rom).
How long did u wait when the HTC logo appeared?
Have you tried to S-OFF your Desire S?
It could be one of the reason why you can't flash properly.
Here all the guides (maybe you already know everything):
http://forum.xda-developers.com/showthread.php?t=1186401
EDIT:
As I suspected, it does stated it clearly in the link I gave you:
FAQs:
1. What's S-OFF and S-ON?
- If your phone is S-ON, you won't be able to root or flash custom ROMs to your phone. S-OFF let's you to have full control of your phone.
(NOTE: S-OFF is not ROOT, S-OFF your device does not mean that your device is Rooted. They are totally two different things.)
yukinok25, dude thanks for that, I was kinda thinking that it may have something to do with the s-on / s-off thing.
I'll have a butchers at trying to s-off the device, but I thought it was supposed to be a pretty tricky procedure with the version of HBoot that I have on my device, i.e 2.00.0002. So I was hoping to avoide the s-off process but if I gotta do it then I gotta do it, just hope it all goes ok.
Again thanks for the link man, good to get some help as im a bit of a rookie at this sort of stuff ;-)
Cheers
Stewie
Anytime mate.
Just because you are new to XDA: you can use the thanks button next time...
Not sure if this is still relevant, but there is a simple guide on the Dev forum on how to S-OFF the new HBOOT:
http://forum.xda-developers.com/showthread.php?t=1525100
Also, the recommended custom recovery is 4EXT, which is based on Clockwork but more advanced. There is even a touch version now:
http://forum.xda-developers.com/showthread.php?t=1377745
Related
Hi,
Recently I flashed my phone to CyanogenMod 7.1. Later on I changed my mind and wanted to use the latest stock ROM. Specifically RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed.exe.
I extracted the file and followed the instructions. After the flashing is done, I got stuck with the HTC logo on the white screen.
Before that I rooted my phone using Revolutionary and used ClockworkMod to install any image, but now this part is gone due to flashing to stock firmware... so I get the original Android system recovery with options like reboot, apply update from sd card, wipe data/factory reset and wipe cache partition.
So, as a result, I am still able to go to the boot menu as usual, but I can't install any image. When I try to open the CyanogenMod ROM file from the sdcard, I get this message:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
My boot menu shows this:
- Revolutionary -
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
Click to expand...
Click to collapse
I tried to connect the USB cable to my PC, but I could not get adb working. Actually, the only thing that recognized my phone was the exe file of the stock firmware (in FASTBOOT USB mode). I wish that I could use revolutionary again or at least to deactivate signature verification, so I would be able to flash using the extended recovery screen (and as a result I would be able to install any ROM that I want).
How do I get out of this messy situation?
Thanks a lot for your help.
The thing messed up because the phone was able to successfully update the ROM, but its your HBOOT now which has a problem. What you've tried to do will NEVER gonna work. You have managed to S-OFF your phone, you should have know already that its unchangeable (on a certain angle).
The latest official ROM uses system/lib on a separate partition but your HBOOT does not support that. That maybe one of the reason why ROM is not booting up.
Installing CM directly won't be successful as you are not in a custom recovery.
Method to get out of this messy situation:
1. Install custom recovery via fastboot
2. Install custom ROM again
3. If you really want to be on stock, you need to change your HBOOT first to either the old S-ON or S-OFF HBOOT, then RUU (GoldCard recommended). It's just easy considering you are still on revolutionary HBOOT.
All the step's guides has already been posted a LOT on the forum, use search.
Hint!
|
V
Thanks so much. That really helped. I thought that getting the original stock ROM back would be as easy as setting a new ROM, so I am back to CM7.1 and everything is fine now.
barman1 said:
Thanks so much. That really helped. I thought that getting the original stock ROM back would be as easy as setting a new ROM, so I am back to CM7.1 and everything is fine now.
Click to expand...
Click to collapse
Good to hear you got it working. Ask a mod to close the thread.
#CASE SOLVED#
Hi,
I was using CWM7 and then i tried to flash my phone with shipped custom ROM that was listed on this link http://forum.xda-developers.com/showthread.php?t=1002506&page=37
I chose this version "RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed"
I followed all the procedure and all the process was going right. However, when the phone start to rebooting, it stuck at HTC logo screen for almost half an hour.
I tried the (up) (down) (power) procedure and "adb reboot recovery" but none worked. So i pulled off the battery and try to restart it. However, it stopped again at HTC log screen.
I can still access my recovery, so is there anything that I can still try to do?
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3882.10.08.04_M
NB: this info might useful; when i went to the recovery and connect the usb it mention "HBOOT USB PLUG"
Any help or hint will be really appreciated...
zul.zulkarnaen said:
Hi,
I was using CWM7 and then i tried to flash my phone with shipped custom ROM that was listed on this link http://forum.xda-developers.com/showthread.php?t=1002506&page=37
I chose this version "RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed"
I followed all the procedure and all the process was going right. However, when the phone start to rebooting, it stuck at HTC logo screen for almost half an hour.
I tried the (up) (down) (power) procedure and "adb reboot recovery" but none worked. So i pulled off the battery and try to restart it. Alas, it stopped again at HTC log screen.
I can still access my recovery, so is there anything that I can still try to do?
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3882.10.08.04_M
NB: this info might useful; when i went to the recovery and connect the usb it mention "HBOOT USB PLUG"
Any help or hint will be really appreciated...
Click to expand...
Click to collapse
With the latest Sense 3.0 RUU, the ROM requires that the corresponding HBOOT 2.00.0002 get flashed too in order to boot properly. Since you have S-OFF via Revolutionary, the Revolutionary HBOOT 6.98.1002 is preventing the RUU from overwriting the it, therefore you have ended up with a ROM / HBOOT mismatch and that is why the ROM hangs at the HTC screen.
IMO you would be better off sticking with custom ROMs that have implemented Sense 3.0/3.5 and keeping S-OFF.
From this point you probably need to reinstall ClockworkMod recovery from FASTBOOT mode and then you can restore you nandroid backup (you did make a backup before you attempted this, right?) to get back to CM 7
I did make a backup. But right now, when I choose recovery I can only goes to the stocked recovery. My CWM recovery is lost after the flashing. And when I navigate through the stocked recovery, I can't find a way to restore my last ROM.
zul.zulkarnaen said:
I did make a backup. But right now, when I choose recovery I can only goes to the stocked recovery. My CWM recovery is lost after the flashing. And when I navigate through the stocked recovery, I can't find a way to restore my last ROM.
Click to expand...
Click to collapse
Yes I understand that CWM is no longer there. I said you need to reinstall it using Fastboot.
Look at this thread
http://forum.xda-developers.com/showthread.php?p=14693680
Oh, I didnt know that there's manual process, I only knew the one that use the web. OK, I'll try it
SOLVED. Thanks a lot..
zul.zulkarnaen said:
SOLVED. Thanks a lot..
Click to expand...
Click to collapse
NP. Glad to help. I noticed you updated your first post with SOLVED. It would also help if you modified the Title of your first post and "SOLVED" to it also. That way when others are browsing the threads, they know that a solution is in the discussion.
I know there are probably other threads that can help me but I'm really desperate here. I just got my Sensation 4G (T-Mobile) a few days ago and decided to root it and install a custom ROM. This is my first Android device so I followed a newb guide specifically for the Sensation 4G. However, I think I accidentally missed the step describing how to S-Off and I ended up trying to install Cyanogen Mod 9. It installed ok but I got stuck at the boot screen. From there, I tried restoring to a backup I made before installing Cyanogen but it didn't work. Now I'm stuck at the HTC logo. Can anyone help me out? Here are some more details about my device:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012, 17:33:34
I think my firmware is 3.32 and the Android version was 4.0.3 although I guess there's nothing on it now.
EDIT: The latest guide I followed shows how to install/flash the stock ICS firmware but I couldn't update the firmware. It says "Parsing .zip" but doesn't go further than that.
Enable smartflash in 4ext recovery, then flash Rom again
Enviado desde mi HTC Sensation 4G
serio22 said:
Enable smartflash in 4ext recovery, then flash Rom again
Enviado desde mi HTC Sensation 4G
Click to expand...
Click to collapse
I don't have 4ext recovery installed, only CWM. Is there a way to install it even though I can't boot into the phone?
Yeah, just have to flash another recovery (4ext) through fastboot.
If you look around the development section, you'd probably find a guide how to do it, if not PM me, and I'll give you the steps.
Have a look in this thread: http://forum.xda-developers.com/showthread.php?t=1631861 Asskicker's guide, how to flash roms with S-ON. If you don't want to flash the 4ext recovery (I highly recommend to install it!) then you can do Step "EXTRA 1" from that guide and install "boot.img" from the downloaded rom. You find it in the zip file, in the kernel folder. But read the guide, there are plenty of very useful info in it! And to answer your question, No! Your phone is not bricked!
matekaneve said:
Have a look in this thread: http://forum.xda-developers.com/showthread.php?t=1631861 Asskicker's guide, how to flash roms with S-ON. If you don't want to flash the 4ext recovery (I highly recommend to install it!) then you can do Step "EXTRA 1" from that guide and install "boot.img" from the downloaded rom. You find it in the zip file, in the kernel folder. But read the guide, there are plenty of very useful info in it! And to answer your question, No! Your phone is not bricked!
Click to expand...
Click to collapse
I have a bunch of ROMS that I've tried and they're all on my desktop. Only two of them have a kernels folder, so I guess the other two are using a stock kernel and I can't use them, right? I'll try following that thread you linked me to, hopefully it'll work this time.
EDIT: It worked! Thank you so much! Now if I wanted to install Cyanogen Mod 9 for example, which doesn't have that kernels folder, I would need to S-OFF first right?
If you want to install ROM's without being S-OFF I'm pretty sure you need 4EXT.
And for future reference to all who may find this thread down the road, if you can get into your Recovery (any recovery) your phone is almost certainly not bricked. You may have a lot of fixing to do, but it's almost certainly fixable.
When the splash screen doesn't even come up after hitting the power button or the charing light doesn't come on when plugged in...that's when it's time to worry. (And even then you may have options)
Skipjacks said:
If you want to install ROM's without being S-OFF I'm pretty sure you need 4EXT.
And for future reference to all who may find this thread down the road, if you can get into your Recovery (any recovery) your phone is almost certainly not bricked. You may have a lot of fixing to do, but it's almost certainly fixable.
When the splash screen doesn't even come up after hitting the power button or the charing light doesn't come on when plugged in...that's when it's time to worry. (And even then you may have options)
Click to expand...
Click to collapse
I did the wire-trick to S-OFF my device. WHen I first did that, my only option in the bootloader was RUU and I was about to ask you about that but took my battery out first. Now it's back to normal and it shows S-OFF. However, my microSD card is now completely wiped. I have a backup on my computer, so should I just copy the files back on there and try another ROM so that my WiFi will work?
Ir0nMa1deN said:
I did the wire-trick to S-OFF my device. WHen I first did that, my only option in the bootloader was RUU and I was about to ask you about that but took my battery out first. Now it's back to normal and it shows S-OFF. However, my microSD card is now completely wiped. I have a backup on my computer, so should I just copy the files back on there and try another ROM so that my WiFi will work?
Click to expand...
Click to collapse
copy your files into sdcard then reboot your device
about wifi you can flash the boot.img manually(maybe you do not need that because you are S-OFF now)
otherwise flash your rom again
up the irons:good:
Ir0nMa1deN said:
I did the wire-trick to S-OFF my device. WHen I first did that, my only option in the bootloader was RUU and I was about to ask you about that but took my battery out first. Now it's back to normal and it shows S-OFF. However, my microSD card is now completely wiped. I have a backup on my computer, so should I just copy the files back on there and try another ROM so that my WiFi will work?
Click to expand...
Click to collapse
Yes. Just copy everything back. Everything will be where its supposed to be.
Sent from my HTC Sensation using xda app-developers app
rzr86 said:
copy your files into sdcard then reboot your device
about wifi you can flash the boot.img manually(maybe you do not need that because you are S-OFF now)
otherwise flash your rom again
up the irons:good:
Click to expand...
Click to collapse
Haha I was waiting for that "Up the Irons." My username is pretty much the same on every site I register on so I always get that. Anyway, I'm not sure what's going on with the WiFi but I'm going to try a different ROM and hope WiFi works there.
:highfive:
Hey guys,
I can really use your help - I thought this would be relatively easy but boy was I wrong.
I started with an HTC Sensation (locked / unrooted / S-ON / ICS) with HBOOT 1.27
What did I do to end up where I am now?
1. http://forum.xda-developers.com/showthread.php?t=1497404 - I followed all the steps top left to unlock the bootloader, which succeeded. Only to find out I needed to S-OFF the device differently.
2. http://forum.xda-developers.com/showthread.php?t=1614617 - I followed this guide, but did nothing with step 2 (I didn't have a superuser application and couldn't get root because I didn't have any custom abilities since the device was S-ON still). Device was succesfully S-OFF.
3. Here I installed JuopunutBear HBOOT-1.27.1111
4. Then I flashed CWM Recovery 6.0.0.3 for the pyramid by following these instructions: http://www.androidauthority.com/sensation-clockworkmod-recovery-6-0-0-3-custom-recovery-105930/ and removed the PG58IMG.zip file again.
5. Now I booted the CWM Recovery with a fully empty Micro-SD card (already formatted from previous use in same device). I do a factory reset and wipe all cache (including dalvik/battery stats). I then install January 9 '13 release (Bruce AOKP) and then GAPPS latest version for 4.1.2 - succesful.
6 Here I think I am done, reboot ... HTC white screen ... reboot ... HTC white screen ... CWM Recovery. What the ... happens everytime. After some searching people said because my phone was unlocked (HTCDev method) before installing custom ROM I should install boot.img manually. Did that (yes I used the boot.img from Bruce his zip) using fastboot flash boot boot.img - succes (so it said).
7. Step 6 changed nothing ... and here I am stuck .... please help me to get into my favourite mod!
Extra information: Version-Main = 1.24.401.1, full JuopunutBear intro screen info:
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
eMMC-boot
Jan 13 2012, 17:33:34
Please help me continue and make it run. I have a feeling maybe something in the root steps or whatever - but this process is not as easy as many users here make it seem. Sifting through the info ... I was surprised I got this far :silly: ...
SensationProblem said:
Hey guys,
I can really use your help - I thought this would be relatively easy but boy was I wrong.
I started with an HTC Sensation (locked / unrooted / S-ON / ICS) with HBOOT 1.27
What did I do to end up where I am now?
1. http://forum.xda-developers.com/showthread.php?t=1497404 - I followed all the steps top left to unlock the bootloader, which succeeded. Only to find out I needed to S-OFF the device differently.
2. http://forum.xda-developers.com/showthread.php?t=1614617 - I followed this guide, but did nothing with step 2 (I didn't have a superuser application and couldn't get root because I didn't have any custom abilities since the device was S-ON still). Device was succesfully S-OFF.
3. Here I installed JuopunutBear HBOOT-1.27.1111
4. Then I flashed CWM Recovery 6.0.0.3 for the pyramid by following these instructions: http://www.androidauthority.com/sensation-clockworkmod-recovery-6-0-0-3-custom-recovery-105930/ and removed the PG58IMG.zip file again.
5. Now I booted the CWM Recovery with a fully empty Micro-SD card (already formatted from previous use in same device). I do a factory reset and wipe all cache (including dalvik/battery stats). I then install January 9 '13 release (Bruce AOKP) and then GAPPS latest version for 4.1.2 - succesful.
6 Here I think I am done, reboot ... HTC white screen ... reboot ... HTC white screen ... CWM Recovery. What the ... happens everytime. After some searching people said because my phone was unlocked (HTCDev method) before installing custom ROM I should install boot.img manually. Did that (yes I used the boot.img from Bruce his zip) using fastboot flash boot boot.img - succes (so it said).
7. Step 6 changed nothing ... and here I am stuck .... please help me to get into my favourite mod!
Extra information: Version-Main = 1.24.401.1, full JuopunutBear intro screen info:
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
eMMC-boot
Jan 13 2012, 17:33:34
Please help me continue and make it run. I have a feeling maybe something in the root steps or whatever - but this process is not as easy as many users here make it seem. Sifting through the info ... I was surprised I got this far :silly: ...
Click to expand...
Click to collapse
Hi,
Did you root your phone?
Look HERE
malybru said:
Hi,
Did you root your phone?
Look HERE
Click to expand...
Click to collapse
Root is a userspace level thing that shouldn't affect the installations of ROMs, plus all ROMs (except for stock ROMs) come pre-rooted. SensationProblem, I suggest you install the TWRP recovery from here: http://techerrata.com/file/twrp2/pyramid/openrecovery-twrp-2.4.1.0-pyramid.img
Flash this using fastboot. This is the command to flash it:
Code:
fastboot flash recovery openrecovery-twrp-2.4.1.0-pyramid.img
After it completes successfully, reboot the bootloader then after it reboots back into the bootloader select the bootloader option then just enter the recovery from there. In the recovery, go to Wipe and wipe the Cache, Dalvik Cache, Factory Reset, and System, then flash Bruce's CM10.
android1234567 said:
Root is a userspace level thing that shouldn't affect the installations of ROMs, plus all ROMs (except for stock ROMs) come pre-rooted. SensationProblem, I suggest you install the TWRP recovery from here.
Flash this using fastboot. This is the command to flash it:
Code:
fastboot flash recovery openrecovery-twrp-2.4.1.0-pyramid.img
After it completes successfully, reboot the bootloader then after it reboots back into the bootloader select the bootloader option then just enter the recovery from there. In the recovery, go to Wipe and wipe the Cache, Dalvik Cache, Factory Reset, and System, then flash Bruce's CM10.
Click to expand...
Click to collapse
Dude that worked, thank you so much (want to give kudo's - can't find button). Can you maybe shortly explain to me why it worked? Because as I can understand it now it was because of something in the CWM Recovery that was messing things up?
SensationProblem said:
Dude that worked, thank you so much (want to give kudo's - can't find button). Can you maybe shortly explain to me why it worked? Because as I can understand it now it was because of something in the CWM Recovery that was messing things up?
Click to expand...
Click to collapse
The current version of CWM for the Sensation is extremely old and, as a result, does not support the installation of Jelly Bean ROMs.
Hi all!
First of all: I know. I am a dumbass for not doing a backup. (and several other things)
Second: Thank you for your time! I really appreciate it- thats why I tried for two days to solve the problem by searching the internet for guides to restore my phone and not stealing your time.
If you just want to help me - skip the first part ("The story"). I just had to write it down, because I am that desperate and hopeless...
The story
Beside my Nexus 5 I wanted a spare phone to go outdoors and have a nice small phone - other than the huuuuuuge Nexus.
My last phones were the HTC Sensation, a Desire GSM and the Wildfire. So I decided to get a Desire S and do what I did to all my phones and tablets yet: root it.
Because I had the dumb idea that rooting a couple of phones makes me an expert I skipped the "reading guides"-part and jumped right to the "beeing an idiot"-part and downloaded the Revoked-tool.
After I got the TWRP-recovery I also skipped the "making a backup"-part and that is where my disaster began....
The problem
I tried to root my phone, but I did not reverse the Hboot. So now my phone IS NOT s-off, but I've got a working recovery installed and I can get into Fastboot and the Bootloader.
But because my partitions are wiped I can neither boot normally nore can I install a custom recovery (because of the "s-on").
My phone has got an O2-branding, so I can't install the normal Android 4.0 RUU. Neither works the O2 RUU. I suppose, because it still is the Android 2.4 - Version ( the name of the file is "RUU_Saga_O2_UK_1.31.206.1_Radio_20.28b.30.0805U_38.03.02.14_M_release_178935_signed.exe") and it does not work with my phone....
Is there any chance to get a working Desire S again?
Thabks for your time....
u have stock recover. and u have (i suppose) an unlocked bootloader.
have u tried flashing the recovery through fastboot command ?
fastboot flash recovery recovery.img
download TWRP or 4EXT touch zip file - then unpack it and copy the recovery.img inside it to fastboot or android-tools folder
open cmd there (preferably with admin rights)
and run that command.
if it is able to flash a custom recovery, then u can try to flash a rom.
u might need to check if u have a sony or hitachi screen panel though (but that should have been before u tried rooting, i think)
Hi rht_sg,
thanks for your answer!
Right. My Bootloader is unlocked.
The problem is the "S-ON" I think.
I've got a recory installed, but I can not intall any custom ROM because of the "S-ON"-Mode.
Here the important things I have foregotten in my first post:
In FASTBOOT my phone says:
"
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.19.00.110
eMMC-boot
"
...and my recovery is TWRP v2.4.0.0
You can install a custom rom without being s-off, but you have to flash the boot.img (from the rom) manually in fastboot after installing the rom in recovery (fastboot flash boot boot.img).
I would recommend updating your recovery to either twrp 2.7 (from the thread in this forum) or the latest 4ext touch. One reason being that older recoveries fail when trying to flash kit-kat roms (error 7).
To update your recovery while still s-on, use fastboot (fastboot flash recovery recovery.img)
Thanks!
That solved it. - Now I could install a custom ROM again.
Now I follow your advice to flash the latest recovery.