To disable this setting, go to Settings > Power > Fast boot (uncheck the box).Ģ) Hold down the power button and select Power Off from the menu. This is a setting in Sense to allow the phone to boot up faster. Note, this "Fast Boot" has nothing to do with the fastboot executable I've been talking about. To do this:ġ) make sure the Fast Boot option is disabled. Once the recovery image is in the same /tools folder as fastboot, you'll need to put your phone in fastboot USB mode. I would also rename the recovery file to something short like recovery.img. Once you've verified you can run fastboot, it's time to move the recovery image to the /tools folder (easier not to have to specify a path to the recovery file). Check your path and where you installed the SDK and make sure you are in the /tools folder. If you don't get that, you're probably not in the right folder. You should see a list of fastboot commands available. Open up a cmd window and go to your SDK tools folder.
Ok, these instructions are for Windows users, but the equivalent steps should work for mac and linux: In there, you'll see the fastboot executable.
zip file and extract it anywhere on your computer.
Once the drivers are installed, you should get the Android SDK here: (go to the part, "are any drivers required?") Both adb and fastboot require that you have the HBOOT drivers installed for your phone. If you have adb working, then fastboot is ready to go. If you ever want to help in the effort to crack bootloaders, having fastboot working is a mustįastboot is a little executable tool that comes with the Android SDK.
This method requires a little more setup and is a bit more manual than the above update.zip method, but in my experience, having a computer set up to run fastboot and adb can come in handy, especially once you've graduated to an advanced power root user. Name the file PG86IMG.ZIP, and you're all set. Then, put it in a ZIP file without compression. For example, if you have a recovery image file, it needs to be named recovery.img. img file, you can make your own update.zip file. HBOOT will automatically scan for the file, and if it was named correctly, it will ask you if you want to flash what's in the file. All you need to do is rename it and put it in the root of your SD card. The link to TWRP recovery above is distributed in this update.zip format. You just have to rename it to PG86IMG.ZIP. Most of the time, you don't need to worry about all this the file you download will already be in the correct format. img files named the same as the partition name. The filename needs to be named PG86IMG.ZIP for the Evo 3D, and it needs to contain the. Essentially you place a file at the top (root) level directory of your SD card and HBOOT will automatically find the file and flash its contents. This method can be used to flash to any partition, not just recovery.
If you are unsure how to do this, see this post: The other way, fastboot, is more technical and requires that your PC is set up with drivers and the and fastboot tool.īoth methods require that you boot your phone into HBOOT. The easiest way is known as the update.zip method. There are two popular methods to flash a recovery. Or you can go with ClockworkMod recovery, which is what you would end up with if the recovery portion of Revolutionary succeeds:Ĭhoose which recovery you want to try, and save that image to your computer. TeamWin Recovery Project (twrp) v1.0.2 - xda-developers But if you're one of the people who has run Revolutionary and is without a recovery image, this is for you.įor now, TeamWin has created a brand new recovery called TWRP, and it works great. Or you may want to wait for Revolutionary to address the issue. The following is a guide on how to manually flash a recovery. And once it S-OFFs your HBOOT, it won't run again, so there's no way to get it to retry the recovery flashing. I installed cm12.1 on this phone before without any problem.As of this post, it would appear that the S-OFF tool, Revolutionary, may not successfully flash clockworkmod recovery for everyone. (bootloader) Erase of partition 'system' requested (bootloader) Erase operation complete, 0 bad blocks encountered (bootloader) Erase of partition 'boot' requested since I already erase the system, boot, and recovery, fastboot is the only way I can interact with my phone. Here is the result of other fastboot commands.
I'm trying to flash cm13 boot.img to my phone and it stuck on this for more than 20 minutes: $fastboot flash boot boot.imgĪnd after I disconnect the cable I get this error: FAILED (data transfer failure (Protocol error))