Related
Hi,
In fastboot mode my linux distro (Debian testing) can see and reboot the device:
Output of lsusb:
Bus 003 Device 011: ID 0502:33a5 Acer, Inc.
but with ./adb devices, I cannot see anything:
No trace in lsusb, debug usb is on, udev rules are ok, adb_usb.ini is ok and with ADB_TRACE="all", everything is ok except that there is no device in adb...
Any clue?
Thanks.
Ps: I did google around...
I am writing a tool under Linux as an implemention of Qpst under linux
plateform: Qualcomm msm8909
PC OS: Linux (ubuntu 12.04) with qcserial model for Gobi QDL
Actually， two protocols refered，(sahara + firehose)
I have some documents about the details of the protocols and I have implement them in C on linux,
There’s a /dev/ttyUSBx for gobi QDL,
below’s a flow on QDL mode(bricked)
PC ——a firmware bin———> PHONE // sahara protocol
PHONE runs the firmware just downloaded, programming the emmc via firehose protocol .
the program has almost done, but the success rate’s low while trying to flash the images to phone.
for example:
if there’s a image named XXX.bin (1k),
the tool will tell the firmware: “hi, i am going to send you a xxx.bin image, please flash it on sector 8787, and the it covers 2 sectors(1K)”,
the firmware:” oK, place send me the raw data of the XXX.bin”,
the tool then sends the raw data to firmware via ttyUSBx ~~
I tried so many times, but most failed though somethins It succeeded. It seems the data lost on the USB wire, , :crying:
Is there any ways to debug the serial port ttyUSBx ? I am not familiar with kernel programming.
I will insist to open source the program when the tool’s finished if it could do more help for other guys.
It’s not a duty work for company, but there’s docs ，programs and devices in work, so I am not quite sure about the legal risk ,
It’s JUST a simplified QPST (QDLtool?) for LINUX.
https://git.linaro.org/landing-teams/working/qualcomm/qdl.git/about/
usage : ./qdl --debug prog_emmc_firehose_8992_lite.mbn rawprogram0.xml patch0.xml
Great tip!
ryu_hayabusa said:
usage : ./qdl --debug prog_emmc_firehose_8992_lite.mbn rawprogram0.xml patch0.xml
Click to expand...
Click to collapse
I was experimenting with the encryption and my Lenovo Vibe K5 (a6020a40) phone was somewhat "bricked": I was able to install and play with various recovery images, but any system image kept stuck on a boot loop. I tried to restore a stock rom with QPST by I was not able to make it talk with the phone: I do not have a windows machine and I had to borrow one, with limited opportunity to tweak the operating system.
Finally I returned to my beloved Debian linux machine, compiled qdl and tried again to install the stock ROM (A6020a40_S033_160824_16G_ROW_qpst.7z, found on shreps web site).
Code:
sudo systemctl stop ModemManager
cd dir_with_mbn
# connect powered off phone and push VolumeUp+VolumeDown+PowerOn
/usr/local/src/qdl/qdl --debug prog_emmc_firehose_8929.mbn rawprogram0.xml patch0.xml
# HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0 ....
After several minutes of XML output I got a diagnostic (Chinese) screen. When I rebooted, without touching anything, the system was in recovery mode with the original recovery image. Then everything worked as usual: I flashed my Lineage 14.1 and my phone was back to life.
Thank you!
I can't help you. I do not know the answer either. Good luck though.
I have an htc Desire 526G (MT 6582), the phone was working bad, so I found a thread here on XDA about flashing the phone via Fastboot.
I use only Linux, Ubuntu, and I installed ADB and Fastboot. The procedure was OK, but the result was bad, now the phone is bricked.
So, in the same thread, I found a ROM scattered to use with SP Flash Tool and I downloaded Sp Flash Tool for LInux (SP_Flash_Tool_v5.1628_Linux) and Installed the MTK drivers. I suppose that the MTK driver is working because the pc can recognize another identical phone as "MTKXXX device".
Unfortunately the SP Tool is not able to access my phone, this is the output
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1479500736.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,131))
comboTimeout index(3) saved.
To make the "Download" I make a click on the "download" button, the tool start waiting for the connection, so I insert the usb in the phone (in power off), I tried with battery and without battery.
It's strange that I tried the connection hundreds of times, using different USB ports, cables, Full/High speed, with and w/o battery, auto detect mode, different agents and so on, and once (only once) SP tool could connect to the phone, but it said thet PMT was chamged, so I found on the net that I should format the phone, but there were no more successes in connecting.
Could someone help me in fixing this problem?
XDA Visitor said:
I have an htc Desire 526G (MT 6582), the phone was working bad, so I found a thread here on XDA about flashing the phone via Fastboot.
I use only Linux, Ubuntu, and I installed ADB and Fastboot. The procedure was OK, but the result was bad, now the phone is bricked.
So, in the same thread, I found a ROM scattered to use with SP Flash Tool and I downloaded Sp Flash Tool for LInux (SP_Flash_Tool_v5.1628_Linux) and Installed the MTK drivers. I suppose that the MTK driver is working because the pc can recognize another identical phone as "MTKXXX device".
Unfortunately the SP Tool is not able to access my phone, this is the output
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1479500736.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,131))
comboTimeout index(3) saved.
To make the "Download" I make a click on the "download" button, the tool start waiting for the connection, so I insert the usb in the phone (in power off), I tried with battery and without battery.
It's strange that I tried the connection hundreds of times, using different USB ports, cables, Full/High speed, with and w/o battery, auto detect mode, different agents and so on, and once (only once) SP tool could connect to the phone, but it said thet PMT was chamged, so I found on the net that I should format the phone, but there were no more successes in connecting.
Could someone help me in fixing this problem?
Click to expand...
Click to collapse
Hello,
Please register for a XDA account to post and reply in the forum.
Also you might try posting your query here Android Q&A Forum with all relevant details, the experts there maybe able to assist you.
Regards
Vatsal,
Forum Moderator.
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
Hi, I have recently flashed the Evolution X (Android 11) ROM to my previously bricked device. I'm trying to install some APKs but I get the device offline error:
Code:
~ $ adb install ~/usr/local/Downloads/sh.ppy.osulazer.apk
Performing Push Install
adb: error: failed to get feature set: device offline
This hasnt happened in LineageOS or Pixel Experience.
And if you ask, yes the laptop is detecting the device
Code:
~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:5521 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 025: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I tried adding the /etc/udev/rules.d/51-android.rules file with the following contents:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", GROUP="adbusers"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_fastboot"
Then restarted my computer, reloaded udev rules but it still doesnt work. Yes, my user is part of the adbusers group. Also tried as root user but same thing. I'm on Arch Linux btw.
Is there any way to fix this or do I just go back to PixelExperience/LineageOS?
rogerpanza said:
Hi, I have recently flashed the Evolution X (Android 11) ROM to my previously bricked device. I'm trying to install some APKs but I get the device offline error:
Code:
~ $ adb install ~/usr/local/Downloads/sh.ppy.osulazer.apk
Performing Push Install
adb: error: failed to get feature set: device offline
This hasnt happened in LineageOS or Pixel Experience.
And if you ask, yes the laptop is detecting the device
Code:
~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:5521 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 025: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I tried adding the /etc/udev/rules.d/51-android.rules file with the following contents:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", GROUP="adbusers"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_fastboot"
Then restarted my computer, reloaded udev rules but it still doesnt work. Yes, my user is part of the adbusers group. Also tried as root user but same thing. I'm on Arch Linux btw.
Is there any way to fix this or do I just go back to PixelExperience/LineageOS?
Click to expand...
Click to collapse
Restart your device.
SubwayChamp said:
Restart your device.
Click to expand...
Click to collapse
I've done that tons of times
rogerpanza said:
I've done that tons of times
Click to expand...
Click to collapse
Well, you didn't mention it, it looks like all is fine with Linux, it could be an error on the ROM side anyway check that you killed ADB server previously, and you don't have many devices attached to the PC. You should try running a terminal from user space like Desktop or Downloads (moving the app there) and not from the root directory to see if something change.
SubwayChamp said:
Well, you didn't mention it, it looks like all is fine with Linux, it could be an error on the ROM side anyway check that you killed ADB server previously, and you don't have many devices attached to the PC. You should try running a terminal from user space like Desktop or Downloads (moving the app there) and not from the root directory to see if something change.
Click to expand...
Click to collapse
I only have my phone plugged into my laptop, tried moving /usr/bin/adb to another folder as you said but same thing. And yeah it's most probably a ROM problem :/