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.
OK, so tired with the 10 V misery, I’ve just ordered a refurbished violet 1 IV. It should arrive on Monday or Tuesday. I was told that it is the XQ-CT54, hopefully it is so.
What troubles me is the overheating issues of the 1 IV and 5 IV (or SG 8 gen 1 in general) I read about here and there. Is it really that severe? When does it manifest itself the most on SFOS? During web browsing?
Another thing is the green lines on display issue? Is it a common failure on these devices? The one I ordered has a brand new display replaced by Sony service centre, quite possibly because it might have had that problem. Should I expect it to develop this issue in some foreseeable future?
Sorry silly questions but I really got worried about those issues. It’s not a cheap phone, even refurbished one.
I have a 5 IV running android as daily driver since it hit the market. The only issues I had with overheating was while taking videos, especially when recorded in 4K. It happened several times (especially in summer) that the camera stopped while filming cause of heat, even when I turned on flight mode and also took of the bumper.
1 Like
That is kind of ridiculous for such expensive hardware. But my Sony XZ2 Compact gets hot easily when under heavy load too. So let’s say I can feel failed processes with high CPU-Load before I see them in crest.
My Jolla C2 is the complete opposite of it. Only when the brightness is set to full will the bottom of the display be warm, but not hot.
In browser device may warm up more, but not sure its overheating. Battery consumption surely goes up then.
Re green lines: I hope we wouldn’t see that. But I don’t know the origin of them nor how to prevent it.
2 Likes
A few posts above there’s a video and pictures from @Zebastian with those green lines. Looks horrible 
I’ve read that it’s caused by excessive heat - something inside the display gets disconnected.
I remember how my Blackberry Passport suddenly started overheating. Since then it was only getting worse. At one point it developed a permanent discoloration (yellow/orange spot of a fingerprint size) on the display right above the place that was getting hot the most. But it only started happening after several years of use, not on a new device.
On the other hand, I also had a serious overheating incident with the 10 III with SFOS and AAS. While driving, I was using a very popular Polish Android navigation (and speed camera warning) application. It made the device so hot that it shut down and the protective glass on its display unglued in a few places. When I touched it, I was literally shocked because it was extremely hot, almost hurting. The same application launched on the 10 V with its stock Sony Android didn’t make it even warm, let alone hot.
I really hope I won’t have similar adventures with the 1 IV. Well, I can return it within 14 days so I’ll need to test it carefully first. From the pictures, it looks like a new device, without a single scratch. The seller sent me the IMEI, so I was able to check that its warranty ends on Feb 10 - so it’s relatively new. Indeed, like the seller said, it was serviced by Sony service center only a week ago. I requested the service to give me full list of replaced parts, because their online warranty repair status page is broken and only shows a few unimportant ones (it looked the same with my 10 III which got its mainboard replaced while that page only showed some tiny parts like rubber seal of the back cover, etc. Let’s see if/when they respond.
If the device heats too much, I’ll test it with some less demanding CPU governor (conservative? powersaving?) - maybe it’d keep it cooler. It’s some 2-3 times faster than the 10 III so I guess even with powersaving governor it might be very usable…
I’ve read that AAS (from 10 V) works just fine on it. Is that true? How about sending/receiving MMS? What is currently the biggest / most troublesome issue in daily use?
Once again, thanks a lot for all your responses and I’ll be back as soon as I get the device.
you ask a lot of questions after your purchase…
where did you read about AAS? I remember only one post about it in this thread and that said, its working but some features are missing.
SMS seems to work but nobody will give you the guarantee it works with your provider/configuration.
Is it unusual?
I was actually asking specifically about MMS (images, to be more precise). I know it is operator dependent, I just wanted to know if it is at all implemented.
As for AAS, it’s sad that mobile data doesn’t work atm, does anybody have a clue if it is relatively easy to fix? That’s actually the only serious issue. If Jolla is supposed to ever want to officially enable AAS for such a port, I bet that it’d be up to the community to first make its basic functionality work, or else Jolla would never have the time, resources or willingness to do anything about it themselves…