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"
Related
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
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?
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
OK, so I am new to the epic 4g (it belongs to a friend, I have a cappy). I've flashed to stock, upgraded to E05, rooted with the latest one-click, and all that goes perfectly!
When I install bonsai 4.0.1 the installation goes flawless, but on bootup it keeps doing the FC vibrate and boot loops. I've tried 3 fresh installs but I am getting nowhere. I have also tried it doing the 3x wipes and without. I'm familiar with odin, so I know it's not something there. Any thoughts?
Having the same issue. Sadly.
*One thing I'll note is to ensure you are using ClockWorkMod 3, not 2.5. Wanna make sure you have the correct file type (EXT4).
I have tried to install Bonsai 4.0.0 & 4.0.1 multiple times and have had the same boot loop issue.
I love the Bonsai (3.0) Rom, which worked just fine w/ EB13, but has not worked at all since upgrading to EC05. I want to keep EC05 as bluetooth actually works.
I always odin back to Stock DI18 and update to EC05, then root using CMW 3, wipe date/cache/dalvik 3X, then install Bonsai 4 (and 4.0.1 one another attempt). The install seems to be successful, but I end-up stuck in the boot loop. I tried to re-flash the ROM after netting the bootl oop, but it errors-out in CWM.
Any ideas are greatly appreciated. I am crazy frustrated as there must be something simple I am missing...?
If you follow the instructions exactly you can't go wrong. Forget what you think you know. Bonsai is totally different than other roms out there...
Sent from my SPH-D700 using Tapatalk
I was having problems after installing bonsai, force closes, no call sounds, ect. I copied all the files on the sd card to pc and formated th sd card. I only put the bonsai rom on the sd card and then flashed. Put files that I wanted back on card after and everything is great. If all else fails try it, I have seen it work on several different epics.
Sent from my Premium Epic, bliatch.
Aron1980 said:
OK, so I am new to the epic 4g (it belongs to a friend, I have a cappy). I've flashed to stock, upgraded to E05, rooted with the latest one-click, and all that goes perfectly!
When I install bonsai 4.0.1 the installation goes flawless, but on bootup it keeps doing the FC vibrate and boot loops. I've tried 3 fresh installs but I am getting nowhere. I have also tried it doing the 3x wipes and without. I'm familiar with odin, so I know it's not something there. Any thoughts?
Click to expand...
Click to collapse
Did you update to EC05 with the "over the air" update? If so, there has been a lot of issues with that.
Yes, best to go back to eb13 prerooted with CWM3 and then go to Bonsai.
So am I reading that Bonsai 4 is incompatible w/ EC05?
I have gotten Bonsai up an running while on EB13, but no such luck since upgrading to EC05. I am not using the OTA update.
I have also heard that there may be issues w/ CWM 3 and EC05?
Any insights?
mrjuboy said:
I have gotten Bonsai up an running while on EB13, but no such luck since upgrading to EC05. I am not using the OTA update.
I have also heard that there may be issues w/ CWM 3 and EC05?
Any insights?
Click to expand...
Click to collapse
Bonsai 4.0.0+ is a EC05 ROM. It uses Framework and kernel source of EC05(heavily modded of course just like the other EC05 ROM's). But I too have been reading many reports from folks having issues flashing ROMs from stock EC05. Not sure if Sprint/Samsung has thrown some kind of roadblock in there or if it's something we are missing here, but it doesn't matter how you get there. If you are on EB13 when you flash Bonsai 4.0.1+ it will update the modem for you, so it's not necessary to be on EC05 when you flash the ROM.
As far as CWM goes, the Epic community is in need of an official version of CWM 3.
I got it to work!
Odin'd back to stock, completed stock upgrade to EB13, then installed CMW 3 and flashed Bonsai 4.0.1.
I did have to reflash Bonsai once in CWM, but I am now up and running on Bonsai 4.0.1 on the EC05 Kernal and loving it!
Thank you very much for your assistance.
Hey guys,
I recently tried flashing the Team Hacksung ICS port, Gummy Fascinate, and AOSPK and they all have the same issues for me. I understand that these are in an alpha state but none of the "Not Working" sections include the problems I am having. First, I cannot receive text messages but I can send them. Second, when exiting an app or the settings menu, the home screen takes five seconds to reset (all of the icons/dock are gone, only the wallpaper shows at first). Third, the launcher becomes incredibly slow after only a few minutes. I close out of all of the apps that are running using the new multitasking feature (holding the home button) but the phone remains sluggish until I reboot it. Then, it is lightning fast until I open any app. Fourth, scanning of my SD card seems to stop after a few seconds after booting. I have about 14 GB of music on my SD card and it only loads the first few artists. It does this every time I boot up so I can never see the entire library. Fifth, sometimes the app I am using will close and I am forced to wait for the home screen to reset, as I mentioned before. No error messages for force closing appears. Sixth (this is only a minor inconvenience but I want to understand why it happens), when I use SMS Backup + to restore my texts, the minute I leave the app or let the screen turn off, it returns to "Idle mode and I have to restart the entire process over again.
TL;DR I have a bunch of issues that other users don't seem to be having and they are not listed on the "Not Working" sections of the ROMs.
I would appreciate if anyone could help me come up with a solution to any one of these problems. I am looking forward to using ICS!
What method are you using to install ics based roms?
I flash back to stock EH03 and then follow these directions to the letter: http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
Those instructions are pretty good aside from the part in step 8 that suggests flashing the radio. It's already included in the EH03 package so it's just redundant, but those instructions are essentially the same as my procedure and I'm on build 6 without the issues you're experiencing (as are other people).
I'm curious if you have the same problems on other roms or is it just ICS? Have you ever messed around with overclocking and maybe got a bit aggressive? I know that if you're not careful and know what you're doing with the new overclocking and voltage control that are a part of glitch v14 you could certainly damage your phone. If it's just ICS roms and you've never messed with OC, I'm not really sure why you'd be running into those issues.
smokinbeanbean1992 said:
I flash back to stock EH03 and then follow these directions to the letter: http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
Click to expand...
Click to collapse
have you tried a different sd card?
I only have these problems on ICS. I don't flash EH03 everytime like it suggests in the instructions. My last SD card was fried by CM7 so this SD card is brand new and I'm pretty sure it's a class 10, so speed shouldn't be an issue. Could it really be the SD card that's causing these problems?
Sent from my SCH-I500 using XDA App
Also, I have messed around with glitch v14 and overclocking to attempt to alleviate the sluggishness and I used to use v12 and v13 with CM7 before with no issues. V14 did not help at all so I'm on the stock CM9 kernel and I have erased the voltage settings.
Sent from my SCH-I500 using XDA App
smokinbeanbean1992 said:
I only have these problems on ICS. I don't flash EH03 everytime like it suggests in the instructions. My last SD card was fried by CM7 so this SD card is brand new and I'm pretty sure it's a class 10, so speed shouldn't be an issue. Could it really be the SD card that's causing these problems?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I didnt say it was the sd card, just simply asked if you have tried another...relax grasshoppa. If you dont follow instructions expect stuff not to work right.
Not sure if it will make a difference, but I ODIN and repartitioned to stock verizon DL09.. then CWM, wipe, build two, wipe, gummyfassy...
I have run into some strange issues when I reverted to another stock verizon package other than DL09 before flashing custom roms.. so out of superstitions sake, I always default to DL09.
elarson006 said:
Not sure if it will make a difference, but I ODIN and repartitioned to stock verizon DL09.. then CWM, wipe, build two, wipe, gummyfassy...
I have run into some strange issues when I reverted to another stock verizon package other than DL09 before flashing custom roms.. so out of superstitions sake, I always default to DL09.
Click to expand...
Click to collapse
I use to have to do the same thing when I was on the stock sd card. Pretty sure the op did not odin back to stock anything going by his last post. I agree tho it wouldnt hurt to try stock ed05 or dl09, but dl09 should no longer be necessary.
I wasn't angry or anything, I was just wondering if the SD could be a problem. I always flash back to the stock EH03 ROM before flashing ICS or CM7 but do you think I should go all the way back to DL09?
Sent from my SCH-I500 using XDA App
I don't think it would harm anything to go to a more previous version. Make sure you repartition using the .pit file when flashing in ODIN if coming from MTD rom
Every time i tried all the ICSs I odined to EH03 as my starting point, then odined CWM4 fixed for CM7, then I flashed ICS Hacksung 3 first......Reboot...Reboot into recovery, Flash ICS 6 [or what ever new flavor you would like] then flash Gapps 7.1....Reboot.... Enjoy
Start from scratch and you will be good to go.
Droidstyles is the man when it comes to guides!
Ok, so at what point do you personally wipe data/cache/dalvik? I flash to stock, flash CWM fixed, wipe all three, install THS build 2, reboot, wipe all three, flash ICS rom of choice, flash all three, install gapps 7.1, and reboot.
Sent from my SCH-I500 using XDA App
usually before you flash a full rom:
Odin EH03
LET THE PHONE BOOT
pop battery
Odin CWM4 for CM7
[three finger salute]
Wipe the three
Flash THS 3
Let Phone boot, then reboot to recovery using the power button [DO NOT 3 finger!!!!]
Wipe the three
Flash THS 6 [or any of the others, you dont need to flash all three just which ever your end game is, i recommend THS 6 not 6.1 for starters]
*No need to wipe or reboot in between these two*
Flash Gapps 7.1
Then reboot and enjoy
Ok I'll give that sequence a shot. Thanks for your help everyone!
Well I don't know what it was but my phone is working flawlessly now. Thanks again everyone!
There is a thanks button for this...
Ah yes, I forgot about that
smokinbeanbean1992 said:
Ah yes, I forgot about that
Click to expand...
Click to collapse
Pretty sure your issue came from wiping the 3 after you flashed ics.
Should go like this
after flashing build 2
Wipe the 3
Flash your choice ROM
Flash gapps
Reboot
Sent from my SCH-I500 using xda premium