Related
Please delete this thread.
The updated version is here
http://forum.xda-developers.com/showthread.php?t=1167819
you could always post the links as text and then after 10 posts then you can convert to urls again
www.filefactory.com/file/cb882b4/n/Flash_Recovery.zip
www.filefactory.com/file/cb88370/n/Full_recovery.zip
filefactory.com/file/cb882b4/n/Flash_Recovery.zip link 1
filefactory.com/file/cb88370/n/Full_recovery.zip link 2
PM Sent.....
Its telling me that fastboot is not a internal or external command. I'm going into the cmd and typing cd filepath then the fastboot instructions. Am I missing something?
Fixed! Thanks so much!
cloo24 said:
Its telling me that fastboot is not a internal or external command. I'm going into the cmd and typing cd filepath then the fastboot instructions. Am I missing something?
Fixed! Thanks so much!
Click to expand...
Click to collapse
Your welcome and so everyone else knows you have to hold ctrl and shift in the folder and then click on open command prompt.
ok i made it simpiler to follow. I decided to do this because the ota is coming and many people want stock back.
Anyone have any issues getting stock recovery back on their nexus? I have ran odin a few times with stock files and I end up with no recovery, just that triangle exclamation thing. I have tried fastboot flashing stock recovery as well as custom ones with no luck. The only thing that has saved me is shabby's one click...for some reason its fastboot flash of recovery works while doing it manually doesn't...but that doesn't put on stock recovery...
Thanks I really needed these instructions.
Sent from my Nexus S 4G using XDA Premium App
raiderep said:
Anyone have any issues getting stock recovery back on their nexus? I have ran odin a few times with stock files and I end up with no recovery, just that triangle exclamation thing. I have tried fastboot flashing stock recovery as well as custom ones with no luck. The only thing that has saved me is shabby's one click...for some reason its fastboot flash of recovery works while doing it manually doesn't...but that doesn't put on stock recovery...
Click to expand...
Click to collapse
When I was on stock (when I first got the phone) I remember not having a recovery at all ( just the triangle) .
Sent from my Nexus S 4G using XDA Premium App
ok i used odin put those files in the right spot but its not doing anything. It says all threads comp succeed 0 failed 0 any ideas
ok will i treid this method and it dosent work i follow the directions just like it says put the tar files in the right spot hit start and nothing happens. it gives me the mess suceed 0 failed 0. put it download more and it just sits there. i do have adb set up for the device
Petes method is better than this method guys. Use fastboot, just copy and paste the commands into the terminal. Much better than this.
mikeyinid said:
Petes method is better than this method guys. Use fastboot, just copy and paste the commands into the terminal. Much better than this.
Click to expand...
Click to collapse
Hey mike would you mind a pm on how to, cause I'm a little lost.
Sent from my Nexus S 4G using XDA Premium App
info[]box1 said:
Hey mike would you mind a pm on how to, cause I'm a little lost.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
OK. You obviously have fastboot drivers installed cus your rooted. Download THESE, courtesy of Pete. Extract that zip to a folder on your desktop. Open that folder, hold shift and right click in the folder and choose open command window here. Then run these commands, hitting enter at the end of each line:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
That is all, takes like a minute or 2 and your back to stock. I can do it with my eyes closed
Thanks Mike
Sent from my Nexus S 4G using XDA Premium App
windows can not recognize my phone can someone help me !
damnn said:
windows can not recognize my phone can someone help me !
Click to expand...
Click to collapse
can't recognize it at all, or can't recognize it in fasboot mode?
cant recognize it in fast boot mood.. my phone is on like normally and usb debugging is on and when i type in the cmd it doesnt go through it says "adb" is not regnozied as an internal or external command operable program or batch file
gonna try this since ive got a replacement phone on the way, what would happen if it sent the phone back unlocked and rooted anyway?
Hi
I have bricked my nexus s when I loaded a ROM that I downloaded.
I have used several different ROMs and had no problems.
I asume this ROM was dodgey.. Anyway I get no screen at all, the menu control at the botom of the screen lights up but that is it.
I can get to it using fastboot but it won't load any ROMS. There is no action on the Nexus screen itself.
Is there a guide using fastboot to recover this also what file/files will I need to download?
Thanks in advance any help would be much appreciated.....
If you are here looking for help you need to give us more information.
What model Nexus S do you have?
What rom did you flash?
What have you done sense flashing the rom?
My guess is you flashed a rom that isn't for your model phone. So you either have SAMOLED or SLCD. I'm guessing the rom you installed was for the screen type you don't have.
So let us have some more details so we can help.
Sent from my Nexus S 4G using xda premium
Sounds like a call for the mighty Odin...
Sent from my Nexus S 4G using xda premium
And u can't get into recovery using the button method?
Sent from my Nexus S using XDA App
If you can get fastboot to work, you can flash all partitions including system. Don't worry, this is an easy fix.
Hi Again guys
Firstly thanks a lot for the replys I really appreciate it.
Its a 3g the model no: is GT-19023.
Its SAMOLED that much I know.
I cannot get into recovery I can get fastboot to recognise the phone but nothing on the screen.
I have downloaded a stock rom and extracted the boot, recovery & system.img files.
I have followed the instructions below and all seems to work till I get to the system. it fails with the following message. The other steps seem to work OK.
"FAILED (remote write failed)"
I have also tried this with several other ROMs I know work on wifes Nexus s and still no luck. Some allow the system to be flashed but the phone still won't boot.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
Any help would be great
I also downloaded ODIN but cant get it to work; It does not recognise that it is connected to the USB, but fastboot does!. (Is there a step by step guide to using it?)
Sorry for sounding like noob, but I have read everything and looked up these forums and tried a lot before asking for help.
GL
If your phone is a Gt-i9023 it is SLCD!!!!! Not SAMOLED.
Again what rom did you flash? Post a link to it. I still think you flashed a rom for SAMOLED when you have SLCD.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
If your phone is a Gt-i9023 it is SLCD!!!!! Not SAMOLED.
Again what rom did you flash? Post a link to it. I still think you flashed a rom for SAMOLED when you have SLCD.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
BTW, so 9020 ROMs are incompatible with 9023? I am aware of differences between those devices, but when I looked in "Development" section, there is no info, about compatibility with 9020a/t/9023
http://forum.xda-developers.com/showthread.php?t=955719
pretty sure that is the link to the ROM.
I tried to restore using another stock ROM (I backed it up from another Nexus that was only rooted and stock)... Yes it was exactly the same phone model etc.
The problem is now the error is saying ===FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)===
I tried that (the unlock command) and the prompt just types three dots (...) and then hangs there. I have tried removing the battery etc and the same issue.
I am happy to erase the phone to nothing and load another image.
It seems that maybe this phone is cooked....
I hope not ==shattered==
k_myk said:
BTW, so 9020 ROMs are incompatible with 9023? I am aware of differences between those devices, but when I looked in "Development" section, there is no info, about compatibility with 9020a/t/9023
Click to expand...
Click to collapse
ROMs are compatible between those variants! But, if you're flashing some stock ROM bundles you can flash wrong one. Because bundles contain rom, kernels and radios for specific device with specific drivers. In that case you can flash wrong driver for your display, or even something worse...
Follow what it says, unlock your bootloader first.
Sent from my GT-P1000 using xda premium
glockman63 said:
http://forum.xda-developers.com/showthread.php?t=955719
pretty sure that is the link to the ROM.
I tried to restore using another stock ROM (I backed it up from another Nexus that was only rooted and stock)... Yes it was exactly the same phone model etc.
The problem is now the error is saying ===FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)===
I tried that (the unlock command) and the prompt just types three dots (...) and then hangs there. I have tried removing the battery etc and the same issue.
I am happy to erase the phone to nothing and load another image.
It seems that maybe this phone is cooked....
I hope not ==shattered==
Click to expand...
Click to collapse
Your link still does not tell us which rom you flashed....
You can't flash a rooted rom through fastboot without unlocking the bootloader first. Sounds like you need to restore a factory rom with Odin.
Sent from my Nexus S 4G using xda premium
Hi all
I got this sorted out and am really happy to have my phone going again.
For those interested or in the same predicament I was in please read on as this is how I managed to make this phone go again.
Please rmemeber this phone was really bricked no screen at all jus the menu light like in the picture in my first post.
As I stated I could get fast boot to see the phone. And also Odin. (Still no screen at all)
I had another phone the same with the original rom on board.
I rooted this phone and installed ClockworkMod recovery ad used this to backup the standard ROM.
I then rebooted this phone an copied these files from the backup into my fastboot directory (boot.img, recovery.img, system.img)
I then connected my dead phone up to my PC and ran the following commands.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
I then removed the battery and to my astonisment the phone booted normally into the standard ROM.
WOW I was over the moon I have since installed my MIUI Rom and using my phone happily...
Thanks everyone for your input..
Rem3Dy said:
Your link still does not tell us which rom you flashed....
You can't flash a rooted rom through fastboot without unlocking the bootloader first. Sounds like you need to restore a factory rom with Odin.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I've got a phone in the same state I am trying to revive for a guy. With the bootloader locked download mode gives you a locked bootloader screen. Odin sends the flash images to the phone, the phone verifies them but then refuses to flash them (presumably due to the bootloader being locked). The bootloader won't unlock so there is no way to flash a rom to fix the phone.
glockman63 said:
Hi all
I got this sorted out and am really happy to have my phone going again.
For those interested or in the same predicament I was in please read on as this is how I managed to make this phone go again.
Please rmemeber this phone was really bricked no screen at all jus the menu light like in the picture in my first post.
As I stated I could get fast boot to see the phone. And also Odin. (Still no screen at all)
I had another phone the same with the original rom on board.
I rooted this phone and installed ClockworkMod recovery ad used this to backup the standard ROM.
I then rebooted this phone an copied these files from the backup into my fastboot directory (boot.img, recovery.img, system.img)
I then connected my dead phone up to my PC and ran the following commands.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
I then removed the battery and to my astonisment the phone booted normally into the standard ROM.
WOW I was over the moon I have since installed my MIUI Rom and using my phone happily...
Thanks everyone for your input..
Click to expand...
Click to collapse
So it wasn't bricked...... glad you got it working.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
So it wasn't bricked...... glad you got it working.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Your lucky your bootloader was already unlocked. Once a phone gets borked like that unlocking the bootloader is impossible and Odin refuses to flash.
jboxer said:
Your lucky your bootloader was already unlocked. Once a phone gets borked like that unlocking the bootloader is impossible and Odin refuses to flash.
Click to expand...
Click to collapse
Dude.... stop spreading incorrect information. The bootloader state does not affect Odin. Please understand this!
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
Dude.... stop spreading incorrect information. The bootloader state does not affect Odin. Please understand this!
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes it does! Or at least on the phone I am trying to repair it has. On the phone I am trying to repair when you go into download mode you get a screen that says to unlock the bootloader. Odin connects and sends the file but then the phone refuses to flash it. If that is not the bootloader being locked affecting Odin then I don't know what is. I have flashed with Odin hundreds of times with Galaxy S phones so I know what I am doing. I have never seen Odin send a file, have the phone say it is verified and then refuse to flash it, but that is what is happening with this Nexus S with an unlockable bootloader. The files are the correct files and Odin is the correct version. If you are so smart, then you tell me what to do to get Odin to accept the flash and you will be my hero.
I have attached a shot of the phone in "download mode." Notice it is a warning about the bootloader being locked, not the normal screen with the Android bot and a shovel. Odin sees the phone (connected to computer as Samsung device) but once the phone verifies the file nothing else happens. The file is never flashed. Notice in the photo there is no YES and NO selections to unlock the bootloader like you get when you issue the "fastboot oem unlock" command. In Fastboot when that command is issued you get the normal unlock the bootloader screen but when you select YES and press Power nothing else happens. It just hangs no matter how long you leave it. A battery pull is the only thing you can do and when you turn the phone back on the bootloader is still locked.
If you are getting g stuck there you may have a hardware issue. I still think you need to try flashing through fastboot.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
If you are getting g stuck there you may have a hardware issue. I still think you need to try flashing through fastboot.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Cannot flash in fastboot. Sends over image then says fail due to bootloader being locked. If you have a signed update.zip with android-info and android-product files that can be flaahed in fastboot mode let me know where it can be downloaded from.
Sent from my LG-P999 using Tapatalk
Hi everybody
I've been so stupid
I tried to flash Jelly Bean to my nexus s,
I forgot to root, restarted, it didn't start, I went into stock recovery, deleted system by accident, now it won't boot anymore.
Can I do something about it or is it really dead?
Dennis
If the phone turns on and fastboot works then no it is not dead.Follow the instructions below to install CWM on your phone and then you can flash stock/custom rom using CWM.
If you have lost recovery then install pdanet on your computer.(It will also install Nexus S USB Drivers) then put your phone into fastboot mode by holding down both Volume Up and Power buttons together. When you are in fastboot mode connect your phone to your PC using USB cable.Download ADB and recovery you want to flash put it in your C:/recovery (Put adb and recovery image in this folder)
Then open cmd and type
1)CD C:/recovery
2)fastboot flash recovery recoveryname.img (replace recoveryname with actual file name of the recovery image).
You can download recovery from here
Or you can avoid all this and just use this
http://forum.xda-developers.com/showthread.php?t=1544940&highlight=recovery
Android-Junky said:
If the phone turns on and fastboot works then no it is not dead.Follow the instructions below to install CWM on your phone and then you can flash stock/custom rom using CWM.
If you have lost recovery then install pdanet on your computer.(It will also install Nexus S USB Drivers) then put your phone into fastboot mode by holding down both Volume Up and Power buttons together. When you are in fastboot mode connect your phone to your PC using USB cable.Download ADB and recovery you want to flash put it in your C:/recovery (Put adb and recovery image in this folder)
Then open cmd and type
1)CD C:/recovery
2)fastboot flash recovery recoveryname.img (replace recoveryname with actual file name of the recovery image).
You can download recovery from here
Or you can avoid all this and just use this
http://forum.xda-developers.com/showthread.php?t=1544940&highlight=recovery
Click to expand...
Click to collapse
Thank you for you reply. I have adb installed and it worked, but now my laptop won't recognize my device anymore:S
Denn77 said:
Hi everybody
I've been so stupid
I tried to flash Jelly Bean to my nexus s,
I forgot to root, restarted, it didn't start, I went into stock recovery, deleted system by accident, now it won't boot anymore.
Can I do something about it or is it really dead?
Dennis
Click to expand...
Click to collapse
Lol, forgot to root? That made me literally laugh out loud. Are you the same guy that posted this on Engadget.com? Some guy just explained on there of how he did the exact same thing...
Make sure you are running as admin on your computer. Right click on whatever program you are using and click "run as admin". That can solve most of the problems with your computer not recognizing the device. Good thing you messed up on the nexus. It's a pretty good phone for fixing newb mistakes.
Sent from my Galaxy Nexus using xda app-developers app
nikeman513 said:
Lol, forgot to root? That made me literally laugh out loud. Are you the same guy that posted this on Engadget.com? Some guy just explained on there of how he did the exact same thing...
Make sure you are running as admin on your computer. Right click on whatever program you are using and click "run as admin". That can solve most of the problems with your computer not recognizing the device. Good thing you messed up on the nexus. It's a pretty good phone for fixing newb mistakes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Well, i forgot to flash the root as I first wanted to see if Jelly Bean worked at all.. And it wasn't me on Engadget.com
I really really really hope I can fix it, as I don't want to lose my nexus s, it's a great phone!
If i can fix it, I'll be more carefull in the future
thanks for your replies!
PdaNet hangs on 'installing PdaNet to your phone'
Solved
He's alive again (My phone wasn't dead, I know)
Thank you so much!
Good! We learn from mistakes! Rooting is fun and has many benefits! Hard parts done, flash away!
Sent from my Galaxy Nexus using xda app-developers app
Having an issue flashing a custom recovery via fastboot. Everything is set up properly, fastboot commands work, but it keeps telling me that it cant open the recovery.img. Here is the error I am getting:
Daniels-MacBook-Pro:~ danielmasterson$ fastboot flash recovery openrecovery-twrp-2.6.3.2-hammerhead.img
error: cannot open 'openrecovery-twrp-2.6.3.2-hammerhead.img'
I am at a loss. I have had this set up this way since the Galaxy Nexus and it's never not worked. Any ideas?
if it's showing up when you search for fastboot devices, it may be the file. have you tried re-downloading it, renaming it, or even grabbing the 6.0.4.4 cwm img and flashing that? i'm curious.
xBeerdroiDx said:
if it's showing up when you search for fastboot devices, it may be the file. have you tried re-downloading it, renaming it, or even grabbing the 6.0.4.4 cwm img and flashing that? i'm curious.
Click to expand...
Click to collapse
Yes, I've redownloaded, renamed, tried CWM, etc. I'm totally buffaloed...
Sent from my Nexus 5 using Tapatalk
Hell, I unlocked the bootloader via fastboot so...
Sent from my Nexus 5 using Tapatalk
what is the ls -l of the .img file? Maybe a permission issue?
Typically I always rename my recovery images to 'recovery.img' thats the only thing I do differently than you on my mac. Second, where are you storing your recovery file before you flash it? External HDD? Check the permissions on the file/ the source drive.
also, did you update your SDK/adb?
Thanks for the replies guys. I'm still not sure what was going on, I nuked my whole ADB setup and started over again and all is well. Liking the N5 so far, it's really nice stock. May not eben jack with it too much, but I know I'll get the itch sooner or later...
A couple of things to try...
1) Make sure the recovery image is in the same directory where you installed fastboot and you are executing the terminal commands from that directory
2) Try adding ./ in front of the command so it would be ./fastboot flash recovery nameofrecovery.img
Sent from my Nexus 5 using xda app-developers app
chef_christoph said:
A couple of things to try...
1) Make sure the recovery image is in the same directory where you installed fastboot and you are executing the terminal commands from that directory
2) Try adding ./ in front of the command so it would be ./fastboot flash recovery nameofrecovery.img
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I got it worked out brother. What was strange though, is that I could fastboot flash a recovery on my Galaxy Nexus, but it wouldn't work on the N5, so I just re-did the setup and all is well...
0dBu said:
I got it worked out brother. What was strange though, is that I could fastboot flash a recovery on my Galaxy Nexus, but it wouldn't work on the N5, so I just re-did the setup and all is well...
Click to expand...
Click to collapse
I would think then you didn't update to the latest SDK/adb for N5.
0dBu said:
I got it worked out brother. What was strange though, is that I could fastboot flash a recovery on my Galaxy Nexus, but it wouldn't work on the N5, so I just re-did the setup and all is well...
Click to expand...
Click to collapse
Sorry, missed your post while I was typing mine. Glad to hear you got it working. Cheers!
Sent from my Nexus 5 using xda app-developers app
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