Search This thread

bigfry

Member
Mar 31, 2010
16
4
bricked im on the same roadif you find way out let me know

edit : just debricked real easy using odin 3b patch last version and A326USQU2AUD9_A326UOYN2AUD9_TMB
I'm fairly confident the problem here is the bootloader version. The file that worked to restore your phone has the V2 bootloader, and the XAA firmware is a V1 bootloader. I just tried the same on my up to date A32 5g and got the same results - the XAA load bombed out, and the error screen popped up on reboot. Loading the TMB firmware worked just fine.

I have two more A32 5g that should still be factory images with no updates. I'll try to find some time to do the same process to one of them tomorrow and verify if that's the difference. My limited research indicates that Samsung created some new hurdles to jump through with the updated bootloader in the last OTA update.
 
  • Like
Reactions: financeledger

financeledger

Senior Member
May 31, 2021
140
24
I'm fairly confident the problem here is the bootloader version. The file that worked to restore your phone has the V2 bootloader, and the XAA firmware is a V1 bootloader. I just tried the same on my up to date A32 5g and got the same results - the XAA load bombed out, and the error screen popped up on reboot. Loading the TMB firmware worked just fine.

I have two more A32 5g that should still be factory images with no updates. I'll try to find some time to do the same process to one of them tomorrow and verify if that's the difference. My limited research indicates that Samsung created some new hurdles to jump through with the updated bootloader in the last OTA update.
yes thats the cause
 
  • Like
Reactions: bigfry

bigfry

Member
Mar 31, 2010
16
4
Just to touch base, yes, the bootloader was the problem. An A32 5g with the V1 bootloader can be flashed to the XAA firmware no problem. It does not enable unlocking the bootloader as mentioned in another thread on here. I attempted OPs combination firmware and can't get anywhere with it at all, Odin gives me "Re-Partition operation failed." and the phone itself reports "Please get the approval to use factory binary (Pit)". I've tried a couple different Pit files, different combinations of files, and following a couple guides that are supposed to bypass the error, but gotten nowhere, and that's about it for my limited knowledge on the matter.

The phone still works, and is de-bloated, but I was hoping to get root, and that hasn't happened as of now.
 
  • Like
Reactions: financeledger

financeledger

Senior Member
May 31, 2021
140
24
Just to touch base, yes, the bootloader was the problem. An A32 5g with the V1 bootloader can be flashed to the XAA firmware no problem. It does not enable unlocking the bootloader as mentioned in another thread on here. I attempted OPs combination firmware and can't get anywhere with it at all, Odin gives me "Re-Partition operation failed." and the phone itself reports "Please get the approval to use factory binary (Pit)". I've tried a couple different Pit files, different combinations of files, and following a couple guides that are supposed to bypass the error, but gotten nowhere, and that's about it for my limited knowledge on the matter.

The phone still works, and is de-bloated, but I was hoping to get root, and that hasn't happened as of now.
you NEED to unlock bootloader for root first. but make sure your on V1 Bootloader for twrp to work
Also use Odin3B modded
 

Metconnect2000

Senior Member
Dec 5, 2015
118
16
Moto G 5G
Just to touch base, yes, the bootloader was the problem. An A32 5g with the V1 bootloader can be flashed to the XAA firmware no problem. It does not enable unlocking the bootloader as mentioned in another thread on here. I attempted OPs combination firmware and can't get anywhere with it at all, Odin gives me "Re-Partition operation failed." and the phone itself reports "Please get the approval to use factory binary (Pit)". I've tried a couple different Pit files, different combinations of files, and following a couple guides that are supposed to bypass the error, but gotten nowhere, and that's about it for my limited knowledge on the matter.

The phone still works, and is de-bloated, but I was hoping to get root, and that hasn't happened as of now.
How do you check the bootloader version?
 

elliwigy

Retired Forum Moderator / Recognized Developer
XDA App Taskforce
¿Cómo desbloqueaste el gestor de arranque para poner combinación

Translated by GT: How did you unlock the bootloader to put combination
hopefully you guys figured it out by now but to clear things up...

- A326U, A326U1 and A326W can be cross flashed using patched ODIN meaning you can flash U1 (XAA) firmware onto a U or W model and so forth.

- A326U, A326U1 and A326W cannot be bootloadee unlocked unless on rev1 firmware using paid service.

- A326U, A326U1 and A326W (or any Samsung for that matter) cannot downgrade firmware meaning you cannot be on rev2 then try to flash rev1 firmware hence before someone posted an error something like "SW Rev Check Fail Fused 2 > 1" which means it was on rev2 trying to flash rev1 firmware which isnt possible.

- On newer devices you cannot flash factory/combibation firmware without a token which again can only be obtained via a paid service, this is even when your bootloader is unlocked (if you unlocked via paid service.) Hence why the person posted an error that said something like "please get approval to use factory binary".
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I am also going to try using Frija to download the TMK version which is apparently another US unlocked variant Firmware to see if that might flash and go from there
    Thanks. Will post if I find a solution.

    T Mo and Samsung are not playing nice. I was able to completely remove the T Mo app with the Samsung A21, but no luck with the A32 5G (using ADB). Also removed over 200 junk apps from the A32 5G. My goal was to get it as bare-bone as the A21. Yet the A32 still pull about 1.3 GB of RAM vs. 930 MB for the A21, with the major difference being Android 11 vs. Android 10. Apparently, the claim about better memory management in Android 11 does not pan out in actual use. The Android 6 in my ZTE V8 Pro is lightning fast compared to Android 11.

    Most people are not aware of the tremendous amount of spyware that are hidden on these Samsung phones (Amazon, Microsoft, etc). The OS is free, but informed users should have the option to easily remove these junk apps with a few keystrokes.
    2
    I tried last night but it wouldn't flash Odin kept failing it, so I'm going to try to find a different combo Firmware and re-up with the new link to it once I know the new one works.... In the meantime y'all could try that to see if you get a different result with flashing it
    I'm new to this device and still figuring things out. Meanwhile, came across this post that gives different versions of Odin to try with. https://www.droidwin.com/create-samsung-combination-firmware-flash-it-via-odin/
    2
    Did nothing special, same procedure as with all other Samsung phones. Flash U1 firmware on top of U firmware. Don't see what's so difficult about it. @hyelton also mentioned how he did it as well.
    1
    Using Odin Patched 3B v3.14.1 and I’m receiving a truncate message stating the following:

    sw rev check fail [vbmeta[fused 2 > bi

    I’m using the SM-A326U1 for Product Code TMB from April 19, 2021. The phone now boots up with a blue screen ”An error has occurred while updating the device software”. Any suggestions?

    CSC seems to fail at boot.img per Odin
    CSC_HOME fails at preloader.img

    ——— Update ——-
    Flashed latest TMK using Patched Odin 3.14.1 and the device is functional again.
    1
    Using Odin Patched 3B v3.14.1 and I’m receiving a truncate message stating the following:

    sw rev check fail [vbmeta[fused 2 > bi

    I’m using the SM-A326U1 for Product Code TMB from April 19, 2021. The phone now boots up with a blue screen ”An error has occurred while updating the device software”. Any suggestions?

    CSC seems to fail at boot.img per Odin
    CSC_HOME fails at preloader.img
    bricked im on the same roadif you find way out let me know

    edit : just debricked real easy using odin 3b patch last version and A326USQU2AUD9_A326UOYN2AUD9_TMB
    debricka32.png