Related
Hey all, I had a botched ICS upgrade on my Nexus S 4G today using Google's factory images. I can get into TWRP and into the bootloader, but my device is not recognized by any operating system that I have tried to connect it to. Swapping USB cables hasn't made a difference. My other NS4G can connect with no problems to any of these operating systems with any USB cable. While the phone does charge over USB while connected to a computer, I can't mount the SD card in TWRP and I can't use fastboot in the bootloader. With fastboot, the only message I get is "waiting for device."
Should I just cut my losses and jettison the phone? Any suggestions on how to remedy the situation?
Thanks in advance for your help.
Pitiful bump.
Which factory image did you flash? What's the exact model of your phone? See the sticker beneath the battery.
Can you boot the mobile?
What was the problem through fastboot update?
Boot into bootloader/fastboot mode. What does it display?
Please provide a lot more details about the problem.
anglergab said:
Which factory image did you flash? What's the exact model of your phone? See the sticker beneath the battery.
Can you boot the mobile?
What was the problem through fastboot update?
Boot into bootloader/fastboot mode. What does it display?
Please provide a lot more details about the problem.
Click to expand...
Click to collapse
Thanks for the reply. Pretty sure I'm bricked unless I can get JTAG. I wasn't paying attention and it was super late at night when I was flashing for my wife (who was over custom roms). I mixed up bootloaders and sent the GSM version to my CDMA Nexus. I can't boot into Android. I can get into TWRP, but can't mount USB to get any files onto the device.
Connect the phone to a Linux PC, then please post in this thread the output of the following commands:
Code:
tail /var/log/messages
Code:
lsusb
By the way you can reflash baseband/radio firmware image from recovery through ADB.
anglergab said:
Connect the phone to a Linux PC, then please post in this thread the output of the following commands:
Code:
tail /var/log/messages
Code:
lsusb
By the way you can reflash baseband/radio firmware image from recovery through ADB.
Click to expand...
Click to collapse
Thanks for the reply. I'll give it a shot in a few hours when I can get to a linux box. Part of the problem is that I get no recognition that the device is connected from any OS. I tried accessing the phone while it was in download mode through Heimdall running on Ubuntu and it couldn't see the phone.
I'll give the commands a try though and let you know. Should the phone be at the bootloader or in recovery?
You can try connecting the phone first in bootloader and then recovery. Run the above commands in both modes. Connect the phone directly, without hubs, preferably with its own cable.
anglergab said:
You can try connecting the phone first in bootloader and then recovery. Run the above commands in both modes. Connect the phone directly, without hubs, preferably with its own cable.
Click to expand...
Click to collapse
This is my output both times. The computer can't see the phone.
[email protected]:~$ tail /var/log/messages
tail: cannot open `/var/log/messages' for reading: No such file or directory
[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 04f2:0841 Chicony Electronics Co., Ltd
Bus 001 Device 004: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
Bus 001 Device 005: ID 0781:5530 SanDisk Corp. Cruzer U3 4gb SDCZ36
Bus 001 Device 006: ID 0461:4d0f Primax Electronics, Ltd
Bus 002 Device 003: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
Bus 002 Device 004: ID 148f:3573 Ralink Technology, Corp.
[email protected]:~$
Click to expand...
Click to collapse
So I have many many things I want to do with (Specifically) USB devices on my TF101. It's my baby and I use it for almost everything now, but there's still a few problems I haven't been able to shake or get other answers too.
I have a USB-MIDI cable that doesn't work (isn't detected, I think driver issue/isn't supported) Could I make a driver to do this so I can connect my keyboard to my tf and record some jams?
More Important
I have a USB - 3.5 mm converter/cable, usb in, headphone port out. It's by logitech and works fine on computer to plug any 3.5mm headphones into, not at all on android though. My headphone port is broken so this would be an amazing thing to get working properly.
Any help or guidance would be greatly appreciated, even workarounds to get these things working.
Well actually when you are rooted, you can anything!
If nothing helps, you can write your own kernel module since you can compile yourself a custom kernel.
Therefore: yes, we can
conizius said:
Well actually when you are rooted, you can anything!
Click to expand...
Click to collapse
Alright then step 1 is complete I suppose! xD I am rooted and running the tastymehICS kernel.
Gratz good luck for everything else - access to the whole system is open now!
In my opinion guvours kernel is a bit better (got less - not to say no - SoD).
Sent from my HTC Vision using XDA
I've tried both and guevor's seemed a bit more unstable for long periods of usage --just my preference, but that's beside the point xD"
So does anyone know how I could go about creating + adding drivers to the system?
You need download kernel source from asus site and prepare build environment according google andriod development site. Then you can build your kernel a start to add new features and write new kernel modules
Sent from my HTC Desire S using xda premium
I have windows drivers, all I'd need to do is port them, not necessarily write a whole new kernel X3
you don't need write whole kernel, source code for current stock kernel are on asus web site. And you don't have sources for guevor or other kernel. Is not possible to port windows driver to andriod without source code.
Try find if linux driver for you device exist. If yes, it is easy to add it to asus kerenel for transformer. And later is possible to combine your device driver (module) with some other custom kernel.
(I have working USB dvb-t stick on my transformer)
Thanks, I misread what I thought you read when I posted (if that makes any sense x.x")
Ok, it's plug and play on my linux machine too, where could I find the driver to import? So how would I make a module + combine with the guevor/tastymehics kernel?
ok, if your device is plug and play in linux, install any terminal emulation application into transformer (if you not have now) and use "lsusb" then plug your device into usb and use lsusb command again.
You should see something like BUS 001 Device 001: ID 1a4b:0003.
Then use google and try find what module is needed for device 1a4b:0003
then you need environment for building kernel and use some comamnd to build yout kernel module.
1) make menuconfig - choice module needed for your device
2) make ARCH=arm CROSS_COMPILE=mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin/arm-eabi- modules
this comple kernel modules for your device. Or you can ask for help from one of developer of custom kernel what you use to comile module what you need from his suource. Kernel and kernel modules musbe compiled from same version.
then copy modules to transformer and use insmod command to load it into kernel. Then you can plug in your device and it should work. (use dmesg to check if device driver is loaded)
Please post "dmesg" output after you plug your device in.(e.g last 10 lines) and output from lsusb.
Take a look in the thread http://forum.xda-developers.com/showthread.php?t=1513490
There is a lot of possibilities to play with usb drivers.
crossik1 said:
Please post "dmesg" output after you plug your device in.(e.g last 10 lines) and output from lsusb.
Click to expand...
Click to collapse
Dmesg (relevant lines):
usb 1-1.2: new full speed USB device number 28 using tegra-ehci
usb 1-1.2: new usb device found, idvendor=046d, idproduct=0a17
usb 1-1.2: new usb device strings: mfr=1, product=2, Serialnumber=0
usb 1-1.2: Product: Logitech g330 Headset
usb 1-1.2: Manufacturer: Logitech
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 <-- These were here already
Bus 001 Device 026: ID 05e3: 0610<-- These were here already
Bus 001 Device 028: ID 046d:0a17 <--- this is the new entry after plugging in
These are the log results asked for. I'm looking into the module now, thanks
At this point I have 4 options to fix my headphone port (that I know of)
1. Open it and try to sauter the port back together (best but, dangerous :/)
2. Get this driver stuff to work so I can use my adapter (great)
3. Bluetooth headphones (meh sound quality from my experience, but good if they work, also expensive)
4. HDMI-Out to Rca to 3.5mm to headphones. (UGH CABLES, but all I would need is the hdmi-rca cable.)
Please see if someone helps me, I've tried all the tutorials I've found and unbrick no way to flash my Asus.*
I had installed CWM Recovery 5.5.0.4 and wanted to upgrade it, so I installed Rom Manager and then click on the Install ClockWorkRecovery and I installed version 6.0.1.3, there seemed to be no problem until you restart the tablet, and I was on the logo Android and there was no more, I did a factory reset and wipe cache and nothing was the same. I just reinstalled the rom would solve the problem but when I started at the Recovery and gave him the option Install zip from sdcard, surprise: Can not mount / sdcard, so I can not access the sdcard. I do not know if the memory is screwed up or the fault of the recovery. I tried flashing with nVFlash, Easyflaser and I installed the ADB but I can not revive it.*
I do not know what else to give, the problem is that my Slider is B80 and apparently there is no system for flashing, no driver support, or can not find it.
Not completely bricked, I can enter the Recovery, but does not recognize SDcard and MicroSD.
I appreciate any help.
(Sorry for my incorrect English)
maikelbus said:
Please see if someone helps me, I've tried all the tutorials I've found and unbrick no way to flash my Asus.*
I had installed CWM Recovery 5.5.0.4 and wanted to upgrade it, so I installed Rom Manager and then click on the Install ClockWorkRecovery and I installed version 6.0.1.3, there seemed to be no problem until you restart the tablet, and I was on the logo Android and there was no more, I did a factory reset and wipe cache and nothing was the same. I just reinstalled the rom would solve the problem but when I started at the Recovery and gave him the option Install zip from sdcard, surprise: Can not mount / sdcard, so I can not access the sdcard. I do not know if the memory is screwed up or the fault of the recovery. I tried flashing with nVFlash, Easyflaser and I installed the ADB but I can not revive it.*
I do not know what else to give, the problem is that my Slider is B80 and apparently there is no system for flashing, no driver support, or can not find it.
Not completely bricked, I can enter the Recovery, but does not recognize SDcard and MicroSD.
I appreciate any help.
(Sorry for my incorrect English)
Click to expand...
Click to collapse
This should be in Q&A, not Development.
However, you can boot to CWM, then use PERI to unbrick. It will install Rogue Recovery.
If you do not have a ROM zip on the internal memory, you will need to use ADB to push a .zip file to the internal memory then flash that.
I would stick with the CWM 5.5.0.4 for the slider. The 6.X versions were never adapted, and ROM Manager does not work with Asus tablets.
http://forum.xda-developers.com/showthread.php?t=1671598
frederuco said:
This should be in Q&A, not Development.
However, you can boot to CWM, then use PERI to unbrick. It will install Rogue Recovery.
If you do not have a ROM zip on the internal memory, you will need to use ADB to push a .zip file to the internal memory then flash that.
I would stick with the CWM 5.5.0.4 for the slider. The 6.X versions were never adapted, and ROM Manager does not work with Asus tablets.
http://forum.xda-developers.com/showthread.php?t=1671598
Click to expand...
Click to collapse
Sorry if the post is not in place, would be grateful if any moderator can move.
The problem is that I can not use ADB, because if I type "adb devices" does not my ASUS in the list of devices, since none of the four drivers I've tried works. I used PERI but does not work, and says "tablet is not ready for nVFlash". I need a driver that works on Slider SL101, TF101 drivers do not work. Those in the official ASUS serve no APX mode.
Thanks for your help.
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
Give these drivers ago from this thread
pops106 said:
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
Give these drivers ago from this thread
Click to expand...
Click to collapse
Thanks but not work
Posted a video with errors and an image of the Show Log of recovery.
http://youtu.be/AUogpmDT7pA
http://i299.photobucket.com/albums/mm287/maikelbus/_DSC4593_zps2de84e2e.jpg
maikelbus said:
Posted a video with errors and an image of the Show Log of recovery.
http://youtu.be/AUogpmDT7pA
http://i299.photobucket.com/albums/mm287/maikelbus/_DSC4593_zps2de84e2e.jpg
Click to expand...
Click to collapse
I had the exact same problem when I upgraded my recovery. I used ADB successfully though. I had to push another recovery blob. I have not attempted to re upgrade since.
I am pretty sure that unless you can get ADB working, you are in trouble.
APX mode won't work because AFAIK, the SBK has not been cracked for the SL101.
Might want to try another cable - I have seen numerous cables that charge the tablet, but do not work for USB (ADB, APX or MTP connections). New cable solved it.
frederuco said:
I am pretty sure that unless you can get ADB working, you are in trouble.
APX mode won't work because AFAIK, the SBK has not been cracked for the SL101.
Might want to try another cable - I have seen numerous cables that charge the tablet, but do not work for USB (ADB, APX or MTP connections). New cable solved it.
Click to expand...
Click to collapse
I bricked my th101 and could not use Adb either. I had a bad cable. Order a new non OEM and it worked. Unbricked and happy again. Did not even need to use adb push just a all in one tool. Hope u get it working again.
Sent from my Galaxy Nexus using Tapatalk 2
Ok, try another cable to see if we are
lucky and commented, thanks to all
maikelbus said:
Ok, try another cable to see if we are
lucky and commented, thanks to all
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1681155
Maybe give this a blast as well, it worked for everyone one i have flashed.
Cheers
pops106 said:
http://forum.xda-developers.com/showthread.php?t=1681155
Maybe give this a blast as well, it worked for everyone one i have flashed.
Cheers
Click to expand...
Click to collapse
I tested the 4 versions of PERI and any works, the problem is probably the cable, but in my town costs a lot to find, Asus does not provide too purchase. Nor do I know if there are several models, is it possible to have a cable that flash and another cable that forbid? On the website of Asus only sell the charger cable, not loose. In Spain.
http://shop.asus.es/shop/es/es-ES/H...on-conectores-para-EURO-y-UK).aspx?show_popup
On Amazon there are two.
http://www.amazon.es/Mobiles®-Cable...SZK2/ref=sr_1_1?ie=UTF8&qid=1361305799&sr=8-1
http://www.amazon.es/GTMax-Cable-me...1_fkmr0_1?ie=UTF8&qid=1361305799&sr=8-1-fkmr0
It's a great price, but do not know if the original cable, and if it will work.
The cable I have now bought it at Deal Extreme, so I guess it is not original, I know. The original purchase box broke down quickly.
Either should work. I would probably go with the bottom one, no reason why.
Sent from my Galaxy Nexus using Tapatalk 2
Hi,
I have finally decided to buy the cable GT-max, I consulted the dealer and assures me that is identical to the original Asus and because the other is identical to the one I bought last year in Dealextreme:
http://dx.com/p/usb-data-charging-cable-for-asus-eee-pad-transformer-tf101-95cm-length-114609
While I get the new cable, I decided to install Android ADB in Ubuntu and I have the same problem, the tablet is not recognized. I have setup several parameters in the file 51-android.rules and none works:
SUBSYSTEM==”usb”, ATTRS{idVendor}=="0955", ATTRS{idProduct}==:"7820", MODE=”0666″
SUBSYSTEM==”usb”, ATTRS{idVendor}=="0955", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955:7820", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", ATTRS{idProduct}=="7820", SYMLINK+="libmtp-%k", MODE="0666"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0955",ATTRS{idProduct}=="7820",MODE="0666",OWNER="rehcla" #Asus Transformer
Can anyone tell me what is the correct line for the Asus?
with the command lsusb I get the following:
[email protected]:~$ lsusb
Bus 008 Device 002: ID 040b:2011 Weltrend Semiconductor
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0955:7820 NVidia Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04f2:b083 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
While ADB does not recognize the device, I'm not able to do anything, do you?,
Reconsidering, I think the recovery 6.x after installing updated the Rom unchecked USB debugging mode, so it is possible that all problems are for that reason, then format the rom, and now can not turn on USB debugging.
Is there any way by the ADB to enter the bootloader and force the flash? memory left clean, and you can install everything from scratch? I am new to this.
regards
maikelbus said:
with the command lsusb I get the following:
[email protected]:~$ lsusb
Bus 008 Device 002: ID 040b:2011 Weltrend Semiconductor
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0955:7820 NVidia Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04f2:b083 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
While ADB does not recognize the device, I'm not able to do anything, do you?,
Click to expand...
Click to collapse
You are now in nvflash mode. adb never works in nvflash mode. Only nvflash works in nvflash mode.
josteink said:
You are now in nvflash mode. adb never works in nvflash mode. Only nvflash works in nvflash mode.
Click to expand...
Click to collapse
Sorry, I was confused, thinking that the ADB was used in APX mode, in normal USB mode, the tablet does not recognize either, as the new cable does not work, I'll have to send it to ASUS service center.
Thank you.
I have already received the new cable and no solution, apparently APX mode does not work on devices like my Slider B80.
As APX mode flash no way, I managed to install a compatible Samsung drivers recovery mode and I was able to install the recovery Rogue with Peri. Now I recognize the MicroSD but no internal SDCard. I tried installing the latest firware from Asus and it reads:
-- Instaling: /sdcard/WW_epad-user-9.2.1.27.zip
Finding update package...
Opening update package...
Instaling update...
assert failed: write_raw_image("/tmp/blob", "staging")
E: Error in /sdcard/WW_epad-user-9.2.1.27.zip
(status 7)
Installation aborted.
If I do a Wipe data / factory reset tells me:
--Wiping data...
Formating /Data...
Error mounting /Data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android.secure...
Error mounting /sdcard/.android.secure!
Skipping format...
Data wipe complete.
I can do now? Any idea?
Edit:
Solved! I used the HD Super Wipe Full Eeepad.zip to recreate the system partition without reboot after I installed the ROM HD Revolution 3.5.
Thank you very much to all who have helped me
Explain the solution, as I have asked private and will not usually entered in the forum, and I think it's better than staying here for anyone who has this same problem:
The problem I have is that the partition table is damaged, you have to recreate it, for it uses the full Android superwipe, and then you can already install any Rom.
You need to first install a Recovery that allows access to the MicroSD, since the internal SDCard is inaccessible.
If the current Recovery permitting, no problem. but you need to install another recovery Android do for ADB, as the slider is not supported apx, using nvflash programs are not going to run, but those using adb.
Install another recovery with peri 0.4, this tablet if you recognize the adb interface as being in recovery mode.
decompresses the peri 0.4 on the desktop.
1. connect the tablet to the pc being torn into recovery mode (no apx mode or with the tablet asus on screen)
Two. mouse right button on EasyRecoveryV0.4.bat and run as admin.
Three. you type r and hit Enter
*Out a notice that going to flash the rogue recovery, press enter
*if you connect well and see your recovery 1234567ABCD hit Enter
*recovery begins pushing, if all went well, press enter again
*flash the recovery begins, when done you will only restart the tablet, let it restart
*Now if you should see a rod installing the new recovery.
Once installed, insert a MicroSD with Android_Revolution_HD_Super_Wipe_Full_EeePad.zip I install it in the usual way. They create new Android partitions and internal SD Card.
In the MicroSD also puts your favorite rom and install it later.
This process erases the entire contents of the internal memory, but no other known remedy.
Greetings.
asus slider bricked
Hi! I would like to know if it is now possible to unbrick an asus slider with serial B80?
Fhurzel said:
Hi! I would like to know if it is now possible to unbrick an asus slider with serial B80?
Click to expand...
Click to collapse
Depends, how did you brick it, can you get to recovery, did you install a custom recovery?
hi,
maybe some of you already know, that i am working on a dualboot solution for the note2.
it is almost functional now, but i have no idea anymore, where to search for a solution for the last bug, mentioned in the titel.
the commits in question are this, for cm-10.1:
https://github.com/DerTeufel/androi...mmit/5dc8b0e77cb21562aa41981fdea65fef6945270e
and this, for samsung based roms:
https://github.com/DerTeufel/androi...mmit/a57b6da843d0b6b47071e947008bb5665099163f
both commits are similar to the changes, gokhanmoral has made to his i9300 dualboot initramfs. i could not (edit: fixed typo here, this word was missing before) see anything related (if he had similar issues) in his commits/code
as you can see in the commis, i only have switched the data partition at this point.
basically it's like this:
mounted another partition at /data
created a new data folder at data/media (now mounted in /.secondrom)
bind mount /.secondrom/media/data into the deafult /data partition
create media folder in the new /data
bind mount /.secondrom/media into the new /data/media
everything is working as expected, just connecting to usb fails. phone is going into charging mode, without usb connection notification, usb debugging/adb is also not working.
do i just reboot into primary rom, usb is working again.
could oneone give me a hint, what could be causing this?
edit: the changes don't depend on the kernel used with the initramfs. if you want to try yourself, you should be fine by just applying the changes to your initramfs.
switching between roms is done by:
echo primary > /cache/.secondaryboot
and then reboot
echo secondary > /cache/.secondaryboot
reboot
it is going to be changed by recovery normally, but i need to do some more changes, before pushing it to github
AW: usb connection non functional, after changing data partition
Just a little update, without any change to the problem.
I thought, maybe mounting the sdcard by using fuse is causing the issue. Well, it is not. I have commented it out, exported storage/sdcard0 as storage, and bind mounted data/media into it.
USB still isn't working after this.
Any other ideas are highly welcome.
Gesendet von meinem GT-N7105 mit Tapatalk 2
after some more testing, i realized, that the device gets recognized by ubuntu, running in a vm. i now can adb to it
mounting the sdcards to it, does still not work
i am still stuck at the same thing...no one an idea?
today i have realized, that my vm is recgnizing my phone as different devices, if i am using another data partition...if this isnt weird enough, it also tells me, it is a galaxys 2 (i never owned a s2, and never installed drivers for it).
this is, when it is working normally (/data unchangend):
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 052: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
this is the same device, same kernel, same rom, 5 minutes later, just mounted the other /data partition:
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 058: ID 18d1:d002 Google Inc.
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 :/