Related
I missed out something i think.
I have my sdk, with those files.
I went to cmd and type the commant
bla bla bla
fastboot devices >>> no error, means connected
fastboot oem unlock
>>>> it is connected but why it still waiting for my device?
I added the path to the system too, but still cant get rid of
I search the net and I cant get the solution.
Any idea anyone?
What drivers did you install? And yes, I read the "fastboot devices"
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Phone has to be in bootloader mode?
Sent from my Nexus S using XDA App
yup.. it is in volume up + on mode.
If you plug your NS in and look in the Device Manager, do you see an unknown device with the question mark? If so, you should try to manually install the driver located in android-sdk-windows\extras\google\usb_driver
And when you issue the command
Code:
fastboot devices
It should display your NS device id, not just a blank line.
melvinchng said:
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Click to expand...
Click to collapse
"samsung" driver... no
you use the drivers obtained from the Android SDK or PDAnet
Pretty much what suksit said.
Try pdanet! Last place i go y find drivers
Sent from my Nexus S using XDA Premium App
I tried sdk driver, pdanet driver. I can't unknown driver, it is listed as android. Means my phone is found by computer
I have android 2. 3. 4. Does it effect?
Sent from my Nexus S using XDA Premium App
Just curious, did you enabled the option in Settings > Applications > Development > USB debugging?
In Device Manger it should say something like "Android Composite ADB Interface"
I enabled it too... maybe I will try to reinstall and root it via my XP in VM.
I rooted my wildfire with this pc last time, maybe the drive mixed up.
Sent from my Nexus S using XDA Premium App
Just noticed that your location is in Malaysia. Could it happen that you have the i9023 (SLCD) model? If that's the case then I think you should try this.
Ya, I bought slcd set.
I will try it tomorrow at night and report back to you guys.
--------------------------------
It is really strange. Tried everything and won't work.
Pdanet detected my device that it is connected to computer, but it just show wait for device.
----------------------------------------
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
melvinchng said:
Ya, I bought slcd set.
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yeah thats normal, Samsung did some weird battery calibration thing!
However people here have found to get 100% or close to it.
When charging just leave screen on for 1 hour and have tethered wifi On, so far im charging full up to 98%, just waiting to squeeze in the last 2%.....could take awhile.
and yeah the 95% charge is normal. heres a explanation in further detail
Your battery gauge is lying to you (and it's not such a bad thing)
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
j0l6 said:
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
Click to expand...
Click to collapse
i have these in tools. and still waiting for device.
anyone any idea?
I forgot to tell you guys that my windows is 64-bit
Sent from my Nexus S using XDA Premium App
Try this or this then (the latter is quite hard to read anyway, I think they messed up the code formatting)
Unlocked bootloader!
thanks!
Sent from my Nexus S using XDA Premium App
melvinchng said:
I haven't root yet.
After I root, my storage and Rom will be wipe? So I need to install new Rom?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Rooting will add su binary and Superuser app to your NS. But your data will be wiped (both on phone and SD card) when you unlock the bootloader -- it's the same as doing a factory reset. However, your system partition will not be affected so no need to install new ROM if you prefer using stock.
Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
haloux said:
Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
Click to expand...
Click to collapse
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Vivek_Neel said:
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
Thanks for the quick response.
Win7 doesn't even detect the N5. Device manager doesn't even show that it exists (as android device or anything else). I've unplugged and replugged, no sound, multiple different ports.
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
habitformer said:
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
Click to expand...
Click to collapse
Will do (or won't do?). Thank you for the advice. Any tips on how to get my system to recognize the device?
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
habitformer said:
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
Click to expand...
Click to collapse
Yea, USB debugging was on. The recovery mode just yields the dead android.
adrman said:
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
Click to expand...
Click to collapse
How would I verify that? I assumed that fastboot drivers were installed bc I used them in the past.
Code:
fastboot devices
(yields)
No devices found.
I would do a search here for "windows fastboot drivers". I can't be of much help to you as I haven't used windows for several years now. Also, if you have a working Android device, see if it shows up when connected in bootloader mode as a test.
Sent from my Nexus 5 using Tapatalk
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
haloux said:
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
Click to expand...
Click to collapse
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Wow. It worked! The device showed up! Thank you guys.
haloux said:
Wow. It worked! The device showed up! Thank you guys.
Click to expand...
Click to collapse
Not sound like a turd but I mentioned using a nexus USB cable in post #7 after mentioning my issue.
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
osamarchie2000 said:
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
Click to expand...
Click to collapse
Why don't you flash the factory image using fastboot?
The Cmd box you are referring to happens because you need to navigate to that directory using Cmd and run it from there. You cannot just click it.
Thanks but I cant get the SDK to work at all. Im still looking into it but at the moment it wont work
Please somebody help me with the SDK, I dont know what else to do.
I cant open the SDK manager and I cant open it through eclipse either.
Someone else must have had this problem before
Click the link in my signature and then "adb and fastboot. What is it?"
This will help you configure adb properly. It also helps you learn commands. Like adb push.
adb sideload is the same as push but you type sideload instead.
FYI as much as people round here say it, there is no such thing as a soft brick. Its brick or not brick.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Show down and don't panic. Your device is easily fixed. Hold the power button for 20 seconds. This will shut down the phone. Then press and hold the vol down then press the power button. That'll bring your into the bootloader.
Sent from my Nexus 5 using XDA Free mobile app
osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Power + volume down button brings you in the bootloader, from there go into recovery (navigate with volume buttons and select with power button)
In recovery follow this guide: http://forum.xda-developers.com/showthread.php?t=2559200.
Or flash the factory image in the bootloader. (that should work because you need to unlock your bootloader in fastboot)
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yeah that will work too. Water damage is never good for a phone even if it stil works after that. But that's another story
osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yes you can. You'll have to "tell" twrp where to find the rom zip.
Sent from my Nexus 5 using XDA Free mobile app
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
osamarchie2000 said:
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
Click to expand...
Click to collapse
You don't need the SDK. You're not developing here
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
TWRP cant find any of the files on my USB-OTG
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Did you read my thread that I told you to read?
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Here's a hint, read rootSU's sticky rollup and look for the 15 second fastboot adb installer.
Sent from my Nexus 5 using XDA Free mobile app
Very sorry, Ive just re-read what Im looking for
Appologies
thankyou all, phone is well and good and im on CM11.
Thanks guys, anyone who helped is the best
Android users need help with my phone! I am trying to manually turn on USB debugging (to access files on phone through update thru ADB mode in recovery options, I can install the driver for the phone but won't work until USB debugging is turned on) while my phone cannot boot into the OS. Is there a secret way to turn on USB debugging through recovery mode? (I do not want to wipe the data, and phone unfortunately is not rooted)
USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk
rootSU said:
USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My main issue is that I am trying to retrieve my non backuped data on the phone and the phone itself will not boot into the Android OS.
I have looked into unlocking the fastboot/bootloader but it will wipe the data which would be pointless.
The data on the phone is more critical to me than the phone itself (and yes I was dumb enough to not back it up, didn't expect a flagship phone less than a year to crash on me, but I have learned for next time).
I am looking for any possible way to retrieve the data. I have tried to access the phone from the computer but I cannot access it since USB debugging is turned off and the phone is not rooted or doesn't have any other modifications.
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?
Y is it non bootable?
Sent from my Android 5.0 Nexus 5
You are stuck. Stock recovery, locked bootloader, and OS will not boot. As RootSU mentioned, USB debugging has nothing to do with this. Stock recovery will not connect to adb.
Unless you can get the phone to boot looks like data is lost. Sorry.
Yoda8232 said:
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?
Click to expand...
Click to collapse
No.
Yoda8232 said:
didn't expect a flagship phone less than a year to crash on me
Click to expand...
Click to collapse
Expect it from every electronic device. Especially expensive and complicated ones.
So I actually had warranty left from Google (bought directly from Google) and was going to RMA it but I decided not to because the data on there is important to me and worth more than the phone itself (yes I should of backuped everything but oh well what can I do now). And I bought a new phone so this Nexus 5 will be my little side project to try and revive it; somehow.
I will try to keep going at it, I have small programming/coding skills but it would be nice to find a way to open up the USB debugging option on the locked stock phone somehow that doesn't bootup.
Any suggestions on where I should start to start testing different "procedures"?
Nexus 5 Stuck in bootanimation with flying dots (No usb debugging)
Hi,
I have this nexus 5 which was not rooted, the usb debugging option is off and the bootloader is in locked state as nothing has been done on it in the past.
The phone is stuck on flying dots animation. I have tried various methods but all require usb debugging to be on. How can I go back to stock without having to turn usb debug option on? I have seen some mentions of fast oem unlock, but how do I do that?
Thanks!
The first thing you do is go here and look for how to return to stock, http://forum.xda-developers.com/showthread.php?p=53439068. Then remember this thread because it had everything you'll ever need.
Sent from my Nexus 9 using XDA Free mobile app
buhnanafone said:
Hi,
I have this nexus 5 which was not rooted, the usb debugging option is off and the bootloader is in locked state as nothing has been done on it in the past.
The phone is stuck on flying dots animation. I have tried various methods but all require usb debugging to be on. How can I go back to stock without having to turn usb debug option on? I have seen some mentions of fast oem unlock, but how do I do that?
Thanks!
Click to expand...
Click to collapse
+1
jd1639 said:
The first thing you do is go here and look for how to return to stock, http://forum.xda-developers.com/showthread.php?p=53439068. Then remember this thread because it had everything you'll ever need.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Hey man thanks, I have seen that but again it requires usb debugging. However I did find this program that unlocks bootloader WITHOUT usb debugging on!!!! It's called Unlockmybootloader v2 by yashade2001. Now I can continue my journey onto trying to return to stock! Wish me luck :fingers-crossed:
buhnanafone said:
Hey man thanks, I have seen that but again it requires usb debugging. However I did find this program that unlocks bootloader WITHOUT usb debugging on!!!! It's called Unlockmybootloader v2 by yashade2001. Now I can continue my journey onto trying to return to stock! Wish me luck :fingers-crossed:
Click to expand...
Click to collapse
You do not need usb debugging enabled to use fastboot. To unlock the bootloader all you need to do is have fastboot instated on your pc, then boot into the bootloader and run the command fastboot oem unlock. I highly encourage you do read the thread I linked you to and learn about your device. There's a lot there so focus on how to return your device to stock and how to unlock the bootloader, root and flash a rom. You'll thank me in the long run
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You do not need usb debugging enabled to use fastboot. To unlock the bootloader all you need to do is have fastboot instated on your pc, then boot into the bootloader and run the command fastboot oem unlock. I highly encourage you do read the thread I linked you to and learn about your device. There's a lot there so focus on how to trying your device to stock and how to unlock the bootloader, root and flash a rom. You'll thank me in the long run
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I have tried cmd prompt fastboot oem unlock before with fastboot installed, it didn't work. And even for that it said usb debugging must be on. Also new problem persists, flash-all.bat file to flash factory images is giving me error such as
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1046364912 bytes
error: update package missing system.img
buhnanafone said:
I have tried cmd prompt fastboot oem unlock before with fastboot installed, it didn't work. And even for that it said usb debugging must be on. Also new problem persists, flash-all.bat file to flash factory images is giving me error such as
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1046364912 bytes
error: update package missing system.img
Click to expand...
Click to collapse
Alright, first Google 15 second adb install xda. That'll setup fastboot and adb on your pc and make it so you don't need to worry about what directory your running fastboot from.
Then, in the thread I linked you to look for how to return to stock and follow method 2, the long method. Flash-all.bat doesn't work almost all the time.
Don't worry about the *.sig errors. Those are normal.
Sent from my Nexus 5 using XDA Free mobile app
Here is your solution: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
eross said:
Here is your solution: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Click to expand...
Click to collapse
Man, that's a lot of messing around when the first step should be trying to flash the factory images. Then, maybe trying to fix the persist partition. And you're fix requires usb debugging enabled which the op doesn't have.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Man, that's a lot of messing around when the first step should be trying to flash the factory images. Then, maybe trying to fix the persist partition. And you're fix requires usb debugging enabled which the op doesn't have.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
That is why you first flash Android 4.4. It will boot with a corrupted persist partition, enough to enable usb debugging.
Yeah but prob no need for all that
Sent from my Nexus 5 using Tapatalk
ldubs said:
Yeah but prob no need for all that
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It was for me and quite a few others..... Nothing to lose by trying.
buhnanafone said:
Hey man thanks, I have seen that but again it requires usb debugging. However I did find this program that unlocks bootloader WITHOUT usb debugging on!!!!
Click to expand...
Click to collapse
I started and restarted a reply to this post but I'm just baffled. I'll just say that you don't understand USB debugging at all.
Yeah, bootloader has nothing to do with usb debugging. In order to fix persist partition, you need adb, which requires usb debugging, which can only be enabled from a working OS (AFAIK).