I want to upgrade my FP4 from 1.16s to 1.17t stable without unlocking the bootloader. When I enter the sideload command in adb sideload mode, I get the error: protocol fault (no status).
e/Os version: 1.16-s-20231013341147-stable-FP4
But no worries, I realize it just isn’t done yet and will wait until the stable version is announced.
I did a little research myself. The reason was the ancient adb I was using (from 2014). I actually had to delete the file and manually move the new one to my adb folder, until then Windows used the old version for some reason. Update is installing now
Thanks a lot for your help AnotherElk!
Update: Flashed your image, no errors during update. Now it boots straight to bootloader. Recovery still worked so I downgraded back to s.
…seen this while downloading " IMG-e-latest-s-FP4.zip " via easy-installer …
Your warning includes this version/way of installing /e/, right?
Is it possible to use " IMG-e-1.18-s-20231207360611-stable-FP4.zip " as further version via easy-installer?
grrrz,
Bric
(sometimes heaven sends procrastinating offers…i rather wanted to flash the FP4 yesterday, but the wheather was too fine…and now your today’s notice)
This is yesterday’s latest statement from Manoj concerning FP4 Android T (13) version upgrade. So hopefully next version 1.21 would bring Android 13 to the FP4.
Hi,
Will FP4 finally get Android 13 upgrade ?
It had been announced for several /e/OS versions, at least v1.19, v1.20, and then v1.21, but the release notes for v1.21T does not mention it (though it mentions that FP3 will be running Android 13…).
I am really longing for this upgrade (as I hope that it might fix several issues I am facing with my Murena FP4, mainly related to Bluetooth, audio, and WIFI).
Thanks for any news in this regard !