Yes. How to root?
Got root
Found this from goapk forum:
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
Reboot phone
Set USB debugging on
Download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
From here http://forum.xda-developers.com/showthread.php?t=1321582
Unzip, connect usb (dont mount SD) and run runme.bat
Let it do the magic, and when phone reboots, its rooted
sanpsa said:
Got root
Found this from goapk forum:
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
Reboot phone
Set USB debugging on
Download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
From here http://forum.xda-developers.com/showthread.php?t=1321582
Unzip, connect usb (dont mount SD) and run runme.bat
Let it do the magic, and when phone reboots, its rooted
Click to expand...
Click to collapse
Do you using chinise version or overseas? Because it don't work on overseas version.
Overseas and it worked
do not forget to disable fast boot!
Source
Rough translation:
1, download ROOT tools, there are links below. (DooMLoRD_v3_ROOT-zergRush-busybox-su.zip)
2, ensure that ADB drivers are correctly installed
3, turn on usb debugging in settings -> applications -> debugging. turn off fast boot option in settings -> applications
4, open dialer, type *#*#2846579#*#*, projectmenu, background settings, log setting, on, go back, open dump & log, turn on all options.
5 , on the PC run runme.bat
6, wait for the complete restart.
7, OK Congratulations root complete!
Tested myself. Works perfectly.
Edit: ah darn you beat me to it lol. Ah well. :-D
Yep confirmed, this method really works.
Isamu_Dyson said:
Source
Rough translation:
1, download ROOT tools, there are links below. (DooMLoRD_v3_ROOT-zergRush-busybox-su.zip)
2, ensure that ADB drivers are correctly installed
3, turn on usb debugging in settings -> applications -> debugging. turn off fast boot option in settings -> applications
4, open dialer, type *#*#2846579#*#*, projectmenu, background settings, log setting, on, go back, open dump & log, turn on all options.
5 , on the PC run runme.bat
6, wait for the complete restart.
7, OK Congratulations root complete!
Tested myself. Works perfectly.
Edit: ah darn you beat me to it lol. Ah well. :-D
Click to expand...
Click to collapse
You must also turn on Unknown sources from settings >applications>Unknown sources. Otherwise it does not work
Just did this and all went ok.
Shouldn't we have a superuser installed with the rooting?
Because my phone rebooted after rooting but I can't find any SU
it's not working
Superuser is there. Latest version also. Look harder ;-D
I think phone is not rooted as I installed the root explorer and wont show the option to mount R/W
sanpsa said:
Got root
Found this from goapk forum:
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
Reboot phone
Set USB debugging on
Download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
From here http://forum.xda-developers.com/showthread.php?t=1321582
Unzip, connect usb (dont mount SD) and run runme.bat
Let it do the magic, and when phone reboots, its rooted
Click to expand...
Click to collapse
Oila! its working great love it.....
I am getting "adb server is out of date.killing..." and then "daemon started successfully" message after each command it executes and at the end nothing happens.
You may need drivers for adb to work, if you havent used adb before...
Should be in the Mobile partner drive, that pops up when usb is connected...
No i have all drivers and sdk installed.
I rooted the chinese gingerbread version this morning using same tool.Now i have the English version.
Now i get this messages and although it says that is completed,it is not.
---------- Post added at 09:31 PM ---------- Previous post was at 09:03 PM ----------
Ok it seems it was droidexplorer causing this problem.
I uninstalled it and it works fine.
I did a second run and root went ok and SU is now there.
New issue, the PC don't detect the phone anymore.. any ideas?
I' ve successfully root the device with your instructions, thanks. But with DoomLord tool, needed to write command su every time to get root rights in adb shell. So I tried the SuperOneClick method, and rerroot the device. After that I have root uccount automatic, as on froyo rom.
I dont know what happen but my computer stop detecting any USB devices, only pen drives.
will this DooMLoRD_v3_ROOT-zergRush-busybox-su.zip change the PC configuration????
Kamajoo said:
You must also turn on Unknown sources from settings >applications>Unknown sources. Otherwise it does not work
Click to expand...
Click to collapse
Exactly, If you dont do that, superuser.apk doesnt install.
Thanks for the guide guys. I did it with overseas version and it worked. Thanks!
Hi,
I recently rooted my Samsung Galaxy Tab A thanks to the wonderful folks of this forum. However, now that it's rooted I can't seem to connect to it via adb. For example, I see the device listed when I run "adb devices", but it is listed as "unauthorized". I no longer received the prompt to allow USB debugging. More precisely, I can still access the developer options and see that "USB debugging" is enabled, I just don't receive the pop-up prompt to "Allow USB debugging?" that list my local computer's RSA fingerprint/etc after I plug in the usb... the device just remains unauthorized and never asks me to click ok to allow usb debugging.
As suggested elsewhere, I tried removing the adbkey and adbkey.pub in the .android directory on my local computer and the killing/starting the adb server to generate new keys on the local machine, but that also doesn't seem to help...
Additionally, I noted that there is also no longer a button under developer option to "Revoke USB authorizaiton" (maybe because there are now no longer any keys in /data/misc/adb/adb_keys ?)
Any idea how to get adb shell to work again? Or maybe it not possible after rooting?
Thanks!
__adam_ said:
Hi,
I recently rooted my Samsung Galaxy Tab A thanks to the wonderful folks of this forum. However, now that it's rooted I can't seem to connect to it via adb. For example, I see the device listed when I run "adb devices", but it is listed as "unauthorized". I no longer received the prompt to allow USB debugging. More precisely, I can still access the developer options and see that "USB debugging" is enabled, I just don't receive the pop-up prompt to "Allow USB debugging?" that list my local computer's RSA fingerprint/etc after I plug in the usb... the device just remains unauthorized and never asks me to click ok to allow usb debugging.
As suggested elsewhere, I tried removing the adbkey and adbkey.pub in the .android directory on my local computer and the killing/starting the adb server to generate new keys on the local machine, but that also doesn't seem to help...
Additionally, I noted that there is also no longer a button under developer option to "Revoke USB authorizaiton" (maybe because there are now no longer any keys in /data/misc/adb/adb_keys ?)
Any idea how to get adb shell to work again? Or maybe it not possible after rooting?
Thanks!
Click to expand...
Click to collapse
I finally solved this problem.... I don't think it was particular to the Galaxy Tab A.
In order to get adb working again I had to put the device into recovery mode (power down, then power up while holding power, up-volume, home button). I then went to the terminal application of the Team Win Recovery. In terminal I issues "stop adbd" then "start adbd". At this point the device now shows up on the local host PC when I run "adb devices" (it shows up as "recovery" rather than unauthorized). I can adb root/shell to the device now. This is really all I need to do. I expect this will solve my problem in non-recovery mode as well. Or, at this point I can push my PC pub key to the device and it should be fine.
Phone is rooted, TWRP installed, (almost) everything is OK.
What is not OK is that now I cannt ADB connect. The "Allow USB debugging" window with the RSA key does not open at all.
Another thing I've noted - the "Revoke USB debugging authorizations" option in the Developer options - does not exist.
Any ideas as to how to solve this ?
I'm using linux (Arch, 64 bit). Another phone (an older, stock Moto G2) connect with ADB without any problem - so this is not a problem on the computer side, nor a USB cable problem.
Thanks.
Ben
Solved (almost).
After more googling I've found a solution on stackoverflow (as a new user I cannt insert a link) :
Code:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
Now the G5+ is recognized as a "device" with adb.
It's a partial solution because the "Revoke USB debugging authorizations" option is still missing.
Hope this helps future generations
ben-moto said:
After more googling I've found a solution on stackoverflow (as a new user I cannt insert a link) :
Code:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
Now the G5+ is recognized as a "device" with adb.
It's a partial solution because the "Revoke USB debugging authorizations" option is still missing.
Hope this helps future generations
Click to expand...
Click to collapse
+1 to this solution. I have a very similar problem on my HTC One M8. No prompt, also missing the "Revoke USB debugging authorizations" option.
Between this thread, a few others, and that same stackoverflow answer, I was able to come up with a couple of solutions:
[SOLVED] ADB 'unauthorized', no RSA prompt, and no 'Revoke USB debugging' option
I'm experiencing this now, except I still have my "revoke USB auth" option under Dev Options.
I'll try the adb push method now...
OK, this is driving me nuts! The phone has been restored to stock (Android Version 8.0.0) and has nothing on it from the Play Store, just the stock Samsung apps - trying to get ADB to work without any joy, as want Fluid NG on it........
It did once offer the options (weird?), but I got the Allow USB Debugging popup with the RSA Key, but also the error 'Because an app is obscuring a permission request, Settings can't verify your response' error - Went to the 'Apps that can appear on top' section (assume this is the same as 'Draw over other apps?), and disabled everything in the list - still the same error!
Now the only options I get when connecting are:
Transfer Files
Transfer Images
MIDI Device
Charge this Phone
So far I've.......
Enabled Dev mode
Enabled USB debugging
Disabled Verify Apps via USB
Installed Samsung Drivers
Installed ADB Fastboot
Disabled all 'Draw over other apps' apps in the Apps list.
Tried another laptop
Tried another USB cable
It shouldn't be this difficult, I know!!
I haven't been able to get data transfer to work when connected to computer since Color OS 6 update. Pop up warning says resetting USB Debugging is required. Actions already taken :
1. Turn usb debugging on/off
2. Turn developer options on/off
3. Revoke usb debugging (adb devices shows device ID)
4. Enable usb tethering
Any suggestions?
After days of no response and some efforts of painful google-searching , I finally find a solution using adb command which is
adb shell svc usb setfunctions mtp
That being said there should not be any issue with usb / adb driver whatsoever, because I can use file transfer on my LG V30+ just fine using the very same laptop. Also system security check showed usb transfer is being blocked (see attached pics)