Database Info

[Material]S-off/on Partition Dumps

since the s-off thread is so long with all the discussion going on...
I like to create a new thread for all the materials related to s-off.
There is my partition dumps from my s-off htc evita (htc one xl / att/rogers ht one x)
mmcblk0p from 1 -38 excluding
33 system
22 recovery
34 cache
35 userdata
36 fat
https://www.dropbox.com/sh/tmpa7i7ibjy0ciy/lnAD6aSvBS
include:
s-off partitions from niceppl
"this is dumped from a supercid, 1.85 and cleanrom 2.1 s-off phone just fyi."
s-on partitions from dharani1234
"here are the partitions from an unlocked bootloader ,rooted RUU - 1.85 with superCID."
I have to replaced my imei sn and mb for the s-off partitions dumps.
with
000000000000000
999999999999
8888888888888
in 4-6 partitions...so if you see those, you know what they are...

Heres a mirror:
http://goo.im/devs/rohan/evita/soff
(feel free to update the OP with this link since this won't run out of bandwidth)

niceppl said:
since the s-off thread is so long with all the discussion going on...
I like to create a new thread for all the materials related to s-off.
There is my partition dumps from my s-off htc evita (htc one xl / att/rogers ht one x)
mmcblk0p from 1 -38 excluding
33 system
22 recovery
34 cache
35 userdata
36 fat
https://www.dropbox.com/sh/tmpa7i7ibjy0ciy/lnAD6aSvBS
include:
s-off partitions from niceppl
"this is dumped from a supercid, 1.85 and cleanrom 2.1 s-off phone just fyi."
s-on partitions from dharani1234
"here are the partitions from an unlocked bootloader ,rooted RUU - 1.85 with superCID."
I have to replaced my imei sn and mb for the s-off partitions dumps.
with
000000000000000
999999999999
8888888888888
in 4-6 partitions...so if you see those, you know what they are...
Click to expand...
Click to collapse
EDIT - I see these are from the 1.85 RUU, I need 1.73...

I'm gonna repost this here in the hopes that those checking this thread might actually care to share their thoughts...
JeepFreak said:
I'm trying to mount dd images of the partitions in /dev/block on my Linux box, but mount can't figure out the filesystem types used. I found some of them by running the "mount" command with no parameters on on the phone, but there are still a bunch of partitions that I can't identify (list below). I've tried ext4, vfat, sysfs, tmpfs, debugfs, and others with no luck. What else might they be?
Strangely, when I try to mount with sysfs, tmpfs, and debugfs it shows me files that aren't actually on the partition.
Anyway, the non-bolded ones below are the ones I'm still trying to mount:
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p34
mmcblk0p35
mmcblk0p36
mmcblk0p37
mmcblk0p38
Any insight is appreciated! I've been searching and guessing/checking for hours!
Click to expand...
Click to collapse
Thanks,
Billy

32 Gb PIT file

I am in need of the PIT file for a SCH-I535 32Gb version.
Anyone willing/able to rip one for me? My 32Gb phone got JTAG'd back to life but using files from a 16Gb version, so it's kinda confused as to how much internal storage it has. I'm hoping I can flash the PIT from a 32Gb phone, then do a reinstall of the ROM and it'll recognize all of my available storage....
Thanks for your help!
-Andy
EDIT:
Problem solved: See post#57

Bump
Sent from my SCH-I535 using xda app-developers app

letinsh said:
I am in need of the PIT file for a SCH-I535 32Gb version.
Anyone willing/able to rip one for me? My 32Gb phone got JTAG'd back to life but using files from a 16Gb version, so it's kinda confused as to how much internal storage it has. I'm hoping I can flash the PIT from a 32Gb phone, then do a reinstall of the ROM and it'll recognize all of my available storage....
Thanks for your help!
-Andy
Click to expand...
Click to collapse
do you have a pit from the 16 gb version

man that would be great if somebody would post a pitfile for both versions...I know that would help a few folks that corrupted thier emmc internal memory and get the "e cant mount" errors in recovery.

I am game ... how would I extract the PIT file?
Sent from my SCH-I535 using xda premium

Standby. Getting confirmation, then I'll post instructions.
Sent from my SCH-I535 using xda app-developers app

bump...

il gladly dump my 32gb blue if there's instructions.

here is some info from the i9300 forum
http://forum.xda-developers.com/showthread.php?t=1742668

What I'm trying to get confirmation on is using darkyy's dd command from the first post in this thread:
http://forum.xda-developers.com/showthread.php?t=960946
Just trying to verify that's the correct place to get it for the SGS3 and that that would produce a flashable .pit file.
Sent from my SCH-I535 using xda app-developers app

please post as soon as you get the ok because i think then we would also be able to use heimdall but i might be wrong.

Bump
Sent from my SCH-I535 using xda premium

aight, darkyy's method won't work as /dev/mount/bml2 (or any of the bml's) doesn't exist on the GS3. I think I posted without knowing enough info.
I don't know where the PIT file's located on the GS3, and whether it's a function of the phone or the OS (ie ICS vs Gingerbread). I didn't have time over the weekend to look into it, too much. Going to look on that i9300 thread posted and also try to learn a little about Heimdall, as I've only ever used Odin.
To sum up:
Goal is to have a .pit file for SCH-I535 for both the 16Gb and 32Gb versions.
Needed:
I don't know enough about Android/SGS3 to know where the .pit is located. Once that's determined, we'll figure out how to extract it and make a functional flash.
Sorry for the false start, still learning here.

letinsh said:
aight, darkyy's method won't work as /dev/mount/bml2 (or any of the bml's) doesn't exist on the GS3. I think I posted without knowing enough info.
I don't know where the PIT file's located on the GS3, and whether it's a function of the phone or the OS (ie ICS vs Gingerbread). I didn't have time over the weekend to look into it, too much. Going to look on that i9300 thread posted and also try to learn a little about Heimdall, as I've only ever used Odin.
To sum up:
Goal is to have a .pit file for SCH-I535 for both the 16Gb and 32Gb versions.
Needed:
I don't know enough about Android/SGS3 to know where the .pit is located. Once that's determined, we'll figure out how to extract it and make a functional flash.
Sorry for the false start, still learning here.[/QUOTE\]
Maybe try the code won't work is you have to use with yaffs2 in the middle or somewhere, i know that the phone runs off of that but that's pretty much all i say since i don't know much.
Click to expand...
Click to collapse

joka10 said:
Maybe try the code won't work is you have to use with yaffs2 in the middle or somewhere, i know that the phone runs off of that but that's pretty much all i say since i don't know much.
Click to expand...
Click to collapse
What I was saying is that /dev/block/bml2 doesn't exist in our file structure on this phone.
Code:
C:\Users\my_computer>adb shell
~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 mmcblk0boot0 mmcblk0p16 mmcblk0p3 platform ram2
loop1 mmcblk0boot1 mmcblk0p17 mmcblk0p4 ram0 ram3
loop2 mmcblk0p1 mmcblk0p18 mmcblk0p5 ram1 ram4
loop3 mmcblk0p10 mmcblk0p19 mmcblk0p6 ram10 ram5
loop4 mmcblk0p11 mmcblk0p2 mmcblk0p7 ram11 ram6
loop5 mmcblk0p12 mmcblk0p20 mmcblk0p8 ram12 ram7
loop6 mmcblk0p13 mmcblk0p21 mmcblk0p9 ram13 ram8
loop7 mmcblk0p14 mmcblk0p22 mmcblk1 ram14 ram9
mmcblk0 mmcblk0p15 mmcblk0p23 mmcblk1p1 ram15
/dev/block #
As you can see, no bml's of any kind.
I don't know if that's because darkyy was messing with a GB version of Android, or because the phone (Samsung) has put the PIT file in a different location. I've got a PM out to Odia from that I9300 thread and he should have some helpful info as to where it's stored and how to get it.
Stay tuned.

letinsh said:
What I was saying is that /dev/block/bml2 doesn't exist in our file structure on this phone.
Code:
C:\Users\my_computer>adb shell
~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 mmcblk0boot0 mmcblk0p16 mmcblk0p3 platform ram2
loop1 mmcblk0boot1 mmcblk0p17 mmcblk0p4 ram0 ram3
loop2 mmcblk0p1 mmcblk0p18 mmcblk0p5 ram1 ram4
loop3 mmcblk0p10 mmcblk0p19 mmcblk0p6 ram10 ram5
loop4 mmcblk0p11 mmcblk0p2 mmcblk0p7 ram11 ram6
loop5 mmcblk0p12 mmcblk0p20 mmcblk0p8 ram12 ram7
loop6 mmcblk0p13 mmcblk0p21 mmcblk0p9 ram13 ram8
loop7 mmcblk0p14 mmcblk0p22 mmcblk1 ram14 ram9
mmcblk0 mmcblk0p15 mmcblk0p23 mmcblk1p1 ram15
/dev/block #
As you can see, no bml's of any kind.
I don't know if that's because darkyy was messing with a GB version of Android, or because the phone (Samsung) has put the PIT file in a different location. I've got a PM out to Odia from that I9300 thread and he should have some helpful info as to where it's stored and how to get it.
Stay tuned.
Click to expand...
Click to collapse
Yea your right it's because he's using a exynos processor instead of the one we have, have you tried replacing the command with those listed above. I know from the odin thread it can't be mmcblk0p1, mmcblk0p15, mmcblk0p18,mmcblk0p14, mmcblk0p12, mmcblk0p13, mmcblk0p17, nor mmcblk0p7.

joka10 said:
Yea your right it's because he's using a exynos processor instead of the one we have, have you tried replacing the command with those listed above. I know from the odin thread it can't be mmcblk0p1, mmcblk0p15, mmcblk0p18,mmcblk0p14, mmcblk0p12, mmcblk0p13, mmcblk0p17, nor mmcblk0p7.
Click to expand...
Click to collapse
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?

letinsh said:
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?
Click to expand...
Click to collapse
Heimdall has never been able to recognize my phone...and I was looking somewhere and the developer said it wasn't working and to try 1.3.1 which was not successful either. I had to borrow a computer to use Odin...I know this isn't a solution for getting heimdall to work but I personally don't think it will...if you do get it to work the steps you took would be appreciated
Sent from my SCH-I535 using xda premium

letinsh said:
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?
Click to expand...
Click to collapse
We can use either or I thin for odin you flash using repartition checked and placing it in the pda field but it will allow us to flash with heimdall using that pit since it can't find the one on the phone. Lastly internal flash /dev/block/mmcblk0 becomes /dev/block/mmcblk1 is what i have found so it looks like either im wrong or it has to be one of the 24 blocks.

Can someone with a working 32 run this in a Terminal? It should pull the PIT from your phone and place it in the SD card. I'm sure those with a 16gb would love to have their PIT file as well.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/pit.bin bs=4096 count=1 skip=4
Info from HERE (International device, but the blocks should be the same)

[Q] 64gb tf700 partitions show up as tmpfs

Hey all, i accidentally formatted the partitions on the tf700. it was unlocked/rooted and i have TWRP installed.
i do not have access to fastboot. i can use adb and adb shell.
i have tried the options 1a & 1b for the prime tf201 unbrick with no luck.
in the terminal if i write the command "df" it shows that the only partition i have is TMPFS, and it is 499732 1K blocks - mounted on /dev
since the card is showing up as TMPFS it is basically a ramdisk and it will be erased on a reboot, so no matter what changes i make, or rom i install it will always be erased.
if i try to mount the /data /system /cache partitions they all return E:Unable to mount '/system' (tw_mount)
( '/system' changes with '/data' and '/cache')
if i go to /dev/block the only things i see are loop0 - loop7 and mmcblk0p3
im thinking that all i need to do is somehow format the internal memory to reinstall a rom and i should be good to go, but i dont know what the partitions need to be, but i could also be way off.
im hoping someone has some insight. i would hate to have a brick

pbcustom98 said:
Hey all, i accidentally formatted the partitions on the tf700. it was unlocked/rooted and i have TWRP installed.
Click to expand...
Click to collapse
How did you do that?
pbcustom98 said:
if i go to /dev/block the only things i see are loop0 - loop7 and mmcblk0p3
Click to expand...
Click to collapse
Looks like your GPT got damaged - this may not be easy to repair (AFAIK the original GPT is nowhere in the Asus firmware download), but as long as you can boot TWRP and use adb, there is hope.
First of all, what does "cat /proc/partitions" say? For comparison, here is my output:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 62087168 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 59976192 mmcblk0p8
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1

_that said:
How did you do that?
Looks like your GPT got damaged - this may not be easy to repair (AFAIK the original GPT is nowhere in the Asus firmware download), but as long as you can boot TWRP and use adb, there is hope.
First of all, what does "cat /proc/partitions" say? For comparison, here is my output:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 62087168 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 59976192 mmcblk0p8
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
Click to expand...
Click to collapse
out of stupidity
cat /proc/partitions shows the following:
# cat /proc/partitions
major minor #blocks name
under it though, there is nothing there

pbcustom98 said:
out of stupidity
Click to expand...
Click to collapse
If you can describe what you did, maybe it is easier to find out what exactly happened.
I assume you don't have an nvflash backup, right?
pbcustom98 said:
under it though, there is nothing there
Click to expand...
Click to collapse
OK. What is the output if you run:
Code:
dmesg|grep mmcblk0
?

_that said:
If you can describe what you did, maybe it is easier to find out what exactly happened.
I assume you don't have an nvflash backup, right?
OK. What is the output if you run:
Code:
dmesg|grep mmcblk0
?
Click to expand...
Click to collapse
I was unlocking the tablet, installing TWRP and then wiping the data, i misread the options and went too far by doing the format data option.
no backup. i do not have access to fastboot/APX now, and i did not create one before.
C:\Users\Daniel>adb shell
~ # ←[6ndmesg|grep mmcblk0
dmesg|grep mmcblk0
~ # ←[6n^C
C:\Users\Daniel>
also, the only way i have seen to get the other mmcblk0 partitions to show up (0p3, 0p4 etc) is to run the commands for the tf201 unbrick (option 1a/b)
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
i was thinking that all i needed to do was to somehow format the data so the tablet can write to the partition instead of it just acting as a ramdisk. i even tried running fdisk -H 1 /dev/block/mmcblk0 and tried to format the data but i'm not familiar with the partition table of this tablet to redo it.
i have also tried doing those commands above and then running a live usb gparted disk to see if it shows up, but it hasnt worked yet

pbcustom98 said:
C:\Users\Daniel>adb shell
~ # ←[6ndmesg|grep mmcblk0
dmesg|grep mmcblk0
~ # ←[6n^C
C:\Users\Daniel>
Click to expand...
Click to collapse
Strange, it should at least output the line about detecting the card. Please reboot your tablet into recovery (to restart the kernel log), then do from your computer
Code:
adb shell dmesg > dmesg.txt
and put the resulting file on pastebin or attach it here.

pbcustom98 said:
I was unlocking the tablet, installing TWRP and then wiping the data, i misread the options and went too far by doing the format data option.
no backup. i do not have access to fastboot/APX now, and i did not create one before.
C:\Users\Daniel>adb shell
~ # ←[6ndmesg|grep mmcblk0
dmesg|grep mmcblk0
~ # ←[6n^C
C:\Users\Daniel>
also, the only way i have seen to get the other mmcblk0 partitions to show up (0p3, 0p4 etc) is to run the commands for the tf201 unbrick (option 1a/b)
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
i was thinking that all i needed to do was to somehow format the data so the tablet can write to the partition instead of it just acting as a ramdisk. i even tried running fdisk -H 1 /dev/block/mmcblk0 and tried to format the data but i'm not familiar with the partition table of this talet to redo it.
i have also tried doing those commands above and then running a live usb gparted disk to see if it shows up, but it hasnt worked yet
Click to expand...
Click to collapse
That's odd, format data will not and shouldn't do that. I did this all the time. Do you have the lastest TWRP and was on JB? if you do, go back to "WIPE" option and do the wipe format again. This should reformat with ext4. After that do factory reset, wipe system, internal storage then try to reflash Cleanrom. TWRP may some how corrupted your partition, but not what you did.

_that said:
Strange, it should at least output the line about detecting the card. Please reboot your tablet into recovery (to restart the kernel log), then do from your computer
Code:
adb shell dmesg > dmesg.txt
and put the resulting file on pastebin or attach it here.
Click to expand...
Click to collapse
i cannot post outside links until about 10 posts.
Here is the pastebin attachedView attachment dmesg.txt

pbcustom98 said:
also, the only way i have seen to get the other mmcblk0 partitions to show up (0p3, 0p4 etc) is to run the commands for the tf201 unbrick (option 1a/b)
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
Click to expand...
Click to collapse
If the partitions are not already there, then these commands simply create files that are named like the block devices that are missing. Not what you want at all, but harmless.
pbcustom98 said:
i was thinking that all i needed to do was to somehow format the data so the tablet can write to the partition instead of it just acting as a ramdisk. i even tried running fdisk -H 1 /dev/block/mmcblk0 and tried to format the data but i'm not familiar with the partition table of this tablet to redo it.
Click to expand...
Click to collapse
Do not try to to use fdisk, it does not support GPT.
pbcustom98 said:
i have also tried doing those commands above and then running a live usb gparted disk to see if it shows up, but it hasnt worked yet
Click to expand...
Click to collapse
How would you run a live disk on the tablet?
---------- Post added at 05:53 PM ---------- Previous post was at 05:46 PM ----------
pbcustom98 said:
i cannot post outside links until about 10 posts.
Here is the pastebin attachedView attachment 1456337
Click to expand...
Click to collapse
The important part is here:
Code:
<6>[ 9.067211] [mmc]:mmc_read_ext_csd:259 ext_csd.sectors 0x766c000 prod_name HYNIX BOOT_SIZE_MULTI 0x20
<4>[ 9.109988] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 9.116163] mmc0: error -110 whilst initialising MMC card
The recovery kernel cannot initialize the MMC card. So there is no point in trying to run partitioning tools at this time, first you need to gain access to the eMMC. It cannot be completely broken, otherwise it could not boot the recovery.
Next step: find out what error -110 is and how to fix it.
btw, this thread seems to describe the same situation (read the post from MysticMgcn): http://forum.xda-developers.com/showthread.php?t=1917304

_that said:
If the partitions are not already there, then these commands simply create files that are named like the block devices that are missing. Not what you want at all, but harmless.
Do not try to to use fdisk, it does not support GPT.
How would you run a live disk on the tablet?
Click to expand...
Click to collapse
i ran gparted live usb on my laptop and tried connecting the tablet via usb after i had the partitions created.

pbcustom98 said:
i ran gparted live usb on my laptop and tried connecting the tablet via usb after i had the partitions created.
Click to expand...
Click to collapse
I still don't understand - where did you create those partitions? On your laptop?
Anyway, your TF700 is bricked until someone finds out how to make the TWRP kernel initialize the eMMC correctly in your situation. Without that, your internal storage is inaccessible, so any fix attempt at that level will fail.
Unfortunately there is still very little public information how the bootloader interacts with the kernels, so I cannot help you further. You may try asking in the thread I linked in my last post if anyone was able to recover from this.

_that said:
I still don't understand - where did you create those partitions? On your laptop?
Anyway, your TF700 is bricked until someone finds out how to make the TWRP kernel initialize the eMMC correctly in your situation. Without that, your internal storage is inaccessible, so any fix attempt at that level will fail.
Unfortunately there is still very little public information how the bootloader interacts with the kernels, so I cannot help you further. You may try asking in the thread I linked in my last post if anyone was able to recover from this.
Click to expand...
Click to collapse
i ran these two commands via adb shell:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
then once i saw them in /dev/block, i rebooted my laptop into gparted hoping that they would show up as a partition i can make changes to, but they didnt.
i will ask in the thread you linked, and thanks for all your help.

[Q] How to Nandroid my Samsung galaxy Core i8260

Hello
I want to make an image Back-up of my Core and I cannot find something!
I tried the search but I couldn't.
I tried also the rom manager but it does not support my Core.
I want to make this image back up so I can go back if i install an other ROM.
How can I do this?
I hope you can help me!!
(I have already succesfully rooted my phone)
Thank you for your time and help!

trelozakinthinos said:
Hello
I want to make an image Back-up of my Core and I cannot find something!
I tried the search but I couldn't.
I tried also the rom manager but it does not support my Core.
I want to make this image back up so I can go back if i install an other ROM.
How can I do this?
I hope you can help me!!
(I have already succesfully rooted my phone)
Thank you for your time and help!
Click to expand...
Click to collapse
Try this. https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup PM me if u have any problems.
Smack that Thanks button if I helped!
KitKat came in on my OmniROM, running on my Note 2.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA

Irwenzhao said:
Try this. nandroid PM me if u have any problems.
Smack that Thanks button if I helped!
KitKat came in on my OmniROM, running on my Note 2.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
Click to expand...
Click to collapse
Thank you for your reply... I have used already this app and I have some questions...
a) When it asks me for select device it says
"Your device code is arubaslimss. Please select the path that corresponds to your device!
If device is nit in list please click the Get Identified button"
So my phone is not on the list and I clicked the get identified button and it sends an email
Code:
Android version: REL 4.1.2
onandroid script version: 9.2
Device: arubaslimss samsung samsung GT-I8260
Contents of: /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 20 mmcblk0p1
179 2 175 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 1000 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 12288 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 12288 mmcblk0p16
179 17 24576 mmcblk0p17
179 18 4096 mmcblk0p18
179 19 512 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 1331200 mmcblk0p21
179 22 737280 mmcblk0p22
179 23 327680 mmcblk0p23
179 24 5115488 mmcblk0p24
179 32 3870720 mmcblk1
179 33 3869696 mmcblk1p1
I din't get any response yet...
b) Without identifying my phone I pressed the backup and it did a 2GB backup.
Although I don't know how to check if this works. I mean I can't my phone restore this backup. Any help?

trelozakinthinos said:
Thank you for your reply... I have used already this app and I have some questions...
a) When it asks me for select device it says
"Your device code is arubaslimss. Please select the path that corresponds to your device!
If device is nit in list please click the Get Identified button"
So my phone is not on the list and I clicked the get identified button and it sends an email
Code:
Android version: REL 4.1.2
onandroid script version: 9.2
Device: arubaslimss samsung samsung GT-I8260
Contents of: /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 20 mmcblk0p1
179 2 175 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 1000 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 12288 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 12288 mmcblk0p16
179 17 24576 mmcblk0p17
179 18 4096 mmcblk0p18
179 19 512 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 1331200 mmcblk0p21
179 22 737280 mmcblk0p22
179 23 327680 mmcblk0p23
179 24 5115488 mmcblk0p24
179 32 3870720 mmcblk1
179 33 3869696 mmcblk1p1
I din't get any response yet...
b) Without identifying my phone I pressed the backup and it did a 2GB backup.
Although I don't know how to check if this works. I mean I can't my phone restore this backup. Any help?
Click to expand...
Click to collapse
Guess the phone's not supported yet then. But if u already made a backup, backup all your apps using helium (backup to sd) and try restoring using the backup u have. (wipe data first)
Smack that Thanks button if I helped!
KitKat came in on my OmniROM, running on my Note 2.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA

trelozakinthinos said:
Hello
I want to make an image Back-up of my Core and I cannot find something!
I tried the search but I couldn't.
I tried also the rom manager but it does not support my Core.
I want to make this image back up so I can go back if i install an other ROM.
How can I do this?
I hope you can help me!!
(I have already succesfully rooted my phone)
Thank you for your time and help!
Click to expand...
Click to collapse
Use CWM to backup the phone. It's way easier. Preferably backup to external sd card

sawan.aware.1 said:
Use CWM to backup the phone. It's way easier. Preferably backup to external sd card
Click to expand...
Click to collapse
CWM does not work with my phone! Not in the list! That's why I was searching for nandroid!

trelozakinthinos said:
CWM does not work with my phone! Not in the list! That's why I was searching for nandroid!
Click to expand...
Click to collapse
Dude follow guide in forum of galaxy core. Cwm is ported for galaxy core amd I am using cwm. It's yet not available in list.

sawan.aware.1 said:
Dude follow guide in forum of galaxy core. Cwm is ported for galaxy core amd I am using cwm. It's yet not available in list.
Click to expand...
Click to collapse
Sorry my friend but I do not understant this. What it means ported?
I downloaded but when i try to find my phone on the list i can't! so I can't use it. Right?
Where exavtly in the galaxy core forum? Give me a link please!
Thank you

trelozakinthinos said:
Sorry my friend but I do not understant this. What it means ported?
I downloaded but when i try to find my phone on the list i can't! so I can't use it. Right?
Where exavtly in the galaxy core forum? Give me a link please!
Thank you
Click to expand...
Click to collapse
Here is the link where you can find cwm for galaxy core and its working. The issues are also discussed.
http://forum.xda-developers.com/showthread.php?t=2517850

1) Remove SD card
2) Boot into CWM Recovery by pressing Power + Volume Up + Home button.
3) Choose "Backup and Restore" and then choose "Backup".
Wait for few minutes and you will get your Nandroid backup in phone's internal memory.
NOTE : You should have enough memory(around 1.8GB - it was in my case) and yup i have got BLACK screen when i did it without removing SD card so i have said remove SD card in the very first step.

I have succesfully backed up my phone's ROM without removing the SD CARD, many times. I haven't got any error's afterall.
Personally, I don't recommend backing up to the internal memory, because it's the /data partition, wich oftenly gets wiped (or you wipe it yourself) when flashing a new ROM.
Just some thought.

MirXas said:
I have succesfully backed up my phone's ROM without removing the SD CARD, many times. I haven't got any error's afterall.
Personally, I don't recommend backing up to the internal memory, because it's the /data partition, wich oftenly gets wiped (or you wipe it yourself) when flashing a new ROM.
Just some thought.
Click to expand...
Click to collapse
You are right friend but i just told him how to take nandroid backup and that is just a matter of common sense that anyone will transfer the backup either to PC or external SD card.

How big is nandroid backup for Core? (Stock rom)

friendfriend said:
How big is nandroid backup for Core? (Stock rom)
Click to expand...
Click to collapse
Depends on what you have. Mine was over 2GB

1 gb
Sent from my GT-I8260 using XDA Premium 4 mobile app

Depends on how much tada you have in your /data and /system partitions, 'cause all of that is backed up. Mine was from 1 to about 1,5 GB.
Sent from my Lenovo A3000-H using xda app-developers app

mine was 1.8 gb on stock odexed rom
Sent from my GT-I8262 using XDA Premium 4 mobile app

Mine iz 1.7gb.

[Q] BigPart partitioning or formatting issue?

Hi, I finally made the jump to BigPart on my MZ604 Wingray and started off with CM10.1 with the BigPart boot partition. Everything went perfectly and for days I had no problems whatsoever UNTIL I had used up 10GB of my initial 27.7GB free Internal storage with 17.7GB showing as remaining. At this point I can no longer install any apps or updates to existing ones as I get a "not enough storage" error. Also using any file manager, if I try to copy anything to the internal storage it shows that it copied successfully but only the folder names actually copy over, all file content is missing? If I delete some things to achieve more than 17.7GB free I can successfully copy, install, update again until I reach 17.7GB free again!
Everything actually works perfectly except I only seem to have 10GB available instead of the full 27.7GB, indicated in Settings>Storage and any other app I try, after a clean BigPart repartition and format. If I run cat /proc/partitions I get;
179 0 7761920 mmcblk0
179 1 7760896 mmcblk0p1
179 8 31162368 mmcblk1
179 9 3072 mmcblk1p1
179 10 2048 mmcblk1p2
179 11 2048 mmcblk1p3
179 12 4096 mmcblk1p4
179 13 2048 mmcblk1p5
179 14 12288 mmcblk1p6
179 15 8192 mmcblk1p7
259 0 1048576 mmcblk1p8
259 1 524288 mmcblk1p9
259 2 29525504 mmcblk1p10
To me this looks fine but I am no expert. Could anyone shed any light as to why I can only seem to use 10GB of my 27.7GB remaining internal storage? This has now occurred twice in a row after wiping and repartitioning again using the TWRP BigPart recovery and going for my 3rd attempt now as I really would like to be able to use ALL of my internal storage for music etc. as I use my Xoom as my car music player, sat nav, reversing camera display, etc...etc...

OK after deleting, repartitioning, and reformatting the 3rd time it all seems good as I have now been able to use more than 10GB.
I have no idea how or why this occurred but I'm glad it's fixed now.