Related
Note:
You can't install a pfx/p12 certification file which is not password protected, it is UNSAFE, android won't allow you do that
Please uninstall previous version first before install 0.9.0.
Due to Titanium Backup can't restore the permission to the keystore, if you are using Titanium Backup to backup/restore configurations, after a restore, please reconfigure your profile, repick the user certification to grant the permission to the keystore.
Features:
Compatible to all ICS device (NO ROOT REQUIRED, works on stock firmware)
Easy to use
Multiple VPN profile
Username/password authentication
Secure (Don't store your private key in App, but managed by Android system)
Open source
Limitation:
Only TUN mode, no TAP mode. (system API limitation)
One simultaneous connection only. (system API limitation)
ChangeLog:
5/02/2012 0.9.4
Fix redirect-gateway option
4/28/2012 0.9.3
Temporary fix tls-auth (Store tls key file in sdcard is insecure !!!)
Fix crash
4/27/2012 0.9.2
Add ns-cert-type option
Fix connection without user certification
4/25/2012 0.9.1
More error message
Fix extra arguments option
4/23/2012 0.9.0
Fix some crash
4/21/2012
Add username/password based authentication support. (Need to input password manually every time when connect)
Issues:
Connection interrupted if leave GUI while preparing/connecting. (It will be OK to leave once connected)
Won't work on JB, wait until google release openssl engine for system keystore
Screen Shots: Here
Download: Here
Source code: Here
Any feedback is welcome.
OpenVPN
Please don't retire this! people haven't stumbled on it but this is great!
The #1 reason most people root their phones even when they don't want to!
Thank you very much. I was using the one in cm7 and worked perfectly. Is there any plans to port it to cm9, this is the most missing feature for me in cm9. Thank you.
Waiting for password authentication.
Nice work anyway!
jcasares said:
Waiting for password authentication.
Nice work anyway!
Click to expand...
Click to collapse
Sure, I'm still working on it, it will be done soon. And I need to setup a test openvpn server first.
I can provide an OpenVPN connection (username and password) if required or it's too much work building a test server.
jcasares said:
I can provide an OpenVPN connection (username and password) if required or it's too much work building a test server.
Click to expand...
Click to collapse
I have already completed it, still thanks
Seems to be an issue with using the tls-auth option. It ignores the file even though the path is correct.
idmud said:
Seems to be an issue with using the tls-auth option. It ignores the file even though the path is correct.
Click to expand...
Click to collapse
I haven't test this feature before, maybe I should migrate this with the new keystore API.
can't select trusted CA
When I select my CA nothing changes so I'm not sure if it registers the certificate in the connection.
When I hit connect the icon flashes in the notification area and disappears.
I have tried the CA certificate in both .pem and .crt formats
Log says: No log.
Am running CM9 on AT&T Nexus S.
config request
Hi! Thanks for your great work!!!
Could you please add a simple checkbox in the connection settings to make the option "--ns-cert-type server" optional?
omriasta said:
When I select my CA nothing changes so I'm not sure if it registers the certificate in the connection.
When I hit connect the icon flashes in the notification area and disappears.
I have tried the CA certificate in both .pem and .crt formats
Log says: No log.
Am running CM9 on AT&T Nexus S.
Click to expand...
Click to collapse
Both .pem and .crt is pem format, where the content should be enclosed between "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----", you can use any text editor like notepad to check it.
I'll make the error message more verbose and accurate. Before that, can you use `adb logcat` to check if there is any error message ?
zealot0630 said:
Both .pem and .crt is pem format, where the content should be enclosed between "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----", you can use any text editor like notepad to check it.
I'll make the error message more verbose and accurate. Before that, can you use `adb logcat` to check if there is any error message ?
Click to expand...
Click to collapse
I know they are the same but for some reason the android store will only load .crt files.
The certificate begins and ends as mentioned.
I will try to run a logcat tomorrow.
Sent from my Nexus S using XDA
hamster79 said:
Hi! Thanks for your great work!!!
Could you please add a simple checkbox in the connection settings to make the option "--ns-cert-type server" optional?
Click to expand...
Click to collapse
I have fixed 'Extra arguments' option in 0.9.1, please update and you'll be able to specify custom options.
I have a working OpenVPN server with PCs and Android devices connecting to it.
Here is the situation with ICS.
I have installed this OpenVPN for a friend running ICS Midnote 3.3 for his Samsung Galaxy Note. Unfortunately, I can't get it to work, the logs does not display anything. It goes on stating its preparing and does not do anything else.
I tried forcing it to write any logs by supplying log /sdcard/openvpn/log.txt under the parameter section.
My currently VPN settings include.
Ca.crt, username and password. No keys are supplied.
To isolate things, I tried it with DroidVPN client, which works but is painstakingly slow.
You assistance is highly appreciated.
Thank you.
jaidee said:
I have a working OpenVPN server with PCs and Android devices connecting to it.
Here is the situation with ICS.
I have installed this OpenVPN for a friend running ICS Midnote 3.3 for his Samsung Galaxy Note. Unfortunately, I can't get it to work, the logs does not display anything. It goes on stating its preparing and does not do anything else.
I tried forcing it to write any logs by supplying log /sdcard/openvpn/log.txt under the parameter section.
My currently VPN settings include.
Ca.crt, username and password. No keys are supplied.
To isolate things, I tried it with DroidVPN client, which works but is painstakingly slow.
You assistance is highly appreciated.
Thank you.
Click to expand...
Click to collapse
Would you please try this one , see if it works
zealot0630 said:
Both .pem and .crt is pem format, where the content should be enclosed between "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----", you can use any text editor like notepad to check it.
I'll make the error message more verbose and accurate. Before that, can you use `adb logcat` to check if there is any error message ?
Click to expand...
Click to collapse
Double checked and there were a few characters before "begin certificate ". Removed them and the certificate loads(the app should ignore any text before/after those words). Still wouldn't connect and nothing in the log.
Just tried 0.9.2 and the log now says:
1335355150,D,MANAGEMENT: CMD 'state on all'
1335355150,D,MANAGEMENT: CMD 'hold release'
1335355150,D,MANAGEMENT: CMD 'username 'Auth' "xxxxxx"'
1335355150,D,MANAGEMENT: CMD 'password [...]'
Sent from my Nexus S using XDA
It seems that it doesn't work and I'm not clear about what the issue is. I'm using user+password authentication.
Code:
W/info.kghost.android.openvpn.OpenVpnService( 3856): Error generate pkcs12
W/info.kghost.android.openvpn.OpenVpnService( 3856): java.lang.NullPointerException: alias == null
W/info.kghost.android.openvpn.OpenVpnService( 3856): at android.security.KeyChain.getPrivateKey(KeyChain.java:291)
W/info.kghost.android.openvpn.OpenVpnService( 3856): at info.kghost.android.openvpn.OpenVpnService$Task.prepare(OpenVpnService.java:123)
W/info.kghost.android.openvpn.OpenVpnService( 3856): at info.kghost.android.openvpn.OpenVpnService$Task.doInBackground(OpenVpnService.java:313)
W/info.kghost.android.openvpn.OpenVpnService( 3856): at info.kghost.android.openvpn.OpenVpnService$Task.doInBackground(OpenVpnService.java:44)
W/info.kghost.android.openvpn.OpenVpnService( 3856): at android.os.AsyncTask$2.call(AsyncTask.java:264)
W/info.kghost.android.openvpn.OpenVpnService( 3856): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
W/info.kghost.android.openvpn.OpenVpnService( 3856): at java.util.concurrent.FutureTask.run(FutureTask.java:137)
W/info.kghost.android.openvpn.OpenVpnService( 3856): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
W/info.kghost.android.openvpn.OpenVpnService( 3856): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
W/info.kghost.android.openvpn.OpenVpnService( 3856): at java.lang.Thread.run(Thread.java:856)
D/dalvikvm( 2108): GC_CONCURRENT freed 433K, 28% free 10263K/14151K, paused 2ms+3ms
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): alias == null
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): java.lang.NullPointerException: alias == null
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): at android.security.KeyChain.getPrivateKey(KeyChain.java:291)
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): at info.kghost.android.openvpn.OpenVpnService$Task.prepare(OpenVpnService.java:123)
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): at info.kghost.android.openvpn.OpenVpnService$Task.doInBackground(OpenVpnService.java:313)
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): at info.kghost.android.openvpn.OpenVpnService$Task.doInBackground(OpenVpnService.java:44)
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): at android.os.AsyncTask$2.call(AsyncTask.java:264)
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): at java.util.concurrent.FutureTask.run(FutureTask.java:137)
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
F/info.kghost.android.openvpn.OpenVpnService$Task( 3856): at java.lang.Thread.run(Thread.java:856)
Maybe you know why the alias==null happens.
Seems there are still some problem when user certification is not set. I'll figure it out soon.
This is what I got now after installing the new version. The application doesn't stay in the notification bar as before and it seems there is no connection to the OpenVPN network.
Code:
D/PackageManager( 2000): New package installed in /mnt/asec/info.kghost.android.openvpn-1/pkg.apk
D/BackupManagerService( 2000): Received broadcast Intent { act=android.intent.action.PACKAGE_ADDED dat=package:info.kghost.android.openvpn flg=0x10000010 (has extras) }
I/ActivityManager( 2000): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=info.kghost.android.openvpn cmp=info.kghost.android.openvpn/.VpnSettings} from pid 12559
I/ActivityManager( 2000): Start proc info.kghost.android.openvpn for activity info.kghost.android.openvpn/.VpnSettings: pid=12965 uid=10087 gids={3003}
D/dalvikvm(12965): Trying to load lib /mnt/asec/info.kghost.android.openvpn-1/lib/libjni_openvpn.so 0x41357cc8
D/dalvikvm(12965): Added shared lib /mnt/asec/info.kghost.android.openvpn-1/lib/libjni_openvpn.so 0x41357cc8
D/dalvikvm(12965): No JNI_OnLoad found in /mnt/asec/info.kghost.android.openvpn-1/lib/libjni_openvpn.so 0x41357cc8, skipping init
I/ActivityManager( 2000): Displayed info.kghost.android.openvpn/.VpnSettings: +378ms
I/ActivityManager( 2000): START {cmp=info.kghost.android.openvpn/.VpnEditor (has extras)} from pid 12965
I/ActivityManager( 2000): Displayed info.kghost.android.openvpn/.VpnEditor: +263ms
I/info.kghost.android.openvpn.OpenVpnService$Task(12965): >INFO:OpenVPN Management Interface Version 1 -- type 'help' for more info
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: real-time echo notification set to ON
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: END
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: real-time log notification set to ON
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367061,I,OpenVPN 2.2.2 i686-pc-linux-gnu [SSL] [LZO2] [EPOLL] [eurephia] built on Apr 25 2012
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367061,,MANAGEMENT: unix domain socket listening on /data/data/info.kghost.android.openvpn/cache/manage
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367061,,Need hold release from management interface, waiting...
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367062,,MANAGEMENT: Client connected from /data/data/info.kghost.android.openvpn/cache/manage
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367062,D,MANAGEMENT: CMD 'echo on all'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367062,D,MANAGEMENT: CMD 'log on all'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: END
I/info.kghost.android.openvpn.OpenVpnService$Task(12965): >LOG:1335367062,D,MANAGEMENT: CMD 'state on all'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: real-time state notification set to ON
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367061,CONNECTING,,,
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: END
I/info.kghost.android.openvpn.OpenVpnService$Task(12965): >LOG:1335367062,D,MANAGEMENT: CMD 'hold release'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: hold release succeeded
I/info.kghost.android.openvpn.OpenVpnService$Task(12965): >LOG:1335367062,D,MANAGEMENT: CMD 'username 'Auth' "jcasares2"'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: 'Auth' username entered, but not yet verified
I/info.kghost.android.openvpn.OpenVpnService$Task(12965): >LOG:1335367062,D,MANAGEMENT: CMD 'password [...]'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: 'Auth' password entered, but not yet verified
I/ActivityManager( 2000): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=info.kghost.android.openvpn/.VpnSettings} from pid 2256
I/ActivityManager( 2000): Displayed info.kghost.android.openvpn/.VpnSettings: +205ms
I/info.kghost.android.openvpn.OpenVpnService$Task(12965): >INFO:OpenVPN Management Interface Version 1 -- type 'help' for more info
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: real-time echo notification set to ON
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: END
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: real-time log notification set to ON
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367167,I,OpenVPN 2.2.2 i686-pc-linux-gnu [SSL] [LZO2] [EPOLL] [eurephia] built on Apr 25 2012
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367167,,MANAGEMENT: unix domain socket listening on /data/data/info.kghost.android.openvpn/cache/manage
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367167,,Need hold release from management interface, waiting...
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367168,,MANAGEMENT: Client connected from /data/data/info.kghost.android.openvpn/cache/manage
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367168,D,MANAGEMENT: CMD 'echo on all'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367168,D,MANAGEMENT: CMD 'log on all'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: END
I/info.kghost.android.openvpn.OpenVpnService$Task(12965): >LOG:1335367168,D,MANAGEMENT: CMD 'state on all'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: real-time state notification set to ON
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: 1335367167,CONNECTING,,,
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: END
I/info.kghost.android.openvpn.OpenVpnService$Task(12965): >LOG:1335367168,D,MANAGEMENT: CMD 'hold release'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: hold release succeeded
I/info.kghost.android.openvpn.OpenVpnService$Task(12965): >LOG:1335367168,D,MANAGEMENT: CMD 'username 'Auth' "jcasares2"'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: 'Auth' username entered, but not yet verified
I/info.kghost.android.openvpn.OpenVpnService$Task(12965): >LOG:1335367168,D,MANAGEMENT: CMD 'password [...]'
W/info.kghost.android.openvpn.OpenVpnService$Task(12965): Unknown Command: SUCCESS: 'Auth' password entered, but not yet verified
My htc was off for one month because i went to a trip and did not take it with me. when i came back i turned it on and boom! bootloop! came from nowhere.
I had the vipers rom on it so i tried to update to the newest vipers rom but still bootloop. i tried to install different rom but nothing help,
At the end i installed RUU and still i'm in bootloop! please help me
amitshkuri said:
My htc was off for one month because i went to a trip and did not take it with me. when i came back i turned it on and boom! bootloop! came from nowhere.
I had the vipers rom on it so i tried to update to the newest vipers rom but still bootloop. i tried to install different rom but nothing help,
At the end i installed RUU and still i'm in bootloop! please help me
Click to expand...
Click to collapse
can you boot into bootloader?
if yes post all the on screen details
rzr86 said:
can you boot into bootloader?
if yes post all the on screen details
Click to expand...
Click to collapse
yes i can get into bootloader but in recovery i get error.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
JAN 13 2012, 17:33:34
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
amitshkuri said:
yes i can get into bootloader but in recovery i get error.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
JAN 13 2012, 17:33:34
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
from this guide it has 3 options to flash 4ext recovery(see step 1)
http://forum.xda-developers.com/showthread.php?t=1472298
after that go into recovery
format all partitions except sdcard
flash the rom
see if it boots
rzr86 said:
from this guide it has 3 options to flash 4ext recovery(see step 1)
http://forum.xda-developers.com/showthread.php?t=1472298
after that go into recovery
format all partitions except sdcard
flash the rom
see if it boots
Click to expand...
Click to collapse
i flashed 4ext recovery and flashed 3.33 firmware and flashed ARHD 7.2 (i did full wipe for all patitions)
still in bootloop but now it pass the HTC logo and the quitly brilliant logo and start the beats animation then it restart.
HI
GREETINGS
according to your bootloader you have stock htc hboot and
stock htc hboot does not go well with soff
flash the hboot in my attachment
to flash the hboot:-
1 put the file in root of sd card
2 reboot into bootloader
3 the bootloader will scan the file, follow on screen instruction
4 reboot back in to bootloader and make a clean installation of the rom as suggested by "RZR86"
shrex said:
HI
GREETINGS
according to your bootloader you have stock htc hboot and
stock htc hboot does not go well with soff
flash the hboot in my attachment
to flash the hboot:-
1 put the file in root of sd card
2 reboot into bootloader
3 the bootloader will scan the file, follow on screen instruction
4 reboot back in to bootloader and make a clean installation of the rom as suggested by "RZR86"
Click to expand...
Click to collapse
I flashed the new hboot and flashed the recovery again and made a clean installation including format for all partitions and still i stuck in this bootloop! what can i do more?
amitshkuri said:
what can i do more?
Click to expand...
Click to collapse
Absolutely loads of stuff. First thing is to get the logs.
Flash a rom with adb set in the default.prop in the boot image ramdisk ( CM for example )
while the device is bootlooping run
Code:
adb shell dmesg
which gives the kernel messages then you can run
Code:
adb logcat -b system -b radio -b events -b main
this will run forever, you'll notice it repeating the same messages over and over, look out for lines that start with "E/"
they're errors being reported and will lead you to the cause of you're bootloop
If either of these two fail then reboot into recovery and run
Code:
adb shell cat /dev/last_kmsg
This is a saved copy of dmsg from the last session.
Once you've got the logs you can easily pinpoint the cause of the problem all you got is read them
PROTIP: Look for the word error or fail or something similar
ok so that's all the errors i found while booting:
E/QC-NETMGR-LIB( 165): couldn't open file /sys/module/f_rmnet/parameters/rmnet_ctl_ch
E/QC-NETMGR-LIB( 165): couldn't open /sys/module/rmnet/parameters/rmnet_ctl_ch
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/DxDrmNexPlayerIntegrator( 169): ** Discretix Server loaded config file - result=0 **
E/DxDrmNexPlayerIntegrator( 169): ** Discretix SignalsListener Thread is starting **
E/DxSecureClock( 169): ** Discretix Clock Monitor is starting **
E/msm8660.gralloc( 153): DEBUG_CALC_FPS: 0
E/msm8660.gralloc( 153): period: 10
E/msm8660.gralloc( 153): ignorethresh_us: 500000
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 0
E/SurfaceFlinger( 153): composer device failed to initialize (Invalid argument)
E/rmt_storage( 120): Unable to open /boot/modem_fsg
E/rmt_storage( 120): Invalid rmt_storage client
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 1
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 2
E/HtcBootAnimation( 225): Could not find width.
E/HtcBootAnimation( 225): Could not find height.
E/HtcBootAnimation( 225): Could not find framerate.
E/HtcBootAnimation( 225): Could not find part1.
E/HtcBootAnimation( 225): Could not find part2.
E/HtcBootAnimation( 225): Could not find part3.
E/HtcBootAnimation( 225): sqlite3_open error, sqlite result: 14, errno: 2, No such file or directory
E/QC-DIAG_LSM( 156):
E/QC-DIAG_LSM( 156): Diag_LSM: Diag_LSM_Init: Failed to open handle to diag driver, error = 13
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 3
E/ExtendedExtractor( 156): Failed to open MM_PARSER_LIB, dlerror = Cannot load library: reloc_library[1290]: 156
E/AudioPolicyManagerBase( 156): Could not open support_receiver()
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 4
And this came at the second of crash:
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 5
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 6
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 7
am i in trouble?
amitshkuri said:
am i in trouble?
Click to expand...
Click to collapse
It's difficult to say with ONLY the errors LOL. You've just removed all the context of what was going on around leading upto it. Can you post the rest of them, not here though, pastebin or somewhere like that.
Also dmesg output would be pretty useful to see if all the drivers are install correctly.
At first glance, You seem to be missing some vital libraries. files, to say anything more at this point would just be guessing? but yeah, dmesg and a full logcat.
Actually to save a back and forth you can run the following commands
Code:
adb root
adb shell stop
adb shell dumpstate > state.txt
adb shell dumpsys > sys.txt
Don't know what you know so I'll explain what this does.
adb root , restarts adb as the root user
adb shell stop, this stops the servicemanager and it's child services , basically stop loading android. If you have a boot animation you should see it stop, this also stops device from rebooting as the next commands take some time to run.
dumpstate and dumpsys will dump your entire device contents to state.txt and sys.txt on your desktop machine. you won't see any output and they do take some time to run so please be patient. As you've fully formatted it I wouldn't expect any personal data to be present in those files but may contain device specific info please have a look before posting. searching the for things like your email address, name, IMEI, serial no's etc should help.
Then zip the files and attach them to this thread. Like I mentioned these files contain everything about the Device and the current state and will give us everything we need to figure out whats wrong.
If you're not comfortable "doing the dump!" ( sounds like a song ) then option 1 of logcat and dmesg should do I'll probably end up asking for more but meh!
ok i tried but
Code:
adb root
adb shell stop
didn't help and the boot restart again and again so i cannot write the rest of codes you gave me.
i attached a rar file with the context of logcat and dmesg.
amitshkuri said:
ok i tried but
Code:
adb root
adb shell stop
didn't help and the boot restart again and again so i cannot write the rest of codes you gave me.
i attached a rar file with the context of logcat and dmesg.
Click to expand...
Click to collapse
That's fine dmesg tells all in this case, It's a bit weird. you system partition seem to be at fault. these messages
Code:
<6>[ 2.457794] EXT4-fs (mmcblk0p22): INFO: recovery required on readonly filesystem
<6>[ 2.457977] EXT4-fs (mmcblk0p22): write access will be enabled during recovery
<6>[ 2.466827] EXT4-fs (mmcblk0p22): barriers disabled
<6>[ 2.468963] EXT4-fs (mmcblk0p22): recovery complete
<6>[ 2.476013] EXT4-fs (mmcblk0p22): mounted filesystem with writeback data mode. Opts: barrier=0
which is just information but a couple of lines down is this
Code:
<6>[ 3.588012] EXT4-fs (mmcblk0p22): re-mounted. Opts: noauto_da_alloc,barrier=0
Logcat also has this related message
Code:
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): The needs_recovery flag is set. Please run e2fsck before clearing
what it looks like is happening is the kernel has remounted your /system partition to try to set it up for recovery while the device is booting make system files unavailable in the process, which ties up to the messages about missing libraries from earlier on. it may well be easily solved simply by following the instruction and running e2fsck on /dev/block/mmcblk0p22, it worth a shot I'd say.
reboot into recovery and run
Code:
adb shell e2fsck /dev/block/mmcblk0p22
you may also have to remove the need_recovery flag from the partition... I don't know how to do that off the top of my head and I have to go out for a bit.... Google may be your friend
More Soon!
own diBeco
trevd said:
That's fine dmesg tells all in this case, It's a bit weird. you system partition seem to be at fault. these messages
Code:
<6>[ 2.457794] EXT4-fs (mmcblk0p22): INFO: recovery required on readonly filesystem
<6>[ 2.457977] EXT4-fs (mmcblk0p22): write access will be enabled during recovery
<6>[ 2.466827] EXT4-fs (mmcblk0p22): barriers disabled
<6>[ 2.468963] EXT4-fs (mmcblk0p22): recovery complete
<6>[ 2.476013] EXT4-fs (mmcblk0p22): mounted filesystem with writeback data mode. Opts: barrier=0
which is just information but a couple of lines down is this
Code:
<6>[ 3.588012] EXT4-fs (mmcblk0p22): re-mounted. Opts: noauto_da_alloc,barrier=0
Logcat also has this related message
Code:
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): The needs_recovery flag is set. Please run e2fsck before clearing
what it looks like is happening is the kernel has remounted your /system partition to try to set it up for recovery while the device is booting make system files unavailable in the process, which ties up to the messages about missing libraries from earlier on. it may well be easily solved simply by following the instruction and running e2fsck on /dev/block/mmcblk0p22, it worth a shot I'd say.
reboot into recovery and run
Code:
adb shell e2fsck /dev/block/mmcblk0p22
you may also have to remove the need_recovery flag from the partition... I don't know how to do that off the top of my head and I have to go out for a bit.... Google may be your friend
More Soon!
Click to expand...
Click to collapse
The shell e2fsck did not help, still in bootloop.
i searched in google about the need_recovery flag and i found one post that explain how to do this but in ubuntu linux
the command " debugfs " mentioned there, i dont really understand what to do.
amitshkuri said:
The shell e2fsck did not help, still in bootloop.
i searched in google about the need_recovery flag and i found one post that explain how to do this but in ubuntu linux
the command " debugfs " mentioned there, i dont really understand what to do.
Click to expand...
Click to collapse
hi again.
After reading some more e2fsck need some extra options. apologises for that
Also as is usually the case with these things you're not the first person to have this problem. A quick xda search for "The needs_recovery flag is set" brings up this post
I've just tested it because my cache partition has the needs_recovery flag set so I ran the commands in that post in recovery and it did clear the needs_recovery flag. so in your case you need to boot into recovery make sure /system is NOT mount which should be the default state and run the following commands
Code:
adb shell
tune2fs -l /dev/block/mmcblk0p22 | grep features
this command get the list of filesystem features it should look something like this ( order may be different )
Code:
Filesystem features: has_journal resize_inode filetype needs_recovery extent sparse_super large_file
Next we'll run e2fsck with the right command this time LOL
Code:
e2fsck -f /dev/block/mmcblk0p22
After that we can remove the old journal with tune2fs
Code:
tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p22
This should remove both the has_journal and needs_recovery flags from the feature list. Seeing as has_journal was set we'll turn it back on
Code:
tune2fs -O has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p22
Note the caret symbol ( ^ ) which is the difference between the above to commands. This controls whether a feature should be added or removed
Finally check the feature list again
Code:
tune2fs -l /dev/block/mmcblk0p22 | grep features
It should now look like this or something similar, If it still has needs_recovery in the list then something is wrong
Code:
Filesystem features: has_journal resize_inode filetype extent sparse_super large_file
All we need to do now is pray to the ghost of steve jobs and say the magic words
Code:
reboot
And hopefully we might have a win for you! :good:
when i write this line: e2fsck -f /dev/block/mmcblk0p22
i get this: Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>?
if i press "y" i get this: Inode 13765 is in use, but has dtime set. Fix<y>?
and more and more and more questions and cant continue with the next lines you gave me.
what to do?
amitshkuri said:
when i write this line: e2fsck -f /dev/block/mmcblk0p22
i get this: Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>?
if i press "y" i get this: Inode 13765 is in use, but has dtime set. Fix<y>?
and more and more and more questions and cant continue with the next lines you gave me.
what to do?
Click to expand...
Click to collapse
e2fsck -f -y /dev/block/mmcblk0p22
That will answer yes to all questions!
i did all exactly and still in a bootloop..
i got Filesystem features: has_journal resize_inode filetype extent sparse_super large_file
without the needs recovery, all went well.
is there hope?
amitshkuri said:
i did all exactly and still in a bootloop..
i got Filesystem features: has_journal resize_inode filetype extent sparse_super large_file
without the needs recovery, all went well.
is there hope?
Click to expand...
Click to collapse
Time to rinse and repeat, Grab the dmesg and the logcat and lets see what it's saying now? Also Have you tried reflashing the rom, it's possible the tune2fs has deleted some files but we can only find out by looking at the logs!
i tried now to reflashed and still bootloop :/
i attached the new demsg and logcat.
thank you for all the help!
amitshkuri said:
i tried now to reflashed and still bootloop :/
i attached the new demsg and logcat.
thank you for all the help!
Click to expand...
Click to collapse
Not a problem on the help. At least you bought an interesting problem to solve It's not your normal bootloop cause.
hmmm , It seems to have gone back to needs recovery.... Ok. Can you run the command from earlier but this time do not re-add the journal feature, so these commands
Code:
tune2fs -l /dev/block/mmcblk0p22 | grep features
e2fsck -f -y -v /dev/block/mmcblk0p22
tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p22
tune2fs -l /dev/block/mmcblk0p22 | grep features
#EDIT Mount as read only to mark it ready for mounting
mount -ro -text4 /dev/block/mmcblk0p22 /system
reboot
can you copy the output of these commands and post them up, I'm just curious to see what its runnning.
Do you know how to make your boot image insecure and how to mount /system with rw by default?
If not can you send me the boot image you're using an i'll fix it up.
The plan is to attempt the fs repair and remove journaling which from what I understand can be responsible for triggering the needs_recovery. should that not work, the kernel will try running recovery on the fs at boot time but this time it won't need to remount the /system partition because it will be already mounted as rw ... that's the theory at least.
If it fails send the logs and we'll have a look a some other options depending on the log out. But I wouldn't be worried there's still a couple of more things we can leverage to fixup the system partition.
hi all:
i download aosp kitkat4.4 source codes from google website. i compiled the code. i got the ROM.but when i flash the ROM to my device nexus 7(deb). it cannot boot.
from the log. i found that following error log. the sentence "couldn't find an OpenGL ES implementation" maybe cause the fatal question.
any advices is welcomed !
thank
brian
02-10 08:37:07.375: E/QCOMKeyMaster(17633): failed to load qseecom library
02-10 08:37:07.375: E/keystore(17633): could not open keymaster device in keystore (Operation not permitted)
02-10 08:37:07.375: E/keystore(17633): keystore keymaster could not be initialized; exiting
02-10 08:37:07.405: A/libEGL(17630): couldn't find an OpenGL ES implementation
02-10 08:37:07.405: A/libc(17630): Fatal signal 6 (SIGABRT) at 0x000044de (code=-6), thread 17630 (surfaceflinger)
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libacdbloader.so
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libcsd-client.so
02-10 08:37:07.575: E/MonoPipe(17632): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
Hi
I updated my Google Play services to latest and I have been getting this notification when I go to Internet wifi or mobile data.
authorization problem if the problem persists please log in and log out and try it again.
I do not want to make factory reset until CM12 comes out.
here is logcat
Code:
--------- beginning of /dev/log/main
--------- beginning of /dev/log/system
E/wpa_supplicant( 2513): wpa_driver_nl80211_driver_cmd: failed to issue private commands
E/WifiStateMachine( 794): Unexpected BatchedScanResults :null
E/wpa_supplicant( 2513): wpa_driver_nl80211_driver_cmd: failed to issue private commands
E/ConnectivityService( 794): Unexpected mtu value: [email protected]
E/PlayEventLogger( 3088): Invalid device id 9cb3889439509678
E/PhoneMonitor( 3153): onOtaspChanged old =0, new =3
E/AudioManagerAndroid( 3182): BLUETOOTH permission is missing!
E/AudioManagerAndroid( 3385): BLUETOOTH permission is missing!
F/ActivityManager( 794): Service ServiceRecord{42866038 u0 com.google.android.music/.net.NetworkMonitor} in process ProcessRecord{42e61648 3088:com.google.android.music:main/u0a65} not same as in map: null
F/ActivityManager( 794): Service ServiceRecord{427a3950 u0 com.google.android.music/.preferences.MusicPreferenceService$MusicPreferenceServiceBinder} in process ProcessRecord{42e61648 3088:com.google.android.music:main/u0a65} not same as in map: null
E/AuthorizationBluetoothService( 1571): Proximity feature is not enabled.
E/GCoreFlp( 1608): Bound FusedProviderService with LocationManager
E/AudioManagerAndroid( 3758): BLUETOOTH permission is missing!
E/dalvikvm( 3798): Could not find class 'android.app.Notification$Action$Builder', referenced from method f.a
E/dalvikvm( 3798): Could not find class 'android.app.RemoteInput[]', referenced from method f.a
E/SQLiteLog( 3798): (1) no such table: mmsconfig
E/Babel ( 3798): canonicalizeMccMnc: invalid mccmnc nullnull
P.S: I have removed google play services and updated it back still this problem is there. Then when I change my language to English notification stays in my language
EDIT: It is pure stock no Root or anything!
Same error
I have the same error "PlayEventLogger( 3088): Invalid device id" on my Moto G 1st gen
All of a sudden, on Stock + Root TF700T, WiFi won't turn on. I highly doubt that this is related to my WiFi router ... the WiFi won't even enable on the tablet, and I can't even see a MAC address in About Tablet section.
I also did some digging and have some additional detail, but I cannot find a solution.
logcat:
Code:
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '43 softap fwreload wlan0 STA' failed with '400 43 Softap operation failed (No such file or directory)'
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2767): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2767): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2767): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2767): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 3ms+3ms, total 57ms
D/AsusBrightnessManager( 489): br transform : 35 -> 13
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '46 softap fwreload wlan0 STA' failed with '400 46 Softap operation failed (No such file or directory)'
E/WifiStateMachine( 489): Failed 6 times to start supplicant, unload driver
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '48 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 48 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2792): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2792): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2792): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2792): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 2ms+1ms, total 22ms
W/NvCpuClient( 489): Failed to bind to service
D/AsusBrightnessManager( 489): br transform : 35 -> 13
E/WifiHW ( 489): Supplicant not running, cannot connect
W/NvCpuClient( 489): Failed to bind to service
Also, output from netcfg:
Code:
[email protected]:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
dummy0 DOWN 0.0.0.0/0 0x00000082 76:ad:93:6b:c9:b7
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
And here is output of my wpa_supplicant.conf:
Code:
[email protected]:/ # cat /etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
And I searched the entire filesystem for "nl80211" and found nothing.
Does anyone have suggestions on where to go next? Did my driver somehow get deleted, or am I just not looking for the right thing?
Thanks.
I will use this question in the future as an example of how to ask for support properly. Unfortunately I don't have a solution for you, but you could check the files in your /data/misc/wifi, maybe you can find something unusual. Your MAC address should come from some file on the FAT filesystem on /dev/block/mmcblk0p5 - I'd recommend making an image of it as a backup and then analyze the image.
_that said:
I will use this question in the future as an example of how to ask for support properly.
Click to expand...
Click to collapse
I provide Enterprise-level support to software devs working in the Cloud and particularly on CentOS/RHEL Linux servers. This is why I know how to ask for help properly.
Well, since I can't find much, and there aren't any definitive answers here, my next thoughts are:
1) Something is seriously jacked up on the filesystem, possibly corrupted driver, possibly something worse. Hopefully, this is the case, because a software problem is possible to fix.
2) The WiFi radio is permanently damaged, or "burnt out".
In the hopes that it's something more like software, I'm going to reimage. I just need to decide what ROM to use. Not having network connectivity will make the prep for this a bit more challenging, but I can work through it using a MicroSD card.
If it's #2, well then I suppose I will have wasted my time reimaging and will be on the market for a new tablet ... and I need to get on that right away because I need to travel soon. Any suggestions are welcome ... I'd like a 9" or 10" tablet and it must have an HDMI out (micro preferred) and be able to handle 1080p video.
Thanks.
[SOLVED]
I am having a heckuva time even doing what I described above.
-I had never unlocked the bootloader before, so when I tried the ASUS unlock util v8, it gave error "INSTALL_FAILED_SHARED_USER_INCOMPATIBLE"
-I tried the ASUS unlock tool v7, and was finally able to install it but when I run and select Unlock I get an error that there is no network connection (FFS that's what I'm trying to resolve!)
-I can't get into recovery, I just get the Android guy with "ERROR!" when I enter fastboot and select "RCK".
My only option is to go back to Stock. So, I tried this:
http://forum.xda-developers.com/showthread.php?t=1833212
The steps in that post result in the same Android guy with the "ERROR!" screen ... not a very helpful error msg.
So, I tried this, and used the stock firmware from ASUS. (NOTE: I downloaded "ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)" directly from ASUS after I read their notes on where to check for which one you need ([Settings]-->[About tablet]-->Build number).):
http://www.transformerforums.com/fo...e-firmware-tf700-tf701-tf300-tf101-tf201.html
From that post ^^ I did Method B: Flash from MicroSD. I extracted the .zip I downloaded from ASUS, and renamed the new zip EP201_768_SDUPDATE.zip per the GUIDE linked above.
I put in my MicroSD, went back into fastboot, and selected "RCK". It was at this point that I began typing the above. Total time to get to this point was about 90 minutes!
-----
FINALLY, for the first time, I saw a progress bar under the Android guy, and he had gears turning in his belly.
*INSERT SIGH OF RELIEF HERE*
As I was typing out all the above, progress bars were moving, and a few reboots happened. I expected that I would be fully back on Stock ROM, and that my data would have been wiped. I never ran a data wipe, I just assumed the ASUS installer would do that by default.
Well, it didn't wipe data. But, what it did do: restore all my device drivers!! After about 10 minutes, and 2-3 reboots, Android loaded with my existing desktop and settings, and the WiFi connected right away!!
So, this fixed it. I documented the above so anyone (even me, months from now) having a similar problem might be able to use these steps.
WOO HOO!
lost root
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.
CaptainRewind said:
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.
Click to expand...
Click to collapse
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
sbdags said:
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Click to expand...
Click to collapse
Yep, I had to do that anyway because I wanted to do a full Titanium Backup first. Still, I'm moving to CM now.