Database Info

root exploit for the d6603?

Hi guys sorry if this is a dumb question but I've been out of the loop on this.
Has there been a root exploit found for the D6603 Z3's?
I'm using a Xperia Z3 on the Canadian Bell network which is showing the bootloader is locked through the Sony app. I'd like to keep it but if there's nothing yet I might just sell it and get something else.
Thanks in advance.

tinodevoe said:
Hi guys sorry if this is a dumb question but I've been out of the loop on this.
Has there been a root exploit found for the D6603 Z3's?
I'm using a Xperia Z3 on the Canadian Bell network which is showing the bootloader is locked through the Sony app. I'd like to keep it but if there's nothing yet I might just sell it and get something else.
Thanks in advance.
Click to expand...
Click to collapse
Google 'giefroot'
You will need to downgrade to a firmware where the exploit works, but it is easy enough to do and easy enough to run the tool
AFAIK, there is a compatible FTF for your network, find one in the mega collection thread or download one from Xperiafirm

gregbradley said:
Google 'giefroot'
You will need to downgrade to a firmware where the exploit works, but it is easy enough to do and easy enough to run the tool
AFAIK, there is a compatible FTF for your network, find one in the mega collection thread or download one from Xperiafirm
Click to expand...
Click to collapse
Thanks for the info. Does the method still cripple the camera or is there a way to work around this?

tinodevoe said:
Thanks for the info. Does the method still cripple the camera or is there a way to work around this?
Click to expand...
Click to collapse
No, because the method does not involve unlocking the bootloader.
Also, the camera issue when unlocking the bootloader was sorted about a year ago

gregbradley said:
No, because the method does not involve unlocking the bootloader.
Also, the camera issue when unlocking the bootloader was sorted about a year ago
Click to expand...
Click to collapse
Just searching around and it looks like I need to be on 23.0.A.2.93 firmware for the exploit to work.
on my phone the current firmware is 23.0.1.A.5.77 (according to xperiafirm Bell's latest FW is 23.0.1.A.5.77 / R7B)
Is there one of these that I can use to downgrade my phone?
{
"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"
}

tinodevoe said:
Just searching around and it looks like I need to be on 23.0.A.2.93 firmware for the exploit to work.
on my phone the current firmware is 23.0.1.A.5.77 (according to xperiafirm Bell's latest FW is 23.0.1.A.5.77 / R7B)
Is there one of these that I can use to downgrade my phone?
Click to expand...
Click to collapse
The carrier or region should not matter.
As long as you have a 6603 any 6603 FTF will do the job. Make sure you have a 6603 though and not a 6616. I am not to clear on the device models from across the pond and flashing a 6603 rom on 6616 (AT&T device US) will result in bootloop.
Not a problem to fix, but may not enable you to root.

gregbradley said:
The carrier or region should not matter.
As long as you have a 6603 any 6603 FTF will do the job. Make sure you have a 6603 though and not a 6616. I am not to clear on the device models from across the pond and flashing a 6603 rom on 6616 (AT&T device US) will result in bootloop.
Not a problem to fix, but may not enable you to root.
Click to expand...
Click to collapse
Thanks again.
What does the R7B at the end stand for and does that matter when choosing the rom to flash?
sorry to ask one more thing, can you point me in the direction on what to use to flash the rom to an earlier version?

tinodevoe said:
Thanks again.
What does the R7B at the end stand for and does that matter when choosing the rom to flash?
sorry to ask one more thing, can you point me in the direction on what to use to flash the rom to an earlier version?
Click to expand...
Click to collapse
Its just regional and carrier branding, nothing to worry about.
Use flashtool to flash FlashTool Files

gregbradley said:
Its just regional and carrier branding, nothing to worry about.
Use flashtool to flash FlashTool Files
Click to expand...
Click to collapse
bloody shame, I got this far and now I can't seem to be able to get it to root.
I did the firmware downgrade, went smooth.
Now following the steps here: http://www.gizmobolt.com/2015/01/24...-giefroot-rooting-tool-cve-2014-4322-exploit/
I get this message after the giefroot does its thing. It reboots the phone but I end up with the same message on each pass.

Disable antivirus anf firewall.

Alright I've made some progress!
I managed to get my phone rooted. Checked with root checker and its legit! SuperSU is installed.
Now I'm trying to figure out how to install a recovery but no dice.
I downloaded the Z3-lockeddualrecovery2.8.14-RELEASE.installer from here: http://nut.xperia-files.com/
and when running, after selecting the first option for rooted phones with SuperSU, it there are a million error messages adb server is out of date. killing...
at the end it says it worked but I still can't boot into recovery. The phone even shows up within the command prompt when I type adb devices. But adb reboot and key presses don't boot into recovery, it only reboots back into the OS.
Is there another way to flash a custom rom or at least a rooted rom with 5.0/5.1? Ideally I'd like to run Cyanogen on my phone but not sure if its possible without unlocking the bootloader.
Thanks in advance for any advice and help!

You will have to unlock to install CM.
Try rebooting to recovery via NDRUtils app

Yes you are rooted, but I bet you don' t have busybox installed.

TheTeslaCoil said:
Yes you are rooted, but I bet you don' t have busybox installed.
Click to expand...
Click to collapse
Both the giefroot and Dual Recovery installations install Busybox into the correct folder.
Issues normally arise when people try to manually install busybox

gregbradley said:
Both the giefroot and Dual Recovery installations install Busybox into the correct folder.
Issues normally arise when people try to manually install busybox
Click to expand...
Click to collapse
Not true.
Busybox can be installed via a flashable zip without any problems.
And there were people who didn' t had busybox installed after root, RootCheker said busybox is not.installed. Then they flashed the zip and voila. Perfection at it' s best.

TheTeslaCoil said:
Not true.
Busybox can be installed via a flashable zip without any problems.
And there were people who didn' t had busybox installed after root, RootCheker said busybox is not.installed. Then they flashed the zip and voila. Perfection at it' s best.
Click to expand...
Click to collapse
If you follow the NDR thread int he cross device development forum you will see that [NUT] advises not to install busybox manually but to use the NDR installer or NDR flashable zip (Maybe this is what you are referring to)
As this user is having an issue installing dual recovery I would follow the advice the dev of that tool.

gregbradley said:
If you follow the NDR thread int he cross device development forum you will see that [NUT] advises not to install busybox manually but to use the NDR installer or NDR flashable zip (Maybe this is what you are referring to)
As this user is having an issue installing dual recovery I would follow the advice the dev of that tool.
Click to expand...
Click to collapse
Right, he must follow the OP' advice.
In this particular case, that' s the way to go.

Guys, finally after hours of trying everything yesterday figured out my problem. A bloody POS Monoprice usb cable!!
I tried with another usb cable and sure enough it patched everything ok....
So now I have installed a prerooted/recovery version of sony's 5.0 which seems to work fine.
If CM needs to be unlocked, are there any other versions out there that will work with the locked bootloader besides the official sony roms?

tinodevoe said:
Guys, finally after hours of trying everything yesterday figured out my problem. A bloody POS Monoprice usb cable!!
I tried with another usb cable and sure enough it patched everything ok....
So now I have installed a prerooted/recovery version of sony's 5.0 which seems to work fine.
If CM needs to be unlocked, are there any other versions out there that will work with the locked bootloader besides the official sony roms?
Click to expand...
Click to collapse
No

Galaxy S6- Knox Warranty Void 1 (0x0400)

[HELP] Knox Warranty Void tripped while flashing official stock ROM
Hello, just bought a new Galaxy S6 with SFR France firmware. Downloaded and installed my country firmware (Romania) to get rid of SFR bloat. flashed via Odin (Knox was 0), reboot to recovery then it showed error dm-variety failed or something like that. I wiped system and cache, reboot again, waited and configured the settings and just to be sure I rebooted the phone in Odin mode and it showed Knox Warranty Void 1 (0x0400). why did that happened? Didn't try to root or install custom firmware, only official stock firmware from sammobile. anything I can do in this case?

Pray that somebody comes up with a workaround or reset (and nobody will notice it on warranty claim). Similiar thing happened to men since then I use custom ROMs.

I hope someone comes with a solution for this. I'll pay for it. Hate it because it happened to me.

What does that code stand for anyway? (0x0400) is it something like an error code or something?

really? flashing through odin up the knox?? that's new, at least to me...

hajyihia said:
really? flashing through odin up the knox?? that's new, at least to me...
Click to expand...
Click to collapse
Yes. no root, no custom ROMs/kernel/recovery. I only needed a stock official ROM with no carrier bloat whatsoever. and this is what happened.

Addix64 said:
Yes. no root, no custom ROMs/kernel/recovery. I only needed a stock official ROM with no carrier bloat whatsoever. and this is what happened.
Click to expand...
Click to collapse
there has to be something wrong, i had a galaxy S4, and i flashed many stock roms and it never upped the knox....can someone more professional explain or confirm that? because i was planning to flash a stock rom through odin to get the latest update....

hajyihia said:
there has to be something wrong, i had a galaxy S4, and i flashed many stock roms and it never upped the knox....can someone more professional explain or confirm that? because i was planning to flash a stock rom through odin to get the latest update....
Click to expand...
Click to collapse
Every time I install the stock firmware KNOX stays 0x0.
The only time I install the stock firmware is when my phone is in a bootloop.
It works every time--no issues whatsoever.
Odin should be the safest program in the world.

Snowby123 said:
Every time I install the stock firmware KNOX stays 0x0.
The only time I install the stock firmware is when my phone is in a bootloop.
It works every time--no issues whatsoever.
Odin should be the safest program in the world.
Click to expand...
Click to collapse
yeah, that's weird, did you try it on your S6? thanks

I can't post pictures yet so I can show to you. After flashing the ROM, reboot to recovery to perform system wipe..at the bottom of the screen where normally it shows applying the CSC, instead it wrote something like "dm-variety failed". Wiped, reboot to write the new firmware, check odin mode and there it was: Knox Warranty Void 1 (0x0400)

hajyihia said:
yeah, that's weird, did you try it on your S6? thanks
Click to expand...
Click to collapse
I actually own the galaxy s6 edge. I have tried it and have never once gotten a single issue.

No fix for this at all?
Sent from my SM-G920F using XDA Free mobile app

There is no fix at this moment for sure. I also flashed ROM(ania) and other stock roms and never had problems, maybe accidentally you tried to flash the carrier romania rom, not the stock one.
Anyway, there isn't anything you can do at this moment, but at least you can install some custom roms and make this phone fly.

http://www.sammobile.com/firmwares/download/54541/G920FXXU2COH2_G920FOXX2COH2_ROM/ this is the ROM I flashed. it's not my first time flashing with Odin. had the S4, Note 3 and Note 4, never had problems while flashing official stock ROMs.
{
"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"
}

Weird, i saw some people also saying that they triped knox flashing stock roms. I don't really know the technical details about s6 but my only ideea is that your SFR rom had a different partition scheme(usually carrier roms have different PIT files) and installing a stock rom which also has a different partition scheme and maybe that''s what triggered the knox. I bought mine directly unlocked from emag and i can freely flash stock roms.
Your phone was locked and then unlocked via code or you bought it directly unlocked?

Phone was locked and unlocked via code. I use it on Digi Mobil network.
Sent from my SM-G920F using XDA Free mobile app

If I flash the SFR rom back, will it do something to the knox flag?
Sent from my SM-G920F using XDA Free mobile app

No Adi, it won't. Sorry.
Sent from my SM-G920F using Tapatalk

Well..bad luck. gonna have to wait for a fix.

Addix64 said:
Well..bad luck. gonna have to wait for a fix.
Click to expand...
Click to collapse
Which will never come, since the Knox counter is an eFuse, so once it is set to 0X1, then only Samsung can set it back to 0 (probably by replacing HW or the mainboard).

[Q] Can we Downgrade SM-G930FD from 7.0 to 6.1 ????????

Can we downgrade SM-G930FD from 7.0 to 6.1. dual sim india model exynos.
not rooted ever
stock rom
bootloader locked.
if i simply flash 6.1 firmware from odin will it brick my device as i guess bootloaders are different in 7 and 6.

When you flash with Odin you should be flashing 4 files (AP, BL, CP, CSC) one of which is the bootloader (BL). So long as you download the correct BL for MM6.1 it should be fine.

Is downgrade possible ? i read somewhere that we cant downgrade because of the new locked bootloader. can some experienced person shed light on this ?

That might be true for the US models, but the 930F and 930FD bootloaders are unlockable.
Also correct me if I'm wrong, but flashing stock firmware is meant to work even if the bootloader is locked. It's only custom firmware that should be a problem.

mor_1228 said:
Can we downgrade SM-G930FD from 7.0 to 6.1. dual sim india model exynos.
not rooted ever
stock rom
bootloader locked.
if i simply flash 6.1 firmware from odin will it brick my device as i guess bootloaders are different in 7 and 6.
Click to expand...
Click to collapse
Can confirm this works, did it like a week ago on my SM-G930F.
Just be sure to flash AP,BL,CP and CSC, as @Beanvee7 mentioned

jaannnis said:
Can confirm this works, did it like a week ago on my SM-G930F.
Just be sure to flash AP,BL,CP and CSC, as @Beanvee7 mentioned
Click to expand...
Click to collapse
so u mean to say. i can flash 6.1 on 7.0 with locked bootloader just by simply flashing all these files in odin ?

mor_1228 said:
so u mean to say. i can flash 6.1 on 7.0 with locked bootloader just by simply flashing all these files in odin ?
Click to expand...
Click to collapse
Am pretty sure, but you will lose your files as you cant take the home_csc to downgrade (I believe??). Why not just try? Backup your stuff and in worst case just flash the 7.0 back.

jaannnis said:
Am pretty sure, but you will lose your files as you cant take the home_csc to downgrade (I believe??). Why not just try? Backup your stuff and in worst case just flash the 7.0 back.
Click to expand...
Click to collapse
but if i bricked my device then ?

mor_1228 said:
but if i bricked my device then ?
Click to expand...
Click to collapse
G930FD can use G930F firmware, I have successfully flashed from 7.0 to 6.0.1 a couple of times on my G930F
You will need to use CSC not HOME_CSC as nothing from 7.0 will work with 6.0.1 and you'll either bootloop or get lots of app crashes on boot

*Detection* said:
G930FD can use G930F firmware, I have successfully flashed from 7.0 to 6.0.1 a couple of times on my G930F
You will need to use CSC not HOME_CSC as nothing from 7.0 will work with 6.0.1 and you'll either bootloop or get lots of app crashes on boot
Click to expand...
Click to collapse
where will i get this csc and not home csc

{
"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"
}
i got this from g930fd file. so in this
i should not use home_csc and should use all other files ?

mor_1228 said:
i got this from g930fd file. so in this
i should not use home_csc and should use all other files ?
Click to expand...
Click to collapse
Already been explained to you, use CSC and not HOME_CSC, yes all the others too

*Detection* said:
Already been explained to you, use CSC and not HOME_CSC, yes all the others too
Click to expand...
Click to collapse
i read in other threads people are facing issues after downgrading like apps behaving funny camera not working . did u also faced the same ?

mor_1228 said:
i read in other threads people are facing issues after downgrading like apps behaving funny camera not working . did u also faced the same ?
Click to expand...
Click to collapse
Did you read anything I wrote?
You made this thread 2 weeks ago, you could have tested it yourself many times by now
Either try it or don't

If you flash all 4 files you should have no issues.
Issues like you described are when people change android version using TWRP flashing ROM's, then they end up with bootloader mismatches etc.
That can't happen to you because you're cleanly flashing all 4 firmware files to a matching version.

*Detection* said:
Did you read anything I wrote?
You made this thread 2 weeks ago, you could have tested it yourself many times by now
Either try it or don't
Click to expand...
Click to collapse
its better to know the + - before flashing anything. flashing anything like stupid and crying later is not what i need. u r most welcome to help.
can i use ? Odin3_v3.10.6 or ODIN 3.12.3 ?????

mor_1228 said:
its better to know the + - before flashing anything. flashing anything like stupid and crying later is not what i need. u r most welcome to help.
can i use ? Odin3_v3.10.6 or ODIN 3.12.3 ?????
Click to expand...
Click to collapse
All the information is already here on XDA S7 forums many times over in many different threads, if you read some threads
No need for multiple ? either, we can see one just fine

Use the latest odin, there's a full update guide on updato.com with a link to the latest version of odin

i am back on 6.0.1 on december build.
but feels bit laggy and battery drain alot android OS.
is there any better version that i can flash rather than december build.
when i got the new device my mobile was fast and good battery life.
my device is manufactured of july 2016 so i guess the firmware must be pre installed of earlier than july.
so is there any firmware 6.0.1 which is faster than other build or is it a myth only ?

The differences between months would mostly be security updates, I doubt there is any major under the hood changes that would impact performance. Did you phone come with carrier bloat originally? Could be that you just need to debloat.

Is it possible to Flash SM-G955W firmware on SM-G955U

As the title says, Is it possible to Flash SM-G955W firmware on SM-G955U from sammobile.
PhoneInfo app screenshots:
General/Model:
{
"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"
}
CSC Code:
Firmware:

_abc said:
As the title says, Is it possible to Flash SM-G955W firmware on SM-G955U from sammobile.
PhoneInfo app screenshots:
General/Model:
CSC Code:
Firmware:
Click to expand...
Click to collapse
i know the samfail partcyborg rom does it

TheMadScientist said:
i know the samfail partcyborg rom does it
Click to expand...
Click to collapse
Thanks for the reply. I searched on xda and it seems it will most likely trip knox. Is it possible with the official firmware from sammobile using odin?

_abc said:
Thanks for the reply. I searched on xda and it seems it will most likely trip knox. Is it possible with the official firmware from sammobile using odin?
Click to expand...
Click to collapse
Partcyborg rom does not trip knox as it does not unlock the bootloader

TheMadScientist said:
Partcyborg rom does not trip knox as it does not unlock the bootloader
Click to expand...
Click to collapse
A..are you serious?

turboedm said:
A..are you serious?
Click to expand...
Click to collapse
Yes as the boot-loader is not unlocked Knox is not tripped on snapdragon S8s we do not have twrp or custom roms besides the one....
But as we have locked boot-loaders that is a perk to it as Knox is nearly untrippable

TheMadScientist said:
Yes as the boot-loader is not unlocked Knox is not tripped on snapdragon S8s we do not have twrp or custom roms besides the one....
But as we have locked boot-loaders that is a perk to it as Knox is nearly untrippable
Click to expand...
Click to collapse
Doesn't root break samsung pay though? That ROM comes pre-rooted.

turboedm said:
Doesn't root break samsung pay though? That ROM comes pre-rooted.
Click to expand...
Click to collapse
That it does it does break pay

I have never went through the csc switch so i do not know the exacts to it but it could be as easy as just flashing the u1 firmware and which you pick determined by which bootloader your on now

TheMadScientist said:
That it does it does break pay
Click to expand...
Click to collapse
Yeah, Samsung Pay is used on a daily basis for me. Unfortunately I can't use a custom ROM if it's rooted

Most people go from W to U not the other way but I dont see why it wouldnt work

TheMadScientist said:
Yes as the boot-loader is not unlocked Knox is not tripped on snapdragon S8s we do not have twrp or custom roms besides the one....
But as we have locked boot-loaders that is a perk to it as Knox is nearly untrippable
Click to expand...
Click to collapse
How do I tell if the boot loader is locked or not? I booted to Download mode at it doesn't say anything about boot loader there.

_abc said:
How do I tell if the boot loader is locked or not? I booted to Download mode at it doesn't say anything about boot loader there.
Click to expand...
Click to collapse
They are all locked all the us snapdragons and ws only china and exynos has unlockable
There is basically nothing you can do to trip knox
All of us that test and those that dev
I have tested some pretty righteous stuff and still no knox trip Infact mine is currently on its way to the repair center for stuff I flashed just testing some theory out..... but it was major stuff not just with the rom or anything I dont want to scare you....

Trying this
Hi there,
So I am trying exactly this (flashing an SM-G955U with firmware for SM-G955W). My reason for doing this is I am hoping that it will improve the reception since SM-G955W is the Bell Mobility firmware and I am on Bell Mobility in Canada.
I have tried Odin 3.13.1 and 3.12.5. I got my firmware from SamMobile.com. This is the link to the exact firmware I downloaded:
https://www.sammobile.com/firmwares/galaxy-s8-plus/SM-G955W/BMC/download/G955WVLU5BRG4/230118/
I put my device into bootloader (power off, power on with Power+Bixby+Volume Down) and when I try to flash I get FAIL! SHA256 is invalid in Odin.
Any suggestions? Am I missing something?
I do not want to root my device. Just flash with stock firmware to re-brand it for the carrier I am using. I want this phone to be as if I purchased it from Bell directly if at all possible. Or should I be using the generic "Canada (XAC)" firmware instead of the BMC firmware? I can get the XAC firmware here:
https://www.sammobile.com/firmwares/galaxy-s8-plus/SM-G955W/XAC/download/G955WVLU5BRG4/230670/
OK, slight update on this. If I use the PrinceComsey edition or Odin found here:
https://drive.google.com/file/d/1dzNPNe2SPVPr2FR1R9aPmbiENajzRsMN/view?usp=sharing I can get it loading but it loads to my phone real quick (doesn't seem like it transfers everything) and then reboots and my phone is still running the same firmware (with all my apps installed, etc) as before.
Thanks,
The Fish

I recently went from bootloader 5 G955u to g955w. Phone was carrier unlocked. Need a combination rom and a rom from your desired canadian cell provider with same bootloader version.
Follow the carrier switching steps. Then follow the flashing standard firmware steps.
https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255

avo1213 said:
I recently went from bootloader 5 G955u to g955w. Phone was carrier unlocked. Need a combination rom and a rom from your desired canadian cell provider with same bootloader version.
Follow the carrier switching steps. Then follow the flashing standard firmware steps.
https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
Click to expand...
Click to collapse
I am really interested in how you did this. I keep getting a fail at step 13 in the "Carrier Switching" section. The only thing I can think of is that I am using 3.13.1 and his guide says (under step 6) that I should be using Odin 3.12.7 but I am using the one from the download links the author provides in his post.
The failure message I get on my phone itself is SW REV CHECK FAIL: [abl]Fused 5 > Binary 2 which makes me think this has something to do with the bootloader being at version 5?
Any tips would be greatly appreciated!!
The Fish

thefish123 said:
I am really interested in how you did this. I keep getting a fail at step 13 in the "Carrier Switching" section. The only thing I can think of is that I am using 3.13.1 and his guide says (under step 6) that I should be using Odin 3.12.7 but I am using the one from the download links the author provides in his post.
The failure message I get on my phone itself is SW REV CHECK FAIL: [abl]Fused 5 > Binary 2 which makes me think this has something to do with the bootloader being at version 5?
Any tips would be greatly appreciated!!
The Fish
Click to expand...
Click to collapse
OK, just to answer my own question(s) and document this for Google. I successfully carrier switched my SM-G955U to Bell and it now reports that it actually is an SM-G955W.
You need version 5 of everything (boot loader, factory ROM, HOME_CSC, etc). You also need to use the new “3b” Patched Odin 3.13.1 by realbbb available here:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572. Otherwise I could not flash the HOME_CSC file.
Basically you can follow the instructions here:
https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
But replace the references to Prince Comsy Odin with the 3b patched Odin. In fact I think you can use 3b patched Odin in place of “standard” Odin as well.
Regards,
The Fish

Question SM-A326U Combination Firmware

US Combination Firmware link for Galaxy A32 5G
Supposedly you can FRP bypass or OEM unlock based on what I've heard
Google Drive - Virus scan warning
drive.google.com

TypicalGellert said:
US Combination Firmware link for Galaxy A32 5G
Supposedly you can FRP bypass or OEM unlock based on what I've heard
Google Drive - Virus scan warning
drive.google.com
Click to expand...
Click to collapse
Have you tested this approach? If yes, then can you provide instruction.
TIA

furballi said:
Have you tested this approach? If yes, then can you provide instruction.
TIA
Click to expand...
Click to collapse
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

TypicalGellert said:
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
Click to expand...
Click to collapse
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

TypicalGellert said:
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
Click to expand...
Click to collapse
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.

TypicalGellert said:
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
Click to expand...
Click to collapse
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/

TypicalGellert said:
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
Click to expand...
Click to collapse
You have to use a patched version of Odin.

TypicalGellert said:
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
Click to expand...
Click to collapse
TMK is T-Mobile not unlocked varient.

Crossflashing to unlocked/bloat-free firmware works just fine.

gamer765 said:
Crossflashing to unlocked/bloat-free firmware works just fine.
Click to expand...
Click to collapse
More info please? Were you able to flash a different firmware on a Tmobile device and unlock bootloader with it?
If yes, can you confirm that the phone works fine and give the rest of us step by step instructions?

gamer765 said:
Crossflashing to unlocked/bloat-free firmware works just fine.
Click to expand...
Click to collapse
Did you crossflash to A326U1 XAA firmware?
how did you managed to do that without unlock bootloader

financeledger said:
Did you crossflash to A326U1 XAA firmware?
how did you managed to do that without unlock bootloader
Click to expand...
Click to collapse
ODIN, You never have to be bootloader unlocked for that on Samsung Devices.

hyelton said:
ODIN, You never have to be bootloader unlocked for that on Samsung Devices.
Click to expand...
Click to collapse
then i am missing something i am trying with Odin to flash the A326u1 XAA and get only fail.
pressing Volumey kesyw while inserting usb i never get into DL mode for flashing

Don't PM me please.
{
"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"
}

gamer765 said:
Don't PM me please.
Click to expand...
Click to collapse
Wont get pms if you share info
Did you use combination from this thread?

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.

gamer765 said:
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.
Click to expand...
Click to collapse
newb here just wanted to make sure it was same steps thanks for that

(OS11/Sprint/SPR)
(OS11/MetroPCS/TMK)
(OS11/US Cellular/USC)
(OS11/T-Mobile/TMB)

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.

tavella said:
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
Click to expand...
Click to collapse
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