Related
UPDATE: I was on XDA Portal! http://www.xda-developers.com/android/bypass-htc-server-problems-when-unlocking-bootloader/
Hey guys,
So basically I spent two hours checking trying to unlock my HTC One X's bootloader a few days back.
I mean seriously? Two hours to unlock my bootloader? That's utter bull. HTCdev has the worst bootloader unlock servers ever, mostly because server keeps overloading.
I found several fixes if you have this error when you open the website on Google Chrome, but these aren't really fixes that fix the server, these are temporary bypasses if you want to get your bootloader unlocked immediately.
You would want to follow this if you constantly get these errors by using Google Chrome:
1. "The connection to htcdev.com was interrupted."
2. "This webpage is not available"
3. After logging in to the website, you select "All Other Supported Models" and press Begin Unlock, no popup window comes up asking you to verify ToS and verifying that you will void warranty.
4. *without logging into HTCdev* You click Begin Unlock and you get a popup to login, after login you get an error "This webpage is not available"
To bypass most of these problems, follow these steps before proceeding:
1. Login to the website and make sure you get to the page where you can see "Welcome XXXXXXXXX Logout Account" on top of the window.
2. *OPTIONAL TO TEST* Try selecting All Other Supported Models from the dropdown box and click Begin Bootloader Unlock, if this fails and does not show a popup after 2-3 minutes, refresh and do the same except click the button two more times. If this fails, proceed onwards to step 3.
3. Make sure you have Fastboot, HTC Sync and Java installed on your computer.
4. Put your phone in Fastboot mode, do this command in the fastboot cmd to get your code: fastboot oem get_identifier_token
{
"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"
}
Right Click > Mark > highlight the block of text > Right click to copy to the code
5. Make sure you are logged in, then proceed to this site: http://htcdev.com/bootloader/unlock-instructions, when navigating through the pages, you get the above Chrome errors, just do one or two refreshes until you see something on your screen and not a Google Chrome error. Navigate to Step 10, http://htcdev.com/bootloader/unlock-instructions/page-3
6. Paste in the code and immediately click Submit, if you get a Google Chrome error, go back and Submit again. Repeat until you see the HTC success screen when you unlock your bootloader, telling you to check your email. If you get an error about your code, recopy your code and paste into the box.
7. Check your email, download the Unlock.bin into your Fastboot folder and open your Fastboot cmd prompt, run this command to unlock your phone: fastboot flash unlocktoken Unlock_code.bin
8. Follow on-screen instructions to unlock your bootloader.
9. Flash CWM recovery by Koush: http://forum.xda-developers.com/showthread.php?t=1594819
Use this command to flash the recovery onto your phone: fastboot flash recovery nameofrecovery.img
For example: fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img.img
10. Smile, you unlocked your phone's bootloader
Huh~ the problems you faced simply cause by the high serverload on HTCDev. Perhaps caused by those who are waiting for Desire and Rhyme RUUs..
"HTCdev has the worst bootloader unlock servers ever." -- can't give any comments on this because there no others available.
Need to clarify HTC is the first to offer official bootloader unlock though not s-off. Currently already made it to available for all their android devices, hardworks. Who you are comparing it with? Motorola's single device unlock site?
and why you need java for bootloader unlocking process.
the unlocked process is already done on step 8 actually.
HebeGuess said:
Huh~ the problems you faced simply cause by the high serverload on HTCDev. Perhaps caused by those who are waiting for Desire and Rhyme RUUs..
"HTCdev has the worst bootloader unlock servers ever." -- can't give any comments on this because there no others available.
Need to clarify HTC is the first to offer official bootloader unlock though not s-off. Currently already made it to available for all their android devices, hardworks. Who you are comparing it with? Motorola's single device unlock site?
and why you need java for bootloader unlocking process.
the unlocked process is already done on step 8 actually.
Click to expand...
Click to collapse
Please read the title. Obviously it is high server load or just crappy server upload speeds. I have waited weeks and weeks for it to load fast, if you try to go on HTCdev again right now, it is extremely slow and would constantly hang.
Think about it logically, HTC is such a big company, and plus we shouldn't have extremely high network ping since the HQ is just an hour flight away from where I live. It's not hardwork if people want to unlock their bootloaders and they purposely lock it down, they're just pissing people off, intentionally wanting to record down who voided their warranty. Look at all the Samsung users, their phones come with a pre-unlocked bootloader and they're doing much better than HTC.
They are in fact the first to do this kind of unlock, no other company is doing it the same way, which means it is the worst way to do it.
If you can be bothered, please take a look at HTCdev's twitter page. There are loads of people complaining about their bootloader unlock page, and HTCdev claiming that they fixed it, but its an ongoing problem and I have never ever had such a hassle when trying to root your phone.
Anyways this is a technique I would follow if you have the problems stated above, just wanting to help people, not start flames.
Actually i was on the site regulary basis recents day for Desire S's RUU..
But bid samsung shipped with pre-unlocked bootloader? No, please dont includes nexus flagship devices and the funny verizon GS3 dev edition that wanting people to paid more..
And I have no intents to pouring flames on this..
We're on the International variant of the HTC One X forum here, and the major population here are from everywhere around the world, not just US.
Samsung releases pre-unlocked versions of their International devices, I never said anything about US carrier released ones.
Nexus flagship devices are controlled by Google, if Google says lock the bootloader, they listen, but if its a Samsung Galaxy S series device, Google can't force them to lock the Galaxy line's bootloader.
oh thank god!!! finally! =) Thank you thank you thank you!!! =) I'd been wrestling with their servers off and on for about FOUR hours lol. This totally worked
Hi,
A better approach will be this way:
1. with your "My Device Identifier Token" ready (have it in a notepad)
2. use google chrome and launch 5 tabs
3. navigate all to http://www.htcdev.com/bootloader/unlock-instructions/page-3
4. login to each of the 5 tabs
5.scroll all the way down to the part to input your token for all 5 tabs
6. copy your token from the notepad stated earlier.
7. paste and submit into all 5 tabs by using the short cut Ctrl+Tab
8. At least one will be submitted and you will received an email even though all the page shows you login error.
problem with bootloader
after flashing unloctoken from cmd by fastboot flash unlocktoken Unlock_code.bin
i m not able to get any flash screen on my htc evo 3d gsm i m on
hboot 1.48.0005
build no 1.14.0.0 cl95535-keys
i m on ginger bread not able to update to ics.
default ics update is not also coming on my mobile
i m tired of doing it i hv done whole process like 100 times but splash screen dsnt appears on my mobile
i htc driver+java+htcsync+adt-bundle-windows
is their any other method to unlock my htc evo 3d gsm then htcdev pls help me i m trying this from last 1 year not no sucess yet
haroujf said:
Hi,
A better approach will be this way:
1. with your "My Device Identifier Token" ready (have it in a notepad)
2. use google chrome and launch 5 tabs
3. navigate all to http://www.htcdev.com/bootloader/unlock-instructions/page-3
4. login to each of the 5 tabs
5.scroll all the way down to the part to input your token for all 5 tabs
6. copy your token from the notepad stated earlier.
7. paste and submit into all 5 tabs by using the short cut Ctrl+Tab
8. At least one will be submitted and you will received an email even though all the page shows you login error.
Click to expand...
Click to collapse
+1
The guide shown here (OP) is useless, this is what everybody does anyway.
You've just made a massive guide, basically saying just keep refreshing and you'll pass through soon enough.
Using the method you described, it could still take hours...
Thank you so much nicolaschum! Your introduction works perfect and I've just unclocked my father's HTC VT328t. It is contract model of a carrier China Mobile, with lot of useless carrier apps and worst part is all google apps and frameworks are removed.
I've been stuck in HTC legal term page for near two hours and unable to get into Unlock Instructions page (step 1 - 4) and was about to give it up. Fortunately I found this thread and with your instruction I've bypassed them and got final Token submitted successful message in only 4 tries within 5 minutes. Now I can get google apps installed on his mobile :laugh:
Thanks!
Thanks for this
Sent from my HTC One X using xda app-developers app
nicholaschum said:
Hey guys,
So basically I spent two hours checking trying to unlock my HTC One X's bootloader a few days back.
I mean seriously? Two hours to unlock my bootloader? That's utter bull****. HTCdev has the worst bootloader unlock servers ever, mostly because server keeps overloading.
I found several fixes if you have this error when you open the website on Google Chrome, but these aren't really fixes that fix the server, these are temporary bypasses if you want to get your bootloader unlocked immediately.
You would want to follow this if you constantly get these errors by using Google Chrome:
1. "The connection to htcdev.com was interrupted."
2. "This webpage is not available"
3. After logging in to the website, you select "All Other Supported Models" and press Begin Unlock, no popup window comes up asking you to verify ToS and verifying that you will void warranty.
4. *without logging into HTCdev* You click Begin Unlock and you get a popup to login, after login you get an error "This webpage is not available"
To bypass most of these problems, follow these steps before proceeding:
1. Login to the website and make sure you get to the page where you can see "Welcome XXXXXXXXX Logout Account" on top of the window.
2. *OPTIONAL TO TEST* Try selecting All Other Supported Models from the dropdown box and click Begin Bootloader Unlock, if this fails and does not show a popup after 2-3 minutes, refresh and do the same except click the button two more times. If this fails, proceed onwards to step 3.
3. Make sure you have Fastboot, HTC Sync and Java installed on your computer.
4. Put your phone in Fastboot mode, do this command in the fastboot cmd to get your code: fastboot oem get_identifier_token
Right Click > Mark > highlight the block of text > Right click to copy to the code
5. Make sure you are logged in, then proceed to this site: http://htcdev.com/bootloader/unlock-instructions, when navigating through the pages, you get the above Chrome errors, just do one or two refreshes until you see something on your screen and not a Google Chrome error. Navigate to Step 10, http://htcdev.com/bootloader/unlock-instructions/page-3
6. Paste in the code and immediately click Submit, if you get a Google Chrome error, go back and Submit again. Repeat until you see the HTC success screen when you unlock your bootloader, telling you to check your email. If you get an error about your code, recopy your code and paste into the box.
7. Check your email, download the Unlock.bin into your Fastboot folder and open your Fastboot cmd prompt, run this command to unlock your phone: fastboot flash unlocktoken Unlock_code.bin
8. Follow on-screen instructions to unlock your bootloader.
9. Flash CWM recovery by Koush: http://forum.xda-developers.com/showthread.php?t=1594819
Use this command to flash the recovery onto your phone: fastboot flash recovery nameofrecovery.img
For example: fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img.img
10. Smile, you unlocked your phone's bootloader
Click to expand...
Click to collapse
Helped me unlock an HTC Eris, thank you. Was annoyed with the long wait and sluggish website.
Thanks for the help, but I'm stuck at submitting token..
Now its getting bad..i dont know why htc seem doesnt care about this.
Really really bad
http://www.isitdownrightnow.com/htcdev.com.html
Re: [FIX] Unlocking Bootloader when HTCdev site is crashing/semi-down [SERVER OVERLOA
Everyone, I had to use a browser other than Chrome. Safari had much more success, even better than IE. Still took a couple of reloads o finish.
Sent from my SGH-T959 using xda app-developers app
2 day trying.....htc sucks
3 day trying...same..sometimes its past till last but at the end ..error 173...
Wilks3y said:
+1
The guide shown here (OP) is useless, this is what everybody does anyway.
You've just made a massive guide, basically saying just keep refreshing and you'll pass through soon enough.
Using the method you described, it could still take hours...
Click to expand...
Click to collapse
Yes if everyone does this then why would anyone have any errors? I have done this on more than 15 HTC One X devices, so I'm pretty sure my guide is useful for me at least. I could even say it's failproof if done correctly.
I even tried his guide you +1'd, but all my tabs did not load, however that is just a smaller condensed method of what I did, that method would still work and is identical to the process of my guide, as it still loads multiple pages anyways, but you can't say a Samsung Galaxy S II is useless compared to the Samsung Galaxy S III because the S II has outdated or a different architecture compared to the S III. Without an S II invented you won't get an S III, so without a guide like this, there would still be people running around yelling how HTC servers should be fixed and never actually getting a fix, and there would not be a compressed version of this guide.
day 3 for me..ihve had multiple tabs open, no dice
HARDLOCKING YOUR DEVICE:
Hardlocked means your device will be unable to accept one of “working unlocking codes” as you are out of attempts. Depending on the manufacturer of your device you may have 3-10 tries.Now Mobile put Hard Locke does not accept any code where I bought more than one server and the same code sends me what is the solution Mobile works with only 3 and I want his way to open it?Or remove hard rock?Or any tool unlock htc form USB cable? pls Any idea or help on this problem
I have searched but couldn't find anyone with the exact same problem as mine.
This is the message I got from HTCDev.com
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 173.
Error Reason: Check Rule Fail with exception.
I have all the requirements (HTC Drivers, adb and fastboot files, JRE) and I am 100% sure I copied the code correctly as I have helped friends unlock their HTC phones before.
Also its definitely not the carrier disallowing me to unlock.
Can anyone help me figure out what's wrong here?
Servers down !?
http://www.isitdownrightnow.com/htcdev.com.html
More info here
Hey everyone as i mention above have using the device abot a week more, since i get this devices i also used another Xiaomi devices no need to mentions all of them here, so basically it's not a new things for me unlocking, applying, and executes the UBL. day one i use the existing MID to loggin in the micloud/miaccount on my 5s (i've two old existing MID)both of them has permissions to UBL already.
Activating developer mode through setting, and heads to that options, activating debug, oem unlock allowance, and last step binding the MID in miunlock status, day one after many tries its still failed to bind with tost messages said "failed to verify, wait a minute or two, please try again", ok i leaves that for a next day, assuming that i might to hurry doing that. Next two days still gimme the same error, trying to find some post and thread to solve and try some of tutorial to fix that.
signing out the MID, and factory reset the devices setting up as new without signing MID on the 1s settup, log in in MID (Two MID) through chrome and cleaning all devices connected and leaves it empty (not even one devices left connected to that MID), entering MID on the setting app on my devices (try using email,phone number, just the ID) and activating the developer mode and trying to bind the MID in miunlock status , Crap its still gimme the same error (trying winth cellular/wifi).
Okay some told me to create fresh and new account with new number and applying unlock done 24X1 i receved messages granted to unlock. reseting device to factory setting, signing a new and fresh MID and heads to miunlock status trying to BIND the MID again its failed with the same error message.
I do have flashing the devices through testpoint EDL mode to make sure that i'm on official Miui not a fake one, (try both stable,dev, CN and Global) still no luck.. Please can somene here help and share me another guides, thanks
Please ask this directly in the English Miui forum. There you can also check if you still have the unlock permission.
Sometimes their servers are overloaded and it can take some days until they work fine again.
patoberli said:
Please ask this directly in the English Miui forum. There you can also check if you still have the unlock permission.
Sometimes their servers are overloaded and it can take some days until they work fine again.
Click to expand...
Click to collapse
Did it, no attentions there, contacting mi global service through email 4times without solutions yet, and now seems they ignoring my email ni respons at all, F"#£K!!!
I don't know if you need to get a fresh unlock permission for your phone. If you do, then this can take 2 weeks after you applied for it.
I am following the instructions from motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
I've downloaded Motorola drivers for Mac, as well as platform-tools. I am booting the phone to booloader but then a weird barcode shows up: imgur.com/a/8sT2lds
Any idea how to make progress from there? By the way my phone model is XT2029-2
Nycticorax said:
I am following the instructions from motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
I've downloaded Motorola drivers for Mac, as well as platform-tools. I am booting the phone to booloader but then a weird barcode shows up: imgur.com/a/8sT2lds
Any idea how to make progress from there? By the way my phone model is XT2029-2
Click to expand...
Click to collapse
Would like to know it too. Passed some days searching the web for a answer, and got none. The only thing I get when scanning the barcode is a number that AFAIK doesn't match any serial nor anything at all in the phone; just a number from what I can tell. Using fastboot oem get_unlock_data doens't work at all too, I just get a "command unknown" error returned from fastboot. Tried different drivers, none seemed to work, and the only ones that did, gave me the barcode and the fastboot error when trying to unlock. A very weird error, this one; fastboot devices work just fine, fastboot getvar all too, so it really doesn't seem like a fastboot or driver issue. My last try was this article (https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/) to see if I could get a list of the phones OEM commands and figure out how to unlock it. Tried to extract the bootloader from the firmware I downloaded online, using a tool I found on the forum, but no success until now. Will try to root the phone and extract it as it is shown in the tutorial to see if I can get more lucky. I saw somewhere that there's an app called sunshine that was used to unlock some older models, maybe you wanna try that too. I won't, because it's paid and I don't have the money to pay for it . Anyway, I'll try the bootloader extracting and see how that works, and depending on the output, maybe I'll post a tutorial here.
Def4lt_ said:
Would like to know it too. Passed some days searching the web for a answer, and got none. The only thing I get when scanning the barcode is a number that AFAIK doesn't match any serial nor anything at all in the phone; just a number from what I can tell. Using fastboot oem get_unlock_data doens't work at all too, I just get a "command unknown" error returned from fastboot. Tried different drivers, none seemed to work, and the only ones that did, gave me the barcode and the fastboot error when trying to unlock. A very weird error, this one; fastboot devices work just fine, fastboot getvar all too, so it really doesn't seem like a fastboot or driver issue. My last try was this article (https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/) to see if I could get a list of the phones OEM commands and figure out how to unlock it. Tried to extract the bootloader from the firmware I downloaded online, using a tool I found on the forum, but no success until now. Will try to root the phone and extract it as it is shown in the tutorial to see if I can get more lucky. I saw somewhere that there's an app called sunshine that was used to unlock some older models, maybe you wanna try that too. I won't, because it's paid and I don't have the money to pay for it . Anyway, I'll try the bootloader extracting and see how that works, and depending on the output, maybe I'll post a tutorial here.
Click to expand...
Click to collapse
Ok so after analysis the barcode just the IMEI associated with my SIM card's slot. (This phone has two SIM card slots.) Nothing interesting about it, I think.
Also it seems that Motorola does not support unlocking this bootloader as it does for other phones; in fact "motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a" is just a hub for any phone listed at "support.motorola.com/us/en/solution/MS87215", and this one is not on the list. I am not aware of any way to unlock the bootloader in these circumstances.
Please let me / us know if you are more successful than me. For now I will consider this phone not rootable via this method.
PS: The furthest I've been: `fastboot oem get_unlock_data` returns a blank line as if the mobile was working. No error message or anything.
PPS: What do you mean by "extracting the bootloader"? What rooting method is extracting the bootloader part of?
The official list of devices that can be unlocked has never been complete.
Usually all moto models can be unlocked, except Carrier branded devices or those on Amazon software channel.
Those getting the barcode screen, is that from
Pressing the volume down button and power on, or
adb reboot bootloader
?
Sent from my ali using XDA Labs
Nycticorax said:
Ok so after analysis the barcode just the IMEI associated with my SIM card's slot. (This phone has two SIM card slots.) Nothing interesting about it, I think.
Also it seems that Motorola does not support unlocking this bootloader as it does for other phones; in fact "motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a" is just a hub for any phone listed at "support.motorola.com/us/en/solution/MS87215", and this one is not on the list. I am not aware of any way to unlock the bootloader in these circumstances.
Please let me / us know if you are more successful than me. For now I will consider this phone not rootable via this method.
PS: The furthest I've been: `fastboot oem get_unlock_data` returns a blank line as if the mobile was working. No error message or anything.
PPS: What do you mean by "extracting the bootloader"? What rooting method is extracting the bootloader part of?
Click to expand...
Click to collapse
That's weird. My barcode number doesn't seem to match any numbers at all, serial, IMEI, nothing. I'll double check it to see if I have missed something. Never got this blank line, would be happy if you shared how you achieved it, maybe there could be some insight I can get from the process. Answering the question about the bootloader, the extraction isn't a part of a rooting method, it's only something I'm trying in order to get the list of oem fastboot commands of the phone. Those are manufacturer-specific, aren't listed anywhere, and differ from model to model. The method I'm using is the one from the article I pointed in my previous answer. Anyway, if it takes me anywhere, I'll bring an update about it with details.
---------- Post added at 23:36 ---------- Previous post was at 23:04 ----------
sd_shadow said:
The official list of devices that can be unlocked has never been complete.
Usually all moto models can be unlocked, except Carrier branded devices or those on Amazon software channel.
Those getting the barcode screen, is that from
Pressing the volume down button and power on, or
adb reboot bootloader
?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
The barcode is from entering the bootloader. Any method that gets you there shows it. At first I thought it was a driver-related bug, but after some experimentation it seems like whenever the device is recognized by fastboot, it shows this barcode; So it appears to be a bootloader-related thing (I never saw nothing like it, so just guessing for now). Also tried the method from the Motorola website, and I really wish it had worked as expected, but what it seems to me is that MediaTek devices are a pain in the ass in general for this kind of thing. The device doesn't recognizes the oem commands sent through fastboot as valid (And yes, OEM Unlocking is properly enabled under Developer Settings). Here's a screenshot from a powershell session showing the results of trying the commands. Notice how the device is correctly recognized by both adb and fastboot, only the unlocking commands doesn't work: https://pasteboard.co/JnW4cvK.png
sd_shadow said:
The official list of devices that can be unlocked has never been complete.
Usually all moto models can be unlocked, except Carrier branded devices or those on Amazon software channel.
Those getting the barcode screen, is that from
Pressing the volume down button and power on, or
adb reboot bootloader
?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
In my case the barcode shows up whenever I reach fastboot, whether via booting with [vol up + power] and then selecting fastboot, or via adb reboot bootloader. I've tried several barcode recognition apps and 2 out of 3 confirm it's my IMEI.
Nycticorax said:
In my case the barcode shows up whenever I reach fastboot, whether via booting with [vol up + power] and then selecting fastboot, or via adb reboot bootloader. I've tried several barcode recognition apps and 2 out of 3 confirm it's my IMEI.
Click to expand...
Click to collapse
Did you try
Code:
fastboot flashing unlock_critical
according to this thread... it is for e6 plus. May be it works with e6 play.
https://old.reddit.com/r/androidroot/comments/f6c5k5/unlock_bootloader_moto_e6_plus/fupyalw/
No,
Code:
fastboot flashing unlock critical
does not work. And no, we shouldn't assume that a method meant for the e6 plus works for the e6 play.
Phone in red state not able to change settings
I have struggled with the same problems as above. I am not able to get into the developer mode as I only have access to the recovery screen. Anybody who knows how to do that from the recovery screen - perhaps using terminal?
I have been able to enter into the phone by adb sideload filename.zip and the phone acknowledged connection, but the upload failed, probably due to I am not able to unlock the phone from the red state/Android Recovery. It is running bali-reteu/bali9/POAS29.550-81-1/
glensbo said:
I have struggled with the same problems as above. I am not able to get into the developer mode as I only have access to the recovery screen. Anybody who knows how to do that from the recovery screen - perhaps using terminal?
I have been able to enter into the phone by adb sideload filename.zip and the phone acknowledged connection, but the upload failed, probably due to I am not able to unlock the phone from the red state/Android Recovery. It is running bali-reteu/bali9/POAS29.550-81-1/
Click to expand...
Click to collapse
It is not clear to me what you did exactly. The step where we -- the others participants to this post and I -- are stuck is [2] here below:
boot to fastboot by running `adb reboot bootloader` from a command line on a connected and turned on device
get the OEM unlock code by doing `fastboot oem get_unlock_data` from a connected device under the fastboot interface
exchange the unlock code on the motorola support site and input that code to confirm bootloader unlock
glensbo said:
I have struggled with the same problems as above. I am not able to get into the developer mode as I only have access to the recovery screen. Anybody who knows how to do that from the recovery screen - perhaps using terminal?
I have been able to enter into the phone by adb sideload filename.zip and the phone acknowledged connection, but the upload failed, probably due to I am not able to unlock the phone from the red state/Android Recovery. It is running bali-reteu/bali9/POAS29.550-81-1/
Click to expand...
Click to collapse
Got a little further as the code:
#fastboot flash unlock_critical Filename.zip#
the phone replied - Transferring and Transmission OK .... time etc
But I got an error sadly to say:
Failed (remote: not allowed in locked state) so I'm back to basics as I cannot open the state from the recovery mode (as of yet)
glensbo said:
Got a little further as the code:
#fastboot flash unlock_critical Filename.zip#
the phone replied - Transferring and Transmission OK .... time etc
But I got an error sadly to say:
Failed (remote: not allowed in locked state) so I'm back to basics as I cannot open the state from the recovery mode (as of yet)
Click to expand...
Click to collapse
Okay, I would like to be positive and call that a progress but the whole point of steps (2-3) is to have it unlocked so that you can proceed to root to flashing it the way you're trying to.
So I am pretty pessimistic on that one. To me it looks like a case of a cheap phone a company has no real urge to make easy to unlock.
Nycticorax said:
It is not clear to me what you did exactly. The step where we -- the others participants to this post and I -- are stuck is [2] here below:
boot to fastboot by running `adb reboot bootloader` from a command line on a connected and turned on device
get the OEM unlock code by doing `fastboot oem get_unlock_data` from a connected device under the fastboot interface
exchange the unlock code on the motorola support site and input that code to confirm bootloader unlock
Click to expand...
Click to collapse
Sorry got carried away finding a group dealing with the same problem as I have. And not skimming but reading the text I can confirm that I am stuck at the same place. Sorry for the interruption. I will revert if/when I have something new.
glensbo said:
Sorry got carried away finding a group dealing with the same problem as I have. And not skimming but reading the text I can confirm that I am stuck at the same place. Sorry for the interruption. I will revert if/when I have something new.
Click to expand...
Click to collapse
It's okay. I hope one of us can find something useful. Let Root, the God of Hacks, send His best love waves to you guys
wow No Help
Biniesuschristos said:
wow No Help
Click to expand...
Click to collapse
Just curious do you know what software Channel your phone is on?
The software Channel might be listed in
Settings/ about phone.
Or try
Code:
fastboot getvar all
While in fastboot mode
ro.carrier = Software Channel
Sent from my ocean using XDA Labs
You didn't ask me but perhaps it might help you help us:
Code:
reteu
for me.
I'm don't actually know anything regarding rooting mobile devices but i'm going to post some of my experience thinking it might help someone who actually knows what to do.
I've been having the same issue while trying to unlock the bootloader.
As it seems all of the fastboot commands are working fine except the OEM ones which is strange considering that i'm sure i toggled the OEM Unlock on the dev. options, just like some members commented already.
Regarding the barcode it shows as soon as i connect the device via USB in Fastboot mode, and it shows up when i use "adb reboot bootloader" too, but it wasn't showing before i updated the USB Drives so i could find the device via "fasboot devices" (the phone wasn't showing before i did it).
pontiacus said:
I'm don't actually know anything regarding rooting mobile devices but i'm going to post some of my experience thinking it might help someone who actually knows what to do.
I've been having the same issue while trying to unlock the bootloader.
As it seems all of the fastboot commands are working fine except the OEM ones which is strange considering that i'm sure i toggled the OEM Unlock on the dev. options, just like some members commented already.
Regarding the barcode it shows as soon as i connect the device via USB in Fastboot mode, and it shows up when i use "adb reboot bootloader" too, but it wasn't showing before i updated the USB Drives so i could find the device via "fasboot devices" (the phone wasn't showing before i did it).
Click to expand...
Click to collapse
Windows 10?
Sent from my ocean using XDA Labs
@sd_shadow: Do you think it looks like a bootloader you could unlock?