Database Users

[Q] Any luck getting unknown sources outside of the listed guide?

Been trying to get Unknown Sources on my phone for the better part of 2 weeks. Have tried everything I can find on google, tried SuperOneClick, and tried the guide on here at least 10-15 times. http://forum.xda-developers.com/showthread.php?t=867637
There are a few replies in the guide i just linked where people are having the EXACT same errors I am but said it was fixed by manually running the script...
I know NOTHING about scripting and have no clue what it means to manually run a script. Anybody know another way to do it or can anybody explain to me how to manually run the script?
I know this is a highly noob question but i'm out of choices. As I said I've done EVERYTHING i know how. Been working to the point that I now hate this phone.

When the poster mentioned running it manually they were talking about using adb to push the altered files to the correct location. That's what I had to do to get it working since the script didn't execute properly.
you have to take the settings.db files out of the zip at the end of the first post and put them in the same directory as your adb.exe (depending on your OS this could be in a few locations). Note you don't want to push the same settings.db to both locations, there are 2 files. The file structure of the zip file matches that of the phone so you just need to drill down into the zip file to find the right files.
adb push settings.db /data/data/com.motorola.android.providers.settings/databases/
adb push settings.db
/data/data/com.android.providers.settings/databases/

[HOWTO] Dalvik2Cache 90MB extra Space for Apps

found this http://forum.xda-developers.com/showthread.php?t=1174160 here in the forum, but cant get it to work on my neo
after a little seaching i found an other script that seems to work on NEO maybe on ARC too
also install-recovery.sh isnt execute on my neo so i put the call into hw_config.sh and it works fine now
howto.
1. push dalvik2cache /system/bin/dalvik2cache
2. adb shell
3. chmod 755 /system/bin/dalvik2cache
4. echo "/system/bin/dalvik2cache" >> /system/etc/hw_config.sh
5. reboot
btw. you need an inscured adb or an insecure kernel like this -> http://forum.xda-developers.com/showthread.php?t=1197263
if you do that, then at your own risk, do not complain when your phone is broken

hi,
i think it should also work without insecure adb and with stock kernel.
but root is needed...
copy the dalvik2cache file to sdcard first
with rootexplorer copy file to system/bin
set permissions
edit the hw_config.sh with editor (rootexplorer)

works great, thanks!

since my kernel supports init.d binaries/scripts u can actually just push it to /etc/init.d/ OR /system/etc/init.d/
it should work... though u may need to verify permissions... chmod 777 is best bet

DooMLoRD said:
since my kernel supports init.d binaries/scripts u can actually just push it to /etc/init.d/ OR /system/etc/init.d/
it should work... though u may need to verify permissions... chmod 777 is best bet
Click to expand...
Click to collapse
can you please post 1,2,3,4 simple guide to make this work with you fantastic kernel Doomlord?
i really need more space for apps
@inteks: what are the cons of this dalvik2cache? if there are cons

Alejandrissimo said:
@inteks: what are the cons of this dalvik2cache? if there are cons
Click to expand...
Click to collapse
i found out that some apps dont work just after install they need a reboot before they work ?!?!
dont know why!

DooMLoRD said:
since my kernel supports init.d binaries/scripts u can actually just push it to /etc/init.d/ OR /system/etc/init.d/
it should work... though u may need to verify permissions... chmod 777 is best bet
Click to expand...
Click to collapse
i placed a scipt in /etc/init.d/ but it isnt execute on startup ...
ps:
the script is startable and permissons should be ok.
if i place the name of that script (/etc/init.d/start.sh) at the end of hw_config.sh then its executet on startup

Hi friends,
I've been trying to do this but I really don't know how to use adb. I have Android SDK installed on my computer, and fastboot, flash...ect. But every time I type "adb remount" then I get the answer is 'adb' is not found (blah blah blah...).
Plus my phone can't boot to recovery. Anyone please tell me where can I find the instruction how to do it? I really want to have more space for my phone and move all installed apps to sd card (I also have my sd card partitioned with ext3 and fat32).
Many thanks in advance.

Saigonian said:
I've been trying to do this but I really don't know how to use adb.
Click to expand...
Click to collapse
Have a look at first post in this thread - you have to copy two files
Saigonian said:
Plus my phone can't boot to recovery.
Click to expand...
Click to collapse
You will have to unlock your phone first and then, using adb, install a custom kernel by fx. DooMLoRD from the link in my signature.

I dont know how to use cmd, can I use Root Explorer?

Anyway to revert it back? Because few apps are missing after it's done.

inteks said:
found this http://forum.xda-developers.com/showthread.php?t=1174160 here in the forum, but cant get it to work on my neo
after a little seaching i found an other script that seems to work on NEO maybe on ARC too
also install-recovery.sh isnt execute on my neo so i put the call into hw_config.sh and it works fine now
howto.
1. push dalvik2cache /system/bin/dalvik2cache
2. adb shell
3. chmod 755 /system/bin/dalvik2cache
4. echo "/system/bin/dalvik2cache" >> /system/etc/hw_config.sh
5. reboot
btw. you need an inscured adb or an insecure kernel like this -> http://forum.xda-developers.com/showthread.php?t=1197263
if you do that, then at your own risk, do not complain when your phone is broken
Click to expand...
Click to collapse
I'm sorry was that a typo? When your phone gets broken! Or if?
Sent from my LT15i using XDA Premium App

Hi harfot,
Thank you so much! I have it done now! But I wonder why the free space in my phone is now still the same (184MB - Because I only have a few apps installed).

inteks said:
hi,
i think it should also work without insecure adb and with stock kernel.
but root is needed...
copy the dalvik2cache file to sdcard first
with rootexplorer copy file to system/bin
set permissions
edit the hw_config.sh with editor (rootexplorer)
Click to expand...
Click to collapse
hey! This sounds like a best solution if you dont want to unlock the bootloader. But I am not too advanced user yet, could you please explain me this one with more details? actually I only need to know
1). which permissions exactly need to be set and
2). what to write inside the hw_config.sh file
Any help appreciated!

bump! no one has any ideas?

Thanks it's work in arc

unable to switch keyboards in rooted nst with nook Color tools

Hi,
I have rooted NST, installed Any Soft Keyboard from the market as well as pushed a copy in the /system/apps folder.
When trying to use Nook Color Tools to switch the keyboard, it doesn't show that the Any soft keyboard exists.
Any ideas ?

Did you reboot after pushing the apk into /system/apps ?

cowbutt said:
Did you reboot after pushing the apk into /system/apps ?
Click to expand...
Click to collapse
Same problem, did reboot

This is specific to my keyboard app.
Use it as a guide to do your own keyboard thing.
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update secure set value='com.android.inputmethod.latin/.LatinIME:com.temblast.nullkbd/.NullKeyboard' where name='enabled_input_methods';
update secure set value='com.android.inputmethod.latin/.LatinIME' where name='default_input_method';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db

You need to reinstall from the system/app folder once you move them.

Y-3 said:
You need to reinstall from the system/app folder once you move them.
Click to expand...
Click to collapse
Installing from there didn't help.

Enabling multiple IMEs (Input Method Editors) and selecting them is usually part of Settings.apk
If you have the stock Nook Settings.apk this is not included.
The easiest way to enable another IME is using SQLite to modify settings.db in my previous post.
You could also use Settings.apk taken from the Emulator in the SDK.
That would require you to re-sign your entire system with a new signature.

[Q] build.prop edits for 803

I'm trying to edit the build.prop file on the G2 803 model. It's rooted and unlocked on a stock Bell Rom. The phone has the wi-fi forgetting problem. everytime I reboot it I have to reset the wifi password. I've tried editing the build.prop file to change the wifi.lge.patch line to=false but I can't seem to enter more than 4 characters after the = on that line. Am I missing something?

Use build prop editor free on playstore
_____________________________________Read more write less and be smart

siggey said:
Use build prop editor free on playstore
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
Thanks, I tried that but the changes don't appear to stick.

Fraggle_Shamy said:
Thanks, I tried that but the changes don't appear to stick.
Click to expand...
Click to collapse
Reason 1: Some build.prop values get their values from the ramdisk on each boot, so that's why some values wont stick.
Reason 2 (requires root): build.prop is located in /system. Your /system may be read-only, we want it to be read-write to make changes, so.. run the following command in a Terminal Emulator downloaded from the play store. Run the following commands,
Code:
su
mount -o rw,remount /system
Now make your build.prop changes. Once finished run the following command to get your system back to how it was,
Code:
mount -o ro,remount /system
If the app isnt helping you, download a file explorer such as ES and navigate to /system/build.prop, open the file and edit the values you want.
Note: It's nice to hit the "Thanks" button under our posts if you indeed are thankful. Saying thanks and not hitting the thanks button is a slap in the face .

Thanks for the suggestion, but the emulator didn't help. I'm guessing it's because it's locked to the boot rom (your first suggestion)? Any way around this? I have anohter 803 that doesn't have this issue. Can I copy the ROM from that phone to the problematic one?

Fraggle_Shamy said:
Thanks for the suggestion, but the emulator didn't help. I'm guessing it's because it's locked to the boot rom (your first suggestion)? Any way around this? I have anohter 803 that doesn't have this issue. Can I copy the ROM from that phone to the problematic one?
Click to expand...
Click to collapse
Try this. (Pretty much the same as a previous suggestion, doubt it will work)
Get a root capable browser. Jrummy has one that's free, I think it's called Root Browser.
Browse to /system there should be a button to mount it r/w, if not it may prompt you when you go to edit the file... Long click the file, and try to open for editing. (it may be some other combination, I don't have my phone handy right now). Make the a change or two, reboot and see if they stick.
Or the other thing you cna do is:
The other thing you can try is to do is check if they're being set on boot.
adb pull /*.rc
which will pull all of the ramdisk's initialization scripts into your current folder on your computer. Look through them and see if the values are indeed being set by the boot image. If they are, you'll need something like AIK (android image kitchen) to extract the ramdisk, either change or delete those lines, rebuild the boot.img and flash it (using flashify or manually using adb and dd). You have to rebuild them into the boot.img, any changes you make to them directly on the phone will never stay as they get re-created every boot. It's a pretty roundabout way to do it, but it's entirely possible to do.
A much easier, and less likely to cause you issues would simply be to create an init.d script that sets it. This will occur after whatever is setting it in your boot.img so there would be no need to recreate that.
create a file in /etc/init.d called something like... "Set_wifi_pass" set the permissions so that it can be executed and read by everyone.
Then enter the following:
Code:
[B][I]#!/system/bin/sh[/I][/B]
setprop wifi.lge.patch = WifiPassword
You can check that it worked by going through adb shell with
adb shell
getprop wifi.lge.patch
which should return that value you set. Same thing that build.prop is ultimately doing, just in a different way.
Hope that helps.

build.prop please upload

HI , im new here but i know a long time ago about this community, anyway, someone can help me uploading a build.prop of the moto g5 plus, i modify it and well... :/ i try to fix it whit a adb on the command promp but my phone still stuck on the boot, and i sorry about this topic maybe can help on the future

Which model do you have? What build are you on? Are you running a custom ROM?
It would probably be easier to post your build.prop and see if someone will look at it and give you some advice as to what is wrong.

willclein said:
Which model do you have? What build are you on? Are you running a custom ROM?
It would probably be easier to post your build.prop and see if someone will look at it and give you some advice as to what is wrong.
Click to expand...
Click to collapse
Thanks in advance for the reply, i can solve the problem flashing the firmware beacuse i have some troubles on the console using adb, but this happening beacuse i dont give it the correctly permisons, but i want share the way to fix that problem as well, therefore i bring the solution on the command prompt on windows, the solution is very simply but helpfull
step by step, there are been taked on the siteweb TAS beacuse i'm a new user and i cant post url's of the other sites
///
Setup ADB and Fastboot on your PC.
Boot your Android device into TWRP recovery.
Select Mount » and then select System from the list of partitions to mount the system partition and then go back.
Connect your device to the PC with an authentic USB cable.
Open a command window on the PC and issue the following command to pull build.prop file from the device:
adb pull /system/build.prop
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from.
└ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file.
Download and install Notepad++ software on your PC.
Open the build.prop file on your PC using the Notepad++ program.
Edit the build.prop file as per your requirement and save it on the PC after making the changes.
Once you’ve saved the edits to the build.prop file, push it back to the device using the following command:
adb push build.prop /system/
Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
adb shell
cd system
chmod 644 build.prop
Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option.
thanks and i hope this can help someone else

The number one issue I see with people modifying build.prop (myself included) is forgetting to fix the permissions once you are done. My preferred method for editing it is using BuildProp Editor. It makes editing easy as well as makes setting the permissions extremely easy without having to use ADB. Best part is you can do this on the fly instead of having to use your PC.