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

[Link575]

The core development of TWRP and OrangeFox, SHRP, is maintained by only 2 or 3 core devs and they are struggling to keep up with the complex changes of each new android update

Oh interesting, thanks for the info.

 

[famewolf]

Just thought I'd mention that twrp for many models now can decrypt android 12 rom's....not sure if that version is available for n200 yet.

 

[EnumC]

┤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]

@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.

 

[MiniNinja2024]

Cool. So what should I do now if I want to flash Magisk? Wait for your 0.3.0 version?

you could do $adb push (FILE) /sdcard or /tmp

 

[vipermark7]

Disclaimer:​

* 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]

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]

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?

 

[radford.will]

Did not read well enough. Bricked my N200 5G from Metro. I flashed the twrp image and got the following message:
The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image...

Any ideas, I'm very stuck.

 

[Metconnect2000]

Did not read well enough. Bricked my N200 5G from Metro. I flashed the twrp image and got the following message:
The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image...

Any ideas, I'm very stuck.

You can try to use the msm took to restore to stock. You should be able to search for it in the forum

 

[radford.will]

You can try to use the msm took to restore to stock. You should be able to search for it in the forum

I used the stock boot image for my software from the post below and ended up wiping data that wasn't necessary. But I restored it without the msm tool, it doesn't run on my pc, and rooted it with magisk. Thanks for the tip though.
https://forum.xda-developers.com/t/...le-metro-de2118-c_17-ota-for-dummies.4484651/

 

[zfk110]

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.

how you are going to replace the TWRP with the stock recovery?

 

[scanman0]

how you are going to replace the TWRP with the stock recovery?

You can flash the latest stock or magisk rooted boot.img from this thread:

Root latest A12 US OEM (DE2117)C_21/T-Mobile-Metro(DE2118) C_20 OTA for dummies

I have posted all the boot.img files for N200 A12 to AFH for DE2117 US OEM firmware and now latest for DE2118 (Tmobile/metro) I have posted both the original file as well as pre-patched with Magisk v25.2 for each. The T-Mobile/Metro image...

forum.xda-developers.com

 

[CmdrCrichton]

Hello. Congratulations on twrp. My OnePlus n20 and I would like to have a twrp also the n20, and. The n200 are almost the same. One is just missing a 0.

My n20 is being replaced . I did the ota a12 and it broke the touchscreen response

Point me on the right direction to port twrp and I'll begin my lessonss

This twrp build was abandoned and is very likely to cause issues. I would not base anything off this. If you are interested in building twrp of your project, I would suggest check out their resources for building.

 

[EnumC]

This twrp build was abandoned and is very likely to cause issues. I would not base anything off this. If you are interested in building twrp of your project, I would suggest check out their resources for building.

Yeah, I made this unstable build to root the phone initially. This was back when practically no development was available for this device.
Since this thread keeps getting bumped to the front, I have added an additional disclaimer to the OP that points to the official LineageOS recovery. If anyone wants to take over this thread and the GitHub repo, feel free to PM me.