Hello there,
my K30 Ultra fell down and the display only shows green/purple lines when on. A display replacement costs 165 bucks for the amoled only (at least i didn't found it cheaper), so I think I would just buy a Poco F4. Unfortunately, my last backup is too long ago and i would like to access the data. But every time I connected the phone, it failed because usb debugging authentication didnt work (I tried tapping the screen everywhere).
The phone is unlocked and rooted. Any way to access it or use an external screen with it?
Thank you so much for the help!
USB debugging is your friend.
More here.
https://forum.xda-developers.com/t/...ly-has-an-unresponsive-broken-screen.4455331/
Thank you, GalaxyA325G!
I read through a lot of what you linked in that post and the farthest I got is getting my device into Recovery and getting it recognized by ADB. But then it says
PS C:\Program Files\platform-tools> adb devices
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
wgg6rwt8eipnfuto unauthorized
PS C:\Program Files\platform-tools> ./adb shell mount data
adb server version (32) doesn't match this client (41); killing...
* daemon started successfully
adb.exe: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Click to expand...
Click to collapse
So i was thinking, what if i could enable USB Debugging in TWRP? I need a couple clicks but i may be able to do it, right? Im just afraid of breaking my phone to be honest. Any others steps you could think of?
Related
Hey guys!
ill start with some specs...
running RA-hero-v1.7.0.1 on a GSM hero with 2.1. Villainrom12
When I try to connect via ADB I seem to loose connection after a couple of seconds..
If I run adb shell it just drops out or doesnt work at all.
C:\android-sdk-windows\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
if I try adb shell a couple of times again I get.
C:\android-sdk-windows\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ #
C:\android-sdk-windows\tools>
Drops out of shell before I have time to do anything.
This only happens when im in recovery mode on the phone. Not if the phone is in normal mode.
Would be very happy if someone has any idea of whats going on.
You can ONLY use ADB in the normal mode of your phone ;-) (correct me if I'm wrong)
nah.. thats not correct.. I am supposed to be able to use adb in recovery..
hmm.. I was never able to use ADB in recovery..
its a feature in RA-hero-v1.7.0.1
anvendarnamn said:
its a feature in RA-hero-v1.7.0.1
Click to expand...
Click to collapse
ohh.. okay, well I'm not at that recovery rom yet, the version I'm running works fine ;-)
I kinda need it to use PSFreedom :/
anvendarnamn said:
I kinda need it to use PSFreedom :/
Click to expand...
Click to collapse
hehe
maybe reflash rom/recovery rom ?
yea, think im gonna wipe it completely, reroot and so on..
Moved to Q&A as not development.
Can you update your USB drivers to the HTC Sync 3 ones and see if that helps
where do I get those drivers?
oh... hehe.. learn to read?
thanks, ill try that..
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
Make sure that you've mounted USB as "None", you can do so by pulling down the notification bar. Hope that helps!
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
make sure usb debugging is ON, set usb connection to NONE. I'm assuming you have sdk installed in c:\ of computer. Then go to cmd prompt and type: "cd c:\android-sdk-windows\platform-tools" [enter]
Then, type: "adb devices" [enter]
Should detect device, or something is wrong.
Hell, just go install the CWM and install the mods that way. A lot of them are updated to now work with CWM. See here: http://forum.xda-developers.com/showthread.php?t=1019143
I am very comfortable working with ADB.
For some reason I cannot get it to recognize my device for the life of me.
Dameon Running etc. etc..
and then error:device not found
Help Please
Same for me .. what's the deal with Galaxy S2
Happens to me too, sometimes, but not only for the SGS2 but for the emulator as well (says "no devices online" even though it's running).
What so far always helped me was to give the adp.exe process a headshot via the Windows TaskManager (i.e. kill the adb process) and restarting it with "adb start-server", giving it a few seconds to settle and try again.
Which drivers have you installed? The google ones or the ones from Kies? Also are you running stock or using an AOSP rom?
hi, i saw this 3rd....i have the same problem. adb doesn't recognize my Samsung GS2. I enabled the debugging mode and set up the system but adb always says "Permission Denied". I use Ubuntu 10.04.
Please need help.
hello, new user here. just got my maxx in today and love it!
ive been looking online on how to root it on my mac, seems easy enough.
however, went i go to type in "sh run.sh" to run the root exploit, it says:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
then it does nothing and just sits there.
am i missing something? USB debugging is on, it is on Charge Only. i cannot figure out if im missing a step here...
also, this is using the MotoFail exploit, if that helps at all.
so i think it might have to do with USB debugging NOT working. which is odd, phone is stock out of the box right now, why wouldnt it work??
Strange... Have you tried a normal command via adb like "adb get-serialno" if you get your serial number then debug mod is working.
Oberbufdi said:
Strange... Have you tried a normal command via adb like "adb get-serialno" if you get your serial number then debug mod is working.
Click to expand...
Click to collapse
i have not yet, good idea though. can you explain how id do this exactly? sorry im kind of a noob when it comes to adb. also, im pretty sure debugging isnt working.
Oke I dont own a MAC but am using Linux. I need to set the usb to pc mode to make rooting work with motofail. Maybe that's your case also?
Sent from my XT910 using Tapatalk
bryannh said:
i have not yet, good idea though. can you explain how id do this exactly? sorry im kind of a noob when it comes to adb. also, im pretty sure debugging isnt working.
Click to expand...
Click to collapse
I don't own a mac but you just need to open Terminal and cd to the folder where you extracted motofail.
Hello, I am very new here and I have a big problem, I was working with a device that is using Android OS, suddenly its ADB is not working. I tried to start the service but I think the adbd file is missing. I searched a lot and found nothing, Can you please tell me how can I fix this issue?
I have no root access, I don't know how it is removed.
@newdevnoob
Basically adbd ( ADB daemon ) only present on developer-friendly Android devices, means what are debugable.
Have you enabled USB debugging in device's Developer options?
jwoegerbauer said:
@newdevnoob
adbd ( ADB daemon ) only present on developer-friendly Android devices, means what are debuggable.
Click to expand...
Click to collapse
I have used that before, I mean, it suddenly appeared and I did nothing, I enabled developer mode and also enabled Debugging mode, but it still is not working.
newdevnoob said:
I have used that before, I mean, it suddenly appeared and I did nothing, I enabled developer mode and also enabled Debugging mode, but it still is not working.
Click to expand...
Click to collapse
How do you know that adbd is missing on Android device? What error message do you get PC-side?
jwoegerbauer said:
How do you know that adbd is missing on Android device? What error message do you get PC-side?
Click to expand...
Click to collapse
I used Terminal Emulator to start adb Service manually but it's not working.
even I tried to find its executable, it doesn't exist too.
can you please help me to diagnose this problem?
@newdevnoob
OMG
You run ADB on PC, NOT on Android device.
My advice: Become familiar with ADB.
You are right, we run adb on PC but there should be a service that handles those commands so I am saying that there is a problem on the device side, I tried other devices and they are working fine, I only cant use this device with adb, I asked for your help not a joke.