yashsingh1/xdaforums huggingface dataset:
[Android General] Tzul:
[MENTION=492896]CaptainJager[/MENTION] "File is not loaded yet" - you didn't load a file. Click on the appropriate line of the "Location" column to load the file that you want to flash to that partition. ;)
[Android General] theclarkster:
Sorry for the delayed response. Thank you for your explanations. I wouldn't say I'm adamant about Marshmallow. There are no major changes it brings about that make me think I need to have it. The underlying changes to the system are what are most interesting to me.

I use a Nexus 5, and Android M feels to me like what Windows 7 was to Vista. For some reason, Lollipop was always a little troublesome and laggy on that device. Android M, on the other hand, runs much better, has better battery life, and is super smooth.

Battery life isn't really a concern on these tablets, and Lenovo's latest OTA seems to have fixed the problems many were experiencing under the previous versions. Strictly speaking, Android M doesn't really have anything really special that would necessarily improve the performance of this tablet. It's hard to say if battery life and performance would increase without actually using it, but the tablet runs well as is.

The main advantage I see to using a custom ROM based on AOSP would be for security updates. Now that Google has pledged to release monthly security patches, it would be nice to have those available. I understand that under careful use, security compromises are rare and even with known vulnerabilities patched there's still a risk. However, I tend to think that it's better to be safe than sorry!

I believe that, if I'm not mistaken, the source code for these tablets is available on Lenovo's website (http://support.lenovo.com/us/en/products/tablets/a-series/a10-70-2/downloads/ds102789). Just out of curiosity, what does having access to this allow? Like I said in my previous post, I'm not pushing for ROM development and I hope I haven't come across that way. I'm pretty content with the current state of this tablet, and appreciate the work that's been done thus far too allow us to acquire root and have a solid custom recovery!
[Android General] CaptJager:
Thanks Worked perfectly
[Android General] Tzul:
[MENTION=1915411]theclarkster[/MENTION] I didn't chime in until now because I don't really know enough to answer your questions definitively. It is unlikely that the current kernels we have would work unmodified with Android 6. I don't know what would be required to make them work. That source code you can download from Lenovo is the kernel source. They're basically forced to release it, thanks to the GPL. But those sources are probably outdated by now and wouldn't even work for Android 5 in that state, I guess. Lenovo is obligated to release the current kernel sources, I think. Maybe somebody should demand it from them... By the way, I doubt that Lenovo is much involved in writing/maintaining that source, that's probably done by MediaTek, and Lenovo simply adds a bit of branding here and there.

Anyway, that's just the Linux kernel (plus Android modifications). It includes neither the source for the LK bootloader (found one here which might or might not be usable for our tablet), nor the source for Android itself.

If you want to compile those sources, you need to set up a Linux development machine (real or virtual). I have some limited experience with smaller projects, but nothing as big as the kernel. I'd like to try it someday, but I don't have the time for that right now. There are probably some tutorials out there (or here on xda) to get you started, but it's not going to be easy, especially if you have no prior experience with Linux and programming.

As for flashing official updates with a custom recovery: has anybody actually tried that yet? If so, which update with which recovery precisely? Would be interesting to know.

It could work, depending on what exactly the update does, but it's unlikely. Flashable update zips contain the folder META-INF/com/google/android/ in which there are two files: update-binary and update-script. The former is a (compiled) program which executes the instructions given by the latter (and possibly some more).

If the update-binary can be executed by a custom recovery, but some script command fails, we might be able to tweak the script. Or somebody could create a new update zip that works in TWRP and simply installs all the system files that were changed by the official update. Would require some manual work to build, of course.
[Android General] Old faithful:
You also need to make sure, when flashing a custom recovery, that it is actually named "recovery.img" ;)

---------- Post added at 18:05 ---------- Previous post was at 17:13 ----------

Good point. Upgrades are sometimes worth it ;) And sorry if I came across as unpleasant ;)

The fact of the matter is, once you've found a way to make things work, they always come up with new things that invariably break things. For example, I run a super effective widget on my phone called CircleWidget3D Works great on JB. Of course, it's broken on Lollipop. Several others that used to work now crash or otherwise cause errors. Very frustrating, hunting for new solutions and getting used to new impediments.

But ... the redeeming thing is, at least it's an android and like you say, a lot of the code is open source, so it's well worth the effort :) But I can sure understand the allure of iProducts for the 'mere mortal' who doesn't care and prefers to follow and obey: it's easier. None of this fighting windmills nonsense :D

I have had several computers, from Windows 3.1 to 7. I have never, ever been protected from harm by the OS but by being proactive, which means, NEVER trust anyone or any single company, especially those who claim they'll protect you. You need to do it yourself by being smart and prudent. That always works. On the other hand, the increased, forced security has caused more hassles and a significant increase in workload over the past decades that is orders of magnitude worse than anything that ever happened, virus, malware or even worse, because it's accepted as a norm, the relentless, pernicious adware! So excuse me if I simply refuse to trust Google to 'protect' my data ;)

Don't be a sheep, stop believing the wolf!

And by the way, just a small tip, you should firewall "Lenovo User Experience" ;)
[Android General] loner.:
[MENTION=5919159]Tzul[/MENTION]

I have the 10-70F. I know now that I flashed the wrong lk.bin and preloader.bin. The ones I flashed were for the 10-70L

---------- Post added at 02:07 PM ---------- Previous post was at 01:55 PM ----------

When I connect the tablet to be the PC the device manager reads

MediaTek Preloader USB VCOM (Android) (Com 3)

Off and on again in the connect loop.
[Android General] Tzul:
[MENTION=5142831]loner.[/MENTION]

Then you should try to flash the correct A10-70F preloader. Load a proper scatter file in the SPFT, load the proper preloader.bin for the preloader partition, uncheck all other partitions, click the Download button, then press and hold the volume-up key on the tablet before you connect the USB cable. Keep the volume-up button pressed at least until the SPFT shows activity.

I'm not 100% sure it'll work like this, because luckily I've never had to restore a preloader myself so far, but I know that it can be done.
[Android General] loner.:
I think I have the proper scatter file, but could you point me to it so there is no doubt?
[Android General] bigrammy:
He will need to flash it as a "Firmware Upgrade" in SPFlashtool which will require all items to be checked so he will need the full A10-70F ROM.
[Android General] Tzul:
[MENTION=5142831]loner.[/MENTION] There's a scatter file in this TWRP 3 zip, for example. And here's my collection of preloaders and bootloaders for A10-70F. I'd try "preloader_hq8752_tb_b2b_l (20150907).bin", that's the one that had been preinstalled on my tablet.

[MENTION=3924647]bigrammy[/MENTION] The full firmware? Well, then loner is going to need only this: A10-70F_S000121_151222_ROW
[Android General] Old faithful:
Yeah, almost fell into the trap myself, but wasn't my suggestion removing the back panel and removing the battery reasonable?
[Android General] bigrammy:
If that Firmware .zip contains all the .img's and .bin files shown checked in this image then yes. If it's a "recovery" flashable Firmware then No.
[Android General] loner.:
I tried flashing them one at a time and separately with volume up and this is what I got.

View attachment 3715451View attachment 3715452
[Android General] Tzul:
[MENTION=3924647]bigrammy[/MENTION] Yes, that's a full SPFT firmware package for the Tab 2 A10-70F I created from the latest official update and my own backup (because the official updates don't contain all partitions).

[MENTION=5142831]loner.[/MENTION] Don't try one at a time. Use the "Firmware Upgrade" mode, which will force you to flash all partitions.
[Android General] bigrammy:
That should work then :good:

Just for the curious I removed the back of my A10-70F a few days ago to see if Lenovo left in the Sim Tray attachment point on the Wifi version. Sadly they have used another board with the sim part missing. :rolleyes:

See Attached image.
[Android General] loner.:
Sorry but it will not go into "Firmware Upgrade" mode.

I think I got something going though, i think I got it to format.

I put SPFT on "Firmware Upgrade". Notice that the bar on the bottom of the page went from red (fail) to green format 100%

then the flash tools error box appeared.

What next lol.View attachment 3715470
[Android General] loner.:
Lot of caffeine and some rock. Smoke over water, crazy train, sweet home Alabama
[Android General] loner.:
Yea!

Flashed the preloader and lk.View attachment 3715480
[Android General] loner.:
What now? Charge it up before I try more?
[Android General] Tzul:
That error message literally tells you that you haven't loaded any/all files for the partitions you have selected for flashing.

As you can see in the last column of the table ("Location"), no file names there...

(The partition image files get automatically loaded by the SPFT when they are in the same folder as the scatter file. Otherwise you need to load them manually, by clicking into the Location column).

Well done! So you didn't need to do a full firmware upgrade flash like bigrammy said? Interesting.

Depends on what the current battery level is. If charging works now (as indicated by the bootloader's battery charging graphics), then you can do that first.
[Android General] Sparkrite:
Come on, we're all dying to know,

Try a reboot.............
[Android General] bigrammy:
Yes you do hence the reason why it started flashing and Formatting. The fact it failed to complete is not a problem as it will have updated the GPT which has allowed him to now flash the correct preloader.
[Android General] Tzul:
No, that is not how it works. Flashing the preloader has nothing to do with the partition table (GPT in this case). Using the "Firmware Upgrade" mode will update/rewrite the partition table, yes, but that was not loner's problem. He flashed an incorrect preloader (and bootloader). His GPT was still fine. The preloader isn't even listed in the GPT, because the preloader resides in the EMMC_BOOT_1 region, whereas the GPT only governs the EMMC_USER region!
[Android General] loner.:
[MENTION=5919159]Tzul[/MENTION]

I need to flash the rest of the ROM but here's my question.

I have the correct scatter file loaded I have the right firmware extracted in the same folder. I think you said the scatter file would pick up the files without being checked but after I select the "download only" when I hit download it tells me to select at least one ROM at least before execution.

What box do I check so it will pick up the rest?
[Android General] bigrammy:
If you still have problems then use the Factory Firmware in this post http://xdaforums.com/showpost.php?p=62449690&postcount=37 the link is in his signature.

It is the KitKat 4.4.4 Firmware but it will at least revive the tablet if you still have problems due to the incomplete flash.

Be sure to use the scatter file in that firmware folder and all files should then load automatically. Again use "Firmware Upgrade" mode in SPFlashtool.

[MENTION=5919159]Tzul[/MENTION]

Bro please dont tell me about how Mediatek works.

I not going to start giving a full detailed explanations you will just have to trust my many years experience with this SoC .

Take it or leave it thats upto you. :rolleyes:
[Android General] Tzul:
[MENTION=5142831]loner.[/MENTION]

Yes, the SPFT will pick up the firmware files. Just click the "Scatter-loading" button, and select the scatter file again to reload it. If the firmware files are in the same folder as the scatter file, and are named properly, they should then get assigned automatically. Otherwise you need to assign them manually, by clicking the Location column.

After flashing, you might boot into the recovery first (doesn't matter if stock recovery or TWRP), and do a factory reset / wipe. Unless you have important data in the userdata partition (internal storage). In that case, you shouldn't flash it with the SPFT either, of course.

[MENTION=3924647]bigrammy[/MENTION] First, I'm not your "bro". Second, yes, I will tell you how Mediatek works. If I said something wrong, I'm all ears. Please, enlighten us. "I not going to start giving a full detailed explanations" - sounds like you want to hide the fact that you don't really know what you're talking about, and that's not even proper English.

PS: there is no "factory firmware" in the post you linked. Only a link to the USB drivers. I already did post a link to a full firmware package before, in case you forgot.
[Android General] loner.:
[MENTION=5919159]Tzul[/MENTION]

OK I reloaded the scatter file and hit the download button and it say I need to load at least one ROM before execution. I did extract the ROM in the same folder but of course it made subdirectorys.
[Android General] Tzul:
[MENTION=5142831]loner.[/MENTION]

See attachment.
[Android General] loner.:
Having the SPFT set to "Download Only"

---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------

@Tzul

Where did you get that scatter file. It's not in anything I downloaded.

Unless it's named "LenovoTab2A10-70_Android5_scatter.txt" that's what I have.

---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------

@Tzul

My scatter file will not load the file paths.
[Android General] Tzul:
[MENTION=5142831]loner.[/MENTION] It's the scatter file of the full A10-70F firmware I linked. It should be identical to your "LenovoTab2A10-70_Android5_scatter.txt". The name of the scatter file doesn't really matter, but its path does. Like I said before, the firmware files (lk.bin, boot.img, recovery.img, etc.) must be in the same folder as the scatter file, otherwise the SPFT won't pick them up automatically. But even if it doesn't, just assign the files manually in the SPFT, by clicking the lines of the "Location" column.
[Android General] loner.:
Ah I see. I hoped it would. The I need to unload all the subdirectorys in the same dir or remember the unzip command then. That explains a lot.

---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------

I have been unzipping with the file structure intact.

---------- Post added at 06:02 PM ---------- Previous post was at 05:49 PM ----------

Cripes,

I am going to try finding the files in the subdirectorys and manually load them.
[Android General] Tzul:
[MENTION=5142831]loner.[/MENTION] I don't know where those subdirectories you speak of are coming from. The firmware archive I linked contains exactly one directory, which contains the scatter file and all firmware files, as shown on my screenshot. No subdirectories.
[Android General] zMILWAUKEE:
Try re-extracting the firmware, making sure the scatter and all files are all in the same folder, it sounds like spft can't find the necessary files that coincide with the scatter file. Just right click on the firmware zip folder, extract, and extract them all to the desktop. When you load the scatter file, make sure it's the one you just extracted to the desktop, spft should then pick up the rest of the files. Oh and are you running spft as administrator. That just might be the issue to, I know it's a small thing, but makes a huge difference, and now that you can flash with spft why would you do a firmware upgrade, it should only be set to download only if your just putting the stock 4.4 or 5.0 from the first page of this thread. I think you should listen to Tzul more than the rest, he has been on this thread since the start and not once has given bad info or wrong advice. Some people are making this harder than it needs to be. Good luck buddy.
[Android General] loner.:
Do you use Windows? Every compression software I use the file has 3 subdirectorys with more subdirectorys.
[Android General] zMILWAUKEE:
On Windows you shouldn't be getting any subdirectories, when you extract the firmware all you have to do is right click on the downloaded file, there should be an extract option in the menu that pops up after you right click, click extract, then choose the destination, I.e. desktop, it will then extract the files to the desktop.you don't need to "run" a compression program just to extract the files to the desktop. Next go to spft, run as administrator, choose scatter loading, then browse to the extracted scatter file you put on desktop. Spft will pick up the rest.
[Android General] loner.:
I wish it was that easy, there are a lot of directory's to do.

---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------

If anyone has the stock ROM that would extract in one directory in Windows, I want it.
[Android General] Tzul:
[MENTION=5142831]loner.[/MENTION] Yes, I do use Windows. And the free 7-Zip archiver. You can also use WinRAR or other programs that are able to unpack 7z archives. Here's proof that the archive contains just a single directory, with all the firmware files in it:
[Android General] loner.:
Well fellas thanks for all the help, but this tablet seems to be DOA.

It will not turn on, attempt to boot or anything, it doesn't even seem to take a charge. Even though I seem to have got it formated and reflashed the files I had wrong it as unresponsive as my ex got to be at the end. I hit the power button and get nothing.

---------- Post added at 10:20 PM ---------- Previous post was at 09:33 PM ----------

@Tzul

OK, I see. I think someone told me that the lollipop file was a complete ROM but you have to do the kit Kat ROM first.

It's flashing now.
[Android General] bigrammy:
Maybe you find it on your own but I did link the wrong post with the KK "Factory Firmware" it's here. http://xdaforums.com/showpost.php?p=62511857&postcount=42 :o

Direct Download Here: KK Factory Firmware Download Here It's a .RAR file which you will need "Winrar" or other compatable program to extract it. http://www.rarlab.com/download.htm If you have problems extracting it.

Sorry I was/am rushing a little but have to go to work now after very little sleep. :eek:

I am 99.9% sure that firmware will revive the tablet when flashed as one package in "Firmware Upgrade" mode.

---------- Post added at 05:16 AM ---------- Previous post was at 05:02 AM ----------

Whatever......

Good luck flashing the preloader at will then but I am pretty sure it will ask you to "Download All" if there is a mismatch of the preloader and pgtp. But hey what do I know :laugh:
[Android General] loner.:
Finally the tablet is up and running really well.

Thank everyone.
[Android General] Tzul:
It is a complete ROM, and you didn't have to do Kitkat first.

There cannot be a "mismatch between preloader and GPT", for the reason I explained. Go ahead, open the GPT in a hex editor and show me where it references the preloader. Or at least tell me a working theory what these two parts have to do with each other. On older MediaTek platforms, which didn't use GPT but PMT, the preloader actually did contain a list of all partitions. But our preloader does not.

If there's a mismatch between scatter file and partition table, that's easy enough to recognize, because the SPFT will show a specific error message.

But this was not the case here. The GPT didn't even change from Kitkat to Lollipop on this tablet, it stayed exactly identical. Again: the GPT was never the problem here. The problem was that an incorrect preloader was flashed. That's what error 5054 in the Flash Tool means.
[Android General] clsA:
That's great news

The last 3 pages we an interesting and informative read. Thanks
[Android General] Sparkrite:
Couldn't have put it better myself, VERY interesting and informative indeed. :good:
[Android General] loner.:
I never brought on back that was as dead as this one before, but the it really seems like a better device now.
[Android General] dallev79:
My dad recieved his tablet today. I'll be taking a look at it for the weekend.

1. So if it is on KitKat, then root and after that update?

2. If is already is on lollipop, what then?

3. These updates that you have on the German site. Are these OTA:s? Or must I root and manually update?
[Android General] Old faithful:
No, unless you want to risk a brick ;)... It's the other way around. In short, update to whatever OS you prefer and only then root and install a custom recovery. Of course, you can technically deviate from that... If you know what you're doing. Read up on Tzul's posts to learn more.

Both KitKat and Lollipop OEM ROMs work well. That tablet is essentially bloat free and was designed to do actual work and works very well with limited tweaking compared to many other devices.

Basic differences in my experience:

- KitKat: more apps will work on it especially if you're used to some older ones, Lollipop will break some.

- Lollipop has better photo image realism, colors look more true to life and it would seem some of the earlier bugs that came with Lollipop have been resolved. OTOH, you'll have to deal with excessively bright 'Material' Design, unless you can dig up apps that have dark themes. The screen on that tablet is VERY bright!!!

Read up on the first post, it's got the links to most of what you're looking for. Or look up for Tzul's posts in this thread, he's got a full repository of files. Just make sure not to confuse the Tab 2 A10-70F and its LTE variant the Tab 2 A10-70L. Also, as you may have learned reading the posts of the last few days, DON'T mix major version elements when flashing: If you decide to go to Lollipop, flash the whole ROM first using SPFT. Stay within generations of ROMs and by all means stay within hardware types, the F and L don't mix well (abstain unless you really know what you're doing)

Oh and rooting is the probably the simplest procedure you will be doing after updating your OS. Installing the TWRP recovery for your ROM version is actually all that's needed now to root as the option is already built in thanks to Tzul's generous work.

If you're looking for some basic info I've written a basic but pretty detailed step-by step flashing guide that I've uploaded here.
[Android General] gtallmadge:
Old faithful,

Read your Taking ownership tutorial and have a few comments to make as per your request.." do feel free to comment, criticize and to correct me if I'm wrong, it will only help me improve it, my goal is to hopefully help the community."

Many of the technical suggestions are on spot and hope you will continue to refine and expand the tutorial. However, you are probably preaching to the choir here so the need for the polemics is unnecessary and may be off putting to many neophytes that are just looking for answers to their questions. The community might be better served with warnings about malware, trojans or viruses instead of political or social statements.
[Android General] Old faithful:
Well understood, I'll admit you're not the first one to cringe at my political digressions, it needs to be pared down anyway, thanks for your critique.