• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root HTC Eris RUU won't run

scary alien said:
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!
Click to expand...

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

From this thread is this post which says:

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...

So I'm hoping that fastboot will get a response...
 
doogald said:
From this thread is this post which says:

So I'm hoping that fastboot will get a response...
Click to expand...

from some experimentation with my phone,sort of looks like sdk will not see adb and fastboot devices at the same time... if that makes sense. in normal bootted up mode,adb devices will list it.. or in recovery. i can only get a listing for fastboot devices,in fastboot. at that time,adb devices no longer sees it.

so... im thinking its good that its not seen when typing "adb devices". hoping also fastboot devices gets a response...
 
scary alien said:
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!
Click to expand...

i dont think that the fastboot opening and being out on the screen is a requirement.

from what i gather from this post:
xda-developers - View Single Post - [Q] semi-Bricked?? fix?

if he gets a response by typing fastboot devices,then he can flash recovery,and it should work :)
 
scotty85 said:
also,might be worth trying some other button combinations as mentioned in this post:

xda-developers - View Single Post - [Q] semi-Bricked?? fix?

and since the last 4 replys are from me,im gonna be quiet now :)
Click to expand...

Thanks a lot Scotty you really are helping a lot. Trying the fastboot devices now, then I'll try the other key combinations.

Edit: give me the exact command for fastboot and for adb to paste in front of "C:\Users\users>"
Please. :)
 
I just used that video and I have successfully typed in fastboot and a big list of stuff came up with commands and options!

I think this i really good, so what do i do next?!

Sorry, I just feel that this is major progress. :) haha
 
This is where I am right now. :) :)


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\user>cd c:\android-sdk-windows\tools

c:\android-sdk-windows\tools>dir
Volume in drive C has no label.
Volume Serial Number is B0AE-AF4E

Directory of c:\android-sdk-windows\tools

06/08/2011 11:19 PM <DIR> .
06/08/2011 11:19 PM <DIR> ..
06/08/2011 11:18 PM 5,445,617 aapt.exe
06/08/2011 11:18 PM 410,942 adb.exe
06/08/2011 11:18 PM 96,256 AdbWinApi.dll
06/08/2011 11:18 PM 60,928 AdbWinUsbApi.dll
06/08/2011 11:16 PM 323 adb_has_moved.txt
06/08/2011 11:18 PM 1,344,051 aidl.exe
06/08/2011 11:16 PM 3,237 android.bat
06/08/2011 11:16 PM <DIR> ant
06/08/2011 11:16 PM 1,444 apkbuilder.bat
06/08/2011 11:16 PM 2,275 ddms.bat
06/08/2011 11:18 PM 423,585 dexdump.exe
06/08/2011 11:16 PM 127,504 dmtracedump.exe
06/08/2011 11:16 PM 1,445 draw9patch.bat
06/08/2011 11:18 PM 2,682 dx.bat
06/08/2011 11:16 PM 9,733,600 emulator.exe
06/08/2011 11:16 PM 17,976 emulator_NOTICE.txt
06/08/2011 11:16 PM 779,819 etc1tool.exe
06/08/2011 11:16 PM 183,651 fastboot.exe
06/08/2011 11:16 PM 2,349 hierarchyviewer.bat
06/08/2011 11:16 PM 36,100 hprof-conv.exe
06/08/2011 11:16 PM <DIR> Jet
06/08/2011 11:16 PM 1,627 layoutopt.bat
06/08/2011 11:19 PM <DIR> lib
06/08/2011 11:18 PM 16,046,592 llvm-rs-cc-2.exe
06/08/2011 11:18 PM 15,424,512 llvm-rs-cc.exe
06/08/2011 11:16 PM 30,830 mksdcard.exe
06/08/2011 11:16 PM 1,503 monkeyrunner.bat
06/08/2011 11:18 PM 332,494 NOTICE.txt
06/08/2011 11:16 PM <DIR> proguard
06/08/2011 11:18 PM 301 source.properties
06/08/2011 11:16 PM 1,446,224 sqlite3.exe
06/08/2011 11:16 PM 1,919 traceview.bat
06/08/2011 11:16 PM 460,463 zipalign.exe
29 File(s) 52,420,249 bytes
6 Dir(s) 425,065,365,504 bytes free

c:\android-sdk-windows\tools>adb devices
List of devices attached


c:\android-sdk-windows\tools>fastboot
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader

options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048

c:\android-sdk-windows\tools>
 
I'm going to get to bed, if you post I'll check back in the next hour a couple times but I'll be up around 8 or so in the morning to keep this rolling too. So let's keep up the work, we're making progress and just for the record, if you guys every get a motorola phone and need help get at me. It's the only way I can think of to pay back what you're doing for me. I've pretty much mastered all this with the Droid X and OG Droid lol.
 
jonzey231,

Thank you very much for making that video...it really does re-affirm what you've been saying (and things that I've not personally seen before...).

I couldn't tell you had the screen showing the S-OFF at the top of your phone what the option that was listed (i.e., the last line of text near the middle of the screen). Was it "HBOOT"?

Let's back up a smidge here on the Android SDK... in what folder / subdirectory, do you find the "adb.exe" utility?

I have my SDK installed at the top of the C:\ drive...a lot of folks have theirs installed under "Documents and Settings" (I believe). So, launch a Windows Prompt (old DOS / command window) and type:

Code: 
c:\users> [B][COLOR="Blue"]cd c:\[/COLOR][/B]
c:\> [B][COLOR="blue"]dir/s adb.exe[/COLOR][/B]

My adb.exe is in c:\android-sdk-windows\platform-tools. Your's might be in ...\android-sdk-windows\tools.

Anyway, that's the directory that you want to be in (cd to) to launch the subsequent commands that Scotty and doogald gave you.

Lemme know what you see.
 
yes,the video was extremely helpful. try putting the phone in the ruu mode(htc and triangles in the corners) and open your command window. navigate to C:\Users\user>cd c:\android-sdk-windows\tools and type

adb devices

fastboot devices

im betting(and hoping) that youll get a listing while on this screen.if not,try it on the black screen as well
 
scary alien said:
Hey, jonzey231, looks like we crossed-posts! LOL.

Have you tried a "fastboot devices" while the phone is plugged-in via USB?
Click to expand...

I have not tried that. How do I do it? You were right, my stuff is in the regular tools, not the platform-tools like yours. anyways, from a fresh command prompt, how would i try the "fastboot devices"?
 
nevermind that, I just got the fastboot devices. You'll think i'm dumb but my device was shut off and that's obviously why it didnt show up when i tried it after reading your post originally.

anyways, my phone shows up in "fastboot devices"
 
next thing that you need to do is download the recovery-RA-eris-v1.6.2-trackball-optional.img,and after double checking its md5 sum,place it into the tools directory.

the download link is in doogalds post,#28

do "fastboot devices" to make sure the phone is still bein seen,and then:

Code: 
fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img

it should do something like this:

Code: 
d:\android-sdk-windows\tools>fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img
  sending 'recovery' (3834 KB)... OKAY [  0.844s]
            writing 'recovery'... OKAY [  1.390s]
finished. total time: 2.236s
d:\android-sdk-windows\tools>

please note that i did not come up with this,its from the master recovery maker,scary alien,and his thread here: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html

but i figured it would be a lil less confusing to just cut and paste it here instead of directing you there,where youd have to sort thru the other methods of installing it :)
 
scotty85 said:
next thing that you need to do is download the recovery-RA-eris-v1.6.2-trackball-optional.img,and after double checking its md5 sum,place it into the tools directory.

do "fastboot devices" to make sure the phone is still bein seen,and then:

Code: 
fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img

it should do something like this:

Code: 
d:\android-sdk-windows\tools>fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img
  sending 'recovery' (3834 KB)... OKAY [  0.844s]
            writing 'recovery'... OKAY [  1.390s]
finished. total time: 2.236s
d:\android-sdk-windows\tools>

please note that i did not come up with this,its from the master recovery maker,scary alien,and his thread here: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html

but i figured it would be a lil less confusing to just cut and paste it here instead of directing you there,where youd have to sort thru the other methods of installing it :)
Click to expand...

Already have that img file downloaded and I'll do it now and return when i am finished.
 
Nevermind, I read back through it and saw i forgot the .img part of the command.
I just did it again, and it was a success! :)
 
if you get the 2nd part of after running the command,im not sure what will happen. if your phone does not just come on,and have the menu,you can make sure the phone is still being seen,then try:

adb reboot recovery

or

adb shell

then

reboot recovery

i dont think those commands will work,but they are worth a try.

if they dont work,unplug the phone,pull the battery and try the key combinations again...

vol down/power
vol up/power
send/end

and see if any of those things work.
vol up/power should take you to recovery
vol down/power should take you to hboot,where you could pick recovery with the volume and power keys.

if you can get this far,place a very small footprint(small MB size) rom on the sd card and try to flash it

if adb quits seeing your phone at any time,try unplugging for a couple minutes,then plug back in.
 
You must log in or register to reply here.
Back
Top Bottom