Hello, physical keyboard geeks!
I've added basic support for the galaxy s relay to the postmarketos project. You can now build a new kernel with a modern compiler that will boot on our sliders. Tested: Boot, usb ethernet, flashing with heimdall, nothing else.
Something like this might work to install:
apt-get install -y python3
Clone the repo and cd into it.
git clone https://gitlab.com/postmarketOS/pmbootstrap.git
cd pmbootstrap
Start the install wizard
./pmbootstrap.py init
Chose samsung-apexq for device and use the xfce4 gui. (unsure if graphics will work, but if it does it's the one you want)
./pmbootstrap.py install --android-recovery-zip --no-fde
Now export the zip file
./pmbootstrap.py export
It should give you a path to a zip you can flash with CWM or TWRP. If that doesn't work, then run install without --android-recovery-zip and try flashing with the heimdall wrapper like this:
./pmbootstrap.py flasher flash_rootfs
./pmbootstrap.py flasher flash_kernel
(Obviously, make sure you have a good usb data cable and not just a charge only cable, oh and make sure you have backups of your favorite android rom so you can go back to android).
Go forth and test! My dev phone's screen died so now it's up to YOU! File bugs in the postmarketos gitlab project issues. Complaints, insults about my mother, and general snark are welcome here. If you have a problem, I'm happy to ignore you while you figure it out, so don't be shy!
Here's a flashable zip: https://gitlab.com/5ilver/apexq/blob/master/20190329-pmos-samsung-apexq.zip
I can't test it (no working screen), but the root/boot heimdall flash version is working for me via download mode at least far enough to ssh into the phone and poke around.
Hi i managed to follow your Steps.
Thanks for that wonderfull Howto.
Installed FatToad on my regular Phone and PostmarketOS from you on my Spare t-699.
Your Display is broken?..how is that happend?
Managed to make a flashable CWM Zip and i did not go further than the PostmarketOS Screen.
ADB is not working and now after use Install via Fastboot..it stay postmarketscreen.
I let it stay the next 10 Minutes on this..maybe something usable come out
btw:
Do you come from Germany?
Maybe i can Donate you with my Spare T-699?
Many Thanks for your work..a second Post from me will come when i am little further.
And i had to laugh loud in the Moment where i saw that i can use simply the git Software Downloader for Gitlab too..and i thought i need a special Gitlab Software :good:
Thanks for teaching me this
ingoreis said:
Hi i managed to follow your Steps.
Thanks for that wonderfull Howto.
Installed FatToad on my regular Phone and PostmarketOS from you on my Spare t-699.
Your Display is broken?..how is that happend?
Managed to make a flashable CWM Zip and i did not go further than the PostmarketOS Screen.
ADB is not working and now after use Install via Fastboot..it stay postmarketscreen.
I let it stay the next 10 Minutes on this..maybe something usable come out
btw:
Do you come from Germany?
Maybe i can Donate you with my Spare T-699?
Many Thanks for your work..a second Post from me will come when i am little further.
And i had to laugh loud in the Moment where i saw that i can use simply the git Software Downloader for Gitlab too..and i thought i need a special Gitlab Software :good:
Thanks for teaching me this
Click to expand...
Click to collapse
Awesome! This is great to see! I'm in the US, but thanks anyway. Ok so the kernel booted on your phone. This is cool. Now the next steps are to get X working so we can use the screen and run programs. If the phone is connected to your computer with a usb cable, it should identify itself as a usb ethernet adapter that you can get a dhcp address from. Something like sudo dhclient -v enp0s19f2u1 and then ssh [email protected] should allow you to access the phone. The errors are in /var/log/Xorg.log.0 I think. Need to get that dumped and give it a good hard look, maybe enable some fallback display mode or something. Need to probe around in /dev/input too and see what sort of input devices are detected. This is good progress though. We're getting the phone back into a supportable state.
Not sure how my display broke. One day it was just blank when I tried to wake it, but it worked after a few tries. It got harder and harder to use with the keyboard out, and so I got another one. When I started working on this port the screen had to be held very still or it would blank out. Now, it just won't come on at all. It is possibly a bad flex cable.
silvermagnet said:
If the phone is connected to your computer with a usb cable, it should identify itself as a usb ethernet adapter that you can get a dhcp address from. Something like sudo dhclient -v enp0s19f2u1 and then ssh [email protected] should allow you to access the phone.
Click to expand...
Click to collapse
had this Error in my Linux:
Code:
[email protected]:~/Downloads$ sudo dhclient -v enp0s20f0u10
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/enp0s20f0u10/62:3d:43:73:74:09
Sending on LPF/enp0s20f0u10/62:3d:43:73:74:09
Sending on Socket/fallback
DHCPREQUEST of 172.16.42.2 on enp0s20f0u10 to 255.255.255.255 port 67 (xid=0x2be8f493)
DHCPACK of 172.16.42.2 from 172.16.42.1
RTNETLINK answers: File exists
bound to 172.16.42.2 -- renewal in 395804 seconds.
[email protected]:~/Downloads$ ssh [email protected]
ssh: connect to host 172.16.42.1 port 22: Connection refused
[email protected]:~/Downloads$
Unfortunaly Connection Refused @ Port 22
But you are right..Kernel seem to boot fine and it is a "NetworkDevice"
Phew Ameria is on the other Side of the World from here..thanks again for help to get it work.
Btw i saw an Android Device in my File Explorer from Linux but it cannot be mounted via MTP.
Edit:
I can connect but need a Password
ingoreis said:
had this Error in my Linux:
Code:
pando[email protected]:~/Downloads$ sudo dhclient -v enp0s20f0u10
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/enp0s20f0u10/62:3d:43:73:74:09
Sending on LPF/enp0s20f0u10/62:3d:43:73:74:09
Sending on Socket/fallback
DHCPREQUEST of 172.16.42.2 on enp0s20f0u10 to 255.255.255.255 port 67 (xid=0x2be8f493)
DHCPACK of 172.16.42.2 from 172.16.42.1
RTNETLINK answers: File exists
bound to 172.16.42.2 -- renewal in 395804 seconds.
[email protected]:~/Downloads$ ssh [email protected]
ssh: connect to host 172.16.42.1 port 22: Connection refused
[email protected]:~/Downloads$
Unfortunaly Connection Refused @ Port 22
But you are right..Kernel seem to boot fine and it is a "NetworkDevice"
Phew Ameria is on the other Side of the World from here..thanks again for help to get it work.
Btw i saw an Android Device in my File Explorer from Linux but it cannot be mounted via MTP.
Edit:
I can connect but need a Password
Click to expand...
Click to collapse
The password is password
silvermagnet said:
The password is password
Click to expand...
Click to collapse
Thank you tried it but did not work.
"ssh [email protected]"
gave me an error
"ssh: connect to host 172.16.42.1 port 22: Connection refused"
and
"ssh [email protected]"
ask for a Password and do not accept "password"
I am near..only this last Step to get the Important Files
Now i tried another USB Port and something is working but not working:
Code:
[ 8406.035731] rndis_host 1-9:1.0 enp0s20f0u9: unregister 'rndis_host' usb-0000:00:14.0-9, RNDIS device
[ 8406.366663] usb 1-9: new high-speed USB device number 34 using xhci_hcd
[ 8406.515928] usb 1-9: New USB device found, idVendor=18d1, idProduct=d001
[ 8406.515934] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8406.515938] usb 1-9: Product: Android
[ 8406.515942] usb 1-9: Manufacturer: Android
[ 8406.515945] usb 1-9: SerialNumber: 0123456789ABCDEF
[ 8406.519381] rndis_host 1-9:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-9, RNDIS device, 66:93:21:86:d9:50
[ 8406.529243] rndis_host 1-9:1.0 enp0s20f0u9: renamed from usb0
[ 8406.555024] IPv6: ADDRCONF(NETDEV_UP): enp0s20f0u9: link is not ready
[email protected]:~/Downloads$ sudo dhclient -v enp0s20f0u9
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/enp0s20f0u9/5a:14:3c:18:78:36
Sending on LPF/enp0s20f0u9/5a:14:3c:18:78:36
Sending on Socket/fallback
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 3 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 5 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 6 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 11 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 13 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 9 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 11 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 20 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 20 (xid=0x810a2043)
but do not stop that
ingoreis said:
Thank you tried it but did not work.
"ssh [email protected]"
gave me an error
"ssh: connect to host 172.16.42.1 port 22: Connection refused"
and
"ssh [email protected]"
ask for a Password and do not accept "password"
I am near..only this last Step to get the Important Files
Click to expand...
Click to collapse
172.16.42.2 is your own computer. Maybe ssh didn't successfully start on the phone. Try restarting it. Don't worry about getting the logs for me, I have a copy from mine. I just need to go through them and find the errors.
Restarting phone did not start ssh but i have an Idea:
gmtp had Errors too because i tried to vonnect with MTP
HTML:
[email protected]:~/Downloads$ gmtp
Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone.
Device 1 (VID=16c0 and PID=0489) is UNKNOWN in libmtp v1.1.13.
Please report this VID/PID and the device model to the libmtp development team
LIBMTP PANIC: Unable to find interface & endpoints of device
Fehler: Verbindung zu Gerät nicht möglich.
LIBMTP PANIC: Trying to dump the error stack of a NULL device!
LIBMTP PANIC: Trying to clear the error stack of a NULL device!
Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone.
Device 1 (VID=16c0 and PID=0489) is UNKNOWN in libmtp v1.1.13.
Please report this VID/PID and the device model to the libmtp development team
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt
Fehler: connection not possible.
Edit:
I have the Connection now
EditEdit:
Here is the Log that you want inside the Attachments:
EditEditEdit:
Fixed the Logfile..last Part was missing
Hey this is great! I still take out my Relay "for a spin" occasionally, so I'm thinking of testing this.
I'm guessing the .zip is flashable withTWRP, not CWM?
I don't have any dev tools and I'm running Win10 (been ages since I've had a running Linux rig), so I'm not sure how much feedback I can provide. Should I wait until the build is a little more stable?
cucumbers said:
Hey this is great! I still take out my Relay "for a spin" occasionally, so I'm thinking of testing this.
I'm guessing the .zip is flashable withTWRP, not CWM?
I don't have any dev tools and I'm running Win10 (been ages since I've had a running Linux rig), so I'm not sure how much feedback I can provide. Should I wait until the build is a little more stable?
Click to expand...
Click to collapse
It should work in either recovery, or at least the documentation I've seen so far does not specify. You shouldn't need any tools, just put the image I linked from gitlab on an sd card. Stability... well things are quite stable in their current very broken state. I ran my phone for almost a week straight, so no worries there. Getting X working is probably the next big step. It will likely be a while. The frame buffer driver doesn't seem to be giving very useful errors but I'm sure someone has bumped into the same problems on another phone, so we'll get there.
i tried little with startx xinit and others
and it seem to need xterm but xterm is not installed
(see the attached Picture)
I tried to change the Config from Display 0 to Display 1 but no success
and no Screen on the Relay for now.
And a little good Information:
Touchscreen is working.
When i touch the Display i see touched Coordinates in dmesg
Sometimes i had the Message that Xserver is already running on Display 0
but after trying some Things not more.
Starting X over ssh probably will not work since your local term is not graphical. I tried putting a default screen section in the xorg config, but that didn't make the X service work. I've read that disabling 3d accel for the msm chipset in the kernel can help so I'll try that next.
No luck with disabling MSM_KGSL, seems to have the same stream of errors followed by a segfault in the X log. I also tried including an additional package xf86-video-fbdev which had no effect either (I think it must have already been pulled in by a dependency). The msm-fb-refresher package appears in the similar looking samsung-jflte APKBUILD, so I'll try that later today.
Maybe the weston graphical environment is worth a try instead of X? Seems some other msm based phones like it.
silvermagnet said:
No luck with disabling MSM_KGSL, seems to have the same stream of errors followed by a segfault in the X log. I also tried including an additional package xf86-video-fbdev which had no effect either (I think it must have already been pulled in by a dependency). The msm-fb-refresher package appears in the similar looking samsung-jflte APKBUILD, so I'll try that later today.
Maybe the weston graphical environment is worth a try instead of X? Seems some other msm based phones like it.
Click to expand...
Click to collapse
About that i have no Knowledge but thanks that you try so much
any News?
I dropped my phone, got a dead spot in the camera, got another relay on ebay, and here we are with a perfectly good dev phone with a good screen. So I can hack on the display now. X11 is broken, but weston works fine. No update on last time, just select weston instead of xfce4 in pmbootstrap init. I'll get hackin on the 'red' problem, which from what I gather is pretty common and easily patchable.
https://i.imgur.com/vy18cjJ.jpg
Wow Great News,thank you for still working on it.
When you send me your Paypal Adress via PM then i want to donate little Bit for you because you bought another T-699 over Ebay for us all.
This Picture look good and this "Red Error" is little bit funny and
i am glad to see Weston is working.
Touchscreen worked good?
The touch screen worked great. The keyboard even works too! Some small gotchas, like numeric symbols being selected with shift instead of alt, but it works!
https://i.imgur.com/lE3x4OK.jpg
Related
The attached package contains USB to Ethernet driver pack for Honeycomb v3.2
It extends the support of stock ASUS kernel for USB to Ethernet adapters.
This thread is continuation of: http://forum.xda-developers.com/showthread.php?t=1224660
Installation and activation
-------------------------------------
- Install ZIP package via recovery
- Attach USB to Ethernet device to USB on the docking
- To setup network configuration execute the following sequence from terminal:
Code:
su
usb_ethernet
Known supported adapters
------------------------------------
- EDIMAX EU-4207 (http://goo.gl/OqR6X)
- Cisco USB200M (http://goo.gl/0I0W5)
- Cisco USB300M (http://goo.gl/g9sf1)
- AXIS based unbranded from DealExtreme (http://goo.gl/hn06o)
- QF9700 based unbranded (http://goo.gl/yKMyx)
- Apple USB Ethernet Adapter (http://goo.gl/RfWaT)
- Belkin F5D5055 (http://goo.gl/4FQle)
- SMC EZ Connect USB (SMC2206USB/ETH) (http://goo.gl/FtdOv)
- "Maxvalue" USB2 to 10/100 Ethernet adaptor (http://goo.gl/8qzfe)
- D-Link DUB-E100 (http://goo.gl/JJTCo)
- Airlink 101 USB 2.0 to Ethernet Adapter(http://goo.gl/rjgMz)
- BUFFALO LUA3-U2-ATX (http://goo.gl/0Emwq)
(Please report which devices works for you)
Known issues
------------------------
USB to Ethernet is not supported explicitly by Honeycomb v3.2 so there are some constrains in working with these devices:
- Executing 'usb_ethernet' with WiFi enabled is not recommended
- Some apps don't recognize that network connection is enabled via USB to Ethernet
Source
--------------
Source can be downloaded from github: https://github.com/MarkLuk/USB_Ethernet_DriverPack
Expanding the driver pack is quite straightforward:
- Add new driver source to 'src/drivers' folder
- Recompile by executing 'make' in the driver package root
Comments, contributions and suggestions are welcome
Download
------------------
USB to Ethernet Driver Pack v0.1: https://github.com/downloads/MarkLu...SB_Ethernet_DriverPack.v0.1.[Quiethinker].zip
Awesome work mate, I didn't know there were usb to ethernet adapters
Arobase40 said:
I had much hope, but sounds like this is not working with my device.
Can't even ping the default gateway... ^^
I might have one of the 2 latter models : AXIS or QF9700 based unbranded... I have to check again.
It was working quite fine with Android-x86 : Froyo-x86 or Gingerbread-x86.
I'll try to check if I can see something wrong in the source code, when I have time... ^^
Thanks anyway for the try.
Click to expand...
Click to collapse
Connect your device to Linux box and check what 'lsusb' returns.
Arobase40 said:
Bus 001 Device 005: ID 9710:7830 MosChip Semiconductor MCS7830 Ethernet
With lsmod, I have : usbnet 26147 1 mcs7830
---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------
Forgot to say, I receive a DHCP address and I can ping on it, but couldn't pass beyond the gateway...
Click to expand...
Click to collapse
OK so the driver seems to work.
Please attach the output of the following commands from Transformer terminal:
'route'
'ifconfig'
Arobase40 said:
route : invalid argument
ifconfig : nothing
Click to expand...
Click to collapse
What ROM do you have? Is it rooted?
Arobase40 said:
It's Revolver 3.2 created by gnufabio (I guess) and yes rooted...
Click to expand...
Click to collapse
Strange i'm using the same ROM.
Check that you using 'usb_ethernet' with superuser permissions:
Code:
su
usb_ethernet
if this doesn't work, try to set your routing and IP manually:
Code:
su
ifconfig eth0 YOUR_MANUAL_IP (like 192.168.0.40) netmask 255.255.255.0 broadcast YOUR_NETWORK_PREFIX.255 (like 192.168.0.255)
route add default gw YOUR_GATEWAY_IP (like 192.168.0.1)
setprop net.dns1 8.8.8.8
Now check that the setting is working by:
Code:
ping google.com
Arobase40 said:
Yeah, I typed all these commands, but sounds like the problem comes from the route command !!! ^^
Whatever argument I type I have an "Invalid argument" response. Even with a single route without any argument...
Is it your own version of route or the one supplied by busybox (I have the latest version installed from the Market) ?
At least, we have narrowed the issue...
Click to expand...
Click to collapse
Maybe the problem is with the busybox from the market.
I suggest re-installing the ROM, not install the busybox from the market and re-test the device.
Arobase40 said:
Before reinstalling the ROM again, I first uninstall busybox, then Titanium just to be sure.
But this doesn't change anything : route still responds "Invalid argument" ???
So where does this route version come from ??? From revolver or your pack ? ^^
Click to expand...
Click to collapse
'route' is a busybox command.
Busybox comes with Revolver ROM build-in.
I don't know if Market's Busybox destroys ROMs busybox installation or not, and whenever uninstalling it helps to recreate the previous state of busybox (pathes, softlinks, etc).
There might be also that there is some issue with your busybox softlinks.
You can try execute 'busybox route' instead of 'route'.
Suggest using the command:
busybox route add default gw (IP to your router)
~J
Hi,
1) Thank you very much for this
2) It works great
3) I'm on Prime 1.9+21a
4) I use Apple Dongle
5) This was typed while using LAN with Wifi Off from settings.
PS: Thank you again.
Thank you! I have 2 adapters, the $6.99 unbranded from DealExtreme and a Belkin F5D5055 Gig adapter, and they both work.
Be careful: the DealExtreme adapter mentioned in the OP might not always be the ASIX chipset! I ordered the exact same model and got a MosChip Semiconductor MCS7830 chipset. Fortunately, your driver pack has its driver.
The Belkin F5D5055 adapter is the ASIX chipset, so it is in your pack as well.
I had to type SU in the terminal before 'usb_ethernet' would run with the correct permissions. I do not know if it was just me, or if you should modify the OP to add the SU command as well.
Anyways, thanks again! -SysWiz
SysWiz said:
Thank you! I have 2 adapters, the $6.99 unbranded from DealExtreme and a Belkin F5D5055 Gig adapter, and they both work.
Be careful: the DealExtreme adapter mentioned in the OP might not always be the ASIX chipset! I ordered the exact same model and got a MosChip Semiconductor MCS7830 chipset. Fortunately, your driver pack has its driver.
The Belkin F5D5055 adapter is the ASIX chipset, so it is in your pack as well.
I had to type SU in the terminal before 'usb_ethernet' would run with the correct permissions. I do not know if it was just me, or if you should modify the OP to add the SU command as well.
Anyways, thanks again! -SysWiz
Click to expand...
Click to collapse
Thanks!
Updated the first post regarding 'su'.
Arobase40 said:
Sorry, took me some times to rebuild a whole proper system, from stock Asus or with Revolver 3.2, with busybox from brk rootkit 6.3 or just busybox from titanium but got just the same issue with route... ^^
Still get an DHCP IP, but can't pass through gateway or route command (invalid argument, whatever the argument)...
Click to expand...
Click to collapse
Arobase40,
Please try NOT to install external busybox (from market, brk rootkit, titanium backup, whatever).
Anyhow, did you try to use 'busybox route' instead of 'route'?
Don't forget this is Linux at heart...
For default gateway...
route add -net 0.0.0.0 netmask 0.0.0.0 gw "your gw's IP here"
Mine was: route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.10.1
Also for the DNS:
setprop net.dns1 8.8.8.8
it works, but use your DNS IP, not 8.8.8.8
You may also want to check out this thread here: http://forum.xda-developers.com/showthread.php?p=17128491#post17128491 a little old, but still pertinent (maybe)
Paul
SMC EZ Connect USB (SMC2206USB/ETH) works fine - using ROM Prime 1.9.1 - Thanks !!
Great job!
Now, I want the same thing for my Huawai 3G USB stick!
Quiethinker said:
The attached package contains USB to Ethernet driver pack for Honeycomb v3.2
It extends the support of stock ASUS kernel for USB to Ethernet adapters.
This thread is continuation of: http://forum.xda-developers.com/showthread.php?t=1224660
Installation and activation
-------------------------------------
- Install ZIP package via recovery
- Attach USB to Ethernet device to USB on the docking
- To setup network configuration execute the following sequence from terminal:
Code:
su
usb_ethernet
Known supported adapters
------------------------------------
- EDIMAX EU-4207 (http://goo.gl/OqR6X)
- Cisco USB200M (http://goo.gl/0I0W5)
- Cisco USB300M (http://goo.gl/g9sf1)
- AXIS based unbranded from DealExtreme (http://goo.gl/hn06o)
- QF9700 based unbranded (http://goo.gl/yKMyx)
- Apple USB Ethernet Adapter (http://goo.gl/RfWaT)
- Belkin F5D5055 (http://goo.gl/4FQle)
- SMC EZ Connect USB (SMC2206USB/ETH) (http://goo.gl/FtdOv)
(Please report which devices works for you)
Known issues
------------------------
USB to Ethernet is not supported explicitly by Honeycomb v3.2 so there are some constrains in working with these devices:
- Executing 'usb_ethernet' with WiFi enabled is not recommended
- Some apps don't recognize that network connection is enabled via USB to Ethernet
Source
--------------
Source can be downloaded from github: https://github.com/QuietThinker/USB_Ethernet_DriverPack
Expanding the driver pack is quite straightforward:
- Add new driver source to 'src/drivers' folder
- Recompile by executing 'make' in the driver package root
Comments, contributions and suggestions are welcome
Download
------------------
USB to Ethernet Driver Pack v0.1: https://github.com/downloads/QuietT...SB_Ethernet_DriverPack.v0.1.[Quiethinker].zip
Click to expand...
Click to collapse
Any chance you could port this to work with the nook since it has usb host support now ?
bled82 said:
Any chance you could port this to work with the nook since it has usb host support now ?
Click to expand...
Click to collapse
Nook doesn't have honeycomb yet, and uses different kernel version.
Unfortunately i don't have enough time to port this and i don't have this device available for testing.
I prefer to spend the little time i have to enhance the experience of my Transformer
Maybe you can ask some Nook kernel devs to take a look here. I'll be glad to help out.
SalsaForte said:
Great job!
Now, I want the same thing for my Huawai 3G USB stick!
Click to expand...
Click to collapse
Take a look here: http://forum.xda-developers.com/showthread.php?t=1259677
UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/
well I see you fixed it. did you get adb going?
Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk
are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.
Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone
Hi,
I’ve been working on trying to connect my USB GPS dongle (Chipset: Ublox 6) to my tablet through USB OTG Cable. Since my tablet isn’t popular (Can’t find on the forum’s list), I had to do it myself.
(My knowledge about Linux isn’t that good (I’m a high school student who is on summer vacation), please forgive me if I made a mistake )
1.Ublox said the driver for Linux is cdc-acm, so I downloaded from a website and tried to install the kernel module (cdc-acm.ko) through insmod, but a vermagic error came up, said that the module’s version is 3.0.8 and mine is 3.0.8+, I tried using insmod –f , still no good luck.
2.Then I tried to modify the module’s vermagic with a HexEditor, install it again, but I got a “Segmentation falut” error.
3.Then I tried to use “busybox modprobe cdc-acm”, but it says “cannot parse modules.dep”, so I tried to create the folder “/lib/modules/3.0.8+” manually (I know this could be silly), then “busybox depmod”, finally run “busybox modprobe cdc-acm” again, but still the same error.
4.Then I remember that when I plug in the device, dmesg said
“usb 1-1: new full speed USB device using….”
“usb 1-1: New USB device found, idVendor=1546, idProduct=01a6”
Then nothing happened.
5.At last, I found out that I have “usb_modeswitch.d” in /etc
And my device profile isn’t listed there, but how could I know my device’s profile?
I know the vendor, the product, but how about the “MessageContent”?
By the way, what’s the difference between “DefaultVendor” and “TargetVendor”, “DefaultProduct” and “TargetProduct”
I know the post may be too long,
But to sum up, Is it possibly going to work if I create my Device Profile and everything will work out?
I still doesn’t have “cdc-acm.ko” install yet. (Though I already put it in /system/lib/modules)
By the way, I don’t have the folder /dev/ttyusb0 /dev/usb/tty0
I only have /dev/bus/usb/001 with nothing in it.
Sorry again for my bad Linux knowledge.
Thanks A Lot!!!
Golden Chang
hi everyone i've found another thread about this problem but no one answered to me so i decided to start a new thread.
I'm trying to unbrick my one s but I'm blocked at the second command of the tutorial when I've to enter the command ls dev/sd* etc..
I'm trying in the right way: when 'qualcomm inc. ecc ' disappear I do the command in the second window of the terminal (I alredy tried faster and faster) but I always had back the same yellow line without sd*4 and 12 that i need...
can you help me??? sorry for my bad english!
Try to unplug and replug the USB cable. I have the same problem and after unplug and replug usb cable that work. Maybe you must hold power down on your phone for about 10 seconds after replug
If that does not work, restart the computer
jac10000 said:
Try to unplug and replug the USB cable. I have the same problem and after unplug and replug usb cable that work. Maybe you must hold power down on your phone for about 10 seconds after replug
If that does not work, restart the computer
Click to expand...
Click to collapse
I've tried to unplug and replug and also to restart my pc,but I recive everytime the same line without what I need ..
I'm running ubuntu 12.10 fully installed on an external hdd..can this be a problem?
Have you really brick your phone with killp4 ?
You should talk about your problem in this thread beacause you would have more answers: http://forum.xda-developers.com/showthread.php?t=1990043
jac10000 said:
Have you really brick your phone with killp4 ?
You should talk about your problem in this thread beacause you would have more answers: http://forum.xda-developers.com/showthread.php?t=1990043
Click to expand...
Click to collapse
I've not bricked the phone with the guide,but after I flashed an RUU and tried to update OTA to JB..then,during the automatic process ,the phone stopped band gone bricked . so I can 't follow the guide from the start and the files that I need ha ve been passed to me by some people on another site.
PS.I can't write on that thread because I ve not 10 posts yet
UMBYDD said:
hi everyone i've found another thread about this problem but no one answered to me so i decided to start a new thread.
I'm trying to unbrick my one s but I'm blocked at the second command of the tutorial when I've to enter the command ls dev/sd* etc..
I'm trying in the right way: when 'qualcomm inc. ecc ' disappear I do the command in the second window of the terminal (I alredy tried faster and faster) but I always had back the same yellow line without sd*4 and 12 that i need...
can you help me??? sorry for my bad english!
Click to expand...
Click to collapse
Notes:
I did this procedure yesterday - I cry once or twice! - but it will 100% work. Relax!
It can be very,very hard the 'working time' is only seconds - I was not quick enough to do a ls in the other window. I suspect this is your problem.
On my TMobile HTC One S, I had to hold the power button for 15 seconds then release ( not ten nor thirty ). I suspect this could be your problem too.
On some linux distro's the kernel module qcserial will block the emmc_recover program ( not your problem )
On some linux distro's udev will be too slow and the procedure cannot work => Debian based distro's seem to work better. ubuntu should be fine
On some linux distro's /dev/ttyUSB0 is taken by other devices - this is hard coded in emmc_recover. Often this is used by USB to serial devices or internal modems in laptops ( also not your problem )
The 'new' drive letter is always one more. i.e. One a two disk rig ( sda & sdb ) the phone will be sdc
=> My suggestion to all is: Recover mmcblk0p4 ( bakp4 ) first as it's only one write - this is step 12. If this works and the phone is okay (and you are okay!), brick it again then do the full procedure.
This may give you better visual:
1) Run a shell script or enter in a linux shell:
while true
do
ls -al /dev/sd*
echo =========
sleep 0.2
done
2) While above running, connect the phone and do the 15 second power button push then release. Remember to verify with the suggested command ( watch -n 1 lsusb )
With reference and much thanks to the software and forum authors for http://forum.xda-developers.com/showthread.php?t=1990043. I cannot post their either as I am new user too.
Hope this helps, good luck
bluebenno said:
Notes:
I did this procedure yesterday - I cry once or twice! - but it will 100% work. Relax!
It can be very,very hard the 'working time' is only seconds - I was not quick enough to do a ls in the other window. I suspect this is your problem.
On my TMobile HTC One S, I had to hold the power button for 15 seconds then release ( not ten nor thirty ). I suspect this could be your problem too.
On some linux distro's the kernel module qcserial will block the emmc_recover program ( not your problem )
On some linux distro's udev will be too slow and the procedure cannot work => Debian based distro's seem to work better. ubuntu should be fine
On some linux distro's /dev/ttyUSB0 is taken by other devices - this is hard coded in emmc_recover. Often this is used by USB to serial devices or internal modems in laptops ( also not your problem )
The 'new' drive letter is always one more. i.e. One a two disk rig ( sda & sdb ) the phone will be sdc
=> My suggestion to all is: Recover mmcblk0p4 ( bakp4 ) first as it's only one write - this is step 12. If this works and the phone is okay (and you are okay!), brick it again then do the full procedure.
This may give you better visual:
1) Run a shell script or enter in a linux shell:
while true
do
ls -al /dev/sd*
echo =========
sleep 0.2
done
2) While above running, connect the phone and do the 15 second power button push then release. Remember to verify with the suggested command ( watch -n 1 lsusb )
With reference and much thanks to the software and forum authors for http://forum.xda-developers.com/showthread.php?t=1990043. I cannot post their either as I am new user too.
Hope this helps, good luck
Click to expand...
Click to collapse
well..first of all this is not a problem of speed.. I'm really really quick! then the 10 seconds procedure works well for me..after 10 sec the qualcomm. inc. etc disappear.
I have the bakp4 because I take it from another friend on the forum.
now I've not comprise so well your procedure ..can you explain me better the 2 steps? thank you!
ps.I've tried to do the step 12 but it tells me COMMAND NOT FOUND
First of all, I have a HTC Droid DNA. I was searching for about a year. Finally I got a solution for my problem and I know some of you are still out there with no solution.
The Fail Code is: Unknown USB device (Device Descriptor Request Failed)
Windows has stopped this device because it has reported problems. (Code 43)
So I found a German solution where you have to go to regedit.
Step 1: You need to install the HTC drivers (Google, Samsung etc...) in the normal mode your PC will find your phone, but when you turn into Fastboot you get that error "Unknown USB device (Device Descriptor Request Failed) "
Step 2: Make sure you see that error in your Device Manager under USB - Controller
Step 3: Open "regedit"
Step 4: Navigate to : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags
Step 5: Create a new Key called
0BB40FF00100
Step 6: In that Key you create a Binary Value
Name: SkipBOSDescriptorQuery
Value: 01 00 00 00 (ignore the "0000" at the beginning)
Step 7: Reconnect the Phone and enjoy your FIX
I hope I helped you. I can just tell you that it worked for me. I m not sure if it works on all HTC devices.
tried it with a S7 right now, didnt work. thanks for your post tho!
Had the solution for windows 8.1, from a blog on microsoft MSDN. (Sorry can't link to it. Since I'm new @ xda)
But as it turned out the Datatype for SkipBOSDescriptorQuery has changed from windows 8.1 to 10. Instead of a DWORD Value in Windows 8.1 it should be a Binary Value in Windows 10 .
So thanks :good: Now I can connect via fastboot to my HTC Incredible S.
Ps. Google this:
why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43
And blogpost will show as top result
Thank you very much the regedit method worked for sure..
I spent 5 hours on my computer and laptop different usb cables different ports installing uninstalling drivers and ADB nothing
Thanks BoBo Rich:good:
Thnx!!
Didn't work for HTC Explorer (Pico)
Worked with the HTC Aria on Win10 x64!
Thanks a ton.
edit: Hrm. Seems to have cropped up again. Time to continue the battle *sigh*
edit 2: Got it! Thankfully I had a Win7 laptop that I was able to fire up. The HTC Aria's fastboot hardware ID is "USB\VID_0BB4&PID_0FFF&REV_0100" which means the vvvvpppprrrr is 0BB40FFF0100. So follow the instructions above but using the key of 0BB40FFF0100
Has anyone else gotten this to work?
My Pixel XL isn't recognized at all when plugged in while in system, but it shows up as unrecognized when plugged in while in fastboot. But despite installing the drivers, Windows still refuses to recognize the phone. I tried the various solutions in this thread, but none of them worked. Perhaps it's because my Pixel's fastboot hardware ID is different, but I can't seem to find out what it is.
work perfectly for htc one xl (evita). Thanks !!
Thanks
After 48 Hours of searching!! thanks man! HTC ONE S (Ville)
Thanks! I have this problem with my Shield TV Pro, will try this after work.
Here's some PowerShell code for doing the registry editing, if anyone is interested.
Code:
#Requires -RunAsAdministrator
[string] $Path = 'HKLM:\SYSTEM\CurrentControlSet\Control\usbflags\0BB40FF00100'
[string] $Name = 'SkipBOSDescriptorQuery'
if ($false) {
# Create the path if not exist
if (-not(Test-Path -Path $Path)){New-Item -Path $Path -ItemType 'Directory'}
# Set "SkipBOSDescriptorQuery" to $true
Set-ItemProperty -Path $Path -Name $Name -Value 1 -Type 'DWord'
# Set "SkipBOSDescriptorQuery" to $false
Set-ItemProperty -Path $Path -Name $Name -Value 0 -Type 'DWord'
# Remove item
Remove-ItemProperty -Path $Path -Name $Name
# Remove path and item(s)
Remove-Item -Path $Path -Recurse -Force
}
Edit: This did not work for my Shield TV 2015 Pro unfortunately..
The error changes to "Port Reset failed". Error code remains the same 43. In my case I am trying to connect an LG G3 D858HK. I have tried many different cabels but no solution.
Unknown usb device error Motorola
Doesn't work on lg v20... Haven't been able to fix this issue for a while now..
Thanks for the info mate !
The registry key worked just great in my Windows 10 x64 computer at home and at my work laptop.
I have a Huawei P9 mobile Device.
Had this issue and nothing i tried seemed to work.
Your key did.
Thanks again !!!:good::good:
V20 Method prior to attempt....
@texas### whos still having trouble with a V20 stuck in the firmware screen ( like me) and I have a theory so I'm posting this prior to attempting it but someone please let me know if I have this wrong.
I read this post on the first page of the thread by someone whos name I've forgotten now (sorry) but they wrote....
--------------- edit: Hrm. Seems to have cropped up again. Time to continue the battle *sigh*
edit 2: Got it! Thankfully I had a Win7 laptop that I was able to fire up. The HTC Aria's fastboot hardware ID is "USB\VID_0BB4&PID_0FFF&REV_0100" which means the vvvvpppprrrr is 0BB40FFF0100. So follow the instructions above but using the key of 0BB40FFF0100 -----------------------
and based on this --- my V20 hardware ID reads "USB\VID_0000&PID_0002\5&2BF451F8&0&2" or rather the instance path does and using this I should be able to correct the value of the binary string to fit this corresponding ID for the VVVVPPPPRRRR correct? so value will be "0000000252BF451f02" ????
Im making the key and binary value now and I'll repost results later
I'm so invested in this phone both in time and sheer ignorance of what else I can do to get this damn thing out of the firmware screen.
* I've tried loading the "LG drivers from both LG composite device and VZW versions" to no avail.
*On a side note, tapping the power button brings up a "download mode" sub screen where is searches for wifi connections and after finding mine I went ahead and tried to connect 1- normally 2- removing my wifi password 3- using the WPS button to connect, all of which ended in "connection failed" so can someone explain the actual purpose of this option if there is no way to connect? or am I finding the wrong signal so to speak>?
Thanks
I'll gladly post all of my results or screen shots, (all failed so far) using ADB, uppercut, LGUP, odin, placing TOT files on the SD card, plus a few absolutely embarrassing methods but had to try something.
Please tell me someone knows a way out of this
Otherwise start a *.bat file containing
Code:
REG ADD HKLM\SYSTEM\CurrentControlSet\Control\UsbFlags\0BB40FF00100 /v SkipBOSDescriptorQuery /t REG_BINARY /d 01000000 /f
or use this in the Run window that you can call by pressing the Windows button and R, Win+R.
DEAD
Hi
Hope there's still anyone here that could help. I got the same error {The Fail Code is: Unknown USB device (Device Descriptor Request Failed) Windows has stopped this device because it has reported problems. (Code 43)} that appears on windows when watch is connected and i press the red button. I tried to get the identifier via device manager and microsoft message analyzer but it is not detected. What else can i do?
Thanks!
didnt work for the V40. anyone got any ideas?
SuperMike393 said:
didnt work for the V40. anyone got any ideas?
Click to expand...
Click to collapse
Have you tried going to device manager > universal bus controllers, right click USB Root Hub and unintall. Restart the PPC/Laptop and reconnect the device. It works on both Xiaomi and other brands as well.