hi everyone,
received my trojan china tablet. need a rom/ source recommended to set up the android OS clean. only found buggy stuff on needrom.com; anyone can help?
sorry. total beginner.
flaboom8 said:
hi everyone,
received my trojan china tablet. need a rom/ source recommended to set up the android OS clean. only found buggy stuff on needrom.com; anyone can help?
sorry. total beginner.
Click to expand...
Click to collapse
The stuff on needrom (version 1.0.5) is the latest/newest/best available ROM atm. Unfortunately, google play services still gives error 501 when trying to update. manually updating it to version 11.0.62 gives an almost 100% working system, only AVG is refusing to work (needs an even newer version of google).
Rooting seems possible but complicated. I am also hoping/wating on a fixed/rooted rom...
The System.img of all the ROMs for V10 pro , I've downloaded so far are corrupt.
Has anyone successfully been able to flash this firmware to their devices so far??
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
Having a hard time finding a backup and Rom for this rather generic tablet. TWRP doesn't seem to be able to work with it, nor most rooters I found. anyone know what should / will work for me? This was a present for my wife, was supposed to have Android 7.1 but came with 5.1 which is almost useless now and system updates don't work.
attached are the specs / info of the tablet in photo form:
Similar problem with ALPS M962-2G
I have an ALPS JHZL M962-2G, Android 8.1. This was possibly infected by a virus and I want to completely reflash the ROM to make sure I've got rid of it. Unfortunately, I can't find a suitable ROM. I'd be happy with Android 8.1 or later. Anyone got any ideas? Some more info:
Model M962-2G
CPU 10 core 2.5G
Kernel 3.4.67
Build no. ALPS.KK1.MP1.V2.46
Custom build version JHZL-M962-2G-20191009
I'd be really grateful for some help.
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
Hello, I'm trying to upbring a device to Android Oreo, its the Samsung Galaxy Tab 2, but the wifi does not work. In the logcat it says `[email protected]: Failed to load WiFi driver` which seems to be the main issue. Any help on how to fix this issue?
The sources are kernel - https://github.com/MightyM17/android_kernel_ti_omap4 device - https://github.com/MightyM17/android_device_samsung_espresso
Logcat - https://pastebin.ubuntu.com/p/7zG5yppSTZ/
Oops didnt realise i posted this in general, mods could you move it to Q&A
Man, no one knows the solution for this issue ????? I saw this thread and read the issue but I don't know the fix so i didn't reply but i thought someone would. Please anyone help !! We may be getting closer to "android 8 on tab 2."
Arc android said:
Man, no one knows the solution for this issue ????? I saw this thread and read the issue but I don't know the fix so i didn't reply but i thought someone would. Please anyone help !! We may be getting closer to "android 8 on tab 2."
Click to expand...
Click to collapse
Android 8 on tab 2 already works, only wifi and gps arent working
Well some info that might , or might not, be relevant.
[SOLVED] Wi-Fi failure with custom kernel
I built a minimally modified BTI (Android 10) kernel for my Exynos S20+ (G986B) from the Samsung-released source and used Android Image Kitchen by @osm0sis to extract the boot.img from my device and repack it with the kernel image I built. I...
forum.xda-developers.com
LR7875 said:
Well some info that might , or might not, be relevant.
[SOLVED] Wi-Fi failure with custom kernel
I built a minimally modified BTI (Android 10) kernel for my Exynos S20+ (G986B) from the Samsung-released source and used Android Image Kitchen by @osm0sis to extract the boot.img from my device and repack it with the kernel image I built. I...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the help but the issue there seems to be different than the one I'm facing, for me the driver cannot insmod the module
So far I have only found few threads regarding the issue. Most threads does not have replies. I only got to these, which got some comments but did not have the issue fixed.
MIUI 12.5 wifi issues
Hi, today I received the EU update to MIUI 12.5 - 12.5.1.0(RFAEUXM) . However, now my Mi 9 can't connect to wireless networks. I already tried restore the network defaults and then the factory reset without success. Any ideas? The behavior is - I...
forum.xda-developers.com
wifi turning itself off, driver not being loaded.
Edit: Considering all the complex processes that I've done, I'm willing to do some series of steps again with the gathered knowledge, but I still need some guidance. Actual status: Losing my mind (not fixed) Here's the info of my current problem...
forum.xda-developers.com
We might need to seek help from other ROM developers which is active.
LR7875 said:
So far I have only found few threads regarding the issue. Most threads does not have replies. I only got to these, which got some comments but did not have the issue fixed.
MIUI 12.5 wifi issues
Hi, today I received the EU update to MIUI 12.5 - 12.5.1.0(RFAEUXM) . However, now my Mi 9 can't connect to wireless networks. I already tried restore the network defaults and then the factory reset without success. Any ideas? The behavior is - I...
forum.xda-developers.com
wifi turning itself off, driver not being loaded.
Edit: Considering all the complex processes that I've done, I'm willing to do some series of steps again with the gathered knowledge, but I still need some guidance. Actual status: Losing my mind (not fixed) Here's the info of my current problem...
forum.xda-developers.com
We might need to seek help from other ROM developers which is active.
Click to expand...
Click to collapse
Again the errors seem to be different. Well indeed we need other ROM developers' help here
Unfortunately, here are no active devs for TI OMAP devices. We (galaxy tab 2) have TI OMAP 4430.
Well we may ask other devs (of other phones with other chipsets), e.g. @html6405