search

nohajc / termux-adb

Run adb in Termux without root permissions!
MIT License
375 stars 37 forks source link

Not recognized? #21

Closed CamsShaft closed 10 months ago

CamsShaft commented 11 months ago

Hey man this would be everything I need, if it worked for me that is. Seem to be having issues with one of my devices but not sure which one or maybe both. Trying to attach an S10 G973U snapdragon android 12 using an S22 S901W snapdragon android 14. Of course they're samsung, which you love so much and is probably the dumbest company ever to try dealing with šŸ™„ haha. Your awesome program installed and everything, but I must be doing something wrong. "Termux-fastboot reboot" says and "termux-fastboot devices" just tries to do something, pauses for a split second, then goes to a new line like this: ~ $ termux-fastboot devices ~ $ I am also new to fastboot commands but have used termux often enough to know my way around a bit. I should also point out my S10 for whatever reason wants to default to master no matter what I do. I tried searching and all I could find was my drivers may need to be updated but I couldn't find anything for android to android, it was all for installing drivers on a pc, mac, etc. I'm at a bit of a standstill here and with no other ways to solve this I had to come here and bother you. The versions on termux are all up to date since I installed last night. I apologize if this is too vague. I'm not sure what other information you would need, if any, maybe I'm just dealing with some brain fog... anyways, this project would be sweet to use if only I could :) thanks for all your hard work!

CamsShaft commented 10 months ago

Also keeps throwing this error: $ fastboot devices -l < waiting for any device >

nohajc commented 10 months ago

Hi, there's the Samsung workaround mentioned in the other issue, maybe you already tried it: ANDROID_NO_USE_FWMARK_CLIENT=1 fakeroot

Otherwise, my program relies on termux-usb, so you can check directly whether your connected device is properly recognized and accessible by Termux:

$ termux-usb -l
[
  "/dev/bus/usb/002/002"
]

If the above gives you just an empty result [], it might be a hardware/firmware limitation of the Samsung device in question.

You can try with different devices (like connecting a flash drive) and see what results you get.

Anyway, if the device is not recognized, you might have better luck asking Termux developers about it...

CamsShaft commented 10 months ago

Damn, got this thrown in my face [] . I love Samsung devices, but I swear it's like a bunch of apes eating crayons and throwing poop at each other when it comes to accessibility. Every great app that does work has other apps for extra testing and they don't work. I'm pretty much stuck with a key that doesn't fit any locks and they make it extremely difficult to get super user privileges. I haven't even tried because this phone was expensive and as a bit of a novice I don't want to destroy it. Not sure what to get next, but samsung is blacklisted for me... thanks anyways and hope you continue with your tweaking work!