Database Users

Explaining the i5800 Partitions

Right in brief I have a Samsung i5800 and I have temporary rooted the device and then accessed the adb shell and using the command cat /proc/partitions I have the following:
major minor #blocks name
139 0 513024 tfsr0/c
139 1 256 tfsr1
139 2 1280 tfsr2
139 3 512 tfsr3
139 4 8192 tfsr4
139 5 7680 tfsr5
139 6 225280 tfsr6
139 7 207360 tfsr7
139 8 38912 tfsr8
139 9 7168 tfsr9
139 10 16384 tfsr10
179 0 7761920 mmcblk0
179 1 7757824 mmcblk0p1
137 0 513024 bml0/c
137 1 256 bml1
137 2 1280 bml2
137 3 512 bml3
137 4 8192 bml4
137 5 7680 bml5
137 6 225280 bml6
137 7 207360 bml7
137 8 38912 bml8
137 9 7168 bml9
137 10 16384 bml10
138 4 4352 stl4
138 6 217600 stl6
138 7 200192 stl7
138 8 34816 stl8
So here are my queries I am lead to believe and understand that bml (does it stand for Boot Module or similar?) bml1 is the primary bootloader and bml2 is the secondary now can anyone shed any light on the other areas, I know the mmc areas are the multi media card and stl8 seems to be system or similar with stl6 being media on the device.
Now I am looking for the SMS of the device so I can back this area up and at a later date restore it if required. Which of these areas are the SMS stored in and if anyone knows the contacts and the Call Logs?
Second I was wondering does anyone know what these areas all represent for example tfsr1 - tfsr10 and why the tfsr areas are the same size as the bml1 - bml10 areas?
Kind regards,
Chris

Partition mapping got nothing to do with sms backup
FYI stl6 is system, 7-cache n 8-data
Use SMS Backup and Restore from Market (By Ritesh Sahu)
And he also made another app to backup call logs
For contacts
Sync them to ur google account
or open contacts app,press menu and touch import/export

cdesai said:
Partition mapping got nothing to do with sms backup
FYI stl6 is system, 7-cache n 8-data
Use SMS Backup and Restore from Market (By Ritesh Sahu)
And he also made another app to backup call logs
For contacts
Sync them to ur google account
or open contacts app,press menu and touch import/export
Click to expand...
Click to collapse
Thank you for the swift response. Ok so where on the device are the SMS stored I presume they are stored on the NAND chip, the reason I am asking this is I wish to extract them in raw HEX format rather than just backup using an app. As for the Contacts, Calls etc I am not as worried about these areas just interested but as I say for the SMS I was hoping the find a way to extract the HEX in any format where they are stored.
Edit do we think the mirror image called TFSR could be Temporary File System Root?
Thanks again!

"Fried" eMMC - Unooting?

Hi.
I was trying to flash my ROM to CyanogenMod today, however it didn't go through... my phone went into a bootloop and I tried to restore the backup I made through the RomManager. Now it's giving me the unable to mount /cache/ error.
I still have access to the RomManager and adb, however I was wondering if it was possible to fix my phone or at least turn S ON from OFF. If there is no solution to this issue, I want to try to return the phone to T-Mobile to get a new one, but I don't want to keep S-OFF...
Are there any solutions? Thanks.

http://forum.xda-developers.com/showthread.php?t=1448441
read the whole thread...

hoffmas said:
http://forum.xda-developers.com/showthread.php?t=1448441
read the whole thread...
Click to expand...
Click to collapse
Unfortunately, I tried following what the OP did and it was not working. fdisk kept returning an error stating that it could not read the partitions.

ViaTheStars said:
Unfortunately, I tried following what the OP did and it was not working. fdisk kept returning an error stating that it could not read the partitions.
Click to expand...
Click to collapse
If you pull the SD card, navigate to /dev/block/, and run ls whats the output it gives you? Then if you could put your SD card back in and do the same thing and post that too I might be able to help you do the same thing I did.

CollegeBound1987 said:
If you pull the SD card, navigate to /dev/block/, and run ls whats the output it gives you? Then if you could put your SD card back in and do the same thing and post that too I might be able to help you do the same thing I did.
Click to expand...
Click to collapse
Code:
loop0 loop6 mmcblk0p12 mmcblk0p18 mmcblk0p23 mmcblk0p3 mmcblk0p
9
loop1 loop7 mmcblk0p13 mmcblk0p19 mmcblk0p24 mmcblk0p4 platform
loop2 mmcblk0 mmcblk0p14 mmcblk0p2 mmcblk0p25 mmcblk0p5
loop3 mmcblk0p1 mmcblk0p15 mmcblk0p20 mmcblk0p26 mmcblk0p6
loop4 mmcblk0p10 mmcblk0p16 mmcblk0p21 mmcblk0p27 mmcblk0p7
loop5 mmcblk0p11 mmcblk0p17 mmcblk0p22 mmcblk0p28 mmcblk0p8

ViaTheStars said:
Code:
loop0 loop6 mmcblk0p12 mmcblk0p18 mmcblk0p23 mmcblk0p3 mmcblk0p
9
loop1 loop7 mmcblk0p13 mmcblk0p19 mmcblk0p24 mmcblk0p4 platform
loop2 mmcblk0 mmcblk0p14 mmcblk0p2 mmcblk0p25 mmcblk0p5
loop3 mmcblk0p1 mmcblk0p15 mmcblk0p20 mmcblk0p26 mmcblk0p6
loop4 mmcblk0p10 mmcblk0p16 mmcblk0p21 mmcblk0p27 mmcblk0p7
loop5 mmcblk0p11 mmcblk0p17 mmcblk0p22 mmcblk0p28 mmcblk0p8
Click to expand...
Click to collapse
yea see mine didnt look like that until after i recreated the partition tables
before i did that all i had listed there was
loop0 loop2 loop4 loop6 platform
loop1 loop3 loop5 loop7
If clockworkmod can mount your SD card i would try going to sdb shell and running these three commands
mke2fs /dev/block/mmcblk0p25
mke2fs /dev/block/mmcblk0p26
mke2fs /dev/block/mmcblk0p27
then install a new rom from your SD Card
I figure if the phone is already bricked you have nothing to lose
You may also want to try running 'busybox fdisk -l mmcblk0' in sdb shell putting the results here.

CollegeBound1987 said:
yea see mine didnt look like that until after i recreated the partition tables
before i did that all i had listed there was
loop0 loop2 loop4 loop6 platform
loop1 loop3 loop5 loop7
If clockworkmod can mount your SD card i would try going to sdb shell and running these three commands
mke2fs /dev/block/mmcblk0p25
mke2fs /dev/block/mmcblk0p26
mke2fs /dev/block/mmcblk0p27
then install a new rom from your SD Card
I figure if the phone is already bricked you have nothing to lose
You may also want to try running 'busybox fdisk -l mmcblk0' in sdb shell putting the results here.
Click to expand...
Click to collapse
Code:
/dev/block # fdisk -l mmcblk0
fdisk -l mmcblk0
fdisk: can't open 'mmcblk0': I/O error
/dev/block #

Cwm recovery install ics

Looking for a method that would allow me to install CWM or any other recovery without rooting first. I would really like to have the un-rooted backup image files before rooting. I usually DD but cannot since that requires root privileges. If ANYONE knows of a way, please provide me with some instructions, thank you???
Usually I use these commands in recovery since most of these partitions are not mounted.
su = if I could gain root access and change to read/write, and then:
dd if=/dev/block/mmcblk0p1 of=/sdcard/Download/recovery.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/Download/boot.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/Download/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/Download/flexrom.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/Download/data.img
mmcblk0p1 = recovery
mmcblk0p2 = boot
mmcblk0p3 = system = /system
mmcblk0p4 = cache = /cache
mmcblk0p6 = flexrom = /system/vendor
mmcblk0p8 = data = /data

mikerowes69 said:
Looking for a method that would allow me to install CWM or any other recovery without rooting first. I would really like to have the un-rooted backup image files before rooting. I usually DD but cannot since that requires root privileges. If ANYONE knows of a way, please provide me with some instructions, thank you???
Usually I use these commands in recovery since most of these partitions are not mounted.
su = if I could gain root access and change to read/write, and then:
dd if=/dev/block/mmcblk0p1 of=/sdcard/Download/recovery.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/Download/boot.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/Download/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/Download/flexrom.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/Download/data.img
mmcblk0p1 = recovery
mmcblk0p2 = boot
mmcblk0p3 = system = /system
mmcblk0p4 = cache = /cache
mmcblk0p6 = flexrom = /system/vendor
mmcblk0p8 = data = /data
Click to expand...
Click to collapse
blackthund3r had a post about this a while back - maybe also check out his thread re ics one click root.
i dont know alot about this stuff but i've always wanted to know how to do it-
possibly check out some of the older threads in dev regarding 'its magic' not that you will get a solution but may give you the info you need to find one - dont think you'll find any quick answers though, but i'll be keeping any eye on yr thread

[System, Boot & Recovery Dump][8-27-13] SGH-T599 (4.1.2) JZO54K.T599UVAMB5

I managed to get the system folder. Via http://forum.xda-developers.com/showthread.php?t=1578099
CWM
Instructions and discussion available here
Click to expand...
Click to collapse
CWM Flashable Recovery
Both have been tested by me
Stock Recovery
CWM 6.0.3.6 by Unjustified Dev
Click to expand...
Click to collapse
DOWNLOAD:
System.img (/dev/block/mmcblk0p22)
Boot.img (/dev/block/mmcblk0p20)
Recovery.img (/dev/block/mmcblk0p21)
Modem.img - T599UVAMB5 (/dev/block/mmcblk0p12)
modem.bin (/dev/block/mmcblk0p16)
param.lfs (/dev/block/mmcblk0p19)
Preload.img (/dev/block/mmcblk0p24)
efs.img (/dev/block/mmcblk0p11)
Click to expand...
Click to collapse

Hmmm... can you explain me what is that? Thx

Feyerabend said:
Hmmm... can you explain me what is that? Thx
Click to expand...
Click to collapse
It is for development purposes. It is basically the stock firmware minus the kernel and recovery.

goldfingerfif said:
I uploaded the system tar its almost 1GB I cannot pull the Kernel though.
I managed to get the system folder. Via http://forum.xda-developers.com/showthread.php?t=1578099
If someone can assist with getting the kernel without root I would be forever grateful. If it is unpossible then please let me know as well as I cannot find a root method that works.
Click to expand...
Click to collapse
So, what you basicly need is someone with linux who can make a system.img from this, and add supersu and su binary?
And then someone who makes a factoryreset and flash it in odin I guess..
That person might then be able to extract recovery.img and boot.img. Am I right?

tys0n said:
So, what you basicly need is someone with linux who can make a system.img from this, and add supersu and su binary?
And then someone who makes a factoryreset and flash it in odin I guess..
That person might then be able to extract recovery.img and boot.img. Am I right?
Click to expand...
Click to collapse
You don’t NEED linux, you can use Cygwin with windows, but yes someone can then make system.img or system.tar.md5 with supersu and su.
From there if a root shell is obtained recovery and boot partitions should be able to be extracted from the phone.
Then insecure kernel and custom recovery can be installed.
I’ve done something like this with the T989 but this phone is for someone at my work and so bricking is an issue unlike if it was a personal phone as well there is less motivation to do it if it isn’t mine.

goldfingerfif said:
You don’t NEED linux, you can use Cygwin with windows, but yes someone can then make system.img or system.tar.md5 with supersu and su.
From there if a root shell is obtained recovery and boot partitions should be able to be extracted from the phone.
Then insecure kernel and custom recovery can be installed.
I’ve done something like this with the T989 but this phone is for someone at my work and so bricking is an issue unlike if it was a personal phone as well there is less motivation to do it if it isn’t mine.
Click to expand...
Click to collapse
Somethimg like this I guess? http://forum.xda-developers.com/showthread.php?t=1081239&highlight=odin

tys0n said:
Somethimg like this I guess? http://forum.xda-developers.com/showthread.php?t=1081239&highlight=odin
Click to expand...
Click to collapse
Yes just like that minus the need to unpack it because it is just a tarball so 7zip or whatever should open it fine. I am at work but I believe my home computer has either a linux vm installed or Cygwin with dsixda’s kitchen.
I should be able to manually or through dsixda’s kitchen add supersu and su convert to a odin img and flash.
If it successfully roots so I can at least get a rooted shell so I can dd if=/dev/block/….. of=/sdcard/…img to get a recovery.img and boot.img then carefully cook up a TWRP or CWM recovery to flash then make a “custom” or modified stock rom to flash with insecured kernel.

Anything new on how this is going?

thecasual01 said:
Anything new on how this is going?
Click to expand...
Click to collapse
I added SuperSU.apk and su binary.
Scared to flash it without a known good working factory image. Need to read up on a couple things a little more like triple check I can flash just the system partition without boot, etc.

goldfingerfif said:
I added SuperSU.apk and su binary.
Scared to flash it without a known good working factory image. Need to read up on a couple things a little more like triple check I can flash just the system partition without boot, etc.
Click to expand...
Click to collapse
Excuse me if this may come across as stupid or ignorant, but to my understanding the SGH-T599 seems to be an alternative version of the S3 Mini , I think the main difference is the screen size? That being said, can you not use the current existing kernel, boot.img of the S3 mini? I'm basing this off the fact that I had soft-bricked my phone by attempting to flash CWM Recovery but it didn't work, and I couldn't get myself the stock recovery.img file so in an attempt to revive my phone, I substituted that with the S3 mini's and it worked. Although at first every time i turned on and off the phone it displayed noise (TV Static) but it no longer does so.
I would offer being a test monkey, but this is my only phone and I do not have any other phones that I could use in the scenario it does get bricked.

goldfingerfif said:
I added SuperSU.apk and su binary.
Scared to flash it without a known good working factory image. Need to read up on a couple things a little more like triple check I can flash just the system partition without boot, etc.
Click to expand...
Click to collapse
I think it will be fine to flash system.img only as long as you don't use any pit and repartition. Factory reset first to prevent bootloops.
tamil.soljahz said:
Excuse me if this may come across as stupid or ignorant, but to my understanding the SGH-T599 seems to be an alternative version of the S3 Mini , I think the main difference is the screen size? That being said, can you not use the current existing kernel, boot.img of the S3 mini? I'm basing this off the fact that I had soft-bricked my phone by attempting to flash CWM Recovery but it didn't work, and I couldn't get myself the stock recovery.img file so in an attempt to revive my phone, I substituted that with the S3 mini's and it worked. Although at first every time i turned on and off the phone it displayed noise (TV Static) but it no longer does so.
I would offer being a test monkey, but this is my only phone and I do not have any other phones that I could use in the scenario it does get bricked.
Click to expand...
Click to collapse
Are you saying you used a boot.img from s3 mini?

tamil.soljahz said:
Excuse me if this may come across as stupid or ignorant, but to my understanding the SGH-T599 seems to be an alternative version of the S3 Mini , I think the main difference is the screen size? That being said, can you not use the current existing kernel, boot.img of the S3 mini? I'm basing this off the fact that I had soft-bricked my phone by attempting to flash CWM Recovery but it didn't work, and I couldn't get myself the stock recovery.img file so in an attempt to revive my phone, I substituted that with the S3 mini's and it worked. Although at first every time i turned on and off the phone it displayed noise (TV Static) but it no longer does so.
I would offer being a test monkey, but this is my only phone and I do not have any other phones that I could use in the scenario it does get bricked.
Click to expand...
Click to collapse
What exactly did you use to get it up and running, just the recovery.img, system.img, or boot.img (kernel) you flashed or some combo?
Looks like processor, screen and possibly bluetooth are different
T-599 vs i8190

goldfingerfif said:
What exactly did you use to get it up and running, just the recovery.img, system.img, or boot.img (kernel) you flashed or some combo?
Looks like processor, screen and possibly bluetooth are different
T-599 vs i8190
Click to expand...
Click to collapse
I just flashed the recovery.img, and (incorrectly) came to the assumption that the boot.img and system.img would work on the phone as well. In fact, I realize I can't access recovery. I was asking whether that the S3 mini's boot.img would work on the T599V as well.
Also, according to this link: http://www.sammobile.com/2012/11/24/review-samsung-galaxy-s-iii-mini-gt-i8190-2/
it says the S3 mini uses the U8420 chipset as well, which is why I thought the phones were similar.

tamil.soljahz said:
I just flashed the recovery.img, and (incorrectly) came to the assumption that the boot.img and system.img would work on the phone as well. In fact, I realize I can't access recovery. I was asking whether that the S3 mini's boot.img would work on the T599V as well.
Also, according to this link: http://www.sammobile.com/2012/11/24/review-samsung-galaxy-s-iii-mini-gt-i8190-2/
it says the S3 mini uses the U8420 chipset as well, which is why I thought the phones were similar.
Click to expand...
Click to collapse
The site you linked doesn't mention the SGH-T599 just the GT-8190 and the GT-i9300, did you send the right link?

According to http://www.gsmchoice.com/en/catalogue/samsung/galaxyexhibit/ it's built on same board. ST-Ericsson U8420.
It' same for i8190, some sites say U8500 others say U8420.

The Cydia Impactor root method works on the T599, I just did it to mine. Stays rooted on reboot.

marksalot said:
The Cydia Impactor root method works on the T599, I just did it to mine. Stays rooted on reboot.
Click to expand...
Click to collapse
Cool
So, first guy who "dd" will be hero of the day
If partition layout is the same as i8190 it should look like this.
Code:
GT-I8190 PARTITION LAYOUT
Official Name * Fs * Mount point * Known as * Contents
/efs * ext4 * /dev/block/mmcblk0p11 * Efs folder *Device IMEI,mac address etc
/modemfs * ext4 * /dev/block/mmcblk0p12 * Radio *
/SdCcard * vfat * /dev/block/mmcblk1 /dev/block/mmcblk1p1 * Internal sd * Your stuff
/boot * emmc * /dev/block/mmcblk0p20 * kernel/zimage * Drivers etc
/recovery * emmc * /dev/block/mmcblk0p21 * Recovery partion * ??????
/system * ext4 * /dev/block/mmcblk0p22 * System folder * The operation system
/cache * ext4 * /dev/block/mmcblk0p23 * Cache partition * Update.zips csc,samsung and carriers customizations
/preload * ext4 * /dev/block/mmcblk0p24 * Hidden partition * Media files,apks etc from Samsung/carriers
/.lfs * j4fs * /dev/block/mmcblk0p19 * param.lfs ## * splash screen,charging animation download mode pngs, etc
/data * ext4 * /dev/block/mmcblk0p25 length=-16384 * data folder * Your download apps, current device and use, settings
/temp * ? * /dev/block/mmcblk0p5 * nedded to load *
* * * psccd and CSPSA *
* * * when reset is *
* * * triggered *
* * * *
* * * *
* *
* * * *
I guess boot, recovery, and param is most wanted

Here is the content of /proc/partitions
Code:
major minor #blocks name
7 0 5229 loop0
179 0 3866624 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 737280 mmcblk0p23
179 24 102400 mmcblk0p24
179 25 1535983 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15637504 mmcblk1
179 97 15633408 mmcblk1p1
254 0 5229 dm-0
Here is the output of busybox df -h
I have a 16GB SD Card, apparently Maverick (GPS map app I installed) creates it's own partition.
Code:
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 402.1M 112.0K 401.9M 0% /dev
tmpfs 402.1M 0 402.1M 0% /mnt/asec
tmpfs 402.1M 0 402.1M 0% /mnt/obb
tmpfs 402.1M 0 402.1M 0% /dev/shm
/dev/block/mmcblk0p22
1.2G 965.4M 215.7M 82% /system
/dev/block/mmcblk0p12
15.7M 4.3M 11.4M 28% /modemfs
/dev/block/mmcblk0p23
708.7M 12.0M 696.7M 2% /cache
/dev/block/mmcblk0p11
15.7M 4.5M 11.2M 29% /efs
/dev/block/mmcblk0p24
98.4M 11.6M 86.8M 12% /preload
/dev/block/mmcblk0p25
1.4G 1.3G 173.7M 88% /data
df: /mnt/.lfs: Function not implemented
/dev/fuse 1.3G 1.3G 73.7M 95% /storage/sdcard0
/dev/block/dm-0 5.0M 2.9M 2.1M 57% /mnt/asec/com.codesector.maverick.full-1
/dev/block/vold/179:97
14.9G 10.1G 4.8G 68% /storage/extSdCard

cat /proc/partitions gives me in I8190.
Code:
major minor #blocks name
7 0 16664 loop0
7 1 2111 loop1
7 2 5229 loop2
7 3 2111 loop3
7 4 2111 loop4
7 5 2111 loop5
7 6 2111 loop6
7 7 17703 loop7
179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 860160 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 4945920 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15558144 mmcblk1
179 97 13473792 mmcblk1p1
179 98 2075648 mmcblk1p2
254 0 16663 dm-0
254 1 2110 dm-1
254 2 5229 dm-2
254 3 2110 dm-3
254 4 2110 dm-4
254 5 2110 dm-5
254 6 2110 dm-6
254 7 17703 dm-7
7 8 2111 loop8
254 8 2110 dm-8
7 9 26019 loop9
254 9 26019 dm-9
Looks like it matches pretty well

So, I used the Online Nandroid app, it detects the T599 as "codinatmo" and doesn't have a patch available.
Manually chose the "Samsung Galaxy S III mini GT-l8190" patch and installed.
Was able to back up boot.img and recovery.img, both 16MB.

HELP PLEASE Lg L2 Lost memory 32 go after bad flash 16go kdz

After flashing a 16go kdz in my lg g2 d802 I lost my 32go memory, I followed this tuto http://forum.xda-developers.com/showthread.php?t=2470207&page=3
What I did ; used lg flash tools 2014 to flash 32 go kdz [doesn't solve the problem, just 10.7go] then I rooted my phone with iroot25,check root with root checker, copy files and overwrite by Total Commander to system/bin after making it RW, but when I set permissions to 755 and apply doesn't saved check again and found 602 so I can't use ADB to modify partitions and got permissions denied also I lose my root.
if I reboot phone I lose network
where is the problem??
I really appreciate your help, thank you very much
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
07459cead6cc4ddf device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
/system/bin/sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ $ su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # adb devices
adb devices
List of devices attached
@ANDROID:/ # cd /system
cd /system
@ANDROID:/system # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC 032G96 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 101MB 101MB 524kB DDR
5 117MB 118MB 1049kB aboot
6 118MB 120MB 1049kB rpm
7 134MB 151MB 16.8MB boot
8 151MB 152MB 1049kB tz
9 152MB 152MB 1024B pad
10 168MB 171MB 3146kB modemst1
11 171MB 174MB 3146kB modemst2
12 174MB 174MB 1024B pad1
13 185MB 201MB 16.8MB misc
14 201MB 235MB 33.6MB ext4 persist
15 235MB 252MB 16.8MB recovery
16 252MB 255MB 3146kB fsg
17 268MB 269MB 524kB fsc
18 269MB 269MB 524kB ssd
19 269MB 269MB 1024B pad2
20 269MB 270MB 524kB encrypt
21 285MB 294MB 8389kB ext4 drm
22 294MB 302MB 8389kB ext4 sns
23 302MB 336MB 33.6MB laf
24 336MB 369MB 33.6MB fota
25 369MB 403MB 33.6MB ext4 mpt
26 403MB 403MB 524kB dbibak
27 403MB 404MB 1049kB rpmbak
28 404MB 405MB 1049kB tzbak
29 405MB 405MB 8192B rct
30 419MB 3322MB 2902MB ext4 system
31 3322MB 3959MB 638MB ext4 cache
32 3959MB 4043MB 83.9MB tombstones
33 4043MB 4060MB 16.8MB spare
34 4060MB 4110MB 50.3MB ext4 cust
35 4110MB 15.7GB 11.6GB ext4 userdata
36 15.7GB 15.8GB 37.7MB grow
(parted) quit
quit
quit
@ANDROID:/system # quit
quit
sh: quit: not found
127 @ANDROID:/system # ./dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512
seek=61071327 conv=notrunc
of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: ./dd: not found
127 @ANDROID:/system # dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 se
ek=61071327 conv=notrunc
=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: dd: can't execute: Permission denied
126 @ANDROID:/system # /dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 s
eek=61071327 conv=notrunc
f=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: /dd: not found
127 @ANDROID:/system #
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
/system/bin/sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ $ su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # cd /system
cd /system
@ANDROID:/system # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print

Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.

Goona work hhh
Yoinx said:
Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.
Click to expand...
Click to collapse
Yes very true I learned a lot but this solution works for a lot of users, im just struggling with system/bin permissions, I know something wrong with SU or root or kdz or lg tools 2014, so im looking for the generosity of experts or people who had the same issue, im very sure its gonna work, in the same time, im trying to be familiar with android/Linux, lol, thank you for your reply

Yoinx said:
Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.
Click to expand...
Click to collapse
Everything is possible with Linux, you may learn something new from this thread too, lol

thequietman1979 said:
Everything is possible with Linux, you may learn something new from this thread too, lol
Click to expand...
Click to collapse
Yeah, it's possible.
Tbh... it looks like you're either on the stock rom without busybox installed. Or your permissions are hosed as you suspect.
If you type busybox while in your adb shell, what do you get?

RE
Yoinx said:
Yeah, it's possible.
Tbh... it looks like you're either on the stock rom without busybox installed. Or your permissions are hosed as you suspect.
If you type busybox while in your adb shell, what do you get?
Click to expand...
Click to collapse
Yes right, im in stock coz this solution doesn't work for others roms, rooted and busybox, when I type it in adb it gives me busybox 1.20.0 installed and all the commands and functions but when I make changes in system/bin I lose adb access and lose also root.
thank u man

thequietman1979 said:
Everything is possible with Linux, you may learn something new from this thread too, lol
Click to expand...
Click to collapse
thequietman1979 said:
Yes right, im in stock coz this solution doesn't work for others roms, rooted and busybox, when I type it in adb it gives me busybox 1.20.0 installed and all the commands and functions but when I make changes in system/bin I lose adb access and lose also root.
thank u man
Click to expand...
Click to collapse
make sure that you're allowing root access for adb in your phone's developer options and/or the security settings for your phone.
restart adb as root: adb root
remount your system as r/w: adb remount
see if that makes a difference.

Solved
Yoinx said:
make sure that you're allowing root access for adb in your phone's developer options and/or the security settings for your phone.
restart adb as root: adb root
remount your system as r/w: adb remount
see if that makes a difference.
Click to expand...
Click to collapse
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here

thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
Yes Thanks for mentioning that : su in folder xbin and not system/bin
kindly try with this last 2 commands
2.
adb shell
su
cd /system
./dd if=/system/xbin/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/xbin/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc

where can i find the files to download?

http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/

Hello! Please help!!! I try to paste the last two lines
./dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
and when press enter it says : sh: ./dd: not found
I also try and these :
./dd if=/system/xbin/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/xbin/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
but with the same results!!

Which link process is the final? And where is a link with the finally sdparted-recovery-all-files?
Which firmware can i use before process? 4.2.2 or 4.4.2?
Which root i can use? With SuperSU or Superuser?
Which programe to use? Total commander or Root explorer??
PLease help me!

if i flash the correct kdz without doing anything else does it fix the problem ??

Please explain
thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
How you root your phon, thats my biggest problem

Ebaharloo said:
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
How you root your phon, thats my biggest problem
Click to expand...
Click to collapse
You need to root it before following the tutorial to get back 32go
http://forum.xda-developers.com/showthread.php?t=2470207&goto=newpost
To root your phone use iroot

Ebaharloo said:
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
How you root your phon, thats my biggest problem
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2448887

thequietman1979 said:
http://forum.xda-developers.com/showthread.php?t=2448887
Click to expand...
Click to collapse
I tired many methods, iroot, towelroot,... But no result.
After flashing my g2 to stock lollipop i lost root and recovery also 32 gb phon become 10gb.
So i tried many method to root and try methods which is available to solve 10gb problem but all if them need root.
You wrote you had same problem.please help me

Ebaharloo said:
I tired many methods, iroot, towelroot,... But no result.
After flashing my g2 to stock lollipop i lost root and recovery also 32 gb phon become 10gb.
So i tried many method to root and try methods which is available to solve 10gb problem but all if them need root.
You wrote you had same problem.please help me
Click to expand...
Click to collapse
What s the model of your lg g2?
If its d802 try to flash it back to kitkat using lg flash tool 2014 than root it using iroot or iroot 10, than follow the tuto, u gonna restore your memory
Root lg g2 d802 : http://forum.xda-developers.com/lg-...ols-how-to-install-twrp-bump-d80230a-t3072186.
Manual method: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772