Root Can someone help, noob and problems flashing recovery

[ahjee]

Ive got the rooted 2.1, easy.
Ive got all the java and adk and what not
I got the flash_image and recovery.img
the command prompts all work fine till the last command, (ive tried 2 different chain of commands both work untill a certain point)

adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img (after this one it says it cannot find flash recovery or image, cant exactly remember.)

this was the first thread i founds suggestion of commands or whatever youd call it, im a noob

then i found another thread with different commands (northmendo,xda forum)

8. Open the Terminal and copy and paste the following commands with the phone connected to your computer.

8. adb shell [hit enter]

9. su [hit enter]

10. flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img (once again not found but i believe i followed correctly)
this the end of commands the first half worked fine.

i dunno what to do, i also found another thread with a different suggestion which was open prompt \tools\ fastboot flash recovery recovery.img
or suttin to that matter and that didnt work either. im lost.

 

[droidkevlar]

I am prob no help but have you rebooted your phone? Is our SD card unmounted ( you want it unmounted)? Are you sure the phone is rooted? Dont kill me for asking but you say your a n00b so just wanted to make sure.

 

[acidbath5546]

Ive got the rooted 2.1, easy.
Ive got all the java and adk and what not
I got the flash_image and recovery.img
the command prompts all work fine till the last command, (ive tried 2 different chain of commands both work untill a certain point)

adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img (after this one it says it cannot find flash recovery or image, cant exactly remember.)

this was the first thread i founds suggestion of commands or whatever youd call it, im a noob

then i found another thread with different commands (northmendo,xda forum)

8. Open the Terminal and copy and paste the following commands with the phone connected to your computer.

8. adb shell [hit enter]

9. su [hit enter]

10. flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img (once again not found but i believe i followed correctly)
this the end of commands the first half worked fine.

i dunno what to do, i also found another thread with a different suggestion which was open prompt \tools\ fastboot flash recovery recovery.img
or suttin to that matter and that didnt work either. im lost.

Ask your question here:
http://androidforums.com/all-things...d-all-links-faq-roms-q-here-03-25-2010-a.html

 

[droidkevlar]

Ask your question here:
http://androidforums.com/all-things...d-all-links-faq-roms-q-here-03-25-2010-a.html

Just a thought acidbath, but doing what you're saying will just make 1 giant thread and not easily searchable. Most of the time the question isnt answered right away and you will have multi posts before its the correct one. People may not read all of them and get messed up. So why not just after someone creates a new thread and its answered correctly move it to this thread you have created. Like how you did for a few things I had issues with.

Just a thought, please dont kill me. Just a thought from a first time rooter.

PS. Thank you all for your hard work so far on this and how much support you give us.

 

[GrdLock]

Please post the output you're seeing after you type each command.

 

[acidbath5546]

Just a thought acidbath, but doing what you're saying will just make 1 giant thread and not easily searchable. Most of the time the question isnt answered right away and you will have multi posts before its the correct one. People may not read all of them and get messed up. So why not just after someone creates a new thread and its answered correctly move it to this thread you have created. Like how you did for a few things I had issues with.

Just a thought, please dont kill me. Just a thought from a first time rooter.

PS. Thank you all for your hard work so far on this and how much support you give us.

Thats actually a very good point, I hadnt really though of it that way.
I think I will actually do that, and then copy and past or summarize the Question and Answer in the new thread.
Good Thought, and thanks

LOL...I wouldnt kill you...might take away your Eris and make you use a Iphone....but never death

 

[droidkevlar]

.I wouldnt kill you...might take away your Eris and make you use a Iphone....but never death

NOOOOOOO. Take anything but my Eris. I just checked local state law and its still not viewed as a legit marriage in Cali to marry your Eris. So I guess my Eris will still have to be the women on the side until I get a bill passed that makes it legal.

 

[acidbath5546]

NOOOOOOO. Take anything but my Eris. I just checked local state law and its still not viewed as a legit marriage in Cali to marry your Eris. So I guess my Eris will still have to be the women on the side until I get a bill passed that makes it legal.

LMAO...Creepy, but funny

 

[ahjee]

to grdlock

something is obviously wrong haha, or maybe its not i dunno but this seems extensive for command response

1)adb shell mount -o rw,remount/dev/block/mtdblock3/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory

2)adb push recovery.img/sdcard
Android Debug Bridge version 1.0.25

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP disconnect <host
>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb help - show this help message
adb version - show version num

DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB adb
tcpip <port> - restarts the adbd daemon listening on TCP on the spec
ified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

3)adb push flash_image/system/bin
Android Debug Bridge version 1.0.25

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP disconnect <host
>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb help - show this help message
adb version - show version num

DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB adb
tcpip <port> - restarts the adbd daemon listening on TCP on the spec
ified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

4)adb shell chmod 755/system/bin/flash_image
Usage: chmod <MODE> <FILE>

5)adb shell flash_image recovery/sdcard/recovery.img
flash_image: not found

this was the first set of commands i tried using, then i tried another i found in a different thread.

 

[GrdLock]

You're forgetting spaces.

to grdlock

something is obviously wrong haha, or maybe its not i dunno but this seems extensive for command response

1)adb shell mount -o rw,remount/dev/block/mtdblock3/system

adb shell mount -o rw,remount /dev/block/mtdblock3 /system

There's a space after remount and a space after mtdblock3

2)adb push recovery.img/sdcard

There should be a space after .img

3)adb push flash_image/system/bin

There should be a space after flash_image

4)adb shell chmod 755/system/bin/flash_image

Space should be after 755

5)adb shell flash_image recovery/sdcard/recovery.img

Should be a space after recovery before /sdcard

 

[ahjee]

WOOOOW LMAO, ill give it a try, see what happens.
funny thing is the whole time i was wondering if they were spaces or not haha

edit-Thanks to, for responding.

 

[ahjee]

\adb push recovery.img /sdcard
cannot stat 'recovery.img': No such file or directory

i do have the recovery.zip downloaded and unzipped into the android sdk..well i think

 

[GrdLock]

Make sure it's in the same directory as "adb.exe"

 

[ahjee]

adb and the flash and recovery all in tools directory.
it dosent say adb.exe but its the adb application and when i right click then properties it says its an .exe file.

 

[ahjee]

is it possible that its not working cause maybe the link that was posted as the root 2.1 was actually leak 2.1?

 

[GrdLock]

What is the filename of the ROM you used?

 

[ahjee]

i matched up the software info with a rooted eris on you tube and it all matches, so i assume it is the rooted 2.1, as for the file name, do you mean like, Recovery.zip? cause that was the link/download and i saved as that and unzipped then placed the flash_image and recovery.img in the tools directory. sorry if i didnt answer your question and am being redundant

 

[GrdLock]

Type these commands:

adb shell
su

After typing that, you should see a # sign prompt. If you still see a $ prompt, you don't have a rooted rom.

 

[ahjee]

# is what i get. thankfully

 

[GrdLock]

Do you have your sdcard mounted on your computer when you're doing this? Because you shouldn't. Make sure it's set to Charge Only.

 

[ahjee]

yea its on charge only

should i mention to you im running windows?

 

[GrdLock]

Ok, umm.... mount your sdcard in Windows. Copy recovery.img and flash_image onto the root directory of it. Then unmount the card.

Now back in the command prompt:

adb shell
mount -o rw,remount /dev/block/mtdblock3 /system
copy /sdcard/flash_image /system/bin
chmod 755 /system/bin
flash_image recovery /sdcard/recovery.img

(note the linux command prompt is case sensitive, and I can't remember if Recovery.img is capitalized or not, so if it is be sure to type it like that)

 

[ahjee]

adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
mount -o rw,remount /dev/block/mtdblock3 /system
# copy /sdcard/flash_image /system/bin
copy /sdcard/flash_image /system/bin
copy: not found
#

 

[GrdLock]

ahh crap lol my bad... i'm overloading here!

replace "copy" with "cp"

 

[ahjee]

im a screwed lol?
i dunno, for a while this computer wouldnt recognize this eris inparticular (me and my girl each have one)
even if i attached it to the computer and mounted SD it wouldnt recognize it, i couldnt transfer music or anything, untill recently.
I put her sd in my eris and vice versa and plugged each in at a time, then switched them back and now it recognizes mind, not sure if it does hers now though haha. duno if this could have something to do with it though, like the the usb or phones being a different one from the initial hardware install of the phone, am i making sense lol? im sorry ive been up hours trying to figure this out haha