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?
Related
Hey all. I have searched but I was unable to find a thread pertaining this issue.
Phone: Android Dev Phone 1
Running: JFv1.50 ADP1.5
What has happened is that today SU/Root seemingly stopped working. I discovered it when I bought Kosh's Screenshot app and started it up. The app requires SU permission, and therefore the "SU Request" window popped up. But it's blank. A blank black screen which eventually will run low on memory and then force close.
I then tried to open the Superuser Permission app, same result. Opened Task Manager for Root Users, same deal. Opened the Terminal Emulator and typed "su", which actually worked! I still had SU privs there. Closed the TE and decided to reboot the phone, and now I don't have SU privs in TE anymore. Everything that's non root related is still working fine.
Does anyone have an idea what's happening here? I suspect that maybe the Market Enabler app or the AdsFree apps could have something to do with it, because they're the only root related apps I have installed the last few weeks, before this problem occurred.
I'm sure a wipe would fix this glitch, but I'd prefer not to do that unless it's necessary. Plus, it would be nice to know what's causing this, so I can avoid it in the future.
Same thing has happened to me. It worked fine for Term Emu, task manager, and ad block. But I tried using an OC app and when super user popped up blank. All my previous apps still work but any new root apps I install do not work. Not sure why though and the only way I found to fix it is to wipe. Do you have your apps on the sd card? I'm using the old method haven't gotten around to trying the new method. Not sure if that is the issue or not, the old version of super user never gave me any issues.
I did a wipe, and it sorted the problem out, for some root apps. Now I'm back to the same crap again though, the SU Request window pops up but it's all black and eventually it force closes.
According JF's blog he included "a much better Superuser app, courtesy of zinx" in the 1.50 release. It's obviously what's causeing our problems, I never had an issue with the old one, but I don't know what to do about it. I don't want to go back to 1.1 or Haykuro's builds. I guess I'm stuck with a semi-crippled JFv1.50 ADP1.5 until someone with more brains than me finds and posts a proper solution.
Yeah Ive been noticing the same thing. Also the superuser list GUI is horrible. I liked how in the last one you can choose what programs you'd want to remove su access from.
andonnguyen said:
Yeah Ive been noticing the same thing. Also the superuser list GUI is horrible. I liked how in the last one you can choose what programs you'd want to remove su access from.
Click to expand...
Click to collapse
Exactly. I'm not sure what he means by "a much better Superuser app", because for a layman like myself it seems a lot worse than the old one
This is just going from bad to worse. Now I discovered I have no positioning via wifi/3G anymore. I have to start the GPS and go outside and wait for a signal to get a lock on my position, which sucks. What the hell is going on? If not even a wipe is enough I guess I'm looking at a complete reinstall, but if all this has happened once it can/will happen again. I would much prefer to find the cause of all this crap.
Ok, so I found the cause for the Assisted GPS issue at least. My Micro SD card needed repairs. I put it in a SD card adapter and plugged it in to my laptop and let Vista repair the file system (apparently there were close to 100 errors on the damn thing) and now it seems to be working again.
Edit: This might actually have fixed my issues with the superuser permissions too. Knock on wood. I'll have to get back to you on this.
I'm having this Exact issue
I am having this exact same issue on dudes build. I have tried everything from scanning to formatting the SD i have flashed back and forth from Jf1.42 to jf1.50 and then to all different dude builds and i have no clue what to do next.
I do a wipe every time i flash and the only way to get any su access is to have jf1.42 or haykuro build. Anyone Else having an issue? I have been working on this for 3 days straight now...
For me it was an SD card issue. If you have a spare card, try that instead, or if you can borrow a card from a friend, just to see if it resolves your problems.
I realize that you have repaired/formatted your SD card, but it could be something wrong with it that screws things up. Worth a try, right?
Absolutely I'm looking for one right now thanks for the quick response. I'll let you know if it works. I have a 2gb sandisk in there now, so i still have my 1gb and my girlfriends 1gb too. Her phone has no su problems at all.
I also ran across the same problem reported here, only a wipe solved it. I believe it had something to do with the Market Enabler (non-signed) app, which was the only one I installed that first showed me the dreadful empty SU screen...
Fixed It
My Problem has been fixed by formatting the sd card with the phone itself.
I copied off all my info, unmounted it from the computer, unmounted it from the phone, this gave the option to format the sd card.
Once that was done i copied all my data back and when i installed programs from my sd i have not had a single su problem since.
I was having all these same problems in JF's 1.5 build, and none of the wiping/formatting SD/trying a different SD card combinations did the trick. Then, I went into JF's blog post where he released 1.5, and someone posted there that enabling USB debugging would fix the issue. I did this, and what do you know, now my superuser permissions app works again in everything, even in unsigned apps! Maybe this is why a wipe fixed it for some people, and not for others?
n17ikh said:
Then, I went into JF's blog post where he released 1.5, and someone posted there that enabling USB debugging would fix the issue. I did this, and what do you know, now my superuser permissions app works again in everything, even in unsigned apps! Maybe this is why a wipe fixed it for some people, and not for others?
Click to expand...
Click to collapse
Not to Jesus resurrect this thread, but I had the same issue and same fix as n17ikh here on the ION build. Enabled USB debugging and su/superuser permissions started working Too bad I have to disable USB debugging in order for my car stereo to mount my G1 as a USB device, but at least I have a solution
Hope this helps anyone else who may stumble upon this.
Hi All,
I viewed the video posted by the Unrevoeked team a little while back about their EVO 4G root and it definitely caught my attention.
http://grack.com/blog/2010/05/23/root-on-an-htc-evo-4g/comment-page-1/#comment-8123
I just noticed today they posted an update on the thread and a link to:
http://unrevoked.com/
If you follow the site they let you download unrevoked.apk
If this APK running in some way means we can root. Well It installs successfully and when you actually run it it says "done." So I believe it does what it is suppose to do on the Eris, I just dont know what steps to take from their.
I have tried installed 2 different superuser apks and neither seems to work. Not sure if I should be doing something else.
PS I am using unrooted OTA
jvward said:
Hi All,
I viewed the video posted by the Unrevoeked team a little while back about their EVO 4G root and it definitely caught my attention.
http://grack.com/blog/2010/05/23/root-on-an-htc-evo-4g/comment-page-1/#comment-8123
I just noticed today they posted an update on the thread and a link to:
http://unrevoked.com/
If you follow the site they let you download unrevoked.apk
If this APK running in some way means we can root. Well It installs successfully and when you actually run it it says "done." So I believe it does what it is suppose to do on the Eris, I just dont know what steps to take from their.
I have tried installed 2 different superuser apks and neither seems to work. Not sure if I should be doing something else.
PS I am using unrooted OTA
Click to expand...
Click to collapse
well just plug in to your pc and go to your adb command window and enter adb remount
adb shell
if you get a # you have root...
jvward said:
Hi All,
I viewed the video posted by the Unrevoeked team a little while back about their EVO 4G root and it definitely caught my attention.
http://grack.com/blog/2010/05/23/root-on-an-htc-evo-4g/comment-page-1/#comment-8123
I just noticed today they posted an update on the thread and a link to:
http://unrevoked.com/
If you follow the site they let you download unrevoked.apk
If this APK running in some way means we can root. Well It installs successfully and when you actually run it it says "done." So I believe it does what it is suppose to do on the Eris, I just dont know what steps to take from their.
I have tried installed 2 different superuser apks and neither seems to work. Not sure if I should be doing something else.
PS I am using unrooted OTA
Click to expand...
Click to collapse
By meaning neither one of them "work" you mean when you press on the app and all you see is a black screen thats all it will do until a program that requires root requires permission to do whatever the app was designed to do. Ohh usb debugging in setting->applications->Development-> USB debugging should be checked.
Hey,
I tested out ADB its not working and by not working I mean neither prompt for superuser permission.
doesnt work
It doesn't work sadly. The Dev's blog is shadowmite. com/blog/ (without the space) if you are looking for any followups though.
It looks like all it does is try and replace/write /system/bin/su but I can't entirely tell. This app is supposed to run something on boot so you may want to try rebooting. Also, it creates a log: /data/DxDrm/unrevoked.log
So I'm stuck at the command prompts. I have messed around with several things, and have also updated the usb driver correctly. Where I am stuck at is getting the adb usb.ini file to show up. I can run C: START adb update usb, and something runs for a split second, but after that I'm still unable to get the ini file to show up. Is there something wrong I'm doing?
just follow this tutorial, its noob proof. I hope this helps........
http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
its easier then the tut here
Well I've tried both tutorials but for some reason I must be doing something wrong, because I'm unable to get the usb driver.ini file to show up, so that it can be copied and pasted to the .android folder. I was advised that I had to do the adb update usb command in cmd, so i tried START adb update usb but all it does is run something for a split second then nothing shows up. I'm in the correct directory as far as I know, and I tried different directories for about 3 hours last night. I was able to successfully update the usb drivers through device manager, not sure if I was supposed to run the adb usb update before actually updating through device manager?
Then you didn't follow the instructions because the file would automatically be there if you did.
Movieaddict, you are a godsend. I did attempt to do this by watching the Youtube vid, but the link you sent me actually just showed pictures of what to do. It worked! Now I just have to figure out what to do now that it's rooted lol. Thanks so much!
jtb224 said:
Well I've tried both tutorials but for some reason I must be doing something wrong, because I'm unable to get the usb driver.ini file to show up, so that it can be copied and pasted to the .android folder. I was advised that I had to do the adb update usb command in cmd, so i tried START adb update usb but all it does is run something for a split second then nothing shows up. I'm in the correct directory as far as I know, and I tried different directories for about 3 hours last night. I was able to successfully update the usb drivers through device manager, not sure if I was supposed to run the adb usb update before actually updating through device manager?
Click to expand...
Click to collapse
Ifd u follow the tut i posted u really cant go wrong, seriously!
why when im trying to install the cm7 on the kindle in the cmd appears this error:
cp: can't stat ' /sdcard/log' : No such file or directory
Please help!
are you on recovery process? I have the same situation, when I try to instal CM7, I instaled recovery first, my be there's a mistake for "log" file, now I can't exit recovery. For I have changed boot mode "idme bootmode 0x5001", it still boot into recovery process when I try to restart it.
Please help.
i am in the beginning of the process and have this error :s
Sent from my Kindle Fire using Tapatalk
Soooo...I'm back again. Finished the root process, everything went hunky-dory until I actually tried to install something from the Android Market. Now everything force closes from Android Market, though my Amazon market still works. Also my games are force closing as well. The only way I can actually get back into the Market is if I clear all data to it, then can do searches. Also with my games, I am completely unable to get to work even after reinstalling them. Any ideas?
jtb224 said:
Soooo...I'm back again. Finished the root process, everything went hunky-dory until I actually tried to install something from the Android Market. Now everything force closes from Android Market, though my Amazon market still works. Also my games are force closing as well. The only way I can actually get back into the Market is if I clear all data to it, then can do searches. Also with my games, I am completely unable to get to work even after reinstalling them. Any ideas?
Click to expand...
Click to collapse
try installing app vending.apk
Sent from my Kindle Fire using Tapatalk
The way I fixed that problem for me was updating market apk
Sent from my Kindle Fire using xda premium
Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!
goalkeepr said:
Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!
Click to expand...
Click to collapse
Nice find, I'll be adding this thread to my Guides / Info Thread....
Thank you dude
Cool Awsome!! Now my phone is working properly with ROOT.
Is this step still needed? Been following the links on DrakenFX's thread that lead me here.
Thanks guys. The dev is much appreciated as is the guide pulling everything together.
Barsky said:
Is this step still needed?
Click to expand...
Click to collapse
Whether it is done by a script (if so there should be clear indication that it does this so people know where they stand in the overall process) or by hand it still needs to be done, it is a completely separate issue from whether or not the boot-loader is unlocked or the phone rooted.
Already did it. :cyclops:
Is this only needed if your bootloader is locked but you still wanna root ?
Ugh, so this was the reason why I couldn't uninstall system apps even w/ a system app uninstaller....
So developer unfriendly :/
Haha needed to do this on the official root for EU as well.
Yay, thanks guys! got adaway running. Starting to feel like home again..now to backup it before I screw it up..
I'm not getting it to work on my Axon 7 rooted with terminal emulator
Sent from my ZTE A2017U using XDA-Developers mobile app
Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong
nickcaper said:
Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong
Click to expand...
Click to collapse
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.
xtermmin said:
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.
Click to expand...
Click to collapse
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all it does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.
nickcaper said:
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all ti does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.
Click to expand...
Click to collapse
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.
xtermmin said:
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.
Click to expand...
Click to collapse
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions
nickcaper said:
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions
Click to expand...
Click to collapse
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.
xtermmin said:
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.
Click to expand...
Click to collapse
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.
nickcaper said:
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.
Click to expand...
Click to collapse
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.
xtermmin said:
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.
Click to expand...
Click to collapse
Can you tell me if your phone is rooted? what update version si your phone? Mine is 27.
Did you do this permission fix before or after root? did you use an emulator to do the fix or adb?
Need some help, got a broken note 4 here and I want to access my files that are still stored inside it. I tried the Vysor Application to see the display but the problem is I forgot the passcode of my phone because i haven't touched that phone for over a month now.
My phone is running custom Note 7 port rom (Ditto Note 7) and I have TWRP installed as a recovery option for my phone. I tried using the adb shell comand su to my phone to remove the gesture.key but it seems that I haven't accept permissions for the adb on my device.
How do I clear the passcode of my phone? or can I clear the settings and data (without internal storage) using TWRP?
Need replies ASAP please
There's probably a few dozen (at least) threads on recovering data on XDA
Did you try the forum search?
I did and amazingly this turned up very quickly
https://forum.xda-developers.com/showthread.php?t=2339530
If that doesn't nail it, try a search yourself, it's free, and easy
Another option is to go to Find my phone/android device manager website, sign in, and unlock the phone, and then connect it to PC and copy as normal....
p.s. the denied on su is most likely because you do not have apps not apps AND adb option enabled in your superuser app under developer settings
stylemessiah said:
There's probably a few dozen (at least) threads on recovering data on XDA
Did you try the forum search?
I did and amazingly this turned up very quickly
https://forum.xda-developers.com/showthread.php?t=2339530
If that doesn't nail it, try a search yourself, it's free, and easy
Another option is to go to Find my phone/android device manager website, sign in, and unlock the phone, and then connect it to PC and copy as normal....
p.s. the denied on su is most likely because you do not have apps not apps AND adb option enabled in your superuser app under developer settings
Click to expand...
Click to collapse
Okay thanks for the reply I'll try the link above