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… 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… 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.
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.
0 kommentar(er)
