Hi,
I tried to sideload the last ota update on my Nexus 5x but I can't because the device is not recognized.
I tried to install again and again the Google USB drivers, but nothing changes.
I found a lot a tips on internet which worked for other people but nothing works me.
Does anybody have a solution ?
Thanks.
Cheers.
Lolokro.
I don't know if I'm in the right section, sorry if I don't.
Sent from my Nexus 5X using XDA Free mobile app
Have you installed and setup according to Heisenberg's guide from the sticked thread?
Hi Darke5tShadOw,
Thanks for your answer. I didn't exactly follow this guide but the steps I did where the same.
I had the same issue with my Nexux 5, and I was fixed so I guessed it should be OK with the 5x....
Sent from my Nexus 5X using XDA Free mobile app
lolokro said:
Hi Darke5tShadOw,
Thanks for your answer. I didn't exactly follow this guide but the steps I did where the same.
I had the same issue with my Nexux 5, and I was fixed so I guessed it should be OK with the 5x....
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Does adb recognize you device?
Darke5tShad0w said:
Does adb recognize you device?
Click to expand...
Click to collapse
Yes, but only when the device boots on system. When booting in bootloader or recovery, it's not. That's my problem.
Sent from my Nexus 5X using XDA Free mobile app
lolokro said:
Yes, but only when the device boots on system. When booting in bootloader or recovery, it's not. That's my problem.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Do you know that adb needs to be replaced with fastboot when in bootloader? Try running in a cmd window with admin privileges (I don't use windows and it needs admin privileges on linux)
Do you have custom recovery or stock?
Have you tried with the nexus toolkit? If it works then the problem has to be with your adb setup. On another windows computer I had to repoint my fastboot drivers.
http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
These are the instructions I and a few others needed to get fastboot working
http://forum.xda-developers.com/showpost.php?p=65367022&postcount=1555
Read thishttps://www.reddit.com/r/nexus5x/comments/49xwg4/faq_regarding_adb_sideloading_with_the_new_ota/ or see this https://www.youtube.com/watch?v=uvch38KDmTk
Darke5tShad0w said:
Do you know that adb needs to be replaced with fastboot when in bootloader? Try running in a cmd window with admin privileges (I don't use windows and it needs admin privileges on linux)
Do you have custom recovery or stock?
Have you tried with the nexus toolkit? If it works then the problem has to be with your adb setup. On another windows computer I had to repoint my fastboot drivers.
http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
These are the instructions I and a few others needed to get fastboot working
http://forum.xda-developers.com/showpost.php?p=65367022&postcount=1555
Click to expand...
Click to collapse
freq_ency said:
Read thishttps://www.reddit.com/r/nexus5x/comments/49xwg4/faq_regarding_adb_sideloading_with_the_new_ota/ or see this https://www.youtube.com/watch?v=uvch38KDmTk
Click to expand...
Click to collapse
I will try this on Sunday.
But the fact is my Nexus is not recognized in the Windows Device Manager. It doesn't appear even in hidden devices..
I 'll tell you when i'll try.
Sent from my Nexus 5X using XDA Free mobile app
Hi,
I tried today to re-install the drivers and I tried to use the NRT but nothing work. I can't push the ota update. A pop-up said the device is not found in fastboot mode. Again...
I will try next time with another Windows PC but I don't when I will can.
I don't understand what is the problem because NRT told me the drivers installation was successful.
Sent from my Nexus 5X using XDA Free mobile app
Hi, i tried today with another Windows PC and my Nexus was finally recognized but the sideload abort during the process because an "error" occurred. Anybody knows what it means?
Thank you for your answers.
Cheers.
Sent from my Nexus 5X using XDA Free mobile app
lolokro said:
Hi, i tried today with another Windows PC and my Nexus was finally recognized but the sideload abort during the process because an "error" occurred. Anybody knows what it means?
Thank you for your answers.
Cheers.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
The ota is probably corrupt. Re-download the file and try again.
PiousInquisitor said:
The ota is probably corrupt. Re-download the file and try again.
Click to expand...
Click to collapse
I downloaded the filed from here http://www.digitaltrends.com/mobile...es-on-google-nexus-devices/3/#:wQDy1wa9IyyUWA
Do you have any source?
Sent from my Nexus 5X using XDA Free mobile app
lolokro said:
I downloaded the filed from here http://www.digitaltrends.com/mobile...es-on-google-nexus-devices/3/#:wQDy1wa9IyyUWA
Do you have any source?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/ota#fugu
Sent from my Nexus 5X using Tapatalk
Related
Hey everyone, I need some help. I flashed my Gnex to Yakju a few months ago using the official drivers and Android SDK with no problem. A friend of mine recently bought a Gnex and asked me to flash his phone. For some reason -fastboot devices couldn't recognize his phone when connected to the same computer that I used to flash my own Gnex. I can't unlock his bootloader as a result. I tried again with my own Gnex and my computer was able to recognize my phone. What did I do wrong?
Try reinstalling the drivers.
The same problem happened to me when I was trying to flash my friends Xoom.
I reinstalled the drivers and it located the device.
Sent from my Nexus 7 using xda premium
You used the command 'fastboot devices' when you loaded the phone into the bootloader mode? Cause if you're in the android OS, you need to use 'adb devices' (assuming you enabled debugging under developer options)
Sent from my Galaxy Nexus using xda app-developers app
El Daddy said:
Try reinstalling the drivers.
The same problem happened to me when I was trying to flash my friends Xoom.
I reinstalled the drivers and it located the device.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I should try that. Do I need to uninstall the old drivers first?
-Psycho- said:
You used the command 'fastboot devices' when you loaded the phone into the bootloader mode? Cause if you're in the android OS, you need to use 'adb devices' (assuming you enabled debugging under developer options)
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Ya it was in bootloader mode. I forgot to mention that when my friend's phone was in the Android OS, "adb devices" worked and my computer recognized his phone. So strange.
NexusDro said:
I should try that. Do I need to uninstall the old drivers first?
Ya it was in bootloader mode. I forgot to mention that when my friend's phone was in the Android OS, "adb devices" worked and my computer recognized his phone. So strange.
Click to expand...
Click to collapse
I have always said that the "official" drivers are flaky at best. You should really use 1wayjonny's package.
Sent from my Galaxy Nexus using Tapatalk 2
So as will be immediately obvious, I am new to posting on this site and I'm sure the title will explain why. Before I start, I was using (the 'was' will be explained later) a rooted stock ROM and I had not backed it up (the instructions I used forgot to mention it).
The 2.17 HOX OTA update was finally released by three (I'm currently on 1.28) and I hoped that this update would fix several problems I've been having (standard HOX problems like battery life, camera quality, lag, and an ever growing system data). So I was fairly desperate to install this update, but when I tried clockwork recovery told me that it failed, and by using google I discovered that I'm not the only one with this problem.
This where I get stupid. In desperation to install this update I found that SuperSu has an option to full unroot and I hoped that this would reinstall the stock recovery in the process, but now I am left with an unrooted phone with clockwork recovery installed.
If anyone can help me reinstall the stock recovery so I can install this update I'd very much appreciate it. I apologise if I was long winded, I just felt it better to try and explain the whole situation.
Sent from my HTC One X using xda app-developers app
I'm not sure what's stopping you from installing the stock recovery?
fastboot flash recovery stock-recovery.img
Thanks for replying. I'm not very knowledgeable at this so I'm not sure how to, and would I need to use a computer or can I do it directly on my phone?
Sent from my HTC One X using xda app-developers app
adb reboot-bootloader
adb flash recovery recovery.img
Click to expand...
Click to collapse
do you have the stock reocvery.img?
No I don't think so, can I download it? Should I already have it, and if so where would it be?
Sent from my HTC One X using xda app-developers app
Mbennett156 said:
No I don't think so, can I download it? Should I already have it, and if so where would it be?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
hold on ill upload it for you
Thanks
Sent from my HTC One X using xda app-developers app
Mbennett156 said:
Thanks
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
recovery for 1.28
hamdir said:
recovery for 1.28
Click to expand...
Click to collapse
thanks so much. how do i flash it? if it's too much trouble i'm sure i could find it on google
@Mbennet
hamdir said:
recovery for 1.28
Click to expand...
Click to collapse
Place it in your fastboot Android-SDK folder on your PC (C:/Android-SDK/platform-tools)
Put phone into fastboot USB
Open command prompt on PC
CD c:/Android-SDK/platform-tools
fastboot flash recovery recovery.img
Sent from my Nexus 7 using XDA Premium HD app
chrisjcks said:
@Mbennet
Place it in your fastboot Android-SDK folder on your PC (C:/Android-SDK/platform-tools)
Put phone into fastboot USB
Open command prompt on PC
CD c:/Android-SDK/platform-tools
fastboot flash recovery recovery.img
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
thanks so much for your help and quick replies my phone is currently on low battery as i've spent all day frantically trying to figure this out, but when it is charged i'll let you know if this is successful :good:
EDIT: the computer i'm using at the moment is not the same computer that i used when i rooted (that one broke unfortunately) can i just create that folder or do i need to redownload other files?
Mbennett156 said:
thanks so much for your help and quick replies my phone is currently on low battery as i've spent all day frantically trying to figure this out, but when it is charged i'll let you know if this is successful :good:
EDIT: the computer i'm using at the moment is not the same computer that i used when i rooted (that one broke unfortunately) can i just create that folder or do i need to redownload other files?
Click to expand...
Click to collapse
You need to install Android SDK on the PC you want to do this on.
http://developer.android.com/sdk/index.html
Update/install everything on it once installed.
Then you can begin.
Sent from my Nexus 7 using XDA Premium HD app
chrisjcks said:
@Mbennet
Place it in your fastboot Android-SDK folder on your PC (C:/Android-SDK/platform-tools)
Put phone into fastboot USB
Open command prompt on PC
CD c:/Android-SDK/platform-tools
fastboot flash recovery recovery.img
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have just successfully reinstalled the stock recovery, and although I am very grateful for your help, you forgot to mention the next step which was to type "fastboot oem lock" on command prompt.
Thanks again!
Mbennett156 said:
I have just successfully reinstalled the stock recovery, and although I am very grateful for your help, you forgot to mention the next step which was to type "fastboot oem lock" on command prompt.
Thanks again!
Click to expand...
Click to collapse
I would have done had you kept your ongoing progress posted.
But guess you figured it out yourself, congrats.
Sent from my HTC One X using XDA Premium HD app
Some of you may have read my thread a few days ago about me having problems pushing the unlock code into my htc one x well I took that back and exchanged it for the plus
model and I am still in the same boat it says cannot load the unlock code bin file, could it be that my windows 8 just won't allow it to run properly ? Has anyone else unlocked a android device successfully with win 8?
Sent from my Nexus 7 using xda app-developers app
Ok I just tried doing this on a windows vista is and it still comes up cannot load file...
Sent from my Nexus 7 using xda app-developers app
I had problems with Win 8 too. Vista I have never tried.
What you could try is deleting all your htc and phone drives from your computer. Not just run the unninstaller but also remove them from device manager. Then reboot. Then plug your phone back in and let windows install the drivers again.
Ok... Has anyone on a telus htc one x plus unlocked theirs yet?
Sent from my Nexus 7 using xda app-developers app
Can someone help me I am getting extermly frusterated I have tried two diff OSs maybe ADB is not installing right I don't know..
Sent from my Nexus 7 using xda app-developers app
windows 8 works fine, don't know your problem.
Just try:
- Install HTC Sync,
- then install Android SDK with fastboot and ADB,
- then flash Unlock_code.bin
Unlock_code.bin should be 256 bytes in size.
tomascus said:
windows 8 works fine, don't know your problem.
Just try:
- Install HTC Sync,
- then install Android SDK with fastboot and ADB,
- then flash Unlock_code.bin
Unlock_code.bin should be 256 bytes in size.
Click to expand...
Click to collapse
I have done all thee above says my ADB is out of date I went and downloaded the SDK and it does not have the SDK manager in it but this eclipse thing and when I try to install says the java.exe is missing I have latest java install I don't know what's wrong
Sent from my Nexus 7 using xda app-developers app
Lord_Xovon said:
Ok... Has anyone on a telus htc one x plus unlocked theirs yet?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Have you been able to unlock the ONE X+ from Telus ?
I bought the phone new/used from Craigslist. It was a Telus phone and I unlocked it. I've attempted to root it using a guide on here. I'm just looking for a little bit of assistance. I'm also wondering why I am unable to receive OTA JB update. I'm on Bell and in Canada.
http://forum.xda-developers.com/showthread.php?t=2181103
If this is the guide you were following, read it again.
Sent from my Nexus 7 using Tapatalk
atifsh said:
http://forum.xda-developers.com/showthread.php?t=2181103
If this is the guide you were following, read it again.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you. Yes this is the guide I was following. I have downloaded lg united drivers and android sdk. I run the command bat and it goes through all the steps incredibly quickly. It says it's rooted but I don't have root access.
Xoom Master said:
Thank you. Yes this is the guide I was following. I have downloaded lg united drivers and android sdk. I run the command bat and it goes through all the steps incredibly quickly. It says it's rooted but I don't have root access.
Click to expand...
Click to collapse
Android debugging on?
If windows 7 + internet it should auto install drivers
Sent from my GT-P3100 using Tapatalk
atifsh said:
Android debugging on?
If windows 7 + internet it should auto install drivers
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
It seems android sdk is not installed properly. It downloaded and extracted for probably 10 mins using winrar. I believe that is the problem but I'm not sure. I'll give it a go and see what happens. Thanks
Xoom Master said:
It seems android sdk is not installed properly. It downloaded and extracted for probably 10 mins using winrar. I believe that is the problem but I'm not sure. I'll give it a go and see what happens. Thanks
Click to expand...
Click to collapse
Huh?
Should be running stock rom
Debugging in developers option
Plug in phone
Set to charge only
Run the script bat file
Do what it says
Sent from my GT-P3100 using Tapatalk
atifsh said:
Huh?
Should be running stock rom
Debugging in developers option
Plug in phone
Set to charge only
Run the script bat file
Do what it says
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
It keeps saying waiting for device... I'm all stock I put it in debug and charge only. When I run the script it says waiting for device.
Drivers issue or cable issue
Windows 7 install drivers itself from internet, if other OS find proper drivers
Sent from my LG-E975 using Tapatalk
Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
Sounds like debugging is not enabled.
Sent from my Nexus 5X using Tapatalk 2
hopesrequiem said:
Sounds like debugging is not enabled.
Sent from my Nexus 5X using Tapatalk 2
Click to expand...
Click to collapse
How can i do that when i can't get on the phone aha
mworley1991 said:
How can i do that when i can't get on the phone aha
Click to expand...
Click to collapse
Does anything come up when you type "fastboot devices" while your connected in bootloader/fastboot mode?
Sent from my Nexus 5X using XDA-Developers mobile app
hopesrequiem said:
Sounds like debugging is not enabled.
Sent from my Nexus 5X using Tapatalk 2
Click to expand...
Click to collapse
That's only necessary for ADB when booted into Android. Not required when using it from recovery. Anyway, that's irrelevant. The op should be using fastboot in bootloader mode.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
That's only necessary for ADB when booted into Android. Not required when using it from recovery. Anyway, that's irrelevant. The op should be using fastboot in bootloader mode.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
yeah im in fasboot
mworley1991 said:
yeah im in fasboot
Click to expand...
Click to collapse
You should be using fastboot then. I suspect you were, but like so many, erroneously called it ADB.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
You should be using fastboot then. I suspect you were, but like so many, erroneously called it ADB.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
any idea how i can fix this? i meant ADB as in the console on the pc trying to flash through the console isnt showing my device
mworley1991 said:
any idea how i can fix this? i meant ADB as in the console on the pc trying to flash through the console isnt showing my device
Click to expand...
Click to collapse
You need to take Android 101 again. ADB doesn't work when in the bootloader. It works when booted and in recovery.
There are a few potential fixes and a for-damn-sure one. Were you an a custom rom when the bootloop occurred? Rooted stock? More info please...
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
You need to take Android 101 again. ADB doesn't work when in the bootloader. It works when booted and in recovery.
There are a few potential fixes and a for-damn-sure one. Were you an a custom rom when the bootloop occurred? Rooted stock? More info please...
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Rooted stock, but for some reason the custom recovery isn't there anymore either
mworley1991 said:
Rooted stock, but for some reason the custom recovery isn't there anymore either
Click to expand...
Click to collapse
So if I were you I'd download the latest factory images from HERE. Unzip bullhead-mhc19q-factory-22ba5e5a.tgz (or whatever the name is). Then remove the -w from the flash-all.bat file located in the unziped folder. Then execute the flash-all.bat to reflash the factory images without wiping data. Have fun.
mworley1991 said:
Hey,
My nexus 5 is
Click to expand...
Click to collapse
Hold up.
Do you own a 2015 LG Nexus 5X with a fingerprint scanner on the back of the phone?
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
So if I were you I'd download the latest factory images from HERE. Unzip bullhead-mhc19q-factory-22ba5e5a.tgz (or whatever the name is). Then remove the -w from the flash-all.bat file located in the unziped folder. Then execute the flash-all.bat to reflash the factory images without wiping data. Have fun.
Click to expand...
Click to collapse
I don't think that works.
I also have the same problem and when I do that, it errors as "FAILED (remote: device is locked. Cannot flash images)"
Is there a way to unlock bricked device??
redpotatojae said:
I don't think that works.
I also have the same problem and when I do that, it errors as "FAILED (remote: device is locked. Cannot flash images)"
Is there a way to unlock bricked device??
Click to expand...
Click to collapse
You are not in the same situation. Your bootloader is locked. Before anyone can help you, you need to provide more information about your sh!tuation.
Sent from my Nexus 5X using Tapatalk