Related
Hello everyone!
I've been coming to this site for a few weeks now. What a ton of helpful information! I finally decided to create an account though, because I had a question I couldn't seem to get answered.
I'm fairly new to android, this a100 tablet is my first device I've "owned" but have worked with and have a little experience with other android devices. I'm pretty good with Linux, being an IT admin. I'm sure my issue is minute, I'm just stumped as to what is causing the problem.
I've upgraded my a100 to the latest ICS build. I've installed the drivers from acer (unfortunately after windows detected the device drivers first) and I am trying the quickroot method I found in the development forum. I can run the windows .bat file, and everything goes through CMD so quickly that I am not able to read whats happening, but it reboots my device and says root achieved. I've got super user installed, it won't find any updates for the SU in the settings menu, says failed every time it looks for them. I open terminal emulators, still getting $ instead of #. Tried a terminal command I read about for root, where I put the root and SU files at mnt/sdcard and use the command to install, no luck.
Am I truly rooted? I cant tell anymore. I just want to unlock the bootloader, install cwm, and flash an a500 custom rom to it.
Any help at all is greatly appreciated. I'm sure I'm overlooking something, but Im not sure. I can add a legacy device, add Acer's ADB driver, but the fastboot one gets a code 10 and cannot start.
Thanks!
pbrady5 said:
Hello everyone!
I've been coming to this site for a few weeks now. What a ton of helpful information! I finally decided to create an account though, because I had a question I couldn't seem to get answered.
I'm fairly new to android, this a100 tablet is my first device I've "owned" but have worked with and have a little experience with other android devices. I'm pretty good with Linux, being an IT admin. I'm sure my issue is minute, I'm just stumped as to what is causing the problem.
I've upgraded my a100 to the latest ICS build. I've installed the drivers from acer (unfortunately after windows detected the device drivers first) and I am trying the quickroot method I found in the development forum. I can run the windows .bat file, and everything goes through CMD so quickly that I am not able to read whats happening, but it reboots my device and says root achieved. I've got super user installed, it won't find any updates for the SU in the settings menu, says failed every time it looks for them. I open terminal emulators, still getting $ instead of #. Tried a terminal command I read about for root, where I put the root and SU files at mnt/sdcard and use the command to install, no luck.
Am I truly rooted? I cant tell anymore. I just want to unlock the bootloader, install cwm, and flash an a500 custom rom to it.
Any help at all is greatly appreciated. I'm sure I'm overlooking something, but Im not sure. I can add a legacy device, add Acer's ADB driver, but the fastboot one gets a code 10 and cannot start.
Thanks!
Click to expand...
Click to collapse
You do have Superuser and it's su binary, so yes, you should be rooted. Try this app if you want to be sure: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en.
Besides the root checker that theonew pointed you too I have always found downloading and installing Titanium Backup from the market as a surefire way of determining if root was successful.
Upon first run it will ask for SU permissions and should present you with a dialog box asking if that is ok with you. I always answer yes and make sure that the "remember this selection" box is checked.
That will be the first sign that you are rooted. Then, The program should provide you with a summary where you will see a bunch of green check marks. Most notably Busy Box should have a green checkmark and it will probably state Installed from program or something to that effect.
Wahla, you have confirmed you are rooted.
BTW, I recommend this program for it's ability to backup your apps which makes flashing new rom's easier as the apps can then be restored after performing a data wipe which is usually a requirement of flashing new Roms. Just be sure you understand that sometimes restoring app's AND their associated DATA can mess with a new ROM. In that case you can simply install the APP only. which still saves you the time and bandwidth of re-downlaoding it from the market.
Good luck and welcome to the playground.
This tutorial will teach you how to root, install a custom recovery and deodex the ROM on your Mediatek processor smartphone. You can use this tutorial for other Android devices too, Lenovo or not.
I myself own a Lenovo A390 and I have rooted, installed recovery and deodexed using these software tools, without any pain. And I assure you, it will be extremely rare that anything can go wrong. And you don't need a computer to root or install recovery-yes, you can do it on your phone itself.
But let's get some things straight:
1. Rooting/installing recovery voids your warranty.
2. If you're not using a Lenovo device or a device that runs on a MediaTek processor, I recommend that you search for a version of recovery appropriate for your processor.
3. The chances of damaging your phone using these tools is extremely rare, trust me, but in case anything goes wrong, I, OR THE DEVELOPERS OF THESE TOOLS, OR XDA-DEVELOPERS WILL NOT BE RESPONSIBLE FOR ANY INTERNAL/EXTERNAL DAMAGE TO YOUR PHONE.
How to root your Lenovo a390:
1. Download Framaroot: http://forum.xda-developers.com/showthread.php?t=2130276 Note: Framaroot may not work on all Android devices. Please see compatibility list in the link.
Framaroot is an Android app created by XDA user alephzain. It allows you to root your device directly from your Android device-please click on link above to view full compatibility list. Download and Install this app. If it says "Installation blocked", go to your phone's Settings>Security and tick the "Unknown Sources" box. (Believe me, there are n00bs )
2. Open Framaroot. For the a390, there is only one exploit-Boromir, since it's a Mediatek powered device. Select Boromir.
3. Now you see two buttons: Install Superuser and Install SuperSU. You need to select only one of them. Framaroot will then root your device and install Superuser/SuperSU. (Superuser/SuperSU are apps which control root operations on your device ie. ensure no app uses root features without your permission-it is a MUST.)
The choice is up to you, but I'd recommend Superuser since it's like the Industry standard of rooted Android phones.
4. Reboot your phone. You'll find Superuser installed. Open it, swipe from left to right to access Superuser settings. The su binary is outdated and it'll appear in a red font. Tap it to update su binary.
This is proof enough that your phone is rooted, but if you really need to see, here's one more step.
5. Install Root checker from Google Play Store: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck
Run this app, and if your phone is rooted, Superuser will come up automatically asking you whether Root Checker should be granted permission- press Yes and root Checker will deliver the result.
That's it-congratulations, you've rooted your a390 without any pain. Now you can flash a recovery, install Busybox, overclock your phone, get rid of the dumb apps Lenovo has included with the a390.... Enjoy! :laugh:
How to install a recovery
Now, there are two recoveries that rule the Android universe: ClockworkMod Recovery (CWM), and TeamWin Recovery Project (TWRP). The bad news is, neither is officially available for the Lenovo A390 or most of MediaTek devices. But where there's a will, there's a way- and some anonymous Android developer has created TWRP recoveries for the entire Lenovo smartphone series. <salute to the unsung hero> I used one specially customised for the A390, and it works fabulously.
First of all, ensure that your phone is rooted. If not, read the tutorial above.
1. Download this recovery.img file from this Google Drive: https://drive.google.com/file/d/11-...c9b-MfFTWpi9D_vBI0oVISPgRVcB/edit?usp=sharing
2. Install Recovery Tools-Flasher from the Google Play Store: https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
3. Now press "Flash Recovery" button, it will open a file browser. Select the recovery.img file you downloaded from the file browser.
4. It should show a dialog box that says Flashing done. Press OK to boot into recovery. Press OK, and you'll see the TeamWin IdeaPhone load screen-and boot into TWRP.
Congrats, you've installed the recovery. Now you can install custom ROMs on your phone and backup your phone's kernels as protection against troubles. Enjoy! :highfive:
How to deodex your phone's ROM
Sadly, you cannot do this using your phone. You'll need a Windows PC for this process, a good Internet connection as you'll have to download large files for this process, and plenty of time.
Here's a good XDA Developers Tutorial on how to deodex your rom, complete with step-by-step explanation and screenshots: http://forum.xda-developers.com/showthread.php?t=2374008
There you go. If you followed my tutorial completely, you are now a proud owner of a rooted, recovery-flashed, deodexed MediaTek device/Lenovo A390.
Enjoy!
Please hit Thanks button if my post helped you.
Hi All,
I have a LG G3 (European d855) that was previously running CyanogenMod 13, a long time ago it refused to install future updates either over the air or flashing, I left it a long time as it was only a secondary phone I used for work.
I have since decided to flash a fresh OS (Lineage and also tried AOSCP) as the only important thing on this phone was my contacts. At first TWRP was giving me an error 7 no matter what ROM I downloaded, I read to change the script in META-INF to bypass the security feature to remove the "Asserts" re-package and try again. So I used the adb push command to add the new packaged file to the device and attempted to flash. I now get a new error "could not find META-INF/com/google/android/update-binary" in the zip file (the binary file was never edited).
Also as a side note I can no longer connect with adb when I had no issues before. The phone currently has no OS and refuses to install any package.
Could I possibly have corrupt partitions?
Any help will be much appreciated
So I am pretty new to this, but here goes....
About a month ago I got some help from a friend and downloaded lineage OS 15.1 to my Lenovo p2a42 device. Very happy with everything, until yesterday when the phone began to vibrate and then proceed to shut down with a blue indicator light showing. After some fiddling and attempts to get the latest update of lineage, I got stuck in my first boot loop. After all my various attempts to solve the problem, I decided to do a clean wipe and reinstall lineage. Which I've done successfully I believe, no crashes yet. What I am having trouble with now is remembering how to download the first applications since I don't have the Gsuite or Gapps downloaded. I remember my friend mentioning a problem with the stock file manager for lineage and I believe that is one of the first applications we downloaded along with the apk pure app store.
If anyone can help this newbie figure out how to download the apk mirror to my device without an appstore, I would appreciate it.
>maybe the answer is to download to my laptop first and then use adb to flash it to my device?
Thanks for the help!!
If you want to have Google apps on your phone, search for Open GApps and download for ARM64 devices (nano package is recommended). Then flash it alongside LOS in TWRP. You will have Google Play Store installed.
But, if you only want APKPure store then you must download the APK from their website (either via computer then move it to your phone, or by using default LOS browser). Navigate to your downloaded APK using file manager and open it, you will have a prompt to install it or not. That's pretty much it though.
XDAquareis said:
If you want to have Google apps on your phone, search for Open GApps and download for ARM64 devices (nano package is recommended). Then flash it alongside LOS in TWRP. You will have Google Play Store installed.
But, if you only want APKPure store then you must download the APK from their website (either via computer then move it to your phone, or by using default LOS browser). Navigate to your downloaded APK using file manager and open it, you will have a prompt to install it or not. That's pretty much it though.
Click to expand...
Click to collapse
I downloaded apk pure directly on my mobile from the website (not interested in GApps). It opens in the LOS default file manager and there are basically no options to run it. I think this is because the root may be disabled, my boot loader is unlocked, but it says adb only in my developer options settings. I am new to using adb to flash an apk. I was able to flash lineage, but not sure how to install the apk. For instance, should my phone be on when I enter command install xxx.apk or should it be in recovery mode or boot mode? I tried once already and the apk install failed, not sure what I am doing wrong here. Thanks for the response above.
LineageP2newb said:
I downloaded apk pure directly on my mobile from the website (not interested in GApps). It opens in the LOS default file manager and there are basically no options to run it. I think this is because the root may be disabled, my boot loader is unlocked, but it says adb only in my developer options settings. I am new to using adb to flash an apk. I was able to flash lineage, but not sure how to install the apk. For instance, should my phone be on when I enter command install xxx.apk or should it be in recovery mode or boot mode? I tried once already and the apk install failed, not sure what I am doing wrong here. Thanks for the response above.
Click to expand...
Click to collapse
Answered my own question. Was able to download a file manager using adb, this allowed me download apk mirror.
Teclast M40 Pro Discoveries​Various helpful points of knowledge to unlock your bootloader, to root, and use your tablet.
Problem: Where can I obtain the official firmware?
Solution: Teclast Website
Usage: type M1A3 in search
Problem How can I unpack "pac" files?
Solution: Build C utility divinebird / pacextractor
Solution: Download pre built Linux executable pacextractor.zip
Usage: >./pacextractor Firmware.pac
Bash:
git clone https://github.com/divinebird/pacextractor
cd pacextractor
make
Problem: I need tools to flash my device
Solution: Download the latest SPD Upgrade Flash Tool SPD_Upgrade_Tool
Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools
Solution: Download and install 2010 Visual C++ Distribution
Problem: I want to unlock my bootloader. (Window and Linux kit)
Solution: Download TeclastM40Pro_Unisoc_UnlockTools.zip
Usage: Read readme file.
Problem: How can I remove the dm_verify warning on boot up after unlocking the bootloader?
Untested Solution: digitally sign the vbmeta partition and write it back. See [Tutorial] How to create a custom signed vbmeta.img
Problem: I want to root my device.
Solution: Modify boot.img with Magisk, then sign.
Usage: Upload to your device's download directory, the current boot.img read from your device, or from the same version firmware. Then install Magisk app from here. Use Magisk to patch the boot.img. Sign the partition. Then flash back the signed magisk version of boot.img to "boot_a" partition. Guide to flashing single partition at Hovatek Website
Problem: I need to emergency flash my device?
Solution: Currently only from Windows, use SPD Upgrade Tools to reflash firmware.
Usage: From the tablet powered off, or if boot looping. Hold down the power-button and volume-down for five seconds, release the power-button, and keep the volume-down button still held for another five seconds, then release or release if the detected earlier. Windows and SPD tools should then detect your device to flash.
Problem: I want to improve my Telcast M40 Pro
Solution: List of suggested apps below;
FDroid App Store F-Droid Website
Aurora > via FDroid. App store allowing the direct download from Google Playstore, without your own account.
Lawnchair > via FDroid. Fast open source sophisticated launcher.
AdAway > via FDroid. Removes adverts whilst using apps.
TrackerControl > via FDroid. Manages apps access to internet, and blocks spyware and trackers.
.
Problem: I want root mode without the effort of hacking a rom partition.
Solution: For those with World version Teclast M40 Pro device, here is a signed rooted boot partition I created. Read the readme file inside the zip. You will require an unlocked device, windows setup with USB drivers for Teclast, the complete firmware from Teclast website, and SPD Update Tools installed. If you're successful, then on rooting you will need to install Magisk app to get root active. Magisk will reboot once to finalise.
Download : TeclastM40Pro_ROW__v1p0_signedboot_magiskrooted.zip
Download : TeclastM40Pro_ROW__v1p2_signedboot_magiskrooted.zip
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
laurorual said:
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
Click to expand...
Click to collapse
Sorry for replying late. I got no indication of the response. To the problem, I can only suggest getting a different version of SPD or m aking sure your computer system is properly updated. I hope you've already solved the issue!
Maybe you're experiencing, "Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools" See above for solution.
I've noticed a new ROM for world edition, "M40 Pro(M1A3)_Android 11.0_ROW V1.02_20220525", but not getting any system update options for OTA. People flashing their systems may want the latest firmware!
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Is there any way to install Magisk modules?
Thanks for your post, it helped me a lot to unlock my tablet.
Edit: My version is the M1A1 firmware V1.03_20210804
Edit 2: Finally, when updating my tablet with the root file that is in the post, it did not allow me to install any Magisk module, the solution is to download version 24.3, and update automatically, without changing to a higher version of Magisk
Glad you worked it out Miny !!! Sorry the warning emails for new posts have been going to a gmail account I no longer use.
Also your hardware maybe different and require it's own unique firmware and boot images. It seems the cracking in similar though.
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Hi there.
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked?
Thanks in advance
rubsbcn said:
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked? Thanks in advance
Click to expand...
Click to collapse
To tell you the truth, not sure. Most SoC are impossible or near impossible to brick. They usually allow for an injection or have a read only boot section. Other words you could test. Also research difference in hardware between models, and that may indlicate if something may not work. The kernel/drivers are the improtant aspect.
jorkusjorkus said:
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Click to expand...
Click to collapse
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
minyfriki said:
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Click to expand...
Click to collapse
What I found works, is when using SPD Research Tool, load up the firmware.pac and then go into settings and click "Select All Files" and again to unselect, which leaves the default required items.
Then manually change BOOT to the Magisk img. Then click on all VBMETA types, and UBOOT_LOADER (may not be required though). Then flash.
You should get bootable tablet (no looping). Warning: UserData partition is written over.
I'll share my Magisk image for v1.2
e8hffff said:
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I'm using the same version as you on the same OS. After some research it seems like unlock_bootloader was removed in this commit from 2018. From what I can tell, unlock_critical does something else (unlock_bootloader runs
Code:
fb_queue_download("unlock_message", data, sz); fb_queue_command("flashing unlock_bootloader", "unlocking bootloader");
while unlock_critical runs
Code:
do_oem_command("flashing", "unlock_critical" and doesn't take the signature argument);
)
I'll see if I can compile the older version with the needed command.
What about my other questions?
Issue: Android not starting. I had the infinite restart when plugged in the usb. I tried to reload the installation package (succeeded), but didn't fixed the issue. Battery was not charging yet. When I started the Teclast M40 pro, the logo showed up, but the tablet turned off again.
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
dougcwb said:
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
Click to expand...
Click to collapse
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
e8hffff said:
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
Click to expand...
Click to collapse
I did the installation package process that the Teclast sent me. The last thing they told me to do was keep trying to install the package (wft?). Well, I just open the tablet, unplugged the battery for a while and after that it worked.
Maybe this resolved 2 things:
1-the battery was not properly connected in the first place, so when I plugged the 5 pin to the board it connected as it should.
2- Maybe there is a "memory" in the board attached to the battery that was bricked (or something like that) when I pulled off the plug, this memory was reseted.
BTW, when the tablet came to life again, the battery was at 87%.