Hi I've searched the forums to the best of my ability, and cant figure out how to install a system app. I pulled the app (Via ADB Pull) and tried to push it back into /system/app and it works, but never installs? And i cant find it with astro or other software. =( Im using a G1 with Cyan, If you need more information please tell me!
Pushing does install. It doesn't have the install text like adb install does, but that is how you push files so it should work.
You could check to see if you have it set as read only, or delete the file then copy over the new one.
Im not sure what i did but i just kept trying and rebooting untill something worked =/ Lol Thanks though.. What do you mean by Read Only?
System partition is read-only by default, you need to change it to read-write if you want to install or push anything to it. I can never remember commands but they are all over this forum.
For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you
Yes this method definitely works. I have market working now and can search for protected apps etc.
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/
Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
Yes, it requires an edit to a file that you can only be edited when rooted
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!
OP has been updated with original build.prop
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.
Thanks for the reply.
I'm not sure if this has been answered or not. I searched through the forums but didn't find anything about it. Can you change the boot screen on this version of the rom?
You just need to replace the "bootanimation.zip" package in /system/media
hmmm, i tried to do it with a root explorer. I may not of done it right, ill try it again
I used super manger, I realized at first that it wasnt using root permison. fixed that, coppied it there, reboot, and still didnt see the custom animation. any thing else im missing?
well i retried it, and copied to some /local directory and vala it worked! thanks guys
My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?
u need to rsd the swu.zip in order to get the update
OK, where can I get the swu.zip?
lacesout said:
OK, where can I get the swu.zip?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)
mrcastillo said:
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)
Click to expand...
Click to collapse
Thank you, this work!
lacesout said:
My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?
Click to expand...
Click to collapse
lacesout, had the same experience. Used one-click method to root, then used psouza4's bloat script to remove, then restore apps when the update became available. These were my only mods. Went to /system/app and all app's are back with the proper apk extension. Update downloads fine, then hangs at 1/4 to 1/3 of install. Anyone else with similar experience or thoughts as to what's hanging the OTA install?
If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App
nu2droid said:
If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks for the reply and the tip on root explorer, it's an elegant tool, more intuitive to use than the freeware apps.
All the file extensions in /system/app are either .apk or .odex with the exception of Fota.apk.bak, and Fota.odex.bak. As the first time I heard of nandroid was your post, I unfortunately didn't use it, so I don't know if these were the extensions before I used psouza's bloat removal script. Fota was not on the list of scripts to remove/rename in his original post.
As Fota is the "firmware over the air" app, it is suspicious that it's the only one with a .bak ext. I am using root explorer to rename both, removing the .bak, and then will attempt another update.
Success! "Your phone has been upgraded to 5.6.890.en US version". Have lost root, at least for the moment. Will deal with that tomorrow. Last thing to do before going to bed is find the "Thanks" button. Thanks for setting me on the right path. P.
Unable to root after OTA to .890
One click root not longer works. After clicking "run_to_root_your_droid3.sh" on PC (Ubuntu 10.04) I get no prompts on screen, but phone does reboot twice. No su privileges after boot. Busybox is installed in /system/xbin and there is nothing I can do about it as I can't mount r/w. Using Root Explorer and Script Manager as tools.
I realize I'm going to have to increase my learning curve here. Would appreciate any links to relative threads on this topic, or suggestions on what to try next (I have searched, but need some direction).
Hello
I've got the Note 5 SM-N9208 and I am trying not to root (tripped Knox tho as I but Phillippines system.img on it) it as the annoying Barclays App doesn't work.
I am however, trying to add my custom CA certificate into the /system/etc/security/cacerts folder. This is what I used to do in my rooted devices before and worked fine.
I have flashed TWRP and taken a full backup (thank God!) and then mounted the system as RW, copied the file, rebooted and voila, boot loop on the Samsung Note 5 screen.
The only fix is to reflash the system partition from the original TAR file which makes me wonder - is there a mechanism that prevents system from being modified if the device is unrooted? Something like Samsung's system protection or something.
Could anyone try to reproduce the issue on an unrooted phone just to see if it's just me being unlucky? Or is is simply not possible to modify system without root? If so, how come TWRP allows me to do so?
Let me know what you think guys
Looking forward to hear someone else's opinion.
mateuszd said:
Hello
Let me know what you think guys
Looking forward to hear someone else's opinion.
Click to expand...
Click to collapse
You must be rooted to make system changes.
You need to make some changes in ramdisk : remove support_scfs,verify from the fstab files for system partition