Root Samsung Galaxy A52 SM-A525F Android 11 Official - AUC4 Firmware. TWRP Recovery for Galaxy A52 Android 11 does not available yet when I posted this rooting guide. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Rooting Instructions ( Don't make mistake )
Make sure the bootloader are unlocked, OEM unlock option is grey out
Patch boot.img then Pack it to magisk_patched.tar. If you don't want to do it by your self, you can download it from link below
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN
Insert magisk_patched.tar in AP, then click start. The phone will rebooting to ANDROID RECOVERY MODE
in ANDROID RECOVERY, Select Factory data reset and press power key to confirm
select 'Factory data reset' again and confirm
Setup the phone
Connect to Internet
Install and Open Magisk App, it will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Download
magisk_patched
Telegram: https://t.me/SamsunGalaxyA52
Watch This Video Tutorial
Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.
Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?
<deleted>
VonSparq said:
Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?
Click to expand...
Click to collapse
On qcom devices, not really. Even on exynos devices after removing that you still need to physically press the power button or if you don't wanna even do that you have to w8 bout 10 to 15 extra seconds..
hansxl said:
Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.
Click to expand...
Click to collapse
Okay, solved. Flashed latest firmware (AUC5) and patched boot.img with Magisk. Fingerprints works now and no reboots so far
Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?
Rerel14 said:
Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?
Click to expand...
Click to collapse
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com
hansxl said:
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?
Rerel14 said:
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?
Click to expand...
Click to collapse
Yes, it's more or less the procedure. But I would just download the latest magisk (22.1) from
Magisk v22.1 brings an improved log writer, resetprop bootloop fixes, and much more
The latest stable update for Magisk (v22.1) has been released with tons of bug fixes and feature improvements. Read on to know more!
www.xda-developers.com
the UI is a bit different from the one in your video
My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?
Rerel14 said:
My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?
Click to expand...
Click to collapse
bootloader unlocked
hansxl said:
bootloader unlocked
Click to expand...
Click to collapse
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?
Rerel14 said:
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?
Click to expand...
Click to collapse
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also
hansxl said:
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also
Click to expand...
Click to collapse
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?
I think I found one :
Rerel14 said:
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?
Click to expand...
Click to collapse
How To Unlock Samsung Galaxy A52 Bootloader - NaldoTech
In this tutorial, you will learn how to unlock the bootloader on your Samsung Galaxy A52. A bootloader is the piece of code that runs before the operating
www.naldotech.com
don't forget to backup your data. I think after unlocking bootloader your phone will return to factory settings
I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?
I installed Magisk from an other source and eventually I succeeded to get root !
Huge thanks Hansxl for your help and patience. Really appreciated it.
Last question : if I update the firmware I'll need to make the full procedure described above again ?
Rerel14 said:
I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?
Click to expand...
Click to collapse
deinstall magisk and install magisk again
Related
Greetings from the AT&T S5 Forum!
We've recently discovered the usability of engineering firmwares in our journey to get root, as outlined here: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
Now, I'm here to try to bring this same method to you guys! With the help of @jrkruse, here are the root instructions:
How it works:
These engineering firmwares are usually based on KitKat, and have their SELinux set to PERMISSIVE. This not only leaves the firmware very vulnerable to towelroot, but it also keeps SELinux from raining on our parade.
Thanks again to @jrkruse for the updated root instructions, and @mohammad.afaneh for the Safestrap!
Revised October 6, 2018.
Directions:
Before you get going, use this APK to check your eMMC chip's CID:
eMMC_CID_Checker_.apk[/SIZE][/B][/CENTER]
Your CID Number will be the first two numbers in the eMMC Box under "CID"
If the first two digits are "15," your bootloader is unlockable and you can install TWRP/AOSP ROMs.
If the first two digits are "11," your bootloader is not unlockable, but you can use rooted Lollipop ROMs that are based on TouchWiz (with the help of SafeStrap). You can also use non-rooted Marshmallow ROMs (based on TouchWiz) and flash mods with SafeStrap.
BACK UP YOUR STUFF NOW, YOUR STORAGE WILL BE WIPED!
If your eMMC CID starts with "15," start here:
1. Download and unzip this file: EMMC_15_Root_Bootloader_Unlock S5_QB2_PB1.zip
2. Reboot the phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the "COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5" firmware in the AP Slot
4. Flash and let the phone process the file. It will reboot twice and you should be dropped into Android within a minute and a half.
5. Copy the following files to your phone:
"RootS5" Folder and "EMMC_15_SafeStrap_QA1_6_0_1_MM_Bootloader_Unlock_AIO.zip",
and EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery choose install and select EMMC_15_SafeStrap_QB2_6_0_1_MM_Bootloader_Unlock_AIO.zip
13. Install the zip. The phone will power off. Reboot the phone to TWRP Recovery with Pwr+VolUp+Home
14. You will now have an Unlocked Bootloader and TWRP recovery Installed. Now whoose Wipe > Advanced Wipe. Select Dalvik Cache; Data; System; Cache, and swipe the swipe to wipe bar. When done, click the back button, click Install, and choose:
EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
You're done! You will have stock rooted Marshmallow QB2 Build installed with an unlocked bootloader and custom recovery.
If your eMMC CID starts with "11," start here:
1. Download and unzip this file: EMMC_11_ Root S5_QB2_PB1.zip
2. Reboot Phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot.
4. Flash and let the phone reboot. It will reboot to recovery and finish install then it will reboot and take about 20 seconds to boot.
5. Copy the following to the phone:
Root S5 Folder, EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip, and the TouchWiz ROM you want to install.
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery, choose what firmware you want to be on:
Lollipop 5.0 Firmware=EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip
Marsmhallow 6.0 Firmware=EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip
13. Install the firmware zip, and then flash a TouchWiz Lollipop ROM. (Here is the latest stock rooted Lollipop Rom: VZW_BPB1_ODEX_DEODEX_V9.zip). You may want to download a copy of the latest SuperSu zip, and flash if installing a Lollipop ROM that is not rooted. Remember that you cannot root Marshmallow ROMs, so do not try and flash the SuperSu zip on a Marshmallow Rom (you will softbrick if you do).
14. After you install any Lollipop ROM, you may need to reinstall SafeStrap Recovery. Most of the time you don't have to and SafeStrap can be reached by flashing the KitKat Kernel in Download Mode with ODIN. But, in some cases, when flashing a ROM that flashes a system.img instead of a system folder, you may lose SafeStrap during install. This will be the case if you install the above ROM. You can reinstall it after the ROM is booted up. A Safestrap-G900V-4.04_LL_MM.apk is included that will flash a version of SafeStrap that will allow you to reboot to SafeStrap Recovery without flashing a KitKat kernel in Odin. Install BusyBox again from the BusyBox App in the RootS5 Folder. Install Safestrap-G900V-4.04_LL_MM.apk and make sure to grant SuperSU access. It may take a few seconds to prompt. If SafeStrap is not installed, click "Install Recovery". If Safestrap is still installed click on "Uninstall Recovery", close the app, and reopen it. It should say recovery is not installed. Now click on "Install Recovery". If this doesn't work, reboot the phone and try again. Once installed, you can just click reboot to SafeStrap from the SafeStrap app and you will reboot straight to SafeStrap. Remember to flash the appropriate Kernel when leaving SafeStrap!
Download and place these on your device:
LL_KERNEL_SS-FF_Flashable.zip, and
MM_KERNEL_SS-FF_Flashable.zip
If something goes wrong you can usually get back to SafeStrap by simply rebooting the phone to Download Mode and flashing NI2_stock_kernel.tar.md5. When the phone reboots, watch for the SafeStrap splash screen and enter SafeStrap.
WARNING: Do NOT change ANY boot options in SafeStrap. ROM slots cannot be used, so you must flash to the Stock ROM slot EVERY TIME OR YOU WILL SOFTBRICK. Some functions don't work in SafeStrap, like choosing an image file to flash directly. All image files must be flashed via zip file.
For CID11 users that have followed the above instructions and want to use Marshmallow:
QA1_MM_Firmware_With_QA1_Bootloader_CAUTION.zip=Marshmallow Firmware (use if flashing a MM TW ROM other than the one posted below). Just remember there is no root for Marshmallow ROMs, but having SafeStrap installed gives you the ability to do things like flash debloat Scripts, Mods, etc and the ability to go back to a rooted Lollipop ROM without going through the root process all over again. Simply flash the Lollipop ROM and EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip.
Here is a special ROM that includes SafeStrap, so you can flash a Marshmallow ROM and still be able to use SafeStrap to flash things. You will not have root but you can still access SafeStrap. VZW_QB2_STOCK_SAFESTRAP_ONLY_V1.zip More Instructions about this can be found HERE
When using a MM ROM, it is necessary to flash the KitKat Kernel with Odin to enter SafeStrap. When leaving SafeStrap, make sure to flash MM_KERNEL_SS-FF_Flashable.zip which is necessary to leave SafeStrap (This zip will be placed on storage automatically with the above ROM and you also download it in instructions above.) Just navigate to the .MM_KERNEL_SS-FF folder located on both Internal and External storage.
i'll odin my spare s5 to stock later if i get the chance and let you know if this works on my g900v.
The methods in post 1 are seriously outdated the easiest method to obtain unlocks or update or downgrade unlocked bootloaders can be found below they were updated December of 2021
EMMC 15 Unlocking Bootloader
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
EMMC 15 Updating Unlocked Bootloaders Or Downgrading
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
For Rooting EMMC 11 Phones
2021_VZW_Locked_Bootloader_EMMC_11_Rooted/NonRooted_Roms_With_Safestrap_MM_LL_KK
This Process Will Install On The EMMC_11 Locked Bootloader Verizon S5 Marshmallow QL1 Stock Rom NonRooted With Safestrap. Lollipop PB1 Stock Rom Rooted With Safestrap. KK Rom Rooted With Safestrap What This Does This gives you the ability to...
forum.xda-developers.com
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
its uploading sorry it failed at 99 percent
jrkruse said:
its uploading sorry it failed at 99 percent
Click to expand...
Click to collapse
Thank you! very much appreciated
jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
Its uploaded
jrkruse said:
Its uploaded
Click to expand...
Click to collapse
Downloading as we speak. I will let you know how everything goes!
tested on one of the spares I had kicking around
does what it says on the tin
!kickass
The apps are kind of hard to see in the App Drawer I installed View attachment Apex_Lancher.apk and it gets rid of that Info screen covering the Apps
The OP has been updated to reflect @jrkruse 's new instructions
AptLogic said:
The OP has been updated to reflect @jrkruse 's new instructions
Click to expand...
Click to collapse
I just cleaned them up a little I'll Pm you the changes
---------- Post added at 08:22 PM ---------- Previous post was at 07:32 PM ----------
jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.
jrkruse said:
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.
Click to expand...
Click to collapse
Which, I should add, has about a 1 in 10,000,000 chance of occurring.
I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used: (one linked in original thread)
http://org.downloadcenter.samsung.c...NG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe
guitar1238751 said:
I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used:
Click to expand...
Click to collapse
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.
AptLogic said:
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.
Click to expand...
Click to collapse
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.
guitar1238751 said:
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.
Click to expand...
Click to collapse
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.
AptLogic said:
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.
Click to expand...
Click to collapse
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks
guitar1238751 said:
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks
Click to expand...
Click to collapse
Happy to help
["QUOTE=AptLogic;71212479]Happy to help [/QUOTE]
A simple guide for users which will help them to install TWRP on their S8 after Oreo Update.
This guide is only for Exynos models.
Requirement -
1. PC/Laptop
2. Original Samsung USB Type-C Cable
3. Prince Comsy Odin (Because some users reported on this thread that normal Odin doesn't work)
Instructions -
1. Backup your important data from internal storage before proceeding towards the installation.
2. Now go to Settings - About Phone - Software Information - Tap On Build Number 7 Times.
3. Now come back to Settings Home and Open Developer Options. Check OEM Unlock is turned ON.
4. Power off device and boot into download mode.
5. Connect your device to the PC/Laptop.
6. Now Open Prince Comsy Odin and click on the AP option.
7. Choose the TWRP .tar file and press the START button.
8. Now after Odin says PASS, press the VOLUME UP, BIXBY KEY, and POWER BUTTON at the same time until device boots into TWRP recovery.
9. Now allow the modifications and go to WIPE option.
10. Choose FORMAT DATA - Type yes - ENTER.
11. Just Reboot Once Into Recovery Once.
12. Flash no-verity-opt-encrypt.zip.
12. Now Choose INSTALL option and install Magisk or SuperSU.
13. Done!
You can also refer to this video for installation of TWRP - https://www.youtube.com/watch?v=2SqgHFcHLMw
Downloads -
Latest TWRP For Exynos S8 - TWRP 3.2.1-0-DREAMLTE
Prince Comsy Odin - https://drive.google.com/open?id=1enVG5a_ocyjhRlta8AX_0b7LLoHWciVU
No dm-verity - https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Magisk - https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
SuperSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Credits -
@jesec for TWRP
@topjohnwu for Magisk
@Chainfire for SuperSU
Prince Comsy Odin
The main problem is that most users dont have oem unlock after oreo update (e.g me)
EugenStanis said:
The main problem is that most users dont have oem unlock after oreo update (e.g me)
Click to expand...
Click to collapse
Flash this official firmware through Odin if you have Exynos S8, and you'll get OEM unlock option.
I also manually updated to Oreo through this firmware and not through OTA. Also, note that flashing this will not wipe any of your existing data and also will not trip your knox
Ruturaj Kadam said:
Flash this official firmware through Odin if you have Exynos S8, and you'll get OEM unlock option.
I also manually updated to Oreo through this firmware and not through OTA. Also, note that flashing this will not wipe any of your existing data and also will not trip your knox
Click to expand...
Click to collapse
Flashed official XEO for Poland and still OEM unlock isnt there :/
Does the Oreo update affect the the locked bootloader on the Snapdragon version? I thought it was impossible to install TWRP on the Snapdragon versions of the S8?
I have installed but now shows me 0 mb on inernal sotorage , ive tried to change data but nothing cant mount sdcard
EugenStanis said:
Flashed official XEO for Poland and still OEM unlock isnt there :/
Click to expand...
Click to collapse
Try use AQK7 ( 4 file firmware + re-partition PIT)
In my case I 100% success returned form CRAP to AQK7.
OEM unlock is in dev settings, no RMM and FRP.
Powodzenia ^_^
I'm guessing this is not for the US snapdragon variant.
There's no way this can work on US Snapdragon, we don't have a OEM unlock option here.
Tired of the US locked bootloaders.
Next time I'll get a Exynos GS9 for sure.
Will822 said:
I'm guessing this is not for the US snapdragon variant.
Click to expand...
Click to collapse
I'm sorry! It was one of my friends who told me the method is same. I'm sorry again. OP edited
iamnotexisting said:
There's no way this can work on US Snapdragon, we don't have a OEM unlock option here.
Click to expand...
Click to collapse
I'm sorry for that! Edited the OP! Got misguided due to one of my friends
Silenus21 said:
Tired of the US locked bootloaders.
Next time I'll get a Exynos GS9 for sure.
Click to expand...
Click to collapse
Haha yes! Exynos devices are best in performance and battery too.
This method trip knox? I can still use Samsung Pay and other features that require Knox to not be tripped?
168 hours Open my device oem lock on of after twrp flash data storage 0 dm verity flash wipe data
thiagomed said:
This method trip knox? I can still use Samsung Pay and other features that require Knox to not be tripped?
Click to expand...
Click to collapse
TWRP trips Knox if I'm not mistaken.
i did this guide and everything is went good but when i restarted the phone it went to a softbrick and i had to do a restore...
the error was something on the original binary
to have the OEM option, will I have to go back to crap?
I have just tried this method and booted into TWRP but the screen was totally unresponsive, rebooted and still the same. I had to go back to Oreo.
How do I get around this problem?
dr.vetony said:
I have installed but now shows me 0 mb on inernal sotorage , ive tried to change data but nothing cant mount sdcard
Click to expand...
Click to collapse
Wipe / format data - " yes"
How to Flash Factory Firmware
Warning
You will loose all your data. Make sure to backup. You are doing this at your own risk. Neither me nor xda is responsible for any bricked devices.
Youtube Video :- https://www.youtube.com/watch?v=eCGB-yxC09w
Text Guide
HOW TO INSTALL STOCK ROM IN MOTO X4:
Download Moto X4 Stock Firmware from below (in factory firmwares section).
Extract factory firmware to a folder.
Install Motorola Driver and ADB Fastboot Driver on your PC.
Copy all contents of ADB fastboot folder and paste it in factory firmware folder.
Download flash-all.sh(Mac & Linux) or flash-all.bat (Windows)
Place flash-all.sh/flash-all.bat file in factory firmware folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt/terminal window, navigate to factory firmware folder.
Windows
Code:
fastboot devices
Mac & Linux
Code:
./fastboot devices
Make sure device is detected in fastboot mode.
Windows
Code:
flash-all.bat
Mac & Linux
Code:
./flash-all.sh
Once everything is flashed.
Windows
Code:
fastboot reboot
Mac & Linux
Code:
./fastboot reboot
Motorola Bootloader Unlock - https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Downloads
Motorola drivers for Windows & Mac :- https://support.motorola.com/us/en/drivers
Setup ADB and fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
flash-all.sh (Linux + Mac) - https://mega.nz/#!OYFiRKZC!2CjMLxpoEAqpFyB_q1Q1FncC9a1oNofh9Hjm99PwiGo
flash-all.bat (Windows) - https://mega.nz/#!DF1XwSjC!tkHhb9H9-1piNr1AbKaPJK_yLuv4rpIxw1AWicD1I94
Factory Firmwares
https://mirrors.lolinet.com/firmware/moto/payton/official/
US Retail Android 9.0 Pie :- https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Android One Android 9.0 Pie :- https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Twitter Account to Follow for latest firmware uploads
https://twitter.com/motofirmware123
you da man!
Your tutorials are very helpful .Thanks
When will you have the 28.2 firmware with the May update? Thats what version mine was on before I bricked it.
jpolster2005 said:
When will you have the 28.2 firmware with the May update? Thats what version mine was on before I bricked it.
Click to expand...
Click to collapse
you should be able to flash the latest firmware listed above as long as you can boot into fastboot.
but my locked boot loader says preflash validation failed
jpolster2005 said:
but my locked boot loader says preflash validation failed
Click to expand...
Click to collapse
unlock the bootloader.
I can't, because OEM UNLOCKING is set to off
Thanks for the simplified guide. Worked great, I was able to relock the bootloader and accept an OTA with no problem. Only issue is the device doesn't pass safety net - signature validation error, and when I boot up I get the device has been modified pop up.
michael28056 said:
Thanks for the simplified guide. Worked great, I was able to relock the bootloader and accept an OTA with no problem. Only issue is the device doesn't pass safety net - signature validation error, and when I boot up I get the device has been modified pop up.
Click to expand...
Click to collapse
rooted?
No -unrooted, stock rom from this thread, locked bootloader.
michael28056 said:
No -unrooted, stock rom from this thread, locked bootloader.
Click to expand...
Click to collapse
well, i never stay on stock long enough to check that ..sorry cant help with that.
guys PLEASE help me I have a $300 paperweight here. Best Buy wouldn't take it back so I NEED to get it fixed. I was already on the newest OTA when I bricked my phone on a locked boot loader, and when I try to flash 28.1 thru Fastboot, it says validation failed. is there anyone out there who has access to the Fastboot flashable 28.2? I need my phone back!
jpolster2005 said:
guys PLEASE help me I have a $300 paperweight here. Best Buy wouldn't take it back so I NEED to get it fixed. I was already on the newest OTA when I bricked my phone on a locked boot loader, and when I try to flash 28.1 thru Fastboot, it says validation failed. is there anyone out there who has access to the Fastboot flashable 28.2? I need my phone back!
Click to expand...
Click to collapse
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Neffy27 said:
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Click to expand...
Click to collapse
same peeps thread
aw man... well, I meant to post specifically to the last post in the thread but was on the mobile app.
:good::good: Just wanted to say thank you for this post, the links to the image files and the flash-all BAT file. This really saved my butt with a Project Fi Moto X4, which I had rooted using Magisk before checking on the availability of factory firmware images from Motorola. (of course there are not any available from Motorola ) The phone was continuously prompting for an OTA update, which would fail. I first tried the Magisk uninstaller, which ran successfully in TWRP, but the OTA update was still failing. After some digging on Google I found your post and used the Project Fi image to flash the phone, it worked perfectly! There was an OTA update available after flashing (The May 2018 security patches, "28.2") and it installed successfully. I love the Android community, the XDA community, and folks like yourself who take the time to write posts like this. Seriously, thank you!
g3m1n1 said:
I love the Android community, the XDA community, and folks like yourself who take the time to write posts like this. Seriously, thank you!
Click to expand...
Click to collapse
glad to be of help :highfive:
g3m1n1 said:
There was an OTA update available after flashing (The May 2018 security patches, "28.2") and it installed successfully.
Click to expand...
Click to collapse
Hello!
I understand you have Android One version. If that's the case, anyone catching the URL to OTA for the Android One 28.2 update? I've been looking for it for days, and the OTA link generator is not working (at least with the data I'm providing which should be correct).
Neffy27 said:
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Click to expand...
Click to collapse
how long before we see one. I have been relegated to using an iPhone 6 32GB! I really NEEEEEEED my phone to not be bricked. I tried to do the blank flash and boot off sd card and all that to no avail. none of it worked. meow I am getting so frustrated.
Hello, XDA Community.
Since the release of the last major update, Android Pie 9.0/OneUI, as soon as we trigger an update to the bootloader while we are running unofficial binaries, like TWRP and custom ROMs, a message pops up on boot splash when we perform a simple reboot:
"Only official released binaries are allowed to be flashed"
This message shows up when we have KG State Prenormal (you can check KG State by entering download mode).
Before the Pie update, we were able to skip RMM State Prenormal by setting system date for 7 days before current date, then triggering a "check for system update", then setting back to current date. However, this doesn't work on the new Pie bootloader, which is why I am writing this guide, as I got caught many times into this damn state
The workaround I've found is downgrading bootloader from Pie to Oreo, but, as we know, after flashing Pie bootloader, we are not able to downgrade it to Oreo using Odin, however it's possible forcing the downgrade using Heimdall on Ubuntu.
REQUIREMENTS:
1. Ubuntu 16.04+
2. Heimdall (install it through Ubuntu terminal)
sudo apt install heimdall-flash
Click to expand...
Click to collapse
3. 'cm.bin' + 'modem.bin' + 'sboot.bin' files from Oreo firmware (you can get them by extracting BL and CP .tar files from the official stock firmware zip - download them on SamFirm, SamMobile or updato.com)
4. Internet connection (important - needed to download PIT file)
5. Attention while typing the commands
GUIDE:
1. Boot your phone into download mode (Power + Vol (-) + Bixby, then Vol (+) to enter download mode)
2. Place cm.bin + modem.bin + sboot.bin into your Ubuntu user folder (/home/username/) - check attachment
3. Open terminal (Ctrl + Alt + T)
4. Type the following command:
heimdall flash --CM cm.bin --RADIO modem.bin --BOOTLOADER sboot.bin
Click to expand...
Click to collapse
5. It should take about 5 seconds. After that, you're done and now you can flash unofficial binaries (e.g. TWRP), or even fully downgrade to Oreo, if you got fed up with Pie :laugh:
I hope this helps anybody. If this guide helped you, leave me a 'Thanks' and/or drop a comment.
Yours sincerely,
James
^ I flash TWRP normally through Odin, at this point KG state is "Checking"
Reboot to recovery, if you try to flash something at this point it fails since it can't mount data and system if I remember correctly, either you format them or change the filesystem for the partitions that can't be mounted to another format and then again to the original format(ext4). Now you can flash dm-verity disable and a custom ROM. This was my case. I don't know about the rmm state bypass you mentioned earlier. The only thing I know is that KG State is set to Checking, and stays like that.
i have all files but flasher i mean heimdall-suite-1.4.0-win32 its not working because me PC is win 7 64 Bit so what must i do need help please.
and i got this flash file G955FXXU4CRL3 and some device like Z3X, UMT, Chimera ETC.. can i use this device or u will give me any other tool?
THX.
I thought Heimdall didn't work for s8 and new firmware
then whats is the solution for RMM Status prenomal ?
talhagsm said:
i have all files but flasher i mean heimdall-suite-1.4.0-win32 its not working because me PC is win 7 64 Bit so what must i do need help please.
and i got this flash file G955FXXU4CRL3 and some device like Z3X, UMT, Chimera ETC.. can i use this device or u will give me any other tool?
THX.
Click to expand...
Click to collapse
"win32"? I have tested this solution on Ubuntu. I can't guarantee this works with Windows 7, sorry
talhagsm said:
then whats is the solution for RMM Status prenomal ?
Click to expand...
Click to collapse
On Oreo, I used to follow this guide:
https://forum.xda-developers.com/ga...iscussion/stoping-damn-rmm-prenormal-t3883519
However, this doesn't work with Pie/OneUI
TheMadScientist said:
I thought Heimdall didn't work for s8 and new firmware
Click to expand...
Click to collapse
Worked for me while downgrading DSBA to CSB1 bootloader
jameskunst said:
Worked for me while downgrading DSBA to CSB1 bootloader
Click to expand...
Click to collapse
Last I heard it hadn't been updated. I stand corrected
thank you
but how to remove KG State Prenormal if i want stay on pie
like i have file to remove rmm state and byebass
are there any way to byebass KG State or remove
Can I use this to get back to nougat?
Whats the best way to 'extract' the BL & CP files? If I use 7zip in windows or archive manager in linux it gives me cm.bin.lz4 & sboot.bin.lz4 etc. Do I rename these or use them as is?
kgr said:
Whats the best way to 'extract' the BL & CP files? If I use 7zip in windows or archive manager in linux it gives me cm.bin.lz4 & sboot.bin.lz4 etc. Do I rename these or use them as is?
Click to expand...
Click to collapse
I used linux dude, lz4 is another form of compression, like zip etc.
If you rename the files it'll fail.
In parrot linux, lz4 wasn't installed.
##so I downloded it first##
sudo apt-get install lz4
##then i used lz4 to decompress each of the files##
lz4 -d modem.bin.lz4
this will decompress and spit out the modem.bin file you're after.
---------- Post added at 11:11 AM ---------- Previous post was at 11:01 AM ----------
SM-G950F
SO I successfully flashed the required .bin files in linux to the phone as per the guide.
Booted back into windows to used odin and tried flashing twrp-3.2.3-2-dreamlte.img.tar
Still failed with "only official released binaries etc" error on the bootloader after Odin fails.
RMM prenormal still showing on the bootloader.
Is this normal and I have to wait another 7 days or should this have worked?
what is KG gate?
there's no need to go through all that, just reflash BL,CP & Home from Oreo Stock rom.Then you can reflash TWRP after that,atleast thats what i did on G965N Pie and it worked
flash this using odin
done
peeyemv said:
flash this using odin
done
Click to expand...
Click to collapse
On AP tab?
LU SONEVESSO said:
On AP tab?
Click to expand...
Click to collapse
If your going to flash it then yes use AP section in Odin.
I threw my S8 Fury can not do anything oem unlock no longer appears now I have an S10 .... XD The Life is Strange
Psydt0n3 said:
I used linux dude, lz4 is another form of compression, like zip etc.
If you rename the files it'll fail.
In parrot linux, lz4 wasn't installed.
##so I downloded it first##
sudo apt-get install lz4
##then i used lz4 to decompress each of the files##
lz4 -d modem.bin.lz4
this will decompress and spit out the modem.bin file you're after.
---------- Post added at 11:11 AM ---------- Previous post was at 11:01 AM ----------
SM-G950F
SO I successfully flashed the required .bin files in linux to the phone as per the guide.
Booted back into windows to used odin and tried flashing twrp-3.2.3-2-dreamlte.img.tar
Still failed with "only official released binaries etc" error on the bootloader after Odin fails.
RMM prenormal still showing on the bootloader.
Is this normal and I have to wait another 7 days or should this have worked?
Click to expand...
Click to collapse
yeah, the same here with s8+, done with linux and went back to windows, flashed twrp and fails, i don't know what to do now
the only different thing was the phone state was custom, but still rmm was lock
i even flashed stock oreo but nothing
and i must say, the linux thing is a pain in the ass, that procedure is not for everyone,im a soft engineer and it took me 2H
peeyemv said:
flash this using odin
done
Click to expand...
Click to collapse
doesn't work, get "SECURE CHECK FAIL : (BOOTLOADER)" in download mode and state is still Prenormal
This is an updated root and unroot method for the s7/s7 edge.
I updated the zip file with the latest eng boot
Uploaded the latest stock files
Credit: https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616
Use V10 Odin Files this will allow you to root the s7/s7 sdge on the latest firmware. (02/09/2020)
Directions:
This works for Oreo And Nougat Roms
As always there is a chance of bricking your phone
1. Download and extract S7_Oreo_Nougat_Adb_Advanced_Root.zip
2. Reboot your phone to download mode
3. Inside the S7_Oreo_Nougat_Adb_Advanced_Root folder you will find an Odin_Firmware folder. Use Odin and flash the Eng Boot Image for your
phone
4. Once phone is rebooted and connected to computer click on the cmd-here.exe and type root.bat in the command window and hit enter
5. Follow directions on the command window
6. You can only use system root on Oreo
7. Once root is done and root bat closes leave your phone alone for a few minutes it may reboot a couple of times
8. Sprint Users This should work for you as well just let me know if your phone reboots with eng boot.img installed like it did on nougat while try too run the root.bat. I may need to change some things
9. With this system root do not update su binary if in anyway you get something asking you to update binaries ignore it. You can also disable notifications about updating binaries. This will not affect su app
10. Don't flash any superuser zips in recovery that are not made by me
S7 Oreo Nougat Adb Advanced Root V13: https://archive.org/download/s7oreo...Nougat_Adb_Advanced_Root_V13 (02-08-2020).zip
Return to stock:
Open odin
Reboot in download mode
Apply files
Plus in device
Flash to device
VZW-G935VVRUACSH1: https://archive.org/download/vzwg935vvruacsh120191014133427/VZW-G935VVRUACSH1-20191014133427.zip
Thank you. Followed the straight forward steps and got mine done perfectly on v10_BL. I even flashed stock and did it again just to be sure. I very much appreciate your work.
1) will this work on G935TUVSACSI1
2) how to install magisk plz reply
abdullahpk33 said:
1) will this work on G935TUVSACSI1
2) how to install magisk plz reply
Click to expand...
Click to collapse
Works on latest firmware
No bootloader unlock so no magisk
How do I return to stock with the changes that I have while rooted on S7 flat model? Sorry for nooby question
thank you so after trying for 1yr i got root on 935t ...
Can we install custom recovery/twrp???
And plz anyone know how to install xposed framework
i tried on G935P sprint , everything went like u said, but after cm closed and phone rebooted, and i went to open supersu (ur app) said root undetected !!!
i choosed supersu app (not system root ) ! any help
edit: i run root bat again, but this time choosed (system root orio while i am on nougat lol) and i choosed only root no tweak (before chosed on demand) + didnt choose finger fix..
but i feel the device little slow, any help ?
Somehow I am on version 11 of bootloader.....
Does it delete all my files? Oo
Also after flashing eng boot my phone is stuck at endless reboot
stuck at bootloader
abdullahpk33 said:
thank you so after trying for 1yr i got root on 935t ...
Can we install custom recovery/twrp???
And plz anyone know how to install xposed framework
Click to expand...
Click to collapse
To install Xposed, just download the Xposed installer 3.15 apk and install from the app. Reboot.
Will this work on SM-G935U
(Baseband: G935UUEU4BQD2) ???
will this work for Samsung Galaxy s7 edge SM-G935T Qualcomm Android 8.0 sir ?
Do you know??
Is there an unbranded firmware download available somewhere for this phone???
It did'nt work on my S7 edge SM-G935T T-mobile Qualcomm
I already used different cables, usb port, restart my laptop..
Anyone can help ? Will appreciate a lot!
it says on the phone [boot]fused 11 > binary 10
Good work man..
Can you explain how to unroot because my phone is little bit lagging and I can't flash stock firmware because after flashing the stock firmware my phone will stuck on Samsung logo..
Sorry for my bad English.. ?
None of the odin files worked for G930PVPSBCTA1
I'm on version G930PVPSBCTA1 and none of the odin files would flash. Fails immediately when flashing. Am I doing something wrong?
dont work on 930p v11 booloader
Well that sucks. I highly doubt we'll see a root method then at this point. Thanks for replying.
eng boot v11
hello,
I'm trying to root g935u and see every tread stuck on v11 bootloader.
Seems it may help: h_t_tps:// support.halabtech.com/index.php?a=downloads&b=file&id=234247
I have no access or knowledge to use that alone.
I get the same error message as you on a Verizon version
I get the same error message as you on a Verizon version
sinizter0202 said:
It did'nt work on my S7 edge SM-G935T T-mobile Qualcomm
I already used different cables, usb port, restart my laptop..
Anyone can help ? Will appreciate a lot!
it says on the phone [boot]fused 11 > binary 10
Click to expand...
Click to collapse