Root help save a brick

scotty85 · Jul 10, 2011

scary alien said:
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 ).

gotcha... i wonder why either didnt update to the march 5 ota? and even wierder i wonder why it wont let him hboot update? :confused:

at any rate i think the GF is wanting to go eat... when i get back i should be charged enuff to try and see what happens. :eek:

hopefully scary can help you get the cmd window set up and help you with those commands. most of that i dont know much about. when i installed adb i used the video i referenced, so i dont know for sure about the things that you guys were discussing.

scary alien · Jul 10, 2011

13kyl said:
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.

13kyl,

Getting FASTBOOT to run from the command line is (hopefully) just a Windows setup issue, but let me verify how things look on my PC / phone to see if this might even make any difference for you (i.e., prove the concept before putting you through all of the machinations).

I'm going to go back and do a quick review of the posts that you guys did while I was away, and then I should be able to try the stuff that eu1 suggested.

Cheers!

P.S., you've been amazingly patient with us...you are a real trooper

(not sure I would have lasted this long, LOL).

erisuser1 · Jul 10, 2011

13kyl said:
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

l

That screenshot says it is working. Based on what you said, it appears you are double clicking on that file (fastboot.exe) rather than opening a command window first, and typing commands into that window. The others will show you how this works. Now I really need to go.

scary alien · Jul 10, 2011

Sorry guys, I can report that the "fastboot oem rebootRUU" command / mode in combination with trying the SoSicWitIt root ROM replacement of the rom.zip while running the RUU still resulted in the same "ERROR [140]: BOOTLOADER VERSION ERROR"

.

Bummer.

edit: by the way, I forgot to mention that I did check the bootloader version...still S-ON

.

13kyl · Jul 10, 2011

yes, I have been double clicking it. How do I open it otherwise or from cmd?

erisuser1 · Jul 10, 2011

scary alien said:
Sorry guys, I can report that the "fastboot oem rebootRUU" command / mode in combination with trying the SoSicWitIt root ROM replacement of the rom.zip while running the RUU still resulted in the same "ERROR [140]: BOOTLOADER VERSION ERROR" .

Bummer.

Don't discourage 13kyl from trying it. His phone is not in the sa me condition as your phone. Specifically his misc partition might have different content than yours.

13kyl · Jul 10, 2011

erisuser1 mentioned it looks like my fastboot is working I am just doing it wrong. How should I be utilizing fastboot.exe?

scary alien · Jul 10, 2011

13kyl said:
yes, I have been double clicking it. How do I open it otherwise or from cmd?

13kyl,

You'll have to start a Windows Command Prompt (old DOS command window)... You can get there from the Windows key and selecting the Command Prompt" icon --or-- you can click the Start button and find and select the Command Prompt (its usually in the main Start list or in the Accessories folder).

Once you are there (i.e., have the "Command Prompt" window), you'll need to cd (change directory) to where the Android SDK folder is installed. In my case, its in d:\android-sd-windows. You then need to cd to the directory containing your fastboot.exe utility (probably in the same folder as adb.exe). Here's what I recently did when I tried the rebootRUU thing with the root ROM:

Code:

d:\android-sdk-windows\tools>[COLOR=blue][B]dir adb*[/B][/COLOR]
 Volume in drive D is Data
 Volume Serial Number is 2807-76ED
 Directory of d:\android-sdk-windows\tools
07/12/2010  06:51 PM           578,611 adb.exe
07/12/2010  06:51 PM            96,256 AdbWinApi.dll
07/12/2010  06:51 PM            60,928 AdbWinUsbApi.dll
               3 File(s)        735,795 bytes
               0 Dir(s)  241,474,605,056 bytes free
d:\android-sdk-windows\tools>[COLOR=blue][B]dir fast*[/B][/COLOR]
 Volume in drive D is Data
 Volume Serial Number is 2807-76ED
 Directory of d:\android-sdk-windows\tools
07/12/2010  06:51 PM           336,613 fastboot.exe
               1 File(s)        336,613 bytes
               0 Dir(s)  241,474,605,056 bytes free
d:\android-sdk-windows\tools>[COLOR=blue][B]fastboot devices[/B][/COLOR]
HT9XXXXXXXXX    fastboot
d:\android-sdk-windows\tools>[COLOR=blue][B]fastboot oem ?[/B][/COLOR]
                              ... INFOcommand list
INFO [COLOR=blue]keytest[/COLOR]
INFO [COLOR=blue]heap[/COLOR]
INFO [COLOR=blue]boot[/COLOR]
INFO [COLOR=blue]reset[/COLOR]
INFO [COLOR=blue]powerdown[/COLOR]
INFO [COLOR=blue]rebootRUU[/COLOR]
INFO [COLOR=blue]enableqxdm[/COLOR]
INFO [COLOR=blue]rtask[/COLOR]
INFO [COLOR=blue]task[/COLOR]
OKAY [  0.034s]
finished. total time: 0.039s
 
[COLOR=blue]Now, here's where I put the phone in rebootRUU mode (it'll just sit there[/COLOR]
[COLOR=blue]in the "htc" screen (I think that's what showed):[/COLOR]
 
d:\android-sdk-windows\tools>[COLOR=blue][B]fastboot oem rebootRUU[/B][/COLOR]
                              ... OKAY [  0.026s]
finished. total time: 0.027s
 
[COLOR=blue]The command comes right back, but the command should have been obeyed[/COLOR]
[COLOR=blue]by your phone (you'll see it change). Anyway, after I closed-down the RUU[/COLOR]
[COLOR=blue]window on my PC (since the test failed), I tried a few other things, just[/COLOR]
[COLOR=blue]for grins:[/COLOR]
 
d:\android-sdk-windows\tools>[B][COLOR=blue]fastboot devices[/COLOR][/B]
d:\android-sdk-windows\tools>[COLOR=blue][B]adb shell[/B][/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
d:\android-sdk-windows\tools>[COLOR=blue][B]adb devices[/B][/COLOR]
List of devices attached
 
d:\android-sdk-windows\tools>
d:\android-sdk-windows\tools>[COLOR=blue][B]adb devices[/B][/COLOR]
List of devices attached
d:\android-sdk-windows\tools>[COLOR=blue][B]adb devices[/B][/COLOR]
List of devices attached
 
d:\android-sdk-windows\tools>[COLOR=blue][B]fastboot oem ?[/B][/COLOR]
                              ... INFOcommand list
INFO keytest
INFO heap
INFO boot
INFO reset
INFO powerdown
INFO rebootRUU
INFO enableqxdm
INFO rtask
INFO task
OKAY [  0.012s]
finished. total time: 0.012s
d:\android-sdk-windows\tools>[COLOR=blue][B]fastboot oem powerdown[/B][/COLOR]
                              ... OKAY [  0.003s]
finished. total time: 0.004s
d:\android-sdk-windows\tools>[COLOR=blue][B]exit[/B][/COLOR]

Hope that helps a little.

13kyl · Jul 10, 2011

Alright I have the cmd open, I'm at the correct directory.

I moved the android-sdk-windows to my C: drive

I have C:\android-sdk-windows\tools>fastboot oem
<waiting for device >
finished. total time: 1310345597.017s

scary alien · Jul 10, 2011

erisuser1 said:
Don't discourage 13kyl from trying it. His phone is not in the sa me condition as your phone. Specifically his misc partition might have different content than yours.

Oh, sorry...did not mean to imply that...I was just really hopeful.

13kyl, lemme know if / when you are going to try this and need help. I've done the "find the rom.zip" thing after starting the RUU about 5 times now, LOL.

Here's what I did, by the way:

1. Start the RUU running and wait until you get the first screen that asked you to check a box and hit next

2. From Windows Explorer, navigate to your C:\Users\13kyl\AppData\Local\Temp directory (i.e., using whatever real name you use to login into Windows with for "13kyl"

3. In the "Search" box (top, right-hand corner of the screen), enter "rom.zip" and hit return

4. When the "rom.zip" file is found, right click on the file and select "Properties".

5. Mouse over and copy the contents of the "Location:" field that is displayed

6. Paste the copied location contents in another Window Explorer window's address (so that you'll be in better position to replace the rom.zip file)

7. From the "other" Windows Explorer, copy your base root ROM .zip file

8. Return to the Explorer window with the rom.zip location and paste your base root ROM here

9. Delete the rom.zip file

10. Rename the base root ROM file you pasted in step #8 above and rename it to "rom.zip"

11. Make sure you phone is connected via USB and you are booted-up in FASTBOOT mode

12. Start-up your Command Prompt like I mentioned in my prior post above

13. Type "cd c:\android-sdk-windows\tools" (or to where ever you actually have the fastboot.exe file)

14. Type "fastboot oem rebootRUU" and watch your phone change modes

15. Return to the RUU program you started-up in step #1 and proceed with trying to install the base root ROM (now renamed as rom.zip)

Crossing fingers (again, LOL).

Good luck, mate!

13kyl · Jul 10, 2011

fastboot devices (should see your device ID reported)
fastboot eom rebootRUU

just using above for reference

Note:
fastboot devices
HT9C4HG03823 fastboot

13kyl · Jul 10, 2011

I ran:

fastboot oem rebootRUU
...
OKAY [ 0.23s]
finished. total time: 0.023s

I'm trying to follow your directions... My phone says HTC in the middle of the screen and is stuck there.

scotty85 · Jul 10, 2011

im back. and watching. crossed fingers here also

13kyl · Jul 10, 2011

There are 2 rom.zip files in my temp directory.
How to proceed?

Should I replace both?

Delete one of them?

scary alien · Jul 10, 2011

13kyl said:
I ran:

fastboot oem rebootRUU
...
OKAY [ 0.23s]
finished. total time: 0.023s

I'm trying to follow your directions... My phone says HTC in the middle of the screen and is stuck there.

You're doing fine!

scary alien · Jul 10, 2011

13kyl said:
There are 2 rom.zip files in my temp directory.
How to proceed?

Should I replace both?

Delete one of them?

I would replace them both unless you are able to identify which is for the most current RUU session (that will be safer).

You might have had a killed RUU session from sometime earlier I guess and the temp files didn't get cleaned-up...

13kyl · Jul 10, 2011

Shoot!

I replaced both rom.zip files, but I did not replace them with this:
Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP

I instead used a file called PB00INT.ZIP from my desktop which I assume was an older Leak. Not 100% sure though.

The RUU is still "Sending"

13kyl · Jul 10, 2011

Error [140]:bootloader version error

scary alien · Jul 10, 2011

13kyl said:
Shoot!

I replaced both rom.zip files, but I did not replace them with this:
Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP

I instead used a file called PB00INT.ZIP from my desktop which I assume was an older Leak. Not 100% sure though.

The RUU is still "Sending"

Well, let's hope its an Eris ROM, LOL... If it is an older 2.1 leak and it loads / works...that's okay since you are really just trying to get to a point where you can actually boot your phone.

We can get you rooted and running other things when you are able to boot.

If this doesn't work, just re-do the steps but with the base root ROM.

Keep in mind that your phone is not charging (or charging very faster) while in RUU / fastboot mode (at least I don't think it will be). So, I hope you had a good charge to begin with...if not, take a break and make sure you put a good charge on that puppy

.

Good luck!

13kyl · Jul 10, 2011

Well it didn't work.

I got the BOOTLOADER error again.

S-on

scotty85 · Jul 10, 2011

13kyl said:
Well it didn't work.

I got the BOOTLOADER error again.

S-on

dammit!

i guess the next thing to try is this:

erisuser1 said:
(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)

what state is your phone in? is it still RUU mode? if so,type

Code:

fastboot oem powerdown

if i remember it correctly,that should turn your phone off so you dont have to something destructive like pulling the battery(prolly wont hurt at this point,but who knows?)

have your command window open and in the directory youve been using. now turn your phone on normally from a powered off state. listen the the pc to make little "usb pluggin in device" noices for lack of somethin else to call them.

at various points,as its doing whatever its doing,keep typing

Code:

adb devices

into the command window.

hopefully at some point it will spit back out your phones serial number

do that for maybe 10 minutes or so and report what happens

edit: if you do get a a serial number output,type

Code:

adb shell

into your command window and see if the promt changes in the window to a "#"

13kyl · Jul 10, 2011

I tried the replace rom.zip trick in FASTBOOT USB mode

It's doing some interesting things. It said waiting for bootloader then loading bootloader err something similar to that

then it said erasing user data

Now it is Sending......

scary alien · Jul 10, 2011

13kyl said:
Well it didn't work.

I got the BOOTLOADER error again.

S-on

Well, that's too bad...

Okay, let's try eu1's second item to try. Go ahead and do a "fastboot oem powerdown" (I think that's right) to shut your phone down without having to do a battery pull.

Then, if you think you still have enough battery charge left, do this:

1. Get yourself back to the Command Prompt, and make sure you have access to the "adb.exe" utility. You can do a "dir adb.exe" to make sure its in the same directory as your fastboot.exe utility is.

2. Power the phone on as normal, but try issuing "adb devices" command repeatedly while its booting, for at least as long as you think that its hanging again like when you first reporting things in this thread (probably just a four or five minutes should be more than sufficient).

Note, you can use the up-arrow key to recall your last command and just hit the return key to re-execute it.

Let us know if you actually see anything from "adb devices" (like your device ID like you reported before from the "fastboot devices" command).

If you do get a device name from the "adb devices", go ahead and try "adb shell" and let us know.

Cheers!

scary alien · Jul 10, 2011

13kyl said:
I tried the replace rom.zip trick in FASTBOOT USB mode

It's doing some interesting things. It said waiting for bootloader then loading bootloader err something similar to that

then it said erasing user data

Now it is Sending......

Wow...

...and hopeful!

That might be a good sign...I never saw that (but I also thought you had tried this...?).

Let us know (crossing fingers/toes/arms/legs,...)

scotty85 · Jul 10, 2011

13kyl said:
I tried the replace rom.zip trick in FASTBOOT USB mode

It's doing some interesting things. It said waiting for bootloader then loading bootloader err something similar to that

then it said erasing user data

Now it is Sending......

oh snap! fingers crossed

i forgot we hadnt really tried that option since you were having trouble finding the file. good call :cool:

lol scary and i typin basically the same thing again

Root help save a brick

Extreme Android User

not really so scary

Android Expert

not really so scary

Member

Android Expert

Member

not really so scary

Member

not really so scary

Member

Member

Extreme Android User

Member

not really so scary

not really so scary

Member

Member

not really so scary

Member

Extreme Android User

Member

not really so scary

not really so scary

Extreme Android User