Related
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.
My phone is working fine now on Bonsai4All, so this is more of a comment or general question.
My phone had the "official" DK28, CWM 2.5, and RFS.
I followed the directions for installing Bonsai4All, and the installation seems to have gone well until the end, when the phone apparently re-booted on its own, and acted strangely during that reboot --- it alternated between the Samsung animation and the word "android" as an animation. It did this repeatedly for maybe 10 minutes. It wouldn't respond to any buttons. So I took the battery out, and rebooted. The phone seems to have booted normally, but again, none of the buttons worked. I then took the battery out again, and this time booted to CWM3 by the usual "down volume, camera, on". That worked fine, so I decided to re-install the bonsai ZIP file. This time, it seems to have worked OK, and on reboot got the Bonsai tree boot animation.
Many of my apps failed to work until I deleted them and then re-installed them.
Now everything seems to work. Works great!!!
fsc137 said:
My phone is working fine now on Bonsai4All, so this is more of a comment or general question.
My phone had the "official" DK28, CWM 2.5, and RFS.
I followed the directions for installing Bonsai4All, and the installation seems to have gone well until the end, when the phone apparently re-booted on its own, and acted strangely during that reboot --- it alternated between the Samsung animation and the word "android" as an animation. It did this repeatedly for maybe 10 minutes. It wouldn't respond to any buttons. So I took the battery out, and rebooted. The phone seems to have booted normally, but again, none of the buttons worked. I then took the battery out again, and this time booted to CWM3 by the usual "down volume, camera, on". That worked fine, so I decided to re-install the bonsai ZIP file. This time, it seems to have worked OK, and on reboot got the Bonsai tree boot animation.
Many of my apps failed to work until I deleted them and then re-installed them.
Now everything seems to work. Works great!!!
Click to expand...
Click to collapse
This is a common issue for users who try to install Bonsai on a fresh stock DK28 install. It has been reported several times in the Bonsai thread. It's designed to flash from an existing ROM so it can backup and migrate your data.
mattallica76 said:
This is a common issue for users who try to install Bonsai on a fresh stock DK28 install. It has been reported several times in the Bonsai thread. It's designed to flash from an existing ROM so it can backup and migrate your data.
Click to expand...
Click to collapse
Yet, when upgrading to CWM3 many people have to flash via odin back to DK28 stock bc CWM3 doesn't play well with other RFS roms and gives the "not found" error when trying to convert to ext4. A bit of a conundrum, and I think the OP should state this step in install steps, bc it is easily skirted by just reflashing Bonsai.
OK, thanks. May I humbly suggest that the Bonsai installation instructions have some additional steps for Bonsai newbies? Would it help to wipe to stock before the first installation? It's a bit much to expect everyone to read through the hundreds of posts on the bonsai thread, prior to the first installation.
It's such a good ROM, my phone seems to now have all the features working.
I'm very grateful & made a donation.
fsc137 said:
OK, thanks. May I humbly suggest that the Bonsai installation instructions have some additional steps for Bonsai newbies? Would it help to wipe to stock before the first installation? It's a bit much to expect everyone to read through the hundreds of posts on the bonsai thread, prior to the first installation.
It's such a good ROM, my phone seems to now have all the features working.
I'm very grateful & made a donation.
Click to expand...
Click to collapse
Yeah the rom is designed to NOT wipe, but for those of us just upgrading to CWM3, then to bonsai, are kinda forced to wipe (not wipe, but odin to a 'wiped', clean rom) which then causes the problems. Maybe he just needs to add the step for those who come from stock dk28.
That added step would probably be to flash something like Bonsai 1.1.4 after DK28 so that Bonsai 2.0 doesn't choke when it installs. IIRC, 1.1.4 still has dual file system support and could be done even before converting to cwm3/ext4.
Alot of.this is explained in the bonsai thread. It just takes a little bit of reading.
Sent from my Evo Killer!!!
I have to poke my head in a say that I was happy to see this thread as I have been reading the bonsai thread wanting to move to 2.01. but have been leary to, as I haven't read a post referencing if coming for a dk28 custom rom(rfs) with cwm 2.5.1 will work with a flash of cwm3 installer and then a bonsai flash. I love my setup now its so stable but I would like the improvements, and I like the idea of keeping all my data. I've seen a lot of talk of the issues discussed above from stock dk28, but my worry is more of cwm 2.5.1 should I be worried or will cwm3 work fine over 2.5.1? I do have to say that reading is absolutely necessary but alas I do think that most of the OPs for various roms could use a bit of work, but hey at least thy can code right? Thx everyone!
sent from "The Other Woman"
Once you get into CWM3 for the first time and EXT4 and everything is happily in place you should be able to wipe the phone completely (format /data /cache and /system) and flash the rom and it should be happy.. never had any kind of issues personally, but yes the script is designed to backup all your data and restore it, perfect if you're upgrading to a new version of Bonsai, bad if you're coming from a stock dk28 rom.. best to start with a clean slate once you've made the switch to ext4 I think.
upgrade to ext4 and CWM3 worked without wiping
As I said at the top of this thread, I had DK28 and CWM 2.5.0, no ext4, and did the Bonsai install without erasing anything. The first boot resulted in flaky behavior and locked-up switches, but a subsequent boot to CWM3 (after removing the battery after a couple minutes to turn off the phone) allowed me to re-install the bonsai zip file and then the OS seemed to be OK. At that point, I still had all my apps and data, but the apps from the marketplace could not write to memory. I had to delete them all and re-install from the marketplace, and then everything worked. It was a benefit not having to restore all my data and files.
bryanfritz1 said:
I've seen a lot of talk of the issues discussed above from stock dk28, but my worry is more of cwm 2.5.1 should I be worried or will cwm3 work fine over 2.5.1?
Click to expand...
Click to collapse
CWM3 will install over 2.5.1.x just fine.
You can install bonsai 2 with a combo of 2.5.1.0 and 2.5.1.2, but it takes a bit more work. At a minimum you will have to format to ext4 instead of letting cwm3 do it. I'm not sure if you would have to manually flash the no-journal mod or if bonsai will still install it through 2.5.1.2.
DiGi760 said:
CWM3 will install over 2.5.1.x just fine.
You can install bonsai 2 with a combo of 2.5.1.0 and 2.5.1.2, but it takes a bit more work. At a minimum you will have to format to ext4 instead of letting cwm3 do it. I'm not sure if you would have to manually flash the no-journal mod or if bonsai will still install it through 2.5.1.2.
Click to expand...
Click to collapse
Bonsai will install it.
Doesn't the bonsai rom have a transparent notification pull down? Mine is the regular stock looking notification pull down but with the circle battery indicator. Any suggestions?
Sent from my Nook color using the xda app.
Thx guys. I went ahead and took the plunge and with no major issues, cwm3 and bonsai 2.01 with frozen emotionless beast theme running great. The theme is growing on me more and more but I'm not so keen on the font, I think I remember a font changing mod awhile ago anyone know of one that is compatible with bonsai 2.01?
sent from "The Other Woman"
cnuckols1 said:
Doesn't the bonsai rom have a transparent notification pull down? Mine is the regular stock looking notification pull down but with the circle battery indicator. Any suggestions?
Sent from my Nook color using the xda app.
Click to expand...
Click to collapse
The themed version does, but Mammon has not released the theme for this version of bonsai yet.
Sent from my SPH-D700 using Tapatalk
Thanks thought I was going crazy.
Sent from my SPH-D700 using XDA App
bryanfritz1 said:
The theme is growing on me more and more but I'm not so keen on the font, I think I remember a font changing mod awhile ago anyone know of one that is compatible with bonsai 2.01?
Click to expand...
Click to collapse
I'm not sure what "mod" you mean. Fonts are stored in /system/fonts. If you rename any ttf font to the same name as the system fonts and overwrite the fonts that are in /system/fonts, you can change to any font.
Thank you I didn't realize it was that easy.
sent from "The Other Woman"
Hey folks, I'm hoping one of you can help me out with an issue that just cropped up on my phone. I've been running EB01 since it's release and have had no issues whatsoever except for today when I noticed my apps (Titananium Backup, Tapatalk, Root Explorer) we're remembering preferences anymore and/or every time I exit from them and launch again....it thinks it's the first run again.
Did something hose up my permissions/ownerships? Only think I did recently was flash the de-binged browser via CWM.
Any ideas??
What are you running? It may be a permissions problem. Have you tried uninstalling it and reinstalling it?
I'm having a similar issue. Help!
jpolzner said:
Hey folks, I'm hoping one of you can help me out with an issue that just cropped up on my phone. I've been running EB01 since it's release and have had no issues whatsoever except for today when I noticed my apps (Titananium Backup, Tapatalk, Root Explorer) we're remembering preferences anymore and/or every time I exit from them and launch again....it thinks it's the first run again.
Did something hose up my permissions/ownerships? Only think I did recently was flash the de-binged browser via CWM.
Any ideas??
Click to expand...
Click to collapse
I was just about to start a thread about this. I'm having the same problem. I upgraded from blackhole 4.1 (DL30) to Superclean 2.2 EB01 with voodoo lagfix. I got the red CWM flashed via odin and proceeded to install the EB01 modem and the superclean 2.2v (EB01).
The first time I flashed was a disaster, there were issues with Odin completing the flash, so I had to do USB pulls about 4 times (which ended up giving me full "light blue" screens during download mode at times).
After getting Odin to cooperate, I was able to flash the Superclean 2.2v (EB01), and then I restored everything from Titanium Backup, which worked fine until I restarted the phone or left it alone for a couple of hours. Everything would force close (like ADWLauncer Ex, forcing me to use ONLY TWLauncher) and all my preferences were lost. Like gmail would have to resync as if it were new, all the EULA dialogs would come up (like in android market), my trillian profiles were all lost, if i turned off haptic feedback that would turn back on, my ringtones would go back to the defaults, etc.
So I read some other thread in the Development section which said to reflash, and do not do any restores at all. So I reflashed with Super clean 2.3v (EB01), but it happened again, all my preferences would be lost. I also tried to do "fix permissions" from RED CWM, but it just ran for like a fraction of a second and didn't seem like it did anything, as the problem persisted.
I'm planning to go back to DL30 or even DL09 to see if my phone functioned properly or not.
If anyone has a solution to this problem please help!
- Superclean 2.3v (EB01)
I'm thinking it has something to do with flashing either the De-Binged browser or the new market update. Maybe something in the framework-res is getting hosed up?
I just did a wipe and reflashed plain old EB01 and I'm not going to flash any changes and see if the problem comes up again.
emortio said:
I was just about to start a thread about this. I'm having the same problem. I upgraded from blackhole 4.1 (DL30) to Superclean 2.2 EB01 with voodoo lagfix. I got the red CWM flashed via odin and proceeded to install the EB01 modem and the superclean 2.2v (EB01).
The first time I flashed was a disaster, there were issues with Odin completing the flash, so I had to do USB pulls about 4 times (which ended up giving me full "light blue" screens during download mode at times).
After getting Odin to cooperate, I was able to flash the Superclean 2.2v (EB01), and then I restored everything from Titanium Backup, which worked fine until I restarted the phone or left it alone for a couple of hours. Everything would force close (like ADWLauncer Ex, forcing me to use ONLY TWLauncher) and all my preferences were lost. Like gmail would have to resync as if it were new, all the EULA dialogs would come up (like in android market), my trillian profiles were all lost, if i turned off haptic feedback that would turn back on, my ringtones would go back to the defaults, etc.
So I read some other thread in the Development section which said to reflash, and do not do any restores at all. So I reflashed with Super clean 2.3v (EB01), but it happened again, all my preferences would be lost. I also tried to do "fix permissions" from RED CWM, but it just ran for like a fraction of a second and didn't seem like it did anything, as the problem persisted.
I'm planning to go back to DL30 or even DL09 to see if my phone functioned properly or not.
If anyone has a solution to this problem please help!
- Superclean 2.3v (EB01)
Click to expand...
Click to collapse
I'm having the exact same problem. I've been all the way down to DJ05 to see what happens, and when I come back to superclean 2.2 voodoo-ed, I get force closes on everything the first time I restart - that issue was due to the new feature froyo added "automatic restore" in settings > privacy. I got that taken care of by uninstalling all apps.
However, when I restart now, my entire phone defaults back to cleared data. I'm talking every setting that I could think of (usb debugging, sound, brightness, contacts, security pin cleared). I don't get it at all. Everything else has been working right though.
Just thought I would share - I'm kinda still in limbo till I figure out what I should do.
brettdacosta said:
I'm having the exact same problem. I've been all the way down to DJ05 to see what happens, and when I come back to superclean 2.2 voodoo-ed, I get force closes on everything the first time I restart - that issue was due to the new feature froyo added "automatic restore" in settings > privacy. I got that taken care of by uninstalling all apps.
However, when I restart now, my entire phone defaults back to cleared data. I'm talking every setting that I could think of (usb debugging, sound, brightness, contacts, security pin cleared). I don't get it at all. Everything else has been working right though.
Just thought I would share - I'm kinda still in limbo till I figure out what I should do.
Click to expand...
Click to collapse
I wonder if it has to do with the type of EB01 we're using or the CWM. I flashed CWM red via Odin, rather than updating via Rom Manager or update.zip. Also I used the EB01 Walkthrough in the fascinate developers section, the link is:
http://forum.xda-developers.com/showthread.php?t=948722
***UPDATE***
I resolved the problem... I think. I noticed there was a difference in the file names of the EB01 Modem in the walkthrough link I provided on the last line of the paragraph above and the EB01 Modem given in the original EB01 stock thread (http://forum.xda-developers.com/showthread.php?t=948679). I flashed with the eb01a_modem.tar given in the stock thread and then upgraded to Super Clean with Voodoo (v. 2.4 as of this writing). The market DID restore all the apps, before I was able to stop it, but after I restarted, there were no force closes nor were there any loss of preferences. I hope the modem issue was what was wrong...
Started doing it again this morning. This time I did not flash any mode via ROM Manager. Only things I did was de-bloat using Root Explorer and Titanium Backup.
Not every app started forgetting preferences, some still reemebered. Any of the devs have an idea of what's going on here? I'm running the plain old, fully-bloated EB01 ROM. No voodoo, no de-odexed, or anything like that.
I think it's a dbdata partition issue. I can't say how to fix because it's above my paygrade, but you may have to wait until it is officially released.
jpolzner said:
Started doing it again this morning. This time I did not flash any mode via ROM Manager. Only things I did was de-bloat using Root Explorer and Titanium Backup.
Not every app started forgetting preferences, some still reemebered. Any of the devs have an idea of what's going on here? I'm running the plain old, fully-bloated EB01 ROM. No voodoo, no de-odexed, or anything like that.
Click to expand...
Click to collapse
Try the Odin back to stock...DI01, wipe everything. Reroot and and get cwm. Then ODIN EB01 Modem Tar followed by super clean 2.4 install through cwm. Be sure to wipe data and cache before flashing super clean.
I there a reason I have to go all the way back to DI01, or can I use any All-In-One Odin package that writes the ROM, Kernel, & Radio?
jpolzner said:
I there a reason I have to go all the way back to DI01, or can I use any All-In-One Odin package that writes the ROM, Kernel, & Radio?
Click to expand...
Click to collapse
I suggest that typically before anything else b/c it seems to help most. I've never experienced these issues but many suggest this is a viable method to remedy certain problems. Don't see why you couldn't try the odin DL09 all-in-one and wipe the hell out of it and try again. Good Luck.
Is the corruption in the dbdata partition caused by an older version of CWM or a problem in the EB01 ROM itself?
Is it safe to go back to EB01?
jpolzner said:
Is the corruption in the dbdata partition caused by an older version of CWM or a problem in the EB01 ROM itself?
Is it safe to go back to EB01?
Click to expand...
Click to collapse
I believe it's currently inconclusive. There is speculation about exactly what causes it hence the reason I suggest wiping everything and then flashing the most recently provided stuff. That way it'll narrow things down. Someone can correct me, but if you odin back to stock, I'm 99% sure super cleans 2.4 voodoo kernel includes the new cmw. I was on green cmw unitl I flashed the seperate voodoo kernel posted by jt. I haven't had any issues.
Its almost certainly dbdata corruption. The cause is...yeah questionable. Seems most common with voodoo with the current hack being used to get it working with froyo.
Sent from my SCH-I500 using XDA App
I've never run Voodoo on my phone, but I did my initial install of EB01 with one of the older "Green" CWM versions.
adrynalyne said:
Its almost certainly dbdata corruption. The cause is...yeah questionable. Seems most common with voodoo with the current hack being used to get it working with froyo.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Any other suggestions or fixes?
I went all the way back to DI01, then flashed to EB01 using an Odin All-In-One and now 48-72 hours later, my apps (most notably Tapatalk, Root Explorer, and Titanium Backup) think it's the first time they've run every time I launch it.
Shouldn't have going back to DI01 fixed the corruption since it reformats the ROM partition? Also, something I notice was that flashing to DI01 or EB01 using odin did not get rid of the new CWM Recovery.
Would running the permission fix correct the issue?
jpolzner said:
Any other suggestions or fixes?
I went all the way back to DI01, then flashed to EB01 using an Odin All-In-One and now 48-72 hours later, my apps (most notably Tapatalk, Root Explorer, and Titanium Backup) think it's the first time they've run every time I launch it.
Shouldn't have going back to DI01 fixed the corruption since it reformats the ROM partition? Also, something I notice was that flashing to DI01 or EB01 using odin did not get rid of the new CWM Recovery.
Would running the permission fix correct the issue?
Click to expand...
Click to collapse
No...are you running voodoo? And what rom are you using?
EB01 Fully Bloated, Non-Voodoo Kernel
Baseband version: S:i500.04.V.EB01
Kernel version: 2.6.32.9
Build number: SCH-I500.EB01
http://forum.androidcentral.com/ver...roms-w-root-new-clockwork-updated-2-15-a.html
Try This...
This will hopefully repartition and clean dbdata corruption. BTW, I couldn't get 2.2 to run on my phone until I odin flashed a ROM which allowed me to then flash Adrynalyne's 2.4.
DI01, DJ05, DL09 did not work for the fix. Eclair worked fine, but Froyo would not work until I flashed a 2.2 odin.
Do I need to check the "Re-Partition" option in Odin when flashing or does it do it automatically?
I just Odin'd straight from DK28 to EB13 with no problems what so ever thus far, I thought everyone was saying it's not a possibility?
Not a possibility to update via flashable .zip not with ODIN
Seanc13 said:
I just Odin'd straight from DK28 to EB13 with no problems what so ever thus far, I thought everyone was saying it's not a possibility?
Click to expand...
Click to collapse
I think they were referring to receiving the OTA or updating with the zip file
Ah, ok I see, I've been wonderin all day while I was at school haha.
Oh, and am I the only one who still can't get a gps lock?
Edit: I got a lock accurate to 100 meters, better than the usual 2800 meters, but still not great
I still cant get a lock anywhere better than 2800 meters, running EB13, what can i do to fix it?
Seanc13 said:
I still cant get a lock anywhere better than 2800 meters, running EB13, what can i do to fix it?
Click to expand...
Click to collapse
It's actually possible (correct me if I'm wrong) that whatever you flashed through ODIN didn't have the modem for EB13. Going back to DI18 and then using the update.zip to get to EB13 is a sure-fire way to get the new modem...
Chances are you actually did get the modem though if you used the link to the .tar that was posted here... in that case I'm not too sure
Yea I used the modem posted here and in my setting it says EB13
try downloading gps status and deleting agps data thru the app.
I'm on a dk28 ROM with eb13 kernel and modem. My gps lock is quick and within 10 meters tops.
Sent from my SPH-D700 using XDA App
Good to hear. I was sick of idiots telling me I have to lose all my data and settings just to jump from DK28 to EB13 (froyo to froyo!).
nonzenze said:
Good to hear. I was sick of idiots telling me I have to lose all my data and settings just to jump from DK28 to EB13 (froyo to froyo!).
Click to expand...
Click to collapse
The only two ways to do this, either using the Samsung tool or Odin, will both completely wipe your data and settings. If you want to save your data make sure you do a nandroid backup before updating and then do an advaned (/data) restore with clockwork after you've updated and restored your root/clockwork.
There are more than two ways.
*Samsung tool (or Odin)
*update.zip (for fully stock system)
*cwm flashable di18->eb13. If you are on dk28, then use the cwm flashable di18 w/ modem in the wiki, first.
You will probably lose data and settings when flashing the di18 zip, but as mentioned before, you can do a backup and then restore /data once you make it to eb13.
edonnelly said:
The only two ways to do this, either using the Samsung tool or Odin, will both completely wipe your data and settings. If you want to save your data make sure you do a nandroid backup before updating and then do an advaned (/data) restore with clockwork after you've updated and restored your root/clockwork.
Click to expand...
Click to collapse
What a pain. I have my phone set exactly the bloody way I like it.
I can live with DK28 for the time being, maybe I'll flash once CM7 or some other custom ROM actually supports the Epic properly.
nonzenze said:
What a pain. I have my phone set exactly the bloody way I like it.
I can live with DK28 for the time being, maybe I'll flash once CM7 or some other custom ROM actually supports the Epic properly.
Click to expand...
Click to collapse
This is kind of where I'm leaning now. My phone works great, I have relatively few problems and introducing new ones just to get from DK28 to EB13 doesn't sound like a good idea at all.
Is the compass/accelerometer issue resolved in EB13? Will Google Sky Maps work properly? Does wifi turn on everytime, without error? If not, I have nothing to gain and everything to lose by even considering updating to EB13..
New Epic 4g - Rooted and Rommed
Hi, I just swapped out my Evo 4G to a Galaxy Epic 4G, I first was trying to figuring out how to updated to the latest mods but thanks to XDA developers i got it all working fast now. I first installed the Root one Click 3.0.0.5/6 and then i tried to install the Rom but it woulnt take it. So after reading much online, i figured i had to take it to Android 2.2 first to install one of the latest ROM's. si i did the Froyo 2.2 update and the I was able to Flash it using the One Click Root CWM3 Clockwork 3.0.0.6 and installed ViperROM Trinity 4.0.4 and now its running Fast and clean I also installed the Genocide 1.20Ghz EB13 Kernel V.0.2
I ran sum benchmark test and got:
16.561 mflops @ 5.06 sec Linpack
1773 on Quadrant
38.99 seconds on SQL
1315, 2948 on Smartbench
My Epic is Working great Thanks XDA-Dev.
nonzenze said:
What a pain. I have my phone set exactly the bloody way I like it.
I can live with DK28 for the time being, maybe I'll flash once CM7 or some other custom ROM actually supports the Epic properly.
Click to expand...
Click to collapse
Why is this a pain? Barely different than flashing a new Rom/Kernel:
1) CWM, make backup
2) Odin combo EB13/Root/CW (ext or RFS)
3) CWM, Flash EB13 Rom/kernel (required for ext4, optional for RFS)
4) CWM, restore data
I used Midnight 4.0 and Genocide 0.2a kernel. My homescreen, settings, apps, etc. all restored perfectly.
danmax2010 said:
Hi, I just swapped out my Evo 4G to a Galaxy Epic 4G, I first was trying to figuring out how to updated to the latest mods but thanks to XDA developers i got it all working fast now. I first installed the Root one Click 3.0.0.5/6 and then i tried to install the Rom but it woulnt take it. So after reading much online, i figured i had to take it to Android 2.2 first to install one of the latest ROM's. si i did the Froyo 2.2 update and the I was able to Flash it using the One Click Root CWM3 Clockwork 3.0.0.6 and installed ViperROM Trinity 4.0.4 and now its running Fast and clean I also installed the Genocide 1.20Ghz EB13 Kernel V.0.2
Click to expand...
Click to collapse
Well, that's one way to do it... as long as it works for you. I was thisclose to flashing ViperROM but it was delayed by a couple days... so I put on Nebula and two days later EB13 was confirmed. So I'm sitting here, waiting for the EB13 based Nebula (or CM6.2).
Hey, someone else from Orlando... cool.
mis3 said:
Why is this a pain? Barely different than flashing a new Rom/Kernel:
1) CWM, make backup
2) Odin combo EB13/Root/CW (ext or RFS)
3) CWM, Flash EB13 Rom/kernel (required for ext4, optional for RFS)
4) CWM, restore data
I used Midnight 4.0 and Genocide 0.2a kernel. My homescreen, settings, apps, etc. all restored perfectly.
Click to expand...
Click to collapse
The fact that you put up with this nonsense is really astounding.
An upgrade should *never* destroy anything on the phone. The homescreen, settings, apps being as they were -- I take that as an absolute non-negotiable minimum, not some amazing contrivance.
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