Database Info

Bricked cdma htc hero after ruu 1.56 Semi Solution

Ok, just like all of you I have rooted, experimented to the limits and pushed them well little did i Know is that you cant reflash the 1.56 ruu so needless to say I ended up with a brick but luckily for us it will still connect in fastboot
so this is a solution to at least get it up and running
Pros-
Reactivate your phone since it will be formated
All functions will work
can still root, install .apk's use wifi etc
camera etc
so the pros are it will operate just like nothing ever happened now to the con's
YOU WILL HAVE TO DO THIS EVERYTIME YOU TURN OFF YOUR DEVICE
Ok here is how to fix it
Connect your phone to your PC
open command and navigate to your android tools folder
type in
fastboot devices
make sure it detects your device
should show the HTC logo on your phone
now simply type
fastboot oem boot
wait a couple minutes while your phone reboots
viola you phone is back to running again...just dont turn it off LOL

can you launch the RUU again and (hopfully) have it restore your phone correctly?

You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet

rayborn said:
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
Click to expand...
Click to collapse
hmmmm interesting man. honestly you should be able to rebuild all the / partitions. such as /misc and /radio. we need some linux junkies in this thread to tell us how to rebuild failed / partitions

This is amazing. Sure did work for me. I just wish there was a way to get it flash the original radio. I have only had this thing two weeks and would love to take it back and exchange it, but I am just paranoid since it shows radio 2.41.04.02.03.

wait, what exactly did you do to get your near-bricked phone?
you used the 1.56 RUU on your phone that had a 2.xxxxxx radio?

have you tried both of the RUU's? the original and 1.56?

My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution

did you try the 1.29 RUU?

yeah i tried every sprint hero ruu i promise you i left no stone unturned trying to fix this

BRILLIANT!
I can't tell you how impressed I am that somebody has found what i now consider to be the first step towards getting the RUU 110 error solved.
I still feel that the issue comes down to the lack of ADB that seems to happen once you get 110... maybe a driver issue on the phone vs. driver issue on the computer? after all the RUU starts failing on all the ADB commands when you check out the RUU logs...
sorry i can't help take it from there, i returned my phone to sprint inside of the 30-day window and just told them something i installed form the market "bricked" my phone...
I eagerly await your results though for a final step towards solution, as I am dreading the day i have to RUU my phone for whatever reason that may be, although I've been running a personally customized Pancake ROM for almost a week and totally happy with it so won't be doing anything until 2.1 is official...
R

rayborn said:
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
Click to expand...
Click to collapse
Same exact thing for myself. Multiple people said the way to go back to the stock radio was to use the RUU. I tried both RUU's and same results. Now I am just trying to decide what is better.
Live with this and hope for a better option to come or take back a "bricked" hero that shows Radio 2.41.04.02.03 and hope I don't end up getting charged later.

IMHO I think the best thing for you guys to do is wait for our 2.1 update, which will more than likely have a smiliar radio update. Then you can just say the update bricked the phone.
If we get the same radio version, then just take it back, if we get a different version then maybe we can find a file to edit the number to make it say what ever version you want it to say, something like editing Build.prop. Then Sprint has nothing to ask questions about. Should be out in a few weeks if the rumors are right. Maybe you can deal with this soultion until then.
As far as the don't turn your phone off issue, mines been up for 13 days. I hate turning it off, partially because of the missed emails and partially because I worry that it won't come back up.

Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?

SamXp said:
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
Click to expand...
Click to collapse
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?

mginther said:
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
Click to expand...
Click to collapse
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen

tatonka_hero said:
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
Click to expand...
Click to collapse
True, and if we elect to continue to use either a Fresh or Damageless version of an official 2.1 Sprint ROM, then we should be ok. But if we wanted to go to the Sprint ROM, there are going to be a lot of bricked phones if there isn't a way to understand what is going on when a 1.56 RUU is used over a phone with the 2.x Radio update.

Just wanted to pass along some more information in case anyone else is having this problem. I had reactivated an old phone temporarily since this one was bricked. This morning I reactivated my hero due to this semi fix and immediately I could call and textimg was fine, but i kept getting vision error 67 for data. Sprint reset my data about three times and it never worked. I tried updating my profile multiple times and it never worked. Finally I Ran the RUU again and sure enough after a reboot or an "oem boot" I had error 67again. I went ahead and updated my profile and this time it worked and data started working. Still hoping someing else comes along though.

well I think the issue here might be that it does not have the recovery backup on it after you do an RUU. I could be wrong but who knows? I would say install flashrec-1.1.3-20091107-2.apk on your phone once you are able to get it up and running then flash the recovery backup and restart. That could possibly fix the issue? I have the files if anyone needs them, I'm not sure how to upload them on here...
~Danny

I'm not sure if it's possible boot into recovery console using this method, but if you can, has anyone tried manually flashing the old radio in the same manner they flashed the new one to revert back and then RUU. Perhaps that may do the trick.
My phone isn't bricked so I can't try it out, but seems like it might be worth a shot in theory.

[Q] Quasi-Bricked?

Hello! I'm a long-time lurk and this is my first post. Why? Because you folks at XDA are extremely knowledgeable and very helpful! I actually enjoy reading the forums and usually can find my answer using search. Call me a masochist, I guess. I just wish I had the chops to develop and not just be a continuous noobish sponge. I have successfully rooted my own Inspire with Bubby’s method and have flashed several radios and ROMs, no problem (knock on wood).
Anywho, I have searched and have seen similar issues to mine, but I have what I consider a more unique problem (which, if I’m wrong, I’m sure you fine folks will let me know). I attempted to root my brother’s Inspire over the weekend and it is currently showing a black screen with three vibrations and amber light (If I try to go to Hboot manually, I get five whole vibrations with a green light). I can, though, pull the battery for 5 minutes or so, then the phone will boot normally. Although I think it’s on the downgraded ROM, because it shows the funky AT&T splashscreen instead of HTC. What I did was attempt root with Bubby’s and got stuck at the boot screen when the phone was trying to flash the PD98IMG.zip (downgrade I believe) after making the goldcard. It would show that it was trying to read the zip, however I never would get the “volume up to upgrade” option. I tried this three times. When that failed, I tried rooting with the Ace Hack Kit and after creating the goldcard image, when the script tried to reboot the phone to install the downgrade, I got the black screen, amber light with the 3 vibrations. My problem is that I don’t have root, can’t get to recovery from the Hboot screen (shows red exclamation with triangle) and was unable to install Clockworks Mod thru ROM manager because I’m not rooted, so no SuperUser privileges.
What can I do at this point? Maybe off base, but I believe I have somehow corrupted the boot partition or the like, including screwing up Hboot. Is it possible to fix this if I am not able to reboot without pulling the battery? I have tried going thru Bubby’s and the Ace kit again, but always fail when the phone reboots.
Thanks for your help!

I am far from an expert, or even a novice, but to me it sounds like you have a corrupted download for the bubbys one click.... Have you checked the Md5 on the downloaded file?
Sent from my Inspire 4G using XDA App

I could lie and say yes, but no I didn't check md5 the first go around (although I did the 2nd time I reinstalled, after it screwed up). I did have all antivirus programs uninstalled and firewall turned off.

It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk

@OP:
Follow the files and instructions in this post to get back to stock so u can start fresh. I followed these to get back to stock only today evening, and it worked.
--------------------
TO RETURN TO STOCK:
Make sure you S-ON (if able) BEFORE you Unroot. The S-On tool needs root permissions to function.
--------------------
Turn the phone on, connect to computer, and perform step 1. Make sure USB debugging is enabled.
Step 1 (S-On):
Run Bubby323's S-On tool: S-On Tool
Step 2 (STOCK ROM in ZIP FORMAT):
Place this .zip file on the root of your SD card. Disable fast boot in settings > applications. Turn off your phone. Hold down the volume down button and the power button at the same time. The phone will reboot into hboot. It will load the ROM automatically. Follow the steps to flash the ROM.
http://www.multiupload.com/JELMZNSKDF
I did this like a couple hours back, and mine's back to stock.
Note: I consolidated the links here from various posts on this forum.

Diablo: Was posting the reply below, when I saw your message. Would you still recommend I follow your steps to unroot, return to stock and run hack again?
Update: Well, I went thru Bubby’s root process again and was able to get the phone rooted (had to pull battery and wait 4 minutes when it needed to reboot). And I have confirmed root was successful. I also used Bubby’s fix to Eng S-Off (couldn’t hurt, right?). The phone now has the latest Android Revolution with Sense and the radio has been flashed (including full wipe and EXT4 wipe). However, it STILL won’t reboot correctly. I can boot directly into Clockwork from ROM Manager, but if I try to reboot normally (hold down power button and select restart), I get the black screen, amber light and 3 vibrations. Again, pull battery and wait 4 minutes and either power button to boot normally or power and volume down to get to Hboot works fine and goes to Clockwork from Hboot fine also. I guess I can keep up with the batter pull only when I have to manually restart, but WTH? There has got to be a fix for the reboot issue. Any ideas?

fernandezhjr said:
It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.

ogarlen said:
...I also used Bubby's fix to Eng S-Off (couldn't hurt, right?)...
Click to expand...
Click to collapse
Well, actually, wrong, it could hurt. I'm not saying that's the cause of your problems, but you really should've read up a little more before clicking on stuff so nonchalantly.
Eng s-Off means the engineering bootloader. If that process were to fail while in the midst of performing it on your phone, it would most likely hard-brick it.
Not to mention it's unnecessary. It was only included in that rooting method at the time for flashing radios, I believe, and since then a safer method for doing so has come into standard usage that doesn't require eng s-Off.
It's also one method of resolving the cwr blackscreen people were having, where you're actually in cwr, but the screen is black so you can't see what your doing. Not the same black screen your seeing, I don't think, because you're able to at least get into cwr.

ogarlen said:
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.
Click to expand...
Click to collapse
The vibrations with the blinking led, I have seen a few posts with this. Sadly, I haven't seen anyone post a fix yet.
Sent from my Desire HD using Tapatalk

Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.

ogarlen said:
Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.
Click to expand...
Click to collapse
Heh. Now that you explain it, I can see the sarcasm. I'm usually good a picking up on it, but you know how these internet textual posts go....smilies are crucial...
As to your problem, there seem to be a few posts in recent days describing the led/vibrations type of symptom.
I don't know if they're interrelated or not. I don't have an answer, but I'm curious and will drop in if I manage to come across any pertinent information.

Thanks for the replies! I will continue to research and update this thread if I find a solution. I really believe that it has something to do with the startup processes or boot cache or some other $10 phrase related to what happens when the phone is attempting to startup normally. I appreciate all help.
Sent from my Inspire 4G using XDA App

Just wanted to add a quick update for anyone searching that comes across this post: The phone in question is now working flawlessly (knock on wood). Restarting, power down and battery pulls work with no problems (no vibrations or flashes). I am honestly unsure what I did to cause this error or what the resolution was and can only speculate. Since my last post, I have made a Nandroid backup and flashed a couple ROMs (namely AR with Sense, then Virtuous Unity with full wipes in between), so I assume that somewhere in there the corrupted boot files (or whatever) were corrected. All's well that ends well...

Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.

Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.

seems like you got yourself a good taste of rom flashing issues. that's a good thing. i know that you have everything working flawlessly now, BUT i would still HIGHLY recommend that you download the Super Wipe script from the Android revolution thread and use that to completely wipe and format your partitions, then do a FULL wipe through clockwork and then install whatever ROM you would like. but i cant stress enough, MAKE SURE that the Md5 sums match always. this can be the difference between a working rom and a bricked phone. also i would like to add that through my experience i usually find that the first time you root the inspire, the very first rom you install on it almost always has issues. that's how it is for me atleast. Ive rooted plenty of Inspire's and all of them have had some sort of issue on the first flash. and as always, follow the directions per rom to the T or else it might not work.
P.S. Some roms run better with matching Radio and RIL. flashing these is AWLAYS good practice to get your phone to tunr the best possible.

Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
Thats why I posted the full steps in the guide , to s-on and ruu back to stock. On a side note bubbies s-on tool does not always work.
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.

mudknot2005 said:
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.
Click to expand...
Click to collapse
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.

Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
You are correct. I should have re phrased that differently. I know that S-Off would survive the RUU procedure so I should have said "almost out of the box". The RUU is still a very handy thing to have.

Gene Poole said:
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.
Click to expand...
Click to collapse
Please, sir.
Seriously, this would be, imo, a profound contribution to this phone.

WiFi error's after flashing HTC unlock bootloader

Boy oh boy, I had a really tough few days trying to flash a custom rom. I was pretty heavy into flashing roms from the G1 days until I got my sensation on the day it was released. I then took a long break. Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON(security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock. And picture this living in a area with tmobile that is still using the edge network(2 ****ing g) OMFG I was so mad trying to even boot a new rom without wifi is a nightmare, took me literally 20 minutes to download rom manager. Anyway's this rom was the last one I tried before busting my phone into pieces.
Rom's I tried:
1. Android Revolution 3.6.1, and 4.1 (3.6.1 booted but had no wifi)
2. RCMix 3.5 v04 (bootloop)
3. LeeDroid booted fine (no wifi)
4. I believe there was one other I tried. NO GO
5. Then I flashed this one late last night, and to my surprised it worked.
I was so happy I almost pissed myself.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
Anyway I guess what I am getting at. For anyone else that might have to go through what I did.
1. How in the world can you get you phone back to complete stock?
2. Why is this happening?
3. Why is my wifi not working with any other rom? And everyone else's is?
4. How do I go about getting my S-OFF?
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
I probably have more question's. I just wanted to see if I might be able to get a few answers from you fine people. Help me understand what in the world is going on and how many other people are dealing with what I am dealing with.

droiddv said:
Boy oh boy, I had a really tough few days trying to flash a custom rom. I was pretty heavy into flashing roms from the G1 days until I got my sensation on the day it was released. I then took a long break. Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON(security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock. And picture this living in a area with tmobile that is still using the edge network(2 ****ing g) OMFG I was so mad trying to even boot a new rom without wifi is a nightmare, took me literally 20 minutes to download rom manager. Anyway's this rom was the last one I tried before busting my phone into pieces.
Rom's I tried:
1. Android Revolution 3.6.1, and 4.1 (3.6.1 booted but had no wifi)
2. RCMix 3.5 v04 (bootloop)
3. LeeDroid booted fine (no wifi)
4. I believe there was one other I tried. NO GO
5. Then I flashed this one late last night, and to my surprised it worked.
I was so happy I almost pissed myself.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
Anyway I guess what I am getting at. For anyone else that might have to go through what I did.
1. How in the world can you get you phone back to complete stock?
2. Why is this happening?
3. Why is my wifi not working with any other rom? And everyone else's is?
4. How do I go about getting my S-OFF?
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
I probably have more question's. I just wanted to see if I might be able to get a few answers from you fine people. Help me understand what in the world is going on and how many other people are dealing with what I am dealing with.
Click to expand...
Click to collapse
Personally i would just do the normal s-off method as it gives you a little more freedom compared to HTC unlocking method.
My wifi is dead too, but i have no way of fixing it at all, i've got a thread called "wifi is dead" in the q+a section of the sensation forum.
Let me know if you get yours working, i imagine that if you revert your phone back to stock again and then use the alpha rev method that you will have better luck.

1. You can Relock your bootloader using HTC site but this time u will see Relocked instead of Locked
2. No idea
3. Did you try resetting your router? Works for me. Also try flashing a different radio.
4. No idea
5. You can relock bootloader on HTC site but have no idea of you can unlock it with Revolutionary again.

Try write secureflag command, just search for.the correct one on xda. Also, try flashing your RUU and then s-offing via revo.
Sent from my HTC Sensation Z710e using XDA App

tinky1 said:
Try write secureflag command, just search for.the correct one on xda. Also, try flashing your RUU and then s-offing via revo again. You might need eng s-off, pm EddyOS, he should be able to help, I believe he's done it before.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Sent from my HTC Sensation Z710e using XDA App

[ Solved ] WiFi error , Radio flash Problem , and revert back to any Custom Rom
droiddv said:
Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON (security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
.
Click to expand...
Click to collapse
[Solved ] WiFi error , Flash Radio Problem , Install any Custom Rom without errors , Wrong S-on Brick
this is Solved and the wifi error is because of kernel included in Boot.img
you can use the following solution to install any custom rom without wifi errors
first read " how htc dev works " to have an understanding why this happened to you and why you are still S-on and why you can't flash Radio . link is here " Solve WiFi Errors , Radio Flashing Problem , Caused by htc Dev Unlock Method "
the solution itself is in the following link , Read title " Custom Rom Flash " and "[FONT=&quot][ Implementation ][/FONT][FONT=&quot] Successful S-OFF using my above method " . [/FONT]link is here " Successful S-OFF after brick (wrong S-ON) for ICS or GB , Downgrade OTA firmware "
this also solve wrong S-on Brick , hope that helps
Press the thanks Button for this Post

[Q] Need to flash my phone back prior to the recent ota (1.63... doubleshot)

I am trying to attempt messing with this type of thing for the first time so noob handling will be required. My reason is simply my phone is a nice wallpaper display three days after the ota from tmobile 1.63.531.2 710rd.
I began by trying to follow:
http://forum.xda-developers.com/showthread.php?t=1505999
To no avail. Of course I noticed afterwards that for some reason it says to turn s-on in the header... exactly the opposite what what I need to flash the phone back to (PG59IMG_Doubleshot_TMOUS_1.28.531.9_Radio_10.48.9007.00U_10.12.9007.07_M2_release_201815_signed.zip) I have had problems with the phone ever since its first ota a year or so ago. With this latest ota the phone is more or less bricked as of the phone using power saver when I went to sleep last night... Wont call or check into the network...no dial tone. Took me 3-4 restarts for it to even show the antenna symbol and the 4g icon in the taskbar.
My phone is set as S-on for now. The only instructions I have found through the search tool relay how to do it to the sensation... I believe that is the mytouch 4g not slide. However I have the slide which is doubleshot. So my question is, is this instruction on http://forum.xda-developers.com/showthread.php?t=1192300 safe to use with the doubleshot since the (T-Mobile branded HTC myTouch 4g Slide ( doubleshot ) Developers Reference) page links to it indirectly. Using the link at the top of the how to S-on after s-off... again the opposite of what I need so I tried following the link at the top of that page " Guide to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on " which takes you to the s-off instruction page for the sensation (Link: http://forum.xda-developers.com/showthread.php?t=1192300 )...I am guessing that it will work and sensation refers to HTC sense, but I don't care to make the mistake of doing it wrong and bricking my phone due to being derp.
I know there is a bit of overdone explanation and redundancy in the addresses I have left here. I am just trying to cover all my bases thanks for the help in advance.
The short and sweet is I need a link by link list with instructions on how to step my phone back for multiple reasons. First the recent OTA more or less broke my phone and I don't want a refurb phone with inferior parts from Assurion...(They were in class action lawsuits for this in the past.) nor do I want to pay 130$ for said replacement. Next from what I just read the 1.63 update has some serious security compromises that are awaiting response from HTC for an update. Basically it gives full accesses to all your data to include your sim and SD card contents to all apps. Regardless of user specified/agreed permissions.

Following ANY routine or procedure for another phone is just too dangerous & will never work anyway. The bad part being you may very well create a brick in the process. If you have the MT4G SLIDE, this is where you will get all that you need so don't even consider other threads.
Since you've done the OTA & are sitting at Hboot 1.63.XXX now you will HAVE to get S-Off before you can go back to your previous Hboot. To DO that you will have to follow the instructions HERE.
If all you are wanting to do is start flashing ROMs, then the instructions you need are HERE.
Keep us informed & we'll try to help if you need it. Good Luck!

WeekendsR2Short said:
Following ANY routine or procedure for another phone is just too dangerous & will never work anyway. The bad part being you may very well create a brick in the process. If you have the MT4G SLIDE, this is where you will get all that you need so don't even consider other threads.
Since you've done the OTA & are sitting at Hboot 1.63.XXX now you will HAVE to get S-Off before you can go back to your previous Hboot. To DO that you will have to follow the instructions HERE.
If all you are wanting to do is start flashing ROMs, then the instructions you need are HERE.
Keep us informed & we'll try to help if you need it. Good Luck!
Click to expand...
Click to collapse
Thanks for the hasty post reply any other suggestions...I have win7ult 64bit. Or will will juopunutbutter work even though they have the below disclaimer?
"Supported Operating Systems:
We only support Windows 7 32bit or Ubuntu 12.04 (and newer) 32bit, you may use a LiveCD if you have the wrong OS installed natively. Win XP 32bit might work for you but we do not support it as we did not test on it."
Also, this, "Be on the Stock RUU and be rooted (have superuser flashed). No other ROMs are supported, Fresh ROM will not work regardless of what you have read elsewhere."
-I am not rooted. Which is something else I want to accomplish so I can set up firewalls that block certain things.
Oh btw provided I can get this phone working again I am also going to attempt to reflash my older mytouch 3g... back to original as well that thing worked better than any of the current phones for my purposes before it got the update prior to the 2.2.1... the original update didn't work with adobe which is fine with me, people need to move on from adobe's garbage anyway. Specifically with the old mytough 3g though that really did add functionality at the sacrifice of sanity since it slowed the phone down so much. On that note though I may just put on a custom if I can get comfortable with this stuff. The last time I looked at a pc this hard was back in win98se when you had to know how to do tricks to make it faster like modifying available rame to twice as much above and below physical ram and a few other tweeks I have long forgotten.
That brings me to another question. If I go custom rom and unlocked this looming threat of brick is weighing in on me. If a phone is bricked is it possible to recover using some of the same tools that bricked it in the first place... flash install original rom as a fix? Just trying to see how much margin of error I have to work with.
Thanks again.
PS who do we talk to about backing off all the java on the site since it is so compromised right now? This sight has more java permissions than most sights of ill reput... though I have been reading these forums off and on for a while so I trust it more than most with this much tracking. I doubt patch 11 actually fixed the issue...since the day before they said it would take two years or more to actually resolve the java zero day exploit.

You should be fine with your pc, I used a 64bit win7 too. If you're worried dual boot linux.
Your my touch 3g is rooted diferentley, go to that forum for details, its not true radio soff but its close enough.
If you brick it its dead, depending how it was bricked jtag could bring it back to life or this phone is part of the unbricking project which will fix some other bricks. Problem is people use brick as a term that means a whole lot of things so its hard to answer. Usually a brick is forever dead, most people don't actually brick their phone though and usually have to be neglecting things to do it.
As for java... just read up on a bunch of trustworthy places for more info and understanding
Sent from my HTC Vision using xda premium

I'm afraid I just don't know about Win 7 64bit and how it will react but I'm sure there has to be a person or two around with experience concerning that OS. It may very well work fine. I CAN tell you that the "wire trick" (junoptobear?) will work fine on MikTouch because that's what I used. It's a stripped down GB stock ROM which is all you're really looking for. Why....I don't know.
As far as bricking goes, there's not a GREAT deal to worry about as long as you follow all instructions to a tee. You REALLY don't have to even have S-Off to flash ROMs as you read in that link. You just need to flash the kernel after you flash the ROM. It WILL limit a few things you can do but not ROM flashing.
When it comes to rescueing a bricked device though, there are only a very few instances that can be done as far as I know. But I'm no developer either. But if you can make it to your bootloader and/or recovery you not bricked. It may be a hardware of software issue but most of the time you can come back from those.
As far as the Java issue you spoke of goes, you may be able to get an answer to that one by PM'ing one of our moderators or admins.

I want to step it back to previous versions because they worked better...primarily the first version... Also, I am not seeing a guide that refers to doing it to the 1.63 patch. keyboard hasn't swyped right since the first ota update. Also my intent is to root an older version so I can remove crapware like dt sync, friend stream, kidzone, tmobile mall, tmobile tv, tmobile setup, telenav gps, and zinio reader.

X-Lander said:
I want to step it back to previous versions because they worked better...primarily the first version... Also, I am not seeing a guide that refers to doing it to the 1.63 patch. keyboard hasn't swyped right since the first ota update. Also my intent is to root an older version so I can remove crapware like dt sync, friend stream, kidzone, tmobile mall, tmobile tv, tmobile setup, telenav gps, and zinio reader.
Click to expand...
Click to collapse
It's a simple flashing process but you HAVE to achieve S-Off first with the "Wire Trick". You can flash it forward without S-Off but not backwards. Does it work at all or is it just frozen to some point in the boot process? Can you access your SDcard? Can you boot to Hboot & recovery? These are a couple of things you will have to be able to do to go forward if I understand you correctly.

[Q] [Help] getting my Inspire 4G back to stock

I had a ATT inspire 4G running on android 2.2
I rooted and installed CWS with easy ace root. worked perfectly
then following another guide I found, I tried to flash update-aospX-1.0.0-AR26-DesireHD-signed using recovery.
But my phone was stuck on the white HTC screen and didn't go anywhere. Trying to solve this issue I wiped everything with recovery and flashed this: GizRoot_v_2 (1) which I found on this forum as a rom made similar to the stock rom. this worked and now phone was good but the guide did say to change the radio.
I tried to update my radio via hboot with sd card, but it always got stuck on the installing part and never finished. After researching it the problem was that I am still S-ON and you cant change radios while S-on?
I have spent 4+ hours googling and researching I have about 12 tabs open with different guides. I am very frustrated at this point
I Have a inspire 4g phone that works but the radio doesn't work. 1st it would connect to the movil network of the carrier but the wifi did work. I changed the simcard to another provider and it did work calls were made and internet data worked. but now wifi doesn't work!
I would like to have the phone back to factory setting and stock att rom. how can I do this, I used a RUU exe, but it always said error connecting to the phone. the RUU is RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed
or maybe I am doing it wrong?
help please
edit: I booted phone to fastrecovery usb and ran the RUU.exe again, this time it went all the way to wiping and sending then it said an unknown error occurred right after updating signature and sent me to error recovery step 0, followed prompts but nothing worked

Flash boot.img from fastboot. Read the Ace Think Tank in Desire HD General for details.

steps
Ok
So.
I booted into recovery, wiped data and factory reset, wiped cache partition, wiped dalvik cache
installed from sd card update-aospX-1.0.0-AR30-DesireHD-signed. rebooted device into fastboot, connected usb cable.
downloaded android-win-tools and extracted into one folder. I also extracted the boot.img from update-aospX-1.0.0-AR30-DesireHD-signed into the same folder.
I opened a cmd window, went to said directory. typed fastboot.exe then fastboot devices. my device is there, then I did fastboot flash boot boot.img sending boot, writing boot ok.. did fastboot reboot...
and HOLY **** IT WORKS...
I still have to test wifi gps calls etc
EDIT: WIFI WORKS, GPS WORKS BLUETOOTH TOOK A WHILE TO TURN ON BUT WORKS, and calls work! camera works yey!

MIUI on Inspire 4G
Hi,
I need something like that too.
I bought my phone from USA in 2011, Android 2,2, i think, and with MIUI on it, locked on AT&T and I use it in Europe.
I unlocked it here in Europe and everything was fine.
So, the phone started work slow and after 2 years of use it I didn't receive any system update. My husband bought one same model, no MIUI on it, but HTC Sense I think, AT&T locked, unlocked here, but he received the system update and worked fine.
Now, in my silly thinking, I started to look for update on Internet and I saw that the Android is already 4.2. and I have 2.2. And I said,man, that's why is not working so well.
So, I upgraded my phone to Android 4.2.2 JDQ39E - the most stupid thing I could do. Starting that day, my phone is freezing non-stop, it restarted itself while I am talking on the phone. The apps are not working well, are freezing often. I read on AT&T website that for my model, the last Android is not 4.2.2 at all, but it was too late.
I found out how to upgrade the MIUI and I did it. This is ok, but this MIUI it makes me cray. I don't like it at all.
I WANT TO GET RID OF MIUI AND PUT SOMETHING ELSE INSTEAD OF IT. And put the normal Android system that my phone support it well.
HOW I CAN DO THAT?
Please help me with some advices before I will creat a new model: HTC Inspire 4G smashed.
Thank you so much.

Melabella said:
Hi,
I need something like that too.
I bought my phone from USA in 2011, Android 2,2, i think, and with MIUI on it, locked on AT&T and I use it in Europe.
I unlocked it here in Europe and everything was fine.
So, the phone started work slow and after 2 years of use it I didn't receive any system update. My husband bought one same model, no MIUI on it, but HTC Sense I think, AT&T locked, unlocked here, but he received the system update and worked fine.
Now, in my silly thinking, I started to look for update on Internet and I saw that the Android is already 4.2. and I have 2.2. And I said,man, that's why is not working so well.
So, I upgraded my phone to Android 4.2.2 JDQ39E - the most stupid thing I could do. Starting that day, my phone is freezing non-stop, it restarted itself while I am talking on the phone. The apps are not working well, are freezing often. I read on AT&T website that for my model, the last Android is not 4.2.2 at all, but it was too late.
I found out how to upgrade the MIUI and I did it. This is ok, but this MIUI it makes me cray. I don't like it at all.
I WANT TO GET RID OF MIUI AND PUT SOMETHING ELSE INSTEAD OF IT. And put the normal Android system that my phone support it well.
HOW I CAN DO THAT?
Please help me with some advices before I will creat a new model: HTC Inspire 4G smashed.
Thank you so much.
Click to expand...
Click to collapse
Uh mate, It's best to go back to Stock Roms for that. And Everytime you guys go upgrading and degrading Roms, It's best to make a backup image with Nandroid.
Easiest way to go back to stock is find the proper RUU's for your phone.
http://forum.xda-developers.com/showthread.php?t=1385016
Pick one of these, Download the RUU, Plug in your phone and Let the App do it's magic.
And take note, It's going back to the STOCK.
After that, Use the AAHK tool or search around the forums to unlock and S-Off.
Good luck.

Thank you!
ZhakamiZhako said:
Uh mate, It's best to go back to Stock Roms for that. And Everytime you guys go upgrading and degrading Roms, It's best to make a backup image with Nandroid.
Easiest way to go back to stock is find the proper RUU's for your phone.
http://forum.xda-developers.com/showthread.php?t=1385016
Pick one of these, Download the RUU, Plug in your phone and Let the App do it's magic.
And take note, It's going back to the STOCK.
After that, Use the AAHK tool or search around the forums to unlock and S-Off.
Good luck.
Click to expand...
Click to collapse
Thank you so much. Before I will do what you said, I will read all the threads about AAHK and how to unlock. I need to be informed before to do it. It is a little hard for me to do all these steps, but I will try. If I will succeed, than I will reconvert my job :laugh:

Yeyyyy
ZhakamiZhako said:
Uh mate, It's best to go back to Stock Roms for that. And Everytime you guys go upgrading and degrading Roms, It's best to make a backup image with Nandroid.
Easiest way to go back to stock is find the proper RUU's for your phone.
http://forum.xda-developers.com/showthread.php?t=1385016
Pick one of these, Download the RUU, Plug in your phone and Let the App do it's magic.
And take note, It's going back to the STOCK.
After that, Use the AAHK tool or search around the forums to unlock and S-Off.
Good luck.
Click to expand...
Click to collapse
I did it, I did it. And it's working. THANK YOU SO SO SO MUCH!
Have a great weekend!

Melabella said:
I did it, I did it. And it's working. THANK YOU SO SO SO MUCH!
Have a great weekend!
Click to expand...
Click to collapse
No worries mate. Have a good weekend to you too.