**Your Bootloader MUST be unlocked**
**does not work on Android Q**
1) Download Magisk APK from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and install the APK
2) download your system image from https://developers.google.com/android/images Make sure you check settings-->about phone to get your current software version to your PC
3) extract the boot.img and copy it to your Pixel
4) open Magisk and select install then write to a file. Select boot.img
5) wait for it to finish then copy the patched boot image back to your PC
6) open a powershell window from the folder you copied the patched boot image to and either ADB reboot bootloader or turn off your phone and hold the volume down and power key until your in fastboot mode, plug it in and run "fastboot getvar current-slot"
7) take note which boot letter pops up either A or B
8) run "fastboot flash boot_<Letter> <patched_image_name>.img
9)"fastboot reboot"
PROFIT
This also appears to break Google Pay even though Magisk Hide is enabled. If anyone has a work around please share!
Link to the newest Google USB drivers:
https://developer.android.com/studio/run/win-usb
Nice post. As I posted in another thread. I would test the patched image with the following command.
"fastboot boot <patch_image_name>.img"
If it works then flash it permanently.
In case anyone wants to put the old style nav bar on their new phone this still works
How to disable Android Pie gestures on the Google Pixel 3
1. Install any 3rd-party launcher of your choice. This is a must because otherwise, you won’t have a launcher app left once we’re done with this tutorial!
2. Set up ADB on your PC. Here’s a tutorial we previously wrote that you should you through the process.
3. Connect your Pixel 3 to your PC and open up a command prompt/terminal in the directory where you downloaded the ADB binary. Enter the following command depending on your OS:
Windows Command Prompt
adb shell
Windows Power Shell
.\adb shell
macOS/Linux Terminal
./adb shell
4. Now, enter the following command to uninstall the Pixel Launcher from the current user.
pm uninstall -k --user 0 com.google.android.apps.nexuslauncher
5. Now, enter this command to re-enable the stock navigation bar after reboot. This is the setting you’ll be changing by issuing the below command.
settings put secure system_navigation_keys_enabled 1
6. Reboot your Pixel 3.
7. Once you’re booted back up, you should see the original 3 button navigation bar layout and the original vertical stacked card recent apps overview.
Does not work for me on my Pixel 3a XL with Android Q Beta 3.
All the steps appear to succeed but when the phone is rebooted and Magisk Manager run it says "Magisk is not installed."
I also notice that the Magisk patched boot.img is _much_ smaller than the original. 31 MB vs. 64 MB. Doesn't seem to have kept the phone from booting though so I don't know if this is normal.
Code:
[[email protected] bonito-qpp3.190404.015]$ fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.022s
[[email protected] bonito-qpp3.190404.015]$ fastboot flash boot_b magisk_patched.img
Sending 'boot_b' (30756 KB) OKAY [ 1.160s]
Writing 'boot_b' OKAY [ 0.496s]
Finished. Total time: 1.734s
[[email protected] bonito-qpp3.190404.015]$ fastboot reboot
Rebooting
Finished. Total time: 0.068s
[[email protected] bonito-qpp3.190404.015]$ ls -lh boot.img boot_magisk_patched.img
-rw-r--r-- 1 carl users 64M Jan 1 2009 boot.img
-rw-r--r-- 1 root root 31M May 10 10:48 magisk_patched.img
clipcarl said:
Does not work for me on my Pixel 3a XL with Android Q Beta 3.
All the steps appear to succeed but when the phone is rebooted and Magisk Manager run it says "Magisk is not installed."
I also notice that the Magisk patched boot.img is _much_ smaller than the original. 31 MB vs. 64 MB. Doesn't seem to have kept the phone from booting though so I don't know if this is normal.
Click to expand...
Click to collapse
Doesn't work on Q Beta 3
Anyone here about the progress on the Q magisk? Haven't wandered over to pixel land in a while; seems like I recall him saying he was onto something last time I did.
Last I heard Magisk works for the Pixel 1 and 2 running Android Q but due to different software on the Pixel 3 it still isnt working but the dev has said he is working on it. I am sure with time he will get it fixed since he has a Pixel 3.
krabman said:
Anyone here about the progress on the Q magisk? Haven't wandered over to pixel land in a while; seems like I recall him saying he was onto something last time I did.
Click to expand...
Click to collapse
Worked fine after downgrading my 3aXL to Pie.
Thanks for the instructions!
Worked great. As stated, Google Pay didn't work, but Chase and Mario Run worked (which they didn't on my last rooted device). Thanks!
It's totally wrong but I flash both A and B and call it a day. Makes it easier to remember the commands. As a point of interest for those on Fi using the eSim remember to go through the setup using it again after you unlock or you're going to get a toast asking you to connect to Fi every ten minutes. I had assumed it would just remember the sim information, not a good assumption, I had to factory reset and go through the setup again.
echoarcade28 said:
Worked great. As stated, Google Pay didn't work, but Chase and Mario Run worked (which they didn't on my last rooted device). Thanks!
Click to expand...
Click to collapse
How is that possible? With my very very old Nexus 5, a custom ROM and Magisk, Google Pay perfecty works... (I'm waiting for the 3a)
Thanks for this thread! I just want to inform folks who just bought their Pixel 3a/Pixel 3a XL from T-Mobile, that root is not possible as of now since the bootloader is locked. I was misinformed thinking the bootloader would be unlocked. However, the bootloader came locked and is dependent upon factory unlocking your device. In which, T-Mobile only offers after 45 days being on their service and paying the device off in full
xFierce said:
Thanks for this thread! I just want to inform folks who just bought their Pixel 3a/Pixel 3a XL from T-Mobile, that root is not possible as of now since the bootloader is locked. I was misinformed thinking the bootloader would be unlocked. However, the bootloader came locked and is dependent upon factory unlocking your device. In which, T-Mobile only offers after 45 days being on their service and paying the device off in full
Click to expand...
Click to collapse
You sure not confusing their carrier unlock policy with unlocking bootloader. The phone's all have locked bootloaders they are just easily unlocked using fastboot.
Sent from my [device_name] using XDA-Developers Legacy app
shadyshadow said:
You sure not confusing their carrier unlock policy with unlocking bootloader. The phone's all have locked bootloaders they are just easily unlocked using fastboot.
Click to expand...
Click to collapse
I tried to unlock the bootloader through fastboot but received an error. On tmobile pixel 3a devices the bootloader is linked to OEM unlocking of the device unfortunately. OEM unlocking is grayed out on tmobile sim locked devices until they're permanently unlocked by tmobile.
xFierce said:
I tried to unlock the bootloader through fastboot but received an error. On tmobile pixel 3a devices the bootloader is linked to OEM unlocking of the device unfortunately. OEM unlocking is grayed out on tmobile sim locked devices until they're permanently unlocked by tmobile.
Click to expand...
Click to collapse
Wow..ok 45 days long time to be adding data, installing apps etc. be good to play safe and buy from Google store
Sent from my [device_name] using XDA-Developers Legacy app
shadyshadow said:
Wow..ok 45 days long time to be adding data, installing apps etc. be good to play safe and buy from Google store
Click to expand...
Click to collapse
Nah, just a few days. All they need to do is hop on Twitter and ask for SIM unlock. They'll generally do it without too much hassle so long as it's not a brand-new account and it's in good standing.
Got my 6T unlocked by them long before it was paid off, and my 3aXL SIM unlocked by them before the first payment was even made.
Not exactly a root question,
But I rooted and then tried to install the Magisk viper. I keep getting prompted to install drivers and then after a wait, a confirmation to reboot
Then all over again.
Any body found a way to get viper working without TWRP?
jcrompton said:
Not exactly a root question,
But I rooted and then tried to install the Magisk viper. I keep getting prompted to install drivers and then after a wait, a confirmation to reboot
Then all over again.
Any body found a way to get viper working without TWRP?
Click to expand...
Click to collapse
I just installed it Working great.
Download from here.
poncespr said:
I just installed it Working great.
Download from here.
Click to expand...
Click to collapse
Thanks
Did install successfully.
But I'm not familiar with that build .... Is there a way to load old saved profiles? I can't find that in the some what different UI
ok, so maybe someone here can help me out, I don't get it, why I cant unlock the bootloader on my 3a xl.
I could enable OEM unlock and USB debugging in developer settings.
"adb reboot bootloader" sets it into fastboot mode. But the command "fastboot flashing unlock" does in fact nothing.
I dont even get an error message?!
{
"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"
}
I exit out with "fastboot reboot". That does work. Could it be that Google has blocked it somehow until the 15 days return window? (Bought the 3a xl in the german google online store)
Related
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/
{
"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"
}
UNLOCK YOUR BOOTLOADER
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
Prepare Your Moto G6/G6+ for Bootloader Unlock
Code:
Your device must be charged up to 70% before going completely through the process mentioned below.
Make sure that you have installed proper device drivers on your computer.
INSTRUCTIONS:
Make sure to take a backup of your entire device data.
Download the Android SDK OR Download the Minimal ADB and Fastboot
Install the latest Motorola USB Drivers on your desktop. Download here.
Go To Settings -> Dev Settings, And Select "Allow OEM Unlock"
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
Open Command Prompt on androidsdk/platform-tools/ (Hold Shift and right click and press open command window here)
If you have downloaded Minimal ADB and Fastboot Go to C://Program Files/Minimal ADB and Fastboot and open Command Prompt from there.
Connect your Phone to PC
Type this in the CMD prompt window - fastboot oem get_unlock_data
You will get a return string. Copy it. [Right Click-Mark- Mark the text by pressing the shift key-Now press Ctrl+C]
Paste all the lines together in a notepad. Remove the empty spaces.
Now go to the Motorola Site.Sign in using your Google account or Motorola ID. Scroll down the page and paste the copied string in the field at step #6. Then click on ‘Can my device be unlocked?’, after which a "REQUEST UNLOCK KEY" button will appear at the bottom of page.
To get your unlock key, select the ‘I Agree’ option. Note: You will receive an email with your Unlock Key at the email address you used to log in there.
Important – Copy the 20-character key that Motorola sent you via email. Make sure your device is connected.
Then in CMD type: fastboot devices (To check your device is connected)
Then type: fastboot oem unlock UNIQUE_KEY
NOTE: In above command, replace the word ‘UNIQUE_KEY’ with the unlock code that you got via email. Then hit enter and the unlocking process should begin. Wait for a while and soon you’ll see ‘Bootloader Unlocked’ warning on your Moto G6/G6+.
To relock the bootloader:
before re-locking the bootloader, you must have reinstalled the official firmware
Go to Fastboot and give the command fastboot oem lock
Thank you! Great guide. :highfive:
lohanbarth said:
To relock the bootloader:[/COLOR]
Go to Fastboot and give the command fastboot oem lock
Click to expand...
Click to collapse
But please,
Advise that prior to relock the bootloader the stock firmware needs to be restored. This is important if you replaced the recovery (with TWRP), installed a custom kernel, rooted with MagiskSU (as it replaces the RAMDISK of the kernel), or replaced the bootimage (for disable the unlock message).
In fact, prior to relock is good to: wipe all data, restore all stock partitions, and then (and only then) relock the bootloader.
I hope this helps!
Regards.
manos78 said:
Thank you! Great guide. :highfive:
But please,
Advise that prior to relock the bootloader the stock firmware needs to be restored. This is important if you replaced the recovery (with TWRP), installed a custom kernel, rooted with MagiskSU (as it replaces the RAMDISK of the kernel), or replaced the bootimage (for disable the unlock message).
In fact, prior to relock is good to: wipe all data, restore all stock partitions, and then (and only then) relock the bootloader.
I hope this helps!
Regards.
Click to expand...
Click to collapse
here is edit and thank you for the info
I just bought my Moto G6 Plus (RETEU) and can't unlock it (yet). When I enter the unlock string I get "Your device does not qualify for bootloader unlocking."
If anybody knows of an alternative to patiently waiting for them to allow unlocking, I'm all ears!
sicae said:
I just bought my Moto G6 Plus (RETEU) and can't unlock it (yet). When I enter the unlock string I get "Your device does not qualify for bootloader unlocking."
If anybody knows of an alternative to patiently waiting for them to allow unlocking, I'm all ears!
Click to expand...
Click to collapse
Damn it, I have the same problem. I bought moto G6 plus because motorola allows to unlock bootloader
However I sent a message to the motorola dedicated thread for bootloader unlocking problems.
I hope there is a solution otherwise I will return the phone.
Thanks for the info! I posted in the same thread, hope they still actively monitor it...
sicae said:
Thanks for the info! I posted in the same thread, hope they still actively monitor it...
Click to expand...
Click to collapse
It seems actively maintained, last response is from yesterday.
Inviato dal mio moto g(6) plus utilizzando Tapatalk
I also don't get a key... XT1926-3/RETEU.
As usual I will wait, I'm sure there will be a solution sooner or later.
Howlbeck said:
I also don't get a key... XT1926-3/RETEU.
As usual I will wait, I'm sure there will be a solution sooner or later.
Click to expand...
Click to collapse
Hi, many users have problems to unlock Moto G6 Plus XT1926-3/RETEU, the solutions is to post a message to the motorola official thread for bootloader unlocking problems.
ok, and what happens when I did ?
Howlbeck said:
ok, and what happens when I did ?
Click to expand...
Click to collapse
they will send you unlock key. It's written in the first post
ty - didn't see it in the 1st post here. Will try
Howlbeck said:
ty - didn't see it in the 1st post here. Will try
Click to expand...
Click to collapse
You're welcome. Sorry it is in the first post of Motorola forum, not here. However, Motorola forum's moderator told me that they will send me the code within 2 business days.
Update: it seems that Motorola is updating online tool. Retry to request unlock key now
Inviato dal mio moto g(6) plus utilizzando Tapatalk
Mod Edit:
Please do not quote the entire OP.
Either quote JUST the first line, or use "hide content' tags"
[HIDE*] content to be quoted [/HIDE*] remove the *s for code to work.
lohanbarth said:
UNLOCK YOUR BOOTLOADER
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
Prepare Your Moto G6/G6+ for Bootloader Unlock
Code:
Your device must be charged up to 70% before going completely through the process mentioned below.
Make sure that you have installed proper device drivers on your computer.
INSTRUCTIONS:
Make sure to take a backup of your entire device data.
Download the Android SDK OR Download the Minimal ADB and Fastboot
Install the latest Motorola USB Drivers on your desktop. Download here.
Go To Settings -> Dev Settings, And Select "Allow OEM Unlock"
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
Open Command Prompt on androidsdk/platform-tools/ (Hold Shift and right click and press open command window here)
If you have downloaded Minimal ADB and Fastboot Go to C://Program Files/Minimal ADB and Fastboot and open Command Prompt from there.
Connect your Phone to PC
Type this in the CMD prompt window - fastboot oem get_unlock_data
You will get a return string. Copy it. [Right Click-Mark- Mark the text by pressing the shift key-Now press Ctrl+C]
Paste all the lines together in a notepad. Remove the empty spaces.
Now go to the Motorola Site.Sign in using your Google account or Motorola ID. Scroll down the page and paste the copied string in the field at step #6. Then click on ‘Can my device be unlocked?’, after which a "REQUEST UNLOCK KEY" button will appear at the bottom of page.
To get your unlock key, select the ‘I Agree’ option. Note: You will receive an email with your Unlock Key at the email address you used to log in there.
Important – Copy the 20-character key that Motorola sent you via email. Make sure your device is connected.
Then in CMD type: fastboot devices (To check your device is connected)
Then type: fastboot oem unlock UNIQUE_KEY
NOTE: In above command, replace the word ‘UNIQUE_KEY’ with the unlock code that you got via email. Then hit enter and the unlocking process should begin. Wait for a while and soon you’ll see ‘Bootloader Unlocked’ warning on your Moto G6/G6+.
To relock the bootloader:
before re-locking the bootloader, you must have reinstalled the official firmware
Go to Fastboot and give the command fastboot oem lock
Click to expand...
Click to collapse
I'm getting this error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
front camera broken
hi
i unlocked my bootloader (G6 plus) with this tutorial, and now my front camera doesn't work anymore. When i want to select it in the camera-app, the app freeze and crash.
What can I do?
Shall I relock the bootloader, and send it back to amazon?
I didn't modified the recovery, and flashed nothing. Is it enough to make
Code:
fastboot oem lock
And do I have to save my data, because there is a full wipe like in the unlock?
Or is there another solution?
Thanks for your help!
algieba said:
hi
i unlocked my bootloader (G6 plus) with this tutorial, and now my front camera doesn't work anymore. When i want to select it in the camera-app, the app freeze and crash.
What can I do?
Shall I relock the bootloader, and send it back to amazon?
I didn't modified the recovery, and flashed nothing. Is it enough to make And do I have to save my data, because there is a full wipe like in the unlock?
Or is there another solution?
Thanks for your help!
Click to expand...
Click to collapse
Your camera problem is not related to unlocking the bootloader, also your warranty is void now, you should do a full factory reset again and see it that fixes it, if not reflash stock rom
Does requesting the code void the warranty, or only actually unlocking it?
PorygonZRocks said:
Does requesting the code void the warranty, or only actually unlocking it?
Click to expand...
Click to collapse
Just requesting the code is enough to void the warranty.
Regards.
Enviado desde mi moto g(6) plus mediante Tapatalk
PorygonZRocks said:
Does requesting the code void the warranty, or only actually unlocking it?
Click to expand...
Click to collapse
No requesting will not void the warranty. Idk why dude is saying just even requesting it will do that cause it doesn't lol. Once you get the bootloader unlock code you get from the Moto website and put it in cmd and actually unlock the bootloader is when you void the warranty. The only exception is if you somehow have gotten a Dev edition of the phone.
ninjakira said:
No requesting will not void the warranty. Idk why dude is saying just even requesting it will do that cause it doesn't lol. Once you get the bootloader unlock code you get from the Moto website and put it in cmd and actually unlock the bootloader is when you void the warranty. The only exception is if you somehow have gotten a Dev edition of the phone.
Click to expand...
Click to collapse
The Motorola unlock bootloader site and accompanying legal document both suggest that obtaining the unlock code is enough to void your Motorola warranty. https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a the way it's been written (though I'm not a lawyer) suggests your warranty is void regardless of whether you use it or not. Of course, local consumer law may still offer you protection.
Hi Guys,
first off i am no dev but i am a tech nerd and want to gain access to everything on my phone.
After some digging around i finally figured out how to Unlock the Bootloader of my Xiaomi Black Shark (Global Version).
The steps might vary for the Chinese Version but i guess they might be the same.
CAUTION! THIS WILL ERASE YOUR WHOLE DATA AND SETTINGS!
What you need:
Your Xiaomi Black Shark
Drivers installed (you can use the miunlock tool for that but dont need it to unlock the Bootloader)
ADB installed.
A Backup tool.
If you want to unlock the bootloader do the following:
First Backup all your files and Settings.
Go to Settings/System/About the Phone and Tap on the Build Number to gain Dev Settings
In the Dev Settings enbale USB Debugging and OEM Unlock.
Connect your device to your computer.
Install the ADB Drivers if you did not already do so
Open a command prompt as admin
Type in
Code:
adb devices
to see if your device is recognized. If not try again to install them through the MiUnlock tool.
If it is recognized it will look like this:
{
"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"
}
After that type
Code:
adb reboot bootloader
as soon as your phone restarts remove it from the USB Cable. Otherwise it might want to reboot right after you tried it.
Connect it to the cable again as soon as you are in Fastboot.
In your console type
Code:
fastboot flashing unlock
Type
Code:
fastboot reboot bootloader
or use the menu of the Bootloader to reboot to the Bootloader. As you will see your device is now unlocked.
thats it ?
Yes. That`s it. Proof right here https://i.imgur.com/tRgWSpi.jpg Unfortunately the forum wouldnt scale it down.
I would love to tamper with it further but unfortunately i can not backup the boot.img caused by missing root which i would need to install root with the Magisk Manager since there is no TWRP for it yet.
in china rom cant unlock, please tell me,.. thanks
siliwangi said:
in china rom cant unlock, please tell me,.. thanks
Click to expand...
Click to collapse
Seems it is different for the Chinese Version then. So im not able to help you since i do not have the Chinese Version.
Failed <Unlock is not allowed on device has sales on market!>
It happens on Black Shark CN version.
Zerohexer said:
Failed <Unlock is not allowed on device has sales on market!>
It happens on Black Shark CN version.
Click to expand...
Click to collapse
Like i already wrote under the MIUI Forum Post. It seems that the way to do this for the chinese Version is different and since i do not own the Chinese Version i can not test anything aside from that that would be way over my abilities.
Invisan said:
Yes. That`s it. Proof right here https://i.imgur.com/tRgWSpi.jpg Unfortunately the forum wouldnt scale it down.
I would love to tamper with it further but unfortunately i can not backup the boot.img caused by missing root which i would need to install root with the Magisk Manager since there is no TWRP for it yet.
Click to expand...
Click to collapse
If you already unlocked device and you want to try to root it you can download stock rom for your model (same build that you are using), extract boot.img, put it in your sdcard, install Magisk apk and patch it through the app, then move your patched-boot inside adb folder to your pc and flash it using fastboot; in order to can reboot device is probably that you need to format data, maybe not. But it´s possible too that device refuses permanently to boot and you need to flash the stock boot image again.
this is irritating, i believe Xiaomi or Blackshark itself should do something regarding this.
Hello guys, i am in the same situation. I have the Black Shark's chinese version and i'm stuck here "Failed <Unlock is not allowed on device has sales on market!>"
I have 2 days left to decide if i keep or not the phone but in this state (not rooted, and doesn't know if i could do it a day or not), i can't keep it.
If someone have a solution, i'll be really grateful and i'm sure i'm not the only one.
Thanks.
Yotatouch said:
Hello guys, i am in the same situation. I have the Black Shark's chinese version and i'm stuck here "Failed <Unlock is not allowed on device has sales on market!>"
I have 2 days left to decide if i keep or not the phone but in this state (not rooted, and doesn't know if i could do it a day or not), i can't keep it.
If someone have a solution, i'll be really grateful and i'm sure i'm not the only one.
Thanks.
Click to expand...
Click to collapse
Honestly?
Just return it. Community is almost dead, no root/unlocked bootloader, limited Google Services support (Google Home and Assistant have problems, Android Auto won't mirror).
There seemed to be a little hope with the unlocked bootloader but if that's achieved only on the Global version, it's useless to us unfortunately.
Invisan said:
Like i already wrote under the MIUI Forum Post. It seems that the way to do this for the chinese Version is different and since i do not own the Chinese Version i can not test anything aside from that that would be way over my abilities.
Click to expand...
Click to collapse
If you are willing to share some ideas to test and try to unlock the chinese version, I'd be very happy to help.
I have a chinese Black Shark.
Offical Xiaomi unlock tool seems to recognize the phone but gets an error at 99%
The command you provided gives the error someone else posted (about the market).
loriz said:
Honestly?
Just return it. Community is almost dead, no root/unlocked bootloader, limited Google Services support (Google Home and Assistant have problems, Android Auto won't mirror).
There seemed to be a little hope with the unlocked bootloader but if that's achieved only on the Global version, it's useless to us unfortunately.
Click to expand...
Click to collapse
Thank you for your feedback.
This is what will happen at the end... i still have 2 or 3 days left but if i don't have any hope, i'll probably do it with regrets cause i love the phone. Technically it is a monster and i don't get why people doesn't work harder on it to figure out how to root the chinese version.
is you phone is BlackShark 2 (helo),this one ,2 have rgb logo in back.
https://unwire.hk/2018/11/02/helo/shop_guide/
BlackShark 1 not have Global version
1 https://www.mi.com/blackshark/
2 https://www.mi.com/blackshark2/
Blackshark 1 has a global Version!
Band 20 LTE, an other rom and unlockable bootloader.
We only need twrp to flash gsi roms.
black shark versione globale banda 20
mi e arrivato ieri questo smartphone, ma fin dalla accensione non mi e piaciuto. italiano si c'è, multilingue ma un android stock non c'è praticamente nulla, si servizi google funzionanti, ma non ci sono impostazioni tipo miui in un telefono così e proprio un castrone.
inservibile praticamente, con una rom xiaomi.eu sarebbe il top, ma questi sviluppatori non si trovano nemmeno a pagarli.
Invisan said:
Hi Guys,
first off i am no dev but i am a tech nerd and want to gain access to everything on my phone.
After some digging around i finally figured out how to Unlock the Bootloader of my Xiaomi Black Shark (Global Version).
The steps might vary for the Chinese Version but i guess they might be the same.
CAUTION! THIS WILL ERASE YOUR WHOLE DATA AND SETTINGS!
What you need:
Your Xiaomi Black Shark
Drivers installed (you can use the miunlock tool for that but dont need it to unlock the Bootloader)
ADB installed.
A Backup tool.
If you want to unlock the bootloader do the following:
First Backup all your files and Settings.
Go to Settings/System/About the Phone and Tap on the Build Number to gain Dev Settings
In the Dev Settings enbale USB Debugging and OEM Unlock.
Connect your device to your computer.
Install the ADB Drivers if you did not already do so
Open a command prompt as admin
Type in
Code:
adb devices
to see if your device is recognized. If not try again to install them through the MiUnlock tool.
If it is recognized it will look like this:
After that type
Code:
adb reboot bootloader
as soon as your phone restarts remove it from the USB Cable. Otherwise it might want to reboot right after you tried it.
Connect it to the cable again as soon as you are in Fastboot.
In your console type
Code:
fastboot flashing unlock
Type
Code:
fastboot reboot bootloader
or use the menu of the Bootloader to reboot to the Bootloader. As you will see your device is now unlocked.
Click to expand...
Click to collapse
this metod is working thank you !!!!!
model skr-h0 international
the comand fastboot flashing unlock works !!!!!!
now we need the patched boot
patched_boot.img for the black shark please !!!!!
we need root
3B3RT said:
this metod is not working .
model skr-h0 international
the comand fastboot flashing unlock is not working
Click to expand...
Click to collapse
Well that is not really an answer we can help you with without Screenshots or an error message.
Invisan said:
Well that is not really an answer we can help you with without Screenshots or an error message.
Click to expand...
Click to collapse
it works !!!!
now we need a patched boot
patched_boot.img i hope someone do this
3B3RT said:
it works !!!!
now we need a patched boot
patched_boot.img i hope someone do this
Click to expand...
Click to collapse
Unfortunately BlackShark is Not willing to provide us with the full Image so that wont Happen in the near Future.
3B3RT said:
it works !!!!
now we need a patched boot
patched_boot.img i hope someone do this
Click to expand...
Click to collapse
rooted and unrooted. many crashing things happened a lot. including mine was bricked twice. lol.
The Nokia 7.2, surprisingly, comes with an unlockable bootloader. The information is shared by TechMesto and I am just re-using it to create this guide.
Notes:
Unlocking the bootloader may void the device's warranty.
All existing data on the device will be erased.
To unlock:
Update: Nokia has disabled the unlock ability with the December MR. You can only unlock if you downgrade your phone to an old release first. You can get it at Nokia Care or by buying remote flashing services.
Before you start: Make sure that you have platform-tools downloaded on your PC. You need to open a CMD or Terminal window in the folder where you have saved the platform-tools, unless you have installed them system-wide.
• First of all, enable Developer Options by tapping 7 times on BuildID in "About phone".
• Then go to developer options and enable OEM Unlocking option.
• Now reboot the phone into bootloader/fastboot mode. You can use the adb command:
Code:
adb reboot-bootloader
or else use hardware keys to reboot to bootloader mode.
• Make sure the phone is detected in fastboot mode. Then send the OEM unlocking command:
Code:
fastboot flashing unlock
• Confirm the unlock on the phone.
{
"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"
}
• That's it!
You can also do the unlock_critical if you plan to flash the bootloader.
Reserved for future use.
I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?
KohGeek said:
I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?
Click to expand...
Click to collapse
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.
singhnsk said:
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.
Click to expand...
Click to collapse
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.
KohGeek said:
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.
Click to expand...
Click to collapse
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.
singhnsk said:
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.
Click to expand...
Click to collapse
I was curious too, it kicked me off the bootloader screen when I was doing that on version 060, but it seems all is well now
https://nokiamob.net/2019/11/02/off...nlock-the-nokia-7-2-and-nokia-6-2-bootloader/
I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??
Coolboy996 said:
I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??
Click to expand...
Click to collapse
You can use TWRP or patched image to root the 7.2
Can confirm that it is still unlockable. Got 2 of them today from Argos in the UK (Scotland). They are on 00WW_1_130 with security batch from 2019/08/05.
Only thing I had to do was enable internet and reboot to get the option to stop being greyed out.
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Are you sure? Has Horrendously Menacing Dicks actually started blocking people having reasonable control of their 7.2 devices after letting them have it for so long?
allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Yep. They blocked the ability with the most recent December MR.
singhnsk said:
Yep. They blocked the ability with the most recent December MR.
Click to expand...
Click to collapse
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.
CGarz said:
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.
Click to expand...
Click to collapse
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.
That really sucks. Now no devs will buy it =(.
allc0re said:
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.
Click to expand...
Click to collapse
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.
bkttk2 said:
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.
Click to expand...
Click to collapse
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.
Lamtanloc512 said:
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.
Click to expand...
Click to collapse
Think we may be out of luck then, but one last suggestion. I noticed when reading through the thread on user indicated they were using "flash" instead of "flashing" when trying to unlock the bootloader.
I know I personally did the same thing at first. Did anyone confirm that "flashing" was used?
I know the older methods used flash. Just asking.
I have an alcatel 1b which I am trying to install Magisk and TWRP on (any decent guides on that would be appreciated).
I'm told I first need to unlock the bootloader.
I am on a mac so I have installed ADB via homebrew
If I run
Code:
adb devices
, the device shows up.
I then run
Code:
adb reboot bootloader
and the device boots up into a screen which says "fastboot mode" at the top
I then try
Code:
fastboot oem unlock
and get
Code:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I tried
Code:
fastboot flashing unlock
and
Code:
fastboot oem unlock-go
and
Code:
fastboot oem get_unlock_code
and get the same response.
I also tried
Code:
ADB fastboot flashing unlock
and got
Code:
ADB: unknown command fastboot
If I enter recovery mode and then select "enter fastboot" I get a different screen with big red text saying "fastbootd" at the top.
If I then try
Code:
fastboot oem unlock
I get
Code:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Anybody know what I'm doing wrong/what I can do to get past this?
Same issue here!?
same here its because the bootloader is not unlocked and queries all say it is we need a backup or pull of someones boot.img to make a magisk boot img for our particular phone (seoul tct alcatel 5002s 1b) greatly appreciated if i could get a copy of that
To get Fastboot working try to use Alcatel's USB Driver
Download Alcatel USB Driver for Windows (Latest Driver)
Download the latest and original Alcatel USB Driver to connect any Alcatel Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
I'm also having the exact same issue. Anyone have a solution yet?
jokey carrot said:
I'm also having the exact same issue. Anyone have a solution yet?
Click to expand...
Click to collapse
Try fastboot flashing unlock-critical, I'm sceptical of it'll work
this is a goid phone to remove bloatware ob and use it for simple things, like an MP3 player. can someone pull the boot.img or show me where i can learn how to do it myself? and how would i patch it with Magisk?
i may just be a newbie, but doesnt putting the device in download mode let you flash anything? could i be able to flash majisk and obtain root while in download mode? or flash TWRP?
I am hoping to unlock the bootloader and use any customer recovery like TWRP or orangefox. Also Alcatel 1b 5002s (Canada) firmware would greatly appreciate if some one can help?
Its not yet possible to unlock the bootloader. For the past year i worked hard to figure this phone out. All of that lead to this
new link down below, the original file had alcatel protection not removed causing imei loss
that file contains firmware, flash tools and has intstructions on how to restore a lost imei.
Hope it helps you. You can also try to look at the bootloader file and try to unlock the phone.
If you need anything more feel free to dirrect message
KashiNEC said:
Its not yet possible to unlock the bootloader. For the past year i worked hard to figure this phone out. All of that lead to this
.........................................................................
that file contains firmware, flash tools and has intstructions on how to restore a lost imei.
Hope it helps you. You can also try to look at the bootloader file and try to unlock the phone.
If you need anything more feel free to dirrect message
Click to expand...
Click to collapse
Where is the firehose loader.bin file located?
I made an error zipping the file. New link here
It is in description
*firehose included*
I have noticed that in other devices they manage to unlock the bootloader through the EDL mode, who removes and needs to perform Test Point or needs more than that, for example a special EDL cable may be necessary, this morning I was trying to backup my Stock ROM with the Inferno Unitool, the funny thing is that it recognized the port but I don't know, it seemed that something else was missing, in the end I ended up flashing the @KashiNEC ROM with the guide of your audit. I'm still interested in installing GSI to at least get an upgrade to A12, I won't give up in the meantime.
Alain+ said:
I have noticed that in other devices they manage to unlock the bootloader through the EDL mode, who removes and needs to perform Test Point or needs more than that, for example a special EDL cable may be necessary, this morning I was trying to backup my Stock ROM with the Inferno Unitool, the funny thing is that it recognized the port but I don't know, it seemed that something else was missing, in the end I ended up flashing the @KashiNEC ROM with the guide of your audit. I'm still interested in installing GSI to at least get an upgrade to A12, I won't give up in the meantime.
Click to expand...
Click to collapse
For now its is not possible to unlock. Alcatel/TCL have clearly thought of someone dumping the system and have taken measures. boot partition doesnt contain the usual "unlock" stuff and bootloader seems to be modified and needs to be signed for the phone to accept it. The only thing you can do is upgrade to the newer russian version of the firmware by changing traceability.bin. But theres a little bit of hope. The bootloader makes a few references to a "secret key" and that it needs to be updated. If we can somehow get the secret key, we can unlock
This device is full of secrets everywhere, it obviously looks like a safe.
{
"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"
}
There were days when I knew there was an engineer mode, however I didn't know how to access that corner, until with the utility shown in the image, I also got the code: *#*#825364 #*#* although not much can be done with this...
Alain+ said:
This device is full of secrets everywhere, it obviously looks like a safe.
View attachment 5685055
There were days when I knew there was an engineer mode, however I didn't know how to access that corner, until with the utility shown in the image, I also got the code: *#*#825364 #*#* although not much can be done with this...
Click to expand...
Click to collapse
Interesting discovery. I think i got how to unlock bootloader now. There is a hidden app on this device called TCL TOKEN. It enables you to unlock bootloader, but requires a valid connection. I couldnt get it to connect
KashiNEC said:
Interesting discovery. I think i got how to unlock bootloader now. There is a hidden app on this device called TCL TOKEN. It enables you to unlock bootloader, but requires a valid connection. I couldnt get it to connect
Click to expand...
Click to collapse
I'm in the same situation. It seems that something else is missing or that service is disabled.
For a moment I thought it was my connection or that I was doing something wrong.