Fun with Flipper Zero

I’m trying to play around more with my Flipper Zero, especially since I came across info on custom firmware to unlock some extra features with the device. The install was extremely simple, just using the qFlipper application to flash the CFW: GitHub: RogueMaster / flipperzero-firmware-wPlugins.

There were a few extra steps to take after flashing, but as long as you read the instructions provided, it should work fine. I still have to play around with it a bit & see what else I can do with it, but I will definitely be reading \ loading most of what’s available through RogueMaster‘s awesome-flipperzero-withModules GitHub repo.

I haven’t actually played any of the included games or used the Game Mode, but since I’ve seen some questions in the Discord asking how to disable it (despite it being in the instructions 😉 ) I figured I would also include it here for reference: UP UP DOWN DOWN LEFT CENTER LEFT CENTER
That looks somewhat familiar 😉

EDIT20220715-1913: SMc: Also want to make note of this:
/r/FlipperZero: WiFi Dev Board with Marauder firmware

Fun Projects: Ubuntu Touch & LuneOS

Two things I’m currently working on:
Ubuntu Touch on my old Nexus 6P, just to see how it’s coming along. I did need to reference this comment in order to get mine booting properly.
LuneOS on my old HP TouchPad… Which is giving me some problems. It started off rough because I was trying to find some files that were released between 2011-2014, & then trying to get them running… Then once I finally got that done, I still wasn’t able to get LuneOS to boot. Here are some of the files I collected while working on this:

➜  webOS ls -lah
total 4503576
drwxr-xr-x  17 smc  staff   544B Aug 25 21:43 .
drwx------+  7 smc  staff   224B Aug 25 22:00 ..
-rw-r--r--@  1 smc  staff   6.0K Aug 25 21:43 .DS_Store
-rw-r--r--@  1 smc  staff   268M Aug 23 22:17 HP_webOS_SDK-Win-3.0.5-676-x64.exe
-rw-r--r--@  1 smc  staff   264M Aug 23 22:18 HP_webOS_SDK-Win-3.0.5-676-x86.exe
-rw-rw-rw-@  1 smc  staff   224K Aug 25 18:11 UniversalNovacomInstaller-1.3.jar
-rw-r--r--@  1 smc  staff   354M Aug 25 21:42 luneos-dev-image-tenderloin-20170430092844-stable-050-86.rootfs.tar.gz
-rw-r--r--@  1 smc  staff   354M Aug 25 21:43 luneos-dev-image-tenderloin.tar.gz
-rw-r--r--@  1 smc  staff   369M Aug 25 21:39
drwxr-xr-x@  4 smc  staff   128B Aug 24 19:39 moboot_038-tenderloin
-rw-r--r--@  1 smc  staff   185K Aug 24 19:38
-rw-r--r--@  1 smc  staff    60K Aug 25 18:34
-rw-r--r--@  1 smc  staff    11M Aug 23 22:06
-rw-r--r--@  1 smc  staff   341M Aug 23 22:19 palm-sdk_3.0.5-svn528736-pho676_i386.deb
-rw-r--r--@  1 smc  staff   6.4M Aug 25 21:40 uImage--3.0.101-20161117-94-r0-tenderloin-20170430092844-stable-050-86.bin
-rw-r--r--@  1 smc  staff   9.2M Aug 24 19:39 uImage.LuneOS
-rw-r--r--@  1 smc  staff   223M Mar  8  2012 webosdoctorp305hstnhwifi.jar
➜  webOS

webOS Resources

Just making note of some webOS tools \ resources that could be useful as I start playing with my HP TouchPad (Tenderloin) again. Specifically, I want to install LuneOS on my device.

➜  webOS ls -lah
total 744704
drwxr-xr-x  5 smc  staff   160B Aug  9 22:53 .
drwx------+ 8 smc  staff   256B Aug  9 22:53 ..
-rw-r--r--@ 1 smc  staff   352M Aug  5 11:11 Palm_webOS_SDK.
-rw-r--r--@ 1 smc  staff    12M Aug  5 12:09 WebOSQuickInstall-4.6.0.jar
-rw-r--r--@ 1 smc  staff    78K Aug  5 11:27
➜  webOS sha256 *
SHA256(Palm_webOS_SDK. c2cd8346fd8e92e7090766652160879b0416ee1d4922d4942159c8c33442464f
SHA256(WebOSQuickInstall-4.6.0.jar)= 3dec2ca6b724a763a69019c6e0ed1803f4a12e8809bbe79eb80595b7819d5d00
SHA256( 9cdbef200daf21ea33fff883ac42809c80a204d7d562aa5ec6126b3fbaa728fd
➜  webOS Needed this version because it has options included for LuneOS.
WebOSQuickInstall-4.6.0.jar: I didn’t actually need this, but downloaded it because I was nostalgic.

So WordPress is giving me an issue when I try to actually upload a ZIP of the above (I can appreciate them not wanting me to upload DMG or JAR files), but I keep just getting a generic error when I upload the ZIP. This is mainly for my own reference anyway, but if anyone else is reading this, feel free to reach out & I can send you what I have.

EDIT: 20210810-1019: Just making note of some helpful links, that are currently still active right now (one with SSL errors, but the site still works):
– GitHub: WebOS Internals
WebOS Internals

Reasons why I run a network-wide adblocker…

In the last 24 hours…

Screenshot from Pi-Hole dashboard

For anyone else looking to run a network-wide adblocker, I recommend Pi-Hole. I have also recently started testing out AdGuard Home & will see in the long run if I decide to switch, or just leave it as a backup.

I run Pi-Hole as my primary DNS & DHCP server with an excessive number of blocklists (totaling ~4.5m blocked sites) & have no issues with it. I only started looking into AdGuard Home after a resource issue on my original Pi-Hole (it seems when I added Resilio Sync to my Pi, the system would lock up). So, I decided to replace RasPi 3 B+ with a RasPi 4, 8GB, & turn the original 3+ into the secondary AdGuard DNS server.

I definitely do like the AdGuard Home interface better than Pi-Hole, but will see if there’s actually enough there that will make me want to switch off Pi-Hole once & for all, or as my primary.

Goodbye Google Fi & Android

I find it pretty ironic that Google Fi is the reason I’m leaving Android as well. Whether it’s because of an actual Fi issue or juts a tower issue in my area, that caused me to finally switch off of Fi (something I’ve been meaning to do anyway), & I decided to switch to an iPhone to get more use out of my phone, but also so I could actually still communicate with some people on iMessage.

I guess I’ll also be looking into jailbreaking some more, especially since the phone I’m using for now is vulnerable to Checkra1n.

Super Mario 64 Natively on Android

Found a post on XDA about building Super Mario 64 for Android using Termux, & figured I’d try it out for fun.
Source: XDA Developers: Super Mario 64 can be natively run on Android without a Nintendo 64 emulator

Their instructions worked fine, so below is really just a copy & paste from the XDA post:

➜  ~ pkg install git wget make python getconf zip apksigner clang
Checking availability of current mirror: ok
Reading package lists... Done
Building dependency tree       
Reading state information... Done
apksigner is already the newest version (29.0.2-5).
clang is already the newest version (10.0.1-2).
getconf is already the newest version (0.5-1).
git is already the newest version (2.28.0).
make is already the newest version (4.3-1).
python is already the newest version (3.8.5).
wget is already the newest version (1.20.3-3).
zip is already the newest version (3.0-5).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
➜  ~ cd Development 
➜  Development git clone
Cloning into 'sm64-port-android'...
remote: Enumerating objects: 15616, done.
remote: Total 15616 (delta 0), reused 0 (delta 0), pack-reused 15616
Receiving objects: 100% (15616/15616), 22.76 MiB | 5.71 MiB/s, done.
Resolving deltas: 100% (7567/7567), done.
➜  Development cd sm64-port-android 
➜  sm64-port-android git:(master) cp ~/storage/shared/Super\ Mario\ 64\ \(USA\).z64
➜  sm64-port-android git:(master) sha256 
The program openssl is not installed. Install it by executing:
 pkg install openssl-tool
➜  sm64-port-android git:(master) pkg install openssl-tool
Checking availability of current mirror: ok
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 185 kB of archives.
After this operation, 643 kB of additional disk space will be used.
Get:1 stable/main aarch64 openssl-tool aarch64 1.1.1g-4 [185 kB]
Fetched 185 kB in 0s (214 kB/s)    
Selecting previously unselected package openssl-tool.
(Reading database ... 14219 files and directories currently installed.)
Preparing to unpack .../openssl-tool_1.1.1g-4_aarch64.deb ...
Unpacking openssl-tool (1.1.1g-4) ...
Setting up openssl-tool (1.1.1g-4) ...
➜  sm64-port-android git:(master) sha256   
SHA256( 17ce077343c6133f8c9f2d6d6d9a4ab62c8cd2aa57c40aea1f490b4c8bb21d91
➜  sm64-port-android git:(master) md5sum 
➜  sm64-port-android git:(master) ./
~/Development/sm64-port-android/SDL ~/Development/sm64-port-android
--2020-09-20 11:56:47--
Resolving 2604:a880:1:20::181:e001,
Connecting to|2604:a880:1:20::181:e001|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6784187 (6.5M) [application/zip]
Saving to: ‘’                       100%[=======================================================================>]   6.47M  5.65MB/s    in 1.1s    

2020-09-20 11:56:49 (5.65 MB/s) - ‘’ saved [6784187/6784187]

➜  sm64-port-android git:(master) make --jobs 4
cp build/us_pc/ build/us_pc/
apksigner sign --cert certificate.pem --key key.pk8 build/us_pc/
➜  sm64-port-android git:(master) ls   Makefile.split  assets           charmap.txt       enhancements       key.pk8  text
CHANGES       assets.json      charmap_menu.txt  levels         sm64.ld       textures
Dockerfile   SDL      data          lib    tools
Doxyfile     actors          bin       undefined_syms.txt
Jenkinsfile  android         build            rsp            sound
Makefile     asm             certificate.pem  doxygen           include     src
➜  sm64-port-android git:(master) ls build 
➜  sm64-port-android git:(master) ls build/us_pc 
actors  bin   endian-and-bitwidth  lib         rsp          src   textures
assets  data  include              levels  sound                         text
➜  sm64-port-android git:(master)
Super Mario 64 running natively on my OnePlus 7 Pro.

OnePlus 7 Pro: Update System Firmware on Custom ROM

Follow up to the OnePlus 7 Pro: LineageOS+MicroG post, where I mentioned I would have to update the Bluetooth & Modem firmware on my device. This fortunately went as smoothly as the LineageOS+MicroG install, so I’m very happy about that.

The first step was downloading the latest OxygenOS ZIP through this post: XDA Developers: [ROM][STOCK][FASTBOOT][OP7P] Stock Fastboot ROMs for OnePlus 7 Pro/ 7 Pro 5G by mauronofrio. The specific ZIP i pulled down from Android File Host was “”. From there, it was just a simple matter of extracting that,, & flashing the bluetooth.img & modem.img files:

➜  Downloads cd 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61-FASTBOOT/images
➜  images file bluetooth.img
bluetooth.img: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "MSDOS5.0", Bytes/sector 4096, sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 3, sectors/track 63, heads 255, sectors 16384 (volumes > 32 MB), serial number 0xbc614e, unlabeled, FAT (16 bit)
➜  images file modem.img
modem.img: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "MSDOS5.0", Bytes/sector 4096, sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 10, sectors/track 63, heads 255, sectors 76800 (volumes > 32 MB), serial number 0xbc614e, unlabeled, FAT (16 bit)

➜  images adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
➜  images adb devices
List of devices attached
1234abcd        device
➜  images adb reboot bootloader
➜  images fastboot devices
1234abcd        fastboot
➜  images fastboot flash bluetooth_a bluetooth.img
Sending 'bluetooth_a' (828 KB)                     OKAY [  0.030s]
Writing 'bluetooth_a'                              OKAY [  0.005s]
Finished. Total time: 0.049s
➜  images fastboot flash bluetooth_b bluetooth.img
Sending 'bluetooth_b' (828 KB)                     OKAY [  0.032s]
Writing 'bluetooth_b'                              OKAY [  0.005s]
Finished. Total time: 0.050s
➜  images fastboot flash modem_a modem.img
Sending 'modem_a' (161700 KB)                      OKAY [  4.308s]
Writing 'modem_a'                                  OKAY [  0.633s]
Finished. Total time: 4.954s
➜  images fastboot flash modem_b modem.img
Sending 'modem_b' (161700 KB)                      OKAY [  3.769s]
Writing 'modem_b'                                  OKAY [  0.696s]
Finished. Total time: 4.480s
➜  images fastboot reboot
Rebooting                                          OKAY [  0.002s]
Finished. Total time: 0.002s
➜  images

OnePlus 7 Pro: LineageOS+MicroG

After a full weekend of originally getting CrDroid on my new OnePlus 7 Pro a few months back, I decided to switch to LineageOS+MicroG because I was never able to get location working on CrDroid. This was mostly due to the changes in Android 10, but when I was still unable to get it working with the new UnifiedNLP package, I just decided it was easier to switch & settled for reinstalling MicroG, which I had avoided on CrDroid because I wanted to avoid as many Google services as possible.

Since I had so many issues getting CrDroid setup in the first place (mainly due to me lack of experience with A\B partitions & not knowing I needed to flash OxygenOS first, then the ROM on top of it), I wanted to keep track of the exact steps I took to get LineageOS+MicroG so I could follow it the next time I decide I want to try a new ROM. Posting it here just makes it easier to come back to & maybe it will help out someone else.

First step was just backup & prep: Making sure I had backups of my messages, F-Droid repositories, 2FA tokens, as well as my list of installed apps.

One thing I was surprised at for the installation was that I wasn’t expected to flash an OxygenOS ROM first… Below are the two “guides” i followed:

This one specifically included when to flash Magisk:
XDA Developers: [ROM]-[10-04-2020]-[microG] Unofficial LineageOS 17 w/ microG support by gigatex

Flashing Recovery: I thought this was one place where I had issues, but that may have only been on the Essential Phone, where I couldn’t boot recovery. that did work on the OP7Pro:

➜ OP7Pro adb reboot fastboot
➜ OP7Pro fastboot devices
0810d6ea fastboot
➜ OP7Pro fastboot boot twrp-3.4.0-0-guacamole.img
Sending 'boot.img' (31704 KB) OKAY [ 0.742s]
Booting OKAY [ 0.106s]
Finished. Total time: 0.886s
➜ OP7Pro

Once I was booted into TWRP I formatted DATA & pushed the LineageOS+MicroG & TWRP installer ZIPs, then rebooted to recovery again (without flashing anything). I ended up having to push the two ZIPs again because they were not present on the “SD Card” after the reboot. After pushing the files again I flashed & rebooted the system to complete setup.

An issue I did run into with Magisk appeared to be due to the A\B slots again. The fix seemed to be flashing when getting into TWRP, then manually changing the A\B slot, rebooting to recovery, & flashing again. Just a simple “Reboot > Recovery” didn’t change the slots.

I did just attempt a system update yesterday, & it was successful, following the same process I took during CrDroid: Use the internal updater, but DO NOT REBOOT through the updater. You have to go into Magisk Manager > Magisk Install > Install > Install to Inactive Slot (After OTA). You can then reboot & will still be rooted with Magisk.

I will have another update shortly about updating firmware, since I just noticed this morning that Bluetooth will not stay enabled. While on CrDroid the fix seemed to be flashing Bluetooth & Modem firmware from an official OxygenOS update.

Custom ROM on Mi MIX 3

I recently picked up a Xiaomi Mi MIX 3 & was able to unlock the bootloader after the 72 hour waiting period. That wasn’t a problem, however getting TWRP up & running was where I had a problem.

For some reason, whenever I would flash TWRP, but device was stuck in a fastboot loop — could not reboot out of it, boot the TWRP image, or any other method of exiting fastboot. I finally got TWRP working properly after flashing perseus_global_images_9.5.17_20190517.0000.00_9.0 _global_134d3070e5.tgz. I tried flashing one of the China ROM’s, & that was of no help.

Since this was turning out to be nothing close to simple like other devices, I was then running into an issue flashing NanoDroid after my ROM. That one seemed to be related to the /system partition not being found. It looks like my partition was instead mounted as /system_root, but the NanoDroid install script was looking for /system. Managed to fix that as well:

Results of mount:

/dev/block/sde48 on /system_root type ext4 (rw,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)

Remount /system_root as /system:

perseus:/ # mount -o bind /system_root/system /system

Taking a look at\CommonInstaller: Lines 248-252:

if [ -f /system/init.rc ]; then
mkdir /system_root 2>/dev/null
mount –move /system /system_root
mount -o bind /system_root/system /system

Once NanoDroid was working, I then needed to double check how to restore my backed up Signal messages: Signal: Backup & Restore Messages.