<![CDATA[oneplus nord n100 not booting, dumps me into recovery]]>I used the firehose and installed OnePlus_Nord_N100_EU_OxygenOS_10.5.2.zip unlocked bootloader, used the installer. I got dumped into recovery. do i need to install firehose to both slots first?

]]>https://forums.ubports.com/topic/12327/oneplus-nord-n100-not-booting-dumps-me-into-recoveryRSS for NodeMon, 01 Jun 2026 20:36:03 GMTMon, 01 Jun 2026 18:17:42 GMT60<![CDATA[Reply to oneplus nord n100 not booting, dumps me into recovery on Mon, 01 Jun 2026 19:17:02 GMT]]>Any special reason why this is posted in Libertine when it's not about Libertine?

]]>https://forums.ubports.com/post/96246https://forums.ubports.com/post/96246Mon, 01 Jun 2026 19:17:02 GMT<![CDATA[Reply to oneplus nord n100 not booting, dumps me into recovery on Mon, 01 Jun 2026 18:40:36 GMT]]>device is BE83BA could it be because this "rev_OverSeas_201031_1929_release_OTA-BLOCK_Signed_fp2010311929_cve2020-10-05_ufs_Oxygen-OS-10.5.2.BE83BA" was included with bengal_14_E.05_201031.ops? if so and i remove it from the folder is that a brickable offence? lol the update could alter the fstab targets?

]]>https://forums.ubports.com/post/96245https://forums.ubports.com/post/96245Mon, 01 Jun 2026 18:40:36 GMT<![CDATA[Reply to oneplus nord n100 not booting, dumps me into recovery on Mon, 01 Jun 2026 18:29:40 GMT]]>it was on slot a when i installed 0]
<6>[19700104_06:34:51.811364]@0 pmi632_charger: default_irq_handler: IRQ: aicl-done
billie2:/tmp # cat recovery.log
cat recovery.log
[ 0.000118] I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 0.000173] recovery filesystem table
[ 0.000178] =========================
[ 0.000182] 0 /system ext4 system_a 0
[ 0.000185] 1 /vendor ext4 vendor_a 0
[ 0.000188] 2 /product ext4 product_a 0
[ 0.000191] 3 /odm ext4 odm_a 0
[ 0.000193] 4 /metadata ext4 /dev/block/by-name/metadata 0
[ 0.008259] 5 /data ext4 /dev/block/bootdevice/by-name/userdata 0
[ 0.013007] 6 /mnt/vendor/persist ext4 /dev/block/bootdevice/by-name/persist 0
[ 0.016726] 7 /misc emmc /dev/block/bootdevice/by-name/misc 0
[ 0.021798] 8 /storage/sdcard1 vfat /devices/platform/soc/4784000.sdhci/mmc_host* 0
[ 0.021814] 9 /storage/sdcard1 vfat /devices/platform/soc/1da4000.ufshc_card/host* 0
[ 0.021818] 10 /storage/usbotg vfat /devices/platform/soc/.ssusb/.dwc3/xhci-hcd..auto 0
[ 0.021822] 11 /vendor/firmware_mnt vfat /dev/block/bootdevice/by-name/modem_a 0
[ 0.025153] 12 /vendor/dsp ext4 /dev/block/bootdevice/by-name/dsp_a 0
[ 0.028834] 13 /vendor/bt_firmware vfat /dev/block/bootdevice/by-name/bluetooth_a 0
[ 0.032721] 14 /tmp ramdisk ramdisk 0
[ 0.032736]
[ 0.032742] W:DM_DEV_STATUS failed for system_a: No such device or address
[ 0.032747] E:Failed to find block device for partitionsystem_a
[ 0.032752] W:DM_DEV_STATUS failed for vendor_a: No such device or address
[ 0.032757] E:Failed to find block device for partitionvendor_a
[ 0.032761] W:DM_DEV_STATUS failed for product_a: No such device or address
[ 0.032766] E:Failed to find block device for partitionproduct_a
[ 0.032771] W:DM_DEV_STATUS failed for odm_a: No such device or address
[ 0.032776] E:Failed to find block device for partitionodm_a
[ 0.032780] I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 0.035381] I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 0.036372] I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 0.038601] Loading make_device from librecovery_ui_ext.so
[ 0.038620] I:vkeys: could not open /sys/board_properties/virtualkeys.touchpanel
[ 0.046870] I:Brightness: 1023 (50%)
[ 0.046890] Unknown format 875713089
[ 0.046897] Unknown format 875713089
[ 0.590296] erasing_text: en (91 x 38 @ 1365)
[ 0.593482] no_command_text: en (166 x 38 @ 1365)
[ 0.596183] error_text: en (66 x 38 @ 1365)
[ 0.604578] E:Failed to load bitmap cancel_wipe_data_text (error -1)
[ 0.604670] E:Failed to load bitmap factory_data_reset_text (error -1)
[ 0.604730] E:Failed to load bitmap try_again_text (error -1)
[ 0.604786] E:Failed to load bitmap wipe_data_confirmation_text (error -1)
[ 0.604843] E:Failed to load bitmap wipe_data_menu_header_text (error -1)
[ 0.634681] I:Starting recovery (pid 544) on Sun Jan 4 06:33:02 1970
[ 0.634722] I:
[ 0.634748] I:locale is [en-US]
[ 0.636311] SELinux: Skipping /product_file_contexts: empty file
[ 0.636380] SELinux: Skipping /odm_file_contexts: empty file
[ 0.636482] SELinux: Loaded file_contexts
[ 0.645049] [libfs_mgr]Invalid ext4 superblock on '/dev/block/bootdevice/by-name/userdata'
[ 0.645837] [libfs_mgr]__mount(source=/dev/block/bootdevice/by-name/userdata,target=/data,type=ext4)=-1: Invalid argument
[ 0.645870] recovery: [libfs_mgr]Failed to mount /data: Invalid argument
[ 0.646183] stage is []
[ 0.646206] reason is [(null)]
[ 0.646378] I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 1.305455] >
[ 1.326643]
[ 1.326695]
[ 1.328934]
[ 108.913374] Enabled ADB.
billie2:/tmp #

]]>https://forums.ubports.com/post/96244https://forums.ubports.com/post/96244Mon, 01 Jun 2026 18:29:40 GMT<![CDATA[Reply to oneplus nord n100 not booting, dumps me into recovery on Mon, 01 Jun 2026 18:25:03 GMT]]>@miketatts No, firehose is the flashing protocol, think of it as the software protocol that communicates with the attached device and PC and pushes the ROM data onto the device.

Your device is not the T-Mobile or Verizon US models?

If not try reinstalling UT to the device from the bootloader (manually selecting it from the drop down box).

If that fails, reinstall Android and try again.

]]>https://forums.ubports.com/post/96243https://forums.ubports.com/post/96243Mon, 01 Jun 2026 18:25:03 GMT