Stuck in Blue Recovery 5.5.0.4 - Samsung Infuse 4G

My infuse has been coming back to blue recovery ever since i decided to update to the newest version of stock ICS. I have been searching for hours to not find any solution. I installed a ICS kernel that can be used with Heimdall but that still didnt work. I've used Odin a couple of times but everytime i get a ICS rom it keeps staying in a recovery loop. i am out of ideas and i really need help!

jayxvino said:
My infuse has been coming back to blue recovery ever since i decided to update to the newest version of stock ICS. I have been searching for hours to not find any solution. I installed a ICS kernel that can be used with Heimdall but that still didnt work. I've used Odin a couple of times but everytime i get a ICS rom it keeps staying in a recovery loop. i am out of ideas and i really need help!
Click to expand...
Click to collapse
in recovery go to mounts nd storage and format system and cache then do the normal wipe data and dalvik cache then flash rom nd whatever else after it done nd ready go to advanced and fix permissons and then go to mounts and storage and if it isnt already mounted then mount system......hope this helps

Yeah...after going to stock, instead of flashing the kernel try the, double flash method...not sure if it will make a difference but its worth a try
Sent from my HTC PH39100 using Tapatalk 2

just check
forum.xda-developers.com/showthread.php?t=1783899

Related

[Q] Stuck on splash screen

ok i have another inspire and everything rooted fine flashed eva miui awhile back and havnt touched it sense. so yesterday i decided to update it to a working ICS build and i cant seen to get any of them to work. i have tried the recovery included with the ace kit and the 4ext touch recovery and talons recovery. all of them make it to the flashy boot screen and just sits there. i let it sit for almost an hour so obviously i did something wrong. now i cant flash any new rom. luckily i made a nandroid before doing all this so im still able to use eva miui but i cant flash a new rom. what am i doing wrong???
yes i wiped 3 times, factory, data, cache, dalvik
tried flashing rom twice before reboot to test.
switched to the 4ext recovery to convert everything to 4ext but still nothing.
all these roms say they have the kernel included so im guessing i shouldnt have to flash a different kernel
nevermind got the collective ics rom to flash. just not the aospX rom.
tsdeaton said:
ok i have another inspire and everything rooted fine flashed eva miui awhile back and havnt touched it sense. so yesterday i decided to update it to a working ICS build and i cant seen to get any of them to work. i have tried the recovery included with the ace kit and the 4ext touch recovery and talons recovery. all of them make it to the flashy boot screen and just sits there. i let it sit for almost an hour so obviously i did something wrong. now i cant flash any new rom. luckily i made a nandroid before doing all this so im still able to use eva miui but i cant flash a new rom. what am i doing wrong???
yes i wiped 3 times, factory, data, cache, dalvik
tried flashing rom twice before reboot to test.
switched to the 4ext recovery to convert everything to 4ext but still nothing.
all these roms say they have the kernel included so im guessing i shouldnt have to flash a different kernel
Click to expand...
Click to collapse
Deleted...didn´t see the second post
Sounds like a bad flash. Mine did that the one time I didn't verify md5 sum.
Zombies ate my Inspire
tsdeaton said:
ok i have another inspire and everything rooted fine flashed eva miui awhile back and havnt touched it sense. so yesterday i decided to update it to a working ICS build and i cant seen to get any of them to work. i have tried the recovery included with the ace kit and the 4ext touch recovery and talons recovery. all of them make it to the flashy boot screen and just sits there. i let it sit for almost an hour so obviously i did something wrong. now i cant flash any new rom. luckily i made a nandroid before doing all this so im still able to use eva miui but i cant flash a new rom. what am i doing wrong???
yes i wiped 3 times, factory, data, cache, dalvik
tried flashing rom twice before reboot to test.
switched to the 4ext recovery to convert everything to 4ext but still nothing.
all these roms say they have the kernel included so im guessing i shouldnt have to flash a different kernel
Click to expand...
Click to collapse
I'd get the same problem once, i flashed official rom, and then i used AAHK and everything was fine, hope it will helps.

Need serious help immediately

I tried to flash a aokp rom and before flashing made a back up. Now when I flashed the rom and rebooted the phone im stuck at samsung boot. I can get into recovery. At first it was a messed up recovery i tried to get to an old rom and reinstalled inimitable on reboot still stuck at samsung but can get into red recovery. Backup when reinstalling says cant mount system/! please help me asap I cant do anything I need my phone I am in panic mode.
Have tried reflashing The ROM again...or if you just want to go back to stock see my signature for links to the one click method
...btw your in the wrong section to post this...
The OP for aokp does state to flash twice...did you?...first time with wipes, then you can pull battery ...go back to cwm and reflash...again.
going back to stock is your way. clear all that crap out
http://forum.xda-developers.com/showthread.php?t=1524081
Post one to stock.....
Post two to put cwm back on....
Read with detail...the thread I provided....
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
soulysephiroth said:
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
Click to expand...
Click to collapse
We have no ics boot loaders...froyo boot loaders make the recovery look funky...gingerbread boot loaders fix that problem and can be used with froyo, gingerbread and ics ...not trying to be rude or a jerk just informing you
Sent from my SGH-I997 using XDA
Actually the "messed up" or rainbow recovery is from the lack of gingerbread boot loaders, just figured this out this morning when I attempted to flash aokp uniporn. Once I did the heimdall one click with bootloaders checked (gingerbread boot loaders) I was able to successfully flash the aokp rom and recovery works perfectly. Its really better not to reply when one does not know what they are talking about oh and I was still able to reflash a gingerbread rom as well although I probably won't go back to gingerbread again since aokp is the **** and runs super smooth
Sent from my SGH-I997 using xda premium
Please move this thread from the Development Section.
edit- Thanks for moving it.
Sorry about posting so quickly in wrong section. I just know the guys who post in here are pros. I used heimdall and everything is back to stock, no superuser. Should that be right, am I now not rooted? I havent tried to boot into recovery, but I think I have it still. Can I just follow root methods if I want to go back to root? Thanks again.
I my experiences, I've noticed our phones use a form of "Cumulative" Upgrade system, where You have to essentially go from Froyo to GB to ICS or things go haywire when you actually start using your ICS Rom..
I've tried using Heimdall to flash back to stock, but it doesn't seem to fix all my files from time to time, so I still use GTGs Ultimate Unbrick, and once it starts up as you're in Recovery Mode do a Factory Reset/Wipe Cache Partitions, it helps with not having the "Google Authentication Failed".
It's a long process from start to finish either way, so i figure save yourself the hassle for the long run and wipe it fresh...
I used heimdall without clicking the GB bootloaders checkbox. Upon reboot after sucessfully flashing everything, my phone shows the rainbow color thing then boots normally. I have no seen any issues other than that, however I only got it back up and running about an hour ago. I will see as the day progresses what happens. I just would like to know where I go from here to reacquire root priveleges. When I try to boot into recovery with the button combo I get a rainbow colored screen and nothing else showing, should I re-run heimdall with gb bootloaders box checked?
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
drnecropolis said:
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
Click to expand...
Click to collapse
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Cjohns8792 said:
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
bigjoe2675 said:
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
Click to expand...
Click to collapse
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Cjohns8792 said:
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Click to expand...
Click to collapse
Aft your 1st flash...dont close program...but put your phone back into download mode again and then it should allow you to check the box...then..
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Axiomkid said:
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Click to expand...
Click to collapse
Can't access recovery, it just shows a full rainbow screen.
Cjohns8792 said:
Can't access recovery, it just shows a full rainbow screen.
Click to expand...
Click to collapse
my suggestion is do the method i mentioned..

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

[Q] Confused as to what to do next: un-bricked, but recovery is still a garbled mess

So I rooted my brother's infuse 4G because it was slow as sin and needed A. a data/cache wipe and B, I wanted to give him Jellybean
I followed all the instructions I could; rooted, installed the modded 3e (or thought I did), got a CWM installed afterwards, and then set about installing first CM9 (as the Jellybean ROM post says I should) followed by the actual ROM and its Gapps. Well, I installed CM9 (although it seemed to take all of 30 seconds, rather fast...) when I tried to wipe data/factory reset, CWM froze. I rebooted and from then on I had it softbricked. Stuck booting at the samsung logo, and when I tried to return to the recovery, the recovery was a garbled mess that looked like a scrambled TV channel. I used Heimdall and did the one-click reset to stock, and here I am. The phone boots to stock just fine, but my recovery is still completely boned.
Do I re-root? How do I install CWM again without being able to install 3e? (can't install 3e without a working recovery in the first place, after all..)
One anomaly of note - when I was going about all this, booting the phone into recovery always got me 3e, even after installing CWM. I had to manually install CWM by using an update.zip and "reinstall packages" every time I wanted to use CWM. ROM manager would boot me to CWM, but it took several reboots and a flashable CWM zip before I could even get CWM installed in the first place - ROM manager refused to do it the easy way.
What did I do wrong, and more importantly, how do I get back on track? What do I do to put a fixed recovery back on this thing? Odin? ADB?
Today was the first time I ever used Heimdall, I've been a fair weather flasher since the beginning, I've never had to ADB or Odin.
It sounds like you didn't install cwm recovery properly, but I'm not sure I've never ran into this problem before. If you go here
http://forum.xda-developers.com/showthread.php?t=1524081 and carefully read over the first and second post you should end up with gb and red cwm recovery. The way I've done it was to put the phone in dl mode and flash the first package (the stock gingerbread att rom). After it is installed and booted up, I then power it off and go back into dl mode. Then flash the second package, which is just the kernel and red cwm recovery, (be patient because it takes awhile). Once that is done then go into recovery and wipe data/factory reset, wipe dalvik cache, wipe system, and install cm9. I think it only installs the kernel and recovery the first installation after formatting and creating the partitions, but after its done you have to go through the menus and tell it to reboot. After it reboots it will be stuck at the cyanogenmod galaxy s logo, so you will have to go into recovery once more. When you're there you should have blue cwm (only continue if you do) and install jb, without actually having to install the full cm9. When you navigate to which ever jb rom you want to install, a prompt will appear stating that there is incompatible partition layout and to confirm installation you will have to reselect the jb zip again to install. It will flash pretty quick because at this point its doing the same thing as when you went from gb to cm9 and only installs the kernel, recovery, and reformat/creates the partitions, (I think). It will reboot on its own but it will take you back into recovery. At this point all you have to do is navigate to the same jb zip you want to install and flash it, followed by gapps, and then reboot system. This process has worked for me but I highly recommend reading and following the instructions given in the post above.
Use goo.I'm app. Also you need to flash GB bootloaders in Odin . is recovery all colorful? If you see recovery fine just get goo app on play store and install a recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I would go the ODIN route, I have bricked so many times because i try to make the impossible possible. Just search for a already rooted pda,mdr file. I skipped the cm9 part idk if that would make things better or not but as my post says im a risk-taker
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
UnhoIy said:
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
but if don't have any problems i'm good right or should i go back and do it
MajorLeagueROM said:
but if don't have any problems i'm good right or should i go back and do it
Click to expand...
Click to collapse
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
UnhoIy said:
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
MajorLeagueROM said:
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
Click to expand...
Click to collapse
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
UnhoIy said:
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
Click to expand...
Click to collapse
lol it happens to the best of us

Categories

Resources