yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] anomalous3:
no more than 2GB for ext2. DO NOT USE the ROM manager to partition the SD card; it partitions the internal SD card which breaks things, and this looks for a partition on an external SD card anyways.
[Vibrant Android Development] ttabbal:
Pull the usb cable and try again. No idea why, but it works.

There's also download mode and odin.
[Vibrant Android Development] anomalous3:
Also if that doesn't work do

adb kill-server

and then try again
[Vibrant Android Development] theMAGNUM:
I tried the adb kill-server and that didn't work. I also tried unplugging usb and plugging back in, still nothing.

EDIT: after adb kill-server and then adb shell it says system/bin/sh failed no such directory

I'm new to download mode and odin. Care to share how I would utlize these to help throw the update.zip onto the internal memory?
[Vibrant Android Development] ttabbal:
They don't, not directly anyway. It flashes the phone back to the stock rom so you can boot normally and use usb storage to put the file in the right place.
[Vibrant Android Development] anomalous3:
this will actually only work from recovery, clockwork or stock. If you have trouble, just mount your sdcard onto your computer and drag and drop it on there.

On another note, is anyone interested in seeing some utilities kanged from CM/amon-ra recovery onto this? (such as ext tools, zipalign, etc.)
[Vibrant Android Development] theMAGNUM:
Ok, that makes sense. If I can just get the phone to load up then I can throw the update.zip on there.

Coming from G1 I never utilized odin or download mode. Is there anyone willing to give me step-by-step directions on how to work this? I would greatly, greatly appreciate it.
[Vibrant Android Development] theMAGNUM:
I might be missing something obvious here, but the only sd card I can see from the back is the 2g one with Avatar on it. Not the 16g one that I believe you need to put the update.zip on its root. Is there a way I can get at the 16g one? If so, I can just load it on there through my computer and then put it back in the vibrant
[Vibrant Android Development] ttabbal:
I came from a G1 as well. Download mode is kind of like fastboot. Look at the stock rom thread. I'm on my phone or I'd give you more info, but they cover the steps pretty good over there and have links to the files you need.
[Vibrant Android Development] ttabbal:
I don't think the 16g flash is an actual card, they just mount it there as that's what android expects.
[Vibrant Android Development] player4lifeov:
You place the update file on the root of the internal memory. That way, when you do clockwork recovery you can install it. Someone correct me if im wrong.

Note: do not partition or reformat your internal memory!
[Vibrant Android Development] player4lifeov:
I'm in the process of trying this out! We'll see how this goes! Kind of nervous!
[Vibrant Android Development] anomalous3:
you would need to partition an

external

SD card (preferably a class 6 card) in order to use the data2sd. The one that Avatar came on will work in a pinch though. It won't break your phone if you don't have one, but it will speed it up if you do.
[Vibrant Android Development] theMAGNUM:
Oh gosh I'm feeling overwhelmed here. I was trying to partition my sd card through clockworks recovery. When I finished I realized I did not have the update.zip on the root sd card. Now my system will not load up. I can load whatever I want onto my 2g sd card, the one with Avatar. However, I tried loading the update.zip onto that and then in the original recovery (it resorted back to that) it did not notice it.

I am trying the odin way of doing things but this is over my head right now, considering I can't even get adb to recognize my device. Is there any way one of you can go on gchat and help me out?
[Vibrant Android Development] JLundberg:
Is there any way to partition without using the pc...parted is not there
[Vibrant Android Development] player4lifeov:
So i got the thing to work and I noticed that there were some forceclose issues at first but after a fixpermissions from rom manager and reboot everything seems to be working very smooth and very snappy. I'll try to get a quadrant score ASAP for you guys!
[Vibrant Android Development] player4lifeov:
I attached the pictures to the thread hopefully you guys can see them!

I was able to hit 1505 at first before permissions fix. After I did permissions fix and rebooted it brought in down to 1383 or whatever. Nonetheless there it is, we have surpassed the Nexus One and Droid X
[Vibrant Android Development] Kid Poker:
If I don't like this or anything happens, can I use nandroid to restore how I had the phone when I backed it up?
[Vibrant Android Development] junkdruggler:
Yup... Its the same thing tho... Same rom just deodexed...
[Vibrant Android Development] MTC44:
Just flashed this ROM thru clockwork with the stock kernel. Hangs on the S in bootup and then shuts down. What do I need to do?

EDIT: Nevermind. Wiped thru recovery and it booted up. Thanks.
[Vibrant Android Development] YepMan68:
Anyone having clock problems...

so I've happily applied this ROM and the the JAC kernel and I'm finding that my clock "takes off" on me. After booting up and staying on for about an hour, I'm a minute or so faster than my computer or phone time at work. By lunch time I'm about 5-10 mins. faster and by late afternoon, I'm a good 20-30 mins. ahead. I reboot and it fixes the time, but is the overclocking or something else just making everything race???

Any thoughts welcomed and if there is a fix (or another thread on this), please point me in that direction. Thanks
[Vibrant Android Development] anomalous3:
This is a known issue with JAC's Overclock v3 kernel, honestly I find that the standard clocked v9 seems to be faster than stock and doesn't have this problem.
[Vibrant Android Development] robavila721:
Are you running any lag fix along with the new kernel?
[Vibrant Android Development] anomalous3:
Eh, I was running apps2sd for a bit but I decided against it since I had market troubles. Still no complaints though, even without a lagfix.
[Vibrant Android Development] YepMan68:
Thanks for that advice. I'll give that v.9 a try and report back. Also thanks for that great work on this ROM.
[Vibrant Android Development] YepMan68:
Thanks for the advice. I'll give it a try and report back. Thanks also for the great job with this ROM. You're work is awesome.
[Vibrant Android Development] YepMan68:
Thanks. I'll give it a try. Thanks ask also for the great work on this ROM.

--Sorry about the multiple posts. My app kept FCing and I didn't realize it was posting them until I logged on with a computer. -thanks all.
[Vibrant Android Development] The_Chrome_Coyote:
Getting the following error, same as when I try to install Eugene's Vibrant7 ROM. I dont have the issue with Vibrant9 though.

Any idea whats causing it? SU does exist in the xbin folder. Id like to get this working again bc its my preferred "stock" flashable ROM.

E:Cant chown/mod /system/xbin/su

(so such file or directory)

E:Failure at line 65:

get_perm 0 0 04755 SYSTEM:xbin/su

Installation Aborted
[Vibrant Android Development] YepMan68:
-So JAC's kernel is updated and the new OCv4 is running very smooth and the time drift has been corrected - if anyone was on the fence about updating. That plus this ROM has been awesome. -great job.
[Vibrant Android Development] Arcadia310:
Can someone explain to be what a deodexed ROM is and how it's better than let's say, eugene's ROMS?
[Vibrant Android Development] junkdruggler:
This is just the stock rom... it has been optimized fir theming... Eugene's rom's are also deodexed but he has added and taken away what he likes...
[Vibrant Android Development] shawn1979:
y no screen shots 4 this rom
[Vibrant Android Development] anomalous3:
Because it looks exactly the same as stock. At some point in the near future I might come out with a deodexed version of the new release, but I haven't had much time to mess with stuff lately.
[Vibrant Android Development] tweezit:
Looking forward to that release as I like the deodexed version as easy to customize that way I don't have to install 50+ apps after using oden :D
[Vibrant Android Development] Ojuani:
I tried to install VibrantDeodexed1_2.zip from Android system recovery <2e>, but when I select the option "reinstall packages", shows me

-- Install from sdcard...

Finding update package...

Opening update package...

Installing update...

Installation aborted.

Please Thanks in advance for any help
[Vibrant Android Development] YepMan68:
did you remember to rename to update.zip

--Did you rename it as the OP stated on the first page to update.zip? If you are flashing through the Samsung recovery you have to rename. If you are flashing via Clockwork, you don't.
[Vibrant Android Development] anomalous3:
If you have already partitioned your internal SD card, don't even worry about ADB at the moment. Follow the instructions in this thread with one important exception: In step 5, also check the "repartition" even though the instructions tell you not to check anything else:

http://xdaforums.com/showthread.php?t=734475

to get back to stock. Then worry about updates/upgrades.
[Vibrant Android Development] theMAGNUM:
Ok I'm trying this right now, waiting for the PDA file to finish downloading. All I need to do is have the rom load then I should be good to go. Hopefully this is a step in the right direction. I'll check back in in about 5-10 min

EDIT: Ok so I hit the start button with everything loaded and it says "<OSM> All threads completed. (succeed 0 / failed 0)" What am I doing wrong here?
[Vibrant Android Development] anomalous3:
If it's the first time you have your phone in download mode, your computer needs to install the drivers for it when it's first plugged in (it should do so automatically if you've installed the samsung drivers from This thread:

http://xdaforums.com/showthread.php?t=728929

. Once you've done that, close down odin, unplug the phone, shut down the phone, boot back up into download mode, turn on odin, and THEN plug the phone back in. One of the COM ports should light up yellow in odin, then you know you're good to go. And don't forget to use the .pit file.
[Vibrant Android Development] ceroglu:
I want to try this, I have rooted my phone and also I have installed the Clockwork Recovery. But I am not sure on how to repartion the SD card, Is there a wiki or tutorial on this?
[Vibrant Android Development] theMAGNUM:
This worked! Thank you very much. Odin is in the file DO NOT TURN OFF TARGET mode right now. Any idea's of how long this will take? So this basically loads the stock vibrant firmware?
[Vibrant Android Development] anomalous3:
the problem is that clockwork can't partition the external sd card. If you have an old G1/Mytouch lying around you can use Amon Ra or clockwork recovery to partition your sdcard (that's what I did). Or if you're running a linux distro you can put your sdcard in a card reader and partition it using one of the many fine partitioning utilities included with various linuxi.
[Vibrant Android Development] player4lifeov:
I used my old G1 to partition the

external

sd card. Other then that i have no idea...
[Vibrant Android Development] anomalous3:
This basically loads the stock firmware. As long as you have the force reboot checked off it should reboot when it's done. If it doesn't show a loading bar though, pull the battery and try again.
[Vibrant Android Development] theMAGNUM:
Ok on my third pull. I've waited about 3 minutes each time (according to some other threads that's ample time).

EDIT: Third pull and still no status bar. When I unplug and try to go back into download mode there is a computer and a phone in the middle of my screen. Is that normal? Is there anything else I could be doing wrong? I'm still getting the yellow com and clicking repartition
[Vibrant Android Development] ceroglu:
Unfortunately I don't have neither of those two. Do I have to partition the SD card for this ROM?
[Vibrant Android Development] anomalous3:
to get out of the computer and phone you have to unplug the phone, take the battery out again, then hold volume down while powering up. Make sure you set the .PIT file as well as the PDA file. Also, close odin after every failed attempt.

I've managed to bring it back from the computer/phone screen many times, but the secret is pulling the battery first.
[Vibrant Android Development] theMAGNUM:
That didn't work to get it out of computer and phone. I can still get into downloader mode though. I have been restarted odin after ever fail. Just to clarify PDA is a rar file, correct?
[Vibrant Android Development] anomalous3:
The PDA is a .TAR file, should be about 283MB

the .PIT file needs to be extracted from a rar file. It's pretty tiny.
[Vibrant Android Development] theMAGNUM:
Ok yea, that's what I'm doing...still nothing...on my 6th try. I have to be doing something wrong here.

EDIT: I'm at com6 if that's any help (previously at com5)
[Vibrant Android Development] player4lifeov:
To enjoy the benefit of it, I would say yes. Sadly I don't know any other way to do it.
[Vibrant Android Development] anomalous3:
If you're not having any luck with the 512 pit file, try the 513 pit file that came with the odin download in the link I posted earlier.
[Vibrant Android Development] theMAGNUM:
Ok sorry I did a quick search and can't find 513. Sorry I'm at my breaking point here this is so frustrating!!!
[Vibrant Android Development] anomalous3:
It's one of the files in this .rar:

http://www.justanotherdev.slackdev.com/Odin3.rar
[Vibrant Android Development] ceroglu:
I am not sure If I can be helpful on this, but other day when I re-flashed stock firmware, I had to learn how to use Odin and it was a little tricky.

First while in DL mode you need to make sure that the device is synced to your computer. Did you install the drivers on your computer? if yes, then when you open Odin on your windows, it should say that you are connected to your vibrant with Com# usually 3 or 7. Then make sure three check boxes are filled under option. Click on PIT and select the PIT file and then click on PDA(make sure the check box is selected) and select the .tar file. Then you hit the start on Odin and wait untill it flashes and your device boots up.
[Vibrant Android Development] theMAGNUM:
What is frustrating is I have done that 6 times now, exactly how you said. It doesn't do anything besides say DO NOT DISCONNECT or something. I'm looking for pit 513 hopefully that is the answer to my problems because I'm currently using 512...

EDIT: Does sim card need to be in?
[Vibrant Android Development] farrisizdaman:
I'm in the same boat as Magnum. Please keep giving the advice. On my 4th pull
[Vibrant Android Development] theMAGNUM:
This is now my 3rd time pulling on 513...I just don't get it. Hopefully T-Mobile will refund my vibrant cause at this point, I don't know what else I'm doing wrong.

Thanks for all the help sorry its in vain :mad::confused::(
[Vibrant Android Development] farrisizdaman:
Can we just use the nandroids at the bottom of the topic you linked to? Will those work?
[Vibrant Android Development] farrisizdaman:
Where is this pit 513 i still can't find it
[Vibrant Android Development] anomalous3:
also, make sure adb is not enabled while you are using odin; do adb kill-server in command line, maybe try a different usb port.
[Vibrant Android Development] robavila721:
flashed perfectly following eugenes steps from the other vibrant.zip

excellent job sir hopefully we can get JIT working.

1. go into recovery (clockwork)

2. go into partitions menu and do a /system wipe

3. from the main menu do a factory wipe

4. flash .zip from sd

5. reboot

first boot takes a while at the "S" screen, but then this thing flies, no lag 1450 on quadrant (class 2 sd (2gb ext2))
[Vibrant Android Development] farrisizdaman:
Switched usb ports already. How long do you wait because odin only says DO NOT TURN OFF TARGET
[Vibrant Android Development] theMAGNUM:
Well I had everything packed up and about to go to bed saw this last post and pulled it out of its box. Now it is just stuck at file analysis...doesn't get to DO NOT DISCONNECT.

EDIT: On 2nd pull it got to DO NOT TURN OFF TARGET...and then nothing.
[Vibrant Android Development] theMAGNUM:
SOOO jealous...and frustrated
[Vibrant Android Development] farrisizdaman:
MIne is still stuck on DO NOT DISCONNECT. What do I do. Odin never works.
[Vibrant Android Development] anomalous3:
try with both 512 and 513 after adb is killed. if still no luck, the .tar file may have been corrupted. possibly try the one from eugenes post. also reinstall samsung drivers.
[Vibrant Android Development] farrisizdaman:
Ok I'm not sleeping until its fixed. Please keep trying to help me.
[Vibrant Android Development] farrisizdaman:
OMGG IT WORKED I LOVE YOU.

This is how I did it.

Open odin.

then have phone plugged it and put into download mode. Odin should detect it then set files click start.
[Vibrant Android Development] farrisizdaman:
Short lived. It didnt work still same problem It flashed but to no avail.
[Vibrant Android Development] anomalous3:
did you check repartition?

If that doesn't work, next step is to try the old ms_guru files and then upgrade to this, it flashed 3 files, possible that one of them is necessary to repartition the sd card.
[Vibrant Android Development] farrisizdaman:
I flashed it a second time to be sure. I had repartition checked. In this thread

http://xdaforums.com/showthread.php?t=743875

He did that. Problem is I dont have adb set up on my computer.
[Vibrant Android Development] farrisizdaman:
IN the thread with the odin download. In the second post he posted links to nanddroids. Do you think I could flash that with odin. The nandroids extenstion is md5 i believe.
[Vibrant Android Development] The_Chrome_Coyote:
Paragon HD Manager 2010 can format and create linux partitions in the Windows environment.

FYI
[Vibrant Android Development] brandnewsimmy:
I was having serious trouble flashing with Odin and I ended up fixing by rebooting my computer, tapping F8, and selecting Disable Driver Signature Enforcement.

After about 3 hours of trying to flash, as soon as I did this Odin flashed my phone right away. Good luck.
[Vibrant Android Development] anomalous3:
The problem with the internal SD card is that it's, well, internal. No way to mount it to the computer without getting the phone booted up and working. I'm thinking the fix will have to be to get clockwork recovery working somehow and then pushing parted or partedsd to the phone via ADB, and then using that to repartition the SD card to a stock configuration.

You are almost certainly going to need to get ADB setup on your computer to fix this one. Plus it comes in handy with other stuff too. Sadly, I left my only micro USB cable at work so I won't be able to do much experimenting tonight, but I'll check through some stuff and see if I can find something useful.

That might come in very handy for those people who are having trouble. Definitely appreciated ;)
[Vibrant Android Development] The_Chrome_Coyote:
I was mostly referencing this for people who were asking how you can create an EXT3 partition without a G1/Mytouch laying around.

But having Parted on this phone would make things a WHOLE lot easier. Can you just push those files from the G1 ROM? Where would I put them?
[Vibrant Android Development] anomalous3:
/system/bin should do the trick. you will need to mount the /system/ partition from recovery before they'll work though. /sbin from recovery will work but it'll get erased when you reboot. Also I think you'd need to reboot your G1 into recovery and pull parted from /sbin because it's not a normal part of CM
[Vibrant Android Development] dboii54:
Just wanted to say THANK YOU!!! Didn't really think this phone lagged before, but now, it flies! I was a little worried putting a ROM on her for the first time, but just followed your steps, and it was all good. Heart started to speed up when it hung it the galaxy s screen, kinda like the first time I flashed JesusFreke on the G1, but everything is as it should be. Good Job!
[Vibrant Android Development] anomalous3:
Yup, first bootup takes longer because it has to dexopt stuff ;)
[Vibrant Android Development] ceroglu:
Ok, after the sd repartitionning with Ubuntu. I tried your ROM and my first quadrant score turned out to be 1923 and this is on 16gb class 2 card. I am very impressed with the speed so far. I havent tested and installed all my apps but so far everything works great. Thanks a lot for making this avaliable for us.
[Vibrant Android Development] The_Chrome_Coyote:
People who have bricked their devices by clearing /system with this ROM on the wrong SD Card,

Grab ODIN, 512 PIT and TAR from Stock Recovery Thread

Follow these instructions in the following order:

1. Install Drivers (if you have already, skip step 2)

2. Reboot Computer

3. Start Odin

4. Select PIT File, Select PDA file

5. With the Phone OFF, connect to USB, Boot into Download Mode (whichever way you can)

6. Make sure computer recognizes device, and Odin COM is yellow.

7. Start

it makes a huge difference that you do it in this order for some reason.
[Vibrant Android Development] brandnewsimmy:
I use Gparted and UNetBootin to create a liveUSB of Gparted. You could also make a live CD, but I don't have a disc drive. Anyway, Gparted works great to create an EXT3 partition.
[Vibrant Android Development] krichek:
Just had to say THANKS!! and thumbs up to the OP. This thing flies!! I'm not getting 1923 in quadrant but consistent 1450's with a very crappy sandisk 16GB class 2 card and everything seems smooooooooooth!!!

I used GParted as well, and since I didn't have a card reader handy I just tossed the card into an old Touch Pro I had lying around and mounted it via USB. Had no problems formatting it that way at all.

Stupid question time, Anyone thing I would see much of a difference if I went back and formatted as Ext2 instead of ext3?
[Vibrant Android Development] The_Chrome_Coyote:
Im getting a ton of FC errors, the biggest pain is android.phone which wont allow itself to be dismissed... ugh

back to ODIN for me
[Vibrant Android Development] ELFungi:
So, some of you are saying that the hung up at the first boot occurs at the "S" screen. Anybody else's hung at the Vibrant/Samsung screen? I've been waiting to see if it would boot since I wasn't sure how long the first bootup is suppose to take. Wanted to make sure to see if I messed up..again.
[Vibrant Android Development] krichek:
Not a single FC or hitch of any kind for me. Have you tried another reboot after the first?

Mine sat at the Vibrant/Samsung screen for a bit and then freaked me out because I heard the music about 30 seconds before the lame pink words fly across the screen. I was sure it was hosed lol, but it booted up eventually just fine.

I would say it took roughly 10-12 minutes total for it to boot completely.
[Vibrant Android Development] ELFungi:
Ok. I'm going to assume I messed up then because I heard the music too, but the pink words never came even after 10 minutes. Going to try again. :mad:

EDIT:

So I flashed back to the original firmware using ODIN and tried to update this through the stock recovery since Clockwork gave me the hang the last time. Renamed the file to update.zip and put it into the root directory of the internal sdcard, but when I try to "reinstall packages", it starts the installation, tries to opens and read the files, and then immediately "Installation aborted!" in red. Thoughts?
[Vibrant Android Development] Chalup:
Haha the same thing just happened to me. I make a point of turning my volume off before turning off my phone in order to avoid the ridiculously loud T-Mobile jingles. I guess it was turned up by default, and I almost went deaf as a result.

Anyways, just finished past the Galaxy S screen as I write. So far, so good...
[Vibrant Android Development] The_Chrome_Coyote:
Okay, now Im getting

E: Cant chown/mod /system/xbin/su

(no such file or directory)

Failure at line 64:

set_perm 0 0 04755 SYSTEM:xbin/su

Installation aborted

back to ODIN... jeez