Develop Bugs

Some problems

Hello,
last week or so I asked about rooting the Defy and flashing a ROM on it via Linux. That worked. It's now running the 2.3.4 leaked 134 build.
But I have a problem with it. I did as the instructions told me to do. Rooted it, nandroided the rooted backup and then flashed the SBF on top of it. So that should mean it's still rooted. But it's not. For some strange reason, it's unrooted now. That's a problem as I have to flash GreenBread for the camera via Clockwork. But I can't install Clockwork back without root. And when I try to root it again via adb, it gives me the error that the system is read-only or not writable or something like that.
What can I do to root it again? Or did I do something wrong?

Indeed. The exact error message is that it's read-only. adb remount gives 'Operation not permitted'. And su gives 'Permission denied', which is really weird as it was rooted before the flashing, including with the nandroid being rooted too. Plus Superuser is still installed, though still no root. Weird.
Please help me.

Is there no one who can help me?

Bumpbump

Busy Box - NO ROOT??

OK, since search is down, I'm going to be a noob and ask something I know has been asked before...
I installed and ran V6 Supercharger yesterday, but wasn't completely sure if it worked properly, so I decided to start again. So I went back to tutorial and started again, first trying to re-install Busybox 1.18.2, as directed. I got message "unable to load busybox onto /sys/xbin". Odd.
So I backed out and opened Busybox installer again, this time got error message "No Root Access!". Tried that a few times, but same message. So I opened Titanium, No Root, MyBackUpRoot...NO ROOT!! 4Ext is also reporting errors, although it does accept SU Permissions...
Ummm...help??
E: Build.prop Editor, ROM manager, RAM Manager Pro, Root Explorer, ES Explorer all granted SU Permissions...

I think I know what may have happened, although don't know how or exactly why... Thinking busybox.apk has been deleted from /system somehow.
I am able to boot to recovery and doing nandroid now, so I obviously still have root. Going to wipe Dalvic and reflash ROM.
Fingers crossed.

Nope.
Did fresh download of Runnymede 6041 and reflashed.
Still same problem. Titanium does not see root, neither does busybox or MbR.
Really not happy now.
Edit: If anyone reading this has experience, where would I find the Busybox.apk, to verify if it was missing and how would I replace??

Have you try to clear superuser data in settings-applications-manage applications ?
I had this problem when I restore data for superuser using mybackup root.
Also check how much free system space that you have before downloading a new busybox. Maybe the free space is not enough for the new busybox.

Download program called visionary and install it. Open it then press (temproot) then keep going on what u doing. Make sure that u having 2.2 android or custom ROM. I did that and update worked as it should with no problem
Sent from my HTC Desire using XDA

Thanks for replies guys.
@mahmoud, want to point out I am root and s-off with custom ROM etc. Not sure if temproot will help me. I'm pretty sure the original Busybox file that is installed during unrEVOked has gone missing. Is that what happened for you too??
As I say, I can still boot to recovery and most SU apps are working...just not those that need Busybox.
@ckp, I will try that this evening. Cheers.

777ace said:
Thanks for replies guys.
@mahmoud, want to point out I am root and s-off with custom ROM etc. Not sure if temproot will help me. I'm pretty sure the original Busybox file that is installed during unrEVOked has gone missing. Is that what happened for you too??
As I say, I can still boot to recovery and most SU apps are working...just not those that need Busybox.
@ckp, I will try that this evening. Cheers.
Click to expand...
Click to collapse
Aaaaaahhhhh ok. Sorry I misunderstood u. What happened to me is that I wanted to root my phone and I couldn't use unrEVOked
Coz it always show me CID MISSING so I downloaded 3 apps and rooted my phone without computer. Visionary, superuser and ROM manager. I had to update busybox in superuser app. But it didn't update until I did temproot using visionary app. I don't know if that will help u or no. But nothing will happen if u downloaded visionary and temproot then try busybox.. let me know if u had any thing. Goodluck
Sent from my HTC Desire using XDA

777ace said:
OK, since search is down, I'm going to be a noob and ask something I know has been asked before...
I installed and ran V6 Supercharger yesterday, but wasn't completely sure if it worked properly, so I decided to start again. So I went back to tutorial and started again, first trying to re-install Busybox 1.18.2, as directed. I got message "unable to load busybox onto /sys/xbin". Odd.
So I backed out and opened Busybox installer again, this time got error message "No Root Access!". Tried that a few times, but same message. So I opened Titanium, No Root, MyBackUpRoot...NO ROOT!! 4Ext is also reporting errors, although it does accept SU Permissions...
Ummm...help??
E: Build.prop Editor, ROM manager, RAM Manager Pro, Root Explorer, ES Explorer all granted SU Permissions...
Click to expand...
Click to collapse
AFAIK, Titanium uses its own Busybox, so I would suggest uninstalling Titanium, reflashing Busybox (I don't know if it's possible), then reflashing Titanium. I hope this will help.

Thanks Coempi, but I did that already... Somehow, whatever tells Busybox or Titanium that I have root, is not doing that.

Dunno wtf just happened, but I uninstalled Titanium again, rebooted (again) and installed Busybox straight up... Everything back to normal, but nfi what I did.
I guess sometimes its the simple things, yeah...??
Thanks for help all.

777ace said:
Dunno wtf just happened, but I uninstalled Titanium again, rebooted (again) and installed Busybox straight up... Everything back to normal, but nfi what I did.
I guess sometimes its the simple things, yeah...??
Thanks for help all.
Click to expand...
Click to collapse
I'm glad it worked out finally.
Sent from my HTC Desire using Tapatalk

Losing root for some reason?? Help

So I used odin to flash the official stock jelllybean rom then I used the Samsung toolkit to flash clockwork mod recovery and root. To root it said to flash a superuser zip in recovery. I did.after I reboot everything is working fine. Apps gain root access the promp pops up but after a few minutes it didn't anymore and I cant open busybox or setcpu because it cant gain access but the apps I already granted can. I updated su binary and it fails on gaining root access.
This happens with both super su and superuser. I also tried starting again by oding rom and rooting again. No luck. Please help
Sent from my SGH-T999 using xda premium

Sent from my SGH-T999 using xda premium

Ok, you can try a few things.
First since you have Root Explorer already granted, go into /system/xbin and make sure that there is a file named su. If not, then go into /system/bin and see if it is there. Follow this: If it is in /system/bin, copy it and put it in /system/xbin, check permissions and reboot. Then try an un-granted app and see if that works. Pay attention to the bin and xbin parts here ok.!?
^^^Edit: While you are in /system/xbin make sure that busybox is there also. Just to be sure it installed properly.
Second. If the above didn't work, the go to the market and ChainsDD used to have an app called SuperUser Updated Fixer or something like that. I remember a long time ago, I was having some trouble updating the binaries (as were tons of other people) and he came out with that handy little app. I have been using it since (whenever I have a ROM that uses SuperUser.apk).
Third: I literally just read over in mrRobinson's thread that ICS likes SuperUser, while JB likes SuperSU. Might be something to look into. Maybe swapping out the two apps, might alleviate the issue.

I tried swapping out to super su but was having the same problem. Instead of trying the root explorer method you posted I thought I would go ahead and clean install yet another time. I just wanted the update and root access to work no errors. So here's what I did to fix it and it worked however there's another problem now.
I factory reset, wiped caches
flashed jb stock firmware (instead of the stock fw i now flashed mr.robinsons prerooted firmware)
rebooted checked and saw super su was working fine with my apps.
flashed clockwork mod recovery
made a nandroid backup
flashed wildchilds stock deodexed jb rom (i needed a deodexed rom thats why i flashed this otherwise i would of just kept stock)
booted up and in the play store theres an update for Super Su however i cant update it, it gives me an error.
error retrieving information from server. cant download.tried wifi on off, mobile data on off, clearing google play data and cache. no luck. restored nandroid and there was no update so i clicked reinstall from playstore in su and when i went to go download it, it gave the same error.
So my previous problem is fixed and i dont seem to be losing root anymore but now I cant update SU anymore.

Never mind I seemed to have linked the two issues just because 1 happened before the other, but that might not be the case.
The Google play error is now happening with other apps that i try to update as well.
Is this happening to you guys too?

sometimes when i power off my phone it doesnt boot anymore it gets stuck on boot loop. for example all i did was fix permissions in cwm and it got stuck on boot loop.

Did you Odin root66?

Yeah I odined the root 66 fw by Robinson. That has fixed losing root. Super user is working fine. The only remaining problem is that I get into a boot loop sometimes when I restart for some reason like when I fix permissions.
Sent from my SGH-T999 using xda premium

[Q] (Self-answered) Easy re-root with TWRP installed.

UPDATE:
After a little more trying, I ended-up using the 'Reinstall' item in SuperSU's settings (from the flashed version). This quit the app, and I re-installed from the play store one more time. This time SuperSU seems to be working fine. My /system was still mounted 'ro' but I was able to resolve this using Terminal Emulator to su (and grant from SuperSU), and running
Code:
mount -o rw,remount /system
.
I seem to be all set again now, perhaps the original unroot was unsuccessful which left the su binary behind... I dont know, but it works now.
ORIGINAL POST:
So,
I rooted, installed TWRP, and installed CleanROM 3.3...
Then my company decided I needed to have GFEinstalled, then they backed off.
I performed the 'Permanent Unroot' in SuperSU to be OK for GFE, but now I want root back (since they arent pushing me, and I want Google Wallet)
Is there an easily done re-root, that I can flash from TWRP? I would prefer to not have to use ODIN to CF-Root and re-install TWRP, if I could just flash back the appropriate stuffs. I tried just re-flashing the SuperSU thing from this forum [04.12.2012] SuperSU v0.99, this did not seem to work (SuperSU would just stop, and /system was still mounted ro)
Thanks in advance!

invisosniperx said:
UPDATE:
After a little more trying, I ended-up using the 'Reinstall' item in SuperSU's settings (from the flashed version). This quit the app, and I re-installed from the play store one more time. This time SuperSU seems to be working fine. My /system was still mounted 'ro' but I was able to resolve this using Terminal Emulator to su (and grant from SuperSU), and running
Code:
mount -o rw,remount /system
.
I seem to be all set again now, perhaps the original unroot was unsuccessful which left the su binary behind... I dont know, but it works now.
ORIGINAL POST:
So,
I rooted, installed TWRP, and installed CleanROM 3.3...
Then my company decided I needed to have GFEinstalled, then they backed off.
I performed the 'Permanent Unroot' in SuperSU to be OK for GFE, but now I want root back (since they arent pushing me, and I want Google Wallet)
Is there an easily done re-root, that I can flash from TWRP? I would prefer to not have to use ODIN to CF-Root and re-install TWRP, if I could just flash back the appropriate stuffs. I tried just re-flashing the SuperSU thing from this forum [04.12.2012] SuperSU v0.99, this did not seem to work (SuperSU would just stop, and /system was still mounted ro)
Thanks in advance!
Click to expand...
Click to collapse
I was just searching for something along this line earlier today. I also run GFE and my company wouldn't think of allowing root access. AES256bit encryption isn't good enough apparently. Anyway, I just posted in the CleanROM thread that I wanted to root/CWM and install and configure the ROM and then unroot via SuperSU - basically EXACTLY what you described. I was curious what I would need to do to re-root in the future if I wanted to. I was wondering if I wanted to try a different ROM, etc then I could gain root again via ODIN, etc and then boot into CWM and nandroid, factory reset, and try the other ROM. When I wanted to revert back, I was hoping there would be some way to restore the nandroid and then flash an unrooted kernel so GFE would not know the difference since the phone never booted with root and GFE at the same time. Even if I could run some ADB commands from a PC while the phone was in CWM, etc then I would learn how to do it if it is even possible. I don't know if I am grasping at straws though...

lost root and other issues

Just wanted to share my bizarre experience..
So last night I was trying to flash a new ROM and I accidentally wiped internal storage during the process, killing my nandroid and everything. I had no OS installed and was basically "soft bricked".
I ram wugfresh's nexus toolkit to reflash the stock image. During this, the toolkit told me that my super SU was outdated as well as TWRP and needed to install updates so I allowed them.
I re unlocked and rooted and installed custom recovery, but once I opened superSU in the ROM it said "no binary has been installed, if you are running android 4.3 you will need to manually root device, please follow forums for support".
I ended up just running the root script in the nexus toolkit and it actually worked the second time in gaining root access.
However... This is the strange part. I have has stability issues and lag since I reinstalled root this time. Paranoid android won't recognize my device in the OTA updater and something just feels off.
Hopefully this won't happen to any of you. I'm going to flash back to stock and retry.
Sent from my Nexus 7 using xda app-developers app

I've seen some other people also have problem with SuperSU. Downgrading from v1.65 to 1.55 apparently fixed whatever problem they had.