Database Develop

XT1092 Carrier ID Needed (UK/EU Unlocked)

Hi All,
I need to find the carrier ID for my XT1092 which is a UK Unlocked International Version.
I set it to "irl" during a ROM flash back to stock, which stops the APN setting up correctly.
If anyone has a UK unlocked edition can you goto the bootloader and run the command "fastboot oem config carrier" and output the results??
If should look like the picture attached, but the section "irl" should be something else.
attachment.php
I am on EMobile Ireland as the network, but expect the carrier ID to be a unlocked non region specfic one I think as the phone was bought direct from a supplier.
Thanks

Hi,
Has anyone a EU/UK unlocked to get the carrier ID?
Thanks

Anyone?

Hi Again,
Anyone out there able to help with checking their Carrier ID?
Thanks

Hi mate,
it might be strange, but I got the following output (unlocked bootlader, UK retail phone, retgb). Checked a couple of times, always the same.
$ fastboot oem config carrier
ERROR: could not get pipe properties
... INFO<UTAG name="carrier" protected="false">
INFO <value>
INFO </value>
INFO <description>
INFO Carrier IDs, see http://goo.gl/lojLh3
INFO </description>
INFO</UTAG>
I guess the command you mentioned is for changing the carrier only, it doesn't echoes the current value. I've googeled a bit and found the fastboot getvar all command, and maybe the last value of its output might be the carrier you'd need. I'm not an expert, so don't take it for granted, that's all I could figure out now.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6011
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: .....
(bootloader) cid: 0x0007
(bootloader) channelid: 0x41
(bootloader) uid: .....
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: .....
(bootloader) meid:
(bootloader) date: 12-06-2014
(bootloader) sku: XT1092
(bootloader) iccid:
(bootloader) cust_md5: .....
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Dec 2 23:16:34 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retgb/victara:5.0
(bootloader) ro.build.fingerprint[1]: /LXE22.46-19/18:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.19.victara_ret
(bootloader) ro.build.version.full[1]: gb.retgball.en.GB
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_4125.184.08.27.01R VICTARA_E
(bootloader) version-baseband[1]: MEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g4338799 ([email protected]
(bootloader) kernel.version[1]: ilclbld27) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Dec 4 10:30:40 CST 2014
(bootloader) sdi.git: git=MBM-NG-V60.11-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.11-0-g0d2c7a3
(bootloader) rpm.git: git=MBM-NG-V60.11-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.11-0-g1de0fa8
(bootloader) aboot.git: git=MBM-NG-V60.11-0-g72b218f
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: retgb
all: listed above
finished. total time: 0.109s
Fingers crossed it'll help.
Best,
j.e.d.

Strangely - all I get is a blank element for <value>. I'm also on retGB, unlocked bootloader as well. This handset was bought straight from Motorola's site.
fastboot oem config carrier
...
(bootloader) <UTAG name="carrier" protected="false">
(bootloader) <value>
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see google link - not allowed to post, but same as yours
(bootloader) </description>
(bootloader) </UTAG>​

jagw said:
Strangely - all I get is a blank element for <value>. I'm also on retGB, unlocked bootloader as well. This handset was bought straight from Motorola's site.
fastboot oem config carrier
...
(bootloader) <UTAG name="carrier" protected="false">
(bootloader) <value>
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see google link - not allowed to post, but same as yours
(bootloader) </description>
(bootloader) </UTAG>​
Click to expand...
Click to collapse
What"s really strange, since I ran that config command, I don't have a single SMS in Messages and can't restore it.

IrishLad said:
Hi Again,
Anyone out there able to help with checking their Carrier ID?
Thanks
Click to expand...
Click to collapse
You seemed to be too desperate not to reply at all.

Thanks
josecartman said:
You seemed to be too desperate not to reply at all.
Click to expand...
Click to collapse
Hi All,
Thanks for the replies, and my late check in, was travelling for work, I also had someone confirm for me via PM.
It does look like it should be blank, but I can't figure out how to remove the carrier ID I entered in error.
The issue it causes me is the APN, they appear to be setup but don't work, if I manually create them again it works fine with the same settings.
So I assume the ID is doing something odd.
Looking at flashing a complete custom ROM to hopefully erase the carrier ID then flash back to stock.
Unless anyone has any other advice I think I'll try this and post the results in the coming days.

XT1053 invalid CID

My wife recently got a fitbit, and we were trying to connect it to her 2013 Moto X. After repeated failures, and attempts to connect the phone to other devices, other devices to the phone, and other phones to the fitbit, I concluded that there was a Bluetooth issue with the Moto X - it can't see other devices, and other devices can't see it either. A factory reset didn't help. The phone was using the stock ROM, never unlocked, never rooted. This was her first Bluetooth device, so we don't really know if Bluetooth ever worked.
With the phone long out of warranty, I decided to unlock the boot loader and flash the stock firmware. After successfully flashing the 'ghost' firmware (downloadable in another thread here, since the official firmware from Motorola's site fails with the stagefright update), Bluetooth still didn't work. At some point, the phone offered to install the stagefright update, which I allowed. After the update the phone rebooted into the boot loader, with a message "fastboot reason: invalid cid". The screen also indicates that the bootloader is now locked.
At this point, I can't get it to boot to any other screen. Fastboot devices can see the phone, though the device ID is now different than it was before flashing (is this normal?), but I can't do anything with it because it's locked. Fastboot oem get_unlock_data fails, as does fastboot oem unlock .
Am I screwed?
Sent from my SM-T713 using Tapatalk

UncleMike said:
My wife recently got a fitbit, and we were trying to connect it to her 2013 Moto X. After repeated failures, and attempts to connect the phone to other devices, other devices to the phone, and other phones to the fitbit, I concluded that there was a Bluetooth issue with the Moto X - it can't see other devices, and other devices can't see it either. A factory reset didn't help. The phone was using the stock ROM, never unlocked, never rooted. This was her first Bluetooth device, so we don't really know if Bluetooth ever worked.
With the phone long out of warranty, I decided to unlock the boot loader and flash the stock firmware. After successfully flashing the 'ghost' firmware (downloadable in another thread here, since the official firmware from Motorola's site fails with the stagefright update), Bluetooth still didn't work. At some point, the phone offered to install the stagefright update, which I allowed. After the update the phone rebooted into the boot loader, with a message "fastboot reason: invalid cid". The screen also indicates that the bootloader is now locked.
At this point, I can't get it to boot to any other screen. Fastboot devices can see the phone, though the device ID is now different than it was before flashing (is this normal?), but I can't do anything with it because it's locked. Fastboot oem get_unlock_data fails, as does fastboot oem unlock .
Am I screwed?
Sent from my SM-T713 using Tapatalk
Click to expand...
Click to collapse
Paste the results please..
fastboot getvar all

Here's the output from 'fastboot getvar all':
Code:
(bootloader) version-bootloader: 30BE(*)
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Hynix S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x8300
(bootloader) radio: 0x6
(bootloader) secure: yes
(bootloader) mid: 026b
(bootloader) serialno: 47cc93b8
(bootloader) qe:
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: F9D920040C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Invalid CID
(bootloader) ro.build.date:
(bootloader) ro.build.id:
(bootloader) ro.build.tags:
(bootloader) ro.build.type:
(bootloader) ro.build.user:
(bootloader) ro.build.version.codename:
(bootloader) ro.build.version.incremental:
(bootloader) ro.build.version.release:
(bootloader) ro.mot.build.customerid:
(bootloader) ro.product.name:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) kernel.version:

System UI has stopped, Phone locked

Hey All,
Device - Motorola One Power
Status - Completely in Stock condition
OS Version - 10(QPTS30.61-18-3)
After I changed a wallpaper on the phone, a popup "System UI has stopped" is perpetually occurring on top of my lock-screen which is making me unable to unlock or use the phone.
User is given with two options on the popup error, App info and Stop app, selecting any of these will give a blank screen and error will popup again repeating the same process.
Situation - USB Debugging is not enabled, USB connection settings set to charging as default.
Troubleshooting and results
1. Normal Mode - Fingerprint accepted, vibration feedback received, PIN mandatory, cannot login as display goes blank after every touch.
2. Safe Mode - Same issues as normal boot.
3. USB OTG-Mouse - Mouse pointer appears on top of the popup error, cannot dismiss, same issue as normal and safe boot.
4. Emergency call mode - Popup appears even on the emergency call.
5. Wipe Cache is unavailable in recovery as the I guess it's the new seamless A/B data structure.
Situation : Data is not backed up and Full Userdata wipe is not an option..
Wipe Data is not an option as I have the only copy of photos of recent family get-together and baby cousin's birthday which I could not back up due to lack of personal time.
Is there any way to get my data back ?
Fastboot?
ADB Zip Sideload?
Factory Mode?
Please help me out guys
Thanks

Anyone?
Please help guys

Jack_731 said:
Anyone?
Please help guys
Click to expand...
Click to collapse
Without USB debugging enabled,
I don't think there are any options.
You could try to flash firmware and skip the
erase userdata command
But with the bootloader lock likely
Flashing is blocked.
Sent from my ali using XDA Labs

sd_shadow said:
Without USB debugging enabled,
I don't think there are any options.
You could try to flash firmware and skip the
erase userdata command
But with the bootloader lock likely
Flashing is blocked.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Thank you for replying
USB Debugging is disabled, but when I boot to Recovery and go to 'load zip using ADB', ADB gets loaded in "Sideload" mode and the device is visible in Sideload mode in ADB command prompt.
Questions
1) Can I an sideload an official OTA Zip on a locked bootloader?
Here is a link from google support on that same sideload method for Google Pixel https://support.google.com/pixelphone/thread/17016500?hl=en&dark=1
Am referring to that cause my phone is running Android One, and they have migrated the data structure into the new A/B seamless partition.
Thank you again

Jack_731 said:
Thank you for replying
USB Debugging is disabled, but when I boot to Recovery and go to 'load zip using ADB', ADB gets loaded in "Sideload" mode and the device is visible in Sideload mode in ADB command prompt.
Questions
1) Can I an sideload an official OTA Zip on a locked bootloader?
Here is a link from google support on that same sideload method for Google Pixel https://support.google.com/pixelphone/thread/17016500?hl=en&dark=1
Am referring to that cause my phone is running Android One, and they have migrated the data structure into the new A/B seamless partition.
Thank you again
Click to expand...
Click to collapse
Possibly, but Motorola doesn't openly share the OTA updates like Google
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Possibly, but Motorola doesn't openly share the OTA updates like Google
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Here is a link to a tool made by members of xda https://forum.xda-developers.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039
and here is another link of firmwares for motorola one power https://mirrors.lolinet.com/firmware/moto/chef/official/RETIN/
Can you guide on how should I try this way?
Please help me out
Thanks

Anyone here with the expertise and knowledge to guide me through the process?
Any kind of link or guide or steps in which I can revive my on-device data?
Please help me out.
It will be very helpful to me ..

Anyone?
Any help will be appreciated
Thanks..

[
Jack_731 said:
Hi,
Will this method work on Locked BLs, and if USB Debug is off?
My Phone - Moto One Power
Click to expand...
Click to collapse
I don't think the ota update method is going to work.
But editing the erase userdata line
Then flashing with LMSA may
As discussed here
https://forum.xda-developers.com/g5-plus/how-to/how-to-flash-stock-loosing-data-t3871703

Jack_731 said:
Hey @sd_shadow
this is what I get on my Moto One Power (fastboot getvar all)
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-chef_retail-38523c9-200122
(bootloader) product: chef
(bootloader) board: chef
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ZF6223TFLL
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: FDF7898C
(bootloader) verity-state: enforcing (0)
No more info from bootloader.
BL = Locked
USB Debug = Locked
Unrooted
Is there anything I should do?
Thanks
Click to expand...
Click to collapse
I don't know over half the lines are missing
You should have more like this
Code:
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 11-20-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4006
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -39-6-2/d2226:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.461.11.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g496fe5a (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Oct 31 07:27:03 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-eca8056-191031
(bootloader) git:xbl: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:pmic: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-191031
(bootloader) git:tz: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:hyp: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:devcfg: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:keymaster: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:prov: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:storsec: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.250s

Hey, I just saw your post in my Pixel 3a thread (link if anyone is curious), sorry to hear you ended up in the same boat.
For what it's worth, my 3a suffered from a screen issue before. It's very unlikely (though not impossible) that something was corrupted being processed, but I wanted to add this thought.
Anyway, I hope you find a solution if nothing from my thread works. Although somewhat chaotic (and sometimes unconventional by freezing the UI before it crashes/restarts), it featured every bit me and others were able to think of.
In the end, only a factory reset helped and I lost all data in the process.
I would have been able to rescue everything, if I only had one more second between crashes or hadn't I rebooted in the meantime (no fingerprint allowed), sadly such small obstacles can be complete roadblocks.
So, sorry for not being of bigger help, but if you manage to find a solution which might be applicable to the 3a as well, I'd happily add it to my thread, too.
Good luck.

sysuicrash0511 said:
Hey, I just saw your post in my Pixel 3a thread (link if anyone is curious), sorry to hear you ended up in the same boat.
For what it's worth, my 3a suffered from a screen issue before. It's very unlikely (though not impossible) that something was corrupted being processed, but I wanted to add this thought.
Anyway, I hope you find a solution if nothing from my thread works. Although somewhat chaotic (and sometimes unconventional by freezing the UI before it crashes/restarts), it featured every bit me and others were able to think of.
In the end, only a factory reset helped and I lost all data in the process.
I would have been able to rescue everything, if I only had one more second between crashes or hadn't I rebooted in the meantime (no fingerprint allowed), sadly such small obstacles can be complete roadblocks.
So, sorry for not being of bigger help, but if you manage to find a solution which might be applicable to the 3a as well, I'd happily add it to my thread, too.
Good luck.
Click to expand...
Click to collapse
Hey there,
I think we understand each others problems very well,
Don't be sorry, your post has actually helped me understand that am not alone with the current issue.
This is a serious issue in Android Devices (System UI has stopped), and I guess more than 80% of the consumers don't know anything about USB Debugging or would keep that enabled.
First of all, an error popup should not be front and center on any UI, the pop-up should be dismiss-able / can be minimized away from the general display area of any device.
Just like when in older Android UI, even an incoming-call used to take the entire screen, but nowadays, they are part of notifications, if the user is focusing on another app.
The fact that this 'System UI' error occurred on the latest Android 10 update (Feb 2020), makes it even worse., that Android hasn't matured yet to be stable.
In hindsight, yes if we had not restarted the phone the moment we face that "System UI keeps stopping" error, the in-device data could have been saved 100%.
Cause the phone was functional even after the error pops up, and there are certain ways we can circumvent it (except restarting).
At least Google is publicly providing OTAs for Pixels so that users can try sideloading.
Motorola doesn't provide anything official, even though it's an "Android One" device.
I guess I will have to do factory reset after all , If nothing turns up positive.
Will keep you posted.
Thanks
Cheers

sd_shadow said:
I don't know over half the lines are missing
You should have more like this
Code:
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 11-20-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4006
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -39-6-2/d2226:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.461.11.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g496fe5a (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Oct 31 07:27:03 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-eca8056-191031
(bootloader) git:xbl: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:pmic: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-191031
(bootloader) git:tz: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:hyp: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:devcfg: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:keymaster: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:prov: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:storsec: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.250s
Click to expand...
Click to collapse
This was the error message displayed after the command.
Code:
getvar:all FAILED (status read failed (Too many links))
Is there any hardware issue with the phone?

Hey @sd_shadow,
Can you check these recovery logs to get a clearer picture of this issue?
Especially these lines
Code:
ro.adb.secure=1
ro.mot.security.enable=1
ro.opa.eligible_device=true
ro.secure=1
ro.debuggable=0
ro.oem_unlock_supported=1
ro.boot.flash.locked=1
ro.boot.write_protect=0
ro.boot.secure_hardware=1
1) Does it means it is flash protected?
2) If 'fastboot getvar all' command result is not completely getting loaded, does that mean "fastboot flash" command is out of bounds?
Thanks..

Jack_731 said:
Hey @sd_shadow,
Can you check these recovery logs to get a clearer picture of this issue?
Especially these lines
Code:
ro.adb.secure=1
ro.mot.security.enable=1
ro.opa.eligible_device=true
ro.secure=1
ro.debuggable=0
ro.oem_unlock_supported=1
ro.boot.flash.locked=1
ro.boot.write_protect=0
ro.boot.secure_hardware=1
1) Does it means it is flash protected?
2) If 'fastboot getvar all' command result is not completely getting loaded, does that mean "fastboot flash" command is out of bounds?
Thanks..
Click to expand...
Click to collapse
@sd_shadow
What do you think?
Am a bit concerned , as If I may get stuck while flashing and this phone will end up useless.
If 'fastboot getvar all' command result is not completely getting loaded, does that mean "fastboot flash" command is out of bounds?
Thanks

After 10 Hours... I need help, please: "Invalid zip file format! error installing zip

After 10 Hours... I need help, please: "Invalid zip file format! error installing zip
Guys and gals - I just want to say in advance, thank you so much for your time and help with this, I really tried hard (over 10 hours) of referencing old xda forums and youtube videos, with nothing working so far.
Ok here it goes:
So I bought for a good price the Moto g5s Plus from ali express. Everything came fine, except one thing... it had a Chinese variant baseband flashed on the phone, which means everything worked normal except I couldn't update past 7.1.1
Baseband: M8937_37.13.03.53R Montana_Chinadsds_cust
The typical phones update to 8.1 oreo, so I want to jump on that wagon. It had been about 10 years since I've flashed or unlocked anything so I was happy to find through youtube and XDA that the process was easier. But the phone came with unlocked boot.
I put TWRP on there pretty easily and everything looked like it was going to be cake.
I was getting different errors after trying different tactics of flashing - everything from error 7, to error 1, to all kinds of errors that I've overcome... but when I'd solve one error, i'd get a different error...
I spent hours of diving through youtube / xda...
Eventually it led me to that I kept getting "cant unmount" error when trying to flash roms. I realized that tha phone isn't friendly to flashing because of something called "treble" or "trebling" - one of the developers here, liquidengineer, released a version of twrp to deal with it... but it didn't work for me.
To keep it short, after like 10 hours and nothing working... I then decided to do what was in this video:
Oreo 8.1 Stock ROM on Moto G5s Plus(English):
(notice url has a space between "youtube" and ".com")
youtube .com/watch?v=-f67lVbDqkc&t=3s
The video was nice because it was step by step. I chose to do it last because it involved using a custom script.
I followed all of the steps, the script ran. What I realized after is that this script only works if original stock roms, but I had this chinese custom rom/baseband.
In short, the script wiped everything... my partitions, files, etc...
TWRP Recovery still worked so I changed the format of the partitions to E2, then E4, that allowed me to use the phone as a drive and add the roms.
when I try to install any rom in TWRP 3.1.1-1... I now just get:
data successfully decrypted, new block device:
'/dev/block/dm-0'
Updating Partition Details....
...done
Successfully decrypted with default password.
Updating partition details...
...done
Full SELinux Support is present.
MTP Enabled
Installing zip file '/sdcard/arrow-v10.0-sanders-OFFICIAL-20200329-VANILLA.zip'
Invalid zip file format!
Error installign zip file '/sdcard/arrow-v10.0-sanders-OFFICIAL-20200329-VANILLA.zip'
Updating partition details...
...done.
It doesn't matter which rom i try to install.
Factory recovery doesn't work.
I also get a Motorola error that my phone has been unlocked and cant be trusted (bad ID).
I kept this post as short as I could, and didn't include all of the different attempts I tried.... but I am now completely lost as to what to do. Please, please help! I'll paypal someone $10 for the winning answer.
-----------------------------------
Current Bootscreen:
AP Fastboot Flash Mode (Secure)
BL: BC.06(*) (sha-865eb9a-diety. 2017-07-07 15:02:25)
Bandbase: M8937_37.13.03.53R Montana_Chinadsds_cust
Product/Variant: montana XT1799-2 64 gb p3
Serial #: I have one
CPU: MSM8937
eMMC: 64 GB Samsung etc...
DRAM: 4GB SAMSUNG etc...
Console [Null]: null
Tools Mode Confid: DISABLED
BATTERY OK
flashing_unlocked
Software status: modified
Connect USB Data Cable
(as of now - using TWRP 3.1.1-1 (boots normal))

If you really have the g5s plus aka sanders, and fastboot says Montana - someone flashed a g5s aka Montana firmware, which is never a good idea.
Try flashing Sanders firmware. If that doesn't work, enjoy the paperweight

Phazmos said:
If you really have the g5s plus aka sanders, and fastboot says Montana - someone flashed a g5s aka Montana firmware, which is never a good idea.
Try flashing Sanders firmware. If that doesn't work, enjoy the paperweight
Click to expand...
Click to collapse
yes that did look odd to me. I'm not so familiar with flashing firmware, do you have any good guidance with that?

smbfission said:
yes that did look odd to me. I'm not so familiar with flashing firmware, do you have any good guidance with that?
Click to expand...
Click to collapse
What's
Code:
fastboot getvar all
give you?
Please post it here after you remove the IMEI line

Hey shadow, i feel like an idiot. It's been 10 years since I've done any of this stuff and I'm realizing there are 2 things going on...
first - even though I bought a g5s Plus (also called sanders), that's not what I got. I unknowingly got a g5s (without the plus). Still, it should have installed probably anyway... regardless of whether it's a plus or not. So not sure why I get the errors - will that happen if the phone distro's don't match?
Finally, the moto g5s's are not all the same, because they each carry their own country. And in my case, I have the xt1799-2 - which is the chinese ZUI variant (customized lenovo version), which makes it more complex.
One guy sent me this: https://forum.xda-developers.com/moto-g5s/how-to/guide-moto-g5sxt179x-stock-rom-t3839003/amp/
however... the problem is because he uses the Chinese language firmware, it still seems he's stuck in 7.1.1 which won't even allow me to use custom roms because most of them rely on the 8.1 oreo firmware. Do you guys see holes in his approach?
Although to answer your question, do you want me just to run that function?
sd_shadow said:
What's
Code:
fastboot getvar all
give you?
Please post it here after you remove the IMEI line
Click to expand...
Click to collapse

smbfission said:
Hey shadow, i feel like an idiot. It's been 10 years since I've done any of this stuff and I'm realizing there are 2 things going on...
first - even though I bought a g5s Plus (also called sanders), that's not what I got. I unknowingly got a g5s (without the plus). Still, it should have installed probably anyway... regardless of whether it's a plus or not. So not sure why I get the errors - will that happen if the phone distro's don't match?
Finally, the moto g5s's are not all the same, because they each carry their own country. And in my case, I have the xt1799-2 - which is the chinese ZUI variant (customized lenovo version), which makes it more complex.
One guy sent me this: https://forum.xda-developers.com/moto-g5s/how-to/guide-moto-g5sxt179x-stock-rom-t3839003/amp/
however... the problem is because he uses the Chinese language firmware, it still seems he's stuck in 7.1.1 which won't even allow me to use custom roms because most of them rely on the 8.1 oreo firmware. Do you guys see holes in his approach?
Although to answer your question, do you want me just to run that function?
Click to expand...
Click to collapse
The getvar all give a lot of info about what is going on with the device.
So yes please.

Thanks so much in advance:
Just one note - even though it says I have a rom, i cant boot into it because as mentioned, i ran a script for g5s+ and it more or less corrupted it.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.06(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322WHXP7
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: 758A323800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) I removed this as mentioned
(bootloader) meid:
(bootloader) date: 09-06-2018
(bootloader) sku: XT1799-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 18 5: 1:50 UTC 1971"
(bootloader) ro.build.fingerprint[0]: motorola/montana_retcn_n/montana_n
(bootloader) ro.build.fingerprint[1]: :7.1.1/NZS26.86-128/112:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.112.montana_re
(bootloader) ro.build.version.full[1]: tcn.retcn.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8937_37.13.03.53R MONTANA_CHINADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g647ff94-0000
(bootloader) kernel.version[1]: 7-g13fa5e2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Wed Apr
(bootloader) kernel.version[3]: 11 23:05:29 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.06-0-g518a6f1
(bootloader) rpm.git: git=aa33522-dirty
(bootloader) tz.git: git=1fe3cc8-dirty
(bootloader) devcfg.git: git=1fe3cc8-dirty
(bootloader) keymaster.git: git=1fe3cc8-dirty
(bootloader) cmnlib.git: git=1fe3cc8-dirty
(bootloader) cmnlib64.git: git=1fe3cc8-dirty
(bootloader) prov.git: git=1fe3cc8-dirty
(bootloader) aboot.git: git=MBM-NG-VBC.06-0-g865eb9a-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retcn
all: listed above
finished. total time: 1.195s
sd_shadow said:
The getvar all give a lot of info about what is going on with the device.
So yes please.
Click to expand...
Click to collapse

smbfission said:
Thanks so much in advance:
Just one note - even though it says I have a rom, i cant boot into it because as mentioned, i ran a script for g5s+ and it more or less corrupted it.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.06(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322WHXP7
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: 758A323800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) I removed this as mentioned
(bootloader) meid:
(bootloader) date: 09-06-2018
(bootloader) sku: XT1799-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 18 5: 1:50 UTC 1971"
(bootloader) ro.build.fingerprint[0]: motorola/montana_retcn_n/montana_n
(bootloader) ro.build.fingerprint[1]: :7.1.1/NZS26.86-128/112:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.112.montana_re
(bootloader) ro.build.version.full[1]: tcn.retcn.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8937_37.13.03.53R MONTANA_CHINADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g647ff94-0000
(bootloader) kernel.version[1]: 7-g13fa5e2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Wed Apr
(bootloader) kernel.version[3]: 11 23:05:29 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.06-0-g518a6f1
(bootloader) rpm.git: git=aa33522-dirty
(bootloader) tz.git: git=1fe3cc8-dirty
(bootloader) devcfg.git: git=1fe3cc8-dirty
(bootloader) keymaster.git: git=1fe3cc8-dirty
(bootloader) cmnlib.git: git=1fe3cc8-dirty
(bootloader) cmnlib64.git: git=1fe3cc8-dirty
(bootloader) prov.git: git=1fe3cc8-dirty
(bootloader) aboot.git: git=MBM-NG-VBC.06-0-g865eb9a-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retcn
all: listed above
finished. total time: 1.195s
Click to expand...
Click to collapse
So, the correct Firmware for your device is Montana/RetCN/XT1799-2
https://mirrors.lolinet.com/firmware/moto/montana_retcn/official/RETCN/
which looks like has only been updated to 7.1.1 blur 26.68-117
You could try Retail software channel
https://mirrors.lolinet.com/firmware/moto/montana/official/RETAIL/
But I can't tell which model that is for...
RetEU is XT1793/XT1794
RetGB is XT1794
Doesn't look like there is a RetUS which is preferred if you live in the USA.
and I'm not seeing if there are any hardware differences between them.
I guess I would flash RetCN just to get it back to stock and working again.
If that goes good, try the Retail.
I've posted some general flashing instructions in
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039

sd_shadow said:
So, the correct Firmware for your device is Montana/RetCN/XT1799-2
https://mirrors.lolinet.com/firmware/moto/montana_retcn/official/RETCN/
which looks like has only been updated to 7.1.1 blur 26.68-117
You could try Retail software channel
https://mirrors.lolinet.com/firmware/moto/montana/official/RETAIL/
But I can't tell which model that is for...
RetEU is XT1793/XT1794
RetGB is XT1794
Doesn't look like there is a RetUS which is preferred if you live in the USA.
and I'm not seeing if there are any hardware differences between them.
I guess I would flash RetCN just to get it back to stock and working again.
If that goes good, try the Retail.
I've posted some general flashing instructions in
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Click to expand...
Click to collapse
Quick question - it seems that the Russians have a lot more support and roms for xt1799-2, because probably they buy from aliexpress. What I don't get is if you take this thread, https://4pda.ru/forum/index.php?showtopic=886009&st=260#entry76570414 (translate with google translate chrome extension)
people are installing custom ROM For XT1799-2
crDroid v4.7.2 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=89050911
crDroid v5.11 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=92946311
Do they first install the stock 7.1.1 firmware? and then the ROM, even though 4.7.2 is Android 8.1, and crDroid 5.11 is Android 9.0?
Does the firmware version need to match the ROM version?
Also, if i want to avoid risking to mess up the bootloader, can i just leave out the following:
fastboot of flash partition gpt.bin
fastboot of flash the bootloader bootloader.img

smbfission said:
Quick question - it seems that the Russians have a lot more support and roms for xt1799-2, because probably they buy from aliexpress. What I don't get is if you take this thread, https://4pda.ru/forum/index.php?showtopic=886009&st=260#entry76570414 (translate with google translate chrome extension)
people are installing custom ROM For XT1799-2
crDroid v4.7.2 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=89050911
crDroid v5.11 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=92946311
Do they first install the stock 7.1.1 firmware? and then the ROM, even though 4.7.2 is Android 8.1, and crDroid 5.11 is Android 9.0?
Does the firmware version need to match the ROM version?
Also, if i want to avoid risking to mess up the bootloader, can i just leave out the following:
fastboot of flash partition gpt.bin
fastboot of flash the bootloader bootloader.img
Click to expand...
Click to collapse
I believe they are on stock 7.1.1, and installing the updated custom rom.
Likely there is not much of 7.1.1 left other than the bootloader.
Sent from my ali using XDA Labs

Unlock and Root Moto E5 Play

Hi there everyone. This post of a question is going to be long. So, bear with me. A week ago I decided I wanted to unlock and root my Motorola E5 Play that I have been using with Consumer Cellular as the carrier for nearly a year. I have done this once before with my previous Android phone, so, naturally, I follow instructions to be found on websites, including those to be found on xda forums. The process did not go as expected. I installed the right Moto drivers on my laptop, installed adb utilities, got the Motorola unlock code via a portal to be found here on xda, and proceeded with the typical process. I can't remember all of the frustrations I had, but, basically, I ended up flashing the stock ROM for my phone just to get it usable again, and then discovered I had lost radio transceiver capabilities. I could not connect to Consumer Cellular's network to make or receive calls. The little icon for your cell signal strength was gone. I did a little reading on flashing necessary firmware for your phone's radio transceiver, but since I could find nothing about Consumer Cellular and the idea of going by specifications for my model phone and figuring it out without specific instructions seemed too much, I ultimately decided to buy a carrier unlocked model of my phone, take out the sim-card from my old phone and put it into the new phone. The new phone (or renewed should I say) was the exact same model of Moto E5 Play I had, it worked on the GSM networks, and so I have a working phone again. The only little problem was that, originally, the phone I just bought was an AT&T phone. So, I see the AT&T logo when I turn the phone on, and there are a couple of other quirks here and there, but once I backed up Android data to this phone from Google's Cloud everything was back. However, I still would like the benefits of a rooted smartphone, whether it be programs like SDMaid Pro having more access to clean your phone deeper, or being able to uninstall bloatware, customize boot up animations, etc.
So, after having screwed up as I did, I thought it might be best to pay a professional to unlock and root this newly bought renewed phone of mine. I tried making use of oneclickroot.com, but the operator there told me my phone is not eligible for OEM unlocking. This leads me to two requests of you guys here at xda. One of which may get this thread removed, and the other of which hopefully will be satisfied if this thread is not taken down due to the first request.
Request #1:
-------------------------
I know these phones are made with the capability of being unlocked. If it is not eligible for unlocking then it has something to do with the carrier. I know this because my previous phone (a Verizon Prepaid) was not eligible for unlocking when I got it years ago, but a nice and entrepreneurial Motorola employee looking to make a little money on the side over in China was gracious enough to email me the unlock code once I sent him $45 dollars via Paypal. So, if any of you know how to get my Consumer Cellular Moto E5 Play XT-1921-2 unlock code, be it this way, that way, or the other way, then, please, do tell.
Request #2:
--------------------------
I need some good instructions for unlocking and rooting this phone without screwing it up like I did the last one. If this involves extra steps like flashing needed firmware for the chipset the radio transceiver uses that is OK (I believe this model phone uses QualComm). I just need those steps spelled out and listed.
So, the grand goal here is an unlocked and rooted Motorola Android phone of mine. Relevant device information is below.
Model: Motorola E5 Play XT-1921-2
OS: Android 8.0.0 Oreo
Network: GSM
Carrier: Consumer Cellular
Radio Transceiver Chipset: Some version of QualComm
Baseband version: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
Build Number: OCPS27.91-157-15
Any help would be greatly appreciated.
***This question was originally posted by me in the general discussion area of xda forums for unlocking and not here like I was told should have been by a guy that replied to the question. I have reposted it here, and below I am including what he requested of me when the executing of the command "fastboot getvar all". The information returned by that command should be of help to whomever can assist me.***
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 9
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY323GTQV8
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 854514E600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359542090844190
(bootloader) meid:
(bootloader) date: 11-23-2018
(bootloader) sku: XT1921-2
(bootloader) carrier_sku: 6798BB
(bootloader) battid:
(bootloader) iccid: 89014103271819071604
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_a/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-157-15/16:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.16.james_a.a.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gb838762-0007
(bootloader) kernel.version[1]: 1-g3aa9cf9 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 12 02:30:49 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=083cf5f-dirty
(bootloader) devcfg.git: git=083cf5f-dirty
(bootloader) keymaster.git: git=083cf5f
(bootloader) cmnlib.git: git=083cf5f
(bootloader) cmnlib64.git: git=083cf5f
(bootloader) prov.git: git=083cf5f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: att
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.396s

vindy1099 said:
Hi there everyone. This post of a question is going to be long. So, bear with me. A week ago I decided I wanted to unlock and root my Motorola E5 Play that I have been using with Consumer Cellular as the carrier for nearly a year. I have done this once before with my previous Android phone, so, naturally, I follow instructions to be found on websites, including those to be found on xda forums. The process did not go as expected. I installed the right Moto drivers on my laptop, installed adb utilities, got the Motorola unlock code via a portal to be found here on xda, and proceeded with the typical process. I can't remember all of the frustrations I had, but, basically, I ended up flashing the stock ROM for my phone just to get it usable again, and then discovered I had lost radio transceiver capabilities. I could not connect to Consumer Cellular's network to make or receive calls. The little icon for your cell signal strength was gone. I did a little reading on flashing necessary firmware for your phone's radio transceiver, but since I could find nothing about Consumer Cellular and the idea of going by specifications for my model phone and figuring it out without specific instructions seemed too much, I ultimately decided to buy a carrier unlocked model of my phone, take out the sim-card from my old phone and put it into the new phone. The new phone (or renewed should I say) was the exact same model of Moto E5 Play I had, it worked on the GSM networks, and so I have a working phone again. The only little problem was that, originally, the phone I just bought was an AT&T phone. So, I see the AT&T logo when I turn the phone on, and there are a couple of other quirks here and there, but once I backed up Android data to this phone from Google's Cloud everything was back. However, I still would like the benefits of a rooted smartphone, whether it be programs like SDMaid Pro having more access to clean your phone deeper, or being able to uninstall bloatware, customize boot up animations, etc.
So, after having screwed up as I did, I thought it might be best to pay a professional to unlock and root this newly bought renewed phone of mine. I tried making use of oneclickroot.com, but the operator there told me my phone is not eligible for OEM unlocking. This leads me to two requests of you guys here at xda. One of which may get this thread removed, and the other of which hopefully will be satisfied if this thread is not taken down due to the first request.
Request #1:
-------------------------
I know these phones are made with the capability of being unlocked. If it is not eligible for unlocking then it has something to do with the carrier. I know this because my previous phone (a Verizon Prepaid) was not eligible for unlocking when I got it years ago, but a nice and entrepreneurial Motorola employee looking to make a little money on the side over in China was gracious enough to email me the unlock code once I sent him $45 dollars via Paypal. So, if any of you know how to get my Consumer Cellular Moto E5 Play XT-1921-2 unlock code, be it this way, that way, or the other way, then, please, do tell.
Request #2:
--------------------------
I need some good instructions for unlocking and rooting this phone without screwing it up like I did the last one. If this involves extra steps like flashing needed firmware for the chipset the radio transceiver uses that is OK (I believe this model phone uses QualComm). I just need those steps spelled out and listed.
So, the grand goal here is an unlocked and rooted Motorola Android phone of mine. Relevant device information is below.
Model: Motorola E5 Play XT-1921-2
OS: Android 8.0.0 Oreo
Network: GSM
Carrier: Consumer Cellular
Radio Transceiver Chipset: Some version of QualComm
Baseband version: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
Build Number: OCPS27.91-157-15
Any help would be greatly appreciated.
***This question was originally posted by me in the general discussion area of xda forums for unlocking and not here like I was told should have been by a guy that replied to the question. I have reposted it here, and below I am including what he requested of me when the executing of the command "fastboot getvar all". The information returned by that command should be of help to whomever can assist me.***
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 9
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY323GTQV8
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 854514E600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359542090844190
(bootloader) meid:
(bootloader) date: 11-23-2018
(bootloader) sku: XT1921-2
(bootloader) carrier_sku: 6798BB
(bootloader) battid:
(bootloader) iccid: 89014103271819071604
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_a/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-157-15/16:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.16.james_a.a.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gb838762-0007
(bootloader) kernel.version[1]: 1-g3aa9cf9 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 12 02:30:49 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=083cf5f-dirty
(bootloader) devcfg.git: git=083cf5f-dirty
(bootloader) keymaster.git: git=083cf5f
(bootloader) cmnlib.git: git=083cf5f
(bootloader) cmnlib64.git: git=083cf5f
(bootloader) prov.git: git=083cf5f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: att
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.396s
Click to expand...
Click to collapse
First I would try LMSA's Flash Rescue option with device in fastboot mode.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk