i have a DX and i tried up some RÓMs
But now i can't boot my phone and it has vibrated 7 times when i turned on / boot to bootloader
I relocked bootloader
I install RUU.zip but it had error
sending 'zip' (375648 KB)...
OKAY [ 35.104s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 107.404s
Click to expand...
Click to collapse
i checked var and here is
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: UNKNOWN SHIP S-ON
(bootloader) serialno: u+næg"öa6ü?¡S+?
(bootloader) imei: 358835
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: ¦ò£e¦˜ªñ(Éè·-Q-~=¼-Q)¼=p±/ `oj\±
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-f3c065d3
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
Click to expand...
Click to collapse
My serial and model id is invalid and now i can't unlock bootloader.
please help me
Sorry dude. It most probably is bricked. I had same problem and only fix was another motherboard.
Sent from my HTC Desire X using XDA Free mobile app
Hello ...
I'm Trying To Flash HTC M7_WLS :
here The Var Info :
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.5555
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: FA35SS901094
(bootloader) imei: 355859056067481
(bootloader) meid: 99000146845583
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN072000000bkp s1se=68
co-e'x0x
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3720mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Trying to Flash it with is Rom : PN07IMG_M7_WL_L50_SENSE60_MR_VERIZON_WWE_6.22.605.3_R1_Radio_1.13.41.1209_NV_VZW_4.64_002_release_429680_partial_2_4
Failed with this Erorr :
HTML:
C:\Android\sdk1\platform-tools>fastboot flash zip "H:\New folder (4)\PARTIRAL\PN
07IMG_M7_WL_L50_SENSE60_MR_VERIZON_WWE_6.22.605.3_R1_Radio_1.13.41.1209_NV_VZW_4
.64_002_release_429680_partial_2_4.zip"
target reported max download size of 1526722560 bytes
sending 'zip' (46695 KB)...
OKAY [ 2.913s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.963s
any Suggest ? Any Solution ?
Thanks !
today my Moto E won't start. recently my mobile flashed a bug which i ignored now it is stuck to Motorola logo only..
what should I do please help..Please send me the details of how to unlock my Moto E XT1022.
Then I tried to unlock it and was unable..I'm attaching those results hope it helps..
HELP!!!
H:\Android\sdk\platform-tools> fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 3A55640206907587#5A583142333358
(bootloader) 364E5600585431303232000000#8D5A
(bootloader) 110BB311F3B8D086226093D55305A8B
(bootloader) 52E26#97B9FE0412000000000000000
(bootloader) 0000000
OKAY [ 0.267s]
finished. total time: 0.267s
H:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: 500E
(bootloader) product: condor
(bootloader) secure: yes
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x5
(bootloader) emmc: 4GB Hynix REV=06 PRV=05 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8210 CS
(bootloader) serialno: ZX1B34RQXN
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: 97B9FE0412000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 299892736
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355462060095778
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Feb 22 16:27:51 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/condor_retaildsds/condor_
(bootloader) ro.build.fingerprint[1]: umtsds:5.1/LPCS23.13-34.8-3/3:user
(bootloader) ro.build.fingerprint[2]: /release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.201.3.condor_reta
(bootloader) ro.build.version.full[1]: ildsds.retaildsdsall.en.03
(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:
(bootloader) kernel.version[0]: Linux version 3.4.42-g70ad15f ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Feb 22 10:19:39 CST 2016
(bootloader) sdi.git: git=MBM-NG-V50.0E-0-g3ccd862
(bootloader) sbl1.git: git=MBM-NG-V50.0E-0-g20700d2
(bootloader) rpm.git: git=MBM-NG-V50.0E-0-gcebb121
(bootloader) tz.git: git=MBM-NG-V50.0E-0-g65c6b0f
(bootloader) aboot.git: git=MBM-NG-V50.0E-0-g4ed7eaf
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.126s
3A55640206907587#5A583142333358364E5600585431303232000000#8D5A110BB311F3B8D086226093D55305A8B52E26#97B9FE04120000000000000000000000
Copy only this much to get unlock key.
Thanks for the reply. I tried it but the website said that my mobile does not qualify for bootloader unlocking..
I posted lenovo forum,still no reply..
what should i do to reinstall a fresh os??
Ujwal Agrawal said:
3A55640206907587#5A583142333358364E5600585431303232000000#8D5A110BB311F3B8D086226093D55305A8B52E26#97B9FE04120000000000000000000000
Copy only this much to get unlock key.
Click to expand...
Click to collapse
Same problem for me
Same happened with me but fortunately i got the key and unlocked the bootloader but now when i am trying to flash stock kitkat rom with mfastboot its failed every time.
is there any way to install TWRP in this case ?? Please
Akil Imran said:
Same happened with me but fortunately i got the key and unlocked the bootloader but now when i am trying to flash stock kitkat rom with mfastboot its failed every time.
is there any way to install TWRP in this case ?? Please
Click to expand...
Click to collapse
If you have unlocked your bootloader then first flash the latest twrp v3.0.2.0 . After flashing twrp then go to recovery from your phone. Clean the rom which is installed and then flash the Rom.
Phone is not turning on
Ankit_29 said:
If you have unlocked your bootloader then first flash the latest twrp v3.0.2.0 . After flashing twrp then go to recovery from your phone. Clean the rom which is installed and then flash the Rom.
Click to expand...
Click to collapse
Thanks bro but my phone is not turning on it stuck on motorola unlock bootlaoder sign.. is any way to install twrp in this case if yes plz help
Akil Imran said:
Thanks bro but my phone is not turning on it stuck on motorola unlock bootlaoder sign.. is any way to install twrp in this case if yes plz help
Click to expand...
Click to collapse
It seems that you have soft bricked your phone.
Just flash twrp through mfastboot note that android debugging must be on.
For better step by step instructions check this video on YouTube
The video is too long but well explained.
It all started when I wanted to root my phone so that I could move more apps to my sd card. I followed this tutorial: https://www.theworldsbestandworst.com/2020/06/root-motorola-moto-e5-play/ but the version of SuperSU they had me install bricked my phone (My phone would freeze on startup at the t-mobile logo).
So, having done so in the past, I knew I could flash the stock firmware and hopefully get my phone back to working condition. I tried using two different downloads of the stock firmware. One from here: https://sourceforge.net/projects/moto-e5-firmware/files/JAMES/XT1921-3/ and one from here: https://forum.xda-developers.com/t/...he-e5-play-xt1921-3-t-mobile-variant.3839675/ (it's the link first given by timjames474). For both downloads I used the batch file method of flashing described here:
because RSDLite wasn't detecting my device. However, both of the times I tried flashing the stock firmware my phone worked normally but was unable to detect my sim card.
Was I using the wrong download of stock firmware? Is my phone broken for good? Please help me.
tezcatlipoca7123 said:
It all started when I wanted to root my phone so that I could move more apps to my sd card. I followed this tutorial: https://www.theworldsbestandworst.com/2020/06/root-motorola-moto-e5-play/ but the version of SuperSU they had me install bricked my phone (My phone would freeze on startup at the t-mobile logo).
So, having done so in the past, I knew I could flash the stock firmware and hopefully get my phone back to working condition. I tried using two different downloads of the stock firmware. One from here: https://sourceforge.net/projects/moto-e5-firmware/files/JAMES/XT1921-3/ and one from here: https://forum.xda-developers.com/t/...he-e5-play-xt1921-3-t-mobile-variant.3839675/ (it's the link first given by timjames474). For both downloads I used the batch file method of flashing described here:
because RSDLite wasn't detecting my device. However, both of the times I tried flashing the stock firmware my phone worked normally but was unable to detect my sim card.
Was I using the wrong download of stock firmware? Is my phone broken for good? Please help me.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Here is what my terminal returns when I enter getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.45
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(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: ZY323SRCZP
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 09E5223100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146092420788
(bootloader) meid:
(bootloader) date: 03-18-2019
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-51-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5480efb-0001
(bootloader) kernel.version[1]: 6-gd2768b6 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 20 10:36:48 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB9.45-0-geb7a3e0
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=5fefee4-dirty
(bootloader) devcfg.git: git=5fefee4-dirty
(bootloader) keymaster.git: git=5fefee4
(bootloader) cmnlib.git: git=5fefee4
(bootloader) cmnlib64.git: git=5fefee4
(bootloader) prov.git: git=5fefee4-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.45-0-gff56367
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(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.772s
tezcatlipoca7123 said:
Here is what my terminal returns when I enter getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.45
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(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: ZY323SRCZP
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 09E5223100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146092420788
(bootloader) meid:
(bootloader) date: 03-18-2019
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-51-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5480efb-0001
(bootloader) kernel.version[1]: 6-gd2768b6 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 20 10:36:48 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB9.45-0-geb7a3e0
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=5fefee4-dirty
(bootloader) devcfg.git: git=5fefee4-dirty
(bootloader) keymaster.git: git=5fefee4
(bootloader) cmnlib.git: git=5fefee4
(bootloader) cmnlib64.git: git=5fefee4
(bootloader) prov.git: git=5fefee4-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.45-0-gff56367
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(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.772s
Click to expand...
Click to collapse
The firmware you are using should be correct.
getvar say baseband is missing
Code:
(bootloader) version-baseband: <not found>
and both system slots are INVALID
Not a good sign.
You didn't see any flashing errors?
RSD Lite doesn't work with Windows 10, do you have a Windows 7 machine?
Try posting the service.xml text in https://kfhost.net/flashfile
and compare with your batch file.
sd_shadow said:
The firmware you are using should be correct.
getvar say baseband is missing
Code:
(bootloader) version-baseband: <not found>
and both system slots are INVALID
Not a good sign.
You didn't see any flashing errors?
RSD Lite doesn't work with Windows 10, do you have a Windows 7 machine?
Try posting the service.xml text in https://kfhost.net/flashfile
and compare with your batch file.
Click to expand...
Click to collapse
The batch file I had was slightly different than the one produced by the website you had me use. I replaced the batch file's contents and flashed the firmware again. I got these errors (not sure if 'image signed with key bad key' is an error so I'm including it just incase):
(bootloader) is-logical:FSG: not found
Sending 'FSG' (1696 KB) OKAY [ 0.222s]
Writing 'FSG' (bootloader) Invalid partition name FSG
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logicalSP: not found
Sending 'DSP' (16384 KB) OKAY [ 0.689s]
Writing 'DSP' (bootloader) Invalid partition name DSP
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.526s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.553s]
Finished. Total time: 1.279s
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.698s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.584s]
Finished. Total time: 1.316s
I got the same bad key errors when I flashed the firmware with my first batch file. After this flash the phone still works normally besides not being able to read the sim card.
tezcatlipoca7123 said:
The batch file I had was slightly different than the one produced by the website you had me use. I replaced the batch file's contents and flashed the firmware again. I got these errors (not sure if 'image signed with key bad key' is an error so I'm including it just incase):
(bootloader) is-logical:FSG: not found
Sending 'FSG' (1696 KB) OKAY [ 0.222s]
Writing 'FSG' (bootloader) Invalid partition name FSG
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logicalSP: not found
Sending 'DSP' (16384 KB) OKAY [ 0.689s]
Writing 'DSP' (bootloader) Invalid partition name DSP
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.526s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.553s]
Finished. Total time: 1.279s
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.698s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.584s]
Finished. Total time: 1.316s
I got the same bad key errors when I flashed the firmware with my first batch file. After this flash the phone still works normally besides not being able to read the sim card.
Click to expand...
Click to collapse
Strange you shouldn't have a recovery.img
Can you attach the service.xml ?
sd_shadow said:
Strange you shouldn't have a recovery.img
Can you attach the service.xml ?
Click to expand...
Click to collapse
I did have twrp on my phone before the flash
Here's the servicefile.xml, the firmware doesn't have a service.xml:
tezcatlipoca7123 said:
I did have twrp on my phone before the flash
Click to expand...
Click to collapse
Devices with a/b system slots don't have a recovery partition it's part of the boot.img now
so now when you install Twrp or magisk the boot partition must be changed.
Here's the servicefile.xml, the firmware doesn't have a service.xml:
Click to expand...
Click to collapse
Yes, my bad
Try just
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Tried it, each command comes back "OKAY". My phone still can't read the sim card though.
tezcatlipoca7123 said:
Tried it, each command comes back "OKAY". My phone still can't read the sim card though.
Click to expand...
Click to collapse
Windows 10?
sd_shadow said:
Windows 10?
Click to expand...
Click to collapse
Yes, I have have an older machine but I don't know if it still works or what version it is.
tezcatlipoca7123 said:
Yes, I have have an older machine but I don't know if it still works or what version it is.
Click to expand...
Click to collapse
If it's XP or 7 you could try RSD Lite
With the current machine, have you updated adb files?
Tried different USB ports?
sd_shadow said:
If it's XP or 7 you could try RSD Lite
With the current machine, have you updated adb files?
Tried different USB ports?
Click to expand...
Click to collapse
The other pc is also windows 10 .
I'm using the most current platform-tools.
I'll try using other usb ports but my computer doesn't have trouble connecting to my phone so I'm not sure how that'd help (or if your talking about trying to get RSD Lite to work I've already tried other usb ports).
tezcatlipoca7123 said:
The other pc is also windows 10 .
Click to expand...
Click to collapse
The only time RSD Lite has worked for me with Windows 10 is if it originally shipped with 7 and was upgraded to 10.
Man any solutions? I reinstalled firmware, after unlocking bootloader then I flashed twrp and magisk using that twrp but my baseband version is unknown, IMEI unknown.
but my Wi-Fi is working fine, Can someone guide me through with it?
muneebwolf said:
Man any solutions? I reinstalled firmware, after unlocking bootloader then I flashed twrp and magisk using that twrp but my baseband version is unknown, IMEI unknown.
but my Wi-Fi is working fine, Can someone guide me through with it?
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>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: 1
(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: ZY323JV88W
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: B94B05DB00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146091881899
(bootloader) meid:
(bootloader) date: 12-17-2018
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 9:35:18 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-150-5-1-3/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.311.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gf60ba68 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue May 7 15:58:26 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=7a51f9f-dirty
(bootloader) devcfg.git: git=7a51f9f-dirty
(bootloader) keymaster.git: git=7a51f9f
(bootloader) cmnlib.git: git=7a51f9f
(bootloader) cmnlib64.git: git=7a51f9f
(bootloader) prov.git: git=7a51f9f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(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
muneebwolf said:
C:\Program Files (x86)\Minimal ADB and Fastboot>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: 1
(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: ZY323JV88W
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: B94B05DB00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146091881899
(bootloader) meid:
(bootloader) date: 12-17-2018
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 9:35:18 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-150-5-1-3/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.311.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gf60ba68 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue May 7 15:58:26 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=7a51f9f-dirty
(bootloader) devcfg.git: git=7a51f9f-dirty
(bootloader) keymaster.git: git=7a51f9f
(bootloader) cmnlib.git: git=7a51f9f
(bootloader) cmnlib64.git: git=7a51f9f
(bootloader) prov.git: git=7a51f9f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(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
Click to expand...
Click to collapse
Looks like you have this version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-5-1-3_cid21_subsidy-MPCS_RSU_regulatory-DEFAULT_CFC.xml.zip
this is the newest version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-14-13_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but that shouldn't have anything do with your problem, unless you have been flashing a different version than 27.91-150-5-1-3
The invalid slots are worrisome, often with this problem, a blankflash is needed to fix it.
Are you using flashfile.xml to get the correct flash commands?
sd_shadow said:
Looks like you have this version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-5-1-3_cid21_subsidy-MPCS_RSU_regulatory-DEFAULT_CFC.xml.zip
this is the newest version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-14-13_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but that shouldn't have anything do with your problem, unless you have been flashing a different version than 27.91-150-5-1-3
The invalid slots are worrisome, often with this problem, a blankflash is needed to fix it.
Are you using flashfile.xml to get the correct flash commands?
Click to expand...
Click to collapse
Man I used downloaded this firmware from lolinet, used all the necessary commands but still its not working, and yes I used flashfile.xml
Sorry, I did not see a form for 2022 version. So I'm posting it here:
I ran into a hurdle unlocking the bootloader on my Moto G Power (2022).
I enabled OEM unlocked and usb debugging on my phone and allow my computer access to it.
My device is listed after I entered the code: fastboot devices.
However, when I tried to find the unlock codes with the: fastboot oem get_unlock_data. I get the following error:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
The following is what I get after I used the code: fastboot getvar all
(bootloader) cpu-abi:arm64-v8a
(bootloader) snapshot-update-status:none
(bootloader) super-partition-name:super
(bootloader) is-logical: preloader_raw_b:no
(bootloader) is-logical: preloader_raw_a:no
(bootloader) is-logical:vendor_boot_a:no
(bootloader) is-logical:vendor_boot_b:no
(bootloader) is-logical: para:no
(bootloader) is-logical:misc:no
(bootloader) is-logical:boot_b:no
(bootloader) is-logical:metadata:no
(bootloader) is-logical:userdata:no
(bootloader) is-logical:mmcblk0:no
(bootloader) is-logical:boot_a:no
(bootloader) is-logical:md_udc:no
(bootloader) is-logical:super:no
(bootloader) is-logical:system_ext_a:yes
(bootloader) is-logical:system_ext_b:yes
(bootloader) is-logical: product_a:yes
(bootloader) is-logical: product_b:yes
(bootloader) is-logical:vendor_a:yes
(bootloader) is-logical:vendor_b:yes
(bootloader) is-logical:system_a:yes
(bootloader) is-logical:system_b:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:0
(bootloader) off-mode-charge:0
(bootloader) treble-enabled:true
(bootloader) is-userspace:yes
(bootloader) partition-size: preloader_raw_b:0x3FF800
(bootloader) partition-size: preloader_raw_a:0x3FF800
(bootloader) partition-size:vendor_boot_a:0x4000000
(bootloader) partition-size:vendor_boot_b:0x4000000
(bootloader) partition-size: para:0x80000
(bootloader) partition-size:misc:0x80000
(bootloader) partition-size:boot_b:0x2000000
(bootloader) partition-size:metadata:0x2000000
(bootloader) partition-size:userdata:0xC26CF8000
(bootloader) partition-size:mmcblk0:0xE8F800000
(bootloader) partition-size:boot_a:0x2000000
(bootloader) partition-size:md_udc:0x169A000
(bootloader) partition-size:super:0x220000000
(bootloader) partition-size:system_ext_a:0x25760000
(bootloader) partition-size:system_ext_b:0x0
(bootloader) partition-size: product_a:0x11F654000
(bootloader) partition-size: product_b:0x0
(bootloader) partition-size:vendor_a:0x1B8A5000
(bootloader) partition-size:vendor_b:0x0
(bootloader) partition-size:system_a:0x3FB3A000
(bootloader) partition-size:system_b:0x2F5E000
(bootloader) version-vndk:30
(bootloader) partition-type: preloader_raw_b:raw
(bootloader) partition-type: preloader_raw_a:raw
(bootloader) partition-type:vendor_boot_a:raw
(bootloader) partition-type:vendor_boot_b:raw
(bootloader) partition-type: para:raw
(bootloader) partition-type:misc:raw
(bootloader) partition-type:boot_b:raw
(bootloader) partition-type:metadata:raw
(bootloader) partition-type:userdata:raw
(bootloader) partition-type:mmcblk0:raw
(bootloader) partition-type:boot_a:raw
(bootloader) partition-type:md_udc:raw
(bootloader) partition-type:super:raw
(bootloader) partition-type:system_ext_a:raw
(bootloader) partition-type:system_ext_b:raw
(bootloader) partition-type: product_a:raw
(bootloader) partition-type: product_b:raw
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-type:system_a:raw
(bootloader) partition-type:system_b:raw
(bootloader) has-slot: preloader_raw:yes
(bootloader) has-slot:vendor_boot:yes
(bootloader) has-slot: para:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:boot:yes
(bootloader) has-slot:metadata:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:mmcblk0:no
(bootloader) has-slot:md_udc:no
(bootloader) has-slot:super:no
(bootloader) has-slot:system_ext:yes
(bootloader) has-slot: product:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:system:yes
(bootloader) security-patch-level:2022-03-01
(bootloader) vendor-fingerprint:motorola/tonga_g/tonga:11/RRQ31.Q3-68-140
(bootloader) /d6db2d:user/release-keys
(bootloader) hw-revision: pVT
(bootloader) current-slot:a
(bootloader) serialno:ZY22G2VF57
(bootloader) product:tonga
(bootloader) version-os:11
(bootloader) first-api-level:30
(bootloader) slot-count:2
(bootloader) max-download-size:0x10000000
(bootloader) version:0.4
(bootloader) version-baseband:
(bootloader) secure:yes
(bootloader) variant:NA
(bootloader) dynamic-partition:true
(bootloader) system-fingerprint:motorola/tonga_g/tonga:11/RRQ31.Q3-68-140
(bootloader) /d6db2d:user/release-keys
(bootloader) version-bootloader:MBM-2.1-tonga_g-79f07f8d82-220330
(bootloader) unlocked:no
all:
Finished. Total time: 0.427s
Anyone ran into similar issues and have a solution?
Edit: some how the : p was changed to the smiley face. I changed them back.
Don't know but I seen that updating security patches might help in another forum. Good luck to you. I will need to unlock a Power 2022 soon so hopefully I have better luck than you did.
Make sure you are trying the unlock from the bootloader and not fastbootd by doing 'adb reboot bootloader' while booted to android. I found that the issue usually happens because of trying to unlock from fastbootd which it can't do.
Moosetears said:
Don't know but I seen that updating security patches might help in another forum. Good luck to you. I will need to unlock a Power 2022 soon so hopefully I have better luck than you did.
Click to expand...
Click to collapse
Best of luck to you.
Alvin64DD said:
Make sure you are trying the unlock from the bootloader and not fastbootd by doing 'adb reboot bootloader' while booted to android. I found that the issue usually happens because of trying to unlock from fastbootd which it can't do.
Click to expand...
Click to collapse
The bootloader mode does not recognize the fastboot commands. So, maybe I misunderstand what you mean by bootloader. I didn't touch anything after using the adb reboot bootloader command. Not all, but most fastboot commnads works in fastboot mode (adb reboot bootloader -> recovery mode -> fastboot).
MooseXBaller said:
The bootloader mode does not recognize the fastboot commands. So, maybe I misunderstand what you mean by bootloader. I didn't touch anything after using the adb reboot bootloader command. Not all, but most fastboot commnads works in fastboot mode (adb reboot bootloader -> recovery mode -> fastboot).
Click to expand...
Click to collapse
The bootloader mode should be the menu with the android logo in the center along with device information on the bottom left of the screen. At that point, you can run the unlock commands. You can also get to that mode by holding down Power and Volume Down.
I was not getting adb or fastboot commands to work until I typed
MooseXBaller said:
Sorry, I did not see a form for 2022 version. So I'm posting it here:
I ran into a hurdle unlocking the bootloader on my Moto G Power (2022).
I enabled OEM unlocked and usb debugging on my phone and allow my computer access to it.
My device is listed after I entered the code: fastboot devices.
However, when I tried to find the unlock codes with the: fastboot oem get_unlock_data. I get the following error:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
The following is what I get after I used the code: fastboot getvar all
(bootloader) cpu-abi:arm64-v8a
(bootloader) snapshot-update-status:none
(bootloader) super-partition-name:super
(bootloader) is-logical: preloader_raw_b:no
(bootloader) is-logical: preloader_raw_a:no
(bootloader) is-logical:vendor_boot_a:no
(bootloader) is-logical:vendor_boot_b:no
(bootloader) is-logical: para:no
(bootloader) is-logical:misc:no
(bootloader) is-logical:boot_b:no
(bootloader) is-logical:metadata:no
(bootloader) is-logical:userdata:no
(bootloader) is-logical:mmcblk0:no
(bootloader) is-logical:boot_a:no
(bootloader) is-logical:md_udc:no
(bootloader) is-logical:super:no
(bootloader) is-logical:system_ext_a:yes
(bootloader) is-logical:system_ext_b:yes
(bootloader) is-logical: product_a:yes
(bootloader) is-logical: product_b:yes
(bootloader) is-logical:vendor_a:yes
(bootloader) is-logical:vendor_b:yes
(bootloader) is-logical:system_a:yes
(bootloader) is-logical:system_b:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:0
(bootloader) off-mode-charge:0
(bootloader) treble-enabled:true
(bootloader) is-userspace:yes
(bootloader) partition-size: preloader_raw_b:0x3FF800
(bootloader) partition-size: preloader_raw_a:0x3FF800
(bootloader) partition-size:vendor_boot_a:0x4000000
(bootloader) partition-size:vendor_boot_b:0x4000000
(bootloader) partition-size: para:0x80000
(bootloader) partition-size:misc:0x80000
(bootloader) partition-size:boot_b:0x2000000
(bootloader) partition-size:metadata:0x2000000
(bootloader) partition-size:userdata:0xC26CF8000
(bootloader) partition-size:mmcblk0:0xE8F800000
(bootloader) partition-size:boot_a:0x2000000
(bootloader) partition-size:md_udc:0x169A000
(bootloader) partition-size:super:0x220000000
(bootloader) partition-size:system_ext_a:0x25760000
(bootloader) partition-size:system_ext_b:0x0
(bootloader) partition-size: product_a:0x11F654000
(bootloader) partition-size: product_b:0x0
(bootloader) partition-size:vendor_a:0x1B8A5000
(bootloader) partition-size:vendor_b:0x0
(bootloader) partition-size:system_a:0x3FB3A000
(bootloader) partition-size:system_b:0x2F5E000
(bootloader) version-vndk:30
(bootloader) partition-type: preloader_raw_b:raw
(bootloader) partition-type: preloader_raw_a:raw
(bootloader) partition-type:vendor_boot_a:raw
(bootloader) partition-type:vendor_boot_b:raw
(bootloader) partition-type: para:raw
(bootloader) partition-type:misc:raw
(bootloader) partition-type:boot_b:raw
(bootloader) partition-type:metadata:raw
(bootloader) partition-type:userdata:raw
(bootloader) partition-type:mmcblk0:raw
(bootloader) partition-type:boot_a:raw
(bootloader) partition-type:md_udc:raw
(bootloader) partition-type:super:raw
(bootloader) partition-type:system_ext_a:raw
(bootloader) partition-type:system_ext_b:raw
(bootloader) partition-type: product_a:raw
(bootloader) partition-type: product_b:raw
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-type:system_a:raw
(bootloader) partition-type:system_b:raw
(bootloader) has-slot: preloader_raw:yes
(bootloader) has-slot:vendor_boot:yes
(bootloader) has-slot: para:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:boot:yes
(bootloader) has-slot:metadata:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:mmcblk0:no
(bootloader) has-slot:md_udc:no
(bootloader) has-slot:super:no
(bootloader) has-slot:system_ext:yes
(bootloader) has-slot: product:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:system:yes
(bootloader) security-patch-level:2022-03-01
(bootloader) vendor-fingerprint:motorola/tonga_g/tonga:11/RRQ31.Q3-68-140
(bootloader) /d6db2d:user/release-keys
(bootloader) hw-revision: pVT
(bootloader) current-slot:a
(bootloader) serialno:ZY22G2VF57
(bootloader) product:tonga
(bootloader) version-os:11
(bootloader) first-api-level:30
(bootloader) slot-count:2
(bootloader) max-download-size:0x10000000
(bootloader) version:0.4
(bootloader) version-baseband:
(bootloader) secure:yes
(bootloader) variant:NA
(bootloader) dynamic-partition:true
(bootloader) system-fingerprint:motorola/tonga_g/tonga:11/RRQ31.Q3-68-140
(bootloader) /d6db2d:user/release-keys
(bootloader) version-bootloader:MBM-2.1-tonga_g-79f07f8d82-220330
(bootloader) unlocked:no
all:
Finished. Total time: 0.427s
Anyone ran into similar issues and have a solution?
Edit: some how the : p was changed to the smiley face. I changed them back.
Click to expand...
Click to collapse
After I did what this page shows you to do it worked for me
[Solved]“ADB Is Not Recognized As An Internal Or External Command”
ADB is an advanced command line used for debugging your android phone or for other developmental purposes. The "ADB is not recognized as an internal or
www.technewstoday.com
[Solved]“ADB Is Not Recognized As An Internal Or External Command”
ADB is an advanced command line used for debugging your android phone or for other developmental purposes. The "ADB is not recognized as an internal or
www.technewstoday.com