Go to default prop from vendor . Open default prop.Find
persist.sys.usb.config=mtp
Add adb after mtp and save and reboot.
Done
Like this .
persist.sys.usb.config=mtp,adb
Yea, but there'll be a comma
Should be like mtp,adb
Related
ok so im not responsible for anything that happens to you or your tablet....
this will add HW acceleration and adb in your build.prop(not fully test on g tab) and some other things with the kernel
lets begin
this has been only tested on ICS right now ill test on GB later
this WON'T work with a build.prop editor you are going to have to open the actual file
you NEED to be ROOTED
there are 2 ways of doing this and i will show both methods...
method 1.)
Code:
1.) with a root file explorer goto /system
2.) long press on the build.prop file till the menu comes up
3.) press "open in Text Editor
4.) paste the code into your build.prop and hit back
5.) when it ask if you want to save your changes hit yes
6.) reboot
note:**this was done with Root Explorer; it might and very well could be different in other apps.**
method 2.)
Code:
0.) you need the android sdk and adb working
1.) adb remount
2.) adb pull /system/build.prop
3.) open the file and paste the code into your build.prop
4.) adb push build.prop /system
5.) adb reboot
here is the code please add it to the end, so after whatever your last line is add this
Code:
ro.secure=0
ro.debuggable=1
persist.adb.notify=0
persist.service.adb.enable=1
persist.service.mount.playsnd=0
persist.service.debuggable=1
ro.ril.disable.power.collapse=1
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
com.qc.hardware=true
debug.enabletr=true
ro.min.fling_velocity=8000
ro.max.fling_velocity=12000
ro.config.nocheckin=1
video.accelerate.hw=1
Hi,
How do I save my kernel configuration as the default settings when building a kernel ? I use this:
$ make menuconfig
I save the settings when asked, but how do I make them the default settings so I don't have to keep going back and setting it all up again? When I build a kernel the settings are saved, but when I build a boot.img or do a:
$ make distclean
the settings revert back to what they were originally. What am I missing? Please help.
Thanks,
Problem solved!!!!!
I went through the process of setting up to build a kernel. I then entered the following commands:
$ make distclean
$ make <NAME>_defconfig
$ make menuconfig
After getting all my settings the way I wanted them, instead of exiting all the way to the "save settings yes or no", I exited to the main or home screen and hit the "Save an Alternate Configuration File". Then I named the file. This was saved in the "kernel" directory (by default). I went into the kernel/arch/arm/configs folder and renamed the (in my case) "imx6_defconfig" and "imx6_android_defconfig" files to "original_ imx6_defconfig" and "original_imx6_android_defconfig" (to keep the originals). I then took the Alternate Configuration file in the kernel directory and copied the contents and created my own "imx6_defconfig" and "imx6_android_defconfig" files in the kernel/arch/arm/configs folder. Now my settings are saved as the default settings (unless I go through this process again). I now can build a "rom" or a "boot.img". I can do a:
$ make distclean
and then:
$ make imx6_android_defconfig
I do not have to use the:
$ make menuconfig
to reset my settings.
persist.service.adb.enable=1 anytime i add it into the default prop and pack the boot image and try to test it it just hangs on the boot screen.. need some assistance in figuring out how to add persist.service.adb.enable=1 to the default prop in ramdisk.
CoffeeNAndroid said:
persist.service.adb.enable=1 anytime i add it into the default prop and pack the boot image and try to test it it just hangs on the boot screen.. need some assistance in figuring out how to add persist.service.adb.enable=1 to the default prop in ramdisk.
Click to expand...
Click to collapse
If you want to start adb on boot add adb to the USB config line , it will be similar to this :
persist.sys.usb.config =mtp,adb
messi2050 said:
If you want to start adb on boot add adb to the USB config line , it will be similar to this :
persist.sys.usb.config =mtp,adb
Click to expand...
Click to collapse
I added the adb and the persist.service.adb.enable=1 and got stuck on the boot screen. Maybe just persist.sys.usb.config =mtp,adb will do the trick.
CoffeeNAndroid said:
I added the adb and the persist.service.adb.enable=1 and got stuck on the boot screen. Maybe just persist.sys.usb.config =mtp,adb will do the trick.
Click to expand...
Click to collapse
Exactly
messi2050 said:
Exactly
Click to expand...
Click to collapse
That worked.. thanks.. booted right up..
CoffeeNAndroid said:
That worked.. thanks.. booted right up..
Click to expand...
Click to collapse
You are welcome
Im getting closer to my goal.. i got adb shell to work and the device to show up as a reconized device with adbd insecure cause the way it patches it makes the device as a attacted device even though the rsa fingerprint never asked you to allow the computer/laptop which is what is giving the unauthorized device errors and vendor keys not set. Thats why adb root access would only work with a custom recovery but now i see it works with adbd insecure and bypasses the rsa fingerprint. Ive got alot of testing to do..
Getting there slowly
Is it possible change settings like those
development_settings_enabled 1
enable_freeform_support 1
only by MCU update? or it works only for full images, and settings like those can not be easly updated?
SOLUTION
It is easier to do so by manually editing prop files via ADB
adb root
adb remount
adb pull /default.prop default.prop
edit file
adb push default.prop /default.prop
Is it possible to enable root debugging from the command line. The rom that I'm using is missing the setting in developers options. When trying adb root I get the
Code:
ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options
I don't believe it's totally disabled because I don't get the "adb root is not allowed in production builds". I think it's there but no switch to toggle. Haven't found anything searching for setting name and would need correct value and table if it can be set. Anybody know how to toggle it on from shell ?
Command adb root works in development builds only ( i.e. eng and userdebug which have ro.debuggable=1 by default ). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to /system/build.prop file.
If you want adb shell to start as root by default - then add ro.secure=0 as well.
jwoegerbauer said:
Command adb root works in development builds only ( i.e. eng and userdebug which have ro.debuggable=1 by default ). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to /system/build.prop file.
If you want adb shell to start as root by default - then add ro.secure=0 as well.
Click to expand...
Click to collapse
Thanks, actually looking into it, I don't know what to think about it. It is a user build of crdroid. I can not and absolutely do not understand the point of building a user build to post on XDA. The fact that someone is installing a custom rom kinda throws a user build out the window AFAIFC. It didn't even dawn on me to check if it was userdebug or not, in my mind, of course it is. That's what I get for thinking I guess. I like CrDroid so syncing source now, time to sync and build I should have an eng build in about 3 hours.
Take note that if adbd in your phone's firmware is build without ALLOW_ADBD_ROOT then you're wasting your time.