Related
Hey all, ive been trying to change my boot screen to the haters gonna hate one for a few days now but cant seem to get it to work at all, i have full root and tried to the fastboot method and recovery/adb method. no matter what it stays the same as the one i had originally, i never get errors when trying to push the files if someone can give me instructions for dummies haha or another method id really appreciate it sorry for being a noob at all this.
I had the same problem
First of all, what rom are you using? Different rooms pull from different places. I might be able to help you out. If you are running cyan6, try this:
Adb reboot recovery
Adb remount (make sure it remounts. Maybe also do adb root to make sure.)
Adb push blahblah.zip /system/customize/resource/bootanimation.zip
Adb push blahblah.zip /system/media/bootanimation.zip
Adb push blahblah.zip /data/local/bootanimation.zip
If you want sound, push that to the same locations. Make sure there is only one of each file in each folder. Then, to check,
Adb reboot
Hope this helps
oh yeah sorry i should have included that i am on evios 1.2 beta 2 rom
I'm not familiar on where to place boot on this rom. Try all three locations I suggested. System customize resource. System media. Data local. Tell me if it works out.
I had this animation on EViO. I just pushed it from my desktop to system/media. Worked fine for me.
how do you push it from the desktop? i tried all 3 methods posted above and none worked. i had the file in the android sdk tools folder though...also whenever i try to do adb remount i get "remount failed:invalid argument" and adb root gives me "error:closed" i tried killing adb and restarting but no luck
This might be an obvious question, but do you have USB debugging enabled on your phone? Under Setting>Applications>Development
You arent going to be able to push anything if you can't get ADB running first.
yeah debugging has been enabled the whole time
ok have you been in recovery mode?
try typing
adb shell
su (make sure #comes up.)
exit (retype until you get back to the tools directory)
then do the push commands to system media, system customize resource, and data local.
Just use this program. Its as easy as it gets.
http://forum.xda-developers.com/showthread.php?t=701295
dkdude36 said:
First of all, what rom are you using? Different rooms pull from different places. I might be able to help you out. If you are running cyan6, try this:
Adb reboot recovery
Adb remount (make sure it remounts. Maybe also do adb root to make sure.)
Adb push blahblah.zip /system/customize/resource/bootanimation.zip
Adb push blahblah.zip /system/media/bootanimation.zip
Adb push blahblah.zip /data/local/bootanimation.zip
If you want sound, push that to the same locations. Make sure there is only one of each file in each folder. Then, to check,
Adb reboot
Hope this helps
Click to expand...
Click to collapse
Putting sound in boot animation doesn't work with cm6. Just to clarify. No one has been able to get it to work unless you found something out to make it work please share as I have hates going to hate also and want to use haters everywhere mp3 and is perfect for it.
Sent from my PC36100 using XDA App
yeah i have also been in recovery mode every time i tried to run a command prompt for adb...i tried that when i hit adb shell i get # but when i type su after the # it says "/sbin/sh: su: not found"
mount: mounting /dev/block/mtdblock4 on /system failed: Device or resource busy
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
thats what i get when in command prompt when i try to use the program you just posted above
Want a easier way? Use root explorer and copy and paste. Works for my every time. It's in the market. And root explore you can manually turn writeable on and off to move it into system. It's on the top right of screen in root explorer when you go into system folder.
Edit: the command you are tying to put in enables you to push and pull in the system folder. Root explore you can just click a button.
Sent from my PC36100 using XDA App
Good idea
Root explorer works most of the time. If you have the cash, go ahead. You should make site out posted though.
/sbin/sh: reboot: not found
been trying to use adb and i keep on getting that....any of you know a fix?
I cannot figure this out to save my life. I have downloaded and installed HTC Sync. I have the folder for android-sdk setup on my local drive. I added the environmental settings so I don't have to change directories each time.
I connect my phone with USB Debugging enabled, and then open command prompt. I change directories to E:\android-sdk\tools (My "E" drive is my default drive). Anytime I try and "Adb" command, it says that ADB isn't recognized as a command. I don't know why. Cannot figure it out to save my life.
I've attached some pictures so you can get a brief idea as to what I am talking about. I am on Windows 7 32 bit, if that makes any difference.
The first thing I noticed from your screenshot that is that you dont have adb application in your sdk tools folder.
adb has moved...try the platform-tools folder instead of just tools.
*Sigh*
I would miss something as simple as that. It's working now, thank you guys.
Edit:
One more question.. I am trying to install the "com.skype.raider-all-in-one-camwidth". I am assuming I need to use ADB to push it to the system files, but how do I go about doing that from CMD? Probably incredibly simple, but I'm lost again. Lol
dpilcher said:
adb has moved...try the platform-tools folder instead of just tools.
Click to expand...
Click to collapse
I wonder if the adb_has_moved.txt file in his screenshot might have given him a clue?!?
JimSmith94 said:
I wonder if the adb_has_moved.txt file in his screenshot might have given him a clue?!?
Click to expand...
Click to collapse
Lol I admitted it was something stupid to miss, forgive me.
Can anyone help me with the file pushing though? I am trying install that Skype .zip file, and I'm assuming it has to be pushed to the system area. Any clues as to how I go about that?
If you need to get it into system apps,
Adb push filename /system/app
Make sure you put a space between the end of the filename and the /
And make sure the file is located in the platform-tools folder.
hey guys. im tryin to put a file from my computer to my sdcard on my phone through adb and this is the path that im using
/Users/my name/androidsdk/platform-tools/adb push cm_supersonic_full-170.zip /sdcard/cm_supersonic_full-170.zip
and it keeps saying
cannot stat 'cm_supersonic_full-170.zip': No such file or directory
can anyone tell me what im doing wrong. i have the zip file in the platform-tools folder.
It looks like adb may be looking for the zip file in whatever folder you're in when you run adb. You have the zip file in the platform-tools folder, but are you also running adb while in that folder? If not, try moving to the platform-tools folder and then running adb, or else fully qualify your zip file name.
I do have adb in the platform-tools folder along with the zip file.
quikswitch said:
hey guys. im tryin to put a file from my computer to my sdcard on my phone through adb and this is the path that im using
/Users/my name/androidsdk/platform-tools/adb push cm_supersonic_full-170.zip /sdcard/cm_supersonic_full-170.zip
and it keeps saying
cannot stat 'cm_supersonic_full-170.zip': No such file or directory
can anyone tell me what im doing wrong. i have the zip file in the platform-tools folder.
Click to expand...
Click to collapse
Looks like a syntax error. Are you running adb from c:\ or are you in the platform-tools folder when you run adb?
im running it from the platform-tools folder. im also on a mac
Try this.
Adb push cm_supersonic_full-170.zip /sdcard/
The syntax error it is giving is saying that you are trying to push the zip to a folder on the sdcard called cm_supersonic_full-170.zip
Sent from my PC36100 using Tapatalk
Khilbron said:
Try this.
Adb push cm_supersonic_full-170.zip /sdcard/
The syntax error it is giving is saying that you are trying to push the zip to a folder on the sdcard called cm_supersonic_full-170.zip
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
that didnt work either.
I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.
maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:
THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.
error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?
i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help
ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help
dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]
I have been able to root my Kindle and want to get the store working.
I think I need to copy the Google Services Framework APK to the /system/app directory.
I am using ES File Explorer version 1.6.2.5.
My Kindle is version 6.3.2.
When I try to copy the file from the SD card to the /system/app directory it says unable to copy.
Thanks in advance for the help
Did you mount system as read/write?
I'm afraid I don't know what that means. I used KFU 0.9.6 to root the device. I had installed ES file explorer before I did the rooting. Does explorer need to be read/write, or is that an option for KFU? Is it an option I can change or do I have to re-install something?
robvia said:
I'm afraid I don't know what that means. I used KFU 0.9.6 to root the device. I had installed ES file explorer before I did the rooting. Does explorer need to be read/write, or is that an option for KFU? Is it an option I can change or do I have to re-install something?
Click to expand...
Click to collapse
ES File Explorer should have the option to do so, but I don't use it so I couldn't say for sure. If you can't figure it out, I'm sure someone around here will be able to help.
I found the Root settings in ES F E and checked the option for Root Explorer. It gave me a message that test fails option not allowed on your phone. Not sure if that is what I should be looking for or not.
robvia said:
I found the Root settings in ES F E and checked the option for Root Explorer. It gave me a message that test fails option not allowed on your phone. Not sure if that is what I should be looking for or not.
Click to expand...
Click to collapse
Do you have an ADB connection?
The Mount File System option is greyed out.
Below that it says Mount/ , /system as writable.
Does that have to be installed after the rooting is done?
Is there another file explorer option that is better?
Should I uninstall and re-install ES?
ES is on the Kindle. I have copied the APK to the kindle and to the SDcard directory. When I am connected to the computer, my computer only has access to the sdcard directory. I can't even see the /system folder.
ES can see the folder, but can't write to it.
robvia said:
ES is on the Kindle. I have copied the APK to the kindle and to the SDcard directory. When I am connected to the computer, my computer only has access to the sdcard directory. I can't even see the /system folder.
ES can see the folder, but can't write to it.
Click to expand...
Click to collapse
You still didn't answer my question. Do you have a connection with ADB? You were able to root it weren't you? You must have had an ADB connection at some point.
Sorry, Since I was trying to copy the file with out the device connected to the computer, I didn't think it mattered.
When connected to the computer, in device manager, it's Android Composite ADB Interface.
The Kindle shows up as a drive in Windows Explorer. At one point when I was doing the root, it did not show up as a drive.
If I can copy from my computer to the /system directory, that would be great, but since i don't have access to that through the computer, I was copying from the download directory on the Kindle to the /system directory on the Kindle.
robvia said:
Sorry, Since I was trying to copy the file with out the device connected to the computer, I didn't think it mattered.
When connected to the computer, in device manager, it's Android Composite ADB Interface.
The Kindle shows up as a drive in Windows Explorer. At one point when I was doing the root, it did not show up as a drive.
If I can copy from my computer to the /system directory, that would be great, but since i don't have access to that through the computer, I was copying from the download directory on the Kindle to the /system directory on the Kindle.
Click to expand...
Click to collapse
You say you used the KFU to root...do you still have it available? Run it and see if it shows ADB ONLINE.
Yes, the ADB status is online when I run KFU. I also ran Super One Click and it said your device apears to be rooted.
I also installed the app, mount /system (rw/ro).
when I select mount rw, it says the system dir remounted with r/w permission.
robvia said:
Yes, the ADB status is online when I run KFU. I also ran Super One Click and it said your device apears to be rooted.
I also installed the app, mount /system (rw/ro).
when I select mount rw, it says the system dir remounted with r/w permission.
Click to expand...
Click to collapse
Soooo...problem solved, right?
I wish it were that easy. Even though it says it's mounted in r/w mode, I can't get it to copy. Should I try and root it again? Could I have done something wrong? I used KFU and did root with superuser. Should I use Super One Click and unroot then try to root again? I don't remember any options for me to select wrong. Is there a PC tool that alllows you to copy directly to the /system directory? I really thought I was past the hard part. Thanks again for all the help.
Okay, since you have KFU and you have connection with ADB, press Shift then Right-click on the KFU "tools" folder and select "Open command window here". At the command prompt that opens up enter the following (omitting the comments in red, of course) ;
Code:
$ adb push /local/path/to/GoogleServicesFramework.apk /sdcard/ [COLOR=Red]<-- Replace "/local/path/to/..." with the location of GoogleServicesFramework.apk on your computer
[/COLOR]
$ adb shell
$ su [COLOR=Red]<-- If you receive an error here, you need to re-root
[/COLOR]~ # mount -o remount,rw ext4 /system [COLOR=Red]
[/COLOR]~ # mv /sdcard/GoogleServicesFramework.apk /system/app/GoogleServicesFramework.apk
~ # chmod 644 /system/app/GoogleServicesFramework.apk
~ # pm install -r /system/app/GoogleServicesFramework.apk
do the same for AccountAndSyncSettings and GoogleLoginService, reboot, then do the same for Vending.apk (I'm assuming you are trying to install the Market, right?)
Ok. I think I might see the issue. When I rooted the Kindle I did not have the apk copied to the device. It looks like there is a move command that copies the APK file from the SDcard to /sysstem/app folder. I think I need to put the apk in the proper place on the device and then un-root and then try and root it again.
Yes I am tyring to get the market running.
So you are saying there are 3 files that need to be copies? I have the file com.android.vending_3.8.15.apk, but I do not have AccountAndSyncSettings.
The more I read your reply, I'm less sure of myself. Before I root with KFU (or maybe super one click) do I need to have files copied to the Kindle? I guess I would have expected KFU to have these files, but OK if not included. Does KFU attempt to copy the framework file to the proper directory? If so, where does the files need to exist before starting?
I think your instructions here are a command line version of what I am trying to do with ES File Explorer. Is that true?
robvia said:
Ok. I think I might see the issue. When I rooted the Kindle I did not have the apk copied to the device. It looks like there is a move command that copies the APK file from the SDcard to /sysstem/app folder. I think I need to put the apk in the proper place on the device and then un-root and then try and root it again.
Yes I am tyring to get the market running.
So you are saying there are 3 files that need to be copies? I have the file com.android.vending_3.8.15.apk, but I do not have AccountAndSyncSettings.
The more I read your reply, I'm less sure of myself. Before I root with KFU (or maybe super one click) do I need to have files copied to the Kindle? I guess I would have expected KFU to have these files, but OK if not included. Does KFU attempt to copy the framework file to the proper directory? If so, where does the files need to exist before starting?
I think your instructions here are a command line version of what I am trying to do with ES File Explorer. Is that true?
Click to expand...
Click to collapse
You need AccountAndSyncSettings. Are you using a tutorial for this? If so, which, one?
And yes, it is the command line version of what you're trying to accomplish with ES. It will give you more control and you'll be less likely to screw up.
Sure is rooted?
I recently back to stock firm to can check battery issues. I was using JB Hashcode very happy so far and was thinking go back again, but a short pass by the stock firmware was a really bad idea because got an update on the air (6.3.2) and lose my rooted status. I've used KFU again with no luck. Root explorer, droidwall says that i'm not rooted... So sad. Any ideas?
chocaru said:
I recently back to stock firm to can check battery issues. I was using JB Hashcode very happy so far and was thinking go back again, but a short pass by the stock firmware was a really bad idea because got an update on the air (6.3.2) and lose my rooted status. I've used KFU again with no luck. Root explorer, droidwall says that i'm not rooted... So sad. Any ideas?
Click to expand...
Click to collapse
What does this have to do with the topic at hand?
Sorry for not getting back earlier. My weekend included getting hit by a deer. Really messed all my plans up.
I used the instructions here http://forum.xda-developers.com/showthread.php?t=1399889.
These screenshots show an option to install Google Apps, but I don't see that option when I run it. I guess I'm a little confused. Are there different instructions I should be following?