[Q] Lenovo Tab 2 A10-70F --Root??

Search This thread

loner.

Senior Member
Feb 25, 2013
1,457
289
Does this matter to us?

TWRP 3.0.2-0 Released

Apr 5, 2016

TWRP 3.0.2-0 is out now for all currently supported devices.

What’s new in 3.0.2-0:

Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.Add Greek translation to some builds.

We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to*our github*and we have*a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
 

Productiongeek

New member
Apr 30, 2016
2
0
Would you please post the instructions to root the Lenovo Tab2 a10-70f with Lollipop? I am using the latest OTA update from Lenovo.

Please?

Thank you!
 

Tzul

Senior Member
Jun 25, 2014
421
430
Does this matter to us?

TWRP 3.0.2-0 Released

The TWRP 3.0.0 that lion567 compiled has no support for encrypted Android, and therefore doesn't suffer from related bugs.
Of course it would be nice to have a version of TWRP 3 that does support encrypted Android, and if someone is going to build it, he/she should use the latest version of TWRP 3 anyway.

Yes. I am reading through the entire post this weekend. Much of it is over my head and I'm trying to overcome my confusion...
I think I understand it is possible to root lollipop with Kingoroot, then replace King with Supersume, and install TWRP...

Is this correct?
No. Just install a custom recovery, i.e. TWRP. You can try to do that via Fastboot (if your tablet has the new bootloader), or always with the SPFT.
After installing TWRP, immediately boot it (so that it doesn't get replaced by the stock recovery), and then install SuperSU from within TWRP (just leave TWRP via the Reboot menu, it should automatically offer to install SuperSU; or check if there's an "Instal SuperSU" button in the Advanced menu).
 
  • Like
Reactions: loner.

MarkyboyUK

Member
Nov 4, 2013
36
9
I hear of people rooting this device in order to remove the "bloatware" - what is it exactly that you guys are removing from this tablet please and does it make a significant difference to performance?

Thanks
 
Last edited:

Tzul

Senior Member
Jun 25, 2014
421
430
@MarkyboyUK "Bloatware" is everything that is pre-installed but deemed useless or unnecessary. Different people will therefore consider different apps bloatware.
This tablet includes a bunch of foreign language apps, e.g. Japanese ones, but they aren't active if you're using the tablet in other regions of the world. Removing those foreign language apps therefore makes no difference to performance. Deleting them will free some storage space, but since it is on the system partition, which is normally read-only, most people won't be able to make use of that freed space either.

There are also some other apps, like LenovoID. They might be running in the background constantly, and therefore consume some memory (RAM) and a tiny bit of performance. People like to disable or delete those apps mainly to free up more RAM and to prevent those apps from "spying" / phoning home.
 
Last edited:

iru786

Senior Member
Sep 9, 2011
135
8
Birmingham
Hi Guys,

Is there any easier method to root this device ? I used Kingo Root and it does not work. i am on latest updated for the software on this.

Thanks
 

Old faithful

Senior Member
Dec 31, 2008
585
202
Wentworth-Nord
@MarkyboyUK "Bloatware" is everything that is pre-installed but deemed useless or unnecessary. Different people will therefore consider different apps bloatware.

I would posit that bloatware is more specifically poorly written, inefficient apps supplied by large commercial entities, basically designed to generate income while adding little value if any to users under its heavy gloss and interface glitz.

Pretty much most of the stuff coming out from Google and constantly updating your device whether you like it or not.



ReSent from my SGH-I317M using Tapatalk 2
 

Old faithful

Senior Member
Dec 31, 2008
585
202
Wentworth-Nord
Thanks... I should clarify my question a bit more. I have used the method to root it and has flashed TWRP and SU but i am not able to update SU binary and because of this, Not able to grant root access to any apps

The best way to update the binary would be to download the latest stable SU release as a zip to the root of your sd card and install it from TWRP.

Also wiping the Android cache and the Dalvik is a good practice to prevent possible conflicts.

HTH...

Sent from my SGH-I317M using Tapatalk 2
 

iru786

Senior Member
Sep 9, 2011
135
8
Birmingham
The best way to update the binary would be to download the latest stable SU release as a zip to the root of your sd card and install it from TWRP.

Also wiping the Android cache and the Dalvik is a good practice to prevent possible conflicts.

HTH...

Sent from my SGH-I317M using Tapatalk 2
Did all of the above... Still the same issue for some reason.

I have rooted quite a few devices before but never has this issue. So scratching my head with this one.
 

Old faithful

Senior Member
Dec 31, 2008
585
202
Wentworth-Nord
Did all of the above... Still the same issue for some reason.

I have rooted quite a few devices before but never has this issue. So scratching my head with this one.

I would then suggest you simply start by reloading the OEM ROM through SPFT, because as you probably know resetting the device to factory settings doesn't really restore anything especially anything modified in the system partition. Flashing with SPFT OTOH insures everything is fresh and is really a no brainer once you got the proper preloader driver and SPFT version.

Sent from my SGH-I317M using Tapatalk 2
 
  • Like
Reactions: iru786

iru786

Senior Member
Sep 9, 2011
135
8
Birmingham
I would then suggest you simply start by reloading the OEM ROM through SPFT, because as you probably know resetting the device to factory settings doesn't really restore anything especially anything modified in the system partition. Flashing with SPFT OTOH insures everything is fresh and is really a no brainer once you got the proper preloader driver and SPFT version.

Sent from my SGH-I317M using Tapatalk 2
Sorted. Reflashed the stock ROM and did the rooting... Thanks
 
  • Like
Reactions: Old faithful
Yes, it is for A10-70L version but it works for A10-70F! There is just only data and call features which are useless for A10-70F. I have installed it and i have no issue for the moment

Which is the file to download? I've had Google Translate translate the page and find nothing about either A10-70F or 70L. Have even looked forward a few pages on that site and it honestly looks like the same page duplicated over and over.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    Lenovo A10 70f finally rooted and cwm lollipop 5.0.1

    Hi my first post but I'm sure u will all enjoy, finally got this tablet rooted on lollipop 5.0.1, using following method.
    1. Download and install SPflashtools.
    2. Download and install MT6575 USB vcom drivers,
    3. Download a zip called carlivtouchrecovery.zip
    4. Download UPDATE-SuperSU-v2.46.zip.
    Right now to start.
    First off set device into USB debug, from about device, press build 10 times to access features.
    Now with device turned ON connect to PC using cable make sure all drivers installed OK.
    No disconnect again, and load up SPflashtools, choose scatter file from within carlivtouchrecovery. And make sure only recovery option has a tick. Now click download.
    Now connect device again whilst switched OFF, and now custom recovery is installed.
    Disconnect device, turn on device holding power and vol+ check recovery installed.
    Now to ROOT, insert the UPDATE-SuperSU-v2.46.zip onto sdcard1, load into recovery mode using power and vol+ again, choose recovery, then from here choose update from sdcard1, choose the UPDATE-SuperSU.zip and install. Restart and 100% rooted and with custom recovery, unfortunately I cannot add links but easy to Google search to find, please like if helps, thanx :D
    5
    Recoveries...

    Just a quick question - I'm coming from the well worn and comfortable neighbourhood of CWM and as i tried to do my first backup using this recovery, I notice there isn't any option to do backup on the external SDCard and was wondering if it was just me, or is it truly missing from this recovery? 16GB fills very quickly when experimenting!

    I have noticed that, you can back up to sd card on the recovery for lollipop, not on the kitkat version. My understanding was that recovery is independent of the os. Probably someone can shed some light on this issue?

    I have analyzed the two custom recoveries from that Russian forum. I'll henceforth call them CR4 and CR5. They are virtually identical, and they were made for the Elephone P6000! Except for the kernels, of course.

    A quick primer on the format of Android boot.img and recovery.img:
    They start with an "ANDROID!" header containing some address and size data, and a few other things that aren't important here.
    After this header, the actual Linux kernel image starts. This kernel image is usually compressed, to save space in flash memory. There are a few of popular formats, more about them in a second.
    After the kernel, there's a "rootfs" or "ramdisk". It's a compressed file system that literally provides the root file system, and contains the initial files required for booting Android, or the recovery. Mainly some init scripts and binaries.
    The ramdisk part usually concludes the boot/recovery image. There's an option to have a second loader afterwards, but I've never seen one personally.
    In Mediatek boot/recovery images, there's also a special 512 byte sector attached to the front of the kernel and ramdisk parts, but that's not important here either.

    Back to the compressed kernel formats. One is "zImage" - this is a gzipped kernel that self-extracts, i.e. it starts with a bit of decompression code and has the final gzipped kernel embedded. Our Lenovo tablet uses this format for Android 4.4, and therefore the CR4 uses it, too.
    For Android 5 however, the kernel is just plain gzipped, without self-extraction code. And of course CR5 mimics that. So how does the kernel get extracted in memory then? That's done by the bootloader. The tablet uses (L)ittle (K)ernel - you might have seen the "lk" partition in the scatter file. When powering on, the boot sequence is basically preloader (the thingy that's also responsible for initiating the VCOM connection with the SPFT) -> bootloader (has fastboot integrated and is responsible for the little "recovery, fastboot, normal" menu) -> kernel (boot.img / recovery.img).

    It's highly likely that the LK version from the Android 4.4 firmwares expects zImage kernels and can't handle plain gzipped kernels.
    That's why CR5 does not work when the tablet is still running Android 4.4 (or more precisely, the older LK). And like I said, it'd be pointless anyway, because the two recoveries are identical (that is, their ramdisks are identical, with one silly minor difference: the banner graphic of CR4 reads "Ported by hanuma50" whereas in CR5 it reads "Ported by >>psihop<<").

    So, the fact that the external SD card does get mounted in CR5 but not CR4 is not due to differences in the actual recoveries (ramdisks). It's due to the different kernels and/or bootloaders (LK).
    It might be possible to create a working zImage-based recovery from the Android 5 kernel and use that on the tablets with older firmware. Maybe it's also possible to use the new LK with the older firmware, if the new LK still supports zImage...
    version "4" of LK + CR4 = SD card not mounted
    version "4" of LK + CR5 = fails to boot, as explained above
    version "4" of LK + zImage version of Android 5 kernel = ???
    version "5" of LK + CR4 = ???
    version "5" of LK + CR5 = SD card mounted

    Would make an interesting experiment, but I don't feel like doing it. Also, it's probably easier to have the SD card mounted in CR4 by just doing a few modifications to certain files inside the ramdisk (fstab).
    I did originally consider porting a more properly adapted custom recovery to the tablet myself. But since I don't really need one (except for the initial installation of SuperSU), I probably won't try any time soon. I do all my partition backups with the SPFT. ;)
    5
    Well, I figured I would copy the backup from the internal sd card to my pc and then to a microsd along with all the other backups I intend to make.
    That way they are double backed up.
    Unless there's a reason that I wouldn't be able to see the files over mtp then I think that should work.


    Well, Sparkrite was giving me the impression that re-flashing the entire stock rom was riskier that restoring a backup made with the custom recovery.
    Maybe I misunderstood something but if that was what he meant then I would think that having a pre-rooted backup at least would make the process of getting the device safely back to stock condition easier.
    I may make a tweaked backup at the point that I know what I want on the tablet to begin with but right now I'm still figuring out what apps I need.
    My last tablet was from a few years ago so it hasn't been able to handle some of the newer things I have access to on the lenovo.
    Titanium backup sounds like a good idea, I may do that in addition.


    Well, I checked my stock os version number against the one from the rom Ondigo provided and they were the same before I installed that 4.4.4 update.
    Is there a reason that after returning to the stock state I couldn't just use the lenovo system updater to install the update again?
    Why do I need to load a a zipped update file as opposed to just using the normal update method.
    Also where would I get said file as I haven't seen any links posted to it so far in the thread.


    That's ok, I do too sometimes. :)


    That's probably what I'll do then, sounds simpler.


    Ok, I thought it would be, it's worked with every other driver install I've done.
    Sometimes there's a reason though, like having 2 drivers for the same device in separate child folders inside a parent folder.
    Hard telling which one windows will pick in that situation and it might not be the right one for the intended purpose.


    What would it overwrite the custom recovery with, isn't this one of the options from within the custom recovery?
    Does that option restore the stock recovery or overwrite the custom recovery with something else entirely?
    Why specifically would it be bad to use that option? :confused:


    pfff... ha! :rolleyes:


    Well, the idea would be to restore the device to it's pre-root state, basically exactly the way it is right now with that pre-root custom recovery backup I mentioned before.
    Then after that I would re-flash the stock recovery.
    So unless root and any changes made by root apps would persist through the pre-root backup restoration I'm unclear on why it would be any riskier than re-flashing the entire stock rom.
    Do you still think it's too risky after that clarification and if so could you be more specific about what flags it might throw up and?
    I'm not eager to see if the factory rom will actually work, I'm glad to have it in a worst case scenario but I would rather restore the tablet to stock on the current version of the os than re-install it entirely if I can avoid that.

    Also, Have you been through that process before of returning a tablet to stock and submitting it for warranty service?
    I would be curious about your experience with it since I never had to do that with my previous tablet.

    Great conversation guys...
    couple of things, Carliv Recovery will backup to sdcard0 (internal) or sdcard1 (ext-sdcard)
    backing up everything before flashing SuperSu root is the best way to have a full back to stock system.

    the carliv backups on the Internal sdcard did not show up on my PC but they are their when you boot back to recovery
    The backups to sdcard1 show up on the PC so they can be backed up without any problem

    Well, I checked my stock os version number against the one from the rom Ondigo provided and they were the same before I installed that 4.4.4 update.
    Is there a reason that after returning to the stock state I couldn't just use the lenovo system updater to install the update again?
    Why do I need to load a a zipped update file as opposed to just using the normal update method.
    Also where would I get said file as I haven't seen any links posted to it so far in the thread.

    all the OTA updates are in my AFH account here >> https://www.androidfilehost.com/?w=files&flid=46340

    also their is a hack to use exfat on your 64gig sdcard while in the tablet OS
    the file is in my AFH collection I posted above - update-android-fs-1-0-4-install-sud-zip.
    Instructions to use it are here >>https://translate.googleusercontent...42143/&usg=ALkJrhjp1hOQYA3ML76vkdrXgeqQrqiKkA
    5
    Hi my first post but I'm sure u will all enjoy, finally got this tablet rooted on lollipop 5.0.1, using following method.
    1. Download and install SPflashtools.
    2. Download and install MT6575 USB vcom drivers,
    3. Download a zip called carlivtouchrecovery.zip
    4. Download UPDATE-SuperSU-v2.46.zip.
    Right now to start.
    First off set device into USB debug, from about device, press build 10 times to access features.
    Now with device turned ON connect to PC using cable make sure all drivers installed OK.
    No disconnect again, and load up SPflashtools, choose scatter file from within carlivtouchrecovery. And make sure only recovery option has a tick. Now click download.
    Now connect device again whilst switched OFF, and now custom recovery is installed.
    Disconnect device, turn on device holding power and vol+ check recovery installed.
    Now to ROOT, insert the UPDATE-SuperSU-v2.46.zip onto sdcard1, load into recovery mode using power and vol+ again, choose recovery, then from here choose update from sdcard1, choose the UPDATE-SuperSU.zip and install. Restart and 100% rooted and with custom recovery, unfortunately I cannot add links but easy to Google search to find, please like if helps, thanx :D

    Well done!
    The exact method I said (linked to) in post 121 of this thread.
    However you took the time to elaborate on the steps needed.
    5
    TWRP is here!

    I managed to make a working TWRP custom recovery for this tablet!
    Like I said before, the screen boots up in portrait mode, but the touch panel driver returns coordinates in landscape mode, making everything unusable. If you compile TWRP from scratch, you can specify the flags RECOVERY_TOUCHSCREEN_SWAP_XY and RECOVERY_TOUCHSCREEN_FLIP_X to fix this.

    Here's the download, containing the two versions for Android 4 and 5. And here are some screenshots.

    If you'd like to show your appreciation and encourage me to continue working on this, I have a donation link on the left.

    Anyone know how repair NVRAM? Wifi error, imei zero without root... MTK Engineering Mode not solution. Thnx.
    Well, if your personalized data (MAC addresses, IMEI, ...) is gone, then it's gone. There's no permanent fix for a deleted NVRAM yet, but if you place the proper files in the /data/nvram/ folder, you can get rid of the errors. I guess you have a A10-70L, because you mentioned IMEI? I only have the files from my A10-70F, without IMEI. You can download them here. But you'll need root and you'll need to edit the files (enter a valid MAC address for Bluetooth in the file BT_Addr at offset 0, and a MAC address for WLAN in the file WIFI at offset 4; you might also want to change the country code from "DE" [Germany] to "US" or whatever... here's a datasheet describing the format of the WIFI file).