[X]Assistant

[S * k]

пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅ MTK6739

download

Development of kernels and firmware for devices on the MTK platform пїЅ | Self-compiled kernel from source пїЅ | Assembly instructions for ANDROID from sources пїЅ | Porting firmware to MTK6580 / MTK8321 пїЅ | Porting firmware to MTK6735 / 53, 6750 пїЅ | Development and porting of GSI-firmware В»

Device or OS, firmware:Android OS 8.x.x - 9.x.x
I propose to combine efforts to address issues of porting to the aforementioned processor.

If a forum member gave good advice that helped in solving your problem, do not post a message with the text “Thank! You are super!!!". On our forum, it is customary to express gratitude by raising the reputation of a particular participant.

Useful programs

• Android ROM Tool- for working with firmware images
• Unpacker System + Vendor- unpacking, building .img, .dat, .br
• New Unpacker System + Vendor- unpacking, building .img, .dat, .br
• The program for finding dependencies lib files Android
• Beyond Compare Pro- a program to compare files
• Batch ApkTool- a program for editing resources
• Imgxtractor- program for unpacking system.img
• Carliv Image Kitchen- disassembly / assembly of boot.img and recovery.img
• LogoBuilder- a program for editing logo.img / logo.bin
• A utility for finding lib and bin dependencies
• Update Script Generate 18.6 Alpha- to create updater-script (update.zip).

Instructions

• Bootloader unlocking
• Debug firmware with Logcat
• Instructions for cross-android 8.1-9
  
• How to start not working Wi-Fi on Android 9
• Correction method for offline charging
• Patch offline charging
• If Magisk Manager does not issue permissions.
  

Donors

• List of smartphones on MT6739
• List of System Images (GSI)
• ARM64 A:
  1. Neffos C9
  2. Meizu V8 (M8) Lite
  3. ZTE Blade A530
  4. Huawei Y5 Prime 2018
  5. UMIDIGI A3
  6. UMIDIGI A1 Pro
  7. Oukitel C11 Pro
  8. Vernee T3 Pro
  9. Lenovo A5
  10. MIUI V10.1 MT6765
• ARM A:
  1. Alcatel 3
  2. Leagoo Power 2 Pro
  3. Oukitel C12 Pro
  4. Elephone A4
  5. Black fox b7
     
• SYSTEM AS ROOT:
  1. Doogee Y8 for twrp
  2. Doogee Y8 - Pie
• sGSI MTKfrommdeejay(ARM64 A):
  1. AOSP
  2. AOSP + gapps
  3. AOSP-GSI
  
  

When porting - do not forget to specify the source or author of the firmware.

For questions about filling the topic caps - contactQMS- to the curatorandrey.medwe - indicating the name of the topic

Post has been editedandrey.medwe - 18.05.19, 09:34

Reason for editing: If Magisk Manager does not issue permissions

[Petrovich72]

Most of the instructions from these topics are:
Instructions for editing system resources
Porting firmware to MTK6580 / MTK8321
Porting firmware for smartphones based on Mediatek 6735/53 processors
They will work with us, on MT6739 and Android 8-9

[S * k]

Petrovich72,
The theme is created in order not to jump on a related topic, it will be useful for beginners. and we still have a different core.

[S * k]

Unlocking the bootloader.

Unlocking the bootloader is needed to install third-party recovery and firmware.

1. Turn on "Factory Unlock" in the "For Developers" settings by activating them (by pressing the "Build Number" menu several times)

Screen Unlock

2. Install drivers MTK_Driver_Auto_Installer_SP_Drivers_20160804.exe(8.87 MB)

3. We connect the device and activate it in the "For Developers" settings "Debug USB". If a message appears about debugging permission, we tick the option to always enable and allow.

4. Unpack platform-tools.zip(2.4 MB)

Attention! After unlocking the bootloader, all data will be deleted (excluding the sd card)

4.1. Run 1-reboot-bootloader.cmd, the device should reboot in fastboot mode

4.2. We launch 2-unlock.cmd, we will be prompted to unlock the device by pressing the key Vol +

4.3. After successful unlocking, we write a command to the console fastboot reboot or reboot the device by holding the Power button

You can check unlocking in the "For Developers" settings.

EVERYTHING YOU DO WITH YOUR DEVICE, YOU DO AT YOUR OWN RISK!
DO NOT FORGET PRO BACKUP!

[mishadulev]

Instructions for cross-reference Android 8.1.0

Requirements

1. Stock firmware
2. System.img from stock firmware. Unpack it, you can useAndroid ROM Tool.
3. Boot.img from the stock firmware, which can be unpacked by the programCarliv Image Kitchen for Android.
4. System.img and Boot.img of the ported firmware (It is desirable that the firmware was for TWRP, so it is easier to port ...).
5. The kernel version of the stock firmware, must match the port.
6. In some cases, you will need a stock Vendor.img, which you can open withAndroid ROM Tool

Training

1. DownloadMagisk Manager
2. After installing and running, drop a kernel image (boot.img) from the stock firmware on the phone. In Magisk, click on the first "Install" button and select "Patch the kernel image (boot.img). After you have specified the path to the kernel and patch it, we throw our patched Boot back onto the PC.
3. Disassemble Boot patched by Magick and Boot portable firmware by the Carliv Image Kitchen program. How to disassemble ? Very simple! See the topicCarliv Image Kitchen for Android.
4. Unpack the System.img stock and portable firmware programAndroid ROM Tool

Work with boot.img

1. Take Kernel from stock Boot.img and throw ported firmware in Boot.
2. Putting it together and renaming it ... You need to remove the date and "-" to get "boot.img", or just "boot" if the display of file extensions is disabled in Windows ... We throw our rebuilt boot.img to the root of the archive portable firmware and agree to a replacement. With Booth all!

What files need to be replaced?

Vendor

Attention! First try to run the firmware without editing vendor. If there are bugs - then we sort and edit the vendor, but in most cases, this is not necessary!

- Sound:
/ vendor / lib / hw /
audio.primary.default.so
audio.primary.mt6739.so
- notification indicator:
/ vendor / lib / hw /
lights.mt6739.so
- Sensors:
/ vendor / lib / hw /
sensors.mt6739.so
- Cameras and flashlight:
As usual in previous versions of Android
/ vendor / lib /
lib3a.so
libcam.paramsmgr.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libfeatureio.so
libfeatureiodrv.so
In principle, from the main edits in the vendor, everything.

System

- Recent menu, on Hard Buttons
/ system / usr // keylayout /
generic.kl
- fix animation battery charging in the off state
/ system / lib /
libshowlogo.so
Well, as if to start everything ...

If the firmware does not start

/vendor/etc/fstab.mt6739 - change, or reduce to stock. After that, the firmware should start !!!

Post has been editedmishadulev - 28.02.19, 12:22

Reason for editing: Changed something ...

[S * k]

Petrovich72, It's about turning on root in the port firmware.

[mishadulev]

S * K @ 02.26.19, 15:15

This is about enabling root in the port firmware.

Aah, then yes ... Not everyone knows how to do it ...

[andrey.medwe]

[email protected], 22:24

Instructions for cross-reference Android 8.1.0

You yourself tried to run it on it?
P.SOr something I did not understand - what is it for? If vendor in a separate way - then run on the left vendor? Or instructions for those - who vendor in the system? Then it is desirable to specify)

Post has been editedandrey.medwe - 27.02.19, 17:21

[mishadulev]

Andrey.medwe @ 02.27.19, 16:15

You yourself tried to run it on it?

Of course not! There is nothing to try on!) On the 8th bucket, I only have Redmi 5, and there Qalcomm ... However, in the same way I started 15 - 20 firmware on the 7th Android ... So, I understand what I'm talking about and what I write ...

[andrey.medwe]

[email protected], 21:21

on Android 7th ... So, I understand what I'm talking about and what I'm writing ...

Ie - vendor in the system and in a separate way - but what's the difference?

Posted on 02/27/2019 5:27 PM:

[email protected], 21:21

There is nothing to try

A body appeared on this kernel - 8.1. There are of course common moments with a 7 droid (from 6737 tons for example) - but it’s not all right)

[mishadulev]

Andrey.medwe @ 02.27.19, 16:23

Ie - vendor in the system and in a separate way - but what's the difference?

So I wrote: You can view the vendor using 7 - Zip ???

Andrey.medwe @ 02.27.19, 16:23

A body appeared on this kernel - 8.1. There are of course common moments with a 7 droid (from 6737 tons for example) - but it’s not all right)

So, what does not fit?) It’s just that now you need to work not with one way, but with two. That's the whole difference ...)

[andrey.medwe]

[email protected], 21:35

Now you just have to work not with one way, but with two. That's the whole difference ...)

or maybe try pens - and then write instructions? Vendor was not made for beauty alone - and what lives in it is not hard to find. And to run on the left - then something to change it - sadness. That is why he was carried out - that there would be no crap with the launch of the camera - the sound - communication, etc.

[Petrovich72]

[email protected], 22:24

Also, you will need a stock Vendor.img, which can be opened again with 7 - Zip.

Before writing such nonsense, it would not hurt to download at least one factory firmware from mt6739 and check!

Posted on 02/27/2019, 17:42:

What is this written instruction for, written by a theoretician and never tested?
I can write with the same success that it is possible to port firmware especially successfully in the full moon.
It is after these instructors that the bricks come out!

Post has been editedPetrovich72 - 27.02.19, 17:52

[andrey.medwe]

[email protected], 22:02

on the stock vendor, custom firmware is unlikely to be able to run ..

pieces 30 at least 6739 -here .

[andrey.medwe]

[email protected], 22:18

Yes, I would have ...., I would prove

Good advice - check with pens - then write. Usually he saves from such conversations - screenshots at least can be shown, etc. And so -wouldinterferes)

Post has been editedandrey.medwe - 27.02.19, 18:23

[andrey.medwe]

mishadulev
Running on a foreign vendor at 6739 is about (roughly) running on the left boot-kernel. And so on according to the instructions.

Post has been editedandrey.medwe - 27.02.19, 19:56

[kory-vadim]

mishadulev,
Sparse image naturally will not open with 7 zip, the raw image will open, only you can not change anything in it anyway. So either unpacking, editing and assembling an image, or mounting, editing, unmounting.

[S * k]

Android ROM Tool
Android ROM Tool is a powerful shell that combines several tools for working with firmware images
Android ROM Tool (Post VADER # 82468933)

[Your Sempai]

On which core do you have 9 android?

Post has been editedYour Sempai - 28.02.19, 10:24

[S * k]

Your Sempai, 4.4.95

[Alpos]

S * k
Do you need to rewrite the kernel for Android 9? 4.4.95