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
Related
So, I'm pretty new w/ Android. Just flashed with voodoo lag fix D02-Kernel-LV-1250 using Dirrk's instructions. This means that I did the following:
- Rooted (was already done)
- Installed CWM (from instructions here)
- Downloaded D02-Kernel-LV-1250 and put on SD card
- Rebooted to CWM and did a backup
- Booted into recovery and flashed kernel
- Rebooted
Now, I see that DJ05 is released. (I even see stuff about voodoo lag fix for it...didn't know that was available.) So, now I wished I hadn't installed voodoo lag fix, because I hear it is difficult to uninstall.
I've tried to do my own research here, but I really don't want to change messing up my phone, so I'm asking for help here. Here are the threads I have sifted through:
- http://forum.xda-developers.com/showthread.php?t=805052
- http://forum.xda-developers.com/showthread.php?t=804784
- http://forum.androidcentral.com/fascinate-roms-hacks/34819-how-go-back-stock.html
- http://www.fascinateforums.com/foru...oms/685-instruction-remove-voodoo-kernel.html
- http://www.fascinateforums.com/foru...everything-you-wanted-know-about-kernels.html
Questions
What is the trade-off b/w D02 and DJ05?
If DJ05 really has the lag fix, is there any benefit of staying on D02?
For future reference, how do I know what kernel version I am using (Voodoo4 vs Voodoo5)?
Understanding what I've done above, what do I need to do to get to DJ05?
Do I really need to flash to stock and lose everything to get there?
And if so, can I use the backup I made in CWM?
If not, and I have Titanium Backup installed and all apps/data backed up, does it matter if I have to go back to stock?
Sorry for the newbie questions for help, but I really want to make sure I do it right. Any help is greatly appreciated.
FYI, this is what I've looked through for the new stuff available (should I go with the last link?):
- http://forum.xda-developers.com/showthread.php?t=869990
- http://forum.xda-developers.com/showthread.php?t=872378
- http://forum.xda-developers.com/showthread.php?t=874809&highlight=voodoo+lag+fix+vs+dj05
Thanks for any help you can give!
1. D02 is just the kernel version and DJ05 is a firmware update so there is really no comparison here.
2. updating to dj05 is worth it because it fixes several issues with the phone.
3. the only way to tell between voodoo 4 and 5 is to read which one you are downloading
4. it's a good idea to do a full wipe of the phone before updating to dj05 and your nand backup before the update will not work properly because the new kernel doesn't work with the old firmware.
5. if using ti-backup then yes wipe
to remove voodoo go to the voodoo folder on you sd and make a TEXT file called disable_lagfox.txt and reboot then LET IT FINISH COULD TAKE UP TO 20 MIN IN SOME CASES so wait it out don't pull battery no matter what.
when you update use the stupidfast kernels if your afraid of messing up your phone don't use voodoo it really is more of a power user option. didn't answer everything on order I know lol but think I coveted most of it
Sent from my SCH-I500 using XDA App
I'd like to add that in some cases the disable_lagfix method might not work. (It's supposed to be disable_lagfix, not .txt and not lagfox lol). In my case, it ran for nearly two hours without doing anything. Don't worry, if it takes that long just pull the battery and use ODIN to return to stock (from Adrynalyn's thread). But obviously make backups before you try to disable voodoo.
lol yea disable_lagfix sry swype error haha and the .txt will be added guess I just was thinking about doing it pc side I'm use to putting my own extension sometimes.
Sent from my SCH-I500 using XDA App
Thanks for the info! I've run out of time to do it before I leave for Christmas, but I'm going to do this first thing when I get back!
DJ05 fixed my GPS to the point of locking nearly instantly.
That's the kicker for me
everything else is gravy
I think my phone may be bricked when I turn it on all I get is the samsung title and it does nothing else. I had just recently updated it with the voodoo with lag fix from rom manager and then this morning flashed it with one of the super fast kernals and that is when it rebooted and never advanced past the samsung logo.
I tried to get the stock .tar form drop box but keep getting a 404 error and I am unable to get that or follow the link to remove the voodoo, that link just goes to just a jumble of symbols with nothing to download. Again sorry if this is covered somewhere else in here but I have looked and tried to fix this but not even the cw recovery works. Oh in case you can't tell I am a newb .
You can't flash non voodoo over voodoo. I'm sure someone will chime in shortly. I don't know how to fix it. Sorry
Sent from my SCH-I500 using XDA App
Odin to stock. You aren't bricked. Keep trying to download the tar file
Sent from my sch-i500 using dl09 supah clean
I believe you will have to completely reset your phone to stock with stock kernel/rom etc and you will lose all your data. It will essentially be a new phone again. It will work though.
You can flash non voodoo over voodoo as voodoo uses a different filesystem that is not 'seeable' by non voodoo kernels.
Cali3350 said:
You can flash non voodoo over voodoo as voodoo uses a different filesystem that is not 'seeable' by non voodoo kernels.
Click to expand...
Click to collapse
Note: Cali3350 meant to write shouldn't instead of can.
I would start here:
http://forum.xda-developers.com/showthread.php?t=804784
Ok I click on the first link and the page just brings up gibberish, like I said I am a newb so don't flame me too bad please, what am I supposed to do with that first link?
Don't click the link. Right-click, save as.
I am unfortunately unclear on the finer points of recovering from a voodoo misadventure, but that first link is intended for voodoo4 and perhaps catastrophic circumstance. I believe you would have voodoo5 if you installed recently via RM, but someone should correct me if I am wrong.
I haven't ever needed voodoo, so I have yet to go down any of these roads. However, if I were in your situation, I would try to clear the lagfix with red cwm first and leave my MBR alone until I was convinced I had to overwrite it. Once you are back to an RFS file system, put on a nonvoodoo file system that matches your base band and/or odin to stock as needed.
In any case, you are embarking on quite a crash course.
You should just be able to flash another voodoo kernel, then all will be fine. If you decide to flash a non voodoo kernel after that, disable the voodoo within red CWM, reboot to let the file system revert, then flash your new kernel
Thanks Kevin that worked just fine, I had to use a different sd card because somehow I write protected the one that came with the phone. It now boots up fine but I need to download everything again . But now I cannot access the market, press the icon and if flashes and then nothing.
I am looking to flash the KA6 Voodoo kernal to my Vibrant (This One). I was told to flash with SGS Kernal Flasher, but in the kernal post, she references CWM. I have never used either. Should I go with one or the other, or it doesn't matter? Also, what do I do (yes, I will search also), copy the file to the SD and tell it to run, or what?
Thanks...
I have never used sgs kernel flasher to flash a kernel, only to backup an older kernel. Its a newer app and clockwork is still the far more used.
From her instructions I would use clockwork to flash it.
Download and flash with clockworkmod, its safe to flash with voodoo enabled (I did several times tonight.)
Click to expand...
Click to collapse
SykesAT said:
I have never used sgs kernel flasher to flash a kernel, only to backup an older kernel. Its a newer app and clockwork is still the far more used.
From her instructions I would use clockwork to flash it.
Click to expand...
Click to collapse
Good enough for me. Thanks a lot...
*Edit: How do you flash? Do I place it in the MicroSD root, or the phone root? And then do I just run it? Need to rename, etc?
Thanks
It doesn't really matter they are both very similar. The only difference being with sgs kernel flasher you can back up your current kernel in case you don't like the new one. it also easier to use since it's just an app.
ferhanmm said:
It doesn't really matter they are both very similar. The only difference being with sgs kernel flasher you can back up your current kernel in case you don't like the new one. it also easier to use since it's just an app.
Click to expand...
Click to collapse
So, using SGS, how do I flash it? Do I copy the extracted .zip to the SD, or do I put the uncompressed .zip somewhere, and if so, do I rename it? Not sure where to go from here...
leave it as the zip you dl, put it in the root of your internal SD card, flash.
SykesAT said:
leave it as the zip you dl, put it in the root of your internal SD card, flash.
Click to expand...
Click to collapse
Thanks, will do so now...
VisualOddity said:
Thanks, will do so now...
Click to expand...
Click to collapse
Its going. It's been sitting on the "Google" screen for 4-5 minutes now, and a robot voice talks every little while, although I can't tell what she's saying...
So... It did that for a while, shut down and rebooted, now is a blank screen and just vibrating a little every 2-4 seconds... Is this expected, or am I F***ed?
Help! So, I went through flashing this kernal. The phone went to the Google screen, a robot voice said something every so often, then it rebooted. It looked as though it went through the Samsung screens, then went blank. For maybe 10+ minutes now, it has been blank, the phone is giving small vibrations over and over every 4-5 seconds, and the menu/home/back/search lights are on...
What do I do? Do I let it go, or do I pull the battery and restart...? Help!
Sounds like you have a bootloop of sorts. You will need to odin to stock then reflash the rom and kernel.
Don't worry, your fine. Sorry this happened to you the first time around, but it does from time to time. Did you make a Ti backup or nandroid backup, doubt the latter as you were not sure about clockwork.
Checkout the stickies for help with odin. Will reply more when I get home.
SykesAT said:
Sounds like you have a bootloop of sorts. You will need to odin to stock then reflash the rom and kernel.
Don't worry, your fine. Sorry this happened to you the first time around, but it does from time to time. Did you make a Ti backup or nandroid backup, doubt the latter as you were not sure about clockwork.
Checkout the stickies for help with odin. Will reply more when I get home.
Click to expand...
Click to collapse
Thank You! I actually did both backups, the nand w/ SGS... I posted this in the Kernal thread and we are talking about it. Please visit.
http://forum.xda-developers.com/showthread.php?p=11612890#post11612890
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
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?