Database Info

[Q] My phone doesn't boot after loading back a stock firmware

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.

[Q] Desire S, Rooted, S-On, Cant flash new custom ROM

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

[Q] stuck on splash-screen

Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow

onemanshow85 said:
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
Click to expand...
Click to collapse
Hi,
2 things you can try.
1.Run a GingerBread RUU.
Look HERE
2.If that works,try s-off.
Look HERE
Then,you could change firmwares and do whatever you like.

Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
edit: I downloaded and executed a RUU that apearantly wasn't compatible with the phone. I'm guessing it removed whatever ROM was installed, but didn't install the ROM from the RUU.
I also followed step 3; RUU to restore stock up to the part of relocking the bootloader. I didn't come any further cause I can't find the right RUU.
the phone now only boots into bootloader with "security warning" displayed below "relocked".
I'm guessing, if I find the correct RUU with gingerbread, things will be okay again.
on a sidenote, does a RUU install also returns the recovery to stock?

onemanshow85 said:
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
Click to expand...
Click to collapse
Hi,
RUU does not matter too much as long as it is Europe and GB.
If you can find a dutch tmo ,then even better.
No harm will come if it is the wrong one.
It will only throw up an error.
This will at least get a ROM on your phone,so that you can s-off .
Revolutionary is the easiest way to s-off.

so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?

onemanshow85 said:
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
Click to expand...
Click to collapse
Hi,
The closer the match,the more chance of success.
But close will do.
Yes,with the same radio.

finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?

onemanshow85 said:
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
Click to expand...
Click to collapse
Hi,
Try the European RUU with the 10.14 radio that matches yours.
Add your CID in the PG58IMG text file.
Make sure you have the phone in fastboot when you attach your USB cable(it should say "fastboot USB"),and start running the RUU from your PC.

http://db.tt/A7lS7PaD
Here is a link to 4ext touch recovery as a IMG. http://db.tt/KFKpcrhB and here is a pg58img.zip. put the zip file onto the sdcard and boot to boot loader. It will hopefully flash the recovery. If not fast boot flash the IMG. Once you have the recovery installed enable smart flash and then flash the roms. Hopefully that will work for you
Sent from my HTC Sensation using xda premium

tnx for the files.
I tried the suggestions you made but flash from sdcard doesn't work; it checks the file once and doesn't do anything after it.
when I try to flash either one of the files through fastboot I get signature verification fail.
my bootloader says RELOCKED, I got that after following step 3.1 in the RUU flash guide to return to stock. I don't know if this is blocking anything from being flashed with the nasty signature notifications?
also, most like because nothing is installed on my device, when I plug in the USB cable when it's turned off, it automatically swithces on displaying SECURITY WARNING below RELOCKED.

Damn, wasn't fast enough. I'm not sure what the best way to approach this is. Either attempt to full s-off the device with revolutionary/ jupuntobear, or re-unlock your boot loader with htcdev, then fastboot flash the recovery. Then install the rom. Then run jupuntobear to full s-off
Sent from my HTC Sensation using xda premium

heavy_metal_man said the right thing. First focus on unlocking it on hTCdev.com and afterwards, flash a 4Ext Recovery to make things easyer. Then put the device in bootmenu (not in the Graphic shell) and attach a USB, start any Official European RUU that is Gingerbread - with 1.50 in the numbers.

an update
I managed to get it unlocked again with htcdev.com. After that I flashed 4EXT recovery, succesfully.
only thing now I need to do is installing a ROM. I tried the following without succes so far:
with RUU
I can't find a dutch RUU for TMO with radio 10.14.9035 anywhere so I tried the closest match possible, a german one. through the .exe method I get incompatibility errors. So I extracted the ROM/.zip, added my CID and tried with SDcard flash and fastboot flash, both unsuccesfull. Hboot checks the file twice and does nothing afterwards, and fasboot prompts the message "FAILED (remote ** unknown fail)"
Universal firmware package to make sure I'm on 3.32, so I can install ARHD 6.7.2 or any other ICS rom
I took one from http://forum.xda-developers.com/showthread.php?p=21711154#post21711154.
I get the same errors as when I was trying to flash the ROM.zip from the RUU, both with sdcard flash and fastboot flash.
a random Gingerbread ROM
I found this GB ROM http://forum.xda-developers.com/showthread.php?t=1226564.
I installed it through EXT4. after a reboot it's stuck in a bootloop. No splash screen is shown however, it get's to the withe-field-green-HTC-screen and reboots after, showing the same.
I don't understand what's wrong. I got a good recovery now and the bootloader is unlocked. For some reason the ROM's I tried are incompatible with the current state of the device and I can't figure out why. are dutch T-mobile branded phones so tough to crack or what?
also, after a certain step wich I can't remember, my bootloader doesn't display a radio anymore.
Current bootloader:
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
EDIT: I would be less restricted in my actions if the damn thing were to be S-OFF. is there any way to get get S-OFF through bootloader/fastboot? All the S-OFF methods and utillities I found so far need the device to have a ROM running.

SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help

onemanshow85 said:
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
Click to expand...
Click to collapse
Glad you got sorted pal and thanks for letting us know

[Q] Desire S bricked by not downgrading Hboot?

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.

[HELP] Messed phone, messed situation - I'll show you

Hello - I'm new here,
Some day ago I was trying to change rom on my HTC One S. I've ended up with Cyanogenmod which worked almost ok but after some update system crashed.
So I was trying to find something else - I've ended on Venom.
I was having issues almost all the time - phone was resetting, had calling, signal issues.
Then today I was trying to install another rom but I've ended "softbricked" after installing newest Cyanogenmod for One s. Just blank screen after flashing it from recovery.
Please help me to make this phone to work I will have some big problems without it (I know I'm stupid messing with that in the first place)
Anyway if there's some good souls on XDA, here's my specs:
Team Win Recovery project 2.7.1.0
HBoot 2.15 - Tampered, S-On (no idea what happened)
radio 1.1.50
opendsp-v31.1.0.45.0815
And my situation: I was trying to install ANY of windows 8.1 driver that works with this phone but none of it was working properly. I have only connected and sent zip files trough adb commands (while in recovery).
PLEASE HELP! So many hours on this and nothing works as it should.
*crying idiot*
What rom should I install to make this phone shine again?
I have now unlocked fastboot on Windows thanks to http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337

Since you didn't mention it I got to ask you whether you flashed the kernel (boot.img) via fastboot after you flashed any rom via your recovery. Due to the fact that your phone is still S-ON none of the roms here on xda is going to work properly without that step.
I guess your problems started because the cyanogenmod update you tried to install contained a new kernel your phone couldn't flash on its own (because of the S-ON status).
Just unzip the "boot.img" from the rom archive into your fastboot/adb folder and flash it with "fastboot flash boot boot.img" and your phone should work properly again.

Thanks!
I have flashed new boot.img before installing rom from recovery (http://forum.xda-developers.com/htc-one-s/development/unofficial-slimkat-hboot-2-15-t2918217). And rom worked correctly - without reboots. I hope that is the end of my problems.
Should I do S-off and get rid of that Tampered thing? Or I can leave it as is?

Well, that depends on you. If you want do downgrade your hboot, install the leaked hboot 2.16 or don't want to be obliged to always flash the kernel seperately then you should S-OFF your phone.
The "tampered" actually has no effect besides that it may annoy you. It dissappeared after I ran a RUU the first time.