Develop Bugs

[Q] !!!"your phone was not recognized or is unsupported at this time"

The HBOOT of my desire is 0.93.0001, after no-pain root, I use the alpharev 1.8 to root my desier, but the PC shows as "your phone was not recognized or is unsupported at this time , if you are 100% sure your phone type should be supported in this version,please onte the model id dispaly".
Anyone could tell me how to solve it?

If you read carefully you need to download the correct driver for your USB.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Go there and read.

huhaifan1 said:
The HBOOT of my desire is 0.93.0001, after no-pain root, I use the alpharev 1.8 to root my desier, but the PC shows as "your phone was not recognized or is unsupported at this time , if you are 100% sure your phone type should be supported in this version,please onte the model id dispaly".
Anyone could tell me how to solve it?
Click to expand...
Click to collapse
When u used alpharev, do u was already rooted right? It is a requirement to run alpharev..Or maybe ur phone is really unsupported

GoogleJelly said:
If you read carefully you need to download the correct driver for your USB.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Go there and read.
Click to expand...
Click to collapse
when I root the desire, the PC reboots from the ISO, so, does the driver also need ?

andQlimax said:
When u used alpharev, do u was already rooted right? It is a requirement to run alpharev..Or maybe ur phone is really unsupported
Click to expand...
Click to collapse
Yes, the no-pain root has been done.
but how to see the "ur phone is really unsupported" ?!
I can change the recovery or delete the app in the system/data, just can't change the first picture as booting!

huhaifan1 said:
Yes, the no-pain root has been done.
but how to see the "ur phone is really unsupported" ?!
I can change the recovery or delete the app in the system/data, just can't change the first picture as booting!
Click to expand...
Click to collapse
What method are u using? Burn the iso on a cd is the easiest way..If the problem persist, try searching in this thread http://forum.xda-developers.com/showthread.php?t=794314 if someone had the same problem..
Or in this too http://forum.xda-developers.com/showthread.php?t=805811

yuor MID is PB992
check if your MID is "PB992" , which is not recognized by alpharev1.8 ,when you see "your phone was not recognized or is unsupported at this time, if you are 100% sure your phone type should be supported in this version, please onte the model id dispaly", press the keyboard "Ctrl + c ", then appears:
$
type "vi alpharev.sh" and press "Enter "
Move the cursor to the 117 line, that is
if [$ a == "PB9920000"] | | [$ a == "PB9921000"] | | [$ a == "PB9922000"],
The first "pb9920000" to "pb992", that is, to remove the back four “0”, the other constant.
Then press shift and the colon key, enter wq, enter save. Then it will re-display $
At this point type“. / alpharev.sh”,enter to re-run soff, successfully identify the machine, and then back to the prompts to step through the brush!

plz i don't understand that part ????
The first "pb9920000" to "pb992", that is, to remove the back four “0”, the other constant.
Then press shift and the colon key, enter wq, enter save. Then it will re-display $
At this point type“. / alpharev.sh”,enter to re-run soff, successfully identify the machine, and then back to the prompts to step through the brush!

epsylon5 said:
plz i don't understand that part ????
The first "pb9920000" to "pb992", that is, to remove the back four “0”, the other constant.
Then press shift and the colon key, enter wq, enter save. Then it will re-display $
At this point type“. / alpharev.sh”,enter to re-run soff, successfully identify the machine, and then back to the prompts to step through the brush!
Click to expand...
Click to collapse
I think he is saying change the first value from PB9920000 to PB992 but leave the other two values as they are.......

I had this exact problem after I created a goldcard and rooted (unrevoked) but before I wiped and flashed a new rom. I checked that I had the correct drivers, adb running and device visible, USB debugging enabled, no on-screen superuser request holding things up.
Never did get to the bottom of it, all I can say is after a complete backup, wipe and flashing oxygen rom it worked first time and recognised the phone first time!

Hi there, I did exactly what you advised 2x changing pb9920000 to pb992, and yet it still isn't able to recognise my phone. Any ideas?
Thanks!

Device not detected in bootloader mode.

Help.
I need help unlocking my bootloader, I can type adb devices while the device is powered on & my unique I.D number comes up in cmd, but whenever I boot into bootloader, the device doesn't come up in cmd what gives? All my drivers are up to date & installed correctly, though I get an MTP driver issue, could that be causing this? This is my second M8 (T-Mobile this time), first one was the dev edition s-off & converted to GPe.

You never said what command you used in the bootloader ?
It's :
Fastboot devices (not adb devices)

adb devices for adb wile phone is booted in OS
fastboot devices in fastboot/hboot mode

Oops never mind, another thing - I keep getting an error while trying to submit my code to HTC Dev after getting the identifier token.

EternalAndroid said:
Oops never mind, another thing - I keep getting an error while trying to submit my code to HTC Dev after getting the identifier token.
Click to expand...
Click to collapse
Please state the error if you would [emoji12]

After reading the opening post here, I get the impression that the code you get for the token is more an issue on your side(You messed up somewhere).
That being said, it doesn't help alot saying "I keep getting an error" but you don't tell us what the error is.
Taking a wild guess, it has to do with the actual token. Make sure you don't have any spaces in the selection of the code. Select it with the <<<<< >>>>> included. Do NOT include the <bootloader> parts next to it and again make sure there are NO spaces in the selection.
Comparison pictures of the code how it SHOULD and SHOULD NOT look.
If that is not your problem then give more information as to the error you're receiving. Doesn't help to phone an IT dept for help and you don't tell them what the problem is either, does it? Same here...

jball said:
Please state the error if you would [emoji12]
Click to expand...
Click to collapse
Sorry guys just frustrated & keep forgetting, "error reason token decryption fail (cannot generate result)."
But I think I figured out my issue, so my computer's internet is off right now & I'm trying to do all this from my N5. I'm typing the code on my phone, reading it letter for letter, number for number.
BerndM14 said:
After reading the opening post here, I get the impression that the code you get for the token is more an issue on your side(You messed up somewhere).
That being said, it doesn't help alot saying "I keep getting an error" but you don't tell us what the error is.
Taking a wild guess, it has to do with the actual token. Make sure you don't have any spaces in the selection of the code. Select it with the <<<<< >>>>> included. Do NOT include the <bootloader> parts next to it and again make sure there are NO spaces in the selection.
Comparison pictures of the code how it SHOULD and SHOULD NOT look.
If that is not your problem then give more information as to the error you're receiving. Doesn't help to phone an IT dept for help and you don't tell them what the problem is either, does it? Same here...
Click to expand...
Click to collapse

Oh wow I see

Copy the text to notepad. Copy it to your phone. Open it in your phone using any file manager. Copy and paste .

HTC M8: Root, virus, ripped off £26.68 & then tele view fraud! Please help, how hard?

HTC M8: Root, virus, ripped off £26.68 & then tele view fraud! Please help, how hard?
I have decided to keep my HTC M8 and go sim only to avoid another 24 months of contract. Today I sim unlocked and bought my new network sim. I have enabled USB Debugging and Developer options.
Then I set about trying to root the phone - the primary reason so I can delete all the Vodafone and HTC bloatware now I'm out of contract.
So I tried the hasoon2000 thread on here, which ended up with AVG going mental at all the viruses/adwares/trojans I'd installed. After sorting all that out, I found onelclickroot.com online. It seemed too simple, it was. I paid £26.68 and it didn't work. Chat comes up and a guy offered to teleview my computer screen to do the job! I don't believe this can be genuine... Is it?
So... Please can anyone tell me how I can root a British, Vodafone HTC M8 in reasonably simple steps that someone who's pretty new to this can make work without wrecking their PC and phone!???
Many thanks,
Al

playboater15 said:
I have decided to keep my HTC M8 and go sim only to avoid another 24 months of contract. Today I sim unlocked and bought my new network sim. I have enabled USB Debugging and Developer options.
Then I set about trying to root the phone - the primary reason so I can delete all the Vodafone and HTC bloatware now I'm out of contract.
So I tried the hasoon2000 thread on here, which ended up with AVG going mental at all the viruses/adwares/trojans I'd installed. After sorting all that out, I found onelclickroot.com online. It seemed too simple, it was. I paid £26.68 and it didn't work. Chat comes up and a guy offered to teleview my computer screen to do the job! I don't believe this can be genuine... Is it?
So... Please can anyone tell me how I can root a British, Vodafone HTC M8 in reasonably simple steps that someone who's pretty new to this can make work without wrecking their PC and phone!???
Many thanks,
Al
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
Try looking here
It's full of stuff and Root is also included through the links
Good luck!

playboater15 said:
So... Please can anyone tell me how I can root a British, Vodafone HTC M8 in reasonably simple steps that someone who's pretty new to this can make work without wrecking their PC and phone!???
Many thanks,
Al
Click to expand...
Click to collapse
Don't see any further post from you, don't know whether you still interested doing what you want to do.
Most important - post fastboot getvar all result without serial & imei no. for a start
What you need :
Install fastboot/adb - http://forum.xda-developers.com/showthread.php?t=2317790
Install HTC Sync Manager for the latest HTC USB drivers - download : http://www.htc.com/us/support/software/htc-sync-manager.aspx
after installation is completed, uninstall HTC Sync Manager but leave the drivers (don't uninstall)
Open a command prompt then type - fastboot getvar all

ckpv5 said:
Don't see any further post from you, don't know whether you still interested doing what you want to do.
Most important - post fastboot getvar all result without serial & imei no. for a start
What you need :
Install fastboot/adb - http://forum.xda-developers.com/showthread.php?t=2317790
Install HTC Sync Manager for the latest HTC USB drivers - download : http://www.htc.com/us/support/software/htc-sync-manager.aspx
after installation is completed, uninstall HTC Sync Manager but leave the drivers (don't uninstall)
Open a command prompt then type - fastboot getvar all
Click to expand...
Click to collapse
Hi - Thanks for the info. I take it that my phone is plugged in during this process, and what state will it be in once I've typed "fastboot getvar all"? Thanks.

on bootloader/fastboot screen.
You have a good running device, right ?
go to settings - about - software information - more - build number - click on it 7 times to enable developer options
then settings - developer options - tick usb debugging
connect phone to PC, open a command prompt then type -> adb reboot bootloader
this will boot the phone to bootloader/fastboot screen - you should see fastboot usb (in red)
then type in command prompt -> fastboot getvar all (post the result here (minus serial & imei no.)
to reboot it back to system, use volume down button to scroll to "reboot" and power button to select

ckpv5 said:
on bootloader/fastboot screen.
You have a good running device, right ?
go to settings - about - software information - more - build number - click on it 7 times to enable developer options
then settings - developer options - tick usb debugging
connect phone to PC, open a command prompt then type -> adb reboot bootloader
this will boot the phone to bootloader/fastboot screen - you should see fastboot usb (in red)
then type in command prompt -> fastboot getvar all (post the result here (minus serial & imei no.)
to reboot it back to system, use volume down button to scroll to "reboot" and power button to select
Click to expand...
Click to collapse
Thanks - Will the phone then be rooted?
If yes, will all my apps and saved files have been deleted?
If yes, how can I reinstall them?
Thanks for putting up with my newb questions.

playboater15 said:
Thanks - Will the phone then be rooted?
Click to expand...
Click to collapse
NO. Getvar data is just giving us the basic information to get started helping you out.
Hasoon's toolkit just gives false positives for malware, it should be okay in that regard (assuming you used a reputable download source - for instance links from reputable XDA members). However, its very obsolete, having not been updated for over a year (going on 2 years) and therefore won't work on my current devices.
You never should have spent money to root the device (s-off by sunshine yes, but just to root, NO). Everything you need is available here for free. Even if the service was legit, its just a waste of money and you are cheating yourself. One click root methods never work for HTC devices, either. So any claim otherwise, is not to be believed.
Post the requested info. and we'll get you started sorting you out. My advice is to read and learn properly, and that is always a better idea than trying to take shortcuts like "one click" roots.

Bootloader Unlock KeyGen (ATTN: MODERATOR)

There was a "repository" thread for members to post the output of their
"fastboot oem get_unlock_data"
command and the corresponding Unlock Code provided by Motorola's Servers but, for the love of Odin, I can't find it.
Moderators, Please move to the proper thread if known...
I haven't been fortunate enough to socially engineer an Unlock Code out of some bored and barely literate Help Desk Associate yet but, here is what I have figured out...
The output of my "oem get_unlock_data" command
3A45310027120187
5A593232335658425335005854313633352D0000
B1125F7EFB00B8A710156EEA517BD63BD1D467EA
75C97DE0000000000000000000000000
Where the first line,
3A45310027120187
is actually my IMEI_MEID reversed, well, not reversed in the "palindrome" sense...
more like Hex Pairs... like how the NV_ITEM appears in a hex editor
Output: 3A 45 31 00 27 12 01 87
Actual IMEI:3 54 13 00 72 21 10 78
Another dedicated member who's name I can't recall (Props whoever you are) figured out that plugging the second line into a Hex to ASCII converter returned your device's serial and model numbers.. ie:
Input in Hex: 5A593232335658425335005854313633352D0000
Output in ASCII: ZY223VXBS5 XT1635-
Notice version delineator (-01,-02,-03,etc...) not included...
and, the fourth line,
75C97DE0000000000000000000000000
is my UCCID... NOT the SIM card's ICCID, the device's UCCID...
as far as the mystical third line is concerned...
B1125F7EFB00B8A710156EEA517BD63BD1D467EA
i'm currently investigating the hypothesis that lines 1,2, and 4 are used to identify the individual device and perhaps catalog devices for which an unlock code has been requested and that the Unlock Code is some how contained in or somehow derived from the otherwise random 40-bit Third line... perhaps as a key or hash....
Hope these insights further the cause and again, if any Mods know the proper thread to place this post in, please do so..
Thanx!
Roam8

You don't have to 'socially engineer an Unlock Code out of some bored and barely literate Help Desk Associate'
Motorola will give you an unlock code, all you have to do is ask. The only catch is that requesting it will void the warranty of your device.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b

I'm sorry... I did fail to mention in the OP that this was concerning the Verizon Version (Addison) of the Moto Z... Droid Edition's Play and Force respectively...
And at this time Verizon will not allow Moto to assist us in unlocking the Boatloader...
So we are concentrating our efforts around the info Moto uses to authorize and generate said code
Thanks though!
Roam8

Interesting! Other than the lack of VR capability and inability to root the Verizon variant of this phone, I have absolutely no gripes with it.
I've thought about switching out my phone for something I can root but if we can achieve root on this I will have no reason to do so. So thank you for posting this and I'll continue to follow your progress.

If you have a Verizon variant... We could really use the output of your "fastboot oem get_unlock_data" command as well as the output lf "fastboot getvar all" command to add to the database.. you can PM me if you don't feel comfortable posting it in open forum...
Thanx again

Roam8 said:
If you have a Verizon variant... We could really use the output of your "fastboot oem get_unlock_data" command as well as the output lf "fastboot getvar all" command to add to the database.. you can PM me if you don't feel comfortable posting it in open forum...
Thanx again
Click to expand...
Click to collapse
I take it I need to plug my phone into the computer and run adb fastboot to get the output? What type of information will be outputted and how could it be used negatively by posting it in a public forum?

You are correct, Sir... Procedure is as follows...
-enter Fastboot Mode
-Turn device off
-Hold Vol- key for 3 seconds
-After three seconds, whilst continuing to hold Vol-, press and hold Power key
-Release both keys once Fastboot option menu appears
Connect your device to the any PC at your disposal that has both ADB and Moto Drivers installed
-launch Command Prompt and navigate to your ADB directory
-Type "fastboot oem get_unlock_data"
-Type "fastboot getvar all"
Copy and paste the output to your post...
as far as the risk involved in publishing the info? I honestly don't know the extent of the shenanigans that may be played by some talented and enterprising individual... I only know that your IMEI, UCCID, ICCID, Carrier info, Model Number and Serial Number can be gleaned from the output of these two commands....
Caveat Emptor
Roam8

Roam8 said:
You are correct, Sir... Procedure is as follows...
-enter Fastboot Mode
-Turn device off
-Hold Vol- key for 3 seconds
-After three seconds, whilst continuing to hold Vol-, press and hold Power key
-Release both keys once Fastboot option menu appears
Connect your device to the any PC at your disposal that has both ADB and Moto Drivers installed
-launch Command Prompt and navigate to your ADB directory
-Type "fastboot oem get_unlock_data"
-Type "fastboot getvar all"
Copy and paste the output to your post...
as far as the risk involved in publishing the info? I honestly don't know the extent of the shenanigans that may be played by some talented and enterprising individual... I only know that your IMEI, UCCID, ICCID, Carrier info, Model Number and Serial Number can be gleaned from the output of these two commands....
Caveat Emptor
Roam8
Click to expand...
Click to collapse
I'd prefer to just PM you the output. Are you willing to share the data you have currently collected so others can take a stab at it?

I can do this later as well..I will pm u
Sent from my LG-H918 using Tapatalk

Of course! As a matter of fact.. I was trying to add my Info to the current "repository" thread but, couldn't find it... I finally posted here hoping a moderator would pick it up and place it in the hands of any developer currently working on it

What are you using to compile the data? I'd like to see it if you can post it on a shared drive.

You execute two "fastboot" commands from the command line and copy and paste the output... i'll pull mine and post it when I get home this evening..

I'll be working all day and won't have time to address it until tomorrow at the earliest.

i wish you guys luck. id love to root my Z Droid

I take a kick on it lol just give me time to get back up phone

looking forward to it... thnx all

fastboot oem get_unlock_data data
hear the output of the fastboot oem get_unlock_data command on my device
(bootloader) Unlock data:
(bootloader) 3A45310027251965#
(bootloader) 5A5932323357514C364D005854313633352D0000#
(bootloader) 7ACFC7093BA2C54D0B7C2438EC713DDDD68C459F#
(bootloader) E5E13C38000000000000000000000000
dont know why the first line is Unlock data: is that normal?

This is awesome, if the unlock code gets cracked, Hello Z Force ????

If I knew that Verizon locks all there phones. I would have went to Sprint or At&t. I had about 6 Android phones. And so far this is the only Android phone and I can't root it.

It's your device. I would not accept not being possible to root it. I mean, if you rent it, ok. Is not your device. But not being able to control a device which I bought is really annoying for me. Did once buy a device (Amazon Fire TV) which I thought could be rooted later. It was 50% off, and still 50% too expensive for something that after short look at its functions never was turned on ...
Idea: Tell them there is a malfunction. If you copy music or photos onto the internal memory of your device, it never keeps its dates. You want to sort by file date, and ask them for a solution.

Struggling to unlock booloader: getting weird barcodes

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?