Related
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
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.
Hi.
I am about to RMA my phone and need to lock the bootloader..
BUT - I cant get into recovery.
I have tried everything, reverted to stock image (followed the thread how to return to stock image) , but no matter what, I cant boot into recovery.
I can get into the bootloader / fastboot , ie and run adb commands, but I cant boot into recovery.. its just flashed the google logo and then gets tuck there ..
Is there any way I can relock the bootloader given my predicament?
it's doing some other pretty weird stuff.. pretty sure the battery is near flat, but If I plug it in to charge, it flashes the charging logo and then about 10 seconds tries to boot,.. flashes the google logo and then about 1 second ofthe spinning colour circles.. then just black screen.. even if I go into the bootloader and hit power off..
If anyone has any Ideas I would love to know.
Does anyone know if google will RMA with an unlocked bootloader or am i screwed? This sucks!
1) you cannot run adb commands from fastboot. Adb commands only work in android or recovery
2) you just use fastboot commands from fastboot (bootloader). Accessing recovery is not part of the process
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
You lock the bootloader from the bootloader, but it sounds like you have lots of problems. I would just send it back if you can't lock it
Sent from my Nexus 5
Just boot into bootloader and run fastboot oem lock. No need to go to recovery for locking the bootloader. If you have flashed the stock images already the data was already wiped.
Sent from my Nexus 5 using Tapatalk
Why is there a whole thread about relocking the bootloader and a zip to flash via CWM (talking about resetting the tamper flag?)
http://forum.xda-developers.com/showthread.php?t=2513701
If I just do fastboot oem lock isn't Google going to be able to tell I have been flashing..?
llewelld said:
Why is there a whole thread about relocking the bootloader and a zip to flash via CWM (talking about resetting the tamper flag?)
http://forum.xda-developers.com/showthread.php?t=2513701
If I just do fastboot oem lock isn't Google going to be able to tell I have been flashing..?
Click to expand...
Click to collapse
If you have a custom recovery/ROM on the phone then of course they'll know what you've done! You have to flash the factory image and then relock the bootloader and you'll be OK
EddyOS said:
If you have a custom recovery/ROM on the phone then of course they'll know what you've done! You have to flash the factory image and then relock the bootloader and you'll be OK
Click to expand...
Click to collapse
Why don't use Bootunlocker? You can unlock/relock directly from the Nex5 without loss data and no wipe!!
I seriously doubt that they will check the tamper flag. Maybe sprint would, but I doubt that Google will. Just relock the bootloader and send it in bro. You'll be OK. I've sent nexus 7, nexus 4 both back with an unlocked bootloader and got my replacement no questions asked.
Sent from my Nexus 5 using Tapatalk
enzippo said:
Why don't use Bootunlocker? You can unlock/relock directly from the Nex5 without loss data and no wipe!!
Click to expand...
Click to collapse
because I cant boot. - cant get past the google logo so I cant run any apps..
llewelld said:
because I cant boot. - cant get past the google logo so I cant run any apps..
Click to expand...
Click to collapse
What about trying Wugfresh toolkit he has a setting in it for recovering from a none booting/softbricked device.
Download the factory images, unzip the file, while in the bootloader, click on flash-all.bat. when that's done, get back into the bootloader, and open a command window, and type fastboot oem lock. Now you are back to a stock phone.
Sent from my Nexus 5 using XDA Premium 4 mobile app
lyall29 said:
Download the factory images, unzip the file, while in the bootloader, click on flash-all.bat. when that's done, get back into the bootloader, and open a command window, and type fastboot oem lock. Now you are back to a stock phone.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks.. did all that... and have had to RMA the phone.. its screwed just died.. I think the first time I have had a phone just die that is so new and not from any soft of physical damage. Thanks!
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
Today I decided to try and put my Nexus 5 4.4.4 rooted phone back to stock. I unlocked the bootloader and then it would boot up to the 4 coloured orbs. I discovered that this is because of ClockworkMod Recovery (which is the reason I wanted to get a fresh install of 4.4.4). I went into clockworkmod and do the "wipe data / factory reset" but that didn't help. I think my USB debugging has since been turned off due to this.
I can boot my phone into the area with the menu for "Recovery" and "restart bootloader" and stuff like that. The bootloader is unlocked but when I run "flash-all.bat" it says "waiting for device".
Please help me! ):
PsykoP said:
Today I decided to try and put my Nexus 5 4.4.4 rooted phone back to stock. I unlocked the bootloader and then it would boot up to the 4 coloured orbs. I discovered that this is because of ClockworkMod Recovery (which is the reason I wanted to get a fresh install of 4.4.4). I went into clockworkmod and do the "wipe data / factory reset" but that didn't help. I think my USB debugging has since been turned off due to this.
I can boot my phone into the area with the menu for "Recovery" and "restart bootloader" and stuff like that. The bootloader is unlocked but when I run "flash-all.bat" it says "waiting for device".
Please help me! ):
Click to expand...
Click to collapse
Also when I use "fastboot devices" nothing comes up!!
PsykoP said:
Also when I use "fastboot devices" nothing comes up!!
Click to expand...
Click to collapse
Make sure your device is in Fastboot mode. When its in fastboot mode, then run the flash-all.bat
107bird107 said:
Make sure your device is in Fastboot mode. When its in fastboot mode, then run the flash-all.bat
Click to expand...
Click to collapse
I am. I don't think my PC can find the Nexus 5
PsykoP said:
I am. I don't think my PC can find the Nexus 5
Click to expand...
Click to collapse
Google 15 second adb install xda. That'll setup fastboot and the drivers you need. Then flash the factory image.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Google 15 second adb install xda. That'll setup fastboot and the drivers you need. Then flash the factory image.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thats what I am trying but I am having difficulty doing it :/
PsykoP said:
Thats what I am trying but I am having difficulty doing it :/
Click to expand...
Click to collapse
What is the difficulty?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
What is the difficulty?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not sure. I just tried it and it looked like it was working but it was stuck on "writing..." for ages after pressing any key to end because the .bat had finished.
I do now have stock recovery but it is just showing the open Android with the exclamation point .
Ohhh now it is booting back to the orb screen... I'll leave it for a few mins
Working now! I reflashed and it is working! ))))))))))))))
PsykoP said:
I'm not sure. I just tried it and it looked like it was working but it was stuck on "writing..." for ages after pressing any key to end because the .bat had finished.
I do now have stock recovery but it is just showing the open Android with the exclamation point .
Ohhh now it is booting back to the orb screen... I'll leave it for a few mins
Working now! I reflashed and it is working! ))))))))))))))
Click to expand...
Click to collapse
Great to hear!!!
Sent from my Nexus 5 using XDA Free mobile app