Digitizer is broken, but I can see the screen. I need to enable debugging but I have absolutely no touch response.
I know that debugging is enabled in a custom recovery but I need it to be enabled on the os level. Is there a ROM that has USB debugging enabled by default? A backup image of a stock image with usb debugging enable would work too. (I am not trying to enable MTP or pull data, I am trying to establish adb and lunch a program with os running"
I have tried enabling it via terminal in recovery but its not working; I can't seem to find the path to change the value.
Thanks in advance.
I actually have the same exact issue. The screen is smashed to hell, but it still turns on and off. I still get calls, texts, and all other notifications...but the touch screen is totally unresponsive and I can't get to my files through my computer because I can't unlock the phone. If there's anyway around this, I'd much appreciate the help too.
Thanks.
frankyredz said:
I actually have the same exact issue. The screen is smashed to hell, but it still turns on and off. I still get calls, texts, and all other notifications...but the touch screen is totally unresponsive and I can't get to my files through my computer because I can't unlock the phone. If there's anyway around this, I'd much appreciate the help too.
Thanks.
Click to expand...
Click to collapse
well your problem is easy...well easier.
unlock the bootloader flash a custom recovery (cwm) you can enable SD card via the recovery and move your files using MTP. search the forum for "how-tos"
Why not use a mouse or keyboard?
ace7196 said:
Why not use a mouse or keyboard?
Click to expand...
Click to collapse
No otg and you need your screen to setup a Bluetooth connection, right?
otg http://forum.xda-developers.com/showthread.php?t=2181820
also, use the google. tons of people have busted their digitizers. http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
ziddey said:
otg http://forum.xda-developers.com/showthread.php?t=2181820
also, use the google. tons of people have busted their digitizers. http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
Click to expand...
Click to collapse
No otg without external power*
Better?
ace7196 said:
Why not use a mouse or keyboard?
Click to expand...
Click to collapse
no native OTG, Enabled debugging ROM would solve my problem much easier
ziddey said:
otg http://forum.xda-developers.com/showthread.php?t=2181820
also, use the google. tons of people have busted their digitizers. http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
Click to expand...
Click to collapse
I actually stumbled upon this but only saw the first part. and had the same problem where the value would not stick. Didn't see the second part; will try. Still, a rom that has debugging enabled would be ideal and is originally what I asked for in the op. Nevertheless, thank you.
estallings15 said:
No otg without external power*
Better?
Click to expand...
Click to collapse
LOL. this.
Bump. None of the above has worked. Is there a ROM that adb is enabled by default? CM?
Sent from my Nexus 4 using xda app-developers app
Thread Necromancer requires assistance!
frankyredz said:
I actually have the same exact issue. The screen is smashed to hell, but it still turns on and off. I still get calls, texts, and all other notifications...but the touch screen is totally unresponsive and I can't get to my files through my computer because I can't unlock the phone. If there's anyway around this, I'd much appreciate the help too.
Thanks.
Click to expand...
Click to collapse
Sorry for dredging up a dead post from ages long forgotten, but I was hoping to find some semblance of help here.
I am fully aware of the fact that this is for the Nexus 4, but I'm optimistic in my approach to find answers regarding the absolutely decimated screen and digitizer of my (otherwise undamaged) AT&T Exhilarate (i577) android.
It'll be about a week before I can get in to get them replaced, so I was hoping to at least read the texts that I've since received or scavenge my contacts via [email protected] due to situational intensity ((family member health issues)My Google account does not hold this information), and I've followed all of the setup walk through found here: droid-at-screen.ribomation..com/installation/
My issue now is that I cannot load my device from the [email protected] application, presumably caused by a severe lack of USB debugging enabling.
My phone is not rooted or modded in the least.
Is there any hope for me?
Thanks in advance!~
I was in the same situation with a HTC Sensation.
I had to S-OFF to get superCID and get the screen calibration to work.
But juopunutbear required to be in normal mode and ADB enabled. I finally get it working by installing CWM recovery, which has ADB, and enable the adb debugging.
adb shell
mount -a
(if the following two commands show error "file doesn't exist", don't worry, it's ok!)
rm /data/property/persist.service.adb.enable
rm /data/property/persist.sys.usb.config
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
/system/xbin/sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value='1' where name='adb_enabled'";
/system/xbin/sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value='1' where name='development_settings_enabled'";
sync
reboot
Click to expand...
Click to collapse
If the sqlite3 command shows error (command not found) then your phone doesn't have sqlite3 installed.
Still, you can do it!
First extract settings.db:
adb pull /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Copy that file to a usb drive or whatever.
Now you need linux. It's ok to use a live Ubuntu DVD, but you need to be connected to internet.
http://www.ubuntu.com/download/desktop
I recommend to use the 32bit version for compatibility.
Usually sqlite3 is not installed by default.
In ubuntu:
sudo apt-get install sqlite3
Click to expand...
Click to collapse
You will be asked for the root password!
Now we can edit the settings.db:
sudo sqlite3 /path_to_your_folder/settings.db
update global set value='1' where name='adb_enabled';
update global set value='1' where name='development_settings_enabled';
.exit
Click to expand...
Click to collapse
Now we have the settings.db changed and ready!
Copy that settings.db again to a pen drive or whatever, go back to windows or keep in linux if you already have a working ADB.
adb push settings.db /data/data/com.android.providers.settings/databases/
adb shell "chown system.system /data/data/com.android.providers.settings/databases/settings.db"
adb shell "chmod 644 /data/data/com.android.providers.settings/databases/settings.db"
sync
reboot
Click to expand...
Click to collapse
Done! ADB should work when in starts.
I had to use "mass_storage,adb" because "mtp,adb" or just "adb" didn't work. Thought, the phone was not working in mass storage, but who cares! ADB was!
thanks @dabyd64 , i was in a similar situation of dealing with an htc evita, basically a corrupted rom made the display useless, so had to enable debugging via recovery, I used twrp. And its enabled now.
Thanks @dabyd64!!!! I also was in a similar situation of my Samsung Xcover 2 S-7710. I succesfully enabled the debuging mode
Wow, I'm working with something old... My old Nexus 7 2013 is having touch screen problems so I tried the sqlite3 option. The commands executed fine but now I'm in a boot loop. It's been booting for twenty minutes. Any advice?
Wow this is OLD !
Make a factory reset,that should fix the bootloop .
And then try again?
Related
Anyone else having problems rooting after flashing the full sbf from MDW?
I have tried the 1click and 123root method and neither will connect to my device.
Just keeps saying it is waiting for it.
Any ideas how I can fix this? I do appreciate all you smarter people lol!
SuperOneClick worked for me:
http://forum.xda-developers.com/showthread.php?t=803682
First post says this:
If you're having issues with "wait for device" or if RATC is looping, try this
Unplug your USB Cable
Go to Settings > Applications > Development
Uncheck USB Debugging
Plug in your USB Cable
Unplug your USB Cable
Check USB Debugging
Plug in your USB Cable
Click to expand...
Click to collapse
I did that and it worked fine.
...eh still doesn't work....this is weird!
I should also mention that Superoneclick just freezes...like
when I go to close it I get the program not responding prompt.
i used the DOroot and it worked fine was rerooted in under 5mins.
so when you used DoRoot does it take a while for things to happen or is it right away? I am stuck at the waiting for device prompt, I tried the unplugging and debugging method above but it just won't acknowledge that my device is plugged in, and there is no action from the device end either it just sits there and stares at me with my stock home screen.
I have reflashed the 2.3 sfb like 5 times and it just won't register that my device is connected.
I read somewhere that there is a non-pc root method, anyone know what that is all about?
enzojrc said:
so when you used DoRoot does it take a while for things to happen or is it right away? I am stuck at the waiting for device prompt, I tried the unplugging and debugging method above but it just won't acknowledge that my device is plugged in, and there is no action from the device end either it just sits there and stares at me with my stock home screen.
I have reflashed the 2.3 sfb like 5 times and it just won't register that my device is connected.
I read somewhere that there is a non-pc root method, anyone know what that is all about?
Click to expand...
Click to collapse
I forgot to update SDK so mine kept failing too. Make sure its up to date as well as your moto drivers.
enzojrc said:
so when you used DoRoot does it take a while for things to happen or is it right away? I am stuck at the waiting for device prompt, I tried the unplugging and debugging method above but it just won't acknowledge that my device is plugged in, and there is no action from the device end either it just sits there and stares at me with my stock home screen.
I have reflashed the 2.3 sfb like 5 times and it just won't register that my device is connected.
I read somewhere that there is a non-pc root method, anyone know what that is all about?
Click to expand...
Click to collapse
if I'm not mistaken, the non-PC method requires installing a Terminal Emulator app on your phone and rooting from there. Since I'm new and can't post a link, just google this:
"Droid 2 root non-pc emulator" --- should be a link to DroidForums explaining it.
it sounds like you are missing the motorola drivers. Did you have your d2 on pc mode when you tried? Dark Onions solution and Karnovarens soltution worked for me with no issues on w7 64 ultimate or on lmde
Yep I updated drivers twice! I will try the SDK update and see if that works, I get home in an hour.
p.s. I appreciate all of the help from you guys, nice to know I can go somewhere and find like minded people that are more than willing to help out!
p.s.s. - - - what is SDK? lol
Same thing was happening to me when I updated..I also was trying the 123 superuser method..kept freezing and what not..
What I did was take out the batter. Reboot it and plug it in..after a couple of tries..I was rooted..pain in the butttt but I got what I wanted
Sent from my DROID2 using XDA App
Username2011 said:
Same thing was happening to me when I updated..I also was trying the 123 superuser method..kept freezing and what not..
What I did was take out the batter. Reboot it and plug it in..after a couple of tries..I was rooted..pain in the butttt but I got what I wanted
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
I have taken the battery out, cursed it, begged it, put it back in..... pretty much my phone hates me or something.
But enough ranting. When I get home shortly I will continue trying everyones suggestions and let you know what I come up with.
Again THANK YOU ALL FOR BEING AWESOME PEOPLE AND HELPING ME OUT!
enzojrc said:
I have taken the battery out, cursed it, begged it, put it back in..... pretty much my phone hates me or something.
But enough ranting. When I get home shortly I will continue trying everyones suggestions and let you know what I come up with.
Again THANK YOU ALL FOR BEING AWESOME PEOPLE AND HELPING ME OUT!
Click to expand...
Click to collapse
I understand; wish you luck!
Sent from my DROID2 using XDA App
andd.........nothing works. IDK what to do short of getting it stuck in bootloader mode and trading it to Verizon for a new one.
enzojrc said:
andd.........nothing works. IDK what to do short of getting it stuck in bootloader mode and trading it to Verizon for a new one.
Click to expand...
Click to collapse
You could always try and do it the old-fashioned manual way lol. It takes a bit longer but if you get through it you understand more about your phone and the process that the others just streamline for you.
newk8600 said:
You could always try and do it the old-fashioned manual way lol. It takes a bit longer but if you get through it you understand more about your phone and the process that the others just streamline for you.
Click to expand...
Click to collapse
That is what most of my night consisted of. I hit a brick wall when I couldn't get this to work:
chmod 4755 /system/bin/su
it kept saying file doesn't exist or some crap
change your USB Connection to Charge Only, and every option to root will work from manual ADB or superoneclick. Some reason when updated it change the usb option that used to be PC MODE to Charge Only mode.
What error do you get?
enzojrc said:
That is what most of my night consisted of. I hit a brick wall when I couldn't get this to work:
chmod 4755 /system/bin/su
it kept saying file doesn't exist or some crap
Click to expand...
Click to collapse
it should be chmod 0755 /system/bin/su
Heres what I do every time theres an update:
Open command prompt
cd c:\android-sdk-windows\tools
adb devices (to verify the connection)
adb push Superuser.apk /sdcard/Superuser.apk
adb push su /sdcard/su
adb push busybox /sdcard/busybox
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell
cd data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
let the process run until it 'kicks' you out (may take a minute or two)
cd c:\android-sdk-windows\tools
adb devices
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
cp /sdcard/busybox /system/bin/busybox
chmod 0755 /system/bin/su
chmod 0755 /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
exit
exit
I want to thank you all for giving me great info on how to fix my problem. It is people like you who take the time out of your day to help someone like me that makes forums the best place to go when you need help with anything.
That being said I think I made my problem so HUGE....that when I figured out the tiny tiny TINY mistake....it makes me feel bad that I got the helpful responses that you all gave me.
I tried it on a different laptop and it rooted...first try. So apparently it is my main laptop that had the problem connecting to my phone.
Again thank you ALL....and please add TRY ANOTHER COMPUTER to the list of helpful hints for future Android brothers/sisters who need the assist lol....
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
mikeew83 said:
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
Click to expand...
Click to collapse
This is the way its done. Sorry up front for quoting myself but I have responded to this issue in the past:
Download the file from this post
http://forum.xda-developers.com/showpost.php?p=8752645&postcount=5
Follow the steps with this post
http://forum.xda-developers.com/showpost.php?p=14199959&postcount=11
Profit!
Holy run on sentence Batman.
Sounds like a drivers issue, or that you don't have USB debugging enabled on the phone.
Open the Dalvik Debugging Monitor Service (DDMS) that came with the Android SDK.
Does it recognize the phone at all in DDMS?
If yes, then does it say "online"? If yes, then you have something blocking adb from talking to your phone from your computer. (firewall?)
If no, then you have a driver or USB connectivity issue. (bad driver installation, usb debugging not enabled on phone, bad usb cable, plugged usb cable into a port not directly on the motherboard)
EDIT: Looks like the post above me could understand the run on sentence more than I could.
You can also run the command lsusb and it should tell you if your system is seeing the device.
What Linux distro your running?
Sent from an Epic with 4G
ok to recap
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
tried your directions again
I have tried them again and they do not work.
Try the usb cable for the droid x. Its a really good one.
if that were an option
I have an incredible cord i can try that is about the only one but i dont see how it has anything to do with the usb cable when lsusb recognizes the device plugged in just adb will not list it on devices so that i dont think is the answer but thank you for the suggestion.
mikeew83 said:
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
Click to expand...
Click to collapse
You should only have 1 rules file, my suggestion, delete the 15 one and keep the 99.
Make sure the permissions are configured correctly, the biggest issue to run this type of operations in linux is the permissions and the ownership on the config files
Sent from an Epic with 4G
thanks
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
mikeew83 said:
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
Click to expand...
Click to collapse
Let me go over what to do:
After downloading the rules file on the above post, for example I have the SDK (adb) installed on my PC on the following path: ~/android/tools/, so go to your SDK folder (where adb is located) and run the chmod a+rwx adb command.
After this, take the rules file you downloaded from the above post and moved it to the /etc/udev/rules.d/ folder (logged as root, NOT SUDO). After doing this, run the following commands:
make sure that 51-android.rules file has the following permissions -rw-r--r (read and write for owner, group + others read only)
su [then placed the password] (Once again DO NOT USE SUDO)
chown root:root 51-android.rules
Once done, restart the PC and it should be working 100%. Before connecting the phone, make sure USB Debugging is active, and restart your phone.
Connect your phone via USB and run the lsusb command to confirm the connection of the device and then run ./adb devices and check for the positive return!
Note: if you have never had a password on su, run the following command: sudo passwd and change the password and try running the series of command above.
Note2: add your user to the plugdev group on your computer
Note3: sometimes while performing the ./adb devices command will return a response stating that a device by the name ?????????????? is connected, this is OK, you can connect via ./adb shell and you will see your device file structure, if you request SU permissions you will have to authorize it on the phone via the SUPERUSER app that gets installed when rooting the device.
IMPORTANT: The password for ROOT (su) user is not the same as the password you enter for the SUDO command (your user) unless you make them the same!
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
SweetBearCub said:
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
Click to expand...
Click to collapse
Though this is good info (thanks for pointing it out), I would highly suggest to leave UART as Modem, and just change USB to PDA.
Sometimes you may have issues with Tethering if you set the UART to PDA.
I have been a bit busy I appreciate the run down and will try it here tomorrow or its 2am so later today I also checked the 8778 and my usb is already set to what was specified.
Sent from my SPH-D700 using Tapatalk
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
plug the phone, open a terminal as administrator/root and type
adb stop-server
adb start-server
adb devices
the last command must return your device name-id
If not there is smth wrong with your installation
The device didn't show up do you know what I could have done wrong? Do I have to turn on mass storage? Could it have something to do with my drivers, can't remember installing any... And in the device manager I see four android with a orange triangle with am exclamation mark inside.
Sent from my U8800 using Tapatalk 2
theminikiller said:
The device didn't show up do you know what I could have done wrong? Do I have to turn on mass storage? Could it have something to do with my drivers, can't remember installing any... And in the device manager I see four android with a orange triangle with am exclamation mark inside.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
No you don't need to enable mass storage, but you need to enable USB debugging from dev settings from the device. Use these drivers
https://www.dropbox.com/s/ryn7l7z0nfc842g/u8800_pc_drivers.zip
emmm... feeling kinda stupid right now... but how do i install the drivers? xD
theminikiller said:
emmm... feeling kinda stupid right now... but how do i install the drivers? xD
Click to expand...
Click to collapse
You have to install them manually from device manager.
Sent from my U8800
After i choose the folder with the drivers i only get a message saying it didnt find any drivers. Do you know why i cant install them?
Is it the same drivers when I'm using aurora ics as gingerbread roms?
Sent from my U8800 using Tapatalk 2
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
kross666 said:
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
Click to expand...
Click to collapse
Thanks alot! That worked perfectly, now i can start using adb on my phone xD
btw i have a question for adb... what does reboot to download mode mean? is that pink screen?
theminikiller said:
Thanks alot! That worked perfectly, now i can start using adb on my phone xD
btw i have a question for adb... what does reboot to download mode mean? is that pink screen?
Click to expand...
Click to collapse
I think its safe mode
Sent from my Impulse 4g running vPure Professional CM7.
kross666 said:
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
Click to expand...
Click to collapse
Thank you the instructions in the link provided worked for me. I am able to see my listed by adb device command...
help
i have been trying to root my acer iconia tablet A100 for a week now, i ve tried and followed a dozen of ways. this is were it has brought me,
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
please help me, what did i do wrong
thanks in advanced
jakk181571 said:
i have been trying to root my acer iconia tablet A100 for a week now, i ve tried and followed a dozen of ways. this is were it has brought me,
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
please help me, what did i do wrong
thanks in advanced
Click to expand...
Click to collapse
this is not the forum for ur device..
then please tell then where is the correct forum.
i only when to this one because google brought me here, and it was on adb, which is what i am have trouble with.
Re: Adb - device not found (I had same problem) Fixed
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
I had the same issue updating my Nexus 7 in adb download mode device not found. You will also notice in system setting device driver is showing an error. You can download Adb driver installer which should detect any missing driver and fix the issue.
It worked for me straight away otherwise I had no way round getting to solve the problem. Fheww!! hope it works for you
Many Thanks.
adbdriver.com/downloads
---------- Post added at 05:55 PM ---------- Previous post was at 05:43 PM ----------
You may be missing the device driver when switching to USB Debugging mode using ADB Command prompt device not found.
Please download and intsall adb driver installer. It found my device and installed missing driver straight away problem fixed now I dont seem to have any issue.
adbdriver.com/downloads/
Glory be to Almighty God. Thank you!!
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
same problem...
Hey guys. My phone slipped out my pocket and the digitizer is broken. My phone is rooted, the boot loader is unlocked, and I have it recognised as an ADB Recovery device. I want to enable USB Debugging so I can use androidscreencast to use my phone over my PC so I can set it up to push notifications to my computer and to my pebble(smart watch).
How can I do this. Most of the threads I have found just flat out don't work or stop because of some sort of restriction due to the phone being still locked.
It looks like you need to run some commands in a terminal emulator on your phone. Which in your case is going to be impossible. Why don't you just use adb pull to pull the data off your sdcard?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
It looks like you need to run some commands in a terminal emulator on your phone. Which in your case is going to be impossible. Why don't you just use adb pull to pull the data off your sdcard?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Don't need any of the stuff - I could just boot in and take it over USB. All I need is to enable USB Debugging to send touch commands in place of my touch screen. Once I have that my pebble can let me use my phone outside of the house and I can send notifications to my PC too.
Bump!
Bump!
Anyone? I can't get a new phone for a while.
The biggest Problem ist the Drivers "FOR ALL"problems
You must have all Drivers for it
ThePraeceps said:
Hey guys. My phone slipped out my pocket and the digitizer is broken. My phone is rooted, the boot loader is unlocked, and I have it recognised as an ADB Recovery device. I want to enable USB Debugging so I can use androidscreencast to use my phone over my PC so I can set it up to push notifications to my computer and to my pebble(smart watch).
How can I do this. Most of the threads I have found just flat out don't work or stop because of some sort of restriction due to the phone being still locked.
Click to expand...
Click to collapse
R-2-D-2 said:
You must have all Drivers for it
Click to expand...
Click to collapse
Drivers are installed for it too, I literally just need to get USB Debugging
I am in exactly the same boat! I just need to enable debugging so i can remote control my Nexus 4. i have adb access from CWM, in case there is any commands i can do from there?
Roguecube said:
I am in exactly the same boat! I just need to enable debugging so i can remote control my Nexus 4. i have adb access from CWM, in case there is any commands i can do from there?
Click to expand...
Click to collapse
Hey man. Ultimately I just got a new screen but I was able to enable usb debugging with these instructions.
Hope it helps!
http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
My daughter dropped her HDX 7 and the screen shattered. I was able to secure a new one for her but she had some serious sweat equity into a few games she was playing on the old one. I am trying to get the game files of the old one to move to the new one but the touch screen won't work and as such, will not take her password. (due to the drop).
Is there an easy way to bypass this? I am trying to access the kindle drive from my PC for purposes of copying the files (done a million times) but with the device technically locked, the device does not show in file explorer.
Any suggestions welcome.
Thank You!
Chris
Do you have Safestrap installed?
EncryptedCurse said:
Do you have Safestrap installed?
Click to expand...
Click to collapse
No I don't. The device is purely vanilla right as it came from the factory.
Chriss9, you should try to get adb working. That should allow you to pull data.
lekofraggle said:
Chriss9, you should try to get adb working. That should allow you to pull data.
Click to expand...
Click to collapse
Can you tell me where to get it and maybe some instructions? Thanks so much!!
Chris
Look into the rootkit in the dev section. That should install the drivers for you. Then, search for how to use adb. You may need to download the developer kit from Google as the toolkit is a little limited.
You need to pull the data to your computer then push it to the new Kindle.
ADB pull on locked phone? // Simulate input
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk
Grtschnk said:
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk
Click to expand...
Click to collapse
Thanks for the suggestion. I installed ADB on my PC and when I use "ADB DEVICES" my device does not show on the list though it does show in Windows explorer. Am I out of luck here?
Thank you again for your kind support.
Chris
Assuming you have the latest Fire OS 4.5.1 : (If you have the older version installed there may still be a glimpse of hope (see long answer))
Short answer: Sorry, looks grim.
Your ADB is switched off and there is no way I know of to switch it on.
I wanted to make sure it wasn't just a driver issue with your computer so I checked with my Kindle:
ADB set off: Kindle in Windows, but not detected by ADB-program
ADB set on: Kindle in Windows and detected by ADB-program
Long answer (may be frustrating to read because it states all the possibilities the Kindle lacks): On a nonlocked (in terms of bootloader, not screenlock) device there would have been some possibilities. Install a custom recovery that has ADB built in and pull the files or try to enable ADB from within recovery inside the ROM. If the device could act as a USB host a mouse or keyboard could have been hooked up. The Kindle supports Bluetooth input devices but they have to be set up first (from within the device, not possible without touch). If your device has older Fire OS you could try the mentioned steps, however that's beyond my expertise. So I don't know if it is possible/will work. You'd have to check other threads about flashing the device or hope that someone else posts advice in this thread.
I became a Kindle owner quite recently, so I can't guarantee everything I wrote is correct, but I believe as long as noone magically finds a way to unlock the bootloader the more experienced users will agree to my post.
Did you install the driver as well? I recommended the toolkit because comes with the driver and if you are not used to installing adb drivers on Windows, it can be a bear. But, Grtschnk may be right. I always enable it n all my devices. It is the first thing I do.
Just to be really sure about possible driver issue: You (chris) could try to connect an Android phone via ADB (I'm assuming you have one). Enable ADB on it and see if connects. Unfortunately this will only prove more that your Kindle turned into a piece of plastic :/
Grtschnk, unfortunately, that won't prove anything. ADB requires separate drivers for each device. Again, that is why I recommended the rootkit. It sets it up for you and can even test it.
That's why I compared with my Kindle, computer and S2 (CM11). Newly set up computer, no SDK, just Minimal ADB. Never installed special drivers for Kindle or S2. Newest Visual Studio (2013) runs on the machine, but without additional packages there is no Android support.
However if I was in the situation myself I would have also tried the full SDK.