[Q] Rooting Problem...Folder not found - myTouch 4G Q&A, Help & Troubleshooting

Please forgive me if this is covered in an earlier thread. I searched several different ways and found nothing.
I've been temp rooted with Visionary for a several months now with no real problems. Recently I decided to perma-root and try some other ROMs. I double checked all my settings and downloaded the appropriate root files and loaded them to the root directory of my sd card. When I open the Terminal Emulator and start going through the commands:
su
cd/sdcard/root
I get a "cd/sdcard/root: not found" response...?
I've double checked the location of the Root folder both using a file explorer and connecting to my computer. Is it my sd card? I haven't had any problems that I know of...?
Any help would be appreciated...

What bootloader do you have
pedaler said:
Please forgive me if this is covered in an earlier thread. I searched several different ways and found nothing.
I've been temp rooted with Visionary for a several months now with no real problems. Recently I decided to perma-root and try some other ROMs. I double checked all my settings and downloaded the appropriate root files and loaded them to the root directory of my sd card. When I open the Terminal Emulator and start going through the commands:
su
cd/sdcard/root
I get a "cd/sdcard/root: not found" response...?
I've double checked the location of the Root folder both using a file explorer and connecting to my computer. Is it my sd card? I haven't had any problems that I know of...?
Any help would be appreciated...
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA Premium App

You're missing the spaces.
And "root directory" means - NO directory. You should have copied the files to your SD card without putting them into any directory on it.
The command looks like that/:
cd /sdcard/

Make sure you didn't unzip the files...
Edit: sorry, don't unzip roms! But you haven't gotten that far! Sorry about that, my mistake.
Sent from my HTC Glacier using XDA App

pedaler said:
Please forgive me if this is covered in an earlier thread. I searched several different ways and found nothing.
I've been temp rooted with Visionary for a several months now with no real problems. Recently I decided to perma-root and try some other ROMs. I double checked all my settings and downloaded the appropriate root files and loaded them to the root directory of my sd card. When I open the Terminal Emulator and start going through the commands:
su
cd/sdcard/root
I get a "cd/sdcard/root: not found" response...?
I've double checked the location of the Root folder both using a file explorer and connecting to my computer. Is it my sd card? I haven't had any problems that I know of...?
Any help would be appreciated...
Click to expand...
Click to collapse
If i remember correctly its cd /data/local not cd/data/local make sure you hit the space bar between cd and /

This was the culprit....I didn't have a space in the correct place. I can't believe I over looked that one...Thanks

Related

[Q] can't cd to /sdcard/root

So this is my first Android phone..
And I am wanting to use it to its full extent..
I have the 2.2.1 Version Mytouch 4g..
Downloaded..
Astro..
Terminal Emulator..
Visionary r11..
Also the root.rar file..
I extracted the root.rar file..
And got the Root folder..
Placed it into the root of my sd card..
And when I go to Terminal Emulator..
After running Visionary for root access..
I type in the Command..
"cd /sdcard/root"
And I get..
"cd: can't cd to /sdcard/root
What am I doing wrong..?..
Any pointers would be much appreciated..
Thank you in advance..
Syph3r03 said:
So this is my first Android phone..
And I am wanting to use it to its full extent..
I have the 2.2.1 Version Mytouch 4g..
Downloaded..
Astro..
Terminal Emulator..
Visionary r11..
Also the root.rar file..
I extracted the root.rar file..
And got the Root folder..
Placed it into the root of my sd card..
And when I go to Terminal Emulator..
After running Visionary for root access..
I type in the Command..
"cd /sdcard/root"
And I get..
"cd: can't cd to /sdcard/root
What am I doing wrong..?..
Any pointers would be much appreciated..
Thank you in advance..
Click to expand...
Click to collapse
Make sure phone is not connected to computer via usb cable.
Sent from my HTC Glacier using XDA App
Phone is not connected by usb..
Has been ejected and unplugged from computer upon adding root file..
One thing to Mention is..
In my application block I have the superuser Icon..
And I can select it and use it..
But if I go to Terminal emulator, and type su..
I get permission denied..
Although when I did try to Root the phone..
I went thru Visionary..
Checked the r/w box did the root.. on r11..
Then went to type the..
"cd /sdcard/root"
And that is when i got the..
"can't cd to /sdcard/root"
Try using Visionary 14, I was having the same issue reading the SD card figured it had to do with something with the root. I'm sure you can find the link in the forums
Sent from my HTC Glacier using XDA App
Syph3r03 said:
So this is my first Android phone..
And I am wanting to use it to its full extent..
I have the 2.2.1 Version Mytouch 4g..
Downloaded..
Astro..
Terminal Emulator..
Visionary r11..
Also the root.rar file..
I extracted the root.rar file..
And got the Root folder..
Placed it into the root of my sd card..
And when I go to Terminal Emulator..
After running Visionary for root access..
I type in the Command..
"cd /sdcard/root"
And I get..
"cd: can't cd to /sdcard/root
What am I doing wrong..?..
Any pointers would be much appreciated..
Thank you in advance..
Click to expand...
Click to collapse
I had that same trouble rooting my phone. My problem was that I didn't realize that the .rar was a different type of compression and needed a different extractor. I suggest uninstall visionary and superuser. Remove the battery and reboot. Then install visionary and temp root. Then try "su" in terminal again. That should work. Make sure you are using visionary r11+ also. I made the mistake of downloading just plane r11 that doesn't have the options that are necessary to permaroot.
skidooman said:
I had that same trouble rooting my phone. My problem was that I didn't realize that the .rar was a different type of compression and needed a different extractor. I suggest uninstall visionary and superuser. Remove the battery and reboot. Then install visionary and temp root. Then try "su" in terminal again. That should work. Make sure you are using visionary r11+ also. I made the mistake of downloading just plane r11 that doesn't have the options that are necessary to permaroot.
Click to expand...
Click to collapse
Thank you all for your continued support..
I am starting to feel as if my phone is unable to be rooted.. lol..
I have tried using r11+ and r14+ in order to root my phone..
Each and every time I get to the Terminal Emulator and input the first command I get the error message..
Maybe using winzip to extract the root file, is not the correct software to use..?..
If anyone still needs an answer to this question, I might have one. This issue just occurred for me on my mt4g, it was a real palmslap to the forehead when I realized what I had done. I put the files from the "root" folder into the root of the sdcard. So when it said "can't cd to /sdcard/root" it was because the folder root didn't exist and /sdcard/ held the files I wanted. In other words, put the entire folder named root onto your sd card and not just the files.
Hopefully this might help someone who made the same foolish mistake I did.
skidooman said:
I had that same trouble rooting my phone. My problem was that I didn't realize that the .rar was a different type of compression and needed a different extractor. I suggest uninstall visionary and superuser. Remove the battery and reboot. Then install visionary and temp root. Then try "su" in terminal again. That should work. Make sure you are using visionary r11+ also. I made the mistake of downloading just plane r11 that doesn't have the options that are necessary to permaroot.
Click to expand...
Click to collapse
After SU...
Type cd(space)/sdcard/root
Then do the rest
Smile when it starts to work
After SU...
Type cd(space)/sdcard/root
Then do the rest
Smile when it starts to work
im still having the same problem any suggestions?
I type in the Command..
"cd /sdcard/root"
And I get..
"cd: can't cd to /sdcard/root
formeka909 said:
After SU...
Type cd(space)/sdcard/root
Then do the rest
Smile when it starts to work
im still having the same problem any suggestions?
I type in the Command..
"cd /sdcard/root"
And I get..
"cd: can't cd to /sdcard/root
Click to expand...
Click to collapse
First try to cd to /sdcard. If that works type ls that is LS but lowercase. Look for root in the response. If it is not there, the directory doesn't exist.
If you can't change to /sdcard try cd /mnt/sdcard
My phone's directory structure is /mnt/sdcard.
Edit:
Just tried /sdcard, it worked. Then I tried to cd to a folder by not using proper caps, that worked too. Last I tried to cd to a folder that didn't exist and got the same error. You are telling terminal to change to a directory that does not exist, meaning, there is no folder named root on the sdcard.
Sent from my HTC Glacier using XDA App
1) download the root.rar file
2) unzip to the sdcard
3) make sure the folder name is "root"
4) make sure the folder named "root" is actually in the SDcard
5) open terminal emulator
6)
Code:
su
cd /sdcard/root
sh root.sh
BEFORE DOING ANY OF THIS, YOU MUST HAVE ALREADY TEMP ROOTED USING VISIONARY. and when you use visionary to root, MAKE SURE USB DEBUGGING IS ON OR IT WILL NOT WORK!!
IF NOTHING WORKS FOR YOU, THEN TRY THING GFREE METHOD HERE: http://forum.xda-developers.com/showthread.php?t=858996
the files u copied from the zip folder...save it on sdcard with the folder named root...
cd (space) sdcard/root
.sh root.sh

ADB vs. Root Explorer vs. Terminal on device

With certain files, SteelH describes using Root Explorer as "like trying to swap the engine of a car while it's running"
I experienced this as I tried to copy back a modified services.jar file with Root Explorer. I ended up using ADB and it worked fine.
Question 1: I did this while the phone was running/OS loaded, but ADB copy method worked while Root Explorer didn't. Why? Does ADB have higher authority in some way?
Question 2: How about using a terminal window on the phone to copy/replace files (if a computer is not handy)? Does it yield the same function/result as Root Explorer or ADB?
Question 3: If I simply want to back up the file, say services.jar or framework.apk, to be copied to SD, can I use Root Explorer for that?
Thanks.
snovvman said:
With certain files, SteelH describes using Root Explorer as "like trying to swap the engine of a car while it's running"
I experienced this as I tried to copy back a modified services.jar file with Root Explorer. I ended up using ADB and it worked fine.
Question 1: I did this while the phone was running/OS loaded, but ADB copy method worked while Root Explorer didn't. Why? Does ADB have higher authority in some way?
Question 2: How about using a terminal window on the phone to copy/replace files (if a computer is not handy)? Does it yield the same function/result as Root Explorer or ADB?
Question 3: If I simply want to back up the file, say services.jar or framework.apk, to be copied to SD, can I use Root Explorer for that?
Thanks.
Click to expand...
Click to collapse
i can't answer all of these authoritatively, but i will say
-i find adb to be the easiest way to do ANY modifications, as long as you know just a handful of commands and remember to remount. also remember to pull anything you are getting ready to mess with, just in case you bork it up. takes a lot less time to push an unmodified file than it does to do a complete restore. especially if you forgot to backup, lol
-if you have a terminal app mounted with rw privileges, you can move whatever you want wherever you want. however, referring back to my last point, adb is easier. i find that trying to type type type things out on a dinky little keyboard is a bigger pain in my butt than using my full size one, especially when i can use cut/paste from the intertubes.
-i think rooted explorere shouldn't have a problem copying a file from /system/ or /data/ to some folder on your sdcard
Thank you for the information. I just copied a file with terminal (on phone) and Root Explorer. Interesting thing: using the CP command, the file that was copied onto the SD showed the current date. The file that was copied using RE has the original date.

[Q] rooting from the sdcard

Im trying to root my g2. 2 weeks ago i stumbled on a web page that explained how to do this but I was at a work computer and i can't find it anymore. what i remember is that u dont have to install adb on your computer. u put it in a folder in your sdcard and run terminal emulator to start the rooting process. But thats all i remember. Im missing something. I don't know what. Please somebody help me. Any advice?
This method can be done from the phone for the G2, but apparently people were having issues with the Desire Z.
http://forum.xda-developers.com/showthread.php?t=928160
Just go to the Dev forum and check the Wiki. Most rooting methods that require ADB can be accomplished with manually putting the files in the correct directories on your SD card and using the Terminal Emulator app on the phone to execute the commands.

[Q] NS4G Rooted still can't access any files in /root/

First off, I have a Nexus S 4g from Sprint (d720) rooted using the method as posted in the thread titled "[GUIDE] Nexus S 4G Simple Root/Unroot" by kpkimmel back a few weeks ago when that was the ONLY method available.
I am trying to edit an XML file located in my /root/data/data/ directory but I can't access it from adb shell nor the app "Root Explorer", I can however see and 'cd' to the directory but it shows up empty on both "Root Explorer" and through adb . As it seems, I don't have the proper permissions to be able to view/edit the files/folders in the root folder.
SuperUser permissions have been granted for both adb shell and Root Explorer as well so I know that part is in order. I guess I could just be missing an obvious step in accessing the /root/data folder but any help would be greatly appreciated.
Should I just unroot my device and re-root using a different method? Anybody with adb and permissions issues experiences please help. I'm more than frustrated at this point.
Thanks in advance.
try mounting it as rw
Would you be able to list the steps please?
Top right of the page, hit read write
Sent from my Nexus S 4G using Tapatalk
My /root contains nothing either. What is it exactly you want to edit?
its a empty folder.

[SOLVED] Adb Access Denied on Rooted Kindle Fire

Hi everyone. As a new Kindle Fire user, I bought mine AFTER the recent Kindle 6.2 update. After following step-by-step the instructions posted on this forum to root KF, I seemed to have succeeded at my first attempt. However, when trying to copy and paste either vending.apk or amarket.apk to system/app folder using File Expert which I got from Amazon store, I couldn't get it to work. This means I don't see either apps in the system app folder after I paste them there. I followed the instructions to the T and rebooted KF, still no show. I then tried to install it via adb, I was able to "adb install" googleservice frameworks on KF. But when trying to "adb push" the market app to system/app, I keep getting "adb access denied". I tried re-rooting with superoneclick, still can't "adb push".
I really don't know what went wrong. BTW, I could hard install the market app on to KF and gained access to the market. (I thought KF blocked it.) But all my download from android market seem unsuccessful. I need help. Thanks.
Problem solved. And here's what I found out and how I made it work. Thanks for everyone who posted to help.
After trying what everyone suggested here, I still couldn't get r/w perssion to the system folder. I reset my KF to factory setting and started all over again. This time I realized it was the File Expert app that's causing this problem. Although it seems like File Expert could gain full access to the system, it doesn't allow you to make any modification to the system folder. I know someone claimed it worked on theirs. But if your File Expert comes from Amazon app store, it DOES NOT work when you try to paste anything into the system. When I realized that ROOT EXPLORER is no longer available on Amazon, I figured that could be the reason. After downloading Root Explorer to my PC and installed it onto KF, everything worked like a charm! So for those of you who encounter similar problems, it's not you. It could be the File Expert app that you got from Amazon.
You need to mount system as writable
Thanks Felnarion. But I did that. It didn't help. I followed the instructions step by step. Don't where the problem is. I find it hard to believe that KF allows me to do regular install of android market(the market icon even shows on the carousel) but I can't do it the "sneaky" way? Anyone else tried installing market app directly from the sd card?
In that case I think it's your app. I just downloaded file expert and had problems copying to /system as well.
Try root explorer, haven't had any problems with it.
File Expert is broken in regards to mounting folders RW/RO. Even though it claims it has successfully changed permissions, it never does or they don't stick. I suffered the exact same issue, regarding mounting folders RW/RO, and had to install Root Explorer to get the job done.
Code:
mount -o rw,remount -t ext4 /dev/block/platform/mmci-omap-hs.1/by-name/system /system
is the adb command
nycrare said:
However, when trying to copy and paste either vending.apk or amarket.apk to system/app folder using File Expert which I got from Amazon store, I couldn't get it to work. This means I don't see either apps in the system app folder after I paste them there. I followed the instructions to the T and rebooted KF, still no show. I then tried to install it via adb, I was able to "adb install" googleservice frameworks on KF. But when trying to "adb push" the market app to system/app, I keep getting "adb access denied". I tried re-rooting with superoneclick, still can't "adb push".
Click to expand...
Click to collapse
This might be a dumb question, but did you
Code:
su
and click OK on the Superuser prompt on the KF screen prior to the adb push attempts? Were you able to mount /system rw through adb? If adb can't get root access there's no way File Expert will be able to.
devilot said:
File Expert is broken in regards to mounting folders RW/RO. Even though it claims it has successfully changed permissions, it never does or they don't stick. I suffered the exact same issue, regarding mounting folders RW/RO, and had to install Root Explorer to get the job done.
Click to expand...
Click to collapse
File Expert works fine. I've used it to do all my root related installs. You just have to make sure you check the 'Root Explorer' box under Settings>File Explorer Settings before trying to do any /system mounts, it's off by default.
Thank you everyone for your help. If I remember correctly, I did try "su" in adb. but not sure if entered the code correctly. I also heard about File Expert could be the cause when it comes to gaining permissions. I checked root explorer on File expert settings as well. I'm beginning to wonder if my hard install of market app ,which worked to my surprise, messed things up. I will try to reset my KF to factory setting and start over again. I will report back with the result. Once again, I really appreciate everyone's help.
death2all110 said:
Code:
mount -o rw,remount -t ext4 /dev/block/platform/mmci-omap-hs.1/by-name/system /system
is the adb command
Click to expand...
Click to collapse
i have to admit this is the first time I see this code. I tried something similar based on an instruction from another site. But not this exact code. I will try it later.
that command line was a life saver
Saved me a future headache
nycrare said:
After trying what everyone suggested here, I still couldn't get r/w perssion to the system folder. I reset my KF to factory setting and started all over again. This time I realized it was the File Expert app that's causing this problem. Although it seems like File Expert could gain full access to the system, it doesn't allow you to make any modification to the system folder. I know someone claimed it worked on theirs. But if your File Expert comes from Amazon app store, it DOES NOT work when you try to paste anything into the system. When I realized that ROOT EXPLORER is no longer available on Amazon, I figured that could be the reason. After downloading Root Explorer to my PC and installed it onto KF, everything worked like a charm! So for those of you who encounter similar problems, it's not you. It could be the File Expert app that you got from Amazon.
Click to expand...
Click to collapse
Interesting. I was the one it worked for and I'm pretty sure I got mine from the Market, not Amazon. Good thing I haven't clicked that update button from within Amazon App Store.
Thank you for following up. Perfect example of how it can help others.
Glad you got everything sorted.

Categories

Resources