2014-09-02, 18:15
(2014-09-02, 17:42)aus9 Wrote:Code:./unpack-MT65xx.pl recovery-850.img
MTK-Tools by Bruno Martins
MT65xx unpack script (last update: 27-01-2013)
Valid Android signature found...
Input file information:
Kernel size: 3419448 bytes / load address: 0x10008000
Ramdisk size: 1499179 bytes / load address: 0x11000000
Second stage size: 0 bytes / load address: 0x10f00000
Page size: 2048 bytes
ASCIIZ product name: ''
Command line: (none)
Kernel written to 'recovery-850.img-kernel.img'
Ramdisk size: 4432 blocks
Extracted ramdisk contents to directory 'recovery-850.img-ramdisk'
Successfully unpacked kernel and ramdisk.
first I post the recovery.fstab in your CWM
then I will explain why its wrong
Quote:# mount point fstype device [device2]
/misc emmc /dev/misc
/data ext4 /dev/block/mmcblk0p8
/system ext4 /dev/block/mmcblk0p6
/cache ext4 /dev/block/mmcblk0p7
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
#################
###############################################################
###############################################################
###############################################################
###############################################################
A) we already know you have no sdcard and no external slot to take an external sdcard
b) my dev blocks differ from yours so I will need but no rush to guide you on how to install the first apk
if phone boots....go into system settings -> security and allow unknown sources
(it may be a box you tick)
2) see if you can move the term.apk onto your storage then disconnect cable
pull down notification bar and un-check enable usb storage
leave usb debugging on
use file manager to get to internal storage and click on apk and it should now offer option to install
3) open terminal and run this command just to see if list command exists
and report backCode:ls
4) lets pretend it works i need you to photograph the following command unless you want to use adb
Code:cat /proc/dumchar_info
(and)
cat /proc/mounts
5) the first one is so I can ensure my rebuild does not exist your hex value of recovery size
b) the second one is to align the recovery.fstab to your system mounts
mounts means where Android can read information
ok peeking into ramdisk we find next error
Quote:write /sys/class/android_usb/android0/idVendor 18D1
write /sys/class/android_usb/android0/idProduct D001
this is not the ids of lenovo but of google
that means the russian ROM was a port.
grrrr
2) In windows does usbdeview show you the ids of your device?
idVendor should show as 17ef
Done all that. ls gives the attached screenshot.