Carbon ROM for Shield Tablet (WiFi Only) (wx_na_wf) - Shield Tablet Android Development

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* 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.
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a build of Carbon-ROM for the Shield Tablet (WiFi Only) (wx_na_wf)
You need to have CWM recovery installed on your device See Here for instructions install CWM. Try this version of CWM when flashing
Or use PhilZ
Instructions on installing:
Make a backup of your current ROM (Optional but highly recommended)
Wipe --> Factory Reset (Data, Cache, and Dalvik Cache)
Flash ROM
Flash Gapps
Reboot
Downloads:
9/7/14 Build
9/6/14 Build
If the above build doesn't work try this one
Bugs
You tell me
Kernel Source
XDA:DevDB Information
Carbon ROM for Shield Tablet WiFi Only, ROM for the Nvidia Shield Tablet
Contributors
joshuabg
Source Code: https://github.com/CarbonDev/android
ROM OS Version: 4.4.x KitKat
Based On: Carbon ROM
Version Information
Status: No Longer Updated
Created 2014-09-06
Last Updated 2016-01-01

Reserved

Reserved

Please post any feedback on testing the ROM.

If the first build I posted (carbon_wx_na_wf-ota-ae4195f719.zip) doesn't work, try this one:
https://s.basketbuild.com/filedl/de.../CARBON-KK-UNOFFICIAL-20140906-1608-wx_na.zip
(CARBON-KK-UNOFFICIAL-20140906-1608-wx_na.zip)

Tried both files. WiFi won't turn on for either of them. Thank you for your efforts.

Tried 2nd build, wifi does not turn on., but, it sees my exfat 128GB SDCARD !! :good:

Eogram said:
Tried both files. WiFi won't turn on for either of them. Thank you for your efforts.
Click to expand...
Click to collapse
Gilbot said:
Tried 2nd build, wifi does not turn on., but, it sees my exfat 128GB SDCARD !! :good:
Click to expand...
Click to collapse
Hmm WiFi doesnt work on my builds of Carbon and PAC. I wonder if I'm missing something or my build enviornment got messed up by a ubuntu update.....

joshuabg said:
Hmm WiFi doesnt work on my builds of Carbon and PAC. I wonder if I'm missing something or my build enviornment got messed up by a ubuntu update.....
Click to expand...
Click to collapse
Yup. Was just about to confirm that. Tried all 3 new builds. No WiFi. Back to land of fc
Sent from my One M8 using XDA Free mobile app

minieod said:
Yup. Was just about to confirm that. Tried all 3 new builds. No WiFi. Back to land of fc
Sent from my One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Ok I'm going to build PAC for my device Kindle Fire (otterx partitions)
It's already supported. If WiFi doesnt work I'll know that something is wrong with my build environment.

joshuabg said:
Ok I'm going to build PAC for my device Kindle Fire (otterx partitions) (My Verizon Galaxy S4 has a locked bootloader :crying
It's already supported. If WiFi doesnt work I'll know that something is wrong with my build environment.
Click to expand...
Click to collapse
Woot. Lemme know when to test
Sent from my SHIELD Tablet using XDA Free mobile app

minieod said:
Woot. Lemme know when to test
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
WiFi worked on the build I made for my Kindle Fire (otterx)
Not sure what in the device tree is causing it to not turn on.

After looking though the log cat I find this
Code:
E/WifiHW ( 844): Supplicant not running, cannot connect
Code:
I/wpa_supplicant.sh( 1948): Executing wpa_supplicant for BRCM chips
I/wpa_supplicant( 1949): /system/bin/wpa_supplicant: invalid option -- z
I/wpa_supplicant( 1949): wpa_supplicant v2.1-devel-4.4.4
I/wpa_supplicant( 1949): Copyright (c) 2003-2013, Jouni Malinen <[email protected]> and contributors
I/wpa_supplicant( 1949): This software may be distributed under the terms of the BSD license.
I/wpa_supplicant( 1949): See README for more details.
I/wpa_supplicant( 1949): This product includes software developed by the OpenSSL Project
I/wpa_supplicant( 1949): for use in the OpenSSL Toolkit (http://www.openssl.org/)
I/wpa_supplicant( 1949): usage:
I/wpa_supplicant( 1949): wpa_supplicant [-BddhKLqqstuvW] [-P<pid file>] [-g<global ctrl>] \
I/wpa_supplicant( 1949): [-G<group>] \
I/wpa_supplicant( 1949): -i<ifname> -c<config file> [-C<ctrl>] [-D<driver>] [-p<driver_param>] \
I/wpa_supplicant( 1949): [-b<br_ifname>] [-f<debug file>] [-e<entropy file>] \
I/wpa_supplicant( 1949): [-o<override driver>] [-O<override ctrl>] \
I/wpa_supplicant( 1949): [-N -i<ifname> -c<conf> [-C<ctrl>] [-D<driver>] \
I/wpa_supplicant( 1949): [-p<driver_param>] [-b<br_ifname>] [-I<config file>] ...]
I/wpa_supplicant( 1949): drivers:
I/wpa_supplicant( 1949): nl80211 = Linux nl80211/cfg80211
I/wpa_supplicant( 1949): options:
I/wpa_supplicant( 1949): -b = optional bridge interface name
I/wpa_supplicant( 1949): -B = run daemon in the background
I/wpa_supplicant( 1949): -c = Configuration file
I/wpa_supplicant( 1949): -C = ctrl_interface parameter (only used if -c is not)
I/wpa_supplicant( 1949): -i = interface name
I/wpa_supplicant( 1949): -I = additional configuration file
I/wpa_supplicant( 1949): -d = increase debugging verbosity (-dd even more)
I/wpa_supplicant( 1949): -D = driver name (can be multiple drivers: nl80211,wext)
I/wpa_supplicant( 1949): -e = entropy file
I/wpa_supplicant( 1949): -g = global ctrl_interface
I/wpa_supplicant( 1949): -G = global ctrl_interface group
I/wpa_supplicant( 1949): -K = include keys (passwords, etc.) in debug output
I/wpa_supplicant( 1949): -t = include timestamp in debug messages
I/wpa_supplicant( 1949): -h = show this help text
I/wpa_supplicant( 1949): -L = show license (BSD)
I/wpa_supplicant( 1949): -o = override driver parameter for new interfaces
I/wpa_supplicant( 1949): -O = override ctrl_interface parameter for new interfaces
I/wpa_supplicant( 1949): -p = driver parameters
I/wpa_supplicant( 1949): -P = PID file
I/wpa_supplicant( 1949): -q = decrease debugging verbosity (-qq even less)
I/wpa_supplicant( 1949): -v = show version
I/wpa_supplicant( 1949): -W = wait for a control interface monitor before starting
I/wpa_supplicant( 1949): -N = start describing new interface
I/wpa_supplicant( 1949): example:
I/wpa_supplicant( 1949): wpa_supplicant -Dnl80211 -iwlan0 -c/etc/wpa_supplicant.conf
E/WVMExtractor( 189): IsWidevineMedia not found in libwvm.so
E/WVMExtractor( 189): IsWidevineMedia not found in libwvm.so

minieod said:
Woot. Lemme know when to test
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Ok I'm compiling a Carbon build now with a modified vendor file. I removed the -z option, not sure what -z did but it doesn't seem to be compatible with Carbon or PAC. Hopefully it deosn't keep the device from blowing up. Compiling with make clean so could take a while.

joshuabg said:
Ok I'm compiling a Carbon build now with a modified vendor file. I removed the -z option, not sure what -z did but it doesn't seem to be compatible with Carbon or PAC. Hopefully it deosn't keep the device from blowing up. Compiling with make clean so could take a while.
Click to expand...
Click to collapse
sweet! send me a PM when its done and ill download

minieod said:
sweet! send me a PM when its done and ill download
Click to expand...
Click to collapse
Ok new build is up.
https://s.basketbuild.com/filedl/de.../nightlies/carbon_wx_na_wf-ota-b7e7db1059.zip
Tell me how it goes.

joshuabg said:
Ok new build is up.
https://s.basketbuild.com/filedl/de.../nightlies/carbon_wx_na_wf-ota-b7e7db1059.zip
Tell me how it goes.
Click to expand...
Click to collapse
I am able to turn on the wifi. It says "searching for wi-fi networks" but it dosnt find anything

EverythingPortable said:
I am able to turn on the wifi. It says "searching for wi-fi networks" but it dosnt find anything
Click to expand...
Click to collapse
Have you tried manually adding a network? Maybe reboot?

joshuabg said:
Have you tried manually adding a network? Maybe reboot?
Click to expand...
Click to collapse
Not manually adding, but itried reboot, no luck

EverythingPortable said:
Not manually adding, but itried reboot, no luck
Click to expand...
Click to collapse
OK, I will try to do another build of pac first then I'll do antoher build of carbon. (With some patches made)

Related

[CWM] ClockworkMod 6.0.4.0 that will NOT update your touchscreen firmware

So I have this new tablet, and knowing all the bugs surrounding the touchscreen, decided not to update it (it came as stock JSS15J). However I still want to be able to use CM on it, so I patched the kernel to never update the touchscreen fw. Here's the compiled recovery from CM-10.2 synced today (october 2th), and then the kernel patch:
https://docs.google.com/file/d/0ByHQWL5Q6bSwYXJpaE9JZ0dnbVE/edit?usp=sharing
Code:
diff --git a/drivers/input/touchscreen/ektf3k.c b/drivers/input/touchscreen/ektf3k.c
index 4b6a7e7..451bcee 100755
--- a/drivers/input/touchscreen/ektf3k.c
+++ b/drivers/input/touchscreen/ektf3k.c
@@ -392,7 +392,7 @@ static int check_fw_version(const unsigned char*firmware, unsigned int size, int
id = firmware[size - 2*FIRMWARE_PAGE_SIZE + 122] |
(firmware[size - 2*FIRMWARE_PAGE_SIZE + 123] << 8);
- touch_debug(DEBUG_INFO, "The firmware was version 0x%X and id:0x%X\n", version, id);
+ touch_debug(DEBUG_INFO, "The firmware was version 0x%X and id:0x%X, new fw_version: 0x%X\n", version, id, fw_version);
if (id == 0x3029 && BOOTCODE_VERSION >= 0x6046) {
/*if the touch firmware was empty, always update firmware*/
@@ -1318,7 +1318,10 @@ static int firmware_update_header(struct i2c_client *client, unsigned char *firm
unsigned char nb_isp_cmd[4] = {0x45, 0x49, 0x41, 0x50};
unsigned char *cursor;
struct elan_ktf3k_ts_data *ts = i2c_get_clientdata(client);
-
+
+ printk("[ektf3k]: firmware_update_header: not updating your firmware, bro\n");
+ return 0;
+
if(ts == NULL)
return -1;
I can also upload the kang if anyone needs it. Note my patch has the old/new version swapped (small bug), it says new fw_version, but it's actually the current version.
I tested it with my own device just in case someone is wondering wether it works or not.
On a slightly unrelated note, my CM 10.2 kang would not have the Wi-Fi module loading. I had this error in logcat:
Code:
E/WifiHW ( 190): Failed to write wlan fw path param (Operation not permitted)
E/WifiStateMachine( 597): Failed to reload STA firmware java.lang.IllegalStateException: command '6 softap fwreload wlan0 STA' failed with '400 6 SoftAP command has failed'
Digging a bit further led to this error in the kernel log:
Code:
<6>[ 69.311614] wlan: loading driver v3.2.2.17B
<3>[ 69.314300] wlan: [573:F :HDD] hdd_parse_config_ini: request_firmware failed -2
However the official nightly didn't have this issue. I tracked it down to the lack of a symbolic link, which I had to create manually:
Code:
mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
cd /vendor/firmware/wlan/prima/
ln -s /data/misc/wifi/WCNSS_qcom_cfg.ini WCNSS_qcom_cfg.ini
ln -s /data/misc/wifi/WCNSS_qcom_wlan_nv.bin WCNSS_qcom_wlan_nv.bin
I hope this information will be useful to others. Still not sure why my build has this problem and the official builds don't.

[Guide] How To Logcat

I think this one is definitely needed for this forum as i am seeing more and more users ask how to logcat. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.
Good work, Khizar. A very handy and usefull guide. Thanks.
Perfect idea! Very good guide!!! As usual! Amazing job, my friend!
Sent from my SM-G900F using Tapatalk
Pierre118 said:
Good work, Khizar. A very handy and usefull guide. Thanks.
Click to expand...
Click to collapse
daxgirl said:
Perfect idea! Very good guide!!! As usual! Amazing job, my friend!
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Thank you both but JFYI this isn't my work. I shared this guide on my previous phone and since it's so good and there is ALOT of need I shared it here as well. I mentioned that in the OP.
Sent From My SM-N9005 To All You Wonder Nobodies!!
Due to the lack of mods, trolls can ruin the XDA forum's. Don't feed them...Instead report them.
Click to expand...
Click to collapse
daxgirl said:
Perfect idea! Very good guide!!! As usual! Amazing job, my friend!
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
agree !
Khizar said:
Thank you both but JFYI this isn't my work. I shared this guide on my previous phone and since it's so good and there is ALOT of need I shared it here as well. I mentioned that in the OP.
Sent From My SM-N9005 To All You Wonder Nobodies!!
Click to expand...
Click to collapse
Though not pure your own work, but noobies will need it, especially to send a log back to devs to know what is the problem.
And it's a good thing to share here.
:good:
antique_sonic said:
agree !
Though not pure your own work, but noobies will need it, especially to send a log back to devs to know what is the problem.
And it's a good thing to share here.
:good:
Click to expand...
Click to collapse
Appreciate the support brother...
Sent From My SM-G900F-Morphed SM-N9005 With XNote Goodness To All You Wonder Nobodies!!
Due to the lack of mods, trolls can ruin the XDA forum's. Don't feed them...Instead report them.
Click to expand...
Click to collapse
Khizar said:
Appreciate the support brother...
Sent From My SM-G900F-Morphed SM-N9005 With XNote Goodness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
No worries Bro.
Sent from somewhere under the sky, at the corner of this rounded earth.
Great idea bro. We finally have a proper logcat thread for our Note3. ?
Sent from my SM-G900F using Tapatalk
fahadali2315 said:
Great idea bro. We finally have a proper logcat thread for our Note3. ?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
:good:

[SOLVED][Q] WiFi won't turn on

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.

Kali Linux on Android Phone with Metasploit, Aircrack ng, John, Tmux...

Hello everyone !
I was so glad to know the release of Nethunter 1.1 on offensive security, so I immediattely decided to tried it on my Nexus 4. But It didn't really work as Nexus 4 devices doesn't really support USB external devices :/ even if XDA devs did release a patch for this, it made WIFI disapear...
That's why I decided to use Linux Deploy in a new way : I thought this app was really limited, but finally I managed to get something really similar to a Nethunter device !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So here we are, and I'm gonna show you a few steps to install and configure kali linux with some tools !
1) Root your phone
2) Dowload Linux Deploy
3) Download the Kali image BUT :
The installator will automatically generate a 4Gb image in your internal memory - which is relally big - thats why you might have two solutions :
- Use an external sdcard but it would be a waste of memory
- BETTER SOLUTION : Tap on "Image size (MB)" and enter the amount of memory youwant to allocate. I suggest 2200 MB (2,2GB)
Then, go to "Compents to install, and UNCHECK EVERYTHING EXCEPT -> SSH SERVER.
Thanks to this, your linux image will occupate 2,2Gb with a lot of freespace in it, so we'll be able to download some utilities, without getting useless things such as a graphical desktop.
So just click install and wait a few minute for the installation to complete.
So what ?
In order to connect to your new kali environnement you will need an ssh client (for we've only selected the ssh server and no VNC)
So just install a ssh client or use a terminal emulator such as "Terminal IDE" (and not the Jack Palevitch's one whisch has no built in ssh and i really dont like his emulator)
I personally prefer use the ssh client : https://play.google.com/store/apps/details?id=com.anstudios.ssh
This one is light efficient and not intrusive.
You might also want to install the "Hacker's keyboard" or use the "Terminal IDE"'s one. You'll surely need it, as the arrows, esc and ctrl keys are really useful.
Then, launch your system via the "Launch" button. You should have an output like this one :
http://img.wonderhowto.com/img/original/21/16/63562179326178/0/635621793261782116.jpg
EXCEPT THAT : You've only installed the ssh client so you output should look like : SSH :22 ... done
VNC :5900 ... fail
Awesome.
Now just launch your ssh client :
The default credentials are "android" and "changeme". So infront of "ssh" just type :
[ssh] [email protected]
And when the system ask you for the password , type "changeme".
Just have fun !!
TIP : If the display is too small, just use the volume keys to fix it.
NOW : Some basic steps
1) Checkout the space available : df -h
2) Get root : su
3) Install all the packages you want.
/WARNING\ : Smartphones chipsets doen't allow injection or monitor mode even if a few guys managed to. But iys eally experimental. You can use an external wifi card and heres the tutorial to do it :
http://forum.xda-developers.com/goo...opment/guide-convert-phone-pwn-phone-t2852293
Some things to install to have fun :
- aircrack-ng to break a 4 way handshake (tutorial below)
- Metasploit to send your backdoors (tutorial below)
- Tmux because were limite to only one window (script below)
- GCC to compile
- Vim to edit
1) Get root
For those who have issues to get root just follow these step
sudo passwd root
type twice your password
2) Install the packages :
apt-get install aircrack-ng
apt-get install metasploit
apt-get install metasploit-framework
apt-get install tmux
apt-get install john
3) If you wish to install SET :
cd /opt
sudo apt-get install git
git clone https://github.com/trustedsec/social-engineer-toolkit/ set/
cd set/
python setup.py install
Have fun.
THE TUTORIAL PART
You have to consider the fact that you're running a chrooted environment.
So, in order to access to the internal sotrage, yo have to go into Linux Deploy options : Scroll down to "Custom Mounts" and enable it. Then tap on "Mount points" and enable all the path presented. It will allow you, once you've booted your linux img to access all of your phone's data
Now you might i communicate with a pc for example, get your handsake and crack it on your phone, or send a backdoor generated on your phone ?
Here's another solution :
NETCAT. On a linux or windows machine with netcat here's a little metasploit fun :
On your kali PHONE
msfvenom /your/payload/ OPTIONS -a YOUR_ARCH -e exe and some stuff here > mybackdoor
nc -w 3 IPADDRESS_OFDESTINATION < mybackoor
On your victims's computer :
nc -l -p 1234 > mybackdoor
And now, no mattter how you managed to transfer the backdoor -netcat / usb cable/ any other hack - , let's play :
Proof of concept ? Here's a Metasploit shell gained on a linux machine :
AND..... PWNDED !! (yeah that was quite simple...)
Metasploit3
And this Netcat trick works with ANY file.
For example : a captured handshake on a kali pc ! Tip : You can reduce it size with wpaclean :
wpaclean <out.cap> <in.cap>
How to crack the key ? Pipe Crunch into aircrack or john OR use this program if you want to generate HEXADECIMAL keys :
HexKeygenerator
/*
* HexKeygenerator is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published
* by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
*
* HexKeygenerator is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License along with Foobar. If not, see http://www.gnu.org/licenses/.
*
*/
// Autheurs : Sdpbz1 and improved by romeoandjuliet
#include <stdio.h>
#include <stdlib.h>
#include <time.h>
void help(char name[]) {
printf("Usage:%s <Nb keys to generate> <file>\n\n", name);
printf("Exemple: generate 1000000 keys in the file dictionary.wpa\n");
printf("%s 10000000 dictionary.wpa\n", name);
}
int main(int argc, char * argv[])
{
long long int nb;
int size; //Key lenght
double i, z;
int byte = 0;
FILE *PF1;
if(argc != 4) {
help(argv[0]);
return 1;
}
//Convert to long and check
nb = atol(argv[1]);
if(nb == 0) {
printf("Please enter a valid number !!!\n");
help(argv[0]);
return 1;
}
size = atol(argv[3]);
if(nb == 0) {
printf("Please enter a valid number\n");
help(argv[0]);
return 1;
}
PF1 = fopen(argv[2], "w");
if (PF1 == NULL) {
printf("Cant create file %s\n", argv[2]);
return 1;
}
printf("Générating de %d hexadecimal keys\n", nb);
srand(time(NULL));
for(z = 1; z <= nb; z++) {
for (i = 1; i <= size; i++) {
byte = rand() % 256;
fprintf(PF1,"X", byte); //Hex display
}
if(z % 100000 == 0) {
printf("%l keys generated\n", z); // }
fprintf(PF1,"\n");
}
fclose(PF1);
return 0;
}
To compile it :
gcc HexKeygnerator.c -o HexKeygnerator
Here's a first script to handle the crack : startup.sh
for i in `seq 1 1000000``
do
./HexKeygenerator 1000000 password$i.lst 5 # for a 10 char hexadecimal key
aircrack-ng /path/to/handshake -e ESSID -w password$i.lst -p #NBOF_CORES >> log.txt # IF YOU USE ALL CORES AVAILABLE YOUR PHONE WILL ALMOST FREEZE
rm password$i.lst
then
grep "KEY FOUND" log.txt > KEY_FOUND # On sauve la clé
grep "KEY FOUND" log.txt
grep "KEY FOUND" log.txt
fi
done
To have this run and be checked permanently in a TMUX session : Use this script and it ill automatically launch the previos script (save both in the same directory)
SESSION=$USER
tmux split-window -h
tmux select-pane -t 0
tmux send-keys "sh ./startup.sh" C-m
tmux select-pane -t 1
tmux send-keys "Watch -n 30 grep KEY log.txt" C-m
tmux split-window -v
tmux send-keys "Watch -n 30 tail log.txt" C-m # to check the cracking's speed
tmux select-window -t $SESSION:1
tmux -2 attach-session -t $SESSION
Screenshot ? :
And here it is. This is only the beginning ! thaths why i thing linux deploy is better and more modulable than nethunter.
Have fun !!!
If you liked this, please check my little website :
http://mindhackingdevices.e-monsite.com/pages/premier-post.html
Pour les francophones, ce post existe en fracnais ssur l'excellent forum :
http://www.crack-wifi.com/forum/topic-11195-linux-deploy-kali-linux.html
Romeoandjuliet
Gonna give this a go as I was struggling to get my head around it. Nice one ?
Sent from my SM-G925F using Tapatalk
Ssh and vnc services fail every time.
Can anyone help me?
Awesome tutorial and lots to learn. Thanks
I am not able to install any of the linux on my phone using linux deploy, while installation part it stops suddenly and says that cant download (specific package name).
help broh
> start
[23:18:50] Mounting partitions:
[23:18:50] / ... skip
[23:18:50] /proc ... skip
[23:18:50] /sys ... skip
[23:18:50] /sys/fs/selinux ... skip
[23:18:50] /dev ... skip
[23:18:50] /dev/pts ... skip
[23:18:50] /dev/shm ... done
[23:18:50] :: Mounting partitions:
[23:18:50] /system ... done
[23:18:50] /sdcard ... done
[23:18:50] :: Configuring core/mnt ...
[23:18:50] :: Configuring core/net ...
[23:18:50] :: Starting extra/dbus ... done
[23:18:50] :: Starting extra/ssh ... fail
[23:18:50] :: Starting graphics/vnc ... done
[23:18:50] <<< start
Mohsin Pathan said:
I am not able to install any of the linux on my phone using linux deploy, while installation part it stops suddenly and says that cant download (specific package name).[/QUOTE
You must have root for Deploy it is for loading the graphical environment
Click to expand...
Click to collapse
okietruax said:
Mohsin Pathan said:
I am not able to install any of the linux on my phone using linux deploy, while installation part it stops suddenly and says that cant download (specific package name).[/QUOTE
You must have root for Deploy it is for loading the graphical environment
Click to expand...
Click to collapse
My all the phones are rooted.
Click to expand...
Click to collapse
Mrcable said:
> start
[23:18:50] Mounting partitions:
[23:18:50] / ... skip
[23:18:50] /proc ... skip
[23:18:50] /sys ... skip
[23:18:50] /sys/fs/selinux ... skip
[23:18:50] /dev ... skip
[23:18:50] /dev/pts ... skip
[23:18:50] /dev/shm ... done
[23:18:50] :: Mounting partitions:
[23:18:50] /system ... done
[23:18:50] /sdcard ... done
[23:18:50] :: Configuring core/mnt ...
[23:18:50] :: Configuring core/net ...
[23:18:50] :: Starting extra/dbus ... done
[23:18:50] :: Starting extra/ssh ... fail
[23:18:50] :: Starting graphics/vnc ... done
[23:18:50] <<< start
Click to expand...
Click to collapse
Same here
No one has asked, but have you install busy box and did you check the box to have ssh server start? Have you tried logging in with ssh to "localhost" or 127.0.0.1 on port 22?
Link to busy box: https://play.google.com/store/apps/details?id=ru.meefik.busybox
Kali Linuxx Install
My video shows in less then 5 mins
youtube.com/watch?v=RoHsMwzxLG8
How to solve this
E: unable to locate package aircrack-ng:
confused:
Excuse me guys for my intelligence but I wanna ask about all that
In the end what is the purpose of this kali linux ?
This Deploy what is for?
Some hacking wifi or what?
And again I'm sorry that i don't understand it

Ubuntu Touch Porting: Motorola Moto E 2015 4G/LTE

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!!!

Categories

Resources