Hi!
I found this page -by Christian Troy: http://forum.xda-developers.com/showthread.php?t=2354025
I am very happy, because custom roms now can be found for allwinner a31, but I have problem with the compatibility zips. There's nowhere for the MyAudio 916 QR, everwhere just Onda and few others. Do you have any idea?
Thanks!
Somnius
Hi Christian or anyone could help with this momo20 compatibility.zip that you have attached in pg 1 of this section?
I just realized that actually this zip works except that it is unsigned.
I 'll need anyone who has signed it & put it in a link for download...
I tried signing it with the software but it keeps giving me issue on my windows...
Appreciate someone who could signed it or post the signed momo20 compatibility.zip...
Ployer MOMO20 (v2.0 based) 2.0_rc0 which can be found here
https://mega.co.nz/#...NICQ8xfN3QoeYxU
Appreciate with thanks!
Hello Guys
I am new here and I have a allwinner a13 tab
Android 4.0.4
1.2 Ghz Single Core Cortex A8
Baseband V 1.5
Kernel armv7I
512 mb ram
4gb rom
Board Nuclear_evb
GPU Mali 400
GPU ARM
Hardware sun5i
kernel version 3.0.8+
7 inch screen
I want a custom kitkat rom for my device.
Searched all XDA threads found none useful
I want to develop own rom 4.4 for my device. I am a noob so please bear with me
I will be highly obliged if someone would make it for me
But just want some guidance to develop custom rom.
Please can just someone tell me how to develop rom for my device.
My device is Intex I Buddy 3 and is rooted. I have knowledge about rooting ,firmwares , kernels etc.
Can someone tell me that rom can be developed?
If yes then guide me the steps to do so as I am a quick learner I won't cause much trouble :laugh:
If no then why rom can not be developed.
So please help me
Thanks in advance.
Note: Please don't ignore this thread as I really need a kitkat rom for my device as it is completely screwed up . I dont have enough funds so that I can buy a new device
Still no help found
Tech N You said:
Hello Guys
I am new here and I have a allwinner a13 tab
Android 4.0.4
1.2 Ghz Single Core Cortex A8
Baseband V 1.5
Kernel armv7I
512 mb ram
4gb rom
Board Nuclear_evb
GPU Mali 400
GPU ARM
Hardware sun5i
kernel version 3.0.8+
7 inch screen
I want a custom kitkat rom for my device.
Searched all XDA threads found none useful
I want to develop own rom 4.4 for my device. I am a noob so please bear with me
I will be highly obliged if someone would make it for me
But just want some guidance to develop custom rom.
Please can just someone tell me how to develop rom for my device.
My device is Intex I Buddy 3 and is rooted. I have knowledge about rooting ,firmwares , kernels etc.
Can someone tell me that rom can be developed?
If yes then guide me the steps to do so as I am a quick learner I won't cause much trouble :laugh:
If no then why rom can not be developed.
So please help me
Thanks in advance.
Note: Please don't ignore this thread as I really need a kitkat rom for my device as it is completely screwed up . I dont have enough funds so that I can buy a new device
Click to expand...
Click to collapse
I have been wanting this as well but so far I have yet to see someone port or try to port a ROM for the A13 using the KitKat rom. I have many A13 tabs and I have some custom ROMs I created myself but none entail the makes of the KitKat ROM. To be honest I am not even sure it can be done other then a stock ROM modified to replicate the KitKat ROM meaning it is per say JellyBean 4.2 but the prop is edited to say KitKat and the theme to look like KitKat the added features etc.
orbitA13 said:
I have been wanting this as well but so far I have yet to see someone port or try to port a ROM for the A13 using the KitKat rom. I have many A13 tabs and I have some custom ROMs I created myself but none entail the makes of the KitKat ROM. To be honest I am not even sure it can be done other then a stock ROM modified to replicate the KitKat ROM meaning it is per say JellyBean 4.2 but the prop is edited to say KitKat and the theme to look like KitKat the added features etc.
Click to expand...
Click to collapse
I also want to run KitKat as you. Can you guide me how to modify stock rom in order to flash kitkat boot img and run kitkat or anything else that can create a cutsom rom.?
Tech N You said:
I also want to run KitKat as you. Can you guide me how to modify stock rom in order to flash kitkat boot img and run kitkat or anything else that can create a cutsom rom.?
Click to expand...
Click to collapse
Light MODing like editing build.prop start up sound and things like that is easy you can even change your start up/splash images and even APK's adding and removing with simple tools you can find on the net just do a search for how to edit your stock ROM or any ROM for that matter even here you might find all the tools you need.
I create all my ROMs using Ubuntu 12.04.3 desktop AMD64 and Source for JB 4.2.2 or a donor ROM which is similar to the stock ROM of the device the user may own. As for explaining step by step I am sorry but you will need to do the leg work for that as it is not easy to explain and you will need a general knowledge of what you are doing and at some points advanced knowledge. As for flashing the boot.img from KitKat to JB 4.2.2 will not work.Things that would/could be added if compatible to your donor ROM are Drivers, Sounds, Images, APKs, System Apps, Etc...
So the point is here that you can add images and splash screen and boot up images that come from KitKat and even add the apps if compatible with JB 4.2.2 and tweaks of your own that are made to boot with the system or not anything else would need to be ported and as mentioned I have yet to see a ported KitKat version for the A13. You can also edit your SystemUi.apk to make changes but this is another avenue make sure you understand and know what you are doing when doing so and always make backups!
Some Tools
=========
System Type is up to you!
ADB Tools is a (MUST)
DragonFace
LiveSuite
APK Tool
Bootimage Tools
slidepad704ce-jb-kitchen
Script-Bin Tools
Uberizer
This is just some of the things you can use some are for Windows other I use on Ubuntu.
orbitA13 said:
Light MODing like editing build.prop start up sound and things like that is easy you can even change your start up/splash images and even APK's adding and removing with simple tools you can find on the net just do a search for how to edit your stock ROM or any ROM for that matter even here you might find all the tools you need.
I create all my ROMs using Ubuntu 12.04.3 desktop AMD64 and Source for JB 4.2.2 or a donor ROM which is similar to the stock ROM of the device the user may own. As for explaining step by step I am sorry but you will need to do the leg work for that as it is not easy to explain and you will need a general knowledge of what you are doing and at some points advanced knowledge. As for flashing the boot.img from KitKat to JB 4.2.2 will not work.Things that would/could be added if compatible to your donor ROM are Drivers, Sounds, Images, APKs, System Apps, Etc...
So the point is here that you can add images and splash screen and boot up images that come from KitKat and even add the apps if compatible with JB 4.2.2 and tweaks of your own that are made to boot with the system or not anything else would need to be ported and as mentioned I have yet to see a ported KitKat version for the A13. You can also edit your SystemUi.apk to make changes but this is another avenue make sure you understand and know what you are doing when doing so and always make backups!
Some Tools
=========
System Type is up to you!
ADB Tools is a (MUST)
DragonFace
LiveSuite
APK Tool
Bootimage Tools
slidepad704ce-jb-kitchen
Script-Bin Tools
Uberizer
This is just some of the things you can use some are for Windows other I use on Ubuntu.
Click to expand...
Click to collapse
Ohk! Thank you:laugh::good:
Here is version for allwinner a10(this is allwinner a13+HDMI):
4pda.ru/ forum/index.php?showtopic=425228&st=2380#entry30353733
sorry for non working link but i cant add working (restrication)
Hi guys! I'm a proud owner of a Cherry Mobile Fusion Wave Tablet that I don't freakin' know the OEM. I was wondering on how I can extract the ROM straight from the device itself?
I've already tried the romdump_v82b.zip method and it gave me an error about the emmc.
I can't do an SPFT Extraction because this tablet is having the Samsung Exynos 4412 SoC (The reason I got the tablet)
Any help is appreciated!!!
Hi there
There are many guides and tutorials here for developing roms:
> Chef Central > Android
After lots of reading, if you still have questions, ask in the thread of the guide you are using, or start your own thread and ask for help.
FYI: [TUTORIAL][GUIDE] How to extract your ***.tar.md5 ROM file (Samsung stock ROM) [EASY]
Good luck
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