Related
So, I'm writing this post so that there is a unified "thing" for G2X and Linux. I just did this on mine, with information from a bunch of different places, so I'd like to make it easier some people (doing it with a guest Windows machine is not fun).
Thanks to jnichols595, and others.
The procedure itself is painless and quick. For me, everything worked from the first time.
1. ROOTING
* download http://forum.xda-developers.com/attachment.php?attachmentid=577906&d=1303754302
* extract it so it is a folder and cd into it with terminal.
* run the following 1 command:
Code:
$ [B]sudo ./root.command[/B]
There appears to be a permissions problem accessing your device
Press Y to try running adb with sudo or any other key to quit: Y
Checking for connected device...
Pushing temporary root exploint (psneuter) to device...
2635 KB/s (585731 bytes in 0.565s)
Running psneuter on device...
property service neutered.
killing adbd. (should restart in a second or two)
Waiting for device...
Remounting /system read/write...
remount succeeded
Pushing su to /system/bin/su...
580 KB/s (26324 bytes in 0.044s)
Pushing busybox to /system/bin/busybox...
1273 KB/s (1062992 bytes in 0.815s)
Installing Superuser.apk android application...
1134 KB/s (196521 bytes in 0.169s)
Removing psneuter from device...
Rebooting device...
Once device has rebooted you should be rooted.
Press Enter when you're ready to quit:
Done, rooted. How do you know? There should be a Pirate's icon in your app menu.
2. INSTALLING CLOCKWORKMOD
* get the nvflash scripts from http://mirror.dal.tdrevolution.net/ctso/g2x/nvflash-recovery.tgz and extract the folder.
* go into the folder and put http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.7-p999.img in there
* open flash-recovery.sh in that same folder with a text editor and modify the line to say
Code:
sudo ./nvflash --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-clockwork-3.0.2.7-p999.img
* now open terminal and cd into the folder
* remove the battery on the phone, and plug the cable while holding both VolUp and VolDown keys. Hold like that for 5sec and let go
* in the terminal you opened, execute the commans
Code:
lsusb
to make sure you see something like this:
Code:
Bus 002 Device 008: ID 0955:7f20 NVidia Corp.
* immediately after that, execute the script
Code:
./flash-recovery.sh
this is what I had
Code:
[email protected]:~/Desktop/nvflash$ [B]lsusb[/B]
Bus 003 Device 014: ID 0955:7f20 NVidia Corp.
Bus 003 Device 005: ID 046d:c526 Logitech, Inc. Nano Receiver
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 021: ID 0489:e00f Foxconn / Hon Hai
Bus 001 Device 009: ID 064e:2100 Suyin Corp.
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~/Desktop/nvflash$ [B]./flash-recovery.sh[/B]
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x038891c443c145d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: recovery-clockwork-3.0.2.7-p999.img
\ 4308992/4308992 bytes sent
recovery-clockwork-3.0.2.7-p999.img sent successfully
[email protected]:~/Desktop/nvflash$
* as soon as some image appears on your phone saying it's updating, you can unplug the phone
Awesome we have the recovery now.
3. Installing the Custom ROM
This one is a video. It is done on a mac, but the computer system does not matter at this point. You just download it to your computer, and then put the zip on the SD card. Use Up/Down to move and Power to select when in recovery mode. This is the guide: http://theunlockr.com/2011/05/03/how-to-load-a-custom-rom-on-the-t-mobile-g2x/
Awesome. Now you can flash ROMs on your device.
***Credits and thanks go to the developers who came up with this, I just put it together!
aplsux said:
So, I'm writing this post so that there is a unified "thing" for G2X and Linux. I just did this on mine, with information from a bunch of different places, so I'd like to make it easier some people (doing it with a guest Windows machine is not fun).
Thanks to jnichols595, and others.
The procedure itself is painless and quick. For me, everything worked from the first time.
1. ROOTING
* download http://forum.xda-developers.com/attachment.php?attachmentid=577906&d=1303754302
* extract it so it is a folder and cd into it with terminal.
* run the following 1 command:
Code:
$ [B]sudo ./root.command[/B]
There appears to be a permissions problem accessing your device
Press Y to try running adb with sudo or any other key to quit: Y
Checking for connected device...
Pushing temporary root exploint (psneuter) to device...
2635 KB/s (585731 bytes in 0.565s)
Running psneuter on device...
property service neutered.
killing adbd. (should restart in a second or two)
Waiting for device...
Remounting /system read/write...
remount succeeded
Pushing su to /system/bin/su...
580 KB/s (26324 bytes in 0.044s)
Pushing busybox to /system/bin/busybox...
1273 KB/s (1062992 bytes in 0.815s)
Installing Superuser.apk android application...
1134 KB/s (196521 bytes in 0.169s)
Removing psneuter from device...
Rebooting device...
Once device has rebooted you should be rooted.
Press Enter when you're ready to quit:
Done, rooted. How do you know? There should be a Pirate's icon in your app menu.
2. INSTALLING CLOCKWORKMOD
* get the nvflash scripts from http://mirror.dal.tdrevolution.net/ctso/g2x/nvflash-recovery.tgz and extract the folder.
* go into the folder and put http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.7-p999.img in there
* open flash-recovery.sh in that same folder with a text editor and modify the line to say
Code:
sudo ./nvflash --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-clockwork-3.0.2.7-p999.img
* now open terminal and cd into the folder
* remove the battery on the phone, and plug the cable while holding both VolUp and VolDown keys. Hold like that for 5sec and let go
* in the terminal you opened, execute the commans
Code:
lsusb
to make sure you see something like this:
Code:
Bus 002 Device 008: ID 0955:7f20 NVidia Corp.
* immediately after that, execute the script
Code:
./flash-recovery.sh
this is what I had
Code:
[email protected]:~/Desktop/nvflash$ [B]lsusb[/B]
Bus 003 Device 014: ID 0955:7f20 NVidia Corp.
Bus 003 Device 005: ID 046d:c526 Logitech, Inc. Nano Receiver
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 021: ID 0489:e00f Foxconn / Hon Hai
Bus 001 Device 009: ID 064e:2100 Suyin Corp.
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~/Desktop/nvflash$ [B]./flash-recovery.sh[/B]
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x038891c443c145d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: recovery-clockwork-3.0.2.7-p999.img
\ 4308992/4308992 bytes sent
recovery-clockwork-3.0.2.7-p999.img sent successfully
[email protected]:~/Desktop/nvflash$
* as soon as some image appears on your phone saying it's updating, you can unplug the phone
Awesome we have the recovery now.
3. Installing the Custom ROM
This one is a video. It is done on a mac, but the computer system does not matter at this point. You just download it to your computer, and then put the zip on the SD card. Use Up/Down to move and Power to select when in recovery mode. This is the guide: http://theunlockr.com/2011/05/03/how-to-load-a-custom-rom-on-the-t-mobile-g2x/
Awesome. Now you can flash ROMs on your device.
***Credits and thanks go to the developers who came up with this, I just put it together!
Click to expand...
Click to collapse
With the G2X as long as you get clockworkmod recovery on your phone you can flash any compatible rom. No need to root first.
And if you do want to root your existing rom, just get clockworkmod on your phone and then flash the root zip file that jboxer has posted in the development section. It issues the commands and installs su and superuser.apk for you, and sets the proper permissions for those files.
phburks said:
With the G2X as long as you get clockworkmod recovery on your phone you can flash any compatible rom. No need to root first.
Click to expand...
Click to collapse
Yes, as long as you are going to a custom ROM. However, if you don't want the whole thing, i.e. just root - easier and quicker.
phburks said:
And if you do want to root your existing rom, just get clockworkmod on your phone and then flash the root zip file that jboxer has posted in the development section. It issues the commands and installs su and superuser.apk for you, and sets the proper permissions for those files.
Click to expand...
Click to collapse
Awesome!
aplsux said:
Yes, as long as you are going to a custom ROM. However, if you don't want the whole thing, i.e. just root - easier and quicker.
Awesome!
Click to expand...
Click to collapse
Notice that that zip doesn't install busybox but it can be easily installed from the Market once you have root access.
Here's a link to the thread.
http://forum.xda-developers.com/showthread.php?t=1255214
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
A while ago I received a free Wave S8500 running Bada 1.2. Since this OS was pretty awful I decided to upgrade having done the process before on another phone of the same model. Unfortunately I was stupid and managed to flash the wrong files so my phone ended up in a boot loop. I found the correct set of files and tried to flash them but Multiloader only works up to SHP APP, at this point it fails with a "serial port open error". When I try and boot the phone I reach a blue screen full of the following debugging information:
Page: 1/2 <Pic #>
S/W version: S8500+XP+KJ1
Modem: Q6270B-KPRBL-1.5.45T
SHP: VPP R5 2.1.1
Build Host:s1-AGENT08
BuildAt:2011/10/05 22:44:23
App Debug Level l: 0
ASSERTION_REQUIRE:m_hLib != IN
VALID_HOBJ failed/ (file WinLibDllMgr.cpp, line 40)
Cannot load (shpWindow)
<Callstack information>
PC = 40318BEF OemDumpRegister
LR = 403118 OemDumpRegister
<Running Task(InvalidTask) Call stack>
_SysAssertReport
GWES:WinLib::CDI I Mgr::LoadLibrary
WinLibDllProxyInit
WinLibDispatch
OemBmPrelnitMochaTask
mochaTaskPreInit
Page: 2/2 <* #>
All HW Information:
HW VERSION: S8500_REV07
IMEI VERSION: Not Active
RF CAL DATE: Not Active
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = 2, Current BMPs = 0
Nucleus Task Information:
Running Task name = SHP_PRE SI
ices = 00000000
Wait = 00000000
Signal = 00000000
Priority = 0
To exit
Press 0 for 2sec
After pressing the home key it goes to a screen I've never previously seen with yellow text stating "UPLOAD to pc". Clearly the phone has a problem with the SHP_APP file and the Windows system it's connected to but beyond that I'm completely out of my depth. Can somebody shed some light on what is wrong with my phone and how I might go about fixing it?
Thanks in advance.
Hello,
I installed EFS pro, all *seems* okay, phone is found, etc etc, messages say That things are going fine, unless the end:
Checking device connection... Device is connected!
Checking for block device: '/dev/block/mmcblk0'... Okay.
Extracting PIT from device for mapping... Skipped, already exists.
Checking backup folder location... Okay.
Backing up selected partition(s)...
EFS - read: /dev/block/mmcblk0p3 - write: efs.img... Okay.
20971520 bytes transferred in 0.648 secs (32363456 bytes/sec)
Creating archive: GT-I9300_20140813_011925.tar.gz... Okay.
Copying: GT-I9300_20140813_011925.tar.gz to PC storage... Okay.
Copied: remote object '/storage/extSdCard/EFSProBackup/GT-I9300_20140813_011925.tar.gz' does not exist
Cleaning up temporary files... Okay.
Operation successful!
And in fact the file GT-I9300_20140813_011925.tar.gz is not present anywhere neither on the phone nor on the PC.
I run EFS from the Win7 "My documents" folder, "as an administrator"...
Param on the phone for storage location is "/storage/extSdCard". I find the folder On the phone, EFS created a sub directory "/storage/extSdCard/EFSProBackup" but there is nothing inside...
Any suggestion?
Thank you
PS: Device info:
---------- Hardware Information ----------
Connected Device SN.: [REMOVED]
Device Manufacturer: SAMSUNG
Device Model: GT-I9300
Product Code: GT-I9300RWDXEO
Hardware Version: MP 1.100
---------- Firmware Information ----------
PDA Version: I9300XXUGNA5
Baseband Version: I9300XXUGNA8
CSC Version: I9300XEOGNC1
---------- Software Information ----------
Kernel Release: 3.0.31-2429075
Kernel Version: #1 SMP PREEMPT Thu Jan 16 23:47:54 KST 2014
ROM Build: m0xx-user 4.3 JSS15J I9300XXUGNA5 release-keys
Android Version: 4.3
BusyBox Version: 1.20.2-cm9
SU Binary Version: 2.00:SUPERSU
Nobody?
Ruzakuku said:
Hello,
I installed EFS pro, all *seems* okay, phone is found, etc etc, messages say That things are going fine, unless the end:
Checking device connection... Device is connected!
Checking for block device: '/dev/block/mmcblk0'... Okay.
Extracting PIT from device for mapping... Skipped, already exists.
Checking backup folder location... Okay.
Backing up selected partition(s)...
EFS - read: /dev/block/mmcblk0p3 - write: efs.img... Okay.
20971520 bytes transferred in 0.648 secs (32363456 bytes/sec)
Creating archive: GT-I9300_20140813_011925.tar.gz... Okay.
Copying: GT-I9300_20140813_011925.tar.gz to PC storage... Okay.
Copied: remote object '/storage/extSdCard/EFSProBackup/GT-I9300_20140813_011925.tar.gz' does not exist
Cleaning up temporary files... Okay.
Operation successful!
And in fact the file GT-I9300_20140813_011925.tar.gz is not present anywhere neither on the phone nor on the PC.
I run EFS from the Win7 "My documents" folder, "as an administrator"...
Param on the phone for storage location is "/storage/extSdCard". I find the folder On the phone, EFS created a sub directory "/storage/extSdCard/EFSProBackup" but there is nothing inside...
Any suggestion?
Thank you
PS: Device info:
---------- Hardware Information ----------
Connected Device SN.: [REMOVED]
Device Manufacturer: SAMSUNG
Device Model: GT-I9300
Product Code: GT-I9300RWDXEO
Hardware Version: MP 1.100
---------- Firmware Information ----------
PDA Version: I9300XXUGNA5
Baseband Version: I9300XXUGNA8
CSC Version: I9300XEOGNC1
---------- Software Information ----------
Kernel Release: 3.0.31-2429075
Kernel Version: #1 SMP PREEMPT Thu Jan 16 23:47:54 KST 2014
ROM Build: m0xx-user 4.3 JSS15J I9300XXUGNA5 release-keys
Android Version: 4.3
BusyBox Version: 1.20.2-cm9
SU Binary Version: 2.00:SUPERSU
Click to expand...
Click to collapse
I'm having a similar problem.....
I'm a noob so I really need some help. I have a sgs3 1747m from Canada. The phone is rooted (I followed xda CF method)
I wanted to back up the efs folder so I also followed the instructions on xda. (downloaded busybox and efs pro) Phone connects Everything says okay. The problems starts when I have to choose the device filter. I select sgs3 US - operation failed but then I thought the phone is from Canada so I tried a couple other selections all say operation failed. In addition, there are no partitions, files or folders shown for me to select to back up. Have I done something wrong? Does efs pro not work with my phone?
ATTENTION:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, the expulsion of some contestant at the Spanish version of Got Talent,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
THIS WILL WIPE ENTIRELY YOUR DEVICE. YOU WILL NEED TO CHANGE THE FILE SYSTEM OF /DATA TO EXT4 FROM F2FS IN TWRP BEFORE ANYTHING ELSE. AND, IT IS A MUST REQUIREMENT DOING A NANDROID OF YOUR CURRENT ROM WITH TWRP: TWRP Home >> Wipe >> Advanced Wipe >> tick data >> Repair or Change File System >> Change File System >> EXT4 >> Swipe to change.
UPDATE 22/07/2021: It has been discovered that some American surnia units (with model code XT1526 and XT1527, sold on Sprint and AT&T carriers) have different partition table than the European or Global versions (XT1521 and XT 1524). Sprint and AT&T surnia models are NOT COMPATIBLE with UBPorts, and trying to do this steps will cause a bootloop (easily fixable with a reflashing of LineageOS/stock ROM).
Hello. I'm a developer from Spain and I'm doing a porting work on my Moto E 2015 in Halium and Ubuntu Touch, and I'm looking for testers with surnia (CAUTION: ONLY surnia is allowed in this, NOT otus, sorry for this, I don't have otus) for testing this compilated version of Halium and Ubuntu Touch, because I'm having trouble with the port (rootfs not flashing on /data properly). I have some instructions to test this, and files to download and test on a real device.
-INSTRUCTIONS (only with Ubuntu Linux):
1-Download halium-boot (https://mega.nz/file/6TRRgAAa#YjtJ35nXxIMS_tVyaURRHuJfvjx3mxLFY1H6WWzD_Z4). Boot in Recovery Mode and flash with:
Code:
fastboot flash boot /path-to the image of halium-boot/halium-boot.img
2-Download system.img and halium-install.zip
https://mega.nz/file/GXBVAQyA#w68fYNKZ3He4Zg69QC9bkvQI8702ZAho4M4TVmKdfxg
https://github.com/JBBgameich/halium-install/archive/master.zip
Uncompress halium-install.zip and get into the folder via Terminal.
3-Download the latest rootfs from UBPorts:
https://ci.ubports.com/job/xenial-r.../out/ubports-touch.rootfs-xenial-armhf.tar.gz
4-Boot into TWRP recovery (or your recovery with BusyBox) and run this command (in the folder halium-install):
Code:
halium-install.sh -p ut -v path/to/rootfs.tar.gz path/to/system.img
Put a password that you can remember when prompted.
Wait, and it should flash all succesfully, if all goes well. I do not guarantee the success in this (my device has a problem with /data partition), so I need all the feedback possible in this (Terminal logs, for example, would be useful to me).
5-Reboot. Now, it should be the phone on Bootloader screen, but if you text in a terminal
Code:
ssh [email protected]
It should ask for a password and load the rootfs successfully.
After that, with this settings:
Code:
sudo mount -o remount,rw /
and
Code:
sudo -i # And enter your password
cat /var/lib/lxc/android/rootfs/ueventd*.rc|grep ^/dev|sed -e 's/^/dev///'|awk '{printf "ACTION=="add", KERNEL=="%s", OWNER="%s", GROUP="%s", MODE="%s"n",$1,$3,$4,$2}' | sed -e 's/r//' >/usr/lib/lxc-android-config/70-[codename].rules
and, finally, rebooting the phone, it should boot Ubuntu Touch. The lock password is the same than the password you made before in the install.
I need feedback to do this well. Any comments on this will be welcomed.
Logo of the project licensed by UBPorts by Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) License.
XDA:DevDB Information
Ubuntu Touch Porting: Motorola Moto E 2015 4G/LTE, ROM for the Moto E 2015
Contributors
impreza233, bartbart2003
Source Code: https://github.com/Halium/projectmanagement/issues/97
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked bootloader, latest TWRP or custom recovery with BusyBox installed
Version Information
Status: Alpha
Created 2018-09-29
Last Updated 2020-09-20
Great job!
Buen trabajo! Quizás lo testee más tarde, cuando esté seguro de que no necesitaré el celular para algo importante jajajaj.
~~
For English readers:
Great job! I may test it later, when I'm sure I won't be needing the phone for something important haha.
impreza233 said:
4-Boot into TWRP recovery (or your recovery with BusyBox) and run this command (in the folder halium-install):
Code:
halium-install-standalone.sh -p ut -v path/to/rootfs.tar.gz path/to/system.img
Click to expand...
Click to collapse
The file halium-install-standalone.sh is not existant. Tried using halium-install and /utils/standalone.sh, but both are giving me a "Permission denied" dialog. SU not found, using Squid's TWRP.
SonicoXD said:
The file halium-install-standalone.sh is not existant. Tried using halium-install and /utils/standalone.sh, but both are giving me a "Permission denied" dialog. SU not found, using Squid's TWRP.
Click to expand...
Click to collapse
Yes, it's a little fail on my install tutorial. The file is named halium-install.sh. utils/standalone.sh won't do nothing. I will fix this error in the tutorial. Thanks for the tip!!!
Otherwise, what version of Squid's TWRP do you use? I use the latest version from here: https://eu.dl.twrp.me/surnia/ and no problems on my side. I will investigate this too.
EDIT: fixed error on the install tutorial.
sh:halium-install.sh not found (twrp 3.2.3)
Android-fan117 said:
sh:halium-install.sh not found (twrp 3.2.3)
Click to expand...
Click to collapse
If you are inside the folder of halium-install.sh, when you have to type the command halium-install.sh, drag and drop the .sh file to the terminal, in this way:
path/to/halium-install.sh -p ut -v path/to/rootfs.tar.gz path/to/system.img
EDIT: fixed on the main tutorial.
ok... all flashed just fine,but ssh [email protected] gives Connection timed out (new network connection appears,when phone boots).I just can`t connect.
Android-fan117 said:
ok... all flashed just fine,but ssh [email protected] gives Connection timed out (new network connection appears,when phone boots).I just can`t connect.
Click to expand...
Click to collapse
Well, this is a good signal
What do you get if you do this command?:
Code:
ssh -vvvv [email protected]
I need to know that messages to debug this.
impreza233 said:
Well, this is a good signal
What do you get if you do this command?:
Code:
ssh -vvvv [email protected]
I need to know that messages to debug this.
Click to expand...
Click to collapse
I get this:
openSSH_7.2p2 Ubuntu-4ubuntu2.4, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "10.15.19.82" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 10.15.19.82 [10.15.19.82] port 22.
debug1: connect to address 10.15.19.82 port 22: Connection timed out
ssh: connect to host 10.15.19.82 port 22: Connection timed out
(But new network connection appears)
ALSO I saw some errors while installing:
I: Pushing rootfs and android image to /data via ADB
5528 KB/s (2147483648 bytes in 379.315s)
5243 KB/s (1895825408 bytes in 353.069s)
Installing udev rules
cannot stat './file/70-tenshi.rules': No such file or directory
cannot stat './file/70-tenshi.rules': No such file or directory
cannot stat './file/70-tenshi.rules': No such file or directory
Android-fan117 said:
I get this:
openSSH_7.2p2 Ubuntu-4ubuntu2.4, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "10.15.19.82" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 10.15.19.82 [10.15.19.82] port 22.
debug1: connect to address 10.15.19.82 port 22: Connection timed out
ssh: connect to host 10.15.19.82 port 22: Connection timed out
(But new network connection appears)
ALSO I saw some errors while installing:
I: Pushing rootfs and android image to /data via ADB
5528 KB/s (2147483648 bytes in 379.315s)
5243 KB/s (1895825408 bytes in 353.069s)
Installing udev rules
cannot stat './file/70-tenshi.rules': No such file or directory
cannot stat './file/70-tenshi.rules': No such file or directory
cannot stat './file/70-tenshi.rules': No such file or directory
Click to expand...
Click to collapse
Well, it means that the flashing of rootfs has been sucessful. Yipeee!!!! Well, the tenshi thing will be removed in future versions of the script. It was here only for debugging purposes.
For the ssh thing, I will provide a patch for that. Thanks again for your feedback!!!
impreza233 said:
Well, it means that the flashing of rootfs has been sucessful. Yipeee!!!! Well, the tenshi thing will be removed in future versions of the script. It was here only for debugging purposes.
For the ssh thing, I will provide a patch for that. Thanks again for your feedback!!!
Click to expand...
Click to collapse
Ok. Just let me know,when all be done. I'll test it again.
Android-fan117 said:
Ok. Just let me know,when all be done. I'll test it again.
Click to expand...
Click to collapse
Thanks for being the test case!
Android-fan117 said:
Ok. Just let me know,when all be done. I'll test it again.
Click to expand...
Click to collapse
Well, I have news. When you finish the halium-install process unpack and run the file attached to this message and remember to run the command to cancel previous connection with 10.15.19.82 in case of your ssh needs to. At that point it should be a connection to ssh.
impreza233 said:
Well, I have news. When you finish the halium-install process unpack and run the file attached to this message and remember to run the command to cancel previous connection with 10.15.19.82 in case of your ssh needs to. At that point it should be a connection to ssh.
Click to expand...
Click to collapse
get this(when run ssh_connection.sh):
* The device seems to be connected as enp0s20u7
RTNETLINK answers: File exists
RTNETLINK answers: File exists
PING 10.15.19.82 (10.15.19.82) 56(84) bytes of data.
From 192.168.2.89 icmp_seq=1 Destination Host Unreachable
From 192.168.2.89 icmp_seq=2 Destination Host Unreachable
From 192.168.2.89 icmp_seq=3 Destination Host Unreachable
--- 10.15.19.82 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2038ms
pipe 3
* Connecting using ssh
OpenSSH_7.2p2 Ubuntu-4ubuntu2.5, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 10.15.19.82 [10.15.19.82] port 22.
debug1: connect to address 10.15.19.82 port 22: No route to host
ssh: connect to host 10.15.19.82 port 22: No route to host
Android-fan117 said:
get this(when run ssh_connection.sh):
* The device seems to be connected as enp0s20u7
PING 10.15.19.82 (10.15.19.82) 56(84) bytes of data.
From 192.168.2.63 icmp_seq=1 Destination Host Unreachable
From 192.168.2.63 icmp_seq=2 Destination Host Unreachable
From 192.168.2.63 icmp_seq=3 Destination Host Unreachable
--- 10.15.19.82 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2052ms
pipe 3
* Connecting using ssh
OpenSSH_7.2p2 Ubuntu-4ubuntu2.5, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 10.15.19.82 [10.15.19.82] port 22.
debug1: connect to address 10.15.19.82 port 22: No route to host
ssh: connect to host 10.15.19.82 port 22: No route to host
Click to expand...
Click to collapse
Don't worry. I will continue tuning it for best results. My result is the same as you.
impreza233 said:
Don't worry. I will continue tuning it for best results. My result is the same as you.
Click to expand...
Click to collapse
Ok.I`ll be waiting for this.
Android-fan117 said:
Ok.I`ll be waiting for this.
Click to expand...
Click to collapse
I'm thinking about the fact that the system would not be properly booted when the phone is switched on. Could you do a dmesg -w when the phone is switched on and shows a network on your computer?
impreza233 said:
I'm thinking about the fact that the system would not be properly booted when the phone is switched on. Could you do a dmesg -w when the phone is switched on and shows a network on your computer?
Click to expand...
Click to collapse
I`ll do it right now
---------- Post added at 04:20 PM ---------- Previous post was at 04:04 PM ----------
impreza233 said:
I'm thinking about the fact that the system would not be properly booted when the phone is switched on. Could you do a dmesg -w when the phone is switched on and shows a network on your computer?
Click to expand...
Click to collapse
ok...I found this
[ 1373.515554] usb 3-7: New USB device found, idVendor=18d1, idProduct=d001
[ 1373.515560] usb 3-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1373.515564] usb 3-7: Product: Failed to boot
[ 1373.515568] usb 3-7: Manufacturer: Halium initrd
[ 1373.515571] usb 3-7: SerialNumber: halium-initrd telnet 192.168.2.15
Android-fan117 said:
I`ll do it right now
---------- Post added at 04:20 PM ---------- Previous post was at 04:04 PM ----------
ok...I found this
[ 1373.515554] usb 3-7: New USB device found, idVendor=18d1, idProduct=d001
[ 1373.515560] usb 3-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1373.515564] usb 3-7: Product: Failed to boot
[ 1373.515568] usb 3-7: Manufacturer: Halium initrd
[ 1373.515571] usb 3-7: SerialNumber: halium-initrd telnet 192.168.2.15
Click to expand...
Click to collapse
Just as I suspected. Halium fails to boot. I will continue investigating this. Thanks!!!