Teclast M40 Installing ROM from Windows - General Questions and Answers
Hello! Just received my first tablet, so am very new to all of this. Looking for guidance and direction. Glanced through the first page of Noob friendly thread and didn't see this addressed. So asking here.
Background: I ordered a Teclast M40 on Aliexpress and received it last week. I tried using Zoom on it and the person I was speaking to said that he could barely hear me. I then tried recording myself on the stock recording app app, and playing the file back indeed my voice was barely audible and somewhat muffled. I contacted the seller, and he sent me a Zip file asking me to reburn the stock ROM onto the Tablet thinking that this would solve the issue. I struggled with the software last week and refused to work. But this week, for whatever reason, everything worked and I was able to reflash the software. Obviously the issue was not resolved. Understanding that I am unlikely to get my money back, I now need to find a way to fix this myself, which is why I'm here.
My Questions
1. Since I have this software, do I still need to unlock the bootloader to flash a custom ROM?
2. Found a very helpful thread on Teclast M40 Here in it people talk about replacing the stock system with a gsi system. Which I never knew was an option until I came here. Since this appears less of an understaking, I'm hoping to try this first and see if it solves my microphone issue. The question is do I still need to unlock my device to install the GSI? Or can I just copy the GSI over the vbmeta.* files and burn it that way.
Just in case it is of any use here are some listings of directory entries from the Zip that I received from the Vendor I bought the Tablet from
Wiki:
Directory of Z:\Zoot\Teclast
01/17/2021 10:49 PM <DIR> .
01/17/2021 10:49 PM <DIR> ..
01/13/2021 12:10 AM <DIR> Firmware
01/17/2021 10:49 PM 0 rootFolder.txt
01/13/2021 12:11 AM <DIR> Upgrade Driver
01/14/2021 04:02 PM <DIR> Upgrade Tools
01/13/2021 12:11 AM 401,967 Upgrade tutorial.pdf
Directory of Z:\Zoot\Teclast\Firmware
01/13/2021 12:10 AM <DIR> .
01/13/2021 12:10 AM <DIR> ..
01/13/2021 12:11 AM 3,342,253,832 Firmware.pac
Directory of Z:\Zoot\Teclast\Upgrade Tools
01/17/2021 10:52 PM <DIR> .
01/17/2021 10:52 PM <DIR> ..
01/13/2021 12:11 AM 361 BinPack.ini
01/13/2021 12:11 AM 11,567 BMAConfig.xml
01/13/2021 12:11 AM 314,368 BMAFrame9.dll
01/13/2021 12:11 AM 1,214 BMError.ini
01/14/2021 10:09 PM 6,263 BMFileType.ini
01/13/2021 12:11 AM 290,816 BMPlatform9.dll
01/13/2021 12:11 AM 1,149 BMTimeout.ini
01/13/2021 12:11 AM 1,357 Channel.ini
01/13/2021 12:11 AM 252,928 Channel9.dll
01/13/2021 12:11 AM 266,240 CmdDloader.exe
01/13/2021 12:11 AM 228 CmdDloader.ini
01/13/2021 12:11 AM 803,727 Guide.chm
01/17/2021 09:54 AM <DIR> ImageFiles
01/13/2021 12:11 AM 2,413 MCPType.ini
01/13/2021 12:11 AM 139,264 PortHound.dll
01/13/2021 12:11 AM 196,608 ProcessFlow.dll
01/13/2021 12:11 AM 478 ProcessFlowSetting.ini
01/13/2021 12:11 AM 251,392 SecBinPack9.dll
01/13/2021 12:11 AM 244 SprdMes.ini
01/13/2021 12:11 AM 1,884,672 SprdMesApp.dll
01/13/2021 12:11 AM 120,056 udl_bkmark.bmp
01/13/2021 12:11 AM 1,763,328 UpgradeDownload.exe
01/17/2021 09:43 AM 14,385 UpgradeDownload.ini
01/17/2021 10:52 PM 0 utFolder.txt
Running the UpgradeDownload.exe extract the image files from the Firmware directory and produces the following directory
Wiki:
Directory of Z:\Zoot\Teclast\Upgrade Tools\ImageFiles\_DownloadFiles276766062
01/17/2021 10:54 PM <DIR> .
01/17/2021 10:54 PM <DIR> ..
01/17/2021 10:54 PM 36,700,160 boot.img
01/17/2021 10:54 PM 94,332 cache.img
01/17/2021 10:54 PM 8,388,608 dtbo.img
01/17/2021 10:54 PM 947,120 EXEC_KERNEL_IMAGE.bin
01/17/2021 10:53 PM 59,956 fdl1-sign.bin
01/17/2021 10:53 PM 632,612 fdl2-sign.bin
01/17/2021 10:54 PM 593,059 gnssmodem.bin
01/17/2021 10:54 PM 479,368 odmko.img
01/17/2021 10:54 PM 2,305,080 P20HD_EEA.bmp
01/17/2021 10:54 PM 2,305,080 P20HD_EEA.bmp(1)
01/17/2021 10:54 PM 2,097,152 persist.img
01/17/2021 10:54 PM 45,132 prodnv.img
01/17/2021 10:54 PM 41,943,040 recovery.img
01/17/2021 10:54 PM 26,214,400 SC9600_sharkl5pro_pubcp_customer_modem.dat
01/17/2021 10:54 PM 1,048,576 sharkl5pro_cm4.bin
01/17/2021 10:54 PM 6,291,456 sharkl5pro_pubcp_customer_AGCP_DSP.bin
01/17/2021 10:54 PM 1,048,576 sharkl5pro_pubcp_customer_CDMA_DSP.bin
01/17/2021 10:54 PM 2,264 sharkl5pro_pubcp_customer_deltanv.bin
01/17/2021 10:54 PM 10,485,760 sharkl5pro_pubcp_customer_DM_DSP.bin
01/17/2021 10:54 PM 20,971,520 sharkl5pro_pubcp_customer_LTEA_DSP.bin
01/17/2021 10:54 PM 765,396 sharkl5pro_pubcp_customer_nvitem.bin
01/17/2021 10:54 PM 53,796 sml-sign.bin
01/17/2021 10:54 PM 50,385,032 socko.img
01/17/2021 10:54 PM 3,124,144,944 super.img
01/17/2021 10:54 PM 1,940 teecfg-sign.bin
01/17/2021 10:54 PM 2,213,892 tos-sign.bin
01/17/2021 10:54 PM 632,612 u-boot-sign.bin
01/17/2021 10:54 PM 63,140 u-boot-spl-16k-sign.bin
01/17/2021 10:54 PM 32,545 ums512_1h10.xml
01/17/2021 10:54 PM 147,772 userdata.img
01/17/2021 10:54 PM 1,048,576 vbmeta-sign.img
01/17/2021 10:54 PM 4,096 vbmeta_system.img
01/17/2021 10:54 PM 4,096 vbmeta_vendor.img
Flashing a Custom ROM requires a Custum Recovery gets flashed before, what as 1st thing of all things requires AVB gets disabled before - means toogle the related flag ( bits ) in the 3 vbmeta images , what is known as unlocking the bootloader.
The Teclast M40 is based on UNISOC T618 Aortex-A75 Core chipset. Hence its a good idea to use SPD Flash Tools , IMO, when it comes to operate on device's bootloader and/or Android OS.
Advice: Add "TECLAST M40" to front of this thread's title what will prevent visitors to unnecessarily open this thread for reading.
Sorry my questions are going to be extremely Noob
jwoegerbauer said:
Flashing a Custom ROM requires a Custum Recovery gets flashed before,
Click to expand...
Click to collapse
This device is brand new and I have nothing on it that I want/need to save. Do I still need the Recovery?
jwoegerbauer said:
what as 1st thing of all things requires AVB gets disabled before - means toogle the related flag ( bits ) in the 3 vbmeta images , what is known as unlocking the bootloader.
Click to expand...
Click to collapse
Is there a link that someone as new as me can check out and see a little bit more info about this?
jwoegerbauer said:
The Teclast M40 is based on UNISOC T618 Aortex-A75 Core chipset. Hence its a good idea to use SPD Flash Tools , IMO, when it comes to operate on device's bootloader and/or Android OS.
Click to expand...
Click to collapse
So it siunds like you are saying don't use the software that I already have, that the Vendor sent me
jwoegerbauer said:
Advice: Add "TECLAST M40" to front of this thread's title what will prevent visitors to unnecessarily open this thread for reading.
Click to expand...
Click to collapse
Done! Thank you.
The Stock Recovery, that comes by default with all Android devices, only allows to re-flash tablet's Stock ROM - means a ROM signed by OEM/carrier and compiled for that tablet, whereas a Custom Recovery skips the related signature-verification process hence you can flash any matching ROM onto your tablet.
Android 7.0 started strictly enforcing Verified Boot ( AVB ) to prevent compromised devices from booting.
With regards to unlocking tablet's bootloader - i.e. disable AVB: Typically people by means of SPD Research Tool extract existing vbmeta-sign.img, then pass this extracted file to Fastboot - the default tool to operate on Android devic's bootloader - what rewrites it at its own when you run
Code:
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta-sign vbmeta-sign.img
fastboot reboot
It's on you to use the software provided by vendor. It was only a hint to use SPD Flash Tools instead.
FYI:
I don't own that tablet, hence I can't guide further. Thanks for your understanding.
What would be a good place to see all of the steps involved in rooting? At the moment I see 2 rooting options. (There may of course be more)
1. Installing an OS like Lineage and others (I'm not sure what that does, I assume it simply replaces the entire ROM.
2. Modifying/Replacing the GSI which (does something that you described and I didn't quite understand ) to the vbmeta files.
Hi,
My Teclast M40 has the same problem as yours regarding volume of recorded sound from the built in microphone. Based on the icons painted on the back of the tablet it appears the microphone is located between the two speakers. However, you will notice there is no hole cut in the case where the microphone should be. I looked all over the tablet for another microphone hole and the only other holes are for the reset button and speakers. So I think this is a design defect that cannot be corrected in software. The only option you have is to open the device, locate the microphone and cut a hole in the case to allow sound in, OR use a headset. Hope this helps.
Steve
steve.l said:
Hi,
My Teclast M40 has the same problem as yours regarding volume of recorded sound from the built in microphone. Based on the icons painted on the back of the tablet it appears the microphone is located between the two speakers. However, you will notice there is no hole cut in the case where the microphone should be. I looked all over the tablet for another microphone hole and the only other holes are for the reset button and speakers. So I think this is a design defect that cannot be corrected in software. The only option you have is to open the device, locate the microphone and cut a hole in the case to allow sound in, OR use a headset. Hope this helps.
Steve
Click to expand...
Click to collapse
Hi,
Did you manage to open the tablet and cut a hole? Does the problem got solved?
Regards
I cut a hole without opening it but apparently that fixed only the echo part which the other end experienced. Yet the mic still barely hear me...any other suggestions?
How come he got a decent answer and I got a copy paste, "Hold power button + volume down to boot into recovery where you can flash update.zip" junk? Oooo didn't think I would see this huh! Full on busted.
RudyGireyev said:
Sorry my questions are going to be extremely Noob
This device is brand new and I have nothing on it that I want/need to save. Do I still need the Recovery?
Is there a link that someone as new as me can check out and see a little bit more info about this?
So it siunds like you are saying don't use the software that I already have, that the Vendor sent me
Done! Thank you.
Click to expand...
Click to collapse
Read this post and beyond. I disabled avb completely
Teclast M40 How to unlock bootloader?
I have found a method of Teclast P20HD to unlock bootloader which can be found in "https://forum.xda-developers.com/android/help/teclast-p20hd-android-10-tablet-4g-t4141997" and "https://forum.hovatek.com/thread-32287.html", but I'm not sure if...
forum.xda-developers.com
Related
[Q&A] [ ROM ] Stock Rooted 4.4.4 XNPH30O [ Aug 11 build / Deodex zip attached ]
Q&A for [ ROM ] Stock Rooted 4.4.4 XNPH30O [ Aug 11 build / Deodex zip attached ] Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Before posting, please use the forum search and read through the discussion thread for [ ROM ] Stock Rooted 4.4.4 XNPH30O [ Aug 11 build / Deodex zip attached ]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help. Thanks for understanding and for helping to keep XDA neat and tidy!
i AM TRYING TO LAUNCH CAULKINS ROM AND IT IS SAYING THE FOLLOWING "Verifying update package E: footer is wrong E: signature verification failed" i HAVE A MOTOROLA DROID BIONIC
help My actual os is: 11-20141008-snapshot-m11-bacon I flashed "File Type: zip Calkulin's_4.4+_Deodex_System.zip" and my opo restart continuously. I made a full wipe and reboot and oneplus one logo doesn't go away from the screen. I let it for 10 min and nothing happened. Now I backup my opo to the previous version and it is rooted. (controlled with root checker app) wich one of files i have to flash? 1- Stock Rooted 4.4.4/XNPH30O ROM (v1.1) 2- XNPH30O Radio files, etc 3- Calkulin's_4.4+_Deodex_System.zip
albuser said: My actual os is: 11-20141008-snapshot-m11-bacon I flashed "File Type: zip Calkulin's_4.4+_Deodex_System.zip" and my opo restart continuously. I made a full wipe and reboot and oneplus one logo doesn't go away from the screen. I let it for 10 min and nothing happened. Now I backup my opo to the previous version and it is rooted. (controlled with root checker app) wich one of files i have to flash? 1- Stock Rooted 4.4.4/XNPH30O ROM (v1.1) 2- XNPH30O Radio files, etc 3- Calkulin's_4.4+_Deodex_System.zip Click to expand... Click to collapse any help?
what are the radio files? ---------- Post added at 05:26 PM ---------- Previous post was at 04:30 PM ---------- is anyone here? ---------- Post added at 05:31 PM ---------- Previous post was at 05:26 PM ---------- is anyone here?
ubuntu on surface RT
Is it possible to install Ubuntu on surface RT?
We can only wish :$
Look here :- https://help.ubuntu.com/community/UEFI#SecureBoot here :- http://www.howtogeek.com/175641/how-to-boot-and-install-linux-on-a-uefi-pc-with-secure-boot/ and here :- http://www.pcworld.com/article/3026...nt-secure-and-threatens-even-windows-pcs.html
It as actually been done. Unfortunately it's not public, I'm sure someone will know where to find some more info tho Google ms16-094 exploit to find out more ---------- Post added at 09:20 PM ---------- Previous post was at 09:13 PM ---------- Also.... "Details on how to evade the Secure Boot defenses are not public. Although, before unlocking the bootloader, we're told you should run manage-bde -protectors C: -disable to make sure BitLocker is disarmed, or your slab won't boot"
J7 2016 OTG problem
I'm unable to use otg on my galaxy J7 2016. otg cable is showing connected but pen drive is not detected by phone.
Just reboot your phone and clear cache ---------- Post added at 02:02 PM ---------- Previous post was at 02:02 PM ---------- Or just go to file manager info and clear data
[ROM][STOCK][Silent OS 3.0.14] Blackphone 2 (BP2) + ROOT
[UPDATED 2017/08/21] All I felt it would make sense to start a new thread for the Blackphone 2, with an original ROM. Here is: Blackphone BP2 3.0.14 ROM (RoW edition) In order to install it you must be on 3.09. install via original recovery... which is here... And for those who want the TWRP, here it is. Root (I know you been waiting for it...) You got two options, let's start with an easy one: Magisk 1) Download the latest version (ZIP file). copy to the sd card. 2) Boot to TWRP recovery 3) install 4) reboot. install the APK either from the play store or via a direct link (my preferred path) 5) Welcome to the brave world of root 6) Read the guide! More... soon Love
Aloha Friend, links below (RoW edition) do not work (#8026) Not authorized: Link has been deleted). Thx for your help Cheers
Apostrike said: Aloha Friend, links below (RoW edition) do not work (#8026) Not authorized: Link has been deleted). Thx for your help Cheers Click to expand... Click to collapse silent circle would it be behind deleting files !
Is it a joke? I tried to download the 3.0.9 row but here is the message that i received: " BP2_3.09_full_row.zip Apr 10, 2017 7:53 PM 808.2 MB 0% File too large to download with browser decryption. What does exactly it mean? Thank you. ---------- Post added at 04:53 PM ---------- Previous post was at 04:36 PM ---------- I did it, I downloaded with chrome, but strange that was impossible to donwload it with firefox on linux.... ---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ---------- I confirm. It's a joke. Download file BP2_3.09_full_row.zip File Date Size BP2_3.09_full_row.zip Apr 10, 2017 7:53 PM 808.2 MB 0.63% Timeout error downloading 1 item" It is absolutely absurd.
kenfalco_14 said: Is it a joke? I tried to download the 3.0.9 row but here is the message that i received: " BP2_3.09_full_row.zip Apr 10, 2017 7:53 PM 808.2 MB 0% File too large to download with browser decryption. What does exactly it mean? Thank you. ---------- Post added at 04:53 PM ---------- Previous post was at 04:36 PM ---------- I did it, I downloaded with chrome, but strange that was impossible to donwload it with firefox on linux.... ---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ---------- I confirm. It's a joke. Download file BP2_3.09_full_row.zip File Date Size BP2_3.09_full_row.zip Apr 10, 2017 7:53 PM 808.2 MB 0.63% Timeout error downloading 1 item" It is absolutely absurd. Click to expand... Click to collapse I tried to download it more then 30 times, always with same result. What is it gone wrong?
All ok. Download 3.09 ok. System updated to 3.10 Thank you androidblue
Sorry all, I accidentally enabled the "enhanced privacy" option. It is now fixed, and all should have no further problem to download.
androidblue said: Sorry all, I accidentally enabled the "enhanced privacy" option. It is now fixed, and all should have no further problem to download. Click to expand... Click to collapse The link to "REAL Blackphone 2 Silent OS 3.10 update (April 2017)" https://ln.sync.com/dl/c33995da0/63y9vshx-v9fwjz6c-3mz6yi7i-ky8ekwnr still says "(#8026) Not authorized: Link has been deleted". Could you fix that too? Thanks. Edit: also the link to the "original recovery" https://ln.sync.com/dl/9429c1020/rgjz6bep-dvmnd36x-r3j7q55c-3vrcmmsh is broken "(#8026) Not authorized: Link has been deleted"
The link is not working anymore... Could you please reupload it?
akikoo said: The link to "REAL Blackphone 2 Silent OS 3.10 update (April 2017)" https://ln.sync.com/dl/c33995da0/63y9vshx-v9fwjz6c-3mz6yi7i-ky8ekwnr still says "(#8026) Not authorized: Link has been deleted". Could you fix that too? Thanks. Edit: also the link to the "original recovery" https://ln.sync.com/dl/9429c1020/rgjz6bep-dvmnd36x-r3j7q55c-3vrcmmsh is broken "(#8026) Not authorized: Link has been deleted" Click to expand... Click to collapse Hi all I can assure you that I didn't delete the links. The files still exists, but the link have been deleted. I'm going to update the links and provide more soon to hopefully prevent this silly act of reporting the files are illigal. Silent Circle - if you're behind this, please stop. This is unprofessional.
androidblue said: In order to install it you must be on 3.09. install via original recovery... which is here... Click to expand... Click to collapse How do you install this recovery_BP2_310_ORIGINAL.img file? Thank you for these files.
akikoo said: How do you install this recovery_BP2_310_ORIGINAL.img file? Thank you for these files. Click to expand... Click to collapse 1) enter settings, about phone, scroll down to build, press until you are a developer, get out of about phone. 2) enter developer menu, allow oem unlock, shutdown phone, keep unconnected to computer/power. 3) install abd tools. 4) press the volume down, and then while being pressed press the power button. release when you see the "android" menu 5) magic time. connect cable to computer, type Code: fastboot flash recovery recovery_BP2_310_ORIGINAL.img fastboot reboot 6) phones reboot. quickly press the power up + power key before the phone reboots. if it rebooted, just keep on pressing them until it reboots again and release when you see the android screen. welcome to recovery.
root have been posted. Have fun and try to break everything (see 1st post in this thread)
hi, 4 is not working for me, no android menue, only reboot. 3.10 is installed. what do i have to do to get magisk installed ???
I updated to 3.0.10, but when i check updates, it still tells me update 3.0.10 available? also when i try install twrp, it still says phone locked despite oem and usb debugging being unlocked
Rapyer said: I updated to 3.0.10, but when i check updates, it still tells me update 3.0.10 available? also when i try install twrp, it still says phone locked despite oem and usb debugging being unlocked Click to expand... Click to collapse you missed an important step... unlocking it. boot into bootloader (lower volume + power key) connect to computer If I remember correctly type: Code: fastboot oem unlock-go and after your data will be deleted, you can now flash your recovery with TWRP.
Rapyer said: I updated to 3.0.10, but when i check updates, it still tells me update 3.0.10 available? also when i try install twrp, it still says phone locked despite oem and usb debugging being unlocked Click to expand... Click to collapse Oh, forgot to mention - why do you still get a message that update 3.0.10 is available: Your phone is still contacting to silent circle servers and it tries to brick you. soon to be explained how to stop it
Updates Hello: Phone already updated to 3.0.10 using your links. No problem at all. Thank you very much. Do you think you could provide additional updates in the near future? Thanks
Good afternoon! Make please the step-by-step detailed instruction on updating 3.10 and receiving root for simple users of lamers))
vendoelpiso said: Hello: Phone already updated to 3.0.10 using your links. No problem at all. Thank you very much. Do you think you could provide additional updates in the near future? Thanks Click to expand... Click to collapse Hi Most likely yes. We will see
Restrict data in background app - disable/enable in custom rom. Android 5.0
Hi I want to prepare my own ROM for smartwatch KW88. How to disable restrict data in background app on boot? It can be modify in build.prop?
Is your device an mtk based device ? If yes and mtk engineer mode is enabled on your custom rom , you can use mtk engineering mode tovset the background dsata restriction ---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ---------- If your rom supports mtk engineer mode , you can use the mtk engineer mode app to set the background data restriction
DE SEXIEST said: Is your device an mtk based device ? If yes and mtk engineer mode is enabled on your custom rom , you can use mtk engineering mode tovset the background dsata restriction ---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ---------- If your rom supports mtk engineer mode , you can use the mtk engineer mode app to set the background data restriction Click to expand... Click to collapse Yes, it is MTK device, but I need to disabled this option on first boot device.