Hi, recently I realized that my device has the bootloader locked and I cannot flash the firmware through Fastboot Flash Mode (Secure). When I try to unlock it taking in mind the Motorola site instructions and entering the fastboot oem get_unlock_data command it throws me this error:
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.040s]
finished. total time: 0.041s
I lost my IMEI and I don't know if that's interfering when trying to unlock bootloader. Can someone please tell me what's happening?
Thx for reading.
[CLOSED]
Caney said:
Hi, recently I realized that my device has the bootloader locked and I cannot flash the firmware through Fastboot Flash Mode (Secure). When I try to unlock it taking in mind the Motorola site instructions and entering the fastboot oem get_unlock_data command it throws me this error:
Click to expand...
Click to collapse
Please do NOT create duplicate threads.
Please read the Forum Rules.
This one applies here:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Related
Hi guys,
IMPORTANT ***
- THIS TUTORIAL IS ONLY FOR PHONES THAT HAS BEEN UPGRADED TO ANDROID 4.4.4 ONLY DO NOT FLASH IN ANDROID RUNNING 4.4.2 -
I was trying to unlock the bootloader of my Moto G from Boost;
I completed the process according to motorola's website .
And at the moment of running the code | fastboot oem unlock [UNIQUE DEVICE 20 DIGITS KEY] | the result was | "Password Incorrect" | : that was because I had upgraded the Android Version 4.4.2 to 4.4.4 before unlocking the bootloader, There was no way how to fix it. I last the entire day looking for a solution and at the end of the day I found this tutorial provided by Motorola.
AND IT DID WORK FOR ME
Here you have all you need to fix the "PASSWORD INCORRECT" ISSUE:
Download the .zip file on this link
https://forums.motorola.com/files/51c3cbf839/G_4.4.4.BL_Fix.zip
Extract it and you will find two folders, select the one that say | G_4.4.4.BL_Fix | inside you will find different Word files, select the one called READMEFIRST.rtf |That's the motorola tutorial for the Password Incorrect issue|
BEFORE FOLLOWING THAT TUTORIAL FROM MOTOROLA
Make sure you have the files motoboot.img and motoboot_41.5_testdrive.img into the same directory that you're running the adb codes [ in my case it was Platform Tools ]
and as the tutorial says it might give errors as is not identifying the password as correct but just ignore them.
:good: :good: Good Luck, :good: :good:
Google + Irandis Ditren
GitHub Irandisdev
The file you need to download and extract is attached to this thread.
MOTOROLA TUTORIAL FOR THE BOOTLOADER UNLOCK:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
FILE FOR THE "PASSWORD INCORRECT" ISSUE:
Hi, this is really not the correct forum to post this. I'm going to ask a moderator to move it to, http://forum.xda-developers.com/moto-g/general
jd1639 said:
Hi, this is really not the correct forum to post this. I'm going to ask a moderator to move it to, http://forum.xda-developers.com/moto-g/general
Click to expand...
Click to collapse
Thanks :good:
guys plz help me how can i use this im stuck on Password incorrect
plz help me
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
Thread closed
Hello, anyone can help me with this error? "your device is corrupt and cannot be trusted and may not work properly." This is after I updated my phone from Oreo to Pie.
I tried to follow the steps from an XDA forum (https://forum.xda-developers.com/asu...upted-t3937991), When I checked the Verity Mode settings using the command fastboot oem device-info I see that it is set to FALSE.
But when I tried to run the command : adb reboot "dm-verity enforcing" or fastboot reboot "dm-verity enforcing" I am getting an error message saying : fastboot: usage: unknown reboot target dm-verity enforcing
I attached a screenshot of the error message.. I am not sure what are the next steps for me.. I need some help please...
[email protected] said:
Hello, anyone can help me with this error? "your device is corrupt and cannot be trusted and may not work properly." This is after I updated my phone from Oreo to Pie.
I tried to follow the steps from an XDA forum (https://forum.xda-developers.com/asu...upted-t3937991), When I checked the Verity Mode settings using the command fastboot oem device-info I see that it is set to FALSE.
But when I tried to run the command : adb reboot "dm-verity enforcing" or fastboot reboot "dm-verity enforcing" I am getting an error message saying : fastboot: usage: unknown reboot target dm-verity enforcing
I attached a screenshot of the error message.. I am not sure what are the next steps for me.. I need some help please...
Click to expand...
Click to collapse
Instead of opening another thread you should've posted this in the thread you followed. It'll be much more helpful. Also try using USB 2.0 port instead of 3.0 and with the latest drivers.
@[email protected] THREAD CLOSED! @ all interested in the subject, please follow this already existing thread, where the OP posted before this thread was created and where the OP got his problem solved.
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse
Please help
I wiped all the data with TWRP and i reboot mobile without installing OS , after that it'll shows black screen, But it is connecting to PC , I checked in command window it's working.. And i tried Flashing 334 stock ROM though ADB , it's done but always showing light black screen..
please get out this situation..
thanks in advance
Same happened with me and wait for the solution
helpp plzz
sharathcherry1699 said:
Please help
I wiped all the data with TWRP and i reboot mobile without installing OS , after that it'll shows black screen, But it is connecting to PC , I checked in command window it's working.. And i tried Flashing 334 stock ROM though ADB , it's done but always showing light black screen..
please get out this situation..
thanks in advance
Click to expand...
Click to collapse
THREAD CLOSED as a subject matter related thread already exists as you well know because you've posted there before you created this thread: https://forum.xda-developers.com/asus-zenfone-max-pro-m1/help/problem-dead-phone-black-screen-t4075571
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse
So, my HTC U Ultra got stuck in bootloop just 3 days after warranty ended(tough luck level : 100).
My phone runs on everything stock and no root.
I press all the buttons when powered off and it goes into bootloader mode. It displays options to boot into recovery mode, boot into download mode and power down, all of which(except power down) gets device into bootloop again.
THE PRIORITY OF GOALS IS : DATA RECOVERY > PHONE BOOTING AND WORKING PROPERLY AGAIN
I did a little research and figured out some sort of procedure by putting bits and pieces together :
1. Download ADB/Fastboot toolkit || universal driver from koush github // I have HTC Sync manager installed as well || twrp custom recovery image for htc u ultra || new ruu from htc support for rom update.
2. Now I put my phone into fastboot mode (since it doesn't show up on adb devices), connect to pc using usb.
3. I type in cmd : "fastboot devices" --> My device shows up there --> Again in cmd : "fastboot boot recovery mytwrp.img" --> the twrp boots into my phone
I was able to put this many steps together and after the last step, i have an abstract idea of what to do :
Enable USB Debugging using twrp recovery --> Use ADB Pull Command to get my all my data from phone to pc --> Use adb wipe the old Firmware (Not sure which command) --> Use adb again to flash new RUU (again not sure how, I've got an .exe file as RUU || should I get it in zip or img or any other format ? || Please help on this too) --> Finally Boot and hopefully everything turns out smooth and secure.
CAN YOU EXPERTS HELP ME TO PUT TOGETHER REMAINING STEPS (AND MODIFY ERRORS, IF ANY, OF EXISTING STEPS ) OF THIS PROCEDURE...???
noobie12112 said:
...
Click to expand...
Click to collapse
@noobie12112 THREAD CLOSED as duplicate of https://forum.xda-developers.com/u-ultra/help/htc-ultra-stuck-bootloop-experts-t4180387
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse