I have bricked my brand new BraX3 phone. How can I fix it?

Have you used --stock ?

python mtk-patched.py printgpt --plstage --stock --preloader ../files/BraX3-repair-tools/preloader_k6835v1_64_patched.bin --loader ../files/BraX3-repair-tools/DA_BR_patched.bin

GPT Table:
-------------
proinfo:             Offset 0x0000000000008000, Length 0x0000000000300000, Flags 0x0000000000000000, UUID 00000000-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
misc:                Offset 0x0000000000308000, Length 0x0000000000080000, Flags 0x0000000000000000, UUID 00000001-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
para:                Offset 0x0000000000388000, Length 0x0000000000080000, Flags 0x0000000000000000, UUID 00000002-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
expdb:               Offset 0x0000000000408000, Length 0x0000000008000000, Flags 0x0000000000000000, UUID 00000003-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
frp:                 Offset 0x0000000008408000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000004-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
nvcfg:               Offset 0x0000000008508000, Length 0x0000000002000000, Flags 0x0000000000000000, UUID 00000005-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
nvdata:              Offset 0x000000000a508000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 00000006-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
vbmeta_a:            Offset 0x000000000e508000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000007-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
vbmeta_system_a:     Offset 0x000000000ed08000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000008-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
vbmeta_vendor_a:     Offset 0x000000000f508000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000009-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
vbmeta_b:            Offset 0x000000000fd08000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000000a-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
vbmeta_system_b:     Offset 0x0000000010508000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000000b-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
vbmeta_vendor_b:     Offset 0x0000000010d08000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000000c-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
metadata:            Offset 0x0000000011508000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 0000000d-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
persist:             Offset 0x0000000015508000, Length 0x00000000032f8000, Flags 0x0000000000000000, UUID 0000000e-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
protect1:            Offset 0x0000000018800000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000000f-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
protect2:            Offset 0x0000000019000000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000010-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
seccfg:              Offset 0x0000000019800000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000011-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
otp:                 Offset 0x000000001a000000, Length 0x0000000002b00000, Flags 0x0000000000000000, UUID 00000012-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
pstore:              Offset 0x000000001cb00000, Length 0x0000000008500000, Flags 0x0000000000000000, UUID 00000013-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
md1img_a:            Offset 0x0000000025000000, Length 0x000000000c800000, Flags 0x0000000000000000, UUID 00000014-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
spmfw_a:             Offset 0x0000000031800000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000015-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
mcf_ota_a:           Offset 0x0000000031900000, Length 0x0000000002000000, Flags 0x0000000000000000, UUID 00000016-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
pi_img_a:            Offset 0x0000000033900000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000017-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
dpm_a:               Offset 0x0000000033a00000, Length 0x0000000000400000, Flags 0x0000000000000000, UUID 00000018-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
scp_a:               Offset 0x0000000033e00000, Length 0x0000000000600000, Flags 0x0000000000000000, UUID 00000019-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
vcp_a:               Offset 0x0000000034400000, Length 0x0000000000600000, Flags 0x0000000000000000, UUID 0000001a-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
sspm_a:              Offset 0x0000000034a00000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 0000001b-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
mcupm_a:             Offset 0x0000000034b00000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 0000001c-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
gz_a:                Offset 0x0000000034c00000, Length 0x0000000002000000, Flags 0x0000000000000000, UUID 0000001d-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
lk_a:                Offset 0x0000000036c00000, Length 0x0000000001000000, Flags 0x0000000000000000, UUID 0000001e-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
boot_a:              Offset 0x0000000037c00000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 0000001f-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
vendor_boot_a:       Offset 0x000000003bc00000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 00000020-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
init_boot_a:         Offset 0x000000003fc00000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000021-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
dtbo_a:              Offset 0x0000000040400000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000022-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
tee_a:               Offset 0x0000000040c00000, Length 0x0000000000500000, Flags 0x0000000000000000, UUID 00000023-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
connsys_bt_a:        Offset 0x0000000041100000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000024-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
connsys_wifi_a:      Offset 0x0000000041900000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000025-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
connsys_gnss_a:      Offset 0x0000000042100000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000026-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
sec1:                Offset 0x0000000042900000, Length 0x0000000000200000, Flags 0x0000000000000000, UUID 00000027-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
nvram:               Offset 0x0000000042b00000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 00000028-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
boot_para:           Offset 0x0000000046b00000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000029-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
dram_para:           Offset 0x0000000046c00000, Length 0x0000000001900000, Flags 0x0000000000000000, UUID 0000002a-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
logo_a:              Offset 0x0000000048500000, Length 0x0000000001300000, Flags 0x0000000000000000, UUID 0000002b-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
md1img_b:            Offset 0x0000000049800000, Length 0x000000000c800000, Flags 0x0000000000000000, UUID 0000002c-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
spmfw_b:             Offset 0x0000000056000000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 0000002d-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
mcf_ota_b:           Offset 0x0000000056100000, Length 0x0000000002000000, Flags 0x0000000000000000, UUID 0000002e-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
pi_img_b:            Offset 0x0000000058100000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 0000002f-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
dpm_b:               Offset 0x0000000058200000, Length 0x0000000000400000, Flags 0x0000000000000000, UUID 00000030-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
scp_b:               Offset 0x0000000058600000, Length 0x0000000000600000, Flags 0x0000000000000000, UUID 00000031-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
vcp_b:               Offset 0x0000000058c00000, Length 0x0000000000600000, Flags 0x0000000000000000, UUID 00000032-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
sspm_b:              Offset 0x0000000059200000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000033-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
mcupm_b:             Offset 0x0000000059300000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000034-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
gz_b:                Offset 0x0000000059400000, Length 0x0000000002000000, Flags 0x0000000000000000, UUID 00000035-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
lk_b:                Offset 0x000000005b400000, Length 0x0000000001000000, Flags 0x0000000000000000, UUID 00000036-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
boot_b:              Offset 0x000000005c400000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 00000037-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
vendor_boot_b:       Offset 0x0000000060400000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 00000038-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
connsys_bt_b:        Offset 0x0000000064400000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000039-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
connsys_wifi_b:      Offset 0x0000000064c00000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000003a-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
connsys_gnss_b:      Offset 0x0000000065400000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000003b-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
dtbo_b:              Offset 0x0000000065c00000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000003c-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
logo_b:              Offset 0x0000000066400000, Length 0x0000000001000000, Flags 0x0000000000000000, UUID 0000003d-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
tee_b:               Offset 0x0000000067400000, Length 0x0000000000500000, Flags 0x0000000000000000, UUID 0000003e-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
init_boot_b:         Offset 0x0000000067900000, Length 0x0000000000f00000, Flags 0x0000000000000000, UUID 0000003f-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
super:               Offset 0x0000000068800000, Length 0x0000000240000000, Flags 0x0000000000000000, UUID 00000040-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
userdata:            Offset 0x00000002a8800000, Length 0x0000003783ff8000, Flags 0x0000000000000000, UUID 00000041-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
mrdump:              Offset 0x0000003a2c7f8000, Length 0x0000000010000000, Flags 0x0000000000000000, UUID 00000042-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
flashinfo:           Offset 0x0000003a3c7f8000, Length 0x0000000001000000, Flags 0x0000000000000000, UUID 00000043-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

Total disk size:0x0000003a3d7fc200, sectors:0x000000001d1ebfe1
1 Like

DashGPS.net/brax3_2026_preloader_recovery.zip

–sha256 below-

brax3_2026_preloader_recovery.zip: 4827e345b16c7556178641b3784fb28371d699475d7427150be748c684b9c16e

preloader_2026_from_boot0.bin (inside the zip):

d9ec305e5cf8b786ba5f39cd1715f49e9e7eee903cc54ed490c581604a414661

1 Like

For info, I was able to repair my phone successfully :tada:

Thank you all, and especially to @daniel for sharing the right preloader.

@TheCanuckdian @Lazarus @lab26 @wouterx

Here is the process I used:

1. Flashing the preloader:

# boot1 (the slot the bootloader actually boots from)
mtk w preloader emmc_boot.bin \
    --parttype=boot1 \
    --plstage \
    --preloader preloader_2026.bin \
    --loader    DA_BR_patched.bin \
    --stock

# boot2 (the redundant slot — keep them in sync)
mtk w preloader emmc_boot.bin \
    --parttype=boot2 \
    --plstage \
    --preloader preloader_2026.bin \
    --loader    DA_BR_patched.bin \
    --stock

With:

  • preloader_2026.bin kindly shared by @daniel here, also available here, sha256: d9ec305e5cf8b786ba5f39cd1715f49e9e7eee903cc54ed490c581604a414661
  • emmc_boot.bin from here It is the above preloader correctly wrapped to be flashed on the phone. sha256: ba3bf676b27e70efeb05a200d9ba35089965ac7d4dc50e625866739abbab2b43
  • DA_BR_patched.bin from here, sha256: 21ab67dc6759b2726f11c2d734ba76f80a9077330bf48eea6b99726ed4bd6ffe
  • mtk from the plstage branch of this fork of mtkclient that supports --plstage (cf this pull request)

2. Flashing iodé 7.6 firmware

Warning: this erases nearly everything on the phone

mtk wo 0x308000 0x2a8f32200 flash.bin
    --plstage \
    --preloader preloader_2026.bin \
    --loader    DA_BR_patched.bin \
    --stock

With:

  • preloader_2026.bin: as above
  • DA_BR_patched.bin: as above
  • mtk: as above
  • flash.bin built from from the stock iodé 7.6 fastboot firmware using these scripts, a prebuilt version can be downloaded from here (sha256 of the zip: ec113dbba9526e0caa1d10cc1d210ea411f7575c7d844b9fdb7709efe8f22065, sha256 of flash.bin: 0c113c6da45a8d36221a42b45d259ac3dad3108f9d820d3f1daeb6b8c0bed2f6)
  • offset 0x308000, length 0x2a8f32200, formats and replaces all partitions, except proinfo (containing the serial number…) and partitions that follow userdata.
3 Likes

Good job! I’m impressed! :nerd_face:

1 Like

I left it untouched for the weekend.
With these steps, I got the device booting back into Iode. Great job! You can really see the power of the community. Now I just need to find the IMEI numbers again (found the IMEI numbers on the box); they’re no longer present on the device. Everything else seems to be back, including the Wi‑Fi and Bluetooth MAC addresses.

1 Like

Glad to read it worked for you.
The commands I mentioned don’t indeed reset the imei, but it was also reset before by “format all”. The doc for the imei is here (on my side I did not use it as I had a backup of the proinfo nvram partition):

EDIT (07/07/2026): In the first version of my post I incorrectly thought the imei was with the serial number in the proinfo partition. The serial number is indeed in the proinfo partition, but the imei is in the nvram partition.

U can’t be tracked by triangulating from cell towers now! :nerd_face:

I accidentally wiped my IMEI numbers many times and got them and the serial number restored successfully. I detailed it here but it seems to only work with Windows:

Thanks much! Your code is solving it for my case. Your step 1/step 2 resulted in the Brax3 becoming visible when connected to SPFlashTool again, for example, I ran the MemoryTest in SPFlashTool.

However, the display was still blank which was slightly confusing until I accidentally discovered the battery had fully drained in its boot looping days and the device would not power on by itself. The display is alive now, showing recovery mode (cannot boot android).

  • Which SPFlash image that is safe for “Format All + Download” on the new 2026 model BraX3? I see the Iode 7.5 has SPFlash files, is that what you would recommend?

  • Or, does anyone have the official manufacturing EOL image?

Since as yet, the device is i) only booting into recovery, and due to ii) connecting via USB to SP Flash tool the Download only option errors out with: “GPT layout change. FW upgrade or Format all first”

I am thinking I just need a full SPFlash with “Format all and Download”. I will proceed down this path soon but if you have tips that would be great.

@lab26 I am glad you were able to successfully flash the preloader.
If you want to use SP Flash tool, You can probably use iodé 7.5 indeed.
A’nd even though version 7.6 (0623) has a wrong CRC error in the zip file, it was reported to still work successfully.
Don’t forget to untick the preloader and its backup to avoid flashing the incompatible version.

I set up a Windows machine just for this. But no matter what I try, I can’t get any IMEI numbers on the phone. The tool detects the device and puts it into preloader/meta mode, but then it hangs at “Start searching kernel com port and handshake”.

I’ve tried everything: reinstalling drivers, rebooting, running as admin, and using different power-cycle options, different cables and different physical USB ports.. Maybe it’s just my limited Windows knowledge…

I’ve had that problem many times and it seems like there are 2 things that need to be done. First, get rid of the serial number if it is still there. Make note of it first. This is contrary to what Plamen said but I got stuck many times and this worked for me. Put it back into SPFlash and do a download and format all with this Lunar OS version:

Then get the phone ready again: enable developer mode and then enable USB debugging. Use adb devices and accept the device from your phone.

The second thing that u may not have done is turn off the phone lock screen. Power it off.

I took screenshots in Windows 10 of the SN Writer settings in this link:

Read through the SN Writer guide they posted here:

I may have forgotten things I tried but I made a lot of posts with screenshots everytime that happened, so if still stuck try searching IMEI and lazarus in advanced search! :nerd_face:

@divde @lab26 @daniel @Lazarus

It’s great to see that we actually have a solution to this problem. I’ve already sent my phone back and they’re processing my replacement as I speak. But at least I know I can attempt to root the device again, and won’t risk permanently bricking the device.

Does anyone have advice for how I should go about unlocking the bootloader and rooting the device, that would differ from the existing tutorial Brax provided? That process bricked my device last-time, but apparently that was due to a corrupt preloader. Has this been resolved?

Thanks for your help!

1 Like

@TheCanuckdian As documented in the unlock guide:

Due to a known Mediatek firmware issue, unlocking the bootloader can break over-the-air (OTA) update installs (slot b becomes unusable). If you keep the bootloader unlocked, plan to update by flashing full stock firmware (for example via SP Flash Tool) instead of OTA. If you want OTA updates to work, keep the bootloader locked.

Unlocking the bootloader when the device is on slot b causes a bootloop. A stock device boots on slot a, when we installed the OTA update, it started to boot on slot b, then we unlocked the bootloader and it had a bootloop due to the above Mediatek firmware issue.

The solution is to make sure we are on slot a before unlocking the bootloader.

The corrupt preloader was installed when we tried to solve the bootloop by doing “Format + Download” in SP Flash tool.

I have not yet been able to reprogram my IMEIs. The method to drop down to LunarOS and use SNWriter works on the 2025 BraX3 but does not work on the 2026 BraX3.

The steps I used overall were to recover via above instructions and push the @divde flash.bin that he built. For my device without valid userdata I then do a factory reset and this brings up Iode but without IMEIs.

To try to drop down to LunarOS I switched to use SPFlashTool but it needs matching partitions, so I could not use the scatter file in the LunarOS 6.0 download in this thread due to a mismatch on partitions and will halt the SPFlashTool.

In SPFlashTool, with LunarOS files loaded and matching partitions, use “Download Only” and UNCHECK preloader, UNCHECK preloader_backup, UNCHECK lk. I left the other items checked. After it finishes, boot the device. Let it boot on its own 3 times into recovery and do the factory data reset.

Then it boots LunarOS, however, my touchscreen is not working. I may try again or maybe since I have a 2025 BraX3 I could just program the IMEIs into that device, then extract the nvram/nvcfg/nvdata and push them to the 2026 BraX3.

If someone is running LunarOS on a newer 2026 BraX3 let me know.

@divde @lab26 @Lazarus @daniel @wouterx @mingor

I’m pretty pissed-off at the fact, that not one Brax representative has replied to this thread at all! This thread has been going for over a month now!!! This is absolutely unacceptable, especially when we’re asked to first report our issues on the forum before requesting further help.

Seeing as my RMA is currently being processed, it appears that the forum is not linked in any way to their primary support channel… @plamen appears to have been the only support tech on the forums, and even he’s been MIA for well over a month now!

This whole operation is clearly NOT a scam, but it sure feels like it sometimes… Just a real amateur operation that has been poorly managed from the onset… Sad.

2 Likes

My device is showing two IMEI numbers again … fingers crossed when i flash back to IodeOS.

I think my BraX3 is from 2026; I’ve had it for about a week now.

Starting from a working Iode(without IMEI numbers, but with a not connected working SIM card), after booting , where I first had to wipe userdata (factory reset) I only checked the settings to see whether the IMEI numbers were present.

Using SP Flash Tool, with LunarOS 6.0 files loaded and matching partitions, I selected “Download Only” and unchecked Preloader, Preloader_backup, and LK. I left the other items checked. After that, the device booted into factory reset and then started LunarOS.

I also had no touchscreen, so I connected a mouse via USB-C to check Settings to see whether the IMEI numbers were present.

With SNWriter, I finally got a “PASS.” After restarting, again with my mouse, immediately the notifications came in and my IMEI numbers appeared correcttly in Settings.

1 Like

@wouterx Keep a backup of the nvram partition (even before flashin iodéOS) to avoid having to do that again!

I did it with Magisk. Follow this:

I am now uncertain of the first gen BraX3 phones are the same as the second gen BraX3 phones since people here are having trouble with things that worked for me on a BraX3 from last year.

Exactly-poorly managed operation! :+1:

It seems we have Droidian as an option now on the BraX3 thanks to work done by @daniel HERE:

@tech-support should make Droidian into a Linux install option like Ubuntu Touch was!