Might this be relevant to our issues?: Flash the firmware to both slots · Issue #29 · munjeni/newflasher · GitHub
how did you run newflasher when the device is in fastboot? Do i just go to flashmode after setting it to A? Also it was already set to A when I checked when it was flashed with sailfish os already
Yes you reboot into flash mode.
I flashed my firmware to both slots and now it gets to a sony logo and immediatelly turns off… Should i try to get recovery and do the rest?
Nvm it got worse
nvm i got it to boot after setting it back to A
did the slots thing and still the same issue with it being stuck on the sony logo. (ignore the green lines, it aint my main phone anymore 
)
You can use fastboot commands in flash mode too. Check that you have active slot A, newflash it with stock and boot into stock. Check that all works. Then flash LOS, check that it works. And check that you are on slot A. Then flash sfos as instructed via los recovery (combination of adb/tar and fastboot)
I did all of those and it still gets stuck on the sony logo… What am I missing? I’m gonna record a video of it and upload it here to show what it looks like when im installing it later…
Edit: I recorded the entire thing from showing it being on slot a from installing firmware using newflasher, install lineageos which works just fine and from it not working on flashing sfos.
1 Like
Are you enabling init debug? (you shouldn’t)
Looked it through and it seems like all is done correctly. Debug was not enabled, as far as I could see. Thank you for a very thorough video!
Now, what I have been doing differently. I would have booted to stock twice. And in between that, I would have shutdown the phone.
Same with LOS: boot twice and shutdown in between.
All boots would have been without USB plugged in.
Booting without USB maybe important for SFOS. With the cable plugged in, you may get into act-dead mode. Not sure whether it would activate in this case, but worth a try.
Also, after flashing SFOS, I would have shutdown the phone first from fastbootD and booted into SFOS by power button.
No idea if anything here matters, hopefully would help. Good luck!
When looking closer in the path of flashed files, looks like you have the same vendor_boot for LOS and SFOS. It seems that you unpacked LOS and SFOS images into the same folder and due to the same image file one overwritten another one.
Please unpack LOS and SFOS archives into separate folders and flash making sure that the files are correct.
3 Likes
One interesting thing I noticed - in this port I never had the broken audio issue (when you have to restart the audio subsystem to get it back). I always thought this issue was happening on all devices. Or maybe I’m just lucky. Can anyone confirm?
I only had it one or two times on my 10ii over the past years and that was somehow related to the use of AAS (I think with something using GPS).
It happened relatively often for me on 10 III and it is connected to Bluetooth audio - happened after disconnection from my car.