yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Nadaaaaa:
I should had red this thread before

So i got my new A10-70F tablet and rooted it fine with kingroot.

Everything worked fine until i noticed when i rebooted with a SD card inside this message would come up every time :Warning Application has been moved completed!

So i thought to upgrade to lolipop and well it got bricked....factory reset does nothing.

So i figured i have to flash it with a factory ROM or something.....tho when i start looking for one it seems there aren't any

There is a chineese and a rusian webside noone of them i was able to download from because the chineese needs to download a plugin and register all in chineese ofc (it also requires a chineese mobile number to register btw) and the rusian it says or that i don't have authorisation or that the file doesn't exist(in rusian ofc)

So i am wondering wtf to do why there is not a Rom for my tablet anywhere in the world why it got bricked so easily and why factory reset doesn't work.

If i couldn't do anything else do you think returning it to them would be hard for them to flash it back to the factory state ?
[Android Q&A, Help & Troubleshooting] evaporic:
Maybe try

http://xdaforums.com/android/develo...secured-boot-img-twrp-2-t3162981/post62407374
[Android Q&A, Help & Troubleshooting] Ondigo:
Friends,

Finally I managed to get the Tab 2 A10-70F factory firmware. Flash it using latest version of SP tools. This is KitKat 4.4 ROM

I added the link in the signature below. Please repost it in as many resources as possible to give everybody an access
[Android Q&A, Help & Troubleshooting] Nadaaaaa:
SP flash tool doesn't seems to work for me

Ondigo thx for the upload dude but SP flash tool just sits there and doing nothing.

The ADB only sees my device when i go to recovery and chose to update using ADB.

Reading the instructions of the SP flash tool ADB should be able to see my device even with power off...i don't have much experience with those things.

But playing around i found out that by pressing the volume up key when the device is off it starts on a menu that has fastboot.

So my question is this:

Can i flash the images that you uploaded manually using the fastboot ?
[Android Q&A, Help & Troubleshooting] Ondigo:
First of all you need to install lenovo drivers from the file SP_Drivers_v2.0 using legacy drivers installation method from device manager. only AFTER THAT Sp TOOLS WILL BE ABLE TO SEE THE TABLET. I posted link to signature
[Android Q&A, Help & Troubleshooting] Nadaaaaa:
It ****ing worked !!!

My tablet is back from the dead.

Thx Ondigo. U r the best.

As for the drivers i installed them all exept the 2 unsigned on the main directory that windows 8 wouldn't let me install but i think the only driver needed is the MediaTec PreLoader USB VCOM located in the CDC folder.
[Android Q&A, Help & Troubleshooting] ikilforfree:
has anyone managed to root with lollipop?

I mean damn I have this tablet I installed lollipop on it and it crashed a bunch had to reset to get it work again til it stopped working within 10 days of being bought. :( my niece has same one I guess hers is less problematic. But still crashes I got a new one with KitKat not one crash yet... Really don't know if lollipop is worth it for me any advice?
[Android Q&A, Help & Troubleshooting] evaporic:
http://xdaforums.com/android/development/lenovo-a10-70-unsecured-boot-img-twrp-2-t3162981
[Android Q&A, Help & Troubleshooting] clsA:
Look closer at my picture, you'll see the preloader and the second trustzone.bin are Unchecked. This is for good reason. The preloader did not change in the lollipop update so their was no need to dump it at all. Just use the old one. The change in the offset did get the preloader closer to the right value (removed some other padding at the beginning of the file). but It was still necessary to trim off some extra at the end of the file. Mine 168 to the needed 138. At any rate it was a waste of time after finding the 2 files were identical after some trimming.

So you see all I did was copy the preloader and MT6752_Android_scatter.txt from the old ROW to the new dumped files.

If you compare all the files in my readback to Tzuls you'll see their are differences in many of the files. File dates for one and some size differences in others. But when you load the 2 recovery files for example in the hex editor it tells you the files are the same but of different size.

my only guess to why is that my readback was made on a 32 gig tablet and his is 16 or we did the readback at different times. I did mine before booting to the new lollipop update and it installs on first bootup. His readback could have been after this last step had already been completed.

Or he could have trimmed his recovery before backup.

If you get the exact file length for the data partitions on your readback please share them here as this is what I'm attempting next. I would like to create a SPFT flashable ROW of a debloated / Rooted / with custom launcher and busybox and xposed ready to flash release.
[Android Q&A, Help & Troubleshooting] Old faithful:
Yeah, I figured that much but why did you create that second trustzone.bin, to see if it would make a difference? (I checked and they are bit by bit identical).

Mine is exactly the same as yours and Tzul's, except for the padding. Same data at the same addresses when taking the offset into account (your's start at hex 800 from SPFlash, and mine has the exact same content stating at address 800, all the way to the end of your file - the rest of mine is filled with FFs and 00s). So it comes to reason that reflashing that 'bloated' file should make no difference. The rest is simply unused space and whatever is in it should be irrelevant. That's why I was wondering why, when you first did it like I did myself, you encountered problems. Surely playing with a preloader is asking for trouble! Just saying.

Understood.

Indeed, I noticed that as well. I'm not at my computer now, but my initial findings were that these files were identical on my extract, except for one and the preloader, presumably because I extracted it

after tweaking the device

, in other words, as a backup.

Agreed... User and system could be different. However recovery should be the same... I'll check after a good night's sleep.

One thing I noticed, the preloaders are different in the KitKat and Lollipop ROMs. But surely recoveries would be identical, we're talking Carliv 5.02, aren't, we?

Considering everything in data is set on to vary in size from one device to another and I did it after tweaking the device, I don't think it'll be of much help... I'll take a look at it when I come back.
[Android Q&A, Help & Troubleshooting] Sparkrite:
Thank you very much Tzul, works well, just two things....................

1) Where is the " Integrated full installation of SuperSU v2.52 for easy rooting" placed in the menu(s), effed if I could find it? ;)

2) I used "rashr" to flash it as I thought it safer than SPFT due to the lack of a scatter file, how would you go about using SPFT, edit an exiting scatter file, pointing the recovery entry to the new TWRP img. and just checking that box ?
[Android Q&A, Help & Troubleshooting] clsA:
I did that just in case their was a difference I wanted both to be sure. but dropped the 2nd one after finding they are the same.

Same as above, after finding the correct Starting location the hex editor tells you the files are the same, so no need to dump it again.

No I was comparing the 2 Stock recovery's. Tzul mentions below he trims his and I didn't

---------- Post added at 04:10 PM ---------- Previous post was at 03:55 PM ----------

That's the exact path I used for the readback. So the only real differences in yours and mine are the trimmed up files in your release.

Their are some minor differences in the 2 stock recovery's we both dumped, if you get time have a look and see if you know why that would happen.

I think I can find out the correct size for the userdata with diskInfo ( at least close enough to do a working backup without all the filler )
[Android Q&A, Help & Troubleshooting] suhridkhan:
For use with SPFT, I used the scatter file included in Corliv recovery, worked without issue.
[Android Q&A, Help & Troubleshooting] Old faithful:
Are you saying that I should then simply start the preloader readback at hex 800, not 0 like I read from the scatter file?

How do you determine the start of padding at the end of the preloader, is there a special character string that identifies the EOF?

Isn't that policy ultimately dangerous, like removing the ability for a computer to have a second hard drive? What if the main hard drive or partition becomes corrupted? You'd have lost everything if you didn't have your data stored on a separate piece of hardware (the external SD card). It actually happened to me and a friend of mine on our Galaxy Note 2, not being able to restore a nandroid backup, precisely because of internal memory corruption, which required reflash by Odin through the PC, 'Factory' reset having failed.

[philosophical rant]

If do find such authoritarian, restrictive policies not only offensive, but also fundamentally flawed and dismally misguided. The emperor is indeed naked.... History has proven time and again that coercion doesn't work, that concentration of power results in disastrous collapse because they are against natural law, which states that we are all interconnected.

Like John Gilmore who once famously said "The Net interprets censorship as damage and routes around it." There are of course numerous other examples all along history, such as the Prohibition, to name one of the most famous ones in our recent past... ;)

[/philosophical rant]

---------- Post added at 23:41 ---------- Previous post was at 23:22 ----------

Well I have tried and the Xposed Framework definitely interferes with WiFi Signal Booster. After installing it, WiFi Signal Booster would simply close right after opening, as in a force close. Trying all the usual remedies: deleting app cache and data, deleting the cache partition and the dalvik cache, the only way I got it to work was after I uninstalled the framework altogether from recovery. Since I was simply looking for a way for the battery percentage to show in the notification bar, I uninstalled the whole thing. Too bad, it had a lot of interesting capabilities.

I emailed the developer of WiFi Signal Booster, hopefully I'll get some answers. As for the Xposed Framework, I did notice very long boot up times whenever I changed anything that required a reboot.

I'll check it some more later, got a few days of intense work coming up, so I'll have stop experimenting with the tablet for a little while. That doesn't mean I won't be around listening and barging in your conversations, hehehe...

---------- Post added at 23:50 ---------- Previous post was at 23:41 ----------

You might want to take a look inside the /logs/recovery/*.log files. I was surprised to find it contained all the start and length data from the scatter file. I wonder if the original scatter files weren't created from those files. Looking at the folder dates, I was also surprised to see a timestamp of "Jan 01, 2010, 12:07:36"
[Android Q&A, Help & Troubleshooting] Lohenstein:
The newest Firmware is 5.0.1,

Build A10-70F_S000121_151222_ROW

Does anyone have an idea how to root the device now?
[Android Q&A, Help & Troubleshooting] clsA:
So let me get this straight If diskinfo and TWRP tell me userdata is 2.99GB how do I determine the length I need in SPFT to ensure all the data is backed up ?

Is this chart correct ? and if so can you just use the 3GB hex address for length (C0000000)

or am I doing it all wrong ?

Change Scatter Address

Size: Hex-Address Decimal-Address
1,5GB 60000000 1.610.612.736
2,0GB 80000000 2.147.483.648
2,5GB A0000000 2.684.354.560
3,0GB C0000000 3.221.225.472
3,5GB E0000000 3.758.096.384
4,0GB 100000000 4.294.967.296
[Android Q&A, Help & Troubleshooting] Tzul:
That's the occupied size. You cannot assume that it is allocated in one contiguous block at the beginning of the partition. Those 2.99 GB worth of files could be scattered all over the 12.3 GB userdata partition (which in your case, with a 32 GB tablet, would be about twice as large).

So, if you wanted to make an image of userdata, after you've started using it (installed some new apps, copied some pictures and music to /sdcard, and so on), you'd have to dump the full partition, unless you have some "inside knowledge" about the highest address in use by your files (which you normally don't).

To find out the real size of the userdata partition (not the stub that is specified in the Scatter.txt for the sake of limiting the distribution size and unifying 16 GB and 32 GB tablet versions), check /proc/partinfo on your tablet. For the 16 GB model, the full size is 0x313580000 = 12.3 GB.

And that's why TWRP doesn't make images of those ext4 partitions, but archives their files. The result is going to be much smaller and will only contain data that's actually used. Alternatively, one can make a manual backup of the files in /sdcard (e.g. via USB) and use something like Titanium Backup for apps and settings in /data.

The A10-70F_S000121_151222_ROW update doesn't touch the /data partition at all, by the way. So we could have just copied over my original backup of the S000120 version. I checked, a few bytes did change after the readback, but that was probably some organizational stuff done by the filesystem driver, no actual file contents changed.

Yes, looks correct. Every decent calculator (both hardware and software ones) should have a hexadecimal mode for such conversions, by the way ("Programmer view" / Alt+3 in Windows calculator, for example).

And to summarize my ramblings from above: don't distribute images of userdata after it's been in use. They are too big, and your 32 GB versions won't fit on 16 GB tablets. Use other means like TWRP backups or update zips.
[Android Q&A, Help & Troubleshooting] clsA:
Thank you

I understand .. it will be easier to just create a Twrp flashable rom then .. thanks again for your time
[Android Q&A, Help & Troubleshooting] fjell_strom:
See this thread: HERE

___________

Also, I am on latest updated version of Lollipop and still have WiFi dropouts quite regularly. I have tried a few things I found across the net on this issue, but still so far nothing has solved it for me. Anyone have some good advice? Success stories?
[Android Q&A, Help & Troubleshooting] SCWells72:
Ever since disabling Allow Wi-Fi scanning under Advanced Wi-Fi settings, I haven't had any dropout issues. Have you tried that?
[Android Q&A, Help & Troubleshooting] fjell_strom:
Funny enough, it's been off for me for quite some time... though I turned it ON about half an hour ago and haven't had a disconnection yet. :p But I also assigned my tablet a static IP at the same time. Anyway, as said, so far, no dropouts. We'll see if it holds. Thanks for the suggestion.
[Android Q&A, Help & Troubleshooting] hajkan:
I like the Lollipop one but one thing pisses me of is that my F-droid installs keeps being uninstalled or vanished randomly after reboots ;( I installed Newpipe the other day. I restart it yesterday, boom the app is gone along with couple others. What the hell?

Also it would be nice if Kingroot is removed from the first post as a recommended method. That app is malicious.
[Android Q&A, Help & Troubleshooting] Badwater55:
Check if the vanished apps reside/used sd card; move the apps completely to internal memory.

I had the same behaviour on another device.
[Android Q&A, Help & Troubleshooting] fjell_strom:
Just wanted to report that, although it has only been a matter of hours, my WiFi connection has finally remained solid and not dropped a single time since I gave my tablet a static IP address, in case there are others looking for suggestions in regards to the same issue. Good luck.
[Android Q&A, Help & Troubleshooting] pjcons:
Ignore...
[Android Q&A, Help & Troubleshooting] fjell_strom:
No, of course not. Nothing in this entire thread is about the a7. Why would it be?
[Android Q&A, Help & Troubleshooting] clsA:
The last Lollipop update (A10-70F_S000121_151222) totally fixed all the issues I had with wifi. no static ip needed.
[Android Q&A, Help & Troubleshooting] Sparkrite:
First off, thanks for all your work on TWRP and especially for remembering me in the latest version. ;)

However I am not having much success with it (Lollipop 5.01 latest ver).

While it appears to make a backup successfully I cannot do a full restore, it stops when it tries to restore "System data" with a "Cannot mount /system" error.

Also the same error when I try to flash a zip, eg. Superuser 2.49beta.zip. But after the error it continues to the end of the script and says that it installed successfully, but it's not.

And just to cap it, when I try to use the integrated rooting method the familiar "Cannot mount /system" error flashes on screen followed by I think something like (too fast to be sure) "Renaming ROM ............ ........ ............????" and then reboots.

Any Ideas ?

TIA
[Android Q&A, Help & Troubleshooting] Old faithful:
just a quick question - have you tried on KitKat?
[Android Q&A, Help & Troubleshooting] Sparkrite:
Just a quick answer - No. :D
[Android Q&A, Help & Troubleshooting] Tzul:
Yeah, sorry, I had some mistakes in the init files that caused /system to be mounted read-only, and TWRP couldn't change it. Should be fixed now. Just download and flash the latest version (same link).

USB-OTG is working now, too - you can access external USB storage devices, if you connect them with an OTG cable (and if they have a supported filesystem... FAT and exFAT should work, NTFS doesn't).

I even fixed the "Partition SD Card" feature, although it's not that relevant anymore (its purpose is to create a 2nd and optionally 3rd partition on your external SD card, format it with the ext filesystem [hence "sd-ext"], so that something like Link2SD can free up space on /data by moving apps to that partition... but with >12 GB of available internal storage, you shouldn't run out of space on /data that easily).

If you try the new "Install SuperSU" button, let me know if it works.
[Android Q&A, Help & Troubleshooting] Sparkrite:
Great stuff Tzul, "Install SuperSu" working perfectly now, haven't tried a full restore yet but I have every confidence in your work that I'm sure that will be fine as well now. :D

PS.: Just did a full backup/restore...........................Flawless...............Very well done.
[Android Q&A, Help & Troubleshooting] clsA:
Same here ...restore works fine now

thanks again
[Android Q&A, Help & Troubleshooting] Old faithful:
OK, maybe I'm the only one not able to get it going...

So after unrooting, preparing the device for downgrading to KitKat and flashing it back to kitkat and installing the 150626 update from the standard recovery, with a normal boot in between each, after flashing the TWRP recovery for KitKat through SPFlash then immediately rebooting in recovery, the tablet boot loops once then starts normally without entering recovery, in effect erasing the flashed custom recovery: upon reentering recovery, I'm back to stock recovery.

In other words, upon first boot into recovery after flashing TWRP, it won't boot into it. Anything I could be missing? I'm going to try flashing Carliv Recovery for now and see how it goes.

There was one thing that I thought abnormal after reflashing KitKat: after I flashed the 150626 update ZIP through standard recovery, nothing happened when I selected "reboot" and I got stuck on the broken android picture. I had to turn it off with a long press on the power button, when I turned it on it started normally

Any help would be appreciated ;)

OK, Carliv works. So something must be off with the TWRP recovery...

OK, so after rooting with Super SU I decided to try installing TWRP again... And now there is NO RECOVERY AT ALL 8)

Back to reflashing Carliv... Wiping Cache and Dalvik... Reflashing Super SU... Rebooting... back to a functioning tablet... But the TWRP recovery for KitKat is definitely broken...

OK so I redownloaded the TWRP recovery from the link above and made a binary compare with what I flashed, and I definitely have the right file. MD5 sum is for TWR4.img: 69A05B56A8284AA93D1352870B4EF69D, for the TWR5.img: 2760F8D8481AF53C35829B0B65F30FAC.

At this point I don't know what else to say, going to reinstall my apps now, staying on KitKat.
[Android Q&A, Help & Troubleshooting] Tzul:
I guess you're the first to actually try my Android 4.4 version. I simply took the latest Lenovo kernel for Android 4.4 and packaged it with the recovery ramdisk, hoping it would work.

But apparently it doesn't...

Did you try to flash the Android 5 version? That one should work, even if you have 4.4 installed (again: the recovery is pretty independent of the installed OS, as long as the bootloader can run it, it should work).

By the way, could you point me to the specific Wifi Signal Booster app you're using? I wanted to give it a try, and see if it works for me.

I won't be going back to Kitkat on this tablet. I still dislike the abundance of white in Android 5 / material design. And I find the old way of having separate pull-down menus for notifications and quicksettings at left and right screen corners much more usable on tablets than Android 5's combined menu. But Android 5 is faster and more stable for me.

And now that I've figured out how to disable that darn dynamic backlight, it has even become as smooth as Kitkat. I'll explain how to do that later... ;)
[Android Q&A, Help & Troubleshooting] franizus:
Back in business !!!!

Thanks Tzul, for the work you did on TWRP for Lollipop and scatter file. Worked like a charm for me after getting repeated errors because of RAM mismatch??? from SPTK using the Carliv Touch Recovery (for 5.01 and 5.02). Surprisingly, they worked ok before I downgraded to KitKat because of the WI-FI issue. Today I re-upgraded to 5.01 again using the latest update from Lenovo (151222). I was not able to re-install Carliv as explained above. Your link to the new TWRP file is a life saver. Thanks a lot.
[Android Q&A, Help & Troubleshooting] suhridkhan:
Now this is something I would love to get fixed.
[Android Q&A, Help & Troubleshooting] Old faithful:
Your latest, corrected version works great on KitKat, as I mentioned in the sister thread, I also added comments on the recovery itself as it pertains to the KitKat versions. To sum it up, it works great :)

I'm using Wifi Signal Booster by Liqiaolan

However, upon further testing over a half hour period, activating and deactivating the utility, using WiFi Analyzer to measure actual signal variation, I did not see significant change from the background variations. Sometimes the signal would drop with it activated, sometimes the opposite, sometimes for no reason at all. As if it had no real effect. Go figure! But it did keep my WiFi connected when I first used it over an evening far from the router. But I digress, this would be better discussed in the sister thread.

Furthermore, it conflicts with the Xposed Framework: it opens and closes immediately when the Xposed Framework is installed, at least on Lollipop.

Great to know. If you've figured a way to tone down the reds (greens and blues are fine) or otherwise control saturation that could be useful on KitKat, please let me know! Display control on this device is definitely a work in progress. colors are much more natural on Lollipop. On KitKat, even with Miravision tuned way down, skin tones are still too ruddy and unpleasant. So yeah, I'm on the fence on this one and am not sure I will stay on KitKat ;)

But I do like the fact the battery percentage works, that the One More Clock widget works again and that it may even be possible to run the CirclesWidget3D.

I'll post my findings at some later time on the sister thread, pros ans cons of each OS.
[Android Q&A, Help & Troubleshooting] clsA:
I left some goodies for those on Lollipop and TWRP here >> http://xdaforums.com/showpost.php?p=64546198&postcount=3