Related
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.
I bought a Mediapad X1 3G version. It is a nice machine, albeit a bit too large as a phone - picture a large brick near your head,
Well, I emailed [email protected] to obtain the bootloader unlock code. I got the code so I would like to go ahead. But I ran into a very strange fastboot issue. When I issue the command "fastboot devices" -
? fastboot
That question mark is supposed to be some number. So this means the device is not recognized. Hence the unlock code does not work. Weirdly, commands such as "fastboot oem get-bootinfo" works, it shows the bootloader is locked. "Fastboot reboot" also works.
Anyone has any idea how I can solve this problem? Some driver issue? Thanks.
wxppro said:
I bought a Mediapad X1 3G version. It is a nice machine, albeit a bit too large as a phone - picture a large brick near your head,
Well, I emailed [email protected] to obtain the bootloader unlock code. I got the code so I would like to go ahead. But I ran into a very strange fastboot issue. When I issue the command "fastboot devices" -
? fastboot
That question mark is supposed to be some number. So this means the device is not recognized. Hence the unlock code does not work. Weirdly, commands such as "fastboot oem get-bootinfo" works, it shows the bootloader is locked. "Fastboot reboot" also works.
Anyone has any idea how I can solve this problem? Some driver issue? Thanks.
Click to expand...
Click to collapse
You just emailed them asking for bootloader unlock code? What information did you have to provide them?
Update: bootloader on my device was already unlocked
acuratlsfan said:
You just emailed them asking for bootloader unlock code? What information did you have to provide them?
Update: bootloader on my device was already unlocked
Click to expand...
Click to collapse
I just gave them the serial number, IMEI, MAC address, and model (7D-501U). They reply pretty quickly, a few hours.
Good that you have an unlocked bootloader - When you run the fastboot command, does it show a number for your device but not a question mark?
wxppro said:
I just gave them the serial number, IMEI, MAC address, and model (7D-501U). They reply pretty quickly, a few hours.
Good that you have an unlocked bootloader - When you run the fastboot command, does it show a number for your device but not a question mark?
Click to expand...
Click to collapse
i
I can't remember i it displayed a number or a " ? " . I updated to 4.4.2 earlier... and 4.4.2 has an updated fastboot.img. The way i know if because when I enter fastboot now it displays in green letters " DEVICE UNLOCKED " under the"...hold power down 10 sec...."
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
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
AndyYan said:
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
Click to expand...
Click to collapse
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
PsYk0n4uT said:
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
Click to expand...
Click to collapse
Try prepending 0s?
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
PsYk0n4uT said:
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
Click to expand...
Click to collapse
Tried adding zero on front and back of serial it just tells me invalid serial
PsYk0n4uT said:
Tried adding zero on front and back of serial it just tells me invalid serial
Click to expand...
Click to collapse
Chatting with OnePlus hasn't yielded anything so far
Just a tip, because in my infinite forgetfulness I wasted an hour last night trying to figure out why I was getting the error, fastboot could not open target HAL.
Remember that you must request the unlock code from fastboot, not fastbootd. Which is what you will boot into if you issue adb reboot fastboot.
So here's a quick step by step.
1.Enable usb debugging. 2. Connect your device and allow access for the computer. My device asks if I want it to charge or transfer files. Select transfer files/Android auto and then use adb start-server. May have to unplug the USB cable and reconnect. Select "always allow this device/PC".
3. Issue "adb devices" to make sure your connected.it should list your device by it's serial number. If not then try unplugging the device and revoke adb authorizations in dev options and toggle USB debugging off and back on, may even need to reboot the device to get it to connect after doing this.
4. If your device is listed under devices go ahead and issue "adb reboot fastboot"
5. Once rebooted issue "fastboot devices" and make sure the device is listed again.(If not listed make sure you have your driver's installed correctly and fastboot is installed correctly, may need to install Android SDK into same folder as fastboot)
6.You can select English or whatever language if you want but it doesn't seem necessary.You are in fastbootd mode you will see if you DO select a language.
So from here issue"fastboot reboot bootloader" device will reboot and you will have scrollable option at the top beginning with a big green START at the top. This is regular fastboot And where you wanna be to get your unlock code for submitting to Oppo for your unlock token.
7. Issue "fastboot oem get_unlock_code"
8. It should return the info you need, you will also need your IMEI number when submitting so be sure to copy that down.
you can copy and paste the unlock code into notepad or Word and delete out the extra stuff so your left with just the two lines of your unlock code as one single contiguous string of numbers.
8. Go to the link listed by OP and submit the required info. And wait for what seems like forever.
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
PsYk0n4uT said:
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
Click to expand...
Click to collapse
Simply "adb reboot bootloader". You won't need fastbootd until GSIs (which I already did ofc).
Thanks, definitely a quicker way to get to fastboot. I guess I wasn't sure if you could reboot directly. Seems maybe I was confusing an older device where you had to reboot to fastboot then "fastboot reboot fastboot" to get to fastbootd for a whole different reason.
This one goes directly to fastbootd when you "adb reboot fastboot"
Nice catch.
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
I'm not really sure to be honest, this is my first OnePlus device and just trying to contribute anything I can to get the N20 section up and going as I make progress with the device.
Just a quick search though turns up this and maybe it could be of use if you can still access the bootloader.
the current image(boot/recovery) have been destroyed
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip. After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g...
forum.xda-developers.com
Someone mentions extracting the boot.img from stock image and flashing it. I would imagine it should work for you if the stock firmware can be found and circumstances are similar. Maybe at least a start. Wish I could be of more help, maybe someone else can chime in that knows more.
Try Linux, maybe a live dist. if your on a windows machine that won't recognize it just to get it into a state that you can work with it again.
Just an idea, I don't want to steer you wrong as i still have a lot to learn
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsettinghav
Click to expand...
Click to collapse
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
Click to expand...
Click to collapse
I want to try and help but I'm so new it's sketchy I don't want to say something and get bashed
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Fyi according to a recently made friend who also had the 7 digit serial issue, they were told by OnePlus their dev team is working on an OTA update that will resolve the serial number issues. I'm not sure how that's going to work but I saw the email between them and Oppo support
I guess this must be a widespread issue that they feel is cheaper to invest the amount of money it takes for r&d to come up with a fix than it was to replace a few devices or attempt to do remote repairs.
But this also makes me wonder what avenue they will take to correct the issue.
Also I wonder if someone with the right skillset could gather enough bootloader unlock codes along with the unlock tokens, serial, IMEI, pcba etc.. maybe the algorithm their using to generate the codes could be broken. I'm no crypto expert or math genius either, but if we have the variables to the equation minus one but have the answer, isn't this pretty simple almost pre-algebra?
I mean I guess their not worried about enough people being brave enough to give out sensitive info like that. But maybe Im just ignorant of the complexity of these algorithms.
64 digit key on one end
T-Mobile bought sprint and they have T-Mobile sims no. But I understand that sprint is still a somewhat seperate company (tried to buy a T-Mobile phone and it would not activate on my sprint account. So I bought this from the sprint side of the T-Mobile site so I knew it would work but I assume this is a sprint phone and not a T-Mobile phone so this method would not work.
Can anyone confirm this?
PsYk0n4uT said:
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Click to expand...
Click to collapse
okay peep theres a way i put my oneplus into efu mode, hold both vol up and down then put usb c in continue to hold u should hear PC recognize it
So, before i do it, would deleting the modemst1/modemst2 partitions still let me bypass the t-mobile sim lock and let me unlock the phone like it did on the old oneplus phones?
Flashed a patched boot.img and lost modems. Anyone willing to post the modems? Are they device specific like a device partition?
Sim locked and trying to recover. No radios are working
My phone has imei 0, but I passed it to the cricket system since it originally comes from there but RSA put another rom that isn't it, it still turned on but without imei. I tried to pass a cricket by command and it worked fine but now it stays in fastboot, the oem never let me unlock it but the code to unlock bootloader if I have it, someone please help me
run "fastboot getvar all" (without the quotes) and head over to Telegram channel "Lolinet (English Only)" with that info and post it there and ask to get some help, explaining the issue in detail. The admins there know their stuff and would be the best bet to help you solve your problem.