yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] split52:
adb shell ls /dev

BOOT

FM50AF

MJC

MTK_SMI

MT_pmic_adc_cali

RT_Monitor

Vcodec

__properties__

accdet

aed0

aed1

alarm

als_ps

ampc0

anc

android_adb

ashmem

binder

block

camera-fdvt

camera-isp

camera-sysram

ccci_aud

ccci_fs

ccci_imsa

ccci_imsc

ccci_imsdc

ccci_imsv

ccci_ioctl0

ccci_ioctl1

ccci_ioctl2

ccci_ioctl3

ccci_ioctl4

ccci_ipc_1220_0

ccci_ipc_2

ccci_md_log_ctrl

ccci_monitor

console

cpu_dma_latency

cpuctl

device-mapper

devmap

dummy_cam_cal

dummy_eeprom

eemcs_it

eemcs_lb_it

fm

full

fuse

gps

graphics

gsensor

gyroscope

hotknot

hwmsensor

input

ion

kd_camera_flashlight

kd_camera_hw

kd_camera_hw_bus2

kick_powerkey

kmsg

log

loop-control

m_acc_misc

m_alsps_misc

m_batch_misc

m_gyro_misc

m_mag_misc

md32

misc-sd

msensor

mt6605

mtfreqhopping

mtgpio

mtk-adc-cali

mtk-kpd

mtk_almk

mtk_cmdq

mtk_disp_mgr

mtk_sched

mtp_usb

network_latency

network_throughput

null

pmic_ftm

ppp

psaux

ptmx

pts

ptyp0

ptyp1

ptyp2

ptyp3

ptyp4

ptyp5

ptyp6

ptyp7

ptyp8

ptyp9

ptypa

ptypb

ptypc

ptypd

ptype

ptypf

pvr_sync

pvrsrvkm

radio

random

rtc0

sec

snapshot

snd

socket

stpant

stpbt

stpgps

stpwmt

sw_sync

tgt

touch

tpd_em_log

tty

ttyC0

ttyC1

ttyC2

ttyC3

ttyGS0

ttyGS1

ttyGS2

ttyGS3

ttyMT0

ttyMT1

ttyMT2

ttyMT3

ttyp0

ttyp1

ttyp2

ttyp3

ttyp4

ttyp5

ttyp6

ttyp7

ttyp8

ttyp9

ttypa

ttypb

ttypc

ttypd

ttype

ttypf

tun

uhid

uibc

uinput

urandom

usb_accessory

uvvp_hotplug

wmtWifi

wmtdetect

xLog

xt_qtaguid

zero

adb shell cat /sys/devices/platform/mtk-msdc.0/mmc_host and adb shell cat /sys/devices/platform/mtk-msdc.1/mmc_host

Microsoft Windows [Versión 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.

C:\Users\linde>adb shell cat /sys/devices/platform/mtk-msdc.0/mmc_host

/system/bin/sh: cat: /sys/devices/platform/mtk-msdc.0/mmc_host: Is a directory

Microsoft Windows [Versión 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.

C:\Users\linde>adb shell

root@vanzo95_lwt_ds_kk:/ # env | grep sdcard

env | grep sdcard

/system/bin/sh: env: not found

1|root@vanzo95_lwt_ds_kk:/ #
[Upgrading, Modifying and Unlocking] :
Well, I unpacked and repacked the recovery with bgcngm's tool and it worked, so that won't be a problem - the problem si only in windows with michfood's tool. With boot is something different which we have to find why repacked boot fails. Also I saw that the MTK header is still in place, so they didn't changed this thing, probably because the MTK basic platform for the phone is made this way (it requires that MTK header to works).

So, I'll try to build a recovery to see if it works. I created already the device tree, and I have to tune some things. Thanks to Lihis I've got almost everything I need now.

Cheers!
[Upgrading, Modifying and Unlocking] marsapa:
well, if you need to let me know, because I'm too tired to recompile the system I miss aroma installer;)
[Upgrading, Modifying and Unlocking] ghost45:
Hi Sorry for my Delay but i wasn't at home!

P:\ANDROID\zp999\MtkDroidTools-253>adb shell ls /dev
BOOT
FM50AF
MJC
MTK_SMI
MT_pmic_adc_cali
RT_Monitor
Vcodec
__properties__
accdet
aed0
aed1
alarm
als_ps
ampc0
anc
android_adb
ashmem
binder
block
camera-fdvt
camera-isp
camera-sysram
ccci_aud
ccci_fs
ccci_imsa
ccci_imsc
ccci_imsdc
ccci_imsv
ccci_ioctl0
ccci_ioctl1
ccci_ioctl2
ccci_ioctl3
ccci_ioctl4
ccci_ipc_1220_0
ccci_ipc_2
ccci_md_log_ctrl
ccci_monitor
console
cpu_dma_latency
cpuctl
device-mapper
devmap
dummy_cam_cal
dummy_eeprom
eemcs_it
eemcs_lb_it
fm
full
fuse
gps
graphics
gsensor
gyroscope
hotknot
hwmsensor
input
ion
kd_camera_flashlight
kd_camera_hw
kd_camera_hw_bus2
kick_powerkey
kmsg
log
loop-control
m_acc_misc
m_alsps_misc
m_batch_misc
m_gyro_misc
m_mag_misc
md32
misc-sd
msensor
mt6605
mtfreqhopping
mtgpio
mtk-adc-cali
mtk-kpd
mtk_almk
mtk_cmdq
mtk_disp_mgr
mtk_sched
mtp_usb
network_latency
network_throughput
null
pmic_ftm
ppp
psaux
ptmx
pts
ptyp0
ptyp1
ptyp2
ptyp3
ptyp4
ptyp5
ptyp6
ptyp7
ptyp8
ptyp9
ptypa
ptypb
ptypc
ptypd
ptype
ptypf
pvr_sync
pvrsrvkm
radio
random
rtc0
sec
snapshot
snd
socket
stpant
stpbt
stpgps
stpwmt
sw_sync
tgt
touch
tpd_em_log
tty
ttyC0
ttyC1
ttyC2
ttyC3
ttyGS0
ttyGS1
ttyGS2
ttyGS3
ttyMT0
ttyMT1
ttyMT2
ttyMT3
ttyp0
ttyp1
ttyp2
ttyp3
ttyp4
ttyp5
ttyp6
ttyp7
ttyp8
ttyp9
ttypa
ttypb
ttypc
ttypd
ttype
ttypf
tun
uhid
uibc
uinput
urandom
usb_accessory
uvvp_hotplug
wmtWifi
wmtdetect
xLog
xt_qtaguid
zero

P:\ANDROID\zp999\MtkDroidTools-253>

P:\ANDROID\zp999\MtkDroidTools-253>adb shell cat /sys/devices/platform/mtk-msdc.
1/mmc_host
/system/bin/sh: cat: /sys/devices/platform/mtk-msdc.1/mmc_host: Is a directory

P:\ANDROID\zp999\MtkDroidTools-253>adb shell ls /sys/devices/platform/mtk-msdc.1
/mmc_host
mmc1

P:\ANDROID\zp999\MtkDroidTools-253>adb shell ls /sys/devices/platform/mtk-msdc.1
/mmc_host/mmc1
device
mmc1:0001
power
subsystem
uevent

P:\ANDROID\zp999\MtkDroidTools-253>adb shell cat /sys/devices/platform/mtk-msdc.
1/mmc_host
/system/bin/sh: cat: /sys/devices/platform/mtk-msdc.1/mmc_host: Is a directory

P:\ANDROID\zp999\MtkDroidTools-253>adb shell ls /sys/devices/platform/mtk-msdc.0
/mmc_host
mmc0

P:\ANDROID\zp999\MtkDroidTools-253>adb shell ls /sys/devices/platform/mtk-msdc.0
/mmc_host/mmc0
device
mmc0:0001
power
subsystem
uevent

P:\ANDROID\zp999\MtkDroidTools-253>env | grep sdcard
"env" non è riconosciuto come comando interno o esterno,
un programma eseguibile o un file batch.

P:\ANDROID\zp999\MtkDroidTools-253>
[Upgrading, Modifying and Unlocking] bigrammy:
:laugh: A little late to the party bro. :laugh:

Well it seem's things are moving along nicely and hopefully :fingers-crossed: we can get to the bottom of the problems encountered with this SoC a special thanks to [MENTION=5186178]carliv[/MENTION] for his time spent on a phone he don't even own and also thanks to [MENTION=4729462]marsapa[/MENTION] for modding and rooting the system in the first instance :good:

[MENTION=4729462]marsapa[/MENTION] you can see my post here http://xdaforums.com/showpost.php?p=57682948&postcount=65 regarding michfoods boot/recovery tools for windows. It seem's the ram_disk(Cpio) gets corrupted slightly when packed to the ram_disk.gz :eek:

The problem is with gzip I think :confused: links and images are in the post.

[MENTION=5186178]carliv[/MENTION] New 64bit SoC mt6732 should we stay away from it for now? :laugh:

Merry Christmas to All at Xda

Regards bigrammy.
[Upgrading, Modifying and Unlocking] ghost45:
This is one screeshot of what happen when in actual recovery stock someone try to install one zip files..... And when someone try to make a backup. :)
[Upgrading, Modifying and Unlocking] yuweng:
Come to know this thread when bigrammy mentioned my name, a little free over the holiday, sharing my findings as below . . . :cool:

Found out Zopo999 uses different address & also uses ASCIIZ product name too. Further googling found this, donno if this is one of the reason it doesn't boot . . .

PM 4 users only 2 response with one carrying out tests, Thanks to split52, recovery doesn't boot so further digging found out the differences between MT6592 & MT6595 though both are OctaCores !

Hopefully these findings will speed up development or may even halt development until cm repo supports ARM's big.LITTLE, idk . . . :o

Having said that, i've seen TARGET_2ND_CPU_VARIANT but then again, its for 64bit SoC & may not be suitable for big.LITTLE, idk . . . :cowboy:
[Upgrading, Modifying and Unlocking] mrjavum:
I found today the right way for packing/unpacking boot.img and recovery.img for Lenovo X2 (MT6595M).

I found the same thing that X2 images differ from older MTK images by another offsets, addresses and board name.

My own scrpts, michfood scripts and bruno scripts can't pack images correctly for my phone.

So there is the correct data for X2:

BOARD_KERNEL_CMDLINE
BOARD_KERNEL_BASE 40000000
BOARD_NAME X2-EU_ROW_S121_
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 04000000
BOARD_TAGS_OFFSET 0e000000

BOARD_NAME does nothing - phone boots well without it. The main things are BOARD_KERNEL_BASE, BOARD_KERNEL_OFFSET, BOARD_RAMDISK_OFFSET and BOARD_TAGS_OFFSET.

Using this command I have packed boot.img and recovery.img which boots well:

./mkbootimg --kernel ./kernel --ramdisk ./ramdisk_new --board X2-EU_ROW_S121_ --base 0x40000000 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x04000000 --tags_offset 0x0e000000 -o ./new_recovery.img
[Upgrading, Modifying and Unlocking] ghost45:
Hi,

Good news... Post these two new test boot and recovery i would like to test it.

See you
[Upgrading, Modifying and Unlocking] marsapa:
but you know that the boot of the 999 you can open and close to change simply using dsixda kitchen?
[Upgrading, Modifying and Unlocking] :
mrjavum is right. Using his findings the boot can be packed back correct.

In this image first command is for unpack my repacked boot img and in second is the stock unaltered:

These can't be done yet with bgcngm's tool, but if we add mkbootimg arguments to command line it will work. For now only the manual command will work:

./mkbootimg --kernel kernel --ramdisk ramdisk --board 1418885616 --base 0x40000000 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x04000000 --tags_offset 0x0e000000 -o new_boot.img

I added these to BoardConfig and today, maybe a little bit later I will post the built recoveries (TWRP and CTR) for test. I will upload the device folder also on github for you to take it and continue to work on it. These is all I can do without seeing even the device :)

I attached here the repacked boot image with security turned off in default.prop. Maybe someone can test it to see if this time works.
[Upgrading, Modifying and Unlocking] marsapa:
OK, now i test

edit:

ok it works, Now try the recovery TWRP or cwm
[Upgrading, Modifying and Unlocking] ghost45:
You are welcome!
[Upgrading, Modifying and Unlocking] :
So, until I wait for the recovery to build, let's share the info from this images, to complete mrjavum info.

As you can see, they are the same for both phones (Zopo ZP999 and Lenovo X2), but anyway they share same CPU (6595M):

.........
++ /bin/busybox sed 's/ //g'
+ [COLOR="Red"]base[/COLOR]_addr=[COLOR="Red"]0x40000000[/COLOR]
++ od -A n -D -j 36 -N 4 boot.img
+ [COLOR="Red"]page_size[/COLOR]=2048
++ od -A n --strings -j 64 -N 512 boot.img
+ [COLOR="Red"]cmd_line[/COLOR]=
+ [COLOR="Red"]kernel_offset[/COLOR]=32768 => [COLOR="Red"]0x00008000[/COLOR]
+ [COLOR="Red"]ramdisk_offset[/COLOR]=67108864 => [COLOR="Red"]0x04000000[/COLOR]
+ second_offset=15728640 => 0x00F00000
+ [COLOR="Red"]tags_offset[/COLOR]=234881024 => [COLOR="Red"]0x0E000000[/COLOR]
.........

Great to see you here [MENTION=4893922]codelover[/MENTION]. Thank you for all your support :highfive:
[Upgrading, Modifying and Unlocking] SevenMaxs:
Hello everyone!

I apologize for the bad english.

I also compile recovery (TWRP) for Lenovo Vibe X2.

But it does not boot.

But that's not all: I also compiled the recovery (CWM/TWRP) for Lenovo Vibe Z2 (msm8916), and it also does not boot, but I was able to adjust work only adb (At this time, the display shows the Splash picture.).

I have a assumption: that either the kernel version 3.10.xx or source recovery are not compatible at this monent with cortex-17, cortex-53, cortex-57...
[Upgrading, Modifying and Unlocking] ghost45:
Hi Great friend,

Welcome here!
[Upgrading, Modifying and Unlocking] SevenMaxs:
Glad to see you here, as well mrjavum and marsapa.

Now I, too, in case. :highfive:
[Upgrading, Modifying and Unlocking] marsapa:
Hello seven, unity is strength
[Upgrading, Modifying and Unlocking] :
For recovery we will have to wait a little (I'm building four versions - 3 TWRP and 1 CTR).

But I want to test something. Besides codelover's tests, can someone tests these attached images? I want to see which one of those offsets are mandatory for the boot image to work. I need to narrow down the thing and maybe to think a method to integrate it in bgcngm's script.

For those who want to test them, just post here the result like this:

boot_test_1 - ok or fail

boot_test_2 - ok or fail

etc,

Thanks!

The images for test are here: http://xdaforums.com/showpost.php?p=57759458&postcount=103

PS: Can someone tell me where is the path for lunfile for this phone? Or to check if it is the same with this:

/sys/devices/virtual/android_usb/android0/f_mass_storage/lun%d/file

?
[Upgrading, Modifying and Unlocking] ghost45:
Hi to everyone,

I'm very happy to see all of You here to try to resolve these mistakes of this new phone!
[Upgrading, Modifying and Unlocking] marsapa:
Now i test

edit:

I tested it on my rom

boot1: part of the logo and then goes into the loop;

boot2: part of the logo and then goes into the loop;

boot3: white screen;

boot4: white screen
[Upgrading, Modifying and Unlocking] :
Ok, so all have to be in place, even board name (ASCIIZ "1418885768") .... That will match "ro.build.date.utc=1418885768" from ROM build prop for board name. But probably if you use uboot, and modded boot and recovery from same build it will work.
[Upgrading, Modifying and Unlocking] :
Ah, I did such a stupid mistake :silly:

Sorry [MENTION=4729462]marsapa[/MENTION] but those tests are not concludent. I forgot to append MTK header to ramdisk, so that's the reason all failed.

Can you or somebody else to test again?

Here are all: http://ge.tt/49kUmU72?c

And please someone tell me the right lunfile path for this phone.
[Upgrading, Modifying and Unlocking] coldhurricane:
carliv,

As I understand,

/sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file

This path exists in root explorer
[Upgrading, Modifying and Unlocking] marsapa:
boot1: it's ok

boot2:it's ok;

boot3: black screen and loop

boot4: black screen and loop

boot4: black screen and loop
[Upgrading, Modifying and Unlocking] ghost45:
This path exist not in lun folder... Butin:

/sys/devices/virtual/android_usb/android0/f_mass_storage/

In this position there are :

Power (folder) .. But is empty

Bicr (file)

Device (file)

Inquiry_string (file)

Lun (file)

Subsystem (file)

Uevent( file)
[Upgrading, Modifying and Unlocking] SevenMaxs:
[IMG="LunFile"]http://dl-1.va.us.xda-developers.com/3/0/8/2/7/0/3/Screenshot_2014-11-12-18-44-02.jpg?key=YtoCaLwT0Sz0y-wan_9lZg&ts=1419608645[/IMG]

Partition:

ls -l /dev/block/platform/mtk-msdc.0/by-name/
lrwxrwxrwx root root 2014-11-13 00:55 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-13 00:55 cache -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-11-13 00:55 expdb -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-11-13 00:55 flashinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-11-13 00:55 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-11-13 00:55 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-11-13 00:55 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-13 00:55 para -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-11-13 00:55 preload -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-11-13 00:55 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-13 00:55 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-13 00:55 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-13 00:55 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-13 00:55 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-13 00:55 secro -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-11-13 00:55 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-11-13 00:55 userdata -> /dev/block/mmcblk0p16
[Upgrading, Modifying and Unlocking] :
Ok, then this one exists:

/sys/devices/platform/mt_usb/musb-hdrc.0/gadget/lun%d/file

?

Thanks [MENTION=4729462]marsapa[/MENTION]. It's ok, now I know. Except board name or ASCIIZ. everything has to be there.

---------- Post added at 17:50 ---------- Previous post was at 17:45 ----------

Ah, that's it! thank you very much SevenMaxs. That was the right one:

/sys/devices/platform/musb-mtu3d/musb-hdrc/gadget/lun%d/file

In CTR and CWM isn't used anymore, but for TWRP 2.7 it is.
[Upgrading, Modifying and Unlocking] bigrammy:
Wow!!!! I go to work come home and look what happens :D

It's great to see all these MTK devs together again. :victory:

It's Like the good old days :cowboy:

Thanks All.
[Upgrading, Modifying and Unlocking] :
Ok, finally the built recoveries.

After many tries and builds - I worked all day - I ended up with two builds:

- linked again in this post: http://xdaforums.com/showpost.php?p=57764613&postcount=112

Both are packed properly, as you can see here (this is after the build process finished):

+ base_addr=0x40000000
+ cmd_line=
+ kernel_offset=32768 => 0x00008000
+ ramdisk_offset=67108864 => 0x04000000
+ second_offset=15728640 => 0x00F00000
+ tags_offset=234881024 => 0x0E000000

I set the args on BoardConfig, and so there is no need to unpack and repack with right offsets:

BOARD_MKBOOTIMG_ARGS := --base 0x40000000 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x04000000 --tags_offset 0x0e000000

So, they should boot at least, but if there are some fine tunings to apply (in init files or fstabs - things I can't do without the phone), here is the device folder tree: https://github.com/carliv/device_zopo_zp999

You can start with this guys and take it further. ;)
[Upgrading, Modifying and Unlocking] marsapa:
I feel at once both recovery

edit:

unfortunately black screen on all 2 recovery
[Upgrading, Modifying and Unlocking] :
Arghh, that's bad.

I repacked again both this time with board name too.

check my post from next page: http://xdaforums.com/showpost.php?p=57773296&postcount=126
[Upgrading, Modifying and Unlocking] marsapa:
do not start, basically if I do reboot in recovery stops at the logo, then restarts and the part s.o., non white o black screen stop in logo and after reboot
[Upgrading, Modifying and Unlocking] :
I understand... I can't see now where's the problem... Maybe someone who has the phone can take my device folder and try it to solve this issue. I am sorry I couldn't do more to help you guys. :(
[Upgrading, Modifying and Unlocking] marsapa:
I try to see, someone else has ideas?
[Upgrading, Modifying and Unlocking] codelover:
see... told ya you will have to solve the recovery restriction first, the repacking & builds are not the source problem.

It's better to start with stock recovery first, because i don't think you can boot a custom recovery if the modded stock recovery is not even booting...

It's time to dig deeper into the boot contents, probably something is stopping it from booting into modded recovery.

So, anyone willing to try my recommendation here?

[MENTION=5186178]carliv[/MENTION], i was thinking to flash the CWM/TWRP .img to BOOT just to test it out, what do you think? Might need to repack ramdisk header as rootfs tho.

And thank you very much for your efforts! I am out of thanks for today but you well deserved it :good:, now go take some good rest!

Btw, can i use your ported recoveries as base & port it to other device? or these are for MT6595 only?

Tomorrow i will try to see if i can get some free time to write some 'backdoor' and utilize the OTA recovery update method to install custom recovery.

But for now i am more interested to see if it can be done with SPFT only, anyone can try? If the stock recovery_nomod.img works you can replace it with CWM/TWRP.

Regards.
[Upgrading, Modifying and Unlocking] split52:
buy a 999 and send to carliv;), i dont have any idea, one week working with this recovery and no way, whte screen, black screen etc and nothing, thanks carliv for your work, sometimes reading your thread, my brain works:o, but recovery does not help;),but i cant solve this issue for the moment:silly:
[Upgrading, Modifying and Unlocking] ghost45:
Hi Code,

the recovery _nomod works!
[Upgrading, Modifying and Unlocking] marsapa:
at least 999 have a rom, for lenovo and MX4 not, however, sooner or later we succeed : D
[Upgrading, Modifying and Unlocking] ghost45:
Sure at 100%!;)
[Upgrading, Modifying and Unlocking] :
:laugh: I'm out of thanks for today too!

Well, the repacked stock recovery worked without those offsets args, at least that ghost45 told me. Only for boot was a problem. Now with mrjavum findings, the boot works but the built recovery don't. Hm, I didn't tried to post the recoveries unpacked and repacked with bgcngm's tool and without offsets args, but I don't think that is the problem. It may have something to do with init files from root. I couldn't check them well, because it needs a phone for that. For example when I developed version 3.0 for kitkat I started with 4 init files in root (usb, protect, ssd, init) and now I'm using only one, the init.rc; but that is something to do working on device. So, if you have it you may try this too. My device folder is on github already.

These recoveries for zp999 are not ported. I built them especially for it and I don't think they will work for other phones..., maybe TWRP, but CTR won't (it doesn't have board_has_mtk enabled since this phone has defined blocks for nand partitions). I built today over 12 recoveries, but I shared only those two because those are the most close to a good one - even if they don't work now.

To flash recovery on boot? that's an interesting ideea, but I don't think it will work.

Cheers mate! :good:
[Upgrading, Modifying and Unlocking] bigrammy:
:confused:

Hi [MENTION=5186178]carliv[/MENTION]

I dont wish to interfere bro but I notice the BoardConfig.mk in your git is for Cortex 7 and the mt6595 is both

MediaTek MT6595 2.2 GHz quad-core Cortex-A17	1.7 GHz quad-core Cortex-A7	PowerVR G6200 (600 MHz)	32-bit dual-channel 933 MHz LPDDR3 (14.9 GB/sec)

as [MENTION=4478781]yuweng[/MENTION] suggest in his post Here maybe you need to add TARGET_2ND_CPU_VARIANT for the Cortex-A17 cores

Please refer to his post for details.

Just thinking out loud but maybe the boot uses one core set and the recovery uses the other. :confused:

I will shut up now as this is now well above my Pay Grade :laugh: :laugh:
[Upgrading, Modifying and Unlocking] :
Ah yes, if you build a boot image or full ROM those can be set. I created only a skeleton of the device folder. But for recovery won't matter. Those are important if you build the kernel and are mandatory for a 64 bit build (not the case here), but I used a prebuilt kernel. The non-booting issue is not related to this.

I saw on google android source how they are defined for lollipop:

TARGET_2ND_ARCH := arm
TARGET_2ND_ARCH_VARIANT := armv7-a-neon
TARGET_2ND_CPU_VARIANT := cortex-a17
TARGET_2ND_CPU_ABI := armeabi-v7a
TARGET_2ND_CPU_ABI2 := armeabi

If you want I can add them to BoardConfig to see it won't make any difference.

Cheers!
[Upgrading, Modifying and Unlocking] yuweng:
Thank you so much Master Shifu [MENTION=4268134]mrjavum[/MENTION] for sharing your insight . . . Different timezone, so much progress, one mystery solved, one more to go . . . :cool:

Owners of the new MT6595/ M/ T interested to further develop Factory ROM backup for MT6595 can contact me in PM . . . :cowboy:

Once i've prepare all the data, i'll pass you my findings BUT no n00bs & newbies pls, for DEVs ONLY . . . :cool:

Master Shifu rua1 has been MIA for almost half a year now, i've actually contacted him in both private here & also private/ forum at china-iphone but no response, i really hope everything is o.k with him . . . :fingers-crossed:

Been hacking MTK Droid Tools since then & found out how it works on my old faithful MT6577. . . its like that, when we've been spoon feed all these while, we never bothered but once spoon feeding stops then only we'll start looking for solutions though still looking forward to his updated version that suppports latest MTK SoC . . . :fingers-crossed:
[Upgrading, Modifying and Unlocking] SevenMaxs:
I've tried it, this does not work. :crying:
[Upgrading, Modifying and Unlocking] :
Ok guys, one more try from me.

I keep thinking last night why doesn't boot and I decided to make one more try.

This time I repacked the stock recovery also, for control, one version with mrjavum's offsets and one just repacked with bgcngm's tool.

Also, for both recoveries I made two tests each. So here they are:

stock + offsets

stock no offsets

TWRP 1

TWRP 2

CTR 1

CTR 2