Sorry guys, I searched all over and it seems that either all the methods are outdated (2010), or I'm getting different opinions on how to do this.
I'm helping my friend root his fascinate, which we have done, however he told me he tried flashing clockwork via Rom Manager. I looked it up and it doesn't appear that's the way to go. He has no familiarity with Odin, however I do.
Can someone post a nice guide on how to do this, I found one that's really good but it's missing an "update.zip" file
Thank you in advance.
Put the phone into download mode, and then use Odin to flash the CWM odin image using the PDA button. The guides from 2010 should be just as valid then as now. Also, don't bother with Rom Manager, it regularly doesn't support our phone. You also don't need an update.zip file necessarily.
Never use the Phone button in Odin!!!
Thank you sir, I imagined this is the way to go since that's what I have done with my Droid Charge.
Will I lose recovery after I odin, if I don't install a customer rom and kernel in time?
is the latest OTA update rootable?
You only need to replace the kernel. The stock Samsung kernel on any Froyo+ (and some Eclair, IIRC) roms will try to nuke CWM on boot up.
The common method is to pull the battery from the phone, be holding volume down (or was it up?) and plug it into the computer, and it should boot to the downloading screen. Odin the CWM image, and once it's totally done, unplug it. Then, holding both volume up and down, put the battery back in and press and hold the power button. Once you see the 'SAMSUNG' logo appear, you can release the keys, and it should take you to CWM. From there, you can flash a compatible kernel.
Just a heads up, any 'MTD' based ROM/kernel (MIUI, Cynanogen, AOSP) isn't compatible with stock roms/kernels. When you flash an MTD rom/kernel, it'll completely change the filesystems & layouts on your phone (making Vodoo lagfix redundant), and you can only get back by Odin w/ a few special images along with the Atlas .pit file.
I'm just looking to put him on a decent rom.
Could I just flash the PBJ kernel found here
http://forum.xda-developers.com/showthread.php?t=1012571
and after that, what is a good rom? not looking to go MTD route.
Samsuck said:
I'm just looking to put him on a decent rom.
Could I just flash the PBJ kernel found here
http://forum.xda-developers.com/showthread.php?t=1012571
and after that, what is a good rom? not looking to go MTD route.
Click to expand...
Click to collapse
Just went to the ED05 powerwashed version and its working well. Not a whole lot different than stock but at least its debloated and rooted. I had too many battery pulls when using evil fascination and Com rom (all versions). I'm still on the factory kernel because more people seem to be having issues with the PBJ kernal.
link: http://forum.xda-developers.com/showthread.php?t=1178544
zanktank said:
Just went to the ED05 powerwashed version and its working well. Not a whole lot different than stock but at least its debloated and rooted. I had too many battery pulls when using evil fascination and Com rom (all versions). I'm still on the factory kernel because more people seem to be having issues with the PBJ kernal.
link: http://forum.xda-developers.com/showthread.php?t=1178544
Click to expand...
Click to collapse
Flash the PW-Fusion OTB kernal. It's overcloackable to 1.5 and undervolt -100, you will like it over stock kernal...atleast I do! ccampos has a link with it built into the PW v.1.2 rom...may I ask why you didnt take this route initially?
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1199851%26page%3D38&v=1&libid=1313532685208&out=http%3A%2F%2Fwww.mediafire.com%2F%3Fm8cghl7y6dcrx99&ref=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1199851%26page%3D39&title=%5BROM%5D%5BKERNEL%5D%5BED05%5D%5B8%2F16%5D%20PowerWashed%20ED05%20ROM%20%5Bv1.2%5D%20-%20Page%2038%20-%20xda-developers&txt=http%3A%2F%2Fwww.mediafire.com%2F%3Fm8cghl7y6dcrx99&jsonp=vglnk_jsonp_13135327380463
droidstyle said:
Flash the PW-Fusion OTB kernal. It's overcloackable to 1.5 and undervolt -100, you will like it over stock kernal...atleast I do! ccampos has a link with it built into the PW v.1.2 rom...may I ask why you didnt take this route initially?
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1199851%26page%3D38&v=1&libid=1313532685208&out=http%3A%2F%2Fwww.mediafire.com%2F%3Fm8cghl7y6dcrx99&ref=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1199851%26page%3D39&title=%5BROM%5D%5BKERNEL%5D%5BED05%5D%5B8%2F16%5D%20PowerWashed%20ED05%20ROM%20%5Bv1.2%5D%20-%20Page%2038%20-%20xda-developers&txt=http%3A%2F%2Fwww.mediafire.com%2F%3Fm8cghl7y6dcrx99&jsonp=vglnk_jsonp_13135327380463
Click to expand...
Click to collapse
I didn't take the route initially because immediately after the kernal was linked in the powerwashed thread, there were like 4 posts of people getting Force Closes so I decided to wait a bit and see how it pans out (patience is a virtue). I've already downloaded the kernel, i'm just waiting. One thing i'm missing from the PW rom is getting rid of the battery popup. I'm scared to flash the mod because I beleive it was made for EB01.
PS i'm on PW v2
zanktank said:
Just went to the ED05 powerwashed version and its working well. Not a whole lot different than stock but at least its debloated and rooted. I had too many battery pulls when using evil fascination and Com rom (all versions). I'm still on the factory kernel because more people seem to be having issues with the PBJ kernal.
link: http://forum.xda-developers.com/showthread.php?t=1178544
Click to expand...
Click to collapse
I agree with ZankTank. This is a great ROM and I am also still on the stock kernel that was posted. My phone has never felt as smooth as with this ROM/kernel combination. Just installed the V2 version last night and it is working great and no missed calls.
--bill
the otb-fusion kernal and the pbj kernal both work great on powerwash! 90% of peoples problems are user error.
One of the reasons I moved away from stock or stock-ish roms was the battery popup that came with Froyo. Well I've just flashed the zip to remove this "originally intended for EB01 as I mentioned above and there's no popup and I haven't had any FC's or issues as of yet. Granted i've only been using it an hour. I'll update after more use.
Link to the clock popup thread: http://forum.xda-developers.com/showthread.php?t=955615&highlight=ed05+battery
I used the file download #1
zanktank said:
One of the reasons I moved away from stock or stock-ish roms was the battery popup that came with Froyo. Well I've just flashed the zip to remove this "originally intended for EB01 as I mentioned above and there's no popup and I haven't had any FC's or issues as of yet. Granted i've only been using it an hour. I'll update after more use.
Link to the clock popup thread: http://forum.xda-developers.com/showthread.php?t=955615&highlight=ed05+battery
I used the file download #1
Click to expand...
Click to collapse
Also, I forgot to mention that I had to install this zip using Clockwork version 2.5.xx because you get edify script errors with version 3.xxxx
May I ask why does the battery popup bother you so much?
Related
First off, I would like to say I did NONE of the work of making these amazing mods for the Captivate or i9000. NONE. I just figured out a good order to make them work well with each other.
All thanks for the work goes to:
xcaliburinhand for the i9000 Reorient Kernel. Without this, it would not be possible to do this and have it work right.
Tayutama for his ROM. It is quite nice too look at, and works great.
DesignGears for the Odin One Click.
REAVER117 for posting the Bell Vibrant Modem.
All those thanked by the aforementioned. Without great people like these we would all be basically stuck with an iOS knockoff. (touchwiz)
DO A NANDROID BACKUP FIRST IF YOU WANT TO SAVE YOUR DATA. Titanium Backup will work as well if you do not mind losing settings and logs/SMS/MMS.
Tayutama's ROM, get the NON VOODOO version(very important)
xcaliburinhand's Reorient Kernel(I recommend the update.zip method)
Stock Captivate Kernel from Koush
Get the JM9 i9000 ROM from SamFirmware
Get the CSC file (OXA) from Here
And finally, Bell Vibrant Modem from REAVER117(Others may work, but I used this one and it DOES work)
Get the JG8 modem here: MultiUpload
I will upload a .zip I did over the weekend from home later, it has all necessary files.
Once you have these components and have backed up your Captivate, follow these steps and you should be up and running on JM8 with Tayutama's ROM and HSUPA.
1. Flash to stock with Odin One Click
2. Flash to JM9 PDA in Odin 1.0 or 1.3 (CSC optional, I do it to remove all traces of AT&T)
3. Flash v1.2 of the reorient kernel(Allows button press in recovery mode, stock captivate kernel should also work) in Odin v1.0 or 1.3
4. Flash JG8 modem in PHONE portion of Odin(can be done at same time as step 2 and 3)
4. Flash Tayutama Full, Lite, or Super Lite 1.2 update.zip, NOT THE VOODOO package through Clockwork mod recovery. Flash supplementals like stock lock after this step.
5. [OPTIONAL]Restore Nandroid backup(Data only though Advanced Restore or Titanium Backup(optional, nandroid restore CANNOT BE DONE AFTER VOODOO without disabling lagfix)
6. Flash Reorient kernel 1.3 with Voodoo and BLN through the ClockWorkMod update.zip method
7. Reboot and enjoy!
Screenshots
(I am using Launcher Pro, NOT SENSE! I just did that to trick my boss who is an HTC junkie)
I don't see any files posted by Zilch25 in that modem thread. Do you mean the Vibrant Bell modem posted by Rever117?
no driver said:
I don't see any files posted by Zilch25 in that modem thread. Do you mean the Vibrant Bell modem posted by Rever117?
Click to expand...
Click to collapse
Yeah that's why i edited my first post, I remembered incorrectly.
Gonna try this out later
Sent from my SAMSUNG-SGH-I897 using Tapatalk
You should include that you need to actually download the JM8 firmware. I was following the directions and then realized that there was no link to JM8 itself haha I almost flashed Tayutama's ROM directly w/o going to JM8 first!
So what are the positives and negatives? Is it better or faster than Cognition?
Must have linked to one of the few threads I didn't post it in
Quick Question:
In the instructions you say to flash the Reorient Kernel 1.3 through update.zip method, so I am assuming that means in stock recovery. However, when I try to install via the stock recovery I get the "installation aborted" message. Can I install via Clockwork Mod Recovery?
KCutrer1 said:
Quick Question:
In the instructions you say to flash the Reorient Kernel 1.3 through update.zip method, so I am assuming that means in stock recovery. However, when I try to install via the stock recovery I get the "installation aborted" message. Can I install via Clockwork Mod Recovery?
Click to expand...
Click to collapse
Yeah use Clockwork.
irtehun said:
Yeah use Clockwork.
Click to expand...
Click to collapse
Thanks. I went to the Reorient Kernel thread to check how it's installed over there and they said Clockwork as well. Working pretty well right now!
KCutrer1 said:
Thanks. I went to the Reorient Kernel thread to check how it's installed over there and they said Clockwork as well. Working pretty well right now!
Click to expand...
Click to collapse
Gonna be switching to windows and flashing this setup here real soon.
Ughh.... I know this was gone over before the site crash but I'll post my experience. I flashed this setup following the steps to a T but for some reason my Quadrant was lower and the phone seemed like it was running a little slow, checked my speed test and averaged about 400-500kb down and up, and my phone signal was shotty. So I flashed back to stock with Odin then flashed Cognition 2.1. As soon as I was done flashing I noticed I had no signal. This was sitting in the same spot where I normally have 4-5 bars. Now here's where my heart sunk. I came to XDA looking to find the fix cause I knew I had seen it somewhere on this thread.... and... site's down. My phone is a company phone so not being able to make or take calls puts a little damper on things. So I flashed stock about 4 more times and had the same result every time. Finally I gave up and tossed the phone on my counter. While making my daughter something to eat I just happened to look over at it and what do I see...? FULL BARS. Not sure if anyone cares or not but thought I'd tell my story. I don't know what caused it to stop working or what caused it to start working but that's my experience. Could just be me doing something wrong also.
Bah 24 hour forums data rollback =(
Glad it just randomly came to life for you though... we'll chalk this one up to a "samsung problem"
crap. where'd all the posts go?
I got mine to work after the forum went down. I did all the Odin flashes and then the 3 button flash worked for the rom.
Question though. If I use mods like the circle battery mod should I get the one from the captivate forum or the i9000 forum, or are they the same?
wmwilker said:
I got mine to work after the forum went down. I did all the Odin flashes and then the 3 button flash worked for the rom.
Question though. If I use mods like the circle battery mod should I get the one from the captivate forum or the i9000 forum, or are they the same?
Click to expand...
Click to collapse
You'd prob wanna use the i9000 versions.
irtehun said:
You'd prob wanna use the i9000 versions.
Click to expand...
Click to collapse
Thanks
Going to give that a try
After running this command.
am start -a android.intent.action.MAIN -n com.android.Preconfig/com.android.Preconfig.Preconfig
I have no XEU setting in there.
So right now i am stuck in KOR.
any fix for this?
I gave up on this. Just not working for me.
This will most definitely wipe all previous remnants of data, including any unlock codes that you may have on your phone!
Update 10/11/10: This is now a confirmed fix for phones with larger NAND chips;
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. Once done and phone has rebooted, root your phone & install Rom Manager.
14. Download & Install Bionix 1.7 with OCUV Voodoo
Click to expand...
Click to collapse
NOTE: The bootup sound HAS changed.. But if you hear Linda go through the process of changing the format then you can now run voodoo..
(Or if you don't know & you arent for sure, just download Quadrant & if your score is 1500+ voodoo is enabled.)
If you would like to know if you have a larger NAND chip, please follow This guide.
Credits: sombionix | SkOrPn | Master™ | JAC
If I forgot anyone in that list, I apologize. Please just PM me so I can add you to the list.
i think my vibrant has the larger nand chip, any way to make sure before i go through the steps above? using terminal on the phone would be best, it's just mount right? not sure what to look for after that
Supercurio has already supplied JAC with the fix for the larger NANDS (I asked him). JAC just has to make a new kernel with it included.
BUT, JI6 is so fast that I don't think that it even needs a lag fix. I've been running it for a couple days with not one hiccup. Don't know what Samsung did but it worked.
kangxi said:
Supercurio has already supplied JAC with the fix for the larger NANDS (I asked him). JAC just has to make a new kernel with it included.
BUT, JI6 is so fast that I don't think that it even needs a lag fix. I've been running it for a couple days with not one hiccup. Don't know what Samsung did but it worked.
Click to expand...
Click to collapse
Yeah I know, But until he makes it we can test this for a temp fix
Ok well, I DO have a larger NAND which is why I've been trying to follow the Beta5 development. Can you explain what doing all of this actually does and why it works?
kangxi said:
Ok well, I DOCan you explain what doing all of this actually does and why it works?
Click to expand...
Click to collapse
We have no clue.. But we both have done this & for some reason voodoo works on both of our devices now
kangxi said:
Ok well, I DO have a larger NAND which is why I've been trying to follow the Beta5 development. Can you explain what doing all of this actually does and why it works?
Click to expand...
Click to collapse
I have been using voodoo for several weeks now. I kept getting the dreaded "this model is not supported" error when trying to apply voodoo kernels. I tried literally dozens of times if not more, I was on the verge of quiting but sombionix told me to try flashing to the froyo rom that does not brick, and then to the stock rom. I immediately rooted, installed Rom Manager and Clockwork recovery, and then flashed bionix 1.4 rom (might have been bionix 1.3 at first, but 1.4, 1.6 and 1.7 have all worked since) containing JAC's v1.1 OC/UV/Voodoo kernel with Voodoo beta4.
Voodoo has worked flawlessly ever since... My NAND is the larger 416MB NAND. Go figure....
All we are asking of you guys is to have a little faith and try this procedure. If it works, then you get voodoo bliss, and if it don't then we are back where we started. You have nothing to lose but a hour or less of your time. Give it a try and report back here please. Good luck...
SkOrPn said:
I have been using voodoo for several weeks now. I kept getting the dreaded "this model is not supported" error when trying to apply voodoo kernels. I tried literally dozens of times if not more, I was on the verge of quiting but sombionix told me to try flashing to the froyo rom that does not brick, and then to the stock rom. I immediately rooted, installed Rom Manager and Clockwork recovery, and then flashed bionix 1.4 rom (might have been bionix 1.3 at first, but 1.4, 1.6 and 1.7 have all worked since) containing JAC's v1.1 OC/UV/Voodoo kernel with Voodoo beta4.
Voodoo has worked flawlessly ever since... My NAND is the larger 416MB NAND. Go figure....
All we are asking of you guys is to have a little faith and try this procedure. If it works, then you get voodoo bliss, and if it don't then we are back where we started. You have nothing to lose but a hour or less of your time. Give it a try and report back here please. Good luck...
Click to expand...
Click to collapse
+1
He didn't even tell me, lol
It'd be nice to see Bionix v1.8 come with Voodoo Beta5 since they're both so close at hand so we don't have to go through this crazy business. Good work and great find, though!
I followed this method and it allowed me to use the Voodoo Lag Fix. I was never able to get it to work before, would never hear the boot up sequence telling me my file system was being converted etc. After flashing Eugenes Froyo rom and flashing back due to stability issues I tried Bionix 1.5 and was able to flash the voodoo kernel. I checked before when it wouldn't work for me and found that I too also have the larger NAND chip. I upgraded to Bionox 1.6 just fine, not sure why it worked but Its been wonderful these past 2 weeks.
I second ji6 is impressive.
Sent from my SGH-T959 using XDA App
vdubgti08 said:
I followed this method and it allowed me to use the Voodoo Lag Fix. I was never able to get it to work before, would never hear the boot up sequence telling me my file system was being converted etc. After flashing Eugenes Froyo rom and flashing back due to stability issues I tried Bionix 1.5 and was able to flash the voodoo kernel. I checked before when it wouldn't work for me and found that I too also have the larger NAND chip. I upgraded to Bionox 1.6 just fine, not sure why it worked but Its been wonderful these past 2 weeks.
Click to expand...
Click to collapse
Yeah Voodoo beta5 was never needed, so a whole lot of people waited for nothing. LOL
So i searched the forums and didnt find a definate answer, maybe i didnt search the correct terms or something, idk. My question is, if you have a larger nand and voodoo DOESNT install, do you still need to run "disable-lagfix" when flashing a backup or another rom?
2sh0rt said:
So i searched the forums and didnt find a definate answer, maybe i didnt search the correct terms or something, idk. My question is, if you have a larger nand and voodoo DOESNT install, do you still need to run "disable-lagfix" when flashing a backup or another rom?
Click to expand...
Click to collapse
No i do not believe so, BUT, I would still put that file into the voodoo folder anyway. There is no harm in doing so. When you get the other rom installed and setup how you like, then you can remove it. Voodoo can be enabled and disabled at will simply by removing/replacing the "disable-lagfix" file into the voodoo folder. Its just as easy as that really...
Hope that helps.
I Really think you don't need to since your file system is still rfs,
how do you totally remove voodoo? if i flash back to the last backup i have BEFORE installing bio1.7 voodoo will voodoo still be there or will it be gone?
I think you would need to put the disable-lagfix file/folder in the voodoo folder. Then reboot wait until it's done, then flash a kernal that isn't voodoo.After that then restore your back up. For some reason, I thought my back up was fine, but when I take the disable-lagfix file out, it would reinstall voodoo again when I boot. It might just be me, but I don't think nandroid back-ups restore the kernal. I could be wrong...
Daddy_617 said:
I think you would need to put the disable-lagfix file/folder in the voodoo folder. Then reboot wait until it's done then flash a kernal that isn't voodoo then restore your back up. For some reason before I thought my back up was fine and when I take the disable-lagfix file out it would reinstall it again when I boot. It might just be me but I don't think nandroi back ups restore the kernal. I could be wrong...
Click to expand...
Click to collapse
+1
Yes you need to put that disable-lagfix file into the voodoo folder on the sdcard. Reboot, it will tell you voodoo is being disabled/transformed back into rfs, once finished you can then proceed with your normal flashing routine.
Linda's beautiful voice!!!
I'm a long time lurker, but I've never had anything constructive to say so I've silently read, and slowly learned how to make my phone more awesome. I'm happy to say that I followed these directions exactly and voodoo finally enabled. What a great find! Thanks!
Orwell83 said:
I'm a long time lurker, but I've never had anything constructive to say so I've silently read, and slowly learned how to make my phone more awesome. I'm happy to say that I followed these directions exactly and voodoo finally enabled. What a great find! Thanks!
Click to expand...
Click to collapse
Glad to hear another happy voodoo user, and yet more proof that beta4 works on all vibrants including larger nand variants.
Your welcome Orwell
This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor
Yes this try to keep this thread open.
Sent From My Evo Killer!
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force
forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.
olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.
Duplicate... Sorry
forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted
Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3
Hey all, my buddy's getting his wife a Fascinate tonight -- we want to root it/lagfix it before he gives it to his wife.
But I thought I read somewhere Lagfix doesn't apply anymore....
So can someone help me out with the correct steps on this?
You are looking to use voodoo5 lagfix. Yes we all still use it. Imo, it is well worth it. And remember, the fascinate is *almost* impossible to brick. We have some VERY talented devs for this phone. If you are going to use voodoo lagfix, you might as well use adrynalyns debloated/deodexed rom. It removes all of vzw bloatware. I am running a different rom, but I started with voodoo lagfix with ed01 db/do rom. Battery is way better and phone is overall snappier. Surf around the development thread to get your feet wet. Good luck!
Bob-o
Sent from my SCH-I500 using XDA Premium App
Thanks -- is adrynalyns debloated/deodexed rom different from the community Rom I'm seeing?
bigshotproducer said:
Hey all, my buddy's getting his wife a Fascinate tonight -- we want to root it/lagfix it before he gives it to his wife.
But I thought I read somewhere Lagfix doesn't apply anymore....
So can someone help me out with the correct steps on this?
Click to expand...
Click to collapse
One Click Lagfix no longer applies, but if you install a voodoo kernel on the phone you will enable voodoo lagfix.
If you just want to root the phone and stay stock you will need to download the Samsung USB drivers for the Fascinate to your computer. After downloading the file, double click on the downloaded file to install the drivers:
http://www.megaupload.com/?d=NZS8BF7E
Download superuser 2.3.6.1 + busybox 1.19 and place it on the base of the sd card:
http://adrynalyne.us/files/odin/su-2.3.6.1+busybox1.19.zip
Load ODIN onto your computer:
http://www.megaupload.com/?d=J4Y10P6G
Flash this CWM recovery in the PDA section of ODIN:
http://www.mediafire.com/file/06al8prkgj29gps/cwm-recovery-ALL-3-30-FIX.tar
Boot directly to CWM by holding the volume up, volume down, and power buttons until you see the samsung logo flashes twice then let go of all three buttons, use volume buttons to scroll to install zip from sd card, power button, scroll to choose zip from sd card, power button, scroll to su + busybox file, power button. When that finishes installing, menu soft key until you are back at the main CWM menu where reboot system now will be highlighted, power button and phone will reboot.
bigshotproducer said:
Thanks -- is adrynalyns debloated/deodexed rom different from the community Rom I'm seeing?
Click to expand...
Click to collapse
Ha! I was actually going to suggest the debloated/deodexed ROM anyway after writing the novel. Yes debloated/deodexed and Comm ROM are different ROMs. Debloated/deodexed is just the stock ROM deodexed with most of the verizon bloat removed. Comm ROM is further debloated and includes much more customization including a custom kernel.
Thanks, you guys rock! Thanks for the direction and help!
One more question -- will this work the same for 2.1 *&* 2.2? I don't know yet which the phone has.
bigshotproducer said:
One more question -- will this work the same for 2.1 *&* 2.2? I don't know yet which the phone has.
Click to expand...
Click to collapse
These should work on both. If she is getting a new one it will have 2.2. If it was purchased from someone else, won't know until you get it.
Thanks all! Everything worked great!
1 More quick question. We Rooted, then OTB Kernel, and then went to install the Debloated/Deodexed Rom, but it gave an Edify error?
We made a nandroid after rooting and then again after the kernel.
Should we have installed the ROM and then then kernel to make it work?
Thanks again.
bigshotproducer said:
1 More quick question. We Rooted, then OTB Kernel, and then went to install the Debloated/Deodexed Rom, but it gave an Edify error?
We made a nandroid after rooting and then again after the kernel.
Should we have installed the ROM and then then kernel to make it work?
Thanks again.
Click to expand...
Click to collapse
always flash the rom first then the kernel. Odin this recovery: http://www.mediafire.com/file/06al8prkgj29gps/cwm-recovery-ALL-3-30-FIX.tar
This recovery won't give you any edify errors
Made a One Click Odin. By the way, I'm not a developer by any means. This was easy to do and I just wanted to share this with everyone. I hope some of you find it useful.
And of course, standard disclaimer applies... What you do with your phone is on you.
Stock I897UCKH3 with boog_kh3_kernel3, NO Bootloaders
INFO:
Stock i897uckh3 with the stock zImage removed and replaced with boog_kh3_kernel3 zImage. NO Bootloaders.
Credit and Thanks to boog for his awesome work on this kernel.--Thread on the Boog Kernel.
And a quote from boog's OP in said thread for permission to use his kernel-- "Anyone is available to use the kernel any way they like. Cook it in roms released here, flash it to your personal rom, or stock KH3! Take it apart, look at the pieces, see if you can make it better! I am far from a pro at this, and it may not be perfect, use at your own risk..yada yadda."
We also have PM'd back and forth a few times. And on a side note, boog also has made a Heimdall version of the stock kh3 with his kernel...see Here if you are interested in that option.
Credit and Thanks also to Samfirmware.com for their leaked release of the firmware.
And I need to give credit to malebornin69 for posting a question about this kind of mod being made... here. His question is what got me interested in making this Mod.
This One Click Odin should serve the purpose of getting you back to Stock KH3 with the bonus of having the boog kh3 kernel3 included, that has ClockWorkMod Recovery v4.0.1.5 built in. And in addition, no worries of flashing bootloaders because they are not included.
This does not wipe data/factory reset though. So you will have to either wipe data/factory reset prior to using this Odin or afterwards. If you do not then you will probably have issues once you flash your Dev Rom of choice. Also, I suggest that you wipe dalvik cache.
So, once you have used this One Click Odin and have wiped data/factory reset, wiped dalvik cache, then just reboot into the CWM Recovery via the button combo or adb reboot recovery and flash the Dev Rom of your choice. Or of course, you have the option of staying on the stock kh3 and using the CWM Recovery to flash mods, tweaks, modems, etc.
Note: This is a modified KH3 because in addition to the zImage that is changed, I also took the dbdata.rfs and the param.lfs files from the leaked KF1 .tar and moved them into this KH3 (these files were not in the leaked KH3 .tar file from samfirmware.com).
I did this just to make it a complete flash for those not coming from KF1 or KE3. Also, I have this set to re-partition. (the re-partition will not work without the dbdata.rfs file).
My tests of this included... Starting from stock kh3 with fuguroot and going to the stock kh3 with boog kernel through the one click odin I made, factory reset and wiped dalvik cache in CWM recovery, flashed Fusion V (this is a full wipe version too) with zero problems. Then repeated the process of going into CWM recovery and factory reseting and wiping dalvik cache and flashed Pinnacle 1.2 (not sure if this rom is a full wipe) and zero issues. Repeated the process and flashed the Victory 1.4 with zero problems as well. Repeated process and flashed the KH3 Project v1.0 rom with no problems. And finally, repeated the process in CWM recovery to factory reset and wipe dalvik cache, got into download mode and used this one click odin to get back to the Stock KH3 with the boogkernel3...and again, all good.
DOWNLOAD LINK ---- {One Click Odin} Stock I897UCKH3 with boog_kh3_kernel3, NO Bootloaders @ Dropbox *This is a compressed zipped folder that contains the Mod. About 185 MB. Download, Extract and Right click and Run as administrator.*
Additional download links will be in Post #2
DOWNLOAD INSTRUCTIONS:
You must have the i897 Gingerbread Bootloaders. Gingerbread bootloaders are needed to run Gingerbread Roms. If you have not installed them, then get them--I897 Gingerbread Bootloaders , credit and thanks to Cezar`.
Download this Mod One Click Odin to your desktop.
Be sure you have the Captivate drivers installed on your computer.
Wipe data/factory reset. Wipe dalvik cache if you can.
Right click and Run as administrator the Odin.
Remove your sim card and external sdcard from you phone.
Put your phone into download mode.
Connect micro usb end of cable to phone and usb end to the computer.
Wait for Odin to recognize your device. Yellow com port will light up.
Click the big Start Button.
Sit back and watch. This should only take between 2 or 3 minutes to complete.
When the process is finished and your phone begins to reboot and you see the 2nd at&t screen you may go ahead and unplug the micro usb from your phone.
Let your phone boot all the way up.
And there you go...you now have Stock KH3 with the boog kh3 kernel3
Additional Download Links... Updated 9-20-2011
*These download links are a compressed zipped folder that contains the Mod. About 185 MB.*
*Download, Extract and Right click and Run as administrator.*
{One Click Odin} Stock I897UCKH3 with boog_kh3_kernel3, NO Bootloaders @ Hotfile
{One Click Odin} Stock I897UCKH3 with boog_kh3_kernel3, NO Bootloaders @ Minus (Thanks prbassplayer for the suggestion and the link to Minus.com)
boog has provided a 4shared mirror link in Post 17 (Thanks boog)
Those who appreciate this Mod, please stop by The Boog Kernel Thread and show your thanks to boog for his work on the KH3 kernel.
.
Great!!!!!!!!!!!!!!!!!!!
Sent from my I897 using XDA Premium App
Good work bro!!
looking good! KH3 is quite the popular rom!
^ Yes, it is very popular these days. KH3 is very stable, with great battery life and the call quality is awesome. And as well, the Dev work with KH3, including yourself, is outstanding.
Thanks again for your Kernel work and for allowing me to use your kernel in this mod.
Sent from my SAMSUNG-SGH-I897 using xda premium
thanks for this. This is definitely helpful. Its good to see an odin package for this.
Thanks for putting this together.
Thanks for putting this together. KH3 has become my daily driver. It's probably the fastest, most stable thing I've put on my Captivate. Easy to root... easy to remove the AT&T bloat with TiBu. This thing just flies. Best battery live I've ever had, too. Great modem for both voice and data. Samsung really should get this pushed out.
4-2ndtwin said:
^ Yes, it is very popular these days. KH3 is very stable, with great battery life and the call quality is awesome. And as well, the Dev work with KH3, including yourself, is outstanding.
Thanks again for your Kernel work and for allowing me to use your kernel in this mod.
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Thanks! And your welcome, I only managed to do it with the help of people like existz, and xcal. I saw no one else releasing a cwm kernel, so I blundered my way through it lol
You guys wouldn't believe how many failed attempts I had, then had to do the fixes, and I still can't figure out the nandroid issues, I think that is in the source with differences in samsung gingerbread.
And I love the sharing that goes on here with the captivate. Other devices I have used, appeared to have secrets that no one would share. I am also thinking about writing up some sort of how to for taking the kernel apart and looking at the initramfs, and the associated scripts, and commands that can be used to find the differences in the files, and how to find what you need to change to make an injected cwm kernel, because the info is spread all over the internet, and not always in obvious spots because source availability is assumed most of the time. But, that may take me some time lol
And, I agree, so far kh3 is THE best rom for captivate, ever, and the reason for me even wanting to dig into the kernel.
And now back on topic. I will have to try this on my vm of windows at some point. But I have really fallen in love with heimdall, especially with all the flashing of kernels that I do. But more options like yours is always welcome in my book!
we are spanking yor DB accounts ass right now, said there is too much traffic.
nice job on this by the way. much appreciated.
^ Lol.
I will try my best to get another link up asap.
At work now...
Sent from my SAMSUNG-SGH-I897 using xda premium
^Try out Minus. Starts with 10GB can expand till 50 for free and no traffic limit. Only thing is their UI is less than great.
Enabling tethering
Is there a simple way to enable tethering? I tried various cooked gingerbread roms and I see lagging performance especially opening the email. It takes about 3 to 5 seconds to see the email list once I click on email. Used the stock 2.3.4 KH3 and really like the stock ATT/Samsung email (social hub) that has number of unread emails on the icons. None of the cooked email does that. Main thing I wanted is enable tethering.
prbassplayer said:
^Try out Minus. Starts with 10GB can expand till 50 for free and no traffic limit. Only thing is their UI is less than great.
Click to expand...
Click to collapse
Thanks...may give that a try later. Right now I am uploading to Hotfile because I already had an account set up. Hopefully will be able to attach that link in 30 minutes or so.
---------- Post added at 04:37 PM ---------- Previous post was at 04:32 PM ----------
chuh said:
Is there a simple way to enable tethering? I tried various cooked gingerbread roms and I see lagging performance especially opening the email. It takes about 3 to 5 seconds to see the email list once I click on email. Used the stock 2.3.4 KH3 and really like the stock ATT/Samsung email (social hub) that has number of unread emails on the icons. None of the cooked email does that. Main thing I wanted is enable tethering.
Click to expand...
Click to collapse
This is pure stock KH3, except for boog's kernel. The files I used to make this One Click Odin are the same files that are in the leaked KH3 from samfirmware.com
As for the tethering... the only two ways to do it on this stock kh3 is to either pay for it or use Titanium Backup and uninstall or delete the Tethering Manager. You have to be rooted of course with the Titanium Backup option.
Additioal download links
Attached a couple of more download links in Post #2.
Links are through Hotfile and Minus.
Also the Dropbox link in the OP is fixed.
*These download links are a compressed zipped folder that contains the Mod. About 185 MB.*
*Download, Extract and Right click and Run as administrator.*
.
Here is a 4shared mirror http://www.4shared.com/file/ZHWqcF-K/Stock_KH3_with_boogkernel3_and.html
^ Awesome ! Thanks boog ! (been out of thanks since way earlier today)
I will reference your post in my post #2.
A friend of mine wants just stock 2.3.4 so is this automatically rooted, or does that have to be done afterwards?
Also, nice to see a stock KH3 and Boogs kernel all-in-one... makes it much faster and its really convenient. Thanks for making this.
^ This Mod is not rooted. I'm currently just running this Mod as is, but I did root through the FuguRoot method (quick and easy).
And I appreciate the feedback.