Root help save a brick

[scotty85]

i would go ahead and try it,but my battery is almost dead. ill be watching to see what happens

im assuming the battery will not charge in ruu mode?

 

[13kyl]

I get error:

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

This is when trying to launch fastboot.exe

edit:
I am downloading: android-sdk_r12-windows.zip

 

[erisuser1]

i would go ahead and try it,but my battery is almost dead. ill be watching to see what happens

im assuming the battery will not charge in ruu mode?

dunno for sure. It is safe to assume that it will NOT charge, and therefore doing things with a low battery is dangerous.

13kyl, you should be aware of this as well - the Eris will not charge if it is sitting in HBOOT, or FASTBOOT mode. It might be time for you to turn it off completely, and charge it well.

We can walk you through all the fastboot instructions in the meantime.

eu1

 

[13kyl]

I charged the phone fully overnight. I am trying to make sure to be charging it between attempts. This may cause me to take a few minutes longer when I try something new. I have to get into the menus again.

 

[erisuser1]

PS.

Both "adb" and "fastboot" can be used without installing the full-up SDK - so long as the drivers on the PC are already installed.

I would avoid setting up the SDK if possible. If we need "adb", all that really needs to be done is to download and unpack the SDK, but not install it.

That avoids all the Java JDK and Eclipse nonsense... so long as 13kyl's drivers are working.

eu1

 

[13kyl]

I get error:

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

This is when trying to launch fastboot.exe

edit:
I am downloading: android-sdk_r12-windows.zip

I am not sure the drivers are working as I get a .dll error when I try to run fastboot.exe

 

[13kyl]

I have downloaded and unpacked: android-sdk_r12-windows.zip

 

[erisuser1]

I charged the phone fully overnight. I am trying to make sure to be charging it between attempts. This may cause me to take a few minutes longer when I try something new.

Gotcha. Thing is though - there's no battery meter available to you, so you don't know how deeply it is already discharged.

When the Eris is sitting in either HBOOT mode or FASTBOOT mode, the processor appears to be operating at full tilt - the phone will completely discharge in something like 90 minutes

Note that the phone charges about twice as fast on the charger than via a USB connection to a computer (when it is off).

I have to get into the menus again.

Eh? Having trouble parsing what you mean here.

 

[13kyl]

I just mean I have to remove the battery, hold volume down + power on, to get into HBoot mode. I'm pretty sure I have a good charge as I've never left it in HBoot mode or FASTBOOT mode for more than a few minutes.

I will grab my wall charger! Thank you.

 

[erisuser1]

I am not sure the drivers are working as I get a .dll error when I try to run fastboot.exe

That's a dynamic link-library dependency, not a driver dependency.

If you unpacked the SDK, I believe that fastboot (a different version) is in the platform-tools subdirectory? (search for "fastboot.exe" under the folder where you unpacked the tools).

 

[erisuser1]

I am not sure the drivers are working as I get a .dll error when I try to run fastboot.exe

Is the missing DLL named "AdbWinApi.dll" ?

If so, see if you can find it underneath the SDK folder you unpacked.

 

[13kyl]

I located fastboot.exe in the unpacked android-sdk_r12-windows.zip
I get the same error.

AdbWinApi.dll is missing

 

[erisuser1]

I located fastboot.exe in the unpacked android-sdk_r12-windows.zip
I get the same error.

AdbWinApi.dll is missing

If you can find this .dll file underneath the (unpacked) SDK folder, make a copy of it and put it into the same folder as the fastboot.exe program. (Either the one you downloaded from HTC, or the SDK folder containing a different version of fastboot.exe).

There is a different way to handle this (adding the folder containing the .dll to the Windows PATH variable), but I think you can use this as a work-around (putting any .dll files needed into the same folder with the .exe.

 

[scotty85]

When the Eris is sitting in either HBOOT mode or FASTBOOT mode, the processor appears to be operating at full tilt - the phone will completely discharge in something like 90 minutes

lol thats what drained mine... its been sitting in fastboot for awhile.

 

[13kyl]

I cannot find AdbWinApi.dll in the sdk file or with a search (either of jsut the file or the entire computer)

 

[erisuser1]

I cannot find AdbWinApi.dll in the sdk file or with a search (either of jsut the file or the entire computer)

are you sure it is not in the platform-tools/ folder underneath the SDK unpack location?

[ Edit ]
If not, maybe the SDK needs to be installed. UGH.

 

[13kyl]

I do not have platfor-tools/ path

The folder "tools" contains this note:


The adb tool has moved to platform-tools/
If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"
Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.

edit:
Looks like that may be the case...

 

[erisuser1]

I do not have platfor-tools/ path
...
edit:
Looks like that may be the case...

UGH. Well, I guess you need to install the SDK. UGH.

 

[13kyl]

... 5% ...

... 22% ...

from "Installing Archives":

Downloading Android SDK Platform-tools, revision 5
Installing Android SDK Platform-tools, revision 5
'adb kill-server' failed -- run manually if necessary
Installed Android SDK Platform-tools, revision 5
Downloading Documentation for Android SDK, API12, revision 1

 

[erisuser1]

So, scotty85 / 13kyl / scary alien:

I need to scoot out of here around 18:30 EDT, and probably can't be back until midnight (EDT) or later. Can/will you pick up assisting 13kyl?

Here are the possibilities to consider:

(1) The RUU utility might not complain about "Main Version is Older" problems if the phone is in the RUU mode to begin with. Might.
So, it is worthwhile to try putting the phone into RUU mode ("fastboot oem rebootRUU"), and then re-trying the 2.36.605.1 RUU, replacing the "rom.zip" file (located in a temporary folder) with the ROOT PB00IMG.zip file (renamed to "rom.zip", of course).

Usually, a failure will occur, but this process is a complete success if the S-OFF bootloader gets installed. From there proceed to a soft-booting of Amon_RA's recovery ("fastboot boot recovery-RA-Eris-v1.6.2.img"), followed by an attempt to install a ROM file. If this (ROM flash) fails during /system or /boot flashing, then the ClockworkMod corruption has occurred, and ErisMTDNuke_v0.9.zip needs to be run first. If it succeeds, hard flash the recovery using fastboot ("fastboot flash recovery recovery-RA-Eris-v1.6.2.img").


(2) If "adb devices" responds affirmatively with the device ID (after trying to start the phone normally), that indicates that there is some sort of booted linux kernel alive and "adbd" is running on the phone, see if "adb shell" gives a root prompt. If the unlockr install was partially succesful - and 13kyl was lucky enough that the unlockr method installed a ROM that had USB debugging enabled by default, then a root shell is possible. From there, the "flash_image" utility can be used (via adb) to flash Amon_RA - just like in the bad old days of early rooting. (Alternatively, "flash_image" can be used to flash a copy of the misc partition from jcase's "Flash any RUU" post, as in "flash_image misc misc.img" - this would allow any RUU or PB00IMG.zip install to work without "Main Version Older" complaints)

(3) The third option is the worst - attempting the "tereg race condition" exploit of the recovery. I don't know if it ever worked with the 2.41.605.1 recovery - it was only attempted on the 2.36.605.1 recovery. (Yes, each of the recoveries are slightly different from each other - at a minimum, they use the same kernel that is in use in /boot).

eu1

I will check back on this thread - but it might not be until "tomorrow" your time.

 

[13kyl]

I am still installing SDK on my laptop. I chose my laptop because my desktop search function appears to be malfunctioning. My laptop is able to search out files that my desktop says do not exist.

I found "AdbWinApi.dll" on my laptop and moved the file to the same directory as "fastboot.exe". (This is in the "android-sdk_r12-windows" that I unpacked but did NOT install on my desktop)

It flashes a command line interface that rapidly disappears. I was able to get a screenshot though. This command line will not stay on my desktop it lasts milliseconds.

I posted the image I captured in photobucket:

Eris :: fastbootscreenflashcapture.jpg picture by 13kyl - Photobucket

 

[scary alien]

I'm half-back...cooling-off from the 90-degree heat...and still have to get a shower and some food.

I'm catching-up on the posts since I left...I'll try the FASTBOOT thing in a while too...but I'm wall-charging my phone: I left it in FASTBOOT mode this entire time I've been gone and its almost empty, LOL (yes, I have an extended battery in it , so that's why it wasn't totally drained).

The wall-charger should get it juiced-up quicker. Then, I'll accept the latest OTA to make my phone like 13kyl's again and try the FASTBOOT thing.

Cheers!

 

[scotty85]

The wall-charger should get it juiced-up quicker. Then, I'll accept the latest OTA to make my phone like 13kyl's again and try the FASTBOOT thing.

Cheers!

scary... check your firmware version before you procede,after the OTA. i bet youll be on 2.41.605.6,and not 2.37.605.4(what 13kyl is on).

im going to try and fastboot myself into ruu mode and then do the rootrom sneekaroo on top of v3. if it works there,it should work on top of 2.37.605.4

 

[scary alien]

scary... check your firmware version before you procede,after the OTA. i bet youll be on 2.41.605.6,and not 2.37.605.4(what 13kyl is on).

im going to try and fastboot myself into ruu mode and then do the rootrom sneekaroo on top of v3. if it works there,it should work on top of 2.37.605.4

After I installed the v3 leak before and accepted and installed the OTA, I was 2.37.605.4 (http://androidforums.com/eris-all-things-root/371983-help-save-brick-3.html#post2932438), and I think that makes sense since 13kyl's dad would have accepted and installed any OTA updates, too.

Phone's about 50% charged...gonna give it a little while longer.

Gonna grab a quick shower (I stink ).

 

[13kyl]

I've been charging my phone and I have a green led now.

SDK Platform is still downloading (It's literally at like 20% overall)

I have not been able to get fastboot.exe to work.