yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] elcabone:
Even on 4.x?

Most of the users have the wifi issues on 5.x, including me. That's y i'm back, running 4.x.
[Android Q&A, Help & Troubleshooting] markvarvel:
Help

Can you please explain how to install SP driver, as there is no installer
[Android Q&A, Help & Troubleshooting] gmincca:
Upgraded from kk to lp. (ROW 22 to 118), followed by updates to 119 then 120. So far tab runs well apart from occasional touch screen lack of sensitivity, same as with kk.
[Android Q&A, Help & Troubleshooting] Stubensauger:
Sometimes, yeah. Especially when the Tabletscreen is five minutes off or something. But it runs better than 5.0.1.
[Android Q&A, Help & Troubleshooting] Sparkrite:
Ok, turn off the tablet,

Open "device manager" on PC,

Now connect the tablet via usb and keep an eye on the device manager,

Be ready to move quickly, you should see an unrecognised device detected, as far as I can

remember it appears as something like "Mediatek Preloader" or something like that,

Before it disappears click on it and update/load the drivers by pointing it to where you have

the drivers saved on drive.

And Voila !!

It took me a couple of attempts but it only has to be done once.
[Android Q&A, Help & Troubleshooting] markvarvel:
Thank you. Somehow I kept missing that post #165.
[Android Q&A, Help & Troubleshooting] ChaosDM:
Hard/Soft Bricked 2 Lenove Tab 2 A10-70f !!!

EDIT : Problem partially solved...please read this post first and then the next post before replying. Thanks.

OK, this is going to sound stupid...got myself three (3)Tab2 A10-70f (one for each kid)...I managed to root the first one (I upgraded it first to a newer ROM when asked, still 4.4.4 and then rooted it)...I then wanted to do the same with the 2nd one...but unfortunately did it the other way around...Rooted first and then upgraded when asked by the Tablet. After this (obviously) the Tablet was "soft" bricked (I can access the System Recovery). I TRIED EVERYTHING with the SP Tool...I installed all drivers as explained in this thread...but when I plug the USB cable into the tablet I always get the SP Tool to show me a Red Bar at the bottom with "Download DA 100%" in it.

I REALLY TRIED EVERYTHING...meaning that I also tried to reflash the standard ROM onto the first Tablet which was rooted perfectly...by doing that (I always got the Red Bar in SP Tool) I managed to HARD brick that tablet!!!! I can't boot into anything...when I plug it into a charger I don't see it charging...the only thing I can do is connect it to my PC with the USB cable and then I hear a "ping sound" (found new hardware sound)...and the only thing that I get in my Device Manager is "unknown device"!!!!

Aaaaaargh.

So I guess I should concentrate on the soft bricked Tablet first. Isn't there a way to insert an SD card into the slot with the stock ROM on it and then "just" boot into system recovery and "apply update from SD card"? I tried it, but no luck...question is...what has to be in the .zip file? Can the .zip file be named anything? I tried to name it ROM.zip and FIRMWARE.zip...but no luck.

I'm using the files that are inside the file I found in this thread (A10-70F_S000021_150501_ROW_USER_DCC). It has the scatter.txt fil in it as well.

Please help :)

Thanks in advance.

ChaosDM
[Android Q&A, Help & Troubleshooting] ChaosDM:
OK...I succeeded in reviving the "soft bricked" Tab 2. What was the problem? Well the latest build of SP FLASH Tool (SP_Flash_Tool_v5.1524.00.000) DOES NOT WORK WITH THE LENOVO TAB 2!!!! Or....at least not with my Tab 2's.

Just for the heck of it I DL'ed an older version of SP FLASH TOOL (SP_Flash_Tool_v5.1436.00) and just hit "Download", plugged in the Tab 2 with the USB cable...hear the "ping" sound and immediately I got the Red Bar "Download DA 100%" again...I thought, oh well...too bad, same problem...but then suddenly, after a couple of seconds it suddenly started to show a green progress bar instead of the Red bar and the Tab 2 got flashed!!! Yipppeee..

So...great news I thought, now that I found the problem I'll be able to revive the "hard bricked" one...I hit "Download" once more, plugged in the Tab 2 with the USB cable BUT then the PC said "Unknown Device" detected" and that was it.

So...I'm left with a really dead Tab 2...anyone got any ideas to circumvent that "unknown device" problem?

Thanks,

ChaosDM
[Android Q&A, Help & Troubleshooting] EternalGrump:
Hi, I'm new to xda and to rooting in general, I got a Lenovo Tab 2 A10-70F recently and I want to root it.

I've had 1 tablet up until now that a friend helped me root and this time I'm doing it solo and before I make my attempt I want to make sure I understand what I need to do and why.

I've read through this entire thread and I think I largely understand what is required but I have some questions/things I want confirmed.

From what I've read it looks like the general consensus is to not update to lollipop as there are wifi issues and 4.4.4 just woks better all around on this tablet.

The primary method of rooting seems to be to use kingroot and then to replace kingroot with supersu via a script such as the one from W0lfdroid.

If something goes wrong the solution seems to be to re-flash with the stock rom that I've got saved and ready.

Now this is part of where I'm unsure about things.

When my friend helped me root my last tablet, I remember we installed cwm and used it to make a backup and that seems to be something that isn't involved with the default method of rooting the A10-70F.

I saw some posts that seemed to be talking about rooting after updating to lollipop that involved cwm but none that specifically addressed doing that with 4.4.4.

Why is that, is it really not necessary, is it not possible to do safely, etc.?

It seems like it would be sensible to make a backup before rooting if possible or after, or both just to avoid a worst case scenario, so I'm not clear on why that isn't a default step.

Beyond that I don't know that I really understand all that much about cwm itself other than it can be used to make backups, so that may be part of my confusion as well.

I think I read something somewhere in this thread about cwm affecting the factory default restore method, possibly making it not work after being installed so that concerned me a bit as I don't really understand why that would be the case.

By rooting without cwm, does that end up not interfering with the default restore method and is it then possible to do a factory reset after rooting and have the reset remove root status?

Like I said I am new and inexperienced at this and I just want to make sure I don't screw something up.

Ultimately I'm not looking to do anything crazy with my tablet by rooting it, I mainly just want to be able to install an effective ad blocker, one or another of the permission limiting apps to deal with devs that ask for unreasonable permissions, utility stuff, etc., I'm not really confident enough to attempt anything like a custom rom even if that was an option for this tablet.

If anyone can answer my questions and let me know if there's any part of my understanding that isn't accurate, I'd very much appreciate it.
[Android Q&A, Help & Troubleshooting] Sparkrite:
I think you may be confusing rooting with "CWM" (or any other recovery out there).

AFAIK there is NO CWM/TWRP/PHILIZ etc. for this pad, but rather there is Carliv Recovery ( a derivative of cwm), which I have linked to many times in this thread.

See my post..................

http://xdaforums.com/showpost.php?p=63535771&postcount=128

Also remember that rooting just allows you what is termed root access, ie. very deep access to normally protected apps by installing a file called "su.bin" into the system.

Carilv recovery ( as do the others) rewrites the recovery routines and therefore allows you to make complete backups, install custom roms and flash many third party rewrites etc.

NB. OTA updates that require flashing generally will not work as they will expect the stock recovery to be present.
[Android Q&A, Help & Troubleshooting] EternalGrump:
I don't think I was confusing root with cwm I understand that root has to do with unlocking access to deeper system files and I understand that cwm is not related to rooting the tablet, it was just an extra step that my friend felt was prudent to safeguard against possible future problems.

I think one of the main things I didn't really understand was that cwm overwrites the stock recovery.

I mainly mentioned cwm because that was what my friend used on my last tablet but he didn't give a full explanation at the time of how cwm worked, just that we needed it to make a full backup of the tablet.

I did see carlivrecovery mentioned earlier in the thread but the link you posted seems to be for the A10-70L not F, so that may be why I dismissed it earlier as not intended for my tablet version.

Has the L version of the recovery been tested successfully on the F model tablet?

I think part of what I also need to understand is should I even be using the custom recovery or not?

As I said before I don't intend to use custom roms at this point, I just want the deeper access that root provides for misc. utility app purposes.

That said I also would like to make sure that in a worst case scenario I have a reliable way to fix my tablet.

I don't know if flashing the custom recovery early on and making a backup is better or worse than just re-flashing the stock rom later.

I would Ideally like to have the option of restoring the tablet to factory default so I can send it in for servicing if it ever needs it.

I'm not clear on how putting the custom recovery on the tablet would affect my ability to do that.

Is it easy enough to put the stock recovery back if necessary or is that complicated/risky?

Can I just root the tablet without doing the custom recovery and then use the default factory restore to remove root if I ever need the tablet serviced or need to update it (say to lollipop if that ever gets fixed) or is root access more complicated to undo than that?

Also, what is NB. OTA?

I haven't come across that so far and google failed me when I tried to look it up.

Thank you for getting back to me and I hope you can help me understand all this a bit better.
[Android Q&A, Help & Troubleshooting] Sparkrite:
First off, NB. OTA = Note Bene (latin, meaning note well). Over The Air.

I think you have a fair understanding of what rooting is and also what a custom recovery is, so the

choice is yours what you want to do, remember you can always go back to stock by flashing the rom linked to

in this thread with SPtools.

And that Carliv Recovery works with the tab2 A10-70F, I have it on mine.
[Android Q&A, Help & Troubleshooting] EternalGrump:
Alright, good to know that the custom recovery will work on the A10-70F.

There were still a number of questions that you didn't address though that I would like to get an answer on.

1) Is flashing the custom recovery and making a backup a better or worse (safer) option than re-flashing the stock rom?

2) I would like to have the option of restoring the tablet to factory default so I can send it in for servicing, how would putting the custom recovery on my tablet affect my ability to do that?

3) Is it easy enough to put the stock recovery back if necessary or is that complicated/risky and how would I go about that?

4) Can I root the tablet without the custom recovery and then use the default factory restore to remove root or is root access more complicated to undo than that?

I think I understand most everything else but these questions are the ones that are causing me the most unease with my being new to this process.

I'm trying to make sure I have a firm grasp of what the risks involved are and the best way to mitigate those risks so I can feel reasonably confident about what I'm doing.

I understand that which way I go about this is ultimately up to me but part of figuring out which option is best for me is understanding the consequences of choosing one option vs another.
[Android Q&A, Help & Troubleshooting] Sparkrite:
1) All flashing has some level of inherent risk, but it follows that just flashing a recovery carries less risk than flashing an entire ROM.

2) Putting a custom recovery on and then needing to revert fully to stock (if NOT rooted) would require flashing just the recovery partition, available within SPtools.

3) If you are comfortable using SPtools then it is easy, after loading the Scatter file within the full rom just select the "recovery" tick box within Sptools and flash.

4) No guarantee that using the default factory restore will unroot the tablet, a lot of root apps will allow you to remove root access if needed without flashing.

If you are very concerned about flashing anything then why not use an app like "Gobackup" or any of the myriad backup apps available that when rooted will allow you backup all your apps, settings and even layout of your screens.
[Android Q&A, Help & Troubleshooting] EternalGrump:
1) Ok, so flashing the custom recovery is safer than waiting and re-flashing the rom later.

I'm just guessing based on context but is the reason that flashing the recovery is safer because failing the recovery flash wont brick the tablet and or am I wrong about that?

What is the worst case scenario if the custom recovery flashing fails?

I know that failing a rom flash generally results in bricking the tablet but I don't know the outcome of the recovery failing to flash correctly.

2) From what you are saying about restoring the stock recovery it sounds like it's included in the stock rom.

So just to be clear, everything (not including SPtools & drivers) that I need to re-flash the stock recovery is contained in the A10-70F_S000021_150501_ROW_USER zip file from earlier in the thread correct?

I do see a recovery.img file inside it when I look, I just want to make sure I've got the correct recovery and don't have to go hunt it down still.

3) You said that if I'm concerned about flashing then I should use a backup program like GoBackup after root.

I guess I'm not entirely sure what the benefit would be.

GoBackup doesn't appear to backup the entire os so much as the user apps and settings, which is nice if the tablet has been in operation for a while but this one is new so not much is on it right now besides the default set of apps.

Does GoBackup provide any advantages over doing a full nandroid backup with carlivrecovery?

The main reason I can think of to use GoBackup would be if there are default apps on my tablet that might not be part of the stock rom but again I'm not sure why to use GoBackup as opposed to a nandroid backup.

4) I'm guessing I should flash the custom recovery and do my nandroid backup before rooting the tablet.

Is that the best order to do things in or do you have a better recommendation for ordering this whole process?
[Android Q&A, Help & Troubleshooting] sgtslaughter:
It took me a while to read through all this and to accumulate the files and tips. But afterwards it took me 5 Minutes to root the tab and I am really really really thankfull for you masters giving us apprentices the help we need!!!!!!!!!!!!!!!!!!!!!!!!
[Android Q&A, Help & Troubleshooting] EternalGrump:
Thanks for answering my questions in so much detail Old faithful, it put my mind a bit more at ease.

I think most of my questions are answered now, though I do want to discuss the last part of your post.

The rooting software discussed in this thread is kingroot not kingoroot, from what I can tell they are 2 similarly named but different programs.

From what I remember kingoroot causes some kind of issue that kingroot doesn't, I think kingoroot causes problems with removing root later.

The main reason I was planning to go with kingroot is that it has been the only successful method that I've seen discussed so far in this thread.

If the method you mentioned works I'd be curious to know how to go about it.

Could you explain it in more detail or provide a link to an explanation?

Also If you decide to try that method with your tablet I would be curious to know if it works.

I'll probably try to root my tablet sometime in the next day or two.

If you happen to post back before I do and confirm that the direct method works then I may try it but otherwise I'll probably go with kingroot since that has been confirmed to work.

Good luck with your root attempt, I hope it goes well for you.
[Android Q&A, Help & Troubleshooting] Old faithful:
I'm definitely going the cwm and super su way after having backed up my factory ROM. After Christmas, that is ;)
[Android Q&A, Help & Troubleshooting] clsA:
I ordered the 32gb model (ZA000086US) from Lenovo and it arrived yesterday (12/23/15).

The crazy part is it has a Build date of 12/15/2015. it's less than 10 days old and in my hands on the other side of the world ...amazing

it's still in the factory wrapping right now I'll get to it over the weekend.

Huge thanks to all that have contributed to this thread especially [MENTION=5658496]Sparkrite[/MENTION] (Great Job Sir)

And I'm not new to flashing at all, I have just never used SP Flash Tool but with the instructions posted here I'm confident their will be no problems

Merry Christmas Everyone.
[Android Q&A, Help & Troubleshooting] Old faithful:
Hmmm... I was under the impression that its the same thing except for the language... One in Chinese the other in English...

I'll be doing that today, just getting ready, done my backups already, making sure my external battery pack is fully charged ( we've had power failures like is often the case at that time of the year hete). In other words, backing up my factory ROM using mtkdroid and S P Flash.

Backing up is a one hour plus non interruptible process, that's why I'm making sure my laptop batteries are full.

After that I'll flash cwm and Super SU.

I'll make a (hopefully) concise summary of it afterwards.

Happy Christmas, we always celebrate at Christmas eve so today is just digest and relax day ;)

---------- Post added at 13:28 ---------- Previous post was at 13:20 ----------

Btw, Root is a _necessity_on this version of android as I just found out after inserting my new SD Card: The OS won't even let me _access_ it!

It's a good thing the anal retentive idiots at Android reinstated SD Card access in Lollipop, they must have received some nasty lawyers letters about rendering privately owned products that don't belong to them non functional. I wonder how many people returned the tablet to Lenovo precisely for that reason.

If I had money I wouldn't hesitate to sue these arrogant bastards.

Crippling hardware should be considered as criminal as sabotage and is a prime example of deliberate destruction of property, just as wilfully hostile as Digital Restriction Measures (DRM) are, which is nothing but another weapon of oligarchs to wage war against civilization. But I digress...
[Android Q&A, Help & Troubleshooting] Old faithful:
Well, I'm sorry to say that MTKDroidTools, which is needed to backup this tablet's factory ROM, even in its latest version, 2.5.3d, does NOT support this tablet's MT8165 chipset.

I guess we'll have to wait for a leak from Mediatek or on one of the published fatory ROMs for now.

If anyone here has any new info or workarounds, specifically about chipset equivalence and compatibility, please let us know. In other words, since I don't know what the MT8165 is compatible with I can't edit MKTDroidTols.ini to make it possible to create the scatter file.
[Android Q&A, Help & Troubleshooting] Old faithful:
OK, so I've been digging into scatter files and have found that both the posted factory ROM for the Tab 2 A10-70L (which is compatible with the 70F - only difference being the presence of a cellular radio on the 70L) and the 4.4.4 Carliv Recovery zips, which have proven to work on this tablet, have a scatter file with MT6752 in their names.

Am I correct to assume that the MT8165 should therefore be compatible with the MT6752 listed in the name of the factory ROM and the 4.4.4 Carliv zip recovery? I which case I would edit the MTKDroidTools.ini to list 6752:8165...

---------- Post added 26th December 2015 at 00:41 ---------- Previous post was 25th December 2015 at 23:47 ----------

OK, so it looks like there is no solution to backup this tablet's ROM using MTKDroidTools, as the development has apparently stopped :(

Flashing is therefore risky, although we can probably still be saved using the ROMs that have been posted previously. Not sure, however, if that will do in case warranty service is required (the posted 4.4.4 ROM is slightly different, at least for my tablet). Ah well...
[Android Q&A, Help & Troubleshooting] EternalGrump:
Are you sure you have the right stock rom?

I do remember there being a link posted earlier in the thread for a A10-70L rom but that isn't the one I picked up.

Ondigo posted a link to what is supposed to be an official factory stock rom for the A10-70F in his signature here: http://xdaforums.com/showpost.php?p=62511857&postcount=42

If you didn't have that one already, give it a try and see if that works any better.

There were people earlier in the thread saying they used the rom Ondigo provided to fully and successfully reflash their tablets after bricking so I would think it would work, unless lenovo did something to their newest iteration of the tablet since then.

That's disappointing to hear, I hope someone else will pick up the project.

It seems like a very useful/fairly critical tool.

One other thing, from a couple of your previous posts it sounds like your tablet is running lollipop, is that correct?

If so, I believe the rooting method for your tablet and the version of carlivrecovery that you require are different than for 4.4.4 KitKat.

You'll need to check the earlier parts of the thread for the differences but for sure I remember Sparkrite posting a link to a different version of carlivrecovery for 5.01 Lollipop.

http://xdaforums.com/showpost.php?p=63535771&postcount=128
[Android Q&A, Help & Troubleshooting] Old faithful:
Yes, that's the one I have, and I also have the update to it exactly as what my tablet is running, which I found on this German site here. So it's not so bad, except for the fact I am still looking for a way to backup the NVRAM (which may be possible once I have the CWM recovery installed).

As for the custom recovery, it's from a 70L and it is apparently compatible. Since that 70L based recovery shows in SP Flash to be MT6752 based just like the 70F stock ROM is, I see no reasons whatsoever to be alarmed and will definitely flash it when I can finally figure how to put the tablet in download mode for SP Flash! I'm a bit at a loss here since interrupting the process is risky, but when I click Download in SP Flash after loading the recovery in it, nothing happens... Which buttons should I press on the device, volume up? Down? Up plus power? down plus power? For how long? I can't believe no one has posted the correct procedure anywhere, I simply can't find it!!!

I know my vcom drivers are correctly since I'm perfectly able to communicate with the device using MTKDroidTools, and I've been able to push files to the device using adb so I've got the adb drivers correctly installed, but SP Flash has me at a loss... I'm probably missing something here, just haven't been able to figure it out yet.

I realize it's been a long process, but I always make sure my computing devices do exactly what I need them to do with NO interference from outside forces - it's a matter of principle, a principle I will NEVER budge from. Freedom is NOT negotiable, as simple as that.

Nope, KitKat 4.4.4, build A10-70F_S000022_150626_ROW. In other words, the Ondigo factory ROM plus the A10-70F_S000021_150501_ROW_TO_A10-70F_S000022_150626_ROW_USER_WCB1 update...
[Android Q&A, Help & Troubleshooting] clsA:
The download_mode is achieved by powering the tablet off and plugging in the USB to the pc. This is where you watch Device manager on your PC and install the SP Tools drivers

See post #211

Also someone mentioned hitting power to start the download