Can someone explain this to me, why does root explorer can't access files on "root/storage/emulated"
You know, nexus 5 virtual sdcard directory is "root/storage/emulated/0" but CWM backup directory is "root/system/clockworkmod"
I used to place the .zips for flashing new roms at "root/storage/emulated" using CM's file manager, though I'm on PA I installed CM's file manager from CM App Installer
the problem is CM's file manager not guaranteed to run on every rom. And from root explorer "root/storage/emulated" is not shown correctly (yes it can be accessed but the .zips and clockworkmod backup directory is not shown). But from CM's file manager it is accessible
Here I attached the problem I mean, you can see on the root explorer there's only 2 folder on "root/storage/emulated" (0 and legacy) but from cm's file manager it shows another files
What went wrong?
Sorry if my English are weird since English is not my primary languange
Because CWM is outdated.
Lethargy said:
Because CWM is outdated.
Click to expand...
Click to collapse
This. Stop using cwm.
Sent from my Nexus 5 using Tapatalk
rootSU said:
This. Stop using cwm.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Can you guys just explain why the folders isn't showing on root explorer but it is shown on cm file manager?
dustinraditya said:
Can you guys just explain why the folders isn't showing on root explorer but it is shown on cm file manager?
Click to expand...
Click to collapse
Can't explain why it shows in cm. I don't/won't use it.
Storage/emulated isn't a real location. Click the link in my signature and then find my data info thread. Everything is explained there. And stop using cwm
Sent from my Nexus 5 using Tapatalk
rootSU said:
Can't explain why it shows in cm. I don't/won't use it.
Storage/emulated isn't a real location. Click the link in my signature and then find my data info thread. Everything is explained there. And stop using cwm
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
"
I figured out that the files is at "root/mnt/shell/emulated"
I don't know why Cm and rootex shows different directory
OOT, what rom are you running now? Just curious
And Philz touch at your signature, can I just flash the .zip in cwm to get it replacing my current cwm?
I use slimkat and yes you can
FYI the true location of sdcard is /data/media/0
Sent from my Nexus 5 using Tapatalk
rootSU said:
I use slimkat and yes you can
FYI the true location of sdcard is /data/media/0
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Okay thank you. I'll flash philz touch right now
Related
I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
mrnexus said:
I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
There is a .sh file that needs to be removed, totally forgot the location of it :/
/etc/install-recovery.sh needs to be deleted or renamed.
It's a "safety" feature in 3.3.1 and above to restore the stock recovery if it doesn't pass a check on boot each time.
This is pointed out in numerous threads...search a little for more details if you need them.
Ok thanks
Sent from my Nexus S using XDA App
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
mrnexus said:
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
distortedloop said:
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
Click to expand...
Click to collapse
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
EDIT: Nevermind, I used root explorer and was able to find "mount r/w" and rename it finally. Thanks.
godzigga said:
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
Click to expand...
Click to collapse
Because those won't allow you to modify system files. Get Root Explorer, like he said, and use that.
AllGamer said:
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
Click to expand...
Click to collapse
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
sarge363 said:
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
True, I used adb, spent like 2 hour trying to get the pc drivers to recognize the nexus. I used the PDAnet drivers eventually.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Are you on a custom ROM like CM or Bionix? They remove the script that rewrites stock recovery.
If you're on stock, what version of it are you on? 2.3.1 and higher have a file called /etc/install-recovery.sh on them, and if that's there it should be reflashing stock on every boot, whether you renamed the image you flashed to recovery or not...
Hi there!
I have U30GT tablet which unfortunely till now didn't have any custom recovery. Some time I want to flash files to the ROM but due to this limitation I need to copy the files manually (easy job) and set the permission (hard job when there's a lot of files).
So is there any other ways that I can automated the task of copying the files and setting the correct permission without using custom recovery?
Many thanks!
Have you tried using a script or bat file to copy and set permissions through adb from your desktop?
Sent from my VS910 4G using xda app-developers app
I.M.famous XMAN said:
Have you tried using a script or bat file to copy and set permissions through adb from your desktop?
Sent from my VS910 4G using xda app-developers app
Click to expand...
Click to collapse
Thanks. But I don't know how to do a script or bat file to be used with adb. Can you write up some guide for it?
I'll see what I can do. No garruntees. But another option is to push the files through adb then use v6 supercharger to fix emissions. Idk. Let me see if I can Whip something up for you.
Sent from my VS910 4G using xda app-developers app
package can be flashed through stock recovery but they are needed to be signed properly with the manufacturer's key
dheeraj (dhlalit11) said:
package can be flashed through stock recovery but they are needed to be signed properly with the manufacturer's key
Click to expand...
Click to collapse
Thanks but I wanna copy files for some tweaks only.
Well I found 1 solution, that is to manually copy the files than use ROM Manager app to fix permission. Also found thread here in XDA about using .bat file to automated the push and set permission but as I very lacking in knowledge in using command, I'll stick to Root Explorer + ROM Manager combo.
you can root device,cat stock recovery.img,and then compile cwm recovery.
Check this website someone is working on getting CLOCKWORK recovery on U30GT
http://www.freaktab.com/showthread.php?1396-Cube-U30GT-H-JB-Finless-1-4-ClockWork-BETA1
Sent from my EVO
I'm trying to flash this recovery, but it does not seem to stick.
I have CM9.1, and i have tried flashing the zip and manually flashing the .img.
Both times don't work.
Any ideas?
bringonblink said:
I'm trying to flash this recovery, but it does not seem to stick.
I have CM9.1, and i have tried flashing the zip and manually flashing the .img.
Both times don't work.
Any ideas?
Click to expand...
Click to collapse
Check with a file manager with root rights that you don't have install-recovery.sh in the /etc/ folder at the root of your phone.
If yes, delete it.
polobunny said:
Check with a file manager with root rights that you don't have install-recovery.sh in the /etc/ folder at the root of your phone.
If yes, delete it.
Click to expand...
Click to collapse
You can get this working by flashing the recovery from rommanager. Worked for me.
Sent from my Nexus S using xda app-developers app
polobunny said:
Check with a file manager with root rights that you don't have install-recovery.sh in the /etc/ folder at the root of your phone.
If yes, delete it.
Click to expand...
Click to collapse
rather than deleting I suggest a renaming of the file to <filename>.<ext>.bak , as if he wants to return to stock , though I doubt that will ever happen
ReVo_007 said:
rather than deleting I suggest a renaming of the file to <filename>.<ext>.bak , as if he wants to return to stock , though I doubt that will ever happen
Click to expand...
Click to collapse
I'm on cm 9.1 and don't have that file
Sent from my Nexus S using Tapatalk 2
i modified the build prop and rebooted my htc and it is now showing nothing
i have made a back up of it but how can a access the root files of the phone????
Please help?!?!?!?
blitz100 said:
i modified the build prop and rebooted my htc and it is now showing nothing
i have made a back up of it but how can a access the root files of the phone????
Please help?!?!?!?
Click to expand...
Click to collapse
you must have nandroid..
PopaStefanx said:
you must have nandroid..
Click to expand...
Click to collapse
whats that.ima noob
blitz100 said:
whats that.ima noob
Click to expand...
Click to collapse
fml.:banghead: you should always make a nandroid backup using your custom recovery before messing with system files.
do you know what recovery you have?
what version is your hboot?
when you say nothing what do you mean?
completely empty homescreens not even the app drawer?
Could he push the backup of the build prop via adb?
Sent from my GT-P5110 using xda app-developers app
Skipjacks said:
Could he push the backup of the build prop via adb?
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
Yeah, original build.prop file from the original ROM
Download your rom zip, extract the build.prop. Put it on the root of your sd card. Download aroma file manager and put it on your sd card. Go in recovery, install aroma file manager, find your build.prop in system and delete it. Navigate to the sd card and find your build.prop you downloaded, and paste it where the build.prop file was deleted. Usually it's in the system directory
Kind Regards
Dave
Sent from my HTC Sensation using xda app-developers app
topgeardave said:
Download your rom zip, extract the build.prop. Put it on the root of your sd card. Download aroma file manager and put it on your sd card. Go in recovery, install aroma file manager, find your build.prop in system and delete it. Navigate to the sd card and find your build.prop you downloaded, and paste it where the build.prop file was deleted. Usually it's in the system directory
Kind Regards
Dave
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Not my issue but I had to thank you anyway.
Explained like a Sir! :good:
topgeardave said:
Download your rom zip, extract the build.prop. Put it on the root of your sd card. Download aroma file manager and put it on your sd card. Go in recovery, install aroma file manager, find your build.prop in system and delete it. Navigate to the sd card and find your build.prop you downloaded, and paste it where the build.prop file was deleted. Usually it's in the system directory
Kind Regards
Dave
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Every day i learn something new.Thanks man!
dw ive sorted it ...i flashed the rom again n it is there
I am having trouble finding my nandroid backup file made with TWRP. I can't even find the TWRP directory! This file system is so confusing! I have tried ES File Explorer, Root Browser, and tried searching the file system using my laptop. I have even searched for "2014-12-13" and nothing is found. Can anyone please help? Nexus 5 on Android 5.0 w/ TWRP v2.8.1.0
I had probaby the same problem as you are facing. N5 with TWRP 2.8.1.0. After making nandroid I could not get the backup to show up within the TWRP folder (which is visible and accessible with ES File Explorer).
This issue was when I was using this specific Lollipop 5.0 rom (don't know if it is rom related or not) :
http://forum.xda-developers.com/showpost.php?p=57372774&postcount=1
Then I went looking for another Lollipop rom, specifically a 5.0.1 version and found this one :
http://forum.xda-developers.com/showpost.php?p=56734946&postcount=1
After flashing this rom and making nandroid the backup shows up normally within ES File Explorer. Not more issues.
Don't know if this helps, hopefully :fingers-crossed:
daffie said:
I had probaby the same problem as you are facing. N5 with TWRP 2.8.1.0. After making nandroid I could not get the backup to show up within the TWRP folder (which is visible and accessible with ES File Explorer).
This issue was when I was using this specific Lollipop 5.0 rom (don't know if it is rom related or not) :
http://forum.xda-developers.com/showpost.php?p=57372774&postcount=1
Then I went looking for another Lollipop rom, specifically a 5.0.1 version and found this one :
http://forum.xda-developers.com/showpost.php?p=56734946&postcount=1
After flashing this rom and making nandroid the backup shows up normally within ES File Explorer. Not more issues.
Don't know if this helps, hopefully :fingers-crossed:
Click to expand...
Click to collapse
I flashed factory image 5.0 Lollipop from Google's website. I don't think our issue is related. I can't even find a TWRP folder.
Nebul0us said:
I flashed factory image 5.0 Lollipop from Google's website. I don't think our issue is related. I can't even find a TWRP folder.
Click to expand...
Click to collapse
Ok I see.
Nebul0us said:
I flashed factory image 5.0 Lollipop from Google's website. I don't think our issue is related. I can't even find a TWRP folder.
Click to expand...
Click to collapse
Look in /data/media/0
Sent from my Nexus 9 using XDA Free mobile app
Nebul0us said:
I am having trouble finding my nandroid backup file made with TWRP. I can't even find the TWRP directory! This file system is so confusing! I have tried ES File Explorer, Root Browser, and tried searching the file system using my laptop. I have even searched for "2014-12-13" and nothing is found. Can anyone please help? Nexus 5 on Android 5.0 w/ TWRP v2.8.1.0
Click to expand...
Click to collapse
Terminal
su
restorecon -FR /data/media/0/*
jd1639 said:
Look in /data/media/0
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
/data folder is empty
Nebul0us said:
/data folder is empty
Click to expand...
Click to collapse
It isn't empty. You're just using a file explorer that isn't very good at reading things that need root permissions
rootSU said:
It isn't empty. You're just using a file explorer that isn't very good at reading things that need root permissions
Click to expand...
Click to collapse
I'm using ES File Explorer. But SuperSU doesn't show it having root access. How do I give it root access? It was my impression that ES was THE way to go for file explorer apps...is there a better one? Obviously opinion, but I'm open to suggestion...
Edit: Okay, using Root Browser I found the TWRP directory and the backup. However when connected to PC, windows explorer can't see it. How do I move the backup to my PC? This is ridiculously complicated to backup to PC...
Nebul0us said:
I'm using ES File Explorer. But SuperSU doesn't show it having root access. How do I give it root access? It was my impression that ES was THE way to go for file explorer apps...is there a better one? Obviously opinion, but I'm open to suggestion...
Edit: Okay, using Root Browser I found the TWRP directory and the backup. However when connected to PC, windows explorer can't see it. How do I move the backup to my PC? This is ridiculously complicated to backup to PC...
Click to expand...
Click to collapse
Install a terminal emulator and run the commands that @Aerowinder suggested. See my /sdcard problems thread in general for more information
rootSU said:
Install a terminal emulator and run the commands that @Aerowinder suggested. See my /sdcard problems thread in general for more information
Click to expand...
Click to collapse
I am trying to run those commands and getting "The selected command does not exist."
Nebul0us said:
I am trying to run those commands and getting "The selected command does not exist."
Click to expand...
Click to collapse
Screenshot?
Nebul0us said:
I'm using ES File Explorer. But SuperSU doesn't show it having root access. How do I give it root access? It was my impression that ES was THE way to go for file explorer apps...is there a better one? Obviously opinion, but I'm open to suggestion...
Click to expand...
Click to collapse
open the side menu and expand the tools menu, find root explorer and hit on
rootSU said:
Screenshot?
Click to expand...
Click to collapse
Nebul0us said:
Click to expand...
Click to collapse
I don't know that terminal. Try "terminal emulator"by jackpal
rootSU said:
I don't know that terminal. Try "terminal emulator"by jackpal
Click to expand...
Click to collapse
This is what I get when I try to install that terminal...which is why I went with that other one...
Nebul0us said:
This is what I get when I try to install that terminal...which is why I went with that other one...
Click to expand...
Click to collapse
That's a known issue on Lollipop. It happens when 2 apps require the same permission.
Have you got ROM toolbox installed? That app is known to conflict with jack pal
If not, you'll need to run a Logcat whilst installing to find out which app is conflicting
rootSU said:
That's a known issue on Lollipop. It happens when 2 apps require the same permission.
Have you got ROM toolbox installed? That app is known to conflict with jack pal
If not, you'll need to run a Logcat whilst installing to find out which app is conflicting
Click to expand...
Click to collapse
Okay, so I uninstalled ROM Toolbox and the terminal I had. Good call :good:
So now the question is, what did that command do? Hahaha...
/data/media/0 is supposed to be the mount point for /sdcard. Sometimes when flashing lollipop, this association breaks, making your /sdcard contents (and sometimes just some of it) disappear. The command restores that
rootSU said:
/data/media/0 is supposed to be the mount point for /sdcard. Sometimes when flashing lollipop, this association breaks, making your /sdcard contents (and sometimes just some of it) disappear. The command restores that
Click to expand...
Click to collapse
Okay but how does that benefit me? And how can I view my backup locations in windows explorer?