Rooting guide for NOTE 20 series *super nooooob friendly*
Requirements - Brain, note 20, working data cable, windows laptop/ PC, magisk manager, 7Z, Firmware of note 20.
Part A
Bootloader unlocking -
1. Enable OEM unlock under developer options.
2. Turn off your NOTE 20 and make sure it is disconnected from charger or PC/ Laptop.
3. Hold volume up and volume down. While holding them connect your NOTE 20 to PC/ Laptop. When you see warning screen release both keys.
4. You should 3 options. Long press volume up until bootloader unlock prompt appears. Press volume up again to confirm bootloader unlock.
5. NOTE 20 will reset and reboot. Just setup device as usual. Bootloader is unlocked now.
This will trip knox so knox related features won't work and banking apps might not work as well.
PART B
Rooting -
1. Download appropirate firmware according to your current build number. You can check build number in settings > about > software information.
2. Extarct the downloaded firmware. You will see 4 files AP, BL, CP, CSC. Unzip AP file using 7Z 64 BIT.
3. Extracted AP will have several files. Look for boot.img.lz4 extract this file you will get boot.img
4. Install magisk manager ( canary recommended however 20.4 is also working ) on your NOTE 20, move boot.img to internal storage of NOTE 20.
5. Open magisk > click on install > select and patch file > find boot.img and select it. Wait for a while for magisk to patch it. When magisk says DONE you're good to go.
6. Go to internal storage of device > downloads/ download folder > look for magisk_patched.img copy this file to your PC.
7. Rename magisk_patched.img to boot.img and use 7Z to convert boot.img to boot.tar
8. Reboot device to download mode. ( ok this one is easy please google if you don't know how to boot your note 20 to download mode )
9. Open latest odin 3.14X under AP slot select the boot.tar ( created in step 7 ) under options is odin uncheck auto reboot and click on start. When ODIN says "PASS" in green disconnect NOTE 20 from PC.
10. Do it carefully > hold volume down + power until screen turn black. As soon as screen turn black release volume down and hold volume up + power when you see bootloader unlock warning/ samsung splash screen release powe but keep holding volume up until android recovery appears. If you don't see android recovery but you see options like recovery logs, try again, factory reset. That is fine just select factory reset confirm it and reboot device.
11. It will take 5-7 minutes to reboot. When you see setup screen setup device connect to wifi. Install magisk open it and allow additional setup device will reboot again don't worry.
12. After reboot open magisk you will have 2 green check marks.
13. Verify root with root checker. You're done.
Required files -
7Z
ODIN 3.14X
magisk manager ( canary or latest )
Is this for exynos or Qualcomm version?
I could not do root and unlock oem on the snapdragon note 20 5 g att version
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SM-N981U cihazımdan Tapatalk kullanılarak gönderildi
There is no oem lock /unlock key under the developer options on my note 20
SM-N981U cihazımdan Tapatalk kullanılarak gönderildi
Did anyone get rooted on us unlocked Note 20 Ultra? If you did, could you enable eSim by changing the settings in CSC?
Thanks in advance
Sent from my SM-N986U1 using Tapatalk
housepabldroid said:
Is this for exynos or Qualcomm version?
Click to expand...
Click to collapse
Exynos
hasim.kilic said:
I could not do root and unlock oem on the snapdragon note 20 5 g att version View attachment 5101753
SM-N981U cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
This method is not for snap
hasim.kilic said:
There is no oem lock /unlock key under the developer options on my note 20
SM-N981U cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
You may have to wait for kg status
eric6268 said:
Did anyone get rooted on us unlocked Note 20 Ultra? If you did, could you enable eSim by changing the settings in CSC?
Thanks in advance
Sent from my SM-N986U1 using Tapatalk
Click to expand...
Click to collapse
There is a paid service for bootloader unlocks. But that's it
housepabldroid said:
Is this for Exynos or Qualcomm version?
Click to expand...
Click to collapse
Exynos of course
KRAZZIEBOY said:
Exynos of course
Click to expand...
Click to collapse
What if u don't have a oem unlock? Note 10 exy
TheMadScientist said:
What if u don't have a oem unlock? Note 10 exy
Click to expand...
Click to collapse
can't root without unlocking bootloader
What is kg status
SM-N981U cihazımdan Tapatalk kullanılarak gönderildi
hasim.kilic said:
What is kg status
SM-N981U cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
Knox gaurd
---------- Post added at 05:54 PM ---------- Previous post was at 05:52 PM ----------
So its come to my attention that even though I got a F dual sim model in the US since its subsidized payment services and knox are preventing me from achieving oem unlock on my device.
Hi,
I have a silly question, I am very familiar with rooting using Magisk. I am also familiar with flashing custom rom, but not using any Samsung official rom.
If I would unlock the bootloader + root as indicated, how do we manage the rom updates from Samsung? (I see there are hardly any custom roms now for those Note 20 devices).
Does it still work to update when any update is made available by Samsung? Is there any manual actions required? etc...
Tx
htchd2sucks said:
Hi,
I have a silly question, I am very familiar with rooting using Magisk. I am also familiar with flashing custom rom, but not using any Samsung official rom.
If I would unlock the bootloader + root as indicated, how do we manage the rom updates from Samsung? (I see there are hardly any custom roms now for those Note 20 devices).
Does it still work to update when any update is made available by Samsung? Is there any manual actions required? etc...
Tx
Click to expand...
Click to collapse
No. You have to manually update and reroot. It's been like that since day 1 you can never update and be rooted
Wouldn't the Part B work on a Snapdragon after having the bootloader unlocked anyway?
Hi everyone
I have fully root on my N980F exynos.
Tutorial:
- https://forum.xda-developers.com/galaxy-note-20-ultra/how-to/guide-how-to-root-n20-ultra-t4147023 . If you after unlocking bootloader DON NOT have OEM unlock grey out, do this: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
and continuing.
I root my device, flashed everything, but can not start TWRP recovery. Reboot every time. I used stock recovery for now.
hasim.kilic said:
There is no oem lock /unlock key under the developer options on my note 20
SM-N981U cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
what is my rom binary?!
KRAZZIEBOY said:
Rooting guide for NOTE 20 series *super nooooob friendly*
Requirements - Brain, note 20, working data cable, windows laptop/ PC, magisk manager, 7Z, Firmware of note 20.
Part A
Bootloader unlocking -
1. Enable OEM unlock under developer options.
2. Turn off your NOTE 20 and make sure it is disconnected from charger or PC/ Laptop.
3. Hold volume up and volume down. While holding them connect your NOTE 20 to PC/ Laptop. When you see warning screen release both keys.
4. You should 3 options. Long press volume up until bootloader unlock prompt appears. Press volume up again to confirm bootloader unlock.
5. NOTE 20 will reset and reboot. Just setup device as usual. Bootloader is unlocked now.
This will trip knox so knox related features won't work and banking apps might not work as well.
PART B
Rooting -
1. Download appropirate firmware according to your current build number. You can check build number in settings > about > software information.
2. Extarct the downloaded firmware. You will see 4 files AP, BL, CP, CSC. Unzip AP file using 7Z 64 BIT.
3. Extracted AP will have several files. Look for boot.img.lz4 extract this file you will get boot.img
4. Install magisk manager ( canary recommended however 20.4 is also working ) on your NOTE 20, move boot.img to internal storage of NOTE 20.
5. Open magisk > click on install > select and patch file > find boot.img and select it. Wait for a while for magisk to patch it. When magisk says DONE you're good to go.
6. Go to internal storage of device > downloads/ download folder > look for magisk_patched.img copy this file to your PC.
7. Rename magisk_patched.img to boot.img and use 7Z to convert boot.img to boot.tar
8. Reboot device to download mode. ( ok this one is easy please google if you don't know how to boot your note 20 to download mode )
9. Open latest odin 3.14X under AP slot select the boot.tar ( created in step 7 ) under options is odin uncheck auto reboot and click on start. When ODIN says "PASS" in green disconnect NOTE 20 from PC.
10. Do it carefully > hold volume down + power until screen turn black. As soon as screen turn black release volume down and hold volume up + power when you see bootloader unlock warning/ samsung splash screen release powe but keep holding volume up until android recovery appears. If you don't see android recovery but you see options like recovery logs, try again, factory reset. That is fine just select factory reset confirm it and reboot device.
11. It will take 5-7 minutes to reboot. When you see setup screen setup device connect to wifi. Install magisk open it and allow additional setup device will reboot again don't worry.
12. After reboot open magisk you will have 2 green check marks.
13. Verify root with root checker. You're done.
Required files -
7Z
ODIN 3.14X
magisk manager ( canary or latest )
Click to expand...
Click to collapse
Hi Krazzieboy. I was excited when I found your thread but disappointed with the lack of success everyone seems to have had with following your process. So, I wanted to ask exactly which model number and OS are you using with the Note20 Ultra 5G and where people could go to get the firmware. This would help clarify which version/model of this phone to get if someone (such as myself) wanted to get one of these. I just got a Motorola One 5G Ace and I hate it. I'd like to go back to a Samsung phone (my previous phone was a Note 4).
KRAZZIEBOY said:
Rooting guide for NOTE 20 series *super nooooob friendly*
Requirements - Brain, note 20, working data cable, windows laptop/ PC, magisk manager, 7Z, Firmware of note 20.
Part A
Bootloader unlocking -
1. Enable OEM unlock under developer options.
2. Turn off your NOTE 20 and make sure it is disconnected from charger or PC/ Laptop.
3. Hold volume up and volume down. While holding them connect your NOTE 20 to PC/ Laptop. When you see warning screen release both keys.
4. You should 3 options. Long press volume up until bootloader unlock prompt appears. Press volume up again to confirm bootloader unlock.
5. NOTE 20 will reset and reboot. Just setup device as usual. Bootloader is unlocked now.
This will trip knox so knox related features won't work and banking apps might not work as well.
PART B
Rooting -
1. Download appropirate firmware according to your current build number. You can check build number in settings > about > software information.
2. Extarct the downloaded firmware. You will see 4 files AP, BL, CP, CSC. Unzip AP file using 7Z 64 BIT.
3. Extracted AP will have several files. Look for boot.img.lz4 extract this file you will get boot.img
4. Install magisk manager ( canary recommended however 20.4 is also working ) on your NOTE 20, move boot.img to internal storage of NOTE 20.
5. Open magisk > click on install > select and patch file > find boot.img and select it. Wait for a while for magisk to patch it. When magisk says DONE you're good to go.
6. Go to internal storage of device > downloads/ download folder > look for magisk_patched.img copy this file to your PC.
7. Rename magisk_patched.img to boot.img and use 7Z to convert boot.img to boot.tar
8. Reboot device to download mode. ( ok this one is easy please google if you don't know how to boot your note 20 to download mode )
9. Open latest odin 3.14X under AP slot select the boot.tar ( created in step 7 ) under options is odin uncheck auto reboot and click on start. When ODIN says "PASS" in green disconnect NOTE 20 from PC.
10. Do it carefully > hold volume down + power until screen turn black. As soon as screen turn black release volume down and hold volume up + power when you see bootloader unlock warning/ samsung splash screen release powe but keep holding volume up until android recovery appears. If you don't see android recovery but you see options like recovery logs, try again, factory reset. That is fine just select factory reset confirm it and reboot device.
11. It will take 5-7 minutes to reboot. When you see setup screen setup device connect to wifi. Install magisk open it and allow additional setup device will reboot again don't worry.
12. After reboot open magisk you will have 2 green check marks.
13. Verify root with root checker. You're done.
Required files -
7Z
ODIN 3.14X
magisk manager ( canary or latest )
Click to expand...
Click to collapse
I guess I should have said these are in files on my PC and it was emailing then to me to open on my phone. I'm sorry.
How can I extract the PDU files not and and MMS and then once they are extracted and readable I can then email then to my phone
hey.
when i extract the img file, it is only 1kb, anf the magisk is failing to patch it.
am i missing something?
Related
This guide was made prior to there being a working custom recovery for this device. I highly recommend installing @afaneh92 TWRP in this thread and then simply flash magisk from recovery.
I purchased this phone a few days ago for around £120 - Bargain.
I have spent a few evenings trying to obtain root - and finally managed to achieve it with Magisk
Full data wipes are required during the process (please backup first)
Knox will trip but safetynet passes and google pay working once magisk hide enabled
Based on the Samsung specific guide provided on Magisk Github - with a few minor differences.
I have uploaded all of the tools and files used to my personal onedrive folder -
Make sure your device is on the latest firmware and download the zip
- I used SamFwTool version 1.21.0 to download the BTU Firmware for SM-A025G A025GXXU1AUA3
Install Magisk apk on your device.
Extract the AP _ tar.md5 from the downloaded firmware .zip using 7zip
Transfer the AP to your device and Patch it with Magisk , then copy back to your computer.
Enable OEM Unlock and Unlock the bootloader the instructions from magisk git are below, for those that need a reminder.
Spoiler: Unlocking Bootloader
Unlocking bootloader on modern Samsung devices have some caveats:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader.
This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is greyed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
This is where we deviate from the magisk guide... as when I flashed the magisk patched AP along with the BL CP and CSC, you get a vbmeta error and it simply reboots to stock. Magisk seems to patch the vbmeta file and I tried replacing the vbmeta with the stock version from the firmware zip but that also was fruitless.
Extract the boot.img from magisk patched AP
Extract recovery.img.lz4 and vbmeta.img.lz4 from the stock (unpatched) AP file
7zip - create a new TAR, adding only those 3 files. Boot.tar will suffice for filename
Odin 3.14.4 - uncheck auto reboot and then Flash boot.tar in the AP section (CSC, HOME CSC, CP, BL not required - as the device and download are using the latest firmware)
The next part is essential and doing it wrong will again, result in no root....
I mistakenly pressed power up and it loaded fastboot... booting direct to recovery from fastboot again, results in no root.
Hold volume down and power to reboot...
As soon as the screen turns black indicating it is rebooting let go of volume down and hold power and volume up
Release power button when you see the android logo but continue to hold volume up
Release volume up when the unlocked bootloader warning appears
Tap the power button once to skip that warning
Stock recovery should now appear
Select wipe data / factory reset
Reboot system
Setup as usual and install the magisk apk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. .
Update 10April2021: Since doing this quite a few times, I've actually had most success with Magisk 22.0 (I initially went with Canary - but stock is less hit and miss and if you do it exactly like the steps above you will get root.
Update:
Have just updated to magisk 22003 directly within magisk app - no issues to report so far
thank you so much for the guide, i found nothing from google
can i unroot after modify this device with magisk canary ??
Normanbayuaji said:
thank you so much for the guide, i found nothing from google
can i unroot after modify this device with magisk canary ??
Click to expand...
Click to collapse
No problem at all, It was the same position I was in so had to post as it was painful process - needed it documented for myself to follow in future too lol
yes - it's very easy to unroot directly in the magisk app
I successfully upgraded to the latest version 22004 from within the magisk app. No issues to report.
can this work on the tmobile version??
mines is a 025q
I am trying to use this same process on an SM-A025V (US Verizon) but I have ran into an issue. I was able to find and download firmware for my variant but I do not have the "oem unlock" option in my developer menu. Is this because I do not have the international version?
Flik93 said:
I am trying to use this same process on an SM-A025V (US Verizon) but I have ran into an issue. I was able to find and download firmware for my variant but I do not have the "oem unlock" option in my developer menu. Is this because I do not have the international version?
Click to expand...
Click to collapse
Seems like its carrier locked. You need to be able to unlock bootloader unfortunately
Ghet2 said:
can this work on the tmobile version??
Click to expand...
Click to collapse
Can you unlock your bootloader?
Dont kno i have t-mobile version and. I have it
Flik93 said:
I am trying to use this same process on an SM-A025V (US Verizon) but I have ran into an issue. I was able to find and download firmware for my variant but I do not have the "oem unlock" option in my developer menu. Is this because I do not have the international version?
Click to expand...
Click to collapse
CFKod said:
Seems like its carrier locked. You need to be able to unlock bootloader unfortunately
Click to expand...
Click to collapse
T-mobile isn't so would I be able to do this with t-mobile firmware . If it's available I don't kno
Well..
Ghet2 said:
Dont kno i have t-mobile version and. I have it
T-mobile isn't so would I be able to do this with t-mobile firmware . If it's available I don't kno
Click to expand...
Click to collapse
If you have oem unlock then you'll be able to do it...
CFKod said:
Well..
If you have oem unlock then you'll be able to do it...
Click to expand...
Click to collapse
Has to be a t-mobile firmware? or would this one work
Anything for a025u yes
CFKod said:
I purchased this phone a few days ago for around £120 - Bargain.
I have spent a few evenings trying to obtain root - and finally managed to achieve it with Magisk
Full data wipes are required during the process (please backup first)
Knox will trip but safetynet passes and google pay working once magisk hide enabled
Based on the Samsung specific guide provided on Magisk Github - with a few minor differences.
I have uploaded all of the tools and files used to my personal onedrive folder -
Make sure your device is on the latest firmware and download the zip
- I used SamFwTool version 1.21.0 to download the BTU Firmware for SM-A025G A025GXXU1AUA3
Install Magisk apk on your device.
Extract the AP _ tar.md5 from the downloaded firmware .zip using 7zip
Transfer the AP to your device and Patch it with Magisk , then copy back to your computer.
Enable OEM Unlock and Unlock the bootloader the instructions from magisk git are below, for those that need a reminder.
Spoiler: Unlocking Bootloader
Unlocking bootloader on modern Samsung devices have some caveats:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader.
This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is greyed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
This is where we deviate from the magisk guide... as when I flashed the magisk patched AP along with the BL CP and CSC, you get a vbmeta error and it simply reboots to stock. Magisk seems to patch the vbmeta file and I tried replacing the vbmeta with the stock version from the firmware zip but that also was fruitless.
Extract the boot.img from magisk patched AP
Extract recovery.img.lz4 and vbmeta.img.lz4 from the stock (unpatched) AP file
7zip - create a new TAR, adding only those 3 files. Boot.tar will suffice for filename
Odin 3.14.4 - uncheck auto reboot and then Flash boot.tar in the AP section (CSC, HOME CSC, CP, BL not required - as the device and download are using the latest firmware)
The next part is essential and doing it wrong will again, result in no root....
Przez pomyłkę wcisnąłem zasilanie i załadowałem fastboot ... ponowne uruchomienie bezpośrednio do odzyskiwania z fastboot, nie daje roota.
Przytrzymaj głośność i włącz, aby ponownie uruchomić...
Gdy tylko ekran stanie się czarny, wskazując na ponowne uruchamianie, puść zmniejsz głośność i przytrzymaj zasilanie i zwiększ głośność
Zwolnij przycisk zasilania, gdy zobaczysz logo Androida, ale nadal zwiększaj głośność
Zwolnij głośność, gdy pojawi się ostrzeżenie o odblokowanym bootloaderze
Naciśnij raz przycisk zasilania, aby pominąć to ostrzeżenie
Odzyskiwanie zapasów powinno się teraz pojawić
Wybierz wyczyść dane / przywróć ustawienia fabryczne
Uruchom ponownie system
Skonfiguruj jak zwykle i zainstaluj aplikację magisk
View attachment 5241955. View attachment 5241957.View attachment 5241959
Aktualizacja 10 kwietnia 2021: Odkąd zrobiłem to kilka razy, w rzeczywistości odniosłem największy sukces z Magisk 22.0 (początkowo poszedłem z Canary – ale zapasy są mniej trafione i chybione, a jeśli zrobisz to dokładnie tak, jak powyższe kroki, dostaniesz root.
Click to expand...
Click to collapse
cześć5g
CFKod said:
I purchased this phone a few days ago for around £120 - Bargain.
I have spent a few evenings trying to obtain root - and finally managed to achieve it with Magisk
Full data wipes are required during the process (please backup first)
Knox will trip but safetynet passes and google pay working once magisk hide enabled
Based on the Samsung specific guide provided on Magisk Github - with a few minor differences.
I have uploaded all of the tools and files used to my personal onedrive folder -
Make sure your device is on the latest firmware and download the zip
- I used SamFwTool version 1.21.0 to download the BTU Firmware for SM-A025G A025GXXU1AUA3
Install Magisk apk on your device.
Extract the AP _ tar.md5 from the downloaded firmware .zip using 7zip
Transfer the AP to your device and Patch it with Magisk , then copy back to your computer.
Enable OEM Unlock and Unlock the bootloader the instructions from magisk git are below, for those that need a reminder.
Spoiler: Unlocking Bootloader
Unlocking bootloader on modern Samsung devices have some caveats:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader.
This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is greyed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
This is where we deviate from the magisk guide... as when I flashed the magisk patched AP along with the BL CP and CSC, you get a vbmeta error and it simply reboots to stock. Magisk seems to patch the vbmeta file and I tried replacing the vbmeta with the stock version from the firmware zip but that also was fruitless.
Extract the boot.img from magisk patched AP
Extract recovery.img.lz4 and vbmeta.img.lz4 from the stock (unpatched) AP file
7zip - create a new TAR, adding only those 3 files. Boot.tar will suffice for filename
Odin 3.14.4 - uncheck auto reboot and then Flash boot.tar in the AP section (CSC, HOME CSC, CP, BL not required - as the device and download are using the latest firmware)
The next part is essential and doing it wrong will again, result in no root....
I mistakenly pressed power up and it loaded fastboot... booting direct to recovery from fastboot again, results in no root.
Hold volume down and power to reboot...
As soon as the screen turns black indicating it is rebooting let go of volume down and hold power and volume up
Release power button when you see the android logo but continue to hold volume up
Release volume up when the unlocked bootloader warning appears
Tap the power button once to skip that warning
Stock recovery should now appear
Select wipe data / factory reset
Reboot system
Setup as usual and install the magisk apk
View attachment 5241955. View attachment 5241957. View attachment 5241959
Update 10April2021: Since doing this quite a few times, I've actually had most success with Magisk 22.0 (I initially went with Canary - but stock is less hit and miss and if you do it exactly like the steps above you will get root.
Click to expand...
Click to collapse
Hi i have sm-a25g As I connect with vol plus vol minus I connect usb nothing happens but charging the battery as I hold other keys, e.g. power vol plus I release power I keep vol plus the phone jumps in fastboot mode. In download mode I can only enter from adb reboot download but bypass the bootloader lock window, the manual input combinations in download mode do not work for me. Do you have any idea and can I ask for help?
Hi, I have a problem with unlocking the bootloader in SM-A025G. I wrote a comment on you tube I got a contact from you whats upp. The problem is that after selecting oem unlock and connecting the turned off phone, holding vol plus vol minus and connect usb, there is only a charging mode and it should be a download mode with the selection of vol plus to unlock the bootloader. To flash firmware, the only way to go with adb reboot download but bypass the unlock board is the download mode. Phone with European distribution binary u2 android 11
[email protected] said:
cześć5g
Hi i have sm-a25g As I connect with vol plus vol minus I connect usb nothing happens but charging the battery as I hold other keys, e.g. power vol plus I release power I keep vol plus the phone jumps in fastboot mode. In download mode I can only enter from adb reboot download but bypass the bootloader lock window, the manual input combinations in download mode do not work for me. Do you have any idea and can I ask for help?
Click to expand...
Click to collapse
With device turned off but plugged into USB...
Power it back up
let go of power and hold volume up and volume down. and it will boot to the download mode screen.
[email protected] said:
Hi, I have a problem with unlocking the bootloader in SM-A025G. I wrote a comment on you tube I got a contact from you whats upp. The problem is that after selecting oem unlock and connecting the turned off phone, holding vol plus vol minus and connect usb, there is only a charging mode and it should be a download mode with the selection of vol plus to unlock the bootloader. To flash firmware, the only way to go with adb reboot download but bypass the unlock board is the download mode. Phone with European distribution binary u2 android 11
Click to expand...
Click to collapse
Sorry for late response.
Follow as per thread just posted
idk if this is news or not but im rooted on the boost variant of the sm-a025u. my question is now that im rooted can i flash the u1 (unlocked xaa) firmware to network unlock the device?
chrisdsj said:
idk if this is news or not but im rooted on the boost variant of the sm-a025u. my question is now that im rooted can i flash the u1 (unlocked xaa) firmware to network unlock the device?
Click to expand...
Click to collapse
How did u root it I have the metro version
Not sure regarding network unlock sorry.
Hi there,
I haven't found much information regarding the Canadian variant of the A52 5G yet, sorry.
I'd assume that the Canadian bootloader is already unlocked to begin with (Carrier is Koodo. I know my older Koodo Galaxy S4 I337 was never locked as well) ? I do not see the OEM Unlock option, even when I bump the date by 7 days from now on.
This would mean that I could simply proceed and patch the boot to install Magisk? Has anyone succeeded yet on the Canadian variant?
Thank you, appreciated,
Ryola said:
This will erase your phone's data so backup first
This will trip knox and prevent alot of samsung apps working
Unlocking Bootloader
1. Enable OEM unlocking in developer options
2. Turn phone off
3. Plug a usb into pc but not phone
4. Hold vol up and down and plug usb into phone
5. Wait for green screen and follow instructions to unlock bootloader (as follows)
5.5. Long press vol up on green screen then press vol up again
Installing magisk
1. Download your firmware from the internet
2. Extract the AP tar.md5 file
3. Place file on root of phone
4. Download and install Magisk (I used Canary)
5. Make sure connected to internet
6. Open Magisk and press the top install (Manager not the app install)
7. Select Install > Select and Patch a File and select the AP file you put on the phone
8. Wait for it to patch and create a new file
9. Find the new file, usually called magisk_patched in your downloads folder, but Magisk would have said what and where on the patching screen when done
10. In Odin flash this new AP file
11. If needed reinstall Magisk app, open it and let it update
To get saftey net to pass I had to use The universal saftey net magisk module found somewhere on this site. I can find it later if needed
Those are the steps I did, hope it helps
Click to expand...
Click to collapse
EDIT: Seems like I'm mistaken and I need to pay and unlock anyway I believe: https://forum.xda-developers.com/t/...unlock-for-samsung-us-canada-devices.4215101/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[EXYNOS ONLY] Samsung Galaxy S10 series OneUI 4.0 Android 12 Beta Thread
[Beta Program has Start Now]
Samsung has started the beta program for the S21 Series in Korea and Germany and will be rolling out to other countries later, however the beta program for the S10 series is yet to start/even get announced. It is expected to start in the coming weeks.
-This thread will be for sharing tips and help and update.zip/.bin files (when/if available) for the upcoming OneUI 4.0 Android 12 Beta for the Galaxy S10 series (Exynos/International/Unlocked) version.
Eligible models
-Galaxy S10e (SM-G970F)
-Galaxy S10 (SM-G973F)
-Galaxy S10+ (SM-G975F)
-Galaxy S10 5G (SM-G977B)
Installation Methods:
ADB-method:
1. Download SDK platform tools https://developer.android.com/studio/releases/platform-tools
2. Extract the file in your desktop.
3. Inside the extracted folder put the update.zip file
4. Inside this folder, holding left shift, right click the mouse and select "open command prompt here". The command prompt will open.
5. Shutdown your phone and connect it to the pc
6. Holding power+volume up buttons, enter into recovery mode.
7. Select "update via ADB". (scroll down using the volume buttons and select using the power button).
8. Connect the phone to a PC using an original samsung USB cable.
9. In the command prompt run the following command:
./adb devices
10. Wait to see that the daemon has started and that your device is found.
11. If you device is found, run the following command:
./adb sideload update.zip
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options on your pc you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Connect any USB device to your device, AKG earphones could work, then press Power+volume up buttons to get into recovery mode.
5. Using your volume keys navigate to "update via sdcard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes installing. It will take some time.
8. Phone will reboot by itself and load android.
The update process will start. You will see a percentage counting. First it will verify, then patch etc. Do not move the cable, disconnect the phone or power off the PC.
Once the process is completed (it takes some time) the phone will boot itself, update the apps and log into your home screen.
-Update.zip FOTA links:
S10e (SM-G970F) :S10 (SM-G973F) :S10+ (SM-G975F) :S10 5G (SM-G977B) :
-South Korean versions :S10e (SM-G970N) :Beta 1 Beta 2 Beta 3 newS10 (SM-G973N) :Beta 1Beta 2Beta 3 newS10+ (SM-G975N) :S10 5G (SM-G977N) :Beta 1Beta 2 new
-US versions:S10e (SM-G970U) :S10 (SM-G973U) :S10+ (SM-G975U) :S10 5G (SM-G977U) :
For Note DevicesGalaxy Note 10 (SM-N9700)Galaxy Note 10 (SM-N970F)Galaxy Note 10 (SM-N970N)Galaxy Note 10 (SM-N970U)Galaxy Note 10 (SM-N970U1)Galaxy Note 10 (SM-N970W)Galaxy Note 10+ (SM-N9750)Galaxy Note 10+ (SM-N9758)Galaxy Note 10+ (SM-N975C)Galaxy Note 10+ (SM-N975D)Galaxy Note 10+ (SM-N975F)Galaxy Note 10+ (SM-N975J)Galaxy Note 10+ (SM-N975N)Galaxy Note 10+ (SM-N975U)Galaxy Note 10+ (SM-N975U1)Beta 1Galaxy Note 10+ (SM-N975VU)
Galaxy Note 5G Korea (SM-N971N)Beta 1Beta 2 new
Galaxy Note + 5G Korea (SM-N976N)Beta 1Beta 2 new
There are two methods that you can use to get into recovery mode
Method 1:
1. Connect your phone to your PC (Make sure USB debugging is on).
2. Using ADB, enter the command ./adb reboot recovery
3. Wait a little and you should be in recovery mode.
Method 2:
1. Power off your device
2. Connect your device to a PC or use the AKG earphones.
3. Hold down Power+VolumeUp buttons and keep pressing them until you enter recovery mode.
How to capture the update.bin file to share with other people:
1. Download HTTP canary app https://apkgk.com/fr/com.guoshi.httpcanary
2. Open HTTP Canary app
3. Leave the app and go to the settings and Start the software update in settings by pressing "download" and don't pause it
4. Go back to canary app and start it by pressing the little circle at the bottom right, and it will grab the link for you
5. Copy the link and post it here if you wish.
This will not trip knox if done by the methods above
Don't install a beta unless you are fully aware what you are going into.
Don't install the beta if you want your phone to be stable, IT'S a BETA.
It's recommended to make a backup of your data before updating to the Android 12 Beta.
Important Notes:
-Rename the .bin file to update.zip in order to be able to flash it from recovery.
-A common mistake done by some people is that they see the file named update while its a WinRAR.zip file already, then they add another .zip making the name of the file update.zip.zip which will not be flashed successfully, So make sure you do it right.
-Updating to the beta is AT YOUR RISK, No one is responsible if anything goes wrong.
You will not receive OTAs again UNTIL you are on a firmware that gets released later for your original CSC, thats most likely not happening before the BETA is over.
Small note:
My Galaxy S10e isn't from a country that has a beta program, I manually changed the CSC to TUR, that makes me receive TUR OTA Updates but participating in the beta in the past years, needed a sim card from the country of your CSC, Meaning i need a german SIM to be able to participate, so sadly i will not be able to pull the update.zip file unfortunately, But i will try my BEST to keep the thread updated with the latest beta update.zip file (If/when someone pulls it)
Thank you
You welcome
Can't wait!
G973N link http://fota-secure-dn.ospserver.net:80/firmware/KOO/SM-G973N/nspx/667b4adbde854411912fe145d1951ef1.bin?px-time=61f91980&px-hash=8ab0ada7027aff196ee1a22655208a8d&px-wid=2834565-WSA211203112901&px-wctime=2021-12-03 11:29:01&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
Hacker_Ayoub said:
G973N link http://fota-secure-dn.ospserver.net:80/firmware/KOO/SM-G973N/nspx/667b4adbde854411912fe145d1951ef1.bin?px-time=61f91980&px-hash=8ab0ada7027aff196ee1a22655208a8d&px-wid=2834565-WSA211203112901&px-wctime=2021-12-03 11:29:01&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
Click to expand...
Click to collapse
Does this Work For G937F or is the Korean variant completly different from the European?
MathiTV said:
Does this Work For G937F or is the Korean variant completly different from the European?
Click to expand...
Click to collapse
Its just for the G973N only bro so its just for the korean variant
Can't wait for the S10e version. Will the Korean Zip work with my SM-G970F from a different country?
m.zakariyya.g said:
Can't wait for the S10e version. Will the Korean Zip work with my SM-G970F from a different country?
Click to expand...
Click to collapse
no it will not.
themediapadguy said:
no it will not.
Click to expand...
Click to collapse
A bit confused, if the zip would only work with the Korean SM-G970F, then what's the point of the entire thread?
according to sammyfans: Samsung confirmed that the Android 12-based One UI 4 Beta is only available in seven countries, check the list below:
South Korea
United States (For Unlocked/T-Mobile/Sprint)
Germany
India
United Kingdom (UK)
China
Poland
so if you are In one of this countries you can check the Members app. I'm from Germany and I will upload the zip when its avalible (in germany we have the SM-G973F variant)
MathiTV said:
according to sammyfans: Samsung confirmed that the Android 12-based One UI 4 Beta is only available in seven countries, check the list below:
South Korea
United States (For Unlocked/T-Mobile/Sprint)
Germany
India
United Kingdom (UK)
China
Poland
so if you are In one of this countries you can check the Members app. I'm from Germany and I will upload the zip when its avalible (in germany we have the SM-G973F variant)
Click to expand...
Click to collapse
im from india, banner doesnt show up on members app.
looks people from USA have started getting it
Y
m.zakariyya.g said:
Can't wait for the S10e version. Will the Korean Zip work with my SM-G970F from a different country?
Click to expand...
Click to collapse
Yes bro it will work but you should have the update file for G970F only not for other variant i am also have G970F and i am waiting for someone to post the update file for it
Hacker_Ayoub said:
Y
Yes bro it will work but you should have the update file for G970F only not for other variant i am also have G970F and i am waiting for someone to post the update file for it
Click to expand...
Click to collapse
Thanks a lot, anxiously waiting for it.
m.zakariyya.g said:
Thanks a lot, anxiously waiting for it.
Click to expand...
Click to collapse
Me too brother if you get the update file post it here okey
Hacker_Ayoub said:
View attachment 5473849
[EXYNOS ONLY] Samsung Galaxy S10 series OneUI 4.0 Android 12 Beta Thread
[Beta Program has Start Now]
Samsung has started the beta program for the S21 Series in Korea and Germany and will be rolling out to other countries later, however the beta program for the S10 series is yet to start/even get announced. It is expected to start in the coming weeks.
-This thread will be for sharing tips and help and update.zip/.bin files (when/if available) for the upcoming OneUI 4.0 Android 12 Beta for the Galaxy S10 series (Exynos/International/Unlocked) version.
Eligible models
-Galaxy S10e (SM-G970F)
-Galaxy S10 (SM-G973F)
-Galaxy S10+ (SM-G975F)
-Galaxy S10 5G (SM-G977B)
Installation Methods:
ADB-method:
1. Download SDK platform tools https://developer.android.com/studio/releases/platform-tools
2. Extract the file in your desktop.
3. Inside the extracted folder put the update.zip file
4. Inside this folder, holding left shift, right click the mouse and select "open command prompt here". The command prompt will open.
5. Shutdown your phone and connect it to the pc
6. Holding power+volume up buttons, enter into recovery mode.
7. Select "update via ADB". (scroll down using the volume buttons and select using the power button).
8. Connect the phone to a PC using an original samsung USB cable.
9. In the command prompt run the following command:
./adb devices
10. Wait to see that the daemon has started and that your device is found.
11. If you device is found, run the following command:
./adb sideload update.zip
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options on your pc you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Connect any USB device to your device, AKG earphones could work, then press Power+volume up buttons to get into recovery mode.
5. Using your volume keys navigate to "update via sdcard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes installing. It will take some time.
8. Phone will reboot by itself and load android.
The update process will start. You will see a percentage counting. First it will verify, then patch etc. Do not move the cable, disconnect the phone or power off the PC.
Once the process is completed (it takes some time) the phone will boot itself, update the apps and log into your home screen.
-Update.zip FOTA links:
S10e (SM-G970F) :S10 (SM-G973F) :S10+ (SM-G975F) :S10 5G (SM-G977B) :
-South Korean versions :S10e (SM-G970N) :S10 (SM-G973N) :Beta1S10+ (SM-G975N) :S10 5G (SM-G977N) :
-US versions:S10e (SM-G970U) :S10 (SM-G973U) :S10+ (SM-G975U) :S10 5G (SM-G977U) :
There are two methods that you can use to get into recovery mode
Method 1:
1. Connect your phone to your PC (Make sure USB debugging is on).
2. Using ADB, enter the command ./adb reboot recovery
3. Wait a little and you should be in recovery mode.
Method 2:
1. Power off your device
2. Connect your device to a PC or use the AKG earphones.
3. Hold down Power+VolumeUp buttons and keep pressing them until you enter recovery mode.
How to capture the update.bin file to share with other people:
1. Download HTTP canary app from playstore
2. Open HTTP Canary app
3. Leave the app and go to the settings and Start the software update in settings by pressing "download" and don't pause it
4. Go back to canary app and start it by pressing the little circle at the bottom right, and it will grab the link for you
5. Copy the link and post it here if you wish.
This will not trip knox if done by the methods above
Don't install a beta unless you are fully aware what you are going into.
Don't install the beta if you want your phone to be stable, IT'S a BETA.
It's recommended to make a backup of your data before updating to the Android 12 Beta.
Important Notes:
-Rename the .bin file to update.zip in order to be able to flash it from recovery.
-A common mistake done by some people is that they see the file named update while its a WinRAR.zip file already, then they add another .zip making the name of the file update.zip.zip which will not be flashed successfully, So make sure you do it right.
-Updating to the beta is AT YOUR RISK, No one is responsible if anything goes wrong.
You will not receive OTAs again UNTIL you are on a firmware that gets released later for your original CSC, thats most likely not happening before the BETA is over.
Small note:
My Galaxy S10e isn't from a country that has a beta program, I manually changed the CSC to TUR, that makes me receive TUR OTA Updates but participating in the beta in the past years, needed a sim card from the country of your CSC, Meaning i need a german SIM to be able to participate, so sadly i will not be able to pull the update.zip file unfortunately, But i will try my BEST to keep the thread updated with the latest beta update.zip file (If/when someone pulls it)
Thank you
Click to expand...
Click to collapse
So i have s10e verizon (USA) unlocked and i live in indonesia without the vzw sim card, then i cant join the beta program? Even it via samsung member app?
Hacker_Ayoub said:
View attachment 5473849
[EXYNOS ONLY] Samsung Galaxy S10 series OneUI 4.0 Android 12 Beta Thread
[Beta Program has Start Now]
Samsung has started the beta program for the S21 Series in Korea and Germany and will be rolling out to other countries later, however the beta program for the S10 series is yet to start/even get announced. It is expected to start in the coming weeks.
-This thread will be for sharing tips and help and update.zip/.bin files (when/if available) for the upcoming OneUI 4.0 Android 12 Beta for the Galaxy S10 series (Exynos/International/Unlocked) version.
Eligible models
-Galaxy S10e (SM-G970F)
-Galaxy S10 (SM-G973F)
-Galaxy S10+ (SM-G975F)
-Galaxy S10 5G (SM-G977B)
Installation Methods:
ADB-method:
1. Download SDK platform tools https://developer.android.com/studio/releases/platform-tools
2. Extract the file in your desktop.
3. Inside the extracted folder put the update.zip file
4. Inside this folder, holding left shift, right click the mouse and select "open command prompt here". The command prompt will open.
5. Shutdown your phone and connect it to the pc
6. Holding power+volume up buttons, enter into recovery mode.
7. Select "update via ADB". (scroll down using the volume buttons and select using the power button).
8. Connect the phone to a PC using an original samsung USB cable.
9. In the command prompt run the following command:
./adb devices
10. Wait to see that the daemon has started and that your device is found.
11. If you device is found, run the following command:
./adb sideload update.zip
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options on your pc you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Connect any USB device to your device, AKG earphones could work, then press Power+volume up buttons to get into recovery mode.
5. Using your volume keys navigate to "update via sdcard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes installing. It will take some time.
8. Phone will reboot by itself and load android.
The update process will start. You will see a percentage counting. First it will verify, then patch etc. Do not move the cable, disconnect the phone or power off the PC.
Once the process is completed (it takes some time) the phone will boot itself, update the apps and log into your home screen.
-Update.zip FOTA links:
S10e (SM-G970F) :S10 (SM-G973F) :S10+ (SM-G975F) :S10 5G (SM-G977B) :
-South Korean versions :S10e (SM-G970N) :S10 (SM-G973N) :Beta1S10+ (SM-G975N) :S10 5G (SM-G977N) :
-US versions:S10e (SM-G970U) :S10 (SM-G973U) :S10+ (SM-G975U) :S10 5G (SM-G977U) :
There are two methods that you can use to get into recovery mode
Method 1:
1. Connect your phone to your PC (Make sure USB debugging is on).
2. Using ADB, enter the command ./adb reboot recovery
3. Wait a little and you should be in recovery mode.
Method 2:
1. Power off your device
2. Connect your device to a PC or use the AKG earphones.
3. Hold down Power+VolumeUp buttons and keep pressing them until you enter recovery mode.
How to capture the update.bin file to share with other people:
1. Download HTTP canary app from playstore
2. Open HTTP Canary app
3. Leave the app and go to the settings and Start the software update in settings by pressing "download" and don't pause it
4. Go back to canary app and start it by pressing the little circle at the bottom right, and it will grab the link for you
5. Copy the link and post it here if you wish.
This will not trip knox if done by the methods above
Don't install a beta unless you are fully aware what you are going into.
Don't install the beta if you want your phone to be stable, IT'S a BETA.
It's recommended to make a backup of your data before updating to the Android 12 Beta.
Important Notes:
-Rename the .bin file to update.zip in order to be able to flash it from recovery.
-A common mistake done by some people is that they see the file named update while its a WinRAR.zip file already, then they add another .zip making the name of the file update.zip.zip which will not be flashed successfully, So make sure you do it right.
-Updating to the beta is AT YOUR RISK, No one is responsible if anything goes wrong.
You will not receive OTAs again UNTIL you are on a firmware that gets released later for your original CSC, thats most likely not happening before the BETA is over.
Small note:
My Galaxy S10e isn't from a country that has a beta program, I manually changed the CSC to TUR, that makes me receive TUR OTA Updates but participating in the beta in the past years, needed a sim card from the country of your CSC, Meaning i need a german SIM to be able to participate, so sadly i will not be able to pull the update.zip file unfortunately, But i will try my BEST to keep the thread updated with the latest beta update.zip file (If/when someone pulls it)
Thank you
Click to expand...
Click to collapse
thanx for your job, please don't forget the Snapdragon one (G9750), If someone else can provide the update link too
No have S10.
ZmisiS said:
No have S10.
Click to expand...
Click to collapse
That's odd. What is this source?
add N10 plus snapdragon too please
Unlock and Root Galaxy M52 5G
I just share my experience. Do it at your own risk
Tested on M526BRXXU1AUK2 firmware
I. Unlock bootloader
1. Enable developer options by tapping build number 7 times
2. Go to Developer options, turn on OEM unlocking
3. Turn off phone, connect it to computer while holding Volume Up and Volume Down keys until you see the bootloader screen
4. Long-press Volume Up key to enter Device unlock mode
5. Press Volume Up key to confirm and unlock the bootloader
Done
II. Root
1. Unlock bootloader (skip this if you have done it)
2. (On PC) Extract boot.img.lz4 from Stock AP...tar file, then copy it to phone
3. (On phone) Install ZArchiver to extract boot.img from boot.img.lz4
4. (On phone) Install Magisk and patch the boot.img that you have just extracted from step 3
5. (On PC) Copy magisk_patched.img (in phone\download) to pc, rename it to boot.img
6. (On PC) Use 7zip to pack boot.img from step 5 into boot.tar
7. (On PC) Use odin to flash boot.tar from step 6 (in AP slot)
8. Phone will reboot to recovery, just wipe data factory reset then reoboot
Done
Yo, wondering if you have done this your self on your own samsung m52 5g. Does it work on android 13 and samsung m52 5g SM-M526BR/DS?
yes it works on m52 BR. many thanks
neviquatro said:
Yo, wondering if you have done this your self on your own samsung m52 5g. Does it work on android 13 and samsung m52 5g SM-M526BR/DS?
Click to expand...
Click to collapse
sure i tried myself with magisk delta
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Edit: thanks for the answers, when I buy this phone an root it I can let you know how it went.
lWanderingl said:
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Click to expand...
Click to collapse
there is no problem to root xiaomi device,because it can unlock BL
lWanderingl said:
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Click to expand...
Click to collapse
Hello , You can unlock bootloader then root your device easily with magisk , xiaomi devices are root friendly if you need any help lemme know i will do as much as i can
I would love a step-by-step, hold my hand type of tutorial. If some of you have spare time to do something good for the less capable brothers here, it will be great.
Yeah step by step Link would bei very helpful
Here is step-by-step tutorial
Step 1 Unlock bootloader (it will erase ALL YOUR DATA)
1) create and login in Mi account
2) go to settings>My device>All specs> click MIUI version several times
3) go to settings>additional settings>developer options> here enable OEM unlocking, usb debugging and link your Mi accont to phone
4) download latest MI unlock tool from official site https://en.miui.com/unlock/download_en.html and unzip the archive into a folder
5) download qualcomm usb drivers or launch driver_install_64.exe in downloaded MI unlock tool folder
6) launch miflash_unlock.exe and login in your MI account, hold power and volume down for 5-7 sec to boot in fastboot mode, connect phone to pc
7) try to unlock (it will say to wait 1-7 days and try again)
8) Voila, your phone unlocked and wiped
Step 2 flashing or booting TWRP
1) go to settings>additional settings>developer options> here enable usb debugging
2) download platform-tools https://developer.android.com/studio/releases/platform-tools
3) download TWRP https://mega.nz/file/USUjQR4D#g8_rCCouOcJLK4DrryIyHbE99dwP4Hj-T-XSBtoSx6Q
3) unzip the archive into a folder
4) put twrp-3.6.2_A12-diting-skkk.img in the same folder
4) run cmd (win+r and type "cmd")
5) type "cd path/to/folder" (if folder not on C drive run "DriveLetter:" for example "D:"
6) boot in fastboot and connect phone to pc
7) type "fastboot devices" your phone should appear
Method 1 flashing TWRP (recomended)
pros: easily accesible (just hold power and volume up for 5-7 sec)
cons: replaces original recovery
8) type "fastboot flash recovery twrp-3.6.2_A12-diting-skkk.img"
9) fastboot reboot
10) hold power and volume up for 5-7 sec)
11) install magisk (flash downloaded magisk.apk or zip in recovery)
Method 2 booting in TWRP (not recommended on this device, may cause bootloop)
pros: original recovery wont be replaced
cons: loads temporary recovery, once you booted system or disabled device TWRP will be erased
8) type "fastboot boot twrp-3.6.2_A12-diting-skkk.img"
9) install magisk (flash downloaded magisk.apk or zip in recovery)
GoldenWarriorM said:
Here is step-by-step tutorial
Step 1 Unlock bootloader (it will erase ALL YOUR DATA)
1) create and login in Mi account
2) go to settings>My device>All specs> click MIUI version several times
3) go to settings>additional settings>developer options> here enable OEM unlocking, usb debugging and link your Mi accont to phone
4) download latest MI unlock tool from official site https://en.miui.com/unlock/download_en.html and unzip the archive into a folder
5) download qualcomm usb drivers or launch driver_install_64.exe in downloaded MI unlock tool folder
6) launch miflash_unlock.exe and login in your MI account, hold power and volume down for 5-7 sec to boot in fastboot mode, connect phone to pc
7) try to unlock (it will say to wait 1-7 days and try again)
8) Voila, your phone unlocked and wiped
Step 2 flashing or booting TWRP
1) go to settings>additional settings>developer options> here enable usb debugging
2) download platform-tools https://developer.android.com/studio/releases/platform-tools
3) download TWRP https://mega.nz/file/USUjQR4D#g8_rCCouOcJLK4DrryIyHbE99dwP4Hj-T-XSBtoSx6Q
3) unzip the archive into a folder
4) put twrp-3.6.2_A12-diting-skkk.img in the same folder
4) run cmd (win+r and type "cmd")
5) type "cd path/to/folder" (if folder not on C drive run "DriveLetter:" for example "D:"
6) boot in fastboot and connect phone to pc
7) type "adb devices" your phone should appear
Method 1 booting in TWRP
pros: original recovery wont be replaced
cons: loads temp recovery once you booted system or disabled device TWRP will be erased
8) type "fastboot boot twrp-3.6.2_A12-diting-skkk.img"
9) install magisk (flash downloaded magisk.apk or zip in recovery)
Method 2 flashing TWRP (recomended)
pros: easily accesible (just hold power and volume up for 5-7 sec)
cons: replaces original recovery)
8) type "fastboot flash recovery twrp-3.6.2_A12-diting-skkk.img"
9) fastboot reboot
10) hold power and volume up for 5-7 sec)
11) install magisk (flash downloaded magisk.apk or zip in recovery)
Click to expand...
Click to collapse
Just confirming: in the TWRP page, the 12T Pro is not listed as a compatible device (https://twrp.me/Devices/Xiaomi/).
Will the provided version of the TWRP work? I would like to avoid boot loops or even a hard brick.
And, would Orange Fox work too? Could you point us the correct version?
TIA.
Just did as instructed and it works. Only bummer is that twrp is in Chinese. I did google a youtube video and followed instructions to change language. So far all good.
Do OTA updates still work after rooting? Or what is the process to upgrading once rooted?
GoldenWarriorM said:
7) type "adb devices" your phone should appear
Click to expand...
Click to collapse
You mean "fastboot devices", as it is already in fastboot
booting to recovery ended in error for me " FAILED (Status read failed (Too many links))" which led to bootloop.
I reflashed original ROM and I will try flashing.
flashing the recovery went as sharp as possible.
I do not recommend to boot into recovery before flashing it.
HValenti said:
flashing the recovery went as sharp as possible.
I do not recommend to boot into recovery before flashing it.
Click to expand...
Click to collapse
I didn't tried to boot without installing, I think there is a problem with A/B slots. On devices without B slot booting in TWRP should work as intended.
JF_Derzi said:
Will the provided version of the TWRP work? I would like to avoid boot loops or even a hard brick.
And, would Orange Fox work too? Could you point us the correct version?
TIA.
Click to expand...
Click to collapse
Provided version works on my device (Mi 12T Pro, Global ROM). Hardbrick is impossible if flashing TWRP in recovery partition.
I didn't found compatible Orangefox recovery
There are 3 versions of TWRP:
BOOT:
Command:
fastboot boot twrp.img
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP
REC:
Update with existing TWRP.
gold
CMD
fastboot flash recovery_ab twrp.img***
powershell
./fastboot flash recovery_ab twrp.img***
BOOT REC:
Both methods
On this thread the proposed version is REC.
***Remove lock screen security and reboot to decrypt data then install TWRP.
Reboot with the buttons combination and not with a fastboot command
Update REC
twrp-3.7.0_12-v6.5_A12-diting-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
Spoiler: Change languages
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then reboot TWRP
No need TWRP for Rooting
Root:
1. Find or redownload the TGZ file for your current ROM
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
Xiaomi 12T Pro
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
Pass SafetyNet without Magisk Hide Props Config and
How to Hide Root from Apps via Magisk DenyList [Android 13]
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
HValenti said:
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/#METHOD_2_Pass_SafetyNet_without_Magisk_Hide_Props_Config_NEW and
https://www.droidwin.com/how-to-hide-root-from-apps-via-magisk-denylist/
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
Click to expand...
Click to collapse
Try island app on Google play
HValenti said:
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/#METHOD_2_Pass_SafetyNet_without_Magisk_Hide_Props_Config_NEW and
https://www.droidwin.com/how-to-hide-root-from-apps-via-magisk-denylist/
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
Click to expand...
Click to collapse
Maybe you have already tried this (your links don't work):
magisk/settings/hide Magisk, renaming it..
Zygisk enable/enforce exclusion list enable.
Configure exclusion list / display system apps / check those related to your problem.
Reboot.
NOSS8 said:
Maybe you have already tried this (your links don't work):
magisk/settings/hide Magisk, renaming it..
Zygisk enable/enforce exclusion list enable.
Configure exclusion list / display system apps / check those related to your problem.
Reboot.
Click to expand...
Click to collapse
Yes I have done all of this. Links have been fixed.
tavocabe said:
Try island app on Google play
Click to expand...
Click to collapse
I don't think I can isolate Google Pay/Wallet, but I will try it.