Develop Bugs

How to unlock XT 1799-2 Montana if official Moto unlock key does not work? Help!

Hey guys,
So I bough the latest G5S version, the Green Pomelo aka XT 1799-2. It's a wonderful phone for the price, but I am stuck with stock ROM and locked features such as camera2.api. Decided to root and followed this guide to the letter https://forum.xda-developers.com/moto-g5s/how-to/guide-unlock-bootloader-moto-g5s-t3691200 , but hit a block. When I obtained the phone, my boot loader was already indicating following warning:
"Your device failed verification and may not work properly". I assumed it was already flashed by reseller. Neverthless, I tried to unlock the bootloader using official Motorola key anyway just to receive following:
C:\Minimal ADB and Fastboot>fastboot oem unlock EG2Q6NB37LSZ2RHIX6KZ
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
I assume they locked the bootloader again, but due that I am hopeless now. I contacted their technical support, but they can only offer either full refund or replacement, which will leave me a month without a phone. Thus I am turning on you guys. Is there a way to unlock the bootloader somehow anyway? And if, could you state how?
Here is the full getvar:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.06(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX64MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322D4JM7
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: AC71A4BE00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359565080402695
(bootloader) meid:
(bootloader) date: 10-08-2017
(bootloader) sku: XT1799-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Dec 21 19:25:12 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/montana_retcn_n/montana_n
(bootloader) ro.build.fingerprint[1]: :7.1.1/NZS26.86-108/112:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.112.montana_re
(bootloader) ro.build.version.full[1]: tcn.retcn.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8937_37.13.03.53R MONTANA_CHINADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g647ff94-0000
(bootloader) kernel.version[1]: 7-g13fa5e2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Thu Mar
(bootloader) kernel.version[3]: 1 20:32:27 CST 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.06-0-g518a6f1
(bootloader) rpm.git: git=aa33522-dirty
(bootloader) tz.git: git=1fe3cc8-dirty
(bootloader) devcfg.git: git=1fe3cc8-dirty
(bootloader) keymaster.git: git=1fe3cc8-dirty
(bootloader) cmnlib.git: git=1fe3cc8-dirty
(bootloader) cmnlib64.git: git=1fe3cc8-dirty
(bootloader) prov.git: git=1fe3cc8-dirty
(bootloader) aboot.git: git=MBM-NG-VBC.06-0-g865eb9a-dirty
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retcn
Cheers
Six

sixtheninth said:
C:\Minimal ADB and Fastboot>fastboot oem unlock EG2Q6NB37LSZ2RHIX6KZ
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
Click to expand...
Click to collapse
In my also gave this same error when I tried to unlock the bootloader, is giving this error because this phone already comes with the unlocked bootloader, it is blocked to flash
Try unlocking using this command
Code:
fastboot flashing unlock

Oh man, thanks a lot for that! That worked. So shall I normally proceed to root now without problems?

how to root now
jvfigueredo said:
In my also gave this same error when I tried to unlock the bootloader, is giving this error because this phone already comes with the unlocked bootloader, it is blocked to flash
Try unlocking using this command
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
Would you tell me how did you root the phone afterwards? I am trying to flash TWRP Recovery twrp-montana-3.2.3-r1.img but getting error.

sixtheninth said:
Would you tell me how did you root the phone afterwards? I am trying to flash TWRP Recovery twrp-montana-3.2.3-r1.img but getting error.
Click to expand...
Click to collapse
I don't root my phone but this twrp works fine, others releases of twrp screen bug rotate 180°, its sucks
Flash Twrp recovery
Code:
fastboot flash recovery twrp.img

i stuck on bootloader i tried installing stock but no use please help me

(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.12
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX64MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322Q2DZQ
(bootloader) cid: 0x00FF
(bootloader) channelid: 0x00
(bootloader) uid: 2CF0D7BF00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359574083302191
(bootloader) meid:
(bootloader) date: 06-20-2018
(bootloader) sku: XT1795
(bootloader) carrier_sku:
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jul 16 9:14:51 UTC 1972"
(bootloader) ro.build.fingerprint[0]: motorola/montana/montana:8.1.0/OPP
(bootloader) ro.build.fingerprint[1]: S28.65-37-7-6/4cc5a:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.montana.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_37.13.03.72u MONTANA_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g26d4309 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Wed Jun 26 06:06:58 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VBC.12-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=9a0b157
(bootloader) devcfg.git: git=9a0b157
(bootloader) keymaster.git: git=9a0b157
(bootloader) cmnlib.git: git=9a0b157
(bootloader) cmnlib64.git: git=9a0b157
(bootloader) prov.git: git=9a0b157
(bootloader) aboot.git: git=MBM-NG-VBC.12-0-g0b9dae9
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: unknown
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.094s

deepa007 said:
(bootloader) reason: Reboot mode set to fastboot
Click to expand...
Click to collapse
this is it
did you use a script to flash stock or did you flash all parts step by step?
at the beginning there is a
fastboot oem fb_mode_set this means fastboot always reboots to bootloader/fastboot to make sure all is done before reboot to system
at the end, when all files are flashed and all /data /cache etc is erased there is a
fastboot oem fb_mode_clear to clear the lock
fastboot reboot
done

zitronenmelissa said:
this is it
did you use a script to flash stock or did you flash all parts step by step?
at the beginning there is a
fastboot oem fb_mode_set this means fastboot always reboots to bootloader/fastboot to make sure all is done before reboot to system
at the end, when all files are flashed and all /data /cache etc is erased there is a
fastboot oem fb_mode_clear to clear the lock
fastboot reboot
done
Click to expand...
Click to collapse
yeah then also i stuck stuck on fastboot
mode

Try booting the phone to bootloader from fastboot command through system. Then you can copy the rom to internal storage and then flash directly.

deepa007 said:
yeah then also i stuck stuck on fastboot
mode
Click to expand...
Click to collapse
how did you flash stock? with a script or step by step? which firmware did you choose?
here is a good HowTo: https://forum.xda-developers.com/t/...latam-ora-playpl-retail-retru-trueth.3845848/
you can boot twrp with fastboot: fastboot boot twrp-name.img
then you should backup efs / persist to sdcard first if you haven't done that already.
then format data in wipe menu (agree with YES) and reboot

rdbhadri said:
Try booting the phone to bootloader from fastboot command through system. Then you can copy the rom to internal storage and then flash directly.
Click to expand...
Click to collapse
Please tell me the steps how to do

Question Unbrick Moto G10

Hello. I think I messed it up trying to root my Motorola G10. I'm stuck on a bootloop as you can see in the picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried to recover it with all kinds of assistants, but they all fail. I've also tried to flash it with fastboot, but it turns out that oem is not enabled, and if I try to unlock it with fastboot commands I just get the "Check OEM unlocking in Android settings >Developer options" message. Obviously, I cannot access my phone so I cannot check that option. After searching for many hours in the forums, the only thing I haven't tried is EDL mode, but I can't manage to set it on either.
I don't know what else to do, so any help will be welcome. Thanks.

luisgb78 said:
I've tried to recover it with all kinds of assistants
Click to expand...
Click to collapse
What does that mean? Which assistants? There is only one that I know of.

Well. First I tried with "Rescue and Smart Assistant", suggested by Motorola support team, but it fails. At this point I don't really know if I have to recover it, flash it, factory reset it or what. I also tried other software like Kingo Root, RSD Lite, but I don't get anywhere.
In case this helps, this is what i get with >fastboot getvar all:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-capri_retail-7d6811cfd7-201230
(bootloader) product: capri
(bootloader) board: capri
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX hC9aP3 RV=08 PV=01 FV=0000000031303030
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5-M8=06 05 00 11
(bootloader) cpu: SM_KAMORTA 1.0
(bootloader) serialno: ZY32C2KNPT
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: CEC0747D
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804464640
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 03-28-2021
(bootloader) sku: XT2127-2
(bootloader) carrier_sku: XT2127-2
(bootloader) battid: SB18C85291
(bootloader) battery-voltage: 4140
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: reteu
(bootloader) ro.build.fingerprint[0]: motorola/capri_retailen/capri:11/R
(bootloader) ro.build.fingerprint[1]: RB31.Q1-3-16-2/67641:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-01800-KAMORTA.0
(bootloader) version-baseband: HAK10_18.534.02.63R CAPRI_EUAPEMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.19.136-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Wed D
(bootloader) kernel.version[4]: ec 30 02:41:02 CST 2020
(bootloader) git:abl: MBM-3.0-capri_retail-7d6811cfd7-201230
(bootloader) frp-state: no protection (0)
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SP69A6PCNN
(bootloader) primary-display: tm_ili9882n_652_vid_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.399s
When I try to follow tutorials that I've found online I always run into the OEM problem. If I try to unlock it with fastboot this is what I get:
>fastboot oem unlock
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.092s
My initial plan was to root the phone, but at this point the device is useless. I don't know what should I do next to fix it or go back to its original state. Any help will be apreciated.

Hi. This is what Rescue and Smart Assistant shows:

It looks like bootloader is locked and I can't unlock it because OEM is not checked:
>fastboot oem unlock xxxxxxxxxxxxxxxxxxxxxxx
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.261s
>fastboot flashing unlock
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.307s
Is there anything I can do?

Anybody knows how to start EDL mode in a Motorola G10?
Thanks.

luisgb78 said:
It looks like bootloader is locked and I can't unlock it because OEM is not checked:
>fastboot oem unlock xxxxxxxxxxxxxxxxxxxxxxx
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.261s
>fastboot flashing unlock
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.307s
Is there anything I can do?
Click to expand...
Click to collapse
Ik I am very late, but did you try flashing the stock firmware?

[SOLVED] Soft bricked (looking like Hard Brick)Moto G7 Play [XT1952-2]

I have figured out how to solve this! My phone came back when i blankflashed it and ran script Blank-Flash through https://mirrors.lolinet.com/firmware/moto/ find your code name, the MotoG7 Play is called Channel, and go to Blankflash, after that install your BF of choice. install all the qualcomm drivers, i have done so through here. then after that, type fastboot oem blankflash and your device will turn off (its okay).
After that, load in the firehose in the Blank flash folder. Load up the script and hopefully itll return back to normal!
ORIGINAL POST:
My MotoG7 Play was Soft Bricked yesterday (12/05/2021). I tried to install Sakura Project ROM via TWRP(latest version) , and i factory reset my phone, and cleared partition A/B. when i rebooted back to recovery i was greeted with an unpleasant Bootload screen, i shrugged it off thinking i just clicked the wrong button but when i tried to got back to recovery i received the following error:
Start up failed: Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant. you can try to press powerkey in failure interface to fix it. If you try to fix it, pleas try it at least 6 times.
Click to expand...
Click to collapse
after this i was startled. so it proceeded below in the logs:
AP Fastboot Flash Mode (Secure)/ Fastboot Reason: Failed to initialize partition table
Click to expand...
Click to collapse
No bootable A/B slot
Click to expand...
Click to collapse
Failed to boot Linux, falling back to fastboot / Boot up failed
Click to expand...
Click to collapse
going back, i couldnt help but notice my Product/Variant which included XT1952-2 has now turned into "channel radio1 32GB PVTB", i didnt have a Baseband. and my bootloader was now locked(which wasnt before)! oem_locked.
i tried booting up a new Firmware Stock, latest version of my retailer and it gave errors, which i expected because Product/Variant was erased
i also tried using the Motorola SRA and they couldnt recognize my firmware, not surprised.
also note to mention that my device is in fact being recognized via fastboot as its serial number, i do not know if thats a good thing but its not as its name Moto G7, so when i do:
fastboot getvar all
Click to expand...
Click to collapse
this is the Output
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-4376d256f0a-2
(bootloader) version-bootloader[1]: 01130
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVTB
(bootloader) radio: 1
(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: b4890066
(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: 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-channel_retail-4376d256f0a-201130
(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.022s
so alot of things are comepletely wiped, and i only have access to slot A which is invalid.
i tried a Blank Flash but it just waited for my device and no results.
I use a Linux PC, but most of the process was done via a Windows laptop if its of any concern.
please help me out, i dont know what to do as of now and im near hopeless.
Edit 1: figured out Qualcomm and BlankFlash, and it now detects my device. now ill study more on how Qualcomm works and what do i need to restore my phone. if anyone knows how to work with Qualcomm i ask for a reply

mine also bricked after that I never get motorola above the g6 to install custom because that's the problem

HellxDo said:
I have figured out how to solve this! My phone came back when i blankflashed it and ran script Blank-Flash through https://mirrors.lolinet.com/firmware/moto/ find your code name, the MotoG7 Play is called Channel, and go to Blankflash, after that install your BF of choice. install all the qualcomm drivers, i have done so through here. then after that, type fastboot oem blankflash and your device will turn off (its okay).
After that, load in the firehose in the Blank flash folder. Load up the script and hopefully itll return back to normal!
ORIGINAL POST:
My MotoG7 Play was Soft Bricked yesterday (12/05/2021). I tried to install Sakura Project ROM via TWRP(latest version) , and i factory reset my phone, and cleared partition A/B. when i rebooted back to recovery i was greeted with an unpleasant Bootload screen, i shrugged it off thinking i just clicked the wrong button but when i tried to got back to recovery i received the following error:
after this i was startled. so it proceeded below in the logs:
going back, i couldnt help but notice my Product/Variant which included XT1952-2 has now turned into "channel radio1 32GB PVTB", i didnt have a Baseband. and my bootloader was now locked(which wasnt before)! oem_locked.
i tried booting up a new Firmware Stock, latest version of my retailer and it gave errors, which i expected because Product/Variant was erased
i also tried using the Motorola SRA and they couldnt recognize my firmware, not surprised.
also note to mention that my device is in fact being recognized via fastboot as its serial number, i do not know if thats a good thing but its not as its name Moto G7, so when i do:
this is the Output
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-4376d256f0a-2
(bootloader) version-bootloader[1]: 01130
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVTB
(bootloader) radio: 1
(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: b4890066
(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: 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-channel_retail-4376d256f0a-201130
(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.022s
so alot of things are comepletely wiped, and i only have access to slot A which is invalid.
i tried a Blank Flash but it just waited for my device and no results.
I use a Linux PC, but most of the process was done via a Windows laptop if its of any concern.
please help me out, i dont know what to do as of now and im near hopeless.
Edit 1: figured out Qualcomm and BlankFlash, and it now detects my device. now ill study more on how Qualcomm works and what do i need to restore my phone. if anyone knows how to work with Qualcomm i ask for a reply
Click to expand...
Click to collapse
people for those who still don't understand is the following
1. download the blankflash folder
2.install the motorola drivers
3.download the adb+fastboot folder that you find it when you go to unlock the device's bootloader for the 1 time
4.pass the contents of adb+fastboot folder to blankflash folder
5.download the firehose file
6.open cmd inside the blankflash folder
7.type inside the fastboot cmd oem blankflash
8.pass the firehose file into the blankflash folder
9.execute the .bat file blank-flash.bat and that's it

Androi100Olá, segui o passo a passo e deu certo. Muito obrigado pela resposta!​
Mod translation: Android 100 Hello, follow the step by step and it worked. Thank you very much for the answer!

Does anyone know where I can find the fire hose for moto g7 river?

Phone currently a brick with no bootable slots

I'm pretty sure my phone is properly bricked but decided to post here to since most of the information I could find when troubleshooting myself came from here.
Background:
I quite a bit of CS experience and work in IT but mostly stick to desktops and enterprise networking
I have never done anything "interesting" with my phone, no sideloading, no 3rd party bootloaders, ROMs or OSs, haven't even unlocked it. My phone was running stock OEM OS
I've been experience random crashes that would cause it to restart a couple times a month but just assumed that was normalish since it would always come back fine
After this most recent crash it is stuck at bootup
Phone Bootloader logs:
Code:
AP Fastboot Flash mode (Secure)
Fastboot Reason: Failed to initialize partition table
USB Connected
No bootable A/B Slot
Failed to boot Linux,falling back to fastboot
Boot up failed
Desktop APT output:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At this point I'm not really sure what to do, none of the articles or forum posts I found had no valid slots
Any help would be greatly appreciated,
Thanks

when there are no bootable slots it means that flash is damaged or corrupted. try booting different bootloader. when close thing happend to my pixel 4 i booted linage os boot.img and it went just fine. in fastboot check build and kerenel to be sure.
you can get it here https://download.lineageos.org/devices/channel/builds

I tried the lineage OS bootloader and followed their installation instructions as well as I could but still got the error of not having a valid slot to write the boot image to.
The output from getvar all doesn't inspire confidence, most of the entries seem to just have null values. Also it might just be a coincidence but the CID of 0xDEAD is certainly fitting.
Code:
C:\Users\#####\Downloads\platform-tools_r34.0.1-windows\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-16222030b3b-210202
(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: f4c414d
(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: 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-16222030b3b-210202
(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.050s

Dont flash it directly first try to boot up recovery boot with
Code:
./fastboot boot {boot. Img that you downloaded without curly braces}
Then from recovery use start or flash Whole image using adb sideload

KirinPixel said:
Dont flash it directly first try to boot up recovery boot with
Code:
./fastboot boot {boot. Img that you downloaded without curly braces}
Then from recovery use start or flash Whole image using adb sideload
Click to expand...
Click to collapse
If it says 0xDEAD or smt like that its likly a emmc mem broken