1. ADB doesn't see/detect your phone
- Make sure you're using the latest version of ADB. Download links are posted here.
- The phone is finicky in terms of USB cables. Try the one which came with the phone or a brand new good one.
2. You get a permission error trying to run adb grant com.developer.app android.permission.PERMISSION commands, e.g.
Code:
adb -d shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
Exception occurred while executing 'grant':
java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
at android.app.ContextImpl.enforce(ContextImpl.java:2253)
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:2281)
at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermissionInternal(PermissionManagerServiceImpl.java:1364)
at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermission(PermissionManagerServiceImpl.java:1346)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:553)
at android.permission.PermissionManager.grantRuntimePermission(PermissionManager.java:597)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2591)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:302)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageManagerService.java:6351)
at android.os.Binder.shellCommand(Binder.java:1073)
at android.os.Binder.onTransact(Binder.java:901)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4313)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerService.java:6335)
at android.os.Binder.execTransactInternal(Binder.java:1331)
at android.os.Binder.execTransact(Binder.java:1268)
What you need to do is:
Go to development settings and enable "Disable Permission Monitoring". You'll have to reboot your device afterwards.
3. BetterBatteryStats complains about a lack of access to PrivateAPI
Run this:
Code:
adb -d shell settings put global hidden_api_policy 1
Unfortunately it enables Hidden APIs globally for all apps which could be considered a security risk, so after using BBS you could revert it by:
Code:
adb -d shell settings delete global hidden_api_policy
I still cannot connect with ADB after updating drivers, ADB and using the factory cable.
biggiesmalls657 said:
I still cannot connect with ADB after updating drivers, ADB and using the factory cable.
Click to expand...
Click to collapse
Try rebooting. If it still doesn't help, try to change USB mode: e.g. switch from charging to "File transfer".
birdie said:
Try rebooting. If it still doesn't help, try to change USB mode: e.g. switch from charging to "File transfer".
Click to expand...
Click to collapse
Yes I tried that multiple times and every time I do it says USB malfunction like Windows can't understand it
biggiesmalls657 said:
Yes I tried that multiple times and every time I do it says USB malfunction like Windows can't understand it
Click to expand...
Click to collapse
Share a pic of device manager when device is connected.
biggiesmalls657 said:
Yes I tried that multiple times and every time I do it says USB malfunction like Windows can't understand it
Click to expand...
Click to collapse
That usually indicates you've got a bad cable or/and broken usb port on either of devices (your PC/smartphone).
birdie said:
That usually indicates you've got a bad cable or/and broken usb port on either of devices (your PC/smartphone).
Click to expand...
Click to collapse
Well it does it on all ports on my PC, I've used multiple cables
biggiesmalls657 said:
Well it does it on all ports on my PC, I've used multiple cables
Click to expand...
Click to collapse
Try a different PC, if it's still happening your phone USB port could be faulty.
birdie said:
Try a different PC, if it's still happening your phone USB port could be faulty.
Click to expand...
Click to collapse
I couldn't even get wireless ADB to work but it used to work on my Pixel
Related
The easiest way of getting ADB to work:
Turn your phone OFF (Yes, off)
Connect it to your pc and wait for windows to finish "installing the drivers"
Try ADBing by going to ure fastboot folder (assuming it has the ADB executable inside the folder as well).
You could check if your device was recognized by firing
Code:
adb devices
If it doesn't show anything then do the following:
Grab the appropriate pc drivers from here: http://www.android-advice.com/2012/how-to-root-the-htc-one-x-and-htc-one-s/
Extract the drivers
Now go to Start menu and right click on my computer and then click manage.
Now go to device manager and there you should see your connected One X listed as being without a driver.
Right click on that entry and select 'update driver'
Now tell it that you have the driver on local disk and then browse to the folder you extracted.
Update your driver.
Disconnect and reconnect the device and try ADBing again.
Should work.
If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!
EddyOS said:
If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!
Click to expand...
Click to collapse
That is the thing -- IT DOES SEE IT! Try it yourself.
I didn't think it would but Jotha told me that it would. I tried it and it worked. I was surprised.
Yes device is seen through adb when off.
This is because as soon as you plug the USB cable, offmode comes up with charging and ADB support
Offmode is embeded in the recovery partition
PS: This needs latest clockworkmod recovery to work...
Latest ADB?
Hi!
When i was restoring my Sensation to S-ON i noticed that ADB was complaining about version out of date something....
Where can i get the latest version of ADB for using with my One X when i've decided if i should wait or use hTC bootunlocker...
Is there a way for Linux?
D0GuKaN said:
Is there a way for Linux?
Click to expand...
Click to collapse
Android SDK straight from Google should take care of that.
Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.
DoeBoi said:
Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.
Click to expand...
Click to collapse
No. As long as the cable is properly USB 2.0 compliant, it WILL work, otherwise HTC CANNOT certify against USB 2.0. Tried with proper Nokia, Sony Ericsson, Samsung and Google cables.
that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.
tashunke said:
that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.
Click to expand...
Click to collapse
See here a few posts back:
You have to have the latest clockworkmod recovery.
Can you help/guide me on how to install it ?
Sorry for being a dummy.
Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...
RaVe-N said:
Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...
Click to expand...
Click to collapse
Huh? It's OFF. My guess would be that it's not in any BOOT mode.
rilorolo said:
Huh? It's OFF. My guess would be that it's not in any BOOT mode.
Click to expand...
Click to collapse
Never mind... I found the androidlib.DLL (I think that's wrong, but its a .net DLL available here on xda) and that manages to return fast boot so I can tell programatically what state it's in...
Thanks
Thats Work
.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon: No error
error: cannot connect to daemon: No error
C:\adb>
Click to expand...
Click to collapse
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
Thibor69 said:
.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
Click to expand...
Click to collapse
I can understand the difficulty. This problem is pretty common because there are no official drivers for Win10. These drivers work best on XP. I also could not get the adb to work on my Win10 so I installed Ubuntu and rooting/installing ROM's from ubuntu is a breeze.. srry for not hvng a solution for this.
I have got my device to be recognized by my PC but adb will not work ... Can anyone provide help on how to make it work?
When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.
dratsablive said:
When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.
Click to expand...
Click to collapse
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work
canemaxx said:
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work
Click to expand...
Click to collapse
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?
Lawlrus said:
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?
Click to expand...
Click to collapse
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC
canemaxx said:
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC
Click to expand...
Click to collapse
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computers fingerprint, meaning make alterations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use
Lawlrus said:
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computer fingerprint, meaning make altercations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use
Click to expand...
Click to collapse
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?
canemaxx said:
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?
Click to expand...
Click to collapse
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Try running adb devices and see if it will make the prompt show up
Lawlrus said:
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Click to expand...
Click to collapse
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl
canemaxx said:
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl
Click to expand...
Click to collapse
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.
Lawlrus said:
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.
Click to expand...
Click to collapse
I don't get what else I could do to make this work tho that's the problem....what am I missing
USB debugging enabled?
Heisenberg420 said:
USB debugging enabled?
Click to expand...
Click to collapse
Ues
canemaxx said:
Ues
Click to expand...
Click to collapse
Try running adb kill-server and then adb devices
Heisenberg420 said:
Try running adb kill-server and then adb devices
Click to expand...
Click to collapse
Bro thank you!!!! That worked
canemaxx said:
Bro thank you!!!! That worked
Click to expand...
Click to collapse
Yep
canemaxx said:
I don't get what else I could do to make this work tho that's the problem....what am I missing
Click to expand...
Click to collapse
Adb kill-server worked
I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.
Yooperjusty said:
I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.
Click to expand...
Click to collapse
You have to enable USB Debugging in settings in order to delete the unlock code. Unfortunately, you can't because he forgot it. You can try booting TWRP on the device using fastboot and see if you can delete the unlock code's key file using TWRP's file manager, but the reality here is that you likely will have to reset. Hope your friend didn't use a throwaway email address when setting up the device.
So I tried to flash a rom last night and by accident I hit the option to return the phone to factory. Long story short I can't transfer files and when I try to do fastboot threw that wugsfresh I think it says that my cable is bad I've tried all my cables on all ports. Any ideas?
Sent from my SM-G955U using Tapatalk
fomotomo said:
So I tried to flash a rom last night and by accident I hit the option to return the phone to factory. Long story short I can't transfer files and when I try to do fastboot threw that wugsfresh I think it says that my cable is bad I've tried all my cables on all ports. Any ideas?
Click to expand...
Click to collapse
Is it file transfer in...
- Android?
- TWRP?
- ADB or MTP protocol?
Does fastboot register a new item in Windows device manager? If so, what's the device's VID/PID?
All of the above require different drivers. Please try the following:
- https://developer.android.com/studio/run/win-usb
- https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
k23m said:
Is it file transfer in...
- Android?
- TWRP?
- ADB or MTP protocol?
Does fastboot register a new item in Windows device manager? If so, what's the device's VID/PID?
All of the above require different drivers. Please try the following:
- https://developer.android.com/studio/run/win-usb
- https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Click to expand...
Click to collapse
It doesn't initiate file transfer on twrp and I tried the wugsfresh toolbox or what ever u call it and it gets stuck on the fastboot connection says to retry I've tried all my cables even the OEM one and it keeps that message I even tried it on different ports and I only have one computer so I can't try on a different one
Sent from my SM-G955U using Tapatalk
fomotomo said:
It doesn't initiate file transfer on twrp and I tried the wugsfresh toolbox or what ever u call it and it gets stuck on the fastboot connection says to retry I've tried all my cables even the OEM one and it keeps that message I even tried it on different ports and I only have one computer so I can't try on a different one
Click to expand...
Click to collapse
What about USB VID/PID from Windows device manager? Are you on Linux? If so, post the output of "lsusb". This information is critical to troubleshooting the issue. If in TWRP MTP you get USB\VID_18D1&PID_4EE2 then your PC has a driver problem. If you get USB\VID_000x then your N7 or the cable are faulty.
Let's assume the most likely scenario where you have a broken driver in Windows. In this case, go to the device manager and delete the existing driver associated with Nexus and reboot your PC. When it is running again the driver will be reinstalled and probably OK. If not, get and run this app http://www.uwe-sieber.de/usbtreeview_e.html and compare it to my N7 in TWRP MTP.
Sorry for noob question. Searched Searched xda and can't find anything. Pixel3 xl. Stock Android 10. Rooted. Windows 10 with correct drivers so it sees device. Can transfer files easily. USB debugging enabled. ADB and Fastboot do not see device. Used to work but not now. Tried kill-server and start-server in ADB. Tried different cables, restarting phone and computer. No luck. In fastboot mode (on phone) fastboot devices returns nothing. Totally stumped. Can anyone help. Again apologize for noob question but this has always worked before and I've flashed roms as well as stock numerous times with no issues till now. Help!
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
sliding_billy said:
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
Click to expand...
Click to collapse
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Daisymae said:
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Click to expand...
Click to collapse
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
jd1639 said:
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Click to expand...
Click to collapse
Thanks. Did that. Same thing. Blank list.
Daisymae said:
Thanks. Did that. Same thing. Blank list.
Click to expand...
Click to collapse
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Have you recently updated and not re-authorized your phone?
sliding_billy said:
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Click to expand...
Click to collapse
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
spotmark said:
Have you recently updated and not re-authorized your phone?
Click to expand...
Click to collapse
Turned usb debugging off then back on again. When I plug in a cable I reauthorize usb debugging but get the same results.
Daisymae said:
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
Click to expand...
Click to collapse
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
sliding_billy said:
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
Click to expand...
Click to collapse
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
ktmom said:
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Click to expand...
Click to collapse
No. Tried that first thing. Fastboot devices turns up nothing.
sliding_billy said:
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
Click to expand...
Click to collapse
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Daisymae said:
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Click to expand...
Click to collapse
just for the heck of it, do you have other cables. Stranger things have happened that made a difference, and the next suggestion involves reinstalling computer and/or phone. Maybe a live USB Ubuntu disk to see what is working and what is not.
Daisymae said:
No. Tried that first thing. Fastboot devices turns up nothing.
Click to expand...
Click to collapse
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
ktmom said:
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
Click to expand...
Click to collapse
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Daisymae said:
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Click to expand...
Click to collapse
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Homeboy76 said:
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Click to expand...
Click to collapse
Only one instance of fastboot. Not sure what you mean execute
permissions. You mean on Windows or on the device? Windows has execute permissions. I don't have adb or fastboot on the device.
I investigated the ADB program. At How to Install ADB on Windows, macOS, and Linux, I am stuck at step 7 of the instructions for windows. I do not receive any kind of pop up in my SMJ200G phone (j2).
This step:
7. On your phone’s screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you never want to see that prompt again).
Click to expand...
Click to collapse
Perhaps my PC's connection to the phone is buggy, not the cable, but the software? by software I mean Windows/PC not my phone.
btw does file AdbWinUsbApi.dll need to be installed?
Are the following applicable for a official device that have never been rooted:
NVCore said:
-Missing ADB Confirmation Dialog(can be bypass by placing adb_keys(from PC/Laptop that has platform-tools and the file name is adbkey.pub, rename it to adb_keys) move the file to device (/data/misc/adb)
Click to expand...
Click to collapse
mbalino said:
Unable to detect the phone -win nor Lin
Hello guys
Something really extrange is happening.
My j2 prime -532G- can't be detected by Windows nor Linux.
The usb is working because it charges the phone, but I can't access the phone at all. I checked all the drivers in Win -google/adb and samsung- and in Linux libmtp/heimdall/etc.
I have tryed different usb -not the original one since i lost it-
Even when i start the download mode, nothing happens.
it there a way to root the phone without a PC? i have tryed also kingroot apk but it is useless.
Thanks
Click to expand...
Click to collapse
citation