|
| 1 | +metadata: |
| 2 | + maintainer: SirRGB |
| 3 | + device_name: OnePlus Nord N10 5G |
| 4 | + is_ab_device: true |
| 5 | + device_code: billie |
| 6 | + supported_device_codes: |
| 7 | + - billie |
| 8 | + - OnePlusN10 |
| 9 | + untested: true |
| 10 | + additional_steps: |
| 11 | + - dtbo |
| 12 | + - vbmeta |
| 13 | + - vendor_boot |
| 14 | +requirements: |
| 15 | + android: 11 |
| 16 | +steps: |
| 17 | + unlock_bootloader: |
| 18 | + - type: call_button |
| 19 | + content: > |
| 20 | + As a first step, you need to unlock the bootloader. A bootloader is the piece of software, that tells your phone |
| 21 | + how to start and run an operating system (like Android). Your device should be turned on. |
| 22 | + Press 'Confirm and run' to reboot into the bootloader. |
| 23 | + command: adb_reboot_bootloader |
| 24 | + - type: call_button |
| 25 | + content: > |
| 26 | + In this step you actually unlock the bootloader. Just press 'Confirm and run' here. The phone will automatically reboot and reformat. |
| 27 | + Once it's done, press continue here. |
| 28 | + command: fastboot_oem_unlock |
| 29 | + - type: confirm_button |
| 30 | + content: > |
| 31 | + The bootloader is now unlocked. Since the device resets completely, you will need to re-enable Developer Options and USB debugging to continue. |
| 32 | + boot_recovery: |
| 33 | + - type: call_button |
| 34 | + content: > |
| 35 | + Now you need to boot a custom recovery system on the phone. A recovery is a small subsystem on your phone, that manages updating, |
| 36 | + adapting and repairing of the operating system. |
| 37 | + Make sure your device is turned on. You need to reboot into the bootloader again by pressing 'Confirm and run' here. Then continue. |
| 38 | + command: adb_reboot_bootloader |
| 39 | + - type: call_button |
| 40 | + img: twrp-start.jpeg |
| 41 | + content: > |
| 42 | + Boot a custom recovery (temporarily) by pressing 'Confirm and run'. Once it's done continue. |
| 43 | + command: fastboot_boot_recovery |
| 44 | + - type: call_button |
| 45 | + content: > |
| 46 | + In some cases, the inactive slot can be unpopulated or contain much older firmware than the active slot, leading to various issues including a potential hard-brick. |
| 47 | + We can ensure none of that will happen by copying the contents of the active slot to the inactive slot. Press 'confirm and run' to to this. Once you are in the bootloader again, continue. |
| 48 | + command: adb_twrp_copy_partitions |
| 49 | + - type: call_button |
| 50 | + img: twrp-start.jpeg |
| 51 | + content: > |
| 52 | + Now we need to boot into recovery again. Press run and when you see the TWRP screen you can continue. |
| 53 | + command: fastboot_boot_recovery |
0 commit comments