yashsingh1/xdaforums huggingface dataset:
[Android General] bigrammy:
Hi,

Well this is venturing well off topic for this particular thread which is already very complicated/confusing for the newbe's :o

I did follow the maze and figured it out in the end a have already done these mod's on my tablet, logo's boot animation, pixel launcher, sony id, de-bloat, etc.

I hit a few bumps along the way with things like image format, resizing, unpacking, repacking, frame rates, etc etc but I eventually got there :laugh:

I cannot simply say do this do that job done if you want to start from scratch just in case you hit the same bumps as me which will need more detailed a explanations.

I will pm you some detailed info at the end of my shift roster in a couple of day's

Regards.
[Android General] theclarkster:
Something strange seems to be happening when Google screen search is turned on. When I hold the home button down to activate it, screen search does indeed activate. However, the swipe up to open Google search icon appears on top of it. Does this happen to anyone else and, if so, is there a fix for it?

* I am running Marshmallow, so it could be isolated to that particular version. I don't remember if this was an issue on Lollipop.
[Android General] coolbeans2016:
Exactly

Yes, thats exactly what I am trying to do! Care to elaborate?!!!
[Android General] kryzeK:
Is there any update for Nougat? Any custom ROM? Or is the maximum only Stock 6.0?
[Android General] bigrammy:
To all experienced users

I have opened a new thread to discuss all these kind of questions and share info ;)

https://xdaforums.com/android/general/lenovo-tab-2-a10-70-mm-6-0-custom-roms-t3587177#post71798442
[Android General] chris5s:
I used ffmpeg in a terminal to convert jpeg images from a marshmallow bootanimation.zip into a usable mp4.

Took a few goes because the tablet is quite picky about frame size and rate, and eventually i stopped at something slightly less than perfect because the time and effort was beginning to outweigh the result! (All done using fedora Linux, there may be a Win program that does it too)

Here :good:

Peace.
[Android General] bigrammy:
No Nougat update or any custom 6.0 ROM's out in the wild just yet :o

We are all working with the stock 6.0 prebuilt kernel at the moment unless someone knows how to upstream the 4.4 KK KERNEL Source which maybe possible :confused:

I started a new thread for just this kind of discussion Here if you fancy getting your hands dirty. :fingers-crossed:
[Android General] zzzk:
Downgrade from android 5.0.1 to 4.4

Hello,

I have the a10-70F with 5.0.1 and want to downgrade to 4.4. I see that I need to install twrp, first. I see there is a version 5 and a version 4. Do I need to use version 5 of twrp because I'm already on 5.0.1, then downgrade to 4.4 android with the procedures on the 1st page? After I downgrade to android 4.4, do I need to also downgrade twrp to version 4? Here are the twrp files available from the 1st page links:

recovery_twrp2870_for_A10-70F_Android4

recovery_twrp2870_for_A10-70F_Android5

Once I downgrade to 4.4 android, I can root with the "beta supersu" no?
[Android General] bigrammy:
Firmware Upgrades and Downgrades are best accomplished using SPFlashtool.

If you Downgrade to 4.4 then you should add the TWRP Android4 to the flash.

Simply remove the stock recovery.img from the folder and rename the TWRP4 recovery to recovery.img add it to the folder and flash it all in one go choose "Firmware Upgrade" mode in SPFlashTool.

When the flash is complete Unplug the Tablet wait a couple of minutes then using the buttons boot to recovery copy the SuperSU "system root" to the internal sd-card Then install it. (I am not sure about the v4 but I think TWRP has supersu built in)

If you accidentally boot to system first then the TWRP will be replaced (Overwrote) with the Stock recovery and you would need to re flash only the TWRP recovery again just using Download mode in SPFlashTool.

So Android 4.4 KK ROM = recovery_twrp2870_for_A10-70F_Android4

So Android 5.0 LP ROM = recovery_twrp2870_for_A10-70F_Android5

So Android 6.0 MM ROM = recovery_twrp2870_for_A10-70F_Android6

Simply put most Mediatek ROM's need to have matching boot and recovery Kernel versions
[Android General] zzzk:
Flash Question

Hello,

I unzipped the rar, then replaced the recovery.img as you said with version 4. Do I use the For the bin, preloader_huaqin8752_tb_b2d_kk from the extracted files? Also, do I need a scatter file for this "all-in-one" flash to twrp4 and kitkat 4.4 in one go? Thank you for your help.
[Android General] bigrammy:
The firmware is for flashing your tablet using SPFlashTool only.

TWRP will not flash this kind of update.

When you use SPFlashTool you will be ask to load that scatter file.

See this and hundred's more on how to use SPFlashTool

[YOUTUBE]1p2anwd7_RA[/YOUTUBE]

Or if you prefer to read see this post https://xdaforums.com/showpost.php?p=50322823&postcount=5 by [MENTION=5186178]bluefirebird[/MENTION] (aka Carliv) :good:
[Android General] zzzk:
checksum error

Hello,

You said to replace the stock recovery.img with the twrp 4 version and flash it with spflashtool. I did that, but when I add the stock rom scatter file, I get a checksum error. Do I need to create a new scatter file because I changed the file? Thank you.
[Android General] bigrammy:
Just remove the md5 file from the folder and reload the scatter. ;)
[Android General] zzzk:
Safe for nvram, etc?

Oh, ok, thank you. I read in the post it is important to choose, "download", but you said to choose "firmware upgrade" I assume because I'm doing twrp and the stock rom in one go. There is a warning to choose "download" so it does not mess with the nvram, etc. Sorry, just being careful I understand. If I choose "firmware upgrade" do I need to be careful somehow of the nvram? Thank you.
[Android General] bigrammy:
It is not compulsory to use the "Firmware + Upgrade" option just good practice.

"Download" will generally work fine in most cases but I always use the "Firmware + Upgrade" option to Upgrade or downgrade my firmware and I have never fried my nvram with that option the clue to it's use is in the name :laugh:

EDIT: Just to be clear After the Downgrade is complete you would just use the "Download" option until you next Upgrade the firmware version.
[Android General] zzzk:
Ok, thank you. I used the "download" option with the stock 4.4 and twrp method you gave. It seems to have worked. I assume that was fine, then? Thank you. If I upgrade to Lollipop with OTA from here, will I retain root? Thank you.
[Android General] bigrammy:
No you will not retain root and you will need to re-flash the correct TWRP and re run Supersu.

Flashing any Official OTA will usually require that you have a unmodified system and re-flash the stock recovery.

I would recommend you use SPFlashTool updates rather than official OTA's :good:
[Android General] Tzul:
The "bitness" must match, i.e. you can't have a recovery image with 32 bit kernel and a boot image with 64 bit kernel at the same time. I don't know whether that's by design or a bug in the bootloader. But when the bitness is the same, boot and recovery can use different kernels.

The three modes are "Download Only", "Format All + Download", and "Firmware Upgrade".

The warning is to not use "Format All + Download", because it really does format everything, including hidden partitions like NVRAM.

"Download Only" is the one to use in 99% of cases, even when upgrading or downgrading firmwares.

The only thing that "Firmware Upgrade" does differently is to enforce that all regular partitions are flashed (i.e. you can't just update a single partition like recovery with it), and it will rewrite the partition table(s) on the device, using the data from the scatter file. Therefore, if the start address or size of some partition changed, you have to use "Firmware Upgrade". Otherwise you don't (it's pointless and even slightly detrimental to the flash chip to let the SPFT rewrite partition tables if they haven't changed).

Last time that I know of when "Firmware Upgrade" was really necessary was upgrading some devices from Jelly Bean to Kitkat, because the sizes of the boot and recovery partitions at that point was increased from 6MB to 16MB in order to accomodate larger kernels and ramdisks.
[Android General] bigrammy:
Hi Tzul,

5.0 and 6.0 use the same bitness as far as I know yet in the majority of my oem mediatek devices a 5.0 recovery kernel will not boot on 6.0 environment and vise versa. Iike you say not sure if this is by design or a bug in the Mediatek source some place.

I have noticed that the Team M.A.D builds do not seem require recovery kernel upgrade's

The only exception of the devices I own is my Sony C4 (my6752) which seems not to care about Kernel version 5.0 > <6.0

My reason for using "Firmware Upgrade" for Firmware Upgrades stems back to my Elephone P6000 days.

Many people had nvram errors and sensors not working battery drain etc etc after upgrading their firmware 4.4.4 to 5.0 even though the Partition Table had not changed.

Using the "Firmware Upgrade" option prevented any errors and was insisted upon by Elephone.

It was theorised that because some of .img's are trimmed that old files may be left on the partitions been flashed and using the "Firmware Upgrade" option wiped clean each partition before flashing the new .img's.

Maybe this was a problem that SPFlashTool had at that time or something that Elephone messed up I am not sure.

I have stuck with the theory of using "Firmware Upgrade" for Firmware Upgrades ever since on all my MediaTek devices and never once had any issue so it does no harm to use the correct function option for the task you are doing as said it's just good working practice. :)
[Android General] zzzk:
xposed warning, Aliyun

Hello,

Just downgraded to kitkat 4.4. Now trying to install xposed according to your procedures. However, I get a warning "Aliyun" OS may cause loops, etc. Does this mean I cannot install it even though you have the procedure for this device, Lenovo, etc.

Am I correct in saying that the download link for kitkat on page 1 is actually NOT kitkat, but aliyun? Is that a bad thing? Can I flash a stock kitkat from somewhere? Any known links? If I do that, can I resore the apps with titanium after flashing even though Aliyun is a similar os?

Thank you.
[Android General] pjadec:
Sorry, but xposed in KK version will not work well, because this Aliyun complications. You have go to LP or MM version if you want xposed to work
[Android General] coolbeans2016:
gonna jump in & bug ya in herre!

In the new thread for MM 6.0 OP says "DO NOT MENTION SPFLASH TOOL!"

So........

Question is, for the .custom-stock-v1.zip, use TWRP to flash? I loaded SPFlash Tool and it did not find any scatter file to load and I did not see one browsing manually..........

Sent a pm on this but really getting antsy waitin on a reply, sorry, wanna try that out!

So we have a ROM now thats flashable through TWRP?!!!

Waitin on ya response!

Thanks,

zach :cool:
[Android General] bigrammy:
It's for TWRP and the META-INF folder gives you a clue as to what kind of update it is. :rolleyes:

It's a Holiday here in the UK so I have been out visiting family hence the delay in my reply's.
[Android General] bryandroid98:
This tablet update to Marshmallow 6.0??
[Android General] zzzk:
Kitkat non-aliyun version?

Ok, thank you for letting me know. Do you know of a link for a Kitkat, non-aliyun version? Thank you
[Android General] pjadec:
Sorry, but there are no non-aliyun KK version at all. All KK version have aliyun. I had tryed it and no go with xposed + KK version
[Android General] apnt1984:
Yes,

And works like a charm.
[Android General] chris5s:
Might be worth heading over here :good:
[Android General] janek125:
Hello everyone

Couple weeks ago I was install Marshmallow on my A10-70L. Everything work fine except battery time. In my opinion is shorter than in Android 5.

Anyone know how fix battery drain?

Couple days ago I was install CPU-Z for Android. My SoC is a MT 6752 and it support on Android 7. Maybe anyone compile newest version for our tablets? Maybe is similar device to recompile an OS.

On Google I was seen Jiayu S3 with the same processor. Maybe this or LineageOS is a answer?

Any LineageOS developer maybe read this and can made OS for as.

Thanks.
[Android General] gtallmadge:
Look at post #1583 by Chris5s to fix the battery drain.
[Android General] runekock:
Here is a direct link:

https://xdaforums.com/android/general/guide-lenovo-tab-2-a10-70-root-t3279322/post69639163

More important, has anyone actually tried this on the L model? Chris thinks it has something to do with the radio, so it might disable the mobile network, SMS or something.
[Android General] Trainingwheels:
Backward Compatibility

Is this version of TWRP compatible with earlier versions of Android?
[Android General] zMILWAUKEE:
no its not, check first page of thread, all the links you need are there, https://www.androidfilehost.com/?w=files&flid=68727 better yet TZul has all the TWRP versions for this tablet there
[Android General] ai5g:
windows doesn't recognize the preloader

I cannot find the tab in the device manager and there is no sound from windows when I connect it.

I have a Lenovo Tab 2 A10-70F (WLAN version) and windows 10 64 bits. I open the device manager and attach the tab, which is turned of. after a few seconds, the tab displays the lenovo logo and shows that it is charging, but windows doesn't recognize anything. I have then installed the driver (cdc-acm.inf) in windows directly and repeated the procedure, but again nothing happens in windows. I have also repeated it with different USB cables and at different USB ports - nothing.

Any ideas how I could solve it?

Thank you very much!!
[Android General] zMILWAUKEE:
here is great tut.. https://www.youtube.com/watch?v=sADkzyI8Z5Q
[Android General] charlestek:
Need to ensure userdata is destructively erased

Recently, the usb charging port on my Tab 2 A10-70F was damaged apparently due to too much pressure on a usb cable plug in the connector.

The connector is loose and intermittent for charging and even if it charges it does so extremely slowly.

So I had a Square Trade warranty on the device and am going to send it to them for repair or ?? whatever they decide depending on how badly the circuit board might be damaged at the soldering points for the connector.

So I want to erase my userdata, and I imagine I can just do a factory reset, or flash only the userdata with the flash tool.

However, since this is solid state memory, I'm not sure if the data actually gets erased or is overwritten with the stock userdata partition.

How can I make sure the userdata is destructively erased???

The few articles I've seen pertain to android phones and rely on the ability to encrypt user data, but I don't think the Tab 2 has this option in the latest marshmallow firmware.

http://www.ubergizmo.com/how-to/wipe-android-phone-tablet/

BTW, Right now Lenovo is selling brand new Tab 2 A10-70F's at a clearance price of $119, vs Newegg's price of $189.

http://www3.lenovo.com/us/en/landingpage/promotions/weekly-sale/tablets/?gclid=CjwKEAjw3KDIBRCz0KvZlJ7k4TgSJABDqOK7oV6b0H48rkjbBUn0pYZTiWtspHq-_y6jmhoZFT5cMRoCXaHw_wcB&cid=us:sem:pd8gxr|se|google|kw_1899|Lenovo_Tablet|NE_Lenovo_Tablet&s_kwcid=AL!4030!3!192748630055!e!!g!!lenovo%20tablets&ef_id=WI1rBgAABH-GFyag:20170503044544:s
[Android General] Tzul:
Overwrite and trim. First, delete the internal storage manually or do a full factory reset.

Then, open a root shell, e.g. the terminal in TWRP, or an ADB shell followed by "su", and type this:

cd /data
dd if=/dev/zero of=bla bs=4k
rm bla
fstrim -v /data

Explanation:

The first command changes the current directory to /data (which corresponds to the userdata partition). You can also do this for /system and /cache, but make sure they're mounted as writeable.

The second command copies data from input file "/dev/zero" to output file "bla" (in the current directory), in blocks of 4 KB. "/dev/zero" is a special Linux device that produces an endless amount of 0-bytes. Alternatively, you could also use "/dev/urandom" for random bytes. Shouldn't make a difference. A larger blocksize such as 128K or even 1M will be slightly faster, just make sure it's a power of 2 and not too large (ideally, it should be the same size as a flash/eMMC memory page, which should be something like 2K, 4K, 8K). The "dd" command will abort once there is no free space left on the partition.

The "rm" command will delete the garbage file we just created.

The "fstrim" command will report all unused (free) blocks in the specified filesystem to the eMMC flash chip, so that the chip can purge/trim them. So, all the free space we just overwrote with zero or random bytes should now be completely wiped.
[Android General] charlestek:
Wiping Tab 2 Userdata with zeros

[MENTION=5919159]Tzul[/MENTION]

That sounds great. It does ? imply that the tablet is rooted?, which I have not done.

Please verify that I need to root the tablet.

Thanks,

Phil
[Android General] Tzul:
Like I wrote, you should use a root shell. Actually, for the userdata partition, you can do everything without root, except for fstrim. Just go to a directory where you have write permission, e.g. /data/local/tmp instead of /data.

You don't necessarily need to root your tablet, though. TWRP gives you a root shell by default, both via the GUI terminal, and ADB.
[Android General] charlestek:
[MENTION=5919159]Tzul[/MENTION],

Thanks again, I will use ADB from my PC to do the job.
[Android General] srinagar:
12345
[Android General] woweetablet@gmail.com:
No video. Any tips on replacing the LCD Video screen?

Off Topic: My tablet has a dead screen.

My Lenovo Tab2 A10-70 went dark. When powered on the device vibrates, but shows nothing.

Have you attempted a video screen replacement? Do you have any suggestions?

Thanks!
[Android General] KainXSS:
has anyone been able to build the kernel for this device yet?
[Android General] ChaosLord88:
Got a microSD card problem on this tablet. When I insert the card (which i formated and it WORKS on other devices), tablet shows "checking for errors" notification which then disappears after couple of seconds and the card seems like mounted/recognized but under "storage" it says "total" 0.00B! Anyone had an issue like this?
[Android General] charlestek:
I would tell you to put it in a windows pc and run chkdsk, but if there is corruption, it may create "found" blocks, screwing up what's on there.

If you can copy the contents to internal memory, then play with trying to fix the card it would be the best route. In fact, if you copied off the contents, formatted the card and recopied the contents back onto the card, that would be one method.

I'm sure there are some Android apps for checking a SD card integrity, though I don't know if they would require the tablet being rooted.
[Android General] Nodevski:
Tablet completely dead and revived it

I don't know if it's been posted yet but these are the steps I used to revive a dead tablet:

I was sychronising a 64GB sd card between tablet and linux PC and it took ages because some big files had to be synced. The tab was connected to a charger while syncing, so the battery was not dead. I restarted the tab, and then ran syncthing again, and all of a sudden the tab shut down and I was not able to turn it back on by long pressing the power button several times. I noticed the tab had become heated, probably because syncthing hogged the CPU.

I found the fix here: http://www.ifixit.com/Answers/View/169073/Why+won't+my+Lenovo+tablet+turn+back+on

1. Take off the back cover, it is simply clipped on and quite easy to remove with your fingernails.

2. There is a small metal cover with two mini screws over the flat cable that connects the battery to the mainboard. Take out the screws and metal cover.

3. Unplug the connector of the flat cable with a pair of tweezers, and leave it unconnected for a minute or so.

4. Reconnect the flat cable, reattach the screws and metal cover, and clip on the back. The tab should power on now.
[Android General] nannycrick:
Hi guys. Back again as I've recently bought a Lenovo Tab10 TB-X103F. A Walmart issue. After the tragic death of my beloved Tab2, I have been missing that beautiful display. Traded a refurbished Acer netbook for the Tab10 and starting looking for root info. Found a discussion right here on XDA. Here's the link in case anyone is shopping here. It has stable root, TWRP recovery, and even a couple of stable Nougot flavored roms.

https://xdaforums.com/general/help/req-walmart-black-friday-tablet-lenovo-t3508508

Just a side note to everyone who worked to develop the Tab2....Thank you! Love, prayers and all my best!
[Android General] Tzul:
There's an official Android 6 OTA update for the Tab 2 A10-70F! :victory:

I haven't installed it yet, but I'm going to.
[Android General] Johnny Storm:
Downloading for me too. I am away from home at the moment so not planning to install until I get back
[Android General] Tzul:
The Tab 2 A10-70L got an update, too!

I've uploaded them to my AndroidFileHost:

A10-70F_S000216_170601_ROW

A10-70L_S000214_170606_ROW

Note: these are the OTA update zip files. To be installed via recovery (TWRP works), not via SPFT.

If you want to root the new Android 6 firmware, then you should know that the SuperSU installer fails because it cannot decompress the ramdisk of the boot image.

I made a modified boot image that is "SuperSU ready".

Lenovo Tab 2 A10-70F, S000216_170601

Lenovo Tab 2 A10-70L, S000214_170606

Unzip, flash the contained img file first, then install the latest SuperSU zip. My old TWRP 3.0.0 still works, but it has no support for encrypted data partitions and adopted storage. Maybe I'll try to build a new one if I find the time.
[Android General] mjsharon:
Thanks Tzul. I get an error message saying the scatter file is invalid. Trying to install on the 70F.
[Android General] Tzul:
[MENTION=4857436]mjsharon[/MENTION] Sounds like you're trying to install the update zip with the SPFT? That won't work. They're OTA (over-the-air) updates, intended to be installed via recovery.

If it's a zip file and contains a "META-INF" folder, then it's probably meant for the recovery. ;)
[Android General] cha0zine:
Device is performing much smoother with Marshmallow. Good job Lenovo.
[Android General] lion567:
[MENTION=5919159]Tzul[/MENTION], do you have any ideas what is /sig/recovery.sig for in A10-70L_S000214_170606_ROW_WCFEE7F639.zip ? I don't find recovery.img in OTA archive and recovery.sig doesn't mentioned in updater script ... :confused:

Does TWRP survives after flashing OTA?
[Android General] Tzul:
[MENTION=5469284]lion567[/MENTION] It's the signature for the recovery, but it's useless, because as usual, the recovery is automatically built from the boot image by /system/bin/install-recovery.sh each time Android boots. That script also applies the recovery signature from /system/etc/recovery.sig then.

If you use TWRP to flash the update, then yes, it should survive, because TWRP will disable the install-recovery.sh script by renaming /system/recovery-from-boot.p to recovery-from-boot.bak.

By the way, I've discovered that the new vold (Volume Daemon - as in storage volumes, not audio volume) apparently includes NTFS support!

It expects the files ntfs-3g and ntfsfix in /system/bin, which aren't there by default. I placed them there, but unfortunately ntfs-3g fails to mount the "/dev/block/vold/public:179,129" device, which is vold's version of /dev/block/mmcblk1p1, the external SD card.

ntfsfix can successfully check "/dev/block/vold/public:179,129", at least after putting SELinux into permissive mode (setenforce 0).

But "ntfs-3g /dev/block/vold/public:179,129 /sdcard/test" fails with the message "ntfs-3g-mount: mount failed: No such file or directory" (it's not the mountpoint /sdcard/test, that does exist, otherwise the error message would say "failed to access mountpoint").

Maybe someone here has an idea how to fix that. It would be great if NTFS-formatted SD cards could be made working (adopted storage does not suit my use case).
[Android General] runekock:
Interesting. Not that I know much about this, but maybe try putting your mount point somewhere else? /sdcard is a weird emulated fs.