Related
My carrier (C Spire) has found a problem with the device on their network that makes the device lose it's signal all the time. They claim it is a device problem anyway. I have unlocked the bootloader on the phone, but have not flashed any roms or made any other changes to the phone. Just the unlocked bootloader. They have said that since they know it is a problem with the device, they will let owners come in and exchange the phone for a Galaxy SIII free and clear. The only stipulation is it has to be in like new condition. My phone is perfect except for the unlocked bootloader. They'd probably never notice if it wasn't for that notification screen when the phone reboots that would tell them. I need to relock the bootloader to make that screen go away.
So, my question is, how do I do that? I've tried doing 'fastboot oem lock' but that doesn't work.
This is what I get when I try:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.014s]
finished. total time: 0.016s
If I run the command as it suggests I get:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.246s]
finished. total time: 0.248s
I'm not sure what to do to get it to lock again.
Can anyone please help?
The problem is, you've unlocked it 'officially' from Moto... so it's registered in the database as unlocked.
You can try to change the boot logo, I haven't tried yet... Supposedly you can to get rid of that annoying screen.
Maybe you will just have to take it in and hope they don't reboot it. Kinda sucks that we have official unlocks now, because they can now easily track who has unlocked their phones and who hasn't :/
According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.
adear11 said:
According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.
Click to expand...
Click to collapse
Did you try using the same key to unlock to relock?
I've never bothered relocking...
arrrghhh said:
Did you try using the same key to unlock to relock?
I've never bothered relocking...
Click to expand...
Click to collapse
Is the key required to relock? I had not tried using it.
adear11 said:
Is the key required to relock? I had not tried using it.
Click to expand...
Click to collapse
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.
arrrghhh said:
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.
Click to expand...
Click to collapse
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"
adear11 said:
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"
Click to expand...
Click to collapse
You entered fastboot oem lock begin <key>?
arrrghhh said:
You entered fastboot oem lock begin <key>?
Click to expand...
Click to collapse
When I do 'fastboot oem lock begin [key]' I get "(bootloader) Ready to flash signed images".
From here, if I do 'fastboot oem lock' again, I get "Re-Lock Failure. See display." On the phone's display, I get:
Code:
No valid PIV block in SP for system
piv validation failed (system)
Re-lock failure
Hrm. I was poking around Moto's FAQ's and community site, and they talk about relocking - but not in detail unfortunately. They cryptically state that they will not release any stock recoveries at this time - so perhaps if you don't have the stock recovery, you can't relock...?
I would post up on Moto's forums or call their support... Not sure how much help they will be, but their website leaves much to be desired about the relocking process...
oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.
shabbypenguin said:
oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.
Click to expand...
Click to collapse
so, if one were interested in using this anonymous persons script, how would one proceed?
adear11 said:
so, if one were interested in using this anonymous persons script, how would one proceed?
Click to expand...
Click to collapse
i would imagine gathering all the files and putting them in the proper spots/folders would assemble a replica of this script. i was just mentioning you should look thru to see if there is anything taht helps you tho
In short, in order to relock the bootloader, you have to flash signed software in the process.
Ugh why did I try this lol.. Still having problems. I restarted my computer and that fixed the problem "waiting for device" now in cmd it will at least recognize the phone BUT, I get this trying to figure out some information
getvar:cid FAILED (command write failed (unknown error))
Hello, A few days ago I ordered a Moto G which arrived this morning. I went onto Motorola's bootloader unlocking tool (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b) and attempted to unlock my Moto G's bootloader. To my discontent, I got an error message. "Your device does not qualify for bootloader unlocking." My device is a first generation Moto G running KitKat 4.4.4. I have been looking all day for a solution, but nothing has turned up. I have tried scrolling to the bottom of the T&A form and accepting the terms before clicking "Can my device be unlocked?" I have tried unlinking my Motorola ID, and I have tried using different browsers. I am absolutely positive I'm entering the "fastboot oem get_unlock_data" return correctly. If anyone can help, please do. I'll paste the return below.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
(bootloader) A00000510C598300#54413936353134
(bootloader) 49594200585431303238000000#FC60
(bootloader) DC73B20014F7E300C8D22FDFADAC524
(bootloader) DFABF#8ACC1F070F000000000000000
(bootloader) 0000000
OKAY [ 0.156s]
finished. total time: 0.156s
Certain carriers prevent moto from providing unlock keys. AT&T, Verizon, and I'm sure there's others. Your best bet is to try to adapt the newest root method for the x to our device or find a Chinese middleman to get you a key.
Sent from my XT1028 using Tapatalk 2
jacobas92 said:
Certain carriers prevent moto from providing unlock keys. AT&T, Verizon, and I'm sure there's others. Your best bet is to try to adapt the newest root method for the x to our device or find a Chinese middleman to get you a key.
Sent from my XT1028 using Tapatalk 2
Click to expand...
Click to collapse
I know it's a Verizon prepaid phone, and I knew Verizon was going to cause trouble. But I got it from Best Buy brand new for $40, so I don't have too much to complain about. Do you think I could go through SunShine to get an unlock code? I'm sure I could scrape up $25 pretty quick.
As long as you haven't updated past 4.4.2 afaik, it will still work. 4.4.4 won't work with sunshine though.
Unless there's money to be made, not much effort is going to be put into it. I just don't see any more progress with this thing unless there's a bounty involved. I'd do it myself for free if I had the time and knowledge to do so.
Sent from my XT1028 using Tapatalk 2
Do you think I could go to a Verizon store and ask them to unlock the bootloader for me?
Nope. You can only get the code from moto and if the phone is on that blacklist, its not gonna happen.
Sent from my XT1028 using Tapatalk 2
I like rooting my devices as I like having control over them and what they do. The Galaxy A32 5G is no exception so I was disappointed to see that the OEM Unlocking was not even shown in the Developer menu. I did a little research and basically if you got this phone through the 5g Trade-Up promotion (I suspect most did) then you're stuck on stock until April 19th 2023 or later when these phones get paid off. So unless you pay it of sooner or are in the military being deployed overseas, then you're stuck on stock.
Reference: https://www.t-mobile.com/responsibility/consumer-info/policies/sim-unlock-policy
Check again in a week or so. Samsung phones always block displaying the oem unlock option for that long, from what I have read.
scottyrick2 said:
Check again in a week or so. Samsung phones always block displaying the oem unlock option for that long, from what I have read.
Click to expand...
Click to collapse
There also is a special binary from T-Mobile that needs to be flashed.
I don't think we will ever see it. My A10e still has no OEM unlocking option and its been active for months.
Also as a test OEM unlock does not show up even when the A32 5G is carrier unlocked either
How about some kind of turbo sim? May be some paid services ? Really need to use with another sim... And if I pay it off I will not get credits, right?
hyelton said:
I don't think we will ever see it. My A10e still has no OEM unlocking option and its been active for months.
Also as a test OEM unlock does not show up even when the A32 5G is carrier unlocked either
Click to expand...
Click to collapse
I was able to convince T-Mobile to unlock my phone. I can confirm that network unlock does not enable OEM unlock option in Developer Options.
Elastep said:
How about some kind of turbo sim? May be some paid services ? Really need to use with another sim... And if I pay it off I will not get credits, right?
Click to expand...
Click to collapse
Wait til you get at least 1 bill credit before you pay it off just to make sure the promotional credits are active. But if you do pay off the phone, you'll still receive the promotional recurring device credits as long as that line remains active. Info here if you want to read the details by T-Mobile.
jke000 said:
Wait til you get at least 1 bill credit before you pay it off just to make sure the promotional credits are active. But if you do pay off the phone, you'll still receive the promotional recurring device credits as long as that line remains active. Info here if you want to read the details by T-Mobile.
Click to expand...
Click to collapse
That's awesome!!! Att stopped paying you promo credits as soon as you pay it off... I'll definitely give it a shot! Thanks for the hint!
Can anyone get a stock unlocked rom build from their phone that has been unlocked by T-Mobile? Even the bootloader.img? We could all flash it and it might work for us.
For example,
Taking a dump of the bootloader partition such as this:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Magnetox said:
Can anyone get a stock unlocked rom build from their phone that has been unlocked by T-Mobile? Even the bootloader.img? We could all flash it and it might work for us.
For example,
Taking a dump of the bootloader partition such as this:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Click to expand...
Click to collapse
T-Mobile phones can only be carrier unlocked, which I believe is done via the network and IMEI, not through software/boot loader. T-mobile phones can not be OEM unlocked at this time. I am not sure if a carrier unlocked T-mobile dump would get us any closer to a root, and I don't think a dump is possible via the directions you posted since it requires root.
DeadDjembe said:
T-Mobile phones can only be carrier unlocked, which I believe is done via the network and IMEI, not through software/boot loader. T-mobile phones can not be OEM unlocked at this time. I am not sure if a carrier unlocked T-mobile dump would get us any closer to a root, and I don't think a dump is possible via the directions you posted since it requires root.
Click to expand...
Click to collapse
Dumps actually don't require root AFAIK, you sure? Even then, a T-Mobile unlocked person could easily root boot.img with magisk and then pull it.
Magnetox said:
Dumps actually don't require root AFAIK, you sure? Even then, a T-Mobile unlocked person could easily root boot.img with magisk and then pull it.
Click to expand...
Click to collapse
The dump instructions you linked require root. Is there an updated guide that does not require root? I'm happy to try.
Could we use the info and resources here https://www.getdroidtips.com/stock-rom-samsung-sm-a326u-firmware/
to create an already rooted stock rom and flash it via odin?
Chad The Pathfinder said:
Could we use the info and resources here https://www.getdroidtips.com/stock-rom-samsung-sm-a326u-firmware/
to create an already rooted stock rom and flash it via odin?
Click to expand...
Click to collapse
ill look into this
It will not work, it will fail due to bad signatures.
Magnetox said:
Can anyone get a stock unlocked rom build from their phone that has been unlocked by T-Mobile? Even the bootloader.img? We could all flash it and it might work for us.
For example,
Taking a dump of the bootloader partition such as this:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Click to expand...
Click to collapse
working on this.
Any luck?
If this phone (A326U) can't have the bootloader unlocked it is of almost no use to me. I wonder if I can return it.
It will go to fastboot and can be seen via fastboot devices. Issuing fastboot flashing unlock returns
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I suppose this means existing bootloader does not have these commands in it or the missing OEM locking option is preventing the command from running?
Also I am wondering if there is somewhere to buy one that can have the bootloader (like for Metro PCS or other).
T-Mobile indicates they will bring a phone in to their network that can be unlocked but their policies (as mentioned in other threads) preclude unlocking a T-Mobile sourced device that has not been on their network for 40 days or after the 2 year contract if it is a contract purchased phone. An externally sourced phone can be added to their network and unlocked for SIM and bootloader.
injuhneer said:
Any luck?
If this phone (A326U) can't have the bootloader unlocked it is of almost no use to me. I wonder if I can return it.
It will go to fastboot and can be seen via fastboot devices. Issuing fastboot flashing unlock returns
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I suppose this means existing bootloader does not have these commands in it or the missing OEM locking option is preventing the command from running?
Also I am wondering if there is somewhere to buy one that can have the bootloader (like for Metro PCS or other).
T-Mobile indicates they will bring a phone in to their network that can be unlocked but their policies (as mentioned in other threads) preclude unlocking a T-Mobile sourced device that has not been on their network for 40 days or after the 2 year contract if it is a contract purchased phone. An externally sourced phone can be added to their network and unlocked for SIM and bootloader.
Click to expand...
Click to collapse
Mines rooted. theres a service for unlocking the bootloader
Buy directly from Samsung and you wont have bootloader problems
Here you can unlock bootloader
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Today I used the Samsung chat option on the website and asked for the unlock code for my A32 5G on Metro POS network. They put a ticket in for unlock code request. I'll let you know how it goes!
Hi All,
Been at this for several hours today and feeling a bit frustrated. Here's the context.
I bought a used Verizon Galaxy Note 10 and took it to another country.
I arrived and put a sim card in *(the phone is intended to stay here)
4G signal appeared and text messages came in
Phone blocked signal and said "sorry, your device cannot be activated on another Network right now" then it says to call Verizon.
I call Verizon and ask how to unlock.
After transferring to multiple agents, the answer is that the phone is not locked in their system and that upon inserting a SIM from another carrier, I should be prompted to put in a code and it will be "00000000" to unlock the phone
The phone never presents this option and is perpetually unable to activate because of this sim lock.
At this point, I started reading up on how I could get around this and settled on using odin to flash firmware for a different carrier and maybe having to flash the SM-N970U1 packages because that should allow me to have different stock firmware.
So I proceed to download various different images.
Here is the TMB image for SM-N970U that I downloaded:
https://samfw.com/firmware/SM-N970U/TMB/N970USQU6FUBH
I also figured maybe I would be able to flash the verizon base image and get around this lock:
https://samfw.com/firmware/SM-N970U/VZW/N970USQU6FUCD
So then I proceed to use Odin3_v3.14.4 and place all of the 4 files in their corresponding fields in odin. The file list is as follows for one of the packages:
BL_N970USQU6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
AP_N970USQU6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
CP_N970USQU6FUD9_CP19049000_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_OMC_OYN_N970UOYN6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
I click start, the phone is recognized and then the flashing appears to occur successfully until it says pass at the end.
I reboot the phone and I notice right away that the signal is present, but then disappears and as the phone initializes the VERIZON message appears again.
Immediately I'm thinking, ok, I've just reflashed it with the TMobile image but the phone boots and says verizon and the sim lock is still there, so I probably didn't do something right.
So I factory reset, try again, no changes, I try adding the USERDATA and it also does nothing different.
At this point I'm willing to try the U1 firmware, so I download from here:
https://forum.xda-developers.com/t/n970u-and-n970u1-firmware-links-here.3957705/
But when I run the odin flash, I get model mismatch, yet the thread says they're compatible as U1 is just the samsung unlocked version. so I try the odin patch b found here:
https://odindownload.club/download/197/Odin3-v3.14.1-3B-PatcheD.zip
And it fails to write.
I am in desperate need of help as I've been unable to find more specific information, typically in threads people may say they've resolved the issue, but then they don't actually indicate what steps they took, or any of the details surrounding the resolution. If I can get help getting this resolved, I can document the exact steps i've taken in explicit detail so that others can follow them and achieve the same result.
Update:
Downloaded FRIJA to get the latest firmware, am going to explore doing a nand erase and repartition, followed by flashing tmobile firmware to see if that gets around it.
following:
https://technastic.com/odin-nand-erase-samsung/
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Verizon has a 6 month unlock policy. if the phone is free of debt and older than 6 months it should be automatically unlocked. phone them, you bought the phone in good faith.
jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
That's why I am thinking of wiping the NVRAM and just re-partitioning. Then I'll flash a non-verizon system onto it. Could be that this resolves it.
Thoughts?
3mel said:
Verizon has a 6 month unlock policy. if the phone is free of debt and older than 6 months it should be automatically unlocked. phone them, you bought the phone in good faith.
Click to expand...
Click to collapse
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.
4rg3ntum said:
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.
Click to expand...
Click to collapse
With AT&T they give you requested then they gave you an unlock code, it's not automatic. At least it was like this a few years back.
4rg3ntum said:
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.
Click to expand...
Click to collapse
sorry yeah, 60 days is the right period.
jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
So this appears to be true.
I loaded up ADB and turned on USB debugging and started passing shell commands through and found these files in the system with nvram in the name:
/sys/module/dhd/parameters/nvram_path
/vendor/firmware/nvram.txt_ES03_semco_b0
/vendor/firmware/nvram.txt_1rh_es13_b0
/vendor/firmware/nvram.txt_CS01_semco_b1
/vendor/firmware/nvram.txt_ES02_semco_b0
/vendor/firmware/nvram.txt_1rh_es43_b1
/vendor/firmware/nvram.txt_1rh_es41_b1
/vendor/firmware/nvram.txt_1rh_es32_b0
/vendor/firmware/nvram.txt_ES00_semco_b0
/vendor/firmware/nvram.txt_ES01_semco_b0
/vendor/firmware/nvram.txt_1rh_es12_b0
/vendor/firmware/nvram.txt_1rh_es42_b1
/vendor/firmware/nvram.txt_1rh_es11_b0
Makes me wonder if the value for locked/unlocked is editable in one of those files.
a sample of what is in the /vendor/firmware/nvram.txt_ES03_semco_b0 file:
### RSDB mode Parameters(Both core are active)
## 2g normal:15dB airplane:14dB
#slice/1/grip_rsdb_dynsar_2g=0xbcbc
#slice/1/grip_rsdb_dynsar_2g_2=0xb8b8
## 5g normal:13dB airplane:12dB
#grip_rsdb_dynsar_5g=0xb4b4
#grip_rsdb_dynsar_5g_2=0xb0b0
#
### FCC Mode: 10dB
#slice/1/fccpwrch12=0x28
#slice/1/fccpwrch13=0x28
In any case I have an issue that I can't seem to resolve. Every guide I have found about how to change carrier firmware is pretty straightforward. Yet when I flash the firmware successfully through odin for say, the sprint version of the phone, upon reboot, in about phone still says VZW, which basically tells me the phone isn't actually flashing.
I need to understand why I can't seem to get it to have another carrier's firmware. What am I doing wrong?
jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
Maybe I can edit this with ADB?
I have seen several forums where people with the same error message simply flashed another carriers firmware onto the phone and were able to get around it.
Here is someone saying they tried the U1 firmware and it gave them the option to put in an unlock code:
https://forum.xda-developers.com/t/is-verizon-locking-s10.3908683/post-80813873
Every time I try to flash the U1 firmware odin tells me model mismatch.
Update:
I flashed the latest available ATT version of U1 firmware from here:
https://samfw.com/firmware/SM-N970U1/ATT/N970U1UEU6FUDA
Using Odin patch 3B downloaded from here:
https://www.droidmirror.com/downloading/download-odin3_v3-13-1_3b_patched-zip
Having tried many U firmware + USERDATA from different carriers and never was able to get it to say anything other VZW in the about phone section.
By going to the U1 version I was able to get the unlock code portion to pop up when inserting the sim card, the phone also claims it's model number is SM-N970U1 instead of SM-N970U now.
The code Verizon gave me on the phone 0000 0000 flat out DOESN'T work. I called again today and they had their manager use a tool to provide an unlock code because the "unlock" button in their system didn't appear for my IMEI.
That system said the unlock code is 0000 0000 just like the tech the previous day. So now, they're transferring me to the advanced technical support, but somehow I doubt they will give me a code.
In any case, what I would rather do is go through ADB and try to get some binaries or text files out (may require root for these files) and get the unlock code from the device itself.
I wish this thread was more active because there are some good opportunities here to explore the OS itself and the files in it as well as tools that can be used to read the binary.
Spoke with "Advanced" support at verizon. They had no way to generate a code to unlock the device. Basically Verizon's systems didn't automatically generate an unlock code after the previous owners had the phone activated for the minimum 60 days. Because the phone was a prepaid phone and not a post paid phone, their system deleted the history of the of the prepaid account after a certain period of time when the previous owner had sold the phone to the repair shop and it sat there for months.
BASICALLY, Verizon phones are uniquely equipped with a block that prevent legitimate purchasers of various types from being able to use their devices as they hold everyone hostage with their network locking.
It looks like I can't root the device either because of the oem unlock option not being present and the workaround of changing the date not presenting the option.
At this point I'm looking to root the device so I can inspect the OS
4rg3ntum said:
It looks like I can't root the device either because of the oem unlock option not being present and the workaround of changing the date not presenting the option.
At this point I'm looking to root the device so I can inspect the OS
Click to expand...
Click to collapse
Hello I came across your thread because I am having the same issue. I think mine is similar because thus phone was a replacement through asurion/verizon. It also says its unlocked when verszon looks and when asurion looks, but I do not have service for more than 10 secind with my new AT&T Sim. Have you found anything new?.
I also looked into rooting the phone but I don't plan to keep this phone and if I want to do the trade in process and they see the root on the back end I will not receive the trade in money.
TomHanks92 said:
Hello I came across your thread because I am having the same issue. I think mine is similar because thus phone was a replacement through asurion/verizon. It also says its unlocked when verszon looks and when asurion looks, but I do not have service for more than 10 secind with my new AT&T Sim. Have you found anything new?.
I also looked into rooting the phone but I don't plan to keep this phone and if I want to do the trade in process and they see the root on the back end I will not receive the trade in money.
Click to expand...
Click to collapse
If Verizon says the phone is unlocked, make sure to Flash the U package with Verizon bloat. Connect phone to Wifi and the unlock should happen. They only seem to unlock when on the Verizon bloat U package. Anything other than that and the phone stays locked. Once it unlocks you can flash back to whatever you want.
I just wanna learn how to begin the rooting don't know what driver how to get a sdk what app nothing?
I'm looking at the A13 as well since the GS5 is now blocked by AT&T.
I just spoke to Samsung, and they told me the A13 G5 unlocked version purchased directly from them comes with an unlocked bootloader.
I think I just wet myself.
MaddogK said:
I just spoke to Samsung, and they told me the A13 G5 unlocked version purchased directly from them comes with an unlocked bootloader.
I think I just wet myself.
Click to expand...
Click to collapse
What about flashable firmware?
Rularick5 said:
What about flashable firmware?
Click to expand...
Click to collapse
I don't think there's any yet, it's only been on the market for a few months. Aside from it's size it's pretty nice, I've had it 2 weeks and love the battery life.
MaddogK said:
I just spoke to Samsung, and they told me the A13 G5 unlocked version purchased directly from them comes with an unlocked bootloader.
I think I just wet myself.
Click to expand...
Click to collapse
This one dosnt
Samfirm should have the version of android you need for you're phone you need the Samsung flash tool su+twrp+magisk is optional good luck! Ps.always back up everything
I will be working on mine purchased from Metro PCS. Its OEM bootloader is locked at the moment. I will be using Magisk and flashing a TWRP. Utilizing an ADB wireless USB connection from PC. I will keep you posted if someone else doesnt beat me too it. Either way this thread is going so im sure together we can knock this out. Im going to do my LG Stylo 4 firsy. Its OEM came unlocked from Metro PCS...so i scored. Just havent had time. I just did my ZTE ZMax Pro Z981 from Metro PCS...it also was unlocked OEM. They will all need a PC usb connection and Magisck. You can find them in threads here. Good luck. Will post again when i get time. Hope this helps a little. Here you might not get an answer you want...but if you dig youll find what youre looking for...just got learn by doing...like they said...always backup... everything...first...dont forget to remove sd before you factory reset or you will wipe it. And your phone. If youre not sure...dont change things you dont know...you will brick your phone. Follow directions you find in threads...and you will be fine. I learned how to be a great chef from other chefs who told me the ingredients but never amounts of ingredients. Thats how you become a great chef and also become great developer...good luck guys. Im learning too. Share what you learn. FYI...the one click....dont bother...IJS...PC you will need for this....
GeekNout23 said:
I will be working on mine purchased from Metro PCS. Its OEM bootloader is locked at the moment. I will be using Magisk and flashing a TWRP.
Click to expand...
Click to collapse
How do you plan on flashing those if the bootloader is locked.....?
Sorry to break it to you, but it's a Samsung thing. It doesn't matter if it's a device from a carrier or carrier-free directly from Samsung, if you buy a U.S. Samsung phone you will not unlock bootloader freely.
ShaDisNX255 said:
Sorry to break it to you, but it's a Samsung thing. It doesn't matter if it's a device from a carrier or carrier-free directly from Samsung, if you buy a U.S. Samsung phone you will not unlock bootloader freely.
Click to expand...
Click to collapse
Correct
first you need oem unlock on that takes pluging in phone holding volume+/- (both) and power till it shutdown and restarts with the unlock option in recovery
Just bought this but the 5G version
Hi, I just rooted my Samsung Galaxy A13. Here's a quick tutorial of what worked for me:
Prerequisites:
Install Heimdall onto your computer. I used Manjaro Linux as my OS, and haven't tested anything else. Install any drivers if necessary.
Install Magisk onto your phone. I recommend using the F-Droid store/app, or Magisk's GitHub page.
Steps
Install any updates for your phone.
Unlock Bootloader
First of all you need to unlock the bootloader:
Enable Developer Mode by navigating: Settings > About Phone > Software information.
Tap Build number about 7 or 8 times until it says You're now a developer.
Allowing the bootloader to be unlocked:
Settings > Developer Options > Enable OEM unlocking.
Allow it to be enabled if prompted.
Turn off your device.
Turn on Download Mode by holding down Volume Up and Volume Down.
When you see a blue screen, hold Volume Up until it shows Unlock Bootloader screen.
Press Volume Up to confirm.
Flashing firmware
https://samfw.com/ is a good resource for downloading firmware. Be careful that you're downloading the correct firmware though. You can find information by navigating on your phone:
Settings > About Phone, and Settings > About Phone > Software information. If you call *#1234# it will show you the current firmware.
Extract the archive.
Extract the file staring with AP.
Extract the file boot.img.IZ4.
Move boot.img onto your phone.
Open Magisk. Click install. Locate and patch the file. Move the file back onto your computers.
Extract the file starting with CSC. Locate the pit file.
Open Heimdall.
Choose the pit file and the patched boot image.
Put your phone in Download Mode and connect via USB.
Flash your phone.
If it worked successfully, your phone will reboot. It will probably throw an error before starting. Choose to do a factory reset. This will delete all the user data, but the patched boot file will stay in place.
Download Magisk again. Follow the prompts.
To test if you have super user access, install Termux from the F-Droid store. type su into the terminal. You will get a pop up asking if you want to give super user permissions.
Congratulations! You're now the UNIX sysadmin of your own phone!
hello Everyone, a friend of mine from America bought an A13 5G, now we are in Europe and the phone is blocked.
exactly inserting a European sim says:
Phone locked. Please contact our customer service center to unlock your phone.
i tried to unlocked bootloader, but unfortunately i don't have OEM unlock present, no way i get it out!
there is a complicated procedure with Flashing a Combination Firmware, but it looks difficult!!! I haven't done it yet.
but would it be possible to only unlock the phone to use European sims?
many thanks
K
krellz said:
hello Everyone, a friend of mine from America bought an A13 5G, now we are in Europe and the phone is blocked.
exactly inserting a European sim says:
Phone locked. Please contact our customer service center to unlock your phone.
i tried to unlocked bootloader, but unfortunately i don't have OEM unlock present, no way i get it out!
there is a complicated procedure with Flashing a Combination Firmware, but it looks difficult!!! I haven't done it yet.
but would it be possible to only unlock the phone to use European sims?
many thanks
K
Click to expand...
Click to collapse
Unlocking the bootloader would not do anything for you in regards to network unlocking. Those are 2 totally separate and distinct procedures.
What's the Baseband Version on the device? You can find that under Settings-->About-->Software Information (and don't do any software updates to the device if it prompts you to)
Hello, the first thing would be to unlock the bootloader which is very easy in Samsung terminals, In all Samsung is the same, you can see the following video that I recommend. No PC needed, The video is in Spanish but it is only to follow the same steps:
The second thing would be to get root, the easiest would be with Magisk, I recommend you watch this video since it is not necessary to format the cell phone, the video is also in Spanish, but you still follow the same steps. In this case, a PC is necessary:
Soon I will make a post myself, teaching you how to root without losing data, the same way as in the video, in case you didn't understand the video.
There is no boot.img.IZ4 im my ap file
ok i found the boot.img I extracted the ap file with winrar before. some how it does not see the .img files but untarring on linux worked. i managed to re flash the ap fille with odin and i saw lot of .img files being flashed and the extracted foldersize by winrar was way smaler than the archive. so that made me look at the ap file and i got the boot.img patched by magisk and made an lz4 file out of it how do i get that boot.img.lz4 back in the archive?
also whats wrong with fast boot?
"fastboot devices" lists my device when its connected but like many here post it does not work with other commands it failes like thIs :
fastboot flash bootloader b.img
Sending 'bootloader' (32768 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
Tried other examples too but nothing works tried the fastboot included in android studio and one of the minimal adb/fastboot. the boot loader is unlocked (Not using fastboot) and odin works fine. my phone is in the "entertering fastboor mode" state .its a samsung galaxy a13 g5 and i flashed this firmware using odin
AP_A136BXXS2BWA1_A136BXXS2BWA1_MQB61124574_REV00_user_low_ship_MULTI_CERT_meta_OS13 now its stock again with no accounts.
fastboot reboot does work so some is right.
fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
i hope some one can point me in the right direction.
thx
Hans de Groot said:
i hope some one can point me in the right direction.
thx
Click to expand...
Click to collapse
Fastboot isn't functional on Samsung devices. Samsung replaces it with Download mode. Therefore, all flashing is done via Download mode using Odin, not via fastboot mode using command terminal