Related
Hey guys, We are going to try something new for our china phones - cyanogenmod.
But we need some more devs to get everything going.
For now we have:
-Github tree for Lenovo P700i(mediatek 6577, android 4.0.4, kernel 3.0.8)
-Lens_flare - original port author(may work with system folder and configs)
-some kernel source from other devices like liquid gallant
The main problem is getting adb to work that could help a lot on remaining development. For now even zygote not starting, but all partitions seems mounted successfully.
We need more devs (especially that could assemble working kernel for device), working with p700i may lead to following porting for other mtk devices, as sources are nearly the same.
good project
i am in... :laugh:
We've done our best to deliver robust and delicious custom roms to our device (even using andrea or some other work [which are great], but, well.. android is opensource in the end ).
We hope you could help us with cm development (mostly on kernel part).
At last it would be great to see some light in the mtk darkness..
Hi,
I'm trying to start working on CM for MTK6589 device. (Star S7589)
Kernel sources (for normal Android) can be found (has been released by Acer few weeks ago), but the biggest problem is the "device" folder.
I've written e-mails to few producers (ZOPO, Cubot, THL), and even that I've gotten replies from ZOPO and THL, they don't want to share anything, nor the kernel, nor any other sources.
If you'll get to something, please post it here, or pm me, and if I'd make any step I'll also keep you informed.
Maybe it would be a good idea to sign a petition to Lenovo to "open the source code for the device"? 4pda russian forum would participate in signing such petition. And I assume there will be much more other communities / forums where we can spread this information to join us!
There are two steps to do this:
1. What is a petition website preferrable for such action?
2. To prepare the text for the petition which would be technically correct and would cover all the aspects we are waiting from Lenovo.
Anyone to take responsibilities for any paragraph?
---------- Post added at 03:18 PM ---------- Previous post was at 02:50 PM ----------
dmplot said:
1. What is a petition website preferrable for such action?
Click to expand...
Click to collapse
As an example of petition I looked at the "Give us Ice Cream Sandwich for HTC Desire HD".
So, the petition site I think is chosen. It is http://www.ipetitions.com/
So, who will take care of technically correct statement for the petition?
There is one more issue: the channels for such information spread. As to my thoughts it might be:
1. xda developers (of course),
2. 4pda russian forum,
3. Lenovo russian forum,
4. Please propose more...
nice to see guys good if we get this working but any chance of mt6575 processors they are capable of running ics so cyanogenmod 9 ?
This is great, i´m a ZTE v970 MT6577 owner and love the idea. I have kernel for ZTE Grand X V970 already uploaded to github and download the android sources and CM to start building.
The problem is im not a dev or have any kind of formation so I dont know if Im doing rigth. But i will try
I build a cm from scratch to my htc wildfire but I just had to do the steps of the CM tutorials.
Sorry for my inglish
Good luck to you guys, i was lurking on XDA just to search for a few optimizations for my MTK6589 phone (HDC). This quadcore cpu is spreading like wildfire among chinese phones due to its low price, so hopefully you will get some good help for getting started.
i'am hopi will custom rom ICS for my phone lenovo a690 mtk 6575,rom512,ram512
Sent from my Lenovo A690 using xda app-developers app
Short update on the topic:
1. I've made working TWRP recovery for mine Star.
I had to rip it a bit (awfully small recovery partition), but it looks like it's 90-95% working, just without partitioning possibilities. (But backups/recovery of them fully works, as same as other TWRP functions, and offcourse it's all operated by touch.)
2. I've compiled CM10.1, but it doesn't start, so here there is really a lot of work in front.
hey guys I kinda ported cm7 on my mt6575 phone well I luckly got it booted up but only the thing was I was not able to go pass the lockscreen its some thing to do with some touch screen drivers only my power button worked any one know how to deal with the touch screen drivers ?
FenixxPl said:
Short update on the topic:
1. I've made working TWRP recovery for mine Star.
I had to rip it a bit (awfully small recovery partition), but it looks like it's 90-95% working, just without partitioning possibilities. (But backups/recovery of them fully works, as same as other TWRP functions, and offcourse it's all operated by touch.)
2. I've compiled CM10.1, but it doesn't start, so here there is really a lot of work in front.
Click to expand...
Click to collapse
Maybe its better to start with CM9 or CM10, since Mediatek (ours) does not support JellyBean 4.2 yet. So getting CM10 on it would be freaking hard.
I also have a mtk phone, i would like to run cyanogend on it one day, iam no developer, im just gonna sit back and watch good luck
LPCRJ™ - Congrats! That's something, I'd say that even something really big, because noone else had even got to that point.
If you can, please share your sources (device/vendor catalogues) on github, then we'll be able to help you more
nathan-96 - Mine has got JellyBean (4.2.1), that's why i try to port the CM10.1, also I'm not sure if kernel 3.4.5 will work with CM9 and I haven't got any other to work on.
Still, mine CM isn't even going past first boot screen, even using hints from Lenovo P700 sources.
FenixxPl said:
LPCRJ™ - Congrats! That's something, I'd say that even something really big, because noone else had even got to that point.
If you can, please share your sources (device/vendor catalogues) on github, then we'll be able to help you more
nathan-96 - Mine has got JellyBean (4.2.1), that's why i try to port the CM10.1, also I'm not sure if kernel 3.4.5 will work with CM9 and I haven't got any other to work on.
Still, mine CM isn't even going past first boot screen, even using hints from Lenovo P700 sources.
Click to expand...
Click to collapse
Sorry I thought you had the same mediatek processor as the op, but I read that you have one that, apperiantly, supports JellyBean 4.2. Its indeed a big step.
But we need Logcat's to see why its not passing bootscreen, because you might be closer than everyone's thinking right know.
Xolo Q800 / Fly IQ446 / Gionee GN708W Kernel
Hi friends, I was able to get my hands on the kernel for Xolo Q800 / Fly IQ446 / Gionee GN708W Kernel which are essentially the same phone. They run JB 4.2.1 today, though the kernel is based on 4.1.2. Will this suffice or do we need anything more to get CM working.
http://yadi.sk/d/-zrdnTk_4Iy7c
All these phones are Quadcore MT6589 1.2 GHz processors with 1 GB ram and 4 GB flash. And, roms of these phones can run on each other.
Thanks
amardeepsingh77 - You're my god!
There is literally everything in that source, the "device" catalogue, prebuilder scripts, complete kernel sources, it's kind of unbelieveable!
Now we are possible to really get to work, not just move in the dark
yo guys I was trying to port cm7 but I really wanted to port cm9 so I left porting cm7 because my phone is already running gingerbread here is a thread I found http://forum.xda-developers.com/showthread.php?t=2246892 he have actually ported cm9 to mt6575 processor phone though I don't have this phone but I think porting to other mtk phone might become easy using his ways I flashed it on my phone but I had a bootloop I try editing stuff but no success. thanks to PdroidAndroid
Google translate
Click to expand...
Click to collapse
It seems to me that for a start, and 9 will do.
For at least that is what I can bude customize.
Yes and no need for the device in 512 MB, 4.2.
Also, can anyone have an idea for $ agree to help?
Original
Click to expand...
Click to collapse
Мне кажется что для начала и 9 сойдёт.
Ибо хоть что то буде что можно будет кастомизировать.
Да и не нужен на девайсах в 512 мб ,4.2.
Также есть идея может кто за $ согласиться помочь?
Next update from the field:
However sources from amardeepsingh77 are awesome, it'll take a lot of time to succeed the build.
Our MTK devices can't be compiled like all others Android devices, because we can't simply use ./build/envsetup.sh, we've got to use makeMtk, and it's got a lot of annoying stuff.
Without that we can't build preloader, and without it I don't think any Cyan or other rom will work.
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
Hello...I'm trying to get Android working on an older tablet/laptop (Dell Venue 11 Pro i3). No matter which distro/version I try (and I've tried lots, both custom releases and the Android-x86 project), I always end up with no wif or bluetoothi. Android installs and runs no problem every time, but without connectivity...
I'm a newb with this but not with PC tech in general. I assume I am missing a fundamental step in how to install and configure/add wifi support but I can't find a comprehensive set of instructions or even some rough steps as to how I can add support for my wifi chip (Intel).
Can anyone point me to some good reading that will educate me on how to do this? (...or just tell me I'm SOL if it doesn't work after installing)
Thanks much. I've been trying to find this information for many days now for fear of it being something that's obvious to everyone else.
Kevin
hulakai said:
Hello...I'm trying to get Android working on an older tablet/laptop (Dell Venue 11 Pro i3). No matter which distro/version I try (and I've tried lots, both custom releases and the Android-x86 project), I always end up with no wif or bluetoothi. Android installs and runs no problem every time, but without connectivity...
I'm a newb with this but not with PC tech in general. I assume I am missing a fundamental step in how to install and configure/add wifi support but I can't find a comprehensive set of instructions or even some rough steps as to how I can add support for my wifi chip (Intel).
Can anyone point me to some good reading that will educate me on how to do this? (...or just tell me I'm SOL if it doesn't work after installing)
Thanks much. I've been trying to find this information for many days now for fear of it being something that's obvious to everyone else.
Kevin
Click to expand...
Click to collapse
You need to make sure that whatever OS you are installing has the correct OS and correct kernel that is built specifically for your device's model number. The kernel is what allows the software to use your hardware, kinda like drivers on PC, if the kernel isn't correct, your hardware doesn't work correctly, regardless of whether the OS works or not.
You need to be using your specific model number to find a compatible ROM/OS for your device.
What is your device's specific model number?
What android version are you trying to install?
Sent from my LGL84VL using Tapatalk
Droidriven said:
You need to make sure that whatever OS you are installing has the correct OS and correct kernel that is built specifically for your device's model number. The kernel is what allows the software to use your hardware, kinda like drivers on PC, if the kernel isn't correct, your hardware doesn't work correctly, regardless of whether the OS works or not.
You need to be using your specific model number to find a compatible ROM/OS for your device.
What is your device's specific model number?
What android version are you trying to install?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I realize now that I've posted in the wrong place....but I'm referring specifically to Android-x86 and the many variations out there (Remix, Prime, Android x86 Project, another whose name escapes me right now).
I've never seen hardware specific versions of Android x86, but I've always wondered if users need to recompile the kernel for their specific hardware...yet I've never seen that mentioned anywhere.
I don't think I have hardware that's super obscure. Dell Venue Pro 11 (7130 MS)...i3, Intel HD4000 graphics, Qualcomm/Atheros/Dell 1537 wifi/bt. The most recent version I tried was 8.1 from the Android-x86 project site. Each variation I try runs fine in every other way, but without connectivity.
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
Hi,
I am using a TCL 20Y, and it's UI is boring and also it runs android 11.
I want to experience the android 13 with a a custom rom like project elixir or ricedroid or pixelplus ui, so can anyone please let me know wheather I can do that.
Like most manufacturers TCL uses different chipsets in different models. I believe your device uses a Mediatek MT6762D. TCL has some snapdragon based phone that have fastboot. TCL Mediatek phones can be rooted and flashed with mtkclient.
This thread documents installing Android 13 in another TCL phone using the same series of Mediatek chipset (P22)
Thank you for the reply,
I am an Android newbie so I don't understand most of those complicated stuff.
If possible could you send me a step by step guide on how to add an custom ROM.
Also I couldn't find any custom ROMs for this device.
Newbie advice: Web search and use the forums search function. There are many, many web pages and videos , maybe even in your native language, that will walk you through this. Before starting you need to have android tools and mtkclient. These are available for Windows, Linux and MacOS.
The first 2 pages of the thread I provided are complaints about how hard TCL made this and unsuccessful attempts to hack. Starting w/ page 3 post #42, @malfuncion first documents how he installed a custom rom.
@malfuncion also provides downloads of all the files that worked for him.
In post #73 I provide copy/paste instructions for mtkclient.
The ROM's I used in the thread are GSI (Generic System Images). I used the ones from TrebleDroid which were fairly stripped down and based on the most recent AOSP code base.
@malfuncion used a CherishOS rom and provides it, repacked as linsuper.bin, on his download site. This may not work as it repacks a vendor.bin which may be different on your TCL model.
On my TCL A30, using the latest TrebleDroid Android 13 rom, the following works: phone, messaging, sim, wifi, camera, gps, brightness. Headphone jack works with alternate Phh jack settings. I successfully provisioned VOLTE using these instructions.
I had issues with apks not being fully functional when installed directly from F-Droid (specifically Geometric Weather widgets did not appear). Installing the apks using "adb install" fixed Geometric weather widgets.
Thanks a lots.