Related
So, I have contacted AT&T about my move to T-Mobile and that I needed my phone unlocked. They told me how to do it and once I received the code, I tried it with my cousins sim card (T-Mobile) and tried it twice, but it failed. The email in which I received the code stated that I only have 5 tries before it permanent locks to AT&T, so I stopped trying. I went to the T-Mobile store and tried with a sim card there, and it failed again. I now only have 1 last try, so I want to know if there is a way to unlock my phone after it has been rooted. I suspect the reason my unlock code is not working is because of my phone is rooted, and running the slimkat image.
Does anyone know what is the best way to proceed from here? I don't have the original image from my phone anymore, but I have my sister's phone and if making an image of her phone would work to restore my phone to AT&T, then I can do it. But if there is another way of doing this, please let me know. I even tried using some unlock tool app, but it failed. It actually doesn't do anything. I tried SGS Unlock Tool and CSC Select.
mji2015 said:
So, I have contacted AT&T about my move to T-Mobile and that I needed my phone unlocked. They told me how to do it and once I received the code, I tried it with my cousins sim card (T-Mobile) and tried it twice, but it failed. The email in which I received the code stated that I only have 5 tries before it permanent locks to AT&T, so I stopped trying. I went to the T-Mobile store and tried with a sim card there, and it failed again. I now only have 1 last try, so I want to know if there is a way to unlock my phone after it has been rooted. I suspect the reason my unlock code is not working is because of my phone is rooted, and running the slimkat image.
Does anyone know what is the best way to proceed from here? I don't have the original image from my phone anymore, but I have my sister's phone and if making an image of her phone would work to restore my phone to AT&T, then I can do it. But if there is another way of doing this, please let me know. I even tried using some unlock tool app, but it failed. It actually doesn't do anything. I tried SGS Unlock Tool and CSC Select.
Click to expand...
Click to collapse
I don't believe it failed do to being rooted so much as being on a custom ROM and not having the stock dialer. You will probably be best served by reverting to a Stock ROM before using your last try. BE CERTAIN you flash the ROM appropriate for your current bootloader and modem. If you fail with your last try your only recourse will be to purchase an unlock code from a third party, or so I have read (unless you are still on the 4.1.1 bootloader and modem).
The best bet is to revert to stock unrooted if possible. What is your current boot loader? This is extremely important as this will determine your options, if any, of returning to stock and methods of unlocking.
Well, I rooted my phone back when I first got it (2 years ago), so I am not sure what boot loader I have (I think I was running Jelly Bean 4.1). I know that I never updated to anything afterwards. It was not until recently that I updated to the SlimKat, rather than trying to update to an AT&T image. If I was to install one of the stock ROMs, do I need to use my computer, or can I use TWRP? Or do I need everything to be stock?
Before flashing anything, download the Samsung Phone Info app from the play store and confirm the bootloader and modem currently on your phone. Post the version here and we'll try to help you get your phone unlocked.
Root gives you access to system files and does not have an effect on entering an unlock code into a stock ROM.
I just download an app called "Phone INFO Samsung" but I don't see anything under "Firemware's CSC Code" -- totally blank. When I choose to browse firmware, it only shows me the year 1970-01-01, and CSC: ATT. The Mnufacture date: 2013-01-19
You need to look for the bootloader, not firmware.
If you have a terminal app on your phone, open the app, type su and press enter. Type getprop ro.bootloader and press enter.
okay, this is what I got:
I747UCDLK3
Thanks for helping out with this.
So, since my attempts of unlocking have been on the non-Stock ROM, does it still count towards my 5 failed attempts? Or is the phone able to keep count of the attempts, regardless of ROM? I would assume that since the correct ROM has to be installed for the unlock code to work, then shouldn't the ROM be the one keeping count of the failed attempts, too? Just wondering...
Since you are on LK3 bootloader, that means you can use the free method to unlock your phone.
You can use Odin to flash the stock ATT 4.1.1 ROM from sammobile.com: http://www.sammobile.com/firmwares/database/SGH-I747/.
Free method is here: http://forum.xda-developers.com/showthread.php?t=2529200
audit13 said:
Since you are on LK3 bootloader, that means you can use the free method to unlock your phone.
You can use Odin to flash the stock ATT 4.1.1 ROM from sammobile.com: http://www.sammobile.com/firmwares/database/SGH-I747/.
Free method is here: http://forum.xda-developers.com/showthread.php?t=2529200
Click to expand...
Click to collapse
Sorry to be such noob at this, but do I need to use (Odin via) my computer, rather than using the TWRP recovery tool already on my phone? I know I have not gone through all the research material, I just did this once and never looked back, I am still in the noob stage.
Yes, you must use desktop Odin (I recommend Odin 3.07) to flash stock 4.1.1.
If you decide to flash using Odin, uncheck everything except f.reset time before flashing. After flashing and you see the word "reset" in the status window, remove USB cable, remove battery, replace battery, boot into recovery, do a full factory reset/wipe, boot the phone, use the free method to unlock the phone, restart, and you should be permanently sim unlocked.
Okay, got it! Thanks for the responses, and I appreciate the fact that you guys did not just send me searching through the tons of threads you have compiled in the forums. I was sort of expecting to be chastised for not doing extensive research before posting. You guys have been great!
Hey guys. I'm very new and have spent the last few days researching about how the whole rooting, unlocking sim, unlocking bootloader, flashing radios and installing customer ROM's work.
From what I understand the process all start with having an unlocked bootloader so that you can install a recovery like TWRP. From there, you can flash ROM's, radios and kernels (if you want to) via zip files, from an micro sd card.
**please let me know if I understand this process correctly**
The problem is, I can't find a single place online (searched on this site and on google for over an hour straight last night) that actually tells you specifically for my model I317M with 4.1.1 (if that matters, I'm not sure) HOW to unlock the bootloader. I've seen a lot of people asking and no answers.
If someone could please tell me exactly HOW to unlock the bootloader for my phone that'd be amazing.
Is flashing the bootloader done via odin? (there is an option in odin for it) If not, how do you flash a bootloader?
Jay26Canada said:
Hey guys. I'm very new and have spent the last few days researching about how the whole rooting, unlocking sim, unlocking bootloader, flashing radios and installing customer ROM's work.
From what I understand the process all start with having an unlocked bootloader so that you can install a recovery like TWRP. From there, you can flash ROM's, radios and kernels (if you want to) via zip files, from an micro sd card.
**please let me know if I understand this process correctly**
The problem is, I can't find a single place online (searched on this site and on google for over an hour straight last night) that actually tells you specifically for my model I317M with 4.1.1 (if that matters, I'm not sure) HOW to unlock the bootloader. I've seen a lot of people asking and no answers.
If someone could please tell me exactly HOW to unlock the bootloader for my phone that'd be amazing.
Is flashing the bootloader done via odin? (there is an option in odin for it) If not, how do you flash a bootloader?
Click to expand...
Click to collapse
You are lucky to have the device you do because the bootloader isn't locked! Some carriers lock the bootloader on some devices (it varies, like note 2 on at&t is unlocked but note 4 is locked). Some manufacturers even offer instructions or tools to unlock (ie htc offers Dev tools, on Google's nexus line it's a simple adb command "fastboot oem unlock").
Now for the i317, the procedure is simple. Gain root access with cf auto root (it's a tar.md5 file you flash with Odin. As a side note: Odin is a tool you will come to love because it can fix nearly anything you break. Just load the stock firmware for your device in Odin, flash and done. From there you can reroot or remain stock). Once you have root access after flashing cf auto root, have your custom recovery tar.md5 on hand to also flash in Odin.
So Odin, cf auto root, and recovery of your choice. (To flash the phone with Odin, the phone must be in download mode: vol-, home, power. Connect to computer and load up Odin)
Once you have flashed your root files and recovery, you can then enter recovery by holding vol+, home, and power, make a backup of your current stock setup, and then flash whatever rom you like as long as it's compatible with your device.
One more piece of advice: if you want to do anything like carrier unlock the device, I would do it now while you're on 4.1.1. In kitkat 4.4.2 and above some of the built in functionality of dialer codes and such were removed by Samsung... and people looking to carrier unlock who have already updated have to go through the tedious downgrade procedure to do so. Therefore, if that is something you are planning on needing at some point (or to just up the resale value of the device a bit), go ahead and root + recovery, then carrier unlock the device using dialer codes as specified in some of these threads. Then you can flash whatever you want and nothing can undo that unlock (mine is an att i317 on tmobile, so I highly recommend carrier unlock, you never know when you might need it!) Just do it before you move from 4.1.1 if you do want to do it
Good luck
absinthesummer said:
You are lucky to have the device you do because the bootloader isn't locked! Some carriers lock the bootloader on some devices (it varies, like note 2 on at&t is unlocked but note 4 is locked). Some manufacturers even offer instructions or tools to unlock (ie htc offers Dev tools, on Google's nexus line it's a simple adb command "fastboot oem unlock").
Now for the i317, the procedure is simple. Gain root access with cf auto root (it's a tar.md5 file you flash with Odin. As a side note: Odin is a tool you will come to love because it can fix nearly anything you break. Just load the stock firmware for your device in Odin, flash and done. From there you can reroot or remain stock). Once you have root access after flashing cf auto root, have your custom recovery tar.md5 on hand to also flash in Odin.
So Odin, cf auto root, and recovery of your choice. (To flash the phone with Odin, the phone must be in download mode: vol-, home, power. Connect to computer and load up Odin)
Once you have flashed your root files and recovery, you can then enter recovery by holding vol+, home, and power, make a backup of your current stock setup, and then flash whatever rom you like as long as it's compatible with your device.
One more piece of advice: if you want to do anything like carrier unlock the device, I would do it now while you're on 4.1.1. In kitkat 4.4.2 and above some of the built in functionality of dialer codes and such were removed by Samsung... and people looking to carrier unlock who have already updated have to go through the tedious downgrade procedure to do so. Therefore, if that is something you are planning on needing at some point (or to just up the resale value of the device a bit), go ahead and root + recovery, then carrier unlock the device using dialer codes as specified in some of these threads. Then you can flash whatever you want and nothing can undo that unlock (mine is an att i317 on tmobile, so I highly recommend carrier unlock, you never know when you might need it!) Just do it before you move from 4.1.1 if you do want to do it
Good luck
Click to expand...
Click to collapse
Wow! Thanks a lot for that detailed reply. I wasn't expecting that
I managed to get a recovery installed and working. I've tried two ROMs today and that was neat. ( I put them on the external sd card and flashed the .zip from recovery ). Now my main problem is, finding a ROM that actually works decently (any suggestions would be nice) and unlocking the sim.
Now, I was on 4.1.1. and when I was there, I followed these steps http://forum.xda-developers.com/showthread.php?t=2014982 and it seemed to have worked. It went just like the steps said it would.
Then, I actually went to a WIND mobile store today and asked if I could use a SIM to see if it would work with their network. It didn't (their network didn't show up on my phone )
I've since then tried that old method again but I am getting this error "connection problem or invalid mmi code" So I couldn't try doing that again.
Now I'm kinda stuck. I have been trying to find out if I can flash the radio with some firmware to fix it but I've had no luck finding anything.
I know this is a newish problem, but if you can guide me in the right direction or help me out I'd appreciate it. Otherwise, I might just have to buy a new phone.
Jay26Canada said:
Wow! Thanks a lot for that detailed reply. I wasn't expecting that
I managed to get a recovery installed and working. I've tried two ROMs today and that was neat. ( I put them on the external sd card and flashed the .zip from recovery ). Now my main problem is, finding a ROM that actually works decently (any suggestions would be nice) and unlocking the sim.
Now, I was on 4.1.1. and when I was there, I followed these steps http://forum.xda-developers.com/showthread.php?t=2014982 and it seemed to have worked. It went just like the steps said it would.
Then, I actually went to a WIND mobile store today and asked if I could use a SIM to see if it would work with their network. It didn't (their network didn't show up on my phone )
I've since then tried that old method again but I am getting this error "connection problem or invalid mmi code" So I couldn't try doing that again.
Now I'm kinda stuck. I have been trying to find out if I can flash the radio with some firmware to fix it but I've had no luck finding anything.
I know this is a newish problem, but if you can guide me in the right direction or help me out I'd appreciate it. Otherwise, I might just have to buy a new phone.
Click to expand...
Click to collapse
Im at work so I don't have a lot of time to explain, but the unlock probably worked fine. However, when you add a new Sim, you also have to program the access point name (or more commonly, APN). If you don't set the apn, the phone won't know which network to connect to. You may use a wind sim but if you still have the apn set for tmobile, it's gonna look for tmobile's network.
Apns can be configured under settings > more networks > mobile networks > access point names. You can have multiple apns programmed and switch between them as often as you switch sim cards. Search for wind apn and you'll figure it out (I keep a text file with lists of tmobile and at&t apns just in case.
Also you probably flashed a newer rom where Samsung/Google have removed the built in dialer codes, so you won't be able to use them anymore, but you can launch the codes you need using shortcut master (an app) where you can find the code you need and launch it fine with root permissions.
The problem was resolved after flashing stock, reunlock, then restore. I will report if problems comeback.
Hello,
My phone was unlocked (not sure how, bought it second hand years ago) and used it fine on 4.4 custom rom. Ive updated it onthursday to the revolution 6.0.1 (with 3.0.2 twrp, nano open gappsa) and used it fine without problems on thursday.
However, yesterday, it lost cell signal and would not reconnect. So i rebooted the phone and now it is asking me to put sim unlock pin. What is the best course of action to get unlocked 6.0.1? I couldn't find an unlock method for 6.0.1. Should i backup rom, go back to 4.4, unlock, then restore?
Thank you.
It's asking for the sim pin or network unlock pin?
audit13 said:
It's asking for the sim pin or network unlock pin?
Click to expand...
Click to collapse
SIM Network unlock pin. My modem/bootloader is I317MVLBMA3. Do you think i can safely load a 4.1.1 rom and unlock again?
If i install phone info+ and look under secret codes, it does list the code for unlocking, but if i click on it, it gives me a blank page titled "service mode" but doesn't do anything (none of the three methods of entering work under the app). Probably because it is not stock ROM?
I tried searching for stock I317MVLALJ2 ROM to downgrade easily, but it seems like the link is down. I guess ill have to use ODIN.
EDIT:
Can I use TWRP to flash http://stockroms.net/file/GalaxyNote2/SGH-I317M/I317MVLALJ2_I317MOYAALJ2_RWC.zip stock ROM? Or do I have to use ODIN? I am assuming I can as it is a zip rather than img, and as long as I flash recovery right after flashing rom, I shouldn't lose recovery either?
Thank you.
The easiest way would be to flash a stock 4.1.1 rom in Odin. I am fairly certain you can downgrade as I think I downgraded from 4.3 or 4.4.2 on a Koodo note 2 so I could use it on Rogers. If it's not possible to downgrade, Odin will stop.
audit13 said:
The easiest way would be to flash a stock 4.1.1 rom in Odin. I am fairly certain you can downgrade as I think I downgraded from 4.3 or 4.4.2 on a Koodo note 2 so I could use it on Rogers. If it's not possible to downgrade, Odin will stop.
Click to expand...
Click to collapse
Thank you for the reply. I am currently on 6.0.1, but since modem is 4.4.2 ish, i hope that's okay. I will try ODIN. The zip i mentioned above is not a TWRP flashable zip, so I guess I have to use ODIN. The thing that worries me, though, is the fact that I cannot get to the recovery mode from off. I press and hold the volume up-power- home combo, but it keeps on resetting without entering TWRP. The only way for me to enter recovery right now is using a custom rom restart menu. If I go to stock ROM, I won't be able to access the recovery .
EDIT: If I let go of the power button at a certain time while booting, it seems to go into recovery just fine.. The problem is, that timing is tricky.
For flashing a stock rom, you need download mode so don't worry about getting into recovery.
To enter stock recovery, power off and try holding power, volume up, and home. Once the phone boots, let go of power but keep holding home and volume up until you see the dead android, then let go of all buttons.
audit13 said:
For flashing a stock rom, you need download mode so don't worry about getting into recovery.
To enter stock recovery, power off and try holding power, volume up, and home. Once the phone boots, let go of power but keep holding home and volume up until you see the dead android, then let go of all buttons.
Click to expand...
Click to collapse
Thank you. Flashed stock using ODIN, rebooted, showed samsung logo with music (stock boot animation), then the phone is stuck on SAMSUNG logo changing colors. Stuck there for the last 10 minutes... Not sure where to go from here ..
Boot into recovery and do a factory wipe.
audit13 said:
Boot into recovery and do a factory wipe.
Click to expand...
Click to collapse
Success. Thank you very much. So I've done the factory reset and successfully rebooted the phone. Then applied the unlock method, which seemed to have worked. Does not ask for SIM unlock pin. However, it does not seem to actually lock cellular signal. It still says 'Emergency Calls Only'. I am on Mobilicity, which used to be AWS, but now I believe is under Rogers. I know mobilicity used to take a while to connect, but I doubt that is the same now. This may be due to the old modem, so I will try updating the modem back to the 4.4 one... wish me luck
EDIT:
Without the modem update, it just connected to mobilicity !
Now the issue is, whether this phone will re-lock again once I flash 6.0.1...
Thank you very much audit13 for your live help!!
I will post back in a week or so (hopefully I remember...) whether this unlock sticks.
The 317m does not natively support was frequencies. You'll have to software enable was support.
You mean it doesn't ask for network unlock pin?
audit13 said:
The 317m does not natively support was frequencies. You'll have to software enable was support.
You mean it doesn't ask for network unlock pin?
Click to expand...
Click to collapse
Yup. It unlocked for sure. But that is no different than what I had before updating to 6.0.1. I've used the phone without problems on Mobilicity for 2-3 years.
Mobilicity is no longer AWS, so it has no problems connecting to the network. It just takes a while, especially with the 4.1.1 modem...
Now I'm just restoring the TWRP backup that I have made on 6.0.1 to see if the unlock sticks.
The unlock stayed for my phone when I installed a custom rom.
audit13 said:
The unlock stayed for my phone when I installed a custom rom.
Click to expand...
Click to collapse
Yes, that was the case yesterday as well. It stuck for a day, but after the cell lost the signal once (zero bars, emergency calls only), the phone got re-locked.
Now that I have restored the 6.0.1 backup, the phone is back up and running with it unlocked. Now ill will see how long this lasts.
Thank you very much for your continued support
I am having this issue now.. but the strange thing is that I've flashed to the Resurrection 6.0 rom a while back and it was working fine. Until a while ago I was pokemon hunting and all of a sudden my network died and its been asking me for a sim network pin... I was getting the intermittent network disconnect when I was on the Pokemon go app too long but it would reconnect back to the network after a short time.. not sure if it has something to do with the game app. Well, now I've downloaded the latest Resurrection rom and flashed it again doing a factory wipe but still nothing. I'm going to try and flash the modem and see if that helps.
EDIT: forgot to mention I'm on Koodo network which is also Telus, I believe. But now it wants to automatically connect to the rogers network hence I'm assuming its asking for the PIN.
(edited for grammar)
This is really strange that this happens. I've unlocked a few note 2 phones and none of them have relocked.
Did you change the csc in the phone settings to Koodo?
audit13 said:
This is really strange that this happens. I've unlocked a few note 2 phones and none of them have relocked.
Did you change the csc in the phone settings to Koodo?
Click to expand...
Click to collapse
do you know why I cannot do the universal unlock method by entering the *#197328640# method? when I enter those digits nothing happens..
EDIT: Forgot to mention that the newest Resurrection rom did not work so I tried DNA 4.4 rom and still asking for unlock pin.. damn. need a new phone it seems..
I believe you need to be running a particular version of the stock Samsung dialler.
audit13 said:
I believe you need to be running a particular version of the stock Samsung dialler.
Click to expand...
Click to collapse
What's the csc you mentioned?
Csc is a carrier customization file. If you change the csc, which can be done using a stock rom, you can choose the carrier for whom the rom phone was intended. I choose Telus as a carrier because they have very little bloatware.
audit13 said:
Csc is a carrier customization file. If you change the csc, which can be done using a stock rom, you can choose the carrier for whom the rom phone was intended. I choose Telus as a carrier because they have very little bloatware.
Click to expand...
Click to collapse
I'm using this rom
http://forum.xda-developers.com/showthread.php?t=2541860
which is a modded stock rom I believe but I don't know how to edit the csc file.
I had bought a GS3 a few years back but never used it. Had some carrier issues as all the SIMs here in India were not supported. Ever since I bricked my Moto E, I decided to start using it again.
I realised that the sticker on the rear of my phone says it's I9300 (International Version) of the S3 but the firmware and bootloader in downloader mode shows it as SGH-747 which I believe is the d2att device. I decided to try and flash the I9300 bootloader and flash the I9300 firmware using Odin to sort my carrier network issues (modem difference issues maybe). Ended up causing a hard brick on my phone didn't turn on properly.
I used the bootloader debrick image from: https://androidfilehost.com/?fid=23501681358549813 and was able to boot my phone into download mode. I assume it's the I747 image which helped me turned on my phone although the battery and rear panel says it's I9300. Nevertheless, I downloaded the 4.0.4 firmware from AndroidMTK.com to flash on my bootloader to completely debrick the device. Downloaded the I747 as the debrick I downloaded earlier bootloader is I747 one.
I tried flashing the firmware and get the below error:
Code:
WARRANTY BIT: 1
BOOTLOADER AP SWREV: 3
SW REV CHECK FAIL: Fused 3 > Binary 0
Is my bootloader a Kitkat Bootloader? Am I flashing the wrong firmware? Should I flash the 4.4.2 firmware and see if it works? Would really appreciate if anyone could guide me here. I really want to unbrick my phone.
I can access my TWRP by using the debrick image from a SD Card. I tried booting into TWRP and Flashing CM 12.1, Lineage 14.1 and Slim 6. I have previously used these three roms on the device. Now, they won't boot after getting installed. I'm stuck at bootlogo when rebooting. Would appreciate any help.
Can anyone help out with this?
Are you able to determine the model # with the phone in download mode?
Since there is mention of "warranty bit", the phone must be running a 4.3 or newer bootloader which cannot be downgraded.
AT&T never released a full Odin-flashable firmware after 4.1.1.
audit13 said:
Are you able to determine the model # with the phone in download mode?
Since there is mention of "warranty bit", the phone must be running a 4.3 or newer bootloader which cannot be downgraded.
AT&T never released a full Odin-flashable firmware after 4.1.1.
Click to expand...
Click to collapse
The phone model is the SGH-747. It's the AT&T variant. Which firmware should I flash then?
Flash this: https://forum.xda-developers.com/ga...ile-sgh-i747ucufne4v4-4-2attall-odin-t3305899
I feel like I've done a big door.
I work in a cell repair shop and we had an ATT unlocked S20 FE that came in and I liked it so I bought it.
Long story short. I did some reading that you can install the XAA software using patched Odin. This was essential because I'm on Tmobile and didnt get 5G on the ATT firmware.
Easy enough. The device now has 5G access on Tmobile, and identifies itself as SM-G781U1/DS in settings.
The issue I'm facing is now unlocking the bootloader. The XAA firmware doesn't have the option and I'm unable to flash back to ATT firmware without (auth) fail errors in Odin and 'Secure boot check fail: PIT' on download mode.
Here's what I've tried that's failed so far:
- show option using time/date change
- software updating (I do receive OTA)
- flashing stock ATT firmware
- flashing stock TMB firmware
- Fastboot oem unlock (command not found)
- fastboot getvar unlocked (unlocked: no)
I'm about out of ideas, could use some guidance on where to begin looking next, I really like the power of this phone and wanna see what custom roms bring.
Device stats:
Galaxy S20FE SM-G781U (with U1 XAA flash)
CSC: ATT
Build: G781U1UESAGWC7
Service provider info:
G781U1_OYM_TMB_13_0011
TMB/TMB/ATT
Android 13, One UI 5.1
To be honest the custom rom screne for this phone is not so great yet. I imagine once the official support ends we will be getting some well developed custom roms.
As for the bootloader unlock issue, try using smartswitch to restore stock firmware, or try changing only the CSC if the firmware is multi-csc, the oem unlock option might reapper.
What kind of patched odin did you use to flash the XAA firmware? stock odin should be able to flash it too. As far as i am aware north american samsung phones do not offer oem unlock. The option probably dissapeared for good. There was etoken but since you are on android 13 i imagine the exploits have been already patched. You're basically stuck on XAA now. You can try using samkey to change the csc but i doubt that even that can help you oem unlock it.
hoptockets said:
I feel like I've done a big door.
I work in a cell repair shop and we had an ATT unlocked S20 FE that came in and I liked it so I bought it.
Long story short. I did some reading that you can install the XAA software using patched Odin. This was essential because I'm on Tmobile and didnt get 5G on the ATT firmware.
Easy enough. The device now has 5G access on Tmobile, and identifies itself as SM-G781U1/DS in settings.
The issue I'm facing is now unlocking the bootloader. The XAA firmware doesn't have the option and I'm unable to flash back to ATT firmware without (auth) fail errors in Odin and 'Secure boot check fail: PIT' on download mode.
Here's what I've tried that's failed so far:
- show option using time/date change
- software updating (I do receive OTA)
- flashing stock ATT firmware
- flashing stock TMB firmware
- Fastboot oem unlock (command not found)
- fastboot getvar unlocked (unlocked: no)
I'm about out of ideas, could use some guidance on where to begin looking next, I really like the power of this phone and wanna see what custom roms bring.
Device stats:
Galaxy S20FE SM-G781U (with U1 XAA flash)
CSC: ATT
Build: G781U1UESAGWC7
Service provider info:
G781U1_OYM_TMB_13_0011
TMB/TMB/ATT
Android 13, One UI 5.1
Click to expand...
Click to collapse
for some reason Samsung doesn't allow bootloader unlocks in the US anymore. if as a phone repair guy you have the means force older firmware onto the device then you could pay someone to get an unlock token on the DL from a contact of theirs.
downgrading isn't something we can do at all hence me mentioning you maybe having access to resources others don't.
if you could get it onto the very first firmware you'd have a chance, if you can't there's no chance.