Database Users

[Q] Few questions about custom Epic ROMs

i have the HTC EVO and have been running Flipz FreshROM since he first put out his custom EVO ROM and even used his HERO ROMs before that. my wife has an Epic now, which i rooted back in October. she's currently running the last official update from Samsung (DI18, i believe) and i wanted to update her to the latest release (DK28).
what are the best custom ROMs to use that are based off of the DK28 update?
is it best just to update to DK28, then root and not worry about a custom ROM?
in order to update to DK28, do i have to unroot first or is there an already unrooted DK28 ROM that i could flash?
thanks for the help.

Sturmie said:
i have the HTC EVO and have been running Flipz FreshROM since he first put out his custom EVO ROM and even used his HERO ROMs before that. my wife has an Epic now, which i rooted back in October. she's currently running the last official update from Samsung (DI18, i believe) and i wanted to update her to the latest release (DK28).
what are the best custom ROMs to use that are based off of the DK28 update?
is it best just to update to DK28, then root and not worry about a custom ROM?
in order to update to DK28, do i have to unroot first or is there an already unrooted DK28 ROM that i could flash?
thanks for the help.
Click to expand...
Click to collapse
In my opinion, different people will have different opinions regarding which ROM is the "best". User experience can vary from person to person. What may not be an issue to one person may be a deal breaker for another.
I would recommend trying each until you find one that meets your needs. To update to DK28, I would recommend following this guide:
http://forum.xda-developers.com/showthread.php?t=853209
Couldnt be easier. If you find that you have issues with DK28, use ODIN to get back to 2.1 and then reroot. The process is simple and easy to find if you search. Personally, the second time I tired DK28, I used ODIN to go back to stock 2.1, then used the link above to go to DK28. I would also recommend giving your phone a few days to adjust to 2.2. This helped some of my issues work themselves out.

Use odin to flash the dk28 modem first. I can't post links yet but look in the ViperRom thread for a good zip of Odin with the dk28 modem and the correct Pit file. Unzip everything, untar the modem.tar. Turn off your phone. Boot while holding the 1 key down (you get a Yellow Icon in the middle of the screen). Run Odin, Place the modem.bin file in the PHONE slot in odin, put the .PIT file in the PIT slot in odin. Plug the phone into the computer. Odin will see your phone as a COM# port, any number is fine. Auto-Reboot and F.Reset Time should be the ONLY things checkmarked in options. Click start.
Its complicated but it works pretty good. The phone will restart and run with the DI18 and the DK28 modem. Get a GPS Lock in Navigation or Google Maps on the phone, make sure it locks! Skipping this step has led to some people not being able to get locks with the internal gps on epics with dk28.
Apply the oneclick root found in the forums (Android Developement).
Pick a rom, i think Bonsai 1.04 is very stable and pretty with its elegant font.. not so strongly masculine like some of the custom roms. Download the rom and put it on the sdcard, boot into clockwork (volume down, camera and the power button simultaneously) and wipe / factory reset, wipe cache, wipe dalvik cache. Flash the rom...zip off the sdcard and then reboot.
Yes you can flash directly dk28 with modem using ODIN.. I tried the OTA zip on a stock DI18 and couldn't get that to work for me. But when I went direct to dk28 from di18 i lost gps.
Anyway, just my story, and what I did. I love my custom rom, but it took me hours to figure it out. I hope these instructions are complete and errorfree, but it would be a good idea to read forum threads about this stuff besides just what I have to say. ViperROM's thread was especially helpful with the odin use stuff. There is a wiki about it too, but im not allowed to post links, oops.

I don't know if it was just me but I immediately jumped on the DK28 band wagon, and yes it was cool but for me it was somewhat unstable. My Wifi was borked, sometimes it'd go on perfect, other times I'd hit the widget in the pulldown, and it'd sit there green and do nothing. i'd have to go into the Settings -> Wifi and it'd say "Error". So like I said I don't know if it was just me cause everyone else here loves it. Anyway just thought I'd let you know!
Good luck!
Sincerely,
D3luSi0n4L

thanks for the responses...i really appreciate the info.
candypeart said:
Apply the oneclick root found in the forums (Android Developement).
Pick a rom, i think Bonsai 1.04 is very stable and pretty with its elegant font.. not so strongly masculine like some of the custom roms. Download the rom and put it on the sdcard, boot into clockwork (volume down, camera and the power button simultaneously) and wipe / factory reset, wipe cache, wipe dalvik cache. Flash the rom...zip off the sdcard and then reboot.
Click to expand...
Click to collapse
if i'm wiping everything and flashing a custom DK28-based ROM, do i need to unroot, flash the stock DK28, re-root and then flash? or could i just wipe the current state of her Epic and flash the Bonsai ROM? i know with my EVO that i have to update the baseband/radio separately from the ROM, but whenever i want to update my EVO, i just wipe and re-flash the new ROM.

D3luSi0n4L said:
I don't know if it was just me but I immediately jumped on the DK28 band wagon, and yes it was cool but for me it was somewhat unstable. My Wifi was borked, sometimes it'd go on perfect, other times I'd hit the widget in the pulldown, and it'd sit there green and do nothing. i'd have to go into the Settings -> Wifi and it'd say "Error". So like I said I don't know if it was just me cause everyone else here loves it. Anyway just thought I'd let you know!
Good luck!
Sincerely,
D3luSi0n4L
Click to expand...
Click to collapse
I was having voice problems myself... lots of distortion at high volumes. Went back to 2.1 and the problem is gone.

Sturmie said:
i have the HTC EVO and have been running Flipz FreshROM since he first put out his custom EVO ROM and even used his HERO ROMs before that. my wife has an Epic now, which i rooted back in October. she's currently running the last official update from Samsung (DI18, i believe) and i wanted to update her to the latest release (DK28).
what are the best custom ROMs to use that are based off of the DK28 update?
is it best just to update to DK28, then root and not worry about a custom ROM?
in order to update to DK28, do i have to unroot first or is there an already unrooted DK28 ROM that i could flash?
thanks for the help.
Click to expand...
Click to collapse
Check out Quantum rom,with EXT4..Just did my wifes epic,no issues at all....BTW i run fresh 3.5, good rom....

I have a question about roms and the (eventual) update to official froyo...will those of us on DK28 need to flash back to use custom roms or will we be able to simply odin a new modem and install a new rom? Or better yet, not have to odin anything and just be able to flash in CWM.

Flashed from Bionix-v 1.21 to Trigger 2.1, now my data is stuck in E.

I flashed from TW Bionix-v 1.21 to Trigger 2.1.1 and though the flash went great and the rom seemed to work perfect, my data is all messed up. It seems stuck on E now where before I was always on H. Speedtest has gone from 4000kbps down to 120kbps down. I flashed back to Bionix and even flashed in the KA6 modem that I had the best results with before and the problem still persists. In Boinix it will show the data speed as H, but as soon as I try to access the internet or use Speedtest, it drops to G, then to E. I'm lost as to where to go from here. Any help is greatly appreciated.

What about flashing back to stock using odin then reflashing the rom
Sent from my SGH-T959 using XDA App

Woah, wait up don't flash back to stock or anything. Follow this thread, it has all the modem software in it. I suggest using Odin...it's real simple, just dl the file extract it and load it into the phone section in odin and hit start....BAM you got a new modem. Do tests with JL5, it's a good modem.

I was thinking of flashing back to stock but I've never done it before. Is there anything I need to do differently because of Voodoo? I may just go the AIO Toolbox method if that's ok.

I won't be doing anything until later tonight. I've flashed a few modems in the modem thread, but none have fixed this problem. I may just flash back to stock (I really don't mind), but I'm just nervous about doing it because of having Voodoo on my phone right now. Can I just flash back to stock using the AIO Tools, or is this ill-advised?

Always best to disable lag fixes, I do it even if I don't have to. If the problem is persisting through different modems I dunno what's up....maybe hardware related? Maybe try one of those cell reception mods. That'd be the absolute last thing I'd do though, try every modem if you can.

I really don't know what happened. It may have even been a bad flash with Trigger, that's when things went bad. Honestly I wish I'd have just stayed put with Bionix. The phone was working perfectly with it. Oh well, I think I'll try flashing back to stock, then going back to Bionix.

Try this:
Settings-->Wireless and Network-->Mobile Networks-->Network Mode
I have mine set to WCDMA only. I only use Auto mode when I travel outside of town. Works great and keeps me out of the edge network.

kbohip said:
I was thinking of flashing back to stock but I've never done it before. Is there anything I need to do differently because of Voodoo? I may just go the AIO Toolbox method if that's ok.
Click to expand...
Click to collapse
DUDE, if you haven't ever flashed back to stock, I recommend it now then reflash the new rom. It will totally clean up in ghost data in the phone.
Remember the sequence is Backup everything 1st, then disable the lagfix, Then flash the froyo that does not brick (do not check the repartition box), then flash Stock JFD (this time check the repartition box) Then Root, then, the flash your new rom then Download Rom manager and titanium backup and you are good to go.
BTW, you most likely got a corrupted bit of software in the flash or already it was on the phone but there is no way of knowing, THAT is why you should do this.

kbohip said:
I won't be doing anything until later tonight. I've flashed a few modems in the modem thread, but none have fixed this problem. I may just flash back to stock (I really don't mind), but I'm just nervous about doing it because of having Voodoo on my phone right now. Can I just flash back to stock using the AIO Tools, or is this ill-advised?
Click to expand...
Click to collapse
Sorry to hear that man. I've had this problem before... looong ago. I had just flashed a new release of a TW ROM and all the sudden my data was stuck on E. I was freaking out just like you haha. I odined to stock and reflashed at least 3 times and the problem persisted.
I just left the phone on overnight and it seemed to work itself out by morning. Maybe it was T-Mobile doing maintenance or maybe the phone was just being retarded...
Either way, I'd suggest flashing back to stock at least once to clear things up. Check back in the AM and see if it's fixed or not

oka1 said:
DUDE, if you haven't ever flashed back to stock, I recommend it now then reflash the new rom. It will totally clean up in ghost data in the phone.
Remember the sequence is Backup everything 1st, then disable the lagfix, Then flash the froyo that does not brick (do not check the repartition box), then flash Stock JFD (this time check the repartition box) Then Root, then, the flash your new rom then Download Rom manager and titanium backup and you are good to go.
BTW, you most likely got a corrupted bit of software in the flash or already it was on the phone but there is no way of knowing, THAT is why you should do this.
Click to expand...
Click to collapse
I've never flashed back to stock, and of course all of these excellent custom roms have me flashing like a madman. I think I've flashed at least 5 different roms in the last month at least. I think I understand what you mean by "ghost" data. It's like the old days in Windows 98 where an upgrade install was never as good as a clean install. Flashing back to stock is sort of a clean install for Android I'm guessing?
birgertime said:
Sorry to hear that man. I've had this problem before... looong ago. I had just flashed a new release of a TW ROM and all the sudden my data was stuck on E. I was freaking out just like you haha. I odined to stock and reflashed at least 3 times and the problem persisted.
I just left the phone on overnight and it seemed to work itself out by morning. Maybe it was T-Mobile doing maintenance or maybe the phone was just being retarded...
Either way, I'd suggest flashing back to stock at least once to clear things up. Check back in the AM and see if it's fixed or not
Click to expand...
Click to collapse
Ok, this is strange. It looks like this is exactly what's happening. I'm now getting 4000+kbps down again on H. All day though the phone has been bouncing down to E every time I access the internet, go to market, etc. Upload is still quite a bit lower than it used to be though. Still, in the back of my mind though I feel like what oka said above is probably not a bad idea. For peace of mind I'm going to flash back to stock using AIO Vibrant Toolbox, then root, then flash either Bionix or Trigger back on.
Btw, for the short amount of time I had Trigger installed on my phone, I can tell you that it's a VERY nice rom. It looks great and is at least as fast, if not faster than Bionix. Great, great work.

I was having this problem earlier today too on Bionix. I was downloading Quadrant and I was stuck in E for a couple of hours. Must be something wrong with Bionix. Either way it's working now and I hope you solve your problem!

3g
Sent from my SGH-T959 using XDA App

kbohip said:
I flashed from TW Bionix-v 1.21 to Trigger 2.1.1 and though the flash went great and the rom seemed to work perfect, my data is all messed up. It seems stuck on E now where before I was always on H. Speedtest has gone from 4000kbps down to 120kbps down. I flashed back to Bionix and even flashed in the KA6 modem that I had the best results with before and the problem still persists. In Boinix it will show the data speed as H, but as soon as I try to access the internet or use Speedtest, it drops to G, then to E. I'm lost as to where to go from here. Any help is greatly appreciated.
Click to expand...
Click to collapse
Maybe you did something wrong,i also move from Bionix V to Trigger 2.1 and my data is working well,the only thing i notice is that 3g works like edge now,very slow and when on H it fly.

[Q] evo cm7 nightly freeze

i'm running cm7 nightly with latest radio, wimax, 1.90 pri and nv. everytime i flash a kernel my phone gets stuck at white screen and will not allow a nand restore whatsoever. my battery life is terrible even if i try pri 1.7 and nv 1.7.. wiping never helps.. why is this happening? any ideas???

Probably because you are doing something wrong. Just like this thread you felt compelled to start. You know you could ask this question in the CM7 thread or even the question and answer forum...
Ok now that that has been said what kernel are you trying to flash?
Sent from my PC36100 using XDA App

i placed the same question over on cyanogen forums and got no help. i was using cm7 nightly build 8. I wiped then flashed sz 0.0.9 no sbc kernel and 30 minutes later froze, rebooted and still stuck at white screen. Booted into recovery and only got amon_ra_1.8 never loaded. So i had to put the pc36 file on my sd card via laptop and managed to go into hboot that way. Let it update itself then reflashed cm7 nightly #8. Was working smoothly except for battery life which is why i did a back up and tried netatchy_toast_4.2.3. That worked a few hours and landed me back at frozen white screen with a nand backup that kept giving me a flash error. After 3 tries the backup loaded and thats where i'm stuck at. I think i'm about to flash cm7 build 12, the latest, see how it works, then give a shot to another kernel. Any ideas?

Yes. It's a nightly build. It's unstable, and no one is going to help because it's almost impossible to troubleshoot.
also netatch's kernels are for sense roms. Use an AOSP kernel.

Try the kernel in my sig. Seems to work pretty well.

tried to post in cm7 thread but got a "new user" warning saying i dont have enough posts to post in that area. so i had to start at the noob level..

HipKat said:
Try the kernel in my sig. Seems to work pretty well.
Click to expand...
Click to collapse
Im gonna give that kernel a shot if nightly 12 still sucks up my battery. Only thing is, thats the same kernel that got me frozen the first time lol. Maybe it will run better with nightly 12?

Do a full wipe of system, boot, data, and cache, then flash just the ROM and GApps package. If you still have issues, get a logcat, and post in the CM7 Nightly thread here.

sounds like a plan. just got done flashing #12. Colors in notification bar stay white sometimes now lol. I wiped first then flashed. Read somewhere you didnt have to wipe if flashing 12 over another nightly. Wiped regardless, just throwing it out there..
oh, do i need to reflash pri and nv or are they not an option for nightly builds? tried them once before and pri never showed up.

cm7 nightly #12 seems to have helped battery life alot. Taught my daughter to ride her bike, went to movies and saw "Rango", stopped by walmart, came home, battery remained strong. On nightly #8 it was dead in 3 hours. #12 seems like a winner so far!! Not sure what pri and nv come in #12 or if they need to be reflashed or which one i should flash if they remain old etc... etc... Thanks in advance for any help!!

quickstang1 said:
Not sure what pri and nv come in #12 or if they need to be reflashed or which one i should flash if they remain old etc... etc... Thanks in advance for any help!!
Click to expand...
Click to collapse
There are NO PRIs / PRLs/ NVs, or any of those things. Those are never part of any rom flash. Those are either flashed separately, or obtained through a sense ROM via profile or prl updates.
Also, even though you are thinking things are fine with your current build, I am curious what recovery you are using... and what is your HBOOT. are you forever S-OFF?

using amon_ra 1.8, unrevoked forever. Cm7 nightly #12 is kickin a$$!!! No reboots, no battery drain, no weird glitches.. Stock kernel, cpu set at "performance", unplugged from 8am to 4 pm, using internet all day, wimax on, 3 weather widgets running, made it all that time and still had 15% battery left... Not sure what was changed in 12, but its a definite keeper!!!

[ROM] Bonsai User Discussion

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

How To Install Clockwork Recovery

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?