Bootloop after flashing Octane 2.3.6 - Samsung Galaxy S (4G Model)

What I did:
Had octane 2.X running fine.
Octane 3.0 released, so I wanted to upgrade.
Downloaded to sd
installed from CWM, rebooted from CWM
Phone kept looping the SGS4G initial splash screen, and would not do anything else.
Had to pull battery.
Put into download mode, Odin flashed bootlooders that I got from here
then flashed Krylon360's stock ota noCIQ rom, and here we are.
I know the bootloop has something with ext4 being enabled. I would appreciate if someone could point me at a tut, or explain it to me as if I was 5 Would love to use Octane again. Man I miss that sound quality

HeavenlySin said:
What I did:
Had octane 2.X running fine.
Octane 3.0 released, so I wanted to upgrade.
Downloaded to sd
installed from CWM, rebooted from CWM
Phone kept looping the SGS4G initial splash screen, and would not do anything else.
Had to pull battery.
Put into download mode, Odin flashed bootlooders that I got from here
then flashed Krylon360's stock ota noCIQ rom, and here we are.
I know the bootloop has something with ext4 being enabled. I would appreciate if someone could point me at a tut, or explain it to me as if I was 5 Would love to use Octane again. Man I miss that sound quality
Click to expand...
Click to collapse
At this point are you still boot looping or did flashing Krylon's stock noCIQ get you running again?
Ignore that, you must still be boot looping else you wouldn't have posted. LOL.
The boot loaders you loaded are for KC1 which is Froyo. You need to flash the GB boot loaders to get going again. I'd suggest using one of Bryan's ROMs from the The KJ6 Heimdall One-Click Collection. After flashing one of those, then you should be able to re-flash Octane.

That did the trick! Thank you!

you can try again, it helped me
sorry
how to delete a post?

Related

[Q] Phone force boots into recovery [Solved]

So here's the deal:
I've been working with a pretty decently running version of Cognition for the last two weeks on my Captivate. I decided to give Perception II a try and check out some gingerbready goodness. That's where the problem started. Perception for some reason wouldn't allow me back into Recovery Mode no matter what I try so I forced the phone to download and flashed back to 2.1 stock with ODIN. I then reinstalled CWM Recovery and tried to flash back to my Cognition backup I made in ROM manger.
The process looks like everything completed fine but when my phone boots, it loads the AT&T screen for a minute or two and then reboots into recovery mode.
What's the deal?
The details I had when using Cognition was:
CWM Recovery (I believe with LagFix)
Overstock Kernel
It didn't work with my original 2.2 backup either, I still get the same boot into recovery problem.
Any ideas?
Nandroid backups don't actually restore the rom, just your settings and **** of that particular rom. You have to Flash cognition then restore the backup and it'll be like you never changed anything.
Handalaan said:
So here's the deal:
I've been working with a pretty decently running version of Cognition for the last two weeks on my Captivate. I decided to give Perception II a try and check out some gingerbready goodness. That's where the problem started. Perception for some reason wouldn't allow me back into Recovery Mode no matter what I try so I forced the phone to download and flashed back to 2.1 stock with ODIN. I then reinstalled CWM Recovery and tried to flash back to my Cognition backup I made in ROM manger.
The process looks like everything completed fine but when my phone boots, it loads the AT&T screen for a minute or two and then reboots into recovery mode.
What's the deal?
The details I had when using Cognition was:
CWM Recovery (I believe with LagFix)
Overstock Kernel
It didn't work with my original 2.2 backup either, I still get the same boot into recovery problem.
Any ideas?
Click to expand...
Click to collapse
Let me guess, you didn't convert back to RFS before flashing??
Try Factory reset. And don't use the backup you have for Cognition, Flash a fresh full ROM. Your backup could be messed up.
EDIT: Studa beat me to it.. Grrrr
studacris said:
Nandroid backups don't actually restore the rom, just your settings and **** of that particular rom. You have to Flash cognition then restore the backup and it'll be like you never changed anything.
Click to expand...
Click to collapse
This is exactly what I needed to do. Apparently, (after finding a link I somehow overlooked before posting this) it had something to do with the format of the partition so upgrading the Stock to Cognition forced the RFS to EXT3 change allowing -all- of my backups to work. Thanks guys for getting me in the right direction.
Perhaps Im a little Slow
So Im suffering the same issue. Running Serendipity 7 update 2
I looked down at my phone one day and it was in clockwork recovery v2.5.1.2
I figured I had loaded it by an errant button press. So I selected reboot system now. It goes back into Clockwork right after the serendipity 7 splash screen.
Tried Factory Reset
Tried doing a restore
Tried doing a serendipity 7 re install Original and update.
I can install zips from sd card including the external one.
Any Recommendations ?

question about clockworkdmod and charge

I recently got my charge. used jt's
[ROOT] [KERNEL] [RECOVERY] - Root / Voodoo Lagfix / CWM Recovery
and got root and voodoo going.
then I downloaded CWM from the market and tried to "backup current rom"
after I did this the phone rebooted and is now stuck on the "samsung" splash screen.
anyone know why this happened?
why did CWM do this when I tried to backup the rom? anyone know because I do not know.
i tried to odin jt's file again but its still stuck on the samsung screen.
I just odin'd [ODIN] Stock Rooted ED1 (downgrade from ED2) [2011.05.18]
and was able to get it past the samsung screen but now its stuck in a boot animation loop.
Just wondering if anyone can tell me what happened when i tried to create a back up in CWM. and any ideas on what to do next. thanks!
i am going to try to odin altered beast and see if this will get it past the boot animation. if not i am totally out of ideas and will take any.
thanks guys,
if you don't like this post feel free to ignore it.
frogdod said:
I recently got my charge. used jt's
[ROOT] [KERNEL] [RECOVERY] - Root / Voodoo Lagfix / CWM Recovery
and got root and voodoo going.
then I downloaded CWM from the market and tried to "backup current rom"
after I did this the phone rebooted and is now stuck on the "samsung" splash screen.
anyone know why this happened?
why did CWM do this when I tried to backup the rom? anyone know because I do not know.
i tried to odin jt's file again but its still stuck on the samsung screen.
I am just odin'd [ODIN] Stock Rooted ED1 (downgrade from ED2) [2011.05.18]
and was able to get it past the samsung screen but now its stuck in a boot animation loop.
Just wondering if anyone can tell me what happened when i tried to create a back up in CWM. and any ideas on what to do next. thanks!
thanks guys,
if you don't like this post feel free to ignore it.
Click to expand...
Click to collapse
You can't dl cwm from the market. you have to install the version jt1134 posted in the first thread. your phone is bootlooping because you didn't disable lagfix b4 flashing ed1 package.
Flash the Alltered Beast Odin package and see if that doesn't get you unstuck.
Oh, and don't use cwm for backup/restore, it doesn't work yet.
hoppermi said:
You can't dl cwm from the market. you have to install the version jt1134 posted in the first thread. your phone is bootlooping because you didn't disable lagfix b4 flashing ed1 package.
Flash the Alltered Beast Odin package and see if that doesn't get you unstuck.
Oh, and don't use cwm for backup/restore, it doesn't work yet.
Click to expand...
Click to collapse
thank you. i am flashing altered beast now.
and yes it got me past the boot animation and i am back into my phone.
thank you for the reply.
I must go to sleep now as i cannot think straight.
[Odin][Rom][5/29/11]AC's Altered Beast **Alpha** Voodoo & CWM, ED2 with roo
seems pretty cool so far.props there.
but can i flash Jt's back over this and go back to the more stock feel with root? or first disable lagfix then go to ed1 then to jt's?
I think i will try that tomorrow night.(unless i fall totally in love with alteredbeast)
thank you for the replies and i hope my mistake can help someone else from not doing the same.
frogdod said:
thank you. i am flashing altered beast now.
and yes it got me past the boot animation and i am back into my phone.
thank you for the reply.
I must go to sleep now as i cannot think straight.
[Odin][Rom][5/29/11]AC's Altered Beast **Alpha** Voodoo & CWM, ED2 with roo
seems pretty cool so far.props there.
but can i flash Jt's back over this and go back to the more stock feel with root? or first disable lagfix then go to ed1 then to jt's?
I think i will try that tomorrow night.(unless i fall totally in love with alteredbeast)
thank you for the replies and i hope my mistake can help someone else from not doing the same.
Click to expand...
Click to collapse
Yes you can change roms now. If you flash a non-voodoo kernel you have to disable lagfix b4 flashing or you'll get stuck again
thanks for the replies guys.
im still running alteredbeast. Animations on it are nice.

Samsung vibrant help needed.

I flashed back to stock 2.1 on my samsung vibrant.
the phone boots up fine at first, then all of a sudden i get a wierd screen and the phone reboots automatically. i dont know what the problem is. can anyone please help me with this problem.
the phone is continuously rebooting for the past half and hour. and i have no idea what to do now.
PLEASE HELP ME WITH THIS.
im posting a photo of the "wierd" screen below. the quality is crappy, but i cant help it.
Were you coming from a GB rom? Be sure your not mixing bootloaders...Not sure what that is but if you flash just the stock kernel in ODIN, with the phone off (pull the battery)and using the button combo try and get into DOWNLOAD mode. you might recover it....or flash the Bali kernel and then try going back to stock again.
erad1 said:
Were you coming from a GB rom? Be sure your not mixing bootloaders...Not sure what that is but if you flash just the stock kernel in ODIN, with the phone off (pull the battery)and using the button combo try and get into DOWNLOAD mode. you might recover it....or flash the Bali kernel and then try going back to stock again.
Click to expand...
Click to collapse
yes i did try flashing a 2.3 ROM,but it didnt work properly, so i tried flashing the stock 2.1 again using ODIN...it got installed, but later all these things started happening.
i even flashed the 512 PIT file that came along with the stock 2.1, but still no use.
can u please post the link to the kernel you are talking about and also how should i flash the kernel?
thanks for your reply.
hey the problem is solved. i installed eugene's 2.2 leaked build and my phone is back to normal now...!!!!
thanks for all your help. i really appreciate it...!!!
Glad to hear you got it...just be careful to know which bootloaders you are on, GB or FROYO... unless you have alot of problems with a ROM its not really necessary to ever flash back to stock...I flash rom to rom without any issue as long as you:
1. wipe cache partition,
2. then wipe dalvik cache and then
3. factory reset all from CWM...
4.then flash whatever .zip ROM you like.
Flashing back to stock FROYO/ECLAIR from GB with an odin rom you must be sure the stock rom either includes both PBL and SBL or no bootloaders at all and then your good.

[q] [q&a] !!devs!! I need advice on what to do!!

ok...i have a semi-bricked phone.. i mean semi-bricked because it's functional, but I can't seem to restore from my backups or flash other Roms in CWM recovery.
so, the story goes..it's a long story but please read!! i am in dire need of help!
I was on the latest Infused V2, and have previously tried CM7, S7, hellraised Roms, etc.
so I was kinda experienced in switching back and forth between Roms from CWM.
Yesterday I felt like trying bigfau's port of DlevROM 5.0, which i managed to flash successfully. I made a backup of my infused ROM. DlevROM was missing support for my language so I decided to switch back to infused. but then i remembered MIUI, which I never had tried before.
so I flashed MIUI successfully and played around with it. everything was working but i just didn't like MIUI, so i wanted to restore my backup that i had made earlier that day.
Now.. I had restored previously many times so I thought I knew what I was doing..
when i booted into recovery from MIUI, it was blue. then i remembered from my recovery from CM7 to Infused that I need to be on the same recovery (aka RED) as the one i made the back up in. So i booted back into MIUI, downloaded SGS kernel flasher, then flashed bedwa's Infusion.
I then booted into recovery and i was in RED CWM!
So i proceeded to restore my backup.
it checked md5 sum, it then went on to restore system. I thought it was going smoothly until it started to restore data. then it failed.
here is what CWM says.
Checking MD5 sums...
Restoring system...
Restoring data...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
E:Can't mount /dev/block/mmcblk0p2
(File exists)
Can't mound /data/!
yeah.. i don't know where I went wrong.. I've never encountered a problem with restoring from CWM..
I only had MIUI, an older version of Infused V2, and S7 in my sdcard so i tried to flash infused v2 and s7. neither worked. i mean they flashed, but i kept on going into a samsung logo bootloop...
so i re-flashed MIUI... so i'm on MIUI right now.. which i don't like =((
i'm only planning on keeping it until someone gives me a solution!!
I've asked for help previously and all I got was a "sorry, use ODIN to stock"
I've never used ODIN to go back to stock before so I don't know how to do it...
I've read up on the ODIN threads but most seemed to have problems with it...
Would Odin to stock (not gtg's ultimate unbrick) give me root and modded 3e? what exactly is it going to wipe? pictures?
thanks for your help... please help... i really don't like MIUI... i want to go back to Infused V2... or DlevROM once bigfau puts in the language support!
please help
Would Odin to stock (not gtg's ultimate unbrick) give me root and modded 3e? what exactly is it going to wipe? pictures?
Click to expand...
Click to collapse
Use this
This would give you root and modded 3e. Odin would wipe EVERYTHING
Just follow the instructions on the page and you should be fine. I've done it a couple times.
Don't worry too much. Its not bricked or anything like that.
Reboot in recovery, and flash the infused ROM that's on ur phone. This should work.
Thumb rule: When moving between ROMs, install the ROM clean, and then restore ur backup (of the same ROM) on top of it. It could be a disaster restoring backup of a different ROM.
Just fyi, I had the same problem trying to go back from MIUI... I've used the ODIN/Root+3e on numerous occasions to basically start over BUT it keeps all my files like pics,music,contacts etc. so don't be intimidated by it..it works. Once you've done that you can re-flash S7, V2 or whatever you want.
Make sure you've got your drivers installed (download samsung kies to do so) and when you open Odin, you right click and run as administrator then follow the instructions.
ok, thanks guys! I will give both a try! =)
Another Solution:
1. Use GTG ultimate unbrick with PIT file to restore partitions. CLICK HERE TO DOWNLOAD GTG ULTIMATE UNBRICK FOR ODIN.
2. Flash community kernel v8 in Odin in order to root + clockwork mod. (Put the downloaded file in the PDA slot of odin)CLICK HERE TO DOWNLOAD COMMUNITY KERNEL FOR ODIN.
3. Flash whatever rom you want to use.
4. Restore your backup for that rom.
5. Enjoy.
diablo009 said:
Don't worry too much. Its not bricked or anything like that.
Reboot in recovery, and flash the infused ROM that's on ur phone. This should work.
Thumb rule: When moving between ROMs, install the ROM clean, and then restore ur backup (of the same ROM) on top of it. It could be a disaster restoring backup of a different ROM.
Click to expand...
Click to collapse
question,
since i'm in blue recovery right now (i'm on MIUI for the time being)
would I have to flash red CWM before flashing Infused V2? or can i just flash it from blue recovery??
thanks~
jhong91 said:
question,
since i'm in blue recovery right now (i'm on MIUI for the time being)
would I have to flash red CWM before flashing Infused V2? or can i just flash it from blue recovery??
thanks~
Click to expand...
Click to collapse
Yes
Sent from my SGH-I997 using XDA App
LG_iiNsTiiNcT said:
Yes
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
You might want to be a bit more specific about which of those questions you were answering
GGXtreme said:
You might want to be a bit more specific about which of those questions you were answering
Click to expand...
Click to collapse
Lol my bad. Flash red cwm first
Sent from my SGH-I997 using XDA App
Bandit_Kaine said:
Another Solution:
1. Use GTG ultimate unbrick with PIT file to restore partitions. CLICK HERE TO DOWNLOAD GTG ULTIMATE UNBRICK FOR ODIN.
2. Flash community kernel v8 in Odin in order to root + clockwork mod. (Put the downloaded file in the PDA slot of odin)CLICK HERE TO DOWNLOAD COMMUNITY KERNEL FOR ODIN.
3. Flash whatever rom you want to use.
4. Restore your backup for that rom.
5. Enjoy.
Click to expand...
Click to collapse
ok guys..
i just tried GTG's odin back to stock (not ultimate unbrick)
computer recognized my phone,
folllowed every step to a TEE,
and then the phone rebooted itself and i saw the ATT bootscreen, so i was in a relief.
then after the att bootscreen the screen just went blank.... dark... pitch dark.. and nothing seems to work...
so i downloaded GTG's ultimate unbrick, and followed the instructions to a TEE and still the phone screen turns black right after the att bootscreen...
ok.. so what do i do now..??
Edit 1: So I booted into stock blue recovery, deleted all user data, and rebooted and it workedd!! yay~~ now push the community kernel and restore? right?

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:

Categories

Resources