[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]

[sd_shadow]

Has anyone used this on T-Mobile Model: BE2025 "lito"?

​

 

[BTK19]

Yes i have

 

[sd_shadow]

Yes i have

Thanks!
Worked Great!

 

[BTK19]

Welcome

 

[JazzieBoi]

Has anyone used this on T-Mobile Model: BE2025 "lito"?

​

What is strange to me is that It says product_name - "lito" when i boot to fastboot. Even though I have a Glo BE86AA.

 

[ninjasinabag]

What is strange to me is that It says product_name - "lito" when i boot to fastboot. Even though I have a Glo BE86AA.

They're all lito. That's the specific design of phone.

BE86AA is just the firmware version.
Be2025 is model version for the metrobytmobile device.

 

[R3D RUM]

Need assistance please. I've unlocked the bootloader. Now trying to root. But unsure where to start. Really new to this.

 

[boom15]

Need assistance please. I've unlocked the bootloader. Now trying to root. But unsure where to start. Really new to this.

Root N10 using Magisk

Warning: I'm not responsible for any damage or bricked phones! Mirror for all OxygenOS images General Info: You need adb and fastboot installed and should know how to use it TWRP is not needed You must do this process only once...

forum.xda-developers.com

 

[R3D RUM]

Root N10 using Magisk

Warning: I'm not responsible for any damage or bricked phones! Mirror for all OxygenOS images General Info: You need adb and fastboot installed and should know how to use it TWRP is not needed You must do this process only once...

forum.xda-developers.com

Where do you find out which build to use?

 

[Japexz]

Works great thanks

 

[n10tetris]

Can someone please summarize answers to a few questions regarding this recovery? It's hard to tell from
questions and answers through this thread - 1) Is the SD card issue totally resolved now? 2) Is restoring a backup made from this recovery working? If restoration isn't working, is it possible to take the backup files created and selectively restore portions by extracting the parts you might need from them?
So far no one has responded, anyone that has used this, please reply on if the backups can be restored and if the SD card issue has been fixed?

 

[zuhaibsarwar]

Hello anyone here. Can anyone help us to make twrp for Redmi note 11 Pro viva mtk user or help us to extract boot. Img so we can make twrp ourselves

 

[Fedon]

Hello anyone here. Can anyone help us to make twrp for Redmi note 11 Pro viva mtk user or help us to extract boot. Img so we can make twrp ourselves

i dont have this device now, but i can exract boot.img . Give me (rom what you need) link and i can extract boot.img for you

 

[OdinVex]

@EduardoA3677, I forked your TWRP device project on GitHub and made modifications to get it working on billie8/billie8t devices. If you can find the time to give it a quick look, I'd be willing to test. The dtb, Image.gz, and recoverydtbo are from the stock OnePlusN10Oxygen_14.O.37_OTA_0370_all.

 

[twindragon6]

I'm interested in building twrp, how did you go about this? I want to make a build that has functional touch (It's not working on the BE2026) but am confused as to where to start.

 

[OdinVex]

I'm interested in building twrp, how did you go about this? I want to make a build that has functional touch (It's not working on the BE2026) but am confused as to where to start.

They haven't been online in over a year. :/

 

[twindragon6]

They haven't been online in over a year. :/

Hmm... Well... I guess I'll figure it out.

I'm thinking that the issue is missing drivers/libs that aren't included in the recovery or boot partitions due to the fact that the device just doesn't use touch when it's in recovery or fastboot. This is a newer device with A/B partitions and a Super. I'm wondering if the missing drivers/libs are actually in the super and not accessible to TWRP for some reason at boot; so they should be included in the build process for TWRP. The only source code available is for the kernel and sound.

GitHub - OnePlusOSS/android_kernel_oneplus_sm6350

Contribute to OnePlusOSS/android_kernel_oneplus_sm6350 development by creating an account on GitHub.

github.com

GitHub - OnePlusOSS/android_vendor_qcom_opensource_audio_kernel_sm6350

Contribute to OnePlusOSS/android_vendor_qcom_opensource_audio_kernel_sm6350 development by creating an account on GitHub.

github.com

I'm thinking I'll have to dump the whole rom/phone and find/reverse enginer the boot process. Maybe look for missing drivers/libs for touch support.


For the OnePlus Nord N10 5G - BE2026 - Firmware Version 11.0.8.BE86AA

C:\platform-tools>adb shell ls -la /dev/block/bootdevice/by-name/
total 0
drwxr-xr-x 2 root root 2260 1971-04-12 07:36 .
drwxr-xr-x 3 root root 2220 1971-04-12 07:35 ..
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 ALIGN_TO_128K_1 -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 ALIGN_TO_128K_2 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 abl_a -> /dev/block/sde8
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 abl_b -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 abl_log -> /dev/block/sde64
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 aging_kernel -> /dev/block/sde61
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 aging_mod -> /dev/block/sde62
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 android_log -> /dev/block/sde66
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 aop_a -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 aop_b -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 apdp -> /dev/block/sde48
lrwxrwxrwx 1 root root 41 1971-04-12 07:36 bluetooth -> /dev/block/bootdevice/by-name/bluetooth_a
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 bluetooth_a -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 bluetooth_b -> /dev/block/sde28
lrwxrwxrwx 1 root root 36 1971-04-12 07:36 boot -> /dev/block/bootdevice/by-name/boot_a
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 boot_b -> /dev/block/sde34
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 carrier -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 catecontentfv -> /dev/block/sde75
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 catefv -> /dev/block/sde74
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 cateloader -> /dev/block/sde55
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 config -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 core_nhlos_a -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 core_nhlos_b -> /dev/block/sde45
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 devcfg_a -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 devcfg_b -> /dev/block/sde35
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 devinfo -> /dev/block/sde46
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 dip -> /dev/block/sde47
lrwxrwxrwx 1 root root 35 1971-04-12 07:36 dsp -> /dev/block/bootdevice/by-name/dsp_a
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 dsp_a -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 dsp_b -> /dev/block/sde32
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 dtbo_a -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 dtbo_b -> /dev/block/sde40
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 featenabler_a -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 featenabler_b -> /dev/block/sde41
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 frp -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 fsg -> /dev/block/sdf4
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 hyp_b -> /dev/block/sde26
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 hyp_log -> /dev/block/sde68
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 imagefv_a -> /dev/block/sde18
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 imagefv_b -> /dev/block/sde42
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 kernel_log -> /dev/block/sde65
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 keymaster_a -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 keymaster_b -> /dev/block/sde33
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 keystore -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 limits -> /dev/block/sde51
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 limits-cdsp -> /dev/block/sde52
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 logdump -> /dev/block/sde56
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 logfs -> /dev/block/sde54
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 logo_a -> /dev/block/sde19
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 logo_b -> /dev/block/sde43
lrwxrwxrwx 1 root root 45 1971-04-12 07:35 mdm_oem_stanvbk_a -> /dev/block/bootdevice/by-name/mdm_oem_stanvbk
lrwxrwxrwx 1 root root 45 1971-04-12 07:35 mdm_oem_stanvbk_b -> /dev/block/bootdevice/by-name/mdm_oem_stanvbk
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 mdtp_a -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 mdtp_b -> /dev/block/sde30
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 mdtpsecapp_a -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 mdtpsecapp_b -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 metadata -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root 37 1971-04-12 07:36 modem -> /dev/block/bootdevice/by-name/modem_a
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 modem_a -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 modem_b -> /dev/block/sde27
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 multiimgoem -> /dev/block/sde58
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 oem_dycnvbk -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 oem_stanvbk -> /dev/block/sda8
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 op1 -> /dev/block/sde63
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 op2 -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 param -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 qsee_log -> /dev/block/sde67
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 questdatafv -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 qupfw_a -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 qupfw_b -> /dev/block/sde36
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 rawdump -> /dev/block/sda13
lrwxrwxrwx 1 root root 40 1971-04-12 07:36 recovery -> /dev/block/bootdevice/by-name/recovery_a
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 recovery_a -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 recovery_b -> /dev/block/sde37
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 reserve1 -> /dev/block/sde69
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 reserve2 -> /dev/block/sde70
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 reserve3 -> /dev/block/sde71
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 reserve4 -> /dev/block/sde72
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 secdata -> /dev/block/sde60
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 splash -> /dev/block/sde50
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 spunvm -> /dev/block/sde49
lrwxrwxrwx 1 root root 36 1971-04-12 07:35 spunvm_a -> /dev/block/bootdevice/by-name/spunvm
lrwxrwxrwx 1 root root 36 1971-04-12 07:35 spunvm_b -> /dev/block/bootdevice/by-name/spunvm
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 storsec_a -> /dev/block/sde57
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 storsec_b -> /dev/block/sde73
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 super -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 toolsfv -> /dev/block/sde53
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 tz_b -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 uefisecapp_a -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 uefisecapp_b -> /dev/block/sde44
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 uefivarstore -> /dev/block/sde59
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 userdata -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 vbmeta_a -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 vbmeta_b -> /dev/block/sde39
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 vbmeta_system_a -> /dev/block/sde15
lrwxrwxrwx 1 root root 16 1971-04-12 07:35 vbmeta_system_b -> /dev/block/sde38
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 xbl_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 xbl_config_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root 15 1971-04-12 07:35 xbl_config_b -> /dev/block/sdc2

C:\platform-tools>

Here is a batch file to dump it!

 

[twindragon6]

They haven't been online in over a year. :/

I think I found the problem and a possible solution.

Loadable Kernel Modules | Android Open Source Project

source.android.com

 

[OdinVex]

You'll need to use the latest open-source dumps for the firmware from OnePlus (kernel) and build your device tree, then build based on the version of OxygenOS that OnePlus...then you need to figure out which files are proprietary and include those...and modify boot parameters, etc. Look into porting TWRP in general. Sucks for non-Samsung phones. X_x;

 

[twindragon6]

You'll need to use the latest open-source dumps for the firmware from OnePlus (kernel) and build your device tree, then build based on the version of OxygenOS that OnePlus...then you need to figure out which files are proprietary and include those...and modify boot parameters, etc. Look into porting TWRP in general. Sucks for non-Samsung phones. X_x;

I might be able to just take this recovery and use Android Image Kitchen on it, Modify the init.rc

on early-init
# Set the security context of /postinstall if present.
restorecon /postinstall

# ueventd wants to write to /acct
mount cgroup none /acct cpuacct
mkdir /acct/uid
start ueventd

# Load all kernel modules in one pass from init.rc* by invoking modprobe -a
exec u:r:vendor_modprobe:s0 -- /vendor/bin/modprobe -a -d \
/vendor/lib/modules module_a module_b module_c ...

and copy the pre-compiled kernel modules from the extracted/dumped super.img

\super\vendor_a\lib
\super\vendor_a\lib64

to \ramdisk\vendor\

then repack and

fastboot boot Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img

to test it.

I beleive twrp uses the phones kernel to boot right? Why recompile when you can just copy and paste kernel modules from a dump? It's a theory, I'm going to test it out later tonight. It'll probably be a lot easier to try to port this build (TWRP Porting to Unsupported Device).

It looks like EduardoA3677's Souce Code

GitHub - EduardoA3677/device_oneplus_billie_twrp: TWRP Source for OnePlus Nord N10 (billie)

TWRP Source for OnePlus Nord N10 (billie). Contribute to EduardoA3677/device_oneplus_billie_twrp development by creating an account on GitHub.

github.com

is actually ported from the OnePlus Nord (Avicii) with some tweaks to get it running. It's a different device. Since the full OnePlus N10 5G Source Code isn't available we should be able to steal from a dumped ROM Backup of the current firmware 11.0.8.BE86AA or even an older version

Software Upgrade - OnePlus.com

Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.

www.oneplus.com

the correct files to make TWRP fully functional for this device.