Im unable to connect to usb while in recovery because I can't find the drivers. I've installed every drivers I could find and no go. I tried also switching ports and no matter what the driver isnt found and it prevents me from running scripts like the auto debloat because my device cannot be found. im running stock rooted Help!
Did you enable USB debugging?
tonymtl said:
Did you enable USB debugging?
Click to expand...
Click to collapse
Yeah
Why in recovery mode? You can run it booted to ROM.
tonymtl said:
Why in recovery mode? You can run it booted to ROM.
Click to expand...
Click to collapse
well the auto debloat i found needed to be used in cwm. While I would appreciate if you can point me to and alternate solution; I still need figure this out to avoid future mishaps.
I mean you should be booted to ROM with USB debugging on and run it, it will auto reboot to recovery.
tonymtl said:
I mean you should be booted to ROM with USB debugging on and run it, it will auto reboot to recovery.
Click to expand...
Click to collapse
ah gotcha. well I did but when i get to recovery my computer is asking for a driver that cant be found and i have no idea why. the script says that the "device is not found" and im pretty sure this is why. thanks for the help btw
Plug in your phone to PC, it will show locate drivers recommended, leave it.
In Windows go to control panel/system/device manager you'll see one with yellow "?" mark right click on it and update driver software>browse my computer for driver software >let me pick from list>pick Samsung android ADB interface. That should do it.
tonymtl said:
Plug in your phone to PC, it will show locate drivers recommended, leave it.
In Windows go to control panel/system/device manager you'll see one with yellow "?" mark right click on it and update driver software>browse my computer for driver software >let me pick from list>pick Samsung android ADB interface. That should do it.
Click to expand...
Click to collapse
you hit it on the nose. thanks man. now the next problem. all the apps were not found on the debloat script. smh. 1 down 1 to go. many thx
I believe that script was written for international gs3. You can download root browser and manually delete apps you don't like.
tonymtl said:
I believe that script was written for international gs3. You can download root browser and manually delete apps you don't like.
Click to expand...
Click to collapse
yeah i just read about it. what a bust. big help man.
Related
Hello guys, first of all i wanna thank u for your work, i'm a new user but i follow you by a really some times. Today i decided to install the 4.2.1 ROM on my nexus, i deleted all internal file in recovery mode but now when i connect the telephone on pc it doesn't work, maybe because the usb debugging is off and now i don't have any rom on my cellular phone. The problem is that i can't browse my telephone because my pc don't recognize it. i tryed to install some usb driver but nothing has worked then i can put in the now or old rom. how i can solved this problem? Thank u ( and sorry for my english )
NexusPsy said:
Hello guys, first of all i wanna thank u for your work, i'm a new user but i follow you by a really some times. Today i decided to install the 4.2.1 ROM on my nexus, i deleted all internal file in recovery mode but now when i connect the telephone on pc it doesn't work, maybe because the usb debugging is off and now i don't have any rom on my cellular phone. The problem is that i can't browse my telephone because my pc don't recognize it. i tryed to install some usb driver but nothing has worked then i can put in the now or old rom. how i can solved this problem? Thank u ( and sorry for my english )
Click to expand...
Click to collapse
To enable USB debugging, go to settings>about phone>tap on the build number 7 times. It will tell you "you are now a developer" and your will have USB debugging back
As far as your driver issues go, it sounds like you only installed fastboot drivers and not the regular drivers. Or somehow the regular drivers got deleted. If it was me, I would try rebooting my computer and phone. If that doesn't work, run the driver setup wizard in the Galaxy Nexus Toolkit. The first part of that process is deleting old drivers. It does a very thorough walkthrough on how to do that.
rudeguy said:
To enable USB debugging, go to settings>about phone>tap on the build number 7 times. It will tell you "you are now a developer" and your will have USB debugging back
As far as your driver issues go, it sounds like you only installed fastboot drivers and not the regular drivers. Or somehow the regular drivers got deleted. If it was me, I would try rebooting my computer and phone. If that doesn't work, run the driver setup wizard in the Galaxy Nexus Toolkit. The first part of that process is deleting old drivers. It does a very thorough walkthrough on how to do that.
Click to expand...
Click to collapse
Thanks for the answer, the problem is that i don't have any rom on my telephone atm then i can't go to settings ecc. is there a way to change the usb debugging in recovery mode?
NexusPsy said:
Thanks for the answer, the problem is that i don't have any rom on my telephone atm then i can't go to settings ecc. is there a way to change the usb debugging in recovery mode?
Click to expand...
Click to collapse
so you are running stock 4.2.1?
Or...I guess I'm not understand what condition your phone is currently in.
NexusPsy said:
Thanks for the answer, the problem is that i don't have any rom on my telephone atm then i can't go to settings ecc. is there a way to change the usb debugging in recovery mode?
Click to expand...
Click to collapse
Try connecting your GNex to PC while in recovery mode then use ADB to push any ROM from PC to your /sdcard/ of your GNex in order to flash it.
At worst case, I think you can use a fastboot image to flash your GNex via fastboot.
rudeguy said:
so you are running stock 4.2.1?
Or...I guess I'm not understand what condition your phone is currently in.
Click to expand...
Click to collapse
Now i running nothing, pratically i formatted all internal data because i would use the 4.2.1 version that is on my pc, after the format the computer does not recognize my cellular phone, so atm i don't have any rom on my phone and now i don't know how i can solve that, it could be easy if i can browse the phone on computer
ahmadallica said:
Try connecting your GNex to PC while in recovery mode then use ADB to push any ROM from PC to your /sdcard/ of your GNex in order to flash it.
At worst case, I think you can use a fastboot image to flash your GNex via fastboot.
Click to expand...
Click to collapse
It works, thank u < 3
I recently broke my HOX+ and got a GNex for my replacement. Whenever I try to connect it, using another cable (Nexus 7) because its stock cable did not come with the phone (used) I get that pop up which says "Unable to recognize device" or sometimes an error. Though on all events, I get something called Error 43.
Anyone know how to fix this? Ive tried fixing to usb port. It is all stock. I just want to connect so I can root this thing.
Mikeonic said:
I recently broke my HOX+ and got a GNex for my replacement. Whenever I try to connect it, using another cable (Nexus 7) because its stock cable did not come with the phone (used) I get that pop up which says "Unable to recognize device" or sometimes an error. Though on all events, I get something called Error 43.
Anyone know how to fix this? Ive tried fixing to usb port. It is all stock. I just want to connect so I can root this thing.
Click to expand...
Click to collapse
Try installing samsung mtp drivers..
Sent from my Galaxy Nexus
Ive tried
mixtapes08 said:
Try installing samsung mtp drivers..
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I have tried installing drivers...still nothing..
I do assume you're using windows?
And my apologies, are you getting this error message when you try to root?
Were these the MTP drivers you installed?
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
iLeopard said:
I do assume you're using windows?
And my apologies, are you getting this error message when you try to root?
Were these the MTP drivers you installed?
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
Click to expand...
Click to collapse
Yes, Windows 7. Those were the ones and I want to root, but I can't even connect my phone. I'll plug in my GNex and it will charge through the computer though it will not be recognized nor connected for storage purposes.
Mikeonic said:
Yes, Windows 7. Those were the ones and I want to root, but I can't even connect my phone. I'll plug in my GNex and it will charge through the computer though it will not be recognized nor connected for storage purposes.
Click to expand...
Click to collapse
One thing you may want to try if you havent yet:
My Computer -> Right Click -> Properties -> Device Manager (On Sidebar) -> Find the GNex Drivers currently installed and remove them and reinstall (Re-plug) your phone so that the drivers can re-install.
Is this a used or new replacement?
iLeopard said:
One thing you may want to try if you havent yet:
My Computer -> Right Click -> Properties -> Device Manager (On Sidebar) -> Find the GNex Drivers currently installed and remove them and reinstall (Re-plug) your phone so that the drivers can re-install.
Is this a used or new replacement?
Click to expand...
Click to collapse
Unfortunately, the device appears as Unknown Device. It was my Uncles and it was able to work for him. So it bothers me how its not for me. At times even, when I connect the USB to the Device, it causes my Computer to Shut Down abnormally. So, either something is wrong and I need to fix it...or this phone is haunted,
Mikeonic said:
Unfortunately, the device appears as Unknown Device. It was my Uncles and it was able to work for him. So it bothers me how its not for me. At times even, when I connect the USB to the Device, it causes my Computer to Shut Down abnormally. So, either something is wrong and I need to fix it...or this phone is haunted,
Click to expand...
Click to collapse
Even after deleting it?
Did he by chance have it rooted prior to the ownership change?
Is the result replicated in other computers? If you haven't tried, do so. That way you can eliminate either your PC or the GNex as the culprit.
iLeopard said:
Even after deleting it?
Did he by chance have it rooted prior to the ownership change?
Is the result replicated in other computers? If you haven't tried, do so. That way you can eliminate either your PC or the GNex as the culprit.
Click to expand...
Click to collapse
He was stock at all times. Though when I got it, it seemed to be freshly restored...but 5 minutes into using the phone, it froze and gave a fixed screen of something being flashed...though even after I factory restored it again...It wont connect to my All in One PC, Desktop or Laptop, every other device I own connects properly .
Mikeonic said:
He was stock at all times. Though when I got it, it seemed to be freshly restored...but 5 minutes into using the phone, it froze and gave a fixed screen of something being flashed...though even after I factory restored it again...It wont connect to my All in One PC, Desktop or Laptop, every other device I own connects properly .
Click to expand...
Click to collapse
Wierd. Did you try a reset through the stock recovery or just defaults from the security menu?
Here's what I've done. I've pulled my drivers and compressed them. Update the "Unknown Device" from the Device Manager by pointing it to the extracted DLL's and see if that will work.
Drivers
iLeopard said:
Wierd. Did you try a reset through the stock recovery or just defaults from the security menu?
Here's what I've done. I've pulled my drivers and compressed them. Update the "Unknown Device" from the Device Manager by pointing it to the extracted DLL's and see if that will work.
Drivers
Click to expand...
Click to collapse
Been trying and it wont let me push those files and when I do, I get Code Error 10
Mikeonic said:
Been trying and it wont let me push those files and when I do, I get Code Error 10
Click to expand...
Click to collapse
Pushing them? Sorry for my poor explanation. Those files you downloaded are my working drivers that I managed to pull from:
C:\Windows\system32\DRIVERS\UMDF
C:\Windows\system32\DRIVERS\
C:\Windows\system32\
All you have to do is press START -> Type "Device Manager" -> Select the "Unknown Device" -> Press "Update Driver" -> "Browse my computer for driver software" -> Hit "Browse" and point to the folder were the DLL's are located in your computer (Once you have decompressed the archive of course)
iLeopard said:
Pushing them? Sorry for my poor explanation. Those files you downloaded are my working drivers that I managed to pull from:
C:\Windows\system32\DRIVERS\UMDF
C:\Windows\system32\DRIVERS\
C:\Windows\system32\
All you have to do is press START -> Type "Device Manager" -> Select the "Unknown Device" -> Press "Update Driver" -> "Browse my computer for driver software" -> Hit "Browse" and point to the folder were the DLL's are located in your computer (Once you have decompressed the archive of course)
Click to expand...
Click to collapse
It says there are no files in the folder...
UPDATE
It says it FOUND Drivers though cannot execute actions due to error 43
Mikeonic said:
UPDATE
It says it FOUND Drivers though cannot execute actions due to error 43
Click to expand...
Click to collapse
Honestly, I'm stumped. The drivers should have installed correctly regardless. This leads me to believe that its the GN acting up. Again, when you did a reset on it; Did you do it from the Security Submenu or from the Stock Recovery?
Is the device recognized under fastboot? ADB usually works fine there.
iLeopard said:
Honestly, I'm stumped. The drivers should have installed correctly regardless. This leads me to believe that its the GN acting up. Again, when you did a reset on it; Did you do it from the Security Submenu or from the Stock Recovery?
Is the device recognized under fastboot? ADB usually works fine there.
Click to expand...
Click to collapse
It was through the Settings SubMenu, I'll try a Fast boot
Mikeonic said:
It was through the Settings SubMenu, I'll try a Fast boot
Click to expand...
Click to collapse
Also try a factory reset via Stock Recovery. You should find it under the Fastboot menu
iLeopard said:
Also try a factory reset via Stock Recovery. You should find it under the Fastboot menu
Click to expand...
Click to collapse
Still nothing....this is hopeless
Mikeonic said:
Still nothing....this is hopeless
Click to expand...
Click to collapse
Wow, I'm truly amazed how nothing seemed to work. I don't think 1-Click Temp-Root Methods work on the GN, in which case you would use the terminal to Perm-Root it.
This happens on all computers?
Tried Different USB ports?
Rebooting PC?
iLeopard said:
Wow, I'm truly amazed how nothing seemed to work. I don't think 1-Click Temp-Root Methods work on the GN, in which case you would use the terminal to Perm-Root it.
This happens on all computers?
Tried Different USB ports?
Rebooting PC?
Click to expand...
Click to collapse
I will try getting a new USB, maybe a stock if I can find and see if that works. Wish I could root without a USB...Thank You for your help. I will update if anything.
After going through a replacement process (twice) after cracking the screen on my first device, I was relieved to find that the replacement I got sent wasn't updated to un-moddable status. However, after using rumrunner to s-off, flashing cwm 6.0.4.8 recovery, and using that to install cm11 m6 snapshot, I was disappointed to find that my phone will not connect to Windows in a manner where I can access USB storage. Enabling debugging in dev options does initiate the "device plugin sound" from Windows, but after looking in device manager, all that shows up there is "Android ADB Interface". When debugging is disabled, Windows makes no sounds, and there is nothing in the device manager. The only response i'm receiving is that the charge light on the device comes on. I would try to install drivers, but seeing as the computer doesn't even recognize that a device is plugged in, i'm pretty much halted on that front. Any comments or solutions would be greatly appreciated.
Cheers!
StaticSpark said:
After going through a replacement process (twice) after cracking the screen on my first device, I was relieved to find that the replacement I got sent wasn't updated to un-moddable status. However, after using rumrunner to s-off, flashing cwm 6.0.4.8 recovery, and using that to install cm11 m6 snapshot, I was disappointed to find that my phone will not connect to Windows in a manner where I can access USB storage. Enabling debugging in dev options does initiate the "device plugin sound" from Windows, but after looking in device manager, all that shows up there is "Android ADB Interface". When debugging is disabled, Windows makes no sounds, and there is nothing in the device manager. The only response i'm receiving is that the charge light on the device comes on. I would try to install drivers, but seeing as the computer doesn't even recognize that a device is plugged in, i'm pretty much halted on that front. Any comments or solutions would be greatly appreciated.
Cheers!
Click to expand...
Click to collapse
try a different USB port?
also, uninstall HTC drivers. reboot the pc then install the drivers again should fix this.
synisterwolf said:
try a different USB port?
also, uninstall HTC drivers. reboot the pc then install the drivers again should fix this.
Click to expand...
Click to collapse
Unfortunately, as the computer doesn't even react at all when I plug in the device, I can't manipulate drivers at all. That means no uninstalling or installing :/
StaticSpark said:
Unfortunately, as the computer doesn't even react at all when I plug in the device, I can't manipulate drivers at all. That means no uninstalling or installing :/
Click to expand...
Click to collapse
which windows are you on?
also HTC driver was an EXE file so you should be able to find in the uninstall program portion of windows.
synisterwolf said:
which windows are you on?
also HTC driver was an EXE file so you should be able to find in the uninstall program portion of windows.
Click to expand...
Click to collapse
Windows 7. But I never used HTC Sync or anything like that. I didn't install any exe's for drivers
StaticSpark said:
Windows 7. But I never used HTC Sync or anything like that. I didn't install any exe's for drivers
Click to expand...
Click to collapse
ah okay, install sync manager:
http://www.htc.com/us/software/htc-sync-manager/
once the windows sees the phone. feel free to remove the sync portion of the install and keep the driver installer on the pc.
this should fix it and wont mess with ADB or fastboot.
Hehe, thanks. I guess I'm just a little paranoid about having junky, manufacturer specific software on my pc. Will see if this works.
StaticSpark said:
Hehe, thanks. I guess I'm just a little paranoid about having junky, manufacturer specific software on my pc. Will see if this works.
Click to expand...
Click to collapse
me too. :/ but i found that this was the less headache way for me. sync and drivers will show up as 2 different installers. i deleted sync and kept the drivers. im sure one can uninstall the driver installer part of htc software and windows will keep the ini file intact but i never tried this.
synisterwolf said:
me too. :/ but i found that this was the less headache way for me. sync and drivers will show up as 2 different installers. i deleted sync and kept the drivers. im sure one can uninstall the driver installer part of htc software and windows will keep the ini file intact but i never tried this.
Click to expand...
Click to collapse
Thanks for your input! Turns out, i'm an idiot. I had to enable MTP in the usb connection settings >.<
StaticSpark said:
Hehe, thanks. I guess I'm just a little paranoid about having junky, manufacturer specific software on my pc. Will see if this works.
Click to expand...
Click to collapse
Your worried about junky software and you run windows
Glad to see you got everything worked out mate
I flash twrp v2.7.1.1 as my recovery mode.
Managed to go in the recovery, but failed to flash any ROM.
It keep telling me "Installing '/eternal_sd/rom-to-be-installed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/rom-to-be-installed.zip'
Updating partition details...
What should i do? I've done wipe the cache and factory reset but still no luck to install and now i'm stuck and going now where...
please help, i've download the official firmware as well to flash back but yet still the same error... =(
can anyone please help me on this?
:crying::crying::crying:
danieltanz said:
I flash twrp v2.7.1.1 as my recovery mode.
Managed to go in the recovery, but failed to flash any ROM.
It keep telling me "Installing '/eternal_sd/rom-to-be-installed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/rom-to-be-installed.zip'
Updating partition details...
What should i do? I've done wipe the cache and factory reset but still no luck to install and now i'm stuck and going now where...
please help, i've download the official firmware as well to flash back but yet still the same error... =(
can anyone please help me on this?
:crying::crying::crying:
Click to expand...
Click to collapse
Does this even happen flashing tar file of official firmware through Odin?
pdolton2000 said:
Does this even happen flashing tar file of official firmware through Odin?
Click to expand...
Click to collapse
I can't get Odin connected. I plug in windows detected and shows on the task at there but grey off can't accessed it. Odin can't find where it was connected too
danieltanz said:
I can't get Odin connected. I plug in windows detected and shows on the task at there but grey off can't accessed it. Odin can't find where it was connected too
Click to expand...
Click to collapse
Check out device manager whilst connected via USB in download mode, if there's any devices with yellow symbols it probably means you need the adb drivers found here
http://developer.android.com/sdk/win-usb.html
Then Odin should pick up your tab and your in business, Odin is your way out of this I believe.
pdolton2000 said:
Check out device manager whilst connected via USB in download mode, if there's any devices with yellow symbols it probably means you need the adb drivers found here
Then Odin should pick up your tab and your in business, Odin is your way out of this I believe.
Click to expand...
Click to collapse
It does detect in my windows now i can see and through device manager, it has been assigned to com port 2 but odin still failed to detect any incoming port...can i manually tell odin that transfer it via com port 2? Because i did realized when i boot to recovery the first thing will appear is TWRP...that cause the the Odin cant detect it through...
danieltanz said:
It does detect in my windows now i can see and through device manager, it has been assigned to com port 2 but odin still failed to detect any incoming port...can i manually tell odin that transfer it via com port 2? Because i did realized when i boot to recovery the first thing will appear is TWRP...that cause the the Odin cant detect it through...
Click to expand...
Click to collapse
Okay show me a screenshot of device manager whilst tablet is connected in download mode, also expand any sub catogeries that contain either your adb device in it or anything with samsung in it if you can...you shouldn't need to play with com ports really, if the adb USB drivers are installed and the adb device shows up in device manager Odin's meant to detect it automatically, also right click on the adb device in device manager and click properties, and go to the section where it shows driver version and screen shot that just so I can verify a couple of things...sounds to me like its not using googles adb driver but can't be sure.
pdolton2000 said:
Okay show me a screenshot of device manager whilst tablet is connected in download mode, also expand any sub catogeries that contain either your adb device in it or anything with samsung in it if you can...you shouldn't need to play with com ports really, if the adb USB drivers are installed and the adb device shows up in device manager Odin's meant to detect it automatically, also right click on the adb device in device manager and click properties, and go to the section where it shows driver version and screen shot that just so I can verify a couple of things...sounds to me like its not using googles adb driver but can't be sure.
Click to expand...
Click to collapse
What I did is, I uninstall the driver from device manager, reboot my laptop let windows re-detect it again and walla..it found the new hardware and driver being installed again. Run odin, my device added and I flash back the original rom with the download mode and everything back to normal. Thank you so much for your help spending your time to help me troubleshoot together.
Appreciate all your help.
danieltanz said:
What I did is, I uninstall the driver from device manager, reboot my laptop let windows re-detect it again and walla..it found the new hardware and driver being installed again. Run odin, my device added and I flash back the original rom with the download mode and everything back to normal. Thank you so much for your help spending your time to help me troubleshoot together.
Appreciate all your help.
Click to expand...
Click to collapse
That's perfect mate glad it all worked outout for ya.
pdolton2000 said:
That's perfect mate glad it all worked outout for ya.
Click to expand...
Click to collapse
I would like to flash it too lolipop but is it good enough? Will it cause me hang again like before? Any advice
I cannot give you any advice for lollipop as I've never tried it, I only have t805 which its not available for yet, but if I did own a t705 I would definitely take a look at this:
http://forum.xda-developers.com/galaxy-tab-s/development/rom-blisspop-team-bliss-t2987234
Some people love it, some don't...but it seems feature packed anyway...good luck pal enjoy your working tab.
Hi all,
I rooted my M8 recently with the Windroid toolkit. Everything worked great, and I flashed the digitalhigh GPE rom and love it.
Now when I try to connect my phone to my computer, I do not receive the prompt for RSA key trust. My phone shows offline on my 8.1 VM and it is just not found on my Windows 7 machine. It also shows offline on a Macbook Air. I have tried everything I can find to get USB debugging to start working again but I just can't seem to find out what needs to be done. I have the latest version of the HTC drivers I believe and I should have the latest add drivers. On Sense, I had to turn on USB debugging and select the phone to be mounted as a disk drive for WinDroid to be able to root my phone.
So, how can I get this fixed? Is it an issue with the ROM? Is there some way that I can turn on a disk drive mode on the rom.
Any help is appreciated!
Thank you.
Check the device manager in Windows. Does it state a 'unknown device' (or similar)
Sent from my HTC One_M8
Joery360 said:
Check the device manager in Windows. Does it state a 'unknown device' (or similar)
Sent from my HTC One_M8
Click to expand...
Click to collapse
Looking at device manager, it shows my phone in two different places. It shows once in 'other devices' as just android phone and then under 'portable devices' as the name of the phone.
When I go into detail under 'other devices', device manager show that drivers are not installed but says everything is installed correctly under 'portable devices'.
I have the latest version of Sync Manager, so by that reasoning I should have the latest version of the HTC drivers. What else would I need to get my phone to not show as offline?
Thank you
RaspberryRye said:
Looking at device manager, it shows my phone in two different places. It shows once in 'other devices' as just android phone and then under 'portable devices' as the name of the phone.
When I go into detail under 'other devices', device manager show that drivers are not installed but says everything is installed correctly under 'portable devices'.
I have the latest version of Sync Manager, so by that reasoning I should have the latest version of the HTC drivers. What else would I need to get my phone to not show as offline?
Thank you
Click to expand...
Click to collapse
Uninstall Sync Manager. It doesn't play nice with ADB. The only thing it is good for if you are rooted is installing the drivers. After that, get rid of it.
xunholyx said:
Uninstall Sync Manager. It doesn't play nice with ADB. The only thing it is good for if you are rooted is installing the drivers. After that, get rid of it.
Click to expand...
Click to collapse
Hm, alright. I will try that.
Thank you.
Still having issues
Hello all,
I am still having issues with getting my computer to recognize that USB debugging is on and getting it connected to my computer with adb. I have uninstalled sync manager, and yet my phone is still not recognized.
Under debugging in developer options, the only thing I have checked is USB debugging.
Is there something else that needs to be checked in the developer options? Why do I still have this issue?
P.S. I would post pictures, but I can't unfortunately :\
RaspberryRye said:
Hello all,
I am still having issues with getting my computer to recognize that USB debugging is on and getting it connected to my computer with adb. I have uninstalled sync manager, and yet my phone is still not recognized.
Under debugging in developer options, the only thing I have checked is USB debugging.
Is there something else that needs to be checked in the developer options? Why do I still have this issue?
P.S. I would post pictures, but I can't unfortunately :\
Click to expand...
Click to collapse
Hey man, you constantly have to go to here... And change the option from charge only to whatever you want
bford152 said:
Hey man, you constantly have to go to here... And change the option from charge only to whatever you want
Click to expand...
Click to collapse
Thanks for the reply bford152. Oddly, I do not have this option available to me.
I would like to post pictures of the options I have under USB debug. But even posting a link and not having it parse still tries to read it and says I cannot post outside links. Next question, how do I attach photos without adding it as a link to the post. Maybe I'm blind, because I cannot see an option to do this.
Thanks everyone!
What's your adb version ?
It needs 1.0.31 for Android 5.1 and 1.0.32 for Android 6.0 (minimum requirement)
Have you tried with a secured kernel/boot.img ? If you don't have "Revoke USB debugging authorizations" in Developer options - means that you have insecure kernel installed.
ckpv5 said:
What's your adb version ?
It needs 1.0.31 for Android 5.1 and 1.0.32 for Android 6.0 (minimum requirement)
Have you tried with a secured kernel/boot.img ? If you don't have "Revoke USB debugging authorizations" in Developer options - means that you have insecure kernel installed.
Click to expand...
Click to collapse
I have adb version 1.0.32, so all good there.
I don't seem to have "Revoke USB debugging authorizations". So, I have Elite kernel right now and I guess that's the issue. I will get a different kernel and see if that helps.
Thanks!
RaspberryRye said:
I have adb version 1.0.32, so all good there.
I don't seem to have "Revoke USB debugging authorizations". So, I have Elite kernel right now and I guess that's the issue. I will get a different kernel and see if that helps.
Thanks!
Click to expand...
Click to collapse
I got everything to work now. Switched to Cyanogenmod 12.1 and it gives me all the options I need. Thanks for all your help.