So I just flashed a new rom to try it. Because i didnt liked it I reflashed my backup and since then I'm not able to use my internal storage. I can't take pictures, can't take photos I'm not even able to listen to music or copy files to the internal storage.
How can I fix this? Is there any solution?
Could it possibly be a permissions or file ownership problem?
What kind of error messages do you get? Are there any folders it does allow you to write?
If you can ADB shell into the phone, try:
cd /data/media
ls -l
ls -n
and show us the output of those commands.
It says that the internal storage is maybe already in use.
I'll try to reset everything to stock.
Edit:
Okay just did this in adb shell.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, so for some reason everything on your internal storage has the root user listed as the owner. This is a problem I once had when I pushed in the contents of my internal storage over ADB in recovery after a full wipe. Is that perhaps something you did in the process of reflashing your phone at some point?
Reboot into ClockwordMod Recovery. Plug in the USB and open an adb shell.
Enter the following:
cd /data/media
chown -R media_rw.media_rw *
Then reboot and see if you still have the problem. This does not wipe or modify your files - it just changes the ownership flag.
This should recursively change the ownership of the internal storage files so that you can read/write them in the OS properly. You *must* do this from recovery and not from ADB in the OS, because chown does not support the -R option when booted into the OS.
Is it okay if I did it that way?
Edit:
I can't even flash another radio/recovery or anything from the bootloader.
Edit2:
Still nothing works.
Edit3:
If I flash a new rom shouldn't it change the permissions?
I'm sorry, I made an error. In recovery, before you enter any commands, go to mounts/storage and mount data. Then try the commands.
Thank you this worked.
Is it right that it looks like this?
Yes, that looks better. Are you now able to read/write files in the OS?
Yes. Everything works as it should. I'm not sure about flashing anything from the bootloader but I'll ask again if I need any help.
Thank you very much.
Welcome! And to think I'm just a Linux noob myself too It just happened that I'd had this exact problem before.
.
cmstlist thanks il try this to fix my problem aswel!
Related
I just tried to adb push a file into system\customize\resource folder (for custom bootanimation) and got a "failed to copy" message saying it is a read only file system... does this mean im not fully rooted?
Thanks in advance and sorry if this is the wrong forum or anything, this is my first post on here...
run adb shell, if the prompt looks like this
Code:
#
youre rooted. the problem is that the root filesystem, or / , is set to readonly after the system as booted. if you want to push into root, you need to remount it as read write, or push the file while youre in recovery.
yeah i have the # when i run shell.... thanks for the quick response! i was able to push the file after that =)
glad i can help, work is slow today
nenn said:
run adb shell, if the prompt looks like this
# youre rooted. the problem is that the root filesystem, or / , is set to readonly after the system as booted. if you want to push into root, you need to remount it as read write, or push the file while youre in recovery.
Click to expand...
Click to collapse
New guy here trying to use the search to get an answer to my question.....sorry for bumping an older thread. What is the command to "remount it as read write"
Also, I'm booted into recovery (Amon RA), but still can't seem to write to the system folder. Coincidentally, I too am toying with a custom boot animation.
Thanks to anyone who can help!
erikivy said:
Also, I'm booted into recovery (Amon RA), but still can't seem to write to the system folder. Coincidentally, I too am toying with a custom boot animation.
Click to expand...
Click to collapse
If you're booted into recovery, the filesystem usually mounted on /system isn't mounted. That's kinda the point.
So if you need to write to it, mount it first.
posguy99 said:
If you're booted into recovery, the filesystem usually mounted on /system isn't mounted. That's kinda the point.
So if you need to write to it, mount it first.
Click to expand...
Click to collapse
Thanks for your speedy reply. I'm sorry to be a dunce, but once again, what is the command to "mount it?" I'm guessing I do it via ADB, right?
I think you are looking for the command: remount rw
elegantai said:
I think you are looking for the command: remount rw
Click to expand...
Click to collapse
Thanks! Headed off to try it now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
edit: YES! It's the simple things that bring so much joy. It worked perfectly, Bro. Thanks again.
So I have a rooted Evo and am wondering how the heck do I open up a shell? I'm trying to see if I my Evo is properly rooted and it says I need to open up a shell so I can check for this. I'm guessing it's like opening a Linux terminal but I have no idea how to do this on my phone and it seems like it's a fairly common thing. Should I have access to an adb shell after rooting? I am new to all of this so please go easy on me...
PC-48 said:
So I have a rooted Evo and am wondering how the heck do I open up a shell? I'm trying to see if I my Evo is properly rooted and it says I need to open up a shell so I can check for this. I'm guessing it's like opening a Linux terminal but I have no idea how to do this on my phone and it seems like it's a fairly common thing. Should I have access to an adb shell after rooting? I am new to all of this so please go easy on me...
Click to expand...
Click to collapse
Just try downloading an app that requires root... like Titanium backup or wifi tether... all on the market...
or goto your tools folder from the SDK..with your phone plugged into your computer...on charge mode.... from a command prompt type "adb shell" and then if you get a "#" you are rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
that is for the terminal emulator for your phone. Or just grab it from the market:
'Android Terminal Emulator' by Jack Palevich
Ok so I downloaded that app using the barcode scanner and it runs so I must be properly rooted. I'm just wondering what the SDK is that apristel mentioned. I'm guessing Software Development Kit but I don't have one of those that I am aware of. I used the Terminal Emulator and typed in adb shell and it responded with "adb: permission denied". I'm just trying to learn about how all of this stuff works, Thank you for your help so far.
PC-48 said:
Ok so I downloaded that app using the barcode scanner and it runs so I must be properly rooted. I'm just wondering what the SDK is that apristel mentioned. I'm guessing Software Development Kit but I don't have one of those that I am aware of. I used the Terminal Emulator and typed in adb shell and it responded with "adb: permission denied". I'm just trying to learn about how all of this stuff works, Thank you for your help so far.
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html
After you install that you will be able to open command prompt (windows) and type adb shell (when device is pluged in and in usb mode) to get shell access via your pc.
Ahh! Ok it's all starting to make sense now. By "usb mode" do you mean the Disk drive option or is it the Charge only option? I'm talking about the Connect to PC options...
I think he means usb debugging mode and charge only.
vbyt said:
I think he means usb debugging mode and charge only.
Click to expand...
Click to collapse
Yeah thats exactly what i meant. thanks for clearing that up.
Hi Guys, Im attempting to gain root for the first time on my (Telus Desire HD). I am well aware that I need to downgrade but cant get, dont understand the following...
B.a Downgrade Process
1- Copy the PD98IMG.zip file from the "Step 1 - PD98IMG" folder and put it on the root of your SD card (i.e. not in any folders). Do NOT rename this file.
2- Go to the "Common files" folder and double click Start Here.
3- Copy the files in "Step 3 - Downgrade" to the "Common files" folder.
4- In the new command window that opens, type the following commands (you shouldn't get any errors. hit enter after each):
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell[/B]
When asked to copy the files in step 3- "Downgrade" to the common files folder... where was I supposed to locate this??? is it supposed to b on my computer C drive where it was downloaded to was I supposed to copy that too to the phone external drive.
Plain & simple the 4th step the new command window doesnt open & attempting to re-open after copying the files to the common folder doesnt give the "#" symbol when im finnished. Tried multiple times. Also phone is set to usb debugging... but should it be mounted, charge only, or htc sync?
Thanks any help greatly appreciated.
Not wanting to quite & keep trying I attempted to find out @ which step the cmd stopped working or responding. when entering the...
adb shell chmod 777 /data/local/tmp/psneuter portion of the above task this is the message that came back.
Failed to set prot mask (inappropriate ioctl for device)
I also noticed that htc sync stopped working after the first of 5 lines.
Also being a noob, I need to complete 10 replies before asking those in the development portion ss yeah sorry.
Another note: to which led me to the need to get root access soon is that telus just released an OTA update that doesnt work, so much that did work now doesnt or fails every 10 seconds.
Still no luck today, same responses as above.
All of the telus related posts I have read suggest using the same method but I havent read anyone getting stuck at this simple step so early on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what I get. I have also tried from other locations and I get the same result. Please help.
The attached is a pic of what i get in the cmd
the common folder is in the telus desire hd folder after you have extracted the package.
Thanks, I was aware of that. I think mabey the whole issue has something to do with the lame OTA update i just installed. It Changed my software # to 2.43.661.1
As I have been made aware by other topics... Version 2.3 + can not yet be downgraded.
Would be quite interested in knowing when I can downgrade version 2.43.661.1
Learn how to predict the future then Because nobody knows.
Sent from my Desire HD using Tapatalk
Ok, so most of you probably already know people can screen shot your snapshot stuff, but you will obviously know.. Root users know you can just grab them without opening..How do you do so?
On the S3, you just open root explorer or something similar, go to data/data/apps/com.snapchat or w/e, then go to cache, and then theres a received image folder but at /sdcard/android/data/com.Snapchat.Android/cache is the videos. Just take whats in those, copy them, paste them somewhere on your sd card thats easily accessible, and then remove the .nodata at the end so only the image type of video format remains. Then, you have the images, actually saved, never expires, and they dont appear as opened on snapchat unless you press the button.
Remember, be careful of what you send people =p
I made a post asking if anyone who knows scripting wanted to make a script to go to the folders and grab them and drop them into a easy access folder and remove the .nodata at the end but there was no hits on that =p
When I go into the recieved images folder, theres nothing there....
Script coming...
EDIT: I need the exact path to each image
Or am I right in thinking that is like this?
com.xxxx/cache/receivedImages/xxxxx.nodata
@ReapersDeath
Script is finished and working, I just need the path now. Just give me a sample path to 1 image and 1 video
Images are each named differently so nothing specific but for images, /data/data/apps/com.Snapchat.Android/cache/received_image_snaps/xxxxx.jpg.nodata
Correcting myself from op, but for videos /sdcard/android/data/com.Snapchat.Android/cache/received_video_snaps/xxxxxx.mp4.nodata
So this script copies them to a new location and removes the .nodata?
And is there a way you could make this script into like a widget that you press and it does It? Or any app you know
Also, for videos I've noticed, when ever you open an app over Snap chat, videos instantly unload, ie the folder disappears for videos. Forcing you to use multi Window and root explorer to load the video and grab it without shrinking Snap chat
Code:
#!/system/bin/sh
OUT=/sdcard/snapchat
IN=/data/data/com.snapchat.android/cache
IMG=received_image_snaps
VID=received_video_snaps
su
mkdir -p $OUT/$IMG
mkdir -p $OUT/$VID
cd $IN/$IMG
for file in *; do name=${file%.*}; busybox cp $file $OUT/$IMG/$name; done
cd $IN/$VID
for file in *; do name=${file%.*}; busybox cp $file $OUT/$VID/$name; done
echo "Finished."
exit
exit
There you go. Just copy and paste that into an app like Script Manager and run it
It will make a folder on your internal storage called "snapchat" with 2 subdirectories, 1 for images and 1 for videos
It will make the folder, but retrieve no images or videos as I can see.
Figured it out. Have to mount system as r/w. Could you throw something in that changes it to r/w then back to r/o?
Also in the video folder only images show up. Won't get videos
Here it is with the mounting, sorry my mounting is set to rw by default so I didn't catch that
As for the other part, I don't know, I tested it and it pulled from both folders...
Let me try again
EDIT: Just tried it again and it works fine..
Code:
#!/system/bin/sh
OUT=/sdcard/snapchat
IN=/data/data/com.snapchat.android/cache
IMG=received_image_snaps
VID=received_video_snaps
su
mount -o remount, rw /system
mkdir -p $OUT/$IMG
mkdir -p $OUT/$VID
cd $IN/$IMG
for file in *
do name=${file%.*}
busybox cp $file $OUT/$IMG/$name
done
cd $IN/$VID
for file in *
do name=${file%.*}
busybox cp $file $OUT/$VID/$name
done
mount -o remount, ro /system
exit
Must be something with the moar rom with app priorities. Maybe it closes down snapchat instantly. Anyways, how could I get this to work with script Manager? I made the script into a file, but when I click the script, and then run, only the prompt console comes up without the code placed in
More specifically I press the widget assigned to the script, and get this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doesn't want to run it the easy way.
Edit: the script isn't mounting the system. Still having to manually
Aren't there apps in the playstore that do this for you?
Sent from my Nexus 7 using xda app-developers app
Rename it so that it has no spaces in its name
CNexus said:
Rename it so that it has no spaces in its name
Click to expand...
Click to collapse
Didn't work.
Discard
Anyone have any idea why it won't launch the script? No spaces or caps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is not my device (this is just a stock picture so you know what device I am talking about)
Guys I have a Telstra T-Hub 2 that is in dire need of root.
I can't find any method to root the device.
So far I've got the USB drivers installed, and I can access the device with 'adb devices' and 'adb shell'
I've moved busybox and su to /data/local/tmp but no matter what I do I cannot move anything to /system/bin
The tablet is running Stock ICS 4.0.4. It's not modified in any way (yet).
I have the ability to open Android System Recovery (3e)
But there seems to be NO download mode on the device at all.
Tried cmd > adb reboot download - Device just reboots normally... (reboot recovery, does work, and reboots into recovery)
I can hold Volume - & Power that gives me a dead android screen, then I can press Power & Volume + which gets me to 'Android System Recovery 3e' however no matter what button combination I use. I cannot find some sort of 'download mode'. There doesn't seem to be one on the device....
So, so far I have only Android Stock System Recovery 3e and rebooting into 'Bootloader'. No download mode. So I cannot seem to find a way to browse the '/' root partition with a computer, (especially with SU permissions).
Do you have any advice at all?
Stuff I've tried:
SuperOneClick - Permissions denied
Cydia Impactor - cannot create /system/xbin/su: Read-only filesystem
Towelroot - Device unsupported
Kingo root - Device just reboots and doesn't root
Universal Root.zip from stock Android System Recovery (3e) - Signature verification of whole-file failed
Pushing su to /system/bin (from data/local/tmp/) - Permission denied
./psneuter (in data/local/temp) to try and get a root adb shell - failed to set prot mask (invalid ioctl for device)
Guys nothing is working. I'm raking my brain. There has to be a way to get rood privileges on this device.
Someone talked about flashing a custom restore on the device set to install an .apk in a weird place that gave root. But he didn't bother explaining how he did it
Does anyone have any information at all? I'd be happy to buy you a coffee if you can help me get root on this thing.
Thanks again!