Lenovo s850 root (mtk6582/4.4.2)

[siewarner]

Actually it was this one thats installed now - [Only registered and activated users can see links Click here to register]

But that says its for the euro version and I assume since I got mine from pandawill china it must be the china version, not sure if its different in anyway?

[Athos]

OK, it looks like something went wrong with the formatting that flash tool did.
I'm just comparing this to mine.

Preloader - OK
MBR - OK
EBR1 - OK
PRO_INFO - you have type: NONE, should be NORMAL ROM
NVRAM - you have type: NONE, should be NORMAL ROM
PROTECT_F, PROTECT_S - you have type: NONE, I have ext4_img (I think yours should be Yaffs_img)
SECCFG - you have type: NONE, should be NORMAL ROM
UBOOT - OK
BOOTIMG - OK
RECOVERY - OK
SEC_RO - OK
MISC - you have type: NONE, should be NORMAL ROM
LOGO - OK
EBR2 - OK
EXPDB - you have type: NONE, should be NORMAL ROM
PRELOAD - you have type: NONE, I think this should also be Yaffs_img
ANDROID - OK
CACHE - OK
USRDATA - OK
BMTPOOL - you have type: NONE, should be NORMAL ROM

Your ANDROID, CACHE, and USRDATA are of type YAFFS_IMG
Could you check if the scatter file of the ROM you flashed have these formats.

I'm listing this here because I don't currently have an answer for you as to how to properly format each partition. Hopefully someone with experience with this can help out.

[siewarner]

I assume the scatter file is the one from the russian rom I linked to as my phone was not working before installing that so my original scatter has gone. I really could do with finding the same rom it came with but its not available

[Athos]

The one you attached is the one you made with Droid Tools, yes?
Yup, please cross check the types listed in the Russian ROM if they match the ones I listed as yours.
Hmm just check if the file system is really yaffs format, and if there are any NONE types. Although I think recent Android versions generally use ext4 file system?

[aus9]

edit

It seems internal partion table is corrupt. Cwm will not install anything as it will not mount internal sd.

Ok I can modify your CWM to adjust the recovery fstab file.

I need you to upload your CWM....that truly boots and I will edit it for you.

try at own risk of course....give me a link to it....such as available at file sharing sites like dropbox

2) In the meantime....can you see an option to mount emmc?
I am currently on CTR and will have to change to CWM to have a look

[siewarner]

[aus9]

ok I have unpacked CWM recovery and here is /etc/recovery.fstab

# mountpoint fstype device [device2]
/misc emmc /dev/misc
/data ext4 /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2

on repack I will remove last 2 lines

Notice emmc.....thats your internal storage

but if phone boots but you have no android terminal I will upload a APK as I need the output of your mounts area....

I need to match /dev/blocks

#################

I am guessing you can't get access to your internal storage thru windows?

we can use adb to push and install the apks onto your device

##############

download the terminal to your PC
[Only registered and activated users can see links Click here to register]
I will check out busybox later

[siewarner]

I am just installing a newer version of the rom which says it works in china version too so will see if any better.

Thing is I can access storage from the pc and some things copy to it fine and others such as root.zip fails saying its unplugged or unavailable. The rar of the same file copies which is strange?

I will see if apk files will copy and install once this flash has finished.

[aus9]

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

# 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

Code:

ls

and report back

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 eceed 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

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

[siewarner]

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

# 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

Code:

ls

and report back

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

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.