Development [TWRP][3.5.2-11][dre8t][WIP] Unofficial TWRP for OnePlus Nord N200 5G

Search This thread

EnumC

Senior Member
Dec 22, 2014
126
80
Cupertino
enumc.com
TCL 10 5G
OnePlus 8T
Mod Edit├┤Quote removed├

Do not share my broken builds.
There is a high priority bug with charging from 0% (and charging in recovery) that needs to be addressed before I promote it here again on XDA.

And it's definitely not stolen, the broken builds were made from trees for a moto device that I brought up from information obtained from the latest stock dump that I extracted and staged myself/fastboot commands/adb getprop and a few bits pulled from OnePlus 9 Pro after talking with the 9 Pro TWRP developer (Nebrassy) asking what he would suggest, and he suggested forking his entire tree as a base, which I also did not do for TWRP bringup.

There are sooo many boardconfig flags alone that are set properly in my tree that weren't event touched or present in EnumC's TWRP because he used a script to generate his base for TWRP. I tried the script and didn't like how minimal information was output, so I went the route suggested by ArtiicPanda to fork his personal Moto TWRP tree which is for a device on the same chipset, and use it for a base, upon analysis of the source I deemed this to be the cleanest base that I could use. I then stripped Motorola OEM specific code, substituted with alternatives for either CAF (Qualcomm) source for our specific chipset's CAF tag, or from the OnePlus 9/Pro modified as much as necessary to be meant specifically for N200.

I really shouldn't have to explain my development process to prove myself against these claims that you know damn well to be false. I'm very open about my development process, secrets when it comes to these projects has an overall negative impact on the community and slows progress for everyone.

I keep linking my GitHub in response because I have alot of commit history on there. Albeit quite noobish commit history as I'm not the best with using Git, but I put my time into doing all of this crap not just for myself but in hopes that it gives other people a better user experience with their own devices. Just to have people such as yourself claiming "he steals work" because you don't know how to click a link a look at a few commits yourself?

Just stop man. You're not doing anyone any favors by trying your absolute hardest to push away one of the two ROM developers on a device that has no custom ROM support aside from GSI.
@Travisholt92, great work! Yep, as you said, I used a common TWRP generation script for the base, then modified the boardconfig flags for this device. I was expecting to use this as a temporary build until a more experienced dev publishes their build, but it appears that never came to fruition. If you would like to publish a more stable build, I would be happy to link the original post to your thread or your build. If there's anything I can do to help, just let me know.
 

Travisholt92

Senior Member
Jun 28, 2012
1,312
1,188
30
Fort Wayne, Indiana
Honor 6X
OnePlus 6T
@Travisholt92, great work! Yep, as you said, I used a common TWRP generation script for the base, then modified the boardconfig flags for this device. I was expecting to use this as a temporary build until a more experienced dev publishes their build, but it appears that never came to fruition. If you would like to publish a more stable build, I would be happy to link the original post to your thread or your build. If there's anything I can do to help, just let me know.
It's awesome to see you around again! 🙂

I have been working on trying to better optimize my server for compile speeds before attempting android 12 TWRP bring-up and updating the android 11 TWRP to support newer OTA versions. Stuff on the to do list but things have been hectic around here with a newborn baby and 2 other children. I haven't been able to find the time to set up my server to compile.
 

vipermark7

Member
Oct 20, 2016
8
0

Disclaimer:​

Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.

Warning: This build is still WIP in early stages. I posted this version so everyone can at least flash magisk and other standard zips without too much hassle. Expect bugs and possibly other unexpected behaviors, especially if you attempt to use any features not listed below. Currently working on encryption and getting the other TWRP features online.

=========

Update (10/14/2021): I am taking a hiatus from this unofficial TWRP build. With that being said, you are welcome to fork the device tree at the bottom of the post or submit PRs. I may continue working on this when I have more time, but I'm sure another experienced developer will be able to pick up and accomplish what I had trouble with before.

=========


What Works:

* Booting to TWRP.
* Installing ZIPs.
* System, Product, Vendor, ODM, opluslog, Metadata, Persist, modem.
* a/b slot
* sdcard

What doesn't work:​

* userdata decryption. Requires forceencrypt disabler.
* Backup for any partition besides Super.
* Restore
* Factory Reset
* CPU temperature

Downloads:​

0.2.0: https://www.androidfilehost.com/?fid=7161016148664790178
0.1.0: https://www.androidfilehost.com/?fid=7161016148664789523

Installation:​







This release is built w/ the stock kernel (5.4.61-qgki-gf8e532b).

Source
Manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp
Device Tree: https://github.com/EnumC/android-OnePlusN200TMO-TWRP
Pull requests to the device tree are welcome!
Works like a dream! Thanks a ton :)
 

scanman0

Senior Member
Feb 2, 2015
50
27
Works like a dream! Thanks a ton :)
I would HIGHLY suggest you do not KEEP this broken TWRP installed on your phone and only install it when you are at 100% charge and remove it when your done with it.

There is a high priority bug with charging from 0% (and charging in recovery) that can leave your phone in a bricked and non chargeable state if your phone battery runs low and turns off.
 

vipermark7

Member
Oct 20, 2016
8
0
I would HIGHLY suggest you do not KEEP this broken TWRP installed on your phone and only install it when you are at 100% charge and remove it when your done with it.

There is a high priority bug with charging from 0% (and charging in recovery) that can leave your phone in a bricked and non chargeable state if your phone battery runs low and turns off.
What recovery should I use instead, that can install .zips?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10

    Disclaimer:​

    Code:
    * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
    * YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
    * Your warranty will be void if you tamper with any part of your device / software.

    Warning: This build is still WIP in early stages. I posted this version so everyone can at least flash magisk and other standard zips without too much hassle. Expect bugs and possibly other unexpected behaviors, especially if you attempt to use any features not listed below. Currently working on encryption and getting the other TWRP features online.

    =========

    Update (10/14/2021): I am taking a hiatus from this unofficial TWRP build. With that being said, you are welcome to fork the device tree at the bottom of the post or submit PRs. I may continue working on this when I have more time, but I'm sure another experienced developer will be able to pick up and accomplish what I had trouble with before.

    =========


    What Works:

    * Booting to TWRP.
    * Installing ZIPs.
    * System, Product, Vendor, ODM, opluslog, Metadata, Persist, modem.
    * a/b slot
    * sdcard

    What doesn't work:​

    * userdata decryption. Requires forceencrypt disabler.
    * Backup for any partition besides Super.
    * Restore
    * Factory Reset
    * CPU temperature

    Downloads:​

    0.2.0: https://www.androidfilehost.com/?fid=7161016148664790178
    0.1.0: https://www.androidfilehost.com/?fid=7161016148664789523

    Installation:​

    1. Run
    Code:
    fastboot boot twrp-3.5.2-11-holi.img
    . This will not boot you to twrp, but you should see the device boot to system successfully. If it boots properly, run adb reboot bootloader. If it bootloops or freezes, STOP. Leave your model number in the comments and force reboot your device.

    2. Run
    Code:
    fastboot getvar current-slot
    to get your current active partition slot. If it's A, then run
    Code:
    fastboot flash boot_a twrp-3.5.2-11-holi.img
    . If it's B, run
    Code:
    fastboot flash boot_b twrp-3.5.2-11-holi.img

    3. Run
    Code:
    fastboot reboot
    to get back to the system

    This release is built w/ the stock kernel (5.4.61-qgki-gf8e532b).

    Source
    Manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp
    Device Tree: https://github.com/EnumC/android-OnePlusN200TMO-TWRP
    Pull requests to the device tree are welcome!
    3

    These builds have an issue with being able to charge while in recovery (battery stats are not updated in recovery), and when the device dies, it will only charge via EDL mode) I do not recommend using these builds at this time for that reason. For temporary usage just to achieve a specific task and restore the previous boot image afterwards would be fine. If you need magisk, you need to use the magisk app to modify your stock boot image, and disable verity and verification (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img) which requires having the stock vbmeta.img

    Here are my latest TWRP and OrangeFox recovery builds for N200.

    DO NOT FASTBOOT FLASH THESE
    You'll have a bad experience and probably won't be able to boot back into your stock ROM until you switch back to a proper boot.img.

    Fastboot boot the image then go to advanced settings and "install this TWRP/OrangeFox" (depending on which you're on)

    I'm running 11.0.5.0.DE17AA N/A firmware (on my T-Mobile branded variant)

    You must remove your lockscreen security (you can re-enable it when you're done in twrp).
    If you don't remove your password,pin,pattern,fingerprint you're not going to be able to access your data within recovery.


    I'll upload my device tree later today and get threads made.
    For me, I can daily driver this to achieve anything I need custom recovery.

    The build flags I set should support metro, T-Mobile, and unbranded/NA variant.

    I have flashed the latest NA build from the OnePlus website with this project and it switched me from slot A to slot B in the process without an issue

    If you encounter issues (aside from decryption because your have a password set), I'll do my best to resolve them
    2
    Is this still being worked on? What exactly still needs to be figured out to get TWRP fully functional?
    yes it is, i just got decryption of userdata working :) then fixed touchscreen on screen off, then fixed mtp/adb functionality on boot, fixed fastbootd, fixed flashing stock OTAs, tested flashing a stock OTA (from internal storage) and it worked with no issues. no red error messages at all. Only thing i have left to fix (before i apply for Official) is to fix booting the OS when building from source. THAT IS IT!. I will have a thread up soon with the usable (fastboot boot twrp.img ONLY, no fastboot flash boot, your device wont be able to boot any OS). but it at least can flash zip files, use SD card, use USB OTG.
    2
    Mod Edit├┤Quote removed├

    Do not share my broken builds.
    There is a high priority bug with charging from 0% (and charging in recovery) that needs to be addressed before I promote it here again on XDA.

    And it's definitely not stolen, the broken builds were made from trees for a moto device that I brought up from information obtained from the latest stock dump that I extracted and staged myself/fastboot commands/adb getprop and a few bits pulled from OnePlus 9 Pro after talking with the 9 Pro TWRP developer (Nebrassy) asking what he would suggest, and he suggested forking his entire tree as a base, which I also did not do for TWRP bringup.

    There are sooo many boardconfig flags alone that are set properly in my tree that weren't event touched or present in EnumC's TWRP because he used a script to generate his base for TWRP. I tried the script and didn't like how minimal information was output, so I went the route suggested by ArtiicPanda to fork his personal Moto TWRP tree which is for a device on the same chipset, and use it for a base, upon analysis of the source I deemed this to be the cleanest base that I could use. I then stripped Motorola OEM specific code, substituted with alternatives for either CAF (Qualcomm) source for our specific chipset's CAF tag, or from the OnePlus 9/Pro modified as much as necessary to be meant specifically for N200.

    I really shouldn't have to explain my development process to prove myself against these claims that you know damn well to be false. I'm very open about my development process, secrets when it comes to these projects has an overall negative impact on the community and slows progress for everyone.

    I keep linking my GitHub in response because I have alot of commit history on there. Albeit quite noobish commit history as I'm not the best with using Git, but I put my time into doing all of this crap not just for myself but in hopes that it gives other people a better user experience with their own devices. Just to have people such as yourself claiming "he steals work" because you don't know how to click a link a look at a few commits yourself?

    Just stop man. You're not doing anyone any favors by trying your absolute hardest to push away one of the two ROM developers on a device that has no custom ROM support aside from GSI.
    2

    Disclaimer:​

    Code:
    * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
    * YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
    * Your warranty will be void if you tamper with any part of your device / software.

    Warning: This build is still WIP in early stages. I posted this version so everyone can at least flash magisk and other standard zips without too much hassle. Expect bugs and possibly other unexpected behaviors, especially if you attempt to use any features not listed below. Currently working on encryption and getting the other TWRP features online.

    =========

    Update (10/14/2021): I am taking a hiatus from this unofficial TWRP build. With that being said, you are welcome to fork the device tree at the bottom of the post or submit PRs. I may continue working on this when I have more time, but I'm sure another experienced developer will be able to pick up and accomplish what I had trouble with before.

    =========


    What Works:

    * Booting to TWRP.
    * Installing ZIPs.
    * System, Product, Vendor, ODM, opluslog, Metadata, Persist, modem.
    * a/b slot
    * sdcard

    What doesn't work:​

    * userdata decryption. Requires forceencrypt disabler.
    * Backup for any partition besides Super.
    * Restore
    * Factory Reset
    * CPU temperature

    Downloads:​

    0.2.0: https://www.androidfilehost.com/?fid=7161016148664790178
    0.1.0: https://www.androidfilehost.com/?fid=7161016148664789523

    Installation:​







    This release is built w/ the stock kernel (5.4.61-qgki-gf8e532b).

    Source
    Manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp
    Device Tree: https://github.com/EnumC/android-OnePlusN200TMO-TWRP
    Pull requests to the device tree are welcome!

    Ayee soo I'm working on fixing up your twrp. Can you inform me how you linked the kernel modules into the build? I got it "booting" (stays at bootloader is unlocked and can't be trusted screen but with adb recovery commands working. I found a big reason you couldn't get decryption working. Wrong sysfs location listed in the fstab. I'll send a pull request 😎 also most of your "inclusion of fbe" is already included in device/qcom/twrp-common 👍