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.
Related
I'm just going to leave this here in case anyone of you encounters this problem after modifying files in the system or after flashing custom ROMs. Do note that this fix does not remove the error, but instead bypasses it (for those without EFS backup) and enables the system to boot up normally (installs SuperSU as well). Also, as this requires the use of Odin, devices running MacOS or OSX are not supported.
An alternative (and easier) method has been discovered (refer to post #4 for more details)
Prerequisites:
1) TWRP recovery (https://drive.google.com/open?id=0B6QXDUz9wzc9YWcyZklybmZLc0k)
2) dm-verity bypass (https://drive.google.com/open?id=0B6QXDUz9wzc9Wk1ra0hKYVJtT1k)
3) Odin (https://drive.google.com/open?id=0B6QXDUz9wzc9c3BxYzdBNXhvbnc)
Steps (please follow the steps accordingly in order):
1) Place your phone in D/L mode
- Ensure device is fully turned off by pressing the volume down and power button
- Hold the volume down, home, and power button until a blue warning screen appears
- Press once on the volume up button
- Connect your device to your computer
2) Flash TWRP onto your device
- Open Odin and click on the "AP" tab, and then directing to the location of the TWRP recovery (TWRP_3.0.2.tar)
- Click on the "Options" tab and untick the option "Auto Reboot" [DO NOT TICK ANYTHING ELSE]
- Click on "Start" until Odin says "PASS!"
3) Reboot device into TWRP and flash the bypass zip
- Hold the volume down and power down button until the screen turns off
- Then, hold the volume up, home, and power button until "Set Warranty Bit : recovery" appears at the top of the screen
- Click on "Advanced", followed by "ADB Sideload" and ensure that "Wipe Dalvik Cache" and "Wipe Cache" is ticked, then swipe the bar at the bottom to start sideload
- Using the command prompt, type "adb sideload dm-verity bypass.zip" and wait till it completes
- Click on "Reboot System" after it completes, and your system should be able to boot
Possible errors which you may have encountered:
1) Odin does not detect my device
-- [You will need to install the device driver]
> Download the driver at https://drive.google.com/open?id=0B6QXDUz9wzc9LU9FclQ5WjNWRFk and install it.
2) My device does not boot into recovery after flashing via Odin
-- [System was trying to boot instead of recovery and had ignored the custom recovery after that]
> Go back to step 1) and repeat again
What is ADB and where can I get it?
> The installer is available for download at https://drive.google.com/open?id=0B0MKgCbUM0itNVB1elljU2NPR0k
> Run the installer and type "Y" for every prompt
> Open the command prompt (On your keyboard, press the windows key followed by the "R" key, then type "cmd" in the window and press enter
> Type "cd C:\adb" and you may continue with the steps (do note that C: is the mounted letter of your root drive which may be different from yours)
"* cannot read 'dm-verity bypass.zip *" appears after I entered the command
-- [ADB cannot read the file as the file cannot be found]
> Copy the dm-verity bypass.zip into your ADB folder, or after typing "adb sideload ", drag the dm-verity bypass.zip into your command prompt window and then pressing enter.
Do notify me immediately if there are any errors. Thank you and good luck!
Thanks to @KingWilliams for the dm-verity bypass zip which was present in one of your ROMs.
Q&A
Will OTA updates still work?
> No, the phone will detect that files has been modified and thus OTA updates are stopped. Updates will have to be carried out manually.
NIce Info Thanks, btw is it work on Marshmallow or Lollipop j500f ?
NIce Info Thanks, btw is it work on Marshmallow or Lollipop j500f
Click to expand...
Click to collapse
Should work on both versions but would you mind trying out a simpler and better method instead? It works fine on my device but I am unsure if it works on other models/variants. This method keeps the system status official and even enables OTA updates.
The guide below encompasses the updated method. Do note that as the guide is still being tested and is not an official method, I am assuming that all necessary drivers are installed correctly on your computer and that you have the knowledge and experience to work through the steps as these prerequisites are not included in this guide.
1) Download SamFirm (https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462), extract and then run the application.
2) After checking the "Auto" and "Binary Nature" box, type in your model (in your case, SM-J500F) and your region (refer to http://samsung-updates.com/device/?id=SM-J500F if you need help identifying your region) before clicking on "Check Update".
2.1) The application should now be able to detect a firmware saying (for example)
Code:
SamFirm v0.3.6.0
Checking firmware for SM-J500F/TGY/J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
Model: SM-J500F
Version: J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
OS: Lollipop(Android 5.1.1)
Filename: SM-J500F_1_20161018133014_hz4nve666g_fac.zip.enc4
Size: 1060126192 bytes
LogicValue: 0us57tdgetwzs2jy
3) Before clicking on "Download", ensure that the option "Decrypt automatically" is checked. The "Check CRC32" option is optional.
4) Once the application is done downloading and decrypting the firmware image, extract it.
5) Using Odin, flash BL, AP, CP, CSC and once it reboots and the error pops up, boot the phone back to the Download Mode.
6) Using Odin, flash AP only (untick BL, CP and CSC checkboxes).
The phone should now boot up normally into the system. Do report the results here for further analysis. Thank you!
Thanks mate, i'll try it :highfive:
Rizzed said:
Should work on both versions but would you mind trying out a simpler and better method instead? It works fine on my device but I am unsure if it works on other models/variants. This method keeps the system status official and even enables OTA updates.
The guide below encompasses the updated method. Do note that as the guide is still being tested and is not an official method, I am assuming that all necessary drivers are installed correctly on your computer and that you have the knowledge and experience to work through the steps as these prerequisites are not included in this guide.
1) Download SamFirm (https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462), extract and then run the application.
2) After checking the "Auto" and "Binary Nature" box, type in your model (in your case, SM-J500F) and your region (refer to http://samsung-updates.com/device/?id=SM-J500F if you need help identifying your region) before clicking on "Check Update".
2.1) The application should now be able to detect a firmware saying (for example)
Code:
SamFirm v0.3.6.0
Checking firmware for SM-J500F/TGY/J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
Model: SM-J500F
Version: J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
OS: Lollipop(Android 5.1.1)
Filename: SM-J500F_1_20161018133014_hz4nve666g_fac.zip.enc4
Size: 1060126192 bytes
LogicValue: 0us57tdgetwzs2jy
3) Before clicking on "Download", ensure that the option "Decrypt automatically" is checked. The "Check CRC32" option is optional.
4) Once the application is done downloading and decrypting the firmware image, extract it.
5) Using Odin, flash BL, AP, CP, CSC and once it reboots and the error pops up, boot the phone back to the Download Mode.
6) Using Odin, flash AP only (untick BL, CP and CSC checkboxes).
The phone should now boot up normally into the system. Do report the results here for further analysis. Thank you!
Click to expand...
Click to collapse
excuse me, i've tried this method but when i boot the phone to the recovery mode, an error message still show (Device does nit have DRK (Device Root Key), contact to SW PL please flash ENG binary then install DRK), any suggestion ?
dv6661 said:
excuse me, i've tried this method but when i boot the phone to the recovery mode, an error message still show (Device does nit have DRK (Device Root Key), contact to SW PL please flash ENG binary then install DRK), any suggestion ?
Click to expand...
Click to collapse
Sorry about that and for wasting your time. In my original thread, I stated that this method does not eradicate the problem completely but simply bypasses it. The guide that I had requested you to try had two differences - sets the system status to official and enables OTA updates. Now that I think of it, this method is only useful for devices that does not have a workable TWRP/CWM recovery yet, or to give people a peace of mind that their system is official and unmodified. Since entering the recovery mode resurfaces this problem , this method is more or less useless as OTA updates are installed in recovery mode. All updates would need to be done manually via Odin/Smart Switch.
You got to admit this method is simpler and easier though! Could I ask does this method work? Did your phone boot up normally? Thank you.
Rizzed said:
Sorry about that and for wasting your time. In my original thread, I stated that this method does not eradicate the problem completely but simply bypasses it. The guide that I had requested you to try had two differences - sets the system status to official and enables OTA updates. Now that I think of it, this method is only useful for devices that does not have a workable TWRP/CWM recovery yet, or to give people a peace of mind that their system is official and unmodified. Since entering the recovery mode resurfaces this problem , this method is more or less useless as OTA updates are installed in recovery mode. All updates would need to be done manually via Odin/Smart Switch.
You got to admit this method is simpler and easier though! Could I ask does this method work? Did your phone boot up normally? Thank you.
Click to expand...
Click to collapse
yes my phone just boot up normally, the only problem is when i entering recovery mode there's a message "dm-verity need to check verification failed drk first"
i fixed it by mount /system and it worked on j500f .
s10gopal said:
i fixed it by mount /system and it worked on j500f .
Click to expand...
Click to collapse
Are you sure about that? This error only appears when the /efs partition is corrupted.
100%
https://source.android.com/security/verifiedboot/
s10gopal said:
100%
https://source.android.com/security/verifiedboot/
Click to expand...
Click to collapse
Will test it out later on my device.
I have a question. Can I take a DRK backup from one phone and repair another? I have a working Galaxy S6 64gb, and a Galaxy S6128GB that has DRK issue.
Can't Flash TWRP, FRP lock :/
Hi, I have the dm-verification failed problem, but I can't flash twrp because of the FRP lock. Any solution? thanks
_ale33_ said:
Hi, I have the dm-verification failed problem, but I can't flash twrp because of the FRP lock. Any solution? thanks
Click to expand...
Click to collapse
Got to developer settings and tap oem lock on and it should fix your problem.
Hello.
My phone is a Samsung Note 5. 64gb, SM-N9208 ( Taiwan ).
Many many thanks for this post! I have trawled the net for weeks and weeks to find a solution for this ridiculous dm-verity, DRK missing fiasco. I have managed to fix it thanks to your instructions. I understand that this is a work around, don't mind that one bit! But should anyone have a solution to get rid of the problem permanently, you will be an even bigger hero. Let me know if anyone does. Best Regards. Ian.
JaanZZ said:
Got to developer settings and tap oem lock on and it should fix your problem.
Click to expand...
Click to collapse
there's a problem, a mobile go backup sent the device in bootloop, can't boot, only stock recovery or download mode available and i need to backup sensible data.
witty2309 said:
Hello.
My phone is a Samsung Note 5. 64gb, SM-N9208 ( Taiwan ).
Many many thanks for this post! I have trawled the net for weeks and weeks to find a solution for this ridiculous dm-verity, DRK missing fiasco. I have managed to fix it thanks to your instructions. I understand that this is a work around, don't mind that one bit! But should anyone have a solution to get rid of the problem permanently, you will be an even bigger hero. Let me know if anyone does. Best Regards. Ian.
Click to expand...
Click to collapse
Glad that I could help. I suppose you used the TWRP method to recover your device?
_ale33_ said:
there's a problem, a mobile go backup sent the device in bootloop, can't boot, only stock recovery or download mode available and i need to backup sensible data.
Click to expand...
Click to collapse
Perhaps the system files are corrupted. Try flashing the AP file (not HOME file) in Odin and you should be good to go.
Jamessr79 said:
I have a question. Can I take a DRK backup from one phone and repair another? I have a working Galaxy S6 64gb, and a Galaxy S6128GB that has DRK issue.
Click to expand...
Click to collapse
Really sorry for the late reply but in case you have not found an answer yet, no it's not possible (even if it is possible it would be considered illegal - duplicate IMEI).
So i recently bought my Samsung galaxy A 10 ,I have been trying to root it but no luck.i unlocked the bootloader, installed proper adb drivers and latest version of odin on my Pc. I was following procedures from rootmydevice.com slash root-samsung-galaxy-A10(sorry cant post external links, im new).evrything went fine up until i got to the flashing part using odin. I am not sure weather the twrp file is corrupt or I am missing something.anyone who might know please help.
here is my device info:
SM-A105F
Have you tried this tutorial:
https://forum.xda-developers.com/galaxy-a30/how-to/root-galaxy-a30-magisk-canary-relaese-t3936481
I'm stuck in two problems here...
1- I dont have the option OEM Unlock on my developers option. I think that it maybe because ive checked that option before and after that it desapeared... When entering on download mode, it shows OEM Lock: ON (L), i dont know if that means OEM is unlocked or locked...
2- I cant find the files in step 2: .extract the boot.img.lz4 from the AP file.
Just came here to find a root method for the SM-A105M. Seems like not a lot of love for the A10 here.. Lol Anyways, I will be testing this method I came across out tonight. I will post the link but can't confirm it's working. I'll post my results tomorrow.
https://rootmydevice.com/root-samsung-galaxy-a10/
Sassiest said:
Just came here to find a root method for the SM-A105M. Seems like not a lot of love for the A10 here.. Lol Anyways, I will be testing this method I came across out tonight. I will post the link but can't confirm it's working. I'll post my results tomorrow.
https://rootmydevice.com/root-samsung-galaxy-a10/
Click to expand...
Click to collapse
do not flash that recovery is for sm-a720f aka A7 2017 https://www.gsmarena.com/samsung_galaxy_a7_(2017)-8335.php
hanonicaro said:
Have you tried this tutorial:
https://forum.xda-developers.com/galaxy-a30/how-to/root-galaxy-a30-magisk-canary-relaese-t3936481
I'm stuck in two problems here...
1- I dont have the option OEM Unlock on my developers option. I think that it maybe because ive checked that option before and after that it desapeared... When entering on download mode, it shows OEM Lock: ON (L), i dont know if that means OEM is unlocked or locked...
2- I cant find the files in step 2: .extract the boot.img.lz4 from the AP file.
Click to expand...
Click to collapse
Hi everybody,
I managed to root my A105FN with this method but with using the Magisk Manager v7.3.1 (no need of Magisk Canary)
It will be good to have a TWRP as welll but couldnt find a compatible one for the A10 (maybe useful for no-verity-opt-encrypt-6.0 and RMM-State_Bypass_Mesa_v2 patch)
we need :
1. odin 13.3.1
2. official firmware for your device (to get the boot.img from AP_xxxx part => follow the other tutorial how to get boot.img and boot.tar magisk patched)(keep an original boot.tar, just in case stuck at boot)
3. 7zip ZS
4. Last Magisk Manager (for me was v7.3.1)
5. computer + usb cable
Warning : this root will give you big warning messages at every boot !
First you need to unlock your bootloader :
1/Under android, activate internet and go under "Developper Mode" (Setting>About>Software>Build Number and Tap on the build number repeatedly). OEM unlock option should be there.
If not wait and retry to see if there ... (needs internet, dont know why)
2/Then go under Recovery Mode (VolUp + Power at phone boot). No method to go "Download Mode" directly for my device.
3/Under Recovery, we need to unlock the bootloader as well. I cant remember what exactly I pressed but try to press VolUp or VolUP+VolDown just after you click to reboot under bootloader... It should show you a page where you can choose to unlock bootloader by long pressing VolUP. if you dont have it, retry again ... without that no Flash possible.
Warning : this unlock will give you a big warning at every boot !
4/if you managed to unlock the bootloader, it s almost finished... know under Download Mode with bootloader unlock, flash with Odin the magisk patched boot.tar. Do not forget to untick "reboot" under Odin.
(reminder:follow the other tutorial to get the file and remember to use the Magisk Manager v7.3.1 and not the canary.)
5/when flash done, reboot by pressing VolDown+Power then immediately on reboot VolUp to go under Recovery Mode.
6/Under Recovery, erase data/factory reset and reboot to system
(7/I dont know if it s necessary the VolUp at reboot till the vibration)
8/wait the booting ... if you are stuck on the warning page for a long time, retry to reflash the original boot.tar and restart from "1/"
9/if you managed to boot under android, good news you are rooted but it s not finished yet....
Under Android check you have "OEM unlock option" under Developper Mode (cf. 1/) otherwise at the reboot the system will go KO.
So when you have "OEM unlock" enabled you can install Magisk Manager. It will ask you to install something and it will reboot automatically. That s why check you have "OEM unlock" enabled before doing that !
10/After reboot, Done. ROOTED.. enjoy ! you can reboot as you want ...
Hi everybody
Yes, I facing same everyone's problem, I see on "download mode" it's show "OEM Lock: On (L)" I try all the ways to unlock in YouTube but no any method to unlock
I try to unlock with all tools I have but useless (my tool: Z3X, Miracle box, MCT Dongle , NCK Dongle, Octopus Suite Unlock, Samkey Unlock Crack)
I try to flash Custom Rom with Odin , Try to Install "Magisk" and "TWRP" by method in many website , it's useless at all
However I think I need to unlock OEM first but I can't because OEM not show in the developer option
I try all the ways to appear the OEM Unlock toggle by a changing date, Flash tar.md5, factory reset in many website it's can't help me
Samsung developer very strong and can't hacking to "OEM Lock : On (L)" on Android Pie 9.0??
1.power off device
2.while press and hold vol+ and vol- plug the data cable with pc
3.then warning screen apper
4.volume up long press.
5.then press volume up.
bootloader will unlocked!
*sorry for my bad english
keepfun said:
Hi everybody,
er Download Mode with bootloader unlock, flash with Odin the magisk patched boot.tar. Do not forget to untick "reboot" under Odin.
Everything is about having this flash file you said you used. Please send us the link for that twrp file or whatever it is called right now as it is maybe not a Team Win Rom.
Thank you for your help
Click to expand...
Click to collapse
Hi,
It is not a TWRP file, it is the boot.img file from the original firmware for A10, patched with Magisk to access the root function, unfortunately it does not work, have tested it.
Benjamin.L said:
keepfun said:
Hi everybody,
er Download Mode with bootloader unlock, flash with Odin the magisk patched boot.tar. Do not forget to untick "reboot" under Odin.
Everything is about having this flash file you said you used. Please send us the link for that twrp file or whatever it is called right now as it is maybe not a Team Win Rom.
Thank you for your help
Click to expand...
Click to collapse
Click to expand...
Click to collapse
IneedFiveMore said:
Yes, I facing same everyone's problem, I see on "download mode" it's show "OEM Lock: On (L)" I try all the ways to unlock in YouTube but no any method to unlock
I try to unlock with all tools I have but useless (my tool: Z3X, Miracle box, MCT Dongle , NCK Dongle, Octopus Suite Unlock, Samkey Unlock Crack)
I try to flash Custom Rom with Odin , Try to Install "Magisk" and "TWRP" by method in many website , it's useless at all
However I think I need to unlock OEM first but I can't because OEM not show in the developer option
I try all the ways to appear the OEM Unlock toggle by a changing date, Flash tar.md5, factory reset in many website it's can't help me
Samsung developer very strong and can't hacking to "OEM Lock : On (L)" on Android Pie 9.0
Click to expand...
Click to collapse
If you have an US variant of the A10, don't expect TWRP to work on your device.
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?
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/
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.