[Galaxy S III Q&A, Help & Troubleshooting] andrioit:
Hello guys, first i hope it's in the right place to post this and second sorry for my english.

And also thx for many tips i got from here on my road to get this working. But now i don't know what to do.

(Win 7 Starter 32bit, Android Debug Bridge version 1.0.31)

My situation: had a S3 (I9300) with Android 4.3 and a broken screen. Touch is still working. The broken screen wasn't a problem at first, because as it fell down, the screen was all right. After about 15 min it started to get black at the top. But most of the screen was ok. After the night everything was black.

So i read about droidatscreen and started to root and play with the device. First i put CF-Root-SGS3-v6.4 with Odin on the phone and then started to try to make adb work under Android.

I was in recovery and add this line to the build.prop "persist.service.adb.enable=1" .

I'm not sure, but i think after a reboot of the phone i had adb running under Android. At this time adb said not authorized and the window with the confirmation for usb debugging wasn't popping out (because i tried and tried to touch at the place where it shold be).

Than i read about "persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb" adding to default and build.prop , also didn't work.

Than i added "ro.adb.secure=0" and changed "ro.adb.qemud=1" to 0 in both files, and after rebooting the phone i hit the place on the screen and adb devices went from unauthorized to device. I finally made it and could use droidatscreen. (i don't think that ro.adb.secure=0 deactivated the rsa fingerprint, but i think it got it to pop up the confirmation window).

Now i was able to see the menue, i changed some things in options, like touch sound and screen unlock sound to be able to hear the things i couldn't see, i also changed the setting for showing touches in the dev menue.

And now the bad thing happened, i touched the option usb debugging (not on the check, but on the word itself (i could see it because of the latency of droidatscreen and the phone rebooted and wasn't able to connect to adb).

Now i only get the mtp device and adb devices shows nothing but a blank line.

I'm still able to change build.prop and other data in recovery but even load the original files to the phone and going step by step further didn't bring me the unauthorized message in adb devices.

I hope someone could help me. Maybe someone knows the files which are changed during changing the options in Android menue.

Btw. i already wiped cache, but do not want to do more than this (i mean wiping :) ).

Thx

Edit:

Solved the problem.

Found out about the getprop and setprop commands and used getprop in adb shell. Didn't found anything like "persist.service.adb.enable" ... , only something like

[service.adb.root]: [1] [ro.adb.qemud]: [1] and [persist.sys.usb.config]: [mtp] .

Searched in /data/property for adb things, and saw "persist.service.adb.enable" "persist.sys.usb.config" .

"getprop persist.service.adb.enable" showed a blank line, so i "setprop persist.service.adb.enable 1",

now "getprop persist.service.adb.enable" showed a 1 and after rebooting phone, i was able to get a unauthorized message from adb devices, and reconneting the usb let the confirmation popup.

Thx anyways.