Database Users

[Q] rooting problem: "device not found"

Hi: I'm a long time lurker here on xda-dev, but I'm a first time rooter and this is my first time posting here.
I appreciate any help that I can get, and I will try to be as descriptive as possible so that I don't waste anyone's time. You should know that I am running OS X 10.6.7 (which is 64 bit if that makes a difference). I know that it's possible to root from OS X because I've been in contact with a fellow xda'er about his success with it and my subsequent problems. You will notice from the screenshots that I have a bootcamp partition because I plan on installing Windows 7 at some later time. I think that this may be a driver issue, but really dunno why I would have this driver problem if the person who I know has had success with OS X 10.6.7 didn't have any problems. Not sure if this matters, but I am using this sdcard: http://amzn.com/B003WGJYCY
Things that I've done that you might ask me if I've done:
-Debugging is on (I've toggled it a few times too)
-temprooted with Visionary
-Extracted the Shift file to the root of my sd card
-Checked the md5 of the file in Shift using Terminal emulator (it matches what the guide says it should be)
-Reinstalled the SDK
-Reinstalled Visionary
-Re-Extracted the 'Shift' file to my sdcard.
I am trying to root my shift following this guide : http://forum.xda-developers.com/showthread.php?t=932153
I have installed Android SDK and for have installed the packages that you can see in this screen shot: http://oi55.tinypic.com/2dvimb6.jpg
I then temprooted using Visionary: After a few failed temproots, I did get a successful temproot, which I am verified by gaining SU with the app Terminal Emulator.
I open up command prompt and do the commands that you can see in this screenshot and as you can see after ./adb shell I get "error: device not found" : http://oi51.tinypic.com/2ztcymt.jpg
As you can see, I can open adb, but the adb shell command returns an error that no device is found. I've also done this: http://oi51.tinypic.com/264t6o5.jpg
So, what do you think?

i forgot to mention that my phone is in charge only mode when I execute ./adb shell

is it connected to a 2.0 USB port?
Also have you tried restarting your phone and mac?
I also saw on another forum that Superuser had to be uninstalled then try temp rooting again.
Also are you keeping an eye on your phone while trying to gain su access? You have to click yes when it asks if you wanna give permission.

You could always try rooting via terminal on the phone. That's what I did, no PC involved.
^ Shift Faced

Thanks for your responses.
I assume these are USB 2.0 ports on my 2010 MacBook Pro. I've uninstalled superuser a couple of times, but when I use terminal emulator to check if I'm temprooted, it shows back up in my apps list.
I have never had the option of giving adb superuser permissions, but yes I have kept my eye on the phone to make sure that the phone wasn't requesting this.
@jesusice -- even though I did the md5 check on the phone, I never thought of rooting the phone through terminal emulator. Would I just follow the directions from the guide, and just input all of the commands into terminal emulator? Anything else I should know about if I try this?

dubs.law said:
@jesusice -- even though I did the md5 check on the phone, I never thought of rooting the phone through terminal emulator. Would I just follow the directions from the guide, and just input all of the commands into terminal emulator? Anything else I should know about if I try this?
Click to expand...
Click to collapse
That's what I did. Had been waiting for perm root so long and was so excited I couldn't stand to wait until I got home and just put the commands into terminal on the phone. Just make sure that you input all commands EXACTLY. It was recommended by others to do it from desktop so you can be sure and copy and paste the commands so as to cutdown on errors but I'm not sure why... I can copy and paste from the phone It's just kinda a pita.
^ Shift Faced

Does the phone have to be plugged in the wall or into the computer at all to do this without a computer?

dubs.law said:
Does the phone have to be plugged in the wall or into the computer at all to do this without a computer?
Click to expand...
Click to collapse
Nope.
^ Shift Faced

So, there is no adb commands, you just flash the "eng spl" , correct?

I rooted without a computer. Thanks!

dubs.law said:
I rooted without a computer. Thanks!
Click to expand...
Click to collapse
Awesome! I was coming on to tell you I don't really remember all the details as it was a long time ago and that I couldn't help any
Exciting doing it from the phone, right? The fear of bricking is fun
^ Shift Faced

i really dont understand

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

[UPDATED][Video] How To Root Transformer & Downgrade Honeycomb 3.1

WE ARE NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE! FOLLOW THE INSTRUCTIONS AND YOU SHOULD BE FINE!
IF YOU HAVE HONEYCOMB 3.1 OR SOME OTHER FIRMWARE OTHER THAN 8.2.3.9 THEN YOU CAN DOWNGRADE VERY EASILY
[HERE IS HOW TO DOWNGRADE]
Some prerequisites to the rooting process:
1) You must have a Windows 7 or XP for this tutorial.
2) You must have a micro SD card in your tablet throughout the procedure. It is safe to remove it AFTER you finish the ALL steps. There's no minimum size requirement but 2gb should be fine.
3) The files needed to root your device from here:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
4) An Asus Transformer (16 or 32gb) running Honeycomb 3.0.1...SEE DOWNGRADE INSTRUCTIONS IF YOU ARE ON HONEYCOMB 3.1
5) Data cable
6) Me guiding you
Alright now that you have everything set, lets begin the rooting process!
1) You need to make sure your device has USB Debugging activated. To do this go to Setting>Applications>Development and make sure there is a check box next to USB Debugging. Leave the other two options unchecked.
2) Check what your Build Number is. Go to Settings>About Tablet>Build Number. Make a note. If it it says 0423 at the end (or anything after) then you use V5. If its anything below (ex. 0421) then you use V4. Got it?
3) Hook up your Transformer to your computer via the USB Cable. Avoid USB hubs if possible.
4) If you are using Windows 7 then the drivers will install automatically. I have provided you with the link to the drivers here:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
4) Download & Install the Asus Sync software. I know its annoying to have to install bloatware that you will probably never use but in this case, your Windows machine will not detect your device without it.
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
5) Insert the MicroSD card into your Transformer and make sure that the tablet recognizes it. I have had issues with some cards not being detected.
6) Now we need to download the Android SDK. You can download it here.
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
7) Install the Java Developer Kit if you dont have it already. You can find it here:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
*Edit*
Even after you install the JDK the SDK installer might say that its not installed. Just click back then next again (or restart the installer again) and it should work-Thanks Codiox
8) Install the SDK to the root of your hard drive and put it in a folder called Android. This means when you click the local disk C: drive the first folder you should see is the Android folder. This will make using the command prompt simple.
9) Go to Start>All Programs>Android SDK and click in the SDK Manager. When you're presented with the option to install all updates (and you have time to do so) let it all install. All you really need though is the Android SDK Provision tools update. You can hit cancel once that is installed successfully.
10) Open up the command prompt
11) Lets being with the terminal commands. Make sure you press the ENTER button after every command line. You can copy and paste the commands if you want; if you do so, you dont need to press enter to go to the next line.
12.
Code:
adb devices
make sure your device is detected
13.
Code:
adb push gingerbreakBB /data/local/
14.
Code:
adb shell chmod 777 /data/local/gingerbreakBB
15.
Code:
adb shell
you will get a $ sign.
16.
Code:
./data/local/gingerbreakBB
nothing will happen at first, but after about 5 minutes, you will see a long list of "vold" commands....let this run its course...go grab a sandwich or something.
If for some reason it says permission denied, try running these commands immediately after running the
Code:
./data/local/gingerbreakBB
command. DO THIS ONLY IF YOU GET PERMISSION DENIED LIKE IN MY VIDEO! If you didnt get the permission denied error, continue to step 20.
17.
Code:
rm /data/local/tmp/boomsh
then type.
18.
Code:
rm /data/local/tmp/sh
then redo step 16 again which is
19.
Code:
./data/local/gingerbreakBB
20. After about 7-10 minutes you will be presented with a # sign. THIS IS GOOD!
21. Open ANOTHER command prompt window; the same way you opened the first one. DO NOT FOR ANY REASON CLOSE THE FIRST COMMAND PROMPT. LEAVE IT OPEN IN THE BACKGROUND!
22. type
Code:
adb devices
23. PAY ATTENTION HERE! Remember when I told you to look at your build number? We need that information now. If your tablet has a build number ON OR AFTER 0423 then use this command
Code:
adb push CWM_BLOB_V5 /data/local
If it has a build number BEFORE 0423 (ie. 0422) then use this command
Code:
adb push CWM_BLOB_V4 /data/local
24. Whatever number you used above, you will continue to use it throughout the installation! REPLACE THE # SIGN WITH WHATEVER YOUR NUMBER ABOVE WAS; EITHER 4 OR 5.
Type
Code:
adb pull /data/local/CWM_BLOB_V# cwmblob_retransfer
then
25. Return BACK to the PREVIOUS command prompt that had the # sign just sitting there.
26. Type
Code:
dd if=/data/local/CWM_BLOB_V# of=/dev/block/mmcblk0p4
Replace # with your number (4 or 5)
27.
Code:
adb shell
28.
Code:
reboot
29. Your device will reboot now. This will take a bit longer than a normal reboot so be patient.
30.
Code:
adb remount
31.
Code:
adb push su /system/xbin
32.
Code:
adb push Superuser.apk /system/app/
33.
Code:
adb shell
34.
Code:
reboot
THAT'S IT! Congratulations! You have successfully rooted your Asus Transformer. I hope this tutorial made it simple for you. Let us know if you have any questions!
Credit Goes To Androidroot.mobi devs for the original rooting process.
Original Thread:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/

+1 Thanks!

So its a no go on vista 64 bit
LEEDROID GB3.0.1DESIRE HD using XDA PREMIUM

combat goofwing said:
So its a no go on vista 64 bit
LEEDROID GB3.0.1DESIRE HD using XDA PREMIUM
Click to expand...
Click to collapse
sorry i keep forget that Vista existed at one point ...yes it should work fine on vista

Does anyone know when it will get 3.1 support?

PatrikSelin said:
Does anyone know when it will get 3.1 support?
Click to expand...
Click to collapse
Not until someone updates the modifies blob files for 3.1. However you can use this how-to to root the 3.0.1 build then flash a 3.1 ROM. Unless you're on 3.1 now with no root...then ur SOL for just a but longer
Sent from my ThunderBolt using Tapatalk

damn,!!!!! awsome post should be sticky, thank u for your support and work

Added to ultimate thread. Nice job.

Should be in the dev section as a sticky.

Trouble installing development kit
I installed the Java SE Development Kit 6 Update 25 (64-bit) but when I try to run the SDK tools setup it says the JDK is not found. The Development Kit shows up in my programs and I've installed it and reinstalled it about 3 times now, including downloading a fresh file and rebooting my computer. Is that the wrong file? I'm running Windows7 on a 64-bit computer. TIA - sheureka

PatrikSelin said:
Does anyone know when it will get 3.1 support?
Click to expand...
Click to collapse
If you have root already you can update to 3.1 using the modified update that is floating around here. Sorry I don't have a link.

sheureka said:
I installed the Java SE Development Kit 6 Update 25 (64-bit) but when I try to run the SDK tools setup it says the JDK is not found. The Development Kit shows up in my programs and I've installed it and reinstalled it about 3 times now, including downloading a fresh file and rebooting my computer. Is that the wrong file? I'm running Windows7 on a 64-bit computer. TIA - sheureka
Click to expand...
Click to collapse
just click on the "back" button, then the "next" button and you'll be fine. its a known bug.

Good write up. There are two problems. You do not give credit to the source of the root method (apache/bumblebee and rayman) and they specifically asked that their method not be reposted, only linked.

If you watched the video you would know that I took a minute to thank the developers of over at androidroot.mobi (which include all the people you just mentioned). As for their files, I respected their wishes... again I specifically said this in the video that I will honor their wishes. The link on my site takes them directly to their site. I do not host any of their files. As for the write up itself, this is my variation of their work. I wrote everything you see in my own words so newbies will understand it without confusion. Their procedure didn't work for me so I just tweaked it to make it work for me and decided to share. I'm not trying to steal their work, I think people here know my true intentions. I just wanted to help and promote my site a little. I hope that clears up everything. I will add additional credit on the main page so there's no confusion.
Sent from my Transformer TF101 using Tapatalk

Well, I got to [*] vold: 0085 GOT start: 0x00017368 GOT end:0x000175e8 (right after the donate and thanks stuff and nothing ran. I went ahead to went to the other command screen and did that stuff, hoping something would shake lose. Exploit did not take a while. In fact nothing happened at all. I'm not sure what to do - should I reboot the tablet to see what happens or just unplug and start all over. Any ideas?
I just saw that someone over on AsusTransform site has exactly the same problem. I did unplug and everything seems to be running fine (though it's obviously not rooted) but it's a little scary.

sheureka said:
Well, I got to [*] vold: 0085 GOT start: 0x00017368 GOT end:0x000175e8 (right after the donate and thanks stuff and nothing ran. I went ahead to went to the other command screen and did that stuff, hoping something would shake lose. Exploit did not take a while. In fact nothing happened at all. I'm not sure what to do - should I reboot the tablet to see what happens or just unplug and start all over. Any ideas?
Click to expand...
Click to collapse
I have another person on my forum with the same issue. What was your battery life when you attempted this? His was below 20%. Are u using a USB hub? My recommendations are to reboot, try a different usb port, charge the tab above 50% if its low and try again. You most likely need to do steps 17-19 since you pushed the gingerbreak file already. Let me kknow iif that works.

ayman07 said:
If you watched the video you would know that I took a minute to thank the developers of over at androidroot.mobi (which include all the people you just mentioned). As for their files, I respected their wishes... again I specifically said this in the video that I will honor their wishes. The link on my site takes them directly to their site. I do not host any of their files. As for the write up itself, this is my variation of their work. I wrote everything you see in my own words so newbies will understand it without confusion. Their procedure didn't work for me so I just tweaked it to make it work for me and decided to share. I'm not trying to steal their work, I think people here know my true intentions. I just wanted to help and promote my site a little. I hope that clears up everything. I will add additional credit on the main page so there's no confusion.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Video and writeup are 2 different things. Thanks for adding the credit.
Sent from my Transformer TF101 using XDA Premium App

My battery was about 80% and I'm directly plugged into my desktop. - sheureka

sheureka said:
My battery was about 80% and I'm directly plugged into my desktop. - sheureka
Click to expand...
Click to collapse
I apologize, I was mistaken. This will not work on the following firmware
8.2.3.13
There is currently no way to root this and I dont think theres a way to downgrade either. I will adjust my post. Sorry about that :-( your tab is fine though. No harm done.
Sent from my Transformer TF101 using Tapatalk

Never mind.

Getting Nexus S to mount on Linux

I just recently installed Arch Linux with KDE as the GUI and I can't for the life of me figure out how to mount my Nexus S. It doesn't show up in /media so I don't know how on earth I can mount it. I've tried in CWM with mount USB and still nothing shows up anywhere on my system. Prior to Arch I was running OS X (10.7) and it was mounting fine. Obviously very different OS and Arch is a lot more complicated to use. I've spent several hours trying to figure out how to mount it but I can't find anything that solves it. Maybe anybody out there using linux could give me a hand?

Arch is best Good choice.
Easiest way is to mount it manually. First you'll have to find out which device it is. Plenty of ways to do this, using "fdisk -l" in terminal, gparted, etc. It will be something like "/dev/sdc1". Once you know this, you need to create a folder to mount it. Something like:
mkdir /media/nexus
Now, you need to mount it (after you've chosen to mount on the phone). To do this:
mount -t auto /dev/sdc1 /media/nexus
auto is the file system, you can type fat32 also but it can figure it out. Then the disk location, then where to mount.
You may need root permissions or changes to the sudoers file to do these. Type "man mount" or "man command" for just about every commands manual. I'm on the phone so I can't write up anything much better than that.
Also, the arch Linux wiki is an invaluable resource, make the most of it.

Harbb said:
Arch is best Good choice.
Easiest way is to mount it manually. First you'll have to find out which device it is. Plenty of ways to do this, using "fdisk -l" in terminal, gparted, etc. It will be something like "/dev/sdc1". Once you know this, you need to create a folder to mount it. Something like:
mkdir /media/nexus
Now, you need to mount it (after you've chosen to mount on the phone). To do this:
mount -t auto /dev/sdc1 /media/nexus
auto is the file system, you can type fat32 also but it can figure it out. Then the disk location, then where to mount.
You may need root permissions or changes to the sudoers file to do these. Type "man mount" or "man command" for just about every commands manual. I'm on the phone so I can't write up anything much better than that.
Also, the arch Linux wiki is an invaluable resource, make the most of it.
Click to expand...
Click to collapse
Thanks very much for your help. I'll work on this later tonight since I have a lot of school work I need to get done now. Oh yeah you say to mount the device on the computer after pressing mount on the phone but that dialog never actually shows up when I plug the phone in. The phone doesn't recognize it's being plugged into a computer it just shows that it's charging. The arch wiki is definitely a great place for all things arch. Best documentation for any operating system I think I've ever seen.

Try in recovery first if it doesn't show up in Android. If it still doesn't show up I'll try to break my arch and fix it, whether its in android or cwm.

tycruickshank said:
Thanks very much for your help. I'll work on this later tonight since I have a lot of school work I need to get done now. Oh yeah you say to mount the device on the computer after pressing mount on the phone but that dialog never actually shows up when I plug the phone in. The phone doesn't recognize it's being plugged into a computer it just shows that it's charging. The arch wiki is definitely a great place for all things arch. Best documentation for any operating system I think I've ever seen.
Click to expand...
Click to collapse
I've experienced this before as well. It turned out that I had a dodgy cable that's just not compatible with my NS for some reason.
If you want a pop on your KDE desktop when you enable UMS mode on your phone, make sure you udev is added to the daemon list in /etc/rc.conf. Then, you can either reboot or do /etc/rc.d/udev start and restart KDE again.

I've tried everything that you guys have said and still no luck. Its not showing up anywhere. Not in fdisk -l, I tried lsusb, looked in /dev/disk and it wasn't there. Nothing was pointing to a device being connected. I checked the everything.log file as well. Last photo is the everything.log and of course these were all taken with my phone connected to my computer. I tried multiple different USB cables too.
Sent from my Nexus S using Tapatalk 2

Just curious, with the phone on, and screen unlocked, what do you get with:
adb devices
?

Sorry but try to check it with other OS to be sure that your USB host is good .
Sent from my Nexus S

Unplug the USB. Then plug it back in then immediately run lsusb. If you dont see the device should be /dev/sdb1 should be the device according to your current fstab.
If it does not show in /dev/ or lsusb you have a bad cable.
Sent from my Nexus S 4G using xda premium

Well this morning it decided to work. I had turned my computer off last night and I tried it this morning with the same cable and it decided to work. I hope it's not going to be intermittent but seems to be working for now. Thanks everybody for all the help!

[Q] Broken digitizer, need to enable USB debugging..image with ADB enabled?

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?