Database Info

[Q] Unable to boot into recovery mode

I've tried using ROM manager and booting back into recovery mode but it stalls at the Google unlock screen. I've also tried installing the stock version of 2.3.2 version from Rom manager but got the same results.
I've also flashed the clockworkMod recovery to 3.0.0.5 then rebooted into Bootloader where i selected the "Recovery" option but again I only reach the Google unlock icon screen. It's been sitting at that screen for the past 20mins. Only way past it is to boot normally (after i reinsert the battery).
I have tried restoring from a previous backup but that too fails because it cant reach the recovery portion of the process after rebooting.
About Phone
Version: 2.3.2
Baseband Version: I9020XXJK8
Kernel Version: 2.6.35.7-g81433b [[email protected]#1]
CPU INFO: ARMv7 Processor Rev 2 (v7l)
Mod Version: CyanogenMod-7-02102011-NIGHTLY-NS
Build #: GRH78C
Click to expand...
Click to collapse
any help is greatly appreciated.

reflash recovery

thejron said:
reflash recovery
Click to expand...
Click to collapse
try reflashing the recovery from within the bootloader with "fastboot flash recovery recovery.img" or something like that. you should find something about this here on XDA i think.

floomat said:
try reflashing the recovery from within the bootloader with "fastboot flash recovery recovery.img" or something like that. you should find something about this here on XDA i think.
Click to expand...
Click to collapse
thx. i'll try that now.

thx for the reply, this page worked:
http://forum.xda-developers.com/sho...ighlight=fastboot+flash+recovery+recovery.img
i was able to update the ROM to 2.3.3, while in recovery mode. I rebooted the device but now when i go to Reboot>Recovery it still hangs at the google unlock screen. I think the only way for me to successfully access the recovery screen would be to connect my phone to the pc and run the fastboot boot-recovery-clockwork-3.0.0.5-crespo.img file.

headsh0tshurt said:
I think the only way for me to successfully access the recovery screen would be to connect my phone to the pc and run the fastboot boot-recovery-clockwork-3.0.0.5-crespo.img file.
Click to expand...
Click to collapse
What's happening is that Android is overwriting your custom recovery whenever it reboots.
To fix it, you first have to go back to the stock rom. Then, using either root explorer or adb, you have to rename /etc/install-recovery.sh
That way, when you flash your custom recovery, it doesn't rewrite the stock one when you reboot.
Check out this link:
http://forum.xda-developers.com/showthread.php?t=740748
edit: Also, in case someone else reads your post about using fastboot to get into recovery... the command is actually: "fastboot boot recovery-clockwork-3.0.0.5-crespo.img"
Note the space, not hyphen, between boot and the recovery image
Edit2: Ugh, the link I gave is pretty unclear (very shoddy google work). Anyway, the idea in the link is right, the command to remount your system in adb is:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
The full list of commands would be:
adb shell
su [you have to allow root access on your phone at this point - superuser will give you a popup]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /
cd etc
mv ./install-recovery.sh ./install-recovery.sh.old

kaimyn said:
What's happening is that Android is overwriting your custom recovery whenever it reboots.
To fix it, you first have to go back to the stock rom. Then, using either root explorer or adb, you have to rename /etc/install-recovery.sh
That way, when you flash your custom recovery, it doesn't rewrite the stock one when you reboot.
Check out this link:
http://forum.xda-developers.com/showthread.php?t=740748
edit: Also, in case someone else reads your post about using fastboot to get into recovery... the command is actually: "fastboot boot recovery-clockwork-3.0.0.5-crespo.img"
Note the space, not hyphen, between boot and the recovery image
Edit2: Ugh, the link I gave is pretty unclear (very shoddy google work). Anyway, the idea in the link is right, the command to remount your system in adb is:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
The full list of commands would be:
adb shell
su [you have to allow root access on your phone at this point - superuser will give you a popup]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /
cd etc
mv ./install-recovery.sh ./install-recovery.sh.old
Click to expand...
Click to collapse
i ran adb shell and entered the commands listed above. Below is a screenshot of what was entered.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now after I entered the mv ./install-recovery.sh ./install-recovery.sh.old
command it says that i can't rename the .install-recovery.sh because it doesn't exist. do i have to manually create a folder on the root with this name?

Did you go back to stock first? I think the files get deleted on a new rom, but for some reason you still have to rename the files while in stock. I had the same issue the first time I went to a custom rom.
I'm about to head to bed (asia) but I'll double check the directory in the morning.
You should also be able to Google the answer... I may have told you the wrong directory for the file. Look for something along the lines of android mount install-recovery.sh
Sent from my Nexus S using XDA App

No i didn't go back to stock prior to running the earlier cmd lines.
while in USB Debug mode, i transferred over the GRI40-2.3.3-rooted.zip into the phones' clockworkmod/backup folder. i then rebooted it into the bootloader and:
ran fastboot boot recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
I then chose the Backup & Restore option and selected to Restore the GRI40-2.3.3-rooted.
Once it was done i then selected reboot, it powered back on with full stock image. i rebooted it once more to confirm it had the stock image of 2.3.3. then from the bootloader screen i selected the recovery option and it took me to the screen with the android icon and the exclamation mark above it.

headsh0tshurt said:
No i didn't go back to stock prior to running the earlier cmd lines.
while in USB Debug mode, i transferred over the GRI40-2.3.3-rooted.zip into the phones' clockworkmod/backup folder. i then rebooted it into the bootloader and:
I then chose the Backup & Restore option and selected to Restore the GRI40-2.3.3-rooted.
Once it was done i then selected reboot, it powered back on with full stock image. i rebooted it once more to confirm it had the stock image of 2.3.3. then from the bootloader screen i selected the recovery option and it took me to the screen with the android icon and the exclamation mark above it.
Click to expand...
Click to collapse
So now if you delete or rename install-recovery.sh you should be good. For future reference
Code:
fastboot boot
Doesn't flash anything so you're literally just booting into an image so no matter what you wouldn't boot back into that image without the command again. If you want to flash a new recovery without using ROM Manager you can use the following command:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img

kenvan19 said:
So now if you delete or rename install-recovery.sh you should be good. For future reference
Click to expand...
Click to collapse
Okay I was not able to locate the file "install-recovery.sh" file on the SD, so from bootloader, I ran the code:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
and went into recovery mode where i ran the latest nightly (cm_crespo_full-12.zip) and rebooted it more than once and each time it gets stuck @ the cyanogen mod7 boot screen....progress :/

headsh0tshurt said:
Okay I was not able to locate the file "install-recovery.sh" file on the SD, so from bootloader, I ran the code:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
and went into recovery mode where i ran the latest nightly (cm_crespo_full-12.zip) and rebooted it more than once and each time it gets stuck @ the cyanogen mod7 boot screen....progress :/
Click to expand...
Click to collapse
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.

Suggest you try the instructions at the bottom of this page > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
7-step process that will help you go to CMR instead of stock recovery. Worked perfectly for me.

kenvan19 said:
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Click to expand...
Click to collapse
yeah i copy/pasted what you wrote in my response but in actuality i wrote the correct file name into the the CMD and it went through. IF/when i get past the CM7 boot screen i'll look into the root explorer app. thx for the assist

kenvan19 said:
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Click to expand...
Click to collapse
.cruiser said:
Suggest you try the instructions at the bottom of this page > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
7-step process that will help you go to CMR instead of stock recovery. Worked perfectly for me.
Click to expand...
Click to collapse
Thanks for the link. I went through the instructions and the results were the same. the end of the instructions mentions to get the Root explorer on the phone but that doesnt work b/c i cant bypass the CM7 boot screen. so i just restored it to GRI40-2.3.3-rooted.zip via the clockwork recovery

The install-recovery.sh file is missing in CM7 - you have to do this process from a stock rom.
Personally, this is exactly how I did it. You may try it this way if you like... you should have instructions for all the individual pieces.
1. Go back to stock 2.3.2
2. Get the OTA update to 2.3.3
3. Unlock your bootloader
4. Using the fastboot boot recovery method, install SU
5. Boot in to Android and then rename install-recovery.sh
6. Install rom manager
7. Flash CWM 3.0.0.5
Good luck! Who knows, maybe you have to have an unlocked bootloader to get CWM to stick.

kaimyn said:
The install-recovery.sh file is missing in CM7 - you have to do this process from a stock rom.
Personally, this is exactly how I did it. You may try it this way if you like... you should have instructions for all the individual pieces.
1. Go back to stock 2.3.2
2. Get the OTA update to 2.3.3
3. Unlock your bootloader
4. Using the fastboot boot recovery method, install SU
5. Boot in to Android and then rename install-recovery.sh
6. Install rom manager
7. Flash CWM 3.0.0.5
Good luck! Who knows, maybe you have to have an unlocked bootloader to get CWM to stick.
Click to expand...
Click to collapse
my impatience got the best of me. after restoring it to the stock 2.3.3. i just reinstalled all the applications. none of my downloaded files (music/wallpapers) were lost.
[sarcasm]just have to go through the joy of reorganizing each screen [/sarcasm]. Mostly i am pisssed that i'd have to start from scratch in Angry birds .

This happened to me with gingercollab. I did fastboot flash then booted straight to recovery and installed cm7. Everything was working fine until I restored my nandroid of gingercollab by mistake.
Sent from my Nexus S using XDA Premium App

the issue was never resolved. and i get the system update for 2.3.4 about twice a week and i cant install it b/c after it restarts it bombs out at the android icon w/ the excalamtion mark.
i've tried the factory wipe/reset thinking that would start me off clean but that didnt work.

Unless you RENAME the stock recovery it WILL NEVER STICK. Unlocked bootloader or not. I just reflash recovery from fastboot if/when I need it.
Sent from a bird cage, with a swing!

Bricked?? what can I do

Hi all,
I got my replacement phone today. The first thing I wanted to do was to take the phone I am sending back and "unroot" it....Stupid me...I forgot to take the lagfix off....so now after I installed the EE2 rom to go back to stock.....I am in a DROID BOOTLOOP.....does anyone have any suggestions that I may be able to try to get it out of the bootloop? or else I have to take my chances and send it back anyway.....

Use p3droids method on mydroidworld
Sent from my SCH-I510 using XDA Premium App

Or put sd card into new phone. Make a file called disable-lagfix in the voodoo file. Flash voodoo onto bootlooped droid charge that is bootlooped and put sd card into broken charge after you flash it
Sent from my SCH-I510 using XDA Premium App

You should be able to flash a package w/ voodoo kernel like Altered Beast and get out of your boot loop. Then disable lagfix and flash the stock EE4 pkg.

hoppermi said:
You should be able to flash a package w/ voodoo kernel like Altered Beast and get out of your boot loop. Then disable lagfix and flash the stock EE4 pkg.
Click to expand...
Click to collapse
thats what I just did......I installed Gummy Package.....with kernel...voodoo...CWM.....I will report back in a few
EDIT::: yep it worked.....I asked the question before I thought about it....I got it to go...thanks to all that answered my stupid question....I answered it myself LOL

hogowner said:
thats what I just did......I installed Gummy Package.....with kernel...voodoo...CWM.....I will report back in a few
EDIT::: yep it worked.....I asked the question before I thought about it....I got it to go...thanks to all that answered my stupid question....I answered it myself LOL
Click to expand...
Click to collapse
Thanks for answering your own question. Now I don't have to ask the same question.

Couldn't you also have just flashed the stock ED1 Odin package?
http://forum.xda-developers.com/showthread.php?t=1137369
imnuts:
"Flash the ED1 or ED2 full odin package. It will take you back to stock, and you don't need to worry about voodoo being enabled/disabled if you flash one of them as it will also wipe that out."

el_brio said:
Couldn't you also have just flashed the stock ED1 Odin package?
http://forum.xda-developers.com/showthread.php?t=1137369
imnuts:
"Flash the ED1 or ED2 full odin package. It will take you back to stock, and you don't need to worry about voodoo being enabled/disabled if you flash one of them as it will also wipe that out."
Click to expand...
Click to collapse
Yes....I tired both files and it didn't let me load them in ODIN....it keep failing.....
I know it could have been a bad download...but I downloaded them each 3 times and got the same results with EE1 and EE2....
I am going to try over the weekend...don't want to send back the phone to VZ with a custom rom, voodoo and CWR installed LOL
if anyone has a good copy of either file that works with odin, please pm me your e mail address....I will e mail you back...and you can send it to me...this way I KNOW it is a good file...
thanks!

papi92 said:
Use p3droids method on mydroidworld
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
This is for sure the best option seeing as the file is the Full blown flash file. IE like an SBF file for Moto devices.
Here is a link to the info http://www.mydroidworld.com/forums/...harge-full-factory-tar-flashing-software.html

I saw that file..not sure about loading it..it says u need 7z to unzip it and put to install it...not sure how to use. .and put is a few files when unzipped that i am not sure how to go about using it
Sent from my 4g Verizon Charge!

I'm in a worse boat than the OP. Long story short, I started getting all kinds of weird FCs the other day, well after I had flashed my last ROM, which was Gummy 1.7.5, I think -- maybe even 1.5.
Anyway, I figured no biggie, I'll just wipe and flash the 1.7.5 ODIN and then put 1.8 on top of that. About 10 hours later, I'm still not there, and I'm pretty sure I'm screwed. Would like any suggestions.
So far I've tried ODINing back to stock ED1 and ED2, and SamsungPSTing to stock ED1, all of which flash fine, but DROID boot loop. I've tried disabling lagfix, I've tried just leaving it alone, I've wiped and wiped and wiped, all to no avail. Ultimately when flashing to these stock packages the stock recovery gives me the following text when recovery starts, and I can never boot to the OS:
Before "Movie_check Start..!!"
E:Can't mount /dev/block/mmcblk0p1
After "Movi_check done!..."
E:Can't mount /dev/block/mmcblk0p3
(Invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount dev/block/mmcblk0p3
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount dev/block/mmcblk0p3
(Invalid Argument)
Flashing rooted stock ED1 also boot loops. I can get to recovery and wipe a bunch, but to no avail.
The only thing that will kind of work is ODINing Gummy 1.7.5 This will at least boot. Problem is -- and I think this is the "root" of my problem, that programs that I had installed that I've uninstalled (and wiped a million times) keep coming up and causing FCs. It doesn't matter if I uninstall them from Manage Applications, or anything. They're always still there, still somehow on the internal memory. I also get FCs from the Gallery, the Browser, and who knows what else. At least I can make a phone call and send an email tho.
I'm thinking a trip to the Verizon store is in order, but am hoping that someone out there has a magic bullet for me.
Thanks in advance for any assistance, and let me know if I've left out any pertinent info. I really don't know much about this stuff, I've just been doing the script kiddie thing on this stuff, which has worked until yesterday...

I doubt if this fixes anything, but it will give you something to do while someone who knows way more than me can chime in. I read on the GummyCharged thread about people having the Let's Golf app constantly reappear on reboot after uninstalling it. The app ended up being in the /preinstall folder. You can look there and see if all your apps that keep FCing ended up there by some magical chance.

hogowner said:
I saw that file..not sure about loading it..it says u need 7z to unzip it and put to install it...not sure how to use. .and put is a few files when unzipped that i am not sure how to go about using it
Sent from my 4g Verizon Charge!
Click to expand...
Click to collapse
7z is just another program like WinZip or WinRar and it works the exact same way.

rheno said:
I doubt if this fixes anything, but it will give you something to do while someone who knows way more than me can chime in. I read on the GummyCharged thread about people having the Let's Golf app constantly reappear on reboot after uninstalling it. The app ended up being in the /preinstall folder. You can look there and see if all your apps that keep FCing ended up there by some magical chance.
Click to expand...
Click to collapse
Thanks rheno, I'll give that a shot.
I do have that 11MB golf game in there too.

cshorter said:
I'm in a worse boat than the OP. Long story short, I started getting all kinds of weird FCs the other day, well after I had flashed my last ROM, which was Gummy 1.7.5, I think -- maybe even 1.5.
Anyway, I figured no biggie, I'll just wipe and flash the 1.7.5 ODIN and then put 1.8 on top of that. About 10 hours later, I'm still not there, and I'm pretty sure I'm screwed. Would like any suggestions.
So far I've tried ODINing back to stock ED1 and ED2, and SamsungPSTing to stock ED1, all of which flash fine, but DROID boot loop. I've tried disabling lagfix, I've tried just leaving it alone, I've wiped and wiped and wiped, all to no avail. Ultimately when flashing to these stock packages the stock recovery gives me the following text when recovery starts, and I can never boot to the OS:
Before "Movie_check Start..!!"
E:Can't mount /dev/block/mmcblk0p1
After "Movi_check done!..."
E:Can't mount /dev/block/mmcblk0p3
(Invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount dev/block/mmcblk0p3
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount dev/block/mmcblk0p3
(Invalid Argument)
Flashing rooted stock ED1 also boot loops. I can get to recovery and wipe a bunch, but to no avail.
The only thing that will kind of work is ODINing Gummy 1.7.5 This will at least boot. Problem is -- and I think this is the "root" of my problem, that programs that I had installed that I've uninstalled (and wiped a million times) keep coming up and causing FCs. It doesn't matter if I uninstall them from Manage Applications, or anything. They're always still there, still somehow on the internal memory. I also get FCs from the Gallery, the Browser, and who knows what else. At least I can make a phone call and send an email tho.
I'm thinking a trip to the Verizon store is in order, but am hoping that someone out there has a magic bullet for me.
Thanks in advance for any assistance, and let me know if I've left out any pertinent info. I really don't know much about this stuff, I've just been doing the script kiddie thing on this stuff, which has worked until yesterday...
Click to expand...
Click to collapse
Seeing as yours boots somewhat here is what I would do. Flash the stock ED1 file which ever one you prefer or you know that works. Then before even trying to fully boot the first time flash Imnut's CWM to the device using ODIN. If that passes boot into CWM and wipe data/cache and also dalvik. however before booting flash/install Imnut's kernel from in CWM then let it boot and see what you get.

will2live said:
Seeing as yours boots somewhat here is what I would do. Flash the stock ED1 file which ever one you prefer or you know that works. Then before even trying to fully boot the first time flash Imnut's CWM to the device using ODIN. If that passes boot into CWM and wipe data/cache and also dalvik. however before booting flash/install Imnut's kernel from in CWM then let it boot and see what you get.
Click to expand...
Click to collapse
I gave this a shot, but no dice. I could get the ED1 OS to boot, but I'd get stuck in an endless loop of FCs -- every process would FC while on the 1st setup screen. It was worth a shot.
While I was on this non-voodoo, stock except for CWM and imnuts' kernel, I ran a mount command from a shell. This is what I got:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
nodev on /tmp type tmpfs (rw,relatime)
/dev/block/stl7 on /mnt/.lfs type j4fs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl10 on /system type rfs (rw,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=utf8)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,nosuid,nodev,noexec,relatime,uid=1
000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso
8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/mmcblk0p3 on /cache type ext4 (rw,noatime,barrier=0,data=ordered)
~ #
I'm way over my head, but after digging around on the web, I'm pretty sure that what's happened is that the mmcblk0p3 (whatever that is -- a chip or memory?) is borked. It's showing as ext4 even though everything else is rfs.
After this last round of messing around, one thing has changed, I've now gotten Root Explorer to install. I'm back on Gummy 1.7.5, and I'm limping along, all the core stuff works, it's just most apps that are broken.
Can any devs out there give me a hand here, or am I toast?
Thanks
PS, now that I have Root Explorer, I looked in preinstall, and the golf game was in there, but that's it.

Instructions to UN-brick
Ok.... I have bricked my phone several times and became an expert at fixing it. This fix wipes everything from your phone and puts you back into a stock EE1 ROM but it makes your phone work again. I am posting the instructions here and am currently uploading the needed files. Will update this post with the links once they are up.
I HAVE PROVIDED PICTURE ATTACHMENTS SO YOU CAN REFER TO WHAT IM TALKING ABOUT
YOU WILL HAVE TO UNZIP TWO OF THESE FILES IF YOU DONT HAVE AN UNZIP UTILITY YOU MAY DOWNLOAD WINRAR FROM HERE.......
http://www.win-rar.com/download.html
1. First download all the attached files and place them somewhere you can find them or just make note of where you downloaded them.
2. Install Samsung USB driver for mobile phone.exe if you had not already done so. If you have used ODIN in the past with your Droid Charge, then you may skip this step for you already have the drivers.
3. Unzip the folder named SAMSUNGPSTlite...zip. Then open the folder and install the setup.exe file
4. When installation is done, install the Samsung SCH-150.msi file
5. Make sure your phone is off, with the battery OUT and connect it to your computer.
6. Hold volume down until your phone responds, i think with a yellow triangle. Once the triangle appears REMOVE THE BATTERY!
7. Open the Samsung Application we just installed. It will probably be under a folder named Phone flashing application. You will probably have to grant it user permission to run when asked.
8. Double click on your phone where the error points in picture 1.
9.Make sure your phone is connected on the lower right hand corner (check picture 2)
10. On the left hand side click on SW Download.
11. Make sure the drop down window says PDA + PHOne update
11. Now check the box that says Boot update.
12. CLick the button that says open AP and search for the file you downloaded AND UNZIPED named something like.... CI50_VZW_ED1 and ends with a .tar extension
13. Now click on Start Download.
14. Your phone will begin loading the information and when the operation is done you are good to go!!!
15. Turn on your phone
16. It will take a while for your phone to completely turn on so just be patient.
SamsungPST SCH-I510 For Verizon.msi
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.3.1900.0.exe
SamsungPSTLite FW Setup1.0.004_MSI1ndEdition.zip
CI510_VZW_ED1_ALL_ONE-LTE-CP_REV03_user_CL986330.tar.zip - 398.55MB

The process will2live mentioned from the myandroidworld website works flawlessly sending you back to stock.
I would try that process and then as the phone reboots at the very end make sure you go into recovery mode prior to it booting up and do a FACTORY RESET but remember you will lose all your data which i assume you shouldn't have any anyhow since you're returning the phone.
This worked for me and hopefully will work for you.
cshorter said:
I gave this a shot, but no dice. I could get the ED1 OS to boot, but I'd get stuck in an endless loop of FCs -- every process would FC while on the 1st setup screen. It was worth a shot.
While I was on this non-voodoo, stock except for CWM and imnuts' kernel, I ran a mount command from a shell. This is what I got:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
nodev on /tmp type tmpfs (rw,relatime)
/dev/block/stl7 on /mnt/.lfs type j4fs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl10 on /system type rfs (rw,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=utf8)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,nosuid,nodev,noexec,relatime,uid=1
000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso
8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/mmcblk0p3 on /cache type ext4 (rw,noatime,barrier=0,data=ordered)
~ #
I'm way over my head, but after digging around on the web, I'm pretty sure that what's happened is that the mmcblk0p3 (whatever that is -- a chip or memory?) is borked. It's showing as ext4 even though everything else is rfs.
After this last round of messing around, one thing has changed, I've now gotten Root Explorer to install. I'm back on Gummy 1.7.5, and I'm limping along, all the core stuff works, it's just most apps that are broken.
Can any devs out there give me a hand here, or am I toast?
Thanks
PS, now that I have Root Explorer, I looked in preinstall, and the golf game was in there, but that's it.
Click to expand...
Click to collapse

thareefer said:
Ok.... I have bricked my phone several times and became an expert at fixing it. This fix wipes everything from your phone and puts you back into a stock EE1 ROM but it makes your phone work again. I am posting the instructions here and am currently uploading the needed files. Will update this post with the links once they are up.
I HAVE PROVIDED PICTURE ATTACHMENTS SO YOU CAN REFER TO WHAT IM TALKING ABOUT
YOU WILL HAVE TO UNZIP TWO OF THESE FILES IF YOU DONT HAVE AN UNZIP UTILITY YOU MAY DOWNLOAD WINRAR FROM HERE.......
http://www.win-rar.com/download.html
1. First download all the attached files and place them somewhere you can find them or just make note of where you downloaded them.
2. Install Samsung USB driver for mobile phone.exe if you had not already done so. If you have used ODIN in the past with your Droid Charge, then you may skip this step for you already have the drivers.
3. Unzip the folder named SAMSUNGPSTlite...zip. Then open the folder and install the setup.exe file
4. When installation is done, install the Samsung SCH-150.msi file
5. Make sure your phone is off, with the battery still IN and connect it to your computer.
6. Hold volume down until your phone responds, i think with a yellow triangle.
7. Open the Samsung Application we just installed. It will probably be under a folder named Phone flashing application. You will probably have to grant it user permission to run when asked.
8. Double click on your phone where the error points in picture 1.
9.Make sure your phone is connected on the lower right hand corner (check picture 2)
10. On the left hand side click on SW Download.
11. Make sure the drop down window says PDA + PHOne update
11. Now check the box that says Boot update.
12. CLick the button that says open AP and search for the file you downloaded AND UNZIPED named something like.... CI50_VZW_ED1 and ends with a .tar extension
13. Now click on Start Download.
14. Your phone will begin loading the information and when the operation is done you are good to go!!!
15. Turn on your phone
16. It will take a while for your phone to completely turn on so just be patient.
SamsungPST SCH-I510 For Verizon.msi
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.3.1900.0.exe
SamsungPSTLite FW Setup1.0.004_MSI1ndEdition.zip
CI510_VZW_ED1_ALL_ONE-LTE-CP_REV03_user_CL986330.tar.zip - 398.55MB
Click to expand...
Click to collapse
This worked GREAT!!! the only thing is, I left the battery out not in......if the battery is in and you hold the volume button...nothings happens.....so just take the battery out....hold the volume button...and you are in the download menu screen..yellow triangle...then I put the battery in......then I followed your steps and it worked like a CHARM!!!
now I can return the phone completely STOCK!!!!

Thanks hogowner for pointing that out i fixed it in the original guide.

[EP4D/FP1H/FP5E][MOD][ODIN] Change Boot Splash Image

This is from a whole lot of brainstorming, reading, headaches & lack of sleep. I now understand Odin & Heimdall a whole lot better; & my skills with Samsung Android phones have increased a bit more. I hope that at least one person can benefit from having a modified param.lfs for a custom boot splash.
Let me know if there are any ways that I can improve this post.
Before you begin, this is for the fearless types that know what they're doing or go all out even if they're jumping into a tornado. Your phone may soft-brick if something goes wrong.
Modified Instructions (from kmalinich's thread):
Needed:
Rooted Samsung Droid Charge
Working ADB
Latest Odin3
Hacked param.lfs (attached & mirrored)
New jpeg boot logo size 480x800 (less than 64KB - test to see if larger works)
Steps:
Copy your new splash image (logo.jpg) to your sd card however you'd like.
Remove your SIM card for safe keeping until this process is finished
Start Odin
Enter download mode (reboot to it or disconnect the phone, take out the battery, press the volume down button, plugin the USB cable, wait for the download screen to appear & place the battery back in)
Extract param_mod.tar.md5 from droid_charge_param_mod.zip
Flash hacked param_mod.tar.md5 via Odin3 in the PDA area _*ONLY*_
Reboot into CWM recovery
Mount the system partition from within CWM
Open ADB shell
Enter these commands:
Code:
mount -o remount,rw /dev/block/stl7 /mnt/.lfs
cp /sdcard/logo.jpg /mnt/.lfs/logo.jpg
Reboot and enjoy!
Notes:
I've tested multiple versions of Heimdall with just the modified param.lfs & it fails to upload 99 times out of 100. I recommend Odin3, SamsungPST Lite, or redbend_ua.
The boot splash image only appears for a short while since the Droid Charge kernels have splash images, too. If you'd like the same image for the duration of boot, utilize an app or a guide to change your favorite kernel's splash image.
Mirror:
modded param.lfs - http://db.tt/fjyx4uEf
sample boot splash - http://db.tt/Nj26hmb6
original param.lfs - http://db.tt/HcCZ6O0H
Sources:
Free Your Android - Modifying Samsung Splash Screens (Galaxy S Series + SGS2) <- how I learned to do it
[Mod][ec09] samsung boot splash/image change 7.7.11 - xda-developers <- how I learned about it with the Fascinate
Fixes & verification of FP5E by Tanno of DroidForums

Attempted and soft-bricked phone, I am sure it was my fault, but if you are not comfortable fixing your phone then do not try this mod. That being said it looks sweet and thanks for your effort!

Endless2232 said:
Attempted and soft-bricked phone, I am sure it was my fault, but if you are not comfortable fixing your phone then do not try this mod. That being said it looks sweet and thanks for your effort!
Click to expand...
Click to collapse
Did you happen to select "Re-partition"? That will soft-brick your phone if you're only flashing the param.lfs.

CrimsonKnight13 said:
Did you happen to select "Re-partition"? That will soft-brick your phone if you're only flashing the param.lfs.
Click to expand...
Click to collapse
Nope, not a complete idiot. =) haha. I will try again later and report back.

Endless2232 said:
Nope, not a complete idiot. =) haha. I will try again later and report back.
Click to expand...
Click to collapse
I was hoping for the best. I'll do what I can to help & correct any errors that jack phones up. :fingers-crossed:

This looks great; thanks for doing this! I'll give this a try in a few days once I'm reunited with my laptop (and hence have access to Odin).
Some suggestions:
It would be good to provide the stock param.lfs for people who want to return to the original boot logo. Alternatively, you could provide a CWM zip for people who have the mod installed to revert to the original logo.
It's possible to mount filesystems and perform file operations using the Android recovery, so you could create a CWM zip and just instruct people to drop in their logo image of choice and flash it after applying the base modification through Odin. This would reduce the steps required to just flashing the Odin package and then flashing a CWM zip.
Would it be possible to flash the param.lfs file through CWM? This would simplify things even further.
Anyway, thanks again and I look forward to trying this out!

substanceD said:
This looks great; thanks for doing this! I'll give this a try in a few days once I'm reunited with my laptop (and hence have access to Odin).
Some suggestions:
It would be good to provide the stock param.lfs for people who want to return to the original boot logo. Alternatively, you could provide a CWM zip for people who have the mod installed to revert to the original logo.
It's possible to mount filesystems and perform file operations using the Android recovery, so you could create a CWM zip and just instruct people to drop in their logo image of choice and flash it after applying the base modification through Odin. This would reduce the steps required to just flashing the Odin package and then flashing a CWM zip.
Would it be possible to flash the param.lfs file through CWM? This would simplify things even further.
Anyway, thanks again and I look forward to trying this out!
Click to expand...
Click to collapse
Original param.lfs in tar.md5 format will be posted tonight.
I'm reading mixed news regarding /mnt/.lfs/ file flashing through CWM. Most people are saying its unflashable from CWM but I need to confirm that it can be done.
As far as I know, param.lfs can't be flashed through CWM.
Edit: It appears I can create a CWM zip but I'll need to dig into what others have made to verify that its doing what I need it to do.
http://forum.xda-developers.com/showthread.php?t=1474753

CrimsonKnight13 said:
Original param.lfs in tar.md5 format will be posted tonight.
I'm reading mixed news regarding /mnt/.lfs/ file flashing through CWM. Most people are saying its unflashable from CWM but I need to confirm that it can be done.
As far as I know, param.lfs can't be flashed through CWM.
Edit: It appears I can create a CWM zip but I'll need to dig into what others have made to verify that its doing what I need it to do.
http://forum.xda-developers.com/showthread.php?t=1474753
Click to expand...
Click to collapse
I'm sure others will get to this before I do, but I'll tinker a bit with this as well - at least in reference to exploring what cwm recovery can do.

Works.
Sent from my SCH-I510 using xda premium

dwitherell said:
I'm sure others will get to this before I do, but I'll tinker a bit with this as well - at least in reference to exploring what cwm recovery can do.
Click to expand...
Click to collapse
Any community effort to make this into a smooth working mod is fine with me. I'll do more research myself tonight.
kvswim said:
Works.
Click to expand...
Click to collapse
Great to know.

I attempted to make a usable CWM zip but it fails with a line in the updater-script.
assert(package_extract_file("param.lfs", "/tmp/param.lfs"),write_raw_image("/tmp/param.lfs", "/dev/block/stl7"),delete("/tmp/param.lfs"));
Click to expand...
Click to collapse
It gives the error:
assert failed: write_raw_image("/tmp/param.lfs", "/dev/block/stl7")
<snip> (Status 7)
Click to expand...
Click to collapse
I'm wondering if /dev/block/stl7 is even writable from CWM.
I have attached both zips for anyone's perusal.

CrimsonKnight13 said:
I attempted to make a usable CWM zip but it fails with a line in the updater-script.
It gives the error:
I'm wondering if /dev/block/stl7 is even writable from CWM.
I have attached both zips for anyone's perusal.
Click to expand...
Click to collapse
I've been playing around with things on my end - but it seems you are right. I've had no luck w/ this as well. Tried a few changes but to no avail. Ah well - other than that your original method worked for me

dwitherell said:
I've been playing around with things on my end - but it seems you are right. I've had no luck w/ this as well. Tried a few changes but to no avail. Ah well - other than that your original method worked for me
Click to expand...
Click to collapse
I'm glad that the original method does work & that we both came to the same conclusion. Thanks for looking into it.
Is there a method to split the zImage, change the RLE, & rejoin it into a workable kernel? Making this thread into a boot & kernel splash image mod combo would be nice. I'm coming up empty handed with my searches through Google & XDA. Most modifications are for Sony phones.

Is step #7 something that can be done within the stock recovery or is that a separate ADB command?

nismology said:
Is step #7 something that can be done within the stock recovery or is that a separate ADB command?
Click to expand...
Click to collapse
I don't recommend EVER using stock recovery due to the possibility of complications with custom-built zips.
/system can be mounted via adb shell as well. The step assumes that you know how to do it via cwm or adb. If I need to clarify, I can.

CrimsonKnight13 said:
I don't recommend EVER using stock recovery due to the possibility of complications with custom-built zips.
/system can be mounted via adb shell as well. The step assumes that you know how to do it via cwm or adb. If I need to clarify, I can.
Click to expand...
Click to collapse
I was in the process of attempting the ADB method of this mod and had CWM installed which was overwritten by the modded param file and step 6 says allow it to boot into recovery which turned out to be the stock one. I guess that is what threw me off.
I guess I didn't know I had to re-Odin CWM to remount the system partition. Just for posterity though, what is the command for mounting it via ADB? I have it all setup already. Thanks for your patience!
Edit: I got it to work. I had to let it boot up, enter shell, get superuser permission, then execute the mount command. This was great ADB practice for a newb like myself. Excellent work and it looks great! Thanks for the how-to!
:good:

nismology said:
I was in the process of attempting the ADB method of this mod and had CWM installed which was overwritten by the modded param file and step 6 says allow it to boot into recovery which turned out to be the stock one. I guess that is what threw me off.
I guess I didn't know I had to re-Odin CWM to remount the system partition. Just for posterity though, what is the command for mounting it via ADB? I have it all setup already. Thanks for your patience!
Click to expand...
Click to collapse
It doesn't & won't overwrite CWM. It is merely overwriting the /dev/block/stl7 partition of your phone.
The mount for system varies if you have rfs or ext4.
rfs
mount once: mount -t rfs -o rw /dev/block/stl10 /system
remount: mount -t rfs -o remount,rw /dev/block/stl10 /system
ext4
mount once: mount -t ext4 -o rw /dev/block/stl10 /system
remount: mount -t ext4 -o remount,rw /dev/block/stl10 /system
nismology said:
Edit: I got it to work. I had to let it boot up, enter shell, get superuser permission, then execute the mount command. This was great ADB practice for a newb like myself. Excellent work and it looks great! Thanks for the how-to!
:good:
Click to expand...
Click to collapse
Good to know. I'm glad it worked out for you.
Just doing mount is another good way since it calls up fstab or whatever equivalent it might be on the system.

CrimsonKnight13 said:
It doesn't & won't overwrite CWM. It is merely overwriting the /dev/block/stl7 partition of your phone.
The mount for system varies if you have rfs or ext4.
rfs
mount once: mount -t rfs -o rw /dev/block/stl10 /system
remount: mount -t rfs -o remount,rw /dev/block/stl10 /system
ext4
mount once: mount -t ext4 -o rw /dev/block/stl10 /system
remount: mount -t ext4 -o remount,rw /dev/block/stl10 /system
Good to know. I'm glad it worked out for you.
Just doing mount is another good way since it calls up fstab or whatever equivalent it might be on the system.
Click to expand...
Click to collapse
Thanks for that. I used a slightly different syntax for mounting /system but it seemed to work out anyway.
And by "just doing mount" are you referring to doing it through CWM? That might be a more straight-forward method indeed. I could use the ADB practice though.

And the original source of my confusion was that step #6 says "allow the phone to reboot into recovery". When you flash the modded param and power on the phone, it automatically boots into stock recovery. It might help other people if the step mentions the fact that you must enter into CWM to mount the system partition instead of "allowing" it to boot up normally, which will result in stock recovery after initial boot-up.

nismology said:
And the original source of my confusion was that step #6 says "allow the phone to reboot into recovery". When you flash the modded param and power on the phone, it automatically boots into stock recovery. It might help other people if the step mentions the fact that you must enter into CWM to mount the system partition instead of "allowing" it to boot up normally, which will result in stock recovery after initial boot-up.
Click to expand...
Click to collapse
As I said, it shouldn't be booting into stock recovery when the modded param.lfs is pushed. If you have already flashed a custom kernel, CWM recovery will stay. If you still have a stock kernel, stock recovery will constantly take over.
Additionally, whenever I did it, due to lack of logo.jpg, it would kick me straight into CWM. I'm unsure what your setup on your phone looks like though.
nismology said:
Thanks for that. I used a slightly different syntax for mounting /system but it seemed to work out anyway.
And by "just doing mount" are you referring to doing it through CWM? That might be a more straight-forward method indeed. I could use the ADB practice though.
Click to expand...
Click to collapse
Yes, mounting through CWM is the easiest way.

[Q] Infuse 4g looping even after flashing back to GB2.3.6

Hi guys, I have been pulling my hair out trying to figure out how to bring my infuse back to life, I upgraded to GB 2.3.6 from froyo 2.2.1 a while back. a couple of days ago it just died and could not get back in no matter what (constantly rebooting) so I flashed back to stock with "Heimdall One-click Back-To-Stock UCLB3" and it completes just fine but it does not boot normally. it reboots after the AT&T screen.
I read something about the partition been altered when it was updated to 2.3.6, is that a fact? also I'm not able to use recovery (red recovery) to get it to see the external SD card so I'm really stuck, please help
I would love to be able to update to 4.2.2 any rom.
Thanks a bunch
sorry if I'm posting in the wrong section

Have you tried flashing the heimdall package a second time? Or using heimdall to flash a custom kernel to get red CWM?
Try loading recovery (stock or CWM) and let it sit for a minute (just to see if it reboots by itself there too). You do this by holding power+vol up+vol down then releasing only power when you see the Samsung logo.
Note also that you will only be able to see the internal sd card from recovery and that sd-ext does not refer to the external sd card despite the similarity of the name.
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Have you tried flashing the heimdall package a second time? Or using heimdall to flash a custom kernel to get red CWM?
Try loading recovery (stock or CWM) and let it sit for a minute (just to see if it reboots by itself there too). You do this by holding power+vol up+vol down then releasing only power when you see the Samsung logo.
Note also that you will only be able to see the internal sd card from recovery and that sd-ext does not refer to the external sd card despite the similarity of the name.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
OK, tried to flash the heimdall package again but I had the same result(rebooting att animation even after doing the reset from the 3e recovery menu). let the recovery screen sit (it does not reboot). searched for a custom kernel like you suggested and went to this page (http://forum.xda-developers.com/showthread.php?t=1603220) and was able to flash the kernel but all that did was replace the att animation with "android" but still rebooting. i'm trying to flash with Odin from this page (http://forum.xda-developers.com/showthread.php?p=27123262) and i'll report back.
meanwhile I would like to know how to get access to the internal sd memory to be able to copy things there?
I appreciate you time and effort tying to help.

Your best bet for flashing Odin or heimdall stock packages are found in the super everything thread, 2nd and 3rd options in first section - check my sig for link. The ones with repartitioning may resolve the issues you are having.
After the ROM flash...
Try installing a custom kernel/recovery from either the odin page you linked above, or via heimdall (posts 2 or 3 here):
http://forum.xda-developers.com/showthread.php?p=23118134
Once installed and you reboot, you may see a Samsung or blank screen for about 5 minutes with a robot voice speaking periodically - this is normal, let it finish.
Boot into recovery, it should be red.
If you are still not able to boot into the phone OS, but are able to get red recovery, you can try loading the android sdk and running adb or adbmagic to copy rom install files to your internal sd card (/sdcard)..
Lastly andros11 published a guide on how to get to JB from stock ... If you have red recovery and can get files on your internal sdcard this guide shows how to get the rest of the way to JB.
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Your best bet for flashing Odin or heimdall stock packages are found in the super everything thread, 2nd and 3rd options in first section - check my sig for link. The ones with repartitioning may resolve the issues you are having.
After the ROM flash...
Try installing a custom kernel/recovery from either the odin page you linked above, or via heimdall (posts 2 or 3 here):
http://forum.xda-developers.com/showthread.php?p=23118134
Once installed and you reboot, you may see a Samsung or blank screen for about 5 minutes with a robot voice speaking periodically - this is normal, let it finish.
Boot into recovery, it should be red.
If you are still not able to boot into the phone OS, but are able to get red recovery, you can try loading the android sdk and running adb or adbmagic to copy rom install files to your internal sd card (/sdcard)..
Lastly andros11 published a guide on how to get to JB from stock ... If you have red recovery and can get files on your internal sdcard this guide shows how to get the rest of the way to JB.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
The only rom that seems to stop the loops was "stock root mod3e UCKD5 Odin , but it seems to boot to a black screen,(at least is something) also my recovery has a couple more options like reinstall package and format internal sd card (Samsung recovery utils for BML), any ideas?
Thanks

Can you provide more detail about all the things you have tried so far?
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Can you provide more detail about all the things you have tried so far?
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I have tried Stock_SGH_I997_UCLB3_Repartition-One-Click, SGH-i997-UCKJ4-One-Click, SGH-i997 InfuZen-A16 Kernel One-Click, SGH_I997 Entropy 4_4_2012-One-Click-Heimdall, GTGs_Ultimate_Unbrick, DFT_Summy_Rainbow, not necessarily in that order but the first one I tried was UCLB3_Unbrick_w_root (odin) and then I997UCLB3-GB-bootloaders-only.tar
I know I should have wrote things down but here we are. is there a way to completely start over? or maybe may be do it in steps like partitioning first then flash? i'm also totally lost with all the terms since I don't think I have red recovery at all. I read so many things these past three days.
I really appreciate your help and time and I would understand if this is a lost cause.

Probably not a lost cause. It's tough to brick this phone.
1. Check your drivers.. Use Samsung drivers for Infuse, not Kies. You may need to uninstall both, then install just Infuse drivers. Make sure you are using a high quality and reliable usb cable.
2. Boot recovery, red preferred. Do a factory reset, then format system (available in red recovery)
3. Battery pull, boot into download mode. Try odin or heimdall uclb3 with repartition option. Follow instructions exactly.
4. Boot phone normal.
5. If this works, next step is to flash a custom recovery, convert file system (robot voice, wait), boot phone, copy the roms you need to internal sdcard then follow andros11 guide to continue to jb... (I recommend removing the external sdcard before step 5 to eliminate possibility of using the wrong sd card by accident).
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Probably not a lost cause. It's tough to brick this phone.
1. Check your drivers.. Use Samsung drivers for Infuse, not Kies. You may need to uninstall both, then install just Infuse drivers. Make sure you are using a high quality and reliable usb cable.
2. Boot recovery, red preferred. Do a factory reset, then format system (available in red recovery)
3. Battery pull, boot into download mode. Try odin or heimdall uclb3 with repartition option. Follow instructions exactly.
4. Boot phone normal.
5. If this works, next step is to flash a custom recovery, convert file system (robot voice, wait), boot phone, copy the roms you need to internal sdcard then follow andros11 guide to continue to jb... (I recommend removing the external sdcard before step 5 to eliminate possibility of using the wrong sd card by accident).
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
SO do I need to flash a new rom to be able to boot red recovery?
Thanks

skopedia said:
SO do I need to flash a new rom to be able to boot red recovery?
Thanks
Click to expand...
Click to collapse
Just a custom kernel. On the infuse recovery is included in the kernel.
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Just a custom kernel. On the infuse recovery is included in the kernel.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I just flashed 2012.04.05-ODIN-Entropy_DD-GB-zImage custom kernel on it, is there a trick to be boot to red recovery? I must be doing something wrong.. everything I read is talking about accessing the internal memory to copy to it and install zip from there (remember that I'm not able to do that since I'm not able to boot to rom) please clarify as much as you can.
Thanks

I mentioned that a few posts back... Hold both volume buttons plus power until you see the Samsung logo then release just power. Continue holding volume buttons until recovery loads.
Next steps are as in my previous post, or, with a bit of research on your part attempting to copy rom files via adb, then flashing via red recovery.
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Just a custom kernel. On the infuse recovery is included in the kernel.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
finally after many tries, I was able to get cwm recovery 5.5.0.4 by flashing an ICS kernel (jt1134's kernel) from here . not sure why it worked !
http://forum.xda-developers.com/showpost.php?p=25526654&postcount=3
So could you please advice as to how I can enable usb debugging without normal phone boot so I can copy files on the sd? I downloaded sdk but it will not detect the phone when i'm in recovery mode using the "adb devices" command
if I can copy files to the sd card via command line with adb, what kind of rom can I put and run from there? will I be able to run jb 4.2.2?
Thanks

skopedia said:
finally after many tries, I was able to get cwm recovery 5.5.0.4 by flashing an ICS kernel (jt1134's kernel) from here . not sure why it worked !
http://forum.xda-developers.com/showpost.php?p=25526654&postcount=3
So could you please advice as to how I can enable usb debugging without normal phone boot so I can copy files on the sd? I downloaded sdk but it will not detect the phone when i'm in recovery mode using the "adb devices" command
if I can copy files to the sd card via command line with adb, what kind of rom can I put and run from there? will I be able to run jb 4.2.2?
Thanks
Click to expand...
Click to collapse
You need the Samsung usb driver if you don't have it already (smaller of the two files):
http://www.samsung.com/us/support/owners/product/SGH-I997ZKAATT
(If you installed kies previously, I would recommend uninstalling that and installing only the usb driver)
Once you get adb working, you can follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1667929
to push all the rom packages you need - This will include CM9 plus any of the JB roms you want (follow Andros11's guide once the roms are copied successfully). for first JB rom I recommend going with CM10.1 to ensure the file system conversions are completed correctly - read instructions carefully. In some cases a double flash from CWM may be needed.
Side note - Given the issues you have been having with Heimdall and Odin, it is possible that your USB connection is unreliable. Have you tried different, new, better cables or different USB ports for adb access?

Zen Arcade said:
You need the Samsung usb driver if you don't have it already (smaller of the two files):
http://www.samsung.com/us/support/owners/product/SGH-I997ZKAATT
(If you installed kies previously, I would recommend uninstalling that and installing only the usb driver)
Once you get adb working, you can follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1667929
to push all the rom packages you need - This will include CM9 plus any of the JB roms you want (follow Andros11's guide once the roms are copied successfully). for first JB rom I recommend going with CM10.1 to ensure the file system conversions are completed correctly - read instructions carefully. In some cases a double flash from CWM may be needed.
Side note - Given the issues you have been having with Heimdall and Odin, it is possible that your USB connection is unreliable. Have you tried different, new, better cables or different USB ports for adb access?
Click to expand...
Click to collapse
I never had trouble flashing with odin or heimdall so I know my cable and usb are fine, even though I have tried new PC and usb port and cable before with the same results so I know the issue is with the phone.i haveno keis installed, just USB drivers.
the link you provided call for swm to show unmout system and sdcard, but clicking on them gives me error mounting\system and mounting\sdcard so i'm stuck yet again

skopedia said:
I never had trouble flashing with odin or heimdall so I know my cable and usb are fine, even though I have tried new PC and usb port and cable before with the same results so I know the issue is with the phone.i haveno keis installed, just USB drivers.
the link you provided call for swm to show unmout system and sdcard, but clicking on them gives me error mounting\system and mounting\sdcard so i'm stuck yet again
Click to expand...
Click to collapse
OK - so when you go the the mounts menu, both /system and /sdcard show as unmounted, and when you click on them you get an error? Were you able to get adb working with this recovery? If so, please run "adb shell" then at the prompt run "mount" then mark/paste the output here. That will help confirm whether you have a viable file system on your phone. (If not, that would partially explain why the stock revert packages are not working).

skopedia said:
Hi guys, I have been pulling my hair out trying to figure out how to bring my infuse back to life, I upgraded to GB 2.3.6 from froyo 2.2.1 a while back. a couple of days ago it just died and could not get back in no matter what (constantly rebooting) so I flashed back to stock with "Heimdall One-click Back-To-Stock UCLB3" and it completes just fine but it does not boot normally. it reboots after the AT&T screen.
I read something about the partition been altered when it was updated to 2.3.6, is that a fact? also I'm not able to use recovery (red recovery) to get it to see the external SD card so I'm really stuck, please help
I would love to be able to update to 4.2.2 any rom.
Thanks a bunch
sorry if I'm posting in the wrong section
Click to expand...
Click to collapse
Hey! Check the power button of the infuse i have the ramdomly rebooting problem too i was thinking that i was a rom problem but no the power button of the infuse get dirty from inside and get stock i clean my power button and never have the randomly reboot problem again

Zen Arcade said:
OK - so when you go the the mounts menu, both /system and /sdcard show as unmounted, and when you click on them you get an error? Were you able to get adb working with this recovery? If so, please run "adb shell" then at the prompt run "mount" then mark/paste the output here. That will help confirm whether you have a viable file system on your phone. (If not, that would partially explain why the stock revert packages are not working).
Click to expand...
Click to collapse
Sorry it took so long to respond. I was almost ready to give up, I found this page http://forum.xda-developers.com/showthread.php?t=1767837
where it had a new driver link listed which allowed me to use adb properly on the same pc and usb cable. (before this, it would just say no device attached). I did run the first section on the first post to completion (and flashed froyo refuse_v1.7_cwm.zip)but it still won't boot normally.reboots to recovery screen and it freezes there.)(see photo)
so here are the outputs you requested
/ # mount
mount
rootfs / rootfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=
utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=utf8 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/stl11 /cache rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=
utf8 0 0
/dev/block/stl10 /dbdata rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/ #
I appreciate your help.
I would love to be able to update the to the latest stable rom and also please be specific to what I need to do next.
Thanks

alexischino said:
Hey! Check the power button of the infuse i have the ramdomly rebooting problem too i was thinking that i was a rom problem but no the power button of the infuse get dirty from inside and get stock i clean my power button and never have the randomly reboot problem again
Click to expand...
Click to collapse
I'm afraid my problem was more that just a stuck power button. I have taken the cover off and cleaned what I could but I does not make a deference.
Thanks

skopedia said:
Sorry it took so long to respond. I was almost ready to give up, I found this page http://forum.xda-developers.com/showthread.php?t=1767837
where it had a new driver link listed which allowed me to use adb properly on the same pc and usb cable. (before this, it would just say no device attached). I did run the first section on the first post to completion (and flashed froyo refuse_v1.7_cwm.zip)but it still won't boot normally.reboots to recovery screen and it freezes there.)(see photo)
so here are the outputs you requested
/ # mount
mount
rootfs / rootfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=
utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=utf8 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/stl11 /cache rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=
utf8 0 0
/dev/block/stl10 /dbdata rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/ #
I appreciate your help.
I would love to be able to update the to the latest stable rom and also please be specific to what I need to do next.
Thanks
Click to expand...
Click to collapse
From what you have posted, and from the error messages shown in your picture of recovery after attempting to format the sdcard there are two possibilities:
1 - your internal SD card (which contains /data and /sdcard) is dead
2 - your internal SD card is corrupted
Scenario 1 - try for warranty repair if still covered, or see if a repair shop can help (MobileTechVideos.com gets frequent mentions on XDA as a reasonable option for many infuse4g repairs).
Scenario 2 - if the SD card is corrupted there may be a way back, but it requires advanced steps - using programs such as parted and fdisk to repartition the problem device and reformat the two file systems (/data and /sdcard on the infuse). I'm not aware of a guide specifically for the infuse, but there are some available for the i9000 which might be adaptable. You'll likely need to be running a kernel/recovery combo that includes root/su access to be able to use these tools, plus do some research to determine the correct command syntax. If you are not familiar with linux system-level command line utilities, or the equivalent on windows, it's probably best to skip this option.
Lastly, read through this thread from last year. Similar issues to yours - http://forum.xda-developers.com/showthread.php?t=1581977
One person was able to finally recover by flashing GTG's Odin unbrick package - might be worth a try, perhaps from a different PC if one is available):
thread (instructions) - http://forum.xda-developers.com/showthread.php?t=1116251
mirror (files) - http://d-h.st/7DB
Note that if you are running a newer version of the samsung infuse usb drivers, you may need a newer version of Odin (gtg package references v1.7). I use version 3.07 now, but others report success with 1.85 - here's a link to all Odin versions for download - http://forum.xda-developers.com/showthread.php?t=2189539
Good luck.

[Q] Accidentally Wiped /system, Can't Flash ROM

I was going to install a superuser.zip file to root my M4 but when I went to wipe the /cache the /system get wiped as well. I can boot into either CWM or TWRP and have full fastboot/adb, but when I try to boot into Android it just brings me back to the bootloader. When I try to install a stock ROM it just says it's flashing it but hangs at a certain point, I even had it run overnight and it still didn't install. When I try to flash a custom ROM suh as Cyanogenmod it either completes the flashing in about 2 seconds or greets me with an error. RUU and FUU don't seem to work. I'm 100% out of ideas now, and I'm open to anything to try.

legofan623 said:
I was going to install a superuser.zip file to root my M4 but when I went to wipe the /cache the /system get wiped as well. I can boot into either CWM or TWRP and have full fastboot/adb, but when I try to boot into Android it just brings me back to the bootloader. When I try to install a stock ROM it just says it's flashing it but hangs at a certain point, I even had it run overnight and it still didn't install. When I try to flash a custom ROM suh as Cyanogenmod it either completes the flashing in about 2 seconds or greets me with an error. RUU and FUU don't seem to work. I'm 100% out of ideas now, and I'm open to anything to try.
Click to expand...
Click to collapse
Andyt95 said:
Download Magio R4
reboot into recovery, type in cmd
Code:
adb devices
adb shell
mount data
exit
adb push /path/to/magioR4.zip /data/
[I](you should reboot here, in which case you'll
need to type[/I] "mount data" [I]again after adb shell,
but it's not really essential and should work anyway)[/I]
adb shell
mount /data /sdcard [I](creates a virtual sdcard)[/I]
flash your ROM in recovery just like you would normally (select .zip from sdcard) and boot up
run rumrunner, it should work, giving you S-OFF which will let you flash absolutely anything. If it doesn't, let me know and I'll come up with a workaround.
Click to expand...
Click to collapse
should work

Andyt95 said:
should work
Click to expand...
Click to collapse
Well first:
~ # ←[6nmount data
mount data
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
But instead I just used a USB OTG and flash drive so no big deal
And then Magio popped up with its installer and I went through that and then hit "reboot" to be greeted with the bootloader, so I hit "reboot" in the bootloader, but it still brings me back to the bootloader immediately after a black screen, so I thought "Oops, needed to flash the boot.img", so boot.img was then flashed. Now the green HTC logo is sitting there and isn't doing anything, probably frozen.

Code:
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
means /data is already mounted

I actually got it up and running from a nandroid restore, I tried it once before but the restore didnt finish so I thought it wouldnt work. Thanks for helping me out anyway though!