Database Info

Is my Nexus 5 bricked?

Last night I tried to flash CM 11 through TWRP. I wiped factory and it failed. This morning I rebooted and no sim card or sd card could be found. I went to fastboot, tried to unroot back to stock and now my phone is stuck on boot loop. I can still boot into twrp but now my backup is missing and its not recognizing the sd. Can anyone help?

there's an sd card slot?!?

dicecuber said:
there's an sd card slot?!?
Click to expand...
Click to collapse
No, just the internal sd.

is it not letting you flash the stock image?
http://forum.xda-developers.com/showthread.php?t=2513701

Have you tried reading the sticky threads that tell you how to unbrick the device?
Sent from my Nexus 5 using Tapatalk

jj14 said:
is it not letting you flash the stock image?
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Thanks, trying this now.

jj14 said:
is it not letting you flash the stock image?
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
It's saying fastboot is not a recognized as an internal or external command

FuMMoD said:
Have you tried reading the sticky threads that tell you how to unbrick the device?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Where are these stickies at? I'm not finding one in either development forum.

You skipped a step somewhere
Which method are you using? If you are using method 2, you have to set the path (or change directory) - depending on where you installed abd/fastboot to.

Top in general and top in question&answer forum.
Sent from my Nexus 5 using Tapatalk

FuMMoD said:
Have you tried reading the sticky threads that tell you how to unbrick the device?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Was it necessary to be rude? Would it have been more helpful to provide a link?
Engineer4life said:
It's saying fastboot is not a recognized as an internal or external command
Click to expand...
Click to collapse
Engineer4life said:
Where are these stickies at? I'm not finding one in either development forum.
Click to expand...
Click to collapse
You need to have adb and fastboot .exe's in the same directory as the factory images(assuming you're using Windows). Here's a link to a guide. You're definitely not bricked, just some problems with TWRP right now. http://forum.xda-developers.com/showthread.php?t=2513701

i would also suggest you to try to use some toolkit and bring it back to factory setting and then re root it...

housry23 said:
Was it necessary to be rude? Would it have been more helpful to provide a link?
You need to have adb and fastboot .exe's in the same directory as the factory images(assuming you're using Windows). Here's a link to a guide. You're definitely not bricked, just some problems with TWRP right now. http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
I went through the steps of adding the different drives. Downloaded SDK, saved to C:/ and tried to run fastboot to flash image. It keeps telling me fastboot is not recognized. Do you know of any other methods to flash a stock image. I cant even access my internal sd through TWRP, it's not recognized.

Engineer4life said:
I went through the steps of adding the different drives. Downloaded SDK, saved to C:/ and tried to run fastboot to flash image. It keeps telling me fastboot is not recognized. Do you know of any other methods to flash a stock image. I cant even access my internal sd through TWRP, it's not recognized.
Click to expand...
Click to collapse
You need to open a command prompt in the same directory as the fastboot executable. There are a million tutorials on exactly how to set up your adb/fastboot properly. Even Google provides the instructions on the same page you download the factory images. It isn't hard to do so
Sent from my Nexus 5

Pirateghost said:
You need to open a command prompt in the same directory as the fastboot executable. There are a million tutorials on exactly how to set up your adb/fastboot properly. Even Google provides the instructions on the same page you download the factory images. It isn't hard to do so
Sent from my Nexus 5
Click to expand...
Click to collapse
I've followed every step from this link
http://forum.xda-developers.com/showthread.php?t=2513701
I created and named the file image-hammerhead-krt16m and saved to C:/
the folder contains
android-info
boot.img
bootloader.img
cache.img
flash-all
flash-all.sh
flash-base.sh
image-hammerhead-krt16m..zip
radio.img
recovery.img
systerm.img
userdata.img
I've tried executing the command "fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img" from C:/android-adb/. It keeps giving me error: cannot open 'C:/image-hammerhead-krt16m/bootloader.img'

Engineer4life said:
I've followed every step from this link
http://forum.xda-developers.com/showthread.php?t=2513701
I created and named the file image-hammerhead-krt16m and saved to C:/
the folder contains
android-info
boot.img
bootloader.img
cache.img
flash-all
flash-all.sh
flash-base.sh
image-hammerhead-krt16m..zip
radio.img
recovery.img
systerm.img
userdata.img
I've tried executing the command "fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img" from C:/android-adb/. It keeps giving me error: cannot open 'C:/image-hammerhead-krt16m/bootloader.img'
Click to expand...
Click to collapse
You're using the wrong slashes. File directories are C:\file\goes\here, not C:/file/goes/here

bilago said:
You're using the wrong slashes. File directories are C:\file\goes\here, not C:/file/goes/here
Click to expand...
Click to collapse
Sorry, I used the right slashed in cmd and it's the same error

Engineer4life said:
Sorry, I used the right slashed in cmd and it's the same error
Click to expand...
Click to collapse
try making a simple folder . Move all the files from this directory to C:\nexus5\ .
open a command prompt and type this:
Code:
pushd c:\nexus5
then type
Code:
fastboot flash bootloader bootloader.img
what is the results

open command prompt from start menu. on mine, it starts me at
Code:
C:\Documents and Settings\Users\Austin
Use the command "cd.." to back up until you're at C:\
From there, type
Code:
cd image-hammerhead-krt16m
You should be at that directory now. and it'll say
Code:
C:\image-hammerhead-krt16m
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
without having to try and navigate to them every time. This worked for me. If you have adb drivers installed correctly and the "adb version" and "fastboot devices" command both work, you're good.
EDIT : Just as a heads up, the last command "fastboot erase cache" messed up something on mine. It wouldn't hold APNs or connect to any network, so I had to run fastboot flash cache cache.img

Synyster06Gates said:
open command prompt from start menu. on mine, it starts me at
Code:
C:\Documents and Settings\Users\Austin
Use the command "cd.." to back up until you're at C:\
From there, type
Code:
cd image-hammerhead-krt16m
Click to expand...
Click to collapse
Its a lot faster and efficient to just type
Code:
pushd c:\image-hammerhead-krt16m
Your method will not work if the user has their documents folder on another partition, which is a smart way to set up your computer.

[GUIDE]How to update from 5.0 to 5.x without loosing data if you're not 100% stock

Instead of having instructions all over the place inside various threads I felt a clear guide should be available as it's own thread. Now since Google implemented this great feature (all hail google) where normal OTA's no longer work on Nexus devices with Android 5.0 that isn't 100% stock i.e. rooted with or without custom recovery a lot of people don't know how to update their devices.
IMO opinion the easiest way without losing any data is to use Fastboot and this is an attempt of a how-to-guide. This is made on a windows PC, probably works with other OS's too.
What you need:
1. You need ADB.exe and fastboot.exe inside an easy accessed folder i.e. put in c:\ADB.
The easiest way to get these are with this tool: http://forum.xda-developers.com/showthread.php?t=2317790
You can also get this by installing the whole Android SDK but that is just a waste of bandwidth and time.
2. You also need to download the latest factory image for Nexus 5. Do this here: https://dl.google.com/dl/android/aosp/hammerhead-lrx22c-factory-0f9eda1b.tgz
3. You might need adb drivers but you'll have to find instructions for this by yourself.
The procedure:
1. Extract necessary files. The factory image you'll download is named hammerhead-lrx22c-factory-0f9eda1b.tgz
This is an archive which can be opened with an extractor of your choice e.g. 7-zip
Inside this archive is another file with no file type extension. Extract this file and rename it to whatyouwant.zip since it's a regular zip file. Then extract all files within this file (very meta with zips inside zips inside zips etc).
The files you need for updating with fastboot are:
system.img
boot.img
radio-hammerhead-m8974a-2.0.50.2.22.img (rename this to radio.img for more convenience)
put all these files in the ADB folder (it will make things easier).
2. plug your phone to your PC. You need to have USB debugging activated in developer mode.
3. open a command prompt and orient yourself to the adb folder (c:\ADB)
4. type adb reboot bootloader and wait until your phone is in bootloader mode.
5. type fastboot flash system system.img and wait until it's finished.
6. type fastboot flash radio radio.img
7. type fastboot flash boot boot.img
8. reboot your device (type fastboot reboot).
Hopefully this will work and you will update without loosing any data. Then you can proceed with rooting, flashing custom recovery etc. This is easiest done with WUG nexus root toolkit (http://forum.xda-developers.com/showthread.php?t=2389107)
I couldn't find any other guide's but if there's already one please remove this.

Just a note, you don't need adb.exe at all, and the drivers are actually USB drivers.
Its also worth noting that 95% of us prefer to recommend users not use toolkits.
Also, you could simply say:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
...then point them to the existing adb and fastboot thread which would have saved you writing all the installation stuff out.

Thanks for the guide @mertzi. I've just used to upgrade my Nexus 5 to 5.0.1 without any loss of data. I appreciate the help!

rootSU said:
Just a note, you don't need adb.exe at all, and the drivers are actually USB drivers.
Its also worth noting that 95% of us prefer to recommend users not use toolkits.
Also, you could simply say:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
...then point them to the existing adb and fastboot thread which would have saved you writing all the installation stuff out.
Click to expand...
Click to collapse
Do I still use "fastboot flash radio radio.img" even though the radio image from the tgz file is "radio-hammerhead-m8974a-2.0.50.2.22.img"?

optoisolator said:
Do I still use "fastboot flash radio radio.img" even though the radio image from the tgz file is "radio-hammerhead-m8974a-2.0.50.2.22.img"?
Click to expand...
Click to collapse
No. The 4th section is the file path and location.

So this keeps user data? Just updated the system to 5.0.1?
Maintains root and all?
Sent from my Nexus 5 using XDA Free mobile app

Keeps user data but you will have to re-root.

Thank you, thank you, thank you.
I've spent last couple days trying to make heads or tails out of other "tutorials". Some of them linked the OTA update and gave instructions for full image, others gave instructions but lacked the links to the image. I am surprised that none of my searches took me here until today.

Thanks a lot for this guide I was ale to update to 5.0.1 thanks to this guide.

Can I use this method to update from 4.4.4 to 5.0.0 ?

... Not aire if you can jump from 4.4.4 to 5.0 this way...
I actually jumped flashing radio and baseband and THEN flashing CM12.1

[Q] NOT your average stuck in bootloop

Bear with me: Right now my nexus is stuck in a bootloop. My nexus had been partially rooted, everytime i went to download the OTA 5.0.1. update it would just take me to TWRP, and i didn't know what to do with that. So I finally tried to fully root the phone, and also use TWRP to install the OTA update. Now I'm stuck, I've tried wiping the cache/factory reset. How do I got about flashing it back to stock without losing all my data?
(apologies for the title, I thought originally that I had killed mtp and adb, but I figured out how to get them back just after posting)
Thanks!

As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits

Ben36 said:
As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits
Click to expand...
Click to collapse
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.

The reason I say read the guides is simply it saves me or anyone else typing out a massive guide that already exists in many places.
If you're looping then something is more than likely wrong with the system not the data. So flashing just the system will keep your data safe (as long as you flash the same android version as you previously had, lollipop or kitkat)
You need to be in the bootloader not recovery and use the command fastboot flash system system.img
Google img's are here - https://developers.google.com/android/nexus/images
(just keep unzipping until you find the individual img files)

photobumm said:
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.
Click to expand...
Click to collapse
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!

_MetalHead_ said:
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!
Click to expand...
Click to collapse
So I have adb and fastboot running. And I changed the flash-all.bat file. However, I don't understand what I do now? I downloaded the Hammerhead zip and it has a bunch of things in it. Which files do I put into the adb/fastboot folder and how do I then flash them?
In the hammerhead file it lists the bootloader, flash-all, radio and then a zip file "image-hammerhead...". What files am I using and what is the code that I input? Is this the same sa flashing a rom?
I also tried placing the system.img in the adb folder, and then using the
Code:
fastboot flash system system.img
but it gives me an error "cannot load 'system.img'

So now my issue is I get a "error: could not load 'system.img'. after running
Code:
fastboot flash system system.img [code/] . I also tried with boot.img. Same error.
I ran the "flash all" script, by accident, a screenshot of the terminal is attached.. I'm still stuck in a the boot loop, however, and if try to enter recovery mode an android lying down with a red triangle is present. The above "error: could not load..." is still present.

Create a folder and put fastboot in it.
So you unzipped the stock image. You said you have some images in the folder and a zip image.
Unzip that second zip.
There you will find the rest of the images you need.
Now take the recovery, bootloader, system, userdata, cache, and radio images and move them into the folder which you created for fastboot.
Rename the bootloader image to bootloader. img
Now when looking at that open folder containing all the images and fastboot hold down shift and left click and select "open command promt from window"
Type
/fastboot erase bootloader
/fastboot flash bootloader bootloader.img
/fastboot reboot-bootloader
/fastboot erase recovery
/fastboot flash recovery recovery.img
/fastboot erase radio
/fastboot flash radio radio.img
Repeat for the rest of the image files
Finally type /fastboot reboot
Profit.
---------- Post added at 10:54 PM ---------- Previous post was at 10:51 PM ----------
P. S. Make sure your phone is booted in fastboot mode first.

Oh and that android is stock recovery

U fixed it?

So for some reason I still kept getting that error. I ended up restoring to stock using the nexus root toolkit. So it all worked out in the end.

cannot load system.img error

Hello
I am not able to flash system.img , i get the cannot load system.img error in cmd prompt. All other .img flash fine
i flashed twrp and tried repair , did not help.
i have also fastboot erased cache , system , bootloader but it didnt help in clearing the system and flashing the stock one on top
Also i can flash a custom rom in TWRP and boot but the storage is then stuck at around 12 GB.
Any pointers guys ?

Are you flashing the files one by one or using the script?
A factory reset from stock recovery should bring you back to 32. After a good flash of course.

this happened to me once
heres how i fixed it on my windows vista machine
1- Make sure you run CMD as admin
2- Make sure you close all other applications before sending system.img (on my case it was chrome holding RAM even tho i have 3GB of RAM and plenty was available)

Solved
Thanks for the replies guys.
I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
It was for sure the RAM being used a lot on the current machine although i had 4 GB of RAM.

likonvampire said:
Thanks for the replies guys.
I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
It was for sure the RAM being used a lot on the current machine although i had 4 GB of RAM.
Click to expand...
Click to collapse
Wow thank you so much for this! I was running into this error on Windows 8.1 with 10GB of RAM and plenty free!!!! I guess this command sends it out and writes it in chunks? Can we figure out why this is happening?

Could it be instead related to using up inodes? And not RAM?

likonvampire said:
Thanks for the replies guys.
I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
It was for sure the RAM being used a lot on the current machine although i had 4 GB of RAM.
Click to expand...
Click to collapse
Thank you so much for this. My rig has 16 Gigs or ram, could it be something else causing this issue?

HELP!
on my side is showing me waiting for device what should i do?

Aosp e6653

I've managed to compile 5.1.1 aosp,
here is my problem, fastboot doesn't seem to recognize the command i'm typing in '-S 256M' as stated on the sony site.
If i try and flash them the normal way, for example "fastboot flash system system.img"
it doesn't flash like this, i have tried on linux and windows.
I've attached screenshots to show my problem.
Edit- I should of said first, I can flash boot, recovery and userdata the normal way, but system.img hangs. Fastboot won't let me use the command listed on the sony site when flashing any of the partitions.
My compiled system.img seems fine and I can view and extract the files so I don't think it's corrupted.

issue '-S 265M' after 'flash'..!!!
SO it should be 'fastboot flash -S 265M system system.img'
And you need to specify memory breakdown for the system image only, as it has a massive size, for the rest skip using '-S 265M'
P.S.: You certainly seem to be new at Android compilation.. I would advice you to try checking other forums first... checking out what works and what doesn't before experimenting! Just saying!
Cheers