SOLVED- SEE POST #6
Please forgive me if this has been answered- but I have searched through all the posts here on the LG G3 and ADB and can not find a solution.
I have got this far following the guide on ADB Mac- but as you can see from the pic is says that my phone is offline. Changed the MTP to Ethernet to modem- and nada. Is this a facepalm and I am missing something here? many thanks in advance.
rwcasto said:
Please forgive me if this has been answered- but I have searched through all the posts here on the LG G3 and ADB and can not find a solution.
I have got this far following the guide on ADB Mac- but as you can see from the pic is says that my phone is offline. Changed the MTP to Ethernet to modem- and nada. Is this a facepalm and I am missing something here? many thanks in advance.
Click to expand...
Click to collapse
If you look closely, you can tell that the problem is that your not using a pc.
Chilidog said:
If you look closely, you can tell that the problem is that your not using a pc.
Click to expand...
Click to collapse
ahhh... thanks.. I think
Chilidog said:
If you look closely, you can tell that the problem is that your not using a pc.
Click to expand...
Click to collapse
Not even close.
Using ADB on my Mac, is a non issue.
OP make sure you are running the latest version of ADB.
A security feature was added to Android and it will ask you if you want to have that computer authenticated or some such.
If your phone didn't ask you probably have an old version of ADB.
tech_head said:
Not even close.
Using ADB on my Mac, is a non issue.
OP make sure you are running the latest version of ADB.
A security feature was added to Android and it will ask you if you want to have that computer authenticated or some such.
If your phone didn't ask you probably have an old version of ADB.
Click to expand...
Click to collapse
Right on! Thanks man! updating right now!
ADB Working Mac!
follow the guide here http://forum.xda-developers.com/showthread.php?t=1917237
with one addendum- use the attached zip file with latest ADB/Fastboot files and you now have a working solution for ADB on MAC
rwcasto said:
follow the guide here http://forum.xda-developers.com/showthread.php?t=1917237
with one addendum- use the attached zip file with latest ADB/Fastboot files and you now have a working solution for ADB on MAC
Click to expand...
Click to collapse
Glad you got it working.
If I helped don't forget the thanks button.
tech_head said:
Glad you got it working.
If I helped don't forget the thanks button.
Click to expand...
Click to collapse
Humm. Using a Mac with 10.10 Yosemite, I have a D850 on LP 5.01 and have followed the lead in the link given above, and used the dab and fast boot file in the zip just above. My Oneplus's in the house (3), work great. My G3, with new drivers, seen but "offline". It does have USB debugging selected. I have tried toggling that, using the MTP or PTP choices, and both get the same result. I have installed the newest android SDK as well.
frustrating. Any thought would be appreciated.
Solved the issue by uploading another newest ADB file set. G3 is not ween, however, when I run the command "su
restorecon -FR /data/media/0/", adb tells me "command not found"
I do have the newest Android SDK 23.02 tools installed.
Related
I'm sorry if there is something already posted here somewhere about the rezound, but I haven't seen anything...yet...lol.
I've been trying to root my rezound ALL DAY and can't seem to figure anything out apparently.
If someone could help me out with sending me a link to the best way of unlocking bootloader and then rooting my phone. I had a dinc2 previously and that was not as hard to root compared to the rezound IMO. So please, if someone can take the time for me and help me out with getting my phone unlocked and rooted I would greatly appreciate it a TON!!!
Try this out http://forum.xda-developers.com/showthread.php?t=1648578
http://bit.ly/N3cfpa
hey guys thanks for replying back....I'm still getting no luck whatsoever with unlocking the bootloader.....I'm doing everything (or so I think I am) right with the steps on htcdev.com and when I get to the command prompt and type in fastboot oem get_identifier_token...this is what comes up
'fastboot' is not recognized as an internal or external command,
operable program or batch file.....now I have NO CLUE what the heck to do!! I'm getting pissed off lol. I could really use some help here. thanks
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
EmerikL said:
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
npainter7 said:
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
Click to expand...
Click to collapse
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
kzoodroid said:
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
Click to expand...
Click to collapse
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Fastbird said:
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Click to expand...
Click to collapse
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
npainter7 said:
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Click to expand...
Click to collapse
After you install Android SDK the directions on the HTCdev site tell you to run sdk manager and download the Android SDK Tools and Android SDK Platfrom-tools. What I did was to take this a step further and also install the Google USB Driver which is listed in ADB Manager under Extras and also the API's for GB and ICS. The API's really aren't necessary but I don't think ADB will recognize the phone without the Google USB Drivers.
npainter7 said:
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
Click to expand...
Click to collapse
This may not work for you, but one time my drivers weren't working because I plugged my phone into a USB 3.0 port, so when I used a USB 2.0 port, it worked fine.
I have tried recently to root my DNA running 3.06 and 4.2.2 with rumrunner. My phone gets to the bootloader screen from the rumrunner program, and then on the first step the program says waiting for fastboot but my phone just sits there. It isn't frozen and I can move it around but it doesn't do anything automatically like I know it should. Not sure if it maybe has something do do with ADB or anything along those lines. If anyone has any idea I could really use some help. This is my first android phone and my first root attempt. Thanks.
Mr.Schneider said:
I have tried recently to root my DNA running 3.06 and 4.2.2 with rumrunner. My phone gets to the bootloader screen from the rumrunner program, and then on the first step the program says waiting for fastboot but my phone just sits there. It isn't frozen and I can move it around but it doesn't do anything automatically like I know it should. Not sure if it maybe has something do do with ADB or anything along those lines. If anyone has any idea I could really use some help. This is my first android phone and my first root attempt. Thanks.
Click to expand...
Click to collapse
Sounds like a problem with ADB and or Fastboot.
Fix those and you should be fine.
sdamark said:
Sounds like a problem with ADB and or Fastboot.
Fix those and you should be fine.
Click to expand...
Click to collapse
I believe I fixed my adb, put it in my directory and the path settings. Everything still isn't working. I know fastboot is set up correctly because i can type it in the cmd line and all the info comes up, I'm just lost. Not sure if you know what to do from here.
Mr.Schneider said:
I believe I fixed my adb, put it in my directory and the path settings. Everything still isn't working. I know fastboot is set up correctly because i can type it in the cmd line and all the info comes up, I'm just lost. Not sure if you know what to do from here.
Click to expand...
Click to collapse
In a command prompt, type "adb devices'
response should be device serial # "[FA2CXXXX blah blah] device"
Next in a command prompt, type "adb reboot bootloader"
device should boot into bootloader Fastboot USB
Then type "fastboot devices"
response should be device serial # "[FA2CXXXX blah blah] fastboot"
Then type "fastboot reboot"
Device should reboot into android.
If all this works, then ADB and Fastboot are working. :good:
How is Rumrunner failing? Can you post a screenshot of your computer? Need more info to help.
I had a similar issue, but on step 2. Confirm before any reboots that both adb and fastboot work. If so, run the exe. If they stop working during the program running it could be usb cord or port
I am doing it on my windows 7 computer and everything is working perfectly so far. Thanks for all the help and ill post again if I run into more troubles. While Your'e here, does anyone know the commands to flash a custom recovery onto the devise after I have S-Off?
Thanks for all the help guys! It worked perfectly. Now all I have to do is install some roms and see what else I can do.
Sent from my HTC DROID DNA
Mr.Schneider said:
Thanks for all the help guys! It worked perfectly. Now all I have to do is install some roms and see what else I can do.
Sent from my HTC DROID DNA
Click to expand...
Click to collapse
Do you know how to do that or do you need help?
thayl0 said:
Do you know how to do that or do you need help?
Click to expand...
Click to collapse
I installed cyogen mod, but I'm having an issue wjere y data is being weird and I cannot send text messages. Anyone know any smooth running ROMs I could try? Preferably ones that look similar to stock android and not sense.
Mr.Schneider said:
I installed cyogen mod, but I'm having an issue wjere y data is being weird and I cannot send text messages. Anyone know any smooth running ROMs I could try? Preferably ones that look similar to stock android and not sense.
Click to expand...
Click to collapse
Cm is stable. So that could be another problem we have here
thayl0 said:
Cm is stable. So that could be another problem we have here
Click to expand...
Click to collapse
Would you Happen to have a link to the stable release you know of? Just to be sure I have an updated one? I'll attach a picture.
Mr.Schneider said:
Would you Happen to have a link to the stable release you know of? Just to be sure I have an updated one? I'll attach a picture.
Click to expand...
Click to collapse
You have the latest version for 10.2
ViperDNA is pretty much a stock Sense 5.0 JellyBean 4.2.2 ROM, with a million little things you can tweak on with Venom Tweaks and Venom Hub.
Find download here http://forum.xda-developers.com/showthread.php?t=2475739
This one is Sense 5.5 based, KitKat 4.4.2, pretty much 100% stock from the HTC One.
Find download here http://forum.xda-developers.com/showthread.php?p=50142710
Both are awesome.
Really glad you figured out how to S-Off. :good:
Welcome to the community.
Updated to a 11c ROM and cannot adb anymore. I have tried removing all drivers and installing different drivers to no avail. When I do adb devices, nothing is listed. What am I missing? It is in debug mode.
droidkevlar said:
Updated to a 11c ROM and cannot adb anymore. I have tried removing all drivers and installing different drivers to no avail. When I do adb devices, nothing is listed. What am I missing? It is in debug mode.
Click to expand...
Click to collapse
http://forum.xda-developers.com/verizon-lg-g3/general/usb-debugging-update-kvt49l-vs98511c-t2930817
bweN diorD said:
http://forum.xda-developers.com/verizon-lg-g3/general/usb-debugging-update-kvt49l-vs98511c-t2930817
Click to expand...
Click to collapse
Thanks man!
In case anyone else has this issue, this is the link I used and works.
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427
droidkevlar said:
Thanks man!
In case anyone else has this issue, this is the link I used and works.
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427
Click to expand...
Click to collapse
thanks, worked great
So, my fire HD has the Android composite ADB interface as the driver.. I can find the tablet on prompt ADB devices but when I put the device into adb reboot recovery I lose it.. The cme can't see the tablet anymore, any thoughts on a solution? Windows 8 x64
Thanks very much
Are you saying "adb reboot recovery" doesn't boot you into recovery or that once in recovery adb commands don't work. If you're booting into stock recovery, that seems to be how it works.
If you can't get into recovery with the generic drivers, I swear by Google Galaxy Nexus from Koush's Universal Android package. Someone recommended the HTC dream driver.
EDIT: I see the prob. Wouldn't be able to issue "adb sideload" would you? Sorry, not much help.
---------- Post added at 10:25 PM ---------- Previous post was at 10:06 PM ----------
Well, this is good to know at this thread too!
limitedxj said:
I fixed my own problem, when in recovery the tablet was acting like a new tablet, wondered if that was true so i checked the managed devices, sure enough, the fire had a new name, added the Adb composite to the new name, boom..
Click to expand...
Click to collapse
Correction
Thanks for pasting that, I originally posted it in the specific thread I was trying to duplicate then realized it was a driver issue and more Q/A related. The fix for my problem was checking the driver setting at each step of Adb on 1st initation. Simple fix but threw me off a bit..
Thanks for the quick reply
So I'm seeing this exact issue. (As you said in other thread, adb devices returns device id, then in recovery it doesn't.) Can you clarify "first initiation"? I've had these drivers installed for months. You just updated, checking driver setting in device mgr? thx
limitedxj said:
The fix for my problem was checking the driver setting at each step of Adb on 1st initation.
Click to expand...
Click to collapse
DoLooper said:
So I'm seeing this exact issue. (As you said in other thread, adb devices returns device id, then in recovery it doesn't.) Can you clarify "first initiation"? I've had these drivers installed for months. You just updated, checking driver setting in device mgr? thx
Click to expand...
Click to collapse
limitedxj said:
Thanks for pasting that, I originally posted it in the specific thread I was trying to duplicate then realized it was a driver issue and more Q/A related. The fix for my problem was checking the driver setting at each step of Adb on 1st initation. Simple fix but threw me off a bit..
Thanks for the quick reply
Click to expand...
Click to collapse
DoLooper said:
Are you saying "adb reboot recovery" doesn't boot you into recovery or that once in recovery adb commands don't work. If you're booting into stock recovery, that seems to be how it works.
If you can't get into recovery with the generic drivers, I swear by Google Galaxy Nexus from Koush's Universal Android package. Someone recommended the HTC dream driver.
EDIT: I see the prob. Wouldn't be able to issue "adb sideload" would you? Sorry, not much help.
---------- Post added at 10:25 PM ---------- Previous post was at 10:06 PM ----------
Well, this is good to know at this thread too!
Click to expand...
Click to collapse
limitedxj said:
So, my fire HD has the Android composite ADB interface as the driver.. I can find the tablet on prompt ADB devices but when I put the device into adb reboot recovery I lose it.. The cme can't see the tablet anymore, any thoughts on a solution? Windows 8 x64
Thanks very much
Click to expand...
Click to collapse
Try this when you are in sideboard mode forum.xda-developers.com/showthread.php?p=36523572#post36523572
Sent from my Nexus 7 using Tapatalk
powerpoint45 said:
Try this when you are in sideboard mode forum.xda-developers.com/showthread.php?p=36523572#post36523572
Click to expand...
Click to collapse
ok, by "sideboard," I'm guessing you mean sideload, but figure you must mean recovery Anyway, thanks!
I think I see problem. I saw this post over here in Q&A, not as part of your upgrade to 5/downgrade to 4.5.3 guide. So, I'm trying this on 4.5.3(!) which doesn't have any "Apply update from ADB" option. When OP said he was able to fix drivers so he could give adb command from recovery, I thought he meant on 4.5.3 and wondered why I couldn't do that.
Makes perfect sense that adb wouldn't recognize a 4.5.3 device in recovery, where it's basically turned off while waiting for a manual reboot or reset. (Eagerly awaiting method to preserve root through 5.0 upgrade ) Ah, well . . .
DoLooper said:
ok, by "sideboard," I'm guessing you mean sideload, but figure you must mean recovery Anyway, thanks!
I think I see problem. I saw this post over here in Q&A, not as part of your upgrade to 5/downgrade to 4.5.3 guide. So, I'm trying this on 4.5.3(!) which doesn't have any "Apply update from ADB" option. When OP said he was able to fix drivers so he could give adb command from recovery, I thought he meant on 4.5.3 and wondered why I couldn't do that.
Makes perfect sense that adb wouldn't recognize a 4.5.3 device in recovery, where it's basically turned off while waiting for a manual reboot or reset. (Eagerly awaiting method to preserve root through 5.0 upgrade ) Ah, well . . .
Click to expand...
Click to collapse
Lol yes I mean sideload. Dumb auto correct. I say sideload instead of recovery because recovery alone has no adb access. Adb is only activated whenever you put it in sideload mode
Sent from my Nexus 7 using Tapatalk
Ah. . . now i get it. Thanks!
Looper,
In cme, using adb devices I was able to see the fire, when typing adb reboot recovery, then adb devices I could no longer cme find the tablet. Well sideload was not going to happen till I could see it again, even tho the tablet was on the recovery prompts. The fix was just checking the driver in device manager after doing the reboot recovery prompt.. Added adb composite to that and then I could find the tablet again, I then sideloaded fine.
I am trying to flash a custom ROM on my OPX because the MM builds of OOS have been giving me strange bugs which apparently no one else seems to be experiencing.
So when trying to unlock my bootloader, when I enter the "Fastboot Devices" command, nothing happens. My device isn't showing up no matter what.
I have all the prerequisite drivers installed so I don't know what is causing this.
Any help would be much appreciated.
Mr. Viscous said:
I am trying to flash a custom ROM on my OPX because the MM builds of OOS have been giving me strange bugs which apparently no one else seems to be experiencing.
So when trying to unlock my bootloader, when I enter the "Fastboot Devices" command, nothing happens. My device isn't showing up no matter what.
I have all the prerequisite drivers installed so I don't know what is causing this.
Any help would be much appreciated.
Click to expand...
Click to collapse
Assuming your putting the phone in bootloader mode what version of windows?
Using Windows 10 and yes, when I boot into bootloader mode still there is no device listed under fastboot devices command.
Mr. Viscous said:
Using Windows 10 and yes, when I boot into bootloader mode still there is no device listed under fastboot devices command.
Click to expand...
Click to collapse
Same Here
ADB also won't work
Fixed adb after installing Google usb driver
But fastboot still not detected
Sher1234 said:
Same Here
ADB also won't work
Fixed adb after installing Google usb driver
But fastboot still not detected
Click to expand...
Click to collapse
Yeah mate do me a favor and let me know if you find a solution for this, alright?
Mr. Viscous said:
Yeah mate do me a favor and let me know if you find a solution for this, alright?
Click to expand...
Click to collapse
No success till yet but hopefully someone would help us soon
Mr. Viscous said:
Yeah mate do me a favor and let me know if you find a solution for this, alright?
Click to expand...
Click to collapse
I'm pretty sure it has something to do with Windows 10. And I read somewhere a fix just can't remember. Something to do with rolling back the driver or uninstalling. I believe its written in the hardbrick guide take a look there.
Install USB drivers and 15 second ADB and fastboot drivers then you are good to go. I am also using windows 10 without any problem.adb and fastboot working nicely..even in Linux adb and fastboot working perfectly.
farooque7508 said:
Install USB drivers and 15 second ADB and fastboot drivers then you are good to go. I am also using windows 10 without any problem.adb and fastboot working nicely..even in Linux adb and fastboot working perfectly.
Click to expand...
Click to collapse
Ok I'll try it & let u know
farooque7508 said:
Install USB drivers and 15 second ADB and fastboot drivers then you are good to go. I am also using windows 10 without any problem.adb and fastboot working nicely..even in Linux adb and fastboot working perfectly.
Click to expand...
Click to collapse
This didn't worked I tried this but afterwards doing this I wasn't able to use adb anymore & no luck for fastboot even
I think it's a driver issue but my other device is working so can't say what's exactly happening
Any other idea or method to use fastboot
Sher1234 said:
This didn't worked I tried this but afterwards doing this I wasn't able to use adb anymore & no luck for fastboot even
I think it's a driver issue but my other device is working so can't say what's exactly happening
Any other idea or method to use fastboot
Click to expand...
Click to collapse
Try on an old fashion Win7 computer...
Or a flash drive booting linux distro
Did you try
Install Qualcomm USB driver and check
faap25 said:
Install Qualcomm USB driver and check
Click to expand...
Click to collapse
Can I have the link for this please
@Sher1234 use this and try
http://www.androidbrick.com/download/qdloader-hs-usb-driver/
farooque7508 said:
@Sher1234 use this and try
http://www.androidbrick.com/download/qdloader-hs-usb-driver/
Click to expand...
Click to collapse
I'll surely give it a try tomorrow & let you know if this worked or not
& Thanks for your help
farooque7508 said:
@Sher1234 use this and try
http://www.androidbrick.com/download/qdloader-hs-usb-driver/
Click to expand...
Click to collapse
Not Worked
But I'll try installing Windows 7 and perform the same process this weekend
If you done with installing windows 7
Install OnePlus X drivers you can find it in OnePlus forum
Install 15 sec ADB and fastboot
And check it should work.
farooque7508 said:
If you done with installing windows 7
Install OnePlus X drivers you can find it in OnePlus forum
Install 15 sec ADB and fastboot
And check it should work.
Click to expand...
Click to collapse
Thanks for info I'll install Windows 7 this weekend due to college work
I'll will do it as you said and it will be stepwise
And will inform you if this work or not
Thanks Anyways
Sher1234 said:
Thanks for info I'll install Windows 7 this weekend due to college work
I'll will do it as you said and it will be stepwise
And will inform you if this work or not
Thanks Anyways
Click to expand...
Click to collapse
Don't install Win7 just for that. Find someone who have one.
Or try with a USB booting Linux Distro it will be quicker and easier.
Kéno40 said:
Don't install Win7 just for that. Find someone who have one.
Or try with a USB booting Linux Distro it will be quicker and easier.
Click to expand...
Click to collapse
Ok I'll try it and will report if this works for me or not
---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------
Kéno40 said:
Don't install Win7 just for that. Find someone who have one.
Or try with a USB booting Linux Distro it will be quicker and easier.
Click to expand...
Click to collapse
But can you tell which Linux OS should I try???
I tried Ubuntu it doesn't install fastboot drivers on live boot so can't use fastboot or adb commands