Database Info

[Q] Tablet Help

Hi.
I need some help trying to fix WiFi on a tablet I was given to fix.
Its some chinese thing so off to a good start!
So its an A13 Allwinner based tablet.
I have re-flashed it with the same firmware that was on it when I got it and the wifi is still not working.
Wifi just wont turn on.
I have done some digging and found that the tablet uses an RTL8188ETV chip.
The module thats being loaded on the tablet is 8188eu.ko IS that right? Or should it be a 8188etv.ko module that I need?
Diagnostic wise, I can see some errors in the error log like:
E/WifiHW ( 159): insmod 8192cu ko failed!
E/WifiStateMachine( 159): Failed to load driver!
E/WifiStateMachine( 159): DriverFailedState
E/WifiHW ( 159): timeout, register netdevice wlan0 failed.
E/WifiStateMachine( 159): Failed to load driver!
E/WifiStateMachine( 159): DriverFailedState
E/WifiHW ( 159): timeout, register netdevice wlan0 failed.
E/WifiStateMachine( 159): Failed to load driver!
E/WifiStateMachine( 159): DriverFailedState
I tried to manually load the 8188eu.ko but all i got was "file already exists"
Anyone got any ideas on how I can get this thing going again?

Seansmit17 said:
Hi.
I need some help trying to fix WiFi on a tablet I was given to fix.
[snip]
The module thats being loaded on the tablet is 8188eu.ko IS that right? Or should it be a 8188etv.ko module that I need?
[snip]
Anyone got any ideas on how I can get this thing going again?
Click to expand...
Click to collapse
This applies to something I'm working on right now. Did you ever find/figure out a solution?
Looks like Realtek supplies Linux (specifically Android-compatible) drivers on their website, but they don't have the ETV version explicitly: http://www.realtek.com/downloads/do...n=4&DownTypeID=3&GetDown=false&Downloads=true

wifi problem

Hello,
i own a RK3188 device (T-R42 with board version B351 V1.1)
I flashed a custom rom and since then i am no more able to reactivate the wifi
I tried many other custom roms and stock roms, but i have always the same behavior:
When from the settings i try to turn it on, it stays on for a few seconds ( no wireless network is shown ), and then it goes off
This is the logcat that is printed when i try to turn my wifi on:
(using command adb logcat on terminal emulator session)
D/WifiHW ( 368): Read wifi chip type OK ! wifi_chip_type = RK901
D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko, DRIVER_MODULE_ARG =
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/WifiService( 368): setWifiEnabled: true pid=870, uid=1000
D/AudioHardwareALSA( 109): Audio exiting sandby will open audio device
D/AudioHardwareALSA( 109): AudioStreamOutALSA::standby().....
D/WifiHW ( 368): wifi_load_driver: driver load failed
D/WifiHW ( 368): Unable to unload driver module "wlan": No such file or directory
E/WifiStateMachine( 368): Failed to load driver!
E/WifiStateMachine( 368): DriverFailedState
i checked that under system/lib/modules do exist these files:
rkwifi.ko
wlan.ko
both with owner 'root', group 'root' and permissions 644
Can someone give me some hints on what is the possible cause of this error,
and how to discover the right wifi drivers for my device?
Thank you!

Try reflashing the baseband again, I was having the same problem with a kernel, and a custom rom, I flashed the stock baseband and reflash the custom rom and my wifi started working again, or check the kernel that you are using, that could be the problem. Hope this helped out a bit, I know its a real headache when this happens, hope you made a backup too.

Vicolodo said:
Hello,
i own a RK3188 device (T-R42 with board version B351 V1.1)
I flashed a custom rom and since then i am no more able to reactivate the wifi
I tried many other custom roms and stock roms, but i have always the same behavior:
When from the settings i try to turn it on, it stays on for a few seconds ( no wireless network is shown ), and then it goes off
This is the logcat that is printed when i try to turn my wifi on:
(using command adb logcat on terminal emulator session)
D/WifiHW ( 368): Read wifi chip type OK ! wifi_chip_type = RK901
D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko, DRIVER_MODULE_ARG =
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/WifiService( 368): setWifiEnabled: true pid=870, uid=1000
D/AudioHardwareALSA( 109): Audio exiting sandby will open audio device
D/AudioHardwareALSA( 109): AudioStreamOutALSA::standby().....
D/WifiHW ( 368): wifi_load_driver: driver load failed
D/WifiHW ( 368): Unable to unload driver module "wlan": No such file or directory
E/WifiStateMachine( 368): Failed to load driver!
E/WifiStateMachine( 368): DriverFailedState
i checked that under system/lib/modules do exist these files:
rkwifi.ko
wlan.ko
both with owner 'root', group 'root' and permissions 644
Can someone give me some hints on what is the possible cause of this error,
and how to discover the right wifi drivers for my device?
Thank you!
Click to expand...
Click to collapse
Do you have stock firmware/rom of your device? If yes then you need to flash(patch) all the files in lib/modules.
Also in updater-script add this code:
symlink("rkwifi.ko", "/system/lib/modules/wlan.ko");
then flash it via cwm

MgudFrn said:
Do you have stock firmware/rom of your device? If yes then you need to flash(patch) all the files in lib/modules.
Also in updater-script add this code:
symlink("rkwifi.ko", "/system/lib/modules/wlan.ko");
then flash it via cwm
Click to expand...
Click to collapse
Ok thank you,
yes, the seller gave me some links for the stock firmware, but he is not sure on which is the original stock firmware
(for T-R42 there are a lot of different board versions with different chipsets...)
i can extract the components with a tool (perhaps i need only system.img and unpack it)
and build a zip to patch the system/lib/modules
by the way, why i have to add that symlink?
i checked that RK901 information is under the sys folder,
the file system under this folder is built dynamically by the kernel, i am right?
do you think that RK901 is hard-coded into the kernel?
because opening the board i checked that i have a different chipset... wifi is managed by chip AP6210
Thank you!

kidkree1 said:
Try reflashing the baseband again, I was having the same problem with a kernel, and a custom rom, I flashed the stock baseband and reflash the custom rom and my wifi started working again, or check the kernel that you are using, that could be the problem. Hope this helped out a bit, I know its a real headache when this happens, hope you made a backup too.
Click to expand...
Click to collapse
Thank you too
The strange thing i see on the settings is that the wifi mac address is not set (unknown)...perhaps this happens because wifi driver cannot be loaded?
The second strange thing i see is that the file
/sys/class/rkwifi/chip
(this is the file used by the wifi driver loader procedure to know which is the wifi chip of the board)
contains RK901
i read somewhere that this chip is used on rk3066 boards, instead i have a rk3188 board
Besides that, i opened my tv box and i saw that i have the chip AP6210...
By the way, this is the link to an example driver loader procedure
https://github.com/gripped/MK808-he...lob/master/RK30_MT5931_MT6622/wifi/wifi.c.new
I found it googling one of the strings that is reported by the logcat
'D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko',
this string is contained in the c source file
so also the driver load procedure seems done for other device (rk3066)...
or perhaps rk3066 and rk3188 share the same procedures... i dont know...

Vicolodo said:
Ok thank you,
yes, the seller gave me some links for the stock firmware, but he is not sure on which is the original stock firmware
(for T-R42 there are a lot of different board versions with different chipsets...)
i can extract the components with a tool (perhaps i need only system.img and unpack it)
and build a zip to patch the system/lib/modules
by the way, why i have to add that symlink?
i checked that RK901 information is under the sys folder,
the file system under this folder is built dynamically by the kernel, i am right?
do you think that RK901 is hard-coded into the kernel?
because opening the board i checked that i have a different chipset... wifi is managed by chip AP6210
Thank you!
Click to expand...
Click to collapse
Previously I faced same problem with my mt6575 chipset and that was resolved by this method. I know mine and yours chipset is totally different but the logcat that I got was same as yours mentioning 'loading drivers failed'. So you can give it a try. but plz do a nandroid backup first.

Driver problem??
Vicolodo said:
Hello,
i own a RK3188 device (T-R42 with board version B351 V1.1)
I flashed a custom rom and since then i am no more able to reactivate the wifi
I tried many other custom roms and stock roms, but i have always the same behavior:
When from the settings i try to turn it on, it stays on for a few seconds ( no wireless network is shown ), and then it goes off
This is the logcat that is printed when i try to turn my wifi on:
(using command adb logcat on terminal emulator session)
D/WifiHW ( 368): Read wifi chip type OK ! wifi_chip_type = RK901
D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko, DRIVER_MODULE_ARG =
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/WifiService( 368): setWifiEnabled: true pid=870, uid=1000
D/AudioHardwareALSA( 109): Audio exiting sandby will open audio device
D/AudioHardwareALSA( 109): AudioStreamOutALSA::standby().....
D/WifiHW ( 368): wifi_load_driver: driver load failed
D/WifiHW ( 368): Unable to unload driver module "wlan": No such file or directory
E/WifiStateMachine( 368): Failed to load driver!
E/WifiStateMachine( 368): DriverFailedState
i checked that under system/lib/modules do exist these files:
rkwifi.ko
wlan.ko
both with owner 'root', group 'root' and permissions 644
Can someone give me some hints on what is the possible cause of this error,
and how to discover the right wifi drivers for my device?
Thank you!
Click to expand...
Click to collapse
The last few line sof your logcat show that there is some driver error...try a full wipe, then (as already suggested) flash a stock ROM for your device.
(<--Remember to Thank me if this helps)

Vicolodo said:
Thank you too
The strange thing i see on the settings is that the wifi mac address is not set (unknown)...perhaps this happens because wifi driver cannot be loaded?
The second strange thing i see is that the file
/sys/class/rkwifi/chip
(this is the file used by the wifi driver loader procedure to know which is the wifi chip of the board)
contains RK901
i read somewhere that this chip is used on rk3066 boards, instead i have a rk3188 board
Besides that, i opened my tv box and i saw that i have the chip AP6210...
By the way, this is the link to an example driver loader procedure
https://github.com/gripped/MK808-he...lob/master/RK30_MT5931_MT6622/wifi/wifi.c.new
I found it googling one of the strings that is reported by the logcat
'D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko',
this string is contained in the c source file
so also the driver load procedure seems done for other device (rk3066)...
or perhaps rk3066 and rk3188 share the same procedures... i dont know...
Click to expand...
Click to collapse
Vicolodo,
Were you able to get your wifi working again? I am having a similar issue on RK3066 aftermarket GPS car unit and can really use some advice.
Thanks!
P340

[Q] WiFi connect possible, but no scanning?

Hi,
problem:
i can´t see any wifi networks, that im not connected to
i´m able to add manuelly any wifi network without problems.. wifi on those manually added networks, works perfect
notification of open networks is enabled.. and i got a notification that there is an open wifi network in range.. so scanning itself seems to work? but my device doesn´t show any network but the one im connected to.
EDIT: "MotoTool AIO" shows me at "SysInfo" -> "wifi" a wifi scan... so this seems really a problem on just displaying the wifi scan results on the device?!?!?
tools like "wifi analyzer" don´t show ANY network
what i tried/looked for, without a positive result:
wifi_display_on has still value 0 in settings.db
file WCNSS_qcom_wlan_factory_nv.bin is existing in /persists (http://forum.xda-developers.com/showpost.php?p=49656627&postcount=3)
flashed stock baseband (http://forum.xda-developers.com/showthread.php?t=2649763)
i did more.. but can´t remember everything.. im sorry...
im on latest gapps.. latest cm12 nightly.. (problem exists since some nightly in the summer of 2014)
im on moto g XT1032
i did not a clean install.. i just upgraded via adb sideload in TWRP (and i don´t really want to do a clean install)
after fixing systemUI Crash and launcher3 crash on myself (look: http://forum.xda-developers.com/showpost.php?p=58316659&postcount=768) i just have this problem (also no GPS Signal, tried to fastboot erasing modemst1 and modemst2)
im really really interested in finding the problem instead of just do a clean install..
so i also take a look at logcat.. and found those errors:
the errors:
I/wpa_supplicant(4981): CTRL_IFACE: Detach monitor /data/misc/wifi/sockets/wpa_ctrl_774-5\x00 that cannot receive messages
E/WifiHW (774): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
E/WifiHAL (774): wifi_error wifi_set_scanning_mac_oui(wifi_interface_handle, byte*): requestResponse Error:-95
E/WifiHAL (774): wifi_error wifi_get_gscan_capabilities(wifi_interface_handle, wifi_gscan_capabilities*): GSCAN is not supported by driver
more details:
I/wpa_supplicant(4981): CTRL_IFACE: Detach monitor /data/misc/wifi/sockets/wpa_ctrl_774-5\x00 that cannot receive messages
E/WifiHW (774): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
I/wpa_supplicant(6513): Successfully initialized wpa_supplicant
I/wpa_supplicant(6513): rfkill: Cannot open RFKILL control device
E/WifiHW (774): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
I/wpa_supplicant(6513): rfkill: Cannot open RFKILL control device
D/WifiConfigStore(774): Loading config and enabling all networks
I/wpa_supplicant(6513): wlan0: CTRL-EVENT-SCAN-STARTED
D/WifiNative-HAL(774): Setting external_sim to 1
D/WifiStateMachine(774): Setting OUI to DA-A1-19
I/WifiNative-HAL(774): startHal
D/wifi (774): setting scan oui 0x977ece20
I/WifiHAL (774): ******HexDump len:0*********
I/WifiHAL (774): ******HexDump End***********
E/WifiHAL (774): virtual int WifiVendorCommand::create() ifindex obtained:29
E/WifiHAL (774): virtual int WifiVendorCommand::set_iface_id(const char*) ifindex obtained:29
I/WifiHAL (774): MAC_OUI - da:a1:19
D/WifiHAL (774): virtual int WifiVendorCommand::requestResponse(): request a response
E/WifiHAL (774): wifi_error wifi_set_scanning_mac_oui(wifi_interface_handle, byte*): requestResponse Error:-95
D/RttService(774): SCAN_AVAILABLE : 3
D/WifiScanningService(774): SCAN_AVAILABLE : 3
D/RttService(774): DefaultState got{ when=-1ms what=160512 target=com.android.internal.util.StateMachine$SmHandler }
D/WifiScanningService(774): DefaultState got{ when=-1ms what=160006 target=com.android.internal.util.StateMachine$SmHandler }
I/WifiNative-HAL(774): startHal
D/wifi (774): getting scan capabilities on interface[0] = 0x977ece20
E/WifiHAL (774): wifi_error wifi_get_gscan_capabilities(wifi_interface_handle, wifi_gscan_capabilities*): GSCAN is not supported by driver
D/wifi (774): failed to get capabilities : -3
E/WifiScanningService(774): could not get scan capabilities
D/WifiMonitor(774): startMonitoring(p2p0) with mConnected = true
D/class com.mobisystems.wifi_direct.StartWifiDirectReceiver(6198): Wifi notification received.
D/class com.mobisystems.wifi_direct.StartWifiDirectReceiver(6198): WIFI State Changed.
Click to expand...
Click to collapse

added important info in first post!

[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.

USb tethering lags - fix enhancement

Hi everyone!
Sorry for the long post, but I wanted to be clear
I've just read a recent post concerning USB tethering lags under windows 8.1:
http://forum.xda-developers.com/android/general/fix-usb-tethering-lags-freezes-windows-t3039183
All in all, to fix the issue, I have to force the installation of another driver (which is called "Remote NDIS Compatible Device") instead of the windows stock one (called "Remote NDIS based Internet Sharing Device"). After the operation, the lags disappeared.
Now, what i would like to do is modify the usb device descriptor given by android when tethering is activated to tell windows to directly install the right driver. According to the inf file of "Remote NDIS Compatible Device", named rndiscmp.inf, any usb hardware with the following spec will trigger the driver install:
DeviceClass=EF
DeviceSubClass=04
DeviceProtocol=01
Now there is an rc file in / called init.qcom.usb.rc on my device telling what parameters to give to the usb when usb tethering is enabled. The interesting part is here:
Code:
on property:sys.usb.config=rndis
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 05C6
write /sys/class/android_usb/android0/idProduct 676A
write /sys/class/android_usb/android0/functions rndis
write /sys/class/android_usb/android0/enable 1
setprop sys.usb.state ${sys.usb.config}
So I went to /sys/class/android_usb/android0/ and it seems this is the place where the usb device descriptor is set. There are 3 interesting files:
bDeviceClass
bDeviceSubClass
bDeviceProtocol
So to make the modification, I added in the rc file before the "enable 1":
Code:
write /sys/class/android_usb/android0/idProduct 676E
write /sys/class/android_usb/android0/bDeviceClass EF
write /sys/class/android_usb/android0/bDeviceSubClass 04
write /sys/class/android_usb/android0/bDeviceProtocol 01
(I changed the idProduct to see if it would change in windows when I would plug the device).
I rebuilt the boot.img with these modifications (since / is a ramdisk and the rc file is extracted from the boot image at each startup), flashed it to my phone (with fastboot flash boot boot.img) and hoped that when enabling the usb tether option, I would see the new idProduct and the new class, subclass and protocol of the device, and with the right driver!
When plugging it on windows, and enabling usb tethering, the idProduct changed as expected, but the class, subclass and protocol were the same than before (FYI: E0,01,03), therefore triggering the bad driver install (whose inf is named WceISVista.inf by the way). I went to /sys/class/android_usb/android0/ and checked each three files I asked to be modified:
cat bDeviceClass : 0
cat bDeviceSubClass : 4
cat bDeviceProtocol : 1
Why would the bDeviceClass be set back to 0?
I feel I'm so close, would you guys have any ideas? Thank you!