Database Develop

I Deleted the OS of my Note 9 using TWRP and now it is in a constent bootloop, Help!

So I wanted to "ROOT" my Note 9 "N960F" Model just to overclock the "CPU" and do some fun stuff, for about a month I was studing the ways of opening the Bootloader and Rooting but then I finally did it! Hurray!
One Month later I felt like it was making my Note 9 slower, probably placiboo but I wanted to go back to making it normal again
So I logged in to the Recovery Mode on the "TWRP" Software and by mistake deleted the OS from the phone, it is now impossible to enter the phone, I've tried the most tips and tricks form the web and nothing seems to work. Any solutions?

Always make sure to post asking questions, help and support in device specific Q&A Forum ( when exists) and otherwise General Q&A Forum.
Thanks.

All you have to do is flash the current version again. For example, I did the same thing on my Xiaomi Mi Mix 3. All I had to do was flash the correct .zip for the latest version (doesn't have to be latest, could be older).

Redmi note 9 twrp recovery????

Anybody have twrp recovery for redmi note 9 ????

Mbilalkhaan said:
Ksi k pass redmi note 9 ki twrp recovery ha ????
Click to expand...
Click to collapse
Guessing you're asking if there's a custom recovery available for the RN9. Not yet, so far as I know
I've found the stock firmware pretty solid so far - can't see me bothering too root this

@Mbilalkhaan I see that you're new here. Welcome to XDA Developers! I suggest you read the Forum Rules in complete before posting from now on. Please note that as per the forum rules, only English is allowed:
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Click to expand...
Click to collapse
Request you to please keep this in mind while posting going forward.
Have a nice day!
Regards,
shadowstep
Forum Moderator

interested too in a twrp for RN9 for magisk and stereo mod

Probably gonna be a while. The forum for this phone just opened a couple days ago , plus it has a mediateck processor so gonna be a while

Unofficial twrp?
Has anyone tried this Unofficial TWRP 3.4.1 for Redmi Note 9/Merlin_Global?
unofficialtwrp.com /twrp-3-4-1-root-redmi-note-9/
just remove the space before the forward slash

i must wait 166 hours to unlock my bootloader...after that i will try it. thanks

danger2u said:
i must wait 166 hours to unlock my bootloader...after that i will try it. thanks
Click to expand...
Click to collapse
May I ask, why do you need to wait 166 hours to unlock bootloader? I this about the apply thingy that you need to do before unlocking Xiaomi devices? Because I have read this article that stated "Before some years ago you need to apply and wait 1-15 days for permission! But, now Xiaomi changes its policy. Now you don't need to apply for unlocking your device.Oct 13, 2018"
c.mi.com /thread-1635834-1-1.html#:~:text=Before%20some%20years%20ago%20you,apply%20for%20unlocking%20your%20device.

danger2u said:
i must wait 166 hours to unlock my bootloader...after that i will try it. thanks
Click to expand...
Click to collapse
I see now. Mine's 168 hours. You just need to add your Mi account first then it will tell you to wait 168 hours on the Mi unlock tool. Thanks Mr. danger2u

tested the unofficialtwrp thing today. And now got me bootlooped. seems like the no-verity-opt-encrypt.zip is not working as expected. now im trying to restore the old state.... hope there will be a good way to root this cause i need adaway

Adguard is loads less trouble - fine without root

darthm0e said:
tested the unofficialtwrp thing today. And now got me bootlooped. seems like the no-verity-opt-encrypt.zip is not working as expected. now im trying to restore the old state.... hope there will be a good way to root this cause i need adaway
Click to expand...
Click to collapse
Thanks darthm0e! Hope you keep updating here on your findings BTW, how can we create a custom recovery? I want to know how to.

Adguard doesn't work for all my needs. and its more or less browser based. Anyway i need root for some other stuff too...so.
2nd try i used the Xiaomi Tool V2 (by Francesco Tescari). It loads also the same TWRP image and i also get stucked in the Bootloop.
on tradingshenzhen they explained more or less the same method then unofficialtwrp.com except they use the XiaomiTool V2
and the TWRP i found there is the same.
whats strange is that i only read about Codename Merlin for the Redmi Note 9, but mine reports hisself as MerlinNFC. maybe this is the thing or are they all equipt with NFC? I will try tomorrrow again.

darthm0e said:
Adguard doesn't work for all my needs. and its more or less browser based. Anyway i need root for some other stuff too...so.
2nd try i used the Xiaomi Tool V2 (by Francesco Tescari). It loads also the same TWRP image and i also get stucked in the Bootloop.
on tradingshenzhen they explained more or less the same method then unofficialtwrp.com except they use the XiaomiTool V2
and the TWRP i found there is the same.
whats strange is that i only read about Codename Merlin for the Redmi Note 9, but mine reports hisself as MerlinNFC. maybe this is the thing or are they all equipt with NFC? I will try tomorrrow again.
Click to expand...
Click to collapse
Note 9 phones with model number M2003J15SG have NFC
M2003J15SS don't
(Can check your model number in settings)

Redmi note 9 root
How root redmi note 9???? Any body know about redmi note 9 recovery?????? When recovery coming for redmi note 9??????

Hi guys,
New here and I got this phone a few weeks ago. I tried rooting it via Magisk both by flashing the zip on the unofficial TWRP and by patching the boot.img file, but both methods ended up in bootloop.
So I'd like to know if any of you have informations on this : has a consistent way of rooting this phone been found?
(My question may seem stupid since it only came out a month or so ago, but honestly I don't really have an idea how long it usually takes after a device's release for people to find a way to root it)
Thanks for your answers!

https://forum.xda-developers.com/re.../how-to-unlock-root-redmi-9-9s-9-pro-t4108913
This post worked for me as far as rooting goes.
I also managed to verify the SafetyNet test (with magisk spoofing modules + clearing Play Store/Services data), then installed edXposed just fine too.
But, then I installed some module that got me stuck in a bootloop and had to wipe and start over, and I couldn't pass the SafetyNet check anymore for some reason.
So I wiped again and keeping it unrooted for now, I'll wait for custom ROMs.

Akitake said:
https://forum.xda-developers.com/re.../how-to-unlock-root-redmi-9-9s-9-pro-t4108913
This post worked for me as far as rooting goes.
I also managed to verify the SafetyNet test (with magisk spoofing modules + clearing Play Store/Services data), then installed edXposed just fine too.
But, then I installed some module that got me stuck in a bootloop and had to wipe and start over, and I couldn't pass the SafetyNet check anymore for some reason.
So I wiped again and keeping it unrooted for now, I'll wait for custom ROMs.
Click to expand...
Click to collapse
Could u tell me please how did u install ? I flashed it in magisk but it shows me that it's not installed in the edxposed manager.

@Akitake: That's always nice to see that a particular rooting method of some related Redmi phone works on our Redmi Note 9. :good:
Now, you know for sure that the Redmi Note 9 has a MediaTek G85 processor and Xiaomi devices are notorious for getting very easily bricked. See for example the Custom Rom threads for Redmi Note 8. It is really spooky how some guys end up having their smartphone turn in to a Xiaomi service center - if there is such a center at all in their country. So what's paramount here for us Redmi Note 9 users is that we really, really make sure that we don't arrive at a hopeless situation! That's why I need to ask you some questions to make sure we all are on the same page.
1) What Note 9 do you have? Is it one with NFC or not? Mine, for example, is a M2003J15SG where G denotes the NFC variant.
2) What's the MIUI version you are running? Mine, for example, is 11.0.5.0 (QJOEUXM)
3) You unlocked your phone, right?
4) Did you use any particular tools like a particular fastboot version, for instance?
5) Which version of Magisk did you install?
6) Which version of edXposed did you install?
7) Which Magisk spoofing module did you install? Why that and not another one?
8) What do you mean with "clearing Play Store / services data". Do you mean all Google Play services data?
9) If you arrived at a bootloop, how did you wipe? Did you wipe data/cache/etc? Did you use fastboot or some LR-TWRP or MiFlash? Which version of the tool?
10) Once you reinstalled your original boot.img, did your phone start up normally or were there "hickups"?
Sorry for asking so many questions, but as I said, I want to make a 100% sure that everything goes well.
Thanks for your answers in advance!
Best whishes to you!
- dfahren
Akitake said:
https://forum.xda-developers.com/re.../how-to-unlock-root-redmi-9-9s-9-pro-t4108913
This post worked for me as far as rooting goes.
I also managed to verify the SafetyNet test (with magisk spoofing modules + clearing Play Store/Services data), then installed edXposed just fine too.
But, then I installed some module that got me stuck in a bootloop and had to wipe and start over, and I couldn't pass the SafetyNet check anymore for some reason.
So I wiped again and keeping it unrooted for now, I'll wait for custom ROMs.
Click to expand...
Click to collapse

dfahren said:
@Akitake: That's always nice to see that a particular rooting method of some related Redmi phone works on our Redmi Note 9. :good:
Now, you know for sure that the Redmi Note 9 has a MediaTek G85 processor and Xiaomi devices are notorious for getting very easily bricked. See for example the Custom Rom threads for Redmi Note 8. It is really spooky how some guys end up having their smartphone turn in to a Xiaomi service center - if there is such a center at all in their country. So what's paramount here for us Redmi Note 9 users is that we really, really make sure that we don't arrive at a hopeless situation! That's why I need to ask you some questions to make sure we all are on the same page.
1) What Note 9 do you have? Is it one with NFC or not? Mine, for example, is a M2003J15SG where G denotes the NFC variant.
2) What's the MIUI version you are running? Mine, for example, is 11.0.5.0 (QJOEUXM)
3) You unlocked your phone, right?
4) Did you use any particular tools like a particular fastboot version, for instance?
5) Which version of Magisk did you install?
6) Which version of edXposed did you install?
7) Which Magisk spoofing module did you install? Why that and not another one?
8) What do you mean with "clearing Play Store / services data". Do you mean all Google Play services data?
9) If you arrived at a bootloop, how did you wipe? Did you wipe data/cache/etc? Did you use fastboot or some LR-TWRP or MiFlash? Which version of the tool?
10) Once you reinstalled your original boot.img, did your phone start up normally or were there "hickups"?
Sorry for asking so many questions, but as I said, I want to make a 100% sure that everything goes well.
Thanks for your answers in advance!
Best whishes to you!
- dfahren
Click to expand...
Click to collapse
1) It's the lower end version, with 64GB internal storage, Redmi Note 9 (merlin)
2) Latest at time of writing, shouldn't matter but yes, 11.0.5.0, we're also going to get MIUI 12 soon-ish as it's already released in China.
3) Yes with miunlock (Official tool)
4) I just always use the ADB and Fastboot versions provided with MiUnlock (same folder, open CMD inside it then you can use adb and fastboot)
5) Latest? 20.4
6) I installed EdExposed manager from XDA Labs and simply installed it that way, so, latest
7) One of them is like Magisk Props something, the other is lib something which seemed to help for DRM content (netflix etc)
8) Once I installed the Magisk modules for spoofing, I restarted, then cleared the Google Play Store & Play Store services data (In Settings>Apps>Manage Data> Clear all Data), restarted again.
9) I didn't bootloop ever. And even if you do, it's to either use fastboot (power + vol down) and flash the official rom back with MiFlash.
10) Nah it was completely normal.
Links:
- Official Roms for Redmi note 9: https://c.mi.com/oc/miuidownload/detail?device=1900378
- Re-flash stock rom via recovery (power + vol up): https://c.mi.com/oc/miuidownload/detail?guide=1
- Re-flash stock rom via fastboot (power + vol down): https://c.mi.com/oc/miuidownload/detail?guide=2
Their links to roms in that guide are dead, you can get them here though: https://xiaomifirmwareupdater.com/miui/merlin/
Just make sure the ROM you download is of the right type (recovery for recovery method, fastboot for fastboot+miflash method) before downloading.

Problems & Solutions: Installing Lineage on a SM-T713, Samsung Galaxy Tab S2 8”

Problems & Solutions: Installing Lineage on a SM-T713, Samsung Galaxy Tab S2 8”
There are many sites offing Step-by-Step guides.
I used
https://wiki.lineageos.org/devices/gts28vewifi/install and/or
https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-16-0-t3903286
(SEE BELOW for what’s missing from the instructions)
I have a 2016 Samsung Galaxy Tab S2 8.0 that seemed to be on its last legs. After all, it is the 4th quarter of 2020 as I write this. The current version of Android is 10. This poor old, much loved, tablet runs either Android 5, 6 or 7. Ancient, right!
I upgraded to Lineage 16.0 (17.0 was still “unofficial” in late summer 2020) – Android 9. All I can say is WOW!! A whole new tablet, or at least that is the way it behaves.
The process took me two days. It should have been about 2 hours. I’m writing this to save others those 46 hours of frustration.
I absolutely hate it when those that create the “How to” guides assume …
Don’t get me wrong I greatly appreciate and respect the intent and effort involved. Heck I’m doing a “how to” myself right now! But skipping info because “everyone” knows or because of an “assumed configuration” is unfortunate and causes major frustrations for others.
So things that didn’t work for me installing Lineage 16.0 on my Samsung Galaxy Tab S2 , SM-T713 region XAR.
Things they DON’T tell you:
• Let us start right at the end of that last sentence “region XAR.”
Look at any list of regions Samsung Firmware is released for that you can find. Canada is listed, United Kingdom is listed. Is USA, United States, or America listed? Nope! Somehow we are supposed to know that “Cellular south” is the correct firmware to use?
• The Tab S2 needs to have the Android Nougat 7.0 firmware. That makes sense. But would you presume that the latest 2019 Samsung Update, T713XXS2BSG1_T713XAR2BSB1, would not work?
It turns out that the latest (as of this writing) Lineage, lineage-16.0-20200928-nightly-gts28vewifi, requires a SPECIFIC Samsung Firmware Update -> T713XXU2BRB2_T713XAR2BRB2, dated March of 2018.
Repeated Error 7 from TWRP: Unzip the Lineage file. Look in META-INF\com\google\android and open the updater-script with notepad (Notepad++ is even better) find the “Target:” statement. It will tell you which Samsung firmware update the Lineage was built for.​
• Odin won’t recognize the Tab S2:
and/or
Heimdall returns ERROR: “Failed to access device. libusb error: -12”:
Samsung firmware update requires Odin. Changing recovery to TWRP uses Heimdall. It appears these two Flash Softwares use different Windows 10 Drivers to communicate with the SM-T713
o After using Heimdall (and zadig-2.4.exe to install its drivers) you need to use SAMSUNG_USB_Driver_for_Mobile_Phones.exe to reinstall the Samsung Drivers if you want to use Odin3
o After using Odin3 and the required Samsung Drivers you need to use zadig-2.4.exe to reinstall the drivers used by Heimdall​
• Tab S2 stuck on Samsung at boot after Samsung firmware upgrade:
Use recovery or TWRP, either one, to Wipe the Cache Partition
NOTE: I didn’t fix this boot loop issue after Flashing T713XXU2BRB2 and TWRP installed lineage-16.0-20200928 just fine . And lineage booted up A-OK.
There are things I haven’t told you that aren’t in the instructions either:
When you boot into stock recovery you’ll get “no instruction” – just wait it out
Flashing Lineage from your MicroCD is much easier than “adb sideload”
Odin takes a long time to load the Samsung Firmware before you can proceed
If Odin3 fails or especially partially fails, just do it again from the beginning
Boot into Recovery – Home + Power + Volume Up works best
Download mode - Home + Power + Volume Up works best
If you screw something up and can’t shut down – Power + Volume Down
Then IMMEDIATELY at black screen Home + Power + Volume Up – you can power off from there
Before Lineage install in TWRP
Wipe – Format
Wipe – Advanced - Cache & System
(Some instructions wipe more, DON’T)
If the Lineage install fails, you’ll have no OS and will need to reinstall a Samsung Firmware via Odin3
And more I’m sure ​

bardell3600 said:
Problems & Solutions: Installing Lineage on a SM-T713, Samsung Galaxy Tab S2 8”
There are many sites offing Step-by-Step guides.
I used
https://wiki.lineageos.org/devices/gts28vewifi/install and/or
https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-16-0-t3903286
(SEE BELOW for what’s missing from the instructions)
I have a 2016 Samsung Galaxy Tab S2 8.0 that seemed to be on its last legs. After all, it is the 4th quarter of 2020 as I write this. The current version of Android is 10. This poor old, much loved, tablet runs either Android 5, 6 or 7. Ancient, right!
I upgraded to Lineage 16.0 (17.0 was still “unofficial” in late summer 2020) – Android 9. All I can say is WOW!! A whole new tablet, or at least that is the way it behaves.
The process took me two days. It should have been about 2 hours. I’m writing this to save others those 46 hours of frustration.
I absolutely hate it when those that create the “How to” guides assume …
Don’t get me wrong I greatly appreciate and respect the intent and effort involved. Heck I’m doing a “how to” myself right now! But skipping info because “everyone” knows or because of an “assumed configuration” is unfortunate and causes major frustrations for others.
So things that didn’t work for me installing Lineage 16.0 on my Samsung Galaxy Tab S2 , SM-T713 region XAR.
Things they DON’T tell you:
• Let us start right at the end of that last sentence “region XAR.”
Look at any list of regions Samsung Firmware is released for that you can find. Canada is listed, United Kingdom is listed. Is USA, United States, or America listed? Nope! Somehow we are supposed to know that “Cellular south” is the correct firmware to use?
• The Tab S2 needs to have the Android Nougat 7.0 firmware. That makes sense. But would you presume that the latest 2019 Samsung Update, T713XXS2BSG1_T713XAR2BSB1, would not work?
It turns out that the latest (as of this writing) Lineage, lineage-16.0-20200928-nightly-gts28vewifi, requires a SPECIFIC Samsung Firmware Update -> T713XXU2BRB2_T713XAR2BRB2, dated March of 2018.
Repeated Error 7 from TWRP: Unzip the Lineage file. Look in META-INF\com\google\android and open the updater-script with notepad (Notepad++ is even better) find the “Target:” statement. It will tell you which Samsung firmware update the Lineage was built for. ​
• Odin won’t recognize the Tab S2:
and/or
Heimdall returns ERROR: “Failed to access device. libusb error: -12”:
Samsung firmware update requires Odin. Changing recovery to TWRP uses Heimdall. It appears these two Flash Softwares use different Windows 10 Drivers to communicate with the SM-T713
o After using Heimdall (and zadig-2.4.exe to install its drivers) you need to use SAMSUNG_USB_Driver_for_Mobile_Phones.exe to reinstall the Samsung Drivers if you want to use Odin3​
o After using Odin3 and the required Samsung Drivers you need to use zadig-2.4.exe to reinstall the drivers used by Heimdall​
• Tab S2 stuck on Samsung at boot after Samsung firmware upgrade:
Use recovery or TWRP, either one, to Wipe the Cache Partition
NOTE: I didn’t fix this boot loop issue after Flashing T713XXU2BRB2 and TWRP installed lineage-16.0-20200928 just fine . And lineage booted up A-OK.
There are things I haven’t told you that aren’t in the instructions either:
When you boot into stock recovery you’ll get “no instruction” – just wait it out​
​
Flashing Lineage from your MicroCD is much easier than “adb sideload”​
​
Odin takes a long time to load the Samsung Firmware before you can proceed​
​
If Odin3 fails or especially partially fails, just do it again from the beginning​
​
Boot into Recovery – Home + Power + Volume Up works best​
​
Download mode - Home + Power + Volume Up works best​
​
If you screw something up and can’t shut down – Power + Volume Down​
Then IMMEDIATELY at black screen Home + Power + Volume Up – you can power off from there​
​
Before Lineage install in TWRP​
Wipe – Format​
Wipe – Advanced - Cache & System​
(Some instructions wipe more, DON’T)​
​
If the Lineage install fails, you’ll have no OS and will need to reinstall a Samsung Firmware via Odin3​
​
And more I’m sure ​
​
Click to expand...
Click to collapse
Thanks for this,
I am looking to breath some life into my wife's S2 8.0. Where did you get the March 18 firmware? I looked on Sam Mobile and I cannot download it as I am not a premium member. Her tablet is already on the July 2019 version which is what I downloaded this morning just to have on hand ( I am also in Canada)
**Update - I found a link to the firmware you mentioned and downloaded it**

Do you mind sharing the link to the download? thanx

RJC_68 said:
**Update - I found a link to the firmware you mentioned and downloaded it**
Click to expand...
Click to collapse
Hello there, do you mind sharing where you downloaded the right firmware?
Thanks a lot

pas7771 said:
Hello there, do you mind sharing where you downloaded the right firmware?
Thanks a lot
Click to expand...
Click to collapse
It may have been this site
Galaxy Firmware - Samsung Galaxy Tab S2 8.0 (SM-T713)
Samsung Galaxy Tab S2 8.0 Android tablet. Announced Jul 2015. Features 8.0″ Super AMOLED display, Exynos 5433 chipset, 8 MP primary camera, 2.1 MP front camera, 4000 mAh battery, 64 GB storage, 3 GB RAM.
galaxyfirmware.com
We have sold all our android devices and gone back to Apple so I cannot be 100% sure.
Hope this helps

Note 9 custom ROM beginner questions

Hi everyone
I have a Galaxy Note 9 and I would love to use Android 11 to make use of the new Ethernet tethering feature. I have decided to try to install a custom ROM allowing me to do this but I have never done this before, or even rooted my device. I have been doing lots of research over the past week and I think I'm almost ready, but I have a few questions that I would like to ask.
My setup:
I have a Note 9 exynos SM-N960F. It does not have the latest software version as I have an official update available, but I have OneUI2 which is a requirement for the custom ROM. I have enabled USB Debugging and disabled the OEM. All backups are made and my note 9 is not rooted. On my PC, I have downloaded & installed the latest version of the Samsung drivers and Odin. I have downloaded a copy of the latest TWRP version to flash onto the Note 9 (.tar), and a .tar file of the custom ROM I want to install (made by somebody in this forum and it looks like SM-N960F is compatible).
From what I understand, I now need to plug my device into the PC via USB to connect it to Odin, boot into download mode and flash on TWRP. I can then use TWRP to install the custom ROM.
Questions:
I haven't rooted my device, I don't really want to but will if I need to. So far, I've heard that I don't need to root my device to install a custom ROM. But if I want to install Gapps, do I need to root the device?
Is there anything else that I am missing?
Thank you!

If this is your daily device, i suggest to keep using the stock...

How To Guide Instructions to Install One UI 4 Beta on any S21 device (Exynos+Snapdragon)

First of all, as you all know - you are responsible for anything that you do to your device, neither me nor anyone helping you are responsible for it. Of course this generous community will help you through if anything unexpected happens.
and just to make sure that you're not an idiot, this is for SAMSUNG phones only and only for S21 Series. YOU CAN TRY THIS METHOD ON OTHER SAMSUNG DEVICE BUT YOU WILL NEED UPDATE FILE OF ONE UI BETA 4 FOR THE DEVICE YOU TRYING TO FLASH
-- The process I am explaining and/or describing here is tested by me and it works 100%. I have Canadian S21ultra which is not part of the beta program, I tried to install beta update on Canadian firmware but it failed so I tried this method and I have successfully installed ONE UI 4 Beta and everything works. This should work with S21/S21+
This is a few steps process so read carefully through each and every step, I am gonna try to keep this as easy and noob friendly as possible, if you have any questions feel free to ask.
-- This process will take place in 4 parts so it doesn't get confusing, it needs to go in chronological order.
Step 1 : Download needed files and tools for your device
Step 2 : Backup your data
Step 3 : Flash current stable firmware for your device family either exynos or snapdragon via ODIN
Step 4 : Install One UI 4 Beta 1
Step 1 : Download needed files and tools
1. ODIN tool to flash the firmware (Search xda/Google for this)​2. SDK Platform-tools from here SDK Platform-tools - once downloaded, extract files​3. CURRENT stock firmware of the device (One UI 3.1) - This is the latest One UI 3.1 firmware from the country getting beta updates.​- For Example : If you are installing UK One UI beta, Download Latest Stable One UI 3.1 firmware from UK which is compatible for your device (Please make sure it is the same processer as your current device, if you have exynos S21 device, download exynos and if you have snapdragon version download snapdragon one) -- you can download it from Galaxy Firmware Website or website or source of your choice.​- Extract Firmware zip.​4. Beta Update zip file - Copy this file in Platform-tools folder and rename it to update.zip if needed.​Snapdragon Version : Click Here​Exynos Version : Click Here​​​Step 2 : Backup your data (Recommended but not necessary)
1. Samsung smart switch for Computer -- From Here​2. Samsung Cloud Backup - from settings of your device.​3. Google Backup - from settings of your device.​​Step 3 : Flash Current stable firmware corresponding of your device family either exynos or snapdragon via ODIN - This step will wipe all the data on your phone.
1. Open ODIN executable file (i.e. exe)​2. Connect your phone in download mode to the computer via USB cable (Turn off your phone, while pressing volume up+down button, plug in the USB Cable to your computer, you will see teal screen with some disclaimers on your phone, press volume up)​3. Click on BL on ODIN screen and navigate to the folder where you extracted firmware from step 1, click on file name starting with BL_xxx.tar.md5, wait for it to populate in ODIN. Repeat process with AP, CP and CSC (NOT HOME_CSC) in ODIN (AP will take a lot of time to load so grab a coffee/bear/Tea or whatever you like while that processes).​4. Click start and wait for that to be finished​5. You will see success in ODIN and your device will reboot to the system​6. Turn off your device by pressing power button once its booted.​​Step 4 : Install One UI Beta 1 update
1. Boot your phone into recovery by continue pressing power and volume up button, once you see the samsung logo release both buttons.​2. Select Install update from adb​3. Open platform-tools on your Computer, hold shift and right click - select open command prompt here.​4. write adb sideload update.zip​5. Wait till the process finished.​6. Power On your phone by pressing power buttons and your device should boot into One UI 4 Beta.​7. Follow on-screen instruction to set-up your phone.​​

Sweet write up, thank you. Does this wipe your data at all?

Great job mate. Thank you for the clear instruction

Crushader said:
Sweet write up, thank you. Does this wipe your data at all?
Click to expand...
Click to collapse
yes , he mentioned to flash csc not home csc in step 3

Thank you for the helpful instructions. But , as you already know, a noob question is a must . I own a Hong Kong version of the S21 ultra which is SM-N9980 , snapdragon of course. Can I flash a US or UK firmware that has a different model number in order for me to sideload the One UI 4.0 ?
Thank you for your patience.

[email protected] said:
Thank you for the helpful instructions. But , as you already know, a noob question is a must . I own a Hong Kong version of the S21 ultra which is SM-N9980 , snapdragon of course. Can I flash a US or UK firmware that has a different model number in order for me to sideload the One UI 4.0 ?
Thank you for your patience.
Click to expand...
Click to collapse
sure u cant flash uk as its exynox and for multi oxm csc .
and u have snapdragon
about us i guess u cant too .

carlitobahsoun said:
sure u cant flash uk as its exynox and for multi oxm csc .
and u have snapdragon
about us i guess u cant too .
Click to expand...
Click to collapse
Thank you for the quick answer. I never knew UK version was Exynos. I believe I will wait for the official release.

x10forevers said:
First of all, as you all know - you are responsible for anything that you do to your device, neither me nor anyone helping you are responsible for it. Of course this generous community will help you through if anything unexpected happens.
-- The process I am explaining and/or describing here is tested by me and it works 100%. I have Canadian S21ultra which is not part of the beta program, I tried to install beta update on Canadian firmware but it failed so I tried this method and I have successfully installed ONE UI 4 Beta and everything works. This should work with S21/S21+
This is a few steps process so read carefully through each and every step, I am gonna try to keep this as easy and noob friendly as possible, if you have any questions feel free to ask.
-- This process will take place in 4 parts so it doesn't get confusing, it needs to go in chronological order.
Step 1 : Download needed files and tools for your device
Step 2 : Backup your data
Step 3 : Flash current stable firmware for your device family either exynos or snapdragon via ODIN
Step 4 : Install One UI 4 Beta 1
Step 1 : Download needed files and tools
1. ODIN tool to flash the firmware (Search xda/Google for this)​2. SDK Platform-tools from here SDK Platform-tools - once downloaded, extract files​3. CURRENT stock firmware of the device (One UI 3.1) - This is the latest One UI 3.1 firmware from the country getting beta updates.​- For Example : If you are installing UK One UI beta, Download Latest Stable One UI 3.1 firmware from UK which is compatible for your device (Please make sure it is the same processer as your current device, if you have exynos S21 device, download exynos and if you have snapdragon version download snapdragon one) -- you can download it from Galaxy Firmware Website or website or source of your choice.​- Extract Firmware zip.​4. Beta Update zip file - Copy this file in Platform-tools folder and rename it to update.zip if needed.​Snapdragon Version : Click Here​Exynos Version : Click Here​​​Step 2 : Backup your date (Recommended but not necessary)
1. Samsung smart switch for Computer -- From Here​2. Samsung Cloud Backup - from settings of your device.​3. Google Backup - from settings of your device.​​Step 3 : Flash Current stale firmware corresponding of your device family either exynos or snapdragon via ODIN
1. Open ODIN executable file (i.e. exe)​2. Connect your phone in download mode to the computer via USB cable (Turn off your phone, while pressing volume up+down button, plug in the USB Cable to your computer, you will see teal screen with some disclaimers on your phone, press volume up)​3. Click on BL and navigate to the folder where you extracted firmware from step 1, click on file name starting with BL_xxx.tar.md5, wait for it to populate in ODIN. Repeat process with AP, CP and CSC (NOT HOME_CSC) in ODIN (AP will take a lot of time to load so grab a coffee/bear/Tea or whatever you like while that processes).​4. Click start and wait for that to be finished​5. You will see success in ODIN and your device will reboot to the system​6. Turn off your device by pressing power button once its booted.​​Step 4 : Install One UI Beta 1 update
1. Boot your phone into recovery by continue pressing power and volume up button, once you see the samsung logo release both buttons.​2. Select Install update from adb​3. Open platform-tools on your Computer, hold shift and right click - select open command prompt here.​4. write adb sideload update.zip​5. Wait till the process finished.​6. Power On your phone by pressing power buttons and your device should boot into One UI 4 Beta.​7. Follow on-screen instruction to set-up your phone.​​
Click to expand...
Click to collapse
As the Latest 3.1.1 official firmware for G9980 Galaxy s21 ultra is on August Patch that cause side loading update.zip not to work on current firmware, is it possible to get the same error again in the last step considering firmware patch still not on September??

taher2 said:
As the Latest 3.1.1 official firmware for G9980 Galaxy s21 ultra is on August Patch that cause side loading update.zip not to work on current firmware, is it possible to get the same error again in the last step considering firmware patch still not on September??
Click to expand...
Click to collapse
This is why we flashing latest 3.1.1 firmware first from the country which has already received beta update.

x10forevers said:
This is why we flashing latest 3.1.1 firmware first from the country which has already received beta update.
Click to expand...
Click to collapse
And now which firmware you suggest I should download to install on my Hong-Kong G9980 S21 ultra snapdragon first to accept sideloadin the beta?

taher2 said:
And now which firmware you suggest I should download to install on my Hong-Kong G9980 S21 ultra snapdragon first to accept sideloadin the beta?
Click to expand...
Click to collapse
Guessing it's a snapdragon processor, latest US 3.1 firmware (G998U1) one would be your best bet.

But I guess it has been said they're not compatible with each other!
Different build number versions conflicts!
x10forevers said:
Guessing it's a snapdragon processor, latest US 3.1 firmware (G998U1) one would be your best bet
Click to expand...
Click to collapse

It's not a guide that is needed, but the download links of the Exynos variants haha.
That's the real problem here..

Does this change available bands? I have a Canadian S21U as well on Telus but wondering if it changes bands to the UK.

lexcyn said:
Does this change available bands? I have a Canadian S21U as well on Telus but wondering if it changes bands to the UK.
Click to expand...
Click to collapse
UK is Exynos variant and Canadian s21u is snapdragon, so flashing UK variant won't work on Canadian S21U

x10forevers said:
UK is Exynos variant and Canadian s21u is snapdragon, so flashing UK variant won't work on Canadian S21U
Click to expand...
Click to collapse
Sorry I saw in your example the UK one was mentioned but did not realize that they only had Exynos.
Which firmware did you flash on yours to get it to work? US T-Mobile? And would that also change which bands are available (since I assume it also flashes a different baseband)?

lexcyn said:
Sorry I saw in your example the UK one was mentioned but did not realize that they only had Exynos.
Which firmware did you flash on yours to get it to work? US T-Mobile? And would that also change which bands are available (since I assume it also flashes a different baseband)?
Click to expand...
Click to collapse
VZW variant from US, and I think most of the network bands are same for US and Canada. So you won't have any problem with network. P.S. I am with Telus too and everything works

x10forevers said:
VZW variant from US, and I think most of the network bands are same for US and Canada. So you won't have any problem with network. P.S. I am with Telus too and everything works
Click to expand...
Click to collapse
Thanks, I'm going to give it a go!

x10forevers said:
VZW variant from US, and I think most of the network bands are same for US and Canada. So you won't have any problem with network. P.S. I am with Telus too and everything works
Click to expand...
Click to collapse
Hello why did you choose to flash VZW variant and not XAA or XAS or another variant ?

omek07 said:
Hello why did you choose to flash VZW variant and not XAA or XAS or another variant ?
Click to expand...
Click to collapse
Because the beta update package was from vzw , just wanted to stick to one carrier.