Database Info

[UNLOCK] Bootloader Unlock Package

Introduction
This is the bootloader unlock from ZTE. It was provided to me in private email by a ZTE engineer.
Warning
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Note
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool's unlock are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot, which provides a way to flash a custom boot and recovery (among other things).
Flashing Instructions
Place axon_mini_unlock.zip on the root of your sdcard.
Reboot into recovery.
Select "Apply update from SD card".
Select axon_mini_unlock.zip.
Usage Instructions
After the package is flashed, you may boot into the bootloader:
adb reboot bootloader
Once in the bootloader, you will see an on-screen menu. Additionally, you may access the typical fastboot commands:
fastboot oem device-info
fastboot oem unlock
fastboot flash ...
... etc ...
Download
axon_mini_unlock.zip
md5: ea8f1a21c8a46b3045d00f17a37fe359

So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?

Yes, that is correct.
JoeGatto said:
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Click to expand...
Click to collapse

This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Click to expand...
Click to collapse
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot.
Click to expand...
Click to collapse
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.

trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Yeah...verdandi is stuck on Marshmellow. But since it has different hardware it could brick if this is tried.

The ZTE engineer is USA based, he is not on the China development team (read: probably a support engineer). He said: "I attached the unlock update zip package, please try it. It is based on B14 build."
Sorry, that's all I have to go by for "official" information.
I do not want to be responsible for anyone bricking their device, so I cannot claim that this bootloader will work with anything other than a tulip device running 7.1.1 b14.
If you want to try and report back, I'm sure others will appreciate it. But I can't be responsible for the results.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse

Oh, and here is some more information to help you decide...
The volume key combo to enter EDL is handled by aboot (bootloader, eg. the thing we are flashing). This means even if you aren't currently able to use the key combo, you should be able to use it with the new aboot here. And if you can get to EDL, you can never really brick the device.
The volume key combo is detected very early in the aboot code. Like, first thing after basic platform init. So even if this isn't compatible with your device, it's likely we could restore the old aboot (assuming you back it up first, of course).
I'm convinced that the tulip is not locked based on my investigation today. So I have no idea if this aboot is properly signed. If your device is locked and this aboot is not signed properly, the lower boot loader won't load it. I'm not quite sure if that kicks you into EDL or not.
Not sure if that makes the decision easier or harder...

How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.

So here's the deal...
I initially assumed the bootloader was locked because... well... it's supposed to be. So I found the place in aboot code where it checks the lock flag in the devinfo partition. I used the firehose to write unlocked to that flag. Then I built TWRP, flashed it and it booted. So I assumed everything was working just as I expected.
Today, I flashed the aboot with fastboot support and ran "fastboot oem device-info". It said that my device was locked. So I went to look and, sure enough, my devinfo partition flag was still set. Hmm, that's odd.
So I wrote locked back to the flag. TWRP still booted. Now things are looking pretty suspicious.
But maybe the new aboot doesn't even support locking? So I flashed the original b14 version of aboot and TWRP still booted.
That's pretty hard evidence that aboot is ignoring the lock flag. I don't know what they did -- whether they just removed the code that reads the lock flag or introduced a bug or what.
This does not necessarily mean that the lower layers are unlocked. That is, the lower boot loader may still required a properly signed aboot. I don't know, and I'm not ready to brick my device trying to find out.
trpn111 said:
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
Click to expand...
Click to collapse

Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.

Ah, yes, you have the euro model. See the "calling all mini owners" thread, posts #76 and #77.
maestromony said:
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Click to expand...
Click to collapse

i get a message saying "cant update from sd card?"

yeshivabachur said:
i get a message saying "cant update from sd card?"
Click to expand...
Click to collapse
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.

JoeGatto said:
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
Click to expand...
Click to collapse
My battery was 80%+ mine still said can't update from sdcard

Aries2010 said:
My battery was 80%+ mine still said can't update from sdcard
Click to expand...
Click to collapse
Try turning on the OEM unlock setting in developer settings.

JoeGatto said:
Try turning on the OEM unlock setting in developer settings.
Click to expand...
Click to collapse
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware

Aries2010 said:
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Click to expand...
Click to collapse
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.

JoeGatto said:
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
Click to expand...
Click to collapse
Thank you sir I appreciate it I shall try it tomorrow.

here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?

The "standard" (not Samsung) method of updating via OTA is to ship:
1. Full images of any firmware partitions (rpm, tz, aboot, etc.)
2. Full image of boot.
3. A delta (patch) to system.
Also note that custom recoveries generally do not work with vendor OTA's.
This means that if you wish to apply an OTA, you must first have stock recovery and a completely pristine, unmodified system partition. The rest doesn't matter.
yeshivabachur said:
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
Click to expand...
Click to collapse

Calling all people with unlocked bootloader :)

So in a last effort to get the global ROM on my Chinese PDEM30, I decided to manually flash all of the global ROM images to my device. I managed to recreate the recovery image using some code from the OTA update (as it doesn't exist in the OTA download).
One big issue is the super partition, a feature exclusive to Android 10 which actually contains 4 logical partitions (system, vendor, product, odm). I thought I could rebuild this super partition into a raw file, convert to a sparse image and then flash it in fastboot, but it didn't work.
Long story short, I've bricked my Chinese device. I do also have the Global device (which doesn't obviously have an unlocked bootloader like my Chinese version).
So I can continue my tinkering in getting the global ROM onto the Chinese variant, can someone who's unlocked their bootloader (using the depth testing app), extract a copy of the super image for me using ADB? I believe it can be done using the following command but not 100% so can't test:
adb pull /dev/block/bootdevice/by-name/super
Would be massively appreciated and even willing to PAY someone to do it, getting desperate now!!

I don't have an unlocked device yet but as for dynamic partitions this might be able to help you mount them the right way: https://blog.isaacchen.cn/
(The same person also dumped the device tree for the PDEM30 as far as I can tell)
klanbo78 said:
So in a last effort to get the global ROM on my Chinese PDEM30, I decided to manually flash all of the global ROM images to my device. I managed to recreate the recovery image using some code from the OTA update (as it doesn't exist in the OTA download).
One big issue is the super partition, a feature exclusive to Android 10 which actually contains 4 logical partitions (system, vendor, product, odm). I thought I could rebuild this super partition into a raw file, convert to a sparse image and then flash it in fastboot, but it didn't work.
Long story short, I've bricked my Chinese device. I do also have the Global device (which doesn't obviously have an unlocked bootloader like my Chinese version).
So I can continue my tinkering in getting the global ROM onto the Chinese variant, can someone who's unlocked their bootloader (using the depth testing app), extract a copy of the super image for me using ADB? I believe it can be done using the following command but not 100% so can't test:
adb pull /dev/block/bootdevice/by-name/super
Would be massively appreciated and even willing to PAY someone to do it, getting desperate now!!
Click to expand...
Click to collapse

curtisy said:
I don't have an unlocked device yet but as for dynamic partitions this might be able to help you mount them the right way: https://blog.isaacchen.cn/
(The same person also dumped the device tree for the PDEM30 as far as I can tell)
Click to expand...
Click to collapse
Thanks for that, I can't use adb as I can only get into fastboot right now. I've attempted to get TWRP working so I can at least run adb, but no luck so far.
Once I do though I'm sure the link will be useful :good:

Come on people help a brother out!

I really want to help but i don't have unlocked bootloader. How can unlock bootloader?

tuanda82 said:
I really want to help but i don't have unlocked bootloader. How can unlock bootloader?
Click to expand...
Click to collapse
Can only be done (officially) on the Chinese version, steps are here: https://forum.xda-developers.com/find-x2-pro/how-to/how-to-unlock-bootloader-chinese-rom-t4160407
But basically, make sure you have registered an account with Oppo, install Oppo's "Depth Testing" app, log in and submit an application. It takes about a month to approve.
Once approved, the app will then unlock the bootloader.

Question Any solution to remove the annoying bootloader unlocked message ?

Hi everyone, this question is for developers who have some bases in hexadecimal programming, I would like to know if it is possible to remove the message after unlocking the bootloader, I had an LG V20 H990DS and I had followed the tutorial on this thread and it was working fine, is there a similar solution for the ROG 5.
[Guide][MOD] Hide unlocked Bootloader warning boot screen
. This fix is for those who want to get rid of the annoying Red Corruption warning screen!!. Disclaimer: You apply the fix at your own risk. I'm not responsible for any software or hardware damage it can lead. The only thing i can assure is...
forum.xda-developers.com

zinou213 said:
Hi everyone, this question is for developers who have some bases in hexadecimal programming, I would like to know if it is possible to remove the message after unlocking the bootloader, I had an LG V20 H990DS and I had followed the tutorial on this thread and it was working fine, is there a similar solution for the ROG 5.
Click to expand...
Click to collapse
That depends. I modified a Teclast T30 bootloader (Mediatek garbage) that forced a delay and printed an orange error message about the bootloader being unlocked. A bit of Arm64 reverse-engineering and I shorted the delay to 0ms (none, basically) and just cut the string short (null-byte) and it works fine on my junker tablet. I've just bought an ASUS ROG Phone 5, getting into it, but I'm nervous about touching anything without, say, TWRP or without knowing how to do a full raw backup and restore.

Yuji Saeki said:
That depends. I modified a Teclast T30 bootloader (Mediatek garbage) that forced a delay and printed an orange error message about the bootloader being unlocked. A bit of Arm64 reverse-engineering and I shorted the delay to 0ms (none, basically) and just cut the string short (null-byte) and it works fine on my junker tablet. I've just bought an ASUS ROG Phone 5, getting into it, but I'm nervous about touching anything without, say, TWRP or without knowing how to do a full raw backup and restore.
Click to expand...
Click to collapse
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
There ya go. Good luck

twistedumbrella said:
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
There ya go. Good luck
Click to expand...
Click to collapse
Thanks. Just waiting to figure out how to do a raw backup and restore, then I can get to it. If TWRP isn't required to do a raw backup and restore, then I can also begin work on porting TWRP. I've some experience, but not the most when it comes to TWRP porting.
*Edit* I'd like to add, reverse-engineering the ASUS Unlock Tool seems to show the limits on unlocking may be artificial by ASUS. Uses a call-home to fetch data to unlock with. The logic though may be in another castle, I mean package. The FOTA app does the same thing.
*Edit* By the way, does anyone have the exact message that displays about the bootloader being unlocked? I might be able to begin work tracking it down to remove as well as any delay (if there is one).

Some mods target the abl.img (possibly Android Boot Loader) so that may be one place to start. I personally never bother with backups, so I didn't really consider that. All of the data for my apps is synced and everything else is installed from Google Play. I guess that would be a bit more difficult if this were my primary phone.

The text for fussing is in tz.img, or at least it is *one location* with it. But since this is a stupid Tencent version, I can't flash anything to test, otherwise I'd have done it by now. Ah well. Sending the Tencent POS back.

OK , So the possible partitions to see deeper are abl.img and tz.img, can anyone help us with some more informations to remove this annoying message, thanks to all for your participation

Use payload_dumper and a hex editor to compare the original to yours.

Still Waiting for help to remove this message, if anyone has the solution

Question ROG Phone 5

Hello I need a hand, I installed the latest OS version for Rog Phone with the tools provided by ASUS Rog phone Since my updates it is installed very well, but I have a Bootloader message each time the phone is started (see photo) I would like to STOP it but I can't! If you have a simple tutorial I would be happy or a helping hand, thank you all

As long as your bootloader is unlocked like the message indicates you'll get that. You can lock it again if it really bothers you or just leave it as is (recommended to leave it alone, especially if your device is not a true Global).

Thank you I know that this is possible to lock the "Lock Bootlocker" there are tutorials but very badly explain, it bothers me if I want to resell it.
Asus are not great on the Update part, because it explains nothing, no simple tutorial, I had only downloaded the software.APK to unlock Bootloader and since the updates are made it always tells me the Bootloader message and I really want to delete it.
Thanks if you have any other info.

Andrologic said:
As long as your bootloader is unlocked like the message indicates you'll get that. You can lock it again if it really bothers you or just leave it as is (recommended to leave it alone, especially if your device is not a true Global).
Click to expand...
Click to collapse
I would like to lock it but I don't know the principle !

PARISSMART said:
I would like to lock it but I don't know the principle !
Click to expand...
Click to collapse
Is your device original WW/Global version? If it is/was originally a Tencent/CH version, take careful note of other users here reporting that you can only unlock it once, meaning if you re-lock it, there is no going back if you one day want to unlock it. Quite important.
If you're all good with above and at own risk, the steps are fairly simple:
1) Backup all your stuff
2) Boot the device into bootloader (Volume UP + Power until you're on the bootloader menu)
3) Connect your device to a PC with a data capable USB cable
4) Execute the command >> fastboot oem asus-lock << (requires that you have Fastboot access and drivers installed of course: Link )
5) Reboot the device. Your bootloader should now be locked.
If it bootloops or you get a red "device is corrupted bla bla.." message, do a factory reset from Recovery or RAW flash a rom. Recommend you make sure you're fully on top of recovering this device from bootloop/soft brick before attempting this, just in case.
If your only concern is about selling the device, I'd suggest keeping it as is and only re-lock it if you decide to sell it. Your warranty is gone anyway since you've used the ASUS Unlock tool once..

Andrologic said:
Is your device original WW/Global version? If it is/was originally a Tencent/CH version, take careful note of other users here reporting that you can only unlock it once, meaning if you re-lock it, there is no going back if you one day want to unlock it. Quite important.
If you're all good with above and at own risk, the steps are fairly simple:
1) Backup all your stuff
2) Boot the device into bootloader (Volume UP + Power until you're on the bootloader menu)
3) Connect your device to a PC with a data capable USB cable
4) Execute the command >> fastboot oem asus-lock << (requires that you have Fastboot access and drivers installed of course: Link )
5) Reboot the device. Your bootloader should now be locked.
If it bootloops or you get a red "device is corrupted bla bla.." message, do a factory reset from Recovery or RAW flash a rom. Recommend you make sure you're fully on top of recovering this device from bootloop/soft brick before attempting this, just in case.
If your only concern is about selling the device, I'd suggest keeping it as is and only re-lock it if you decide to sell it. Your warranty is gone anyway since you've used the ASUS Unlock tool once..
Click to expand...
Click to collapse
Thank you, I will try this and *I will let you know the situation and the *tests
Thank you very much for the explanations, it's nice

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