yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] anteko:
To answer your question follow the link in ssiddiqi1's post.

I was not able to push the script while 'eugenes rom that does not brick' was on my phone. So I used odin to flash a voodoo kernel. I was then able to push the sdparted.txt script and repartition the sd... then simply flashed back to stock and viola, I have one less paper weight in my house :D

Let me know if you have any issues with the instructions in the link, I found them a little confusing but not too bad. Good luck!
[Vibrant Q&A, Help & Troubleshooting] anteko:
Here is the PDA I used with odin to get it to work. I will write a complete guide on how I did it later tonight when I have more time.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
This could be a miracle in the making. I am going to look for the sdparted.txt now and see if I can figure out how to use adb. It's all greek to me at this point.
[Vibrant Q&A, Help & Troubleshooting] traicer:
so is this problem fixed?

if so can someone post a summery of how they got it to work for the others? then we can ask for it to be added to the sticky library post
[Vibrant Q&A, Help & Troubleshooting] :
This is great, I kept getting file not found for the sdparted file. Can't wait for the instructions.
[Vibrant Q&A, Help & Troubleshooting] wbexpress:
Wow, this would be great to those who have the main "similar" issues going on. Me and my buddy Murphy and his law :confused: . It seems I am the only one with the specific issues of not being able to get Odin to recognize the phone/mounting not opening the drives up/can't get ADB to recognize the device. I guess I should be asking a different set of questions than everyone else: what is the most likely reason I cannot get the computer to recognize Odin and the SD cards? Since I have the ability to use a card reader and Root Explorer to transfer things to the internal card and flash, is there "something" I can do along those lines? TIA...
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
It would be much better if someone would make a one click method or something for the sd parted fix that some have claimed worked for them, I was one of the first ones to brick my phone this way, in fact I even started this thread hoping to fix my phone. My phone has been bricked for nearly 6 days now. Please someone figure this out and thank you.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
I haven't solved my problem yet but adb is not as bad as it sounds. I'm struggling with access.
[Vibrant Q&A, Help & Troubleshooting] anteko:
I think I'm the only one who has gotten has been able to get this problem fixed so far. So here's a summary of what I did:

Firstly, I think many people with this problem are using Eugene's ROM That Does Not Brick.. I had no luck with the following process while I had this flashed on my phone, so I would recommend using odin to flash this instead.

1. Download and install the Android SDK starter package. Really, you probably just need these two files adb and AdbWinApi.dll.. I'm no expert so I'm not sure if you need to install or just use those two files. Save both of these files to your system32 folder. I believe you also need JDK for this which can be found here http://java.sun.com/javase/downloads/

2. Download sdparted.txt from this thread. Save it directly to your C: drive.

3. Open Command Prompt and enter the command "adb push /sdparted.txt /sbin/sdparted" then enter "adb shell chmod 755 /sbin/sdparted". If all goes well and you don't get hung up on any of these steps enter the command "adb shell", and then "sdparted -efs ext4"... it will ask you multiple times "Do you want to continue?" Just answer "Y" to this every time. When its finished, you should see something like this.

4. Get your phone into download mode by holding down the +/- while the phone is off, then connecting to your computer with odin running via USB.

5. Flash to stock using odin.

If you have any trouble with any of these steps let me know and I will try to work through them with you, it wasn't a very straight forward process for me and I got caught up quite a few times on various things. Hopefully this works for everyone ")
[Vibrant Q&A, Help & Troubleshooting] jangst123:
I'm not sure anteko had the same problem!!!

I think his problem is fixed, but the DoW bricking problem after 2 to 3 days, I believe is different!
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
I understand what kernel you are running. But what ROM please.
[Vibrant Q&A, Help & Troubleshooting] wbexpress:
Hey, any of you who are savvy enough: The terminal Emulator works as it should. Theoretically, shouldn't the commands used with ADB work with TE? If so, can someone please tell me the steps?
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
I wish I knew. I'm still learning to spell adb.
[Vibrant Q&A, Help & Troubleshooting] wbexpress:
Levity is good, keeps one from going bonkers :D. Time to "reboot". Hope there's a small miracle in the morning.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
Using adb I cannot get the # symbol to show up when I shell. Only the $ sign. Does this mean I do/do not have root access? Everytime I try to push the sdparted file I get 'permission denied'. I also can't get the shell to run while in recovery. 'Applet not found'.

This one is wearing me out!
[Vibrant Q&A, Help & Troubleshooting] :
yes this means no shell root, SuperOneClickv1.5.5-ShortFuse, Eugenes no brick, and device working in debug, was the only successful combo to start pushing.
[Vibrant Q&A, Help & Troubleshooting] :
Anteko, did you originally come from the DOW bricking problem? Really need to know what rom you were on with the i1900 kernel you used.

I can get root access in shell and typing su, but I can't keep it rooted so to exit and push files using adb push.
[Vibrant Q&A, Help & Troubleshooting] anteko:
My phone was bricked almost immediately after I flashed the ROM... probable 2 or 3 hours, not days. But either way, the same issues with the sd being unaccessible and the phone looping seemed to be consistent to what I was experiencing with my phone.
[Vibrant Q&A, Help & Troubleshooting] :
Anteko, DOW14 is a kernel, not a rom. now that you were successful, you left out the part about what rom and kernel (Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-odin-pda) you were using.

I tried your voodoo i1900 based and another T959 base (stock+Voodoo-Froyo-T959-UVJK2.tar)

flashed upon eugenes no brick...but they both won't allow me to stay shell rooted so I can push.

superoneclick freezes trying to shell root
[Vibrant Q&A, Help & Troubleshooting] chris17922:
hey when developers brick their phone...how can they use warranty to get a new one??
[Vibrant Q&A, Help & Troubleshooting] :
modify eugene's no brick to have ryanza's oclf

Does anyone think that if ryanza's oclf was preinstalled (remove some of the bloat on eugene's no brick odin rom) it could fix the issue? is modifying his odin rom possible....
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
You need Superoneclickroot-1.5.5.Fuse. Without root you will get permission denied.

Looks like anteko got it working. Sdparted is your only bet to fix the partitions corrupted by DOW kernel crash.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Buy a new one under insurance plan
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
NO, and how are you can you use OCLF if phone is fully bootable?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Are you in download mode? Have you installed Smasung Drivers? make sure one of the COM field on ODIN turns yellow, otherwise START on ODIN will stay gray.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
anteko

Open Command Prompt and enter the command "adb push /sdparted.txt /sbin/sdparted" then enter "adb shell chmod 755 /sbin/sdparted".

The above in step 3 from you will over-write the sdparted executable with sdparted.txt script. to run sdparted script, you will chmod the sdparted.txt and execute the sdparted.txt script. It will fail with "file not found error" because of missing sdparted executable. adb push /sdparted.txt /sbin/sdparted will not push anything, anyway. /sdparted.txt means /sdparted.txt is on internal sdcard, which is not. Your push command failed and you executed sdparted executable manually. You command sdparted -efs ext4 means, you ran sdparted manually, not the script. But it does not matter, your picture show that you successfully converted entire internal sdcard to ext4, on which you odin eugenes kernel with voodoo then odin stock UVJFD which boots up your phone.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
With all due respect to everyone and all developers. Why over clock is needed? I am personally against OC. A few second gain of speed is not worth taking the risk of crashing hardware. Correct me, but I believe by overclocking, you are forcing chips to over work beyond the limits they were engineered. This could increase the risk of frying your hardware sooner or later. Same with colors and sounds, a little gain in colors and sound is not worth the risk of tinkering with internal hardware, therefore I had stayed away from voodoo colors and sound. I use only voodoo for ext4, I am on deodexed UVKB1 with KB1+voodoo kernel, that is it, nothing more to force hardware over work beyond its capacity. I prefer to stay with deodexed stock. I only hate TMO boot screens, sound and shutdown sounds, for that I had my own dancing droid boot screen with no sound and skate-boarding droid with Jazz music for shutdown.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
By over-clocking, you are forcing hardware to over work beyond the capacity they were engineered for. This could increase hardware crash/damage/frying (whatever) several folds. It is my personal belief, with all due respect to developers, that with OC sooner or later you may completely fry your phone.
[Vibrant Q&A, Help & Troubleshooting] :
YES, with eugene's no brick and any kernel, voodoo or stock, my phone is bootable... read my earlier posts.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Great!!! congratulation!!! sorry yesterday, I was away whole day therefore missed most of the posts. Also, my phone was not bricked, I was only trying to help others.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Eugene-no-brick is not for daily driver. It is based on 1900 sources. It is for fixing bricked phones. Have you tried leaving phone for 15 to 20 min after completely booting? then odining to UVJFD, boot up again and leave for 10-15 minute. After that, I would suggest re-root and install ROM manager and flash deodexed UVKA7 or deodexed UVKB1, boot up and leave 10-15 min then flash KA7+voodoo kernel or KB1+voodoo kernel.
[Vibrant Q&A, Help & Troubleshooting] fnjamesiii:
I have had this issue also.. How ever the way you can tell that you really bricked your phone is to connect it to you computer. What you are looking for when you power it on is will your computer recognize that a device was connected. If not you are finished you phone has been bricked. The phone is no longer sending data via the USB port.. So you will not be about to put into Download mode via any method that people are say to do. The buttons and ADB are not going to work. So this is the next part... When you phone boots up does it look stock if so EXCHANGE if not sorry you now have a really nice paper weight. I hope this helps
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Sorry, this is not a test for brick or no brick. Your PC may not recognize it for several reasons. First, missing Samsung USB drivers, Windows XP does not recognize it unless phone is completely boot up (XP is a crap), you are better of with Windows 7 or Linux.

If your phone boots up at least up to Vibrant screen or recovery screen or phone--!--pc icon, then it can be fixable. It can be a pain in the neck but fixable. In case of phone--!--pc icon, you need Heimdall and linux wroks best in this case. Heimdall command close-pc-screen may get you out of pc--!--phone screen.

You cannot get into download mode if you have a phone from July or August TMO stock. Those phones had a buggy secondary boot loader (sbl.bin) which was never updated to a newer one. Therefore, your combo buttons to get into download mode may not work... If you can get into recovery mode, download fixed sbl.bin from XDA and try to fix your secondary boot loader first.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
Here is where I am at the moment.

While the phone is sitting in the recovery screen I am unable to get the "#" symbol after a 'adb shell' command. All I get is "$".

If I try to push the sdparted.txt file I get "permission denied".

I think I need a confirmed rooted ROM that can be ODIN'd into the phone.

After 1 attempt all I get is "applet not found" trying to adb shell or logcat. (Unless I let the phone boot) Interesting thing the windows does when you logcat while the phone is completely booted up. Looks pretty busy. :)

What I desperately need to access to sbin on the phone to place the sdparted file there and execute it. I have tried a couple of ODINable ROMS with a voodoo kernel. I cannot make it work.

Looking for a link to an ODINable ROM that is already rooted.

or

perhaps the command that will execute the existing partition file in the sbin directory. (Does Linux call it a directory?)

Many thanks in advance.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
After flashing Euegen's-no-brick-Froyo, did you try SuperOneClickv1.5.5-ShortFuse.zip from http://xdaforums.com/showthread.php?t=803682? at least few members got re-rooted this way.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
I will now. Thank you.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
You can also give attached root.zip a try. extract it and execute rootme.bat from windows. No guarantee it will work. onclickrootme 1.5.5 from link in previous post is preferred.
[Vibrant Q&A, Help & Troubleshooting] :
maybe a superoneclickapps2sd

I posted something to see if superfuse could modify his superoneclick app...

http://xdaforums.com/showthread.php?p=11518511#post11518511
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
xdarooted, I did not fully understand the issue you posted the shortfuse thread. I believe file not found error is coming from sdparted.txt error from these lines

FATSIZE=

FATTYPE="fat32"

FATPATH="/dev/block/mmcblk0p1"

EXTSIZE=512

EXTFS="ext2"

EXTPATH="/dev/block/mmcblk0p2"

EXTEND=

SWAPSIZE=32

SWAPTYPE="linux-swap"

SWAPPATH="/dev/block/mmcblk0p3"

SWAPEND=

CMPARTED="/sbin/parted"

CMTUNE2FS="/sbin/tune2fs"

CME2FSCK="/sbin/e2fsck"

mmcblk0p2 p3 and p0 mount points do not exist on Vibrant. sdparted.txt was written for Nexus One, those are nexus one mount points. those could me replaced by your phone mount points. therefore I suggested a couple of times, if someone could post a mount table, perhaps it can be fixed.

EDIT: also, if you are editing a UNIX script, e.g. sdparted, on Windows, do not edit it with Notepad or wordpad. Windows often insert invisible \r\n\ ending to line which makes scripts behave funny and give weird "not found errors" . Best is to edit on Linux or use gvim/vim from http://www.vim.org/download.php I HATE BILL GATES NOTEPAD and WORDPAD. It never creates cross=platform compatible scripts/text files.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
Well I've tried this to no avail.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
what superoneclick reports when you try to root? root successful or failed?

if successful when run the command

su -C what happen?

give rootme.zip a try or does it fail too?
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
So this is where I'm at too;

I ODIN'ed the Darky's I9000 Kernel. I was finally able to use SDK. YES!

But without root, I can't push files

I tried OCROOT and ROOTME (doesn't work, it's an APK).

OCRoot just freezes forever after "OK" in the picture above.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
I am guessing that all of these require some ability to access or at least identify the internal SD card. I don't think that is happening in it's current condition.

Is there a way to execute the partition command (SDparted or whatever) that already resides in the sbin or does one even exist by default?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
rootme.zip which I posted had same things which superoneclick has except busybox. It has Superuser.apk and su. That is all you need for now to root. Once superuser.apk and su are in /system/app, you rub adb shell then su -C
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
Using DroidExplorer, I checked SBL folder, there exists no file named SDPARTED

I'm really, seriously, out of ideas here.

Everyone has been extremely helpful, but i've got a brick for -going 5 days now.

This goes into one of the other problems as well. What in the world do I do if I ever need to access the phone files yet, I do not have root access.

The whole point of this is to undo the corruption, yet I can't undo the corruption with the file script to tell the phone what to do (SDparted). And i can't push the file script without root. And I can't get root access from ROOT ME or from OCRoot.

just, Wow.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
without su you cannot run sdparted. You will get permission denied. you need to figureout how to root it.
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
SSiddiqi-

okay, I getcha. I have both Rootme and OCROOT. I see the files:

1. SU

2. Superuser.apk

how do I get these ONTO the phone?

Thank you
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
extract rootme.zip

run rootme.bat from windows after connecting phone to pc, like you did superoncick.

rootme.zip was written for Droid, I modified rootme.bat for vibrant. It worked on my vibrant, but again I am not bricked, therefore I said, no guarantee it would work.
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
Thanks,

I'll give it a try.

My phone is in Recovery right now, afer flashing Darky's I9000 Kernel.

So, at least ADB recognizes the phone. But I can't do much with it, without root.

I'll see if I can find another kernel that already has root access so that I can push sdparted file.

Thanks for your help.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
ODIN Eugene's no-brick-froyo

FIRST DOWNLOAD AND COLLECT EVERYTHING

Froyo with Downgrading back to Stock Possible:

Download here > EUGENE373_SamsungS_Froyo_PDA.zip

*Stock Froyo with*

~ Root

~ SuperUser.apk

~ Build.prop now Correct

~ Defualt.prop Also Correct

****

It is already rooted, then ODIN KB1+Vooddo kernel only from supercurio http://xdaforums.com/showthread.php?t=870480

boot, let's see if it bootsup leave it on for 15 min

if it does boots up after 15 min use adb push files from sdparted.zip to /sbin and chmod to 755 all sdparted files you push, then execute adb shell

su -C

and cd sbin directory, and execute sdparted -efs ext4, follow commands on the screen....
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
I'm pretty sure i've got that file from Eugene already. That's the one where ADB can't access the phone in Recovery.

But, in any event, I will give it a shot anyway.

Thank you. give me a moment. I'm still downloading.

BTW, i have all supercurio's stock+voodoo kernels.

So, we'll see what's what.

Thanks
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Then you are already rooted. You cannot access su because su recognize adb as unknown, unless you are in GUI mode and start su manually when su complain unknown trying to access root, you press "accept" button. since you are not booted therefore no GUI. Let me see if I can find a work around for it.

can you do adb shell

then su -C (-C is important)

does it still $ prompt?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
With Eugene's no-brick-froyo you are already rooted

after you get adb shell

type following at the $ prompt

su - unknown

It should grant adb super user access, and you would have # sign
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
Okay,

so yeah, Eugene's ROMs, can't connect with ADB.

i just downloaded the exact ROM that you posted in your link + Supercurio's KB1 Kernel.

Doesn't matter, can't connect ADB.

So, if I use Darky's Rom - ADB *(but no root)

If I use Eugene's ROM- no adb *(but has root access)

WTF>!
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
One thing I haven't tried, for both ADB and Root access-

Darky's 9.2 I9000 Rom

I'm going to try that right now.

Please hold. . .
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
with Eugene's, no adb access or when you type su in adb shell, you get permission denied? In the later case do what I posted in previous post

adb shell

at the $ prompt

type su - unknown
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
are you trying all this while in recovery mode?
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
Yes I am.

Once I flash with ODIN, it boots me into recovery,

that's when I use ADB.

So ,with I900 ROM- ADB connects

with Eugene's Froyo - ADB does NOT connect.

With Darky's I9000 - it's supposed to have ROOT, yet I'm still getting PERMISSION DENIED

I can't copy anything into SbL
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
With Darky's have tried

adb shell

su - unknown

do you get permission denied after typing su - unknown?
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
Also,

here's what I got

This is with Darky's I9000- 9.2 Resurrection Rom.

So, ADB (YES)

Root (NO)

Still no closer to putting SDparted.txt onto my damn phone.

This thing is just locking me out.

Other thing too, since the brick,

E: Dev . . .

has never mounted. Internal SD card does not exist.

So in addition to not have root access *(Can't access SYSTEM) folder, even if I had root, I don't know whether that would in fact, help/fix the situation because my internal SD *(E:) isn't even recognized.

Thanks. Really appreciate your help.
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
This is the result:

*sigh*
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
ummm the permission denied is not because of root access :-) you are typing wrong path.

tell where is sdparted.txt file is? move it to same folder where adb.exe is then type following

adb push sdparted /sbin/sdparted (no / before sdparted after push)

adb shell

su - unkown

cd /sbin

chmod 755 *

sdparted -efs ext4

post the picture of any error or success you get - Thanks
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
Okay,

I copied sdparted.txt into the adb.exe folder/directory. Even copied into tools. pretty much in every place where I would need to access it.

Should be accessing the correct file.

Tell me what i'm doing wrong.

Thanks
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
It does not look like rooted

type

adb shell

su - unknown

and post the picture of output
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Your su from Darky rom is not working on your Vibrant.

I am not much familiar with Darkys ROM

do this please

adb shell

mount

and post the picture of output. It will be a lot of out put, therefore you may have to maximize your cmd shell
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
I've tried a variety of su - things. This is like when I was in highschool on a date. No matter what I try. "Permission Denied".

Just changed kernels (desperate) same thing.

Grrrrrrr:mad:
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
do do not su, just do mount as I asked before and post the picture of out put. partition is completely messed up, that is why nothing executing
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
Bingo,

Here ya go.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
Sorry, thought you asked the guy with Darkeys kernel for that. I'll get that together for us.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Can someone please make a video tutorial on how to setup adb as well as how they unbricked their phone, thank you all for your contributions to the android community.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
ooops, yes I did ask him, sorry did not pat attention to name. But it is needed from anyone. mount table can provide useful information.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
Here is mine: