Database Users

Larger NAND Voodoo Fix

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

For ANYONE having difficulty installing TnT Lite 2.00-2.xx

Read This
http://forum.xda-developers.com/showpost.php?p=9542514&postcount=662

Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.

Still not that simple for me, since even a "Gtablet Vet" like myself tried the OP method and failed. My second out of box new Gtablet went in perma-loop when simply installing straight to 2.0, via recovery folder & update.zip. Ended up having to get CW on the device by putting on the sd card, remapping command and stopping the loop with power + volume to get CW installed. I then had to install TnT 1.02 and then finally got 2.0 installed after that (cache and data wipe of course).
Cleanest way seems install 1.02 via recovery folder / update.zip method and then install 2.0 the same way. Thats is unless I just had bad luck with second Gtablet. VERY possible.
added:
Frankly, we seem at the stage now where CW seems a survival requirement- IF you want to keep trying new roms & updates.

roebeet said:
Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.
Click to expand...
Click to collapse
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task

LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.

roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
Installing TnT 1.0 roms appears to zap CW pretty good.

roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
I have found that you can put the stock recovery img (let's call it recovery-stock.img) on the sdcard and get an adb shell while booted into cw recovery. Then it's just a
Code:
flash_image recovery recovery-stock.img
That should get you back to stock recovery.
Sent from my Incredible using XDA App

LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
I had to go back to stock at first because I kept getting status 7 errors with CW. Roebeet's suggestion to partition sdcard with CWR seems to have solved that.
Sent from my Incredible using XDA App

Flashed 2.0.0
I liked TnT 2.0.0 and it really helped performance but the gtab is still full of issues....
Out of the box my Gtab's proprietary email and photo app forced closed before ever loading. the viewsonic update didn't fix it and so I flashed it with TnT 2.0.0.
I got a System UID's warning while I did it and I guess that was the cause of those apps not working. I then did a system reset to factory default or whatever its called and lost everything but after flashing TnT 2.0.0 again it worked a lot better and the email app worked great, photo app still doesn't work. My new problems are that the sound and and flash don't work anymore. I reinstalled flash and the browser just crashes whenever flash is involved with a site. Sound will sometimes work when I first boot up but it quits after a while, especially after waking from sleep. A lot of the time I get crackles and pops when I first boot up or wake it from sleep.
I am returning this Gtab and I am going to buy another one from somewhere else in hopes that I don't get these issues out of the box.....I haven't read anywhere that anyone has experienced these specific problems other than the sound; as this is a TnT error; so I warn all, DON'T BUY FROM STAPLES!!!

New to epic =)

hello just got my new epic 4g about 3 hours ago i just came from the samsung mesmerize and before that i was on captivate so far i am loving the epic (because of the keyboard) well i was looking at roms and things seem really different compared to the mesmerize... the rom i was looking at was the Frankenstein FROYO rom and i am looking forward to pick up and test out that rom but the thing is i am a little confuse on some of the things it wants me to do like the whole DK28 modem thing and the convert to ext4 system..... what is this stuff about? and also the whole No Journaling thing? so far i am rooted and thats about it on my phone where should i start lol

Welcome! I also use Frankenstein ROM.

Ok. The dk28 is our froyo leak that we have. If you go into settings and about phone and look at the baseband version that tells you your modem version. If you update to dk28 then the baseband version should say dk28. If you update to dk28 using Odin to flash the rom it will automatically update your modem. The ext4 thing is changing our filesystem from stock Rfs to ext4 which is a lot faster. When you update to dk28 use the one click root with clockwork mod version 3 and once finished boot into cwm by using power down,camera and power button and the cwm3 will automatically convert your filesystem to ext4. The no journaling mod speeds up the phone by about 15%. Having journaling is enabled to protect your data. If you bare in the middle of something and your battery dies it is there to protect it. Now when you disable it you just gave to be careful to Jake sure your battery doesn't die while your doing something cause it could corrupt your data. I've been using it for almost a month and I haven't gad any trouble. Good luck. Anymore questions just ask.

Midnight+midnight theme ftw
Sent from my SPH-D700 using XDA App

Welcome! Glad to hear you are enjoying the Epic so far. I use MeatROM. It works really well, especially with ext4.
Sent from my SPH-D700 using XDA App

Musclehead hit everything spot on, though I'm not sure exactly how much no journaling speeds up your processing capability. I'm on Viperrom Frozen, which uses EXT4 and flashes through CWM3. I think it's terrific. Tried Bonsai but it was too stock for my taste. It's a barebones, clean deal with Bonsai. I go more for the theme and baked in stuff personally.

so im a little lost here i am following this guide to upgrade to 2.2 http://briefmobile.com/how-to-update-sprint-epic-4g-to-android-2-2?cp=5
when i try the first way it says update verification failed
and the 2nd way in odin says SPH-D700-DK8-8Gb-REL.tar.md5 is invaild and then end sooo im a little stuck here and when i use the one click root with CWM3 it wont boot into the CWM it still stays in the standered manger

now i am stuck even more i got CWM3 to install and right after it it turned my phone into a ext4 system it wont boot and stays on the samsung screen =/ and i have the update.zip on my sd card but it is still giving me a error saying error 7

icebear8 said:
now i am stuck even more i got CWM3 to install and right after it it turned my phone into a ext4 system it wont boot and stays on the samsung screen =/ and i have the update.zip on my sd card but it is still giving me a error saying error 7
Click to expand...
Click to collapse
If you run CWM3/Ext4 on your 2.1 install it will bork and get stuck on the Samsung screen. CWM3/Ext4 only works with DK28.
I don't know if you could apply a zip via CWM3 (while installed on 2.1) or not, I would wager you couldn't... but since the DK28 update should apply all the changes as you would by flashing I'm not sure.
The proper process is DK28, then CWM3/Ext4, then rom.
If your DK28 tar file is giving an error in Odin before you even try to apply it, download it again and retry; something got messed up in your download most likely.

ok got my phone to go back to stock 2.1 with the odin way soo gonna try and download the dk28 file again and see where that takes me

icebear8 said:
ok got my phone to go back to stock 2.1 with the odin way soo gonna try and download the dk28 file again and see where that takes me
Click to expand...
Click to collapse
Yeah give that a go if the new file checks OK, odin it to get to 2.2 (or you could download the update.zip if it is still floating around out there and install it via the samsung recovery). Boot it up and get your gmail configured etc, then go to debugging mode and run CW3 again.
Reboot into CWM3 and let it finish, then it should boot right up to the phone again. The pick a rom (if you want one) and apply it in CWM3. Just make sure the rom is compatible with ext4 and CWM3. Some are compatible with neither, some with ext4 but not CWM3. It usually says in the thread title which it is.

ok redownloaded it and installed my settings says i have 2.2 and the baseband says DK28 and did the CWM3/ext4 and now im stuck at the same samsung screen again

icebear8 said:
ok redownloaded it and installed my settings says i have 2.2 and the baseband says DK28 and did the CWM3/ext4 and now im stuck at the same samsung screen again
Click to expand...
Click to collapse
After you ran the CWM3 batch file, did you reboot into CWM3 to let it finish the installation (down volume, camera, power button at same time to turn the phone on)?
If yes, did it complete without errors?

this is what i am doing right after i installed the DK28 file i started my phone and used the oneclickCWM3 root it went thru fine and started up fine so i reset it and did the whole cam,power,volume down stuff and then it went into CWM and was updating my file system to EXt4 and then after it said complete it restarted and then just hangs in the samsung logo

At the CWM3 menu, you have to install a ROM from zip file.

ok everything is good just need to know if my undervolt took in dont know how i find out about that

So you got past the cwm3 conversion? Yeah you needed to flash a rom or it would get stuck. What undervolt mod are you talking about? What rom did you flash?
Sent from my Evo Killer!!!

I did the franken rom it said that it had the undervolt option in it so I downloaded that and threw it in with the rom
Sent from my SPH-D700 using XDA App

Flaky first boots with CWM3 & Bonsai

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"

Truly Epic Problem

I just flashed from Truly Epic 1.2 (was working) to Truly Epic 1.5 using CW. After rebooting the phone gets stuck on the Samsung screen. I tried wiping and re-installing 1.2 and it gets stuck on the Samsung screen also. Any suggestions? Thanks.

When I try to flash 1.5 I get the message cant open cache/recovery/log

chrylaser said:
When I try to flash 1.5 I get the message cant open cache/recovery/log
Click to expand...
Click to collapse
Odin time for you
Epic 3.5g | Syndicate Rom
Nook Color|My own honeybunches (sd), nookie froyo (eMMC)

I don't know to much about that rom but are you using the correct cwm version?
Sent from my Evo Killer!!!

Yes. CWM. I went back to stock DK28 with ODIN and still get stuvk when trying to flash 1.2 or 1.5.

chrylaser said:
Yes. CWM. I went back to stock DK28 with ODIN and still get stuvk when trying to flash 1.2 or 1.5.
Click to expand...
Click to collapse
Does your CWM have green or orange text?

Green. Any help is appreciated.

Ditto ya gotta find cwm3.0.0.5
Sent from my SPH-M900 using XDA App

chrylaser said:
Green. Any help is appreciated.
Click to expand...
Click to collapse
You need to convert from RFS to EXT4 by flashing CWM 3.0.0.1. Follow this link, then click the link in Step 1 of the install instructions. You'll have to create an AndroidCentral user in order to download the files needed, but this is the guide I used to convert my phone over so I know it works.

I installed CWM 3.0.0.5 and it still gets stuck. Now I am getting boot loops. Thanks for all the input.

I got Truly Epic 1.2 to run and select update.zip by mistake. Think that might be affecting everything? I cant even get 1.2 to flash now.

chrylaser said:
I installed CWM 3.0.0.5 and it still gets stuck. Now I am getting boot loops. Thanks for all the input.
Click to expand...
Click to collapse
hmm, everything you're describing is pointing towards the FS being RFS still.
If you are flashing TER 1.5 with a CWM with green text, your flash of CWM3 (orange text) didn't take.
Here's what I would do in this situation:
1. Odin back to DK28
2. Reflash CWM3
3. Flash TER 1.5
Again, I would use the thread I linked in my previous post as I know it works.

chrylaser said:
I got Truly Epic 1.2 to run and select update.zip by mistake. Think that might be affecting everything? I cant even get 1.2 to flash now.
Click to expand...
Click to collapse
That may have something to do with it, depending what update.zip was on you SD card.

i think theres definately something up with truly epic.. i had to restart my phone just now and i got stuck in a boot loop.. tried to reflash.. same problem.. tried to flash a different rom.. same problem.. i had to delete everything to get it to work again.. sucks

Anyone having a problem going from TER v1.2 to TER v1.5 using the full version (auto backup/restore) try using the TER v1.5 clean version now offered. It has the auto backup/restore removed.
TrulyEpic Rebirth v1.5 Clean Install
Make a NANDROID backup in CWM3 as usual
Wipe 3x
Flash and Enjoy
Any FC's from framework.google (FC errors) try rebooting into CWM3 and select Fix Permissions. That should do the trick.

Should I try to delete all the files off my SD card, ODIN back to stock DK28 and put on a fresh CWM 3?

Curious to know how different 1.2 and 1.5 are. Been on 1.2 for a week and is very stable. Only complaint is with multitasking in browser. Seems like it pauses page load if you run another app while waiting completed loading. Definately liked the benchmark scores. Sql even beats viperrom on ext4

tpike said:
Curious to know how different 1.2 and 1.5 are. Been on 1.2 for a week and is very stable. Only complaint is with multitasking in browser. Seems like it pauses page load if you run another app while waiting completed loading. Definately liked the benchmark scores. Sql even beats viperrom on ext4
Click to expand...
Click to collapse
See the changelog.