• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Mods [Guide]How to flash a Nexus Factory Image manually.

You can skip to step 11.

If you have custom recovery like CWM or TWRP then you can flash it directly on the phone.
 
I do all the tuto with the latest version but always the same thing .

the phone bootsto the animation but after nothing happen...

Rahhhhhhhhh :(
 
If you've completed all the steps without any error messages, when you reboot how long do you wait? Reflashing a phone will make it recompile all the stock apps into the cache. This could take up to 15 minutes. If it sits there only for a minute or two before you reboot, you might not be waiting long enough.

However, if you waited a while and it's still stuck, failure to boot could be an indication that you have a hardware failure somewhere.
 
den75 said:
Hummm thanks for your fast reply but I don't download this archive.

On your step lines you not mention that :/

I Have a Nexus 4

And the product name is MAKO
Bootloader version - MAKOZ30d
Click to expand...

Hi i'm getting error here in step 9 it says Failed <REMOTE: flash write failure>
here is my input fastboot flash bootloader bootloader-mako-makoz30d or fastboot flash bootloader bootloader-mako-makoz30d.img

please help me.
 
jrwild99 said:
Hi i'm getting error here in step 9 it says Failed <REMOTE: flash write failure>
here is my input
Code: 
fastboot flash bootloader bootloader-mako-makoz30d.img

please help me.
Click to expand...

If you get a flash write failure, then fastboot is finding the file and attempting to flash it, so your commands are correct. There could be a few things that could be interfering. First you could have a corrupt bootloader.img file. Try re-downloading it. Another possibility is that you have your phone connected to your PC through a USB 3.0 port. There has been some strangeness trying to flash using USB 3.0, so if possible use a USB 2.0 port. You might also try a different cable, although my Nexus phones have been nowhere near as fussy as my Samsung phones when it comes to cables.

Finally, it could be a hardware fault, but we won't go there, because that's "send it in for service" time.

Good Luck!
 
lunatic59 said:
If you get a flash write failure, then fastboot is finding the file and attempting to flash it, so your commands are correct. There could be a few things that could be interfering. First you could have a corrupt bootloader.img file. Try re-downloading it. Another possibility is that you have your phone connected to your PC through a USB 3.0 port. There has been some strangeness trying to flash using USB 3.0, so if possible use a USB 2.0 port. You might also try a different cable, although my Nexus phones have been nowhere near as fussy as my Samsung phones when it comes to cables.

Finally, it could be a hardware fault, but we won't go there, because that's "send it in for service" time.

Good Luck!
Click to expand...

Thank you for your fast reply...Currently I am using USB 2.0 port and I re-downloaded 3 times and used different cable and the error still persist. Please help me.
 
Hi jrwild99,

Are you able to flash any of the file systems (recovery, for instance) or do they all fail with the same error?
 
Assuming your phone is set properly (Like i said, if it finds the file and attempts to flash, then i would say it is.) The easiest method would be to use one of the toolkits to automate it for you. They might even be able to provide more detail on the error should it fail again.

Wug's toolkit.
Android Unified Toolkit.
 
codesplice said:
Hi jrwild99,

Are you able to flash any of the file systems (recovery, for instance) or do they all fail with the same error?
Click to expand...
Yes it is, I can't flash any files in my phone. what are the steps on how fixing my phone? please help

lunatic59 said:
Assuming your phone is set properly (Like i said, if it finds the file and attempts to flash, then i would say it is.) The easiest method would be to use one of the toolkits to automate it for you. They might even be able to provide more detail on the error should it fail again.

Wug's toolkit.
Android Unified Toolkit.
Click to expand...
ok thnx I will try these tools, thank you so much will update here once I have the output.
 
If it's failing to flash everything, it means your bootloader is still locked, or there's some sort of hardware issue.
 
jhawkkw said:
If it's failing to flash everything, it means your bootloader is still locked, or there's some sort of hardware issue.
Click to expand...

If the bootloader were locked, wouldn't it fail to *begin* the flash process? I take it the flash process starts but fails to complete. :dontknow:

I was hoping it wasn't going to be a hardware issue. :o
 
jhawkkw said:
If it's failing to flash everything, it means your bootloader is still locked, or there's some sort of hardware issue.
Click to expand...
My phone is already unlocked when im trying to flash the bootloader.

lunatic59 said:
If the bootloader were locked, wouldn't it fail to *begin* the flash process? I take it the flash process starts but fails to complete. :dontknow:

I was hoping it wasn't going to be a hardware issue. :o
Click to expand...
My observation is when I use the fastbood oem unlocked then restart bootloader it will go back to locked mode. How to fix this issue?
 
When you put your phone into fastboot mode you should see this ...

android-fastboot-bootloader-screenshot.png


If it says "locked" then your bootloader in not unlocked and flashing will fail. The proper command is
Code: 
fastboot oem unlock
 
lunatic59 said:
When you put your phone into fastboot mode you should see this ...

android-fastboot-bootloader-screenshot.png


If it says "locked" then your bootloader in not unlocked and flashing will fail. The proper command is
Code: 
fastboot oem unlock
Click to expand...
My steps are correct but when I am trying to flash the bootloader it keeps failing to flash... I done it correctly from Step 1 to step 8 and failed to step 9.
 
Try repeating step 8 and then try one of the toolkits to flash the stock bootloader. They will get the files from known repositories. If it still fails to flash at this point, I can only assume there is something wrong with your hardware.
 
nexus 4, tried to revert to stock. but for some reason failed at step 11, couldn't flash the system bundle, so i extracted it and flashed them one by one, system-boot- recovery, the cache.img was missing as well as userdata.img, so i skipped these steps and rebooted unfortunately didn't go past the animation logo. booted into recovery the laying little android was there nothing else no options. waiting for any suggestions. thanks.
 
i found userdata image but no cache image . can someone plz tell where to get it. and why it always fails at step 11, it says error: failed to load "image': no error.
i erased everything and did it over with same outcome stuck in boot animation.
i did everything as written in tuto. really driving me nuts. any help!!!

reedit: i got it!!!
for those confronted with the same problem, after flashing system, boot and recovery enter the command: "fastboot format cache", instead of flash cache.img. then reboot, worked like a charm.
 
Things have gone horribly wrong for me. When I got to step 9, it didn't flash the new bootloader and now I think I have a brick. Nexus won't start, i keep seeing booting failed error.
Please help, i am new too this so not sure what to do and don't want to make things worse.
Thanks.
 
The latest Lollipop from the Google Nexus Factory Images have included a bat file for windows installs and a couple of Linux shell scripts one installs all and the other just the base. Now all you really have to do is extract the download hook up the device and run the script. (Make sure you are root / admin on the computer as some systems require it)
 
argedion said:
The latest Lollipop from the Google Nexus Factory Images have included a bat file for windows installs and a couple of Linux shell scripts one installs all and the other just the base. Now all you really have to do is extract the download hook up the device and run the script. (Make sure you are root / admin on the computer as some systems require it)
Click to expand...
Protip: there's a line in the flash-all.bat script (or the *nix equivalent) that includes fastboot update -w somethingsomething.zip. That "-w" means "wipe". You can edit the script to just remove the "-w" if you don't want to fully erase the userdata (/data) partition (so fastboot update somethingsomething.zip instead). :thumbsupdroid:
 
codesplice said:
Protip: there's a line in the flash-all.bat script (or the *nix equivalent) that includes fastboot update -w somethingsomething.zip. That "-w" means "wipe". You can edit the script to just remove the "-w" if you don't want to fully erase the userdata (/data) partition (so fastboot update somethingsomething.zip instead). :thumbsupdroid:
Click to expand...
good catch I didn't think of that I just do it anymore lol
 
codesplice said:
Protip: there's a line in the flash-all.bat script (or the *nix equivalent) that includes fastboot update -w somethingsomething.zip. That "-w" means "wipe". You can edit the script to just remove the "-w" if you don't want to fully erase the userdata (/data) partition (so fastboot update somethingsomething.zip instead). :thumbsupdroid:
Click to expand...

Does the Flash-All method for Lollipop bypass all of the steps you posted?

https://developers.google.com/android/nexus/images
 
You must log in or register to reply here.
Back
Top Bottom