Database Develop

Mounting storage in recovery

So I managed to screw up by wiping both my data and my system, so now I have no os installed and no way to flash an OS from .zip files. Is there anyway for me to add a file to my storage and then flash it via recovery?

jason27131 said:
So I managed to screw up by wiping both my data and my system, so now I have no os installed and no way to flash an OS from .zip files. Is there anyway for me to add a file to my storage and then flash it via recovery?
Click to expand...
Click to collapse
Download a rom and put it in your adb folder
hold in shift and right click on your adb folder - 'open folder in terminal' or similar (not at my computer atm) should be there
Type
adb push name_of_rom.zip /sdcard/
Or
adb sideload name_of_rom.zip
both must be done in recovery. If you do the sideload method, choose the sideload option in recovery - once it transfers it will begin to install automatically. 'adb push' will put the file onto your sdcard then install it yourself in recovery.
Sent from my HTC One using xda premium

Awesome i'll try that. Thanks!

redbull123 said:
Download a rom and put it in your adb folder
hold in shift and right click on your adb folder - 'open folder in terminal' or similar (not at my computer atm) should be there
Type
adb push name_of_rom.zip /sdcard/
Or
adb sideload name_of_rom.zip
both must be done in recovery. If you do the sideload method, choose the sideload option in recovery - once it transfers it will begin to install automatically. 'adb push' will put the file onto your sdcard then install it yourself in recovery.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It says device not found.

What about if you go into fastboot in the bootloader screen and type
fastboot devices
Maybe you need to reinstall your adb files...
Sent from my HTC One using xda premium

then you need to install HTC drivers for your phone. If configured correctly you can do adb devices and it will show up.
If you have drivers installed correctly under device manager the phone shows up as My HTC. Make sure you aren't using a USB 3 port if your computer has one.

Reboot your computer. That worked for me. I did the same thing
Also download HTC all in one tool kit. Its a lifesaver.
Sent from my HTC One using xda app-developers app

fastboot does work. Can i use the adb command in bootloader screen?

jason27131 said:
So I managed to screw up by wiping both my data and my system, so now I have no os installed and no way to flash an OS from .zip files. Is there anyway for me to add a file to my storage and then flash it via recovery?
Click to expand...
Click to collapse
I had same problem nothing was working .i used twrp and from there mount storage as otg as that was only working and put a rom in external pendrive and flash your rom
Sent from my HTC One aka M7

jason27131 said:
fastboot does work. Can i use the adb command in bootloader screen?
Click to expand...
Click to collapse
no only fastboot commands.

So then where do i do the adb commands? In the recovery? I don't get why adb devices isn't giving me anything when fastboot is.

jason27131 said:
fastboot does work. Can i use the adb command in bootloader screen?
Click to expand...
Click to collapse
No, adb must be done in recovery.
Go into recovery and try
adb devices
If nothing shows up you need to re-install/update your adb files and HTC drivers.
If your devices shows up this time then do what I said earlier...
Sent from my HTC One using xda premium

You can either reboot the computer or stop and restart the adb service from the windows management console. The driver for fastboot and adb are the same so I suspect it's something with adb server acting up

I'm guessing you update adb files via sdk manager?

redbull123 said:
Download a rom and put it in your adb folder
hold in shift and right click on your adb folder - 'open folder in terminal' or similar (not at my computer atm) should be there
Type
adb push name_of_rom.zip /sdcard/
Or
adb sideload name_of_rom.zip
both must be done in recovery. If you do the sideload method, choose the sideload option in recovery - once it transfers it will begin to install automatically. 'adb push' will put the file onto your sdcard then install it yourself in recovery.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
gunnyman said:
You can either reboot the computer or stop and restart the adb service from the windows management console. The driver for fastboot and adb are the same so I suspect it's something with adb server acting up
Click to expand...
Click to collapse
I stopped and restarted the adb services and it stil lcan't find the phone. is there any thing specific I have to do in recovery? This is confusing me so much.

jason27131 said:
I stopped and restarted the adb services and it stil lcan't find the phone. is there any thing specific I have to do in recovery? This is confusing me so much.
Click to expand...
Click to collapse
How hard is to flash via external flash drive using micro usb otg in recovery menu
Sent from my HTC One aka M7

Remove and reinstall the driver

zinder33 said:
How hard is to flash via external flash drive using micro usb otg in recovery menu
Sent from my HTC One aka M7
Click to expand...
Click to collapse
Reasonably hard if he doesn't have a USB OTG cable atm...
Sent from my HTC One using xda premium

zinder33 said:
How hard is to flash via external flash drive using micro usb otg in recovery menu
Sent from my HTC One aka M7
Click to expand...
Click to collapse
Very, since clicking on the micro-otg doesn't do anything. I managed to get sideload working I believe. It's at 40%, hopefully it is sideloading the file.

jason27131 said:
Very, since clicking on the micro-otg doesn't do anything. I managed to get sideload working I believe. It's at 40%, hopefully it is sideloading the file.
Click to expand...
Click to collapse
Should be good to go
If it freezes in Aroma just force reboot and try again.
Sent from my HTC One using xda premium

Adding ROMs to completely empty phone.

I stupidly showed my teenage son how to use ROM Manager and CWM on my phone.
He has now completely deleted (and I feel formatted) ALL Data etc on the phone.
So, as I cannot use any software on my MAC to transfer ROMs to the phone CAN Someone please advise how to get a ROM on the phone?
I can still access CWM Recovery. I have Android SDK installed, including Eclipse.
Please remember I am using a MAC, when you helpfully pass on ideas or solutions

Go to adb and fastboot folder, boot into recovery and use the command from terminal:
Code:
adb push name-of-rom.zip /sdcard/
.
Remember to put the rom into adb/fastboot folder

Hey, thank you.
I will try that soon

Hmm, trouble getting this done
I keep getting "command not found" message. Everything is in the folder.
I have done a CD to the folder etc

aussie_boi said:
Hmm, trouble getting this done
I keep getting "command not found" message. Everything is in the folder.
I have done a CD to the folder etc
Click to expand...
Click to collapse
Are you doing it while in recovery?
Try 'adb devices' and see if it sees your device
Type exactly the command you're typing to try push your ROM so we can see if you've made a slight mistake...
Sent from my HTC One using xda premium

redbull123 said:
Are you doing it while in recovery?
Try 'adb devices' and see if it sees your device
Type exactly the command you're typing to try push your ROM so we can see if you've made a slight mistake...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Okies, I have tried adb devices and it comes back with no device listing. I was in CWM Recovery mode.
This is what I typed - /Users/Greg/Downloads/Android/sdk/platform-tools/adb push AR10.1.zip /sdcard/ for the push, and
I typed this for the adb devices command - /Users/Greg/Downloads/Android/sdk/platform-tools/adb devices

aussie_boi said:
Okies, I have tried adb devices and it comes back with no device listing. I was in CWM Recovery mode.
Click to expand...
Click to collapse
What does your adb folder have in it? I use a Mac and all I have is 2 files:
adb
fastboot
Try going into fastboot it should say FASTBOOT USB then try 'fastboot devices'
Also, try a different usb port...
Sent from my HTC One using xda premium

redbull123 said:
What does your adb folder have in it? I use a Mac and all I have is 2 files:
adb
fastboot
Try going into fastboot it should say FASTBOOT USB then try 'fastboot devices'
Also, try a different usb port...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
This is the response this time - homelatform-tools Greg$ /Users/Greg/Downloads/Android/sdk/platform-tools/fastboot devices
HT34LW912007 fastboot

aussie_boi said:
This is the response this time - homelatform-tools Greg$ /Users/Greg/Downloads/Android/sdk/platform-tools/fastboot devices
HT34LW912007fastboot
Click to expand...
Click to collapse
Now try recovery again
adb devices
Sent from my HTC One using xda premium

redbull123 said:
Now try recovery again
adb devices
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It's not playing ball at all - this is the response after "adb devices"
home:Android Greg$ /Users/Greg/Downloads/Android/adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
home:Android Greg$

aussie_boi said:
It's not playing ball at all - this is the response after "adb devices"
home:Android Greg$ /Users/Greg/Downloads/Android/adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
home:Android Greg$
Click to expand...
Click to collapse
Try finding the two files I said earlier in your sdk and make a new folder just with those two files and your ROM.zip and try opening your terminal window from that new folder.
Sent from my HTC One using xda premium

redbull123 said:
Try finding the two files I said earlier in your sdk and make a new folder just with those two files and your ROM.zip and try opening your terminal window from that new folder.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Okies, I have already done that. I copied the "adb and fastboot" files from the sdk and added the "ROM.zip" file there also.
In recovery, I still get no devices listed with "adb devices"
I have opened a terminal window from within the case folder ... etc etc

I'm in the same spot and I don't have acess to a windows computer, tried doing this for almost 3 hours last night
Sent from my HTC VLE_U using xda premium

rizzxx7 said:
I'm in the same spot and I don't have acess to a windows computer, tried doing this for almost 3 hours last night
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/

I've seen this happen on my friend's HTC One a week ago. I was able to fix it by using the ALL IN ONE TOOL that was posted in this forum. I SIDELOADED a ROM, but only AFTER flashing the stock Boot.img and kernel. I dunno if this helps, but it certainly fixed the problem for me.... oh and also, I did this on a Windows 7 lappy and I'm not familiar with Macs.

MacHackz said:
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/
Click to expand...
Click to collapse
I will try this once again when I get home, I've got a nandroid file from a stock tmobile Rom that I will try to install
Sent from my HTC VLE_U using xda premium

MacHackz said:
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/
Click to expand...
Click to collapse
When I do this, I still get the error: device not found
This is what I did when in the directory using Terminal within that directory. I was in Fastboot USB for the ADB push
home:Android Greg$ ./adb push ar10.1.zip /data/media/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
And when I do Fastboot Devices and ADB Devices, I get this in Fastboot USB mode
home:Android Greg$ ./fastboot devices
HT34LW912007 fastboot
home:Android Greg$ ./adb devices
List of devices attached
home:Android Greg$
This has really got me puzzled

shinobix37 said:
I've seen this happen on my friend's HTC One a week ago. I was able to fix it by using the ALL IN ONE TOOL that was posted in this forum. I SIDELOADED a ROM, but only AFTER flashing the stock Boot.img and kernel. I dunno if this helps, but it certainly fixed the problem for me.... oh and also, I did this on a Windows 7 lappy and I'm not familiar with Macs.
Click to expand...
Click to collapse
@shinobix37
Can you give me the link for the AllInOne Tools etc and where to download the Stock Kernel etc and how you did the side load.
Seems the SDK ADB is not working for me. Fastboot obviously is. This is all really strange

aussie_boi said:
@shinobix37
Can you give me the link for the AllInOne Tools etc and where to download the Stock Kernel etc and how you did the side load.
Seems the SDK ADB is not working for me. Fastboot obviously is. This is all really strange
Click to expand...
Click to collapse
When you use the command make sure your in cwm not fastboot.
So go into cwm then use command that you said before
Sent from my HTC One using xda premium

Android The Greek said:
When you use the command make sure your in cwm not fastboot.
So go into cwm then use command that you said before
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks. I had been in CWM earlier, and the same as just now, when I try ./adb devices ... while in CWM, terminal returns no listing of devices.
It seems to me that ADB does work, as it identifies the "daemon is out of date" and restarts it successfully.
It is just that ADB does not recognise the HTC One, whilst "Fastboot devices" does, while not in fast boot usb.
I am still lost. CWM works. ADB cannot connect ...
Help

Full Panic Mode. Boot Issues + Format

Hey guys,
I done ****ed it all up.
Was in my TWRP recovery on my One, was wiping the phone to prepare for a new rom. Unfortunately, I was stupid and didn't realize that I was formatting it instead of wiping it. Now, I have a useless chunk of beautiful metal.
I can get into TWRP, but cant really do anything from there. It wont connect to my PC ( I dont see it under My Computer ) so I cant move any roms over to flash. I feel like I'm missing something very simple here.
Any ideas?

Adb sideload from recovery, advanced option.
Sent from my HTC One using Tapatalk 4

Dont panic as pablo11 have said, you can use adb sideload to sideload a rom.
Boot into twrp go to advanced, then adb sideload and swipe then on your computer open a command line where you have your folder for rooting the htc one (where fastboot is etc) and put the ROM you want to flash in that folder and type adb sideload ROM.zip and you should be good to go!

ADB Sideload
What is ADB*sideload?
ADB*sideload is a new feature that was added to AOSP*recovery in Jelly Bean.* As of version 2.3, TWRP*now supports ADB*sideload mode.* ADB*sideload is a different ADB*mode that you can use to push and install a zip using one command from your computer.* Most likely*ADB*sideload won't be very useful for your average recovery user, but ADB*sideload can be a huge time-saver for a ROM developer.
How do I*use ADB*sideload?
Have a recovery installed on your device that supports ADB*sideload like TWRP*2.3 or higher
Have newer ADB binaries installed on your computer.* If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from*the Android*SDK.* You will need version 1.0.29 or higher.* You can find your current version by typing*"adb version" at the command line.
Set the device into ADB*sideload mode. In TWRP*you do this by going to Advanced then ADB*Sideload.
From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page.* It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device.* As soon as the file is copied to your device, it will automatically be installed.* When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB*mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Sent from my HTC One using Tapatalk 4

Instructions:
http://forum.xda-developers.com/showthread.php?t=2325853&highlight=sideload

All fixed last night. Thanks guys, got my phone running again! Now to fix that radio...
Sent from my Nexus 7 using XDA Premium 4 mobile app

yasha.sinitski said:
All fixed last night. Thanks guys, got my phone running again! Now to fix that radio...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Happy to hear it and glad to help!

Windows terminal not finding adb device

I'm attempting to flash android M on my nexus 6. I've installed the proper drivers from google, after checking in device manager it says the proper drivers are installed. When I enter "adb devices" into the terminal nothing shows up in the list. I've searched through forums and tried the universal adb installer which isn't compatible with Windows8x64, so I used the 15 second installer which worked but didn't change the result. Am I doing anything wrong?
Sent from my Nexus 6 using Tapatalk

semenick96 said:
I'm attempting to flash android M on my nexus 6. I've installed the proper drivers from google, after checking in device manager it says the proper drivers are installed. When I enter "adb devices" into the terminal nothing shows up in the list. I've searched through forums and tried the universal adb installer which isn't compatible with Windows8x64, so I used the 15 second installer which worked but didn't change the result. Am I doing anything wrong?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Are you using the usb cable that came with your phone? That's the only one that will allow my PC to recognize my N6.

Yes I am
Sent from my Nexus 6 using Tapatalk

I use wug's toolkit which includes easy setup for adb and has worked with both Windows 7 and Windows 10. You might try that.
Otherwise, you didn't say whether your device is recognized by the computer when you plug it in. Windows should recognize and try to install drivers for the device automatically when plugged in via USB. If it's not, there's probably something wrong with the cord you're using. If it is recognized, then it might be the drivers of you might not have debugging enabled on your phone.
Sent from my Nexus 6 using XDA Free mobile app

The computer recognizes the phone and USB debugging is enabled
Sent from my Nexus 6 using Tapatalk

Forget about adb since you don't use it for flashing anyway. Boot into the bootloader.and type "fastboot devices". That's all that matters. Check drivers and device manager in bootloader too.
Uninstall the device if you have to and set up as per my thread.. Nexus 6 general > sticky roll-up thread > adb and fastboot.

danarama said:
Forget about adb since you don't use it for flashing anyway. Boot into the bootloader.and type "fastboot devices". That's all that matters. Check drivers and device manager in bootloader too.
Uninstall the device if you have to and set up as per my thread.. Nexus 6 general > sticky roll-up thread > adb and fastboot.
Click to expand...
Click to collapse
I followed your guide and restarted my windows 8 computer accordingly. When I open the command window and type "fastboot devices" it says that is not recognized as an internal or external command, operable program or batch file
Sent from my Nexus 6 using Tapatalk

semenick96 said:
I followed your guide and restarted my windows 8 computer accordingly. When I open the command window and type "fastboot devices" it says that is not recognized as an internal or external command, operable program or batch file
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That means you didn't do the environment variables correctly or it didn't take after the reboot.
Confirm the location you have fastboot in is the location in environment variables.

danarama said:
That means you didn't do the environment variables correctly or it didn't take after the reboot.
Confirm the location you have fastboot in is the location in environment variables.
Click to expand...
Click to collapse
How do I check the location of fastboot?
Sent from my Nexus 6 using Tapatalk

semenick96 said:
How do I check the location of fastboot?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
What part of my thread did you follow? How did you put fastboot on your.computer?

danarama said:
What part of my thread did you follow? How did you put fastboot on your.computer?
Click to expand...
Click to collapse
Is that the platform-tools? I'm sorry if these are stupid questions! I'm still learning aha
Sent from my Nexus 6 using Tapatalk

semenick96 said:
Is that the platform-tools? I'm sorry if these are stupid questions! I'm still learning aha
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, if you followed my thread and installed the sdk, the fastboot.exe should be in there. The full path is mentioned in my thread. Go.and check that and if it is, go onto the next step about environment variables.. Remember, the variable must be the location of fastboot and MUST start with ;
To be honest, I cheat and simply drop adb and fastboot into c:\windows\system32 as that is already and environment variable.

danarama said:
Yes, if you followed my thread and installed the sdk, the fastboot.exe should be in there. The full path is mentioned in my thread. Go.and check that and if it is, go onto the next step about environment variables.. Remember, the variable must be the location of fastboot and MUST start with ;
To be honest, I cheat and simply drop adb and fastboot into c:\windows\system32 as that is already and environment variable.
Click to expand...
Click to collapse
I redid all of the steps, but my computer is taking a long time to do the restart. Is that normal?
Sent from my Nexus 6 using Tapatalk

semenick96 said:
I redid all of the steps, but my computer is taking a long time to do the restart. Is that normal?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No.

danarama said:
No.
Click to expand...
Click to collapse
Alright, I'll look into it. Thanks for all the help!
Sent from my Nexus 6 using Tapatalk

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