yashsingh1/xdaforums huggingface dataset:
[Android General] lion567:
Couldn't agree that it's easy. IMHO SP FlashTool is the most weired and worth documented tool.

AFAIK there are 5 different ways to restore stock recovery in case someone has TWRP installed, all of them, except first, required recovery.img from stock ROM:

1. When you flashed TWRP, you had to rename or remove /system/etc/install-recovery.sh script. Why? Because it restore stock recovery during system bootup! So if you boot in TWRP, restore original install-recovery.sh script with correct owners and permissions and reboot to system, then it'll done the trick.

2. If you have TWRP up and runnung, then you can put stock recovery.img on extenal SD card and flash it from withing TWRP (Install -> Image -> <select recovery.img> -> <select Recovery> -> <swipe to flash>)

3. If you have Android 5.0.1 on your tablet, then you have "modern" (unlocked) uboot and you can use fastboot command to flash stock recovery.img

fastboot flash recovery <path_to_recovery.img>

4. If you have root on your tablet, there are a lot of tools, which can help you flash stock recovery.img - Flashify, MobileUncle Tools etc.

5. Of course you can use SP FlashTool to flash recovery.img. Its also recomended to flash stock system.img, if you made any modifications to it (root, remove install-recovery.sh, etc), to have it untouched and your warranty valid.
[Android General] Old faithful:
The latest TWRP does include the option to root via Super SU, so all is well there :)

---------- Post added at 03:03 ---------- Previous post was at 02:46 ----------

Sure, but you can bypass that issue by booting into recovery right after flashing.

Sure, it can be done that way

Excellent advice, I second that. Best thing is you only need a working preloader if your device was otherwise bricked and you could flash the complete OEM ROM through SP Flash and be back to pure factory OEM. And, if like me, your factory ROM was an update from the original ROM, you could, if you want to be really fussy, flash the update from the stock recovery after having pushed it to the internal SD Card. After deleting the zip, no one will know it don't as it was went it was sent out to you ;)
[Android General] lion567:
[MENTION=5919159]Tzul[/MENTION], some comments about uboot(bootloader) and A10-70L (I'm own one :o ):

1. If somebody tries to run KK with "new" uboot (lk.bin form A10-70L_S114_150908_ROW), mobile networking (2G/3G/4G/LTE) wouldn't work - Android don't see SIM card though it's installed. I don't think somebody could prefer open bootloader with "new" uboot over mobile network functionality, thus anybody running KK on A10-70L should have "old" uboot.

2. Somebody can run 5.0.1 (A10-70L_S000115_160119_ROW) with "old" uboot - S000115 is distributed as OTA update over KK (S018, S019) and it don't include "new" lk.bin

META-INF\
boot.img
file_contexts
mobicore.bin
scatter.txt
system.new.dat
system.patch.dat
system.transfer.list
type.txt

5.0.1 stock ROM (S000115) runs without issues with both versions of uboot ("old" lk.bin from KK - A10-70L_S114_150908_ROW and "new" lk.bin from LP - A10-70L_S114_150908_ROW).

3. I'm running KK (A10-70L_S000019_150625_ROW) with "old" uboot, which don't allow flash recovery via fastboot, but I have "Hardware : MT8732" in my /proc/cpuinfo

shell@A10-70L:/ $ cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
processor : 0
BogoMIPS : 15.60
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 2

Hardware : MT8732
Revision : 0000
Serial : 0000000000000000

You can find "new" lk.bin for A10-70L (from stock A10-70L_S114_150908_ROW for FT ) here. I've renamed it to lk_S114.img be able flash it via TWRP. I've succesfully tested it with A10-70L_S000115_160119_ROW and it alows flash any partiotions via fatsboot.
[Android General] Tzul:
Hello, [MENTION=7184758]charlestek[/MENTION]!

You can make backups with the SPFT, that's what "Readback" is for! Also, MtkDroidTool won't work with this device. Please read my post on the previous page for some more info.

If you leave TWRP (Reboot menu), it'll check if your tablet is rooted. If not, it ask whether you want to install SuperSU. So, it doesn't root automatically, it just prompts automatically. Rooting or not is still your choice. I also added an explicit "Install SuperSU" button to the "Advanced" menu, which normally isn't there in other versions of TWRP.

The Lenovo Update app doesn't actually install anything, it just downloads the update file and then reboots into recovery mode where the installation will be performed. Whether or not that'll work with TWRP instead of the stock recovery, I don't know. Incremental/differential updates are more finicky, they might fail, especially if you're rooted. "Full" updates basically just overwrite the /system partition completely, and update a few other things (boot, tee1, tee2). I think people have successfully flashed them with TWRP, but I'm not sure.

Note that neither type of official OTA update actually updates the recovery directly. That's done indirectly on the next Android boot, by a certain script. However, both TWRP and SuperSU disable that script in separate ways, meaning that the stock recovery will not automatically replace TWRP. Maybe I'll write the details in a seperate post.

The only thing to look out for is to immediately boot TWRP after first installing it, because if you boot Android first, then TWRP will be overwritten by the stock recovery.

The "SP drivers" do contain the VCOM Preloader drivers. Different names for basically the same thing. I usually call them the USB VCOM drivers.

Anyway, yeah, installing them can be a bit troublesome. I've had mine installed for years now, which is why I tend to not give them any thought. They're just there and work. ;)

If you run a 64 bit version of Windows, you have to disable the driver signature enforcement to install them, as they are unsigned. But I think I already told you that.

TWRP has to be customized for each and every device. You normally can't just take a TWRP image built for one device and use it on another without any modifications.

And if it's not clear by now, to get rid of TWRP, just flash the stock recovery, using one of the several ways to do that (SPFT, Fastboot, TWRP, an Android app such as Rashr [requires root]).
[Android General] bman2010:
Is there away to enable the A10-70F's fast charge option, using software? I have a number of 2.1 Amps wall chargers and USB cables but they are not fast charge enabled. I would like to use them so that I can have spare charging stations. Charging with the standard USB current takes at least twice as long as the Lenovos standard charger.
[Android General] lion567:
AFAIK there is no software fast charge option. Charge currend (and though charging time) depends on USB power sources for charging detection by device (tablet) charging controller, which isn't programable. If charging controller unable to detect USB power source type, it limit charge current to 0.5A.

For maximum charging carrent wall outlet chargers and auto chargers USB should be detected as DCP USB port, so if you find an USB cable with shorted data pins (a short between D+ to D-) on microUSB side, it should make the trick - tablet charging controller detect your charger as DCP and alows charging current up to 1.8A.

You can find more detailed info here The Basics of USB Battery Charging: A Survival Guide
[Android General] Tzul:
There is no special "fast charge". For Android, it usually goes like this:

If you connect the device to a USB data port, it will limit the drawn current to 500 mA, because that's the maximum in the USB 2 standard. Even though many USB 2 ports these days can and will provide more than that (e.g. 1000 mA).

If you connect the device to a dedicated charging port (DCP, i.e. a "charger"), it'll draw as much as it wants. For our tablet, that would be around 2000 mA (2 A).

What's the difference between a data port and DCP? Well, a USB 2 connection has 4 wires (plus a 5th for OTG, but that's not important here). Two are for power (ground and voltage), the other two for data (D+ and D-). The D+ and D- wires are obviously needed for data transfer, but not for charging, so a DCP will just short-circuit them. That's how devices can detect if they're connected to a DCP. Most chargers for Android devices nowadays should have D+ and D- shorted. But there are still some out there that don't, and therefore the device won't draw more than 500 mA from them. Apple chargers are like that (of course), they use their own proprietary way of signalling the charger's maximum current via voltages on D+ and D-, meaning they aren't shorted, meaning they won't be recognized as DCPs.

Cables can also play a role. Both length and quality. I tried the original Lenovo power supply for this tablet with several USB cables, and the results varied. The original cable could do 2000 mA. Some short and crappy noname cable I had caused a limit to 1000 mA for some reason.

Furthermore, I just noticed yesterday that this tablet also appears to limit the current to 500 mA while it is being used. :(

That means if you want fast charging, don't use the tablet while it's charging. Keep it in standby, screen off (powered down should also work).
[Android General] lion567:
It became weired if you ran in some undocumented error. And sometimes (unpredicated) you can lose your NVRAM after "succesfull" ROM flash via SP FlashTool.

Oh, yes, I've fogot about this.

It seem that both (MT6752 and MT8752 ) are there :D :

root@A10-70L:/ # grep 6752 /system/data/misc/ProjectConfig.mk
CUSTOM_HAL_ANT = mt6752_ant_m1
CUSTOM_HAL_COMBO = mt6752
MTK_BT_CHIP = MTK_CONSYS_MT6752
MTK_COMBO_CHIP = CONSYS_6752
MTK_GPS_CHIP = MTK_GPS_MT6752
MTK_PLATFORM = MT6752
MTK_RELEASE_PACKAGE = rel_customer_basic rel_customer_platform_mt6752 rel_customer_tablet
MTK_WLAN_CHIP = CONSYS_MT6752
root@A10-70L:/ # grep 8752 /system/data/misc/ProjectConfig.mk
#Project = HUAQIN8752_TB_B2D_KK
MTK_TABLET_HARDWARE = mt8752
root@A10-70L:/ # getprop | grep 752
...
[ro.hardware]: [mt8752]
[ro.mediatek.platform]: [MT6752]

Thanks, I'll try it.
[Android General] Papanik:
Guys anyone tried to port TWRP 3 yet?
[Android General] charlestek:
Tzul,

Thank you for the very detailed and informative reply. One other question would be, if I restore the stock recovery, how can I before or after unroot, remove root, or is that even possible? My concept of rooting seems to remind me of unix/linux chmod. Otherwise per your comments on incremental or base updates, it would seem to me that installing TWRP is best done after the final KitKat incremental if one wants to stay in KitKat, or the final Lollipop incremental if one wants to stay in Lollipop, though we're not sure if Lenovo is going to issue another Lollipop base or incremental. As far as "ReadBack", I have to look at that in the SPFT gui. Unfortunately in English "ReadBack" means you want something to be told again to you, it does not directly translate to "BackUp".
[Android General] lion567:
Try this one

recovery-TWRP_300-0_A10-70L_lion567_armeabi.img. I've just comiled it from latest TWRP sources several minutes ago and don't test it troughly. Its armeabi (32-bit). It should run with KK installed on tablet (old bootloader). It also can run with LP (new bootloader).
[Android General] bigrammy:
Which SD card are you talking about the Internal or external SD card or are both of them not available via MTP-usb :confused:
[Android General] jedinat:
I can access the device fine when it's on. I'm trying to run SP Flash Tool which has you plug it in when powered off.
[Android General] bigrammy:
OK thank you that's clearer so it must be the preloader driver.

If you installed the signed drivers in this thread then you should "choose" driver/ usb-serial (Cant remember the exact device's offered) / Mediatek / mtk-preloader should be offered in the list of "Mediatek" drivers.

I cant remember the exact names as I am on Linux just now.

As on my windows 10 pc I have to use the same usb port I installed the driver on. If I use another port I have to do the same again :eek:
[Android General] Olly89:
Right could do with some help. I followed all the instructions, root and MM installed perfectly, but left me with no root. This was a while ago and I'd like to change ROM, but obviously can't without root and the instructions given only give scatter files for android 4 and 5. Kingroot's failed numerous times, any suggestions?

Thanks in advance.

EDIT: Boot to recovery gives me a few options including: 'Reboot to Bootloader, Apply update from ADB, Root integrity check, Factory Reset'

EDIT: Nevermind. All info on page 154
[Android General] Sparkrite:
Ah, the power of the "Search" button, too many people underestimate its power, or maybe are just too lazy.

At least you helped yourself instead of looking to be spoon-fed, so fair play. ;)
[Android General] Olly89:
Yeah only used the site a couple of times didn't know there was a thread search tool. Ah well just waiting for a 7.1 rom now, set up on my LG G3 with substratum and its the bees knees.
[Android General] Juhful:
Is it worth it to put Marshmallow on this device? How does it run?
[Android General] Olly89:
Well its definitely worth rooting this device and, when rooted, you might as well upgrade to MM. Honestly there's a lot of ****e programs on this device, just removing them is worth the root.
[Android General] mr-br:
Hi

I'm trying to flash MM & TWRP from stock and, TBH despite having searched this thread until my head spins and having flashed many other devices, I've found myself suffering a reboot loop that I've no idea how to fix.

I downloaded the 6.0 TWRP.7z file from https://xdaforums.com/showpost.php?p=69580395&postcount=1537 and used spflash to load TWRP 3.0.0.. But after then my troubles started.

I wanted do to a backup but there were many unfamiliar partitions. So I decided to take the plunge anyway and flash boot.img. Then did the format as per the instructions in the above post but the system just comes up with boot logo, pauses and then restarts again. I've tried reflashing boot.img (to boot partition) and then various wipes, flashing supersu but the reboot loop remains.

Any ideas how to recover?
[Android General] chris5s:
[MENTION=4577235]mr-br[/MENTION] i used SPFT to flash the MM ROM, TWRP, and modified boot img all in one go, which worked for me.

Just replace the stock img's with the appropriate ones, rename them to recovery/boot.img in the folder and remove the checksum.ini file.

And boot to recovery after flashing and flash SuperSU to get root.

This all worked for me and saves multiple flashes. Might be worth starting from scratch and of course checking you have all the relevant files...

Peace
[Android General] mr-br:
Thanks - I just used spflashtool to install TWRP, with which I'm familiar.

I'm not used to renaming files though let alone modifying boot.img so this has me rather lost I'm afraid. It all seems very different to other devices. Ijn any case I cna;'t rename any files as all the stock files have disappeared as the TWRP For 6.0 instructions said to format (/data) after flashing boot.img.

However even TWRP on this is different as it asks me which partition to flash the boot.img file - so I assumed that was the boot partition?

I also looked at flashing a previous rom that I found on the TWRP download page (in the OP) but that is a whole bunch of img and bin files that I'm not used to seeing - my prev experience with TWRP is that it just flashes a single img or zip file for the OS.

I'm starting to regret this journey ...
[Android General] chris5s:
SPFT flashes several files from the specified folder when flashing a complete ROM. Which includes system, data, recovery and boot images. This is the folder i meant (the one on your desktop/laptop)when talking about renaming and flashing TWRP, modified boot and ROM in one go. How did you flash the MM ROM?

Edit: this is the contents of my folder when flashing ROM using SPFT:

boot.img

cache.img

lk.bin

logo.bin

MT6752_Android_scatter.txt

preloader_hq8752_tb_b2b_m.bin

recovery.img

secro.img

system.img

trustzone.bin

userdata.img

- where boot and recovery images have been replaced by the modified/custom ones :good:
[Android General] mr-br:
I never got as far as flashing (or even downloading) a MM rom - I was just trying to get TWRP on first as that's how my other devices have all worked, but somehow the original OS got wiped.

I've only found a 5.0.1 rom so far (A10-70F_S000121_151222_ROW) which has all the different img and bin files as in your list.

But despite searching and searching I can't find a link to download MM, so I'm rather stumped. Perhaps it was naive of me to think that once TWRP was on then everything would be relatively simple.
[Android General] chris5s:
Link for MM ROM :good:

If you flashed TWRP and modified boot img that were meant for Marshmallow over your original Lollipop ROM then its no huge surprise that you had a boot loop :rolleyes:

Download MM, unzip, replace the appropriate recovery and boot images and flash with SPFT.

Good luck - btw searching this thread for the MM ROM link took me about, em, 5 seconds :eek:

Peace.
[Android General] CaliTexan5:
I've been experiencing this myself in the MM ROM
[Android General] bigrammy:
Use this app to save you rebooting it's free and works just a shame about the adds :mad: https://play.google.com/store/apps/details?id=com.bjemtj.headsettoggle&hl=en
[Android General] IAHOO:
Error flashing zip exretnal...

Hi every body

I'm trying to install MM on my Tab. I done all preliminary requirements but when i want to install custom ROM by TWRP 2.8.7.0. it is failed: Error flashing zip ...

I tried another SD card but no answer again. plz help me to fix it.

device: 70L

previous android: 5
[Android General] chris5s:
Try and install TWRP 3.0.0-0 which is the latest one for 6.

Which custom ROM are you trying to install?
[Android General] IAHOO:
I can't find twrp 3 on official web site and google.

This file:

mediafire.com/file/a4hlhrvz70qcxhq/A10-70_6.0.7z
[Android General] chris5s:
TWRP 3.0.0 here

Not sure about that file, but it's likely a zip package of ROM that needs to be flashed thru SPFlash Tool. :good:

---------- Post added at 11:30 PM ---------- Previous post was at 10:54 PM ----------

SEARCH THE THREAD....

[IMG="Search the thread!!!"]https://pmcdeadline2.files.wordpress.com/2016/02/deadpool-21.jpg[/IMG]

:p
[Android General] d0e01:
Thank you for guides. I've got twrp and root . Any custom roms that we can just flash a zip via TWRP?
[Android General] IAHOO:
tnx.

Now i recive this error: Could not find "Meta-INf/com/google/android/update binary" in the zip File

Is there any other custom android 6 or 7 ROM for this device?
[Android General] chris5s:
What are you doing when you get that error? Remember the full ROM is flashed with SPFlash Tool, not twrp. Check by unzipping the download, and if it has a bunch of files that look like those in my post on the previous page, it needs SPFT.

There are some customs ROMs around, check out 4pda and lenovo-forums-ru but i think the stock MM ROM is good, tweaked a bit :good:

---------- Post added at 11:55 AM ---------- Previous post was at 11:54 AM ----------

PS sorry about the twrp link, version 3.0.0-0 is out there!
[Android General] janek125:
Hi
[MENTION=1795513]chris5s[/MENTION]

Where I can find marshmallow stock or custom rom for this tablet?
[Android General] chris5s:
On the previous page....:rolleyes:

Here....
[Android General] mr-br:
Thanks - I found the link eventually for MM, and then used SPFlash, unticking Boot and Recovery as I'd already done those, and it all worked fine! :)

Now the only issue is the battery drains very quickly, so more searching ...

I'm sure it's frustrating for the old hands, but it seems that quite a few others are having issues searching this thread for MM info, and I don't think we're all numpties, so why don't we create a new MM one to save everyone having the same problems?
[Android General] bigrammy:
Do both HERE and HERE and that should fix the battery drain. :good:
[Android General] coolbeans2016:
a question for ya!

Question for ya Mr. BigRammy! Don't think its 2 off-topic since it do relate to the missgivings of getting this TAB 2 jusz' rite! I have Pixel's launcher (flashable) and other items out of a larger flashable zip (complete wouldn't have worked) and the bootscreen looks just like (in file comparison, not "looks") this devices in the fact it has a folder with a bunch of pics, a folder with a single pic and a <desc> text file. But............. when I take the Pixels folders, descriptive text file and replace Lenovos stock ones, still boots Lenovos?!!!

Care to help enlighten my ignorance O' Smart One?

zach :cool::good:
[Android General] janek125:
[MENTION=1795513]chris5s[/MENTION] tell me is this firmware is safe to my tablet? I don't wan't broke my hardware. How to install it? The same like at first post by FlashTool? Is this official firmware from Lenovo? Everythink working on this firmware or someting isn't work? How it's work LTE connection and 5 GHz? Please answer me. Tomorrow I would like install it. Is this firmware include polish language?
[Android General] chris5s:
Yes it works good, and you can use FlashTool to install.

It is, as I understand, an official Lenovo firmware for the L version of this tablet. Just make sure that you have the same tablet as mentioned in this thread, not a different one! There seems to be different tablets with very similar names floating about.

5GHz works fine, not sure about LTE as I have the WiFi only version (F).

I'm sure it supports Polish language, but can't say for absolute certain.

:good:
[Android General] janek125:
[MENTION=1795513]chris5s[/MENTION] thanks for your answer. I have Tab2 a10-70L with LTE connection. This Android is for me :D:D:D
[Android General] bigrammy:
Hi,

Not really sure I understand the question fully :confused:

Are you talking about modding the pixel launcher .apk :confused:

Are we talking default wallpapers here. :confused:

Or are you referring to my other device (Infocus v5) and the way I setup my custom stock rom on that :confused:

Sorry for not understanding. :o
[Android General] chris5s:
[MENTION=1237913]coolg[/MENTION]eans2016 are you talking about replacing the boot screen? If so, I've only managed to do it using a modified mp4 file.

Changing bootanimation.zip doesn't seem to have any effect...

Peace.
[Android General] Ax-Soft:
Hi guys, can you please share sources of TWRP config for building TWRP from source code for A10-70L? I'm trying to build, it's building but not booting :(
[Android General] Sparkrite:
Just as an aside, why are you trying to build one when we already have a working TWRP ??
[Android General] Ax-Soft:
I have a task at my work to modify it for in-house usage.
[Android General] Sparkrite:
Cheers !

That clears that up so, good luck with it. :svetius:
[Android General] bigrammy:
This should help HERE :good:
[Android General] coolbeans2016:
sorry got side swiped

Sorry for the delay in responding BigWhammy... No, I'm talking about the stock boot screen. I have Pixels Launcher that can be flashed through TWRP, and the bootscreen for the pixel which would be great on this tablet, take the Lenovo off of it,:cool:

I have gone under system media where the stock Boot.zip is and trying replacing with the Pixel and it still just boots Lenovos stock one?!!!! Is there a set of steps or another location for changing the boot screen? Pixels is just like Lenovos as in two folders with one containing a large number of stills to make animation + another folder with a standard Google pic along with a <desc> text file to tell it how to go about showing itself.

zach

---------- Post added at 07:01 PM ---------- Previous post was at 06:55 PM ----------

I have been trying to find an online site that sells the Lenovo TAB 2 A10-70L, since the wi-fi only version is all that was sold in America I believe (A10-70F).

Any reliable links for purchasing this tablet would be greatly appreciated!

Thanks,

zach