Hi guys.
I extracted the bootloaders and param.lfs from the latest AT&T Firmware, I897UCKF1 and created an OneClick ODIN package.
Flashing bootloaders is a dangerous deal but you take the same risk every single time you go back to stock using OdinOne CLick.
However, if you decide to go ahead with this method, you do it at your own risk.
I tested the package 3 times on my phone so it should be safe.
Now, you might ask why would you update the bootloaders again?
Mainly because I9000 bootloaders are not designed for I897. We've seen that there are a several differences between I897 and I9000 so is not hard to believe that having I9000 bootloaders might impact stability and even performance.
WARNING! Make sure you have a stable USB connection between your computer and your phone!
I really cant tell you how to check that, but is THE MOST IMPORTANT prerequisite.
WARNING! Key combos after flashing the bootloaders will be the same as in Froyo:
Vol UP + Vol Down + Power = Recovery
Vol UP + Vol Down + USB insert = Download
WARNING! If you have troubles connecting the phone to PC, download samsung Kies and install it to get the latest samsung drivers but make sure is not running while flashing the bootloaders.
Cyanogen MOD users, stay away!
The steps which you will need to take are as follows:
Download the package from here
Extract OneClickI897UCKF1-bootloaders.exe
Restart the phone in Download Mode
Run OneClickI897UCKF1-bootloaders.exe - with administrator permissions if on Windows 7 or Vista!
Connect the USB cable to the PC and the phone
Click "Start"
The phone will reboot by itself and you should see the ATT boot logo.
Good Luck!
Note: ANY version of Android should work with these bootloaders.
Note: Some users reported that after flashing the package, the ATT logo didnt appear but some black screen with colored points. If that happens, flash the package again.
First off, thanks for creating the One-Click package!
Did you do it with the new tool in the most recent Gingerbread leak?
Also, has anyone noticed any appreciable differences between the Captivate and i9000 bootloaders? I think it's fair to assume there must be some difference...
icezar1 said:
Hi guys.
I extracted the bootloaders and param.lfs from the latest AT&T Firmware, I897UCKF1 and created an OneClick ODIN package.
Flashing bootloaders is a dangerous deal but you take the same risk every single time you go back to stock using OdinOne CLick....
Click to expand...
Click to collapse
So after doing this will the roms like Apex 7 work with these bootloaders? Seems like that is what your are saying since any android version should work. Or will it not since it would be different framework or something? I have been on the i9000 gingers Continuum and the Apex along with the first gingerbread. I really liked Apex 2.3.4 and would be nice to have the ATT Captivate Gingerbread yet be able to use Apex. Then if this is the case we would then lose the advantage of having the awesome call quality of the audiance chip since we would have a i9000 based kernel and i897 modem. Just trying to clarify here. Thanks for your time and work.
PS. I am on DGs 1click gingerbread right now.
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
Sweet awesome work
Shammyh said:
First off, thanks for creating the One-Click package!
Did you do it with the new tool in the most recent Gingerbread leak?
Also, has anyone noticed any appreciable differences between the Captivate and i9000 bootloaders? I think it's fair to assume there must be some difference...
Click to expand...
Click to collapse
As I stated above I have been using the i9000 gingerbread roms and now trying DGs 1click and one major noticeable difference in my opinion was how CLEAR and LOUD the calls are. I guess being on i9000 froyo and Ginger roms I never really realized how much the audience chip made call sounds so much better. The downfall is no hsupa+ speeds but it did not seem too bad as I get about 2-2.5 download but only 500-1.0 upload with it. As far as smoothness and reliability I would almost say pretty damn equal.
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
Just FYI, this just *almost* hard bricked my phone.
One-Click packaged crashed while downloading "boot.bin" aka Primary Bootloader. Got the wonderful ol' "Phone ! PC" symbol.
Also of note, vol down + vol up + usb DID NOT bring be back to Download mode, like it would normally have down with any i9000 or i897 PBL and SBL combo. Luckily Vol Down + Power did bring me back to Download, and I'm back up and running. In fact, I believe that's the first time ever that I've recovered a soft-brick without using vol up / down + usb. Very odd. Just counting my lucky stars that I had a crash while using ODIN to flash "boot.bin" and I'm still alive to talk about it.
Edit: Glad to hear it's working for others, but I've NEVER had an Odin flash crash on it's own before. Makes me a little suspicious something is not right.
Just flashed over Apex 7.1 and it worked perfectly. Feels good to have the old three button combo back Thanks Cezar!
Shammyh said:
Just FYI, this just *almost* hard bricked my phone.
One-Click packaged crashed while downloading "boot.bin" aka Primary Bootloader. Got the wonderful ol' "Phone ! PC" symbol.
Also of note, vol down + vol up + usb DID NOT bring be back to Download mode, like it would normally have down with any i9000 or i897 PBL and SBL combo. Luckily Vol Down + Power did bring me back to Download, and I'm back up and running. In fact, I believe that's the first time ever that I've recovered a soft-brick without using vol up / down + usb. Very odd.
Just a warning to anyone else... Icezar1 you might want to test this package a bit more before dropping it on XDA.
Click to expand...
Click to collapse
What ROM are you running? I just flashed over COG 5b with no problems.
DG thought the boot sound had been removed but it was still there. Now it is gone as planned by DG.
RockRatt said:
As I stated above I have been using the i9000 gingerbread roms and now trying DGs 1click and one major noticeable difference in my opinion was how CLEAR and LOUD the calls are. I guess being on i9000 froyo and Ginger roms I never really realized how much the audience chip made call sounds so much better. The downfall is no hsupa+ speeds but it did not seem too bad as I get about 2-2.5 download but only 500-1.0 upload with it. As far as smoothness and reliability I would almost say pretty damn equal.
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
Click to expand...
Click to collapse
That however is due to Modem + Kernel + ROM. Not bootloader.
xpakage said:
What ROM are you running? I just flashed to COG 5b with no problems.
DG thought the boot sound had been removed but it was still there. Now it is gone as planned by DG.
Click to expand...
Click to collapse
Was running Continuum 5.6 v/ Talon Test build and Voodoo Lagfix enabled.
It's possible it was just a fluke, but after hundreds of Odin flashes off of my archived One-Click copies, I just find it unlikely. Then again, we humans due have a bias to find causality in not nessecarily related events...
Shammyh said:
Just FYI, this just *almost* hard bricked my phone.
One-Click packaged crashed while downloading "boot.bin" aka Primary Bootloader. Got the wonderful ol' "Phone ! PC" symbol.
Also of note, vol down + vol up + usb DID NOT bring be back to Download mode, like it would normally have down with any i9000 or i897 PBL and SBL combo. Luckily Vol Down + Power did bring me back to Download, and I'm back up and running. In fact, I believe that's the first time ever that I've recovered a soft-brick without using vol up / down + usb. Very odd. Just counting my lucky stars that I had a crash while using ODIN to flash "boot.bin" and I'm still alive to talk about it.
Edit: Glad to hear it's working for others, but I've NEVER had an Odin flash crash on it's own before. Makes me a little suspicious something is not right.
Click to expand...
Click to collapse
Your flash didn't take. Thats the i9000 loader combo for dl mode. Also, I flashed this twice and had no problems. A lot people flashed this with no problem.
mrhaley30705 said:
Your flash didn't take. Thats the i9000 loader combo for dl mode. Also, I flashed this twice and had no problems. A lot people flashed this with no problem.
Click to expand...
Click to collapse
I'm aware of the button combos. Yet if the "flash didn't take", why would it boot to the "Phone ! PC" screen?
Well, if it works for everyone else, it must have been a fluke. No other way around it.
Shammyh said:
That however is due to Modem + Kernel + ROM. Not bootloader.
Click to expand...
Click to collapse
Cog 5 is KF1 based, right? Same bootloaders, different rom.
Shammyh said:
I'm aware of the button combos. Yet if the "flash didn't take", why would it boot to the "Phone ! PC" screen?
Well, if it works for everyone else, it must have been a fluke. No other way around it.
Click to expand...
Click to collapse
Your data cable may be going bad.
Shammyh said:
Just FYI, this just *almost* hard bricked my phone.
One-Click packaged crashed while downloading "boot.bin" aka Primary Bootloader. Got the wonderful ol' "Phone ! PC" symbol.
Also of note, vol down + vol up + usb DID NOT bring be back to Download mode, like it would normally have down with any i9000 or i897 PBL and SBL combo. Luckily Vol Down + Power did bring me back to Download, and I'm back up and running. In fact, I believe that's the first time ever that I've recovered a soft-brick without using vol up / down + usb. Very odd. Just counting my lucky stars that I had a crash while using ODIN to flash "boot.bin" and I'm still alive to talk about it.
Edit: Glad to hear it's working for others, but I've NEVER had an Odin flash crash on it's own before. Makes me a little suspicious something is not right.
Click to expand...
Click to collapse
I am not sure why would you have this problem. Did you take in consideration the possibility of having corrupted /lfs previously? If this flash would fail, then your phone would be totally dead right now
mrhaley30705 said:
Cog 5 is KF1 based, right? Same bootloaders, different rom.
Click to expand...
Click to collapse
I was asking for practical differences between the i9000 and i897 bootloaders. The poster referenced call quality/sound and attributed it (perhaps by inference) to the different bootloaders.
I was simply pointing out that the Audience chip working or not depends on the ROM/Kernel/Modem pairing, not the bootloaders.
Boot goes vaguely like this:
iROM -> PBL "boot.bin" -> SBL "sbl.bin" -> Kernel -> Android.
The audience chip support doesn't really come into play until the kernel.
icezar1 said:
I am not sure why would you have this problem. Did you take in consideration the possibility of having corrupted /lfs previously? If this flash would fail, then your phone would be totally dead right now
Click to expand...
Click to collapse
Don't see why, considering if the params were corrupted I probably wouldn't even see the boot logo image during PBL/SBL booting. And yes, I found it odd as well, seeing as a boot.bin fail should result in a "hard" brick.
Eh, just tried it again after a fresh flash and it worked. So who knows? I'm happy to just chalk it up to gremlins and move on.
RockRatt said:
So after doing this will the roms like Apex 7 work with these bootloaders? Seems like that is what your are saying since any android version should work. Or will it not since it would be different framework or something? I have been on the i9000 gingers Continuum and the Apex along with the first gingerbread. I really liked Apex 2.3.4 and would be nice to have the ATT Captivate Gingerbread yet be able to use Apex. Then if this is the case we would then lose the advantage of having the awesome call quality of the audiance chip since we would have a i9000 based kernel and i897 modem. Just trying to clarify here. Thanks for your time and work.
PS. I am on DGs 1click gingerbread right now.
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
Click to expand...
Click to collapse
Bootloaders have nothing to do with framework so you may run any rom after flashing this pack.
And to answer your other questions, I am not sure what you mean by having the the captivate gingerbread and being able to use a custom rom. I guess the only way to have a captivate gingerbread and the rom which you prefer is that rom to be build from a Captivate GB.
I am not sure how awesome is the call quality on captivate original roms compared to i9000 ones but i wouldn't trade some assumed better voice quality on HSUPA. This is not only a phone after all. Most of us use it less than 20% for calls and more than 70% for browsing and playing
Shammyh said:
Don't see why, considering if the params were corrupted I probably wouldn't even see the boot logo image during PBL/SBL booting. And yes, I found it odd as well, seeing as a boot.bin fail should result in a "hard" brick.
Eh, just tried it again after a fresh flash and it worked. So who knows? I'm happy to just chalk it up to gremlins and move on.
Click to expand...
Click to collapse
Probably Leprechauns, Gremlins would have done a lot more damage
So after doing this will the roms like Apex 7 work with these bootloaders? Seems like that is what your are saying since any android version should work. Or will it not since it would be different framework or something? I have been on the i9000 gingers Continuum and the Apex along with the first gingerbread. I really liked Apex 2.3.4 and would be nice to have the ATT Captivate Gingerbread yet be able to use Apex. Then if this is the case we would then lose the advantage of having the awesome call quality of the audiance chip since we would have a i9000 based kernel and i897 modem. Just trying to clarify here. Thanks for your time and work.
PS. I am on DGs 1click gingerbread right now.
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
Click to expand...
Click to collapse
Bootloaders have nothing to do with framework so you may run any rom after flashing this pack.
And to answer your other questions, I am not sure what you mean by having the the captivate gingerbread and being able to use a custom rom. I guess the only way to have a captivate gingerbread and the rom which you prefer is that rom to be build from a Captivate GB.
I am not sure how awesome is the call quality on captivate original roms compared to i9000 ones but i wouldn't trade some assumed better voice quality on HSUPA. This is not only a phone after all. Most of us use it less than 20% for calls and more than 70% for browsing and playing
Click to expand...
Click to collapse
I guess what I was trying to ask is kind of answered already but was trying to confirm that as long as we have these captivate TB loaders installed we CAN STILL run apex with it and not have issues with weird colors upon boot like you see when someone came from a 2.2 rom and did not flash the i9000 bootloaders. I also was not trying to say anything about the bootloaders affecting the sound quality. I know it is a trade off between the hsupa speed or call quality. I would be awesome if we could have both but I know that wont happen. Was just trying to comment on one or the other as far as pros and cons of each.
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
Related
It's really a shame to start off in a place with a post that has someone mad at themselves for performing a soft brick on their relatively new Verizon Samsung Fascinate. I have to admit I love the phone, but after seeing some videos about DarkyMod I was so impressed I felt compelled to try it.
All I've done, far as I know, is Rooted the phone, but I also used Odin and apparently flashed the incorrect kernel. So what happens now is when I power on my Fascinate, I get a Galaxy S (GT-i9000) screen. At this point, the phone reboots. I know I'm an idiot for having used the wrong Odin kernel, but after attempting to decipher the post in the Darky's installation for "first timers" I apparently choose the incorrect kernel.
At any rate, I suppose I could ask for an experienced modder for the right kernel, the one that would allow me to perform the flash after I had installed the ROM Manager, etc.. But I doubt that would help. What I'm looking for is a file which has been removed from the forums here, and was originally in someone's Dropbox account.
I believe that the file that I'm looking for is the "Stock-i500-VZW-Kernel.tar.md5"... I might be incorrect, as I had mentioned I believed I had successfully "rooted" the phone, but when I used Odin to flash the kernel, I think that's where I went wrong. Can anyone help me find this file? Or should I get the modified kernel, which will allow me to perform the backups and then the flashing to this mod? Thanks ahead of time, I do apologize for the length of the post.
-
T.C.
Samsung Fascinate (Verizon) DL09
http://forum.xda-developers.com/showthread.php?t=867648
thats full d101 thread
http://forum.xda-developers.com/showthread.php?t=885262
thats full dj05 thread
both should be able to get you back to stock through odin then you can restart what you did. personally i keep both handy since i already had to use them due to an error that cause the phone to freeze up completely at the samsung logo. hope that helps
Thank you kdaz!
I'll give that download a shot real fast and see what happens. I'm assuming you've modded/rooted your Samsung Fascinate? Which of those Odin kernels did you use to successfully start changing things? I never did get past the "update.zip" part, it always came back with an error.
Thanks for taking the time to write a response, I really feel bad to post and have my first ever be a soft bricked phone, haha!
Quick thank you...
After looking all over the forums here, and elsewhere... I did find what I was looking for, though I didn't manage to restore the kernel and save my settings, I did unbrick the phone by reapplying the DL01 firmware with the Odin software. The forums here were a huge help, and I just wanted to say thanks!
haha glad you got it working. yes i have rooted and modded mine. got it last thursday brand new and was modding it on friday when i got back from vacation. friday night i feared that i had totally bricked it but luckily found both of those files on the forums. i believe i used the dl05 one then imediately updated to the dl09 radio and now running blaze voodoo kernel clocked at 1.2ghz and i honestly forget what rom lol waiting to use aosp
Thank god these phones are so easy to unbrick with Odin. Almost impossible to truly brick, though sometimes you might lose some data here and there or it won't save your data etc. That's why you might need to odin the full stock rom more than once
Thanks for the responses guys, kudos!
I had really hoped to start using Darky's ROM but it turned out that I didn't have the right modem file, or at least, that's what Darky said. At any rate I was kind of curious which custom ROMs you guys are using and why? The names alone should be sufficient, there's so much information here on these forums.
I admit I'm worried to reflash but at the same time, I know how to do it and if something goes wrong I just use Odin and apply DL01, or whatever the original ROM is called. Any thoughts about good and fast custom ROMs on the VZW Fascinate, guys?
Look for the full DL09 Odin, DI01 is really old and DJ05 was killed inside VZ before it was ever released to the general public.
As you have discovered, the Fascinate is its own animal and you cannot flash stuff made for other Galaxy S phones to it unless you feel like breaking your phone on purpose. Most of us are running one derivative or another of DL09 that has been hacked up in various ways to remove the stock bloatware, add root/themes, add new functionality into the kernel, etc. Some of us are using AOSP or CyanogenMod froyo-based roms which (still) have many/most things broken. We are finally about to have official updates to 2.2 and that is the missing piece that was needed to get full custom development working. Big changes will be coming before we know it.
[email protected]
I had just read earlier that there was a Froyo leak, I'll be really curious to see whether or not it speeds things up or not. It sounds like the custom ROMs are here for our VZW Fascinate but what I'm really looking (and waiting for like everyone else) is just Froyo. I'm grateful to everyone here who reached out and helped.
I'm not sure if my rooting days are done, but I got pretty scared when I thought I'd bricked this thing. Can't thank you guys, and the community, enough.
im currently running OTB ul1300 kernel which has the voltage turned down and processor speed of 1.3ghz and im currently running the dl09 supah clean rom. was running kaoscinate yesterday but missed being able to use my camera. the flashablility of this phone is great..i love just switching roms and kernels almost completely at will. cant wait until they get the leaked froyo out to use but im enjoying trying everything else until then.
tclore77 said:
I had just read earlier that there was a Froyo leak, I'll be really curious to see whether or not it speeds things up or not.
Click to expand...
Click to collapse
If you really want a boost in your phone speed, you should look into getting custom ROMs and kernels, not Froyo. There are a bunch of kernels out there that are overclocked (and even undervolted, to save battery life too) that will significantly improve your performance.
The best thing you can do with your phone is to get yourself a custom ROM - something like Blackhole 3.0 by sonofskywalker or SuperClean 0.4. Those will get rid of the bloatware crap that Verizon puts on your phone, and (more importantly) change the default search from that P.O.S. Bing back to Google.
So I got the Vibrant the other day and for the most part I absolutely love the phone. Feels like I'm holding a light sabre or a magic wand. The thing is just so powerful. I have been reading up as much as possible on how to flash ROMs and root. A month ago I'd never even heard of this stuff and now I feel like I at least have a basic knowledge....just don't have the balls to attempt it yet. I want to make sure I know what I'm doing.
So in the meantime (while I work on growing a pair and actually doing it) I want to update to the Tmob 2.2 froyo official. I have read that if I do this I won't be able to get in download or recovery mode. Is this correct? And if this is correct then does that mean it will be impossible to flash roms after updating?
I just want a little performance boost and have my system a little snappier til I decide if I'm gonna flash some roms or not. Anyone know the answer?
Thanks fellas
If you can muster the balls to get the official 2.2, just flash team whiskey s bionix. Its better, easier, more reliable, better supported, and looks cooler. Don't be scared, follow directions and its easy!! GL!
Sent from my SGH-T959 using XDA App
In all seriousness, you're far better off flashing the latest Bionix-v than you are the "official" 2.2. Having done both, you are far more likely to have an issue during the update process using that garbage mini Kies program than you are rooting and flashing. I rooted and flashed 4 different ROMS without issue. Then I used ODIN to go back to stock because I wanted to see the official release.
4 hours later I was able to get my phone back to a usable state. Between driver issues and crappy software (Kies), it just wasn't worth it. And after using my buddies Vibrant that was running the official release, it was way slower and less usable than most of the latest ROMS offered here.
You should root and then flash the latest Whiskey or Axura ROM and be done with it. The devs here have given us a far better experience and options on our phones than Samsung has.
Actually, the official 2.2 tmo update got rid of the hardware lock for me. I couldn't get into recovery or download mode out the box. The previous JI6 update through Kies mini didn't help. Since I am no longer hardware locked, I'll probably flash some roms. I am pretty dissappointed with this official update after that long wait.
I agree with the other comments that just getting one of the better/faster ROMs here is going to be what you want. As for your question about getting the "official" update and then being able to flash, that's what I did so it should work for you with just a little reading.
I disagree...I love team whiskey and all the other custom roms and even used them for a long time. But right now I have been using stock 2.2 ka7 with voodoo kernel and it is really fast and snappy. I like the stock look as well and haven't experienced any bugs or slowdowns since I installed this rom ...my suggestion: if you want stock....then read up a bit and Odin to ka7...mini lies is the worst program invented and it only flashes you to ka6
Sent from my SGH-T959 using XDA App
Don't download the official! Take your time, read a lot, grow a pair and then execute! You'll be alright. confidence comes from research and doing. Everyone was nervous at one point.
Sent from my SGH-T959 using XDA App
tmo throws people in jail for flashing custom roms making our phones super amazin and they dont want that so remember to odin back when u bring ur phone for warranty
Yaz75 said:
In all seriousness, you're far better off flashing the latest Bionix-v than you are the "official" 2.2. Having done both, you are far more likely to have an issue during the update process using that garbage mini Kies program than you are rooting and flashing. I rooted and flashed 4 different ROMS without issue. Then I used ODIN to go back to stock because I wanted to see the official release.
4 hours later I was able to get my phone back to a usable state. Between driver issues and crappy software (Kies), it just wasn't worth it. And after using my buddies Vibrant that was running the official release, it was way slower and less usable than most of the latest ROMS offered here.
You should root and then flash the latest Whiskey or Axura ROM and be done with it. The devs here have given us a far better experience and options on our phones than Samsung has.
Click to expand...
Click to collapse
The only time you'll have an issue is if you're too dumb to turn on debug mode. And most of those people who are too dumb to do that were likely too dumb to read the threads where it was repeated ad nauseum to turn debug mode on...
Turn on Debug Mode
Update
Format Internal SD
Factory Reset
Enjoy.
N8ter said:
The only time you'll have an issue is if you're too dumb to turn on debug mode. And most of those people who are too dumb to do that were likely too dumb to read the threads where it was repeated ad nauseum to turn debug mode on...
Turn on Debug Mode
Update
Format Internal SD
Factory Reset
Enjoy.
Click to expand...
Click to collapse
Well thank goodness you aren't talking about me because I did have debugging mode turned on! And then mini Kies started to update the firmware, then it decided to crap the bed at about 75% and turned the phone into a confused jumble of uselessness.
But I guess you were there so I'll let you tell everyone how I recovered it.
bartek25 said:
tmo throws people in jail for flashing custom roms making our phones super amazin and they dont want that so remember to odin back when u bring ur phone for warranty
Click to expand...
Click to collapse
What the heck are you talking about?!
So thanks to some of the competent answers from guys in here and a leap of faith and trusting my extensive research (I read way too many threads about rooting, flashing, odin, custom roms, etc..), I am now rooted and have backed up my system. To be honest I'm almost just happy with that. While completeing this process I ran into a few questions that I didn't have the answer for mainly revolving around wheter to reboot or reinstall from recovery mode whether it be clockwork or samsung.
I posted a question in the Q and A forum about it (so I apologize for the kinda double post but this is more of a update on my progress) but whats the deal with update.zip file? I don't know when to reinstall it from recovery and when to delete it once the phone has booted. Should I delete it every time I have booted back up or does it even matter?
Thanks guys. I'm the kind of guy that, once I have the knowledge I am just as willing to share. Hopefully a year from now I'll be in your shoes and able to help others.
Next up after the update.zip question is resolved in my mind I plan to flash to bionix v. Official froyo 2.2 be damned lol
You use Clockwork Recovery to backup or flash anything. Sometimes you will get the Samsung recovery and you'll need to select reinstall packages to get to Clockwork. Sometimes you'll even need to reinstall packages twice.
Leave the update.zip on your sd. That's a necessary file for Clockwork.
..
Dont believe the current methods of rooting supports EA28. Why dont you flash EB01 roms as those are pre-rooted. (Along with modem)
..
rubenhan said:
http://forum.xda-developers.com/showthread.php?t=948679
can i just use this method even if it's not rooted?
Click to expand...
Click to collapse
No, you will need to be rooted as it uses CWM.
Try this:
http://forum.xda-developers.com/showthread.php?p=11410537
It will use Odin instead of CWM, also pre-rooted.
My phone udated to EA28 right after I got it and I had a little trouble getting it rooted as well. What ultimately helped me was this:
http://forum.xda-developers.com/showpost.php?p=10601576&postcount=1
Specifically the part where he says
I have found that the stock Samsung kernel is very sneaky and replaces clockwork on the next reboot...it seems to be most common with those who have updated using Verizon's OTA updates. Odin users usually do not see the issue and hence, was tough to track down.
So to alleviate this, please add an extra option to your list of things to do. On FIRST boot into clockwork recovery, please flash your appropriate kernel of choice. For simplicity, I have added a rather plain kernel (non-voodoo) for those who may want to flash their choice of kernel later. This must be done for those who have this problem, no matter if clockwork is red or green.
Click to expand...
Click to collapse
There is a link to a kernel to flash before rebooting your phone. Worked for me.
By the way, I have just recently come from a Motorola Droid where I've been flashing ROMs for the past year. This phone does seem slightly more difficult, but so far (almost two weeks in) I'm really pleased with it. I'm currently running Super Clean 2.4 with VooDoo.
Good luck!
...
Really odd timing for this one, for me personally anyway. I finally gave up waiting yesterday and tried to install CM7 and bricked my phone. Panicked for a while, then finally figured out forcing download mode with VOLUP+VOLDOWN, connected to USB, while inserting the battery!
Anyway... it's now on Kies for Telus Fascinate. I was hoping this would finally fix GPS, but it's somehow made it completely unusable for me. 0 satellites after several minutes of looking.
Firmware version 2-3-3
Baseband version 2-6-35-7-T959TLKG2
Kernel version 2-6-35-7-T959TLKG2
sj0829-kwon-SEP-08 #2
Build number GINGERBREAD-LKG2
^^^ had to replace decimals with hyphens to appease the "no links posted by newbies" forum rule.
Also, superoneclick can't root this one. Other options?
UPDATE: Root instructions here - [Telus Only][How-To] Root your Fascinate Gingerbread 2.3.3 T959TLKG2
tenthousandfeet said:
Also, superoneclick can't root this one. Other options?
Click to expand...
Click to collapse
I tried flashing Semaphore 1.5 - which is an i9000 kernel for stock JVR - and it wouldn't boot. Went back to LKG2 un-rooted for now.
I'm tempted to try CF-root for the i9000s, but given my recent bricking(s) I'm a bit tired of flashing back to 2.2. Anyone else care to try?
Though it wouldn't necessarily help with root - do you suppose zacharias.maladroit's Neo kernel would work with stock Gingerbread? Supposedly for CM7, but Gingerbread seems close enough.
tenthousandfeet said:
I'm tempted to try CF-root for the i9000s, but given my recent bricking(s) I'm a bit tired of flashing back to 2.2. Anyone else care to try?
Though it wouldn't necessarily help with root - do you suppose zacharias.maladroit's Neo kernel would work with stock Gingerbread? Supposedly for CM7, but Gingerbread seems close enough.
Click to expand...
Click to collapse
so did u try it after?
Trying to root my Girlfriends phone, unfortunately, the gingerbreak exploit has been closed and the 3e recovery won't install unsigned ZIP files.
None of the custom kernels flashable through odin are going to work properly either. you will either end up with an unbootable device, or wonky buttons.
I'm not going to try anything until an odin flashable of the stock kernel is available.
Things like this make me glad I moved my personal phone to the the Nexus lineup.
I guess we wait for the next exploit to be found
Most people who try to install this are getting errors as soon as kies tries to update the phone, where it instantly shuts down and reports numerous signature errors.
Add that you can't root and I think it's borked all around. Thanks for nothing Telus.
harjon said:
Most people who try to install this are getting errors as soon as kies tries, where it instantly shuts down and reports numerous signature errors.
I think it's borked all around. Thanks for nothing Telus.
Click to expand...
Click to collapse
why blame Telus? It is samsungs fault.
Sent from my Nexus S
harjon said:
Most people who try to install this are getting errors as soon as kies tries to update the phone, where it instantly shuts down and reports numerous signature errors.
Add that you can't root and I think it's borked all around. Thanks for nothing Telus.
Click to expand...
Click to collapse
I installed this update yesterday with no problems. Then I tried a rooted i9000 kernel which didn't work, so I had to flash back to 2.2 and update AGAIN via Kies. No problems.
Matridom said:
None of the custom kernels flashable through odin are going to work properly either. you will either end up with an unbootable device, or wonky buttons.
I'm not going to try anything until an odin flashable of the stock kernel is available.
Click to expand...
Click to collapse
The CF-root kernel link I posted earlier should theoretically work, as long as it's bootable. The kernel applies root, which remains even if another kernel is flashed. If it's bootable with wonky buttons then we could then flash another kernel to fix the button mappings. The problem, of course, is that there are no 2.3.3 kernels for the Telus Fascinate, except zacharias.maladroit's Platypus Neo (linked above) which is designed for CM7/MIUI and may or may not play nice with stock Gingerbread.
As I said, I'm sick of reflashing to stock with no backup, so I'm opting out of trying this route. Anyone more adventurous care to give it a try?
tenthousandfeet said:
Really odd timing for this one, for me personally anyway. I finally gave up waiting yesterday and tried to install CM7.
Click to expand...
Click to collapse
Thats hilarious, I installed CM7 yesterday as well. I'm about to Odin back to stock and then update to see how this is. CM7 is a little bit to buggy for me atm.
Does this mean anything for verizon fascinate users?
uzumaki82 said:
Does this mean anything for verizon fascinate users?
Click to expand...
Click to collapse
Nope.
Sent from my Nexus S
Cool. Quick question, does an update through Kies do the Kernel and ROM together? And will a currently installed custom Kernel mess with the update? Thanks!
IronStomach said:
Cool. Quick question, does an update through Kies do the Kernel and ROM together? And will a currently installed custom Kernel mess with the update? Thanks!
Click to expand...
Click to collapse
Yes, the update will overwrite the current rom and firmware. As to your current kernel messing with the update, it depends, I used the stock kernel w/ voodoo and I could update. First I disabled lagfix and root just to be safe.
MrManiacNF said:
Yes, the update will overwrite the current rom and firmware. As to your current kernel messing with the update, it depends, I used the stock kernel w/ voodoo and I could update. First I disabled lagfix and root just to be safe.
Click to expand...
Click to collapse
You disable voodoo and unroot the phone before making the upgrade?
How did you disabled the voodoo and unroot the phone?
johnelway said:
You disable voodoo and unroot the phone before making the upgrade?
How did you disabled the voodoo and unroot the phone?
Click to expand...
Click to collapse
Boot into clockwork recovery (VOLUP+VOLDOWN held while powering on) and there will be a menu for Voodoo with an option to disable. It's probably a good idea to disable it, as everything I've read seems to indicate that new roms with voodoo enable may create problems.
As for root - I can't see that having any effect on flashing a Kies update, but there is an option in superoneclick to unroot.
tenthousandfeet said:
Boot into clockwork recovery (VOLUP+VOLDOWN held while powering on) and there will be a menu for Voodoo with an option to disable. It's probably a good idea to disable it, as everything I've read seems to indicate that new roms with voodoo enable may create problems.
As for root - I can't see that having any effect on flashing a Kies update, but there is an option in superoneclick to unroot.
Click to expand...
Click to collapse
I reflashed back to the stock 2.2 Kernel/ROM just to be safe, and so far the update's great, way faster than before even without Voodoo enabled.
Others are reporting issues with trying to root on 2.3 so I would leave it rooted.
tenthousandfeet said:
Boot into clockwork recovery (VOLUP+VOLDOWN held while powering on) and there will be a menu for Voodoo with an option to disable. It's probably a good idea to disable it, as everything I've read seems to indicate that new roms with voodoo enable may create problems.
As for root - I can't see that having any effect on flashing a Kies update, but there is an option in superoneclick to unroot.
Click to expand...
Click to collapse
Sent from my SGH-T959D using XDA App
I have 2.3 stock rooted, useing the speedmod kernel/stock kernel method on here. I ain't had any problems at all.
As for the speed of the rom, I agree. Its double the speed of froyo, and there is no voodoo. So I can't wait till there is a voodoo or somthing available, I would maybe have to tie it down.
Maniac
Need some help with VooDoo sound. I have Bionix v and DoW 221 and I installed VooDoo control. VooDoo control shows ver 2.1.1 with lagfix enabled but says " this device doesn't run a kernel supporting extended sound controls".
I show: firmware ver 2.2.1, baseband KB1, kernel ver 2.6.32.9, build number nerov4 w/DoW 2.2.1 By Team Whiskey.
I downloaded dow directly to phone and flashed with CMR. I installed VooDoo controls from marketplace.
What am I missing?
scooter421 said:
Need some help with VooDoo sound. I have Bionix v and DoW 221 and I installed VooDoo control. VooDoo control shows ver 2.1.1 with lagfix enabled but says " this device doesn't run a kernel supporting extended sound controls".
I show: firmware ver 2.2.1, baseband KB1, kernel ver 2.6.32.9, build number nerov4 w/DoW 2.2.1 By Team Whiskey.
I downloaded dow directly to phone and flashed with CMR. I installed VooDoo controls from marketplace.
What am I missing?
Click to expand...
Click to collapse
Update to a more updated froyo kernel, the up-to-date TeamWhiskey kernels are Bali, Bali-X, and Immortality, other favorites are OverStock and Bullet from EDT. These kernels are guaranteed to have Voodoo Sound, i thought DoW did, but you may have an older version.
Thank you Mr. A for the information. Unfortunatly I tried to flash another kernal last night-project core 1.2-and must have missed a step or did something out of the natural order things are supposed to go and now I have the dreaded phone-triangle-computer screen. After trying many times I could not get my phone into download mode. My computer shows something from samsung is connected to it but I can't see the memory cards. I tried to odin but no recognintion. Ialso tried to flash clockwork back on using zadig then heimdall. Zadig installed the driver and Heimdall said uploading kernal but then just stopped. I ordered a jig from TW. Hoping for the best. I don't have the equipment to perform the UnBrickable Mod or the time. Any suggestions other than I have a nifty paperweight?
scooter421 said:
Thank you Mr. A for the information. Unfortunatly I tried to flash another kernal last night-project core 1.2-and must have missed a step or did something out of the natural order things are supposed to go and now I have the dreaded phone-triangle-computer screen. After trying many times I could not get my phone into download mode. My computer shows something from samsung is connected to it but I can't see the memory cards. I tried to odin but no recognintion. Ialso tried to flash clockwork back on using zadig then heimdall. Zadig installed the driver and Heimdall said uploading kernal but then just stopped. I ordered a jig from TW. Hoping for the best. I don't have the equipment to perform the UnBrickable Mod or the time. Any suggestions other than I have a nifty paperweight?
Click to expand...
Click to collapse
Project Core is a VERY, VERY old kernel and i think it was only for 2.1. You're not really bricked though you just flashed a 2.1 kernel to a 2.2 rom, you should be able to get into download mode and reflash a froyo kernel. Have your tried?:
1. Remove the battery and put it back in to ensure its off
2. Open Odin on PC, connect USB to PC, but not phone
3. While holding both Volume buttons and nothing else, plug USB into phone
4 Phone should go to Download mode, and if your have correct drivers installed, Odin will recognize
We've talked to Viralblack many times about removing those old kernels and roms from the homepage, we'll bug him some more about it. But once you get back up and running, make sure you flash a kernel that is supported for the rom you have. Good luck!
Mr. A,
You are a god, I bow down to you. I am odined by to stock. Thank you. I had'nt thought to check the drivers. I reinstalled from Kies then tried what you suggested. Worked like a charm and done in less than 5 min. Up and running. Whoo Hoo!
scooter421 said:
Mr. A,
You are a god, I bow down to you. I am odined by to stock. Thank you. I had'nt thought to check the drivers. I reinstalled from Kies then tried what you suggested. Worked like a charm and done in less than 5 min. Up and running. Whoo Hoo!
Click to expand...
Click to collapse
Glad it all worked out for you
and i'm no god, we were all noobz once, we learn something new everyday.
What is the team whisky peeps doing these days? Since your roms seem to be the most bragged about by far, I have always wondered if one of you would pick them back up and freshen them up with latest build.prop tweaks and whatever other things that can make it awesome..?
Silentbtdeadly said:
What is the team whisky peeps doing these days? Since your roms seem to be the most bragged about by far, I have always wondered if one of you would pick them back up and freshen them up with latest build.prop tweaks and whatever other things that can make it awesome..?
Click to expand...
Click to collapse
Team Whiskey is still around, but from what i hear, Sombionix is returning to dev, but will not be deving on the Vibrant anymore. Most of the team has left the Vibrant scene, but there are a few of us that still have ours. I still use mine and will continue to dev kernels on the vibrant for a little while longer, but sadly i can't dev roms to save my life. I would've personally loved to continue the Frost project, but like i said, i suck at rom deving. We're still around, but can i promise anything from us for the Vibrant anytime soon? Most likely no.
Thanks again for your help. Decided to try Malice v5. First day since flashing. 12 hrs and at 44%. Had a couple of bumps before I got it together, but so far so good.
Mr. Apocalypse said:
Team Whiskey is still around, but from what i hear, Sombionix is returning to dev, but will not be deving on the Vibrant anymore. Most of the team has left the Vibrant scene, but there are a few of us that still have ours. I still use mine and will continue to dev kernels on the vibrant for a little while longer, but sadly i can't dev roms to save my life. I would've personally loved to continue the Frost project, but like i said, i suck at rom deving. We're still around, but can i promise anything from us for the Vibrant anytime soon? Most likely no.
Click to expand...
Click to collapse
I am surprised just a little they found founds they considered an upgrade(I'm assuming), personally I am holding out for tmo's ICS variant of the nexus.. till then I have been trying to do research into how to develop, but sadly I have been limited to links from this section, which the resources don't explain the WHY part at all or very little.. I have always had a natural ability with technology so I am confused why I'm not seeing anything useful to help me figure out what I can do..
Which brings up a question, how did you get into working on kernels? Do you have any resources that you could share? I'm going to keep looking into the rom part, but until I find the missing link I could use some stuff to play around with..
Glad you are still around, team whisky was a major part of the evolution of these phones