Asus ATOM.. UnLOCK bootloader, no official. So which unofficial should I pick? HELP - General Questions and Answers

Hi All, I have a Asus TRIO TX201LA intel x86 z2560 soc (AKA TX201LAF, french). I device so obscure almost no one knows it even exists on XDA. Owners of this device are so rare most are dead or locked away with no internet access. Ok all joking aside its pretty rare device with little to no support for it anywhere. Asus never gave it 1 update. Its on android 4.2. It has MANY asus clones including but not limited to the following: Zenfone A450CG/A500CG, FonePad 7 FE375CG/CGX, Asus Memo Pad 7 ME176C/CX, Asus Memo pad 10 me302c. As for devices that share the soc thing include the Galaxy Tab 10.1, Dell Venue 7 and probably more. I think there are more asus devices out there also.
What I want to figure out is this. Which method that I have found to unlock the boot loader is best for me to try to avoid a brick. Here are a list of methods:
1. This method comes from the memo pad 7: https://forum.xda-developers.com/memo-pad-7/help/help-me176c-fastboot-123-screen-t3713930
2. This method also comes from the memo pad 7: https://forum.xda-developers.com/memo-pad-7/general/asus-me176c-cx-unlock-bootloader-t3315603
3. This method comes from the dell venue 7: https://forum.xda-developers.com/showthread.php?t=1787620
4. There is an official method from the Zenfone 4 A450CG which is involves an unlock tool provided by asus. Its called: Unlock_Tool_A400_v8.1.apk. I've explored this the most (tried v7 &7.5) but have been unable to get it to work. This apk installed and gives me the warning about unlocking and losing warranty but then says the my "device model is not supported". I figured an edit to the APK may allow this to work on my bootloader. see: https://www.asus-zenfone.com/2014/11/download-official-unlock-bootloader-tool-zenfone4.html?m=1
5+ there are actually a few more unlock methods I've found mostly for the zenfone 4/5 but they involve flashing here is 1. https://forum.xda-developers.com/zenfone-5/general/guide-how-to-unlock-bootloader-safely-t3562640 & another: https://www.asus.com/zentalk/thread-39834-1-1.html
Due to no support from asus no bootloader unlock will ever be released for my device but I believe one of the above methods either could work "as is" or may need a small edit to work. So can someone help me unlock my bootloader? After this I plan to build a rom using my kernel source here: https://rebyte.me/en/asus/86392/file-543531/ to build a Bliss rom.
Hope that the Unlock_Tool_A400_v8.1.apk can be edited as I see it this maybe the best and easiest to avoid a brk..

Anyone?????

Come on.. this is a simple task for any dev, i should think.
DANG, to many devices not enough devs.. It was all so different before 2010. RIP how it used to be.

son of a snake bite
madhits45 said:
Come on.. this is a simple task for any dev, i should think.
DANG, to many devices not enough devs.. It was all so different before 2010. RIP how it used to be.
Click to expand...
Click to collapse
Yeah man I hear you.. it was once so much better, just to many dang devices now..

Bumpy boompop shazam.. Hello Atoms not DEAD yEt.. https://www.pcworld.com/article/315...m-chip-in-panasonics-2189-android-tablet.html

ompa lumpa bumity bump

Related

Possible way to root B70 Transformers on 3.1/3.2?

When I was looking at the Android news, I found this video:
http://www.youtube.com/watch?v=jmWR3vUq7Ww
This demonstated two unpatched security holes in Android. The second one, a privilege escalation vulnerabilitiy targeting the Linux kernel, got me very intrested: If we could persuade the team to open source this exploit, we could gain a very useful program that can shell root ANY Android device, meaning that we could root B70 tablets with the new SPK (like mine). This is something worth looking in to, and if it's realased to us, we could gain a very potent resource that will help us with rooting in general.
check the pad's serial number...if your SN is before KAS180..you can root it using Brk v7 method..worked for me...
If your device has KAS180+ well..be patient and wait for a root method...
Actually, I know my device right now cannot be rooted. The point of this post was to bring up a potental new exploit that can shell root ANY android device, including Honeycomb 3.1-3.2.
Sounds good. Found it from yesterday.
Originally Posted by j0hn0n1
Just wanted to let you guys know that a root for the B70 Transformer is on it's way. Thanks to amazing work of :-
* RaYmAn (@DroidRay)
* Bumble-Bee (@BumbleDroid)
* kmdm (@alpharevx)
* IEF (@alpharevx)
* lilstevie (@littlesteve)
We will soon be able to root our B70's & possibly B80's, they have figured out a way to use NVFlash without the SBK.
So we just need to be a little patient, and wait until they release it.. which I'm sure will be very soon... Attachment 918
Sent from my Transformer TF101 using xda premium
I do know about that, but I was just bringing up a method, that if we badger the creators enough, can make shell root on a signifant number of Android devices possible. Can't wait for the day for which I can NVFlash...
Sent from Remilla, my stubbon stock ASUS Transformer
Ultfreecomputing said:
I do know about that, but I was just bringing up a method, that if we badger the creators enough, can make shell root on a signifant number of Android devices possible. Can't wait for the day for which I can NVFlash...
Sent from Remilla, my stubbon stock ASUS Transformer
Click to expand...
Click to collapse
The method mentioned in the OP probably won't apply to the transformer since it looks like the Econet Privilege Escalation Exploit that only affects kernels older than 2.6.36.2.
mingocr83 said:
check the pad's serial number...if your SN is before KAS180..you can root it using Brk v7 method..worked for me...
If your device has KAS180+ well..be patient and wait for a root method...
Click to expand...
Click to collapse
mine has B70KAS098 but can't be rooted with 7.0
ITS a WW version.

[Q] Bootloader concepts for developers - in-depth explanation request

Hello,
Can sombody provide me some in-depth sources to read about locked bootloaders?
What I would like to understand mainly is the concept which won't let you overwrite the locked bootloader with another one.
I think once you have the hardware in your hands you can write (flash) the whole memory if it's writable.
I will provide an example to give a starting point.
I've stumbled upon this conceptional problem when users trying to change the LG G Pad 8.3 rom.
It has two versions:
V500 with LG's mod on Android 4.2.2
V510 with Stock Android 4.4 (Google play edition)
The hardwares in these devices are the same, the difference is in the software.
Why one can't just mirror the whole V510 contents (partitions, data, boot, etc...) on a V500?
I'm a developer, so I'd really like to understand the concept in depth.
Thanks for any help,
atatek
(reserved)

ASUS Transformer TF303

With a desperate need to replace my TF700T, no rumours anywhere of a TF701T replacement coming, the only "new" Transformer coming to the UK being the entry level TF103 and a Facebook post reply from ASUS UK stating that they've no intention to bring the TF303 to the UK, I've ordered a TF303CL from Germany -- yeah, yeah, squiffy keyboard I know ...but less than ½ what I paid for TF700.
Has the buzz and excitement gone out of the TF line now as when I was looking at the Prime and then the Infinity there was quite a furore over them but the TF103 and TF303 have appeared with hardly a whisper about them on the internet. There is still nothing else out there that that offers the combination of features that the Transformers do with regards keyboard, trackpad, ports, etc. I'm disappointed that ASUS seem to have embarked on de-specing the Transformers. Is it all about the Transformer Books now?
Will this be a mainstream enough device to get its own section on here?
JTHM said:
With a desperate need to replace my TF700T, no rumours anywhere of a TF701T replacement coming, the only "new" Transformer coming to the UK being the entry level TF103 and a Facebook post reply from ASUS UK stating that they've no intention to bring the TF303 to the UK, I've ordered a TF303CL from Germany -- yeah, yeah, squiffy keyboard I know ...but less than ½ what I paid for TF700.
Has the buzz and excitement gone out of the TF line now as when I was looking at the Prime and then the Infinity there was quite a furore over them but the TF103 and TF303 have appeared with hardly a whisper about them on the internet. There is still nothing else out there that that offers the combination of features that the Transformers do with regards keyboard, trackpad, ports, etc. I'm disappointed that ASUS seem to have embarked on de-specing the Transformers. Is it all about the Transformer Books now?
Will this be a mainstream enough device to get its own section on here?
Click to expand...
Click to collapse
I have the TF303CL for a while now and am very pleased with it! But have not found anything yet on rooting the device etc. Hoping it will get it's own section here,but have my doubts
Got a TF303K, very pleased with it but still looking for a way to get root.
Also I noticed that busybox installer reports it as already rooted but not able to install busybox binaries so no root yet...
Will gladly see a dedicated section!
edit: did anyone tried towelroot?
edit2 : not working
franklin01 said:
Got a TF303K, very pleased with it but still looking for a way to get root.
Also I noticed that busybox installer reports it as already rooted but not able to install busybox binaries so no root yet...
Will gladly see a dedicated section!
edit: did anyone tried towelroot?
edit2 : not working
Click to expand...
Click to collapse
Try this app. There few posts on 4pda.ru that say that it helped.
Thanks but did not work, it says "only for zen phones". I also tried the last version but same error. That's a strange thing as the TF303CL version can be rooted using this app.
I will keep looking for something.
If someone can try on their 303k just to confirm that it is not working.
Also I did the update when I got so maybe a factory reset might do the trick.
Edit:
got the last apk version on asusfone blog: http://www.asuszenfoneblog.com/search/label/RootZenFone
Model: K01B
System: 4.4.2
Build: KOT49H.WW_epad-11.12.1.39-20141009
RootZenFone does not shows the "root" button because it is not a zen phone, so the app is checking device name or something like that. If we can change that file then it might work ( or explode and kill every cat within a mile ).
If someone is smart enough to root the TF303K I will gladly send him an "inbox" invite or "ello" invite if it can help things moving.
mrtruebeliever said:
I have the TF303CL for a while now and am very pleased with it! But have not found anything yet on rooting the device etc. Hoping it will get it's own section here,but have my doubts
Click to expand...
Click to collapse
Where did you purchase your TF303CL? I've been searching high and low for one but no one seems to even have them listed, let alone in/out of stock. Thanks!
skylar.sutton said:
Where did you purchase your TF303CL? I've been searching high and low for one but no one seems to even have them listed, let alone in/out of stock. Thanks!
Click to expand...
Click to collapse
I bought it here on tabletcenter . be
www . tabletcenter . be/product/475001/asus-transformer-pad-tf303cl-wifi-4g-blauw.html
It's from a company in Belgium. Don't know if they ship to the US
skylar.sutton said:
Where did you purchase your TF303CL? I've been searching high and low for one but no one seems to even have them listed, let alone in/out of stock. Thanks!
Click to expand...
Click to collapse
And I got mine imported to the UK from Amazon.de. Again, I don't know whether Amazon.de export outside the EU - you'd have to give it a try ...and live with a German keyboard layout.
Anybody knows how to root this device?
I got my Asus Asus TF303CL-1D024A tody and try FramaRoot, TowelRoot and the App for ZEN Phones ... nothing works ...
Cant await some solution to root my Asus TF303CL...
root
For root: downgrade to 31.ver (from asus site), install rootzenfone 1.4.6.4r. and start procedure in airplane mode, then install supersu 2.42 apk + pro 2.05 key. In settings SU install them in system and set on boot. Then upgrade to 32.ver over air update. Note: downgrade proceed to remove your data.
Thx to BlackVictor from 4pda.ru
Thanks, will try it tomorrow.
Merry Christmas to all from Germany.
roma321 said:
rootzenfone 1.4.6.4r
Click to expand...
Click to collapse
It does not work for me ... :silly:
roma321 said:
For root: downgrade to 31.ver (from asus site), install rootzenfone 1.4.6.4r. and start procedure in airplane mode, then install supersu 2.42 apk + pro 2.05 key. In settings SU install them in system and set on boot. Then upgrade to 32.ver over air update. Note: downgrade proceed to remove your data.
Thx to BlackVictor from 4pda.ru
Click to expand...
Click to collapse
Please, how did you flash 31.ver? Thanks an merry christmas ?
spiderman1961 said:
Please, how did you flash 31.ver? Thanks an merry christmas ?
Click to expand...
Click to collapse
Download from asus.com, put zip in root of lnternal storage and then reboot.
roma321 said:
Download from asus.com, put zip in root of lnternal storage and then reboot.
Click to expand...
Click to collapse
Must i use stock recovery? Right?
spiderman1961 said:
Must i use stock recovery? Right?
Click to expand...
Click to collapse
I think, it's possible only on stock recovery...
I'm still waiting for a recovery and a custom ROM.
Does anyone know when I can expect. I'm not really happy with the Asus shield
spiderman1961 said:
Must i use stock recovery? Right?
Click to expand...
Click to collapse
not quite understand you, sorry.
Flash 31.ver not in recovery, by simple reboot.

Intel Atom x86 SOC, how hard is it to load rom from a different atom z25xx device?

I am on a Asus trio tx201la INTEL x86 tablet on android 4.2 on the tablet part. I researched that The zenfone 5, dell venue 7 and the samsung galaxy tab 3 10.1. All have the same intel atom z2560 cpu soc and some are running Android 7 & even 8 now.
The Galaxy tab 3, zenphone 5 got a lot more attention and thus a lot more custom rom attention. Dell venue and my Trio got little to no attention due to poorer sales.
The galaxy tab 3 has been updated to 7.1.1 see:
http://techbeasts.com/install-android-711-nougat-galaxy-tab-3-101-lineageos-141/
Now How can that help the Trio? I found this tool, but no flash.xml so no luck using it:
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Here is a guide on how to use it: http://www.aryk.tech/2016/04/how-to-flash-stock-firmware-using-intel.html?m=0
This is all NEW as of 2017. So its not been available before this.
The TX201LAF a french tablet version of the TX201LA is in the same boat but it at least it is on 4.4. Its kernel firmware is here: http://support.asus.com.cn/Download.aspx?SLanguage=en&m=TX201LAF&p=3&s=587
My big question is with all these roms for x86 atom z2560 & z2580 soc's shouldn't I be able to get an updated rom somehow? I imagine that would involve building a rom myself but if the base soc is the same isnt it possible to build the rom for a different device and use a different kernel source like I linked above? The kernel source has the drivers I need right, for the device to run? Ive heard a lot of people talk about you wont get the touch panel to work or the wifi. I understand that but isnt it all loaded from the kernel source? So basically if I have kernel source and grab an updated rom from lineage 7 for the galaxy tab 10.1 and replace the kernal i'm good to go right? I know there is more to it but really looking for some help here?
Even if I can just get the tx201laf image to load on my tx201la that would be
something, its an update from 4.2 to 4.4. Both devices are identical, so that should make it a lot easier right? Looking for any insight to xda experts can provide.
Hi ! I'm still using my trio so I'm very interested ! Did you succeed ?
Thks a lot
no luck yet
I had hopes that this would turn out to work but you cant use the intel flash tool without a flash.xml which is written for the device. SO that stopped me dead in my tracks.
I recently found this: https://forum.xda-developers.com/android/software-hacking/efidroid-t3447466/page37
Hoping this dev will give the tx201la a shot. There is also this: https://forum.xda-developers.com/an...g/tool-multirom-recovery-replacement-t3102395
Do you realize how simular the tx201la is to just about every zenphone made since the newest. IE almost all of those roms would likely boot on our tablet.
??
Any other input?
Come on guys, has everyone moved on to the shinny new toys?
madhits45 said:
Common guys, has everyone moved on to the shinny new toys?
Click to expand...
Click to collapse
Best bet https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Palm Trees said:
Best bet https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Click to expand...
Click to collapse
Thanks for the tip. Now I need to find help up-streaming my kernel:
Device info: https://valid.x86.fr/a/wkb2d8
Kernel source: http://support.asus.com.cn/Download.aspx?SLanguage=en&m=TX201LA&p=3&s=587
Could really use help doing that.. Total noob & trying to understand all the terminology.
madhits45 said:
Thanks for the tip. Now I need to find help up-streaming my kernel:
Device info: https://valid.x86.fr/a/wkb2d8
Kernel source: http://support.asus.com.cn/Download.aspx?SLanguage=en&m=TX201LA&p=3&s=587
Could really use help doing that.. Total noob & trying to understand all the terminology.
Click to expand...
Click to collapse
Then go here: https://4pda.ru/forum/index.php?showtopic=530541
Palm Trees said:
Best bet https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Click to expand...
Click to collapse
Palm Trees said:
Then go here: https://4pda.ru/forum/index.php?showtopic=530541
Click to expand...
Click to collapse
HOLLY $#%^ PALM TREES!!!!!!
Ok I checked out the Russian thread, which I cant believe I had never found, seriously what search engine do you use? Or are you Russian?
Anyway that lead me to this: https://cs5-3.4pda.to/10031052/20170404_145326.jpg?6c8bd0e99d5f5d5ce8c14e92c456565c
That might not mean much to many but its the TX201LA running the Asus memopad 10 android 4.2.2 and its actually working. So that is a huge deal.
Then I found this: https://forum.xda-developers.com/an.../rom-8-0-0-lineageos-15-0-unofficial-t3693838
There is a updated rom for the memopad 10. Now I hope I can get this rom to run with slight variations.. Will see..
madhits45 said:
HOLLY $#%^ PALM TREES!!!!!!
Ok I checked out the Russian thread, which I cant believe I had never found, seriously what search engine do you use? Or are you Russian?
Click to expand...
Click to collapse
No problem. I'm not Russian. I use Google mostly. My pride and joy is my memory (lol) :laugh: and I like to help if I can. Saw your thread and simply shared a few resources, I figured were helpful

Mediatek MT8173 & MT8176 Development

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

Categories

Resources