Hello,
I have Lenovo S720 running on Android 4.0.4 that I recently factory reset because It has only few little internal storage (~1,4 GB), and cannot support many updating apps.
After I do that, whats left in the internal storage is about 500 MB of storage, the rest being taken up by the system (I suppose).
I installed Framaroot to root the device, then System App Uninstaller (ROOT) and ES File Explorer.
First, I try to uninstall any bloatware with the System App Uninstaller -> I didn't get much free internal storage.
Then, I use ES File Explorer to seek, which folder took up the most space.
-> One of the is /system/vendor folder.
-> So, I copied that folder to /mnt/sdcard/backupsys/ (or /sdcard/backupsys/ [little bit forget]), Thinking it would come in handy later.
-> Then, I (foolishly) proceed to delete the folder using the root privileges .
-> It took a moment until all of my app start crashing (including the ES File Explorer!).
-> I turned-off the device, and now it still stuck in the (what I think as) "bootloop" mode.
Fortunately I still can communicate to the phone using adb tools, which I have a little knowledge of. But, the pm and am command cannot function well.
Now, I'm only thinking about moving back the vendor folder from /mnt/sdcard to the /system folder.
But I encounter some problem:
1) I can't (& don't know how to) write to the /system
2) I can't (& don't know how to) read from the /sdcard
- command 'ls' inside this dir returned nothing.
Glad I have the "su" tools from the Framaroot. I searched on the Internet and it seems the problem can be solved with mount tools, but I don't know how.
ls -la tools on root (/) return:
(other dir)
root /system ,,,,,,,,,,other info,,,,,,,
system /sdcard ,,,,,,,,,,other info,,,,,,,
(other dir)
So maybe because I can't gain system account, I can't access the folder and read it...
I try to hard-reset in the recovery mode, but I can't select the options! (I can move the selector with volume up/down) but I cant click it with the power button!
The phone seems to be worse every second.
My main question is: can I recover my phone (copying the vendor folder back) using command tools on my development computer? Or is there any other ways?
I'm willing to install any custom ROM best suited to my phone.
Thanks in advance.
Hello,
Welcome to XDA.
If you have a copy of what you deleted or can get it from somewhere and you want to adb push your missing files and folders back to your device then you need to have the files you want to push stored on your PC and push them from there to the device. For instructions on how to use adb read through the thread linked below and go from there.
http://forum.xda-developers.com/showthread.php?t=2141817
If you have further questions or need further help with using adb then you can post in the Q&A forum linked below:
http://forum.xda-developers.com/android/help
Related
So I'm trying to test out the OC Kernel for UD, downloaded the 1.5.1 Kernel tbz2 file, moved it to my Archos, but when I tried to move it to my /data/urukupdate I find that it is missing (the whole urukupdate dir is just not there). My /data is completely empty. Any ideas on how this could have been wiped out and how to restore it without having to wipe and reload everything?
If you have an empty /data directory, you bootet into the wrond android.
You booted into std Android and there you have no root, therefore you can't see anything.
Boot into Developer Edition.
You have to enable root explorer in the filexpert settings and the data folder is the one on the root and not on the storage.
EDIT : To enable root explorer in filexpert:
-Press menu key then press more
-Press settings and go to File Explorer settings
-Scroll down and check "Root Explorer" accept the root acces and you're done
Sorry for my bad english
@ fzelle Actually I uninstalled the android OS, so that I can only boot into UD.
@ Starman this worked! Thanks for your help. I usually use ES file explorer or Astro and I've never had to grant SU access manually before so hadn't thought to look. Thanks!
I downloaded the leaked google music app from ICS, and it works great.
My only caveat is that when I choose to make something available offline, it goes straight to my internal storage (Motorola Atrix).
I have a 32gb microSD card with a dedicated folder for music. Is there a way I can get the offline songs onto there?
I currently use PlayerPro from the market, and I wanted to use the Google cloud for "wirelessly syncing" my music.
Any ideas?
Nobody was able to figure it out?
Does any other music player sync with google?
Wouldn't it be possible to somehow mount a folder that is located on the sd-card and link it to /sdcard/Android/data/com.android.music/cache just like it is done with the apps2ext hacks on low memory devices?
Would the file system of the sd-card then have to be ext instead of fat32?
Maybe someone who has more practical knowledge of the matter could look into this. I can only theoretically assume how it might work
I did some further research and found this post.
It describes how to mount an external sdcard to to /sdcard instead of sdcard. But would this also work with a subfolder of /sdcard?
I fiddled around myself a bit.
So here is what I did:
format sdcard as ext2
manually mount sdcard since it won't automatically when ext:
Code:
mkdir /Removable/MicroSD
mount -r -w -t ext2 /dev/block/vold/179\:9 /Removable/MicroSD
mkdir /Removable/MicroSD/GoogleMusicData
Then move all data from /sdcard/Android/data/com.google.android.music/cache to /Removable/MicroSD/GoogleMusicData/cache
I did this with root explorer since I'm not too much of a terminal h4xx0r.
Delete the folder /sdcard/Android/data/com.google.android.music/
Link the new Folder on external MicroSD Card to the original location via this terminal command:
Code:
ln -s /Removable/MicroSD/GoogleMusicData /data/media/Android/data/com.google.android.music
Since /sdcard is already a link like the one we are setting up here, it is not possible to link to this linked location (/sdcard/Android/data/com.google.android.music).
Instead we have to link to the origninal destination of /sdcard which is /data/media.
Now the microSD card is accessible for root explorer. It shows read and write access.
But google music won't find it. It says that it doesn't have enough space to stream music so I figure that it somehow doesn't have access to the sd card.
What could be the issue here?
Also instead of 28GB free memory root explorer shows me only 364,44MB free memory. the command "df" in terminal however confirms 28GB of free memory.
Help please?
EDIT:
I thought that a reboot might do it. But it doesn't. Instead it gets rid of all the hacking I've done in terminal. So I guess I would have to place a script in /etc/init.d for the link to be set everytime I reboot, right?
Another Fix (no sdcard formatting needed)
This is a fix i figured out piecing together other peoples attempts.
Use this as a script
mount -o bind sdcard2/android/data/com.google.android.music sdcard/android/data/com.google.android.music
Alternately you can change the first location to the location of your choosing as long as it resides on the external as card.
Ex.
Mount -o bind sdcard2/music sdcard/Android/data/com.google.Android.music
will bind:
sdcard/Android/data/com.google.Android.music (google's forced save location)
to
sdcard2/music
Go to google music (play music now) settings and clear any music that is currently saved to your device.
this only applies to music made available offline. If you do not clear it before running the script the music will exist on your internal sdcard but not be accessible.
open script manager and find the script you made
Select it and make sure to click set on boot and superuser
Run Your script.
That is it now your default save location for google music is bound to the location on the external sdcard. the device will see the location as its default but really be saving to the external sdcard.
You can check this by going to google music. Selecting "make available offline" and look at the free space. It should shoe the space available on your external sdcard.
TLR Version (noob version)
I was getting a lot of questions about the preliminary steps here (i.e. rooting, writing script, etc) so i decided to attach the noob version in case anyone needs verification on how to accomplish these steps.
HOW DO I ROOT?
So, Rooting gives you full access and control over your phone. instructions for how to root are device specific. so i would start by searching XDA for "YOUR DEVICE one click root"
ex. samsung galaxy s2 one one click root
some devices are easier to root than others. i cannot provide steps for your particular device, but through XDA, and google you CAN find everything you need.
some devices have one click root tools, some do not, so the rooting process is more in depth for those devices.
rooting instructions are so device specific i could not find a generic set of instructions, and don't want to mislead anyone by linking them to a set of instructions not compatible with their device.
There is a risk of bricking your device (making it inoperable) while rooting, although the risk is minimal... almost non existent if you carefully follow instructions. I have rooted 5 seperate devices without bricking any, and, in most cases even if bricked the device can still be restored.
there are additional benefits to rooting, such as overclocking
for example my Galaxy S2 normally runs at 1.5 GHZ, i have increased the speed to 1.8GHZ
(NOTE** Without XDA DEVELOPERS i would have rooted 0 devices, and probably bricked at least one, so thank you to all of you out there who have helped me, I hope this method will help some of you in return.)
NOW THAT YOU ARE ROOTED...
INSTALL SCRIPT MANAGER..
First, to install script manager just go to google market (Play Store) and search for script manager
INSTALL ES FILE EXPLORER..
To make a script go to google market (Play Store) and find ES File Explorer
WRITE SCRIPT..
Open es file explorer when install completes.
in es file explorer click the menu button, and select "new"
when prompted select "File"
name your file something you'll remember
Ex.MusicScript
Click your new file
when prompted select "Text"
type this EXACTLY how you see it
Mount -o bind sdcard2/music sdcard/Android/data/com.google.Android.music
press back and when prompted to save click yes
MAKE DESTINATION FOLDER..
now on es file explorer click "Favorites" (the star)
a new menu will pop up, at the top you willsee a picture of a phone with "/" underneath it click the phone
this will take you to the root directory
click the folder Sdcard2
click the menu button, and select "new"
when prompted select "Folder"
Name the folder music
Your script and destination music location are created
EXECUTE SCRIPT..
now open script manager
find your script which should be located in the directory /mnt/sdcard and the file name you chose earlier
select the script
open as script/executable
make sure script is selected not executable
click the buttons for "Su" and "Boot"
click save
Go to google music (play music now) settings and clear any music that is currently saved to your device.
this only applies to music made available offline. If you do not clear it before running the script the music will exist on your internal Sdcard but not be accessible.
now reboot the script will run at boot a prompt will appear asking for superuser rights, click yes and remember this selection (it may say something different than remember this selection whichever option resembles remember needs to be selected.)
YOU'RE DONE!!!
your music should now save to sdcard2/music but the device will still think it is saving to the default sdcard/Android/data/com.google.Android.music
You can check this by going to google music. Selecting "make available offline" and look at the free space. It should shoe the space available on your external sdcard.
So try your hardest to figure out how to root using google, and if your not confident enough to attempt it this fix may not be for you.
if you have tried everything you can and are still stuck message me back, including what device you have, and i will see if i can find a link to the rooting instructions for your particular device.
I assume no responsibility if you damage your device... These steps do work, and if followed will fix your music issues as well as introducing you to a world of additional benefits of being a rooted user.
Hey FuzzyMeep Two! Thanks for the great tutorial.
It worked, with some minor adaptions:
1.) The script should read "mount -o ...". Note that there's no space between '-' and 'o'. You got that right in the first script though
2.) On GalaxyS2 with JellyBean/4.1.1 the correct paths are storage/sdcard1 (external) and storage/sdcard0 (internal).
regards,
Patrick
Thank you
Hi,
I tried changing file permission on one of the folders where I saved my photos to read-only using "Root Browser Lite".
The following error message came up: "Changing permission was not successful. Please note that some file systems do not allow permission changes".
I tried using ES file explorer but it also failed.
Could someone please tell me how I could change the file or folder permission. I wanted to prevent the photos from being accidentally deleted by my children when I let them browse their photos..
My phone I9300 was rooted using CF Auto Root.
Thanks
Get root explorer, it's much better.
Simply long press on a folder and the permissions option is there.
Sent from my GT-I9300 using xda premium
Don't forget to set to rw at the top of root explorer before attempting to change permissions
If you're talking about the internal memory, you can do chattr +i /data/media/[name of folder] to set the immutable bit. EDIT: You need BusyBox installed for the chattr command
This works because /storage/sdcard0 (JB's usual mountpoint for the internal eMMC) is a fake FAT32 file system Google created for compatibility; the internal eMMC can really be found at /data/media, which is of the ext4 filesystem.
For the external memory, you can try SGS3 Easy UMS and set the read only property on the folder using your computer. (I can't find mattrib for Android.) There is no guarantee that Android/Linux programs will obey the RO attribute, however.
The reason why Root Browser Lite & ES File Explorer didn't work is because they work on UNIX file permissions, while a file system formatted using FAT obviously doesn't understand them - it would expect DOS/FAT attributes. That said, though, have you already backed up the data you consider to be important?
100% work
Try this.....
http://forum.xda-developers.com/showthread.php?t=2038243
this will help you 100%..
qwerty12 said:
If you're talking about the internal memory, you can do chattr +i /data/media/[name of folder] to set the immutable bit. EDIT: You need BusyBox installed for the chattr command
This works because /storage/sdcard0 (JB's usual mountpoint for the internal eMMC) is a fake FAT32 file system Google created for compatibility; the internal eMMC can really be found at /data/media, which is of the ext4 filesystem.
For the external memory, you can try SGS3 Easy UMS and set the read only property on the folder using your computer. (I can't find mattrib for Android.) There is no guarantee that Android/Linux programs will obey the RO attribute, however.
The reason why Root Browser Lite & ES File Explorer didn't work is because they work on UNIX file permissions, while a file system formatted using FAT obviously doesn't understand them - it would expect DOS/FAT attributes. That said, though, have you already backed up the data you consider to be important?
Click to expand...
Click to collapse
=============
Thank you all for your advice. The file system explanation betw FAT and ext4 fs makes sense. I have BusyBox installed.
Via Terminal Emulator, when I did "chattr -i /data/media/DCIM/Camera", I got a "permission denied".
Is there something that prevented me from this?
I'm running ICS.
Thanks
Did you type su before the command..
Just asking..
sent from here, there, somewhere!!
zoot1 said:
Did you type su before the command..
Just asking..
sent from here, there, somewhere!!
Click to expand...
Click to collapse
Thanks Zoot1.
I did that.
Image Gallary is still showing /mnt/sdcard/DCIM/Camera as "writeable".
What is the difference between two folders /data/media/DCIM/Camera and /mnt/sdcard/DCIM/Camera?
Thanks,
Note that I used +i in my example invocation of chattr. - removes the attribute; + sets it, which is what you want
Sent from my GT-I9300 using Tapatalk 2
Thanks qwerty12, after 'chattr +i folder name' , I return to root browser lite to change permission on mnt/sdcard/DCIM/Camera, I still get permission denied. What did I do wrong?
Sent from my GT-I9300 using xda app-developers app
Mount System RW
The problem is that your system is currently in RO (Read-Only) mode.
Even if you are root, can't mess with system files if the setup is like that.
ES File Explorer works because it has an option (that DOES work) to mount the system in RW (Read-write) mode.
On my ES File Explorer Version 3.0.0 it goes like this:
Android menú button--->Tools---->Root Explorer--->Mount R/W.
Set: /system (or all of the options) to: RW----->OK.
Now, explore your files using the ES File Explorer interface on your phone and you should be able to erase every file and apk you want even if they are system files.
Vanyna said:
The problem is that your system is currently in RO (Read-Only) mode.
Even if you are root, can't mess with system files if the setup is like that.
ES File Explorer works because it has an option (that DOES work) to mount the system in RW (Read-write) mode.
On my ES File Explorer Version 3.0.0 it goes like this:
Android menú button--->Tools---->Root Explorer--->Mount R/W.
Set: /system (or all of the options) to: RW----->OK.
Now, explore your files using the ES File Explorer interface on your phone and you should be able to erase every file and apk you want even if they are system files.
Click to expand...
Click to collapse
finally its worked for me thx very much dude:laugh::good:
Hi guys, having an odd problem.
I've made some nandroid backups (about three) via CWM Recovery, and I can't seem to browse to them, or delete them.
It's definitely taking up space, and I'm not sure what to do now.
A backup that I made straight to my external SD card however, seems to be browse-able, so I'm a bit confused now.
Attached are some screenshots from ES File Browser (with root access turned on).
The last screenshot is going to /storage/sdcard0/clockworkmod/ (same directory, but now I can't seem to see anything about "backups").
I've also tried to delete these backups straight from CWM Recovery, but CWM says that it can't access the folder.
Oddly enough, if I do another backup (straight to internal), it seems to put all the files in /sdcard/Clockworkmod/backups but never to be accessed again.
Anyone have any ideas?
Delete via Windows Explorer .
jje
JJEgan said:
Delete via Windows Explorer .
jje
Click to expand...
Click to collapse
Thanks for the suggestion, but nope, that didn't work. (Obviously tried that first).
The folder was shown as empty via Windows.
After a lot of digging and trying different things (including Root Explorer and Terminal Emulator), I've managed to delete it.
I'll post the instructions so other people who may have similar problems in the future can follow it.
First, you'll need ADB and you'll need to reboot into CWM Recovery.
Once you've gotten that sorted, boot into CWM Recovery and go to "mount and storage" and then select "mount /data".
This will mount the /data structure which we need to use.
Afterwards in CMD, use the following:
Code:
adb root
adb shell
After this, you should be logged in as ~ (root)
Proceed to go into the directory using the cd function. (PROTIP: Use the ls function to check where you're going.)
You need to get to ../clockworkmod/backup/
You'll find that you can finally access the /backup/ folder, and you'll then be able to delete the files. Please note that the below command will delete ALL the files within this folder.
Code:
rm -rf *
Afterwards, do
Code:
cd ..
to get back to the ../clockworkmod/ folder and then run the below code to delete the now empty /backup/ folder:
Code:
rmdir backup
no, to be logged in as root you need to type in "su"
Hey Guys,
i have unlocked, rooted and flashed my Phone with Hassons ToolKit.
I have a problem getting full write access to my system folder, and all other folders / files which are in same path where system folder is.
I have just rights in SdCard Folder..
THis is the path where i dont have any permission to change something: is this normal?
If yes, so how can i push an apk to system folder then, if i need a new keyboard for instance...?!
acct
cache
config
d
data
dev
devlog
etc
mnt
proc
rca
rfs
root
sbin
sdcard (just in this one i have rights)
storage
sys
system
vendor
...
some files...
Ropb said:
Hey Guys,
i have unlocked, rooted and flashed my Phone with Hassons ToolKit.
vendor
...
some files...
Click to expand...
Click to collapse
Are you using adb or some Android based file manager to copy the file?
If it is adb = use adb remount, this normally solves the problem. If you are using some file manager - make sure system is mounted in RW mode..
Ropb said:
Hey Guys,
i have unlocked, rooted and flashed my Phone with Hassons ToolKit.
I have a problem getting full write access to my system folder, and all other folders / files which are in same path where system folder is.
I have just rights in SdCard Folder..
THis is the path where i dont have any permission to change something: is this normal?
If yes, so how can i push an apk to system folder then, if i need a new keyboard for instance...?!
acct
cache
config
d
data
dev
devlog
etc
mnt
proc
rca
rfs
root
sbin
sdcard (just in this one i have rights)
storage
sys
system
vendor
...
some files...
Click to expand...
Click to collapse
i guess you want to acces those folders with a file explorer? afaik it is normal that you don't have acces to other folders than sdcard, you have to use a file explorer with root capability to acces/write the other folders.
I'd recommend you to use ES File Explorer, very good app for me.
To grant root acces for it:
open the app -> press menu -> Tools -> Root Explorer (now the app should ask for root acces) -> Mount R/W -> set the paths where you want write acces to RW
now you should be able to write to the other folders.
If you want to use adb push (USB Debugging mus be enabled):
- copy the desire file or apk to your adb/fastboot folder
- connect your phone to your computer, open command line, navigate to adb/fastboot folder on your pc if necessary
- type "adb devices" (to see if your phone is recognized)
- type "adb push <name_of_your_file.file_extension> /path_of_your_destination_folder/<name_of_your_file.file_extension>"
Example: adb push example.apk /folder1/folder2/example.apk