"rm -rf" command cannot run on the device
I've got an new device LG Optimus LTE II (LGE F160L) and install "Better Terminal Emulator Pro"
The Android version is 4.0.3
The kernel is 3.0.8-00001-g65e7cd3
1. I properly rooted the device
2. I used "su" command before runnig follow the commands.
3. When I try to run "rm -rf /sdcard/.ads" command, it showed "No such file or directory"
I've found the command "-rf" has been trade as a diretory but parameters.
How does it happened?
How can I resolve this?
I think it's because the folder /sdcard/.ads doesn't actually exist because /sdcard is a symbolic link to /mnt/sdcard. So to answer your question, I think the following might work:
Code:
rm -rf /mnt/sdcard/.ads
If that doesn't work, I dunno...
THK Malnilion,
I have also tried "rm -rf /mnt/sdcard/.ads", but didn't work with a respond of "rm failed for -rf, No such file or directory."
the "rm" command thought "-rf" is a file or a directory., and the "-rf" should be parameters.
Ah, I see, this might be a limitation of busybox, then.
Malnilion said:
I think it's because the folder /sdcard/.ads doesn't actually exist because /sdcard is a symbolic link to /mnt/sdcard. So to answer your question, I think the following might work:
Code:
rm -rf /mnt/sdcard/.ads
If that doesn't work, I dunno...
Click to expand...
Click to collapse
Malnilion said:
Ah, I see, this might be a limitation of busybox, then.
Click to expand...
Click to collapse
Oh, really?
I need to run a lot of testing scripts in "Gscripts". I see, why those scripts don't work on this device.
Then, how can I update the busybox? Those testing is my work!! Otherwise, I need to change back to HTC Desire which scripts are working well.:crying::crying: OH, Nooooo........:crying::crying::crying:
aswasw said:
Oh, really?
I need to run a lot of testing scripts in "Gscripts". I see, why those scripts don't work on this device.
Then, how can I update the busybox? Those testing is my work!! Otherwise, I need to change back to HTC Desire which scripts are working well.:crying::crying: OH, Nooooo........:crying::crying::crying:
Click to expand...
Click to collapse
Are you using the same terminal emulator application and version on the Desire?
drumist said:
Are you using the same terminal emulator application and version on the Desire?
Click to expand...
Click to collapse
Yes, of course. But the andorid version is 2.3.7.
I use "rm -r /mnt/sdcard/.ads" without parameter "f" as a mistake, and the script runs without a respond of error. ^_^
I used R.E browse to /mnt/sdcard , I found directory "/mnt/sdcard/.ads" has been removed !!!!!!!
I try to remove other directory with the "rm -r" command which seems non-forced remove command, but in fact, the command remove the folder, and everything in the folder, too.
OMG...Is there something has been modified in the kernel??
Related
Ok so the ubuntu install now works on slide credit goes to eratosthene he updated all the files to make it work all other credit goes to the dev’s listed on the links provided. FYI this was tested on eugenes latest froyo rom.
1. Go to http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/ download the ubuntu.zip file .
2. Unzip to a location on your pc to a folder named ubuntu.
3. Download the ubuntu-slide-v2 from here.
4. Unzip the ubuntu-slide-v2 to the same folder you used in step 2.
5. Create a ubuntu folder on the root of your sdcard .
6. Connect your Slide to the pc verify debugging enabled and storage disabled.
7. Adb push the files in the ubuntu folder to the /sdcard/ubuntu.
8. Then adb shell.
9. cd /sdcard then sh ubuntu.sh
Note: At this point, the scripts are now located in /data/local/bin and the mount point is /data/local/mnt
10. sh /data/local/bin/bootubuntu
11. you should now see [email protected]:/#
Note : install completed only do the following if you want to access ubuntu from android vnc app.
12. apt-get update
13. apt-get install tightvncserver
14. export USER=root
15. vncserver -geometry 480x320
16. • Run the android-vnc-viewer app and specify localhost port 5901 .
UPDATE: This is not working on CM 6 , I'm not sure why please help if you know .
That would be sooooo coool
Sent From My HTC Espresso Running Froyo Thanks to eugene373
Tried it but the install fails , may be the script or may be rights to edit the files im not that good with linux yet so im not sure .
Ok thanks, any help would be apriciated . If we can get a procedure that works ill write up a step by step for everyone and maybe make a video how to also.
Just guessing but it's probably because we don't have rw access to /system.
Until we get an unlocked bootloader it ain't happenin...
I could be completely way off though
I think you are right , if i rember most the errors where do to access issue's with files in the system folder. If it is the bootloader what would need to be done to " unlock " it ?
bled82 said:
I think you are right , if i rember most the errors where do to access issue's with files in the system folder. If it is the bootloader what would need to be done to " unlock " it ?
Click to expand...
Click to collapse
An OTA update would unlock it.
So once we get the froyo ota we should be able to follow the same process as the nexus one then ?
i would say "unlikely," i dont see how an ota would unlock the bootloader in any fashion. but i guess he might have been referencing the possibility of someone using the new ota to create an unlocked bootloader. the whole "how could the bootloader be unlocked," question bothers me, i never seem to get a straight answer
aceraider4 said:
i would say "unlikely," i dont see how an ota would unlock the bootloader in any fashion. but i guess he might have been referencing the possibility of someone using the new ota to create an unlocked bootloader. the whole "how could the bootloader be unlocked," question bothers me, i never seem to get a straight answer
Click to expand...
Click to collapse
Once there is an official OTA devs will be able to extract the keys needed to properly sign files I believe.
I thought the engineering build had an unlocked boot loader on it and once we flashed it that was that ?
Here's an updated zip for you guys. The process is generally the same as on the above-linked nexus one version, I just changed the scripts to move a few files to different places. You'll need to download ubuntu.zip from that post as well. Summary:
unzip ubuntu.zip somewhere
unzip ubuntu-slide.zip in the same place, replace all the files
make a directory called 'ubuntu' on your sdcard
adb push all the files in the zip to that directory
adb shell
cd /sdcard/ubuntu
sh ubuntu.sh
At this point, the scripts are now located in /data/local/bin and the mount point is /data/local/mnt
sh /data/local/bin/bootubuntu
You're now chrooted into the ubuntu install. Have fun.
Thanks going to try it now !!!
Does not work get attached error.
bled82 said:
Does not work get attached error.
Click to expand...
Click to collapse
I haven't tried this but based on your error, try this from the shell:
mkdir /data/local/bin
then run the ubuntu.sh again
falken98 said:
I haven't tried this but based on your error, try this from the shell:
mkdir /data/local/bin
then run the ubuntu.sh again
Click to expand...
Click to collapse
I did cd /data/local then ls and bin is listed , ran mkdir /data/local/bin failed file exists . i cant cd /data/local/bin get error cant cd to /data/local/bin
bled82 said:
I did cd /data/local then ls and bin is listed , ran mkdir /data/local/bin failed file exists . i cant cd /data/local/bin get error cant cd to /data/local/bin
Click to expand...
Click to collapse
This is some other script messed up when bin wasn't there and ended up creating a file called bin instead of it being a directory.
rm /data/local/bin
mkdir /data/local/bin
falken98 said:
This is some other script messed up when bin wasn't there and ended up creating a file called bin instead of it being a directory.
rm /data/local/bin
mkdir /data/local/bin
Click to expand...
Click to collapse
Ok getting closer , Thank you very much . Now when i ran sh .data/local/bin/bootubuntu i get error attached .
bled82 said:
Ok getting closer , Thank you very much . Now when i ran sh .data/local/bin/bootubuntu i get error attached .
Click to expand...
Click to collapse
What rom are you using? It looks like you don't have the ext3 module built into your kernel. I set my scripts up to use ext3 (more reliable, I really don't care that it eats into the life of my sd card), but many roms only have ext2. You might try uncommenting the first line of bootubuntu, and changing the ext3 to ext2 on line 10.
eratosthene said:
What rom are you using? It looks like you don't have the ext3 module built into your kernel. I set my scripts up to use ext3 (more reliable, I really don't care that it eats into the life of my sd card), but many roms only have ext2. You might try uncommenting the first line of bootubuntu, and changing the ext3 to ext2 on line 10.
Click to expand...
Click to collapse
I am running froyo using Kanged CM6 newbuild.zip from eugene373 , http://forum.xda-developers.com/showthread.php?t=721515 .
This thread is copied and modified from the G2 thread by trigeek for the Desire Z:
http://forum.xda-developers.com/showthread.php?t=834228
Apart from the changed hboot and wpthis-Z kernel module for the Desire Z instead of the G2, I have also updated the su-binary and SuperUser.apk to the latest version by ChainsDD
In no way I can be held responsible for any bricks to your phone. You are using this guide at your own risk!! I did test this guide on my own, and also on a friend's Desire Z.
As there was no manual rooting guide for the Desire Z, I posted it myself in order to help others that do not like visionary and like to do it 'the clean way'.
[GUIDE] Temp to permanent root on Desire Z, using rage instead of visionary
=================================================
There's already a guide here for obtaining permanent root using VISIONary, but some folks in #G2ROOT are having issues with the way that VISIONary modifies parititons. Using rage directly is a bit cleaner, since you know exactly what it's going to touch at each step of the way. I did NOT come up with any of this on my own, I'm building completely off of work that others have done. Speaking of which-
None of this would be possible without the tireless work that scotty2 put in. He stayed with the project for well over a month, through lots of smashed hopes and dead ends, until the solution was finally found. Were it not for his work, as well as the help of a few other key folks- we wouldn't be here. He deserves our thanks and some donations! We're talking hundreds of hours of work here, a couple bucks is not too much for that. His paypal is:
[email protected]
Send him some love! I'm not asking for anything myself, because I spent a half hour putting this together, and that doesn't deserve any donations!
DESIRE Z ROOT INSTRUCTIONS
=================================================
These are modified instructions based on the ones posted at http://bit.ly/g2root that use Visionary. A number of people have run into issues with the way that Visionary juggles around temporary partitions, and using the original root exploit is a much easier, and cleaner method for achieving permanent root. This tutorial will walk you through the rooting process by first achieving temporary root, and moving on to permanent root.
REQUIREMENTS
=================================================
•Visionary disabled at boot or uninstalled completely
•Android Terminal Emulator app
•ADB
•desirez-combined-root.zip (Attached to this post)
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.
VERY IMPORTANT!
Visionary has caused filesystem corruption for some users during the rooting process. Before attempting the instructions below, make sure that you have "auto run on boot" turned OFF, and reboot your system. Since you will not need visionary anyway after this, you might as well just uninstall visionary and reboot NOW before doing anything.
TEMP ROOT
=================================================
ON YOUR PC:
Unzip the z-temp-root files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
Code:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
ON YOUR PHONE:
1.Launch Terminal Emulator
2.
Code:
/data/local/tmp/rage
3.Wait for the message: "Forked #### childs."
4.Menu > Reset Term - Terminal Emulator will exit.
5.Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
6.**NOTE**: in the original directions from the XDA thread, you are instructed to run the /data/local/tmp/root script here. DON'T do this just yet. Leave the terminal window open.
PERM ROOT
=================================================
ON YOUR PC:
unzip z-perm-root and navigate to that folder. There will be four files. You will need to push two of these to your phone: hboot_7230_0.84.2000_100908.nb0 and wpthis-Z.ko. The other two files are optional for checksum verification.
Code:
$ adb push hboot_7230_0.84.2000_100908.nb0 /data/local
$ adb push wpthis-Z.ko /data/local
Optional but might came in handy:
Code:
$ adb push md5checksum /sdcard/md5checksum
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt. Now run:
Optional but recommended:
Code:
# /data/local/tmp/busybox md5sum /data/local/*
You should see:
hboot_7230_0.84.2000_100908.nb0 2ce1bdd5e4c1119ccfcecb938710d742
wpthis-Z.ko c73c5e77c91d306c418983c002b60b93
In case your hboot or wpthis-Z.ko file do not have the same md5hash as shown above, DO NOT CONTINUE. This means your file is corrupt or you are using a different file, for example the one for the G2 instead of Desire Z.
Now, let's turn off security for permanent flashing:
Code:
# insmod /data/local/wpthis-Z.ko
init_module 'wpthis-Z.ko' failed (Function not implemented)
That means it worked. This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)
# dd if=/data/local/hboot_7230_0.84.2000_100908.nb0 of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
You should see some messages indicating that it was written.
Code:
# /data/local/tmp/root
This will lock in root, and give you 'su' access in the future. Next, run:
Code:
# sync
Now wait at least a minute, just to be safe. After waiting, reboot your phone using the power button. After it finishes starting up, launch the terminal emulator, and type 'su'. You should get the prompt asking you to grant permissions. If you got the prompt, congratulations! You have permanent root!
Nice guide, thanks
Thank you Mr Q. works like a charm!
first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
when I just ignore it and type sync after that I have no root acces after a reboot.
Does anybody have a solution for it? I have already done a hardreset with the same results.
thanks in advance...
So this only roots your phone? Or does it s-off as well? From what I understand this s-offs as well because you're pushing the hboot as well.
EDIT: Nevermind. I read the thread again and it does indeed s-off as well.
MarDor said:
first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
when I just ignore it and type sync after that I have no root acces after a reboot.
Does anybody have a solution for it? I have already done a hardreset with the same results.
thanks in advance...
Click to expand...
Click to collapse
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen
ssyed said:
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen
Click to expand...
Click to collapse
having the same issue here
So I'm looking into these S-OFF and rooting threads and here is two bricks too. Does anyone have an answer for these two or should I skip this? Did the hboot do this or was it due to some problem in inserted kernel module? (I.E. the reboot of the emmc controller resulted in a ****ed up file system?)
yelti said:
having the same issue here
Click to expand...
Click to collapse
AnyDone said:
So I'm looking into these S-OFF and rooting threads and here is two bricks too. Does anyone have an answer for these two or should I skip this? Did the hboot do this or was it due to some problem in inserted kernel module? (I.E. the reboot of the emmc controller resulted in a ****ed up file system?)
Click to expand...
Click to collapse
Ok, so I have figured out how to get out of this "quietly brilliant" loop.
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.
ssyed said:
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.
Click to expand...
Click to collapse
Ok, so does any one have an explanation why this happened?
1. It wasn't wrong or screwed hboot, otherwise we would be facing a real brick?
Was it the root method? Was it the wpthis-Z.ko?
It might have been the kernel module, but I can't be sure about that with so little knowledge I have. (sure not the module itself but the kick to the emmc?) Just that it seems to be more likely option than a rooting attempt on a cached r-o file system?
I'm not complaining about the guide, it is specific and easy to follow but I would really love to have these semi bricks etc inspected more closely. It is not really helping to encourage ppl to root and try safe-off when we have unexplained bricks and semi-bricks around
MarDor said:
first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
Click to expand...
Click to collapse
ssyed said:
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen
Click to expand...
Click to collapse
yelti said:
having the same issue here
Click to expand...
Click to collapse
Did you guys run Visionary before trying this "rage" method of rooting ?
steviewevie said:
Did you guys run Visionary before trying this "rage" method of rooting ?
Click to expand...
Click to collapse
I don't know about others, but I didn't on mine. I was rooting it for the first time. Also, I don't know if this has anything to do with it, but I have the Bell version from Canada.
The root script threw an error for me too, so just to be safe I opened the script and typed in the commands manually. If you have problems with the script, just run these commands from the root terminal on your phone:
Code:
/data/local/tmp/busybox killall rage
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
mkdir /system/xbin
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
sync
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Hope this helps someone.. Thanks to the OP for the scripts.
Have a quick look, /system/xbin already seems to exist on my phone too.
So is there an error in the script ? e.g. needs to ignore if the directory already exists ? Or am I (we ?) missing something ?
goldenarmZ said:
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Click to expand...
Click to collapse
Good info, thanks. Perhaps just comment out that line of the script, to save running it all by hand (and therefore be prone to more error ?) ?
steviewevie said:
Good info, thanks. Perhaps just comment out that line of the script, to save running it all by hand (and therefore be prone to more error ?) ?
Click to expand...
Click to collapse
I did that first.. it threw more errors with the mount commands because I'd already run the script once, so some of the commands were repated. If it's your first run through, commenting it out would be fine.
I only did it line by line so I could see any more errors for myself and decide if they were important. As it turns out the script is very simple and only involves moving files around and changing their permissions.. anything that goes wrong should be immediately apparent even if you have no experience with shell commands.
goldenarmZ said:
I only did it line by line so I could see any more errors for myself and decide if they were important. As it turns out the script is very simple and only involves moving files around and changing their permissions.. anything that goes wrong should be immediately apparent even if you have no experience with shell commands.
Click to expand...
Click to collapse
Thanks, I was starting to worry about the bad experiences outlined above, given that this method appeared to be a more reliable one than VISIONary, and a route I was going to go down. But I'm pretty comfortable with shell scripts, so your input makes me feel a whole lot better !
goldenarmZ said:
The root script threw an error for me too, so just to be safe I opened the script and typed in the commands manually. If you have problems with the script, just run these commands from the root terminal on your phone:
-code-
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Hope this helps someone.. Thanks to the OP for the scripts.
Click to expand...
Click to collapse
thanks for this... I will give it a try
Yay, I just perma-rooted my phone using this method, many thanks to those who came up with the method in the first place, plus this handy guide too.
I got the message about /system/xbin already existing, but you can just ignore that message, it runs the rest of the script anyway.
ssyed said:
Ok, so I have figured out how to get out of this "quietly brilliant" loop.
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.
Click to expand...
Click to collapse
So after doing the guide you simply reeboot your phone into bootloader and select factory reset?
And then will the device be perm root and s-off???
[Q] Help me root my OTA upgraded G2 Visionary R14 Don't Work "Visionary R7 needed"
HELP...HELP....HELP.....PLEASE HELP
I have the T-mobile G2 and I did an over the air upgrade in December of 2010, ever since then the only version of VISIONARY that work on my phone was "Visionary R7" I have search all over the web trying to find the "Visionary R7" so far I have yet to find it...that is why I am posting on this forum......By the way I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA upgraded T-mobile G2....
So if anyone know where I can download "Visionary R7" please let me know...
Or
If someone know of a way to either Temporary or permanently root the G2 without Visionary please let me know as well
Thanks so much for your kind help......
Is temp root working?
Sent from my HTC Vision using XDA App
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
My whole goal is to get the phone temporary rooted using visionary and then finding a way to permanently root the phone....so to answer your question temp root is not working using Visionary R14....It did work when I was using Visionary R7... but since the visionary app (which was the R7 version) came off the Android Market, the process has be super difficult...thanks
My whole goal is to get the phone temporary rooted using visionary and then finding a way to permanently root the phone....so to answer your question temp root is not working using Visionary R14....It did work when I was using Visionary R7... but since the visionary app (which was the R7 version) came off the Android Market, the process has be super difficult...thanks
Nonentity018 said:
Is temp root working?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
+1
Like he said, use that, don't waste your time with visionary
sammd301 said:
HELP...HELP....HELP.....PLEASE HELP
I have the T-mobile G2 and I did an over the air upgrade in December of 2010, ever since then the only version of VISIONARY that work on my phone was "Visionary R7" I have search all over the web trying to find the "Visionary R7" so far I have yet to find it...that is why I am posting on this forum......By the way I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA upgraded T-mobile G2....
So if anyone know where I can download "Visionary R7" please let me know...
Or
If someone know of a way to either Temporary or permanently root the G2 without Visionary please let me know as well
Thanks so much for your kind help......
Click to expand...
Click to collapse
I'd stay away from visionary if I were you! Its messing up just as many phones as it is rooting them!
part of the problem is that a visionary method is stickied in one of these subforums... that needs to be taken down desperately and replaced with gfree/rage.
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
I am in the process of using this method....I'll let you all know how it turns out. by the thanks for pointing me to it...
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
Yes I am in the process of using ADB / RAGE method....I run in problem and I could use someone help please...
TEMP ROOT
ON YOUR PC: Unzip the gfree_temp-root.zip files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
===========
All the commands are working except
$ adb push rage /data/local/tmp/rage
the reply I get after input the command is
Cannot open 'rage': No such file or directory
I have search the web for help...but I could find help on that issue
SO please if anyone knows what I am doing wrong could you please help....
thanks
unzip the gfree_temp-root.zip again and make sure it extracted rage.
rage IS in there, I just downloaded the zip and opened it and looked.
yeah, look for a file called "rage". if it's there, you didn't get the proper directory. you have to get to the "gfree_temp-root" directory on your computer, and THEN adb push it
Cobra281 said:
yeah, look for a file called "rage". if it's there, you didn't get the proper directory. you have to get to the "gfree_temp-root" directory on your computer, and THEN adb push it
Click to expand...
Click to collapse
Yes the "Rage" file is there, all the other command work fine...except the one dealing with the "Rage" file
ratchetrizzo said:
unzip the gfree_temp-root.zip again and make sure it extracted rage.
rage IS in there, I just downloaded the zip and opened it and looked.
Click to expand...
Click to collapse
Thanks so much for your input....when I gfree_temp-root.zip file I can see that the "RAGE" file is present but after 20 to 30 minutes the "RAGE" file disappear from the folder but all the other files remains....Is an alternative gfree_temp-root download link that anyone might know of....thanks again
Disable your virus scanner while you do this, I bet its giving a false positive to the rage file and deleting it
Sent from my HTC Vision using XDA App
ratchetrizzo said:
Disable your virus scanner while you do this, I bet its giving a false positive to the rage file and deleting it
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thanks so much "Ratchetrizzo" for the tip on disable my anti-virus program, I was able to get the "Rage" command line to work....But now I have run into another ROAD BLOCK and truly hoping someone could help me out as well
I am now getting this error on the Terminal Emulator on my G2 after inputting the following command line from rooting instruction...
'You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:'
"# /data/local/tmp/root" without the # sign
I got this error message
"## mkdir failed for /system/xbin, File exists
## cp: can't stat '/system/xbin/busybox': Not a directory
## Unable to chmod /system/xbin/busybox: not found
## cp: not found
## cp: not found
## Unable to chmod /system/bin/su: No such file or directory"
Once again I am seeking help on this...So if anyone can help...please let me know. Thanks again for all of the support that I have received so far ...
sammd301 said:
Thanks so much "Ratchetrizzo" for the tip on disable my anti-virus program, I was able to get the "Rage" command line to work....But now I have run into another ROAD BLOCK and truly hoping someone could help me out as well
I am now getting this error on the Terminal Emulator on my G2 after inputting the following command line from rooting instruction...
'You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:'
"# /data/local/tmp/root" without the # sign
I got this error message
"## mkdir failed for /system/xbin, File exists
## cp: can't stat '/system/xbin/busybox': Not a directory
## Unable to chmod /system/xbin/busybox: not found
## cp: not found
## cp: not found
## Unable to chmod /system/bin/su: No such file or directory"
Once again I am seeking help on this...So if anyone can help...please let me know. Thanks again for all of the support that I have received so far ...
Click to expand...
Click to collapse
Well, start all over but once you get a root (a #) for the first time, rm -rf /system/xbin then reboot the phone, then start all over again and see if that works. for some reason you have a /system/xbin FILE, not a directory.
ratchetrizzo said:
Well, start all over but once you get a root (a #) for the first time, rm -rf /system/xbin then reboot the phone, then start all over again and see if that works. for some reason you have a /system/xbin FILE, not a directory.
Click to expand...
Click to collapse
When I input "rm -rf /system/xbin" command I got back
"rm failed for -rf, Read-only file system
sammd301 said:
When I input "rm -rf /system/xbin" command I got back
"rm failed for -rf, Read-only file system
Click to expand...
Click to collapse
well that's a problem, if /system is read only you can't lock in root
do this before you rm that stuff (remember to be at a root # prompt)
mount -o remount,rw /system
then rm the stuff, then start the root process over.
ratchetrizzo said:
well that's a problem, if /system is read only you can't lock in root
do this before you rm that stuff (remember to be at a root # prompt)
mount -o remount,rw /system
then rm the stuff, then start the root process over.
Click to expand...
Click to collapse
Yes, I did what you suggested, but now I am getting
"rm failed for -rt, no such file or directory" after inputting ""rm -rf /system/xbin" command...by the way thanks so much for helping me out on this...
I'm trying to use Terminal Emulator and no matter what I try to enter it tells me its not found. I am rooted and it has been given SU rights. I've also tried to uninstall and reinstall but nothing works. Any ideas?
presumedsublime said:
I'm trying to use Terminal Emulator and no matter what I try to enter it tells me its not found. I am rooted and it has been given SU rights. I've also tried to uninstall and reinstall but nothing works. Any ideas?
Click to expand...
Click to collapse
I don't quite understand your issue here. Are you trying to launch Terminal Emulator and get this message?
A few things to try:
1. Clear Terminal Emulator's cache and data, retry.
2. Uninstall, restart, install again, retry.
Alternative route: Install Connectbot and do what you need to do.
I'm trying to get to cd /system/etc/init.d but each time i type it in it says "cd /system/etc/init.d: not found:
presumedsublime said:
I'm trying to get to cd /system/etc/init.d but each time i type it in it says "cd /system/etc/init.d: not found:
Click to expand...
Click to collapse
Just did it on my phone using Connectbot and no issues. I don't know.
Would anyone else like to chime in with assistance?
Okay connect bot worked but now it won't let me run "remount rw". It says "mount: can't find rw in /proc/mounts
Try "mount -o remount,rw /system" or similar
And it could be possible the init.d directory isn't there...
sent from my miui-ified epic
Thanks for your help. I was trying to copy a file to the system/etc/init.d directory through emulator since I've never done it before. Decided to save some time and use Root Explorer.
Hi,
I recently had to unroot and I backed up all my data from the SD card. After flashing CWM again I (ADB) pushed my backup back onto the SD card. (Yes, I know it's not really a SD card).
Now I can't take any pictures because the camera app throws a permission error. It's not crashing, it simply doesn't save the images.
But a logcat says more then I can:
Code:
E/CameraStorage( 4453): Failed to write image
E/CameraStorage( 4453): java.io.FileNotFoundException: /mnt/sdcard/DCIM/Camera/IMG_20120131_111328.jpg: open failed: EACCES (Permission denied)
E/CameraStorage( 4453): at libcore.io.IoBridge.open(IoBridge.java:406)
E/CameraStorage( 4453): at java.io.FileOutputStream.<init>(FileOutputStream.java:88)
E/CameraStorage( 4453): at java.io.FileOutputStream.<init>(FileOutputStream.java:128)
E/CameraStorage( 4453): at java.io.FileOutputStream.<init>(FileOutputStream.java:117)
E/CameraStorage( 4453): at com.android.camera.Storage.addImage(Storage.java:58)
E/CameraStorage( 4453): at com.android.camera.Camera$ImageSaver.storeImage(Camera.java:995)
E/CameraStorage( 4453): at com.android.camera.Camera$ImageSaver.run(Camera.java:935)
E/CameraStorage( 4453): Caused by: libcore.io.ErrnoException: open failed: EACCES (Permission denied)
E/CameraStorage( 4453): at libcore.io.Posix.open(Native Method)
E/CameraStorage( 4453): at libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
E/CameraStorage( 4453): at libcore.io.IoBridge.open(IoBridge.java:390)
E/CameraStorage( 4453): ... 6 more
ls -al shows the following for /sdcard/DCIM and /sdcard/DCIM/Camera
Code:
drwxrwxr-x root sdcard_rw 2012-01-29 20:53 DCIM
drwxrwxr-x root sdcard_rw 2012-01-28 15:36 Camera
Can someone please tell me where the permission error is?
Thanks.
I had the same issue as you.
The underlying permissions might be messed up. See if the permissions in /data/media look correct. (Things shouldn't be owned by root/0)
This worked for me -- install busybox, then this:
Code:
./busybox chown 1023:1023 -R /data/media
dlzinc: you just fixed a huge issue for me. I was having issues removing files in /sdcard, and my media players couldn't view the album art in my music folder. It was driving me nuts. The command you posted fixed it.
I have no idea how the /data/media permissions got messed up
dlzinc: thanks to you, I've resolved my issue of not being able to write to the sdcard on my nexus phone after i upgraded yakju 4.0.4 to 4.1.1 and didn't managed to push busybox over. Installing the latest busybox and changing the owner of /data/media as you suggested worked for me.
For those who may be searching for similar solutions, the symptoms i faced were:
Camera not able to save any photos
SwiftKey not able to update language packs
Installed BusyBox, now how do I put in that piece of code?
bellerophon90 said:
Installed BusyBox, now how do I put in that piece of code?
Click to expand...
Click to collapse
Launch Terminal Emulator, and enter the command there, like so:
Code:
cd /system/bin/
./busybox chown 1023:1023 -R /data/media
dlzinc, thank you so much for this. Your code fixed my issue as well. I went the more round about way of using adb shell from PC when the phone was connected to it via USB to run the code, but the results are the same.
I did exactly that and it came up permission denied? How do I fix these permissions?
Sent from my Galaxy Nexus using xda app-developers app
bellerophon90 said:
I did exactly that and it came up permission denied? How do I fix these permissions?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You have to make sure that you are SU in the terminal emulator before you run the command. At the first prompt just type "su" and give the app superuser permission. You should be able to run the command after that.
Thanks guys so much! its fixed now.
This didn't work at at all for me. I have a toro. Does that make a difference?
I think this is happening because I copied my old micro SD pictures to my Win 7 PC, and copied them on to the SGN. So there's an ownership problem on the /data/media/DCIM/Camera folder (bekit thinks) and now it's constantly force closing. I thought it was all the ROMs I was flashing...
Thanks heaps! Camera wouldn't save any images after update to 4.1.1....this fixed the problem...all working now!
sorry but...
lokety said:
Launch Terminal Emulator, and enter the command there, like so:
Code:
cd /system/bin/
./busybox chown 1023:1023 -R /data/media
Click to expand...
Click to collapse
can i get a lil noob help here Ok so it seems this is the fix i need as i just went to 4.1.1 and pushed my backup - now this issue. Thing is I cant get this busybox command to work (this is the first time using terminal emulator or busy box) so i have both apps installed - but when i go to terminal and input the code i get 'busybox not found'... Is there a way to do without busybox or..? according to the busybox app it has been installed (went through it all). Any help is much appreciated!
Is busybox installed in that location or somewhere else? On my phone it's in/system/xbin/, not bin.
Sent from my Galaxy Nexus using Tapatalk 2
skols said:
Is busybox installed in that location or somewhere else? On my phone it's in/system/xbin/, not bin.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
according to busybox app it says installed to /system/xbin/ ....
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
skols said:
dlzinc, thank you so much for this. Your code fixed my issue as well. I went the more round about way of using adb shell from PC when the phone was connected to it via USB to run the code, but the results are the same.
Click to expand...
Click to collapse
can this also be done using the gnex toolkit (i otice it has a command line option) ? can you tell me what to type in? :crying: thanks!
hmmmm82 said:
according to busybox app it says installed to /system/xbin/ ....
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
can this also be done using the gnex toolkit (i otice it has a command line option) ? can you tell me what to type in? :crying: thanks!
Click to expand...
Click to collapse
I actually used the adb command from the cmd window after navigating to where my adb.exe was located ("Program Files(x86)\Android\android-sdk\platform-tools" for me). I don't remember everything I did though. Before that doing that though, try the terminal emulator first. After you open it, make sure you are SU. If the prompt is a #, then you are. If not, type su and hit enter. You'll have to give the app superuser permissions. After that's done run the following:
cd /system/xbin/
./busybox chown 1023:1023 -R /data/media
That should do it if busybox is installed in /system/xbin/ . If not you could try the gnex toolkit command line option when your phone is plugged into the USB. I don't have that installed on the computer I'm on now, so I can't say for sure. You'll have to navigate to the same place on your phone and run that same busybox command again, but you'll be doing from that command line instead.
I hope this helps!
skols said:
I actually used the adb command from the cmd window after navigating to where my adb.exe was located ("Program Files(x86)\Android\android-sdk\platform-tools" for me). I don't remember everything I did though. Before that doing that though, try the terminal emulator first. After you open it, make sure you are SU. If the prompt is a #, then you are. If not, type su and hit enter. You'll have to give the app superuser permissions. After that's done run the following:
cd /system/xbin/
./busybox chown 1023:1023 -R /data/media
That should do it if busybox is installed in /system/xbin/ . If not you could try the gnex toolkit command line option when your phone is plugged into the USB. I don't have that installed on the computer I'm on now, so I can't say for sure. You'll have to navigate to the same place on your phone and run that same busybox command again, but you'll be doing from that command line instead.
I hope this helps!
Click to expand...
Click to collapse
That did it! thanks so much not sure what the issue was but its all good now!
You're welcome! I'm glad it worked for you.
Sent from my Galaxy Nexus using Tapatalk 2
dlzinc said:
I had the same issue as you.
The underlying permissions might be messed up. See if the permissions in /data/media look correct. (Things shouldn't be owned by root/0)
This worked for me -- install busybox, then this:
Code:
./busybox chown 1023:1023 -R /data/media
Click to expand...
Click to collapse
Thanks guys, this solved my problem with the camera and several other applications, who shows "write errors".
/Hermann
This worked perfectly!! Thanks guy!