RUU not working after revolutionary 2.3.3 - EVO 4G General

So I gladly ran revolutionary for my evo. I managed to flash cm7 to it and wanted to see if i could get it back to stock just in case i needed to. Well i ran the file and it reboots the phone and tried to get into bootloader. It sits at the HTC screen and then the program states it fails and cannot find bootloader. Im not sure if this is important to people or not, but my evo is only a month old and if i can put it back to stock for warranty purposes it would be awesome. Anyone else try it?

Related

[Q] I would like to know

I have a T-Mobile MyTouch 3g 1.2 and I have tried to unroot it and load the original rom back on it and for the life of me I can't. It updates the sappimg just fine in hboot until it gets to system and then I get some sort of error and have to reroot it and flash CM6.1 RC1 back on. I have tried running Universal Androot to unroot it with no success. Well, today I downloaded this nice little app from the Market called z4root by RyanZA(I think that's his name) and low and behold it actually unrooted my phone. I confirmed this by rebooting, opening rom manager app and it told me I need root to use it. I used z4root to reroot with no problems. My question is how would I flash the original T-mobile rom if I use this app to unroot my phone. Could I use the RUU.exe or is there a better way? I really want to go back to stock when the OTA for this phone comes out. I don't need to right now, but I just want to know how and try it so I know I can do it when the time comes. Would it be best to use a goldcard after unrooting to load sappimg? If anyone has any ideas or experience doing this please advise and I appreciate everyone here. This forum is great. I am a noob to Android devices and have been coming here about every day to read, read, read. I have learned so much here. Some of it is still gibberish to me, but I am learning. Thanks all!
When not flash a 32A 'port' of the mytouch 1.1 froyo ROM? It will perform exactly the same as any official update.
I was thinking about doing that, but after trying to go back to stock and failing I have kind of made it a challenge to get this done and figure it out. I guess since no one knows what to do I will just keep trying blind and keep reading. Thanks all and have a great day.

[Q] New Evo complaints...

So just decided to get an evo. My wife has had hers since release day. This one Has the 2.20 and the 3.30.651.2 Build. The quality of the screen is horrible compared to hers (the color and brightness). Before even being able to root it I couldnt use QIK because it reboots the phone. Downloaded the latest one and I can open the software and its after my camera kicks on that it reboots now....
So i rooted it and got the s-off. Now I can take nand backups but its says they are corrupt. Cant flash a rom because it will hang on the Evo boot screen or it will drop to a boot loader loop with the HTC with 4 exclamations....
Is anyone else seeing this or is this guy flat out a lemon?
I have looked around the forums a little and found people having a hard time rooting and s-off which was easy after skimming the forums for a while. Thanks ahead of time for any input in this.
The screen problems im not sure how to fix
there is a new ota to fix your camera issues, yours is most likely the new hardware/camera 004 model.
for rooting the only method that works is toast's, unrevoked wont. Unless im behind on info. Have you tried toast's method?
Unrevoked works fine. Took me about five minutes to root useing that method when I got my replacement phone.
As far as your phone issues, take it back to the store and show them the problems. Get a replacement.
Oracle, go to your bootloader. What is the first line? Is it Supersonic EVT2-3 S-off? If so, I had the same problem. You have bad blocks. My recommendation is the that you flash sprintlovers ROM. It cones as a pc36img.zip, and you flash it through bootloader. I tried every method of rooting and none of them would let me flash through recovery.... I always either got errors while flashing or, even if it seemed to flash fine, it would never boot. Also, Sprintlovers will get your pri corrected. If this works for you, give me a shout, and I have an idea we can try.

[Q] Bricked Wildfire after attempted Froyo Update, Please help!

First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one
Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.
This this a decent guide from Paul over at MoDaCo.
Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.
There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier
Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks

New Mytouch fender user, semi-bricked. Looking for help

Hey guys, I am a decently experienced android user (D1, D2, Eris, SGS, etc). But I seem to have run into a problem. I had rooted a friend of mines MyTouch Fender months ago, using some root app, I forget which, z4root or one of those.
Anyways, he came to me the other day because he got a new phone, and the MyTouch Fender is semi-bricked, im not sure what he did, he said he was playing with it and screwed it up. Anyways, the phone just stays at the Fender loading screen. I can access hboot, recovery etc. The phone is completely stock, 32A, S-ON Google, etc. So what would be the easiest way for me to get this phone going again? He's given the phone to me for free, and I would like to get it working to give to my gf to replace her crackberry curve.
If someone could point in the right direction that would be great. Unfortunately I have no idea what he did to break it in the first place. I've tried wiping data and cache via stock recovery to no avail. Is there maybe a stock oem update.zip that could be flashed via recovery that would flash it back to stock?
I do eventually want to mod the phone and probably throw CM6 on it, but for now I'd rather just bring it back to working stock. Unless rooting it and custom recoveries would be faster.
Thanks in advance.
It's certainly fixable, but I don't know about getting back to stock. The issue is that no one has an actual stock Fender sappimg (sappimg being a file you flash from fastboot to get completely back to stock). The things you will lose by rooting will be the extra Fender apps and the Fender splash image (the first image you see when booting the phone). That's pretty much all that's missing, but there's a group of guys working on getting it back in order. So it all really depends on what you want to do right now. Do you want to root and install a custom recovery/ROM (which will be the quickest fix right now) or would you rather wait until someone can get a similar stock image put back together?
Since you can't get into the ROM, you'll have to root using the goldcard method. Luckily for you it seems you have an extra Android powered phone around to be able to make the goldcard (you need to be able to boot the phone to complete this process).
At either rate, the best way to go about getting you straightened out would be for you to post the phone's current fastboot information. To do this, turn the phone off, then turn it back on holding the back button+power. Post everything from there.
Thanks man. Here's the info from HBOOT:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CLPD-13
RADIO-2.22.28.25
For the moment I would like whatever is the easiest way to get it close to stock. My problem is I don't always readily have access to a computer, but I have lots of android phones, lol. I'd like if I could just make a goldcard on another phone if possible, and flash a normal stock image from another dream/sapphire that is compatible. Is this possible?
Sent from my SCH-I500
hello first post
You could flash the stock sappimg for the myTouch 1.2. The myTouch 1.2 is the one that came out after the Fender. Same everything minus the Fender splash screen and apps. It also isn't capable of getting the 2.2.1 OTA update that came out last month. It's also stock 1.6, but it is very stable and pretty fast considering the phone's hardware.
I can tell that you that your friend's phone got hosed doing the OTA update and he could've gotten a Samsung Vibrant as a trade-out if he would've called T-Mobile about the issue, but we won't tell him that.
Rooting would require computer access. Actually, you'll need a computer period. Either rate. Before we do anything, try booting into recovery (hold home+power) and doing a "wipe data/factory reset" and then reboot. We could also try just reapplying the update.
You can hit me up on Google Talk at [email protected] if you want to get this sorted out tonight instead of having to go back and forth.
Do you have custom recovery or stock recovery...
If it is custom recovery, then fixing your problem(s) is pretty straight forward...
mumilover said:
Do you have custom recovery or stock recovery...
If it is custom recovery, then fixing your problem(s) is pretty straight forward...
Click to expand...
Click to collapse
Got him on Google Talk. Apparently his friend or the former owner hosed the phone doing the OTA since he's got the new radio and the SPL is untouched. We're going to try re-flashing the OTA update and maybe root later on. He's just trying to get it back working.
Yup. Stock recovery. From what I just got from the guy I got it from, it died after/while doing the ota update. It stuck on the splash when it went to reboot.
My guess its due to the fact I rooted the phone like 8 months ago, and removed a bunch of stuff via adb. Including probably what it considers some critical system stuff.
Sent from my SCH-I500
have a mytouch 3g 1.2 with the old radio and SPL, i acidently bricked it trying to flash the new radio and SPL and now i cant get into recovery or fastboot and the flash screen is frozen, pleassssssee help me get this fixed it has been completel useless for the last week or so

Trying to unroot Evo after using Simple Root

I'm trying to get my phone back to stock because i used Simple Root v.1 when it came out last year. I need to bring my phone to Sprint because my USB port is defective and won't charge anymore. I have a hardware 2 version of the phone. Not sure if that helps or not.
This thread (i would post in there but it says i must have more than 10 posts to do so) says i can just flash a stock signed rom, but my phone says "S-off" even though i never used unREVoked forever. Do i just flash the rom anyway?
How will i know (or Sprint) once i flash the stock rom if my phone is stock with no root?
Download the Unrevoked S-on zip, place that on your sd card and flash it like you would anything else.
After that, download the PC36IMG.zip for the 3.70 OTA here (the one in the OP of the link you posted is out of date, I know b/c I just used it last week):
http://forum.xda-developers.com/showthread.php?t=884060
Rename the file so it says PC36IMG.zip and that is the full exact name, remove all the other crap.
Place that on your sd card, turn the phone off and power on while holding vol down. This will take you to hboot where it will read the PC36IMG.zip. Follow the on screen instructions to update and you will be unrooted.
Once you do that, power off again and go back to hboot by holding power+vol down (same as before). Once you get to hboot, and it says s-on, you will know you unrooted.
So i tried the unREVoked S-on tool and my phone still says S-off. I tried it three times and no change.
Should i go ahead and just flash the stock 3.7 ROM? I downloaded it already, changed it to say PCIMG36.zip, and moved it onto my SD card.
Currently trying to get my phone charged up to at least 30% before flashing the ROM but it is such a pain to get my phone to charge. If i move the charging wire around i can get the charging light to come on but i never know if it is really charging because most of the time i'll turn my phone on and it is only charged to 5-7%.
I don't think it will work if your are s-off. Try redownloading the s-on.zip, esp if you dl it from your phone.
Edit: Just making sure you flashed the s-on zip from recovery?
Yes, i flashed the unrevoked tool from recovery and it says it installed successfully but it still says s-off.
I think that was toasts methods they used back then.
Sent from my PC36100 using Tapatalk
So i went ahead and just flashed the 3.7 stock ROM and it worked. It says S-on and looks to be back to stock. Unfortunately, the local sprint repair store just closed so i will bring in my phone tomorrow. It will be nice to have a phone that charges again. I guess i should be happy it happened two months prior to my one-year manufacturer warranty expiring.
Thanks for the help guys!
Anytime, glad you got it sorted.

Categories

Resources