Database Users

[HOW TO] Use Reorient Kernel V1.3 with Tayutama's i9000 ROM and HSUPA[UPDATED 9.29]

First off, I would like to say I did NONE of the work of making these amazing mods for the Captivate or i9000. NONE. I just figured out a good order to make them work well with each other.
All thanks for the work goes to:
xcaliburinhand for the i9000 Reorient Kernel. Without this, it would not be possible to do this and have it work right.
Tayutama for his ROM. It is quite nice too look at, and works great.
DesignGears for the Odin One Click.
REAVER117 for posting the Bell Vibrant Modem.
All those thanked by the aforementioned. Without great people like these we would all be basically stuck with an iOS knockoff. (touchwiz)
DO A NANDROID BACKUP FIRST IF YOU WANT TO SAVE YOUR DATA. Titanium Backup will work as well if you do not mind losing settings and logs/SMS/MMS.
Tayutama's ROM, get the NON VOODOO version(very important)
xcaliburinhand's Reorient Kernel(I recommend the update.zip method)
Stock Captivate Kernel from Koush
Get the JM9 i9000 ROM from SamFirmware
Get the CSC file (OXA) from Here
And finally, Bell Vibrant Modem from REAVER117(Others may work, but I used this one and it DOES work)
Get the JG8 modem here: MultiUpload
I will upload a .zip I did over the weekend from home later, it has all necessary files.
Once you have these components and have backed up your Captivate, follow these steps and you should be up and running on JM8 with Tayutama's ROM and HSUPA.
1. Flash to stock with Odin One Click
2. Flash to JM9 PDA in Odin 1.0 or 1.3 (CSC optional, I do it to remove all traces of AT&T)
3. Flash v1.2 of the reorient kernel(Allows button press in recovery mode, stock captivate kernel should also work) in Odin v1.0 or 1.3
4. Flash JG8 modem in PHONE portion of Odin(can be done at same time as step 2 and 3)
4. Flash Tayutama Full, Lite, or Super Lite 1.2 update.zip, NOT THE VOODOO package through Clockwork mod recovery. Flash supplementals like stock lock after this step.
5. [OPTIONAL]Restore Nandroid backup(Data only though Advanced Restore or Titanium Backup(optional, nandroid restore CANNOT BE DONE AFTER VOODOO without disabling lagfix)
6. Flash Reorient kernel 1.3 with Voodoo and BLN through the ClockWorkMod update.zip method
7. Reboot and enjoy!

Screenshots
(I am using Launcher Pro, NOT SENSE! I just did that to trick my boss who is an HTC junkie)

I don't see any files posted by Zilch25 in that modem thread. Do you mean the Vibrant Bell modem posted by Rever117?

no driver said:
I don't see any files posted by Zilch25 in that modem thread. Do you mean the Vibrant Bell modem posted by Rever117?
Click to expand...
Click to collapse
Yeah that's why i edited my first post, I remembered incorrectly.

Gonna try this out later
Sent from my SAMSUNG-SGH-I897 using Tapatalk

You should include that you need to actually download the JM8 firmware. I was following the directions and then realized that there was no link to JM8 itself haha I almost flashed Tayutama's ROM directly w/o going to JM8 first!

So what are the positives and negatives? Is it better or faster than Cognition?

Must have linked to one of the few threads I didn't post it in

Quick Question:
In the instructions you say to flash the Reorient Kernel 1.3 through update.zip method, so I am assuming that means in stock recovery. However, when I try to install via the stock recovery I get the "installation aborted" message. Can I install via Clockwork Mod Recovery?

KCutrer1 said:
Quick Question:
In the instructions you say to flash the Reorient Kernel 1.3 through update.zip method, so I am assuming that means in stock recovery. However, when I try to install via the stock recovery I get the "installation aborted" message. Can I install via Clockwork Mod Recovery?
Click to expand...
Click to collapse
Yeah use Clockwork.

irtehun said:
Yeah use Clockwork.
Click to expand...
Click to collapse
Thanks. I went to the Reorient Kernel thread to check how it's installed over there and they said Clockwork as well. Working pretty well right now!

KCutrer1 said:
Thanks. I went to the Reorient Kernel thread to check how it's installed over there and they said Clockwork as well. Working pretty well right now!
Click to expand...
Click to collapse
Gonna be switching to windows and flashing this setup here real soon.

Ughh.... I know this was gone over before the site crash but I'll post my experience. I flashed this setup following the steps to a T but for some reason my Quadrant was lower and the phone seemed like it was running a little slow, checked my speed test and averaged about 400-500kb down and up, and my phone signal was shotty. So I flashed back to stock with Odin then flashed Cognition 2.1. As soon as I was done flashing I noticed I had no signal. This was sitting in the same spot where I normally have 4-5 bars. Now here's where my heart sunk. I came to XDA looking to find the fix cause I knew I had seen it somewhere on this thread.... and... site's down. My phone is a company phone so not being able to make or take calls puts a little damper on things. So I flashed stock about 4 more times and had the same result every time. Finally I gave up and tossed the phone on my counter. While making my daughter something to eat I just happened to look over at it and what do I see...? FULL BARS. Not sure if anyone cares or not but thought I'd tell my story. I don't know what caused it to stop working or what caused it to start working but that's my experience. Could just be me doing something wrong also.

Bah 24 hour forums data rollback =(
Glad it just randomly came to life for you though... we'll chalk this one up to a "samsung problem"

crap. where'd all the posts go?

I got mine to work after the forum went down. I did all the Odin flashes and then the 3 button flash worked for the rom.
Question though. If I use mods like the circle battery mod should I get the one from the captivate forum or the i9000 forum, or are they the same?

wmwilker said:
I got mine to work after the forum went down. I did all the Odin flashes and then the 3 button flash worked for the rom.
Question though. If I use mods like the circle battery mod should I get the one from the captivate forum or the i9000 forum, or are they the same?
Click to expand...
Click to collapse
You'd prob wanna use the i9000 versions.

irtehun said:
You'd prob wanna use the i9000 versions.
Click to expand...
Click to collapse
Thanks
Going to give that a try

After running this command.
am start -a android.intent.action.MAIN -n com.android.Preconfig/com.android.Preconfig.Preconfig
I have no XEU setting in there.
So right now i am stuck in KOR.
any fix for this?

I gave up on this. Just not working for me.

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

[Q] Few questions about custom Epic ROMs

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

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

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

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

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

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

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

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

[Q] EB01 - Application not remembering preferencess

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?

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

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

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

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

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

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

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

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

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

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

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

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

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

3g
Sent from my SGH-T959 using XDA App

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