Related
[HOWTO] root Galaxy S8 S8+ CRGH CRI5 CRI1 CRJ5 CRK1 CRL3 TWRP&ambasadii stock kernel
[Guide]How to root Galaxy S8 or S8+ SM-G95xF/D with CRGH, CRI5 CRI1 CRJ5 CRK1 CRL3 ROM using TWRP and ambasadii stock kernel (which is including magisk)?
This topic is showing how to root à Samsung Galaxy S8 or S8+ (Oreo - 8.0.0) Exynos with the CRGH or CRI5 ROM where Samsung has again added some security features to avoid the rooting device.
Previous found topics seem running fine until the device reboot. It is stucked on SAMSUNG starting message with on top "Only official released binaries are allowed to be flashed"
WARNING:
- At end of this process, keep checked your OEM unlock.
- Rooting and bricking your device is at your own risk.
Tested on:
- S8 SM-G950FD Exynos model ROM G950FXXU3CRGH from sammobile G95xF_Stock_Kernel_CRGH_v2.zip and TWRP 3.2.3-2-dreamlte
- S8 SM-G950FD Exynos model ROM G950FXXU4CRI5 from sammobile G95xF_Stock_Kernel_CRI5.zip and TWRP 3.2.3-2-dreamlte
- S8 SM-G950FD Exynos model ROM G950FXXU4CRI5 G95xF_Stock_Kernel_CRI5_v2.zip and TWRP 3.2.3-2-dreamlte thanks @gtrs36 for testing this new version of rooted boot loader
- S8 SM-G950FD Exynos model ROM G950FXXU4CRI1 G95xF_Stock_Kernel_CRI5_v2.zip and TWRP 3.2.3-2-dreamlte thanks @Jon Saridjan for tests using the mix of ROM and rooted boot loader
- S8+ SM-G955F Exynos model ROM G955FXXU4CRJ5 Stock_Kernel_G95xF_CRJ5.zip and TWRP 3.2.3-2-dream2lte thanks @.RadziU. for testing this new version of rooted boot loader
- S8+ SM-G955F ROM CRJ5 Stock_Kernel_G95xF_CRJ5.zip and TWRP 3.2.3-2-dream2lte thanks @DarthKyria for testing this version of rooted boot loader
Please keep me in touch to update this list!
Download links:
- TWRP
** Thanks @teamwin
** For S8 twrp-3.2.3-0-dreamlte.img.tar download on https://dl.twrp.me/dreamlte/
** For S8+ twrp-3.2.3-0-dream2lte.img.tar download on https://dl.twrp.me/dream2lte/
- @ambasadii stock kernel
** For S8 and S8+ G95xF_Stock_Kernel_CRGH_v2.zip download from https://androidfilehost.com/?fid=1322778262903989728
Link unavailable, use the below version** For S8 and S8+ G95xF_Stock_Kernel_CRI5.zip download from https://androidfilehost.com/?fid=1322778262904009192
** For S8 and S8+ G95xF_Stock_Kernel_CRI5_v2.zip download from https://androidfilehost.com/?fid=1322778262904024753
** For S8 and S8+ Stock_Kernel_G95xF_CRJ5.zip found there: https://androidfilehost.com/?fid=11410932744536984254
** For S8 and S8+ Stock_Kernel_G95xF_CRK1.zip found there: https://androidfilehost.com/?fid=11410963190603872259
** For S8 and S8+ Stock_Kernel_G95xF_CRL3.zip found there: https://androidfilehost.com/?fid=11410963190603878451
** Other versions are there https://androidfilehost.com/?w=files&flid=260111
- Odin3-v3.13.1 download on https://samsungodin.com/
- Samsung drivers download on https://samsungodin.com/
- MagiskManager-v6.0.0.apk from MagiskManagerDOTcom
- RootChecker.apk from https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
- RootCheckerPro.apk from https://play.google.com/store/apps/details?id=com.joeykrim.rootcheckp&hl=en
- Titanium Backup from https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
1. Backup your important data from internal storage before proceeding towards the installation. (I'm using smart switch and helium for some other apps. Unfortunately, smart switch is not able to fully backed up bluemail, Call Recorder Pro and so on)
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. (It should be blue) If not found, set the date 8 days ago, uncheck "Automatic System Update" and reboot.
4. Power off device and boot into download mode by pressing the VOLUME DOWN, BIXBY KEY, and POWER buttons then VOLUME UP button to continue
5. Connect your device to the PC.
6. Now open Odin3-v3.13.1 as administrator and you should see a blue-highlighted box with a random COM number, which means you have proper drivers installed.
7. Put on our SD card (or on USB key - in case of USB key, you gonna use the usb dongle to flash/install - )
** MagiskManager-v6.0.0.apk
** RootCheckPro.apk
** G95xF_Stock_Kernel_CRGH_v2.zip
____ or
** G95xF_Stock_Kernel_CRI5.zip
8. In the tab Options, uncheck "Auto Reboot" and kept checked "F. Reset Time". Click on the AP button and choose the twrp-3.2.3-0-dreamXlte.img.tar file.
9. Press the START button.
10. Now after Odin says PASS,
____10.1 Press the VOLUME DOWN, BIXBY KEY, and POWER buttons until the screen goes black
____10.2 Press VOLUME UP, BIXBY KEY, and POWER buttons for about 4 seconds until you should be in TWRP recovery.
11. Now allow the modifications by swiping and go to WIPE option.
12. <WARNING> Disconnect your device from your PC </WARNING> and choose "Format Data" - Type "yes" - ENTER.
____<WARNING> If at the Format Data step, you got red messages, complete the below step 13 and redo both step 12&13 </WARNING>
13. Go back to Home menu and choose “Reboot” then “Recovery” also choose “Swipe to Install”.
14. Once rebooted, choose “Keep Read Only” if needed then “Install” then flash G95xF_Stock_Kernel_CRGH_v2.zip or G95xF_Stock_Kernel_CRI5.zip
15. The device should reboot, it's taking a long time. Enter your PIN code. Select your language and so on... Ignore the popup asking you to reboot because of the SIM Card changed"
16. Enjoy, your phone is rooted, Magisk and TWRP are both installed!
17. Install RootCheckPro.apk and start it, tape VERIFY ROOT the app should said your device has root access. Don't be afraid about SuperSU @Chainfire not installed.
18. Install MagiskManager-v6.0.0.apk, start it. Control the SafetyNet, all should be green.
19. Install Titanium Backup, start it. You should see a popup asking you to agree the root access.
20. Start TWRP app, agree the new installation, reboot.
21. Reboot once the device is stable without any notifications.
22. Restore your data thru smart switch and helium or other apps.
Thanks for
@ambasadii for the updated stock kernel
@teamwin for TWRP
@topjohnwu for Magisk
@joeykrim for Root Checker Pro
@Titanium Track for Titanium Backup
@Ruturaj Kadam for the initial topic
@max lee for video and photo topic
@coyote950 for the help
@Chainfire for SuperSU
Please find below the rooting result displayed by root checker pro. Thanks @joeykrim
{
"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"
}
And the ROM version even OEM unlock ON
I am G955F ; Still on R16NW.G955FXXU1CRB7 boot loader not unlocked yet. Is best practice (Sept, 23rd 2018) to upgrade and use this guide? Or use another for my U1 (older) bootloader?
Loupps said:
[Guide]How to root Galaxy S8 or S8+ SM-G95xF/D with CRGH ROM august 2018 using TWRP and ambasadii stock kernel (which is including magisk)?
This topic is showing how to root à Samsung Galaxy S8 or S8+ (Oreo - 8.0.0) Exynos with the CRGH ROM from august 2018 where Samsung has again added some security features to avoid the rooting device.
Previous found topics seem running fine until the device reboot. It is stucked on SAMSUNG starting message with on top "Only official released binaries are allowed to be flashed"
WARNING:
- At end of this process, keep checked your OEM unlock. Maybe, the risk is to flash back an official ROM if you restart your phone with OEM unlock unchecked.
- Rooting and bricking your device is at your own risk.
Tested on:
- SM-G950FD Exynos model ROM G950FXXU3CRGH from sammobile patch august 2018
Please keep me in touch to update this list.
Download links:
- TWRP
* For S8 twrp-3.2.3-0-dreamlte.img.tar download on https://dl.twrp.me/dreamlte/
* For S8+ twrp-3.2.3-0-dream2lte.img.tar download on https://dl.twrp.me/dream2lte/
- @ambasadii stock kernel
* For S8 and S8+ G95xF_Stock_Kernel_CRGH_v2.zip download from https://androidfilehost.com/?fid=1322778262903989728
* Other versions are there https://androidfilehost.com/?w=files&flid=260111
- Odin3-v3.13.1 download on https://samsungodin.com/
- Samsung drivers download on https://samsungodin.com/
- MagiskManager-v6.0.0.apk from https://******************/
- RootCheckPro.apk from https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
- Titanium Backup from https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
1. Backup your important data from internal storage before proceeding towards the installation. (I'm using smart switch and helium for some other apps. Unfortunately, smart switch is not able to fully backed up bluemail, Call Recorder Pro and so on)
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. (It should be blue) If not found, set the date 8 days ago, uncheck "Automatic System Update" and reboot.
4. Power off device and boot into download mode by pressing the VOLUME DOWN, BIXBY KEY, and POWER buttons then VOLUME UP button to continue
5. Connect your device to the PC.
6. Now open Odin3-v3.13.1 as administrator and you should see a blue-highlighted box with a random COM number, which means you have proper drivers installed.
7. Put on our SD card (or on USB key - in case of USB key, you gonna use the usb dongle to flash/install - )
- MagiskManager-v6.0.0.apk
- RootCheckPro.apk
- G95xF_Stock_Kernel_CRGH_v2.zip
8. In the tab Options, uncheck "Auto Reboot" and kept checked "F. Reset Time". Click on the AP button and choose the TWRP.tar file.
For S8 twrp-3.2.3-0-dreamlte.img.tar download on https://dl.twrp.me/dreamlte/
For S8+ twrp-3.2.3-0-dream2lte.img.tar download on https://dl.twrp.me/dream2lte/
Thanks @teamwin
9. Press the START button.
10. Now after Odin says PASS,
10.1 Press the VOLUME DOWN, BIXBY KEY, and POWER buttons until the screen goes black
10.2 Press VOLUME UP, BIXBY KEY, and POWER buttons for about 4 seconds until you should be in TWRP recovery.
11. Now allow the modifications and go to WIPE option.
12. <WARNING> Disconnect your device from your PC </WARNING> and choose FORMAT DATA - Type yes - ENTER.
13. Go back to Home menu and choose “Reboot” then “Recovery” also choose “Swipe to Install”.
14. Once rebooted, choose “Keep Read Only” then “Install” then flash G95xF_Stock_Kernel_CRGH_v2.zip
For S8 and S8+ G95xF_Stock_Kernel_CRGH_v2.zip download from https://androidfilehost.com/?fid=1322778262903989728
Other versions are there https://androidfilehost.com/?w=files&flid=260111
Thanks @ambasadii
15. The device should reboot, it's taking a long time. Enter your PIN code. Select your language and so on... Ignore the popup asking you to reboot because of the SIM Card changed"
16. Enjoy, your phone is rooted, Magisk and TWRP are both installed!
17. Install RootCheckPro.apk and start it, tape VERIFY ROOT the app should said your device has root access. Don't be afraid about SuperSU @Chainfire not installed.
18. Install MagiskManager-v6.0.0.apk, start it. Control the SafetyNet, all should be green.
19. Install Titanium Backup, start it. You should see a popup asking you to agree the root access.
20. Start TWRP app, agree the new installation, reboot.
21. Reboot once the device is stable without any notifications.
22. Restore your data thru smart switch and helium or other apps.
Thanks for
@ambasadii for the updated stock kernel
@teamwin for TWRP
@topjohnwu for Magisk
@JoeyKrim for Root Checker Pro
@Titanium Track for Titanium Backup
@Ruturaj Kadam for the initial topic
@max lee for video and photo topic
@coyote950 for the help
@Chainfire for SuperSU
Click to expand...
Click to collapse
Can we use fresher driver from ? Driver : USB_Drivers_1.5.27.0.rar 26-Aug-2016 02:35 10636k
https://samsungusbdriver.com/category/download
https://samsungusbdriver.com/download/samsung-driver-v1-5-65-0
Or -v1.5.65.0 as the best ?
Also why are you installing Titanium Backup, what was intended for it?
futiless said:
I am G955F ; Still on R16NW.G955FXXU1CRB7 boot loader not unlocked yet. Is best practice (Sept, 23rd 2018) to upgrade and use this guide? Or use another for my U1 (older) bootloader?
Click to expand...
Click to collapse
Hello,
The stock G95xF_Stock_Kernel_CRB7.zip found there https://androidfilehost.com/?fid=746010030569956301 does'nt contain magisk nor twrp.
So you have to flash both stock G95xF_Stock_Kernel_CRB7.zip and magisk.
Please refer this topic https://www.xda-developers.com/how-to-install-magisk/ to download magisk
Then you will have to install "magisk manager" and "official twrp app"
futiless said:
Can we use fresher driver from ? Driver : USB_Drivers_1.5.27.0.rar 26-Aug-2016 02:35 10636k
https://samsungusbdriver.com/category/download
https://samsungusbdriver.com/download/samsung-driver-v1-5-65-0
Or -v1.5.65.0 as the best ?
Also why are you installing Titanium Backup, what was intended for it?
Click to expand...
Click to collapse
If you are able to communicate with the device thru odin (the box COM should be blue with a random port number and you should see Added!!! or Removed!!! when you connect or disconnect your device) or backup your device thru smart switch, it's mean your driver are running fine.
Titanium Backup is able to perform a full backup on SDcard as there is a root access.
Smart Swich is not able to fully backed up (right access issue) the configurations for some applications. And it's forgot the SMS notification configuration, strange!!
Helium (without root access) is able to backed up few applications but said it's ok for some others even if it's failed. Don't properly work on SDcard, so you have to move the carbon directory from internal device to SDcard before flash or format any things.
Regarding installing magisk I understand … but would you recommend me to upgrade my bootloader and phone or use CRB7 and upgrade after. Which is a better option?
After rooting, how do we update with next version of the firmware without loosing root?
Probably flash the new firmware using Odin without restart and then flash the corresponding kernel version from the link above using TWRP?
futiless said:
Regarding installing magisk I understand … but would you recommend me to upgrade my bootloader and phone or use CRB7 and upgrade after. Which is a better option?
Click to expand...
Click to collapse
I don't know the release date for the CRB7 but according to sammobile the latest version seems CRI5. I hope the previous number is not important. For my tested version, it's 3 and for this version it's 4.
I've checked the G95xF_Stock_Kernel_CRI5.zip is containing TWRP and magisk for S8 and S8+.
So my advise is to
- upgrade first to G950FXXU4CRI5 (download from sammobile ; from my point of view, the country is not an issuer) using odin without restore your data at end then
- apply the root process following this topic by flashing G95xF_Stock_Kernel_CRI5.zip instead of G95xF_Stock_Kernel_CRGH_v2.zip
- restore your data
alexander_sirakov said:
After rooting, how do we update with next version of the firmware without loosing root?
Probably flash the new firmware using Odin without restart and then flash the corresponding kernel version from the link above using TWRP?
Click to expand...
Click to collapse
Of cause you will lost the root access if you're upgrading your device except if you use some specific tools. This is because, the upgrade consist to put an image into a partition. I don't know if you're talking about automatic system update but on my side, it's off as I want to stay to my current stable version.
CRI5 gas got sama path for rooting
Can be rooted by using sama method
950f CRI5
Loupps said:
I don't know the release date for the CRB7 but according to sammobile the latest version seems CRI5. I hope the previous number is not important. For my tested version, it's 3 and for this version it's 4.
I've checked the G95xF_Stock_Kernel_CRI5.zip is containing TWRP and magisk for S8 and S8+.
So my advise is to
- upgrade first to G950FXXU4CRI5 (download from sammobile ; from my point of view, the country is not an issuer) using odin without restore your data at end then
- apply the root process following this topic by flashing G95xF_Stock_Kernel_CRI5.zip instead of G95xF_Stock_Kernel_CRGH_v2.zip
- restore your data
Click to expand...
Click to collapse
First of all the data partition is of no value ... yet..
This almost completes my question yet, my CRB7 is from Feb and you say upgrade to CRI5 which would in fact be a downgrade. This still begs the question as well,,, I guess I should have mentioned I want to run the latest bootloader and 8.1/9 roms with recent modem etc.
Should I CRI5 provide me any benefit lost by upgrading the bootloader?
futiless said:
First of all the data partition is of no value ... yet..
This almost completes my question yet, my CRB7 is from Feb and you say upgrade to CRI5 which would in fact be a downgrade. This still begs the question as well,,, I guess I should have mentioned I want to run the latest bootloader and 8.1/9 roms with recent modem etc.
Should I CRI5 provide me any benefit lost by upgrading the bootloader?
Click to expand...
Click to collapse
I mean about an upgrade from CRB7 to CRI5 using an official released version. The CRI5 has been officially released on september 2018.
The ambasadii stock kernel seems to collaspe the boot partition (to avoid the stucking message) and the recovery partition (to install TWRP instead of the official recovery tool) and root the system.
So adventure is adventure, it should work to only flash the CRI5 bootloader, flash TWRP and then flash the ambasadii stock kernel. At end, you shoud be root and kept your CRB7 rom.
But keep in mind that at the format data step, you will lost all your personal configuration. So I'm clearly don't understand why you are trying to mix rom.
Where to get the CRI5 original bootloader?
I’m in catch 22, shall i root or wait for slow Mo and emoji’s updates? Man I’m on the exact firmware, that your guide is written for. Would there be any way to update once I’m rooted to slow Mo emoji firmware without breaking root? Sorry last time i rooted was Android 4.4.4 and Android 6.0.1.. Since them days, so much has changed Samsung really is making it harder to root there high end smartphones, i am rooting Galaxy Tab S4 10.5 but that feels so easy to root, as i don’t want to go through re-root backing up process etc. on the S8+?
So my question is shall i wait for the slow Mo update? And then root? Or shall i root and then apply slow Mo update? What’s the best course of action? Or what would you do? Thanks..
N1NJATH3ORY said:
I’m in catch 22, shall i root or wait for slow Mo and emoji’s updates? Man I’m on the exact firmware, that your guide is written for. Would there be any way to update once I’m rooted to slow Mo emoji firmware without breaking root? Sorry last time i rooted was Android 4.4.4 and Android 6.0.1.. Since them days, so much has changed Samsung really is making it harder to root there high end smartphones, i am rooting Galaxy Tab S4 10.5 but that feels so easy to root, as i don’t want to go through re-root backing up process etc. on the S8+?
So my question is shall i wait for the slow Mo update? And then root? Or shall i root and then apply slow Mo update? What’s the best course of action? Or what would you do? Thanks..
Click to expand...
Click to collapse
Please have a look on this video https://www.youtube.com/watch?v=Npc-PCutvvA CRI5 is compatible with slow Mo and emoji’s.
So, my advice is to download the official CRI5 version (on SamMobile firmware) then rooting using the root process following this topic by flashing G95xF_Stock_Kernel_CRI5.zip instead of G95xF_Stock_Kernel_CRGH_v2.zip and you will have slow MO and be able to install emoji's apps.
futiless said:
Where to get the CRI5 original bootloader?
Click to expand...
Click to collapse
You have to download the fully ROM on SamMobile firmware (that's should be a good thing in case of recover process to have the fully rom on your side)
Loupps said:
Please have a look on this video https://www.youtube.com/watch?v=Npc-PCutvvA CRI5 is compatible with slow Mo and emoji’s.
So, my advice is to download the official CRI5 version (on SamMobile firmware) then rooting using the root process following this topic by flashing G95xF_Stock_Kernel_CRI5.zip instead of G95xF_Stock_Kernel_CRGH_v2.zip and you will have slow MO and be able to install emoji's apps.
Click to expand...
Click to collapse
Thank you so much! Quick question i purchased my S8+direct from Samsung website there's no BTU CRI5 ? Does it matter lets say i pick poland or spain ? See pics for what i mean.. Thanks again..
P.S.S Sammobile sucks for firmware download speeds, updato.com is so fast 2 mins fully donwloaded, sammobile 2 hours unless your on a piad plan!
N1NJATH3ORY said:
Thank you so much! Quick question i purchased my S8+direct from Samsung website there's no BTU CRI5 ? Does it matter lets say i pick poland or spain ? See pics for what i mean.. Thanks again..
P.S.S Sammobile sucks for firmware download speeds, updato.com is so fast 2 mins fully donwloaded, sammobile 2 hours unless your on a piad plan!
Click to expand...
Click to collapse
The country is not an issue except if you phone is locked to a network. That was the case in the past but now we brough phone from china and network operator from another way. So two ways: wait a couple of day the UK released version or download the south africa one as they are speacking british english too.
You're right about sammobile but I'm downloading and go to another activity... I've never tried updato.com, sammobile is more readable from my point of view.
Anyway to use this without sd card?
RikoudoS said:
Anyway to use this without sd card?
Click to expand...
Click to collapse
After the format data, reconnect the device and you will be able to see the internal storage with only the TWRP directory. (at the step 14. for this topic)
Copy/paste or drag/drop the G95xF_Stock_Kernel_CRGH_v2.zip at the root and you will be able to flash it.
Another way should be to connect an USB key thru the usb connector delivered with your S8.
Download the Samsung firmware for the Galaxy A7 2018 SM-A750G with product code CPA from Panama (Claro). This firmware has version number PDA A750GUBS6BTE1 and CSC A750GOWA6BTE1. The operating system of this firmware is Android 9 , with build date Fri, 15 May 2020 03:19:56 +0000. Security patch date is 2020-05-01, with changelist 16854835.
Model... SM-A750G - A750G/DS
Model name... Galaxy A7 2018
Country... Panama (Claro) (CPA)
Versión... Android 9
Changelist... 16854835
Build date... Fri, 15 May 2020 03:19:56 +0000
Security Patch Level... 2020-05-01
Product code... CPA
PDA... A750GUBS6BTE1
CSC... A750GOWA6BTE1
INSTRUCTIONS * 5 Files *
1.- Download Odin 3.14.4 - Install Samsung USB Drivers
2.- Extract the firmware file you just downloaded. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
3.- Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
4.- Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY
Other options in case first option did not work or isn't possible.
Option 2 VOLUME DOWN + VOLUME UP then USB cable
Option 3 POWER + VOLUME DOWN + VOLUME UP
Option 4 POWER + VOLUME DOWN + HOME BUTTON
Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY
Option 6 (Note10) POWER + VOLUME UP
5.- Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
6.- Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
7.- Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC.
Download Samsung USB Driver for Mobile Phones
https://developer.samsung.com/mobile/file/68b2dc40-3833-4a8b-b58e-32f7aca25c00
Download Odin 3.14.4
https://dl2018.sammobile.com/Odin3-v3.14.4.zip
Download Firmware
https://samfrew.com/download/Galaxy__A7__%E2%91%A7__/sw2m/CPA/A750GUBS6BTE1/A750GOWA6BTE1/
Or
Download Firmware
https://www.sammobile.com/samsung/galaxy-a7-2018/firmware/SM-A750G/CPA/download/A750GUBS6BTE1/340041/
Root + Recovery
https://forum.xda-developers.com/galaxy-a7/development/recovery-twrp-3-2-3-1-galaxy-a7-2018-t3876798
thank you for this sir....
Hi, In the indian version of a7, I am unable to downgrade from 10 to 9. The phone is showing that binary is mismatching. How to downgrade ?
Downgrade from 9 to 8?
vaidhy2007 said:
Hi, In the indian version of a7, I am unable to downgrade from 10 to 9. The phone is showing that binary is mismatching. How to downgrade ?
Click to expand...
Click to collapse
If the binary is mismatching it's not possible to downgrade.
Why would you downgrade from 10 to 9? anyone?
DESCRIPTION
Realme Like Few Other Companies Have Dishonest Rules For Unlocking The Bootloader In Different Regions(EU). Unlocking Bootloader On The EU Variants Is Not Allowed By Realme. But I Have Found A Way To Remove The Restriction And Pave The Way For Further Development.
This Will Not Unlock Your Bootloader But It Will Convert Your Device To Global Variant (EX) There By Allowing You To Apply For Bootloader Unlock. Tested On Realme 5 (EU) Variant
NOTES
I'm Not Responsible For Anything Whatsoever. If This Guide Leads You To A Bricked Device I'll Simply Laugh At You.
STEPS (FOLLOW VERY CAREFULLY)
1. Download the Oppo_Free_Unlock_v1.0.zip file from this link
2. Enable Developer Options, USB Debugging & Make Sure Device Is Detected
3. Now Connect Your Device To The Computer Using A Micro USB Cable
3. Open Control Panel - Device Manager and expand the Network Adapters category.
4. Disable all your ethernet adapters except the wifi adapter .
5. Click on the action tab, then choose add legacy hardware
7. Choose install the hardware that I manually select from a list (Advanced) and click next.
8. Click network adapters, then click next.
9. Select Microsoft and choose Microsoft KM-TEST Loopback Adapter, then click next.
10. Click next, then click finish.
11. In the device manager,browse the Network adapters and double click on Microsoft KM-TEST Loopback Adapter to open its properties.
12. Go to the Advanced tab and find the Network Address option
13. Click the blank chackbox and paste 704D7B61ABCD in the text box .
14. Close the properties window and close Device Manager.
15. Go to where you extracted the unlock tools. Open Sec5.exe.
16. Make sure your device is in MTP mode, and then press the Unlock button.
17. After about a second, a string of numbers and letters should show up in the left pane. A few seconds later, "OK" should start flashing in the right pane. Press "Stop unlocking" and close the window.
18. Open the phone app on your device and dial *#3954391#. Then dial *#391#. A screen should come up with a whole bunch of regions listed. Take a look which region is marked in green, this is your current region .Write it so that you can go back if you want .
19. Now you can choose any region you want, I tested two, "IN INDIA" AND "MULTILINGUAL VERSION EX"
20. Your phone should now reboot. Once it's rebooted, your region will have changed .
Every time you changed region and want to change it again you need to use the software.
CREDITS
@or965 (For The Orginal Trick)
@Hanif380 (For Testing)
Followed this guide and finally managed to get the android 10 update. For some reason my region was stuck on Android 9.
Thanks.
mizdrake7 said:
DESCRIPTION
Realme Like Few Other Companies Have Dishonest Rules For Unlocking The Bootloader In Different Regions(EU). Unlocking Bootloader On The EU Variants Is Not Allowed By Realme. But I Have Found A Way To Remove The Restriction And Pave The Way For Further Development.
This Will Not Unlock Your Bootloader But It Will Convert Your Device To Global Variant (EX) There By Allowing You To Apply For Bootloader Unlock. Tested On Realme 5 (EU) Variant
NOTES
I'm Not Responsible For Anything Whatsoever. If This Guide Leads You To A Bricked Device I'll Simply Laugh At You.
STEPS (FOLLOW VERY CAREFULLY)
1. Download the Oppo_Free_Unlock_v1.0.zip file from this link
2. Enable Developer Options, USB Debugging & Make Sure Device Is Detected
3. Now Connect Your Device To The Computer Using A Micro USB Cable
3. Open Control Panel - Device Manager and expand the Network Adapters category.
4. Disable all your ethernet adapters except the wifi adapter .
5. Click on the action tab, then choose add legacy hardware
7. Choose install the hardware that I manually select from a list (Advanced) and click next.
8. Click network adapters, then click next.
9. Select Microsoft and choose Microsoft KM-TEST Loopback Adapter, then click next.
10. Click next, then click finish.
11. In the device manager,browse the Network adapters and double click on Microsoft KM-TEST Loopback Adapter to open its properties.
12. Go to the Advanced tab and find the Network Address option
13. Click the blank chackbox and paste 704D7B61ABCD in the text box .
14. Close the properties window and close Device Manager.
15. Go to where you extracted the unlock tools. Open Sec5.exe.
16. Make sure your device is in MTP mode, and then press the Unlock button.
17. After about a second, a string of numbers and letters should show up in the left pane. A few seconds later, "OK" should start flashing in the right pane. Press "Stop unlocking" and close the window.
18. Open the phone app on your device and dial *#3954391#. Then dial *#391#. A screen should come up with a whole bunch of regions listed. Take a look which region is marked in green, this is your current region .Write it so that you can go back if you want .
19. Now you can choose any region you want, I tested two, "IN INDIA" AND "MULTILINGUAL VERSION EX"
20. Your phone should now reboot. Once it's rebooted, your region will have changed .
Every time you changed region and want to change it again you need to use the software.
CREDITS
@or965 (For The Orginal Trick)
@Hanif380 (For Testing)
Click to expand...
Click to collapse
I follow every step but i don t receive ok from Sec5
What is this?
This is a guide on how to enable all LTE and 5G bands on the US or Canadian S22 series phones by going through the service menu. This guide is mostly based on this S20U guide by mellojosh, but has been adapted for the S22U phone with more information added.
Which bands can be enabled this way?
All bands the phone supports in hardware can be enabled through the service menu. For the S22 Ultra, that includes all Sub-6 bands like n78, and mmWave bands, as well as 5G SA bands, as shown in this screenshot below.
{
"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"
}
Which phones does this method support?
This method has been confirmed to work on:
Samsung S22 Ultra (S908U, S908U1, S908W).
Galaxy Z Fold 4. Thanks @Abaddon.
This method works on both Android 12 (One UI 4.1) or Android 13 (One UI 5.0 beta).
This method requires your device be on the US firmware (XAA or other US CSC), so as long as you can Odin flash XAA firmware on your device (such as Canadian variant), you should be able to do this.
If you get this method working on your phone that isn't in the known list, post it here and I will add it to the list above.
How To Guide
You will need a Windows computer (or VM) and the Samsung USB Driver installed to do the following steps. Install the USB driver from here before proceeding if you do not have it installed.
A. Flash US Firmware
First, your device must be on US firmware (XAA or other CSC). You can skip this step and go to B if your device is already on US firmware.
If you're not on a US firmware because you have another Snapdragon variant (like Canadian), follow the steps below to flash XAA firmware. Note this will WIPE and FACTORY RESET your device. ALL DATA WILL BE LOST. So backup if you need to.
Download Odin 3.14.4 or latest version.
Download US XAA U1 firmware for your device from SamMobile.com or SamFw.com. For example, for the S22 Ultra, download the XAA firmware for S908U1. Extract the contents of the firmware to somewhere on your computer. You should have 5 files (BL, AP, CP, CSC, HOME_CSC). We won't use HOME_CSC.
Restart your phone and go into download mode. On the S22 Ultra, hold all three power and up + down volume at the same time until the phone starts, then press the up volume key to get into download mode.
Open Odin and connect your phone to your computer with a USB. Odin should say your phone was added.
Click each of the BL, AP, CP, CSC buttons and select the corresponding files from the firmware zip you extracted. For CSC, use the file that starts with CSC and not HOME_CSC (we won't be using HOME_CSC). Do not load anything into USERDATA.
Click start and let it flash the firmware (see the picture below). If it flashed correctly, your phone will be on XAA firmware after it restarts and you will have to set it up again from scratch.
Set up your phone and verify it is on XAA firmware by going to Settings -> About Phone -> Software information -> check that it says XAA/XAA,XAA/OOO under "Software provider software version". OOO here will be your phone's original CSC like XAC which you cannot change and do not need to.
B. Unlock Service Menu Secret Codes
The next step is we need to unlock access to the service menu. Usually this is locked by default, but it might already be unlocked for you.
First check if you can access the service menu by trying each of these ways:
Open dialer and enter *#27663368378# to try to get directly into the service mode main menu. The menu should open after you press the last # character, you shouldn't have to press call.
Open dialer and enter *#73# to get into RF Test mode. Press Band Selection. Press three dots on top right -> Back. Repeat three dots -> back three more times until you get to the service mode main menu.
If either of the above ways works for you to get to the service mode main menu, then you can skip the below steps to unlock the menu and go directly to instructions C.
If you cannot access the menu with the above codes, then follow these instructions to unlock the secret codes.
Enable USB Debugging in Developer menu.
Download SamFW FRP tool 3.1 or latest version from here.
Open SamFW FRP tool and connect your phone to the computer with a USB.
Using SamFW FRP tool, go to MTP tab and click on "Enable Secret Code for Verizon". See the picture below. Note it works on any US CSC even though it says "for Verizon".
If in the program output you see it's getting stuck on "Waiting for DIAG", then dial *#0808# on your phone to open USB settings and select "DM + MODEM + ADB" then press OK. The program should then complete the step and then get stuck on "Disabling DIAG". When it does, using the *#0808# menu again, select "MTP + ADB" this time and press OK. Now the program should complete the step and say that secret codes was unlocked.
Now you should be able to use *#73# for RF test, *#27663368378#* to go directly to service menu. Test it to make sure the codes work and the service menu is opening.
C. METHOD 1: Use the Service Menu to Unlock All Bands
Enter the service menu using either way.
Open dialer and enter *#27663368378# to get directly into the service mode main menu.
Open dialer and enter *#73# to get into RF Test mode. Press Band Selection. Press three dots on top right -> Back. Repeat three dots -> back three more times until you get to the service mode main menu.
Use the service mode to set the following options. Note you can go back between screens with three dots -> back for quicker navigation, but I am just starting each option below from the main menu so it's easy to read.
Enable all LTE and 5G bands.
Service Mode Main Menu -> UE SETTING & INFO -> SETTING -> SYSTEM -> Next page 4 times -> SET LTE BAND CONFIG -> SET DEFAULT LTE BAND.
Service Mode Main Menu -> UE SETTING & INFO -> SETTING -> PROTOCOL -> NR5G -> NR5G PRUNE STATUS -> REMOVE NR5G PRUNE.
Service Mode Main Menu -> UE SETTING & INFO -> SETTING -> PROTOCOL -> GCF -> REMOVE ONLY NR WHITELIST.
Optional if you need to enable mmWave bands: Service Mode Main Menu -> UE SETTING & INFO -> SETTING -> PROTOCOL -> NR5G -> Sub6/mmWave -> ALL ENABLE.
Optional if you have issues going from LTE to LTE+ (carrier aggregation not working properly): Service Mode Main Menu -> UE SETTING & INFO -> SETTING -> PROTOCOL -> AS -> Next Page -> DISABLE CA COMBO CHECK -> DISABLE ON.
Enable 5G NR features (DSS & CDRX) if needed. These options might already be enabled for you by default.
Service Mode Main Menu -> UE SETTING & INFO -> SETTING -> PROTOCOL -> AS -> Next Page -> NR CDRX CONTROL -> NR CDRX ENABLE. NR CDRX is 5G power saving mode.
Service Mode Main Menu -> UE SETTING & INFO -> SETTING -> PROTOCOL -> AS -> Next Page 2 times -> NR DSS CONTROL -> NR DSS ENABLE. NR DSS is 5G Dynamic Spectrum Sharing.
Enable 5G SA if you're lucky enough to have a carrier with standalone 5G networks. This option might be enabled by default already.
Service Mode Main Menu -> UE SETTING & INFO -> SETTING -> PROTOCOL -> NR5G -> NR5G SA/NSA Mode Control -> SA/NSA ENABLE.
Service Mode Main Menu -> UE SETTING & INFO -> SETTING -> PROTOCOL -> NR5G -> NR5G SA/NSA Mode Control -> Remove SA permit list.
Service Mode Main Menu -> UE SETTING & INFO -> SETTING -> PROTOCOL -> NR5G -> Next Page -> NR5G NRDC -> NRDC ENABLE. NRDC is for dual connectivity with Sub6 + mmWave bands in parallel. Only applies to 5G SA networks and only if your carrier uses it.
Restart your phone, then dial *#73# to get into RF Test Mode. Click Band Selection -> Sim 1 or Sim 2 (whichever you use). On this screen if you scroll down, you'll see a list of enabled NR5G bands. Make sure all bands are enabled. See my picture below.
NOTE: Band selection won't be reset with a reboot, but might be reset after a CSC update (or a software update that includes a CSC update). You will have to re-do the service menu settings every update or re-flash of a CSC.
NOTE: If you use an eSIM or a dual-SIM phone with a 2nd SIM, you need to change the NR5G stack before changing the NR5G related options above. Change the NR5G stack to Stack 2 with the following setting first.
Service Mode Main Menu -> UE SETTING & INFO -> SETTING -> PROTOCOL -> NR5G -> NR5G STACK SELECTION -> Select STACK 2.
OPTIONAL: Now that all bands are enabled and usable, you can use the Band Selection menu under *#73# to selectively disable certain bands if you need to. This is not covered here but that menu is self-explanatory.
If this method isn't working, try METHOD 2 below. You do not need to try METHOD 2 if this method ended up working for you.
D. METHOD 2: Unlock all bands via Protocol Simulation menu.
If METHOD 1 above didn't work or not all bands were unlocked, you can try to unlock all bands by simulating a change in your CSC to GCF (Global Certification Forum). This won't actually change your CSC to GCF, but will change the options in the service menu as if you were on GCF CSC, which should give you access to all SA and NSA bands. Credits to @wr3cckl3ss1 for figuring out this method.
To do this method, first enter the service mode main menu using either of the following ways.
Open dialer and enter *#27663368378# to get directly into the service mode main menu.
Open dialer and enter *#73# to get into RF Test mode. Press Band Selection. Press three dots on top right -> Back. Repeat three dots -> back three more times until you get to the service mode main menu.
Using the service menu, change the following options
Go to: Service Mode Main Menu -> PROTOCOL STATE -> PROTOCOL SIMULATION -> IMEI PRE CFG SIMULATION.
In this menu, click [1] AP, then click GCF (last option). Then click [2] NET1 and change it to GCF as well. Do the same for [3] NET2. All GCF.
Press [4] Write. Then restart phone.
Check if all SA bands were unlocked. If not, repeat the band unlocking instructions from METHOD 1 above and then restart the phone and check again.
Enjoy your unlocked LTE and 5G bands!
FYI, I have personally tested this on a Canadian S908W on XAA firmware to enable 5G in Canada. In fact, I was even able to update to One UI 5.0 using the adb sideload method since I was on XAA firmware, and then I repeated the steps above to enable all 5G bands on the beta (service menu was still unlocked). So now I have 5G on One UI 5.0 beta in Canada! The trifecta!
CREDITS
@mellojosh for his guide on service menu band options on the S20U1.
@wr3cckl3ss1 for his guide on selecting bands from the dialer for the S22 series phones, and for instructions on protocol simulation.
@bigdave79 for reminding me about needing the Samsung USB Driver for this to work.
Excellent job sir.
i'm on android 13 beta2 on unlocked s22 ultra.
after i click on "DM + MODEM + ADB" then ok,
it' still stuck at Waiting for DIAG....
Great effort man, Thank you.
but this will not work on variants like S908N Korea or the S9080 China correct ?
netnerd said:
i'm on android 13 beta2 on unlocked s22 ultra.
after i click on "DM + MODEM + ADB" then ok,
it' still stuck at Waiting for DIAG....
Click to expand...
Click to collapse
Which CSC are you using and which model (S908U1)?
When I tested this, I unlocked the secret codes first on Android 12, then upgraded to Android 13 and secret codes still worked. I'm not sure if you can unlock it directly on Android 13.
Are you willing to downgrade to Android 12 first to try?
Mem_0 said:
Great effort man, Thank you.
but this will not work on variants like S908N Korea or the S9080 China correct ?
Click to expand...
Click to collapse
Can you flash US firmware on the Korean and Chinese variants with Odin (normal or patched)? If you can get on US firmware, then it might work. I do not think it will work on other firmwares.
peacey8 said:
Can you flash US firmware on the Korean and Chinese variants with Odin (normal or patched)? If you can get on US firmware, then it might work. I do not think it will work on other firmwares.
Click to expand...
Click to collapse
I don't think that's possible as the pit files are different.
peacey8 said:
Can you flash US firmware on the Korean and Chinese variants with Odin (normal or patched)? If you can get on US firmware, then it might work. I do not think it will work on other firmwares.
Click to expand...
Click to collapse
till now there is no way to flash US on a Korean
Mem_0 said:
till now there is no way to flash US on a Korean
Click to expand...
Click to collapse
peacey8 said:
Can you flash US firmware on the Korean and Chinese variants with Odin (normal or patched)? If you can get on US firmware, then it might work. I do not think it will work on other firmwares.
Click to expand...
Click to collapse
The only Snapdragon variant that has the same pit file as S908U/S908U1....is the S908N. But to no avail. It fails.
wr3cckl3ss1 said:
The only Snapdragon variant that has the same pit file as S908U/S908U1....is the S908N. But to no avail. It fails.
Click to expand...
Click to collapse
why does it fail ? bec of different pit files ?
The pit files are what partition the device. And....
S908U/S908U1/S908N have B0Q_USA_SINGLEW
S908E - B0Q_GBL_OPEXX
S908W- B0Q_CAN_SINGLEX
And even if you were to get it to flash. That still won't unlock the bootloader. Just an FYI.
I have made a lot of research and failure tries trying to change the CSC of the S908N I have from KTC to KOO, but every time it fails using Samkey or even Samfw, after further looking they said that Samsung had blocked the Korean variants starting from S21 I guess.
wr3cckl3ss1 said:
The pit files are what partition the device. And....
S908U/S908U1/S908N have B0Q_USA_SINGLEW
S908E - B0Q_GBL_OPEXX
S908W- B0Q_CAN_SINGLEX
And even if you were to get it to flash. That still won't unlock the bootloader. Just an FYI.
Click to expand...
Click to collapse
I don't want to unlock the bootloader at the moment, I just want to change csc at first to KOO instead of KTC and after that maybe install international software.
peacey8 said:
Which CSC are you using and which model (S908U1)?
When I tested this, I unlocked the secret codes first on Android 12, then upgraded to Android 13 and secret codes still worked. I'm not sure if you can unlock it directly on Android 13.
Are you willing to downgrade to Android 12 first to try?
Click to expand...
Click to collapse
yes, I'm on s908U1 with FKR/FKR, TMB/XAA (Visible wireless on sim, tmobile on esim).
if i downgrade to Android 12, will it wipe my data? i really don't wanna wipe my phone
netnerd said:
yes, I'm on s908U1 with FKR/FKR, TMB/XAA (Visible wireless on sim, tmobile on esim).
if i downgrade to Android 12, will it wipe my data? i really don't wanna wipe my phone
Click to expand...
Click to collapse
Yes it might wipe your phone, I'm not sure. I wouldn't risk it without backing up first.
I haven't tested this on FKR. So if it doesn't work for you on Android 12, use SamFW FRP Tool to change your CSC to XAA when you're on Android 12. Then it should definitely work.
Thanks for this.
Question: if I'm on att or TMOB, does this unlock more useable bands for me?
netnerd said:
i'm on android 13 beta2 on unlocked s22 ultra.
after i click on "DM + MODEM + ADB" then ok,
it' still stuck at Waiting for DIAG....
Click to expand...
Click to collapse
I'm having the same issue and I'm on Android 12.
EDIT: I'm an idiot. I did not have the Samsung Android USB drivers installed. Tried it again and now it works!
ekerbuddyeker said:
Thanks for this.
Question: if I'm on att or TMOB, does this unlock more useable bands for me?
Click to expand...
Click to collapse
The phone already comes with all almost all the bands already. This guide just shows you how to enable them all.
Has anyone had any luck, I followed all the step to the T, but it still stuck on "waiting for DIA".
Running androind 12 / SM-S908U1
canada S22U
formula666 said:
Has anyone had any luck, I followed all the step to the T, but it still stuck on "waiting for DIA".
Click to expand...
Click to collapse
Install Samsung Android USB drivers from here.
Recently I had to replace my Samsung Galaxy A32 5G under warranty (losing all my sdcard0 data) because my previous unrooted free T-Mobile A32-5G was frozen, so what I want to do for the future is document, in words, the exact steps to copy data off and to unfreeze & reload new firmware onto the unrooted T-Mobile SM6U I have, for me in the future (if needed) and for others (if they need it).
For the hardware modes below, I'm heavily borrowing from this YouTube video titled
Samsung a32 5g Hard Reboot - Download Mode
But I'm doing all the steps myself and writing them up step by step so they are extremely clear to anyone (and I'm adding information).
Wake
Click power button to wake the phone (assume this fails)
Shutdown or Restart
Hold both volume down & power button to shutdown/restart (assume this fails)
Fastboot Mode
Connect the A32-5G to the Windows PC via USB
C:\> adb devices
C:\> adb reboot-bootloader
In red, "fastboot mode... " shows up on the phone
You can now run fastboot commands, such as:
C:\> fastboot flashing unlock
Debug Mode (mandatory)
Settings > About phone > Software information > Build number (press 7 times)
This enables Developer mode (if you don't already have it enabled)
Settings > Developer options > USB debugging = on
Settings > Developer options > Disable adb authorization timeout = on (otherwise authorization is revoked in 1 to 7 days)
Settings > Developer options > Default USB configuration = Transferring files
Settings > Developer options > Stay awake = off (but know this exists to turn it on if your screen becomes cracked)
Debug Mode (optional)
Settings > Developer options > Wireless debugging = on
Settings > Developer options > Quick settings developer tiles > Wireless debugging = on (that adds a brand new tile to your pulldown area)
Permanently add that new "Wireless debugging" tile to the front of your swipe-down quick tiles since this button goes off whenever Wi-Fi is turned off
Android Recovery Mode
Hold both volume down & power until the screen cycles past the poweroff/restart screen to a black screen and then hold both volume up & power until the phone cycles past the "Secured by Knox" screen and keep holding until you see Android Recovery mode which has the following options, selectable by your volume button and executed when you press the power button with any selection below highlighted.
The screen will be black with orange writings saying "Android Recovery Mode" and the following options...
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
Repair apps
Recovery mode (using the PC)
C:\> adb devices
C:\> adb reboot recovery
That will put your phone into recovery mode
Download mode (aka Odin mode)
With the phone turned off, press & hold the volume up & volume down & power buttons and plug in a USB cable from the PC at the same time as you're pressing the three buttons to put the phone into Download Mode (also known as Odin Mode).
The screen will turn light blue saying...
Warning A custom OS can cause critical problems in phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise press the volume down key to cancel
Volume up = Continue
Volume down = Cancel (reset phone)
Side key = Show Barcode {IMEI, SN, Device ID}
In summary, my last A32-5G was toast because I didn't know to access it from the computer with USB debugging on, nor did I know how to reload the firmware, so I don't want that ignorance to happen to me or to anyone else moving forward - which is why this thread is created so we can all pitch in.
What we need to add to this are the steps to access an A32-5G phone to mirror it over USB using FOSS scrcpy tools when the screen is unresponsive, or at least to copy the data off the sdcard0 but that will be only for those who already had the foresight to set USB debugging on permanently.
1. First let's outline all the ways to get the Galaxy A32-5G into debug mode, odin mode, download mode, factory reset mode, android recover mode, etc. - all of which I tried today.
2. Then let's run through a firmware recovery process using Odin & Samfw - which I have never done so I rely heavily on others.
Note the "official" ODIN is here for flashing stock firmware.
3. Then let's recover Samsung firmware again, this time using Odin & Frija - which I have never done but I will try soon.
4. Then let's cover how to mirror your screen over USB (and later, over Wi-Fi) - which I do all the time.
5. And then let's cover how to mount the Android file system
(both sd cards) over Wi-Fi as Windows drive letters using WebDAV - which I do all the time.
6. Then let's add a section on how to recover your old adb authentication keys if they have expired so that you can again trust the computer.
Linux = ~/.android/{adbkey,adbkey.pub,adb_known_hosts.pb}
Windows = C:\Users\you\.android\{adbkey,adbkey.pub,adb_known_hosts.pb}
macOS = ?
Android: /data/misc/adb/adb_keys
7. I don't know if the A32-5G SM6U can be rooted yet, but if it
can be rooted, I'll likely add a section on how to root it after that.
This is required reading to understand the terminology, all of which is new to me (and likely to those of you who read this).
And this is required reading for the OEM Unlock option.
--
If you've enjoyed it or it has helped you, a thumbs or or thanks is always appreciated! Feel free to share and link to this thread for newbies to messing with Android devices like I am.
Here is how to download firmware using SAMFW & how to flash with Odin. (make sure you get the right odin!)
The assumption is the first post was followed which is to proactively:
1. Turn USB debugging = on
2. Connect by USB cable once to a trusted PC & save the authentication
3. Turn off the automatic release of those authentication keys
4. Set the default USB mode = file transfer
Click to expand...
Click to collapse
WARNING: Everything below is a work in progress for the step-by-step tested procedure to download the firmware for the T-Mobile USA Samsung Galaxy A32 5G using Windows 10 as shown below.
Determine the name, model, and baseband version
Settings > About phone > Model name Galaxy A32 5G, Model number SM-A326U
Settings > About phone > Software information > Baseband version = A326USQS8BVJ1
With that information, get the latest Samsung firmware
Frija is one way to download the latest Samsung firmware
But my first test was with https://samfw.com/
In the SamFW web page on Windows 10, enter the device name or model code = SM-A326U / Galaxy A32 5G
That brings you to here which has hundreds of files, many with the designation "A326USQS8BVJ1" and some for Android 12.
https://samfw.com/firmware/SM-A326U
I'm not sure which "A326USQS8BVJ1" "Android 12" file to pick next (is there any way to intelligently choose from the many that do exist)?
Most (if not all) are USA files, so I arbitrarily selected one of the "AIO" CSC (whatever that means) files and that brings up three files that are for Android 12, the latest being:
Build Date = 20221012183750
Download the firmware flash for Samsung Galaxy A32 5G with the code is SM-A326U. This firmware for the region with CSC code is AIO (AIO - United States). Please make sure the code is correct. You can check model code in Setting - About, in Download mode or you can find it by flipping your phone or among the things you found in the box. This product PDA version is A326USQS8BVJ1 and Android version is S(Android 12). This firmware size is 5.83 GB.
This firmware is official from Samsung Cloud Server. Of course, we recommend you are using official Samsung tool like Samsung Smart Switch or Samsung Kies. Samfw.com will not responsible for any damage caused by using the files on this website
AP VERSION A326USQS8BVJ1
CSC VERSION A326UOYN8BVJ1
ANDROID VERSION S(Android 12)
BIT (BINARY/U/SW REV.) 8
SIZE 5.83 GB Full Files
MD5 9019690daf609d85d21bbf6eccebb9b8
Click to expand...
Click to collapse
That process of creating the firmware took me an hour and perhaps a bit more as it automatically generated a "A326U_AIO_A326USQS8BVJ1_fac.zip" file of 5.83GB size which I then had to manually download when it was finally 100% finished, creating.
Name: Samfw.com_SM-A326U_AIO_A326USQS8BVJ1_fac.zip
Size: 6259616116 bytes (5969 MiB)
SHA256: 89B5CF61033173BAFABBF7E7980F7FE1F8F43D88AD99C82729A4643884E5045B
Can someone advise me as to what's the next step?
OK. This seems to be the next set of steps.
1. Extract (unzip) that Samsung firmware zip archive.
Application Processor (or PDA)
AP_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT_meta_OS12.tar.md5 (6,331,637,961)
Bootloader
BL_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (2,959,548)
Core Processor
CP_A326USQS8BVJ1_CP23036338_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (41,666,760)
Consumer Software Customization
CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (86,405,314)
HOME_CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (86,384,839)
USERDATA_AIO_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (887,490,760)
_FirmwareInfo_Samfw.com.txt (719)
Note that nowadays, the CSC contains the Partition Information Table file (PIT) in most cases, but you might have a PIT file if not.
Also note the difference between the CSC and the HOME_CSC where you can only burn one, not both.
CSC = Updates the firmware using the PIT which means it wipes the device entirely and reformats the super partition containing everything from /boot, /system and /vendor
HOME CSC = updates the firmware but without the PIT file so that it does NOT wipe the device
2. Download the Windows Samsung Odin Tool 3.13.1
Name: Odin3_v3.13.1_3B_Patched_Samfw.com.rar
Size: 1080120 bytes (1054 KiB)
SHA256: 796DBCD0A2262228AF0492B69BCFF0555CDC9AFE422045BC295BB2ABF74FF107
3. Extract that Odin RAR file (I used 7zip).
Name: Odin3 v3.13.1_3B_Patched_Samfw.com.exe
Size: 3172864 bytes (3098 KiB)
SHA256: 1E84628BD5EF44EB6A00954A7DE5445375C953879F889EF82CB73DB0358CEEAF
4. Run that unpacked executable file on Windows with its associated ini file in the same directory to make sure it brings up the Odin GUI which makes no sense to a noob like me. (Need to add more here since this is a critical step in the process which has no good instructions yet). OK. I think I got it. See Odin file upload steps below.
5. Put the Samsung A32-5G into "Download Mode" by holding volume up, volume down, and power and then right away plug in the USB cable from the computer port such that all four are done simultaneously.
Immediately this puts the phone screen blue which is apparently Download Mode (aka Odin Mode) which will say...
Warning A custom OS can cause critical problems in phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise press the volume down key to cancel
Volume up = Continue
Volume down = Cancel (reset phone)
Side key = Show Barcode {IMEI, SN, Device ID}
6. In the Odin tool on Windows 10, you have two use models, the first of which is to add the five BL, AP, CP, CSC, and USERDATA files separately, or together as one HOME_CSC file.
I don't know where to load the HOME_CSC file so I'll load the five BL, AP, CP, CSC & USERDATA files separately into the Windows Odin GUI (the CSC and HOME_CSC being different in that the home version is said to not wipe user data).
In Windows Odin, click the BL button and navigate to the file named BL_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 file.
In Windows Odin, click the AP button and navigate to the file named AP_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT_meta_OS12.tar.md5 (notice this will take a while as this is the largest file).
In Windows Odin, click the CP button and navigate to the file named CP_A326USQS8BVJ1_CP23036338_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
In Windows Odin, click the CSC button and navigate to the file named HOME_CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 or CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (the difference is said to be the HOME version doesn't wipe user data clean).
In Windows Odin, click the USERDATA button and navigate to the file named USERDATA_AIO_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 where the "home_csc" is said to not wipe userdata but the "csc" will wipe user data.
7. Make sure re-partition is NOT ticked in the Windows 10 Odin GUI "Options" tab which has the following settings by default
[x] Auto Reboot
[_] Nand Erase
[_] Re-Partition
[x] F. Reset Time
[_] DeviceInfo (mine is grayed out)
[_] Flash Lock
8. In the Windows 10 Odin GUI, with the phone connected to the Windows 10 PC in blue Download Mode (aka Odin Mode), now click the Odin GUI START button to begin reflashing.
Please improve if/when you test this out as I only ran up to the last steps but I did not actually install the firmware.
Here (will be) how to download firmware using Frija & flash with Odin.
[Frija is the wife of Odin in Norse Mythology.]
WARNING: Everything below is a work in progress for the step-by-step tested procedure to download the firmware for the T-Mobile USA Samsung Galaxy A32 5G using Windows 10 as shown below.
This is a work in progress... to be updated as I test it and document the steps.
Please improve if/when you test this out as I only ran up to the last steps but I did not actually install the firmware.
Here is how to mirror the phone on the desktop over USB or over Wi-Fi using the FOSS scrcpy software.
1. Read the FOSS scrcpy readme explanatory file.
[https://github.com/Genymobile/scrcpy#readme]
The two fundamental steps are
C:\> adb devices
(That should report the adb-name-of-your-android-device.)
C:\> scrcpy -s adb-name-of-your-android-device
(That should mirror your phone onto the PC over USB or Wi-Fi.)
2. Download both the adb & scrcpy commands from this zip file.
[https://github.com/Genymobile/scrcpy]
Note that you can use any adb from anywhere so if you already have adb from Android Studio, then use that if you want to.
3. Turn on USB Debugging & default mode is file transfer.
4. Connect your Galaxy A32-5G to the PC over the USB cable.
The notifications should say "USB for file transfer".
5. For this test, I purposefully turned off Wi-Fi on the phone so that the connection would only be via USB cable.
6. If necessary install Windows drivers to ensure the phone shows up as "Galaxy A32 5G" on the Windows network.
6. Run the adb daemon and obtain your device name over USB.
C:\> adb devices
You should see something like:
ABCD##ABCDE device
x. Run scrcpy to mirror the device onto your Windows 10 PC.
C:\> scrcpy -s ABCD##ABCDE
Where the "1ABCD##ABCDE" is the unique name as reported by adb but if you only had one device connected to the adb daemon, you don't even need that '-s' option; yet it's a good habit to use it.
At this point all the following work seamlessly together
Your PC will show what's on your phone screen.
Your PC mouse will manipulate your phone screen.
Your PC keyboard will type into your phone screen.
Your PC & Android clipboards will be interchangeable.\
Here are some useful things you can do with scrcpy.
To take a movie of the entire session (on either USB or over Wi-Fi):
C:\> scrcpy --record foo.mp4
C:\> scrcpy -r bar.mkv
To perfectly screenshot just the phone window on demand in Windows:
C:\> Irfanview
Irfanview:Options/Capture Screenshot > (o)Foreground window - Client area
File name: capture_$U(%Y%m%d_%H%M%S)_###
(Or you can automatically capture every half second or whatever)
DETAILS:
1. Install adb on Windows as per instructions here.
<https://www.xda-developers.com/install-adb-windows-macos-linux/>
<https://dl.google.com/android/repository/platform-tools-latest-windows.zip>
<https://dl.google.com/android/repository/platform-tools_r31.0.3-windows.zip>
Note you do not need to be root on the phone nor admin on the Windows PC.
Note: You can skip this step if you ONLY want to run scrcpy as
scrcpy comes with its own adb which works fine for that purpose.
2. On the phone, check if you have Developer Mode turned on.
Settings > About phone > Software information > Build number
If you tap once & it says "Developer mode has already been turned on"
then you don't need to tap it 7 times to turn Developer Mode on.
3. On the phone, enable the USB Debugging mode option.
Settings > Developer options > USB debugging = on
4. Connect your phone via USB to the PC & run a quick test.
C:\> adb devices
On Windows you will see some debugging information:
* daemon not running; starting now at tcp:55555
* daemon started successfully
List of devices attached
ABCD##ABCDE unauthorized
On your phone’s screen, you should see a prompt to allow or deny USB Debugging access which you should grant permanently for this computer so that when the screen is broken, it will still connect!
Grant USB Debugging access when prompted (and tap the always-allow check box if you want).
Then run the command again:
C:\> adb devices
List of devices attached
ABCD##ABCDE device
5. From the PC you should now be able to access even the phone root filesystem.
Optional test:
C:\> adb pull /system/etc/hosts .\hosts.txt
[That should copy the Android hosts file over to your Windows machine.]
Find the number of packages you have which have "google" in the name.
C:\> adb shell pm list packages google | find /c /v ""
6. And from the PC, you should now be able to bring up Android Activities.
Optional teset:
Bring up the gms "Reset AD ID" Activity on Android from Windows:
C:\> adb shell am start -n com.google.android.gms/.ads.settings.AdsSettingsActivity
That should pop up the "Reset AD ID" settings page on your phone.
[GMS is a set of "google mobile services" products native on Android.]
You can close that page on Android from Windows by running this:
C:\> adb shell am force-stop com.google.android.gms
Which you can put into a "closegms.bat" one-line file for convenience.
7. Obtain the Windows "Screen Copy" code to mirror the Android screen.
<https://www.khalidalnajjar.com/take-screenshots-of-secure-conversations-on-android/>
<https://github.com/Genymobile/scrcpy>
Save to C:\installer\editor\android\scrcpy\scrcpy-win64-v1.23.zip
Name: scrcpy-win64-v1.23.zip
Size: 35446869 bytes (33 MiB)
SHA256: D2F601B1D0157FAF65153D8A093D827FD65AEC5D5842D677AC86FB2B5B7704CC
Extract to C:\app\editor\android\scrcpy
Note there is an adb.exe which comes with that zip file
You can now interact with your phone using the Windows kebyoard & mouse
11. To record a mirrored Android session as an MP4 video run this:
C:\> scrcpy --record file.mp4
C:\app\editor\android\scrcpy\scrcpy-server: 1 file pushed, 0 skipped. 1.4 MB/s (41123 bytes in 0.027s)
[server] INFO: Device: samsung SM-A326U (Android 11)
INFO: Renderer: direct3d
INFO: Initial texture: 720x1600
INFO: Recording started to mp4 file: file.mp4
Note you can press control+c to end the recording when desired.
14. If desired, use the TCP/IP Wi-Fi connection between Windows & Android which requires the USB connection first, and then you can disconnect after establishing the Wi-Fi connection.
C:\> adb connect 192.168.1.2:5555
Where 191.168.1.2 is the IP address of your phone on your LAN.
C:\> scrcpy
Or you can establish the Wi-Fi connection from the start but this always requires interacting with the screen first.
(WORK IN PROGRESS TO ADD THESE STEPS.)
I do this all the time so I just need to document it.
This is a placeholder work in progress to document the WebDAV solution which enables you to mount the entire Android file system onto Windows 10 as drive letters (one Windows drive letter for each sdcard).
I do this all the time so I just need to document it.
This is a placeholder for recovering old keys if you no longer have the computer trusted and you can no longer access the screen.
Accessing An Android Device With Broken Screen Via ADB and Unauthorized Machine in 2022
Just as a datapoint, while I use a variety of adb implementations, I looked for these stored keys and found the files, albeit they were rather old.
adb shell ls /data/misc/adb/adb_keys
Directory of C:\Users\username\.android
11/25/2022 03:39 PM <DIR> .
11/25/2022 03:39 PM <DIR> ..
12/14/2020 01:27 PM 1,732 adbkey
12/14/2020 01:27 PM 709 adbkey.pub
11/25/2022 03:39 PM 936 adb_known_hosts.pb
08/06/2022 08:16 AM 185 analytics.settings
12/16/2020 12:37 AM <DIR> avd
12/14/2020 04:57 PM <DIR> breakpad
08/06/2022 09:15 AM <DIR> cache
12/14/2020 01:26 PM 2,107 debug.keystore
12/14/2020 01:29 PM 0 debug.keystore.lock
12/16/2020 12:36 AM 4,640 emu-last-feature-flags.protobuf
12/16/2020 12:36 AM 67 emu-update-last-check.ini
12/16/2020 12:37 AM 119 maps.key
12/16/2020 12:36 AM 171 modem-nv-ram-5554
12/14/2020 12:59 PM <DIR> studio
10 File(s) 10,666 bytes
Note that I do not use the adb inside of Android Studio much, since any adb works for what I use it for, so this is probably a feature of AS perhaps?
Do you think _old_ keys would work in an emergency situation?
This is something we should flesh out for the general user.
TimmyP said:
If you have bootloader version 3 or lower (probably not anymore, 5th number from right in baseband version) look at this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a32-5g-mediatek.4286631/
Click to expand...
Click to collapse
I really would like to try to root my T-Mobile Samsung Galaxy SM-A326U.
Unfortunately, my baseband is A326USQS8BVJ1 where the 5th character from the right is {8} (which is a lot bigger than 3).
In Android 12 Settings > About phone > Software information >
Service provider software version =
Current CSC = SAOMC_SM-A326U_OYN_TMB_12_0008TMB
Best CSC for SIM card 1 = TMB
Best CSC for SIM card 2 (if dual SIM is possible) = TMB
Factory CSC that cannot be changed = TMB
The CheckFirm Android app by Bluesion reports
SM-A326U (TMB)
Latest official firmware = A326USQS8BVJ1/A326UOYN8BVJ1/A326USQS8BVJ1
Likewise Windows Frija & BitFrost tools report similar information:
Model = SM A326U
CSC = TMB
Version = A326USQS8BVJ1/A326UOYN8BVJ1/A326USQS8BVJ1
Size = 5970 MB
OS = S(Android 12)
Filename = SM-A326U_2_20221020211950_3bw6oqi4sf_fac.zip.enc4
Windows Frija downloaded that firmware for me which resulted in:
Name: SM-A326U_2_20221020211950_3bw6oqi4sf_fac.zip
Size: 6260154041 bytes (5970 MiB)
SHA256: 04B3FE98BD303DA3F56DB166838E846C82BEC4D2659569C0BE9025764511464D
Unpacked, that resulted in the following set of SM A326U firmware.
Application Processor (or PDA)
Name: AP_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT_meta_OS12.tar.md5
Size: 6331637961 bytes (6038 MiB)
SHA256: DD2A0B508160644462C7717B8FBBB6AC0288CA64B71E524214855395E6AA9CBD
Bootloader
Name: BL_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
Size: 2959548 bytes (2890 KiB)
SHA256: D21FEFE7A3C5F5883F0F74A9FCF05709A97CAFAAC129A255480A2BE4195A1C29
Core Processor
Name: CP_A326USQS8BVJ1_CP23036338_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
Size: 41666760 bytes (39 MiB)
SHA256: D56AD0641F4CAE6E3488CD7842DCEAE91E941091A0E392397A83B8F9ABC92632
Consumer Software Customization (with PIT)
Name: CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
Size: 86405314 bytes (82 MiB)
SHA256: 59EE866BC393D0B3E017712229BDA2F07EA17FB165609D53BE0724EB419291A7
Consumer Software Customization (w/o PIT)
Name: HOME_CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
Size: 86384839 bytes (82 MiB)
SHA256: 865A0563845EA2AB9575C5BDD350A6F07B9B145004B8385DA922CDABAD86E001
User Data (supposedly not used on newer devices)
Name: USERDATA_TMB_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
Size: 861655240 bytes (821 MiB)
SHA256: 7C03E8DA8784F14B6EEC924BF052E6EC30701B3F8FB539F344CD6106E4494FBC
I picked up Windows Frija here.
https://github.com/SlackingVeteran/frija/releases
https://github.com/SlackingVeteran/frija/releases/download/v1.4.4/Frija-v1.4.4.zip
Name: Frija-v1.4.4.zip
Size: 6533283 bytes (6380 KiB)
SHA256: 1067F48DE201E26596F473613CB2CEAC31F1A10550CE6AE352827CCE9FA23161
Unpacked:
Name: Frija.exe
Size: 3445248 bytes (3364 KiB)
SHA256: 76C6E277C9E2D167FCFCF4077D13481111C1750909CDAEFB195480609BC16516
I picked up the BitFrost from here, which does what Frija does.
https://www.ytechb.com/samsung-firmware-downloader/
https://github.com/zacharee/SamloaderKotlin/releases
https://github.com/zacharee/SamloaderKotlin/releases/download/1.0.11/Bifrost_Windows.zip
Name: Bifrost_Windows.zip
Size: 73379150 bytes (69 MiB)
SHA256: 6E8335FD91B0135F92421C54C55D1363D5B246720F492D4B120DB962E8113A40
Unpacked
Name: Bifrost.exe
Size: 462848 bytes (452 KiB)
SHA256: 9A71CF4A6F2C74F15C5C00D9BBB7BE2D68AF3E9A22111D0BAE35BD23713B66AC
Still, I'd love to be able to root this phone (if possible).
I tried the methods to root described here, the first test is
Go to OneClickRoot on any web browser
a. I clicked on "Samsung",
b. and typed the model "SM-A326U",
c. and selected "Galaxy A32 5G (SM-A326U)"
d. Then I selected "Android 12" as the Android version
e. And then pressed on "Verify Device Rootable"
f. It reported "We're Sorry"
"Your Samsung Galaxy A32 5G (SM-A326U) is not rootable."
Then I installed SuperSU on the SM-A326U but it failed.
https://download.chainfire.eu/696/supersu/
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Name: UPDATE-SuperSU-v2.46.zip
Size: 4017098 bytes (3922 KiB)
SHA256: D44CDD09E99561132B2A4CD19D707F7126722A9C051DC23F065A948C7248DC4E
Name: Superuser.apk
Size: 5904943 bytes (5766 KiB)
SHA256: 624B7205B818F1A36877DA0E3575B5B671F4933DFD0FDDF31EE168583C6B2090
Then I installed KingoRoot on both the PC & the SM-A326U, but it too failed to root.
https://www.kingoapp.com/
https://d.kingoapp.com/android_root.exe
https://d.kingoapp.com/default/KingoRoot.apk
Name: android_root.exe
Size: 19128680 bytes (18 MiB)
SHA256: 2F400F0B2FE121B8E5B1415A99DFDA2F5502B7AA2E7002EF6E464F0D587DBA0F
Name: KingoRoot.apk
Size: 6615009 bytes (6459 KiB)
SHA256: E6B2EC7E8663229A0F8DD903D7704CCFDE81F7AE0B1881407E068E63A7F125B8
I've installed Magisk but I'm not sure what the next steps are.
https://f-droid.org/en/packages/com.topjohnwu.magisk/
https://en.wikipedia.org/wiki/Magisk_(software)
https://github.com/topjohnwu/Magisk
Name: Magisk-v25.2.apk
Size: 11278270 bytes (10 MiB)
SHA256: 0BDC32918B6EA502DCA769B1C7089200DA51EA1DEF170824C2812925B426D509
Yet the referenced thread (TWRP for Galaxy A32 5G) implies that we CAN root the SM-A326U where the thread clearly says the SM-A326U US model is supported and the thread even points to a bootloader unlock thread for this USA model over here (Bootloader Unlock for Samsung US/Canada Devices) so this is extremely confusing conflicting information.
This is all very very very confusing.
Either we can root this Galaxy A32-5G SMA326U or we can not root it.
Which is it?
Has anyone been successful with that TWRP/Bootloader unlock process with a bootloader fifth-from-right digit of 8?
NO FOR THE BILLIONTH TIME
TimmyP said:
March 2021 is bootloader 5. The device was rootable though that update. Anything after that no known exploit im sure the people I paid to root mine here would be "advertising" their services if there was.
Click to expand...
Click to collapse
Thanks for the confirmation that anything with a bootloader version of 6 or above (mine is 8) can't be rooted by anyone.
Settings > About phone > Software information > Baseband version = A326USQS8BVJ1
All the articles that say the Galaxy A32-5G can be rooted must have been done using the older bootloader (version 5 or lower).
How to ROOT A32 5G