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.
Related
it does it everywhere else except for the system folder. i really want to get this version of pandora off, but it's not doing anything. it worked with my other android devices, not sure why it's happening with this
Do you have the latest version of Root Explorer?
yeah what version of root explorer???
Generally if you can mount R/W in other folders you should also be able to do so in the system folder. You may have already tried this but you may want to boot into recovery and wipe cache and try again. If you have ADB set-up you should also be able to mount the device in R/W by doing the following command: su [enter] mount -o remount,rw -t /dev/block/mtdblock5 /system [enter] if that goes out without a hitch you should be able to delete in the system folder. You can also put that command in to terminal (if you have it) and that also should put the system into R/W. To remount the device in R/O just replace rw with ro. Hope this helps.
2.9.3...wow i'm restarted...i updated and it works now
I have had this issue a couple of times and a simple reboot has fixed it.
Sent from my B.A.M.F. Thunderbolt
Gingerbreak 1.2 goes through the motions, seems to be working, and the phone reboots, but root is not achieved.
Is there any procedure available to root this phone? Even a temporary root?
For the time being I'd like to push one file into /system/framework (framework-res.adk).
Thanks,
Chris
~~~~~~~~~~~~~~~
Phone details:
System version
Version.1.2.148.MB870.Verizon.en.US
Model
Droid X2
Android version
2.2.2
Baseband version
n_03.13.23s
Kernal version
2.6.32.9-00049-g1e05fe4
[email protected] #2
Build number
4.4.1_274_DTN-14.8
ERI version
5
PRL version
52341
Works on all my X2 's
Did you turn on usb debugging, if so try removing gingerbreak, format the sd card, and install gingerbreak again after a fresh boot. Might want to find another source for the gingerbreak apk to. No luck, try another sd card.
USB debugging on, a different formatted SD card used, fresh reboot and downloaded gingerbreak from a different source; same. I have also tried Gingerbreak 1.1 just for kicks.
Check at the very end of your app drawer. I used gingerbreak 1.2 last night and for some reason super user was all the way at the end of the app drawer, not in its alphabetical spot.
just before running gingerbreak
reboot your phone
do not start any other app before starting gingerbreak
this should work
I got my X2 on Friday afternoon.. and rooted it using Gingerbreak Friday evening. I downloaded it from the link provided in the "Getting Started.." thread in this section. So it *should* work, take a deep breath and follow the very good advice given above, take your time and let it do its thing - walk away if you have to in order to avoid panic!
Good luck.
ChrisPappas said:
USB debugging on, a different formatted SD card used, fresh reboot and downloaded gingerbreak from a different source; same. I have also tried Gingerbreak 1.1 just for kicks.
Click to expand...
Click to collapse
Format Sd, and factory reset the phone. Download the apk to your desktop and drag and dropdrop it to the root of your sd and install it from there. A full wipe should rule out any third party apps from causing the problem.
I got the answer for this. The rooting process worked. What was tripping me up is that the partition needed to be remounted as RW.
Chris
Okay, I don't know if I'm rooted or not. I have enabled root access for File Expert and it acts like it's letting me cut and paste into the /system/framework directory, but the original file stays in place. AndroidCommander notates Root=no.
These adb commands are not working:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
TA054029VA device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
$ ^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push framework-res.apk /system/framework/framework-res.apk
failed to copy 'framework-res.apk' to '/system/framework/framework-res.apk': Read-only file system
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb root
adbd cannot run as root in production builds
Su does not change $ to #:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
Root Checker shows the following detailed results:
Congratulations! You have root access!
Standard su binary location:
/system/xbin/su: No such file or directory
Alternale su binary location:
/sbin/su: Permission denied
Root user if:
uid=0(root)
Root group id:
gid=0(root)
Does anyone have any ideas of what can I do to fix?
Thanks,
Chris
I was able to get the abd shell to perform with su. Someone led me to look at the phone when I was typing su in abd shell. The phone was asking for permission, which was opting out after a few seconds. When I approved the access within the window, it gave me the # prompt.
I also found out that adb push needed to have the volume mounted as rw, which I was able to do from the #.
After that, I was able to push a file into the system/framework directory. I bricked the phone doing it because the file I was pushing is apparently very picky (framework-res.apk). Luckily there's an SBF for the droid 2 now.
I'm not sure what the deal is with this root, as it only half-ass works. I rooted a Thunderbolt a couple of weeks ago and I didn't have any of these problems. For example, AndroidCommander on the PC reports no root access.
My next mission is to collect details on the ins and outs of fooling with the framework-res.apk.
Chris
It seems that nobody is talking about deodexing the Droid X2. Just thought I would let everyone know that xUltimate 2.2.8 works on the Droid X2 with the newest drivers installed. I am currently manually deodexing my root GB Droid X 2.
Some Members Might Not Wanna Take The Risk. With All The ROMs Are Already Deodexed. Me Personally I've Had That Program Downloaded Since The First Time It Was Posted And Have Used It Numerous Times. Now That You Mentioned This, You Should Go Bump That Thread.
If anyone can instruct me on how to successfully create an update zip I would gladly do it for those that don't want to take the risk of deodexing manually. But I am really shocked that a deodexed GB is not in the TBH App and no one seems to be talking about it.
I'm Gonna PM You A Few Websites To Learn How To Do It.
Am I doing something wrong? I am trying to use the adb commands to copy everything over from the done_app and the done_framework folders but it is saying: CP: /sdcard/done_app/* when I run cp /sdcard/done_app/* /system/app
These are the commands that I am trying:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
dimitri407 said:
Am I doing something wrong? I am trying to use the adb commands to copy everything over from the done_app and the done_framework folders but it is saying: CP: /sdcard/done_app/* when I run cp /sdcard/done_app/* /system/app
These are the commands that I am trying:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Click to expand...
Click to collapse
You Need To Manually Transfer Them Over USB First. Both App And Frame Place Them On Your SD Card.
They are both on my sd card. Actually they are on the external sdcard and the internal sdcard. That is what seems so weird about the error. The files are there. Is the command wrong for the Droid X 2?
dimitri407 said:
They are both on my sd card. Actually they are on the external sdcard and the internal sdcard. That is what seems so weird about the error. The files are there. Is the command wrong for the Droid X 2?
Click to expand...
Click to collapse
When You Did "su", Did You Grant The Superuser Request On The Phone?
Yeah. You have to do that initially to be able to use the mount command. Is the mount command my issue by chance?
dimitri407 said:
Yeah. You have to do that initially to be able to use the mount command. Is the mount command my issue by chance?
Click to expand...
Click to collapse
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
I can't figure it out either. I did this to my Droid X with no problems. But the Droid X 2 just wants to be a pain when I am trying it.
MikeJ92YJ said:
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
Click to expand...
Click to collapse
I am wondering, since it is not working in adb shell then could I do it in the terminal?
MikeJ92YJ said:
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
Click to expand...
Click to collapse
So I finally got everything to work but to do so I had to copy the done_app and the done_frame folders to /data/local/tmp then run the cp commands.
For some reason, I could not get to the SD Card or the External SDCard.
you both need to quit hijacking threads and grow up. If I was the mod I would ban both of you.
Sent from my DROID X2 using XDA App
mistawolfe said:
Lol. You beg for 'em. Signature...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Can we please stop hijacking my thread. This is suppose to be about Deodexing the Droid X 2.
Well I am suprised to report that since deodexing my stock pre-rooted GB, my battery life has been much better. Will have to see what it is like at the end of the day.
dimitri407 said:
Well I am suprised to report that since deodexing my stock pre-rooted GB, my battery life has been much better. Will have to see what it is like at the end of the day.
Click to expand...
Click to collapse
Oh God Yes. It's Gonna Faster And Smoother. The Point Of Deodexing Is It Recompiles The Odex Inside The Apk For Easier Themeing And The System Is Able To Read The Apks Faster. Definitely Gonna Help Battery If The System Isn't Working As Hard.
when you connect USB, you MUST be in "charge only" mode w/ usb debugging enabled. ANY OTHER MODE will fail to allow complete access to /sdcard or /sdcard-ext...
or at least that was my experience.
I'll Challenge That I Used PC Mode To Run The Deodex App And Then To Transfer The Completed Files Without Switching Modes. Anytime I Run ADB Operations My Phone Is In PC Mode.
I will check both settings today. But by mounting the partition, it should become available either way. But we will see.
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.