Hello,
I am trying to root my LG Lucid 4G with a one-click sort of method. However, it doesn't work. I am getting messages such as
Code:
failed to copy 'su' to 'system/bin/su': Read-only file system
I then opened up ADB, and tried to use the command
Code:
adb remount
, but that just responded with the message
Code:
remount failed: Operation not permitted
Does anyone know how to fix this, so I can root my phone?
Thanks in advance!
shotgunfacelift said:
Hello,
I am trying to root my LG Lucid 4G with a one-click sort of method. However, it doesn't work. I am getting messages such as
Code:
failed to copy 'su' to 'system/bin/su': Read-only file system
I then opened up ADB, and tried to use the command
Code:
adb remount
, but that just responded with the message
Code:
remount failed: Operation not permitted
Does anyone know how to fix this, so I can root my phone?
Thanks in advance!
Click to expand...
Click to collapse
try super su.
adithbalan said:
try super su.
Click to expand...
Click to collapse
By that, do you mean I should type
Code:
super su
into the ADB shell, or do you mean I should download the application for Android?
shotgunfacelift said:
By that, do you mean I should type
Code:
super su
into the ADB shell, or do you mean I should download the application for Android?
Click to expand...
Click to collapse
download the zip from their website and try flashing via system updater.
OR TRY THIS:
Code:
adb shell
su
mount -o remount rw /system
adithbalan said:
download the zip from their website and try flashing via system updater.
OR TRY THIS:
Code:
adb shell
su
mount -o remount rw /system
Click to expand...
Click to collapse
I can get to
Code:
adb shell
properly, but as soon as I type
Code:
su
, it says
Code:
/system/bin/sh: su: not found
shotgunfacelift said:
I can get to
Code:
adb shell
properly, but as soon as I type
Code:
su
, it says
Code:
/system/bin/sh: su: not found
Click to expand...
Click to collapse
try skipping it.
adithbalan said:
try skipping it.
Click to expand...
Click to collapse
It ends up saying
Code:
mount failed: Operation not permitted
https://theunlockr.com/2013/06/16/how-to-root-the-lg-lucid-4g-bin4ry-method/
adithbalan said:
https://theunlockr.com/2013/06/16/how-to-root-the-lg-lucid-4g-bin4ry-method/
Click to expand...
Click to collapse
Thanks, I'll try that.
adithbalan said:
https://theunlockr.com/2013/06/16/how-to-root-the-lg-lucid-4g-bin4ry-method/
Click to expand...
Click to collapse
So I tried it, and after the phone reboots a few times, the command prompt shows this message and then closes immediately:
Code:
Waiting for device to show up again....
Going to copy files to it's place
mount: permission denied (are you root?)
GOTO was unexpected at this time.
Related
Hi,
I am trying to alter the boot xml file to get my boot sound back. I am on Modaco 2.5.1 now.
Pulled the boot sound xml file, edited. But when I try push back to phone I get the 'android adb push read-only file system' message.
How do I get round this?
Thanks
Phil
Phil_UK said:
Hi,
I am trying to alter the boot xml file to get my boot sound back. I am on Modaco 2.5.1 now.
Pulled the boot sound xml file, edited. But when I try push back to phone I get the 'android adb push read-only file system' message.
How do I get round this?
Thanks
Phil
Click to expand...
Click to collapse
Do a adb remount before doing the push should solve it.
Thanks
That solved it!
Phil
i'm having the same error when i want to delete stock apps. i'm rooted already, but not sure how to get myself to read write rights. any idea?
Get around read-only
I am having the same problem. Have you had any luck??
woowoowooty said:
I am having the same problem. Have you had any luck??
Click to expand...
Click to collapse
adb remount
"remount failed: Operation not permitted"
you cant do it while in recovery,you have to be booted up.
EXAMPLE to remove Sim Toolkit
adb remount
remount successful
adb shell rm /system/app/Stk.apk
Done...
If you still have problems type adb shell, type su,press allow on your phone screen then try again.
If it shows a $ sign when u type adb shell then u got no root son
................ delete post. ....
sorry but i am quite new to android and rootin... can u please tell me what is recovery and what is boot up.. cause i am facing teh same issue and when i try adb remount from my command prompt, i get permission denied error . Can this also be done from terminal emulator in android.. my device is rooted and i have superuser permission..
thanks in advance,
Rejo
rejo_nazi said:
sorry but i am quite new to android and rootin... can u please tell me what is recovery and what is boot up.. cause i am facing teh same issue and when i try adb remount from my command prompt, i get permission denied error . Can this also be done from terminal emulator in android.. my device is rooted and i have superuser permission..
thanks in advance,
Rejo
Click to expand...
Click to collapse
You can try it in terminal emulator after su.
Code:
$ su
# mount -o rw,remount /system
<do what you want>
# mount -o ro,remount /system
thanks for the information!
Hi.
Samsung Galaxy Ace - FroYo 2.2.1 - Rooted with superuser.
Pulled framework.jar from /system/framework/framework.jar
edited it and now pushing back.
I get
failed to copy 'framework.jar' to '/system/framework/framework.jar': Read-only file system.
I know it's a read-only file system, but I need to push that (and other files) back there.
How to allow that process?
My other option is to "FLASH" a .zip file which contains these files, and I think that puts them in their desired location, but:
What is Flashing and how is it done on my device? I've been googling for a couple hours now with no luck. Adobe Flash is taking all the search results, and some found forum entries aren't helping.
Many thanks, I hope for a quick reply.
Hi, same problem trying to push some libs and framework.jar back to where they originally pulled from. I need to do that for Arabization on Samsung Galaxy Ace running Froyo 2.2.1 with Root.
Error returs "failed: read-only file system"
I've beek googling and searching forums for a couple days now with no luck. Tried many things, commands and chmod which all failed.
The other option, which is to use update.zip on stock recovery to send the files home has failed. Got the following:
Finding update package...
Opening update package...
Installing upate...
E:Error in /sdcard/update.zip (Status 0)
Installation aborted.
I couldn't install ClockworkMod to try it there because Rom Manager does not list my phone (Samsung Galaxy Ace) in the options it gives me when I ask it to Flash ClockworkMod Recovery into my phone. I don't know which phone to choose form the list:
- Huawei Pulse Mini
- Dell Streak
- Huawei Pulse
- Commtiva Z71 (Boston, blaze, and more)
- Geeksphone ONE
- Spice MI700, Commtiva Link N700 and more)
- Huawei Ascend
Halp.
Oh just noticed I have both last posts. How progress works.
By the way,
#mount -o rw,remount /system
does not help. Trying to copy files using 'cp' commant in shell now simply brings 'file exists'. Is there an 'overwrite' attribute to add that'll fix it?
adb remount worked for me thanks..
pigfoot said:
You can try it in terminal emulator after su.
Code:
$ su
# mount -o rw,remount /system
<do what you want>
# mount -o ro,remount /system
Click to expand...
Click to collapse
champagne post. tnx!!!
pigfoot said:
You can try it in terminal emulator after su.
Code:
$ su
# mount -o rw,remount /system
<do what you want>
# mount -o ro,remount /system
Click to expand...
Click to collapse
Worked for me, thank you!
going through the entire 1.5 to 2.1 root tutorial to a tee, but once i get to the recovery image, this happens (following is an entire copy/paste of what I went through, incase i did something wrong before i hit the point)
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Lemcott>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
adb server is out of date. killing...
* daemon started successfully *
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
C:\android-sdk-windows\tools>adb push recovery.img /sdcard
1192 KB/s (3926016 bytes in 3.215s)
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
448 KB/s (9640 bytes in 0.021s)
C:\android-sdk-windows\tools>adb shell flash_image recovery /sdcard/recovery.img
flash_image: permission denied
C:\android-sdk-windows\tools>
EDIT: I am a complete ass hat. nothing to see here, move a long. mods delete this if you please.
P.S. Everyone else: ALWAYS DOUBLE CHECK BEFORE POSTING FOR HELP. *ahem* now be on your way.
try programming thru fastboot. press call + vol down and select the fastboot option and use this command from the pc
fastboot flash recovery recovery.ing
Sent from my Evil Eris v1.1 using the XDA mobile application powered by Tapatalk
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
I had the same thing but I just kept reentering
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
and after maybe 4 iterations it worked.
I have a very simular problem:
(moto droid with android 2.1)
$su
su
Permission denied
Click to expand...
Click to collapse
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
>adb shell chmod 755 /system
unable to chmod /system: Read-only file system
>
Click to expand...
Click to collapse
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
make it read/write
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
I wouldn't try to flash anything you find here to a Moto Droid.
This is for the HTC Droid Eris.
Otherwise, and if I'm misunderstanding you, good luck with your problem.
archmagus said:
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
Click to expand...
Click to collapse
I've been bashing my head in ALL day trying to get past this and finally found this thread! This worked perfectly!
theboo7 said:
make it read/write
Click to expand...
Click to collapse
How should i make is read/write?????
i cant get it to work at all.. need help plz.
Hello Guys
why cant i mount that **** together, i have the root permission, but also i dont..somehow
Code:
Microsoft Windows [version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle rettigheder forbeholdes.
C:\Users\Rasmus H. G. Johnsen>d:
D:\>cd android\tools
D:\android\tools>adb devices
List of devices attached
HT9B7LG00092 device
D:\android\tools>adb shell mount -o rw,remount /dev/block/mtdbloc3 /system
mount: Operation not permitted
D:\android\tools>adb shell
$ ls
ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.rc
init.goldfish.rc
init.bahamas.rc
init
default.prop
data
root
dev
$ exit
exit
Also if I go on and try to do this:
Code:
D:\android\tools>adb push flash_image /system/bin
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
I know that the flash_image fil and my recovery.img file is in this library and also on my sdcard, but I cant push the gotdamn flas_image file in the /system/bin catalog.
Can some one please help me ?
PS. I have the USB-debugging turned ON.
How do you know that you have root? Or, how did you gain root?
doogald said:
How do you know that you have root? Or, how did you gain root?
Click to expand...
Click to collapse
I have the app called androot from google market, ang i have run it to get root.
wfdi said:
I have the app called androot from google market, ang i have run it to get root.
Click to expand...
Click to collapse
I'm not aware of that app, and cannot find it in the market myself (do you have a link?)
However, one way to check for sure if you truly have root is run the adb command adb shell and, when you get a prompt, type the command "su". If it returns with a "#" prompt (rather than the "$" prompt that you are seeing), then you have root on the phone.
Most people these days root with either jcase's 1click root for eris: https://market.android.com/details?id=net.andirc.erisrooter or they use the procedure here: http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html
You may be able to use the steps here as well, since you seem pretty comfortable with adb and have that working already: http://androidforums.com/eris-all-things-root/125436-detailed-leak-root-tutorial.html
Guys new I found another solution (tested on u8150)
First make sure that you are rooted first.
Open adb shell
Type in su.
Remount the system partition as read write.
Change the owner of system from root to system via chown root system
the exit the shell and push flash_image to system/
also push clockworkmodrecover.img into the system partion dont forget the last /.
then exit.
use a file manager, I used rootbrowser.apk without a memory card and installed recovery.
with rootbrowser copy flash_image to the bin directory.
don't forget to change the owner back to root to the system partition after you finish with rootexplorer or whatever u use even adb can work.
then the rest follows.
The above works only if your'e rooted and have adb.
Goodluck
haha am a genius Installing ROM +Recover without sdcard on u8150
all you have to do is:-
1. Make sure u have installed clockwork mode recovery on your device and have su binary.
2. Open adb with the device normally on.
3. Remount the data partition as read write using mount remount in adb .
4. use adb and push the cynogenmode.zip or any rom that fits into the data partition using
adb push romname.zip /data/
5. Reboot into clockworkmod recovery using the various options available.
6. This is what to do if you don't have a sdcard.
open adb with phone connected and run
adb shell
mount /data /sdcard
then go back to the main recovery menu and wipe dalvik cache only
then choose update from sdcard
flash your rom and tadaaa.
your'e done.
NB:CAUTION MAKE SURE TO FLASH A ROM THAT DOES NOT WRITE INTO THE DATA PARTION
THIS CAN BE DONE BY LOOKING FOR A FILE CALL UPDATE SCRIPT IN THE zip OF THE ROM U WANT TO INSTALL
Am going to make a post about this later.
Goodluck
Lol, 3 and a half year break between responses.
The problem with flash_image & dump_image is that it doesn't work on devices devices which use emmc (recent phones)and have
mmcblk0
and cat /proc/mtd won't work here either.
This means that you have to use dd to write to this devices.
I wonder how guys determine the partitions to use on such devices, and someone should hint as to what is going on since it seems manufacturers seriously don't want people to exploit their devices.
** This is completely unsupported!!!!!!! **
ALL credit goes to saurik for the root method, Jason A. Donenfeld (zx2c4) for finding the exploit, alpharevx for finding the offsets and initial confirmation on the Transformer Prime and viperboy for finding it and posting it in his thread. I did not research, find, or develop this root method!
Mods, if I've done anything wrong, please feel free to remove this thread.
You will need to know how to use ADB commands, otherwise, use viperMOD PrimeTime!!!!!!!!!!!!!!!!!!!!!!!!.
Downloads:
mempodroid binary
su binary
Root:
adb push mempodroid /data/local
adb push su /data/local
adb shell
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd9ec 0xaf47 sh
** You should now be in a remote shell session with root (indicated by #)
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
** IF you have previously rooted your Prime, run the following two commands. They may throw an error that the file a file was not found.
rm /system/bin/su
rm /system/xbin/su
cat /data/local/su > /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local/mempodroid
rm /data/local/su
exit
exit
adb reboot
After your Transformer Prime comes up, install Superuser from android market.
HOPEFULLY everyone has learned their lesson and will also install Voodoo Rootkeeper as well!!!!!!!!!!!!!!!!!!!! R
Enjoi!!!!!!!!!!!!!!!
** Feb 21 2012 Edit **
Works on 9.4.2.14
** Feb 09 2012 Edit **
Works on 9.4.2.13
** Jan 25 2012 Edit **
Changed the mount command - thanks viperboy!
Added steps to possibly resolve issues with previously rooted systems
Changed a few steps to be a little bit easier.
**Jan 24 2012 Edit **
Some people are reporting issues with this method. I suspect this is due to previously having root or other altered files. A method that has worked for some is to update to 9.4.2.11.1 and then following the above procedures. Please note, this firmware release is unofficial and at this time THERE IS NO DOWNGRADE PATH.
i keep getting permission denied after
adb shell /data/local/mempodroid 0xd9ec 0xaf47 mount -o remount,rw '' /system
i missed a chmod step, add it just now.
run:
adb shell chmod 777 /data/local/mempodroid
and then pick up right where you left off.
as i am not root nor superuser .. i don't even get access
/ $ cd data
~ $ ls
ls: can't open '.': Permission denied
after this command
adb shell /data/local/mempodroid 0xd9ec 0xaf47 sh
i got [email protected]:/ # but i cant type anything else in the dos windows after it.. can you explain further please
insane111 said:
after this command
adb shell /data/local/mempodroid 0xd9ec 0xaf47 sh
i got [email protected]:/ # but i cant type anything else in the dos windows after it.. can you explain further please
Click to expand...
Click to collapse
click on the window, you should be able to continue typing
/mnt/sdcard/Download $ adb push su /data/local
error: device not found
for some odd reason i cant type anything else after on that window..
after shell with root, i get the #, but i can't type anything afterwards. do i just repeat the process over?
edit: question was already asked, tried clicking on window, doesn't work.
insane111 said:
for some odd reason i cant type anything else after on that window..
Click to expand...
Click to collapse
updating!
10 char
toby77jo said:
/mnt/sdcard/Download $ adb push su /data/local
error: device not found
Click to expand...
Click to collapse
no offense, you may want to just wait for the one click root.
Tairen said:
after shell with root, i get the #, but i can't type anything afterwards. do i just repeat the process over?
edit: question was already asked, tried clicking on window, doesn't work.
Click to expand...
Click to collapse
updated, should be working now.
hehe that is fine .. not offended
se1000 said:
updated, should be working now.
Click to expand...
Click to collapse
thank you very much sir.. it work...
insane111 said:
thank you very much sir.. it work...
Click to expand...
Click to collapse
NICE!!!!!!!!!!!!!!!!!!!!
hmm did everything on your post, and rebooted. already had SU so i just opened up an app that requires root (titanium backup) and it says it wasn't able to attain root?
edit: confirmed with root checker that i still don't have root
Tairen said:
hmm did everything on your post, and rebooted. already had SU so i just opened up an app that requires root (titanium backup) and it says it wasn't able to attain root?
edit: confirmed with root checker that i still don't have root
Click to expand...
Click to collapse
Try re-installing superuser? When I was rooted before, sometimes superuser wouldn't prompt me for SU on occasion too.
se1000 said:
Try re-installing superuser? When I was rooted before, sometimes superuser wouldn't prompt me for SU on occasion too.
Click to expand...
Click to collapse
ahh i see the problem..
cat /data/local/su > /system/xbin/su
sh: cannot create /system/xbin/su: Read-only file system
how do i proceed?
Tairen said:
ahh i see the problem..
cat /data/local/su > /system/xbin/su
sh: cannot create /system/xbin/su: Read-only file system
how do i proceed?
Click to expand...
Click to collapse
Looks like something went wrong on the first mempodroid command. Go back and start from the begining just in case. Shouldn't hurt anything.
se1000 said:
Looks like something went wrong on the first mempodroid command. Go back and start from the begining just in case. Shouldn't hurt anything.
Click to expand...
Click to collapse
Sounds good, will try again and update!
Hi all, i added some files into the system directory of my kindle fire hdx 7'.. when i restarted it is stuck in a boot loop on the animated Kindle Fire boot screen, i can ADB onto it, and i attempted to remove the files, but "ADB su" isn't working for me, and I'm unable to access the system directory over ADB... and i don't have custom recovery.
Any ideas on this one? is there a way of restoring the Kindle?
Thanks
osmorgan said:
Hi all, i added some files into the system directory of my kindle fire hdx 7'.. when i restarted it is stuck in a boot loop on the animated Kindle Fire boot screen, i can ADB onto it, and i attempted to remove the files, but "ADB su" isn't working for me, and I'm unable to access the system directory over ADB... and i don't have custom recovery.
Any ideas on this one? is there a way of restoring the Kindle?
Thanks
Click to expand...
Click to collapse
what you get on
Code:
adb shell
su
?
thanks for the reply. when i
adb shell
su
Click to expand...
Click to collapse
it returns to 1:[email protected] where it should show [email protected] any ideas?
osmorgan said:
thanks for the reply. when i
it returns to 1:[email protected] where it should show [email protected] any ideas?
Click to expand...
Click to collapse
after that use
Code:
mount -o rw,remount /system
if you wil get permission denied you need to do hard reset from recovery and try again
after that you could change files in /system
great, i will try this later.. any guides on doing a hard reset?? keeping in mind that i don't have custom recovery..
thanks again.
osmorgan said:
great, i will try this later.. any guides on doing a hard reset?? keeping in mind that i don't have custom recovery..
thanks again.
Click to expand...
Click to collapse
you could get into stock recovery by holding power+volume up
all of this suggesting that you are at 4.5.2 and rooted
for 3.2.X hard reset will delete su - file
You're a star. Thanks. I'll get onto this after work.
ONYXis said:
you could get into stock recovery by holding power+volume up
all of this suggesting that you are at 4.5.2 and rooted
for 3.2.X hard reset will delete su - file
Click to expand...
Click to collapse
No luck :/ was unable to mount, and hard reset via recovery still results in boot loop :/ any other ideas?
Could you post output?
and pls what is your firmware and root method?
Seems no way to recover(sorry
How do I provide the output? I was 4.5.2 and rooted with CVE
copy-paste output from cmd
like:
Code:
adb shell
su
....
ahh i see what you mean.. ive run s uagian after factory reset and its now giving me the root prompt! great! im just about to follow this guys steps
http://forum.xda-developers.com/showthread.php?t=2793253
thanks for your help.. i may be back.
any idea if this method works with stock recovery?
ONYXis said:
copy-paste output from cmd
like:
Code:
adb shell
su
....
Click to expand...
Click to collapse
nope.. that didnt work for me.. do you know how i can push a deb to reflash?
Pls post output to see that exactly doesn't work.
to use that manual you need to use 4.5.3 bin btw
I see, I was having permissions errors when pushing the file to the sdcard, I had mounted the data partition. I am unable to write anything as shell user, but fine as root. Any ideas?
Thanks
adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /cache
[email protected]:/ # mkdir /cache/recovery
mkdir failed for /cache/recovery, File exists
[email protected]:/ # echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
[email protected]:/ # chmod 0777 /cache/recovery/openrecoveryscript
[email protected]:/ # exit
[email protected]:/ $ exit
Mac-miniownloads $ adb push update-kindle-13.4.5.3_user_453011120.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/cache/kindleupdate.bin': Permission denied
What do you think?
ONYXis said:
what you get on
Code:
adb shell
su
?
Click to expand...
Click to collapse
ONYXis said:
Pls post output to see that exactly doesn't work.
to use that manual you need to use 4.5.3 bin btw
Click to expand...
Click to collapse
osmorgan said:
Mac-miniownloads $ adb push update-kindle-13.4.5.3_user_453011120.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/cache/kindleupdate.bin': Permission denied
What do you think?
Click to expand...
Click to collapse
You cant do this at that way
you need :
Code:
adb push update-kindle-13.4.5.3_user_453011120.bin /sdcard/update.zip
adb shell
su
mount -o remount,rw /cache
cd /sdcard
cp update.zip /cache
chmod 777 /cache
chmod 777 /cache/recovery
cd /cache/recovery
echo "--update_package=/cache/update.zip" > command
exit
exit
adb reboot recovery
thank you but i still get permissions issues -
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/sdcard/update.zip': Permission denied
ONYXis said:
You cant do this at that way
you need :
Code:
adb push update-kindle-13.4.5.3_user_453011120.bin /sdcard/update.zip
adb shell
su
mount -o remount,rw /cache
cd /sdcard
cp update.zip /cache
chmod 777 /cache
chmod 777 /cache/recovery
cd /cache/recovery
echo "--update_package=/cache/update.zip" > command
exit
exit
adb reboot recovery
Click to expand...
Click to collapse
osmorgan said:
thank you but i still get permissions issues -
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/sdcard/update.zip': Permission denied
Click to expand...
Click to collapse
Hmm....Strange. Are you see Fire as mtp device on you Pc (for Mac you need https://www.android.com/filetransfer/)?
If "yes" - try to copy update.zip manual into Fire's internal storage.
Hi, does anyone know how to delete a file on root with terminal, as rm -r returns screenshotted error.
kriki200 said:
Hi, does anyone know how to delete a file on root with terminal, as rm -r returns screenshotted error.
Click to expand...
Click to collapse
Did you execute this command as root ? If not enter "su" then enter your command. (Make sure you hit "Allow" when the prompt for you to allow root accès to the shell appears)
And maybe it sounds stupid but try chmod commands if your command doesn't work.
I'm not an expert with android terminal so if the problem is persistent you can try this with a root explorer.
Hope all of this helped
Have a good day
kriki200 said:
Hi, does anyone know how to delete a file on root with terminal, as rm -r returns screenshotted error.
Click to expand...
Click to collapse
The partitition you want to deal with must be mounted as READ-WRITE before.
Raiz said:
Did you execute this command as root ? If not enter "su" then enter your command. (Make sure you hit "Allow" when the prompt for you to allow root accès to the shell appears)
And maybe it sounds stupid but try chmod commands if your command doesn't work.
I'm not an expert with android terminal so if the problem is persistent you can try this with a root explorer.
Hope all of this helped
Have a good day
Click to expand...
Click to collapse
I did, kinda don't want to change permissions... same.
jwoegerbauer said:
The partitition you want to deal with must be mounted as READ-WRITE before.
Click to expand...
Click to collapse
How do I do and undo that, will it change any file permissions?
Example:
Code:
su
cd /
mount -o rw,remount -t auto /system
jwoegerbauer said:
Example:
Click to expand...
Click to collapse
Thank you, it worked, do you know how to undo it, the below command deosn't seem to work and do you know what the "auto" is for in the command?
Code:
mount -o ro,remount -t auto /system