Database Develop

[QUESTION] *.apk Gets overwritten on Reboot

For some reason, on the G1 with AOSP1.6_r1.2 & expansion, When i write the new maps.apk (3.2) From Here, over the origonal GoogleMaps.apk, It installs Fine. And loads fine, But Once Android is rebooted, the old file comes back... Reminds me of microsoft's shadow copy..... Anybody have a clue on how to stop it or force a particular file????

are you replacing the file in system/app? since that is where most roms store maps?

david1171 said:
are you replacing the file in system/app? since that is where most roms store maps?
Click to expand...
Click to collapse
You are correct.. thats where my GoogleMaps.apk is.

if you are replacing that file, then you could try to remove it, then install maps like a normal app onto the data partition.

david1171 said:
if you are replacing that file, then you could try to remove it, then install maps like a normal app onto the data partition.
Click to expand...
Click to collapse
Im in the middle of trying that right now.... It installed again without problems, now just waiting for the reboot to test if it got overwritten.
EDIT - Still no luck.... Just keeps getting Overwritten..... Can i change the Name of the new Google Maps so it has a new icon???

Any ideas anyone? Is this in the Wrong Forum??????

did you rm the file from /system/app/ and install it like a normal app? did you copy the .apk file from your sdcard to its location in /system/app/?
do you need commands on how to do this?

I deleted system/app/GoogleMaps.apk , and watched it disappear from the app drawer. then Moved the new GoogleMaps.apk into data/app/ . Installed it and ran it no problem... can exit and even go back into 3.2 no problem. but as soon as i reboot,the original GoogleMaps.apk is back in system/app/ ..... so im clueless.

I just installed successfully by copying the file to /system/app/Maps.apk
... not GoogleMaps.apk

Technochris1 said:
I deleted system/app/GoogleMaps.apk , and watched it disappear from the app drawer. then Moved the new GoogleMaps.apk into data/app/ . Installed it and ran it no problem... can exit and even go back into 3.2 no problem. but as soon as i reboot,the original GoogleMaps.apk is back in system/app/ ..... so im clueless.
Click to expand...
Click to collapse
how are you deleting it?
do that in the recovery console and see if that works
Code:
mount system
rm /system/app/GoogleMaps.apk
reboot

did what you said, after reboot the old googlemaps.apk is still there......

ls /system/app
remove maps.apk

david1171 said:
ls /system/app
remove maps.apk
Click to expand...
Click to collapse
in recovery or terminal?

Technochris1 said:
in recovery or terminal?
Click to expand...
Click to collapse
in terminal
Code:
su
ls /system/app/
(will give you a long list of .apk files)
(find the correct name for maps.apk)
reboot recovery
then in the recovery console
Code:
mount system
rm /system/app/-insert appname form above-.apk
reboot

I just did the above and as soon as you reboot again the old google maps is back!
Perhaps you could copy the new maps over while in recovery after deleting the old one?
The Maps apk file is named "GoogleMaps.apk" btw.
Phil

Technochris1 said:
For some reason, on the G1 with AOSP1.6_r1.2 & expansion, When i write the new maps.apk (3.2) From Here, over the origonal GoogleMaps.apk, It installs Fine. And loads fine, But Once Android is rebooted, the old file comes back... Reminds me of microsoft's shadow copy..... Anybody have a clue on how to stop it or force a particular file????
Click to expand...
Click to collapse
I see you are running Enomther's ROM. I was having the same problem - it turns out that Enomther's ROM had an easy fix all along. Run expsetup in terminal and choose Option 15 - you can delete Google Maps right there (I took advantage of deleting a few other apps that I don't use at the same time).
Then just reboot - place your new GoogleMaps.apk in the /system/app folder and you are golden.

Thanks dude. Thats the solution to my question....

I posted in the other thread...It is in the following folder
/system/sd/expstick/vsapps/GoogleMaps.apk
I am running the new app and am on Enoms latest AOSP 1.6.

Great! That worked a treat. Got it working just fine.
Phil

[Q] Root Explorere not working?

Ok so I'm rooted with Nooter 3 and have 1.1ghz kernel running and loving my $199 tablet. Only problem so far is getting Root Explorer to work right. I want to install my Swift Keyboard but when I try to change /System/App to R/W it doesn't change. I can change the root folder but not /System or lower. What am I doing wrong?
Thanks for any help,
Don
EVO 4G and Nook Color w/1.1 and OC

Get super explorer, its free and it will mount r/w. I have the same problem with root explorer.

evopanop said:
Ok so I'm rooted with Nooter 3 and have 1.1ghz kernel running and loving my $199 tablet. Only problem so far is getting Root Explorer to work right. I want to install my Swift Keyboard but when I try to change /System/App to R/W it doesn't change. I can change the root folder but not /System or lower. What am I doing wrong?
Thanks for any help,
Don
EVO 4G and Nook Color w/1.1 and OC
Click to expand...
Click to collapse
That's strange, as I've got the same setup as you (though I rooted with Monster Rootpack) and I was able to do exactly what you're trying to just yesterday.
Try fixing permissions via Clockwork, perhaps?

Hi. I am having an issue with the wifi after trying to use root exp. to paste in a wpa_applicant file. The R/W toggled, and worked, and i was able to set permission changes, but it went wrong and i cannot get wifi to come back on. I've booted again several times, plus i've tried reversing it, get the old file named back to original name, but that isn't doing anything to help. Does Clockwork help if you've screwed something up with the root exploring? Anyone have an example of an attempt at fixing something in the system/bin structure?
thanks much
EDIT: this has been solved. I put the fix outside if the folder and then also renamed the wpa supp folder and this worked.
lyam23 said:
That's strange, as I've got the same setup as you (though I rooted with Monster Rootpack) and I was able to do exactly what you're trying to just yesterday.
Try fixing permissions via Clockwork, perhaps?
Click to expand...
Click to collapse

When I had issues with root explorer not going into r/w or vise versa I just installed busybody from the market
Sent from my Ginger Tazz using XDA App

[ROM][CWM]KhasMek Stock Deodexed plus! For Tab 10.1

As normal, it's not my fault if you fubar your tab by flashing this or if zombies come and speedhump your cat. You've been warned.
Well, hello there, some of you may know me from my vzwtab (7") work, but I'm sure most of you don't.
No matter, I just finished deodexing my framework and app folders, so I decided to share with you.
This isn't anything special, just you're stock system that's been deodexed, I did not remove any programs, there are really only three or so 'bloatware' apps on here, so I didn't bother.
If you would like to, just use root file explorer (or your preferred method) to remove them.
In addition to the stock items I have added pershoot's SU/Busybox/misc package (SOURCE) All credit goes to him for that.
If there's anything else, just let me know. I have tested this on my own rooted tab and everything seems to work fine and be stable.
If you notice any issues, please format/clear both Dalvik & normal Cache. It's probably the cause.
Features
Deodexed flashable system
Pershoot's SU/Busybox/misc pacakage (nano, VIM, all kinds of other goodies)
Changelog
06212011- r1 - Initial Release
Known Issues
You may have to go through and manually delete your odex's in /system/app/ and /system/framework/ but the apk's and jar's no longer call them. (I can't get the amend format command working right. if you want to tell me how, please!)
Installation
Reboot into CWM either via ROM Manager or via power off, volume down + power, volume down to CWM icon and volume up to select.
Select Install Zip from SD Card
Navigate to location of zip and select okay
Clear Cache and Dalvik Cache (in advanced)
Reboot
Make themes for me
Download
HERE
Lastly, if you like my work, donate to me so I can donate money to devs that make my world easier (and therefore yours).

awesome finally someone to break ground for the Samsung Galaxy tab! Thanks will try it out!

Not sure if it matters but is this for retail or I/o version? Does it matter since it is basically the same tab?
For any ideas: maybe you could include a way for hulu to work without any work arounds? And maybe some lag fixes. Although that may be solved with a custom kernel.
Sent from my PC36100 using XDA Premium App

Decided to test this on the retail version.
The only problem is that root is broken because there are two su binaries installed.
/system/bin/su - installed from file Samsung_Galaxy_Tab_10.1_root.zip when you rooted the device.
/system/xbin/su - installed when you added [Tools] – SU/BusyBox/Misc – Galaxy Tab 10.1 (Update: 6/18/11).
To fix:
http://forum.xda-developers.com/showpost.php?p=14016703&postcount=18
------
the /system/bin/su binary need to be removed.
Su does not work on the tablet with two su binaries installed.
Use adb to remove /system/bin/su
adb remount
adb shell
cd /system/bin
rm su
reboot
I tried running titanium backup prior to a reboot after removing /system/bin/su and it would not work. I uninstalled/reinstalled and it worked, but a reboot may have fixed the problem.
I manually deleted all the odex files - no problems so far. I will provide an update later if I have problems.
------------
You can remove /system/bin/su when you update the image again.
JD

Yeah, I just noticed that myself actually. Don't know why I didn't catch it before.
Anywho, I think I'll prolly push an update to this tomorrow after I write a script to remove the odex's. It was my initial thought, but I thought it would be easier to used the updater-script to do it, but looks like just writing an additional one will be best.
Glad the su thing didn't confuse you too much!

Sweet thanks for this. Going to give it a whirl!

I flashed the Samsung_Galaxy_Tab_10.1_root.zip after flashing the Rom. Everying is working fine.
I didn't need to remove su from anywhere.
Thanks!
Sent from my GT-P7510 using XDA Premium App

Same here
Sent from my GT-P7510 using XDA Premium App

Any chance you can add a browser.apk that gives access to Google Labs?
Sent from my GT-P7510 using Tapatalk

touchpro247 said:
I flashed the Samsung_Galaxy_Tab_10.1_root.zip after flashing the Rom. Everying is working fine.
I didn't need to remove su from anywhere.
Thanks!
Sent from my GT-P7510 using XDA Premium App
Click to expand...
Click to collapse
You will only have problems when you try to run an app that requires root (Root Explorer, Titanium backup....).

danielsjam said:
You will only have problems when you try to run an app that requires root (Root Explorer, Titanium backup....).
Click to expand...
Click to collapse
Nope, not at all. They both run fine. Thanks tho. Others may have that problem, I don't.

touchpro247 said:
Nope, not at all. They both run fine. Thanks tho. Others may have that problem, I don't.
Click to expand...
Click to collapse
If you have both su binaries - and all works - good to hear. I will flash again, but will reboot a second time to see if it matters. Those apps did not run until I remove the su from bin.
Strange how two devices with the same specs operate different on certain software.
JD

shouldn't that have been:
cd /system/bin ?
i didn't try mine w both since i didn't want hassle of find out if it worked or not. no reason for 2 su's.
danielsjam said:
Use adb to remove /system/bin/su
adb remount
adb shell
cd /system/app
rm su
reboot
JD
Click to expand...
Click to collapse

madsquabbles said:
shouldn't that have been:
cd /system/bin ?
i didn't try mine w both since i didn't want hassle of find out if it worked or not. no reason for 2 su's.
Click to expand...
Click to collapse
Yes - my bad - should be /system/bin - will correct it.
Thanks
Jd

Its because one su has the correct permissions and the other doesn't.
Sent from my GT-P7510 using XDA Premium App

how about adding some screenshots ??

pflorin said:
how about adding some screenshots ??
Click to expand...
Click to collapse
Looks just like stock...

So whats this have that stock doesnt,,,whats the pro's to flashing as opposed to what I already have?
concept0 said:
Looks just like stock...
Click to expand...
Click to collapse

camblue said:
So whats this have that stock doesnt,,,whats the pro's to flashing as opposed to what I already have?
Click to expand...
Click to collapse
When themes become available you'll be able to flash them. You'll aslo be able to flash a few other mods...
Sent from my GT-P7510 using XDA Premium App

anaphora68 said:
Any chance you can add a browser.apk that gives access to Google Labs?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
No, you're more than welcome to sideload an apk's you wish however.
I'll push out an update today that gets rid of my silly su mistake, gimmie a couple hours.
Glad you people are enjoying it.

Enable Paid Apps in Market for Xoom Wi-Fi

That will be easy if you have root permission. No need any kind of Market Enabler, just modify the build.prop in you /system/ directory add add some lines:
1) Make /system writable
adb remount
2) Download default build.prop from Xoom
adb pull /system/build.prop
3) Use text edit to open build.prop and add following lines
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.com.google.clientidbase=android-verizon
4) Upload modified build.prop back to your Xoom
adb push build.prop /system/build.prop
5) Reboot device to apply changes
adb reboot
Then you Xoom will turn a Verizon devices, and you could see Paid Apps and also the Books and Movies tab.

Thanks, I did the edit with root explorer instead. Working great.

great info, confirmed working.

Awesome. Worked perfectly on my Xoom; also used Root Explorer.
I take it it should also work on other tablets (Acer Iconia A500 in mind)?
Sent from my T-Mobile G2 using Tapatalk

Those who got this to work using root explorer are you guys rooted or on stock.? I don't want to wipe my device just root.

supremecream06 said:
Those who got this to work using root explorer are you guys rooted or on stock.? I don't want to wipe my device just root.
Click to expand...
Click to collapse
Im on stock, didn't push any files. Manually edited the build.pop

I apologize for my ignorance. But what exactly is this mod for?

1el said:
I apologize for my ignorance. But what exactly is this mod for?
Click to expand...
Click to collapse
To make Market on tablets could list paid apps, books and movies.

hi, i am a little bit confused by "paid apps," what exactly are you referring to.
if you don't mind explaining and enlightening me. thanks..

With this mod can you actually rent and watch movies even without VPN ?

It's not useful for me as I need access to the Japanese Market as well. I can't keep on adb-ing everytime I need to change the build.prop.
Market Enabler is still the way to go for me.

nan.ye said:
That will be easy if you have root permission. No need any kind of Market Enabler, just modify the build.prop in you /system/ directory add add some lines:
1) Make /system writable
adb remount
2) Download default build.prop from Xoom
adb pull /system/build.prop
3) Use text edit to open build.prop and add following lines
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.com.google.clientidbase=android-verizon
4) Upload modified build.prop back to your Xoom
adb push build.prop /system/build.prop
5) Reboot device to apply changes
adb reboot
Then you Xoom will turn a Verizon devices, and you could see Paid Apps and also the Books and Movies tab.
Click to expand...
Click to collapse
Unfortunately in version 3.2.2 this trick stopped working.
It was good while lasted

So who has the old market 1.0.28?
Sent from my ADR6400L using xda premium

Has anyone tested this with a Samsung Note device running Gingerbread 2.3.6?

mount -o remount,rw /system mount: Read-only file system

Im on Android M preview 2 with Desparis 3.3 kernel, rooted.
I would like to update build.prop and change user -> userdebug.
Before on Lollipop all I had to do is remount /system in rw and change the file.
Android M doesn't allow me to remount /system in rw.
adb push fails to overwrite the file.
Any solutions please ?

jodvova said:
Im on Android M preview 2 with Desparis 3.3 kernel, rooted.
I would like to update build.prop and change user -> userdebug.
Before on Lollipop all I had to do is remount /system in rw and change the file.
Android M doesn't allow me to remount /system in rw.
adb push fails to overwrite the file.
Any solutions please ?
Click to expand...
Click to collapse
I dont think you can write to system at all anymore, even with root. I do it all in recovery for right now.

Thanks! At least it's one possible solution !

david279 said:
I dont think you can write to system at all anymore, even with root. I do it all in recovery for right now.
Click to expand...
Click to collapse
Actually, can you elaborate how do you do it ?
I've just tried booting into TWRP, then connected the phone to PC, did adb push of changed build.prop into /system, reboot the phone and realized that the phone still has the old build.prop.

jodvova said:
Actually, can you elaborate how do you do it ?
I've just tried booting into TWRP, then connected the phone to PC, did adb push of changed build.prop into /system, reboot the phone and realized that the phone still has the old build.prop.
Click to expand...
Click to collapse
First in twrp make sure you mount system in the mount menu then you should be able to push and pull. You probably pushed the file nowhere even though I think you should've got a error message. I pulled the build.prop straight from twrp edited it then pushed it right back. Did it for the tethering hack. ? ?

david279 said:
I dont think you can write to system at all anymore, even with root. I do it all in recovery for right now.
Click to expand...
Click to collapse
sure you can. all i use is root explorer. i change what i need, save it, then reboot for it to take affect. works every time.

simms22 said:
sure you can. all i use is root explorer. i change what i need, save it, then reboot for it to take affect. works every time.
Click to expand...
Click to collapse
I didn't think write to system was working in the M builds. Must be something wrong with his root method.

david279 said:
I didn't think write to system was working in the M builds. Must be something wrong with his root method.
Click to expand...
Click to collapse
maybe. im using despair and sometimes elementalx kernels. does everything else root work for you? all is working here.
edit.. i should ask him, not you

simms22 said:
maybe. im using despair and sometimes elementalx kernels. does everything else root work for you? all is working here.
edit.. i should ask him, not you
Click to expand...
Click to collapse
Root works great in all apps.
The only problem I have is with RO system. Before M I would use ES explorer to modify and save build.prop and Android Terminal to remount system as RW. But it doesn't work like that anymore in M.
Ive never tried root explorer.

jodvova said:
Root works great in all apps.
The only problem I have is with RO system. Before M I would use ES explorer to modify and save build.prop and Android Terminal to remount system as RW. But it doesn't work like that anymore in M.
Ive never tried root explorer.
Click to expand...
Click to collapse
it works exactly like it did before over here. and ive manuslly changed my build.orop several times already.

I'm on Preview 2, rooted, Despair kernel 3.3.
Still confused as to how to enable mounting /system r/w from within Android and not TWRP. Trying FX file explorer as well as Terminal Emulator with no success. I have Busybox installed and under Applet Manager it shows the "Mount" applet as installed and symlinked to /system/bin/toolbox.

KnifeSkills said:
I'm on Preview 2, rooted, Despair kernel 3.3.
Still confused as to how to enable mounting /system r/w from within Android and not TWRP. Trying FX file explorer as well as Terminal Emulator with no success. I have Busybox installed and under Applet Manager it shows the "Mount" applet as installed and symlinked to /system/bin/toolbox.
Click to expand...
Click to collapse
Haven't tried M as it buggy but have used Root Explorer the grand father of file explorers on everything since TBolt.

prdog1 said:
Haven't tried M as it buggy but have used Root Explorer the grand father of file explorers on everything since TBolt.
Click to expand...
Click to collapse
root explorer since 2009 here

simms22 said:
root explorer since 2009 here
Click to expand...
Click to collapse
Root Explorer FTW. Always works and same file system as shows on PC.

Well Root Explorer wasn't the answer, surprisingly enough haha...
Needed insecure boot.img obtained here flashed with help from this thread, with further reading here for better understanding or doing it yourself.
Also I apparently forgot that adbd insecure by chainfire exists until just now, which could have potentially been another solution.