Database Info

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

Twrp boot loop

This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??

lonoguge said:
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
Click to expand...
Click to collapse
Where did you get twrp?
lonoguge said:
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
Click to expand...
Click to collapse
What is "another rom"?
lonoguge said:
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
Click to expand...
Click to collapse
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.

bhundven said:
Where did you get twrp?
What is "another rom"?
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
Click to expand...
Click to collapse
I got it from what I thought was the official XDA TWRP thread but I'm not sure if it was official or not
at first I tried reinstalling codename but now I'm trying Beam (Tuk edition) and it seems to be working

TWRP Major Boot Loop
hey guys, im new here and i desperately need help with my phone!
the other day i was flashing a rom on my samsung galaxy s 4g. Things were turning out fine, until i had some complications on my phone.. so, i removed the rom. when i rebooted my phone, it went directly into the team win recovery project boot loop and every time i try to reboot my phone, it goes into the twrp. I also can't wipe anything and i can't delete anything! Does anybody know how I can solve this or is my phone basically bricked

more details would be helpful..
As in what rom, or what kernel.... etc... and make sure you have the corret phone.

Same problem with t959p
Looks like I'm not alone.......here's my story
the other day I wanted to switch from a stock rom to a custom, so I flashed redux 1.3 which was actually a froyo rom, and it started draining my batt like crazy so I flashed another rom on top of the froyo rom not realizing what I was doing and somehow messed it up cuz now it will only boot into recovery.
Now just to be clear I know this was my fault, I know I should have odin'd back to stock first, but I wasn't thinking at the time.....Ohh and just so you know I've flashed this sucker hundreds of times and was always able to get out of any mess I got in.
So here is the situation as it stands now, 3 button combo to enter download does not work. I can only get it into download with the jig I made. the problem is even in download mode none of my pc's will detect the device as a Samsung composite device, so odin will not see it. I've installed every possible 32 n 64 bit driver I could find including reinstalling kies. Kies wont even see it. I've tried flashing a few roms that I know worked and still it just boots into recovery. Now one thing I'll tell you is that depending on which rom I flash I can get recovery to switch from cwm to twrp. right now I left it with cwm 6.x.
what I need is a cwm flashable stock telus t959p rom complete with bootloaders or at the very least a cwm flashable zip file containing the bootloaders to see if I can recover the phone.
ohh and if your thinking about telling me to google search for the answer then don't bother.......I've spent the last 4 days reading posts and going to different websites and repositories trying to find something that would help me and so far nothing has.
the only thing that might work as a last resort is pushing the bootloaders as per one of raver's or whitehawks posts but it's a little more complicated for me as I would have to set up a laptop with Linux as I don't think i'll be able to pull it off with any of my windows pc's, win7 and win 8 only.
so if anyone has the files I need or can make them please let me know....or if you think you have another solution I could try i'm all ears err eyes.
thanks
Jedi

Have you tried heimdall one-clicks? Maybe it's showing up as gadget or something like that. I've had luck using zadig and heimdall to bring it back from the brink of death.
http://forum.xda-developers.com/showthread.php?t=1358498

EDIT
Woops replied to the wrong thread .
Nothing to see here, move along

Would like to revive a slightly dead thread.
I upgraded to a Galaxy S3 and no longer use my SGS4G for daily use. I had AOKP and disliked it, FC's and didn't like the feel. I have been trying to install a new rom ( old rom, VH Black Ed. ). Every time It loads into TWRP I have the ability to select the zip, install, it says complete, but reboots right back to TWRP menu. I've tried flashing CWM and it will install, flash the rom, reboot, and right back to this TWRP B.S... what am I doing wrong? I want to continue to use this SGS4g for music and internet duties.
How can I install CWM and have it stay even after a reboot? This TWRP is starting to me off

Did you happen to one click to stock before you went ham at the recovery?
Sent from my SGH-T959V using Tapatalk 4

Am I hard or soft Bricked?

I had been running liquidsmooth rom. There were issues when it booted up, would always boot twice then went into the system ok. I decided that I'd rather have a more stable rom on my phone, so I went into ez recovery and tried to flash back into cwm 6 recovery. When it came up, the restore backup option was not there, and I couldn't boot back into the rom. I tried several times, but to no avail
Since then I have tried Odin on the phone, and have gone through the soft brick recovery steps that I had to do one time before. I flashed both files and the stock file for the third step. I do get the error messages that I normally would where normally I would factory reset and clear cache, however I then get two more.
e: failed to verify whole-file signature
E: signature verification failed
Instalation aborted.
I cannot get beyond that, I do the wipe and reset each time, however when I reboot I just get funneled back to the same error message. I've scoured the forums and the internet but cannot find a solution to my problem. Am I SOL, or is there a solution I haven't found yet?

What you could do is on your computer, download a synergy ROM like 1.5 1.6 1.7 since those don't require an unlocked boot loader. Connect your phone via USB (I don't know if it will register in the state its in) or you can get a micro SD card reader and pop that into your computer, and transfer the synergyrom on your SD card and pop it back into your phone..get to your custom recovery wipe data/factory reset wipe cache and dalvik cache. Then install .zip from SD card and choose the synergyrom. From there it'll take a bit for your phone to boot up, but you should be up and running and then you can do what you want. I usually keep one ROM like this on my phone so if something doesn't work out I can start over. Let me know if you need more help, I'll try my best to see what I can do from work.
VZW SGSIII SynergyRom R60 w/Imoseyon's LeanKernel v0.5

95talondsm said:
What you could do is on your computer, download a synergy ROM like 1.5 1.6 1.7 since those don't require an unlocked boot loader. Connect your phone via USB (I don't know if it will register in the state its in) or you can get a micro SD card reader and pop that into your computer, and transfer the synergyrom on your SD card and pop it back into your phone..get to your custom recovery wipe data/factory reset wipe cache and dalvik cache. Then install .zip from SD card and choose the synergyrom. From there it'll take a bit for your phone to boot up, but you should be up and running and then you can do what you want. I usually keep one ROM like this on my phone so if something doesn't work out I can start over. Let me know if you need more help, I'll try my best to see what I can do from work.
VZW SGSIII SynergyRom R60 w/Imoseyon's LeanKernel v0.5
Click to expand...
Click to collapse
I actually had that on my sd card from last night when I was messing with it trying to fix it. I did try that and this is what I get
--Install /sdcard...
Finding update package...
opening update package...
verifying update package...
E:signature verification failed <in red type>
Instalation aborted.
Thanks for your suggestion, Part of the problem could be I'm not getting the traditional cwm loader, every time it starts it comes up in tiny type at the top: Recovery Booting.... dont know if that makes a difference or not?

signature verification error means your booting into stock recovery instead of cwm recovery...thats why there is no back up/ restore option.

droidstyle said:
signature verification error means your booting into stock recovery instead of cwm recovery...thats why there is no back up/ restore option.
Click to expand...
Click to collapse
I can't get it to do anything other than that. I've held the up and home button to try to get elsewhere, but it always goes to that. The only other thing I can do is get to the Odin download screens, but even then, after flashing it boots back to the same place with the above errors.

udrunner said:
I can't get it to do anything other than that. I've held the up and home button to try to get elsewhere, but it always goes to that. The only other thing I can do is get to the Odin download screens, but even then, after flashing it boots back to the same place with the above errors.
Click to expand...
Click to collapse
wipe data/factory reset then reboot from stock recovery. use my guide for proper instructions on flashing back to stock. research then flash, dont flash then research.

And Liquid is supposed to boot twice. It's kexec.
Sent from my SCH-I535 using Tapatalk 2

udrunner said:
I can't get it to do anything other than that. I've held the up and home button to try to get elsewhere, but it always goes to that. The only other thing I can do is get to the Odin download screens, but even then, after flashing it boots back to the same place with the above errors.
Click to expand...
Click to collapse
Why don't you Odin back CWM recovery, boot into cwm recovery and use this to toggle secure signature off and flash synergy rom?

buhohitr said:
Why don't you Odin back CWM recovery, use this to toggle secure signature off and flash synergy rom?
Click to expand...
Click to collapse
because it trips the flash counter when you odin anything custom.

droidstyle said:
because it trips the flash counter when you odin anything custom.
Click to expand...
Click to collapse
Gotcha! I forgot about the flash counter. Thanks.

buhohitr said:
Gotcha! I forgot about the flash counter. Thanks.
Click to expand...
Click to collapse
no problem...really its not a huge deal as the app triangle away can reset it, but i prefer to just use odin for stock purposes only.

droidstyle said:
wipe data/factory reset then reboot from stock recovery. use my guide for proper instructions on flashing back to stock. research then flash, dont flash then research.
Click to expand...
Click to collapse
I had actually followed those steps already, but still get the recovery booting problem and can't seem to get past that. I can try it again after work, but have done those steps at least 3 or 4 times to no different results.
Thanks for the help though. I'll keep trucking on, just missing my phone today....

year voldsou
droidstyle said:
because it trips the flash counter when you odin anything custom.
Click to expand...
Click to collapse
I'm willing to try it if it might help me get back, I just dont want to do anything that will mess it up anymore than I already have.
At this point I just want to get back to stock /synergy if I can and be happy with it. I've never had issues like this when rooting/flashing on other phones that I've had, but at this point will just be happy with a useable phone.

droidstyle said:
because it trips the flash counter when you odin anything custom.
Click to expand...
Click to collapse
I'm willing to try it if it might help me get back, I just dont want to do anything that will mess it up anymore than I already have.
At this point I just want to get back to stock /synergy if I can and be happy with it. I've never had issues like this when rooting/flashing on other phones that I've had, but at this point will just be happy with a useable phone.

udrunner said:
I'm willing to try it if it might help me get back, I just dont want to do anything that will mess it up anymore than I already have.
At this point I just want to get back to stock /synergy if I can and be happy with it. I've never had issues like this when rooting/flashing on other phones that I've had, but at this point will just be happy with a useable phone.
Click to expand...
Click to collapse
As droidstyle mentioned that when the flash counter tripped, it won't allow you to re odin cwm. My question is can you Odin back cwm (clockmod recovery) and boot directly to it?

droidstyle said:
because it trips the flash counter when you odin anything custom.
Click to expand...
Click to collapse
Then why is it that flashing a rooted "stock" /system partition, which is technically custom, through Odin, doesn't trip the flash counter?
Is there any other downside to tripping the flash counter besides having to use triangle away to reset it if you ever want to return your phone?

buhohitr said:
As droidstyle mentioned that when the flash counter tripped, it won't allow you to re odin cwm. My question is can you Odin back cwm (clockmod recovery) and boot directly to it?
Click to expand...
Click to collapse
No, I ran home on lunch and tried, and it wont let me do that. Odin wont flash it and I just get a FAIL, and the phone say security check fail.

I After trying a few differnt times with a couple versions of the stock rom I found, I got it back up and running.
As much as I love custom roms, I think I'm done playing with this phone. Thanks everyone for the help.

[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