Related
Help,teach me how to update it could i use g610f firmware to update?
do this first
Go to developer options:
Settings -> Developer Options -> OEM unlocking AND ENABLE oem unlock
Knox will be tripped and system updates wont work once you root. dont matter because they wont update you
download odin
https://odindownload.com/download/#.WqPE4vluaUk
boot into download mode by holding power button and volume down
and flash this using odin latest twrp custom recovery
https://drive.google.com/file/d/1f6NaBo-0Av_x9tQa1gDT9_zlIQbuvQYm/view
select file as ap and click ap check box
after flashing twrp download the rom its a big zip file put it on ur sd card install using twrp
https://forum.xda-developers.com/showpost.php?p=75454632&postcount=301
this seems to be the most popular rom for the g610 a NoteFE port rom (and yes its nougat)
https://forum.xda-developers.com/ga...-on-nxt-exynos7870/j7-prime-sm-g610y-t3733264
according to this u can root ur phone and flash any of the roms on this page says all g610s can use the same software
just select csc (ur network region is XTC unbranded philippines (u can select globe postpaid prepaid and abscbn)
check this forum for additional roms u would like to check out
https://forum.xda-developers.com/galaxy-j7/samsung-galaxy-j7-prime--j7-on-nxt-exynos7870
is it possible to flash another country ROM version on my samsung j7prime? i.e. g610Y marshmallow (philippines) to g610y nougat (new zealand)... however, i have rooted my j7 prime to NovaOS...
any tips?
ztill hoping
There is a guide to a variety of methods, but it is updated to 2014 ...
https://forum.xda-developers.com/showthread.php?t=2620456
Does anyone know whether TWRP can be installed via download mode via Odin for a Galaxy J4 (2018) or that there are security blocks that prevent the installation of unknown firmware (oem lock)?
If so, will the first method in the above guide (under the heading METHOD I) through the built-in recovery be useful here?
If not, is there any other method that will work here without resetting the device?
Thanks for your help
shraga1 said:
There is a guide to a variety of methods, but it is updated to 2014 ...
https://forum.xda-developers.com/showthread.php?t=2620456
Does anyone know whether TWRP can be installed via download mode via Odin for a Galaxy J4 (2018) or that there are security blocks that prevent the installation of unknown firmware (oem lock)?
If so, will the first method in the above guide (under the heading METHOD I) through the built-in recovery be useful here?
If not, is there any other method that will work here without resetting the device?
Thanks for your help
Click to expand...
Click to collapse
There is a TWRP Recovery available, https://forum.xda-developers.com/ga...ecovery-twrp-3-2-3-1-galaxy-j4-j415f-t3876876 which is for the J4+ so I don't know if it'll work for your device. You can flash Recoverys only if the FRP Lock and/or the OEM Lock is disabled, they both probably will block the flashing process when they are activated. In TWRP you'll have to delete some files (something that has lockscreen.db as name or any similar files to that one) to unlock the Device without having to wipe all data.
Must Have An Unlocked Bootloader To Do This!
This A full stock firmware file I have created to flash with odin to automatically install TWRP recovery along with Disable VBMETA image. The Userdata _AIO tar file will also automatically install magislk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2
I Do Not Recommend Mixing Bit 1 And Bit 2 Firmware!!!!
Downloads
SM-G981U/U1/W- Model
G981USQU3HWB3_Bit1_Safe --This will bring you to Android 13 without loosing unlock
SM-G986U/U1/W- Model
G986USQU3HWB3_Bit1_Safe --This will bring you to Android 13 without loosing unlock
SM-G988U/U1/W- Model
G988USQU3HWB3_Bit1_Safe --This will bring you to Android 13 without loosing unlock
Odin3_v3.14.1_3B_PatcheD.zip
TWRP Recovery Provide by @afaneh92
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load files in appropriate odin slots
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Features
No patches or mod zips are needed phone will already be rooted
Fix Safetynet
Bluetooth is patched for pairing to survive reboots
Samsung Health working
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
elliwigy
klabit87
Krog18
me2151
stang5litre
Raymonf for modified odin
rayan-refoua for boot animation
TheMadScientist
afaneh92
kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
JDBarlow for test S20 stuff
markfm For Bitsafe Firmware
Source For Userdata AIO
Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Z Fold2 5G BL V1
Fold 5G BL V1-4
Fold BL V1-4
Z Flip 5G BL V1
Z Flip BL V1-3
Note series 20 BL V1
S20 series BL V1
S20 FE 5G BL V1-2
Note 10 series BL V1-5
S10 Lite BL V1-3
Note 10+ 5G N976U BL V1-4
Note 10+ 5G N976V BL V1-5
S10 5G BL V1-5
S10 series BL V1-4
Note 9 BL V1-7
S9 series BL V1-9
Tab S6 BL V1-3
Tab S7 BL V1
Tab S7+ BL V1
A71 5G BL V1-2
A51 BL V1-5
A51 5G BL V1-4
A50 A505W BL V1-A
A50 A505U BL V1-B
S21 BL V1
A32 5G BL V1-3
Tab Active Pro 10.1 BL V1-4
XCover Pro BL V1-7
Good to see you here, I will make use of this. Thanks, I hope to see you playing with roms!
jhr5474 said:
Good to see you here, I will make use of this. Thanks, I hope to see you playing with roms!
Click to expand...
Click to collapse
I dont have s20 so Im limited what I can make
If tokens can be updated to flash higher bootloaders then I will adjust files accordingly
This works great! I flashed the entire U1 DUB7 update with the force wipe with BL files in the USERDATA slot. Everything went well.
Tried this on my G981V and failed on (auth). Was worth the try although I soft bricked my phone lol
scepz said:
Tried this on my G981V and failed on (auth). Was worth the try although I soft bricked my phone lol
Click to expand...
Click to collapse
So please give more info. What file you tried flash. You should be able to flash the ones that don’t have bootloaders in them
jrkruse said:
So please give more info. What file you tried flash. You should be able to flash the ones that don’t have bootloaders in them
Click to expand...
Click to collapse
Both files that say contain bootloader from UI 3.0 and that I'll keep my unlock token. kg status was checking as well.
scepz said:
Both files that say contain bootloader from UI 3.0 and that I'll keep my unlock token. kg status was checking as well.
Click to expand...
Click to collapse
Sorry I had no clue there was an sm-g981v mode. Just don’t flash the bl file of your stock firmware and you will be fine using my userdata without bl files
jrkruse said:
Sorry I had no clue there was an sm-g981v mode. Just don’t flash the bl file of your stock firmware and you will be fine using my userdata without bl files
Click to expand...
Click to collapse
I tried with just your user data file still didn't work. So your saying next time use all files besides BL?
scepz said:
I tried with just your user data file still didn't work. So your saying next time use all files besides BL?
Click to expand...
Click to collapse
I'll make a specific one for sm-g981v
jrkruse said:
I'll make a specific one for sm-g981v
Click to expand...
Click to collapse
Ok
scepz said:
Ok
Click to expand...
Click to collapse
files in the OP
jrkruse said:
Must Have An Unlocked Bootloader To Do This!
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install magislk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2
Downloads
SM-G981U/U1/W- Model
These contains bootloaders from One UI 3.0 firmware so you will not loose token and do not need to alter firmware you are flashing
They contain bootloaders too allow you too load full stock One UI 3.1 firmware in odin without having to worry about removing certain files as the bootloaders in the USERDATA file will keep you on the correct bootloaders.
USERDATA_AIO_G981_FORCE_WIPE.tar.md5
This will force a wipe of data no mater what. This Must Be Used On U1 Firmware and can be used on U firmware if you choose so.
USERDATA_AIO_G981_NO_WIPE.tar.md5
This will only wipe if you have encrypted data. This Can Only Be Used On U firmware
These do not contains bootloaders from One UI 3.0 firmware and you will loose token if you flash higher version bootloaders unless you alter the firmware. You can use these to do the firmware as you see fit.
USERDATA_AIO_G981_FORCE_WIPE_NO_BL.tar.md5
This will force a wipe of data no mater what. This Must Be Used On U1 Firmware and can be used on U firmware if you choose so.
USERDATA_AIO_G981_NO_WIPE_NO_BL.tar.md5
This will only wipe if you have encrypted data. This Can Only Be Used On U firmware
SM-G981V- Model
These contains bootloaders from One UI 3.0 firmware so you will not loose token and do not need to alter firmware you are flashing
They contain bootloaders too allow you too load full stock One UI 3.1 firmware in odin without having to worry about removing certain files as the bootloaders in the USERDATA file will keep you on the correct bootloaders.
USERDATA_AIO_G981V_FORCE_WIPE.tar.md5
This will force a wipe of data no mater what. This Must Be Used On U1 Firmware and can be used on U firmware if you choose so.
USERDATA_AIO_G981V_NO_WIPE.tar.md5
This will only wipe if you have encrypted data. This Can Only Be Used On U firmware
These do not contains bootloaders from One UI 3.0 firmware and you will loose token if you flash higher version bootloaders unless you alter the firmware. You can use these to do the firmware as you see fit.
USERDATA_AIO_G981V_FORCE_WIPE_NO_BL.tar.md5
This will force a wipe of data no mater what. This Must Be Used On U1 Firmware and can be used on U firmware if you choose so.
USERDATA_AIO_G981V_NO_WIPE_NO_BL.tar.md5
This will only wipe if you have encrypted data. This Can Only Be Used On U firmware
SM-G986U/U1/W- Model
These contains bootloaders from One UI 3.0 firmware so you will not loose token and do not need to alter firmware you are flashing
They contain bootloaders too allow you too load full stock One UI 3.1 firmware in odin without having to worry about removing certain files as the bootloaders in the USERDATA file will keep you on the correct bootloaders.
USERDATA_AIO_G986_FORCE_WIPE.tar.md5
This will force a wipe of data no mater what. This Must Be Used On U1 Firmware and can be used on U firmware if you choose so.
USERDATA_AIO_G986_NO_WIPE.tar.md5
This will only wipe if you have encrypted data. This Can Only Be Used On U firmware
These do not contains bootloaders from One UI 3.0 firmware and you will loose token if you flash higher version bootloaders unless you alter the firmware. You can use these to do the firmware as you see fit.
USERDATA_AIO_G986_FORCE_WIPE_NO_BL.tar.md5
This will force a wipe of data no mater what. This Must Be Used On U1 Firmware and can be used on U firmware if you choose so.
USERDATA_AIO_G986_NO_WIPE_NO_BL.tar.md5
This will only wipe if you have encrypted data. This Can Only Be Used On U firmware
SM-G988U/U1/W- Model
These contains bootloaders from One UI 3.0 firmware so you will not loose token and do not need to alter firmware you are flashing
They contain bootloaders too allow you too load full stock One UI 3.1 firmware in odin without having to worry about removing certain files as the bootloaders in the USERDATA file will keep you on the correct bootloaders.
USERDATA_AIO_G988_FORCE_WIPE.tar.md5
This will force a wipe of data no mater what. This Must Be Used On U1 Firmware and can be used on U firmware if you choose so.
USERDATA_AIO_G988_NO_WIPE.tar.md5
This will only wipe if you have encrypted data. This Can Only Be Used On U firmware
These do not contains bootloaders from One UI 3.0 firmware and you will loose token if you flash higher version bootloaders unless you alter the firmware. You can use these to do the firmware as you see fit.
USERDATA_AIO_G988_FORCE_WIPE_NO_BL.tar.md5
This will force a wipe of data no mater what. This Must Be Used On U1 Firmware and can be used on U firmware if you choose so.
USERDATA_AIO_G988_NO_WIPE_NO_BL.tar.md5
This will only wipe if you have encrypted data. This Can Only Be Used On U firmware
Odin3_v3.14.1_3B_PatcheD.zip
TWRP Recovery Provide by @afaneh92
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions For Newly Unlocked Devices
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load file USERDATA_SLOT_G98*U_**.tar.md5 you must choose one of the FORCE_WIPE files and load in the USERSDATA slot of odin and flash file
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Install Instructions For Updating Firmware On Phone Already Unlocked
1. Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above
2. Use patched 3.14 odin and load stock firmware in appropriate slots use regular CSC file in the CSC slot and load file one of the USERDATA_SLOT_G98*U_**.tar.md5 in the USERSDATA slot of odin and flash firmware. Do not use the User Data file that comes with firmware.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not
Install Instructions If Updating Images With TWRP
1. When done flashing images in TWRP Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above.
2. Use patched 3.14 odin and load file USERDATA_AIO_G98*_NO_WIPE_NO_BL.tar.md5 in the USERSDATA slot of odin and flash file.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not.
4. Alternatively to using USERDATA_AIO_G98*_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_22_S20_Series.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
Fix Safetynet
Bluetooth is patched for pairing to survive reboots
Samsung Health working
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
@elliwigy
@klabit87
@Krog18
@me2151
@stang5litre
@Raymonf for modified odin
@rayan-refoua for boot animation
@TheMadScientist
@afaneh92
@kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
@JDBarlow for test S20 stuff
Click to expand...
Click to collapse
Does this work on s20 plus g9860?
If not...can you make a file for SM-G9860 TGY.
This is the link for latest firmware
Download Samsung Galaxy S20+ SM-G9860 TGY Hong Kong firmware
All Samsung firmwares for Galaxy S20+ in Hong Kong with model code SM-G9860. We offer free and fast download options. Check them out now.
www.sammobile.com
Gianni's said:
Does this work on s20 plus g9860?
If not...can you make a file for SM-G9860 TGY.
This is the link for latest firmware
Download Samsung Galaxy S20+ SM-G9860 TGY Hong Kong firmware
All Samsung firmwares for Galaxy S20+ in Hong Kong with model code SM-G9860. We offer free and fast download options. Check them out now.
www.sammobile.com
Click to expand...
Click to collapse
The ones without bootloaders will work. The NO_BL ones. Probably have to use the force wipe one
So, if I have the S20+ (US Cellular) and want to try the 3.1 firmware:
1.) Download the firmware
2.) Put your file for it into user data field in Odin
3.) Put in AP, CSC (home or whatever to not overwrite my USC one I think) and the rest EXCEPT for the bootloader into Odin
4.) Flash as usual and then everything should work. I'll keep my unlock and be able to use the 3.1 firmware?
rlewis312010 said:
So, if I have the S20+ (US Cellular) and want to try the 3.1 firmware:
1.) Download the firmware
2.) Put your file for it into user data field in Odin
3.) Put in AP, CSC (home or whatever to not overwrite my USC one I think) and the rest EXCEPT for the bootloader into Odin
4.) Flash as usual and then everything should work. I'll keep my unlock and be able to use the 3.1 firmware?
Click to expand...
Click to collapse
I did it that way, used the BL included file and flashed all the stock files, after the full wipe everything that I needed was included. Worked great, on UI 3.1 rn
It worked for me also, thanks for making this.
hi jrkruse i just got an A71 5g unlocked (thanks afaneh92), and i was wondering if you could make an aio userdata file for it? so i can flash ui 3.1 firmware to it? like this for my s20 ultra..(this thread)
I have a samsung galaxy sm-a325m and sl try to root it, the odin gives me the following error: CUSTOM BINARY BLOCKED BY OEM LOCK . vbmeta, but when putting the file that was not altered by magisk if it lets me, does anyone have a solution?
The message is pretty self-explanatory. before trying to flash custom binaries make sure it is allowed by OEM.
enable OEM unlocking in developer options. enter Download mode and unlock bootloader (will factory reset device). reboot into One UI and double check OEM unlocking in developer options.
then you can flash magisk patched boot + vbmeta.
Welcome to XDA and enjoy the forums!
Cheers
'Introductions' are only for introductions. Support goes into the appropriate section.
No introduction in post, thread deleted.
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Gateway05184 said:
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Click to expand...
Click to collapse
Under no circumstance should you relock the bootloader. The only OS that I know of that currently lets you do that on any device is Graphene OS on pixel devices. And that is written by extremely gifted developers. So... no... not now or anytime soon. Sorry!
Nope. While you could relock your bootloader now, you'd get an error message the next time you turned on your phone and it would refuse to boot. (And there's no guarantee that you could recover it, though usually the MSM tool works.) In most cases, you should never relock the bootloader unless you're on stock, unmodified firmware. In some cases, it is possible if the custom ROM you're using instructs you to relock your bootloader and provides their own keys for you to flash or if you build and sign your own ROMs yourself, but otherwise, it's just not worth it.
You should read this reddit post for more details as to why you shouldn't relock your bootloader.
Yeah, I kind of figured. I tried locking the bootloader out of curiosity (obviously, you shouldn't do this.) which caused it to brick. I unbricked it using the MSM tools for the specific model. I also tried flashing the public key but it only allows recovery to boot and boot loops if you just leave it sit. lol
Don't' try this ever, you will most probably soft brick the device without being able to recover it.
You can only safely relock the bootloader on stock OS without the risk of bricking the device.
Sprunglicious said:
Under no circumstance should you relock the bootloader. The only OS that I know of that currently lets you do that on any device is Graphene OS on pixel devices. And that is written by extremely gifted developers. So... no... not now or anytime soon. Sorry!
Click to expand...
Click to collapse
Gateway05184 said:
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Click to expand...
Click to collapse
Not entirely true. CalyxOS allows relocking bootloader on Pixels. My own development for Oneplus 6/6T/8/8T/8Pro/9 and 9Pro allows relocking bootloader.
I managed to find a way to relock the bootloader with LineageOS installed by compiling it from source and patching a few files. Then I flashed the avb_custom_key partition via fastboot with the key I used to sign the image I've compiled. This resulted in me getting the yellow error screen (Your device has loaded a different OS.) rather than the usual orange screen you get with the bootloader unlocked. I even used a tool called "avbroot" to patch the image for magisk support.
just use the MSMDownload tool for the firmware you want, it will set it back to factory defaults and factory OS including re-locking the bootloader
NOTE: if you ever want to unlock it again just use the token file/bin file that oneplus sent you originally to unlock. no need to re-apply or ask oneplus again for new token, can just use the original one they sent you.
Gateway05184 said:
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Click to expand...
Click to collapse
I don't like seeing my Nord n200 boot to the unlocked bootloader screen, and found a way to prevent that.
I found the method on the Reddit forum for LineageOS.
From CevicheMixto:
I was able to complete the upgrade (dirty flash from the latest LineageOS 19.1). Here's what I had to do.
First, I upgraded the device firmware, following this guide. Note that the oneplus.com page that is linked from that guide does not appear to actually provide firmware for the Nord N200. The Oxygen Updater app does allow you to download the firmware, once the app's settings have been changed to enable "Advanced mode." It will save the firmware file in the /sdcard directory, and adb can be used to transfer it to your PC. (Alternatively, the firmware can be directly downloaded from https://android.googleapis.com/packages/ota-api/package/6be3f133f8fb9bbcc30d787679bd7b5da5e30995.zip.)
At this point, my phone would not boot into the LineageOS recovery (19.1 or 20); it kept returning to bootloader mode. I fixed this by flashing the LineageOS 20 boot, dtbo, and vendor_boot images onto the device. These images can be extracted from the LineageOS 20 ZIP file with payload-dumper-go, or they can be downloaded from the dre builds page.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
(Unlike fastbootd, the bootloader does not appear to support the --slot=all option, but I only needed to flash these for the active slot.)
I was now able to boot into the (installed) LineageOS 20 recovery, choose "Apply update" and "Apply from ADB" to put the device into sideload mode. I then followed the upgrade instructions to flash the LineageOS 20 ZIP file, reboot back to recovery, and flash the MindTheGapps ZIP file.
Do yourself a favor and just load Oxygen Updater onto another Android phone and download the files. It will pop up a notice that the phone isn't the correct one, but just click advanced and download the file, then continue on.
My Nord n200 now boots with the OnePlus logo then directly to LineageOS with Android 13
KeysStickler said:
I don't like seeing my Nord n200 boot to the unlocked bootloader screen, and found a way to prevent that.
I found the method on the Reddit forum for LineageOS.
From CevicheMixto:
I was able to complete the upgrade (dirty flash from the latest LineageOS 19.1). Here's what I had to do.
First, I upgraded the device firmware, following this guide. Note that the oneplus.com page that is linked from that guide does not appear to actually provide firmware for the Nord N200. The Oxygen Updater app does allow you to download the firmware, once the app's settings have been changed to enable "Advanced mode." It will save the firmware file in the /sdcard directory, and adb can be used to transfer it to your PC. (Alternatively, the firmware can be directly downloaded from https://android.googleapis.com/packages/ota-api/package/6be3f133f8fb9bbcc30d787679bd7b5da5e30995.zip.)
At this point, my phone would not boot into the LineageOS recovery (19.1 or 20); it kept returning to bootloader mode. I fixed this by flashing the LineageOS 20 boot, dtbo, and vendor_boot images onto the device. These images can be extracted from the LineageOS 20 ZIP file with payload-dumper-go, or they can be downloaded from the dre builds page.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
(Unlike fastbootd, the bootloader does not appear to support the --slot=all option, but I only needed to flash these for the active slot.)
I was now able to boot into the (installed) LineageOS 20 recovery, choose "Apply update" and "Apply from ADB" to put the device into sideload mode. I then followed the upgrade instructions to flash the LineageOS 20 ZIP file, reboot back to recovery, and flash the MindTheGapps ZIP file.
Do yourself a favor and just load Oxygen Updater onto another Android phone and download the files. It will pop up a notice that the phone isn't the correct one, but just click advanced and download the file, then continue on.
My Nord n200 now boots with the OnePlus logo then directly to LineageOS with Android 13
Click to expand...
Click to collapse
That doesn't solve what I was originally attempting to do but I appreciate the suggestion nonetheless. However, the DE2117 OTA update is not meant for the carrier exclusive models (i.e. DE2118 aka the MetroPCs T-Mobile model.) I've already attempted this on my own DE2118 and it resulted in a boot loop. This problem doesn't exist in Lineage 19.1.
Gateway05184 said:
That doesn't solve what I was originally attempting to do but I appreciate the suggestion nonetheless. However, the DE2117 OTA update is not meant for the carrier exclusive models (i.e. DE2118 aka the MetroPCs T-Mobile model.) I've already attempted this on my own DE2118 and it resulted in a boot loop. This problem doesn't exist in Lineage 19.1.
Click to expand...
Click to collapse
I used this to update to LineageOS 20
there is no known way to relock the boot-loader on a custom rom on the nord n200 . However you can re-lock in on the official firmware. You can always go back to the official firmware with the locked bootloader by flashing the official firmware via MSM Download tool