yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G2x] IRASadPanda:
I would try the third party apps (chomp, handcent, etc...). A vcard file is a contact right? I'm not sure why it would open in an email, but not in an sms...
[T-Mobile LG G2x] Волк:
Also, you may have to import it from the contacts app rather than just opening it direct. Theoretically it should automatically know what to do, but you never know.
[T-Mobile LG G2x] tjyoung:
Any resolution to this? I have the same issue.
[T-Mobile LG G2x] wishvak:
I'm a newbie in real trouble ....hopefully not by making a new thread on XDA.

If I 'm violating rules pl delete this.

I m with my G2X.I have stock 2.3.3 OTA rom.nandroid ,CWM ,Baseband July 2011 ,

Whenever I press "0" or "#" on my dialer it automatically goes to hidden menu.This cannot be undone even when i wipe factory data,clear cache,clear delvic cache,or by flashing a new rom(stock froyo or gb)..etc.

This problem makes number dialing impossible

Only way is to flash CM 7.then it doesn't come.

How can i undone this auto hidden menu from coming.

Thanks in advance
[T-Mobile LG G2x] IRASadPanda:
You answered your own question; **** LG/2.3.3 based ROMs, use CM based ROMs.
[T-Mobile LG G2x] wishvak:
Thanks for the reply.

I too agree CM7 the best.

unfortunately in CM7(stable and nightly 222) the APN get deleted automatically.

Tried APN backup and restore app,Fixing permissions,.....nothing works so far....

BTW when I bought this GTX and upgraded to 2.3.3. the hidden menu didn't automatically come.Since few weeks only this bug....

Any idea even to cure CM7 problem even......
[T-Mobile LG G2x] Longevite:
reset the phone to see the bug go away.
[T-Mobile LG G2x] wishvak:
Did factory rest,cleared cache,clears delvik cache.....nothing happens....still the hidden menu comes.....

No idea how to get rid of it.....at least if CM 7 doesn't delete my APN i could have stick with it.....
[T-Mobile LG G2x] TyMc:
I have this trouble too. Please help us.
[T-Mobile LG G2x] dexi:
GO Contacts

How about using GO Dialer from the market? Is their keyboard has the same issue?
[T-Mobile LG G2x] kompheak:
You said you got clockwork mod... factory reset... clear delvic cache n cache... how about formatting system???
[T-Mobile LG G2x] kenzi_100c:
i can't Press 0 and # on keypad on LG Ku5900

i can't Press 0 and # on keypad on LG Ku5900

please help me fix it

http://xdaforums.com/showthread.php?p=22862921#post22862921
[T-Mobile LG G2x] mr2000jp:
the same here , i think it started after i upgraded to 2.3.4 that was released a few weeks ago, i had to upgrade using the LG official flasher , its a must to upgrade the baseband , its really annoying ,

im almost sure there is some secret code to dial that will disable this menu , that is enabled some how
[T-Mobile LG G2x] mr2000jp:
at last , i fixed it , this time i took a little more time to think of the matter and i came to a conclusion , this matter happens due to some thing happened in the part of the FW that doenst get touched when flashing or wiping the rom , so reflashing the rom didnt fix it , first thing i did i made a backup of every thing using the custom recovery , then i went into the menu (the secret menu that keeps poping up) i got into it by pressing # which always happens to bring up that secret menu , after that i did a factory reset which is found in that menu , not the one you get into it from the settings icon , it took some time to reset , a lot longer than i thought it might take , just leave it alone till it restarts , after that you will find your self in the initial screen , like the one when you flash a new rom , just skip every thing and go directly to your dialer and press # or 0 and see for your self that its fixed at last , no secret menu any more , just a normal 0 or # , now you can do a full restore from the recovery menu using your backup , dont worry , after restoring every thing the problem wont come back ,

good luck every body
[T-Mobile LG G2x] Ahmed.gogo:
i cant understand this step i do it but not work pls help
[T-Mobile LG G2x] mr2000jp:
just do a factory reset using the factory reset option you find inside the secret menu , not the one you usually use by going into settings >privacy

this will reset every thing , i mean really every thing , and it will go back to normal

you can do a full backup and after finishing the reset do a restore , yes thats right , this will not bring back the problem again
[T-Mobile LG G2x] mr2000jp:
you are most welcome
[Galaxy S II Q&A, Help & Troubleshooting] fr3quency:
Just for WiFi, BT, GPS and Silent/Vibrate/Normal. Also the battery percentage.

For latest CM(based on LPH kernel)

Come on guys! It's amazing. :)
[Galaxy S II Q&A, Help & Troubleshooting] JJEgan:
Amazing but ugly ugly .

jje
[Galaxy S II Q&A, Help & Troubleshooting] Paradoxxx:
Who on the earth need so many toggles?

Envoyé depuis mon GT-I9100 avec Tapatalk
[Galaxy S II Q&A, Help & Troubleshooting] anfearg:
Looks like a MIUI notification bar with an ICS Theme. I'd expect that the Cyanogen team would have to implement it, but to be honest im happy with the option of 5 toggles on CM9.
[Motorola Droid RAZR] DigitallyChallenged:
New day. I ran Dan's exploit again today and got root! Mod, feel free to delete post...
[Motorola Droid RAZR] aceboogie62:
I'm having the same issue this is what i get when trying to root my Droid Razr

Easy rooting toolkit (v2.0)

created by DooMLoRD

Modified by Frasertag

Modified for Linux/Mac by Max Lee at DroidRazrRoot.com

using exploit zergRush (Revolutionary Team)

Credits go to all those involved in making this possible!

---------------------------------------------------------------

[*] This script will:

(1) root ur device using latest zergRush exploit (10 Nov)

(2) install Busybox (1.18.4)

(3) install SU files (binary: 3.0.3 and apk: 3.0.6)

[*] Before u begin:

(1) enable USB DEBUGGING

from (Menu\Settings\Applications\Development)

(2) enable UNKNOWN SOURCES

from (Menu\Settings\Applications)

(3) [OPTIONAL] increase screen timeout to 10 minutes

(4) connect USB cable to PHONE and then connect 2 computer

---------------------------------------------------------------

--- STARTING ----

--- WAITING FOR DEVICE

--- cleaning

rm failed for *, No such file or directory

--- pushing zergRush

3108 KB/s (23056 bytes in 0.007s)

--- correcting permissions

--- executing zergRush

[**] Zerg rush - Android 2.2/2.3 local root

[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x00019118

[*] Scooting ...

[*] Sending 149 zerglings ...

[*] Sending 189 zerglings ...

[-] Hellions with BLUE flames !

--- WAITING FOR DEVICE TO RECONNECT

if it gets stuck over here for a long time then try:

disconnect usb cable and reconnect it

toggle USB DEBUGGING (first disable it then enable it)

--- DEVICE FOUND

--- pushing busybox

2604 KB/s (1075144 bytes in 0.403s)

--- correcting permissions

--- remounting /system

mount: permission denied (are you root?)

--- copying busybox to /system/xbin/

/system/xbin/busybox: cannot open for write: Read-only file system

--- correcting ownership

Unable to chmod /system/xbin/busybox: No such file or directory

--- correcting permissions

Unable to chmod /system/xbin/busybox: No such file or directory

--- installing busybox

/system/xbin/busybox: not found

--- pushing SU binary

failed to copy 'su' to '/system/bin/su': Read-only file system

--- correcting ownership

Unable to chmod /system/bin/su: No such file or directory

--- correcting permissions

Unable to chmod /system/bin/su: No such file or directory

--- correcting symlinks

rm failed for /system/xbin/su, Read-only file system

link failed Read-only file system

--- pushing Superuser app

failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file system

--- cleaning

--- rebooting

--- WAITING FOR DEVICE

3562 KB/s (3104805 bytes in 0.851s)

pkg: /data/local/tmp/recovery.apk

Failure [INSTALL_FAILED_ALREADY_EXISTS]

All Done, run Bionic Recovery from App Draw

Check out DroidRazrRoot.com for more cool hacks!
[Motorola Droid RAZR] WVULTRA:
Matt's Utility!

Guarantee this Utility will get you rooted:

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

;)
[Motorola Droid RAZR] lpoppe22:
same problem no solution

I tried that and everything else and no dice... the problem i have is that i rooted once before and then unrooted to show my brother how it works and not i cannot root anymore... every utility i try says that it cant write an that it is read only or the location doesnt exist... i am so totally lost. can anyone help me?!?!?!?:(:(:(
[Motorola Droid RAZR] jachar:
I'm having the same problem... it fail to copy the files, then the phone restarts but still no root :(
[Motorola Droid RAZR] BakaPhoenix:
http://goo.im/apps/mattlgroff/DroidRazrRoot404.zip

Use this to root, works on ics too
[Motorola Droid RAZR] jachar:
worked like a charm!!! thanks!
[Samsung Captivate Glide] romanr:
Does anybody know, which partition table type is used on the /dev/block/mmcblk0 (sgh-i927) ?

I thought there is GPT, but

~ # dmesg | grep -B1 -e mmcblk0
...
<4>[ 7.293135] Primary GPT is invalid, using alternate GPT.
<6>[ 7.293252] mmcblk0: p1 (䙅S) p2 (偁P) p3 (䅃C) p4 (䵉S) p5 (卍C) p6 (䑕A) p7 (䑍M) p8 (体S) p9 (乌X) p10 (呏A) p11 (䥈D)
...

fdisk does not recognize the partition table

~ # fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 7733 MB, 7733248000 bytes
4 heads, 16 sectors/track, 236000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ # fdisk -l /edevblommcb1
fdisk: can't open '/edevblommcb1': No such file or directory
~ # fdisk -l /dev/block/mmcblk1

Disk /dev/block/mmcblk1: 8166 MB, 8166309888 bytes
255 heads, 63 sectors/track, 992 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 992 7968208+ b Win95 FAT32

ok, no msdos table - no problem, I dumped mmcblk0 to my pc and checked it with parted:

[roma@roma][~/work/android-work/sgh-i927/device]> parted mmcblk0 print
WARNING: You are not superuser. Watch out for permissions.
Warning: Unable to open /home/roma/work/android-work/sgh-i927/device/mmcblk0 read-write (Permission denied).
/home/roma/work/android-work/sgh-i927/device/mmcblk0 has been opened read-only.
Warning: Unable to open /home/roma/work/android-work/sgh-i927/device/mmcblk0 read-write (Permission denied).
/home/roma/work/android-work/sgh-i927/device/mmcblk0 has been opened read-only.
Error: /home/roma/work/android-work/sgh-i927/device/mmcblk0: unrecognised disk label

disassembled:

[roma@roma][~/work/android-work/sgh-i927/device]> ../../../android-sdk-linux_86/tools/adb pull /sbin/recovery ./mmcblk0.elf
2823 KB/s (793872 bytes in 0.274s)
[roma@roma][~/work/android-work/sgh-i927/device]> dd if=mmcblk0 of=mmcblk0.mbr count=1
1+0 records in
1+0 records out
512 bytes (512 B) copied, 5.8074e-05 s, 8.8 MB/s
[roma@roma][~/work/android-work/sgh-i927/device]> arm-eabi-objcopy --add-section mmcblk0=mmcblk0.mbr mmcblk0.elf
BFD: st4OsaEp: warning: sh_link not set for section `.ARM.exidx'
[roma@roma][~/work/android-work/sgh-i927/device]> arm-eabi-objdump -d -j mmcblk0 mmcblk0.elf
BFD: mmcblk0.elf: warning: sh_link not set for section `.ARM.exidx'

mmcblk0.elf: file format elf32-littlearm

Disassembly of section mmcblk0:

00000000 <mmcblk0>:
0:	3d5463d0	ldclcc	3, cr6, [r4, #-832]
4:	7c021fb1	stcvc	15, cr1, [r2], {177}
8:	9d1cfe9b	ldcls	14, cr15, [ip, #-620]
c:	bd8ba89c	stclt	8, cr10, [fp, #624]
10:	a2bfdf46	adcsge	sp, pc, #280	; 0x118
14:	fa289616	blx	0xa25874
18:	ffd97eab	undefined instruction 0xffd97eab
1c:	6b1737f5	blvs	0x5cdff8
20:	14ea3ae2	strbtne	r3, [sl], #2786
24:	545ad41f	ldrbpl	sp, [sl], #-1055
28:	720e0d51	andvc	r0, lr, #5184	; 0x1440
2c:	5cbb5c11	ldcpl	12, cr5, [fp], #68
30:	406ec5b9	strhtmi	ip, [lr], #-89
34:	4514c01f	ldrmi	ip, [r4, #-31]
38:	52aac445	adcpl	ip, sl, #1157627904	; 0x45000000
3c:	f83a0f38	undefined instruction 0xf83a0f38
...

seems garbage to me.

Has anybody else the same "broken" partition table?
[Samsung Captivate Glide] romanr:
fdisk -l /dev/block/mmcblk0

Everybody!

Please, help me in the research.

Post please here your terminal output for these commands:

$ su
# fdisk -l /dev/block/mmcblk0

Thank you!
[Samsung Captivate Glide] gabby131:
my result:

sorry for late response.....I am quite stuck with job hunting :)
[Samsung Captivate Glide] tcfx44:
And my results

$ su
su
# fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 7733 MB, 7733248000 bytes
4 heads, 16 sectors/track, 236000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0 doesn't contain a valid partition table
[Samsung Captivate Glide] Lookin4Trouble:
<-- doesnt have a linux box available, sorry
[Samsung Captivate Glide] romanr:
Thanks everybody!

seems there is no standard msdos partition table on SGH-i927, but how does it work then... will dig it more
[Samsung Captivate Glide] Litatus:
repartition

How can I re partition my Glide?

I think my NAND is corrupted, It does not boot. I can't get into the recovery (vol down + power).

I can get into the Download Mode.

Thanks
[Samsung Captivate Glide] terinfire:
You shouldn't have to do anything crazy. Put it into download mode and get one of the official releases for ICS -- and then run it against your phone -- it should get everything setup for you perfectly. I believe the download is about 660MB, though, just as a heads-up!
[Samsung Captivate Glide] Litatus:
Well, i did that. I used the GB and the ICS roms, but nothing. No boot and no recovery, just the samsung logo or the download mode. I was thinking that my NAND could be corrupted, and since I didn't find the .pit file, I started to try other pits files. I've found one that finish the whole process with odin (the others gave me error). But the pit was for 16GB, and now when i flash the GB rom I get an error at the end of the flashing process, when the modem.bin is been transfered, and with the ICS rom at the beggining of the flashing process, when the fs is transfered. In the first case i get the following error message in the glide's screen: "partition size too small". In the second case i get: "data too large". So if i didn't have partitions problems before, now i got it.
[Samsung Captivate Glide] terinfire:
http://xdaforums.com/showthread.php?t=1831561

Try using that -- that's an all-in-one tool, which should hopefully repartition your tables and the like. Make sure you put your phone into download mode. If not, sounds like you're going to have a lot of pain moving forward.
[Samsung Captivate Glide] Litatus:
not working.. proof...

ok. here are the snapshots. The first two are when I try to flash the stock GB rom. The other two are when I try to flash the stock ICS. The last one is when I try to flash the all-in-one tool...

Nothing... I need to Re-partition my NAND. (I think is the last thing to do before to say it is a hardware issue).

Maybe I could do a JTAG. My friend has the riff box, but he doesn't know the pinout to do the jtag. Does anyone knows?
[Samsung Captivate Glide] romanr:
gdisk

Seems there is GPT, but only the backup copy is used

GPT fdisk (gdisk) version 0.8.4

Unsupported GPT version in backup header; read 0x00000000, should be
0x00010000
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present

Creating new GPT entries.

Command (? for help): p
Disk /dev/block/mmcblk0: 15104000 sectors, 7.2 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 95328BF5-FDA5-45A2-BD5F-CE18C3F102AD
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15103966
Partitions will be aligned on 2048-sector boundaries
Total free space is 15103933 sectors (7.2 GiB)

Number Start (sector) End (sector) Size Code Name

Command (? for help): r
Recovery/transformation command (? for help): c
Warning! This will probably do weird things if you've converted an MBR to
GPT form and haven't yet saved the GPT! Proceed? (Y/N): y
Caution! After loading partitions, the CRC doesn't check out!

Recovery/transformation command (? for help): p
Disk /dev/block/mmcblk0: 15104000 sectors, 7.2 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 95328BF5-FDA5-45A2-BD5F-CE18C3F102AD
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15103966
Partitions will be aligned on 2048-sector boundaries
Total free space is 23485 sectors (11.5 MiB)

Number Start (sector) End (sector) Size Code Name
1 21504 46079 12.0 MiB 0700 ES
2 46080 1274879 600.0 MiB 0700 AP
3 1274880 1913855 312.0 MiB 0700 CC
4 1913856 9779199 3.8 GiB 0700 IS
5 9779200 9783295 2.0 MiB 0700 MC
6 9783296 13977599 2.0 GiB 0700 UA
7 13977600 14010367 16.0 MiB 0700 MM
8 14010368 14020607 5.0 MiB 0700 SS
9 14020608 14036991 8.0 MiB 0700 LX
10 14036992 14053375 8.0 MiB 0700 OA
11 14053376 15101951 512.0 MiB 0700 HD

Recovery/transformation command (? for help): q

Despite checksum error the table seems sane.

I thought if there is GPT, then probably there should be an EFI, but I don't see an EFI system partition, also the first partition is not FAT32 (seems it is even zero-filled) so it does not contain EFI boot loader. Probably the bootloader is written in the first 21503 sectors that are marked as free.

Until we know how the bootloader works changing the partition table is rather dangerous.
[Samsung Captivate Glide] romanr:
partition data

MC - seems like recovery bootloader, or something related (solely out off "boot-recovery" keyword :)

00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000800 62 6f 6f 74 2d 72 65 63 6f 76 65 72 79 00 00 00 |boot-recovery...|
00000810 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000820 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000830 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00100000 ff ff ff ff 01 02 ff ff ff ff ff ff ff ff ff ff |................|
00100010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00100800 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
001ff000 3b 86 7c 39 74 01 00 00 00 00 00 00 ff 00 00 00 |;.|9t...........|
001ff010 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
001ff020 00 00 00 00 00 00 00 00 44 4c 4f 57 00 00 00 00 |........DLOW....|
001ff030 01 00 00 00 d4 fa fb ee 17 f2 c0 e7 e1 8f 8d 6e |...............n|
001ff040 b3 9a 72 08 ab c6 b9 17 26 89 ae 99 57 85 2d 57 |..r.....&...W.-W|
001ff050 74 7f 71 79 9a 9f 49 12 6a 9b 68 0e 22 da 07 13 |t.qy..I.j.h."...|
001ff060 c1 e5 e8 60 73 f5 61 4d 0f 05 b2 11 53 f4 46 8c |...`s.aM....S.F.|
001ff070 02 19 19 3b 71 c1 6f 4d bd ad cb e2 7e 48 c4 28 |...;q.oM....~H.(|
001ff080 d5 a9 4f 7e 85 99 5c c1 a3 2f a1 43 90 bf 1f 30 |..O~..\../.C...0|
001ff090 39 9a 2f a0 61 df e4 41 e0 c8 9c ab d1 f2 ca a9 |9./.a..A........|
001ff0a0 d3 0f 6c 46 02 51 8c 13 89 18 18 4d 04 e9 a3 94 |..lF.Q.....M....|
001ff0b0 55 79 ea 0d fe f7 35 6c 93 e6 d5 2a 7c 1e f6 9f |Uy....5l...*|...|
001ff0c0 b9 53 c6 ab 8a 60 2d 77 81 f6 cd e4 86 18 f2 57 |.S...`-w.......W|
001ff0d0 20 00 9b 61 33 1c 35 3b 64 3a 11 0b cf cb 84 6e | ..a3.5;d:.....n|
001ff0e0 70 7f 6a 20 72 03 63 f0 0c d1 05 79 cd 87 53 d0 |p.j r.c....y..S.|
001ff0f0 e4 78 da 3e 71 95 5a b0 1f 8b 9a 76 69 4f 68 d9 |.x.>q.Z....viOh.|
001ff100 56 cb 56 48 64 2b b2 15 e4 24 29 00 b2 57 9c b0 |V.VHd+...$)..W..|
001ff110 e3 b8 e0 b1 89 b3 c8 a8 d1 9b f9 54 3d c2 e8 57 |...........T=..W|
001ff120 94 ab aa 6d 37 5e 2e b3 98 7b 98 29 af 01 b8 9a |...m7^...{.)....|
001ff130 de 7d 6f 9f cb af 0d 71 cb ce 73 94 f8 46 d0 bf |.}o....q..s..F..|
001ff140 66 12 83 95 b6 3a d4 40 08 25 f3 c2 1e 8e b4 42 |f....:.@.%.....B|
001ff150 bc c8 82 f5 27 e3 40 c2 5a eb 3d 6b 14 19 2d 5f |....'.@.Z.=k..-_|
001ff160 d5 9e 0a a9 19 f0 3d 91 26 34 51 bb 66 a9 97 be |......=.&4Q.f...|
001ff170 ab 06 74 b7 ff ff ff ff ff ff ff ff ff ff ff ff |..t.............|
001ff180 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
001ff800 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00200000

SS - is the system kernel (figured out by initramfs dismantling)

LX - is the recovery kernel

OA - empty partition, zeroed out

MM - really don't know what is it
[Samsung Captivate Glide] romanr:
no way to change the partition table (for now)

Actually there is GPT-like partition table, but it's impossible to modify it because there is a data (or a code) that overlaps with primary GPT header, so modifying the table with bare GPT tools like parted or gdisk will definitelly break something.
[Samsung Captivate Glide] romanr:
my PIT file

Here is my pit file attached. Try to flash recovery, than if it works - try the factoryfs image.
[Samsung Captivate Glide] Litatus:
thanks, but...

wow... thanks!... finally i got a pit file... unfortunately does not work either... :(

I get an error...
[Samsung Captivate Glide] romanr:
Try heimdall, perhaps console one. I think you did put the recovery into the wrong slot.
[Samsung Captivate Glide] romanr:
GB images

Here are my GB images: http://romanr.info/android/sgh-i927-GB-img.zip

These images do not contain EFS and factoryfs, so normal boot will not work.

Use heimdall 1.4, 1.3 may not work.

You may start with repartitioning and flashing only GPT and SOS images.

heimdall flash --repartition --pit sgh-i927-GB.pit --GPT GPT.img --SOS SOS.img

Than reboot and try to enter the recovery (hold volume down key). If the recovery works - you'r fine.

If recovery does not work, then try to flash more images.

heimdall flash --MSC MSC.img
heimdall flash --EBT EBT.img --EB2 EB2.img

Than try to reboot into recovery again.

Flash other images only at last resort.

Flash PT.img at very last resort.
[Samsung Captivate Glide] romanr:
sgh-i927 does not have NAND/emmc, it has bare MMC card internally mounted, all partitions lie on that internal card. Curious, that odin for now does not allow to read/dump the partition, but it is possible to dump all the internal mmc drive and get access to bootloader and other things. The first 2 blocks (block size = 512KiB) are hidden though.

I belive that samsung devices are truly unbreakable. Seems that samsung odin-download mode is booted out of some hidden storage, so repartition or even full wipe of internal SD card does not break the download mode.

Also I noticed that nvflash mode works too (holding volume up + volume down), but it requires some additional files. You may dig into it, it is JTAG-equivalent low-level mode.
[Samsung Captivate Glide] Litatus:
results...

well... i've tried to do what you said... i had the heimdall 1.3, I compiled from source the R.C. 1.4... but I'm getting and error in the pit... check the image please... I did flash the PT.img, and now the glide gets directly to download mode, "reason: no kernel"...

about the nvidia usb recovery boot (pressing vol + & -), my ubuntu detects and make conection, but when I send any comand to the cellphone, I get an error too. Check the third picture.

This is too weird... I'm loosing my mind...
[Samsung Captivate Glide] romanr:
Well, download mode is not the worst thing.

Try then with partition ids:

heimdall flash --repartition --pit sgh-i927-GB.pit --18 GPT.img --14 SOS.img

You may check partition IDs by

heimdall print-pit --file sgh-i927-GB.pit

Also you may download your current pit

heimdall download-pit --output my.pit

Did you hold the "volume down" key while reboot? Probably you weren't fast enough. While you're in the download mode, hold the volume down key, then press the power key until device reboot. You should reach the recovery. Do not release volume down key until you reach the recovery. Try several times if the download mode loaded again.
[Samsung Captivate Glide] terinfire:
For PIT files, you don't want to do recovery mode -- you want to do download mode. That would be volume up + power on.