I am trying to re-root after the 2.3.6 update, I did not remove root before the OTA update.
I made sure USB connection was set to none, and USB debugging was on. I see that is saying that I am out of space, problem is I don't know how I could possibly be able to be out of space, I have plenty of room on both the internal and external cards. Below is the output with the error. Any help would be appreciated. Thanks.
C:\moto-fastboot-win32>moto-fastboot.exe flash preinstall preinstall.img
sending 'preinstall' (30720 KB)... OKAY [ 2.682s]
writing 'preinstall'... OKAY [ 3.447s]
C:\moto-fastboot-win32>moto-fastboot.exe reboot
rebooting...
C:\moto-fastboot-win32>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
cp: write error: No space left on device
[email protected]:/#
same thing happened here
same here
i have the same problem, do i reboot?
any update on this?
Hi there... I had the same issue when I installed the 2.3.6 ATT OTA update when I lost root... I tried RootKeeper application but it didn't work after the OTA installation. I looked for information about this error but didn't find much or complex solutions as to free space from that system dir... so then I thought about if the copy command would have an overwrite option and it did, so I tried it and it worked for me.... I'm rooted again!
I see this is an old post but in case you still need it, it may help you too. I used line bleow to overwrite and the rest you know it.
cp -f /preinstall/su /system/bin/su
by the way, I got an error in the line "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk" telling me that the application or file already existed as I already had superuser installed... I guess it should work without re-installing it, in my case the reinstallation was to a different superuser version... anyway if you want to skip that error and proceed with the re-installation you can use option -r as shown in line below.
PATH=/system/bin:$PATH pm install -r /preinstall/Superuser.apk
cheers!
avelezmtz,
Thanks for the idea, but it did not work for me, I still got the no space left error. Do you know if there a way to delete the SU file and then try to copy it? Thanks
I tried the, PATH=/system/bin:$PATH pm install -r /preinstall/Superuser.apk, command and it was able to reinstall the apk which it never has before so that's good, but it's still not rooted.
If anyone else has any ideas let me know. I am thinking about backing everything up and doing a factory reset and seeing how that goes.
First... as suggestion, if you will be playing deleting files, ensure you have clockworkmod backup or anyother way to restore a previous backup just to be safe.
I think rm command should delete su, but I'm not sure if it would help since the error is not a permissions error, so the ovewrite option should work if the space in the system dir is enough... if you still wanna try the removal of su I think line below will do it.
rm /system/bin/su
Another option I saw somewhere it was about freeing up space by deleting apk files from /system/app dir which is mounted in the same volume, however it would depend on how big those files are. Of course you should back them up first maybe copying them to /sdcard/ for instance. In the post I saw that they removed swype.apk and that was enough for them but in my case it didn't help and as the ovewrite worked I didn't try removing more apps.
If you want to know the space on that dir you can use
df /system/bin/
avelezmtz,
Thanks for all the help, I am now rooted again!!
Using your suggestion I deleted Superuser.apk and Swype.apk from the /system/app directory.
After that I was able to rerun all the commands and get root back. Thanks for all the help, I appreciate it. Sure beats wiping the phone and starting all over again.
I have a problem with my Yu Yureka which running on CM 12.1 and Rooted (su) twrp
1. When I was trying to to flash any zip file like CameraNext Mod, it was flash successfully. After reboot the system, I can't find the CameraNext Mod, it was not in menu.
2. Sometime when i tried to flash other zip file like xposed framework, it was not completely installed. there was error and the error message was " cp:write error: no space left on device"
plz help me with right direction..
Related
Gingerbreak 1.2 goes through the motions, seems to be working, and the phone reboots, but root is not achieved.
Is there any procedure available to root this phone? Even a temporary root?
For the time being I'd like to push one file into /system/framework (framework-res.adk).
Thanks,
Chris
~~~~~~~~~~~~~~~
Phone details:
System version
Version.1.2.148.MB870.Verizon.en.US
Model
Droid X2
Android version
2.2.2
Baseband version
n_03.13.23s
Kernal version
2.6.32.9-00049-g1e05fe4
[email protected] #2
Build number
4.4.1_274_DTN-14.8
ERI version
5
PRL version
52341
Works on all my X2 's
Did you turn on usb debugging, if so try removing gingerbreak, format the sd card, and install gingerbreak again after a fresh boot. Might want to find another source for the gingerbreak apk to. No luck, try another sd card.
USB debugging on, a different formatted SD card used, fresh reboot and downloaded gingerbreak from a different source; same. I have also tried Gingerbreak 1.1 just for kicks.
Check at the very end of your app drawer. I used gingerbreak 1.2 last night and for some reason super user was all the way at the end of the app drawer, not in its alphabetical spot.
just before running gingerbreak
reboot your phone
do not start any other app before starting gingerbreak
this should work
I got my X2 on Friday afternoon.. and rooted it using Gingerbreak Friday evening. I downloaded it from the link provided in the "Getting Started.." thread in this section. So it *should* work, take a deep breath and follow the very good advice given above, take your time and let it do its thing - walk away if you have to in order to avoid panic!
Good luck.
ChrisPappas said:
USB debugging on, a different formatted SD card used, fresh reboot and downloaded gingerbreak from a different source; same. I have also tried Gingerbreak 1.1 just for kicks.
Click to expand...
Click to collapse
Format Sd, and factory reset the phone. Download the apk to your desktop and drag and dropdrop it to the root of your sd and install it from there. A full wipe should rule out any third party apps from causing the problem.
I got the answer for this. The rooting process worked. What was tripping me up is that the partition needed to be remounted as RW.
Chris
Okay, I don't know if I'm rooted or not. I have enabled root access for File Expert and it acts like it's letting me cut and paste into the /system/framework directory, but the original file stays in place. AndroidCommander notates Root=no.
These adb commands are not working:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
TA054029VA device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
$ ^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push framework-res.apk /system/framework/framework-res.apk
failed to copy 'framework-res.apk' to '/system/framework/framework-res.apk': Read-only file system
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb root
adbd cannot run as root in production builds
Su does not change $ to #:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
Root Checker shows the following detailed results:
Congratulations! You have root access!
Standard su binary location:
/system/xbin/su: No such file or directory
Alternale su binary location:
/sbin/su: Permission denied
Root user if:
uid=0(root)
Root group id:
gid=0(root)
Does anyone have any ideas of what can I do to fix?
Thanks,
Chris
I was able to get the abd shell to perform with su. Someone led me to look at the phone when I was typing su in abd shell. The phone was asking for permission, which was opting out after a few seconds. When I approved the access within the window, it gave me the # prompt.
I also found out that adb push needed to have the volume mounted as rw, which I was able to do from the #.
After that, I was able to push a file into the system/framework directory. I bricked the phone doing it because the file I was pushing is apparently very picky (framework-res.apk). Luckily there's an SBF for the droid 2 now.
I'm not sure what the deal is with this root, as it only half-ass works. I rooted a Thunderbolt a couple of weeks ago and I didn't have any of these problems. For example, AndroidCommander on the PC reports no root access.
My next mission is to collect details on the ins and outs of fooling with the framework-res.apk.
Chris
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
The problem:
I rooted my Samsung Galaxy Ace and went exploring the root directory with Root Explorer. I renamed the folder "apk" found in /data to "apk_old", thinking that if everything worked, I could just delete it as it contained a handful of stock apks as well as several apps installed from the market. At the time, I though apks were needed just for installation and that by deleting the folder I would save ~30MB of internal memory. Well, I turns out I was horribly wrong. Several stock apps, such as Youtube or Maps and all market apps that were installed in internal memory have stopped working. In the app drawer, their icons have turned into those default apk icons and their names into com.something.blabla. I was getting crashes every 1-2 minutes from those apps. The widgets on my home screen, such as Google search or Homework 4x2 have also stopped working.
What I've tried:
*renaming the folder back to "apk", obviously. That didn't work, it said something like "execution failed"
*making a copy of the folder - failed
*zipping the folder - failed
*thinking there was a problem with Root Explorer, I installed Total Commander and Solid Explorer hoping I could rename the folder back. Total Commander cannot open the /data folder, while Solid Explorer says the /data folder is empty
*"pulling" all of "/data" with ADB - 0 files pulled.
However, as I was trying to clean up my own mess, things changed a bit. At some point the crashes stopped and all of the "corrupt" apps have simply gone away from the app drawer. While I was unable to do anything with the "apk_old" folder in /data, something changed so that right now I can't even access /data anymore.
So yea, I have a bad feeling that somehow everything inside the /data folder has been wiped, though I sure hope I'm wrong. Anyone have anything to advise?
Oh, and I also noticed that Superuser is gone. I tried re-rooting my phone from this link, it worked the first time I rooted, but not now...
http://forum.xda-developers.com/showthread.php?t=1552792
I don't know exactly what you have in /data/apk I guess is the same I have in /data/app all the installed package.apk
Since your system is compromised I would avoid to use programs from it like Root Explorer to change anything, and for the other programs looks like they don't have root access.
I would try with plain adb: http://forum.xda-developers.com/showthread.php?t=2141817
Once you have your phone connected with adb shell you can go root:
Code:
$ su
to list files and directories in /data
Code:
# ls /data
and then to rename the folder
Code:
# mv /data/apk_old /data/apk
then reboot the phone
good luck
I'm assuming those # signs were suppose to be $'s?, Anyways, what I typed into adb:
1. adb shell
2. $ ls data
What I get:
opendir failed, Permission denied
Another atempt:
1. adb shell
2. $ su
What I get:
su, and after a long pause - Permission denied
eh? So, apparently I can't get root access, what now?
the dficua
Ha, made progress. I installed Superuser through adb and it gave me permission to access data and to rename apk_old back to apk. However, the folder has been wiped of all the apps. Luckily, I have a friend who also has a Galaxy Ace, I'll just copy the folder and paste it into /data, hopefully i'll bring back the default apps.
$ is the normal shell
# is root shell
I forgot to tell you to try that on recovery mode to prevent the calling of SuperUser to grant privilegs, su binary itself should be in /system/xbin
When you restore apps remember also to fix permissions, user and group, it should be something like this:
# chmod 0664 /data/apk/*.apk
# chown system:system /data/apk/*.apk
check the right values in your friend's phone.
Hi all.
I apologize ahead of time that this thread is so long, but I have quite a problem. I am in the process of rooting my unlocked Galaxy S4 running Android 5.0.1 lolipop, but I cannot add the su and busybox to my /system/bin folder because /system is a read-only filesystem. I have done just about everything I can think of to mount and remount, like typing adb remount and mount -o remount,rw /system, but they just give me the same answer saying permission is denied. I tried doing adb root to get the permission I needed, but I got an error message saying that adbd cannot run as root in production builds. After doing some research, I found out that the /default.prop has debuggable=0 and that may be what is not allowing me to restart adb as root. So I opened the shell and typed cat to see and sure enough it was set to 0. So I did echo and set the variable to 1. However, whenever I hit enter, I got another error telling me the same thing, that /default.prop is a read-only file. I am at a loss of what to do now. How I can mount and unmount the /system if I can't get any permission to do so? Any help would be greatly appreciated. I do ask though, please don't recommend ready made apps that can insta-root your phone like a supah-hackah because I want to do this the hard way for gratification's sake. I am just stuck and need some help to get the /system to allow writing as opposed to read-only. Thanks in advance.
So I have rooted Huawei y550 and I messed up build.prop by adding qemu.mainkeys=0 in wrong pace and now when I boot up my phone its stuck at error system ui has stopped but I found a workaround by factory reseting.
So now I can enable usb debugging and stuff.
Anyway I cannot save build.prop when I edit it with root explorer.
And then I try to push it using adb it gave access denied error so I did this chmod 777 /system/build.prop
But now when I try to push the file back it says that directory (or file) is read only.
And I tried many things as adb remount and mount in shell but nothing works.
Also I cannot unloack bootloader because I cannot get code form offical site it says that my ID need to be conneced with my phone atleast 16 days but as the phone is fked I cannot do that (even if i could i have no idea how)
Any help? Thanks!
Edit heres what adb say when I try to chmod
10|[email protected]:/ # chmod -R 777 /system
chmod -R 777 /system
Unable to chmod /system: Read-only file system
10|[email protected]:/ # chmod 777 /system
chmod 777 /system
Unable to chmod /system: Read-only file system
Yeah i ****ed HUAWEI Y550 even harder, nothing works now because changed almost everything, didnt knew it was so important, because its my first android phone. now only few basic apps are running, text, calls, phonebook and chrome(old version). If you will found way to edit it back, please share. i already having this problem for two months.
Evaldas Januskevicius said:
Yeah i ****ed HUAWEI Y550 even harder, nothing works now because changed almost everything, didnt knew it was so important, because its my first android phone. now only few basic apps are running, text, calls, phonebook and chrome(old version). If you will found way to edit it back, please share. i already having this problem for two months.
Click to expand...
Click to collapse
Yes I found rom form manufacturers site, Installed thought system update and it works... Until my friend smashed it.
Here's a tutorial how to do it androidmtk. com/flash-stock-firmware-huawei-smartphone (remove spaces) but I did it bit diffrently. Hope this helps!