yashsingh1/xdaforums huggingface dataset:
[Android General] charlestek:
[MENTION=5919159]Tzul[/MENTION],

Yes, it is settled, that I should just do the readback with the standard scatter file and append userdata.

??? How one would load a file over a gig into a hex editor and figure out how to split it into the normal partition regions is beyond me.

Though for that size, I would have to use EmEditor: https://www.emeditor.com

(I'm not going to do this, so any answer would be hypothetical, but interesting)

---------- Post added at 08:49 PM ---------- Previous post was at 08:20 PM ----------

Quite an argument over eemc writes on the Asus (windows) transformer tablet/laptop forum:

http://www.transformerforums.com/forum/asus-transformer-book-t100-general-discussions/43595-32g-vs-64g-free-disk-space-3.html

Reinforces the argument that one in general should buy the tablet model with the higher Eemc memory, like buying the 32GB Tab 2 instead of the 16GB Tab 2 for memory write life reasons. Unfortunately it seems that the 32GB Tab 2 was never really marketed or sold much in the U.S. and the price premium was ridiculous.

It is therefore simplistic to think that you can make up for buying the Tab with the base smaller 16GB eeMC by adding MicroSD space. Indeed, every time I set the Tab 2 to store new apps on the MicroSD, Android kept on turning that setting off or reverting it, some kind of bug (on KitKat)
[Android General] A.Priori:
maybe a dumb question, but if I root, then want to apply lollipop recovery (by flashing the ota lollipop), will root remain?
[Android General] charlestek:
You might want to go back to the first page of this thread and see if the instructions say what partition gets changed with the root package. If you overwrite that partition with a flash, then I would expect the rooting to be gone.
[Android General] EZ-Poop:
Sorry, question put wrong... Besides the obvious descriptiveness, I didn't know that a "X.bin" file obviously is sort of the same as what SPFT creates in standard "ROM_X" folders.

But as far as I can tell, all went well, thanks to your kind instructions. Really hope I'll never need it but at least now I'm prepared just in case.

Thanks again.
[Android General] charlestek:
[MENTION=4111468]A.Priori[/MENTION]

You didn't specify which program you use to root.

Per http://xdaforums.com/android/general/guide-lenovo-tab-2-a10-70-root-t3279322/post65259425#post65259425

So, therefore if you flash the boot partition with the standard lollipop image, you most likely loose the rooting functionality provided by SuperSu, unless its mechanism survives outside of the boot partition (I do not know for sure).
[Android General] Tzul:
You're confusing terminology a bit. "Applying the Lollipop recovery" doesn't really make sense. You mean flashing the Lollipop update.

The update will overwrite the system partition as well as the boot partition, meaning it will eradicate root (whether "systemless" root or not).

But that's an absolute non-issue, because after the update, you can simply flash TWRP as custom recovery, boot into it, and reinstall SuperSU for root.
[Android General] charlestek:
[MENTION=5919159]Tzul[/MENTION],

Can you remind me what the features of the new preloader and bootloader are?
[Android General] Tzul:
It's actually quite simple, albeit tedious. Every decent hex editor should be able to handle that.

It's also simple to write a small program or shell script that does the work for you.

I don't really agree with that. If the higher capacity model is available and doesn't cost outrageously more, then it's a no-brainer to buy. But the benefit would be increased internal storage, not really increased flash memory service life. Because long before you'll run into that limit, you will have broken the tablet, or replaced it with a newer model anyway. Unless you're writing gigabytes of data to the internal storage each day...

---------- Post added at 03:07 AM ---------- Previous post was at 01:59 AM ----------

The newer bootloader has better Fastboot support (allows flashing of all partitions*). And it patches the chip ID to the correct value, so it'll no longer read "MT6752".

I don't know about the differences of the preloader. But since both preloader and bootloader work together to initialize different parts of the hardware, I think they should be kept "in sync" (old preloader + old bootloader, OR new preloader + new bootloader).

*I made a patched version of the old bootloader that also allows flashing more partitions via Fastboot. The file is "lk.patched.bin" and available in this archive for Tab 2 A10-70F, or in this archive for Tab 2 A10-70L.
[Android General] charlestek:
With userdata dumped, we're talking about a 14gig file here. In any case, if I did want to do this, I would probably rather do it with a program then take the risk of

chopping off the data at the wrong address. But I haven't done any programming in 5 years and don't intend to go back. When javascript became a first class programming language (php too for that matter), it was long overdue to get out of programming. Maybe Dart will someday kill javascript, it deserves to die, anyway, I digress.....

This article has a nice explanation:

http://www.androidcentral.com/android-z-what-fastboot

What is fastboot? In Android, fastboot is a special diagnostic and engineering protocol that you can boot your Android device into. While in fastboot, you can modify the file system images from a computer over a USB connection. It's a powerful, nerdy tool that deserves to be broken down into terms we all can understand -- let's try and do that.

Not all phones have a fastboot mode that the user can access. It's turned on with Nexus devices by default (as well as a few other phones and tablets) and has been enabled by independent Android developers and enthusiasts on some other phones. It also requires more than what ships with the Android SDK, and different USB drivers for Windows computers. Fastboot runs on Windows, Mac, and Linux and all the information about setting it up can be found in the forums if you're interested. Once set up, you boot your phone to fastboot and you can flash image files to your phone's internal memory. Flashing a custom recovery like ClockworkMod is a popular use case, as is resetting it all back using factory images after we're done breaking things. The images you flash don't need to be signed with a particular key, so just about anything will try to flash -- even if it shouldn't be used, so use care. There are other commands you can use with fastboot, and they're a bit more advanced. Things like erasing partitions and overriding kernel command line options can be done, and this makes the tool very useful for developing hardware and software solutions that may need customized booting procedures. With a little bit of knowledge, and the right Android hardware, fastboot can be a great tool.
[Android General] A.Priori:
Ok so I just used kingroot on 5.01 and it worked. I manually replaced it with superSU. Need to flash twrp and xposed next. So far so good. Any drawbacks to staying with lollipop?
[Android General] Old faithful:
Lollipop has better color fidelity for photographs, under KitKat colors are way too saturated. KitKat supports more apps, especially older ones and is the main reason I went back to KitKat (the second is the native battery percentage meter). Also KitKat's SD Card no-write bug is essentially fixed using a simple app if you're rooted. If you don't mind Material Design and the excessive whiteness of it all, stay on Lollipop, it now works just as well as KitKat contrarily to the early iterations, which had issues with WiFi.

In other words, no huge difference between the two, just check the features you like best and go for the OS that supports them.
[Android General] charlestek:
[MENTION=1454767]Old faithful[/MENTION]

Have you noticed any difference in battery life between KitKat and Lollipop (although Tzul recommends his AAL brightness patch, that may lower power consumption)?
[Android General] nannycrick:
Is that patch for Kitkat or Lollipop? And is it downloaded as a separate fix? I didn't see it in the OP.
[Android General] EZ-Poop:
I'm almost finished with setting this slab up. Just now I realize that I missed to install the latest Kitkat update (Typ 0: S000018_150423 to S000019_150625). Having gone through steps 1-3 of this guide, how can I safely install this update now?

The other issue I'm having: I've removed apps from autostart for the main user using ES File Explorer but can't seem to find to do so for other users (multi user). How to fix this?
[Android General] Tzul:
[MENTION=4717484]nannycrick[/MENTION] What patch? If you mean AAL, everything is explained in this post (the patch is only for Kitkat, because in Lollipop AAL can be disabled by other means).

[MENTION=7313452]EZ-Poop[/MENTION] The update will most likely fail to install now, due to the "root check", and some files that might have been changed or renamed (TWRP will have renamed /system/recovery-from-boot.p to /system/recovery-from-boot.bak, and that's one of the files that the update tries to patch... if it can't find it, it'll abort).
[Android General] EZ-Poop:
So what would I have to do then to install Typ 0: S000018_150423 to S000019_150625?
[Android General] Tzul:
[MENTION=7313452]EZ-Poop[/MENTION] I don't know for sure, because I've never run into this problem myself and therefore never analyzed it. You might have to completely uninstall Xposed and SuperSU (unroot), restore the S000018 stock recovery (I have it here), rename /system/recovery-from-boot.bak back to /system/recovery-from-boot.p, then try to install the update with the stock recovery.
[Android General] EZ-Poop:
F*ck, guess I'll stay on S000018_150423 then.

Is there a changelog for S000019_150625 somewhere?
[Android General] Old faithful:
Since patching the AAL using Tzul's patch it's been outstanding on KitKat. Also didn't notice much of a difference when I was on Lollipop. I would say in constant use browsing and tapatalking I use about 6% per hour. For my usage, I typically get 2 days out of it before recharging when it gets down to 40% or so. I try to avoid using the USB port too much, if it breaks you'd be in big trouble as it's soldered directly on the motherboard.

---------- Post added at 17:04 ---------- Previous post was at 17:00 ----------

None that I read about, perhaps they have info on the Lenovo forums. Honestly, I didn't notice any differences.
[Android General] charlestek:
[MENTION=1454767]Old faithful[/MENTION],

I had been considering buying a right angle micro sd adapter to prevent wear problems on the Tab 2 micro usb connector:

http://www.miniinthebox.com/9mm-long-connector-90-degree-right-angled-micro-usb-2-0-5pin-male-to-female-extension-adapter-free-shipping_p1677599.html?currency=USD&litb_from=paid_adwords_shopping&utm_source=google_shopping&utm_medium=cpc&adword_mt=&adword_ct=94710053401&adword_kw=&adword_pos=1o1&adword_pl=&adword_net=g&adword_tar=&adw_src_id=1364803665_328601281_21739983481_pla-136049705056&gclid=CMbX-tnJvssCFZQbgQod93EAPw
[Android General] EZ-Poop:
Take a fine rasp or an emery board and file down the two pins of the plug (a bit, not completely).

This will reduce the force on the socket when unplugging.
[Android General] charlestek:
[MENTION=7313452]EZ-Poop[/MENTION]

I'm not sure I would want to do that. Maybe filing down the edges of the male connector might reduce insertion force, but usually the issue is getting the male plug centered, as it usually hits the edges of the female connector not uniformly and you sort of initially scrape the connector in.

I have a couple of very high quality Anker usb to micro usb cables that I normally use.
[Android General] EZ-Poop:
Not the edges, the 2 spring pins!
[Android General] Old faithful:
Great idea, unfortunately it wouldn't fit in my handy dandy protective sleeve anymore :(

I'd love to find something really low profile, something a little bit like that one...

[IMG="low profile micro usb connector"]http://www.howardforums.com/attachment.php?attachmentid=104403&d=1391674678[/IMG]
[Android General] charlestek:
[MENTION=1454767]Old faithful[/MENTION]

I use this leather case with bluetooth keyboard. There is plenty of room for the right angle connector I cited. The case is great, the keyboard keys are a little too close together to type well though:

http://www.amazon.com/dp/B00U67WXG6/ref=pe_825000_114717100_TE_item

I also do have the Lenovo Oem bluetooth keyboard whose keys are bigger and space further apart, but it is made for a bare tablet to sit in a groove on top.
[Android General] nannycrick:
Thanks Tzul! I hadn't read that post. Had to work the weekend with my old man parked on the couch cause he was off! I'm also busy STILL trying to resurrect my dead RCA Pro II 10". It's a matter of pride & revenge now! I downloaded the patch and it's working...thanks for the tip!

I gotta pay closer attention to this discussion! You guys are full of helpful tidbits!

---------- Post added at 12:44 AM ---------- Previous post was at 12:33 AM ----------

Old Fàithful...I got my Evercase fitted leather case on Amazon too! And I bought that 90° right angle adapter you mentioned. Well worth it! It connects my printer to my tablet. Had a hard time connecting other usb devices but the printer was the important thing! I'm almost "weened" off of needing a dedicated keyboard now. Still working with Google Keyboard w/Flat Style module for Xposed! It's set at 75% and a nice blue grey color to the background! Me likey!
[Android General] EZ-Poop:
To whom it may concern, here's my post on the Lenovo forum:

https://forums.lenovo.com/t5/Lenovo...ovo-TAB-2-A10-70L-S000019-150625/td-p/3282746

Let's see what happens. :cyclops:
[Android General] Old faithful:
Nice :good::good::good::good:

But I got my sleeve for a mere CAD3 (USD2.25) and it's quite well made. pouch for touch pen. Magnetic closure. Suede like internal material. faux leather exterior with sturdy stitching. The way it's stitched it should protect the tablet from a corner fall. double thcinedd t from the flap should give it good protection to the glass.

Of course, no keyboard, but protection aplenty. I liked it so much I went back to the dollar store where I got it, apparently it's some surplus, and got three more... For when it will inevitably wear out and fall apart (like the phone cases).

Here's a couple of pictures. For fellow Canadians, it was still available from at several Dollaramas in Quebec as of last week. Bring the tablet and try it in store, some of them are a bit tight.

---------- Post added at 00:07 ---------- Previous post was at 00:04 ----------

Well to install the update on a rooted device definitely go with Tzul's recommendations, he's our local guru.
[Android General] charlestek:
I would suspect that Tzul is right, how much trouble would it be to unroot it, etc. then apply the update?
[Android General] rumbla:
Sorry, here again, with another noobish question.

KitKat served me well...now tho, I would like to experiment out some more with this tablet.

So, before I do anything "bad" I want to ask if there are any irreplaceable partitions other then the "NvRAM" one.

I already have a "ReadBack" of this ROM3 partition, after loading the scatter-file from the last firmware I flashed (A10-70F_S000021_150501_ROW_USER).

Is this partition enough to have a "Pristine/BrandNew" A10-70f tablet (software wise, naturally)?

Also, another question.

Till lately, I didn't really notice how annoying is the AAL.

Now, I would like to install Tzul's patch for it (on this KitKat firmware, without reflashing it completely).

As I understand, I need to flash TWRP (recovery_twrp2870_for_LenovoTab2A10-70_Android4.img).

Two way...directly from Android using apps (the usual listed apps) or using SPFT.

Going the SPFT way, I've noticed the two scatter files (the one from TWRP zip and the one from the firmware directory) differs for:

Only present in the firmware scatter. Any problem there?

Thank you
[Android General] Tzul:
[MENTION=7268959]rumbla[/MENTION] You should at the very least make a backup of the "proinfo" and "nvram" partitions, because they are unique on each tablet. I also recommend changing the filenames from "ROM_2" and "ROM_3" to something more useful, e.g. "proinfo.bin" and "nvram.bin".

Normally, these two partitions won't be overwritten, so you never have to restore them. But accidents can happen, and it's better to be prepared.

To get back to a "pristine" state, you can flash an SPFT firmware package. Or an official "type 1" update, and do a factory reset.

Yes, you can flash TWRP (recovery_twrp2870_for_A10-70F_Android4.img) via SPFT, or Fastboot (but only if you have my patched bootloader or the new one), or from within Android (only if you have root).

This checksum value is irrelevant, you can ignore it.
[Android General] nannycrick:
You guys have brought up a very good subject...

How to restore back to factory stock after life as a rooted device. Although I'm happy with my Tab2, some readers may have the reason to change tablets & sell their Tab2. I personally make it a point never to sell a rooted device, so the need to change back may be required for some.

After uninstalling the root dependent apps, where does one go from there? Flash stock recovery then uninstall SuperSU or the other way around?

And Old Faithful... Nice sleeve! I couldn't find anything that affordable here in the US and I wanted a fitted case to protect that big glass screen, besides just the screen protector. Here's a pic of the Evercase available on Amazon for about $15 USD.
[Android General] nannycrick:
Found a good resource for MTK device stuff...

Needrom.com. they have the latest SPFT, MTK Driver Auto Installer, Lenovo specific drivers, etc. Found a Lenovo USB otg helper apk there. It works perfect to help hook up my Tab2. For USB accessory folks, I recommend that one instead of the generic on posted on Google Play. Now on to fix (or go down trying) that RCA Pro II ! It's another MTK 8127 device. Grrrr!
[Android General] charlestek:
[MENTION=1454767]Old faithful[/MENTION],

That is a nice pouch. You can get a plain leather wrapping case from Amazon for about $8 US, but the one I tried did not have the proper holes for the speakers and a poor standup mount, such that the tablet fell over backwards. There are some better models. With the case around the tablet all the time, it would be hard to damage the plastic corners or the back for which you run the risk when using the tablet bare.

I also forgot that you are one of the few that are sticking to KitKat. Theoretically using Lollipop with ART runtime and 64 bit the tablet should run better. .....Theoretically.... :)

BTW, If Donald Trump becomes president, I may join you in Canada.....
[Android General] Tzul:
[MENTION=4717484]nannycrick[/MENTION] I know needrom.com, but I don't particularly like it. It may be a good source for firmwares for more exotic devices. But things like USB OTG Helper I'd rather download from their original source (I guess it's this app... there are more like it, e.g. Paragon and Stickmount. Personally, I use Stickmount Pro, but I rarely need it). You also don't need any Lenovo-specific drivers, as far as I know.

What's the problem with your RCA Pro II? Have you found firmware for it?
[Android General] nannycrick:
Needrom.com has firmware listed for it but, I already have the scatter file , and a backup for it that I made using MTK Droid Tools, but can't seem to flash! I have three mtk tablets...my Tab2 on mtk 8127 chips, my dead RCA Pro II also on mtk 8127 chips, and a working rooted & backup SM n9106v 10" dual sim on mtk 6572 chips that has a loose charge port but still working, rooted w/twrp recovery. My Tab2 is great! Thanks for your help on that! The RCA died after the last official system update loaded BEFORE rooting. Sent it back for repair. Got it back running but "kinda" rooted. Rooted it with Kingroot & tried to flash twrp using Flashify. It bricked. I know It's running but I have no bootloader, no logo spinning, no sign of life at all. My HP PC sees it and has it listed as a USB device. I can't get my backup nvram, scatter file, boot or recovery to flash. I've tried. I may sell it for parts!

On a different note..I downloaded the Google Play version of USB OTG Helper and it didn't work. I clicked a link in the app for a "stock rom" version and it sent me the Lenovo version of the same app. It works with my Cannon printer now. That "driver" was listed on Needrom.com. It's where I seem to wind up for these MTK tablets. I so glad for this forum. It's everything for my Tab2...consolidated!

Now..deciding to go Lollipop in my tab2 or stay. I think I'll put that thought on the back burner until I get the RCA fixed or sold for parts! Any takers? LOL!
[Android General] charlestek:
So you have installed the Mediatek Vcom preloader driver on your PC in testsigning mode or via booting with F8 to accept unsigned drivers and tried SPFT on the RCA???
[Android General] nannycrick:
I've tried SPFT on it. I just downloaded SPFT Driver Auto Installer and will install it when I get back from my yearly visit with the local tax office! Grrrr! I'm not sure on which mode I have the Vcom running in. Maybe that's the whole issue with my backup not flashing. I didn't use SPFT or MTK Droid Tools on the Tab2. I did make a complete backup..nvram, and all with your ported TWRP recovery. All kept on a 32GB SD card. I'll check on it and let you know. The two devices are similar so I have to be careful to keep the files for the one away & out of the other! Thanks for the advice!
[Android General] charlestek:
I would use the older SPFT drivers, though I have played with the more recent auto ones.

Tzul has a link a few pages back for me.

Read this regarding unsigned drivers:

https://www.raymond.cc/blog/loading-unsigned-drivers-in-windows-7-and-vista-64-bit-x64/2/

Remember that you must configure SPFT first, then MAKE SURE SPFT IS IN "DOWNLOAD" MODE ONLY, AND THE USB CABLE IS DISCONNECTED, THE POWER TO THE TABLET IS OFF, then click the green download arrow in SPFT, and THEN AND ONLY THEN, CONNECT THE USB CABLE TO INITIATE THE DA DOWNLOAD AND THE FLASH

Probably, you DO NOT WANT TO FLASH THE PRELOADER PARTITION.

Read this regarding unbrick, and read Tzul's explantion of the boot sequence earlier in this thread.

http://laurentiumihet.ro/technology/sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices/
[Android General] nannycrick:
Thanks! I'll try installing & running the correct drivers for Windows 10 32 bit (x86). Hoping for the best!

One difficulty I'm having is figuring out if it's running or off as I have no visual screen working to tell. I may have to let it run out of power a few days, then try! If this works..I'm buying beers for everyone!

Sent by my happy Tab2 via Wifi Tether Router by Fabio Grasso in my HTC Desire 626s running Nightbreed813's Debloat rom.
[Android General] Old faithful:
Sleeve and keyboard

Funny thing is, the sleeve was originally made for... Verizon!!! (if you look closely at the front you can faintly notice the logo).

For those in my area who are interested - Dollarama has a no return final sales policy so make sure it fits the tablet before purchasing, I simply took a chance. Also check them thoroughly, they're obviously handmade, there are minute differences between them, check the stitching, furthermore after purchase I tried them and two were a bit tight lengthwise, I'll have to stretch them a bit before using them (using a piece of plywood and moistening the fabric usually works great for that, like fitting a tight shoe)

As for a keyboard - I'm still looking into it although I am not sure, I'd be looking to get exact functionality replication with a PC keyboard with shorcuts, if anyone has tried a keyboard and has been satisfied with the results, please let me know. Also, I haven't been able to find button-type keyboards (great for clumsy fingers - chiclet like keyboards are very unforgiving with imprecise finger location)