The Sony Xperia XZ1 I recently bought from Iodé Shopp suddently stopped seeing the SIM card on October 12. A bit like @rom4nb and @Xyguma except the date. Everything else worked fine AFAIK (here’s my original post with @petefoth kind tips just in case).
With no reaction from Iodé to my requests (e-mail, communauty, GitLab issue) other than Pete, I:
updated to iodéOS 4.17 on WiFi → same issue.
tried to downgrade to iodéOS 4.15 → RECOVERY screen "Can't load Android system (...) : Try again || Factory data rest"
Please note I have no XP using TWRP and almost none tinkering with Android builds in general. Am just the average FOSS guy with a decent linux / command line background so long I’m given a mechanic keyboard. Reason why I bought it already degoogled from Iodé Shopp.
Just want to point out that those links to the ROMs are for the XZ1 Compact, not the XZ1. You can’t use them on your XZ1.
It’s fairly easy to install TWRP and a custom ROM. It only seems complicated if you haven’t done it yet. You simply install a package or two from the Terminal, issue a few commands, and follow several simple instructions.
That said, I don’t have experience “converting” an iodé pre-installed device to a manually-installed setup, so I can’t provide input there.
If you really bought an XZ1 (poplar) from Iodé, then don’t install my ROM - it’s for XZ1 Compact (lilac): they are different phones - even though they share a common platform and a build for one model will not run on the other.
Whatever device you have, I would follow @rom4nb’s suggestion of flashing the stock Android ROM, then installing an Iodé build: the official v4 release if you have an XZ1, or my 5.0 release if you have an XZ1 Compact
EDIT: Looks like I made a 5.1 build for Poplar also - see here
EDIT 2: Before you start, you should back up as many of your apps and data as you can. Checkout the solutions in this wiki post. They won’t backup ‘EVERYTHING’ , but they are the best I’ve found
Got it @petefoth, so I’ll try your 5.1 build (iode-5.1-20240618-UNOFFICIAL-poplar_dsds-img.zip right?). Starting by
getting/flashing the stock SONY Android 9 ROM with XDA’s Newflasher,
then TWRP 3.7 official,
and then TWRP 3.6.2 by Yoshino. There’s no way over ADB, correct?
I have no idea how to backup my apps with the current status of my XZ1. Nor why I should give this any more time (all my pictures but a couple were trnasfered via ssh and the apps I use can be reinstalled via F-Droid on Wifi), yeah?
The phone you bought is an XZ1 (Poplar), officially supported. You need to download the iode 5.1 from the github site. The unofficial build (@petefoth ), is the unofficial build for the XZ1c (Lilac) which is not the phone you bought for the reasons that @petefoth described in his earlier post. I think that there is an installer for it too if you are uncertain how to proceed. The official version (Poplar) is accessed using the github link on the iode site. If there is an installer for it try it or use petefoth’s method.
For quite a while I have been using los4microg rather than IodéOS on my ‘daily driver’ device (mainly because I am maintainer of the los4microg project). A few days ago, my banking app (Nationwide UK bank) got an update which stopped it from working with LineageOS - both los4microg and official LIneageOS GApps (which my wife runs on her XZ1C). This is clearly a SafetyNet / Device Integrity issue, so I decided to try the latest IodéOS build.
Good news: the Nationwide app runs fine under IodéOS
Bad news: the battery consumption seems to be significantly worse runnng IodéOS than running los4microg. I charge my phone overnight, so it is always at 100% when I wake up (around 6:00).
on los4microg, in ‘normal’ use, the battery would last until around the time I go to bed (around 23:00), though battery saver would usually kick in (at 15%) a bit earlier
on IodéOS, battery saver seems to be kicking in early in the evening - around 18:00
This may be because I have been using my phone more, or it may be that IodéOS is using more battery when idle than los4microg. I have access to stats exported as .csv file from BatteryBot Pro from before and after the move to IodéOS, which I will look at to see if there is any obvious difference. If anyone else can provide similar stats (for either OS), I would be grateful if you could either attach them here, or contact me by private message for my email address.
Any other information that might help me get to the bottom of this issue is also welcome.
TIA
Pete
I also had tried and similarly had to transition to IodéOS for certain banking apps. While I can’t offer evidence to support higher battery usage under IodéOS, I can at least offer some hope that the problem isn’t guaranteed to occur just because you use IodéOS. I’ve been running your 2024-06-17 build for many months and I continue to have good battery usage. In fact, considering the age of the device itself, the battery health is frankly amazing.
The only thing I may have done differently than you is that I’m using Lineage Recovery Version 21.0 (20240620) rather than TWRP.
I think my battery drain issue was due to user error: a couple of weeks ago I set Screen timeout to 30 minutes (the maximum) to ensure a long-running task would complete, I’ve changed the timeout back to 1 minute (the default I think), and my battery life is back to expected levels (i.e. I can get though a full waking day with normal phone useage without needing to recharge).
Thanks for your help and sorry to have disturbed you
Hi all. @petefoth I am currently using the latest IodeOS built for XZ1C that was posted in this thread (from June 17th 2024). I was thinking new builds will be posted here as soon as you have time to make them.
I have 'dirty flashed the lilac build over the previous build with no problems so far. Dirty flashing over a LineageOS for microG build will probably not work.
Does it mean I can download iode-5.7-20241205-UNOFFICIAL-<device>zip from the other thread and dirty flash it with TWRP and adb sideload over the June build from this thread? Or were there other “intermediate” builds which I should flash step by step?
EDIT: I just noticed, the title of this thread is with a typo, right? It says “ZX1 Compact” but it should be “XZ1 Compact”, right? Can it be corrected?
I did the upgrade to iode-5.8-20241220-lilac.zip (I used this zip file as I used recovery and adb sideload and not fastboot).
In TWRP recovery, I used Advanced → ADB Sideload → checked “Wipe Dalvik Cache” and “Wipe Cache” and then did the sideload via adb -d sideload iode-5.8-20241220-lilac.zip
Reboot took some time, but it seems to work and now I am on security patch December 2024.
Thanks to you both @rom4nb and @petefoth
I didn’t realise that there were new updates. I did from iodé 5.1 to 5.8 directly by recovery. It worked. Same as rom4nb it took some time to reboot and the message app and thunderbird were not showing on the first reboot but on the second one everything was there so thanks a lot
I just updated to 5.8 and for some reason Aurora Store wants to update Google Play Services even though I obviously don’t have that installed. If I try to uninstall it in Aurora, then it asks for confirmation if I want to unstall microG services.
You need to add it to Aurora STtore’s ‘blacklist’, then you will no longer be offered udates for it
Thanks, @petefoth. I did suspect that, but hadn’t had to do this before (at least as far as I recall). I presume an inadvertent attempted update wouldn’t harm anything? It just seemed to fail and ask to be updated again.
Hi all and a big thank you to @petefoth for providing builds to our small community of ZX1 lovers. However, I have been repeatedly been running into a problem that I could not solve without completly reinstalling iode. The problem I had was that (apparently) all in a sudden my phone refused to connect to a mobile network and responded with “Service not available”. No matter what I did, I could not resolve this problem, so I had to reinstall iode now for the 4th time (This also means that it is very unlikely that this is a hardware defect). But at least I found the cause for this problem: Turning on flight mode and swithing it off again, seems to cause my SIM and/or mobile connection to fail. I am wondering if anybody else has experienced this and whether there is a remedy for this. TIA
