Database Develop

Google Maps with Nav: For NoObs! For Cyanogen ROM's (works!)

First thank you Followinginsanity for breaking the code!
Credit for this break down goes to Paul22000 for his write up. I just added all the links and my input which worked on 5 of my buddy's phones.
Please let me know if I am stepping on anyone's toes and I will remove this.
go to this page ( http://forum.xda-developers.com/showthread.php?t=582656&page=8 ) and download build.props.zip then open and place on the root of the sdcard.
then go to: http://forum.xda-developers.com/showthread.php?t=583627 and download the link on the first page. open it and go to the apps folder in the zip and copy the Maps.apk and place on the root of the sdcard.
- Make sure before you start to make a nandroid backup.
A) Place 3 files on sdcard (build.prop, build.trout.prop, Maps.apk)
B) Terminal (on phone):
su
ash
mount -o remount,rw /system
cp /system/build.prop /sdcard/build.prop.backup
cp /system/build.trout.prop /sdcard/build.trout.prop.backup
cp /sdcard/build.prop /system
cp /sdcard/build.trout.prop /system
cd /system/app
rm *Maps*
rm *maps* ( an error is ok go on, just need to make sure all are deleted. So both Maps and maps done.)
cd /system/sd/app
rm *maps*
rm *Maps* ( an error is ok go on, just need to make sure all are deleted. So both Maps and maps done.)
cd /system/sd/dalvik-cache
rm *maps*
rm *Maps* ( an error is ok go on, just need to make sure all are deleted. So both Maps and maps done.)
reboot
C) Terminal:
su
mount -o remount,rw /system
install /sdcard/Maps.apk /system/app/
D) Open "Maps" on your phone
Directions -> Put end point -> Go -> "Navigate" under "Show on Map" -> Install voice etc
(Must have GPS on and data connection active)
- Not there? Go to the market and download Google Voice. install... open and then exit. go back to Maps and try - Directions -> Put end point -> Go -> "Navigate" under "Show on Map" Agian.
(If "Navigate" doesn't show up, something went wrong.)
E) To get other apps back to normal (if stuff broke):
su
ash
mount -o remount,rw /system
cp /sdcard/build.prop.backup /system/build.prop
cp /sdcard/build.trout.prop.backup /system/build.trout.prop
reboot

this is much faster.. its a update.zip and it supports the builds so facebook and handcent work just fine..
http://forum.xda-developers.com/showthread.php?t=583684

Rock on. Just wanted to put something up for all the new people who tried all the other's and couldn't get them to work.

Jamison904 said:
Rock on. Just wanted to put something up for all the new people who tried all the other's and couldn't get them to work.
Click to expand...
Click to collapse
lol yuh iw as there and damn i was there wit so many issues lol..but im glad people are gettin helped and thank you as well for takin ya time out to write all that **** lol.. i woulda just been like egh fucc it to lazy lol..thanks

navigate dissappeared after upgrading to cyan 4.2.5

You could either try reinstalling it or some say you can uninstall Google Voice and reinstall it.
I upgraded from 4.2.4 to 4.2.5 just fine and kept it, but I'd give it a reinstall. Couldn't hurt or try the google voice trick.

nice! good to go after first install, no problems yet!

Works so nice. You devs are geniuses. Love it. Thx so much.

no prob yet but on my phone it says my firmware version is 2.0 and my mod version is cyanogenmod 4.2.3.1 build number esd20, is this right? prior to this i was 1.6 running cyanogenmod 4.2.5
edit**
just did this and it changed everything back to normal
E) To get other apps back to normal (if stuff broke):
su
ash
mount -o remount,rw /system
cp /sdcard/build.prop.backup /system/build.prop
cp /sdcard/build.trout.prop.backup /system/build.trout.prop
reboot

my phone says 1.6 and cyan 4.2.4 but i have all the features of 4.2.5 and yes i have google voice installed

jonnunez said:
no prob yet but on my phone it says my firmware version is 2.0 and my mod version is cyanogenmod 4.2.3.1 build number esd20, is this right? prior to this i was 1.6 running cyanogenmod 4.2.5
edit**
just did this and it changed everything back to normal
E) To get other apps back to normal (if stuff broke):
su
ash
mount -o remount,rw /system
cp /sdcard/build.prop.backup /system/build.prop
cp /sdcard/build.trout.prop.backup /system/build.trout.prop
reboot
Click to expand...
Click to collapse
the problem with this is when you reinstall the backup's you will lose Google Nav. But your old apps work fine again. There is something in the build.prop and build.trout.prop that Google Nav looks for. Once you replace the new ones with your backup's, your back to square one. Might not do it right away but after a few minutes Nav is gone.

jj71787 said:
navigate dissappeared after upgrading to cyan 4.2.5
Click to expand...
Click to collapse
I have to redo this everytime I upgrade. It messes with the build.prop as I mentioned above. Until Cayogen puts out 2.0, we will have to keep messing with Nav to keep it when updating.

L
Jamison904 said:
the problem with this is when you reinstall the backup's you will lose Google Nav. But your old apps work fine again. There is something in the build.prop and build.trout.prop that Google Nav looks for. Once you replace the new ones with your backup's, your back to square one. Might not do it right away but after a few minutes Nav is gone.
Click to expand...
Click to collapse
Ahh your 100% right, woke up this morning and navigate was gone!

jonnunez said:
L
Ahh your 100% right, woke up this morning and navigate was gone!
Click to expand...
Click to collapse
oooooooooh..dude... i just follow you did the part E...

I get file exist at these two steps
cp /sdcard/build.prop /sytem
cp /sdcard/build.trout.prop /system
And I get cannot delete read-only at
rm *Maps*
What am I missing?

jonnunez said:
L
Ahh your 100% right, woke up this morning and navigate was gone!
Click to expand...
Click to collapse
hey man . i find a way to fix our mistake..
you can simply edit one line in your build.trout.prop file found in the system directory on your G1.
The edit is simply changing the ro.build.fingerprint line to:
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
then it works good..facebook works .. handcent works .. and look into about phone..back to the normal..1.6 tmo G1 drc83

I ended up finding this blog. I did the manual install and then installed Google Voice and everything is working perfectly for me.

FireBrush said:
I get file exist at these two steps
cp /sdcard/build.prop /sytem
cp /sdcard/build.trout.prop /system
And I get cannot delete read-only at
rm *Maps*
What am I missing?
Click to expand...
Click to collapse
You must of forgot to type "su" then press enter when you first started the script.

everyone listen up!
follow the instruction..finally you got map2.0,but look into your setting-about phone..it shows 2.0 not 1.6 tmo g1..i think thats why we cant use facebook and handcent..
just put these 2 build.trout.prop and build.prop in your phone system instead
it shoud works ..everything back normal..and nav works just fine

Can anyone comment if this works in the UK - I have tried a number of ways and none seem to work,
I am using Cyanogens latest Rom and followed the instructions to the letter...
Just get the show on Map options nothing more, nothing less

Apps missing and won't let me re-install

something weird happened on my phone when I installed the SuperD 1.9.3 rom. I've never had this problem before, so see if you can help me. I installed Chompsms and Acontacts amongst a variety of other apps. Well, I was texting earlier, when my phone froze. No biggy, I popped the battery out, placed it back in, and turned it on. Well I got the green boxes in place of the the logos for Chomp and Acontacts. I clicked on them and it said that the apps weren't installed? um, ok. I have aps2sd with ext3, so I figure something must have corrupted the file, no biggy, I'll just redownload it. So I go to the market, and it says the program is installed. I click on the program to try to reinstall, and the bottom where it says "open, uninstall" are greyed out. So the app isn't installed, but it is, so I can't uninstall and re-install. Anyone, help please? I really use these 2 apps!

Delete the apk's from /system/sd/

It also sounds like your marketdb file is still there too. I've had this problem with Backup for root users. It'll import the marketdb but sometimes it won't import the APK's. So that leaves you with no apps and the market seeing that you already have it. I'm trying to find where the program is pulling that file, and i'll let you know. If anyone else knows where it's at feel free to jump in.

nolimit78 said:
If anyone else knows where it's at feel free to jump in.
Click to expand...
Click to collapse
/data/data/ I think.

evilkorn said:
/data/data/ I think.
Click to expand...
Click to collapse
That's what I was thinking but I didn't see it there...
While Im still looking for that file, you could also do the following:
Code:
Use switchrom and save your rom
flash a new rom
download the apks that are giving you problems (if its not too many)
use linda to save the apks to your SD card
switchrom back to the old rom
download and use linda to install the apks you saved.
It's not pretty but it'll get the job done.

Had a little time to look at the phone, did you try to delete the folder in /data/data/com.android.vending/?

Goto terminal emulator.
Type - mount -o remount,rw /dev/block/mtdblock3 /system (enter)
Type - rm /data/data/com.android.vending/databases/* (enter)
Type - reboot (enter)
Words in bracket are instructions and not to be typed.

shadowch31 said:
Goto terminal emulator.
Type - mount -o remount,rw /dev/block/mtdblock3 /system (enter)
Type - rm /data/data/com.android.vending/databases/* (enter)
Type - reboot (enter)
Words in bracket are instructions and not to be typed.
Click to expand...
Click to collapse
yeah I found that it was in the vending/databases folder, I just hadn't had time to post until now. Good job!

i had the same problem and it worked...at first the terminal emulator went like 'are you root' and im like whaaat...i have cynogen 4.2.14.1...so had to type su before the 3 lines of codes...it worked

Issue with market and apps

Hey guys...
I bought a new mini-SD card for my rooted G1. I have the latest CM on it. So now i decided to install my nandroid-backup.. but now i have a problem with downloading all of my old apps from android market. In the market it says that all of my apps are installed, though they aren't. In the app-list of my phone my old apps are still shown and when i click on them it says: This App is not installed on your phone (sorry i'm using a german g1, so i have to translate the messages). So as you can see, my problem is that I can't download any of my old apps from market and i can't delete those entries or like the "rest of the app thats still on my phone". Any ideas ? I don't want to factory reset my phone... cause i love the way it is now (except this issue haha)

Try this. There is a similar issue there the apps don't exist but the Market DB still does, which gives you the problem of not being able to install but cannot uninstall it, because it doesn't exist. Below should help you out.
Code:
Type - mount -o remount,rw /dev/block/mtdblock3 /system (enter)
Type - rm /data/data/com.android.vending/databases/* (enter)
Type - reboot (enter)
Words in bracket are instructions and not to be typed.

[Q] Help upgrading Market

I recently rooted my Nook color with Auto Nooter 2.12.25. It gave me the Google Market but it is the old one and it only displays 10 apps in portrait mode and some of the buttons have problems working. I read in a thread that the newer market fixes that and I downloaded an apk named com.android.vending02.apk but when I try to install it, the app manager doesn't have an install tab. I downloaded a 3rd party install manager and when I try to install it says that 'There is a problem parsing this package'.
I have read that people have installed the updated market but no one gives an explanation how. Does anyone know how do this? Thanks for your help.

Found solution
I found a solution.

Dont just post you found a solution, that helps no one. post what the solution was or atleast a link to the fix.

Good Call
I installed the APK at the top of this thread http://forum.xda-developers.com/showthread.php?t=872621 and then reset my NC and the new Market worked. Apparently, after reading through the thread, this method doesn't work for everyone. There are further instructions that may be of some use.

Now my market isn't working. After trying to install this and switch back both times when I open market it just disappears.

buffnutz1 said:
Now my market isn't working. After trying to install this and switch back both times when I open market it just disappears.
Click to expand...
Click to collapse
I had the same problem on my 1.1.0 NC rooted with Decad3nce's V1.1.0_r2 [01/29/2011] method (there's a huge long thread on that in the Development forum). I was dreading the possibility of having to wipe the machine and start over, but I just re-flashed the zip file, and everything's working fine again. Unfortunately, I'm still stuck with the old Market.

If you're feeling like you can handle cmd-line stuff, try this method out.
First download the attached newmarket.apk
open/connect adb
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb pull /system/app/Vending.apk (notice the cap V, also this will get put into your platform-tools folder. Back it up!)
adb push pathtonewmarket.apk /system/app/Vending.apk
adb reboot
Once you've rebooted then go into settings->applications->manage->all
Find the market and clear the cache
Then find google services framework and clear the data then force quit
reboot once more
After that the new market should work just fine.

Thanks Woot! does this work on Froyo 0.6.7 too?
woot1524 said:
If you're feeling like you can handle cmd-line stuff, try this method out.
First download the attached newmarket.apk
open/connect adb
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb pull /system/app/Vending.apk (notice the cap V, also this will get put into your platform-tools folder. Back it up!)
adb push pathtonewmarket.apk /system/app/Vending.apk
adb reboot
Once you've rebooted then go into settings->applications->manage->all
Find the market and clear the cache
Then find google services framework and clear the data then force quit
reboot once more
After that the new market should work just fine.
Click to expand...
Click to collapse

necroscopev said:
Thanks Woot! does this work on Froyo 0.6.7 too?
Click to expand...
Click to collapse
I can confim that it does, I used it my self to get the new market installed.
If you're booting off of an SD card and want to install the new market there. All you need to do is change one line.
FROM: mount -o remount,rw /dev/block/mmcblk0p5 /system (eMMC system partition)
TO: mount -o remount,rw /dev/block/mmcblk1p2 /system (SD-card system partition)

[Q] Droid3 system corrupt and unable to fix

Okay, so this is a doozy. I recently got a Droid3 to replace my original Droid. I've had it for less than 3 months. Its been rooted using Pete's One Click Root for this entire time without any issues.
Last week the following symptoms manifested:
1) Most applications, including system applications, force close constantly.
2) I'm usually unable to run any applications, including the Market.
3) What applications are having issues is not consistent.
4) The phone will reboot itself randomly, sometimes constantly.
5) Sometimes after a reboot it gives me no service and has the "Touch Android to begin" screen again. The phone is completely unusable when it does this, and the only fix is to pull the battery and then its back to its previous state.
5) Any changes made to the phone do not survive a reboot.
This last one is the real kicker. I can go through, uninstall every application I've ever downloaded but if you restart the phone or it restarts itself they will all return. This goes for everything on my Internal Storage. The SDCard seems unaffected...
I tried the SBF trick here from rootzwiki. (can't link since I'm new)
This did not work. How it failed might be important:
1) The primary method (psouza4's) acts like its successful but doesn't actually do anything.
2) RSDLite method will fail in step 3 (mbmloader.bin) every time, no matter what fastboot file I try to use.
3) After doing RSDLite I had the "flashboot flash failed" error and the phone was unusable. I then tried psouza4's method again and my phone has reverted to the same broken state it was in when I started.
So I'm not at all sure what I can do here. Since the bootloader isn't cracked yet I have no means to load another ROM. The only method I can find for Droid3 is through a Marketplace app that, on the rare instances I can install it, force closes immediately!
Any advice or ideas at all would be nice.
As for what started this, only two things happened out of the normal phone usage:
1) My girlfriend tried to text me a picture for the first time (of some chairs she wanted to buy for those curious/suggestive ) which never got to me initially but when it finally did after the 4th attempt I was never able to download the image.
2) I put a PDF file on the Internal Storage. Its one I've had for years and its just some manual I needed mobile and I don't have a laptop. Confirmed its malware free as far as any software can tell.
Working theory is I unplugged my phone from the USB too quickly after uploading the file but I don't know for sure. Nothing else was done unless Verizon had a OTA update that would break a rooted phone (guessing not since no one else seems to have this issue anywhere).
Again, any help someone can provide would be excellent. I'm going to have to load up my broken Droid in the mean time. Keyboard doesn't work and the touchscreen is failing but it can take calls more reliably than my Droid3 currently!

Cowmonaut said:
Okay, so this is a doozy. I recently got a Droid3 to replace my original Droid. I've had it for less than 3 months. Its been rooted using Pete's One Click Root for this entire time without any issues.
Last week the following symptoms manifested:
1) Most applications, including system applications, force close constantly.
2) I'm usually unable to run any applications, including the Market.
3) What applications are having issues is not consistent.
4) The phone will reboot itself randomly, sometimes constantly.
5) Sometimes after a reboot it gives me no service and has the "Touch Android to begin" screen again. The phone is completely unusable when it does this, and the only fix is to pull the battery and then its back to its previous state.
5) Any changes made to the phone do not survive a reboot.
This last one is the real kicker. I can go through, uninstall every application I've ever downloaded but if you restart the phone or it restarts itself they will all return. This goes for everything on my Internal Storage. The SDCard seems unaffected...
I tried the SBF trick here from rootzwiki. (can't link since I'm new)
This did not work. How it failed might be important:
1) The primary method (psouza4's) acts like its successful but doesn't actually do anything.
2) RSDLite method will fail in step 3 (mbmloader.bin) every time, no matter what fastboot file I try to use.
3) After doing RSDLite I had the "flashboot flash failed" error and the phone was unusable. I then tried psouza4's method again and my phone has reverted to the same broken state it was in when I started.
So I'm not at all sure what I can do here. Since the bootloader isn't cracked yet I have no means to load another ROM. The only method I can find for Droid3 is through a Marketplace app that, on the rare instances I can install it, force closes immediately!
Any advice or ideas at all would be nice.
As for what started this, only two things happened out of the normal phone usage:
1) My girlfriend tried to text me a picture for the first time (of some chairs she wanted to buy for those curious/suggestive ) which never got to me initially but when it finally did after the 4th attempt I was never able to download the image.
2) I put a PDF file on the Internal Storage. Its one I've had for years and its just some manual I needed mobile and I don't have a laptop. Confirmed its malware free as far as any software can tell.
Working theory is I unplugged my phone from the USB too quickly after uploading the file but I don't know for sure. Nothing else was done unless Verizon had a OTA update that would break a rooted phone (guessing not since no one else seems to have this issue anywhere).
Again, any help someone can provide would be excellent. I'm going to have to load up my broken Droid in the mean time. Keyboard doesn't work and the touchscreen is failing but it can take calls more reliably than my Droid3 currently!
Click to expand...
Click to collapse
I can say a couple words to describe my reaction.. OH ****. Your phone seems to have too many problems to be software related. Try to flash back to stock 5.6.890 and get a new phone.
Sent from my DROID3 using XDA App

Hmm, I guess for the mean time I'll just have to keep trying to get the Marketplace ROM Manager to install and launch. Should be a way to install straight to the SDCard that doesn't have problems.
Thinking it over, my Internal Storage may just have a bad sector... Yeesh.

Have you tried formatting /system in mounts and storage in CWM? Then reinstalling a fresh rom on top?
Sent from my DROID3 using xda premium

Negative. I didn't have CWM installed (stock ROM just rooted for certain apps) and apps are usually crashing now.
I'll give that a shot though. Sometimes I can use an app so maybe if I'm persistent...

and to verify, you are using the verizon droid 3 xt862? Are you on 5.5.959 or 5.6.890 (or possibly 5.7.894)?

Yea can't get any new apps to run. Interestingly, the camera app seems to crash the OS at the moment.
I think I'm going to have to try to RMA...

MrJudylicious said:
and to verify, you are using the verizon droid 3 xt862? Are you on 5.5.959 or 5.6.890 (or possibly 5.7.894)?
Click to expand...
Click to collapse
Its running 5.6.890. Unless I'm mistaken its the xt862. I've only had it since September.

well as long as root isnt showing and the /system hasnt been changed from stock rom, it should work. i do find it bad that rsd didnt work. i wonder if you were trying to flash the .959 sbf on your .890 system? I would def try again to sbf and wipe data/cache through stock recovery after that using volume buttons (android!)

Well, that's kind of the problem. Changes don't survive a reboot so i haven't been able to unroot the phone. I double checked and the file was the .890 flashboot. Wiping data/cache literally does nothing.
Is there a way to format this offline, from a PC? Going to try some more Google searches...

wiping data/cache should erase all of your saved data and force you to *228. Make sure USB debugging is on, set usb to Charge Only, try petes motorola tools to unroot but using RSD 5.5 fastboot .890 found http://forum.xda-developers.com/showthread.php?t=1255198

MrJudylicious said:
wiping data/cache should erase all of your saved data and force you to *228. Make sure USB debugging is on, set usb to Charge Only, try petes motorola tools to unroot but using RSD 5.5 fastboot .890 found http://forum.xda-developers.com/showthread.php?t=1255198
Click to expand...
Click to collapse
1) How do you unroot with Pete's motorola tools? Is it a different version than the one click root? Cause that's how I rooted my phone in the first place but it doesn't seem to have an option to unroot...
2) The link for the flashboot file gives a 404 error. The attached .RAR only has the .XML file.
Any place else I can get that version?

just enter stock recovery by holding down the x key on the keyboard when you boot up and wipe data
Edit: srry didnt read the full post

jellydroid13 said:
just enter stock recovery by holding down the x key on the keyboard when you boot up and wipe data
Click to expand...
Click to collapse
If you read the original post, that doesn't work.

Okay so I had an outdated version of Pete's tools which is why I didn't see the unroot option. Mine is the older one that was a batch file, not a application.
Got that sorted out and it still doesn't work. Seems I may have some permissions issues:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
[email protected]_solana:/$ su
exit
exit
exit
Permission denied
sh[email protected]_solana:/$ /system/xbin/su
Permission denied
[email protected]_solana:/$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]_solana:/$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
[email protected]_solana:/$ exit
(success)
That's part of the ADB log. There are a lot of other permission denied messages, which is a little comforting. The only thing I could think of that happened is permissions didn't get set right when Internal Storage was unmounted from my PC.
Since I can use ADB to access the shell, how can I format /system on the droid3? I can't seem to find the correct root name to use.

Cowmonaut said:
Okay so I had an outdated version of Pete's tools which is why I didn't see the unroot option. Mine is the older one that was a batch file, not a application.
Got that sorted out and it still doesn't work. Seems I may have some permissions issues:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
[email protected]_solana:/$ su
exit
exit
exit
Permission denied
[email protected]_solana:/$ /system/xbin/su
Permission denied
[email protected]_solana:/$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]_solana:/$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
[email protected]_solana:/$ exit
(success)
That's part of the ADB log. There are a lot of other permission denied messages, which is a little comforting. The only thing I could think of that happened is permissions didn't get set right when Internal Storage was unmounted from my PC.
Since I can use ADB to access the shell, how can I format /system on the droid3? I can't seem to find the correct root name to use.
Click to expand...
Click to collapse
Have you tried to root manually? Here are the original instructions vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/
[edit] I guess I miss read that you are trying to unroot.

try http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/ but you cant go from .890 back to .959! no idea about mounting, sorry.

MrJudylicious said:
try http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/ but you cant go from .890 back to .959! no idea about mounting, sorry.
Click to expand...
Click to collapse
That's the reference to Rootzwiki I made in the original post, doesn't work sorry.
Using ADB I mounted /system as rw and tried to manually remove certain apps. Once I re-mounted they were there again. So something is preventing me from making real changes to the Internal Storage.

Cowmonaut said:
That's the reference to Rootzwiki I made in the original post, doesn't work sorry.
Using ADB I mounted /system as rw and tried to manually remove certain apps. Once I re-mounted they were there again. So something is preventing me from making real changes to the Internal Storage.
Click to expand...
Click to collapse
You don't have superuser permissions.. In the ADB shell your command line should start with a # indicating superuser permissions.. you have a $

ChaoticWeaponry said:
You don't have superuser permissions.. In the ADB shell your command line should start with a # indicating superuser permissions.. you have a $
Click to expand...
Click to collapse
Where do you get that idea?
When I do this manually:
1) I'm running the command prompt as Administrator
2)I'm launching into adb using the command "adb shell".
3) First thing I do is type in "su"
4) second thing I do is approve "unknown" in the superuser app on account of it never remembering I already did that.
5) I use the command "mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system"
6) I use the "ls" command on /system/app and find an .apk to uninstall (not all my apps seem to be installed in this location either...)
7) I use the "pm list packages" command to find the rest of the files for that .apk
8) I use "rm <filename>.apk" followed by "pm uninstall <whatever that developer chose to name things>" command to fully uninstall.
I should note on my phone at this point it disappear from the application list.
9) I use the command "mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system"
10) I use the "ls" command on /system/app to confirm and voila, the apk file is back!
The app doesn't show up in my app manager until I reboot the phone. Changes to /system and /data are not persisting and I have no idea why.
I can't seem to unmount them either so I can't format via ADB...