Database Info

[ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g

[ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g
ABOUT
--------------
These Odin flashable tar.md5 packages contain the stock AT&T 2.3.6 Gingerbread release for the Samsung Infuse 4G with root added.
For those who are interested, there are also rooted options below that have busybox and are deodexed and zipaligned. An option is also provided below that includes CWM recovery and a few extras.
These rooted Odin packages do not contain bootloaders. Have rainbow distortion and want GB bootloaders to fix that? See question 1.) in the FAQ below for an explanation, warning, and link to a separate package that contains and flashes Gingerbread bootloaders.
The first two versions below use the stock UCLB3 kernel and have stock recovery. The third option below uses Entropy's Daily Driver (April 5th, 2012 test kernel with working MHL HDMI out), and includes red CWM recovery. For more information about Entropy512's kernel, go HERE.
INSTALL
--------------
1.) Download Odin from HERE and extract the program from the .zip file.
2.) Download the version you want. Use a program like 7zip to extract the Odin flashable tar.md5 from the .rar file.:
**** OPTION A ****
I997UCLB3-root.rar
Features in this version
- Stock kernel
- Stock recovery
- Rooted
******* OPTION B *******
I997UCLB3-root-deodex.rar
Features in this version
- Stock kernel
- Stock recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
************ OPTION C *************
I997UCLB3-CWM-root-deodex-extras.rar
Features in this version
- Entropy's Daily Driver kernel
- Red CWM recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
- AT&T and other bloatware removed
- Scrolling wallpaper fix
- CRT off animation
- 8 lock screens
- Extended power menu
- Accurate battery mod
- Get lidroid's 14 statusbar toggles HERE
************ OPTION D *************
I997UCLB3-CWM-root-deodex.rar
Features in this version
- Entropy's Daily Driver kernel
- Red CWM recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
- Get extra mods HERE
Want to try some different kernels, like Zen Arcade's Infusion-Z? Odin kernel packages are HERE.
3.) Install Samsung Kies to install the latest Samsung USB drivers. This can be found HERE.
Reboot PC. Then, attach phone via USB, and allow drivers to install.
4.) In recovery, wipe all user data and wipe all cache data, BEFORE flashing. If you don't do this, I can't guarantee that your phone won't loop at the AT&T boot animation, or that you won't have other issues.
Put phone in Recovery Mode (Turn phone off, disconnect USB cable, hold power button and both volume buttons, release power button when Samsung logo appears, continue to hold volume buttons until recovery screen appears.). In recovery, choose and follow prompts for options to wipe user data and to wipe cache data.
5.) Place phone in Download Mode (Remove battery, hold down both volume buttons, replace battery, attach USB cable, and then continue to hold volume buttons until the phone enters Download Mode.).
6.) With phone in Download Mode, open the Odin exe. In Odin, if the phone is recognized, the window under ID:COM will turn yellow.
7.) In Odin, click on "PDA" and browse to the tar.md5.
8.) Select the tar.md5. Make sure it shows up in the PDA window, and then click on Start. Do not power off or disconnect the phone while Odin flashes the package and reboots the phone.
9.) You're finished. You now have stock AT&T 2.3.6 Gingerbread (UCLB3) with root.
NOTES
----------------
a.) If you skipped step 4.) and your phone boot loops at the AT&T boot animation, hold down the power button and both volume buttons until you enter recovery. In recovery, wipe all user data and wipe all cache data. Reboot and the phone will boot into rooted 2.3.6 Gingerbread.
b.) If everything has been done correctly, the Setup Wizard will appear when you first boot Gingerbread. If the phone first boots into Gingerbread, and you don't get the Setup Wizard, go to Settings / Privacy / Factory data reset and choose "Reset Phone".
FAQ
-----------------
1.) I have rainbow distortion in recovery or in the boot animation. How can I get Gingerbread bootloaders to fix this?:
You can download THIS .rar file, extract using 7zip, and flash the tar.md5 package in Odin (use the pda slot). Flashing Gingerbread bootloaders will correct rainbow distortion in recovery and in the boot animation. Only flash these if you are having issues with rainbow distortion, and only if you have had success flashing other, less dangerous items in Odin. If something happens to cause a flash of these bootloaders to fail, then you run the risk of bricking your phone. See THIS post and THIS post for more of an explanation of why bootloaders weren't included in the rooted UCLB3 Odin packages.
2.) Isn't there a way to root stock UCLB3 Gingerbread without flashing these Odin packages?:
Yes. See THIS how-to thread that I put together for an explanation of how to root stock UCLB3.
3.) How do I get CWM recovery if I flashed a version with the stock kernel?:
If you didn't flash Option C with CWM recovery already included, you can flash a custom kernel that includes CWM recovery by using SGS Kernel Flasher on the phone. Find and install SGS Kernel Flasher in Android Market / Google Play Store. Then, place the zImage of a compatible custom kernel that includes CWM recovery on your internal sdcard, and flash using SGS Kernel Flasher. Entropy's Daily Driver, includes red CWM recovery, and can be found HERE.
4.) My phone is displaying something that looks like this: Phone-!-PC. What is this, and can I use these Odin packages from here?
That is still download mode. If you reach that screen, a flash has been interrupted or has failed, and you are in a type of backup download mode. Reset Odin, and start over with your flash. These packages will flash in this mode, just as they will in regular download mode.
THANKS
-----------------
ChainsDD for root bits
Entropy512 for his kernel
NunHugger for 8 lockscreens, extended power menu, and accurate battery mod
gtg465x for posts on how to dump factoryfs.rfs
imnuts for posts on how to create Odin images
Przekret for the Samsung UCLB3 leak
Everyone in the Infuse 4g XDA forum
Hope this helps someone out. Please use this thread for any questions or comments about using the Odin packages. It's okay to ask UCLB3 related questions here also, but remember, I didn't create the firmware. That one is on Samsung / AT&T, and these are just packages provided to make it easier to get root and /or CWM recovery with that firmware.

Good Job, bro.

Very nice. Thanks
Sent from my MB865 using xda premium

Using this for a day. And I like it very much. All functionas that I need is working perfectly for now. With root I can customize stock as I want. Thanks. As for me this is best ROM out here!

Is there any interest in a deodexed version also in this format?
Sent from my SGH-I997 using Tapatalk 2

jscott30 said:
Is there any interest in a deodexed version also in this format?
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yes there is. The deodexed version has a lot less lag. I ran the leak for about a month when it was released and then i flashed the deodexed version and you can tell a big difference.
Sent from my MB865 using xda premium

Yeah, when I was using UCLB3 (on CM9 now), I had it deodexed and preferred it that way.
When I get home from work, I'll make and upload a deodexed version in this format.
Sent from my SGH-I997 using Tapatalk 2

Thanks for taking the time to do that.
Sent from my MB865 using xda premium

jscott30 said:
Is there any interest in a deodexed version also in this format?
Click to expand...
Click to collapse
Cant tell about this for sure. I've used only UCLB3 stock and [UCBL3] [Dev]astation [2.3.6]. First is good and have many usefull functions and they are working fine (fast GPS, Car Holder, correct bluetoth and many other). Second one is a lot faster but not all functions are working, GPS is realy slow also stability is not so great for me. Right now current your ROM is good for me becouse it has thing that I needed being on UCLB3 - ROOT. If deodexed version will add speed and will not make this ROM less stable, than people will love it. Me for sure =)

dredik said:
If deodexed version will add speed and will not make this ROM less stable, than people will love it. Me for sure =)
Click to expand...
Click to collapse
This will just optimize system apps and framework stuff that depends on .odex files, and will make it easier to mod system and framework files. Nothing major; everything will still work like stock. I'll keep the stock version available also.
Sent from my SGH-I997 using Tapatalk 2

jscott30 said:
This will just optimize system apps that depend on .odex files. Nothing major; everything will still work like stock. I'll keep the stock version available also.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
jscott,
The tar you packed was with the stock kernel, correct?

qkster said:
jscott,
The tar you packed was with the stock kernel, correct?
Click to expand...
Click to collapse
Correct. This package uses the stock kernel. That being said is there any interest also in another version w/ Entropy's Daily Driver
and CWM recovery in this format? I'll have to get Entropy's permission, but can do that also.
Sent from my SGH-I997 using Tapatalk 2

jscott30 said:
Correct. This package uses the stock kernel. That being said is there any interest also in another version w/ Entropy's Daily Driver
and CWM recovery in this format? I'll have to get Entropy's permission, but can do that also.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
So if everything on stock hdmi works too then?
Thanks...
Edit: Never mind i decided to flash this with other infuse and will update later the result...Thank a lot....

jscott30 said:
Correct. This package uses the stock kernel. That being said is there any interest also in another version w/ Entropy's Daily Driver
and CWM recovery in this format? I'll have to get Entropy's permission, but can do that also.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
I was curious, mostly.
2 wks ago, I had put together a method to root the UCLB3 when we saw a spike in how to root this thing in the Q/A everyday. It consisted of a cwm-flashable that installed busybox and superuser, then deleted most ATT bloats. And then installed google talk video from the G-Nex.
To get to cwm, I had a Heimdall-1-click of Entropy's DD kernel. I suppose any GB insecure kernel would work too. Entropy's latest would be nice because it would also have HDMI and CWM recovery.
After the kernel flash, you can boot into recovery and flash the cwm package.
And then UCLB3 would be "rooted", busybox and SuperUser.apk. Plus some bonuses (Gtalk, Gvoice, Terminal Emulator and minus ATT bloats. It was painful but I left Facebook and a few others in place)
Once you started with the Tar for Odin, I made a Heimdall-1-click for this rooted ROM as well. What was odd was that I had corrected the vold.fstab for the external sdcard access, before copying over the factory.rfs.
After the package was put together, the vold.fstab reverted back to mm2 instead of mm1 for the stock kernel.
Odd...
I didn't know if that happened to you or not.
Anyway, imo, I don't think you need to worry about another version with Entropy'd DD, I think most users should be able to use SGS-Kernel flasher to get to cwm.
About the deodex aspect, dman already made up a deodex version...I thought it was odd that others didn't use it. It may also be redundant too, but that's just my opinion.
I think the Odex apk do not make dalvik caches. Thereby, have a fast boot time and less chance of cache corruption. I've been using the odex rooted version with the stock kernel, and have noted an initial lag, but after leaving the phone alone for 20 minutes, it is pretty responsive and snappy.
This stock rom is missing Lidroid's, Battery mod, and a few other things..but then, after you add those, lol..we are running vagabond, spartan, pharmnerd midagu's etc...
If anyone wants a heimdall 1 click...

qkster said:
I was curious, mostly.
2 wks ago, I had put together a method to root the UCLB3 when we saw a spike in how to root this thing in the Q/A everyday. It consisted of a cwm-flashable that installed busybox and superuser, then deleted most ATT bloats. And then installed google talk video from the G-Nex.
To get to cwm, I had a Heimdall-1-click of Entropy's DD kernel. I suppose any GB insecure kernel would work too. Entropy's latest would be nice because it would also have HDMI and CWM recovery.
After the kernel flash, you can boot into recovery and flash the cwm package.
And then UCLB3 would be "rooted", busybox and SuperUser.apk. Plus some bonuses (Gtalk, Gvoice, Terminal Emulator and minus ATT bloats. It was painful but I left Facebook and a few others in place)
Once you started with the Tar for Odin, I made a Heimdall-1-click for this rooted ROM as well. What was odd was that I had corrected the vold.fstab for the external sdcard access, before copying over the factory.rfs.
After the package was put together, the vold.fstab reverted back to mm2 instead of mm1 for the stock kernel.
Odd...
I didn't know if that happened to you or not.
Anyway, imo, I don't think you need to worry about another version with Entropy'd DD, I think most users should be able to use SGS-Kernel flasher to get to cwm.
About the deodex aspect, dman already made up a deodex version...I thought it was odd that others didn't use it. It may also be redundant too, but that's just my opinion.
I think the Odex apk do not make dalvik caches. Thereby, have a fast boot time and less chance of cache corruption. I've been using the odex rooted version with the stock kernel, and have noted an initial lag, but after leaving the phone alone for 20 minutes, it is pretty responsive and snappy.
This stock rom is missing Lidroid's, Battery mod, and a few other things..but then, after you add those, lol..we are running vagabond, spartan, pharmnerd midagu's etc...
If anyone wants a heimdall 1 click...
Click to expand...
Click to collapse
I run a deodexed version and think having a odin version of it is just a extra way of having a lb3 deodexed available for me to use if need be. I dont use heimdall so odin is my preference.
Sent from my MB865 using xda premium

tmease1 said:
I run a deodexed version and think having a odin version of it is just a extra way of having a lb3 deodexed available for me to use if need be. I dont use heimdall so odin is my preference.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yes. I know that some odd people prefer Odin and others prefer heimdall. Jk..
Some use both. Either way, nbd.
I was thinking that there was already a deodex uclb3.

qkster said:
Yes. I know that some odd people prefer Odin and others prefer heimdall. Jk..
Some use both. Either way, nbd.
I was thinking that there was already a deodex uclb3.
Click to expand...
Click to collapse
I use both odin and heimdall...too

qkster said:
Yes. I know that some odd people prefer Odin and others prefer heimdall. Jk..
Some use both. Either way, nbd.
I was thinking that there was already a deodex uclb3.
Click to expand...
Click to collapse
Odin ftw .

Yeah, I get that great options have already been presented to do all of this. Didn't mean to step on any toes.
Some posters were asking for an Odin option, so I made one. I personally prefer Heimdall myself, but maybe Odin is easier for some.
This is mainly just another tool to get rooted stock UCLB3. Hopefully it helps some.
When I get home, I'll still do a deodexed version, but agree that it's easy enough to use SGS Kernel Flasher to get CWM recovery.
Sent from my SGH-I997 using Tapatalk 2

qkster said:
After the package was put together, the vold.fstab reverted back to mm2 instead of mm1 for the stock kernel. Odd... I didn't know if that happened to you or not.
Click to expand...
Click to collapse
qkster, that didn't happen to me when I made this package. But, that is probably because of the process I used to get the factoryfs.rfs. I got everything exactly how I wanted on the phone, including setting up vold.fstab after switching kernels back and forth during the root process, and then I did a system dump using dd on the phone after doing a factory reset.

Infuse Loops at Recovery after RemICS flashed.

____________________________________Solved, thanks for all who offered help.___________________________________
Hi All, I have just flashed the RemICS ROM 1.3 and i have followed the set of directions for Gingerbread users, which I previously was. The installation had been successful until I did the final Reboot, where it loops back into the Recovery mode even after numerous of re-flash and reboots. I'm pretty sure the ROM is installed, yet it would not load into the OS, thoughts? Thanks everyone in Advance.
http://forum.xda-developers.com/showthread.php?t=1613523 I had the option C installed initially, for everyone's info.
________________________________________________Solution________________________________________________
Finally got my ICS working now. Can't thank you enough for qkster Heimdall One Click Gingerbread ROM.
For everyone's reference, the following is what I've done;
1) Flashed the Heimdall One Click GB Stock rom, a big thanks to qkster,
2) Flashed the CWM Recovery just under the same thread,
3) Flashed the RemICS rom with factory wipe and formatting data, system and cache, again after reboot.
4) >Bootlooped at the SAMSUNG screen,
5) Followed the solution of bootlooping under the RemICS thread and flashed Heimdall GB Stock again,
6) Flashed Clockworkmod again,
7) Installed RemICS rom again (Step 3) & WORKING LIKE A CHARM NOW!
I suspect my initial problem was caused by internal conflicts between the Rooted ROM and ICS, yet it is not evident nor I'm experienced to make such conclusion. Anyway, glad that my Infuse is finally able to run on Ice Cream Sandwich and I really dont care about what had caused the problem prior.
Big Thanks to rkkaranrk and qkster.

Post sent to dev thread of this ROM, just hang tough, tell the storm troopers arrive....
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2

Do u have the GB boot loaders ? If not flash them......will solve ur problem.
Sent from my SGH-I997 using Tapatalk 2

rkkaranrk said:
Do u have the GB boot loaders ? If not flash them......will solve ur problem.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Gb bootloaders would not cause this problem...it only causes rainbow...I've had this happen to me countless times when I was porting Roms back when I had an infuse...I just came to the conclusion the the ics recovery is buggy and is borked easily
The fix, flash back to stock via heimdal or Odin, then get cwm recovery and flash the Rom using gingerbread instructions (double flash) (unless you flash the ics kernel...in that case one flash)
If you want detailed instructions on flashing or getting gb bootloaders (in case you have rainbow recovery) then check out my infinitum port thread (in my signature) at the bottem of the OP you will find some good instructions...I wouldn't reccomend flashing it though as it is old and doesn't have the latest fixes...but the flashing instructions are still good
Sent from my HTC PH39100 using Tapatalk 2

I had faced this same issue last night when I was trying to flash REM ics on my friends phone and it don't have the GB boot loaders I tried to flash the recovery from the OP and after flashing recvery I was not able to RAF anything the fonts were so tiny and were in pink color.
After all this I flashed it back to lb3 thanks to Scott and from there I flashed it again and this time lost recovery was not able get the phone to recovery, So finally I decided to flash the GB BL with heimdall (thanks to qkster) flashed stock one more time with BL ticked and the REM ICS, All good.
Sent from my SGH-I997 using Tapatalk 2

rkkaranrk said:
I had faced this same issue last night when I was trying to flash REM ics on my friends phone and it don't have the GB boot loaders I tried to flash the recovery from the OP and after flashing recvery I was not able to RAF anything the fonts were so tiny and were in pink color.
After all this I flashed it back to lb3 thanks to Scott and from there I flashed it again and this time lost recovery was not able get the phone to recovery, So finally I decided to flash the GB BL with heimdall (thanks to qkster) flashed stock one more time with BL ticked and the REM ICS, All good.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
The bootloaders fixed the rainbow recovery, what fixed your whole problem was that you flashed stock...so you pretty much killed two birds with one stone, you fixed your rainbows and you fixed your soft brick...
The pink recovery you referred to is known as rainbow recovery
Sent from my HTC PH39100 using Tapatalk 2

Mate u missed the part i said i flashed stock twice first time with out the BL and then with the BL, When i flashed stock without the BL and from there when i flashed REM i lost recovery so and flashed again with the BL this solved.
I had read all aver that BL does not mess with flashing only gives u messed recovery on ICS and rainbow boot but i don't know how this worked for my friends phone.
Edit: i know how rainbow recovery looks like but the fonts are still in blue color but in this case the blue fonts were pink in color and were too small if the normal size of the font say 10 then the size in this recovery was like 2/3.

rkkaranrk said:
I had faced this same issue last night when I was trying to flash REM ics on my friends phone and it don't have the GB boot loaders I tried to flash the recovery from the OP and after flashing recvery I was not able to RAF anything the fonts were so tiny and were in pink color.
After all this I flashed it back to lb3 thanks to Scott and from there I flashed it again and this time lost recovery was not able get the phone to recovery, So finally I decided to flash the GB BL with heimdall (thanks to qkster) flashed stock one more time with BL ticked and the REM ICS, All good.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yes i have flashed the original stock gingerbread (the one listed in the OP) back onto my infuse last night. The phone is working flawlessly at this moment under the stock GB.
And the ICS Rom was flashed twice everything worked, cache cleared, factory reset, no rainbow, and the only problem was recovery looping. Im considering reflashing the rem ICS rom sometime soon but i doubt I'd see any difference, any chance i can get ICS working? Thanks for all the above replies
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

There is no reason for it not to work if done properly u will boot in to a new world.
Sent from my SGH-I997 using Tapatalk 2

RemICS kernal question
I am currently using version 1.3 on my infuse. I have noticed that the past couple of days that the phone seems to be slowing down and doing soft reboots every once in awhile. I have gone through and deleted a bunch of apps and moved some to my sdcard and it has gotten faster, however I still have some slow downs and reboots, especially when coming back to the homescreen after exiting an app (It seems to take a few seconds to redraw the homescreen) or if an app locks up. I also have RemICS version 1.3.1 on my Captivate and it has a different kernel (Devil Kernel). I was wondering if there was a version of this kernel that would work with the Infuse as my Captivate seems to be rock-steady and fast. I have not overclocked or messed with the memory settings on the Infuse, but I have noticed that no matter what Rom I use on it (even stock Gingerbread loaded by ATT repair center), it seems to slow down and mess up over time. RemICS so far has seemed to last the longest and I would like to keep it going smoothly. Any suggestions would be extremely helpful. Thanks!
Chris Veverka
[email protected]

cx831 said:
Hi All, I have just flashed the RemICS ROM 1.3 and i have followed the set of directions for Gingerbread users, which I previously was. The installation had been successful until I did the final Reboot, where it loops back into the Recovery mode even after numerous of re-flash and reboots. I'm pretty sure the ROM is installed, yet it would not load into the OS, thoughts? Thanks everyone in Advance.
http://forum.xda-developers.com/showthread.php?t=1613523 I had the option C installed initially, for everyone's info.
Click to expand...
Click to collapse
yes it happens with me when i flash ics over gb and after every thing phone just struck up in blue recovery it happens coz some previous system files sometimes not completely deleted, dont worry just do following as what i do.
search and download infuse toolkit v1.10 and when u got in bootloop in cwm just flash this toolkit from cwm and follow the instructions till option full wipe or complete wipe after that it will again boot up in cwm recovery now wipe cach system and again install ur rom.

cx831 said:
Yes i have flashed the original stock gingerbread (the one listed in the OP) back onto my infuse last night. The phone is working flawlessly at this moment under the stock GB.
And the ICS Rom was flashed twice everything worked, cache cleared, factory reset, no rainbow, and the only problem was recovery looping. Im considering reflashing the rem ICS rom sometime soon but i doubt I'd see any difference, any chance i can get ICS working? Thanks for all the above replies
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
be positive, you can get ICS running in no time. follow our directions and you shouldnt come up with any complications
1. wipe data, cache, and dalvik
2. flash remICS
3. after reboot you will be stucked at samsung. pull out the battery and place it back in
4. enter recovery with 3 finger combo (vol up & down, and power). release power when samsung appears
5. flash rom again, and reboot
hopefully you should now see your phone booting up into ICS

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

rkkaranrk said:
There is no reason for it not to work if done properly u will boot in to a new world.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
babamanan said:
yes it happens with me when i flash ics over gb and after every thing phone just struck up in blue recovery it happens coz some previous system files sometimes not completely deleted, dont worry just do following as what i do.
search and download infuse toolkit v1.10 and when u got in bootloop in cwm just flash this toolkit from cwm and follow the instructions till option full wipe or complete wipe after that it will again boot up in cwm recovery now wipe cach system and again install ur rom.
Click to expand...
Click to collapse
Thanks for the tip and I have made 3 more attempts today, which all failed. I have returned to the stock rooted GB as mentioned at the initial thread each time to return to a working OS. I have recorded my last attempt of the day throughout the duration, including the method you have mentioned. I'll list what I have done in short below;
youtube.com/watch?v=RGCEkRVlHog (Unable to embed links, my apologies for any inconvenient)
1. Factory Format, Wipe Cache, Wipe Delvik Cache,
2. Flash rom from internal SD,
3. Advance > Reboot Recovery,
4. Flash again after re-enter Recovery,
5. Boot-looped as expected, thus flashed Infuse Toolkit v1.1,
6. Wipe Cache and Complete Wipe,
7. Quit and automatic reboot,
8 -Stuck at Cyanegen Mod Screen, wont enter Recovery Mod again-, no matter what i do. I tried pulling battery out and reboot into recovery, stuck anyhow.
Then I entered Odin and flashed stock GB back and my phone is working fine. Please point out any missing steps or mistakes to the installation. I suppose it's a conflict with the internal SD rather than system error, welcome to any suggestions. Again, thanks for all the replies so far. Anything is appreciated!
ps: I will give other Ice Cream Sandwich ROMs a shot this weekend, hope the above would not occur on the other roms. :/

Don't use the reboot option from recovery and did u tried downloading the ROM file again.
Sent from my SGH-I997 using Tapatalk 2

Sorry for the late update, but no luck for any other ICS roms available for infuse. All ended up the same, blue recovery bootlooped.
I'm wondering if there's any way that I can wipe all the data, including the stuff on internal SD like an ultimate factory reset with only the running ROM left so I can do a clean ICS flash? Thanks all.

cx831 said:
Sorry for the late update, but no luck for any other ICS roms available for infuse. All ended up the same, blue recovery bootlooped.
I'm wondering if there's any way that I can wipe all the data, including the stuff on internal SD like an ultimate factory reset with only the running ROM left so I can do a clean ICS flash? Thanks all.
Click to expand...
Click to collapse
It is possible that reboot recovery while in cwm got you in this recovery loop.
There may be a misc recovery img created.
You have to delete that misc with a prepare cwm-flashable script.
On the infuse, mounting usb in cwm doesn't work.
If you can get at it in adb, this command may work:
C:\> adb shell erase_image misc
You will have better luck in factory/data reset in cwm.
Put the phone in DL mode.
Odin or Heimdall back to stock with repartition and start over.
This time around, remember not to reboot into recovery while in cwm

I had the OP's exact issue when I upgraded from CM7 to remics last week. I was running froyo bootloaders and LB's CM7 (http://forum.xda-developers.com/showthread.php?t=1195525) with whatever kernel came with that (it had blue CWM).
I followed the instructions for "coming from Gingerbread" in the original remics thread (before it was updated this week) and I ran into OP's *exact* problem with looping back into recovery. I got on the #infuse4g IRC and got help from Aerema(sp?) and entropy. I learned some new things and tried everything they suggested (a lot of which I'm reading in this thread)... but none worked for me.
To get to the point, in the end... and I know this doesn't seem to make sense, but what worked for me was using Odin to "return to stock", then flashing the kernel from the remics package and flashing remics.
I had been using qkster's Heimdall OneClick return-to-stock (http://forum.xda-developers.com/showthread.php?t=1524081). Heimdall always worked and didn't report any problems. I even used heimdall command line interface when I upgraded from froyo to gb bootloaders.
To this day, I don't understand why using Odin return-to-stock (http://forum.xda-developers.com/showthread.php?t=1705260) got me out of the recovery loop.
I *think* my upgrade path went like this.
Starting with CM7Kang/froyo BL
1) download remics1.3.zip, followed instructions exactly & flashed remics1.3.zip from blue CWM.
2) rebooted, ROM worked just fine but had rainbow recovery.
3) attempted qkster's heimdall OneClick GB BL upgrade (update bootloader checkbox). It failed.
4) updated to GB bootloader using heimdall command line (http://forum.xda-developers.com/showpost.php?p=24901128&postcount=3)
5) ** recovery loop ** seemingly tried everything from double-flashing kernel-only using heimdall command line to reverting back to stock (heimdall), format /system, Infuse Toolkit, etc and so on.
6) used ODIN return-to-stock and from there the upgrade went perfectly.
I, too, would like to express my gratitude to bradman117 and everyone else involved in making this ROM available to the general public. I'm really liking it. Nice to have ICS on a > 1 yr old device. Thanks to those who still visit the #infuse4g IRC chan as well.
TL;DR - I had to use the Odin return-to-stock to fix recovery looping, even though Heimdall return-to-stock appeared to be doing everything correctly.

Problem Solved.
qkster said:
It is possible that reboot recovery while in cwm got you in this recovery loop.
There may be a misc recovery img created.
You have to delete that misc with a prepare cwm-flashable script.
On the infuse, mounting usb in cwm doesn't work.
If you can get at it in adb, this command may work:
C:\> adb shell erase_image misc
You will have better luck in factory/data reset in cwm.
Put the phone in DL mode.
Odin or Heimdall back to stock with repartition and start over.
This time around, remember not to reboot into recovery while in cwm
Click to expand...
Click to collapse
Finally got my ICS working now. Can't thank you enough for qkster Heimdall One Click Gingerbread ROM:good::good::good:.
For everyone's reference, the following is what I've done;
1) Flashed the Heimdall One Click GB Stock rom, a big thanks to qkster,
2) Flashed the CWM Recovery just under the same thread,
3) Flashed the RemICS rom with factory wipe and formatting data, system and cache, again after reboot.
4) >Bootlooped at the SAMSUNG screen,
5) Followed the solution of bootlooping under the RemICS thread and flashed Heimdall GB Stock again,
6) Flashed Clockworkmod again,
7) Installed RemICS rom again (Step 3) & WORKING LIKE A CHARM NOW!
I suspect my initial problem was caused by internal conflicts between the Rooted ROM and ICS, yet it is not evident nor I'm experienced to make such conclusion. Anyway, glad that my Infuse is finally able to run on Ice Cream Sandwich and I really dont care about what had caused the problem prior.
Big Thanks to rkkaranrk and qkster. :laugh:

Help going to JB

Ok I have completed the following process to flash my Infuse 4G to GingerBread
http://forum.xda-developers.com/showthread.php?t=1613523
I used Option C
I would like to get to JB and would like to know what I have to do next to accomplish this.
Thanks for your help.

This has been explained in many threads already, but you have already asked so lets go.
Before we start, do you have Gingerbread bootloaders installed? If you don't, your recovery will be rainbow distorted once on ics or jb. Some people can live with it, some not.
You need blue recovery to flash JB. You can get this in two ways:
a) flash any ics rom following the double flash instructions since you are coming from GB.
b) use the ics one-click recovery linked in cm10 OP
Once on blue recovery, follow the directions of whatever JB rom you want to flash. These will indicate you to wipe data, cache & dalvik and format /system and the flash the Rom.
Sent from my sweet & buttery Infuse

help pls! can i flash clockworkmod recovery files with odin??

ok so long story short i tried to flash my samsung infuse 4g with a rom from this website (ROM][Jellybean] CNA 3.5.0 for Samsung Infuse [PORT] ) i used to have froyo 2.2. all was well and then my phone just stopped working and wouldnt pass boot screen. but i saved my old rom's data with clockworkmod on my sd card. the thing is there are like 5 .tar files and i want to know if i can recover my old rom using odin since i cant even get passed the boot screen??? pls someone help me i'm freaking out, ive been googleing all night and i'm totally burnt out. the files i have are .android_secure.vfat.tar, cache.rfs.tar, data.rfs.tar, efs.rfs.tar, nandroid.md5 and system.rfs.tar...... pls someone show me how to fix my phone
thanks in advance

Don't think you can flash those files, but you should be able to go back to stock.
Sent from my sweet & buttery Infuse

Follow these instructions. I would use the zip that takes you back to stock with root.
Keep one thing in mind.....you CANNOT go from Froyo to JB.
http://forum.xda-developers.com/showthread.php?p=27286083#post27286083
I keep this thread bookmarked. I have soft bricked my phone so many times, it's not funny!!!
http://forum.xda-developers.com/showthread.php?t=1700416

Lack of reading/research caused your error :/
Anyways go back to stock with heimdall.or Odin, get red cwm again and you should be able to restore your backups
If you want to go to jb in the future....then you must first follow go to ics, then jb...you have to have ics before you can flash gb
Sent from my HTC PH39100 using Tapatalk 2

thanks again to all the comments, yes this was a big Noob mistake, i guess i was just way to excited to jump on the JB wagon. i have since returned to stock froyo using one of the kernals from this site (Stock_Root-Mod3e-UCKD5_Odin), so this is what i have now... although a little phased i still want to give this a second attemp. the rom i wanted to flash was [ROM][JellyBean] CNA 3.5.0 / Nightly 9/20 for Samsung Infuse [PORT]....
just to get things straight so i don't mess up again, i have to flash froyo with ics (is there a specific ics version i should get? on a how to guide on flashing jb i found this info: Entropy512's CM9 Kernel / Blue CWM Recovery 2012.05.02-ODIN-Entropy-CM9-zImage.rar) can i use this one, i prefer odin b/c i've never used heimdall. then after i flash ics then i can flash to jb.... but reading some threads i saw that....
"Currently on stock Froyo:
1) Use Heimdall or Odin to flash stock UCLB3 (GB)
*Reccomendation: Also flash GB bootloaders. See first post for links and warnings.*
2) Flash Entropy's DD kernel to obtain root and red CWM recovery.
Currently on stock GB:
1) Flash Entropy's DD kernel to obtain root and red CWM recovery."
do i have to do this step or can i go forward with the current Stock_Root-Mod3e-UCKD5_Odin that i now have installed....?
secondly, after i install ics, right before i flash jb it states i have to do an aroma prep....then flash jb.....
all flashes are done with clockworkmod and i wipe only cache and dalvik? or is there anything else i have to wipe?
sorry for all the questions, i have read and researched many threads but they are all pretty overwhelmingly full of lots of info.....just wanna get it in order....
thanks again
from froyo to ics i use odin, from odin to jb i use cwm, correct?

marielacvn said:
thanks again to all the comments, yes this was a big Noob mistake, i guess i was just way to excited to jump on the JB wagon. i have since returned to stock froyo using one of the kernals from this site (Stock_Root-Mod3e-UCKD5_Odin), so this is what i have now... although a little phased i still want to give this a second attemp. the rom i wanted to flash was [ROM][JellyBean] CNA 3.5.0 / Nightly 9/20 for Samsung Infuse [PORT]....
just to get things straight so i don't mess up again, i have to flash froyo with ics (is there a specific ics version i should get? on a how to guide on flashing jb i found this info: Entropy512's CM9 Kernel / Blue CWM Recovery 2012.05.02-ODIN-Entropy-CM9-zImage.rar) can i use this one, i prefer odin b/c i've never used heimdall. then after i flash ics then i can flash to jb.... but reading some threads i saw that....
"Currently on stock Froyo:
1) Use Heimdall or Odin to flash stock UCLB3 (GB)
*Reccomendation: Also flash GB bootloaders. See first post for links and warnings.*
2) Flash Entropy's DD kernel to obtain root and red CWM recovery.
Currently on stock GB:
1) Flash Entropy's DD kernel to obtain root and red CWM recovery."
do i have to do this step or can i go forward with the current Stock_Root-Mod3e-UCKD5_Odin that i now have installed....?
secondly, after i install ics, right before i flash jb it states i have to do an aroma prep....then flash jb.....
all flashes are done with clockworkmod and i wipe only cache and dalvik? or is there anything else i have to wipe?
sorry for all the questions, i have read and researched many threads but they are all pretty overwhelmingly full of lots of info.....just wanna get it in order....
thanks again
from froyo to ics i use odin, from odin to jb i use cwm, correct?
Click to expand...
Click to collapse
Follow all steps, don't skip a thing. As for wiping, wipe Cache, Data, Dalvik, and format /System when going from GB to ICS and ICS to JB. That UCLB3 file is Gingerbread stock and you have to go to gingerbread before you go to ICS.
Also, if you are confident that your phone won't get disconnected from Odin while flashing the UCLB3 file, flash the GB bootloaders while you're at it. If the flash fails while flashing bootloaders then your device is bricked so be sure about Odin before you flash them.
Sent from my SGH-I997 using xda app-developers app

Since you have already used Odin, I would use option "C". The best thing you can do is read everything two or three times. There are also many vids on YouTube that are helpful.
Once you are on GB.....just pick out any ICS ROM an flash it. Once it installs, I wouldn't even bother sitting it up and then you can go to JB.
Th3Bill uses an Aroma installer in his ROMs and the first time you use it, you will have to flash his aroma-prep first.
Hang in there....go slowly...and read. This gets easier and easier the more you do it. I always just d/l the zips to my phone and never even have to mess with the PC.
http://forum.xda-developers.com/showthread.php?t=1613523
Edit: All of his ROMs for the Infuse can be found and d/l at Jokersax.com
Edit: I just reread your post......once you are on GB, you won't use Odin again. You will use whatever ICS zip to flash your ROM using CWM. Same thing with JB.

Shawn said:
Follow all steps, don't skip a thing. As for wiping, wipe Cache, Data, Dalvik, and format /System when going from GB to ICS and ICS to JB. That UCLB3 file is Gingerbread stock and you have to go to gingerbread before you go to ICS.
Also, if you are confident that your phone won't get disconnected from Odin while flashing the UCLB3 file, flash the GB bootloaders while you're at it. If the flash fails while flashing bootloaders then your device is bricked so be sure about Odin before you flash them.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
okay i think i understand....never has my phone disconnected during a flash with odin, ive always gotten a straight pass...exactly how important are the bootloaders anyways? if failures happen b/c of faulty usb cords, then im good...if bricking happens b/c of "unlucky chance" then id rather avoid it.... either way ill start the whole process tonight after i put the kiddos away so i can concentrate 100%.
thanks again for the tips

dparrothead1 said:
Since you have already used Odin, I would use option "C". The best thing you can do is read everything two or three times. There are also many vids on YouTube that are helpful.
Once you are on GB.....just pick out any ICS ROM an flash it. Once it installs, I wouldn't even bother sitting it up and then you can go to JB.
Th3Bill uses an Aroma installer in his ROMs and the first time you use it, you will have to flash his aroma-prep first.
Hang in there....go slowly...and read. This gets easier and easier the more you do it. I always just d/l the zips to my phone and never even have to mess with the PC.
http://forum.xda-developers.com/showthread.php?t=1613523
Edit: All of his ROMs for the Infuse can be found and d/l at Jokersax.com
Edit: I just reread your post......once you are on GB, you won't use Odin again. You will use whatever ICS zip to flash your ROM using CWM. Same thing with JB.
Click to expand...
Click to collapse
okay, ill take ur advice and use option c. froyo to gb using odin and possibly bootloaders, then from gb to ics, ics to jb using cwm
wish me luck!

Bootloaders prevent Rainbow fault I guess you could call it in ICS. You don't have to flash them but its recommended. If you have any problems, post and you'll get help pretty quick.
Sent from my SGH-I997 using xda app-developers app

Shawn said:
Bootloaders prevent Rainbow fault I guess you could call it in ICS. You don't have to flash them but its recommended. If you have any problems, post and you'll get help pretty quick.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
so far so good, it seems i need to do the gb bootloader after all...got the rainbow screen....i have my gbbootloader file ready to go....only thing is i want to confirm where i put the file, i've searched and i can only find a procedure for heimdall not odin...do i put the md5 file in PDA or bootloaders?? also it says in heimdall to tick bootloaders, do i do the same in odin??? it also says to flash twice....?? ok im really not risking a hard brick, i'll be patient and wait
http://forum.xda-developers.com/showthread.php?t=1878458
i'll wait for your answer before i proceed....after this i'll continue to flash ics and then jb...
btw, am i supposed to flash ics twice?? that's what the [GUIDE] How To Flash JB says,
"9. Flash ICS Rom, then ICS Gapps"
but when i tried to flash ics a second time i couldn't (because of rainbow screen, and because it didn't show up in my directory....and where does ICS Gapps show up?
thanks again

If you downloaded the bootloaders linked in the guide, then yes, they go on the pda slot. You only have to flash once.
Heimdall-one click is the one you must flash once before it allows you to flash the bootloaders too.
Edit: to fully install ics you must flash twice, because I believe that what it does when coming from GB is that it just flashes the ics kernel on the first flash, requiring you to run it a second time after rebooting for it to install the complete rom.
Ics gapps are often linked in the rom OPs, although you don't need to flash them if you are headed to JB.
Sent from my sweet & buttery Infuse

andros11 said:
If you downloaded the bootloaders linked in the guide, then yes, they go on the pda slot. You only have to flash once.
Heimdall-one click is the one you must flash once before it allows you to flash the bootloaders too.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
That's odd, I flashed GB bootloaders in Odin from a rooted stock GB. But andros is right about going in the PDA slot. Maybe its just me that didn't have to flash with heimdall first.
Sent from my JellyBeaned Infuse, unofficial cm10

Shawn what I meant is that heimdall one-click wont allow you to flash bootloaders the 1st time, so you must run it once and then a 2nd time but with "flash bootloaders" ticked on.
There's no need to use heimdall before flashing them with Odin.
Sent from my sweet & buttery Infuse

Oh, I see what you mean. My mistake.
Sent from my JellyBeaned Infuse, unofficial cm10

Alright guys, I'm officially a jelly beaner!! Thanks again to all who replied and helped me out, couldn't have done it without your help everything seems to we working fine (with the exception of a few apps that aren't compatible, but they weren't that important ) only issue I have now is that I can't use my data plan and surf the web I configured everything just as I had it before according to my carrier and nothing ...... could it have something to do with the change in modem? When I scan for available network operators I get two options one says :NICMS and the other is just a number 71021... any ideas?
Also, when installing jb in the initial setup it asked which would be the defualt location to save I think I chose the sdcard instead of the emmc directory. ..can I change that setting?

I'm pretty sure you can change the setting, but not sure how. Also, your APNs might be messed up. There's a thread with working APNs. One sec and I'll link it.
Edit: http://forum.xda-developers.com/showthread.php?t=1791526
Sent from my JellyBeaned Infuse, unofficial cm10

Shawn said:
I'm pretty sure you can change the setting, but not sure how. Also, your APNs might be messed up. There's a thread with working APNs. One sec and I'll link it.
Edit: http://forum.xda-developers.com/showthread.php?t=1791526
Sent from my JellyBeaned Infuse, unofficial cm10
Click to expand...
Click to collapse
Thanks for the link Shawn, I looked it over, not sure it could apply since I don't live in the states.. but I'll use it as a start.

marielacvn said:
Thanks for the link Shawn, I looked it over, not sure it could apply since I don't live in the states.. but I'll use it as a start.
Click to expand...
Click to collapse
It probably won't but you never know.

how is [ROM][JellyBean][4.1.1]Unofficial CM10 - Updated CM10 9/14 Butter - MTD - OC Kernel working out? since ive gotten cna nightly my camera and video are extremly buggy, more than id like...what works and doesnt work in unofficial cm10

[Q] Recovery boot loop

I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)

Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app

t1op said:
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Click to expand...
Click to collapse
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!

WayTooGosu said:
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
Click to expand...
Click to collapse
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.

lumin30 said:
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
Click to expand...
Click to collapse
Ah I see. But my point was that some ROMs state that the user must be on an ICS ROM/Kernel to flash this. I guess I wasn't very clear as I am new here and lack understanding.

champ1919 said:
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I used Odin to return to stock. I used Super One Click to root. I used root explorer modify the recovery to allow me to boot into "CWM final for Froyo". That much each and every time.
The first time I installed
[TFQ - 30/12/2012]X.A.O.K[Kanged - Xperia Style]
That is an ICS rom. Installed fine with a new CWM.
The second time I installed the same.
The third time I installed
ROM-MTD-TWRP-ICS-4.x-Audiophile
That is another ICS rom. Installed fine with TWRP.
Each and every time, when returning to recovery to flash more, I got stuck. I can't boot to anything except recovery.
My brother suggested that the problem is using the Volume up and down and power button ("three finger salute") to return to recovery instead of from OS power down menu.
For a fourth time I started over again. Now, using the reboot>recovery, everything works fine.

One thing, you need to have ginger bread bootloaders. So, when you say Odin back to stock, are you referring to kj6?
You could cut down some of the work by using Odin to flash a kernel with recovery & root in it. Antonx & drhonk both have kernels that will do that with odin.
I flash bhundven's cm9 Rom before jumping to any of the others(and wipe between). I believe some of the Rom authors have that in their instructions.
Sent from my SGH-T959V using xda app-developers app

Yeah... GB bootloaders, not Froyo. Your return to stock should be a return to GB stock, not Froyo... and your return to stock can be a return to a rooted stock. If you want to make your life less painful.
It's about MTD to BML, not really about the base version. You just don't want to wipe out what allows later stuff to actually work properly...

Thanks for the advice. I haven't used custom roms very much. Trying to figure out which ones to choose was difficult. I started on stock Gingerbread, but everything I encountered in searching indicated that I needed to go back to Froyo to get CWM then go from there. ...Perhaps I kept running into very old instructions? In any case, should I need to go back to stock again some day, I'll try to figure out which GB roms I could use, including root and custom recovery.
I guess the solution to my problem is: 1) flash back to Froyo or Gingerbread; 2) after flashing an ICS+ rom, only go to recovery from OS reboot menu (never "three finger salute").
I'm actually surprised that people don't run into this problem more often, enough to create a sticky about it. I'm sure I'd still be pulling my hair out if my brother hadn't run into the problem on his Fascinate a year ago.

On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.

Theraze said:
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Click to expand...
Click to collapse
Interesting... Perhaps if I went back to a gingerbread stock then upgraded to ICS the problem wouldn't occur?
I'll have to try that the next time I might need to return to stock.

Hello,
First I just want to say thank you to the mods for running a great forum and to the devs for keeping this device current.
I just struggled over a period of days with this issue.
The end result being, that you need to go to CM9 BEFORE you try JellyBean or later!
Just hope this helps someone else who missed that instruction.
Thanks devs/mods/everyone for keeping this device alive!!!! :good::good::good:
*EDIT* correction... i THINK you need to go CM9 Before trying something else

Not all ICS ROMs require CM9, but you must have at least CWM5 recovery to be able to flash CM9 or these ROMs. Follow ROMs' OP instructions.
I personally tested HebMIUI flash over Stock GB with CWM5 (Basic with a twist kernel) without going through CM9.