Database Users

Viper Rom DK 17 2.8

I know there is a Dk 28 version now but I'm still kind of new to the game and want to fully understand everything b4 moving on. I was able to get viper rom dk 17 2.8 installed this wkend after a bunch of mistakes on my part. Everything seems to be working well on this version except for the fact if I go to any web page that requires me to log in. When I click on where I type in my username or password the page will force close. Seems like some sort of security issue. Is there a setting I can change or is this a limitation of DK 17 version. Thanks for your help.

For future reference, this post should go in the Question and Answers section.
That being said, DK17 is an older leak, therefore support for it is going to be minimal. It also wasn't around all that long, so devs didn't spend a huge amount of time on it. The DK28 roms are going to be more stable.
If I were you I would go to this thread : Return to Stock
- Once your phone is back to stock, root it again like you did the first time using the one click.
- Download and install the DK28 modem and pit file using Odin. Should be the same steps you took to install the DK17 modem and pit.
- Then download one of the DK28 roms, i.e. viper, bonsai, quantum. Install those from clockwork.
If you need steps explained a little better than post, but don't do anything you are unsure of, cause you don't want to turn your phone into a paper weight.

swanysto said:
For future reference, this post should go in the Question and Answers section.
That being said, DK17 is an older leak, therefore support for it is going to be minimal. It also wasn't around all that long, so devs didn't spend a huge amount of time on it. The DK28 roms are going to be more stable.
If I were you I would go to this thread : Return to Stock
- Once your phone is back to stock, root it again like you did the first time using the one click.
- Download and install the DK28 modem and pit file using Odin. Should be the same steps you took to install the DK17 modem and pit.
- Then download one of the DK28 roms, i.e. viper, bonsai, quantum. Install those from clockwork.
If you need steps explained a little better than post, but don't do anything you are unsure of, cause you don't want to turn your phone into a paper weight.
Click to expand...
Click to collapse
Will do. Thanks for your help.

[Q] DL09 Quick Questions

Hey everyone! I hate to take up another thread but i like to be as sure as possible when it comes to messing with ODIN, since from what i understand that is where most people have likely bricked their phone.
Currently im running sonofskywalkers 2.3 rom i believe with DI01. I want to update to the newest one, which from what i understand means i need to upgrade to DL09.
My question is they say not to flash 01 stuff to over 09, so do i need to completely revert back to stock to push the new stuff since the rom i am running currently is for 01. Or am i safe to go ahead and update the radio and stuff, and boot up and get into rom manager to download the newest rom?
Thanks for your patience community and quick and helpful responses.

You are fine flashing over what you have, the issues mainly come up when you don't flash all the parts together (ROM, kernel, modem).
As far as Odin goes, as long as you use the PDA function, and not the PHONE function, you will be fine.
Edit: BTW, are you running a voodoo kernel? If so, that needs to be disabled before proceeding

For one, make sure voodoo is disabled if its on your kernal. If thats okay, then I would just odin this and then try to find a root method that would work. Or instead of rooting your stock, just flash a rooted rom onto your phone after the full odin.
BTW if you do want to keep stock, know that it can be a pain to get root to work. For some people it can be annoyingly hard, while others are able to use something simple such as the one click root. I was able to get one click to work, but it varies. If something goes wrong, you can always just re-odin the full package again.

I thought i might add here that you mentioned reading not to flash di01 stuff over dl09.
What that means is after you odin the dl09 upgrade you should no longer flash roms, kernels, themes and such that are not dl09. Flashing a di01 kernel would not work once you upgrade to dl09.
Hope this helps.
Have fun
Sent from my dl09 fascinate through xda app.

Consequences to updating to Tmobiles 2.2 froyo official

So I got the Vibrant the other day and for the most part I absolutely love the phone. Feels like I'm holding a light sabre or a magic wand. The thing is just so powerful. I have been reading up as much as possible on how to flash ROMs and root. A month ago I'd never even heard of this stuff and now I feel like I at least have a basic knowledge....just don't have the balls to attempt it yet. I want to make sure I know what I'm doing.
So in the meantime (while I work on growing a pair and actually doing it) I want to update to the Tmob 2.2 froyo official. I have read that if I do this I won't be able to get in download or recovery mode. Is this correct? And if this is correct then does that mean it will be impossible to flash roms after updating?
I just want a little performance boost and have my system a little snappier til I decide if I'm gonna flash some roms or not. Anyone know the answer?
Thanks fellas

If you can muster the balls to get the official 2.2, just flash team whiskey s bionix. Its better, easier, more reliable, better supported, and looks cooler. Don't be scared, follow directions and its easy!! GL!
Sent from my SGH-T959 using XDA App

In all seriousness, you're far better off flashing the latest Bionix-v than you are the "official" 2.2. Having done both, you are far more likely to have an issue during the update process using that garbage mini Kies program than you are rooting and flashing. I rooted and flashed 4 different ROMS without issue. Then I used ODIN to go back to stock because I wanted to see the official release.
4 hours later I was able to get my phone back to a usable state. Between driver issues and crappy software (Kies), it just wasn't worth it. And after using my buddies Vibrant that was running the official release, it was way slower and less usable than most of the latest ROMS offered here.
You should root and then flash the latest Whiskey or Axura ROM and be done with it. The devs here have given us a far better experience and options on our phones than Samsung has.

Actually, the official 2.2 tmo update got rid of the hardware lock for me. I couldn't get into recovery or download mode out the box. The previous JI6 update through Kies mini didn't help. Since I am no longer hardware locked, I'll probably flash some roms. I am pretty dissappointed with this official update after that long wait.

I agree with the other comments that just getting one of the better/faster ROMs here is going to be what you want. As for your question about getting the "official" update and then being able to flash, that's what I did so it should work for you with just a little reading.

I disagree...I love team whiskey and all the other custom roms and even used them for a long time. But right now I have been using stock 2.2 ka7 with voodoo kernel and it is really fast and snappy. I like the stock look as well and haven't experienced any bugs or slowdowns since I installed this rom ...my suggestion: if you want stock....then read up a bit and Odin to ka7...mini lies is the worst program invented and it only flashes you to ka6
Sent from my SGH-T959 using XDA App

Don't download the official! Take your time, read a lot, grow a pair and then execute! You'll be alright. confidence comes from research and doing. Everyone was nervous at one point.
Sent from my SGH-T959 using XDA App

tmo throws people in jail for flashing custom roms making our phones super amazin and they dont want that so remember to odin back when u bring ur phone for warranty

Yaz75 said:
In all seriousness, you're far better off flashing the latest Bionix-v than you are the "official" 2.2. Having done both, you are far more likely to have an issue during the update process using that garbage mini Kies program than you are rooting and flashing. I rooted and flashed 4 different ROMS without issue. Then I used ODIN to go back to stock because I wanted to see the official release.
4 hours later I was able to get my phone back to a usable state. Between driver issues and crappy software (Kies), it just wasn't worth it. And after using my buddies Vibrant that was running the official release, it was way slower and less usable than most of the latest ROMS offered here.
You should root and then flash the latest Whiskey or Axura ROM and be done with it. The devs here have given us a far better experience and options on our phones than Samsung has.
Click to expand...
Click to collapse
The only time you'll have an issue is if you're too dumb to turn on debug mode. And most of those people who are too dumb to do that were likely too dumb to read the threads where it was repeated ad nauseum to turn debug mode on...
Turn on Debug Mode
Update
Format Internal SD
Factory Reset
Enjoy.

N8ter said:
The only time you'll have an issue is if you're too dumb to turn on debug mode. And most of those people who are too dumb to do that were likely too dumb to read the threads where it was repeated ad nauseum to turn debug mode on...
Turn on Debug Mode
Update
Format Internal SD
Factory Reset
Enjoy.
Click to expand...
Click to collapse
Well thank goodness you aren't talking about me because I did have debugging mode turned on! And then mini Kies started to update the firmware, then it decided to crap the bed at about 75% and turned the phone into a confused jumble of uselessness.
But I guess you were there so I'll let you tell everyone how I recovered it.

bartek25 said:
tmo throws people in jail for flashing custom roms making our phones super amazin and they dont want that so remember to odin back when u bring ur phone for warranty
Click to expand...
Click to collapse
What the heck are you talking about?!

So thanks to some of the competent answers from guys in here and a leap of faith and trusting my extensive research (I read way too many threads about rooting, flashing, odin, custom roms, etc..), I am now rooted and have backed up my system. To be honest I'm almost just happy with that. While completeing this process I ran into a few questions that I didn't have the answer for mainly revolving around wheter to reboot or reinstall from recovery mode whether it be clockwork or samsung.
I posted a question in the Q and A forum about it (so I apologize for the kinda double post but this is more of a update on my progress) but whats the deal with update.zip file? I don't know when to reinstall it from recovery and when to delete it once the phone has booted. Should I delete it every time I have booted back up or does it even matter?
Thanks guys. I'm the kind of guy that, once I have the knowledge I am just as willing to share. Hopefully a year from now I'll be in your shoes and able to help others.
Next up after the update.zip question is resolved in my mind I plan to flash to bionix v. Official froyo 2.2 be damned lol

You use Clockwork Recovery to backup or flash anything. Sometimes you will get the Samsung recovery and you'll need to select reinstall packages to get to Clockwork. Sometimes you'll even need to reinstall packages twice.
Leave the update.zip on your sd. That's a necessary file for Clockwork.

[australia] android-v2.3.3 (optus)

anyone with an australian handset had much luck installing android v2.3.3 on their device without the help of a 3rd party rom like darkys or ultibread?
ive managed to install (original-xxjvk) functioning on samsung galaxy s with only a custom kernel if anyone is interested in a howto. ive only had my galaxy for a few weeks and have only managed to get it running myself without forced closes etc.
i dunno if anyone is having the same amount of trouble as i am trying to hook into android v2.3.3 but i think ive mastered it for aussies lookin to use the latest android on australian networks no hassles. i just didn't want to post a howto for something everyone has already worked out lookin like a fool. heh.
any replies appreciated.

I've been running stock JVK for about a month now, and Stock JVB since Saturday, Virginmobile (phone from Optus). No issues here.

Stock jvk with fugu mod, rooted and voodoo 7 sound with camera mods. I turned Hspda off today and since 7am till now 5pm still have 78%(and I use it fairly heavy). Runs well only thing I want next is android lockscreen and I'm happy.
On Virgin.
Sent from my GT-I9000 using Tapatalk

It took me a good 7 hours, haha all night trying to get GB on mah phone... had all sorts of problems as well.
Eventually, I installed I9000XWJVH, and it seems to be going good.

^^^
Just in time to flash 2.3.4 this evening

Downloading it right now.
Just worried about me having a non-stock kernel... using CWM (I think) with CWM Recovery... (CF-Root-XW_NEE_JVH-v3.2-CWM3RFS)

Are you flashing with Odin?
It wouldn't be a bad idea to flash the stock firmware first to get the updated bootloaders.

Yeah, I am using Odin.
flash stock jvh again?

Nope...
If you have your filesystem converted to ext4, just convert back to rfs.
If you really want to be sure of a clean flash, flash a 3 file firmware with a 512 pit and re-partition.

ok, well, I have no idea if I have ext4 or not... I don't remember ever seeing or doing anything with that, so, I am assuming I am still on rfs.
I have 3 files and a pit for the JVP. Do I just use those and flash with odin + repartition and that's it?
Don't need to do anything before?

I had stock JVK running for quite a while with no problems but with all the tasty looking ROMs out there I gave up and went for Simply Honey. First was using Darkys which was nice but SH wins me over with its lush blue-look =)
Now running JVO with no issues. Can get 6-8hrs heavy usage out of my phone =)

I know this sounds really blonde, but...
I'm trying to find a way to upgrade my Android OS to 2.3 (from 2.1) - however my phone is locked to Telstra and I'm finding it difficult (with my limited knowledge of Android) to upgrade.
Can someone please help me out? I'd be so grateful!

I found the best Guide to be: [GUIDE] Flash/Install/Update to Gingerbread 2.3.4 to I9000: Detailed guide for n00bs
It isn't too difficult but do read, re-read & go through the steps a few times before committing any changes.
Be prepared though... This flashing thing can get quite addictive as there seems like there is always another ROM that does just a little more than your current ROM & often just a little faster.
Good luck.
Oh - To keep all the grumpy forum members happy, do a quick search before asking a question such as this. You are not the first to ask this and there are many threads that have covered possible answers.

Just Updated to 2.3.3 Unbranded from Darky's Rom.
Had to Downgrade to 2.2 then to 2.3.3 as Odin just kept Failing.

[Q] After flashing back stock ROM, the phone keeps blinking on the boot screen (HELP)

I am in desperate need of help you guys! I screwed up so hard that I don't even know where to begin...
THE SITUATION:
-Right now when I go to turn on my phone, it will only stay on the current SAMSUNG GALAXY S I9000 screen (the very first screen when booting your phone) and it keeps flashing in and out.
Before trying to use Odin to put back the original Kernal on my phone, it was just stuck as the SAMSUNG GALAXY S I9000 screen, still wouldn't start. <I followed this website step by step>
http://www.samsunggalaxysforum.com/...-to-a-stock-rom-after-installing-darky's-rom/
BEFORE ALL OF THIS EVER HAPPENED:
I finally rooted my phone and manage to download Clockworkmod recovery on my phone and then used it to flash Darky's 10.2 custom ROM. Everything turned out great except at the beginning of the boot, the screen turned all rainbow coloured, completely distorted, and it continued to do that. I then tried to go back to Recovery mode to do the Voodoo lagfix but I couldn't even get into the recovery mode anymore, it either wouldn't let me, or it did but the screen didn't go to it properly (more likely the first one). I read somewhere that if you reflash your phone again, it should make all the tweeks go away. So I tried that from the Darky's tools menu and ever since then, I've been stuck with the Boot Screen this whole time...
I already bricked my phone once, and that was before the Flashing Boot Screen.
I really need help you guys, I would at least like to have my phone back to the original basis, at least! Your help would be greatly appreciated!
THANK YOU
P.S. (i'm not that great at all this phone tweeking, but I've succeeded in doing it up until yesterday)

Weird colors on boot usually are a sign of an incorrect bootloader version. Since you seem to be familiar with darky stuff (ugh) you could try the darky resurrection edition; there should be easy to follow instructions on their site.

tamaleddon said:
Weird colors on boot usually are a sign of an incorrect bootloader version. Since you seem to be familiar with darky stuff (ugh) you could try the darky resurrection edition; there should be easy to follow instructions on their site.
Click to expand...
Click to collapse
I just flashed the RE version and it's making some progress. Definitely no weird colors.
PROBLEM:
-the boot screen is still flashing when trying to boot my phone, only this time it's with the "Darkcore & Darky's ROM" logo on it. The flashing is at a slower pace this time around.
ALSO:
I can get into the stock recovery screen, I hope this can somehow help
what should I doo!!?!

Ok see your here too and more q's for you based on what I see here:
1) What did you start with as a rom before 10.2 (stock GB, Froyo rom or ???)
2) The RE version - was that GB or Froyo?
I am thinking as the other poster alluded to is that maybe you went from a Froyo rom to 10.2 without getting the GB bootloader from a stock rom (odin with bootloader update checked) and now you are still working with the wrong bootloader?
If that sounds like what happened try flashing the RE edition for Froyo (9.3 I think) if you haven't already.
G

gfacer said:
Ok see your here too and more q's for you based on what I see here:
1) What did you start with as a rom before 10.2 (stock GB, Froyo rom or ???)
2) The RE version - was that GB or Froyo?
I am thinking as the other poster alluded to is that maybe you went from a Froyo rom to 10.2 without getting the GB bootloader from a stock rom (odin with bootloader update checked) and now you are still working with the wrong bootloader?
If that sounds like what happened try flashing the RE edition for Froyo (9.3 I think) if you haven't already.
G
Click to expand...
Click to collapse
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?

As far as i read on the Darky Site you have to activate Lagfix to install 10.2
Do you?
In other case.
Install Resurrection 9.2 FW:
(sorry. new member no links outside allowed: Go darky forum, stable roms, darky resurrection 9.2)
If that works your bootloader if for Froyo and afterwards you can go on to flash Darkys 10.2 like written in the Darky Forum.
But i would suggest to stay on Darky´s 9.5 with 2.2.1
It is the stable version with no bugs at all. This gingerbread sucks a lot with Akku Drain, Light sensor and other thing. Also no call records.
I will stay on 9.5 so far. Best solution at the moment...
The thing with installing 10.2 you installed without installing 2.3.3 rom before could be, that is maybe possible to install Darkys 10.2 Theme on a 2.2.1?
But no guarantee...

roma17 said:
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?
Click to expand...
Click to collapse
The colour distortion problem is 100% caused by incorrect bootloaders. Download jvq from samfirmware (or another 3 file gingerbread of you have one already), use the Odin version contained in the download, tick repartition and update bootloader then flash.
Download cf root for jvq and flash that as PDA without repartition. After the phone boots downlaod darkyrom from the market and from it flash darky 10.2.
Personally the kernal that comes with darkys takes too long to load the phone so I use galaxian instead. Phone flies and it's the first custom jvq rom I've used which doesn't reboot itself.
Sent from my GT-I9000 using XDA Premium App

sxi200 said:
The colour distortion problem is 100% caused by incorrect bootloaders. Download jvq from samfirmware (or another 3 file gingerbread of you have one already), use the Odin version contained in the download, tick repartition and update bootloader then flash.
Download cf root for jvq and flash that as PDA without repartition. After the phone boots downlaod darkyrom from the market and from it flash darky 10.2.
Personally the kernal that comes with darkys takes too long to load the phone so I use galaxian instead. Phone flies and it's the first custom jvq rom I've used which doesn't reboot itself.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Thanks for your response! Greatly appreciated. But at the time, I'm just looking to get my phone to work. It still doesn't work, it's still only stuck flashing the bootscreen, nothing else.
From my other post:
Okay, basically at this point, I just want my phone to work I've tried what you said. I remember that before rooting my phone initially I was running Froyo 2.2.1. So I found the ROM for that ( http://www.samfirmware.com/WEBPROTECT-i9000.htm ) Just like you said. I downloaded from the *Provider Samsung Galaxy S i9000 heading and picked the I9000BOJS5 ## from February 2011 because I think somewhere around there I updated my phone to Froyo. Flashed it, did everything, still no luck.
I've had a recent hunch though. When the bootscreen boots up, it keeps saying i9000 only, when before it used to say i9000M at least for a little bit (yes my phone is i9000m). Is there a stock froyo rom that's specifically designed to go with the i9000m model? Or are they just all the same?
Never give up
-Thank you so much

Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App

Could be that you have a lagfix enabled and the stock ROM can't read the EXT4 file system. If so, try flashing another custom ROM via Odin (e.g. GingerReal), disable the lagfix to go back to RFS, then from there you can go back to the stock ROM.

gfacer said:
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Well CM7 forum is down but here is the most of the link, you can google this and look at the cached pages. cyanogenmod topic/15707-how-to-restore-to-stock-on-your-gt-i9000m/
You should be able to click to the multi upload link too.
Now - you are aware of course that our i9000m models can suck and die fairly readily, especially when flashing certain roms. Has yours even been returned yet? Mine has and they replaced the motherboard. You may actually have a warrenty job and in any regard they won't likely fight too hard (just flash it to one of the jl2 or kc1 rom first).
If you want to find out for sure. look for the i9000m threads where they install eclair and use the external sd to boot and then look at the memory (internal then shows as external I think - its in the thread). Basically if it shows 0 available you're hooped.

gfacer said:
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
I'm downloading the ROM from this link, could you verify it?
http://forum.xda-developers.com/showthread.php?t=883568

It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App

gfacer said:
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
there is a I9000UGJL2_homebinary_add_param.tar
and a SS_DL.dll
so All i would have to do is just put that .tar file in PDA field and get a regular .pit file and check off the re-partitions

gfacer said:
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Okay, I have great news!!!!!!!!
I flashed that previous stock froyo ROM and finally can use my phone once more!!!
THANK YOU VERY MUCH!! Special thanks goes to gfacer! I could never have done it without you!
needless to say, I still require a custom ROM such as Darky's 10.2 RE on this phone of mine.
As a final request, would you be so kind to list all the things necessary for me to do in order to get all the way to darky's 10.2 with the lagfix and all?
Or if not, at least a thread or website that says exactly how to do it on my phone (i9000m) ?
Thanks ever so much!!!

Great!
My advice would be to pretend it never happened, but read all the instructions for the rom you are interested in and start from scratch.
Generally I would go custom froyo kernel from odin which will root you and give cwm generally, update bootloader to gb via a stock rom or ezbase, then flash 10.2 via cwm.
Darky has excellent guides also look at ezbase thread.
Sent from my GT-I9000M using XDA Premium App

roma17 said:
Okay, I have great news!!!!!!!!
I flashed that previous stock froyo ROM and finally can use my phone once more!!!
THANK YOU VERY MUCH!! Special thanks goes to gfacer! I could never have done it without you!
needless to say, I still require a custom ROM such as Darky's 10.2 RE on this phone of mine.
As a final request, would you be so kind to list all the things necessary for me to do in order to get all the way to darky's 10.2 with the lagfix and all?
Or if not, at least a thread or website that says exactly how to do it on my phone (i9000m) ?
Thanks ever so much!!!
Click to expand...
Click to collapse
To load Darky 10.2 successfully on your phone, you have to flash JVP or JVQ bootloader over your phone. The best solution is flash Stock Rom with bootloader over your phone. Then, flash Darky rom over your phone.