yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Did you edit anything in sdparted?

command should be executed inside /sbin directory and it should be

sdparted -efs ext4

or

./sdparted -efs ext4

not /sdparted -efs ext4

let me know if you edited sdparted script or not.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
xdarooted

I am sure you do not have /data folder

do following

cd /

ls

if you see a data directory then "not found" is a different issue, otherwise I could edit sdparted script for you.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
adb push the attached sdparted.vibrant to /sbin directory then

adb shell

su - unknown

cd /sbin

mkdir sdparted

chmod 755 sdparted.vibrant

./sdparted.vibrant -efs ext4

Good luck, let me know.
[Vibrant Q&A, Help & Troubleshooting] :
no luck

I made sure that I didn't have the data folder and I tried your modified sdparted... no luck. I guess I could try the sdsplit ... was there any luck with the other dude ameedi600.

C:\adb\platform-tools>adb push e2fsck /sbin

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

2146 KB/s (428664 bytes in 0.195s)

C:\adb\platform-tools>adb push mke2fs /sbin

1070 KB/s (30680 bytes in 0.028s)

C:\adb\platform-tools>adb push parted /sbin

2584 KB/s (346680 bytes in 0.131s)

C:\adb\platform-tools>adb push resize2fs /sbin

1037 KB/s (22304 bytes in 0.021s)

C:\adb\platform-tools>adb push sdparted.vibrant /sbin

922 KB/s (16055 bytes in 0.017s)

C:\adb\platform-tools>adb push tune2fs /sbin

1039 KB/s (22364 bytes in 0.021s)

C:\adb\platform-tools>adb shell

# ls

ls

dbdata

data_tmo

config

cache

efs

sdcard

acct

mnt

d

etc

modules

data

sh

libz.so

init.rc

libcutils.so

libstdc++.so

libc.so

libcrypto.so

libm.so

default.prop

libutils.so

dev

fota.rc

liblog.so

sbin

sys

lpm.rc

init.smdkc110.rc

system

init.goldfish.rc

res

proc

recovery.rc

lib

init

linker

# cd /sbin

cd /sbin

# chmod 755 e2fsck

chmod 755 e2fsck

# chmod 755 mke2fs

chmod 755 mke2fs

# chmod 755 parted

chmod 755 parted

# chmod 755 resize2fs

chmod 755 resize2fs

# chmod 755 sdparted.vibrant

chmod 755 sdparted.vibrant

# chmod 755 tune2fs

chmod 755 tune2fs

# mkdir sdparted

mkdir sdparted

# chmod 755 sdparted

chmod 755 sdparted

# ls

ls

sdparted

tune2fs

sdparted.vibrant

resize2fs

parted

mke2fs

e2fsck

redbend_ua

adbd

dfta

# sdparted.vibrant -efs ext4

sdparted.vibrant -efs ext4

sdparted.vibrant: not found

# ./sdparted.vibrant -efs ext4

./sdparted.vibrant -efs ext4

./sdparted.vibrant: not found
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
we did not get to sdparted stage last night with ameedi600. We got phone booted and left it at that stage. We will work on it today in the evening.

Previously not found error was coming from /sbin/sh. sh is in /bin directory on Vibrant. The log file was set to /data directory which we do not have therefore I changed it to /sbin/sdparted/sdparted.log

You can check if you have sh in /bin directory. I will read the script again to see where else can be problem. The script was written for Nexus One there is need fixing for Vibrant.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
ummm there should be two sdparted, one directory and one script file. You have only one. Looks like mkdir was ignored and sdparted directory was not created.

do a ls -la

it should show if sdparted is a file or directory.

if sdparted directory inside is missing then it will return not found error. sdparted directory is needed to create a sdparted.log file. I can edit the script again and change the log file path if mkdir is not creating sdparted directory inside /sbin directory.
[Vibrant Q&A, Help & Troubleshooting] :
I thought you said the sdparted.vibrant was the sdparted, only modified.

could you send the new "sdparted" anyway, I'll try both methods again.
[Vibrant Q&A, Help & Troubleshooting] Henchman:
I have never seen an sdparted directory, and ive looked for it. Maybe we need to create it first before running the script.

I will try that tonight.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
yes; sdparted.vibrant is a modified sdparted, but it needs a directory sdparted inside /sbin to create a log file. Attached is another complete zip. You will need only sdparted.vibrant from it because you have already pushed the other files to /sbin. push the sdparted.vibrant from it to your /sbin directory then chmod 755 sdparted.vibrant, after that execute, from within /sbin directory by cd'ing to /sbin directory

./sdparted.vibrant -efs ext4

I have changed log file path to /sbin directory, instead of /sbin/sdparted/. If it works, good, in case it fails, it should create a log file sdparted.log inside /sbin directory, which maybe needed to figure out issues.

Good luck
[Vibrant Q&A, Help & Troubleshooting] Henchman:
Btw, is /sbin mounted in rw mide? Uf not, maybe we need to do that as well.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
yes, you are correct. following should do before running the script

mount -o rw,remount -t rfs /dev/block/stl9 /system

Thanks
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Thanks, this is very useful. If mmbclk0 is pointing to external sd card, then you are right sdparted will not touch internal card, it will partition the external sdcard. It is a good idea to pull external card and not insert it while trying to fix it.

Also, at least one thread I notice, which reports ODIN in some cases does not partition even re-partition checkedhttp://xdaforums.com/showthread.php?t=796458. Technically after reboot with Eugene's Froyo, and then odining pit512 with UVJFD with repartition checked it should revert to stock. Perhaps in this case ODIN is fooling and not repartitioning the internal sdcard. It may worth trying to repartition with Heimdall 1.1.1 http://www.glassechidna.com.au/products/heimdall/
[Vibrant Q&A, Help & Troubleshooting] :
I thinks this is my problem too... my external was referring mmcblk0... I'll try heimdall tonight
[Vibrant Q&A, Help & Troubleshooting] upbeat.addict:
fyi, heimdall requires a bootloader in order to re-partition, of which neither the JFD, nor "eugene's froyo no brick" rom actually contains. i'm grabbing the Eugene_2E_JK2_Froyo right now, since I know that it actually contains those files needed (boot.bin/sbl.bin i think), which has actually led me to believe that it's the reason why flashing actually that particular rom seems to temporarily remedy the situation.

im assuming that if this doesn't work, then the worst thing i've done is flash the same rom im currently running. i also wanna say, that avoid rebooting because it appears that every new boot results in a reset of user and app data, assumedly because of the missing sqllite mounts, can't say for certain tho.

im gonna bite the bullet and see what next level of android hell this leads to ;) good luck to the others.
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
I think you're ONTO something here. Once, flashed, Eugene JK2 actually does have a BL- which, like you said, might help explain that's the only one that actually boots up on our phones.

Please post up your results with Heimdall though. i'm very curious. I've never used Heimdall before, but I'd be willing to give it a shot later today as well.

Thanks for this info.

I worked with Ssiddiqi1 yesterday almost all day trying to figure this out too.

But, I pretty much got to where everyone else is at.

We were trying to get Root+ADB access, hoping and praying that SDPARTED would be the answer. But on second though, I honestly don't know, or think that SDPARTED, even if properly executed would clear the corruption.

The goal right now- beyond our immediate problem, is to find a way- a script that can be flashed to wipe the entire partition clean, then write in Primary and SEcondary Boot Loaders.

This way, it will work way better than any ODIN method on the clock right now. ODIN flashes or tries to flash a new ROM on the phone, and only incidentally repartitions if so desired.

We need something that will completely clear the clutter and cobwebs from the internal SD save for the bootloader.

I'd be willing to throw down good money for this. It will be a useful tool going forward. It seems DOW kernel is getting the shaft from lots of community members because of the data corruption in its latest 2 releases.

Just for the record though. Mor I fic - yes, I like him as MORIFIC, not Morfic- did spend one whole day bricking a fellow colleague's phone just to prove that there is a fix *(JE8). I appreciate his attention to this matter immensely, though accurately admit that it was the solution - to another problem. He hasn't solved our problem, YET. But the fact of the matter is that he did expend one day to try to resolve our issue. So I'm deeply grateful. I just don't know about flashing another DOW kernel is all.

*waiting to hear the good news !
[Vibrant Q&A, Help & Troubleshooting] Henchman:
Well, if this isnt solved by tomorrow, I'm getting the Vibrant 4g and sending my messed up Vibrant to Shorty, to see if he can come up with a solution.
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
Nice, I didn't know it was available already. Congrats.

Who's Shorty BTW?? LoL
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Froyo leaks till KA5 had mount issues, the drive letters were reversed and external sd card was mounting as 2 GB sd card. It was fixed by Samsung starting from KA5 leaks. One could also try to replace /bin/vold and /etc/vold.conf and /etc/vold/fstab from KA5 or later releases.

ODIN is buggy and very unpredictable, Heimdall always behaved at least in my hands. It was just an idea that perhaps ODIN was not repartitioning internal SD therefore reverting to stock UVJFD fail, perhaps Heimdall will work. Technically once phone boots up, one could repartition and revert to stock.

However, if you read Canadian story of Froyo OTA update. Samsung had to pull the update and replace bricked Bell Canada Vibrants. The story had at least one common point. The customer who were running ext4 and applied OTA, it damaged internal SD card. Samsung had to replace the motherboard on those Canadian Vibrants. I hope it is not a case here. I am sure after that Repartition is the only hope. If we cannot repartition the internal sd card, then I am afraid we are in trouble.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
This is one of the few things I knew from the start! :)

I had ODIN'd a factory default set of .tar's and now I can't even get the phone into DL mode. With that development I think I've had it. I'm giving up but wanted to post my appreciation to those who were working with myself as well as the others. Your efforts are greatly appreciated.

I only hope I can contribute as much one day.
[Vibrant Q&A, Help & Troubleshooting] :
Heimdall not letting me repartition

I'm loading all the necessary files, but once I load the pit file, the start button greys out and I can't push it... no workee. please helpee.

Looks like in order to repartition, I need all the files...

should I go straight to JFD or go to KA6 or KB1

Anyway....

I need these files, they only show up in some of the stock roms, can I mix and match....

SBL, boot.bin. param, database, recovery

EDIT: I did mix and match...

EDIT: heimdalled to stock JFD... it's a no go

EDIT stock KA6... it's a no go

EDIT stock KB1... it's a no go
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
darn!!! you must have replaced the secondary boot loader with buggy one. Your only hope is make USB JIG http://factoidz.com/how-to-unbrick-your-samsung-vibrant-galaxy-s/
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
I have no experience with Heimdal-fronted (GUI). I always use command prompt Heimdall. (Also, I rarely use Heimdall on Windows, instead I prefer Heimdall on Linux)

But here are the commands from Heimdall Bible:

1. The nomenclature for running Heimdall from command prompt or terminal is :

heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin

where factoryfs.rfs cache.rfs dbdata.rfs param.lfs zImage and modem.bin are the files you extracted from the T959UVJFD.tar file. Do not worry about primary-boot or secondary-boot. For example, I put my Heimdall_Files folder on my c: drive, or C:\Heimdall_Files.

So my Heimdall command prompt would look like :

heimdall flash –pit c:\Heimdall_Files\s1_odin_20100512.pit –factoryfs c:\Heimdall_Files\factoryfs.rfs –cache c:\Heimdall_Files\cache.rfs –dbdata c:\Heimdall_Files\dbdata.rfs –param c:\Heimdall_Files\param.lfs –kernel c:\Heimdall_Files\zImage –modem c:\Heimdall_Files\modem.bin

2. You can flash just the modem or kernel by leaving the rest of the files out like this

heimdall flash –pit c:\Heimdall_Files\s1_odin_20100512.pit –modem c:\Heimdall_Files\modem.bin –kernel c:\Heimdall_Files\zImage

EDIT: Here is Shorty's Hemidall Tutorial http://board.teamwhiskey.com/viewtopic.php?f=29&t=1196
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
ssiddiqi1, get on yahoo if you can, lets continue with the process of where we were at, I hope to God this time my phone works.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Has anyone been able to successfully unbrick their phone yet?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
ameedi,

if you do not mind, can you please get the Heimdall setup from the link I posted in previous post?

I tried moving some heavy furniture at home and pulled my back muscles. under pain killer medicine, I am afraid my brain may not work properly while trying to walk you through. Can we do it tomorrow evening?
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Alright but I am going to take a chance and move on with flashing the stock Uvjfd or has anyone tried this http://xdaforums.com/showthread.php?t=954509
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Yes, a couple of others had

you will get into a boot loop, and you could also damage your secondary boot loader, after that you may not get into download mode. in my opinion not worth it, as your phone had already booted with Eugene_2E_JK2_FROYO.

Better get Heimdall setup then taking more risk, please
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Has anyone tried ODIN'ing Eugene_2E_JK2_FROYO and PIT512 from this link http://eb-productions.net84.net/vibrant/vibrant-unofficial-tmo-2-2.html

with REPARTITION checked? If so what was the result? I know, Eugene suggests do not check repartition only load pit512 in ODIN.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
I just tried flashing Eugenes Jk2 and pit12 with repartition but it seems to be same, all it is doing is booting up and thats it. Which means I still have the storage problem.
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
Yup,

tried that too.

Same result. Vibrant- Screen off.

Thanks
[Vibrant Q&A, Help & Troubleshooting] upbeat.addict:
alright guys, i have Heimdall'd (is that a word?) the Eugene_2E_JK2_FROYO setup and marked it for re-partition. the good news first, flashing the primary and secondary bootloader that's included does not appear to be a risky move. The bad news, sd card still unmounted and it appears to have the same effect as Odin. Phone boots up, but no sdcard device present.

atm, im not convinced that Odin or Heimdall can actually touch the internal sd card, and the re-partitioning is actually the rom's partitions only. there is an attempt to wipe the /data/ directory (internal sd) but it always fails because it cannot mount the device properly.

i will to continue read up on some more linux commands and verify the hardware device, and figure out how to mount it correctly and repartition. i have a feeling that the MBR of the internal sdcard is fudged. This post is looking interesting because it contains actually MBR's that can be used with "dd" to fix a MBR:

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

not sure of what use it will be. it should be noted that the MBR for the vibrant contains a loopback device with ext4 (i.e lagfix)

fyi, these are all just guesses at this point. im by no means a pro linux user and am coming by this info via the forums and google searches. good luck everyone.
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
I'm afraid that I can't figure out what's up with my phone.

I ended a phone call and it was a black screen. So I did a battery pull and it was stuck on the OC Kernel flash screen. I let it sit for about ten minutes assuming that it's not booting. I hooked it up to ddms and it just said something about /system/bin/sh or whatever. So I tried to ODIN back... it rebooted but kept looping at the grey battery screen. I disconnected the cable and it started to boot up with the T-Mobile animation and stuff but then it just went black. ADB doesn't pick it up either. I started up again and the same thing. So what's the next step?

EDIT:

I tried this: http://eb-productions.net84.net/vibrant/vibrant-unofficial-tmo-2-2.html

and I was able to get my phone to boot... but it doesn't detect my sdcard or internal memory.

Any ideas?

Is there any way that I can access my internal storage so I can back it up to my pc?
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
This is exactly what all of us here are talking about bud.

Sorry, so far, our internal SD seems like it's Toast. Nothing will salvage it.

For the moment.

No ADB, no root, no nothing for me either.

I've flashed 10 different ROMS with 5 other kernels. nothing is getting my partition back to where it needs to be.

The Internal SD is F*K'd.

Sorry for the bad news.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Back it up to PC, everyone will be lucky if you can access internal sd card. OC kernel crashes had fried the internal card. That's why I personally think OC is a bad idea.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
ammeedi, moda (Allen) and a couple of others with whom I wroked off line.

Well, you can call it quit at this stage. Heimdal and repartition with Eugene's JK2 nothing had helped. I think it looks like Bell Canada kind of story where internal sd card was damaged, phones were booting, but internal card was not accessable, samsung ended up replacing motherboard, of course it cost those users Samsung ridiculous charges to fix the phone (as I read Bell/Samsung charged them $250.00)

Anyway, I do not think the internal sd card can be salvaged. We have tried all possible things. If you bought your phone from T-Mobile, flash the UVJFD and talk to TMO for warranty exchange, or call Samsung tech support for a warranty repair. Samsung will charge repair, even it is under warranty period, T-Mobile might exchange it if you have a 2 years contract.
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
That's what I figured but I couldn't tell for sure. Do we know what caused this at all?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
upbeat.addict

I do not believe it is mbr. The over clocking kernel corrupted /data partition which is not mounting, therefore you are not seeing the internal sd card. I am sure you know it, but anyway... Vibrant has internal 16 GB card, 2 GB reserved for OS and 14 GB mounts /dev/block/stl9 to /data which you see as 14 GB Internal storage (sd card). Kernel crash corrupted 14 GB partition therefore /dev/block/stl9 is unable to mount it. Therefore in Settings-->SD Card you see 00 for internal storage and you cannot unmount or format it. Look at various mount tables members posted, everyone is missing /dev/block/stl9 /data in the mount table.

Unfortunately, there are no good software which can read internal storage sectors and mark the bad sector, like we have several commercial partition managers for PCs. If somehow you could mount the internal sd card to your pc, you may be able to run a partition manager software on it. I am not sure it will fix it if card is damage beyond repair.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
You were using a over clocked kernel (probably DOW), and ext4, right? It crashed and left the /dev/block/stl9 /data damaged beyond repair or repartition-able (in slang - it fried your internal sd card with french fries and beacon)
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Sorry, It fails because 14GB partition which is used by /data is corrupted beyond ODIN or Heimdall capabilities to fix it. Therefore nothing mounts or unmounts it. It is not accessible.
[Vibrant Q&A, Help & Troubleshooting] :
given up THANK YOU ssiddiqi1 FOR YOUR HELP

I can't begin to tell you my thanks for trying to help with the issue. I've given up and I'm sending it back. Thanks again.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
xdarooted,

You are welcome. I wish I could have salvaged those bricked phone. Some members bought them at eBay/Craiglist. It is going to cost them $$$ to get it fixed.

Make sure you ODIN UVJFD with pit512 and repartition, before sending it back, even it does not boot after UVJFD.
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
Well I'm not trying to be an ass or anything but this wasn't just a little glitch and it isn't effecting just a couple of people here and there. It seems that an entire crowd of people are experiencing the same issues and messing their phones up beyond repair (thus far) redering it almost useless. Yet... aren't the kernels are still available? Seems kinda like keeping a virus on the forums and hoping that people don't download it. :rolleyes: I understand that everything is "at your own risk" but damn! Who would have thought that it would mess up the phones this bad?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Well, with due respect to all the developers. I do not believe over-clocked kernel are for daily drivers. Manufacturers design hardware with certain specifications, by over-clocking and over-voltage or under-voltage, a user is forcing hardware to operate beyond the limits, it was designed for. Therefore, you increase your risk of a hardware damage. Using Voodoo only for ext4 as a lagfix is different issue. In this case, you are using a different file system to read and write without putting stress on hardware. Therefore, I stay away from OC kernels. This is my personal opinion, not criticizing any developer. Although irrelevant to the issue-When RedHat was being developed in garage in mid 90s, I used to live in Raleigh, NC. I used to help them test and fix bugs in spare time. I assume, I know a little in and outs of Linux OS.
[Vibrant Q&A, Help & Troubleshooting] zentronic:
yeah i agree it says data wipe error and wont install the update ive tried everything guess it is going to ebay for parts . i even tried pushing the update zip back onto the internal sd using

adb push update.zip /sdcard

after droping it into the tools folder in the sdkin my case my girls phone now im in the dog house lol

i got 180 bucks for a vibrant with good amoled on ebay.i guess this one is going on auction too.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
if mount /data is not working due to bad sectors on sdcard, it will not work.

Samsung will charge approx $200 to fix it, for that money TMO is selling Vibrant 4G if you extend your contract for 2 years.
[Vibrant Q&A, Help & Troubleshooting] AngryDinosaur:
same problem

phone wont power up at all

so no download mode or recovery

what can i do?
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
Join the club and complain. That's it for now.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Have you tried following:

1) pull the battery for at 10 sec, put the battery back

2) start ODIN

3) plug USB cable to PC

4) hold vol +/- button

5) while holding volume +/- keys, plug the USB cable to phone

It might you into download mode