Story...
Quick question guys. So I rooted with the one touch root, then grabbed bootstrap recovery, clockwork, made a nandroid backup and upgraded to 2.2 with rom manager.
I then noticed my wireless tethering wasn't working(using wireless tether app), which did work rooted at 2.1. Even normal wireless didn't work. I then wiped all data and did a reset. Wireless now works, however wireless tether app doesn't. I have seen an error in the log while enabling access control in the wireless tether app. I tried reboot, uninstall reinstall with no luck.
I also noticed not having full market, no biggie I have see the build.prop files that will address this.
In an attempt to resolve the wireless tethering problem I was going to make a backup and start from scratch, however now I can't make a backup because I get an error when mounting to my sd card.
"E: Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(Device or resource busy)
Can't mount /sdcard"
What do you think I should do? SBF and start over or....?
Did you do the step to maintain root in 2.2? You are supposed to move "/system/bin/su" to "/system/xbin/su" (mv /system/bin/su /system/xbin/su) which will maintain root throughout the transition. If you didn't, then I'm guessing that you need to reroot in order to get it back.
I did this process as soon as it came out and I don't think that step was in there yet or I missed it. So in short I did not move the file unless the rom manager did it for me. I can still get into superuser and it still prompts me for permission with certain apps. Superuser also shows 3 instances of wireless tether under allowed apps. Can you just move the file now or do I need to attempt to re-root at 2.2?
I figured out what was happening with the backups. I needed to upgrade to bootstrapper 1.0.0.3 from 1.0.0.1. No more mounting problems, however wireless tethering still doesn't work and I am running leaked 2.2 and do have root. Still getting an error in the log showing "Enabling access control....failed" Any ideas?
Related
I used to have superuser/root running fine on my Vibrant. Busybox, titanium backup, everything worked.
I went to install RyanZA's lag fix (specifically the update.zip pack with a new superuser app, different busybox, etc someone else made) and started having troubles. The superuser requests were not working.
Now, I tried to go back to the original update.zip on this thread. I have the original Ninja superuser icon, etc. Now, when programs request SU, I can click allow or deny, the program hangs, and then I get:
"Sorry!
The appication Superuser Permissions (process com.noshufou.android.su) has stopped unexpectedly. Please try again."
And my root access is denied.
I've restarted, used different superuser update.zips, all about 10 times each in different combinations. I can't get past this error.
Question: How can I erase all the root crap I have on my phone and start over fresh? I can't even terminal "SU" to enable superuser.
lag fix...? vibrant isnt fast enough for you?
sigeltek said:
lag fix...? vibrant isnt fast enough for you?
Click to expand...
Click to collapse
I like my Vibrant like my women...not slow.
shadow300z said:
I like my Vibrant like my women...not slow.
Click to expand...
Click to collapse
QUOTE OF THE DAY!!!
As for your issue, you may try contacting the person whose update.zip you used and ask what it modifies/any reported issues like yours, and how to fix it. That's your best bet I think.
Have you tried using Clockwork ROM Manager and restoring to a pre-lag fix state? This same problem happened to me when I tried to install the lagfix from an update.zip file that I tried to access by rebooting the phone while holding down the volume and power keys.
The only way I got the lagfix to install properly was to use Clockwork to restore using nandroid, then used the one-click method (connected to the pc, in debugging mode, etc.). Now everything is working perfectly.
BTW, I have read some folks posting that they can't tell the difference between stock and lagfixed... My experience is exactly the opposite. The Vibrant is *much* faster when lagfixed.
scpieps said:
Have you tried using Clockwork ROM Manager and restoring to a pre-lag fix state? This same problem happened to me when I tried to install the lagfix from an .apk.
The only way I got the lagfix to install properly was to use Clockwork to restore using nandroid, then used the one-click method (connected to the pc, in debugging mode, etc.). Now everything is working perfectly.
Click to expand...
Click to collapse
Clockwork was unable to work because superuser kept crashing. I couldn't do ANYTHING root related.
I did solve the problem though, so for anyone else that has the same issue with SU FCing:
Goto: Menu - Settings - Applications - Manage Applications - Menu button - Filter, Choose to show "all" - Find & choose Superuser Permissions in the list - CLEAR DATA.
This fixed the problem for me, hopefully this will help someone else!
shadow300z said:
Clockwork was unable to work because superuser kept crashing. I couldn't do ANYTHING root related.
I did solve the problem though, so for anyone else that has the same issue with SU FCing:
Goto: Menu - Settings - Applications - Manage Applications - Menu button - Filter, Choose to show "all" - Find & choose Superuser Permissions in the list - CLEAR DATA.
This fixed the problem for me, hopefully this will help someone else!
Click to expand...
Click to collapse
I had this same problem (Clockwork couldn't fix permissions because Superuser Permissions kept FC'ing, and lots of google searching resulted in no help until I found this. Saved me from losing a few days of important text messages because I'm an idiot and hadn't backed up prior to doing a cognition update that didn't go well the first time around. THANK YOU!
worked! you the man my gee
Thanks man..
It seems that it happened when I uninstalled some apps. after that I connected my rooted Desire Z to PC, typed "adb shell" and "su" and.... "permission denied" appeared!
Went through some other apps, and none of them had root access! After rebooting phone, Superuser app crashed, and it kept crashing...
I cleared application data for Superuser app, and - voila! I got my root back again!
Thanks!
Have the droid charge. Superuser stopped working. All my apps started failing with "the application superuser has stopped unexpectedly". Clearing the data didn't do anything. I finally cleared data, uninstalled the superuser app and reinstalled it. Back up and running. Thanks everyone!
Been having issues with the most recent few ARHD ROMs (HTC Sensation), superuser force closing, etc. cleared SU data and all is well again! thanks.
WTF....been rooted for MONTHS and now lost SU permission.
Running jk6 stock (Sombionix)
Lost all SU permissions...TiBU will not fix itself...every SU app has grenaded on me. I keep getting a FC on SU....stoopid ninja icon in the drawer. Never had this issue before even with ODIN'ing back in the 2.1 days. ONCLF doesn't work (macfag) and 2.2 jk6 is running great minus the SU permissions...
HALP.
Cannot even re-install packages...get an E: (can't mount /dev/block/mmcblk0p1 or /dev/block/mmcblk0)
fauk me running....wth happened, did not flash anything since the 2.2 jk6 update.
Bump
Using a chihuahua to post up in this B
I had this problem yesterday, i went to menu, manage applications, and cleared cache for super user
I did a combination of things and somehow resolved it. I couldn't recall what specific step that did it.
1. Took battery,sd card, and sim out for 3 mins.
2. Put battery,sd card, and sim back and turn on phone and disable USB Debugging
3. uninstall and reinstall USB Driver on PC (don't connect usb cable yet).
4. On phone, re-enable USB Debugging
5. connect usb cable to phone and let it reinstall the usb driver
6. After everything is installed correctly, make sure you can mount both int and ext sdcards.
7. Re-install superuser.apk (you may not need to do this)
8. I used ABD to get in recovery mode and did NOT get the " E:... " error.
Hope it helps.
I rooted my phone following these instructions. All seemed great. I then downloaded BusyBox and it says I am root but can't install as I "may not have nand root access".
Also when I connect to the Terminal Emulator I downloaded from the market place and from ADB SHELL I get "Permission denied" when trying to su. Any ideas??
I followed Part 1 and Part 2 in the video. JuiceDefender shows I am root and so does BusyBox. I also have SuperUser application but nothing shows in the logs or in the application list. I figured I get notified if an app asks for SU but nothing notified me. Just "Permission Denied".
Still no idea. Fiddling around with it and it still thinks it's rooted in some applications but a adb shell or terminal emulator (on the phone) and it says SU permission denied.
Do you have a superuser icon?!
yep. sure do. it shows empty logs and applications.
Try and install setcpu or wifi tether and see what u get? If u install setcpu and try and use it and get denied u will know right away if u r really rooted. same with wifi tether, it will say denied!
davidstjohn1 said:
Try and install setcpu or wifi tether and see what u get? If u install setcpu and try and use it and get denied u will know right away if u r really rooted. same with wifi tether, it will say denied!
Click to expand...
Click to collapse
WTF... LOL
Okay, so I download Wireless Tether for Root. Installs fine. Opens fine. Start tethering and get prompted to allow root access from SuperUser. I allow and tethering starts no problem.
So, how come I can't get SU as root? How come I can't install BusyBox (maybe nand not unlocked)?
Problem resolved.
Re-rooted with Unrevoked 3 and it works. Funny because unrevoked failed.
just rooted the vibrant using superoneclick; noticeable slow in apps, not sure if i messed it up, nor i was sure if it's rooted
if i see superuser icon, it should mean that the phone's rooted right?
the write-up mention to download busybox, but all i get is an installer icon, is it a one-time installation or i have to run it everytime? my screen stops at "status: done!" and nothing happens after i click "install" at the bottom
adfree apps cannot connect to host
wasn't able to run root explorer
You might want to download Titanium backup as well. Make sure you "fix Permissions" as well. Without knowing what you rom you are running it's hard to give any other suggestions
Here's my problem,
I had the Droid 2 with stock ROM rooted and all was well. My phone installed the Gingerbread ROM (4.5.601) when Verizon pushed it out a few days ago. Thankfully, this did not totally jack up my phone. However, I no longer have root access.
I have tried three different 1 click root methods for the Gingerbread ROM but none of them worked. I tried un-rooting and re-rooting with one clicks and that's not working. I tried manually removing the Superuser app and rooting, no joy.
The one clicks are connecting with the phone but the phone does not seem to want to allow access to change files.
Before anyone asks, YES I have the drivers installed and the connection with the PC is good. I have attempted to run the 1 click roots in "charge only" AND "PC Mode". Debugging is on and I am set to allow non-market applications.
Suggestions?
Thanks,
Tracker
Update: in trying to manually remove old superuser file with adb shell, I just can't seem to get the # prompt to execute the commands even after running Pete Souza's exploits.
suggestions?
Hope somebody comes up with an answer - same thing happened to me.
did you use the d3 root method? thats the only one that works 100% on gingerbread.
Yes. I used the "Pete's Motorola Root Tools.exe" program on Win7:
psouza4.com/droid3/#root
I also followed the "Droid X Notes" section at the bottom even though I have the D2 and I'm not able to get the "adb shell" ending with #.
SOS!!
Thank you for such a clear, concise post! I am in the same boat with no luck. I used the one click root for D3 which says it will work for a number of Android phones, including the D2 Global, but is NOT working with my D2. I have run the application two times and both times it went through the entire process, rebooted my phone three times and said success but...no success... I am sooo bummed as the only way I get internet at home is via Wireless Tether which I can no longer use because I do not have Root access!
Desperate in Cool (the name of the town I live in), I need help!!
Thanks in advance,
Jeni
Yeah, still no joy here. I've retried everything that I mentioned in the OP and still can't get the # so I can execute an un-root and/or re-root as described on Pete's website.
I've tried it on both a Win XP and a Win 7 machine.
Anyone have any suggestions? It appears the D2 Gingerbread firmware doesn't want to allow permissions to modify certain portions that were allowed before.
Success
I didn't so much fix the problem as hit it with a bat until it shattered, then rebuilt it.
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
At this point I'm getting some force-close errors which I'm sure are related to the Titanium restore but I was able to ADB Shell in and SU so I know I have rooted it properly and at the very least I will do another clean wipe and restore individual applications one at a time so I know which aren't working right and go from there.
Good luck everyone!
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
Click to expand...
Click to collapse
I kinda figured that this would work. I'm trying to avoid a full nuke of the phone, but so far it appears that this is the only work around.
Anyone else got a plan?
Only option I was going to provide was SBF to 2.3.2 with RSDlite and re-flash the OTA, then run the Droid3 exploit.
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
drumster said:
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
Click to expand...
Click to collapse
IMO this instruction should be stickied.
This worked perfectly on my wife's D2G. Rooted Gingerbread = a good start to the day!
Awesome! Thanks!
Just wanted to say I think i love you...this worked for me after two tries on my Droid 2.
First time I was able to remove su and busybox...then when I applied the one click root again, it said there were a bunch of errors but still succeeded. After the reboot I didn't get superuser access yet so I went through deleting su and busybox again (but busybox wasn't found)
The second time i decided to restart my phone before running the script again and when attempting to verify if su was still installed by going into adb shell...it said my phone was already rooted.
Thanks!!
Awesome!
Thanks! This worked for me as well! (after additional reboot)
Good Info but one problem for me
Since I did the OTA Gingerbread, I cannot get into debugging mode. I have uninstalled the Moto drivers & reinstalled using my administrator profile on Windows 7. I have also sbf my phone. Wipe cache. Factory reset. Activate service (NOT download or sync w/ google). OTA Gingerbread. This is on a regualr D2. Anyone have any ideas on how I can get into debugging mode. Otherwise I can't do anything.
Thank you!
I am so glad I found this post and the directions posted by drumster. I had previously used z4root and had not unrooted before allowing the Gingerbread upgrade. Pete's application fixed my Droid 2 on the first attempt; no other steps were needed.
Thanks again,
Andrew
awesome
psouzas 1 click worked for me. Droid 2. previously had rooted with deroot method until it updated by itself to gingerbread which broke root.
enabled usb debugging
in pc mode, clicked on souza's link and followed instructions
i have win 7 64 bit computer
It works
I just got it to work. I was on rooted froyo. Sbf'd back to stock froyo. Downloaded and installed OTA G bread. Then I had to run the D3 one click root method twice but the 2nd time it worked fine.