Related
please help I can not flahsear any firmware all come out error that can be .
I had installed rom CrDroid, I went to act to the ultma version after I made a wipe of everything and when I restart I presented this problem I
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff2029-191212
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ecb1016
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(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: 1
(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-0ff2029-191212
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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.859s
Teriuz said:
please help I can not flahsear any firmware all come out error that can be .
I had installed rom CrDroid, I went to act to the ultma version after I made a wipe of everything and when I restart I presented this problem I
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff2029-191212
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ecb1016
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(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: 1
(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-0ff2029-191212
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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.859s
Click to expand...
Click to collapse
your bootloader is locked
timba123 said:
I have the same problem XT1955-5 metro pcs G7 power. I had rooted it. After forgetting the copy partitions zip I'm stuck in AP Fastboot mode. I had oem unlocked bootloader already. Now it some how relocked. No unlock data can be read. Smh. I've tried blank flashes. I've tried lenovo rescue and my device isn't supported. I've tried various batch file flashes on windows. I've tried RSD lite. I know Samsung you can flash signed oem images with locked bootloader. Why can't lenovo or RSD flash them? I have QPST and Qfil but don't know how to use them or get the mbn programmer and various images or XML or patch files etc. Any ideas? I'd gladly donate on the 3rd of August
Click to expand...
Click to collapse
Dose up PC recognize the phone when pluged in
timba123 said:
In blank flash mode its Qualcomm loader
And fastboot works but phone seen as adb interface?
Click to expand...
Click to collapse
Can u put phone I to fastboot with the key combo
timba123 said:
It's a weird fastboot mode. Its stuck there. I can get to it from blank flash mode.
Click to expand...
Click to collapse
What dose it day in device manager on PC
timba123 said:
When it's in AP Fastboot Mode (secure) its motorola adb interface
When it's in blankflash mode its Qualcomm HS-USB QDLoader 9008 com17
Click to expand...
Click to collapse
Can u do any fastboot comands?
timba123 said:
Yes.
Click to expand...
Click to collapse
Can u type. Fastboot devices in terminal and tell me what it says
timba123 said:
a83507ca fastboot
Click to expand...
Click to collapse
Good deal I'm giving u an address for your stock firm ware https://mirrors.lolinet.com/firmware/moto/
roadkill42 said:
Good deal I'm giving u an address for your stock firm ware https://mirrors.lolinet.com/firmware/moto/
Click to expand...
Click to collapse
And this file rename it take off the zip and put bat ok
roadkill42 said:
And this file rename it take off the zip and put bat ok
Click to expand...
Click to collapse
What location is your adb folder?
roadkill42 said:
What location is your adb folder?
Click to expand...
Click to collapse
Once u downloaded the firm ware put it in ur adb folder then extract it in there and put that file I sent u in there make sure it take off the zip and put in bat ok once file and rom in adb folder look for the ocean fastboot . bat file make sure phone is still in fastboot. Also go to property of the bat file go to security tab and at bottom see if it says locked click it to unlock it then in adb folder click the bat file and sit back watch it run about 20im or less
---------- Post added at 05:40 AM ---------- Previous post was at 05:38 AM ----------
timba123 said:
Do I put the stock rom and bat files in the platform tools folder with fastboot and adb?
Click to expand...
Click to collapse
Yes I have mine on root of c and I used the minuim adb install any ways it only work if bat file is in same folder as adb and extracted rom
---------- Post added at 05:43 AM ---------- Previous post was at 05:40 AM ----------
roadkill42 said:
Once u downloaded the firm ware put it in ur adb folder then extract it in there and put that file I sent u in there make sure it take off the zip and put in bat ok once file and rom in adb folder look for the ocean fastboot . bat file make sure phone is still in fastboot. Also go to property of the bat file go to security tab and at bottom see if it says locked click it to unlock it then in adb folder click the bat file and sit back watch it run about 20im or less
---------- Post added at 05:40 AM ---------- Previous post was at 05:38 AM ----------
Yes I have mine on root of c and I used the minuim adb install any ways it only work if bat file is in same folder as adb and extracted rom
Click to expand...
Click to collapse
Then type fastboot devices before u start to make sure PC sees phone then close terminal then in ur adb folder look for the bat file make sure it renamed take off zip and put bat I noticed in the getall your bootloader is locked if this flashes u need to unlock bootloader . Well I'm hitting bed time come back here to let us know if worked or not ?
timba123 said:
Remote failure invalid partition name etc etc
Click to expand...
Click to collapse
Have screen shot of the terminal on PC and do u use tellagram? And do u have the TWRP image if so make sure PC finds phone then typ this fastboot boot (and the name of recovery img) if all goes well you should be in TWRP if thats the one u use I use ofox if that works u should be able to do factory reset then try to install costm rom try this type getval all send me screenshot of the out put of the terminal
timba123 said:
Remote failure invalid partition name etc etc
Click to expand...
Click to collapse
From what I see bootloader is locked do u have screenshot of the error from the flashing error?
timba123 said:
Everything invalid
Click to expand...
Click to collapse
Hmm try this in fastboot -w then typ fastboot reboot ok try this later then post back I'm going to talk to someone to find out what else to do night night
timba123 said:
Idk
Click to expand...
Click to collapse
https://www.getdroidtips.com/install-use-qualcomm-flash-image-loader-qfil/this looks like ur only option in ur fast boot screen on the phone showing bootloader locked u in us and what carrier u on
Have u tried to go to tellagram group Moto g7 power suport group there is most likely be able to help they more active I'm there as road kill try it out u just need the right firmware to get u going
---------- Post added at 06:08 PM ---------- Previous post was at 05:21 PM ----------
While still holding the VOL DOWN key, press and hold the POWER key
Hold both keys down for over 120 seconds. This hopefully get back into regular bootloader screen after the 120 secs 2 min realse keys to see what happens then post Bak here
timba123 said:
Thanks to Telegram group I was able to fix with blankflash. I flashed stock RETUS to my MetroPCS variant with no issues.
Click to expand...
Click to collapse
can you give me your telegram? I have the same problem and still can't solve it
Has anyone found the solution? I have the same problem.
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-0ff20295b20-200404
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(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: cfa3ac35
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(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-river_retail-0ff20295b20-200404
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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.250s
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.
So I tried flashing some gsi's and they were great other than the fact they never work with verizon(which I have). So I decided to try to rescue and go back to stock but its not reading it as the Edge. I also have tried manually flashing the .imgs but the system imgs fail to flash. Does anyone have any knowledge of what can be done to recue the phone? Thanks in advance.
JimmyJurner said:
So I tried flashing some gsi's and they were great other than the fact they never work with verizon(which I have). So I decided to try to rescue and go back to stock but its not reading it as the Edge. I also have tried manually flashing the .imgs but the system imgs fail to flash. Does anyone have any knowledge of what can be done to recue the phone? Thanks in advance.
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
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-racer_retail-d0a492fa0b-200928
(bootloader) product: racer
(bootloader) board: racer
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA5G
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB MICRON MT256GASAO8U21 FV=0109
(bootloader) ram: 6GB MICRON LP4x DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM_SAIPAN 2.0
(bootloader) serialno: ZY227SPW6K
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 7AA2E144
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: 35552611
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-16-2020
(bootloader) sku: XT2063-2
(bootloader) carrier_sku: XT2063-2
(bootloader) battid: SB18C66911
(bootloader) battery-voltage: 3796
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: unknown
(bootloader) ro.build.fingerprint[0]: Android/treble_arm64_bvN/phhgsi_ar
(bootloader) ro.build.fingerprint[1]: m64_ab:10/QQ3A.200805.001/201230:u
(bootloader) ro.build.fingerprint[2]: serdebug/release-keys
(bootloader) ro.build.version.qcom: LA.UM.8.13.r1-08200-SAIPAN.0
(bootloader) version-baseband: M7250_HI205_55.222.01.30R RACER_NA5G_CUST
(bootloader) kernel.version[0]: Linux version 4.19.81-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 Mon Sep 28 13:3
(bootloader) kernel.version[3]: 8:52 CDT 2020
(bootloader) git:xbl: MBM-3.0-racer_retail-213760469-200928
(bootloader) git:xbl_config: MBM-3.0-racer_retail-213760469-200928
(bootloader) git:abl: MBM-3.0-racer_retail-d0a492fa0b-200928
(bootloader) git:aop: MBM-3.0-racer_retail-51bfe71-200928
(bootloader) git:tz: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:hyp: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:devcfg: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:keymaster: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) git:storsec: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) git:uefisecapp: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) gitrov: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:qupfw: MBM-3.0-racer_retail-6ee337d-200928
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 2
(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: 3
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86464
all: listed above
Finished. Total time: 0.499s
JimmyJurner said:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-racer_retail-d0a492fa0b-200928
(bootloader) product: racer
(bootloader) board: racer
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA5G
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB MICRON MT256GASAO8U21 FV=0109
(bootloader) ram: 6GB MICRON LP4x DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM_SAIPAN 2.0
(bootloader) serialno: ZY227SPW6K
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 7AA2E144
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355526110607947
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-16-2020
(bootloader) sku: XT2063-2
(bootloader) carrier_sku: XT2063-2
(bootloader) battid: SB18C66911
(bootloader) battery-voltage: 3796
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: unknown
(bootloader) ro.build.fingerprint[0]: Android/treble_arm64_bvN/phhgsi_ar
(bootloader) ro.build.fingerprint[1]: m64_ab:10/QQ3A.200805.001/201230:u
(bootloader) ro.build.fingerprint[2]: serdebug/release-keys
(bootloader) ro.build.version.qcom: LA.UM.8.13.r1-08200-SAIPAN.0
(bootloader) version-baseband: M7250_HI205_55.222.01.30R RACER_NA5G_CUST
(bootloader) kernel.version[0]: Linux version 4.19.81-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 Mon Sep 28 13:3
(bootloader) kernel.version[3]: 8:52 CDT 2020
(bootloader) git:xbl: MBM-3.0-racer_retail-213760469-200928
(bootloader) git:xbl_config: MBM-3.0-racer_retail-213760469-200928
(bootloader) git:abl: MBM-3.0-racer_retail-d0a492fa0b-200928
(bootloader) git:aop: MBM-3.0-racer_retail-51bfe71-200928
(bootloader) git:tz: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:hyp: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:devcfg: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:keymaster: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) git:storsec: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) git:uefisecapp: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) gitrov: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:qupfw: MBM-3.0-racer_retail-6ee337d-200928
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 2
(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: 3
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86464
all: listed above
Finished. Total time: 0.499s
Click to expand...
Click to collapse
Lmsa likely not working because of this
Code:
bootloader) ro.carrier: unknown
You are flashing racer/RetUS?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
sd_shadow said:
Lmsa likely not working because of this
Code:
bootloader) ro.carrier: unknown
You are flashing racer/RetUS?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
Yes and the error message is "the device missed ro.carrier" in the smart asst.
this is the outcome of trying to fastboot flash
fastboot flash system C:\ProgramData\LMSA\Download\RomFiles\RACER_RETAIL_QPD30.114_80_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml\super.img_sparsechunk.0
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
JimmyJurner said:
Yes and the error message is "the device missed ro.carrier" in the smart asst.
this is the outcome of trying to fastboot flash
fastboot flash system C:\ProgramData\LMSA\Download\RomFiles\RACER_RETAIL_QPD30.114_80_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml\super.img_sparsechunk.0
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Can you post the servicefile.xml ?
As an attachment if you can.
sd_shadow said:
Can you post the servicefile.xml ?
As an attachment if you can.
Click to expand...
Click to collapse
That file?
JimmyJurner said:
Yes and the error message is "the device missed ro.carrier" in the smart asst.
this is the outcome of trying to fastboot flash
fastboot flash system C:\ProgramData\LMSA\Download\RomFiles\RACER_RETAIL_QPD30.114_80_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml\super.img_sparsechunk.0
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
I'm not familiar with super.img, but the service.xml says
Code:
<step MD5="66475a16cefbb5f6bbaebfcf23defd25" filename="super.img_sparsechunk.0" operation="flash" partition="super"/>
which if flashing manually should be: fastboot, operation, partition, filename
Code:
fastboot flash super super.img_sparsechunk.0
Every time you are going to flash a new firmware you should be looking at the service.xml to see the current commands, they do change from time to time.
or use Rootjunky's Batch Script.
Easy way to create a batch script for flashing firmware
RSD_Lite_Motorola_XML_To_Batch_Script.zip
[Video]How to Firmware Restore your Motorola Device on Windows 10 without RSDlite by RootJunky
sd_shadow said:
I'm not familiar with super.img, but the service.xml says
Code:
<step MD5="66475a16cefbb5f6bbaebfcf23defd25" filename="super.img_sparsechunk.0" operation="flash" partition="super"/>
which if flashing manually should be: fastboot, operation, partition, filename
Code:
fastboot flash super super.img_sparsechunk.0
Click to expand...
Click to collapse
I'm going to give it a try now. If all fails I'll just make a flash all.bat and see if that works. Thank you for all your help! I know what you mean about the super.img. Things keep changing once you get used to it it changes again...
JimmyJurner said:
I'm going to give it a try now. If all fails I'll just make a flash all.bat and see if that works. Thank you for all your help! I know what you mean about the super.img. Things keep changing once you get used to it it changes again...
Click to expand...
Click to collapse
I've done some searching and Super does appear to be the new partition.
Code:
fastboot flash super super.img_sparsechunk.0
sd_shadow said:
I've done some searching and Super does appear to be the new partition.
Code:
]
fastboot flash super super.img_sparsechunk.0
Click to expand...
Click to collapse
That way did end up flashing!
So I took a flash all from my other motos firmware and modded it from 14 super.img to the 7 for this device moved all the files over started the bat file and my phone is stock once again. I think I'll be staying stock from now on(rooted of course)!
Hi, I have installed a custom rom and unintentionally stopped the installation process.
The oem is locked and won't let me unlock.
Start Up Failed
No Bootable A/B slot
Failed to boot Linux, falling back fastboot
TheKillerMaxOfficial said:
Hi, I have installed a custom rom and unintentionally stopped the installation process.
The oem is locked and won't let me unlock.
Start Up Failed
No Bootable A/B slot
Failed to boot Linux, falling back fastboot
Click to expand...
Click to collapse
You relocked bootloader or it relocked it self?
sd_shadow said:
You relocked bootloader or it relocked it self?
Click to expand...
Click to collapse
it self
TheKillerMaxOfficial said:
it self
Click to expand...
Click to collapse
I'm not sure what causes the problem, or what the issue really is, could be corrupt bootloader.
Only fix I've seen is boot to EDL mode and use a blankflash.
You can try LMSA' Flash rescue first
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Not likely to fix but worth trying.
Assuming that doesn't work run
Getvar all
Code:
fastboot getvar all
To see device info, and post here.
Then try
Code:
fastboot oem blankflash
If that works device screen will turn black, and Window device manager will list it as a Qualcomm device.
If you get an error with that command you need to try booting Twrp and use
Code:
adb boot edl
You then need a blankflash for your device
You likely have Ocean, getvar all will tell.
If so try these
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
sd_shadow said:
I'm not sure what causes the problem, or what the issue really is, could be corrupt bootloader.
Only fix I've seen is boot to EDL mode and use a blankflash.
You can try LMSA' Flash rescue first
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Not likely to fix but worth trying.
Assuming that doesn't work run
Getvar all
Code:
fastboot getvar all
To see device info, and post here.
Then try
Code:
fastboot oem blankflash
If that works device screen will turn black, and Window device manager will list it as a Qualcomm device.
If you get an error with that command you need to try booting Twrp and use
Code:
adb boot edl
You then need a blankflash for your device
You likely have Ocean, getvar all will tell.
If so try these
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-7fd887897c6-200930
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: f104484
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(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: 1
(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-7fd887897c6-200930
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.144s
sd_shadow said:
I'm not sure what causes the problem, or what the issue really is, could be corrupt bootloader.
Only fix I've seen is boot to EDL mode and use a blankflash.
You can try LMSA' Flash rescue first
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Not likely to fix but worth trying.
Assuming that doesn't work run
Getvar all
Code:
fastboot getvar all
To see device info, and post here.
Then try
Code:
fastboot oem blankflash
If that works device screen will turn black, and Window device manager will list it as a Qualcomm device.
If you get an error with that command you need to try booting Twrp and use
Code:
adb boot edl
You then need a blankflash for your device
You likely have Ocean, getvar all will tell.
If so try these
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 4.057] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.057] Check qboot_log.txt for more details
[ 4.057] Total time: 4.060s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
TheKillerMaxOfficial said:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-7fd887897c6-200930
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: f104484
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(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: 1
(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-7fd887897c6-200930
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.144s
Click to expand...
Click to collapse
Looks pretty much like I've been seeing where only thing that works is a blankflash.
And Ocean is your device name
TheKillerMaxOfficial said:
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 4.057] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.057] Check qboot_log.txt for more details
[ 4.057] Total time: 4.060s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
Click to expand...
Click to collapse
You may need to install Qualcomm driver and a newer blankflash version
There are several threads about this, may have to do some searching, often the newest versions are posted in the telegram group for g7 power
sd_shadow said:
Looks pretty much like I've been seeing where only thing that works is a blankflash.
And Ocean is your device name
Click to expand...
Click to collapse
it won't let me boot twrp, I didn't have it installed as recovery
sd_shadow said:
You may need to install Qualcomm driver and a newer blankflash version
There are several threads about this, may have to do some searching, often the newest versions are posted in the telegram group for g7 power
Click to expand...
Click to collapse
I don't know much about it and I don't know what else to do.
TheKillerMaxOfficial said:
it won't let me boot twrp, I didn't have it installed as recovery
Click to expand...
Click to collapse
Did you try
Code:
fastboot oem blankflash
sd_shadow said:
You may need to install Qualcomm driver and a newer blankflash version
There are several threads about this, may have to do some searching, often the newest versions are posted in the telegram group for g7 power
Click to expand...
Click to collapse
If you can find something to solve my problem, I would be very grateful.
sd_shadow said:
Did you try
Code:
fastboot oem blankflash
Click to expand...
Click to collapse
waiting for device
TheKillerMaxOfficial said:
waiting for device
Click to expand...
Click to collapse
How is it listed in device manager?
sd_shadow said:
How is it listed in device manager?
Click to expand...
Click to collapse
does not appear
TheKillerMaxOfficial said:
does not appear
Click to expand...
Click to collapse
It's there, you need to search for it, it maybe hidden in a collapsed section
sd_shadow said:
It's there, you need to search for it, it maybe hidden in a collapsed section
Click to expand...
Click to collapse
Qualcomm HS-USB QDLoader 9008 (COM3)
TheKillerMaxOfficial said:
Qualcomm HS-USB QDLoader 9008 (COM3)
Click to expand...
Click to collapse
Ok so it's in EDL mode
Try rebooting PC
sd_shadow said:
Ok so it's in EDL mode
Try rebooting PC
Click to expand...
Click to collapse
I already restarted it, what's next?
TheKillerMaxOfficial said:
I already restarted it, what's next?
Click to expand...
Click to collapse
try
[Guide] Recovering from a hard brick
This guide aims to recover your G7 power from a hard brick that leaves it in emergency download (EDL) mode. Will this work with my device? This should work on any device in EDL mode. To check for this mode, first try entering fastboot by...
forum.xda-developers.com
EDIT:
1 - I don't really care about rooting the phone. I'd simply like to have Lineage OS on it.
2 - I don't really care about having a installed version of TWRP, I can do the fastboot boot only if that would work to install lineage on there.
So I unlock the bootloader fine.
Now following this :
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
I am able to
fastboot boot twrp.img
Then I do the install of the .zip from the TWRP site.
Wipe davlik and reboot
System starts fine. I reboot in bootloader mode (power + volumn down) then go to recovery
it has that
N/A in the top corner, flash black and buzz, flash black again then the androdi starts normally.
I read somewhere the this is a bootloop - and I should install Magisk from TWRP, which I did probably incorrectly at one point.
Booting back into fastboot boot twrp.img
I wipe advanced (system davlik data system)
Then Advanced Fix Recovery Bootloop
Then this seems to be not good:
Unpacking Boot...
Backing up Boot...
Patching kernel...
(in red)
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
So did I screw up my kernel while trying to install magisk ? What would be the next step?
Would it make sense to flash the original firmware from here:
[Guide][Channel][Stock]Moto g7 play Factory Firmware Images
Moto g7 play Android 9 and 10 Factory Firmware Stock Images Info Updated on 23-11-2020 Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download...
forum.xda-developers.com
The question I would have is which one should I choose in there:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
The retail one? Mine is factory unlocked, not connected to any network,
MPN: Moto G7 Play, XT1952-1
Network: Unlocked
The phone still work fine (I think, didn't do more than booting and checking the internet).
damaru said:
EDIT:
1 - I don't really care about rooting the phone. I'd simply like to have Lineage OS on it.
2 - I don't really care about having a installed version of TWRP, I can do the fastboot boot only if that would work to install lineage on there.
So I unlock the bootloader fine.
Now following this :
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
I am able to
fastboot boot twrp.img
Then I do the install of the .zip from the TWRP site.
Wipe davlik and reboot
System starts fine. I reboot in bootloader mode (power + volumn down) then go to recovery
it has that
N/A in the top corner, flash black and buzz, flash black again then the androdi starts normally.
I read somewhere the this is a bootloop - and I should install Magisk from TWRP, which I did probably incorrectly at one point.
Booting back into fastboot boot twrp.img
I wipe advanced (system davlik data system)
Then Advanced Fix Recovery Bootloop
Then this seems to be not good:
Unpacking Boot...
Backing up Boot...
Patching kernel...
(in red)
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
So did I screw up my kernel while trying to install magisk ?
Click to expand...
Click to collapse
If you tried to install magisk, it may be interfering with TWRP.
damaru said:
What would be the next step?
Would it make sense to flash the original firmware from here:
[Guide][Channel][Stock]Moto g7 play Factory Firmware Images
Moto g7 play Android 9 and 10 Factory Firmware Stock Images Info Updated on 23-11-2020 Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download...
forum.xda-developers.com
The question I would have is which one should I choose in there:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
The retail one? Mine is factory unlocked, not connected to any network,
MPN: Moto G7 Play, XT1952-1
Network: Unlocked
The phone still work fine (I think, didn't do more than booting and checking the internet).
Click to expand...
Click to collapse
A few different options
to find the correct Firmware you need to know
Software Channel, Codename, Software Version, and Model #
all of these can be found in the getvar all (remove imei before posting getvar all)
Code:
fastboot getvar all
or you can use LMSA's rescue option, LMSA will find the newest firmware for your device,
So if it's the same Software version as what is on the device, can just flash the boot.img from the firmware folder.
Code:
fastboot flash boot boot.img
or use
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
sd_shadow said:
fastboot flash boot.img
Click to expand...
Click to collapse
That would be fastboot flash boot boot.img right?
I've downloaded the appropriate firmware using fastboot getvar all to get the right model. The phone boots properly (it wasn't after I used the wrong firmware). But then I get to the same error when I fastboot boot twrn.img and try the advance Fix Recovery Bootloop.
When I did flash the whole firmware, the Bad Code was back, then I flashed TWRP and then the N/A was there and when I tried to boot to recovery the same loop happened.
From my lack of understanding, did I updated the Kernel when I reflashed the firmware? And does magisk modify my Kernel. How would I put back the original kernel?
Thanks for the support it's greatly appreciated! I've been on this for too many hours now!
As you mentioned that I should remove my emei before posting this I though that posting it might help
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:56:26 UTC 2020"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(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]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(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: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.010s
damaru said:
That would be fastboot flash boot boot.img right?
Click to expand...
Click to collapse
correct
damaru said:
As you mentioned that I should remove my emei before posting this I though that posting it might help
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:56:26 UTC 2020"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(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]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(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: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.010s
Click to expand...
Click to collapse
Well, a few things don't look right.
Code:
(bootloader) reason: Reboot mode set to fastboot
Likely cause from not using fb_clear after flashing
Code:
fastboot oem fb_mode_clear
Baseband is missing
Code:
(bootloader) version-baseband: <not found>
Did you use firmware from RetCA?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Yes this is the one I used. I might have done more fastboot stuff than what was in the xml file (these are from the post itself and not from the firmware file):
fastboot erase DDR
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
which in the retca xml only had :
<step operation="erase" partition="DDR"/>
<step operation="oem" var="fb_mode_clear"/>
should I reflash the whole thing, omitting the erase at the end?
damaru said:
Yes this is the one I used. I might have done more fastboot stuff than what was in the xml file (these are from the post itself and not from the firmware file):
fastboot erase DDR
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
which in the retca xml only had :
<step operation="erase" partition="DDR"/>
<step operation="oem" var="fb_mode_clear"/>
should I reflash the whole thing, omitting the erase at the end?
Click to expand...
Click to collapse
No, if you used fastboot oem fb_mode_clear
then something else is going on
So the rescue and smart assistant is not working on that particular model (or so Lenovo say) should I try anyway?
I get a Start Up Failed now. So I can't boot in the normal phone anymore. Not sure what I did wrong. So to get back to a normal phone flashing the whole firmware wouldn't help?
I'm at a place where I'd like to bring back the phone to exactly how it was stock so that I can go trough the TWRP process which seems to be straight enough...
EDIT 1 trying with the rescue software I get
Device missed [ro.build.version.full]
Please contact after sale service to re-write
EDIT 2
Reflashed the whole thing and the phone is work now.
Trying to re-install TWRP from:
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Using the TWRP page information, I tried to install it and then when I try to reboot it goes trough the boot loop. Phone boots fine, back the N/A in the top corner of the boot screen. Get back in fastboot boot twrp, the wipe davlik, try to fix the bootloop, get the same freaking error :
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
Phone boots fine though.
Try to fix Magisk (by installing the APK ):
Installation
The Magic Mask for Android
topjohnwu.github.io
Trying to Fix Magisk, using the apk, with the Boot.img that I used to reflash the whole phone didn't seems to work. I was able to create a custom boot img, and then the phone boot it doesn't say BAD CODE but a series of 40 numbers appears on the top screen. When I go back to the Magisk APK it shows that it's not installed, or more appropriate Installed: N/A ...
Trying to install lineage from the zip from the lineage site.
By booting in fastboot boot twrp, I wipe davlik, system, data, the install from zip I get:
Error installing zip file '/external_sd/lineage-18.1-2021-6-6-nightly-channel-signed.zip
Updating partition details...
...done
So, no idea where to go from there. Maybe I'm doing all that stuff in the wrong order. Should I try to reflash the boot, then not trying to install TWRP and trying to install Lineage like that? Is that possible?
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:37:43 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/channel/channel:9/PPYS29.
(bootloader) ro.build.fingerprint[1]: 105-220-3/74206:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.8.channel.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_37.155.01.146R CHANNEL_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(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.011s
damaru said:
So the rescue and smart assistant is not working on that particular model (or so Lenovo say) should I try anyway?
I get a Start Up Failed now. So I can't boot in the normal phone anymore. Not sure what I did wrong. So to get back to a normal phone flashing the whole firmware wouldn't help?
I'm at a place where I'd like to bring back the phone to exactly how it was stock so that I can go trough the TWRP process which seems to be straight enough...
EDIT 1 trying with the rescue software I get
Device missed [ro.build.version.full]
Please contact after sale service to re-write
EDIT 2
Reflashed the whole thing and the phone is work now.
Trying to re-install TWRP from:
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Using the TWRP page information, I tried to install it and then when I try to reboot it goes trough the boot loop. Phone boots fine, back the N/A in the top corner of the boot screen. Get back in fastboot boot twrp, the wipe davlik, try to fix the bootloop, get the same freaking error :
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
Phone boots fine though.
Try to fix Magisk (by installing the APK ):
Installation
The Magic Mask for Android
topjohnwu.github.io
Trying to Fix Magisk, using the apk, with the Boot.img that I used to reflash the whole phone didn't seems to work. I was able to create a custom boot img, and then the phone boot it doesn't say BAD CODE but a series of 40 numbers appears on the top screen. When I go back to the Magisk APK it shows that it's not installed, or more appropriate Installed: N/A ...
Trying to install lineage from the zip from the lineage site.
By booting in fastboot boot twrp, I wipe davlik, system, data, the install from zip I get:
Error installing zip file '/external_sd/lineage-18.1-2021-6-6-nightly-channel-signed.zip
Updating partition details...
...done
So, no idea where to go from there. Maybe I'm doing all that stuff in the wrong order. Should I try to reflash the boot, then not trying to install TWRP and trying to install Lineage like that? Is that possible?
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:37:43 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/channel/channel:9/PPYS29.
(bootloader) ro.build.fingerprint[1]: 105-220-3/74206:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.8.channel.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_37.155.01.146R CHANNEL_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(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.011s
Click to expand...
Click to collapse
I don't think you need to Install TWRP to install Lineage
Just boot twrp and install the Rom
Edit: Looks like you tried that already
Make sure you are using the preinstall zip before installing the rom
Install LineageOS on channel | LineageOS Wiki
wiki.lineageos.org