Hi,
i temp rooted my Flayer 32GB 3G, and i tried to remount the /system partition to rw. It gives me no error but the /system partition stays ro. I know at this point it does not make lot of sense because it`s only temp root, but i wondered if this is only not working for me or if i do something wrong.
I used adb to copy busybox to /data/local/tmp and ran busybox -o rw,remount -t ext4 /dev/block/mmcblk0p25 /system and also tried to just ran busybox -o rw,remount /system.
If anyone has tried to do this, he maybe can say something.
regards
Ok, i did the temp root again because i rebootet, got the exploit area 38126600:a00 and then i could successfuly remount /system rw
using which tool you temprooted ? and possible to replace system files or install another ROM ?
Got my 32GB/3G o2 Germany branded Flyer also temp rooted, exploit found at 38125600:1a00. Remount of /system rw succeeded
Bashar . said:
using which tool you temprooted ? and possible to replace system files or install another ROM ?
Click to expand...
Click to collapse
Please look into the dev section of the flyer forum. Elim explains everything very well there. The fre3vo tool is used.
I'm trying to push files to /system via ADB. However I'm having problems (getting permission errors). I am running Eclipse 2.0.2, so yes, my phone is rooted, I have su and busybox.
Phone is connected to PC and is set as "USB Mass Storage".
USB Debugging is ON
Here is my CMD log:
Code:
C:\android-sdk\tools>adb remount
remount failed: Operation not permitted
I tried to remount and it failed
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to
'/system/myfile.apk': Read-only file system
I tried to push, and got a READ-ONLY FILE SYSTEM error (keep this in mind)
Code:
C:\android-sdk\tools>adb shell
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
I try to push inside of ADB shell. Nothing again...
Code:
$ su
su
# mount -o remount,rw /dev/block/mtdblock4 /system
mount -o remount,rw /dev/block/mtdblock4 /system
# exit
exit
I go into SU and attempt to remount the /system
Code:
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
$ exit
exit
I go back up to ADB shell and try to push again... same error as before
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to '/system/myfile.apk': Permission denied
I go back to the main command line and try to push again. This time I get PERMISSION DENIED. This error is different than before.
Any help on the matter?
I've read about ro.secure needing to be set to 1, but I need to edit the boot.img in order to do this, correct? Does that require an unlocked bootloader? Is root ADB even possible on the DX2.
Thanks!
I am no expert (don't even know if i know enough to b called a newb) but maybe try a root explorer. I use es file explorer because it's free. In settings check root explorer and mount file system. I received similar errors and this solved my problem.
Sent from my DROID X2 using XDA App
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
wesf90 said:
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
Click to expand...
Click to collapse
I was using adb also and had similar problems. After i changed those settings i was able to push a file. I had to have system mounted.
Sent from my DROID X2 using XDA App
No luck on my end :/
Sorry i couldn't be more help. I am new to adb and may have done more to get it working. I'm sure there's someone else around here that can help u out.
Sent from my DROID X2 using XDA App
Make sure there are no spaces in the file path to your android-sdk folder. Can't say if this is your issue but its worth a shot as it has always caused weird problems with android development since day one.
Sent from my DROID X2 using Tapatalk
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
CadenH said:
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
wesf90 said:
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
Click to expand...
Click to collapse
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
ashclepdia said:
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
Click to expand...
Click to collapse
Thanks for that! It's not quite what I'm aiming to eventually do, but did give me more insight on how the whole adb/shell/su systems work. From inside of su, I was able to mount the /system as RW, however I'm only able to do this from inside of SU. I want to be able to do this from the initial CMD so that I can ADB PUSH from my computer to the phone.
Here's my latest log:
Code:
C:\android-sdk>adb shell
[[TRYING TO MOUNT FROM ADB SHELL]]
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
[[TRYING TO MOUNT FROM ADB SHELL USING BUSYBOX]]
$ busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: permission denied (are you root?)
[[GO TO SU]]
$ su
su
[[MOUNTING AS RW SUCCESSFUL]]
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
[[COPYING A FILE INSIDE /SYSTEM SUCCESSFUL]]
# cp framework/framework-res.apk framework/framework-res-test.apk
cp framework/framework-res.apk framework/framework-res-test.apk
[[REMOUNTING /SYSTEM AS RO]]
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
[[ATTEMPTING TO COPY AGAIN, FAILED]]
# cp framework/framework-res.apk framework/framework-res-test2.apk
cp framework/framework-res.apk framework/framework-res-test2.apk
cp: can't create 'framework/framework-res-test2.apk': Read-only file system
#
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Maybe its because im tired but im confused as to why it wont let you push your files if you have remounted as rw. At that point it should be cake. You gained access to system by remounting it as rw successfully already.
Sent from my DROID X2 using xda premium
wesf90 said:
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Click to expand...
Click to collapse
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
I'm no expert in ADB, but I had run into the same issue as you and for me the fix was to go into ADB SHELL , then type SU to get SU access, then type exit twice to get out of shell completely. Then I tried pushing the APK and it worked fine with no read only errors.
This worked for me on my SGS2, could work for you ! Goodluck !
Come to IRC and I can help you with this. http://webchat.freenode.net Come to the #cm7dx2 channel. I'm usually there... Look for the nick(s) Moon|Work|(something), Moon|Home|(something), or MoonShadow-NM. If the (something) says Busy, I might not answer right away. If it says Away, I'm away from the keyboard and you won't receive a response until I return.
Ciao!
Any update
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
I've got a better idea to fix your issue brotha!
From my nexus tappin the talk
<edit post successful>
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
From my nexus tappin the talk
<edit post successful>
jamesh0317 said:
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
Click to expand...
Click to collapse
This won't work with Eclipse since it's not using 2nd init. I asked this question in the Eclipse forums and Nitro responded with the following:
Not without using 2nd init. All of that works due to being able to load its own init.rc which starts services and passes parameters, etc.. during boot time. It is possible to make a stock rom use 2nd init. CM9 will not even have root enabled by default. The only other way to push stuff is to enable root shell prior to pushing.
Click to expand...
Click to collapse
I know that CM7 allows using the adb remount, but that's because it's using 2nd init. I had also asked the question about why CM7 defaults to root shell when you adb shell into it and that's why he mentions how CM9 won't have root enabled by default.
The way I push to Eclipse is to run root explorer on my phone and mount the directory r/w. Then, I can use "adb push" to the phone.
ashclepdia said:
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
Click to expand...
Click to collapse
I think I may have tried that in one of my iterations. Originally I had it rooted with One-Click and then I was having issues with the 2.3.5 OTA update (quickoffice.apk) and at this point I've SBF'ed and rooted it probably 5 times this week so far. Rooted with both One-click and zergRush at various times. Actually I think every time except this last time has been with one-click. So I don't think that has seemed to make a difference for me so far. I can try it again, but if there's any other advice to throw out in the mean time, I'll take it.
Alternatively, I may take the new phone (the first replacement they sent had 2.3.5 on it, but a bad menu key causing the phone to flip out), load Titanium Backup on it, backup all the system apps and restore them to my original phone. Worst case is I have to SBF it again. But that seems like a logical process since I will have two phones available.
I am trying to re-root after the 2.3.6 update, I did not remove root before the OTA update.
I made sure USB connection was set to none, and USB debugging was on. I see that is saying that I am out of space, problem is I don't know how I could possibly be able to be out of space, I have plenty of room on both the internal and external cards. Below is the output with the error. Any help would be appreciated. Thanks.
C:\moto-fastboot-win32>moto-fastboot.exe flash preinstall preinstall.img
sending 'preinstall' (30720 KB)... OKAY [ 2.682s]
writing 'preinstall'... OKAY [ 3.447s]
C:\moto-fastboot-win32>moto-fastboot.exe reboot
rebooting...
C:\moto-fastboot-win32>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
cp: write error: No space left on device
[email protected]:/#
same thing happened here
same here
i have the same problem, do i reboot?
any update on this?
Hi there... I had the same issue when I installed the 2.3.6 ATT OTA update when I lost root... I tried RootKeeper application but it didn't work after the OTA installation. I looked for information about this error but didn't find much or complex solutions as to free space from that system dir... so then I thought about if the copy command would have an overwrite option and it did, so I tried it and it worked for me.... I'm rooted again!
I see this is an old post but in case you still need it, it may help you too. I used line bleow to overwrite and the rest you know it.
cp -f /preinstall/su /system/bin/su
by the way, I got an error in the line "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk" telling me that the application or file already existed as I already had superuser installed... I guess it should work without re-installing it, in my case the reinstallation was to a different superuser version... anyway if you want to skip that error and proceed with the re-installation you can use option -r as shown in line below.
PATH=/system/bin:$PATH pm install -r /preinstall/Superuser.apk
cheers!
avelezmtz,
Thanks for the idea, but it did not work for me, I still got the no space left error. Do you know if there a way to delete the SU file and then try to copy it? Thanks
I tried the, PATH=/system/bin:$PATH pm install -r /preinstall/Superuser.apk, command and it was able to reinstall the apk which it never has before so that's good, but it's still not rooted.
If anyone else has any ideas let me know. I am thinking about backing everything up and doing a factory reset and seeing how that goes.
First... as suggestion, if you will be playing deleting files, ensure you have clockworkmod backup or anyother way to restore a previous backup just to be safe.
I think rm command should delete su, but I'm not sure if it would help since the error is not a permissions error, so the ovewrite option should work if the space in the system dir is enough... if you still wanna try the removal of su I think line below will do it.
rm /system/bin/su
Another option I saw somewhere it was about freeing up space by deleting apk files from /system/app dir which is mounted in the same volume, however it would depend on how big those files are. Of course you should back them up first maybe copying them to /sdcard/ for instance. In the post I saw that they removed swype.apk and that was enough for them but in my case it didn't help and as the ovewrite worked I didn't try removing more apps.
If you want to know the space on that dir you can use
df /system/bin/
avelezmtz,
Thanks for all the help, I am now rooted again!!
Using your suggestion I deleted Superuser.apk and Swype.apk from the /system/app directory.
After that I was able to rerun all the commands and get root back. Thanks for all the help, I appreciate it. Sure beats wiping the phone and starting all over again.
I have a problem with my Yu Yureka which running on CM 12.1 and Rooted (su) twrp
1. When I was trying to to flash any zip file like CameraNext Mod, it was flash successfully. After reboot the system, I can't find the CameraNext Mod, it was not in menu.
2. Sometime when i tried to flash other zip file like xposed framework, it was not completely installed. there was error and the error message was " cp:write error: no space left on device"
plz help me with right direction..
Hi guys
I need some serious help with my phone... i accidently edited build.prop and now my phone doesn't boot anymore.
I need to push a new build.prop file to my phone.. I can get into recovery mode on the phone and I've managed to pull build.prop from the phone but I cannot push it back due to "Permission Denied"
Does anyone know a adb command or application or something that can help me sort this out?
My phone is the Huawei Ascend P2
Thanks guys.
jdcrispe95 said:
Hi guys
I need some serious help with my phone... i accidently edited build.prop and now my phone doesn't boot anymore.
I need to push a new build.prop file to my phone.. I can get into recovery mode on the phone and I've managed to pull build.prop from the phone but I cannot push it back due to "Permission Denied"
Does anyone know a adb command or application or something that can help me sort this out?
My phone is the Huawei Ascend P2
Thanks guys.
Click to expand...
Click to collapse
If you try and mount the USB Storage ?
UltraWelfare said:
If you try and mount the USB Storage ?
Click to expand...
Click to collapse
How do I do that?
adb mount /sdcard?
jdcrispe95 said:
How do I do that?
adb mount /sdcard?
Click to expand...
Click to collapse
No from recovery
UltraWelfare said:
No from recovery
Click to expand...
Click to collapse
oh, the phone doesn't have CWM recovery.. I wish it did though
http://www.techpository.com/?page_id=224
Android: ADB – Mount a filesystem read-write
Mount a filesystem read-write
Very often when you want to write files to a particular partition on ADP1, you will get a “Permission Denied” if the partition is mounted read-only.
To get around this, you need to mount the partition read-write. Typically this is done with /system partition
$adb shell
$ su
$mount -o rw,remount -t yaffs2 /dev/block /mtdblock3 /system
(Replace /dev/block/mtdblock3 & /system with appropriate device path and mount point, as obtained from cat /proc/mounts)
This was the first result on Bing with the search terms "adb mount read write"
Sent from my Nexus 4 using XDA Premium 4 mobile app
HI Dragon
Thanks for your post
I am getting the error "sh: -o: not found" with the last command
I'm not entirely sure on how to use the remount command.. I'm trying to mount the system partition i guess?
could you please provide some noobish info on how to get this done?
I don't know what "/dev/block" means, nor "mtdblock3" .. I know /system is the part with build.prop in though
Edit: device not found
adb devices
You see yours? Good
adb shell
mount
This may tell you or try
adb shell
cat /proc/partitions
Or maybe
ls -l -a /dev/block/platform
Then from here find chip and search this and so on and so and if you find a by-name directory your good
Sent from my Nexus 4 using XDA Premium 4 mobile app
I was trying to copy a update file to the sdcard, but I kept getting permission denied, so I went into adb shell and tried remounting the phone with rw permissions and it kept saying "Device not found" ..
I think im just gonna have to take it back to 3 and wait 50 weeks to get it back
Hi all.
I apologize ahead of time that this thread is so long, but I have quite a problem. I am in the process of rooting my unlocked Galaxy S4 running Android 5.0.1 lolipop, but I cannot add the su and busybox to my /system/bin folder because /system is a read-only filesystem. I have done just about everything I can think of to mount and remount, like typing adb remount and mount -o remount,rw /system, but they just give me the same answer saying permission is denied. I tried doing adb root to get the permission I needed, but I got an error message saying that adbd cannot run as root in production builds. After doing some research, I found out that the /default.prop has debuggable=0 and that may be what is not allowing me to restart adb as root. So I opened the shell and typed cat to see and sure enough it was set to 0. So I did echo and set the variable to 1. However, whenever I hit enter, I got another error telling me the same thing, that /default.prop is a read-only file. I am at a loss of what to do now. How I can mount and unmount the /system if I can't get any permission to do so? Any help would be greatly appreciated. I do ask though, please don't recommend ready made apps that can insta-root your phone like a supah-hackah because I want to do this the hard way for gratification's sake. I am just stuck and need some help to get the /system to allow writing as opposed to read-only. Thanks in advance.