It seems the updater isn’t throwing an error anymore, which was the case before the 20180827 release fixed it, but I’m now running into the problem that a reboot to recovery isn’t possible (a known bug) and so I still need to enter TWRP manually. But after I did this the update seemed to be queued and started directly. I’m on an encrypted FP2 by the way.
I can confirm that: once manually entered recovery the update picked up automatically. But as far as I know the reboot to recovery issue only affects phone with the new (main) camera module.
@jhohn: I noticed that the PIN-Entry for the 2nd SIM gets “whacked” by the Lockscreen. Now I’m waiting for the PIN-Entry to appear a second time before entering the PIN.
Why? I couldn’t detect an open issue for this in any of the open threads. Instead, someone else opened a new thread regarding same issue.
About camera: Ok, I could try the old camera (looked for it already, but didn’t find yet).
Unfortunately not, I tried adb only after buttons didn’t work out but booted into OS as well. They’re working properly as volume buttons when not pressing power.
As I see it, ADB is partly about remote-controlling Android.
If Android reboots into the OS instead of into the recovery, I guess ADB calls the same function Android uses and has no clever knowledge of another way of rebooting.
I could be wrong of course, I guess there’s an “I guess” missing in my earlier post. Fixed .
You can simply disassemble the new camera without assembling the old one. The phone works without the camera.
(I had to do this for encryption, which also doesn’t work with the new camera yet.)
Amazing. I have no clue how that can be and will be very interested in how this all plays out …
“Normally a bootloader will proceed to booting a valid boot partition. In case there is none, the bootloader will fall back into fastboot mode.
There are a few options to force fastboot mode despite valid boot partition:
[…]
By invalidating boot partition. Destroy boot partition signature, issuing on the device (in either Linux or Android command line): # dd if=/dev/zero of=/path/to/boot/partition bs=1 count=1”
Thank you very much, just disassembling the new camera was too easy to hit on it (correct english?) or just try it out Also the idea with invalidating the boot partition is very interesting for more persistent problems!
I’ve now successfully replaced the new camera and the phone boots nicely into recovery, and bootloader respectively and I could go flashing again
.
Also the idea with invalidating the boot partition is very interesting for more persistent problems! 