Related
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)
followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
kirkcody said:
followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
Click to expand...
Click to collapse
That's a tough one to nail down. Below is the stock recovery from the 1.84 t-mobile OTA. Maybe flash that and try the clear storage option.
Also, you might try doing the the Mainver Fix in the all in one tool kit. It's an option in the box in the lower right hand corner.
https://dl.dropbox.com/s/g4r0ryvjy6oce9k/recovery.img?dl=1
Thankyou my friend ill give it a go
unfortunately that didn't work either...i don't know why this wont work for me
kirkcody said:
unfortunately that didn't work either...i don't know why this wont work for me
Click to expand...
Click to collapse
This same thing happened to me at some point. I would suggest just starting over and redoing all the steps.
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
If that doesn't work use a hammer and smash the thing =)
Actually instead of using a hammer I would change to super cid and use a different RUU that had the same hboot as the one your on.
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
@usaf22 really? Did that method work for you?(thought it may not work because we don't have s-off) Did it also remove the tampered and relocked banners? Thanks for both of you guys help will give it a go.
(Edit Hboot wont detect the PJ40IMG.zip )
usaff22 said:
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
No that won't work. Has it ever worked on the One S?
Didn't work Hboot didn't detect PJIMG.zip :crying:
kirkcody said:
Didn't work Hboot didn't detect PJIMG.zip :crying:
Click to expand...
Click to collapse
Did you try all this?
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
kirkcody said:
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
Click to expand...
Click to collapse
link no good-deleted
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Fixter said:
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Click to expand...
Click to collapse
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
dc211 said:
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
Click to expand...
Click to collapse
I got it working guys, but I know why. I was using the incorrect RUU. The link said it was the one for 1.83 but it was for the 1.5 version. I download it again and sure enough it's the 1.83 one. I guess I'm back to work now.
One question and this may save a big headache lol... did you LOCK your bootloader back? I had a couple RUU's that didn't work for me either, but I didn't follow the step of locking the bootloader I was just trying to flash over. Once I relocked I was good to go.
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
kirkcody said:
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
Click to expand...
Click to collapse
Your problem is that there is only 1 RUU you can use. Only 2 exist for T-mobile US and one you can't use because the hboot is lower then yours. But you're kinda lucky that a new OTA came out today. So a newer T-mobile US RUU should be out in a few days, that's normally how long it takes football to get them.
Here's a link to eh 1.83 RUU that should be fast. https://dl.dropbox.com/u/76257867/RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
Our you can try to get the OTA. You should be able to see it now if you check for software updates but it should fail to install. I saw you're using the 1.06es radio. You'd have to go back to the original radio, recovery, lock the booloader and factory reset. For it to work.
I know you should be able to get it working I was stuck where you're at but my Hboot also said "Security Warning" and RUU's & OTA's wouldn't run which I really haven't seen anyone else get.
So a few days ago I rushed into using htcdev to unlock my bootloader without fully researching. I then tried to flash: aospX 1.0.0-MR1 in haste. I couldn't use cwm or ext4 because it stated the phone was not rooted. I assumed since I unlocked the bootloader using htcdev that I wouldn't need either for some reason. I tried flashing the rom using the directions found in glevitan's newbie guide: http://dl.dropbox.com/u/30674730/ULTIMATE ACE GUIDE V5.pdf. In the directions that were given on step 5 I just booted in hboot instead of cwm or ext4. So basically what I did is go into hboot and fastboot and tried flashing the boot img.
After that it seemed as though it was flashing but then it went to a picture of a phone with a red exclamation point next to it. Now in the past two days I have been researching how the fix my problem from acting hastily without researching first. None of my research or actions thus far have been able to get me past hboot. I have tried the directions in the following thread and have not been able to fix the issue: http://forum.xda-developers.com/showthread.php?t=1396229
When I try to reinstall recovery by the directions given in that thread nothing really happens and it just goes back to hboot. When I try flashing the Inspire 4g stock rom in the thread I get error messages in hboot that say invalid image! and it will flash to the white HTC splash screen for a few seconds and then vibrate and go black then back to htc splash screen for a few seconds then back to the picture of a cell phone with a red exclamation point next to it.
The only semi-success I have it trying to flash a RUU (RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe)
But when I try to install the RUU it will install for a few minutes but then I get an error message because it is an older version than I have and wont allow me to "downgrade" because I am currently on 3.20
Any help to try to get this phone back up?
Best guess is (and double check first) relock the bootloader and flash the ruu.
Sent from a dream.
Teichopsia said:
Best guess is (and double check first) relock the bootloader and flash the ruu.
Sent from a dream.
Click to expand...
Click to collapse
First thing, thanks for the response.
It wont let me flash the RUU, I have version 3.20.xxxx and the only ruu I can find is older versions and it wont allow me to flash an older version. The bootloader is already relocked btw.
I'll get back to you. I have to finish doing a few things that will take me a few hours or maybe more, then I'll see what I can find.
Sent from a dream.
You have a few options. The exclamation point is because you don't have a custom recovery installed. You have to flash it manually ie fast boot flash recovery recovery.img my guide doesn't cover that as it was written before HTC dev method was available. And those in the inspire land were recommended from flashing the eng hboot.
So anyways. You can flash cwr via fast boot,then attempt to flash aospx. BUT I suggest you actually gain soff.
The 3.20 ruu is available straight from HTC website.
marsdta said:
You have a few options. The exclamation point is because you don't have a custom recovery installed. You have to flash it manually ie fast boot flash recovery recovery.img my guide doesn't cover that as it was written before HTC dev method was available. And those in the inspire land were recommended from flashing the eng hboot.
So anyways. You can flash cwr via fast boot,then attempt to flash aospx. BUT I suggest you actually gain soff.
The 3.20 ruu is available straight from HTC website.
Click to expand...
Click to collapse
Wow can't believe I didn't check there...
Thanks, running the 3.20 ruu at least got me up and running.
Now that your up and running and want to root you should read this.
http://forum.xda-developers.com/showthread.php?t=1839855
As the process is a little different now. Should also check out attn1 site for the kit for any updates
marsdta said:
Now that your up and running and want to root you should read this.
http://forum.xda-developers.com/showthread.php?t=1839855
As the process is a little different now. Should also check out attn1 site for the kit for any updates
Click to expand...
Click to collapse
Thanks that fixed me up. Now rooted and getting ready to flash aospx
EDIT: Got AOSPX running smooth, thanks again!!
OK.. here is the deal: HTC One S, T-MO, flashed recovery (TWRP), NO ROM would work in the WiFi dept. I tried flashing the radio and no matter what I couldnt get it to flash the 1.5 or 1.84 radio. TWRP would take forever and say it was complete, but the radio version still said 1.04 (or something) in hboot.
Also, I tried going back to a Stock Tmo RUU and it would ALWAYS fail at the signature part of the install EVEN THOUGH I relocked my bootloader.
SO- I unlocked my bootloader, I flashed CWM. Works like a charm.. or so it seems. I flashed the radio and it will only boot into CWM. I can flash a ROM but it still only boots into CWM. I cant even get into fastboot. This sucks.
Ideas anyone?
What happens if you do adb reboot bootloader from your computer while the phone is in CWM?
It reboots, the screen flickers for a millisecond or so (I am sure its probably trying to load hboot and gives some type of error so fast that I can't see) and then it goes to CWM. I am thinking about flashing it back to team win recovery...
mbolden said:
OK.. here is the deal: HTC One S, T-MO, flashed recovery (TWRP), NO ROM would work in the WiFi dept. I tried flashing the radio and no matter what I couldnt get it to flash the 1.5 or 1.84 radio. TWRP would take forever and say it was complete, but the radio version still said 1.04 (or something) in hboot.
Also, I tried going back to a Stock Tmo RUU and it would ALWAYS fail at the signature part of the install EVEN THOUGH I relocked my bootloader.
SO- I unlocked my bootloader, I flashed CWM. Works like a charm.. or so it seems. I flashed the radio and it will only boot into CWM. I can flash a ROM but it still only boots into CWM. I cant even get into fastboot. This sucks.
Ideas anyone?
Click to expand...
Click to collapse
mbolden said:
It reboots, the screen flickers for a millisecond or so (I am sure its probably trying to load hboot and gives some type of error so fast that I can't see) and then it goes to CWM. I am thinking about flashing it back to team win recovery...
Click to expand...
Click to collapse
Try flashing the boot.img thats compatible with your ROM. As for going back to stock try this http://forum.xda-developers.com/showthread.php?t=1927939 If you're on Hboot 1.14 then the T-Mo RUU's wont work for you. I had that problem.
antny said:
Try flashing the boot.img thats compatible with your ROM. As for going back to stock try this http://forum.xda-developers.com/showthread.php?t=1927939 If you're on Hboot 1.14 then the T-Mo RUU's wont work for you. I had that problem.
Click to expand...
Click to collapse
OK.. I thought about that.. but my question is: How can I flash a boot.img if I cant get into fastboot? I installed the trickdroid ROM and I have the boot.img from the zip. I DID try to go back to stock (when I could still access everything pretty easily), but It got stuck on the signature part of the RUU. I went back to trickdroid and all was well sans the WiFi not working.
Can I flash a boot.img via ADB since that is the only thing really working right now?
Thanks
-M
If you still need help...
I'm sure you guys have figured this out by now, but I Solved a problem very similar to this one in my Thread. I was able to return to Stock while still being Rooted.
I've been trying to get back to stock so I can send my phone in for warranty, I'm one of the unfortunate ones who is constantly stuck on edge. Current hboot is 2.15 and cid is ROGERS001, unfortunately there's no ruu out there for my hboot, so I had to use the method mentioned in this thread to get back onto a stock rom.
My problem now is even after unrooting using SuperSU, flashing the stock recovery and relocking my bootloader, it still says "tampered". One thing I've notice is that SuperSU is still present under my apps, when I try to open it it says the binary needs to be updated, and my options are to install the SU binary via cwm/twrp, or "normal". The cwm/twrp method just attempts to reboot into recovery and the "normal" method proceeds to an installation screen where it fails immediately.
Am I forced to s-off and SuperCID, then run a different ruu in order to get back to completely stock?