Database Users

How to UNINSTALL unwanted stock/preinstalled apps from G1

How to remove unwanted stock/preinstalled apps
This is not a question. This is howto
I DID search through the forum and found nothing but
Q: how to remove/uninstall preinstalled apps ?
A: no way !!!
WHAT ??? WRONG ANSWER !!!
Here is how:
First of all I’ll describe my rooted, of course, phone configuration, so if you are on the same boat you can do same trick 99% if not you’ll know where to go
- CyanogenMod 4.1.2.1 (this is latest experimental as of sept-05-09) –works very stable for me
- 4GB SD card partitioned: FAT32, ext3 (512mb), linux_swap (32mb)
(great guide how to part your sd here: http://androidcommunity.com/forums/f56/compcache-userinit-22465/index4.html#post232988 (page 4)
- CompCache with Backing Swap (here: http://androidcommunity.com/forums/f56/compcache-userinit-22465/index4.html#post232988 (page 1)
Requirements:
1) G1 rooted phone
2) Explorer with ability to explore /system folders – I use Astro (market)
3) PC/MAC
4) SDK installed on it (http://developer.android.com/sdk/download.html?v=android-sdk-windows-1.5_r3.zip)
Steps:
1) first and very important: full backup of your system.
- DO NANDROID (it’s preinstalled in Cyano, search forum for “nandroid” if you don’t have it)
- DO ext3.tar (if you use ext3)
- Make full SD copy to your PC
As described here: (yes, same tread, thanks to bdb4269) http://androidcommunity.com/forums/f56/compcache-userinit-22465/index4.html (page 4)
Now we are safe..well, almost
2) find full name for the application you want to uninstall, say for Amazon MP3 it will be com.amazon.mp3.apk
I did it like this
- open Astro explorer
- go to the very top (/)
- search “amazon”
- when search done, write down full app name
- long press trackball – chose – open containing folder – remember the path (ie /system/app)
3) Assume SDK and USB drivers are installed ( http://developer.android.com/guide/developing/device.html )
And phone is connected to pc/mac
= below guide is from http://oneclickandroid.blogspot.com/ with my comments =
- Start emulator (don’t think it is necessary, but lets follow – emulator located in SDK folder\tools\emulator.exe in my case C:\SDK_15\tools\
CMD window pops up for a second and disappeared
- open CMD prompt (in Windows: Start > run > print: cmd , hit OK/enter)
- execute "adb shell" in on terminal from SDK_ROOT/tool folder
(if you did not register SDK folder in windows variables you need to cd to this folder first:
print: cd c:\sdk_15\tools hit enter
print: adb shell hit enter, you’ll see new prompt appeared: #
- print: mount -o remount,rw /dev/block/mtdblock3 /system
This will mount your system folder with read/write permission
- go to system/apps folder of your phone
(print: cd /system/apps hit enter)
*** guide says “/system/apps” but in my case it is “/system/app” ??? (remember I asked you to write down full path and name from Astro ? check your path first ***
- print: rm yourunwantedapplication.apk
i.e. rm com.amazon.mp3.apk hit enter
now, check installed apps in your phone (no reload req.) – is amazon disappeared ?
I wish to try this with app for that has a replacement from the market, like
Dialer – aTakePhone or Music – Meridian etc
Hope someone brave will do it before I do
Deleting may be unsafe if other preinstalled apps or process have links to uninstalled app
What happens in this case? wish someone knows the answer.
I dont think this trick will speedup your phone if you've moved your apps to ext2/3/4 already I just dont want to see useless apps in my phone/pc
Please reply here if you have experience of deleting preinstalled apps
sorry, english is my second languague
Good luck !

Hahahaha... all that trouble just to install a few unnecessary apps off of a ROOTED phone?! If you had searched, you'd have seen the numerous posts where we've posted instructions on uninstalling apps through Terminal. Literally 4 lines of code at most! Note that you can do this with any app you don't want. I have xROM, and one of the first things I do whenever I clean install to the latest version is replace ringtones and remove apps, including HTC Mail, Email, Amazon mp3, and Android Music. It takes me about 2 minutes to remove these apps.
Example for removing Amazon MP3:
su
mount -o rw,remount /system
rm -r /system/app/com.amazon-mp3.apk
mount -o rw,remount /data
rm -r /data/data/com.amazon.mp3
exit
exit

uansari1 said:
mount -o rw,remount /data
Click to expand...
Click to collapse
/data is never mounted read-only.

zelipukin said:
...
- Start emulator (don’t think it is necessary, but lets follow – emulator located in SDK folder\tools\emulator.exe in my case C:\SDK_15\tools\
CMD window pops up for a second and disappeared
...
Click to expand...
Click to collapse
That's not how you start the emulator, in the window that disappears is a message telling you to start with the proper parameters, which you'd see if starting from a command line. If the emulator actually was running, then all your adb commands would then fail because it wouldn't know what device you wanted to address, you'd have to use "adb -d" to tell it to use the real device rather than the emulator.

jashsu said:
/data is never mounted read-only.
Click to expand...
Click to collapse
Thanks for the info.. guess I've been doing an extra step, but this means I can do I through terminal even faster.

Easy way to remove unwanted preinstalled apps
Use Root Explorer to browse to /data/app_s and find the applications you don't want. Delete the APK and ODEX files and you are done.
Always remember to make a backup of your phone, before you start deleting.

ewaldtx said:
Use Root Explorer to browse to /data/app_s and find the applications you don't want. Delete the APK and ODEX files and you are done.
Always remember to make a backup of your phone, before you start deleting.
Click to expand...
Click to collapse
The app_s folder is only used for Hero ROMs because there isn't enough space in /system, so it's placed in /system/sd (the mount point of the ext partition) if you have an ext partition for A2SD.
For regular google source builds just go to /system/app.

there is an app called rootexplorer it has a button to remove syatem apps. real easy to use. http://www.cyrket.com/package/com.sp...e.rootexplorer

saprano614 said:
there is an app called rootexplorer it has a button to remove syatem apps. real easy to use. http://www.cyrket.com/package/com.sp...e.rootexplorer
Click to expand...
Click to collapse
and it works great

Sorry to kind of hijack this but cyrket.com always shows as a blank page.
anyone know why or how to fix that?

i think simply deleting the apk files and data folder will keep an entry in some kind of registry in android. if i just delete the apk files and data folder and run fix_permissions, it shows the same number of processes.

SUFBS
is a rooted file browser and it is, by far, the easiest way of uninstalling any stock apps.
Click one button to make the system folder re-writable (same thing with data folder, just a button), navigate to the apps directory and just delete. or you can search for the app and just delete it from the search window. Voila!

Ssantos6981 said:
is a rooted file browser and it is, by far, the easiest way of uninstalling any stock apps.
Click one button to make the system folder re-writable (same thing with data folder, just a button), navigate to the apps directory and just delete. or you can search for the app and just delete it from the search window. Voila!
Click to expand...
Click to collapse
are you talking about rootexplorer or what? elaborate a little..
i just bought and downloaded/installed rootexplorer simply to delete stock apps. upon opening it ask me to allow it. i say yes and it says my phone isn't rooted.
weird.. i just upgraded from cyanogen v4.1.999( or something around that) to the newest 4.2whatever. so how if my phone not rooted?!

blackinches said:
are you talking about rootexplorer or what? elaborate a little..
i just bought and downloaded/installed rootexplorer simply to delete stock apps. upon opening it ask me to allow it. i say yes and it says my phone isn't rooted.
weird.. i just upgraded from cyanogen v4.1.999( or something around that) to the newest 4.2whatever. so how if my phone not rooted?!
Click to expand...
Click to collapse
try it again lol. it should work
make sure your not on the stock adp recovery

Root explorer!!!

Hi,
i'm trying ro remove stock apps for quite a few days, and i'm getting desperate!
I have everything... titatium, terminal, root explorer, etc etc
with terminal I also receive "directory not empty", but with root explorer I can delete the apk's from /system/app ... I confirm after that they are not there, bus as soon as I reboot the phone they come back.
what can I do ?
I have HTC desire with stock android, rooted .. and also a couple of programs I instaled I don't really knwo what they do.. like rom manager, clockword recovery, etc
plz help!

Sleeepy2 said:
Sorry to kind of hijack this but cyrket.com always shows as a blank page.
anyone know why or how to fix that?
Click to expand...
Click to collapse
It is because the full url path is not correct. Hover cursor over link and look at lower left corner to view the url path...it has those .... in it and will not work. We need the full exact url path.

just use titanum backup,rt click on application it will show (remove),be sure u didn't updated any stock app e.g gmail update

Regarding using Root Explorer on stock G Tab updated to 1.2-4349...
Trying to remove some of the apps preloaded and using Root Explorer get a statement - my phone not rooted.
I want to get the apps off. What to do now? Thanks http://media.xda-developers.com/images/smilies/smile.gif

Thanks for this clear procedure !

An Alternative Super Noob Guide to Streamlined Overclocking and ADB

First off, a big thanks goes out to coolbho3000 and paulobrien for coming up with the overclock module and VISIONary, respectively. And also a big thanks to mcp2009 for first suggesting the use of GScript.
I put this in the other method thread, but I thought it might need it's own topic since a bunch of people found this helpful in the development forum. I think it may be a good guide for some people here. Why is this method nice? Because it streamlines the way the overclock works using VISIONary. I'm new to Android but I've been learning pretty fast, and I want to give back to the community that has helped me come along.
1. Obtain Root through VISIONary
The first thing you need to do is gain root on your phone. To do this, download and install VISIONary from Android Market. The first time you run it, make sure to allow it to run-on-boot from now on. Run it, and you'll have root. Easy as pie.
2. ADB Push to /data/local
Next, you'll need to adb push the vision_oc.ko file to the /data/local folder using my desktop computer. How do you adb push? Cyanogen Wiki has a good guide on how to get this going on your computer. A caveat with the G2 is you may run into driver issues. If this happens, download PdaNet onto your computer, and it will install all the drivers you need for adb. There is also another solution to the driver issues that was solved on this thread. I believe everyone should learn to use adb at some point or another, since it is an invaluable tool and opens up a world of possibilities, which is why I advocate it as the route of choice in this method.
Once you have adb installed, go download the vision_oc.ko file in the original thread. Make sure you put it into the folder on your computer that your command prompt is directed to at the time (most likely your Document and Settings folder). Enable USB debugging on your phone, connect it to your computer, open the command prompt and type:
Code:
adb push vision_oc.ko /data/local
This should copy the file to your /data/local folder on your phone. One more file you should adb push to the /data/local folder is a file you will name visionary.sh. Open up Notepad, and put in there:
Code:
su
insmod /data/local/vision_oc.ko
Make sure you name it visionary.sh, and push it the same way you did the other file using the following code in the command prompt:
Code:
adb push visionary.sh /data/local
There is a lot more to do with adb, so I encourage you to learn it, but for now, we are done with it!
3. Set Scripts up in GScript Lite
Download and install GScript Lite from the Android Market. I then set up 5 scripts to control the overclock:
1. 1017.6 MHz Default
Code:
rmmod vision_oc.ko
insmod /data/local/vision_oc.ko
2. 806.4 MHz Factory Setting
Code:
rmmod vision_oc.ko
insmod /data/local/vision_oc.ko pll2_l_val=42
3. 1209.6 MHz Overclock
Code:
rmmod vision_oc.ko
insmod /data/local/vision_oc.ko pll2_l_val=63
4. 1305.6 MHz Overclock
Code:
rmmod vision_oc.ko
insmod /data/local/vision_oc.ko pll2_l_val=68
5. 1420.8 MHz Overclock
Code:
rmmod vision_oc.ko
insmod /data/local/vision_oc.ko pll2_l_val=74
Basically with these scripts, I can control everything. You can always change the values to make it more suitable to your phone, but I think these values give you a nice range.
4. SetCPU
I highly recommend you buy SetCPU from the Android Market. It will help you have complete control over your overclock and power settings. So go do it!
At this point, you are done! I suggest you reboot the phone so you can see all of this in action! So for example, when I reboot my phone, and everything gets wiped, VISIONary runs, my phone gets rooted, and the visionary.sh script runs automatically to give me the 1017.6 MHz Default script to start the overclock, meaning, you are overclocked already at 1017.6 MHz at boot! The reason I used the default 1017.6 MHz in my visionary.sh script (the vision_oc.ko file is set to overclock your phone at that speed by default without adjusting the value), is because it is definitely stable enough for every G2 to handle, so people won't be locking themselves out because of setting an overclock too high at boot. From there, I can just simply click any other overclock script in GScript to change the CPU to my desired speed at the time.
Hopefully this helps some people out!

Awesome
Sent from my T-Mobile G2 using XDA App

i'm definitely a noob and still climbing the learning ladder - just wanted to say thanks, especially for what is probably a simple step for a lot of folks, but installing adb was a headache - that tutorial link helped a lot

larryccf said:
i'm definitely a noob and still climbing the learning ladder - just wanted to say thanks, especially for what is probably a simple step for a lot of folks, but installing adb was a headache - that tutorial link helped a lot
Click to expand...
Click to collapse
No problem. I'm still learning and am no where near an expert, but I thought I would share the info I have uncovered over the last few weeks. It has been a ball. =)

How can I make the default overclock 1209mhz instead of 1ghz?
Your instructions specify that you have 1ghz as default.
edit- ok so with no values it equals 1ghz? But if I add the values "pll2_l_val=63" to the .sh script I can redefine the default speed.

KShatzkes said:
1. 1017.6 MHz Default
rmmod vision_oc.ko
insmod /data/local/vision_oc.ko
2. 806.4 MHz Factory Setting
rmmod vision_oc.ko
insmod /data/local/vision_oc.ko pll2_l_val=42
3. 1209.6 MHz Overclock
rmmod vision_oc.ko
insmod /data/local/vision_oc.ko pll2_l_val=63
4. 1305.6 MHz Overclock
rmmod vision_oc.ko
insmod /data/local/vision_oc.ko pll2_l_val=68
5. 1401.6 MHz Overclock
rmmod vision_oc.ko
insmod /data/local/vision_oc.ko pll2_l_val=73
Click to expand...
Click to collapse
How does the visionary.sh script no which gscript to run? It's not defined in the code. Your default gscript (for 1ghz) doesn't even define the values. Basically I just wanna know, how with no values it defaults to 1ghz.

sinistersai4d4d said:
How does the visionary.sh script no which gscript to run? It's not defined in the code. Your default gscript (for 1ghz) doesn't even define the values.
Click to expand...
Click to collapse
The module, vision_oc.ko, runs at 1017.6 MHz by default

^Oh. Ok, thought that was kinda odd.

Thanks for the work with this. When I go to push the second file:
Make sure you name it visionary.sh, and push it the same way you did the other file using the following code in the command prompt:
adb push visionary.sh /data/local
I get back:
cannot stat 'visionary.sh': No such file or directory
Any idea what I am doing wrong?

It worked when I added .txt to the end so:
adb push visionary.sh.txt /data/local
Is that correct? I'm also at 806 mhz via SetCPU and can't figure how to launch Visionary at boot. Help please...

make sure you have two files in data/local that you've added. the .oc.ko and the .sh file.
Make sure to open settings/applications/VisionARY and clear any defaults or presents. Then next time you run it try RE enabling boot on start (that worked for me)

ok my g2 is already overclock to 1.42ghz, im trying to learn adb. my laptop recognize my device when i type "adb devices" but the problem is when i type "adb shell" i get a "$" sign instead of " # ". Anybody can help me with this? ive searched the adb for dummies it didnt have the info that i needed =(
THanks in advance!

Type su if your using connectbot form the phone.
G1rome said:
ok my g2 is already overclock to 1.42ghz, im trying to learn adb. my laptop recognize my device when i type "adb devices" but the problem is when i type "adb shell" i get a "$" sign instead of " # ". Anybody can help me with this? ive searched the adb for dummies it didnt have the info that i needed =(
THanks in advance!
Click to expand...
Click to collapse

aka DaBigKahuna said:
It worked when I added .txt to the end so:
adb push visionary.sh.txt /data/local
Is that correct? I'm also at 806 mhz via SetCPU and can't figure how to launch Visionary at boot. Help please...
Click to expand...
Click to collapse
It needs to be a .sh file. Basically what happens is when VISIONary runs on boot, it runs visionary.sh as well, so any script in that file runs.
I also explain why I put the default as 1GHz over clock. It's for stability issues. Every G2 is different, and some people can lock themselves out if they have an over clock too high for them on boot. You can change things if you want, but I wouldn't suggest it honestly.

aka DaBigKahuna said:
Type su if your using connectbot form the phone.
Click to expand...
Click to collapse
I connected my phone to my laptop and using cmd, so when I type "adb shell" I get $ instead of # from cmd.
Sent from my T-Mobile G2 using XDA App

G1rome said:
I connected my phone to my laptop and using cmd, so when I type "adb shell" I get $ instead of # from cmd.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Type su (acronym for Super User) and you will get a # prompt. In *nix a $ is a regular user and a # is a super user. Think of it as a normal user and an administrator in windows.
So you would go:
adb shell
Then you get a $ prompt
su
Now you should have a # prompt.

So im curious if this would work on other android devices or if its just the g2? Worked like a charm on my g2 but im curious if i could run this on a vibrant running eugenes jpm froyowith favorable results.
sent from my froyo-ed vibrant.

Detailed step by step video
Easy way
xww.youtube.com/watch?v=wToXNT3zIqY
put a w in front of the link, can't post url yet.

harriz said:
Detailed step by step video
Easy way
xww.youtube.com/watch?v=wToXNT3zIqY
put a w in front of the link, can't post url yet.
Click to expand...
Click to collapse
That video doesn't really explain THIS guide. It uses the bare minimum to get things running, while this guide explains how to streamline the whole process as best possible with temp root on boot-up.

jeremyritzmann said:
So im curious if this would work on other android devices or if its just the g2? Worked like a charm on my g2 but im curious if i could run this on a vibrant running eugenes jpm froyowith favorable results.
sent from my froyo-ed vibrant.
Click to expand...
Click to collapse
That I am not sure. Maybe one of the developers can answer you there.
Doesn't the Vibrant have its own OC method anyways?

cant access shell...

I installed vodoo lagfix (froyo 2.2) preview6 (or what is newest as today) Before that I had replaced sh with bash, sh was link in same directory binary bash. After vodoo lagfix i encountered reboots... Then i saw that shell is inacessible and now i need to copy bash back to /system/bin (bash is zero bytes) to acess shell and fix things Looks quite simple but i simply cant do it root explorer isint working android mate either any other suggestions? Maybe i can somehow can give root permisions to some simple file explorer? Now my phone restarts as soon as i unplug it and it goes into sleep mode...
Even before that I couldnt simply copy (why there is no cp command?) i had to cat file > file
BTW voodoo really works phone is fast
I hope i posted in right thread thanks for answers.

Had a similar problem: I have JG1, and clockwork replaces my shell and it then becomes unusable.
If you still have your old shell bianry lying around somewhere, or want to "install" your bash again, you can do it by creating an update.zip file.
I've attached a template for this - copy your desired shell binary to system/bin/sh, name it update.zip, place on SD card, go into recovery mode and hit "apply: update.zip"
IMPORTANT: the attached template is untested - you can, however, use the file I actually use, and simply adjust it for your needs (replace its shell binary, and look at the update script... nevermind the "root" text in it... I simply used the rooting update.zip as a base for it...)
Here's what I need when I play around with clockwork: http://db.tt/xGDcT1y
As for the template, see the post's attachments.
I hope this helps.

Cant apply update zip, because there is no such option only reinstall apps and so on... Have 2e recovery. Looks like i will need to use heidmall or similar app.

[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

[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.