Related
Hey All,
I've seen some posts stating that the bootloader for this phone can't be unlocked.
I'm using the E6533 model and wanted to confirm that it is possible.
Just go to this website: http://developer.sonymobile.com/unlockbootloader/ (the official sony one)
Select Xperia Z3 as the model (I know we have the Z4/Z3+ but it still works). Enter your email and click the link they email you.
Insert the IMEI number and they will give you the unlock code. then just run
adb reboot bootloader
fastboot oem unlock <code>
and it will work.
As a note this WILL wipe your device, so backup anything you may need on it.
Hopefully with this we can get root / twrp built
So TA backup is needed to keep the DRM keys before unlocking the bootloader. Is there a way to back up TA of non-rooted devices? Flashtool doesn't fully support Z3+ yet.
help
Quick question , what to do if you have Unlock allowed: No?
Generally speaking this always meant just what it says... That it's not possible to unlock the bootloader. This was often the case with oem phones. Today it could also mean you have myxperia security activated. If you have log out of that and try again.
Oh and do not activate it after unlocking bootloader, you could brick your device for good!
3lastic said:
Quick question , what to do if you have Unlock allowed: No?
Click to expand...
Click to collapse
Make sure you don't have the xperia security software enabled (the find my iPhone equivalent)
It prevents the bootloader from being unlocked. Otherwise it means your carrier disabled the feature
Thanks diemadedrei and ChrisJ951.
It worked, it was the Xperia Security software that was enabled.
Rooting status: unknown
Hello, i tried to unlock my BL from the sony website, but after i flashed the code in my phone, it just restored and now just says rooting status: unknown and also the option of unlock allowed does not even appear! anybody could please help me?
thanks and hello from Mexico!
The z3+ is now selectable on the unlock page officially
@bryantronics: it should say bootloader unlocked yes under rooting status. Generally it should have worked if everything went as described.
diemadedrei said:
The z3+ is now selectable on the unlock page officially
@bryantronics: it should say bootloader unlocked yes under rooting status. Generally it should have worked if everything went as described.
Click to expand...
Click to collapse
hello! thanks for the reply, the bootloader said yes... but that line doesnt appear! it just says rooting status unknown, i tried to upload the screenshot but i dont know how to do it
3lastic said:
Thanks diemadedrei and ChrisJ951.
It worked, it was the Xperia Security software that was enabled.
Click to expand...
Click to collapse
Thanks to all, I have tried to change it to "YES" 24 hours
OK so with this recent tidbit of data that a bootloader unlock no could become a yes I am concerned. When I bought the phone it said yes. But no where can I figure out if the DRM keys are a)original b)intact c) working with this present rom. Could anyone tell me so I can be sure that if I resell this item I don't misrepresent this information.
haist i have a same problem for that issue ...until now i can not flash boot img...please resolve this problem...guys plssssss......
i have the same problem i cant flash img due to remoted lock state: unlocked
any updates?
I am suffering the same problems as my colleagues in the previous posts. I cannot get the bootloader unlock, no matter how hard I try:
performed the official Sony way (using minimal adb and fastboot; phone is listed in fastboot devices; "remote: command not allowed")
flashtool64: both with blu manually and by leaving the text file in the registered devices folder (which was found and used for a unlock, which turned out not to be successful).
Sony MyDevices is not activated. Android 5.0.2 (E6533; 28 0 A 8 272 HK)
Do you have any further tips how to open the bootloader?
thx, Benedikt
ChrisJ951 said:
Hey All,
I've seen some posts stating that the bootloader for this phone can't be unlocked.
I'm using the E6533 model and wanted to confirm that it is possible.
Just go to this website: http://developer.sonymobile.com/unlockbootloader/ (the official sony one)
Select Xperia Z3 as the model (I know we have the Z4/Z3+ but it still works). Enter your email and click the link they email you.
Insert the IMEI number and they will give you the unlock code. then just run
adb reboot bootloader
fastboot oem unlock <code>
and it will work.
As a note this WILL wipe your device, so backup anything you may need on it.
Hopefully with this we can get root / twrp built
Click to expand...
Click to collapse
Thanks for the tip but how I can back up TA Partition? Can you help me about that? And I am using latest Nougat Single Variant E6553, your tip will work with nougat?
I tried this Sony method but showing remote cammand not allow please help
---------- Post added at 05:50 PM ---------- Previous post was at 05:40 PM ----------
I trying same methods but showing remote command not allowed
hi
How long does it take to unlock ? the bootloader. I've waited for long.
Unlock bootloader NO
Any solution
i was crashing my head to do it and nothing to it done, and I discovered that the problem was that my xperia was enabled, so I disabled it and finally unlocked the bootloader
I had bootloader unlock allowed: no on latest firmware. I backed to Android 6 a I have bootloader unlock allowed: yes
Hi,
I have a nexus 6P and one day after a lovel OTA my phone had died on me. Sad enough I decided that I had to put her to bed and go get a dr. pepper from the fridge. Months later, as my feelings withered, I wished to resurrect my nexus.
SO here is what I know. I cannot flahs the stock rom with the bootloader locked. Guess what guys, my bootloader is locked. No flashing, its all locked up, but I kjnow no company is dumb enough to not have a plan B for when you don't wear protection.
Question 1: I heard I have to use TWRP to flah a custom rom to then unlock the bootloader but this seems silly as stock firmware should be far more flashable. ANy explanation?
Question 2> What is the difference between the K and D firmwares?
williamschromebook said:
Hi,
I have a nexus 6P and one day after a lovel OTA my phone had died on me. Sad enough I decided that I had to put her to bed and go get a dr. pepper from the fridge. Months later, as my feelings withered, I wished to resurrect my nexus.
SO here is what I know. I cannot flahs the stock rom with the bootloader locked. Guess what guys, my bootloader is locked. No flashing, its all locked up, but I kjnow no company is dumb enough to not have a plan B for when you don't wear protection.
Question 1: I heard I have to use TWRP to flah a custom rom to then unlock the bootloader but this seems silly as stock firmware should be far more flashable. ANy explanation?
Question 2> What is the difference between the K and D firmwares?
Click to expand...
Click to collapse
To flash twrp you need an unlocked bootloader. If you enabled USB debugging in developer options before the issue then you should be able to do fastboot oem unlock. However if not try going into your stock recovery and adb sideload a stock OTA for the nexus 6p and it should write all the partitions and boot up fine. I'm not sure what K and d firmwares are.
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
Also, when you plug your device into your pc what does it say in device manager? Does it say something like EDL?
Boot loader locked....
I don't think I can glad twrp
williamschromebook said:
Boot loader locked....
I don't think I can glad twrp
Click to expand...
Click to collapse
That doesn't answer my question.
I won't know until my friend brings a device over again later
Some people are just better off not unlocking their bootloader.
DEVILOPS 007 said:
To flash twrp you need an unlocked bootloader. If you enabled USB debugging in developer options before the issue then you should be able to do fastboot oem unlock. However if not try going into your stock recovery and adb sideload a stock OTA for the nexus 6p and it should write all the partitions and boot up fine. I'm not sure what K and d firmwares are.
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
Also, when you plug your device into your pc what does it say in device manager? Does it say something like EDL?
Click to expand...
Click to collapse
I believe the new unlock code is "fastboot flashing unlock" - oem was for older phones. Also, he'd need have checked Allow OEM Unlock or OEM Unlocking or whatever it says in development settings to unlock bootloader, USB debugging for your next step, which could hopefully work.
williamschromebook said:
Boot loader locked....
I don't think I can glad twrp
Click to expand...
Click to collapse
Correct, you need an unlocked bootloader to flash TWRP. I'd try 007s advice above if you had USB Debugging enabled. Try to sideload a newer OTA via stock recovery and maybe a factory reset for good measure. See if it can at least get you booted.
lucky_strike33 said:
Some people are just better off not unlocking their bootloader.
Click to expand...
Click to collapse
Rude. OP said his phone had a locked bootloader (so, stock) and it died during an OTA. He came here asking for help..
I'd like to start a discussion on unlocking the XA2 bootloader and rooting it. So far, it looks like for Sony devices, you need to send a request through the Sony site here: https://developer.sonymobile.com/unlockbootloader/
But there is no device selection for the XA2. This is where i'm currently stuck at. Does anyone know of any other way to unlock the bootloader?
Okay got it to unlock bootloader.
Steps:
1. Head to https://developer.sonymobile.com/unlockbootloader/. Select Xperia XA1 in the dropdown, follow steps, then get your access code.
2. Pretty much follow the steps in that guide from sony, where you get the access code. The only difference was when installing the fastboot drivers. On win 10, i had to go and follow the steps here to install android drivers: https://android.stackexchange.com/questions/129174/windows-10-fastboot-driver
After that, fastboot was able to recognize the device and unlock the bootloader.
So now, i guess i'm waiting for TWRP to be released for XA2 to get recovery and root.
I've been looking for a XA2 page for a while. Can we request one?
This is a interesting device and I hope the development community shows some interest too.
What's your impressions of it so far?
Agreed, I'm quite shocked there is no development threads as of yet for this newly released device. Already checked mine, and can see that sky mobile have left it unlockable, so I would also be interested in development for this device.
Spitfire400 said:
Agreed, I'm quite shocked there is no development threads as of yet for this newly released device. Already checked mine, and can see that sky mobile have left it unlockable, so I would also be interested in development for this device.
Click to expand...
Click to collapse
Same. I bought it off Amazon US and I didn't realize I was buying such a recent phone. To any future devs, add "Night Light" feature and swipe fingerprint to bring down notification bar to any ROMS would make this phone a great sucessor to my Honor 8.
XA2 has been perfect for me so far, coming from Nexus 5x. I mostly use my phone for reddit and podcasts, though. Just need my LineageOS on it.
i unlocked mine also
li0nh3art3d said:
i unlocked mine also
Click to expand...
Click to collapse
Hello, what about fingerprint scanner usability after unlocking? I've heard that after rooting your phone scanner may stop to work with banking and other similar apps. Maybe you noticed other changes after rooting?
Merlin K said:
Hello, what about fingerprint scanner usability after unlocking? I've heard that after rooting your phone scanner may stop to work with banking and other similar apps. Maybe you noticed other changes after rooting?
Click to expand...
Click to collapse
I haven't been able to root yet. I've only unlocked the bootloader, which hasn't caused any problems with bank of America. on my other phone rooting didn't affect bank of America, however Android pay didn't work, and snapchat can only be logged in before root and not after. once you root, you won't be able to log back in snapchat if you logout, however if you log in it'll stay logged in after root.
I've been having problems with the windows 10 fastboot and ADB drivers. i got fastboot to work long enough to unlock the bootloader but then it stopped recognizing my phone. still haven't gotten ADB to work yet ?*
li0nh3art3d said:
I haven't been able to root yet. I've only unlocked the bootloader, which hasn't caused any problems with bank of America. on my other phone rooting didn't affect bank of America, however Android pay didn't work, and snapchat can only be logged in before root and not after. once you root, you won't be able to log back in snapchat if you logout, however if you log in it'll stay logged in after root.
I've been having problems with the windows 10 fastboot and ADB drivers. i got fastboot to work long enough to unlock the bootloader but then it stopped recognizing my phone. still haven't gotten ADB to work yet ?*
Click to expand...
Click to collapse
Thx for info. Let us please know when when/if root your phone.
Merlin K said:
Thx for info. Let us please know when when/if root your phone.
Click to expand...
Click to collapse
I'm waiting for TWRP to keep playing with the drivers on windows 10. for some reason they've been giving me a major headache
The wait game begins. I'm going to wait to unlock the bootloader until TWRP and root available.
Btw can't you root without changing the recovery using ADB. I don't kno since this my first ever Sony phone.
YaKillaCJ said:
The wait game begins. I'm going to wait to unlock the bootloader until TWRP and root available.
Btw can't you root without changing the recovery using ADB. I don't kno since this my first ever Sony phone.
Click to expand...
Click to collapse
I think you can sideload with ADB once the bootloader is unlocked. I was under the impression TWRP is like a GUI for ADB. but There's something funky with the windows 10 drivers. it took forever for my phone to get detected in fastboot, and ADB never seemed to work. then, after i unlocked my phone, the PC doesn't even recognize it in fastboot anymore.
likewise, I've always used Samsung phones & odin. This is my first Sony. the lack of root is killing me ?
From what i read, adb sideload requires custom recovery.
Is anyone else on Project FI with this phone? I'm getting awful 4G and wifi performance with the XA2. Constantly losing internet access (even though signal bar is at 5 bars).
Hi guys, I managed to unlock the bootloader but I can not get into recovery mode. I tried with vol- and power button but it does not work . Did it happen to someone? Thank you all
makotech222 said:
From what i read, adb sideload requires custom recovery.
Click to expand...
Click to collapse
where did you read this? i was under the impression thst TWRP is basically a graphic user interface of ADB, which is command line interface.
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
matitino said:
Hi guys, I managed to unlock the bootloader but I can not get into recovery mode. I tried with vol- and power button but it does not work . Did it happen to someone? Thank you all
Click to expand...
Click to collapse
for this, you will need a custom recovery GUI such as TWRP. I believe tht all you can do on this device by pressing volume- is access ADB, and volume+ gets you into fastboot, which can be accessed via command prompt on a PC
li0nh3art3d said:
where did you read this? i was under the impression thst TWRP is basically a graphic user interface of ADB, which is command line interface.
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
for this, you will need a custom recovery GUI such as TWRP. I believe tht all you can do on this device by pressing volume- is access ADB, and volume+ gets you into fastboot, which can be accessed via command prompt on a PC
Click to expand...
Click to collapse
ADB sideload explicitly, not just ADB: https://twrp.me/faq/ADBSideload.html
makotech222 said:
ADB sideload explicitly, not just ADB: https://twrp.me/faq/ADBSideload.html
Click to expand...
Click to collapse
Isn't TWRP basically just the GUI of all the ADB commands? I was under the impression you could do almost everything you can do in TWRP in ADB CLI mode on a PC ?*
I was under the impression to sideload you can boot with a USB plugged into your computer and your phone press volume- Then the indicator light in the top right corner turns green, and (if the drivers on my PC would cooperate) then it would accept ADB sideload commands. Now, I am unsure of this; that's just what my basic understanding is. If I could get the damn drivers to work right, I could find out for sure ?
li0nh3art3d said:
Isn't TWRP basically just the GUI of all the ADB commands? I was under the impression you could do almost everything you can do in TWRP in ADB CLI mode on a PC ?*
I was under the impression to sideload you can boot with a USB plugged into your computer and your phone press volume- Then the indicator light in the top right corner turns green, and (if the drivers on my PC would cooperate) then it would accept ADB sideload commands. Now, I am unsure of this; that's just what my basic understanding is. If I could get the damn drivers to work right, I could find out for sure
Click to expand...
Click to collapse
I don't know nearly enough about the android ecosystem to comment, beyond what i found. I think adb sideload is a specific command, which requires twrp. But other adb may work? I don't want to risk it yet anyways.
Regarding drivers, did you try the thing i linked in my first post on this thread? My XA2 is still recognized after bootloader unlock with my method.
What do you know flashtool supports our xa2? that I know no because I tried to convert an ftf file but in the device list the xa2 is not there. also does not recognize me in flashmode despite emma recognize it. thank you
[Guide] How to root the Pixel 3a with or without twrp & take OTA updates once rooted
THIS IS A DRAMA FREE THREAD, I'M NOT GOING TO BASH OTHERS THREADS, NOR AM I GOING TO GO AROUND TO THOSE THREADS AND BASH THEM IN IT BECAUSE I SOMEHOW FEEL SUPERIOR TO THEM.
Standard you do this at your own risk and I'm not responsible for anything warning.
There are a few ways you can go about rooting. You can either use twrp, manually patch the stock boot image and flash it, or just flash a pre-patched boot image. I'll be going over all three, but keep in mind i have depreciated the pre-patched method now that we have twrp. twrp is dead on 10
Do these first if you haven't already:
Update your fastboot and adb
I just toss these 4 highlighted files into the windows folder, but you may have a different set up(I put them in the windows folder so I don't have to add them to PATH.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Googles USB driver if you need it
right click the start menu icon, click device manager, then locate your phone(should have a yellow symbol on it, right click it, then click update driver, then click browse my computer, click the browse button and then navigate to where you extracted the drivers, click the main folder(usb_driver) and then click ok, then click next and ok through any prompts.
CMD = Command Prompt
Unlocking your bootloader:
This wipes your phone
Run through the initial setup if you haven't already, if you haven't don't bother logging into your google account.
Enable dev options(settings>about phone>build number>tap it 7 times).
Go into settings>system>advanced>dev options>oem unlocking, click the toggle.
While still in dev options scroll down a little and enable usb debugging.
Plug your phone into your pc.
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Open up command prompt(powershell works to but i always use command prompt) type into the cmd window
Code:
adb reboot bootloader
The phone will reboot into fastboot mode.
Now type into the cmd window
Code:
fastboot devices
See if it lists a device, if not you need to install the drivers I linked to. If you had to install the drivers try the fastboot devices command again after installing them, it should list the device now.
type in
Code:
fastboot flashing unlock
You will then have to use the phone to select yes to the unlock. you use the volume keys to select and the power button to confirm.
Your bootloader is now unlocked and you follow one of the below root methods.
Onto the root methods:
these are for stock phones, not ones using a custom kernel
IF ON Q YOU MUST USE MAGISK 19.4+
Grab your boot.img from here
it's inside the zip that is inside the folder in the main zip you download
patching and flashing the stock boot.img:
This is the only way to root on android 10+ as twrp doesnt work
Reboot your phone.
Run through the initial setup again, this time you can log into your google account and set the phone up how you want. Re-enable dev options, enable adb, and turn off auto updates.
Grab the stock boot.img for your matching build(from the link above).
Put the boot.img on your phone, location doesn't really matter, as long as you know where you put it.
Download and install Magisk Manager.
Open up magisk manager and click install, then select the "Select and Patch a File" option, let it do its thing.
Move the patched image from your phone to your pc(magisk stores the patched image in your downloads folder).
Open up a cmd window and type in
Code:
adb reboot bootloader
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Once you are in the bootloader(fastboot) type in
Code:
fastboot getvar current-slot
This will tell you the currently active slot of your phone, remember it.
Now to flash your patched boot.img.
- If the cmd window location does not match the location of the boot.img you will have to enter that too.
- If you're on windows 10(this only works on English as far as i know) you can use my Tools Menu it will give you some handy options in your right click context menu. It makes things a lot easier as you can just right click in the location of the boot.img and open a cmd window there.
- If your cmd window is opened in the same location as the boot image you can just do(don't include the ")
Code:
fastboot flash boot_"slot "whatever the boot.img is named"
- If your cmd window was not opened in the same location as the boot image you will need to do one of these.
Code:
cd C:\Users\pbanj\Desktop\android
the cd command changes the current directory to where you tell it. then you can just do
Code:
fastboot flash boot_"slot" "whatever the boot.img is named"
- Or you can type out the location to the boot.img or just drag the boot.img file onto the cmd window. example:
Code:
fastboot flash boot_"slot" C:\Users\pbanj\Desktop\boot.img
Once that's done flashing just type in
Code:
fastboot reboot
MAKE SURE YOU GO INTO DEV OPTIONS AND TURN OFF AUTO UPDATES.
You should use the twrp method over this next one. I'll no longer be adding updated pre-patched boot images as they're completely pointless now that we have twrp.
Do NOT use this method, it's here just for history sake
Method 3 booting a prepatched boot.img and direct installing Magisk:
This gets you rooted a bit faster. thanks to @Uzephi for reminding me about this.
Grab the boot.img that matches your build number in about phone. These were made using the newest canary build of magisk at the time of adding them to the post. If I update them I'll mark them as updated. I used the canary builds for these as it's what I personally use
- PD2A.190115.029
- PD2A.190115.032 Updated to newest canary build as of May-28-2019
- PQ3B.190605.006 This is the June update Updated to the 19.4-c1602d25(19301) canary build
- PQ3B.190705.003 this is the July update
Save it somewhere and rename it if you want.
If not already in fastboot mode open up a command prompt window and type in
Code:
adb reboot bootloader
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Once you are in the bootloader(fastboot) type in
Code:
fastboot boot "whatever the boot.img is named".img
- If the cmd window location does not match the location of the boot.img you will have to enter that too.
- If you're on windows 10(this only works on English as far as i know) you can use my Tools Menu it will give you some handy options in your right click context menu. It makes things a lot easier as you can just right click in the location of the boot.img and open a cmd window there.
- If your cmd window is opened in the same location as the boot img you can just do(don't include the ")
Code:
fastboot boot "whatever the boot.img is named".img
- If your cmd window was not opened in the same location as the boot image you will need to do one of these.
Code:
cd C:\Users\pbanj\Desktop\android
the cd command changes the current directory to where you tell it. then you can just do
Code:
fastboot boot "whatever the boot.img is named".img
- Or you can type out the location to the boot.img or just drag the boot.img file onto the cmd window. example:
Code:
fastboot boot C:\Users\pbanj\Desktop\android\boot.img
Once booted run through the initial setup again(if you haven't already after unlocking the bootloader), this time you can log into your google account and set the phone up how you want.
MAKE SURE YOU GO INTO DEV OPTIONS AND TURN OFF AUTO UPDATES.
After you've run through the initial setup(if you had to) open up Magisk Manager(it will most likely say the manager needs to be installed as it is currently only a stub) and then click on the top install option, then click install in the popup that comes up, then click the direct install option.
After it finishes click reboot and you're good to go
UPDATING
There are a couple methods of updating.
Uninstall the edge sense plus mod before you update or you won't be able to root again/you'll end up in a bootloop and will have to enter safemode to disable it.
WHEN UPDATING TO ANDROID 11 DISABLE ALL MAGISK MODS AND REBOOT ONCE BEFORE UPDATING.
If you're using any custom kernel you'll have to flash the stock boot.img first before updating for the sideload method. The magisk method it might not matter but I'm not 100% sure on that. I'd think it'd be fine if you had magisk backup the stock image before you flashed the custom kernel, I don't use one so I cant be 100% sure though.
magisk has removed the ota method for pixel devices so these are the ways to update now.
My personal favorite way to update is to use the full system image as it's fastest. Disable any custom themes or modules that are known to cause bootloops when updating. Then:
grab the system image from here, unzip the folder and inside of it you will find another zip. open that up and pull the boot.img out.
Use magisk manager on your phone to patch that and then take the patched image and rename it to boot.img and put it back in the zip you pulled the stock one from.
Open the "flash-all.bat or .sh if on linux" and remove the -w from the end(this is important as it stops your device from being wiped) save the bat file.
put your phone into fastboot mode and run the flash-all script. should take about 5 min and then your phone will reboot and you are good to go.
I made a telegram group where I'll be posting the system images ready to flash. I typically make them within a few days of the update coming out. https://t.me/joinchat/EC3ivRhc2-t4y1J4REtuqg
Alternative Update method
Grab the OTA update from here.
Reboot the phone into recovery, you can just use
Code:
adb reboot recovery
Once in recovery press power and up and you should see the options.
Go down to apply update from adb(use the volume keys to change options and the power button to select).
Open a cmd window if you haven't already and type in
Code:
adb sideload "ota update file"
Location matters just like it did during the initial flashing, if you didn't open the cmd window in the same location as the update file andyou don't remember what to do, just take a look at one of the root methods as they tell you how to go about fixing that. Or just type in "adb sideload" and then drag the update file onto the cmd window.
After the ota is done select the "reboot to bootloader option".
Once in the bootloader(fastboot) just flash the pre-patched boot.img like you did before. remember the slot changes with each update so make sure you get the current slot, or if you remember what slot it was using before the update just switch input the other one. so if it was on slot a you would flash the patched image to b and vise versa.
BOOT IMAGES:
This is a google drive folder, it will have both stock and patched images. I also provide the newest Magisk manager These are zip files, you must unzip them to use them.
- https://drive.google.com/drive/folders/1wH7pvsHYznbDJ_vTsb_dWBNJBDcx2wHx?usp=sharing
Pass Safetynet
Open Magisk & go into its settings
Scroll down to the "Magisk" category and turn "Zygisk (beta)" on, & "Enforce DenyList" on.
Tap on "Configure DenyList"
Then tap the 3 dot menu and check "show system apps"
Add "google play services", google play store", "google pay", and any of your banking apps or apps that ***** about root.
Reboot
Install Universal Safetynet Fix and reboot
Install Yasnac from the Play Store
Open Yasnac and tap "run SafetyNet attestation" you should get pass on both basic and CTS.
How to use Netflix
Grab the newest apk from here.
Install the apk.
Add the apk to your Magisk DenyList.
if you need help you can ask here in the thread or in the Telegram group
pbanj said:
So I figured I would make a single thread out of the posts I've made. I made prepatched boot.img files to save everyone time.
I assume everyone here knows you need an unlocked bootloader and how to flash them.
Standard you do this at your own risk and I'm not responsible for anything warning.
Update your fastboot and adb
Googles USB driver if you need it
Grab the boot.img that matches your build number in about phone. These were made using the newest canary build of magisk at the time of this thread.
pd2a.190115.029
pd2a.190115.032
Save them somewhere and rename it if you want. then flash
To get google pay to work you may have to do some tinkering(I had to). To get it working go into magisk hide, enable show system apps then make google play services, the play store and pay look like this
Now comes the fun part.
- Plug your phone into your pc
- Grab your root app of choice that allows you to freeze apps
- Freeze google play services this will make your phone pissed and you will get a bunch of notifications, ignore them for now
- Open your favorite command line utility and do
Code:
adb shell
then
Code:
su
grant it root on your phone.
- Then while still in adb shell enter
Code:
rm -rf /data/data/com.google.android.gms
- Go into settings, then apps
- Clear the data of pay, and the play store
- Click disable on the playstore and then yes to restoring the factory version, reenable it
- Reboot your phone. It will ***** about lack of play services again, still ignore it.
- Reenable google play services
- Wait a min so it can do its thing
- Now you can add your cards to pay.
Click to expand...
Click to collapse
Dang, mine worked after I hid Google pay with magisk! That's an intensive process. I clicked hide them rebooted and added my amex without issue. Had to **** system apps to hide play store so I could download Netflix too.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:57 PM ----------
jmtjr278 said:
Dang, mine worked after I hid Google pay with magisk! That's an intensive process. I clicked hide them rebooted and added my amex without issue. Had to click system apps to hide play store so I could download Netflix too.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
Almost forgot to mention, thanks for the patched image. Saved me some time
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
Dang, mine worked after I hid Google pay with magisk! That's an intensive process. I clicked hide them rebooted and added my amex without issue. Had to **** system apps to hide play store so I could download Netflix too.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:57 PM ----------
Almost forgot to mention, thanks for the patched image. Saved me some time
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
Ya I had them hid and it wouldn't let me add my cards. so I went oh it must have triggered before I hid them. So I did the old "clear all their data" trick and it still wouldn't let me do it. I was talking in my discord server and was told about how the play services remembers. They told me to do all the stuff I posted and then run that command from twrp. Well we dont have twrp yet so I was like **** am I screwed until then. then another one was like if you freeze the play services and then try the command it might work. So I did and it worked. wasted about an hour of my time lol.
pbanj said:
Ya I had them hid and it wouldn't let me add my cards. so I went oh it must have triggered before I hid them. So I did the old "clear all their data" trick and it still wouldn't let me do it. I was talking in my discord server and was told about how the play services remembers. They told me to do all the stuff I posted and then run that command from twrp. Well we dont have twrp yet so I was like **** am I screwed until then. then another one was like if you freeze the play services and then try the command it might work. So I did and it worked. wasted about an hour of my time lol.
Click to expand...
Click to collapse
The things we do to have fun! That's what I love though, seeing a problem and figuring out the solution. Android is the best. Teaches me things every day
Sent from my Pixel 3a using Tapatalk
Does this work with US carrier Pixel 3a's? (TMobile, Version, AT&T, etc.)
lovelockdown said:
Does this work with US carrier Pixel 3a's? (TMobile, Version, AT&T, etc.)
Click to expand...
Click to collapse
If they will allow you to unlock the bootloader yes. Otherwise no
pbanj said:
If they will allow you to unlock the bootloader yes. Otherwise no
Click to expand...
Click to collapse
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far
razrlover said:
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far
Click to expand...
Click to collapse
man that sucks. i would just return it and buy it from google. or hell even bestbuy will give you an unlocked one and let you add it to your tmobile account.
pbanj said:
man that sucks. i would just return it and buy it from google. or hell even bestbuy will give you an unlocked one and let you add it to your tmobile account.
Click to expand...
Click to collapse
Yeah i had already downloaded your boot.imgs. thanks for doing that for everyone.
I've been on a S9 for a while so I'm used to finding work arounds for no root. I will try to make it work for a while and see.
razrlover said:
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far
Click to expand...
Click to collapse
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
That's awesome!
A work around indeed! Appreciate it
havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
I will give it a try right now and report back. Thanks.
havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
still grayed out for me after factory reset with no sim
ill try it with a new phone as well
edit: also grayed out on my fresh out of the box phone as well
both from tmobile
havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
Did you actually unlock the bootloader?
Thanks
I thought that oem unlock was greyed until you inserted a sim and connected to a network. Seems like this is the way it's always been on pixels.
gtuansdiamm said:
still grayed out for me after factory reset with no sim
ill try it with a new phone as well
edit: also grayed out on my fresh out of the box phone as well
both from tmobile
Click to expand...
Click to collapse
Did you connect to wifi? It was still grelayed out for me until I connected to wifi. Then went back one menu, and returned to developer options and it wasn't grayed out anymore
---------- Post added at 03:40 PM ---------- Previous post was at 03:39 PM ----------
alphahere said:
Did you actually unlock the bootloader?
Thanks
Click to expand...
Click to collapse
Yes, I did. You need to connect to wifi first before it will allow you to enable OEM unlock.
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
Chronzy said:
I thought that oem unlock was greyed until you inserted a sim and connected to a network. Seems like this is the way it's always been on pixels.
Click to expand...
Click to collapse
Yes, it's grayed out until you connect to a network, but that network doesn't have to come from a SIM card (at least not in my case) it can come from wifi
Didn't work for me, factory reset for nothing. Now time to reinstall everything. ugh.
razrlover said:
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far
Click to expand...
Click to collapse
When the device is paid off and unlocked (permanently, not a travel unlock) through the Unlock app, the OEM unlock option will no longer be grayed out. I can confirm it first hand and I'll add that this is how foreign carriers operate as well with regards to the Pixel.
The way that OEM unlocking works on *all* Pixels is through IMEI whitelisting. Factory Unlocked Pixels sold through Best Buy, Google Fi, Google Store and a few other retailers are whitelisted as being eligible for OEM unlocking. The option will be grayed out until the phone is connected to the internet so as to receive the eligibility state from Google.
Devices branded for T-Mobile are marked as ineligible, but T-Mobile (like virtually all carriers that sell the Pixel except for Verizon and NTT Docomo) updates the OEM Unlock eligibility flag at the same time they deem the device SIM unlock eligible. The device will check in with Google, receive the new eligibility state and unrestrict the OEM Unlock option.
The final bit of weirdness with the T-Mobile variant is how T-Mobile uses the Device Unlock app. Google has a custom SIM unlock solution for carriers that does not involve a carrier app or traditional unlock codes. It is similar to what the iPhone does & how OEM Unlock eligibility works - the carrier sends a request to Google for a phone associated with said carrier to be unlocked. Google processes the request, the phone checks in with Google and displays a notification stating that the SIM unlock was complete. For non Verizon/NTT Docomo carriers, that notification also means that you can now OEM Unlock.
T-Mobile doesn't use that functionality, for whatever reason, if there is even a reason. Maybe on account of Google not supporting temporary unlocks.
T-Mobile has long tied bootloader unlock eligibility to SIM unlock eligibility. You can buy a Moto whatever from T-Mobile, get denied a bootloader unlock code from Motorola's website, pay the device off and, boom, Moto changes their tune. The same is true with the OnePlus 6T and all current T-Mobile devices that have a sanctioned bootloader unlock mechanism.
Beware: My T-Mobile Pixel 3a Came With a SIM Card =(
My new-in-box T-Mobile Pixel 3a had a SIM card installed already. I booted it up, connected to wifi, and now I can't root it. =( Factory reset did not help.
darkmeridian said:
My new-in-box T-Mobile Pixel 3a had a SIM card installed already. I booted it up, connected to wifi, and now I can't root it. =( Factory reset did not help.
Click to expand...
Click to collapse
See above comment for a great explanation of why you can't unlock your TMobile carrier device.
Sent from my Pixel 3a using Tapatalk
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
Have you tried unlocking the bootloader threw the developers settings thee option to unlock the bootloader is the 3rd or 4th option down, personally not tried it tho?
---------- Post added at 11:19 PM ---------- Previous post was at 11:12 PM ----------
Ash180287 said:
Have you tried unlocking the bootloader threw the developers settings thee option to unlock the bootloader is the 3rd or 4th option down, personally not tried it tho?
Click to expand...
Click to collapse
Am sure your aware but if you don't know how to get to the developers menu, open settings, click system at the bottom, go to about phone, and then click your build number 7 times to unlock the developers options.
Ash180287 said:
Have you tried unlocking the bootloader threw the developers settings thee option to unlock the bootloader is the 3rd or 4th option down, personally not tried it tho?
---------- Post added at 11:19 PM ---------- Previous post was at 11:12 PM ----------
Am sure your aware but if you don't know how to get to the developers menu, open settings, click system at the bottom, go to about phone, and then click your build number 7 times to unlock the developers options.
Click to expand...
Click to collapse
I didnt try anything until there is a guide of how to do it tested previously to avoid a possible brick.
RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
Thanks for this, i would try this if i could unlock the bootloader, but i neither know how to do it.
RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
unlocking the bootloader is simple, it works exactly with the black shark helo, you enable the unlock in the developer section and then I have it in fastboot mode and you send the command "fastboot oem unlock" the smartphone will restart and make a factory reset and you will have the bootloader unlocked
Sime90ita said:
unlocking the bootloader is simple, it works exactly with the black shark helo, you enable the unlock in the developer section and then I have it in fastboot mode and you send the command "fastboot oem unlock" the smartphone will restart and make a factory reset and you will have the bootloader unlocked
Click to expand...
Click to collapse
I tried today doing everything you say, but fastboot say command doesnt exist, maybe you have chinese version(I am using global version)
RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
Enable developer function and enable OEM unlock function
pichitpongx said:
Enable developer function and enable OEM unlock function
Click to expand...
Click to collapse
Did it worked for you?
I tried that and didn't work. I have global version
Anyone managed to unlock the boot loader on this phone? I would like to get one but need root.
adkilla said:
Anyone managed to unlock the boot loader on this phone? I would like to get one but need root.
Click to expand...
Click to collapse
Ditto. Waiting on confirmation of root.
r3flux said:
Ditto. Waiting on confirmation of root.
Click to expand...
Click to collapse
I'm also waiting for root confirmation, i have BS 2 Global and unlocking boot loader tutorial was posted by a skilled member, here is the link
https://forum.xda-developers.com/bl...ck-bootloader-problem-easy-t3895992?nocache=1
---------- Post added at 11:18 PM ---------- Previous post was at 11:04 PM ----------
Also here is a full guide to unlock Black Shark 2 and seems to be effective
Steps To Unlock Bootloader On Xiaomi Black Shark 2
1.) First Of We Need To Enable Developer Options
For That Go To Settings >> About Phone >> Now Tap On MIUI Version 6-7 Times
2.) Now Go Back >> Go To Advanced Settings >> Developer Options >> Enable OEM Unlocking & Tap On Mi Unlock Status
These Things You Have To Do It On Your PC/ Laptop
3.) Go To This Link >> Then You Will See MIUI Page Tap On Unlock Now >> Now Fill The Form To Get The Permission From Xiaomi
4.) Once You Applied you will get an OTP sent to your phone, Enter that OTP on your PC >> Then Hit Next. So, this way your application gets submitted
Now You Have To Wait Until You Get A Message On Your Phone Saying “You Are Eligible To Unlock The Bootloader”
Now Follow The Unlocking Procedure
6.) Once You Got The Message >> Next You Need To Download Mi Unlock Tool & Extract It
7.) After That Just Power Off The Device,>> Now Press & Hold Volume Down + Power Button At The Same Time To Boot Into Fastboot Mode
8.) Once Your Are In Fastboot Mode >> Connect Your Phone To PC/Laptop
9.) Now Open (Mi Unlock Tool) From Your PC/Laptop
10.) Next Click On Agree & Next Enter Your Mi-Account Username, Password And Sign In
Use Same Mi Account Details Which You Already Login Into Your Phone To Unlock Bootloader
11.) Hit Next >> After That Tap On Unlock
12.) Once The Process Is Done Tap On Reboot
13.) That’s It ? You Have Successfully Unlock Bootloader Of Xiaomi Black Shark 2
For tutorial link, you can PM me, i can't post it publicly to avoid any moderator ban
Update : **
No any solution above has worked with me, seems there is no active solution for unlocking boot loader of BS2. even developer around all sites doesn't offer effective solution.
The only 2 messages that you will get when you use adb are :
adb>fastboot flashing unlock
Error : Unlock is not allowed on device has sales on market!
adb>fastboot oem unlock
Error, Unknown command
Even MI tool couldn't unlock the bootloader, If Kanded can give a solution as he is a skilled member so it will be great help
Any update? Still waiting for the XBS2 unlocking bootloader and rooting it.
I have found this about patching MM:
https://www.htcmania.com/showthread.php?t=1466079
I Hope enjoy, I have the same problem, BS2 global to root,
Anyone who tried unlocking bootloader and rooting bs2 using the bs helo? CN variant
has anybody got solution? I think this device has a potential to fullfill
So sad. Until now there's no TWRP and way to unlock bootloader of this device.
iampatricktan said:
So sad. Until now there's no TWRP and way to unlock bootloader of this device.
Click to expand...
Click to collapse
Agree. I'm planning to switch to Red Magic 3 because there really is no sign of development on this device.
batuken said:
Agree. I'm planning to switch to Red Magic 3 because there really is no sign of development on this device.
Click to expand...
Click to collapse
Yeah. I don't how can we encourage dev to look into this device, their are many users of this phone that wants to have twrp and root. Also this device is very powerful.
iampatricktan said:
Yeah. I don't how can we encourage dev to look into this device, their are many users of this phone that wants to have twrp and root. Also this device is very powerful.
Click to expand...
Click to collapse
Black Shark is independent of Xiaomi when it comes to the software development. Their team just have to release the kernel source then that's when the real thing starts. Sadly though, the Black Shark team is very lousy and their support is very poor so let's just expect that this device will get stuck to Android Pie, like what happened to Black Shark 1 which development is "dead".