works only for Development phones
{
"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"
}
WHAT IS A BOOTLOADER, CAN I UNLOCK IT AND WHAT ARE THE RISKS?
What is a "bootloader?"
What does it mean to unlock the bootloader?
What is "Rooting?"
Does unlocking the bootloader mean I can use my device with any wireless operator?
Should I unlock the bootloader on my device?
How do I tell if my device has an unlockable/re-lockable bootloader?
Will all of my content, data and applications be there after unlocking?
If Google was backing up my device before I unlocked, will all of that data be restored if I set up the same account on the unlocked device?
What happens to my DRM-Protected content after unlocking?
After unlocking my bootloader, why don't some applications work?
Is there a list of the applications that won't work with an unlocked bootloader?
What is "Fastboot" and where do I get it?
How do I access Fastboot on Motorola devices?
Can I re-lock my device after I have unlocked the bootloader?
Will I receive software updates automatically after I have unlocked the bootloader?
WHAT MIGHT GO WRONG WHEN I TRY TO UNLOCK MY DEVICE?
How do I know if Fastboot recognizes my device?
What is my Device ID ?
The string "fastboot oem get_unlock_data" does not return any device ID. What can I do?
I can get a device ID, and my device is listed as supported, but I am getting a "DEVICE NOT FOUND" error when verifying that my device is eligible for unlock. Why?
I can get a device ID, and my device is listed as supported, but I am getting a "DEVICE IS NOT ELIGIBLE FOR UNLOCK" error when verifying that my device is eligible for unlock. Why?
I can get a device ID, and my device is listed as supported, but I am getting another error. Why?
When is my Warranty voided?
How do I re-lock my device and go back to the original software?
Who can I contact for any issues with the unlocking procedure?
How do I get support after I have unlocked and reflashed my own system image?
WHAT IS A BOOTLOADER?
The bootloader performs basic hardware initialization, verifies the integrity of the operating system, starts the operating system, and provides a method to update device software. This validation is important to verify that the software loaded on the device will not damage sensitive components (radios, processors, etc.) or violate regulatory or carrier requirements. Google provides a base bootloader as part of the Android operating system, and most device manufacturers optimize this for their specific devices.
WHAT DOES IT MEAN TO UNLOCK THE BOOTLOADER?
Unlocking the bootloader is the first step towards gaining root privileges. Some developers and enthusiasts unlock and root in order to experiment with applications or with custom builds of Android. Needless to say, you should not attempt to unlock the bootloader unless you know what you are doing.
WHAT IS ROOTING?
Rooting is when the user has gained root or administrative privileges on the device. In general, this gives users access to make modifications that would not normally be possible. With such privileges comes both risk and additional capability-best left to the very technically savvy. With rooting, you could make changes to the device that may permanently damage it or render it inoperable.
DOES UNLOCKING THE BOOTLOADER MEAN I CAN USE MY DEVICE WITH ANY WIRELESS OPERATOR?
No, this does not disable a carrier subsidy lock if one exists. Some subscriptions are tied to a specific wireless operator and the phone cannot be used on another operator's network. A "locked bootloader" and "carrier subsidy lock" are thus two entirely different topics. Do not unlock the bootloader if you are want to to disable the carrier subsidy lock.
SHOULD I UNLOCK THE BOOTLOADER ON MY DEVICE?
Motorola strongly recommends that users do not alter a product's operating system, which includes rooting the device, unlocking the bootloader or running any operating software other than the approved versions issued by Motorola and its partners. If you do, certain functions in your phone might cease to work. You may also damage your phone permanently. Unlocking the bootloader may cause your device to be unsafe and/or cause it to malfunction resulting in physical injuries or significant damage. Developer editions sold with an unlockable bootloader are sold "as-is" with no warranty. Any other device which has had its bootloader unlocked, or whose operating system has been altered, including any failed attempts to unlock the bootloader or alter such operating system, are not covered by Motorola's warranty. Please read more about the risks associated with unlocking the bootloader.
1. IMPORTANT FCC INFORMATION: YOU MUST NOT MAKE OR ENABLE ANY CHANGES TO THE PRODUCT THAT WILL IMPACT ITS FCC GRANT OF EQUIPMENT AUTHORIZATION. The FCC grant is based on the product's emission, modulation, and transmission characteristics, including: power levels, operating frequencies and bandwidths, SAR levels, duty-cycle, transmission modes (e.g., CDMA, GSM), and intended method of using the product (e.g., how the product is held or used in proximity to the body). A change to any of these factors will invalidate the FCC grant. IT IS ILLEGAL TO OPERATE A TRANSMITTING PRODUCT WITHOUT A VALID GRANT.
HOW DO I TELL IF MY DEVICE HAS AN UNLOCKABLE/RE-LOCKABLE BOOTLOADER?
This depends on a few factors. First is whether the device ships with a bootloader that is capable of being unlocked or re-locked. Second is whether the wireless carrier that sells the device allows the bootloader to be unlocked, as each of our operator partners has their own policy. As new devices are released, please check the bootloader introduction page. You will be able to check whether your device shipped with an unlockable bootloader. We will be adding devices to this list regularly.
As of August 2012, the only Motorola devices which can be unlocked are:
Photon Q 4G LTE (Sprint)
RAZR Developer Edition (Europe Only)
Motorola XOOM Verizon
Motorola XOOM Wifi Worldwide
WILL ALL OF MY CONTENT, DATA AND APPLICATIONS BE THERE AFTER UNLOCKING?
No. All user data, content and media on the internal partition are erased when you unlock the bootloader. Please backup any personal content on your device before attempting to unlock. After unlocking, you may need to move data back to your device, set up user accounts, etc.
This is like a factory reset, but data on a removable SD card will not be deleted. However, any apps that depend upon user data on the internal partition will not be able to access this data. Encrypted data on a removable SD card will also be inaccessible as the encryption keys are removed when the bootloader is unlocked.
IF GOOGLE WAS BACKING UP MY DEVICE BEFORE I UNLOCKED, WILL ALL OF THAT DATA BE RESTORED IF I SET UP THE SAME ACCOUNT ON THE UNLOCKED DEVICE?
Yes, using the same account, with the caveat that anything that relied on Digital Rights Management (DRM)-protected content and/or encrypted data will not work if the bootloader is unlocked.
WHAT HAPPENED TO MY DRM-PROTECTED CONTENT AFTER UNLOCKING?
Content that requires Digital Rights Management (DRM) - such as rented movies in Google Play Movies - will not be available if the device is unlocked. This content is only enabled when the bootloader is in a locked state and when the device is running the original software as shipped by Motorola. When the device is re-locked and running the original software image, these capabilities should become available again.
AFTER UNLOCKING MY BOOTLOADER, WHY DON'T SOME APPLICATIONS WORK?
Certain applications rely on functionality that is only available to a device with a locked bootloader and OEM approved software; thus, once the bootloader is unlocked, they will no longer function properly.
IS THERE A LIST OF ALL OF THE APPLICATIONS THAT WILL NOT WORK WITH AN UNLOCKED BOOTLOADER?
Due to the ever-expanding list of new and revised Android apps and developers, it would be difficult to maintain such a list accurately, so no complete list exists.
WHAT IS 'FASTBOOT' AND WHERE DO I GET IT?
Fastboot is the protocol to update the flash file system in Android devices and supports the commands to unlock or lock the device. Fastboot is included in the Android SDK. See the Google developer site for more details.
HOW DO I ACCESS FASTBOOT ON MOTOROLA DEVICES?
Press and hold the volume down button and then press and release the power button. Alternatively, issue the command "adb reboot bootloader" from a terminal window using the Android SDK when connected to the device via USB cable.
CAN I RE-LOCK MY DEVICE AFTER I HAVE UNLOCKED THE BOOTLOADER?
Yes, by re-loading an original Motorola software image and re-locking the bootloader. After relocking your device, you will only be able to reflash your device with a signed system image. If such an image is not available online, you will have to send it to MOTOROLA support for reflashing. MOTOROLA reserves the right to charge for such assistance. Regardless of whether your device is re-locked, such device is still not covered by the MOTOROLA warranty.
WILL I RECEIVE SOFTWARE UPDATES AUTOMATICALLY AFTER I HAVE UNLOCKED THE BOOTLOADER?
Not necessarily; it will depend on what modifications you have made to the software. Accepting a MOTOROLA OTA (over the air) software update after unlocking your device and rooting or modifying your original system software might render your device inoperable. MOTOROLA therefore recommends you do not accept OTA updates after unlocking. MOTOROLA has no obligation to offer software updates for un-locked devices.
[/IMG]
HOW DO I KNOW IF FASTBOOT RECOGNIZES MY DEVICE ?
To validate your installation, please follow these steps:
Turn off your phone.
Push and hold the power and volume down at the same time, release the power button then release volume down. The key sequence to power up in fastboot mode might differ between phone models. The device will power up in Fastboot mode and display a screen similar to this
Connect the phone to the computer via USB-cable. The Fastboot screen on the device will indicate that the device is connected to the Desktop over USB.
Open a command window
Change directory to the tools folder within the Android SDK folder.
To verify that the Desktop and Phone are connected, enter fastboot.exe devices . This should list your device as connected.
WHAT IS MY DEVICE ID ?
Your device ID is a unique string, retrieved through the fastboot command, which is used to generate a unique unlock code for your device. You can retrieve your Device ID by issuing "fastboot oem get_unlock_data" at the command prompt. Your Device ID is unique to your device, and should not be shared with anyone or posted online.
THE STRING "fastboot oem get_unlock_data" DOES NOT RETURN ANY DEVICE ID. WHY?
The bootloader on Motorola devices released before August 2012 is not unlockable. This fastboot command will not return a device ID or unlock data for these Motorola devices. At this point, only the devices on our Supported Devices list are eligible for the unlockable bootloader program.
The Motorola XOOM Tablet and Developer Edition RAZR can be unlocked through our legacy method.
If your device is on our supported list, and fastboot does not work or does not return a device id, please try the following.
Check that your device is in Fastboot mode. On most devices, to enter fastboot mode, power the device off then power up while pressing the power and volume down button simultaneously.
After powering up in fastboot mode, connect your device to your desktop using a USB cable. The fastboot screen on your device should indicate that it is connected over USB
Make sure the Motorola drivers for your device are installed
Make sure fastboot and the Android SDK are installed
I CAN GET A DEVICE ID, AND MY DEVICE IS LISTED AS SUPPORTED, BUT I AM GETTING "DEVICE NOT FOUND" ERROR WHEN VERIFYING THAT MY DEVICE IS ELIGIBLE FOR UNLOCK. WHY?
This error means that our unlock tool checked our online database but could not find a match between the Device ID/Unlock Data you submitted and any device in our database. This should only happen if the device data entered is not correct, or there are delays in updates to our device database.
Please check that your device model, as sold by your operator, is on our supported devices list
Please double check your device ID has to be entered correctly in the Verification field. The output from the fastboot command must be entered in the validation field on a single line, without any (bootloader) string, empty spaces, line feeds or carriage returns.
For example:
$ fastboot oem get_unlock_data ...
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
OKAY [ 0.297s]
must be entered in the Device ID field as a single entry, with no white spaces
0A40040192024205#4C4D355631323030373731363031303332323239#
BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
I CAN RETRIEVE A DEVICE ID, AND MY DEVICE IS LISTED AS SUPPORTED, BUT I AM GETTING "DEVICE NOT ELIGIBLE FOR UNLOCK" ERROR WHEN VERIFYING THAT MY DEVICE IS ELIGIBLE FOR UNLOCK. WHY?
This error means that our unlock tool checked our online database and determined your device and carrier combination is not part of our unlockable bootloader program and, therefore can not be unlocked. Some of our operator partners do not allow unlockable devices on their networks. That is why a device with one operator may be unlockable, but the same model with a different carrier might not.
I CAN RETRIEVE A DEVICE ID, AND MY DEVICE IS LISTED AS SUPPORTED, BUT I AM GETTING ANOTHER ERROR WITH THE ONLINE TOOL. WHY?
Please consult our forum for answers. When posting an issue to this forum, do not post your Device ID on any public forum as it could be used by a third party to generate an unlock code on your behalf and void your device warranty.
WHEN IS MY WARRANTY VOIDED ?
Your device warranty will be voided as soon as an unlock code has been generated through our online tool, regardless of whether you actually unlock your device. Please do not request a bootloader unlock code unless you have read and accepted the terms of our legal agreement.
HOW DO I RE-LOCK MY DEVICE AND GO BACK TO ORIGINAL SOFTWARE ?
You can re-lock your device. Re-locking a bootloader will ensure that the device will only boot to Motorola signed and provided Android Images. PLEASE NOTE: Re-locking a device will not reinstate your device warranty as damage might have occurred when the device was unlocked.
To return to Original Software, you will need to reflash a Motorola signed software image to your device, or send it in to our service center to get reflashed. MOTOROLA reserves the right to charge for any assistance required by users during this process. At this time, we are not posting a recovery image for the Photon Q 4G LTE.
WHO DO I CONTACT FOR ANY OTHER ISSUE WITH THE UNLOCKING PROCEDURE?
Please consult our forum for questions and answers. When posting an issue to this forum, do not post your Device ID on any public forum as it could be used by a third party to generate an unlock code on your behalf and void your device warranty.
https://forums.motorola.com/pages/home
HOW DO I GET SUPPORT AFTER HAVING UNLOCKED AND REFLASHED MY OWN SYSTEM IMAGE?
Motorola is unable to provide you with assistance. Please consult online forums, such as the XDA developer community.
http://www.xda-developers.com
HERE IS THE URL TO MOTOROLA'S UNLOCK YOUR DEVICE PAGE. BE SURE TO CHECK FREQUENTLY TO SEE IF YOUR DEVICE MAKES THE LIST OF SUPPORTED DEVICES
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
In Europe, the Motorola RAZR™ Developer Edition is now available through the Motorola Shop.
http://developer.motorola.com/products/bootloader/
Here's the link to take a look at the Photon Q
http://www.motorola.com/us/consumers/MOTOROLA-PHOTON%E2%84%A2-Q-4G-LTE/m-PHOTON-Q-4G-LTE,en_US,pd.html?WT.mc_id=social_blog_asanti_bootloader&WT.mc_ev=click
IF YOU HAVE FOUND THIS HELPFUL PLEASE GIVE THANKS
It doesn't even work for the RARZ yet, if it ever will. Thread locked. Discuss here
Reopened
I get the following error
after i put this command $ fastboot oem get_unlock_data
I get the following error
...
FAILED (remote: (00120000))
finished. total time: 0.246s
I have xoom mz604
sorry! English is not my native language
Do you have the Android sdk and all the drivers properly installed?
Sorry it took to answer
hi,
I installed everything the sdk asked me to update and install
and the error still appears :silly:
1. Check that your device is in Fastboot mode. On most devices, to enter fastboot mode, power the device off then power up while pressing the power and volume up and down button simultaneously. You'll get a black screen scroll down using volume down to Ap Fastboot mode select by pressing volume up.
2. After powering up in fastboot mode, connect your device to your desktop using a OEM USB cable that came with the device. The fastboot screen on your device should indicate that it is connected over USB
3. Make sure the Motorola drivers for your device are installed
4. Make sure fastboot and the Android SDK are installed
I. RETRIEVING YOUR DEVICE ID
2. Put your device in fastboot mode (Power+Vol up & Vol Down) then select Ap Fastboot mode then connect over USB
3. Open a command prompt or Terminal session
4. Go to the Directory where you installed the Android SDK tools, and type:
5. $ fastboot oem get_unlock_data
Confirmed working on O2 Germany RAZR HD:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem get_unlock_data
...
(bootloader) ****** HEX CODE ENTFERNT ******
(bootloader) ****** HEX CODE ENTFERNT ******
(bootloader) ****** HEX CODE ENTFERNT ******
(bootloader) ****** HEX CODE ENTFERNT ******
(bootloader) ****** HEX CODE ENTFERNT ******
OKAY [ 0.375s]
finished. total time: 0.376s
http://www.android-hilfe.de/motorol...-hd-voraussichtlich-kaufen-7.html#post4146048
pOOBAH1973 said:
Confirmed working on O2 Germany RAZR HD:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem get_unlock_data
...
(bootloader) ****** HEX CODE ENTFERNT ******
(bootloader) ****** HEX CODE ENTFERNT ******
(bootloader) ****** HEX CODE ENTFERNT ******
(bootloader) ****** HEX CODE ENTFERNT ******
(bootloader) ****** HEX CODE ENTFERNT ******
OKAY [ 0.375s]
finished. total time: 0.376s
http://www.android-hilfe.de/motorol...-hd-voraussichtlich-kaufen-7.html#post4146048
Click to expand...
Click to collapse
Does the code work in the website or do you have to wait for support to be added?
Very helpfull for noobs like me...
Followed instructions to letter
fast boot returns nothing
as if program ran but no parameters were met
nexus6 winows 8.1
I'm trying to unlock my Moto E 2 and I'm having a hard time. I've installed android sdk folder and have it on my macbook's desktop. I've opened a terminal from the folder and entered in "$ fastboot oem get_unlock_data" and all it says is "-bash $ command not found".
I installed the Motorola drivers from the website, and made sure all the sdk files were there including tools, and platform-tools.
What am I missing?!
Can anyone tell me how to bootload my android 2.3.7 Sony st25i???
...new to XDA.
Related
Hi,
Does anyone have a root for the Honor 6 Plus and/or way to install GAPPS?
Thanks in advance...
mikejasonsmith said:
Hi,
Does anyone have a root for the Honor 6 Plus and/or way to install GAPPS?
Thanks in advance...
Click to expand...
Click to collapse
You can look here: http://forum.xda-developers.com/android/general/huawei-honor-6-plus-root-tutorial-t2991788
Thanks but it looks like that account and link have been disabled
Use the inbuilt app center to download google play services, once installed, you can then access google play and off you go. The Chinese inbuilt app center does seem to be really good and enables you to download all Google apps and also it's app updates are ahead of Google play.
I just need to root mine now. Anyone managed it yet?
Thanks mate but it keeps saying its not supported by my device...am I downloading the wrong one?
Go to the in built app center, the blue icon, Huawei app center, Open it and the first tab should have a search page. Type in that Google play services and it should find it, if not search and then install from the link.
It installed fine on my PE-TL10 version that arrived yesterday.
Once that was installed, I could install play and the rest using the same method. No root access required to get them installed. It comes up with the accoun, new or existing page and once that's done, you can use it as normal as well as all your other Google apps.
Don't know why your having problems, this went well on mine. Just need to root it now.
I've done that but it only gives me the option to 'open' it rather than 'install' ????
Open it, it won't work without.
still can't get gmail to work. That's the on,y app that won't work.
Will have to wait for a root I guess then install GAPPS...
That should work shouldn't it?
Check out this guide to install Google apps. This exactly what I did: http://www.huaweimobileshop.com/blog/huawei-honor-6-install-google-account/
I hope it helps. I have now unlocked my boot loader but need cwm recovery for 6 plus to get root sorted as I cannot find any standalone root kit that works, so my task goes on still.
Thanks mate.
How did you get your boot loader unlocked? Will you let me know? And let me know if you find a root and GAPPS ?
Thanks
I am a bit busy today with Sunday jobs at homes but will send you all the guides I follwed and I will get the files on to a web site to download for you. The guide is around but the problem was getting the product code. All good now, so will let you have it all later today.
Sathelp said:
Check out this guide to install Google apps. This exactly what I did: http://www.huaweimobileshop.com/blog/huawei-honor-6-install-google-account/
I hope it helps. I have now unlocked my boot loader but need cwm recovery for 6 plus to get root sorted as I cannot find any standalone root kit that works, so my task goes on still.
Click to expand...
Click to collapse
Sathelp said:
I am a bit busy today with Sunday jobs at homes but will send you all the guides I follwed and I will get the files on to a web site to download for you. The guide is around but the problem was getting the product code. All good now, so will let you have it all later today.
Click to expand...
Click to collapse
Thanks mate :good:
I still do not have root as I need a valid EMUI 3.0 CWM or TWRP recovery but I do have an extracted EMUI stock recovery that I have been using while testing various supposedly Honor 6 Plus Recoveries!
So here is the Bootloader unlocking instructions taken and modified from here
Introduction
Bootloader unlocking works by using the fastboot command line utility and executing a specific command containing a ‘bootloader unlock code,’ which is unique to each specific device and must be generated based on the IMEI and serial number of the device. Once the bootloader is ‘unlocked,’ this gives us permission to flash (or overwrite) sections of the phone memory with code of our own choosing – allowing us to install recoveries, gain root access, and utilise custom ROMs (once they are available).
Huawei provide a website to generate bootloader unlock codes , but this unfortunately does not list the entirety of the Honor 6 Plus, so we have to get creative. Fortunately, there are resources available us to generate a ‘fake’ product ID for an existing model number which can trick the unlock code generator into providing us a valid code for our Honor 6 Plus, and therefore allow us to execute the bootloader unlock successfully.
Generating a Product ID
If you visit the bootloader unlock generator page (this is a page setup by Huawei themselves), you can see there are a number of required fields; namely product model, product serial number, product IMEI and product ID.
However, after selecting smartphone, you will notice that there are no Honor 6 Plus devices present in the model list – and therefore we need to generate our own product ID. To do this, download the Huawei_Product_ID_Generator (Windows only, I’m afraid) file and extract it to your machine. Please note that we did not develop this application and have no knowledge of any malware it may contain – please use your best judgement and always use antivirus when installing unknown software.
Once you have extracted the application, execute it by double clicking the .exe file. When the window appears, select Y300-0000 from the model list, and enter your devices IMEI in the field below the selection box. You can find your device IMEI on the box your Honor 6 Plus came in, or alternatively navigate on the device to Settings > About Phone > Status and your IMEI will be listed.
{
"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"
}
Selecting Y3000-000
After selecting Y300-0000 and entering your IMEI code, your newly generated product code will be visible in the lower box. Save this number or write it down somewhere safe, and move on to the next step, getting hold of the bootloader unlock code itself.
Getting a Bootloader Unlock Code
At this point, we need to go back to the official Huawei bootloader unlock code generator page. Now that we have a product ID, we are able to generate an unlock code quite easily. First of all, select Smartphone for device type, then select Y300-0000 (about halfway down) for the product model. The remaining fields should be fairly straightforward – fill in your IMEI and serial number (either from the box or on your phone in Settings > About Phone > Status) into the appropriate boxes.
For the product ID, enter the one you generated with the generator earlier – not the one of your actual device. Once all fields have been filled, complete the CAPTCHA at the bottom of the field and click ‘submit.’
If everything has been completed successfully, you will now be in possession of your unlock code. Congratulations!
Driver Installation
Now that you have an unlock code, we can move forward with unlocking the bootloader. First of all, you’ll need to download the package containing required drivers and utilities for the phone, extract it to your computer, and navigate to the resultant directory.
You will likely need to install drivers for your device, so do this now – extract the Drivers file and navigation within, then execute DriverSetup.exe and allow it to complete. When this installation has completed, restart your computer as advised by the driver installation wizard. The requisite software for the bootloader unlock and recovery installation should now be prepared and active on your computer.
Bootloader Unlock
You will need to get and down and dirty with a bit of command line magic in order to actually unlock your bootloader. The simplest way to open a command prompt in the correct place is to navigate into the adb_tools folder or somewhere you have them, and open a command line window and cd ****** to this folder. Your should have fastboot etc in this folder if correct.
The first thing to check is whether or not our device has been detected. Within the command prompt in the tools directory, enter the following command and then hit enter:
adb devices
If you don’t see any output after this, you probably need to install drivers. Install the included driver package, restart your machine, then try again. On the other hand, if you see a device listed, then everything has been detected correctly and you will be able to unlock your bootloader straight away. You then need to put your Mate 7 device into bootloader mode. The easiest way to do this is to enter the following command into the command prompt and hit enter:
adb reboot bootloader
This will get you into the bootloader mode of your device. You may have to press ‘okay’ on a phone screen popup to allow the adb command to connect properly. Once in the bootloader, we can perform the bootloader unlock. To do this, simply enter the following command and hit the enter key – replacing YOURUNLOCKCODE with the code we generated earlier:
fastboot oem unlock YOURUNLOCKCODE
If everything works correctly, you will be given a message in the command prompt, and the phone bootloader screen will now stated ‘PHONE Unlocked.’ Congratulations! You now have an unlocked bootloader.
I have added the adb set up file to get your tools folder and also a copy of the generator file
Can those with the 6 plus tell me what the pros and cons of this phone? is the camera really good or not?
Sathelp said:
I still do not have root as I need a valid EMUI 3.0 CWM or TWRP recovery but I do have an extracted EMUI stock recovery that I have been using while testing various supposedly Honor 6 Plus Recoveries!
So here is the Bootloader unlocking instructions taken and modified from here
Introduction
Bootloader unlocking works by using the fastboot command line utility and executing a specific command containing a ‘bootloader unlock code,’ which is unique to each specific device and must be generated based on the IMEI and serial number of the device. Once the bootloader is ‘unlocked,’ this gives us permission to flash (or overwrite) sections of the phone memory with code of our own choosing – allowing us to install recoveries, gain root access, and utilise custom ROMs (once they are available).
Huawei provide a website to generate bootloader unlock codes , but this unfortunately does not list the entirety of the Honor 6 Plus, so we have to get creative. Fortunately, there are resources available us to generate a ‘fake’ product ID for an existing model number which can trick the unlock code generator into providing us a valid code for our Honor 6 Plus, and therefore allow us to execute the bootloader unlock successfully.
Generating a Product ID
If you visit the bootloader unlock generator page (this is a page setup by Huawei themselves), you can see there are a number of required fields; namely product model, product serial number, product IMEI and product ID.
However, after selecting smartphone, you will notice that there are no Honor 6 Plus devices present in the model list – and therefore we need to generate our own product ID. To do this, download the Huawei_Product_ID_Generator (Windows only, I’m afraid) file and extract it to your machine. Please note that we did not develop this application and have no knowledge of any malware it may contain – please use your best judgement and always use antivirus when installing unknown software.
Once you have extracted the application, execute it by double clicking the .exe file. When the window appears, select Y300-0000 from the model list, and enter your devices IMEI in the field below the selection box. You can find your device IMEI on the box your Honor 6 Plus came in, or alternatively navigate on the device to Settings > About Phone > Status and your IMEI will be listed.
Selecting Y3000-000
After selecting Y300-0000 and entering your IMEI code, your newly generated product code will be visible in the lower box. Save this number or write it down somewhere safe, and move on to the next step, getting hold of the bootloader unlock code itself.
Getting a Bootloader Unlock Code
At this point, we need to go back to the official Huawei bootloader unlock code generator page. Now that we have a product ID, we are able to generate an unlock code quite easily. First of all, select Smartphone for device type, then select Y300-0000 (about halfway down) for the product model. The remaining fields should be fairly straightforward – fill in your IMEI and serial number (either from the box or on your phone in Settings > About Phone > Status) into the appropriate boxes.
For the product ID, enter the one you generated with the generator earlier – not the one of your actual device. Once all fields have been filled, complete the CAPTCHA at the bottom of the field and click ‘submit.’
If everything has been completed successfully, you will now be in possession of your unlock code. Congratulations!
Driver Installation
Now that you have an unlock code, we can move forward with unlocking the bootloader. First of all, you’ll need to download the package containing required drivers and utilities for the phone, extract it to your computer, and navigate to the resultant directory.
You will likely need to install drivers for your device, so do this now – extract the Drivers file and navigation within, then execute DriverSetup.exe and allow it to complete. When this installation has completed, restart your computer as advised by the driver installation wizard. The requisite software for the bootloader unlock and recovery installation should now be prepared and active on your computer.
Bootloader Unlock
You will need to get and down and dirty with a bit of command line magic in order to actually unlock your bootloader. The simplest way to open a command prompt in the correct place is to navigate into the adb_tools folder or somewhere you have them, and open a command line window and cd ****** to this folder. Your should have fastboot etc in this folder if correct.
The first thing to check is whether or not our device has been detected. Within the command prompt in the tools directory, enter the following command and then hit enter:
adb devices
If you don’t see any output after this, you probably need to install drivers. Install the included driver package, restart your machine, then try again. On the other hand, if you see a device listed, then everything has been detected correctly and you will be able to unlock your bootloader straight away. You then need to put your Mate 7 device into bootloader mode. The easiest way to do this is to enter the following command into the command prompt and hit enter:
adb reboot bootloader
This will get you into the bootloader mode of your device. You may have to press ‘okay’ on a phone screen popup to allow the adb command to connect properly. Once in the bootloader, we can perform the bootloader unlock. To do this, simply enter the following command and hit the enter key – replacing YOURUNLOCKCODE with the code we generated earlier:
fastboot oem unlock YOURUNLOCKCODE
If everything works correctly, you will be given a message in the command prompt, and the phone bootloader screen will now stated ‘PHONE Unlocked.’ Congratulations! You now have an unlocked bootloader.
I have added the adb set up file to get your tools folder and also a copy of the generator file
Click to expand...
Click to collapse
Cheers mate.
This is awesome - absolutely awesome.
I will give it a go and report back . Ive managed to load Nova on it and get it running so things are moving ahead slowly. But this will help.
Cheers
Mike
I have found a that now roots the 6Plus. Mine is now rooted and original recovery back on.
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
The tool is for the 6 not especially the 6Plus but using the install CWM recovery works, then I used the boot to recovery and then selected root by sidelobe (install zip/install zip by sidelobe menus). SU was installed permissions set. As I wanted to ensure that the correct stock recovery was used (my EMUI3.0 extracted before) I selected to reboot the phone by exiting the (recovery) and it then asked me if I wanted to fix root, I selected yes, rebooted the phone. Checked that root was working and then went back to bootloader and fastboot flash recovery (my recovery) to get it back to stock.
I am now a happy Man, bootloader unlocked and rooted. Hopefully you will be able to as well mikejasonsmith.
Sathelp said:
I have found a that now roots the 6Plus. Mine is now rooted and original recovery back on.
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
The tool is for the 6 not especially the 6Plus but using the install CWM recovery works, then I used the boot to recovery and then selected root by sidelobe (install zip/install zip by sidelobe menus). SU was installed permissions set. As I wanted to ensure that the correct stock recovery was used (my EMUI3.0 extracted before) I selected to reboot the phone by exiting the (recovery) and it then asked me if I wanted to fix root, I selected yes, rebooted the phone. Checked that root was working and then went back to bootloader and fastboot flash recovery (my recovery) to get it back to stock.
I am now a happy Man, bootloader unlocked and rooted. Hopefully you will be able to as well mikejasonsmith.
Click to expand...
Click to collapse
This is cool mate - thanks so much!
Going to try and do it over the next day or so. Really appreciate your hard work on this.
What ROM are you going to stick on it?
I am using the ROM that came with the phone from Pompmall and it updated a small update once turned on. The current ROM is marked as CUSTCHNC00D112SP05, Build Number: PE-TL10V100R001CHNC00B112SP05.
I take it that you are going to put GAPPS on while you have CWM recovery fitted? Don't forget that unless you flash back the stock recovery, you wont be able to use their update files and have to get a zip file of the ROM. But now we have a working CWM Recovery, it can be flashed easy by using fastboot if needed.
The owner of that multitool has said that he will add the 6Plus to it, so that will be good. I have provided him with my stock EMUI3.0 recovery to add in to the process.
Sathelp said:
I am using the ROM that came with the phone from Pompmall and it updated a small update once turned on. The current ROM is marked as CUSTCHNC00D112SP05, Build Number: PE-TL10V100R001CHNC00B112SP05.
I take it that you are going to put GAPPS on while you have CWM recovery fitted? Don't forget that unless you flash back the stock recovery, you wont be able to use their update files and have to get a zip file of the ROM. But now we have a working CWM Recovery, it can be flashed easy by using fastboot if needed.
The owner of that multitool has said that he will add the 6Plus to it, so that will be good. I have provided him with my stock EMUI3.0 recovery to add in to the process.
Click to expand...
Click to collapse
Ive already got GAPPS on it via Nova but this now opens up more possibilities.
What are you going to be doing to yours???? Must admit Im liking this phone so far - battery life is awesome.
{
"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"
}
The LG G6 H870 for the European market and the USA carrier-free US997 can now be officially unlocked through LG's developer unlock program.
Your H870 is from outside Europe? You have a H871/2/3/etc or H870K/DS/etc? That's not a European H870, won't work. Your US997 tied to a carrier? Won't work.
Please read the FAQ and use the thread search feature before asking questions.
This thread is a work in progress and actively being updated.
LG Developer Unlock Site Here
Prerequisites:
European LG G6 H870 or USA carrier-free US997
Computer w/ADB & Fastboot. ADB/Fastboot for Windows here. ADB/Fastboot for Linux/OS X here.
Basic knowledge of ADB, Fastboot and Windows command prompt or Linux/OS X terminal.
Device IMEI. This 15-digit code can be found on your box, the settings menu or by dialing *#06#
LG developer account -- sign up for free by clicking the "Start Unlocking the Bootloader" button at the bottom of the LG site HERE.
Directions:
LG's official bootloader unlock directions can be found here but I've still rewritten the steps out below while revising some things and also adding steps for TWRP and root.
1. Enable USB-Debugging on your phone. USB-Debugging is required for the adb commands to work. To enable USB-Debugging, go to Settings >> About phone >> Software info and tap Build number until it says you are now a developer. Return to the previous screen, select Developer Options and enable USB-Debugging (this option may be greyed out if you have your USB cable plugged into your phone).
2. Enable OEM unlock on your phone. To enable OEM unlock, go to Settings >> Developer options and toggle/turn on Enable OEM Unlock.
3. Open CommandPrompt or Terminal and enter the following ADB command to reboot into the bootloader:
Code:
adb reboot bootloader
If ADB is not detecting your device try switching your phone's USB mode from Charging to MTP or PTP. If using Windows please make sure you've installed LG's USB drivers. You can download them HERE.
Alternatively, you may be able to boot into fastboot without ADB by powering off the phone then power the phone on while holding Volume UP (USB cable will need to be removed otherwise it may boot into LG Download Mode)
4. Once in the bootloader, use the following fastboot command to obtain Device ID:
Code:
fastboot oem device-id
Fastboot command will return a string. This is the Device ID which is needed to generate your unique unlock key.
Example :
Code:
$ fastboot oem device-id
(bootloader)-----------------------------------------------------------------
(bootloader) Device-ID
(bootloader) CD58B679A38D6B613ED518F37A05E013
(bootloader) F93190BD558261DBBC5584E8EF8789B1
(bootloader)-----------------------------------------------------------------
To generate your unlock key, you will need to paste together the 2 lines of output into one continuous string without "(bootloader)" or spaces. In the example above, the Device ID would be:
CD58B679A38D6B613ED518F37A05E013F93190BD558261DBBC5584E8EF8789B1
5. Copy Device ID and IMEI into the LG Developers Bootloader Unlock site and hit the confirm button. In a few moments the unlock.bin will be emailed to you. Download unlock.bin to computer.
6. While the phone is still in fastboot enter the following command to unlock the bootloader:
This will unlock your bootloader AND factory reset your device wiping all data!
You can use the LG Backup app or LG Bridge to backup and restore your data before unlocking the bootloader.
Code:
fastboot flash unlock unlock.bin
7. You can now reboot the phone and boot into your bootloader unlocked device! Enter:
Code:
fastboot reboot
8. Want TWRP or root?
For TWRP you will need to download the TWRP H870 image. Current unofficial TWRP build is available HERE. (thanks to @Rashed97)
For root you will need to download either SuperSU or Magisk and then flash either of the zips using TWRP.
Reboot back into the bootloader
Code:
adb reboot bootloader
(you'll have to first re-enable USB debugging since data was wiped after the bootloader unlock)
or power off again.. unplug the USB cable then power on the phone while holding Volume UP.
9. Flash TWRP:
Code:
fastboot flash recovery twrp.img
After flashing TWRP unplug the USB cable and power off the phone (hold volume down + power button).. continue holding until phone reboots...
As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
Keep holding until you see the Factory Reset screen. Click thru the factory reset screens using the volume buttons to move up/down and power button to select. Choose "Yes" twice until it boots into TWRP. Despite what the screen says it won't actually factory reset/wipe your data... as long as you've installed TWRP. If stock recovery is installed it WILL wipe data.
For TWRP to "stick" you must 1st boot into TWRP and not boot back into Android until after doing one of the following...
flashing SuperSU/Magisk
deleting the recovery-from-boot.p file from the /system directory
flashing the no-verity-opt-encrypt-4.1 or android-boot-repack zips
10. Now you can flash your root zip of choice.
Feel free to back up first.. but otherwise.. time to install SuperSU/Magisk. Reboot into system when finished.
Have fun and be careful.
FAQ:
Q: I have an H870 but it is not a European H870... can I unlock the bootloader?
A: No, this official unlock program is ONLY for the H870 model for countries in Europe just like LG did for the LG G4 and G5.
But... for about a 10 day span G4 devices from SE Asia worked with the official site and users received unlock.bin files.. despite that variant never showing up on the supported list. So you never know what can happen until you try and submit your device-id/IMEI into the LG Developer Bootloader Unlock site. :good:
Q: Will more devices be added?
A: Impossible to say what will happen in the future.. we must wait and see. The LG G5 bootloader unlock program was originally only open to the European H850 but months later the H840 G5SE and the USA RS988 G5 were added to the program.
Q: I can't get my phone to show up with ADB or Fastboot, watdo?
A: Make sure ADB/Fastboot is properly setup for your OS... udev rules setup in Linux.. LG USB drivers installed for Windows... OS X/MacOS just works. Also, confirm USB debugging is enabled.
ADB still not working?... try changing the phones USB modes.. from maybe charging to MTP.. or MTP to PTP.
Q: What happens to warranty if I unlock or root?
A: YMMV I suppose. The official LG site claims that warranty is void if damage is caused by the unlock. On the T-Mobile G6 there is now a bootloader unlock counter. I will assume this counter is also on the H870/US997, so it will be hard to hide the fact that you unlocked the bootloader. Please share any unlocked bootloader LG G6 warranty replacement stories in this thread.
Q: Can I re-lock the bootloader?
It IS possible to re-lock the bootloader with the the command: fastboot oem lock
You'll have to boot back into the bootloader (adb reboot bootloader) to issue the fastboot command.
Re-locking the bootloader WILL wipe data just like the unlock process. Use LG Backup app/LG Bridge or another backup method first if you want your data.
Flashing a KDZ in LGUP or LG Bridge will NOT relock the bootloader.
DO NOT re-lock the bootloader if you have a modified boot/system img... restore them to stock first or you will not be able to boot into android after the lock and need to flash a KDZ in download mode.
Q: So many words... yudodat?
A: Here is a video on how to unlock the G4... up until the 6minute mark it is step-by-step 100% the same as G6. Only slight difference is when you get to the TWRP/root steps. https://www.youtube.com/watch?v=O64GfQORCaE
Click to expand...
Click to collapse
y u quote OP?
Follow me on twitter for future updates on LG-related things - twitter.com/@utoprime
Find this thread helpful? Hit the Thanks button!
Feeling extra generous? Consider donating to me.
Thanks autoprime, keeping an eye out for us G6 owners in the rootless wasteland ☺
(As a VS988 owner I know I'm really stuck in purgatory, but can always hope ? It was time to finally upgrade from my G3 - you did awesome work on that phone, hugely appreciated by many.)
Donated.
Oh yeah. Real theming can start...
Sent from my LG-H870 using Tapatalk
Great news ! I was really missing adblock and Xposed DPI tweaks (with such a big screen)
Did someone already flash TWRP ?
Will try it out on a H870DS eventually and see if it works. Thank you very much!!!
Don't think there is TWRP at present, its coming though.
unlock.bin sitting in my Inbox...
Looks like TWRP will be available in a few days...
Big up to all !
So my guess is that the unlock.bin would be device specific?
I've got the H870, but from ZAF...
You guess right. The file is obtained from the LG Bootloader Unlock Site, and is based on your device-id.
What is the exact model you have in System Settings -> About -> Hardware info ?
Mine is just LG-H870.
Maybe you get the Euro version in ZA ?
zEar said:
You guess right. The file is obtained from the LG Bootloader Unlock Site, and is based on your device-id.
What is the exact model you have in System Settings -> About -> Hardware info ?
Mine is just LG-H870.
Maybe you get the Euro version in ZA ?
Click to expand...
Click to collapse
Mine also just says LG-H870
The IMEI is hardware bound right?
Edit: Reason i'm asking is that i've tried the site and says "Unfortunately, your device(South Africa, (SOUTH AFRICA) )does not support unlocking the bootloader."
I wonder if installing the EU firmware will work?
Awesome!
thanks a lot, is time to mod
Without twrp we haven't make nothing.......
Enviado desde mi LG-H870 mediante Tapatalk
Finally , I have an H870, how can I know if it's the European model?
tried it with the (h870s) and it said that the device is not supported, will it ever be supported?
What about root is it working?
Well this is brilliant news, just upgraded to the G6 and it'll arrive later today so looking forward to future roms for this device.
isaakmg said:
Without twrp we haven't make nothing.......
Enviado desde mi LG-H870 mediante Tapatalk
Click to expand...
Click to collapse
this is gonna be easy
scabs said:
Mine also just says LG-H870
The IMEI is hardware bound right?
Edit: Reason i'm asking is that i've tried the site and says "Unfortunately, your device(South Africa, (SOUTH AFRICA) )does not support unlocking the bootloader."
I wonder if installing the EU firmware will work?
Click to expand...
Click to collapse
Yes the IMEI is flashed somewhere in the hardware, and IMEI ranges are allocated by regions.
An EU firmware could work, but wouldn't change you IMEI.
Sorry for you, you'll have to wait for an unofficial way to unlock the bootloader if it is ever found...
Well, we EU LG G6 users may not get Quad-DAC, 64Gb of storage or wireless charging but we at least get this (which is better than anything).
I have a small problem I have a lot of android devices and their corresponding unlock codes in an excel sheet. So IMEI, Unlock Code
What I want to do is figure if its possible to script the unlock process. I have good dev skills but I've never done any android development. What is the most feasible way to do this? I currently plug in a sim card and manually unlock. The other thing I do if I don't have a simcard for samsung phones you can do #7465625*638*# then enter code. Would I have to write logic to say read the imei figure out the model number then send the appropriate code? Are there any code examples any where of how people unlock phones using bruteforcing? I don't know what interface I'm targeting to be able to unlock. Any help is appreciated.
Minimal amount of manual labor: insert sim if needed (some phones require only wifi connection to check if oem unlock is available, some do need sim though), enable development options, enable ADB. Even that could be automated with arduino and a wire on screen, if you need to unlock hundreds of devices.
After adb is enabled, you would have to write a script to reboot to fastboot, then parse output of 'fastboot getvar all '/ 'fastboot getvar imei' (tough luck if your device isn't reporting imei to fastboot - then you have to code more java/c), issue 'fastboot reboot' and using 'adb shell input' start the unlocking process.
Hi! My name is Bautista.
This is my first post well explained, I already asked this question before but I did not express myself well (I hope to do it correctly in this attempt)
My problem happens with my Samsung Galaxy A01 SM-A015M, Running on OneUI 2.0/Android 10 with 2gb of ram, a Snapdragon 439, the stock rom/firmware and 32GB of storage, from Argentina.
Things I tried so far, and didn't work for me:
Unlocking the bootloader by following the Gearallnews and Cyanogenmods guides to the letter.
When trying to unlock the bootloader with the guides on the aforementioned pages, when starting the device a sign should appear saying that the bootloader is unlocked, which did not appear.
The device started correctly in the process to configure the device the first time it is turned on, connect the wifi as the guides said. Followed by that I went to the developer options and the option "Oem unlock" was still activated and in blue (which should not happen, it should appear grayed) I heard that some Samsung devices with snapdragon processors had a bootloader that cannot be unlocked
Unlocking the bootloader using ADB AND Fastboot. (ADB detects my device fine, but fastboot doesn't detect it at all)
Using Fastboot from Windows 7, Windows 10, and Kali Linux.
Installing TWRP.
Use rooting apps. (the ones that appear on the XDA rooting page)
What I am going to with this thread, is:
Can my device's bootloader be unlocked? And if so, how?
If the bootloader cannot be unlocked, how can I root or install TWRP?
Please, if you don't understand something or need more information, let me know by replying to this thread or sending me a private message.
Look inside here.
jwoegerbauer said:
Look inside here.
Click to expand...
Click to collapse
it's the same as Gearallnews and Cyanogenmods guides, i already did that, it dont work
Like the original poster I also have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) Panama. I have gone through all the aforementioned procedure and the bootloader does not unlock. There is no bootloader unlock warning on reboot and the OEM Unlock in developer option does not grey out. Does the Snapdragon processor not allow bootloader unlock or is anyone aware of a solution. Thanks for any assistance.
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
jwoegerbauer said:
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
Click to expand...
Click to collapse
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
mullerh said:
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
Click to expand...
Click to collapse
Hi! Did you manage to find a way to unlock the bootloader?
I have not been able to unlock the bootloader on this SM-A015M/DS (Latin American) model with Snapdragon processor. I have done a lot of searching but found little info except articles stating Samsung had gone through some extra effort to secure their latest phones. That also means I can not root it. I was hoping to get some feedback from other who may have had a better experience,
have you tried using the twrp app to install twrp?
i had an old galaxy grand prime which was impossible to unlock, but the app worked without issues
the only thing i had to pay attention is to turn it off right before ir reboots after installing and then loading into recovery
letting the mobile startup without doing this overrieded the command to install twrp
Thanks for your response. It is my understanding (I could be wrong) that before TWRP can be installed the Bootloader needs to be unlocked. The older Samsung usually allowed the Bootloader to be unlocked even if there was difficulty in rooting them. It appears that some of the newer Samsung's with the Snapdragon processors have added an additional security feature called SecureBoot which blocks the Bootloader from being unlocked.
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
For what it's worth, when I flashed the firmware onto the phone in the first place, I had to enable the developer option manually- I did this by booting into download mode and then a long press on the volume up button when prompted by the menu. I don't see why this wouldn't work for other devices. There are youtube videos that explain in greater detail if you haven't tried this yet.
Newiser7 said:
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
Click to expand...
Click to collapse
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
jwoegerbauer said:
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
Click to expand...
Click to collapse
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
mullerh said:
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
Click to expand...
Click to collapse
You are right: I was mistaken.
Thank you for clarifying that the bootloader is still locked. But how can I unlock it? Odin will let me flash the files, but I keep getting AUTH errors when I try to flash magisk patched files to root the phone. I'm assuming this is because the bootloader preventing the files from transferring. Is there a way to unlock it using ADB without fastboot, or a way using Odin? It seems crazy that unlocking the bootloader is enabled but I am still unable to actually unlock it.
I have also tried the CROM Service app (couldn't get it to install on my phone, error 3003 with ADB install), as well as the bootloader unlock method where I boot into download mode, hold the volume up key, and unlock the bootloader that way. I have done the latter at least 5 times and the bootloader is still locked. Ridiculous.
This prop apparently only confirms that the phone supports being unlocked, not that it is actually unlocked.
adb shell "getprop ro.oem_unlock_supported"
Check a few others, also see the official docs.
sys.oem_unlock_allowed
androidboot.flash.locked (the docs say this, but I think Samsung uses something different)
ro.boot.flash.locked
ro.boot.other.locked
Maybe also check these:
ro.boot.verifiedbootstate
ro.boot.veritymode
The docs indicate that the verifiedbootstate should be orange if the bootloader is unlocked. I don't know much about it, though.
You can always use grep to search for any interesting values, like "lock" or "boot" or "flash":
adb shell getprop | grep lock
adb shell getprop | grep boot
adb shell getprop | grep flash
Maybe report any interesting values you have with and without OEM Unlock checked. Maybe someone smarter than us will find it useful.
I would really like to see an A01 root happen, it's such an affordable and accessible device for all sorts of things. Great as a backup device or for a project. You think someone would've released some goods for it by now. It's been out all year.
And for the 16GB model, it's absolutely terrible because Samsung eats up so much space, then has the nerve to remove the Adoptable Storage feature. So even if you get a fast SD card, you can't install apps on it. Other than that, it's a perfectly serviceable phone. I would think with root we could get Adoptable Storage working.
To summarize what has been previously stated the Samsung Galaxy A01, version SM-A015M/DS is the Latin American version of this cellphone. This cellphone has a Snapdragon processor. This version is very similar to the versions (also Snapdragon processors) used by some US Carriers. Many current versions of Samsung cellphones have an additional security feature called "SecureBoot" which blocks bootloader unlocking. Some say this features was added at the request of US Carriers
The Asian version of the A01 has a Exynos processor. It is my understanding that with these it is very easy to unlock the bootloader and root the phone using the usual conventional methods. The Asian variant unfortunately does not cover some of the wireless bands used in the US/Canada/Latin America.
I have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) for Panama.
My research indicates that there is not yet an available bootloader unlocking and easy root method for this (A01) phone. For some other current Samsung models there does appear to be a method of flashing certain custom ROMs without a bootloader unlock but they appear to come with problems which include loss of some cellphone functions and a reduction in the charged battery life. So it seems hardly worth it.
It also appears that it is current well known that all current Samsung phones with Snapdragon processors have not allowed bootloader unlocking and rooting due to the enhanced security feature.
At this time we can only complain and/or not buy any additional Samsung phones
Perhaps with time skillful developers will come up with a method to solve this problem with this inexpensive A01.
Please provide any new or updated info if you have it.
Any solution for rooting Galaxy A01 ?
I use A015f region SER (Russia) In Russia, too, the device is locked (bootloader) of course, give any solution
One thing I know is that a fellow SM-M015f, which is almost identical, which is with the same Snapdragon 439, except for the battery capacity and screen size and gigabytes of internal memory, successfully unlocks and gets Magisk root.
this phone actually has a fastboot mode, from recover mode select reboot to bootloader, it will boot to fastboot mode,but ive still been unsucessful in getting fastboot mode to work, devices manager reports device error,
I can start the unlock proccess.
But after it is done and the data is wipped,
It keeps locked.
Sad
Hi guys, how y'all doing?
I've been trying to unlock the bootloader of my phone a couple of months now and every single attempt is a failure. I've done all the steps right but, in the Motorola website I receive a message that my phone don't apply for unlocking the bootloader.
Anyone knows anything about this, if it can be bypassed somehow or if has anyway to contact Motorola to get any information about this issue.
Thanks in advance.
1Apokalypsis said:
Hi guys, how y'all doing?
I've been trying to unlock the bootloader of my phone a couple of months now and every single attempt is a failure. I've done all the steps right but, in the Motorola website I receive a message that my phone don't apply for unlocking the bootloader.
Anyone knows anything about this, if it can be bypassed somehow or if has anyway to contact Motorola to get any information about this issue.
Thanks in advance.
Click to expand...
Click to collapse
Well, I can think of a few reasons why you can't unlock your bootloader.
1. The most obvious one: you haven't enabled OEM unlocking under developer settings.
2. You're not using a retail device. Only retail devices can unlock BL AFAIK. Non-retail devices are those sold by carriers (AT&T, Verizon, whatever else).
3. Your bootloader is not unlockable, even if its retail.
The 1st problem is easy to solve and I won't discuss it.
The other two are stored as variables on your bootloader and can be checked with the "fastboot getvar [x]" command, where [x] is the variable name.
The variables of interest here are:
1. "ro.build.version.full" - this tells if device is retail or not. It should return something like "retail.en.US" or "retail.xx.XX", depends on region.
2. "cid" - I have no idea cid stands for, but I think it's related to bootloader type.
3. Be aware that I don't know if the 1st variable has the same name on all motorola devices. In case of doubt, use "fastboot getvar all" to list all variables, then you can check manually.
Nowadays, it's not common for Motorola devices to have locked cids. In Lollipop/Marshmallow days, some devices had that issue where it was retail but impossible to unlock due to cid. The un-unlockable cids should be the same for all devices but you'll have to research, I don't remember which is which anymore.
SUMMARY:
1. check the developer setting "Allow OEM unlocking". It's a switch. If it's off, turn it on and you'll be able to unlock the BL
2. If that doesn't work, check if your phone is a retail model. If not, you're out of luck.
3. If it is retail and you can't unlock it, you are either providing the wrong unlock code to fastboot, or you have an unlockable cid, in which case you're also out of luck.
[edit]
Forgot to mention this, if your device has a mediatek CPU/SoC, forget about it, they're impossible to unlock too.
[edit 2]
I found the cid list: https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809
freeZbies said:
Well, I can think of a few reasons why you can't unlock your bootloader.
1. The most obvious one: you haven't enabled OEM unlocking under developer settings.
2. You're not using a retail device. Only retail devices can unlock BL AFAIK. Non-retail devices are those sold by carriers (AT&T, Verizon, whatever else).
3. Your bootloader is not unlockable, even if its retail.
The 1st problem is easy to solve and I won't discuss it.
The other two are stored as variables on your bootloader and can be checked with the "fastboot getvar [x]" command, where [x] is the variable name.
The variables of interest here are:
1. "ro.build.version.full" - this tells if device is retail or not. It should return something like "retail.en.US" or "retail.xx.XX", depends on region.
2. "cid" - I have no idea cid stands for, but I think it's related to bootloader type.
3. Be aware that I don't know if the 1st variable has the same name on all motorola devices. In case of doubt, use "fastboot getvar all" to list all variables, then you can check manually.
Nowadays, it's not common for Motorola devices to have locked cids. In Lollipop/Marshmallow days, some devices had that issue where it was retail but impossible to unlock due to cid. The un-unlockable cids should be the same for all devices but you'll have to research, I don't remember which is which anymore.
SUMMARY:
1. check the developer setting "Allow OEM unlocking". It's a switch. If it's off, turn it on and you'll be able to unlock the BL
2. If that doesn't work, check if your phone is a retail model. If not, you're out of luck.
3. If it is retail and you can't unlock it, you are either providing the wrong unlock code to fastboot, or you have an unlockable cid, in which case you're also out of luck.
[edit]
Forgot to mention this, if your device has a mediatek CPU/SoC, forget about it, they're impossible to unlock too.
[edit 2]
I found the cid list: https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809
Click to expand...
Click to collapse
Thanks for all the info.
1. I liked that you mentioned the "OEM Unlocking" switch, but I'm not a total dummy, it's turned on lol.
2. I don't believe that my model is one of those sold by carriers, at least afaik.
3. I will try to get the variables and look it up, but I'm feeling that I'm out of luck already.
It's the Qualcomm version of the One Fusion+
1Apokalypsis said:
Thanks for all the info.
1. I liked that you mentioned the "OEM Unlocking" switch, but I'm not a total dummy, it's turned on lol.
2. I don't believe that my model is one of those sold by carriers, at least afaik.
3. I will try to get the variables and look it up, but I'm feeling that I'm out of luck already.
It's the Qualcomm version of the One Fusion+
Click to expand...
Click to collapse
If it's the qualcomm version and it doesn't unlock it must be bc it must be either bc it is not retail or cid. If you're using a retail phone and cid is unlockable then keep trying/check unlock code/try asking for it again, whatever, it should work.