Database Info

[Q] Fastboot Problems

I am trying to flash a custom recovery with fastboot but it is not working. When i put the device in fastboot mode it says"Starting Fastboot USB download protocol" but the screen doesn't change. When I flash it in CMD it says it finished but the device still does nothing. Then the same when I try to reboot it via flashboot. It says it is done but the device does nothing and I still have no custom recovery.

charger04 said:
I am trying to flash a custom recovery with fastboot but it is not working. When i put the device in fastboot mode it says"Starting Fastboot USB download protocol" but the screen doesn't change. When I flash it in CMD it says it finished but the device still does nothing. Then the same when I try to reboot it via flashboot. It says it is done but the device does nothing and I still have no custom recovery.
Click to expand...
Click to collapse
If fastboot is not working you need to look at 2 things: 1)Android SDK is not installed or 2)driver is not installed correctly. BTW, is your device rooted and unlocked and what version of firmware?
Edit: Also make sure usb debugging is checked in settings.

buhohitr said:
If fastboot is not working you need to look at 2 things: 1)Android SDK is not installed or 2)driver is not installed correctly. BTW, is your device rooted and unlocked and what version of firmware?
Edit: Also make sure usb debugging is checked in settings.
Click to expand...
Click to collapse
I second what buhohitr says...an unlocked tab is imperative to the process.

My device is unlocked but not rooted( I am trying to root it right now). I think it might be the SDK. I'm not sure if I installed it so I will do that now. Thanks
Sent from my Nexus 4 using xda app-developers app

Are you saying it says finished on the cmd prompt? Then it is done :cyclops:
I think you are missing the point.
It won't immediately take you into recovery.
You need to send the reboot command, then power off, power on again with vol down held down until the 4 icons appear, then volume up on RCK which should be default and now you should be in a custom recovery

sbdags said:
Are you saying it says finished on the cmd prompt? Then it is done :cyclops:
I think you are missing the point.
It won't immediately take you into recovery.
You need to send the reboot command, then power off, power on again with vol down held down until the 4 icons appear, then volume up on RCK which should be default and now you should be in a custom recovery
Click to expand...
Click to collapse
Yes I tried that and it just shows a dead android.
Sent from my Nexus 4 using xda app-developers app

charger04 said:
Yes I tried that and it just shows a dead android.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Ah ok it wasn't clear. Are you sure you are unlocked?

sbdags said:
Ah ok it wasn't clear. Are you sure you are unlocked?
Click to expand...
Click to collapse
Yeah... When I boot it says "this device is unlocked"
Sent from my Nexus 4 using xda app-developers app

charger04 said:
Yeah... When I boot it says "this device is unlocked"
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
OK, so everything is clear, you're unlocked. Now back to my previous post:
1. SDK installation (check step 1 (jre java, you probably already have this...everyone does and step 3: SDK)
http://forum.xda-developers.com/showthread.php?t=1842969
2. USB driver:
http://forum.xda-developers.com/showthread.php?t=1706588
Make sure your usb debugging and unknow sources are both checked in settings. (if they are not, please try first before proceed to step 1).

[Q] Need Help! Brand New Out OF Box Root Went Bad.

I'd just rooted Nexus 4 and that went very easy.
Now of out of box root on Nexus 5 went bad.
Installed ADB drivers, adb devices confirmed device, adb reboot bootloader, fastboot oem unlock (which erased everything), fastboot flash recovery recovery-clockwork-touch-6.0.2.3-mako.img (same 1 I used for Nexus 4 4.4 KitKat) and installed, went to recovery and enter. Then it locked up to a dim lit background. Now it won't turn on. Just turns on to very dim lit background that's blank.
The phone is not recognized by the PC no more. No ADB.
Need Help! Any Ideas?

i'll do some looking around. is there a reason you flashed a recovery meant for a different device instead of the ones you can get for the nexus 5?

xBeerdroiDx said:
i'll do some looking around. is there a reason you flashed a recovery meant for a different device instead of the ones you can get for the nexus 5?
Click to expand...
Click to collapse
I was in a hurry and should have read a little more. I thought if it worked for Nexus 4 with KitKat 4.4, it would work for Nexus 5 4.4 (bad idea). Now, I'm worried because the phone won't boot to nothing or turn on. It's just a dim lit background that's black.

so then i'm assuming you cant boot to the bootloader.

xBeerdroiDx said:
so then i'm assuming you cant boot to the bootloader.
Click to expand...
Click to collapse
No, I can't. If I could, I could fit it.

fish411 said:
No, I can't. If I could, I could fit it.
Click to expand...
Click to collapse
just trying to cover the bases, bro

xBeerdroiDx said:
just trying to cover the bases, bro
Click to expand...
Click to collapse
Since I got it today, do you think I could return it and just say it defective? This is going to take an expert to figure this out.

If I read OP correctly it says he flashed recovery for Mako on the N5. Wouldn't that bork a whole bunch of stuff?
Sent from my Nexus 5 using Tapatalk

xBeerdroiDx said:
just trying to cover the bases, bro
Click to expand...
Click to collapse
Hey, I got it in bootloader and tried to start it up but went back to dim lit black background. What should I try next?

@fish411 your only supposed to flash a recovery that's compatible with the nexus 5. You said you flashed to same recovery for your nexus 4 that's the problem it's not compatible.
While your phone is off try accessing recovery mode by holding volume down and power then use volume buttons select recovery. If that brings you to recovery mode try factory resetting
Sent from my Nexus 5 using Tapatalk

fish411 said:
Hey, I got it in bootloader and tried to start it up but went back to dim lit black background. What should I try next?
Click to expand...
Click to collapse
well, the good news is that you can boot to the bootloader. go from there. is the device recognized in windows?

fish411 said:
Hey, I got it in bootloader and tried to start it up but went back to dim lit black background. What should I try next?
Click to expand...
Click to collapse
try fastboot flashing the right recovery. if that doesnt work, you have to fastboot flash the factory image.

OptimusVDarwin said:
@fish411 your only supposed to flash a recovery that's compatible with the nexus 5. You said you flashed to same recovery for your nexus 4 that's the problem it's not compatible.
While your phone is off try accessing recovery mode by holding volume down and power then use volume buttons select recovery. If that brings you to recovery mode try factory resetting
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would he access recovery if he flashed an incompatible one? This looks like flash stock image territory.
Sent from my Nexus 5 using Tapatalk

OptimusVDarwin said:
@fish411 your only supposed to flash a recovery that's compatible with the nexus 5. You said you flashed to same recovery for your nexus 4 that's the problem it's not compatible.
While your phone is off try accessing recovery mode by holding volume down and power then use volume buttons select recovery. If that brings you to recovery mode try factory resetting
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Tried that and get same thing, dim lit black background.

0dBu said:
How would he access recovery if he flashed an incompatible one? This looks like flash stock image territory.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
To see what or if he can enter it or not
Sent from my Nexus 5 using Tapatalk

fish411 said:
Tried that and get same thing, dim lit black background.
Click to expand...
Click to collapse
If you can get to bootloader, flash factory image.
Sent from my Nexus 5 using Tapatalk

0dBu said:
If you can get to bootloader, flash factory image.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Bootloader is recognized by the PC now. I got the Nexus Root ToolKit. What's the best option to use from that?
At least I'd thought, the driver shows up in device manager, but when typing in adb devices in command prompt, it just said " List of devices attached" with on device listed.

fish411 said:
Bootloader is recognized by the PC now. I got the Nexus Root ToolKit. What's the best option to use from that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2507905

fish411 said:
At least I'd thought, the driver shows up in device manager, but when typing in adb devices in command prompt, it just said " List of devices attached" with on device listed.
Click to expand...
Click to collapse
In the bootloader you are in fastboot mode, you would have to use
Code:
fastboot devices
not adb

yup. you'll fastboot flash recovery, not adb flash recovery.

[Q] Stuck at X screen

Obviously I'm a noob, so sorry if this is stupid or there is an obvious answer (I've spent a lot of time looking and couldn't find it though). I was having problems with my phone so decided to flash back to stock and relock it to 'start again'.
Maybe that wasn't a great idea because I've had lots of problems since then. When I try to flash back to stock using nexus root toolkit I get "failed (remote: invalid bootloader)" and the phone finishes still in bootloader. There was a suggestion to force flash, but given the warnings around that I'm pretty nervous about doing that. If I then start my phone up it stays on the google screen for quite a while and then gets stuck on the X screen (it isn't frozen because the animation keeps running, but nothing else happens, even if I leave it for an hour).
I did a bit more reading and tried wiping the dalvik cache and cache. It then said it was upgrading android, optimising apps etc, but then got stuck again. I tried resetting again and the phone now restarts when I push the off button and slowly goes through both the google screen and X screen.
This might be a stupid problem, but I'm stuck so any help would be great.

Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app

http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
Follow this carefully step by step using method 2. Be extremely careful flashing the boot loader, in fact you can probably skip that part. As long as your boot loader is always in tact it's virtually impossible to brick. As of right now you're stuck in what's called a boot loop. Most likely, either your boot.img (not the same as boot loader) or system.img (aka ROM/firmware) is messed up and is causing it.
Welcome to modding, have fun, but be smart
Sent from my Nexus 5 using xda app-developers app

Chromium_ said:
Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).

beshakey said:
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).
Click to expand...
Click to collapse
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app

Chromium_ said:
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks, that worked. But having done it when I reboot the phone it does the same thing (hangs of the Google screen for a long time then moves to the X screen and stays there). My phone is rooted and I have clockworkmod installed, so I selected fix root when asked, not sure if that is relevant?

Did you continue to follow the guide and flash the stock images in fastboot
Sent from my Nexus 5 using xda app-developers app

Yeah I did. I got the message "FAILED (remote:invalid bootloader image) and archive does not contain 'boot.sig' 'recovery.sig' and 'system.sig'. Everything else was OKAY. Put into recovery mode fine (with clockworkmod), wiped data and rebooted (fixing root when asked) but the problem described above remains.

More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh

beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
And you are following the factory image flashing guide that has been provided above?
Can you try going through the guide again, and tell us the specific errors that you are encountering.

And use method two, not the first one that talks about running the flash all script. You should be doing command's like "fastboot flash boot boot.img"
Sent from my Nexus 5 using xda app-developers app

beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
Don't worry, you'll get it, eventually. When you first start doing this kind of thing, it takes some getting used to because you have to read VERY carefully, and perform each step EXACTLY as stated. Computers are absolutely unforgiving of even the tiniest mistake, so you have to take your time, and be patient when you have to start all over. But, it's a challenge, and a learning process, and a lot of fun, once you get the hang of it.
Sent from my Nexus 5

OK, step by step. If you need more detail yell out.
1) I've downloaded ADB and Fastboot
2) If I put ADB devices into the command prompt I don't get any devices listed. But if I put in Fastboot devices I get the serial number of my phone
3) Previously I'd been using method one. So I now extract the image for hammerhead krt16m to my f:\ drive. I've also extracted radio-hammerhead-M8974A-1.0.25.0.17 and bootloader-hammerhead-HHZ11d to the same location and renamed them to radio.img and bootloader.img respectively
4) Phone is connected to computer and in fastboot (and detected by fastboot devices)
5) In command prompt when I type in fastboot flash bootloader f:/bootloader.img I get the error message FAILED (remoteL invalid bootloader image).
6) Flashed radio.img and rebooted bootloader and system.img (no reboot) without any errors (although they took a while)
7) Flashing userdata.img got the error 'FAILED (remote: flash write failure)
8) Performed all the remaining commands without any errors (when erasing the cache I got the message 'Did you mean to fastboot format this partition? erasing 'cache'... OKAY
9) Entered recovery mode. Earlier when I did this it was fine, but now (like when I try to start the phone) the screen lights up but no text etc appears
10) At this point I'm stuck, as I can't see the cwm text so can't select wipe data/factory data reset (although I did do this as part of earlier attempts)
From the 'on but no text' state, I can using the on button to restart into the same state or can enter fastboot (where text etc appears fine)

One at the boot loader you said you put f:/bootlaoder.img that was wrong, no drive letter. You do not need to flash your boot loader though anyways. Avoid doing that unless you have to, it is the only thing that will brick your phone.
You said system.img flashed fine, did not see any Menton of a boot.img or recovery.img. you need all three of these.
So, start over again. Make sure you flash a boot.img system.img and recovery.img separately. DO NOT flash the bootloader.img unless you have to (to update). Again, the boot loader is the one thing that will brick your phone if done wrong.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 07:31 AM ---------- Previous post was at 07:28 AM ----------
Sorry I just read through that tutorial and it does tell you to use drive letters. Im used to flashing with my files in the location of fastboot so I don't need to do that.
Sent from my Nexus 5 using xda app-developers app

@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode

Good catch.
Sent from my Nexus 5 using xda app-developers app

samersh72 said:
@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode
Click to expand...
Click to collapse
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?

beshakey said:
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?
Click to expand...
Click to collapse
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app

travisjustin said:
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?

beshakey said:
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?
Click to expand...
Click to collapse
4.3? The nexus 5 ships with kitkat 4.4 ...there is no 4.3 for it.
Sent using xda-developers app

Did my phone bricked itself? Please help!

Hey guys, I received my OnePlus One today yayy!
BUT. I booted the phone, configured everything like I wanted, installed all the apps I wanted and then I got an OTA update so I figured I would do that too!
The phone rebooted and... stuck on the 1+ logo / powered by android.
I asked around and people on the OnePlus forums told me to boot into recovery and perform a factory reset / clear cache.
I did this and my phone booted again. I reconfigured everything, reinstalled everything and I decided to reboot the phone.
It got stuck again on the logo.
Now though... I can't boot into recovery mode. I asked for help again but no answers... through some research, I installed Android SDK and tried to open a command prompt and type "adb devices". Nothing appears in the list.
Can someone help me? I just want to cry...

Before you can use ADB, you need the ADB drivers. Download the OnePlus One Toolkit and use the feature that downloads and installs the correct drivers. Or you can manually look for them.
Sent from my One using Tapatalk

TheShoxter said:
Before you can use ADB, you need the ADB drivers. Download the OnePlus One Toolkit and use the feature that downloads and installs the correct drivers. Or you can manually look for them.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Drivers are already installed, the phone is stuck in the boot sequence.
It's detected by both "adb devices" and "fastboot devices". It responds to commands like "fastboot reboot" but since it cannot reboot, this achieves nothing. I can't "fastboot oem unlock" because the phone doesn't load the OS.

djodars said:
Drivers are already installed, the phone is stuck in the boot sequence.
It's detected by both "adb devices" and "fastboot devices". It responds to commands like "fastboot reboot" but since it cannot reboot, this achieves nothing. I can't "fastboot oem unlock" because the phone doesn't load the OS.
Click to expand...
Click to collapse
Ok, and you said that you're on 100% stock? No custom ROM or kernel?
Sent from my One using Tapatalk

If you can get fastboot just load everything back to stock and start over.
Sent from my One using XDA Premium 4 mobile app

You can manually enter into fastboot mode without command.Just press power button+volume up button.Once you enter into fastboot ,unlock bootloader,flash twrp & then flash stock rom
Sent from my One using XDA Premium 4 mobile app

RISHI RAJ said:
You can manually enter into fastboot mode without command.Just press power button+volume up button.Once you enter into fastboot ,unlock bootloader,flash twrp & then flash stock rom
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey, thanks for your reply!
I'm also getting help from the OnePlus forums but here are the latest updates:
I managed to get into fastboot and flash everything (boot, cache, system, recovery etc.). However, everytime I reboot, it still hangs on the boot screen. I have to leave the phone off for about 5 minutes, get into recovery mode, clear the cache and boot into the OS... every... single... time I reboot.
Is there a reason for this? Should I install another ROM (like Paranoid Android or Color OS) instead? Is there a fix to this or is it even software-based?

Unlock bootloader ,flash twrp,flash flashable rom zip.In twrp wipe everything,then go to mount & then uncheck system.Then flash the rom.zip
Sent from my One using XDA Premium 4 mobile app

[Q] Nexus 5 boots in "erasing"

Completely stock Nexus 5 wont boot. When it powers on it goes into the animation of the Droid with "erasing" under it. This began randomly last night after I unplugged it from a car charger. Up until this point the phone was perfect.
I can boot into the option menu where I can select Restart Bootloader or Recovery mode, but no matter what I choose the phone restarts and goes directly to Erasing.
Any tips on how to recover without losing everything?
Thanks in advance ~ Shaneous

I'm not sure what the problem is. I haven't seen this issue before. But I'd try booting into the bootloader and flashing the cache.img with fastboot from the factory image of whatever version of android you're on. See method 2 of this http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I'm not sure what the problem is. I haven't seen this issue before. But I'd try booting into the bootloader and flashing the cache.img with fastboot from the factory image of whatever version of android you're on. See method 2 of this http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Will give this a shot right now. Thanks

Shaneous said:
Will give this a shot right now. Thanks
Click to expand...
Click to collapse
Well Method 2 will wipe the phone which is what I am trying to prevent. Also my computer cannot detect the phone when it is in fastboot mode.

Factory reset?

Shaneous said:
Well Method 2 will wipe the phone which is what I am trying to prevent. Also my computer cannot detect the phone when it is in fastboot mode.
Click to expand...
Click to collapse
You only want to run the fastboot flash cache cache.img of method 2, not all the commands. But not being detected by your pc is another issue. Does it show up in device manager at all? Do you have usb drivers installed?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You only want to run the fastboot flash cache cache.img of method 2, not all the commands. But not being detected by your pc is another issue. Does it show up in device manager at all? Do you have usb drivers installed?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Don't think he mentioned if his bootloader was locked or unlocked..
If it's locked, there is nothing you can do except sent it in for a repair (you'll likely lose everything anyways since they'll probably just do a motherboard swap), or unlock it (and lose data).
It it's unlocked, then there a multiple things you can do; flash factory images, use a custom recovery, etc.