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.

why does this happen?

After I odined back to stock like 2 times, I flashed bionix. At first I had to push the froyo jl5 kernel with voodoo because rom manager couldn't install cwm. The everytime I reboot my phone, settings reset. Why?

try the KA7 kernel w/Voodoo and see if you get the same result.. any reason you want to use the JL5 kernel that Supercurio stated causes some problems in the OP???

dont' use cwm just flash through recovery wipe completely first manually,

helikido said:
After I odined back to stock like 2 times, I flashed bionix. At first I had to push the froyo jl5 kernel with voodoo because rom manager couldn't install cwm. The everytime I reboot my phone, settings reset. Why?
Click to expand...
Click to collapse
Sounds like you have some gremlins in your phone. I had a market issue that I tried everything on, and I mean everything. So, for kicks I installed the TW version of bionix and it fixed it right back up. Give it a shot. There's usually no clear answer for these things, but I always keep a version of rom manager and titanium backup on my external sd card for quick flashing. Shoot me a PM if your phone still gives you grief.

[Q] Fascinate Bricked, Need Help!!

I rooted my fascinate, flashed CWM with Odin, and installed one click lag fix. Everything was working fine for a few days, but today I started getting a lot of force closes, and then it just stopped booting. I can't even boot into CWM recovery, it won't access the update.zip file on the sd card. It won't boot to the OS, and just reboots to the stock recovery whenever I try to do anything. I have backups on CWM, but I can't access them. I'm trying to restore it to stock, and start over, but as I said, I can't access CWM, or get to the OS at all. Please help me get this thing running again.
Thanks,
Anthony

Flash one of the All in One Odin packages from the Development forum and you should be good to go.

And never touch OCLF again.

Any particular one I should be looking for? I was looking around, but the only one I saw had a busted link, and I couldn't download the package.

Downloading the DI01 and DL09 Odin packages. We'll see how that turns out. Use PDA option in Odin correct?

diesel43078 said:
Downloading the DI01 and DL09 Odin packages. We'll see how that turns out. Use PDA option in Odin correct?
Click to expand...
Click to collapse
Yes
And only PDA
Sent from my SCH-I500 using XDA App

DL09 flashed with Odin. Seems to be working great. Thanks for all the info fellas.

[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?

edit

delete

quikshifter said:
quick background:
Been using Android 1.5 across many phones, rooting, flashing, etc no issues until I met this samsung vibrant.I picked it up on Ebay to send to a friend overseas and been having problems with it. It seemed to work but when I rooted it it, everything began to force close ..etc maybe that's why it was sold.
The problem I am having now is I can't flash anything on it. I tried CM7, CM9, other ICS roms and everything goes into a bootloop. I can get odin to flash it back to 2.1, clockwork to boot but from there any flash seems to fail.
CM7 gives error as in "checking BML/MTD" and fails.
Can anyone recommend a rom to try on this thing and I will come back with errors I get?
Click to expand...
Click to collapse
When you say error, do you mean it reboots into recovery over and over again?

For CM9 I see a quick "cant mount" error and then it bootloops.. For CM7 its the MTD error.
I found somewhere I should tick re partition when I Odin back to stock and format my sd card.

Ok, yes, do a full odin back to stock 2.2 with all the boxes checked first; then install clockwork recovery, then flash cm7. If you get a bootloop error after it says "checking BML/MTD status", just pull the battery and go back into recovery and it should look different, then just flash cm7 again and you should be good to go.
You're basically installing cm7 twice, the first time is because it will bootloop to update your clockwork recovery (hence why it looks different after you pull the battery and reboot into recovery); the second time is to actually install cm7.

same thing flashing from the second clockwork that installs 5.0..etc.. any other advice?

quikshifter said:
same thing flashing from the second clockwork that installs 5.0..etc.. any other advice?
Click to expand...
Click to collapse
Ok, did you flash back to stock using odin and did it actually boot up into 2.2?

edit

usually when there's random force closes it's a permissions issue. Did you try to go into recovery and run a fix permissions?
Also did you try this? http://forum.xda-developers.com/showthread.php?t=848737

Yes. When I say Odin its those same exact steps and Yes I have done fix permissions.
I just found this post.
http://forum.xda-developers.com/showthread.php?t=797293
The author lists something about a bad kernel can cause this... I expected something like this. Which one should I flash?

That depends on which ROM you want to use....Bali, subzero, and glitch kernels all work really well

Force close apps even after odin
edit

Did you try any of these kernels here? Any kernel in the list except the i9000 kernels should be good. Also try maybe flashing a different modem although I don't think a modem will make a difference.

edit