Database Users

Restoring a dd backup with Odin (A fix for a badly broken EFS)

I was reading rotohammer's post about an easy on-device backup method (using dd) that can restore data at a bit more of a lower level (Odin) than a nandroid backup. (EFS partitions, etc.)
It's possible to get your EFS partition in such a state that the /dev/block/bml3 and /dev/block/stl3 devices are no longer exposed on the device at all. This results in such nice behavior as the Cellular portion of the device not functioning at all. Providing you made a dd backup of all bml and stl devices (i.e. you have a backup of stl3 specifically,) you can recover from this situation.
Odin can recognize any file defined in the .pit file, when they are flashed to the PDA slot in a .tar, and place them in their proper partitions. One benefit to this is that if you get the EFS partition to a place where the device nodes aren't exposed to the OS anymore, you can restore it to working functionality.
These are the possible filenames that Odin recognizes: (from 512.pit, other .pits may have differing partition schemes.)
Code:
ries.pit
efs.rfs (this is the file we are going to restore to fix a broken EFS with a dd backup)
sbl.bin
param.lfs
zImage (kernel and recovery)
factoryfs.rfs
dbdata.rfs
cache.rfs
modem.bin
Any of these files are flashable by Odin3 1.7 if you place them in a .tar and put in the PDA slot.
rotohammer's post details which device matches up with which filename, in this case what we want to do is name the /dev/block/stl3 backup efs.rfs, and add it to a tar file (efs.tar) then flash it.
Assuming you have adb installed, and the stl3.bin file in the current folder:
adb push stl3.bin /sdcard/efs.rfs
adb shell
$ su
#
# cd /sdcard
# tar -cf efs.tar efs.rfs
# exit
$ exit
adb pull /sdcard/efs.tar
Now, get into download mode, open odin, stick efs.tar in PDA slot, and press start. Bam! EFS fixed
Note that in normal conditions you won't need a backup this extreme (copies of the files inside will be ok) but i've seen a number of users who have gotten their phones into this state (and did it myself during testing!) - This works with all the partitions you back up with dd that have support in your .pit file.
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam

how to obtain stl3 and bml3
in adb
adb shell
su (allow the root access)
cat /dev/block/stl3 > /sdcard/stl3.bak
cat /dev/block/bml3 > /sdcard/bml3.bak
rename .bak by .bin
sorry for my english.

Da_G said:
I was reading rotohammer's post
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam
Click to expand...
Click to collapse
How can I make ODIN back of my ROM, a little guide would help. Thanks in advance for your response.

trip007in said:
How can I make ODIN back of my ROM, a little guide would help. Thanks in advance for your response.
Click to expand...
Click to collapse
hi please use the search button , you will easily find how to , this is a 5 month old thread ....

Gonna go out on a limb and assume they are using search, hence the 5 month old post bump.

whiteguypl said:
Gonna go out on a limb and assume they are using search, hence the 5 month old post bump.
Click to expand...
Click to collapse
I dunno how they used it but htere s a 2 weeks old post by darky in the i9000 section .

can someone upload efs.rfs?efs.tar?
i screwd mine and i dont have backup

Every device has there own efs folder (IMEI and stuf).
So if you don't have a backup I don't know what to tell you...

thats not nv_data.bin or imei and product code stuffi want efs partition structure
wich come from stl3.bin

This thread may be almost a year old, but it just saved my Infuse.
Once again it just proves that if you serach, read, try and search, read and try somemore, you can find the answers.

Truckerglenn said:
This thread may be almost a year old, but it just saved my Infuse.
Once again it just proves that if you serach, read, try and search, read and try somemore, you can find the answers.
Click to expand...
Click to collapse
Someone gets it lolz .
Sent from my SAMSUNG-SGH-I897 using xda premium

moeinf said:
thats not nv_data.bin or imei and product code stuffi want efs partition structure
wich come from stl3.bin
Click to expand...
Click to collapse
Sorry im late...but adamoutler was going to post a blank efs partition in another thread . Dont know what happenwd to it tho.
Sent from my SAMSUNG-SGH-I897 using xda premium

Da_G said:
I was reading rotohammer's post about an easy on-device backup method (using dd) that can restore data at a bit more of a lower level (Odin) than a nandroid backup. (EFS partitions, etc.)
It's possible to get your EFS partition in such a state that the /dev/block/bml3 and /dev/block/stl3 devices are no longer exposed on the device at all. This results in such nice behavior as the Cellular portion of the device not functioning at all. Providing you made a dd backup of all bml and stl devices (i.e. you have a backup of stl3 specifically,) you can recover from this situation.
Odin can recognize any file defined in the .pit file, when they are flashed to the PDA slot in a .tar, and place them in their proper partitions. One benefit to this is that if you get the EFS partition to a place where the device nodes aren't exposed to the OS anymore, you can restore it to working functionality.
These are the possible filenames that Odin recognizes: (from 512.pit, other .pits may have differing partition schemes.)
Code:
ries.pit
efs.rfs (this is the file we are going to restore to fix a broken EFS with a dd backup)
sbl.bin
param.lfs
zImage (kernel and recovery)
factoryfs.rfs
dbdata.rfs
cache.rfs
modem.bin
Any of these files are flashable by Odin3 1.7 if you place them in a .tar and put in the PDA slot.
rotohammer's post details which device matches up with which filename, in this case what we want to do is name the /dev/block/stl3 backup efs.rfs, and add it to a tar file (efs.tar) then flash it.
Assuming you have adb installed, and the stl3.bin file in the current folder:
adb push stl3.bin /sdcard/efs.rfs
adb shell
$ su
#
# cd /sdcard
# tar -cf efs.tar efs.rfs
# exit
$ exit
adb pull /sdcard/efs.tar
Now, get into download mode, open odin, stick efs.tar in PDA slot, and press start. Bam! EFS fixed
Note that in normal conditions you won't need a backup this extreme (copies of the files inside will be ok) but i've seen a number of users who have gotten their phones into this state (and did it myself during testing!) - This works with all the partitions you back up with dd that have support in your .pit file.
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam
Click to expand...
Click to collapse
If I could Ill kiss you! Thank you it really did the trick!

Disabling OLD Voodoo Lagfix

Ok, I installed one of the very first Voodoo lag fixes back in late/mid October. I had been pretty busy so I had not been keeping up to date with the recent upgrades for the phone.
My question is how do I remove this Voodoo lagfix? I have read the HOWTO but this is only for Voodoo 4 and 5, and I am assuming I have 1, or maybe nto even one as I think I only had it when there was only the lagfix for voodoo.
I believe I recall someone saying something about installing some file titled disable_lagfix but I do not recall.
Thanks guys.

Yes there should be a thread about it... Theres an app that I used called reboot button from a thread on xda that turned off voodoo for me.. Might want to look into that..
Sent from my SCH-I500 using XDA App

Search the market for voodoo. That app will pop up
Sent from my SCH-I500 using XDA App

Search for a thread entitled "how to completly remove voodoo lagfix" by adrynalyne, it's got your answers
Sent from my StupidFast Blackhole Fascinate using XDA App

the person is referring to the old voodoo lagfix, I don't think the "how to completely remove voodoo" thread covers it anymore... lemme see what i can find
Edit: this is what I found/saved on a text file
As stated by Adrynalyne:
This should not normally be needed...but in my case it was. YOU WILL LOSE ALL DATA. THIS IS NOT A TRIVIAL PROCESS.
If you need to remove Voodoo, for whatever reason (mine was not booting), this is how you do it:
1. Download original.mbr from here:
http://adrynalyne.us/files/kernels/sgs/original.mbr (right click save as....)
2. Download stock kernel:
http://adrynalyne.us/files/kernels/sgs/stock.zip
2. Boot to cwm (battery pull, and hold up volume while putting it back in and connected to usb), and put original.mbr and stock.zip on your sdcard. Mount as mass storage or adb push them to sdcard.
3. Use adb to restore the mbr:
Code:
cat /sdcard/original.mbr > /dev/block/mmcblk0
4. Use cwm to restore the stock.zip (kernel).
5. Mount dbdata and nuke the contents.
Code:
mkdir /dbdata
Code:
mount -t rfs -o nosuid,nodev,check=no /dev/block/stl10 /dbdata
Code:
rm -f /dbdata/*.*
6. Reboot back to stock recovery.
Wipe data.
7. Apply CWM. Wipe data.
8. Reboot.
Done and done. Nandroid restore back after this, if you wish.
If this doesn't work, take the illogical steps of:
Flash system, kernel and PIT with Odin. Remember, only use pda and pit sections.
Wipe again.
Click to expand...
Click to collapse
The only hard part now is to get the files from adrynalyne himself. Good luck.
Edit again: I think the version you have is Voodoo 4, so the "How to completely remove voodoo" thread does cover you! SOrry about that!

[Q] .sh script help

Hey guys, need some help with this one from some of you with more android/linux experience than me.
In my continuing quest to make Blackhole as customizable as possible I've been working on a way for users to easily install paid apps (legally downloaded of course), and stuff that I don't have available in rom manager in one easy step at the same time the rom is installed. In pursuit of this goal I've found that it's possible for the update-script file inside a clockworkmod zip to call a script in the zip as well. I've gotten it to say it's run the script, but it doesn't do what it's supposed to. here's what i've got:
#! /bin/
busybox cp /sdcard/app/* /system/app/
When I type the command into a terminal on the phone it works. When I open an adb shell and type "bash install.sh" it works. But when I get the update.zip to run the script, or run it in root explorer it just says it's run it, but doesn't do anything.
Is there something I'm missing about how to call the script? Do I need to somehow add the bash program to the zip file so it can run the script right? Has anyone ever done something like this who can point me in the right direction?

do you have an output you can show us?
Sent from my SCH-I500 using XDA App

This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.

Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....

Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.

wizang said:
This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.
Click to expand...
Click to collapse
Could very well be, it's not showing me any output when i run it the two ways it doesn't work, just says it's been run.
vegittoss15 said:
Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....
Click to expand...
Click to collapse
Haha, caught me. I was trying to remain incognito Yeah, i'll get 2.4 loaded back up on rom manager for you today. But if you flash 3.0 it will upgrade you to DL09 and the DJ05 kernels and modem are compatible, or at least no one i know of has had issues.
imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
sdcard is mounted when you go to recovery, because it's got to access the update.zip file on it to install anything. I'll try your code, do you know what to put after SYSTEM: to make it go to the /app directory? thanks for the idea, it's a different way to go, i didn't think about the fact the update-script could access the device if you don't use the "package" tag.

Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..

dcow90 said:
Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..
Click to expand...
Click to collapse
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.

I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.

This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500

imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
Well I gave that a shot, and i think it could work, but the recovery wouldnt do it. it says "non-package source path not yet supported" good idea tho.
yutsoku said:
I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.
Click to expand...
Click to collapse
If you can that would be great.
n0yd said:
This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500
Click to expand...
Click to collapse
I spent a good bit of time searching and most of the scripts I found were much more complex than what i need, or were written to run on a computer, which i've already done.

sonofskywalker3 said:
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.
Click to expand...
Click to collapse
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App

jt1134 said:
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.

sonofskywalker3 said:
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.
Click to expand...
Click to collapse
#!/bin/sh for scripts in recovery. #!/system/bin/sh for scripts in android.
Sent from my SCH-I500 using XDA App

[Solved] Remove thread requested

Sup I know there is a hack for ext4 on the nexus s but haven't seen anything for the NS4G. Is it the same hack or what? If so it seems a little complicated to get going with the tutorial given. Does anybody have a better tutorial or if there is a different hack for the 4g can you direct me to it please? Much appreciated.
Sent from my Nexus S 4G using xda premium

Joshhayes801 said:
Sup I know there is a hack for ext4 on the nexus s but haven't seen anything for the NS4G. Is it the same hack or what? If so it seems a little complicated to get going with the tutorial given. Does anybody have a better tutorial or if there is a different hack for the 4g can you direct me to it please? Much appreciated.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
not sure what "ext4 hack" youre talking about, but there is an ext4 mount script. itll give you a little speed/performance kick overall. but its not really a hack, its a fix. type this in a terminal emulator app..
su(press enter)
mount -o remount,noauto_da_alloc /data /data(press enter)
youll have to type it in after each reboot. or you can use an app to run it after each boot. most custom kernels already include it or some version of it, stock doesnt include it.

Use dsixda's rom kitchen to unpack boot.img: http://forum.xda-developers.com/showthread.php?t=633246
Then do this: http://forum.xda-developers.com/private.php?do=showpm&pmid=4452832 and repack.

snandlal said:
Use dsixda's rom kitchen to unpack boot.img: http://forum.xda-developers.com/showthread.php?t=633246
Then do this: http://forum.xda-developers.com/private.php?do=showpm&pmid=4452832 and repack.
Click to expand...
Click to collapse
That second link seems to not work, it says this "Invalid Private Message specified. If you followed a valid link, please notify the administrator"

Joshhayes801 said:
That second link seems to not work, it says this "Invalid Private Message specified. If you followed a valid link, please notify the administrator"
Click to expand...
Click to collapse
fter unpacking the boot.img go to BOOT_EXTRACTED/ramdisk and open the file init.herring.rc and add the following in green to the following to lines and save:
Code:
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/system /system wait ro noauto_da_alloc
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata /data wait noatime nosuid nodev noauto_da_alloc
Sorry bout that

Sweet. Thanks. I'll be doing this later after I run errands.
Sent from my Nexus S 4G using xda premium

snandlal said:
fter unpacking the boot.img go to BOOT_EXTRACTED/ramdisk and open the file init.herring.rc and add the following in green to the following to lines and save:
Code:
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/system /system wait ro noauto_da_alloc
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata /data wait noatime nosuid nodev noauto_da_alloc
Click to expand...
Click to collapse
I think I've done everything right and getting ready to flash soon. How will I know if it worked?

So I did everything you said, repacked (no errors, everything worked fine) now when trying to flash it gives me this "error in/tmp/sideload/package.zip (status 6)" Do you have any clue why this would happen?
EDIT: NVM I fixed it.

I don't understand why people want to make it harder on themselves. just run the script, it does the same thing.

simms22 said:
I don't understand why people want to make it harder on themselves. just run the script, it does the same thing.
Click to expand...
Click to collapse
It's not really hard...it's actually kind of easy with that particular kitchen. Plus I am willing to do it all because I like learning.

Joshhayes801 said:
It's not really hard...it's actually kind of easy with that particular kitchen. Plus I am willing to do it all because I like learning.
Click to expand...
Click to collapse
good answer

Hmm
Tried to flash the repacked rom and got stuck in a bootloop. Really can't find anything on why this happened or how to fix. Restoring nandroid as we speak.

simms22 said:
good answer
Click to expand...
Click to collapse
Lol. yeah well we all gotta start somewhere. I practically live on xda as it is, so I may as well learn as much as I can and hopefully become a contributor in some way. It started as just wanting to dink sound with my own device but now that I know that I CAN do it. I want to go further with it.
Sent from my Nexus S 4G using xda premium

EU bug fix guide!!!!!!!!! actuall fix NOT external sd workaround

ok so first boot into recovery make a nandroid than remove your external sdcard and download the odin flashible semaphore kernel for vibrant from semaphore.gr (be sure its the newest one) now go to download mode and flash that. as soon as its done it will reboot and you want to reboot into recovery. next plug it into your pc while still in recovery mode and run the adb devices command to be sure your devie is connected and recognized now go to adb shell and run these commands hitting enter after each line
parted /dev/block/mmcblk0
print
rm 1
rm 2
and what that does is removes all your partitions so just do rm X for each partition number you have puting a space between rm and whatever number you have. now go back to download mode and flash Eugene_2E_JK2_Froyo.tar heres a link to download http://d-h.st/VGX. and your going to go through the process of everything flashing in oden. besure to flash that as pda. than you will be at stock recovery and you will get the ant mount bla bla bla or if it boots straight to the rom to thats fine. and now go to settings and format internal sdard under storage settings your external sdcard should still be REMOVED now after thats done reboot and you should have a fully working vibrant. this fixed mine. if it doesnt work tell me hope i helped

also works with captivate and facinate too!!

First and foremost, thanks for posting this guide.
I'm gonna' run through this right now. Wish me luck. :fingers-crossed:

if it doesnt work tell me
N00B_IN_N33D said:
First and foremost, thanks for posting this guide.
I'm gonna' run through this right now. Wish me luck. :fingers-crossed:
Click to expand...
Click to collapse
if it doesnt worl tell me

Would it sound messed up if I wanted to EU my phone just to try this lol nice find C looks like a really nice guide
Sent from my Nexus 7 using xda app-developers app

Not 100% working yet sorry people
But im putting alot of work into it.
Sent from my SGH-T959 using xda premium

LOL
So I attempted your guide...and the good news is that i was able to access recovery right after flashing the sephamore kernel .tar in odin. The bad news on the other hand is that I was unable to execute the adb shell commands you've listed in your guide. I got an error stating that "there is no such file or directory". So I skipped the commands and flashed ICS passion v13 and it booted!!! but only to be followed by the dreadful "Encryption Unsuccessful" screen lol.
I took a screenshot of the EU screen by pressing the power button hoping to upload it here for you guys to see...but this is where things got really strange. So I removed the battery, sdcard, and inserted the sdcard into my pc to look for the screenshot and it wasn't there!!!. So this means that the screenshot was saved to the internal memory. I can sense I am getting closer to fixing my old vibrant.
Stay tuned

Like Merio I, too, flashed the Semaphore kernel via ODIN.
But unlike him, I cannot access Recovery.

fham said:
Like Merio I, too, flashed the Semaphore kernel via ODIN.
But unlike him, I cannot access Recovery.
Click to expand...
Click to collapse
Try the following commands in adb.
adb devices
adb remount (might fail but don't worry)
adb reboot recovery

i use devil kernel to access the recovery.....but at 'parted /dev/block/mmcblk0' this step i got the same as merio90

Yeah devil or semaphore. Semaphore is just easer to boot to recovery
Sent from my SGH-T959 using xda premium

Update
Well after 5+ hours of countless rebooting and flashing/modding I have failed to bring my vibrant back to life. However... I was able to go real deep into the device's storage hardware both internal and external(sdcard) and discovered that the internal storage is alive and functioning. In other words it is not hardbricked or physically damaged as a result of the EU bug...it is just corrupted and unable to mount.
Furthermore I attempted several times to create or recreate the partions on the internal sdcard but It just would not allow me to do so. By the way this is all done using the "parted /dev/block/mmcblk0" command(s). Hopefully there is some one who understands how to use this "parted" function in adb as this can be a very useful tool in restoring our devices back to normal.
Here are some helpful details I have learned in the process of all of this...
For those who are having trouble entering the commands in the guide make sure you are entering a space in between "parted" and "/dev/..."
At first I forgot to enter the space and as a result I got an error reading "no such file or directory" so make sure to include the space.
adb shell >>>>>>>>>>> Don't forget to enter this command first...won't work otherwise.
parted /dev/block/mmcblk0 >>>>>>> mmcblk0 is the external sdcard (at least in my case it is) while mmcblk0p1 is the internal sdcard (in my case)
print >>>>>>>> This command list the specifications for the storage device mmcblk0 along with some other useful information.
rm 1 >>>>>>>> This removes partition 1
rm 2 >>>>>>>> This removes partition 2 (if existent)
While still using the "parted" function in adb shell you can simply type "help" and it will give you all the details on how to use this useful tool.
Well I guess that is all I can say for now. Thanks again cannondale...your guide was certainly helpful and allowed me to learn more about this EU bug and how it is "bricking" our devices. This is certainly a step forward in the right direction...I am confident we will have this EU bug squashed pretty soon once and for all.
signing off.

@merio90 i did a lot of research on the EU BUG read my thread.... http://forum.xda-developers.com/showthread.php?t=2176108

manu_ha2001 said:
@merio90 i did a lot of research on the EU BUG read my thread.... http://forum.xda-developers.com/showthread.php?t=2176108
Click to expand...
Click to collapse
Thanks manu...this isn't the first time I've read your thread concerning the EU bug. I simply ignored it at first because it seemed a bit too technical at the time. But now that I've gone through this guide cannondale has provided your thread certainly makes more sense. I'll get back to working on this case soon.

So has anyone besides the OP gotten this to work?

well cannondale has

Merio90 said:
... This is certainly a step forward in the right direction...I am confident we will have this EU bug squashed pretty soon once and for all.
Click to expand...
Click to collapse
@Merio90 ... Just wondering if you made any further progress on the matter. Thanks to cannondaleV2000 for opening these doors and to Merio90 for the detailed posts (esp. concerning syntax). Very interesting thread.
I gave it a go but no nookie for me. In a nutshell, GNU Parted only appears to work on the external sdcard (mmcblk0p1) and not on the internal. Here are my results (after numerous attempts).
RECOVERY ACCESS
My observations flashing Semaphore JB .tar's (after a fresh Odin to Eugene_2E_JK2_Froyo.tar).
* Hangs on Semaphore splash: 2.9.21v, 2.9.15sv, 2.9.12sv.
* Recovery access successful: 2.9.21sv, 2.6.5v, 2.5.0sv
EXTERNAL SD REMOVED:adb shell
# parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
adb shell
# parted /dev/block/mmcblk0p1
parted /dev/block/mmcblk0p1
Error: Could not stat device /dev/block/mmcblk0p1 - No such file or directory.​EXTERNAL SD INSERTED:adb shell
# parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
adb shell
# parted /dev/block/mmcblk0p1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p1
Welcome to GNU Parted! Type 'help' to view a list of commands.​So ... it's rather curious that cannondaleV2000 actually had access to his mmcblk0 while others weren't so lucky. That's the obvious key to using the parted functionality on the internal sdcard. If only we could break through that road block ... and return to the internal sdcard holy grail!! Any thoughts?

@yosup
No I have not made any progress other than the info I have already posted. My vibrant is no longer my daily driver, my Galaxy Nexus is... so my apologies for not giving this issue a higher priority.
I was only able to "fix" my vibrant to the point where I was able to use the SD card swap method many of us have attempted. In case you were unaware I had to take some extra steps as my vibrant was totally screwed up. It was unable to read either internal or external sdcard so that was an obstacle I had to overcome and that's how cannondale's guide was able to help me. So as of today no progress has been made...I haven't really worked on this problem in quite a while now so any progress has come to a halt for now...until someone comes up with a new guide On another note, the good news is that I have yet to encounter the EU bug on JB 4.2.2 (AOKP M1). So those who are using the sdcard swap method you should try a JB ROM...they seem to not be vulnerable to this EU bug.
Sent from my Galaxy Nexus using xda app-developers app

Try this
http://forum.xda-developers.com/showthread.php?p=44794873
Sent from my GT-I9505 using xda premium