Database Develop

[HOW-TO] Enable USB Charging

This guide is to enable USB charging on your Samsung Galaxy Tab.
Requirements:
- Any rooted ROM with Pershoot's kernel
- ScriptManager (free market app)
- USB Charging Script
Procedures
- Ensure you have a rooted rom/custom rom with pershoot's kernel like task650 and PhantomHacker's In Paris rom. Download and install ScriptManager from Android Market. Download the script using the link above and store it anywhere on your tab.
- Open script manager
- Navigate to wherever you stored the script and choose it. Tick run as root and run on boot. Press run.
- If it asks for superuser/root access, please allow it.
- you're done. Press home to exit. Reboot.
Note
Please read and follow all instructions and I am not responsible if anything goes wrong. this should not damage your battery. the reason why samsung disabled usb charging is not because they were worried it would damage the battery. it is because the tab charges very slowly over usb, so they didnt want people to leave a zero battery tablet charging overnight on their pc usb to wake up and find that its only charged 50%.
The common USB connections provide 5 volts DC and between 500mAh to 1,000mAh at most whereas the main power supply provides 12 volts DC and between 1200mAh to 2400mAh. Our Samsung Galaxy Tab needs about 2,000mAh for normal charging. This mod just lets you charge using that low voltage and current from the usb anyways. It is useful for someone like me who never lets the battery drain to zero and I am almost always next to a laptop so when I am watching tv or doing something else, it is always charging.
thanks to pershoot for his kernel, developers on this forum for their excellent roms.
thanks to Giblet-dono for his help and pointers in this thread

dpakrr said:
This guide is to enable USB charging on your Samsung Galaxy Tab. Please read and follow all instructions and I am not responsible if anything goes wrong.
Requirements:
- Any ROM with Pershoot's kernel
- Samsung Mobile drivers (most of you should already have them)
- Latest Android SDK (download the zip file)
- ADB files
Procedure:
- Dont plug in your Galaxy Tab via USB yet. Make a nandroid backup just incase something goes wrong. (Boot into clockworkmod recovery -> backup and restore -> backup)
- Install the Samsung Mobile drivers
- Extract the contents of the sdk zip file onto your desktop. you should get a folder called android-sdk-windows.
- Open this folder and copy all its contents. Go to your C: drive and create a folder called androidsdk and paste the files into this folder.
- Extract the contents of the ADB files zip file you downloaded to C:\androidsdk\tools
- On your tablet, go to Settings->Applications->Development and enable USB debugging. Plug in your Galaxy Tab now.
- On your Windows computer, click on Start and type in cmd in the search bar and press enter.
- type the following and press enter after each line
cd\
cd androidsdk\tools
adb devices
- you should see a combinations of letters and numbers followed by the word device. this means that the adb can interact with your tablet.
- type in the following to enable usb charging (ensure that command prompt is still in the C:\androidsdk\tools folder). again press enter after each line.
adb shell
echo 1 > /sys/class/power_supply/battery/force_usb_charging
exit
you should now be able to charge your tablet via usb.
thanks to pershoot for his kernel, developers on this forum for their excellent roms, and a whole bunch of online guides i looked up on how to access adb lol
Click to expand...
Click to collapse
Will this work on my viewsonic gtablet as well?

hi sorry. like i said in the "requirements", for this to work you need a kernel made by a developer called pershoot. i dont know if hes made any for the viewsonic tablets. please visit his website and see if he has kernels for viewonic tablets and if he has included the option to enable usb charging on them

thats amazing, will try it as soon as possible

SamerBerjawi said:
thats amazing, will try it as soon as possible
Click to expand...
Click to collapse
thanks. let me know how you go.

I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk

halmo20 said:
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Hi thanks. If there's an easier way of ddoing this can you please tell us the steps. I did what you suggested but it says permission denied. Thanks

I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!

Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does is on boot !
Goodluck!
Click to expand...
Click to collapse
Hi thanks. So did you jjust created a script with the following line -
echo 1 > /sys/class/power_supply/battery/force_usb_charging
OK figured it out thx

Work work work, thank you bro .

uomoto said:
Work work work, thank you bro .
Click to expand...
Click to collapse
Your welcome. Are you following the old instructions or the new ones? If you follow the new instructions the usb charging is always set to on even after you restart

Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Click to expand...
Click to collapse
Adding to an existing script works for me. Could not get it working for a new script. Must be missing something. Ironically I just made two cables up tonight with resistors as per other forums. Both hardware and software setups work well! Screw you Samsung
Oh and, THANK YOU for the tip. Go Blacks!

Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?

tallgrasshawk said:
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
Click to expand...
Click to collapse
Yep leave that line there. Press enter to go to the next line. Then type in
su
Press enter again. It should ask for superuser permission which requires root. Allow it root access. Now type in
echo 1 > /sys/class/power_supply/battery/force_usb_charging
And save it and follow the rest of the steps in OP

I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found

tallgrasshawk said:
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
Click to expand...
Click to collapse
Make sure of the following -
- your tablet is rooted
- you have busybox v1.18.2 or lower by downloading busybox installer from market

running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.

tallgrasshawk said:
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
Click to expand...
Click to collapse
Yep its supposed to just sit there. Once you have saved it, just press the back key and choose the file you created. Tick run as root and run on boot and click run. Again it won't do much and it will just show you a command prompt screen. Press home. It should work.
If its getting too complicated for you to follow, I just uploaded my script in the OP. just download it to your tab and run it using ScriptManager. Just tick run as root and run on boot and run it. Thats all. Dont need to type anything.

I tried it, it's working. Thanks for the mod

I'm curious about one thing regarding this mod.
Would it be possible that this can hurt the battery? I mean, what happends to the battery if it gets fed with a current and voltage that is not the current and voltage it was made for? Could that damage the cells?
I'm a computer engineering student but unfortunately we do not study much electronics, perhaps someone with deep electronics and/or chemical knowledge could write something about this? Would be awesome to know more on why/why not it can/can not harm the battery.

Need Help please [solved] !!!

I have Imilika's AOSP ICS ROM V6,
I changed the buid.prop
ro.sf.lcd_density=213
for tablet mode. after I reboot, my GNote is not booting. I cannot go to recovery mode or download mode.
Please help. I don't know what to do

Got it
OK, I was really sad about what happens to my phone, but finally I managed to fix it .
As I told you, my phone was not booting to recovery or download modes (key combinations not worked). finally I try to connect to PC via USB and luckily my PC could detect my phone . So i realized that the problem is the display not coming but phone is halfway booted.
So, I tried to change my build.prop via adb but failed due to cannot grant root permission (becoz display is off).
Finally I issue a adb commad to reboot in recovery mode.
"adb reboot recovery"
yeah, that command directly take me to the CWM recovery. then I flash AOSP v6 again.
Now, my phone is working again.
P.S. I just note this down for others if they get same problem future !

I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!

priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
If you don't know what ADB is, you probably shouldn't be flashing so regularly. Anyway, ADB stands for "Android Debug Bridge" and it is a protocol for device control, development, and debugging.
Sent from my GT-N7000 using Tapatalk

priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
adb is a connection type. we can run shell commands (in the phone), file transfer via adb by using our PC. for that we should have to enable usb debug mode in our mobile.
Actually you might used adb, when you root your phone in the first place . If you have CF-Root zip file, just extract it. you will see a folder called "files", in there you can see adb.exe .
If you need test run,
connect phone via USB(make sure you've enabled USB debug), open command prompt, navigate to that "files" directory.
run "adb shell ls" (to run "ls" command in phone)
run "adb push <anyfile in the PC> /system/sdcard/" (copy files from PC to sdcard)
like that

OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..

priyanv said:
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
Click to expand...
Click to collapse
Its functionality is not only to copy files from pc to mobile and vice versa.You can use it to get logs due to bad flashing,zip align apps,reboot into recovery,DL mode,normal reboot etc...

[Q] [Help] Stuck at the HTC Bootloader with the sdcard, system formatted through CWM

Hello there,
Right now I'm stuck with an HTC one with its complete system wiped out i.e format cache/system/sdcard/media etc via CWM recovery throught the option in mounts and storage (I did that by mistake on CWM, forgetting about how the phone does not have an external sd card which I'm used to...) I don't think its USB debugging option was enabled either because I had fresh unlocked the bootloader so the phone was reset to factory settings, so I don't know if adb sideload is an option. (I don't know how this works either, at least not entirely... only what I learnt over the past 4-5 hours through the web) I feel like i have the adb path set up right, all I need to do is be able to access the device through my computer so I can somehow transfer the ROM zip onto the sdcard so I can install it. Can I just flash the ROM zip through fastboot? I already read around that prolly not but someone mentioned that I can flash the factory stock update... Where can I get that. Help pls! 2 months salary down the drain... replacement is not an option here... there is no customer service where I come from..

crazhy said:
Hello there,
Right now I'm stuck with an HTC one with its complete system wiped out i.e format cache/system/sdcard/media etc via CWM recovery throught the option in mounts and storage (I did that by mistake on CWM, forgetting about how the phone does not have an external sd card which I'm used to...) I don't think its USB debugging option was enabled either because I had fresh unlocked the bootloader so the phone was reset to factory settings, so I don't know if adb sideload is an option. (I don't know how this works either, at least not entirely... only what I learnt over the past 4-5 hours through the web) I feel like i have the adb path set up right, all I need to do is be able to access the device through my computer so I can somehow transfer the ROM zip onto the sdcard so I can install it. Can I just flash the ROM zip through fastboot? I already read around that prolly not but someone mentioned that I can flash the factory stock update... Where can I get that. Help pls! 2 months salary down the drain... replacement is not an option here... there is no customer service where I come from..
Click to expand...
Click to collapse
Check my guide

If u still have cwm recovery u can plug ur phone to pc via USB and select mount USB storage and drop the Rom zip onto internal sd and flash it through recovery.. if not u can download a cwm recovery that u can flash thru adb via command prompt on pc then u can do what I sed earlier
Sent from my HTC Sensation Z710e using xda premium

sibozzy1811 said:
If u still have cwm recovery u can plug ur phone to pc via USB and select mount USB storage and drop the Rom zip onto internal sd and flash it through recovery.. if not u can download a cwm recovery that u can flash thru adb via command prompt on pc then u can do what I sed earlier
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
No you can't

Thank you for the quick response! This is the message I get after typing "adb devices" in the command prompt from the platform tools folder
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
I'd already tried this before but this time I extracted the sdk in C:\ just to see if it made any difference... I even used the command "adb remount" it still says "error device not found". Could this be because of the USB debugging option from the developers menu in settings? I can't make that change right now because i can't boot into the phone! What can i do to correct this?
"C:\adt-bundle-windows-x86-20130522\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86-20130522\sdk\platform-tools>adb remount
error: device not found"
This is what i get in the cmd script
My laptop that i connect to the phone is on a 64 bit operating system does it matter if the sdk i downloaded is for 32 bit?

crazhy said:
Thank you for the quick response! This is the message I get after typing "adb devices" in the command prompt from the platform tools folder
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
I'd already tried this before but this time I extracted the sdk in C:\ just to see if it made any difference... I even used the command "adb remount" it still says "error device not found". Could this be because of the USB debugging option from the developers menu in settings? I can't make that change right now because i can't boot into the phone! What can i do to correct this?
"C:\adt-bundle-windows-x86-20130522\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86-20130522\sdk\platform-tools>adb remount
error: device not found"
This is what i get in the cmd script
My laptop that i connect to the phone is on a 64 bit operating system does it matter if the sdk i downloaded is for 32 bit?
Click to expand...
Click to collapse
did you give up or is this resolved ?

clsA said:
did you give up or is this resolved ?
Click to expand...
Click to collapse
Still looking for a solution!

crazhy said:
Still looking for a solution!
Click to expand...
Click to collapse
are you using MacHackz guide here ? >> http://forum.xda-developers.com/showthread.php?t=2325853
Also do you still have the fastboot folder in c:\fastboot you used to unlock the bootloader ?

crazhy said:
Still looking for a solution!
Click to expand...
Click to collapse
Hop on TeamViewer, think I have the solution

clsA said:
are you using MacHackz guide here ? >> http://forum.xda-developers.com/showthread.php?t=2325853
Also do you still have the fastboot folder in c:\fastboot you used to unlock the bootloader ?
Click to expand...
Click to collapse
Yes I do

MacHackz said:
Hop on TeamViewer, think I have the solution
Click to expand...
Click to collapse
Downloading right now... my internet is really bad today itll be 10 mins to doenload that 5 mb file

crazhy said:
Downloading right now... my internet is really bad today itll be 10 mins to doenload that 5 mb file
Click to expand...
Click to collapse
Will it sustain a connection then ;D

MacHackz said:
Hop on TeamViewer, think I have the solution
Click to expand...
Click to collapse
MacHackz I just had a couple suggestions and I'll step aside
I use the same fastboot folder I used to unlock the bootloader for all adb stuff it contains a working copy of adb
and makes sure the path is easy and correct. (no spaces)
2. I see he mentions using a laptop ..be sure your using a usb 2 port .. not the blue usb 3.0 ports their know to cause issues with adb.

MacHackz said:
Will it sustain a connection then ;D
Click to expand...
Click to collapse
Ill restart it, it reverts to high speeds its just being super spiky right now

MacHackz said:
Will it sustain a connection then ;D
Click to expand...
Click to collapse
Ok lets go! remote control or meeting?
@ clsa, its most deifinitely a usb 2.0 port

crazhy said:
Ok lets go! remote control or meeting?
@ clsa, its most deifinitely a usb 2.0 port
Click to expand...
Click to collapse
Remote just post your id and pass, I will get there first

MacHackz said:
Remote just post your id and pass, I will get there first
Click to expand...
Click to collapse
186 608 490
z57pf4

crazhy said:
186 608 490
z57pf4
Click to expand...
Click to collapse
Black screen ;D

dammit again... i dunno which button to press lol

crazhy said:
dammit again... i dunno which button to press lol
Click to expand...
Click to collapse
Just had the same problem but i got my rom on with usb otg can you try that?
mount usb otg and load zip

H81110N Stock Rooted System Image

Whats up guys, Rydah here again. Here I present you guys with a stock rooted H81110N system image. This is for those who want root but cannot get TWRP to flash prior to root using MicroMod777's "One Click TWRP" tool. I unfortunately was one who couldn't get TWRP to flash before rooting and needed root before doing so but was able to flash TWRP after rooting via my system image.​
Requirements:
An H811 Device
Already On The 10N Base
LG Drivers (Found Here)
A Windows PC
Send_Command Tools (Found Here)
Instructions:
Unzip The Send_Command Tools
Move The Rooted System Image Into The Root Of Your SD Card
Place Your Device Into Download Mode. (Shut Down Your Device. Once Off Holf Vol-Up + Plug In USB Cable)
Go Into Your Send_Command Tool Folder. Once your inside the send_command folder, hold Shift+Right Click and select "Open Command Window Here."
Type in: Send_Command.exe \\.\COM# (Replace the "#" with your devices actual COM number. To find this out, open Window's Device Manager (With your device plugged in) and find it under Ports
Type in: id
You should now have a "#" in the command window.
Type in (Or copy and paste this in): dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
It'll take a few minutes but a successful flash should bring you to another "#" prompt.
Type in: LEAVE
Enjoy
Downloads:
Stock Rooted 10N System Image
MD5: 847cdaf5adaf1b58945e473e8507f8c6
Additional information and clearer instructions can be found here. Same steps and procedures but with a different flash command.
Hope this was useful to some.
Enjoy,
Rydah

Hey. Thanks for doing this.
Should the "if" in the Send_command string point to the folder on the windows computer? It looks like it's pointing to the root of the internal storage as it's written there?

does not seem to work for me. I type in the last command and i get the # right away and reboot the phone and nothing has changed.

It worked for me after I had copied the system image to the root of the internal storage I believe because that command points there. Also, you have to be in Download mode for this to work in case you weren't aware!

custommsp said:
It worked for me after I had copied the system image to the root of the internal storage I believe because that command points there. Also, you have to be in Download mode for this to work in case you weren't aware!
Click to expand...
Click to collapse
i had the file on my sd card. ill move it to internal storage and try again.
and it worked lol thanks

Thank you, it works! Add this step; your phone must be in download mode.

Wooops lol I'll fix instructions
Sent From My LG G4

Rydah805 said:
Wooops lol I'll fix instructions
Sent From My LG G4
Click to expand...
Click to collapse
Did you ever fix the instructions?

YES!
Right. So instructions are not fixed yet. However, as mentioned, placing the image file on root on internal storage and putting phone in download mode gets the job done. Place phone in download mode by holding 'up volume' while plugging in cable and continue to hold until you see it tell you its in the download mode.

You must be on stock N build first?
Sent from my LG-H811 using Tapatalk

aaronrw said:
You must be on stock N build first?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
This system image does not include the 10N bootstack, so yes, you should be on stock N first.

Hey just a few tips
if you already have Android SDK or otherwise an instance of adb.exe installed, you should temporarily uninstall it, so that the adb.exe that is packaged with Send_Command doesn't conflict.
I copied the rootedsystem.img to my phone, used Send_Command, checked my id, and then used the dd command. There is no progress bar on the computer screen, and the progress bar on the phone screen does not move. Do not panic, this is normal.

Updated instructions and added MD5 for download in O.P.

is rootedsystem.img really 4.2g?

Rooted!
Holy Guacamole - this works amazingly well. Thanks much rydah

donbudafuko said:
is rootedsystem.img really 4.2g?
Click to expand...
Click to collapse
Yup... ?
docfreed said:
Holy Guacamole - this works amazingly well. Thanks much rydah
Click to expand...
Click to collapse
Of course. ?
Sent From My LG G4

I like this method best. Thank you!

Thanks for giving us an easy root method.
Sent from my LG-H811

worked perfect. thanks

with this method, will It come with a recovery? and if no, how can it be installed??

How to Solve 'Unauthorize Device' in ADB

Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot

Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

speedyjay said:
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
What does the Android SDK do mate?
I never used it before, so would be great if u can give me some hints
Thanks

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.

android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).

I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

tdamocles said:
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
Click to expand...
Click to collapse
Le_Zouave said:
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
Click to expand...
Click to collapse
Hello sir, i've been trying all of this method, include the wipe the phone (except using another computer) but still no prompt re-appear. Another advice would be greatly appreciated.
Thanks

joho5 said:
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho

toughkid said:
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
Click to expand...
Click to collapse
Have you checked all of your USB ports? I know in the past (with other phones), problems arise if you're not using a direct USB port (one soldered into your MoBo).

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Go to Control Panel > Hardware and Sound > Device Manager > expand Universal Serial Bus controllers. Now connect your phone. You'll now see USB Mass Storage Device. Right click on it. Select Properties, then go to Details. In the Details section, under Property, select Hardware ids. You'll then see the device id. It will be shown something like this: USB\VID_2A70&PID_9011&MI_01. From this you have to take the 2A70 code ~ the code between the first _ and &. Now go to desktop and create a new text document and copy paste this using your device id as shown:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2A70
Now open the Save As menu. In Save As type select All Files. Save the file as adb_usb.ini
Copy this .ini file from desktop and paste it in C:\Users\YourPCName\.android
Disconnect your phone, reboot your pc. Now with USB Debugging turned on, connect your phone to your pc, you'll surely get the permission thingy popup in your phone.

For completion:
If you DO NOT have access to your phone for any reason but still want to use ADB you can simply boot your phone into TWRP and follow these steps.
Windows:
1. Open %userprofile%\.android
2. Copy "adbkey.pub" to your phone (adb push %userprofile%\.android\adbkey.pub /sdcard/adb_keys)
3. Switch to your phone.
4. Go to Advanced > Open Terminal
5. Type in "stop adbd"
6. Move "adb_keys" from /sdcard to /data/misc/adb (mv /sdcard/adb_keys /data/misc/adb/adb_keys)
7. Type in "start adbd"
8. Switch to computer
9. Type "adb shell setprop persist.service.adb.enable 1"
10. Type "adb shell setprop persist.sys.usb.config mtp,adb"
11. Reboot your phone - DONE
Linux / Maybe Mac:
Same steps, but use "~/" instead of "%userprofile%"
Please note:
You may have to repeat the steps 1-7 after boot when still not having permissions so it makes sense to use cp (copy) instead of mv (move) and only repeat steps 5-7.
Edit: Please also check if your drivers are all installed and enabled.
Sent from my OnePlus 2 using XDA Labs

?k