Develop Bugs

[Q] Issues flashing MidNIGHT ROM 4.2 zip on stock eb13

Disclaimer:
I am new at this, I have read a lot and followed a lot of tutorials. I may not use terms correctly so please forgive me.
Problem:
I am trying to flash to MidNIGHT ROM 4.2 zip from stock eb13 on my Epic.
This is my first attempt at such a thing, i was able to successfully root my device via noobnl's instructions: http://forum.xda-developers.com/showthread.php?t=770388
I am able to get rom manager installed and give it SU rights, etc. I got the full rom from the developer’s autism awareness site which is the full package. I make a backup through rom manager and reboot into CWM recovery.
I clear the data/cache 3 times and proceed to update through the zip on sd card option and point it to the midnight rom zip.
It says it is successful, i reboot and I become stuck on the samsung loading screen, I let it sit for 10min just to make sure, but no dice.
I then boot it back into recovery mode and try again multiple times which it is much faster this time but they all fail to load past the samsung load screen.
I go into the CWM recovery and attempt to load my backup, which hangs at installing cache every time.
So I am left with just booting into CWM.
I then resort do using odin to get back to eb13 and I am back where I began.
Sorry for the wall of text but I am lost and have tried to read a lot so I didn’t come on here asking random questions, but I have been working on this for a long time now and figure a forum post was due.

It wont work with CWM 2.5 and RFS. It requires CWM 3.0 and EXT4
After you ODIN back to EB13 go here:
http://forum.xda-developers.com/showthread.php?t=897612
From the midNIGHT ROM first post:
ptfdmedic said:
Instructions:
1) Make sure you are Rooted with NEW CW3.0.0.6 OneClick by Dameon
Click to expand...
Click to collapse

I see now.
I used Rom manager to update my CWM to 3.0 and thought that would work with his first bullet, but I thought wrong.
I guess I dont understand RFS and EXT4, I thought rooting was rooting and noobnl's directions were the easiest for me to follow.
Much appreciated chris5h for the fast reply.
I will test this out when I get home from work.
-sgpigeon

kennyglass123 said:
Do you know how to Odin back to stock? Follow this thread for it:
http://forum.xda-developers.com/showthread.php?t=853209
Then when you restore, only restore data under advanced restore.
If you used Mybackup root or Titanium you can restore your apps from there, otherwise you should download them again from the market.
Click to expand...
Click to collapse
This is the easiest way I have found to root your phone with CWM3 and EXT4. If you don't mind using Odin I would suggest it strongly. I used it and installed Midnight ROM v4.2 and had no problems at all.

Well that was it. Thanks a lot everyone for your help. It took me like 10minutes once I had everything downloaded, much better than the hours upon hours yesterday
I officially have midnight ROM installed and I am rocking some nice speeds on my epic! Finally nice to see just what the phone is capable of.

Glad you got it. I wish people would stop using rom manager for the epic. It doesn't flash cwm
Sent From My Evo Killer!

Question re Clockword Mod Update for Samsung Epic

I tried to post this on the actual thread about this Update, but I was not allowed because I had not posted 10 times previously.
Anyway, I am new to rooting Android phones….new to android phones for that matter. I have had the Samsung Epic 4G for about a month. I have been looking into rooting the phone, finally decided to go for it. I downloaded the filre for Clockwork Mod version 3.0.0.5/6 - UPDATED FOR EB13 from this site. After doing one run of that bat file and getting stuck on the startup screen, I realized I needed to find a compatible ROM and Kernel and install them before rebooting.
I reset the phone to default settings, using the info on http://forum.xda-developers.com/showthread.php?t=909384 and then I used the kernel
from the original update thread, Default Stock Dual FS kernel For EB13, and the Bonzai ROM from their website. This time, the install worked properly, and when my phone rebooted, the firmware is listed as Bonsai/Kernel_v4.01. So I wanted to backup and uninstall some Samsung Bloatware from the phone,and as I understand it, the Titanium Backup is the best way to do it. Well, I installed it, and it has consistently said the program could not acquire root status. I clicked on the “problems” icon, got busybox and upgraded superuse, and that did not effect anything. I even reflashed the Bonzai Rom, but the end result is the same, I am still getting that same message. Since I have replaced my Rom and have installed Superuser, I have to assume I have rooted the phone, so what could be the problem here? The app SetCPU also says I do not have Root Access. So I am not sure what to do at this point.

Sounds like a failed root:
Root again with the oneclick 3.0.0.6, power off, 3 finger boot and ext4 will be put on automatically. After ext4 installs install bonsai before rebooting.
Sent from Bonsai 7.0.3

Is there a difference between onclick 3.0.0.6 and the one in the thread http://forum.xda-developers.com/showthread.php?t=897612,which is labelled 3.0.0.5/6? Because, if not, that is pretty much what I have done already.

Same one.
I would odin to eb13, odin ec05 modem, root, boot to recovery and allow ext4, flash bonsai 4.0.1. Can't remember if 4.0.1 adds ec05 modem during flash, but if it does you can skip the ec05 odin (sorrry, but my mind has been on 4.1.0 for the last week).
The odin process will get rid of the kernel you currently have. Flashing the rom doesn't do anything to the kernel. The odin process will give you a nice clean slate to workv with. If your phone wants to do an ec05 OTA update during this process please tell it later and don't do it.
Suggest you peruse the Bonsai Forum as you will find a lot of treats that will be able to help you. Http://www.bonsaigeeks.com
Sent from Bonsai 7.0.3

Top Nurse said:
Same one.
I would odin to eb13, odin ec05 modem, root, boot to recovery and allow ext4, flash bonsai 4.0.1. Can't remember if 4.0.1 adds ec05 modem during flash, but if it does you can skip the ec05 odin (sorrry, but my mind has been on 4.1.0 for the last week).
The odin process will get rid of the kernel you currently have. Flashing the rom doesn't do anything to the kernel. The odin process will give you a nice clean slate to workv with. If your phone wants to do an ec05 OTA update during this process please tell it later and don't do it.
Suggest you peruse the Bonsai Forum as you will find a lot of treats that will be able to help you. www.bonsaigeek.com
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse

This exact thing happened to me after trying everything from the EC05 OTA. Just run the bat file again on the phone...nothing else and it will work fine.

[Q] Recovery Mode Lost after flashing ROM

Maybe this is by design and I'm just missing something. I got a new e4gt and proceeded to root it using instructions found on epic4gtouchroot.com. Basically I used odin to flash a stock EL29 ROM and then install team Rogue's CWM.
All went well with this process so I proceeded to the next step, which was to download and install a custom ROM. I installed the VeNuM ICE 5.5 since I'm a comic book nerd as well as a computer geek.
This wasn't my first time rooting. I've been rooting my EVO for a year of so, and I've rooted my Wife's Nook Tablet too, so I was a bit shocked to see that the Team Rogue CWM recovery program went bye-bye after flashing the VeNuM ROM.
I downloaded ROM manager and tried to flash the latest CWM recovery program from there, but that dind't work. I haven't tried to download the touch recovery, but I was able to reinstall the Rogue CWM recovery program, which then hosed up my ROM. I actually thought I bricked my phone for a minute, but I was able to go back into Rogue Recovery and re-flash the VeNuM ROM.
All went well and I'm back into my phone, but now again when I reboot into recovery mode, I have "Android System Recovery <3e>" like an abridged version of CWM. I don't have near as many options and wonder what's going on.
I never lost my recovery mode before when flashing a ROM. Is there some sort of custom recovery included with this ROM, or am I doing something wrong?

hi. im pretty new at this also, but i think i know the answer to this. well. not really the answer, but i know how to get clockwork recovery back onto the venum rom you are using now. you need Odin3-v1.85 (just google it) and the clockwork recovery StockCWM-EL26.tar (google). Then you put your phone in odin mode, volume down and power from powered off state, run the program, check the PDA option and browse for the stockcwm file, plug in usb and hit start. That'll put the recovery back on your phone.
But as I've been reading, a lot of times, you cannot just download the rom onto the phone or sd card and flash new roms using the cwm recovery. something about the gingerbread and ics and different kernels. .... =D

Please read the "How not to brick your e4gt" or how ever it goes in general. You need to stay away from rom manager and any touch recoveries. To answer your question, rogue recovery went away because the Venum ICE rom has the stock recovery packed in because of all the custom recovery/bricking issues we've been having with ICS. So the Dev left out custom recovery included with his rom
Sent from my SPH-D710 using Tapatalk

I'm not sure what recovery Venum comes with but this might be by design since custom CWM recovery is not installed by design on most ICS roms.
First of all read through this thread: http://forum.xda-developers.com/showthread.php?t=1525495
You chose to flash ICS; if you had chosen Gingerbread this would not be an issue so please read on... ROM manager should NOT be used with ICS. Since you are new, the only CWM recovery you should be using is the stockcwm-el26 posted here: http://chris41g.devphone.org/index.php?dir=EpicTouch/Stock+Repack/EL26/
Lastly and most important:
Flashing ICS can be a very dangerous thing for your phone if done improperly. Even flashing back to Gingerbread from ICS can go wrong.
Please do not do any further flashing of ICS without reading and understanding the process of flashing ICS safely!
Also, please feel free to ask lots of questions until you are comfortable with the entire process. That is why we are here.
Edit: Sorry for the very strict tone throughout. You have a very nice WORKING phone and we see a lot of newbies flashing over to ICS without a full understanding of what can go horribly wrong. We also see users asking for help here daily because they have bricked their phone (many times with no hope for repair or recovery).

Maybe I'm just lucky?
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.

BBJon said:
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.
Click to expand...
Click to collapse
Coming in late to this thread but I would like to re-iterate what was said about ROM manager and pretty much everything tdunham said. Because you have been, so far lucky, does not mean that luck will continue. Best advice is to remove it and not use it. If you read through some more posts you will see that the bricking doesn't always happen on the first, second, third flash. It can all of a sudden appear. We've had VERY experienced developers brick their phones, so to think you won't just because you've been lucky is not wise.
But some of the comanailities are clear - using ICS recovery to wipe/restore and using ROM manager. Just thought I'd point that out.
If you're coming over from a different phone (HTC etc) check out Qbking77's videos. They are very informative too.
Good luck and have fun.

I'm glad that the op did some reading and had some extra help here. Our phones can be confusing but with extra reading it can be figured out. We try to list the kernel that's in the rom and these are all listed in the development section in some form or another with explanations of what they have, ie cwm or rogue recovery... In addition most of our roms list a change log that you can read that will tell what each version of the rom has in it in case you would rather use an older version. And we keep the older roms posted too... anyway happy flashing !

I've bricked my phone a few time messing around with different ICS roms and kernals. I go back and odin EL29 rooted...start all over from scratch. Try using new recovey kernals posted on ACS. I'm on FE22 with the ACS recovery and am having no issues with flashing zips and making backups as well restoring.
Sent from my SPH-D710 using xda premium

There are some repacked recoveries that Steady used to make for ICS before he disappeared. Those were never and still aren't safe for flashing ROMs though. It's safest to Odin/Mobile ODIN CWM EL26 tar whenever you need recovery and then flash whatever and then reflash an ICS kernel without recovery so that your phone boots
Sent from my SPH-D710 using XDA

[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.

[Q] Confused On How To Install A Recovery

I have been looking around for about an hour or two trying to find a solid tutorial on how to install a custom recovery to install new Roms. I flashed my phone onto Virgin Mobile on FH13. It seems to me that there is more than meets the eye to installing a recovery on this phone. I really don't want to mess anything up at all. Could anyone guide me the right way as to how I can get CWM on my phone? I appreciate any help you can give me. Thanks!

Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.

RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!

bongzilla said:
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1953783

RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
My phone already has root. Everything else is stock. 4.0.4, build FH13, with no custom recoveries.
I don't understand what you mean in your second paragraph with "repacked stock" or "custom tw kernel".
I am completely lost as to where I should be going. My plan is to install this rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies
How would I go around to getting this on my phone?
Also, what about this rom: http://forum.xda-developers.com/showthread.php?t=1810315
I am not sure which rom runs the fastest and most efficient. There are so many kernels for so many things, I have absolutely no idea which kernel to flash and how to flash it.
EDIT: So I have done some more reading up and I THINK I can starting to understand some of it. I assume the steps are to:
1. Install Mobile Odin Lite on my phone.
2. Flash the EL26 kernel on Odin Lite. Link to kernel: http://forum.xda-developers.com/showthread.php?t=1662295 (first kernel on the page)
3. This part I am kinda lost. Not sure if that kernel installed a new recovery or not. I assume I just reboot and go into recovery.
4. Nandroid a backup of my ICS stock that is on now? Can I even go back to this stock backup after putting on a new Rom? Which kernel would I need to install backup of stock?
5. Wipe data, dalvic, and install new Rom using instruction it came with. My problem is I want to run this Rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies and it has no instructions. I assume you just wipe data and dalvic?
6. flash Rom, then flash Gapp? It doesn't have a link for any of the Gapps, so either I have to find a link to download Gapp or that rom already comes with it? Not sure.
7. Reboot into new Rom? Not sure if I missed a step or not.
Another question I have is with the kernels. Can I just leave it on the EL26 kernel for daily use of the phone? Say I want to install maybe cm10 next, do I just keep it on EL26?
Sorry for the spam of questions. I like to be 100% certain.

Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.

RainMotorsports said:
Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.
Click to expand...
Click to collapse
Ah, I read it twice and now it makes more sense. I have a pretty good idea of what to do now.
Put rom and gapp on phone, install EL26, backup, full wipe, flash rom and gapp, rom will install new kernel for me, then just reboot.
Last question, I just want to make sure. What exactly is a full wipe on this phone. I have done plenty of full wipes on the evo 4g. I am just asking because I hear some people have problems when they do a full wipe.
I really appreciate your help. Thank you!

Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.

RainMotorsports said:
Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.
Click to expand...
Click to collapse
That clarified a lot, thanks.
So I did it all. I did a factory reset from the new kernel. did dalvic also. I installed the new rom and gapp. Problem is that once I reboot, it shows the Galaxy SII screen, then goes into a black screen. I can't turn it back on again, so I remove the battery and it can restart. Does the same thing though. I followed your instruction and http://e4gtcm.blogspot.com/p/cm9-install-guide.html
What did I do wrong? I am worried I messed up my phone completely.
EDIT: So I went back into recovery and it was now a new version of CWM. I did everything over again; factory reset, cache, dalvic, and it is doing the same thing. Boots up "Galaxy SII" screen, then a black screen. It seems to still be on in the black screen seeing that it doesn't "turn" on again. I can hold if for 15 second or so for it to reset and does the same thing. Why is there a black screen?

Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me. goo.im seems pretty slow today.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far. I can upload one of the builds I have if you think ti would help any.

RainMotorsports said:
Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far.
Click to expand...
Click to collapse
Phew! I was pretty positive that I could still get back to something working, just my paranoid self was getting tense. I got 10/28. I guess I will do 10/20. Do you know what the other updates have? I would hate to install something that isn't working its most efficient.
Again, thank you so much. You were of great help! Good luck with the weather issue. Hope you're safe!

I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im

RainMotorsports said:
I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im
Click to expand...
Click to collapse
I just got it downloaded. It is now up and running perfectly. I appreciate all your help man, thanks a bunch. I live in Washington state. So the weather wont affect me.

Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app

n1stunna84 said:
Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I assume you do the same thing as I did. Get the EL26 kernel and flash it with Mobile Odin. I would wait on someone else to confirm that though.

Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?

joshlete said:
Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?
Click to expand...
Click to collapse
You either need a kernel with built in over clock support(you'd see the CPU slider go up to 1400-1600 automatically if it was). Or a kernel that supports over locking in tegrak, which you "load over clock module" with in tegrak.
Both Kuban kernel and some of Agats kernels have built in support, mine you need to use tegrak as I have not added built in yet
You can get them all in rwilco's (awesome) kernel repository stickied in development
Sent from my SPH-D710 using xda premium