Database Info

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).

Odin fails galaxy S7 SM-G930T

I've got a Galaxy S7 (SM-G930T) that I'm trying to flash the firmware to get around FRP
{
"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"
}
That is the firmware I'm using
I'm using the Home CSC
When I run Odin it says
and the phone says
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE
RP SWREV: B3(2, 1, 1, 1, 1 ) K1 S2
SECURE DOWNLOAD: ENABLE
SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
[1] eMMC write fail : aboot
and when i use the CSC it says
and says the same stuff on the phone
Can anyone help?

Is your device OEM Unlocked?

Technic_Guy said:
Is your device OEM Unlocked?
Click to expand...
Click to collapse
I don't know

Horizon41 said:
I don't know
Click to expand...
Click to collapse
If not, then go to Settings and enable Developer Options and search for "OEM Unlock". Enable it and try again flashing with Odin

Technic_Guy said:
If not, then go to Settings and enable Developer Options and search for "OEM Unlock". Enable it and try again flashing with Odin
Click to expand...
Click to collapse
the phone doesn't boot

bump

Horizon41 said:
bump
Click to expand...
Click to collapse
bumping as well. i have the exact same issue.
Addition: my phone is able to flash the stock boot img just fine. Still doesn't boot.

Horizon41 said:
bump
Click to expand...
Click to collapse
ebercon said:
bumping as well. i have the exact same issue.
Addition: my phone is able to flash the stock boot img just fine. Still doesn't boot.
Click to expand...
Click to collapse
I had this issue too and it is because you turned OEM unlock off or did not turn it on in the first place.
If flashing Stock Firmware onto your phone is not working, then download the latest Samsung Kies version onto your laptop. Sync your phone and go onto Firmware Upgrade and Initialisation. * This will unfortunately get factory reset your phone so use this method if you have nothing to lose *
Type in your serial number and model number and it will update your phone to the latest software in your region.
Hopefully you guys use Samsung Cloud and/or SmartSwitch and get your data back swiftly.
**I will be honest, I did not write my serial number down anywhere and as I couldn't boot my phone up to find out what it was the only other option was to take the back of my phone off, but there was no way I was going to do that! I was legit ****ting myself thinking I was never getting my phone back ._.
So I typed is S7 serial number on Google Images and typed it into Kies and it worked by some miracle. BUT when the update was done and it came to me setting my phone up as if it was brand new my phone thought i was from Poland lol! ***
Anyways, Good luck

Some of the new phones have the imei microprinted on the removable tray for the sim card. use a magnifier to read it.

Horizon41 said:
I've got a Galaxy S7 (SM-G930T) that I'm trying to flash the firmware to get around FRP
That is the firmware I'm using
I'm using the Home CSC
When I run Odin it says
and the phone says
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE
RP SWREV: B3(2, 1, 1, 1, 1 ) K1 S2
SECURE DOWNLOAD: ENABLE
SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
[1] eMMC write fail : aboot
and when i use the CSC it says
and says the same stuff on the phone
Can anyone help?
Click to expand...
Click to collapse
Yes your bootloader has security check B3 and you are trying to flash a B2 bootloader, you cannot downgrade!!sorry

FRP locked S7

My uncle bought 2 S7 from ebay to India for me.
One of them has FRP locked and the seller can't obviously give me his gmail to unlock it.
Is there anything I can do to bypass it or do I have to send it back to USA?

Aakarsh99 said:
My uncle bought 2 S7 from ebay to India for me.
One of them has FRP locked and the seller can't obviously give me his gmail to unlock it.
Is there anything I can do to bypass it or do I have to send it back to USA?
Click to expand...
Click to collapse
Flash combination firmware then flash back to stock software using home csc

kpwnApps said:
Flash combination firmware then flash back to stock software using home csc
Click to expand...
Click to collapse
am not sure if it has oem unlocking enabled :3

FRP lock on B4 and DRK Issues
I'm also encounter FRP Lock. SM-G930F
After one year of flashing and modding I have it for the first time and I don't now why. I remove every account before change room.
Before thats happend I was on TeamExyKings Note FE 9 Port
But I have missing IMEI problem and I go through standard steps
(Don't do this step if you not sure what you risk) Go to revovery and clean /efs partition
Flash combination firmware I have newest with U4 COMBINATION_FA60_G930FXXU4ASA2.zip
then Flash flash latest original firmware SM-G930F_1_20190307135001_4lzy042ysi_fac.zip
but because I have DRK Issue, after firmware boot up ang go to erasing phase then reboot and show "no command" on blue screen
When that happens I usually flash go with steps below:
flash twrp
repair data to remove encryption
no-verify zip script to bypass DRK
flash some rom and have clean working phone..
Now I've done the same but after adding Google account and syncing and app updates phone reboots and show pink words ( I don't remember what they ware)
I've red on others post that usually steps were
Flash combination
factory reset from inside and flash original firmware .
Bootloader still have FRP: ON
when try to flash twrp i have : custom binary block by frp lock
Now all its run on my phone is Custom binary with wifi without root because Kongoroot and cf-root don't work.
Can some one help me ?

jaqjacek said:
I'm also encounter FRP Lock. SM-G930F
After one year of flashing and modding I have it for the first time and I don't now why. I remove every account before change room.
Before thats happend I was on TeamExyKings Note FE 9 Port
But I have missing IMEI problem and I go through standard steps
Go to revovery and clean /efs partition
Flash combination firmware I have newest with U4 COMBINATION_FA60_G930FXXU4ASA2.zip
then Flash flash latest original firmware SM-G930F_1_20190307135001_4lzy042ysi_fac.zip
but because I have DRK Issue, after firmware boot up ang go to erasing phase then reboot and show "no command" on blue screen
When that happens I usually flash go with steps below:
flash twrp
repair data to remove encryption
no-verify zip script to bypass DRK
flash some rom and have clean working phone..
Now I've done the same but after adding Google account and syncing and app updates phone reboots and show pink words ( I don't remember what they ware)
I've red on others post that usually steps were
Flash combination
factory reset from inside and flash original firmware .
Bootloader still have FRP: ON
when try to flash twrp i have : custom binary block by frp lock
Now all its run on my phone is Custom binary with wifi without root because Kongoroot and cf-root don't work.
Can some one help me ?
Click to expand...
Click to collapse
Why'd you even think clearing EFS partition is a good idea? :/

iOrpheus06 said:
Why'd you even think clearing EFS partition is a good idea? :/
Click to expand...
Click to collapse
I know it's not good idea but if you don't have IMEI and no serial number its only way I know to have it back. Outside backup that I have but I need twrp to flash it

jaqjacek said:
I know it's not good idea but if you don't have IMEI and no serial number its only way I know to have it back. Outside backup that I have but I need twrp to flash it
Click to expand...
Click to collapse
You don't have to mess up your efs by wiping it clean just to get your IMEI back because flashing stock firmware alone is usually enough to fix IMEI issues. Posting this to prevent confusions that may lead to serious problems.

iOrpheus06 said:
You don't have to mess up your efs by wiping it clean just to get your IMEI back because flashing stock firmware alone is usually enough to fix IMEI issues. Posting this to prevent confusions that may lead to serious problems.
Click to expand...
Click to collapse
I've edited my post to avoid any more unnecessary conversation.
My IMEI problems are not not ordinary. Before FRP lock on every rom my IMEI wen't and go back according to moon cycles. Probably hardware issues.
Now please if you have any advice how to fix FRP Lock on B4 booloader from inside COMBINATION rom or from download mode i'm all ears.

jaqjacek said:
I've edited my post to avoid any more unnecessary conversation.
My IMEI problems are not not ordinary. Before FRP lock on every rom my IMEI wen't and go back according to moon cycles. Probably hardware issues.
Now please if you have any advice how to fix FRP Lock on B4 booloader from inside COMBINATION rom or from download mode i'm all ears.
Click to expand...
Click to collapse
Flashing all stock (CSC and not Home_CSC) has always worked for me from the beginning till today (last frp **** happened 3 weeks ago) and yeah my IMEI is still there.
Flashing old ROMs and flashing OLDER cp version can mess up your IMEI. That happened to me about a year ago and all I ever had to do was to flash stock rom (from whichever source you trust) via Odin.
It's the cleanest and safest way to get rid of FRP lock imo. I don't even know why anyone would bother using a combination rom as they require more effort to get your phone to work as intended.
Again, just put your phone into download mode, plug it into a PC, download stock firmware (from Sammobile, Samfirm, updato, or whichever source you trust), open Odin, and flash it there.
At least, this should work fine if you still have your efs partition working fine.

jaqjacek said:
Can you give some steps to follow ?
Click to expand...
Click to collapse
You cant repair efs without a backup. If you really deleted the efs partition no go back anymore without touching the motherboard.
And flashing firmware wont reset frp

Flashed 4 different Original firmware with CSC or HOME_CSC already.
That isn't a problem. firmware show android and erasing phase
Problem is*that after 25% Erasing ste and second reboot Phone stack on "no command" screen stays on it for a while and reboot itselfs and do the same over and over again.
I've reed somewhere thats are DRK issues I'm not a expert in this but usually i flash twrp then install no-verify zip and phone goes buck to live.
Now I have something like this:
{
"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't not a picture of my phone I don't have it on me right now but its very similar.
Thats why I flash Custom binary because its wipes everything and boots up. In other Guide from this forum I've reed that if you run factory reset from Custom binary FRP goes away buts probably samsung fix it in B4 bootloader.
I've don't want to go into /efs mangling because it is very dangerous I only write that I done it before and I'ts always works and If you do not need to do it don't
Now I need a way to skip "no command" screen or some twrp.img thats goes through FRP Lock to flash no-verify script or any magical way to boot up Original System.

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

Question how to downgrade sm-a12/5u from sw_rev3 to sw_rev1

i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?

tekkitheidiot said:
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
Click to expand...
Click to collapse
You can't downgrade once you've upgraded

wouldnt there be a way through twrp or brom mode?

tekkitheidiot said:
wouldnt there be a way through twrp or brom mode?
Click to expand...
Click to collapse
Nope you can try brom mode but i dont trust if works
If you buy a samsung device depending of the device (like this A12 and the MTK imei bug) is not a good idea to upgrade

tekkitheidiot said:
wouldnt there be a way through twrp or brom mode?
Click to expand...
Click to collapse
That's samsung for you, once you've upgraded Binary version there's no going back.
As for the brom mode, samsung has locked their phones out of that mode. I don't know if accessing it through access points works but you could try to see if it can help

I tryed to downgrade via TWRP flashing baseband and BL
Now my A12 is DEAD and i dont had a box to repair it (after flash i see the security error screen and flashed again the Binary 3 BL once odin tell me passed the phone doesn't booted again)
I just wanted to get the imei working because the firmware on the binary 3 (11 and 12) android system uses all my ram memory trying to get the signal working
F*** *** Samsung and mediatek next time i bought an exynos or qualcomm variant

tekkitheidiot said:
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
Click to expand...
Click to collapse
The last rom that i used on my A12 was pixel experience and worked perfectly on binary 3 android 11 based firmare (A125MUBUS3BVF1) just installed TWRP with nulled vbmeta flashed the image as system (not as super) and wiped the data (not advanced wipe) rebooted and the gsi was booted (only bugs mentionated on the thread and the touch bug)

Allehandro said:
That's samsung for you, once you've upgraded Binary version there's no going back.
As for the brom mode, samsung has locked their phones out of that mode. I don't know if accessing it through access points works but you could try to see if it can help
Click to expand...
Click to collapse
i can access brom mode if that helps

tekkitheidiot said:
i can access brom mode if that helps
Click to expand...
Click to collapse
How'd you do it?
Technically since I've always known that I can't access brom on my samsung I've never tried to understand what you can do with it.

Allehandro said:
How'd you do it?
Technically since I've always known that I can't access brom on my samsung I've never tried to understand what you can do with it.
Click to expand...
Click to collapse
i downgraded to the earliest binary 3, then used test points. worked perfectly

tekkitheidiot said:
i downgraded to the earliest binary 3, then used test points. worked perfectly
Click to expand...
Click to collapse
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover

Allehandro said:
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Click to expand...
Click to collapse
its relatively easy tbh. just be careful around the volume buttons, but everything else is okay. there arent too many cables to rip

Allehandro said:
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Click to expand...
Click to collapse
Its easy to open but be careful with the power/fingerprint sensor flex i think the testpoint is near of the charger flex in the mainboard (i see youtube tutorials to access to Brom mode and preloader)
{
"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"
}

Hello,
If you're going to be performing a downgrade, you'll have to have the SCATTAR firmware with all of the old loaded certificates and tokens. Flash is going to be performed via BROOM (fused ROM code) useing SP_FLASH_TOOL.
Regarding the IMEI issue, that I'm not able to help with. And it is pain to work with, maybe you the MODEM file could help bout dbout it. You might have to go diging through firmware sites.
Thats it.
Stay safe,
Krypton.

LAST_krypton said:
Hello,
If you're going to be performing a downgrade, you'll have to have the SCATTAR firmware with all of the old loaded certificates and tokens. Flash is going to be performed via BROOM (fused ROM code) useing SP_FLASH_TOOL.
Regarding the IMEI issue, that I'm not able to help with. And it is pain to work with, maybe you the MODEM file could help bout dbout it. You might have to go diging through firmware sites.
Thats it.
Stay safe,
Krypton.
Click to expand...
Click to collapse
where would i find this scattar firmware?

tekkitheidiot said:
where would i find this scattar firmware?
Click to expand...
Click to collapse
SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)
Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99%...
forum.xda-developers.com
Maybe this can help you only you need to download a firmware (don't try to flash a binary 2 or binary 1 firmware if you do that you phone will get a hardbrick and the sp flashtool will give the 0xC0020029 or the anti roolback error)
Pd: dont forget to change the date to 25/05/2022 to get the mtkmetatool working

MauriJ2001 said:
SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)
Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99%...
forum.xda-developers.com
Maybe this can help you only you need to download a firmware (don't try to flash a binary 2 or binary 1 firmware if you do that you phone will get a hardbrick and the sp flashtool will give the 0xC0020029 or the anti roolback error)
Pd: dont forget to change the date to 25/05/2022 to get the mtkmetatool working
Click to expand...
Click to collapse
ill look through it. thanks

tekkitheidiot said:
where would i find this scattar firmware?
Click to expand...
Click to collapse
You generate it your self

To unlock bootloader on these the easiest way is to convert it to an a125w xac by flashing the a125w bl files. Unlock bootloader with seccfg. Then flash ap, cp, and csc from a125w with odin and when it boots up it should show as a125w. Also in download mode it shows the same. My imei says unknown but i believe thats caused by unlocking bootloader so if you relock it after converting it should go back to normal. Playing with mtk modem tool to rewrite imei. Tried using xposed imei changer but didnt seem effective.