Hello,
I found a firmware file for the Nord N20 5g. However, it is CPH2459_11_A.06, while my phone says it is GN2200_11_A.06. Would it still be possible to do a local update to pull the boot image, or must the CPH and GN match? I have the T-Mobile version, bootloader unlocked, and network unlocked , along with the July security patch.
Thanks!
Take a full-backup of your firmware and find out.. lol.
DrScrad said:
Take a full-backup of your firmware and find out.. lol
Click to expand...
Click to collapse
I'm unfortunately not that brave
Rogo00 said:
I'm unfortunately not that brave
Click to expand...
Click to collapse
Want me to give it a go?
DrScrad said:
Want me to give it a go?
Click to expand...
Click to collapse
It would be awesome just to see if it works, but I don't know if it would harm your phone or not, and I would feel terrible if it did.
i would try flashing to inactive slot then switch over and maintain your functional system
PsYk0n4uT said:
i would try flashing to inactive slot then switch over and maintain your functional system
Click to expand...
Click to collapse
I'm still too new to rooting to do this successfully, I'm afraid
cph2459 is the unlocked version of the N20 5G correct? could you link the firmware please?
It is the unlocked version. I have the TMO version but it is network unlocked. The firmware can be found here: https://mega.nz/file/MXckFawK#IZ1ypD5Ftqw5Oz3oaeHLahqfUeaD6DlTzHCjeR3oseg
Also, this one is GN2200, but it is 11_A.05. Would it downgrade with the current patch? https://mega.nz/file/lX1H3Z5C#hUVmdbWUFI0bt0WQZVfaenTfVwoOqlfn2oexY5uC-Hs
If the OTA contains patches for all the required images then it SHOULD. But don't take my word on that.
What exactly are you trying to accomplish? Do you simply need a backup? It would probably be best to load a prerooter gsi with DSU sideloader and just use Partitions Backup and Restore app from playstore and backup all your partitions then just add them all to a single archive to make it easier to manage. You can select in options to save as raw (.img) and then just compress them all into a single archive and that would make it even easier to retrieve the needed partition images if you happen to need to restore anything.
PsYk0n4uT said:
If the OTA contains patches for all the required images then it SHOULD. But don't take my word on that.
What exactly are you trying to accomplish? Do you simply need a backup? It would probably be best to load a prerooter gsi with DSU sideloader and just use Partitions Backup and Restore app from playstore and backup all your partitions then just add them all to a single archive to make it easier to manage. You can select in options to save as raw (.img) and then just compress them all into a single archive and that would make it even easier to retrieve the needed partition images if you happen to need to restore anything.
Click to expand...
Click to collapse
I see. Basically I'm just trying to obtain root access. You mentioned prerooted gsi? I will need to read up more on this. Man this would be a lot easier with TWRP lol
waiting to hear from someone about a twrp that has been in the works. we tried one yesterday that didnt work. a different device tree is needed from the one that was used.
using DSU loader you can temporarily load a prerooted gsi and back everything up and move it to your pc and then move the boot.img to your internal storage where you can easily find it with the magisk app. install and load the magisk app and patch the boot.img then move the patched boot image to your pc and flash it in fastboot. that will give you a permanent root unless you prefer to stick with the gsi you sideloaded. but keep in mind any gsi you load with DSU Sideloader will be gone when you reboot the phone and your back to your regular system. you can use the sticky command if you want to keep the gsi installed but be sure to allocate plenty of space for your gsi if you plan on using it long term
if your on the may or july security patch you should be able to just download the patched boot.img from my other thread. i posted the stock images too in case you need to go back to stock or have issues booting. that being said. its best to just make your own backups. the july patch is GN2200_11_A.06
PsYk0n4uT said:
if your on the may or july security patch you should be able to just download the patched boot.img from my other thread. i posted the stock images too in case you need to go back to stock or have issues booting. that being said. its best to just make your own backups. the july patch is GN2200_11_A.06
Click to expand...
Click to collapse
I didn't know you did the July patch as well. I will check it out now
Also if and when you do flash the magisk patched boot images, do this command before and/or after flashing the boot.img:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Someone else has tried this and lost radios..... Can maybe get everything working again by reflashing the FULL BACKUP you took before cross flashing.... This would be an experiment though so don't attempt if your not ready to spend some time researching and unbricking your device should it be necessary
I tried it. I'm bootlooped
bricklife4me said:
I tried it. I'm bootlooped
Click to expand...
Click to collapse
I was just about to ask if you had two different devices because remember me telling you to be careful and not get your flashes mixed up?
DrScrad said:
I was just about to ask if you had two different devices because remember me telling you to be careful and not get your flashes mixed up?
Click to expand...
Click to collapse
I have a samsung a02, pixel 7 pro, moto g 5 g , oneplus n20 , iphone 12, iphone 6 , 4 tablets, and two LG
Related
Hello all, I am trying to make a custom recovery for my new phone, the Moto G30. However this is my first phone that is A/B partitioned so I don't know what to do fully. I am trying to extract the recovery.img because that is whats needed in order to make a custom recovery. However, when I look into the device firmware the only image files I see are: boot, bootloader, dbto, radio, vbmeta, vbmeta_system and vendor_boot. The system files are all seperated into "sparsechunks".
On a non-A/B device getting the recovery was as easy as downloading the stock firmware, extracting, and then recovery.img was right there. Now it seems to be different and I don't know what to do, I couldn't find anything on google about how to do this. I am sure it is easy enough though. Thank you in advance.
Drysauce said:
I am sure it is easy enough though.
Click to expand...
Click to collapse
Sure. Everything can be easy - after you've done it at least once.
Try searching the boot... it probably lies there somewhere....
CXZa said:
Sure. Everything can be easy - after you've done it at least once.
Try searching the boot... it probably lies there somewhere....
Click to expand...
Click to collapse
OK thank you
@Drysauce
Don't get confused: An Android device with A/B partition layout simply means it has has 2 slots, named A and B. Slot A holds the active Android OS whereas slot B is reserved to receive / hold Android OS updates ( read: OTAs ).
And the empty slot can be converted to a new mountpoint to hold say... root
so what to do in this case
Build number
DE2117_11_C.17
Hardware version
DE2117_11
I keep seeing T-Mobile version, INTL version, DE18 and all that. I'm so confused, I just need root.
I believe that's the international version since mine is DE2117. Not sure because of the "_11" at the end of yours. Maybe that signifies you updated it, in which case you will probably have to downgrade it.
Rooting this phone is a headache btw. I'm not even sure if I should be providing instructions because I bricked mine multiple times while attempting and had to keep restoring with MSMtools, and now I'm not even sure I can update it without losing root. I don't even think I did anything differently when it finally worked, it's just luck.
Anyway, first step is to download the international version of the MSMtools and payload dumper. look up how to dump the boot image with payload dumper from the MSMtools. And make sure you don't attempt to do anything to the device before unlocking your bootloader (and you'll have to unlock it again everytime you restore with MSMtool).
From there you should be able to follow guides.
@swee08315
I downloaded the latest update available from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
But the phone is updated to July. Hmmmm.....
I've extracted the boot.img from there. Patched it with magisk. I'm about to fastboot flash it..... Wish me luck, I'm going in.
Unless there's a way to extract the boot.img that's currently installed. I think I'll poke around and look for that rather than simply hoping this is the right one.
jova33 said:
I downloaded the latest update available from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
But the phone is updated to July. Hmmmm.....
I've extracted the boot.img from there. Patched it with magisk. I'm about to fastboot flash it..... Wish me luck, I'm going in.
Unless there's a way to extract the boot.img that's currently installed. I think I'll poke around and look for that rather than simply hoping this is the right one.
Click to expand...
Click to collapse
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
A1.1 will get the boot.img your device currently has.
Edit: if you flashed the boot.img from the official site, then your device is most likely bricked. I'll fetch my boot.img and link it here (won't be magisk patched).
justauserthatusesaphone said:
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
A1.1 will get the boot.img your device currently has.
Edit: if you flashed the boot.img from the official site, then your device is most likely bricked. I'll fetch my boot.img and link it here (won't be magisk patched).
Click to expand...
Click to collapse
yeah, I bricked it
Nothing a few beers won't cure.
Once I unbrick, I will do A1.1 though.
jova33 said:
yeah, I bricked it
Nothing a few beers won't cure.
Once I unbrick, I will do A1.1 though.
Click to expand...
Click to collapse
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
justauserthatusesaphone said:
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
Click to expand...
Click to collapse
nah, I don't wipe until I get into the shower.
But yeah, I completely reset everything with MSM tools. In the process of letting all the updates go through. Thanks for the boot img though, It'll save me the trouble of having to pull it using the msm tools.
Edit: I forgot to do the vbmeta stuff after flashing the magisk patched. How do I fix? Can I borrow your vbmeta, @justauserthatusesaphone ?
justauserthatusesaphone said:
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
Click to expand...
Click to collapse
So I can update my oneplus and then patch and use this bootimg to regain root? Or will trying to update my rooted device brick it and I'd have to wipe everything and start from scratch anyway?
jova33 said:
nah, I don't wipe until I get into the shower.
But yeah, I completely reset everything with MSM tools. In the process of letting all the updates go through. Thanks for the boot img though, It'll save me the trouble of having to pull it using the msm tools.
Edit: I forgot to do the vbmeta stuff after flashing the magisk patched. How do I fix? Can I borrow your vbmeta, @justauserthatusesaphone ?
Click to expand...
Click to collapse
I'll get it when I'm on my PC
the c17 one, correct?
justauserthatusesaphone said:
I'll get it when I'm on my PC
the c17 one, correct?
Click to expand...
Click to collapse
Don't worry about it. I redid the MSM tool since the phone wasn't even setup yet, no big loss.
swee08315 said:
So I can update my oneplus and then patch and use this bootimg to regain root? Or will trying to update my rooted device brick it and I'd have to wipe everything and start from scratch anyway?
Click to expand...
Click to collapse
So, I don't know how this phone handles updates. I've had previous phones that if it was rooted, the OTA would fail to install, and others that the OTA would install and replace the boot.img, so root would be removed.
The first case, I would have to unroot, restore the stock boot.img, and then it could take the OTA update.
The other case I would have to block OTAs until I could get the boot.img for it, so that I could root the update.
The guide posted here https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
part B explains how to update and maintain root. Seems like it's the first case. Restore stock boot.img.
jova33 said:
So, I don't know how this phone handles updates. I've had previous phones that if it was rooted, the OTA would fail to install, and others that the OTA would install and replace the boot.img, so root would be removed.
The first case, I would have to unroot, restore the stock boot.img, and then it could take the OTA update.
The other case I would have to block OTAs until I could get the boot.img for it, so that I could root the update.
The guide posted here https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
part B explains how to update and maintain root. Seems like it's the first case. Restore stock boot.img
Click to expand...
Click to collapse
You could turn off automatic system updates so it doesn't reboot automatically and then you install the update and when it asks you to restart, go into magisk and click install and install to inactive slot then you go back to the system update page and click restart. I don't know whether Google's ota system makes it easier or not.
Late reply but I can confirm that all updates fail on this device and you would have to unroot to get the update, and then root again. Very annoying that it's constantly notifying me that an update is available or that it tried to update last night and failed
swee08315 said:
Late reply but I can confirm that all updates fail on this device and you would have to unroot to get the update, and then root again. Very annoying that it's constantly notifying me that an update is available or that it tried to update last night and failed
Click to expand...
Click to collapse
I never had that issue but if you do, press uninstall and restore images (DON'T REBOOT), then after installing the updates (DON'T REBOOT) press install and install to inactive slot. Press the reboot button and you're done.
**Edit: Be sure to read comments at the end of this post******
I've already posted this a few times but I figured I would try to save some people time who want/need to root from any security patch. This is a copy and paste from an answer I gave in another thread but it's a basic how to.
Install DSU sideloader app from playstore to boot a prerooted GSI then use Partitions Backup and Restore app from playstore to save copies on your device. Install magisk app and patch the extracted boot.img and then transfer backups along with the patched boot image to your PC for safekeeping and flash the patched boot.img in fastboot. You can rename any .bin files to .img to flash them if they get extracted as a .bin file. Check your settings in the partitions Backup and Restore app before starting the backup process. You can choose to save them in an easy to find directory and for me it was better to choose to save them RAW/uncompressed then just compress them all into a single archive rather than having a hundred separate archives for each individual partition because it makes it easier if you have to reflash things if you need to recover. You may want to disable battery optimization for the app because it takes a while to extract all the images doing a full backup but its well worth the wait time if it saves you from a brick later on.
I wish I had time to elaborate but hopefully someone else can take the time to elaborate and add to this for anyone needing step by step. I'm surprised nobody has done this already.
Credits to AndyYan for giving advice on the root method. I stole this from him and just made a post with a title that makes it easier to find since so many are still asking how to go about rooting their devices.
*****REQUEST TO COMMUNITY********
There are many who are already on August Security patch and i dont have time to update and post the newest images. So if you are on august patch and pull backups I ask that someone please be so kind as to upload a copy of your backup to Google Drive or a filehosting server of choice and post a new thread so that others can unbrick their devices.
*Please ***DO NOT include**** the following partitions*:
DEVINFO
DINFO
FRP
KEYMASTER_A
KEYMASTER_B
KEYSTORE
LOGDUMP
***MDM1M9KEFS1
***MDM1M9KEFS2
***MDM1M9KEFS3
***MDM1M9KEFS4
MODEMDUMP
OPLUS_SEC_A
OPLUS_SEC_B
RAWDUMP
SECDATA
STORSEC
USERDATA
VM-KEYSTORE
*** These partitions may/contain YOUR personal device info, DO NOT make these public***
You can make a new Google account for the sole purpose of uploading these for the community so as not to fill your own GDrive. Be sure to change permissions for the images to share with anyone who has the link. This would be very much appreciated by many.
*****Update 09/18/2022*****
Thanks to ctschrodinger88 & dmtec for posting more detailed instructions!!! you can find ctschrodinger88's instructions below, scroll down to the 5th post.
dmtec also posted instructions in another thread linked here: https://forum.xda-developers.com/t/august-boot-img.4491831/post-87426877
we are still in need of august modems if anyone cares to upload them to their drive and link them or any other filehosting service.
can you suggest me a pre rooted gsi rom please?
thanks
fictisio said:
can you suggest me a pre rooted gsi rom please?
thanks
Click to expand...
Click to collapse
i used crdroid but its buggy, launcher crashes but its useable, atleast to get this done and then be sure to discard it in the DSU sideloader notification when you reboot so the inactive slot is empty, it will make for easier updates/mods later
has anyone had luck flashing the file in this article? https://www.getdroidtips.com/oneplus-nord-2t-5g-firmware-flash-file-2/#google_vignette
I used the info provided and referenced here as a guide and some external pieces and have things working.
I'll caveat the following, I don't remember the current firmware version I started with, but I'll try to remember to update.
I have the Nord N20 5g, but not the T-mo branded one, though in looking at this, the concepts should be the same.
Base assumptions:
- If you haven't done these beforehand, stop and take care of it. Research if you need, but please DO NOT just keep going or copy, paste, and run, without understanding to some extent what you're doing. If you just run commands it can be much harder to fix later.
a. Your phones bootloader is unlocked. (If you haven't already done it, when you do, your data will be gone, so if you care, back it up NOW)
b. You have access to an Android terminal of some sort (adb or on-device terminal) and you know how to use it. Unless you absolutely can't use a computer for some reason, I would use adb, it makes data backup easier (IMO).
c. You have somewhere to store your backed up partitions (THIS IS IMPORTANT)
Step 0: Download a pre-rooted Generic System Image (GSI) to use. Put it in a good working directory. This page links to several. https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I used the LineageOS image by @AndyYan
If you are wondering about the various file endings this is the basic version
Code:
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
From: https://forum.xda-developers.com/t/teclast-t30-t1px-suitable-gsi-roms.4211427/
Step 1: Enable the Dynamic System Update (DSU) feature flag, you can follow the exact steps for this in this section https://developer.android.com/topic/dsu#feature-flag
If you are unsure, just run the `adb shell` command.
Step 2:
If the image you downloaded needs to be in ".gz" format. Some of the tools will handle alternate types, but that's because it rebundles it at ".gz", you can save some effort doing it yourself.
Code:
gzip -c [IMG_NAME]..img> [IMG_NAME].gz
Step 3: Push the image to the device
`adb push [IMG_NAME].gz /storage/emulated/0/`
This is where I switched from ADB to on-the-device.
Step 4: Download the DSU Sideloader: https://github.com/VegaBobo/DSU-Sideloader
You can do this with adb but I wasn't able to get it to run, so I went with the DSU Sideloader app above which made it much simpler.
Step 5: Run DSU Sideloader. You can follow the instruction there in the README. You will need to run a command that the app provides, either via adb or an emulator. Then you will reboot via the notification.
Step 6: [Once you reboot] Enable Developer tools in phone settings.
Step 7: BACKUP, BACKUP, BACKUP (Please do this now. It will help make life much, much better if you ever have an issue and need to reset.)
This was my process:
Bash:
adb shell
su
mkdir /sdcard/partitions
cd /dev/block/by-name/
for x in *; do dd if=/dev/block/by-name/$x of=/sdcard/partitions/$x ; done
# Note the collective size will be greater than the default space on the GSI boot, so you will want to separate things
# Back on local machine
mkdir [working_dir]
cd [working_dir]
adb pull /sdcard/partitions
# Your files from the adb command should populate the folder
mv [working_dir]/partitions/* [working_dir]/
# On device
rm /sdcard/partitions/*
# repeat the commands above as often as needed.
I don't know for sure all the files you will want to backup, but I pulled everything just to be safe. Keep them safe, because it is your safety net if you fall.
Step 8: Get boot_a or boot_b back on the device along with Magisk.apk (Please only download from here: https://github.com/topjohnwu/Magisk/releases)
Step 9: Install Magisk.apk (you can do this via
Code:
adb install ./magisk.apk
)
Step 10: Launch Magisk and install it to the book image stored on your sdcard.
Step 11: Pull the patched image to your local machine.
Code:
adb pull /sdcard/Download/magisk_patched-[stuff].img
Step 12: Boot phone to fastboot
Code:
adb reboot bootloader
Step 13: This is where there is an ideal and a real.
Ideal command
Code:
fastboot boot magisk_patched.img
where fastboot transfers the files and things just work, and if you reboot the system the regular boot.img is used. I haven't been able to get that to with this device.
I instead just ran
Code:
fastboot flash boot magisk_patched.img
which replaced the existing boot image, which is good, if it works, but if it doesn't, this is why you have backups!!!! Reboot the phone.
Step 14: When you boot, finish installing Magisk and you'll be ready to go.
If I remember other steps I'll add, or if you have questions I will try to help answer.
I just got a MetroPCS nord n20 (gn2200) and will try to root in the next couple days.
ScarletWizard said:
n20
Click to expand...
Click to collapse
Have they removed the unlock portal?
Damn, it's been a long time. Glad to be back.
ScarletWizard said:
No. My serial is 7 digits
Click to expand...
Click to collapse
seems to be a common defect.... if ur device is paid off oneplus can generate you a token but it takes weeks of back-and-forth with support to get it escalated...tmobile may or may not allow you to do that on a device that isnt paid off but i wouldnt even ask tmobile about it if your not paid off already, will only make it harder for those who are trying to unlock theirs if it IS the case that tmobile doesnt want you to unlock it until youve paid the device off in full....oneplus will probably uphold tmobiles decision if your device isnt paid off. for now, we are able to unlock tmobile devices through the portal regardless of the financial status of the device. though you will still be SIM locked unless tmobile unlocks that for you. and their definitely NOT gonna do THAT til it gets paid off.
U.S. carriers dont like customers having unlocked devices and is against most user-agreement policies and can get your service terminated leaving you owing for a device you cant use and for the price of the contract you were on for service
your device is a CPH2459 and not a GN2200?
fictisio said:
can you suggest me a pre rooted gsi rom please?
thanks
Click to expand...
Click to collapse
Andy Yan's Lineage18 or 19..
DrScrad said:
Andy Yan's Lineage18 or 19..
Click to expand...
Click to collapse
pixel experience, crdroid... havent gotten kaleidoscope to work yet. Have heard that someone got aosp a13 going.... There are so many and so long as u use a matching security patch ur good. might work with a newer patch but of the ones ive tried i got thw matching patches to work. If you find one thats on a newer patch in the gsi page you should be able to follow the link and find an older release to match the patch ur on. If ur on may patch try to find a may patch just to make it pess likepy that there will be priblems. If on july or august, likewise find july or august sec patch release. newer patched systems MIGHT work with ur older patched bootloader and other partitions(modems etc...) but def would not advise just straight flashing mismatching security patches... Best to sideload first and see if u can get it working first. Its not very simple to dual boot these devices but i think someone did some work and posted a work around for doing that on a/b devices somewhere on xda......
Am willing to share my stock image with anyone willing to help. I am on the September security update on a OnePlus Nord N20 5G unlocked (Non-Carrier). I am running version 11 and android security update 2022-09-05.
I am having real issues getting LineageOS through DSU. It fails immediately on start every time. Bootloader is unlocked, it even shows through fastboot (Secure boot = on though), flag is set per instructions, and I am trying to install lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.gz . I tried two different versions of the DSU app but nada.
oromis995 said:
Am willing to share my stock image with anyone willing to help. I am on the September security update on a OnePlus Nord N20 5G unlocked (Non-Carrier). I am running version 11 and android security update 2022-09-05.
I am having real issues getting LineageOS through DSU. It fails immediately on start every time. Bootloader is unlocked, it even shows through fastboot (Secure boot = on though), flag is set per instructions, and I am trying to install lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.gz . I tried two different versions of the DSU app but nada.
Click to expand...
Click to collapse
make sure u r using a lineage version with the same security patch as your current OS if your on September u need a GSI on september. i personally gave up on lineage after trying a couple but was successful with a few others while dsu sideloader still worked for me, im not sure what i did to break it on my devices but i havent been able to get it to work on either device in a while.
i have yet to try the october firmware but it should be easy to downgrade and root if you think its the new updates. although make sure ur disabling verity. u might wanna disable the checks on vbmeta_boot too... i usually just disable it on all 3 vbmeta's to be safe.... i have a full july dump and someone else has posted the august dump on TG but that doesnt help in your case since you have the CPH2459 and we are on GN2200's nobody has been able to successfully crossflash them yet and im not sure if it will be possible or not but everyone that has tried it has bricked their devices so far. most have gotten them running again but have lost fingerprint
ScarletWizard said:
im on gn2200
Click to expand...
Click to collapse
Ok my last upload didn't upload correctly for some reason. I will re upload tomorrow I think..... I need to figure out exactly which partitions are device-specific.... I know which partitions get updated in the incrementals so if all of them don't get flashed then everything won't match but I have a feeling that the incrementals update a device-specific partition or two and if so then u will lose fingerprint at minimum...... I think I should just pull full backup of all partitions and then go for it. Worst case so long as u do everything right. U just don't boot and have to reflash the stock boot image... Be sure to flash the stock image to both slots just in case and then switch back to ur active slot and flash the patched boot image. I mean if it was me I would b comfortable doing it but that's completely ur call, I don't wanna encourage anything because there ALWAYS a risk something could go wrong. Power outage or something and it's screwed up but any time u r flashing u will always be taking a risk. Though I think the risk is minimal so long as u do everything right and there's not much to the simple root process, patch the boot image and flash, if it doesn't work then reflash the stock one. If it DIES work out for u we would b grateful for the October firmware if u wanna share it, we didn't get October yet.
ScarletWizard said:
If it dies. Lol scary.
I'm in the process of doing the partition thing
Click to expand...
Click to collapse
If it DOES.. Sry
ScarletWizard said:
who is the ADMIN of this n20 thread?
Click to expand...
Click to collapse
Just look.for the moderator edits lol
PsYk0n4uT said:
seems to be a common defect.... if ur device is paid off oneplus can generate you a token but it takes weeks of back-and-forth with support to get it escalated...tmobile may or may not allow you to do that on a device that isnt paid off but i wouldnt even ask tmobile about it if your not paid off already, will only make it harder for those who are trying to unlock theirs if it IS the case that tmobile doesnt want you to unlock it until youve paid the device off in full....oneplus will probably uphold tmobiles decision if your device isnt paid off. for now, we are able to unlock tmobile devices through the portal regardless of the financial status of the device. though you will still be SIM locked unless tmobile unlocks that for you. and their definitely NOT gonna do THAT til it gets paid off.
U.S. carriers dont like customers having unlocked devices and is against most user-agreement policies and can get your service terminated leaving you owing for a device you cant use and for the price of the contract you were on for service
Click to expand...
Click to collapse
One small problem, although Metron PCS uses T-Mobile towers, they are their own entity and T-Mobile does not have their Bootloader codes. Only OnePlus and Metro PCS have the Metro PCS unlock.bin file. That's what I came here was to try and find a dedicated metro bootloader unlock web page. Like the T-Mobile dedicated page. There is not one so it's going too take several calls over several weeks unless some one here knows a different way or a link to a metro PCS bootloader unlock page? Anyone chime in on this and save all of us that are running in circles back down the straight path to an unlocked bootloader..
jayram1408 said:
One small problem, although Metron PCS uses T-Mobile towers, they are their own entity and T-Mobile does not have their Bootloader codes. Only OnePlus and Metro PCS have the Metro PCS unlock.bin file. That's what I came here was to try and find a dedicated metro bootloader unlock web page. Like the T-Mobile dedicated page. There is not one so it's going too take several calls over several weeks unless some one here knows a different way or a link to a metro PCS bootloader unlock page? Anyone chime in on this and save all of us that are running in circles back down the straight path to an unlocked bootloader..
Click to expand...
Click to collapse
I'm about to file a FCC complaint to get mine then.
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.
Hello, just bought the One Plus Nord N20 unlocked version with the intent of rooting it and installing a ROM. I haven't turned it on because I don't want it to upload the latest security patch and make itself unrootable, so I have nothing to backup. Ideally I would want to install e/OS, but have not rooted nor unlocked the bootloader of a device since 2012, so I essentially know nothing. Can someone please explain if:
- Is this is possible?
- If it is, is it a bad idea?
- Is the GSI for e/OS absent for this phone, and is this an issue?
- Is using a GSI a placeholder until a true custom ROM is made?
- Should I wait until the process is more mature?
- I am told to wait until I know what I am doing. Where should I learn / practice since there is still little documentation for this specific phone?
Thank you for your time!
Oromis995
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
PsYk0n4uT said:
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
Click to expand...
Click to collapse
Thank you, that's helpful
PsYk0n4uT said:
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
Click to expand...
Click to collapse
Is this still the case? I read another thread that says this may be the reason it no longer works.
oromis995 said:
Hello, just bought the One Plus Nord N20 unlocked version with the intent of rooting it and installing a ROM. I haven't turned it on because I don't want it to upload the latest security patch and make itself unrootable, so I have nothing to backup. Ideally I would want to install e/OS, but have not rooted nor unlocked the bootloader of a device since 2012, so I essentially know nothing. Can someone please explain if:
- Is this is possible?
- If it is, is it a bad idea?
- Is the GSI for e/OS absent for this phone, and is this an issue?
- Is using a GSI a placeholder until a true custom ROM is made?
- Should I wait until the process is more mature?
- I am told to wait until I know what I am doing. Where should I learn / practice since there is still little documentation for this specific phone?
Thank you for your time!
Oromis995
Click to expand...
Click to collapse
If you think you don't need a backup because "you've not turned your phone on yet", you should probably think twice about trying to flash custom software. Especially GSI...
Just trying to save you some heart ache down the road. Cheers
mobile_sensei said:
If you think you don't need a backup because "you've not turned your phone on yet", you should probably think twice about trying to flash custom software. Especially GSI...
Just trying to save you some heart ache down the road. Cheers
Click to expand...
Click to collapse
I meant data. I know that I need the partitions
oromis995 said:
Is this still the case? I read another thread that says this may be the reason it no longer works.
Click to expand...
Click to collapse
if you decide to use the security patch it came with stock then be sure not to connect tp the internet at all because once its unlocked and rooted and downloads an update dsu sideloader will not work until that update is dealt with and system updates wont work while bootloader unlocked and definitely not going to work if any partitions are modified(not stock such as magisk patched boot image). im not sure about the september update but some did have issues with the august patch although others were successful so it may have just been user error. my suggestion is to just put dsu sideloader and a prerooted gsi on an sdcard or transfer via pc/usb cord to internal storage but don't connect to the internet and use that to gain root long enough to pull your full stock partitions backups. this would be playing it safe. then ifnyou want you can relock your bootloader and update to september/newest and pull another full backup so you have it in the case that ypur successful and if not then your bases are covered to downgrade and downgrading will be as easy as simply reflashing all the stock images you pulled the first time though you shouldnt have to reflash ALL of them but in case you want to / need to then u have them. I cant stress backups enough. I use Partitions Backup & Restore by Wanam from playstore or wherever u want to download it unless u prefer to dd everything but i like the gui its just easier. read my post on how to root any n20 as there are somegood tips there and a great response detailing the procedure and dmtec also posted a much more detailed guide. i still havr a device on May patch and the other on July