Can someone give me the adb command and/or terminal commands to push a custom Phone.apk?
Thanks
adb remount
adb push Phone.apk /system/app/
Been trying to do the same thing since yesterday.
This is what I get with the two commands posted above:
Code:
failed to copy 'Phone.apk' to '/system/app/Phone.apk': Directory not empty
EDIT:
Trying it again now and it seems to just hang there. It's been over 10 minutes and it doesn't seem to be doing anything (Process status: Sleeping).
All my attempts result in the phone freezing. I have to remove the battery in order to reboot it. Thankfully, I haven't managed to brick it yet, though I suspect I'm getting closer to achieving brickdom with every attempt.
do it via recovery?
Worked like a charm. It fails on "remount" while in recovery and I thought I was doing something wrong but apparently it's not required.
EDIT:
Well the copy worked:
Code:
1224 KB/s (835675 bytes in 0.666s)
but I'm not sure if it actually did anything. The new apk is supposed to change the call screen but it doesn't. Also, while in recovery mode if I
Code:
adb shell ls /system
there's only bin/ directory in there (i.e., no app/). Am I doing something wrong?
S_Dot: Sorry for hijacking the thread. At first it was just to clarify one little problem that I assumed you may have had as well but now it's sorta snowballing.
EDIT2:
OK, I found the "mount /system" option in the advanced menu. Thanks for the help and hope this helps someone.
Achilleas you are AWESOME!
I have been looking for ages how to do this since I always got problems. Finally it worked!
Thanks
can anybody shead some light on this problem. I downloaded file Phone.apk
Voicemail fix
Use adb push to replace phone.apk in system/app
adb remount
adb push Phone.apk /system/app/Phone.apk
adb reboot
I used adb.exe from command; everything went successful, But now cant make any calls or go into setting calls. I get for close error, I made a back up of rom so all good. I tried twice. twice no good, this file must not work with the evo. I have an evo 4g
You could try
Code:
adb shell chmod 644 /system/app/Phone.apk
before the reboot.
phone.apk deleted how to install again
my phone micromax a52 is rooted but unfortunatlly i deleted phone.apk from system/app due to this the sim network gone from status bar and i am not make call or recieve call please help me...................................
Related
I'm running Fresh 2.1.1 and I have quite a few texts built up on my phone but every time I try to delete a thread it just doesn't. I press delete, the menu disappears, and the thread just stays there. Any thoughts? If I need to put more info I can, or if anybody can tell me where I can go in adb to delete them? Thanks in advance!
this does it. i had to do this to my gf's hero last week
this will make a backup of your texts on your pc before.
Code:
mkdir c:\temp
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db c:\temp (this will backup the database to your computer at c:\temp, just in case)
adb remount
adb shell
rm /data/data/com.android.providers.telephony/databases/mmssms.db
reboot
Thank you very much!
Hi guys,
sorry if my english isnt so good...
i'm in trouble with ADB..
i want to upgrade my swype keyboard on my NEW M1 rom eu....i got the 1.58 and i want to try the 1.60..
i found a thread on this forum with commands for upgrading the swype like this way:
Code:
adb remount
adb shell
su
pm list packages -f | grep swype
rm /system/app/<restOfApkPathFoundInAboveCommand>
pm uninstall <value after apk= found in result of 2 commands above>
exit
Install normally. If you want the apk in the rom:
adb push <newSwype.apk> /system/app/<newSwype.apk>
adb remount
adb shell
pm install <newSwype.apk>
(found here-> LINK)
I'm stuck at the beginning:
Code:
C:\android\tools>adb devices
List of devices attached
9000ec2a228b device
C:\android\tools>adb remount
remount failed: No such file or directory
my phone is rooted and in debug usb mode..I dont understand how can I go ahead...
what can I do?
thanks
ivan
Same here.
gbates said:
Same here.
Click to expand...
Click to collapse
oh..i'm not the only one! : >
we need to find the solution...but it's not easy..
are u using the NEW M1 rom too?
Rooting doesn't automatically give you remount permissions AFAIK.
i just use this command
Code:
adb push test.txt /sdcard/test.txt
and the copy is ok....i found the file in the sgs sdcard...
The command adb remount is for the /system directory (for set write permission) .... i think it cant find the directory /system on the phone......why?!?!
danmullen said:
Rooting doesn't automatically give you remount permissions AFAIK.
Click to expand...
Click to collapse
mmmm what do u mean? i need to do something else? thanks
Are you using the internal ext2 lagfix? I think that causes problems with the adb remount command. It doesn't work for me either.
Same results using a different ROM?
psychedelic'd said:
Are you using the internal ext2 lagfix? I think that causes problems with the adb remount command. It doesn't work for me either.
Click to expand...
Click to collapse
No lagfix installed at the moment..i installed lagfix when i was on M2 but i think that reflashing removed the lag fix...is it right?
harold4 said:
Same results using a different ROM?
Click to expand...
Click to collapse
Not yet but i think i'm gonna try it this afteroon if i dont find a solution.
Sent from my GT-I9000 using XDA App
adb remount as well
Trying to remap hard keys, adb remount along with push and pull do not work. Depending on whether im in shell or not I get no such file or directory or file not found errors. I can change into directory of each of the folders im trying to work with, and look at the file but I can't push it from my tools folder(locally) or pull it from the system folder. Every tutorial I see has adb remount command first, which fails every time.
Samsung Fascinate
Blackhole-build your own rom
(also tried on jt's latest rom, same issue
Crazy
I'm having the same issue here too. I'm trying to get a custom boot screen on my rooted Samsung Infuse and I've tried every way I can think of and it wont take. Clockworkmod says successfully installed, but its not. Soon as I reboot I see the At&T stock boot. I've fixed all of my permissions and still no luck.
So I saw a solution to do it via adb by typing "adb remount" and I get the same thing u guys are getting. I've got a headache now. Done all I could, even typing "shell", "su", that all goes well then when I tried to push it "adb push bootanimation.zip system/media" I get adb: not found. Smh, is it a device issue?
i think ive got the solution
flash a new kernel..................................worked for me................
One click root after update: "We have root, but couldn't push busybox. Not sure why!"
I just updated .890 which seemed to go fine with no errors (unfroze all bloat, but did not unroot), but I lost root, as expected.. but when I use Pete's one-click root tool (latest version), it gets to step 3 and gives me the error about not being able to push busybox...!? It says I "have root", but none of my apps recognize it.. I've pulled the battery, rebooted and retried like 10 times... still can't get it to re-root. I've made sure Debugging and Unknown Sources is enabled and tried in Charge Mode and Mass Storage mode... Am I going to have to stock flash this thing and re-update & re-root?
I THINK I have some type of root.. maybe... because Root Explorer will let me mount the System directory as R/W and I can TRY to manipulate files, but if I delete something (like su), it appears to delete successfully, but the file comes back if I refresh the directory.. but I also noticed when I go into the System directory, Root Explorer claims I only have 1MB of free space out of 318.00MB... how did that happen? If I try to run Superuser.apk, it force closes on me.
Any help or ideas are greatly appreciated...
there's an app on the android market that will push busybox if you have root. I'd look into that
edit: have you attempted to run the one-click root again? and if that doesn't work you can try to use the adb method if you're comfortable with it. And make sure that all of your drivers and everything are up-to-date
I have done battery pulls and like a dozen+ re-tries at the 1-click root, always get the same error.. I have been into the ADB shell to try and figure this out and I see the ADB Shell starts out by giving me a # prompt... that means writable/root, right? Any instructions on what I have to do from there?
I will look into that push busybox app, thanks.
http://wiki.rootzwiki.com/index.php/Motorola_Droid_3
This is where all the info about the adb and one-click stuff. The tough part about the adb method is manually pushing su to the (i think) system/xbin folder. Then i just used the app on the marketplace to push busybox. But there's a download link for both of those on the website
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Kraxis said:
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Click to expand...
Click to collapse
After temp ADB root, steps 18 and beyond should do it. You may want to check /system/bin and /system/xbin to remove the old su binaries before pushing the new one. Some folks have one in each location for some reason. Put it in xbin, but if it doesn't work, /system/bin will. Superuser wouldn't recognize xbin for me so I moved it to /system/bin and i'm good since.
Anyone have a thought on the xbin not always working? I think this is the 3rd topic i've seen with this issue, not including myself.
Sent from my DROID3 using XDA App
OK, I got root back! I used steps 18+ for "ADB Method" (after using Pete's temp ADB root) and essentially replaced SU and Superuser.apk, CHMOD'd it rebooted and I had root! Thanks guys!!
Hi,
I've downloaded and installed though recovery mode the boot animation from Nexus Prime on my Galaxy S but now that animation doesn't leave my screen anymore, it keeps running in the foreground even after boot is complete. I can feel and "interact" with the home screen in the background but I'm totally blind.
Already attempt to install Samsung stock boot animation back and also other ones without any success. Prime animation is still there.
Anyone here had the same issue or know some smarter and better way to remove this without have to install custom rom back? Unfortunately I don't have a backup for everything :/ (lessons learned)
Appreciate your attention and help!
- Willian
Get to recovery and try connect your phone via adb, then replace the boot animation... But it sounds like the boot animation may not be the issue...
I've tried to mount /system and move the boot animation to /system/media without any luck, getting 'permission denied' everytime.
C:\android-sdk-windows\platform-tools>adb push GalaxyS-Edify.zip /system/media/
failed to copy 'GalaxyS-Edify.zip' to '/system/media//GalaxyS-Edify.zip': Permis
sion denied
Click to expand...
Click to collapse
/system/media $ mv /sdcard/GalaxyS-Edify.zip /system/media/bootanimation.zip
mv /sdcard/GalaxyS-Edify.zip /system/media/bootanimation.zip
mv: overwrite '/system/media/bootanimation.zip'? y
y
mv: can't remove '/system/media/bootanimation.zip': Permission denied
Click to expand...
Click to collapse
Any idea?
Thanks again!
You could try to make an update.zip which replaces the nexus prime bootanimation with the stock one.
I'll give a try. First time creating an update.zip but let's see if it works.
Thank you.
Nothing ;/
unless I've made something wrong
Im not too familiar with adb but ill give it a shot... Btw you have root and busybox installed?
Get to recovery..hopefully debug is on, plug it in..
Get to platform-tools as you did, then type
adb devices (you should see your device, if not close it all and install the drivers again from kies, then try again...)
type the following, after you have got to platform-tools using the cd command
adb shell mount /system
nothing should show up
you know where the bootanimation is? if not find it, using "adb shell ls /" this will show all the directories, carry on searching it till you find it
next you want to move it so like you did...or like this
"adb shell rm /system/media/bootanimation.zip"
Now check its gone, using the ls command
now put yours in.. rename it to bootanimation.zip
"adb push C:\your full directory of where it is with bootanimation.zip /system/media"
and it should say that its gone....
hopefully that all works..
let us know
Hey Talon, thanks for helping me out, really appreciate!
Hmm, yes for root but no quite sure about busybox now.
I found bootanimation.zip inside /system/media and there's also a bootanimation file inside /system/bin but not quite sure what it's used for.
Got a permission problem when trying to remove the .zip file:
C:\android-sdk-windows\platform-tools>adb shell rm -f /system/media/bootanimatio
n.zip
rm: can't remove '/system/media/bootanimation.zip': Permission denied
Click to expand...
Click to collapse
C:\android-sdk-windows\platform-tools>adb shell chmod 755 /system/media/bootanim
ation.zip
chmod: /system/media/bootanimation.zip: Operation not permitted
Click to expand...
Click to collapse
What am I missing?
Regards.
Ok maybe you know more about these commands but why did you type "-f" after rm? have you tried without it?
In the second box you were trying to change permission (had to search that ) why not change it to 777 for full, and instead apply it to the directory, so the media folder then try...
have you tried just pushing the new file to the media folder?
Btw why not just try flash a new rom either through recovery or odin. I guess you can try this so you don't loose anything, but i think that would be the simplest of things to do. You will loose apps and settings, but int sd should still be there.
Anyway see how that goes...
Just seen this says to remove you can use "adb shell rm -r" so add "-r" instead of the f that you did.
Oh and lastly, if you still cant do that, try copy the whole media folder, make sure you have everything by using ls /system/media then try remove the media file and put it all back with your new boot animation.. (dont forget to rename the bootanimation
Not really, just a few commands. The "-f" just removes the file without the need to confirm your action but no enough permission to perform such action and I'm not able to change this.
I have been trying many ways to move the file to the media folder but could not find one that works yet.
Hmm, I would like to avoid that :/ but maybe it's the only way.
I think my problem here is that I can't get superuser access. When I type "su" I just get a segmentation fault message. Couldn't find a way to fix that yet.
Thanks.
willian7 said:
Nothing ;/
unless I've made something wrong
Click to expand...
Click to collapse
Try to flash this update.zip threw your cwm, just go to install zip from sdcard and choose the update.zip, sure first you have to copy it to your sdcrad . (i've tested it, for me everything worked fine)
hope i was able to help
I WROTE THE FOLLOWING WHILE TRYING TO TROUBLESHOOT/DOCUMENT MY OWN STEPS BUT I HAVE FOUND A SOLUTION. I HAVE POSTED THIS IN CASE SOMEONE ELSE MAY FIND THE INFORMATION USEFUL.
Is that appropriate? Move/delete this if you see fit.
I have an AT&T Moto X running 4.2.2 rooted with PwnMyMoto. Since it is with ATT, it has a locked bootloader.
[PROBLEM]
After putting a custom bootanimation.zip in the /system/media directory, device boots/"works" but display is black.
[HOW IT HAPPENED]
Using ES File Explorer, I turned on the /system r/w, copied the bootanimation.zip from the (internal) sdcard, and then overwrote the original boot animation (I do have a backup).
However, after booting the phone now, there is only a black screen. It seems to be working, there's just nothing displayed.
[WHAT I CAN DO/HAVE DONE]
ADB debugging has already been enabled
ADB shell has already been granted superuser permissions (Using SuperSU, unsure if solution works if this hasn't been done?)
It vibrates sometimes as though I have an email, notification, or whatever
I can access storage with usb cable,
adb get-state returns device,
I CAN get into fastboot (screen displays normally here), however PwnMyMoto overwrites recovery,
when rebooting the phone, the motorola power down animation is displayed
I tried to put back the original with
adb push bootanimation.zip /system/media
but get 'permission denied' (you may be able to use method this on a different device/carrier/ROM)
adb shell getprop ro.boot.write_protect returns 0
in adb shell
mv /sdcard/download/bootanimation.zip /system/media/ returns failed - cross-device link (googled this, seems normal, but I'm unsure how else to copy it back)
su
mount -o remount,rw /system
doesn't return anything but I am unsure where to go from there.
cannot run adb as root, as the phone is not a dev model
[RELATED POSTS]
http://forum.xda-developers.com/showthread.php?t=2249659
[HOW I FIXED IT]
start adb
ensure that 'adb shell getprop ro.boot.write_protect' returns 0 (if not, reboot into recovery)
start phone in recovery mode with
adb reboot recovery
then
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw /system (not sure which one of these ended up being 'correct' but it didn't hurt to do both)
cp /sdcard/download/bootanimation.zip /system/media/ (copy <src> <dest>, src is wherever the backup zip is located, if you are unsure of where the files are, use the 'ls' command to navigate the directories)
adb reboot
After doing this, the screen started displaying as normal.
Apologies for the lack of technicality, not much a dev myself. Just glad to have it working again.
help
oc83 said:
I WROTE THE FOLLOWING WHILE TRYING TO TROUBLESHOOT/DOCUMENT MY OWN STEPS BUT I HAVE FOUND A SOLUTION. I HAVE POSTED THIS IN CASE SOMEONE ELSE MAY FIND THE INFORMATION USEFUL.
Is that appropriate? Move/delete this if you see fit.
I have an AT&T Moto X running 4.2.2 rooted with PwnMyMoto. Since it is with ATT, it has a locked bootloader.
[PROBLEM]
After putting a custom bootanimation.zip in the /system/media directory, device boots/"works" but display is black.
[HOW IT HAPPENED]
Using ES File Explorer, I turned on the /system r/w, copied the bootanimation.zip from the (internal) sdcard, and then overwrote the original boot animation (I do have a backup).
However, after booting the phone now, there is only a black screen. It seems to be working, there's just nothing displayed.
[WHAT I CAN DO/HAVE DONE]
ADB debugging has already been enabled
ADB shell has already been granted superuser permissions (Using SuperSU, unsure if solution works if this hasn't been done?)
It vibrates sometimes as though I have an email, notification, or whatever
I can access storage with usb cable,
adb get-state returns device,
I CAN get into fastboot (screen displays normally here), however PwnMyMoto overwrites recovery,
when rebooting the phone, the motorola power down animation is displayed
I tried to put back the original with
adb push bootanimation.zip /system/media
but get 'permission denied' (you may be able to use method this on a different device/carrier/ROM)
adb shell getprop ro.boot.write_protect returns 0
in adb shell
mv /sdcard/download/bootanimation.zip /system/media/ returns failed - cross-device link (googled this, seems normal, but I'm unsure how else to copy it back)
su
mount -o remount,rw /system
doesn't return anything but I am unsure where to go from there.
cannot run adb as root, as the phone is not a dev model
[RELATED POSTS]
http://forum.xda-developers.com/showthread.php?t=2249659
[HOW I FIXED IT]
start adb
ensure that 'adb shell getprop ro.boot.write_protect' returns 0 (if not, reboot into recovery)
start phone in recovery mode with
adb reboot recovery
then
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw /system (not sure which one of these ended up being 'correct' but it didn't hurt to do both)
cp /sdcard/download/bootanimation.zip /system/media/ (copy <src> <dest>, src is wherever the backup zip is located, if you are unsure of where the files are, use the 'ls' command to navigate the directories)
adb reboot
After doing this, the screen started displaying as normal.
Apologies for the lack of technicality, not much a dev myself. Just glad to have it working again.
Click to expand...
Click to collapse
I had the same problem and i want a simple way to fix. any help?
iamgothamshero said:
I had the same problem and i want a simple way to fix. any help?
Click to expand...
Click to collapse
I wrote down the steps I took to fix it at the end of the post. You'll have to restore the old boot animation file with ADB. Hopefully, ADB shell was already given root permissions on your phone, otherwise I'd be unsure of how to fix it.
reply to u
oc83 said:
I wrote down the steps I took to fix it at the end of the post. You'll have to restore the old boot animation file with ADB. Hopefully, ADB shell was already given root permissions on your phone, otherwise I'd be unsure of how to fix it.
Click to expand...
Click to collapse
In the how i fixed it section, idk how to do those things. i have sdk manager on pc. please i am freaked out. can u give me simple instructions. Thank you so much
iamgothamshero said:
In the how i fixed it section, idk how to do those things. i have sdk manager on pc. please i am freaked out. can u give me simple instructions. Thank you so much
Click to expand...
Click to collapse
If you're unsure how to start ADB, I'd think that you've never used it before, and in that case I'd be entirely unsure if that method would work.
That said, you should find adb.exe in the sdk/platform-tools folder. If you shift+right-click this folder you can quickly open a command prompt there to start using the commands (each line in the instructions is a separate command). If you're unsure how exactly to use adb, I'm sure there are youtube videos or other forum posts documenting the basics (try searching for beginner's guide to adb on xda).
YES!!!
oc83 said:
If you're unsure how to start ADB, I'd think that you've never used it before, and in that case I'd be entirely unsure if that method would work.
That said, you should find adb.exe in the sdk/platform-tools folder. If you shift+right-click this folder you can quickly open a command prompt there to start using the commands (each line in the instructions is a separate command). If you're unsure how exactly to use adb, I'm sure there are youtube videos or other forum posts documenting the basics (try searching for beginner's guide to adb on xda).
Click to expand...
Click to collapse
I just downloaded random bootanimation zip, followed ur process, and it worked!!!!!!!!!!!!!!!!!!!!!!! omg so happy!!! thanks so much!!!!!!
---------- Post added at 11:49 PM ---------- Previous post was at 11:23 PM ----------
oc83 said:
If you're unsure how to start ADB, I'd think that you've never used it before, and in that case I'd be entirely unsure if that method would work.
That said, you should find adb.exe in the sdk/platform-tools folder. If you shift+right-click this folder you can quickly open a command prompt there to start using the commands (each line in the instructions is a separate command). If you're unsure how exactly to use adb, I'm sure there are youtube videos or other forum posts documenting the basics (try searching for beginner's guide to adb on xda).
Click to expand...
Click to collapse
It worked the first time then next reboot it shows black screen but i know it hasnt booted cause no sounds. and when i turn tablet sideways it doesnt show half of a screen. (it did that last time the screen was black).