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] Rooting Inspire 4G with HTC update.

I wanted try the update and same time get my eng-S back on. I followed the return to stock method to get my phone back to the factory state with s-on and successfully got the update. My question is, now will any versions of the ace-hack-kit work on my updated phone to root, s-off and sim-unlock again if I so wished? I only ask because I am not very happy with the battery usage on the stock rom. I did wanted to get rid of the eng-s off because of all the warnings but I didn't think about going back to my rooted and unlocked state when I updated (that was sort of foolish of me).

You're basically back where you started. To re-root, you'll need to downgrade the ROM so you'll lose anything you got from the update anyway.

attn1 has already posted a rooted version of the new update here (http://forum.xda-developers.com/showthread.php?t=1058042) so flashing this ROM will give you everything from the update with root
Or root it yourself using Gingerbreak (http://forum.xda-developers.com/showthread.php?t=1057104)
I have not tried either of these, but both threads are reporting good things. A little search goes a long way

I need to go back to stock actually, and from all the "stock" roms I've seen they are all cingular based. When I got the phone it said nothing about Cingular splash screens or whatever. it was all ATT screens and I cannot for the life of me find that specific stock rom for my Inspire.

Sudogaron said:
I need to go back to stock actually, and from all the "stock" roms I've seen they are all cingular based. When I got the phone it said nothing about Cingular splash screens or whatever. it was all ATT screens and I cannot for the life of me find that specific stock rom for my Inspire.
Click to expand...
Click to collapse
Follow the steps in my sig, second post.

id10terrordfw said:
Follow the steps in my sig, second post.
Click to expand...
Click to collapse
I'm doing that right now actually. I found it after posting that last message.

[Q] HBOOT update PU fail - recovery wont work from 'outside'

I have been flashing for a while, and although not a pro by any means, I'm not a noobie either. I've looked for similar issues from others and have yet to find one that addresses this point specifically: I downloaded and attempted to utilize the PG58IMG.ZIP and repeatedly get the PU Fail. I saw another post relating to the issue being when you either accidentally or purposely try to flash it MORE THAN ONCE. I believe this is the mistake I made ( I was dumb enough to flash while riding in a car ). The issue is this: If I try to enter recovery from the 'outside' ; i.e. a completely turned off phone, with vol and on/off, I cannot use recovery. It will repeatedly make me go through the process of trying and failing to install this over and over. So, am I screwed? To tell the truth, I have no other issues with the phone, running ARHD 3.6.9, 4.1.9, or 5.0.2 as well as RCmix 3.5 v10 or ICS. BUt, if something happens to keep me from accessing recovery from within 4EXT, I will have a real problem. Now, I've seen the new RUU posting for ICS and would like to try it. Will this fix my problem? Is updating my HBOOT the answer? Is there any other way that I'm not thinking of? I don't often start threads with questions becuase I'm willing to find the answer through searching, but haven't found any direct answers to this particular part of the problem. Any help would be appreciated...
HTC Sensation 4G
HBOOT 1.17.1111
Radio 10.14.9035.01
Baseband 10.56.9035.000
Currently running:
RCMix 3.5 V010
2.3.5 w/ sense 3.5
Bricked XE 2.6.35.14
o/c to 1.78

So if you flash a lot of RUU ,you must have supercid?
Sent from my HTC Sensation 4G using XDA Premium App

Silly question perhaps but have you deleted PG58IMG from your SD card and tried then?

wmoore said:
Silly question perhaps but have you deleted PG58IMG from your SD card and tried then?
Click to expand...
Click to collapse
No, as a matter of fact, I re-downloaded it to be sure the one I had wasn't corrupted somehow. Still, no luck.

epsix said:
So if you flash a lot of RUU ,you must have supercid?
Sent from my HTC Sensation 4G using XDA Premium App
Click to expand...
Click to collapse
I don't believe I do. Tried accomplishing that this morning, but permission denied. I flash many ROMs and add-ons, but have only flashed the original RUU to S-off and root.

Just to update, I activated the superCID from my laptop, no problems. Went with the new ICS RUU, and so far everything is sweet! Going to re-flash my ARHD 5.0.2 and then see what I have.

Well, ICS RUU, re-rooted, clockworkmod re-installed, busybox, and 4EXT. Flashed my ARHD 5.0.2 restore, and now I'm running HBOOT 1.20, Android 4.0.1, and it's all very smooth. Impressed! Apparently, if you get an update fail on your HBOOT, you can solve it by going to the next level, so to speak. Anyone out there have any viable suggestions on how to 'recover' their recovery without having to resort to this, I'm sure it would be good information to have. Otherwise, case closed!
Phone: HTC Sensation
ROM: Revolution HD 5.0.2 ICS
Kernel: Stock
Radio: 11.59.3504.00U_11.16.3504.16_M

BMP7777 said:
Well, ICS RUU, re-rooted, clockworkmod re-installed, busybox, and 4EXT. Flashed my ARHD 5.0.2 restore, and now I'm running HBOOT 1.20, Android 4.0.1, and it's all very smooth. Impressed! Apparently, if you get an update fail on your HBOOT, you can solve it by going to the next level, so to speak. Anyone out there have any viable suggestions on how to 'recover' their recovery without having to resort to this, I'm sure it would be good information to have. Otherwise, case closed!
Phone: HTC Sensation
ROM: Revolution HD 5.0.2 ICS
Kernel: Stock
Radio: 11.59.3504.00U_11.16.3504.16_M
Click to expand...
Click to collapse
Delete PG58 file or pull sd card out

tinky1 said:
Delete PG58 file or pull sd card out
Click to expand...
Click to collapse
Tried both with no success. Even thought about downgrading to utilize an older HBOOT like some recommended. Decided if I had to go 'up' or 'down', I'd rather go up. Glad it worked out well. I saw some had a serious problem with other recent releases. Mike1986 is at the top of his game, so I'm grateful! Long Live ARHD! Just to be fair, RCMix does great work as well, its just an apples and oranges thing I guess. (No disrespect to any other developers, these are the only ones I've used )

UPDATE: The ROM itself is good and obviously has great potential, but I am having quite a few issues. It was suggested that System Tuner Pro would force open CPU 2 and give a boost, but it would not view my system as rooted,even after re-boots and permission fixes. 4EXT would freeze and FC in any operation, as would SD Speed Increase, Set CPU, and even Superuser. Font Installer didn't freeze the way some complained it did, but for me it would go through the required re-boot and have no change. Tried to backup with Clockworkmod (since 4EXT was failing), and the backup failed. SOooooo, in my opinion, it is good at this point for a daily user if you do JUST THAT, use it for common daily functions. But, for me at least, anything having to do with increasing performance or customization creates a problem. Not the end of the world, except that I'm a customization junkie, so its a bit of a deal breaker for me. One thing, a lot of people complained of wallpaper issues and failures; the DIY ownskin I was using had no issues. Then again, the wallpaper for the lockscreen DID fail. Oh well.... I know it'll get better. Restoring back for a while ....Mike 1986, RCMix, and all other hard working devs, keep up the good work, Getting better every day...

The last post was by no means any kind of a critique, I dabble but have no experience at this point as to what it takes to create these works, so I hope no one takes it as such. Just thought I would share my various experiences so others can gauge their own. I think that those who take the time to work these out are very talented and deserve praise regardless of glitches that happen without warning.
HTC Sensation 4G
HBOOT 1.20.1111
Radio 11.59.3504.00U_11.16.3504.16_M
Currently running:
RCMix 3.5 V010
2.3.5 w/ sense 3.5
Bricked XE 2.6.35.14
o/c to 1.78

BMP7777 said:
The last post was by no means any kind of a critique, I dabble but have no experience at this point as to what it takes to create these works, so I hope no one takes it as such. Just thought I would share my various experiences so others can gauge their own. I think that those who take the time to work these out are very talented and deserve praise regardless of glitches that happen without warning.
Click to expand...
Click to collapse
All fair comments. The devs do a great job on here but the sharing of experience and information by non-devs like you and me is also important

I have the same problem with Fail-PU

[Q] Touchscreen failing to respond to touches

I've had this problem for a while where while I'm using the phone, the touchscreen and softkeys fail. For now I've just been putting it into wakelock and unlocking it again, however its getting to a point where I can't use the phone anymore.
ROMs it's happened on: CM7.1, CM7.2 and MIUI ICS 2.4.27 (proxuser port)
Kernel: The standard one, I haven't changed that
Something that could cause the issue is the Korean IME from Google (I have that installed as its the best Korean Keyboard out there for the time being)
Pretty sure this is a hardware problem, if so I'll flash it back to stock and S-ON it and get vodafone to replace the phone for me (or try to as the case may be)
If anyone could give advice or a fix that'd be really handy.
Thanks for any help/advice given in advance.

GideonB234 said:
I've had this problem for a while where while I'm using the phone, the touchscreen and softkeys fail. For now I've just been putting it into wakelock and unlocking it again, however its getting to a point where I can't use the phone anymore.
ROMs it's happened on: CM7.1, CM7.2 and MIUI ICS 2.4.27 (proxuser port)
Kernel: The standard one, I haven't changed that
Something that could cause the issue is the Korean IME from Google (I have that installed as its the best Korean Keyboard out there for the time being)
Pretty sure this is a hardware problem, if so I'll flash it back to stock and S-ON it and get vodafone to replace the phone for me (or try to as the case may be)
If anyone could give advice or a fix that'd be really handy.
Thanks for any help/advice given in advance.
Click to expand...
Click to collapse
No fix. Have had exactly the same kind ot issue on a friend's Desire S,which needed replacement. Don't hesitate about restoring S-On and sending it back to HTC. That's the best course of action to take if you're under warranty...
Sent from a Desire S still looking for a good replacement.

Ah, I got my phone basically a year ago next week so I'm not sure if that means its not in warranty anymore.
Its working better now if I don't type really fast, but it is definitely a hardware problem then?
Sent from my Transformer TF101 using XDA Premium HD app

how to back to s-on?
How to get back to s-on? i have the same problem and still have guarantee.
I installed RUU rom but i still s-off.
H-boot version: 6.86.1002

aarnoldaas said:
How to get back to s-on? i have the same problem and still have guarantee.
I installed RUU rom but i still s-off.
H-boot version: 6.86.1002
Click to expand...
Click to collapse
Read the INDEX. Link in my signature. It has all necessary thread links for you to get back to S-On. Read about it and see if you get a hang of it. Then ask questions in the respective threads. Much easier that way than repeating everything all over again. 90% of your questions will be answered while reading the comments, and also some that you haven't thought of yet.
Cheers.

I think I'll hold out until I can get my hands on a Galaxy S or something similar (and then put MIUI on that and sell this phone or something)
Thanks for the help anyways
I'll tag this as solved (if I can)

Help! Learning but still in the dark

I have my Sensation $g from T-MOB for 2 years now and it time to upgrade or something. I have tried several different ROMs from different developers and was ok but now I'm questioning my performance. Signal "seems" to be getting worse but since I didn't log can't be sure. I remember it being better before the last 2 ROM changes but the company has changed windows and put a new roof on the building. But my watering holes also seem to be giving me difficulty getting a signal. So I tried to return to stock thinking it may be the radio included in these roms but it seems almost impossible or at least very dangerous to try compared to going forward. I am running an elegancia rom now and going to try another ARHD only b/c I have the 3.33.401.601 firmware. I just learned this is world wide english where as the T-MOB US is only at 3.32.531.x so I cant go back to that. Does anyone think this new ROM will help my signal/connectivity issue?

are you on S-ON or S-OFF?

I'm still S-OFF after installing ARHD 3.33.401.53. but I think I'm no longer rooted.

dssturk said:
I'm still S-OFF after installing ARHD 3.33.401.53. but I think I'm no longer rooted.
Click to expand...
Click to collapse
every custom rom comes pre-rooted so probably you are
use getril app from playstore
it will show you the best combination of radio/ril
otherwise take a look at this thread
http://forum.xda-developers.com/showthread.php?t=1202867

Actually the ROM I'm installed was a semi stock rom,
https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNEi6ycHiWUAVLkQ-RW0ZoIVvJyiNA
It did remove Root and SuperCid so I returned to previous Rom and looked for another and found what I was looking for "maybe". I'm testing rom's befor I make a desission on whether or not to renew my TMOBUS account or switch.
Thanks so much for the feed back.