• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

Tzul

Senior Member
Jun 25, 2014
421
430
Then I realized he needed both preloader.bin and LK.bin and the preload partition is not accessible from TWRP (or fastboot it seems). So at some point he still needs SPFT to get the full firmware update.
Preloader can't be flashed by fastboot. Even if I could make it work in TWRP, it's not worth the risk.

Is that correct?
dd if=/sdcard/boot.img of= /dev/block/platform/mtk-msdc.0/by-name/lk bs=512
Also you mentioned about preloader, do I still need to flash it
(dd if=/sdcard/preloader_hq8752_tb_b2b_l.bin of=/dev/block/mmcblk0boot0 bs=512 seek=4)
or can just leave my old one?

No, should be "dd if=/sdcard/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/lk". No need to specify a blocksize there.
lk.bin is the bootloader (Little Kernel), boot.img is the Android boot image (Linux kernel + rootfs).
I just tried to flash the preloader this way, but it didn't work, dd reported "operation not permitted" for /dev/block/mmcblk0boot0, even though the device is flagged as writeable.
Since it looks like you don't have a choice anyway, you can keep your old preloader.

Edit: oh, and fastboot might have a limit on the file sizes it can transfer! That limit could be as low as 128 MB... meaning you can't really use it to flash system and userdata, because they are much larger than that. Not sure about this, let me know what happens if you try.
 
Last edited:

Megaco

Member
Jan 17, 2013
8
2
Yes and it also contains the LK.bin backup
I just had really an awkward experience )

Flashed new lk via dd, that allowed me to flash TWRP. I failed flashing system partition in fastboot mode (as Tzul sugested 128 mb limitation). So far so good. Then I restored TWRP backup (deselected lk, just in case, and data partitions) and everything went wrong. After successful restore I got almost dead tablet, only preloader kept working.
Why did it happen? I was hoping to have working lk at least.
Perhaps corrupted backup? How could TWRP ruin lk partition…
Anyway, I decided to begin from the beginning, installed VM box + Arch Linux + SPFT, and everything flashed flawlessly from the very first attempt.

I really appreciate all your help and suggestions!
 
  • Like
Reactions: suhridkhan and Tzul

clsA

Senior Member
Aug 28, 2010
9,822
3,460
Central Florida
I just had really an awkward experience )

Flashed new lk via dd, that allowed me to flash TWRP. I failed flashing system partition in fastboot mode (as Tzul sugested 128 mb limitation). So far so good. Then I restored TWRP backup (deselected lk, just in case, and data partitions) and everything went wrong. After successful restore I got almost dead tablet, only preloader kept working.
Why did it happen? I was hoping to have working lk at least.
Perhaps corrupted backup? How could TWRP ruin lk partition…
Anyway, I decided to begin from the beginning, installed VM box + Arch Linux + SPFT, and everything flashed flawlessly from the very first attempt.

I really appreciate all your help and suggestions!
I'm glad you got it all sorted out.

Sent from my HTC One M9 using Tapatalk
 
Last edited:

dennmtr

Member
Feb 12, 2016
9
0
lollipop update and carlivtouchrecovery

hello guys i patched my lenovo tab with carlivtouchrecovery mod to root my lollipop android. today i have an update confirmation from lenovo. it downloads and after reboot very fast i see a recovery debug messages and immediately the system boots back to android. the update was failed. what have i to do?
 

clsA

Senior Member
Aug 28, 2010
9,822
3,460
Central Florida
hello guys i patched my lenovo tab with carlivtouchrecovery mod to root my lollipop android. today i have an update confirmation from lenovo. it downloads and after reboot very fast i see a recovery debug messages and immediately the system boots back to android. the update was failed. what have i to do?

Install/flash the matching stock recovery and system.img of your current version
My collection of files is here >> https://www.androidfilehost.com/?w=files&flid=46340
 

clsA

Senior Member
Aug 28, 2010
9,822
3,460
Central Florida
nice link idont know how to do it but ll try. where csn i find the system. img file?

in the firmware in the list... their just zip files

find you current version in settings / about / current version
download the corresponding firmware, extract it and flash just the system.img and recovery.img and now OTA will work

Also we no longer use the Carliv recovery, we have TWRP now use it instead
 
Last edited:

dennmtr

Member
Feb 12, 2016
9
0
hello guys . i moved back to stock recovery from carlivtouchrecovery to apply ota updates. i flashed with stock recovery.img but after system reboots to flash the update i get this error :

update.zip is not correct correct installation aborted
 

dennmtr

Member
Feb 12, 2016
9
0
everything messed up with recovery patch. nothing str8 rootting this device. i patched kitkat firmware from the begging and upgrade to lollipop again. everything messed up. no ime, no signal, nv ram errors, no wifi . i have to root this device again and every time i ll do factory reset or firware upgrades i have to root and modify ime codes and mac addresses with the best complicated way, from the begging. i hate android.

best guide ever, http://thefirmwarehub.com/how-to-fix-invalid-imei-and-nvram-error/

mind the gap between AT and +EGMR
 
Last edited:

Old faithful

Senior Member
Dec 31, 2008
585
202
Wentworth-Nord
everything messed up with recovery patch. nothing str8 rootting this device. i patched kitkat firmware from the begging and upgrade to lollipop again. everything messed up. no ime, no signal, nv ram errors, no wifi . i have to root this device again and every time i ll do factory reset or firware upgrades i have to root and modify ime codes and mac addresses with the best complicated way, from the begging. i hate android.

best guide ever, http://thefirmwarehub.com/how-to-fix-invalid-imei-and-nvram-error/

mind the gap between AT and +EGMR
Doing a factory reset won't do diddley squat if your system partition is already messed up, your only recourse is to flash the original ROM. You DO have a backup, don't you?

If you messed with with the nvram (that can happen if you flash with formatting - NEVER DO THAT) you're in trouble unless you have a backup of it, because you may not be able to get online afterwards, as the nvram stores your device's unique identifiers. Perhaps you could retrieve them from Lenovo using the serial number?

In any case I sure hope you get your problem sorted out.

Sent from my Lenovo TAB 2 A10-70F using Tapatalk
 

dennmtr

Member
Feb 12, 2016
9
0
Doing a factory reset won't do diddley squat if your system partition is already messed up, your only recourse is to flash the original ROM. You DO have a backup, don't you?

If you messed with with the nvram (that can happen if you flash with formatting - NEVER DO THAT) you're in trouble unless you have a backup of it, because you may not be able to get online afterwards, as the nvram stores your device's unique identifiers. Perhaps you could retrieve them from Lenovo using the serial number?

In any case I sure hope you get your problem sorted out.

Sent from my Lenovo TAB 2 A10-70F using Tapatalk

i didnt have a backup because i am totally new to android and i didnt know about ime codes, nvram data etc.

my tablet works fine now, but every time i have to do a factory reset i have to configure all this things from the begining, even with random hardware numbers.

i only have the ime code refers to the back side of the tablet. nothing else. i dont know how to retreive the original product numbers and codes from lenovo with my tablet serial number. totally thank u
 

Old faithful

Senior Member
Dec 31, 2008
585
202
Wentworth-Nord
i didnt have a backup because i am totally new to android and i didnt know about ime codes, nvram data etc.

my tablet works fine now, but every time i have to do a factory reset i have to configure all this things from the begining, even with random hardware numbers.

i only have the ime code refers to the back side of the tablet. nothing else. i dont know how to retreive the original product numbers and codes from lenovo with my tablet serial number. totally thank u
I'm sorry you feel sore for finding out the hard way that formatting in SP Flash erases your device data. Have you tried getting the information from Lenovo customer support based on your device serial number?
Whatever you do when you flash NEVER select "Format" in SP Flash UNLESS you have a BACKUP OF NVRAM! THIS is the cause of your problem, and it has been documented extensively.
That being said, having a random MAC address is not the end of the world, but may cause validation problems with some sites.
If you use TWRP custom recovery, there is an option to back up the NVRAM partition. There are other tools that can do it as well but you'd have to dig around on xda-developers. This way you could simply restore the data should you require it later on.
 

dennmtr

Member
Feb 12, 2016
9
0
I'm sorry you feel sore for finding out the hard way that formatting in SP Flash erases your device data. Have you tried getting the information from Lenovo customer support based on your device serial number?
Whatever you do when you flash NEVER select "Format" in SP Flash UNLESS you have a BACKUP OF NVRAM! THIS is the cause of your problem, and it has been documented extensively.
That being said, having a random MAC address is not the end of the world, but may cause validation problems with some sites.
If you use TWRP custom recovery, there is an option to back up the NVRAM partition. There are other tools that can do it as well but you'd have to dig around on xda-developers. This way you could simply restore the data should you require it later on.

i ll never use recoveries in the future because i have problem with android updates. i formated the tablet because of this. kingroot now have strategy for a10-lollipop. i ll send an email support in lenovo site hope some day, month, year :) i ll have an answer . thank u. i think sp flash has option for backing up tablet/partitions . i havent check this

edit: why is my nvram settings returned back to null if i do factory reset ?
 
Last edited:

defishinsea

Member
Dec 6, 2015
10
0
(Solved) Not able to flash stock firmware

Hi all,
I have a Lenovo TAB2 A10-70F and unfortunately I cannot flash the stock firmware using SP Flash Tools. Here you have the long story in a short version.
My tablet updated to Lollipop 5.0.1. I rooted the tablet using Kingroot, which was successful then I replaced the the Kingroot with SuperSu using the SuperSU Me app from the Google Play. After the installation the tablet required a reboot. And then my tablet wouldn't boot anymore. It stays at the logo screen forever. I've managed to go into recovery, did a data and cache wipe, but nothing happened. Fast boot is not working as well.
After reading a lot of tutorials I proceeded to flash a KitKat Rom. Downloaded the stock rom, SP Flash Tools, USB drivers and followed the steps as described in tutorials.
SP Flash Tools seems to work OK, but the flashing process stops after the red progress bar reaches 100%. After that nothing happens. I use Windows 8.1 and the latest USB drivers.
If you guys have any idea about what is going on please let me know. I love this tablet and I don't wanna see it thrown away in the garbage.
Thanks for your time and sorry if this is a double post or it's been answered somewhere else.

The problem was the version of SP Flash Tools I was using.
 
Last edited:

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).