Hello everyone!
Straight to the point.
How to pull OTA links on any Android version. via ADB on PC. [No Root necessary]
This works on any Android version without root.
[NOTE: if you are on Android 4.2.2 and PC can't see file like on NEXUS Devices with 4.2.2 do this: open file explorer on device and look for logcat.txt and compress it to a .zip file. That way PC will see it and you will be able to pass it to PC and open it to search for the link inside logcat.txt.]
What you need:
ADB Tools Files [Download Here] Thanks Garwynn
Samsung Drivers [Download Here] Thanks Rwilco12
Patience and brain matter.
Instructions and Tips:
1. Setting up ADB Tools on Windows 7/8 environment variable:
A. Extract ADB Tools folder to "C:\"
B. Click "Start", right click on "Computer" and select "Properties" in the right pane select "Advance System Settings" then "System Properties" will open, select the "Advance" tab if its not selected by default and click on "Environment Variables".
Under "System variables" look for "Path" on the list, select it and click on "Edit..." then on "variable value:" (be careful not to delete anything there) look for the end and add the patch where you extracted the "ADB Tools" folder, if you extracted to "C:\" then the path should be: ";C:\ADB-Tools\" without colons of course. click OK then OK and OK again. Now the Environment Variable for the ADB Tools is added to system.
To test it open CMD and type: "adb devices", it should show your device ID if its connected via USB, if not it show the strings "daemon not running. blah blah starting it now on port xxxx" and "daemon started blah blah" and list of devices attached empty. (Congrats you set ADB successfully).
2. Install Samsung Drivers.
3. Enable Developer options and USB debugging on device.
4. Plug device via USB to PC (if windows start installing drivers wait for it to finish) and open CMD and type the following ADB commands to create the logcat.txt file on internal sdcard.
Code:
adb devices
Code:
adb logcat -d -f /sdcard/logcat.txt *:V
5. Exit CMD and unplug and plug device again to be able to see logcat.txt on sdcard. Move to PC and search for link inside logcat.txt. Profit.
Tip: to find the link faster open it on notepad press crtl+F and search for http: until you find something like this "http://android.clients.google.com/packages/ota/xxxx.zip"
Thanks:
sextape
MoHoGalore
Garwynn
Rwilco12
Team SXTP
and all XDA Members.
Reserved for later.
Sent from my SPH-L710 using Tapatalk 2
Thanks for the write up, Omar! Hopefully the community will have plenty of opportunities to use your guide.. (who doesn't love trying to get and try/look at an update as soon as possible) :beer:
:beer:
Sent from my SPH-L710 using Tapatalk 2
Hmm :beer:
Sent from my SPH-L710 using Tapatalk 2
Apparently, the log gets cleaned up or cleared at some point because there is no line containing "http", "ota", or even "zip" in my log. It was 5 or 6 days ago when my phone re-downloaded the OTA, so if you are going to do this, you best do this not too long after the update notification.
~Zach~ said:
Apparently, the log gets cleaned up or cleared at some point because there is no line containing "http", "ota", or even "zip" in my log. It was 5 or 6 days ago when my phone re-downloaded the OTA, so if you are going to do this, you best do this not too long after the update notification.
Click to expand...
Click to collapse
no matter if it finish the download or not links are there until you reboot, you need to open the file in the PC, if you open it on the device it will not show the full log.
Edit: also read the blue note in the start of the post.
Oh, I was looking at the log on my PC.
Anyway, your "until you reboot" is the operative phrase here, I think.
shameless bump. :silly:
Hello Android 4.3
Sent from my SPH-L710 using Tapatalk HD
Team SXTP
Bump
Sent from my SPH-L710 using Tapatalk 4
Team SXTP
Omar04 said:
Hello Android 4.3
Sent from my SPH-L710 using Tapatalk HD
Team SXTP
Click to expand...
Click to collapse
Are we getting the update or something or is there a specific reason for the timing on this topic my friend. .
Sent from my SPH-L720 using XDA Premium 4 mobile app
Related
Ok so Ive seen a few people posting in the dev section that they cant get adb working. So heres a quick write up on how to get it working on windows and linux (ubuntu) machines. Follow these directions and you should have no problems. If you notice any errors dont hesitate to point them out to me! This is meant to help, not confuse.
First you need to download ADB.
Click here and select the download appropriate for your operating system: Android SDK
For Windows:
1.Extract the .zip file you downloaded and make a note of where you extracted to.
2.Go into the extracted android-sdk_r12-windows folder.
(if you go into this folder and have another folder named 'android-sdk_r12-windows' then cut and paste it outside of the extracted folder)
3.Open SDK Manager. Let it do its thing and then make sure 'Select All' is checked and click 'Install'
4.When its done it will say ADB has been updated and needs to restart. Select OK.
5.Now go back to your android-sdk_r12-windows folder and you should have a new folder called 'platform-tools'
6.Go into that folder and you should see 'adb'
7.Now to make things easy you're going to create an adb shortcut:
Right click your desktop and choose to create a new shortcut.
It will ask you to type a location for the shortcut. Enter "CMD" without the "".
Click 'Next'
For the name type "ADB" without the "".
Now right click the shortcut you just created and select 'Properties'
Now in the Properties dialog where it says Start In, type the path to your Android SDK foler. In my case I extracted the folder to my desktop, so my path would be C:\Users\Jason\Desktop\android-sdk_r12-windows.
Then click 'OK'
Now all you have to do is click this shortcut and you're automatically in adb in the command prompt.
For Linux:
Everything above is going to be pretty much the same except for the way you get into adb.
So do steps 1-6 above.
Now, instead of a shortcut you're going to open terminal and type the following:
sudo cp <path to your sdk platform-tools folder> /usr/bin
(for <path to your sdk platform-tools folder> it will depend on where you extracted the .zip to. In my case it would look like this because I extracted it to my desktop on MY computer:
sudo cp /home/jason/Desktop/android-sdk-linux_x86/platform-tools/adb /usr/bin
now you can access adb directly from Terminal.
Now I dont own a Mac so Im not going to put a writeup for that. But someone can feel free to post one and I can add it to my original post.
Thats it you now have access to adb on your computer! Go flash alternate recoveries and roms and be merry in 3D!
I am on my mobile app right now and haven't been able to find the link yet in the development section, but can pretty much guarantee that most ppl are having the issue I had with error messages about being denied BC u don't have permission. You have to change the permissions to get read and write access. If someone with better knowledge than me knows about it, then please feel free to elaborate. I spent hours trying to find answers before I stumbled across how to fix permissions. I know it requires u to enter adb shell and the into su to enter the code to change permissions so u can use adb push as well as adb root, etc. If no one addresses this shortly then I will find the link on my laptop and update.
Sent from my LG-P925 using xda premium
http://forum.xda-developers.com/showthread.php?t=1259603
Sent from my LG-P925 using xda premium
Holy cow! I have a new found respect for developers. I wanted the adb tools just so I can flash CWM recovery. Now I'm having to download updated java and there's a ton of stuff to download for the SDK tools.
I'll have to admit that I loved my Captivate in how easy it was to flash CWM and roms and really anything else.
how can i do this if my phone is bricked stuck on lg logo
I got a new replacement phone. I rooted the phone. I started the RevoToolKit app to install ClockWorkMod. I did get a message saying something about md5sum did not match. I install Clockworkmod on my own and booted into recovery from CMW. When it rebooted I got a blackscreen with this:
[470] Fastboot mode started
[520] USB init ept @0x3e000
[620] smem_read_alloc_entry Type: 402
[670] smem_read_alloc_entry Size Read 1816
[720] smem_read_alloc_entry Size Passed 1816
[780] smem ram ptable found: ver :0 len 6
[830] fastboot_init()
[890] Fastboot maximum download size : 450 Mbytes
[950] udc_start()
[1010] --suspend--
[1040] --reset--
[1040] --portchange--
[1050] --reset--
[1050] --portchange--
[1060] fastboot: processing commands
Anyway this is where I am stuck at. I know I screwed something up and I just to get back to using the phone
So far the phone is not being recognized by my computer or others, LGNPST is not working and I don't know anything when it comes to android SDK or how to do commands. Any advice will help. Honestly, I'm about to drop the phone in the toilet.
Thanks
have you tried following this?
http://forum.xda-developers.com/showthread.php?t=1131671
antiwesley said:
have you tried following this?
http://forum.xda-developers.com/showthread.php?t=1131671
Click to expand...
Click to collapse
I attempted to try it but I don't know where to enter the codes or how to enter the codes. I dont even have an SDK set up. It is way to technical for me. I want to send it to somebody to do it for me.
I have insurance maybe i'll drop it the toilet.
satsgt said:
I have insurance maybe i'll drop it the toilet.
Click to expand...
Click to collapse
Insurance doesn't cover water damage.
The only thing I can recommend is to come onto the irc tonight and there may be someone who can help.
Sent from my VS910 4G using xda premium
mtmichaelson said:
Insurance doesn't cover water damage.
The only thing I can recommend is to come onto the irc tonight and there may be someone who can help.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
What is the irc? Im in san antonio, tx.
Just search lg revolution irc. It is a chat room.
Sent from my VS910 4G using xda premium
I dont know mt texas is kind of far away from IRC. lol jk
you can search freenode irc
click channel
enter your nickname(whatever you want it to be)
enter #Lgrevolution into the channel field
enter that weird text thing.
Beamer9408 said:
I dont know mt texas is kind of far away from IRC. lol jk
you can search freenode irc
click channel
enter your nickname(whatever you want it to be)
enter #Lgrevolution into the channel field
enter that weird text thing.
Click to expand...
Click to collapse
My bad im a fresh face nubie at this stuff. thanks for the info.
No problem I was joking.
Sent from my VS910 4G using xda premium
Beamer9408 said:
No problem I was joking.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
any ideas?
mtmichaelson said:
Just search lg revolution irc. It is a chat room.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
so far nobody is chatting
satsgt said:
so far nobody is chatting
Click to expand...
Click to collapse
I said tonight. During the day it is pretty dead.
Sent from my VS910 4G using xda premium
Its not hard to fix at all, you will have to install the Java JDK, Android SDK, and three files AdbWinApi.dll, fastboot.exe, and CWMrecoveryrevolution.img which is the clockwork recovery for our phone.
Here are the files in .rar format.
http://www.mediafire.com/?eb3219cy0lbc71m
Android SDK
Java JDK
The first version should work
1. Install the Android SDK to your C: drive. Make sure the SDK and all the files are in C:\androidSDK. This will make things easier later.
2. Open the SDK and install the additional AndroidSDK platform tools package
3. Install the Java JDK
4. Unzip the .rar to c:/androidSDK/tools
5. Open command prompt, start> type "cmd"> press enter
6. Plug in phone
6. Assuming you placed everything in the right folders, type the following into the command prompt
Code:
cd c:/androidSDK/tools
7. You should now be in the correct folder, paste this command next:
Code:
fastboot erase recovery
then:
Code:
fastboot flash recovery CWMrecoveryrevolution.img
If that succeeds then type the final command:
Code:
fastboot reboot
Hopefully this works and is understandable
adrenaline_rush said:
Its not hard to fix at all, you will have to install the Java JDK, Android SDK, and three files AdbWinApi.dll, fastboot.exe, and CWMrecoveryrevolution.img which is the clockwork recovery for our phone.
Here are the files in .rar format.
http://www.mediafire.com/?eb3219cy0lbc71m
Android SDK
Java JDK
The first version should work
1. Install the Android SDK to your C: drive. Make sure the SDK and all the files are in C:\androidSDK. This will make things easier later.
2. Open the SDK and install the additional AndroidSDK platform tools package
3. Install the Java JDK
4. Unzip the .rar to c:/androidSDK/tools
5. Open command prompt, start> type "cmd"> press enter
6. Plug in phone
6. Assuming you placed everything in the right folders, type the following into the command prompt
Code:
cd c:/androidSDK/tools
7. You should now be in the correct folder, paste this command next:
Code:
fastboot erase recovery
then:
Code:
fastboot flash recovery CWMrecoveryrevolution.img
If that succeeds then type the final command:
Code:
fastboot reboot
Hopefully this works and is understandable
Click to expand...
Click to collapse
Thank you for all you help. it worked!!! My Revo is working again!!
Any chance of an update on this?! I'm stuck.
I am having this same problem and I tried to follow these steps, but the mediafire link is broken. I downloaded another recovery file and followed the rest of the steps, but it didn't work. I'm still stuck at the fastboot page. I have an LG Optimus V. I would appreciate any help you can give.
adrenaline_rush said:
Its not hard to fix at all, you will have to install the Java JDK, Android SDK, and three files AdbWinApi.dll, fastboot.exe, and CWMrecoveryrevolution.img which is the clockwork recovery for our phone.
Here are the files in .rar format.
The first version should work
1. Install the Android SDK to your C: drive. Make sure the SDK and all the files are in C:\androidSDK. This will make things easier later.
2. Open the SDK and install the additional AndroidSDK platform tools package
3. Install the Java JDK
4. Unzip the .rar to c:/androidSDK/tools
5. Open command prompt, start> type "cmd"> press enter
6. Plug in phone
6. Assuming you placed everything in the right folders, type the following into the command prompt
Code:
cd c:/androidSDK/tools
7. You should now be in the correct folder, paste this command next:
Code:
fastboot erase recovery
then:
Code:
fastboot flash recovery CWMrecoveryrevolution.img
If that succeeds then type the final command:
Code:
fastboot reboot
Hopefully this works and is understandable
Click to expand...
Click to collapse
Wow this was a while ago, not sure why the links broke, also don't have those files stored anymore. I noticed you have an Optimus V. Try to find an appropriate recovery.img file for that phone and flash it through ADB similar to the steps above.
I saw a lot of threads asking for instructions on how to use ADB to reboot into recovery, Push/Pull Files, etc, etc.
Just follow this guide to set up ADB in 5 seconds WITHOUT THE ANDROID SDK.
This ADB setup is less than one MB and no need to download the entire useless (for us, anyway) Android SDK.
1. Extract the Mini ADB archive attached below to any folder.
2. Just use the RunME.bat file to open a console directly in the ADB folder, so you can get started directly without the cd command!
To reboot into recovery:
Extract, Open RunMe.bat, type adb reboot recovery.
That easy.
Just make sure to have LG Phone Drivers installed beforehand.
Get Drivers here: Here
thanks mate ,, i never used adb when i get bootloops ,, i thought its complicated
rrgrrg said:
thanks mate ,, i never used adb when i get bootloops ,, i thought its complicated
Click to expand...
Click to collapse
Now you see how easy it is! Did you try it?
Its Super simple!
Does it work on any Android?
cm9 htc a310e
Yes.. It works when debugging is On.....
But how to get into recovery when we have bootloops or system force close
Type adb reboot recovery... it's in the op...
Sent from my LG-P970 using xda app-developers app
When you have bootloops:
Remove battery.
Re insert.
Connect phone to computer using USB.
Try to turn on phone, when bootanimation keeps looping,
run the runme.bat, type adb reboot recovery.
Done
And remember to press thanks
Sent from my LG-P970 using Tapatalk 2
thanks ykumar00 :good:
You can use adb also to install applications from your pc. I keep copies of my apks on windows machine - sending via usb and installing from phone is a tedious task (mounting usb, copying file, unmounting, waiting for sdcard scanning, navigating to apk file, installing). Just type:
adb install -r name.apk
USB debugging should be on.
I've created a batch and registry entry so I just make right click on apk and choose "install to sd" or "install to phone"
kretos said:
You can use adb also to install applications from your pc. I keep copies of my apks on windows machine - sending via usb and installing from phone is a tedious task (mounting usb, copying file, unmounting, waiting for sdcard scanning, navigating to apk file, installing). Just type:
adb install -r name.apk
USB debugging should be on.
I've created a batch and registry entry so I just make right click on apk and choose "install to sd" or "install to phone"
Click to expand...
Click to collapse
That's just one thing adb can do! Apart from reebooting normally and recovery, You can push/pull files to/from any folder, you can take logcats, and on ics, you can use adb to even take phone backups!
Also, could you share the bat and registry file? Looks interesting.
Sure, I'll post it here in the evening (in 4 hours)
Yup it would be really very useful and if someone has something to share related to adb please do so... it would be really very usefull for all ob users.
Sent from my LG-P970 using xda app-developers app
I could add it to the OP. With credits of course....
Ok, here you go:
the scripts assume that adb.exe is extracted to e:\MiniADB\
download attachments and remove .txt extension from them.
put scripts install.bat and install_tel.bat to e:\MiniADB and run (double click and confirm in Vista/W7/W8 to run as administrator) apk_install.reg.
After that you will get two options in context menu for apk files:
Install in phone
Install in SD card
First option will install application in phone's memory, second in sd card. If application is already installed, it will be overwritten.
If you wish to put MiniADB somewhere else you have to:
modify install.bat and install_tel.bat and replace e:\MiniADB\ with your path
modify apk_install.reg and replace e:\\MiniADB\\ with your path but remember to make all \ doubled \\
Example:
if you want to put MiniADB into c:\Android\MiniADB then replace e:\\MiniADB\\ with c:\\Android\\MiniADB\\ in a .reg file
Those scripts are for Windows only. I'm not sure if it works for Windows NT/9x as registry file format was changed as I remember.
Edit:
USB debugging must be on in a phone to adb work properly. Phone must be connected to computer
Sorry for delay
When trying adb, I am having this problem.
Sent from my LG-P970 using xda premium
vishaldhamnekar said:
When trying adb, I am having this problem.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
the command is "adb reboot recovery".
dcop7 said:
the command is "adb reboot recovery".
Click to expand...
Click to collapse
Ohhh sorry,my mistake. I didn't read it carefully.
And Thanks...
I had mutiple issues getting adb to work in adb sideload. It worked while in the OS but not in recovery after selecting sideload. This is how I fixed it!
You must first have SDK installed and know the basics of adb and fastboot. If you do not know how to install SDK or how to use terminal emulator or command prompt (cmd) to get to the platform tools folder you must do all that first. You must also have developers tools and USB debugging on.
See here if you have no idea what I am talking about: http://forum.xda-developers.com/showthread.php?t=2141817
Go to stock recovery and click adb sidload
In Win7 go to:
1. Go to Start
2. Right Click Computer
3. Click Manage
4. Click Device manager
5. You will see the nexus 5 with a yellow !
6. Right Click on nexus 5 and click update driver
7. then choose to browse for driver
Windows 8? See here:
gaga111 said:
http://www.theandroidsoul.com/nexus-5-driver-adb-fastboot-installation-guide/
this helped me
i used the naked driver and disabled the driver signature enforcement (only for windows 8 and 8.1)
Click to expand...
Click to collapse
8. then choose the second option search for driver by device
zallaaa said:
I believe that's the same "wall" I've found.
Select "Android Phone" and next, then you'll find a list of all the compatible "Android ADB Interfaces". I used "Android ADB Interface ver. 8.0.0.0" and it worked, thank The Greek!
Click to expand...
Click to collapse
9. click on Android ADB Interface
10. Should install driver succesfully.... check adb devices it will show device id in sideload mode
Hope this helps the people who can't function without an ota
Hit thanks if this helped:thumbup:
Step 8.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
I had mutiple issues getting adb to work in adb sideload. It worked while in the OS but not in recovery after selecting sideload. This is how I fixed it!
Go to stock recovery and click adb sidload
In Win7 go to:
1. Go to Start
2. Right Click Computer
3. Click Manage
4. Click Device manager
5. You will see the nexus 5 with a yellow !
6. Right Click on nexus 5 and click update driver
7. then choose to browse for driver
8. then choose the second option search for driver by device
9. click on Android ADB Interface
10. Should install driver succesfully.... check adb devices it will show device id in sideload mode
If someone can add screen shots of their computer while following these steps it would be helpful. I can't seem to replicate the issue now that its working on my PC
Click to expand...
Click to collapse
When i click step 8, no option for Android ADB Interface is on the list?
Can you post a screen shot of what the options are?
In the os not recovery does you device show up in adb?
Sent from my Nexus 5 using XDA Premium 4 mobile app
jonyid said:
When i click step 8, no option for Android ADB Interface is on the list?
Click to expand...
Click to collapse
I believe that's the same "wall" I've found.
Select "Android Phone" and next, then you'll find a list of all the compatible "Android ADB Interfaces". I used "Android ADB Interface ver. 8.0.0.0" and it worked, thank The Greek!
Android The Greek said:
Can you post a screen shot of what the options are?
In the os not recovery does you device show up in adb?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
when not in recovery yes it appears in adb and android device appears. When i got through the process of updating the OTA i get up to:
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
and then it appears device not found
jonyid said:
when not in recovery yes it appears in adb and android device appears. When i got through the process of updating the OTA i get up to:
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
and then it appears device not found
Click to expand...
Click to collapse
When device is in adb sideload type in you command prompt adb devices. Do you see anything? Try Ctrl alt delete kill adb.exe in process the retry if adb sees the device I'd in adb side load mode then your good. If not you need to get the drivers to work by following step 8. If you do not see that option add a screen shot of your options.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
When device is in adb sideload type in you command prompt adb devices. Do you see anything? Try Ctrl alt delete kill adb.exe in process the retry if adb sees the device I'd in adb side load mode then your good. If not you need to get the drivers to work by following step 8. If you do not see that option add a screen shot of your options.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm now getting the error message (i uninstalled and re-installed the drivers) "adb cannot run as root in production builds" at stage 3:
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
http://www.theandroidsoul.com/nexus-5-driver-adb-fastboot-installation-guide/
this helped me
i used the naked driver and disabled the driver signature enforcement (only for windows 8 and 8.1)
jonyid said:
I'm now getting the error message (i uninstalled and re-installed the drivers) "adb cannot run as root in production builds" at stage 3:
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
Click to expand...
Click to collapse
Are you stock? Why are you using adb recovery? If adb works in the os but when you manually boot into recovery mode adb sideload and it says failed to install the drivers my method will work.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
Are you stock? Why are you using adb recovery? If adb works in the os but when you manually boot into recovery mode adb sideload and it says failed to install the drivers my method will work.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm 100% stock. This is the guide i was advised to use:
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. Its attached at the bottom
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press power then immediately press volume up and release. The menu will appear. Select “apply update from adb”
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
I've installed the google drivers and when plugged in it recognises both the phone (no yellow ! there) and also an 'android device - android composite ADB interface" option. Both say that the drivers are up-to-date.
jonyid said:
I'm 100% stock. This is the guide i was advised to use:
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. Its attached at the bottom
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press power then immediately press volume up and release. The menu will appear. Select “apply update from adb”
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
I've installed the google drivers and when plugged in it recognises both the phone (no yellow ! there) and also an 'android device - android composite ADB interface" option. Both say that the drivers are up-to-date.
Click to expand...
Click to collapse
In recovery adb sideload do a adb devices in command prompt. What does it say
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
In recovery adb sideload do a adb devices in command prompt. What does it say
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you mean at stage 3? it says:
List of devices attached
03b911s908eb03ff device
jonyid said:
you mean at stage 3? it says:
List of devices attached
03b911s908eb03ff device
Click to expand...
Click to collapse
Why not manually put your device in adb sideload
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
Why not manually put your device in adb sideload
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do i do this? Will it then allow me to install pretty quickly?
jonyid said:
How do i do this? Will it then allow me to install pretty quickly?
Click to expand...
Click to collapse
Pm me your number
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
Pm me your number
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i'm in the UK that's the problem
I had to follow the instructions that were listed here to get my laptop to see my N5 in recovery mode. Worked like a charm afterward.
http://stackoverflow.com/questions/15721778/adb-no-devices-found
Sephiroth_Darko said:
I had to follow the instructions that were listed here to get my laptop to see my N5 in recovery mode. Worked like a charm afterward.
http://stackoverflow.com/questions/15721778/adb-no-devices-found
Click to expand...
Click to collapse
I'm on my work PC and not 100% about doing this
jonyid said:
I'm on my work PC and not 100% about doing this
Click to expand...
Click to collapse
I did it on my home laptop it and it worked fine. But I understand how you could be a bit hesitate to do this on a work machine. Best of luck!
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