When i try to flash my factory image 5.0.1 on my nexus 5 (i got twrp recovery and DU rom) i got the message you will see in the picture... What shall i do? Thanks in advance.
Post a screenshot of your folder structure where the fastboot.exe and flash-all.bat are located. I guess you forgot to copy over the zip archive which contains the system.img / cache.img / userdata.img and so on.
experience7 said:
Post a screenshot of your folder structure where the fastboot.exe and flash-all.bat are located. I guess you forgot to copy over the zip archive which contains the system.img / cache.img / userdata.img and so on.
Click to expand...
Click to collapse
ok
Does the image-hammerhead zip file contain system.img file? If not you maybe got a corrupted download and have to d/l the factory image again...
experience7 said:
Does the image-hammerhead zip file contain system.img file? If not you maybe got a corrupted download and have to d/l the factory image again...
Click to expand...
Click to collapse
Yeah it does!..
Okay then try this:
1) Erase all partitions manually like this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
2) Then extract the content of the zip file and flash each img file manually like this:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
Bootloader and radio don't have to be flashed because they have - as I can see in your screenshot - successfully been flashed with the flash-all.bat.
experience7 said:
Okay then try this:
1) Erase all partitions manually like this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
2) Then extract the content of the zip file and flash each img file manually like this:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
Bootloader and radio don't have to be flashed because they have - as I can see in your screenshot - successfully been flashed with the flash-all.bat.
Click to expand...
Click to collapse
Does it need something like "fastboot reboot bootloader" after every command?
experience7 said:
Okay then try this:
1) Erase all partitions manually like this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
2) Then extract the content of the zip file and flash each img file manually like this:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
Bootloader and radio don't have to be flashed because they have - as I can see in your screenshot - successfully been flashed with the flash-all.bat.
Click to expand...
Click to collapse
i went to fastboot flash boot boot.img and im stuck on google logo
GiwrgosP- said:
Does it need something like "fastboot reboot bootloader" after every command?
Click to expand...
Click to collapse
Use this tutorial its helped me in past hope it will help you also>http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 Thanks to> @abaaaabbbb63
Mobile Solutions said:
Use this tutorial its helped me in past hope it will help you also>http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 Thanks to> @abaaaabbbb63
Click to expand...
Click to collapse
Thats what i did...
GiwrgosP- said:
Thats what i did...
Click to expand...
Click to collapse
Please explain what you did here? use 2nd method
What you did:
fastboot reboot bootloader
That's wrong. It's
fastboot reboot-bootloader
You only flashed stock kernel which is not compatible with DU ROM hence the bootloop.
Never mind. Just turn it off by holding power button. As soon as the screen is off also press vol down to boot in fastboot mode again.
Flash all the partitions like I said without reboot. After you've flashed all partitions type
fastboot reboot-bootloader
experience7 said:
What you did:
fastboot reboot bootloader
That's wrong. It's
fastboot reboot-bootloader
You only flashed stock kernel which is not compatible with DU ROM hence the bootloop.
Never mind. Just turn it off by holding power button. As soon as the screen is off also press vol down to boot in fastboot mode again.
Flash all the partitions like I said without reboot. After you've flashed all partitions type
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks doing it right now, hope it works. I will post soon
GiwrgosP- said:
Thanks doing it right now, hope it works. I will post soon
Click to expand...
Click to collapse
Thank you soooooooo much you helped a lot THANKS
No problem mate Don't hesitate to use the forums thanks button if a post was valuable and helpful
experience7 said:
No problem mate Don't hesitate to use the forums thanks button if a post was valuable and helpful
Click to expand...
Click to collapse
I have already done this
Related
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
You flashed the factory images?
bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
Do a data factory reset and wipe the cache both in recovery and reboot bro.
gee2012 said:
Do a data factory reset and wipe the cache both in recovery and reboot bro.
Click to expand...
Click to collapse
Thinking the same thing. But.. I can admit getting in a hurry and flashing the wrong image! :laugh:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?
bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
Click to expand...
Click to collapse
Long press the power button force it to reboot. As soon as the screen goes black hold down the volume down button. That will boot you into the bootloader, from there you can get to recovery. Factory reset, wipe cache.
You flashed stock recovery?
If you have stock recovery go to the bootloader like I said earlier. Choose recovery. Then you will see android laying down. Press volume up and power button at the same time. Do a factory reset.
bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?
Click to expand...
Click to collapse
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?
gee2012 said:
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?
Click to expand...
Click to collapse
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?
bobyum said:
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?
Click to expand...
Click to collapse
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt
maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk
gee2012 said:
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt
Click to expand...
Click to collapse
Unfortunately, it didnt help Still stuck at writing bootloader...
beaver2233 said:
maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yup, that might work better maybe
hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?
bobyum said:
hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?
Click to expand...
Click to collapse
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Thanks all for the help! Will try it tomorrow. Hopefully it works
wantabe said:
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Click to expand...
Click to collapse
I'd go one better and look to do a COMPLETE reflash - userdata and all! I'd also rename bootloader-hammerhead-hhz11k.img to bootloader.img and radio-hammerhead-m8974a-1.0.25.0.23.img to radio.img as it means there's less to get wrong! SO, to recap:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot format cache
I'd then boot into the stock recovery and perform a factory reset to make sure everything is in order and then reboot. I've done this exact method a number of times on my Nexus 5 and it works every time
EddyOS said:
I'd go one better and rename bootloader-hammerhead-hhz11k.img and radio-hammerhead-m8974a-1.0.25.0.23.img to just bootloader.img and radio.img to make it easier - less to type out and get wrong!
Click to expand...
Click to collapse
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!
wantabe said:
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!
Click to expand...
Click to collapse
As I hardly have any data to backup bar some custom ring tones I always reflash the userdata partition to be thorough. As for the reboots, I've just done it from habit, again just to be thorough. If it still doesn't work after that then it's goosed!
Try using the backup bootloader. Press and hold both volume buttons with the power button. That will take you into the backup bootloader.
Thanks to everyone for helping but I could not even get past writing the bootloader to the phone. I honestly think the flash storage and failed so will be RMAing. Hopefully they will accept it...
CM just posted a cm-11.0-XNPH25R-bacon-signed-fastboot.zip on the OPO homepage.
https://cyngn.com/products/oneplusone/
Can this be flashed via recovery?
donalgodon said:
CM just posted a cm-11.0-XNPH25R-bacon-signed-fastboot.zip on the OPO homepage.
https://cyngn.com/products/oneplusone/
Can this be flashed via recovery?
Click to expand...
Click to collapse
If you want to flash through recovery use the OTA link: http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed.zip
The link works, its just not published. Enjoy!
ddggttff3 said:
If you want to flash through recovery use the OTA link: http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed.zip
The link works, its just not published. Enjoy!
Click to expand...
Click to collapse
So, what can I do with the signed_fastboot.zip ?
4cop2c said:
So, what can I do with the signed_fastboot.zip ?
Click to expand...
Click to collapse
"signed_fastboot.zip" for fastboot mode.
i found something in flash-radio.sh (signed_fastboot.zip 's root-dir) ,maybe you're Into It Too.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
if you had 64g , be careful with userdata.img , try this in "recovery mode" choice "wipe media/data" that doing the same thing gets the almost same results.
kaiwater said:
"signed_fastboot.zip" for fastboot mode.
i found something in flash-radio.sh (signed_fastboot.zip 's root-dir) ,maybe you're Into It Too.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
if you had 64g , be careful with userdata.img , try this in "recovery mode" choice "wipe media/data" that doing the same thing gets the almost same results.
Click to expand...
Click to collapse
I am doing all this because i un-install busybox and lost root. Try root it again, but no hope.. so I have to reflash the whole things. Anyway, thanks! Following are the steps i do:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
reboot into recovery, wipe data and wipe user data
reboot to normal and following this to root again:
http://forum.xda-developers.com/showthread.php?t=2788632
No I have root again! Thanks!!
kaiwater said:
"signed_fastboot.zip" for fastboot mode.
i found something in flash-radio.sh (signed_fastboot.zip 's root-dir) ,maybe you're Into It Too.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
if you had 64g , be careful with userdata.img , try this in "recovery mode" choice "wipe media/data" that doing the same thing gets the almost same results.
Click to expand...
Click to collapse
Can you just do a
fastboot update </path/to/your/signed_fastboot.zip>
???
indesisiv said:
Can you just do a
fastboot update </path/to/your/signed_fastboot.zip>
???
Click to expand...
Click to collapse
Yea I was also wondering this? The only thing that is stopping me from trying it is the two different user data files. Does it automatically decide which one it should take?
Trying to install the 5.1 factory image and can't seem to escape bootloop. I can't even seem to get into recovery post flash to do a factory reset. It's funny, because if I flash TWRP instead of stock recovery i can get into TWRP. However, the file structure isn't built out at all when i mount from there. I flashed using the following method:
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
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase cache
Thoughts?
pearlbrian said:
Trying to install the 5.1 factory image and can't seem to escape bootloop. I can't even seem to get into recovery post flash to do a factory reset. It's funny, because if I flash TWRP instead of stock recovery i can get into TWRP. However, the file structure isn't built out at all when i mount from there. I flashed using the following method:
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
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase cache
Thoughts?
Click to expand...
Click to collapse
Can you get to bootloader? If so, just flash the stock image using the flash-all.bat
Unfortunately the flash all file never works for me. It hangs up after it flashes the radio. I was at least able to do a factory reset, during which several cache errors popped up. Maybe that is the root cause of the trouble?
pearlbrian said:
Trying to install the 5.1 factory image and can't seem to escape bootloop. I can't even seem to get into recovery post flash to do a factory reset. It's funny, because if I flash TWRP instead of stock recovery i can get into TWRP. However, the file structure isn't built out at all when i mount from there. I flashed using the following method:
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
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase cache
Thoughts?
Click to expand...
Click to collapse
You erased the cache after flashing it... System is checking for the cache and so the boot loop, try without erasing the cache(without executing the last line of code)
Hi, i have a nexus 5 rooted on stock android 5.1.1 . I am trying to flash the 5.1.1 factory image to unroot my device. But unfortunately i just get this message when its trying to flash the system.img and my device is now bricked
target reported max download size of 1073741824 bytes
load file:could not allocate 1073741824 bytes
error: cannot load 'system.img' : not enough space.
If someone could please help me with this i would be so greatful.
thank you
this is posted on the wrong section but i had this problem, i just went to
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and did the second method and it worked
ok thank you so much! are you sure it works?
stanleylam24 said:
this is posted on the wrong section but i had this problem, i just went to
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and did the second method and it worked
Click to expand...
Click to collapse
thanks so much are you sure this works?
I agree, this method works for me
yeah It works, I have this issue to every update now.
you need to extract the files in the zip and flash them one by one
fastboot flash bootloader bootloader-hammerhead-hhz12k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.27.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot
of course I don't flash userdata, I don't want to wipe my n5
Matrix_19 said:
yeah It works, I have this issue to every update now.
you need to extract the files in the zip and flash them one by one
fastboot flash bootloader bootloader-hammerhead-hhz12k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.27.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot
of course I don't flash userdata, I don't want to wipe my n5
Click to expand...
Click to collapse
ok thank you! im gonna try flash the 6.0 image, wish me luck!
stanleylam24 said:
this is posted on the wrong section but i had this problem, i just went to
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and did the second method and it worked
Click to expand...
Click to collapse
hi it didn't work, just shows this:
C:\Users\my name\Desktop\Minimal ADB and Fastboot>fastboot fla
sh system system.img
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
Matrix_19 said:
yeah It works, I have this issue to every update now.
you need to extract the files in the zip and flash them one by one
fastboot flash bootloader bootloader-hammerhead-hhz12k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.27.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot
of course I don't flash userdata, I don't want to wipe my n5
Click to expand...
Click to collapse
hi it didn't work, just shows this:
C:\Users\my name\Desktop\Minimal ADB and Fastboot>fastboot fla
sh system system.img
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
It could be the wrong system path, file name, folder name, cmd prompt not as admin. You have to have some sort of knowledge to figure out yourself. I had this problem but was able to fix it on my on. There are many factors that might cause this.
maybe try to find a more recent version of your ADB/Fastboot tools ? I've never had any issue manually
***EDIT*** platform-tool file outdated dag-nam-it... all fixed got mm installing as we speak thanks @Matrix_19 for the pointer :beer:
***EDIT "*** attached a.zip of platform-tools taken from the latest android-sdk
Hi,
i have nexus 5 that was something wrong with the WIFI (find nothing when was search) so , i did factory reset via the device and the problem still stays, so , i unlocked the bootloader via the android factory images webpage, than i installed the latest version with flash all file to the device.
than the device just show Google logo and nothing came up with it, than i tried lower version than the last one, and i got the same result, than i tried manually to enter the commandes and i got the same result,
where do i wrong that the system isn't up yet?
thank you
Hi:
I7210I said:
Hi,
i have nexus 5 that was something wrong with the WIFI (find nothing when was search) so , i did factory reset via the device and the problem still stays, so , i unlocked the bootloader via the android factory images webpage, than i installed the latest version with flash all file to the device.
Click to expand...
Click to collapse
You need this files (if using last factory image, hammerhead-m4b30z-factory-625c027b.zip):
boot.img
bootloader-hammerhead-hhz20h.img
cache.img
radio-hammerhead-m8974a-2.0.50.2.30.img
recovery.img
system.img
userdata.img
so unzip hammerhead-m4b30z-factory-625c027b.zip (factory image), the unzip
image-hammerhead-m4b30z.zip (located inside factory image) to get all files above
in the same folder and last but not least flashing (in fastbood mode):
type this (one line each time and press enter after each line)
fastboot flash bootloader bootloader-hammerhead-hhz20h.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.30.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img (this wipe your device.)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot.
That's all
Good luck
gsausalito said:
Hi:
You need this files (if using last factory image, hammerhead-m4b30z-factory-625c027b.zip):
boot.img
bootloader-hammerhead-hhz20h.img
cache.img
radio-hammerhead-m8974a-2.0.50.2.30.img
recovery.img
system.img
userdata.img
so unzip hammerhead-m4b30z-factory-625c027b.zip (factory image), the unzip
image-hammerhead-m4b30z.zip (located inside factory image) to get all files above
in the same folder and last but not least flashing (in fastbood mode):
type this (one line each time and press enter after each line)
fastboot flash bootloader bootloader-hammerhead-hhz20h.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.30.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img (this wipe your device.)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot.
That's all
Good luck
Click to expand...
Click to collapse
thnk you, i did it manually and i get the same result , what can be more? maybe the last 2-3 versions are making these thing?
Hi:
I7210I said:
thnk you, i did it manually and i get the same result , what can be more? maybe the last 2-3 versions are making these thing?
Click to expand...
Click to collapse
Did it fail or did it complete the process?
How long did you wait?
gsausalito said:
Hi:
Did it fail or did it complete the process?
How long did you wait?
Click to expand...
Click to collapse
now it come up, but the wifi isn't loaded, it search and find nothing even that there is at the room..maybe the hardware have problem?
Sent from my Pixel 2 XL using Tapatalk
Hi,
I7210I said:
now it come up, but the wifi isn't loaded, it search and find nothing even that there is at the room..maybe the hardware have problem?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Sorry, can't help. Never happened to me. It seems a hardware issue!