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

[Travisholt92]

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!

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

 

[Travisholt92]

I have an updated kernel image from the T-Mobile variant that I'm looking to make available to everybody but I could definitely use a tad bit of guidance if possible

 

[AiM2LeaRn]

anyone have any idea how to restore the stock recovery for the tmobile version?

 

[atsalchenberg]

anyone have any idea how to restore the stock recovery for the tmobile version?

Reflash the original boot-b image in regular fastboot

 

[[email protected]]

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!

Worked like a charm

 

[edale1]

Is this still being worked on? What exactly still needs to be figured out to get TWRP fully functional?

 

[AiM2LeaRn]

Is this still being worked on? What exactly still needs to be figured out to get TWRP fully functional?

to be honest with you i notice most of the more recent one plus 8 devices use some kind of custom recovery (non-twrp) and the roms are sideloaded via adb or fastboot. TWRP still has some nice features though, i like the simplicity of EDL/Fast boot that EnumC integrated.

 

[Travisholt92]

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.

 

[Travisholt92]

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.

And I can now boot the ROM. I'll have an updated TWRP thread posted later today, after thorough testing I will apply for official maintainer.
I will start work on LineageOS soon now that TWRP is nearly polished.
On a not so high note, my home internet just got disconnected a few hours ago due to a missed payment (T-Mobile at Home).

This is going to significantly hinder my ability to continue with bringup as I haven't had an active SIM card in months and my main source of internet connectivity just got axed until my tax refund rolls in.
Yaaaaaay. ‍

 

[Travisholt92]

N200 - Google Drive

drive.google.com

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

 

[Travisholt92]

N200 - Google Drive

drive.google.com

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

Decryption does work with Android 12 (including GSI) this is NOT a device specific bug. You may be able to find a flashable patch to disable force encryption to allow you to mount userdata in recovery

 

[Link575]

Hey I'm having issues getting your TWRP to flash. I'm fastboot booting it but despite picking the TWRP version it shows up as OrangeFox and there's not advanced settings. Any idea what I'm doing wrong?

Edit: NVM I see now install this.... but it seems the TWRP is OrangeFox.

 

[Travisholt92]

Hey I'm having issues getting your TWRP to flash. I'm fastboot booting it but despite picking the TWRP version it shows up as OrangeFox and there's not advanced settings. Any idea what I'm doing wrong?

Edit: NVM I see now install this.... but it seems the TWRP is OrangeFox.

Yeah I had a derp. I'll get that fixed

 

[Link575]

Hey I'm having issues getting your TWRP to flash. I'm fastboot booting it but despite picking the TWRP version it shows up as OrangeFox and there's not advanced settings. Any idea what I'm doing wrong?

Yeah I had a derp. I'll get that fixed

Np and thanks for your work. Curious, will we be able to wipe the phone so no more dirty flashing? Or it's just for flashing only.

 

[Travisholt92]

Np and thanks for your work. Curious, will we be able to wipe the phone so no more dirty flashing? Or it's just for flashing only.

I'm not sure I haven't tested a factory reset with it yet to be honest

 

[Link575]

I'm not sure I haven't tested a factory reset with it yet to be honest

Alright guess I'll try it out when it's up then. For now I went with your OrangeFox build which is working great. Thanks

 

[Travisholt92]

┤Mod Edit├┤Quote removed as post was removed├

you can look at my GitHub trees here:

GitHub - Travisholt92/twrp_n200

Contribute to Travisholt92/twrp_n200 development by creating an account on GitHub.

github.com

You're right I totally copy and pasted EnumC's work without working decryption and when I compiled it decryption magically worked. That user messed up by wiping the Super partition partition within TWRP. Because of this I will be disabling the ability to wipe the super partition and probably more.

Stick to your GSI's while I do ACTUAL dev work.

 

[Travisholt92]

┤Mod Edit├┤Quote removed as post was removed├

It's all stolen yupp. Dude look at the commit history. That was ME. NOT stolen in any way even the tree I initially forked was a super generic base that I had to add device specifics to. That gpt-utils didn't shim itself for our specific device

Just to show you how much I "copied" (not quite sure who I could have copied from, other devices? CAF?) I'm going to successfully bring up TWRP on the N100 too.

Am I supposed to disable the terminal to prevent people from bricking their phones?

Don't blame my software out of spite of me. That's just petty. That guy could have broken any phone that way in ANY TWRP not just mine.

Commits · Travisholt92/android_device_oneplus_sm4350-common

Contribute to Travisholt92/android_device_oneplus_sm4350-common development by creating an account on GitHub.

github.com

(This isn't fully up to date with my local changes yet)

I bet this work is all stolen too. I'm nearly at the point of being able to compile full custom ROMs for this specific device with a CAF based kernel I'm bringing up myself.

GitHub - Travisholt92/android_kernel_oneplus_sm4350

Contribute to Travisholt92/android_kernel_oneplus_sm4350 development by creating an account on GitHub.

github.com

I'll let my software speak for itself, I reaaaaaaaally don't need to defend it like this

 

[Travisholt92]

┤Mod Edit├┤Quote removed as post was removed├

Look at the commit history yourself before you make such accusations. Download his device tree and my device tree, run a diff script or use meld to see just how much difference there is between my tree and his. It's quite a bit more than you're making it out to be I HAD used one of EnumC's prebuilt TWRPs and shimmed some files within it as a proof of concept before implementing those changes and many more into a new build tree. And I wouldn't have needed EnumC's previous TWRP work to make it happen. And with my lineageOS bringup, who am I stealing that from? Can you tell me who else is working on lineageOS for the n200? Because the dev group for the N200 all seems to be waiting for me to finish bringup So please show me who I'm stealing all of this work from so I can give credit where credit is due. I know EnumC is going to get a shout-out in all of my n200 ROM/recovery threads.

 

[-Enkidu-]

n200 ROM/recovery threads.

This is great work, thanks for all of it so far