Related
You've been waiting patiently for it and it's finally here.
Welcome to the
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Combination of easiest methods
Integrated Console
All-in-one root
99% Automization (e.g. Not possible to detect fully booted phone through adb/shell)
Logging enabled for easy debugging
Will be updated periodically (as, and if, new versions are released)
prboy1969 and megaghostgamer - for helping me get started with android and stuff! :good:
All name credits go to rhodiggah HERE
Indirect,VICODAN, and JohnnyCakeXM for their rooting methods/finds:
Indirect's Root and downgrade for Android 2.3.4 {Script included - ShiftySonofA script dl added)
VICODAN's [VIDEO GUIDE] FULL S-OFF ROOT for Evo SHIFT. Froyo (2.2) + Gingerbread (2.3.3+2.3.4)
JohnnyCakeXM's 2.3.4 Latest OTA[2.77.651.8] Downgrade!!
Q. Will this root the latest OTA (2.77.651.8)?
Yes. This utility supports all releases of Android for the EVO Shift
Q. Does this work on Linux?
Mostly. I am still ironing out a couple bugs, but since this is written in java, a large chunk of the work is already taken care of by that.
Q: My phone goes into a bootloop after rooting 2.3.4. Did I do something wrong?
No. That is supposed to happen. Assuming you already have the downgraded PG06IMG.zip on the root of your sdcard, you can immediately click "OK" in my utility when prompted so that it takes you to the bootloader to downgrade. If not, you need to turn off your phone, get the PG06IMG.zip on the sdcard and then manually go into bootloader (Power off/Battery pull then Power + VolDown)
Q: After downgrading to 2.2, I tried to temproot with Visionary and it gives me a black screen. How can I fix this? Thanks @asbrand!
Press the home button to exit Visionary, then open it again and attempt to temproot, it should go through this time. I dont know why this happens, but I've had it happen to me as well.
Q: Does this tool give me full S-OFF / unlocked bootloader? Thanks Nooblube
This tool gives you S-OFF (Nand unlocked), and also gives you an unlocked bootloader.
Before starting: Make sure you have installed the HTC USB drivers. If you have not, go to THIS thread, download the ZIP and install both files. Additionally, make sure your phone is formatted to FAT32. If not, make a backup, format it to FAT32, move your files back, and get started.
Windows only: If you have adb in your $PATH, you do not need to download the zip.
Linux only: You MUST download the adb_linux and place the files into the same directory as the utility, even if you ALREADY have adb in your $PATH (absolute file path must be used by utility when running on Linux)
The latest version of Java must be installed to run this utility. (Java 7)
Rooting 2.2
Downloads adb_windows, adb_linux, or adb_mac depending on your OS
Download the root2.2.zip file
Download the utility.jar file
Place the adb files into the same folder as the jar
Extract the root2.2 folder into the same directory as the jar (see picture). DO NOT RENAME THE FOLDER TO ANYTHING BUT "root2.2" OR IT WILL NOT WORK.
Run the utility, thoroughly following ALL prompts and prerequisites
Rooting 2.3.3
Run the 2.3.4 RUU (either one, preferably the 2.77.651.3 version)
Follow the instructions for rooting 2.3.4
Note: There is a method for rooting 2.3.3 directly but I couldn't test it (no RUU found)
Rooting 2.3.4
Follow steps above for rooting 2.2
Download the root2.3.4.zip and extract the FOLDER into the same directory as the utility (same way as with root2.2 folder)
DO NOT RENAME THE FOLDER TO ANYTHING BUT "root2.3.4" OR IT WILL NOT WORK.
Run the utility, throughly following ALL prompts and prerequisites
Folder structure
Warning
You will be on older radios after rooting. Download the ZIP with the most recent radios, WiMAX, and touchscreen firmware from HERE.
Instructions to update:
Download the file from the URL above. Make sure that it is named "PG06IMG.zip" (without the quotes, on Windows 7 the extensions are hidden by default so make sure you are not naming it "PG06IMG.zip.zip" by accident)
Place the file on the root of your sdcard (meaning not inside any folders, just copy and paste to main sdcard drive)
Turn off your phone and go into bootloader by pressing Power+VolDown
Your phone should find the PG06IMG.zip file and commence the update process, follow the onscreen prompts to update the firmware on your phone
Note: This does not eliminate your root privileges or unroot your phone, it merely updates the radios and touchscreen.
IMPORTANT: Your sdcard must be formatted to FAT32 for this to work. If it is not, make a back up, format, and then move your files back and then start this update process.
Note: Please realize that I am only one person with one phone. I could not have possibly tested all scenarios, so if you find a bug, post what the bug is and I will fix it as soon as possible.
As a precautionary note, also check the md5sum of the files on your own. The utility checks some core files, but the rest is up to you, I recommend using THIS commandline one.
DISCLAIMER: I take no responsibility for your actions. However, I would be more than happy to troubleshoot any problems you encounter, post what your problem is and attach the log file too.
ALL Files Here: http://d-h.st/users/CNexus/?fld_id=7741#files
Take the most recent version of the desktop utility.
Other Links (Can be reached through link above as well)
Individual files here (if md5sum does not match): http://d-h.st/users/CNexus?fld_id=10377#files
Utility JAR's: http://d-h.st/users/CNexus?fld_id=10378#files
(New!) http://d-h.st/users/CNexus/?fld_id=10376#files
Code:
[B]1/13/13 - v0.50 [/B]
- Added ability to flash files to different partitions
- Reboot menu is now fully functional (no longer experimental)
- Added link to standalone "FlashImage Tool v1.0" in OP, also packaged in the utility now
[B]12/10/12 - v0.49 [/B]
- Internal md5sum checking for all dependent files (no need to download md5sum.exe anymore)
- Optimized code, removed unnecessary files -> significantly smaller file size. (50.48 KB)
- Reboot menu now included ( Advanced tab > Reboot Menu) [[B]Experimental[/B]]
[B]12/2/12 - v0.47[/B]
- Miscellaneous bug fixes. 2.77.651.8 root now works (accidentally checking Android version instead of firmware number)
[B]11/30/12 - v0.46[/B]
- Added the ability to toggle ADB connection between Wifi and USB.
[B]11/29/12 - v0.44[/B]
- [B]IMPORTANT[/B]: Fixed the 2.3.4 not running (accidentally running 2.3.3 root, which I had left unimplemented, hence the window staying blank and the log being blank as well). The utility should now function correctly for everyone using it.
[B]11/27/12 - v0.42[/B]
- Fixed md5sum checking for hboot_eng.nb0 that would sometimes be faulty.
[B]11/26/12 - v0.41[/B]
- Added support for Linux. Still a couple bugs, but they will be ironed out quickly. Note: Must give adb and md5sum executable permissions for it to work.
[B]11/22/12 - v0.4[/B]
- Initial build released, tested from all software versions
- Integrated console added
- Logging added
many thanks, hopefully i wont force myself into trying this
-somebody- said:
many thanks, hopefully i wont force myself into trying this
Click to expand...
Click to collapse
Thank YOU for the kind remarks!
CNexus said:
Thank YOU for the kind remarks!
Click to expand...
Click to collapse
Thanks man . Will try this out next time I need to Root a Shift. Which is more often than you would think .
prboy1969 said:
Thanks man . Will try this out next time I need to Root a Shift. Which is more often than you would think .
Click to expand...
Click to collapse
Ahhhh the irony.
I just had to root my phone manually because it won't show up in adb long enough for my utility to run everything lol
CNexus said:
Ahhhh the irony.
I just had to root my phone manually because it won't show up in adb long enough for my utility to run everything lol
Click to expand...
Click to collapse
Ummm.... yeah
Nice work, I might try it on this extra shift I picked up for parts/spare etc.
BigSplit said:
Nice work, I might try it on this extra shift I picked up for parts/spare etc.
Click to expand...
Click to collapse
Thanks!
Sent from my JB'd speedy
prboy1969 said:
Ummm.... yeah
Click to expand...
Click to collapse
Yeah I think I broke my phone in the process of making this
It won't root even when I do it manually...
And it just stopped showing up in ADB completely
Good thing my upgrade isn't too far off....
If you broke your phone, how can we know this is safe? I'm hoping it is, because if so it's greatly needed and appreciated.
hgelpke said:
If you broke your phone, how can we know this is safe? I'm hoping it is, because if so it's greatly needed and appreciated.
Click to expand...
Click to collapse
I broke my phone testing...but ive also dropped it. This tool is try at your own risk, but it is safe to use, to the best of my knowledge.
I believe my problem is a hardware issue anyway.
Sent from my JB'd speedy
Perfect timing on this, I had done the 2-step unroot process becuase I was going to sell my Shift on craigslist after upgrading to the Photon Q, but the Q is proving to have all sorts of problems, especially with the LTE network, so I think I may follow Vicodan's footsteps and return to the Shift. I figure if his expertise can't overcome the software and network problems on the Q, I can't either.
---------- Post added at 11:16 AM ---------- Previous post was at 10:58 AM ----------
Ok, so first attempts aren't going so well. First a couple notes:
Might want to include a note about Java being required to run a .jar - new PC didnt have it installed yet and double-clicking the .jar didn't do anything at all).
Also, in the instructions you don't mention downloading md5sum.exe and putting it in the folder, but I see it later in the directory tree. My first run of the utillity I didn't have it there, second attempt its there, but same results:
When I run the utility (v0.42), it comes up with the Prerequisites screen, I confirm my settings, then click next (or ok, or whatever the button said). The utility recognizes my phone and software version (2.77.651.3). I click Root Now! and the utility's console blanks out, and nothing happens, either in the utility or on my phone. Is there anything I can do to see what its hanging up on?
Edit: Here's my directory tree:
Code:
c:\RootEvoShift>dir
Volume in drive C has no label.
Volume Serial Number is 104A-11BE
Directory of c:\RootEvoShift
11/28/2012 11:09 AM <DIR> .
11/28/2012 11:09 AM <DIR> ..
11/28/2012 10:50 AM 191,488 adb.exe
11/28/2012 10:50 AM 96,256 AdbWinApi.dll
11/28/2012 10:50 AM 60,928 AdbWinUsbApi.dll
11/28/2012 11:04 AM 0 log-11282012.log
11/28/2012 11:09 AM 0 log-11282012.log.lck
11/28/2012 11:07 AM 2,048 md5sum.exe
11/28/2012 10:50 AM <DIR> root2.2
11/28/2012 10:49 AM <DIR> root2.3.4
11/28/2012 10:48 AM 41,821 speedy-root-utility-v0.42.jar
7 File(s) 392,541 bytes
4 Dir(s) 367,063,105,536 bytes free
cmags said:
Perfect timing on this, I had done the 2-step unroot process becuase I was going to sell my Shift on craigslist after upgrading to the Photon Q, but the Q is proving to have all sorts of problems, especially with the LTE network, so I think I may follow Vicodan's footsteps and return to the Shift. I figure if his expertise can't overcome the software and network problems on the Q, I can't either.
---------- Post added at 11:16 AM ---------- Previous post was at 10:58 AM ----------
Ok, so first attempts aren't going so well. First a couple notes:
Might want to include a note about Java being required to run a .jar - new PC didnt have it installed yet and double-clicking the .jar didn't do anything at all).
Also, in the instructions you don't mention downloading md5sum.exe and putting it in the folder, but I see it later in the directory tree. My first run of the utillity I didn't have it there, second attempt its there, but same results:
When I run the utility (v0.42), it comes up with the Prerequisites screen, I confirm my settings, then click next (or ok, or whatever the button said). The utility recognizes my phone and software version (2.77.651.3). I click Root Now! and the utility's console blanks out, and nothing happens, either in the utility or on my phone. Is there anything I can do to see what its hanging up on?
Edit: Here's my directory tree:
Code:
c:\RootEvoShift>dir
Volume in drive C has no label.
Volume Serial Number is 104A-11BE
Directory of c:\RootEvoShift
11/28/2012 11:09 AM <DIR> .
11/28/2012 11:09 AM <DIR> ..
11/28/2012 10:50 AM 191,488 adb.exe
11/28/2012 10:50 AM 96,256 AdbWinApi.dll
11/28/2012 10:50 AM 60,928 AdbWinUsbApi.dll
11/28/2012 11:04 AM 0 log-11282012.log
11/28/2012 11:09 AM 0 log-11282012.log.lck
11/28/2012 11:07 AM 2,048 md5sum.exe
11/28/2012 10:50 AM <DIR> root2.2
11/28/2012 10:49 AM <DIR> root2.3.4
11/28/2012 10:48 AM 41,821 speedy-root-utility-v0.42.jar
7 File(s) 392,541 bytes
4 Dir(s) 367,063,105,536 bytes free
Click to expand...
Click to collapse
Thats odd, I downgraded my phone from 2.77.651.3 before I even posted...the thing is I can't even test it anymore because my phone will not show up in ADB (hardware issue, I'm gonna be taking it in soon)
Can you attach the log file the utility makes?
And also, try running the utility again, when it hangs, open a cmd window and type "adb kill-server" and then "adb devices" and make sure your device is showing up as "device"
Sent from my JB'd speedy
Adb shows my device, but the logfile is 0 byte. Nothing to see in it. Any way to get at the backend java console to see what's happening, or maybe you have a debug build?
cmags said:
Adb shows my device, but the logfile is 0 byte. Nothing to see in it. Any way to get at the backend java console to see what's happening, or maybe you have a debug build?
Click to expand...
Click to collapse
Did you install the latest version of java? My program runs using java 7
Sent from my JB'd speedy
Yes, installed the latest today from java.com.
cmags said:
Yes, installed the latest today from java.com.
Click to expand...
Click to collapse
Sorry dude, I don't know why its not logging or why it hangs :\
I'll take a look at the code again and see, but I swear that I downgraded from 2.3.4 just the other day...
I will try to test it on my own phone but I've been having issues connecting it to adb
Sent from my JB'd speedy
I am not responsible for any damage that may or may not occur to your device.
If you use my recovery in your project link back to this thread, and give me credit in your thread for my recovery.
This is the Linux version of TWRP tethered recovery and CWM tethered recovery.
TWRP 2.8.6.0 recovery, currently tested on two tablets, venue 3830, iview -1700
screen for 1-700 is 1024x600 landscape
screen for venue 3830 800x1280 portrait
Purpose of this guide is to root intel tablets using Linux computer.
This project includes the work of people perhaps more.
This version includes 4 triggers.
@vampirefo
Linux Fastboot Binary, intel compatible cwm recovery.
http://forum.xda-developers.com/dell-venue/general/dell-venue-8-cwm-unsecure-boot-recovery-t2866925
@Chainfire
super user package update-supersu-vxxx.zip
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
@social-design-concepts
recovery.launcher, recovery.envsetup, recovery.trigger, triggers and for sharing his work.
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
http://forum.xda-developers.com/showthread.php?t=2681783
TeamWin for their great recovery
https://github.com/omnirom/android_bootable_recovery/tree/android-5.1
Download
https://www.androidfilehost.com/?fid=24052804347784850
Download release.zip extract some where, choose which recovery you want to run, rename to recovery.zip, then execute trigger choice. make sure trigger script is executable All four triggers are included in the trigger script.
1. cwm_recovery.zip
2. twrp_3830_recovery.zip
3. twrp_i700_recovery.zip
To use trigger script, open terminal in directory where files have been extracted.
Code:
adb reboot bootloader
choose which trigger you want to use.
Trigger 1
Code:
sudo ./trigger 1
Trigger 2
Code:
sudo ./trigger 2
Trigger 3
Code:
sudo ./trigger 3
Trigger 4
Code:
sudo ./trigger 4
To allow recoveries to work on more devices delete the contents of /etc, the files in /etc are for my device and other devices similar removing the contents of /etc allows @social-design-concepts tools to generate a fstab for your particular device.
Change log 7-31-2015
Twrp has been updated to 2.8.7.0
This version includes @social-design-concepts latest trigger (fbrl.trigger) and launcher (recovery.launcher), Also included is a script for Tesco Hudl 2 users, this device requires addition info to launch fastboot commands.
For Tesco Hudl 2 users use hudl2 script instead of trigger, or you can still manually edit trigger if you want.
If you would like your device added posted required information about your device.
1. Name of Device
2. Screen Size of device
3. Your device portrait or landscape mode in stock recovery?
Sent from my T1 using Tapatalk
can you tell me bug
---------- Post added at 08:28 AM ---------- Previous post was at 07:56 AM ----------
test work on zenfone 2
But flash zip not work
and only mount sdcard
can you Screen Size for zenfone 2 Full HD ?
tks
ps:UI work good
29y6145 said:
can you tell me bug
---------- Post added at 08:28 AM ---------- Previous post was at 07:56 AM ----------
test work on zenfone 2
But flash zip not work
and only mount sdcard
can you Screen Size for zenfone 2 Full HD ?
tks
ps:UI work good
Click to expand...
Click to collapse
@TheSSJ has made a TWRP recovery for your device.
http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
Sent from my Venue 8 3830 using Tapatalk
Works good for Lenovo Yoga Tablet 2 10150F. KitKat 4.4.2 - Trigger 3, CWM only
Thank you!!!
Dell Venue 7370
Works : Trigger 1
Thank you very much for the Linux version! You saved the day for me!
Hey I forgot you... Thank you for your effort! CWM works, twrp does not. No worries.
Confirmation number: 0YV98561UW917140R
workdowg said:
Hey I forgot you... Thank you for your effort! CWM works, twrp does not. No worries.
Confirmation number: 0YV98561UW917140R
Click to expand...
Click to collapse
Did you remove the files from /etc on twrp? Anyway thanks for the donation.
Sent from my NXA8QC116 using Tapatalk
vampirefo said:
Did you remove the files from /etc on twrp? Anyway thanks for the donation.
Sent from my NXA8QC116 using Tapatalk
Click to expand...
Click to collapse
Doh... I guess I should read and reread... I'll try that now. Thanks.
---------- Post added at 12:54 PM ---------- Previous post was at 12:40 PM ----------
workdowg said:
Doh... I guess I should read and reread... I'll try that now. Thanks.
Click to expand...
Click to collapse
Still errors but works now. "FAILED (status read failed (No such device))".
Thanks
workdowg said:
Doh... I guess I should read and reread... I'll try that now. Thanks.
---------- Post added at 12:54 PM ---------- Previous post was at 12:40 PM ----------
Still errors but works now. "FAILED (status read failed (No such device))".
Thanks
Click to expand...
Click to collapse
Thanks,
I will be updating @social-design-concepts binaries in a few days, and updating the twrp recoveries.
Working - Yoga Tablet 2 - 1050F
-- Lollipop - trigger 4
-- KitKat - trigger 3
Recoveries have been updated.
Change log 7-31-2015
Twrp has been updated to 2.8.7.0
This version includes @social-design-concepts latest trigger (fbrl.trigger) and launcher (recovery.launcher), Also included is a script for Tesco Hudl 2 users, this device requires addition info to launch fastboot commands.
For Tesco Hudl 2 users use hudl2 script instead of trigger, or you can still manually edit trigger if you want.
Thanks for the update!
BTW... Links below in OP are dead or wrong...
@social-design-concepts
recovery.launcher, recovery.envsetup, recovery.trigger, triggers and for sharing his work.
http://forum.xda-developers.com/andr...p-cwm-t2975096
http://forum.xda-developers.com/show....php?t=2681783
Click to expand...
Click to collapse
Links have been changed on OP, sometimes xda changes their short links.
hello. Would like to try this on my lenovo yaga tab 3 pro.
Just wanted to know is this dangerous/chance of brick or all very temporary?
joesnose said:
hello. Would like to try this on my lenovo yaga tab 3 pro.
Just wanted to know is this dangerous/chance of brick or all very temporary?
Click to expand...
Click to collapse
No this can't brick your device, once rooted you could brick your device if you delete needed files.
Sent from my BLU ENERGY X PLUS using Tapatalk
removed.
Sent from my Lenovo YT3-X90F using Tapatalk
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
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.
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