Related
Do not use the lagfix anymore voodoo will be incorporated into our new kernels very soon. Thanks
Kept the attachments so you can remove if needed!
I keep getting permission errors when I try this. I found another way to update busybox but the script doesn't work
With the current limited root I have, I could not write to /system/bin. I just woke up and I didn't feel like figuring that out, so I copied stuff to the sdcard, then I used cat to write the file to /system/bin as shown above (steps below). I would suggest before starting, download Quadrant Standard from the Market, run the full benchmark and see where your device is on the list. Mine was below the Galaxy S before starting.
This is what I did (on Mac) to get busybox in place:
Code:
./adb shell
su
mkdir /sdcard/lag_fix/
exit
exit
./adb push ~/Downloads/busybox /sdcard/lag_fix/
./adb shell
su
cat /sdcard/lag_fix/busybox > /system/bin/busybox
cd /system/bin/
chmod 755 busybox
ls -l (check the permissions)
exit
exit
Now busybox is in it's right place with the right permissions.
Now, I have to manually execute the steps in the lagfixme.bat file, because I'm not on a PC and I don't feel like re-writing the script, because I just woke up.
Before pushing the files, I edited lines 35 and 36 in the createlagfix.txt file to fit my sdcard folder path. I like to keep my SD card organized, so I put all the files from the zip into the /sdcard/lag_fix folder I created above. Here is what my line 35 and 36 look like before I push createlagfix.txt to the SD card:
busybox cp /sdcard/lag_fix/playlogos1 /system/bin/playlogos1
busybox cp /sdcard/lag_fix/userinit.sh /system/bin/userinit.sh
Now, I know the folder paths below looks ugly, but that's because I just pushed the files directly from my Downloads folder. Hopefully you guys can see what I did here. If not, let me know and I'll edit the post to read better. These are basically the lines in the batch file written out manually for Mac users:
Code:
./adb kill-server
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/createlagfix.txt /sdcard/lag_fix/createlagfix.sh
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/playlogos1 /sdcard/playlogos1
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/userinit.sh /sdcard/userinit.sh
./adb shell su -c "/system/bin/sh /sdcard/lag_fix/createlagfix.sh"
Once the process is complete, run Quadrant Standard again and you'll see your device as the fastest one in the list.
Many thanks to Dirrk!!
Worked just fine for me.
Thanks for this and your root instructions!
Guys, is the phone actually laggy, or are you just assuming it's laggy because of complaints with the other models? I mean, you've only had them a day or two, right? Took me longer to notice lag than that on my i9000.
I'm tempted to grab a Fascinate, but all the issues I've had with the i9000 and it's a tough call.
I've seen it lag sometimes under high load, but I thought that was normal.
I've tested it with GroceryIQ, to compare against the last 30 seconds or so of this video ( http://www.youtube.com/watch?v=10ox35vMS78 ) and the Fascinate is nowhere near as bad at lagging. That video was 8/21/2010, so they may have updated their application by now, not sure.
Edit - Anyway, it works just fine. Nice work Dirrk! 2,191 !
Yep, worked like a charm! My Quadrant score jumped to 2125 after the fix. Phone is much snappier too. Thanks Dirrk!
i've been trying this but i keep getting permission denied.
can someone take me step by step on how to do this?
So, after running this, I am now getting a notification that internal storage is nearly full. Any ideas?
spotmark said:
So, after running this, I am now getting a notification that internal storage is nearly full. Any ideas?
Click to expand...
Click to collapse
If you have root, you can now remove many of the bloatware apps that you do not use (this fix uses 1gb of your internal storage - performance is expensive)
m2cool2go said:
If you have root, you can now remove many of the bloatware apps that you do not use (this fix uses 1gb of your internal storage - performance is expensive)
Click to expand...
Click to collapse
Whoa, careful there. That's a quick way to brick your phone. Try removing Verizon Backup Assistant and you're bricked.
C:\sdk\tools>adb shell
$ su
su
# cat /sdcard/busybox > /system/xbin/busybox
cat /sdcard/busybox > /system/xbin/busybox
cannot create /system/xbin/busybox: read-only file system
Any ideas why I'm getting this error? It looks like I'm screwing up something very simple...
namebrandon said:
Whoa, careful there. That's a quick way to brick your phone. Try removing Verizon Backup Assistant and you're bricked.
Click to expand...
Click to collapse
Really? I removed Backup Assistant and I'm not bricked. Am I missing something?
Removing VZW backup assistant will absolutely not brick your phone. Its one of the first things to go on all my android phones since the eris.
undo lagfix
Hello. I want to undo this for now, due to running out of space for apps. I assumed running unlagfixme would do the trick, but it hasn't given me back the 1 gb it used. Am I doing it wrong, or is it stuck like this now? Thanks for your help!
is there a list of apps someone can recommend to remove that's just bloat? thanks....and ive ran this quadrant score, im averaging 871 three times testing now with minimal apps (used task killer...) - and ive got 177mb left on my phone hehe...
Nevermind, figured it out
xirnibor said:
is there a list of apps someone can recommend to remove that's just bloat? thanks....and ive ran this quadrant score, im averaging 871 three times testing now with minimal apps (used task killer...) - and ive got 177mb left on my phone hehe...
Click to expand...
Click to collapse
You screwed up if your only getting 871 thats stock. Open up a shell on your phone and type mount and place the results in here
Whitepaint said:
Removing VZW backup assistant will absolutely not brick your phone. Its one of the first things to go on all my android phones since the eris.
Click to expand...
Click to collapse
Thanks for the info, and my bad on the post!
I heard that removing this on the Droid X was bricking phones.
If people want to share what they've been successful in removing/renaming, that would be helpful.
namebrandon said:
Thanks for the info, and my bad on the post!
I heard that removing this on the Droid X was bricking phones.
If people want to share what they've been successful in removing/renaming, that would be helpful.
Click to expand...
Click to collapse
I am waiting on rom manager so I can make a back up before I continue removing stuff
I have wasted more than 3 days trying to figure out how to configure openvpn
on S2.
I tried the following roms:
Villainrom 1.4
Cognition S2 v1.07
Skyrom 1.0
Lite'ning Rom v1.5
and none of them seems to work.
I tried everything mentioned in :
http://forum.xda-developers.com/showthread.php?t=1115984&highlight=openvpn
http://forum.xda-developers.com/showthread.php?t=1074492&highlight=openvpn
but openvpn does not work.
I also own a HTC desire and configuration files work without a problem.
I tried manually installing openvpn as described in the posts but it does not work.
The problems are:
If I install openvpn manually as described in the threads above it does not connect to the openvpn server.
I installed openvpn from the market by selecting the folder for the binary
/system/xbin
and tried all the possibilities for path for ifconfig/route.
- /system/bin
- /system/xbin
- /system/xbin/bb
The default folder for ifconfig/route should be /system/bin (result from which ifconfig) and only that selection does not give the horrible
"FATAL: Linux ifconfig failed: could not execute external program".
but openvpn still does not work.
Any ideas ?
Hello,
I have the same problem, with same error
but I have successfully get connected to my vpn (vpntunnel.se) but its useless since the route doesnt use the vpn connection.
If anyone could help...
i have same problem too. some help would be good
Could this help?
I'd love to get this working too but I have not made any attempts yet so I'm monitoring this thread.
Searching for that exact error message on google led me to this thread which you may already have found.
In particular, even though it's about the galaxy i5800, the following comment may shed some light:
you may not use the pre-installed busybox from samsung (which is found in /sbin). It is a reduced version of busybox that does not include suitable ifconfig- and route-commands for openvpn. thus you have to install a full version of busybox... normally this is done, when you root your phone according to descriptions found in this forum.
you can alternatively install titanium backup (which installs its own busybox) and copy the "full" busybox from titanum backup to /system/xbin.
Click to expand...
Click to collapse
Try to do it but impossible for me. Im with lite ing rom. Check my configuration tomorow
Sent from my GT-I9100 using XDA App
Alright, so after going nutts (several times) I solved this issue (several times) only to always find I dont really know what the error is. But then again, I know more about Geological disasters than I know about Android ...
Anyways, heres my solution which appears to work. However, it goes away once you reboot (easily fixed) and disappears completely after you update firmware - but I made shortcuts.
The thing is, that the original busybox is not installed where openvpn looks for it. Regardless of this, openvpn has no idea how to use ifconfig / route commands in /system/bin directory.
So this is what I do:
1) Install busybox (from the market, get ver 1.19) to /system/xbin
2) Install openvpn to /system/xbin and point ifconfig/route to /system/xbin/bb (during installation).
3) Link the new busybox to the /bb directory MANUALLY with these commands (customized to steps 1/2 - you can change them to your liking but dont forget to update step 3 as well):
ln -s /system/xbin/busybox /system/xbin/bb/ifconfig
ln -s /system/xbin/busybox /system/xbin/bb/route
Click to expand...
Click to collapse
What it does is place a busybox link to ifconfig and route in /bb directory.
Funny thing - Whenever I tried linking ifconfig/route to other places (like /system/xbin) it just didn't work. It made the tunnel, but tun0 int was always down (thats why it says "connect to as xx.xx.xx.xx" missing the tunnel internal IP - as in, no routing).
Challanges - when you soft reset, something dies. Not sure if its the busybox or the links. However, simply "reinstalling" busybox to /system/xbin solves it (its not really reinstalling, its just going into the busybox installer. Its only recreating links).
When you install an update/new cfw, everything dies. Reinstall busybox and re-enter the link commands.
Hope this helps, hope some android programmer tells me why it works this way. gluck.
So I was having the issue with the settings menu force closing after I rooted the device.
This morning I've done a factory data reset, gone to turn the tablet on, and I'm not getting "The application OLS (process com.sony.nfx.app.ols) has stopped unexpectedly. Please try again.
Can't access the device, tried another factory data reset, can't flash a firmware as I can't access the device.
Not very happy at all.
But any ideas please?
**I can get into the settings menu and when I press the home button is when I get the OLS force close, so I assume it's the home launcher, I did remove it when my device was working.....
I can't access device storage either, even when my device is on - or ADB, but I can access an SD Card through the boot menu.
Well factory reseting doesn't restore anything you deleted from system, but wipe anything else you installed.. so there's the big problem.
On my tab, I can force a boot loop by holding volume down when booting (hold vol down for what seems like an eternity/till you are satisfied that it is boot looping).
ADB seems to work here, so you could potentially push a different launcher apk and get it going that way.
Thanks for the response Dan,
What I can do is start the device, there's no launcher there, but inbetween the force closes I can get into the settings, there's no force closes when I'm in there.
I connect the USB, ADB Devices and it shows, I can pull from the /system but not push.
As soon as I type ADB Shell, then the commands, it tells me "error: device not found"
Exit out of ADB Shell, ADB Devices again, and it's there - but ADB Devices when inside ADB Shell shows nothing.
I've tried all of the OTA packages in the other thread and nothing - I'm at a bit of a loss, i doubt Sony would work with me on this one, so It looks like I've got £349 of paper weight. Any ideas on the ADB? At least then I could push a launcher in.
The issue clearly is becuase there's no launcher.
I remove the default launcher from the /system/app folder and install ADW, the factory reset obviously removed it, hence there's no launcher...
What if the APK for ADW was made into an update.zip?
Would it flash when I hold down power + volume+, Update System from zip?
bummer
Not really sure what can be done if you deleted them from the system and the reset does not reinstall them.
Perhaps someone who has rooted can send them to you, but not sure how that would work.
I'll get in touch with Sony tomorrow, now I know that this is my own fault, but under the warranty they are still abliged to fix it, I certainly won't be rooting it again, thats for sure.
I hope they will help me if I'm honest?
Did you have a look at if ADB works for you in the forced boot loop state I mentioned? It could possibly do some extras from there that you can't otherwise.
Also just try sending a third party launcher in so it's doesn't have to go to system, perhaps it will let you write the file then. And hopefully auto - detect it upon booting .
Tried it Dan, if I attempt ADB Install launcher.apk, it starts installation then;
[1] Killed pm install /data....
I'm getting permission denied in every ADB command when in the Boot Loop.
Thanks anyway - I've emailed them, and been totally honest about what I've done.
I could swear all day - I've fixed it, my tablets working again, what a bloody relief. Thanks ADB!
I tried to duplicate your problem with adb :-
Typed ADB Devices - reports attached device OK
Typed ADB Shell - prompt changes to $
Typed ls - shows root of tablet
Typed cd system - changed to system directory
Then ls again then cd app then ls again - shows all system apps
I then typed ADB devices again and lost the connection to the tablet
It would seem that on my tablet at least that typing ADB devices whilst within the ADB shell breaks the connection with the tablet
Thanks for testing it praed0r, I'm pleased to know that it's not just me that had that issue.
It may be of use to someone, but what I did was mount the /system partition as rw using busybox.
Code:
adb shell
su
busybox mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
From there I removed the app that kept forceclosing, in this case it was OLS (or something like that)
I then mounted the /data drive with;
Code:
busybox mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /data
Then using cp instead of ADB Push,
Code:
cp /sdcard2/golauncher.apk /system/app/golauncher.apk
Rebooted the device and it all worked fine, GoLauncher booted as my default launcher.
For some reason it didn't like adb push, and would give me permission errors, but mounting as busybox fixed it all....
I changed the build.prop so that it would system update, it indeed does, but all STOCK apps (Sony apps) force close, it could be becuase of the framework.jar from the other thread, so I'll try and source one from a kind individual. Then I'll do the update and my system will be OK.
I'd consider myself very lucky this time, lesson learnt not to tweak with things.
I'll stick to the build.prop/local.prop tweaks for now
Any idea why the system apps aren't working, i've retraced my steps to before it happened, the only notable thing that would have an affect was changing the framework.jar?
Recently I decided to try Slim Bean on my phone, seeing they released a new version a few days ago. I had been running Cyanogenmod 7 but decided it was time for a change. Initially, everything worked great, I was able to reinstall all my old apps, send texts, and things functioned well.
About 12-14 hours after doing this however, my phone stopped having signal. I didn't reboot it or anything, just no longer would it pick up a signal. Checking the about phone revealed it saying it had an unknown baseband and IMEI, I wasn't too concerned, I had backups of the EFS files, so I turned on USB debugging, plugged my computer in, and used an adb shell to move the backup to the main system. However, this still didn't work for my phone.
According to the Slimrom's FAQ, there are two solutions to this: delete the 00check and 98tweaks files in the system/etc/init.d folder, or just reinstall the ROM. However, using an adb shell or a terminal emulator on my phone, both with superuser powers, I can't remove those files. chmod spits back that they are read-only files. lsattr shows only the A tag active, which shouldn't be standing in my way. I seem powerless to get rid of these, and I can't find any guide as to how to do so. I've tried restoring to factory defaults and reinstalling the ROM, and this time I don't have signal right from the start. Can anyone help me figure out what to do about this? I've searched around and can't find any answers, which is making me think I'm just missing something really stupid. Any help would be appreciated!
Update: Figured it out. The system partition was mounted as read-only, and I thought I had tried remounting it but must have tried a higher level directory or botched the command. mount -o remount,rw /system gave me the ability to delete those files. Sorry for the trouble!
Hi
I've installed CM10.2 (last update) (http://forum.xda-developers.com/showthread.php?t=2499796) on my Archos 80G9. It also runs the SDE firmware from Archos (http://forum.xda-developers.com/showthread.php?t=1653566). So far, so good, it runs quite nicely, all things concerned. Here's a screenshot to the system info: https://www.dropbox.com/s/0ri8n4jb6gyrfz7/Screenshot_2014-11-17-20-56-01.png?dl=0
Now I'm trying to install X-posed Framework, but this won't work. When I try, I get an error that tells me /system can't be mounted. (Screenshot: https://www.dropbox.com/s/ryaryqkie023sl4/Screenshot_2014-11-17-20-40-16.png?dl=0 )
When I take a look is ES3 if the folder is mounted, it looks like this: https://www.dropbox.com/s/4kwv0ja16qz52tq/Screenshot_2014-11-17-20-49-21.png?dl=0 . I can't tick the other boxes here, I get the message "sorry, operation failed" when I try.
I've already tried to use the "mount -o remount,rw /" command, to no avail...
I have no idea how I have to fix this problem and if it's even fixable.
Does anyone have any idea? Thanks in advance!
Same here...
No solution for that yet.
Before you type the mount command did you type "su" first (without the quotes)?
Just opening up terminal gives you regular user permissions which will not let you run the mount command. You need to become root/superuser first and that's what su does.
Yes I did ... Terminal emulator gives a notification that It's been granted superuser permission, but it still doesn 't Work.
Sent from my Ascend Y300 using XDA Free mobile app
Can you send a screenshot of the "mount" comand and response?
Did the prompt change from $ to #? What was the output of "mount"?
If terminal doesn't work try with superuser adb (allow superuser not only from applications, but from adb). Connect to the device with "adb shell" and issue this command.
Hi, thanks for your response. Here are two screenshots: the first is of the mount command in Terminal Emulator, the second of the same via abd shell. No results.
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Bor-ka said:
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Click to expand...
Click to collapse
1) I had 2.7 Experimental, so I uninstalled it and installed 2.6 Stable instead.
2) I do indeed use the "classical" option for installing Xposed.
3) Tried it, gave the following result: the file is created in /System/bin, so I guess /sytem is mounted okay. (see screenshots)
4) I use SuperSU, XPosed had root acces (see screenshot)
Seems to me /system is mounted fine, but Xposed just doesn't know it...
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Bor-ka said:
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Click to expand...
Click to collapse
Alright, did all of it.
1) Don't fully understand what is listed here, but in the first screenshot is the list of mounts.
2) Checked it, doesn't seem to exist, see second screenshot.
3) Logcat is attached.
Ok, it appears that I got the problem. Need a little time to think how to solve this.
The problem is rather technical. In newer androids supersu has isolated filesystem mounts for different processes.
It means that if you remount filesystem rw in one process, it (read-write-ness) is not accessible to the other process.
I have a little older cm10.2 build (for low-memory devices), perhaps, this was enforced later.
http://su.chainfire.eu/#how-mount (3.5)
So you're saying there's a good chance that if I install version 22_12_2013-13_29_20 (which i was planning anyway), instead of the latest one, the problem could be fixed?
Hmm, I installed the previous version of CM10.2, the problem seems to be persisting...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work. Seems I do have rw access to /system, but not with all apps...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work (permission denied). Seems I do have rw access to /system, but not with all apps...
Well, it seems like what I've said, filesystem mount encapsulation.
I've noticed one thing - you are using the standalone supersu application. And for me superuser mode is integrated in the system settings near the developer options. May be this is the case, internal superuser is patched already.
Alright, I'll uninstall superSU for now, give it a go with the built-in superuser app. I'll let you know!
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself.
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Bor-ka said:
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself..
Click to expand...
Click to collapse
Eureka! I re-installed CM, issued the mount-command i used earlier and installed X-posed! I used the built-in superuser app, no such problems as before. I did have to issue the mount-command, but that isn't a problem Is it normal I have to re-issue the mount-command each time I want to access /system rw?
Thanks a million! I can't believe it was something this trivial But I'm so glad it's solved, thanks!
Bor-ka said:
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Click to expand...
Click to collapse
I don't use the deepsleep-option. I do use Greenify to ensure certain apps (like Youtube or Chrome) aren't active in the background. Boot manager to be sure only essential apps boot in the first place. This seems to save me some battery life. Airplane mode as well.
I got this tablet from my dad because it was so slow he couldn't work with it. Even after factory reset, it very quickly became sluggish again. With CM, it feels like it's a new tablet. So no doubts about CM for me
I do have another issue: My pc won't show the tablet in explorer. I can access it via ADB, but I can't access the storage via explorer... I suppose I best start a new topic for that...
Glad the issue was solved. I wonder why the superuser application didn't work.. Deepsleep - it allowed the tablet to lose, say, 10-15% charge during a week sleep. Very handy if the tablet is used not often - really miss it.
Explorer connection - if I remeber correctly, you should go to settings -> storage (where the size of apps/pictures etc is shown). Then press the three dots in the upper right corner, select "usb computer connection" and select MTP.
P.S. I wonder also if CM12/Android 5.0 in the "development" section is worth a try...