Any Inoi R7 users out there?

Well, at least from the info available here, Jolla pushes updates only to their devices and Sailfish X.

So i did the searching that you perhaps should have done… some other guy in a similar situation was stuck on 4.0, managed to force some more updates - and then it broke.

Maybe they pulled the update server offline?

I dunno. I wrote to INOI support as well as to OMP and they all say sorry we can’t help.
They didn’t say we drop it or pause it. Or advice something. They just say sorry dude we won’t help ya.

Guys on 4pda says that latest one was 4.1.0.24 Kvarken. And I can’t get it. Anyway I’m not sure it tru (about version 4.x.x.).

I can freely login to Jolla account and open Jolla store. And install apps. I need to isnatll on it Warehouse or Storeman and use it as it.

Anyway I’m just wanna now latest official available build version and nothin more. If it is 3.0.0.11 well fine. Bit it’s a lil strange coz it’s not stop-release even.

Rereading this thread, 3.0.0.11 may be the final “official” release for the Inoi R7. Edit: It is not, an flashable image with SFOS 4.0.1 exists, which can be upgraded to at least 4.2.0, see postings below.

Note that the hardware of the Inoi R7 closely resembles the hardware of the Jolla C and the Intex Aquafish (l500d), so one may be able to upgrade further (the Jolla C is still supported), if one exactly understands and knows which packages may cause issues and keeps old versions of them around; you will also have to know the rpm utility and RPM troubleshooting well.

2 Likes

Oh thanks for your research. Ill look at this 2nite to undastood deep.

But we have 2 fw on 4pda for INOI
SailfishOS-service-flashing-IntexAquaFish-2.0.2.48-l500d-in-0.0.1.32
and
SailfishOS-p4903-lvm-4.0.1.48-p4903-0.0.2.44.tar.zip
Both of it were sucefully flashed by community.
As ya may see last one is v4 but not 4.1.0.24 Kvarken for sure.
Maybe Ill try to flash it in time.
And if i try to fetch update via Terminal so it show correct device name in OTA file name - p4903. But download nothing in the end.

And btw in link ya provide says about 3.1.0.11 but I have 3.0.0.11 onboard. So my phone even wont get update to 3.1.0.11. And some guys says that they have 4.1.0.24 preinstalled (but I can’t agree with it).

Well, I guess this won’t be helpful to you, but my R7 got OTA-updates until Version 4.0.1.48 (always updated via GUI without any problems). Then there where no more OTA updates available for it.

User msdk brought his device further by updating via terminal (see this thread), but the latest update to 4.5.0.19 resulted in troubles with camera and gps.

What’s really annoying, is that there’s no reaction of Jolla (or other “knowing people”) on this at all…

2 Likes

Yep this isn’t help me at all) But interesting for sure. When I try to get update with terminal all logs similar to Comparing version strings issue · Issue #32 · Olf0/sfos-upgrade · GitHub

1 Like

Just as a curiosity, are you using SFOS or Aurora OS? Thank you!

As ya may read upper i have both of it. But Aurora is semilocked (locked on administrator account) and useless (but there is totally locked R7 even on user accounts existed). SailfishOS is stuck on old build.

1 Like

Have you tried to contact Jolla on zenhelp desk? The customer care.
INOI did manifactured it, but they don’t have anything to do with software, I guess.

I’m not. I already contact INOI and OMP (both company that have direct relation to this device). But both of it says: “sorry we can’t help ya” and both of it point to each other uhu. The reason is obviously to me (and I can’t say it loud I’m sorry). Ok Ill wrote to Jolla but I doubt they help. There is no any other device in selection but Sony and Jolla (oh and Gemini). So…

And this is kinda strange guys ya know. Well ok if Jolla wouldn’t support any other devices so why I’m still must use Jolla account to check updates (and chaining account works fine). As well as my phone shown in Jolla account:
P4903 IMEI Aug. 7, 2023

Hmm… Is Early access switch in Jolla account is still have any action?

Well ok… Im reflash it with LVM image to 4.0.1.48. Its all works fine. It wont fetch any updates still (no matter is early access on or off). The only visual difference is removed OMP layer (thanks God at least for it).

Finally I have update it to 4.1.0.24. Via terminal. And I still wish to know why it can’t get updates via GUI.
Meanwhile I get that Sailfish Mobile OS RUS isn’t the same as clear Sailfish OS. It is pre-Aurora OS. And I can understand why it can’t get updates. But not clear Sailfish OS. But now I have last one. I hope I can unbirck my another one INOI on Aurora OS to Sailfish OS.

1 Like

SW updates via GUI is a paid feature for Sailfish X.

2 Likes

Please be so kind to provide a link to the source of SailfishOS-p4903-lvm-4.0.1.48-p4903-0.0.2.44.tar.zip, presumably somewhere in the XDA forum. This will allow other users of an Inoi R7 (i.e., device ID p4903) to follow the upgrade path you successfully used.

I recommend using sfos-upgrade for upgrading SailfishOS at the command line; see its description for reasons.

Unfortunately, that post by @msdk does not tell, if it was working fine with SailfishOS 4.4.0.72, or if 4.3.0.12 was the last release which was working well. I also do not comprehend why 4.3.0.15 was not working well, but 4.3.0.12 was reported as O.K., as there is no significant difference. Maybe 4.2.0.21 ist the last release which really works fine. But as you can re-flash to 4.0.1.48 and upgrade from that at any time, you can try.
Note that I provided some ideas and questions to determine what the reason may be for the issues, which were observed.

1 Like

Oh wow… Starting from Sony “acquired” Jolla or something like this? Coz few year ago there were no anything like this. INOI R7 on OMP was updating fine. Brave new world…

Sure I do. There is it. Please mirror it in XDA with good English description. Both 4.0.1.24 (thanks to Ancelad of 4pda.ru and 2.0.2.48 with Tetst-Point method for bricked phones (thanks to eduard07_07 of 4pda.ru and Im pretty sure CODeRUS (readme in Russian guys so use translator). I didn’t check second way but on 4pda.ru users did it. And I wouldn’t check updates next with your scripts at least for now. I’ll try it at my second bricked INOI R7 on Aurora if I can unbrick it. Thank ya all guys!

BTW Android version on this hardware Wiko Mobile - TOMMY

The question: what is it https://releases.jollamobile.com/ ?

And P7 office links to test (Im not sure itll run well on SFOS coz its Aurora OS builds).
Offline edition and Cloud edition. But I suppose its precompiled for Aurora fork and to SFOS its need to be modded.

1 Like

This only applies to Sailfish X; i.e. the Xperias and Gemini PDA where you purchase a license separately.
Inoi, like old Jolla phones has it included in the price of course.

2 Likes

But its is broken. Well not phone didn’t say there is error. Its just say its up to date.
There is a rumors that Jolla ban Russia for known reason. But I can’t prove it. I fetch updates via terminal with no any VPN etc. And with VPN I can’t fetch it in GUI. Its good just to know whats going on and where is problem.

And next question is Jolla account needed for updates via terminal?

If you run ssu lr in terminal, you’ll se what servers are used.
If it is jolla’s, then they may have pulled the updates - and presumably you need an account with them (as opposed to something else).

Sounds pretty reasonable to me. But it doesn’t have to be out of spite or sanctions, it can be that the contract has run out and/or inoi stopped paying, or being able to pay.

1 Like

Guys please advice me how to use test-pont flash metohd right. I know that test points is directly on back of the phone right above battery. Im just don’t understand right way to flash.