{HOW TO REQUEST} Enabling fastboot, Prerequisites to getting the leaked OTA, etc. - Motorola Droid 4

Hey all,
Like the title says, i'm requesting a HOWTO on this fastboot business. There are a mess of links and pages out there and it would be extremely helpful if someone posted the "XDA-Approved" step-by-step links in the order of which they should be done in order to obtain fastboot and then obtain the ICS Leak. Thanks! And I apologize in advanced for my inexperience

First off, fastboot is for reporting your phone to stock. You should be able to fastboot from gingerbread if you can't seem to get the OTA installed, but I haven't tested it.
I'm out and about now, but can throw together something quick...
Before following this guide, be sure the battery is more than 60% charged. Fastboot don't allow flashing on batteries lower than 50%, and if you mess up the instructions you might need to do it a couple times.
1) download and install latest Motorola drivers
2) find a copy of RSDlite 5.7
3) download the latest fastboot file for the Droid4 from sbf.droid-developers.com and extract the files
4) turn off phone and hold vol+ and vol- when posting back up
5) boot menu will appear, use vol- and highlight AP fastboot, then press vol+
6) connect phone to pc
7) open rsdlite, select xml file to fastboot, then press okay
Good luck!
Sent from my Nexus 7 using Tapatalk 2

danifunker said:
First off, fastboot is for reporting your phone to stock. You should be able to fastboot from gingerbread if you can't seem to get the OTA installed, but I haven't tested it.
I'm out and about now, but can throw together something quick...
Before following this guide, be sure the battery is more than 60% charged. Fastboot don't allow flashing on batteries lower than 50%, and if you mess up the instructions you might need to do it a couple times.
1) download and install latest Motorola drivers
2) find a copy of RSDlite 5.7
3) download the latest fastboot file for the Droid4 from sbf.droid-developers.com and extract the files
4) turn off phone and hold vol+ and vol- when posting back up
5) boot menu will appear, use vol- and highlight AP fastboot, then press vol+
6) connect phone to pc
7) open rsdlite, select xml file to fastboot, then press okay
Good luck!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks! So after this we should be able to run ClockWork

No, after the fastboot you need to root then install safestrap 2.0 for d4
Sent from my Nexus 7 using Tapatalk 2

So I'm new to Motorola devices and am not familiar with RSDlite, but it looks like its just a program that gives all the fastboot commands a GUI. Is this right?
Sent from my DROID4 using Tapatalk 2

teookie said:
So I'm new to Motorola devices and am not familiar with RSDlite, but it looks like its just a program that gives all the fastboot commands a GUI. Is this right?
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Mostly correct. There is a special moto-fastboot program that is used to flash the partitions. I think it utilizes that program somewhere beneath the GUI.

Does Droid 4 still have that root counter?
I was still under the impression that there was some type of root counter, like 0/0 to 0/1 if you root once which would void the warranty?
Also, is there a SBF one click or do we still need to use rsdlite 5.7? That was soooo nice with the droid 3, the apfastboot one click.
Does anyone know if either of these issues are being worked on?...
Thank you in advance..

Related

25$ if u unbrick my phone

I will donate to the individual that unbricks my bionic...Plz a lil desperate!!
Hmm.. Maybe some more info. What were you doing when you bricked it? Any of the leaked updates installed?
djr4x4 said:
Hmm.. Maybe some more info. What were you doing when you bricked it? Any of the leaked updates installed?
Click to expand...
Click to collapse
i was back on 886 with updated kernel and radio. wanted to flash the ota but kept failing due to kernel. tried flashing the ota in stock recovery then in cwm to no avail. decided to format somethings in advanced just to see if it would help flash ota but no. after that i rebooted and bam! bricked. thing is i have been in this situatuation before and nothing would restore me except released and 4ever root but now nothing works. no phone going on 24 hours now...
Did the same thing. Used this method. if you can get to the fast boot by holding power and vol down (or power and volume up and down, then selecting fast boot) it will work
http://www.addictivetips.com/mobile/unbrick-motorola-droid-bionic-with-rsd-lite-5-5-guide/
netslum said:
Did the same thing. Used this method. if you can get to the fast boot by holding power and vol down (or power and volume up and down, then selecting fast boot) it will work
http://www.addictivetips.com/mobile/unbrick-motorola-droid-bionic-with-rsd-lite-5-5-guide/
Click to expand...
Click to collapse
rsd didnt work for me ever...i want to try it again but it says that the file is not supported...
got it but still a no go. it fails everytime right away
Is there anyway to flash the fxz file without rsd??maybe fastboot??but it needs to be in IMG format right? anybody?
You can flash individual files from that pacjage in fastboot. Try this.
Fastboot flash /system system.img
Make sure those files are in same folder as fastboot, you have the right drivers and ur in fastboot mode on phone. Do this for every file it will let u. keep ur money tho if this works im not on this forim to get paid. Worse comes to worse pm me a phone number and ill step u thru it over phone.
Sent from my DROID BIONIC using XDA App
Here's some general tips for making RSD Lite work for you. RSD Lite is the only tool that knows how to manipulate FXZ files, as it's Motorola's proprietary file format.
(1) All the files you should need (Either RSD Lite or Fastboot) will come from here: http://briefmobile.com/droid-bionic-receives-fastboot-recovery-files
(2) Running the 32-bit version of the Motorola drivers is recommended. RSD Lite is a native 32-bit app and has a better chance of playing nice if 32-bit Motorola drivers are installed.
(3) When running RSD Lite on Windows Vista or Windows 7, it is also recommended that when you open it that you right-click and choose "Run As Administrator".
(4) After installing the drivers and RSD Lite, reboot and then plug in your Bionic AFTER opening RSD Lite.
From there, you make sure that you start your Bionic in bootloader (aka fastboot) mode and then RSD Lite shouldn't have a problem detecting the device so you can flash in the FXZ file. The best version to use in your situation is the full one that's 685MB.
This is what you need. I personally don't use rsdlite.
http://forum.xda-developers.com/showthread.php?t=1279825
You will boot your phone into fastboot mode then flash it using this utility. Option 1 is what you need to use.
You can also try this: http://droidmodderx.com/bionic/too-easy-unbrick-bionic-with-oneclick-fastboot-restore/
Sent from my DROID BIONIC using Tapatalk
Remember to hit the "Thanks" button when someone helps you!
Terri M said:
You can also try this: http://droidmodderx.com/bionic/too-easy-unbrick-bionic-with-oneclick-fastboot-restore/
Sent from my DROID BIONIC using Tapatalk
Remember to hit the "Thanks" button when someone helps you!
Click to expand...
Click to collapse
i have tried all of those and still no luck. all i can think of is to flash the whole fxz file in fastboot. but it needs to be in .IMG format.
follow the steps in the first post of this thread. should get you back going.
http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html
rgb2448 said:
follow the steps in the first post of this thread. should get you back going.
http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html
Click to expand...
Click to collapse
did this multiple times but heck ill try it again...
brandonaspencer said:
did this multiple times but heck ill try it again...
Click to expand...
Click to collapse
Can you get in fastboot mode? Does it say flash failed? What did you format?
i tried to flash the ota. no go. formatted webtop. stuck in ap mode. says flash failure. at the bottom says invalid sp data and invalid cg webtop. wont flash anything...
You need to use the moto-fastboot.exe and flash the stock webtop partition back to your phone. That is a hacked version of fastboot that supports larger than 256MB partition sizes and will restore your webtop so the phone can boot.
You finally gave enough information about what you actually deleted/formatted and the exact error was so that you could be helped...congrats!
Hint: "moto-fastboot flash webtop grfs.img" from a directory that contains the moto-fastboot.exe and the 2 required .dll files and the grfs.img from the original FXZ.
cellzealot said:
You need to use the moto-fastboot.exe and flash the stock webtop partition back to your phone. That is a hacked version of fastboot that supports larger than 256MB partition sizes and will restore your webtop so the phone can boot.
You finally gave enough information about what you actually deleted/formatted and the exact error was so that you could be helped...congrats!
Hint: "moto-fastboot flash webtop grfs.img" from a directory that contains the moto-fastboot.exe and the 2 required .dll files and the grfs.img from the original FXZ.
Click to expand...
Click to collapse
THank you!
http://dl.dropbox.com/u/7632904/moto-fastboot-win32.zip
That is the moto-fastboot.exe and dll files you need.
I already gave you the syntax to use it above and you already have the FXZ so just put them all together in a folder with the grfs.img and navigate to that folder from command prompt once the phone is booted in fastboot mode and use the command above.
It will proceed to flash the grfs.img in 5 256MB chunks and a 6th smaller chunk and then use moto-fastboot reboot and it should boot normally if you haven't messed up anything else in the meantime.
Good luck!
cellzealot said:
http://dl.dropbox.com/u/7632904/moto-fastboot-win32.zip
That is the moto-fastboot.exe and dll files you need.
I already gave you the syntax to use it above and you already have the FXZ so just put them all together in a folder with the grfs.img and navigate to that folder from command prompt once the phone is booted in fastboot mode and use the command above.
It will proceed to flash the grfs.img in 5 256MB chunks and a 6th smaller chunk and then use moto-fastboot reboot and it should boot normally if you haven't messed up anything else in the meantime.
Good luck!
Click to expand...
Click to collapse
Sir you are a genuis and a scholar! you know there are two different fastboot recoveries?? I needed exactly what you said, so where can I send you the $25?
brandonaspencer said:
Sir you are a genuis and a scholar! you know there are two different fastboot recoveries?? I needed exactly what you said, so where can I send you the $25?
Click to expand...
Click to collapse
Keep it! Learn how to ask better questions with more complete information and tell everyone else to do likewise and you will save us all far more valuable time and effort...seriously.
Happy holidays!
Oh and also share the knowledge you get with others and use the thanks button...it's what this forum is for.
Thanks for the offer, but I'd really rather you just did as I suggested and enjoy your phone and learn to understand it better.
Win, win!
I slept in late or I would have answered, but Cellzealot definitely explained it well.

Need Boot Help

I have two droid 3's and I rooted them both and went to install a blue theme on one of them from the rom manager app and it worked great, so I did it on my second one, too. When it was in the reboot process it never finished bootoing and it stopped at the red M. All it shows is the boot logo, not the boot animation. I have tried flashing it with rsd lite, but it always fails. Is there any other ideas as to what I should do?
You need to get rsdlite working(does it work on the other phone?). Get the drivers installed from motohelper (or reinstall) if needed, get the phone into ap fastboot and sbf to stock and go from there. Check this thread on users with the same issue.
Willis111 said:
You need to get rsdlite working(does it work on the other phone?). Get the drivers installed from motohelper (or reinstall) if needed, get the phone into ap fastboot and sbf to stock and go from there.
Click to expand...
Click to collapse
Yes, the theme works on the other phone. I will get the drivers and try again and will get back to you. Thanks for the help so far.
RaTTeDH said:
Yes, the theme works on the other phone. I will get the drivers and try again and will get back to you. Thanks for the help so far.
Click to expand...
Click to collapse
I meant rsdlite, have you ever used it with either phone without having an issue? I edited my previous post, added a link you might want to check out.
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
http://minus.com/mB0zknQrL/
I have never used RSDLite before. So I do not know if it works. But when I am flashing it with the stock 5.6.890 it fails at step 5. It reboots the bootloader. But it fails always at step 5. Let me try the other replys...
redsox985 said:
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
Click to expand...
Click to collapse
I have downloaded this and tried this. When I run the application moto.fastboot.exe it takes like 30 seconds and when I run the batcch file it immediately finishes and says moto fastboot is not recognized as an internal or external command, operable file or command. And finishes immediately. Sigh.
redsox985 said:
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
http://minus.com/mB0zknQrL/
Click to expand...
Click to collapse
The unbrick script will flash a vzw rom to your xt860 and have you stuck at the M logo anyways so I wouldn't suggest trying that. If you haven't used rsdlite before and are having trouble with it now you probably need to install the drivers from the motohelper software.
1./ download the drivers (from motorola)
2./ shutdown phone and turn it on by hold m + power
3./ select ap fastboot mode, enter and plug your phone into the computer ignoring any add new hardware
4./ start the driver install and follow it through
5./ unplug and replug your phone with computer leaving it fastboot mode.
Rsdlite should show your device under listed devices when you start it up at this point and allow you to flash w/e rom. I would suggest using the iucell or brazil retail fastboot files from the xt860 fastboot thread to get your phone up.
I fixed it using CMD in Windows flashing some stuff. Thanks guys!

Bricked?

My current situation:
Recovery does not work, when I try to enter it it gets frozen on the Google screen with the lock at the bottom.
When I try to go into the phone normally I receive an infinite error "Unfortunately, Setup Wizard has stopped".
My device is not being recognized as an ADB device so i cannot reinstall recovery (possibly USB debugging is disabled and cannot get to it).
How I got here, Used the Nexus RootToolkit v1.5 to unlock the bootloader/root the phone which worked fine except recovery was not working and the play market was gone for some reason. Did a variety of things to get it back with no avail and eventually got frustrated and tried a factory reset. Now I am in this perdicament :crying:
I came from a Samsung Galaxy and Odin was the universal tool to get the phone back even if it could not enter recovery or the phone, Is there anything like that that can fix the phone without entering recovery or the phone itself?
If you can get the device to recognize in fastboot you can flash the factory image for nakasi from here
How do you flash without entering recovery though?
Can you enter the bootloader? While the tablet is off, hold both volume buttons and the power button, and let go of only power after you see the Google logo. You should enter the bootloader. Download and decompress the factory image from the aforementioned link and open the flash-all file in Notepad to see the required fastboot commands. Use the corresponding command to flash the stock recovery back to your Nexus 7 and see if that fixes your issue. If your computer isn't recognizing your Nexus, install the Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=1766220. Good luck!
Sent from my Nexus 7
slifer315 said:
Can you enter the bootloader? While the tablet is off, hold both volume buttons and the power button, and let go of only power after you see the Google logo. You should enter the bootloader. Download and decompress the factory image from the aforementioned link and open the flash-all file in Notepad to see the required fastboot commands. Use the corresponding command to flash the stock recovery back to your Nexus 7 and see if that fixes your issue. If your computer isn't recognizing your Nexus, install the Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=1766220. Good luck!
Sent from my Nexus 7
Click to expand...
Click to collapse
Yeah I can get into the boot-loader. I'll give this a shot and see if it works. thanks!
slifer315 said:
Use the corresponding command to flash the stock recovery back to your Nexus 7 and see if that fixes your issue.
Click to expand...
Click to collapse
I installed the universal naked drivers with no problem. Sorry for the noob question but where do I input the commands in the flash-all file for the fastboot?
Use my video guide to help you out. http://www.youtube.com/watch?v=-E-EF0QC0Gc
l0aded said:
I installed the universal naked drivers with no problem. Sorry for the noob question but where do I input the commands in the flash-all file for the fastboot?
Click to expand...
Click to collapse
You need to have the Android SDK installed, open a command prompt, and cd to its directory and the tools folder. In there is the fastboot binary that allows you to run fastboot commands. For ease of execution, you can just install the SDK on the root of your C: drive or just copy the tools folder to wherever it was installed by default (/Program Files/Android/).
Sent from my Nexus 7
Thanks guys! Restored to factory stock and am back from the brick.
l0aded said:
Thanks guys! Restored to factory stock and am back from the brick.
Click to expand...
Click to collapse
Great!
Sent from my Nexus 7

[Q] Flash back to Stock

Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
samwathegreat said:
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
Click to expand...
Click to collapse
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
samwathegreat said:
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
Click to expand...
Click to collapse
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
samwathegreat said:
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
Click to expand...
Click to collapse
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
samwathegreat said:
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
Click to expand...
Click to collapse
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Awesome!
samwathegreat said:
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Click to expand...
Click to collapse
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
boss. said:
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
Click to expand...
Click to collapse
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
samwathegreat said:
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
Click to expand...
Click to collapse
Re-did the whole thing from scratch again and now all problems are solved. Really appreciate the help my friend!
Sent from my SM-N9005 using XDA Free mobile app

How to unlock BOOTLOADER and Install any zip file on your LG NEXUS 5 D820 using CWM

************
First, I am not responsible if you damage your phone in any way.
Also you might back up your phone's data completely because after unlocking bootloader you can lose all your installed data.
*************
So, first step is unlock the bootloader. First go into
Setiing> About Phone > Press Build Number A couple of time until it shows you are a developer now > go back > Developer Options > Turn on USB debugging.
After that, go to your bootloader, by powering off your phone and once it is powered off press the Volume down key + Power button until something appears with a vibration.
Now download adb and fastboot from this link:
http://*******/1Zsyme
After downloading it, install it. And you can install it easily with no problem. Just make a folder in your windows drive of :
C:\Android-adb\
And you are good to go.
Now goto that folder (C:\Android-adb\) and press SHIFT+CTRL+RIGHT-CLICK together or just SHIFT+CTRL first and then RIGHT-CLICK and then click "open command window here".
Now connect your nexus 5 and check if your PC makes a sound like when you connect a external device.
If yes, then you are good to go. Else try connecting it several times to automatically make the PC install any drivers.
After this, go to that DOS type window and write:
fastboot devices
(press enter to activate any command)
If you it shows a serial number then you are doing fine.
After this, write this command in that CMD.exe window:
fastboot oem unlock
and wait until something pop-ups in your phone. It might be a warning, read it carefully and using your volume up or down key cycle through the options and using power button select yes. And it might reboot on it's own else restart manually by pressing the power button for 10 or 15 sec until you see your screen with a unlocked lock which means you have successfully unlocked the device.
Now after that, it's finally time to FLASH recovery file.
For this to happen you need to download CWM latest version from here:
http://*******/1Zt1Fs
It's latest for HAMMERHEAD or NEXUS 5!!!!
Now, again go to the bootloader as described in the beginning.
Now you can also copy the recovery zip file by your data cable of your phone by turning in on normally and also from bootloader.
How to do it from bootloader? Here's how too.
Now you have to be on the bootloader screen. Now goto the same CMD.exe and write:
adb push filename.zip /storage/emulated/0/
adb push filename.img /storage/emulated/0/
If you get any error ask me.
Now it might get some time to be moved to that.
(Data Cable should be attached to do so, also the RECOVERY img file should be in C:\Android-adb\ this folder to be moved to PHONE)
Now, you might have successfully moved the zip file to your phone. So now write this command to flash Recovery.img file:
fastboot flash recovery your_recovery_image_name.img
After this, it will FLASH the recovery file. Until it's installed successfully wait till then.
Once it is FLASHED, now cycle to recovery mode using volume buttons from the BOOTLOADER and wait till it gets there:
Now you will see some options, but you need to flash a zip file so cycle again using volume buttons and select anyone using power button. So select:
install zip
Now select choose zip from /sdcard
Now you are in your internal storage's directory where you moved your zip files from CMD.exe. Just select it and you are done. go back and reboot system now. And you are done.
Don't forget to say thanks if you find it helpful in any way.
Also report to me if you get any errors between in it. By the way, I didn't have any errors in my journey to do this in first time.
You should point out and highlight that unlocking the bootloader will wipe all data.
Sent from my Nexus 5 using Tapatalk 2
You do not need USB debugging for fastboot, you do not need to open fastboot or adb within the directory they are install in, you...
There are already guides, which are more accurate and up to date, to direct people through the process. Who uses CWM?
wangdaning said:
You do not need USB debugging for fastboot, you do not need to open fastboot or adb within the directory they are install in, you...
There are already guides, which are more accurate and up to date, to direct people through the process. Who uses CWM?
Click to expand...
Click to collapse
TWRP not worked for me. I use and recommend CWM. TWRP is full of bugs and does not show errors and hangs. But CWM is the best.
ddimple4 said:
You should point out and highlight that unlocking the bootloader will wipe all data.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I did mentioned but didn't highlight.
Except for the fact that CWM is out of date and not maintained for our device.
---------- Post added at 05:53 AM ---------- Previous post was at 05:52 AM ----------
Except CWM is out of date and not maintained for our device. TWRP is not full of bugs.
What is the point of this thread? Isn't this all common knowledge?
Google says you need to hold VOL UP, VOL DOWN, and POWER to boot into fastboot, but I've used just VOL DOWN and POWER on my N5.
fastboot oem unlock has been superseded by fastboot flashing unlock, though it still works for the N5.
You can download the Android ADK CLI tools from https://developer.android.com/sdk/index.html . Always point to the authoritative source.
You'll need to be in the \platform-tools directory UNLESS you add it to the PATH.
So far's I know, ADB will not push a file while you're in fastboot. You can just flash the recovery file from the directory you have it, e.g. fastboot flash recovery .\your_recovery_image.img.
Very nice of you to post, OP, but you've got a few things wrong in your guide. Read some others to find your errors, and keep writing, Android needs informed enthusiasts and writers.
Yeah, it's 2016. Why was this thread even made? It's either common knowledge, or there are a hundred other guides about doing this.
Plus, who the hell uses cwm these days? Twrp or don't waste your time.
This whole post feels like something from 4 years ago.
GldRush98 said:
Yeah, it's 2016. Why was this thread even made? It's either common knowledge, or there are a hundred other guides about doing this.
Plus, who the hell uses cwm these days? Twrp or don't waste your time.
This whole post feels like something from 4 years ago.
Click to expand...
Click to collapse
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //
ChromeJob said:
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //
Click to expand...
Click to collapse
Outdated for years.
ChromeJob said:
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //
Click to expand...
Click to collapse
It's outdated, no updates. Last I heard some of the CWM team are now contributing to TWRP. It's pretty much the official unofficial Android custom recovery at this point. You will also have a lot of issues trying to flash or update on older versions of TWRP or other recoveries that aren't updated due to file structure changes in newer Android versions.
RoyJ said:
It's outdated, no updates. Last I heard some of the CWM team are now contributing to TWRP. It's pretty much the official unofficial Android custom recovery at this point. You will also have a lot of issues trying to flash or update on older versions of TWRP or other recoveries that aren't updated due to file structure changes in newer Android versions.
Click to expand...
Click to collapse
I see the light. CWM team seem to have abandoned Helium, too; no longer works on systemless root. That's second or third app they've simply gotten bored with and not continued development.

Categories

Resources