After playing with the latest update One+ One update 38R, I have decided to go back to old update 25R. This is to see if battery life is really that great. 38R so far has came in around 24 hours for battery life, whereas in 22R I managed to clock over 30 hours.
Downgrading the lazy way or dirty flashing I thought should be a straight forward fastboot flash. It was except that I forgot to put in required files in the right places causing an error. The phone was permanently stuck on boot and I could not get into fastboot mode.
Did I just killed the phone?
No. Fastboot mode is activated by pressing volume up and power. Reverse from Samsung. Flashed again and the phone boots up normally.
If anyone is interested, I used this modified script.
echo ######### This patch is Created by ONEPLUS Technical Support. #######
echo ###### This patch should only be used for ONEPLUS ONE 64GB Global Version. ######
rem fastboot oem unlock
rem fastboot erase persist
rem fastboot flash persist persist.img
rem fastboot erase reserve4
rem fastboot flash reserve4 reserve4.img
fastboot flash boot d:\25r\boot.img
rem badidea fastboot flash userdata userdata_64g. img
fastboot flash system d:\25r\system.img
rem badidea fastboot flash recovery recovery.img
fastboot flash cache d:\25r\cache.img
fastboot flash modem d:\25r\NON-HLOS.bin
fastboot flash sbl1 d:\25r\sbl1.mbn
fastboot flash dbi d:\25r\sdi.mbn
fastboot flash aboot d:\25r\emmc_appsboot.mbn
fastboot flash rpm d:\25r\rpm.mbn
fastboot flash tz d:\25r\tz.mbn
fastboot flash LOGO d:\25r\logo.bin
rem badidea fastboot oem lock
echo It is done Now 🙂
The lines for user data, recovery and oem lock are protected against find and replace by badidea tag.