I am sure this has come up before, but I cant seem to find any thing that matches my description. I am new to these forums and it seems like everyone is incredibly helpful. I rooted my Evo using the method described here
hxxp://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/54844-guide-rooting-3-7-hboot2-02-w-screen-shots-1-27-2011-a.html
Everything went smoothly until I tried installing the rom. I am trying to install Sprint Lover 2.2 and every thing installs correctly until the boot partition. My screen looks like this:
[1] RADIO_V2 - OK
[2] RADIO_CUST - OK
[3] SYSTEM - OK
[4] USERDATA - OK
[5] WIMAX - OK
[6] BOOT - Fail-PU
Partition update fail!
Update Fail
My phone works when i reboot it, but I just want to make sure that I didn't do anything incorrectly. Is there anything I can do to fix this? I might just being anal, this is my first time rooting.
Thanks in advance for your help!
Related
I have messed up my phone, and not sure exactly how.
When I first got my evo in august, it came with Froyo. I tried to root it using the procedures for 2.1, not knowing that it was for 2.2. My mistake. I went through the procedures, and it never worked. Then when the rooting for 2.2 came out, i tried to do that, but it didn't work. I followed the instructions from here and followed allong with the video on youtube. When I was pushing those files using the command prompts, they all worked, but that biggest file never came through.
On Tuesday, i was able to use unrevoked 3.2 to root my evo. I know it was successful because unrevoked said done when i finished. I was able to do the wifi tether on it, plus the screen shots, and superuser was asking for permisions, so I know it was fully rooted.
Today I tried to do a rom, and I was unsuccessful from the start. The phone wont start the recovery mode.
This is what it says:
SD Checking....
Loading... [PC36DIAG.zip]
No image!
Loading... [PC36DIAG.nbh]
No image or wrong image!
Loading... [PC36IMG.zip]
And then it will go to the next screen, which says:
Parsing...[SD ZIP]
[1] BOOT
[2] BOOTLOADER
[3] MICROP
[4]RADIO_VZ
[5] RECOVERY
[6] SPLASH1
[7] SYSTEM
[8] TP
[9] TP
[10] USERDATA
[11] WIMAX
Do you want to start update?
So I've pressed yes once before. However, my phone will not move past these screens. I can select all the options, like clear storage, power down, etc. I can't go into recovery. When I do, it shows a black screen with a phone and a red triangle with an exclamation point.
I won't say that it is bricked, but I know something isn't right. Have I messed up my phone beyond repair? And if this is in the wrong place, I am starting a thread in the Q and A general forum with the exact same message.
You trying to flash a rom from the bootloader? Try doing it from recovery...
You probably never deleted/renamed the PC36IMG.zip after rooting.
Also, delete the PC36IMG.zip from your sd card. You dont need it anymore. Just download Quickboot from the market and you can boot directly into recovery instead of selecting it from the bootloader.
Looks like you forgot to delete that pc36img zip from the root of your sd card and you're just updating that same image every time. Try deleting that first or select no for the update next time you boot into recovery.
Sent from my PC36100 using Tapatalk
m4rk0358 said:
You probably never deleted/renamed the PC36IMG.zip after rooting.
Click to expand...
Click to collapse
+1
Also sounds like you may not have flashed a custom recovery yet.
Sent from my PC36100 using XDA App
No, I have not deleted the pc36img.zip file. i can't get it to cut on so i can connect it to the computer to use as a (usb) disk drive to delete it.
When I select no, i don't want to update it, it takes me back to that screen that says hboot at the top.
I also haven't flashed a custom recovery because it gets stuff on that black screen when I select recovery.
I can't use quickboot because I can't get to the phone and apps part of the phone.
If you moved past the bootloader screen and into the black screen with that cool wittle triangle then you may be able to ABD into recovery. Wipe and then flash from there. You can also remove your micro sd card and put into a sd card reader on your pc. Find and delete that pc 32 zip!
Sent from my PC36100 using XDA App
This has happened to me a couple of times, just run the PC36IMG again, let it update again, then reboot. This worked everytime
Sent from my PC36100 using XDA App
I bought an EVO off eBay the other day and it had a trashed MEID. Repaired the MEID and wrote the HA and AAA secrets. Unfortunately, I had a little accident...I overwrote some NVItems that probably should not have been messed with. When I reboot the phone it goes into a continuous boot loop. I can hold the VOL DOWN button and enter the bootloader. After scanning various threads I decided that it might be best to try PC36IMG.zip. I put it in the root dir of an SD card, booted into the bootloader and started the update. Here is the result:
-Revolutionary-
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Mar 8 2011,17:02:15
HBOOT
Parsin...[SD.ZIP]
[1] BOOT - OK
[2] BOOTLOADER- Bypassed
[3] MICROP - OK
[4] RADIO_V2 - Fail-PU
[5] RECOVERY - OK
[6] SPLASH - OK
[7] SYSTEM - OK
[8] TP
[9] TP - Bypassed
[10] USERDATA - OK
[11] WIMAX - OK
Partition update fail!
Update fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
Evidently the person who owned the phone before me had rooted it but I don't really know how to make heads or tails of this information. After I did the PC36IMG update I rebooted and I'm still in the boot loop. If I select RECOVERY after the update it just reboots and continues looping. Can anyone help me resolve this? Obviously, the boot loop is due to my accidentally changing something in NVItems that I shouldn't have. I have tried flashing a couple of stock ROMs but I don't think anything is really changing because it seems that the radio version number never changes.
Radios don't change with roms, I'm not real familiar with NV items but I have seen some threads about it around, try Googling "changed NV evo4g bootloop" and see if it pulls up the old threads, if I'm not mistaken there was a fix that was 50-50, worked for some and not others, but its worth a shot, only problem is I'm not sure if the thread was deleted or not cuz I haven't seen it in a month or so.
Sent from my iCS'd out EViL4G, soaking in a bowl of Ramen Noodles
I don't think the pc36img will flash correctly with the 6.16 hboot. You have to flash the mod hboot to her it back to 2.16. Search for how to unroot revolutionary and you should find it. After your hboot is back to 2.16 then try the pc36img again. Also the hboot and radio on the phone must match that of the pc36img or it will fail every time.
Sent from my DECK'ed out EVO
Recently I decided to get my phone back to stock so I started looking into the unrooting methods. During this process, I came across error after error. Usually error 170 whilst in the Ruu process. After hours of googling I had no luck so tried the alternative method of using the PB99IMG.ZIP file. All seemed to be going well until I got this message.
HBOOT
Parsing... [SD ZIP]
[1] BOOTLOADER - bypassed
[2] RADIO_V2 - Fail - PU
[3] RADIO_CUST - OK
[4] BOOT - OK
[5] RECOVERY - OK
[6] SYSTEM - OK
[7] USERDATA - OK
[8] SPLASH1 - OK
Partition update fail!
Update Fail!
This is the information that comes up on my phone when I put my phone into recovery mode.
-Revolutionary-
BRAVO PVT 4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL - SYNW0101
RADIO-5.17.05.23
Aug 10 2010, 17:52:18
I should also say that my SD card is currently 3gb with a 1gb with an EXT 4 partition.
When I receive the error my phone will neither boot into recovery or into the OS. My screen displays the HTC logo and then either goes black or has black lines across it.
All I currently want to do is get my Desire back to its stock 2.2 like it was when I got it out the box.
If anyone can shed some light on this that would be brilliant.
Thanks.
Never needed to RUU myself but if you want to return totally to stock and remove S-off you'll need to fastboot flash the hboot downgrade from AlphaRev first. Current AlphaRev are protected. I'd do some research on the Radio v 2 error as well, it might be related to the above but I don't know tbh.
Sent from my HTC Desire using Tapatalk 2
reply
I looked into the radio v2 fail and its apparently to do with my partition. I have also looked at the alpha rev instructions but don't understand this part.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
I don't know what I'm meant to check and against what.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
I don't understand what I'm supposed to rename the file to.
Radio brick is usually bad. Try the 2.3 RUU and report back with any luck. Find it in resources on my guide.
Hey bortak, this one is the same guy who is having. MISC Aissues with recovery.
So OP, which one is the current state of the phone?
via xda app
stankyou said:
Hey bortak, this one is the same guy who is having. MISC Aissues with recovery.
So OP, which one is the current state of the phone?
via xda app
Click to expand...
Click to collapse
Oh... well that sucks...
Try the 2.3 RUU I guess, and good luck.
Thanks to everyone's help. I ended up getting Amon Ra recovery to sort fix my recovery and then flashed Cyanogen which has kept more happy in the mean time.
Thanks again.
Hi,
could any one help me please,
since I bought my phone I can not flash any rom other than CM7.
the problem, I thought the best solution is to go back to stock>
thats why I tried to flash the following rom and I forgot that my hone is still s-off:
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed
and I ended up by the following issue:
"ERROR [152]: IMAGE UPDATE ERROR
When I unplug the usb cable from my phone this is what my phone reads
RUU
Parsing...[downloaded ZIP]
[1] BOOT - Fail-PU
[2] RECOVERY - OK
[3] SYSTEM - OK
[4] USERDATA - OK
[5] SPLASH1 - OK
[6] WIMAX -OK
Partition update fail!
Update Fail!"
After I pull the battery and turn my phone back on it just has a black screen. Says HTC in the middle and there are four Exclamation Points in triangles in each corner.
Can someone please help meby solving this issue? I dont mind to reinstall CM7 but how??? I cant open the recovery or the bootloader????
Let me preface this by saying I am not super familiar with this system, I rooted this for my sister.
I am stuck in a bootloop, I am S-Off
I have tried to restore to stock. I placed the stock image on my SD card and it was recognized and it attempted to update. The file is good and the MD5 checked out.
The results are below, and I have also included 2 screen shots.
[1] TP -OK
[2] Recovery - OK
[3] Bootloader - Bypassed
[4] Splash1 - OK
[5] Boot - OK
[6] Userdata - OK
[7] TP - Bypassed
[8] System - OK
[9] Radio - OK
It said during the update that it could not roll back hboot version.
I'm assuming this is related to being S-Off
What is my next move to fix this?
I haven't looked too much into this, but does this guide help? http://forum.xda-developers.com/showthread.php?t=1466295
Sent from my ViperDinc
I am hesitant to follow that because the first step is exactly what I have been doing except with a different RUU file... would the fact that this is froyo change that the bootloader is being bypassed?
For anyone with a similar issue, i fixed this by downloading and installing the android developers kit
http://developer.android.com/sdk/index.html
you have to make sure you install java within the correct folder. ( I believe it is the eclipse folder but the program will tell you when you try to run it the first time)
I then installed htc drivers again just to make sure they were good.
then i downloaded this file
http://www.filefactory.com/file/ccf....01.0622_NV_VZW1.92_release_199487_signed.exe
ran the program from my computer and followed the instructions. I had to run it twice since it froze halfway through the first time and i needed to do a battery pull.
After this i was still in boot loops, but i booted into the recovery and did a factory reset after which point the phone was working...