So I have a G7 Power from Metro. Bootloader is unlocked, TWRP is not loaded yet, device DOES NOT have an IMEI right now.
I am attaching some screenshots of the main details of my phone. I am at a loss as to what to do next. Someone please help me. I am pretty sure that I need to find a way to put an IMEI on the phone before I can do anything with it, right???
Motorola_Moto_XT1955-5_OCEAN_PPO29.114-63_CID50 -- this is the build I used when I flashed in from hard brick. I did try a couple other builds but this is the only one that went full way through, and booted up.
crazyc5127 said:
So I have a G7 Power from Metro. Bootloader is unlocked, TWRP is not loaded yet, device DOES NOT have an IMEI right now.
I am attaching some screenshots of the main details of my phone. I am at a loss as to what to do next. Someone please help me. I am pretty sure that I need to find a way to put an IMEI on the phone before I can do anything with it, right???
Motorola_Moto_XT1955-5_OCEAN_PPO29.114-63_CID50 -- this is the build I used when I flashed in from hard brick. I did try a couple other builds but this is the only one that went full way through, and booted up.
Click to expand...
Click to collapse
You destroyed the baseband
Sent from my LG-LS997 using Tapatalk
cgigate said:
You destroyed the baseband
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
any way to repair it?
crazyc5127 said:
any way to repair it?
Click to expand...
Click to collapse
If you don't have backup, try to flash thr blankflash
Sent from my LG-LS997 using Tapatalk
cgigate said:
If you don't have backup, try to flash thr blankflash
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
thats what i used to be able to see the phone and get it back into fastboot after the hard brick.
crazyc5127 said:
thats what i used to be able to see the phone and get it back into fastboot after the hard brick.
Click to expand...
Click to collapse
Try to flash back the original version firmware (before it got brick) to see if it brings back baseband. If not , you may need to pull off from the same variant phone
Sent from my LG-LS997 using Tapatalk
cgigate said:
Try to flash back the original version firmware (before it got brick) to see if it brings back baseband. If not , you may need to pull off from the same variant phone
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
i ran a getvar all cmd and i can see the IMEI there, but the baseband is not found. And I didn't fully prepare for this task, as i didnt do a back-up before i tried flashing TWRP, which resulted in the hard brick.
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
How did you get a Verizon bootloader installed ?
Sent from my moto g(7) power using Tapatalk
MrCamby said:
How did you get a Verizon bootloader installed ?
Click to expand...
Click to collapse
Fastboot your factory image for your model device. Bootloader is part of it... Without a bootloader I believe the phone is a brick. I believe these have more than one bootloader. That may not be correct but seems like I read that somewhere. But not all AB partition Android devices are the same. My Pixel XL was AB and I never bricked it like I did in the beginning with my G7 Power.
Try to flash stock without wiping userdata
Related
Hey Guys,
I got a bricked Moto G from a friend of mine. The device boots untill it gets to the m logo and then reboots. Device doesn't boot into recovery or doesn't do a factory reset. But i can get into fastboot.
I'm familiar with nexus and samsung devices so I already tried a lot of things but nothing seems to work.
I unlocked the bootloader but no change, tried to reflash stock firmware (RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF_SVC) via mfastboot but no change.
I tried the hard bricked tutorial found on this forum but my device shows up as fastboot falcon s in my device manager and is not detected when i use the driver for "Qualcomm HS-USB QLoader 9008" it keeps giving me waiting for device when trying to execute the clean flash bat.
I tried to brick the bootloader with the Bootloader bricker but it still shows up as fastboot falcon s.
Any ideas?
The device info for this device is (i deleted serial, there was no imei):
Quote:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno:
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 5EE000020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Sep 10 18:59:52 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_reteu/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/36:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.EURetail.en.EU
(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.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 05:33:52 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.057s
Press any key to continue . . .
Like I've said in the other topic, try this:
BobDiaz said:
Can you give us more details?
Like if this is really a bootloop (in wich you would see that white image with an exclamation mark for a loooong time) or if you just can't switch your phone on?
I've read about it and, in a situation like yours, the phone usually bricks...
______________________________________
Edit:
When it happened to me, I did the following:
Download and execute the .bat of this topic after installing the phone drivers.
forum. xda-developers. com/ moto-g/general/ guide-xt1033-downgrade-lollipop-5-0-to-t2969729
After this, my phone went to the GPE but it could not flash an stock rom. Than, I did this:
forum. xda-developers. com/ moto-g/general/guide-moto-g-xt1033-android-5-0-lollipop-t2979623
Follow this steps exactly the way its written and it should work.
Click to expand...
Click to collapse
Hey bobdiaz,
I didn't see a reply on the other thread from you but this didn't happen when downgrading. It has always been a 4.4.4 but i wil try the things you suggest!
Oké the explanation you gave me does not resolve my problem.
But i'm pretty sure the brick doesn't come from a downgrade from version 5.
Any other suggestions?
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.
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!