Database Users

[HOW TO] enable non market apps

I don't know about you, but SuperOneClick's Allow Non Market Apps feature didn't work for me. When I went to setting>applications there was no check box for Unknown sources present. I got it by using Root Explorer and SQLight Editor (both on the market)
1. Use "RootExplorer" take you to
/data/data/com.motorola.android.providers.settings/databases/settings.db/settings
2. click on the "Value" colum of "force_only_market_apps"
3. Press "menu" button and select "Edit Field"
4. Change "1" to "0", then save.
Without even doing a factory reset or just a regular reboot you should have an unknown sources box available in your settings>applications.

That's not how it works. When you use the option in SuperOneClick, it enables that option for you, even if it doesn't show up in settings>applications.

Thanks. When using SuperOneClick I was able to root, but I wan't able to allow Unknown Sources through Settings->Applications.
Now it works!

thanks, sideloading didnt work for me using aroot.

i rooted using SOC a while ago, and DLed the official PSN apk yesterday since it's not on the US market, and installed it by clicking the apk in file manager with no problem.

Thank you so much! This finally worked! Using aRoot/GladEnable/SuperOneClick , all of them SAID it was enabled but it clearly wasn't ... when I navigated to the db field it was still at '1' .. thanks for this, finally it's working

i am on gingerblur, and when clicking the menu button i don't get a dialog to do anything. Maybe a bug of the theme?
So i can't use root explorer to do this, but anyway this is useful since now i know the database name and can do it by hand...

For those that want to do this by hand:
-connect your phone via usb, enable usb debugging
-from a command line, go where you have adb installed (android sdk or many scripts on this forum)
-run adb shell, then su. accept the message on the phone if prompted.
-type: sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" then enter, and you are done

franciscojavierleon said:
For those that want to do this by hand:
-connect your phone via usb, enable usb debugging
-from a command line, go where you have adb installed (android sdk or many scripts on this forum)
-run adb shell, then su. accept the message on the phone if prompted.
-type: sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" then enter, and you are done
Click to expand...
Click to collapse
I tried this and it did not work just said sqlite3 not found. Type exit and type exit then type sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" it just locked up terminal. If I type sqlite3 before adb shell it finds it.
Used root explorer and copied settings.db to sdcard. Once there used as a disk drive on computer. Edited it with navcat for sqlite and saved it. Then disconnected it for computer used root explorer and copied it back to data and overwrote existing file. Rebooted and all was fine.

I did everything, but I am not able to edit the field...
"Thanks

manpreet14 said:
I did everything, but I am not able to edit the field...
"Thanks
Click to expand...
Click to collapse
thanks much
i got it

BravoMotorola said:
I don't know about you, but SuperOneClick's Allow Non Market Apps feature didn't work for me. When I went to setting>applications there was no check box for Unknown sources present. I got it by using Root Explorer and SQLight Editor (both on the market)
1. Use "RootExplorer" take you to
/data/data/com.motorola.android.providers.settings/databases/settings.db/settings
2. click on the "Value" colum of "force_only_market_apps"
3. Press "menu" button and select "Edit Field"
4. Change "1" to "0", then save.
Without even doing a factory reset or just a regular reboot you should have an unknown sources box available in your settings>applications.
Click to expand...
Click to collapse
Thanx. Very useful info.

Worked for me.
Thanks

Works Great. Thank you!

is there a way to enable side loading with out rooting the phone?

aszrael1266 said:
is there a way to enable side loading with out rooting the phone?
Click to expand...
Click to collapse
sideload wonder machine. look it up. pretty easy.

BravoMotorola said:
I don't know about you, but SuperOneClick's Allow Non Market Apps feature didn't work for me. When I went to setting>applications there was no check box for Unknown sources present. I got it by using Root Explorer and SQLight Editor (both on the market)
1. Use "RootExplorer" take you to
/data/data/com.motorola.android.providers.settings/databases/settings.db/settings
2. click on the "Value" colum of "force_only_market_apps"
3. Press "menu" button and select "Edit Field"
4. Change "1" to "0", then save.
Without even doing a factory reset or just a regular reboot you should have an unknown sources box available in your settings>applications.
Click to expand...
Click to collapse
Thanks for this instruction...

Even though this thread is a little old it did help me and therefore want to add my two cents worth to possible help others who may be having issues. I have a rooted Motorola Flipside.
I purchased SQL Lite Editor from the market and was able to change the value directly in it. Here's how:
1. Download and install SQL Lite Editor from the market.
2. Start SQL Lite Editor to display a list of the applications installed on your device.
3. Look for the application titled Settings Storage (and in smaller print underneath it will display "com.motorola.android.providers.settings".
4. Select Settings.db.
5. Select Settings.
6. In the list of columns scroll down to item #70, "force_only_market_apps" and select it.
7. Click the shortcut menu on your device and select Edit Record.
8. Change the value from 1 to 0 then save and exit SQL Lite Editor.
9. Go to Settings > Applications. Unknown Sources will be visible and you will be able to check it.
Hope this helps anyone else who has issues.
Regards,
Greg

franciscojavierleon said:
For those that want to do this by hand:
-connect your phone via usb, enable usb debugging
-from a command line, go where you have adb installed (android sdk or many scripts on this forum)
-run adb shell, then su. accept the message on the phone if prompted.
-type: sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" then enter, and you are done
Click to expand...
Click to collapse
You are awesome buddy.. thanx

[Q] Broken Screen, Need to Enable ADB

Hello all!
I have a Nexus 7 with a broken screen and non-functional LCD (i.e., no backlight or any changes visible on the screen). It has CM10.1 (probably a January build) and CWM (I want to say 5.x, but I don't remember). I had a complex screen unlock password, so I stupidly rebooted into recovery and did a factory reset via ADB. However, this caused the debugging flag to be disabled, hence destroying my ability to control the device through ADB.
Questions:
1) Can someone walk me through the procedure to go from the device's "off" state to CWM?
2) Can someone tell me how to re-enable the debugging switch after mounting system?
Thanks!

I am not sure, but I think ADB in recovery mode is always enabled, so why do you want to enable ADB for the "normal" mode? You can do everything in recovery mode, too.

It works!
AndDiSa said:
I am not sure, but I think ADB in recovery mode is always enabled, so why do you want to enable ADB for the "normal" mode? You can do everything in recovery mode, too.
Click to expand...
Click to collapse
You can do a lot of things in recovery mode, except for setting up applications once they are installed. I wanted to set up a VNC server on that tablet so I can see the screen and click on whatever, and eventually use the device's sensors and antennas for other reasons. On top of that, I was having the stupid issue of not being able to go into recovery again (since you need to scroll through a menu before reaching the "Recovery" option on the Nexus 7).
Anyways, I got it to work now:
To go into "Recovery" mode and enable ADB inside the ROM (I had CM10.1 installed, but it shouldn't matter for most JB roms):
1) Turn the tablet off or check that it is off. Since my screen was broken, I ended up opening it and unplugging/replugging the battery
2) Vol Down + Power button, wait for ~5 seconds
3) Press Vol Down twice, and then press Power
4) On computer, go to "adb shell"
5) Enter the following commands:
Code:
mount /system
mount /data
echo persist.service.adb.enable=1 >> /system/build.prop
cp /data/data/com.android.providers.settings/databases/settings.db /data/data/com.android.providers.settings/databases/settings.db.old
9) Exit adb, enter command:
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db.old ./settings.db
10) Using any SQL database editor, modify settings.db to change "adb_enabled" to 1
11) Save, exit, and enter command:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Now, you can reboot the device (adb reboot). After a few seconds, you should be able to capture screenshots.
I wrote a little bash script to automate the process, so I can get a (somewhat) moving image (at best, I got 4 FPS )
Code:
while true; do
adb shell screencap -p | sed 's/\r$//' > screen2.png
if [ -s screen2.png ]
then
cp screen2.png screen.png
fi
done
Note that it is "buffered" -- if adb fails for any reason, the code will continue until adb is able to get another image.
At this point, you can start adb shell, and then use the following command to send taps, swipes, keyevents, or text:
Code:
input text <string>
input keyevent <key code number or name>
input tap <x> <y>
input swipe <x1> <y1> <x2> <y2>
Doing this, I was able to get all the way to installing a VNC server. I used Droid VNC Server:
https://play.google.com/store/apps/details?id=org.onaips.vnc&hl=en
Of course, you can choose whatever server you want. Just configure it correctly, and then you can stop the script and access the tablet remotely. Also, remember to disable the screen lock -- it's really annoying to have to swipe on the lockscreen using the command each time.
At this point, I've gone ahead and enabled ADB over WiFi, allowing me to access virtually everything for this device from any location.
Time to build something with my (severely handicapped) Nexus 7!

Thank you for this interesting post!
I wanted to suggest a similar process, but I first I wanted to understand better, what you wanted to reach. Yeah, ADB is a very powerful tool, I do not want to miss it.

[TWEAK] Disable Wifi on screen off

[REF] Disable Wifi On Screen Off
RyanZA said:
Some people have picked up an annoying bug - I'm not sure where it comes from, some believe it is the voodoo kernel, I think it is probably JPC firmware or similar.
The bug: When you have wifi on and you turn the screen off, wifi does not turn off like it should.
The reality: The wifi turn-off time has been reset to the android default 15 minutes. You can change this setting if you want. (I like 10 seconds myself.)
You will need:
1. ADB root shell access.
2. SQLite3 Explorer - http://www.singular.gr/sqlite/
or SQLiteBrowser - http://sqlitebrowser.sourceforge.net/
What to do:
1. shell command: busybox cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
2. adb command: adb pull /sdcard/settings.db
3. Open settings.db in SQLExplorer
4. Right click on gservices or secure folders**, choose 'Show Data'
5. Click on the green plus icon "Insert Record"
6. Double click on name column, insert "wifi_idle_ms" - Double click on value column and insert "10000" for 10 seconds for wifi to turn off. 30000 for 30 seconds, etc.
7. Click on the green tick.
8. Right click on the folder again, choose show data, scroll to the bottom and ensure that your change has been made.
9. File -> Close Database
10. adb command: adb push settings.db /sdcard/settings.db
11. shell command: busybox mv /dbdata/databases/com.android.providers.settings/settings.db /dbdata/databases/com.android.providers.settings/settings.db.bak
12. shell command: busybox cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings/settings.db
13. shell command: chown system.system /dbdata/databases/com.android.providers.settings/settings.db
** I'm not sure if the correct folder is gservices, or secure. I believe secure is the correct one though. I just added it to both.
This is too hard:
If there are 10 or more people who have this bug but can't do the required fix, I'll make a small utility to do it for you. Let me know.
Click to expand...
Click to collapse

scratch my above post, this tool will give you full wifi control
[APP][2.1+][20 May - 2.1RC1] Better Wifi on/off

How to Turn Off Carrier Notification of Tethering

I have seen threads on how to turn on tethering. My question is not about how to turn on tethering - I am looking to see if there is a way that the notification from the phone to the carrier that tethering is on can be disabled (yes I know they can do packet inspection, but I usually tether an Android tablet where the packets basically look like phone packets.)

Mount /system read-write in recovery and run this command (with all the standard disclaimers about modifying /system):
echo net.tethering.noprovisioning=true >> /system/build.prop
Also, run this from a root terminal or adb shell:
settings put global tether_dun_required 0

[Sprint/others?] Hotspot now functions correctly with root

Hi there, before now some people were having issues with the hotspot workarounds, where they could enable the hotspot but attached devices received no actual internet. I didn't do any polling but it seemed to be mostly a Sprint phenomenon, as after doing the magic hotspot trick most other people had no issues.
I just tested it, and the new root will get you functioning hotspot on Sprint, and possibly for other people too who were having the same problem. I ran the following code while the hotspot happened to be off, and after turning it back on I was able to get internet through it on other devices. If you try this with the hotspot already enabled please report back so we know if it needs to be either particular setting. Use a normal command line where you have adb.exe and run this command while the phone is on and no further action should be needed once you turn on the hotspot.
Code:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
Just having root itself has not enabled the normal hotspot switch locations, like in the notification drawer or in the tethering settings, and I still had to use the network refresh trick to get them to work. This may need another command to insert/change the correct protection setting, or something else entirely.
I also went back to the APN settings through the shortcut maker and received the same error I had before, about this user not being able to access them.
On a related note, I saw some people mention that their hotspot would automagically turn off after 10-20 minutes, so I'll post this now and keep an eye on whether it does so here, as I never watched before.

I used that code for my Nexus 5 on T-mobile without rooting. My Pixel is on back order and not able to test it on T-mobile. Is it necessary to root for only the phones on Sprint? Anyone test it on T-mobile (for native hotspot)?

Sorry, yes, I copied my post from a comment I made in another hotspot thread where the code was brought up and I tested it, but it didn't work for me without root. Some people were able to use hotspot after using a workaround, including Verizon, but it seemed like for Sprint doing that gave hotspot but no internet access. Once you get your phone I would check out that workaround comment, and if you have problems try the root command.

Sprint Tether working now for me on adroid 7.1
I tried many things including the above..but none worked. I was able to root the system and what worked for me.
I followed these directions
Go here http://www.theandroidsoul.com/enabl...ing-pixel-and-pixel-xl-verizon-sprint-others/
Setup ADB and Fastboot on your PC (link).
Download the CarrierEntitlement.apk file and save it to a separate folder on your PC.
Connect your Pixel phone to the PC.
Open a command window inside the folder where you saved CarrierEntitlement.apk file in Step 2 above. To do that, “Shift + Right click” on any empty white space inside the folder and then select Open command window here from the context menu.
Once the command window is open, issue the following commands one-by-one disable provishning checks on your Pixel phone:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
└ You may get a prompt on your phone to grant root access, accept it.
mkdir /su/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /su/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /su/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /su/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /su/su.d/05TetherMod
chmod +x /su/su.d/05TetherMod
reboot
Your phone will now reboot. Once that is done, go to Settings » More » Tethering & portable hotspot » and enable Portable WiFi hotspot. It should work.
I found this did work to enable the wifi hotspot app but this didnt let the computer connected browse the internet.
I then found this and now im able to browse on a computer connected to my hotspot
http://www.theandroidsoul.com/enable-tethering-nougat-alongside-android-pay/
I only used this part
Download/install a Terminal emulator app from Play Store (link →).
Make sure the terminal asked for rights when typing su because you have to grant it before it works correctly
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
Now my computer connected to the hotspot worked perfect and im very happy.
but i think if you follow this you can get it working right away without my above stuff.
Root your Android device running on Android 7.1 Nougat.
Edit build.prop file: Add the net.tethering.noprovisioning=true line to the bottom of build.prop file on your Android device. Use the link below for help with editing build.prop file.
How to edit build.prop on a rooted Android device
Reboot device after saving changes to build.prop file.
Download/install a Terminal emulator app from Play Store (link →).
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the app when asked.
Reboot device.
That’s it. You should have Tethering enabled on your Android 7.1 Nougat running device now.
I hope this helps as I haven't found this info in one area on here and sorry if it is but I didnt find it.