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.
Related
ntzrmtthihu777 said:
Ok. I've put together some packages to help people who unlocked their bootloaders
and got stuck on version 10.0.13, 10.0.14, or 10.0.16, or who unlocked
(or will unlock) on version 10.0.19 and wish to get whatever the next OTA version is.
reserve.10.0.*.HD61CB.7z has all the files needed to re-insert your reserve.img where
it should be and correct its permissions. It should allow you to OTA ifyou don't root
after this (this uses a temporary root), or if you unroot before trying to take it. Pick
the version that matches whatever version you are currently on.
Files:
reserve.10.0.13.HD61CB.7z
SHA256: 047c18bc7cf29aef556ed023a061276ff940201d5184355da977a911ccb43931
reserve.10.0.16.HD61CB.7z
SHA256: 0b180e338e889aee149672ba026fb02c16f56d1dfad9351dd9e9f3fabee7d310
reserve.10.0.19.HD61CB.7z
SHA256: 34f92a7f114d3bb4dd8e7cf5aee47ad3909f79fa8ccc97fdaa417ef422dc21ed
reserve.10.0.25.HD61CB.7z
SHA256: 85157f6f9f386c2d87235762862fbd5c6f844ab9f750fc5637b87a2fc0c25815
Instructions:
0. This script starts at the normal system screen.
1. Unzip.
2. If you're on windows, extract the contents of platform-tools_r29.0.5-windows.zip
into the root of the same folder. If you're on linux, adjust your $PATH variable in shell.
3. Run fix-reserve.sh or fix-reserve.bat for linux or windows respectively.
4. Follow the instructions in the prompt. (when it says 'when you're booted' that
means booted and unlocked (pin, pattern, whatever. userdata needs to be decrypted
at this point)).
5. It will reboot you. Magisk manager will still be installed but you will otherwise
not be rooted. The magisk_patched.img in this folder will root you permanently
if you would like.
Click to expand...
Click to collapse
Hope this helps! This has been tested to work on a device unlocked on 10.0.13,
and there is little reason to believe it won't work on others. Also, if you use the
msm tool for these devices, and wish to unlock and continue to get OTA updates,
you must use this package, as MSM relocks you, and will destroy reserve.img again.
Those of you who have used this, please keep an eye out for updates from TMO
and report back whether you were able to update.
Confirmed that it works with brand new OTAs. Several members of the TG group
took the update from 10.0.16 and 10.0.19 without issue after restoring reserve with
these packages.
Thanks for this. So just to be clear, I should be able to run the second part (fix reserve) only and this should put back the .img file so I could theoretically receive the OTA? Is the first part necessary at all? I am on 10.0.16 and would just like to receive the OTA directly. Of course, I would unroot first.
No, you need to do the whole thing.
js042507 said:
Thanks for this. So just to be clear, I should be able to run the second part (fix reserve) only and this should put back the .img file so I could theoretically receive the OTA? Is the first part necessary at all? I am on 10.0.16 and would just like to receive the OTA directly. Of course, I would unroot first.
Click to expand...
Click to collapse
The first part is necessary if you are on any other version than 10.0.19. You would need a reserve.img dumped from 10.0.16
to ota to 10.0.19, and since most people unlocked before 10.0.19 came out, we're not likely to get ahold of reserve.img for
those versions.
Does the first part perform a clean wipe or just force the OTA to apply even with the file mismatch?
dstryrwiz said:
Does the first part perform a clean wipe or just force the OTA to apply even with the file mismatch?
Click to expand...
Click to collapse
First part does not wipe at all, just an overwrite. It fastboot flashes all the non-device-specific partitions as dumped
from a phone which was updated from 10.0.13 to 10.0.19, so after the first bit, and then restoring the reserve.img, your
phone should in theory be exactly how it would be if you hadn't unlocked, except its unlocked. Confused yet?
ntzrmtthihu777 said:
First part does not wipe at all, just an overwrite. It fastboot flashes all the non-device-specific partitions as dumped
from a phone which was updated from 10.0.13 to 10.0.19, so after the first bit, and then restoring the reserve.img, your
phone should in theory be exactly how it would be if you hadn't unlocked, except its unlocked. Confused yet?
Click to expand...
Click to collapse
Understood. Just to be clear though, this overwrite doesn't result in a replacement of the data partition with a blank partition, correct?
I understand that it's technically not a wipe, but I just want to be certain by doing this process that I won't end up losing all my files and need to restore all my apps again. If I need to, it's fine, just want to know that will happen before I do this process if it will.
dstryrwiz said:
Understood. Just to be clear though, this overwrite doesn't result in a replacement of the data partition with a blank partition, correct?
I understand that it's technically not a wipe, but I just want to be certain by doing this process that I won't end up losing all my files and need to restore all my apps again. If I need to, it's fine, just want to know that will happen before I do this process if it will.
Click to expand...
Click to collapse
Well, standard disclaimers apply for any sort of flash operation on your phone, but no, it should
not delete anything in userdata. The first script pack should not touch it at all, and the second one
doesn't do anything other than push a file and correct permissions and selinux context.
excellent. thanks
Everything worked for me. Also looks like the Magisk patch works as well. So far no issues. Hopefully this will work with the next OTA update.
Very nice! I will probably take a shot of rooting my phone next weekend. Just got done setting my replacement phone up, and not in a rush during the week to do it again.
Update worked perfectly for me. Thanks for this!
directions are very unclear in batch for update part, says it was finished with the Super (after parsing all 12 parts) and then nothing and now when i closed out to try to do the reserve to the boot loader im getting into qualcoms crashdump mode and its saying corrupted force dump kernel_restart. Please advise.
Keepinitgreen said:
directions are very unclear in batch for update part, says it was finished with the Super (after parsing all 12 parts) and then nothing and now when i closed out to try to do the reserve to the boot loader im getting into qualcoms crashdump mode and its saying corrupted force dump kernel_restart. Please advise.
Click to expand...
Click to collapse
No, it was 'finished' with super. there are more images after that.
Can you get into either fastboot or fastbootd mode?
ntzrmtthihu777 said:
No, it was 'finished' with super. there are more images after that.
Can you get into either fastboot or fastbootd mode?
Click to expand...
Click to collapse
My apologies brother, did not realized there were more to flash. Just completed part one now to do the reserve.
Keepinitgreen said:
My apologies brother, did not realized there were more to flash. Just completed part one now to do the reserve.
Click to expand...
Click to collapse
It happens. I amended the first post to say it would reboot on its own, I thought I had,
but it was only on the second part.
ntzrmtthihu777 said:
It happens. I amended the first post to say it would reboot on its own, I thought I had,
but it was only on the second part.
Click to expand...
Click to collapse
All good man! Appreciate this dope workaround. I have intermediate experience with terminal so it's a lot of guess work haha
ntzrmtthihu777 said:
The first part is necessary if you are on any other version than 10.0.19. You would need a reserve.img dumped from 10.0.16
to ota to 10.0.19, and since most people unlocked before 10.0.19 came out, we're not likely to get ahold of reserve.img for
those versions.
Click to expand...
Click to collapse
Is this still the case? And if so, would it be useful to have access to somebody with a locked HD1925 running 10.0.16?
@ntzrmtthihu777 , I wonder how hard it would be to modify all future snatched OTAs to completely ignore reserve.img? I did see one line in the last one mentioning a specific reserve size.
jhofseth said:
@ntzrmtthihu777 , I wonder how hard it would be to modify all future snatched OTAs to completely ignore reserve.img? I did see one line in the last one mentioning a specific reserve size.
Click to expand...
Click to collapse
You would need root at a minimum, and likely a functional TWRP as well. Once you modify the OTA, it will fail the signature check.
Long story short, I flashed my patched boot image without backing up, so I can’t restore via magisk. THEN I flashed a custom kernel. I have absolutely no way to OTA to January, nor do I even have a computer for awhile. I tried flashing the boot image via EX Kernel app but it doesn’t stick. Probably because of the modified files of the custom kernel.
So, does ANYBODY have A1 (global) kernel, that can be flashed via EX, or any other app?? I’m sure vbmeta might need to be included too. I’m desperate, and yes, it was a rookie mistake on my part. I always get Status error 1 when I try applying update via stock recovery (via sdcard option). OTA is completely broken and just refuses to do anything.
Thank you, in advance!!
draymond1987 said:
Long story short, I flashed my patched boot image without backing up, so I can’t restore via magisk. THEN I flashed a custom kernel. I have absolutely no way to OTA to January, nor do I even have a computer for awhile. I tried flashing the boot image via EX Kernel app but it doesn’t stick. Probably because of the modified files of the custom kernel.
So, does ANYBODY have A1 (global) kernel, that can be flashed via EX, or any other app?? I’m sure vbmeta might need to be included too. I’m desperate, and yes, it was a rookie mistake on my part. I always get Status error 1 when I try applying update via stock recovery (via sdcard option). OTA is completely broken and just refuses to do anything.
Thank you, in advance!!
Click to expand...
Click to collapse
Why don't you use fastboot environment and flash the January factory image without wiping data and then restore root by flashing the new patched boot image from the January update?
phaino00 said:
Why don't you use fastboot environment and flash the January factory image without wiping data and then restore root by flashing the new patched boot image from the January update?
Click to expand...
Click to collapse
I don’t have a computer at all, at least for a little while. I’m away from home, and I don’t have access to somebody else’s PC, either :/
draymond1987 said:
I don’t have a computer at all, at least for a little while. I’m away from home, and I don’t have access to somebody else’s PC, either :/
Click to expand...
Click to collapse
That answers my question. Sorry, I don't have a copy of that build. Just realized you wrote 'nor do I even have a computer...'
phaino00 said:
That answers my question. Sorry, I don't have a copy of that build. Just realized you wrote 'nor do I even have a computer...'
Click to expand...
Click to collapse
I’ll have to edit that part then
draymond1987 said:
Long story short, I flashed my patched boot image without backing up, so I can’t restore via magisk. THEN I flashed a custom kernel. I have absolutely no way to OTA to January, nor do I even have a computer for awhile. I tried flashing the boot image via EX Kernel app but it doesn’t stick. Probably because of the modified files of the custom kernel.
So, does ANYBODY have A1 (global) kernel, that can be flashed via EX, or any other app?? I’m sure vbmeta might need to be included too. I’m desperate, and yes, it was a rookie mistake on my part. I always get Status error 1 when I try applying update via stock recovery (via sdcard option). OTA is completely broken and just refuses to do anything.
Thank you, in advance!!
Click to expand...
Click to collapse
Here you go this is from the December A1 Firmware image. enjoy
LeoD said:
Here you go this is from the December A1 Firmware image. enjoy
Click to expand...
Click to collapse
Is there a way I can make a zip, to flash via EX’s app?
You’re a live saver, so far!
Why don't you wait until you get a PC.
If you keep fooling around. You will have no PC and no P6.
Too risky!
vandyman said:
Why don't you wait until you get a PC.
If you keep fooling around. You will have no PC and no P6.
Too risky!
Click to expand...
Click to collapse
You make a really decent point. Guess I’m just antsy to have all the fixes and not be on a buggy firmware.
The tools in This thread may help.
I've lost root on my Pixel 6. Been rooted since I got it, I update every month then root it. On July 22 update, rooted fine.. I think yesterday I just lost root out of nowhere. I've been sideloading OTAs and fastboot flashing Magisk patched boot image, no issues until suddenly losing it. Any ideas why?
Having root alone voids the warranty on most devices. I'd say somewhere in your venture of installing and changing things you messed something up, triggered an error of some kind.
Serpent.king said:
Having root alone voids the warranty on most devices. I'd say somewhere in your venture of installing and changing things you messed something up, triggered an error of some kind.
Click to expand...
Click to collapse
I haven't installed or changed anything in a few months besides updates...
pbsavages said:
I haven't installed or changed anything in a few months besides updates...
Click to expand...
Click to collapse
If your device isn't crashing or anything else I wouldn't worry Abt the root. I'm guessing the updates have something to do with it. Most operating systems will have auto triggers that stop or disable certain things
pbsavages said:
I've lost root on my Pixel 6. Been rooted since I got it, I update every month then root it. On July 22 update, rooted fine.. I think yesterday I just lost root out of nowhere. I've been sideloading OTAs and fastboot flashing Magisk patched boot image, no issues until suddenly losing it. Any ideas why?
Click to expand...
Click to collapse
Not sure why you lost it but do you continue to lose it after flashing the patched image again? On the latest Magisk I take it?
Since your rank is senior member imma ask where do I start a thread I got a problem with this stupid tablet i need solved
Lughnasadh said:
Not sure why you lost it but do you continue to lose it after flashing the patched image again? On the latest Magisk I take it?
Click to expand...
Click to collapse
Yeah, latest Magisk is what I patched it with for the July update. I'm at work but I'll flash the patched boot image when I get home. This hasn't happened before, just wanted to see if it's happened to anyone else.
Serpent.king said:
Since your rank is senior member imma ask where do I start a thread I got a problem with this stupid tablet i need solved
Click to expand...
Click to collapse
Go to the device's forum, click on "Post Thread" at the top and choose the appropriate section (e.g. General, Question, etc...).
pbsavages said:
I've lost root on my Pixel 6. Been rooted since I got it, I update every month then root it. On July 22 update, rooted fine.. I think yesterday I just lost root out of nowhere. I've been sideloading OTAs and fastboot flashing Magisk patched boot image, no issues until suddenly losing it. Any ideas why?
Click to expand...
Click to collapse
I'm in exactly the same situation. I updated, patched boot.img with latest Magisk (25200) and flashed -> had root. Then I lost it I think after the first restart.
I'm not sure but I'm suspicious that I forgot to open Magisk and do install -> direct install to have permanent root. Maybe that's your case as well?
I just flashed a patched boot.img, tried to restart a few times and so far so good, root stays. Let's see if that works long term.
mic3r said:
I'm in exactly the same situation. I updated, patched boot.img with latest Magisk (25200) and flashed -> had root. Then I lost it I think after the first restart.
I'm not sure but I'm suspicious that I forgot to open Magisk and do install -> direct install to have permanent root. Maybe that's your case as well?
I just flashed a patched boot.img, tried to restart a few times and so far so good, root stays. Let's see if that works long term.
Click to expand...
Click to collapse
Nope, I've had it direct installed for almost a whole month
mic3r said:
I'm not sure but I'm suspicious that I forgot to open Magisk and do install -> direct install to have permanent root. Maybe that's your case as well?
Click to expand...
Click to collapse
You don't need to use direct install to have permanent root. That option is there for when you are already rooted and want to update Magisk itself via direct install instead of patching the boot image again, or if you fastboot boot rather than fastboot flash the patched image.
If you just fastboot booted the patched image rather than fastboot flashed it, then you will only have temporary root until you do a direct install or fastboot flash the patched image.
Serpent.king said:
Having root alone voids the warranty on most devices. I'd say somewhere in your venture of installing and changing things you messed something up, triggered an error of some kind.
Click to expand...
Click to collapse
No. Does not void warranty. Do not spread crap like this.
I've seen it get pissed off with the contents of the boot partition and "revert" it and/or somehow swap boot_b into boot_a. After this happened a few times, I just make sure to write the patched boot.img to BOTH boot_a and boot_b and haven't had it happen since.
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
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.