[Q] Boot Animation WITHOUT Root -- /data/local permission denied - Nexus 7 Q&A, Help & Troubleshooting

Hi there,
I'm looking to put a boot animation on my Nexus 7 without rooting it, similar to this thread: http://forum.xda-developers.com/showthread.php?t=1580642
When I issue the adb command, it thinks for a while and appears to be doing something and then comes back with "failed to copy 'bootanimation.zip' to '/data/local/bootanimation.zip' : Permission denied" The command I'm using is adb push bootanimation.zip /data/local
I've added adb to environment variables and my paths are also correct (bootanimation.zip is in the folder I've navigated to in cmd). I've also tried just putting bootanimation.zip into platform-tools. Is there something that I am missing that will allow me to do this, or is /data/local off limits in the N7?
I probably would've spent less time just rooting the thing, but I am trying to avoid that for now.
Thanks in advance for any insight!

i dont have a non-rooted N7 to test, but u may issue the following commands to see if u can access /data/local
adb shell
cd /data/local
ls
Click to expand...
Click to collapse
see if u get any error msg..

Related

chmod boot_animation.xml ?

This is probably a noob question but I've searched and tinkered and I cant get this file altered or replaced. It's located on the device under /system/media. I've rooted my device(if this is relevant??). and copies he xml file first to my sd card and then to my pc where I've altered it(trying to get rid of the Orange logo) and now i want to copy it back to the Hero. So I've tried adb shell and then
> adb push boot_animation.xml /system/media
but that doesn't work I have also tried to chmod 777 boot_animation.xml but still no go. There has to be some way right?
roeblerrieland said:
This is probably a noob question but I've searched and tinkered and I cant get this file altered or replaced. It's located on the device under /system/media. I've rooted my device(if this is relevant??). and copies he xml file first to my sd card and then to my pc where I've altered it(trying to get rid of the Orange logo) and now i want to copy it back to the Hero. So I've tried adb shell and then
> adb push boot_animation.xml /system/media
but that doesn't work I have also tried to chmod 777 boot_animation.xml but still no go. There has to be some way right?
Click to expand...
Click to collapse
try:
adb push boot_animation.xml /system/media/bootscreen

Replacing HTC apps with ANDROID ones

Hi,
After reading this thread and learning that you CAN replace HTC's apps with stock Android ones, I have started messing around to see what other apps I can / should change. I'll use this thread as kind of a log, so if I mess things up I can come back and see where I went wrong. Fellow noobs can surely use it too!
I am using SDK in Ubuntu, but the procedure should be pretty similar in Windows.
First, follow the Unlockr's method to root your phone.
Download a stock Android rom and extract its /system/apps folder inside /sdk/tools. I named the folder "Apps-stock
Check if Ubuntu recognises your phone:
Code:
./fastboot devices
Load the recovery image and mount the system:
Code:
./fastboot boot cm-hero-recovery.img
./adb shell mount /system
Replacing HTC's calendar:
Code:
./adb shell rm /system/app/Calendar.apk
./adb shell rm /system/app/Calendar.odex
./adb push Apps-stock/Calendar.apk /system/app/
I'll edit the thread, add details as I go on
Nice one!
Please keep us informed!
Thanks for this thread.
Post moved to a more appropriate topic :
http://forum.xda-developers.com/showthread.php?p=4477971#post4477971
Thanks for setting this thread up!
Firstly, you should probably say in the first post that everyone should do a Nandroid backup first - it's saved my bacon. Might be an idea to link to the files, too?
Second, I've got a problem trying to run this method. I removed the original calendar.apk and .odex without any problems, and copied the new one over, but on rebooting, it wasn't in the list of applications anywhere. I browsed there in Astro and opened the file, which gave me an option to install it - which then gave an error of "Calendar could not be installed on this device".
I'm running the MoDaCo 2.1 custom ROM and using the calendar.apk from this thread.
Thanks for your time!
fastboot
can you tell me where this fastboot command is located? I am using Ubuntu too, but can not find fastboot. What is it for by the way?
dragonflyFZX said:
can you tell me where this fastboot command is located? I am using Ubuntu too, but can not find fastboot. What is it for by the way?
Click to expand...
Click to collapse
fastboot and adb are executables you get from the Android SDK - see here.
This thread does require your phone to be rooted, though, which would require you to have already used adb at least once....
frandavid100 said:
........
Replacing HTC's calendar:
Code:
./adb shell rm /system/app/Calendar.apk
./adb shell rm /system/app/Calendar.odex
./adb push Apps-stock/Calendar.apk /system/app/
I'll edit the thread, add details as I go on
Click to expand...
Click to collapse
how about simply replacing those files using a file explorer (like linda)? possible, or would that screw up my system?

root Tattoo with Mac

Hey Boys and Girls,
where i can find an manual to root the tattoo with a mac?
sorry, i have search for this, but i cant find information for this
I don't thing that there is a difference.
As soon as you have SDK installed and adb works, the commands are the same.
hi,
i'm also doing all the rooting process from mac, just put the directory contain 'adb' shell into your home/user places and executing it with 'terminal'..
Same here, using a Mac ever since and also using it for Android development. Due to the underlying Unix core of OS X you just have to follow the steps as described for Linux. If it's just adb commands it's the same on every platform anyway.
You might want to add a
Code:
export PATH=${PATH}:/Users/yourusername/android.sdk/tools
to your .bash_profile file in your home folder so you don't have to cd to the SDK tools folder everytime. Happy rooting!
Mod. edit: not dev related, moved to general
Okay thanks for yours answers but i'm a newbie.
the background story is, I want to edit the boot.mp3. Because the startsound is really annoying
So i have download SDK, open the terminal and switch to usb-debbugging mode on my tattoo.
And now? sorry, I'm still missing a few knowledge
thanks for your help
well just use the various adb commands in Terminal Just type in "adb", press enter and you'll get a list of all possible commands. Assuming you've added the path to your sdk tools folder to your bash profile. Otherwise just drag & drop the adb binary from the tools folder onto your Terminal window, et voila.
The most used commands are probably push and pull where you can, well, push stuff to your phone or pull it to your computer.
So if you want to modify the boot.mp3 you would pull the original from the phone to your computer, modify it and push it back, overwriting the original file. In Terminal speak: ;-)
adb pull /system/media/bootscreen/boot.mp3
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Please note depending on the ROM you're using the paths may be different. To browse the device via Terminal type in "adb shell" and make a simple "ls" to list the directories, "cd" to change directories etc.
Or if you just want to use another mp3:
adb push /path/to/whatever.mp3 /system/media/bootscreen/boot.mp3
Again, on the Mac you can just drag & drop files onto the Terminal to get their full Unix paths like to your custom mp3
Thanks a lot. i love it its really simple
and now i have load and edit the the boot.mp3. But i can't push it to my tattoo, because i can only read but not write
I have tried to root my phone with "adb root" but it is the message "adbd cannot run as root in production builds"
Terminal: "adb remount", then push again
damn the next bad message "remount failed: Operation not permitted"
You need to root your phone first.
http://forum.xda-developers.com/showthread.php?t=637927
Okay i have executed the instructions. But I've stop at this part:
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
Yes i've root but i'cant download the "su binary" because its doesnt exist.
But its absolute essential to need the "su binary" to only copy the boot.mp3 to my phone? Or there is an other way? What are the commands to push the boot.mp3 back to may tattoo then i'm in the root mode like >> "#".
okay hope you understand me
You need "su" to do root stuff... no other way.
Download the package from 1 click root thread and find "su" there...
http://forum.xda-developers.com/showthread.php?t=644279
now, i have install the su binary. Then i does this command
user:~ user$ /Users/user/android-sdk-mac_86/tools/adb shell
$ /data/local/bin/su
#
Click to expand...
Click to collapse
And now? Is there a comand to push the boot.mp3 back to the phone in this mode >> "#" ?
I have try to open an new terminal window and type
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
but the answer is
failed to copy '/Users/android-sdk-mac_86/boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied
Click to expand...
Click to collapse
and adb remount doesnt work to
You also need tattoo-hack.ko file and do insmod tattoo-hack.ko to make /system writable.
Or even better... flash custom amon_ra recovery image and then a custom rom with all this already included.
Mine for example http://forum.xda-developers.com/showthread.php?t=702401
It doesnt have boot sound enabled
Okay thank you very much.
now it was successful

[Q] Editing Build.prop results in failure to boot [bricked]

As you may know, some Android games especially most Gameloft games are not compatible with the Kindle Fire. So in efforts to find a way to make certain Gameloft games to work such as Modern Combat 2 and Shrek Kart and others, I resorted to editing my build.prop in the systems folder to make my device compatible with the apps. So I copied the original build.prop file, renamed it, and saved it to my SD Card folder. I took the copy I made and I then replaced it with the build.prop from HTC Glacier. (I never knew what could possibly happen) So then to apply those settings you have to reboot the device. I rebooted the Kindle and now it won't boot up. It get's to the Kindle Fire screen when booting up but after several seconds it just shows a black screen. No physical damage has been incurred to it but I feel like my stupid mistake of modding the build.prop resulted in the Kindle Fire unable to boot up correctly. It also isn't recognized by the PC when I hook it up to a USB cable. So far I've found nothing that could help to solve this. I've seen a Factory Default Settings Cable which is a special cable to reverts the device to its factory default settings but I'm not too sure if that would work. I'm in desperate need of help as in I use my Kindle Fire for everyday work and play. Thanks.
EDIT: I've tried adb push and renaming and moving the build.prop into the /system/ but returns that it is a Read-File System Only. Also adb shell and su doesn't work as in it ends up with segmentation fault. I've tried to zergRush root it and permanently root it using KFU but it ends up with 'Cannot Access Package Manager. Is System running?' Also the mount -o rw,remount.....command doesn't work either as it says Permission Denied. All of this would be easy to accomplish if only it ADB allowed me to write onto the /system file.
EDIT**: The biggest issue I'm faced with is the permission settings that prevent my from editing anything. You cannot simply change it from RO to RW because apparently the ADB is not rooted. And I also can't root it because problems exist when accessing either Package Manager or Activity Manager. What I need is a way to access the /system files without a root (non-rooted). Either that or enable fastboot because I cannot access that either. On a reply on the second page is the resulting lines when changing bootmodes on the KFU.
Don't know how to fix your problem, but just wondering, did you just completely replace the kindle fire build.prop with the HTC glacier? Because you can't do that, it will, as you have learned, mess up your device.. Your supposed to edit the build.prop and just change a few things. Next time read up on the subject before deciding to mod the device you use everyday...
the cable you'r talking about is a "factory cable" it forces the kf to fastboot mode - it don't restore any settings !
you need fastboot mode to install fff (firefirefire - custom bootloader) and twrp (recovery)
do you allready have installed fff & twrp (or cwm) ?
if you have twrp installed and booted into then you have adb command available and can copy back the original build.prop
Did you remember to restore the read/write permissions to build.prop? It should be set to 644.
As already stated, your not supposed to replace the whole file, build.prop tells android which device you have, so now Android thought and configured itself to different hardware config. which is not available to it. Adb seems like the only option.
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
gococogo321 said:
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
Click to expand...
Click to collapse
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
You dont have access to recovery? Either TWRP or CWM?
daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
gococogo321 said:
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
Click to expand...
Click to collapse
Did you use the 'adb remount' command? Sometimes, when attempting to push a file to the system, I get the 'read-only file system' and I have to issue adb reboot followed by adb remount and then push the file again. It seems after a time the mount system as read write automatically goes back to read-only.
Sent from my ADR6400L using xda premium
Have you got TWRP or ClockworkMod?
Because you could flash a new rom then.
abd - root mode
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
sum1nil said:
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
Click to expand...
Click to collapse
Thanks but I have actually been running it from Administrator from the very beginning. I've used Kindle Fire Utility KFU and it says that ADB Server is Online and my Bootmode is 4000 but it says ADB root: No. And whenever I choose any bootmode whether it be Normal, Fastboot, or Recovery, it always shows this:
***********************************************
* Activating Normal (4000) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
1393 KB/s (1164225 bytes in 0.816s)
Error: Could not access the Package Manager. Is the system running?
Activating BurritoRoot...
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: permission denied
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
Same goes for the Temp Burrito Root and installing FFF and TWRP. It always shows something about cannot access Package manager. I have no clue what the Package Manager even does but apparently I cannot find a solution to that.
I think you need to get a factory programming cable like we talked about on gtalk. I'm confident that will fix this.
Sent from my DROIDX using Tapatalk
I used android commander for windows, mounted system in TWRP and used android commander to copy a new working build.prop to the right place.
With a cable from my htc desire.
would make a little test:
issue "adb shell"
if you get a error message your up to a factory cable because the system shell is messed up and you have no possibility to get to fastboot mode to install fff & twrp
if you get a $ or # prompt you can resume and try "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" to mount system in read/write mode
daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
hey, I've tried to remount my rooted galaxy y, fall in for same problem.but there show this message; "remount failed: Operation not permitted"
my device's usb debugging mode was off in last entire.
what I have to do now?
how did u edit build.prop in the first place if u don't have root and this might help
http://yaseminavcular.blogspot.com/2012/01/how-to-get-bricked-kindle-fire-back-to.html?m=1
Sent from my R800i using Tapatalk

Need System files from Kindle Fire HD 2013 model (no camera)

Hello Everyone. I bricked my device and need the following files to fix that. Please, can someone with a rooted device provide this files?
Thanks much:
/system/framework/services.odex
/system/app/DownloadProvider.apk
/system/app/DownloadProvider.odex
/system/app/DownloadProviderUi.apk
/system/app/DownloadProviderUi.odex
Thanks again
MarcoJoo said:
Hello Everyone. I bricked my device and need the following files to fix that. Please, can someone with a rooted device provide this files?
Thanks much:
/system/framework/services.odex
/system/app/DownloadProvider.apk
/system/app/DownloadProvider.odex
/system/app/DownloadProviderUi.apk
/system/app/DownloadProviderUi.odex
Thanks again
Click to expand...
Click to collapse
hey don't feel bad I need boot img and system img to get my running again....or I just need to pop it in the microwave and call amazon and ask for a new one and start over
My Kindle is alive. If someone need this files too, they can be found in the Update.bin at Amazons website.
@crzyjoker13. Good luck with your device.
Here you go, pulled straight from the latest update...
It's just the files you requested, the file structure should be correct.
crzyjoker13 said:
hey don't feel bad I need boot img and system img to get my running again....or I just need to pop it in the microwave and call amazon and ask for a new one and start over
Click to expand...
Click to collapse
You can get them from Amazon's website. That's your best bet at this time.
really lost
NighthawkXL said:
Here you go, pulled straight from the latest update...
It's just the files you requested, the file structure should be correct.
Click to expand...
Click to collapse
ok this is a start but how do I get them to /system/app
crzyjoker13 said:
ok this is a start but how do I get them to /system/app
Click to expand...
Click to collapse
Your need to get the device to be picked up by ADB and then push the files if your not able to boot into the actual system itself. Your have to ask someone else for the commands... but here's a snippet for services.odex the rest the files should be similar pieces of commands.
Code:
adb shell
su
mount -o rw,remount /system
chmod 777 /system/framework
exit
exit
adb push services.odex /system/framework
adb reboot
step in the right direction
NighthawkXL said:
Your need to get the device to be picked up by ADB and then push the files if your not able to boot into the actual system itself. Your have to ask someone else for the commands... but here's a snippet for services.odex the rest the files should be similar pieces of commands.
Code:
adb shell
su
mount -o rw,remount /system
chmod 777 /system/framework
exit
exit
adb push services.odex /system/framework
adb reboot
Click to expand...
Click to collapse
well hey this is a step in the right direction but all I need now Is to gain read write acess to /system and system/app abd I should bea able to push the old files back...my problem lies in the fact that es explorer tried to update and it messed up so I went to remove and just install the new version at the same time I was following the directions to put play market on the dev so now I can download and I have no file explorer
or if anyone know how I can push and execute an apk to the kindle I would be happy
thanks in advance
crzyjoker13 said:
well hey this is a step in the right direction but all I need now Is to gain read write acess to /system and system/app abd I should bea able to push the old files back...my problem lies in the fact that es explorer tried to update and it messed up so I went to remove and just install the new version at the same time I was following the directions to put play market on the dev so now I can download and I have no file explorer
or if anyone know how I can push and execute an apk to the kindle I would be happy
thanks in advance
Click to expand...
Click to collapse
I was having the same problem as you are and was able to fix it by doing the following.
Download and extract the files NighthawkXL has provided.
From within the folder that you saved the files run command and do the following
adb shell
su
mount -o rw,remount /system
chmod 777 /system/framework
exit
exit
adb push services.odex /system/framework
adb push DownloadProvider.odex /system/framework
adb push DownloadProviderUi.odex /system/framework
exit
adb shell
su
mount -o rw,remount /system
chmod 777 /system/app
exit
exit
adb push DownloadProvider.apk /system/app
adb push DownloadProviderUi.apk /system/app
adb reboot
I think this will solve your problem with the downloads not working. Please keep in mind I have small amount of knowledge when it comes to rooting, but figured that it couldn't do more damage to it since it wasn't working.
LinearEquation said:
You can get them from Amazon's website. That's your best bet at this time.
Click to expand...
Click to collapse
can you provide a link to the system images please
thanks cant seem to find them
davethebrave14 said:
can you provide a link to the system images please
thanks cant seem to find them
Click to expand...
Click to collapse
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin
Just downloaded .bin gonna check this out also. I didn't brick mine its usable but I screwed it up trying to take things off to get more memory and easier on battery. Runs ok now but I took off the system keyboard thinking the android keyboard file would be it the asop or whatever. So had to add Google keyboard which is better and the main navigation is gone with the back and menu key. ROFL. Using all in one gestures and omega status bar as a rig lmao.
adb install package.apk works fine after adb start-server with linux.
Theres app in 1 mobile market for moving .apk to /system/app folder.

Categories

Resources