I just bought a new Moto G Stylus straight from Motorola website. I am familiar in general with the unlock process, as I have an unlocked/rooted Moto G6.
Anyway, I went to the Moto website using both Chrome and Firefox, and when I paste my unlock code it says that my phone is not qualified. I am unable to request an unlock code because of this. I don't understand why that would be the case, since this is straight from Motorola, and others have unlocked the phone here.
I've tried to format the unlock code myself, as well as by using the "formatter tool" on their website.
This is the unlock code I got from my phone:
Code:
(bootloader) 3A95801400567210#5A46363532334E
(bootloader) 4C4647006D6F746F2067200000#A861
(bootloader) C41232F748E8C9B0BAA949482C5A52C
(bootloader) 978A4#CBB8389400000000000000000
(bootloader) 0000000
Here is my formatted version:
Code:
3A95801400567210#5A46363532334E4C4647006D6F746F2067200000#A861C41232F748E8C9B0BAA949482C5A52C978A4#CBB83894000000000000000000000000
My phone is a sofiap retail XT2043-4.
All your info looks good to me, same formatting & length as the data that I used to unlock my Moto G Stylus. I have the same XT2043-4 SKU, also purchased from the Motorola Website. I was able to unlock my device on 5/6/2020. My best guess is that the Moto Unlock Tool is broken, or your phone is from a newer batch than mine and Motorola hasn't "authorized" your phone to be unlocked yet. I would complain to Motorola.
dafunk60 said:
All your info looks good to me, same formatting & length as the data that I used to unlock my Moto G Stylus. I have the same XT2043-4 SKU, also purchased from the Motorola Website. I was able to unlock my device on 5/6/2020. My best guess is that the Moto Unlock Tool is broken, or your phone is from a newer batch than mine and Motorola hasn't "authorized" your phone to be unlocked yet. I would complain to Motorola.
Click to expand...
Click to collapse
Thanks for that. Any suggestions on how best to complain? I found a support thread on Lenovo forums, and I posted there for help. If I get any help from there I'll make sure to add it to this thread. Here is the support thread on Lenovo site:
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809
It's a super long thread that goes on for hundreds of pages, but the thread is still up to date and being used currently.
**** UPDATE ****
I contacted Motorola support via chat, and they said they were unable to assist me with unlocking the bootloader on their end. They directed me to the exact same thread that I posted above.
kholdstayr said:
Thanks for that. Any suggestions on how best to complain? I found a support thread on Lenovo forums, and I posted there for help. If I get any help from there I'll make sure to add it to this thread. Here is the support thread on Lenovo site:
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809
It's a super long thread that goes on for hundreds of pages, but the thread is still up to date and being used currently.
**** UPDATE ****
I contacted Motorola support via chat, and they said they were unable to assist me with unlocking the bootloader on their end. They directed me to the exact same thread that I posted above.
Click to expand...
Click to collapse
Unfortunately I don't have any good contacts / recommendations on how to complain to Motorola. I think Motorola has a 30 day return policy. Personally, I would return the phone if I couldn't unlock the bootloader as that was one of the main selling points for me. You might give Moto support chat another try. When they say they can't help unlocking the bootloader, you can ask if they can help you with a return instead. Sometimes the threat of a return allows the support rep to escalate the issue. Best of luck!
dafunk60 said:
Unfortunately I don't have any good contacts / recommendations on how to complain to Motorola. I think Motorola has a 30 day return policy. Personally, I would return the phone if I couldn't unlock the bootloader as that was one of the main selling points for me. You might give Moto support chat another try. When they say they can't help unlocking the bootloader, you can ask if they can help you with a return instead. Sometimes the threat of a return allows the support rep to escalate the issue. Best of luck!
Click to expand...
Click to collapse
This is probably a dumb question, but for unlocking, do you need to have a SIM card installed?
When I contacted chat support they asked for the phone number, but I told them it doesn't have one because I haven't put the SIM in yet. I was planning on doing that after unlocking and setting the phone up the way I want.
kholdstayr said:
This is probably a dumb question, but for unlocking, do you need to have a SIM card installed?
When I contacted chat support they asked for the phone number, but I told them it doesn't have one because I haven't put the SIM in yet. I was planning on doing that after unlocking and setting the phone up the way I want.
Click to expand...
Click to collapse
No SIM was required for me. I unlocked the bootloader & patched the boot.img with Magisk before I ever inserted a SIM.
kholdstayr said:
I just bought a new Moto G Stylus straight from Motorola website. I am familiar in general with the unlock process, as I have an unlocked/rooted Moto G6.
Anyway, I went to the Moto website using both Chrome and Firefox, and when I paste my unlock code it says that my phone is not qualified. I am unable to request an unlock code because of this. I don't understand why that would be the case, since this is straight from Motorola, and others have unlocked the phone here.
I've tried to format the unlock code myself, as well as by using the "formatter tool" on their website.
This is the unlock code I got from my phone:
Code:
(bootloader) 3A95801400567210#5A46363532334E
(bootloader) 4C4647006D6F746F2067200000#A861
(bootloader) C41232F748E8C9B0BAA949482C5A52C
(bootloader) 978A4#CBB8389400000000000000000
(bootloader) 0000000
Here is my formatted version:
Code:
3A95801400567210#5A46363532334E4C4647006D6F746F2067200000#A861C41232F748E8C9B0BAA949482C5A52C978A4#CBB83894000000000000000000000000
My phone is a sofiap retail XT2043-4.
Click to expand...
Click to collapse
**** EDIT UPDATE ******
I was finally able to get the Motorola site to work, but I don't know why it works today when it didn't work yesterday.
Yesterday when I was trying to do the unlock, I saved the unlock data from my phone into a text file, and I've been using the same text file copy+paste every time I've tried to request the unlock code from Motorola.
There is one difference from yesterday vs today. Today when I tried it, I logged into the phone with my Google account, and then logged into the Motorola site using the same Google account. I don't know why that would make a difference, but that is it. Also, I used Chrome with no adblockers turned on. After requesting the unlock code, I received it in my email about 2 minutes later. The unlock code worked fine with no issues.
Does anyone here know if I can unlock my Moto G Stylus that I just got from MetroPCS? I want to unlock using the unlock app preinstalled on the phone, and also wondering if I can unlock the bootloader and install the stock rom to get rid of all the Metro stuff. I am new to all this, so any advice is appreciated. Thanks.
I'm going through the same issue my bootloader can't be unlock I put the code they send me and that code don't work the code is, AAAAAAAAAAAAAAAAAAAA
AFTER I ADB COMMAND WITH THIS CODE STILL DOESN'T WORK AND HONESTY I THINK IS THE WEBSITE NOT THE PHONE.
Sent from my moto g stylus using Tapatalk
god_of_wisdom said:
I'm going through the same issue my bootloader can't be unlock I put the code they send me and that code don't work the code is, AAAAAAAAAAAAAAAAAAAA
AFTER I ADB COMMAND WITH THIS CODE STILL DOESN'T WORK AND HONESTY I THINK IS THE WEBSITE NOT THE PHONE.
Click to expand...
Click to collapse
Is the code literally all A's? Then yes, that code is wrong then and it seems like a weird glitch with Motorola's email system that sent the code
Big_DDD said:
Does anyone here know if I can unlock my Moto G Stylus that I just got from MetroPCS? I want to unlock using the unlock app preinstalled on the phone, and also wondering if I can unlock the bootloader and install the stock rom to get rid of all the Metro stuff. I am new to all this, so any advice is appreciated. Thanks.
Click to expand...
Click to collapse
If you got it from MetroPCS you probably can't unlock it. You would want to buy the phone independently, not from a carrier, such as the Motorola site itself.
Do you know how to use fastboot? Run the command "fastboot getvar all" . In the long list of information you'll see a CID number. That number can help identify if the phone can be unlocked. My CID is 32.
kholdstayr said:
Is the code literally all A's? Then yes, that code is wrong then and it seems like a weird glitch with Motorola's email system that sent the code
Click to expand...
Click to collapse
What should I do
Sent from my moto g stylus using Tapatalk
god_of_wisdom said:
What should I do
Click to expand...
Click to collapse
Maybe try to request it again, or contact Motorola support.
I did they keep making excuses up.
Sent from my moto g stylus using Tapatalk
i get remote unlock error please help full getvar
Microsoft Windows [Version 10.0.19041.264]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) product: sofiap
(bootloader) board: sofiap
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 128GB SAMSUNG DV6DMB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 06 10 12
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZF6523J4FN
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid:
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-06-2020
(bootloader) sku: XT2043-4
(bootloader) carrier_sku: XT2043-4
(bootloader) battid: SB18C71380
(bootloader) battery-voltage: 3793
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofiap_t/sofiap:10/QPR30.
(bootloader) ro.build.fingerprint[1]: 80-64/777253:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_10.11.03.22R SOFIAP_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Sat Feb 22 04:
(bootloader) kernel.version[3]: 41:00 CST 2020
(bootloader) git:xbl: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:xbl_config: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:rpm: MBM-3.0-sofiap_t-ffcccb0-200222
(bootloader) git:tz: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:hyp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:devcfg: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib64: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:keymaster: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) gitrov: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:abl: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) git:qupfw: MBM-3.0-sofiap_t-f848623-200222
(bootloader) git:uefisecapp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C69985
all: listed above
finished. total time: 0.312s
---------- Post added at 05:53 PM ---------- Previous post was at 05:53 PM ----------
Microsoft Windows [Version 10.0.19041.264]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) product: sofiap
(bootloader) board: sofiap
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 128GB SAMSUNG DV6DMB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 06 10 12
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZF6523J4FN
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid:
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-06-2020
(bootloader) sku: XT2043-4
(bootloader) carrier_sku: XT2043-4
(bootloader) battid: SB18C71380
(bootloader) battery-voltage: 3793
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofiap_t/sofiap:10/QPR30.
(bootloader) ro.build.fingerprint[1]: 80-64/777253:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_10.11.03.22R SOFIAP_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Sat Feb 22 04:
(bootloader) kernel.version[3]: 41:00 CST 2020
(bootloader) git:xbl: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:xbl_config: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:rpm: MBM-3.0-sofiap_t-ffcccb0-200222
(bootloader) git:tz: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:hyp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:devcfg: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib64: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:keymaster: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) gitrov: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:abl: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) git:qupfw: MBM-3.0-sofiap_t-f848623-200222
(bootloader) git:uefisecapp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C69985
all: listed above
finished. total time: 0.312s
calijuana707 said:
(bootloader) cid: 0x0015
It seems like your phone could be unlockable. Your CID is 15 which is in the list of unlockable cids in this forum post:
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809
Click to expand...
Click to collapse
Unlocked mine last night. Went smooth.
Related
is my first time rooting and i run into some problems with my xt1955-5.
the phone no longer recognizes the sim card and imei null appears when i check for the imei i have my phone rooted so i already check into the modem folder and carrier and there is no files there.
I would appreciate the help
update i fix my problem following this steps
https://forum.xda-developers.com/showpost.php?p=80052655&postcount=117
thanks to sd_shadow for the help
zaxcast said:
is my first time rooting and i run into some problems with my xt1955-5.
the phone no longer recognizes the sim card and imei null appears when i check for the imei i have my phone rooted so i already check into the modem folder and carrier and there is no files there.
I would appreciate the help
Click to expand...
Click to collapse
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs
thanks
sd_shadow said:
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[*][Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
thanks bro i finaly fix it and dindt lost my root thanks
sd_shadow said:
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Having this same problem I think, I can't check IMEI using *#0606# (Only Serial number appears and some barcode) nor can I see anything on Settings (Both IMEI are blank, MIN, PRL version and MEID are unknown), I can only check IMEI (IMEI1 only) using "fastboot getvar all". I already tried flashing NON-HLOS.bin, erasing modems and flashing fsg, but still doesn't work. It stopped working some time after I had failed installing custom ROMs and went back to stock (I'm almost 100% sure it was working then after a few days it stopped working, it also stopped on an unrooted Moto G7 Play but still works on a Custom ROM+Magisk Moto G5)
https://forum.xda-developers.com/g7-power/help/sim-card-stopped-t4040745
https://forum.xda-developers.com/g7-power/help/lock-bootloader-oem-unlocking-t4051605 (I only ever flashed stock using eraseandupdate.bat and this thread, so it wasn't caused by "fastboot erase all". I did flash RETUS once (my device is RETBR), but that's after it'd stopped working already)
sd_shadow said:
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
so i am having a similar issue, unknown baseband, IMEI. I did try the flash of NON-HLOS.bin and fsg.mbn but did nothing. and i wasnt able to do a backup before the phone hard bricked. i did use blankflash to recover the phone from the hardbrick. then i found that pp029.114-63_cid50 worked to restore my phone to boot up the system.
crazyc5127 said:
so i am having a similar issue, unknown baseband, IMEI. I did try the flash of NON-HLOS.bin and fsg.mbn but did nothing. and i wasnt able to do a backup before the phone hard bricked. i did use blankflash to recover the phone from the hardbrick. then i found that pp029.114-63_cid50 worked to restore my phone to boot up the system.
Click to expand...
Click to collapse
What does
Code:
fastboot getvar all
Say?
sd_shadow said:
What does
Code:
fastboot getvar all
Say?
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326F5PS2
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid: BF35179D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359527093352077
(bootloader) meid:
(bootloader) date: 07-11-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C46718
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 10 14:11:44 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPO29.114-6
(bootloader) ro.build.fingerprint[1]: 3/6c5d7:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.21.72.ocean.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld107) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ma
(bootloader) kernel.version[3]: r 22 09:36:59 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_vzw-5dc80a2-200210
(bootloader) rpm.git: MBM-2.1-ocean_vzw-22daab3-200210
(bootloader) tz.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) devcfg.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) keymaster.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib64.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) prov.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) aboot.git: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.723s
crazyc5127 said:
What does
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326F5PS2
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid: BF35179D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359527093352077
(bootloader) meid:
(bootloader) date: 07-11-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C46718
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 10 14:11:44 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPO29.114-6
(bootloader) ro.build.fingerprint[1]: 3/6c5d7:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.21.72.ocean.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld107) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ma
(bootloader) kernel.version[3]: r 22 09:36:59 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_vzw-5dc80a2-200210
(bootloader) rpm.git: MBM-2.1-ocean_vzw-22daab3-200210
(bootloader) tz.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) devcfg.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) keymaster.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib64.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) prov.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) aboot.git: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.723s
Click to expand...
Click to collapse
You used the metro pcs firmware?
https://mirrors.lolinet.com/firmware/moto/ocean/official/MetroPCS/
Sent from my perry_f using XDA Labs
sd_shadow said:
You used the metro pcs firmware?
https://mirrors.lolinet.com/firmware/moto/ocean/official/MetroPCS/
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
i think it was just a blank firm to be honest. which of those firmware should i download and flash? the newest, right?
crazyc5127 said:
i think it was just a blank firm to be honest. which of those firmware should i download and flash? the newest, right?
Click to expand...
Click to collapse
Yes, it's not unusual to need to reflash firmware after using a blankflash.
Use the newest.
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Yes, it's not unusual to need to reflash firmware after using a blankflash.
Use the newest.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
just finished the flash, i am able to see all the barcodes with *#06#. thank you for the proper link, searching on my own was close but still off just a little bit.
now, my end goal for this phone is to take it off the Metro network and have it on T-Mobile network directly. i recently upgraded providers, but got a phone that, to me, isnt quite as good as the G7 Power, the REVVlry Plus. its still a great phone, as it is a moto build, but the battery is what has me not wanting to use it. any pointers on going this route? i would like to have root access as well, so i can tune and tinker more.
https://mirrors.lolinet.com/firmware/moto/ocean/official/MetroPCS/
this is what i ended up using to get my phone back to life. now the phone sits at just having an unlocked bootloader.
my goal for this phone is to remove the Metro firmware and replace it with tmobile firmware. or root to be able to use any sim card.
sd_shadow said:
Yes, it's not unusual to need to reflash firmware after using a blankflash.
Use the newest.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
You should never use the firmware to rescue your phone, that was the problem at first place to lose your baseband. Use last known working firmware to rescue
So, I connected my phone and Lenovo Moto Smart Assistant said that there was an update for my mobile, great, click download and flash after doing backups. After flashing, everything looked fine, except for one thing: it doesn't recognize the SIM card. It's not the SIM card itself, I have already tried with another one and it didn't work, while mine did in another phone. So, what should I do? The only thing I can think of is flashing back to the previous version, but when I did it bootloader.img, boot.img and dtbo.img failed, bootloader saying that it was a previous version.
Niemand385 said:
So, I connected my phone and Lenovo Moto Smart Assistant said that there was an update for my mobile, great, click download and flash after doing backups. After flashing, everything looked fine, except for one thing: it doesn't recognize the SIM card. It's not the SIM card itself, I have already tried with another one and it didn't work, while mine did in another phone. So, what should I do? The only thing I can think of is flashing back to the previous version, but when I did it bootloader.img, boot.img and dtbo.img failed, bootloader saying that it was a previous version.
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
sd_shadow said:
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff2029-200210
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY32689JZN
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 9F416CFA00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 06-14-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Feb 11 6:23: 8 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPOS29.114-
(bootloader) ro.build.fingerprint[1]: 134-10/21fefe:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.12.ocean.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld165) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Mon Fe
(bootloader) kernel.version[3]: b 10 12:45:16 CST 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-516ad1c-200210
(bootloader) rpm.git: MBM-2.1-ocean_retail-22daab3-200210
(bootloader) tz.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) devcfg.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) keymaster.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) prov.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) aboot.git: MBM-2.1-ocean_retail-0ff2029-200210
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
Niemand385 said:
run
Click to expand...
Click to collapse
Try to unlock the bootloader
It's the only way you can downgrade Moto firmware
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Setting up and Using adb.exe and fastboot.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
Sent from my ali using XDA Labs
sd_shadow said:
Try to unlock the bootloader
It's the only way you can downgrade Moto firmware
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Setting up and Using adb.exe and fastboot.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Sooo, this time it worked, thanks for the help.
I was ready to throw the towel, admit that I probably ****ed it up taking the SD card out or something and try my hand at a little hardware fix, but decided to keep up with it because, like, what's the worst that can happen when you flash something and it says that the command failed, right? A little brick never hurt anybody. So I did it, and now it recognizes the SIM again, which is great.
Is it me or the website is not allowing people to unlock their bootloader, did anybody experience this issue yet if you did please comment below let me know your thoughts.
I got Verizon I try to unlock it yesterday the bootloader it still says code fail so their isn't no Verizon unlocking on this phone.
Sent from my moto g stylus using Tapatalk
I've tried repeatedly phone was released but as of this post I'm still unable to unlock bootloader.
I got mine unlocked yesterday with no problem
i get remote unlock error please help full getvar
Microsoft Windows [Version 10.0.19041.264]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) product: sofiap
(bootloader) board: sofiap
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 128GB SAMSUNG DV6DMB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 06 10 12
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZF6523J4FN
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid:
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-06-2020
(bootloader) sku: XT2043-4
(bootloader) carrier_sku: XT2043-4
(bootloader) battid: SB18C71380
(bootloader) battery-voltage: 3793
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofiap_t/sofiap:10/QPR30.
(bootloader) ro.build.fingerprint[1]: 80-64/777253:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_10.11.03.22R SOFIAP_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Sat Feb 22 04:
(bootloader) kernel.version[3]: 41:00 CST 2020
(bootloader) git:xbl: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:xbl_config: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:rpm: MBM-3.0-sofiap_t-ffcccb0-200222
(bootloader) git:tz: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:hyp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:devcfg: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib64: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:keymaster: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) gitrov: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:abl: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) git:qupfw: MBM-3.0-sofiap_t-f848623-200222
(bootloader) git:uefisecapp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C69985
all: listed above
finished. total time: 0.312s
jcastro889 said:
I got mine unlocked yesterday with no problem
Click to expand...
Click to collapse
Show and prove photos
Sent from my moto g stylus using Tapatalk
Been knew that go ahead to the Motorola website
Sent from my moto g stylus using Tapatalk
Yep, unlocked mine on 5/6/2020.
Tried to unlock one a few days ago but it wouldn't work. I will try again today
Mine unlocked fine. Did it a few days ago
The new update came out and they gave me a dumb code that isn't working good enough
Sent from my moto g stylus using Tapatalk
I got mine unlocked it's the XT2043-5 sku
god_of_wisdom said:
The new update came out and they gave me a dumb code that isn't working good enough
Sent from my moto g stylus using Tapatalk
Click to expand...
Click to collapse
You said you got one from Verizon? More than likely it is not unlockable....
Don't get discouraged yet. You gotta think outside of the box. I had a Verizon variant Google Pixel and updated it before learning about depixel8.
Shortly there was a bounty out for the Google Pixel. Soon there was someone who found out how to break it greyed out unlocked bootloader on the Google Pixel.
What I'm trying to say is that it's not impossible to get it done if you have the right mindset, but I'd caution you from buying from Verizon. It's a respectable company, however they make their bootloaders hard to crack.
ShadowWeasel said:
You said you got one from Verizon? More than likely it is not unlockable....
Don't get discouraged yet. You gotta think outside of the box. I had a Verizon variant Google Pixel and updated it before learning about depixel8.
Shortly there was a bounty out for the Google Pixel. Soon there was someone who found out how to break it greyed out unlocked bootloader on the Google Pixel.
What I'm trying to say is that it's not impossible to get it done if you have the right mindset, but I'd caution you from buying from Verizon. It's a respectable company, however they make their bootloaders hard to crack.
Click to expand...
Click to collapse
My oem isn't grey out that's the strange part when I got the code it was a dumb code AAAAAAAAAAAAAAAAAAAA i was like wtf I thought be a code that be easy but this code hell no
Sent from my moto g stylus using Tapatalk
god_of_wisdom said:
My oem isn't grey out that's the strange part when I got the code it was a dumb code AAAAAAAAAAAAAAAAAAAA i was like wtf I thought be a code that be easy but this code hell no
Sent from my moto g stylus using Tapatalk
Click to expand...
Click to collapse
Yeah, that is a dummy code. It makes me wonder, though. Is all bootloader keys the same or unique? Many if not all says unique....
you could try mine which is 4JXK6WCCVJTD5VXEKFGV
If it works, then good. If not, I feel for you.
I had mine unlocked for 1 day and still looking how to root the thing. Many say patch the boot.img for magisk, but I cant find it...
U download the stock rom and u find the boot.img from there I will post the root method
Sent from my moto g stylus using Tapatalk
god_of_wisdom said:
U download the stock rom and u find the boot.img from there I will post the root method
Click to expand...
Click to collapse
it's been a while since I rooted a phone but what does everyone use these days to check if bootloader is unlocked
god_of_wisdom said:
U download the stock rom and u find the boot.img from there I will post the root method
Sent from my moto g stylus using Tapatalk
Click to expand...
Click to collapse
yeah, i was fatigued when i sent that last message. anyways i digress....
attempted root. failed miserably....
what happened is the same as a few others on another thread. touchscreen unresponsive. also shows no service and 0% battery.
good thing i backed up everything and downloaded the stock rom.
anyways has anyone had a successful root?
ShadowWeasel said:
yeah, i was fatigued when i sent that last message. anyways i digress....
attempted root. failed miserably....
what happened is the same as a few others on another thread. touchscreen unresponsive. also shows no service and 0% battery.
good thing i backed up everything and downloaded the stock rom.
anyways has anyone had a successful root?
Click to expand...
Click to collapse
I didn't have any problems rooting. Downloaded the stock rom with the Lenovo Rescue & Smart Assist software on my PC. Copied the boot.img to the phone & patched it with Magisk 20.4 / Magisk Manager 7.5.1. Copied the patched boot image back to my PC & flashed it via fastboot.
dafunk60 said:
I didn't have any problems rooting. Downloaded the stock rom with the Lenovo Rescue & Smart Assist software on my PC. Copied the boot.img to the phone & patched it with Magisk 20.4 / Magisk Manager 7.5.1. Copied the patched boot image back to my PC & flashed it via fastboot.
Click to expand...
Click to collapse
How did you do it? I did my 2nd attempt and still failed.
Also, comparing the boot.img is way different. The original boot.img is 60mb while the patched boot.img is about 10mb. Is that supposed to be right?
ShadowWeasel said:
How did you do it? I did my 2nd attempt and still failed.
Also, comparing the boot.img is way different. The original boot.img is 60mb while the patched boot.img is about 10mb. Is that supposed to be right?
Click to expand...
Click to collapse
All I did to root is listed in the steps above. My patched boot images are also much smaller, I think the original boot image is just padded as it's a perfect 64MB. My patched boot image is 11.8MB. All I can think of is that the boot image your patching & flashing may not be the exact version that phone is running. My phone shipped with SOFIAP_RETAIL_QPR30.80_58 & the update from last week was SOFIAP_RETAIL_QPRS30.80_58_3. Where are you getting your original boot.img file from?
Hi, I was wondering if anyone could help me to unbrick my network free moto g7 power UK dual sim edition: xt1955-4. It was working completely fine until one day it got caught in a bootloop, and then when attempting to restart again it only goes as far as the fastboot menu, where it says 'failed to validate boot image'.
I have attempted a few fixes, based on reading forum posts here, but I can't get into the recovery menu, and when I've tried to unlock the bootloader, I receive the error: 'feature disabled'. When I try to flash any firmware images using code people have given, I just get a long string of error messages, essentially telling me that the flash isn't working. My phone is listed under fastboot devices, but is not listed with adb devices (even though it shows up in device manager. LMSA is also unable to detect my phone model, which was the first fix I tried, and nor is RSD Lite.
I am completely new to this, so plz ELI5 if you have any suggestions of potential fixes. Thank you for your help!
If helpful, this is the result of the 'fastboot getvar all' command
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(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: SDM632
(bootloader) serialno: 2a4eacbd
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 5584240700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
motog7help said:
Hi, I was wondering if anyone could help me to unbrick my network free moto g7 power UK dual sim edition: xt1955-4. It was working completely fine until one day it got caught in a bootloop, and then when attempting to restart again it only goes as far as the fastboot menu, where it says 'failed to validate boot image'.
I have attempted a few fixes, based on reading forum posts here, but I can't get into the recovery menu, and when I've tried to unlock the bootloader, I receive the error: 'feature disabled'. When I try to flash any firmware images using code people have given, I just get a long string of error messages, essentially telling me that the flash isn't working. My phone is listed under fastboot devices, but is not listed with adb devices (even though it shows up in device manager. LMSA is also unable to detect my phone model, which was the first fix I tried, and nor is RSD Lite.
I am completely new to this, so plz ELI5 if you have any suggestions of potential fixes. Thank you for your help!
If helpful, this is the result of the 'fastboot getvar all' command
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(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: SDM632
(bootloader) serialno: 2a4eacbd
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 5584240700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Click to expand...
Click to collapse
I don't believe there is much hope.
There is some instructions for flashing with a locked bootloader in my thread
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Also some instructions for RSD Lite
You need Windows 7 or old for RSD Lite
For any flashing with locked bootloader you need the correct firmware
The getvar all has a lot of missing info
I'm not sure which firmware channel is the correct one.
There is a RetGB but I don't know if its dual sim
https://mirrors.lolinet.com/firmware/moto/ocean/official/RETGB/
Or it could on one of the EU channels
Like RetEU2
Sent from my ocean using XDA Labs
Thank you very much for your help! At least I was on the right track, and even though that's a shame it's most likely dead, it's good to know that it's not just an easy fix that I'm not seeing at the moment.
For flashing with a locked bootloader, is it just the firmware channel that needs to be right, or is it the actual firmware version as well? i.e. the phone broke at the beginning of September - will I need to use the OTA update from September, or is it best to just use the most up-to-date version of the firmware?
Thanks again for the guidance
motog7help said:
Thank you very much for your help! At least I was on the right track, and even though that's a shame it's most likely dead, it's good to know that it's not just an easy fix that I'm not seeing at the moment.
For flashing with a locked bootloader, is it just the firmware channel that needs to be right, or is it the actual firmware version as well? i.e. the phone broke at the beginning of September - will I need to use the OTA update from September, or is it best to just use the most up-to-date version of the firmware?
Thanks again for the guidance
Click to expand...
Click to collapse
All I need is to run a blank flash which will get u back up and running
---------- Post added at 04:09 PM ---------- Previous post was at 04:07 PM ----------
roadkill42 said:
All I need is to run a blank flash which will get u back up and running
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/gsi/. Go here and u cans find the blank flash
Thank you - I have tried a blank flash as well, but after running the .bat file, it unfortunately it just hangs on 'waiting for device' I think it is because the phone is not detected as an adb device (I didn't have usb debugging enabled when it broke).
From a quick google it looks like there's no way to change this from fastboot - does anyone have any tips for applying a blank flash when phone is not listed as an adb device on the console? (As I mentioned in the original post, under device manager it is showing up as 'Motorola ADB Interface')
U need the quilt com drivers installed to pc and the moto usb drivers
roadkill42 said:
U need the quilt com drivers installed to pc and the moto usb drivers
Click to expand...
Click to collapse
Thank you for the help - I have installed both sets of drivers, although the qualcomm drivers don't display a device under 'ports' as reported by some people. I have also tried changing drivers on the 'Motorola ADB Interface' from the Motorola specific one to a generic one, but it doesn't seem to make a difference? Is there anything I might be doing wrong here?
motog7help said:
Thank you for the help - I have installed both sets of drivers, although the qualcomm drivers don't display a device under 'ports' as reported by some people. I have also tried changing drivers on the 'Motorola ADB Interface' from the Motorola specific one to a generic one, but it doesn't seem to make a difference? Is there anything I might be doing wrong here?
Click to expand...
Click to collapse
You cannot use a blankflash unless the device is in emergency download mode (EDL)
To my knowledge the is no way to enter EDL with a locked bootloader.
Sent from my ocean using XDA Labs
https://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw fastboot oem blankflash try this comand in terminal then if screen goes black click on the blank flash .bat file should work cause u are simi bricked can go to that link I sent b easer to help
Sure try
Code:
fastboot oem blankflash
Not very likely to work with a locked bootloader.
Sent from my ocean using XDA Labs
---------- Post added at 03:40 PM ---------- Previous post was at 03:29 PM ----------
You will most likely see.
Code:
...fastboot oem blankflash
(bootloader) command restricted
FAILED (remote: '')
fastboot: error: Command failed
sd_shadow said:
Sure try
Code:
fastboot oem blankflash
Not very likely to work with a locked bootloader.
Sent from my ocean using XDA Labs
---------- Post added at 03:40 PM ---------- Previous post was at 03:29 PM ----------
You will most likely see.
Code:
...fastboot oem blankflash
(bootloader) command restricted
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Thanks for the suggestions, both. You're absolutely right - it did return the 'command restricted' result. Any last ditch ideas that I might try?
motog7help said:
Sure try
Not very likely to work with a locked bootloader.
Sent from my ocean using XDA Labs
---------- Post added at 03:40 PM ---------- Previous post was at 03:29 PM ----------
You will most likely see.
Thanks for the suggestions, both. You're absolutely right - it did return the 'command restricted' result. Any last ditch ideas that I might try?
Click to expand...
Click to collapse
RSD Lite using a Windows 7 or older PC
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ocean using XDA Labs
https://www.5g-m.com/en/micro-usb-datacable-for-android/17894-edl-cable-w230.html is said to work
Thank you - I will give both of these a try and report back!
motog7help said:
Thank you - I will give both of these a try and report back!
Click to expand...
Click to collapse
Are u able to get into the quialcom minue using the volume bottons?
can someone help me with advice to get booting again
it was oem unlocked before fail to boot
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_vzw-16222030b3b-200930
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY323W4FKR
(bootloader) cid: 0x0032
(bootloader) channelid: 0x96
(bootloader) uid: C82C277300000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359525091092315
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-17-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C28957
(bootloader) iccid: 89148000005008330805
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Oct 1 5: 5:18 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QCOS30.85-
(bootloader) ro.build.fingerprint[1]: 18-6/691ed:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Sep 30 23:2
(bootloader) kernel.version[3]: 2:14 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_vzw-a30e356d6d-200930
(bootloader) rpm.git: MBM-2.1-ocean_vzw-20f2cf34-200930
(bootloader) tz.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) devcfg.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) keymaster.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) cmnlib.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) cmnlib64.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) prov.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) aboot.git: MBM-2.1-ocean_vzw-16222030b3b-200930
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: comcast
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SP69A6P237
all: listed above
finished. total time: 0.307s
roadkill42 said:
https://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw fastboot oem blankflash try this comand in terminal then if screen goes black click on the blank flash .bat file should work cause u are simi bricked can go to that link I sent b easer to help
Click to expand...
Click to collapse
Thx, this command save me phone.
I installed a "Dynamic System Update" package and after rebooting the OS is not detected, bootloader (Vol D + Power) opens, but start and recovery lead to the same missing os screen.
Is there some way to fix this? I need my phone working
I can get to fastboot but not adb, this is `fastboot getvar all`
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-df63f3de4a8-210524
(bootloader) product: denver
(bootloader) board: denver
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM5V8001DM-B622 FV=2702 WB=2048
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_MANNAR 1.1
(bootloader) serialno: ZY22CKXBPJ
(bootloader) cid:
(bootloader) channelid: 0x99
(bootloader) uid:
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 788201472
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 06-16-2021
(bootloader) sku: XT2131-1
(bootloader) carrier_sku: XT2131-1
(bootloader) battid: SB18D00294
(bootloader) battery-voltage: 4333
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: boost
(bootloader) ro.build.fingerprint[0]: motorola/denver_global/denver:11/R
(bootloader) ro.build.fingerprint[1]: RE31.Q2-11-52/a40ec:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.9.16.r1-03500-MANNAR.0
(bootloader) version-baseband[0]: M4350_HI405_19.533.01.79R DENVER_BOOST
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 5.4.61-moto-gfa1749a591f9
(bootloader) kernel.version[1]: ([email protected]) (Android (6443078
(bootloader) kernel.version[2]: based on r383902) clang version 11.0.1
(bootloader) kernel.version[3]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[4]: ain/llvm-project b397f81060ce6d701042b78
(bootloader) kernel.version[5]: 2172ed13bee898b79), LLD 11.0.1 (/buildbo
(bootloader) kernel.version[6]: t/tmp/tmp6_m7QH b397f81060ce6d701042b782
(bootloader) kernel.version[7]: 172ed13bee898b79)) #1 SMP PREEMPT Mon Ma
(bootloader) kernel.version[8]: y 24 04:24:01 CDT 2021
(bootloader) git:xbl: MBM-3.0-uefi-71c7a1ab-210524
(bootloader) git:xbl_config: MBM-3.0-uefi-71c7a1ab-210524
(bootloader) git:abl: MBM-3.0-uefi-df63f3de4a8-210524
(bootloader) git:rpm: MBM-3.0-uefi-1573f88-210524
(bootloader) git:tz: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:hyp: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:devcfg: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:keymaster: MBM-3.0-uefi-9731016-210524
(bootloader) git:storsec: MBM-3.0-uefi-9731016-210524
(bootloader) git:uefisecapp: MBM-3.0-uefi-9731016-210524
(bootloader) gitrov: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:qupfw: MBM-3.0-uefi-7b29c10-210524
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C93368
(bootloader) primary-display: auo_nt36675_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.159s
Click to expand...
Click to collapse
ShayBox said:
I installed a "Dynamic System Update" package and after rebooting the OS is not detected, bootloader (Vol D + Power) opens, but start and recovery lead to the same missing os screen.
Is there some way to fix this? I need my phone working
I can get to fastboot but not adb, this is `fastboot getvar all`
Click to expand...
Click to collapse
The bootloader is locked, I doubt it can be fixed.
A slightly bigger doubt. How is the device detected as a PVT??
You can also just go to recovery and send us an image to show what it says , maybe the Lenovo Motorola Smart Assistant will help (QFIL flash tool with a good looking UI for Lenovo and moto devices , destroyed my tab due to the Lenovo Smart Assistant installing the firmware in a wrong method causing failures! but lets hope yours will survive!)
Slot b retry count is 0 , we could retry to set slot b as primary slot it might just work! but locked bootloaders don't allow this.... maybe just maybe you can ask Moto about this and they might be able to help , the device is QCOM based so QFIL should work (Lenovo Smart Assistant should also work????)
Seems lenovo moto smart assistant isn't working because support.lenovo.com is down until tomorrow.
Can the device be unlocked like this? or is that a bad idea.
I just got this phone 2 days ago, bought it after breaking my old free phone screen
ShayBox said:
Seems lenovo moto smart assistant isn't working because support.lenovo.com is down until tomorrow.
Can the device be unlocked like this? or is that a bad idea.
I just got this phone 2 days ago, bought it after breaking my old free phone screen
Click to expand...
Click to collapse
I doubt LMSA can help, it pulls info from the phone to match firmware.
Getvar all doesn't show the info needed, so you would just get an error from LMSA.
You should try Moto support
sd_shadow said:
I doubt LMSA can help, it pulls info from the phone to match firmware.
Getvar all doesn't show the info needed, so you would just get an error from LMSA.
You should try Moto support
Click to expand...
Click to collapse
support.motorola.com is also broken, but not for maintenance so who knows how long that will take to work again, this sucks...
EDIT: Its back online, I'll try it
IT WORKED! I used the updated lenovo software and it worked!