Database Info

[Q] Mount 2nd Ext-partition from sd BEFORE init.rc proceeded

Hello,
i have a little problem. I want to mount a ext4-partition from my sdcard (it's the second partition, behind a fat32). Normally you can find that partition in /dev/block and mount that simply.
The challange is to do this before the init-process with the init.rc is running
The problem is (ls /dev/block):
Code:
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk1
mmcblk1p1
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9
As you can see, there is no 2nd partition on the sd. When the Android is fully loaded a mmcblk1p2 is also in this folder - the 2nd. partition.
I guess the vold-service organizes that, but i don't want to start the services.
So, how can i mount my ext4-partition?

Ok, i got it:
Code:
mknod -m 660 /dev/block/mypartition b 179 26
mount -t ext3 -o rw /dev/block/mypartition /myfolder
(179 26 = major minor from /proc/partitions)

[Q] Can't flash any image to restore recovery

Hi guys, I hope one guru here can help me to unbrick my TF300T.
Yesterday I unlock the tablet with the ASUS utility and flashed lastest TWRP. After that the tablet always boot into TWRP but it can't mount any partition. I was able to go to fastboot with adb reboot-bootloader and boot Android from the Android icon. Then I tried to flash ASUS stock image to system (fastboot -i 0x0b05 flash system blob) and now I can't get it to boot.
fastboot send the image but doesn't write it, I get no error, but the process is to fast and the tablet freeze after it:
Code:
./fastboot devices
015d262e0b20101a fastboot
sudo ./fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (5644 KB)...
OKAY [ 2.471s]
writing 'recovery'...
OKAY [ 3.162s]
finished. total time: 5.633s
./fastboot devices
???????????? fastboot
./fastboot reboot
rebooting... <------ freeze!
I'm able to go to adb shell, then I push the recovery image and tried to flash it with but with no luck:
Code:
./adb devices
List of devices attached
0123456789ABCDEF recovery
./adb push recovery.img /root
1327 KB/s (5779560 bytes in 4.250s)
./adb shell
~ # cd root
/root # ls -alh
drwx------ 2 root root 0 Apr 16 07:21 .
drwxr-xr-x 19 root root 0 Apr 16 07:21 ..
-rw-rw-rw- 1 root root 5.5M Apr 15 20:25 recovery.img
/root # flash_image recovery recovery.img
failed with error: -1
/root #
Please tell me that I doesn't send 420€ to trash...
PS: I used Ubuntu for all this stuff.

I have read some threads with similar problems and tried some of the solutions with no luck:
http://forum.xda-developers.com/showthread.php?p=32792384
http://forum.xda-developers.com/showthread.php?t=1916952
http://forum.xda-developers.com/showthread.php?t=2228447

jmsosso said:
I have read some threads with similar problems and tried some of the solutions with no luck:
http://forum.xda-developers.com/showthread.php?p=32792384
http://forum.xda-developers.com/showthread.php?t=1916952
http://forum.xda-developers.com/showthread.php?t=2228447
Click to expand...
Click to collapse
I think, we must spam mail asus to release new nvflash

jmsosso said:
Hi guys, I hope one guru here can help me to unbrick my TF300T.
Yesterday I unlock the tablet with the ASUS utility and flashed lastest TWRP. After that the tablet always boot into TWRP but it can't mount any partition. I was able to go to fastboot with adb reboot-bootloader and boot Android from the Android icon. Then I tried to flash ASUS stock image to system (fastboot -i 0x0b05 flash system blob) and now I can't get it to boot.
fastboot send the image but doesn't write it, I get no error, but the process is to fast and the tablet freeze after it:
Code:
./fastboot devices
015d262e0b20101afastboot
sudo ./fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (5644 KB)...
OKAY [ 2.471s]
writing 'recovery'...
OKAY [ 3.162s]
finished. total time: 5.633s
./fastboot devices
????????????fastboot
./fastboot reboot
rebooting... <------ freeze!
I'm able to go to adb shell, then I push the recovery image and tried to flash it with but with no luck:
Code:
./adb devices
List of devices attached
0123456789ABCDEFrecovery
./adb push recovery.img /root
1327 KB/s (5779560 bytes in 4.250s)
./adb shell
~ # cd root
/root # ls -alh
drwx------ 2 root root 0 Apr 16 07:21 .
drwxr-xr-x 19 root root 0 Apr 16 07:21 ..
-rw-rw-rw- 1 root root 5.5M Apr 15 20:25 recovery.img
/root # flash_image recovery recovery.img
failed with error: -1
/root #
Please tell me that I doesn't send 420€ to trash...
PS: I used Ubuntu for all this stuff.
Click to expand...
Click to collapse
OK, first of all, it sounds like you've updated to the 4.2.1 firmware and flashed a recovery for the 4.1.1 firmware. So, make sure that the new recovery you're flashing is the patched TWRP with -42 at the end of the name. It's not the newest TWRP. If you're trying to flash the same version of TWRP as before, you won't fix anything, if you can even get it to flash.
Second, when you're in ADB shell, what happens when, instead of using flash_image, you use
Code:
su
dd if=/root/recovery.img of=/dev/block/mmcblk0p4
?
The worst that can happen is that you get the same error. That's if flash_image uses dd to flash the recovery. Otherwise, there's a chance it could work. I say it's worth a try.
Putting the ILLA in KILLA since 1985
---------- Post added at 04:18 AM ---------- Previous post was at 04:14 AM ----------
If that doesn't work, try this guide: http://forum.xda-developers.com/showthread.php?p=40343188
Putting the ILLA in KILLA since 1985

EndlessDissent said:
OK, first of all, it sounds like you've updated to the 4.2.1 firmware and flashed a recovery for the 4.1.1 firmware. So, make sure that the new recovery you're flashing is the patched TWRP with -42 at the end of the name. It's not the newest TWRP. If you're trying to flash the same version of TWRP as before, you won't fix anything, if you can even get it to flash.
Second, when you're in ADB shell, what happens when, instead of using flash_image, you use
Code:
su
dd if=/root/recovery.img of=/dev/block/mmcblk0p4
?
The worst that can happen is that you get the same error. That's if flash_image uses dd to flash the recovery. Otherwise, there's a chance it could work. I say it's worth a try.
Click to expand...
Click to collapse
I downloaded openrecovery-twrp-2.4.4.0-tf300t-4.2.blob and renamed it to twrp.blob then:
Code:
./adb push twrp.blob /root
1328 KB/s (7680104 bytes in 5.644s)
./adb shell
~ # cd root
/root # ls
twrp.blob
/root # su
/sbin/sh: su: not found
/root # dd if=twrp.blob of=/dev/block/mmcblk0p4
15000+1 records in
15000+1 records out
7680104 bytes (7.3MB) copied, 0.091978 seconds, 79.6MB/s
/root # exit
./adb reboot
Then the tablet boot directly into TWRP 2.5.0.0, the version that I installed at the beginning
Latter I'll try the other suggestion. Thanks a lot!

There aren't any partition mounted at boot and I can't mount any manually. I think the problem is in /dev/block:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 486.8M 48.0K 486.8M 0% /dev
~ # cat /etc/fstab
/system ext4 rw
/cache ext4 rw
/external_sdcard vfat rw
/sd-ext ext4 rw
~ # mount -a
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /external_sdcard on vfat failed: No such file or directory
mount: mounting /sd-ext on ext4 failed: No such file or directory
~ # cd root
/root # mkdir test
/root # mount /dev/block/mmcblk0p4 test
mount: mounting /dev/block/mmcblk0p4 on test failed: No such file or directory
~ # ls -alh /dev/block/
drwxr-xr-x 2 root root 200 Apr 16 13:52 .
drwxr-xr-x 10 root root 2.1K Apr 16 13:53 ..
brw------- 1 root root 7, 0 Apr 16 13:52 loop0
brw------- 1 root root 7, 1 Apr 16 13:52 loop1
brw------- 1 root root 7, 2 Apr 16 13:52 loop2
brw------- 1 root root 7, 3 Apr 16 13:52 loop3
brw------- 1 root root 7, 4 Apr 16 13:52 loop4
brw------- 1 root root 7, 5 Apr 16 13:52 loop5
brw------- 1 root root 7, 6 Apr 16 13:52 loop6
brw------- 1 root root 7, 7 Apr 16 13:52 loop7
i just noticed of /proc/partitions is empty. Can anybody publish here a valid one? I don't know if just editing the file with the right values will solve my situation.

jmsosso said:
There aren't any partition mounted at boot and I can't mount any manually. I think the problem is in /dev/block:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 486.8M 48.0K 486.8M 0% /dev
~ # cat /etc/fstab
/system ext4 rw
/cache ext4 rw
/external_sdcard vfat rw
/sd-ext ext4 rw
~ # mount -a
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /external_sdcard on vfat failed: No such file or directory
mount: mounting /sd-ext on ext4 failed: No such file or directory
~ # cd root
/root # mkdir test
/root # mount /dev/block/mmcblk0p4 test
mount: mounting /dev/block/mmcblk0p4 on test failed: No such file or directory
~ # ls -alh /dev/block/
drwxr-xr-x 2 root root 200 Apr 16 13:52 .
drwxr-xr-x 10 root root 2.1K Apr 16 13:53 ..
brw------- 1 root root 7, 0 Apr 16 13:52 loop0
brw------- 1 root root 7, 1 Apr 16 13:52 loop1
brw------- 1 root root 7, 2 Apr 16 13:52 loop2
brw------- 1 root root 7, 3 Apr 16 13:52 loop3
brw------- 1 root root 7, 4 Apr 16 13:52 loop4
brw------- 1 root root 7, 5 Apr 16 13:52 loop5
brw------- 1 root root 7, 6 Apr 16 13:52 loop6
brw------- 1 root root 7, 7 Apr 16 13:52 loop7
i just noticed of /proc/partitions is empty. Can anybody publish here a valid one? I don't know if just editing the file with the right values will solve my situation.
Click to expand...
Click to collapse
Hmmm... I think it's interesting that dd seemed to successfully write the recovery and exited with no errors, but didn't actually write anything. Not sure what that means or how it could help, but that wasn't at all what I expected. I thought it would either error out or successfully flash your recovery. It obviously did neither.
As for your request, I hope this helps, though I'm not sure if editing the file will help much. I guess it's better than nothing.
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
7 0 6269 loop0
7 1 5229 loop1
7 2 41612 loop2
7 3 22901 loop3
7 4 9387 loop4
179 0 31039488 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 28924416 mmcblk0p8
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
254 0 6268 dm-0
254 1 5229 dm-1
254 2 41611 dm-2
254 3 22900 dm-3
254 4 9387 dm-4
[email protected]:/ $ ls -al /dev/block/
brw------- root root 254, 0 2013-04-14 03:40 dm-0
brw------- root root 254, 1 2013-04-14 03:40 dm-1
brw------- root root 254, 2 2013-04-14 03:40 dm-2
brw------- root root 254, 3 2013-04-14 03:40 dm-3
brw------- root root 254, 4 2013-04-14 03:40 dm-4
brw------- root root 7, 0 2013-04-14 03:36 loop0
brw------- root root 7, 1 2013-04-14 03:36 loop1
brw------- root root 7, 2 2013-04-14 03:36 loop2
brw------- root root 7, 3 2013-04-14 03:36 loop3
brw------- root root 7, 4 2013-04-14 03:36 loop4
brw------- root root 7, 5 2013-04-14 03:36 loop5
brw------- root root 7, 6 2013-04-14 03:36 loop6
brw------- root root 7, 7 2013-04-14 03:36 loop7
brw------- root root 179, 0 2013-04-14 03:36 mmcblk0
brw------- root root 179, 16 2013-04-14 03:36 mmcblk0boot0
brw------- root root 179, 32 2013-04-14 03:36 mmcblk0boot1
brw------- root root 179, 1 2013-04-14 03:36 mmcblk0p1
brw------- root root 179, 2 2013-04-14 03:36 mmcblk0p2
brw-rw---- root system 179, 3 2013-04-14 03:36 mmcblk0p3
brw-rw---- root system 179, 4 2013-04-14 03:36 mmcblk0p4
brw------- root root 179, 5 2013-04-14 03:36 mmcblk0p5
brw------- drm drm 179, 6 2013-04-14 03:36 mmcblk0p6
brw------- root root 179, 7 2013-04-14 03:36 mmcblk0p7
brw------- root root 179, 8 2013-04-14 03:36 mmcblk0p8
drwxr-xr-x root root 2013-04-14 03:36 platform
drwx------ root root 2013-04-14 03:36 vold
Good luck.
Putting the ILLA in KILLA since 1985
Edit: I almost forgot to mention that the guide I posted earlier uses fastboot, but theoretically you can do it with dd in ADB shell like you tried with the recovery. You'll need to know which partition is the bootloader, though, and substitute that in place of mmcblk0p4 in the dd command.

I was unable to modify the partitions file. I think that the problem is related to the new 4.2 encrypted file system:
http://forum.xda-developers.com/showthread.php?t=2180376

It is, and you're done.
In TWRP, there are no mmcblk devices, and so nothing to mount or mount to. Nothing to 'dd' to either.
In RCK, fastboot will lock the tablet trying to flash anything.
Nvflash won't help because you needed to use it BEFORE it was bricked.
There are likely lots of newly bricked TF300T's because of this.
Folks will say it's because you didn't read, but the directions on the Teamwin website will still result in a brick if they are followed after taking the 4.2.1 OTA update. In my case, I bricked mine in between the time TWRP 2.4.4.0 came out (I used the -JB release), and the time 2.4.4.0-4.2 was released - following those directions exactly. I'd imagine there is even more of this happening now that 2.5.0.0 was released (without a 4.2 compatible version), no change in the instructions on their website, and even more folks that have taken the 4.2.1 OTA update.

splashg said:
It is, and you're done.
In TWRP, there are no mmcblk devices, and so nothing to mount or mount to. Nothing to 'dd' to either.
In RCK, fastboot will lock the tablet trying to flash anything.
Nvflash won't help because you needed to use it BEFORE it was bricked.
There are likely lots of newly bricked TF300T's because of this.
Folks will say it's because you didn't read, but the directions on the Teamwin website will still result in a brick if they are followed after taking the 4.2.1 OTA update. In my case, I bricked mine in between the time TWRP 2.4.4.0 came out (I used the -JB release), and the time 2.4.4.0-4.2 was released - following those directions exactly. I'd imagine there is even more of this happening now that 2.5.0.0 was released (without a 4.2 compatible version), no change in the instructions on their website, and even more folks that have taken the 4.2.1 OTA update.
Click to expand...
Click to collapse
Oh my god! the worst of my nightmares :crying:
My error was, when reading a guide to flash TWRP, to go to the official website and download the latest -jb release and not to use the recommended one. As you said they must include some type of message at the download page.
After that, I was able to boot Android using ADB reboot, but then, trying to go back I flashed the official ASUS system partition. The result was that the command erased the working partition but doesn't flash nothing.
Now I think my better choice is to wait some time. If nobody found a solution then buy a motherboard at eBay and try to replace it.
Thanks for your support folks!
Best regards.

+1 for Asus
Wow, Asus fixed my tablet under warranty without any cost
I received it yesterday after it traveled from Spain (were I live) to Czech Republic and back in 14 days.
When I called to Asus I tell the guy at the phone that I brick the tabled trying to root. He told me that if the tablet was rooted and my answer was not. And he told me then that it's under warranty. :good:
So guys with the same problem, and with the tablet under warranty, try with Asus!
Best regards.

[Q] How to extract boot.img from Zopo C7 ( MTK6589T)

First how to find location of boot image in device? I want to take current boot image. Do modifications and later flash that boot image back to device.
I have searched correct block device and did some image files with dd command but they were not boot images. I tried with several tools.
Here is some listing from the phone with adb shell commands.
Code:
[email protected]:/proc # cat partitions
major minor #blocks name
179 0 30512256 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 1572864 mmcblk0p7
179 8 28077696 mmcblk0p8
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
Code:
[email protected]:/ # ls -l /emm*
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p7
[email protected]:/ #
Code:
[email protected]:/dev/block # ls -al
brw------- root root 7, 0 2014-03-12 12:54 loop0
brw------- root root 7, 1 2014-03-12 12:54 loop1
brw------- root root 7, 2 2014-03-12 12:54 loop2
brw------- root root 7, 3 2014-03-12 12:54 loop3
brw------- root root 7, 4 2014-03-12 12:54 loop4
brw------- root root 7, 5 2014-03-12 12:54 loop5
brw------- root root 7, 6 2014-03-12 12:54 loop6
brw------- root root 7, 7 2014-03-12 12:54 loop7
brw-rw---- root system 179, 0 2014-03-12 12:54 mmcblk0
brw------- root root 179, 32 2014-03-12 12:54 mmcblk0boot0
brw------- root root 179, 64 2014-03-12 12:54 mmcblk0boot1
brw------- root root 179, 1 2014-03-12 12:54 mmcblk0p1
brw-r----- root system 179, 2 2014-03-12 12:54 mmcblk0p2
brw------- root root 179, 3 2014-03-12 12:54 mmcblk0p3
brw------- root root 179, 4 2014-03-12 12:54 mmcblk0p4
brw------- root root 179, 5 2014-03-12 12:54 mmcblk0p5
brw------- root root 179, 6 2014-03-12 12:54 mmcblk0p6
brw------- root root 179, 7 2014-03-12 12:54 mmcblk0p7
brw------- root root 179, 8 2014-03-12 12:54 mmcblk0p8
drwxr-xr-x root root 2014-03-12 12:54 platform
[email protected]:/dev/block #
/dev/block/mmcblk0boot0 looked promising but I made image of it by by command dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot.img
But the image was not boot image.
Code:
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
[email protected] /data ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /storage/sdcard0 vfat rw,dirsync,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ #
I can make full image by dding /dev/block/mmcblk0 but it would be better to get the parts separately.
Is there easy way to find where the boot image is located?

I checked block device sizes
/dev/block/mmcblk0p8 is the internal flash area for user, about 28G. Boot image boot loader etc must be in mmcblk0p1 - mmcblk0p7
Size of the block devices
Code:
/dev/block/mmcblk0 31244550144
/dev/block/mmcblk0boot0 2097152
/dev/block/mmcblk0boot1 2097152
/dev/block/mmcblk0p1 1024
/dev/block/mmcblk0p2 10485760
/dev/block/mmcblk0p3 10485760
/dev/block/mmcblk0p4 6291456
/dev/block/mmcblk0p5 681574400
/dev/block/mmcblk0p6 132120576
/dev/block/mmcblk0p7 1610612736
/dev/block/mmcblk0p8 28751560704
/dev/block/mmcblk1 8178892800
I got these with script
Code:
#!/system/bin/sh
command="/sdcard/busybox blockdev --getsize64"
for f in /dev/block/mm*
do
result=`$command $f`
result="$f \t $result"
echo $result
done

Via Terminal Emulator:
"su
cat /proc/partitions"
When again other command: dd if=/dev/block/(boot_partition_which_showed under /proc/partitions) of=/sdcard/boot.img

Root your device and try MtkDroidTools.
Use MTK SP_Flash_tool to flash image back.

In proc partitions there were two boot related devices listed
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
I made images from both of those but there was nothing inside the images which looked like boot image.
I found that there is /dev/bootimage
Code:
[email protected]:/ # ls -l /dev/boo*
crw-r----- root system 234, 10 2013-01-01 06:30 bootimg
I made image from that. The image is 4.3G. Very large. Anyway I found bootimage inside that. Then I made another smaller one with
Code:
# dd if=/dev/bootimg of=/sdcard/testboot.img count=12000
I can unpack that image in linux with tool unpack-MT65xx.pl. I tried to repack the exact same files without modifying. But repacking the image with repack-MT65.pl generates file which is different.

cnexpat said:
Is there easy way to find where the boot image is located?
Click to expand...
Click to collapse
Looking for same

[Q] Stuck in Bootloader (cache does not mount)

I tried to install cyanogenmod (cm-11-20140504-SNAPSHOT-M6-m4.zip) and in the process I probably did something wrong
Any help is highly appreciated.
The header in the unlocked bootloader is:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.24.40e.00.26
Recovery can be easily flashed via
Code:
sudo fastboot flash recovery recovery-clockwork-touch-6.0.4.8-m4.img
After selecting "BOOTLOADER" > "RECOVERY", I get the error messages
Code:
ClockworkMod Recovery v6.0.4.8
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
After sideloading "adb sideload cm-11-20140504-SNAPSHOT-M6-m4.zip", I receive the following error messages
Code:
Restarting adbd...
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: File exists
Finding update package...
Opening update package...
Installing update...
symlink: some symlinks failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
If anybody can help me, that would be great. (Flashin the Nexus4 was so much more fun )

Ive not seen a cwm v6.0.4.8 for the Htc Mini (m4) i could be wrong?
either try flashing philz latest touch recovery v6.41.6 from here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m4
or twrp 2.7.0.8 from here http://mdmower.cmphys.com/twrp-m4/
these two support the new partition layout.

Braddison said:
Ive not seen a cwm v6.0.4.8 for the Htc Mini (m4) i could be wrong?
either try flashing philz latest touch recovery v6.41.6
or twrp 2.7.0.8
these two support the new partition layout.
Click to expand...
Click to collapse
With philz and twrp I get the same behaviour (warnings and errors).

Try changing the name of your recovery "recovery-clockwork-touch-6.0.4.8-m4.img" to just "recovery.img" (its easier and less chance of a typo)
then try this sudo fastboot flash recovery /path/to/recovery.img
hopefully that will give you a working recovery,if that fails do the same with a different recovery
hope that helps,cheers

Braddison said:
Try changing the name of your recovery "recovery-clockwork-touch-6.0.4.8-m4.img" to just "recovery.img" (its easier and less chance of a typo)
then try this sudo fastboot flash recovery /path/to/recovery.img
hopefully that will give you a working recovery,if that fails do the same with a different recovery
hope that helps,cheers
Click to expand...
Click to collapse
I am not sure why renaming the file would help, but I did anyway.
Still, I get the same errors.

Jini.Dough said:
I am not sure why renaming the file would help, but I did anyway.
Click to expand...
Click to collapse
as stated in previous post, it's for ease of use and less likely to make a spelling mistake causing things to go t*ts up
am thinking your partitions are messed up,

try used twrp1 2.7.0.8 recovery
Sent from my HTC One mini

did you tried OTG option inside of the twrp via OTG cable and usb flashdisc?

410eaL said:
try used twrp1 2.7.0.8 recovery
Click to expand...
Click to collapse
I am not sure if I do understand what you mean by twrp1. Do you have a link.
mypat said:
did you tried OTG option inside of the twrp via OTG cable and usb flashdisc?
Click to expand...
Click to collapse
No, I did not try this. I am not sure if I have an OTG cable.
Since mounting of cache seems the main problem, I tried to get some information about the partitions. Does anybody recognize if these partitions are OK or if I do have to apply some change here:
Code:
adb shell
~ # cat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 46080 mmcblk0p16
179 17 10240 mmcblk0p17
179 18 5120 mmcblk0p18
179 19 8190 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 28671 mmcblk0p21
179 22 1022 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 20480 mmcblk0p25
179 26 4 mmcblk0p26
179 27 256 mmcblk0p27
179 28 16 mmcblk0p28
179 29 1280 mmcblk0p29
179 30 64 mmcblk0p30
179 31 1448 mmcblk0p31
179 32 32767 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 16383 mmcblk0p34
179 35 2195455 mmcblk0p35
179 36 688127 mmcblk0p36
179 37 11927552 mmcblk0p37
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 399632 128 399504 0% /dev
tmpfs 399632 8 399624 0% /tmp
tmpfs 399632 0 399632 0% /storage
tmpfs 399632 0 399632 0% /mnt/secure
tmpfs 399632 0 399632 0% /mnt/fuse
~ # 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)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
To me it appears as if /cache does not even exist anymore. The recovery seems to be OK, since the selinuxfs is used for a sys-partition.
Braddison, do you know how to fix the partition?

Jini.Dough said:
Braddison, do you know how to fix the partition?
Click to expand...
Click to collapse
I’m afraid I don’t.
I would try the above recoveries ensuring that they are copied in your fastboot folder , and spelled exactly the same when flashing.
Then try a different rom other than CM , just to see if you can boot . can always flash cm at a later date from recovery.
Hopefully someone on here will come to the rescue.

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?