Mediatek MT8173 & MT8176 Development - Android General

Mediatek MT8173 & MT8176 development
Hi folks, after I've long been working on my device and only made little progress in building LineageOS for my Xiaomi Mi Pad 3 I decided to look for other developers with similar devices.
My Mi Pad 3 (codename: cappu) is a tablet based on a Mediatek MT8176 SoC. It was launched in April 2017. The tablet comes with a 7.9" display with a resolution of 2048 pixels by 1536 pixels at a PPI of 326 pixels per inch. It is powered by a 2.1GHz/1.7GHz Hexa Core processor ( 2 x 2.1GHz Cortex A72 + 4 x 1.7GHz Cortex A53 ) and it comes with 4GB of RAM. The tablet packs 64GB of internal storage that cannot be expanded. It was shipped out with Android 7.0 (Miui) and is still on this version).
Two months ago Xiaomi finally released Kernel Source Code for my device. It was broken, but I fixed most of the conflicts, streamed the kernel up to latest linux-stable and added some features. I also tried to build LineageOS & AOSP trees, but I have to admit, I'm starting to get desperate. For this specific SoC - even it's predecessor MT8173 - there is no activie development. And that is what I am looking for!
I collected some devices that either use MT8176 SoC, or the older MT8173 SoC. Some of them have Kernel Sources, which I listed and linked below.
All questions, requests for help, suggestions, ... are welcome. If you own any of the listed devices feel free to write and help. This thread is also on Reddit.
MT8176
Xiaomi Mi Pad 3
GPD XD+
Chuwi Hi9
Teclast Master T8
Teclast Master T10
Asus Zenpad 3S 10
Acer Iconia Tab 10 A3-A50
Alfawise Tab
MT8173
ALLDOCUBE Freer X9 (Cube Free X9 (U89))
HITSAN Onda V10 Pro
Pegasus JDTab J01
Acer Chromebook R13 CB5-312T-K8Z9
Amazon Fire HD 10 2017
Lenovo N23 Yoga
Lenovo Flex 11
Xiaomi Mi Box 3 2016
Amazon Fire TV (sloane)
Firmwares & Source-Code:
Chuwi Hi9
https://www.needrom.com/download/chuwi-hi9/ (Firmware)
Acer Iconia Tab 10 A3-A50
https://github.com/Goayandi/android_kernel_acer_titan
https://snlookup.com/acer-iconia-tab-10-a3-a50-tablet-p104780 (Firmware & Kernel-Source)
Xiaomi Mi Pad 3
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/cappu-n-oss (Kernel-Source)
https://github.com/Goayandi/android_kernel_xiaomi_cappu/tree/3.18.108 (Kernel-Source)
http://en.miui.com/a-234.html (Firmware)
https://multirom.me/index.php?m=app&a=view&id=81&app=roms (Firmware)
Teclast T10
https://www.needrom.com/download/teclast-t10-e3c5/ (Firmware)
Teclast T8
https://www.needrom.com/download/teclast-t8-e8c1/ (Firmware)
GPD XD+
https://github.com/Goayandi/android_kernel_mt8176_common (Kernel-Source)
https://github.com/skelton/android_kernel_mt8176_common (Kernel-Source)
https://droidbox.co.uk/how-to/flashing-gpd-xd-plus-firmware/ (Firmware)
http://www.gpd.hk/news.asp?id=1519&selectclassid=002002 (Firmware)
Asus Zenpad 3S 10
https://github.com/Goayandi/android_kernel_asus_z500m (Kernel-Source)
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Zenpad/Z500M/Z500M_V13_6_10_15_kernel.zip (Kernel-Source)
https://www.asus.com/us/Tablets/ASUS-ZenPad-3S-10-Z500M/HelpDesk_BIOS/ (Firmware)
Onda V10 Pro
https://www.needrom.com/download/onda-v10-pro/ (Firmware Android)
http://onda.cn/Tablet_Supports.aspx?id=371 (Firmware Phoenix OS)
http://onda.cn/Tablet_Supports.aspx?id=370 (Firmware Phoenix OS)
Pegasus JDtab J01
https://www.needrom.com/download/jdtab-j01/ (Firmware)
Amazon Fire TV 2015 (sloane)
https://github.com/Goayandi/android_kernel_amazon_sloane (Kernel-Source)
Amazon Fire HD 10 (7th Generation)
https://fireos-tablet-src.s3.amazon...PR/Fire-HD10_7th_Gen-5.3.6.2-20180315.tar.bz2 (Kernel-Source)
https://kindle-fire-updates.s3.amaz...wyB/update-kindle-40.6.0.5_user_605485120.bin (Firmware)
ALLDOCUBE Freer X9 (U89)
http://51cube.com/services?_search=U89 (Firmware)
https://www.leakite.com/2017/10/cube-stock-firmware.html (Firmware)

First thanks for your initiative! And I am very interested in obtaining a Custom ROM for my Teclast T10 E3C5 device with the aforementioned MTK8176 Chipset. I cannot help you with development but are open to test it and report bugs.

Hi Goayandi,
I'm not sure how many experienced ROM developers you will get. (I'm not one of them. I have compiled and modded existing ROMs, but never ported one.) I've heard several people say they will look into building a custom ROM for mt8163 or mt8173. But that's always as far as it gets. They never come back with any results. So I was just curious, what are you getting stuck on?
As far as I can tell, one major problem with porting to Mediatek is that they modify a lot of Google's OS code like frameworks and libraries. I do see that you already have some MTK customized repositories in your github library. You may have to do some reverse engineering of the stock ROM to confirm that the MTK changes are the same ones you have in your repos. Yes, that's a huge pain. It's also likely that MTK's patches for mt81xx and mt67xx, which is probably what you have, are pretty different.
One suggestion I want to make is to start out with a ROM that's as close to stock as possible. That means building a plain AOSP build NRD90M. This will reduce as many trouble-causing variables as possible. That's how I would do it. If you accomplish that, it will be easy to move on to higher Android versions or LineageOS, etc.
I would also use the prebuilt kernel for now. There is not much point to compiling your own for the same reason I just mentioned. A lot more variables would enter the equation. (Unless maybe you can test it independently with the stock FW.)

Any chances of giving TeamMAD access to one of these devices?

I have a Teclast T8 stuck in fastboot mode. No recovery, no system. adb cannot see the device. Is there a way to recover from that?

xivxivxiv said:
I have a Teclast T8 stuck in fastboot mode. No recovery, no system. adb cannot see the device. Is there a way to recover from that?
Click to expand...
Click to collapse
In T10 thread I have heard of same kind of issue. Disconnect battery (solder) or wait for device to die, then charge and it should be fine

BiG_FooT said:
In T10 thread I have heard of same kind of issue. Disconnect battery (solder) or wait for device to die, then charge and it should be fine
Click to expand...
Click to collapse
I tried that. That would work if recovery were bootlooping, and system were intact. In my case, my T8 cannot get to system. The Teclast Logo goes through its animation on startup, then gets stuck there. Holding volume up and power gives me 3 choices: recovery, fastboot, normal. Recovery and Normal are both broken. Fastboot is the only one I can do. How to recover from that?

xivxivxiv said:
I tried that. That would work if recovery were bootlooping, and system were intact. In my case, my T8 cannot get to system. The Teclast Logo goes through its animation on startup, then gets stuck there. Holding volume up and power gives me 3 choices: recovery, fastboot, normal. Recovery and Normal are both broken. Fastboot is the only one I can do. How to recover from that?
Click to expand...
Click to collapse
You need to reflash firmware/rom with the sp flash tool.

fastmix said:
You need to reflash firmware/rom with the sp flash tool.
Click to expand...
Click to collapse
You should flash stock firmware on your tablet with SPflash tools. Search for Mediatek SPflash + your device name in Google. Flash procedure should look like this:
FLASH Mediatek device
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT8173_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Download Only" or if upgrade "Firmware upgrade"
- Turn off your phone (and don't turn on the phone).
- Press “Download” button to start
- and connect your phone into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- You can now safely disconnect your phone and turn it on.
So you should look for your ROM/FIRMWARE and than flash it. Key step for you is to turn of the tablet, push download button in SPflash tools, and then connect USB to the tablet. Flash will then start!
But Google for instructions on how to use SPflash

Thank you, BiG_FooT and fastmix! Leaving it in power off state before SP flash was the missing step. I don't know how I missed that in previous Google searches. Fully working tablet now.
I now have two of these things. If you (or any others interested in developing this Mediatek) want me to use one of my Teclast T8s for testing for you, let me know.

Has anyone successfully flashed the firmware??
The system.img for all the ROMs is corrupt

Hi! I have an Alfawise Tab (rebranded JDTAB 01) with MT8173 chipset and android 6.0.
I managed to find the stock firmware and recovery, so i tried to port this TWRP recovery: https://forum.xda-developers.com/mi-pad/development/recovery-twrp-3-2-1-0-mi-pad-3-cappu-t3744185 unsuccessfully, maybe because of the different android versions(?)
I don't know....
Does anyone know how to port- build a custom recovery for these chipsets (mt8173-76)?
Or know if there is a working TWRP based on android 6.0 and these chipsets?

So, is there still any development? Where kernel-sources for Teclast devices can be found?

What an utter failure. Of both the manufacturers and the community.
It's fairly clear that the problem is hardware fragmentation. There is just too much diversity in Android hardware platforms, even too many different ARM-based CPUs, and too few users on many of those to justify a major development effort for any of them.
The moral of the story must be: if you want your tablet to remain useful for more than a couple of years, don't buy a cheap Chinese generic one made by a company that isn't a famous global brand. Stick to hardware that has sold in the millions.

ralphclark said:
What an utter failure. Of both the manufacturers and the community.
It's fairly clear that the problem is hardware fragmentation. There is just too much diversity in Android hardware platforms, even too many different ARM-based CPUs, and too few users on many of those to justify a major development effort for any of them.
The moral of the story must be: if you want your tablet to remain useful for more than a couple of years, don't buy a cheap Chinese generic one made by a company that isn't a famous global brand. Stick to hardware that has sold in the millions.
Click to expand...
Click to collapse
What we really need to do is reverse engineer a few roms already built for these chipsets, then see what they all have in common. This will help us figure out what needs to be done to the kernel, and what firmware we need.

Any news? Has anyone tried to flash GPD firmware on one of the other tablets with the same chipset? I have a Chuwi Hi9 with MTK 8173 and I would love to be able to change the ROM, the default one sucks big time. I actually bought it because it had the same chipset as one of the GPD devices.

Where To Start??
Goayandi said:
Mediatek MT8173 & MT8176 development
Click to expand...
Click to collapse
Hi,
If I were you I would start by having a really good look through the MTK_X20_BASE_AOSP open source code here https://github.com/archermind/MTK_X20_BASE_AOSP
In that you will find all the required mtk binary's and documented associated google dependency's and stock mtk app's needed. Dig through all the make files and compare your project_confg which should be in your system/data/misc on 6.0 and vendor/data/misc 7.0 with the one in that source to see whats built.
Because it's mediatek it's messy and things are all over the place but after days of reading it you can kinda start follow the rabbit eventually :laugh:
Take what you need and assemble it into a nice logical fashion using a experienced dev's work as a example and try a AOSP build if that works then try Lineage.
When you have things stable follow others who have stepped up in firmware version.
Most things should work if you have a working kernel.
Best place to start would be HERE it's invaluable :good:
There are other places and make's for BT WiFi GPS etc etc so ensure to explore it well.
Obviosly get the blobs from your own device if poss else pinch them form that source and give them a try it's all trial and error.
If I ever find the time I may join you one day to build a rom for the Lenovo Tab2 mt8165 please note most of these mt8xxxx have a equivalent mt67xx/mt65xx see my sig below for a example.
Good Luck and Happy building :fingers-crossed:

bigrammy said:
Hi,
If I were you I would start by having a really good look through the MTK_X20_BASE_AOSP open source code here https://github.com/archermind/MTK_X20_BASE_AOSP
In that you will find all the required mtk binary's and documented associated google dependency's and stock mtk app's needed. Dig through all the make files and compare your project_confg which should be in your system/data/misc on 6.0 and vendor/data/misc 7.0 with the one in that source to see whats built.
Because it's mediatek it's messy and things are all over the place but after days of reading it you can kinda start follow the rabbit eventually :laugh:
Take what you need and assemble it into a nice logical fashion using a experienced dev's work as a example and try a AOSP build if that works then try Lineage.
When you have things stable follow others who have stepped up in firmware version.
Most things should work if you have a working kernel.
Best place to start would be HERE it's invaluable :good:
There are other places and make's for BT WiFi GPS etc etc so ensure to explore it well.
Obviosly get the blobs from your own device if poss else pinch them form that source and give them a try it's all trial and error.
If I ever find the time I may join you one day to build a rom for the Lenovo Tab2 mt8165 please note most of these mt8xxxx have a equivalent mt67xx/mt65xx see my sig below for a example.
Good Luck and Happy building :fingers-crossed:
Click to expand...
Click to collapse
Hello!
Do I have a chance to do this with my teclast T8 device if I don't have even kernel-source code? For now I've ported most of firmwares different from my stock ROM (MIUI, ZenUI etc). But I would like to upgrade android version ( Nougat to Oreo) if it possible. Since not so long new device ( alldocube X) was released on same chipset (mt8176) with installed android Oreo, maybe this may help some way?

Sword900 said:
Hello!
Do I have a chance to do this with my teclast T8 device if I don't have even kernel-source code? For now I've ported most of firmwares different from my stock ROM (MIUI, ZenUI etc). But I would like to upgrade android version ( Nougat to Oreo) if it possible. Since not so long new device ( alldocube X) was released on same chipset (mt8176) with installed android Oreo, maybe this may help some way?
Click to expand...
Click to collapse
Hello To All
I have a Teclast M89 That I rooted with Magisk and have a working TWRP for backing up.
I am very interested in Testing Kernels and new Roms.I have already wiped and reflashed device a couple times -now Everything for testing,flashing, and booting has been verified.

@Goayandi
Just stopping by to say thanks for this, used some stuff from here for lineage-12.1 on Fire HD10
https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-12-1-t3953677

Related

[Q] "A9 NEC RENESAS EMMA V2 Dual Core Android 2.2 Tablet" review anyone?

Hi guys!
Since I didn't find any review to the "A9 NEC RENESAS EMMA V2 Dual Core Android 2.2 Tablet" offered in the (german) cect-shop, I was wondering whether someone already bought and tried it. Specs are quite nice, IMHO and videos on youtube look promising. Can someone share his experience with that tablet?
Thanks in advance.
Rena3 Reply
Hi,
I personally have the device and the experience so far has been good using the device.
There is a whole bunch of information over at slatedroid page where there is a group of active users.
Sorry but my post is very little so you have to head over at slatedroidpage, please replace the dots with "."
www dot statedroid dot com/forum/204-rena/
Perhaps someone wants to start a thread over at this page? Hopefully some XDA developer over here owns the device and we can get things started
overall the device has received 3 firmware upgrades so far and the community is hopeful for gingerbread to be released for this. We do have the kernel source codes for this product but do not have any developers to help us out with getting gingerbread out yet for this.
also replace statedroid with "slatedroid"
I also don't purchase this tablet, but i purchase flytouch 3 from a china site,called mcbub.com,i find they have the A9 NEC renesas tablet, here is some review in their site:
http://www.mcbub.com/customer-revie...GB-Bluetooth-HDMI-MID-black-CN101769--136318/
hope this can help you.
nullandvoid said:
Hi guys!
Since I didn't find any review to the "A9 NEC RENESAS EMMA V2 Dual Core Android 2.2 Tablet" offered in the (german) cect-shop, I was wondering whether someone already bought and tried it. Specs are quite nice, IMHO and videos on youtube look promising. Can someone share his experience with that tablet?
Thanks in advance.
Click to expand...
Click to collapse
There are a lot of discussions on A9 NEC RENESAS EMMA V2 Dual Core Android 2.2 Tablet at tabletrepublic forum too http://tabletrepublic.com/forum/cortex-a9-renesas-ev2/
full root for Rena 3
Greetings, comrades!
All the usual, lazy engine of progress. Tired of doing manually as rooting and rebuild the firmware for Rena, i am wrote a script that works like a flash, but flash itself is not working, just do it root! =)
Thus, the universal root for any firmware Rena 3:
Install:
Unzip all the files and qroot directory to root SD card.
Turn off the device.
Turn on, hold VOL+ POWER.
Wait until the message "Well done. Root complete."
Reboot device, enjoy.
The necessary files and directories:
install.sh
uImage4
ff4
cramfs4
sdboot.bin
uboot-sd.bin
and directory /qroot
NOTE!
The update does not repartition and reformat the partitions do not.
Is provided as is, no guarantees and responsibility.
Everything you do, you do at your own risk.
for download - depositfiles.com/files/gdx84ktmo

Custom Rom Needed For Kult Beyond

Hi Developers
I am buy a new phone it's name is Kult Beyond.
----------specifications----------
Phone - Kult Beyond
Ram - 3GB
Rom - 32GB
Screen - 5.2" IPS HD display
Network - 4G/3G/2G
Battery - 3000mAh
Android - Stock Nougat 7.0
Processor - MT6737 64bit Quad-core 1.25 GHz
GPU - Arm Mali-T720 MP1 650 MHz GPU
With Fingerprint scanner
-------------------------------------
I am not a Developer so i dont know about how to create TWRP and custom rom.
please make any MIUI 8 ported Rom and TWRP recovery for my device.
sorry for my English.
I need same for my kult beyound please somebody step up
Requesting the members to develope roms and recovery for my device
Greetings to one and all present here.Kindly develop some recoveries and roms for my device, ie kult beyond
This is sad.Looks like we made a huge mistake by taking this phone and look how lazy xda members are, they can't even a create a custom recovery for a phoneand they call themselves developers
Don't know about xda but we definitely had done wrong by purchasing it. Total bull****. I even got to know that this device won't get any more update for oreo. We will get stuck on 7.0 only
I also have the same phone.Have been using it for the past 10 months.It is a nice phone but It has some software-based bugs which I feel Developers here can fix -
1) Phone going to silent mode randomly
2) I have to switch on and off Airplane mode to make
Outgoing calls work
3) RAM Management is quite poor.Always above 2GB used,so it requires Optimization
4) Battery,even if it says 3000MaH,It acts like a 1000MaH.Lasts about 4 hours of screen-on time.Again,Down to Optimization I think.
I have contacted kULt about this but no fixes seem to be coming...They seem to completely ignore old Products and focussed on Marketing and new budget offerings.
Guide to root kult ambition
HIDDENSLAYER said:
I need same for my kult beyound please somebody step up
Click to expand...
Click to collapse
Can any one please provide a detailed guide on how to root kult ambition and install twrp on it..I would be grateful..
It runs on mtk 6737 chipset and has Android 7.0 os

[CHAT] HD10 (2017) - custom ROM brainstorming:

With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
GuyInDogSuit said:
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
Click to expand...
Click to collapse
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
I wouldn't mind even if the best ROM available is a 6.0 Marshmallow one. Anything that gives AOSP on a stable base for the Fire HD10 is going to be awesome.
DragonFire1024 said:
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Click to expand...
Click to collapse
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
They will likely need some patches to work with newer versions, but it's a good start I'd say.
It's the most recent version amazon has published.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Sent from my MotoG3 using XDA Labs
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
The one I have and provided is a source to 7.0. looks nicely stocked.
Sent from my MotoG3 using XDA Labs
bibikalka said:
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
Click to expand...
Click to collapse
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
I have fixed the upload, please use amonet-suez-v1.1.1.zip
DragonFire1024 said:
The one I have and provided is a source to 7.0. looks nicely stocked.
Click to expand...
Click to collapse
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
k4y0z said:
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
I have fixed the upload, please use amonet-suez-v1.1.1.zip
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
Click to expand...
Click to collapse
I'll provide a link in a few. Trying your fix now.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Rortiz2 said:
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
Click to expand...
Click to collapse
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
bibikalka said:
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
Click to expand...
Click to collapse
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
This is great news! I am eagerly awaiting more info about this AOSP ROM
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
ffstudios said:
This is great news! I am eagerly awaiting more info about this AOSP ROM
Click to expand...
Click to collapse
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
bibikalka said:
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
Click to expand...
Click to collapse
If my testing on ROMs caused my brick, we have to be careful. I've been testing and flashing test ROMs for months now and never bricked like this. I think I may know what happened and if I'm right, I'm not sure what effect if any this will have on flashing a rom. According to the fstab.mt8173 file in the root directory, the partitions we flash for a rom, aren't part of the EMMC: data, system, cache are all ext4. All other partitions are however EMMC. So if I recall correctly, I did list the system as EMMC in the build script, but did intend to remove it. I made a last minute adjustment to the script and didn't change that part though.
https://forum.xda-developers.com/showpost.php?p=78542898&postcount=618
Sent from my MotoG3 using XDA Labs
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
I too am willing to test. Just let me know and I'll be sure to wear my best testing pants. [emoji41]
Sent from my SM-G9650/DS running stang5litre Pie ROM
AOSP ROM TEST 1 (suez)
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: Removed
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Click to expand...
Click to collapse
Sounds good to me. Won't have a chance till later this afternoon/evening to give it a whirl, but when I do I'll definitely share my results and any information that may be useful. Thank you!
Sent from my SM-G9650/DS running stang5litre Pie ROM
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
...
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Click to expand...
Click to collapse
Which AOSP version is this? Could you try that Oreo Lineage stuff from @wangyiling at some point as well?
One of these days we'll have a ROM developer and a tester within the same person Too bad we've lost @DragonFire1024 since his tablet got bricked

Lenovo Tab 2 A7-20 Development Thread

I bought this tab in mid 2015 and it is showing its age. Wanted to see whats available for the device but couldn't find anything on this device although there is thread for A7-30 variant here.
These Lenovo Tabs have many variants with minor differences such as A7-10, A7-20, A7-30 all 7' ones and the 8" ones have A8 in their names. I have the A7-20F (F stands for Wifi only version, there is another with SIM facility whose identifier I don't remember right now) so most of the testing I will do with be applicable to this one.
I'm collating all available resources here since info on this old device is hard to come by. Ff there is anyone else who would like to join and may find useful later on. I'm new to android hacking so this may be slow on progress.
P.S: Links may contain software which is not tested/not working/unofficial/unstable software. Do not flash them without any backup plans for recovery if something goes wrong. This is a work-in-progress thread.
Known Issues:
1. The tab is reported to have ghost touch issues. Many have reported on the official forums. I myself am facing the same problem. Ghost touches are reported around the top edges where I also am seeing on my tab. People have reported updating drivers resolve it. I use the Partial Screen app as a workaround for the time being.
2. Some people have reported that the stock Lollipop ROM for this device is buggy. Will stay with stock Kitkit for the time being.
Hardware Specs:
Sources:
https://support.lenovo.com/in/en/downloads/ds104407
VCOM Drivers:
SPFlashtool
For flashing: https://spflashtools.com/
Recovery:
TWRP Recovery 2.8.7.0 for A7-20F: https://forums.lenovo.com/t5/Lenovo...P-2-8-7-0-for-Lenovo-Tab-2-A7-20F/m-p/2217156 Reported working here
OR
TWRP Recovery 2.8.7.0 for A7-20F: http://lenovo-forums.ru/topic/14955-lenovo-tab-2-a7-20-расширенный-twrp-recovery/. Reported working on Lenovo forms link here
ROMs
Stock 4.4.2: http://lenovo-forums.ru/topic/14573-lenovo-tab-2-a7-20-прошивка-t2-a7-20f-s08-150820-row/ Reported working here
Other Guides:
These guides may provide useful info on undesired outcomes, additional steps, results etc. which can help us plan for these in advance.
Links to working software for A7-20F at Lenovo forums: https://forums.lenovo.com/t5/Lenovo...2-A7-20F-T2-A7-20F-S08-150820-ROW/m-p/2216538
Guide with links to stock ROM for A7-20F: https://blogthetech.com/flash-file-lenovo-tab-2-a7-20f-firmware-download-stock-rom/
Guide using TWRP Recovery for A7-10: https://www.getdroidtips.com/twrp-recovery-lenovo-tab-2-a7-10f/
Guide using Philz CWM for A7-10: https://androidrootguide.com/2015/06/how-to-root-lenovo-tab-2-a7-10-and-install-cwm-recovery.html
Downgrading from Lolipop to Kitkat: https://forums.lenovo.com/t5/Lenovo...ade-from-buggy-Lollipop-to/m-p/2189574#M27033
Another guide on stock ROM intstalltion for A7-10F: https://www.getdroidtips.com/stock-rom-lenovo-tab-2-a7-10f/
Rooting guide for A7-20F: https://guideroot.net/lenovo-tab-2-a7-20-download-firmware-android-8-0-o/
Updated to Lollipop: https://www.youtube.com/watch?v=OiIH9D0Xxmo
Reserved for future use
Needed to upgrade my T2 A7 20f to Lollipop to continue running a specific app and tried a few different approaches with varying success. The CM12.1 ROM is under-done and full of problems and so is the T2 A7 10f stock ROM. There are screen rendering issues (poor quality) and battery charging issues. Seems that we really need to stick to a ROM based on the 20f to get decent functionality. After a lot of looking, found this link from Lenovo support:
A7-20F_USR_S000024_1605111428_MP1V1_BMAIN_ROW.rar
drive.google.com
This is version T2-A7-20F_USR_S000024_1605111428_MP1V1_BMAIN_ROW
ROW in China speak means Rest Of World i.e. not China version.
It downloads O.K and installs O.K using the included SPFlash tool.
Maybe useful to those still running this clunker?
Best if someone provides a more permanent home for this ROM before it disappears

tiny china phones soyes servo fosa melrose MEGA THREAD

Hello all!
First time poster, just getting into rom porting and android dev.
making this thread, due to the serious lack of information / boards about these tiny china phones that are flooding wish/aliexpress and are stuck on android 6.0/7.0.
I've tried to use a few different roms as ports (where i patch select files from etc/lib and all that good stuff) using a guide found here specifically for mtk chipsets. I've only tried x32 to x32 same SoC, and patching kernel from stock rom in. This was without any kernel changes, still patching in my 3.18.19+ kernel over mostly 7.1.2 roms built for 3.18.19. I'm guessing the + makes it completely different like mt6737 vs 6737t or 6737m.
My goal is to port an MTK kernel to my current device (soyes s10, mt6737m android 6.0 kernel 3.18.19+ 3/32gb model) that supports android 7.1.2. I've found what I believe to be an almost the same version device tree, and I have ubuntu and windows and am rather well versed in both.
I'm not sure how to discern the kernel version (linux ver) of this download, but my "custom build version" is looking very similar, alps-mp-m0.mp1-V2.84_bd6737m.35g.b.m0_P81.
I'm mainly wondering:
1. Who else has some of these tiny china phones (only band 41 us support!) melrose, ifosa, soyes, unbranded, etc? I've ported over TWRP for this device also if anyone is interested. root was simple enough with mtk-su. It flashes zips but it wont boot roms. it's TWRP 3.2.1.0 or 3.1.2.0 I'm not 100%.
1a) could my whole problem be solved by porting a newer version of TWRP for the device?
2. can I port newer kernel 3.18.35 from source above?
3.MTK's whack implementation of fast charging, PE+ 2.0 support for my mt6737, they send 15w (5v3a) motorola branded charging brick with phone. but it seems to charge at random rates, not fast charging. Not sure if it's even worth it to try and find a brick that is listed as MTK PE+ compatible. anybody have any advice there? it would be a dope phone if the fast charge was reliable. maybe I can mod the kernel to force enable it in the future.
4. why won't any of my ported roms boot? I can't find a modules folder in my stock fw's lib image(s) where it should be in order to port. are these maybe just located in the root of /lib and very specific files I have to cherry pick and port over? i'm thinking android -all modules = no booting. not really sure where i'm going wrong but it's a million questions in one so if you can answer any of them, please chime in
I forgot I can't post any links, but like I have links to stuff
Thanks guys, I've been lurking these forums for near a decade.
It's nice to meet all of you, looking forward to some good learning
Nick
Hi mate.
First off, I'm really sorry -but I can't answer any of your questions...
I'm looking at the Servo S10 for myself, though ; how did you go with everything -any progress?
Also, how is the battery life? Sounds like it's not a deal-breaker. Sorry again that this isn't an answer to your questions, but I'd appreciate the feedback.
-anew

Categories

Resources