Hi !
I try to overclock my Spica with CPU Master Pro.apk but when i start it i get the message that Superuser has denied CPU Master Pro permissions.
I have rooted my phone with z4root.apk and with the program from the Unlockroot.com.
I use stock room (Original)
I found this:
__________________________________
1. USB debugging off
2. Plug in the phone to your computer.
3. Turn USB debugging on
4. Open a command prompt and cd to C:\android-sdk-windows\tools
5. type adb shell
6. type su
7. On your phone open up setCPU. It'll then prompt you to allow or disallow SU permissions!
__________________________________
but it didn't work.
Any ideas ?
seriously anyone? almost 100 views..
bump..?
I used this method to try and unroot my mytouch 4g: http://forum.xda-developers.com/showthread.php?t=863899 (it's the most popular way to unroot as some say)
1. Copy PD15IMG.zip and "part7backup-whatevernuberitscalled.bin" to the root of your sdcard
2. Connect your phone to your computer and navigate to your sdk folder then type adb push gfree /data/local
3. Open up terminal emulator or adb shell and type "su" press enter to get root privileges.
4. Type "cd /data/local" and hit enter
5. Type "chmod 777 gfree" and hit enter to make the program executable.
6. Now type "./gfree -f" press enter to run gfree again. It will disable wp on the emmc and remove the brq filter in the kernel. (as well as make another backup. delete this)
I'm stuck on step 6. I typed ./gfree -f but as it runs on my terminal emulator, it ends up saying modile failed to load: No such file or directory.
Can someone please help?
Btw all the other methods consists of two files that needs to be downloaded, however those links leads to a FBI Anti-Piracy warning.
I'm trying to control my Nexus 4 using adb commands from computer, but when I type in adb shell and then su on command prompt I can't click "yes" on the dialog box to enable superuser permissions. How can I do this?
For anyone having the same problem, I found a solution. You'll need USB Debugging for most of this.
-Download a program called MyMobiler to your PC
-Connect your phone via usb and use MyMobiler on the pc toolbar to install the app on the phone
-You'll need to grant superuser permissions if your phone is rooted, so in order to do that you'll need to use adb commands from the Android SDK. Open up a command prompt in the platform-tools folder once you've downloaded SDK
-To get past the lock screen use commands from this link. For me (I don't have a pin or anything, I just needed to get out of the lock screen), I typed "adb shell input keyevent 22" to swipe right to the camera app and then "adb shell input keyevent 3" to hit the home button, which got me to my home screen. If you have a pin, you can type in "adb shell input text 1234" and replace 1234 with whatever your pin is
-Now you can control your screen using the commands on the link above (mainly numbers 19-23)
-If all is running correctly (and you have granted superuser permissions to let MyMobiler run on your phone), you can use the arrow keys to navigate throughout the phone
-If you have any problems, you should follow the MyMobiler start guide
I also followed this guide for help. He uses the app androidscreencast, but that didn't work for me, so I went with MyMobiler.
(as dhayman11 pointed out, "unknown sources" is in security settings, not developer options. but no luck anyway, like most of the settings app, it also crashes if you try to set it.)
instead, here is an extremely stupid idea that just came to me.
1. turn on adb wifi debugging
2. sideload your favorite terminal, e.g.
http://jackpal.github.com/Android-Terminal-Emulator/downloads/Term.apk
(ok I lied. you will need your desktop/laptop/phone/whatever, exactly 1 time. step 2 will be skipped forever after that 1 time.)
3. fire up said terminal from the settings->applications menu.
4. (LOL!)
$ adb devices
4a. if the above command shows no devices,
$ adb connect localhost
and proceed to step 5.
4b. if the command shows exactly 1 device, e.g. "emulator-5554", proceed to step 5.
4c. if the command shows more than 1 device (wtf?!) then you will need to specify a device of your choice ("-s somedevice") in every subsequent adb command, e.g.
$ adb -s emulator-5554 <whatever>
$ adb -s localhost:5555 <whatever>
etc.
5. e.g.
$ adb install /sdcard/Download/foobar.apk
$ adb shell
$ adb uninstall -k com.something.somethingelse
etc. etc.
6. profit? profit!
ok here is a slightly-less incoherent form of the senior-moment-reply I posted earlier
several days ago it occurred to me to alternatively use sshd for terminal access, because:
-a) I feel a little unsafe leaving adb wifi enabled all the time (ok it's only a small thing to turn it on and off, but still) - and for security reasons there is no way to enable/disable it programmatically e.g. from a script/shell/terminal/app (well theoretically this is not exactly true, but practically it is)
-2) some people (i.e. me) would like to do shell/terminal remotely sometimes, rather than on the AFTV (and other people don't have/want a keyboard)
ssh access makes a great alternative to Term.apk, but the problem is:
- Term.apk and/or (pick your favorite android ssh server) don't have permission to run e.g. "pm install foo.apk" - it will fail. (btw 'pm' is a great command, take a look sometime at all the options. it shares a lot of functions as the adb command itself. 'am' is another fun command...)
- so, the hilarious workaround of enabling adb wifi, "adb connect", and then finally "adb shell" or "adb install" etc., is still required. (b/c the adb user is in the 'shell' group, among others - giving it permission to run /system/bin/pm) - oh well.
for random reference:
Code:
127|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
[email protected]:/ $ exit
[email protected]:/ $ id
uid=10009(app_9) gid=10009(app_9) groups=1015(sdcard_rw),1028,3003(inet),50009(app_40009)
(also note it appears the adb shell user might possibly have 'mount' abilities, but since the /dev/block/sd* nodes permissions' are really locked up, who knows...)
Hello, recently I've ran into a stupid problem after unlocking bootloader on my M7. Here is what happened, after unlocking I was not able to use my phone in debugging mode, the authorization pop-up didn't show up wherever I connected my phone to PC in ADB mode. This was not Drivers fault I just lost RSA Key, I managed to get it back, I hope it will help you also.
To get RSA keys you need to do next thing.The trick is to create the .android directory elsewhere, for example on the SD Card:
You need Android Terminal Emulator and Root for this operation. ( Link to Android Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en )
Open Android Terminal Emulator and write:
adb kill-server
HOME=/sdcard adb start-server
At this point you should have /sdcard/.android and the 2 keys in it.
Then just copy adbkey from your phone to your computer into C:/Users/YOURNAME/.android then write in terminal.
stop adbd
start adbd
Then connect you phone in ADB mode Wifi or USB and check again:
adb kill-server
adb start-server
adb devices
Now authorization prompt should pop up!
This issue is also known as Unauthorized device in ADB mode.
Good luck!