• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Enable usb debugging mode from adb under clockworkmode "Broken digitizer"

Hey guys, My friend brought me a Xtreamer Q mobile phone with broken screen, clockworkmode is working, but USB debugging mode is disabled, I found some posts about how to enable it from adb i tried them and none of them worked.
here :
stackoverflow[.com]/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
and from this tutorial i learnt how to edit build.prop file.
modaco[.com]/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
the commands i have used are: adb pull, adb remount, adb push.
While i was under clockworkmode i mounted system and i pulled build.prop then i added this line to it persist.service.adb.enable=1, used remount then pushed the file after that reboot, but i couldn't find the device in adb when it have booted normaly.
Next i tried to set adb_enabled to 1 in /data/data/com.android.providers.settings/databases/settings.db by following some steps from here
forum.xda-developers[.com]/showthread.php?t=774507.
and it also didn't worked "The device was not listed".
Also i have tried this zip file from clockworkmode it didn't work too...
android.stackexchange[.com]/questions/54487/install-adb-enabled-setting-from-zip

My files after editing are attached, wish somebody can help me to enable it.

The phone do not support USB otg cable

delete the [] around .com i can't post links because i am new..

The phone rom is android 4.3.2

http://www.xtreamer.net/downloads/xtreamer-mobile-downloads/xtreamer-q.aspx
 

Attachments

Welcome to the forum :)

Can I ask the obvious question: what are you trying to achieve? I get that you are trying to enable USB debugging for when you are running Android, but what do you hope that will do for you? USB debugging just lets you run ADB, which you can already do when in recovery, and you'll still have a broken screen.

Just asking because if we know what the objective is there may be another way of doing it.
 
Welcome to the forum :)

Can I ask the obvious question: what are you trying to achieve? I get that you are trying to enable USB debugging for when you are running Android, but what do you hope that will do for you? USB debugging just lets you run ADB, which you can already do when in recovery, and you'll still have a broken screen.

Just asking because if we know what the objective is there may be another way of doing it.

thanks, i want to use that program
https://code.google.com/p/androidscreencast/
 
Thanks. OK, I see why you need it now (and admit that I can't see an alternative).

When you tried that XDA method, what was it that replied that "The device was not listed"?

In the stackoverflow thread there was one reply to a reply which said that the setting stuck (on a different device) if they set it in another place in addition. Did you try that too?

TBH I've never tried to do this type of thing, so we may need to wait for someone who has experience.
 
Thanks. OK, I see why you need it now (and admit that I can't see an alternative).

When you tried that XDA method, what was it that replied that "The device was not listed"?

In the stackoverflow thread there was one reply to a reply which said that the setting stuck (on a different device) if they set it in another place in addition. Did you try that too?

TBH I've never tried to do this type of thing, so we may need to wait for someone who has experience.

The device boots normally, I am using Arch Linux, and yeah as i said the device is not listed
 
Sometimes security features work against us :( In most situations, this can save people a lot of pain when dealing with stolen devices and confidential information.
 
with clockworkmod you can pull all the information :D
and there is no digitizer for this stupid phone

TwRP as well. I use device encryption so I would still be fine :p ADB pull should work with both to get files off, but still can't bypass ADB Authentication
 
It may be possible to bypass RSA but its rarely talked about outside of the kernel dev community so far as I can tell. I'm not aware of an easy route. Here is a couple links to check out:

Android 4.2.2 RSA disabling - Stack Overflow
Read the upvoted answer and the associated response.

Android Explorations: Secure USB debugging in Android 4.2.2
Read that and the comments below the article.

After that, go here:
[MOD][HOW TO]Make your favorite kernel adbd insecure to run ADB as root on /system - xda-developers

In short, I'm not an expert in kernel development by any stretch. But I think it might be possible to modify the boot.img such to edit the ro.adb.secure setting to = 0 which may bypass RSA though I'm still not positive on that.

I've not personally seen this done but have observed mention of it on a few occasions. Since you have been able to flash cwm recovery, and have access to that, it seems you could potentially make that work. That said, I know nothing about your device, your bootloader or any limitations you might face.
 
It may be possible to bypass RSA but its rarely talked about outside of the kernel dev community so far as I can tell. I'm not aware of an easy route. Here is a couple links to check out:

Android 4.2.2 RSA disabling - Stack Overflow
Read the upvoted answer and the associated response.

Android Explorations: Secure USB debugging in Android 4.2.2
Read that and the comments below the article.

After that, go here:
[MOD][HOW TO]Make your favorite kernel adbd insecure to run ADB as root on /system - xda-developers

In short, I'm not an expert in kernel development by any stretch. But I think it might be possible to modify the boot.img such to edit the ro.adb.secure setting to = 0 which may bypass RSA though I'm still not positive on that.

I've not personally seen this done but have observed mention of it on a few occasions. Since you have been able to flash cwm recovery, and have access to that, it seems you could potentially make that work. That said, I know nothing about your device, your bootloader or any limitations you might face.

thanks for your effort, i will check what ill be able to do with this when i get some free time.
 
ThElitEyeS, couple of questions if I may (I'm not at all familiar with your device):

1. Is your bootloader unlocked on this device?

2. Do you have fastboot access to your device?

3. Do you know where the boot partition is on your device? (and what it's size is?)

Since you have root and adb access through custom recovery, I was envisioning pulling (using the dd utility) your boot.img from your boot partition. That could be unpacked, the ramdisk modified with the desired property values, re-packed, and re-flashed back to your device (assuming that's allowed / possible--hence the question re. the unlock status of your bootloader).

Having fastboot and an unlocked bootloader available would also make it possible to soft boot a tweaked boot.img file without having to flash it (makes debugging a little safer :p).

Let us know...there might be hope yet.

:)

edit/update 11:42 am 24-Apr-2014: I've done a tiny bit of research and it looks like the manufacturer ships the phone with a custom recovery already installed! :eek: :cool:. I'm guessing that it should be fairly straight-forward to monkey with more stuff on the device given this info. The xtreamer websites aren't loading well for me here at work, so I can't do too much more research re. this, but I'll have a peek again tonight to see if I can find a .zip file with a stock boot.img in it that could be tweaked.
 
Hmm, ran into a snag...:(

The boot.img and recovery.img files do not look like "traditional" bootable image files--at least as far as the utilities that I normally use go.

So, I currently cannot unpack them.

Not sure if the format has changed and/or if there are other existing tools available to manipulate these...

:dontknow:

edit: now wondering if these are actually zImage formats...
 
Back
Top Bottom