Database Info

Bootloader Unlock Guide

DISCLAIMER: I'm not responsible for anything that happens to your device. Use the steps below at your own risk . Be mindful of the facts unlocking bootloader voids your warranty and also hard resets your device - ALL YOUR DATA, SETTINGS, FILES AND APPS WILL BE DELETED. These steps worked for me - I own Chinese version of 8.4" LTE model. I do not know if they will work for any other models of M5, including European versions, WiFi only version and 10" models.
To execute the steps below you will need to obtain unlock code, specific to bootloader of your device. There is a slow, painful and free way to get it, and there is a quick and easy way to get the code instantly, which will cost you 4 euros. The slow way is to create Huawei ID, register on Huawei website and request the unlock code directly from Huawei, through dedicated link they provide. I do not use this method, so I don't have the link - do not ask. You will have to provide justification why you need it, such as being a developer and you bought the device to develop and make a living off of it - something Huawei support would find reasonable. In most cases they will not agree to unlock bootloader if you just tell them you want to install some roms. In this guide I will be describing the other method to get it done, which costs 4 euros.
Follow these steps.
1. Go to DC Unlocker website, register for an account (or login, if you already have one)
2. Buy 4 credits (cost is 4 euro) using the Buy link
3. Download the latest DC Unlocker client (pictures 1,2 below)
4. Open the DC Unlocker client, click "server" tab on the right (picture 1) , enter your website login you created in step 1 and click "Check Login"
5. Select "Huawei phones" from "Select manufacturer" dropdown
6. On your M5, go to Dialer app, and type in *#*#2846579#*#* to open Project Menu
7. Click Background Settings->USB Port Settings->Manufacture Mode
8. Connect your M5 to PC via USB cable and return to DC Unlocker client
9. Click the Search button to detect your device. It should be detected as "Huawei HiSilicon Kirin Android" (picture 1)
10. Click "Unlocking" tab
11. Click "Read Bootloader Code"(picture 2). It may not work on the first try, but don't worry - unsuccessful bootloader code reads do not spend your credits. Give it a few seconds, disconnect/reconnect USB cable and try again
12. Copy and save generated bootloader code
13. Download Huawei Multi Tool from the bottom of this page and install it
14. Boot into download mode by powering off your M5, then holding Vol Down + Power keys simultaneously for a few seconds and then plugging in USB cable while still holding these 2 keys
15. Open Multi Tool v8 and paste the code you got from DC Unlocker into "Get Unlock Key" input field
16 Click "Use your key" button next to it (picture 3)
17. On the bottom right click the green "Unlock bootloader" button
18. You will get a bunch of warnings on your M5 screen about unlocking bootloader - press Vol Up key and then Power key
19. At this point your bootloader will be unlocked and M5 will factory reset itself
Note: using Multi Tool is optional. Instead, if you have ADB tools with fastboot installed on your PC, then after step 14 you can just use fastboot to unlock your bootloader, by typing "fastboot oem unlock <code>"
Note 2: I don't do tech support via PM, so don't PM me for help or with questions. Use the thread instead, and some other XDA members or myself will probably help you. Good luck!
Now I'm hoping some dev takes a shine to our phablet, and compiles TWRP build for it. It can certainly be installed now that we managed to unlock the bootloader

To enter Project Mode on Wifi only tablets, open calculator and enter () () 2,846,579 () (). On 10.8" tablet, it will need to be in landscape mode to get all the calculator symbols to show.

Am I right that warranty is still intact, as Huawei does not know what we are doing?
as long as we relock it when we are done ?

Apo11on said:
2. Buy 4 credits (cost is 4 euro) using the Buy link
Click to expand...
Click to collapse
Why do we have to pay for it? I bet there's an easy way to unlock it without to pay, isn't it?
This Page describe an unlock process for huawei devices that's likely the prozess for Google or Motorola devices.
Isn't it working on the M5, too?

Marcopoloy13 said:
Why do we have to pay for it? I bet there's an easy way to unlock it without to pay, isn't it?
This Page describe an unlock process for huawei devices that's likely the prozess for Google or Motorola devices.
Isn't it working on the M5, too?
Click to expand...
Click to collapse
I think an answer for using the "unofficial" way would be that officially having an unlocked bootloader may void your warranty and I do not know how nice Huawei plays with that, so that the "official" way is not the best option to many people ...
If the device is halfway bricked, however, and you cannot restore the locked bootloader, they still know and are not too friendly either, because one did not use the proper method ...

kev1807 said:
I think an answer for using the "unofficial" way would be that officially having an unlocked bootloader may void your warranty and I do not know how nice Huawei plays with that, so that the "official" way is not the best option to many people ...
If the device is halfway bricked, however, and you cannot restore the locked bootloader, they still know and are not too friendly either, because one did not use the proper method ...
Click to expand...
Click to collapse
Your assumptions are incorrect. Warranty is voided no matter whichever way you use to unlock. The correct answer to Marcopoloy13' post is that (1) he doesn't "have to" do anything, and (2) the site he linked, simply echoes what I already said in the OP - that you can contact Huawei to request the unlock code.

Was just guessing

Apo11on said:
Your assumptions are incorrect. Warranty is voided no matter whichever way you use to unlock. The correct answer to Marcopoloy13' post is that (1) he doesn't "have to" do anything, and (2) the site he linked, simply echoes what I already said in the OP - that you can contact Huawei to request the unlock code.
Click to expand...
Click to collapse
I requested the unlock code via email. They were quick in replying but none of the codes they sent worked. They sent me 4 different codes and one was even my tablets serial number! Gave up asking in the end and will just use dc unlocker.

If you have been successful unlocking your M5 bootloader using the steps provided - please share your experience here, including any kind of problems you've encountered and how did you solve them. This will help others.

Worked for me with no issues. Quick and easy.

magnumlove said:
Worked for me with no issues. Quick and easy.
Click to expand...
Click to collapse
Which Model do you use? And congrats for unlocking.

florian-m19 said:
Which Model do you use? And congrats for unlocking.
Click to expand...
Click to collapse
CMR-W09 (10.8" wifi)

after you successful unlock youre device, is it possible to root it without twrp ?

florian-m19 said:
after you successful unlock youre device, is it possible to root it without twrp ?
Click to expand...
Click to collapse
You could have a look at this thread from the Huawei Mate 9 forum and give it a try but with relevant Mediapad M5 firmware! https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878

magnumlove said:
You could have a look at this thread from the Huawei Mate 9 forum and give it a try but with relevant Mediapad M5 firmware! https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878
Click to expand...
Click to collapse
Is there a way back if it does not work?

I also have the CMR-w09 how ever DC can not find the device i have it fully installed on my windows 10 maybe it is because of HI(hiwai sync)?
---------- Post added at 03:58 PM ---------- Previous post was at 03:53 PM ----------
Marcopoloy13 said:
Why do we have to pay for it? I bet there's an easy way to unlock it without to pay, isn't it?
[new user can not post url"]This Page[/XXX] describe an unlock process for huawei devices that's likely the prozess for Google or Motorola devices.
Isn't it working on the M5, too?
Click to expand...
Click to collapse
I tried this but the link does not open to register for unlock? also i am based in Uk and there is no option to give a UK number
---------- Post added at 04:19 PM ---------- Previous post was at 03:58 PM ----------
m5mediapad said:
I also have the CMR-w09 how ever DC can not find the device i have it fully installed on my windows 10 maybe it is because of HI(hiwai sync)?
---------- Post added at 03:58 PM ---------- Previous post was at 03:53 PM ----------
I tried this but the link does not open to register for unlock? also i am based in Uk and there is no option to give a UK number
Click to expand...
Click to collapse
I am trying yo get debian9 with xfce fully installed on this tablet with NO andriod system running such as linux deploy or VNC....

Am I the only one who couldn't get these instructions to work?
I can't get the device to install cleanly on either or my two Windows PCs. Perhaps I need drivers?
Perhaps as a result, DC Unlocker won't find my phone via automatic detection.
I might be able to get a code elsewhere - but I also can't get this thing to boot into Download mode.
Am I supposed to enable anything in Developer Options?
When I hook up to my PC, I get asked whether I want to charge only or xfer files or photos. Does it matter what I select?
Manufacture mode tends to revert back to Hisuite mode after I disconnect the USB cable.
Thanks...
(ETA - I figured out DL mode - the instructions say "power keyS" not "power key" - my bad)
(ETA - I got my key from DC. Got the following error message from Multi-Tool - 'Error! Unable to execute command, check the status of Bootloader and FRP (Phone Finder).' I'll figure this out.)
(ETA - turns out you have to enable OEM unlocking, who'd a thunk it. For the record, I'm not that Android illiterate, this is simply the first device I have bought in years, the first device I've bought within days of first root, and I'm used to everything being spelled out. Big thanks to the OP nonetheless!)

thref23 said:
Am I the only one who couldn't get these instructions to work?
I can't get the device to install cleanly on either or my two Windows PCs. Perhaps I need drivers?
Perhaps as a result, DC Unlocker won't find my phone via automatic detection.
I might be able to get a code elsewhere - but I also can't get this thing to boot into Download mode.
Am I supposed to enable anything in Developer Options?
When I hook up to my PC, I get asked whether I want to charge only or xfer files or photos. Does it matter what I select?
Manufacture mode tends to revert back to Hisuite mode after I disconnect the USB cable.
Thanks...
(ETA - I figured out DL mode - the instructions say "power keyS" not "power key" - my bad)
(ETA - I got my key from DC. Got the following error message from Multi-Tool - 'Error! Unable to execute command, check the status of Bootloader and FRP (Phone Finder).' I'll figure this out.)
(ETA - turns out you have to enable OEM unlocking, who'd a thunk it. For the record, I'm not that Android illiterate, this is simply the first device I have bought in years, the first device I've bought within days of first root, and I'm used to everything being spelled out. Big thanks to the OP nonetheless!)
Click to expand...
Click to collapse
How'd you fix the device not being detected? I've tried everything to get drivers installed, but none of them work. I'm stuck at finding the phone via automatic detection.

PewPewK said:
How'd you fix the device not being detected? I've tried everything to get drivers installed, but none of them work. I'm stuck at finding the phone via automatic detection.
Click to expand...
Click to collapse
I'm not 100% sure, but three things:
Make sure to enable USB debugging via Developer Options.
Make sure you are still in Manufacturer mode, and have not been reverted back to Hisuite mode, before hooking it up to your PC .
I installed and opened Multi-Tool before I successfully generated a code; I forget if I did anything in particular, but it prompted me to download a Huawei_Drivers zip file that I might or might not have needed.

thref23 said:
I'm not 100% sure, but three things:
Make sure to enable USB debugging via Developer Options.
Make sure you are still in Manufacturer mode, and have not been reverted back to Hisuite mode, before hooking it up to your PC .
I installed and opened Multi-Tool before I successfully generated a code; I forget if I did anything in particular, but it prompted me to download a Huawei_Drivers zip file that I might or might not have needed.
Click to expand...
Click to collapse
I managed to fix it, but I'm also not clear on what I did that caused it to work for others who might be running into the problem.
The last thing I did before it worked was install and update the latest HiSuite from Huawei's website. Otherwise I also was trying to install the Huawei drivers from Multi-Tool. Either one of those is likely the culprit for it finally working.

Anyone know of a working root?

Just got a Nokia 3.1 to use a testing tool and other fun stuff, and therefore would like to root it. Does anyone of you know of a working root of the 3.1?

So this phone is a no go for root and custom roms I guess.

kaslopis said:
So this phone is a no go for root and custom roms I guess.
Click to expand...
Click to collapse
Why do you think so? Bootloader can be unlocked via Developer settings, and I think there is no special magic preventing this device from rooting.
I would try rooting it by flashing some SuperSU zips or something like that, but I didn't try it yet

Has anyone checked this out? I haven't purchased a Nokia 3.1 but am considering it. I went so far as to create a Nokia account and there is a bootloader unlock apk, as well as an unlock.key that can be downloaded, and there are clear instructions on the Nokia page itself.. Since I don't have the phone, I did not attempt to proceed. However, if the 3.1 qualifies (I don't see why it wouldn't) then getting root should be as easy as following Magisk instructions.
There is even a page for the open source releases.
If I were to get the 3.1, my main objective would likely be to just obtain root. Looks like it should be doable.
Edit - well over 100 views since I posted this but no one has tried to unlock and/or root. I thought that was the purpose of this thread.

Unfortunately that app always crashes

VidarPT said:
Unfortunately that app always crashes
Click to expand...
Click to collapse
That is unfortunate! Perhaps, does activating Developer Options allow to select OEM Unlocking and USB Debuging, then running the Unlocking App? To run step 5 of 5 (see NOKIA INSTRUCTIONS below) you would need to have USB Debugging enabled anyway. Nowhere in the instructions is that mentioned.
FYI - Activate Developer Options: Go to Settings>About Phone and tap Build Number 7 times. Back out to access Developer Options.
Also, I do not have this phone but am interested in it. I cannot confirm if any of the advice I am giving will work, but it is what I would try.
NOKIA INSTRUCTIONS
Introduction
Firstly, we need to validate that the phone you would like to unlock is operated by you. There are a few steps to this, so we ask that you carefully follow all instructions. Let’s get started.
To participate, simply complete the following steps:
1. Please download the Nokia Bootloader Unlocker app. You can download the apk from this link and install the apk on your device. If you don’t understand how to install an apk on your device, please do not unlock the bootloader on your device. Doing so will void your phone's warranty and may cause irreparable damage.
2. Launch the Nokia Bootloader Unlocker app and fill your email information and click “Submit”.
3. The app will display a code. Please enter this in the form below along with your email address. Then press "Request to Unlock"
Your bootloader can now be unlocked. Follow the instructions below:
Step 1/5
Check the email you entered during registration. You should receive an email with a message as follows:
Hi, Thanks for requesting the unlocking bootloader. Please download your unlock key from the following link. xxxxxxxxxxxxxxxxxxxxxxxxxx
Download the unlock key and save it as “unlock.key”.
Step 2/5
Power off your device. Once powered off, press and hold the Volume Down button.
Step 3/5
While keeping the Volume Down button pressed, connect the device to the computer via USB cable. The device will boot into “Download mode”. If you have difficulty, try powering up normally, power off the device again and start back from Step 1.
Step 4/5
Download the following fastboot binary for your OS here.
Step 5/5
Open a command prompt:
Windows: Start > cmd
Mac: Applications > Utilities > Terminal.app
Linux: Terminal
Navigate to the directory where the previously downloaded unlock.key file is saved. Then enter the following commands:
fastboot flash unlock unlock.key
fastboot oem unlock
If successful, you should see the below message:
Unlock success!
Then reboot the device by entering the following command:
fastboot reboot
You are done!

It doesn't work either way. I tried with both those options enabled and disabled but the program always crashes. It's interesting to note that the app itself fails to install through chrome or "Files" app. Gives an error saying "Can't open app". I only managed to install it through ES File Explorer. Could it be because of I bought the phone on a Vodafone store? I can't find the original stock rom to flash, sadly.

VidarPT said:
It doesn't work either way. I tried with both those options enabled and disabled but the program always crashes. It's interesting to note that the app itself fails to install through chrome or "Files" app. Gives an error saying "Can't open app". I only managed to install it through ES File Explorer. Could it be because of I bought the phone on a Vodafone store? I can't find the original stock rom to flash, sadly.
Click to expand...
Click to collapse
I have been researching this and have found that, as of this writing, only the Nokia 8 qualifies for bootloader unlocking. See here. The only thing holding me back from jumping on this Nokia 3.1 is the inability to unlock the bootloader (and maybe the lack of fingerprint sensor.) Hopefully it gets "approved soon".

Currently the oem unlock using the Nokia bootloader unlock only works for Nokia 8

is there a way to root the 3.1 yet successfully? im a noob at this stuff and don't want to screw my phone.

snarfydog said:
is there a way to root the 3.1 yet successfully? im a noob at this stuff and don't want to screw my phone.
Click to expand...
Click to collapse
No, not until Nokia decides to allow users to unlock bootloader.

What about the 3.1 plus. I've already unlocked OEM. I just started looking, thought I'd start here first.

XSHADOW3 said:
What about the 3.1 plus. I've already unlocked OEM. I just started looking, thought I'd start here first.
Click to expand...
Click to collapse
It doesn't matter if you have enabled "OEM unlocking" option in Developer settings, currently Nokia doesn't allow unlocking of bootloader and thus rooting device, unless you are Nokia 8 user. You can try this, but it will crash almost for sure.

As far as I can tell, my bootloader is unlocked. I am a noob of course, but I have been researching this topic for a couple of months now. I could be mistaken in thinking "upload" mode is it, but I can't seem to figure out the difference. Otherwise, I don't know what to do next.

Nightseer said:
As far as I can tell, my bootloader is unlocked. I am a noob of course, but I have been researching this topic for a couple of months now. I could be mistaken in thinking "upload" mode is it, but I can't seem to figure out the difference. Otherwise, I don't know what to do next.
Click to expand...
Click to collapse
Can you please tell what did you do exactly?

MilesSeventh said:
Can you please tell what did you do exactly?
Click to expand...
Click to collapse
To get to "Upload" mode? Assuming it's the same for the 3.1 Plus-maybe I should have specified that-holding power button and volume up during startup will open "Upload" mode.
You can also use adb with the command "reboot bootloader." For that reason, I think it's the bootloader, but I could be wrong.
Sorry if I was a bit misleading and it is totally different on the Nokia 3.1, I was just some kinda hopeful to actually see people talk about it.

Let's get her done
Nightseer said:
To get to "Upload" mode? Assuming it's the same for the 3.1 Plus-maybe I should have specified that-holding power button and volume up during startup will open "Upload" mode.
You can also use adb with the command "reboot bootloader." For that reason, I think it's the bootloader, but I could be wrong.
Sorry if I was a bit misleading and it is totally different on the Nokia 3.1, I was just some kinda hopeful to actually see people talk about it.
Click to expand...
Click to collapse
I'm not bringing any sizable programming skills to the table unless somebody wants to teach me real fast.
Hopefully, I bring tidings of great joy. So I got two these Nokia's and they're both locked. to the carrier, Cricket. I suspect they are at least unlawfully locked. . My understanding is you can't lock to used phone especially if it's been sold as a prepaid phone. I believe this falls under the reseller flex policy. I bought it off of eBay from a guy that sells nothing but phones and he's been extremely cagey about what he'll admit to, so I called the carrier. I literally waited an hour and a half on the phone because I am falling asleep and I was on a computer speaker phone so it kept on the time of the call. I only held that long because I had fallen asleep. Anyway since I'm not in a cricket or AT&T customer then don't plan to eitherbe they could care less about me it actually told me they didn't have any information on the phone after I gave them the IMEI number.
My guess is the fcc's not going to do much because it's a trump Administration. So I spent about 45 minutes on the phone with Nokia and well at least they're interesting I think Microsoft paid between 7 and 12 billion to acquire them I recently sold them off for like a box of jujyfruits. Anyway they're committed to customer service so I figure my predicament might give me an in there.
So those unlock codes that it was a link earlier in the post for that's just to unlock the bootloader, right? You know this is a pretty decent phone for a low-end guy I got the newer 3.1 C it's got Cricket's bootloader in bloatware on it,
takes up a ton of space.
I mean it probably won't happen but if Nokia ever goes public again - I think the acquiring companies. Their eye on the prize and they're going to kick some ass. So I'm all in on this let's get this done. If you want I can see what I can do about asking Nokia 4 whatever it's going to take just to keep me a satisfied customer since they know Cricket/ATT isn't following the Obama regs.

Oof... It would be beautiful if Nokia customer support could guide us onto rooting this phone.

its so simple to unlock oem on nokia 3.1 plus. no third app needed. after developer option on -> go to developer option setting -> there is toggle button to on/off developer option , just use that toggle to off it and on it -> press yes for on dev options -> and select oem unlock. that all

It is pretty straightforward once you have unlocked bootloader (not by Nokia). If you want, you can simply dump boot_a or boot_b with SPflash tool, patch in Magisk app, and reflash.
Otherwise you can use my TWRP (NO TOUCH, and has disabled dm-verity). Please note it's only working on build v3.180, updates not supported - as it was only needed for my project.
https://forum.xda-developers.com/no...m-kali-nethunter-nokia-3-1-android-9-t4157681

$50 to remote convert me to global??

Ok I'm at my end with this convert to global I just can't get it done without error or crashdump. I've been flashing since g1 but this is wuppin my ass. This phone (in2017) is literally unusable on anything except T-Mobile. I've tried it on mint mobile and google Fi and it's the same every time. What I'm offering is $50 to whomever can successfuly remote flash and convert my device to the global software. It's extreme I guess but I need a working device. Thanks all

No need for the money. This is what I did because it didn't work for me after A11 upgraded on TMO. Here's what I do
1. MSM back to stock (I have the 10.5.7 TMO version).
2. No wifi, no sign and no mobile data. Just skip until you get normal screen.
3. In developer options toggle on oem unlock, usb debugging ( I assume you know how to get developer options).
4. In fastboot type command fastboot flash cust-unlock unlock_code.bin (This should say okay and then okay once hit return)
5. Then type fastboot oem unlock (on your phone verify unlock)
6. When the phone boots run through set up (no wifi, no e-mail, no mobile data.
7. Developer options - usb debugging
8. Download the firmware from the global thread. (Do the one with global (i have the 10.5.10 global [ this one is the 15.O.19 global one]))
9. Put your phone in bootloader mode
10. Unzip the firware and run the fashall.bat file.
BOOMSHAKALAKA! Happy modding!

Nathan.7118391 said:
No need for the money. This is what I did because it didn't work for me after A11 upgraded on TMO. Here's what I do
1. MSM back to stock (I have the 10.5.7 TMO version).
2. No wifi, no sign and no mobile data. Just skip until you get normal screen.
3. In developer options toggle on oem unlock, usb debugging ( I assume you know how to get developer options).
4. In fastboot type command fastboot flash cust-unlock unlock_code.bin (This should say okay and then okay once hit return)
5. Then type fastboot oem unlock (on your phone verify unlock)
6. When the phone boots run through set up (no wifi, no e-mail, no mobile data.
7. Developer options - usb debugging
8. Download the firmware from the global thread. (Do the one with global (i have the 10.5.10 global [ this one is the 15.O.19 global one]))
9. Put your phone in bootloader mode
10. Unzip the firware and run the fashall.bat file.
BOOMSHAKALAKA! Happy modding!
Click to expand...
Click to collapse
Cool thanks man. I'm gonna give it a go one more time and see what happens. Also when its in bootloader mode what exactly should it show up as in device manager? Depending on the driver I've seen Kedacom or LeMobile, also Google Inc or IN2017. **** one time it showed as IN2023 not sure why. It needs to show specifically as ____?

Justin credible said:
Cool thanks man. I'm gonna give it a go one more time and see what happens. Also when its in bootloader mode what exactly should it show up as in device manager? Depending on the driver I've seen Kedacom or LeMobile, also Google Inc or IN2017. **** one time it showed as IN2023 not sure why. It needs to show specifically as ____?
Click to expand...
Click to collapse
You know what, I never checked device manager. Follow the MSM thread and then follow the upgrade to global thread and you'll be fine. Just remember to use the A10 firmware. For some reason the A11 didn't work for me. Happy modding!

Nathan.7118391 said:
You know what, I never checked device manager. Follow the MSM thread and then follow the upgrade to global thread and you'll be fine. Just remember to use the A10 firmware. For some reason the A11 didn't work for me. Happy modding!
Click to expand...
Click to collapse
Hey man i wanted to say thank you and i very much mean it. The instructions you put up top should be written again and stickied in the guides section because this is what finally got the in2017 converted. my phone actually rings when people call and i can even dial out now. thanks again bro!!!
ps. now if i can figure out how to root it ill be winning for sure!

Justin credible said:
Hey man i wanted to say thank you and i very much mean it. The instructions you put up top should be written again and stickied in the guides section because this is what finally got the in2017 converted. my phone actually rings when people call and i can even dial out now. thanks again bro!!!
ps. now if i can figure out how to root it ill be winning for sure!
Click to expand...
Click to collapse
Hey bro, diss you get it rooted yet?

Nathan.7118391 said:
Hey bro, diss you get it rooted yet?
Click to expand...
Click to collapse
I surely did and all is working and good to go. Thanks for everything!

Nathan.7118391 said:
You know what, I never checked device manager. Follow the MSM thread and then follow the upgrade to global thread and you'll be fine. Just remember to use the A10 firmware. For some reason the A11 didn't work for me. Happy modding!
Click to expand...
Click to collapse
Hi, i am using A11(11.0.4.6 IN55CB ) could you tell me how to rollback to A10 ?. cuz i know how to do the process and everything but not how to rollback.

How To Guide Rooting the SM-F711B (on Version F711BXXU2AUI4) working

First of all:
I'm no Dev...just someone who likes to play lego.
From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk.
I've read a good startup here.
Hopefully this makes this thread clear enough so that i dont need to describe the whole procedure step by step.
(https://www.naldotech.com/root-samsung-galaxy-z-flip-3-5g-magisk/)
(1.OEM-Unlock,2.BL-Unlock,3.extract boot.img,4.patch boot.img via magisk on the unrooted mobile,5.patch boot.img.tar to AP&BL via Odin, 6.pray)
Anyways...here are maybe small hints to avoid a few traps.
a) Just do the oem-unlock in the dev-options (enabled by tapping buildnumber 5 times) is just half of the rent.
Afterwards i had to go in Download-mode (switch of mobile, press volUp+volDown and connect PC-cable.)
There appears a possibility of choice.
Press VolUp short: get the mobile on standby to flash the rom via odin.
Press VolUp LOONG: get the mobile to the menu where the bootloader can finally get unlocked. (Otherwhise every try to patch a rooted img will be blocked by bootloader-protection.)
Of course this can possibly be done via adb/fastboot commands.
Funny side note: OEM-Unlock-option will completely disappear from Dev-options and waranty is lost. Also the mobile stops to get Updates OTA which means that you have to update manually whenever a new version will appear in the net.
b) patching boot.img via magisk should work as described in many other magisk-rooting-manuals.
Flashing the tar back to the mobile via odin was little bit tricky.
It doesnt reach out just to provide the magisk_patched.tar to Odin just on the AB-line.
I had to patch it to BL too.
Cheers
MikGx

When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.

@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2

MikGx said:
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
Click to expand...
Click to collapse
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.

naldotech.com, the link you provide is pretty clear about the process. What it doesnt say is what to do at the end. When you untick "reboot" in odin, and you finish flashing, your phone will stay in download mode. Then what to do?. Press power and volume down to leave and restart the phone? or, power and volume down, screen goes black imediately power and volume up, enter recovery and restart from there.? please someone ?

Press the power and volume down buttons for about 7 seconds and it will reboot

beanbean50 said:
Press the power and volume down buttons for about 7 seconds and it will reboot
Click to expand...
Click to collapse
I did as you mention but it didnt work. It made me reset the system. But I Fallowed the naldotech.com guide. At the end, being in dawnload mode, I pressed power and volume down, when the screen got black I pressed power and volumen up, I entered recovery mod, cleared cache and re- started the system: Voila my phone is rooted

Hello.
Can someone pleas provide a working link for frija download? The one referring from naldotech seems to be broken (https://www.naldotech.com/download-samsung-galaxy-stock-firmware-frija-tool/)
Update: Found a link via google -> https://technastic.com/odin-download-samsung-latest-all-versions/

twistedumbrella said:
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
Click to expand...
Click to collapse
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.

d0x360 said:
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
Click to expand...
Click to collapse
twistedumbrella said:
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
Click to expand...
Click to collapse
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.

twistedumbrella said:
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
Click to expand...
Click to collapse
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.

d0x360 said:
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
Click to expand...
Click to collapse
You got where I said "I guess the disclaimer is misleading" right?

twistedumbrella said:
You got where I said "I guess the disclaimer is misleading" right?
Click to expand...
Click to collapse
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons

d0x360 said:
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
Click to expand...
Click to collapse
Lucky? I dunno. Had I known it would cause this much trolling, I wouldn't have bothered to mention it.

I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?

david.siebauer said:
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
Click to expand...
Click to collapse
Partially. I just did that: I have AfWall running on my old phone, tried to unlock the Flip with this manual here in order to use the firewall there, did something wrong - and stumbled upon Netguard while searching what might have happened and decided to give it a try first. (Unless there is a custom ROM for the phone available, I have no other need for root or an unlocked bootloader.)
From what I could find on my Flip 3, you can unlock and relock the bootloader as you like - but as soon as you install a non-genuine bootloader (i.e. one chnaged by Magisk) you will trip Knox - and this cannot be reverted.
In such a case you can still re-lock your bootloader and unlock it later (on my phone, that "7-day-no-switch-indeveloper-options" routine kicked in, but you can circumvent that) - but Knox will stay in its state. From what I read this means some things will not work such as Samsung Pay, but I do not know the details (yet) apart from that it does not bother me ;-), and the nag screen during boot is gone.

Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now

david.siebauer said:
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
Click to expand...
Click to collapse
Well, it's better than my Sony - there it is "once unlocked, always unlocked" with no way back at all
But I have to admit I understand the logic why the manufacturers do that, at least to the degree that they trip a fuse as Samsung does.
By rooting the phone, you shift the responsibility for the software state of the phone from the manufacturer to the user, so I think it is okay to implement something to make it clear to possible future buyers that it is or has been in that state.
(This does not include however all the other stones they put in the way of people wanting to develop or use custom ROMs!)

I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features. Guess u shouldn't have bought a Samsung lol.

david.siebauer said:
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features.
Click to expand...
Click to collapse
Oh, trust me - as soon as I hear there is a custom ROM that works as a daily driver I will root mine as well. I really hope that there will be one for this phone
david.siebauer said:
Guess u shouldn't have bought a Samsung lol.
Click to expand...
Click to collapse
Sadly there is no Fairphone mini or Fairphone Flip - or would it be Fairfliphone? ... Flipfairphone?... - yet (if ever), so the only current alternative would be Motorola. And the price tag for the Razr is simply too much, even if I personally think it looks better than the Samsung. Additionally, I do not know if they are in any way better when it comes to rooting or loading custom ROMs.

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