Open rainabba opened 8 years ago
Naturally, it's not until I file an issue that I find a workaround. I flashed back to 2.8.7.2 and was able to get into recovery with that. From there, I was able to flash back to 3.0.0-1 and it still wouldn't load.
I then tried 3.0.1 - no go Back to 2.8.7.2 - good Then 3.0.0-1 - no go Back to 2.8.7.2 - good Then to 3.0.0-0 and WAS able to load.
Based on this anecdotal evidence I'd have to conclude that something changed as of 3.0.0-1 that is sensitive to something in 3.0.2 so that once 3.0.2 is installed, >3.0.0-0 won't run without a change in another partition.
Having the same issue on Android N/7. Went from 3.0.2-0 and stepped my way back down til 3.0.0-0... Freaked me out because it hung after my phone rebooted. 3.0.2-0 did, however, work with Android 6.* before I flashed to Android N/7
I have been able to make backups with Flashfire for what it's worth.
This is because encryption isn't supported on N yet -using TWRP. However, if you flash a unencrypted boot.img with verity disabled TWRP will work just fine. I'm actually looking into helping these guys out to get TWRP working on encrypted N builds since the latest version is supposed to be the last one and pretty close to the final release.
Note: After flashing a "no encryption kernel" , you must wipe userdata so decrypt can proceed.
Perhaps this is my issue having misread that 3.0.2 worked with Android N, but after installing it on Preview 3 (npd35k), it's stuck at splash.
I've tried flashing back (fastboot flash recovery) to
3.0.13.0.0-1 and 3.0.0 and it makes no difference. The only way I've been able to get TWRP running again, was a complete factory image reset to Android 6.0.1 then reinstalling TWRP which makes me thing that 3.0.2 is picking something up from Android and it's not reset when flashing a new recovery.I'm way out of the scene these years so I don't have more feedback, but if there's anything I can do to help, let me know.