yashsingh1/xdaforums huggingface dataset:
[OnePlus Nord N200 5G] kbnem930:
I know what you meant to say. It's obvious you were making light of your own mistakes. It is understandable that you would want to clarify that there was no malintent toward the OP, and that you appreciate the time and effort he put into making this "hand holding guide" for "dummies" like us. I am certainly thankful for all of the brilliant minds at XDA that I've had the privilege of learning from over the years by reading step by step guides such as this. However, the only "condescending comments" and "poor attitude" in this post did not come from you, and in my opinion you should be on the receiving end of an apology for these hypocritical accusations. Jus sayin...
[OnePlus Nord N200 5G] chepe263:
If I installed lineageOS in a dre de2117 already, can I go back to OxygenOS with the steps this guide?

Would it be possible to relock the bootloader ?
[OnePlus Nord N200 5G] scanman0:
I just now noticed your question.:oops:

You should use Fastboot Enhance and flash the full rom .zip file for US OEM. Make sure it is the SAME version of Android that you have installed. First in FastbootD mode, and then switch to Fastboot mode and flash the same .zip file again.

Flashing it in FastbootD will flash most partitions and then flashing it a second time in fastboot will then flash the modem.img and boot.img.

After you have flashed it in both, before you boot the phone, go from fastboot to recovery with the volume buttons and then do a full wipe with the recovery screen option where you put in the 4 digit code.

You will then boot ujp in initial setup. In this case on Android 11. You can let OTA updates then upgrade you to A12 current version C_20.
[OnePlus Nord N200 5G] chepe263:
The phone had originally Android 11 to be able to flash LineageOS 19 (Android 12)

I flashed "DE2117-A11-Final-OnePlusN200Oxygen_10.O.11_OTA_011_all_2203021426_downgrade_66cde69fe1e342db" in fastbootD first, then I tried to flash it again in fastboot mode. I'm not able to go into recovery like you suggest.

I also try to boot into regular android and screen is black too. Currently is softbricked, I'm able to enter the bootloader sometimes.

---

edit

I flashed the recovery from LMODroid in both A & B Slot, and used it to flash the "DE2117-A11-Final-OnePlusN200Oxygen_10.O.11_OTA_011_all_2203021426_downgrade_66cde69fe1e342db". It booted into OnePlus recovery. Using chinese and another smartphone to translate, I managed to wipe data and cache.

Then I tried to boot into android but It's stuck in the bootanimation (One red circle with two white circles around it, like a "loading" animation) and it doesn't go beyond that point.

----

edit

wiped user partitions a couple more times and the smartphone booted to oxygen os
[OnePlus Nord N200 5G] scanman0:
I would never touch the recovery in the non active slot and keep it stock so you can use it to recover if you have a bad flash as you do now. It appears you have the Chinese version of recovery on your phone and this will not allow you to flash US rom's.

You should be able to flash just the boot.img from DE2117 with it and then boot into the US recovery and then use fastboot enhance from there to flash the rest of the rom. Flash the boot.img that matches the Android version you had flashed last and restore the rom image of the same version so it has matching partition sizes. I'm assuming it's A11 from what you describe.

If you try to flash the partitions for A12 on a phone that is partitioned for A11, there will not be enough space and it will fail.
[OnePlus Nord N200 5G] chepe263:
With a lot of ignorance and a little bit of luck, I flashed the android 11 zip with fastboot enhanced, several times and once with the LibmobOS recovery the same zip, booted to Oneplus recovery, formatted the user partition and the phone booted to OxygenOS.

After some OTA updates, the bootloader got locked again but now I'm back to stock OS.
[OnePlus Nord N200 5G] nitelitevt:
hey everyone! recently i was trying to flash lineage OS 12 on my device, i didnt downgrade and of course, bricked it. i followed the steps of this guide until i reached the step where i get selected the "read back" button, things went on smoothy until i saw "firehose communication failed", how do i fix this issue?
[OnePlus Nord N200 5G] lurkio:
Stuck on line 37. The OS won't consistently detect that phone in fastbootd mode. Anyone else run into this?
[OnePlus Nord N200 5G] weirdfate:
remote: 'flashing is not allowed for critical partitions

gettig this when i try to convert

oem unlocked and restored to the tmo firmware

any help?

thank you
[OnePlus Nord N200 5G] blueberry.sky:
More information would help.

What step are you at? And which command is giving that error?

And to confirm, you have a T-Mobile or Metro model DE2118, correct?

Bootloader is unlocked using a code from OnePlus, not just the "oem unlocking" switch, correct?
[OnePlus Nord N200 5G] Galaxy198:
It isn't downloading anything, my phone doesn't even come up.
[OnePlus Nord N200 5G] rragu:
Yeah I'm having the same issue.

I entered "adb reboot edl" and phone does appear to be in EDL mode (screen is blank and doesn't respond to touch)

But, msmtool doesn't show anything after phone goes into EDL mode

EDIT: I figured it out. Currently installing DE2117_11.C.21, after which I'll downgrade to Android 11 and then switch to LineageOS.

EDIT2: I took a few steps to get my phone recognized by msmtool.

When I connected the N200 to my PC, Windows Device Manager kept seeing it as "QHSUSB_BULK" under "Other Devices". So, following this article, I installed the Qualcomm HS-USB QDLoader 9008 drivers. After that, my phone showed up as "Qualcomm HS-USB QDLoader 9008 (COM3)" under "Ports (COM & LPT)" in Device Manager.

I also had to reboot Windows with Driver Signature Verification disabled (described in the DroidWin article linked above; at the end, I also re-enabled Driver Signature Verification).

Next, the sequence of steps I took to start msmtool/connect my phone was slightly different (I followed this article). Basically, I disconnected the phone from the PC, then manually booted into EDL mode. Then I did the Read Back process as described in Steps 4-11 of this guide. Then I connected the phone to the PC and everything worked as described in Steps 14-15.

Also, as mentioned by someone else earlier in this thread, after Step 22, I had to turn on Wi-Fi for a minute or so to get "OEM Unlocking" un-greyed. I then turned it on, as described in Step 23 and proceeded from there.

One last minor deviation from the guide: Step 41 failed for me as Fastboot Enhance tried but could not reboot to recovery. If I recall correctly, I just tapped "Advanced" in the fastbootd screen and "reboot to recovery" was an option. After that reboot, I picked "Wipe Data & Cache" and then "Erase everything" (or similarly-named options).

After that, as described in Step 44, it was one last system setup (with Wi-Fi turned on) and two subsequent OTA updates (first to Android 12 C_16, then to latest OTA [currently C_21]).

Thanks for all your hard work on this guide @scanman0! Now I'm off to follow your Android 11 downgrade guide!

P.S. Maybe it's worth adding the Qualcomm drivers to the prerequisites section of the guide (unless it's already there and I just can't read)? I don't know if Windows should have automatically downloaded them after the first time I connected the N200 to my PC; but, in my case, Windows did not do so.
[OnePlus Nord N200 5G] 7h3DuD3:
So just to confirm I can do this sim locked, but bootloader unlocked correct?
[OnePlus Nord N200 5G] nanunoran:
With Android 12 Now my model is DE2117 and Build is DE2117_11_C.15. (BIG SUCCESS YEYIII, THANK YOU GUYS).

For the life of me I can not achieve the same on any build of Android 11. It would either get me to Qualcomm crash dump or remain on DE2118. Anyone has anymore insight? I think I am following guide extremely well and not screwing any step. I actually managed to convert it to DE2117 on A12 very easily, just on A11 its pain in sss.

Also once converted to DE2117 successfully, does update break? New update available version DE2117_11_C.23 fails to install with error message Installation Problem. Is anyone facing same issue or is it unique to my device? ( I am currently on DE2118 fully converted to DE2117 on current build DE2117_11_C.15 & hardware version DE2117_11)
[OnePlus Nord N200 5G] peterparker475:
Is it also work on network locked mobile?
[OnePlus Nord N200 5G] htc_unenthusiast:
I have gone through this process in its entirety now. I think I did everything correctly but the driver situation in windows was painful. At the end of things I am on Android 12 with a DE2117 device. Unfortunately my SIM never can connect to a network. Did my device remain carrier locked after the process completed?

Edit: I now see in a few other threads that a carrier unlock did not occur during this conversion process.

Edit 2: Are there steps to return the phone back to its original state using firehose? I made a full backup but since the device is carrier locked I will need to see if I can fix that part before installing LineageOS.
[OnePlus Nord N200 5G] zm55:
I am curious - if I am planning to run LineageOS or PixelExperience ROM on the device, is there any advantage of moving to DE2117 from 2118?
[OnePlus Nord N200 5G] mastmakerjones:
You cannot install LineageOS on DE2118. In other words, you need to convert your DE2118 to DE2117, install all updates INCLUDING Android 12 up to the latest one, before you can install LineageOS. At this point, if you wish to install LineageOS 19, you need to downgrade to Android 11 (search for detailed guides within XDA). If you wish to install LOS20, you can do so on top of the latest Android 12 update of DE2117 image.
[OnePlus Nord N200 5G] zm55:
Thanks.

I asked this because I am already running PixelExperience on the N200 but it still reports as DE2118.

I was wondering if anything (besides cosmetics) will change if I flash it to DE2117 first and then install PE13.
[OnePlus Nord N200 5G] mastmakerjones:
My DE2118 -> DE2117 -> Android 12 -> LineageOS20 still reports my device as DE2118. It looks like you can fool OxygenOS into thinking it is DE2117 but not LineageOS or PE!! :D
[OnePlus Nord N200 5G] zm55:
Got it. Thanks.

Got it. Thanks.
[OnePlus Nord N200 5G] mysticjp:
im running Q_V1_P14 , help plz! thank u in advanced,, OH and DE2118_11C.23
[General Questions and Answers] schneidz:
[sp1a.210812.016.f926u1ues1dvg3] a few months ago both worked. now when i try to dex to my fire-tv or roku i see the butterfly-flower background image with app icons on the top left of the television screen. i used to press the recent apps overlay button and there was a 4th button to use as a trackpad (no more). so i cant run any apps on the t.v.

also smart view no longer mirrors my cellular-telefones screen. when it first connects i see my fone screen/widgets on the t.v. for half a second and then immediately the screen flashes to the butterfly-flower background image (no app icons but a small white dot on the bottom rite). i can cast videos but i cant mirror. i tried opening email app on my fone and selecting app cast but it makes the email app into a smaller window on my fone but no change on the t.v.
[OnePlus 7 Pro Questions & Answers] ro-mann:
Hi,

starting today, my phone (unrooted and unmodded, Android 11, Oxygen OS 11.0.9.1.GM21BA) freezes every time I open the camera. Doesn't matter if I open it directly or through Snapchat.

The phone freezes completely and I have to restart by holding down the power button.

I already deleted memory and cache of the camera and also turned off battery optimisation. But to no avail.

Does anybody have an idea how this can be fixed?
[OnePlus 7 Pro Questions & Answers] ze7zez:
You haven't tried a factory reset.
[OnePlus 7 Pro Questions & Answers] ro-mann:
No, because that would be a pain in the ass. I have over 100gb on the phone. I wanted to know if there is anything else I can try before that.
[OnePlus 7 Pro Questions & Answers] ze7zez:
Of course, you can clean the system and remove the corpse with the amazing SD Maid.

SD Maid 1 - System Cleaner - Apps on Google Play

A maid for your Android, to keep it clean & tidy.

play.google.com
[OnePlus 7 Pro Questions & Answers] palopaxo:
That can happen if you have "sensors off" active
[OnePlus 7 Pro Questions & Answers] ro-mann:
Thanks, but that didn't yield any results either.

Where do I change this setting?
[OnePlus 7 Pro Questions & Answers] palopaxo:
Quick settings pannel, im not sure if the tile only exits in a12.
[OnePlus 7 Pro Questions & Answers] ro-mann:
thx but that wasnt it either. Sensors were on

Will try factory reset now 😔
[OnePlus 7 Pro Questions & Answers] ro-mann:
Unfortunatly the problem persists after factory reset. Seems to be a hardware issue.
[Android Q&A, Help & Troubleshooting] Mhd.Tj:
How i can install gbwhatsapp latest version on Samsung note3 android5 although whatsapp official works normally .

App not installed
[Android Q&A, Help & Troubleshooting] McWelling:
I have this problem too.

I have GBWhatsApp installed, but now that I wanna update, it says "Suspected Voice Phishing, app reported as voice phishing app" and doesn't allow me install the app.

I'm guessing this is due to some recent security updates on Android 13, and I don't know how to bypass this.

Help please, and thanks.
[Android Q&A, Help & Troubleshooting] JayFifteen:
Same problem ... any fix ?
[Android Q&A, Help & Troubleshooting] McWelling:
Yeah, I used ADB and my laptop to install it.

Pretty straightforward.
[Android Q&A, Help & Troubleshooting] omar022:
Could u teach me how u do that plz
[Android Q&A, Help & Troubleshooting] McWelling:
You can follow the guide in the link below. If everything is followed well, it'd work fine.

How To Install Apps On Your Android Device From Your Computer

Android is one of the most customizable operating systems out there as you can tweak pretty much everything on your Android device. Unlike iOS, Android even allows you to download and install apps onto your device from unofficial sources. What that means is you no longer need to rely on the...

www.online-tech-tips.com
[Android Q&A, Help & Troubleshooting] saoudien07:
You can use

scrcpy

GitHub - Genymobile/scrcpy: Display and control your Android device

Display and control your Android device. Contribute to Genymobile/scrcpy development by creating an account on GitHub.

github.com

It also use ADB connection.
[General Questions and Answers] gr3uh:
Any custom roms like lineage for this device? This is not kiev.
[General Questions and Answers] Fytdyh:
Well, the phone barely launched. It does not have even a year. Since the phone is in order to get another 1 -2 updates, wait for those. Moto can develop faster than any individual dev. If you want lineage or other custom rom, wait a couple more months
[General Questions and Answers] gr3uh:
I tried using a stock firmware and patched magisk but when I booted up the phone I got this
[General Questions and Answers] gr3uh:
View attachment 5698997
[General Questions and Answers] Fytdyh:
You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked.
[General Questions and Answers] gr3uh:
I think I used the wrong firmware possibly
[General Questions and Answers] gr3uh:
Makes no sense since I was perfectly able to unlock the bootloader using Motorola's official guide.
[General Questions and Answers] Fytdyh:
I recommend posting your questions here :

https://xdaforums.com/t/help-thread-ask-any-question-noob-friendly.2257421/page-2453#post-87357675

Do say what you did, what you flashed. Everyone can help you faster if you are concise and say what did you flash or did to that device. Whenever you try something, write it down.
[General Questions and Answers] KParsons0697:
mine did that too and i just kept trying different sim cards untill i found one that worked and it unlocked it
[General Questions and Answers] 3×5:
Hi all, I have a couple questions about this:

My ultimate goal is to get a custom firmware on this (Lineage). I have seen a few threads floating around here, recommending an alternate method for rooting the device, and offering a link to the stock firmware.

However, even if this is successful, I will end up with a rooted, stock-Android phone at the end of it, and since there's still no Lineage release for this phone (or any other alternate firmare, from what I can tell), this effort is not going to get me any closer to a custom ROM. Am I understanding this correctly?

If I'm understanding point 1 correctly, then I need to decide whether to keep this phone, or return it. If a custom OS never becomes available, I don't want the phone. Even in github, there's no indication I could see that Austin is even under development.

However, if this phone is likely to end up with a LineageOS version, I'll just wait a few months. For those of you who spend more time on XDA than I do, how likely is it that this will get a release candidate?

Thanks for your help!
[General Questions and Answers] gr3uh:
I've been told there will never be any progress on custom roms and firmware for this device since it is mediatek and mediatek is locked down their binaries making it hard for people to make custom rom. That being said you can try porting your own twrp or flashing a GSI.
[General Questions and Answers] gr3uh:
My phone I bought it from a carrier and it was locked until payed off, paid it and waited a few days and it worked. Rooting this device was easy, just wish rom development would come sometime. I hear android 13 should be coming to this device around the beginning of Q2 of 2023
[General Questions and Answers] 3×5:
@gr3uh, thanks for the reply. I could try a GSI, but really my goal is to have an open-as-possible, de-Googled phone. I don't even really care about MicroG, or any of this. Even with no services at all, I can use Google Maps in a browser.

I assume if I install the stock firmware from lolinet, it'll have all the Google Play services. Will the phone also be rooter at that point? Or do I have to also root the phone, and then manually remove all the play services?

The big picture question is this: what's the simplest route to me De-Googling this phone?

Bonus question: why is the stock firmware hosted on a site called 'lolinet'? Maybe I don't want to know...
[General Questions and Answers] 3×5:
Alright, here's an update on my progress:

I downloaded a Lineage GSI image from Andy Yan. His site said to install an app called 'Treble Info' to get device information. I did this and got the version that matched this device: lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz

(b means "AB", i.e. system-as-root. VNDKLITE = Read/Write Super partition. Treble info said VNDKLITE was enabled on this device).

I restarted in fastboot mode and ran

fastboot erase system

and got:

erasing 'system_b'...
OKAY [ 0.054s]

Then I ran:

fastboot -u flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz

and got:

target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 164341876 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
OKAY [ 9.599s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))

So then I downloaded an empty vbmeta.img file, and flashed that:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

That appeared to work, because I thought my issue might be that dm-verity was enabled. However, I think the real issue is that I flashed this wrong, because I was looking at a tutorial that didn't apply to a system with a super partition. So my hope is that I can still flash my GSI image to the super partition, but I'm not totally sure how to do this. It might be as simple as

fastboot flash super lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz

But I don't want to make things worse. At this point, my system partition is corrupted. The first time I tried to flash system I got "no such device", and the second time I got

(bootloader) Invalid partition name system

Anyway, I can only boot into fastboot mode. I do have that stock ROM from lolinet, so I could try flashing the super partition, chunk by chunk. There are 26 sparsechunks. Maybe this would get me back to square 1, but I'd rather press forward at this point, if possible, and try to get this GSI image flashed.
[General Questions and Answers] 3×5:
I should also point out that when I boot into fastbootd on the phone, it says 'Secure boot - yes' even though I flashed that empty vbmeta image and got:

target reported max download size of 268435456 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.000s]
writing 'vbmeta_b'...
OKAY [ 0.073s]
finished. total time: 0.074s
[General Questions and Answers] radosomalo:
There should be a batch file in the zip you can use to flash the dynamic partition covers everything just edit it to fit your need. And run as betch
[General Questions and Answers] 3×5:
Thanks for the reply, but the link in my post is just to a .img.xz file. It doesn't have any zip and no "batch/betch" file (I assume you meant bash?)
[General Questions and Answers] radosomalo:
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.
[General Questions and Answers] 3×5:
Thanks for the clarification. Unfortunately, my image is just an img.xz file. There's no .bat script and no zip.

I ran fastboot getvar current-slot and it says 'current-slot: b'. Then I ran fastboot flash system_b imagefile.img.xz and I got:

target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 165282916 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
OKAY [ 9.401s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
finished. total time: 14.558s

So basically the same problem as before. I tried running 'fastboot delete-logical-partition product_b' and got:

fastboot: usage: unknown command delete-logical-partition

I could try 'fastboot flash super imagefile.img.xz' but I don't know if I'm supposed to delete super first, and I don't want to make things worse. So any advice would be appreciated.
[General Questions and Answers] 3×5:
Alright, I was able to flash the GSI ROM, but it didn't work. My phone thinks the OS is corrupted. I think my only choice now is to go back to my stock ROM. I tried to flash the super partition but running

./fastboot flash super ../super.img_sparsechunk.0

and it did this through sparsechunk 26. Then I rebooted and I still have no OS.

Now this stock ROM does not have a .bat file, but it does have flashfile.xml. Is there any way I can use this to automate the flashing process? At this point, I'm thinking I'm going to have to flash every partition.

Related question: In the flashfile, it specifies partitions as logo_a, vbmeta_system_a, etc. But when I run '

fastboot getvar current-slot' it says my current slot is 'b'. So should I replace every instance of _a with _b?
[General Questions and Answers] 3×5:
@gr3uh, it sounds like you were able to get the stock ROM on your phone. DId you DL it from lolinet? Can you post the steps you took to get your stock ROM functional? My phone is a paperweight right now.