Database Info

[Q] Questions about unlocking, rooting and modems.

I'm sorry if this questions have been asked before. I read through many pages on the Q&A section of this phone and didn't come with clear answers to my questions.
This is the first time I will attempt to unlock, root and flash a ROM on an Android phone.
First of all, I've read and I still don't know if I can flash a custom ROM, or one of those Brazil/Orange JB images available and be able to have the phone unlocked to use with different carriers. Jelly Bean hasn't been released to this phone here in Mexico yet.
1.- I don't mind unlocking the bootloader with Motorola solution. Is this the best way to unlock it?
2.- Flashing a custom ROM or a stock one makes the phone unlocked so I can use it with different carriers?. If the answer is yes, what ROM do you recommend. Are those Brazil/Orange images good for any user or its better to stick with third-party ROMs?
3.- If the answer to number 2 is NO, what should I do in order to unlock the phone? I need to be able to use in Mexico (the phone if from Telcel) and also use it on the United States (with AT&T). I've read about modem files that had to do with carriers but I'm not sure if I need special files to unlock this phone? If this is needed, where do I start or where do I find this files?
4.- If there is something else I need to know (and I didn't asked here) about unlocking the phone and flashing a stock or third-party ROM and have it unlocked to work with other carriers, please let me know by replying.
What are you guys using to backup the factory image? I haven't fiddled with Android for a while after flashing a Kindle Fire many times. I got a Nexus 7 and I haven't needed to root, unlock or try third party ROMs. The last time I used TWRP to backup the image of the Kindle Fire I think.
Thanks in advance

ajua said:
I'm sorry if this questions have been asked before. I read through many pages on the Q&A section of this phone and didn't come with clear answers to my questions.
This is the first time I will attempt to unlock, root and flash a ROM on an Android phone.
First of all, I've read and I still don't know if I can flash a custom ROM, or one of those Brazil/Orange JB images available and be able to have the phone unlocked to use with different carriers. Jelly Bean hasn't been released to this phone here in Mexico yet.
1.- I don't mind unlocking the bootloader with Motorola solution. Is this the best way to unlock it?
2.- Flashing a custom ROM or a stock one makes the phone unlocked so I can use it with different carriers?. If the answer is yes, what ROM do you recommend. Are those Brazil/Orange images good for any user or its better to stick with third-party ROMs?
3.- If the answer to number 2 is NO, what should I do in order to unlock the phone? I need to be able to use in Mexico (the phone if from Telcel) and also use it on the United States (with AT&T). I've read about modem files that had to do with carriers but I'm not sure if I need special files to unlock this phone? If this is needed, where do I start or where do I find this files?
4.- If there is something else I need to know (and I didn't asked here) about unlocking the phone and flashing a stock or third-party ROM and have it unlocked to work with other carriers, please let me know by replying.
What are you guys using to backup the factory image? I haven't fiddled with Android for a while after flashing a Kindle Fire many times. I got a Nexus 7 and I haven't needed to root, unlock or try third party ROMs. The last time I used TWRP to backup the image of the Kindle Fire I think.
Thanks in advance
Click to expand...
Click to collapse
Unlocking BL doesn't change the unlocked status of the phone for carriers. If you want to unlock it to use with different carriers you'll have to pay the unlock fee to whoever you choose to unlock with.
1. Answered above.
2. Custom ROMs or ROMs from different carriers won't unlock the carrier.
3. I believe there is some sort of file modification to have it unlocked. Not sure what you have to do but if I remember correctly its risky and affects IMEI.
Sent from my RAZR HD XT925

saloums7 said:
Unlocking BL doesn't change the unlocked status of the phone for carriers. If you want to unlock it to use with different carriers you'll have to pay the unlock fee to whoever you choose to unlock with.
1. Answered above.
2. Custom ROMs or ROMs from different carriers won't unlock the carrier.
3. I believe there is some sort of file modification to have it unlocked. Not sure what you have to do but if I remember correctly its risky and affects IMEI.
Sent from my RAZR HD XT925
Click to expand...
Click to collapse
I know the bootloader won't change the locked status. As this is the first time flashing a phone, not a tablet, I thought that using a custom ROM or one from different carrier would work for this.
I've tried other SIMs on the phone (it's my sister's, not mine) but the phone didn't asks for a code when a SIM from a different carrier is inserted. I haven't bought any code because of this.
Anyone has a suggestion on what to do to have the phone unlocked to use with different carriers?

Bootloader unlock for Moto z3

I just bought the Verizon Moto Z3 today from Verizon solely with the purpose of rooting this phone so that it could be my dedicated computer/phone for my car computer screen. Trying to figure this out is making me come to a conclusion that this can't be unlocked? Is that true? Is there a way around this so that I can root this phone or did I just sign up for a 2 year contract with a POS that i have no use for now?

I have read that the Verizon makes all phones they have not unlockable. Should have read that too before buying maybe?

phelix208 said:
I just bought the Verizon Moto Z3 today from Verizon solely with the purpose of rooting this phone so that it could be my dedicated computer/phone for my car computer screen. Trying to figure this out is making me come to a conclusion that this can't be unlocked? Is that true? Is there a way around this so that I can root this phone or did I just sign up for a 2 year contract with a POS that i have no use for now?
Click to expand...
Click to collapse
El Hombre Principal said:
I have read that the Verizon makes all phones they have not unlockable. Should have read that too before buying maybe?
Click to expand...
Click to collapse
Verizon is notorious for locking the bootloader on all of their devices. If you want a device that can be rooted and/or flash custom ROMs, then, from now on, you just need to stay away from anything offered by Verizon, regardless of how long you've had service with them or how pleased you are with their service and devices.
They can't be rooted by flashing TWRP and/or SuperSU or Magisk, they can only be rooted by using one of the many different universal rooting apps or universal rooting programs on PC, and that is only IF one of them has an exploit that works, if these universal tools won't work, you're out of luck.
Sent from my LGL84VL using Tapatalk

So buying an unlocked phone that is combatable with Verizon is the way to go or are you saying leave Verizon because not that is combatable with their system is rootable.

DocNomad said:
So buying an unlocked phone that is combatable with Verizon is the way to go or are you saying leave Verizon because not that is combatable with their system is rootable.
Click to expand...
Click to collapse
Using a device from somewhere else that is unlocked and has root and custom ROMs available for it and is also compatible with the Verizon network is the way to go.
Do some searches for unlocked devices that you might be interested in, make a note of the specific model number. Then, do some searches with those model numbers to see if they have root and custom development available, like this:
"How to root (the specific model number)"
And
"TWRP for (the specific model number)"
***IMPORTANT NOTE***
The device absolutely must have an unlocked bootloader or at least can be unlocked by some known method for that specific device model number, otherwise, you won't be able to use TWRP or custom ROMs but you "might" still be able to have root, just not custom recovery or custom ROMs, so you'll have to go a little deeper with your searches to verify bootloader status on the chosen device.
And
"Custom ROMs for (the specific model number)"
Those search terms should find whatever is available, if available for those model numbers.
Then, go to Verizon's website to check if the devices are compatible with the Verizon network.
Basically:
1) find a device you're interested in that is unlocked and note its model number and verify the bootloader status for the device.
2) search to see if there is root and custom development for that model.
3) verify it is compatible with Verizon network.
Find something that satisfies those criteria, then you can activate the device on Verizom when you get it then root and or flash the device after you get it successfully activated on the Verizon network. Then you should be good to go to use the device with Verizon and continue using/updating the custom software and/or customize/modify the device. Just be sure that anything you use is for the specific model number of your device. Using stuff that is not for your specific model number will almost certainly lead to a bricked device.
Sent from my SM-S767VL using Tapatalk

Un-rootable thanks to manufacturer. What is it exactly?

What does the manufacturer do to the phone to make it un-rootable?
This quote: "Strictly speaking, when we talk about a platform as open as the Android OS, it is almost impossible for a manufacturer to make an ‘un-rootable’ device."
would suggest that most likely the manufacturer is not making the phone un-rootable. So then that would leave the OS, but my 4.2.2 KitKat has and is rooted on other devices.
So who and what is at fault here? Seems to me that if it was software, that would be easy. Find an exploit and root. But if it was that easy then all phones/devices would be rootable.
That brings us back to hardware and the manufacturer.

RealRobD said:
What does the manufacturer do to the phone to make it un-rootable?
This quote: "Strictly speaking, when we talk about a platform as open as the Android OS, it is almost impossible for a manufacturer to make an ‘un-rootable’ device."
would suggest that most likely the manufacturer is not making the phone un-rootable. So then that would leave the OS, but my 4.2.2 KitKat has and is rooted on other devices.
So who and what is at fault here? Seems to me that if it was software, that would be easy. Find an exploit and root. But if it was that easy then all phones/devices would be rootable.
That brings us back to hardware and the manufacturer.
Click to expand...
Click to collapse
It is more a matter of the carriers trying their hardest to prevent us from being able to unlock/root the devices they offer and less a matter of the manufacturer trying to prevent it.. They do this for several reasons. But the main reasons are to prevent security breaches, to protect the information on their customer's devices, to prevent having to repair/replace devices that have been broken due to failed rooting/flashing/modifying attempts and to prevent us from using their devices on another carrier's network.
It is considered to be impossible to make devices that absolutely can't be rooted. They are all vulnerable in some manner, these vulnerabilities are called exploits, it's just a matter of finding the right exploit. When exploits are found, the manufacturer or carrier will patch the exploit and release an update for their devices to apply the patch.
The main thing they do to make devices unrootable is to use a locked bootloader, some even use specific hardware components to prevent unapproved software from booting.
It's a combination of things really, there is not necessarily one certain thing they do to keep us from rooting, because there are many different ways to unlock/root devices, they try their best to account for them all.
Sent from my SM-S767VL using Tapatalk

It is considered to be impossible to make devices that absolutely can't be rooted. They are all vulnerable in some manner, these vulnerabilities are called exploits, it's just a matter of finding the right exploit.
Click to expand...
Click to collapse
Can you direct me to the recommended newbie reading to get my learn on?
My Alcatel onetouch has stumped current one click methods, so it's time to learn and crack this puppy on my own.

RealRobD said:
Can you direct me to the recommended newbie reading to get my learn on?
My Alcatel onetouch has stumped current one click methods, so it's time to learn and crack this puppy on my own.
Click to expand...
Click to collapse
If all one click methods have failed, the only option left is to flash some kind of customized software or methods to modify parts of your boot and/or system partitions. Flashing custom software and modifying boot or system requires the device to have an unlocked bootloader.
This means that your first step is to determine whether or not your device has an unlocked bootloader. If it is unlocked, you can flash/modify the device, if it is locked, you can't flash/modify unless you find a method to unlock the bootloader, then you can flash/modify. Do some searches for methods to check your bootloader status.
If you find that the bootloader is unlocked, then you have a few choices:
1) if you can obtain a copy of your stock firmware then you can use the Magisk rooting method to modify the boot.img from your firmware to create a patched boot.img then flash that boot.img using the appropriate flash tool for your device brand.
2) if you can find a copy of TWRP custom recovery for your specific device model number you can flash the TWRP file using the appropriate flash tool for your device brand.
3) if there is no TWRP for your specific model number, you can build your own version of TWRP if the necessary resources are available for your specific model number.
4) if the necessary resources to build TWRP for your specific model number are not available, you can try finding a TWRP for a similar device with the same exact CPU that your device has and port that TWRP to be compatible with your own device.
Do your own searching and researching about each of these options, the more you read about them, the more you will understand.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
If all one click methods have failed, the only option left is to flash some kind of customized software or methods to modify parts of your boot and/or system partitions. Flashing custom software and modifying boot or system requires the device to have an unlocked bootloader.
This means that your first step is to determine whether or not your device has an unlocked bootloader. If it is unlocked, you can flash/modify the device, if it is locked, you can't flash/modify unless you find a method to unlock the bootloader, then you can flash/modify. Do some searches for methods to check your bootloader status.
If you find that the bootloader is unlocked, then you have a few choices:
1) if you can obtain a copy of your stock firmware then you can use the Magisk rooting method to modify the boot.img from your firmware to create a patched boot.img then flash that boot.img using the appropriate flash tool for your device brand.
2) if you can find a copy of TWRP custom recovery for your specific device model number you can flash the TWRP file using the appropriate flash tool for your device brand.
3) if there is no TWRP for your specific model number, you can build your own version of TWRP if the necessary resources are available for your specific model number.
4) if the necessary resources to build TWRP for your specific model number are not available, you can try finding a TWRP for a similar device with the same exact CPU that your device has and port that TWRP to be compatible with your own device.
Do your own searching and researching about each of these options, the more you read about them, the more you will understand.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Can't get past "Waiting on devices" when using
Code:
fastboot oem device-info
.
Device manager shows the phone is connected just fine.
The phone has no manual way to set fast boot, whether it be the buttons or entering numbers on the keypad.
Device recognized.
Code:
fastboot devices
returns nothing. I guess that means it's not in fast boot mode.
Code:
adb reboot bootloader
and
Code:
adb reboot fastboot
only reboots the phone.
On the other hand,
Code:
adb reboot recovery
does work.

RealRobD said:
Can't get past "Waiting on devices" when using
Code:
fastboot oem device-info
.
Device manager shows the phone is connected just fine.
The phone has no manual way to set fast boot, whether it be the buttons or entering numbers on the keypad.
Device recognized.
Code:
fastboot devices
returns nothing. I guess that means it's not in fast boot mode.
Code:
adb reboot bootloader
and
Code:
adb reboot fastboot
only reboots the phone.
On the other hand,
Code:
adb reboot recovery
does work.
Click to expand...
Click to collapse
Your device probably doesn't even have fastboot mode, some carriers remove fastboot from their devices, especially MVNO(subcontracted) networks.
Sent from my SM-S767VL using Tapatalk

Yep, looks like no Fastboot onboard...

galaxys said:
Yep, looks like no Fastboot onboard...
Click to expand...
Click to collapse
If it's just software, why can't it be bypassed, cracked, hacked, blown up etc?

RealRobD said:
If it's just software, why can't it be bypassed, cracked, hacked, blown up etc?
Click to expand...
Click to collapse
If you're asking about what was said about not having fastboot, it is a lack of software, as in, the software is not even there.
If you're asking if the software can be bypassed, it can, the trick is to find the right exploit. That is the problem, a working exploit has not been discovered for this device.
Without fastboot, there is no way to flash custom files such as TWRP or patched boot.img. This means, the only chance of rooting the device is if one of the one-click universal rooting apps or universal PC rooting programs has an exploit that just happens to network on this device.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
If you're asking about what was said about not having fastboot, it is a lack of software, as in, the software is not even there.
If you're asking if the software can be bypassed, it can, the trick is to find the right exploit. That is the problem, a working exploit has not been discovered for this device.
Without fastboot, there is no way to flash custom files such as TWRP or patched boot.img. This means, the only chance of rooting the device is if one of the one-click universal rooting apps or universal PC rooting programs has an exploit that just happens to network on this device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Have any fastboot-less phones in the past been rooted?
If so, do you have any recommended reading as far as exploit hunting is concerned?

Mandatory unlocked bootloader for rooting?

Hi everyone.
I'm thinking in buying a phone from CAT (CAT S42) and I'm not sure if I can unlock its bootloader. But I've seen on another forum that the CAT S31 has root available for it through Magisk, and I didn't see anyone mentioning having unlocked the bootloader. S42 has a MediaTek chipset and S31 has a Qualcomm chipset, if that helps.
So my question is: is unlocking bootloader MANDATORY to root a device? Can I just run a custom recovery, root the phone with that, and then the recovery gets overwritten on system boot? Or can I root through USB debugging without even needing custom recovery?
The CAT S31 I mentioned was rooted with Magisk, and as I said, I didn't see anyone talking about unlocked bootloader. But I also read Magisk changes the boot partition and the bootloader checks if it was modified. So I'm a bit confused with this too. It's also written that MiracleBox was used and I'm not sure that's the reason that I'm getting confused or not (I had never heard of this tool until now).
A set of software for obtaining ROOT privileges.
Driver_Qualcom_m.7z (9.27 MB) [link]
Enter HS QDSLoad 9008 mode from Vol + and Vol- off state and connect without releasing to USB
MiracleBox [link]
The Boot image is processed on the phone by the Magisk manager, then uploaded to the phone using Miracle again from the computer.
MagiskManager-v7.3.2.apk (2.71 MB) [link]
Just in case,
Backup firmware without / Data partition
Attached files
XposedInstaller_3.1.5-Magisk.apk (2.96 MB) [link]
Click to expand...
Click to collapse
How may they have done that?
I'm sorry, I don't understand a lot of the root requirements part, since I was lucky and my 1st phone had the bootloader unlocked alreaedy for some reason and the second was as easy as writting a single command. But about this phone there's almost nothing and I'd like to know the general about this. If it's really necessary to have the bootloader unlocked, for example. And if it's not, then what methods can I use with it still locked?
Thanks in advance for any help!

Hello DADi590,
Unfortunately I can't answer all of your questions about S42. I have one of them and I am also looking for and confused with root procedures. But I can tell you that unlock boot loader was just a matter of get developer options on (tapping version # 10 times), and inside you can toogle lock/unlock bootloader...
How to root it safely is what I do not know yet.
good luck!

@DADi590
Rooting the Android OS of a device in practice is nothing more than adding the su cmdlet known from Linux OS to the Android OS. To root Android OS in no case requires device's bootloader must get unlocked to do so.
FYI: The bootloader of an Android device is comparable to the BIOS of a Windows computer.

Actually, after some time I decided to leave CAT alone and buy a Blackview one. If I'd break the phone, at least it wouldn't be as expensive as the CAT S42 (I bought a BV9500 - not Pro or Plus, the normal one).
Since then (with help of adventures with a tablet of mine) I've learned some more things. One of them I was suspecting and was now confirmed (thank you @jwoegerbauer) which is to root the device, just a binary file is needed to be on the correct place: su. I didn't know it was on other Linux OSes though. Interesting!
So the idea is that just a recovery must be installed to root a device. That's it and nothing else, I believe. To install the recovery is the part where one might need to unlock the bootloader - or not, if the chipset manufacturer left a tool to write partitions directly, like MediaTek or Rockchip. On these 2 it's possible to write partitions directly with a locked bootloader (this means the bootloader on my 1st phone was and still is probably locked - like my BV9500 one is, and I flashed various partitions on it already, one of them, a TWRP recovery).
This explanation is for anyone else like me who would have this question. Bootloader is just to flash partitions and I think run modified ROMs too, but not too sure about that (I never use custom ROMs). [Btw, if I said something wrong, I'm happy to be corrected!]
armandrix said:
Hello DADi590,
Unfortunately I can't answer all of your questions about S42. I have one of them and I am also looking for and confused with root procedures. But I can tell you that unlock boot loader was just a matter of get developer options on (tapping version # 10 times), and inside you can toogle lock/unlock bootloader...
How to root it safely is what I do not know yet.
good luck!
Click to expand...
Click to collapse
I believe I asked this because I prefer that it's not required to unlock a bootloader to do stuff. If you screw the phone somehow with the bootloader locked and there's no tool to flash partitions on it and you must be on fastboot with an unlocked bootloader or whatever, you just bricked the phone. And I'd prefer that not to happen. That's why I chose to buy phones that don't need me to unlock the bootloader to do anything on them. That might mean I can't ever brick them (at least I never bricked my 1st phone with the various things I did on it which I later found out not being recommended at all XD).

I've unlocked the bootloader on my Cat S42. Can be done.

Question I have a samsung galaxy A13 can anyone tell me how to begin rooting after developer mode is unlocked and USB debugging in activated never used debug?

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