Develop Bugs

Issue during Desire rooting process

Hello everybody,
today I've received the Desire.
I've tried to root the device but I'm in trouble.
So, I installed the SDK on my C:\sdk and I tested that ADB is working doing "adb devices".
I received a reply with my device and the string "device" after it.
Then,
I disconnected my Desire, then poweroff it.
I pressed the "Back" button then I pressed the Power button.
On the screen of Desire now there are 3 droids on a skate and the word "FASTBOOT" in red.
On my shell on Windows I type "fastboot-windows oem ?"
and I see:
< waiting for device >
I connect the device on USB.
The screen of Desire now has "FASTBOOT USB".
In the shell, I see:
... INFOcommand list:
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOheap_test
INFOrtask
INFOtask
INFOenableqxdm
INFOgencheckpt
OKAY
Now, if i type "fastboot-windows oem unlock"
I receive:
... INFO[ERR] Command error !!!
OKAY
WTF???
Someone can help me, please, to unlock the bootloader?
Why I can't see with "fastboot-windows oem ?" the command "unlock"???
Thanks,
kind regards,
ghale

ghale said:
Hello everybody,
today I've received the Desire.
I've tried to root the device but I'm in trouble.
So, I installed the SDK on my C:\sdk and I tested that ADB is working doing "adb devices".
I received a reply with my device and the string "device" after it.
Then,
I disconnected my Desire, then poweroff it.
I pressed the "Back" button then I pressed the Power button.
On the screen of Desire now there are 3 droids on a skate and the word "FASTBOOT" in red.
On my shell on Windows I type "fastboot-windows oem ?"
and I see:
< waiting for device >
I connect the device on USB.
The screen of Desire now has "FASTBOOT USB".
In the shell, I see:
... INFOcommand list:
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOheap_test
INFOrtask
INFOtask
INFOenableqxdm
INFOgencheckpt
OKAY
Now, if i type "fastboot-windows oem unlock"
I receive:
... INFO[ERR] Command error !!!
OKAY
WTF???
Someone can help me, please, to unlock the bootloader?
Why I can't see with "fastboot-windows oem ?" the command "unlock"???
Thanks,
kind regards,
ghale
Click to expand...
Click to collapse
here, I will save you from the onslaught of people telling you to search.
fastboot oem unlock does not work on the desire.

So, what I have to do?
I've read a lot on this forum and on other sources!
Can you, please, tell me what I have to do then???

ghale said:
So, what I have to do?
I've read a lot on this forum and on other sources!
Can you, please, tell me what I have to do then???
Click to expand...
Click to collapse
There is currently no public way of rooting the desire. Even though it had been rooted there ate still problems with gaining full read/write access to system.

Thank you very much for your reply!
I'll wait, then...

ghale said:
So, what I have to do?
I've read a lot on this forum and on other sources!
Can you, please, tell me what I have to do then???
Click to expand...
Click to collapse
Obviously, you've not read enough... There's plenty of info on this already in the 2 rooting threads in this very section.
Paul over at Modaco has rooted the Desire, but has not yet gotten write access. He's on holiday for 2 weeks now, so we have to wait for him to return.

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.

[TROUBLESHOOTING] Bootloader Unlock Fail: (bootloader) [KillSwitch] Last Byte is 0X01

if you're reading this thread, you're likely tearing out your hair in apt frustration because you're just trying to unlock your bootloader and its a no-go. If you're coming from a One M7 or M8, just be aware that HTC's switched up the game since then. Also, everything mentioned below is indirectly applicable to HTC 10 owners as well.
Writing up this thread as that was me, and I scoured pretty much every link pulled from variations of google keyword searches; and as I was successful in finally unlocking the damn thing, here is my braindump:
[in no particular order], and YMMV, much of this is a compilation of things that saved other people experiencing such errors, every rock unturned is a rock unturned.
There's a new "download mode"---the ol' white backgrounded fastboot that you used to know and love, that's sidelined, you must run fastboot on the black backgrounded Download mode format.
you CANNOT use the standard Google/Android SDK's fastboot. I know, wtf. you MUST use HTC's fastboot (the one they provide on HTCdev.com; note that their's is missing an ADB, you can pluck the ADB portion from the standard Android SDK).
If you are experiencing a fail, I recommend immediately wiping the whole device (reset all data), and then starting anew: from there, be sure to: --get Developer, and check the: allow OEM unlocking + allow USB debugging boxes. also, while you're in settings, might as well: increase the screen off time, put 'no lock screen', allow unknown sources installations, etc. then after all that's set, then try and run the fastboot.
for whatever reason, the Gmail web client might not work happily with your unlock_code.bin that you get sent---and/or you're getting weird HTCdev login errors even though you put in the right password---eff that noise; start anew: create a new account, don't use a Gmail email (I used a live.com email to get the unlock_code.bin that ended up being the golden goose egg). yeah, for reasons unknown, there's some RNGmagic mojo crap going on here, so if you're experiencing errors, there's really nothing to lose by going new routes.
don't use Chrome to go to the HTCdev website; I used Edge (no deliberate Microsoft plug or anything here, fyi)
the HTCdev website won't accept your fastboot paste of oem unlocking info if its not the right number of characters, I tested this, so that's not the problem if you thought it was; I recommend opening up a Notepad and just copying and pasting it there and then double-checking that, and then pasting it onto the HTCdev site.

Dont mean to burst your bubble.. Thats all old news.
Beamed in by telepathy.

Unlock Bootloader & Root Moto Z2 Force

To unlock Bootloader:
On Phone:
Open Developer Mode: Settings>System>About Phone>Click "Build Number" Seven Times
Go back to System>Developer Options>Turn on: OEM Unlocking & USB Debugging
On PC:
Do Google Search for Downloads:
Download: adb and fastboot
Download: appropriate phone drivers
Connect Phone to PC
Open: adb & fastboot Folder>open Command Prompt/PowerShell
Type:
adb devices (Pop-up will appear on phone to allow USB debugging)
re-type adb devices (you should see your device)
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data (this data is used in the Motorola Website: https://motorola-global-portal.custh...-your-device-a)
Once logged in, put in above unlock data in to see if phone is able to be unlocked...click unlock.
You'll receive a unique unlock code via email....copy unlock code.
Go back to Command Prompt/PowerShell
Type:
fastboot oem unlock (unique unlock code) (type in twice to confirm unlocking)
(NOTE: ALL DATA WILL GET DELETED-BACK IT UP!)
If this isn't working, what hiccups are you running into?
To Root your device:
On Phone:
Make sure: Developer Options on>OEM Unlocking & USB Debugging turned on (steps above)
Connect (turned on) Device to PC
On PC:
download (TWRP file specific to phone: https://twrp.me/Devices/): EXAMPLE: twrp-3.2.3-0-nash.img
Open/Create new/clean adb/fastboot folder
place TWRP img file INTO the above folder
Download: Magisk-V18.0.zip (https://forum.xda-developers.com/app...mless-t3473445)
Place Magisk-V18.0 Zip file into adb/fastboot folder
Once all files within adb/fastboot folder, open Command Prompt/PowerShell
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-2-nash ((add: .img)) Phone should open Team Win Recovery
ON PHONE: Swipe to "Allow Modification"
adb devices (should show "recovery")
adb push Magisk-V18.0.zip /sdcard
adb shell twrp install /sdcard/Magisk-V18.0.zip (phone should show installation)
adb reboot
On Phone:
Open: Magisk Manager
select lines in upper left hand corner>Settings>Automatic Response>Grant
Open "Root Checker App" to verify root (i.e., Root Checker Pro, Root Checker Advanced)

JTC Intl said:
To unlock Bootloader:
[NOTE: device with root access no longer receives official update notifications from the manufacturer)
Click to expand...
Click to collapse
Mine did until I went into Developer Setting and un ticked automatic software updates..

I thought I had found the perfect Z2 for me. Ordered on eBay for $130 with no scratches and very slight screen burn-in. I don't worry about light burn-in as I always use Substratum and turn all my screens amoled black with light text, I never notice the burn-in anyway.
Only problem was it being a T-Mo version but I couldn't unlock the bootloader. I did all that was required to receive the Unlock Code, however, when I input it the second time, it states "code verification failure." Verifed correct code multiple times and upon checking the Motorola unlock help thread, there is a list at the beginning with CID #s of bootloaders that can be unlocked and those that can not. Any CID not listed as "can be unlocked" are unable to be unlocked even if the # does not appear under "cannot be unlocked" list. My CID of 0x0015 was not on either list, therefore deemed unlockable.
I saw someone else inquire about his 0x0015 CID and was told pretty much that same thing, so I didn't add to the thread and just returned the phone. Now I am looking to purchase another T-Mo phone from a different seller with hopes of receiving a compatible CID, but I'm kinda concerned about running into the same issue. Are you aware if there are large group of these T-Mobile phone who's bootloaders can't be unlocked or did I just get a one off CID#. Or should I be looking at rooting a Sprint version and trying to change it to a GSM Unlocked or are there Sprint version with unlockable bootloaders as well? Any advice as how you think I should proceed would be most helpful as I would like to order the replacement phone today or tomorrow. TIA

MrBrazil1911 said:
I saw someone else inquire about his 0x0015 CID and was told pretty much that same thing, so I didn't add to the thread and just returned the phone. Now I am looking to purchase another T-Mo phone from a different seller with hopes of receiving a compatible CID, but I'm kinda concerned about running into the same issue. Are you aware if there are large group of these T-Mobile phone who's bootloaders can't be unlocked or did I just get a one off CID#. Or should I be looking at rooting a Sprint version and trying to change it to a GSM Unlocked or are there Sprint version with unlockable bootloaders as well? Any advice as how you think I should proceed would be most helpful as I would like to order the replacement phone today or tomorrow. TIA
Click to expand...
Click to collapse
If you're a T-Mobile/Metro user the TMO model is ideal. It packs every Magenta band aside from B71. The Sprint version will affect your experience on T-Mobile, as it only possesses 2, 4, and 12. So no LAA, 66, nor LTE-U. B46, aka LAA is stupid fast. I've heard U is good too, but availability is limited.
Now, if you use ATT, VZ, or Sprint you won't miss out on anything by buying the Sprint version.
All things considered, I'd gamble with the former. Playing the TMO lottery is definitely worth it. In fact, I bought a 2nd one and will see what happens in a few days.

Ace42 said:
If you're a T-Mobile/Metro user the TMO model is ideal. It packs every Magenta band aside from B71. The Sprint version will affect your experience on T-Mobile, as it only possesses 2, 4, and 12. So no LAA, 66, nor LTE-U. B46, aka LAA is stupid fast. I've heard U is good too, but availability is limited.
Now, if you use ATT, VZ, or Sprint you won't miss out on anything by buying the Sprint version.
All things considered, I'd gamble with the former. Playing the TMO lottery is definitely worth it. In fact, I bought a 2nd one and will see what happens in a few days.
Click to expand...
Click to collapse
Thanks for the feedback. I am primarily a T-Mo network user. I use Google Voice and just grab cheap MVNO sims from eBay and will occasionally use an AT&T sim card. So if I manual unlock it myself from instructions I've seen here, will I still retain the above bands you mentioned?

MrBrazil1911 said:
Thanks for the feedback. I am primarily a T-Mo network user. I use Google Voice and just grab cheap MVNO sims from eBay and will occasionally use an AT&T sim card. So if I manual unlock it myself from instructions I've seen here, will I still retain the above bands you mentioned?
Click to expand...
Click to collapse
Bands stay following SIM and Bootloader unlocks. But, when the modem of another model is flashed access to LTE is lost.

Trying to do this and can't get unlock code. When I type in command i just get . . . in the cmd prompt

mike2246 said:
Trying to do this and can't get unlock code. When I type in command i just get . . . in the cmd prompt
Click to expand...
Click to collapse
Make sure you're using up to date adb/fastboot files and a 2.0 usb port. If no 2.0 ports try using a hub to bring the 3.0+ ports down.

41rw4lk said:
Make sure you're using up to date adb/fastboot files and a 2.0 usb port. If no 2.0 ports try using a hub to bring the 3.0+ ports down.
Click to expand...
Click to collapse
I have used usb 3.0 all the time. Was never be a problem. But I would try, too :good: Wish the person luck

allrightlite said:
I have used usb 3.0 all the time. Was never be a problem. But I would try, too :good: Wish the person luck
Click to expand...
Click to collapse
3.0 ports won't be a problem for everyone, but for some it is. Some have only been able to use one port on their pc for flashing, some have had to use hubs to dumb their ports down. That's why it is generally recommended to use 2.0 port. Saves having to repeat the same info 100x in every other post.

This worked perfectly until the last step for my Sprint version of Z2 Force. Kudos to JTC Intl for crystal clear instructions.
When I launch the Magisk Manager , it asks me if I want to "Upgrade to full Magisk to finish set up. Download and install?" I respond OK, then after sometime, it says "There was a problem parsing the package".
Instead of v18 of Magisk, I downloaded v22 that too not as a ZIP, but it was only available as an APK from their GITHub. (https://github.com/topjohnwu/Magisk/releases/tag/v22.1)
EDIT - I tried the troubleshooting suggestions for this problem in their wiki ( clearing cache, clearing data, reinstalling etc). Did not help.
Please help. I'm almost there.
Thank you.

hi i need help is there any other way i can unlock the boot loader because when i enter my code it says device not eligible....

JTC Intl said:
To unlock Bootloader:
On Phone:
Open Developer Mode: Settings>System>About Phone>Click "Build Number" Seven Times
Go back to System>Developer Options>Turn on: OEM Unlocking & USB Debugging
On PC:
Do Google Search for Downloads:
Download: adb and fastboot
Download: appropriate phone drivers
Connect Phone to PC
Open: adb & fastboot Folder>open Command Prompt/PowerShell
Type:
adb devices (Pop-up will appear on phone to allow USB debugging)
re-type adb devices (you should see your device)
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data (this data is used in the Motorola Website: https://motorola-global-portal.custh...-your-device-a)
Once logged in, put in above unlock data in to see if phone is able to be unlocked...click unlock.
You'll receive a unique unlock code via email....copy unlock code.
Go back to Command Prompt/PowerShell
Type:
fastboot oem unlock (unique unlock code) (type in twice to confirm unlocking)
(NOTE: ALL DATA WILL GET DELETED-BACK IT UP!)
If this isn't working, what hiccups are you running into?
To Root your device:
On Phone:
Make sure: Developer Options on>OEM Unlocking & USB Debugging turned on (steps above)
Connect (turned on) Device to PC
On PC:
download (TWRP file specific to phone: https://twrp.me/Devices/): EXAMPLE: twrp-3.2.3-0-nash.img
Open/Create new/clean adb/fastboot folder
place TWRP img file INTO the above folder
Download: Magisk-V18.0.zip (https://forum.xda-developers.com/app...mless-t3473445)
Place Magisk-V18.0 Zip file into adb/fastboot folder
Once all files within adb/fastboot folder, open Command Prompt/PowerShell
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-2-nash ((add: .img)) Phone should open Team Win Recovery
ON PHONE: Swipe to "Allow Modification"
adb devices (should show "recovery")
adb push Magisk-V18.0.zip /sdcard
adb shell twrp install /sdcard/Magisk-V18.0.zip (phone should show installation)
adb reboot
On Phone:
Open: Magisk Manager
select lines in upper left hand corner>Settings>Automatic Response>Grant
Open "Root Checker App" to verify root (i.e., Root Checker Pro, Root Checker Advanced)
Click to expand...
Click to collapse
Does rooting the phone work for an AT&T Moto Z2 force phone?

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?