Database Info

Verizon Bootloader Unlock

Is anyone else working on unlocking the bootloader for verizon pixels? Its clearly possible as people are doing it but but not releasing it publicly. All the other threads on this are locked because people keep trying to offer services outside of XDA. Are there theories on how its being done? Spoofing the verizon IMEI check server? Temp root and modifying a system file?

Quada said:
Is anyone else working on unlocking the bootloader for verizon pixels? Its clearly possible as people are doing it but but not releasing it publicly. All the other threads on this are locked because people keep trying to offer services outside of XDA. Are there theories on how its being done? Spoofing the verizon IMEI check server? Temp root and modifying a system file?
Click to expand...
Click to collapse
I have been poking around on google for a long time checking for Verizon bootloader unlock activity and I noticed that as well. This got me thinking, and while I haven't done a lot of digging to see if my idea if feasible here's what I got. I was thinking to leverage Spectre "https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)" somehow to leak a signature that can then be passed in an api call to unlock the bootloader. If i recall, I think I remember seeing a function in android source somewhere that took a prm specifying unlock/lock and then a signature created by the vendor to allow the unlock. if you could figure out the appropriate offsets in memory, maybe it would be possible? As said, I have not done much research on this but just figured I'd share and see what others thought.

Pixel 2 Verizon unlock bootloader instructions are here below
Unlocking the Bootloader WILL WIPE YOUR DEVICE!! so backup important files.
Install ADB/Fastboot Drivers
Enable Developer Options
Enable USB Debugging in Developer Options
Plug Pixel 2 into PC
Open a Command Prompt window;
In Command Prompt, type adb start-server
and hit ENTER
If you see * daemon started successfully *
continue to next step
In Command Prompt, type adb devices
and hit ENTER
If you see "List of devices attached" as well as "Your Devices Serial Number device or unauthorized"
continue to next step
On Pixel 2 - Allow PC for USB Debugging
In Command Prompt, type adb reboot bootloader
Once your Pixel 2 has rebooted into the bootloader
In Command Prompt, type fastboot flashing lock_critical
and hit ENTER Then follow the instructions on your Pixel 2 to finish Unlocking Bootloader.
Correct on the steps, including the entire discussion found here. https://forum.xda-developers.com/pix...el-2s-t3726294
***PATCHED BY OUT-OF-CYCLE JANUARY UPDATE***
If you have received the OTA patch for your pixel2, and now are on OPM2.171019.016, you will no longer be able to run the command. And downgrade is not available at this time.
As of 1/24/2018 users who have purchased new phones have been able to remove the SIM, refuse internet (WiFi) connection at the initial startup. After completing the initial setup, you can sideload 8.1 to take advantage of the command in the OP. If you connect to the internet with WiFi or with your SIM, chances are high you will receive the update and this method WILL NOT work. To date, there are no other ways to unlock the bootloader on VZW PIX2 other than this method. Instructions to sideload stock OTA's are found here along with the downloads. https://developers.google.com/android/ota Once again, DO NOT USE 8.1.0 (OPM2.171019.016, Jan 2018, Verizon) but instead use 8.1.0 (OPM1.171019.013, Jan 2018) The command is not available on 8.0.
There is also another alternative way which has worked for me this week on Pixel 32GGB Verizon. Its called depixel8. more info can be found @ http://theroot.ninja/depixel8.html
Usage:
Step 1) Install fastboot and adb on your PC, ensure both are working with your Pixel.
Step 2) Run "adb push dePixel8 /data/local/tmp", "adb shell chmod 755 /data/local/tmp/dePixel8" and finally run the program "adb shell /data/local/tmp/dePixel8"
(put the depixel files in the same folder as your ADB/FASTBOOT drivers are where you do your command prompt commands)
Step 3) Wait for the phone to reboot to the bootloader. If it is not rebooting you can try to run various apps until it does, or you may have to reboot and start over.
Step 4) Issue the command "fastboot oem unlock", this will open up the unlock prompt and warning on the screen. You can now unlock. If you get an error, about unlocking not being allowed, start all over again.

MpandAUS said:
Pixel 2 Verizon unlock bootloader instructions are here below
Click to expand...
Click to collapse
dePixel8 is patched in Android 7.1.1 and newer.

lock bootlooader without power button
How can i relock my bootloader without use of my power button its broken

Keetoowah said:
How can i relock my bootloader without use of my power button its broken
Click to expand...
Click to collapse
Are you rooted?

Keetoowah said:
How can i relock my bootloader without use of my power button its broken
Click to expand...
Click to collapse
I personally recommend not relocking your bootloader. If you aren't on pure stock it will give you problems and even if you are on pure stock, an unlocked bootloader is a devices most powerful recovery tool and OTAs have been known to fail on occasion and other problems you would want to recover from can occur.
As to the answer to your question, if you can boot the device normally at all then you can turn on adb debugging and from there open an adb shell and use adb reboot bootloader to get to fastboot mode and then use fastboot oem lock I believe

KittyRgnarok said:
I personally recommend not relocking your bootloader. If you aren't on pure stock it will give you problems and even if you are on pure stock, an unlocked bootloader is a devices most powerful recovery tool and OTAs have been known to fail on occasion and other problems you would want to recover from can occur.
As to the answer to your question, if you can boot the device normally at all then you can turn on adb debugging and from there open an adb shell and use adb reboot bootloader to get to fastboot mode and then use fastboot oem lock I believe
Click to expand...
Click to collapse
Thank I've decided to have the power button repaired at my own expence since I have a Verizon Pixel 2 with an unlocked bootloader. The replacement they sent me wasn't unlockable. The unlocked bootloader with TWRP and root are well worth the price of the power button.

Keetoowah said:
Thank I've decided to have the power button repaired at my own expence since I have a Verizon Pixel 2 with an unlocked bootloader. The replacement they sent me wasn't unlockable. The unlocked bootloader with TWRP and root are well worth the price of the power button.
Click to expand...
Click to collapse
How much was the replacement button and installation by the way, I'm rather curious

getting back on track, it looks like someone claims to be able to OEM unlock after getting the April OTA? Can anyone support or contradict this claim? https://www.reddit.com/r/GooglePixel/comments/89rnoa/google_pixel_verizon_oem_unlock/

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

bricked lg v50 sprint variant.

so, i was following the guide for the bootloader unlocking process and succeeded. rooting process is what bricked my phone, unfortunately.
i loaded the patched magisk image in to boot_a like it said, and hoping that everything would have went well, it did not.
now phone will not boot. recovery modeis broken. adb does not recognize my device, and i have no clue how to get to edl mode from there.
as far as im aware, there is no kdz for the lg v50 sprint variant. (v450) unfortunately.
can anyone help me?
i feel like im SOL
It's not my main phone, but I really like the cameras on it. Was just looking to rid it of lgs software.

Which abl you used to unlock?The one provides for LG G8 is untested for sprint V50,it's highly you missed something,you need get into the abl's fastboot mode to flash back the original kernel

@Vortex said:
Which abl you used to unlock?The one provides for LG G8 is untested for sprint V50,it's highly you missed something,you need get into the abl's fastboot mode to flash back the original kernel
Click to expand...
Click to collapse
It boots into fastboot as soon as it boots up. So there's hope. Adb just doesn't recognize my phone. The thread said it worked, and everyone else who had the sprint v50 said it worked. So I don't know what went wrong

I didn't use the file for the g8.

Beefybeardedbear said:
It boots into fastboot as soon as it boots up. So there's hope. Adb just doesn't recognize my phone. The thread said it worked, and everyone else who had the sprint v50 said it worked. So I don't know what went wrong
Click to expand...
Click to collapse
Where is the thread?I didn't see any talked about V50,only G8's,the adb will not recognize because it's fastboot mode,you need the fastboot.exe to do further operations,not the adb

@Vortex said:
Where is the thread?I didn't see any talked about V50,only G8's,the adb will not recognize because it's fastboot mode,you need the fastboot.exe to do further operations,not the adb
Click to expand...
Click to collapse
,
Ah, I see. I have the fastboot.exe in my platform tools folder.
The link is https://forum.xda-developers.com/t/...YteGJNSWxEZlhydFpfWm9telNEbUhFZ1pFQlJ6amZORlg.

Beefybeardedbear said:
,
Ah, I see. I have the fastboot.exe in my platform tools folder.
The link is https://forum.xda-developers.com/t/...YteGJNSWxEZlhydFpfWm9telNEbUhFZ1pFQlJ6amZORlg.
Click to expand...
Click to collapse
Good it seems using the rencently appeared lge programmer with G8X ES abl,are you get original phone from sprint ?It's unlocked someway more violent before for sprint model.Have you flashed the abl back?I suggest you follow the bootloader unlock section carefully https://bbs.lge.fun/thread-121.htm

@Vortex said:
Good it seems using the rencently appeared lge programmer with G8X ES abl,are you get original phone from sprint ?It's unlocked someway more violent before for sprint model.Have you flashed the abl back?I suggest you follow the bootloader unlock section carefully https://bbs.lge.fun/thread-121.htm
Click to expand...
Click to collapse
I haven't as I am at work, currently. I will try once I am back home. I mean, it seems as easy as just flashing stock boot_a.bin to the boot partition, right? Or am I wrong?

Beefybeardedbear said:
I haven't as I am at work, currently. I will try once I am back home. I mean, it seems as easy as just flashing stock boot_a.bin to the boot partition, right? Or am I wrong?
Click to expand...
Click to collapse
Yes,just patched the ramdisk file is not enough,you have to deal with dmverity or something else,the root aquirement on android had became much more complex than the early days because the damn google always try to block this routine,even the SuperSu had gave up fighting

@Vortex said:
Yes,just patched the ramdisk file is not enough,you have to deal with dmverity or something else,the root aquirement on android had became much more complex than the early days because the damn google always try to block this routine,even the SuperSu had gave up fighting
Click to expand...
Click to collapse
yeah, i know. back in the old days, there were even apps like king root to give you root permission. damn google acts like we cant just have freedom. they are starting to act like apple now

Beefybeardedbear said:
yeah, i know. back in the old days, there were even apps like king root to give you root permission. damn google acts like we cant just have freedom. they are starting to act like apple now
Click to expand...
Click to collapse
I sincerely suggest you buying some Chinese ODM 5G phones instead of these hell-like phones,It's all carrier unlocked and free to flash with the same Snapdragon Platform like oneplus Xiaomi.

@Vortex said:
I sincerely suggest you buying some Chinese ODM 5G phones instead of these hell-like phones,It's all carrier unlocked and free to flash with the same Snapdragon Platform like oneplus Xiaomi.
Click to expand...
Click to collapse
well xiaomi and all those other brands are banned. i have a oneplus 6t for when i want to flash and customize.

Beefybeardedbear said:
well xiaomi and all those other brands are banned. i have a oneplus 6t for when i want to flash and customize.
Click to expand...
Click to collapse
i also have oneplus 8. but bootloader is locked unless i get my phone sim unlocked. but thats after i pay off the phone

You just need to find a V50 Sprint device from another user or your friend, then backup all partitions, back them up, then flash to your device.
Note: ignore imei partitions

How would I flash it? Through fastboot and adb? I've already found one.

hello?

You flash them through fastboot by giving the following command:
fasboot [file name i.e abl_a] [file location]
Alternatively if you can go back to EDL/QFIL/9008 mode, you can load through the software

Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?

geee0h said:
Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?
Click to expand...
Click to collapse
Unfortunately, I haven't even tried. And I've given up. Going to chinese brands now. They are way easier to root and rom. Like oneplus and xiaomi. You could try the method above that a member mentioned.

geee0h said:
Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?
Click to expand...
Click to collapse
Get KDZ Tools
unzip the kdz
look for abl_a.img abl_b.img laf_a.img laf_b.img xbl_a.img xbl_b.img xbl_config_a.img xbl_config_b.img
flash it on fastboot. If you have follow the guide to unlock, you should have backed up all these files.
hope this helps.

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

Redmi 10C Doubt/help

Hello.
Recently i flashed this: ROM in my Redmi 10C, and now I can't unlock the bootloader to flash it back to the stock ROM. Its not exactly bricked, but I can't root it. Why do I need to root it? Because you can do all the fun things only if you have root of course!
My question is:
Is the Redmi 10C going to let me flash it through EDL mode with QPST/QFIL (Qualcomm emergency tools for dumdums like me)
Or am I forced to go to someone with an authorized MI account (and that person can flash it). Alternatively, can I get my MI account authorized, or at least borrow one only for this.
Thank you for reading, and good day to you.

dthslce42 said:
Hello.
Recently i flashed this: ROM in my Redmi 10C, and now I can't unlock the bootloader to flash it back to the stock ROM. Its not exactly bricked, but I can't root it. Why do I need to root it? Because you can do all the fun things only if you have root of course!
My question is:
Is the Redmi 10C going to let me flash it through EDL mode with QPST/QFIL (Qualcomm emergency tools for dumdums like me)
Or am I forced to go to someone with an authorized MI account (and that person can flash it). Alternatively, can I get my MI account authorized, or at least borrow one only for this.
Thank you for reading, and good day to you.
Click to expand...
Click to collapse
First, be absolutely sure, which model, exactly is your device, check the code name of your device, and which ROM suits for it.
Still, not clear, how did you get to flash a custom ROM, with the bootloader locked?

TThThank you f
SubwayChamp said:
First, be absolutely sure, which model, exactly is your device, check the code name of your device, and which ROM suits for it.
Still, not clear, how did you get to flash a custom ROM, with the bootloader locked?
Click to expand...
Click to collapse
Thank you for answering. I apologize, the bootloader isn't locked. It's just that I cannot check the OEM unlock option (it's greyed out, on the system i installed).
First. I rooted my redmi 10c (still had the stock/default ROM)
Then. I proceeded to flash it (with twrp) with the ROM I quoted before. Although I suspect it didn't completed installation, because it doesn't have some features that all ROMs have (thank god it still has networking & basic telephony functions). And now i cannot root it, because i can't check 'OEM unlock' option.
I researched thoroughly and the only way I see fit (at the moment) is to use the EDL mode and the official 'MI Flash Pro tool'.
BUT according to various sources, the Redmi 10c falls in the category of models that need an Authorized MI Account (log into the official tool) to properly flash a system through EDL mode.
I want to restore it to the stock/default ROM. But to do that through EDL i need an authorized account.
My doubt is simple: do I really need the 'MI Flash Tool Pro' ? Or can I just enter EDL mode, use QPST/QFIL (also an official tool) and do it without the need to log in? (authorized).
Thank you for keeping up!

dthslce42 said:
TThThank you f
Thank you for answering. I apologize, the bootloader isn't locked. It's just that I cannot check the OEM unlock option (it's greyed out, on the system i installed).
First. I rooted my redmi 10c (still had the stock/default ROM)
Then. I proceeded to flash it (with twrp) with the ROM I quoted before. Although I suspect it didn't completed installation, because it doesn't have some features that all ROMs have (thank god it still has networking & basic telephony functions). And now i cannot root it, because i can't check 'OEM unlock' option.
I researched thoroughly and the only way I see fit (at the moment) is to use the EDL mode and the official 'MI Flash Pro tool'.
BUT according to various sources, the Redmi 10c falls in the category of models that need an Authorized MI Account (log into the official tool) to properly flash a system through EDL mode.
I want to restore it to the stock/default ROM. But to do that through EDL i need an authorized account.
My doubt is simple: do I really need the 'MI Flash Tool Pro' ? Or can I just enter EDL mode, use QPST/QFIL (also an official tool) and do it without the need to log in? (authorized).
Thank you for keeping up!
Click to expand...
Click to collapse
There are some confusing concepts here.
Firstly, a locked device doesn´t admit custom images, OK, I must assume you know that, next, if you didn´t expressly re-locked it, then it remains unlocked, the toggle unlock OEM grayed out, is not a problem, always that it is checked, it means your device is still unlocked.
Anyway, if the doubt persists, can you provide some screenshots.

SubwayChamp said:
There are some confusing concepts here.
Firstly, a locked device doesn´t admit custom images, OK, I must assume you know that, next, if you didn´t expressly re-locked it, then it remains unlocked, the toggle unlock OEM grayed out, is not a problem, always that it is checked, it means your device is still unlocked.
Anyway, if the doubt persists, can you provide some screenshots.
Click to expand...
Click to collapse
Mmm, i assumed the the device was still unlocked because it should persist (after you flash it any number of times you want). That, and when I restart it it shows an 'unlocked' padlock icon.
I'm going to post some screenshots.

Pic 2: the 'OEM unlock' should appear with the other debugging (Depuración) options, it doesn't.
Pic 1: it only appears when I search for it, when i tap on it it doesn't do anything.
(Sorry for the Spanish)

dthslce42 said:
Pic 2: the 'OEM unlock' should appear with the other debugging (Depuración) options, it doesn't.
Pic 1: it only appears when I search for it, when i tap on it it doesn't do anything.
(Sorry for the Spanish)
Click to expand...
Click to collapse
I guess you want to referring to OEM unlock toggle, that it´s not present. Again, that the toggle is not present, doesn´t mean, your bootloader is locked, most probably, the ROM you´re actually on is not showing, and nothing more, strange, but as it is.
So, you can do what you want, as the bootloader is unlocked.
You can be absolutely sure, by sending device to fastboot mode and doing fastboot oem device-info

SubwayChamp said:
I guess you want to referring to OEM unlock toggle, that it´s not present. Again, that the toggle is not present, doesn´t mean, your bootloader is locked, most probably, the ROM you´re actually on is not showing, and nothing more, strange, but as it is.
So, you can do what you want, as the bootloader is unlocked.
You can be absolutely sure, by sending device to fastboot mode and doing fastboot oem device-info
Click to expand...
Click to collapse
Mmmmm. I forgot to clarify... It doesn't even let me transfer files trough USB. So fastboot mode is locked(?). You could say that the phone is kinda bricked. Since I have 0 clues on how to change the ROM.
But back to the core of this thread.
Is it advisable to use any of the tools: QPST/QFIL(Qualcomm), in EDL mode to change the ROM.
I ask here because i hope someone knows if using the Qualcomm tools is gonna work.
Since xiaomi tools ABSOLUTELY require an authorized account to complete the process (and not hardbrick the phone pls).

dthslce42 said:
Mmmmm. I forgot to clarify... It doesn't even let me transfer files trough USB. So fastboot mode is locked(?). You could say that the phone is kinda bricked. Since I have 0 clues on how to change the ROM.
But back to the core of this thread.
Is it advisable to use any of the tools: QPST/QFIL(Qualcomm), in EDL mode to change the ROM.
I ask here because i hope someone knows if using the Qualcomm tools is gonna work.
Since xiaomi tools ABSOLUTELY require an authorized account to complete the process (and not hardbrick the phone pls).
Click to expand...
Click to collapse
Man, please, put all the attention, to both, to me, and to your words. I don´t understand at all, why you say you´re bricked or something, or you say, you don´t know how to put another ROM onto your device when you already flashed in the past a custom ROM, Why you should use Qfil/QPST or other of those unbricking tool, if...
Your device has the bootloader UNLOCKED and you DON´T need to put the Xiaomi ROM into your device, an authorized account is needed when you need to flash the OFFICIAL ROM, not for any other custom ROM, in your case, you can flash any other custom ROM as you already did it in the past.
Better tell me:
1-Can your device be power on?
2-Can your device enter to TWRP, and/or fastboot mode?
3-What exactly do you want to achieve right now?

"1-Can your device be power on?"
Yes.
"2-Can your device enter to TWRP, and/or fastboot mode?"
It can enter fastboot mode. But not TWRP, it was erased. I didn't realize until it was too late.
"3-What exactly do you want to achieve right now?"
Either change to other ROM. Or reinstall the current one. But I don't know how.

dthslce42 said:
"1-Can your device be power on?"
Yes.
"2-Can your device enter to TWRP, and/or fastboot mode?"
It can enter fastboot mode. But not TWRP, it was erased. I didn't realize until it was too late.
"3-What exactly do you want to achieve right now?"
Either change to other ROM. Or reinstall the current one. But I don't know how.
Click to expand...
Click to collapse
Ok, if you have a fastboot mode working fine, then you just have to reinstall the recovery available for your device, as you did it once, then, rebooting to it, just flash the ROM available for your device. Jut repeat that process.

SubwayChamp said:
Ok, if you have a fastboot mode working fine, then you just have to reinstall the recovery available for your device, as you did it once, then, rebooting to it, just flash the ROM available for your device. Jut repeat that process.
Click to expand...
Click to collapse
I'm really grateful mate. What you told me about the EDL mode (that i can install any ROM with the Qualcomm tool, as long as it's not the official from Xiaomi) was really helpful. Thank you!
The phone can enter fastboot mode, but it's not recognized by any PC. (That's why I say the 'OEM unlock' option it's the most likely culprit) so -i think- it cannot be done that way.
All drivers were installed (automatically, the unlock tool has an option to scan and install the correct drivers, and manually)

dthslce42 said:
I'm really grateful mate. What you told me about the EDL mode (that i can install any ROM with the Qualcomm tool, as long as it's not the official from Xiaomi) was really helpful. Thank you!
The phone can enter fastboot mode, but it's not recognized by any PC. (That's why I say the 'OEM unlock' option it's the most likely culprit) so -i think- it cannot be done that way.
All drivers were installed (automatically, the unlock tool has an option to scan and install the correct drivers, and manually)
Click to expand...
Click to collapse
OK, from what I understood, you want to follow the guidelines provided, I mean, flash the TWRP again using fastboot, then boot to it, and from there can flash any custom ROM...
If I´m right, and this is correct, you are feeling that you´re stuck in fastboot mode but the device is not recognized as of now...
Unlock tool and also the Xiaomi Unlock tool or even the Xiaomi (Pro) tool, has the correct fastboot drivers for any Xiaomi device, BUT, the issue is "simply" that you have to "call" that specific drivers and "match" it to your device, the right drivers are already there, from within a long list of all of the device (compatible or not) drivers...
I mean, you just have to connect your device in fastboot mode, you have to see, either the Xiaomi bunny (in older devices) or the fastboot legend into your screen, then just update the drivers...
Keep the device manager windows opened in a part of your PC, and check the changes when you connect your device, then you have to see, some driver that appeared, and update it from the list following something like the images I´ll upload, the guide I made is to update EDL drivers, but apply the part you need, in order to get Android Bootloader Interface, note that your device has not to be listed under Port COM like in EDL.
When you uncheck this option, then you can find it from the list.