Apparent serious regression in 6.7 "husky" build - cell data completely disabled/broken, works on downgrade to 6.6

General Discussion
1

I hope this is OK to post here. 1st time posting, if this needs to move please do.

BUG “ONE LINER”:

Mobile data never works on 6.7 (the rom within “iode-6.7-20250905-husky-fastboot.zip”)— calls OK, Wi-Fi OK, but data always shows disconnected / IWLAN. I’ve dug into it quite deeply to verify its likely a ROM bug/regression and try to rule out user error/SIM/provisioning/hardware issue. Downgrade to the rom within “iode-6.6-20250729-husky-fastboot.zip” fixes it.

BACKGROUND:

I just installed 6.7 latest OTA for Pixel 8 Pro (“husky”). It works brilliantly with one absolutely massive bug - mobile data seems completely broken, and it looks like it may be an iode build bug.

I can’t tell if this is all phones everywhere or just some, or UK only or whatever.

SYMPTOMS:

On Pixel 8 Pro (husky), iodéOS 6.7 latest official build fails to establish any mobile data connection.

Tested on both O2 UK and EE UK SIM cards in multiple locations 20 miles/30km apart.

The SIMs both work on other devices (Samsung note 10+ 5G “d2x” running iodeOS 4.x).

Voice calls and WiFi data work normally, but mobile data service always shows Disconnected and Data network type: IWLAN in the ##4636## phone info screen.

EVIDENCE ITS AN IODE ROM BUG, NOT USER ERROR/SIM/HARDWARE:

Identical behaviour across multiple networks. Multiple carriers tested: O2 UK and EE UK SIMs, both provide voice but no mobile data. New SIMs bought for testing.

Identical behaviour on different cell masts: tested in north and south london, 20 miles/30km apart.

SimS tested and work correctly on other devices: SIMs work and data connection works, with both SIMs on other devices.

APN verified: Correct APN entries newly created in O2 shop by O2 staff, as well as at home (mobile.o2.co.uk, everywhere for EE). Behaviour unchanged.

Network modes tested: Auto (NR/LTE/GSM/WCDMA) and LTE-only modes both tried. Still reports IWLAN, never LTE.

SIM provisioning confirmed: Same SIMs work with data in other devices.

Firmware verified: Latest Google factory image was downloaded from official Google site and flashed OTA to both slots, and verified as flashed after, before installing iodéOS 6.7, so modem and vendor partitions are current.

Baseband version displays correctly (not “unknown”).

About phone shows: baseband present, calls working so modem is functional.

Phone info screen shows: Voice service: in service (on UMTS/EDGE), Data service: disconnected, but data network type: IWLAN. This indicates the ROM isn’t even attempting packet-switched data attach.

SUSPECTED AREA OF ISSUE:

Regression in CarrierConfig / RIL stack on husky in iodéOS 6.7 (Android 15)?? Because IWLAN being reported as * default * bearer suggests the ROM is routing “mobile data” only through Wi-Fi (if enabled/connected), and never actually requesting PS attach from the modem.

Compare against older iodéOS builds where data works correctly.

STEPS TO REPRODUCE:

Flash latest Google official firmware via OTA/bootloader, and verify both slits flashed, correct ROM, and show as bootable.
Install iodéOS 6.7 latest, iode ROM only. ***
Insert O2 UK or EE UK SIM. Enable mobile data.
Observe: calls work, but mobile data never connects.
Check ##4636## → data service disconnected, network type IWLAN.

*** For clarity: the radio.img from the iodéOS package was not flashed. This was intentional and consistent with iodéOS/LineageOS installation guidance, since Pixels enforce anti-rollback on radio/bootloader partitions and flashing an older radio image risks permanently bricking the device. Instead, the latest official Google factory firmware (including modem/radio) was flashed to both slots before installing iodéOS. The current baseband version string confirms the radio firmware is up to date and active. Because iodéOS does not ship its own customised radio and expects users to retain the stock Google baseband, the lack of radio flashing should not be the cause of this issue. The fact that voice services work while packet data never attaches across multiple carriers, and that changing the ROM without changing the radio fixes it, strongly suggests the fault lies higher in the stack — in iodéOS’s RIL or CarrierConfig layer — rather than in the radio firmware itself.

EXPECTED / OBSERVED BEHAVIOUR:

Phone should attach to LTE/5G packet data network when mobile data is enabled, and data should work on O2/EE. But doesn’t.

Downgrading 6.7 back to 6.6 (keeping same radio, from latest official Google build) works fine “out of the box” on first boot.

1 Like
2

I am guessing you have looked here, but can you please confirm in the detailed APN settings that no proxy, port, etc. are being set that are unintended, as well as any possibly IPv6 / IPv4 settings change?

Also, as another inquiry, you mention that “Latest Google factory image” was flashed to both slots. Do you mean Android 16? iodéOS is expecting an Android 15 base, this can be reverted but you have to be careful to flash to both slots, following some warnings from this thread discussion:

https://xdaforums.com/t/may-2025-and-newer-beware-of-permanent-bricks-if-you-dont-handle-the-anti-rollback-bootloader-correctly-on-all-pixel-6-6-pro-6a-8-8-pro-8a.4735780/

That wouldn’t explain well why 6.6 works and 6.7 doesn’t, however. But still, wondering if you did have A16 on it before iode install?

3

New phone, came with BP3A sept 2025 (16.0.0 BP3A.250905.014 Sep 2025 hash c1761dd7e5d32476f8e9f23facbe566518731acf90afba90fb918308dca76957), so.its based on 16 not 15.

I OTA flashed that same firmware to the other slot before anything and verified - the anti.rollback models usually have one slot out of date and that’s a brick risk.

That said it doesn’t seem to change the issue. If anything strengthens it. Phone had radio and BL from 16, throughout, as I didn’t reflash / modify those when I flashed iode 6.7 * or * iode 6.6, and verified unchanged radio and BL (and same ROM) both slots after both, the slow way, by changing set_active, reboot, check what radio/BL/ROM active in each before continuing after flash.

So the same 16.0 radio worked “out of the box” with 6.6 (in all ways) but borked completely with 6.7 (on mobile data) whatever I or O2 staff tried, and never tried to do a data connection apparently even with a ton of trimmed.down settings like LTE only.

As to other questions - for 6.7, I checked APN data, in iode settings, in phone info 4636, I checked the settings such as MNC/MCC not shown in settings, and I had O2 staff in their shop check the settings. A new clean APN was created by me, and by them, on 6.7. No unusual settings, standard “well known” basics only, as well as checking all data for unbuilt APNs. Nothing for any. Port/proxy blank, used current mobile.o2.co.uk and o2web not older ones as confirmed by O2 staff, IPv4/6 all.as usual Confirmed correct as voice (and WiFi if that helps) both worked - but never mobile data. By comparison 6.6 voice * and * data worked instantly on same SIM out of the box, the moment I downgrade reinstalled the iode rom zip file (alone) from 6.7 to 6.6. Frankly I was jawdropped, figured it was some kind of “always been there” bug not a one version back regression. Grateful it was so recent.

4

The devs were able to confirm that mobile data is working fine with v6.8 beta (as it did with v6.7. v6.8 will be released in the near future, you could wait to try it when it is released to stable, or move to the beta.

But as installs that had the correct A15 base before installing iodéOS don’t exhibit the problem, I don’t have a lot of other suggestions. I am not denying you are experiencing the issue, and I can’t explain why v6.6 would work without issue but not with v6.7, but as it does have a base system not matching the requirements I don’t know if there is much else we can do.

1 Like
5

If 6.8 works that’s all it takes. (If not , then 6.6 is fine, I’ve been on 4.x for ages before this! Just needed to upgrade to get official husky compared to broken d2x!)

Well done and also, thank you for looking into it.