ics recovery hard to read, gb bootloaders installed - Samsung Infuse 4G

I am still having trouble with the rainbow effect - hard to read recovery in ics. I have already flashed a couple of the fixes in odin, and installed stock GB got red recovery and re install ics. no help -recovery has only gotten harder to read. any suggestions?

U need to flash the boot loader, Flashing stock GB does not flash the boot loaders as they are removed from the stock packages to avoid hard bricks as flashing BL is always risky + once u flashed them u dont need to flash them again.
Search threads by jscott for Odin and heimdall by qkster.
Sent from my SGH-I997 using Tapatalk 2

I had flashed stock gb thru odin as well as trying the gb bootloader package and ics recovery fix with odin. None of it worked. following all directions. However I did just try another gb bootloader package with odin on PDA tab and this time checked the bootloaders box in odin. This worked very quickly. auto rebooted and saw that the boot animation now had a new pic. did not need to reflash rom. recovery is blue. thanks.
some one should update guide to show checking on bootloader in odin.

Related

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:

Need Help Fixing Someone's Cappy

Ok so yesterday I received a cappy from someone on here that I told them I would try and fix. I am not charging them anything and am actually paying shipping back to them. When I received it and turned it on it was stuck at the end of the cornkernel bootlogo. I thought hey this will be easy and flashed the heimdall version of I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click. Phone rebooted and is now stuck at the att logo. So I flash cornkernel, its stuck at the end of cornkernel bootup. So I decided on a whim to try and flash this kernel Devil3_1.1.3_HB_cappy_CFS_BLN_VC_20120807, luckily that got me into recovery, so I did a full backup of all the stuff on his internal storage and completely wiped the phone, wipe data/factory reset, wipe dalvik cache, format boot, format system, format sdcard, format cache, format data, format datadata (yes I know I wiped some things twice) . Then I flashed my rom, it just reboots to recovery after the flash, still reboots after a reflash of the rom. I then wiped everything again and tried flashing CM9's latest nightly to see if I could get it to boot up. Still reboots to recovery. So far all together I have flashed I897UCJI6-OCD-REV02-Low-designgears, i897uckk4 Odin One Click CONTAINS Bootloaders, Re-partition, Full Wipe, I897UCKF1_withBL,SGH-I897_I897UCKJ3, KK4-SE-One-Click, JF6 With Bootloaders, SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click Followed By I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click both are heimdall. All of those either left it stuck at att or kernel screen after I flashed a kernel. Anyone got any ideas? I am almost to my wits end.
Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium
4-2ndtwin said:
Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Already have that is my go to file actually and I tried that before going the heimdall route. Thanks Anyways.
You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium
-SGA- said:
You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Thanks for the idea. It didn't work tho. I am still at the same spot, phone keeps rebooting to recovery.
have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd
stayintwisted said:
have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd
Click to expand...
Click to collapse
Not that I know of, It isn't my phone so I do not know the history other than him saying it didn't boot past the kernel screen and receiving it and seeing that and then what I have done. Normally the sd card data from what I have seen is wiped when the eu bug happens from what I have read, maybe I am wrong, but since I backed up his data off the sdcard that is why I do not believe it has had the eu bug.
Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.
cbalt said:
Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.
Click to expand...
Click to collapse
Long story short, recovery is iffy at best for me. I went through something similar to this when trying to go from CM10 back to CM9 for the first time. Ever since then recovery has not been right.
What I did was
Install a stock one-click with bootloaders, used odin to flash speedmod kernel and then used that recovery to flash CM9 in three successions wiping everything each time. Somehow it took, and now I am no longer a crack flasher because I have the same kernel splash screen problem every time.
So,
Use this http://www.mediafire.com/?5rcofbzusoor6mv
PDA button in Odin3 1.7: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Boot into recovery.
Flash your ROM
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Try to boot normally.
Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.
There is a place that has rogers stock roms
cbalt said:
Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.
Click to expand...
Click to collapse
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way
sunfirestorm said:
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way
Click to expand...
Click to collapse
I have already tried all three of the Rogers One Clicks with none of them actually doing anything more than the Captivate One Clicks, It still doesn't boot past the first screen. Thanks for the input though.
You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work
fohdeesha said:
You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work
Click to expand...
Click to collapse
I'm going to do your steps again which is more or less what I have already done. I am waiting to hear back from the person so I can ship him the phone back and he can send it to MTV or someone or just junk it, its his phone and his choice. At this point I would say it needs Jtag or Unbrickable mod + repair. Although I am still trying ideas of mine and anyone elses lol.
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery
Well if the one clicks are successfully writing primary and secondary bootloaders and it's still not working, a jtag isn't going to do anything else. It almost sounds like the memory has a few corrupt blocks, but I can't say until you flash 2.3.5 BL's and see what happens
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
cbalt said:
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery
Click to expand...
Click to collapse
Oh jeez looks like the memory is failing then

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] I have a Tab that was partially restored from the ICS flashing brick. Advice?

I have a GT-P6210 from Canada (No IR) and back when it was Honeycomb I had no problems with it.
When the ICS rom appeared I installed it and it worked for a while. However, I accidentally wiped from the stock recovery, which we now all know causes a brick. At the time, CWM was only a temporary recovery and it wouldn't accept my HC backups (different partitions?) so I went crazy trying to fix it.
I tried:
To flash ICS again. It didn't really work out for me.
To flash CM9. It got stuck at the CM9 bootlogo.
To flash a patched .pit and ICS.
I was able to flash a patched .pit but I couldn't complete the ICS flashing. It booted... to a screen saying that the "encryption" failed. I sent the tab to my uncle and he was able to flash ICS. This restored the tablet to a mostly working condition
However, because of the patched .pit I flashed earlier, it only has ~800MB of internal storage.
Now, I was thinking about my next step. Should I try to reflash the original .pit and Honeycomb then hope that I get lucky while wiping with stock HC recovery? Should I try to flash JB? Should I use the original .pit and flash JB? Should I just try to live with the fact that I'll be stuck with this problem until I get a new tablet in a few years? Please advice.
EDIT: If I use Mobile ODIN to flash, say, HC from ICS, will that work?
EDIT 2: When I flashed a patched .pit I didn't use emmc_find_brick_start.zip and emmc_find_brick_end.zip and I just randomly went with a patched .pit for the device.
EDIT 3: Say if I flash PA in the tab's current state, will it crash and go boom or I'll have a ~800MB PA experience?
gio32999 said:
I have a GT-P6210 from Canada (No IR) and back when it was Honeycomb I had no problems with it.
When the ICS rom appeared I installed it and it worked for a while. However, I accidentally wiped from the stock recovery, which we now all know causes a brick. At the time, CWM was only a temporary recovery and it wouldn't accept my HC backups (different partitions?) so I went crazy trying to fix it.
I tried:
To flash ICS again. It didn't really work out for me.
To flash CM9. It got stuck at the CM9 bootlogo.
To flash a patched .pit and ICS.
I was able to flash a patched .pit but I couldn't complete the ICS flashing. It booted... to a screen saying that the "encryption" failed. I sent the tab to my uncle and he was able to flash ICS. This restored the tablet to a mostly working condition
However, because of the patched .pit I flashed earlier, it only has ~800MB of internal storage.
Now, I was thinking about my next step. Should I try to reflash the original .pit and Honeycomb then hope that I get lucky while wiping with stock HC recovery? Should I try to flash JB? Should I use the original .pit and flash JB? Should I just try to live with the fact that I'll be stuck with this problem until I get a new tablet in a few years? Please advice.
EDIT: If I use Mobile ODIN to flash, say, HC from ICS, will that work?
EDIT 2: When I flashed a patched .pit I didn't use emmc_find_brick_start.zip and emmc_find_brick_end.zip and I just randomly went with a patched .pit for the device.
EDIT 3: Say if I flash PA in the tab's current state, will it crash and go boom or I'll have a ~800MB PA experience?
Click to expand...
Click to collapse
i experienced this with my tab,What I did was going back to stock HC and do full wipe, then flash ics using heimdall not odin then flash jb using odin..
Sent from my GT-P6200 using xda app-developers app

[Q] this phone does not run any rom stock or custom.....stuck

guys this is 4th day :angel:and i m trying to fix sgs4g t959v.......i downloaded a lot of roms but no one will go beyond boot screen except froyo kd1.....but in froyo after successfull boot it freezes very quickly and reboots...........i m very annoyed now and want someone to share his expertise......thank you in advance:good:
yes it always go into download mode easily and sometimes into recovery but freezes very soon...............
Hi
1. Please update your thread topic, no one will help an empty topicless [Q].
2. Go here and follow instructions. This will bring you to Gingerbread (with GB bootloaders) and from there it will be very easy to upgrade.
3. Once you have a rooted GB ROM with CWM recovery 3 and above, you will be able to flash an MTD ICS ROM such as CM9/MIUI/Ultragen and then JB...
already tried that
itzik2sh said:
Hi
1. Please update your thread topic, no one will help an empty topicless [Q].
2. Go here and follow instructions. This will bring you to Gingerbread (with GB bootloaders) and from there it will be very easy to upgrade.
3. Once you have a rooted GB ROM with CWM recovery 3 and above, you will be able to flash an MTD ICS ROM such as CM9/MIUI/Ultragen and then JB...
Click to expand...
Click to collapse
bro i already tried that......upgraded with kies mini and kies said upgrade is successful but it did not go beyond boot screen
If you used kies mini you did not try that at all.
uninstall all Samsung drivers and actually try that.
itzik2sh said:
If you used kies mini you did not try that at all.
uninstall all Samsung drivers and actually try that.
Click to expand...
Click to collapse
the link you provided said first upgrade from stock froyo to stoc gb, then onwards....i did so......everything went fine but didnt boot
I think if you have the kies drivers installed you should try using gremlin remover.
dervash said:
the link you provided said first upgrade from stock froyo to stoc gb, then onwards....i did so......everything went fine but didnt boot
Click to expand...
Click to collapse
No. You need to read better. The link I sent allows you to upgrade to GB without kies and then further on. Now what you can do is uninstall kies and any other Samsung driver from PC, switch USB port and use heimdall to flash to rooted GB. From there zip flash ICS and then JB...
If you say you don't have boot you probably don't have bootloaders. Please follow instructions and read them well.
sent from me
Did you do the factory reset between?
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
champ1919 said:
Did you do the factory reset between?
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
Click to expand...
Click to collapse
nothing comes beyond boot screen.......how can i do a factory reset.....the one stock rom kd1 i m able to boot but it freezez after seconds.......let me try
i managed to do a factory reset but to no avail
You might be getting confused. Please go back to the link provided by itzik2sh and study the guide on using Heimdall. It's fairly lengthy but completely accurate. It will show you how to use Heimdall to get to stock GB, how to use Heimdall to root your phone by flashing AntonX's kernel, how to flash the necessary bootloaders, and even how to get your device into download mode. It's pretty much foolproof...and it works...please do your homework...we will be grading you.
DickyG said:
You might be getting confused. Please go back to the link provided by itzik2sh and study the guide on using Heimdall. It's fairly lengthy but completely accurate. It will show you how to use Heimdall to get to stock GB, how to use Heimdall to root your phone by flashing AntonX's kernel, how to flash the necessary bootloaders, and even how to get your device into download mode. It's pretty much foolproof...and it works...please do your homework...we will be grading you.
Click to expand...
Click to collapse
bro i did all heimdall one clicks...stock kj6, stock+root, stock kf1..,,but nothing happened........the only thing worked is i downloaded this starter pack http://forum.xda-developers.com/showthread.php?t=1223765 and installed both but nothing happened...then again i flashed first which is kc1 with pit file then i flashed stock froyo rom downloaded from sammobile.....it boots up but suddenly freezes after 20 or so seconds......i erased to factory but the result was same.......then i flashed bali 3.03 kernel and booted to cwm recovery and tried to flash icbinb.....as required i flashed ext4 converter then immediately as i try to flash icbinb....recovery freezes randomly.....and i m unable to complete process.......may be it has some hardware issue
One final thought...looks like you've tried kies, Odin, & Heimdall. There is the possibility that you might have some conflicting drivers wandering around your computer. Why don't you try another computer (if one's available). Run Heimdall...be sure to follow the instructions on verifying your Java version and Microsoft Visual C. If you are successful, be sure and flash the bootloaders and then the basic-with-a-twist kernel.
Hope this works...I'm out of ideas.
i did so.....but no difference......i think it has some hardware problem.....because even if i m in recovery....it freezes after some tine....be it stock recovery or cwm......also i mentioned earlier that only rom which i was able to boot was stock froyo.....but it also freezes after a couple of minutes. and if i dont turn off during it is frozen it becomes very hot and gives over heat signal at next restart..................so assuming it had a hardware problem i returned back the device

Categories

Resources