[Q] Problem with RUU update? - Android Software/Hacking General [Developers Only]

So my Evo 4G messed up recently because I tried to flash Synergy's rom on it (I used unrevoked to root and had Clockwork Recovery) and it failed because it couldn't update the boot.img file (I'm definitely new at all this stuff). When I tried to start up my phone, it would just take me into bootloader. I couldn't restore anything because of the boot.img not being updated, for some reason I don't know why. After getting tired, I googled around on how to fix it, and I read about the PC36img.zip. Naturally, I downloaded and put it on my sd card and let it read from bootloader, but boot still was failing to update. I tried the PC36img.zip that is compatible with HBOOT 2.10.0001 and that was a no go. After it failed, my recovery would just show up as a red triangle and exclamation mark. Then I read about the RUU, so I tried to run it and yet again, "boot" would NOT update. SO now my phone just showed the htc logo in the middle with 4 exclamation marks in the corners of the screen, and when i unplug the usb it gives me the bootloader screen, except it only shows RUU highlighted in orange. Then I used the program "fastboot commander" and after messing around trying to flash zips and recoveries and boots and such, I somehow managed to get my phone to load into bootloader properly on my next start up (using volume down and the power button). I went into recovery and it was now Amon-Ra's (so I guess I flashed an amon-ra recovery zip), but I had no backups. I threw the rom "SavagedZen(MOD)-RC2-Evo4G" on my sd card and flashed it, and it worked. So my worries were over, until I decided that I wasn't going to mess with this rooting stuff anymore. That's when I got unrevoked-forever-son and put it on my sd card and flashed it, which made the phone s-on. Then I thought "okay since my phone is working, the RUU will work now" since I wanted the stock rom. So I ran the RUU again and the boot still did not update, so now I'm back to the htc logo with 4 exclamation marks in the corners, and I now have s-on so everything I try to flash through fastboot commander fails and my bootloader isn't even working because it only shows RUU in orange.
So here is my question: What can I possibly do now to fix my phone? (handing it to Sprint doesn't sound fun)
And sorry for the huge story, I just wanted to put everything I did in there to see if it contributed to the problem.
I'm hoping the easiest way is to just run an RUU but my boot is rejecting every update so far, so I have no idea what to do...

Anyone know a solution?

Related

[Solved] almost bricked mt4g. please verify my next step

First, let me say thanks to all who contribute. I started with a G1 when it first came out, using the JF mods and lurking these forums for hours. Without you guys, we'd all be stuck with boring stock devices!
Heres my question:
I've done a search and just want someone to verify my next planned step.
Tonight I think almost bricked my Mytouch 4g. I had root, and had CM6.1.2-RC2 installed. It was working great.
Then I wanted to get the CM7 nightlies working. I couldn't get the CM7 rom past the mytouch splash screen. So, I upgraded Rom Manager, and thought i had to upgrade ClockworkMod to 3.0 to get the CM7 nightly rom to boot. I accidentaly flashed the wrong ClockworkMod Recovery. I flashed the file that was for a G2 (vision). Rebooted without noticing my mistake, than noticed my error when I couldn't get into recovery mode.
Fortunately i installed Hboot during the rooting process. I'm planning on letting Hboot flash the file mentioned in this post to get back to stock:
http://forum.xda-developers.com/showpost.php?p=10514066
What do you think?
Just don't want to get myself in deeper S...
Thanks again.
connect the usb and run adb. Boot into bootloader and flash the recovery 3.0??? that way. You'll be good to go after that
osugsxr said:
connect the usb and run adb. Boot into bootloader and flash the recovery 3.0??? that way. You'll be good to go after that
Click to expand...
Click to collapse
You can connect adb with the bootloader? I ran:
Code:
adb devices
and adb came back with no devices found.
How do I flash the recovery if adb has nothing to communicate with?
BTW, I'm using Hboot Engineering, and Hboot does recognize the usb connection by displaying: HBOOT USB PLUG
fastboot devices
fastboot devices
fastboot flash recovery recovery.img
SOLVED
Thanks for trying to help osugsxr. I will have to read up on fastboot.
However, I did not follow your advice. I didn't get your reply in time to try fastboot. My impatient ADD personality went ahead and followed the advice in the thread that I referred to in my original post. In an effort to help others who may have gotten into a jam, heres what I did:
1. Took out my SD card and connected it to my PC via external SD card reader.
2. Because I had a ton of crap on the SD card, I formatted it FAT32 to have a clean card.
3. Downloaded the stock Glacier rom (A large 315mb file. Should have a filename like PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M_release_155771_signed.zip)
4. Copied the stock Glacier rom to the SD blank card.
5. Renamed the rom to PD15IMG.zip (maybe case sensitive, not sure)
6. Unmounted/Ejected the SD card from the PC reader an put it back in my phone.
7. Pulled the battery on my phone for about a minute then put it back in.
7. Hold volume down and the power button at the same time.
8. Hboot should start up, then after a few moments it will say loading PD15IMG.zip. After PD15IMG.zip loads, it will ask you "Do you want to start update?". Press VOL UP for Yes.
9. You will then see Hboot working its way down a list of about 9 items. Be patient, this takes a while. After this is done, it will say so, and tell you to press the power button to reboot.
Hopefully you have successfully flashed the stock rom, and your phone will be back to what it was like when you first bought it.
I attached pictures of the Hboot screen and flashing process for reference

When switching to recovery mode phone gets stuck on Google Logo

i was trying to re-root my phone after an update i did with my nexus s. i was following the step by step root by allgamer http://forum.xda-developers.com/showthread.php?t=895545. i skip the unlock bootloader since it was already unlocked skipped to the flash img part and did it then after that i went to recovery. now it just get stuck at a google logo. if im right i had 2 recovery files in the tools folder, i didnt know another recovery img was in the folder so im guessing this is why it gets stuck, but im sort of new to rooting so im not sure what im suppose to do to fix it. thanks
stock ROM? try reflash recovery
yeah stock recovery. sorry for late reply been busy.
it seemed to fix itself but when i install clockwork recovery, it doesnt seem to work.
it just shows an exclamation mark "!" and a android figure.

[Q] cant get into Recovery after Updating FW

i was following this thread to install the ROM
http://forum.xda-developers.com/showthread.php?t=1429953
i applied the PG58IMG.zip from the http://forum.xda-developers.com/showthread.php?t=1432220 as this was said to be required.
now after i updated the firmware through HBOOT, the phone asked to reboot. but it only stays at the white screen "HTC" and nothing more
all i can do is pull the battery out and put it back in and boot into HBOOT
i want to get into recovery mod to install the ROM i have saved on my SD Card. but like i said i cant get into recovery as once i press "bootloader" it will try to update the FW again. i only can say YES or NO, either one will end up with Rebooting the Phone as my only option. which gets me back into the WHITE SCREEN.
HELP PLEASE!!!
Take the memory card out, boot in to hboot, enter recovery. Reinstall memory card, and deleat the file.
thnx
thx. didnt think of that
taogenix said:
thx. didnt think of that
Click to expand...
Click to collapse
Simple when you know how lol.
I learnt it last week
You can also run "adb reboot recovery" while the phone is off. That way you don't have to take the cover off. It also works if you for some reason get stuck (happens sometimes when flashing PG58IMG.zip files) at the HTC splash screen.

recovery boot issues - red triangle, then reboot

I'm having issues getting recovery to work on a Verizon version xoom. I first flashed CWM version 4.0.0.4. The first time I tried to boot into it, it was stuck on the android with the red triangle for a long time before finally getting into it (coincidentally when I was hitting the volume key, don't know if that's related). Anyway, since then I haven't been able to get into it. It will be suck on the red triangle screen for a minute or two before rebooting into the stock rom (I'm running stock ICS). Since then, I've tried flashing the new TWRP 2.2.2 or whatever version it is and it has no effect. It's still doing the same thing. Any clue what's wrong?
So what I'm reading is suggesting that the android guy I'm seeing is the stock recovery. I'm not sure how that's happening. I'm installing the recovery using fastboot on my PC and being in the bootloader on my xoom. The prompts on both appear to confirm success.
I haven't tried this yet as I'm at work, but I think I've got the issue sorted. The following is what appears to be happening from what I've read.
1. I've still got the custom recovery stalled. When the Android guy pops up, one needs to press volume up to enter the options. Otherwise, it reboots.
2. The recovery flashes are taking because I'm booting back into the rom after a flash. The system's built in recovery protection is re-flashing the original recovery at that point.
3. To make my CWM/TWRP/whatever flash stick, I'll need to power down and then boot directly into the recovery.
I'll post again tonight to say if this works. Hopefully this thread can help out others who have the same issue.
If you don't get that to work fastboot img from link..
http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img

[Q] One Mini Unable to flash recovery "IMAGE UPDATE ERROR"

Hi, I have a unlocked HTC One Mini S-ON, not sure if root is still there.
I had it loaded with One-Hybrid-Rom, which used to work fine.
Whenever the phone runs out of battery and I recharge it, after trying to reboot, I always get bootloader.
I have to reboot boatloader 100 times before I finally get the HTC screen and the Rom boots up.
Once the rom is loaded, the phone works fine.
Also, in bootloader, I can NOT enter recovery. When I select "Recovery", it gets back to the same bootloader screen.
So I tried flashing the recovery partition with all kinds of versions of twrp and cwm.
The phone is perfectly connected with adb, fastboot. I use fastboot flash firmware to try and flash the recovery, but it ALWAYS gives me the same error, it is able to send the file to the phone perfectly, but when it starts writing I get "IMAGE UPDATE ERROR".
I have tried literally everything to get the recovery partition working again, but all fails.
As I said, once the phone is booted up, it is working fine...
Is there a fix for this issue? It is just impossible to reboot the phone 100 times before the rom loads.
Thanks a lot guys.
feemanbe said:
Hi, I have a unlocked HTC One Mini S-ON, not sure if root is still there.
I had it loaded with One-Hybrid-Rom, which used to work fine.
Whenever the phone runs out of battery and I recharge it, after trying to reboot, I always get bootloader.
I have to reboot boatloader 100 times before I finally get the HTC screen and the Rom boots up.
Once the rom is loaded, the phone works fine.
Also, in bootloader, I can NOT enter recovery. When I select "Recovery", it gets back to the same bootloader screen.
So I tried flashing the recovery partition with all kinds of versions of twrp and cwm.
The phone is perfectly connected with adb, fastboot. I use fastboot flash firmware to try and flash the recovery, but it ALWAYS gives me the same error, it is able to send the file to the phone perfectly, but when it starts writing I get "IMAGE UPDATE ERROR".
I have tried literally everything to get the recovery partition working again, but all fails.
As I said, once the phone is booted up, it is working fine...
Is there a fix for this issue? It is just impossible to reboot the phone 100 times before the rom loads.
Thanks a lot guys.
Click to expand...
Click to collapse
No one?
No-one willing to help me on an unflashable recovery partition?
Sometimes phone boots into modded OS and runs perfectly, but mostly (99 out of 100 times) it just reboots to bootloader,
unable to enter recovery.
When flashing recovery (I tried all possible recoveries) via fastboot, it connects, but then I get "Failed, image update error"..;
I would really like to use this phone again...
It is S-ON, Unlocked, Hboot-2.21
Thanks.

Categories

Resources