The built-in Superuser whitelist app in ROM 0.3 worked when I allowed my computer to have superuser access for adb shell, but for any apps on the phone that ask for superuser permission it just loads to a black screen. Eventually a window pops up asking me whether i want to wait or force close. Is there a way to fix this?
EDIT: ok, its seems to work for everything when i have usb plugged in and debug turned on...doing further testing...
EDIT2: confirmed, the whitelist only works when usb is plugged in and debug is enabled. whenever usb in unplugged the whitelist comes up black
EDIT3: no idea what changed but its working for now. ill post again if that changes. i didnt do anything so maybe was a weird temp issue.
Yeah always keep debugging on even if your not connected with the USB.
Because If you're getting a black screen when it asks for SU permission, you probably have Debugging off.
you can do this by going to your Settings-->Applications--> Development-->usb Debugging. Make sure it has a check next to it.
Edit:I know this because I was getting this error and one of the Devs in the IRC told me to make sure debugging was on, after I turned it on I don't have that Problem anymore.
gotcha. i must have turned it off and not remembered doing so. all seems good now.
i also saw your post about it on the other forum right after posting this
Well it's good to have the info in two places, in case people don't check this forum or the others.
superuser whitelist issues
is there a way to remove superuser without harming root? the reason i ask is because i cant get it to work on windows xp, on the original hboot 2.1 root i had no problems with getting adb commands to work etc...
when i flashed .3 i could only get it to go to su/$/# then at that point it would not recognize adb...adb not found or permission denied...(screen was black on su and debug was enabled, no permission requests came up...) any help would be appreciated...
ps
are there a separate set of commands when using the embedded su vs using adb without su permissions? thanks...
Idk maybe it was a bad flash? Have you tried to flash 0_3 again?
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.
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.
I want to root my A7+ WITHOUT installing someone elses custom rom. I just want it rooted long enough that I can push GAPPS onto it. Is there any special trick with Elocity A7+ ??
Will I only be able to do this with earlier versions from Elocity?
The reason I want to do it this way is twofold.
1) I want EVERTHING to keep working.
2) I don't want Superuser snoops.
I can work with ./adb shell on this Linux or it would be even better for someone to show me how to COMPILE the newly released source from Elocity.
Thank you all !!
Dan
as shown in this thread http://forum.xda-developers.com/showthread.php?t=1431967 you could use Z4root.apk
It allows for temporary root
Cheers !
Yes Thanks . I did Z4Root PERMANENT. Did my thing and then turned off root .
I remembered just before coming back to post here. I never used ./adb shell push this time. Couldn't get RW with ./adb so I just copied from GAPPS folder to /system/app/ using Root Explorer.
First time I copied TOO MUCH AND IT WAS IN ENDLESS LOOP.
I repaired and then copied the important stuff...Installed Gmail and then rebooted.
All is well after reboot. But I had to go through Wizard again. Now running everything !!
Dan
another thing that i find funny about this new setup is that bluetooth and foursquare only run when while im rooted????
if i turn off root they dont work
So as I said in my last post, BLUETOOTH only works while rooted. (after having rooted once) So, I wanted to use BLUETOOTH with a new keyboard. I removed Z4root, but left Superuser running in the background. Well , once again, everything seemed to run great for a week, but then things went south. I was getting a reboot loop type thing, about 5 times before it would finally boot up.
I'm not sure, but is suspect this leaves you wide open to a virus or other malicious garbage. So now I'm back to factory with no Gmail or Youtube but I'm finding workarounds.
Dan
This is an Android TV box, equipped with a deeply modified android 4.4 system, while the device is shielded from usb interface adb debugging, the only way to adb is to use root privileges to actively start adb wifi from the device.
I tried kingo root yesterday, and it's the only root tool I've found so far that still works with one click.
Seemed to have good luck as it worked once, but after I rebooted it today, kingo superuser tells me the device is not rooted yet.
I noticed that the location /system/bin/su still has a valid binary file (about 70KB in size).
I even installed a terminal emulator to actively execute the su command, but the result should also be as you guessed, no errors reported and no log output, and again, my permissions did not change from $ to #.
I've tried Google, but haven't found anything useful.
Is there anything I can try to solve this problem? I've tried sending a tweet to kingo root and sending feedback to the official website, but the last tweet on its Twitter feed was sent in 2018 and I think it's unlikely that anyone from the official team will be able to see my feedback.
So I'm trying to ask for help on the XDA forums, this is my first post here and I hope I'm not sending it to the wrong partition.
Thank you all.
===
Finally, I'd like to add a bit of information.
Since kingo root thinks the device is rooted, there is no way for me to get it to perform the root steps all over again.
Also, although kingo superuser provides the ability to remove root, there is no way for me to use it to remove this su file and kingo superuser since it suggests the device is not rooted, which seems to be stuck in a dead end loop
Even because it's a box, I don't even seem to have a way to get into fastboot
===
这是一台安卓的电视盒子，搭载的是经过深度修改的android 4.4系统，同时设备从usb接口上屏蔽了adb调试，想要进行adb的唯一办法就是使用root权限从设备上主动启动adb wifi。
我昨天尝试了kingo root，这是我目前找到唯一的一个还能够运行一键的root工具了。
看起来运气不错，因为一次就成功了，但是我今天重启了它之后，kingo superuser告诉我设备尚未root。
我注意到/system/bin/su这个位置依然存在着有效的二进制文件（大约70KB大小）。
甚至我还安装了一个终端模拟器，主动去执行su命令，但是结果也应该正如你所猜测的那样，没有报错，也没有输出log，同样的，我的权限也没有从$变成#。
我尝试过谷歌，但是没有查到过什么有用的东西。
请问我有什么可以尝试的办法去解决这个问题吗？我已经尝试向kingo root发送推特和向官网上发送反馈，但是它的推特上最后一条推文是在2018年发送的，我认为官方团队不大可能能够有人看到我的反馈。
所以我尝试在XDA论坛上寻求大家的帮助，这是我第一次在这里发帖，希望我没有将帖子发送到错误的分区。
谢谢大家
===
最后，我想补充一点信息。
因为kingo root认为设备已经root了，所以我也没有办法让它重新执行一遍root的步骤。
另外，虽然kingo superuser提供了移除root的功能，但是由于它提示设备无root权限，我也没有办法用它把这个su文件和kingo superuser移除掉，这看起来似乎陷入了一个死循环
甚至因为它是一个盒子，我似乎连进入fastboot的办法都没有