Script to mount shares on boot using install-recovery.sh - Fire TV General

Currently I'm using this cmd through adb each time I restart my FireTV "mount -o noperm,unc=........."
to mount my shares from my NAS locally on XBMC
I saw a method that uses system/etc/install-recovery.sh
to create a mounting point at boot time but I can't find that file at that location
and Idk if I can just adb push to create it and that's it, it would be called at boot
If someone with more experience could help me on this I would really appreciate it

Just create and chmod 755

Related

Rooted Hero Fails adb remount, can't move files from SD

I rooted my hero last night and tried out a few different ROMs but eventually decided to revert to stock and make some manual changes. I used nandroid to restore to just after the root (1.56.651.2). I was able to remove some apps using adb, but the adb remount command fails (permission denied), and I'm unable to push a new bootscreen on to the phone. I also tried a Root File Manager and pre-kitchen as alternatives for the bootscreen, and neither one works. The Root Manager won't paste the files from SD into /system/media/ and pre-kitchen just reboots the phone.
Any suggestions?
Any chance this has something to do with downloading only up to SDK Platform 1.5? I'm at a total loss. I RUU'd my phone, did a clean root at startup using adb shell, and I still have the same problem. The adb remount command won't work, and I can't push anything into the system directory. For what it's worth, when I still had Root Manager installed I was able to toggle RO R/W in any directory with no problem, and I could move files around within the ROM... but I couldn't move anything into it from the SD. I'm new at this, so I have no idea what the problem might be. Anyone else had this problem or have any suggestions?
If anyone else runs into this problem, this solution worked for me:
adb shell
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
Restore modified permissions when done.
Though I'm still not sure why this is necessary in place of adb remount.
I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
dametzg said:
I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Thanks... didn't realize stock wouldn't accept adb remount. If I use the above line from within shell, that doesn't help me push anything on to the phone though... so I needed to enable global permission and then do the push. Oddly enough I tried the same approach last night using Root Manager, and the transfer from SD still failed, even after I applied 777 to the dir I was trying to modify. The current solution may be kind of tedious, but at least it works.
you really shouldn't do 777 on your filesystem, ANY app can then write to your system, overwrite things, or install malicious code. Just remount manually and you should be able to push anything you want, just remember that w/ the stock rom you also don't get a full busybox either.
I'm not positive, but I would think after you remount, you should be able to "adb push" to /system. I suppose it might be specific to that shell, but I would think not.
You just may have to do it once each time you boot your phone.
Edit - err nevermind... you're having permission errors.... um... change adbd on the phone to run as root? not sure how off the top of my head...

[Q] 1st update froyo

should i flash it. i dont have root
WOW! i cant believe no one has replied to you.
if you take a look at the first post with the topic
[ROM] Official AOSP 2.2 OTA
but you mentioned you dont have root. so try installing alogcat from the marketplace and capture the whole deal. then you can email directly from the app.
logcat isnt going to do much, it prefetches the files, need to pull the update.zip from adb
ok, so i havnt gotten the notice yet.
but need a bit of help prepping for when i do.
i have the android sdk installed on my desktop, and can create a virtual device etc...
but when i open the cmd prompt and try to run adb devices it says it is populating a list but i see no results or no file created.
so i tried just running adb logcat and it stops at waiting for device.
any pointers. im running win7x64 ultimate
well, i screwed it up. i removed the usb drivers and set it to debugging mode and got it working.
so i am able to run adb shell etc...
once i get the notice ill be ready to do an adb pull
adb shell
su
cd /cache/
ls
adb pull /cache/<package_name>.zip .
sepiid said:
well, i screwed it up. i removed the usb drivers and set it to debugging mode and got it working.
so i am able to run adb shell etc...
once i get the notice ill be ready to do an adb pull
adb shell
su
cd /cache/
ls
adb pull /cache/<package_name>.zip .
Click to expand...
Click to collapse
but how do you know the new radio and spl update name?
you should get that by running su then "cd /cache/ ; ls"
right now i have
download-1.apk
downloadfile.apk
recovery
lost+found
so after it is precached i run that "cd cache/ ; ls" i should have another file or two in there
that would be the file you run adb pull /cache/*.*
a tad bit of help, as a test i am trying to do
adb pull cache/downloadfile.apk d:\
but i get
remote object 'cache/downloadfile.apk' does not exist
i also tried adb pull /cache/downloadfile.apk d:\
and get the same.
edit:
tried doing a adb push
D:\android-sdk-windows\tools>adb push d:\test.txt /cache
failed to copy 'd:\test.txt' to '/cache/test.txt': Permission denied
so i dont have permission to put anything there, which means i likely dont have permission to pull from there
D:\android-sdk-windows\tools>adb pull /cache/downloadfile.apk d:\
remote object '/cache/downloadfile.apk' does not exist
so i opened another cmd prompt and and did an adb shell
su
and i am su
so while the other window was open and i was su i tried the same commands again and got the same results.
edit2:
D:\android-sdk-windows\tools>adb shell ls /cache
opendir failed, Permission denied
so it is definately a su/permissions issue.
Are you rooted? If not use Universal Androot.
*anticipation*
sepiid said:
a tad bit of help, as a test i am trying to do
adb pull cache/downloadfile.apk d:\
but i get
remote object 'cache/downloadfile.apk' does not exist
i also tried adb pull /cache/downloadfile.apk d:\
and get the same.
edit:
tried doing a adb push
D:\android-sdk-windows\tools>adb push d:\test.txt /cache
failed to copy 'd:\test.txt' to '/cache/test.txt': Permission denied
so i dont have permission to put anything there, which means i likely dont have permission to pull from there
D:\android-sdk-windows\tools>adb pull /cache/downloadfile.apk d:\
remote object '/cache/downloadfile.apk' does not exist
so i opened another cmd prompt and and did an adb shell
su
and i am su
so while the other window was open and i was su i tried the same commands again and got the same results.
edit2:
D:\android-sdk-windows\tools>adb shell ls /cache
opendir failed, Permission denied
so it is definately a su/permissions issue.
Click to expand...
Click to collapse
Here do this:
First if you have root, open up terminal or cmd prompt if you are on windows:
adb shell
su
mount -o rw,remount yaffs2 /cache
chmod 777 /cache
that will change the permissions allowing for read and write.
Now exit out of shell and just adb pull /cache/
That will pull everything out of the cache partition.
BAM!!! perfect!
i new it was permissions related. just couldnt figure out the "mount -o rw,remount yaffs2 /cache" part. might i ask you to break that down for me? at least the yaffs2 part.
thanks!
so once the update hits i am ready to grab the files.
callmeradical said:
Here do this:
First if you have root, open up terminal or cmd prompt if you are on windows:
adb shell
su
mount -o rw,remount yaffs2 /cache
chmod 777 /cache
that will change the permissions allowing for read and write.
Now exit out of shell and just adb pull /cache/
That will pull everything out of the cache partition.
Click to expand...
Click to collapse
So the YAFFS2 part of the code I put up there is designating the file system in which we are reading/writing.
YAFFS2 is the most popular and widely used format for flash memory.
please allow me.
yaffs2 is a filesystem type. /cache is of course the directory. -o is for option.
rw: read/write
remount: remount /cache again with new option.
sepiid said:
BAM!!! perfect!
i new it was permissions related. just couldnt figure out the "mount -o rw,remount yaffs2 /cache" part. might i ask you to break that down for me? at least the yaffs2 part.
thanks!
so once the update hits i am ready to grab the files.
Click to expand...
Click to collapse
Oh yeah and BTW, you can change the permissions back if you want after your done, otherwise I believe you can just reboot the phone and it fixes it, not entirely sure, I was trying to rewrite my default.prop to get adb remount to work with stock 1.6 rooted, but I am getting and access denied issue.
perfect was about to ask what the -o was but i tried mount --help and mount -h both resulted in nothing. then you reply sharpt71
thanks again all.
i am now ready to pull the update and upload once i get the update. hopefully soon!
Rather than the remounting and chmoding so you can adb pull.
You could probably get away with
Code:
su
cp /cache/<whatever> /sdcard
Then mount the SD card or put it in a card reader.
SilverSurfR said:
Rather than the remounting and chmoding so you can adb pull.
You could probably get away with
Code:
su
cp /cache/<whatever> /sdcard
Then mount the SD card or put it in a card reader.
Click to expand...
Click to collapse
You probably could I just know that this is a sure fire way to grab everything in cache directly to the machine, otherwise if you aren't next to a machine you could probably do a copy like you said.
My 2nd update failed, do you guys think the files are still in my cache?

Help ADB Push to /System Folder

Hope this is the right place to post this.
My Atrix is rooted stock 1.83 .
I'm trying to "adb push" some OGG files to "/system/media/audio/" to add-to and replace some of the existing system sounds, especially that bloody annoying keypress (typewriter) sound, but I'm getting the following error (which makes sense):
Read-only file system
Tried using Root Explorer, same issue...again makes sense since its mounted as Read only on boot.
I tried booting into recovery mode, but I can't access the phone via ADB at all, even with USB Debug enabled. I also tried "adb remount" command, no luck either. I get an error "operation not permitted".
So, does anyone know the correct sequence of commands I need in ADB to remount the Atrix /system folder as RW??
What I have been doing is using adb push to the /sdcard then using adb shell then su then
mount -t rfs -o remount,rw /dev/stl5 /system
Then cp /sdcard/whatever /system/media
Sent from my MB860 using XDA App
EDIT: im at my computer now so I can write this easier to understand, lol
Lets say the file you want to change is called whatever.ogg
Code:
adb push whatever.ogg /sdcard/whatever.ogg
adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cp /sdcard/whatever.ogg /system/media/audio/notifications
when you access root explorer, does it let you know that it has been granted supervisor privilages? Does it give you the option to change from read to write? what did you use to root? I had to run the original Aroot three times before if finally gave me root.
You're the best, worked perfectly Can't believe that hideous typewriter sound is gone, it only took me 1.5 years as an Android user to finaly say enough is enough. Whomever thought it was a good idea to mimic the sound of an 1800's typewriter on a 21st century device needs to be fired.
Thanks again.
aver2one said:
What I have been doing is using adb push to the /sdcard then using adb shell then su then
mount -t rfs -o remount,rw /dev/stl5 /system
Then cp /sdcard/whatever /system/media
Sent from my MB860 using XDA App
EDIT: im at my computer now so I can write this easier to understand, lol
Lets say the file you want to change is called whatever.ogg
Code:
adb push whatever.ogg /sdcard/whatever.ogg
adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cp /sdcard/whatever.ogg /system/media/audio/notifications
Click to expand...
Click to collapse
i need help
im using a clone samsung galaxy tab2.tried to change the system font with root browser and it bricked.the phone dont have cwm so i didnt back up my rom.any command in adb that can be used to change the font folder
Obiechina said:
im using a clone samsung galaxy tab2.tried to change the system font with root browser and it bricked.the phone dont have cwm so i didnt back up my rom.any command in adb that can be used to change the font folder
Click to expand...
Click to collapse
Well congrats! that was the dumbest thing ever. NEVER attempt something like that unless you have CWM or equivalent installed, have a backup, and know what you are doing.
Have you tried to read your device's xda forum?
Please Help
Hahaha, can you help me?
i want to change my /system/framework folder by using the POWER and UP volume keys
i had a backup of my system/framework in my SD..
What should i do?

Auto-mounting CIFS Shares

I couldn't find any threads on this, sorry if it's been asked before.
I can mount CIFS/NFS shares fine through CIFS Manager, but it doesn't auto-mount those shares on boot.
I'm trying to find a way to do this on boot. I can't find any sort of fstab from looking around that I could use for this.
I find some information that suggested that you can run script commands on boot if they're located at /data/local/userinit.sh So I attempted to put the mount commands in there.
userinit.sh said:
#!/system/bin/sh
mount -t cifs //192.168.1.147/comics /mnt/cifs/comics -o user="joe"
mount -t cifs "//192.168.1.147/collen's movies" /mnt/cifs/avis -o user="joe"
Click to expand...
Click to collapse
(yeah, I know "collen" is misspelled, but it is on the share)
both those commands *will* mount when I do them from terminal after creating the /mnt/cifs/comics and /mnt/cifs/avis directories... For some reason though, they get removed on each boot... so I suspect that maybe that's preventing the script from mounting them?
Anyone know of a way to do this?
You might try adding:
mkdir -p /mnt/cifs/comics
mkdir -p /mnt/cifs/avis
to the script before the mount commands, to make sure the mount points are there after a reboot. It might also be that the userinit.sh script is not being run as the superuser, which may be necessary for the mount command to work.
Actually, it occurs to me that I'm a bit of an idiot for thinking this would work...
I doubt it would have a wifi connection when any boot scripts get ran... so a CIFS mount shouldn't work at that point anyway.

GUIDE - How to install custom full screen boot animations on rooted Fire TV Stick

Hi,
I started playing around with custom boot animations on my rooted Fire TV Stick and thought I'd share the process with everyone. Firstly I would like to note that I am using Ubuntu in this guide.
First download a custom boot animation (bootanimation.zip) from the Internet or make your own. The one I have used in this example is a Dark Knight one downloaded from the Internet and I've set the resolution of the image to 1080x1920 (HxW) and the fps at 30.
Then you need to connect to the rooted Fire TV Stick via adb using Terminal using the adb connect command:
adb connect <IP of Fire Stick>
Your command should look something like this:
Code:
adb connect 192.168.0.8
Now you need to send the bootanimation.zip file to the Fire TV Stick using the adb push command. This may take some time depending on the size of the new bootanimation and the strength/speed of your network.
adb push <source-of-new-bootanimation.zip> /sdcard/
So your command should look something like this:
Code:
adb push /home/ian/Desktop/bootanimation.zip /sdcard/
(Optional step) Backup original bootanimation.zip by using the abd pull command:
adb pull /system/media/bootanimation.zip <directory-to-save-backup>
So the command used should look like:
Code:
adb pull /system/media/bootanimation.zip /home/ian/Documents/
You then need to start an adb shell by using the command:
Code:
adb shell
Get root access in the shell by using the su command:
Code:
su
Then you need to use the mount command to get a list of the mounted partitions so we can copy the address of the system partition:
Code:
mount
Once the mount command has returned the mounted partition list then need to find the system partition, mine is listed as:
/dev/block/platform/sdhci.1/by-name/system /system
Click to expand...
Click to collapse
Copy that address and then remount the partition as read/write instead of read only with the following command.
mount -o rw,remount -t ext4 <address of system partition>
The complete command should look something like this:
Code:
mount -o rw,remount -t ext4 /dev/block/platform/sdhci.1/by-name/system /system
Once you have remounted the drive you need to remove the original bootanimation.zip using the rm command:
Code:
rm /system/media/bootanimation.zip
Now you have to copy the new bootanimation.zip file that was sent over to the sdcard with the following command:
Code:
cp /sdcard/bootanimation.zip /system/media/
Now the custombootanimation.zip file has been copied over we need to set the correct file permissions using the chmod command:
Code:
chmod 0644 /system/media/bootanimation.zip
Once that has been completed you can then remount the system partition as read only by using the following command:
mount -o ro,remount -t ext4 <address of system partition>
Your complete command should look like this:
Code:
mount -o ro,remount -t ext4 /dev/block/platform/sdhci.1/by-name/system /system
(Optional step) You can then remove the copy of the bootanimation.zip file from the sdcard by using:
Code:
rm /sdcard/bootanimation.zip
Then type exit three times and reboot your Fire Stick to see your shiny new boot animation
I have put up a video on YouTube named:
Custom boot animation running on rooted Fire TV Stick.
Click to expand...
Click to collapse
This video shows the end result in action, however as I am a new user here it will not allow me to share the link or embed the video.
Great work. Is there any way to get rid of the initial Amazon display as well?
Initial boot logo replacement
Inspex said:
Great work. Is there any way to get rid of the initial Amazon display as well?
Click to expand...
Click to collapse
I have been wondering this myself so I'll probably have a look into this during the week to see if I can either remove or replace the intial amazon logo. I'll update the original post with my findings once I've had chance to have a look
Thanks for the positive feedback too
witch Size are needed for custom Bootanimation??
Have you tested running an mp4 video file as boot animation at all?
MetaIIica said:
witch Size are needed for custom Bootanimation??
Click to expand...
Click to collapse
I used the resolution 1080x1920 (HxW) for the Batman one shown in my YouTube video.
Inspex said:
Have you tested running an mp4 video file as boot animation at all?
Click to expand...
Click to collapse
I haven't tried using mp4 video files because I tried to replicate the format used in the original amazon one which used *.jpg files in the bootanimation.zip file.
I will more than likely be experimenting with other file formats though and will keep this post updated with any results over the next week or so.
this is great news, ive been wondering if this was possible but was too scared to test it?
Heres the link if anyone wants to see it?
https://www.youtube.com/watch?v=Bh2bH7OJGys
Have a bootloop >.<
bootloop help
Xperience Z said:
Have a bootloop >.<
Click to expand...
Click to collapse
I've read your post in the other thread and if you're still having the boot loop I'd try the following things:
1st you need to make sure you're correctly rooted by typing the command:
Code:
su
you should have the following reply:
Code:
[email protected]:/ $ su
[email protected]:/ #
If your reply looks anything other than the example above, then you need to run the Kingo Root Windows app and re root the Fire Stick.
Once you have done this you can then try the following things to fix the bootloop:
1) Delete the incorrect bootanimation.zip file
connect the Fire Stick to the computer and connect via adb, then open adb shell and type the following commands:
Code:
su
Once again at this point, double check that you get the same reply mentioned above
Code:
mount -o remount,rw /system
Code:
rm /system/media/bootanimation.zip
Code:
mount -o remount,ro /system
Code:
exit
Code:
exit
Once you have completed that, reboot the Fire TV Stick and see if the bootloop has gone. If not then try the step below.
2) Restore a previous firmware by following the guide below from XDA member sconnyuk:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298
In my opinion the first method most likely won't work but the second method should work in theory.
Hope this helps
Will it do any harm by simple removing the original boot animation and not replacing it with a new one? Or will it still take the same amount of time for the firetv stick to boot up?
Inspex said:
Will it do any harm by simple removing the original boot animation and not replacing it with a new one? Or will it still take the same amount of time for the firetv stick to boot up?
Click to expand...
Click to collapse
Hi,
You can remove the original bootanimation.zip but it will only revert it to a default/hidden "fire" logo boot animation instead. However it does not improve the boot up speed of the Fire TV Stick.
When I try to run
cp /sdcard/bootanimation.zip /system/media/
It tells me no such file or directory. What's going on? The file is in the sdcard folder..
Hello,
i have create my own bootanimation for my firetvstick, because the bootanimation is not working the stick is in a bootloop.
Here is my link for my bootanimation.zip https:// www .mediafire .com/?i7rxtfwt74gxa5a
I don't know what is wrong. I hope someone can help me.
Thanks!

Categories

Resources