I have a little problem, I've just updated franco.Kernel to the last version (8 November) on my phone, but when I try to update the su binary from the Superuser app, I get an error when it tries to mount the /system directory in r/w. I tried to reinstall the ROM and the kernel, but I'm still having the same problem. I tried also to use the old version of kernel (6 November), and I can update su binary, so I think it depends from it. I'm using the last version of Oxygen ROM.
Flash super user from recovery.
Sent from my Nexus S 4G using xda premium
Ok, thanks. But I don't understand why I have this problem, because with other apps (for example Root Explorer) I can mount /system in r/w mode without any problem.
i don't know either, but you should try read that flashable zip, perhaps you can find something interesting
Like I thought, I have problems also with other apps that require to access /system in r/w, so I think I will go back to previous version until it will be fixed.
Related
I rooted my Zoom wifi long ago. Flashed all the various Tiamat kernels and followed bigrushdog's 3.1 update with no problems. I recently flashed the CWR RC 4 over the updated 4.0.1 version in Rom Manager. I now see that all my apps requiring root don't work. I have Super user app but don't get the request to grant su anymore. I tried upgrading Super user within the app but it fails and writes a zip update to SD card which is supposed to be flashed through Recovery but doesn't (I suspect because the file is a 0 byte file!).
Any suggestions on how to get root back?
[Solved]: Seems it was a result of trying to upgrade Superuser that I lost root. See the last post below and the solution Almighty1 offers. It worked and I have root back......
Sent from my Xoom using XDA Premium App
tangiers said:
I rooted my Zoom wifi long ago. Flashed all the various Tiamat kernels and followed bigrushdog's 3.1 update with no problems. I recently flashed the CWR RC 4 over the updated 4.0.1 version in Rom Manager. I now see that all my apps requiring root don't work. I have Super user app but don't get the request to grant su anymore. I tried upgrading Super user within the app but it fails and writes a zip update to SD card which is supposed to be flashed through Recovery but doesn't (I suspect because the file is a 0 byte file!).
Any suggestions on how to get root back?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
There is a problem with the latest recovery version in Rom Manager. The recovery from solarnz is probably not at fault, but maybe the interaction of the two. You wil lneed someone with more knowledge than me to help you get root back, but this issue really needs attention. There are several updates to apps that seem to be breaking our Xooms, and there should be pinned warnings or the developers should be making everyone aware of these conflicts as soon as they find out. I had problems and I'm sure a lot of other folks have have problems with these incompatible app updates as well.
Thanks for that. It almost seems like Superuser is "degrading" in the sense that I had a number of apps reflected in the Superuser app as having been granted root (but not Rom Manager). However, I couldn't add new apps to it. And when I cleared Superuser data and reinstalled it, none of the apps that required root (and which had worked before) would work.
I also think that the writing of a 0 byte zip update file by the Superuser app indicates a problem.
I suspect the solution may lie with fastboot and re-pushing Superuser and CHMOD(?) file permissions but like you, I am nervous to play with these sort of things. My Xoom is working and until I have the need to change the ROM, root doesn't matter to me....
after reading this I checked and also had lost root. I had not checked after after flashing 4.0 in rom manger. Superuser was still there but my apps did not have access. I tried flash a new recovery, reflashing Tiamat nether worked. Anyway from adb
adb remount
adb push su /system/bin/
adb shell
chmod 4755 /system/bin/su
exit
adb push Superuser.apk /system/app/
I then rebooted and had root... updated Superuser as I had an older one in my platform-tools and all is well I then flashed the lastest recovery in rom manger and still have root.
Hope this helps
Thanks. I will give it a try this evening when I get back from work.
Also found this: http://forum.xda-developers.com/showpost.php?p=14643716&postcount=340 which seems similar to your solution.
This is why I hate CWR. I wish we had Amon RA recovery.
I'll try to keep this as short and simple as possible:
I am a total newb to the touchscreen, smart-phone, I just got a USCC Samsung Mesmerize SCH-i500, came installed w/ 2.3.4 Gingerbread & I just had to reflash it w/ USCC EH09 root using Odin 3 v1.85, now, everything I have "hacked" in the past (PSP (both fat & slim), iPod Touch, etc) I've always had to use step-by-step instructions (I am not a dev & know absolutely nothing about programming) & the same applies here.
So, it has root access & BusyBox (I don't even know what that is) installed, so my question is what was the point?
What exactly can/should I do from here? Any suggestions?
well, with a rooted android device you can
*remove bloatware (you're wasting your root if you don't do this)
*system-wide adblock (my personal fav)
*change boot animations
*flash custom ROM
*free wifi tethering
*overclock the CPU
and more!
Thank you for the answer, I'll look into these things but on a side note: my su app keeps saying that theres an update available for my su binary & every time I tap update it goes through the process & less than half-way through it pops up a message saying: "This updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM Manager."
I have tried to use ROM Manager, I even bought the Premium version, either way it gives me the same message, even after doing the Fix Permissions option, is there a way to manually allow su access to the files it needs to overwrite/update?
Oh, and, yes, I have allowed it when su asked, so now I'm at a loss....
Xeno Templar said:
Thank you for the answer, I'll look into these things but on a side note: my su app keeps saying that theres an update available for my su binary & every time I tap update it goes through the process & less than half-way through it pops up a message saying: "This updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM Manager."
I have tried to use ROM Manager, I even bought the Premium version, either way it gives me the same message, even after doing the Fix Permissions option, is there a way to manually allow su access to the files it needs to overwrite/update?
Oh, and, yes, I have allowed it when su asked, so now I'm at a loss....
Click to expand...
Click to collapse
I had the same issue today, couldn't update SU.
but after I had updated the terminal emulator, I was able to update SU.
Fixed the Problem with updating SU Binary
Recently updated my device with a new rom and was unpleasantly surprised to not be able to update my SU binary with either the application itself or CWM. I am not sure that this is the best way to handle the problem, but I found a solution that worked for me.
1. Open "System/XBin" in RootExplorer (or a similar app)
2. Mount the drive as R/W using the button up at the top left
3. Open the superuser app and update the binary from within the app
4. There may be an error in the log about the device not being able to remount the drive properly, but the update WILL occur.
5. Use RootExplorer to open the directory again and mount as R/O.
I hope this helps!
Device: Motorola Droid
ROM: CyanogenMod 6.1.2
Let me know if you need any other info other than this.
1. Cannot update su binary without flashing it from CWM recovery. I am currently up to date with 3.0.3 binary and 3.0.6 apk. See #2 for possible explanation.
2. Everything that calls for root access works except for, what I've noticed, apps that need /system/ and/or its subdirectories to be mounted as rw. *Superuser grants them the privileges, but the apps swear up and down that that isn't the case. Examples: ROM Toolbox, root file managers, etc. *Also, I cannot update busybox. It actually accepts the su privileges, but then fails. I can, however, install it to /mnt/sdcard/, not that that helps me. *There is also an app that has the option of mounting /system/ as rw, and while it says it works, I can't write to the directory or any of its subdirectories from any program. *I have Terminal Emulator, but I don't know enough about it to know what to do if that could help. I've gotten su privileges for it, but it won't let me access /system/. (side note: is there a way to flash busybox from CWM recovery and replace the WLAN files that I need to replace in /system/xbin/ and/or /system/bin/? In other words, since this worked for the su binary, would it work for those? If so, do u know of existing zip files or how I would go about making one?)
3. My wifi connects, tries to establish an ip address, and then is marked disabled and doesn't connect. I currently have it inactive. This has been happening since shortly after installing the CyanogenMod 6.1.2 -- not directly afterwards, but likely after installing and updating all my apps (I didn't install or update any system apps, as I knew not to).
Please let me know if you need to know anything else. I have searched and searched and searched for the answers to this problem, but I can't find it. In a nutshell I can't write to /system unless in recovery, and I can't use wifi at all. I did find some WLAN, etc files to replace the ones in /system with (a supposed wifi fix), but I obviously can't so that without write permissions.
Thank you so much in advance! I've figured out all my other previous issues on my own, but this one is a doozy!
Best,
SNJ
Me too - no mounting rw, busybox pro fails
Hi, I have the same problem on a Galaxy S with CM7.1. It just happened after I updated the last version of busybox pro. My wifi can't connect, everything which needs to mount system as rw fails, root explorer can't even start, and so the installation of busybox pro as well. It shows a huge list of apps which I need to symlink (never asked that before), and after trying installation it says that it appears as a different version of busybox than the one I selected was installed. I wonder if removing all the symlinked apps could do some good instead of leaving the overwrite option checked.
Anyone can help?
thanks
---------- Post added at 12:57 PM ---------- Previous post was at 12:24 PM ----------
just a small add-on. I tried a different busybox installer, and even if superuser indicated root access was granted, the app shut down telling it didn't detect root access.
???
OK, not really....I decided to do a system restore....bang, now I can only boot in recovery mode, not even the previous version but v.3.0.0.5, and I can't mount a thing, I get messages as unknown volume for path, unable process volume!....Now, how can I in any way wipe all and try to reinstall CM 7.1? phone doesn't get in download mode either.
Try flashing and moving files through adb.
I tried searching on the forum for a13 allwinners zeepad 7.0 but can't find anything.
I bought this from amazon,
Android version:
4.0.4
Model number:
A13MID
Kernel Version: 3.0.8
Can someone help me root this tablet?
Anyone? :|
Baoish said:
Anyone? :|
Click to expand...
Click to collapse
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
:good:
deeno33 said:
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
Click to expand...
Click to collapse
So, just install su and it will work?
deeno33 said:
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
Click to expand...
Click to collapse
My daughter just got one of these devices for Christmas, as well. I saw this post as well and thought "Great, I don't have to do the part" so, I installed SuperUser, when I went to update the su binary, which was shown as "Legacy" it got all the way to where it needs to remount the / file system as rw, and to my surprise, it wont remount. Another thing I noticed was that even though it does have su installed, I can't get to the point to where the app even asks for root permission. I tried to update Busybox, as well, and it wouldn't let me even do that... The version which is installed to the tablet appears to be 1.18, but when SuperUser goes to update the su binary it reports back as being the same as the installed version, which I know for a fact that it is not. So while I do in fact have root, it seems to only be a partial root. Anyone willing to throw around some ideas as to where I can go from here to A) get the / file system to remount rw, and B) get SuperUser, an updated su binary and an updated Busybox installed so that I can a full root going and get down to business to installing CWM and CM10 installed and running on here for her.
Any help would be appreciated,
Matt
Yes there is A Solution To This Via A Simple App
meskes said:
My daughter just got one of these devices for Christmas, as well. I saw this post as well and thought "Great, I don't have to do the part" so, I installed SuperUser, when I went to update the su binary, which was shown as "Legacy" it got all the way to where it needs to remount the / file system as rw, and to my surprise, it wont remount. Another thing I noticed was that even though it does have su installed, I can't get to the point to where the app even asks for root permission. I tried to update Busybox, as well, and it wouldn't let me even do that... The version which is installed to the tablet appears to be 1.18, but when SuperUser goes to update the su binary it reports back as being the same as the installed version, which I know for a fact that it is not. So while I do in fact have root, it seems to only be a partial root. Anyone willing to throw around some ideas as to where I can go from here to A) get the / file system to remount rw, and B) get SuperUser, an updated su binary and an updated Busybox installed so that I can a full root going and get down to business to installing CWM and CM10 installed and running on here for her.
Any help would be appreciated,
Matt
Click to expand...
Click to collapse
all zeepads come prerooted and shouldnt block u from updating or to have root access (download root checker) from market
Ur Binarys Should Still Update And Say Current If U Download New Binary Just Wont Show Up Till Reboot
If u Want To Stop This Error While Not Having To Reboot Everytime
Ya This IS Annoying to Do Everytime But Simple solution
THis Proplem IS Do To The Tablet Having A Stock Kernel That Doesnt Allow System Read/Write Access
This Is Why SuperUser Fails Cause It Needs Write Access To The Devices File System...(system/xbin/su)
Which means to Remount system after updating to take Affect And Most Stock Devices Do Not Allow This
so if u updated and it said current version ur ok this is to prevent anymore errors in the future
superuser can have different error witch mean different things just cuz u get one doesnt mean
they didnt take affect but remount of system is the most common error check superuser faq
1.Download Mount System R/W App From PlayStore And Install And Open.
2 .Allow Root Access To The App Then Select Mount System R/W Button
3. Press Home Button And Navigate To SuperUser App And Then Try Updating Binary
This Method Should Work For You
Hope This Works For You
As for cwm and cm9/cm10 it depends if u have a8 or a10 device a13 are not yet supported
MikeG_MG56 said:
all zeepads come prerooted and shouldnt block u from updating or to have root access (download root checker) from market
Ur Binarys Should Still Update And Say Current If U Download New Binary Just Wont Show Up Till Reboot
If u Want To Stop This Error While Not Having To Reboot Everytime
Ya This IS Annoying to Do Everytime But Simple solution
THis Proplem IS Do To The Tablet Having A Stock Kernel That Doesnt Allow System Read/Write Access
This Is Why SuperUser Fails Cause It Needs Write Access To The Devices File System...(system/xbin/su)
Which means to Remount system after updating to take Affect And Most Stock Devices Do Not Allow This
so if u updated and it said current version ur ok this is to prevent anymore errors in the future
superuser can have different error witch mean different things just cuz u get one doesnt mean
they didnt take affect but remount of system is the most common error check superuser faq
1.Download Mount System R/W App From PlayStore And Install And Open.
2 .Allow Root Access To The App Then Select Mount System R/W Button
3. Press Home Button And Navigate To SuperUser App And Then Try Updating Binary
This Method Should Work For You
Hope This Works For You
As for cwm and cm9/cm10 it depends if u have a8 or a10 device a13 are not yet supported
Click to expand...
Click to collapse
Sorry for bringing up an old thread, but I got the a13 and was wondering if anyone was making a cm9/cm10 rom for it as well. I have the a13. I tried to Google and can't find any info about any custom roms for this device.
I used kingRoot version 4.1 Any newer version would not root it.
Hello,
I used "OTA RootKeeper" too "save" my root, and then updated my phone.
I had to re root manually, and since this moment when I try to install busybox or to update su binary my phone reboots.
I tried to manually remove the root (by removing the Superuser.apk and su files), to wipe /data, dalvik_cache, cache etc...
Nothing seems to solve the problem
Does anyone have an idea?
Thanks for your answers!
(Sorry for my English I'm French )
Yep, the jb update has a kernel that write protects /system, at least for the One x and Droid DNA
Is that to say Hassoon's toolkit won't work on a JB updated device?
I've just updated and I'm regretting every minute that I've used it since....
RootJunkie said:
Is that to say Hassoon's toolkit won't work on a JB updated device?
I've just updated and I'm regretting every minute that I've used it since....
Click to expand...
Click to collapse
That means root doesn't really exist on jb.. even if you install su, any changes made will be undone at a reboot
absolutelygrim said:
That means root doesn't really exist on jb.. even if you install su, any changes made will be undone at a reboot
Click to expand...
Click to collapse
What to do?
Actually the phone gets rooted fine busybox is installed, checked with Root Validator after several reboots, but it seems system partition, or something else is not mounted with write privileges.
S-On ?? Maybe? I'm not a HTC guy....
mihaiolimpiu said:
Actually the phone gets rooted fine busybox is installed, checked with Root Validator after several reboots, but it seems system partition, or something else is not mounted with write privileges.
S-On ?? Maybe? I'm not a HTC guy....
Click to expand...
Click to collapse
System is write protected.. due to the kernel, you need s-off or a different kernel, and seeing as there is no kernel source, ICS or aosp are your options. Try making a folder in /system, it should be gone after a reboot
But the files I create from TWRP recovery aren't removed after a reboot. The Superuser.apk is still here after a reboot.
So it seems that I can write to /system from recovery.
Do you know if there's a flashable zip for busybox?
I flashed the one in the JB discussion thread... I think it contains Busybox and SU and it works like a charm... It's a problem but there are workarounds...
For me everything works as long as it doesn't write data to system .
AdBlock works, it gets SU rights but it cannot write the hosts file... I will try later to use the symlink solution...
Su + Busybox
WAY LATER EDIT:
System Partition RW on JB stock roms via kernel module
mihaiolimpiu said:
I flashed the one in the JB discussion thread... I think it contains Busybox and SU and it works like a charm... It's a problem but there are workarounds...
For me everything works as long as it doesn't write data to system .
AdBlock works, it gets SU rights but it cannot write the hosts file... I will try later to use the symlink solution...
http://forum.xda-developers.com/showpost.php?p=35907661&postcount=1928
Click to expand...
Click to collapse
I just tested it and everything I used before on my phone is working again and no more unwanted reboot
Thanks a lot !
I sent a PM to TeHashX, he was asking for review on his work, and also thanked him... His work could benefit others... so make his post more visible!
Remember, that because of the kernel, AdBlock still doesn't work, basically every program that modifies /system works but only apparently. I could use Titanium very well, only Integrate in Rom option doesn't work so take care using "ROOT" on HOS JB.