2018-09-28, 18:07
(2018-09-28, 15:51)rauliordache Wrote: Hi everyone,
I have two OFFICIAL builds for my device:
- the first one, based on 3.10.65+ kernel, with Lollipop 5.1 and
- the second one, 3.18.35+ kernel, with Nougat 7.0
I want to port some ROMs with 3.10.65+ (because all ROMs with 3.18.35+ have some problems on my chipset, MTK6753: gps problems).
- The first build, has the bootloader locked, and in FastBoot, the volume-UP button doesn't work (for confirming the fastboot oem unlock). So, it cannot be unlocked for further mods.
- The second build can be unlocked (the bootloader) - and thus custom ROMs can be booted.
I have changed the partition names (in boot.img), and TWRP works great in flashing the new build (3.10.65+), but when booting, it stucks at logo.
Porting ROMs with the same kernel (3.18.35+) works great.
Porting ROMs with the 3.10.65+, even after changing the fstab, kernel (from stock 3.10.65+ boot.img) + partition layouts, cannot be booted. In addition, in the second case, I have changed from boot.img: - all occurrences of
/dev/block/platform/mtk-msdc0/... with
/dev/block/platform/mtk-msdc0/11230000-msdc0/... (fstab, .rc files, update-script, etc.) according with the newer partition layout.
I have tried just to do this with my stock official 5.1 3.10.65+ ROM. It doesn't work (with the preloader+lk.bin unlocked from 3.18)
The question is: Is it possible to have the second build flashed (which has another preloader + lk.bin) from 3.18.35+ - whos bootloader can be unlocked - , and then, using the files from the first build to port a ROM with kernel 3.10.65+ ? Or I am trying the "impossible" ?
In fact, I am not mixing "kernels" regarding boot.img. I am "mixing" a preloader+lk.bin (from one build, which runs Nougat, on 3.18.35+ kernel) with boot.img+system (based on 3.10.65+)
Thank you!
Hello,
In my view, you are trying the "impossible"
Artemisia (Eva Green) on "300: Rise of an Empire"