I changed the /root to r/w and forgot to change it back before my phone died and now it is stuck in boot loop. I have tried twrp fix permission but does not seem to work. Is there any way for me to change it without wiping my phone. Don't want to lose the files I have on my phone.
Thank You in advance.
Reflash the ROM without a wipe. Quickest fix, providing this is the cause of your boot loop. How did you change the permissions? Root is already read/ write
Sent from my Nexus 5 using Tapatalk
I was changing the tether setting from this tutorial I had done previously but had been undone. And i also had reflash the Rom but still stuck in boot loop
nightang3l said:
I was changing the tether setting from this tutorial I had done previously but had been undone. And i also had reflash the Rom but still stuck in boot loop
Click to expand...
Click to collapse
Please answer my other questions.
I used root Explorer and change the r/o to r/W. I'm sorry if I confused you not the root folder it self but the root directory.
nightang3l said:
I used root Explorer and change the r/o to r/W. I'm sorry if I confused you not the root folder it self but the root directory.
Click to expand...
Click to collapse
That's just mounting it, not changing the permissions.
Connect the device in recovery and use adb shell to run the following command
Code:
adb shell
ls -ld /
Result should be
Code:
drwxr-xr-x
Maybe a link to the guide you used would be helpful.
Thank you will try when I have time.
Related
I have a problem with Root Explorer! It ocurred as:
I copy a file, and I can to paste it in System/framework, but when I try paste it the Root Explorer don´t permit me to paste and says me this message:
"The paste operation failed. Would you like to send diagnostic information to the developer to assist with fixing the problem?"
WHY?
Thx 4 all! =)
Not development related Moved
Anybody can help me? =(
Sent from my GT-I5800 using Tapatalk
fersago said:
I have a problem with Root Explorer! It ocurred as:
I copy a file, and I can to paste it in System/framework, but when I try paste it the Root Explorer don´t permit me to paste and says me this message:
"The paste operation failed. Would you like to send diagnostic information to the developer to assist with fixing the problem?"
WHY?
Thx 4 all! =)
Click to expand...
Click to collapse
It's just a guess, but maybe you need to root your phone? Don't know if it's already rooted but...
Yes! Its perfectly rooted with SuperOneClick! I too use TBackup!
Sent from my GT-I5800 using Tapatalk
Did you tried the "RW" option on the rootexplorer? Or just delete first the file, and not try to overwrite them...
You can do this over adb too...
GL!
The R/W Option is Enabled! =(
UP! UP! UP!
First make sure u are rooted and then
try remounting the system by typing in terminal:
mount -o remount,rw /dev/block/stl6 /system
NOTE: When u open Root Explorer a text should appear "Root Explorer has been granted Superuser permission"... If this doesnt appear check the su app for allowing permission to ROOT EXPLORER or u will need 2 reroot ur phone...
Go to the location where you want to paste a file or perform action.
Now click on Mount RW at the top of the screen. It will change to Mount RO.
Now you can copy files.
PS: Your need a rooted phone
jaskiratsingh said:
Go to the location where you want to paste a file or perform action.
Now click on Mount RW at the top of the screen. It will change to Mount RO.
Now you can copy files.
PS: Your need a rooted phone
Click to expand...
Click to collapse
My phone is rooted, and root explorer HAS ROOT ACCESS but clicking on the "Remount as RW" button on the top of the screen does nothing in "/system"
it works on "/sdcard" and anywhere els. But not in "/system"
Any ideas?
Edit: actually in "Superuser" the root access has been allowed but when I start "Root Explorer" there will be no notification of giving the root access ("Root Explorer has been granted Superuser permission")
acutally i got a solution for remounting to rw mode
e.savisaar said:
acutally i got a solution for remounting to rw mode
Click to expand...
Click to collapse
And how did you do it?
Got the same problem on my rooted Nexus 10 running 4.2.1 JB. Rooted it with SuperSU.zip via CWM and root seems to work fine.
Sadly I cant write anything to the system folder.
I tired to use the command "mount -o remiunt,rw /dev/block/stl6 /system" mentioned earlier in this thread but even with the use of "su" and granting SuperSU rights it wont allow me to create directories there. The mount command seems to work fine as there are no error messages but mkdir throws an error:
"mkdir: can't create directory 'test': Read-only file system"
Oh and there are no toast notifications about granting root access to the shell except the first time I typed su.
Anybody else having that problem on the Nexus 10?
fersago said:
I have a problem with Root Explorer! It ocurred as:
I copy a file, and I can to paste it in System/framework, but when I try paste it the Root Explorer don´t permit me to paste and says me this message:
"The paste operation failed. Would you like to send diagnostic information to the developer to assist with fixing the problem?"
WHY?
Thx 4 all! =)
Not development related Moved
Click to expand...
Click to collapse
Long press on the file that you want to paste in , then choose permission and press yes and ok
markus4000 said:
And how did you do it?
Got the same problem on my rooted Nexus 10 running 4.2.1 JB. Rooted it with SuperSU.zip via CWM and root seems to work fine.
Sadly I cant write anything to the system folder.
I tired to use the command "mount -o remiunt,rw /dev/block/stl6 /system" mentioned earlier in this thread but even with the use of "su" and granting SuperSU rights it wont allow me to create directories there. The mount command seems to work fine as there are no error messages but mkdir throws an error:
"mkdir: can't create directory 'test': Read-only file system"
Oh and there are no toast notifications about granting root access to the shell except the first time I typed su.
Anybody else having that problem on the Nexus 10?
Click to expand...
Click to collapse
i got a solution for this issue :
just install es explorer and turn on the root explorer mode then grant the permissions then again click on the tab root explorer and then a popup window will appear where you can allow permissions for each folder differently.
click thanks button if it worked for you.
Root is required. Make a Nandroid backup! (I accidentally deleted by build.prop file and bootlooped my phone)
1) Download ES File Explorer (Or any other root file editor)
2) In ES File Explorer, go into Setting > Root Settings and enable both check boxes
3) Navigate to /system/ and copy/paste build.prop to /sdcard/ (just in case)
4) Open & edit /system/build.prop
5) Change the following lines to make your phone think it is a HTC G2:
ro.product.model=HTC Vision
ro.product.manufacturer=HTC
OR
ro.product.model=Nexus S
ro.product.manufacturer=samsung
6) Reboot the phone
7) Install the netflix apk (if you haven't already)
8) Enjoy
HELP!
I've run into a problem with this. My phone has gone into bootloop.
Is there a way to copy the build.prop I backed up on my sdcard to the /system/build.prop without booting the phone,... I.E. from the cyanogen recovery mode?
thedarkharlequin said:
I've run into a problem with this. My phone has gone into bootloop.
Is there a way to copy the build.prop I backed up on my sdcard to the /system/build.prop without booting the phone,... I.E. from the cyanogen recovery mode?
Click to expand...
Click to collapse
I have the same issue right now but I don't have Cyanogen Rec Mode. I just have the ENG Bootloader and that's it.
Same issue with Samsung Fascinate
Anyone have any ideas how to copy back a build.prop if the phone is stuck in a boot loop? Adb won't work as it doesn't get far enough in boot to connect and it won't connect in recovery mode. As I can get into recovery, I may be able to flash a rom but that would be a worse case scenario.
theberidox said:
Anyone have any ideas how to copy back a build.prop if the phone is stuck in a boot loop? Adb won't work as it doesn't get far enough in boot to connect and it won't connect in recovery mode. As I can get into recovery, I may be able to flash a rom but that would be a worse case scenario.
Click to expand...
Click to collapse
I haven't yet tried ADB but since you've already answered my question then I guess we're stuck and must upload a stock rom and run it. I will try it once I get home but for now any new info would help. Sucks not having a phone at all
Can you not boot into recovery, mount system and use adb shell to copy the file from the SDCard?
D
dsb9938 said:
Can you not boot into recovery, mount system and use adb shell to copy the file from the SDCard?
D
Click to expand...
Click to collapse
No sir. I cannot do such procedure. I'm trying to load the update.zip without wiping all my info out. I can go into recovery but cannot mount. I cannot use ADB it says error device offline.
Bootloop Fixed
dsb9938 said:
Can you not boot into recovery, mount system and use adb shell to copy the file from the SDCard?
D
Click to expand...
Click to collapse
Thanks. I forgot to mount system. I'm back up and running now. Using clockwork recovery, I mounted system and then adb was able to connect. I then used "adb push build.prop /system/" to move a corrected copy from my pc to the phone (I had originally used an on-phone editer that reformated the file and caused the issue). Rebooted phone and it booted. Netflix still doesn't work, (I changed the ro.product.model=Nexus S & ro.product.manufacturer=Samsung) but at least my phone is back.
FYI Update: I changed my build.prop to ro.product.model=HTC Vision & ro.product.manufacturer=HTC and now no longer get the unsuported message but Netflix now closes after log-in. I guess this was all for nothing for me.
Having problems with captivate
ES explorer wont work, so I had to buy different one. Changed it to Nexus S, rebooted, opened netflix, get an error message saying my device is not supported. Please help.
I'm rooted and unknown sources is on and I dl'd es file explorer and went into settings and root options and click on root explorer it asks cyanogen or HiAPK rom. Is there a specific rom I should be running? When i click root explorer then i get "test failed. This feature cannot run on your phone, and then pops up to grant superuser permissions. Any suggestions? Thanks
And now I'm running cyanogen 7.0.3 and select cyanogen from the pop up but still get same error please help I have the apk for Netflix but says needs update and won't find update and just closes so i believe editing build.prop will get it running but cnnt get in to do the edits thanks in advance
nvm. i got it !!!!
krinilssen said:
Root is required. Make a Nandroid backup! (I accidentally deleted by build.prop file and bootlooped my phone)
1) Download ES File Explorer (Or any other root file editor)
2) In ES File Explorer, go into Setting > Root Settings and enable both check boxes
3) Navigate to /system/ and copy/paste build.prop to /sdcard/ (just in case)
4) Open & edit /system/build.prop
5) Change the following lines to make your phone think it is a HTC G2:
ro.product.model=HTC Vision
ro.product.manufacturer=HTC
OR
ro.product.model=Nexus S
ro.product.manufacturer=samsung
6) Reboot the phone
7) Install the netflix apk (if you haven't already)
8) Enjoy
Click to expand...
Click to collapse
Thanx for the Help!
And Not to Totally get off the subject but does Anyone know what needs to be Changed in the Build.Prop to get the Connection time Faster? I saw it in a thread before but Can't Remember Where?
Thanx in Advance!
PMGRANDS said:
Thanx for the Help!
And Not to Totally get off the subject but does Anyone know what needs to be Changed in the Build.Prop to get the Connection time Faster? I saw it in a thread before but Can't Remember Where?
Thanx in Advance!
Click to expand...
Click to collapse
add this to the end of your build.prop
Code:
#ISE:
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
I downloaded everything in the cwm final
I used file manager to overwrite the old files and when I boot into recovery I still get the old recovery and not cwm
There is also nowhere for me to instal from update.zip
I have done this on my evo and it was easy but I'm clearly missing something with my galaxy 4g would someone be so kind as to give step by step instructions?
BGVampire said:
I downloaded everything in the cwm final
I used file manager to overwrite the old files and when I boot into recovery I still get the old recovery and not cwm
There is also nowhere for me to instal from update.zip
I have done this on my evo and it was easy but I'm clearly missing something with my galaxy 4g would someone be so kind as to give step by step instructions?
Click to expand...
Click to collapse
reinstall packages
krylon360 said:
reinstall packages
Click to expand...
Click to collapse
No fair you beat me to it.....duh winning..
Sent from my SGH-T959V using XDA Premium App
krylon360 said:
reinstall packages
Click to expand...
Click to collapse
and yes you must reinstall packages every time you want to re-enter CWM so you must leave the update.zip on you SD card
wrecless said:
and yes you must reinstall packages every time you want to re-enter CWM so you must leave the update.zip on you SD card
Click to expand...
Click to collapse
Thank you for your post. Common knowledge I know but a great reminder!
Sent from my Galaxy s 4g
can't flash CWM recovery
everytime i boot into recovery, i selected reinstall packages, then i get error : signature verification failed!
am I missing something? I have EVO too, it wasn't that difficult to install CWM.
anybody can help me by pointing to things I might have missed?
sarfrazhc said:
everytime i boot into recovery, i selected reinstall packages, then i get error : signature verification failed!
am I missing something? I have EVO too, it wasn't that difficult to install CWM.
anybody can help me by pointing to things I might have missed?
Click to expand...
Click to collapse
recovery.bin probably isn't being overwritten correctly. At first I downloaded the file with Dolphin Browser and had the same problems. Try downloading the file with firefox and then try pushing it to /system/bin again.
probably recovery file is not being copied in system/bin folder. i can see it has only read permission for group and write permission. i tried rom manager permission fix, that didn't change permission of recovery. i tried changing from terminal using chmod +w & chmod 755. but that didn't help change the permission on recovery file.
sarfrazhc said:
probably recovery file is not being copied in system/bin folder. i can see it has only read permission for group and write permission. i tried rom manager permission fix, that didn't change permission of recovery. i tried changing from terminal using chmod +w & chmod 755. but that didn't help change the permission on recovery file.
Click to expand...
Click to collapse
Rom Manager isn't working for the Galaxy S 4G yet.
What application are you using to copy recovery to /system/bin?
typically i use ES explorer but i tried File Expert too.
one typo on my prev post: i don't have write permission on recovery, only got read permission.
sarfrazhc said:
typically i use ES explorer but i tried File Expert too.
one typo on my prev post: i don't have write permission on recovery, only got read permission.
Click to expand...
Click to collapse
ES won't work. File Expert should work. Just make sure you have R/W permissions. Don't do anything with Rom Manager. That won't help.
yea it should work as they say but it does not. I tried changing permission using File expert,it click OK and then i check file permission on recovery right away, the write permission is not checked. even chmod 755 failed to change the write permission!
sarfrazhc said:
yea it should work as they say but it does not. I tried changing permission using File expert,it click OK and then i check file permission on recovery right away, the write permission is not checked. even chmod 755 failed to change the write permission!
Click to expand...
Click to collapse
I don't think you have any problems with R/W. I just don't think the recovery file was overwritten. Look in /system/bin in File Expert. Do you see recovery and recovery.bin? Or just recovery?
/system/bin/recovery file exists and i have been trying to change its permission.
sarfrazhc said:
/system/bin/recovery file exists and i have been trying to change its permission.
Click to expand...
Click to collapse
You don't need to change the permission of recovery. Copy the recovery file and navigate to /system/bin in file expert. When you get there you want to hit menu then more then mount. It will give you two options. Pick mount as read write. Then paste the recovery file.
Read through this thread again. It should help.
http://forum.xda-developers.com/showthread.php?t=1099374
mounted with read/write and now i could boot into recovery.
Thanks a lot for taking time to answer my questions. First backup is in progress...
sarfrazhc said:
mounted with read/write and now i could boot into recovery.
Thanks a lot for taking time to answer my questions. First backup is in progress...
Click to expand...
Click to collapse
No problem man.
when i try to copy files to /system/ nothing happens
i mounted as r/w so what could be the problem?
ripsta99 said:
when i try to copy files to /system/ nothing happens
i mounted as r/w so what could be the problem?
Click to expand...
Click to collapse
when paste or modifying a file in the root system, you need to tap the r/w to r/o in order to write or change permissions.
If you are doing a 3e mod, don't forget to change the permissions too.
....not working. if i change it to read only it Def not working.
ripsta99 said:
....not working. if i change it to read only it Def not working.
Click to expand...
Click to collapse
Check again to see what you are doing wrong. Its a toggle to read/write or read only.
If you're using root explorer, you have root.
Infuse n root explorer is not smart enough to pick out just you.
Edit.. Are you trying the 3e mod?
Three are easier way
ripsta99 said:
when i try to copy files to /system/ nothing happens
i mounted as r/w so what could be the problem?
Click to expand...
Click to collapse
bad su binary?
does super user show root explorer having super user permission? do you have super user installed? does it give a notification or toast that permissions were granted either when the app starts or on boot?
if that is all ok then open terminal emulator and type
su
(you should see $ change to # and a notification for superuser permissions granted.. if not you likely need to re root the phone)
if that goes OK then type
mount -o rw,remount /dev/block/stl9 /system
if it has any error like permission denied or invalid argument or can't remount folder exists or anything at all then there is something odd going on, could be something I'm overlooking, could be a bad su binary. try reflashing and don't update the binary if you are on a custom kernel.
edit: overlooking busy box. try installing it from a busybox installer from the market! that should fix it if su is OK.
Also, you may new to delete the app and reinstall, that happened to me and it thought I was trying to pirate the app. It would open but Wouldn't let me move/replace anything.
Then I went and verified I paid for it and everything worked after that.
Hi,
i rooted my mate8 succefully, but i can't modify files on root/system
I tryed to modify build.prop but i'm not able to save
I used mx explorer and grant proper permissions on super-su .
The root is applied ( checked with the cecker root application)
Any suggest?
Remount system as read/write, that usually isn't done automatically.
ufoman said:
Remount system as read/write, that usually isn't done automatically.
Click to expand...
Click to collapse
thanks for reply, solved by re-root my mate....something was wrong at first time