i know many of you probably know of wat my problem is and i thank everyone for their advice previously but non of the solutions given work
i keep on getting a boot.img error whenever i install a rom
i am getting so fustrated when installing any rom beside cm7 because that works but every other rom i try fails because of the boot.img
when i try it to install it through fastboot it gives me a error when ''writing'' boot.img into the phone
because i can see the fastboot screen (blue screen) it say ''writing boot: error out of space'' the system.img flashes perfectly
when i flash through recovery it always says ''error while flashing boot.img''
please help this is my last hope before going back to 2.1 again
thx in advance
have you tried
fastboot erase boot ?
Or enter recovery -> mount and storage -> format BOOT
and try to flash boot again.
pebe94 said:
have you tried
fastboot erase boot ?
Or enter recovery -> mount and storage -> format BOOT
and try to flash boot again.
Click to expand...
Click to collapse
ive done the first thing but im going to try the second one in recovery
thx
no that hasnt worked
it says this on the fastboot screen:
flash_write_image:bad block 390
flash_write_imageut of space
and it says this in cmd when i write command
sending boot OKAY
writing boot FAILED remote: flash write failure
mohnim said:
no that hasnt worked
it says this on the fastboot screen:
flash_write_image:bad block 390
flash_write_imageut of space
and it says this in cmd when i write command
sending boot OKAY
writing boot FAILED remote: flash write failure
Click to expand...
Click to collapse
Try flashing a fastboot KDZ again. (Use Mur4ik's 234 data one) Do it in CS_Emergency mode. Then go into fastboot and do the following:
fastboot erase boot
fastboot erase system
fastboot -w
fastboot flash recovery <name of recovery file>.img
fastboot reboot
Click to expand...
Click to collapse
Just a theory, not sure if it will work or not. Hope it works.
effortless. said:
Try flashing a fastboot KDZ again. (Use Mur4ik's 234 data one) Do it in CS_Emergency mode. Then go into fastboot and do the following:
Just a theory, not sure if it will work or not. Hope it works.
Click to expand...
Click to collapse
do you where i can get mur4ik's 234 data ?
mohnim said:
do you where i can get mur4ik's 234 data ?
Click to expand...
Click to collapse
Here: http://www.mediafire.com/?gxawu4ava7kt69x
(Thanks fishears for uploading)
effortless. said:
Here: http://www.mediafire.com/?gxawu4ava7kt69x
(Thanks fishears for uploading)
Click to expand...
Click to collapse
thx
i'll give it a try know
i installed mir4ik 234 data but know it's stuck on the lg logo
wat should i do?
This is normal. Flash custom rom now.
no it didnt work same problem
any other solutions
It's very strange, different devices have bad blocks in different places. For example, My GT540 has a bad block when erasing the data partition. My old, bricked, GT540 had a bad block on the system partition. It may be that the bad block ended up on your boot partition and may cause issues. Just a theory and its probably wrong, just guessing
effortless. said:
It's very strange, different devices have bad blocks in different places. For example, My GT540 has a bad block when erasing the data partition. My old, bricked, GT540 had a bad block on the system partition. It may be that the bad block ended up on your boot partition and may cause issues. Just a theory and its probably wrong, just guessing
Click to expand...
Click to collapse
do you know how to fix this bad block on boot partition
the wierd thing is that i never get this error when updating cm7 it works perfectly on that no error
another thing is that on the fastboot screen it say's
''flash write image: out of space''
how could it be out of space
where is the boot image stored inside the phone?
what size have desired boot.img ?
pebe94 said:
what size have desired boot.img ?
Click to expand...
Click to collapse
i have no idea
but i know the boot.img of cm7 works perfectly
maybe i need to be the same size as the cm7
Does the size of boot.img matter because in the fastboot screen it says ''flash write image: out of space ''
Sent from my GT540 using XDA App
What size is the boot.img?
Sent from my GT540 using XDA Premium App
eoghan2t7 said:
What size is the boot.img?
Sent from my GT540 using XDA Premium App
Click to expand...
Click to collapse
I think its 5kb
Sent from my GT540 using XDA App
I have the same problem!!
Expect I can flash through fastboot!!
anyone know a solution?
Sent from my GT540 using Tapatalk
androidboss7 said:
I have the same problem!!
Expect I can flash through fastboot!!
anyone know a solution?
Sent from my GT540 using Tapatalk
Click to expand...
Click to collapse
Have you tried
Fastboot erase boot
Fastboot flash boot boot.img
Sent from my GT540 using xda premium
Related
Phone won't boot post Image flash.
ericerk said:
Phone won't boot post Image flash.
Click to expand...
Click to collapse
what did you flash, and how? a bit more details are needed.
simms22 said:
what did you flash, and how? a bit more details are needed.
Click to expand...
Click to collapse
Nexus Developer images.
I've wiped cache, formated userdata.
It boots with an unlocked bootloader, but when you lock it it just bootloops.
ericerk said:
Nexus Developer images.
I've wiped cache, formated userdata.
It boots with an unlocked bootloader, but when you lock it it just bootloops.
Click to expand...
Click to collapse
odd.
simms22 said:
odd.
Click to expand...
Click to collapse
Yeah, I'm returning it today, and It's a problem if it won't boot...
ericerk said:
Yeah, I'm returning it today, and It's a problem if it won't boot...
Click to expand...
Click to collapse
have you tried reflashing?
simms22 said:
have you tried reflashing?
Click to expand...
Click to collapse
Multiple times.
Did you use the flash all.sh or flashall.bat? Cause that doesnt work! You need to flash the system images manually! Fastboot flash system system.img and so forth! Extract the images from the .zip
ericerk said:
Phone won't boot post Image flash.
Click to expand...
Click to collapse
Try using this tool, it saved me from bootloops, etc. Wug's Nexus Root Toolkit v1.9.9
drunkboi said:
Try using this tool, it saved me from bootloops, etc. Wug's Nexus Root Toolkit v1.9.9
Click to expand...
Click to collapse
I'll try that, though, I'm doing everything via commands that the toolkit would do.
ericerk said:
I'll try that, though, I'm doing everything via commands that the toolkit would do.
Click to expand...
Click to collapse
I see what you're saying... Well let us know if you have any success!
maddoggin said:
Did you use the flash all.sh or flashall.bat? Cause that doesnt work! You need to flash the system images manually! Fastboot flash system system.img and so forth! Extract the images from the .zip
Click to expand...
Click to collapse
I totally miss that post, yes, I manually flashed everything. Below is my "list"
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
sleep 5
#Name Radio...
fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
fastboot reboot-bootloader
sleep 5
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot format userdata
fastboot flash userdata userdata.img
fastboot reboot
Hello everybody. I'm having some problems flashing TWRP after unlocking the bootloader.
First of all, after unlocking the BL, I have flashed back the stock logo using
Code:
fastboot flash logo logo.bin
Then I tried flashing TWRP.
Code:
fastboot flash recovery recovery.img
Everything is successful, but booting to recovery from bootloader turns the phone off, and using
Code:
adb reboot recovery
brings about a 'dead android' screen with 'No command' written below it. I had to force reboot.
The phone itself works fine, and I was able to boot to TWRP, using the same .img file,
Code:
fastboot boot recovery.img
, and flash SU and whatever.
I don't really have a clue about what's going on here, can anybody point me in the right direction?
Thanks in advance
Nevermind, solved using TWRP manager app, and flashing the recovery from Android. Still don't know why I wasn't able to flash recovery from fastboot.
totalnoob34 said:
Nevermind, solved using TWRP manager app, and flashing the recovery from Android. Still don't know why I wasn't able to flash recovery from fastboot.
Click to expand...
Click to collapse
I think you should use mfastboot instead of fastboot
Sent from my XT1068 using XDA Free mobile app
ggunzio said:
I think you should use mfastboot instead of fastboot
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Mfastboot? I am using Linux, I think that it's for Windows only. Anyway, I don't think the problem is on computer side, since the commands were successful both on the pc and the phone.
ggunzio said:
I think you should use mfastboot instead of fastboot
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
I used fastboot for the same thing and it worked flawlessly.
Can anyone advise me off the fastboot command to save a copy of my recovery image before I flash the new one please.
Burtrum57 said:
Can anyone advise me off the fastboot command to save a copy of my recovery image before I flash the new one please.
Click to expand...
Click to collapse
You can't "pull" from fastboot. The protocol doesn't work like that sadly. What you can do though, is download a kernel from the forums here on xda and:
Flash recovery image to boot partition:
fastboot flash boot <recovery.img>
Battery pull (or reboot) and do a normal boot
It'll boot into recovery.
Backup recovery parition.
Reboot to fastboot
Flash kernel back:
fastboot flash boot <kernel boot.img>
Flash recovery to correct spot:
fastboot flash recovery <recovery.img>
Sent from my 0PCV1 using XDA Free mobile app
Many thanks for that. It worked and now I have CWM recovery. And the first thing I did with it was ???? Make a backup and save that on my computer for just in case!!
Something like this
Code:
dd if=/dev/block/mmcblk0p41 of=/mnt/media_rw/ext_sd/recovery.img
should do it.
Burtrum57 said:
Can anyone advise me off the fastboot command to save a copy of my recovery image before I flash the new one please.
Click to expand...
Click to collapse
Burtrum57 said:
Many thanks for that. It worked and now I have CWM recovery. And the first thing I did with it was ???? Make a backup and save that on my computer for just in case!!
Click to expand...
Click to collapse
do you have it on Desire 510 64 bit ?
how i can get it ?
https://dl.google.com/dl/android/aosp/hammerhead-lmy48b-factory-596bb9c1.tgz
md5sum: 2002e1b813921b1dfc67aca09c30a171
sha1sum: 596bb9c125525ce5baf4762a1cac6f5880c50cbc
I dint have access to take a look from here. I know there's an updated radio. Is there also an updated bootloader?
mikebeatrice said:
I dint have access to take a look from here. I know there's an updated radio. Is there also an updated bootloader?
Click to expand...
Click to collapse
Yes, from HHZ12f to HHZ12h.
I Tried to flash 5.1.1 without wipe (-w )
however I had the error "failed to allocate 1046266608 bytes".
So after flashing bootloader and radio,
I had to extract all .img and flash them one by one :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot
everything is working now ... I hope the damn memory leak bug is fixed.
Any new appearance or features?
Could you upload the new radio and bootloader? You could make something like this thread.
http://forum.xda-developers.com/goo...us5-update-bootloader-radio-lmy47d-5-t3052571
SA3DX said:
Could you upload the new radio and bootloader? You could make something like this thread.
http://forum.xda-developers.com/goo...us5-update-bootloader-radio-lmy47d-5-t3052571
Click to expand...
Click to collapse
You can download radio in this thread:
http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095
Matrix_19 said:
I Tried to flash 5.1.1 without wipe (-w )
however I had the error "failed to allocate 1046266608 bytes".
So after flashing bootloader and radio,
I had to extract all .img and flash them one by one :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot
everything is working now ... I hope the damn memory leak bug is fixed.
Click to expand...
Click to collapse
The ADB Error of failed to allocate X Bytes is easily resolved with a reboot of your computer.
mike102871 said:
Any new appearance or features?
Click to expand...
Click to collapse
Generally .1 releases fix bugs, so no, there is no new features or appearance
markdapimp said:
The ADB Error of failed to allocate X Bytes is easily resolved with a reboot of your computer.
Click to expand...
Click to collapse
Sadly in my case this didn´t work. Thanks anyway.
Regards
Android 5.1.1 factory image
I want to know the changelog in android 5.1.1 (LMY48B). is it fix memory leak? and what features added in this OTA?
markdapimp said:
The ADB Error of failed to allocate X Bytes is easily resolved with a reboot of your computer.
Click to expand...
Click to collapse
Matrix_19 said:
I Tried to flash 5.1.1 without wipe (-w )
however I had the error "failed to allocate 1046266608 bytes".
So after flashing bootloader and radio,
I had to extract all .img and flash them one by one :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot
everything is working now ... I hope the damn memory leak bug is fixed.
Click to expand...
Click to collapse
For me, this doesnt happen if i close CHROME and all other running programs and run fastboot as admin
for some reason even tho i have plenty of ram, i get that fail when chrome is open...i close that and fastboot does its thing fine
chaco81 said:
For me, this doesnt happen if i close CHROME and all other running programs and run fastboot as admin
for some reason even tho i have plenty of ram, i get that fail when chrome is open...i close that and fastboot does its thing fine
Click to expand...
Click to collapse
Good to know...
I'll try it next time
BiggerSpain said:
Sadly in my case this didn´t work. Thanks anyway.
Regards
Click to expand...
Click to collapse
Do you have the latest fastboot files?
xda6969 said:
Do you have the latest fastboot files?
Click to expand...
Click to collapse
I think so, but I flashed the system.img manually.
Thank you for your interest.
Regards
BiggerSpain
Same x bytes error for me on both a Win 8 PC and a Win 7 PC, Chrome open/closed doesn't matter. I finally flashed on a Linux machine. Took awhile to figure out Terminal, because this is the first time I've used Linux, but eventually got it right (I like a learning challenge). No problems with a Linux flash.
VivaErBetis said:
You can download radio in this thread:
http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095
Click to expand...
Click to collapse
I guess I wasn't clear enough. I want BOTH the new RADIO AND BOOTLOADER. Which part do you not understand?
SA3DX said:
I guess I wasn't clear enough. I want BOTH the new RADIO AND BOOTLOADER. Which part do you not understand?
Click to expand...
Click to collapse
Ho ho.....calm down Fury.....
Do you really believe that someone is willing to help you
when you write in this way???
krillehb said:
Ho ho.....calm down Fury.....
Do you really believe that someone is willing to help you
when you write in this way???
Click to expand...
Click to collapse
My thoughts exactly.
SA3DX If you download the factory image from google and unzip it everything is there. http://lmgtfy.com/?q=nexus+5+factory+images
SA3DX said:
I guess I wasn't clear enough. I want BOTH the new RADIO AND BOOTLOADER. Which part do you not understand?
Click to expand...
Click to collapse
Now Now stop having a tantrum
SENT BY ENTANGLEMENT
---------- Post added at 07:43 PM ---------- Previous post was at 07:28 PM ----------
Jamalleelee said:
My thoughts exactly.
SA3DX If you download the factory image from google and unzip it everything is there. http://lmgtfy.com/?q=nexus+5+factory+images
Click to expand...
Click to collapse
That link is so funny
SENT BY ENTANGLEMENT
i have been trying to flash the system.img manually and with the script. all i get is cant find the system.img and i get the wrong size reported back when trying to flash it. i am at a loss.. and my system has been erased so all i can do is boot into the bootloader....any help would be GREATLY appreciated...im so pissed i did this and have no phone right now..
thank you
FYI, Verizon N6 on 5.1 , unlocked, and rooted
dvigue said:
i have been trying to flash the system.img manually and with the script. all i get is cant find the system.img and i get the wrong size reported back when trying to flash it. i am at a loss.. and my system has been erased so all i can do is boot into the bootloader....any help would be GREATLY appreciated...im so pissed i did this and have no phone right now..
thank you
FYI, Verizon N6 on 5.1 , unlocked, and rooted
Click to expand...
Click to collapse
Flash all bat doesn't work. Did you unzip the second folder and find actual system.img. Then fastboot flash system system.img.
dvigue said:
i have been trying to flash the system.img manually and with the script. all i get is cant find the system.img and i get the wrong size reported back when trying to flash it. i am at a loss.. and my system has been erased so all i can do is boot into the bootloader....any help would be GREATLY appreciated...im so pissed i did this and have no phone right now..
thank you
FYI, Verizon N6 on 5.1 , unlocked, and rooted
Click to expand...
Click to collapse
dont use the flash-all script. flash each partition separately.
yes...i have tried it manaully..i keep getting "cannot find system.img" and my fastboot, adb and the .img files are all in the same folder... what the heck am i doing wrong...it also shows and i always get an "target allowed MAX download size of 536870912 when ever i try to flash system.img
dvigue said:
yes...i have tried it manaully..i keep getting "cannot find system.img" and my fastboot, adb and the .img files are all in the same folder... what the heck am i doing wrong...it also shows and i always get an "target allowed MAX download size of 536870912 when ever i try to flash system.img
Click to expand...
Click to collapse
Open command prompt. type fastboot flash system (drag and drop system img here)
I had this happen on my n5 with the first preview, honestly what worked for me(and really hate even recommending using toolkits) but NRT with force flash enable fixed it a flashed all files.
Again don't even know if n6 can use NRT but if it helps it helps lol
Sent from my Nexus 5 using XDA Free mobile app
todorcim said:
I had this happen on my n5 with the first preview, honestly what worked for me(and really hate even recommending using toolkits) but NRT with force flash enable fixed it a flashed all files.
Again don't even know if n6 can use NRT but if it helps it helps lol
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Shouldn't use toolkit till understand how it should work manually. Can get into trouble and not know how to fix.
ok..NRT worked!!!! yes...thank god...thanks for all your help
Here are all the manual commands.
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
fastboot flash radio {radio.img}
Step #2
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot format vendor {don't need for phone}
fastboot format cache
fastboot format userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot flash userdata {userdata.img}
fastboot reboot
prdog1 said:
Shouldn't use toolkit till understand how it should work manually. Can get into trouble and not know how to fix.
Click to expand...
Click to collapse
Yep totally agree, notice my brackets?
Good I'm glad it worked!!
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 08:23 AM ---------- Previous post was at 08:18 AM ----------
dvigue said:
ok..NRT worked!!!! yes...thank god...thanks for all your help
Click to expand...
Click to collapse
Don't rely on the toolkits tho, I personally think you need to know and understand the manual flash and Woking with adb/fastboot, I only used it because I spent a good hour trying every other possible fix to flash system (on both windows & Ubuntu).
But again I'm glad it work
Sent from my Nexus 5 using XDA Free mobile app