Database Info

recovery not coming up

I have rc28 g1, was trying to install new recovery image to phone. First reboot i held down home and power and released (didn't hold down till i got recovery triangle....forgot)
Now I hold down home and power together but recovery doesn't come up.... just loads the phone (phone works fine). Recovery screen did work before, I restored phone to defaults before activating.
If i hold down camera, the three colors screen does come up.
Be kind and help a bro out...
thanks

If you still have root, just reflash the recovery.img
1. Extract recovery.img from RC28 update.zip or get modified recovery.img
2. Copy recovery.img to the microSD using usb mount or external usb reader. Make sure to unmount the usb device before disconnecting.
3. Get root prompt somehow (telnetd+Telnet.apk or adb)
4. Do the following:
Code:
# mount -o remount rw /system
# cd /system
# cat /sdcard/recovery_testkeys.img > recovery.img
# flash_image recovery recovery.img
5. Turn off the phone completely by holding down red button.
Recovery should now work. Hold down Home+Red until it appears.

got recovery back
I guess its important to unmount usb before ejecting.
thanks jashsu

[Q] CWM and .android_secure problem

Did anyone find a fix for it yet? Anything that winds up restoring .android_secure causes the phone to hang. It's getting really annoying, not sure if I read about a fix anywhere though.
EDIT
Just saw that this is a dupe thread, check here instead:
http://forum.xda-developers.com/showthread.php?p=14728596

FBis251 said:
Did anyone find a fix for it yet? Anything that winds up restoring .android_secure causes the phone to hang. It's getting really annoying, not sure if I read about a fix anywhere though.
Click to expand...
Click to collapse
You need to have made a clean backup with Krylon360's FINAL CWM, not ROM Manager.
CWM Final is v3.0.2.8
I backed up and restored .android_secure via that version without issue. It's related to the Rom Manager version that causes issues.

Iv been looking into it with dsexton and its a file on your sd card. Also you should only use krylons cwm
Sent from my SGH-T959V using XDA Premium App

I had that problem with the rom manager version of CMW too but if you let it sit on the hangup for a few minutes then just hold the power button until your phone restarts let it boot and your phone will be restored
Sent from my SGH-T959V using XDA Premium App

So I flashed CWM v.3.2.0.0 from ROM manager v.4.3.1.5 but have not yet backed up the phone's original stock ROM. Is there a workaround so I can use krylon360's CWM FINAL instead?

(smint) said:
So I flashed CWM v.3.2.0.0 from ROM manager v.4.3.1.5 but have not yet backed up the phone's original stock ROM. Is there a workaround so I can use krylon360's CWM FINAL instead?
Click to expand...
Click to collapse
Just dont use that..only use kyrlons

no CWM love
Looking for some help here. I am unable to get into recovery and therefore cannot do a nandroid backup and get to ROM-ing / hacking on my phone. Here's what I've done.
In linux I used the following commands to write krylon360's files to my phone:
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#exit
$exit
adb push update.zip /mnt/sdcard
adb push recovery /mnt/sdcard
adb push recovery /system/bin
Next I've tried the following to get into recovery and make a nandroid backup.
1.) simultaneously hold down volume up, volume down and power button.
result: phone stops at Tmobile/GalaxyS splash screen.
if I hold down the power button and reboot, I get a frozen progress star and large battery icon displayed in the middle of the screen. This is the same result for every variation.
repair- pull battery out of phone, put back, power on and execute:
adb reboot
2.) execute: adb reboot recovery
result: phone stops at Tmobile/GalaxyS splash screen.
repair, execute:
adb reboot
3.) selected recovery from ROM Manager
result: phone stops at Tmobile/GalaxyS splash screen.
repair- pull battery out of phone, put back, power on and execute:
adb reboot
Any ideas?

[Recovery]CWM Recovery&Bootmenu 2ndinit for Motorola XT300(Spice)

Do it at your risk!
Hi,everybody.
I had successfully ported CWM recovery&Bootmenu 2ndinit for spice,which allows us to use custom rom.
Now,you have two ways to use CWM recovery.One is entering CWM recovery through bootmenu,the another way is entering CWM recovery through stock recovery(Fake flash update zip).
Method 1:Through bootmenu
First of all,you need to root your spice.And then install bootmenu.
Download the bootmenu.tar file(attached).And push it into /sdcard/
Turn on usb debugging on your phone. And use the following commands in adb:
Code:
C:/> adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock1 /system
# mkdir /system/bootmenu
# cd /system/bootmenu
# busybox tar -xf /sdcard/bootmenu.tar
# rm /system/bin/charge_only_mode
# busybox ln -s /system/bootmenu/binary/bootmenu /system/bin/charge_only_mode
# sync
# mount -o remount,ro /dev/block/mtdblock1 /system
# exit
The bootmenu will be installed.
Restart your device once.
Using Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the red led on your phone will light up for just 3 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Then you can select enter CWM recovery.(Someone say CWM's backup&restore cannot work,you can use method 2 for it)
Method 2:Through stock recovery(Fake flash zip)
I found that we can use CWM recovery with stock recovery leak(Fake flash update zip,like OpenRecovery),but this leak is only existed in SESGC_U3_10.10.0_RT firmware.
I have dumped this recovery(Attached file:recovery.img).And flash it by fastboot.It works well with SESLA_U3_01.72.0 firmware.
And then to flash a fake update.zip(Attached file:update.zip) from the root of your sdcard,you will enter CWM recovery!
By the way,if you want to port CM7 for spice,you need to use 2ndinit for your froyo/gingerbread,because it has locked bootloader.
I have compiled CM7 for it,and it can boot up but stuck in white screen after CM bootanimation.If you want to continue my work,you can checkout my github.
Thanks to:
CyanogenMod
koush
...
sorry for my poor English.

With the first method i can't make a nandroid backup, i'll try it with the second!

Nand backup question
GentryLamp said:
Do it at your risk!
Hi,everybody.
I had successfully ported CWM recovery&Bootmenu 2ndinit for spice,which allows us to use custom rom.
Now,you have two ways to use CWM recovery.One is entering CWM recovery through bootmenu,the another way is entering CWM recovery through stock recovery(Fake flash update zip).
Method 1:Through bootmenu
First of all,you need to root your spice.And then install bootmenu.
Download the bootmenu.tar file(attached).And push it into /sdcard/
Turn on usb debugging on your phone. And use the following commands in adb:
Code:
C:/> adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock1 /system
# mkdir /system/bootmenu
# cd /system/bootmenu
# busybox tar -xf /sdcard/bootmenu.tar
# rm /system/bin/charge_only_mode
# busybox ln -s /system/bootmenu/binary/bootmenu /system/bin/charge_only_mode
# sync
# mount -o remount,ro /dev/block/mtdblock1 /system
# exit
The bootmenu will be installed.
Restart your device once.
Using Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the red led on your phone will light up for just 3 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Then you can select enter CWM recovery.(Someone say CWM's backup&restore cannot work,you can use method 2 for it)
Method 2:Through stock recovery(Fake flash zip)
I found that we can use CWM recovery with stock recovery leak(Fake flash update zip,like OpenRecovery),but this leak is only existed in SESGC_U3_10.10.0_RT firmware.
I have dumped this recovery(Attached file:recovery.img).And flash it by fastboot.It works well with SESLA_U3_01.72.0 firmware.
And then to flash a fake update.zip(Attached file:update.zip) from the root of your sdcard,you will enter CWM recovery!
By the way,if you want to port CM7 for spice,you need to use 2ndinit for your froyo/gingerbread,because it has locked bootloader.
I have compiled CM7 for it,and it can boot up but stuck in white screen after CM bootanimation.If you want to continue my work,you can checkout my github(["github . com/gentrylamp").
Thanks to:
CyanogenMod
koush
...
sorry for my poor English.
Click to expand...
Click to collapse
Hello!
Mr GentryLamp, congratulations done, I do not see many people who understand Android programming interested in XT300, you're the man!
I performed all the procedures above, installed bootmenu (but renamed the "charge_only_mode" as "charge_only_mode.bin" the backup purposes), I installed the old recovery with flash_image (command "flash_image recovery path_of_recovery _.img") and put the update.zip on the root of SD.
I can not perform with nand backup recovery from bootmenu (advance notice, and obviously non-functional), and the second way does not work (the leakage update.zip).
When trying to nand backup the nand, the device is the screen backuping ("SD memory free... Backup system...") For about an hour, and then the screen goes white, and end.
You know how I could accomplish this nand backup? You got on your device? Do you know any script that I can use for it?
If you need more information, or something that I test on my device, I place myself at your disposal.
Sorry my english too, Google Translate help much Brazilians.
Hug.

Regisboliver said:
Hello!
Mr GentryLamp, congratulations done, I do not see many people who understand Android programming interested in XT300, you're the man!
I performed all the procedures above, installed bootmenu (but renamed the "charge_only_mode" as "charge_only_mode.bin" the backup purposes), I installed the old recovery with flash_image (command "flash_image recovery path_of_recovery _.img") and put the update.zip on the root of SD.
I can not perform with nand backup recovery from bootmenu (advance notice, and obviously non-functional), and the second way does not work (the leakage update.zip).
When trying to nand backup the nand, the device is the screen backuping ("SD memory free... Backup system...") For about an hour, and then the screen goes white, and end.
You know how I could accomplish this nand backup? You got on your device? Do you know any script that I can use for it?
If you need more information, or something that I test on my device, I place myself at your disposal.
Sorry my english too, Google Translate help much Brazilians.
Hug.
Click to expand...
Click to collapse
I haven't confirmed whether NAND backup will work in bootmenu,but it works well in fake update.zip way.
If your firmware version is SESLA_U3_01.72.0,you need to boot the phone into fastboot mode(bule screen,pressing Vol-up&Vol-down while the phone boots up),and using fastboot to flash recovery.img.
BTW:Some firmware(such as SESGC_U3_10.10.0_RT) do not allow fastboot.You can see some warnings in fastboot bule screen.

More questions...sorry
GentryLamp said:
I haven't confirmed whether NAND backup will work in bootmenu,but it works well in fake update.zip way.
If your firmware version is SESLA_U3_01.72.0,you need to boot the phone into fastboot mode(bule screen,pressing Vol-up&Vol-down while the phone boots up),and using fastboot to flash recovery.img.
BTW:Some firmware(such as SESGC_U3_10.10.0_RT) do not allow fastboot.You can see some warnings in fastboot bule screen.
Click to expand...
Click to collapse
Thanks for reply man o/
My firmware is SESLA_U3_01.72.0, nand backup really not work on first method, and in the second method, also not .
I followed a guide like this: [ht tp:// forum . xda-developers . com/showthread.php?t=918275]. I believe the command is flash_image the same effectiveness as the fastboot, because I could run the CWM_recovery from the update.zip (you said that this gap is only SESGC_U3_10.10.0_RT recovery firmware, and I do not use - no clue of what it is, just know mine, and Chinese MONSTER).
But I saw now that you've lost your XT300 and therefore believe that there is no possibility to test or you do something for it. But anyway, I am grateful and even my disposal device testing, if desired.
Taking advantage ... would be able to put an 'if' that is, the low volume was not pressed, he continued with the 'charge_only_mode', so that the battery could be charged with the device off? I would also like to know if you know if it is possible to make a nand backup from a script, with the connected device, and if you have some kind of script ...
Excuse me for asking so many questions to you is that I know someone who knows and is as interested as you.
Thank you!
Hug.

i had the same problem with NAND backup using method 2

Regisboliver said:
the low volume was not pressed, he continued with the 'charge_only_mode', so that the battery could be charged with the device off?.
Click to expand...
Click to collapse
The phone will not enter charge only mode when you install bootmenu.
In method 2,NAND Backup&Restore works well when I use spice,I'm sorry that it doesn't work with some phone.

GentryLamp said:
The phone will not enter charge only mode when you install bootmenu.
In method 2,NAND Backup&Restore works well when I use spice,I'm sorry that it doesn't work with some phone.
Click to expand...
Click to collapse
I understand that only with bootmenu the device not charge without boot but, my question was would like to know if one can apply this procedure to boot: power button pressed > magenta led light and Motorola logo > {(before bootanimation and bootinstructions) volume down button pressed while red led light? "yes? -> bootmenu" | "no? -> execute the real charge_only_mode binary", execute charge_only_mode.bkp for example, in my case, since renamed the original charge_only_mode for subsequent restoration of boot } > boot. Understand my question? :s
But if there is, I made two scripts, one for installation and uninstallation of another bootmenu (if someone wants I can post), but if you do not give to run the above algorithm, I use the update.zip CWM_recovery the same, so I can recharge my device is switched off, while I find I try to do a custom for 2ndinit.
Mr GentryLamp, you said above, in the opening thread, it has ported a CM7 for XT300 and it crashed after the Motorola logo. I some time ago, I replaced the file libGLES_android.so (in the folder / system / lib / egl), trying to enable the GPU, I fear there is not even in the chipset of XT300 and while on the Motorola logo, the screen was white, blinking. You keep intact the lib folder? Forgive me if I did wrong or very noob question, because I have no expertise in ROM switches, ports, CM, etc...
Regarding the nand backup, searched about it here, to see if I can find at least one script for it, because then I can become more peaceful to test changes more dangerous, not bothering with RDS, SBF ...
Thanks again bro!

Is there a way to port to other Motorola devices? I have a DROID x that I need to try this on because it is stuck in safe mode. How did you port this to flash in stock recovery?
Sent from my DROID4 using Tapatalk 2

Great job, but I think this work is not useful because we don't have a custom Rom for this phone and the stock Rom sucks, I have this xt300 from my carrier iusacell Mexico, and is so slow and to f**king buggy, if is thera a chance to have a good froyo or gingerbread stable Rom will be perfect this phone have some potential but is too capable by the Motorola software
I hope we can some time get a good Rom for this great and cheap phone

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

[tutorial] flash cwm recovery on karbonn smart tab 1

hello all,
this recovery is not ported by me, xda's senior member fun_ have ported this to many devices, and we using the one which is compatible with paladin, many many thanks to him, a link to original thread is here
requirements:-
1. a rooted phone, you can root your tab here
2. cwm recovery image which you can get here
steps:-
1. open file manager which can have root access
2. go to system and rename recovery.cpio.img to recovery.cpio.img.bak
3. put downloaded recovery in /sdcard
4. open terminal emulator
5. type su
6. type "inand_flash_image recovery /mnt/sdcard/recovery.cpio.img" (if you have put it in flash then replace sdcard with flash)
7. then boot into recovery by holding menu and power button together or by typing "reboot recovery" in terminal emulator
how to control recovery:-
# power button is used to select options
# menu button will take you up
# home button will get you down when pressed
some notes you should keep in mind:-
1. back button do not work in recovery
2. never try the key test option else you will get stuck
3. backup do not work for boot, xboot, mbr areas
4. do not flash any rom available for paladin, basic etc. devices (or you will have a hard bricked tablet)
a simple step to enable on-screen back button
as soon as you booted into recovery, press menu then home then again menu, a message will appear saying enabled ( can be done in every screen)

Cwm
Nt able to rename recovery.cpio.img to recovery.cpio.img from andro zip, es file explorer,terminal . . ? Any solution?

in terminal type
Code:
su
mv /system/recovery.cpio.img /system/recovery.cpio.img.bak

dheeraj (dhlalit11) said:
in terminal type
Code:
su
mv /system/recovery.cpio.img /system/recovery.cpio.img.bak
Click to expand...
Click to collapse
failed - read only file system . . . ? . . Any other way to rename this file

pbhasin21 said:
failed - read only file system . . . ? . . Any other way to rename this file
Click to expand...
Click to collapse
tab is not rooted root it first
http://forum.xda-developers.com/showthread.php?p=29100664

dude i followed ur steps, used root explorer to rename to bak, and then tried, i get kcrc32 file size not same. and then when i boot to recovery the whole screen goes berzerk with curtain falls and doesn't do anything. i renamed the bak file into normal and flashed it and got the old recovery.. could you tell me what im doing wrong? used your recovery.cpio.img 3.5mb file in my sdcard... doesnt work..
rooted karbonn smart tab

kcrc32 not same is normal
did the terminal flash the recovery 2 times
like:-
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
if you get something like above then it is flashed properly

dheeraj (dhlalit11) said:
kcrc32 not same is normal
did the terminal flash the recovery 2 times
like:-
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
if you get something like above then it is flashed properly
Click to expand...
Click to collapse
yup i got it twice, kcrc32 not same.
then i entered reboot recovery. thats when the screen goes all curtainfall like a crash, and recovery doesn't load. i had to use the reset pin and power button to turn on the tab again.. perhaps the img is not compatible with my tab?
btw mine is Karbonn Smart Tablet 2.
http://ncarry.nimbuzz.com/karbonn/product.php?product_id=2212
but when i purchased, it came with android 4.0 ics. everything else is same as in that page..

it is different
and I think that's why recovery is not booting

any suggestions mate? perhaps another ainol tab is similar to karbonn st2?

What if there is no "recovery.cpio.img" file in the system folder? This is after having root permissions...nothing has been done otherwise. I do not have a recovery file to rename and am unsure if it should still go in the system folder or not. It doesn't even have a file extension (I had to transfer it to my laptop just to check, and there's no .img or .zip...nothing.)
Also I keep getting the following message in terminal emulator when attempting to run the command:
sh: inand_flash_image: not found. The image file is in the /mnt/sdcard/Download folder. The full instance is:
[email protected]:/ $ su
[email protected]:/ # inand_flash_image recovery /mnt/sdcard/Download/recovery.cpio.img
sh: inand_flash_image: not found
127|[email protected]:/ # inand_flash_image
sh: inand_flash_image: not found
Any help?