Related
I have Samsung S 3 mini.
I did something really bad to my INTERNAL SD CARD partition layout, so now I have
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 3866624 mmcblk1
179 97 3862528 mmcblk1p1
Code:
~ # ls -la /dev/block/mmcblk*
brw------- 1 root root 179, 0 Jan 1 10:30 /dev/block/mmcblk0
brw------- 1 root root 179, 32 Jan 1 09:28 /dev/block/mmcblk0boot0
brw------- 1 root root 179, 64 Jan 1 09:28 /dev/block/mmcblk0boot1
-rw-rw-rw- 1 root root 16777216 Jan 1 10:07 /dev/block/mmcblk0p20
-rw-r--r-- 1 root root 0 Jan 1 10:07 /dev/block/mmcblk0p22
brw------- 1 root root 179, 96 Jan 1 09:28 /dev/block/mmcblk1
brw------- 1 root root 179, 97 Jan 1 09:28 /dev/block/mmcblk1p1
Code:
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 411756 16452 395304 4% /dev
/dev/block/mmcblk1p1 3858432 1473472 2384960 38% /external_sd
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk1p1 on /external_sd type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
Code:
~ # tail ./etc/recovery.fstab
/system ext4 /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p23
/data ext4 /dev/block/mmcblk0p25 length=-16384
/efs ext4 /dev/block/mmcblk0p11
/boot emmc /dev/block/mmcblk0p20
/recovery emmc /dev/block/mmcblk0p21
/preload ext4 /dev/block/mmcblk0p24
/modem ext4 /dev/block/mmcblk0p12
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1
Code:
~ # tail ./etc/fstab
/dev/block/mmcblk0p23 /cache ext4 rw
/dev/block/mmcblk0p25 /data ext4 rw
/dev/block/mmcblk0p22 /system ext4 rw
/dev/null /sdcard datamedia rw
Code:
~ # 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
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No?
My ClockWorkMod recovery tool can't mount anything (/cache, /system, nothing). This is what kind of stuff I get in CWM:
Code:
-- Wiping cache...
Formatting /cache...
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p23
Cache wipe complete.
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
W:Can't unlink /cache/recovery/command
Formatting /data...
warning: get_file_size: Computed filesystem size less than 0
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Error formatting /data!
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
As you can see, there is no partitions for /system, /cache and other stuff, that should be there. (but /system, and /cache folders are present in dir listing)
I really did everything I could. I tried: restore from backup (I have one, made with recovery tool), install new ROM (With recovery tool), install stock firmware and stock kernel in ODIN mode. I even tried some PIT file: nothing did absolutely nothing to my status.
Frankly I miss some important part in understanding of filesystem, partitions, images, what is ROM, what is stock kernel, how does those 22, 23 25 partitions are created etc ...
What should I do? Please, help.
How did you mess it up
Sent from my Nexus 4 using xda app-developers app
mattoaida said:
How did you mess it up
Click to expand...
Click to collapse
As I remember correctly, I tried to repartition my External SD card with fdisk right on Android via 'adb shell'. And I delete existed (there was only one as I recall) partition on mmcblk0 (which is appeared to be not an External, but Internal =\
I tried to create fat and ext partitions on mmcblk0, but only now I thought, that I didn't format it .. and maybe ext should be made as ext3 or ext4. Don't know exactly how to do it.
Oh, looks like I have everything in console buffer (full history of distraction actions)
In the beginning I had this:
Code:
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
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 3872256 mmcblk1
179 97 3868160 mmcblk1p1
254 0 2110 dm-0
Code:
/ $ df
Filesystem Size Used Free Blksize
/dev 402.1M 84K 402M 4096
/mnt/asec 402.1M 0K 402.1M 4096
/mnt/obb 402.1M 0K 402.1M 4096
/dev/shm 402.1M 0K 402.1M 4096
/system 1.2G 414.5M 766.6M 4096
/modemfs 15.7M 4.3M 11.4M 4096
/cache 826.8M 84.8M 742M 4096
/efs 15.7M 4.5M 11.2M 4096
/preload 315M 64.2M 250.8M 4096
/data 4.6G 4G 699.2M 4096
/mnt/.lfs: Function not implemented
/storage/sdcard0 4.6G 4G 699.2M 4096
/mnt/asec/com.spruds.transport.pro.tallin-1 2M 888K 1.1M 4096
/storage/sdcard1 3.7G 905.7M 2.8G 32768
Even before everything went wrong I tried to use parted command and get an error
Code:
~ # 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) list
list
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
.....
.....
copyright information of GNU Parted
(parted) print
print
Error: Unable to satisfy all constraints on the partition.
This is fdisk print before disaster
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 954368.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes
1 heads, 16 sectors/track, 954368 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 954368 7634943+ ee EFI GPT
Partition 1 does not end on cylinder boundary
And then I deleted it
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 954368.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes
1 heads, 16 sectors/track, 954368 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 954368 7634943+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Command (m for help): d
Selected partition 1
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
I have, or perhaps it is now had, a P3113 - and in a moment of what would later be clear as stupidity, I wiped all the internal partitions. I went through and deleted them and then created some new ones - using parted. Evidence of the stupidity is below.
Code:
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 1
rm 1
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 2
rm 2
(parted) rm 3
rm 3
(parted) rm 4
rm 4
(parted) rm 5
rm 5
(parted) rm 6
rm 6
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) rm 8
rm 8
(parted) 9
rm 9
(parted) 10
rm 10
(parted) 11
rm 11
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
7 54.5MB 789MB 734MB ext4 CACHE
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) >
>
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
help [COMMAND] print general help, or help on
COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition
table)
mkfs NUMBER FS-TYPE make a FS-TYPE file system on
partititon NUMBER
mkpart PART-TYPE [FS-TYPE] START END make a partition
mkpartfs PART-TYPE FS-TYPE START END make a partition with a file system
move NUMBER START END move partition NUMBER
name NUMBER NAME name partition NUMBER as NAME
print [devices|free|list,all|NUMBER] display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit exit program
rescue START END rescue a lost partition near START
and END
resize NUMBER START END resize partition NUMBER and its file
system
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition
NUMBER
unit UNIT set the default unit to UNIT
version display the version number and
copyright information of GNU Parted
(parted) rm 7
rm 7
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: SD SD (sd/mmc)
Disk /dev/block/mmcblk1: 32.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 4194kB 20.8GB 20.8GB primary fat32 lba
2 20.8GB 32.1GB 11.3GB primary ext3
(parted) rm 1
rm 1
(parted) rm 2
rm 2
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) mkpartfs primary fat32 0 7000
mkpartfs primary fat32 0 7000
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary ext2 7000 7400
mkpartfs primary ext2 7000 7400
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary linux-swap 7400 7818
mkpartfs primary linux-swap 7400 7818
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p3 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p3 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) quit
quit
Information: You may need to update /etc/fstab.
~ # upgrade_fs
/sbin/sh: upgrade_fs: not found
~ #
~ # print
/sbin/sh: print: not found
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
(parted)
~ # ls
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /boot/
~ # du -hs
So, now my internal SD card has (or I think it has) a partition that looks like this
Code:
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
This clearly didn't sit well with it. It no longer boots, no screen, no nothing. No download mode. When I plug it into the computer and start it, I get a brief moment where it starts to act like a USB device, then disappears, then restarts. ADB can't see it.
I'm pretty sure I'm screwed here. I've tried Odin and Heimdall, on ubuntu, XP, win7. None can reach the device.
Is there any chance I can get this to run by creating an external SD card with the correct partitions on it? I read a few posts where people were able to run a device that had a corrupt SD internal card on the external one.
Any help greatly appreciated.
really ?
atomatomatomatom said:
I have, or perhaps it is now had, a P3113 - and in a moment of what would later be clear as stupidity, I wiped all the internal partitions. I went through and deleted them and then created some new ones - using parted. Evidence of the stupidity is below.
Code:
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 1
rm 1
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 2
rm 2
(parted) rm 3
rm 3
(parted) rm 4
rm 4
(parted) rm 5
rm 5
(parted) rm 6
rm 6
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) rm 8
rm 8
(parted) 9
rm 9
(parted) 10
rm 10
(parted) 11
rm 11
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
7 54.5MB 789MB 734MB ext4 CACHE
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) >
>
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
help [COMMAND] print general help, or help on
COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition
table)
mkfs NUMBER FS-TYPE make a FS-TYPE file system on
partititon NUMBER
mkpart PART-TYPE [FS-TYPE] START END make a partition
mkpartfs PART-TYPE FS-TYPE START END make a partition with a file system
move NUMBER START END move partition NUMBER
name NUMBER NAME name partition NUMBER as NAME
print [devices|free|list,all|NUMBER] display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit exit program
rescue START END rescue a lost partition near START
and END
resize NUMBER START END resize partition NUMBER and its file
system
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition
NUMBER
unit UNIT set the default unit to UNIT
version display the version number and
copyright information of GNU Parted
(parted) rm 7
rm 7
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: SD SD (sd/mmc)
Disk /dev/block/mmcblk1: 32.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 4194kB 20.8GB 20.8GB primary fat32 lba
2 20.8GB 32.1GB 11.3GB primary ext3
(parted) rm 1
rm 1
(parted) rm 2
rm 2
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) mkpartfs primary fat32 0 7000
mkpartfs primary fat32 0 7000
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary ext2 7000 7400
mkpartfs primary ext2 7000 7400
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary linux-swap 7400 7818
mkpartfs primary linux-swap 7400 7818
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p3 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p3 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) quit
quit
Information: You may need to update /etc/fstab.
~ # upgrade_fs
/sbin/sh: upgrade_fs: not found
~ #
~ # print
/sbin/sh: print: not found
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
(parted)
~ # ls
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /boot/
~ # du -hs
So, now my internal SD card has (or I think it has) a partition that looks like this
Code:
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
This clearly didn't sit well with it. It no longer boots, no screen, no nothing. No download mode. When I plug it into the computer and start it, I get a brief moment where it starts to act like a USB device, then disappears, then restarts. ADB can't see it.
I'm pretty sure I'm screwed here. I've tried Odin and Heimdall, on ubuntu, XP, win7. None can reach the device.
Is there any chance I can get this to run by creating an external SD card with the correct partitions on it? I read a few posts where people were able to run a device that had a corrupt SD internal card on the external one.
Any help greatly appreciated.
Click to expand...
Click to collapse
it happens to me too as i tried to delete and create a new partition for swap. but i can go into the download mode and the recovery mode and it is really hard to get into the download and recovery mode.
Time for a new tab.
Or maybe you can use Hemidall /Linux ADB to setup original partitions.
Google is your friend.
Pp.
I googled a whole day away. No joy. My question is: is there any chance to recover this when there is no download mode? And as far as I can tell, there is no chance of adb or mounting that internal sdcard if the device won't go into download mode. Is that correct?
The only solution I saw, and this was on a different model, is to actually pry off the internal sdcard to force the device to boot off the external sdcard instead. I could then perhaps copy a working image onto the external sdcard on my computer using dd.
The other solution is perhaps a JTAG jig: http://forum.xda-developers.com/showpost.php?p=43555803&postcount=642 -but I am not sure if I've lobotomised my tablet past the point of ever entering download mode again.
I suspect what I have done is seriously confused it by changing the partition table. So, it is stuck in a loop, before it even gets to the download mode check.
Kowyim said:
it happens to me too as i tried to delete and create a new partition for swap. but i can go into the download mode and the recovery mode and it is really hard to get into the download and recovery mode.
Click to expand...
Click to collapse
Hard would be better than my current state of 'impossible' - how did you get it into download mode? I read that people hold it down for ages and it sometimes works. I suspect this may be a cruel joke - poor suckers sitting there holding their dead tablet for days on end.
atomatomatomatom said:
I have, or perhaps it is now had, a P3113 - and in a moment of what would later be clear as stupidity, I wiped all the internal partitions. I went through and deleted them and then created some new ones - using parted. Evidence of the stupidity is below.
Code:
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 1
rm 1
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
(parted) rm 2
rm 2
(parted) rm 3
rm 3
(parted) rm 4
rm 4
(parted) rm 5
rm 5
(parted) rm 6
rm 6
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) rm 8
rm 8
(parted) 9
rm 9
(parted) 10
rm 10
(parted) 11
rm 11
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
7 54.5MB 789MB 734MB ext4 CACHE
(parted) rm 7
rm 7
Error: Partition /dev/block/mmcblk0p7 is being used. You must unmount it before
you modify it with Parted.
(parted) >
>
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
help [COMMAND] print general help, or help on
COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition
table)
mkfs NUMBER FS-TYPE make a FS-TYPE file system on
partititon NUMBER
mkpart PART-TYPE [FS-TYPE] START END make a partition
mkpartfs PART-TYPE FS-TYPE START END make a partition with a file system
move NUMBER START END move partition NUMBER
name NUMBER NAME name partition NUMBER as NAME
print [devices|free|list,all|NUMBER] display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit exit program
rescue START END rescue a lost partition near START
and END
resize NUMBER START END resize partition NUMBER and its file
system
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition
NUMBER
unit UNIT set the default unit to UNIT
version display the version number and
copyright information of GNU Parted
(parted) rm 7
rm 7
(parted) print
print
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk1 mmcblk1p2
mmcblk0boot0 mmcblk0p10 mmcblk0p9 mmcblk1p1
~ # parted /dev/block/mmcblk1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: SD SD (sd/mmc)
Disk /dev/block/mmcblk1: 32.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 4194kB 20.8GB 20.8GB primary fat32 lba
2 20.8GB 32.1GB 11.3GB primary ext3
(parted) rm 1
rm 1
(parted) rm 2
rm 2
(parted) ^C
(parted)
Information: You may need to update /etc/fstab.
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/
loop0 loop7 mmcblk0p9 ram12 ram5
loop1 mmcblk0 mmcblk1 ram13 ram6
loop2 mmcblk0boot0 platform/ ram14 ram7
loop3 mmcblk0boot1 ram0 ram15 ram8
loop4 mmcblk0p10 ram1 ram2 ram9
loop5 mmcblk0p11 ram10 ram3
loop6 mmcblk0p7 ram11 ram4
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # parted /dev/block/mmcblk
mmcblk0 mmcblk0boot1 mmcblk0p11 mmcblk0p9
mmcblk0boot0 mmcblk0p10 mmcblk0p7 mmcblk1
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) mkpartfs primary fat32 0 7000
mkpartfs primary fat32 0 7000
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary ext2 7000 7400
mkpartfs primary ext2 7000 7400
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) mkpartfs primary linux-swap 7400 7818
mkpartfs primary linux-swap 7400 7818
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p1 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p2 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p2 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
Error: Error informing the kernel about modifications to partition
/dev/block/mmcblk0p3 -- Device or resource busy. This means Linux won't know
about any changes you made to /dev/block/mmcblk0p3 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Ignore/Cancel? i
i
(parted) quit
quit
Information: You may need to update /etc/fstab.
~ # upgrade_fs
/sbin/sh: upgrade_fs: not found
~ #
~ # print
/sbin/sh: print: not found
~ # 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
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
(parted)
~ # ls
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /
boot etc sd-ext
cache init sdcard
charger init.rc sys
data misc system
datadata proc tmp
default.prop res ueventd.espresso.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # ls /boot/
~ # du -hs
So, now my internal SD card has (or I think it has) a partition that looks like this
Code:
1 17.4kB 7000MB 7000MB fat32 msftres
2 7000MB 7400MB 400MB ext2
3 7400MB 7818MB 418MB linux-swap(v1)
This clearly didn't sit well with it. It no longer boots, no screen, no nothing. No download mode. When I plug it into the computer and start it, I get a brief moment where it starts to act like a USB device, then disappears, then restarts. ADB can't see it.
I'm pretty sure I'm screwed here. I've tried Odin and Heimdall, on ubuntu, XP, win7. None can reach the device.
Is there any chance I can get this to run by creating an external SD card with the correct partitions on it? I read a few posts where people were able to run a device that had a corrupt SD internal card on the external one.
Any help greatly appreciated.
Click to expand...
Click to collapse
atomatomatomatom said:
Hard would be better than my current state of 'impossible' - how did you get it into download mode? I read that people hold it down for ages and it sometimes works. I suspect this may be a cruel joke - poor suckers sitting there holding their dead tablet for days on end.
Click to expand...
Click to collapse
what did you mean by cruel joke ? it is happening to me right now and i want to know if there is any solution for this..
my parents would've kill me if they know
---------- Post added at 08:39 PM ---------- Previous post was at 08:30 PM ----------
PanchoPlanet said:
Time for a new tab.
Or maybe you can use Hemidall /Linux ADB to setup original partitions.
Google is your friend.
Pp.
Click to expand...
Click to collapse
what did you mean by using hemiball / linux adb ?
please teach me how because i really want to have my tab alive back
Kowyim said:
what did you mean by cruel joke ? it is happening to me right now and i want to know if there is any solution for this..
my parents would've kill me if they know
Click to expand...
Click to collapse
you said you can get it into download mode, but that it was 'hard' to get it into download mode. my device doesn't even go into download mode.
the cruel joke bit was that i read holding down the power/vol down for ages might bring it back into download mode eventually. but how long. 10 minutes, 1 hour, 1 day, 1 week?
if your tablet boots and shows anything on the display, you can probably get it into download mode. then just follow one of the guides that tells you how to restore it it to stock firmware.
atomatomatomatom said:
you said you can get it into download mode, but that it was 'hard' to get it into download mode. my device doesn't even go into download mode.
the cruel joke bit was that i read holding down the power/vol down for ages might bring it back into download mode eventually. but how long. 10 minutes, 1 hour, 1 day, 1 week?
if your tablet boots and shows anything on the display, you can probably get it into download mode. then just follow one of the guides that tells you how to restore it it to stock firmware.
Click to expand...
Click to collapse
hard means i need to do it over and over till i get into the recovery or download mode. i wish i could post a video about it but too bad i dont have a phone that can record..
our problem is the same i think because we tried to delete and recreate partition. now i cant even mount sd card (internal) because of the attempt of swapping.
thanks, perhaps i'll try again to get into download mode. so, you just keep trying. how long do you wait before retrying it? i hold power down, then also power on, and i see nothing. i don't know how long to hold it down before retying - or if i should do anything else in the meantime.
my understanding is you need to use odin or heimdall to restore the whole device, including the partition table. if you can get it into download mode, then you plug it into the computer and transfer the image from there. i would start with the stock one from http://www.sammobile.com/firmwares/
i can't find the instructions right now, but if your partition is altered, i think you want to find a PIT file for your device as well as restore the firmware.
atomatomatomatom said:
you said you can get it into download mode, but that it was 'hard' to get it into download mode. my device doesn't even go into download mode.
the cruel joke bit was that i read holding down the power/vol down for ages might bring it back into download mode eventually. but how long. 10 minutes, 1 hour, 1 day, 1 week?
if your tablet boots and shows anything on the display, you can probably get it into download mode. then just follow one of the guides that tells you how to restore it it to stock firmware.
Click to expand...
Click to collapse
atomatomatomatom said:
thanks, perhaps i'll try again to get into download mode. so, you just keep trying. how long do you wait before retrying it? i hold power down, then also power on, and i see nothing. i don't know how long to hold it down before retying - or if i should do anything else in the meantime.
my understanding is you need to use odin or heimdall to restore the whole device, including the partition table. if you can get it into download mode, then you plug it into the computer and transfer the image from there. i would start with the stock one from http://www.sammobile.com/firmwares/
i can't find the instructions right now, but if your partition is altered, i think you want to find a PIT file for your device as well as restore the firmware.
Click to expand...
Click to collapse
it was around 1-2 minute. if it doesn't work then i will restart and retry till i get into.
---------- Post added at 11:52 PM ---------- Previous post was at 11:33 PM ----------
atomatomatomatom said:
thanks, perhaps i'll try again to get into download mode. so, you just keep trying. how long do you wait before retrying it? i hold power down, then also power on, and i see nothing. i don't know how long to hold it down before retying - or if i should do anything else in the meantime.
my understanding is you need to use odin or heimdall to restore the whole device, including the partition table. if you can get it into download mode, then you plug it into the computer and transfer the image from there. i would start with the stock one from http://www.sammobile.com/firmwares/
i can't find the instructions right now, but if your partition is altered, i think you want to find a PIT file for your device as well as restore the firmware.
Click to expand...
Click to collapse
OMG OMG OMG did you have skype ?
omg you helped me !
i must repay you ! please add my skype - koyimz
that is great. glad you got yours fixed.
i'll try holding down my buttons for longer and hope that something comes up!
atomatomatomatom said:
thanks, perhaps i'll try again to get into download mode. so, you just keep trying. how long do you wait before retrying it? i hold power down, then also power on, and i see nothing. i don't know how long to hold it down before retying - or if i should do anything else in the meantime.
my understanding is you need to use odin or heimdall to restore the whole device, including the partition table. if you can get it into download mode, then you plug it into the computer and transfer the image from there. i would start with the stock one from http://www.sammobile.com/firmwares/
i can't find the instructions right now, but if your partition is altered, i think you want to find a PIT file for your device as well as restore the firmware.
Click to expand...
Click to collapse
awwww i thought that i have it fixed . but it stuck at the samsung logo and when i open recovery mode and try to wipe data it says e: unknown volume for path [/sd-ext] . but it says the data wipe complete and no fail except the sd-ext thing. any idea how to fix this ??
well, i fixed it. the rather harsh way. ebayed a used main board ($20), after shipping and exchange rates it came to about $40 canadian.
i might try hacking the old board open to see if i can scrape off the brain-dead SD card and see if that will force it to boot on the external card. but that is just for 'fun' now.
Thanks for the " Don't mess with the partitions " lesson you gave the forum.
Lol.
Pp.
ha. yeah, won't do that again.
i started going down the rabbit hole of trying to learn how to flash the OMAP4430 back into a booting state, but after wasting about 2 days i realized this was a total waste of my time when i could replace the board (or buy a new tablet) for the amount of time i had spent on it. boooooooo. but still burns!
I have a Prestigio 5044 Duo (PAP5044) with MTK6589. Basically, what I was trying to do was to resize /data partition, beacause it was only about 950Mb, by shrinking Internal SD card (/emmc) partition. For that I used Meteos MTK6589 Apllication.
After going all the steps I found out that Android OS was hanging during boot (like half-way to boot up, and it freezed with no error messages). Though, recovery (I have CWM) boots well.
After doing some research I found out, that partition table of the device was messed up after /cache partition. So, all system and recovery partititons are fine.
Here is fdisk output:
Code:
~ # fdisk -lu /dev/block/mmcblk0
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Disk /dev/block/mmcblk0: 3853 MB, 3853516800 bytes
1 heads, 16 sectors/track, 470400 cylinders, total 7526400 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1024 1022 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26624 47103 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 47104 67583 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 93184 105471 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 134144 1465343 665600 83 Linux
/dev/block/mmcblk0p6 7556096 1022 2143706111+ 83 Linux
And here are /proc/partitions and fstab:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 3763200 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 665600 mmcblk0p5
179 6 129024 mmcblk0p6
179 7 2901504 mmcblk0p7
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 31338496 mmcblk1
179 97 31334400 mmcblk1p1
~ # cat /etc/fstab
/dev/block/mmcblk0p6 /cache ext4 rw
/dev/block/mmcblk0p7 /data ext4 rw
/dev/block/mmcblk0p8 /emmc vfat rw
/dev/block/mmcblk0p5 /system ext4 rw
/dev/block/mmcblk1p1 /sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext auto rw
So, on mmcblk0 there must be 10 partitions, and now there are only 6, according to fdisk.
I have two ideas how it is possible to restore partitions: 1) manually with fdisk, though it doesn't seem like a very good idea 2) I've found some info about scatter file for MTK-based devices, seems like it contains all the partitioning info; I have no idea how to get and use that file, though.
What should I do to recover my device?
Hi guys,
I could probably make a thread outside TF700 forums as my questions are more generic but as I don't know what place would suit it better and as my device is TF700T, I'm doing it here.
Some time ago I was messing around with my TF700T which at that moment was already unlocked and rooted. I had TWRP (not sure what version exactly it was but probably something close to 2.8.x) and CyanogenMod 11-20160815-NIGHTLY-tf700t installed and working properly. As I wanted to install Gentoo on it, I replaced TWRP with something else (don't remember what was that) and finally somehow screwed recovery. As I don't fully remember what has happened back then, I can tell how it is now.
So the tablet is working without problems but recovery is not accessible. Whenever I try to boot into recovery choosing the RCK icon in a boot menu the tablet is hanging.
But as both adb and fastboot can see the tablet, I decided to dig it a bit more.
Code:
# adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
015d2a50865c1a07 device
# adb reboot bootloader
# fastboot devices
015d2a50865c1a07 fastboot
# fastboot -i 0x0B05 flash recovery twrp-3.2.1-0-tf700t.img
sending 'recovery' (7414 KB)...
As this process seems to be endless I decide to interrupt it using the power button on the tablet. As result I get a message:
Code:
FAILED (data transfer failure (Cannot send after transport endpoint shutdown))
finished. total time: 337.278s
Then I decide to inspect how partitions look like using the adb shell but first I inspect fstab to see what supposed to be mounted:
Code:
# adb shell
[email protected]:/ $ su
[email protected]:/ # cat fstab.cardhu
# INIT mount points
/dev/block/mmcblk0p1 /system ext4 noatime,noauto_da_alloc,nodiratime,barrier=0,ro wait
/dev/block/mmcblk0p2 /cache ext4 noatime,noauto_da_alloc,nosuid,nodev,nodiratime,barrier=0,errors=panic wait
/dev/block/mmcblk0p8 /data ext4 noatime,noauto_da_alloc,nosuid,nodev,nodiratime,barrier=0,errors=panic wait,encryptable=footer
# VOLD mount points
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/tegra-ehci.2/usb1/1-1/1-1.2 auto auto defaults voldmanaged=usbdisk0:auto
/devices/platform/tegra-ehci.2/usb2/2-1/2-1.2 auto auto defaults voldmanaged=usbdisk0:auto
/devices/platform/tegra-ehci.2/usb1/1-1/1-1.1 auto auto defaults voldmanaged=usbdisk1:auto
/devices/platform/tegra-ehci.2/usb2/2-1/2-1.1 auto auto defaults voldmanaged=usbdisk1:auto
/devices/platform/tegra-ehci.2/usb2/2-1/2-1:1 auto auto defaults voldmanaged=usbdisk1:auto
/devices/platform/tegra-ehci.2/usb1/1-1/1-1:1 auto auto defaults voldmanaged=usbdisk1:auto
/devices/platform/tegra-ehci.2/usb1/1-1/1-1.3 auto auto defaults voldmanaged=sdcard2:auto
/devices/platform/tegra-ehci.2/usb2/2-1/2-1.3 auto auto defaults voldmanaged=sdcard2:auto
# Recovery only
/dev/block/mmcblk1p1 /external_sd auto defaults recoveryonly
/dev/block/mmcblk0p3 /misc emmc defaults recoveryonly
/dev/block/mmcblk0p4 /staging ext3 defaults recoveryonly
/dev/block/mmcblk0p9 /recovery emmc defaults recoveryonly
/dev/block/mmcblk0p10 /boot emmc defaults recoveryonly
Then I check what partitions I have (I thought maybe recovery partition has been deleted somehow):
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 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 15622144 mmcblk1
179 49 15618048 mmcblk1p1
And finally check if parted can give me any info about these partitions. I don't care about mmcblk1 as it is an external SD card:
Code:
# parted /dev/block/mmcblk0p1
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p1: 805MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 805MB 805MB ext4
# parted /dev/block/mmcblk0p2
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p2: 449MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 449MB 449MB ext4
# parted /dev/block/mmcblk0p3
Error: /dev/block/mmcblk0p3: unrecognised disk label
# parted /dev/block/mmcblk0p4
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p4: 856MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 856MB 856MB ext3
# parted /dev/block/mmcblk0p5
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p5: 5243kB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
# parted /dev/block/mmcblk0p6
Error: /dev/block/mmcblk0p6: unrecognised disk label
# parted /dev/block/mmcblk0p7
Error: /dev/block/mmcblk0p7: unrecognised disk label
# parted /dev/block/mmcblk0p8
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/block/mmcblk0p8: 61.4GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 61.4GB 61.4GB ext4
# parted /dev/block/mmcblk0p9
Error: /dev/block/mmcblk0p9: unrecognised disk label
# parted /dev/block/mmcblk0p10
Error: /dev/block/mmcblk0p10: unrecognised disk label
# parted /dev/block/mmcblk0boot0
Error: /dev/block/mmcblk0boot0: unrecognised disk label
# parted /dev/block/mmcblk0boot1
Error: /dev/block/mmcblk0boot1: unrecognised disk label
As we can see partitions 3, 6, 7, 9, 10 and boot0, boot1 have unrecognised disk label. I can't also mount them to inspect their contents (can mount others and their contents looks good to me).
I don't see partitions 6, 7 in fstab but anyhow it does look like all unrecognised partitions have type emmc.
And recovery partition should be mmcblk0p9. The question now is: how do I mount emmc partition then in order to be able to check if it's okay or dead? How do I manage it (delete / create / resize)?
For now I would like to make recovery work. Any ideas?
Hello,
First, sorry, my ROM is Resurrection Remix ROM 5.8.5,, but i don't know how to edit the title.....
yesterday my phone suddenly rebooted and got stock in bootloop.
I entered recovery and the first thing I tried was to wiped cache and dalvik, but I got this instead:
Code:
could not mount /data and unable to find crypto footer.
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
Failed to mount /data (Invalid argument)
Full SELinux is present
Failed to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount /data (Invalid argument)
Failed to wipe dalvik
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
So I tried to manually mount, and i selected "select storage" and all options says =Mb (Internal, MicroSD and usb otg)...
So i went to the file manager, entered into sdcard and its empty.
I read around, and i found that maybe next adb command might help to find the cause:
Code:
adb shell "dmesg | grep mmc0"
got me:
Code:
<6>[ 10.376129s][pid:1,cpu4,swapper/0]mmc0: SDHCI controller on hi_mci.0 [hi_mci.0] using ADMA
<6>[ 10.462524s][pid:165,cpu7,kworker/u16:3]mmc0: MAN_BKOPS_EN bit is not set
<3>[ 10.462524s][pid:165,cpu7,kworker/u16:3]mmc0: mmc_decode_ext_csd_emmc50: CMDQ supported: depth: 32
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: mmc_decode_ext_csd: eMMC FW version:84
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support STROBE_ENHANCED.
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support CACHE_FLUSH_POLICY_FIFO.
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support RPMB 8K Bytes read/write.
<3>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: EXT_CSD revision 0x08 pre_eol_info = 0x01 device_life_time_est_typ_a = 0x02 device_life_time_est_typ_b = 0x01.
<6>[ 10.479919s][pid:165,cpu7,kworker/u16:3]sdhci: =========== REGISTER DUMP (mmc0)===========
<6>[ 10.504150s][pid:165,cpu5,kworker/u16:3]mmc0: eMMC init card done, support bus_width=8 bit.
<6>[ 10.504180s][pid:165,cpu5,kworker/u16:3]mmc0: new HS400 MMC card at address 0001,manfid:0x13,date:2017/10
<6>[ 10.506164s][pid:165,cpu6,kworker/u16:3]mmcblk0: mmc0:0001 Q3J96V 14.7 GiB
<6>[ 10.506256s][pid:165,cpu7,kworker/u16:3]mmcblk0boot0: mmc0:0001 Q3J96V partition 1 4.00 MiB
<6>[ 10.506500s][pid:165,cpu7,kworker/u16:3]mmcblk0boot1: mmc0:0001 Q3J96V partition 2 4.00 MiB
<6>[ 10.506561s][pid:165,cpu7,kworker/u16:3]mmcblk0rpmb: mmc0:0001 Q3J96V partition 3 4.00 MiB
also:
Code:
adb shell "ls /dev/block"
and I got:
Code:
bootdevice
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p3
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p34
mmcblk0p35
mmcblk0p36
mmcblk0p37
mmcblk0p38
mmcblk0p39
mmcblk0p4
mmcblk0p40
mmcblk0p41
mmcblk0p42
mmcblk0p43
mmcblk0p44
mmcblk0p45
mmcblk0p46
mmcblk0p47
mmcblk0p48
mmcblk0p49
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0rpmb
platform
ram0
ram1
ram2
ram3
zram0
And this is what i could grab from the logcat on the bootloop.
logcat.txt
But I don't know hot to read the outputs, or if they are helpful.....
kurokirasama said:
Hello,
First, sorry, my ROM is Resurrection Remix ROM 5.8.5,, but i don't know how to edit the title.....
yesterday my phone suddenly rebooted and got stock in bootloop.
I entered recovery and the first thing I tried was to wiped cache and dalvik, but I got this instead:
Code:
could not mount /data and unable to find crypto footer.
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
Failed to mount /data (Invalid argument)
Full SELinux is present
Failed to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount /data (Invalid argument)
Failed to wipe dalvik
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
So I tried to manually mount, and i selected "select storage" and all options says =Mb (Internal, MicroSD and usb otg)...
So i went to the file manager, entered into sdcard and its empty.
I read around, and i found that maybe next adb command might help to find the cause:
Code:
adb shell "dmesg | grep mmc0"
got me:
Code:
<6>[ 10.376129s][pid:1,cpu4,swapper/0]mmc0: SDHCI controller on hi_mci.0 [hi_mci.0] using ADMA
<6>[ 10.462524s][pid:165,cpu7,kworker/u16:3]mmc0: MAN_BKOPS_EN bit is not set
<3>[ 10.462524s][pid:165,cpu7,kworker/u16:3]mmc0: mmc_decode_ext_csd_emmc50: CMDQ supported: depth: 32
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: mmc_decode_ext_csd: eMMC FW version:84
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support STROBE_ENHANCED.
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support CACHE_FLUSH_POLICY_FIFO.
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support RPMB 8K Bytes read/write.
<3>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: EXT_CSD revision 0x08 pre_eol_info = 0x01 device_life_time_est_typ_a = 0x02 device_life_time_est_typ_b = 0x01.
<6>[ 10.479919s][pid:165,cpu7,kworker/u16:3]sdhci: =========== REGISTER DUMP (mmc0)===========
<6>[ 10.504150s][pid:165,cpu5,kworker/u16:3]mmc0: eMMC init card done, support bus_width=8 bit.
<6>[ 10.504180s][pid:165,cpu5,kworker/u16:3]mmc0: new HS400 MMC card at address 0001,manfid:0x13,date:2017/10
<6>[ 10.506164s][pid:165,cpu6,kworker/u16:3]mmcblk0: mmc0:0001 Q3J96V 14.7 GiB
<6>[ 10.506256s][pid:165,cpu7,kworker/u16:3]mmcblk0boot0: mmc0:0001 Q3J96V partition 1 4.00 MiB
<6>[ 10.506500s][pid:165,cpu7,kworker/u16:3]mmcblk0boot1: mmc0:0001 Q3J96V partition 2 4.00 MiB
<6>[ 10.506561s][pid:165,cpu7,kworker/u16:3]mmcblk0rpmb: mmc0:0001 Q3J96V partition 3 4.00 MiB
also:
Code:
adb shell "ls /dev/block"
and I got:
Code:
bootdevice
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p3
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p34
mmcblk0p35
mmcblk0p36
mmcblk0p37
mmcblk0p38
mmcblk0p39
mmcblk0p4
mmcblk0p40
mmcblk0p41
mmcblk0p42
mmcblk0p43
mmcblk0p44
mmcblk0p45
mmcblk0p46
mmcblk0p47
mmcblk0p48
mmcblk0p49
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0rpmb
platform
ram0
ram1
ram2
ram3
zram0
And this is what i could grab from the logcat on the bootloop.
logcat.txt
But I don't know hot to read the outputs, or if they are helpful.....
Click to expand...
Click to collapse
i fixed it using:
https://forum.xda-developers.com/transformer-tf701/help/dead-mmc-ideas-t2830332