Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Glendog1 said:
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Click to expand...
Click to collapse
Clean Flash:
1) Latest Official TWRP (Can be done from within old TWRP)
2) Reboot Recovery to new TWRP
3) Wipe
4) Latest Firmware (OB29)
5) ROM
6) OpenGapps Arm64 8.1 Nano or Pico
7) Root Optional
Don't forget to Nandroid first, and it might be a good idea to remove any security measures on your current setup too. (Fingerprint/Pin/Pattern)
Queue up the zips for Firmware/ROM/Gapps and flash in that order together.
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Glendog1 said:
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Click to expand...
Click to collapse
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
DirkGently said:
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
Click to expand...
Click to collapse
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Glendog1 said:
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Click to expand...
Click to collapse
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
DirkGently said:
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
Click to expand...
Click to collapse
Pin/password and fingerprints are two different things. Fingerprints are just a convenient method of authenticating. Removing them does nothing for the actual security with is pin/password.
The reason for removing the lock screen password before taking a backup is that if you install a new ROM and set a password and then restore your older backup, you can't get past the lock screen password. So, remove the password before taking the backup and then you can restore it later and set a new password.
I find the better option is to not remove the password and then, if you need to restore the backup after having changed passwords, you can delete the passwords of the restored backup in TWRP from Advanced>Terminal with these commands:
Code:
cd /data/system
rm -f gatekeeper.* locksettings.*
Changing the pin/password to none doesn't wipe out the on-boot password. However, when setting up a new password and selecting to not set an on-boot password will remove the current on-boot password for some users, but not for others (it doesn't for me).
Sent from my OnePlus 3T using XDA Labs
Thanks guys.
I followed your instructions @DirkGently and it worked a charm.
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Thanks,
Glendog1 said:
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Click to expand...
Click to collapse
Magisk
Glendog1 said:
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Click to expand...
Click to collapse
Yes and yes, but firmware may be tricky and messing up too much may render phone unusable. Messing with ROMs is fine though.
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Glendog1 said:
I have already installed a custom rom, will this be an issue?
Click to expand...
Click to collapse
That's ok of you asking questions, that's what this forum is about.
You should have got no problems if you're running a kernel shipped with custom ROM. Custom kernel is like EX, Mady's Xtended, Franco and so on.
Glendog1 said:
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Click to expand...
Click to collapse
You don't need to worry about Kernel stuff. RR already includes Caesium Kernel. You chose a good ROM by the way!
Here's a little information about Firmware. The OP3 and OP3T have unified builds. This means that in some cases the same Custom ROM can be used on both. There is some device specific software though so this has to be separated out and treated as independent from the ROM. This is what we refer to as Firmware. When Oneplus release new builds they include the updated Firmware in their Official ROM. If you look at the Firmware thread i linked you to, you'll see that kamilmirza takes the Firmware from the Official OOS builds and makes them available as flashable .zip files that we can use on Custom ROMs. Bookmark his Thread for future use.
There is no need to stress about always being on the latest Firmware for your Custom ROM, just ensure it is the Firmware intended for your device. The version you flashed earlier will probably do you for a while. At the same time, if you do always want to be on the latest, there's no reason not to. There's little to be gained by it though. If you're following the RR thread you'll probably see people mention it when the ROM requires a new Firmware. Again, don't stress about it.
As far as flashing Firmware, you can do it any time. You can do it before flashing an updated build of your ROM, or on it's own in a separate visit to Recovery. It's not particular either way. I would stick with the Open Beta Firmware, which people usually abbreviate to OBXX, i.e OB29. Just remember what you flashed so that you know which version you are using.
Now that you're rocking your Custom ROM you're next questions will be about updating it. This can be done easily and safely by Dirty Flashing. I've done dozens of updated builds since my last clean flash and everything has gone perfectly every single time.
Dirty Flash:
1) Download new ROM build (and Firmware if applicable) to Internal Storage.
2) Boot into Recovery
3) Nandroid Backup
4) From Install Menu, flash Firmware (if applicable), and ROM.
5) Wipe Dalvik & Cache when prompted. (BillGoss will tell you it's not necessary. It doesn't hurt either way, so up to you!)
6) Reboot phone.
For a Dirty Flash, you do not need to use the 'Wipe' Menu at all.
I always take a new Nandroid before flashing an updated build. I will have had a whole week on the previous build so i know i'm not backing up a bug and the backup will be as recent as possible if a problem occurs. Once i boot back into the phone i delete the old Backup. The new one is there if i need it. Always have that one recent Backup, just in case. As i've said, RR is great and i'm yet to run into a problem with it. From now on you can Dirty Flash the updated weekly builds with little to worry about and with a Backup to fall back to if anything goes wrong.
I don't mention Magisk because i don't use it, and i don't advise others use it. Unless you need Root access for something specific, don't bother. Half the threads on XDA are about problems with Magisk. Avoid the added complication if you can. Now this statement will trigger the Magisk fans, but nobody has ever had a bug or failure with something that they did not flash in the first place. Keep it as simple as possible.
Related
I have quite an old version of Android on my Nexus 6 (see attached). Is it safe to flash or fastboot to a 7.0 or 7.1 build without wiping? I am on rooted Project Fi. I don't necessarily need to keep root (though I prefer it for tap-to-wake), but I do need Project Fi compatibility since that is my carrier. Thank you!
You are going to have to wipe data and cache, flash bootloader and radio, and then you are clear to go to 7.0 or 7.1! *project FI is not a custom rom thing, its going to work now with any rom! Root is as easy is reflashing SU when done with upgrade, if you want root again.
While you probably can receive OTA updates until you get to Android 7.0, there's no guarantee that you'll get the required updates. Flashing one of the OTA images from the Google Developer website will get you there a lot quicker. But you want to back up your internal storage onto your PC before applying the OTA. Since there is a bootloader update involved, your device may end up wiped.
Darn. Can you link me to whichever bootloader, radio, and build would be best for me to use? I just want the base stock Project Fi build, so I'm not sure if I should get the Google build, or one in the dev forum.
I cannot utilize OTA updates: I click install, it reboots, and fails. Hence why I have been on 5.1 for years. I just haven't had the time (or desire) to do all of this manually. How should I go about the upgrade process? I understand the process of fastboot and all that (though it has been a while), but I need a little guidance on which file (or files) to use and where to download them. Any pointers on which website and which download(s) would be much appreciated, whether it is the official google file, or I need other files as well, etc.
This is a link to the 7.0 bootloader and radio, both flashable! http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
This is a link to a stock (project fi ready) 7.0 build, with radio / bootloader/ rom / gapps / everything. Perhaps it would be easier just to do this writeup! http://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
Excellent thank you. Regarding the second link:
a) This will work for 5.1 and a very old version of TWRP correct?
b) Also, what is the purpose of making a backup if this will wipe the storage anyway?
Of course it fails. OTA updates require the stock recovery to work. Had I known you had TWRP installed I would have had you flashing the factory image using fastboot.
a) no, while it may work, You should definitely update your version of TWRP
b) You aren't going to wipe your internal storage if you use TWRP. that's only when you're flashing via fastboot
If you use TWRP, you can wipe the system, data, and cache without touching your files. just dont' wipe internal storage
Yes. I do have TWRP. In that case, do you agree with the other post that the following link is the best upgrade path? http://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
Ohhh I see. My eyes immediately skipped to the "Method 2" content.
a) So I should first update TWRP, and then perform "Method 1" in that post, correct? Just want to make absolutely sure of the steps.
b) In the case that Method 1 is correct, since my data would remain, will my phone be wiped or not?
Yes.
It worked! I am now proudly on 7.0 without wiping!!! Thank you!!!!!! How do I mark this as the answer? Woohoo!!!
P.S. In case this should help anyone else (or maybe help myself in the future), I updated TWRP though the "TWRP Manager" app, did a full backup of the phone (took 822 seconds), then flashed that zip in that other thread. So far so good!!!
Woot!
Hi There,
I've the Problem that I havent't TWRP-Recovery and SuperSu after Updating to OOS 4.1.1 and Android 7.1.1.
Do someone know if i had to flash TWRP with qiping all Data? Or is there a Way to Flash TWRP and SuperSu without wiping? =(
Sorry I'm new to Android and started with the oneplus 3t. So i didn't know that i hadn't to update the Phone.
Or is the best opinion for me to choose a custom rom? But there are so much, i don't know what to choose.
Thanks for help! =)
Neither TWRP nor SuperSU will wipe anything.
It's totally up to you whether you need a custom ROM or not. If you want features like switching tracks just with your volume keys, you'll totally need a custom ROM since stock ones don't provide this feature. But this is just one example of many.
Regards.
Sent from my OnePlus 3T using Tapatalk
Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
I'll try my best today evening, hopefully nothing will go wrong :-O
What do I need to center the clock?
I'll flash trwp and supersu and anything to center the clock today evening.
Don't know if I need a custom rom, are there reason for a custom rom?
Thank you so much!
m4l4g4 said:
Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
I'll try my best today evening, hopefully nothing will go wrong :-O
What do I need to center the clock?
I'll flash trwp and supersu and anything to center the clock today evening.
Don't know if I need a custom rom, are there reason for a custom rom?
Thank you so much!
Click to expand...
Click to collapse
If you need help with anything, just ask.
I never had to wipe anything. I just wipe the phone when I want to remove the encryption.
EDIT: regular security patches is one big reason for me to install a custom ROM.
Thanks, I'll ask my questions
But why did the update delete trwp and supersu?
I was happy with OOS but missed the future of centering the clock.
May I ask which custom rom you use?
Updates remove SuperSU because they essentially flash over all non-user partitions (everything except /data, where your files, settings and user apps are stored). To root the OS, SuperSU installs its files in the /boot partition, which gets overwritten during ROM flashes. Root gets deleted any time you flash any mod (including most custom ROMs, since they also replace /boot). The only exception to this is if you flash a custom ROM that comes pre-rooted.
TWRP does not get deleted immediately during flashing, but rather when you first boot up afterwards. OOS will attempt to replace any custom recovery with the stock recovery when it first boots up after updating. You can get around this by either flashing TWRP again, or rooting immediately after flashing a ROM update, before you reboot (flash ROM, wipe cache/delvik, flash root, reboot). Most custom ROMs will not replace your custom recovery.
There's a few threads containing OPSystemUI.apk mods in the Themes, Apps and Mod section, though most of them also contain a bunch of other graphical modifications. If you only want to center your clock and nothing else, it can be achieved by modding OPSystemUI.apk yourself, though there is a bit of a learning curve to it.
m4l4g4 said:
Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
Click to expand...
Click to collapse
You are mixing things up a bit but don't worry, I'll explain.
You need to unlock the bootloader first, and that always wipes your data for security reasons. So if your phone is stolen, the thief won't be able to access your data by installing TWRP or a custom rom. After unlocking you install TWRP (custom recovery), and use it to flash stuff. (roms, mods, etc)
After that you only lose data if you (or a rom) mess things up, and your data becomes unaccessible, or you relock your bootloader for whatever reason. That's why you should always backup to a computer before doing major flashing/upgrades, etc.
If you upgrade the rom you'll lose root and/or TWRP, but you can flash it again as explained by others.
Hi there,
so I've flashed TWRP and SuperSu again. You are all right, i haven't to wipe anything. I really mixed up things. But now everything is working for me.
Okay, i have to learn how to get my OPSystemUI.apk modify it and flash it back?
I will seach the threads and learn.
Hello all,
I bought recently a used mi8 for replacing my oldie mi5.
I have reading several posts that are related with flashing the roms, and several talk about the encryption storage.
I know that xiaomi encrypts the storage and that I need to format, but I get confused with the necessity of having to flash or not the dm-verity pack.
So what I know so far and please correct me if I'm wrong:
First boot loader unlock no problem
Second install Twrp, can I use the latest official or search for a specific package????
Third in the Twrp format everything
Fourth after format I remember something about keeping system read only or not, what do I need to do???
Fifth grab an asop rom and flash it
Sixth if I want root, use the Magisk, normally or do I need to pay attention to anything else.
Sorry, for so many things, but I read plenty, before asking
robrodrigues said:
Hello all,
I bought recently a used mi8 for replacing my oldie mi5.
I have reading several posts that are related with flashing the roms, and several talk about the encryption storage.
I know that xiaomi encrypts the storage and that I need to format, but I get confused with the necessity of having to flash or not the dm-verity pack.
So what I know so far and please correct me if I'm wrong:
First boot loader unlock no problem
Second install Twrp, can I use the latest official or search for a specific package????
Third in the Twrp format everything
Fourth after format I remember something about keeping system read only or not, what do I need to do???
Fifth grab an asop rom and flash it
Sixth if I want root, use the Magisk, normally or do I need to pay attention to anything else.
Sorry, for so many things, but I read plenty, before asking
Click to expand...
Click to collapse
Well come to Mi8 mate.
1. You need to unlock bootloader
2. Install official or IMO use Orangefox recovery which is based on latest twrp with some themes and extras.
3. You are right
4. After installing twrp or similar you need to slide on first run if you want to enable flashing etc.
5. Choose any rom you want
6. Yes Magisk is your only option, if you need root.
However if your device is unencrypted than you don't need to install dmverity. I am also used many AOSP roms on my unencrypted device and faced zero issues.
[emoji3590] from [emoji1191]
ammaralidj said:
Well come to Mi8 mate.
1. You need to unlock bootloader
2. Install official or IMO use Orangefox recovery which is based on latest twrp with some themes and extras.
3. You are right
4. After installing twrp or similar you need to slide on first run if you want to enable flashing etc.
5. Choose any rom you want
6. Yes Magisk is your only option, if you need root.
However if your device is unencrypted than you don't need to install dmverity. I am also used many AOSP roms on my unencrypted device and faced zero issues.
[emoji3590] from [emoji1191]
Click to expand...
Click to collapse
Hello all
Well I repeated the same steps once again and voila it worked.
Bootloader unlocked successfully and my Mi8 is with Asop pixel experience.
Thanks once again
Hi everyone! I'm very much a newbie when it comes to custom ROM's, so apologies if this is a a dumb question...
I just managed to install the latest Pixel Experience ROM on my K20 Pro, from the stock Chinese ROM. Before installing it, I had to flash DFE. So, from my understanding, it is now blocking me from re-enabling encryption. I need to have encryption enabled for work email access, so is it possible to enable it somehow? I'm not worried about losing any data on the phone, but I would certainly prefer to use Pixel Experience than to go back to MIUI.
Per another forum thread I found, one member suggested to "reflash your vendor/firmware." Is that accurate? If so, how do I do that, and what would be the result?
shleepy said:
Hi everyone! I'm very much a newbie when it comes to custom ROM's, so apologies if this is a a dumb question...
I just managed to install the latest Pixel Experience ROM on my K20 Pro, from the stock Chinese ROM. Before installing it, I had to flash DFE. So, from my understanding, it is now blocking me from re-enabling encryption. I need to have encryption enabled for work email access, so is it possible to enable it somehow? I'm not worried about losing any data on the phone, but I would certainly prefer to use Pixel Experience than to go back to MIUI.
Per another forum thread I found, one member suggested to "reflash your vendor/firmware." Is that accurate? If so, how do I do that, and what would be the result?
Click to expand...
Click to collapse
Why did you have to flash DFE? It's only used if you change roms frequently to avoid encryption.
I initially had trouble successfully installing the ROM. So, I started from scratch and followed some thorough instructions I found online, which included the DFE step. (I noticed that TWRP was previously showing an encryption error at the start of ROM installation; but I guess it could just be a "warning" more than an error. I suspect my problem before was probably more related to not having the latest MIUI update installed, or something like that.)
I don't plan on frequently swapping ROM's.
shleepy said:
I initially had trouble successfully installing the ROM. So, I started from scratch and followed some thorough instructions I found online, which included the DFE step. (I noticed that TWRP was previously showing an encryption error at the start of ROM installation; but I guess it could just be a "warning" more than an error. I suspect my problem before was probably more related to not having the latest MIUI update installed, or something like that.)
I don't plan on frequently swapping ROM's.
Click to expand...
Click to collapse
Your best bet is to go back to stock and start again. I believe installing an official fastboot ROM will restore encryption. Your previous issues were probably caused by not formatting data when flashing PE.
There is no requirement to disable encryption on this phone, ignore any guide that adds that as a step. You should only disable encryption if it's your personal preference to disable it.
Follow this guide.
Flash the latest Chinese 11.0.5 fastboot ROM. Make sure you don't lock the bootloader if using the Mi Flash Tool.
Boot into MIUI once to allow it to finalise the install, you don't need to do the initial phone setup once it boots into MIUI.
Boot into fastboot and install TWRP. I recommend the latest from mauronofrio which should be 3.1.1-32
Boot immediately into TWRP. I use the volume up button while powering up the phone.
Perform a factory reset in TWRP (using the swipe button), then format data (need to type 'yes' to confirm).
Reboot into TWRP using the TWRP boot menu, this ensures the newly formatted data partition is correctly mounted.
Copy over the PE ROM, then flash.
Boot into your new ROM, everything should be OK. Then boot back into TWRP to install Magisk if you want root.
shleepy said:
I initially had trouble successfully installing the ROM. So, I started from scratch and followed some thorough instructions I found online, which included the DFE step. (I noticed that TWRP was previously showing an encryption error at the start of ROM installation; but I guess it could just be a "warning" more than an error. I suspect my problem before was probably more related to not having the latest MIUI update installed, or something like that.)
I don't plan on frequently swapping ROM's.
Click to expand...
Click to collapse
Do yourself a favour and follow the instructions in the description of the rom, not some instructions you found online telling you to do some unnecessary stuff. Going to and from miui, format data, everything else just wipe cache, system and data to avoid issues, even then you can get away with dirty flashing aosp based roms 99% of the time imo.
As for the miui update, I have no idea how you came to that conclusion but just no, that's not how it works at all. Vendor firmware and the rom is all you need for pixel experience at the bare minimum.
You can try flashing the rom again, but don't flash the DFE.
Hi all. Been a long time. Hope I can get some guidance here.
As always, I've been doing my research and testing, but I haven't got it quite right yet. Here is my issue:
I'm able to flash TWRP, but upon reboot, it reverts back to the stock Android recovery. Found out that its a security feature and you need to disable it. Is this where dm-verity comes into play? Do I need to flash a zip file in TWRP after flashing it, or flash something via ODIN in order to disable this security feature? Also, I've read that after flashing TWRP (and after removing dm-verity or before?), you need to format (not wipe) the /system and/or /data partitions in order to remove the encryption.
I'm a little confused as to the proper sequence of steps in order to accomplish this. I've read some guides here on XDA, but I'm still not getting it regarding after flashing TWRP. Or am I not supposed to flash TWRP first?
I know a little bit about Linux but I am by no means an expert.
My phone is the Note 9 N9600, dual sim, 128GB. Its running stock Samsung Android 10 (OneUI 2.1), Baseband version N9600ZHU4ETG1, Build number QP1A.190711.020.N9600ZHU4ETG1.
I also remember that in some situations, it may be necessary to downgrade the installed ROM in order to properly flash. Hope thats not the case here.
I will continue to search, but any advise would be greatly appreciated. Here is the guide that I've been using as a point of reference: https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-note9-snapdragon-t3845536
Thanks
Talabis said:
Hi all. Been a long time. Hope I can get some guidance here.
As always, I've been doing my research and testing, but I haven't got it quite right yet. Here is my issue:
I'm able to flash TWRP, but upon reboot, it reverts back to the stock Android recovery. Found out that its a security feature and you need to disable it. Is this where dm-verity comes into play? Do I need to flash a zip file in TWRP after flashing it, or flash something via ODIN in order to disable this security feature? Also, I've read that after flashing TWRP (and after removing dm-verity or before?), you need to format (not wipe) the /system and/or /data partitions in order to remove the encryption.
I'm a little confused as to the proper sequence of steps in order to accomplish this. I've read some guides here on XDA, but I'm still not getting it regarding after flashing TWRP. Or am I not supposed to flash TWRP first?
I know a little bit about Linux but I am by no means an expert.
My phone is the Note 9 N9600, dual sim, 128GB. Its running stock Samsung Android 10 (OneUI 2.1), Baseband version N9600ZHU4ETG1, Build number QP1A.190711.020.N9600ZHU4ETG1.
I also remember that in some situations, it may be necessary to downgrade the installed ROM in order to properly flash. Hope thats not the case here.
I will continue to search, but any advise would be greatly appreciated. Here is the guide that I've been using as a point of reference: https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-note9-snapdragon-t3845536
Thanks
Click to expand...
Click to collapse
once you boot into twrp then flash the 1st kernel 2nd magisk
Then follow this here flash 3rd multidisabler.zip and 4th forceencrypt_disabler_q.zip for Android 10 and format data.
The links are on the same guide