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)
Things I have Done (In this Order):
Followed This Guide for Unlocking Bootloader and Flashing ClockworkMod Recovery
Unlocked Bootloader
Flashed ClockworkMod Recovery 5.8.3.1 Touch
Flashed the EU Radio from Here (Still using Stock ROM)
Flashed CyanogenMod 10 NIGHTLY 20121012 Build
Tried to Restore Nandroid Backup (To No Avail)
Flashed Ville-Z Kernel
Flashed CyanogenMod 9 NIGHTLY 20120917 Build (After CM10 didn't work)
Held down the VOL- Button while Rebooting to try to gain access to the Bootloader several times (To No Avail)
Used the ADB Reboot Bootloader Command while in CWM several times (To No Avail)
So, I decided to root my HTC One S today, because I have a Samsung Vibrant that is running CyanogenMod 7, and I really like the abilities that come with being Rooted. I Rooted my Samsung Vibrant myself with no issues, however it seems that my HTC One S is giving me a hard time.
I think the main problem is the fact that I didn't Flash the Boot.img file from the CyanogenMod ZIP, however, now that I am unable to access the Bootloader, I can't even attempt to do that.
Also, I got the CyanogenMod 10 Nightly to get to the Boot Screen when I first flashed it (I only did "Data/Factory Reset"), however, it got Stuck while Booting, so after 15 Minutes of waiting to see if it would proceed, I rebooted it, another 15 Minutes went by with it stuck, and after about 5 Reboots, I gave up, Booted into the Bootloader, hit "Recovery" and got into CWM. Did a "Data/Factory Reset," Wiped Cache Partiton, and Wiped /system, Tried to just Restore my Nandroid Backup, and then began the flickering while its Rebooting and the Bootloop.
After that, I got thrown back into CWM, and then I did a "Data/Factory Reset," Wiped Cache Partiton, and Wiped /system, and then flashed the CM10 Nightly again. Same result, Bootloop, Tried This Solution for trying to get out of the Bootloop, to No Avail.
Then I wiped /system, Data/Factory Reset, and Cache Partiton once again, Flashed the CM9 Nightly, and the same thing happened. It Reboots, screen flickers a few times, and then i'm back to CWM.
So, i'm stuck. I can use ADB with ClockworkMod Recovery, but I can't get into the Bootloader at all. I imagine that there is a way to Flash the Boot.img from CWM, but I have no idea how, nor have I found any Threads on the topic. I would appreciate if you guys could help me on this. I've spent several hours today trying to at least gain access to the Bootloader, but to No Avail. Oh, and sorry for the Wall of Text, I wanted to make sure I covered every angle.
Can this adb command get you into bootloader mode? Use while in CWM but might work while the phone is trying to boot a ROM as well.
adb reboot bootloader
There is a corresponding fastboot command as well, fastboot reboot bootloader or maybe it is fastboot reboot-bootloader.
frdd said:
Can this adb command get you into bootloader mode? Use while in CWM but might work while the phone is trying to boot a ROM as well.
adb reboot bootloader
There is a corresponding fastboot command as well, fastboot reboot bootloader or maybe it is fastboot reboot-bootloader.
Click to expand...
Click to collapse
As stated above, adb reboot bootloader can't get me into the Bootloader. Also, Fastboot doesn't work inside of CWM. I also just tried adb reboot bootloader and fastboot reboot-bootloader while its rebooting (Trying to load the ROM?) to No Avail.
I only get:
Code:
C:\Android>fastboot reboot-bootloader
< waiting for device >
And it hangs. This is the same result I get trying fastboot reboot-bootloader from inside of CWM.
WinterPhoenix96 said:
As stated above, adb reboot bootloader can't get me into the Bootloader. Also, Fastboot doesn't work inside of CWM. I also just tried adb reboot bootloader and fastboot reboot-bootloader while its rebooting (Trying to load the ROM?) to No Avail.
I only get:
Code:
C:\Android>fastboot reboot-bootloader
< waiting for device >
And it hangs. This is the same result I get trying fastboot reboot-bootloader from inside of CWM.
Click to expand...
Click to collapse
Ah sorry didnt see it:-/ actually scanned for it but missed it, I'm on Linux so looked for small letters
Anyways I checked out the CWM-Loop-DeLooper.zip you linked from that LG Connect 4G forum, this is what it does:
Code:
ui_print("Fix'in ****");
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
package_extract_file("recovery.img","/tmp/recovery.img");
run_program("/tmp/busybox", "dd", "if=/tmp/recovery.img", "of=/dev/block/mmcblk0p13");
delete("/tmp/recovery.img");
Basically it installs busybox which is a collection of system tools, then it flashes a recovery.img to /dev/block/mmcblk0p13. Not sure what is on that partition on the One S. This might have screwed things up further since I guess that the recovery.img in that file is not for the One S at all... this is the md5sum of the file, no results when gogling it: fb0db52d705df8bb220ca9f25e3a1f6a recovery.img
Hopefully HTC's S-ON saved you or maybe you have a CWM for the LG Connect 4G. This doesnt explain why you can't get into bootloader mode though. I'd say you should run a RUU but I think you have to be in bootloader or have the phone running for that. Did flashing the Ville-Z kernel work? I f so flash a ROM that is compatible with it. I think the most recent CM-10 builds aftera say 20121004 are not compatible any longer. If Ville-Z kernel didnt flash then you need to flash a ROM that matches the kernel you had before, maybe a stock or Sense-based ROM?
frdd said:
Ah sorry didnt see it:-/ actually scanned for it but missed it, I'm on Linux so looked for small letters
Anyways I checked out the CWM-Loop-DeLooper.zip you linked from that LG Connect 4G forum, this is what it does:
Code:
ui_print("Fix'in ****");
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
package_extract_file("recovery.img","/tmp/recovery.img");
run_program("/tmp/busybox", "dd", "if=/tmp/recovery.img", "of=/dev/block/mmcblk0p13");
delete("/tmp/recovery.img");
Basically it installs busybox which is a collection of system tools, then it flashes a recovery.img to /dev/block/mmcblk0p13. Not sure what is on that partition on the One S. This might have screwed things up further since I guess that the recovery.img in that file is not for the One S at all... this is the md5sum of the file, no results when gogling it: fb0db52d705df8bb220ca9f25e3a1f6a recovery.img
Hopefully HTC's S-ON saved you or maybe you have a CWM for the LG Connect 4G. This doesnt explain why you can't get into bootloader mode though. I'd say you should run a RUU but I think you have to be in bootloader or have the phone running for that. Did flashing the Ville-Z kernel work? I f so flash a ROM that is compatible with it. I think the most recent CM-10 builds aftera say 20121004 are not compatible any longer. If Ville-Z kernel didnt flash then you need to flash a ROM that matches the kernel you had before, maybe a stock or Sense-based ROM?
Click to expand...
Click to collapse
Thanks for the Reply!
Well, if I have LG Connect 4G's CWM now, then its the exactly the same CWM I had before, ClockworkMod Recovery 5.8.3.1 Touch. I think its more likely that HTC's S-ON prevented the Kernel Flash. I'm not sure as to what Partition /dev/block/mmcblk0p13 is on the One S either. I'll look into that when I have a chance and update this Post, but I digress.
You do have to be in at least the Bootloader to run RUU, which I can't access, so that's out of the question at the moment.
I dont believe that Flashing the Ville-Z Kernel worked, because when I tried to Flash ViperOneS ROM (Which is supposedly compatible with it), I still had the same result.
I have not tried to Flash a Stock ROM however, because when I tried Restoring my Nandroid Backup, I still had the same result. I think I'll try to flash a scrubbed version or something of the Stock ROM however, once I get home, and see if that works. I'll try a few different other Sense-Based ROM's as well that are stated to be compatible with the Stock Kernel.
Sent from my SGH-T959 using xda app-developers app
UPDATE
I found out what the /dev/block/mmcblk0p13 Partition is. Its the Data Partition (/data) on the LG Connect 4G's Partition Structure.
Also, I found a ROM that may work Here. If we are even still going down the same path for Flashing ROM's, seeing as I've now gained access to the Bootloader (See Post #7)
WinterPhoenix96 said:
Thanks for the Reply!
Well, if I have LG Connect 4G's CWM now, then its the exactly the same CWM I had before, ClockworkMod Recovery 5.8.3.1 Touch. I think its more likely that HTC's S-ON prevented the Kernel Flash. I'm not sure as to what Partition /dev/block/mmcblk0p13 is on the One S either. I'll look into that when I have a chance and update this Post, but I digress.
You do have to be in at least the Bootloader to run RUU, which I can't access, so that's out of the question at the moment.
I dont believe that Flashing the Ville-Z Kernel worked, because when I tried to Flash ViperOneS ROM (Which is supposedly compatible with it), I still had the same result.
I have not tried to Flash a Stock ROM however, because wheb I tried Restoring my Nandroid Backup, I still had the same result. I think I'll try to flash a scrubbed version or something of the Stock ROM however, once I get home, and see if that works. I'll try a few different other Sense-Based ROM's as well that are stated to be compatible with the Stock Kernel.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
WOW WinterPhoenix96. I am having the EXACT same issue. I even tried a nandroid restore to no avail. Have you found a solution to this issue yet?
-M
Gained Access To Bootloader! How To Proceed?
mbolden said:
WOW WinterPhoenix96. I am having the EXACT same issue. I even tried a nandroid restore to no avail. Have you found a solution to this issue yet?
-M
Click to expand...
Click to collapse
Actually, I saw your Forum Post as well, and I Subscribed to it to see if you ever got a solution. XD But, apparently not yet, and your case was just a Little Bit different than mine, so I started my own Forum Post.
But, The Good News. I FINALLY was able to access the Bootloader! Here's the trick: Let The Battery Die, Then Turn It Back On While Holding The VOL- Button.
So, Bootloader Information, because I don't even want to touch it unless I know for sure how to Proceed:
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0004 <---Note: I've heard that Hboot Version 1.14 causes issues with RUU.
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 14 2012, 18:01:48
So, How Should I Proceed? I've heard RUU won't work on this HBOOT Version anyway, so...
Also, Refer to Post #5's Update.
What issues are caused by hboot 1.14? I think you can never use a RUU to downgrade but always run your current version's RUU or newer. This could be said to be an issue though I guess since 2.31 is the newest RUU atm
WinterPhoenix96 said:
Actually, I saw your Forum Post as well, and I Subscribed to it to see if you ever got a solution. XD But, apparently not yet, and your case was just a Little Bit different than mine, so I started my own Forum Post.
But, The Good News. I FINALLY was able to access the Bootloader! Here's the trick: Let The Battery Die, Then Turn It Back On While Holding The VOL- Button.
So, Bootloader Information, because I don't even want to touch it unless I know for sure how to Proceed:
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0004 <---Note: I've heard that Hboot Version 1.14 causes issues with RUU.
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 14 2012, 18:01:48
So, How Should I Proceed? I've heard RUU won't work on this HBOOT Version anyway, so...
Also, Refer to Post #5's Update.
Click to expand...
Click to collapse
I am letting the battery drain now. So far the recovery screen has been up for days. LOL I cant even turn it off. comes right back on. After it dies I will try to get into fastboot.
-M
RUUs work in HBOOT 1.14.0004 or whatever HBOOT, for that matter, unless the HBOOT in the RUU is lower than yours. In that case, it won't let you flash the ROM.
@mbolden can't you use VOL UP, DOWN and POWER to turn the phone off in recovery?
mbolden said:
I am letting the battery drain now. So far the recovery screen has been up for days. LOL I cant even turn it off. comes right back on. After it dies I will try to get into fastboot.
-M
Click to expand...
Click to collapse
Yeah I had the same
thing. It was on for days on end, then it occurred to me to try that.
usaff22 said:
RUUs work in HBOOT 1.14.0004 or whatever HBOOT, for that matter, unless the HBOOT in the RUU is lower than yours. In that case, it won't let you flash the ROM.
@mbolden can't you use VOL UP, DOWN and POWER to turn the phone off in recovery?
Click to expand...
Click to collapse
Well, I've just heard a lot of people having problems with HBOOT 1.14.0004 and trying to do RUU. Apparently something to do with the Signature Verification Failing.
Also,I haven't tried that. It may work, if you want to look into it, @mbolden.
Sent from my SGH-T959 using xda app-developers app
Guys have you tried to unplug the battery instead of waiting for it to deplete? Looks easy enough to open it up: http://www.youtube.com/watch?v=b0jGY2N2h1U
---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------
BTW there is a bug in CWM that causes the phone to start and boot into recovery when turned off if plugged into USB or charger
frdd said:
Guys have you tried to unplug the battery instead of waiting for it to deplete? Looks easy enough to open it up: http://www.youtube.com/watch?v=b0jGY2N2h1U
---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------
BTW there is a bug in CWM that causes the phone to start and boot into recovery when turned off if plugged into USB or charger
Click to expand...
Click to collapse
Well you see, we (or at least I do) want to be able to do Root It, but without taking apart the phone in the process. I'd rather just wait for the battery to die than permanently break the phone's hardware if I take it apart and screw up.
Also, I am aware of the CWM Bug, however, apparently I forgot to mention it. Thanks!
Btw, nobody has answered How I Should Proceed yet. (Post #7)
usaff22 said:
RUUs work in HBOOT 1.14.0004 or whatever HBOOT, for that matter, unless the HBOOT in the RUU is lower than yours. In that case, it won't let you flash the ROM.
@mbolden can't you use VOL UP, DOWN and POWER to turn the phone off in recovery?
Click to expand...
Click to collapse
I can use the VOL rocker and the power button in recover. I let my battery drain (took 2 days)and tried to boot into fastboot. The screen flickered several times and then it went straight back into CWM. No idea what to do next. Seems that if I can't get into fastboot I am sunk. I cant boot ANY ROM I am stuck in recovery. WTF!??
Any suggestions? Anyone?
-M
frdd said:
Guys have you tried to unplug the battery instead of waiting for it to deplete? Looks easy enough to open it up: http://www.youtube.com/watch?v=b0jGY2N2h1U
---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------
BTW there is a bug in CWM that causes the phone to start and boot into recovery when turned off if plugged into USB or charger
Click to expand...
Click to collapse
I am kind of glad that I didnt open it up. The batt depleted, but it still only boots into CWM.. AAAARRRRGGGHHH!!! (in the voice of the Hulk!)
mbolden said:
I am kind of glad that I didnt open it up. The batt depleted, but it still only boots into CWM.. AAAARRRRGGGHHH!!! (in the voice of the Hulk!)
Click to expand...
Click to collapse
That's really odd... It worked for me... Did you try several times with holding down VOL DOWN while its Booting? It may take a few tries. OH. And its kinda tricky, because If its plugged in while its booting, it will regardless boot to CWM.
I just turned it on without plugging it in, because your battery should be able to power up your phone for like 1 Minute before it legitimately dies, because some of the battery's power is still there, your phone just shuts off when it "detects" its out of battery (Battery Stats).
So, plug it in for just a few minutes to let it get just a bit of charge, then unplug it, let it "die," and then turn it back on while holding VOL DOWN. Then plug it in once it gets to the Bootloader. If it doesn't go to the Bootloader, Rinse and Repeat. Hopefully you'll be able to get into it eventually.
I'M IN!
WinterPhoenix96 said:
That's really odd... It worked for me... Did you try several times with holding down VOL DOWN while its Booting? It may take a few tries. OH. And its kinda tricky, because If its plugged in while its booting, it will regardless boot to CWM.
I just turned it on without plugging it in, because your battery should be able to power up your phone for like 1 Minute before it legitimately dies, because some of the battery's power is still there, your phone just shuts off when it "detects" its out of battery (Battery Stats).
So, plug it in for just a few minutes to let it get just a bit of charge, then unplug it, let it "die," and then turn it back on while holding VOL DOWN. Then plug it in once it gets to the Bootloader. If it doesn't go to the Bootloader, Rinse and Repeat. Hopefully you'll be able to get into it eventually.
Click to expand...
Click to collapse
I got in FINALLY.. I switched from CWM to TWRP (because I read that it will allow you to flash the radio) I tried to flash my radio using radio-0.16.31501S.16_2_10.22.31501S.10L.zip but no matter what it still says my radio version is 1.08ts. Does that sound right? At this point I just want to return to stock so my WiFi will work. This is how this whole fiasco started. :-/ I had the Viper ROM and my Wifi kept turning on and off and would never connect to ANYTHING. So I tried many other ROMS with the same no WiFi result.
When I tried to install the stock RUU, I re-locked the bootloader and installed the RUU only to get a signature err everytime. No one had a solution to the problem. I am kind of stuck (still).
-ideas anyone?
mbolden said:
I got in FINALLY.. I switched from CWM to TWRP (because I read that it will allow you to flash the radio) I tried to flash my radio using radio-0.16.31501S.16_2_10.22.31501S.10L.zip but no matter what it still says my radio version is 1.08ts. Does that sound right? At this point I just want to return to stock so my WiFi will work. This is how this whole fiasco started. :-/ I had the Viper ROM and my Wifi kept turning on and off and would never connect to ANYTHING. So I tried many other ROMS with the same no WiFi result.
When I tried to install the stock RUU, I re-locked the bootloader and installed the RUU only to get a signature err everytime. No one had a solution to the problem. I am kind of stuck (still).
-ideas anyone?
Click to expand...
Click to collapse
Don't know much about RUU's but:
* You can't downgrade anything with a RUU
* The newer RUUs like EU 2.21 and 2.31 will upgrade your HBoot to 1.14 which further locks down the ability to flash radios any other way than with an even newer RUU
* The RUU must be for your CID (~your carrier+country) so
* Bootloader must be relocked I think.
* Check md5sum of your RUU
* Might be good info re RUUs in the shipped ROMs thread in development..
TWRP cant flash a radio anymore than CWM can, they can both do it but you need a low enough Hboot (like 1.06 or 1.09 I think) and you need to fastboot boot your twrp/cwm.img like so:
Code:
fastboot boot cwm-touch.5.8.31-ville.img
Haven't tried TWRP myself, its possible that HTC Dumlock function in TWRP can be used to flash a radio. If youre on 1.08ts you probably have a new Hboot and thats one explanation why you couldn't downgrade your radio.
Most all WIFI problems on these boards are due to people not flashing the boot.img when flashing a new ROM. I would pick any ROM, try TWRP and Dumlock if getting to fastboot is still a rare precious occasion? Sure makes things hard when getting to bootloader is problematic...
frdd said:
Don't know much about RUU's but:
* You can't downgrade anything with a RUU
* The newer RUUs like EU 2.21 and 2.31 will upgrade your HBoot to 1.14 which further locks down the ability to flash radios any other way than with an even newer RUU
* The RUU must be for your CID (~your carrier+country) so
* Bootloader must be relocked I think.
* Check md5sum of your RUU
* Might be good info re RUUs in the shipped ROMs thread in development..
TWRP cant flash a radio anymore than CWM can, they can both do it but you need a low enough Hboot (like 1.06 or 1.09 I think) and you need to fastboot boot your twrp/cwm.img like so:
Code:
fastboot boot cwm-touch.5.8.31-ville.img
Haven't tried TWRP myself, its possible that HTC Dumlock function in TWRP can be used to flash a radio. If youre on 1.08ts you probably have a new Hboot and thats one explanation why you couldn't downgrade your radio.
Most all WIFI problems on these boards are due to people not flashing the boot.img when flashing a new ROM. I would pick any ROM, try TWRP and Dumlock if getting to fastboot is still a rare precious occasion? Sure makes things hard when getting to bootloader is problematic...
Click to expand...
Click to collapse
I can confirm that the Bootloader DOES need to be Re-Locked to perform an RUU.
I don't think the HBOOT Version matters with Flashing Your Radio. I've never heard anything about newer versions causing problems with that.
Don't know what HTC Dumlock does.
Wifi problems are 90% of the time caused by your Kernel or ROM. It CAN however be caused by a Bad Radio Flash.
Same Boat - all CWM, all the time
Took me 2 hours to find this thread...whew.
Any clear set of steps to take once back in bootloader? Safe to say flash TWRP, then reflash custom roms from there? Have rooted/installed custom roms on 5 previous phones without issue...until now. This. is. killing. me.
Thanks in advance for any further tips.
I have been reading and trying to return to stock for over a week, and nothing will work. I used HTCdev to unlock and I installed Jellytime, but now I want to go back to stock to sell it, and I can't get anything to work. It is S-On now, and I think thats why nothing works. I have Clockwork recovery, and the only rom I can get to flash is jellytime, nothing else works. I tried HTC RUU, and that gives me an unknown error. I've tried flashing several PD98IMG's, and they all fail also. I have also tried flashing the att stock rom via RUU and Clockwork recovery, that doesn't work either. Someone please help! Thanks!
tjmortenson said:
I have been reading and trying to return to stock for over a week, and nothing will work. I used HTCdev to unlock and I installed Jellytime, but now I want to go back to stock to sell it, and I can't get anything to work. It is S-On now, and I think thats why nothing works. I have Clockwork recovery, and the only rom I can get to flash is jellytime, nothing else works. I tried HTC RUU, and that gives me an unknown error. I've tried flashing several PD98IMG's, and they all fail also. I have also tried flashing the att stock rom via RUU and Clockwork recovery, that doesn't work either. Someone please help! Thanks!
Click to expand...
Click to collapse
Re lock bootloader. Place phone into fastboot and plug into PC. Run ruu from PC. May need HTC sync installed to avoid errors when running ruu. Also if your hboot is the newest version you will only be able to run the newest ruu from HTC.
Sent from my Motorola Droid RAZR MAXX HD using xda premium.
Gizmoe said:
Re lock bootloader. Place phone into fastboot and plug into PC. Run ruu from PC. May need HTC sync installed to avoid errors when running ruu. Also if your hboot is the newest version you will only be able to run the newest ruu from HTC.
Sent from my Motorola Droid RAZR MAXX HD using xda premium.
Click to expand...
Click to collapse
tjmortenson said:
I have been reading and trying to return to stock for over a week, and nothing will work. I used HTCdev to unlock and I installed Jellytime, but now I want to go back to stock to sell it, and I can't get anything to work. It is S-On now, and I think thats why nothing works. I have Clockwork recovery, and the only rom I can get to flash is jellytime, nothing else works. I tried HTC RUU, and that gives me an unknown error. I've tried flashing several PD98IMG's, and they all fail also. I have also tried flashing the att stock rom via RUU and Clockwork recovery, that doesn't work either. Someone please help! Thanks!
Click to expand...
Click to collapse
In addition to what Gizmoe says, you need To flash an Inspire RUU as you are S-ON. Other RUU's will fail due to cid signature
Thanks, I finally got the RUU to flash, I didn't realize that I had to relock the bootloader, thats why it wasn't working.
Hi I recently tried installing MagioRom and now my phone wont boot. The last working rom I had was MaximusHD 10.0.0. I am S-off, H-Boot 2.15, and T-MOB010 and i have a U.S. Tmobile Htc One S I have tried restoring from several of my nandroids, inncluding my stock nandroid. I've tried several different RUU's (all Tmous), installed many different Roms, but the same thing always happens. The phone will go through the boot process but then freeze at the lock screen, showing only the status bar. After about 15-20 seconds it crashes and reboots. I've tried everything I can think of. Does anyone know how I can fix this? Thanks in advance.
Go back to MaximusHD, this is the only ROM where your new firmware which you flashed will work. None of your nandroid backups will work unless you downgrade your firmware
I tired MaximusHD
usaff22 said:
Go back to MaximusHD, this is the only ROM where your new firmware which you flashed will work. None of your nandroid backups will work unless you downgrade your firmware
Click to expand...
Click to collapse
Thanks for your help but I tried re-flashing MaximusHD, but no luck.It has the same problems as the other ROMs. The aroma installer will work fine and then the phone will boot and it will go through the full boot logo and then the status bar will come up and I can see battery and time, but the rest of the screen is dark. My radio is 1.13.50.05.31 if that makes any difference, I haven't been able to update it.
I see what I forgot do now. I didn't flash the firmware.zip, weird that the ROM worked anyway. I'll download and flash that and let you know if that fixes everything.
So even after trying the firmware.zip and yoouri instructions to install maximus HD it still wont boot. Im now hboot 1.16 and radio 1.20 Im still S-off and Cid is still T-MOB010
xiheartjtag said:
Thanks for your help but I tried re-flashing MaximusHD, but no luck.It has the same problems as the other ROMs. The aroma installer will work fine and then the phone will boot and it will go through the full boot logo and then the status bar will come up and I can see battery and time, but the rest of the screen is dark. My radio is 1.13.50.05.31 if that makes any difference, I haven't been able to update it.
I see what I forgot do now. I didn't flash the firmware.zip, weird that the ROM worked anyway. I'll download and flash that and let you know if that fixes everything.
So even after trying the firmware.zip and yoouri instructions to install maximus HD it still wont boot. Im now hboot 1.16 and radio 1.20 Im still S-off and Cid is still T-MOB010
Click to expand...
Click to collapse
So you could fastboot flash the boot.img and see if that enables your phone to boot.
Then once booted, move the ROM.zip to your phone and reinstall ROM in recovery. (as per instructions) Or sideload the rom in TWRP so that you can reinstall the rom.
Still no luck
tivofool said:
So you could fastboot flash the boot.img and see if that enables your phone to boot.
Then once booted, move the ROM.zip to your phone and reinstall ROM in recovery. (as per instructions) Or sideload the rom in TWRP so that you can reinstall the rom.
Click to expand...
Click to collapse
After flashing the boot.img It gets stuck at white htc screen, but it did go through android is upgrading. After a few seconds it goes dark but the htc is still visible then it says very faintly process system inst responding and then do you want to close it. Then it reboots again.I cant get the phone to boot. Ive tried side loading and pushing the rom and the aroma install works fine, but it wont boot. Is there anyway I can completey go back to stock. I have nandroids, but they don't work and neither do RUU's
Logcat
http://pastebin.com/fRHezgpE heres a logcat if that helps
xiheartjtag said:
After flashing the boot.img It gets stuck at white htc screen, but it did go through android is upgrading. After a few seconds it goes dark but the htc is still visible then it says very faintly process system inst responding and then do you want to close it. Then it reboots again.I cant get the phone to boot. Ive tried side loading and pushing the rom and the aroma install works fine, but it wont boot. Is there anyway I can completey go back to stock. I have nandroids, but they don't work and neither do RUU's
Click to expand...
Click to collapse
yes, I posted a couple ways
http://forum.xda-developers.com/showthread.php?t=2480278
I've done the second way, but you may notice luxandroid installed old firmware before running the RUU.
Thanks but
tivofool said:
yes, I posted a couple ways
http://forum.xda-developers.com/showthread.php?t=2480278
I've done the second way, but you may notice luxandroid installed old firmware before running the RUU.
Click to expand...
Click to collapse
I followed this guide and the phone booted again turned out the Rcdata was messed up somehow.
http://forum.xda-developers.com/showpost.php?p=46308487
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
MAsterokki said:
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
Click to expand...
Click to collapse
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
heavy_metal_man said:
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
Click to expand...
Click to collapse
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
MAsterokki said:
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
Click to expand...
Click to collapse
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
MAsterokki said:
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
Click to expand...
Click to collapse
Its cool pal it is, but then again ruus won't flash unless your bootloader is relocked
Sent from my Nexus 7 using Tapatalk