jonzey231

Okay, so I was trying to install the recently released gingerbread onto my Eris. For some reason it didnt work, but i had already deleted my system and cache and now I am left with a phone with absolutely no software on it.

I'm not worried about the gingerbread now. Now my main goal is to just get back to my stock 2.1 or hell, stock 1.5. Anyways, I am trying to use an RUU and it keeps failing. The error message I am receiving is...

"The ROM Update Utility cannot open the requested files or the files are damaged. The RUU cannot continue with the update.

Please get a complete RUU package and try again."

I have tried several different RUU downloads and it's just been a total fail. If anyone can help at all, it would be greatly appreciated.
Thanks in advance.


Edit: Just for the record, I'm running Windows 7. It matters sometimes when it comes to my Droid X. lol

Last edited by jonzey231; June 7th, 2011 at 06:46 PM.

metlcat

Do you have any nand backups you can restore?

An easier way to get back to stock would be to use this: [ROM][03/06/2011]FlashBack21 v2 -Return to Factory Stock - March 2011 OTA - xda-developers

Just flash it like any other ROM.

jonzey231

I can't even boot into recovery, I believe an ruu is my only option.

doogald

I would try the leak v3 PB00IMG file.

You can find it here: Multiupload.com - upload your files to multiple file hosting sites!

Rename that file to PB00IMG.zip (it must be that exact name - if Windows hides extensions, unhide them, so that the file is not named PB00IMG.zip.zip) and copy to your SD card. Follow the instructions here; basically, these steps:



See if that works.

By the way, the Leak v3 RUU is here: Multiupload.com - upload your files to multiple file hosting sites!

jonzey231

I just tried an ruu again and it got really far to the point I thought it was going to work, then I got the same error I described earlier. If it helps any... this is what the screen says when i unplugged the device after the failure

"PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.00.04.12
Feb 8 2010, 00:08:56

RUU

jonzey231

Just saw your post, downloading and trying it now.

doogald

If you can get this to work, you can root with this procedure. It's a bit long, but very well documented.

Universal Eris Root for Dummies!

After that, if you want a Gingerbread ROM, GSB and CondemnedSoul's CM7 are both good. Condemned requires an additional flash of Google apps after flashing the ROM and before restart, while the latest GSB does not.

jonzey231

Well I just tried the Ruu that you suggested, I didn't try to the rom yet though because at the moment I have no way of getting it on my SD card because since this is my girlfriends eris, I let her have my droid x till further notice.

Needless to say, the ruu.exe that you suggested didnt work, I got the same error as before.

jonzey231

Granted I can get this file on to my sd card, how to you suggest I install it? Like I said, I can't even boot into the stock recovery.

doogald

The instructions are in my post above.

To repeat them, you boot to HBOOT by holding VolDn when you start the phone. The bootloader will check for the presence of a file called PB00IMG.zip - if it finds it, it starts to install the file, showing a progress bar in blue toward the right-hand side of the display. You press the trackball when prompted to agree to install the image, then again to restart the phone when it is done.

jonzey231

I can't boot into hboot.

jonzey231

I just tried loading it onto the sd card anyways and it didn't work. I can't boot to hboot, and none of the windows ruu applications will work.

I'm really scared here, this is my girlfriend's phone and she just got it like a week and a half ago as her first smart phone.

I've gotta get this fixed.

jonzey231

Just ran the application again. It fails at 61 % while it's "Updating User Data".

jonzey231

I can't boot into hboot.

scotty85

im a little confused how youre trying to install the PB00IMG files. how did you get the fillowing info if you cannot boot into hboot? the white screen with colored letters that this info is displayed on IS hboot.

1)so you get the v3 leak "root rom" renamed to PB00IMG on your zip card... you power off,then power on while holding volume down... what happens?

what should happen is the white screen will appear,youll get a blue progress bar on the right,followed by a gold(IIRC) progress bar,followed by a promp to update.

if its something different,describe whats going on in as much detail as possible.

2) what happens if you simply power on? hangs at skateboards or bootloop? or goes to a a functional,or semi-functional operating system? again,please provide as much detail as possible.

__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers.
follow me on twitter @scotty1223

jonzey231

The phone will not boot to anything including hboot. The screen you're asking about I was able to get when unplugging the usb cable after a failled ruu attempt.

Press the power button = black screen
Press the power button + down volume button = black screen

The only time I can even get an HTC logo screen is when the ruu is running on the computer side.

And last but not least, I got the PB00IMG file on my sd card using my moms blackberry as a usb drive and transferring it over.

doogald

Ok, this sounds a little familiar. There have been two people who were able to get this solved using a trick using RUU, as reported in this post at xda-deveopers: xda-developers - View Single Post - [Q] semi-Bricked?? fix?

(And here is the full thread: [Q] semi-Bricked?? fix? - xda-developers )

This thread is a little less geeky and will hopefully walk you through everything you may need to do to recover the phone: [SOLVED] Anyway to Unbricked a Droid Eris? - xda-developers

By the way, just to ask, how did you root the phone? Did the root method install clockwork recovery or Amon_RA?

jonzey231

Okay I just got a new screen!

I installed HTC Sync to make sure I had all the appropriate drivers and when I reconnected the phone the HTC Bootloader driver installed.

I ran the Ruu again, it still failed but before when I would disconnect it I got



This time when I disconnected it I got

Last edited by jonzey231; June 8th, 2011 at 09:18 AM.

jonzey231

Clockwork recovery was installed.

doogald

Well, I hope that you are able to get that RUU replacement trick to work to get the 1.49.2000 S-OFF bootloader on the phone. If you can do that, you hopefully will be able to use fastboot flash to get Amon_RA recovery on the phone and then flash a new ROM that works.

jonzey231

I just read through that link to the xda thread you sent me, and I'm going to be completely honest it was way over my head. This is my first experience with an HTC device so I honestly have no prior knowledge.

Is there anyway you could simplify it for me?

I have the radio that they said I would need, I just don't know how to do any of the stuff they talked about in that thread. It seems that they all had prior knowledge.

I haven't said this in a long time, but I am a noob here on this one.

Last edited by jonzey231; June 8th, 2011 at 09:37 AM.

doogald

I think the first step is to download the original root ROM PB00IMG.zip file from here: [HTC ROMs] Consolidated HTC Eris RUU/OTA/ROM URLs - xda-developers

Do you see where it says "Root ROM"? Download that file. Rename that file "rom.zip".

Now, run the RUU that you have already tried, but stop when you get to the step that would flash the RUU to the phone and follow the steps in this post: xda-developers - View Single Post - [SOLVED] Anyway to Unbricked a Droid Eris? to find where in your temp directory the file created by the RUU called "rom.zip" is stored. Delete that file, replace it with the one that you downloaded, and then go back to the RUU application and let it try to flash. Hopefully you will end up with the 1.49.2000 S-OFF bootloader version on the phone (you will still probably get an error from the RUU utility when it tries to flash the ROM.)

This would be the first step.

By the way, I am in and out all day today. Hopefully somebody else will step in to help if I'm not around, or you can be a little patient.

Last edited by doogald; June 8th, 2011 at 10:03 AM.

scotty85

Just wanted to point out if you can get s-off,another recovery option may be to use the hboot recovery scary and I made

Also,I'm driving,but ill try and help out when I can

Last edited by scotty85; June 8th, 2011 at 10:21 AM.

jonzey231

I just got off work, and I want to say thanks in advance for actually making this a priority. I really appreciate it.

jonzey231

Holy crap, you guys are seriously awesome. I am now at hboot - 1.49.2000 as well as S-OFF.

Now what? lol

scotty85

IIRC,you'll now want to flash amon recovery via fastboot or hboot. Once you have that,try and flash a small MB rom such as celb 4.3,or maybe even aosp tazz GB and it works.

jonzey231

How do I flash amon? I still can't boot into anything.
The only reason I knew I was s-off was because after the failed ruu, it shows it once the phone is disconnected.

doogald

The guy who fooled around with this and discovered this method is the awesome one.

I'm away from a real computer, so the next step will be brief, but next you will want to download a copy of Scary Alien's version of Amon_RA Recovery. You can find it at this link. Scroll down until you find this part:

That's the one that you want. This will be downloading not a zip file, but a file called recovery-RA-eris-v1.6.2-trackball-optional.img.

The next step would be to get fastboot downloaded and verified communicating with the Eris. Here is where I call on somebody else for more help - I am a Mac user and that's much different. And, of course, I am not now at a computer in which I can try to figure this out. I think fastboot requires that the Android SDK be installed. Do you have that set up on your Windows computer yet?

Here is some info about installing the SDK and fastboot: HTC - Developer Center

The SDK download and I think some instructions are here: Android SDK | Android Developers

The download for Fastboot is here (the link above) but you can stop reading after the fastboot download - you don't need to download image packages, etc., and you already have the USB driver installed.

So, the next step would be to get the SDK set up, cable the phone to the computer (see if you can now start the HBOOT by starting with VolDn pressed when you power up - hold the VolDn until you see the skating Androids), and see if you can get to fastboot mode (press VolDn when prompted after the HBOOT starts) and do a "fastboot devices" from a Windows command line.

Hopefully somebody can walk you through some of these steps if you have some trouble. I do have a Windows partition on one of my Macs at home so I could fool around with that later if nobody else gets to it.

doogald

Oh, and try to see if you can learn how to verify MD5 hashes of files that you download. The primary reason is to make sure that you are flashing files that have been completely downloaded rather than just partially downloaded.

scary alien

LOL...hate to stick my nose in here after all that's been written, but I was hoping to see Scotty (or thinking that he might) suggest using the HBOOT flashable Amon_RA custom recovery installer that he suggested in a thread earlier this year.

I can't give too much attention to helping the OP out at the moment, but I could when I get home from work later this afternoon.

I'll reference that thread here, with the stipulation that I think the OP should hold-off doing anything that he is not certain about doing or explicitly directed to do (don't want to muck anything up):

making an hboot flashable recovery

but the OP could read through it just to become familiar.

The file that I think would be needed is this one, referenced in the above thread:

https://sites.google.com/site/scaryalienware/downloads/PB00IMG-amon_ra_trackball-optional.zip?attredirects=0&d=1

The OP should also probably get rid of / rename the base root ROM (PB00IMG.zip) that he used to get the S-OFF bootloader. This file will conflict with my HBOOT flashable version of Amon_RA's custom recovery that I just mentioned.

I'll let Scotty weigh-in too and I'll check back here after I get off work.

Cheers!

edit: LOL again...I do see that Scotty already previously mentioned using the HBOOT installer a few posts up...

__________________
androidforums Site Rules/Guidelines

[App] AFV (Android File Verifier) - file checksum (MD5, SHA1, etc.), signed jar / .zip verifier, and Nandroid backup verification
[App] BattMonX - display battery state via LED indicator & status bar icon
[App] Android Root Toolkit (beta)

Last edited by scary alien; June 8th, 2011 at 01:36 PM.

scotty85

So if you power on holding volume down,do you still get just a black screen? Or can you now get into hboot(white screen with colored letters)?

doogald

Right, if this RUU trick that updated the bootloader also allows HBOOT to start, that would be an ideal way to do this.

Not having done this myself, though, let's just wait to see if jonzey can restart the bootloader successfully holding VolDn on boot.

jonzey231

Okay, I'm terribly sorry. My internet went down today. We were having some bad storms in my area. At the moment, when I hold down the volume button and press the power button, all I get is a lit black screen.

jonzey231

Okay, I am trying to install fastboot and I am getting an error message that says

"The program can't start because AdbWinApi.dll is missing from your computer. Try reinstalling to fix this problem."

doogald

Did you install the Android SDK first?

jonzey231

Yes, I already have it installed. I went to update all my files though so I could get the Google USB Driver, and access was denied to every single download.

It said a file path wasn't found for each one.

doogald

Ok, you're going to have to wait for a person with Windows SDK experience for this one. I'm not sure what the Google USB driver is, though. Based on this:

I don't think that you need the Google USB driver. You already installed the HTC sync thing, which installs the driver for the Eris (as I understand it.) You just need to install the SDK from here:

Android SDK | Android Developers

(the one that says "recommended", I would think).

jonzey231

Like I said earlier, I already have the SDK installed. I have for quite some time. I'll try reinstalling though.

doogald

Ok, I think I understand it. The fastboot.ext is not an installer - it is the command line tool.

If I understand how Windows does this correctly, the easiest thing to do is to move that file to the SDK install directory, where the adb file is. Then also copy the amon_ra recovery .img file to that same directory as well.

The you want to start a command prompt (start run cmd.exe, I think). At the command window prompt, you want to change directory to the location where fastboot and the abd tool are (cd \whateverthatpathis ) and then, with the Eris powered on and connected by USB:

fastboot devices

Hopefully it will return something that looks like HTC and a bunch of numbers - if you are seeing that, that's good news.

Scary or scotty, please pipe in if I am getting this wrong...

scotty85

so what happens if you open a command window,plug in the phone,and type adb devices?

i dont recall doing anything special other than installing the android sdk. i also dont remember exactly what i did about drivers... i had downloaded htc sync for those drivers,but ive also downloaded these drivers: Universal Windows USB Drivers (ADB, BootLoader, Disk Drive, HTC Sync)

ive got 3 htc phones,so its a lil fuzzy at this point what worked with what

jonzey231

It is not fastboot.ext, it is fastboot.exe. Therefore it is a windows executable file. Someone please let me know if I am wrong.

The only progress I've made on this device so far is getting the S-off and the correct hboot.

I just need to know what to do next.

scotty85

this^

once you get adb to see your phone. this directory will usually be in "tools" assuming you have also copied all of platform tools into the tools directory. im still new to all this also,so hopefully scary can chime in with a lil more info.

try
adb devices

fastboot devices

when the phone is plugged in

a lil more on the changing directorys...if you put the sdk in C like i did,open your command window and type:

cd c:\android-sdk-windows\tools

this will get you setup to push the recovery image to the phone via fastboot,from the tools directory.

jonzey231

When I try adb devices it just tells me "adb is not recognized as an internal or external command"

Plus, I may be wrong, but won't adb only work if usb debuggins is turned on? I mean, it was on when the phone was last working but would it still be active?

scotty85

open the command window,plug in the phone,and try the commands:

adb devices

fastboot devices

i did not run any executable files to make fastboot work.

scotty85

did you try directing the prompt to the location where the sdk is stored?

doogald

Nope, I know for a fact that fastboot.exe (the ext was a typo) is a command line tool. Before I had all Macs I was all Windows and before that DOS, and I have run plenty of non-Windows .exe files in my lifetime. It's been a long lifetime. So far.

(Well, to be technical, if it requires a .dll it probably is a Windows app, but one that does not actually run in a graphical window.)

scotty85

i dont know if this will help,but this is exactly what i did to set up adb to root my TB:



afterward,i could do things on my incredible and my eris.

scary alien

Guys, sorry I've been tied-up this evening and just got back to this thread.

Hopefully jonzey231 has the older version of the Android SDK installed, since the adb.exe utility is in the "tools" directory. It has been moved to the "platform-tools" directory, which is a separate download and install for the newer version of the Android SDK.

Also, won't jonzey231's phone need to be booted into FASTBOOT mode in order for the fastboot flash to work? We should probably establish that he can actually bring up the FASTBOOT screen first, eh?

Thanks!

doogald

Yes, I think it stays on. Yes, I think adb requires it in order to do anything while the phone is running Android (right now it's not.) And, if adb devices does not work, how about fastboot devices?

And, let me just repeat: find out where the adb.exe file is stored. Move the fastboot.exe file to that directory. If that directory is c:\AndroidSDK, make sure that you start the command prompt and type:

cd \AndroidSDK

as the first command before you try fastboot devices

Oh, and if there are spaces in the directory path to the storage location of adb.exe and fastboot,exe, do the cd command with quotes, like this:

cd "\path to the adbfile"

(Really not sure windows usually puts this...)

doogald

I am hoping that's not the case, as he (she? sorry, don't know... ) cannot seem to start in hboot mode.