Kinda amusing seeing folks here talking about privacy and anti-censorship... only to later find out they still use cookphones, cookOS and/or faildows. And/or githubs of all sorts. And/or binance. And/or alexa or other "smart home" systems made by who knows who with who knows what. If this isn't hypocrisy, I don't know what is.

OK, I think it's time to do some more clarification. Since #GerdaOS keeps getting mentioned even here even years after it was effectively discontinued, I guess I can't just tell this ghost from the past to stop haunting me, but it's worth a try. GerdaOS was created as a response to a huge security bug in stock #KaiOS 2.5 where every webpage could run anything with root privileges on certain devices, including the one I had. And the only device I had at my disposal at the time was a Nokia 8110 4G TA-1048 (well, two of them), that's it. Besides customization and debloating, there also were several attempts to integrate some privacy features, but in the greater scheme of things, **they just were not enough** at all. While this might have looked like a breakthrough in 2019, it's 2024 now. The development of this custom ROM stalled a long time ago for three reasons. The first one was lack of my personal time and energy. The second reason was increasing inability to even port it to newer KaiOS-based Nokia generations, let alone other devices and non-Qualcomm platforms. The third (and probably most important) reason was... Lack of proper feedback. People, and I mean general public, didn't seem to get why I created it and why what was done was done. When WhatsApp appeared for KaiOS 2.5.1, they demanded backporting it to Gerda. When WhatsApp calling (implemented with a crutch-like third-party .so library as the AudioChannel API is broken beyond repair in 2.5.x) appeared in 2.5.2, they demanded backporting it to Gerda, and I couldn't do it anymore at that time already. I even remember someone being furious about GerdaOS not having KaiStore at all. Lol, how are you expecting a privacy-oriented distro to use apps and services that directly violate it? So, at first, I created some tools that achieved most of the tasks GerdaOS could but worked on a wider range of devices: Wallace Root, which evolved into Wallace Toolbox (and supports IMEI editing on 8110, rooted 2720 and several more phones), and — much later — CrossTweak (mainly for 2.5.2.2+ devices that are not rootable as easily without a boot partition swap). In addition, I also created FastContact and FastLog to replace the stock laggy phonebook and call log apps, and they also can work on a lot of 2.5.x devices. My last development was writing a Gopher client for KaiOS, Kopher. Then, I just quit. And recently, archived the GerdaOS landing page. Why? Because I realized that I had been solving the wrong end of the problem. KaiOS is flawed much deeper than anyone can manage. I can dedicate a whole another note to what was, and still is, wrong with KaiOS, and, sadly, it doesn't look like it will get any better anytime soon. So, whoever wants GerdaOS to return, I just want you to support postmarketOS porting to these devices instead. I heard there are working ports of pmOS to 8110 and 2720 already, as well as 6300 and even 8000. Maybe I'll try them myself, I have enough devices to tinker with. I know that these ports are maintained by talented people from our community, so I can vouch for them. Let the past be the past. Support the future: postmarketOS for these keypad smartphones. --- Luxferre ---

#nostrudel is noice too.

Featurephone IMEI editor codes ------------------------------ These secret codes have been tested on most non-Nokia featurephones manufactured since 2016. They open either the IMEI editor directly, or the engineering menu where it can be found (like "Para Set" - "Update IMEI Number" on Mocor-based phones). In some cases, you may be required to press the Call button after entering the code, so please test both options. ``` #*8378#1# *#0160# *#0161# *#5353# *#0066# *#1923# #*868*# *#4224876# *#1263# *#66# *#066# *#0011# *#1122# *#0623# *#0622# *#09# *#4634# *#4634*# *#868*# *#020*# *#1207# *#1208# *#2012# *#2013# *#9999# *#*#3646633#*#* *#93646633# *#64276# *#36*# *#2018*# *#44# *#0606*# *#*#067067# *#9981# *#1169*# #*8378#9# *#*#1122#*#* *#123456# *#1234567# *#2018+80003# *#91*# *#02# ``` This list will be updated from time to time but it already covers over 80% of cheap featurephones on the market. Bonus: For MediaTek-based featurephones (MT6260, MT6261, MT6276 chipsets) without secure boot, if you find a way to open a USB-COM connection, you can also use the following AT commands to update IMEIs (the change will take effect after rebooting the phone): For SIM1: AT+EGMR=1,7,"newimei" For SIM2, if present: AT+EGMR=1,10,"newimei" For SIM3, if present: AT+EGMR=1,11,"newimei" For SIM4, if present: AT+EGMR=1,12,"newimei" --- Luxferre ---

OK, now to the main topic. What I'm about to post probably won't be useful for USonians or anyone else with LTE/5G-only, but for the rest 3/4 of the globe, I hope it might be useful. Essentially, I'm gonna talk about featurephones that are true featurephones, i.e. not Androids in disguise (like KaiOS ones) and are now completely built upon non-smartphone hardware like MediaTek MT62xx or Unisoc (ex-Spreadtrum) SC6531x/SC770x/UMS9117(L). The UMS9117, btw, supports LTE, so chances are something like CAT B40 may work in 'murica too. Anyway, modern true featurephones are based on low-end MediaTeks/Unisocs, their firmware may contain some trojans (although I hadn't caught Nokia, Alcatel or CAT doing this) but also may contain an autonomous IMEI editor among their secret codes. So lemme repost my codelist and see how censorship-resistant this network truly is.

Well, satellite.earth looks dope while not slow in any way (for a bloated modern web client), the only inability being to edit relay list. And yes, please stop telling me that extensions (which, by design, can read any contents of any opened webpage) are more secure than pasting nsec. I won't buy this crap.

CloudFlare must die. Whenever I access sites "protected" by them with FireDragon/LibreWolf, I have a good chance of being stuck in a neverending loop of "are you human" verification. Whom are you really protecting?