Hi,
i can't get a folder to mount on Android N while. On MM i just did it with init.d
Code:
mnt_boot
Code:
#!/system/bin/sh
sleep 10
mount -o bind /mnt/media_rw/6EF2-A903/.WhatsApp /data/media/0/WhatsApp
That worked well, but on N i can't get it to work. Anyone has a idea what's going on there or if it's a bug?
MorpheusKiller said:
Hi,
i can't get a folder to mount on Android N while. On MM i just did it with init.d
Code:
mnt_boot
Code:
#!/system/bin/sh
sleep 10
mount -o bind /mnt/media_rw/6EF2-A903/.WhatsApp /data/media/0/WhatsApp
That worked well, but on N i can't get it to work. Anyone has a idea what's going on there or if it's a bug?
Click to expand...
Click to collapse
Hi,
same problem on cm14.1. Cause of this seems to be different name spaces.
Start terminal su and you will see the mount.
I've no idea how to switch the name space while executing the init script.
Related
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...
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.
Hi,
I was using Gscript with a mount script to bind my Gameloft game data folders on external USB disk to the original place on the internal SD card.
a sample script is like:
Code:
mount -o bind /storage/usbdisk/N7/Android/Data/com.gameloft.android.ANMP.GloftN3HM /sdcard/Android/data/com.gameloft.android.ANMP.GloftN3HM
However, after updating to Android 4.2, I lost this capability. The mounts are only available within the context of the app that I mount.
When I leave the app (Gscript), and open a terminal emulator, I see the mount (binding) is gone.
Is there a solution to this on Android 4.2 ?
Thanks.
Anybody who can help with this ?
thx.
This should be the same solution as with cifs and others...
http://forum.xda-developers.com/showthread.php?t=2065856
good question,i opened a similar 3ad in past days but no reply..HEREgscripts system and directory bind aren't working anymore..i think it's the changed mount points or how android manage them..
vorcers,
thanks for this information. But what do you mean by 'Stickmount writes the shell-commands in "/system/bin/debuggerd"' ?
/system/bin/debuggerd seems to be a binary file. How can we write shell commands in it ?
Thanks.
..
mrmrmrmr said:
vorcers,
thanks for this information. But what do you mean by 'Stickmount writes the shell-commands in "/system/bin/debuggerd"' ?
/system/bin/debuggerd seems to be a binary file. How can we write shell commands in it ?
Thanks.
Click to expand...
Click to collapse
any ideas ?
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!
Hello fellow xda'ers,
A few weeks I am experiencing a problem with my moto x style. The problem is that i don't have access anymore to my system folder. I have full root access, I can use rooted apps, but i can't switch my file system to r/w. Also when I boot into recovery I can flash roms etc, they are fully working, but once again, no system access. Also when I try to mount the system folder in recovery it seems it won't stick. Also when I use root explorer it says it switched to r/w but in fact it is r/o..
Can someone please hint me out what I could do to fix this problem?
Thanks in advance,
Bump
Have you tried something like this in terminal as root, or via ADB root?
Code:
mount -o rw,remount,rw /system
Then for r/o...
Code:
mount -o ro,remount,ro /system
quakeaz said:
Have you tried something like this in terminal as root, or via ADB root?
Then for r/o...
Click to expand...
Click to collapse
Thanks for your reply. But i still can't get system access.
bartjeh1991 said:
Thanks for your reply. But i still can't get system access.
Click to expand...
Click to collapse
Did you receive an error running the command? You are root, correct? Possibly just use:
Code:
mount -o remount,rw /system
Then run...
Code:
mount | grep system
Mine is read-only, but this should tell you if yours is rw or not.
Code:
u0 a114 clark:/ mount | grep system
/dev/block/bootdevice/by-name/system /system ext4 [B]ro[/B],seclabel,relatime,data=ordered 0 0
quakeaz said:
Did you receive an error running the command? You are root, correct? Possibly just use:
Then run...
Mine is read-only, but this should tell you if yours is rw or not.
Click to expand...
Click to collapse
I get this message everytime i run the commands you give me.