Related
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.
Any of us who have installed ROM Manager from the market have gone through some real pain trying to recover from using its recovery. Until it is verified as fully functional by one of this forum's top devs, do not install it! It's not ready for prime time.
Instead, use krylon360's outstanding CWM Recovery here: http://forum.xda-developers.com/showthread.php?t=1099374. Follow the directions in the OP carefully.
Also, check mad_fitter's great thread on steps needed to flash on this phone. Step 12 addresses what happens if you try and flash using ROM Manager's recovery (ODIN):
http://forum.xda-developers.com/showthread.php?t=1122508
I see that contributing members are still having these issues and hope to help drive the point home. ROM Manager will be great when it works for our device, but right now it doesn't.
Sent from my SGH-T959V using XDA Premium App
I was able to use ROM manager on my device. The only thing that CWM doesn't seem to do is:
(might need to remount system as r/w)
// change permission on recovery binary so we can replace it
su
cd /system/bin
chmod 777 recovery
exit
exit
// push new recovery binary
adb push recovery /system/bin
Once this is performed the CWM from ROM manager works fine.
I just did my co-worker's SGS4G and can confirm this.
matthenry87 said:
I was able to use ROM manager on my device. The only thing that CWM doesn't seem to do is:
(might need to remount system as r/w)
// change permission on recovery binary so we can replace it
su
cd /system/bin
chmod 777 recovery
exit
exit
// push new recovery binary
adb push recovery /system/bin
Once this is performed the CWM from ROM manager works fine.
I just did my co-worker's SGS4G and can confirm this.
Click to expand...
Click to collapse
Hmmm. Can you send this to koush
I had to use recovery file from krylon360's CWM Recovery to make my ROM manager work. It works fine for me.
But of late it gets stuck while recovering on the .andriod_secure folder. Which i think is the last step on the recovery.
No big deal, just pull the battery out and power the phone back on and everything is back to normal.
Yeah that last part it hangs on isn't a big deal. I believe that is where the apps2sd apps are stored and it's not a big deal of that isn't wiped.
Anytime you wipe it's gonna hang as well as any time you do a restore. It will hang while restoring that same dir but once you get to that point system and data have already been restored so you can just pull the battery and reboot from recovery.
Sent from my SGH-T959V using XDA Premium App
Update on 9/11/11: Thanks to phburks there is now a flashable zip to root the G2X stock rom. He figured out that the update-binary we were using was not compatible with the G2X. He found the compatible binary that allows us to create flashable zip files. Hats off to phburks. This is an unsigned zip and you should not be required to toggle signature verification. Of course the files required to root the phone (su and Superuser.apk) were created by Chainsdd.
There are two flashable zip packages. The first one roots the G2X. You simply flash it with Clockworkmod Recovery. The second zip unroots the phone for those who wish to unroot their device for whatever reason.
After rooting go to the Android Market and get the Busybox installer referenced below. Use that to install and keep Busybox updated.
Root Zip for G2X: http://www.mediafire.com/?92qpr525ztblh8w
Unroot Zip: http://www.mediafire.com/?2vr7cmgg7qcdn14
HOW TO ROOT
1. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
2. Download the root zip package referenced above.
3. Put the zip package on your internal or external sd card on your G2X. Do not unzip the package.
4. Turn off phone and boot into Clockworkmod Recovery by pressing volume down and power and hold until the fancy LG (second one) appears.
5. Select install zip from sd card. Select and flash the root zip package. Note: You navigate in Clockwordmod Recovery by using the volume keys up and down and commit the action by pressing the power button.
6. Reboot your phone. You are now rooted.
NOTE: THE FOLLOWING BELOW IS OBSOLETE. IT IS LEFT FOR HISTORICAL PURPOSES ONLY.
Original post made on 9/9/11:
I wanted to run the stock Gingerbread ROM and wanted to root it without flashing a new ROM. I was able to succesfully do it and the instructions are below. I was attempting to make an update.zip to do this but it kept getting a "status 0" error. The original superuser zip by ChainDD also gets this error. So I decided to try and root it using ADB commands while running Clockworkmod Recovery. Here is how I did it. If someone can help me get an update.zip that will install without error in Clockworkmod Recovery to make this easier for people to install it would be much appreciated.
1. Download my G2X root package that includes necessary ADB files (Android SDK install not required) and unzip the contents. The package contains the latest versions of “su” and “Superuser.apk”.
http://www.mediafire.com/?6rdrdfxvdoq9nkv <download link for my root G2X package>
2. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
3. Boot into Clockworkmod Recovery by holding down volume down and power until fancy LG logo shows (about ten to fifteen seconds). This is not the first one displayed when the phone powers up. Wait for recovery to start. Just to be safe perform a backup of your device’s current state.
4. Using the recovery menu scroll down to “mounts and storage,” press the power button, scroll down to “mount system” and press the power button.
5. Now that your system is mounted plug your phone into your computer (let drivers install if you have not done before – requires LG USB driver package).
http://bit.ly/qyoAxY <shortened link for direct download from LG server>
6. Open a command prompt windows on your computer. In the command prompt window change to the directory to where you unzipped the G2X root package.
7. Issue the following ADB commands. Do not type the the text in the brackets <>. That is just information on what the command is doing.
adb kill-server
<make sure no conflict with another version of adb server running>
adb devices
<checks to see if phone is connected to adb>
adb push system /system
<make sure you type a space before “/system”>
adb shell chmod 6755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
<make sure you type a space before “/system/xbin/su ”>
8. System is now rooted. You can unplug the USB cable now.
9. Now in Clockworkmod Recovery choose “unmount system.”
10. Go back to the main menu and choose “reboot system now.”
11. If you want busybox (some root programs such as Titanium Backup require it) on your system go to the Android Market after rebooting your phone and search on “Busybox.” Download and run the Busybox installer by Stephen (Stericson). When you are prompted allow it to have superuser permissions.
http://bit.ly/qIAoXZ <link to Android Market page for Busybox>
12. You are now rooted with a working busybox installation.
13. It is a good idea to go back into recovery and make a backup of your newly rooted system before you start installing and running programs that obtain superuser permissions.
14. Enjoy the power!
Please click the Thanks button if this helped you out.
Reserved for future use.
Much appreciated for the help, but I don't think I will be using it.
Why not just load a rooted GB or xboards GB, same thing isn't it? lol.
Paul Nur said:
Much appreciated for the help, but I don't think I will be using it.
Why not just load a rooted GB or xboards GB, same thing isn't it? lol.
Click to expand...
Click to collapse
This is for people who have been using the phone after applying the update and don't want to start from scratch again. This lets you just root the phone without needing to flash a rom and format the system.
Wow, I've been waiting fire this thanks jboxer.
Sent from my LG-P999 using XDA App
jboxer said:
This is for people who have been using the phone after applying the update and don't want to start from scratch again. This lets you just root the phone without needing to flash a rom and format the system.
Click to expand...
Click to collapse
Ohhhhhhhhhhhhhhh, I got it lol thanks for showing me it from a different angle
still realy no point xboarders is more stable and much faster then stock and all u need to do is flash his rom then go to advanced restore and only restore data ive gotten away with that doesnt always work though
Always good to have more options.
phburks said:
Always good to have more options.
Click to expand...
Click to collapse
Damn straight. Keep it up, jboxer.
Sent from my LG-P999 using xda premium
Very nice! Thanks man, much appreciated.
Sent from my LG-P999 using XDA App
awesome i tried it on another g2x phone running 2.3.3 root the phone so fast plus with no lost data
thread rated 5 stars ^-^
Change Directory
jboxer said:
I wanted to run the stock Gingerbread ROM and wanted to root it without flashing a new ROM. I was able to succesfully do it and the instructions are below. I was attempting to make an update.zip to do this but it kept getting a "status 0" error. The original superuser zip by ChainDD also gets this error. So I decided to try and root it using ADB commands while running Clockworkmod Recovery. Here is how I did it. If someone can help me get an update.zip that will install without error in Clockworkmod Recovery to make this easier for people to install it would be much appreciated.
1. Download my G2X root package that includes necessary ADB files (Android SDK install not required) and unzip the contents. The package contains the latest versions of “su” and “Superuser.apk”.
http://www.mediafire.com/?6rdrdfxvdoq9nkv <download link for my root G2X package>
2. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
3. Boot into Clockworkmod Recovery by holding down volume down and power until fancy LG logo shows (about ten to fifteen seconds). This is not the first one displayed when the phone powers up. Wait for recovery to start. Just to be safe perform a backup of your device’s current state.
4. Using the recovery menu scroll down to “mounts and storage,” press the power button, scroll down to “mount system” and press the power button.
5. Now that your system is mounted plug your phone into your computer (let drivers install if you have not done before – requires LG USB driver package).
http://bit.ly/qyoAxY <shortened link for direct download from LG server>
6. Open a command prompt windows on your computer. In the command prompt window change to the directory to where you unzipped the G2X root package.
7. Issue the following ADB commands. Do not type the the text in the brackets <>. That is just information on what the command is doing.
adb kill-server
<make sure no conflict with another version of adb server running>
adb devices
<checks to see if phone is connected to adb>
adb push system /system
<make sure you type a space before “/system”>
adb shell chmod 6755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
<make sure you type a space before “/system/xbin/su ”>
8. System is now rooted. You can unplug the USB cable now.
9. Now in Clockworkmod Recovery choose “unmount system.”
10. Go back to the main menu and choose “reboot system now.”
11. If you want busybox (some root programs such as Titanium Backup require it) on your system go to the Android Market after rebooting your phone and search on “Busybox.” Download and run the Busybox installer by Stephen (Stericson). When you are prompted allow it to have superuser permissions.
http://bit.ly/qIAoXZ <link to Android Market page for Busybox>
12. You are now rooted with a working busybox installation.
13. It is a good idea to go back into recovery and make a backup of your newly rooted system before you start installing and running programs that obtain superuser permissions.
14. Enjoy the power!
Please click the Thanks button if this helped you out.
Click to expand...
Click to collapse
Hi,
Sorry i'm new on rooting android phone.
on step 6. how i change the directory in the command prompt to go to the g2x root file i saved?
thanks
yogieajuz said:
Hi,
Sorry i'm new on rooting android phone.
on step 6. how i change the directory in the command prompt to go to the g2x root file i saved?
thanks
Click to expand...
Click to collapse
That's a Command Prompt windows on your computer. The easiest way is to open the desired folder in Windows Explorer and then click on the address bar. Highlight the entire location and copy it. Then in your command prompt windows type "cd" a space, right click and paste the copied location and hit return. You will now be in the correct folder in your command prompt windows.
Thank you for quick reply
jboxer said:
That's a Command Prompt windows on your computer. The easiest way is to open the desired folder in Windows Explorer and then click on the address bar. Highlight the entire location and copy it. Then in your command prompt windows type "cd" a space, right click and paste the copied location and hit return. You will now be in the correct folder in your command prompt windows.
Click to expand...
Click to collapse
Thanks jboxer, work like charm....
but when i did back up they said error can not back up image data ???
whats wrong???
never mind, i found out i run out of space on my sd card
@jboxer, I figured out the flashable zip. Just tested it on an unrooted 2.3.3 installation and it worked perfectly. I PM'd you a link to the zip. Please add it to your OP if you'd like. There's no need for me to create a separate thread.
phburks said:
@jboxer, I figured out the flashable zip. Just tested it on an unrooted 2.3.3 installation and it worked perfectly. I PM'd you a link to the zip. Please add it to your OP if you'd like. There's no need for me to create a separate thread.
Click to expand...
Click to collapse
Thanks to phburks for the good work in figuring out why our update zip packages were being rejected by Clockworkmod Recovery. We now have flashable zips to root the G2X (works on stock GB rom) and to unroot it. They are listed in the first post that I have edited.
http://forum.xda-developers.com/showthread.php?p=17398464
I have a Samsung galaxy showcase through cellular south and on android 2.2 my phone is rooted using superoneclick i am trying to get cwm on it so i can install miui and all the forums dealing with this arent exactly breaking it down so the average user can understand. its not that i dont appreciate their effort because im sure these threads help alot of people but im not familiar with this phone i have done these steps on a motorola milestone with no problems but i need help with this samsung. please if any one out there can help by giving me step by step instructions to get the clockworkmod on it so i can flash roms through the recovery i would be eternally greatful.
I'm looking for the same answer, I would be greatful also.
how to install miui on cspire samsung galaxy s showcase
this will erase your phone data make sure you back up your phone contacts photos or anything you dont want to lose because this will reset it all.. i am not responsible for your phone but i have done this about 4 times on my phone in the past few days as i have been testing other roms and havent had a problem.
Netflix will not work on this rom for some reason. all these files can be found on xda or google i will not post links because im not sure of the forum rules.
Download:
ee25 stock firmware
atlas v 2.2.pit
cwm4 fixed for cms odin
miui showcase v8(copy this zip file to your phones sd card)
step 1. plug in your phone to your computer and let it install all the drivers for your phone.
step 2. open odin and take the battery out of your phone plug it in the computer while holding volume down button you will see yellow triangle
step 3. select pda and find where you downloaded the ee25 stock firmware. make sure you unzip this file if needed as it will most likely be compressed when you download this. select pit and find the atlas v2.2.pit file make sure the re-partition option is checked then click start. 5 minutes later it will finish when it says pass click reset. unplug phone and boot it up.
step 4. turn phone off remove battery and plug into computer while holding volume down button to get in download mode. open odin again and select pda and select the cwm4 zip file(this one you should leave zipped)make sure you uncheck the repartition box and press start. when it says pass press reset. unplug phone and install battery but dont turn the phone on yet.
step 5. press volume up down and power button at the same time dont let go till you see the second samsung logo then let go now you are in recovery..wipe data then wipe cache then select advanced and wipe dalvek cache select go back select install zip from sd then select choose zip from sd then choose the miui file you put on your sd card thats it it will install then select reboot give it 5 minutes to reboot and dont be surprised when your phone starts talking to you then your done you will have miui and be rooted. i hope this helps
the ee25 stock firmware is the cellular south or cspire firmware so this will work for cspire. if you are on another provider i recommend you find out what your stock firmware is
make sure abd shell installed on your pc first
You will need to install redbend_ua first extract the zip file then;
adb push path/to/redbend_ua /sdcard/redbend_ua
then you need to make it executable
adb shell
su
chmod 777 /sdcard/redbend_ua
Now you need to move it to the /system/xbin
adb shell
su
mv /sdcard/redbend_ua /system/xbin/redbend_ua
Take the zImage file and push it to the sd card.
adb push path/to/zImage /sdcard/zImage
Finally we need to flash the zImage
redbend_ua restore /sdcard/zImage /dev/block/bml8
Now you can download clockworkmod from market and install the fascinate version of recovery. When you get done you can then flash the attached zip and it will replace your stock phone kernel with the modded one giving access to bln and some other stuff.
if it helps please hit thanks button
---------- Post added at 09:25 PM ---------- Previous post was at 09:23 PM ----------
have abd shell installed first
You will need to install redbend_ua first extract the zip file then;
adb push path/to/redbend_ua /sdcard/redbend_ua
then you need to make it executable
adb shell
su
chmod 777 /sdcard/redbend_ua
Now you need to move it to the /system/xbin
adb shell
su
mv /sdcard/redbend_ua /system/xbin/redbend_ua
Take the zImage file and push it to the sd card.
adb push path/to/zImage /sdcard/zImage
Finally we need to flash the zImage
redbend_ua restore /sdcard/zImage /dev/block/bml8
Now you can download clockworkmod from market and install the fascinate version of recovery. When you get done you can then flash the attached zip and it will replace your stock phone kernel with the modded one giving access to bln and some other stuff.
if it helps hit thanks
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 .