I just noticed that there seems to be some worried about rooting if you ran the verizon DL09 odin package. Don't worry. d2 root method for fascinate found on XDA works just fine. http://forum.xda-developers.com/showthread.php?t=779238
Have not found a one click root that works yet though. If you find one, post it!
**UPDATE**!!!
Looks like there are some that are hit or miss... may have to run them a few times and wait upwards of 5-10 minutes for some.
if you don't want to wait use perm d2 method. happy rooting!
I actually used the one click root method that is found on android central after i upgraded to DL09. Worked for me. It was strange because i had to do it 3 times until it finally ran.
To get it to run it needed over 5 mins (which the once click says if it takes more than 5 mins try again) I had run it then lost track of what i was doing because i was at work. Then next thing i know it completed itself. So i can confirm it does work.
jselden said:
I actually used the one click root method that is found on android central after i upgraded to DL09. Worked for me. It was strange because i had to do it 3 times until it finally ran.
To get it to run it needed over 5 mins (which the once click says if it takes more than 5 mins try again) I had run it then lost track of what i was doing because i was at work. Then next thing i know it completed itself. So i can confirm it does work.
Click to expand...
Click to collapse
Looks like patience is the key here people... if you are familiar with adb, you could probably root it faster. i ran z4 and let it run quite a few times myself before i said screw it (i actually got a FC or 2 as well) and just ran the perm d2 method.
thanks for the heads up!
Possible reason why
I'm gonna look for the page I got my 1 click method from, but it worked for me on the first time. I rooted immediately after flashing the odin file. Then I screwed something up before I pout clockwork on so I reflashed since I lost everything (not really, thanks to Titanium Backup). Then I immediately flashed the clockwork after and then the 1 click failed twice. Reflashed the official dl09 then 1 click and, boom, rooted on the first try.
After doing a little searching, apparently the clockwork.tar flashes a DI01 kernal. So if people are flashing clockwork before rooting, this could be the culprit. I use this method found here
http://m.forum.androidcentral.com/showthread.php?t=33899
Hope this helps some people out.
one click root worked for me
The one click root method from android forums worked for me (said it completed) but none of my root access apps are getting root access.
I rooted through the manual adb method.
I'm having trouble booting into clockwork though.
After grabbing clockwork recovery from ROM manger, it goes to stock recovery where it errors with "signature verification"
do I have to push the original clockwork.tar through odin?
edit: http://forum.xda-developers.com/showthread.php?t=913470 <<< fixed the issue. push through odin
I used the adb method from android central and I had to wait 5-10 minutes to be kicked back out to the windows command prompt after running rage.bin.
It's not just 1 click methods that sometimes take a long time to complete.
i used the 1 click method from dirkk. i had problems with my phone reading as a media driver(trying to sync to my pc) so that was causing the 1 click method to fail at first. once i disabled the media sync it was sucessful first try.
HOW TO UN-BRICK YOUR FASCINATE NOW THAT YOU HAVE BRICKED IT
SINCE IT HAS COME TO MY ATTENTION SOME POEPLE ARE CONFUSED ABOUT WHAT PHONE THIS IS FOR, I WILL MAKE IT AS CLEAR AS POSSIBLE
THIS IS FOR THE VERIZON FASCINATE
So you think you bricked your phone? The first thing you need to do is CALM DOWN, NO NEED TO PANIC , the odds are great that following this guide will fix your mistakes and recover your phone.
Sorry Fascinate owners, but I can no longer support this thread. As state below I test everything I post to make sure it works as advertised. I no longer have a fascinate so i can not test anything new. Sorry but the links to some of the files are gone I don't have them anymore so I suggest you look through the comments someone will have someplace to get what you need. Your recovery methods may have changed but this can still be used to recover your device. If you are looking for anything new look at nitsuj17's roll up post here, he maintains it very well so you should be able to find whatever else you need there.
I HAVE PURPOSELY BRICKED MY PHONE BY DOING THE THINGS YOU ARE TOLD NOT TO JUST TO TEST THE CAPABILITIES OF THESE RECOVERY PROGRAMS. UNLESS YOU CAN AFFORD TO HAVE YOUR PHONE REPLACED BY INSURANCE, TRUST THAT I KNOW WHAT I AM TALKING ABOUT.
SECTION 1: ODIN
SECTION 2: HEIMDALL
SECTION 3: ROOTING METHODS
Since there seems to be an abundance of posts in the Q&A and General Forums asking for help fixing, unbricking, their Fascinates, I decided to try to make a one stop walk through for odin and heimdall with links. Most of us "flash addicts", Developers, and testers have found the Samsung Galaxy Phones are nearly impossible to truly brick without causing physical damage to your phone, in almost all cases it is possible to get it working again.This is nothing more than how to get back a working STOCK phone, nothing custom here that's in the Development section. The first section will cover odin, the second heimdall, the third recovery and rooting.
USUAL WARNING: Everything here is done at your own risk. None of us on the XDA Developers site are responsible in any way, after all we didn't brick it you did. Doing any of this is your decision, I am just providing a collection of information. All credit for everything here belongs to others, who worked hard to give you a way to fix your mistakes, and it usually is the owner of the device trying something without learning how first, or not following directions that got you here in the first place.
My Phone wont boot at all, is stuck at logo, or I cant do anything with it is it a paperweight?
Most likely, no, so lets get to fixing it. All download links necessary for each process will be posted in this walk through and have been tested to make sure they work.
SECTION 1: ODIN
Everything except for the pit file in odin MUST be done in the PDA slot, if not it will not work requiring you to odin again, or possibly have to use heimdall (covered later in this thread) to fix that. After you download odin, I use v1.83 but I will provide all versions I have.
First you need to decide if you want to go all the way back to DI01 (Android 2.1 "Eclair") or EB01, EC01, or a little more involved process for ED01, or ED03 (android 2.2 "Froyo") it makes all the difference with the files you need. The pit file is not necessary for most recoveries, but I have included due to a few issues that will require you to completely wipe everything but your SD card and start over. All of this is possible thanks to our talented developers. After you have odin and all the files you need on your Windows Vista or Win 7 PC, This DOES NOT work on XP, I have had a lot of responses to support this, so lets go with it won't work use Vista or Win 7. To load any file you click that button and use the windows explorer pop up to find your file select it and click open at the bottom of the window.
Start by powering off phone, the pull out battery.
Open odin and load your file in PDA and ONLY THE PDA (downloads) section, If you knew enough about this program to use the other areas you would not need this walk through, soPDA and ONLY THE PDA (downloads) section, for an, all in 1 Recovery. If you are doing a non packaged update I suggest installing the rom one first, modems and recoveries are a lot faster install.
If you are repartitioning put the pit file in the (Pit) section,verify repartition is checked.
Plug your phone into a USB slot, then hold the volume down hard key on the side of the phone. You should see a yellow triangle with a construction droid on your phones screen, and a box on the left right above options (ID:COM) is now yellow.
Now you are in download mode, verify check box next to PDA is checked and the block has the file location in it. Make sure Repartition (unless you are repartitioning and have the pit file in place), Dump, Phone EFS clear, and Bootloader, Phone Bootloader Update, and Flash Lock are NOT CHECKED in the Options section. Auto Reboot and F. Reset Time can be checked or not it doesn't really matter with the battery out. These are the default settings in the options section but double check it anyway.
You are ready to go, click start, and let odin run, it can take anywhere from just a minute to around a half hour. If anything happens like your computer shuts off, you accidentally unplug your phone from your PC, or download failed. Don't freak, just do it again from step one, sometimes it takes multiple attempts to get it. I think at six failed attempts in a row it may be time to look into heimdall, the walk through for that is below this one.
Once odin finishes and does its test you will get a green box lit up that says Pass in it just above where you saw the yellow box showing you were connected. Congratulations on a successful recovery. reinstall your battery and the back cover, reboot your phone and wait for it to boot up. The boot process can take several minutes so be patient. If the boot was successful you should be looking at a stock bloated Verizon Fascinate, that is asking you to back up your system and log into Gmail.
Fascinate USB driver from Samsung, just in case you need it.
Sch-i500 USB driver
odin v1.3
odin v1.7
odin v1.83
Atlas v2.2 Pit file
DI01All in 1
EB01All in 1
ODIN CWM ED01 Stock ROM/Kernel/Recovery Courtesy of Imnuts
ODIN ED03 ROM/Kernel/Recovery Courtesy of Imnuts
MODEM ODIN CWM DL09, EA28, ED01, ED03 modems without ridiculous 100MB OTAs Courtesy of Comradesven (I can now say this works and is easy to do just folloy the instrictions on thread.) Decided to try out this method after bricking my phone again, EASY AND FAST, love it.
EC09 Gingerbread Leak CAUTION:It has not happened to me yet even after several times of flashing something custom and using this to odin back to stock with, but there are many reports of this corrupting users SD cards. This is a leak and as always USE THIS AT YOUR OWN RISK!!
Here are the ONLY TWO, as far as we know guaranteed to get you fixed up, odin files, for anyone coming from CM7 or MUI MTD for the Fascinate.
YOU MUST USE THE ATLAS V2.2 PIT FILE, ONE OF THESE FILES, AND REPARTITION. IF YOU DON'T ODIN WILL FAIL TO COMPLETE THE RECOVERY.
CI500_VZW_DL09_ECLAIR
CI500_VZW_EB01_FROYO
SECTION 2: HEIMDALL
Now for the heimdall walk through, so follow along. I don't think it is possible to completely brick this phone short of actually smashing it, why take unnecessary chances.
First go to the link for heimdall. Download, unzip this and open the folder. In this folder you will find another folder labeled Drivers, open it and you will see a program called zadig.
Now put your Phone into download mode, that is remove the back cover, take out the battery and plug it into your PC with the OEM cable (the one that came with the phone when you got it), then press and hold the down volume button till a yellow triangle and construction droid , now you are in download mode.
Double click zadig and when it opens, click on options and click list all devices. Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver, select it then click install drivers. the usual install stuff from windows about do you want to install this, yes you do. Now If the warning about publisher could not be verified, whatever, install it anyway, no it's not a virus. Your phone MUST be in download mode or zadig will not have the USB you need as an available option.
Now you need the files for this program to install and recover your phone. I was motivated to set up a zip file for download with files ready due to confusion on how to accomplish this step, you will find links below.
Now back into the heimdall file you opened earlier you will need to double click the heimdall.exe file, and click run on the windows pop up, it will show a cmd prompt type screen then disappear shortly after, it's supposed to do that.
Again in the click the application called heimdall-frontend. here is where you can go wrong so I will do this side by side with heimdall names and DI01/EB01 file names. I don't believe there are currently any other full recoveries.
To eliminate confusion on where to put your files follow the guige below.
Heimdall on this side of =Recovery file names on this side.
In Repartition:
PIT = atlas_v2.2.pit see below.
In PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
In CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Now that all the are files loaded into the correct spots, the necessary drivers installed, and phone in download mode, the start button will be able to be clicked, not shaded outlines like before, did you even notice that? If you followed everything in this tutorial step by step, click the START button and let heimdall run. After it finishes reboot your Verizon stock, Bing bloated, WORKING Fascinate. After this is completed successfully you will be able to use odin again if you need or want to.
Heimdall
DI01 heimdall package
EB01 heimdall package
Why did this happen?
Why was this necessary, as far as I can find out, through research, I wont even try to figure out how many times I had to odin ,and the eight, yes that's right I said 8, times I have HAD to use heimdall, because my phone would not recover through odin. Usually because like me you flashed a rom on for a different phone or, it seems to be, dbdata or another partition can not mount. This has happened to me because I didn't remove voodoo, or flashed a pre edify rom after accidently putting cwr3, which is for edify, on a non edify rom. So moral of the story is twofold, yes it is very likely it can be fixed, and remove voodoo before going to nonvoodoo, and make sure you have a version of cwr that supports both ammend and edify script if you are not sure. Don't flash a rom for a different phone on your Verizon Fascinate or you most likely WILL need heimdall.
NEVER USE A FILE, ROM, KERNEL, ANYTHING, THAT IS NOT CLEARLY FOR THE VERIZON FASCINATE.
Remember, thank the developers by clicking the thanks button on threads you find helpful, they did the work. All I did was take some time and put together all the links and processes I have read and had to learn. Some of the walk through threads are well written by the Dev's and some were hard for me to follow. Sometime I wonder if our Dev's forget that us mere mortals have no idea what they are talking about, and I pride myself on being much better than average with computers and software. That said if you have trouble working e mail and office, I think it's fair to say you would be lost. I hope this is easy to follow and always successful for you. Better yet I hope you never need this.
READ:If heimdall, or odin fail, but you can still get into download mode, do it again, and keep trying while you look for further assistance on this site. If you can't get into download mode with your phone plugged into your PC, unplug usb from PC and plug it into the wall outlet, and try to put it into download mode there. When It goes into download mode, unplug usb from adapter, plug it into PC and put it into download mode, This does work.
If this has Helped you not have a $600 dollar paperweight, consider donating to some of our Dev's working so hard to not only give you better than what big red and sammy gave you, but also a way to fix your mistakes without the need for an insurance claim. Isn't it worth a few bucks to support the developers who save you from the insurance deductable? Think about that before you complain about the devs.
SECTION 3: ROOTING METHODS
Here are two easy ways to accomplish rooting your phone.
ROOTING YOUR PHONE VOIDS YOUR WARRANTY. I NOR ANYONE ELSE WILL BE RESPONSIBLE FOR ANYTHING YOU CHOOSE TO DO. NO ONE HERE IS MAKING YOU DO ANYTHING, JUST PROVIDING INFORMATION ON WAYS TO ACCOMPLISH WHAT YOU WANT TO DO.
Super One Click method: unzip file, open file, double click ADB, it will show a quick cmd like window. Now make sure you phone has USB debugging enabled, connect to PC, don't mount USB. Click the SuperOneClick.exe icon and let it run. If it fails run it again, sometimes it does that. If anything pops up on the screen, read and answer. Unless you are using a Captivate leave the Captivate tab alone it is for getting an unlock code and you don't need that for your Fascinate. (works on all fascinate stock OS to include ED03, and EC09 GB, tested by me.)
CWR & SU Method: (DOES NOT WORK ON 2.2.1) Put superuser.zip zip file on root of SD card, odin in cwr, boot phone into recovery by holding power and volume at same time. To do this simply install battery after unpluging from PC press and hold power and volume buttons at the same time. DO NOT let the phone boot as far as the Samsung logo or you will have to odin in cwr again. Go to Install zip, choose zip, install from SD card. Find your superuser.zip file and install it. Reboot, you are rooted, install busybox, free from market if necessary. If you need odin or instruction on using it, see section 1.
GINGERBREAK Method: Gingerbreak v1.20.apk is an easy to do method, put the apk on your sd card, install from file manager, run it.
KEEPING CWR3 IN 2.2.1: To keep CWR on any ED OTA release you need to make some adjustments to a few files. Don't worry I am going to tell you which ones, and I suggest a simple method of adding .no to the end of the file. That way if you ever need to undo it, simply go back in and remove the .no and your not trying to remember what the file name and extension was. Now here are the file names for each file, you will need something like root explorer and a rooted Fascinate to do this, and you can't rename a file unless you tap the mount system as r/w not r/o, its easy here are the examples of how I did it.
/system/recovery-from-boot.p becomes /system/recovery-from-boot.p.no
/system/bin/recovery becomes /system/bin/recovery.no
/system/etc/install-recovery.sh becomes /system/etc/install-recovery.sh.no
Superuser+busybox
CWR 3/30 Fix all
CWR3 Voodoo.tar Blue
times_infinity's recoveries
Gingerbreak v1.20
Special thanks to Adrynalyne, Imnuts, Jt1134, Nitsuj17, Landshark, Sbrissen, ChainsDD, Times Infinity, and Comradesven and anyone I forgot to thank, for creating and sharing, the heimdall, odin, and other files.
This is a great source of information. The formatting could be a little better though. Perhaps break up those great giant paragraphs a bit. It would be easier to follow along. Especially for noobs in a panic state after "bricking" their phone.
Great work though. This should be stickied.
I will Update thread to an easier format over the next few days. Thanks for the tip, i looked good to me but now i see what you are talking about. It took hours today to gather all the info, pull up each program ans walk through it. I guess I was in mental overload.
Attempted Heimdall today after odin has failed using the EB01, error was "Failed to retrieve config descriptor" any ideas?
If I flash with all CSC options unchecked the flash is successful.
When trying to boot after flash without CSC i receive a phone and a computer with a dotted line connecting the to on power up. Phone will return to DL mode.
Also attempted to flash DL01, it seems there are several files that correspond with Heim that are not in the package are the EB01 files interchangeable with the missing files?
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
times_infinity said:
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You were that guy.
times_infinity said:
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Oops, but at least i was consistant on the typo...LOL. I will fix it this weekend.
I just got a fascinate.....commingle from a vibrant.....I can't find a root method that doesn't include a computer,my previous phone I downloaded update.zip went into recovery and bammo rooted then have spent the last unknown amount of time playing with the Roms and now want the same. With this phone anyone help? Thanks.
Sent from my SGH-T959 using XDA Premium App
Figured out this morning I wasnt using my factory usb cable switched cables odin'd stock eb01 worked perfectly now I feel retarded.
Sent from my SCH-I500 using XDA App
Excellent write up. Thanks a bunch.
What are some other differences in Odin 1.7 vs 1.3? I have used 1.3 many times and never had any issues. Any improvements?
Thanks so much Dale! headed to work now, but will try this tonight
Rayn1328 said:
I just got a fascinate.....commingle from a vibrant.....I can't find a root method that doesn't include a computer,my previous phone I downloaded update.zip went into recovery and bammo rooted then have spent the last unknown amount of time playing with the Roms and now want the same. With this phone anyone help? Thanks.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=897889 you pretty much need a computer. z4root worked at one time iirc I used it on my fascinate at some point.
More reasons as to why you should never fear bricking your phone and testing new kernels and ROMs. Thank you for the thorough tutorial.
cbalt said:
http://forum.xda-developers.com/showthread.php?t=897889 you pretty much need a computer. z4root worked at one time iirc I used it on my fascinate at some point.
Click to expand...
Click to collapse
I prefer what i think is a much simpler method. Just go to this link and follow Post 2. I don't believe I have ever had it so easy to root a phone:
http://forum.xda-developers.com/showthread.php?t=948722
nice write up, thanks for posting. I hope I never have to use it
netwalker0099 said:
Attempted Heimdall today after odin has failed using the EB01, error was "Failed to retrieve config descriptor" any ideas?
If I flash with all CSC options unchecked the flash is successful.
When trying to boot after flash without CSC i receive a phone and a computer with a dotted line connecting the to on power up. Phone will return to DL mode.
Also attempted to flash DL01, it seems there are several files that correspond with Heim that are not in the package are the EB01 files interchangeable with the missing files?
Click to expand...
Click to collapse
Got that once cause i didn't install the drivers in zadig. I installed it, didn't reboot PC, worked fine. If you had the CSC unchecked then you didnt install a cache or database, so no your phone wont work like that. Unless you ran into something new, follow this guide step by step, and it should work. I would also make sure you get the files from here, they are tested and known to be good. There are some incomplete, and bad files out there, these work.
Heimdall is officially the greatest piece of software ever created and DaleV is my hero!!! FINALLY have my phone up and running again! Was serious contemplating dropping around $300 for a new phone on Craigslist.
Trying to root a Fascinate, and it showed up in ODIN once, then the flash failed. Now it's in download mode and not showing up in ODIN, any ideas?
Oxirane said:
Trying to root a Fascinate, and it showed up in ODIN once, then the flash failed. Now it's in download mode and not showing up in ODIN, any ideas?
Click to expand...
Click to collapse
after it failed did you unplug then replug and go back into download mode? also I updated the OP with a superuser.zip file it works better than the one in the market for showing you have root access, I have no idea why.
Also you might try a different usb port, sometimes that does the trick.
I've unplugged and replugged and rebooted it a dozen times... it first goes to 2e recovery, then I reinstall packages and it reboots to the simplified download mode with just basic little icons. Doesn't get recognized by the computer though. :/
Wont boot into anything but 2e, and from there into oldschool download mode.
For those with NTT sc-02b. there is a new firmware available on KIES. it is 2.3.3. baseband sc02bomke3. i updated my phone but in my opinion, it kinda suck.
Works good for me. Its much smoother than the previous rom. But, i cant figure out how to root.
Tried super one click and the gingerbreak .apk. they just run forever.
Sent from my SC-02B using XDA App
I just upgraded too.
Works good for me too (actually seems faster from the get-go and I like the new status bar design).
Unfortunately One Click Root is not working for me either.
There are some instructions on how to get it to work already on komugi.net but they are beyond my abilities.
Unfortunately XDA won't let me post direct links yet so here are the instructions copied directly from the site
In Japanese...
この画面を見た時は＼ｵﾜﾀ／と思ったのですが生きてました。
・やり方
1. アップデートのdecode済みファイルを入手する。
2. boot.bin と Sbl.bin を抜いてリパックする。カーネル単体のも作る。
3. リパックしたファイルを Odin3 で flash
4. 適当な rootカーネルを Odin3 で flash
5. リカバリモードから suコマンドを送り込み chmod 6755 su する。
（ドコモロゴで止まった場合でもadb shellから操作可能）
6. Odin3で純正カーネルをflashする。
7. 起動後に root になって Superuser.apk とか busybox とか入れる。
8. おわり。
・問題点
リカバリモードに入れない。
毎回起動時に↑画像のように画面が乱れる。
（画面が乱れるのはbootloaderを更新していない事が原因の模様）
・追記
bootloaderのアップデートを行っても特に問題無く「4.」以降の作業が行える事を確認した。
この場合問題点は全て解決される。
従来のCWMはRecoveryの仕様が変わったため使用不可。
English Translation (from Excite)...
It lives and [mashita] . though thought ＼ [owata]/when this screen is seen.
･Way
1. The file that is decode of the update is obtained.
2. With boot.bin Sbl.bin is pulled out and [ripakku]ed. The kernel unit is made.
3. The [ripakku]ed file With Odin3 Flash.
4. It is suitable The root kernel With Odin3 Flash.
5. From the recovery mode The su command is sent Chmod 6755 su is done.
(It is possible to operate it from adb shell even when stopping in the DoCoMo logo. )
6. Flash does a pure kernel with Odin3.
7. After it starts Become root Superuser.apk Busybox is put.
8. End.
･Problem
It doesn't put it in the recovery mode.
The screen falls into disorder like ↑ image when starting every time.
(It is a pattern that the screen falls into disorder caused by the thing that bootloader has not been renewed. )
･Postscript
The thing that it was possible to work especially unquestionably since "4." even if bootloader was renewed was confirmed.
In this case, all problems are solved.
Because the specification of Recovery changed, past CWM cannot be used.
Hopefully someone will figure out a simpler method soon or dumb it down a bit for me
Yeah. . . Looks rather complicated. I'm hoping for something that can be undone as well, but alas. I may have to finally study up on using Odin and all that jazz.
Sent from my SC-02B using XDA App
Chainfire's cf root method can be used to root this version with one additional step. After flashing and booting one time Chainfire's cf kernel you will have to go back to download mode and re-flash the original ke3 kernel. This will leave you with busybox, su, and superuser install in the correct places. You will not have 2e recovery or cwmod and there will be a couple of Chainfire's utilities that won't work on our kernel that you should be able to uninstall. Since none of his kernels are the same as ours I used the newest one from around post 6. I've done this a couple of times and it seems to work well. As always I take no responsibility if you brick your phone. I have attached the original ke3 kernel the tar file inside the attached zip may take a long time to flash possibly because I made it in 7zip instead of booting ti Linux to make it properly.
If your not comfortable playing with Odin and flashing phones I recommend waiting on someone to come up with a safer process.
link to CFroot thread http://forum.xda-developers.com/showthread.php?t=788108&highlight=cf+root
dejanet said:
Chainfire's cf root method can be used to root this version with one additional step. After flashing and booting one time Chainfire's cf kernel you will have to go back to download mode and re-flash the original ke3 kernel. This will leave you with busybox, su, and superuser install in the correct places. You will not have 2e recovery or cwmod and there will be a couple of Chainfire's utilities that won't work on our kernel that you should be able to uninstall. Since none of his kernels are the same as ours I used the newest one from around post 6. I've done this a couple of times and it seems to work well...
Click to expand...
Click to collapse
Thanks for the tips dejanet...
I gave it a try using CF-Root 3.7 and my SC-02B is stuck in a startup loop now... Maybe I did something wrong though? I don't need to select a PIT file in Odin, do I?
I'll give it another go with an older version of CF-Root, but if you have a specific version that you know works and any tips, that'd be great.
I used the newest one. And you for sure don't want to use a pit file or repartition. You might want to flash back to the ke3 kernel first.
Sent from my L-06C using XDA Premium App
OK! Had to reset my phone to factory once for some reason, but then I was able to flash just as you suggested and it worked fine this time. No looping.
Maybe there was something dirty in the system that was interferring? Maybe I should have tried clearing cache from recovery instead of just restoring to factory first...
Anyway:
Used Cf-root 3.7 flashed PDA with Odin once, rebooted... no baseband..
Used the stock kernel you provided (thank you very much) flashed PDA with Odin and done.
SC-02B 2.3.3 version KE3 Rooted!
(Only really sad thing about resetting to factory was that I hadn't been able to run Titanium Backup without root, so I lost all my Angry Birds progress since the 7th. (T_T) ... some lost spmode emails too, but no big deal.)
rooted 2.3.3 gps problem
My sc-02b rooted 2.3.3 but gps cannot work. I used Angrygps/GPS status/GPS test to connect the satellite, but it's all failed. I also followed the instruction to set up angrygps and gps.conf. Any one know what happen? Is it caused by rooted rom?
Thanks.
Glad you we're able to get root working. Can't think of anything in the root process that would break GPS I rarely use it with this phone sine it has never worked well for me I'll play with it tomorrow.
Sent from my L-06C using XDA Premium App
I'll test GPS too next time I go outside (not till 8pm tonight though).... my work desk isn't close enough to the window to get a GPS signal...
Never even thought to try that and see if it was working. Definately an important feature on the weekends.
dejanet said:
Chainfire's cf root method can be used to root this version with one additional step. After flashing and booting one time Chainfire's cf kernel you will have to go back to download mode and re-flash the original ke3 kernel. This will leave you with busybox, su, and superuser install in the correct places. You will not have 2e recovery or cwmod and there will be a couple of Chainfire's utilities that won't work on our kernel that you should be able to uninstall. Since none of his kernels are the same as ours I used the newest one from around post 6. I've done this a couple of times and it seems to work well. As always I take no responsibility if you brick your phone. I have attached the original ke3 kernel the tar file inside the attached zip may take a long time to flash possibly because I made it in 7zip instead of booting ti Linux to make it properly.
If your not comfortable playing with Odin and flashing phones I recommend waiting on someone to come up with a safer process.
link to CFroot thread http://forum.xda-developers.com/showthread.php?t=788108&highlight=cf+root
Click to expand...
Click to collapse
Quick and easy and works like a charm! Thanks so much!!!!!!!!!!!!
I got a chance to test the GPS and seems to be working ok for me. The one thing I did do was use gps status to reset the assist data.
Have you changed the setup of Angrygps and gps.cong(system/etc)?
Compared to 2.2.1, GPS function on 2.3.3 is useless for me.
Is there anyone know how to optimize it?
Thanks.
Stock ROM download?
Anybody have links to this stock firmware? Maybe modem and pit files too? I've been looking all over the net and on Japanese sites but the best I can find is a place to download a pre-rooted KE3.
how's the battery life compared to froyo? Can the camcorder & camera shutter sound finally be muted on the gingerbread update???........
can someone please upload the 2.3.3 firmware for SC-02B here because for some reason my Samsung Kies says "this firmware cannot be updated", so the only solution for me is flashing the firmware via ODIN
Guys, I am stuck in a bootloop after flashing latest CF-root then flashed back original kernel. How can I fix it without reflashing the whole kernel? I have tried flashing the original kernel provided by Dejanet many times but to no avail.
hello people, long time no see
I myself got the upgrade to gingerbread 2 days ago, and rooted that evil thing yesterday, using CF kernel
well, as I was expecting, that damn CWM just wiped away my mmcblk0p3 partition (fortunately I have a dump) so some original apps don't work anymore, but those were expendable
odd enough, I don't even have root access when using the shell in recovery, get some segfault at best
bad news is that I don't have the sources for Samsung's version of the kernel, so I'm not even able to make my own recovery-2e
it's very annoying to see all the good work done by the community that we're not even able to enjoy... sigh
Can you please post the sc-02b OMKF2 Kernel? I already update to the latest version. Last time I follow your selotion. Is worked well. Thanks !