Develop Bugs

HTC Desire Diag mode?

Have anyone succeeded to connect Desire in DIAG Mode?
I have tried almost everything, but no luck
Thanks in advance.

When you say 'diag mode' are you referring to using ADB from the Android SDK?
If so, yes I have. What you need to do is download the Android SDK for Windows (or Linux) depending on the Operating system that you're using.
Then get all the drivers for the USB sorted out.
To be able to connect to the phone using ADB you need to enable 'debugging mode'. To do this, do the following on your phone:
1. Bring the Menu up using the little arrow on the left.
2. Goto Settings.
3. Goto Applications.
4. Goto Development.
5. Tick 'USB Debugging'.
You should then be able to connect using ADB.

I dont think so, I suspect him want to got the QC diagnostic Mode
I dont think so, I suspect him want to got the QC diagnostic Mode, I'm try to work in this so!

Diag mode? Yes!
After investigating usb-brickness and kernel command lines that are passed out during boot, i found out that their flags can be changed by running
fastboot oem writeconfig 8 x0y00 (not sure if you need a s-offed device), where:
x0000 x=2 - diag enabled (eg. 20000)
00y00 y is a sum of these: 1-disable_uart3; 2-usb_h2w_sw; 4-disable_sdcard;
So, by combining them, we might get the following:
20700 : board_bravo.disable_uart3=1 board_bravo.usb_h2w_sw=1 board_bravo.disable_sdcard=1 diag.enabled=1 board_bravo.debug_uart=0w=0
20000 only diag.enabled=1 (plain diagnostic mode; not compatible with usb_h2w_sw=1)
00400 disable_sdcard=1
00200 usb_h2w_sw=1
20200 usb_h2w_sw=1 diag.enabled=1
After enabling Diag Mode, a new com port appeared in Device Management - HTC Diagnostic Interface
(COM18). I can successfully connect to it with QPST, PSAS, QXDM.
Additional information are welcomed. As you can see, I didn't figure out about board_bravo.debug_uart flag..
I attached a working diag driver I found out.

@sieempi: Do you have any link for engineering SPL of Desire.

No. I used Alpharev's Hboot.
Sent from my HTC Desire using XDA App

Reboot rapidly
After configuration of diag mode enable,my desire reboot rapidly in HTC quietly brilliant screen.
It show this screen again and again.
Can you give me some suggestion?

@sieempi: Thanks for the info man.
Just wanted to confirm from you you had tried this on HTC desire - GSM, Right??

Just wanted to confirm from you you had tried this on HTC desire - GSM, Right??
I am asking this b'coz now I thought to try the same stuff with my Nexus one.
As well as could you give me some hints about how you verified parameters of fastboot oem writeconfig.
I tried the same stuff on HTC sapphire with ENG spl...command was running succesfully but nothing happend... I believe sapphire doesn't have diag mode (not sure for now??)........

Just wanted to confirm from you you had tried this on HTC desire - GSM, Right??
I am asking this b'coz now I thought to try the same stuff with my Nexus one.
As well as could you give me some hints about how you verified parameters of fastboot oem writeconfig.
I tried the same stuff on HTC sapphire with ENG spl...command was running succesfully but nothing happend... I believe sapphire doesn't have diag mode (not sure for now??)........

As I said, I was investigating USB-brickness and I noticed that it changes the values i got from fastboot oem readconfig. So I generated multiple bricks by flashing misc partition with random data/files (recovery, adb.exe, fastboot.exe, busybox, etc - binaries) and analyzed the config values. It was only a matter of time until I figured out the logic. Afterwards, I could easily tell where the flags were stored in misc (I didn't pay too much attention on this, though).
Yes, it was done on a GSM Desire.

Thanks for the info

Hello sieempi
Can you provide dmesg message when you turn on your desire to diag mode?
thank you

Check this out!
You may want to take a look at my post. This will virtually work with any device who's kernel source is released . http://forum.xda-developers.com/showthread.php?t=948360

TESTED
iwanrakic said:
Have anyone succeeded to connect Desire in DIAG Mode?
I have tried almost everything, but no luck
Thanks in advance.
Click to expand...
Click to collapse
root your mobile by kingroot
adb shell
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
to stop diag
echo 0 > /sys/devices/virtual/android_usb/android0/f_diag/on

alfahd said:
root your mobile by kingroot
adb shell
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
to stop diag
echo 0 > /sys/devices/virtual/android_usb/android0/f_diag/on
Click to expand...
Click to collapse
does it work on desire 626s?
thanks

tlclol said:
does it work on desire 626s?
thanks
Click to expand...
Click to collapse
It doesn't for me.
I had found an easy way to enable diag and also get into prog settings without MSL. I have since lost them but I am trying to find them here again. Was relatively easy with no modifications needing to be done. This was done on a Boost Model 626s Desire.

alfahd said:
root your mobile by kingroot
adb shell
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
to stop diag
echo 0 > /sys/devices/virtual/android_usb/android0/f_diag/on
Click to expand...
Click to collapse
Works on the Desire 510 - Virgin Mobile just fine.

HTC One X bootloader: 1.72 0000

Dear Developers,
Since few times ago I am searching information regarding with firmware downgrade for HTC One X updated on ****er version 4.2.2 bootloader 1.72. (I ma so sorry for bad words, but really I don't understand who and why created this firmware with so many bugs). Unfortunately there are a lot of information and disinformation regarding with firmware downgrade procedures. Already I tried almost all what I found until now to unlock the bootloader but everything I tried I didn't found solution to turn S-OFF on this model. Somebody say that is impossible to turn S-OFF on HTC One X, somebody else give some information, starting with HTC One X and finish with other model HTC One, so please somebody who know in details all versions, give us correct information what we are able to do on this particular device (HTC One X) with specific firmware already installed.
Any kind of help shall be much appreciated.
Best regards!
Fredi

Frepa_AL said:
Dear Developers,
Since few times ago I am searching information regarding with firmware downgrade for HTC One X updated on ****er version 4.2.2 bootloader 1.72. (I ma so sorry for bad words, but really I don't understand who and why created this firmware with so many bugs). Unfortunately there are a lot of information and disinformation regarding with firmware downgrade procedures. Already I tried almost all what I found until now to unlock the bootloader but everything I tried I didn't found solution to turn S-OFF on this model. Somebody say that is impossible to turn S-OFF on HTC One X, somebody else give some information, starting with HTC One X and finish with other model HTC One, so please somebody who know in details all versions, give us correct information what we are able to do on this particular device (HTC One X) with specific firmware already installed.
Any kind of help shall be much appreciated.
Best regards!
Fredi
Click to expand...
Click to collapse
Actually:
Unlocking the Bootloader on the HTC phone maybe as simple as you think!
Note:
1. Go here First xda-developers
2. Register as a developer.
3. Go to phone Setting’s
4. For none Developer phones on Andriod
5. Go to Setting’s then About, HTC SDK API Level and start tapping on it to get developer options, continue tapping till it says “Your now a Developer”
6. In Settings go to Power, scroll down to where it says “Fastboot” and un-check it. You will need this to get into your boot menu.
7. BACKUP ALL YOUR DATA. Because “unlocking your BootLoader” WILL WIPE OUT ALL YOU’RE DATA. You will go back to the settings when you initially bought the phone.
8. Power Down
9. After powering down, press Volume Down and while pressing Volume Down, press Power holding both buttons to start the device into Bootloader mode. If you have difficulty, power up normally, go to Settings->Battery and deselect Fast boot ( If you forgot to do this). Power down and try again.
10. Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
11. Connect the device to the computer via a usb cable
12. Go back to xda-developers, Login (If you already have not do so)
13. Select the link for unlocking the Bootloader, make sure your phone is plugged into the pc as discussed above.
14. Follow the simple instruction’s; you will get on the right of the screen where you can select one of the HTC this tool will work with only HTC devices on the list. THIS WILL ONLY WORK FOR the phone’s on the list!
15. A POP UP menu will come up after you select the phone on the list it will be a warning.
16. Check off the warnings (AT YOUR OWN RISK) Remember this is heavy duty!
17. The next screen will be the scariest for newbie’s “What to select”
18. Download the following fastboot binary for your OS using the following links:
19. Platform Download Size (bytes) Checksum fastboot binary, Linux
20. (Unzip the file before executing) Fastboot 618 ffd3b02cdf9aa7609462e3957663d238
21. fastboot-binary, OS X
22. (Unzip the file before executing) fastboot-mac
23. Fastboot binary, Windows
24. (Unzip the file before executing) fastboot-win 83753 a90c25141e306b3062dc8e47e14a1005
(Make sure you are logged into XDA-Developers FIRST before linking to it)
25. I have not gotten to the point past this because I unlocked my BootLoader the old fashioned way. But this way seems a great deal easier than searching for your HTC and not finding the right choice. I have already unlocked my cell and rooted, and through trial and error I got the right OS Modification “InsertCoin Here” Hope I placed this in the right Forum.

thank you for the help

HTC one m8 in a boot loop

Hi all.
I suspect this question has been asked before and I have found loads on how to do's, but I can't seem to achive what is needed, so any help, however small is greatly appriciated.... he goes.
Customer has brought in an HTC One M8. Details I can give from the Fastboot screen is:-=
***Software Status: Official***
***LOCKED***
M8_UL_CA PVT SHIP S-OFF
CID-111111111 (<---- 8X1'S)
HBOOT-3.10.0.0000
RADIO-1.29.214500021.12G
OpenDSP-V51.2.2-00593-M8974_FO.1015
OS-6.12.401.1
eMMC-boot 2048MB
Dec 17 2015,14:15:48.3
It is stuck in a boot loop that alsways shows the HTC boot screen, reboots to the HTC screen and promptly then to the Android recovery screen:-
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power
Reboot system now
Reboot to bootloader
Apply update from ABD
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
_________________________________
Supported API:3
handle_cota_install: install cwpkg to /cache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop tp /cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip cw installation
Sorry to have to type this in as I cant seam to get images to upload.
Now, this seems to be a common problem and most suggestions are re flash the firmware using RUU. The first stumbling block I am hitting is the phone is not being detected on any PC that I use, by any cable I use, either by Windows ( USB detected sound plays and disconnected plays if I unplug but no detection in device manager, I have loaded the HTC ABD drivers, installed HTC manager and Android studio but again no detection) or on a Mac.
Question is, can I reset this phone back to a working state or should I direct the customer back to a HTC service centre?
BTW the phone phone is a European model and currently on 3.
Thanks in advance.
Marc

PC1staid said:
Now, this seems to be a common problem and most suggestions are re flash the firmware using RUU. The first stumbling block I am hitting is the phone is not being detected on any PC that I use, by any cable I use, either by Windows ( USB detected sound plays and disconnected plays if I unplug but no detection in device manager, I have loaded the HTC ABD drivers, installed HTC manager and Android studio but again no detection) or on a Mac.
Click to expand...
Click to collapse
Try another USB cable, and another port on the PC.
Also, go into bootloader, select fastboot (if not highlighted in red already) using vol keys, and confirm with power button. Then see if the phone's serial number is returned with the command: fastboot devices
PC1staid said:
Question is, can I reset this phone back to a working state or should I direct the customer back to a HTC service centre?
BTW the phone phone is a European model and currently on 3.
Click to expand...
Click to collapse
Its not the Euro version. Its US version, hacked to accept Euro software. Due to this, and SuperCID (11111111) its obviously been modified, and HTC won't honor any warranty (if that is what you are asking).
I also wouldn't be surprised if the back cover was replaced (again, voiding the warranty). What does the model number on the back say?

redpoint73 said:
Try another USB cable, and another port on the PC.
Attempted this with 2 PC's, 1 Laptop all running Windows 7 Pro with SP1 64 bit and a Mac. Tried the cable that came with my Samsung S5 ( Not the USB 3 cable) plus 2 other cables that I use in the workshop and the original cable suppled by the customer. Phone not detected in device manager on any of the PC's, however the plugged in and unplugged sounds do play. Mac sit's idoly twiddleing its thumbs...
Also, go into bootloader, select fastboot (if not highlighted in red already) using vol keys, and confirm with power button. Then see if the phone's serial number is returned with the command: fastboot devices
Went into bootloader and fastboot. only option I have to locate the S/N is via show barcodes. the S/N is:- HT444WM04348
Its not the Euro version. Its US version, hacked to accept Euro software. Due to this, and SuperCID (11111111) its obviously been modified, and HTC won't honor any warranty (if that is what you are asking).
I dont think it would be under warranty as customer reckons it is over 12 months old.
I also wouldn't be surprised if the back cover was replaced (again, voiding the warranty). What does the model number on the back say?
Click to expand...
Click to collapse
Shown on the back is OP6B110 M8x
Hope this gives some more helpfull info.

PC1staid said:
Shown on the back is OP6B110 M8x
Hope this gives some more helpfull info.
Click to expand...
Click to collapse
Now that you mention that, I think there may be an Australian variant (OP6B110) which also has the product ID (M8_UL_CA) indicated on the bootloader screen.
Either way, its not the Euro variant; and its been modified by a previous owner (as mentioned).
Any luck getting USB fastboot working? Once you do, do fastboot getvar all, and post the output (delete IMEI and serial number before posting) so we can verify the MID and make sure you are running the right RUU.

exactly the same problem
Hi.. I have also been facing the same problem since today morning. phone completely conked off and not connecting to pc either. the connecting and disconnecting sound is there but device driver error so not installed. pls help... phone model is OP6B100. Bought from US and being used in India

sonalgirdhar said:
Hi.. I have also been facing the same problem since today morning. phone completely conked off and not connecting to pc either. the connecting and disconnecting sound is there but device driver error so not installed. pls help... phone model is OP6B100. Bought from US and being used in India
Click to expand...
Click to collapse
No, its not the same problem. The OP is in a bootloop, which is very different from the screen not coming on.
Folks need to stop saying "same problem", because it really never never never is. Just a minor detail or 2 that is different, makes a huge impact on the condition and the way forward.
Leave the phone on charger for several hours, and then hold power for 30 seconds of so, and see if you can get the screen to come on.
If the screen doesn't come on, there isn't much we can do.

redpoint73 said:
No, its not the same problem. The OP is in a bootloop, which is very different from the screen not coming on.
Folks need to stop saying "same problem", because it really never never never is. Just a minor detail or 2 that is different, makes a huge impact on the condition and the way forward.
Leave the phone on charger for several hours, and then hold power for 30 seconds of so, and see if you can get the screen to come on.
If the screen doesn't come on, there isn't much we can do.
Click to expand...
Click to collapse
Sorry I meant I am also getting the same screen with phone stuck in bootloop amd not moving beyond this screen.

sonalgirdhar said:
Sorry I meant I am also getting the same screen with phone stuck in bootloop amd not moving beyond this screen.
Click to expand...
Click to collapse
"completely conked off" (your previous words) is not a good description of the above. Misleading, really.
Hold the vol down button during the bootloop cycle. Don't let go until you are on the bootloader screen. Then try to connect with fastboot.

My HTC is having same error after Android 6.0 update.
It's not getting connected to pc.. I bought my phone in USA and now using it in UK.
Called HTC and they said they will not accept US phone for repair even though it's in warranty..

tushard007 said:
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc.. I bought my phone in USA and now using it in UK.
Called HTC and they said they will not accept US phone for repair even though it's in warranty..
Click to expand...
Click to collapse
Hi.. Did u find any solution to the problem. The service center here also refused to take a phone bought outside india.

Hi..
Please find attached the result of 'fastboot getvar all'. i had also shared the same with HTCDev team and the reply is as below:
"Hello Sonal
I sincerely thank you for sending us the information that was requested . According to the information you have provided, I was able to identify the reason why the device can not receive updates at this time. For your device to without any problem , it must have all the original software or settings and STOCK.
To begin , let me explain how our devices are distributed to security S -ON to protect your settings and to ensure proper operation. Security on your device has been disabled ( S -OFF) which has allowed the following parameters change at this time prevent the upgrade is installed
cidnum : 11111111 < ---- this parameter will not get your device updates
Here are the options for you:
Option 1 - Return all device settings to their original settings or STOCK. - First you must change the parameters specified as these were originally. Once this is done, now again to contact STOCK install the operating system.At this time, HTC doesn't officially support obtaining S-Off on our devices. Having said that, I'll be happy to take a look at what's going on and at least point you in the right direction. I know this may cause some limitations in the assistance I am able to provide to you but I am more than happy to do what I can to assist you through your issue . We are happy if you contact us about any problems you might, in any part of their development process. .To begin with, the following websites are some examples where we recommend you start your research on S-Off. http://forums.xda-developers.com http://www.androidcommunity.com http://androidforums.com Please note the above web sites are not operated by HTC. We can not validate or guarantee the information contained therein.
Do not hesitate to reach out to us if you have any questions. You can contact us back via email, using the second link listed below (The one at the end of the sentence "To send a reply to this message, please click here"). "
Can you please help with the next steps to get the phone working again.

sonalgirdhar said:
Please find attached the result of 'fastboot getvar all'.
Click to expand...
Click to collapse
Flash the 6.12.401.4 RUU.
See the download in Post #3 of the following thread, and instruction in Post #17 of that thread: http://forum.xda-developers.com/htc-one-m8/general/marshmallow-6-0-update-htc-m8-european-t3296141
sonalgirdhar said:
i had also shared the same with HTCDev team and the reply is as below:
Click to expand...
Click to collapse
Asking HTC for support by sharing info that indicates your phone was modded, was a bad idea. Of course they are going to say "we don't support this" and "return the phone to stock".
No need to go back s-on or change CID. Just run the RUU as I mentioned.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
tushard007 said:
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc..
Click to expand...
Click to collapse
USB connection issues are usually due to issues on the PC, not the phone.
Try a different cable, different USB port (as I suggested in a previous post). Install (or re-install) HTC Sync. You may even need to try a different PC (Win7 and USB 2.0 get the best results).
Also, bear in mind that phone needs to be in bootloader-fastboot mode, for fastboot commands to work. Booted into OS or recovery for adb to work.

redpoint73 said:
Flash the 6.12.401.4 RUU.
See the download in Post #3 of the following thread, and instruction in Post #17 of that thread: http://forum.xda-developers.com/htc-one-m8/general/marshmallow-6-0-update-htc-m8-european-t3296141
Asking HTC for support by sharing info that indicates your phone was modded, was a bad idea. Of course they are going to say "we don't support this" and "return the phone to stock".
No need to go back s-on or change CID. Just run the RUU as I mentioned.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
USB connection issues are usually due to issues on the PC, not the phone.
Try a different cable, different USB port (as I suggested in a previous post). Install (or re-install) HTC Sync. You may even need to try a different PC (Win7 and USB 2.0 get the best results).
Also, bear in mind that phone needs to be in bootloader-fastboot mode, for fastboot commands to work. Booted into OS or recovery for adb to work.
Click to expand...
Click to collapse
@redpoint73 Thank you so much, have been able to update the RUU. Updating apps now

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?