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
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?
Yesterday my phone just switch off and won't be powered on. After whole night on chager i am stuck on CM boot animation. I am able to get in recovery (TWRP), but after entering pin i am getting:
Code:
Updating partition details...
E:Unable to mount '/persist'
...done
E:Unable to mount storage
Full SElinux....
Data succesfully decrypted, new block device: '/dev/block/dm-0
.. and stuck here... Thank you for advices!
Samgarr said:
Yesterday my phone just switch off and won't be powered on. After whole night on chager i am stuck on CM boot animation. I am able to get in recovery (TWRP), but after entering pin i am getting:
Code:
Updating partition details...
E:Unable to mount '/persist'
...done
E:Unable to mount storage
Full SElinux....
Data succesfully decrypted, new block device: '/dev/block/dm-0
.. and stuck here... Thank you for advices!
Click to expand...
Click to collapse
Maybe this will help... http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Thank you, now trying mentioned howto, but things going complicated...
Fastboot detect my device:
Code:
[[email protected] sam]# fastboot devices
04e16ffbf0dc07b5 fastboot
adb does not:
Code:
[[email protected] sam]# adb devices
List of devices attached
Code:
[[email protected] sam]# lsusb
Bus 004 Device 003: ID 0bdb:1911 Ericsson Business Mobile Networks BV
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 04f2:b221 Chicony Electronics Co., Ltd integrated camera
Bus 001 Device 007: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 012: ID 18d1:4ee0 Google Inc. Nexus 4 (bootloader)
Bus 001 Device 006: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D / OP-620D
Bus 001 Device 004: ID 17ef:100a Lenovo ThinkPad Mini Dock Plus Series 3
Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Code:
root ~ $ cat .android/adb_usb.ini
0x0bdb
0x18d1
I am using Nexus tools in Arch Linux, i am getting same result with adb and fastboot utils from distribution packages. Thank you for advices.
Adb commands won't work with the phone in fastboot mode.
Have you tried flashing a stock kk, LP, or mm rom?
I don't know Linux so I can't comment on the logs.
@Samgarr
Some ROM's are not adb debuggable during boot.
You need to have three lines in ramdisk's default.prop for ROM to be able to be debugged in adb on userdebug type of builds.
If your phone is on and still adb is not working, then better flash a different ROM.
IF you're still in bootloop and are looking for a way to go out of it, since you're in fastboot,
Download nexus factory images and flash them in fastboot mode
Hope I helped
Thank you guys for your time, i think my phone have fried eMMC memory.
After i'm succesfull boot (fastboot boot recovery.img) recovery from stock ROM i tried wipe cache/data or flash stock recovery but i am constantly getting read/write errors from cache and recovery partition. Formating and recreating filesystem won't help. I bought this phone as a second hand and after removing backcover i see marks of water damage corrosions. So water damaged eMMC it is .
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 :/