Develop Bugs

Enabled UMS and MTP command line.

I know I can use SGS3 Easy UMS but
Can someone tell me what the commands are to do these same actions from command prompt. This is on a Samsung Note 2 At&t.
1. Enabled UMS mode
2. Enabled MTP mode
3. Mount SD Card.
I am trying to write a tasker task that will kill all applications running and then run UMS mode. My car stereo is picky about what is running i guess. I always have to run advanced task killer to kill all apps and then run UMS mode. This allows my mp3 to play just fine.
I have tried the following commands
setprop persist.sys.usb.config mass_storage,adb
setprop persist.sys.usb.config mtp,adb
neither of those have worked

MTP problem

I have problems with connecting my mobile phone with other devices after introducing MTP connection - when I am pluging t989 into tv, there is a info about problems with recognizing the device, the same prompt is on other devices such like Satelite receiver, etc. Earlier when I had usb storage connection I didnt have such problems. Can sb help me with that ?

sony11 said:
I have problems with connecting my mobile phone with other devices after introducing MTP connection - when I am pluging t989 into tv, there is a info about problems with recognizing the device, the same prompt is on other devices such like Satelite receiver, etc. Earlier when I had usb storage connection I didnt have such problems. Can sb help me with that ?
Click to expand...
Click to collapse
This is possible to fix with some ROM/Kernel pairs, but not all.
you need to run a series of commands to prepare things for "mass storage" mode, and then run a different set of commands before removing it to prevent data corruption and data mismatch. I have found that if you add files while in this "pretend mass storage" mode, you sometimes need to reboot for them to sync up properly.
all of the commands need to be run as root.
first you need to put your phone into mass storage mode by running:
setprop sys.usb.config mass_storage
if you need adb access, run the command as:
setprop sys.usb.config mass_storage,adb
then you need to tell the system where to "look" for the mass storage devices. I will include the optional steps too (mounting the sd cards in RO mode to prevent both systems writing to the card at once which will likely cause corruption):
mount -o remount,ro /storage/sdcard0
mount -o remount,ro /storage/sdcard1
echo /dev/block/vold/179:97 > /sys/class/androd_usb/android0/f_mass_storage/lun/file
echo /dev/block/vold/179:28 > /sys/class/android_usb/android0/f_mass_storage/lun_ex/file
when you are done with your mass storage stuff, you will need to run the following to remove these shares:
echo "" > /sys/class/androd_usb/android0/f_mass_storage/lun/file
echo "" > /sys/class/android_usb/android0/f_mass_storage/lun_ex/file
mount -o remount,rw /storage/sdcard0
mount -o remount,rw /storage/sdcard1
I have not (yet) tested this on a KK ROM, but it works nicely on hellybean with Diablo or Uber kernels. Technically, I suppose you wouldn't need to run the remounts, but I recommend it as you don't want a corrupted filesystem. And technically I guess you don't need to blank out the "file" afterwards, but I do as I don't want android thinking I'm still connected when I'm not.
I personally don't like MTP as it doesn't play as nice with other older devices as mass_storage, but mass_storage doesn't allow both the android phone and windows/mac/linux/etc to preform RW operations at the same time without a high risk of data corruption.

How to enable USB debugging on a broken screen using ADB (Permission & Root Issue)

How to enable USB debugging on a broken screen using ADB (Permission & Root Issue)
I have a Samsung Note 2 with a Broken screen/digitizer. So no haptic feedback's. Anyway the USB Debugging is already on and I could use the Remote tools like SideSync, Mobizen & other software's on my old machine before the screen broke. But now with new laptop I need to re-enable usb debugging or accept the fingerprint thing that pops up but I can't see what's on my screen. Also I don't know how to force this.
I've tried following several guides on how to enable through build.prop and adding lines - http://forum.xda-developers.com/showthread.php?t=2652564
but when trying to push the file back -
Code:
failed to copy c:\android\build.prop /system/build.prop : permission denied.
I've tried
Code:
adb remount
&
Code:
adb shell
su
mount -o remount, rw /system
and for both I get remount failed : operation not permitted.
I've tried using
Code:
adb usb & adb root
adb root shows error -- adbd cannot run as root in production builds.
adb usb - is just stuck nothing happens.
I've tried googling the above errors but any solutions don't seem to be working.
Reason why I use this phone is because I have kodi installed and everything was working up until now. I had wifi on the device - Do you think I could just enable or rename my wifi name to the same one? Problem would be what password I used. I still have my old router.
Any advice?
Thanks

I believe the devices isn't rooted. I tried using ADB Shell and typed in captials SU but got not found however typing it in lowercase nothing happens. just goes to the next line

RAZER PHONE Diag mode(QPST USE) ?

I'm trying to...
1. tprop persist.usb.eng 1, setprop sys.usb.config mtp,mass_storage,diag,serial_smd,adb, setprop sys.usb.config diag,adb
or
2. dial app
*#*#717717#*#*
but diag port isn't open
Is there a way to access diag mode?

Enable adb and usb debug in TWRP 4K

Question.
Is it possible to enable adb and usb debug in twrp.
Currently i try to Bypass initial Setup .
It works with customized com.amazon.tv.oobe.apk
For pairing CEC is needed ,but it is not possible to enable debug and adb. ( no Option in settings ).

0815hoffi said:
Question.
Is it possible to enable adb and usb debug in twrp.
Currently i try to Bypass initial Setup .
It works with customized com.amazon.tv.oobe.apk
For pairing CEC is needed ,but it is not possible to enable debug and adb. ( no Option in settings ).
Click to expand...
Click to collapse
You can connect your Fire stick to your PC and follow these link:
https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd

0815hoffi said:
Question.
Is it possible to enable adb and usb debug in twrp.
Currently i try to Bypass initial Setup .
It works with customized com.amazon.tv.oobe.apk
For pairing CEC is needed ,but it is not possible to enable debug and adb. ( no Option in settings ).
Click to expand...
Click to collapse
I did this and it worked..
1) In Windows grab this file:
C:\Users\XXXUSERNAMEXXX\.android\adbkey.pub
and change filename to adb_keys
Put this on a USB stick that will be accesible form TWRP (You'll need a hub for both mouse and USB stick)
2) In terminal in TWRP type:
echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
echo '' >> /system/build.prop
echo '# Enable ADB' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
3) In File manager in TWRP
Make sure that the drives are properly mounted in the Mount option (I think it's system)
Copy adb_keys from USB stick to Firestick4Kt to this location
/data/misc/adb/
4) Reboot Firestick4K and connect to from windows

tinybilbo said:
I did this and it worked..
1) In Windows grab this file:
C:\Users\XXXUSERNAMEXXX\.android\adbkey.pub
and change filename to adb_keys
Put this on a USB stick that will be accesible form TWRP (You'll need a hub for both mouse and USB stick)
2) In terminal in TWRP type:
echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
echo '' >> /system/build.prop
echo '# Enable ADB' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
3) In File manager in TWRP
Make sure that the drives are properly mounted in the Mount option (I think it's system)
Copy adb_keys from USB stick to Firestick4Kt to this location
/data/misc/adb/
4) Reboot Firestick4K and connect to from windows
Click to expand...
Click to collapse
Thanks for the Help.
Got it working.