Related
Hello guys.
Yesterday i installed Chainfire 3D from Android Market and then installed driver. My phone is now not booting, just galaxy s logo. How can i delete this driver and repair my Android? It's located on my memory card.
Re-apply permissions to all files. Mount the ext2 partition read/write on Linux, cd to it, and do "chmod 0777 ./* -v -R" and then "chmod 4755 ./system/xbin -v -R". Flush the cache with "sudo sync" and unmount.
By the way, how did you manage to install Chainfire? It keeps giving me an error when I do, about not being able to mount /system read/write.
Is this commands safe for my data or i will lose it?
How i installed? Just by downloading *.apk file.
Are you sure? Installing the apk only installs a tool which takes you to a menu to install the driver. If you don't click the icon and go through the install process inside the app nothing happens, so CF3D is most likely not the cause of your problem.
The commands I posted should still solve it and they don't destroy any data.
tydem said:
By the way, how did you manage to install Chainfire? It keeps giving me an error when I do, about not being able to mount /system read/write.
Click to expand...
Click to collapse
You need a kernel which doesn't mount /system as read-only. If you use the latest release from nbates, then I think your only solution is to remount /system as rw either via adb or from a terminal emulator on the device, then install cf3d
anghelyi said:
You need a kernel which doesn't mount /system as read-only. If you use the latest release from nbates, then I think your only solution is to remount /system as rw either via adb or from a terminal emulator on the device, then install cf3d
Click to expand...
Click to collapse
Going to try. If the shell script cannot mount it I doubt a terminal will, but whatever. I'm using the SD version with the audiofix kernel (can't remember date) and the MIUI ROM by the way.
tydem said:
Are you sure? Installing the apk only installs a tool which takes you to a menu to install the driver. If you don't click the icon and go through the install process inside the app nothing happens, so CF3D is most likely not the cause of your problem.
The commands I posted should still solve it and they don't destroy any data.
Click to expand...
Click to collapse
My problem is that I installed that driver (CF3D) from tool. Your commands doesn't help. My android still is not booting.
@edit:
problem solved, i reinstalled system folder
I seem to be having the same exact problem, can someone tell me the adb lines to fix this? not sure how to reinstall the system folder
hi,
guys i am having trouble with my phone all of a sudden.
I flashed back to stock ED05 and now my /system rfs partition is READ ONLY.
I found out its only read only, because i couldn't root anymore. I need root for titanium backup so i can restore my apps.
How do i change it to Readwrite?
Im trying to remount, but i am having problems
i went into cmd > adb shell > window opened up i typed mount -o rw,remount -t rfs /dev/block/stl9 (the stl9 is my /system i think from the look of the screenshot if i am wrong plz post)
and then i tried chmod 777 /system
it says UNABLE TO chmod /system read-only file system
SCREENSHOT from adb shell
replace 1234 in link to http
1234://img535.imageshack.us/img535/1202/android2.jpg
i tried following this guide replace 1234 with http and 123 with www
1234://123.pocketmagic.net/?p=757
thx for help in advance
sorry for links it says u need to have 8 posts before u can link away from forums
someone plz help im going insane on this. I have tried odin DL09 and ED05 over and over again but /system stays read-only
-ADB shell doesnt fix it
-odin doesnt fix it
-trying to get root but since /system is read-only i cant get root
plz someone has to know this
I'm having the same problem. Tried using the Samsung root package mentioned in another thread and it fails to mount the system directory.
I just got my Fascinate this weekend due to a warranty swap from another phone. It ran the update to ED05 when I OTA'd it. Is this something locked down in ED05?
FYI, just found this thread and had no problems doing it the manual way. try it out.
http://forum.xda-developers.com/showthread.php?t=779238
I'm trying to push files to /system via ADB. However I'm having problems (getting permission errors). I am running Eclipse 2.0.2, so yes, my phone is rooted, I have su and busybox.
Phone is connected to PC and is set as "USB Mass Storage".
USB Debugging is ON
Here is my CMD log:
Code:
C:\android-sdk\tools>adb remount
remount failed: Operation not permitted
I tried to remount and it failed
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to
'/system/myfile.apk': Read-only file system
I tried to push, and got a READ-ONLY FILE SYSTEM error (keep this in mind)
Code:
C:\android-sdk\tools>adb shell
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
I try to push inside of ADB shell. Nothing again...
Code:
$ su
su
# mount -o remount,rw /dev/block/mtdblock4 /system
mount -o remount,rw /dev/block/mtdblock4 /system
# exit
exit
I go into SU and attempt to remount the /system
Code:
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
$ exit
exit
I go back up to ADB shell and try to push again... same error as before
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to '/system/myfile.apk': Permission denied
I go back to the main command line and try to push again. This time I get PERMISSION DENIED. This error is different than before.
Any help on the matter?
I've read about ro.secure needing to be set to 1, but I need to edit the boot.img in order to do this, correct? Does that require an unlocked bootloader? Is root ADB even possible on the DX2.
Thanks!
I am no expert (don't even know if i know enough to b called a newb) but maybe try a root explorer. I use es file explorer because it's free. In settings check root explorer and mount file system. I received similar errors and this solved my problem.
Sent from my DROID X2 using XDA App
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
wesf90 said:
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
Click to expand...
Click to collapse
I was using adb also and had similar problems. After i changed those settings i was able to push a file. I had to have system mounted.
Sent from my DROID X2 using XDA App
No luck on my end :/
Sorry i couldn't be more help. I am new to adb and may have done more to get it working. I'm sure there's someone else around here that can help u out.
Sent from my DROID X2 using XDA App
Make sure there are no spaces in the file path to your android-sdk folder. Can't say if this is your issue but its worth a shot as it has always caused weird problems with android development since day one.
Sent from my DROID X2 using Tapatalk
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
CadenH said:
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
wesf90 said:
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
Click to expand...
Click to collapse
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
ashclepdia said:
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
Click to expand...
Click to collapse
Thanks for that! It's not quite what I'm aiming to eventually do, but did give me more insight on how the whole adb/shell/su systems work. From inside of su, I was able to mount the /system as RW, however I'm only able to do this from inside of SU. I want to be able to do this from the initial CMD so that I can ADB PUSH from my computer to the phone.
Here's my latest log:
Code:
C:\android-sdk>adb shell
[[TRYING TO MOUNT FROM ADB SHELL]]
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
[[TRYING TO MOUNT FROM ADB SHELL USING BUSYBOX]]
$ busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: permission denied (are you root?)
[[GO TO SU]]
$ su
su
[[MOUNTING AS RW SUCCESSFUL]]
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
[[COPYING A FILE INSIDE /SYSTEM SUCCESSFUL]]
# cp framework/framework-res.apk framework/framework-res-test.apk
cp framework/framework-res.apk framework/framework-res-test.apk
[[REMOUNTING /SYSTEM AS RO]]
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
[[ATTEMPTING TO COPY AGAIN, FAILED]]
# cp framework/framework-res.apk framework/framework-res-test2.apk
cp framework/framework-res.apk framework/framework-res-test2.apk
cp: can't create 'framework/framework-res-test2.apk': Read-only file system
#
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Maybe its because im tired but im confused as to why it wont let you push your files if you have remounted as rw. At that point it should be cake. You gained access to system by remounting it as rw successfully already.
Sent from my DROID X2 using xda premium
wesf90 said:
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Click to expand...
Click to collapse
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
I'm no expert in ADB, but I had run into the same issue as you and for me the fix was to go into ADB SHELL , then type SU to get SU access, then type exit twice to get out of shell completely. Then I tried pushing the APK and it worked fine with no read only errors.
This worked for me on my SGS2, could work for you ! Goodluck !
Come to IRC and I can help you with this. http://webchat.freenode.net Come to the #cm7dx2 channel. I'm usually there... Look for the nick(s) Moon|Work|(something), Moon|Home|(something), or MoonShadow-NM. If the (something) says Busy, I might not answer right away. If it says Away, I'm away from the keyboard and you won't receive a response until I return.
Ciao!
Any update
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
I've got a better idea to fix your issue brotha!
From my nexus tappin the talk
<edit post successful>
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
From my nexus tappin the talk
<edit post successful>
jamesh0317 said:
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
Click to expand...
Click to collapse
This won't work with Eclipse since it's not using 2nd init. I asked this question in the Eclipse forums and Nitro responded with the following:
Not without using 2nd init. All of that works due to being able to load its own init.rc which starts services and passes parameters, etc.. during boot time. It is possible to make a stock rom use 2nd init. CM9 will not even have root enabled by default. The only other way to push stuff is to enable root shell prior to pushing.
Click to expand...
Click to collapse
I know that CM7 allows using the adb remount, but that's because it's using 2nd init. I had also asked the question about why CM7 defaults to root shell when you adb shell into it and that's why he mentions how CM9 won't have root enabled by default.
The way I push to Eclipse is to run root explorer on my phone and mount the directory r/w. Then, I can use "adb push" to the phone.
ashclepdia said:
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
Click to expand...
Click to collapse
I think I may have tried that in one of my iterations. Originally I had it rooted with One-Click and then I was having issues with the 2.3.5 OTA update (quickoffice.apk) and at this point I've SBF'ed and rooted it probably 5 times this week so far. Rooted with both One-click and zergRush at various times. Actually I think every time except this last time has been with one-click. So I don't think that has seemed to make a difference for me so far. I can try it again, but if there's any other advice to throw out in the mean time, I'll take it.
Alternatively, I may take the new phone (the first replacement they sent had 2.3.5 on it, but a bad menu key causing the phone to flip out), load Titanium Backup on it, backup all the system apps and restore them to my original phone. Worst case is I have to SBF it again. But that seems like a logical process since I will have two phones available.
Hi all,
I just did a System Level root here http://forum.xda-developers.com/showthread.php?t=1505062 and it was successful. It didn't add flash counters which is why I chose this method.
I was able to install Superuser and Titanium Backup.
However I need to return the phone for exchange because this one is currently defective (charger issues).
Now I'm trying to unroot and restore to defaults. First I uninstall Titanium backup which was easy. Then now I can't UNinstall Superuser.apk. I look for guides and found that I need to download Terminal Emulator, enable root then run these commands:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
However, when I run this it gives me this error:
Code:
#rm -r /system app Superuser.apk
rm failed for Superuser.apk, Read-only file system
So yeah, it won't delete and I can't return it with Superuser installed in there
Is there a different method to just download the official restore .tar file from Samsung and just restore it that way using odin. If there is, where can I find that .tar file?
Please help, I only have a few hours before I can return this
Thanks!
Just an update (I'll just reply to myself since I found a solution)
I was able to delete the Superuser.apk,busybox,su by following this guide: http://forum.xda-developers.com/showpost.php?p=7386761&postcount=2
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
However my device is still rooted. Although Bestbuy/AT&T might not detect it, Samsung probably will .. so warranty can still be voided.
Anyway, is there way to unroot easily?
I'm guessing that using the official .tar file from samsung ... will fix this.
Where can I find that file?
THanks again!
How is Samsung going to link your Best Buy return back to you? Since you are within 30 days, your return will be fine. I think the concern is the flash counter when sending in for warranty repairs after the 30 day return window.
jpeg42 said:
How is Samsung going to link your Best Buy return back to you? Since you are within 30 days, your return will be fine. I think the concern is the flash counter when sending in for warranty repairs after the 30 day return window.
Click to expand...
Click to collapse
Thanks! Point taken. But yup .. I guess I was talking about future issues when I will have to deal with Samsung (hopefully not).
So .. is there a restore .tar file that samsung provides?
Thanks again.
Not sure if it will work but i would assume just flashing the stock att tar would remove root
jdphilly said:
Not sure if it will work but i would assume just flashing the stock att tar would remove root
Click to expand...
Click to collapse
Or just do a reset under settings>Privacy.
droidal said:
Or just do a reset under settings>Privacy.
Click to expand...
Click to collapse
will that actually "unroot" it?
spec2323 said:
will that actually "unroot" it?
Click to expand...
Click to collapse
No. 2 ways to unroot. Remount r/w, and remove said binaries, or flash system.img with stock the same way you flashed the rooted system.img.
lastdeadmouse said:
No. 2 ways to unroot. Remount r/w, and remove said binaries, or flash system.img with stock the same way you flashed the rooted system.img.
Click to expand...
Click to collapse
do you have a link for a real/safe ATT stock system.img we can flash?
http://forum.xda-developers.com/showthread.php?t=1506330
There is a stock system here. I'm pretty sure since it is the stock signed kernal it shouldn't trip the counter either. Maybe someone with an already tripped counter can try it and report.
thanks alot
keplenk said:
Just an update (I'll just reply to myself since I found a solution)
I was able to delete the Superuser.apk,busybox,su by following this guide: http://forum.xda-developers.com/showpost.php?p=7386761&postcount=2
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
However my device is still rooted. Although Bestbuy/AT&T might not detect it, Samsung probably will .. so warranty can still be voided.
Anyway, is there way to unroot easily?
I'm guessing that using the official .tar file from samsung ... will fix this.
Where can I find that file?
THanks again!
Click to expand...
Click to collapse
it worked for me.. thanks a lot
Another way to return to stock is with Kies. I have used this method a couple of times with no problems. Once Kies wouldn't recognize my note, so I had to flash a stock ics rom from the super everything thread, then hook it up so kies would recognize. There is also a flash counter reset in the super everything if you are worried about that.
Did you get the insurance from Best Buy? Or just worried about warranty from Samsung? If you have BB insurance, just run over the thing with your car before taking it back. That's what I plan to do. Just before my contract is up I always return for a new phone. They can't check the flash counter if it is snapped in half
Sanjay Kumar
I will say a simple method to uninstall superuser.
First you root your phone again
Download clean master which is free.
Now open it. And allow superuser permission. Now open app manager.
It shows uninstall-backup -move options.
Select pre installed apps . Click superuser and click uninstall.
Hurray u have uninstalled superuser . My what's app number 7401660083. Message me I you have any doubt:good:
problem..
hello, i have i9505 phone and i had superuser with error. i tried to restore with odin just as you said, and i put pit file that was on the folder. i put pda file too. it was too long time to install and i close the connection. after that my phone remains to samsung logo. what can i do?pls help
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
nasenstueber said:
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
Click to expand...
Click to collapse
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
mauricio.valladolid said:
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
Click to expand...
Click to collapse
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
nasenstueber said:
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
Click to expand...
Click to collapse
why dont you just install ext4 recovery and flash supersu.zip?
I really dont get it why are you trying to do it the hard way