[Q] Unable to get pass "Checking BML/MTD" - Samsung Infuse 4G

I have searched xda and the WWW., and have not found anything similar to the issue that I am encountering.
1. I flashed stock rom UCLB3 (http://forum.xda-developers.com/showthread.php?t=1524081) and flashed Entropy512 Kernel
2. Flashed CM9 (http://forum.xda-developers.com/showthread.php?t=160184)
3. Flashed just fine
Here is the issue:
I wanted to put MIUI 2.3.2b Stable ROM and during the flash progress in CWM Blue/Red (CWM ver, doesn't matter), I get stuck at "checking BML/MTD" and all of the sudden the Samsung Logo flashes followed Cyanogenmod 9 flash intro, but then the phone just shuts down.
This only occurs when I try to flash MIUI ROMS, when before I was able to flash MIUI, prior to Cyanogenmod 9 flash.
The phone can be reverted back to stock UCLB3 and flashed with any ROM non MIUI based, but just not MIUI.
Has any one encountered this before or can lead me to possibly checking error logs to see what could be causing the issue?
Thank you in advance

If you really dis search www you should know the recovery you have does matter....
What I would do is Odin back to stock flash cm7 then flash miui ...
Flashing. Miui from red recovery wont work because
It red recovery uses voodoo partitions not compatible with cm7/miui
when you do flash from red cwm you should reboot back into recovery and reflash since.it converts your data partitions
(You should have blue 5.x.x recovery once you reboot into recovery again)
Or re download the rom and see if that's the issue
Sent from my SAMSUNG-SGH-I717 using XDA

Thank you for your response.
I reverted back to stock Froyo. I apologize but I neglected to say that I tried loading the MIUI ROM via the Blue recovery and still no go.
I have flashed CM but not CM7 instead CM9 and then tried flashing MIUI no go.
Not sure if CM9 is a completely different ROM from CM7 but I will give that a try.
Note that the 2.3.2 Stable MIUI rom is a ported ROM from I9000 models and currently I am able to flash non ported ROMS such as MIUI SHOCK & AWE.
I think where the issue may be residing is the fact that I am also getting an MBR Checksum Failure message when booting to Recovery.
Not sure if this whole thing is hopeless as no one seems to know how to get rid of the Checksum errors, but I am still able to flash ROM's on my phone just not ported MIUI Roms with file designation of i9000; ie miuiscotland_I9000-2.3.2b-Stable.zip.
Regardless. Thank you for your time reading and replying. I very much appreciate the input.
jayRokk said:
If you really dis search www you should know the recovery you have does matter....
What I would do is Odin back to stock flash cm7 then flash miui ...
Flashing. Miui from red recovery wont work because
It red recovery uses voodoo partitions not compatible with cm7/miui
when you do flash from red cwm you should reboot back into recovery and reflash since.it converts your data partitions
(You should have blue 5.x.x recovery once you reboot into recovery again)
Or re download the rom and see if that's the issue
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse

Thank you for being reasonable and for having a good reply
I like the way you replied it was very "grown up " to say unlike the little kids who just rant about BS. I appreciate it.
All I can say is try flashing other MiUi bulids
There is one who is very very stable but forbidden to post here on xda :cough: galnet :cough: I heard it was really good I tried it
Back when I had my infuse and its really stable ....apart from the regular MiUi bugs
But Google it since we can't really post links here on xda regarding galnet miui
Sent from my SAMSUNG-SGH-I717 using XDA

Related

Anyone know how to downgrade CWM recovery?

So I upgraded to clockworkmod recovery version 3.0.0.5 to try out the beta version of Cyanogenmod 7.
Anyway, it's waaay too buggy for me at the moment (random battery drainage and restarts) and I'd like to go to a different custom rom.
The problem I'm having is that clockworkmod versions > 3 apparently will only install ROMs that were compiled with Edify scripting... which appears to be just about none of the ROMs I'm interested in at the moment.
So I've tried downgrading through the ROM manager and through running flash_image on the phone's terminal several times - always landing me back in the orange coloured CWM v3.0.0.5.
So my question is; how would I get back to the older green coloured version of the recovery?
I've searched a couple of hours on the internet now, but have found almost nothing relating to the Samsung Galaxy Captivate.
Any help would be greatly appreciated.
Thanks!
Just flash back to stock. Reroot if u need to then use rom manager to flash it
Sent from my SGH-I897 using XDA Premium App
Ownaginatious said:
So I upgraded to clockworkmod recovery version 3.0.0.5 to try out the beta version of Cyanogenmod 7.
Anyway, it's waaay too buggy for me at the moment (random battery drainage and restarts) and I'd like to go to a different custom rom.
The problem I'm having is that clockworkmod versions > 3 apparently will only install ROMs that were compiled with Edify scripting... which appears to be just about none of the ROMs I'm interested in at the moment.
So I've tried downgrading through the ROM manager and through running flash_image on the phone's terminal several times - always landing me back in the orange coloured CWM v3.0.0.5.
So my question is; how would I get back to the older green coloured version of the recovery?
I've searched a couple of hours on the internet now, but have found almost nothing relating to the Samsung Galaxy Captivate.
Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Coming from CM7 you will have to return to stock before you can flash any other roms anyway. Its in the CM7 FAQ.
Ownaginatious said:
Anyway, it's waaay too buggy for me at the moment (random battery drainage and restarts) and I'd like to go to a different custom rom.
Thanks!
Click to expand...
Click to collapse
Ok I see that you have only 2 posts so I am going to spell this out nicely.
1: Flash back to stock always when changing roms
2: Root the phone then load rom manager and install clockwork mod
3: That puts an update.zip on your internal sd card. Copy that to your computer in a safe directory. I put mine where I store my roms
4: Reboot your phone to recovery and install upadate.zip. Reboot to recovery and if CWM doesn't load install update.zip again and it will reboot to CWM the second time.
5: Then when you want to flash a rom flash back to stock then copy that update.zip to the phone copy the rom to the phone then reboot to recovery. If it doesn't reboot to CWM then install update.zip and it will reboot to CWM. Then you can install your rom.
MAKE SURE YOU FLASH BACK TO STOCK BEFORE ATTEMPTING A NEW ROM INSTALL.
zelendel said:
Coming from CM7 you will have to return to stock before you can flash any other roms anyway. Its in the CM7 FAQ.
Click to expand...
Click to collapse
and check repartition when flashing according to the CM7 faq
zelendel said:
Coming from CM7 you will have to return to stock before you can flash any other roms anyway. Its in the CM7 FAQ.
Click to expand...
Click to collapse
Why would anyone read the faq...
Sent from my SAMSUNG-SGH-I897 using XDA App
Sarcoid said:
and check repartition when flashing according to the CM7 faq
Click to expand...
Click to collapse
One click does it automatically.
Sent from my CM7 powered captivate

[Q] ics rom upgrade infuse 4g help

So Im a new member to the site for the most part (have been reviewing threads for more than a year now, though) and decided to finally sign up while trying to flash CM9 ICS on my infuse. Im running into issues. I currently am running ZUES Build 6, with the ICS theme / framework. I LOVED CM7 for the Ascend, so decided to give it (CM) a try on my infuse. The Dev threads say that i should have no issues b/c Im flashing from a UCBL3 / GB ROM, but when i try to just flash it, its an invalid package...? I tried flashing over the ICS recovery from both Hiemdall and Odin but hiemdall needs a "valid tar.gz" and i also encountered the same type of issues with Odin. Ive used Odin before to flash to stock, but im a complete noob to Hiemdall. Any help from an experienced Dev or another flashoholic is greatly appreciated! dont have 10 posts to ask in the Dev section yet...
Could you be trying to flash a .zip file that is designed to be flashed in CWM recovery via Heimdall or Odin? I don't have an Infuse but I'm currently running AOKP on my Galaxy SII and the files posted by in that development thread are CWM flashable.
ive tried in all 3...cwm says
"Cant open /sdcard/update-cm-9.0.0-RCO-infused4g-04152012-UNOFFICIAL-signed.zip
(bad)
installation aborted"
I figured it was a bad DL...tried 2 other DLs, no luck
they said to flash from gb to flash a file called ICSRecovery.tar.... how would i go about doing this...i have red cwm like needed. im completely lost here...And thanks for replying.
edit: here are the pages, and is your rom ICS
http://forum.xda-developers.com/showpost.php?p=24665001&postcount=272
http://forum.xda-developers.com/showthread.php?t=1593187
I does sound like a bad download, redownloading would have been my first instinct as well.
Rereading your post, it seems like maybe you haven't been able to successfully flash the ICSRecovery.tar that jt1134 mentioned in the first link you posted. Entropy512 doesn't mention needing to flash that recovery before the .zip but it may be implied, I haven't read nearly enough of the pertinent threads. You should be able to flash the .tar using Mobile Odin.
It looks like you pulled the download from Entropy's thread here
http://forum.xda-developers.com/showthread.php?t=1601844
Entropy left some pretty detailed instructions that should be easy enough to follow after you've overcome this initial hurdle.
so you suppose i install mobile odin...will try, and will keep progress updates
update:mobile odin not available for my device...must dump... :/ 30 minutes...............
Update: i was able to flash the recovery image for ICS through sgs kernal flasher, reboot, and get rainbow recovery. it WAS a bad DL, the ICS recovery couldnt flash it...but when i tried to reboot normal, i got into what i call IRONY!!! i was stuck in a recovery loop ( you see the irony in that, right?). reboot put me back in recovery again every time i clicked the option...i was able to get out of the recovery loop by flashing the zues 6 rom (because the ICS couldnt read the boot image of my backup) then from there i rebooted and got the voodoo recovery (huge relief). I was then able to restore my backup (after practically drenching myself in sweat)! I will be uploading an image of the rainbow recovery, as its been dubbed, for those who would like to see what a pain in the ass it is.........

[Q] TWRP Q&A

Dont want to muck up the CM7 thread and no thread was started.
FB Im wondering if twrp is fully wiping when you run the wipe option. I used the kj6 heimdall one-click to get back from a bad flash. However once I finally was able to get everything set back up I had restored some apps through Titanium Backup, but only app no data. Amazon app store was one and I had to delete the backup and uninstall the app, reboot clear cache and then re-install it to get it to work. The theme chooser app was fcing on me until I did the same thing.
After I did this I applied a theme apk that borked me. I was stuck on the team acid logo. No boot loop just stuck. I then one clicked to kj6 again, then used antonx kernel one click. Made a new backup of my efs, wiped everything including boot img. Flashed the twrpcm7 zip and followed the directions to finish.
I know anything is possible but is it likely that twrp is seeing something not wiped in the bml to mtd conversion and its causing conflicts?
If your not comfortable with the possibility of bricking your phone do not follow my steps and format everything. Formatting boot has the possibility to brick your device.
Hmm, well /data isn't getting wiped in R11. Bryan submitted a patch for updater.sh that should take care of this though I haven't tested it. I haven't tested a BML->MTD (cm7-twrp) flash though, but I'll have to look into it in the next few days. I'm running a rom build right now, so I'll probably test that out tonight.
I didn't wipe anything, I just flashed the twrp boot.img. I am running Team Kick Asses MIUI Revenge (MTD). After I flashed and the phone booted, wifi would not turn on, and it said error underneath the button. Pulled a logcat but all it said was wifi failed to initialize. Is that error due to the fact I didn't wipe anything or factory reset/fix perms?
Either way, it is super sweet recovery!
Max says its a driver issue. Ill find the post and link it.
m4xm4n said:
The reason wifi didn't work is because the wifi module needed to be from the same kernel build. I'm not sure how FB built the two builds, so I don't know if he included a module from a different kernel build or not.
Try the R11B with TWRP and then install R11(not B) with inject TWRP enabled.
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
Now that you have twrp make a cwm zip for the r11 kernel, flash it via twrp and leave the "inject twrp" option enabled. You should get working wifi and twrp
Sent from my SGH-T959V
Like I said on cm thread the wifi module is different from the one Max used on his new boot.img which is why twrp and the new boot.img doesn't work with the current miui build ...the first release of dianxin os had the new boot.img fb sent me and that was the wifi issue.
sent from my batcave
I flashed miui on with twrp doing a wipe firs and it installed miui fine, with wifi and everything seems to be fully functional. Just to be safe I wanted to test out twrp on miui, however the only way I could get to it was volume up+down+ power. But that loads it right up, and I flashed a few different modems to see which gave me the best signal, and it worked each time. Btw, nice work fb twrp is great.
Sent from my SGH-T959V using xda premium
Which modems did you flash? If the modem flash DID work you should be able to go into Settings > About Phone and check under baseband version. I'm not sure if that's the exact menu on MIUI but there should be something very similar.
I just flashed kg4 and that's what it says under baseband version, I flashed kd1 earlier and that's what it said before I just flashed kg4. Just to make sure it was working. I think it says t959vuvkg4 or something to that effect, it definately just changed though from kd1
Sent from my SGH-T959V using xda premium
Hey guys just a progress report on this. I've been messing with a twrp injection cwm zip all evening. After some discussion with bhundven, the way we're going to go about this is to NOT include twrp by default in cm7. It's been really hard to get a working copy compiled and included with cm7 and if we can't do this automatically there's no point to doing it at all.
The CWM zip will (hopefully) allow us to give you the option of using TWRP even if you're using CWM at the moment. The benefits are the following:
You won't need to mess around with kernel features that don't work (wifi was broken, ffc was broken)
You only really need to inject twrp once via CWM since twrp comes with an inject option before you flash a CM7 update.
It'll make it easier on us since we'll have less releases and thus have to provide less support.
At the moment I'm trying to have something for you guys tonight, but the chances are slim for that happening.
FB
For some reason TWRP can't Flash Zip file like Mtd modem kd1. I try to make a nandroid bk and didn't work. Also I try to save error logs on sd card didn't work.
My english is not the best, sorry
Sent from my SGH-T959V using xda premium
Please post the logs here.
What errors did you get when trying to flash the kd1 modem or make the nandroid backup? I've tried making and restoring a nandroid backup using CM7 R11 with twrp injected by the zip and it's worked fine for me.
What rom/kernel combination are you using?
Error: Unable to open zip file
I try nandroid backup again and for some reason did work but wasn't working.
Am using CM7 R11B & CWM TWRP
Everyting else is working good thanks!!!!
Sent from my SGH-T959V using xda premium

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:

[Q] Recovery boot loop

I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
t1op said:
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Click to expand...
Click to collapse
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
WayTooGosu said:
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
Click to expand...
Click to collapse
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
lumin30 said:
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
Click to expand...
Click to collapse
Ah I see. But my point was that some ROMs state that the user must be on an ICS ROM/Kernel to flash this. I guess I wasn't very clear as I am new here and lack understanding.
champ1919 said:
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I used Odin to return to stock. I used Super One Click to root. I used root explorer modify the recovery to allow me to boot into "CWM final for Froyo". That much each and every time.
The first time I installed
[TFQ - 30/12/2012]X.A.O.K[Kanged - Xperia Style]
That is an ICS rom. Installed fine with a new CWM.
The second time I installed the same.
The third time I installed
ROM-MTD-TWRP-ICS-4.x-Audiophile
That is another ICS rom. Installed fine with TWRP.
Each and every time, when returning to recovery to flash more, I got stuck. I can't boot to anything except recovery.
My brother suggested that the problem is using the Volume up and down and power button ("three finger salute") to return to recovery instead of from OS power down menu.
For a fourth time I started over again. Now, using the reboot>recovery, everything works fine.
One thing, you need to have ginger bread bootloaders. So, when you say Odin back to stock, are you referring to kj6?
You could cut down some of the work by using Odin to flash a kernel with recovery & root in it. Antonx & drhonk both have kernels that will do that with odin.
I flash bhundven's cm9 Rom before jumping to any of the others(and wipe between). I believe some of the Rom authors have that in their instructions.
Sent from my SGH-T959V using xda app-developers app
Yeah... GB bootloaders, not Froyo. Your return to stock should be a return to GB stock, not Froyo... and your return to stock can be a return to a rooted stock. If you want to make your life less painful.
It's about MTD to BML, not really about the base version. You just don't want to wipe out what allows later stuff to actually work properly...
Thanks for the advice. I haven't used custom roms very much. Trying to figure out which ones to choose was difficult. I started on stock Gingerbread, but everything I encountered in searching indicated that I needed to go back to Froyo to get CWM then go from there. ...Perhaps I kept running into very old instructions? In any case, should I need to go back to stock again some day, I'll try to figure out which GB roms I could use, including root and custom recovery.
I guess the solution to my problem is: 1) flash back to Froyo or Gingerbread; 2) after flashing an ICS+ rom, only go to recovery from OS reboot menu (never "three finger salute").
I'm actually surprised that people don't run into this problem more often, enough to create a sticky about it. I'm sure I'd still be pulling my hair out if my brother hadn't run into the problem on his Fascinate a year ago.
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Theraze said:
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Click to expand...
Click to collapse
Interesting... Perhaps if I went back to a gingerbread stock then upgraded to ICS the problem wouldn't occur?
I'll have to try that the next time I might need to return to stock.
Hello,
First I just want to say thank you to the mods for running a great forum and to the devs for keeping this device current.
I just struggled over a period of days with this issue.
The end result being, that you need to go to CM9 BEFORE you try JellyBean or later!
Just hope this helps someone else who missed that instruction.
Thanks devs/mods/everyone for keeping this device alive!!!! :good::good::good:
*EDIT* correction... i THINK you need to go CM9 Before trying something else
Not all ICS ROMs require CM9, but you must have at least CWM5 recovery to be able to flash CM9 or these ROMs. Follow ROMs' OP instructions.
I personally tested HebMIUI flash over Stock GB with CWM5 (Basic with a twist kernel) without going through CM9.

Categories

Resources