Database Users

I may have killed my Vibrant (i kno...wrong sec but my thread is in the rom bible)

i need help...my vibrant is sitting at a blk screen after odining the stock jfd.tar . i had had voodoo lagfix and a market lagfix on there earlier and i dnt think i took it off correctly bcuz i was late to class but shouldnt odin take care of thatif i selected repartition and the stock jfd.tar file?...could it be that its still setup as EXT4 and not rfs like it should be when its stock? now i JUST noticed that it will only boot completely if i load a custom rom despite using odin to revert to stock. what happens is that it boots to the tmobile pink square but no sound, when the galaxy S screen comes on, then the tmo sound comes on (late), then the screen goes blk w/ the touch buttons lit. in order for it to boot i have to flash the root update in clockwork, reboot, then flash a ROM, reboot....have i done somethin wrong? why wont it boot when i odin it?

you need to disable the voodoo fix before you do anything, because its like you said, it still assumes its ext4. In odin its trying to flash its looking for rfs partition. If its too late to disable voodoo, you may want to try flashing one of the 2.2 ROMs through Odin, those seem to fix all bricks (non JTAG bricks that is), and brings phones back to life. If you use a 2.2 i recommend Eugenes very first one where you don't have to mess with kernels and such

boimarc89 said:
i need help...my vibrant is sitting at a blk screen after odining the stock jfd.tar . i had had voodoo lagfix and a market lagfix on there earlier and i dnt think i took it off correctly bcuz i was late to class but shouldnt odin take care of thatif i selected repartition and the stock jfd.tar file?...could it be that its still setup as EXT4 and not rfs like it should be when its stock? now i JUST noticed that it will only boot completely if i load a custom rom despite using odin to revert to stock. what happens is that it boots to the tmobile pink square but no sound, when the galaxy S screen comes on, then the tmo sound comes on (late), then the screen goes blk w/ the touch buttons lit. in order for it to boot i have to flash the root update in clockwork, reboot, then flash a ROM, reboot....have i done somethin wrong? why wont it boot when i odin it?
Click to expand...
Click to collapse
I had the same issues. Here's what I understand. Voodoo changes the filesystem to ext4, as you know. But RFS can't read that. For some reason, the kernel doesn't flash properly because it still sees the ext4 partition.
So here's what I did to fix. Pain in the arse, but it works.
In ODIN, Flash Eugene's Froyo that does not brick ROM in the bible
When that is complete the recovery will come up and there will be some errors. That's ok. We don't want this one.
THEN flash RFS (you should already have it) from the bible.
SHOULD be good to go. Like I said, it's dumb that you have to go through that, but it is what it is. I did it 4 times in 5 hours using trial and error. I know this method works.
Good luck!

in adb, i ran "adb shell", "mount" and i checked the "/dev/block/" and it said "/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vflat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0". so i think its rfs..i think lol is there a command in adb that can disable the lagfix?

is the RFS file ur talkin about, "s1_odin_20100512.pit" ?? or is it somethin else?

I agree, flash to froyo that does not brick, then flash back to the original firmware, not leaked updates. I have had great luck with checking repartition when flashing froyo, keep it checked when flashing back to stock. Then uncheck it and flash the stock rom a second time.
Sent from my SGH-T959 using XDA App

boimarc89 said:
in adb, i ran "adb shell", "mount" and i checked the "/dev/block/" and it said "/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vflat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0". so i think its rfs..i think lol is there a command in adb that can disable the lagfix?
Click to expand...
Click to collapse
No, the problem is probably mmcblk0p4 a.k.a /data being and ext4 filesystem, but if you flashed the stock kernel the phone won't be able to mount /data since it won't understand the ext4 filesystem... and THAT's the problem.
boimarc89 said:
is the RFS file ur talkin about, "s1_odin_20100512.pit" ?? or is it somethin else?
Click to expand...
Click to collapse
Is that sarcasm? I hope it is

boimarc89 said:
is the RFS file ur talkin about, "s1_odin_20100512.pit" ?? or is it somethin else?
Click to expand...
Click to collapse
that pit file just tells Odin how to setup the partition tables... its the actual .tar file that contains the .rfs install files... if you can get into Clockwork and install a custom ROM, then you can disable the voodoo lag fix, and reflash the stock kernel so you can go back to stock
or
like everyone else has mentioned go to froyo, then go to stock

If you can get into clockwork, just flash the flashable zip version of the froyo Rom. Accidentally forgot to disable voodoo when I flashed it earlier. What do ya know, the ROM booted all the way up. That will work without odin. Given that it wasn't a fluke and u have access to clockwork still. If not odin is your only option. Point blank.

http://dl.dropbox.com/u/9742964/Vibrant_Frankin_Twiz_Update3.zip
thats eugene373's Frankin-Twiz3 custom ROM preloaded with JACs Voodoo kernel, just flash through Clockwork and it'll install the voodoo fix again so you can disable it
If it doesn't help you, it may help others in a similar situation.

i got it now..im running the ji2 firmware trying to get to build.prop so i can fix the missing market apps..idk how to get to it...can i extract it by adb?

boimarc89 said:
i got it now..im running the ji2 firmware trying to get to build.prop so i can fix the missing market apps..idk how to get to it...can i extract it by adb?
Click to expand...
Click to collapse
Use a root explorer app and edit it directly from your phone.

boimarc89 said:
i need help...my vibrant is sitting at a blk screen after odining the stock jfd.tar . i had had voodoo lagfix and a market lagfix on there earlier and i dnt think i took it off correctly bcuz i was late to class but shouldnt odin take care of thatif i selected repartition and the stock jfd.tar file?...could it be that its still setup as EXT4 and not rfs like it should be when its stock? now i JUST noticed that it will only boot completely if i load a custom rom despite using odin to revert to stock. what happens is that it boots to the tmobile pink square but no sound, when the galaxy S screen comes on, then the tmo sound comes on (late), then the screen goes blk w/ the touch buttons lit. in order for it to boot i have to flash the root update in clockwork, reboot, then flash a ROM, reboot....have i done somethin wrong? why wont it boot when i odin it?
Click to expand...
Click to collapse
I'm probably asking for it, but ...
How is this thread "in the rom bible"? You messed up in some manner, didn't quite understand exactly what you were doing, you don't fully understand what a fstab is or how partitions really matter, sure, I understand that. But why does this warrant a thread: yeah, that's a bit beyond me ...
After reading several other threads promoting self-policing, why oughtn't it be sought here.?! If the only reason that this thread is offered a place in dev is because there is a mention of ext4, then we are all in trouble.
I've been flamed and chastised before for my views, but if no one polices, then who will? Is your question really geared toward the development of something Android related? Then perhaps you have a valid thread. But if it's not genuinely development related, why are you posting here?!

disable-lagfix in an update.zip
This article has a link to install the disable-lagfix with an update.zip file. If you have access to recovery I suggest you use that.
http://androidspin.com/2010/09/23/overclock-add-some-voodoo-to-your-samsung-vibrant/

[Q] Did i brick my phone?

Ok i was running Froyo Macnut R5 by eugene373 and i decided to go back to fusion so i odin back to stock with justanothercrowd pack. everything seemed to go fine but after the boot image and everything i just get a black screen. with the bottom buttons glowing.
What can i do? any suggestions?
Thanks.

Before someone replies with, "search the forums," I'll try to be somewhat constructive:
I had the same problem. You might have to flash Eugene's "Froyo that doesn't brick" with Odin, then immediately after, flash the stock Vibrant ROM with odin while reformatting your internal storage (only reformat when you flash the stock ROM). It probably wouldn't hurt to wipe cache and data with stock recovery between flashing either.
This means you'll lose SIMS 3 during the reformatting if you haven't already, so try to back it up some how if you can, or search the forums (I responded to one) for how to get it back.
Don't forget to remove your SIM card and external SD card before flashing with Odin.
There's a thread somewhere with detailed instructions on the whole froyo downgrade method. I didn't bookmark it when I followed the instructions, and I would have to reboot my computer into my Windows partition (I'm on Ubuntu) and search through my browser's history. In that time, you might be able to find it yourself.

thank you for your help, ive gotten it recovered now.

Just a quick note, you will always get Sims 3 back when you ODIN to JFD. It is a part of Stock Rom.

kangxi said:
Just a quick note, you will always get Sims 3 back when you ODIN to JFD. It is a part of Stock Rom.
Click to expand...
Click to collapse
You get the Sims launcher back, but if you repartition because you flashed a Voodoo kernel and forgot to remove it first, you lose the Sims data. In that situation, if someone tries to launch it, they'll get an "unable to parse package" error.
Edit: this is the fix I was talking about in my first response. That's when you repartition and lose the Sims 3 data.

I'm sorry, but I have ODIN'd back to JFD many many many (did I mention many?) times and I've always gotten Sim 3 back while re-partioning. I'm not sure what you are flashing but maybe you need to grab another file. And no, I'm not just talking about the icon. Press the icon, it installs and it plays.
I just did a full flash to stock JFD and JI6 today from Bionix Fusion 1.1 using re-partition because I was having many issues. If my phone wasn't charging with the power off (reconditioning) I would show you.
Edit: I think that is the ODIN file I have been using that you linked to. I don't know. I just have JFD and JI6 saved on my computer for my frequent uses.

kangxi said:
I'm sorry, but I have ODIN'd back to JFD many many many (did I mention many?) times and I've always gotten Sim 3 back while re-partioning. I'm not sure what you are flashing but maybe you need to grab another file. And no, I'm not just talking about the icon. Press the icon, it installs and it plays.
I just did a full flash to stock JFD and JI6 today from Bionix Fusion 1.1 using re-partition because I was having many issues. If my phone wasn't charging with the power off (reconditioning) I would show you.
Edit: I think that is the ODIN file I have been using that you linked to. I don't know. I just have JFD and JI6 saved on my computer for my frequent uses.
Click to expand...
Click to collapse
That's interesting then. All I know is that I repartitioned and flashed back to stock with ODIN and then I couldn't open the Sims anymore. I read on some other forums that repartitioning with ODIN erases a partition where the Sims installation files are stored. Obviously, simply flashing with ODIN won't erase it, but repartitioning the internal storage does exactly that... so I assumed that's why it wouldn't launch.

Eugene's froyo unbricked me! Issues still!

ok so i got some help from you guys on fixing my phone after the VooDoo crash. i flashed Eugene's froyo 2.2 and the phone is ALIVE!! one major problem i am seeing is i have no application storage now! i cannot download any apps, when i go to manage apps i have a ton of weird apps installed and i can't uninstall anything. how can i fix this??

Root explorer
V5 custom vibrant

root explorer? whats this?

An app from the market which gives you access to all the files on the phone and the abort ability top delete them
V5 custom vibrant

hmm, but i have zero storage, i cannot download any apps. i get a message saying i have no storage left

Go to the market and push downloads then delete some of the apps you have already maybe that will give you enough room
V5 custom vibrant

i just fixed the phone and got it running, i have not downloaded any apps.

Did you repartition when you odined also the apps usually go off of your google account sign in to the market and your apps should come up from before what ever you had paid for should be available
V5 custom vibrant

Anyway to post any pix of these strange apps your talking about?
V5 custom vibrant

did not repartition, should i?

oh and no i don't know how to send a screen shot of the applications. but they are only in the manage apps section, i can't see the apps on the phone but they are there in the manage section

Dude have odined back to stock yet are you still on eugenes froyo ?you have go back to 2.1 its a pit file and jfd file you can find then on this site
V5 custom vibrant

yeah i have tried to go back to stock after the froyo flash but i end up with the blank screen after the galaxy S logo. the phone only works with the froyo flash installed.

Did you extract the pit file?
V5 custom vibrant

yeah both the 512 pit and jfd rar files are extracted, should i start over and reflash eugene's froyo? then flash the stock jfd file? if so when should i be repartitioning?

you dont extract the jfd file you were supposed to leave that how it was

ok my bad, the jfd file won't extract. i just realized this.

is it possible that the drivers are bad have you tried flashing another 2.2 rom then flashing back to stock?the only thing i can think of is try odin again click re partition and try to go to stock or try to flash another 2.2 rom then go back to stock if odin is set up correctly im not sure why its not working

another 2.2 rom? i had only heard about the eugene's fix for the voodoo brick that im experiencing. whatever i do i always get a blank screen after flashing unless i flass the froyo (rom?).

i'm going to try flashing eugene's froyo back in it without repartitioning then start odin back up and flash the old vj12 with partition selected and see what that does. i had a file called original from my last brick fix but am not sure what that was.

New to epic =)

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

Welcome! I also use Frankenstein ROM.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q]Having issues getting back to stock rom from CM7.

Does anyone have a stock based flashable rom so that I can get back to touchwiz?
All the ones I've tried dont have the right update scripts and I'm not that good with those yet.

Unfortunately you will have to ODIN back to stock JFD. You will need to select repartition in odin also.

Odin is your friend. I've done it half a dozen times now. it's the way to go

And of course you'll have to use Eugene's Froyo That doesn't brick odin first then odin JFD then you'll be good to go. Something with the file system in CM makes it so you have to do all these steps to get back to stock and to be able to use Voodoo again well I had to do it...

just odin back to stock but im not sure if u check off re-partition?? when going back to stock from cm7?

AustinKnight45 said:
And of course you'll have to use Eugene's Froyo That doesn't brick odin first then odin JFD then you'll be good to go. Something with the file system in CM makes it so you have to do all these steps to get back to stock and to be able to use Voodoo again well I had to do it...
Click to expand...
Click to collapse
I really don't think that you need to do this. All I did was odin the jfd with repartitions checked plus the pit file.
Sent from my SGH-T959 using XDA App

Anyone that reads this thread in the future, just check the going back to stock link in my signature.
The reference to Eugene's ftdb is only needed in special circumstances.

You should be fine just using ODIN to go back to JFD. You will want to select repartition as well when coming from CM7. You wouldnt need to use the Froyo that does not brick in this circumstance. That would be used say for example if you forgot to disable Voodoo and flashed a non Voodoo ROM over it.