Database Info

Flashing question

I am new to the Charge but not rooting and Android. I came from the DX so the way things are done in this thing are different. Here's my question:
I am currently rooted and running a rom with a custom kernel. If I use Odin to flash the official software, will I also need to replace the kernel separately or will flashing the official software also restore the original kernel?

You will not need to replace anything, the Odin package is all in one. It will put you back to bare stock which means ROM, kernel, recovery, modem, you name it.
If you wouldn't mind helping could you link me to a rooting guide on a DX? Some general tips on rooting it would be very appreciated. My dad has one and I'd like to root/ROM it for him but i don't feel like studying up >_< Thanks!

Wrightperspective said:
I am new to the Charge but not rooting and Android. I came from the DX so the way things are done in this thing are different. Here's my question:
I am currently rooted and running a rom with a custom kernel. If I use Odin to flash the official software, will I also need to replace the kernel separately or will flashing the official software also restore the original kernel?
Click to expand...
Click to collapse
Odin will replace everything, including your kernel.

Thanks for the response. I got confused because I saw posts saying that some kernels were interchangeable but I didn't know if they meant that you would have to flash the kernel after you flash the rom or if you just flash a new rom and the kernel remains. Appreciate the response.

You have to flash kernal only on cmw versions and not all of them read the pre requisites it will tell you if the cwm version either do not or do.have a kernal included for example humble 5 cwm version I.believe u.have to flash a kernal prior to rebooting or stock recovery will over write cwm happened to me and learned my.lesson the hard way !!!
Sent from my Gummy Charged GBE 2.0 using xda premium

Okay...so flashing the stock file will also get rid of CWM, right?

[Q] Do I have to reflash stock bootloader again when switch to other rom ?

Sorry for dumb question.. as I am really novice for installing custom rom..
I read similar contents from [BIONIX BIUI] but there is no Q&A of [BIONIX BIUI] here so allow me to post here...
I was in Darky Rom and switched to FusionXII direct through CWM qithout any problem and now hope to flash BINIX BIUI...
Do I have to flash UCKL2's stock bootloader first through ODIN then should flash KJ2 based custom rom or can flash direct through CWM ???
Anything should I be careful when switching from one rom to another ??
Thanks, guys...
Pls consider I am learning step by step...

Yes you still have bootloadets
Sent from my SGH-I997 using xda premium

Loaders
Sent from my SGH-I997 using xda premium

You should avoid messing with bootloaders whenever possible.
The only reason EVER to flash a bootloader on Infuse is to transition from Froyo to Gingerbread - once you're on a Gingerbread bootloader, if you're staying with a Gingerbread ROM, keep the bootloader.

Entropy512 said:
You should avoid messing with bootloaders whenever possible.
The only reason EVER to flash a bootloader on Infuse is to transition from Froyo to Gingerbread - once you're on a Gingerbread bootloader, if you're staying with a Gingerbread ROM, keep the bootloader.
Click to expand...
Click to collapse
I had GB running. Last night I flashed Infused 1.6.0 (Froyo), and then came back to GB rom, with no issues. So I think once we are on GB, we can switch back and forth while being careful not to mess with CWM.
Or maybe I was lucky 'cos the the line in Infused 1.6.0 changelog:
"Removed recovery binary to prevent the phone from booting into green CWM"

stick with gingerbread bootloaders after you install them

I'd avoid Bionix for the time being. I've been doing this for a while and I it's taking some work to get back.. flash around with the others for a while and get some experience.. Doesn't mean you don't have good work nopco..

Ok, thanks guys...
Sorry again for novice question again..
I want to "Stick" to GB bootloarder... the problem is "HOW?"
I read through forum and found out there is no way to check whether I am in GB' bootloader or not...
Already flashed with UCKL2 Stock Rom once, so can I consider I have GB bootloader now ???
I flashed other rom such as MaxQ, FusionXII and re-flash to BIONIX without Rainbow problem so this is ok now ?
Thanks again for advice again, duds..

diablo009 said:
I had GB running. Last night I flashed Infused 1.6.0 (Froyo), and then came back to GB rom, with no issues. So I think once we are on GB, we can switch back and forth while being careful not to mess with CWM.
Or maybe I was lucky 'cos the the line in Infused 1.6.0 changelog:
"Removed recovery binary to prevent the phone from booting into green CWM"
Click to expand...
Click to collapse
During switch between one rom to another, my device also booted in "Green Recovery" then I ODIN with community kernel to get Red CWM recovery to re-flash other rom.
Did I do something wrong ??

Paxunion said:
During switch between one rom to another, my device also booted in "Green Recovery" then I ODIN with community kernel to get Red CWM recovery to re-flash other rom.
Did I do something wrong ??
Click to expand...
Click to collapse
Everyone has their way of installing roms. What's weird is I have no idea how everyone is getting different color recovery screens other than red. The only recovery I've ever had has always been red in Cwm. Simple if your on Froyo if you flash the community kernel v8 reboot into recovery, you'll be in red Cwm and can flash any rom you want without issues. You don't need to worry about changing the kernel cause most roms come with a kernel and will erase the community kernel v8. Why is this all so difficult?
Sent from my SAMSUNG-SGH-I997 using xda premium

Yes, I also though as you explained...
I have flashed GB based rom as I believe... never flashed to Froyo Rom.
So there should be no worries about bootloader or kernel.
But when I flashed BOINIX which is based on stock Kernel, things messed up with shown Rainbow affect and this was caused because I was in Froyo Kernel as I read.
Ok, so now I want to make really sure I am in GB bootloader.
Question is,
If flashed successfully to GB based Rom, bootloader is not to be concerned ??
Is there anyway to flash ONLY GB BOOTLOADER with ODIN to make sure I am on GB bootloader ?
Sorry again for dumb question again...
I am really, really newbie not only for Infuse but for ANDROID totally so need help and advice.
Thanks, Axiomkid and all...

Paxunion said:
Yes, I also though as you explained...
I have flashed GB based rom as I believe... never flashed to Froyo Rom.
So there should be no worries about bootloader or kernel.
But when I flashed BOINIX which is based on stock Kernel, things messed up with shown Rainbow affect and this was caused because I was in Froyo Kernel as I read.
Ok, so now I want to make really sure I am in GB bootloader.
Question is,
If flashed successfully to GB based Rom, bootloader is not to be concerned ??
Is there anyway to flash ONLY GB BOOTLOADER with ODIN to make sure I am on GB bootloader ?
Sorry again for dumb question again...
I am really, really newbie not only for Infuse but for ANDROID totally so need help and advice.
Thanks, Axiomkid and all...
Click to expand...
Click to collapse
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Sent from my SAMSUNG-SGH-I997 using xda premium

Axiomkid said:
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Edit: community kernel v8 works for both froyo and gb. I flash it using sgs kernel flasher from the market and then I'm able to flash gb roms without getting bootloops and other issues. You can't flash a gb kernel over Froyo cause it will cause bootloops and it won't load and you'll have to gtg to stock again.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using xda premium

@Axiomkid,
Thanks for kind advice, now I know clearly,
1) Bootloader is in the kernel so unnecessary to flash separately.
2) Community kernel V8 works both for Gb and Froyo so it will be ok to flash Community kernel v8 to get Red CWM to re-flash other GB Rom from existing GB Rom.
Another question is,
If I want to flash Froyo Rom from existing GB Rom, what is the right way to do and if flash to Froyo Rom, I am on Froyo Bootloader, right ??
Thanks again & Merry Christmas !

If you wanna go back to Froyo use Odin and flash GTG ultimate unbrick to reformat the phone back to original Froyo.
Sent from my SAMSUNG-SGH-I997 using xda premium

It is very important if you install a rom and you don't like the kernel, sometimes it can be flashed with a different kernel but chances are it will screw your phone up. I tried using a different kernel on someone's rom and I had a tint of yellow on my screen. The Devs give us a kernel that works specifically for their rom and should not be replaced with another kernel unless told otherwise. People get errors cause of this and fill up a lot of forum space asking why their phone is screwed up. You just need to read before installing a rom. Each rom includes each own set of directions.
Most kernels allow overclocking and under volting your phone, and to be honest I don't mess with the settings so I don't end up with a burnt CPU
Sent from my SAMSUNG-SGH-I997 using xda premium

Axiomkid said:
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
WRONG. DEAD WRONG.
The bootloader is a COMPLETELY different entity than the kernel.
Custom Gingerbread kernels (such as Infusion-GB and Daily Driver) have a workaround that allows operation with Froyo bootloaders.
However, working video acceleration in the latest leaks can only be obtained with a stock kernel from one of those leaks. If you flash a kernel and system image from a leak (such as UCKL2) and you get rainbows, you need to flash new bootloaders. If you don't get rainbows - you don't need new bootloaders and should avoid flashing them if at all possible.
(Basically, don't flash anything with boot.bin or sbl.bin using Heimdall or Odin once you're on GB bootloaders.)

Entropy512 said:
WRONG. DEAD WRONG.
The bootloader is a COMPLETELY different entity than the kernel.
Custom Gingerbread kernels (such as Infusion-GB and Daily Driver) have a workaround that allows operation with Froyo bootloaders.
However, working video acceleration in the latest leaks can only be obtained with a stock kernel from one of those leaks. If you flash a kernel and system image from a leak (such as UCKL2) and you get rainbows, you need to flash new bootloaders. If you don't get rainbows - you don't need new bootloaders and should avoid flashing them if at all possible.
(Basically, don't flash anything with boot.bin or sbl.bin using Heimdall or Odin once you're on GB bootloaders.)
Click to expand...
Click to collapse
Boy, I wish I read this yesterday.
I had struggled with this yesterday trying to install Bionix using heimdall.
Managd to boot loop in 3e blue recovery several times until I flashed bootloaders in heimdall to get back to a working stock.
Paxunion, if I may suggest, if you are on froyo,
I think it'll be easier for you to use Adam outler's heimdall uckj4 return to stock.
Put your phone in the download mode. Flash it once then flash it again with the bootloader checked.
Go to his second post and flash the kernel to get recovery and then you will have gb bootloader and be able to flash the ROM of your choice.
If you did want Bionix, very nice, use the heimdall package that Dani included in the bionix thread. You won't have to flash the kernel step if you use Dani's heimdall package.
Do not check the repartition or partition box with the bionix flash.

qkster said:
Boy, I wish I read this yesterday.
I had struggled with this yesterday trying to install Bionix using heimdall.
Managd to boot loop in 3e blue recovery several times until I flashed bootloaders in heimdall to get back to a working stock.
Paxunion, if I may suggest, if you are on froyo,
I think it'll be easier for you to use Adam outler's heimdall uckj4 return to stock.
Put your phone in the download mode. Flash it once then flash it again with the bootloader checked.
Go to his second post and flash the kernel to get recovery and then you will have gb bootloader and be able to flash the ROM of your choice.
If you did want Bionix, very nice, use the heimdall package that Dani included in the bionix thread. You won't have to flash the kernel step if you use Dani's heimdall package.
Do not check the repartition or partition box with the bionix flash.
Click to expand...
Click to collapse
I was wondering if anyone actually used that...
good to know it worked out. I've wanted to do a rom with stock kernel for a while but nop can do it better. just glad I could help in a way.

Dani897 said:
I was wondering if anyone actually used that...
good to know it worked out. I've wanted to do a rom with stock kernel for a while but nop can do it better. just glad I could help in a way.
Click to expand...
Click to collapse
I ran into some problem due to checking of the repartition box and screwed up everything. Had to reflashed bootloader to get the phone working again.
I found it was easiest to flash adam's uckj4. Then heimdall fronend your package.
Two steps. Simple. If i have some time, i might do a faq step guide thread in the q a

[Q] Help rooting 2.3.6?

I'm gonna make this short and simple.
I've got a stock Infuse 4G on 2.3.6 and I have no idea how to root it.
To my knowledge, SOC does not work.
How do I go about rooting my phone?

This might have already been answered, but I can't find a thread concerning it. A link would be appreciated, if possible.

with a kernel switcheroo. you need a non secure kernel to root it, fortunately the Rogers 2.3.3 kernels do boot 2.3.6. flash an older custom kernel like the hellraiser kernel through heimdall, I suggest heimdall just because its easier to extract a kernel zimage from an update than to do that but then create a .tar.md5 archive of it. you can use the ever popular entropy DD kernel but if you go back to the 2.3.6 kernel then you will have to change the vold.fstab back to stock.
the kernel flash may root the phone depending on the kernel but its an older su binary and if you update it the kernel will overwrite it on next boot.
if you want to use a custom kernel permanently then use entropy DD because it has had the root script removed allowing updates to su. though it doesn't root it will allow root through adb so soc may work after you flash that kernel. then you can update the binary through superuser
if you are gonna use the stock 2.3.6 kernel then use an old build of entropy or an old hellraiser kernel. then boot up and flash the 2.3.6 kernel back to the phone through heimdall or sgs kernel flasher. (sgs Kernel flash has the ability to find the zimage inside of a .zip or. tar even in subfolders so you can actually put the leak .tar on the SD card and flash the kernel that way if you can't figure out heimdall)

Thanks for the quick response. I'll try it tomorrow since it looks like it may take a while...

andrewpottz said:
I'm gonna make this short and simple.
I've got a stock Infuse 4G on 2.3.6 and I have no idea how to root it.
To my knowledge, SOC does not work.
How do I go about rooting my phone?
Click to expand...
Click to collapse
andrew,
did you bought the phone with stock 2.3.6 installed? what version is it? uckl2?
did you flash it with one of the unofficial GB leaks?
thanks.

ohh almost forgot about voodoo. the custom kernels convert the files system and wont allow you to flash the stock kernel, you'll get bootloops. if you don't intend to keep the custom kernel disable lagfix before you start by creating a folder with the path /sdcard/Voodoo/disable-lagfix
the V in Voodoo is capital. all other letters are lower case.
read the Rogers root thread for more details. its the same process laid out for rogers since that thread was written before soc worked on anything above 2.3.2. actually that kernel will also work on 2.3.6 for att.

Dani897 said:
ohh almost forgot about voodoo. the custom kernels convert the files system and wont allow you to flash the stock kernel, you'll get bootloops. if you don't intend to keep the custom kernel disable lagfix before you start by creating a folder with the path /sdcard/Voodoo/disable-lagfix
the V in Voodoo is capital. all other letters are lower case.
read the Rogers root thread for more details. its the same process laid out for rogers since that thread was written before soc worked on anything above 2.3.2. actually that kernel will also work on 2.3.6 for att.
Click to expand...
Click to collapse
I haven't tried this yet, Dani. Would it be possible for him to use heimdall one click defuse kernel that adam made to obtain red recovery then flash the super user fix to install SU?

andrewpottz said:
I've got a stock Infuse 4G on 2.3.6 and I have no idea how to root it.
Click to expand...
Click to collapse
No you don't... If you're on stock you're on 2.2.x (AT&T) or 2.3.3 (Rogers).
AT&T hasn't released Gingerbread for the Infuse yet.

qkster said:
I haven't tried this yet, Dani. Would it be possible for him to use heimdall one click defuse kernel that adam made to obtain red recovery then flash the super user fix to install SU?
Click to expand...
Click to collapse
yes but if he is already on gingerbread he needs a backup gingerbread kernel, if he uses cwm for the gb kernel it must already be on the SD card.
so it would be
1. download cwm flashable gb kernel to the SD card
2. download heimdall defuse kernel oneclick to PC and install drivers, I haven't done this on windows in a while but the Samsung drivers should work but heimdall also has there own system to recognize the device. forgot what its called....
3 run heimdall from run in windows or terminal in other os and put phone in download mode and connect the data cable
4. flash defuse kernel
5. boot into recovery with 3button. phone wont boot gb on froyo kernel but recovery works.
6. flash root
7.flash gb kernel
8. reboot
9. win
I used to use the mismatched kernels on the captivate. if nothing else was working I'd go back to stock 2.1, flash a froyo kernel with cwm and then flash a froyo or gb rom. 3 easy steps.

Rooting 2.3.6
Simply use the Heimdall Defuse Kernel to flash red cwm then flash the rooted version of the ROM Or a custom rom. it pre-roots your phone for you just click flash

Entropy512 said:
No you don't... If you're on stock you're on 2.2.x (AT&T) or 2.3.3 (Rogers).
AT&T hasn't released Gingerbread for the Infuse yet.
Click to expand...
Click to collapse
that's what I was wondering, Entropy.
I was thinking he meant to say he had installed one of the leaks or bought the phone with one of the later leaks like uckl2, where SOC doesn't work

qkster said:
that's what I was wondering, Entropy.
I was thinking he meant to say he had installed one of the leaks or bought the phone with one of the later leaks like uckl2, where SOC doesn't work
Click to expand...
Click to collapse
Which isn't stock...

qkster said:
that's what I was wondering, Entropy.
I was thinking he meant to say he had installed one of the leaks or bought the phone with one of the later leaks like uckl2, where SOC doesn't work
Click to expand...
Click to collapse
Yeah he clearly stated he was on 2.3.6 STOCK infuse 4g and wanted to know how to ROOT IT. Seems like its not stock to me
Sent from my SAMSUNG-SGH-I727 using xda premium

Like they say until we see pictures its not true
Sent from my SGH-I997 using XDA App

shenanigans!!

Does ICS have a kernal?

So i was just wondering but how does CM9 have a kernal if we dont have an ICS kernal?

bradman117 said:
So i was just wondering but how does CM9 have a kernal if we dont have an ICS kernal?
Click to expand...
Click to collapse
It is in the boot.img. So far all Infuse cm9 is based of jt or entropy branching off jt. If you want just the kernel, after you f flash the ROM, you can dump the kernel from bml 7 using dd commamd.
Jt recover ics is such a kernel. Check my thread for the heimdall packed.
Jscott also extracted entropies kernel and i packed into a heimdall 1 click also. I haven't had a chance to test it yet. Pm me if you want a shot at it.
I think having these kernel in a heimdall makes flashing and recovery from cm9 simple.
Dl mode. Flash. factory reset. And it's ready for cm9 ROM.

qkster said:
It is in the boot.img. So far all Infuse cm9 is based of jt or entropy branching off jt. If you want just the kernel, after you f flash the ROM, you can dump the kernel from bml 7 using dd commamd.
Jt recover ics is such a kernel. Check my thread for the heimdall packed.
Jscott also extracted entropies kernel and i packed into a heimdall 1 click also. I haven't had a chance to test it yet. Pm me if you want a shot at it.
I think having these kernel in a heimdall makes flashing and recovery from cm9 simple.
Dl mode. Flash. factory reset. And it's ready for cm9 ROM.
Click to expand...
Click to collapse
I've used your heimdal package of the ics kernel multiple times as I constantly brick my phone trying to port and have to go back to stock...I then flash the ics kernel and I'm back up and running ready for ics...I just wish I could only flash the kernel...always gotta go back to stock first...but with your heimdal I'm back up and running in no time
Sent from my SGH-I997 using XDA

As for the kernel...as far as I know it isn't a full on ics kernel...it is a gingerbread kernel that has been heavily modified to run ics however it will not work with gingerbread any longer...
So its an ics kernel created from a gingerbread kernel...insane development going on there...got tons of respect for jt and entropy getting that done...
Sent from my SGH-I997 using XDA

mg2195 said:
I've used your heimdal package of the ics kernel multiple times as I constantly brick my phone trying to port and have to go back to stock...I then flash the ics kernel and I'm back up and running ready for ics...I just wish I could only flash the kernel...always gotta go back to stock first...but with your heimdal I'm back up and running in no time
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
I don't think you need to go back to stock with system files that you will overwrite anyway.
Flash just the kernel. Wipe.
And flash the ics.
Maybe use entropy kernel flash then a jt kernel if you can't recover with only jt.

qkster said:
I don't think you need to go back to stock with system files that you will overwrite anyway.
Flash just the kernel. Wipe.
And flash the ics.
Maybe use entropy kernel flash then a jt kernel if you can't recover with only jt.
Click to expand...
Click to collapse
What do you mean by an entropy kernel flash then a jt? I've tried just flashing the jt one you have and no matter what rom I flash...when I hit that reboot button it will always boot back to recovery...
Anyways im back up and running in under 10 minutes...so its nothing to complain about...
Sent from my SGH-I997 using XDA

mg2195 said:
What do you mean by an entropy kernel flash then a jt? I've tried just flashing the jt one you have and no matter what rom I flash...when I hit that reboot button it will always boot back to recovery...
Anyways im back up and running in under 10 minutes...so its nothing to complain about...
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
I'm not sure if we're talking about the same thing but:
Let say you tried a port or build and got into a boot loop. Or lost recovery, you don't necessarily have to flash the whole stock package.
In my kernel root thread, post #3. Flash the Jt kernel in download mode. That should bring you n back to recovery from boot loop or lost recovery with the three finger combo.
I've noted that since Jt kernel has the cwm 5.xxx sometimes it doesn't do the trick. If that was the case, I would flash the entropy in download mode..post #2..in the uclb3 thread.
That will also give you cwm recovery without having to flash the whole stock base.
Boot into recovery, wipe and/or mount and you are set to flash the next experimental build. Just be sure to have a couple of different builds to test on your sdcard.
Once you flash what ever build or ROM, it had it's own kernel and system file to write over your current. In this case, it would not matter, as you are not working with a system file...only the recovery.
Edit: it would also make sense of you created a mg_lite ROM for debug if you needed to have the phone system. Make a ROM with minimal stuff. Turn off boot ani. Have only minimal apps..no email or gmail or bt fb or any crap that would allow down the boot and dalvik process. Only a few system files and libs are needed. That way you can save some time instead of going back to the whole stock process

qkster said:
I'm not sure if we're talking about the same thing but:
Let say you tried a port or build and got into a boot loop. Or lost recovery, you don't necessarily have to flash the whole stock package.
In my kernel root thread, post #3. Flash the Jt kernel in download mode. That should bring you n back to recovery from boot loop or lost recovery with the three finger combo.
I've noted that since Jt kernel has the cwm 5.xxx sometimes it doesn't do the trick. If that was the case, I would flash the entropy in download mode..post #2..in the uclb3 thread.
That will also give you cwm recovery without having to flash the whole stock base.
Boot into recovery, wipe and/or mount and you are set to flash the next experimental build. Just be sure to have a couple of different builds to test on your sdcard.
Once you flash what ever build or ROM, it had it's own kernel and system file to write over your current. In this case, it would not matter, as you are not working with a system file...only the recovery.
Edit: it would also make sense of you created a mg_lite ROM for debug if you needed to have the phone system. Make a ROM with minimal stuff. Turn off boot ani. Have only minimal apps..no email or gmail or bt fb or any crap that would allow down the boot and dalvik process. Only a few system files and libs are needed. That way you can save some time instead of going back to the whole stock process
Click to expand...
Click to collapse
Taking a vacation for memorial weekend...but I'll give what you suggested a try Monday night...if I happen to soft brick...
Sent from my SGH-I997 using XDA

solved

Ok so im planning on flashing in cyanogenmod v9.1 and then up to ultragen v1.1 with the jb and tw5 taste, now if i do this do i still need to flash in a version of gapps or is there one in the ultragen rom, and in order to do the flashing can i use the cmw-based voodoo lagfix recover 5.0.2.7 to flash in the cm9.1 or do i need to use odin or something, im kinda new to all this, all ive done to the phone so far is recover from soft brick by using odin to flash back to stock and then using some off site instructions to root the phone which also apparently came along with the voodoo recovery, so im basically a noob at this

jimmy2989 said:
Ok so im planning on flashing in cyanogenmod v9.1 and then up to ultragen v1.1 with the jb and tw5 taste, now if i do this do i still need to flash in a version of gapps or is there one in the ultragen rom, and in order to do the flashing can i use the cmw-based voodoo lagfix recover 5.0.2.7 to flash in the cm9.1 or do i need to use odin or something, im kinda new to all this, all ive done to the phone so far is recover from soft brick by using odin to flash back to stock and then using some off site instructions to root the phone which also apparently came along with the voodoo recovery, so im basically a noob at this
Click to expand...
Click to collapse
No need to flash the gapps with Utragen ROM its included.
Use CM recovery to flash no need for Odin ... cm 5.0.2.x is fine.
I always go to cm 9 then work up never had a problem.
Ultragen is a very stable ICS based rom .. I used it for awhile.
Be sure you follow the OP`s flashing instructions.
If you want JB try slim 4.1.2 its very stable...if you can live
without GPS.
Sent from my Nexus 7 using xda premium

Thanks, everythings installed and its running beautifullyi thanked your post ill mark this thread as solved