Develop Bugs

[Q] Need help with CWM Recovery and other issues!

Hello All,
I have been working with my friends EPIG 4g phone for a while now. The first thing I did was use "superoneclick 1.7" to root his phone. Then he got interested in trying different roms+kernels, so he came to me for more help. Almost all the custom roms I was researching are EC05 based roms, so I looked further into it. For reasons unknown, he is still on DI18 Eclair (must not have got the OTA). I dug on forums and found the zip file that would allow him to jump from DI18 to EC05 (froyo), but I need a custom recovery to install the zip. No matter what I try, I cannot get the phone to boot into CWM recovery. (Tried both from rom manager, and using camera button+vol. down+power combination) I have tried just about everything that I can think of, to no avail.
I have also tried:
Unroot & Re-root using process found here:
http://forum.xda-developers.com/showthread.php?t=770388
Wiping all data via factory reset (really wish I wouldn't have, waste of a try)
Tried using methods found here:
http://forum.androidcentral.com/epic-4g-rooting-roms-hacks/34603-clockworkmod-recovery-rom-manager-guide.html
When trying to do anything in the stock recovery, I always get the:
e:signature verification failed errors.
Please bombard me with any and all ideas you guys have. I am currently about to try to manually install the CWM recovery by placing the update.zip file on the SD root directory. IF I can get that part done, I'm confident I will be able to get everything going. Another option I have read from other people's threads that I have not yet used is the Odin revert to stock and then flash some special .tar files. I took a look at Odin and don't remember seeing options for "stock" or anything, so if anyone can point me to a good Odin walk-through, that would be awesome.
PS: Ask me if I have failed to clarify on any aspects of the problem. Forgive me for not including more info on the problem, Ive been through like 8 hours of random stuff while trying to fix this, so Ive seen too much to remember everything I've seen.
Thanks in advance!
-Clarity

Too many words
I kinda fell a sleep in the middle so yeah
If you want to return too stock use odin
If you want to go to froyo from eclair use odin
If you want cw use I've of the one click rooters
Going to cw is just pressing every button that is not on the keyboard
(power + volume up + volume down + camera)
Sent from my SPH-D700 using XDA Premium App

Stock recovery will get you nowhere on this phone, and with all you have tried so far, I believe Odin is the best course of action. Here is a link to the Odin package-
http://www.mediafire.com/file/fn9s5cqkkwyu68d/Odin3+v1.61andepic.pit.zip
Unzip it to a folder on your desktop.
The necessary drivers and instructions for using it are here in the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
Follow the instructions carefully and be sure the drivers are installed before starting. Obviously, wherever it mentions the DI18 tar, you will use the current one in it's place. You can use this one, it's pre-rooted and de-odexed.-
http://forum.xda-developers.com/showthread.php?t=1021305
That tar file is still RFS file system so you will need to install CWM 3.0.0.6 and boot into it with the 3 finger solute so it can convert the file system to ext4. Package and instructions here-
http://forum.xda-developers.com/showthread.php?t=897612
If you made it this far you should be able to install one of the current ROMs you've been shopping for.

Thanks for the responses guys, I will try that out when I get a chance. Might be a while though because I don't see my friend that often.

So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Basically, I would like to know what I am doing wrong here. Is the CWM included from that .tar file compatible & ready to flash any custom ROM that I want? Or do I need to use that CWM 3.0.0.6+root that Mattalica suggested? The EC05 was prerooted, so I'm wondering what happens if I use the 3.0.0.6 exploit on top of this root... Let me know guys.

onlyclarity said:
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Click to expand...
Click to collapse
What happend when you rebooted that indicated it was not successful? If you had strange vibrations and a bootloop, that is common when trying to flash these new generation ROMs like ACS and Bonsai. A simple reflash usually fixes it.
Sent from my SPH-D700 using Tapatalk

The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.

onlyclarity said:
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
Click to expand...
Click to collapse
BakedSnack 1.6 is a RFS ROM and is DI18 based. If you installed CWM 3.0.0.6, it would have converted your filesystem to EXT4. BakedSnack 1.6 does not have kernel support for EXT4. However if you installed an older version of CWM it would explain how ACS failed to install and how BackedSnack 1.6 was able to install and boot.

[warning] rom manager t-989 for roms [warning]

Looked urgent huh? That's because it is. I see that most people that have their phones bricked is from using ROM manager to install a rom that they downloaded onto their phone.
LISTEN TO ME WHEN I TELL YOU....
Do not use ROM manager to install a custom ROM that is not listed in the application.
I too have bricked my phone this way and I never made a back up. The quickest solution is to actually re-root your phone again by putting it back into download mode.
Look in the forums for instructions. I'm sure others can explain it better than me.
Only use ROM Manager to install clockwork mod recovery.
From there, do it the manual way. It may be more labor, but it is better than bricking your phone.
There are instructions to do that too. If you can't find it just throw me a PM.

Lol I use it all the time to flash roms never bricked
Sent from my SAMSUNG-SGH-T989 using xda premium

same here. can you elaborate why you think or provide proof that cwm is bricking peoples phones.
I have used cwm on several phones and never had any problems getting to recovery and flashing roms.

you didn't read his post. he is saying not to use Rom manager to get/install roms

Probably because rom manager only wipes data and cache at most. Most of these roms work best with a super wipe

The touch cwm is the worst. Have to toggle signature verification every time, and point it to the internal sd card. Only one brick (soft), though.
That v5 one is notoriously bad on many phones. Just buggy. Not a dealbreaker for me. Is the other touch one better?
Sent from my SAMSUNG-SGH-T989 using xda premium

He's probably referring to the roms listed in ROM manager that are not for our phone.I think there is two of them now

I think we're confusing Rom Manager with Clockwork Mod...
Rom Manager is an app made by koush, its a downloadable market app thats included with Cyanogenmod and other roms (on other phones) that makes it easy to install a ROM without bothering with booting into recovery. I used it extensively during my Nexus days, though on the t989 many roms you have to super wipe or do a lot of advanced things you can only do inside clockwork mod.
ClockworkMod is a recovery manager for your android phone, also made by Koush. The classic version that has been on all phones is the non-touch type, latest version is 5.0.2.7. You use the power button and volume rocker to navigate. There is another version dubbed ClockworkMod Touch, latest version is 5.8 something...you can actually navigate with touchscreen in this.
Many people's problems, I've experienced it too, is that CWM touch likes to reboot randomly during crucial moments (during a backup, MD5 creation, flashing a ROM...), leaving the potential for (and in some cases it actually has) bricked phones. Plus the touchscreen navigation is tempermental, its just not very responsive or accurate. Very dangerous bugs for such a sensitive area on the phone.
So do yourself a favor...use ClockworkMod, the originial. Its not going to kill you to navigate with the volume rocker and power button...it actually makes you pay attention and go slower so you don't make mistakes and push the wrong thing. Its easy to install...with Rom Manager! Download it from the market, when you open it near the top there will be a button to flash the latest ClockworkMod. It will be the non touch type.
As stated above, I wouldn't use the ROM flashing functions of Rom Manager with our phone, but it does have an easy button to reboot into recovery for roms without the option in the shutdown menu. It's the easiest way to flash CWM though.
Hope this helps.

You guys can stop "trippin" there are 2 roms under the dl section in rom manager for our phone DO NOT IN ANY WAY SHAPE OR FORM FLASH THIS TO YOUR SGH-T989!!! it WILL BRICK YOUR DEVICE!!! Somebody just needs to email koush about it so they can be removed. IMHO dl to your phone or pc and then flash away a superwipe is recommended. I for one am iffy with rom manager because it errors out on restores sometimes.
Sent from MY Juggernaut!!!

zander21510 said:
I think we're confusing Rom Manager with Clockwork Mod...
Rom Manager is an app made by koush, its a downloadable market app thats included with Cyanogenmod and other roms (on other phones) that makes it easy to install a ROM without bothering with booting into recovery. I used it extensively during my Nexus days, though on the t989 many roms you have to super wipe or do a lot of advanced things you can only do inside clockwork mod.
ClockworkMod is a recovery manager for your android phone, also made by Koush. The classic version that has been on all phones is the non-touch type, latest version is 5.0.2.7. You use the power button and volume rocker to navigate. There is another version dubbed ClockworkMod Touch, latest version is 5.8 something...you can actually navigate with touchscreen in this.
Many people's problems, I've experienced it too, is that CWM touch likes to reboot randomly during crucial moments (during a backup, MD5 creation, flashing a ROM...), leaving the potential for (and in some cases it actually has) bricked phones. Plus the touchscreen navigation is tempermental, its just not very responsive or accurate. Very dangerous bugs for such a sensitive area on the phone.
So do yourself a favor...use ClockworkMod, the originial. Its not going to kill you to navigate with the volume rocker and power button...it actually makes you pay attention and go slower so you don't make mistakes and push the wrong thing. Its easy to install...with Rom Manager! Download it from the market, when you open it near the top there will be a button to flash the latest ClockworkMod. It will be the non touch type.
As stated above, I wouldn't use the ROM flashing functions of Rom Manager with our phone, but it does have an easy button to reboot into recovery for roms without the option in the shutdown menu. It's the easiest way to flash CWM though.
Hope this helps.
Click to expand...
Click to collapse
Holy christ time to flash back to original clockworkmod. Later touch recovery.
Sent from my SAMSUNG-SGH-I727 using xda premium

Still rockin the original CWM, never saw all the fuss about the touch stuff. Manually toggling is much safer and reliable IMO

I see that people have mistaken that I was talking about not using CMW. Let me explain. CMW (Clockwork Mod Recovery) and ROM Manager are two different things. You get CMW from ROM Manager. You use CMW to flash ROMs. Some people use ROM Manager to flash ROMs instead of CMW. That's the way you get bricked. By flashing ROM's that aren't on ROM Manager. I hope this clears it up.

I was unaware people still used Rom Manager.....
Thought we upgraded to ODIN, ADB and Heimdall

ROM manager will not brick your phone! If it does get bricked it was user error! Please close this thread

the OP says it bricked his phone, yet then says he flashed back to stock LOL. If your phone is a BRICK it's dead and does NOTHING.

rsfaze said:
the OP says it bricked his phone, yet then says he flashed back to stock LOL. If your phone is a BRICK it's dead and does NOTHING.
Click to expand...
Click to collapse
There's also soft brick which can be saved. He was most likely referring to that.
Sharpie603 said:
I was unaware people still used Rom Manager.....
Thought we upgraded to ODIN, ADB and Heimdall
Click to expand...
Click to collapse
ODIN is really crappy software IMO.. Despite its uses.

Even rom manager has its uses...I wouldn't use it to flash ROMS, because often with our phones you need more wiping than just data & cache, which is all it can do before it flashes a rom. It however it can be used to easily flash CWM and for phones without the option in the shutdown menu, you can use rom manager to reboot straight into CWM.

Guy's, what he is trying to tell you is that there are 2 ROMS that can be dowloaded and installed by ROM MANAGER that WILL BRICK YOUR PHONE. They are listed as T989 roms but they are actually for the International SGS2....

sbell7105 said:
ROM manager will not brick your phone! If it does get bricked it was user error! Please close this thread
Click to expand...
Click to collapse
He's accurate about what he described in this thread. I created a similar thread (probably got deleted) yesterday about the same issue. Just because you haven't experienced bricking yours doesn't mean he shouldn't warn others.
I hard-bricked my T989 just simply trying to boot into recovery (non-touch CWM) from the Rom Manager app...and I have read similar issues. The phone goes fcuking dead.
UPS just dropped off my replacement phone today...ready to be rooted for an ICS AOSP ROM if I can find one. Done with CM7 for now.

bluepenny65 said:
H
UPS just dropped off my replacement phone today...ready to be rooted for an ICS AOSP ROM if I can find one. Done with CM7 for now.
Click to expand...
Click to collapse
There isn't one that fully works with data and audio
Sent from my SAMSUNG-SGH-T989 using Tapatalk

Need a little help

I flashed Super Galaxy Rom 1.2 the other day, not realizing it didn't have a custom recovery. I've tried everything to get one back on there, but nothing seems to work. I've read all the posts about using odin and/or heimdall to UNROOT the phone, but I really don't want to go that far. All I want is a custom recovery so I can go back to my previous rom, or another that has a custom recovery. ROM manager doesn't seem to want to flash CWM, which is the way I did it before, so I'm really kind of lost here. I have access to my Macbook, no Windows computer available. No need to unroot my phone, just want my custom recovery back that I had on SGR 1.1..

your gonna need to use odin of some sort but you can use mobil odin if you dont have access to a pc. Get it from the market and flash el26 kernal with cwm then you can flash the rom you want. You will not be able to boot into your current ics rom after flashing that kernal though untill you flash a new rom. Make sure you put the kernal in the pda slot of odin.
http://forum.xda-developers.com/showthread.php?t=1662295&highlight=el26+kernal
Thats the link for the kernals just get the one that says reccomended for flashing ics roms due to emmc bug get the el29 or el26 just make sure when you get into recovery it is version 5.0.2.7

Thanks a lot rbTrucking. I've been a flash-aholic ever since I got this thing rooted a couple years ago. I've run into this once before, is there a reason why people don't put custom recovery into their roms? I definitely want to go back to GB for the battery life and overall stability of everything.
It all worked. Thanks a ton!!

TwinsFan said:
Thanks a lot rbTrucking. I've been a flash-aholic ever since I got this thing rooted a couple years ago. I've run into this once before, is there a reason why people don't put custom recovery into their roms? I definitely want to go back to GB for the battery life and overall stability of everything.
It all worked. Thanks a ton!!
Click to expand...
Click to collapse
No problem glad I could help! The reason they dont put custom recoveries in ics roms is because the kernal source hasnt been released yet and many people were bricking trying to flash with ics recoveries.

[Q] Installing ICS CWM

I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?

mazdaspeed6 said:
I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?
Click to expand...
Click to collapse
You really should read more before hopping around like that without checking. Real risk for a brick here.
-Flash EL26 stock CWM kernel via the PDA option in ODIN/Mobile ODIN
-When phone begins reboot, Hold Power + Volume up until boots into recovery.
-Wipe data/factory, cache and dalvik cache
-Flash ROM
-Flash Gapps
-Reboot
Those are the instructions right from the developer's thread. This is an AOSP rom and it sounds like you're trying to install TW kernels.
http://forum.xda-developers.com/showthread.php?t=1662295
This is the kernel repository. It links to each kernel where you can read further and find out if they are safe for flashing things.

Seems like you've done a bunch of stuff. But you really should do a whole bunch of reading first or you will brick your phone.
My suggestion would be to use sfhub's one-click http://forum.xda-developers.com/showthread.php?t=1705730 to get to a fully stock rooted device. Then use his autoroot package http://forum.xda-developers.com/showthread.php?t=1342728 to add CWM (the lates in the package is FF11+CWM Agat I believe) then you can add Agat's latest kernel with CWM http://forum.xda-developers.com/showthread.php?t=1721065
But I would be very careful when flashing ANY ROM; use the developers prefered method. Some recommend using EL26 CWM. Some a different recovery or procedure. Be especially careful with CM9 and AOKP builds to follow the directions there.
Good luck

So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.

mazdaspeed6 said:
So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.
Click to expand...
Click to collapse
My friend some good suggestions above your post. Give yourself a day or two and do some reading prior to flashing. This way you may not end up at Sprint making up stories about why your phone wont boot up.

Let me just echo what everybody else has said, you're gotta read more. A lot more! If you're one goal is to get CNA in your phone I would recommend reading all of the very first post on that thread. They give step by step instructions.
If you need CWM there are several options to get it on your phone. Both sfhub and I have put together several one-click and automated options to get it on your phone.
One thing that hasn't been suggested yet but I would strongly encourage you to do is to read the "How Not To Brick Your E4GT" thread. It's sticked in the General section.
Good luck!

Two more things.
1) If you're going to ask for help give it a few minutes before trying something new. It takes people a minute to reply. Sometimes waiting that extra minute or two is all you need to be saved from bricking.
2) Don't be afraid to hit your thanks button for everyone who has offered advice already. I got them once for you but it might not hurt to do it again.

Is the Epic a fail when custom Rom installed? Questions? also can ICS be rooted?

Well new company gave me 20% Sprint discount and have become sick of my Tmobiles poor coverage. However I fear wimax might be sucky too here in Seattle. Anyway, long time member here and have been involved in the HTC Sensation and One forums. Both with very very stable roms and kernals.
I was excited to pick up a couple Sprint Galaxy epics and the guy at Sprint had his all rooted and claimed it was smoking fast.
However I came to this forum and see all kinds of complaints of loss of stability just from simple Root of the Epic? Also have not read any stable ICS roms and I have read all of the threads. Plus read this phone is very easy to brick under clockwork. With sensation we use Aroma and it rocks!
So before I move on, I am not looking to break rules on asking ROM questions. I simply would like some input on what ICS rom is stable and supported still as I see many devs have moved on the the sg3 here.
What kernal and radio or what you call modem is stable and how do you find what is for your phone match?
Lastly, what is safest way to ROOT and flash ROMS for this phone?
I did read the stickies but am still confused.
I may be just happy at first to simply ROOT and install the fix for Hot Spot Wi fi and go from there.
Thanks so much.
Not even sure if phones will arrive with stock ICS tomorrow or GB...
Ice

The SAFEST way to flash stock ROMs in case of emergency is using Odin.I've found both stock ROMs (GB & ICS) very stable, however I reboot my phone everyother day (windows habit).
This thread http://forum.xda-developers.com/showthread.php?t=1525495 was my starting point.

rovar said:
The SAFEST way to flash stock ROMs in case of emergency is using Odin.I've found both stock ROMs (GB & ICS) very stable, however I reboot my phone everyother day (windows habit).
This thread http://forum.xda-developers.com/showthread.php?t=1525495 was my starting point.
Click to expand...
Click to collapse
First off thank you for your reply. Interesting, I have read ODIn maybe responsible for bricking many of these phones is that incorrect? Lots of what I found seeing the people are very unstable with the custom roms so far for ICS for this phone of course stock ICS will be here soon.is there the ability to just root the phone and leave the stock ics ROM and just run the sprint hot spot mod.
Sent from my Sensation 4G using xda premium

iceshark said:
First off thank you for your reply. Interesting, I have read ODIn maybe responsible for bricking many of these phones is that incorrect? Lots of what I found seeing the people are very unstable with the custom roms so far for ICS for this phone of course stock ICS will be here soon.is there the ability to just root the phone and leave the stock ics ROM and just run the sprint hot spot mod.
Sent from my Sensation 4G using xda premium
Click to expand...
Click to collapse
Odin never causes any bricks as long as the process is not interrupted. Most of the instability is caused by user error. From my experience, all fresh (by fresh I mean wipe data/cache and format system) custom ROM installs have been rock solid stable. Also, most network issues are fixed by updating profile/prl. Official ICS is already out, it is build FF18. Stock ICS will not normally have the hotspot mod. You will have to use a hack to install it yourself. If you want a stock ICS experience, use this odin package (reset user data) to odin your phone to pre-rooted FF18:
http://forum.xda-developers.com/showthread.php?t=1721229
And here is your hotspot hack:
http://forum.xda-developers.com/showthread.php?t=1760712
Nonetheless, I see no reason why you wouldn't just save yourself the time and flash a custom ICS ROM.

Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.

revamper said:
Odin never causes any bricks as long as the process is not interrupted. Most of the instability is caused by user error. From my experience, all fresh (by fresh I mean wipe data/cache and format system) custom ROM installs have been rock solid stable. Also, most network issues are fixed by updating profile/prl. Official ICS is already out, it is build FF18. Stock ICS will not normally have the hotspot mod. You will have to use a hack to install it yourself. If you want a stock ICS experience, use this odin package (reset user data) to odin your phone to pre-rooted FF18:
http://forum.xda-developers.com/showthread.php?t=1721229
And here is your hotspot hack:
http://forum.xda-developers.com/showthread.php?t=1760712
Nonetheless, I see no reason why you wouldn't just save yourself the time and flash a custom ICS ROM.
Click to expand...
Click to collapse
Thanks, I think we are on the same page with this!
So I just loaded the FF18 Full Restore and Samsung drivers as indicated in this thread,
http://forum.xda-developers.com/showthread.php?t=1670110
I also tested after unzipping to a folder and the ODEN program comes up waiting for me to hook up phone I dont have yet till tomorrow.
I also watched this video and it seems very easy to do if this is correct process,
http://www.youtube.com/watch?v=_IL21F8Gfbs
Still some clarifying questions,
1. If my new phone comes with ICS already pushed to it. Do I simply still install FF18 to get root for the ICS rom?
2. If phone does not come with ICS will this install ICS and Root?
3. Do I need to use this or Caulkins to wipe data first before I do this process on phone out of the box new?
http://forum.xda-developers.com/showthread.php?t=1670110
Also I am little nervous reading this post from SFHUB<, Is he saying not to do the above process thru the built in Odin recovery in the phone if it comes with stock ICS in it? What does this mean???
The Epic 4g Touch has a bug in it's emmc controller that can cause the /data partition to become inaccessible/unrecoverable sometimes thanks to the wipe process when flashing from ICS recoveries... DO NOT FLASH FROM ICS RECOVERIES!!!!
7/11/12 edit: In the FF18 source Garwynn has confirmed the presence of the offending code that triggers the emmc bug (http://forum.xda-developers.com/show...1&postcount=32) meaning that it will eventually be safe to flash from ICS as long as the offending code is removed by the dev of the kernel/rom...
- Please see this (http://forum.xda-developers.com/show....php?t=1525495) thread by xST4T1K which details how NOT to brick your device... It is slightly out of date but still very relevant... if you want a more technical understanding of what this emmc bug is and why this is happening you can see Sfhub's thread in general related to it (http://forum.xda-developers.com/show....php?t=1644364 ). The OP contains all of the information that our users have been able to figure out about this bug... Be sure to thank these people, as their hard work has made it exponentially safer for all of us to flash ICS roms on our phones...
-Every ICS rom will have a flashing guide in it's dev thread, its HIGHLY suggested you read and reread the guide for the rom you want to flash and follow it EXACTLY, taking the extra time upfront to fully understand what you're about to do will save you alot of trouble going forward.
-Put simply though you will always want to ODIN or Mobile ODIN (mobile Odin is an app made by the dev chainfire, available in the play store, that allows you to preform Odin flashes from your phone without using a PC) the el26 Gingerbread kernel/recovery and flash any ICS roms from that. NEVER FLASH FROM AN ICS RECOVERY, THAT IS HOW BRICKS ARE MADE!!!! Also do NOT use Rom Manager or Touch recovery!!!!
- Currently there are some ICS recoveries that are thought to be safe to flash from thanks to the work done on the emmc bug. If one of these is included in your rom it will be noted by the dev in the rom thread, however the safest way is still just to Odin back to el26 in order to avoid any chance of bricking!
Next, once I do this FF!8 and have root and ICS. If I want to dabble in custom roms. I am guessing they are installed by CWM from file downloaded to root of SD card like normal. I do not find CWM touch for this phone anywhere. I am sure I am missing it. It seems from reading the exploit in ICS kernal is causing the bricks. So I am guessing to use SF hubs or Claukins data wipe before loading custom roms. Are we beating to the same drum here?
Will correct radio or modem be installed automtic with FF18 or custom roms? I see many threads just on modems.
Thanks and thanks for the hot spot mod.

optimummind said:
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
Click to expand...
Click to collapse
Thats what it seems from hours reading each ROM thread. Reminds me of the Sensation when GB and or ICS first leaked. Will most likely just root stock and go from there.

CWM is in the kernel. Current kernels such as chris41g's or AGAT's kernels have patched up recoveries that avoid the emmc bug, so they are completely safe. You should use calkulins format all before flashing a rom in CWM.
For odin, it wouldn't hurt to odin sfhubs wipe data/cache, but it's not necessary. As long as you use the reset user data odin package for FF18, it will take you to stock rooted FF18. Regardless of what rom your phone comes with, run that odin package. You don't need to worry about the modem either because it will install the latest one. Be sure to update your profile/prl in settings>about>system updates after.
If you want to try a custom rom, use odin to flash a kernel with cwm (agat's or chris41g's). Once you have a recovery, flash calkulins format all, and then the ROM of your choice. Modems are not installed through CWM rom zips. You'll have to flash a modem zip in recovery or odin a modem tar.

revamper said:
CWM is in the kernel. Current kernels such as chris41g's or AGAT's kernels have patched up recoveries that avoid the emmc bug, so they are completely safe. You should use calkulins format all before flashing a rom in CWM.
For odin, it wouldn't hurt to odin sfhubs wipe data/cache, but it's not necessary. As long as you use the reset user data odin package for FF18, it will take you to stock rooted FF18. Regardless of what rom your phone comes with, run that odin package. You don't need to worry about the modem either because it will install the latest one. Be sure to update your profile/prl in settings>about>system updates after.
If you want to try a custom rom, use odin to flash a kernel with cwm (agat's or chris41g's). Once you have a recovery, flash calkulins format all, and then the ROM of your choice. Modems are not installed through CWM rom zips. You'll have to flash a modem zip in recovery or odin a modem tar.
Click to expand...
Click to collapse
I was studying Sfhugs FF18 thread and it says I can do the one click root and then install option D and that puts in the FF18, with agats CWM. So is this more simple then flashing FF18 and then doing a flash for either chris or agat kernal with cwm?
Should I use Calkulins format before flashing FF18 from stock?
So when you guys flash new custom roms you have to flash current modem each time? or only if you want to have a more current one? Coming from HTC you only have to flash radio when its required to match a new base leaked. So little confused there too.
Thanks your help has been great!

iceshark said:
I was studying Sfhugs FF18 thread and it says I can do the one click root and then install option D and that puts in the FF18, with agats CWM. So is this more simple then flashing FF18 and then doing a flash for either chris or agat kernal with cwm?
Should I use Calkulins format before flashing FF18 from stock?
So when you guys flash new custom roms you have to flash current modem each time? or only if you want to have a more current one? Coming from HTC you only have to flash radio when its required to match a new base leaked. So little confused there too.
Thanks your help has been great!
Click to expand...
Click to collapse
I know I personally use Mijjahz's "GOODNESS" ROM and it runs smooth. Many mods and add ons with more added daily. I flashed agat's 2.2 kernel because I don't like the 2.3 that version 16.6.1 comes with.
I also flashed FF18 over my EL26 modem. Modems don't change between flashing I believe. Those you update yourself. A lot of folks stay on EL29 or find something that works perfectly in their area.
Sent from Konnor the E4GT.

optimummind said:
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
Click to expand...
Click to collapse
not sure what you expect from a mobile os but I couldn't disagree more.... my experance on mijjahs goodness has been better and more stable than stock in every way, hell even cm9 and aokp are extremely reliable as well if you can live without dialer codes and prl/profile updates.... no software is ever going to be 100%.... I say flash away, you won't be dissapointed
Sent from my SPH-D710 using xda app-developers app

cp320703 said:
not sure what you expect from a mobile os but I couldn't disagree more.... my experance on mijjahs goodness has been better and more stable than stock in every way, hell even cm9 and aokp are extremely reliable as well if you can live without dialer codes and prl/profile updates.... no software is ever going to be 100%.... I say flash away, you won't be dissapointed
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
QFT.
ICS ROMs are very stable at this point.

iceshark said:
Thanks, I think we are on the same page with this!
So I just loaded the FF18 Full Restore and Samsung drivers as indicated in this thread,
http://forum.xda-developers.com/showthread.php?t=1670110
I also tested after unzipping to a folder and the ODEN program comes up waiting for me to hook up phone I dont have yet till tomorrow.
I also watched this video and it seems very easy to do if this is correct process,
http://www.youtube.com/watch?v=_IL21F8Gfbs
Still some clarifying questions,
1. If my new phone comes with ICS already pushed to it. Do I simply still install FF18 to get root for the ICS rom?
2. If phone does not come with ICS will this install ICS and Root?
3. Do I need to use this or Caulkins to wipe data first before I do this process on phone out of the box new?
http://forum.xda-developers.com/showthread.php?t=1670110
Also I am little nervous reading this post from SFHUB<, Is he saying not to do the above process thru the built in Odin recovery in the phone if it comes with stock ICS in it? What does this mean???
The Epic 4g Touch has a bug in it's emmc controller that can cause the /data partition to become inaccessible/unrecoverable sometimes thanks to the wipe process when flashing from ICS recoveries... DO NOT FLASH FROM ICS RECOVERIES!!!!
7/11/12 edit: In the FF18 source Garwynn has confirmed the presence of the offending code that triggers the emmc bug (http://forum.xda-developers.com/show...1&postcount=32) meaning that it will eventually be safe to flash from ICS as long as the offending code is removed by the dev of the kernel/rom...
- Please see this (http://forum.xda-developers.com/show....php?t=1525495) thread by xST4T1K which details how NOT to brick your device... It is slightly out of date but still very relevant... if you want a more technical understanding of what this emmc bug is and why this is happening you can see Sfhub's thread in general related to it (http://forum.xda-developers.com/show....php?t=1644364 ). The OP contains all of the information that our users have been able to figure out about this bug... Be sure to thank these people, as their hard work has made it exponentially safer for all of us to flash ICS roms on our phones...
-Every ICS rom will have a flashing guide in it's dev thread, its HIGHLY suggested you read and reread the guide for the rom you want to flash and follow it EXACTLY, taking the extra time upfront to fully understand what you're about to do will save you alot of trouble going forward.
-Put simply though you will always want to ODIN or Mobile ODIN (mobile Odin is an app made by the dev chainfire, available in the play store, that allows you to preform Odin flashes from your phone without using a PC) the el26 Gingerbread kernel/recovery and flash any ICS roms from that. NEVER FLASH FROM AN ICS RECOVERY, THAT IS HOW BRICKS ARE MADE!!!! Also do NOT use Rom Manager or Touch recovery!!!!
- Currently there are some ICS recoveries that are thought to be safe to flash from thanks to the work done on the emmc bug. If one of these is included in your rom it will be noted by the dev in the rom thread, however the safest way is still just to Odin back to el26 in order to avoid any chance of bricking!
Next, once I do this FF!8 and have root and ICS. If I want to dabble in custom roms. I am guessing they are installed by CWM from file downloaded to root of SD card like normal. I do not find CWM touch for this phone anywhere. I am sure I am missing it. It seems from reading the exploit in ICS kernal is causing the bricks. So I am guessing to use SF hubs or Claukins data wipe before loading custom roms. Are we beating to the same drum here?
Will correct radio or modem be installed automtic with FF18 or custom roms? I see many threads just on modems.
Thanks and thanks for the hot spot mod.
Click to expand...
Click to collapse
you're quoting some of my new user guide here, and i haven't updated it since the OTA came out so it somewhat overstates the danger of bricking (not a bad thing really, made you read, didn't it!?) which was much easir to do before we got kernel source, since then agat63 and chris41g have been killin it in kernel development since they got ICS source... their ICS kernels are safe to flash from and can be found in the dev section, if you're on the stock FF18 rooted with stock kernel i would personally ODIN (mobile or desktop) back to EL26, and from there flash whatever custom ICS rom you like, as far as I'm aware all of the roms come with a safe kernel these days but do be sure to double check and flash one if it does not... at that point going forward should you wish to flash something else you can just do it via cwm as per usual without having to odin back to gingerbread....do note however that you can't use touchwiz kernels with AOSP roms, there asr safe AOSP kernels as well however...
edit: oops, just noticed revamper addressed most of this on the last page, to answer another one of your questions though you can try as many modems as you like and decide which one works best for you, its varies phone to phone and area to area... the modem is not at all required to match the build number of the rom, (example: may people still use the el29 modem with ICS) you can use ANY modem with ANY rom

Ive flashed this phone hundreds of times. Put your rom and any other zips you have on external card. Then to do a full clean wipe go to privacy. then factory data reset then check usb storage. You can skip this step, but this is how to get it factory fresh. Download the el26 cwm kenal. Its posted everywhere. Next open Odin go to pda and select EL26 cwm kernal. Uncheck auto reboot. Have battery cover off! Flash kernal pop battery out when it starts to boot. or says pass. then use the vol up and power combo hold them down until boot screen pops up then let off. Next flash calkulins wipe all or wipe no data. . Never brick never fail. Then flash your rom and tweaks and be happy. Ive done this driving down the road its that easy. Laptop sitting in passenger seat with odin up lol. Plus i drive a 5sp full size truck. Flashing is easy. Follow directions. There is nothing wrong with this phone just read directions if your a noob. I,ll be making multi scenario flashing youtube movies soon. Like mobile tech videos does.

Flashing is easy. Follow directions. There is nothing wrong with this phone just read directions if your a noob.
Click to expand...
Click to collapse
That's all there is to say.