Hello,
I'm new to rooting hence I'm asking this question just to be safe.
I had Installed passion 10.6 through this route. Stock-2.1>CM7 Gingerbread>10.6. Every time I just wiped cached and installed the ROM form the zip.
What I want to know is if I changed my kernel?
I was reading on the instructions to install bionix and it was mentioned that one would have to disable the lag fix etc or disable vodoo. Do I need to worry about this or should I just flash bionix rom using the zip?
I'm not even sure my question makes sense. Thanks.
If you're thinking of going from passion to bionix then you should odin back to stock just be safe. If you odin back to stock you shouldn't have worry about the lagfix.
You can check what kernel you have by going to settings->About phone->Kernel Version. (i.e. mine is 3.0.1.5-ICUP ICS-Streamline #1). But if you odin to stock, this won't make a difference as flashing bionix will also flash the new kernel they have with the ROM.
Hope I helped a little.
You have to odin to jfd with re partion checked coming from ics, miui, or cm7. The partions are different on non touch whiz roms
Sent from my SGH-T959 using XDA App
Thanks so much. Learning something new everyday.
Can't help but wonder, why are you flashing back to 2.2?
I so wish I did not have to. My battery wouldn't last on passion 10.6 and GPS wouldn't work. So for the time being I'm trying something else. Will try passion again next week(now that I'm hooked ) but I need a working phone in the next week
Related
I am unhappy with ji6, my gps and compass no longer work and i've had nothing but problems since the update. also the call waiting dial screen lag sucks. I would like to go back to my previous rom which was basically stock rooted with ji2 gps fix and accurate battery mod. I have this saved as a backup, but I am afraid to flash it. When I flashed the new ota update it bricked my phone. I was unble to load my previous backup through clockwork recovery. I had to completely wipe my data and start over. any advice on the safety of trying to flash back to my backup rom, will it conflict with the ji6 framework?
Thanks
There should be no issues at all. I assume you still have the stock kernel too... if you had an oc kernel I would go back to stock first.
just go to rom manager and click on restore, then select your old backup... should take you to cwr and reboot when done.
My first thought was to download a custom rom. I just flashed bionix 1.7 and it seems much better than stock JI6.
I would really urge doing that...
yeah, maybe i'll try bionix first, It's just that I was really happy with the way it ran before this stupid update.
I also was fond of my setup before the update. Bionix made it better again. Hope you like it, worst case go back to stock.
I will say I would make sure you can revert to stock from bionix. I have seen a number of posts with issues, but that may be from people who had the oc kernel? I can't say with certainty.
Same here, i flashed bionix (first time using bionix) I flashed bionic 1.7 w ji2 modem oc/uv no voodoo and this thing flies! Gps is fine, navigation is usable.
s15274n said:
There should be no issues at all. I assume you still have the stock kernel too... if you had an oc kernel I would go back to stock first.
just go to rom manager and click on restore, then select your old backup... should take you to cwr and reboot when done.
My first thought was to download a custom rom. I just flashed bionix 1.7 and it seems much better than stock JI6.
I would really urge doing that...
Click to expand...
Click to collapse
I tried flashing back to my backup...(stock, rooted with bat mod and ji2 gps fix) and it got stuck in the vibrant startup screen, same as when I ran the ota. I guess my previous setup is no longer an option. Before I try another rom and have to redo all of settings and apps again, I would like to try to at least get the gps working on the ota ji6. Any advice on how to do that would be appreciated. So far I have tried all of the things I was able to find in other threads...deleted gps data, made sure lbstest settings are stock, turned off wireless, etc. I still get no locks at all.
Is bionix really that good? I'm considering it. I'm on my stock rom, stock kernel.
I think i'm going to try it out.
This is my second time trying to restore a backup using clockwork and it just hangs on the vibrant screen. The first time I forgot to disable voodoo so that was the problem then, but this time I was on obsidian froyo rom and had issues where I was not able to get any data reception (3g/edge) so I figured to try and got back to stock to see if that solved the issue but no I'm stuck on vibrant screen. It went through the process of restoring then rebooting but it got suck. I am very frustrated because I can't never get it to work so what is the point of backing up stuff. I will be using odin again to restore and not use backups anymore. Just wanted to vent as I am very frustrated about this. If there is some out there that could shed some light as to why I keep getting stuck on the vibrant screen I would appreciate it.
Will be getting a replacement phone from my date issue, and yes my voice still works just not data part.
Sent from my T-Mobile G1 using XDA App
Froyo has a differnt kernel than eclair. You were trying to restore an eclair build, but you did not flash the stock eclair kernel first.
s15274n said:
Froyo has a differnt kernel than eclair. You were trying to restore an eclair build, but you did not flash the stock eclair kernel first.
Click to expand...
Click to collapse
what eclair kernel can i use for the future???
i odin back to JFD and my 3g/edge is working again i wonder why i lost it?
Probably the easiest thing to do would have been to flash a new custom rom with the kernel included, like Fusion/Bionix.
You could have flashed the stock kernel and then restored a JI6 nandroid too though I imagine. I've not tried yet. The stock kernel can be found in my signature or in the development section. I have a copy on my internal memory just in case.
Was originally typing this in the Nero thread but didnt wana add clutter..
Ok, so I've been running Nero with voodoo enabled for a little over a week with no issue. ROM was smooth and battery life was solid. Then yesterday for the sake of a little more battery life I disabled voodoo and flashed the Super IO kernel to see how it would be in this ROM. Everything was fine for a while but then they phone would freeze everytime I ran GPS Test Plus. Only thing it would respond to was hitting the power button to put it to sleep and from that it would not wake (sleep of death). I proceeded to pull the battery. Immediately after the phone fully booted I began getting endless force closes from what seemed like every single all on the phone. Pretty sure this was kernel panic yes?
So I reflashed the JL5 Voodoo kernel (posted in the Nero OP) thinking that would fix it. the force close storm stopped but the phone was still acting up freezing and still wouldnt wake from sleep. I decided then backup, factory reset, wipe cach and dalvik cache, and reflash Nero. I thought all was well but to my surprise after being on the charger all night I arrive to work to find that my battery was at 74% O_O. This is shocking due to the fact that the phone had only been off the charger for about 45 minutes and had not been used AT ALL during that time.
So my question is... Did I just have a bad flash or did flashing the Super IO kernel do some unseen damage? Checked the battery info in Spare Parts and nothing looked out of order.
I would recommend, going back to stock and reflashing nero 3 and retrying the Super IO kernel. Hope that fixes the problem.
Will do when I get home. I assume this will unroot me, right?
I remember a post from Eugene on his site that the super io kernel works best when it is flashed with a rom before that rom is booted for the first time. If you're going back to the super io kernel, you should flash your rom, then flash the kernel before your first boot. It was something about how the kernel syncs with the rom, flashing it as an after thought can cause issues.
Ginger Clone's of the World Unite! Via the XDA App
Thats weird because I flashed super io over R14 when he first released it and had no problem -_-
Same thing happens to me when i touch Eugenes work. Thought I was the only one
Sent from my SGH-T959 using XDA App
Br1cK'd said:
I remember a post from Eugene on his site that the super io kernel works best when it is flashed with a rom before that rom is booted for the first time. If you're going back to the super io kernel, you should flash your rom, then flash the kernel before your first boot. It was something about how the kernel syncs with the rom, flashing it as an after thought can cause issues.
Ginger Clone's of the World Unite! Via the XDA App
Click to expand...
Click to collapse
regP said:
Thats weird because I flashed super io over R14 when he first released it and had no problem -_-
Click to expand...
Click to collapse
I was only successful with Super IO when I flashed it after a clean rom install. It sucks, but........
This is interesting, I experienced the same type of battery loss upon flashing Nero V3 for the first time. But, I did not flash eugenes super io kernel. I just stuck with the JL5. Although, Once I did a good recondition on my battery, Things seem to be much better. I'm a stickler when it comes to battery life though lol. Whens the last time you reconditioned the battery and wiped the stats via recovery?
I wipe the stats after every flash. I don't recondition unless the battery meter is trippin because I use 3 different batteries. 2 of which are knockoffs but they last about the same as the original. I factory reset, wiped caches again and then flashed the latest Axura. To my surprise after flashes and restoring data I booted into recovery to find the jl5 voodoo kernel was still there.. so I flashed Eugene's eb-productions stock kernel and everything seems to be fine.
What happened with the fc storm WAS kernel panic right?
I spoke too soon. Battery is still draining like a mofo and now I know why. Checked spare parts battery history and it reports that the phone wont go to sleep. Ill have to try to Odin back to stock when I get home
I have a few questions though because I've never done this before.
1. I downloaded Eugene_E2_JK2 from the Bible. Is that one fine or should I flash back to a stock 2.1 ROM
?
2. Will this process unroot my phone?
3. How is flashing the stock rom with odin any different than doing a factory reset and flashing with clockwork? I'm just worried that since flashing in clockwork didn't work odin wont either.
Vibrant via XDA App
So I odin back to JK2 then flashed a fresh installation of the latest Axura. Everything went fine as far as the flashing but after first boot I went back into recovery and i think the voodoo kernel from nero was active because I had the red letters and an option to enable voodoo O_O. WTF? I disabled voodoo before i did odin. I'm pretty sure Axura doesnt come with the voodoo kernel so how it was there after i came from stock is beyond me. So I flashed the EB-Productions stock kernel which i have used on Macnut and Axura and gotten great battery life before going to Nero. The battery still seems to be draining faster. Spare Parts reports that the "time spend without sleep" is about 10 minutes less than the phones boot time. I havent touched the phone since it booted so i dont see how thats possible.
I have no idea whats going on... Any help would be greatly appreciated. Im about ready to pull my hair out..
Just ODIN back to shipping rom (remember to use pit file and check repartition) It is better to do that everytime you are changing roms with kernel......
What difference would odin to stock 2.1 make over stock 2.2..?
regP said:
What difference would odin to stock 2.1 make over stock 2.2..?
Click to expand...
Click to collapse
The stock 2.1 is the official t-mobile software as it came from the factory. Any 2.2 we have is leaked, there is no official 2.2 for us yet. Although the 2.2 you said you flashed is as close as we got to a stock froyo rom. Flashing one of the two should get you back to stock, but the 2.1 is accepted the official base by many to start from, square one so to speak. After flashing stock, before any other roms are applied, you shouldn't have the red voodoo cwm anymore.
If you do still have voodoo after flashing stock, search for Eugene's Froyo that doesn't Brick. Flash through odin with the 512 pit file, you will reboot to a recovery that doesn't work, pull your battery, set up odin with either stock 2.1 or leaked 2.2 and the pit file, boot back to download mode, and flash the stock rom, being sure this time to select the repartition check box in odin. This will remove voodoo, and is the fix for times when voodoo goes bad. After this you will be as stock as you can get, and if you need a link to the froyo that doesn't brick, let me know I'll post it.
Ginger Clone's of the World Unite! Via the XDA App
What's the difference between reconditioning and just wipeing the stats. I've wiped it through clockwork before however what's reconditioning?
Sent from my SGH-T959 using XDA App
Reconditioning is charging your battery fully then letting it run down until the phone turns off then charging it back up again. The purpose is to make the battery reading more accurate if it seems to be inaccurate.
In other news... I odin back to stock 2.2 AGAIN then reloaded Axura. All is well now. Still bugs me though that voodoo was still there after the first odin. Just dont see how that was even possible.
Thanks for all the help!
The latest axura rom comes with the voodoo kernel, so if you flashed it, you will have, or should have, voodoo recovery. That was my point about checking recovery after flashing stock to verify it was removed, if that was what you were trying to do.
Ginger Clone's of the World Unite! Via the XDA App
I previously had stock Eclair 2.1update1 and flashed through CWM to Bionix-v 1.3.1 which I'm currently running. Now I want to know if I could flash CM 7.1.0.1 directly without Odining to stock. My current CWM is 2.5.1.3 and I don't want to mess with Odin or bootloaders. Is it Ok to flash CM7.1.0.1 with CWM from my current Bionix?
Yes. When you do it, make sure you flash CM7, IT WILL BOOTLOOP, this is normal. Pull the battery, boot back into recovery and then reflash CM7 again. Essentially flashing over itself. It does this bc of a CWR mismatch.
If you are going to go to CM7, why not go to Neo's ICS? Check it out. Very smooth, little bugs, RC came out today and plenty of support (CM team dropped Vibrant so no support from them. Us yes, them no).
Woodrube said:
Yes. When you do it, make sure you flash CM7, IT WILL BOOTLOOP, this is normal. Pull the battery, boot back into recovery and then reflash CM7 again. Essentially flashing over itself. It does this bc of a CWR mismatch.
If you are going to go to CM7, why not go to Neo's ICS? Check it out. Very smooth, little bugs, RC came out today and plenty of support (CM team dropped Vibrant so no support from them. Us yes, them no).
Click to expand...
Click to collapse
Great! I'll give it a try soon.
And yes, I've been following Neo's ICS thread actually. But I'm proceeding slowly as my internet bandwidth is very limited, I live in the third world, so... For now I've got the CM7 ROM and planing to give it a shot.
Another thing I read in Neo's OP instructions is that one can get to flash his ROM going through CM7, even without flashing GB bootleaders with this route. I still can't understand the difference CM7 does make for not needing them, and I wonder why. But well... I think is one step at a time.
Thank you very much Woodrube.
Just reporting that my cm7 flashing was successful and everything went as expected. Good.
I'm now a happy cm7 user.
I'll keep an eye on ics...
hi,
I am sorry if this is a dumb question. But i have failed several attempts while shifting to ICS (RC 5 by team-nyx). Every time when i install ROM & kernel via CWM and boot the device (vibrant t959) it freezes on the screen with VIBRANT and SAMSUNG displaying WHITE on BLACK back ground.
i have gone back to JFD and tried several times BUT same result.
I was on froyo 2.2 (build UVKB5) updated via kies and did it but no luck. I followed wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and did starting from No. 03 --
downloaded Cmenard's Kernel with the ClockworkMod Recovery 2.5
Heimdall Suite 1.3.2 for windows
AND upto No. 9 under Windows ONLY: section
the CWM installs as it says (A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically. )
after that i cleared factory, cache and dalvik cache.
then I select install Zip from SD card and chose the ROM (which is from team-nyx.com/index.php/releases).
after 3% it says rebooting and vibrant shuts down and reboots.. when after I clicked the combo (vol+vol-power) to enter the CWM its not there.. so I reinstall using [heimdall flash --kernel zImage] command in PC's cmd. then after i redid the same to select from SD and then ROM installed ok.
then I selected the kerenel which was taken by same source and installation went normal..
after I select reboot from CWM it reboots and hangs on vibrant screen.
I cannot figure OUT WHAT IM doing WRONG..
Please HELP ME..!!!
thank you for your time
I am moving to 2.2 via kies after going back to stock JFD. then i will root my vibrant. after that i will install ROM manager from market. THEN i will try to FLASH to ICS RC 5 + kernel from nyx TEAM.
I dont know what is wrong.. please HELP
From what you told us it sounds right. Have you tried a different ICS rom? Give ICS slim a try. When you Odin back did you checked re-partition?
Sent from my SGH-T959 using Tapatalk 2
You should try flashing the Gingerbread bootloaders using Odin after you flash back to stock. Those bootloaders can run a Froyo ROM as well as ICS so it wouldn't hurt to do either way. After you flash the bootloader then try flashing the ROM.
And try a different ROM like iwillkillyou suggested. Slim is good, but ICZen is very solid if you're tipping your toes into ICS.
iwillkillyou said:
From what you told us it sounds right. Have you tried a different ICS rom? Give ICS slim a try. When you Odin back did you checked re-partition?
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
hi,
thank you for the reply. No i havent tried a different ROM. yes I checked repartiton when ODin Y this is happening.. I have Flashed this ROM once.. but then when someone calls me they cudnt hear me clearly.. when i initiate the call its ok.. so I moved back to JFD..:/
kaiser_bun said:
You should try flashing the Gingerbread bootloaders using Odin after you flash back to stock. Those bootloaders can run a Froyo ROM as well as ICS so it wouldn't hurt to do either way. After you flash the bootloader then try flashing the ROM.
And try a different ROM like iwillkillyou suggested. Slim is good, but ICZen is very solid if you're tipping your toes into ICS.
Click to expand...
Click to collapse
thank you for the reply.. I jz finished Updating to 2.2 via kies..ok I will flash Gingerbread bootloaders using Odin. I will try I think it wont be necessary to ROOT the vibrant..to Flash Bootloaders.. I am going to Flash the ICS ROM via ROM manager (after rooting via SuperOneclick root2.3.3)..
haarsh said:
thank you for the reply.. I jz finished Updating to 2.2 via kies..ok I will flash Gingerbread bootloaders using Odin. I will try I think it wont be necessary to ROOT the vibrant..to Flash Bootloaders.. I am going to Flash the ICS ROM via ROM manager (after rooting via SuperOneclick root2.3.3)..
Click to expand...
Click to collapse
Just so that you know, everytime you are using Kies, you are running the risk of hardbricking your device. It is notorius for that and in fact someone last week got HBricked with it.
I don't use ROM Manager and probably won't as long as I have a Vibrant. All you need to do is go back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall PAckages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Also for more detailed instructions, se my ICS install giude also in my signature.
Woodrube said:
Just so that you know, everytime you are using Kies, you are running the risk of hardbricking your device. It is notorius for that and in fact someone last week got HBricked with it.
I don't use ROM Manager and probably won't as long as I have a Vibrant. All you need to do is go back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall PAckages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Also for more detailed instructions, se my ICS install giude also in my signature.
Click to expand...
Click to collapse
Thank you for the links.. I downloaded and place CWR inside SD. Without kies can we install official releases via Odin.. is there any way.. im sorry if that is a stupid question
No stupid questions. That is why we are here. I am pretty sure there is a flashable 2.2 stock floating aroung here. I personally don't have it though. Custom 2.2's are at this point tweaked so completely out, that they will blow the doors off any 2.2 stock ROM out there. I usggest Moped_Ryder's ROMs and Fishman's Bionix-redux ROMs. Quality, fast and stable. Not ICS, but everything works and no fear of the dreaded Encryption Bug.
PM incoming btw.
Woodrube said:
No stupid questions. That is why we are here. I am pretty sure there is a flashable 2.2 stock floating aroung here. I personally don't have it though. Custom 2.2's are at this point tweaked so completely out, that they will blow the doors off any 2.2 stock ROM out there. I usggest Moped_Ryder's ROMs and Fishman's Bionix-redux ROMs. Quality, fast and stable. Not ICS, but everything works and no fear of the dreaded Encryption Bug.
PM incoming btw.
Click to expand...
Click to collapse
thank you. btw can we Flash to 2.2 via CWM .. directly selecting the ROM from SD .. without Odin
If you can find it, you should be able to. Just put on your card and flash away, taking care to wipe accordingly.
A note on flow though:
2.1, 2.2 -can go into and out of any 2.2 there is laterally.
2.3-4.0 -will need to Odin to stock before going back to a 2.2 ROM. Can move laterally from 4.0 to 4.0 though.
(i.e DO NOT try to restore a 2.2 nandroid or flash a 2.2 ROM when you are on an ICS variant. the /system is completely changed and reformatted. You need to Odin to get it back.)
Moped Ryder uploaded a semi tweaked version of the stock 2.2 build. It's a zip that you can just flash using CWR:
http://forum.xda-developers.com/showthread.php?t=1674519
It comes rooted with busybox and some other goodies, but it's the stock kernel and whatnot. I'd highly recommend Fishman's Bionix-V Mod or Moped Ryder's Slim_Ryder ROMs if you're going to be on Froyo though. They're both great, but I went with Fishman's latest Bionix Mod since I couldn't get bluetooth to work on Moped Ryder's ROM. Which is really unfortunate because I loved Moped Ryder's otherwise.
And you don't have to Odin back to stock if you're just bouncing around Froyo or Eclair builds; only if you're coming from Gingerbread or ICS (2.3 or 4.0).
Keep us updated. I'm curious to see what worked. It's probably the gingerbread loaders. But, who knows.
Sent from my SGH-T959 using Tapatalk 2
Is your Samsung Vibrant (T959) Rooted.?
iwillkillyou said:
Keep us updated. I'm curious to see what worked. It's probably the gingerbread loaders. But, who knows.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
hi.. I tried again with flashing semaphore kernel through Odin installed CWM version higher than 2.5 to install ICS RC5 by nyx --sorry i need that soo badly so didnt checked anything else ..
@that time I was on vibrant 2.2 UVKB5 (stock)
NOT rooted
I didnt had so called
bootloaders
Click to expand...
Click to collapse
(i dunno what it means though--have to search )
BUT it didnt worked for me instead freezes at Vibrant start-up screen. So i Couldnt switch back to CWM. I Odin back to JFD with repartition clicked and my vibrant was locked (network lock). Finally, I got it cleared by application named Galaxy_S Unlock by Helroz from the market.
Now I am at the very beginning again. I am now on 2.1 JFD. I dont know WHY this happening to me .. :crying:
gonna try again with GB bootloaders.. BUT Im sick of failing and going back to 2.1 (my friends who are having captivate had no problem)
Speedy5150 said:
Is your Samsung Vibrant (T959) Rooted.?
Click to expand...
Click to collapse
At the time i was trying it was NOT rooted.. But now i have it rooted because i needed to unlock the network . which happened me for the very first time after flashing back to JFD using Odin..
Thank you guys for the links and thoughts on 2.2 ROMs.. I am not that expert . Thats why i was updating to 2.2 via KIES -- which is not a good idea as it seems with the ability 2 brick the device. I am going to get Bionix-V FishmanMod V4 FULL and install as http://forum.xda-developers.com/showthread.php?t=1441976 says..
It says Boot into clockwork recovery and i think i found something to do that in this thread http://forum.xda-developers.com/showthread.php?t=734164
I have to get ROM manager from market and go through it..
BUT Im damn upset with the RC5 ICS update by nyx being unable to installed into my device.. I will try with GB bootloaders flashed ..
If you are going to go with Fish's ROM, then all you need to do is Odin back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall Packages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Fish also has a Odin package that you can flash his ROM through Odin and not have to deal with CWR.
ROM Manager is no longer supporting 2.1, so if you do go back to JFD, then it will be hard to get RM. It is out there somewhere but really all you need is the Update.zip from above to do it. I suggest that you stay on Fish's ROM for awhile and read about ICS installs and all the little things that are involved. If you do flash Fish's ROM, you don't need to mess with the bootloaders.
Btw, aside from Kies, messing with Bootloaders is one of the sure fire ways to hardbrick your device. It only takes seconds to flash them, but do it wrong and, well you know.
Good luck and ask if you have any.
Woodrube said:
If you are going to go with Fish's ROM, then all you need to do is Odin back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall Packages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Fish also has a Odin package that you can flash his ROM through Odin and not have to deal with CWR.
ROM Manager is no longer supporting 2.1, so if you do go back to JFD, then it will be hard to get RM. It is out there somewhere but really all you need is the Update.zip from above to do it. I suggest that you stay on Fish's ROM for awhile and read about ICS installs and all the little things that are involved. If you do flash Fish's ROM, you don't need to mess with the bootloaders.
Btw, aside from Kies, messing with Bootloaders is one of the sure fire ways to hardbrick your device. It only takes seconds to flash them, but do it wrong and, well you know.
Good luck and ask if you have any.
Click to expand...
Click to collapse
thanks alot for the info brother.. some guys told me STUPID.. but YOU guys are awesome.. I am a newbie to this flashing and stuff.. but learned a lot from XDA . Thanks again for the reply. now I have stock 2.1 with ROOT . (rooted cuz i had to unlock the vibrant). I will flash to Fish's 2.2 ROM soon. BTW may i ask you after moving to Fish's ROM and later if i need to move to ICS still can I do it without messing with Bootloaders..
Thank you
That is what we are here for in the Q&A/General sections.
Regaring your question about Gingerbread bootloaders being needed:::Yes and No.
Gingerbread bootloaders were required in the infancy of ICS ROMs bc they prevented what is called "Rainbows" in your clockwork where you couldn't see anything. The options were there but you just couldn't see them. Then as ICS evolved, the need for GB bl's lessened and now you don't need them at all.
But...There's always a but...Gingerbread bl's are recommended by most of the devs for ICS builds because they seem to work better with the custom recoveries that come with some of the kernels. There is more to it but in short, GB bl's are not required but recommended.
If you go to my ICS install guide, in the middle pages and more again at the end, Yosup (highly respected user) and I have a detailed conversation about bootloaders and their installation. Once he got over the fear and did it, he was hooked and flashing ICS ROMs weekly if not more. It is a very informative section of that thread.