Database Info

Recovery problems

I had a couple problems so i unrooted then rerooted then i kept trying to flash recovery 1.6.2 but it kept comming up with file not found on the sdcard so i put the file in the tools folder and used android commander. It came up with 2 # then the screen went blank and it sat there so after a few minutes i did a battery pull and now i cant boot into recovery. It just sits at the boot screen.

xxwckdxx said:
I had a couple problems so i unrooted then rerooted then i kept trying to flash recovery 1.6.2 but it kept comming up with file not found on the sdcard so i put the file in the tools folder and used android commander. It came up with 2 # then the screen went blank and it sat there so after a few minutes i did a battery pull and now i cant boot into recovery. It just sits at the boot screen.
Click to expand...
Click to collapse
how long has it sat there? sometimes you have to give it a few minutes after going thru all that.

By the way if i dont try to boot into recovery it loads fine how can i reload the reocvery?

Probably 5 minutes and no go

How were you loading it in the first place? Have you checked to see if its on your card? When pushing the image, are you using the exact image name, i.e, v1.6.2-(color).img.? Also, are you holding the end-home keys at the same time long enough to see it come up?

when i first was trying i opened the terminal i had on the phone and typed flash_image recovery /sdcard/recovery-1.6.2.img and it kept comming up with bad filename(wwhich i had renamed the file to that so i dont know why) then i put it in the tools folder and tried the same from commander and it got me to here ;\

What method are you using? Try amon ras or the method used to push it to your card thru root.

havent heard of amon ras.....i just pushed it to the sdcard again and tried the same command and end up with the same thing iam trying to unroot again

nope came up with bootloader error for the unroot

tried using kitchen to reroot but it comes up with errors

Okay, these are Amon RAs methods just depending on what your using:
Install
There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.imgvia fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-heroc-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell reboot
Or thru adb try this:
cd C:\android-sdk-windows\tools
adb shell
adb push recovery-RA-heroc-v<name>/sdcard
adb shell reboot
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.5.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
reboot recovery
This was complements of theresthatguy's method. Hope this helps.

to tell you the truth 1.6.2 is basically the same as 1.5.2 the only diff is the power off option and the carebear color so if you have 1.5.2 you should just keep it since you are having trouble installing it

VoLoDaR1 said:
to tell you the truth 1.6.2 is basically the same as 1.5.2 the only diff is the power off option and the carebear color so if you have 1.5.2 you should just keep it since you are having trouble installing it
Click to expand...
Click to collapse
I had 1.2.3 or whatever it was thats why i was gonna just shoot to 1.6.2 i had done it before but i dont know what happened this time. I tried the way thru adb and it has been sitting so far 10 minutes and it is still sitting at the boot screen

The first one wont work i cant get into recovery.....the second one i get "fastboot is not recognized as a internal command"and the third is the one i have been trying....

im not sure man i had trouble flashing it also try renameing it to something simple like 1.6.2.img and go to better terminal emulator type in su enter than type in the comands to flash it
flash_image /sdcard/1.6.2.img enter
do not enter mount-a before this this was the problem i was having after you hit enter just type in reboot recovery and you should have 1.6.2 also maKE sure this file is the only file on your sd card that helps good luck man let me know what happens

yeah i renamed it to recovery-1.6.2.img and i just downloaded better terminal but how do you get the keyboard up?

just tap the screen

do you have g talk

sent pm to you

ieatstarz1 said:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.5.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
reboot recovery
This was complements of theresthatguy's method. Hope this helps.
Click to expand...
Click to collapse
This is what worked for me.
The 1.6.2 version did exactly to me like it is doing to you. I couldn't boot in to the recovery screen.
Sooo. I pushed the 1.5.2 image to the sdcard and then I
adb shell
su
flash_image recovery /sdcard/recovery-RA-heroc-v1.5.2.img
I was then able to boot into the 1.5.2 recovery
I then pushed the 1.6.2 image again and then it worked.

HowTo re-flash the recovery image after old 2.1 RUU

This guide was taken from AndroidCentral and I thought I would share it here because it's taken me 4 hours this morning to figure out why I was having so many problems trying to flash a recovery image when I know my phone was rooted and flashed in order to get 2.1 a month or so ago. I have been searching these forums and google and hope anyone else who has my issue finds this post.
1. Make sure you have the Android SDK installed.
2. Download flash_image.zip
3. Download recovery-RA-heroc-v1.5.2.img
4. Unzip the first file, and place both in your Android SDK/tools folder.
5. Make sure USB debugging is ON
6. Connect your phone to the PC
7. Open the command window and navigate to the Android-sdk/tools folder on your computer.
8. At the prompt enter the following, one line at a time followed by enter
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
adb push flash_image /system/bin
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb shell
chmod 0755 /system/bin/flash_image
reboot
9. Your phone will reboot. When it is finished, back at your command window, once again enter
Code:
adb shell
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.5.2.img
reboot recovery
10. With any luck, you'll have the recovery image back and can load custom 2.1 based ROMS again.
Hope this helps. All credit goes to gbhil at Android Central.

You might want to change the title of the post. People might get confused thinking you found a way to downgrade the hboot and not how to flash the recovery image.

Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.

bubbacs1 said:
Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.
Click to expand...
Click to collapse
This won't work for the leak that was put out today. You lost root. This process requires root.

bubbacs1 said:
Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.
Click to expand...
Click to collapse
If you used the new RUU that was leaked today you're screwed. The older 2.1 leaks were test ROMs that were already rooted so you could use the instructions above to flash the RECOVERY. Notice recovery in bold, not bootloader. Once hboot is updated there is no known way to downgrade so you could use an older RUU file.

This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.

HeroMeng said:
This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.
Click to expand...
Click to collapse
So they can't run an older ruu with 1.5?

HeroMeng said:
This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.
Click to expand...
Click to collapse
To clear that up, if you run the RUU you have no root. If you extract the ROM, set it up, and flash it, you will preserve root, just like damageless made for all of us. But, yeah, you are not gonna be able to get back from this one. at least until someone figures it out.

I changed the thread title to hopefully alleviate some confusion. I didn't realize there was a newer RUU released.
I flashed the Damageless Rom and it's running smoothly so far, but I'm still trying to figure out why wifi tethering isn't working out for me. :-(

celemew2 said:
I changed the thread title to hopefully alleviate some confusion. I didn't realize there was a newer RUU released.
I flashed the Damageless Rom and it's running smoothly so far, but I'm still trying to figure out why wifi tethering isn't working out for me. :-(
Click to expand...
Click to collapse
Did you get wifi tether version 1_60? That's the only version that ever worked for me.

Yeah, I have 1.60 installed on my phone right now, but when I try to start tethering, a SU Request black screen comes up and nothing happens until I get an error, "Activity SU Request (in application Superuser Permissions) is not responding."
I'm sure there's an answer somewhere, but lately I haven't been having luck searching for it.
Edit:
Thank you 98classic! All I had to do was enable USB Debugging. (I had it turned off cause I didn't like the warning up top when my phone was plugged into the computer)

"flash_image not found" what the f**k

need the binary? physically check its there with a root explorer
Sent from my broken Typewriter!!!

or do this download and set up the android SDK it itself includes the flash_image binary. after that u will need to open a command prompt on your computer u will have to change directory to platform tools
cd /path/to/platform-tools
after that u will get the chance to do
flash_image recovery /path/to/recovery.img
that will flash the recovery
now reboot into recovery
Typed from my broken Typewriter!!!

[Q] adb shell "exec '/system/bin/sh' failed: No such file or directory (2)"

Hey,
Ok so a little backstory before my problem: So I was in the middle of putting a new ROM on my captivate. I had one before but i wanted to change so I put the rom in update.zip and installed it will clockworkmod recovery. It installed fine I think but then when I tried to boot it gets stuck on the boot screen. So i tried to boot in recovery mode. I geld down both the volume buttons and the power button until it reboots twice, then I let go of the power button. but it still gets stuck on the boot screen and does not go into recovery mode. So i plugged it into my computer and using
Code:
adb devices
it shows up under recovery mode. So far so good. I can use the
Code:
adb reboot
and
Code:
adb push
commands fine. but when i try to use
Code:
adb shell
it says
Code:
exec '/system/bin/sh' failed: No such file or directory (2)
So i can not reflash the recovery image. I read that I just needed to mount the /system file. But i do not know how to do this. the "mount" command does not work with adb. I would appreciate anything to help me to either reflash the rom or restore to factory or anything where i can work off of. thanks

I have exactly the same problem.
Did you get to a solution to this?
Good luck, dude.

Is there a solution to this without using a Motorola Factory cable? I don't have the resources to make one and I don't have money to buy one.

I'm not sure putting the rom into "update.zip" was the right choice.
adb shell could fail because the partition is not mounted, the sh binary is not installed, or not at the correct location
If you can still get the captivate into download mode, you could use odin/heimdall to flash a working ROM.

First of all...thanks to everyone that has EVER posted in the XDA forums! I've spent days reading them and I came across one that had a suggested solution for my problem. So let's start...
1) Bricked
2) ADB is finally working again...so..not a problem any longer
(Don't ask me how I got it to work again....I have no idea. System was wiped while using TWRP from a bootloop)
3) Now...with system wiped I have no '/system/bin/sh'
4)adb shell will not work because of this. adb root does not work because of production model. adb remount is not permitted.
Now....I came across a thread that suggest using r2.6.2.kindlefire.boot.insecure.img and zergRush. I have the zergRush file, but I need the r2.6.2.kindlefire.boot.insecure.img to push with adb.
Does anyone know where I can get the r2.6.2 at? Filesonic is disabled and Multiupload will not return page.
Link I came across: addictivetips /mobile/gain-root-adb-access-with-insecure-boot-image-for-kindle-fire/

1.55.531.3 rom?

Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.

I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU

M9x3mos said:
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
Click to expand...
Click to collapse
yeah, what you are looking for doesn't exist at the moment. i too thought about making a nandroid of the the new ROM for people to flash, but since the new setup comes with a new radio, new kernel, new HBOOT, etc., i'm not sure how it would fly if someone just flashed the nandroid?

Hboot n radio would be the only thing missing... Kernels sits in recovery....
rooted 1.55.531.3 with clockwork recovery and SU

I know I made a flashable package out of the Google Talk apk file, and either did or meant to make some out of the other apps in it - I'm not sure which thread it's in.
I can check later and link it. Not sure what else anyone did with it, if wifi calling wasn't pulled forward from it I'll have a package for that sometime soon anyway.
I also never did get a chance to check what the gps changes were I remember being in it.
Edit:
Link to Gtalk flashable zip package from that update.
Sent from my Bulletproof_Doubleshot using xda premium

nlarge said:
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Do you have the stock rom for 1.55.531.3 that I can flash on my mt4gs? I would really appreciate it

http://forum.xda-developers.com/showthread.php?t=1484679
http://forum.xda-developers.com/showthread.php?t=1433805

It would be flashed as if restoring a nandroid. I would flash the above link. If you really want it I can send it
rooted 1.55.531.3 with clockwork recovery and SU

Thanks. Okay, this is where I am:
Unlocked bootloader with htcdev
s-on
hboot 1.45.0013
software 1.55.531.3
Would like to achieve root so that I can flash custom roms/use titanium backup. From what I can tell, nlarge was able to accomplish this. (http://forum.xda-developers.com/showthread.php?t=1474933&page=6). However, couldn't post on that thread because I have less than 10 posts....sorry.
Cannot use temproot (FR3VO) method because says needs s-off and/or adb mount issue:
An error occurred while running the exploit (-1) (errno: 22)
c:\Android>adb wait-for-device
c:\Android>adb remount
remount failed: Operation not permitted
c:\Android>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
c:\Android>adb shell mount -oremount,suid /dev/block/mmcblk0p23 /data
mount: Operation not permitted
c:\Android>adb shell mkdir /vendor/bin
mkdir failed for /vendor/bin, Read-only file system
c:\Android>adb shell chown root.shell /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb push ./sqlite3 /vendor/bin
cannot stat './sqlite3': No such file or directory
c:\Android>adb push ./su /vendor/bin
cannot stat './su': No such file or directory
c:\Android>adb push ./busybox /vendor/bin
cannot stat './busybox': No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell chmod 6555 /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chmod 4555 /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell busybox --install -s /vendor/bin
busybox: permission denied
c:\Android>adb shell sync
c:\Android>adb shell chmod 6555 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb install ./Superuser.apk
can't find './Superuser.apk' to install
c:\Android>pause
Press any key to continue . . .​
So, I understand, permission denied/operation not permitted, I assume because I don't have root.
When I look at superuser, it says "su binary voutdated" and when I tap to check for updates, automatic update fails and error message "su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Can't boot into recovery mode, phone just sits on mytouch 4g slide screen. Again, I assume because no root. Same thing happens if I try to factory reset, just stays on the mytouch 4g slide screen.
Anyone have any suggestions? I am going crazy trying to get this phone to work. I would really appreciate the help!

Flash clock work recovery... I think I linked it somewhere... Or Google will help
rooted 1.55.531.3 with clockwork recovery and SU

Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU

nlarge said:
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!

Put your phone in fastboot. Pull battery, hold down and power then try again
rooted 1.55.531.3 with clockwork recovery and SU

How to fastboot flash recovery
Return to Contents Page - doubleshot Developers Reference
Boltinghouse said:
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Click to expand...
Click to collapse
(hah, thanked but meant to hit quote)
What you need to do is go here: http://clockworkmod.com/rommanager
Scroll down the list and find the recovery for our device (5.0.2.7 for the myTouch 4G Slide) - download this.
Put it in the same folder as 'fastboot.exe' on your computer. Rename it to recovery.img
On your phone, turn off 'fastboot' in power options.
Power off the phone.
Now, give it a minute to power off - then hold the volume down button and press power.
Now it will boot up to the hboot menu. The list presented will have you highlighted on the word 'fastboot' - press power to choose this.
Now you are presented with the fastboot menu. It should say fastboot with a red highlight around it near the top.
At this time you should plug the USB cord from your computer into the phone. It will update to say fastboot USB in red highlight now.
-okay-
We have the phone booted up in fastboot, attached to the computer, and ready to work with.
Open up your command prompt, and navigate to the folder where you have the fastboot command. This is the same folder that you have the new clockworkmod recovery.img in from before.
In your terminal now type:
Code:
fastboot devices
This will come back with your device, serial number, and show you it is connected and ready to go. (if it is not something is wrong)
Now type:
Code:
fastboot flash recovery recovery.img
Let's break this down:
fastboot = activates the fastboot.exe command, and says that what's typed next uses the definitions in that fastboot.exe file.
flash = command that says write to
recovery = destination (name of partition) being written to
recovery.img = file written to previously defined location.
----
Since you have the new clockworkmod recovery file in the same folder as fastboot.exe, and you renamed it to recovery.img, then the previously shown command will overwrite your stock recovery with the new image you are providing it.
At this point you should have clockworkmod recovery in place of your stock recovery when you boot the device to hboot menu and select recovery.
Let us know if you have any other problems.

Good explanation blue.... It sounded like he knew what he was doing, hence my quick correction...
Hate typing a lot out from phone!
rooted 1.55.531.3 with clockwork recovery and SU

OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~

Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
Boltinghouse said:
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Click to expand...
Click to collapse
rooted 1.55.531.3 with clockwork recovery and SU

nlarge said:
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
It's all good, I know being a chick I'm in the minority here. Either way, thank you so much.

So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?

it depends on what you want to do with your phone...
If you just want to be able to make recovery and flash ROMS than you dont need s-off
If you want to play with other stuff(radios and mounts) then you need s-off.
I personally like doing things to my phone so I would like to get to s-off. I am ok with it for now, but S-off will give me the full control I want.
qwerty3656 said:
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
Click to expand...
Click to collapse

[HowTo] Infuse ADB Flashing Guide - Kernels, Roms, Modified 3e Recovery, Busybox

ABOUT:
This tutorial explains how to use adb to flash the following items starting from a UCLB3 base w/ root.
- Custom kernel w/ CWM recovery
- Modified 3e recovery
- Custom firmware (ROMS)
- Busybox
These instructions will most likely work coming from other rooted Infuse firmwares, but were tested starting from my Odin UCLB3 Unbrick package with root.
ADB SETUP:
Download: adb.zip
Download: SAMSUNG_USB_Driver_for_Mobile_Phones.exe
Setup instructions are for Windows, but adb is also available for Linux and Mac.
a.) If necessary, uninstall any previous Kies or Samsung USB Driver installations, and install the Samsung USB driver from the above download link.
b.) Unzip contents of adb.zip and copy the folder contents to C:\Windows\
c.) If your phone is booted up and running, make sure you select USB debug mode in settings. ADB also works in CWM recovery, and in modified 3e recovery.
d.) To test your installation, open a command prompt (Press WINDOWS KEY + R - type cmd - press Enter).
Type:
Code:
adb devices
If all is working, you will see your device listed.
Some quick command tips:
To move a file from your computer to the phone, "push" it:
Code:
adb push myfile.zip /directory-on-phone/
Of course, you need to be in the computer directory for your file in the command line to push it to the phone.
To get a file from your phone onto your computer, "pull" it:
Code:
adb pull /sdcard/myfile.zip
To access a command prompt for the phone:
Code:
adb shell
Inside that shell, you can use unix commands from within the Android OS to manipulate your phone.
------------------------------------------------------------
INSTRUCTIONS FOR GINGERBREAD:
(Scroll down for ICS Instructions.)
------------------------------------------------------------
Instruction steps must be followed in order.
Step 1: Use adb to install a custom kernel
Download: flash_image.zip (Extract and use flash_image for instructions below.)
You'll also need a Gingerbread kernel zImage.
Code:
adb push flash_image /data/local/tmp/flash_image
adb push zImage /data/local/tmp/zImage
adb shell
$ su
# chmod 755 /data/local/tmp/flash_image
# chmod 755 /data/local/tmp/zImage
# /data/local/tmp/flash_image boot /data/local/tmp/zImage
# reboot recovery
Step 2: Use adb to install modified 3e recovery
Necessary for Step 3.
Download: 3e_recovery_no_sig_check.zip (Extract and use recovery for instructions below.)
Code:
adb remount
adb push recovery /system/bin/recovery
adb shell "chmod 755 /system/bin/recovery"
adb reboot recovery
Step 3: Use adb to install a custom firmware
This step uses the modified 3e recovery to flash unsigned firmware.
You'll need to download the zip file for the Gingerbread (or possibly Froyo) rom that you would like to flash. These instructions have been tested by flashing my Ethereal rom.
Replace YourFirmware.zip with the actual name of your rom zip.
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
Let firmware flash complete, and then type:
Code:
adb reboot
EXTRA: Use adb to install busybox
Download: Busybox-1.20.2.zip (Extract and use busybox for instructions below.)
Code:
adb remount
adb push busybox /system/xbin/busybox
adb shell
# chmod 755 /system/xbin/busybox
# ln -s /system/xbin/busybox /system/bin/busybox
# /system/xbin/busybox --install -s /system/xbin
# exit
----------------------------------------
INSTRUCTIONS FOR ICS:
----------------------------------------
STEP: Use adb to flash an ICS kernel; then use blue CWM recovery to install an ICS rom.
Download: flash_image.zip (Extract and use flash_image for instructions below.)
You'll also need an ICS kernel boot.img and it is recommended that you push an ICS rom zip to your sdcard. Once you are in blue CWM recovery, you won't be able to use adb to push anything else to the device.
Replace YourFirmware.zip with the actual name of your rom zip.
Code:
adb push YourFirmware.zip /sdcard/
adb push flash_image /data/local/tmp/flash_image
adb push boot.img /data/local/tmp/boot
adb shell
$ su
# chmod 755 /data/local/tmp/flash_image
# chmod 755 /data/local/tmp/boot
# /data/local/tmp/flash_image boot /data/local/tmp/boot
# reboot recovery
From here, just follow the normal instructions for flashing your ICS rom in blue recovery.
I'll add to these instructions as I find more for ICS, and as support increases for adb in the CWM recovery we're using in ICS roms. At this time, adb support isn't fully working in Infuse ICS CWM recoveries. If you use adb to get an ICS kernel / CWM recovery combination, just use the recovery menu to do anything else. If you need to get other files onto the device while in blue CWM recovery, go to mounts and storage, mount /sdcard/, and mount USB storage.
Hope this is useful to someone else. I mainly wanted to see how much could be done with just adb, and I learned quite a bit about how the phone works in the process.

Wow my friend...nice and thx for what you provide the Infuse Community.
It is people like you, why i stay!

very nice how-to!

bigjoe2675 said:
Wow my friend...nice and thx for what you provide the Infuse Community.
It is people like you, why i stay!
Click to expand...
Click to collapse
SiL3nTKiLL said:
very nice how-to!
Click to expand...
Click to collapse
Thanks fellas. And, by the way, I know that most general users aren't going to use adb to flash kernels and firmware. It's of course easier to use all of the Heimdall one-click and Odin tools that we have - as well as the Infuse Toolkit, Heimdall suite, SGS Kernel Flasher, and CWM recovery. So, for the person asking, "Why would someone still do this, when we have all of the tools that we have?" - this isn't for you.
I approached this from the standpoint of asking, "What if we didn't have access to all of the easy tools?".
At some point, if someone is having issues with Odin and Heimdall, or if they can't use their hardware buttons, maybe they will find this useful. I like to do things from the command line and not have to touch the phone while I'm working on development stuff - plus I type fast, and since I spent years in the command line on Slackware linux, prefer using unix commands. I'm actually faster at CLI stuff than with GUI stuff, plus I like the control that CLI gives you.
I had to help a forum member restore his phone over a remote tech support session using https://join.me/ . He claimed that he couldn't get Heimdall or Odin to recognize his phone. I was able to use adb to do things from his computer, which was helpful, since I couldn't see or directly use his phone. I had to ask him to do some things on the phone, so I later wanted to figure out how to do more using just adb. That's what this is all about. If I had to help someone over a remote session now, I could do most everything without them ever touching their phone.

First of all thank you very much for the guide, but I seem to be having a problem
Whenever I try this:
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
the first issue is the phone reboots but continues to system and not to recovery.
now if I manually make it boot recovery, CWM gives me an error that it couldn't mount: SDCARD:update.zip
the update.zip that I'm trying to flash is CM9 RC2, also tried other zip files and also failed.
what am I doing wrong ?!
Thanks in advance.

DeepUnknown said:
First of all thank you very much for the guide, but I seem to be having a problem
Whenever I try this:
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
the first issue is the phone reboots but continues to system and not to recovery.
now if I manually make it boot recovery, CWM gives me an error that it couldn't mount: SDCARD:update.zip
the update.zip that I'm trying to flash is CM9 RC2, also tried other zip files and also failed.
what am I doing wrong ?!
Thanks in advance.
Click to expand...
Click to collapse
If you follow the steps correctly from Gingerbread (including the step to install modified 3e recovery), and replace "YourFirmware.zip" with the name of your firmware, these adb commands use 3e recovery to flash firmware. These flashing instructions are not for CWM recovery, and the steps you are following aren't for flashing ICS from Gingerbread. Look further down in the first post for ICS adb instructions.
Sent from my SGH-I997 using Tapatalk 2

jscott30 said:
If you follow the steps correctly from Gingerbread (including the step to install modified 3e recovery), and replace "YourFirmware.zip" with the name of your firmware, these adb commands use 3e recovery to flash firmware. These flashing instructions are not for CWM recovery, and the steps you are following aren't for flashing ICS from Gingerbread. Look further down in the first post for ICS adb instructions.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for clearing it up. The reason why I used that method is because I looked online and I found it on another forum and the post owner didn't mention anything about it should be used with GB.

infuse CM9 rainbows
I'm caught with a half-done CM9 install of the infuse upgraded from cm7.
Somehow I was able too boot once sucessfully into CM9 though with the initial rainbow screen, but now my device hangs in recovery which is also garbled. I've been searching all over for a nice thorough guide to getting this thing going again and your post here was the only one I found remotely applicable to my situation.
I've been trying your ADB instructions for flashing with ICS but I'm stuck at second step: where I only get: cannot stat "flash-image": no such file or directory.
Since I'm stuck in CWM recovery none of the other options seems to see my device, ie. Heimdall or Odin.
Is there a better solution out of my woes?
Excuse my noobiness.

By stucked at recovery you mean it always boots up into recovery (recovery bootloop)?
You should go back to ULCB3 stock, preferably using Jscott's "option C" and flash the GB bootloaders. Then proceed to installing CM9, and remember to do a double flash. (wipes, flash, reboot, phone hangs, boot into cwm with 3-finger combo, wipe and flash!)
This way you'll solve both the recovery bootloop and the rainbows, and bring you CM9
Sent from my sweet and buttery Infuse

andros11 said:
By stucked at recovery you mean it always boots up into recovery (recovery bootloop)?
You should go back to ULCB3 stock, preferably using Jscott's "option C" and flash the GB bootloaders. Then proceed to installing CM9, and remember to do a double flash. (wipes, flash, reboot, phone hangs, boot into cwm with 3-finger combo, wipe and flash!)
This way you'll solve both the recovery bootloop and the rainbows, and bring you CM9
Click to expand...
Click to collapse
Yes the problem right now is that the only understandable thing I get out of the phone is the samsung logo at boot.
I think it goes into recovery but I can't really tell because the screen is garbled. Also using "adb reboot download" seems to make no difference to Odin or Heimdall which both refuse to see the phone.
I would love to find out exactly which state the phone is in but my knowledge of adb isn't that great to say the least.
How do I flash bootloaders using adb only?
I totally appreciate your help Andros, totally out of luck with this so far.

The only way to flash bootloaders is in download mode using either odin or heimdall.
Adb reboot download should get you into download mode as long as you have adb access while on recovery. If not, get into download mode this way:
Take out battery, and put it back in.
Hold both vol+ & vol- (don't press power)
plug in usb cable to phone.
Once in download mode, your phone should be recognized by Odin. If not, try reinstalling the drivers using the ones in the iset thread.
There are many threads about this situation that should also help you out, just search around
Sent from my sweet and buttery Infuse

Okay, somehow I missed how to use the keys to enter download state.
In my mind using adb to enter download state should be the same as the keys but somehow that isn't the case.
Got the GB bootloaders installed and used an odin package and then redid the CM9 installation.
Sorry about spamming this thread, and thanks to andros for getting me going again.

Interesting, I also didn't know that could make a difference. Lesson learned lol
Glad you got it running again
Sent from my sweet and buttery Infuse

hi , i am having serious problem ,
my i997 was ok before after doing a mess , now its in 3e reocvery restarts in samsung logo comes to 3e recovery again and so on.....i did everything ,flashed with I997UCKH1 but all in vain .
Could somebody guide what to do ?

umairrashid1 said:
hi , i am having serious problem ,
my i997 was ok before after doing a mess , now its in 3e reocvery restarts in samsung logo comes to 3e recovery again and so on.....i did everything ,flashed with I997UCKH1 but all in vain .
Could somebody guide what to do ?
Click to expand...
Click to collapse
Use odin or heimdall to repartition back to uclb3 stock.

andros11 said:
Use odin or heimdall to repartition back to uclb3 stock.
Click to expand...
Click to collapse
i used heimdall ,it flashed successfully but still no result .
how to do he same using odin ?
could you please add more steps in order o recover the phone fully .
i am in a big problem .