Database Info

Desire S in one real mess...

Hi all, well i was playing with my Desire S trying to install the generic wwe rom on it since it is brands, and ended up messing up the phone real badly.
Well i used the good old way of creating a gold card and then flash the RUU. The first time went well, i flashed the generic 1.28.401.1 rom on it, retaining the 0002 boot it had.
Then i went to flash the 2.10 wwe RUU and this time things went bad. For some reason the gold card powers were not evoked and it gave me "CID error" but, the all mighty 2.00.0002 hboot was flashed on the phone before it gave the error. So i had to downgrade the bootloader and i used this great guide as a help but once again things went wrong.
I flashed a pre rooted RUU 2.10 rom using 4EXT recovery as the guide tells to do but, i have no wi-fi and usb connection on the rom. This means i got no way to connect the phone to a pc to change the misc_version file and don't even have wi-fi. So i end up asking for any help here as the phone is left in a very bad situation that i can't see the way out...

Try to reflash same ROM again.
Sent from my Desire S

I believe you should have named your thread "I really messed up my Desire S", as the current title is sort of misleading ;-).

In your place I'll try flashing an older ROM, even your initial one and start over. If you still have acces to 4EXT recovery you just have to take out your sdcard, put it on a pc and copy the rom that way (since USB not working). Or you can try to activate USB drive within 4EXT recovery, maybe it'll work.
If you don't have 4EXT recovery, you can try flashing recovery.img (from 4EXT zip file) or a rom by renaming them as PG88IMG.zip and place them on the card (via PC). If you boot to bootloader and try to flash them using the flash procedure for radio, it might work like this.
Sorry if I am saying a stupid thing but this is what I'll try if I had these issues.

Rapier said:
In your place I'll try flashing an older ROM, even your initial one and start over. If you still have acces to 4EXT recovery you just have to take out your sdcard, put it on a pc and copy the rom that way (since USB not working). Or you can try to activate USB drive within 4EXT recovery, maybe it'll work.
If you don't have 4EXT recovery, you can try flashing recovery.img (from 4EXT zip file) or a rom by renaming them as PG88IMG.zip and place them on the card (via PC). If you boot to bootloader and try to flash them using the flash procedure for radio, it might work like this.
Sorry if I am saying a stupid thing but this is what I'll try if I had these issues.
Click to expand...
Click to collapse
Well the initial ROM i had on the phone was a branded Vodafone PT and i can't find that ROM anywhere and for some reason goldcards are not working after the bootloader was flashed by the RUU.
I still have the 4EXT recovery and usb works in it. Flashing a ROM via the PG88IMG only works if the RUU has the right CID as the phone is branded, now i don't know if flashing a rooted ROM using that procedure will work. The other thing i may try is flashing an older rooted ROM, like the 1.28.401.1 and see if the wi-fi and usb works.

Well what i can say is that the phone is completely cursed and i can't find a way out of this.
I tried to flash an older rooted ROM, 1.48 and the same thing happened, no wi-fi and usb connection.
I tried to flash custom ROMs then. Even worse, the phone doesn't boot, gets stuck on the htc logo. I tried more ROMS and the same happens.
Flashing official RUU will not work due to the CID error. All i end up is that i can't put the phone to work, simple as that. The only chance i think is to send the phone to HTC and tell them that a screwed the system and want them to flash it all again. I don't know how much that will cost but it seems to be the only way out.

smash_07 said:
Well what i can say is that the phone is completely cursed and i can't find a way out of this.
I tried to flash an older rooted ROM, 1.48 and the same thing happened, no wi-fi and usb connection.
I tried to flash custom ROMs then. Even worse, the phone doesn't boot, gets stuck on the htc logo. I tried more ROMS and the same happens.
Flashing official RUU will not work due to the CID error. All i end up is that i can't put the phone to work, simple as that. The only chance i think is to send the phone to HTC and tell them that a screwed the system and want them to flash it all again. I don't know how much that will cost but it seems to be the only way out.
Click to expand...
Click to collapse
Return it if you still have warranty. If not, read on:
1. Check you HBOOT if it got updated to the new one.
2. If it is updated, I suggest to flash the pre-root 2.10.5 ROM. Then see if it is going to work.
3. If it does, downgrade from there if you still want to.

Skanob said:
Return it if you still have warranty. If not, read on:
1. Check you HBOOT if it got updated to the new one.
2. If it is updated, I suggest to flash the pre-root 2.10.5 ROM. Then see if it is going to work.
3. If it does, downgrade from there if you still want to.
Click to expand...
Click to collapse
Yes it has warranty but im sure it will not be covered since i was the one who messed up the phone system.
Another thing i can do, but this is not a certain option, is to wait and see if alpharev can find a way to S-OFF the new hboot with revolutionary and then open a way to flash the RUUs again and older bootloaders.
But i am more looking to sending it to HTC. Does anyone have an idea how much does it cost to reflash the system on the phone?

smash_07 said:
Yes it has warranty but im sure it will not be covered since i was the one who messed up the phone system.
Another thing i can do, but this is not a certain option, is to wait and see if alpharev can find a way to S-OFF the new hboot with revolutionary and then open a way to flash the RUUs again and older bootloaders.
But i am more looking to sending it to HTC. Does anyone have an idea how much does it cost to reflash the system on the phone?
Click to expand...
Click to collapse
It would really help if you have given your bootloader details.\
Things you still can do:
1. If hboot is updated to 2.00.0002, then you need to unlock it, flash custom recovery via fastboot, flash custom rom, usable phone.
2. If hboot is S-OFF, same as 1 but skip unlocking. Again, usable phone.
Also, there are a lot of ways for you to change your hboot once you are S-OFF. Use search.

You are able to install custom roms, but the phone doesn't boot? And the 1.47 pre rooted boots but no WiFi?
You unlocked the phone with HTC.dev.
Steps:
- pick a custom Rom, any Rom
- extract boot.img from that Rom
- flash the Rom in recovery
- do not reboot
- flash boot.img using fastboot command from your computer (search around for instructions)
- reboot and enjoy
The problem is your phone is still s-on, and blocking the kernel from being written during normal flash. You end up with old kernel and new un-matching modules and libs.
I could be wrong though...
Cheers
Sent from my HTC Desire S using xda premium

I my case, that was may of this year, I send my desire (not s) back because of bootproblems, and they reflashed it for free. This was in the Netherlands so don't know how easygoing they are in Portugal, but it's worth a shot I guess.

lowveld said:
You are able to install custom roms, but the phone doesn't boot? And the 1.47 pre rooted boots but no WiFi?
You unlocked the phone with HTC.dev.
Steps:
- pick a custom Rom, any Rom
- extract boot.img from that Rom
- flash the Rom in recovery
- do not reboot
- flash boot.img using fastboot command from your computer (search around for instructions)
- reboot and enjoy
The problem is your phone is still s-on, and blocking the kernel from being written during normal flash. You end up with old kernel and new un-matching modules and libs.
I could be wrong though...
Cheers
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Well i can say that this has worked. I flashed the boot.img form the CM7 rom and it worked perfectly, it booted CM7 rom and have wi-fi and usb connection. Now the only thing left is to be able to flash official RUUs passing tne CID error which for some reason the Goldcards are not bypassing.
But many thanks for your help
(ou como se poderia dizer, obrigado pela ajuda)

[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] HTC Desire S Flash ROM disaster

Hi all I'm hoping someone out there can help with recovering my desire S. I tried to flash a custom ROM and had a disaster !!!!!!
I unlocked the boot loader using HTCdev, loaded superuser and 4ext recovery. All worked fine. The first ROM I flashed was ICS SAGA Edition v2.0 and flashed the boot.img all seemed well, it started but during installation there were errors about sense not working etc. It looks to me like the ROM is not suitable as the original wall paper is to large for the screen and it is continuously loading.
I have tried subsequent ROMs, CM7 and a few others but they either don't work or get stuck in an endless load. The 4ext backup I made doesn't work either as I get the message unconfigured use 4ext app to set up.
As a final resort I tried to flash the original stock ROM using the RUU exe file but that comes up with error 155 and won't load. Its not completely bricked but without a ROM it might as well be.
The original RUU was 2.10.401.8 CL156318 release keys, the radio is 3822.10.08.04_M and the HBoot 2.02.0002 S-On.
I can still use 4ext recovery but not a great deal else. Perhaps S-Off would have been a better idea !!!!!
Does anybody have any ideas as at the mo I've had to resort to using an old iPhone 3 ..... disaster :crying:
cheers

[Q] 1.73.502 ruu question

Background story:
I was trying to unlock and s-off 1.73 at&t one x phone with 1.09 hboot so that i could install a custom rom... Having experience with some other phones I prepared myself, software, drivers and everything else and plunged into action... I successfully unlocked the phone using a compilation of tutorials since it's so old bootloader and all, as for root i'm not sure I actually managed to get it work, it complained most of the time of missing bin files although I flashed su through recovery again and it settled down. I couldn't s-off it in any of the way tutorials were suggesting, gathering that i would have to update with some newer RUU, so I quit and phone is still s-on. And then I did an incredibly stupid thing, i didn't do nandroid backup, i just wiped system and tried to flash a new rom to no avail... None of the roms won't get flashed, i tryed sense and cm based ones, i'm getting some partition error, something about 2,14 and 2,15, not sure since error reporting is not consistent... Now I'm stuck within recovery and bootloader, i'm unlocked but s-on, i can't flash system img through fastboot nor a custom rom through adb sideload it says that partition is too small.
So question is what am I to do? What is my safest way out? Should i try flashing RUU (the one that should be the original one 1.73.502) or could I run some newer RUU and which would be preferable? If I'm to run RUU 1.73, should I run it as an exe or should I try to flash it as a zip file? Does it matter that the phone is unlocked and s-on? Why won't the smaller cm roms flash, how small could the partition be and does it have something to do with android version (4.1, 4.2 etc)?

To get a working ROM on your phone you can download an old build of cm and flash that. The new builds require updated firmware but the older builds don't. Go here and download the bottom build (stable cm10), and you'll need to get the 4.1 gapps package from here.
Sent from my Evita

What recovery and version number? I have a feeling this is recovery related, more than anything.
Also, newer builds of CM10.2 require hboot 2.14 or 2.15, so that is probably what the error message you mentioned is about.
We should be able to get you back up in and running on the custom ROM of your choice. But if you do decide to go the RUU route, in order to run an RUU, you must relock the bootloader in fastboot. Then you should be able to run the RUU. 1.73 RUU is fine. DO NOT run the 3.18, as there is a bug where with SuperCID and S-on (and you now have both) will BRICK THE PHONE. But the 1.73 or 1.85 RUUs will be fine.
Run the RUU as an .exe. I don't see the point in extracting and running the ROM.zip. You would just be making the process harder than it should be, and also removing some of the safeguards, if I remember properly.
S-off should work on any hboot version. I believe I got s-off while on hboot 1.09.

I'm running twrp 2.5.0.0 recovery, is there newer version? It never crossed my mind that it could something to do with recovery, so I never looked it up... Perhaps I could change it, it's not like that's gonna ruin chance of restoring any previous backups i didn't make...But i'd rather update the phone's firmware just to get those hboot glitches off the way because it, i'm quite sure, obstructed the s-off process (i was getting few 9x errors during s-offing, mostly 99).
So I'd be safe running 1.85 RUU. Is there some other RUU you would recommend, preferably some which will make the whole process of rooting, SuperCIDing and s-offing easier?
Thank you for helping me out!
edit> I tried flashing oldest CM and it worked! Then, feeling safe and all, I flashed newest twrp recovery and then, to my utter amazement, it flashed other rom I was aiming for... So thanks, for that recovery tip, it saved me a lot of pain! Now all is left for me is to figure out that s-off thing...

[Q] Help with hboot update [Solved]

Hi everyone, first of all thanks for any support you may give, I was really hoping to figure this out on my own but I've ended up with 20+ tabs open on the subject and don't seem to be getting anywhere.
So on to issue: Recently fished out my old HTC One S as a friend wants to buy it, however the custom ROM I had installed crashed when using the camera so thought I'd get this all updated for him before he takes it off me, but things have moved on a lot since I was last here, and I'm now stuck getting everything updated.
I currently have hboot 1.13, s-on and root, and my CID is HTC__001
It appears most ROMS now require either hboot 2.15 or 2.16. I incorrectly thought hboot was related to recovery, so I tried to flash latest twrp, but now phone reboots everytime it gets to lock screen, I can still get into fastboot using adb, but I can't access recovery, and I'm now stuck. So any thoughts or input on how to proceed from here would be amazing!
TL:DR:
Currently on Hboot 1.13 with s-on, need to update to 2.15. Phone keeps rebooting, can access fastboot but not recovery. help.
Thanks again, Andrew.
Update: Solved
I resolved my issue by re-locking the bootloader, and installing one of the latest RUUs with hboot 2.15. I could then unlock the bootloader again, flash the latest twrp recovery and get back to installing custom ROMs.

You'll need to flash a recovery with adb. I can't remember if you can do that with S-On, but I don't see why not.
The command is something like: adb flash recovery name-of-recovery.IMG but I don't have my notes with me.
FYI, I always had to run the command twice for it to "stick".
You'll also have to find an older recovery.
Sorry I don't have the actual commands handy, but it shouldn't be too hard to find.
Edit:
Or, you can run the RUU.

Awesome thanks, I just need to find the right recovery and RUU now. I've had a look on Teamwins website and oldest version I can find is 2.1.6, but there is no documentation to say which hboot this supports, however I have a funny feeling I'll need an older version than even that, any ideas where I could find the correct recovery to flash? Thanks again.