- #FASTBOOT FLASH RECOVERY DID NOTHING INSTALL#
- #FASTBOOT FLASH RECOVERY DID NOTHING ZIP FILE#
- #FASTBOOT FLASH RECOVERY DID NOTHING ANDROID#
- #FASTBOOT FLASH RECOVERY DID NOTHING DOWNLOAD#
#FASTBOOT FLASH RECOVERY DID NOTHING ZIP FILE#
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.
#FASTBOOT FLASH RECOVERY DID NOTHING DOWNLOAD#
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. Hard bricks can be caused by issues like attempting to flash an incompatible ROM or kernel, and. Move your ROM over to the internal storage. You push the power button, and nothing happens. Once you're back on MIUI, flash TWRP again and boot to it. 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. Connect your phone in fastboot mode to the computer and once it's unzipped, open the fastboot folder it creates and double click the flashall.bat file and give it about 5 minutes and you'll be back on stock MIUI 11. Not my day obviously.This method can be used to flash to any partition, not just recovery. Oh well, and I misundertood the TWRP instructions in the other place that I can’t find anymore (not the FP community) in the way that I allowed TWRP to modify the system partition so that it could actually avoid the reinstallation of the original recovery. But it may of course be just my way of reading it. The reboot in step 6 (the second 1 above - citation messes this up) runs the normal OS, and I think this is what might have reinstalled the original recovery for me. Your phone should start normally and flashing is complete.Ħ.b Verify that TWRP was permanently installed: At last we will restart our FP2 by typing:.
The flashing only takes some seconds and should not produce any errors. Next we will flash the image to the FP2 by typing:.Re-reading the TWRP wiki entry, I still understand it as booting into the normal OS first: I really feel stupid today and appreciate your help... The last option (disable fast boot) is what fixed Hillarys problem. Warning: Failed to find package build-tools 27.0.0.0 Warning: File C:\Users\myname\.android\repositories.cfg could not be loaded. Nevertheless, flashing still did not work (and feels too quick) C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery c:\twrp-3.1.1-1-fp2.imgĪs for an alternative to Minimal ADB, I installed the SDK platform tools as suggested, started sdkmanager, looked at the list of modules and figured it would be the build-tools 27.0.0.0 that might contain adb, but no success here either: F:\AndroidSdk\tools\bin>sdkmanager build-tools 27.0.0.0 Thank you guys, that shed some light on the issue… Yes I mixed up boot and recovery It is some years a go that I tried this on a Samsung the last time, and with Samsung tools, so everything felt new to me again…
#FASTBOOT FLASH RECOVERY DID NOTHING INSTALL#
Lucky enough, I can boot the normal FP OS yet.Īny idea how I can circumvent this and still install TWRP? What file versions should I use today, and what do I need to clean from my computer to make sure I work with a correct setup? Or am I completely on the wrong track here? Thank you all in advance… Just like to did to put your phone in fastboot mode but the. Reboot your device into recovery by pressing vol+ and power button, release power button but keep vol + pressed while it boots (with the android/miui) logo until you get into the recovery. The same with Minimal ADB & Fastboot, version 1.4.1 and/or the original recovery images that comes with TWRP - a too short flash duration and the same error when booting to recovery. And from this recovery flash the lineage-17.1 (.).zip.
#FASTBOOT FLASH RECOVERY DID NOTHING ANDROID#
I can boot to recovery but just a small Android figure with a German message like “Invalid operation” appears. Target reported max download size of 536870912 bytesīut the recovery is now destroyed, i.e. Flashing TWRP showed > fastboot flash recovery c:\boot-fairphone-FP2-gms-17.10.2-su-eng-r318.img The only other ADB I could locate on my computer was from Helium, so I deinstalled Helium, and the message disappeared. Googling this message did not reveal anythin that helped me really. I used the latest Minimal ADB & Fastboot, version 1.4.3, and got a message that the ADB server verions (31) does not match the client version (36).
So I felt I should root the phone to circumvent this, and I tried to follow this Howto. True, and I can switch this to PTP, but once I go back to Helium, it bounces back to MTP My original intention was just to move as much as possible from my old phone to my new FP2 with Android 6, but Helium Backup always complains that USB debugging is not in PTP mode.