bootloader 1.49 and S-on NEED HELP! - Droid Eris Q&A, Help & Troubleshooting

bootloader 1.49 and S-on NEED HELP! - Droid Eris Q&A, Help & Troubleshooting

[[[[[[[[[[[[[[[[PROBLEM SOLVED]]]]]]]]]]]]]]]]]]
hi can someone please help me? the phone is able to boot into HBOOT. a normal boot brings up the skateboard droids and stays on it for good. This is what is shown when i go into hboot.
PB00100 XC SHIP S-ON
HBOOT- 1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
FEB 8 2010, 00:08:56
HBOOT
<SEND> FastBoot Mode
<VOL UP> Recovery
there is no recovery on this phone, pressing the VOL UP button just takes the phone to the 3 skateboard screen and gets stuck there.
Can someone please advise me on what to do? Thank you in advance.

Well, I think your best bet may be to try do a factory reset. From http://www.shipped-roms.com/index.php?category=android&model=Desire :
1. With the phone turned off, press and hold the Volume Down, Send (green phone) and Power buttons. The device will turn on. Keep holding down the keys unto you see a screen to clear storage.
2. Press the track ball.
3. Follow the instructions to complete the hard reset.
Click to expand...
Click to collapse
If that does not work, you may be able to install the Leak V3 PB00IMG.zip. You can download it from here: http://www.shipped-roms.com/downloa...sire&file=Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP
Rename that file to PB00IMG.zip (that's letter P, letter B, zero, zero, letter i, letter M, letter G period letter Z, letter i, letter P. Of course you can just delete the starting portion of the name and leave the PB00IMG.zip.)
Copy it to your SD card (you will probably need a USB SD card reader for your computer to copy the file over)
This post walks you through the steps to install the image file: http://androidforums.com/eris-all-things-root/75384-visual-example-pb00img-zip-update-method.html
Alos, whether it works or not (it may not), make sure to delete the PB00IMG.zip file from the SD card as soon as you can. Let us know whether it worked or not.

Hi thanks for the reply
i tried the hard reset, it went through that process without any problems. it rebooted and went straight back to the 3 skateboards. So i did your second suggestion. I downloaded the leak v3 pb00img.zip and renamed it to PB00IMG.ZIP as you said i should and copied it to my Sd card. I started the phone in hboot again. I tried to upload a picture of what it did, but forum rules wont let me till 10 posts.
Anyway it ran through the whole "SD checking" and said no image! for everything and just disappeared and i was left at the same hboot menu as before. What to try and do now ?

god_damn_eris said:
Hi thanks for the reply
i tried the hard reset, it went through that process without any problems. it rebooted and went straight back to the 3 skateboards. So i did your second suggestion. I downloaded the leak v3 pb00img.zip and renamed it to PB00IMG.ZIP as you said i should and copied it to my Sd card. I started the phone in hboot again. I tried to upload a picture of what it did, but forum rules wont let me till 10 posts.
Anyway it ran through the whole "SD checking" and said no image! for everything and just disappeared and i was left at the same hboot menu as before. What to try and do now ?
Click to expand...
Click to collapse
If you renamed it in Windows, are you sure that you didn't have the file extensions turned off, so that the file name is actually PB00IMG.ZIP.ZIP? I'm on a Mac, and can't recall on Windows how to turn on display of file extensions by default, but that is always a possibility.
I'd see if that's the case first. Make sure that the file name is exactly PB00IMG.ZIP

i doubled checked, its correct the way i renamed it. in windows we don't put the .zip extension, we would just rename it as PB00IMG. Anyway i tried it both ways, i did it as PB00IMG.ZIP just in case and it did the same thing. It goes through the "Sd checking" and gives the No image! right under, then goes back to the hboot with the <send> and <vol up> menu.
stumped

god_damn_eris said:
i doubled checked, its correct the way i renamed it. in windows we don't put the .zip extension, we would just rename it as PB00IMG. Anyway i tried it both ways, i did it as PB00IMG.ZIP just in case and it did the same thing. It goes through the "Sd checking" and gives the No image! right under, then goes back to the hboot with the <send> and <vol up> menu.
stumped
Click to expand...
Click to collapse
Did you put the file into a folder on the SD card or at the root of the SD card? Are you sure that there are no spaces in the file name, either at the start (before the P) or at the end (before the period) - it has to be exactly PB00IMG.ZIP. Also, what is the file size? Is it 104.8 MB (or 109,946,224 bytes)?
Also, see this: http://forum.xda-developers.com/showpost.php?p=24186683&postcount=15
I'm going to be traveling tomorrow - hopefully somebody else will see this.
If that still doesn't work, you can try installing the RUU: http://www.shipped-roms.com/downloa...WWE_2.36.605.1_release_signed_with_driver.exe
Connect the Eris to your computer and run that file - hopefully it can update the phone.
By the way, if you can, take some time to charge the battery with the phone turned off - running in HBOOT kills the battery fast, and the last thing you want is for the phone to be in the middle of a PB00IMG flash and fail because the battery ran out.
If that does not work, your problem is not exactly the same, but this procedure may work: http://androidforums.com/eris-all-things-root/556826-stuck-boot-up-screen.html - well, starting at post 15: http://androidforums.com/eris-all-things-root/556826-stuck-boot-up-screen.html#post4475687
It's a lot of steps, but it's worked a few times before.

I placed the PB00IMG.ZIP (i've looked at it several times to make sure im doing what you said and spelling it the way you want me to.) in the Root of my SD card, i dont have any other files on the sd card, just that zip file.
I right clicked it and went to properties via windows explorer (I've also checked to see using the DIR command in command prompt.) It shows no spaces before or after and no .zip.zip.
The file is size: 104 MB (109,946,224 bytes)
Size on disk: 104 MB (109,948,928 bytes)
I read the first link you supplied to me in the last post by bftb0, im not sure if the sd card is partitioned or not, he says it SHOULD NOT BE, so i'll try and reformat the sd card first before trying anything else. Will let you know how it goes. Thanks for helping again, greatly appreciated.:good:

Okay so i formatted the sd card by putting it in my brothers phone and mounting it to my laptop. Right clicked it and hit format. I kept it at the default format setting FAT. Reloaded the PB00IMG onto the sd card and put it into the eris. Started up in HBOOT, it did the same thing as before, gave me the No image, and went back to the <send> and <vol up> menu.
I let the phone charge over night, it had the orange led, and it had the green led when i woke up, so full battery charged. i downloaded the RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe and followed the instructions step by step to run the RUU. the update image version had a from "blank" to 2.36.605.1,the phone went into the bootloader, it showed a black picture with the words HTC on it, It said it was clearing data, then it started sending the rom image to the phone. About 3 or 4 mins later it said updating signature and then gave me an error [131]: customer ID Error. The RUU cannot update your android phone. Please get the correct RUU and try again. I hit exit and its reboots to the 3 skateboard droids with the letters "fastboot usb" highlighted in red.
Im gonna start reading the last link you gave me, crossing my fingers something will work.

I tried something different, i formatted the sd card as FAT32 and placed the PB00IMG on the card. I wasnt sure if this was gna do anything but i did it. i put it into the eris and fired up HBOOT, this time it actually picked up the PB00IMG file, it even brought up the progress bar on the top right, it did its thing and processed all the way but gave me this error:
CID incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes
im assuming this is the same error related to that Error [131]: customer ID i got from the RUU.
i think i'll wait and get some feedback from anyone who can help me out with this till Doogald gets back.

god_damn_eris said:
I tried something different, i formatted the sd card as FAT32 and placed the PB00IMG on the card. I wasnt sure if this was gna do anything but i did it. i put it into the eris and fired up HBOOT, this time it actually picked up the PB00IMG file, it even brought up the progress bar on the top right, it did its thing and processed all the way but gave me this error:
CID incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes
im assuming this is the same error related to that Error [131]: customer ID i got from the RUU.
i think i'll wait and get some feedback from anyone who can help me out with this till Doogald gets back.
Click to expand...
Click to collapse
I think that you need to do what I suggested here:
doogald said:
If that does not work, your problem is not exactly the same, but this procedure may work: http://androidforums.com/eris-all-things-root/556826-stuck-boot-up-screen.html - well, starting at post 15: http://androidforums.com/eris-all-things-root/556826-stuck-boot-up-screen.html#post4475687
It's a lot of steps, but it's worked a few times before.
Click to expand...
Click to collapse
My guess is that there is some sort of error with the flash storage on the phone and that procedure will walk you through the steps. Unfortunately you cannot root the phone at this point without a running OS on the phone (that I am aware of). That procedure above (it's a lot of steps) is about the only thing that I can think of that will work with 1.49.0000 S-ON.

doogald said:
I think that you need to do what I suggested here:
My guess is that there is some sort of error with the flash storage on the phone and that procedure will walk you through the steps. Unfortunately you cannot root the phone at this point without a running OS on the phone (that I am aware of). That procedure above (it's a lot of steps) is about the only thing that I can think of that will work with 1.49.0000 S-ON.
Click to expand...
Click to collapse
okay so i was able to get all the files, the htc drivers and also abd and fastboot. I got to the step where it said for me to put the rom.zip (hboot 1.51) in the same folder as the fastboot and adb. iit gave me an error though :
sending 'zip' (180 KB)...
OKAY [ 0.327s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.660s

Try the PB00IMG.ZIP method. Rename the rom.zip file to that name, place that file on the SD card, and restart the phone in HBOOT mode.

doogald said:
Try the PB00IMG.ZIP method. Rename the rom.zip file to that name, place that file on the SD card, and restart the phone in HBOOT mode.
Click to expand...
Click to collapse
I renamed the rom.zip to PB00IMG and placed it in the sd card. Fired up hboot but still getting this error:
CID incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes

Is there any way to get around this error? Seems like its the only thing thats blocking me from from being able to do anything to my phone. Is there anyone else out there that has had this problem before, if so, please advice on how you solved it.

I got a friend who has the Riff JTAG box, i asked him to fix the IMEI and CID and also if he could downgrade the hboot to either 1.46 or 1.47 with S-OFF. Im sending him the phone to look at. I should have it back in a couple of days. I'll report back when i get it back. Thanks Doogald for all your help.

god_damn_eris said:
I got a friend who has the Riff JTAG box, i asked him to fix the IMEI and CID and also if he could downgrade the hboot to either 1.46 or 1.47 with S-OFF. Im sending him the phone to look at. I should have it back in a couple of days. I'll report back when i get it back. Thanks Doogald for all your help.
Click to expand...
Click to collapse
You're welcome. Sorry it didn't work out this way.

doogald said:
You're welcome. Sorry it didn't work out this way.
Click to expand...
Click to collapse
Dont be sorry, you have been more than helpful and i really appreciate your effort to help me :good:, i hope my friend is able to do something with the riff box.

full memory dump needed?
Hi Doogald,
my friend is trying to repair that CID error, his asking me if i can get the full memory dump from a working phone. Im not sure what he means. But he says he needs to copy the boot memory from a working phone to my phone in order to fix that CID error. Would you know where i can find the dump file?

god_damn_eris said:
Hi Doogald,
my friend is trying to repair that CID error, his asking me if i can get the full memory dump from a working phone. Im not sure what he means. But he says he needs to copy the boot memory from a working phone to my phone in order to fix that CID error. Would you know where i can find the dump file?
Click to expand...
Click to collapse
Not sure. Ask him *exactly* in details what he needs. I'm not sure what "boot memory from a working phone" means.

doogald said:
Not sure. Ask him *exactly* in details what he needs. I'm not sure what "boot memory from a working phone" means.
Click to expand...
Click to collapse
The guy is russian so his english is broken, i'll quote what he said:
so I connected it back to get the resurrector report - unfortunately it has no choice except 49 Hboot, so will try to make s-off, as an alternative - there is a possibility to flash the full memory dump from the working phone (just have to find it), and plus I've received on Saturday the ORT jtag Tool in addition to Riff - so give me some time. Riff Box can repair CID - if you remember the default one - I can reflash it. Other then that I should flash the whole mem dump - I ment first I have to find the same but working phone to copy its boot memory or to find on internet - sometimes it is possible to download it. Without the proper CID we are finished - no way to replace the Hboot or flash a recovery
Click to expand...
Click to collapse
.
He says its a .bin file and that its about 500MB in size. Im wondering if its a file we get when we do a nandroid backup?

Related

[SOLVED] Anyway to Unbricked a Droid Eris?

All I can see is the HTC logo with 4 ! inside of a triangle on each corner. This is a been bricked for a long time and I cant remember how it happened but just wonder is there is anyway to fix it
Thanks,

The state your phone is in sounds similar to this
http://forum.xda-developers.com/showthread.php?t=824290
but there is no way to be sure of that, based on the zero details you provided.
Read the ENTIRE POST, not just part of it (it is quite long).

WOW, exactly the same problem this phone has!
If I remember right it was a mix up with ClockworkMod recovery.
That was a very nice recovery, I will have to read and learn all that. That's a lot of info and stuff that I will have to learn to try to fix this phone.

I think all that is AWAY over my head... lol
OMG my head hurts now... lol

stick2e said:
I think all that is AWAY over my head... lol
OMG my head hurts now... lol
Click to expand...
Click to collapse
You don't need to understand the bit where sosicwitit was repartitioning.
If you can only get into that one mode ("RUU mode"), and not HBOOT, nor FASTBOOT, nor recovery, then the only avenue available is to first try his "trick" of flashing the RUU, but dropping the Root PB00IMG.ZIP file into the "rom.zip" file location of the RUU. If you are lucky, that will get you a working S-OFF bootloader. Try that first and report your results.
bftb0

bftb0 said:
You don't need to understand the bit where sosicwitit was repartitioning.
If you can only get into that one mode ("RUU mode"), and not HBOOT, nor FASTBOOT, nor recovery, then the only avenue available is to first try his "trick" of flashing the RUU, but dropping the Root PB00IMG.ZIP file into the "rom.zip" file location of the RUU. If you are lucky, that will get you a working S-OFF bootloader. Try that first and report your results.
bftb0
Click to expand...
Click to collapse
I have the leak v3 PB00IMG.ZIP, however did you have any idea where is the temp file that is created where I can change rom.zip? I'm running windows 7 32bit.
I can get into FASTBOOT and RUU mode but that all I can do with this unit.
Thanks again!

stick2e said:
I have the leak v3 PB00IMG.ZIP, however did you have any idea where is the temp file that is created where I can change rom.zip? I'm running windows 7 32bit.
I can get into FASTBOOT and RUU mode but that all I can do with this unit.
Thanks again!
Click to expand...
Click to collapse
Well, first off - you should say what version of the boot loader you have. It is shown on the fastboot screen. If you already have the 1.49.2000 S-OFF bootloader this current step can be skipped, And you can proceed directly to flashing a recovery using fastboot from the pc. If you do not have the S-OFF bootloader the whole point of this current step is to get it on the phone - in which case you should be using the ROOT PB00IMG.ZIP file, not the Leak-V3 PB00IMG.ZIP file.
All Eris RUU and PB00IMG.ZIP files can be found at:
http://forum.xda-developers.com/showthread.php?t=909921
When the RUU program is running, just prior to the moment when you would begin flashing to the phone, you use the search function on your PC in the folder
C:\Documents and Settings\<your_user_name>
(Edit - in Win7, C:\Users\<your_user_name> )
to look for the file named "rom.zip". (You will probably need to twiddle the dumbass Microsoft setting which prevents searching for hidden files and folders.)
Then, you delete the rom.zip file, rename the ROOT PB00IMG.ZIP file to rom.zip, and drop it into the same location.
Before starting this step, make sure your phone is completely charged and also be sure to verify the file size and md5 checksum of the ROOT PB00IMG.ZIP file you downloaded.
As I mentioned above if you already have the S-OFF bootloader present on your phone, this operation is not necessary and we can proceed to flashing a recovery using the fastboot program on the PC.
Lemme know how it goes.

PS - It would be helpful for you to answer a few questions about your current skill set and computer setup:
- have you used either the "fastboot" or "adb" programs in the past on your pc?
- if not, do you know how to verify communication with the phone in fastboot mode?
(Note that running the RUU utility will install drivers on your PC)
The original Amon_RA recovery for the Eris can be found here:
http://forum.xda-developers.com/showthread.php?t=648025

I have sdk setup and FASTBOOT can see the phone however ADB dont see the phone. If I do adb devices, nothing get listed.

stick2e said:
I have sdk setup and FASTBOOT can see the phone however ADB dont see the phone. If I do adb devices, nothing get listed.
Click to expand...
Click to collapse
"fastboot devices" when the phone is in fastboot mode.
adb only applies when the normal OS is running with USB debugging turned on, or if the Amon_RA recovery is booted.
What bootloader version do you have?

This is where the phone is right now.
1.49.0000 S-ON bootloader
When I get home today I will look for the proper img file and try the RUU option to see if I can get the S-OFF in there. We will see.

If you can get the S-OFF bootloader to "take" with the RUU+rom.zip replacement trick, and you can communicate with fastboot, then
fastboot flash recovery recovery-RA-eris-v1.6.2.img
is the next step.
Please report any errors that the RUU utility reports - we want to figure out which partitions got corrupted by ClockworkMod.
PS - don't let the phone sit in fastboot mode for extended periods of time - it will discharge rapidly even if it is plugged into the charger

This thread honestly scares me and I hope this never happens to me lol

willwgp said:
This thread honestly scares me and I hope this never happens to me lol
Click to expand...
Click to collapse
All you need to remember is this:
newb + Eris + ClockworkMod = disaster waiting to happen
In almost every bricking that has been reported here on the (XDA) Eris forums, ClockworkMod (or running the battery down to very low charge levels) was involved.
What is also notable is that in almost every case, the folks that got into trouble:
- got their rooting instructions from non-XDA sites (e.g. unrevoked, z4root, unlockr)
- could not clearly explain what they had been doing immediately prior to the event - even after repeatedly being asked to do so,
- were unaware what ROM signing is about (or that ClockworkMod doesn't perform it)
The second observation seems to imply a behavioral trait of innattention or sloppiness.
In the hands of people that are experienced, ClockworkMod seems to behave correctly.
For the moment though, let's stay on topic and see if we can revive stick2e's phone. At the moment, I am guessing that there is about a 30% chance of that. We'll find out more when we hear the result of his/her flashing attempt.
bftb0

I think this is going to work!!!! Thinks are looking better.
I try to flash the RUU but replace the rom.zip (what a pain to find it!!!) with the root rom (PB00IMG.ZIP: Eris_RootROM_v2.19.605.1_PB00IMG.zip) and now I have to load a rom in the sdcard to flash the phone. Fingers crossed we will see.
I'm downloading a ROM now.

RUU Error is 110 but I'm on HBOOT-1.49.2000 and S-OFF
Now?
Ok, I need help on what file to select. I dont think that I grab the right file :-(
In the mind time... charging the battery again!

stick2e said:
RUU Error is 110 but I'm on HBOOT-1.49.2000 and S-OFF
Now?
Ok, I need help on what file to select. I dont think that I grab the right file :-(
In the mind time... charging the battery again!
Click to expand...
Click to collapse
DId you rename the new PB00IMG.zip file to rom.zip?

bftb0 said:
If you can get the S-OFF bootloader to "take" with the RUU+rom.zip replacement trick, and you can communicate with fastboot,
Click to expand...
Click to collapse
Ok, HBOOT-1.49.2000 and S-OFF
bftb0 said:
then
fastboot flash recovery recovery-RA-eris-v1.6.2.img
is the next step.
Click to expand...
Click to collapse
C:\sdk\tools>fastboot flash recovery recovery-RA-eris-v1.6.2.img
sending 'recovery' (3834 KB)... OKAY [ 0.826s]
writing 'recovery'... OKAY [ 1.357s]
finished. total time: 2.183s
bftb0 said:
Please report any errors that the RUU utility reports - we want to figure out which partitions got corrupted by ClockworkMod.
Click to expand...
Click to collapse
RUU Utility report ERROR [110]: FILE OPEN ERROR
Parsing... [download ZIP]
[1] User Data - OK
[2] System - Fail-PU
[3] Recovery - OK
[4] Radio_V2 - OK
[5] Boot - Fail-PU
Partition update fail!
Update Fail!

Gimme a minute to fire up a real computer instead of this stupid phone browser.

Well, I fastboot recover revery-RA-eris-v1.6.2.img but nothing happen now :-(
Before used to take me to RA Recovery but now is not.

Announcement: Do You have a Soft-Bricked Eris?

The release by HTC of an unlockable bootloader (v 1.51.0000) for the Droid Eris has created a potential opportunity for rescue of some soft-bricked Eris handsets.
Are you an owner of one of these units? There is a decent chance of recovery back to a working state!
(Props go to Android Forums user "scotty85" for figuring this out.)
This (v 1.51.0000) bootloader is rather quirky - it does not allow direct flashing of individual partitions using fastboot - but it does allow flashing of zip files containing recovery, boot, and system partitions via fastboot with the phone in "RUU mode" once the bootloader is unlocked with a procedure from HTC.
If your phone can be booted into its' bootloader (HBOOT, FASTBOOT, or RUU mode), but can not successfully boot all the way up - or it gets stuck in a bootloop during booting, and you only have a stock recovery on the phone, this might be the approach for you.
Rather than write up the whole method to begin with, I'll just ask for responses to see if anyone is interested. And then take it from there if I get some nibbles.
If you think you have a phone you want to try to rescue, speak up - and say a few words about whether the phone can get into different bootloader modes, which bootloader version you have on the phone, and so forth.
Note: at the moment, getting this to work requires getting the fastboot program running on your PC - it is not a phone-only method. The amount of effort at the command line is minimal, but you will need to be able to get your PC talking to your phone to do this.
bftb0

I have a friend who is in this exact situation. Any help you can provide would be great.

Yatyas said:
I have a friend who is in this exact situation. Any help you can provide would be great.
Click to expand...
Click to collapse
Take your time, and read and understand this whole post before you begin.
[size=+2]Files Needed:[/size]
Collect all the files you will need, get them on to the root folder of your SD card, and verify their MD5 signatures (the copy that makes it to your SD card, not the copy on your computer) :
"rom.zip" - the 1.51.0000 bootloader install payload - here **
MD5: daab6bcbe78c41938a95c4963c5c44e8
custom recovery - either Amon_RA's ("recovery-RA-eris-v1.6.2.img"), or scary alien's trackball-free derivatives here (e.g. the New 1.7.1 version)
"ErisMiscReset_v0.9.zip" here
"MTD_Inspect_v0.9.zip" here
"ErisMTDNuke_v0.9.zip" here (also, please see disclaimer here)
"Eris_RootROM_v2.19.605.1_PB00IMG.zip" from shipped-roms.com. Note that this (also) is renamed to PB00IMG.zip at the appropriate time. **
A custom (dev) ROM, or even a fully stock ROM such as the HTC Eris March 2011 OTA Stock ROM - v2.41.605.6
[size=+2]Installation Method:[/size]
Note:
A less thorough method than what is described here, but shorter, is reported here. Even though I built the "ErisMTDNuke_v0.9.zip" repair tool, I do not advocate using it unless it is confirmed to be absolutely necessary. Moreover, in almost every case, having the Eris S-OFF bootloader on a rooted phone is an advantage, and (also) having the "misc" partition "MainVer" value reset back to a low value after fooling with RUUs or PB00IMG.zip installs is a good idea to prevent future disasters. The short method does not document either of these two steps.
Note #2: In any of these procedures, it is important to do so with A FULLY CHARGED PHONE. Do not let the phone sit idle for long periods of time in HBOOT, FASTBOOT, or RUU modes - even with the Eris plugged in to a USB port, in those modes it will discharge very rapidly - about two hours or so. That little green light is your friend.
- get fastboot on a PC working and communicating with the phone in its' current state (with the phone in fastboot mode or RUU mode). Doubtful if I will reply to inquiries about Windows and driver installs - it's covered in gory detail all over the place. Same goes with getting a copy of "fastboot.exe" for windows. (Google is your friend).
- Install the "rom.zip" file for the 1.51.0000 bootloader, (Rename to PB00IMG.zip and install it by booting the phone into HBOOT mode**)
- register with htcdev.com for unlocking this new Eris bootloader & follow the bootloader unlocking instructions (you can skip downloading & running the RUU, as you have installed the bootloader already)
- create a zip file with a custom recovery image in it (named "recovery.img"), and an "android-info.txt" file with MainVer set to 2.42.0000 (see step #3 of this XDA post).
- using fastboot and the phone in RUU mode, flash this zip file ("fastboot flash zip zipfilename.zip") Again, see step #3 of the link above.
- power off the phone and boot into the custom recovery and flash the ErisMiscReset_v0.9.zip file (watch for any errors - stop if you see errors!).
- in the same recovery session flash the MTD_Inspect_v0.9.zip file and determine if you have massive (bad block) corruption in any of /boot, /system, or /data. (See instructions here)
- If the above mentioned partitions only have one or two bad blocks, skip the next step.
- Flash (in recovery) ErisMTDNuke_v0.9.zip
- Re-lock the 1.51.0000 bootloader (phone in fastboot mode) with "fastboot oem lock"
- Flash the Eris Root ROM (from shipped-roms.com), using the HBOOT+PB00IMG.zip install method. The objective of this step is primarily to get rid of the 1.51.0000 bootloader, and install the 1.49.2000 S-OFF bootloader. Note this will stomp on your custom recovery (unless you use the battery pull trick), but that's OK.**
- get the custom recovery back onto the phone - using either the standard Eris rooting tools (Dummies or One-Click), or simply flash it using fastboot (e.g. "fastboot flash recovery recovery-RA-eris-v1.6.2.img")
- one last time: in the custom recovery, flash the ErisMiscReset_v0.9.zip file
- Install a ROM and be happy.
** after using any PB00IMG.zip file, it is a really good idea to rename it ASAP, so that you don't accidentally re-install it by inadvertently powering up the phone in HBOOT mode.
bftb0

not much to add. if the notion of downloading the sdk,installing fastboot,adb,etc. is a bit overwhelming you can use this file: http://www.mediafire.com/?hzf1u4bowjewhdq it contains adb and fastboot,and a utility called md5sums,and the needed files to make them work.
simply download,extract(unzip),and place the extracted folder onto the root of the C drive on your PC.
open a command window in windows 7 by clicking the start bubble,and type "command" in the search box. i believe xp is the same,or similar.
once you have a small,black command window open,you can change to the "mini-adb" directory by typing this command:
Code:
cd c:\mini-adb
you can call that folder anything you want,but when you "cd" to it,you must type the exact name the folder is called.
for drivers to get the eris recognized by the PC,you can install htc sync,or use these modified htc drivers from revolutionary public wiki
just holler if you have any questions with any of the above

i got several stuck at 1.49.000000 s on . i dont know if they have the stock recovery on them or not . does have fastbootusb though and hboot

highhacker said:
i got several stuck at 1.49.000000 s on . i dont know if they have the stock recovery on them or not . does have fastbootusb though and hboot
Click to expand...
Click to collapse
Hopefully we can fix them. Do you have any questions to get started?

wrong nv items wont boot or boot into recovery
Hey guys this phone is on an endless bootloop. I installed the 1.51. hboot unlock the bootloader, flash aman recovery 1.6.2 via Ruu successfully but when I try to boot into recover it continues to bootloop. I already install recovery via hboot but no success. I am willing to try anything with this phone for educational purposes for I dont need the phone but is something that I started over a year ago when I did the mistake with the wrong NV items. I can successfully follow all the step until step 4 but when is time to boot recovery it simply wont or any other file. Tried via regular FASTBOOT recovery.img but no luck. I Still have the S-ON on hboot 1.51. Any suggestions????

@obonilla30
obonilla30 said:
Any suggestions????
Click to expand...
Click to collapse
I started a reply and then saw that you were communicating with the right folks over on Android Forums. I was going to send you to exactly the same thread that you found.
If I may make a suggestion - both your posts here and also over there at AF leave quite a bit open to interpretation. For instance, when you mention "bootlooping", you didn't say whether this was for entering recovery from a coldstart (Vol-Up+End/Power), or via navigating from either Fastboot mode (Send+End/Power) or HBOOT mode (Vol-Down+End/Power), and then traversing the menus there to boot the recovery partition. It might be that you tried all three - but you didn't say so. Slow down a little bit and fill in as much detail as you can.
There are TWO methods suggested over in that AF thread - one is to flash (w/ unlocked 1.51 bootloader in RUU mode) a custom recovery to the recovery partition, and the other is to flash a stripped-down version of the (custom) recovery to the boot partition. (You could actually do both in the same flashing operation if you wanted - but note that you can't just rename one of the custom recovery images to "boot.img", because they are too big. But scary alien and scotty85 over there on AF put together something that will fit into the boot partition). That gives you two different ways to get a privileged execution environment running.
cheers
bftb0
PS Not to rehash old painful memories, but do you recall what exactly it was you did when you "did the mistake with the wrong NV items"?

S###
scotty1223 said:
Hopefully we can fix them. Do you have any questions to get started?
Click to expand...
Click to collapse
Well these "steps" got me no where . First step was put the hboot on my sd card and boot into hboot . still have Hboot 1.49.0000 (PB0010000) S-ON ((( That don't work . I got a box full of eris all 1.49.0000 s-on that show some kind of semi recovery on them where i can flash an update.zip and clear to factory .etc.. Still all stuck on three green androids.. Not very good with adb on pc but tried it in fastbootusb mode on phone and gave the command fastboot flash zip zipfilename.zip (my zip) and said remote not allowed . I have 15 tabs up on firefox and is just too much back and forth . is there a Dummy guide

highhacker said:
Well these "steps" got me no where . First step was put the hboot on my sd card and boot into hboot . still have Hboot 1.49.0000 (PB0010000) S-ON ((( That don't work . I got a box full of eris all 1.49.0000 s-on that show some kind of semi recovery on them where i can flash an update.zip and clear to factory .etc.. Still all stuck on three green androids.. Not very good with adb on pc but tried it in fastbootusb mode on phone and gave the command fastboot flash zip zipfilename.zip (my zip) and said remote not allowed . I have 15 tabs up on firefox and is just too much back and forth . is there a Dummy guide
Click to expand...
Click to collapse
You will always get "remote not allowed" with a S-ON bootloader, or with the 1.51.000 bootloader in the locked state. And you will probably also get that error even with a 1.51.0000 bootloader in an unlocked state if you try putting a "boot.img" or "recovery.img" file in the zip. Don't bother using fastboot with a 1.4x.00 S-ON bootloader - it doesn't ever work for anything useful.
Note also that the steps given above need to be performed in sequence and each step needs to succeed. There is no point in doing a 2nd or 3rd step if the first step fails.
As for the PB00IMG.zip install of the 1.51.0000 bootloader, when you boot the phone into HBOOT mode, you should see SOMETHING different happen - even if it is a failure of some sort - than how HBOOT behaves when there is no PB00IMG.zip file on the SD card. If the phone behaves identically whether or not you have the SD card in place, then that means you mis-spelled the name of the PB00IMG.zip file, or didn't put it in the top-level folder of the SD card. Even in the case where it is there on the card, but corrupted, you will see a different behavior of the HBOOT from when there is no PB00IMG.zip file present.
Unfortunately, your post above gives no details about this. That means that anybody that is willing to try and help you is forced to guess about what you are seeing your phone do.
bftb0

defiantely the first step is to get 1.51 onto the phone. in addition to the above,make sure that your sd card is formatted FAT32. i cant remember if this is important for the eris,but it is crucial for other dervices..
what you should see when a properly named PB00IMG file is placed on the root of the sd card,is a quick flash of green writing,then status bars on the upper right corner of the screen as the phone finds and checks the file,followd by a "do you want to update" prompt.
another common error with a PxxxIMG file on any devices,is that the decive must see PxxxIMG.zip. in the case of the eris,the file on the phone must be "PB00IMG.zip". the common error part comes from naming the file with windows. lots of folks will type in the .zip,forgetting that windows naturally adds and hides the file extension. therefore,typing in "PB00IMG.zip" actually names the file to "PB00IMG.zip.zip" in rarer cases,not typing in the ".zip" with windows if configured differently may end up in the file just being "PB00IMG" wish will not be found either.
so to recap
-check sd card for FAT32
-check the name of PB00IMG on the sd card. try adding or removing the ".zip"
-make sure PB00IMG is on the top level of the sd,not hidden inside a folder.
let us know how that goes
once you get the 1.51 hboot onto the phone,the next step is to unlock it. just holler if you have questions on htcdev's directions.

One of the simple mistakes that people make is when they rename the "rom.zip" file, they rename it as
PBOOIMG.zip (PB "oh-oh" IMG.zip)
instead of the correct spelling
PB00IMG.zip (PB "zero-zero" IMG.zip)
As scotty and I both pointed out, if you have a correctly named file on there in the top-level folder, you will see *something* different happen, even if the file is corrupted.
If you don't see something different happen, then the problem is the SD card format, a mis-spelling of the file name (I recall some people transferring files from their PCs, ending up with a file named "PB00IMG.zip.zip"), or the file is not in the top-level folder of the SD card.

bftb0 said:
You will always get "remote not allowed" with a S-ON bootloader, or with the 1.51.000 bootloader in the locked state. And you will probably also get that error even with a 1.51.0000 bootloader in an unlocked state if you try putting a "boot.img" or "recovery.img" file in the zip. Don't bother using fastboot with a 1.4x.00 S-ON bootloader - it doesn't ever work for anything useful.
Note also that the steps given above need to be performed in sequence and each step needs to succeed. There is no point in doing a 2nd or 3rd step if the first step fails.
As for the PB00IMG.zip install of the 1.51.0000 bootloader, when you boot the phone into HBOOT mode, you should see SOMETHING different happen - even if it is a failure of some sort - than how HBOOT behaves when there is no PB00IMG.zip file on the SD card. If the phone behaves identically whether or not you have the SD card in place, then that means you mis-spelled the name of the PB00IMG.zip file, or didn't put it in the top-level folder of the SD card. Even in the case where it is there on the card, but corrupted, you will see a different behavior of the HBOOT from when there is no PB00IMG.zip file present.
Unfortunately, your post above gives no details about this. That means that anybody that is willing to try and help you is forced to guess about what you are seeing your phone do.
bftb0
Click to expand...
Click to collapse
Well that was agood guess. The first step change rom.zip to PB00IMG.ZIP (I ASSUME THAT IS ZERO ZERO ) . it does somthing fast and i can see no image somthing like
Loading .....(PB00DIA0.zip)
no image
loading ......(PB00DIA3.zip)
no image
loading ......(PB00DIA2.ZIP)
no image or wrong image
. i have to keep flipping between fastboot and hboot to try and read what it says . basically it goes for another 5 or 6 lines with no image or wrong image ..
tried re downloading rom.zip and renaming it againg . same srrors..

have you tried renaming "PB00IMG" without the zip?
you can also try flashing it as an RUU,wich eliminates the sd card,and the name of the file from the equation.
place rom.zip(for 1.51 hboot) into the folder containing fastboot and hboot..
-place the phone in fastboot.
-assuming you leave rom.zip named "rom.zip",open a cmd window and enter the following:
fastboot oem rebootRUU
fastboot flash zip rom.zip
it will do some stuff on the screen,then say "finished". then:
fastboot reboot-bootloader
thaT should boot you back into fastboot,where you should see 1.51.0000 locked hboot.
if you get a "failed" error instead of the above results,let us know what that error is and we can hopefully figure out what to do to make the flash work
if you get the 1.51 hboot,next step is to unlock it

highhacker said:
Well that was agood guess. The first step change rom.zip to PB00IMG.ZIP (I ASSUME THAT IS ZERO ZERO ) . it does somthing fast and i can see no image somthing like
Loading .....(PB00DIA0.zip)
no image
loading ......(PB00DIA3.zip)
no image
loading ......(PB00DIA2.ZIP)
no image or wrong image
. i have to keep flipping between fastboot and hboot to try and read what it says . basically it goes for another 5 or 6 lines with no image or wrong image ..
tried re downloading rom.zip and renaming it againg . same srrors..
Click to expand...
Click to collapse
The behavior you describe is EXACTLY how HBOOT mode behaves ... when there is no file named PB00IMG.zip on the root folder of the SD card. When I said "you will see something different happen", what I meant is something in addition to that list of file names rapidly scrolling by.
No doubt you are finding this frustrating.
In the past, there were two other reasons why this occurred:
1) People were using Windows Explorer on the PC. By default, it has an option turned on which is something like "hide file name extensions of known file types". With this (default) behavior, it is possible to rename the file PB00IMG.zip.zip, and yet what would be seen on-screen in Windows Explorer would only be "PB00IMG.zip". Turn that option off, or just use the DIR command from a command prompt to see if that is what happened.
2) Other users reported banging their heads into this without any luck, and then mysteriously solving the problem by formatting the SD card some other way than they previously had done. I don't have any further insight into the details here, other than this: the SD card should NOT be partitioned. If you got a box of phone which were previously rooted, it is possible you have a partitioned card (esp. if the phone had a 2.1 dev ROM on it)
The method scotty details above should allow you to side-step this problem, although you will have to get fastboot communicating with the phone (PC driver installs, etc).
To re-iterate though: if HBOOT discovers a file on the SD card named PB00IMG.zip, you will see something happen in addition to that list of file names rapidly scrolling by and disappearing. If you don't see anything additional - then HBOOT is not finding the file (for some reason or another).
bftb0

I am having an issue getting Amon recovery on my soft-bricked Eris.
I have the 1.51 bootloader unlocked but when I go to run the commands I get the following:
C:\adb>fastboot.exe flash zip recovery.zip
sending 'zip' (3817 KB)...
OKAY [ 0.827s]
writing 'zip'...
FAILED (remote: not allow)
finished. total time: 0.842s
If I try the RUU method it just sits at parsing:
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 2.980s]
finished. total time: 2.980s
C:\adb>fastboot flash zip recovery.zip
sending 'zip' (3817 KB)...
OKAY [ 0.842s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
Also running the RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe and replacing the rom.zip did not work or trying to flash Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP
The version it says I have it 2.42.0.0
Any ideas?
Thanks!

sorry it took me a couple days to reply to this. i believe the prollem your having is due to the android info document,specifically the hboot pre-update value. i had the same prollem starting in this post.
the android info i was using that was hanging at 'parsing' was:
Code:
ModelID: DESI****
ModelID: PB001****
ModelID: PB00100
CIDNUM: 11111111
CIDNUM: VZW__001
hbootpreupdate: 3
MainVer: 2.42.0.0
i pulled the one from the rom.zip extracted from the 1.51 hboot ruu and it worked fine.heres what it looked like:
Code:
CIDNUM:11111111
modelid: PB0010000
cidnum: VZW__001
cidnum: UTSI_001
mainver: 2.42.0.0
hbootpreupdate:12
try repacking your recovery with that android info,if its not what youre allready using.

zmanzbo,
What were the contents of the "recovery.zip" file you were trying to flash? (specifically, were there any .img files contained in it?)
Even when the 1.51.0000 bootloader is in the unlocked state, the flash will be disallowed if you have certain .img files in there (radio.img or recovery.img iirc - but don't quote me on that, I would need to go and re-read scotty's notes over in the AF thread).
Apologies for the vagueness - I'm afk at this time and am typing this from my phone.
bftb0

Well I got it working. I went to the link Scotty posted and downloaded tiny rescue recovery flashed that and then was able to run the various files listed in the original post bu bftb0. After that I was able to flash Eris_RootROM_v2.19.605.1_PB00IMG.zip. I am back in business now.
What was weird is that the contents of my recovery.zip were just the recovery.img and android-info.txt. The android-info.txt file had the same info as the 2nd one Scotty posted.
Thanks alot for the help here. Really appreciate it!
Cheers!

cool.
I'm glad you put the 1.49.2000 S-OFF bootloader on the phone afterward. It is always a good idea to have that bootloader (rather than the 1.51.0000 "unlockable" bootloader) installed, as the ways in which rescue/repair can be performed are more numerous (in case anything goes wrong in the future).
bftb0

[Q] Is my rezound done for?

So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!

SHIDOOBY said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!
Click to expand...
Click to collapse
If you are s-on, it is nearly impossible to be "done for". Probably user error (no offense) but you probably had a file named incorrectly or it didn't flash properly. I just got to work and can't really help you right now, but i know someone can. Just don't worry, you'll be fine. Like i said, it's far from "done for".

tCizler said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
Click to expand...
Click to collapse
Easy fix.
If you don't have the ROM on your computer anymore, download it again. Extract it and copy the boot.img to your ADB directory (if you don't have ADB, you need to get it lol.) Plug your phone into your computer, then just boot your phone into your bootloader, go into recovery, wipe everything 3X to be safe. Install the ROM, reboot into bootloader (make sure you're in fastboot USB mode.) Open up command prompt, CD to your ADB directory and type in fastboot flash boot boot.img. Reboot, and enjoy. If you have any issues, let me know.

In addition to Chyrux's useful post, I'd recommend keeping backups of your phone's storage on PC and possibly cloud storage.
If you got the time, or a spare SD card to get phone running in the meantime, might want to try a recovery program to get those nandroid backups and files off the SD card. I'd suggest Piriform Recuva for Windows, use the Deep Scan option.

I used to have ADB but don't anymore and downloaded the "noob proof" thing that allows you to do everything. Although you can't really use it without your phone turning on. When I press the volume down button it tries to install a kernel and said "Main Version Old" and makes me press the power button to reboot. I do have Amon Ra installed. I haven't really messed with the whole phone thing in awhile and have tried to educate myself by reading and reading and am a bit of a perfectionist. I don't know where I went wrong.
-I do know that I am on the new firmware w/ ICS
-I do know that Amon Ra is installed.
-I don't have a backup because everything seems to have been deleted.
-I suppose something went wrong during the installation process with RezRom S4 2.5
-I currently have no idea what I am doing. I am not stupid, nor do I expect handouts. I am fully capable of reading threads and usually fixing all my problems on my own. But, without a backup and me not being completely familiar with adb and my phone stuck on a white htc screen it makes me a bit timid to do anything else without some direction.

SHIDOOBY said:
I used to have ADB but don't anymore and downloaded the "noob proof" thing that allows you to do everything. Although you can't really use it without your phone turning on. When I press the volume down button it tries to install a kernel and said "Main Version Old" and makes me press the power button to reboot. I do have Amon Ra installed. I haven't really messed with the whole phone thing in awhile and have tried to educate myself by reading and reading and am a bit of a perfectionist. I don't know where I went wrong.
-I do know that I am on the new firmware w/ ICS
-I do know that Amon Ra is installed.
-I don't have a backup because everything seems to have been deleted.
-I suppose something went wrong during the installation process with RezRom S4 2.5
-I currently have no idea what I am doing. I am not stupid, nor do I expect handouts. I am fully capable of reading threads and usually fixing all my problems on my own. But, without a backup and me not being completely familiar with adb and my phone stuck on a white htc screen it makes me a bit timid to do anything else without some direction.
Click to expand...
Click to collapse
Lol I feel your pain. I don't have an SD card reader, so situations like this usually blew. But, there's a bright side: you have an internal storage unit. Let's try something basic. Take out your SD card and plug your phone into your computer. Reboot into your recovery and mount your USB storage. Tell me if you can see your internal and can access it.

So this is where I get stuck at; I appreciate that idea and will try it shortly (at work at the moment). I basically have no access with my computer and phone via usb because i am unable to get past hboot.
2 things happen as of right now:
-I press the power button and it sits at the HTC white screen forever
-I hold volume down and the power button and it tries to flash a kernel and says my Main Version is old. (When in fact, I know I did the MainVer fix while back; frustrating)
So with those 2 things only happening, is your suggestion still to yank out the external? I wish I had a microSD reader to wipe it and put a new rom on there and then figure out how to access amon ra and get passed this mess.
I took 2 min off work to yank the card out(the external, that is) -- I was able to reach recovery. I went into the mounting section of Amon Ra where I was able to see /sd-ext and /sdcard, both of which I got the message. "E: Can't mount /dev/block/mmcblk1p1) (No such file or directory)

Chyrux said:
Lol I feel your pain. I don't have an SD card reader, so situations like this usually blew. But, there's a bright side: you have an internal storage unit. Let's try something basic. Take out your SD card and plug your phone into your computer. Reboot into your recovery and mount your USB storage. Tell me if you can see your internal and can access it.
Click to expand...
Click to collapse
And for that matter, I have gotten in the habit of lifting my battery out at an angle, pressed into the contacts still to remove and insert my SD card on the fly for when I get these lingering PH98IMG.zip files. Pop out, go to recovery with a ninja grip on phone, and pop SD in lol.
I know Amon Ra Revamped 3.15 recovery has an option to delete those zips.
http://forum.xda-developers.com/showthread.php?p=23169557
Need to try reflashing that zip again in recovery perhaps, maybe RUU undid your Misc partition Mainver fix.
In any case... What your white bootloader screen says would help troubleshoot.
(Sorry for constant edits)

When you flash a new kernel the mainver is changed to what that kernel's is. I'd it's a newer number then when you try to flash something with a older number it won't flash. So every time you flash a kernel it is a good idea to go ahead and redo the main version fix
Sent from my ADR6425LVW using Tapatalk 2

*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT 2.21. 0000
RADIO-1.2.22.10. 0310r/1.22.10.0308r
OpenDSP-v13.6.0.7611.00.0104
eMMC-Boot
Mar 11 2012,22:16:16
HBOOT
<VOL UP> to previous menu
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
- How would I flash the Mainver fix when I can't even communicate with my computer through usb?
- Would adb help(I haven't used in a LONG time)
- I'm sitting at the screen I just took about 20 min to type out up above.

The white screen text I showed you was without the external sd card in. I feel like the only solution right now is to buy another external SD card.. put a rom on it, and then flash it... maybe that's the solution since I can't access this SD card and it seems to be ****ed with a mainver problem? Although, even with a new SD card I don't know how I would flash the mainver fix?

SHIDOOBY said:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT 2.21. 0000
RADIO-1.2.22.10. 0310r/1.22.10.0308r
OpenDSP-v13.6.0.7611.00.0104
eMMC-Boot
Mar 11 2012,22:16:16
HBOOT
<VOL UP> to previous menu
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
- How would I flash the Mainver fix when I can't even communicate with my computer through usb?
- Would adb help(I haven't used in a LONG time)
- I'm sitting at the screen I just took about 20 min to type out up above.
Click to expand...
Click to collapse
Okay, you are following the guide of the RezROM to a tee I take it. Have to ask which AmonRa version did you install? I got the same mounting errors once and had to re-flash the recovery to AmonRa 3.14 to detect the mount points properly.
And yes, should be able to use fastboot commands with ADB to push the recovery, the Mainver fix, etc. That is the key communication tool you have barring any other access in your situation.
I'm am not anywhere remotely close to a PC and a bit rusty too, will try and find the ADB commands for that.

PhantasmRezound said:
Okay, you are following the guide of the RezROM to a tee I take it. Have to ask which AmonRa version did you install? I got the same mounting errors once and had to re-flash the recovery to AmonRa 3.14 to detect the mount points properly.
And yes, should be able to use fastboot commands with ADB to push the recovery, the Mainver fix, etc. That is the key communication tool you have barring any other access in your situation.
I'm am not anywhere remotely close to a PC and a bit rusty too, will try and find the ADB commands for that.
Click to expand...
Click to collapse
Those lines I typed were without the SD card in the actual phone. I did install the newer version of AmonRa (3.15 for ICS and GB) In the actual recovery with the External SDcard out I did some scoping around where you're able to delete the kernel install, but that would leave me still with a broken phone. I need to be able to access my SD card and put a new rom on it i'm guessing? I don't even know what the **** I'm doing anymore.

wow.
put THIS file on your sd card. then do the update in HBOOT. once your are back up and running flash the main version fix. then get s-off

*EDIT* just saw where you can go into recovery. Okay. Here comes the fun part. I'm not well-versed in the mainver issue and this method can brick your phone, so be careful. Just what I have for now.
Start by having your SD card out (but on your desk, just make sure you have it lol.) Boot up your phone into the bootloader and go to where you can access your recovery, but don't. Here's where you can brick your phone. Pop out your battery and leave the cable plugged in (you'll have power still going to your phone.) Now, put your SD card back in and put your battery back in as well. Boot into your recovery and mount USB storage. From there, delete the update file using My Computer.

SHIDOOBY said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!
Click to expand...
Click to collapse
Delete the PH98IMG.zip off your sdcard, download and flash THIS and then try flashing the rom and kernel again. should work. Worked for me.
try this link: http://forum.xda-developers.com/show...57&postcount=4

tmettler5 said:
Delete the PH98IMG.zip off your sdcard, download and flash THIS and then try flashing the rom and kernel again. should work. Worked for me.
try this link: http://forum.xda-developers.com/show...57&postcount=4
Click to expand...
Click to collapse
I think his issue is that he can't access his SD card because he doesn't have a reader/other device to use.

Ah... That makes sense. Maybe another sdcard, then? I'll put the set mainver low file in the dropbox later today and send a link. If you can use a second sd card and put it on that he can fix it. I think.
Sent from my ADR6425LVW using XDA

tmettler5 said:
Ah... That makes sense. Maybe another sdcard, then? I'll put the set mainver low file in the dropbox later today and send a link. If you can use a second sd card and put it on that he can fix it. I think.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Nah, he won't have to. Granted, my method is a bit...unsafe lol, but it worked fine for me. he just has to be careful and he'll be able to take the file off. Glad you have the fix cause I don't, though. So hopefully my trick will work and then he can use the fix.

If you get to the point where you can get into recovery, flash this: http://dl.dropbox.com/u/79523435/SetMainVersionLOW.zip
Then flash your rom and kernel as per normal.

[Q] Rezound - bricked or worse - looking for guidance (noob)

So while trying to update to ICS my fingers were working faster than my brain (yes, it happens) and I selected a menu option while using Clockwork and, while I'm not sure, I think the option said something like, "format .. OS...something..." before I could fully read it (and stop my finger from pressing the power button), I pressed the power button.
The phone rebooted, got to the white HTC screen and stopped - stuck on the white HTC screen. I pulled the battery.
I Held down power and up-volume and got to the bootloader menu, selected recovery and Clockwork came up.
Couldn't "Recover" because it couldn't mount the SD card.
Couldn't mount the external SD card either.
Ok - tried a factory reset - Rebooted - up came the white HTC screen where it stays until I pull the battery.
I'm new at this (probably didn't need to say that, but...).
How Do I get past this point?
Is this phone agonner?
How do I load (anything) to the phone at this point?
Thanks in advance! I appreciate it.

MilesTHD said:
So while trying to update to ICS my fingers were working faster than my brain (yes, it happens) and I selected a menu option while using Clockwork and, while I'm not sure, I think the option said something like, "format .. OS...something..." before I could fully read it (and stop my finger from pressing the power button), I pressed the power button.
The phone rebooted, got to the white HTC screen and stopped - stuck on the white HTC screen. I pulled the batter.
I Held down power and up-volume and got to the bootloader menu, selected recovery and Clockwork came up.
Couldn't "Recover" because it couldn't mound the SD card.
Couldn't mound the external SD card either.
Ok - tried a factory reset - Rebooted - up came the white HTC screen where it stays until I pull the battery.
I'm new at this (probably didn't need to say that, but...).
How Do I get past this point?
Is this phone agonner?
How do I load (anything) to the phone at this point?
Thanks in advance! I appreciate it.
Click to expand...
Click to collapse
Try using adb commands from your computer to push a recovery to your phone and go from there
Sent from my ADR6425LVW using xda app-developers app

If it powers on, you're not bricked.
Are s-on or s-off?
Make sure you have a card reader for the following.
The best thing for you to do would probably to flash an RUU.
First, download the latest RUU.
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
If you are s-on with unlocked boot loader, relock it:
Make sure there is no PH98IMG.ZIP on your sdcard. Delete if there is one.
Power off phone completely with battery pull.
Plug in phone to computer with USB.
Go to the bootloader menu with vol down + power.
Select fastboot.
On your computer, run the following fastboot command (do whatever you needed to do to use fastboot):
fastboot oem lock
After that is done, time to install the RUU.
Find the RUU you downloaded and put it on your sdcard, then rename to PH98IMG.ZIP
Put sdcard back, then power on to bootloader.
It should now scan for the PH98IMG and then ask you to install it.
Follow all the instructions to install it.
After you finish this, you will be back to the stock ROM with a locked boot loader.
If either s-off or s-on locked bootloader
Sent from my HTC Rezound using Tapatalk 2

Rezound still major messed up
THANK YOU for your help, I really appreciate your response. I followed your instructions and once the PH98IMG.zip file was on the SD card I loaded bootloader and it did scan for the file, but said "no file or wrong file!" Well, the file is there so I know its not "no" file. I've tried a couple of different PH98IMG files that I found on XDA but I guess the specific file wasn't the problem.
After it gives the error message it simple goes back to the bootloader and waits.
Unlocking the bootloader and then following your instructions did result in the file being seen and, what appeared to be, the installation process beginning - however when the phone reboots for the first time it just goes quiet and never comes back up. I waited for at least 20 minutes before I decided it wasn't just a long boot process.
I"m pretty sure there is NOTHING on this phone. I've verified there's nothing on the SD card besides the PH98IMG.zip file. Assuming I've completely wiped out the OS (and it is not on the phone) is the method you've outlined the right starting point?
Thanks again, and Merry Christmas
Miles
wlmeng11 said:
If it powers on, you're not bricked.
Are s-on or s-off?
Make sure you have a card reader for the following.
The best thing for you to do would probably to flash an RUU.
First, download the latest RUU.
If you are s-on with unlocked boot loader, relock it:
Make sure there is no PH98IMG.ZIP on your sdcard. Delete if there is one.
Power off phone completely with battery pull.
Plug in phone to computer with USB.
Go to the bootloader menu with vol down + power.
Select fastboot.
On your computer, run the following fastboot command (do whatever you needed to do to use fastboot):
fastboot oem lock
After that is done, time to install the RUU.
Find the RUU you downloaded and put it on your sdcard, then rename to PH98IMG.ZIP
Put sdcard back, then power on to bootloader.
It should now scan for the PH98IMG and then ask you to install it.
Follow all the instructions to install it.
After you finish this, you will be back to the stock ROM with a locked boot loader.
If either s-off or s-on locked bootloader
Sent from my HTC Rezound using Tapatalk 2
Click to expand...
Click to collapse

MilesTHD said:
THANK YOU for your help, I really appreciate your response. I followed your instructions and once the PH98IMG.zip file was on the SD card I loaded bootloader and it did scan for the file, but said "no file or wrong file!" Well, the file is there so I know its not "no" file. I've tried a couple of different PH98IMG files that I found on XDA but I guess the specific file wasn't the problem.
After it gives the error message it simple goes back to the bootloader and waits.
Unlocking the bootloader and then following your instructions did result in the file being seen and, what appeared to be, the installation process beginning - however when the phone reboots for the first time it just goes quiet and never comes back up. I waited for at least 20 minutes before I decided it wasn't just a long boot process.
I"m pretty sure there is NOTHING on this phone. I've verified there's nothing on the SD card besides the PH98IMG.zip file. Assuming I've completely wiped out the OS (and it is not on the phone) is the method you've outlined the right starting point?
Thanks again, and Merry Christmas
Miles
Click to expand...
Click to collapse
If you are S-on and have an unlocked bootloader, you will need to relock it before attempting to flash an ruu. Once re-locked, ensure that the PH98IMG is not a zip file within a zip file which is how they are usually uploaded. Attempt to unzip the files until it will not unzip anymore. That file that won't unzip needs to be the one you rename as PH98IMG and placed on the root of your SD card. Reboot to bootloader and allow it to scan. It will ask you if you wish to proceed and you will allow it. After some time it will reboot back to bootloader to flash radios and the rest of firmware. After that process and a 2nd reboot you should he back to stock, locked, and unrooted.
Sent from my Rezound using xda premium

Also, it could be possible that your phone can't recognize the sd card so it needs to be formatted.
Sent from my HTC Rezound using Tapatalk 2

zip file contents?
Maybe I should ask what the contents of the .zip file should be? I did check the zip to make sure it wasn't a double-zip. There were two versions of the PH98IMG file i tried. One had the file (imagemate-3.60.exe) the other had the file(s) (boot.img and android-info.txt).
I did "relock" the bootloader prior to trying and it would not recognize the file. When it was unlocked it would see it, start the install process, then go quiet. So that at least tells us that the file is there and likely workable.
I can't seem to get past the "No image or wrong image" message. I've tried on 3 different cards (the original and two fresh cards) and I've checked to ensure the zip is not a zip within a zip.
IAmTheOneTheyCallNeo said:
If you are S-on and have an unlocked bootloader, you will need to relock it before attempting to flash an ruu. Once re-locked, ensure that the PH98IMG is not a zip file within a zip file which is how they are usually uploaded. Attempt to unzip the files until it will not unzip anymore. That file that won't unzip needs to be the one you rename as PH98IMG and placed on the root of your SD card. Reboot to bootloader and allow it to scan. It will ask you if you wish to proceed and you will allow it. After some time it will reboot back to bootloader to flash radios and the rest of firmware. After that process and a 2nd reboot you should he back to stock, locked, and unrooted.
Sent from my Rezound using xda premium
Click to expand...
Click to collapse

MilesTHD said:
Maybe I should ask what the contents of the .zip file should be? I did check the zip to make sure it wasn't a double-zip. There were two versions of the PH98IMG file i tried. One had the file (imagemate-3.60.exe) the other had the file(s) (boot.img and android-info.txt).
I did "relock" the bootloader prior to trying and it would not recognize the file. When it was unlocked it would see it, start the install process, then go quiet. So that at least tells us that the file is there and likely workable.
I can't seem to get past the "No image or wrong image" message. I've tried on 3 different cards (the original and two fresh cards) and I've checked to ensure the zip is not a zip within a zip.
Click to expand...
Click to collapse
One thing you need to know is that a PH98IMG file can be many things. It is only the name of a file that your phone looks for to use when booted into hboot. So it can be a kernel, an entire RUU (OS), a custom recovery or ROM... basically anything. It just means that item was packed into a PH98IMG file in order to run automatically off your SD card when the phone boots.
So you need to know what the PH98IMG file is that you are using or you might flash something you don't want that can possibly cause your phone to not work properly. In your examples above one is a kernel (boot.img) and I have no idea what imagemate-3.60.exe is. It sounds like you have not had the correct file.
Here is the global RUU you should run to get you back to stock with all the latest radios and firmware:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
You need to be locked to run it so if you are S-ON, which it sounds like you are (don't remember if you mentioned that before), you need to use fastboot from your pc to do that, just like you did when you unlocked it with this command:
fastboot oem lock
***If you are S-OFF you should be locked again from that process already. But if you are S-OFF then confirm with someone to be sure it's safe to run the RUU, there's something about not relocking if you are on a certain hboot or you can brick it or something...***
Then put the RUU on your SD card and reboot the phone. Let it run through the RUU a few times because apparently it needs to do it a few times to get all the system files. Afterwards, if you want to root again and flash a custom ROM you will need to unlock again and flash a custom recovery and reroot.

It Works!
Not that I'm going to give you all the credit, because everyone kinda chipped in - however you DID provide the ONLY correct link to exactly what I needed! LORDY there are a lot of bad links being passed around. THANK YOU Ms. Feralicious, I totally appreciate your help.
... Everyone else as well - very generous with your knowledge and time and I will always love you.
Merry Christmas! Have a safe new year as well!
Miles
feralicious said:
One thing you need to know is that a PH98IMG file can be many things. It is only the name of a file that your phone looks for to use when booted into hboot. So it can be a kernel, an entire RUU (OS), a custom recovery or ROM... basically anything. It just means that item was packed into a PH98IMG file in order to run automatically off your SD card when the phone boots.
So you need to know what the PH98IMG file is that you are using or you might flash something you don't want that can possibly cause your phone to not work properly. In your examples above one is a kernel (boot.img) and I have no idea what imagemate-3.60.exe is. It sounds like you have not had the correct file.
Here is the global RUU you should run to get you back to stock with all the latest radios and firmware:
You need to be locked to run it so if you are S-ON, which it sounds like you are (don't remember if you mentioned that before), you need to use fastboot from your pc to do that, just like you did when you unlocked it with this command:
fastboot oem lock
***If you are S-OFF you should be locked again from that process already. But if you are S-OFF then confirm with someone to be sure it's safe to run the RUU, there's something about not relocking if you are on a certain hboot or you can brick it or something...***
Then put the RUU on your SD card and reboot the phone. Let it run through the RUU a few times because apparently it needs to do it a few times to get all the system files. Afterwards, if you want to root again and flash a custom ROM you will need to unlock again and flash a custom recovery and reroot.
Click to expand...
Click to collapse

Followed these directions & update fails...Please help.
Have PH98IMG.zip on sd card.
Gets this far...
*** LOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
eMMC-boot
HBOOT
Parsing...[SD ZIP]
[1]...
...[18]
...start update?
<VOL UP>
Next to "[1] BOOTLOADER" "- Fail-PU"
And below [18]..., "Partition update fail!"
"Update Fail!"
"Press <POWER> to reboot."
It's an HTC Rezound I'm trying to get back to stock, Verizon.
Any ideas?

It's locked which means it's never been unlocked and it's s-on. A simple factory reset within the rom itself will suffice
Sent from my Rezound using xda premium

rut-row...running rezound reset from rom repeatedly ravaging me :-O
IAmTheOneTheyCallNeo said:
It's locked which means it's never been unlocked and it's s-on. A simple factory reset within the rom itself will suffice
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
When running rom, ...
"RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9
K_release_270509_signed.exe" ...
ends in usb error 170...
Anyone having any pointers for me will be worshiped indefinately!
Thank-You and I'm-not-worthy, in advance,
Tom

screen shots
TommyJames said:
When running rom, ...
"RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9
K_release_270509_signed.exe" ...
ends in usb error 170...
Anyone having any pointers for me will be worshiped indefinately!
Thank-You and I'm-not-worthy, in advance,
Tom
Click to expand...
Click to collapse
attached error window pic.

TommyJames said:
attached error window pic.
Click to expand...
Click to collapse
Try putting the PH98IMG.ZIP on your sdcard manually.
Sent from my HTC Rezound using Tapatalk 2

TommyJames said:
When running rom, ...
"RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9
K_release_270509_signed.exe" ...
ends in usb error 170...
Anyone having any pointers for me will be worshiped indefinately!
Thank-You and I'm-not-worthy, in advance,
Tom
Click to expand...
Click to collapse
Not sure what you're trying to do there, run an RUU?
Did you try a factory reset from the settings of the phone as Neo suggested?
Settings > Storage > Factory data reset
But back up anything you want to save such as pics, settings, etc... it will wipe everything.

same thing happens...
TommyJames said:
Have PH98IMG.zip on sd card.
Gets this far...
*** LOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
eMMC-boot
HBOOT
Parsing...[SD ZIP]
[1]...
...[18]
...start update?
<VOL UP>
Next to "[1] BOOTLOADER" "- Fail-PU"
And below [18]..., "Partition update fail!"
"Update Fail!"
"Press <POWER> to reboot."
It's an HTC Rezound I'm trying to get back to stock, Verizon.
Any ideas?
Click to expand...
Click to collapse
same thing happens...

TommyJames said:
same thing happens...
Click to expand...
Click to collapse
You still needing help?
Where did you get the PH...img file you are using? Are you sure it's an RUU?
Did you ever try resetting to factory settings within the phone? You don't need to RUU for that, check a few posts up on where to find the setting.

[Q] RUU to 4.3 results in white HTC screen

Hi,
I see a few people have run into the endless white HTC boot screen problem and it seems the fix is to just run the RUU again - this isn't working for me. I came from 100% stock with the latest OTA and everything. I've applied the RUU more than 10 times at this point from different computers, it's always successful and the most frustrating part is that the RUU can read the proper version from my phone (it says "upgrade from 4.13.651.3 to 4.13.651.3").
I also tried to go back to 3.15.651.16 with the RUU, but it stops with an hboot incompatible error.
Any ideas?

Have you tried just rebooting phone when it gets stuck, I've had a few roms stick on splash and after a minute or so I just force a reboot. I know it sounds odd but that's what I've always done rather then reflash the rom and after a reboot or 2 it comes up. You can also try holding volume down on the splash, it forces the rom to boot in safe mode.
Sorry I thought you mean after ruu instead of during. You can try reinstalling htc drivers and connecting it in fastboot first, it will force windows to install the drivers that might otherwise not install. Also viperuu has been said to work with the new hboot.

nehpets11 said:
Hi,
I see a few people have run into the endless white HTC boot screen problem and it seems the fix is to just run the RUU again - this isn't working for me. I came from 100% stock with the latest OTA and everything. I've applied the RUU more than 10 times at this point from different computers, it's always successful and the most frustrating part is that the RUU can read the proper version from my phone (it says "upgrade from 4.13.651.3 to 4.13.651.3").
I also tried to go back to 3.15.651.16 with the RUU, but it stops with an hboot incompatible error.
Any ideas?
Click to expand...
Click to collapse
Have you tried running the update files as PJ75IMG.zip files from an external SD card? It'll require running the RUU .exe file until it opens to the first screen with the device icon on it. Then navigating to your OS temp folder (usually by clicking "Run" and typing %TEMP% to open the folder). Then you find the newest folder and inside one of them will be some rom_01 and rom_02 zip files. Those are what you need. Those can be renamed to PJ75IMG.zip, placed on external SD card and flashed through HBOOT. Hopefully doing them that way will get them to apply correctly.

Thanks for the replies, I appreciate the help!
om4 said:
Have you tried just rebooting phone when it gets stuck, I've had a few roms stick on splash and after a minute or so I just force a reboot. I know it sounds odd but that's what I've always done rather then reflash the rom and after a reboot or 2 it comes up. You can also try holding volume down on the splash, it forces the rom to boot in safe mode.
Sorry I thought you mean after ruu instead of during. You can try reinstalling htc drivers and connecting it in fastboot first, it will force windows to install the drivers that might otherwise not install. Also viperuu has been said to work with the new hboot.
Click to expand...
Click to collapse
You were correct, it was after the ruu runs successfully that the white HTC screen sticks. I tried the multiple reboots, but still no luck.
Captain_Throwback said:
Have you tried running the update files as PJ75IMG.zip files from an external SD card? It'll require running the RUU .exe file until it opens to the first screen with the device icon on it. Then navigating to your OS temp folder (usually by clicking "Run" and typing %TEMP% to open the folder). Then you find the newest folder and inside one of them will be some rom_01 and rom_02 zip files. Those are what you need. Those can be renamed to PJ75IMG.zip, placed on external SD card and flashed through HBOOT. Hopefully doing them that way will get them to apply correctly.
Click to expand...
Click to collapse
I got the files, but sorry, I'm a little unsure of which one to rename to PJ75IMG.zip or what order to flash them in.
I also spoke with HTC support for a while, but that didn't really help other than them promising that the "Special Projects" team would call me in the next 7-10 days...
I was perfectly fine with it wiping my data as 99% of it is in the cloud anyway, but I certainly didn't expect the official update to put my phone into this state.

nehpets11 said:
Thanks for the replies, I appreciate the help!
You were correct, it was after the ruu runs successfully that the white HTC screen sticks. I tried the multiple reboots, but still no luck.
I got the files, but sorry, I'm a little unsure of which one to rename to PJ75IMG.zip or what order to flash them in.
I also spoke with HTC support for a while, but that didn't really help other than them promising that the "Special Projects" team would call me in the next 7-10 days...
I was perfectly fine with it wiping my data as 99% of it is in the cloud anyway, but I certainly didn't expect the official update to put my phone into this state.
Click to expand...
Click to collapse
They are numbered, aren't they? Do 01 first, then 02. They will both get flashed the exact same way.

Thanks! I was not aware of that trick. Doing that led me down the path of seeing one of the images was corrupt. From there I did what I should have started with, I downloaded the RUU from HTC again. I got a file with the same byte size but a different MD5 signature. This file took much longer to run and successfully updated my phone!
The winning MD5 for those keeping track at home was: c6ac16fcdd39818f43158329ebdad957
Shame on me for not trying this as one of the first items, but shame on HTC for not validating their own images before pushing the update to the phone.

nehpets11 said:
Thanks! I was not aware of that trick. Doing that led me down the path of seeing one of the images was corrupt. From there I did what I should have started with, I downloaded the RUU from HTC again. I got a file with the same byte size but a different MD5 signature. This file took much longer to run and successfully updated my phone!
The winning MD5 for those keeping track at home was: c6ac16fcdd39818f43158329ebdad957
Shame on me for not trying this as one of the first items, but shame on HTC for not validating their own images before pushing the update to the phone.
Click to expand...
Click to collapse
Well at least you got it to run...lol I have the same MD5 and it wont run past the first screen. All other RUU's i have on my pc run just fine so im at a loss.

OK, I just followed links thru 3 diff of capns threads. Isn't there still a way to change partitions (properly) just doing it as a PJ75 zip, or is PC now required? As my access to one is limited and sketchy. Sorry for not keeping up better, been trying to maintain 3 devices, work full time and parent. And keep up with game of thrones. Lol. Either way, my apologies for not being as current as I usually am, and thanks yo any who respond.
Sent from my EVO 4G LTE using XDA Premium 4 mobile app

Hey, what's up, Scott? Yes, there are PJ75IMG.ZIPs floating around. I think that Yankees has a link in his thread. If you still have a hard time finding everything, I can upload mine and send you a PM.

Captain_Throwback said:
Have you tried running the update files as PJ75IMG.zip files from an external SD card? It'll require running the RUU .exe file until it opens to the first screen with the device icon on it. Then navigating to your OS temp folder (usually by clicking "Run" and typing %TEMP% to open the folder). Then you find the newest folder and inside one of them will be some rom_01 and rom_02 zip files. Those are what you need. Those can be renamed to PJ75IMG.zip, placed on external SD card and flashed through HBOOT. Hopefully doing them that way will get them to apply correctly.
Click to expand...
Click to collapse
If you have both files, why would you need to run the RUU at all, for starting purposes? Couldn't you just run both PJ75 zips and have nothing to do with .exe/PC?
And what should flash first, the ROM or FW (and yes, I know, capn, they're numbered,...that's NOT the answer I'm looking for, I'm trying to find answer that actually means something, as I'm trying to make sure I understand this process.)
Sent from my HTCONE using XDA Premium 4 mobile app

scottspa74 said:
If you have both files, why would you need to run the RUU at all, for starting purposes? Couldn't you just run both PJ75 zips and have nothing to do with .exe/PC?
And what should flash first, the ROM or FW (and yes, I know, capn, they're numbered,...that's NOT the answer I'm looking for, I'm trying to find answer that actually means something, as I'm trying to make sure I understand this process.)
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The purpose of running the RUU.exe is to extract the zip files. If you already have them, then you are correct, you have no need of running it.
I thought this was explained in my thread that has the firmware update, but maybe it isn't. The first zip is just the firmware which repartitions the device for the new layout, and the second zip is the actual ROM. The first zip and my firmware zip are essentially the same. That's why I have it listed as being required in order to flash the new format ROM.

Captain_Throwback said:
Have you tried running the update files as PJ75IMG.zip files from an external SD card? It'll require running the RUU .exe file until it opens to the first screen with the device icon on it. Then navigating to your OS temp folder (usually by clicking "Run" and typing %TEMP% to open the folder). Then you find the newest folder and inside one of them will be some rom_01 and rom_02 zip files. Those are what you need. Those can be renamed to PJ75IMG.zip, placed on external SD card and flashed through HBOOT. Hopefully doing them that way will get them to apply correctly.
Click to expand...
Click to collapse
Been awhile with this device. Sold it via Swappa. Customer cannot connect to Sprint network. Found that after she tries activating it she'd needs to reflash the RUU via a bunch of reading. She doesn't have a Win PC. So, this is my option I guess. So after pulling the 2 ROM files via the RUU, rename the 01 file to PJ75IMG.zip, placed on external SD card and flash through HBOOT....what is the process exactly in hboot? I don't remember. Thought you booted to hboot and it automatically finds and flashes? Then....do you power down/reboot/can you access sd remotely while in hboot to rename 02 file to PJ75IMG.zip, and flash? Thanks for any input. It's hard cause I don't have the device.

gokart2 said:
Been awhile with this device. Sold it via Swappa. Customer cannot connect to Sprint network. Found that after she tries activating it she'd needs to reflash the RUU via a bunch of reading. She doesn't have a Win PC. So, this is my option I guess. So after pulling the 2 ROM files via the RUU, rename the 01 file to PJ75IMG.zip, placed on external SD card and flash through HBOOT....what is the process exactly in hboot? I don't remember. Thought you booted to hboot and it automatically finds and flashes? Then....do you power down/reboot/can you access sd remotely while in hboot to rename 02 file to PJ75IMG.zip, and flash? Thanks for any input. It's hard cause I don't have the device.
Click to expand...
Click to collapse
Once the phone gets to HBOOT, you have to press one of the Volume buttons to confirm the flash. Once the flash of the first zip is complete (and while the phone is still in HBOOT), you'll need to pop out the SD card and rename the second zip, replacing the first zip on the root of the SD card, and pop it back in (while still in HBOOT). Then press whatever volume key it says to reboot, while holding Volume Down, to get back into HBOOT to flash the second zip. Once that flash completes, you can press whatever volume key reboots the device and it should be back to full stock.

Better Mobile App

welcome