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.
Related
WHAT THIS IS FOR:
This is for those of you that upgraded to the newest rogers rom, and caught yourselves with an unrooted device.
IMPORTANT NOTE: Emergency phone calls are broken in this version (the whole reason for the upgrade), so see to it that you switch to a rom / boot.img that doesn't suck. (thanks a lot rogers >_>)
http://haykuro.polygonize.com/ROGERSDREAM.nbh.zip
Steps to take:
1. Download the file
2. Extract and rename to DREAIMG.nbh
3. Place on root of SD card (your SD card has to be formatted as FAT32 if it fails to find it in the next step!)
4. Power off, hold camera button, power on. This will boot into SPL and prompt you to install. Proceed.
5. After your phone is done flashing, it will prompt you to press another key to reboot the phone. Do so.
6. Use flashrec, and follow procedures to root again.
Haykuro strikes again! I didnt put the update on but im sure this will be put to good use.
wow dat was quick, so downgrade and follow the rooting process again is it ?
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Sejanus said:
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Click to expand...
Click to collapse
if u havent update to the new rogers rom and having CM 4.2.13 then forget abt this,
if u flash rogers rom u will lose your root as i did
so better not to if u like the root, cos there is nothing special with the rogers update,
but the Magic update is awesome
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
I get the same thing! arrgghgh
Haykuro: can we use goldcard for this???
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
Get the same thing. Thanks for the effort Haykuro. Anything else up your sleeves?
ok update failed
dammm... was hoping for a fix!
Dropped the nbh file in my goldcard....nada....failed the same way.
I even ran the 1.89 RUU and replaced the rom.nbh file in the temp folder with the old one we all downloaded and named it rom.nbh.... just to see what would happen....failed
I'll have to try another goldcard....I might have messed up somewhere.
Can someone please try this with a goldcard and see if it works?
Thanks haykuro for getting on the ball on this....
Rogers.....karma is gonna be a B*&%$......for you guys one day....
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
weird, I have lost all the signal ever since trying to flash the nbh file
copolii said:
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
Click to expand...
Click to collapse
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
alan090 said:
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
Click to expand...
Click to collapse
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
copolii said:
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
Click to expand...
Click to collapse
... and that is even though HTC would be perfectly happy to make a 1.6 for them.
I assume that the 1-click-root vulnerability is gone, anybody try it?
Annoyances
So, I called Rogers tech support on Monday morning after they turned off my 3G and told the tech guy there that I've been running a ROM with the 911 fix since last September or so, and could they please turn my 3G back on. He did something on his end to re-provision my phone. I had to take out the battery for a little while and then boot my phone, and 3G came back up for me.
This wasn't good enough for Rogers. They have been sending me two text messages a day (one English and one French) and then calling me (twice) with recorded messages warning me about the 911 problem and that I need to 'upgrade'. This is a serious customer satisfaction issue with me. So, I figured it'd set me back for a few days, but I did the following to downgrade my phone from Cyanogen to the Rogers Donut-Hole release:
1) Installed Windows XP mode on my Windows 7 64 Bit OS, because the HTC Sync program wouldn't work on Windows 7 64-bit.
2) Downloaded and installed the HTC Sync program on my Windows XP virtual machine.
3) Dug around and found an old JACxHERO 1.0 ROM and I flashed it, hoping that the Rogers updater wouldn't detect this as a violation and abort.
4) Rebooted the phone, and joy of joys was able to get HTC Sync to connect to my virtual machine. The JACx HERO ROM has HTC Sync inside it, which was enough to fool the installer.
5) Ran the Rogers downgrader. This ran successfully... I just had to babysit the USB 'Attach' menu. If you're not on a virtual machine, you shouldn't need to worry about it.
6) Now I have the updated Radio image, and a downgraded 1.5 Android image.
I miss 1.6 terribly already. I wonder how long it'll be before Rogers detects that I've performed the upgrade so that I can try out this new Hakuro goodness (thanks Man!) and get my phone to a decent OS again. Anyone know how Rogers is detecting the upgraded version? Are they simply looking at the Radio image version? Or do they also know what OS Build I'm running?
I also upgraded my wife's phone. I hope the SMS and Recorded message abuse will now go away.
My message to Rogers would be: Get out of my life. I already pay you far too many dollars for the privilege of holding and using an HTC Dream on your golden network. It is super nice that you regard my safety above all else, however I have never in my life called 911, and really my safety is not your responsibility. I already know about the 911 bug, and had it fixed before you decided to meddle with all of your Canadian customers by removing their network connectivity and abusing them with myriads of reminders. Get out and stay out of my life!
Have a nice day.
I've tried all the usual methods with fastboot. Flashrec doesn't work. Logging in via adb doesn't give me shell access. Someone's tried the goldcard method.
Sigh.
Haykuro, what was your process for initially rooting the Magic? Didn't we send you one and you had to hook up some wires to it to get some port #s or something? (Sorry, it was long time ago.)
If need be, I'm getting an Magic upgrade once they are in stock and I'd be willing to lend you my Dream to hack at.
Sorry to here that you did that but as of now you are fooked.
There were steps in 1 of the 5 threads that told you how to perform the upgrade without flashing the "perfected perfect" spl but it's too late now.
sorry for your luck.
Same issue as everyone else, unable to flash old image...
My phone has been unusable since the update, reception has dropped to emergency calls only in my house, and 1 bar outside.
Every hour or so I have to reboot the phone, I get some ".process" error that keeps popping up in an infinite loop.
I need the droid from telus to be released, I have to ditch this garbage.
I flashed the 2.1 RUU that was floating around a couple weeks ago. Well now, I can not get any PC to recognize my Hero. I cant mount or use ADB and I'm stuck with this BS 2.1 RUU..Can anyone help PLEASE!!
I thought all the threads that had the 2.1 RUU said that we couldn't get root on it yet, and that it was really posted for devs only.
Your best bet right now is to find some way to conveniently "break" your phone and get a replacement.
http://forum.xda-developers.com/showthread.php?t=668905
I could be wrong, but I think that was for development only not ready for a phone.
HeroHTC said:
I could be wrong, but I think that was for development only not ready for a phone.
Click to expand...
Click to collapse
No, your right - some people have had a hard time reading all of the threds about what that does to you phone. Research pays dividens in the long run.
Key thing to remember: Don't flash a rom unless it has a funny name.
gbhil tweeted this a few weeks back as a way to restore after using the leaked 2.1 RUU... I think it'll help you out:
http://forum.androidcentral.com/htc...pair-your-bootloader-after-using-2-1-ruu.html
Key advice (as mentioned above): ALWAYS read the warnings before flashing something.
i would never RUU my hero after all of the issues that have been reported. best bet is to make a backup of your stock hero rom before flashing any custom one.
Kcarpenter said:
No, your right - some people have had a hard time reading all of the threds about what that does to you phone. Research pays dividens in the long run.
Key thing to remember: Don't flash a rom unless it has a funny name.
Click to expand...
Click to collapse
And don't use an RUU with the word "test" in it.
tf2d said:
I flashed the 2.1 RUU that was floating around a couple weeks ago. Well now, I can not get any PC to recognize my Hero. I cant mount or use ADB and I'm stuck with this BS 2.1 RUU..Can anyone help PLEASE!!
Click to expand...
Click to collapse
I too ran the RUU running around but was able to root my phone using the info in the links that "Is_907" and "Kcarpenter" provided. Now I'm running DamageControl v2.07.2 ROM on my Sprint HTC Hero.
Hope it helps you as much as it helped me.
Is_907 said:
gbhil tweeted this a few weeks back as a way to restore after using the leaked 2.1 RUU... I think it'll help you out:
http://forum.androidcentral.com/htc...pair-your-bootloader-after-using-2-1-ruu.html
Key advice (as mentioned above): ALWAYS read the warnings before flashing something.
Click to expand...
Click to collapse
I used that method about a week ago, work great in about 5 mins I was back to full root and flashing 2.1 roms again!
Using only an SD card this method will restore your old boot loader >> http://forum.xda-developers.com/showthread.php?t=657086
I ran the ruu for the new PRI version, but I was able to root it the same ol' way and have installed 10 different ROMs in the last two weeks.
Just recently I wanted to revert my PRI and boot loader to single out a problem I was having and used the above method. I was able to return my phone to complete stock without running any ruu as described in the link above.
Glad that link helped some people out...
Basically, if gbhil posts something, I trust it.
thanks a lot..to those who actually helped, I'm trying this out now..Ive flashed RUUs before and test ROMs for over a half a decade..
someone one this forum said the RUU came pre-rooted..
I'm no noob, check my join date before: before kcarpenters..lol no offense
I had my phone (HTC HERO) rooted and it worked great then my phone was stolen. When the replacement came in I rooted it first thing with fresh 2.1.2 but my phone would not receive or make calls.
So then I had to run the 1.5 RUU to get back to stock thinking I was going to have to get some warrant work. Well that bricked my phone getting the 110 error that many other seem to get too.
I found the fix, and opened command prompt and ran fastboot oem boot. This fixed my phone and I was back running 1.5
After testing my phone, I seen that it made calls with not problem and it was the fresh rom that was messing my phone up. I decided I would not root my phone again, instead just install the 2.1 update. I tried to update through the phone but it did not work so I downloaded the 2.1 RUU and ran it.
I've been using the 2.1 update now for a week and I am unsatisfied. It is incredibly slow compared to my rooted phone. I tried using fresh kitchen to root my phone but it says I have a custom room and fails. (I thought running the 2.1 RUU was like a factory update?)
Anyways, is there a way for my to root my phone again? I am stuck and not sure what to do.
Sorry for the wall of text.
... which phone?
Post it in the forum for the appropriate phone or nobody will know what to tell ya.
Sorry, I'm new to the forums and a little lost.
HTC Hero.
Yes u can check in the hero cdma software forum there is a guide
Sent from my Hero CDMA using XDA App
I didn't post this in the CM7 thread because I believe my problem was a glitch during rooting, not CM7 which seems to work fine.
I recently dropped my Insight 4G which had been rooted and was running the Revolution ROMs and cracked the screen. I purchased a replacement phone, which arrived with the Gingerbread ROM from AT&T.
I decided to try CM7 this time and followed the instruction on wiki.cyanogenmod.com/wiki/HTC_Ace to the letter on rooting, installing clockworkmod, and installing the CM7 roms. Everything worked perfectly with one exception.
Now the phone takes > 10 mins (closer to 20 actually) to boot every time it reboots. I have tried restoring a nandroid backup of the Revolution ROMS from my original phone and everything works fine, but reboot is still very, very long. Restored CM7 from nandroid backup and tried to install RUU file to restore the phone to AT&T, but the software times out due to the extremely long boot time. Everything seems fine on the phone except for the boot time and I don't know what to do next.
After reading a lot of posts it appears that the instructions I followed have a similar effect to using the outdated Ace Hack Kit here. (Wish I'd used the new one). I am well and truly "Jammed Up"
Anyone have a possible fix? I am happy to do whatever it takes... not worried about data.
tricotec said:
I didn't post this in the CM7 thread because I believe my problem was a glitch during rooting, not CM7 which seems to work fine.
I recently dropped my Insight 4G which had been rooted and was running the Revolution ROMs and cracked the screen. I purchased a replacement phone, which arrived with the Gingerbread ROM from AT&T.
I decided to try CM7 this time and followed the instruction on wiki.cyanogenmod.com/wiki/HTC_Ace to the letter on rooting, installing clockworkmod, and installing the CM7 roms. Everything worked perfectly with one exception.
Now the phone takes > 10 mins (closer to 20 actually) to boot every time it reboots. I have tried restoring a nandroid backup of the Revolution ROMS from my original phone and everything works fine, but reboot is still very, very long. Restored CM7 from nandroid backup and tried to install RUU file to restore the phone to AT&T, but the software times out due to the extremely long boot time. Everything seems fine on the phone except for the boot time and I don't know what to do next.
After reading a lot of posts it appears that the instructions I followed have a similar effect to using the outdated Ace Hack Kit here. (Wish I'd used the new one). I am well and truly "Jammed Up"
Anyone have a possible fix? I am happy to do whatever it takes... not worried about data.
Click to expand...
Click to collapse
What I would do is return to a full stock. Then run the hack kit. But that is just me as I have never donebit with the CM wiki instructions
This is a common issue with the latest batch of Inspires (post Aug, 2011 MFG). The hardware is different and not compatible with any hboot except the one that ships with the GB RUU. If you downgraded as per the CM wiki, then you necessarilly installed an older hboot and this is the root cause of your problem.
You can easily replace the hboot on an S-OFF Inspire once it finally does boot by simply writing the later hboot image to the hboot partition (partition 18). There's instructions here:
http://paste.pocoo.org/show/495273/
You can jump into the IRC channel if you need some one-on-one help:
http://webchat.freenode.net/?channels=#liberatedAria
Ok, after many hours of fiddling I finally got it back.
I used the hack kit to re-install the stock RUU using the alternate (hboot) method. It took a LONG time, but was successful. I then used the hack kit to re-root the phone and installed CM7 nightlies. The ace hack kit is a wonderful tool, and I thank the author for making it.
Gene Poole said:
This is a common issue with the latest batch of Inspires (post Aug, 2011 MFG). The hardware is different
Click to expand...
Click to collapse
Hey Gene so what your saying is all Inspire batches post Aug, 2011 must be rooted using the current acehack kit only right?
And older methods of rooting will cause intermittent booting?
Crazy Food For Thought....
jadeus0831 said:
Hey Gene so what your saying is all Inspire batches post Aug, 2011 must be rooted using the current acehack kit only right?
And older methods of rooting will cause intermittent booting?
Crazy Food For Thought....
Click to expand...
Click to collapse
That is correct. The new AHK uses an HTC signed interim firmware patch put out for the DHD which has only a boot.img, radio.img and recovery.img. Fortunately, the radio and boot images are ones that are compatible with gfree and the S-OFF routines can be run without disturbing the rest of the firmware (hboot, system and data mainly), but unfortunately, the kernel is not compatible with the Inspire's graphics hardware so the process literally runs in the dark, and because of the GB changes, it must run in two stages involving both adb and fastboot. USB issues rampant among PCs (so many PC programs assume they are the only program you're ever going to run and so hijack the USB bus thinking you're never going to plug in any other device but theirs) so it is very important that both adb and fastboot drivers can run unimpeded. Occasionally a situation arises where adb runs OK, but fastboot fails and this leave the device in an intermediate state which is not in itself bad, but because there is a blank screen, users freak out and do everything but the right thing (usually involving a "wipe" from hboot) which really screws things up.
Hi Tricotec.
Please, could you describe the steps for doing it. I have the same problem.
Thanks.
nlennis said:
Hi Tricotec.
Please, could you describe the steps for doing it. I have the same problem.
Thanks.
Click to expand...
Click to collapse
i also need those steps.
i tried with ruu but white rebooting bootloader it takes around 10 minutes due to which connection time out occurs b/w phone and wire thus ruu is not installing properly, is there any way we can edit ruu exe file to wait for accepting connect for 10 minutes or so
or please tell other steps
sandeep88822 said:
i also need those steps.
i tried with ruu but white rebooting bootloader it takes around 10 minutes due to which connection time out occurs b/w phone and wire thus ruu is not installing properly, is there any way we can edit ruu exe file to wait for accepting connect for 10 minutes or so
or please tell other steps
Click to expand...
Click to collapse
Nice!! you messed the bootloader for not reading all the warnings. The only fix for the issue is this one:
http://tau.shadowchild.nl/attn1/?p=188
glevitan said:
Nice!! you messed the bootloader for not reading all the warnings. The only fix for the issue is this one:
http://tau.shadowchild.nl/attn1/?p=188
Click to expand...
Click to collapse
i did not did this, i hv gingerbread 2.47 ruu, and i am aware not to downgrade it
its done by my ebay friend, lol he ha sonly that older ruu and he updated 100's of inspire with that, its the first time he got a newer inspire
anyways thanks a lot xda rocks
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.