Hello guys!
Today I was watching the tutorial from curser4eva.com to get AirView on the N7000. I wasn't successful and I get a little frustrated.
I don't really know why but I changed the permissions of the etc/permissions directory to: rw--r--r-- (0644) using Solid Explorer, and then restart my phone, since then I'm not able to access to my interal or external sdcard and also cannot access to a lot of apps.
Here is what I did exactly:
Using Solid Explorer, I copied the com.sec.feature.hovering_ui.xml file from my sdcard and tried to paste it in the etc/permissions directory but it said that there wasn't enough free space (I got the same message few days ago when I've tried to paste and apk. into the system/app directory).
And after this, I change the etc/permissions folder permissions to: rw--r--r-- (0644) using Solid Explorer, and then restart my phone, and after everything loads, a bunch messages of Force Closed services (dropobox, youtube, gapps services, for example) Pops up.
Then I open Solid Explorer to try to restore the permissions, and immediately pops up this message: Error - Cannot browse to "/storage/sdcard0"- An unknown error occured.
Then I jumped to the system root and accessed to etc/permissions and restored the permissions to: rwxr--xr--x-- (0755) and restart my phone, but nothing changes.
Finally in CWM recovery I flashed again the Jelly Bean eybee ROM to try to fix it, without any good result.
And right now I don't know what else could I do, because, in case you haven't noticed yet, I'm a freaking noob :crying:
Information could be useful:
I'm running Android 4.1.1
Baseband: N7000XXLS1
Build number JRO03C.N7000XXLS2
I'm also able to access to the Sdcard with Root Browser, and noticed that all files dates changed to: Dec 31, 1969 06:00:00, and all have the size of: 0.00B
Thanks in advance for your advices!!!..... And an apology if I'm wasting your time.
- José González
Reflash the room you were on when you changed the permission...
If that doesn't solve then make a titanium backup and do a factory reset, then restore apps
May be you want to go to stock rom using odin again and the come back to this rom
I'll take your advices
Thanks for your replys.
I will do your advices tonight.
Also, can you tell me which are your permissions and ownership of the storage and sdcard folders? Mine are:
Storage: r--xr--x-- (0550) , owner: 1000 system, group: 0 root.
Sdcard0: rwx--rwx--rx-- (0775), Owner: 1000 system, Group: 0 root
I'll wait fot your answer.
jgmoran said:
Thanks for your replys.
I will do your advices tonight.
Also, can you tell me which are your permissions and ownership of the storage and sdcard folders? Mine are:
Storage: r--xr--x-- (0550) , owner: 1000 system, group: 0 root.
Sdcard0: rwx--rwx--rx-- (0775), Owner: 1000 system, Group: 0 root
I'll wait fot your answer.
Click to expand...
Click to collapse
I copied the "com.sec.feature.hovering_ui.xml" and i didnt face any problem
Actually you are required to change the permissions of xml file..not for the etc/permissions folder
And permissions of storage : r-xr-x--- ,owner: system ,group:1028: 1028
sdcard : rwxrwxrwx, owner: 0:root ,group: 0:root
Solved!
Thanks guys!
I followed Jamal Ahmed recomendation. I did a factory reset from recovery and then reflash the ROM, and that's it!. And also I was able finally to copy de .xml to the permissions folder .
XDA Developers For the Win!!!
-José González
Related
I've read many times around the forum that apps can be installed by pushing them to the correct directories, but I'm not quite sure how to do that. When my phone is connected to my PC, I can only view the /sdcard directory. In ES File Explorer I can view the other directories but I'm looking for some clarification on how to proceed with pushing apps
pushing means to move the app / file directly to the place it should be, instead of letting the phone do it.
example: if you have an app that will not install, you use a app such as root explorer (many others out there too) and you get that app, move it to /system /app and there ya go, the app is in its right place.
the same goes for files, and other things, there are lots and lots of folders / subfolders, and sometimes this method is the only way. its fairly simple.
i hope i cleared that up for ya ???
azzledazzle said:
pushing means to move the app / file directly to the place it should be, instead of letting the phone do it.
example: if you have an app that will not install, you use a app such as root explorer (many others out there too) and you get that app, move it to /system /app and there ya go, the app is in its right place.
the same goes for files, and other things, there are lots and lots of folders / subfolders, and sometimes this method is the only way. its fairly simple.
i hope i cleared that up for ya ???
Click to expand...
Click to collapse
OK I think you have
I can put the app on my SDcard...then using ES File Explorer, I can copy the file, move to the directory I want, and paste the file. If I do this with an app, will it require installing, or will simply putting it in the proper directory allow me to run it ?
Thanks !
it will not need installing this is the beauty of it. Pushing it, you are putting it where it belongs - manually, hence the saying 'manually push through file explorer'
but once you have put the desired app / file in its correct place, its advised to reboot instantly, other wise it may not show up.
oh and finally, to do such things the system (phone) must be mounted as RW
azzledazzle said:
it will not need installing this is the beauty of it. Pushing it, you are putting it where it belongs - manually, hence the saying 'manually push through file explorer'
but once you have put the desired app / file in its correct place, its advised to reboot instantly, other wise it may not show up.
oh and finally, to do such things the system (phone) must be mounted as RW
Click to expand...
Click to collapse
Thanks for your help AzzleDazzle! Can I mount as RW through ES file explorer, or is it advised to do so through the ADB with standard linux chmod commands?
no you dont need to go through so much hassle.
im not sure if there is an option in file explorer for RW but there is with root explorer
you can also download sgs tools this can mount RW too, and even most kernels have this feature too
I corrupted my nv_data...
Flashing efsbackup didnt help...
A friend friend from the same country as me uploaded his nvdata, but i dont know how to apply it, ADB says device not found, debugging is on, and im using Win 7 x64 SP1.
If you have a complete backup of your /efs folder, a good way to restore it is: With root explorer, go into backuped /efs and multiselect and copy every file. Go to actual /efs folder and paste files in. Reboot, and things should be good now.
fps249 said:
If you have a complete backup of your /efs folder, a good way to restore it is: With root explorer, go into backuped /efs and multiselect and copy every file. Go to actual /efs folder and paste files in. Reboot, and things should be good now.
Click to expand...
Click to collapse
I have only nvdata.
And root explorer says no permission, although i enabled System RW.
8ax said:
I have only nvdata.
And root explorer says no permission, although i enabled System RW.
Click to expand...
Click to collapse
try long clicking the file, select permisions, make a note of whats ticked, then select them all, press ok, make sure the root "/" is mounted as R/W and try again. If sucessful change the permisions back to what they were... Hope that helps
That's true! Perfectly working on my stock rooted ICS for 24h+!
This mod is for test porpoises only. Although I'm using it with success right now, I can not guarantee you that it will work, so:
I'm just reproducing the method I used to make it works on my own device. I have no intentions of being a developer, I don't wanna any donations and I'm not encouraging you to try this, and I'm warning you this can potentially brick your device. So, if even knowing this you assume these risks, be warned that I'm not responsible for any problem you could have trying to do this. In short: do it by yourself!
It works on my stock ICS with rooted system.img, and I did as following:
- Backup your internal SDcard, because if anything goes wrong, you will have to use smartflash/nvflash to recover your phone, and your internal sdcard can be formated if you need to reinstall your system.
- Download ES File explorer from market (of course this is for not so advanced user, since they don't need this instructions)
- Enable all root options on it (menu, settings, root settings, check all the three first options)
- Click on the zip you downloaded from here
- Unpack the system folder from the zip attached to your sdcard
(on ES File explorer, click on "select" button, than on "system" folder, than on "extract" button)
- Go to /data
- Create a new dir called ICS
- Move the extracted "system" folder to /data/ICS/
- Enter /data/ICS/system
- There should be 4 folders: addon.d, app, lib and vendor
- Enter addon.p, long-click on 71-gapps-faceunlock.sh, click properties
- Change its properties to owner:read, write and execute; group: read, execute; others: read, execute
- Go back to /data/ICS/system, enter app folder
- long click on FaceLock.apk and change its permissions to owner:read, write; group: read; others: read
- Go back to /data/ICS/system, enter lib folder
- Change the permissions as you did for FaceLock.apk in all the 9 files, one by one, inside this folder
- Go back to /data/ICS/system
- Click on select, than select the four folders, than on CUT
- Go to /system (note: now it's /system, not /data/ICS/system anymore)
- Click on "Paste", confirm the changes on all the files/folders
- Reboot
Well, at this point, if you are a lucky guy and didn't get a 90% of a bootloop chance, you should be able to change your lockscreen to facelock.
I have no idea if this will work on tonyp/harsh's stock ICS flashable zip, because I don't have it to test. It should work since they are almost the same rom, however they have deleted a lot of LGs stuff to make the zip flashable on GB partition layout, so you can try it (the zip itself should be flashable on CWM), however:
- DO A NANDROID BACKUP firstly and
- YOU WILL NEED at least 39MB free on /system to do it! I have no idea if it's even possible to get this on GB partition layout
Link: http://db.tt/daf7KCmD
If you did this and it worked, press thanks and let us know.
reserved
reserved
I will try but it look too hard
Enviado desde mi LG-P990 usando Tapatalk 2
It is working thanks.
how do you unlock youre phone in the dark on lights off???
You just don't
It's really great that you write this to help others, but there is no need in such long instruction. Why just not to say easier:
1. Download lates ics gapps: http://goo.im/gapps/gapps-ics-20120429-signed.zip
2. Copy-past folders "optional/app" and "optional/vendor" into device system folder. (There is no need in addon.d on a stock rom)
3. Copy-past optional/noneon/lib/libfacelock_jni.so into system/lib folder. (There is no need to replace other libs)
4. Change permissions for system/app/FaceLock.apk and system/lib/libfacelock_jni.so to 644 (-rw-r--r--) (just look how it is set for other files in these folders).
5. Reboot.
I tried earlier to extract the face unlock files from gapps, but it didn't work for me... This way it works perfectly, thanks!
working thanks.........
mivv said:
how do you unlock youre phone in the dark on lights off???
Click to expand...
Click to collapse
Facelock always have a secondary method of PIN number. If facelock fails you can enter PIN number (numeric code) and it unlocks,
Has anyone tried this on CM10... I guess I will be the first then would be nice a .zip to flash
louiscypherbr said:
That's true! Perfectly working on my stock rooted ICS for 24h+!
This mod is for test porpoises only. Although I'm using it with success right now, I can not guarantee you that it will work, so:
I'm just reproducing the method I used to make it works on my own device. I have no intentions of being a developer, I don't wanna any donations and I'm not encouraging you to try this, and I'm warning you this can potentially brick your device. So, if even knowing this you assume these risks, be warned that I'm not responsible for any problem you could have trying to do this. In short: do it by yourself!
It works on my stock ICS with rooted system.img, and I did as following:
- Backup your internal SDcard, because if anything goes wrong, you will have to use smartflash/nvflash to recover your phone, and your internal sdcard can be formated if you need to reinstall your system.
- Download ES File explorer from market (of course this is for not so advanced user, since they don't need this instructions)
- Enable all root options on it (menu, settings, root settings, check all the three first options)
- Click on the zip you downloaded from here
- Unpack the system folder from the zip attached to your sdcard
(on ES File explorer, click on "select" button, than on "system" folder, than on "extract" button)
- Go to /data
- Create a new dir called ICS
- Move the extracted "system" folder to /data/ICS/
- Enter /data/ICS/system
- There should be 4 folders: addon.d, app, lib and vendor
- Enter addon.p, long-click on 71-gapps-faceunlock.sh, click properties
- Change its properties to owner:read, write and execute; group: read, execute; others: read, execute
- Go back to /data/ICS/system, enter app folder
- long click on FaceLock.apk and change its permissions to owner:read, write; group: read; others: read
- Go back to /data/ICS/system, enter lib folder
- Change the permissions as you did for FaceLock.apk in all the 9 files, one by one, inside this folder
- Go back to /data/ICS/system
- Click on select, than select the four folders, than on CUT
- Go to /system (note: now it's /system, not /data/ICS/system anymore)
- Click on "Paste", confirm the changes on all the files/folders
- Reboot
Well, at this point, if you are a lucky guy and didn't get a 90% of a bootloop chance, you should be able to change your lockscreen to facelock.
I have no idea if this will work on tonyp/harsh's stock ICS flashable zip, because I don't have it to test. It should work since they are almost the same rom, however they have deleted a lot of LGs stuff to make the zip flashable on GB partition layout, so you can try it (the zip itself should be flashable on CWM), however:
- DO A NANDROID BACKUP firstly and
- YOU WILL NEED at least 39MB free on /system to do it! I have no idea if it's even possible to get this on GB partition layout
Link: http://db.tt/daf7KCmD
If you did this and it worked, press thanks and let us know.
Click to expand...
Click to collapse
From your description it seems that you are more elaborative person so i need on help?
Stefen has give some instruction to root V28G Rom using NVflash but i am unable to find the meaning of those commands available in NVFlash
can u peovide me step by step along with commands to save system partition and all..............
i've just flash it on my 28g (samrtflash install) and work like a charme! thx
I get an error about the end, I can't move "VENDOR" folder into system, says it cannot move vendor folder.... any idea?
after rebooting I tried faceunlock, it was there but unable to initiate, then i tried again to move the VENDOR folder, i could now, after a reeboot still doesnt work
Anyone willing to test it in CM10?
Face unlock works
It's working on 30a version, did exactly the same way just copied the files from the folder to another. Will try in the morning if it can read the face easily as its night at my place now. Thanks
Hey All,
Having an weird issue with TWRP folder on my today gotten Moto X. I unlocked bootloader, installed TWRP, rooted etc. But when I try to make a new folder in the TWRP folder via my PC, I get this error, see attached.
Also when look at the TWRP folder inside ES File Explorer, I get the message "/sdcard/TWRP is not found". I tried fixing permission in TWRP aswell and deleted the folder and let TWRP create a new one, still same issue.
When I boot into TWRP and go advance > file explorer, I can just open the folder without any problem.
Also when I ADB shell into my sdcard and try to 'cd TWRP/' it says permission denied. Which makes me think there's a permission issue, but ls -l shows no wrong permissions at all.
Anyone know what this issue could be?
Thanks!
Hi... I'm having the same issue of urs... i think it is a twrp bug... hopefully they fix it soon...
If u want a temporary fix do the following as i did each time u do a backup thru twrp recovery:
download (root explorer) from play store and open it (its a paid app btw)
navigate to /data/media/0/
long press on twrp folder
click on (change owner)
change both Owner and Group from (0 - root) to (1023 - media_rw)
check on (Also set on all sub-folders and files)
hit OK
Now u will be able to access and make changes thru Windows....
(Thank me if it worked) :cyclops:
theone_s_me said:
Hi... I'm having the same issue of urs... i think it is a twrp bug... hopefully they fix it soon...
If u want a temporary fix do the following as i did each time u do a backup thru twrp recovery:
download (root explorer) from play store and open it (its a paid app btw)
navigate to /data/media/0/
long press on twrp folder
click on (change owner)
change both Owner and Group from (0 - root) to (1023 - media_rw)
check on (Also set on all sub-folders and files)
hit OK
Now u will be able to access and make changes thru Windows....
(Thank me if it worked) :cyclops:
Click to expand...
Click to collapse
Thanks, that helps a lot!<3
I've updated my device today to 6.0.1 and rooted, however I can't seem to change the boot animation (yes, I have searched for answers and tried quite a few fixes).
Root Explorer tells me I have renamed the old file and copied the new file, however once I leave the directory and go back the old file is still there.
I have used the file explorer in TWRP and managed to delete the stock boot animation, but get a FAILED message when I try to copy the new file.
I used the terminal in TWRP and tried to copy the file manually, and receive a "No space left on device" message.
I've also tried mounting the /system as rw in adb. I can delete the bootanimation.zip file from there, and df -h shows 3mb free. Shouldn't the system partition have more space available than that?
Am I missing something, or has something changed with the new android versions?
Google has filled the system partition up to the brim. Also you can't remount system as rw while Android is running.
But the direction is right, go to TWRP, mount system, delete the old bootanimation. If the new one is not that much bigger then you could just copy it there, set permissions to rw-r--r--. But if the new animation is significantly bigger, you'll have to delete some bloatware first.
Thanks for that. The odd thing is, when I run DF in the terminal, it shows I have 20mb free. The boot animation file I am trying to copy is 6mb.
I'll keep poking around. If it doesn't work, it doesn't. It's not hugely important