@Amarurtuuq Bengal is correct, it is the code name of the SoC (System on Chip) for this device, Billie2

@Amarurtuuq

@Amarurtuuq that's normal if you are installing from fastboot. Select your device from the drop down menu.

@Amarurtuuq OK hold the Volume up, Volume down and power together for about 40 seconds, that should turn the device off.

Just for your info, I had the same issue on one of my N100's. Charging it to 100% resolved the issue (for now, it is still working).

@Moem The banks in the UK are really pushing you to use their app. For example if you log in on a browser, it will push you to authenticate with your app on your phone or tablet. The banks have close the vast majority of counters and now run a service (no cash withdrawals) where a van goes from community to community on set days for all banks to cater for those who don't online bank. Likewise if you do need a big cash withdrawal (i.e over 1000 euros) then they question you like you are a naughty child. (Think of Greta Thunberg saying "how dare you withdraw your own money, how dare you!).

Then to work you now have to have an authenticator app and I have to have the M$ authenticator, no choice. If I don't have it I cannot get into works systems!

The UK is really going to rack and ruin......

@Amarurtuuq MSM Download tool is the tool (Windows only) used to flash a stock Android ROM onto this device. If the RAM chip has gone then this isn't worth doing as it can be finicky to get this device into EDL mode (Emergency Download mode) and it will unlikely not work.

To boot into recovery mode, where you can wipe cache, power off the device and hold volume down and power, when the device boots, release the power button, but hold the volume down button until it reaches recovery. If it won't reach recovery, leave it powered off on charge overnight and try again. If that fails it is battery or motherboard.

Things to try. Power off the device.

1. Boot int the bootloader (fastboot mode) and see if the PC recognises the device in a fastboot terminal.

2. See if it boots into recovery and if it does, wipe cache.

3. Power off the device and put it on charge and see if it charges up.

You may need to spend cash now if all the above fails.

If it still boots to this Qualcomm CrashDump Mode you may need to replace the battery.

If that fails, it is usually a RAM chip failure, either the chip has failed or it requires a reball/reflow or a replacement and it may be cheaper to get a broken use device or mainboard from Aliexpress and replace it.

From experience, most Qualcomm CrashDumps are due to a weak or low charge battery.

@k.nacke That will be the reason. 2Gb and less is not enough to run the system and Waydroid on any UT device.

@TheTrench You need to delve deeper into 5G and what 5G is, plus what Android version supports 5G on that device. 5G falls into two categories - 5G Non Stand Alone (NSA) and 5G (SA). 5G NSA piggybacks of the 4G LTE infrastructure end to end in simple terms. 5G SA is full 5G end to end. This can be affected by available networks, service providers, Android versions and vendor BLOBs and device hardware.

You cannot expect newer firmware files to work on an older version of Android without issues or just not working.

I bought a 5G device when 5G was in its infancy and always got 4G LTE indicated and 4G speeds. 5G has a better infrastructure now and it still shows 4G LTE in a lot of cases. My new device is 5G and always shows 5G and is a bit quicker, but not in all cases.

I got my (x2) BQ Aquaris 4.5 on the day of release. I spammed that buy button and got 2 before they all sold out. I used it as a daily driver for quite a bit (didn't Internet bank then or (have to) use Microsoft Authenticator) back then, the other was for demonstrating. Loved Scopes and would like to see them come back again. I still have one device (on Xenial) which will soon be defunct as a phone as 3G and 2G are going soon.

Read the porters notes here.

It looks like you have the T-Mobile version of the N100. You need to upgrade/downgrade to the stipulated firmware used by the porter.

Here is a similar story.

@messayisto I don't have that device to test, but if you have it, that is good to add it to this thread.

You need a Windows 10, or 11 machine to run the MSM tool:

"The procedure requires a computer running Win10 or Win11. Using a virtualized Windows is impossible."

This is the porters notes here.

You have to install the stipulated Android version or things won't work and you could brick the device.

• Asus Zenfone Max Pro M1

• F(x)tec Pro1 X

• Fairphone 3 and 3+

• Fairphone 4

• Fairphone 5 (new in this release)

• Google Pixel 3a and 3a XL

• JingPad A1

• Lenovo Tab M10 HD 2nd Gen WiFi / LTE (TB-X306F/TB-X306X)

• Oneplus 5 and 5T

• OnePlus 6 and 6T

• OnePlus Nord N10 5G

• OnePlus Nord N100

• Rabbit R1

• Volla Phone

• Volla Phone X

• Volla Phone 22

• Volla Phone X23

• Volla Phone Quintus

• Volla Tablet

• Xiaomi Poco X3 NFC / X3

• Xiaomi Poco M2 Pro

• Xiaomi Redmi 9 and 9 Prime

• Xiaomi Redmi Note 9

• Xiaomi Redmi Note 9 Pro/Pro Max/9S

The above list taken from the news blog indicates devices that will upgrade to 24.04 (Noble).

The following devices will NOT upgrade at the moment:

OnePlus 6 (on the above list)

OnePlus 6T (on the above list)

Xiaomi Mi A2

Lenovo Tab TB-X605F

Lenovo Tab TB-X605L

The above devices that won't upgrade (boot into recovery or hang at the initial splash screen) still get the upgrade notification pushed onto them and the upgrade can be selected on the UT installer.

If you do mistakenly choose the upgrade to Noble and it doesn't work, recover by booting manually to fastboot (the bootloader) and running it through the installer and choosing 20.04 leaving the Wipe Data box unticked.

Ok, to install on this device:

1. Boot into Android, enable Developer Options and enable OEM unlocking and USB debugging.

2. Ensure you are on Android 11 and your device is the 4Gb/64Gb version.

3. Open a terminal on the PC - if using Windows go to the folder where ADB and Fastboot.exe are and right click, Open in Terminal.

4. Plug the device into the PC and in the pop up window accept and then type in to the terminal on the PC, ADB reboot bootloader. This will boot you to fastboot mode.

5. Once in fastboot mode type in fastboot oem unlock or fastboot flashing unlock and follow the onscreen prompts. Once you have selected to unlock, the screen will freeze. Hold the power button and let the device reboot.

6. Set up Android again. Enable Developer Options and USB debugging.

7. Fire up the UT installer and follow the onscreen prompts. I suggest installing Stable 24.04.01. When it is installing, leave the tablet alone and allow it to do its thing.

@as1234 Thats the first bit. You then have to boot to fastboot and unlock it there running the command in terminal of the PC fastboot oem unlock

@as1234 Is your bootloader unlocked? What version of the tablet is it - 2Gb32Gb version or the 4Gb/64Gb version?

@rheomie Press power button and volume buttons together for at least forty seconds or until the device reboots. If not leave it on charge for a few hours and try powering up.

The system pushes the Noble upgrade to devices running on Focal, but don't seem to work with Noble. The specific example I am talking about is the Lenovo Tab TB-X605F/L 3Gb/32Gb version. The upgrade notification appears, upgrade and it just boots to recovery after installation. Running it through the installer results in the same thing. (Yes I know this tablet is a problem child). Would it be possible to stop this and/or remove the upgrade path for Noble from the installer?

(Similar things mentioned with the OP Nord N100 and OP Nord N10 5G, installer is fine with them).

Is the installer now working with Apple based Silicon Macs (M1 - M5) as Apple have just released the M5 version?

@robinsing the software fix does it for you, follow the instructions. You need to create an account or login with Facebook or Google account. You must also have your devices serial number to match the firmware.