Database Info

HTC EVO superuser port to Samsung Transform???

Rooted my Transform and went in to the superuser APK.... I'm disappointed that it has very limited content vs. my buddies HTC EVO. I'm new to Androids, but anyone know if there would be a way to port the superuser APK from the HTC EVO to the Samsung Transfrom, or is it even Feasible?

Can you go into more detail on how you rooted your Samsung Transform. I have tried SuperOneClick but the root never sticks. I would lose superuser randomly.

I just rooted with Super One Click, now, i dont know what to do with it lol. It sticks with me though.

No need for a superuser port. Just download from the market after rooting
via skeeterslint sdx:
Heres is a one click recovery installer for people that don't want to do it by hand.
http://www.mediafire.com/?jl21knp1d0lbf17
This is a still beta but working version of SDX Recovery version 3.1.1.
Things known to work.
Backups and restores.
Clearing dalvik cache.
Clearing cache partition.
Flashing kernel zImages.
Flashing zip files.
Adb works in recovery.
Also mounting the sdcard to your computer works.
Anything else in the options is still in need of testing I am not responsible if your phone gets bricked.
THIS MAY BRICK ALL PHONE MODS YOU DO AT YOUR OWN RISK!
OK now that thats out of the way heres the files needed.
1. http://www.mediafire.com/?862j3wlzftenwef This is the recovery image.
2. http://www.mediafire.com/?67an7lkm9qtmf5b until there is a custom recovery you will need this program to flash recovery. Its called flash_image.
3. http://www.mediafire.com/?5dcv3r14sjvsfdq rage.bin temporary exploit to get root.
4. You will also need the Android SDK so you have a working adb to be able to push files over to your phone.
If you are flashing this from a phone running my rooted kernel you can skip steps 4 and 7 and just su over to a root prompt.
OK these are the steps to install this recovery.
1. Make sure adb is installed and working there are how to's on the forum to get this setup or just use google.
2 adb push recovery.bin /data/local/tmp to move the kernel to the phone.
3 adb push flash_image /data/local/tmp to move flash_image onto the phone.
4 adb push rage.bin /data/local/tmp to move rage.bin onto the phone.
5. Run adb shell to get to a shell prompt on the phone.
6. Run chmod 755 on flash_image and rage.bin chmod 755 rage.bin chmod 755 flash_image.
7. Run ./rage.bin and let it go run through untill it exits you out of adb.
8. adb shell you should now have a root shell on the phone.
9. Run ./flash_image recovery recovery.bin to install the kernel.
Once its installed to get into recovery use Volume down Camera and power to get into recovery.
Volume up and down scroll through the option.
Menu should be the enter key.
Back button is back.
Search key is delete.
You will need to create the directorys on your sdcard that recovery needs to flash zip files make backup and flash kernel and recovery from.
Create directory called sdx on the root of the sdcard and inside it create 3 folders zips update and backup.
At this time it seems that factory restore is not working correctly and anyone else can confirm please let me know.
And for better recovery via vampirefo on sdx:
his is my first recovery, I made the change to the first screen to show that this is a transform recovery rather than a moment recovery. Also I got console to work in recovery, it wont rotate but works just fine.
http://www.4shared.com/file/bBTlN7UZ/recoveryrfs.html
You can flash this via swupdate, or if you already have skeeters recovery installed, just extract recovery.tar to /sdcard/sdx/updates
boot to recovery
Scroll down to
Backup, Restore, Flash
Scroll down to
Flash Recovery
After flash is complete
press back button
Under Reboot options choose Reboot to Recovery to see new recovery

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

ROM Manager will BREAK YOUR RECOVERY!!! DO NOT USE!!!

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

[Q] flash insecure boot image from CWM?

Is there a way to flash an insecure boot image from CWM recovery?
I rooted my transformer with nachoroot, and installed CWM with the one-click recovery installer. None of these methods unlocked the boot loader, obviously, so I can't use adb remount and friends.
I have a B70 tf101, with the .21 firmware if that helps.

I think you need to flash an insecure boot.img.
There are a few few threads kicking around in the dev section that explain this. rebound821 posted an excellent thread. I think this is exactly what moshi and brk's root tools do via nvflash.
In a nutshell:
1) extract your boot.img from your TF
2) unpack the boot.img to the kernel and ramdisk
3) unpack the ramdisk
4) edit default.prop to set ro.secure=0
5) re-assemble in reverse order
6) zip and flash

gee one said:
I think you need to flash an insecure boot.img.
There are a few few threads kicking around in the dev section that explain this. rebound821 posted an excellent thread. I think this is exactly what moshi and brk's root tools do via nvflash.
In a nutshell:
1) extract your boot.img from your TF
2) unpack the boot.img to the kernel and ramdisk
3) unpack the ramdisk
4) edit default.prop to set ro.secure=0
5) re-assemble in reverse order
6) zip and flash
Click to expand...
Click to collapse
thanks for the reply, but I was asking if after I've done that I could flash the boot img with CWM? I've heard that nvflash doesn't work on B70 transformers.
Sent from my HTC Vision using Tapatalk

Yup, in step 6, you would zip it up and flash it via cwm.

pm sent!!!

perquisitor_omnia said:
Is there a way to flash an insecure boot image from CWM recovery?
I rooted my transformer with nachoroot, and installed CWM with the one-click recovery installer. None of these methods unlocked the boot loader, obviously, so I can't use adb remount and friends.
I have a B70 tf101, with the .21 firmware if that helps.
Click to expand...
Click to collapse
If you have root you can do adb remount.
Start a shell in adb and use su to get root. Now you can remount.
I assume this is about remount /system

gls9 said:
If you have root you can do adb remount.
Start a shell in adb and use su to get root. Now you can remount.
I assume this is about remount /system
Click to expand...
Click to collapse
Yeah, but even if I remount /system using adb shell I can still can't do "adb push" to /system so I assume I need to set ro.secure=0 in the bootloader for this to work.

perquisitor_omnia said:
Yeah, but even if I remount /system using adb shell I can still can't do "adb push" to /system so I assume I need to set ro.secure=0 in the bootloader for this to work.
Click to expand...
Click to collapse
I dont know because I don't use adb much.
But why not do this from terminal emulator and just copy the file from sdcard ?
(or with adb shell)
Something like this:
su
mount -o remount,rw /system
cat [source] > [destination]

gls9 said:
I dont know because I don't use adb much.
But why not do this from terminal emulator and just copy the file from sdcard ?
(or with adb shell)
Something like this:
su
mount -o remount,rw /system
cat [source] > [destination]
Click to expand...
Click to collapse
Thats what I am doing at the moment, but it is annoying to have to stage all files to /data/local or /sdcard before copying files to /system from the tablet, when it is much easier to do
$ adb push <file> /system/
from the host computer. Anyway, if I make a insecure bootloader for my tablet that can be flashed from the recovery, I'll post it here as it might be useful to other people in my position.

I've got an insecure boot.img from the US 8.6.5.21 firmware if anyone is interested. It's just the boot in a zip file.

Maybe I'm misunderstanding, but I thought that any image you flashed with CWM recovery was using an insecure boot.img, unless flashing back stock recovery. Anyway, for adb push or adb pull for that matter to work you have to install Asus sync software and USB drivers under Windows and if in Linux, you can search xda for the thread that explains how to get adb working. Once you've got that and root you can adb push and adb pull all day long til you run out of space.

sidneyk said:
Maybe I'm misunderstanding, but I thought that any image you flashed with CWM recovery was using an insecure boot.img, unless flashing back stock recovery. Anyway, for adb push or adb pull for that matter to work you have to install Asus sync software and USB drivers under Windows and if in Linux, you can search xda for the thread that explains how to get adb working. Once you've got that and root you can adb push and adb pull all day long til you run out of space.
Click to expand...
Click to collapse
I have adb working properly (I use it with my G2 all the time), and I use linux.
But for some reason, with my Asus Transformer, when I do
Code:
$ adb remount
I get a 'permission denied' error.
Even if I remount /system rw from the shell, I still get 'permission denied' when trying to use 'adb push' to any directory besides /data/local or /sdcard on the tablet. Is this a bug with the recovery I flashed? or is this because the bootloader hasn't had ro.secure=0 set?
Sent from my Transformer TF101 using Tapatalk

Are you trying this in recovery or under the normal system? Try it under both.
sent from my transformer

I'm trying under the normal system, I will try under recovery when I get access to my desktop.
Sent from my Transformer TF101 using Tapatalk

OK, how about some testing:
from your PC:
adb version
adb shell grep secure /default.prop (or adb shell getprop ro.secure)
This will check your adb version and also see if your ro.secure flag is set.
I tested 'adb remount' and it worked as intended. I'm on adb version 1.0.29 with ro.secure=0.
Also, the recovery ramdisk has it's own default.prop and ro.secure flag, so these can actually be set independantly, but I think you would notice it immediately if recovery wasn't insecure.

Code:
$ adb version
Android Debug Bridge version 1.0.29
$ adb -s shell getprop ro.secure
1
so that would be the problem. can I set the ro.secure property in build.prop?

perquisitor_omnia said:
I have adb working properly (I use it with my G2 all the time), and I use linux.
But for some reason, with my Asus Transformer, when I do
Code:
$ adb remount
I get a 'permission denied' error.
Even if I remount /system rw from the shell, I still get 'permission denied' when trying to use 'adb push' to any directory besides /data/local or /sdcard on the tablet. Is this a bug with the recovery I flashed? or is this because the bootloader hasn't had ro.secure=0 set?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I am familiar with errors kind of like this from Mac OS, dunno if it applies here but you might try repairing permissions from CWM. I have fund that quite a lot of ROMs do not have correct permissions set.
Cheers!
-M
Xda member since 2007

perquisitor_omnia said:
Code:
$ adb version
Android Debug Bridge version 1.0.29
$ adb -s shell getprop ro.secure
1
so that would be the problem. can I set the ro.secure property in build.prop?
Click to expand...
Click to collapse
Yeah, that would cause the issues. Not sure how to fix it, but some ideas:
1) flash an insecure boot.img via cwm
2) use the staging partition to flash a boot.img/blob
3) ???

I finally used the SBK detect tool, my B70 has a nvflashable firmware, so I will pull the boot loader with nvflash and make it insecure that way.
Sent from my HTC Vision using Tapatalk

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