Develop Bugs

[Q] Why does my Galaxy S3 fail when I try to install a rogers Stock ROM on it?

Here's the error I get:
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks guys!
The phone is an I747 from AT&T.
I'm trying to flash the Rogers ROM on it because I am on a Rogers plan and the AT&T version is full of bloatware.

bump

Try downloading the file again. I would also try another usb slot or even pc
Sent from my SAMSUNG-SGH-I747M

mymusicathome said:
Try downloading the file again. I would also try another usb slot or even pc
Sent from my SAMSUNG-SGH-I747M
Click to expand...
Click to collapse
Just tried it again. It keeps failing at sbl2.mbn it seems.
If it means anything, I just noticed in download mode it says
Code:
SECURE CHECK FAIL : sbl2

SevKempf said:
Here's the error I get:
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks guys!
The phone is an I747 from AT&T.
I'm trying to flash the Rogers ROM on it because I am on a Rogers plan and the AT&T version is full of bloatware.
Click to expand...
Click to collapse
I may be wrong but I don't think you can flash the stock ATT ROM on a Rogers device and vice versa. Also, the ATT ROM contains a different modem that may not work well for us on Rogers. Your best bet is to keep the ATT ROM and freeze/delete the bloatware using Titanium Backup Pro and flash the Rogers modem.
Or run a custom ROM.

Tony_YYZ said:
I may be wrong but I don't think you can flash the stock ATT ROM on a Rogers device and vice versa. Also, the ATT ROM contains a different modem that may not work well for us on Rogers. Your best bet is to keep the ATT ROM and freeze/delete the bloatware using Titanium Backup Pro and flash the Rogers modem.
Or run a custom ROM.
Click to expand...
Click to collapse
Yeah, I'm currently running CM10 but I find it has WAY too many bugs for me to use it, things constantly crashing, graphical glitches. The LED doesn't light up for anything except charging.
I originally did use TiBa to delete the bloat, no problem. Except AT&T replaces the Address Book with their own version the "AT&T Address Book" which syncs with some AT&T server every time I open it, super annoying.

Then why not try using one of the custom ICS/JB stock-based ROMs? As he said, i'm pretty sure it's impossible to flash a Rogers ROM on an AT&T device.
And.... which build of CM10 are you using? You could always try Task & Ktoonsez CM10-based ROM. Never experience a graphical glitch (though, i never did even on older CM10 builds, either), hardly ever have anything crash..... and as far as i'm aware, even in stock CM10, you actually have to go into the settings or find an app and manually set up the notification LED colors and what they blink for.

elementaldragon said:
Then why not try using one of the custom ICS/JB stock-based ROMs? As he said, i'm pretty sure it's impossible to flash a Rogers ROM on an AT&T device.
Click to expand...
Click to collapse
Where can I find one of these ROMs? I've searched for them but I haven't found anything. I asked someone and they suggested an AOSP, but I wasn't able to find any, so I used a AOKP ROM and when I booted the phone all that displayed was some 8bit looking gradient from Yellow to Purple, got worried and rebooted my phone and reinstalled Cyanogenmod.
elementaldragon said:
And.... which build of CM10 are you using? You could always try Task & Ktoonsez CM10-based ROM. Never experience a graphical glitch (though, i never did even on older CM10 builds, either), hardly ever have anything crash..... and as far as i'm aware, even in stock CM10, you actually have to go into the settings or find an app and manually set up the notification LED colors and what they blink for.
Click to expand...
Click to collapse
I installed Cyanogenmod from the ROM Manager app. This ROM, specifically.
Also, when I install a ROM, can I do it from CWM? Or do I need to install using Odin?

SevKempf said:
Where can I find one of these ROMs? I've searched for them but I haven't found anything. I asked someone and they suggested an AOSP, but I wasn't able to find any, so I used a AOKP ROM and when I booted the phone all that displayed was some 8bit looking gradient from Yellow to Purple, got worried and rebooted my phone and reinstalled Cyanogenmod.
I installed Cyanogenmod from the ROM Manager app. This ROM, specifically.
Also, when I install a ROM, can I do it from CWM? Or do I need to install using Odin?
Click to expand...
Click to collapse
That link you provided shows that it points to a Galaxy S2 ROM in the url. The link itself didn't work though when i clicked on it.
Try this ROM: http://forum.xda-developers.com/showthread.php?t=1766684

I wonder if the problem you're having is related to the build.prop
ATT have a device model name d2att while the Canadian variants have device model name d2can.
Search the forums add I think I've read something about that.
Also, even though you want to flash a Rogers Rom, make sure you use an ATT modem.
Sent from my SGH-I747M using xda premium

what can be error sbl2.mbn than use Odin ?
i try use other usb port in notebook, any versions Odin (v. 1.85; 3.4; 3.7), reinstalling the USB drivers and use stock SGS3 USB but problem steel be
Thanks

Definitely try out Task650's AOKP rom, Its very stable and has very few (if any) bugs.

nate_benji said:
Definitely try out Task650's AOKP rom, Its very stable and has very few (if any) bugs.
Click to expand...
Click to collapse
i'm use Task650's AOKP rom at that moment, but they are not support extSdCard 64Gb and then i'm try upload stok JB 4.1.1. from Odin i recive a fail massage i think truble in sbl2.mbn
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I747MVLDLK4_I747MOYCDLK4_538866_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sbl2.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Tybalt said:
Also, even though you want to flash a Rogers Rom, make sure you use an ATT modem.
Click to expand...
Click to collapse
Are you suggesting that I download both stock ROMs, extract them, then do a simultaneous mix and match of the parts in ODIN?
I have the AT&T i747 but want to have the reduced Rogers bloatware.

Anonymously_Unknown said:
Are you suggesting that I download both stock ROMs, extract them, then do a simultaneous mix and match of the parts in ODIN?
I have the AT&T i747 but want to have the reduced Rogers bloatware.
Click to expand...
Click to collapse
No, just get a cwm recovery and flash a AT&T modem.
Also, there's a unbloated AT&T stock ROM, why go for Rogers?

Go to twrp or cwm website and get the recovery for d2can instead of d2att. I'm not sure but it could be the source of your issue.
Sent from my SGH-I747 using xda app-developers app

Im having similar problem and need help too
I also have this secure check fail:sbl2 problem, but what I did was diffident. installed ParanoidKangDroid custom rom and then i realized that i use allshare play from stock rom pretty much so i decided to put back to stock my GS3. I used odin 3.0.7 to do that. I download the original stock rom from sammobile exactly the puerto rico version (were i live), but as i said it gives me the sbl2 fail problem.
---------- Post added at 05:19 AM ---------- Previous post was at 05:07 AM ----------
As you see Im a noobie here and I have another question. I like ParanoidKangDroid in my device but cant install allshare play so th question is: If i flash the [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][4/6/2013] KT747 - LJ7 - KTweaker, Can I install allshare play then? if yes what do i need to install it. Is there any other 4.2.2 rom that i can use the kernel mentioned above? or is there any rom which has touchwiz integrated?

sycol65 said:
but as i said it gives me the sbl2 fail problem.
Click to expand...
Click to collapse
I had downloaded the one from the stock firmware page and flashed it with the custom recovery to eliminate that issue. What you are experiencing is a bootloader mismatch.

Can you explain me the correct entire process to do that?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

slb2.mbn error, fail
SevKempf said:
Here's the error I get:
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks guys!
The phone is an I747 from AT&T.
I'm trying to flash the Rogers ROM on it because I am on a Rogers plan and the AT&T version is full of bloatware.
Click to expand...
Click to collapse
This error is caused because a BAD USB CABLE. Please, use an original Samsung GGalaxy Cable. I had that problem with my GT-I9195. Fortunatelly it's working again.
The symptom was that i couldn't copy files from my computer to my smartphone.

Tried to Unroot now bricked

I had Cynagenmod 4.4.4 on my S4. I wanted to unroot it as the release is buggy. So I went to a link on how to unroot at S4 phones and followed the steps and now I cant get it to unroot and its now stuck in a boot loop. I have tried ODIN multiple times and this is what I get.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Removed!!
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help. My phone is a paperweight right now.

Its also giving me a check fail on the phone itself.
Start [224,1140]
SW Rev. Check Fail: 4, Binary : 1

Snakedoktor said:
Its also giving me a check fail on the phone itself.
Start [224,1140]
SW Rev. Check Fail: 4, Binary : 1
Click to expand...
Click to collapse
Your trying to flash the wrong firmware? What was your phone BEFORE you rooted? 4.2.2? 4.3?

The Sickness said:
Your trying to flash the wrong firmware? What was your phone BEFORE you rooted? 4.2.2? 4.3?
Click to expand...
Click to collapse
It was December of last year. I dont honestly remember. I know I was at 4.4.4 when it was rooted. Just looked it up November of last year was 4.3

Snakedoktor said:
It was December of last year. I dont honestly remember. I know I ad 4.4.4 when it was rooted.
Click to expand...
Click to collapse
If you got it in Dec then it was 4.3. If it was 4.4.4 when you rooted meant you took a OTA?

The Sickness said:
If you got it in Dec then it was 4.3. If it was 4.4.4 when you rooted meant you took a OTA?
Click to expand...
Click to collapse
It was an update via cynogen mod that updated it to 4.4.4. It does look like it had 4.3 like you said. Did I download the wrong file?

Snakedoktor said:
It was an update via cynogen mod that updated it to 4.4.4. It does look like it had 4.3 like you said. Did I download the wrong file?
Click to expand...
Click to collapse
Yes you DL the wrong file. Im not too familar with Cynogen. So if it did update you to 4.4.4, you need to Odin the Official 4.4.4 Firmware

Cyanogen 4.4.4 won't require you to flash stock 4.4.4 because it does not update firmware If you had official 4.3 firmware when you flashed cm then you need to flash at least 4.3 firmware. That's why you are getting the error, you were trying to flash 4.2.2. You have the option of flashing 4.3 MK2, 4.4.2 NB4, or 4.4.4 NH7. You might as well flash NH7

One other thought: Just because the CM you are running has some bugs, perhaps another ROM would be a better experience than the bloated Samsung stock.
I'm very happy on Dirty Unicorns, but I've been thinking to try a very basic Slimkat or something like that, then theme it with Themer, and add any apps/functions needed.
Maybe something like that would work for you?
Marc

Unable to Odin stock OB7 or stock NK2.

I don't seem to be able to Odin stock OB7 or stock NK2. When I attempt to Odin either I get this on Odin:
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and get this on the download screen:
UDC START
SW REV CHECK FAIL : [tz]Fused 3>Binary 1
[4]eMMC write fail: TZ
Right now I'm running HYBRID_OB7sbl_SPT_N910PVPU4COG5 unrooted. Any potential help with what I've done would be great. Thanks guys.

Cant go back. Period.
Sent from my SM-N910P using Tapatalk

I have the same problem. Updated the phone with the latest from Sprint / Samsung, then tried to root and got into a boot loop. I can get into download mode and recovery. Trying to flash a ROM with CWM recovery fails too.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Read frezzas stockish thread.
Sent from my SM-N910P using Tapatalk

It's failing because the bootloader is not authenticating. Since you flashed my custom rom odin package I'm surprised it's not letting you flash the official OB7 rom tar. Apparently there's more to this equation than just the bootloader or else you tried or successfully flashed the pre-rooted kernel before you tried to odin the OB7 rom tar. Try flashing my custom OB7/OG5 rom tar again THEN flash the official OB7 rom tar. You need to be bone stock before attempting the odin of OB7. If it still fails then give up because you can't win this battle. Just update to OG5 and don't worry about it.
I'll be honest, there's really no reason why you shouldn't just go ahead and wipe everything clean and flash my custom OB7/OG5 rom tar again or the official OG5 rom tar and let your bootloader update to OG5. I think 5.1.1 is by far the best version of Android to date. I see absolutely no reason to flash older software versions because 5.1.1 is much more responsive in every way and battery life is improved as well. Don't sweat this. If I had any trouble with my OB7 bootloader I'd update mine to OG5 in a second.

After blowing nearly an entire day....
To start off my phone was stock / rooted, I then installed the latest update via Kies (OE1, wanted the Stagefreight patch) and attempted to re-root my phone which I then found was stuck in a boot loop. I got lazy, updates had been going well on the Note 4 and I failed to come to XDA to see if there were any problems rooting it, turns out there is :crying: and I couldn't get Kies to recover it, and factory reset didn't work either. To recover I tried to use ODIN to flash OB7 and received the above results, I tried a few other stock ROMs and got the same problem.
At this point I was about ready to chuck my phone out the door until I noticed a comment saying that once you flash OE1 you can't go back and the only option is to flash an AOSP ROM such as Notirized. I downloaded Notorized, following the OP directions step by step and I now have my phone back! So far I like this ROM, so maybe this was fate
http://forum.xda-developers.com/not...-noterized-rom-super-speedy-reliable-t3099382
Thanks XDA! Now if I only had come here first and saved myself an entire day of grief! (Took away from my time playing Elite Dangerous! lol).

Thanks man. I appreciate the response and the explanation. I thought it was an issue with the bootloader, but I was confused about what I had done. I did wind up wiping everything clean and flashing your custom OB7/OG5 rom tar. Thanks for putting that together. I definitely should have updated everything sooner. I appreciate the advice on the OG5 bootloader as well. Have a great weekend.
tx_dbs_tx said:
It's failing because the bootloader is not authenticating. Since you flashed my custom rom odin package I'm surprised it's not letting you flash the official OB7 rom tar. Apparently there's more to this equation than just the bootloader or else you tried or successfully flashed the pre-rooted kernel before you tried to odin the OB7 rom tar. Try flashing my custom OB7/OG5 rom tar again THEN flash the official OB7 rom tar. You need to be bone stock before attempting the odin of OB7. If it still fails then give up because you can't win this battle. Just update to OG5 and don't worry about it.
I'll be honest, there's really no reason why you shouldn't just go ahead and wipe everything clean and flash my custom OB7/OG5 rom tar again or the official OG5 rom tar and let your bootloader update to OG5. I think 5.1.1 is by far the best version of Android to date. I see absolutely no reason to flash older software versions because 5.1.1 is much more responsive in every way and battery life is improved as well. Don't sweat this. If I had any trouble with my OB7 bootloader I'd update mine to OG5 in a second.
Click to expand...
Click to collapse

ODIN can't flash anything

Hello !
I recently buy an A5 2017 (A520F) and i wanted to try some others ROM. So i Flash TWRP, i rooted my phone but when i want to flash a stock ROM with odin, I have an error message ( i tried with 2 different version of odin and two different firmwares... )
Here is my code , do you ever saw that ?
<ID:0/009> Odin engine v(ID:3.1301)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 5 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> param.bin
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
thanks for all

usb debugging? oem unlock?
put the right file in the right section?

leo31 said:
usb debugging? oem unlock?
put the right file in the right section?
Click to expand...
Click to collapse
^ this

Yes everything is ok ... It's bot my first Samsung phone si i Know ODIN ... It's the first time that i've something like that ?

which version of odin u used? v12?

leo31 said:
which version of odin u used? v12?
Click to expand...
Click to collapse
10.7 and 13.1 .. I just think about that, isn't it because Samsung block the downgrade ? Yesterday I tried to flash an Oreo Modem and it works ! So I think that Samsung blocked the phone to stay in the same firmware ...

matt290514 said:
10.7 and 13.1 .. I just think about that, isn't it because Samsung block the downgrade ? Yesterday I tried to flash an Oreo Modem and it works ! So I think that Samsung blocked the phone to stay in the same firmware ...
Click to expand...
Click to collapse
Oreo July update has locked your phone to Oreo

Yes... And i think that there is no solution for this ...:crying:

matt290514 said:
10.7 and 13.1 .. I just think about that, isn't it because Samsung block the downgrade ? Yesterday I tried to flash an Oreo Modem and it works ! So I think that Samsung blocked the phone to stay in the same firmware ...
Click to expand...
Click to collapse
moozer said:
Oreo July update has locked your phone to Oreo
Click to expand...
Click to collapse
i never know about it. but as long as i own samsung phone, i only lost my imei once, and i fixed it by myself. i revert back to nougatt, and back again to oreo without any issue .

Question I think i bricked my SM-A725F/DS

Does anybody have the stock rom that i could reflash through odin? When i tried flashing the regular a725f stock rom it would give me an error and i accidentally locked the bootloader as well. I dont mean to be a pain.

You can download the latest firmware for your region with tools like for example Frija or Samloader or from websites like samfw.com.

I dont know the region but i did buy it in the usa though i tried reflashing the stock rom and i got an error
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1401)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 8518 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> boot.img
<ID:0/010> recovery.img
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
File name AP_A725FXXU1AUC4_CL20962855_QB38693720_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar
IM not sure if this is the correct rom but it is a rom for the SM-A725F/DS

louie123456789 said:
File name AP_A725FXXU1AUC4_CL20962855_QB38693720_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar
IM not sure if this is the correct rom but it is a rom for the SM-A725F/DS
Click to expand...
Click to collapse
Which version of stock ROM were you using before? Android 13 / OneUI 5 or something older?
Because you're trying to flash ancient Android 11 here, and downgrading to older Android versions is not possible on Samsung phones.

Simon1511 said:
Which version of stock ROM were you using before? Android 13 / OneUI 5 or something older?
Because you're trying to flash ancient Android 11 here, and downgrading to older Android versions is not possible on Samsung phones.
Click to expand...
Click to collapse
I had android 13 with the oneui5.1 or oneui5.0 . Thanks for going out of your way to help me though i appreciate it.I didnt know that rom i was trying to flash was android 11 i thought that was the latest rom. Since i live in the us i wanna make sure to flash the right rom and not the wrong one.

louie123456789 said:
I had android 13 with the oneui5.1 or oneui5.0 . Thanks for going out of your way to help me though i appreciate it.I didnt know that rom i was trying to flash was android 11 i thought that was the latest rom. Since i live in the us i wanna make sure to flash the right rom and not the wrong one.
Click to expand...
Click to collapse
As far as I know the A72 was never "really" sold in the US (at least there is no dedicated firmware for US versions; I might be wrong).
However, in the end even the European or Asian firmwares will work just fine on your phone. It's still the same phone, just different carrier/region-specific apps and features.
I would suggest you flash the latest firmware for a region you choose (anything european should be absolutely fine). I usually download the firmware from samfw.com, they let you directly select between the different regions' firmwares and all.
Feel free to ask if you need any more help.

Simon1511 said:
As far as I know the A72 was never "really" sold in the US (at least there is no dedicated firmware for US versions; I might be wrong).
However, in the end even the European or Asian firmwares will work just fine on your phone. It's still the same phone, just different carrier/region-specific apps and features.
I would suggest you flash the latest firmware for a region you choose (anything european should be absolutely fine). I usually download the firmware from samfw.com, they let you directly select between the different regions' firmwares and all.
Feel free to ask if you need any more help.
Click to expand...
Click to collapse
Thank you so much this will save my device very much but i can use it with US networks right?