@Lindisfarne You do not need to root the device. OEM unlocking is not necessary at this stage. You need a Windows PC (running Windows) and you need to download one of the Android ROMs on the devices page for that device, unzip it and find the MSM Download tool. Please read here to understand how to use the Tool and take your time. Once the tool has finished flashing, the device will reboot, then you can set up Android, unlock the bootloader , set up Android again and then install UT. I have not got the MSM Download tool to run on Linux or in a Virtual Windows machine within Linux.

@MrT10001 To be honest, I have no idea. I know it says Bengal in the fastboot menu and this Billie2 version of Ubuntu Touch says it is Bengal when I try to install it; that's why I was kind of confused.

@irnbru That is correct, the device is "Billie", but the Other names is to do with something else.

@Kamil [image: 1746179214447-screenshot20250502_114518137.png]

@MrT10001 yeah but having a desktop mode but cannot use mouse to the full sucks.

@stanwood ok thank you

@bdomecq said in wi-fi scan: Do you believe that this wi-fi issue is due to the fact the device is the 't-mobile' variation? Could well be the issue.

@kugiigi OK. Anyway, thank you.

@davidm90 the problem in mine was different since the device is a 't-mobile variation', which required that very specific xml modification that I mentioned above.

@domubpkm no go, the developer doesn't know how to do it and unfortunately I am not able to contribute.

@MrT10001 Thanks for the reply I will try the MSM tool, lets see if it works from Virtualbox with USB passthrough, after if backed up all block devices with dd. Will report back.

@nonobike It should work ! Please, take a look a these issues and their solutions. https://github.com/fredldotme/snapz0r/issues

@Timespansoul Its now fixed with the patch to reenable ims services.

@stanwood Thank you for the update. I went back and did some more research and needless to say, I'm less than impressed with the knowledge of the ATT people I spoke to at the store. You're right that 4G isn't going away and the way they built 4G, its basically the backbone for 5G technology so not sure if the ATT people were just fear mongering, or just didn't want to deal with an OS that was clearly very unfamiliar to them. Its good to know UT is continuing to work on this problem. I really liked the OS. The simplicity of it, the lack of apps and ability customize it. Not to mention, its very snappy, even on older, under powered phones like the N100. I know my post sounded negative, but I'm not giving up yet, I see a lot of potential for this OS and will continue to work it. Thanks again for the update.

@moaner said in Oneplus Nord N100 boot failure: I'll speak for myself as i wish. If you don't like it then throw me out or block me We can do that. Please consider this your official warning. You can either play nice, or play elsewhere.

Thank you both, I found it: echo 10 > /sys/devices/platform/soc/5e00000.qcom,mdss_mdp/backlight/panel0-backlight/brightness - this is how I can manually change the brightness... Next I'll see if I can modify somewhere the minimum value that the slider can adjust so that I will use the slider in the brightness menu and not the command line.

You know what? - just before uninstalling it I checked it again and, upon activation, it worked! Maybe meanwhile I restarted the phone but I'm sure I restarted it before and it didn't help... Anyway, I'm very glad it works now! Thank you!

This is what I did and I have now a working device! Thank you for the push

@AppLee ok. I try to experiment .