yashsingh1/xdaforums huggingface dataset:
[Android General] Old faithful:
While you're around, [MENTION=5919159]Tzul[/MENTION], I was wondering if you've ever experience stuttering/crackling bluetooth audio with this tablet? (The WiFi issues I used to experience OTOH seem to be caused by my old router - it takes forever to 'see' WiFi coming out from my home router, it's fine elsewhere). I've posted on the Lenovo forums here, but no response ;)
[Android General] adrian1216:
[MENTION=5919159]Tzul[/MENTION] I' ve creadted sample video in blender. Still does not work. I reduced birate of video. Please tell me what is still wrong in video? https://drive.google.com/file/d/0B12fvnyyrVj4X0t6WTl0QnNZWlk/view?usp=sharing
[Android General] charlestek:
My bad, apparently on WinDoze, you can only address 32GB with FAT 32, but the actual number bits in the address permit addressing 2TB. As far as whether the tab 2 in

Kitkat (works according you, I think you are using KitKat) can read a 64GB formatted flashdrive, it would make sense that a special utility might make the mbr readable by android kitkat. As far as what Tzul says, I will let you and he fight it out :)
[Android General] Tzul:
[MENTION=1454767]Old faithful[/MENTION] I have played some music for a few hours over Bluetooth, and never noticed any stuttering or crackling. But I think I noticed a few instances where the music appeared to skip a beat, as if some data was dropped. But all in all the Bluetooth playback on Lollipop was fine.

[MENTION=7114808]adrian1216[/MENTION] That video works as bootanimation on my tablet. It gets stretched, though. The tablet's screen is 1920x1200 pixels, which is an aspect ratio of 16:10. Your video is 1200x900, which is 4:3. Lenovos original start.mp4 gets stretched, too, but it's hardly noticeable, from 16:9 to 16:10 isn't a big change.

I simply copied your file to /system/media/start.mp4, and made sure it had the right owner (root) and permissions (644). Then I rebooted and it played.
[Android General] adrian1216:
You've just replaced start.mp4 using some kind of root manager?
[Android General] Tzul:
The default tools in Windows allow you to format SD cards with FAT32 only up to 32GB. But that is just an artificial limitation; like you said, FAT32 is perfectly capable of more (and Windows can address/read larger formats just fine). There's nothing special about the MBR or anything like that. The hardware in the tablet supports SD v3 (SDXC), so it is physically able to address 64 GB and more. It's the missing software support for other file systems in Android that's the problem. But Android supports FAT32, and up to 2TB or whatever the limit was.

Yes, a file manager with root access.
[Android General] BoredDude:
Hey there, quick question, installing twrp wipes data or I can do all the bootloader and twrp stuff and keep all my stuff?

Enviado desde mi MotoG3 mediante Tapatalk
[Android General] Tzul:
[MENTION=5352019]BoredDude[/MENTION] Installing TWRP will overwrite your current recovery partition, and installing a new bootloader will overwrite the old one. That won't affect your Android data, because it's in another partition. But just to be on the safe side, you should make backups of everything anyway.
[Android General] nannycrick:
For formatting SD cards I use the MiniTool Partition Wizard for Windows. I has all the utilities to correctly reformat, and partition an SD card.

Check it out....

http://www.partitionwizard.com
[Android General] ronaldo9_r9:
Hello Guys,

I am long time android user and rooting is first thing i do on any of devices i owned wheter its Htc desire, S2,S3, S4, Note 4 or Galaxy tab note 2014 edition. Now i am getting tab 2 A10-70, it seems like rooting is lot harder then any other device i had.

Is OP up to date? I searched google and xda it seems like there are no custom roms for this tablet. I am actually worried that rooting might brick my device.
[Android General] charlestek:
[MENTION=2601258]ronaldo9_r9[/MENTION]

Read the very first page of this thread. There are instructions on how to install TWRP using Mediatek SPFT. The install includes rooting software. I understand that there are now ? two different editions of TWRP now. The first was made by Tzul.

Maybe Tzul can clarify the versions.

Otherwise, once you get the Tab2, it will either come with Kitkat or Lollipop and there are incremental updates for either from Lenovo. If it comes with Kitkat, you can also update it to Lollipop.

I would install all the updates before installing the TWRP/Rooting package.
[Android General] Old faithful:
Thanks, Man! Maybe it's time I gave Lollipop another chance ;)

---------- Post added at 00:59 ---------- Previous post was at 00:53 ----------

Hey, I wasn't aware of that, as Lenovo states 64GB as the maximum... This means one could move on to a 128GB card or more at some point?

---------- Post added at 01:17 ---------- Previous post was at 00:59 ----------

I beg to differ... I've had several phones/phablets and this tablet is a no-brainer to root... The main trouble spots to watch for on this tablet are to make sure NOT to format when flashing using SPFT (will permanently delete unique identifiers stored in NVRAM, although the data is also stored somewhere else - read Tzul's previous posts), and to install the proper drivers for successful flashing. The rest is a piece of cake, just use the stuff that's linked to in the OP and you'll be set.

BUT you're right, there are NO custom ROMs... OTOH, the tablet as very little bloatware or malware and is very easy to take full ownership of.

The only way you could really brick the tablet is if you loaded a ROM designed for a completely different device ;)
[Android General] ronaldo9_r9:
Thanks guys for pointing me to the right direction.

My tablet should be here in few days. It may come with Kitkat i hoping it is because i have read lollipop is not stable at all. I might not upgrade to lollipop due to wifi issue and sound issues.

Another thing is i have windows 7 that has drivers for note 4, S4 and note 4 tab. If i root the device do i have to uninstall other drivers?
[Android General] Tzul:
Yes, 128GB cards work, I've heard from people who use them in this tablet. 200GB cards already exist and should work, too.

Don't believe everything you read. ;)

The latest Lollipop firmware for this tablet is stable. At least for me and other people.

No, those drivers shouldn't interfere with eachother, and they have no direct impact on rooting.
[Android General] Old faithful:
Main differences are small and mostly aesthetic IMO. Some older apps may not work on Lollipop. Some small bugs have been corrected from KitKat, photo display in particular is vastly improved, IMO. But you may not like 'material' design and its excessive whiteness. Honestly, I haven't noticed any differences on WiFi but in my experience the tablet isn't as sensitive to WiFi signal as my Galaxy Note 2, same whether on KitKat or Lollipop but that could also be due to my old DIR-615 router, seems to take forever just to connect to it.
[Android General] vinnycolletti:
Tzul: Just wanted to say thanks for putting the thumbs up for Lollipop out there. I just got my Tab 2 A10-70. You convinced me it was safe and the upgrade was fine after factory reset from recovery. Hoping the good folks here will provide an upgrade to 6.0. I'm a dunce but was able to get 2 Nook HD+ to 6.01 through Cyanogen mods so I have hope
[Android General] nannycrick:
I just got done upgrading to Lollipop. The return to stock, upgrading to Lollipop, and flashing that Update.zip all went smoothly. SPFT loaded & flashed with no problems. That was the first time I flashed anything with SPFT! When I initially rooted, I used Kingroot, then converted to SuperSU. A new experience & good lesson learned. I think I'm gonna try saving that RCA Pro II now.....again!

Thanks again for assembling such a good, well written OP with all the resources we need for this baby!

Beers for everyone..... Or at least those who are "of age"!

??????
[Android General] alireza40ir:
Hello , friends

As I updated to latest version of lollipop, the tablet work fast, stable , without any lags and not seen any bugs .

But;

Aftrr installing the a Twrp ver 3.0 and root it and install xpose , it take many times to boot , after modify some apps and integrate updates , the tablet stuck on boot logo and never came up.

Has to flash stock rom.
[Android General] nannycrick:
Charlestek....I want to thank you for encouraging me to explore that RCA Viking Pro forum for help with my Pro II tablet. A great dev, Smartmanvartan uploaded firmware for the Surf1000. We believed it's the same as the rct6203, just a marketed under a different name. The firmware ran and flashed Lollipop 5.0.1 to it. It BOOTS! OMG! It's running after six months of being dead! Thanks tons!

A round for everyone! ?????????
[Android General] Tzul:
[MENTION=7361217]vinnycolletti[/MENTION] I used to have a Nook HD+, too. Great tablet, and it's still well supported by developers. But it started showing its age and felt too slow for me after a few years.

[MENTION=4717484]nannycrick[/MENTION] Well done! That reminds me, I found a signed version of the MediaTek drivers (Preloader USB VCOM, and a few others). That should make it even easier for people to get the SPFT to work. Download here, instructions in included readme.
[Android General] nannycrick:
I finally got SPFT to run. The Win10 x86 driver you posted a link for works perfectly! Thanks! Got the Tab2 upgraded to Lollipop as per your helpful instructions. Got that hard bricked rct6203w46 flash end and running Lollipop 5.0.1. Giving that one to my youngest son. SPFT working like a charm! Thanks again! Now I have three working tablets.

(I still have my old n9106v as my spare!)
[Android General] Old faithful:
You can only install updates from stock recovery with the tablet unrooted...

You can unroot from the SuperSU application, installing stock recovery usually requires flashing using SPFT.

At this point it may simply be wiser to reflash the OEM ROM, apply updates and be done with it. Then and only then should you root, install TWRP and Xposed.
[Android General] alireza40ir:
Dear friend,

My mean was;

after installing Twrp and Root and install xposed and a little rooty jobs , the tablet doesnot boot any more and i had to flash Stock Rom.

And it was taking long time for boots.

I dont know why , for mentioned problems.
[Android General] ronaldo9_r9:
Guys finally got my tab 2. Installed lollipop 5.0.1. I thought i followed first post to the letter T, it took me few hours for sp tool to recognise the tab. I installed the correct drivers but nothing was flashed using sp tool on win 7, i then booted to windows 10 but same result. After few hours unistalling and installing driver i almost gave up. I decided to read op carefully going through each link then came across where it says install the latest sp tool. The link took me to the page again i choose v5 at top where v3 finishes first time but this time i scroll slightly below and it said latest v5. Loaded the files again and green message came that tab has recovery installed.

I cannot believe i made one silly mistake of not installing latest sp tool version it cost me few hours lol. I learned my lesson now.

Okay now i am rooted what now on this tab. On my note 4 i have viper4android installed will that work here? Also whats the latest supersu version you have?

I am going to restore few apps via titanium excluding data.

Any good apps or games you recommend for this tab. I dont know how games like ashphat or nova 3 will run on this.

Again guys thanks for your help and encouragement to root this device.
[Android General] fastliving:
recovery shows in chinese

hi there, as a noobie i´m not shure what i did wron, but i followed all the steps and everything work´s fine until i saw the recovery menu, it´s in chinese and i dond understand a thing in that language.i´m sorry to bother with something silly like this but i don´t know how to continue. sorry for my bad english, i´m spanish. regards and thank´s in advanced.
[Android General] nannycrick:
Okay...difficulty with Lollipop upgrade. Your version includes a scatter for the MTK6752 not the 8127 chips that the Tab2 has. It loads okay but I can't get into my Google account. Is it because it's now device is "miss identified" by Google's server? I can't go back to the authorized version of KitKat now. I have no ideas on what to do from here. I can't update / download ANYTHING. Your KitKat version also has a MTK6752 scatter. Not correct scatter for an mtk8127 device? Here in the US, if any device is miss identified, Google's US server will not allow connection. Your Lollipop runs but I'm locked out of my account.

Any ideas here?
[Android General] Tzul:
[MENTION=1367800]fastliving[/MENTION] Could you show a picture of that "Chinese recovery"? Some MediaTek devices have a Chinese factory menu, but the Tab 2 A10-70 does not. I don't know what menu you could be seeing.

[MENTION=4717484]nannycrick[/MENTION] The Tab 2 A10-70F has an MT8165, the A10-70L has an MT8732(T). Don't read too much into those numbers, the chips are almost identical (except for LTE support) and belong to the "MT6752" family. So, the scatter file you have is probably correct.

The smaller Tab 2 A7-10 has an MT8127...
[Android General] nannycrick:
I still am not allowed to connect to Google's server. No email, no calendar, no app updates. Flash a signed GAPPS package maybe?

---------- Post added at 01:51 PM ---------- Previous post was at 01:45 PM ----------

Just edited the build prop ...Default region..UnitedStates/WashingtonDC. That worked for my old n9106v. It was a European clone stuck on UK/London as a default. I changed the build prop, rebooted and it connected. Keeping fingers crossed.. I'm reading the current build prop. Not the menu in Settings>About Tablet.

My Lenovo ID login doesn't work either.
[Android General] Tzul:
[MENTION=4717484]nannycrick[/MENTION] Just to be sure, we are talking about your Tab 2 A10-70F, right? What firmware package did you install exactly?

There is no "London" in my tablet's build.prop. The time zone is set to "Asia/Shanghai", but that's just the initial configuration before your change it in Android's settings. It doesn't need to be changed in build.prop, nor should it affect Google logins.
[Android General] nannycrick:
It's my beloved Tab2. Google login service not working. LenovoID not working.
[Android General] Tzul:
[MENTION=4717484]nannycrick[/MENTION] What firmware package did you install?

If "UK/London" was in your build.prop, you might have installed a wrong one.

You could try my S000121 release for SPFT (careful, it'll wipe all files in your internal memory, so back them up beforehand, if necessary).
[Android General] nannycrick:
Trying fresh downloads of stock Lollipop. Including the one from your repository. Thanks.
[Android General] nannycrick:
The example from post 619 was just an example. I'm downloading that version in your repository.

Question....to flash this one in SPFT, unchecked preloader correct? Same instructions from the OP?

---------- Post added at 04:29 PM ---------- Previous post was at 04:10 PM ----------

What I meant from post 616...the build prop in the Lollipop stock ROM downloaded from Android File Host says Asia/Shanghai. Google's US server have trouble with allowing foreign devices to connect. Those restrictions are setup by our "beloved" FCC (Federal Communication Commission). They govern & permit what devices are allowed to run on our network. Sometimes just setting the date & time appropriate for your current location won't work. Example...my rca 6203. Fresh install of firmware from it's related device.. the Surf1000. The build prop in it says Africa. I couldn't login to Google's server here in the US. I changed the default location to US, rebooted, and it worked. Same thing with the old n9106v, a China knockoff bought in London, and brought here on a plane by the user, not imported here. Not an "approved" device.

That build prop trick didn't work for my Tab2. It's probably Google's US servers with their security restrictions. Go figure!

I'll try that other Lollipop, and let you know.

---------- Post added at 05:42 PM ---------- Previous post was at 05:29 PM ----------

Example....right now I'm logged in to XDA's server using an alternate browser, but my Google login service isn't working. Internet bandwidth at our local McDonald's is very good. Everything works BUT Google Login Service.

Sent by my Tab2.
[Android General] Tzul:
Correct. But in this case, you can also flash the preloader once, because your tablet is most likely still running the old "Kitkat" one.

Again, that's the initial "factory reset" timezone. It should not have any effect on Google services!

This tablet is FCC and CE certified, and ROW are international firmwares. You don't need to edit build.prop or anything else on the system partition for Google services to work.

I can't explain the cause of your login troubles (Google server problem? Was your account compromised? Did you have encryption or some advanced security settings enabled?). But the "persist.sys.timezone" value is definitely not it!
[Android General] nannycrick:
FIXED! Downloaded Minimal GAPPS signed package for 5.0. Reboot to twrp recovery. Wipe dalvik & cache, flash zip. Reboot, sign in with Google. Everything syncing! Nice!

Don't know why login service.apk wasn't working as it should. But it works now. Making another nandroid backup now.
[Android General] nannycrick:
Has anyone asked the question.... Are we going to get Marshmallow 6.0 like the Tab3?

And can we get our hands on the source code, and firmware so we can upgrade. Just wondering...
[Android General] Tzul:
[MENTION=4717484]nannycrick[/MENTION] The Tab 2 won't even get Android 5.1, let alone 6. At least not officially.

The Linux kernel source is available as usual, but it's outdated and might not even be in working order. But MediaTek's Android source code is closed.
[Android General] nannycrick:
It was just a small hope!
[Android General] loner.:
I would like to see a custom 5.1 ROM for this device. I have 6.0 on another device and I'm not impressed.

It seems like a lot of people want to see a custom ROM for the lenovo tab 2 a10, but so far no one has put together one. I have read that support for custom Roms has dramatically declined and if it remains this way "buyers may have to settle for what ever company's put on a device". This is very sad indeed, but the overall demand for new devices will decline more. I doubt consumers will buy newer devices just to get updated firmware, if that is what corporations are thinking.
[Android General] nannycrick:
I agree with loner. In some devices, a custom ROM is necessary to fix issues that tired, under paid company devs aren't allowed time to. Manufacturers tend to rush product to market too soon!

I had the Motorola Triumph at one time. The rom was written so poorly that it barely connected at all....and that's right out of the box! Rooting it, loading a Miui ported ROM, and editing parts of the GPS library, was the only way to get full function out of it! You guys aren't hackers, you're necessary technicians!

I would love to see 5.1 in this tablet! It's capable of so much more than it does now!

And as a note.....smartmanvartan from the RCA Viking Pro forum found original 4.4.2 firmware for my rct6203w46 and a beautiful fully functional 5.0.1 ROM too! I've been spreading the word to my fellow crashed rct6203 owners. They can now unbrick & love life again! Thanks for your help Tzul & Charlestek!
[Android General] worm9110:
I too wish there was a customer ROM for this or something like clsA put together at http://xdaforums.com/showpost.php?p=64546198&postcount=3.
[Android General] bman2010:
I agree a custom ROM would be great. I would like to see just a few features builtin, but nothing major.

-Clear ALL Recent Button

-Advanced Power Off menu ( Reboot, Reboot Recovery etc.)

-louder sound modification

Maybe some skilled developer could do this if we supplied a simple list of features desired.

- ALL modification
[Android General] sic0048:
EDIT - I found these instructions on how to fix the "failure to mount" issue I was having. http://xdaforums.com/showthread.php?t=1949372 I followed those instructions and removed and recreated the system partition. I was able to mount the partition after that.

However when I tried to flash the latest OTA image using the SP Flash tool, I still have issues. The flash seems to work and it shows the green check mark after it flashes, but the tablet won't boot any farther past the initial boot screen. It also creates a situation where the system partition cannot be mounted in twrp again, so I have to go through the process of removing and recreating the partition using the above instructions.

So I am at a loss as to what to do next. Any assistance would be greatly appreciated.

-------------------------------Original Post --------------------------------------------

Ok. I need some help. I've installed twrp on my a10-70 (latest 5.0.1 OTA) and attempted to flash the XPOSED framework. However I didn't realize how little storage space was left on the device and the installation failed during the middle of it. Now the tablet will boot only to the point of showing the "Lenovo - powered by Android" splash screen (however it doesn't appear to be a boot looping).

I can still boot into twrp and it appears the ultimate problem is that I cannot mount the system partition. Anytime I try to flash a recovery, etc I get a "cannot mount system" error. This Also makes sense as to why the boot process never gets farther than the splash screen.

Any advice on how I can fix my system partition so that it mounts again?

Thanks!
[Android General] Tzul:
[MENTION=2688390]sic0048[/MENTION] Not enough space on the system partition? What have you done to achieve that?

There is an xposed-uninstaller-*.zip to be flashed that will remove the Xposed framework. But if your system partition can't be mounted, then that will be useless.

You can always reflash the stock system partition image (e.g. contained in this file), either via SPFT or TWRP.

Afterwards, you can delete the /system/appjar directory and all files in it (Lenovo's preinstalled apps, most of which don't even get activated on your tablet, because they're for different countries). That'll free around 300 MB on the system partition.

---------- Post added at 05:11 PM ---------- Previous post was at 04:58 PM ----------

You can get the first two with Xposed + GravityBox.

The sound is loud enough for me, using these Dolby Atmos settings (enabling "Volume Leveler" will give a small additional boost, and "Outdoor Mode" will enable the third loudspeaker on the back of the tablet, but it doesn't make a big difference). You can also go into the Engineer Mode app and set the maximum volume for various modes to the maximum value (160).
[Android General] Tzul:
OTA updates do not contain an image of the system partition that is useable with the SPFT. At least not without a conversion.

Type 1 OTA updates contain "system.new.dat", "system.transfer.list", and "system.patch.dat" (normally empty).

For the SPFT, you need a "system.img". See the file I linked in my previous post.
[Android General] sic0048:
[MENTION=5919159]Tzul[/MENTION] - Sorry for the confusion. That is the file I am using, I just incorrectly called it an OTA file. I downloaded it, unzipped it, and have been attempting to flash the "system.img" file using the Smart Phone Flash tool. That is not working for me. :rolleyes:
[Android General] Tzul:
[MENTION=2688390]sic0048[/MENTION] You have a Tab 2 A10-70F, right?

That system.img is definitely correct, it's directly converted from the official OTA update.

So, if it's not working for you, it either wasn't flashed correctly, or your tablet has other problems.

To test the former, you could flash system.img to the system partition, then do a readback, and compare the read back file with the original; they must be identical.

If all fails, you could try to flash all partitions that are included in the SPFT firmware archive.