yashsingh1/xdaforums huggingface dataset:
[Android General] mayomac:
Hello i have a problem with my tab 2, i cant power it on all i get is a black screen i cant get into recovery nothing will work.

I had about 80percent battery on it when i turned it off last night. I would wecome any help thanks.

Also sorry if i have posted in wrong place
[Android General] Sparkrite:
Have you tried holding the power button for 12 seconds, to force a re-set?
[Android General] mayomac:
Have tried that no joy still have black screen, I also took off the back cover and disconnected the battery reconnect it tried the power button again still no luck.
[Android General] Sparkrite:
Ok, not great, is the preloader being recognised by a PC when it is connected via USB.

If so then maybe a full flash using SPFT could revive it.
[Android General] mayomac:
Good news got it back to life using SPFT

Thanks for your help :good:
[Android General] Sparkrite:
Excellent !!

Thanks for letting us know.
[Android General] Old faithful:
Wow... You miss two weeks due to heavy work and and you've got quite a bit of catching up to do with all you guys' adventures... Kudos, folks! :thumbup::thumbup::thumbup::thumbup:

---------- Post added at 04:42 ---------- Previous post was at 04:18 ----------

Sorry to bring this old post up, but this has been nagging me for a little while - I have had problems with Dolby Atmos for quite some time now due to my use of mortplayer - essentially, the sound inevitably gets tinny and distorted and all settings in the Dolby Atmos become greyed out and the only solution that works is to reflash the system partition from a TWRP backup...

I checked up the linked up post where the original Viper Atmos driver was published and notice it says it's only for CyanogenMod ROMs - would you care to explain in short if I can install it directly or how if it requires special instructions on a standard KitKat ROM such as what I'm running?

On another subject that's related - have you guys noticed any crackling and stuttering when using this tablet with a Bluetooth headset? It only happens using Bluetooth, when I use my headset wired directly everything works fine. The headset in question is a Plantronics BackBeat Pro, which is working perfectly with my Galaxy Note 2 and my PC.

For those who might be interested, that headset is so good and the sound that comes out of it has such depth that I'm rediscovering my recordings altogether, it sounds way better than what is coming out from my big sound system speakers, so much so that I've basically retired it and only use it when we have company ;)
[Android General] ArchieGodfrey:
Sorry to be a noob but will this work for the A10-30F?
[Android General] Tzul:
[MENTION=6912230]ArchieGodfrey[/MENTION] Some of it might (e.g. rooting with Kingroot), but generally, no, it won't work. The Tab 2 A10-30F uses a Qualcomm chip, not a MediaTek one, so you can't use the SP Flash Tool, and also not the A10-70's firmwares and recoveries.
[Android General] loner.:
I wonder if Lenovo will release a update for the tab 2 a10-70f?
[Android General] zMILWAUKEE:
This is no big deal but I thought I would ask. For some reason no app, or the advanced power menu will reboot into recovery. I can manually boot into recovery so I'm not to worried about it. But it bugs me that the device itself won't do it unless I power off and get into recovery with key, power combo. TWRP itself won't even reboot into recovery. I'm on the bliss pop 5.1 based ROM, with TWRP 3. Any suggestions? Thanks everyone. Oh just a quick mention, it was all flashed through TWRP. And I need to add one more little quirky issue, when the tablet is plugged in and only when I'm plugged in, if I choose power off it will shut down but then restart right away.
[Android General] lion567:
[MENTION=5353647]zMILWAUKEE[/MENTION], I've also suffered from this issue after flashing BlissPop. Neither

adb reboot recovery

nor

adb reboot-bootloader

worked for me from Android or TWRP. In all cases my A10-70L rebooted back to Android and this was rather annoing :(

It seems that issue was somewere in 5.0 bootloader, included in BlissPop ROM - I've flashed stock lk.bin for KK patched by [MENTION=5919159]Tzul[/MENTION] and this did the trick for me. :good:
[Android General] zMILWAUKEE:
What post # was that in. Never mind, found it. And of course you came through again. Thanks you and Tzul for all the knowledge you guys share.
[Android General] Tzul:
I guess this happens when there's a mismatch between preloader and bootloader, e.g. if you have the old preloader installed, but the new bootloader. They must have changed something in the preloader that the bootloader relies on to properly determine the boot reason.
[Android General] zMILWAUKEE:
Thank you for that patched ik.bin, it worked like a charm, back in business.
[Android General] worm9110:
Milwaukee, I haven't tried this out yet. Thanks for prepping it for us. Would you say this is bug free enough to use as a daily driver?
[Android General] lion567:
Yes, correct, very helpful info, thanks a lot! :good:

I've reflash preloader and lk.bin from latest 5.0 stock (A10-70L_S117_160226_ROW) and reboot worked as intended.
[Android General] zMILWAUKEE:
Yeah it's bug free, been able on for a few days. Don't DL from that link, I'm uploading a new one right now with the reboot problems fixed. If you decide to use the backup make sure you restore ik.IMG, recovery, boot, and system. Will edit previous post as soon as upload is ready.
[Android General] cscxda:
Error-free flashing via Ubuntu 15.10, 64 bit (and 15.04, 14.04 LTS)

If you find this via search, go back and read the whole thread, not just the OP, for some very useful information on the SPFT package and details on this tablet's partition table and such. Prior to this post, I was not even aware of SPFT. This is 64 bit, no 32 bit SPFT. ANYTHING not Windows specific on the OP still applies though you only need step 3.

Adjust udev settings. You can use this link from [MENTION=6466472]Miss Montage[/MENTION] (no idea what to do about that space in her username; only my 2nd XDA post): http://xdaforums.com/general/rooting-roms/tutorial-how-to-setup-spflashtoollinux-t3160802 I also temporarily disabled the modemmanager service when using SPFT.

Download latest SPFT for Linux. I used v5.1604, no drivers needed. I used the twrp 3.00 recovery (same location as the 2870 version in the OP) initially compiled by [MENTION=5469284]lion567[/MENTION] and tweaked by [MENTION=5919159]Tzul[/MENTION] to include SuperSU option, etc. from his original 2870 recovery.

Before starting SPFT, edit the [ReadBack] section of option.ini to change ShowByScatter to true. On the Download tab, load the correct scatter file for your Android version. Backup the proinfo and nvram partitions via Readback tab. These are the partitions that contain info unique to your specific hardware such as MAC addresses, etc. Via Download tab, flash the recovery file to the recover partition only. Make sure the dropdown is set to Download Only so you don't format/delete everything.

Upon completion, boot into recovery, NOT the system which would overwrite your new custom recovery. Under Advance settings, set the Install SuperSU option and reboot normally. Done and rooted.

--csc
[Android General] zMILWAUKEE:
Just uploaded the wrinkle free backup, link here http://xdaforums.com/showpost.php?p=66200242&postcount=690
[Android General] Old faithful:
Those on Windows who'd like step by step instructions on rooting and flashing using SPFT can just PM me, I've written a step by step guide a couple of months ago as a helper to be able to do it with minimum fuss. The only caveat, apparently it's quite verbose (or so I'm told) ;)
[Android General] loner.:
You may want to check you link, all it does for me is send me to the play store for a app called Mega.
[Android General] suhridkhan:
Link is fine, try form computer. Or on your browser check 'request desktop site'.

Alternatively, you can actually install that app, and it will take care of the download.
[Android General] cscxda:
That poor preparation crack sounded funny in my head. Sorry.
[Android General] loner.:
I'll pass.

Link is not fine, for me I do not want the app.
[Android General] zMILWAUKEE:
After you download file you can delete the app. Or in your browser go to mega.nz, request desktop site and search for the file name. I tried 3 times to upload to mediafire the upload finished but it is not showing up on the site. I will open a One Drive acct and post link.
[Android General] loner.:
Don't worry about it. I am good.
[Android General] Old faithful:
So I was able to test the tablet with another Bluetooth headset and everything works as it should. Looks like the BackBeat Pro is incompatible with the Lenovo Tab 2 A10-70F. Or at least when running KitKat...

I've also decided I don't like Dolby Atmos at all - the Mortplayer equalizer gives much better results IMO...

Any comments from those who have tested Dolby Atmos under both KitKat and Lollipop?
[Android General] Papanik:
Guys after using the custom 5.1.1 ROM (the one based on BlissPop), I have to say it's very smooth and fast.

However, I seem to have HUGE battery drain, compared to stock Lollipop 5.0, both when I'm constantly using the tablet, but also when I'm not.

(e.g. during 8 hours of no use, stock Lollipop 5.0 had battery drain like 10-15% maximum, this 5.1.1 BlissPop ROM has like 40-45 minimum for me.)

Anyone else with the same issue?

P.S.1. I always use the exact number of apps (quite a lot) and settings for all my ROMs so it's not that.

P.S.2. Don't know if it has to do with battery drain, actually don't think so, but I have the BlissPop version without the correct Ik.bin file (haven't had the time for flashing yet).

I'm wondering if there is any "solution" (besides having to charge it every night), because I really like our first custom ROM and it is quite faster than stock Lollipop, loaded as hell that is. The difference in speed is noticeable even when screen goes on-off during the magnet case open-close routine.
[Android General] nannycrick:
Still trying to upgrade to 5.0.1. I have upgraded five times..via your instruction in the OP, via reverting to stock kitkat and upgrade thru OTA, and have flashed the updates that goes with Lollipop. I make it as far as trying to debloat, and it reboots to logo and nothing! I attached a screenshot of my device details. It seems that I have to settle for KitKat. Thank God for nandroid backups!.....yes, I have the patch update A10-70F_S00022_150626.zip for KitKat flashed.

In response to Old Faithful...

I had to wipe cache & dalvik, flash ViperAtmos, reboot. Open app, load the drivers, make sure my choices are set, reboot to recover again, and flash again without wiping. The settings were good then.

I have guitarhero's Viper+Atmos in the Tab2 Kitkat, and his Viper+SonyBeats in my HTC Desire 626s 5.0 1. I don't run a Bluetooth speaker except for phone calls (a junky old RCA over the car visor model) so I can't relate to that issue.

No problems in Kitkat, but the HTC requires SELinux Mode Changer to the partitions to permissive. (A stupid HTC security thing has all the partitions set to enforce), and Walkman Player does "auto stop" if I move the device. A Walkman Player issue? I've relayed it to Ibanez7 who is the dev for that ported player. Sound is breathtaking in both devices with a pair of Sony or Beats headphones! My Pink Floyd collection is amazing....again!
[Android General] Sparkrite:
Hi all,

Thinking of flashing this Blisspop rom (thanks to [MENTION=5353647]zMILWAUKEE[/MENTION] for uploading the patched TRWP image).

What I would like to know is are there any advantages, other than speed, over the stock 5.01 rom.

TIA.
[Android General] zMILWAUKEE:
I'm also on this ROM and don't notice any more battery drain than stock. The ROM does have a bunch of apps that run in the background that you can disable, do not disable adaway cause if you do it will break the dev options. I have a backup with the proper ik here http://www.mediafire.com/download/s88s06zt9998x3z/Patched_BlissPop_TWRP_Backup.zip if you want to use it. Oh yeah if you have the F variant, delete all the cell phone apps, I.e. dialer, cell connection, etc. Don't need them running in the background as we can't use them anyways.

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

Not sure if it's just me, but It seems I get better Wi-Fi performance and better video streaming. I love the viper audio already installed as I think we all agree atmos was a waste of time. The only thing I miss is the Mira vision app and the ability to adjust color, contrast, and such. Love the Bliss Interface, you can customize almost every aspect of ROM without having to install xposed, and with the theme manager you can install the parts of a theme you want and not the whole theme. It's pretty awesome.

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

Quote:

Originally Posted by loner.

If it were English I would be on it.

Well I went and reflashed it and figured everything out. Here is an TWRP backup if your interested https://mega.nz/#!ax8jwLTB!Xt1Mjcl1w...CdRLedZ-MAu_rg , or here http://www.mediafire.com/download/s8...WRP_Backup.zip After restore, everything should be in English, and I set DPI back down to 240, enabled soft keys. After a few hours of messing with it, I'm enjoying it more than lollipop.
[Android General] loner.:
You have done a lot of work finding a custom ROM, and making the ROM compatible for us, when we had absolutely no other choice but the stock ROM.

Great job! Thank you.
[Android General] loner.:
Only problem I can see with this rom is the CPU runs at full speed all the time. CPU-Z says all cores running at 1417mzs all the time.

---------- Post added at 03:05 PM ---------- Previous post was at 03:04 PM ----------

Check and see what your CPU is running at?
[Android General] loner.:
I checked the kernal auditor and it also says that all four cores frequency stays at 1417 MHz at all time. Should I change the governor from interactive to something else?

Any ideas?

Thanks
[Android General] lion567:
It seems that the author of BlissPop for A10-70L port (@psihop at russian Lenovo forum) doesn't properly take in to account SoC differences (MT6752 for P7000 and MT8732 for A10-70L) and there are incorrect (non listeted in /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies) max_freq parameters in /init.hermes.power.rc

# Balanced
on property:sys.perf.profile=1
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq "1469000"
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq "1469000"
write /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq "1469000"
write /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq "1469000"

and even incorrect cores number for Perfomance mode

# Performance
on property:sys.perf.profile=2
...
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq "1950000"
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq "1950000"
write /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq "1950000"
write /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq "1950000"
write /sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq "1950000"
write /sys/devices/system/cpu/cpu5/cpufreq/scaling_max_freq "1950000"
write /sys/devices/system/cpu/cpu6/cpufreq/scaling_max_freq "1950000"
write /sys/devices/system/cpu/cpu7/cpufreq/scaling_max_freq "1950000"

I've set Max CPU frequensy to 1690MHz in Kernel Auditor and select apply on reboot option. And I'm not use Power managment options because they'll set incorrect cpu_max_freq again.

IMO the only multicore aware governor, that supported by existen kernel, is interactive, but may be we have to tune its parameters...

It's the first release of custom ROM for A10-70 and there are a lot of things to fix, so be patient and forgiving ;) May be some issues would be fixed.
[Android General] loner.:
I guess I could use with Trickster Mod to adjust the kernel, but would like some kind of guide since I don't know what I am doing.
[Android General] doandm:
Nice guide, thanks a lot.
[Android General] zMILWAUKEE:
Not sure if any CPU mod app is going to work. The person that ported this ROM ported from a whole different chip set, and if I'm not mistaken, the CPU parameters have to be set within kernel. If when he brought this kernel over to our tablet he only set the max CPU freq. at a certain level all the mod apps will only read that max level that was set within the kernel. And if he got that wrong, I'm not sure I would then "over clock" the CPU, cause then the thermals are not going to work properly and you might just run the risk of overheating, even though the CPU is running at the right max freq. Even on the freq. set by his kernel my tablet has been running warmer than normal, and that's not even running it at full speed. Overall I love the ROM though, but if someone is going to truely build a ROM they are going to have to do it from the ground up and not port. I have been searching all day and have come to the conclusion that this chipset we have on the A10 is only on the A10. I only found 1 other device with it and that was a seven inch China phone with only 1gb of RAM. So looks like we need the stock kernel tore down and rebuilt.
[Android General] loner.:
Would the stock kernel come close to working as is for the BlossPop rom?
[Android General] zMILWAUKEE:
I'm thinking it will, because you gotta remember he ported those to work on this tablet, so I'm thinking it will work for any ported rom for our tablet. I mean other devices that have more than just one modded kernel can flash any kernel with any ROM , as long as both are for that devices chipset. For instance, my desire 510 has like 5 different kernels and about 5 custom/ported Roms, I can flash any one of those kernels with any of the Roms. The only way to find out is to try it. Worse that could happen is we reflash back. Now that you mentioned it I might try it out later and post results.
[Android General] loner.:
If you make a flashable stock kernel send me a copy and I will help test it.
[Android General] zMILWAUKEE:
The stock kernel is within the boot.IMG , I'm going to flash the stock boot.IMG with the blisspop system. IMG. Post back in a bit.
[Android General] loner.:
A stock Android 5.0 kernel should work on 5.1.
[Android General] zMILWAUKEE:
Well that didn't work...:(
[Android General] loner.:
That's what I thought, instead of flashing the boot.img I think we need just need the kernel.

Since I started messing with the blissrom and back to stock, I can't just boot to recovery or bootloader anymore. I have to shut down completely the "power button + volume up" to get into the bootloader then go into recovery. Is there a solution to get booting ability back to normal?
[Android General] zMILWAUKEE:
Tzul posted a patched ik.bin file here, not sure what post it was in though. Are you on lollipop. If so download my restore file that I posted and restore just the ik.bin, reboot into recovery and when you restore your backup make sure the ik.bin box is not checked. http://www.mediafire.com/download/s88s06zt9998x3z/Patched_BlissPop_TWRP_Backup.zip , just in case you need it. What you could do is extract just the ik files from my backup and copy and paste them to yours making sure to overwrite yours, and then just restore.
[Android General] loner.:
Sadly, it didn't work for me.
[Android General] zMILWAUKEE:
OK I found what Tzul posted that worked. http://1drv.ms/1oawUOX , what you want to do is change the ik.bin to ik.IMG and do a image flash with TWRP. The one I'm using is the patched.lk.bin in the kit Kat folder. Works great on bliss, and stock lollipop. If flashing through TWRP or flashify make sure you remember to change the .bin to .img and this will definitely work.
[Android General] loner.:
Ok, thanks I'll give it a try. I hope it works on the tab2 a 10-70f.

---------- Post added at 12:11 AM ---------- Previous post was at 12:01 AM ----------

Should I flash the preloaded file also?

---------- Post added at 12:35 AM ---------- Previous post was at 12:11 AM ----------

Well I flashed the lk.bin(IMG) and the preloader.bin(IMG) not good.

I hard bricked the device. After I flashed I hit reboot and it died.

Can't turn it on or anything. Paperweight, oh well live and learn.
[Android General] delapps:
Thank you for sharing this patch. It works perfectly.

The annoying brightening issue on the lenovo a10-70f running kitkat 4.4.4. is gone.
[Android General] dallev79:
So I'm considering this tablet for my father. I recommended he ad some $$$ and get something better like Nexus. But he doesnt want to shell out that much cash manly due to his limited using patterns. He only want to be able to read some magazins,browse,check mail and do some banking.

He wants the LTE version so he can bring it with him on his travels.

So my questions are:

1. Is there a official Lollipop upgrade for the LTE version?

2. If there is, is it stable and worth considering?

3. If no, is it worth upgrading to 5.1.1 with root? Does it get any better then stock kitkat?

Im a Nexus junky so I would like to remove bloat. Even some Google bloat. Is there a way to do this? It would be sufficient with the stock ROM ,just do a heavy debloat.

I know this will never happend, but I would love cyanogenmod for the tab2.

Thx in advance.

PS. I read the thread, but kinda confusing. Thats why I'm making questions.
[Android General] zMILWAUKEE:
Does your PC recognize the tablet when you plug it in. If so it's not dead yet.
[Android General] Tzul:
The file you linked is for the Tab 2 A10-70L. Here is the corresponding file for the Tab 2 A10-70F.

Like I previously said, preloader and bootloader should be kept "in sync". Either use the old "Kitkat" ones, or the new "Lollipop" ones. Having the old preloader + new bootloader (LK = Little Kernel) is what caused the reboot into recovery issues.

And just to be clear: lk.patched.bin is a version of the old Kitkat bootloader that I modified so that it can Fastboot-flash most partitions. The new Lollipop bootloader can do that by default.

It's been mentioned here before that you should be careful about flashing the preloader, and avoid unless you know it's necessary and you are using the SPFT. What did you use to try and flash the preloader?

Anyway, your tablet can probably be recovered. Get the SPFT running, Windows or Linux version. Try to find out if the preloader on your tablet really is damaged, or if it's just the bootloader. If it's the former, there might be a special unbrick option that allows you to flash a valid preloader. [MENTION=7184758]charlestek[/MENTION] posted this link earlier in this thread. Remember, there are signed drivers for Windows, meaning you won't have to deal with the disabling signature enforcement stuff at least. For the Linux version, you can find pointers here.

If the preloader is fine, then you can flash the other partitions regularly with the SPFT.

You mean my AAL patch? You're welcome. :)

1. Yes. You can find a list of official firmwares in my German topic here. Even if you don't read German, the list shouldn't be hard to understand. As you can see there, the latest firmware for the 70L is S000117_160226.

2. Yes. You'll get more out of it with Root and Xposed, of course. And don't forget to disable AAL.

3. As you can read here, the unofficial 5.1.1 firmware has quite a few bugs and isn't really prime for "normal" users yet.

There really isn't that much bloat. There's over 300 MB of preinstalled third-party apps on the system partition, among them Japanese and Spanish ones, for example. But most of them are disabled by default, because they only get enabled if they match your region. Still, it's of course better to get rid of them entirely, which is as easy as deleting the entire /system/appjar/ directory. Requires root or a custom recovery, and should not be done until after you've installed all updates. Because you cannot install official updates (incremental ones, "type 0") with a modified system partition.