Hi Guys
While trying to unlock the bootloader on my xperia play I get to the step where im in the command prompt window in windows to see if there is a connection between fastboot.exe and the phone.
When I go to see if there is a connection between the 2 (for example 0.3) it just states the message "waiting for device" in the command prompt window.
Ive tried reinstalling the drivers and such, any recommendations or fixes.
Thanks All.
Maybe download the new flashtool and open drivers.exe in the drivers folder,check everything and let it install for 10 minutes,btw post questions in the questions thread! You could get banned FoReveR
Kmd use to be my fav when i was a kid, loved those big rockstar glasses
Related
I tried unlocking the bootloader with fastboot and every time i try i get "waiting for device" i tried in on two different computers. Please if anyone can help i'll really appreciate that.
Dennis Rambarran said:
I tried unlocking the bootloader with fastboot and every time i try i get "waiting for device" i tried in on two different computers. Please if anyone can help i'll really appreciate that.
Click to expand...
Click to collapse
I keep getting that on my desktop (W7U 64-bit), but not on my laptop (W7HP 32-bit). Tried installing the Android SDK and USB drivers (successfully) yet?
Be sure and install java.
This should fix your problem. (I have windows 7 home premium 64 bit, was getting the same issues).
http://javadl.sun.com/webapps/download/AutoDL?BundleId=36668
*facepalm* My god, it's already turning into the same mess as on the Dream Dev forum... all the "please help" questions...
But, this forum is new, so I guess it's easy to get confused. Just so you know, though, this belongs in general, or in Q&A when they get one of those.
About your problem... plug your phone in and see what happens. Do not mount it. Does windows prompt you to install a driver? If not, open a terminal (yeah yeah, command prompt, whatever) and type adb devices. You may need to install the driver.
I installed the SDK and drivers but I get the same problem, BTW - I'm running windows XP SP2. I'm at this for 2 hrs now this is frustrating...
http://forum.xda-developers.com/showthread.php?t=613217
charkosh said:
Be sure and install java.
This should fix your problem. (I have windows 7 home premium 64 bit, was getting the same issues).
http://javadl.sun.com/webapps/download/AutoDL?BundleId=36668
Click to expand...
Click to collapse
Java is *not* needed for this.
Once you have your drivers installed, as linked by Mikey, ensure that you have usbdebugging enabled.
"fastboot devices" will let you know if you have your n1 ready to go or not. Sorry, fastboot-windows devices.
typed fastboot-windows devices and nothing happens
Hello..I am a complete n00bie here
I am trying to root and unlock the bootloader of my N7 and I am having a problem:
http://forum.xda-developers.com/showpost.php?p=42745327&postcount=377
As per the method..I downloaded the files on my desktop and now trying to move those over to /sdcard..but having device not found error..
some help here pls..
rockstar283 said:
Hello..I am a complete n00bie here
I am trying to root and unlock the bootloader of my N7 and I am having a problem:
http://forum.xda-developers.com/showpost.php?p=42745327&postcount=377
As per the method..I downloaded the files on my desktop and now trying to move those over to /sdcard..but having device not found error..
some help here pls..
Click to expand...
Click to collapse
I responded in the other thread let me know if that helps otherwise we can take this to pms and I will try to help you that way.
While following this tutorial..
LINK
I reach successfully till 'adb push supersu.zip /sdcard/'
but when I try to install zip from sdcard..device errors out saying 'Can't mount sdcard'
I tried 'adb push supersu.zip /sdcard/0/' but I get same error
any idea what the problem might be??
underwaterjr said:
Sorry I got tied up. If it doesn't list any devices you don't have adb set up yet. First go into settings on your device, you have to enable developer options by going into about tablet and scroll down to bottom and tap build number about seven times, it will tell you when your getting close. Then go into developer options and enable android debugging. Now plug your tablet into computer and you should get a pop up asking you if this computer is ok for debugging or something like that so enable it or say yes what ever the option is. Sorry doing this from memory so can't tell you exactly verbatim what those popup prompts say. Now for debugging on the computer end. I don't know how long you've had the sdk on your computer so just make sure its up to date by opening the sdk manager and check for any updates. In order for adb to work with 4.2.2 you need the latest tools. Ok so with all that done now open a cmd window and navigate to your platform-tools folder and try adb devices again. you should get a read out of some numbers after that. Let me know if that works and we can proceed. Good luck!
Click to expand...
Click to collapse
This helped me..Thank you underwaterjr:laugh:
Hey,
my Nexus 7 turned off a while ago, I tried to load it overnight and also a reset via power / volume. Nothing worked so far. If connected to a Ubuntu computer, it does not show up in the adb devices list, but under "lsusb" as nvidia device (which makes sense, concidering the Tegra-processor). If connected to a Windows pc it tries to install a ADX driver. No idea what that means though, a google search did not bring up a thing, which is why I posted here.
Does anybody has an idea, what that driver is or if there is a possibility to bring the Nexus 7 back to life? Asus will not exchange the device since the one year warranty is over, and the second year is ignored somehow (I'm located in Germany).
Thanks for your help,
blckDTshadow
blckDTshadow said:
Hey,
my Nexus 7 turned off a while ago, I tried to load it overnight and also a reset via power / volume. Nothing worked so far. If connected to a Ubuntu computer, it does not show up in the adb devices list, but under "lsusb" as nvidia device (which makes sense, concidering the Tegra-processor). If connected to a Windows pc it tries to install a ADX driver. No idea what that means though, a google search did not bring up a thing, which is why I posted here.
Does anybody has an idea, what that driver is or if there is a possibility to bring the Nexus 7 back to life? Asus will not exchange the device since the one year warranty is over, and the second year is ignored somehow (I'm located in Germany).
Thanks for your help,
blckDTshadow
Click to expand...
Click to collapse
There is tons of stuff regarding 7s in ADX, much of it complicated. Do a search here on that topic. I do know that there is a first step that rew I ores you to have made a device-specific backup of certain files beforehand. There are a couple of easier fixes that involved a degree of luck.
Try This
blckDTshadow said:
Hey,
my Nexus 7 turned off a while ago, I tried to load it overnight and also a reset via power / volume. Nothing worked so far. If connected to a Ubuntu computer, it does not show up in the adb devices list, but under "lsusb" as nvidia device (which makes sense, concidering the Tegra-processor). If connected to a Windows pc it tries to install a ADX driver. No idea what that means though, a google search did not bring up a thing, which is why I posted here.
Does anybody has an idea, what that driver is or if there is a possibility to bring the Nexus 7 back to life? Asus will not exchange the device since the one year warranty is over, and the second year is ignored somehow (I'm located in Germany).
Thanks for your help,
blckDTshadow
Click to expand...
Click to collapse
First try following the instructions in the site located in the document below
If that doesn't work, try this. I have done it 2 times already and it worked twice
Here's what to do:
- Downloaded the file N7_restore.zip file before, now the link doesn't work so i'll upload it somewhere soon and give the link.
- Then extract the zip file you just downloaded and in that folder there is another zip called image-nakasi-jrn84d
- Extract that zip and Copy all the files in the newly extracted folder to the N7_restore folder
- in the N7_restore folder open a cmd by pressing shift and right clicking together and then clicking open command window here
- Then type/copy without the quotes "fastboot flash bootloader bootloader-grouper-3.34.img"
Do not go to the next step until it says the flashing is successful or it will be a waste of time.
- Next type/copy without the quotes "fastboot flash boot boot.img"
- Next type/copy without the quotes "fastboot flash recovery recovery.img"
- Next type/copy without the quotes "fastboot flash userdata userdata.img"
- Next type/copy without the quotes "fastboot flash system system.img"
If you want to Lock the bootloader
- type/copy without the quotes "fastboot oem lock"
That's it. It worked for me twice and should work for you
P:S: i am still looking for the link of the recovery so i don't have to upload it but if i don't find it i'll try to upload it by tomorrow.
This instruction works with windows 7/8/8.1. Should work with xp/vista and mac.
Hey John,
that might be a bit late, however thanks for your answer. I manged to get a refurbished device by Google. Was actually really surprised about it - did not really expect this
Have a nice weekend,
blckDTshadow
Hi All,
I have been trying for hours (more than a week actually all in all) to sideload apps to my Lg Smart Watch Sport.
I have found more than one thread that speaks to how to achieve this and I have followed to a T as far as I know.
I have ADB and Fastboot installed and when I enter adb devices it shows my phone is connected.
Each time I follow the script after the adb connect localhost:4444 script I get the message 'no connection could be made because the target machine actively refused it (10061)'
I have debugging and bluetooth debugging on my Sport and phone has debugging as well.
I have tried the Android Wear APK Tools app as well and it just say error, cannot install.
I am using a MI Mix in case it matters.
Im not sure if the problem is my computer (Windows 10) or the Mi Mix but I have hit a dead end.
Anyone out there that can help I would sure appreciate it!
Best source is this: https://developer.android.com/training/wearables/apps/debugging.html
Edit: on the first connection with "adb devices" you should get a dialogue on your watch asking for authorization
ranf said:
Best source is this: https://developer.android.com/training/wearables/apps/debugging.html
Edit: on the first connection with "adb devices" you should get a dialogue on your watch asking for authorization
Click to expand...
Click to collapse
I have been trying for days to get this to work and that tutorial got me up and running.....I cant thank you enough.
make sure you open Command Prompt with Admin privileges.
Guys, i know this question has been asked numerous times here, even about this specific device but ive read dozens of threads and read dozens more of other sites and i can't find an answer to my problem..my problem is this....
I have a Moto E4 from Metro PCS. i want to root it and install a custom rom like i have done on dozens of other phones (thanks to the awesome people here at XDA.D
i get tuck right off the bat since i cant get the bootloader unlocked..i know its poible through this site. https://motorola-global-portal.custhelp.cowithin m/app/standalone/bootloader/unlock-your-device-b
The part that has me stumped (i know its something simple but i jut dont undertand where it says
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
At the prompt, type
$ fastboot oem get_unlock_data
i just dont get it..I like to think im pretty proficient with computer and phones but not so much when it comes to terminal/command line stuff i guess... what does it mean to make sure fastboot is in my $PATH?
does it mean the fastboot.exe? or something else?
also the device for some reason doesn't seem to be recognized under ADB Device..when it is it says it's unauthorized.....and when i try to open up a terminal either in that location or if i navigate to that location within the prompt after i type $ fatstboot "with or without the "$"" it say's something like the command isnt recognized..sorry for this drawn out post, im just trying to give as much info as i can the 1st time around
my device i Metro PCs moto e4 on 7.1.1...model XT1765.
Thank you for just reading this let alone answering or helping me out with this problem..it is much appreciated,, im trying to get my girlfriend phone better and get her into the whole custom rom scene but im making myself look kind of foolish here that ive been able to root/twrp/rom every other phone ive had besides this one.
xandawg said:
Guys, i know this question has been asked numerous times here, even about this specific device but ive read dozens of threads and read dozens more of other sites and i can't find an answer to my problem..my problem is this....
I have a Moto E4 from Metro PCS. i want to root it and install a custom rom like i have done on dozens of other phones (thanks to the awesome people here at XDA.D
i get tuck right off the bat since i cant get the bootloader unlocked..i know its poible through this site. https://motorola-global-portal.custhelp.cowithin m/app/standalone/bootloader/unlock-your-device-b
The part that has me stumped (i know its something simple but i jut dont undertand where it says
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
At the prompt, type
$ fastboot oem get_unlock_data
i just dont get it..I like to think im pretty proficient with computer and phones but not so much when it comes to terminal/command line stuff i guess... what does it mean to make sure fastboot is in my $PATH?
does it mean the fastboot.exe? or something else?
also the device for some reason doesn't seem to be recognized under ADB Device..when it is it says it's unauthorized.....and when i try to open up a terminal either in that location or if i navigate to that location within the prompt after i type $ fatstboot "with or without the "$"" it say's something like the command isnt recognized..sorry for this drawn out post, im just trying to give as much info as i can the 1st time around
my device i Metro PCs moto e4 on 7.1.1...model XT1765.
Thank you for just reading this let alone answering or helping me out with this problem..it is much appreciated,, im trying to get my girlfriend phone better and get her into the whole custom rom scene but im making myself look kind of foolish here that ive been able to root/twrp/rom every other phone ive had besides this one.
Click to expand...
Click to collapse
Your tethered device (phone) is not communicating with the host (PC). Install Motorola Device Manager on the host to insure you have the proper drivers. Might need to install Minimal Fastboot and ADB as well. Links below.
https://support.motorola.com/us/en/drivers
https://forum.xda-developers.com/showpost.php?p=42407269&postcount=1
Thank you for the rapid resonse..see I had that installed but I read somewhere on the site while downloading it that it could interfere with adb interface so I deleted it..I will reinstall and try again and post back..just wondering. Should I install adb/fastboot at the default location or should I install it in the android SDK folder..I read somewhere I need the android SDK to unlock the E4 bootloader. Is that true do u know?..have you done this process yourself?
xandawg said:
Thank you for the rapid resonse..see I had that installed but I read somewhere on the site while downloading it that it could interfere with adb interface so I deleted it..I will reinstall and try again and post back..just wondering. Should I install adb/fastboot at the default location or should I install it in the android SDK folder..I read somewhere I need the android SDK to unlock the E4 bootloader. Is that true do u know?..have you done this process yourself?
Click to expand...
Click to collapse
Every moto device I own is unlocked. No need to alter default locations. Don't believe everything you read from self-anointed experts.