![]() In the current Android platform tools zip, named 'platform-tools_r28.0.1-darwin.zip, there's a 'fastboot' in the root directory, with no ',exe' extension, This should work although you don't really need it as you already have one. exe or flash.sh) for the oem unlock command, in accordance to Sony's instructions. This means you did actually have a compatible fastboot binary in place when you ran flash.sh, and that's what you should have used (not the. For example, suppose the downloaded recovery is TWRP-3.3.1MotorolaOneAction and is placed inside the Downloads folder. Now drag and drop the TWRP file next to that code. It was fastboot that gave you the OKAY and FAILED errors. Just enter the fastboot flash recovery or fastboot boot recovery command and leave a space after the command. In your second piece of output in your original post at the top, you can see that a fastboot command was prepared and executed properly, sending the 'boot' image to the phone which then failed to flash because the phone was still locked. However to do this, internally it runs the fastboot binary (named only 'fastboot' on Linux or OSX, with no '.exe' extension) which is the same binary that can be used in the earlier unlocking step. use SP Flash tool, and install cwm through it. go to /system/ and delete this file ' recovery-from-boot.p '. ![]() It's only for flashing Sailfish onto it after it has already been unlocked. try this: first, root your device, and install root explorer. Flash.sh does not have anything to do with unlocking the phone.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |