Database Info

Internal memory screwed up

Hallo guys,
got a little problem with my phone
it crashed while restoring an backup, now internal memory seems to be messed up.
1. Download Mode is working (flashed StockRom and Broodrom rc5)
2. I can reboot to recovery (I can flash other recovery, from internal sdcard, mounting USB works)
3. Mounting /system /data -> Recovery crashes
4. Factroy Reset does not work
3. When i try to flash a rom.zip it seems that only kernel is changed.
4. Factory Reset is not working
5. I can connect with adb
Perhaps you can have a look on the following outputs
fdisk -l
Code:
~ # ←[6nfdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
~ # ←[6nfdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1
fdisk: can't open '/dev/block/mmcblk0p1': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p2
fdisk -l /dev/block/mmcblk0p2
fdisk: can't open '/dev/block/mmcblk0p2': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p3
fdisk -l /dev/block/mmcblk0p3
fdisk: can't open '/dev/block/mmcblk0p3': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p4
fdisk -l /dev/block/mmcblk0p4
fdisk: can't open '/dev/block/mmcblk0p4': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p5
fdisk -l /dev/block/mmcblk0p5
fdisk: can't open '/dev/block/mmcblk0p5': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p6
fdisk -l /dev/block/mmcblk0p6
fdisk: can't open '/dev/block/mmcblk0p6': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p7
fdisk -l /dev/block/mmcblk0p7
fdisk: can't open '/dev/block/mmcblk0p7': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p8
fdisk -l /dev/block/mmcblk0p8
fdisk: can't open '/dev/block/mmcblk0p8': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p9
fdisk -l /dev/block/mmcblk0p9
fdisk: can't open '/dev/block/mmcblk0p9': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p10
fdisk -l /dev/block/mmcblk0p10
fdisk: can't open '/dev/block/mmcblk0p10': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p11
fdisk -l /dev/block/mmcblk0p11
fdisk: can't open '/dev/block/mmcblk0p11': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p12
fdisk -l /dev/block/mmcblk0p12
fdisk: can't open '/dev/block/mmcblk0p12': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p13
fdisk -l /dev/block/mmcblk0p13
fdisk: can't open '/dev/block/mmcblk0p13': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p14
fdisk -l /dev/block/mmcblk0p14
fdisk: can't open '/dev/block/mmcblk0p14': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p15
fdisk -l /dev/block/mmcblk0p15
fdisk: can't open '/dev/block/mmcblk0p15': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p16
fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
~ # ←[6nfdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
fdisk: can't open '/dev/block/mmcblk0p17': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p18
fdisk -l /dev/block/mmcblk0p18
fdisk: can't open '/dev/block/mmcblk0p18': I/O error
mounting /data in recovery:
Code:
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
E:Unable to mount '/data'
Same error on all recoverys CWM / TWRP
Perhaps someone can give an advice

Try formatting system, data and cache then install broodROM RC5 again, it might work.
Did you use the correct recovery while changing roms? you need to use cwm 5.0.0.4 atleast

Flash recovery through ODIN...
Sent from my GT-I9001 using Tapatalk 2

broodplank1337 said:
Try formatting system, data and cache then install broodROM RC5 again, it might work.
Did you use the correct recovery while changing roms? you need to use cwm 5.0.0.4 atleast
Click to expand...
Click to collapse
How can i format data with adb?
I used CWM 6.0.2.7
recovery stucks always at formating data... until i kill by pressing power button
In recovery all functions where mounting /data is not needed are working.
Works
format system
format cache
wipe android secur
Fails
mount data
wipe dalvik
fix permissions

buffo1987 said:
Hallo guys,
got a little problem with my phone
it crashed while restoring an backup, now internal memory seems to be messed up.
1. Download Mode is working (flashed StockRom and Broodrom rc5)
2. I can reboot to recovery (I can flash other recovery, from internal sdcard, mounting USB works)
3. Mounting /system /data -> Recovery crashes
4. Factroy Reset does not work
3. When i try to flash a rom.zip it seems that only kernel is changed.
4. Factory Reset is not working
5. I can connect with adb
Perhaps you can have a look on the following outputs
fdisk -l
Code:
~ # ←[6nfdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
~ # ←[6nfdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1
fdisk: can't open '/dev/block/mmcblk0p1': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p2
fdisk -l /dev/block/mmcblk0p2
fdisk: can't open '/dev/block/mmcblk0p2': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p3
fdisk -l /dev/block/mmcblk0p3
fdisk: can't open '/dev/block/mmcblk0p3': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p4
fdisk -l /dev/block/mmcblk0p4
fdisk: can't open '/dev/block/mmcblk0p4': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p5
fdisk -l /dev/block/mmcblk0p5
fdisk: can't open '/dev/block/mmcblk0p5': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p6
fdisk -l /dev/block/mmcblk0p6
fdisk: can't open '/dev/block/mmcblk0p6': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p7
fdisk -l /dev/block/mmcblk0p7
fdisk: can't open '/dev/block/mmcblk0p7': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p8
fdisk -l /dev/block/mmcblk0p8
fdisk: can't open '/dev/block/mmcblk0p8': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p9
fdisk -l /dev/block/mmcblk0p9
fdisk: can't open '/dev/block/mmcblk0p9': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p10
fdisk -l /dev/block/mmcblk0p10
fdisk: can't open '/dev/block/mmcblk0p10': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p11
fdisk -l /dev/block/mmcblk0p11
fdisk: can't open '/dev/block/mmcblk0p11': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p12
fdisk -l /dev/block/mmcblk0p12
fdisk: can't open '/dev/block/mmcblk0p12': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p13
fdisk -l /dev/block/mmcblk0p13
fdisk: can't open '/dev/block/mmcblk0p13': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p14
fdisk -l /dev/block/mmcblk0p14
fdisk: can't open '/dev/block/mmcblk0p14': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p15
fdisk -l /dev/block/mmcblk0p15
fdisk: can't open '/dev/block/mmcblk0p15': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p16
fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
~ # ←[6nfdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
fdisk: can't open '/dev/block/mmcblk0p17': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p18
fdisk -l /dev/block/mmcblk0p18
fdisk: can't open '/dev/block/mmcblk0p18': I/O error
Perhaps someone can give an advice
Click to expand...
Click to collapse
did you use TWRP recovery ??

zikozoko said:
did you use TWRP recovery ??
Click to expand...
Click to collapse
cwm 6.0.2.7
Now i tried several recoverys TWRP and CWM but they are all working same without /data
flased broodrom rc5 again, stuck on boot. Can not factory reset, /data still not mountabel

I think your solution must be this:
You need to flash an empty data.img.ext4 to your phone using odin, I did it once, and it succeeded! But you first need to make it:
busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
1gb empty data.img.ext4 file, which can be flashed to restore the paritition
pack the file for odin:
tar -c data.img.ext4 > fix.tar
md5sum -t fix.tar >> fix.tar
mv fix.tar fix.tar.md5
So you either need cygwin or a native linux shell.

Or u can flash a stock rom via Odin and after booting install another recovery (ex 5.5.0.4 the most stable for me) and another costum rom.
VEREY IMPORTANT make sure u have the right AriesVE.ops. Try to download from SamMobile.

broodplank1337 said:
I think your solution must be this:
You need to flash an empty data.img.ext4 to your phone using odin, I did it once, and it succeeded! But you first need to make it:
busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
1gb empty data.img.ext4 file, which can be flashed to restore the paritition
pack the file for odin:
tar -c data.img.ext4 > fix.tar
md5sum -t fix.tar >> fix.tar
mv fix.tar fix.tar.md5
So you either need cygwin or a native linux shell.
Click to expand...
Click to collapse
Looks quite interesting.
I#m not sure what i have to do:
connect phone to ubuntu vm
Terminal:
Code:
$ adb busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
$ cd /sdcard/
$ tar -c data.img.ext4 > fix.tar
$ md5sum -t fix.tar >> fix.tar
$ mv fix.tar fix.tar.md5
2. Flash fix.tar.md5 as one package with odin
right?

broodplank1337 said:
I think your solution must be this:
You need to flash an empty data.img.ext4 to your phone using odin, I did it once, and it succeeded! But you first need to make it:
busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
1gb empty data.img.ext4 file, which can be flashed to restore the paritition
pack the file for odin:
tar -c data.img.ext4 > fix.tar
md5sum -t fix.tar >> fix.tar
mv fix.tar fix.tar.md5
So you either need cygwin or a native linux shell.
Click to expand...
Click to collapse
Hi , TNX
What about this script should run on recovery :
Code:
cat /dev/zero > /dev/block/mmcblk0pX

Code:
[email protected]:~$ adb shell
~ # busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
phone crashes -> data.img.ext4 is only 661 MB
will retry...
I think you did not meant me to do this on the phone.
Code:
[email protected]:~$ cd resc/
[email protected]:~/resc$ busybox dd if=/dev/zero of=^Cata.img.ext4 bs=1M count=1024
[email protected]:~/resc$ busybox dd if=/dev/zero of=data.img.ext4 bs=1M count=1024
1024+0 records in
1024+0 records out
[email protected]:~/resc$ tar -c data.img.ext4 > fix.tar
[email protected]:~/resc$ md5sum -t fix.tar >> fix.tar
[email protected]:~/resc$ mv fix.tar fix.tar.md5
I got the file now
Odin
Code:
Check MD5 FileName...
MD5 File Name : fix.tar
Open File Name : fix.tar
Check MD5 ...
Tail MD5 : 5654164EA05D41668D50F97731E2EB5A
Image MD5 : 5654164EA05D41668D50F97731E2EB5A
Check MD5 ... ok
<1> Added!!!
<1> Detected!!!
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> e - unknown file - "data.img.ext4"
<1> set download environment.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
Problem still exits

buffo1987 said:
Hallo guys,
got a little problem with my phone
it crashed while restoring an backup, now internal memory seems to be messed up.
1. Download Mode is working (flashed StockRom and Broodrom rc5)
2. I can reboot to recovery (I can flash other recovery, from internal sdcard, mounting USB works)
3. Mounting /system /data -> Recovery crashes
4. Factroy Reset does not work
3. When i try to flash a rom.zip it seems that only kernel is changed.
4. Factory Reset is not working
5. I can connect with adb
Perhaps you can have a look on the following outputs
fdisk -l
mounting /data in recovery:
Code:
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
E:Unable to mount '/data'
Same error on all recoverys CWM / TWRP
Perhaps someone can give an advice
Click to expand...
Click to collapse
Hey Buffo,
I have the same problem after trying your test-versions. I could "revive" all partitions but data by downgrading recovery to 5.5.04 and formating system and cache then. But also data could not be formatted via 5.5.04 so I also will try broods proposal...
btw. this does not work to solve it.
Code:
cat /dev/zero > /dev/block/mmcblk0pX

magicw said:
Hey Buffo,
I have the same problem after trying your test-versions. I could "revive" all partitions but data by downgrading recovery to 5.5.04 and formating system and cache then. But also data could not be formatted via 5.5.04 so I also will try broods proposal...
btw. this does not work to solve it.
Code:
cat /dev/zero > /dev/block/mmcblk0pX
Click to expand...
Click to collapse
Sad to here that,
removed all cwm 6.0.2.7 downloads from my post.
At least flashing a stock rom makes the phone look untouched, so i will send it for repair...
I already tried to format data with adb: mke2fs -L data -b 4096 -m 0 -F /dev/block/mmcblk0p17, but also just works with /system + /cache
When exactly did it happen for you?

hey here i found something
i do not know if it helps but read it and decide it looks like your problem in a way
for another device but maybe helpful
http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/

krislibaeer said:
hey here i found something
i do not know if it helps but read it and decide it looks like your problem in a way
for another device but maybe helpful
http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/
Click to expand...
Click to collapse
interesting. I've run parted via adb and mmcblk0p17 shows 1447 MB - shouldn't this be 1024 MB only?

magicw said:
interesting. I've run parted via adb and mmcblk0p17 shows 1447 MB - shouldn't this be 1024 MB only?
Click to expand...
Click to collapse
Code:
179 0 7755776 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5120 mmcblk0p8 //boot
179 9 7000 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 532480 mmcblk0p15 //system
179 16 102400 mmcblk0p16 //cache
179 17 1413120 mmcblk0p17 //data
179 18 204800 mmcblk0p18 //preload
179 19 500 mmcblk0p19 // These
179 20 3596 mmcblk0p20 // partitions
179 21 5120 mmcblk0p21 // are
179 22 20000 mmcblk0p22 // either
179 23 5120 mmcblk0p23 // empty
179 24 7000 mmcblk0p24 // or
179 25 5120 mmcblk0p25 // backup
179 26 5120 mmcblk0p26 // partitions
179 27 5120 mmcblk0p27 //efs
179 28 5228544 mmcblk0p28 //internal sdcard

Xistance said:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5632 mmcblk0p8 //boot
179 9 6488 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 547840 mmcblk0p15 //system
179 16 61440 mmcblk0p16 //cache
179 17 1136640 mmcblk0p17 //data
179 18 51200 mmcblk0p18 //preload
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27 //efs
179 28 1787904 mmcblk0p28 //internal sdcard
Click to expand...
Click to collapse
wtf your internal sdcard is 4gb? (if you look at the total blocks)
check my output with 8gb internal
Code:
cat proc/partitions
major minor #blocks name
179 0 7755776 mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 5228544 mmcblk0p28

broodplank1337 said:
wtf your internal sdcard is 4gb? (if you look at the total blocks)
check my output with 8gb internal
Code:
cat proc/partitions
major minor #blocks name
179 0 7755776 mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 5228544 mmcblk0p28
Click to expand...
Click to collapse
Oh yeah sorry. I took it from arco on his Galaxy W and forgot they had different sizes =.=.
Edit : Fixed ^^

Code:
(parted) check
check
check
Error: Can't have a partition outside the disk!
Code:
major minor #blocks name
179 0 [COLOR="Red"]7552000 [/COLOR]mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 [COLOR="Red"]5024768 [/COLOR]mmcblk0p28

buffo1987 said:
Code:
(parted) check
check
check
Error: Can't have a partition outside the disk!
Code:
major minor #blocks name
179 0 [COLOR="Red"]7552000 [/COLOR]mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 [COLOR="Red"]5024768 [/COLOR]mmcblk0p28
Click to expand...
Click to collapse
the partition has a shift of 203776 (both have same size )
that is weird

[Q] How to restore damaged Internal SD card partition layout? Tried everything.

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

[Q] Problems with partition table

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?

[Q] "FAILED (remote: flash write failure)" Unable to Flash Factory Image

Hey guys,
I had successfully flashed a factory image of Marshmallow 6.0.1, but ran into a problem in which my 32GB Nexus 5 shows only 16 GB of storage. I followed a guide which recommended to reflash the factory image. When attempting to get into the bootloader I had another problem in which my phone would boot on and off repeatedly when charging. A post on Reddit suggested that the problem was with the power button being jammed and gently hitting the side of the phone would do the trick. It worked. I then tried to reflash the factory image. But now currently when I try to flash either bootloader, radio, recovery, system, or userdata, I get the error message "FAILED (remote: flash write failure)".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I even tried running "flash-all.bat", but still got the same error.
I have been unable to find a solution to this error. I tried to flash TWRP (so I can restore my back up), but I still get the error "FAILED (remote: flash write failure)".
I would greatly appreciate it if someone were to guide me through solving this "FAILED (remote: flash write failure)" error.
Thank you so much.
(This is my first time posting on the XDA Forum so forgive me if I didn't follow etiquette to posting a thread. Also i was unable to post any links since this is my first post, I can send you links for the two problems I had in the beginning as they may be related to my current problem.)

Instead of using fastboot flash, do fastboot boot recovery.img,
then, push the recovery.img to the phone:
adb push recovery.img /sdcard/
And finally, if your eMMC isn't dead, you should be able to flash it

The bootloader is unlocked according to the fastboot screen? Does the bootloader remain unlocked when the phone is rebooted?

nagalun said:
Instead of using fastboot flash, do fastboot boot recovery.img,
then, push the recovery.img to the phone:
adb push recovery.img /sdcard/
And finally, if your eMMC isn't dead, you should be able to flash it
Click to expand...
Click to collapse
When I attempt to do "fastboot boot recovery.img" It boots up to the blue teamwin screen and stops working. It's just frozen at that screen and doesn't actually boot into the recovery with options. Since I was unable to do that I tried the adb method. I was unsure as to how to do it but what I did was I booted into stock recovery and chose the option to "Apply update by ADB", after doing so I attempted to do "adb push recovery.img /sdcard/", but I get an error saying "error: closed". I am pretty sure I am doing the adb part incorrectly.
(also how do I post images?)
Also what do you mean by my eMMC being bead?

audit13 said:
The bootloader is unlocked according to the fastboot screen? Does the bootloader remain unlocked when the phone is rebooted?
Click to expand...
Click to collapse
Yes it remains unlocked. The bootloader has not had any issue in which it switches from being unlocked or locked.

emouser said:
When I attempt to do "fastboot boot recovery.img" It boots up to the blue teamwin screen and stops working. It's just frozen at that screen and doesn't actually boot into the recovery with options. Since I was unable to do that I tried the adb method. I was unsure as to how to do it but what I did was I booted into stock recovery and chose the option to "Apply update by ADB", after doing so I attempted to do "adb push recovery.img /sdcard/", but I get an error saying "error: closed". I am pretty sure I am doing the adb part incorrectly.
(also how do I post images?)
Also what do you mean by my eMMC being bead?
Click to expand...
Click to collapse
Your memory chip might be dead, but I am not sure.
Try doing fastboot boot recovery.img again, then it doesn't matter if it doesn't boot fully, adb _should_ be working.
While it is in the blue teamwin screen, do this:
adb shell
With a bit of luck it will work and you will get something like this (or similar):
~ #
If it does work, enter the commands 'mount' and 'ls /dev/block' and tell me what it outputs here, by the way, you can use imgur to post images.

i have the same problem.
i get this:#
C:\Users\mcse\Desktop\hammerhead-m4b30z-factory-625c027b\hammerhead-m4b30z>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
~ # ls /dev/block
bootdevice mmcblk0p1 mmcblk0p19 mmcblk0p28 platform ram3
loop0 mmcblk0p10 mmcblk0p2 mmcblk0p29 ram0 ram4
loop1 mmcblk0p11 mmcblk0p20 mmcblk0p3 ram1 ram5
loop2 mmcblk0p12 mmcblk0p21 mmcblk0p4 ram10 ram6
loop3 mmcblk0p13 mmcblk0p22 mmcblk0p5 ram11 ram7
loop4 mmcblk0p14 mmcblk0p23 mmcblk0p6 ram12 ram8
loop5 mmcblk0p15 mmcblk0p24 mmcblk0p7 ram13 ram9
loop6 mmcblk0p16 mmcblk0p25 mmcblk0p8 ram14
loop7 mmcblk0p17 mmcblk0p26 mmcblk0p9 ram15
mmcblk0 mmcblk0p18 mmcblk0p27 mmcblk0rpmb ram2
~ # 

i have the same problem.
i get this:#
C:\Users\mcse\Desktop\hammerhead-m4b30z-factory-625c027b\hammerhead-m4b30z>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
~ # ls /dev/block
bootdevice mmcblk0p1 mmcblk0p19 mmcblk0p28 platform ram3
loop0 mmcblk0p10 mmcblk0p2 mmcblk0p29 ram0 ram4
loop1 mmcblk0p11 mmcblk0p20 mmcblk0p3 ram1 ram5
loop2 mmcblk0p12 mmcblk0p21 mmcblk0p4 ram10 ram6
loop3 mmcblk0p13 mmcblk0p22 mmcblk0p5 ram11 ram7
loop4 mmcblk0p14 mmcblk0p23 mmcblk0p6 ram12 ram8
loop5 mmcblk0p15 mmcblk0p24 mmcblk0p7 ram13 ram9
loop6 mmcblk0p16 mmcblk0p25 mmcblk0p8 ram14
loop7 mmcblk0p17 mmcblk0p26 mmcblk0p9 ram15
mmcblk0 mmcblk0p18 mmcblk0p27 mmcblk0rpmb ram2
~ # 

its showing up like this

How to root the Honor 8?

I've been reading through many threads on the subject, and it seems that we still don't have a reliable way to root this phone.
Is there any word yet on a TWRP build? Are there any viable alternatives to TWRP?
I'm really starting to miss some of the apps I use that require root.

There are very reliable methods that work..
Just look within this forum.

Where? Pretty sure I've read through every thread on the subject, and all the options are half-baked in one way or another; no backup, designed for a different model, reports of bootloops, messed up file systems, etc.
Can you point me to a verifiably functioning technique for my FRD-L04?

xichael said:
Where? Pretty sure I've read through every thread on the subject, and all the options are half-baked in one way or another; no backup, designed for a different model, reports of bootloops, messed up file systems, etc.
Can you point me to a verifiably functioning technique for my FRD-L04?
Click to expand...
Click to collapse
Root doesn't differ from model variants. It's not perfect but works most of the time.

xichael said:
Where? Pretty sure I've read through every thread on the subject, and all the options are half-baked in one way or another; no backup, designed for a different model, reports of bootloops, messed up file systems, etc.
Can you point me to a verifiably functioning technique for my FRD-L04?
Click to expand...
Click to collapse
Nothing bad will happen if you do the steps right. Head over to the bootloader unlock thread.

I'm not taking any chances. To quote from another thread:
evilpaul13 said:
The SuperSU's not the problem it's nobody's made a working TWRP for FRD-L04. I've seen lots of people who tried the Mondaco TWRP on L04 say they just got a bootloop with one guy saying it worked, but he couldn't make a backup and just install the root package.
Click to expand...
Click to collapse

Try philz touch recovery or other cwm recovery for rooting honor 8
xichael said:
I've been reading through many threads on the subject, and it seems that we still don't have a reliable way to root this phone.
Is there any word yet on a TWRP build? Are there any viable alternatives to TWRP?
I'm really starting to miss some of the apps I use that require root.
Click to expand...
Click to collapse

I am also hesitant to do this on my brand new L04. What are the steps to download and flash the stock ROM for this specific model in case it is bricked? I have not found anything about this yet.

I'd very much like to be able to root, but everything I've read makes it look less than promising at the moment. Honor has the B122 firmware from September on their site: http://www.hihonor.com/us/support/details/index.html?DOC_ID=89264
I'm running B150 though which I got OTA and don't really want to go back to an older version with broken auto-brightness if things don't go right. I had B144 when I got the thing.

So the initial release firmware is available for the L04? I guess we can flash it with Hisuite?
If we want to get TWRP working on L04 we need to send partition mount info to the developer that made TWRP work on the other Honor 8 models. I am not sure who that person would be. I have attached the info I am able to get without root. We may need `cat /proc/mtd`. But this virtual device can only be read by root. If anyone has working root on L04 please post here and share with TWRP developer for Honor 8.
Code:
1|[email protected]:/ $ cat /proc/partitions
major minor #blocks name
253 0 524288 zram0
179 0 30535680 mmcblk0
179 1 256 mmcblk0p1
179 2 256 mmcblk0p2
179 3 256 mmcblk0p3
179 4 768 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 6144 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 14336 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 65536 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 24576 mmcblk0p21
179 22 65536 mmcblk0p22
179 23 65536 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 16384 mmcblk0p26
179 27 12288 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 65536 mmcblk0p30
179 31 65536 mmcblk0p31
179 32 16384 mmcblk0p32
179 33 8192 mmcblk0p33
179 34 16384 mmcblk0p34
179 35 65536 mmcblk0p35
179 36 262144 mmcblk0p36
179 37 2048 mmcblk0p37
179 38 2048 mmcblk0p38
179 39 3670016 mmcblk0p39
179 40 524288 mmcblk0p40
179 41 4096 mmcblk0p41
179 42 25255936 mmcblk0p42
179 96 4096 mmcblk0rpmb
179 48 4096 mmcblk0boot0
179 144 61259776 mmcblk1
179 145 61258752 mmcblk1p1
252 0 3641084 dm-0
252 1 520124 dm-1
252 2 25255920 dm-2
[email protected]:/ $ mount
rootfs / rootfs ro,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1869360k,nr_inodes=467340,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,ionice,cpu 0 0
none /dev/cpuset cgroup rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
none /dev/frz cgroup rw,relatime,freezer 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=750,gid=1000 0 0
none /sys/fs/cgroup/pids cgroup rw,relatime,pids 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,seclabel,relatime,gid=1000,mode=755 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=755,gid=1000 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/dev/block/vold/public:179:145 /mnt/media_rw/1EF6-36FE exfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,iocharset=utf8,namecase=0,errors=remount-ro 0 0
/dev/fuse /mnt/runtime/default/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/dm-1 /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/splash2 /splash2 ext4 rw,context=u:object_r:splash2_data_file:s0,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/3rdmodem /3rdmodem ext4 ro,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/3rdmodemnvm /3rdmodemnvm ext4 rw,context=u:object_r:radio_data_file:s0,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/3rdmodemnvmbkp /3rdmodemnvmbkp ext4 rw,context=u:object_r:radio_data_file:s0,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/secure_storage /sec_storage ext4 rw,context=u:object_r:teecd_data_file:s0,nosuid,nodev,noatime,discard,nodelalloc,data=journal 0 0
/dev/block/bootdevice/by-name/modemnvm_img /mnvm2:0 ext4 rw,context=u:object_r:modem_nv_file:s0,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/modem_om /modem_log ext4 rw,context=u:object_r:modem_log_file:s0,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/dm-2 /data f2fs rw,seclabel,nosuid,nodev,noatime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,extent_cache,active_logs=6 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=755,gid=1000 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/dev/fuse /storage/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/self tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=755,gid=1000 0 0
[email protected]:/ $

Tk has a video. Watch it.

kevev said:
I am also hesitant to do this on my brand new L04. What are the steps to download and flash the stock ROM for this specific model in case it is bricked? I have not found anything about this yet.
Click to expand...
Click to collapse
It's pretty much like any Huawei. And I think the worst case is bootloop, except if you flash some other's model recovery or system.
Download stock full OTA
Extract boot.img, recovery.img, cust.img and system.img from update.app file with Huawei firmware extractor.
To go back to stock just flash boot and recovery partitions.

kevev said:
...we need to send partition mount info to the developer that made TWRP work on the other Honor 8 models. I am not sure who that person would be...
Click to expand...
Click to collapse
Here's the thread where it was originally posted: http://www.modaco.com/forums/topic/377647-twrp-recovery-3020-for-honor-8/
Here's the dev's xda acct: http://forum.xda-developers.com/member.php?u=220328

xichael said:
Here's the thread where it was originally posted: http://www.modaco.com/forums/topic/377647-twrp-recovery-3020-for-honor-8/
Here's the dev's xda acct: http://forum.xda-developers.com/member.php?u=220328
Click to expand...
Click to collapse
Thanks. I sent the dev a PM earlier today on XDA. No preply yet. I am not able to register on modaco. I never receive the registration email. Could someone ping him there for me?
Sent from my FRD-L04 using XDA Free mobile app

kevev said:
Thanks. I sent the dev a PM earlier today on XDA. No preply yet. I am not able to register on modaco. I never receive the registration email. Could someone ping him there for me?
Click to expand...
Click to collapse
Done!

Tmobilefan906 said:
Done!
Click to expand...
Click to collapse
Appreciated
Sent from my FRD-L04 using XDA Free mobile app

So there's finally a working copy of TWRP for the Honor 8: https://twrp.me/devices/huaweihonor8.html
And fortunately the backup/restore feature works properly, as I needed it after UPDATE-SuperSU-v2.46.zip threw my phone into a bootloop.
Is there a different SuperSU zip I could try flashing?
EDIT:
Found the current v2.78, which worked fine: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Google's top results were pointing to the old version on chainfire.eu. Shoulda checked here first...

xichael said:
So there's finally a working copy of TWRP for the Honor 8: https://twrp.me/devices/huaweihonor8.html
And fortunately the backup/restore feature works properly, as I needed it after UPDATE-SuperSU-v2.46.zip threw my phone into a bootloop.
Is there a different SuperSU zip I could try flashing?
Click to expand...
Click to collapse
46 is outdated. Try 78. If it's still giving you bootloop, try phh's SU.
Sent from my honor 5X using XDA Labs

GensTattu said:
I want somebody can help me finished it, it is too difficult for me .
Click to expand...
Click to collapse
What step are you on?