Related
hello,
i need help im stuck on Fastboot Reason Sticky bit factory _fastboot. i was flashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml through RSDlite 6.1.4 during flashing power went off and Pc got shutdown now im trying to flash it again but it gives me error and stuck here at fastboot Reason Sticky bit factory _fastboot
im attaching photo with it please need help its been 4 days im trying to flash it but not working :/
makov said:
hello,
i need help im stuck on Fastboot Reason Sticky bit factory _fastboot. i was flashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml through RSDlite 6.1.4 during flashing power went off and Pc got shutdown now im trying to flash it again but it gives me error and stuck here at fastboot Reason Sticky bit factory _fastboot
im attaching photo with it please need help its been 4 days im trying to flash it but not working :/
Click to expand...
Click to collapse
Besure u have installed fastboot on windows (if not, download and install from here)
Then open cmd
Then Type: fastboot oem fb_mode_clear
It will help to solve ur prob.
If you have unlocked bootloader, I recommend to use Myth Tools to flash firmware
devilsking said:
Besure u have installed fastboot on windows (if not, download and install from here)
Then open cmd
Then Type: fastboot oem fb_mode_clear
It will help to solve ur prob.
If you have unlocked bootloader, I recommend to use Myth Tools to flash firmware
Click to expand...
Click to collapse
after performing this command i've flashed the rom again with Myth tools. Motorola logo appear, it stay for a while then goes Blank! and restart.
makov said:
after performing this command i've flashed the rom again with Myth tools. Motorola logo appear, it stay for a while then goes Blank! and restart.
Click to expand...
Click to collapse
Did u try other fw?
Is your bootloader unlocked?
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
Is your bootloader unlocked?
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
yup bootloader is unlocked! still im not able to get back on stock ..
devilsking said:
Did u try other fw?
Click to expand...
Click to collapse
i guess this is the latest one that i've flashed? btw no i didnt yet, i am downloading 7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml.zip.
after flashing this what i get when flashing finish and it says
fastbootreason: Sticky bit fastboot
usb connected
sp space is not enough
makov said:
i guess this is the latest one that i've flashed? btw no i didnt yet, i am downloading 7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml.zip.
after flashing this what i get when flashing finish and it says
fastbootreason: Sticky bit fastboot
usb connected
sp space is not enough
Click to expand...
Click to collapse
So u want to go back to ICS?
devilsking said:
So u want to go back to ICS?
Click to expand...
Click to collapse
IM confused and dont know what to do ? :s
NEED GUIDANCE
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml.zip>>>>> This is ICS firmware.
I think u should try to flash JB firmware with our tools. Remember to ensure the free space on your hard disk.
After that, do what I said in 2nd post above if it still boot to fastboot mode.
devilsking said:
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml.zip>>>>> This is ICS firmware.
I think u should try to flash JB firmware with our tools. Remember to ensure the free space on your hard disk.
After that, do what I said in 2nd post above if it still boot to fastboot mode.
Click to expand...
Click to collapse
all done, fone has been flashed and its working but now i am getting Question mark error on the fone :s
makov said:
all done, fone has been flashed and its working but now i am getting Question mark error on the fone :s
Click to expand...
Click to collapse
Pul your simcard/sdcard then turn off phone. Then push them in and turn on. If it still has that error, reflash fw again. I have met that prob in the past
devilsking said:
Pul your simcard/sdcard then turn off phone. Then push them in and turn on. If it still has that error, reflash fw again. I have met that prob in the past
Click to expand...
Click to collapse
not working same question mark again n again :s flashed it twice but same thing is happening!
makov said:
not working same question mark again n again :s flashed it twice but same thing is happening!
Click to expand...
Click to collapse
U can try to flash Bell firmware
devilsking said:
Besure u have installed fastboot on windows (if not, download and install from here)
Then open cmd
Then Type: fastboot oem fb_mode_clear
It will help to solve ur prob.
If you have unlocked bootloader, I recommend to use Myth Tools to flash firmware
Click to expand...
Click to collapse
thanks friend
i had this problem on my razr hd and your command help me a solve my issue thanks
HOLY CRAP
devilsking said:
Besure u have installed fastboot on windowsf not, download and install from here[/URL])
Then open cmd
Then Type: fastboot oem fb_mode_clear
It will help to solve ur prob.
If you have unlocked bootloader, I recommend to use Myth Tools to flash firmware
Click to expand...
Click to collapse
You are a god
Saved my ass!
devilsking said:
Besure u have installed fastboot on windows (if not, download and install from here)
Then open cmd
Then Type: fastboot oem fb_mode_clear
It will help to solve ur prob.
If you have unlocked bootloader, I recommend to use Myth Tools to flash firmware
Click to expand...
Click to collapse
was doing stupid experiments on sister's phone, nearly bricked it. Thanks for this
devilsking said:
Besure u have installed fastboot on windows (if not, download and install from here)
Then open cmd
Then Type: fastboot oem fb_mode_clear
It will help to solve ur prob.
If you have unlocked bootloader, I recommend to use Myth Tools to flash firmware
Click to expand...
Click to collapse
Thanks so much its a just conformation i just executed this command and my phone is now can boot normally no need to flash again because i already flashed phone with tested firmware.
Thanks Mate
devilsking said:
Besure u have installed fastboot on windows (if not, download and install from here)
Then open cmd
Then Type: fastboot oem fb_mode_clear
It will help to solve ur prob.
If you have unlocked bootloader, I recommend to use Myth Tools to flash firmware
Click to expand...
Click to collapse
Although your reply was quite old, but it worked for me. Thank You
iamdofus said:
Although your reply was quite old, but it worked for me. Thank You
Click to expand...
Click to collapse
You're welcome I'm glad that it worked for you
i was recently rooted and successfully flashed the recovery through fastboot but when trying to run install the 4.4 update i get an error message during the install. i tried to completely wipe the device but im having a problem flashing the system.img. when trying to manually flash the system.img in fastboot on windows 8.1, i keep getting an error message where fastboot stops working. anyone know what to do?
try to use fastboot in win7 compatibility mode (right click -> properties -> compatiility)
waiflih said:
try to use fastboot in win7 compatibility mode (right click -> properties -> compatiility)
Click to expand...
Click to collapse
That stopped it from crashing but the flash fails. The phone says the package is too small
did you try with mfastboot? i really don't know what's the difference, but in other threads they suggest that. A link was posted in one of those threads:
https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit?usp=sharing
waiflih said:
did you try with mfastboot? i really don't know what's the difference, but in other threads they suggest that. A link was posted in one of those threads:
https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit?usp=sharing
Click to expand...
Click to collapse
Yea just got it from another thread and it worked. What is the difference with mfastboot? Edit: nm you stated you don't know.
Running the install for the update now hopefully it doesn't error
Edit: it worked thanks for your help
yw, i'm charging the phone to flash the vzw
I used mfastboot to flash system and boot, but when I tried flashing recovery I got the error preflash validation failed. Any help with that?
Jelps said:
I used mfastboot to flash system and boot, but when I tried flashing recovery I got the error preflash validation failed. Any help with that?
Click to expand...
Click to collapse
same. trying to flash it with mfastboot ended up with a failed flash for me and wouldn't boot. got it going again, but still without a recovery. hopefully somebody who has experienced this also comes along.
Tanknspank said:
same. trying to flash it with mfastboot ended up with a failed flash for me and wouldn't boot. got it going again, but still without a recovery. hopefully somebody who has experienced this also comes along.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2534438
so that's the problem you're having?
alex94kumar said:
http://forum.xda-developers.com/showthread.php?t=2534438
so that's the problem you're having?
Click to expand...
Click to collapse
not to that extent, no. My device works fine, I just can't reflash recovery to have the update pass through.
Tanknspank said:
not to that extent, no. My device works fine, I just can't reflash recovery to have the update pass through.
Click to expand...
Click to collapse
Worse comes to worse you could try RSD. That should restore recovery. Just make sure you RSD with the correct fastboot files (i.e. the ones that match the version you are running)
piccit said:
Worse comes to worse you could try RSD. That should restore recovery. Just make sure you RSD with the correct fastboot files (i.e. the ones that match the version you are running)
Click to expand...
Click to collapse
Tried, but couldn't get RSD to recognize my Moto X on Windows 8.1. I can access my X through fastboot, adb and storage but it will not show in RSD to save my life. Tried compatibility modes, older versions... just about everything short of another computer which I wont be able to try until my roommate gets back.
EDIT: I can honestly say that this worked, and with a combination of mfastboot and the recovery.img from the latest sbf, I'm updating along just fine. http://forum.xda-developers.com/showpost.php?p=47635914&postcount=10
Tanknspank said:
Tried, but couldn't get RSD to recognize my Moto X on Windows 8.1. I can access my X through fastboot, adb and storage but it will not show in RSD to save my life. Tried compatibility modes, older versions... just about everything short of another computer which I wont be able to try until my roommate gets back.
EDIT: I can honestly say that this worked, and with a combination of mfastboot and the recovery.img from the latest sbf, I'm updating along just fine. http://forum.xda-developers.com/showpost.php?p=47635914&postcount=10
Click to expand...
Click to collapse
If for some reason that doesn't work out this is what I did and was able to at least flash recovery. flash partition gpt.bin flash motoboot motoboot.IMG flash boot boot.img flash recovery recovery.IMG flash system system.IMG *not sure if motoboot is necessary. Still got an error trying to install though. First 410 and then 252. Ugh.
I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Raistlin1 said:
I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Click to expand...
Click to collapse
I would get into bootloader mode and reflash the system.img.
JulesJam said:
I would get into bootloader mode and reflash the system.img.
Click to expand...
Click to collapse
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
I even tried using someone's toolkit to return completely stock u rooted 4.4 but that doesn't work either.
Been reading tons of threads on here but can't seem to get it to flash.
Raistlin1 said:
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
Click to expand...
Click to collapse
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
JulesJam said:
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
Click to expand...
Click to collapse
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Raistlin1 said:
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Click to expand...
Click to collapse
I would try flashing the sparsechunks if you can't flash the single file image.
JulesJam said:
I would try flashing the sparsechunks if you can't flash the single file image.
Click to expand...
Click to collapse
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
I am really screwing myself, now while in bootloader and I try to boot or recovery I get failed to validate. Never had these problems flashing my N5, oh well.
Raistlin1 said:
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
Click to expand...
Click to collapse
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
JulesJam said:
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
Click to expand...
Click to collapse
I am getting bootloader failed to erase partition, failed remote failure.
MDM says phone is on latest version. mfastboot is the size you stated.
Raistlin1 said:
I am getting bootloader failed to erase partition, failed remote failure.
Click to expand...
Click to collapse
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
JulesJam said:
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
Click to expand...
Click to collapse
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Raistlin1 said:
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Click to expand...
Click to collapse
Can you reflash stock recovery?
Your bootloader is locked correct?
JulesJam said:
Can you reflash stock recovery?
Your bootloader is locked correct?
Click to expand...
Click to collapse
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Raistlin1 said:
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Click to expand...
Click to collapse
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
I am spent, going to bed and will pick up again tomorrow. Thanks for helping out.
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Raistlin1 said:
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Click to expand...
Click to collapse
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
JulesJam said:
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
Click to expand...
Click to collapse
As of now I can only get into fastboot mode, I don't believe the phone can even cycle through trying to boot any more. I tried rebooting from fastboot mode but there was an error and it failed.
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Raistlin1 said:
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Click to expand...
Click to collapse
http://www.graffixnyc.com/motox.php
JulesJam said:
http://www.graffixnyc.com/motox.php
Click to expand...
Click to collapse
Downloaded the 5.0 file from there, started flashing those files and it worked up until recovery, then I got the same bootloader message I was getting previously. Tried them over again and they all failed.
When in recovery adb devices starts the daemon and then says list of devices attached but I don't see anything after that.
I think it is fubar`d, going to have to file a warrant claim or use the moto care I purchased.
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