Database Develop

[Q] Need Help Flash Failure

Droid 3 Flash Failure
I assume it is possible to fix this problem but I can not find a solution despite extensive research. I have a Droid 3, XT862 experiencing:
AP Fastboot Flash Mode (S)(Flash Failure)
Every time I start the phone I get this message. I can get around it by using Power+M, going into Boot Mode Selection Menu and using Normal Powerup. I have Safestrap v1.08 installed and am able to run 5.6.890 as my safe ROM and Hash’s Cyanogen ICS and both ROM’s work great.
Having to go through these procedures is a pain. I have tried to SBF. I have attempted to flash using RSD Lite. All attempts fail. I would appreciate any help or even an explanation of what the problem may be. Thanks.

Hello
dowlnoad moto-fastboot
download swu.zip file
( moto-fastboot file and downloaded swu.zip file must be extracted to that same folder )
turn on phone by using power + vol down
and in CMD use a command
moto-fastboot flash preinstall preinstall.img
( you know, how to use a CMD in windows right ? )
after that reboot your phone all should be ok

You Give Me Too Much Credit
Thank you so very much for your help. I have moto-fastboot but have no idea where to obtain the swu.zip file. Any help would be appreciated. CMD in windows, what? Sorry, I am 62 years old, have no experience with this stuff. I thought I was doing well by rooting, strapping, and loading two ROMs. So if you could give me just a little more help here, I will kiss your avatar on the screen (which actually looks pretty hot!). Thanks.

Weird! Could you detail at which step RSD Lite failed to flash the ROM onto your phone? Normally, RSD Lite is the first to call when it comes to flash or unbrick Motorola phones. It's never failed me once since using on my Milestone.
Anyway, I don't know if you've read this instruction. This is pretty much foolproof. The link for the file is dead, you could try this to obtain it.
Good luck!

1. Download full system files from that link
http://www.multiupload.nl/PLYL79UDCC or from link what you got from blackbuddha
1a. make directory on C: and name it 1
2. extract this file to folder c:/1/
3. download moto-fastboot files
http://forum.xda-developers.com/attachment.php?attachmentid=635568&d=1308927194
end extract to C:/1/ where you have system droid3 system files
you must have moto-fastboot file and preinstall.img file in that same folder
( so you must check and if this both file is in diffrent folders please copy all to c:/1/)
4. click on start and in type CMD (and push enter)
5. in this black window ( CMD ) input cd/ (and push enter)
6. now type cd 1 (and push enter) you will go to folder 1
7.and now type moto-fastboot flash preinstall preinstall.img (and hit enter)
*** update ***
You must turn on phone with hold POWER + VOL DOWN buttons i forgot

niko99 said:
1. Download full system files from that link
http://www.multiupload.nl/PLYL79UDCC or from link what you got from blackbuddha
1a. make directory on C: and name it 1
2. extract this file to folder c:/1/
3. download moto-fastboot files
http://forum.xda-developers.com/attachment.php?attachmentid=635568&d=1308927194
end extract to C:/1/ where you have system droid3 system files
you must have moto-fastboot file and preinstall.img file in that same folder
( so you must check and if this both file is in diffrent folders please copy all to c:/1/)
4. click on start and in type CMD (and push enter)
5. in this black window ( CMD ) input cd/ (and push enter)
6. now type cd 1 (and push enter) you will go to folder 1
7.and now type moto-fastboot flash preinstall preinstall.img (and hit enter)
*** update ***
You must turn on phone with hold POWER + VOL DOWN buttons i forgot
Click to expand...
Click to collapse
I tried this but nothing happens after, phone stays in AP Fastboot Flash mode(S)
cmd did sending preinstall and writing okay twice.
Is the phone supposed to restart itself?
What next?

so no problem flash all files
with using a CMD and FAST-BOOT
moto-fastboot flash recovery recovery.img
moto-fastboot flash boot boot.img
moto-fastboot flash devtree device_tree.bin
moto-fastboot flash logo.bin logo.bin
moto-fastboot flash preinstall preinstall.img
moto-fastboot flash cdrom cdrom
moto-fastboot flash radio radio.img
moto-fastboot flash system system.img
and this should help for 100% to you

Still working on this
I, original poster, still working on this to solve problem. Have two Droid3s so I have time to work on it. Will try later today. Thanks.

Does Not work!! Lint in the blowhole?
OK, I have tried this cure multiple ways and it just does not work. I downloaded multiple copies of the files to be installed. I have used CMD as described above but it just does not "flash". When I add the command line in CMD my hard drive cranks and spins, loading the files to be flashed. Then I get <waiting for device>. I put the phone into AP Flashboot Phone battery is OK, and plug in the USB cable. I get Erasing "userdata"...OKAY [0.047s] and Erasing 'cache" ...OKAY [0.156s] CMD says Sending "recovery" <9216 KB>... and nothing. I have waited, and waited. There is just something that prevents the files from being flashed in. Any possible ideas? It is obviously connecting if it can erase, but it will not send.
When using RSD Lite, the phone is detected as Fastboot CDMA_Solana S. When I attempt to flash the SBF file it says: Failed flashing process. Unable to retrieve interface handle. [0x7027]; phone connected.

You also try to flash mbm.bin and mbmloader.bin finally or not ?
MBM.BIN
MBMLOADER.BIN
this two files must work
moto-fastboot flash mbm mbm.bin
moto-fastboot flash mbmloader mbmloader.bin
must work ! look if you have this both files in that same folder where is fast-boot.exe
if you dont have download from here
http://speedy.sh/gURdE/mbmloader.bin
http://speedy.sh/UHGVd/mbm.bin

Thanks again but no luck
Tried to flash just these two files and no luck. The same process as described above occurred, then it did not flash the files. I am about ready to give up and just put up with having to use two steps to start the phone.

Are you on one of the leaked OTA ROMs (.902, .905, or .906)?
I am on .905 and also have this same issue. Cannot flash anything with RSD Lite and I get the AP-FastBoot Flash Failed message everytime I reboot.
I think we need a new version of RSD Lite.
Sent from my DROID3 using xda premium

Maybe Tha's The Problem
Perhaps you have put your finger on the problem. I have .906 currently installed. I am using RSD Lite 5.6 which I assume, but do not know, is the latest version available. My only reservation in agreeing that this may be the problem is that I believe I had 5.6.890 installed when I bricked and tried to unbrick using Pete's unbricking script. Flash would not work. Later I recovered by installing .906 from recovery (I think) and then continued to be unable to flash. So it could be a .906 problem but maybe not.

Stuck while updating N1 to TexasICS.Phone not booting.

Hello All,
I am a noob and recently learned how to root, unlock or re-partition, install blackrose etc but using your blogs and wikicynogemod.
I am trying to update my phone to Texas ICS using blog by OP- http://forum.xda-developers.com/showthread.php?t=1366897
I was able to reach till the step mentioned below :
i.e.
fastboot flash hboot hboot_brcrust_220-10-206-ICS.nb0
fastboot reboot-bootloader
fastboot -w
and now my phone shows TexasICS on the second line that mans it flashed correctly.
I downloaded the tar file "Evervolv-Perdo-2.2.0a6" but I am clueless about the next steps.
1. To build Evervol --> How and where as repo command doesnt work on my computer undert android sdk directory
2. tar xjf --> I am using windows 7 and hence no tar on my laptop.Meanwhile I am downloading the zip file also and see if unzip works.
But I am curious where to run these commands- either on cmd prompt under android-sdk directory or the phone emulator.
And interestingly, android-sdk dont have unzip/tar command and I have no access to phone now, its not booting.
Also I cant login to my phone now, when I boot it, its stuck at the Nexus One startup logo, not going further, so I believe I can't put anything in the SD card now.
Kindly help as my phone is not accessible now and I am kind of handicapped because of that
FYI : Recently I upgraded the phone to 2.3.7 using Cynogenmod, clock recovery.

you might have lost ur recovery
so fastboot any preffered recovery.img . put .zip in sd and flash it
or you can fastboot system.img, boot.img n recovery.img
Sent from my Nexus One using Tapatalk

If you have a custom recovery like clockworkmod just turn on your device holding trackball or something (I don't remember exactly) and you'll be in recovery or fastboot. Anyway, go to recovery and restore your nand backup. After that you can keep trying (or read below).
If you don't have a backup you can insert the SD card directly into the computer and copy the Evervolv latest version (.ZIP). Then go to recovery and wipe data & cache then install the zip from sd card.
You don't need to pay attention to the building Evervolv part of the post as it's not needed for the install. Don't forget to flash gapps later if you want to.
Sorry for my English and I hope this helps as I'm a bit noob also
Sent from my GT-P7510 using xda app-developers app

flash recovery
Flash recovery by
booting in fastboot
fastboot flash recovery recoveryNAME.img
then reboot to recovery u will get recovery the flash ICS.zip rom

[HOW TO][Unlocked Bootloaders]Install Fastboots, CWM, Tips & Ticks, and More

Now that the bootloader is unlocked, everyone is asking "WTF do I do now?". Well, here's a bit of help to get you started. I'm assuming you already have adb and fastboot setup and working -- if not, quit reading and get that taken care of. Also, I only run Linux...so I'll try to be transparent and only list the fastboot commands.
I assume that you're not a complete moron and can Google what you don't understand.
Don't use the stock\SDK fastboot binary for flashing /system.
An updated fastboot binary for Lin\Win\Mac can be found here on the Batakang FTP from our local, neighborhood Mattlgroff.
Linux -- Rename the file to moto-fastboot and add it to a directory in your $PATH -- Ubuntu\Debian users can just add it to ~/bin (enabled by default)
Windows -- Rename the file to moto-fastboot and put it somewhere handy...that's on you to decide.
ROOT\ADMINISTRATOR INFO
On Linux, you might have to run as root in order to run some of the fastboot commands. If your system uses sudo for root commands, typing "sudo -i" will bring up an interactive sudo shell so you don't have to type sudo over and over again. If your system uses su for root, well, you already know the command.
On Windows, you have to enable Administrator Privileges to be able to run some of the fastboot commands.
Linux Terminal Hints
~/ means your home directory -- example -- "gedit ~/Documents/file.txt" would open file.txt in gedit easier than /home/yourusername/Documents/file.txt
You can add a * to file names and directories to not type as much -- example -- "gedit ~/Doc*/file.txt" is the same as the command above, only shortened. If two files have similar names, like Documents and Downloads, then you have to type the name up until the firs different character then add *.
Use the command "../" to go up\back one directory. The command is stackable so "../../" would go back 2 directories and so forth and so on.
Use "cd" to change directories. Is an example really needed for this...
Proper Apps to Use
For zip file editing, use 7-zip on Windows and Archive Manager (file-roller) on Linux
For editing text files on Windows use Notepad++ or any text editor that has unix line breaks -- do not use default Notepad or Wordpad -- you've been warned. Use what ever you prefer on Linux. I prefer Gedit myself.
Basic Fastboot Command Syntax
fastboot flash "partition" "image" -- flashes partition image where partition is where to write to and image is the path to the image being written.
example -- fastboot flash system /path/to/system.img
fastboot -w -- does a factory reset; to expedite things, "-w" can be added to "fastboot flash system system.img -w"
fastboot continue -- continue with the boot process
fastboot devices -- list devices fastboot recoginzes
fastboot -s "device model number" -- set the device fastboot will write commands to; use "fastboot devices" to find model number
fastboot reboot bootloader -- reboot phone into fastboot mode (or restart fastboot mode while in fastboot); same as "adb reboot bootloader"
fastboot help -- list all of this & more
Command Info
Not all the fastboot commands work for us. Specifically, the "erase" commands. If a wipe command doesn't work, skip it. I'll mark them with a ! at the end if it might fail.
Install CWM Recovery by Epinter
Read Epinter's RAZR HD CWM Thread
Download the recovery image
On stock rom, navigate to /system/etc and rename install-recovery.sh to install-recovery.sh.bak
Reboot into fastboot -- use "adb reboot bootloader" from Terminal\Command Prompt
Wipe the existing recovery -- "fastboot erase recovery" !
Flash the recovery with "fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img"
That's it, CWM is installed.
Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Install Stock Fastboots ICS
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img.ext4
fastboot erase cache !
fastboot -w
fastboot reboot
Install Alternate Radio
Reboot into fastboot
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
NON-HLOS.bin is found inside a fastboot zip.
Easy Kernel Install
Download kernel-flash.zip in the attachments[/URL]
Open the zip
Replace the zips current boot.img and device_tree.bin from the fastboot of your choice
Install the zip with CWM
By default, kernel-flash.zip comes with Mex Retail kernel and devtree
Easy CWM Install
Download recovery-flash.zip in the attachments[/URL]
Install the zip with CWM
Not sure if its SS compatible, but it is CWM compatible (for the lazy Photon Q users).
Obtain root after installing a Stock Firmware
There are two choices for obtaining root after a stock flash. the closed source SuperSu by Chainfire & and the open source Superuser by Koush.
Download SuperSu zip from Chainfire (Closed Source)
Download Superuser from Koush (Open Source)
Download the one of the root zips above.
Reboot into CWM/TWRP -- adb reboot recovery
Locate and flash the zip (see below for an alternative way)
Reboot, that's it. Nice not having to run exploits\hacks\Linux just for root
Install Rom/Zip file with ADB + CWM
CWM has the awesome ability to install zip files without having to manually copy them to the phone first. All's necessary is a PC with working adb.
Reboot into recovery
Select "install zip from sideload"
On PC, type "adb sideload /path/to/zip" and press enter
The zip will now be copied to the phone's cache & install
Once installed, do any requirements you'd normally do like wipe caches, etc

I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2

miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Unless you're not rooted with an unlocked BL, there's really no reason why it shouldn't work?
Sent from my N4'd Atrix HD

I was rooted before unlocking... shouldn't it still be rooted?
Sent from my MB886 using Tapatalk 2

miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Did you uninstall safestrap?

Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.

miketravis said:
Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.
Click to expand...
Click to collapse
Still did not work for me

Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2

miketravis said:
Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.

tvd0405 said:
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.
Click to expand...
Click to collapse
same here.

I have the same problem. I was able to flash cwm, uninstall the SS recovery, and uninstall the app. The first time I got the dead android symbol. I restored SS via Titanium Backup, reinstalled the SS recovery, and flashed cwm again. I tried rebooting into recovery and was able to get cwm working. As soon I uninstalled SS and rebooted, I got another dead android.

probably because were all on the XT926 if we were to revert back to XT925 then the recovery should work otherwise we will have to tweak the recovery to get it to work properly witht the XT926 software awesome thing is we can now free up the space that SS used for a rom slot however for noobs you might wana stick with SS once you hardbrick without anything to go back too it will be game over for your phone and then you have to con ATT for another

i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx

htchd2fix said:
i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx
Click to expand...
Click to collapse
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.

skeevy420 said:
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.
Click to expand...
Click to collapse
What's MR?

yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?

Markyzz said:
What's MR?
Click to expand...
Click to collapse
Mexican Retail
Install instructions in OP

htchd2fix said:
yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?
Click to expand...
Click to collapse
You won't lose root
And with an unlocked bootloader, all you gotta do is flash an updater zip with the su binary and app for Stock roms that don't have root
I'll link to a root zip in the op once I find one (or just make it; depends on how quick I find it in a search)

thanx again..
ahahahha...what a beautifullll day....

skeevy420 said:
Mexican Retail
Install instructions in OP
Click to expand...
Click to collapse
is there a point to flash a different firmware? is it required by any means?
I had SS and was backed up, I booted up the "stock ROM" and was successful in unlocking the BL and flashing CWM. I made a new backup of the stock ROM and restored it with success in CWM. In the video it show he has MR , but im confused as to why.
Also, I cant seem to get rid of safestrap....how in the hell do you uninstall it???

For those getting the not enough memory error while flashing the 5.0 Factory Image

THIS WILL FACTORY RESET YOUR DEVICE AND DELETE EVERYTHING
I unzipped everything in the factory image and the ZIP file inside the factory image and made this a batch file, and ran it...works great! Be sure to boot into the bootloader:
NOT MY FAULT IF YOU BREAK YOUR DEVICE THIS WILL WIPE IT CLEAN!
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.21.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot
You may need to boot into the bootloader again and wipe cache/factory rese or reset it from the phone settings itself.
Please put this script in the same folder as all the extracted files mentioned in the script above.
Script: https://www.dropbox.com/s/tfazy6rqamqpazo/flash-all-modified.bat?dl=0
Original Comment Below
http://forum.xda-developers.com/showpost.php?p=56700113&postcount=63
EDIT:
Edited script to remove the reboot bootloaders and also reboot the phone when it is done.

reinert012 said:
I unzipped everything in the factory image and the ZIP file inside the factory image and made this a batch file, and ran it...works great! Be sure to boot into the bootloader:
NOT MY FAULT IF YOU BREAK YOUR DEVICE THIS WILL WIPE IT CLEAN!
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.21.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
Script: https://www.dropbox.com/s/tfazy6rqamqpazo/flash-all-modified.bat?dl=0
Original Comment Below
http://forum.xda-developers.com/showpost.php?p=56700113&postcount=63
Click to expand...
Click to collapse
Is everyone who's getting this error on the 16gb model? Or are there people on the 32 gb model experiencing it as well?

cbowens said:
Is everyone who's getting this error on the 16gb model? Or are there people on the 32 gb model experiencing it as well?
Click to expand...
Click to collapse
I do not know, i'm on 16gb myself.

I was getting this error on my 32GB device
So I went ahead and did the flash commands
Now its showing my 32GB device is a 16GB device
Something bad happened

shoemocker said:
I was getting this error on my 32GB device
So I went ahead and did the flash commands
Now its showing my 32GB device is a 16GB device
Something bad happened
Click to expand...
Click to collapse
Boot recovery and factory reset?

reinert012 said:
I unzipped everything in the factory image and the ZIP file inside the factory image and made this a batch file, and ran it...works great! Be sure to boot into the bootloader:
NOT MY FAULT IF YOU BREAK YOUR DEVICE THIS WILL WIPE IT CLEAN!
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.21.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
You may need to boot into the bootloader again and wipe cache/factory reset.
Please put this script in the same folder as all the extracted files mentioned in the script above.
Script: https://www.dropbox.com/s/tfazy6rqamqpazo/flash-all-modified.bat?dl=0
Original Comment Below
http://forum.xda-developers.com/showpost.php?p=56700113&postcount=63
Click to expand...
Click to collapse
Worked for me on 16gb. Was getting error flashing system.img. Thanks!

reinert012 said:
Boot recovery and factory reset?
Click to expand...
Click to collapse
I just did a factory reset through the settings in the rom itself and that did the trick - thanks for your help

xmishka said:
Worked for me on 16gb. Was getting error flashing system.img. Thanks!
Click to expand...
Click to collapse
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
theretroandroid said:
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
Click to expand...
Click to collapse
So I just did a fastboot reboot after that. Phone is booting. Fingers crossed.
If it boots successfully, is there anything else that I need to do after that?

theretroandroid said:
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
Click to expand...
Click to collapse
Just use your volume keys on the phone so it says Start and then hit the power button or fastboot reboot via the cmd prompt.

theretroandroid said:
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
So I just did a fastboot reboot after that. Phone is booting. Fingers crossed.
If it boots successfully, is there anything else that I need to do after that?
Click to expand...
Click to collapse
Nope, just give it a few min to boot up all the way.

I m getting this error while flashing user data, mine is 32gb one
EDit- just did factory reset from recovery, now it works fine.
Damn you google , you a sec I thought my emmc has got corrupted

reinert012 said:
Nope, just give it a few min to boot up all the way.
Click to expand...
Click to collapse
It booted fine and is working. Setting it all up now. Thanks so much.

This thing didn't work for me at all it started the twrp then it got into bootloop with the twrp i dont know why

I just did a factory reset using the phones settings menu.
Sent from my Nexus 9 using Tapatalk

anshmiester78900 said:
This thing didn't work for me at all it started the twrp then it got into bootloop with the twrp i dont know why
Click to expand...
Click to collapse
Boot into bootloader and run the script again, make sure all the files are in the right place. I will run it again with TWRP installed and see what happens.

anshmiester78900 said:
This thing didn't work for me at all it started the twrp then it got into bootloop with the twrp i dont know why
Click to expand...
Click to collapse
I ran my script with TWRP installed and it worked perfect...please make sure ALL of the files in the script are in the same folder as the script.

reinert012 said:
I ran my script with TWRP installed and it worked perfect...please make sure ALL of the files in the script are in the same folder as the script.
Click to expand...
Click to collapse
I just flashed back to kitkat full stock
ALso now can you please be precise with the steps . Please . What files and where do i have to put them . Just confirming it from you as i got a bit confused with the first post

Er, mine also failed because of lack of memory, but it still booted up into lollipop. Should I reflash using your updated script?

anshmiester78900 said:
I just flashed back to kitkat full stock
ALso now can you please be precise with the steps . Please . What files and where do i have to put them . Just confirming it from you as i got a bit confused with the first post
Click to expand...
Click to collapse
1. Download the factory image from Google.
2. Extract those contents into your platform-tools folder wherever that is.
3. Go to the extracted folder, copy ALL the contents back to your platform-tools folder
4. Extract the contents from image-hammerhead-lrx21o.zip (this was in the extracted folder from step 2, which you copied in step 3) and make sure it's in the platform-tools folder again.
5. Make sure script is in the platform-tools folder too, and run it.
I just ran through this on my phone again....works fine.

reinert012 said:
1. Download the factory image from Google.
2. Extract those contents into your platform-tools folder wherever that is.
3. Go to the extracted folder, copy ALL the contents back to your platform-tools folder
4. Extract the contents from image-hammerhead-lrx21o.zip (this was in the extracted folder from step 2, which you copied in step 3) and make sure it's in the platform-tools folder again.
5. Make sure script is in the platform-tools folder too, and run it.
I just ran through this on my phone again....works fine.
Click to expand...
Click to collapse
Alright going to give it a try
---------- Post added at 05:54 AM ---------- Previous post was at 05:45 AM ----------
UPDATE:
Thanks a lot mate it worked . now my phone is booting up, I hope i dont get that problem where storage is reduced to half as i have 32gb model
anyways thanks a lot again
UPDATE 2:
my storage is reduced to 12.6 gb, how to fix this mate ?

[GUIDE] How to update to Android M-Preview-2 from V1 without loosing your data

If you are in M-preview-1 and don't want to lose your dat/apps you can follow this guide, after that, you'll havw M-preview-2 installed and a rooted device.
Firstly, you need to have a pc with adb working. There are several wyas to achive that, but I presume that if you are already in M preview V1, you have it.
Then, you need to have an unlocked bootloader, again I assume that you have it.
======Skip this is you have adb and unlocker bootloader===========
In any case, in linux there is a very trivial way to get both things (probably in windows and mac is more or less the same):
In a terminal:
sudo apt-get install android-tools*
Then plug your N5 to your computer with a usb cable (depuration mode enable), check that everything is working fine:
sudo adb devices
Then;
sudo adb reboot bootloader
sudo fastboot oem unlock
Then reboot
========================================================
Again, if you are not coming from M-preview-1 I do not recommend this method
1. Download M-preview-2 from this page.
2. Download twrp from here.
3. Create a folder, move twrp to that folder and extract M-preview-2 to the same folder (no sudir, all the files in the same folder), extract again image-hammerhead-MPZ79M.zip in the same folder.
4. Download Despair kernel in your device.
5. Download SuperSU beta 2.49 in your device.
Now, we are ready to flash everything:
6. Open a terminal and cd to the folder where you keep everything from previous steps.
7. Plug your device using a usb cable
8. Type the following commands in the terminal (if you are not in Linux, use the same commands but without "sudo"):
sudo device (just to check that adb ·see your device)
sudo adb reboot bootloader
sudo fastboot flash bootloader bootloader-hammerhead-HHZ12h.img
sudo fastboot flash boot boot.img
sudo fastboot flash radio radio-hammerhead-M8974A-2.0.50.2.26.img
sudo fastboot flash system system.img (this step takes a while)
sudo fastboot flash cache cache.img
sudo fastboot flash recovery twrp-2.8.7.1-hammerhead.img
9. Reboot in recovery (just using the vol up or down and the on buttom).
10. Flash Despair kernel
11. Flash SuperSU
12 Wipe Dalvik and cahe (just in case)
13. Reboot

Flashing over preview 1 won't bring additional issues?

migueldbr said:
Flashing over preview 1 won't bring additional issues?
Click to expand...
Click to collapse
Of course II'm still testing, but it seems that there is not new bugs (yet).

All I did was edit flash-all.sh, removed the '-w', then run it Anyone who has flashed the first version will already have the tools installed.
I wouldn't recommend using alternate kernels as they won't be designed for preview 2.

does your guys system app crash if you open data usage (set language to something except english) ?

tugler said:
does your guys system app crash if you open data usage (set language to something except english) ?
Click to expand...
Click to collapse
Yes

I just did a clean flash via fastboot manually. Booting now. I ain't got time for issues.

Is there a reason the OP links to TWRP 2.8.6.1 instead of the latest version (2.8.7.1)?

Anyone else having trouble flashing the despair kernel? I'm getting assert failed: getprop("ro.product.devices") (Status 7) when trying to flash. I tried sideloading and got the same errors followed by E: Error in /tmp/update.zip. Clearly I'm doing something wrong. Any ideas?

6spdsc4 said:
Anyone else having trouble flashing the despair kernel? I'm getting assert failed: getprop("ro.product.devices") (Status 7) when trying to flash. I tried sideloading and got the same errors followed by E: Error in /tmp/update.zip. Clearly I'm doing something wrong. Any ideas?
Click to expand...
Click to collapse
I'm still transferring my nandroid backup to my PC and haven't tried yet, but it's possible that the kernel won't flash on preview 2 because it's not yet updated for preview 2. As @TonyHoyle said, it's probably not a great idea to use one until they've specifically been updated for preview 2.

TonyHoyle said:
All I did was edit flash-all.sh, removed the '-w', then run it Anyone who has flashed the first version will already have the tools installed.
I wouldn't recommend using alternate kernels as they won't be designed for preview 2.
Click to expand...
Click to collapse
can u explain more detailed?

Flashable zip for multirom
flashable zip to use with multirom, please ?

As TonyHole suggested, just remove the -w; basically this will do: (you can do below on a command line as long as you are in the extracted TGZ file and in the hammerhead-MPZ79M folder/directory)
fastboot flash bootloader bootloader-hammerhead-HHZ12h.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-2.0.50.2.26.img
fastboot reboot-bootloader
fastboot update image-hammerhead-MPZ79M.zip
This works for me no issues as data is left intact but everything else is updated ; suggesting NOT to do this from an Android L to Android M Preview 2 and do a proper wipe
This will rebuild the ART app optimize on reboot
OP: Next time make a guide for doing STOCK update FIRST ; save the kernel and root for a SEPERATE post or a seperate section in the post

Hellscore kernel works great
Clean flash
I don't understand why any one would do a dirty dirty install with a preview no less
Sent from my Nexus 5 xda-dev app

The OTA is out and it will do the same process end result as the dirty flash method I did, keeps Data and app rebuild on reboot.

NPS_CA said:
The OTA is out and it will do the same process end result as the dirty flash method I did, keeps Data and app rebuild on reboot.
Click to expand...
Click to collapse
Do you have a link?
Sent from my Nexus 5

Is there zip file available
Sent from my Nexus 5 using XDA Premium 4 mobile app

thesebastian said:
Do you have a link?
Sent from my Nexus 5
Click to expand...
Click to collapse
Is this a real question?
Sent from my Nexus 5 using Tapatalk

Ben36 said:
Is this a real question?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah I was asking about the official OTA. Since only the link for Shamu was captured so far.
Sent from my Nexus 5

thesebastian said:
Yeah I was asking about the official OTA. Since only the link for Shamu was captured so far.
Sent from my Nexus 5
Click to expand...
Click to collapse
Surely if you go about phone. System update. Then you'll either have it or not if it's been pushed out to your device?
Sent from my Nexus 5 using Tapatalk