Hello
2 years back I dropped my phone in water.
It recovered though and working properly, but last month I saw sometimes the screen flashes sometime while touching the display.
After someday it is completely dark, the touch was working as I can unlock my phone and receive calls by guessing the positions on my screen, and sometimes it shows the display with a hazy screen. So I tried to order a display to replace, but it was not possible during lockdown.
So I was using this > scrcpy-control-android-on-pc
to backup my things and other, while waiting for the new display.
But then after 2 days the phone was rebooted and goes completely dark.
No led while charging, it only keep restarting (only vibrates as I can not see anything on my screen)
I tried many key combinations >>
vol up + vol down + power : long vibration and blue led
vol down + power: while USB connected to PC fastboot devices appeared
here is the fastboot getvar all
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.00(*)
(bootloader) product: kuntao
(bootloader) board: kuntao
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB Samsung REV=08 PRV=07 TYPE=57 PNM=RX14MB
(bootloader) ufs: 32GB Samsung REV=08 PRV=07 TYPE=57 PNM=RX14MB
(bootloader) ram[0]: 3840MB Samsung S8 SDRAM DIE=8Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x5F
(bootloader) cpu: MSM8953
(bootloader) serialno: [STRIKE]Zxxxxxxxxx[/STRIKE]
(bootloader) cid: cid
(bootloader) channelid: no support
(bootloader) uid: [STRIKE]bxxxxxbx0000000[/STRIKE]
(bootloader) unlocked: locked
(bootloader) iswarrantyvoid: iswarrantyvoid
(bootloader) max-download-size: 536870912
(bootloader) reason: no support
(bootloader) imei: [STRIKE]35xxxxxxxxxxxxx[/STRIKE]
(bootloader) meid:
(bootloader) date: 12-19-2016
(bootloader) sku: P2a42
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(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) aboot.git: aboot.git
(bootloader) qe: unknown
(bootloader) frp-state: frp-state
(bootloader) ro.carrier:
(bootloader) sv: 2
As you can see the bootloader is locked, I never flashed anything to this device.
So how to recover from this?
Thanks in advance.
Maybe your phone got into the emergency download mode, try reflash firmware.
Also similar thing happened to me, phone water dropped and vibrates, black screen. I disassembly the phone and dried. It worked. (Also I have same blowned pins, cleared them and it worked, no idea how worked tho)
Related
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
Hey all,
Okay. I have (apparently) the 1789-04 version of the Z2 Force. However, the phone insists, for the most part, internally, that it is an AT&T phone, not the TMO variant, which would be the variant indicated by the model number. This has lately become an issue due to the fact that the other day I was in camera mode on the phone, and POOF it bricked all over me, and I've tried to flash all kinds of stock firmware onto the phone. ATT firmwares flash successfully across the board, but just end up doing a bootloader boot loop, sometimes asking me to factory data reset the phone. TMO stock firmware fails at the point where the boot image flashes with the error "Preflash validation error". I've tried all kinds of firwmares, the most recent, slightly older ones.
The device shows in the bootloader as OEM locked, but when I flash the TMO bootloader, it starts off with the bootloader unlocked warning. Total bonkers. When the ATT is flashed, it never boots, so no point. I only get as far as the Motorola screen. I cannot get the phone to go to blankflash, as the command fastboot oem blankflash (no quotes) produces an error that says something along the the lines of that not being authorized. I would LOVE for my phone to be forced into a spot where I could use blankflash and go from there. Anyway, here's the getvar, if you guys have any suggestions, that would be great.
C:\Users\zacha>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY2249JTJC
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 3D66704C
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 353311080795291
(bootloader) meid:
(bootloader) date: 07-28-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3695
(bootloader) iccid: 89014103270252934039
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g0f8e904 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue May 28 02:06:00 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) git:xbl: git:xbl
(bootloader) gitmic: gitmic
(bootloader) git:rpm: git:rpm
(bootloader) git:tz: git:tz
(bootloader) git:hyp: git:hyp
(bootloader) git:devcfg: git:devcfg
(bootloader) git:cmnlib: git:cmnlib
(bootloader) git:cmnlib64: git:cmnlib64
(bootloader) git:keymaster: git:keymaster
(bootloader) git:storsec: git:storsec
(bootloader) gitrov: gitrov
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: att
(bootloader) current-slot:
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(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
all: listed above
finished. total time: 0.206s
zjcook23 said:
Hey all,
Okay. I have (apparently) the 1789-04 version of the Z2 Force. However, the phone insists, for the most part, internally, that it is an AT&T phone, not the TMO variant, which would be the variant indicated by the model number. This has lately become an issue due to the fact that the other day I was in camera mode on the phone, and POOF it bricked all over me, and I've tried to flash all kinds of stock firmware onto the phone. ATT firmwares flash successfully across the board, but just end up doing a bootloader boot loop, sometimes asking me to factory data reset the phone. TMO stock firmware fails at the point where the boot image flashes with the error "Preflash validation error". I've tried all kinds of firwmares, the most recent, slightly older ones.
The device shows in the bootloader as OEM locked, but when I flash the TMO bootloader, it starts off with the bootloader unlocked warning. Total bonkers. When the ATT is flashed, it never boots, so no point. I only get as far as the Motorola screen. I cannot get the phone to go to blankflash, as the command fastboot oem blankflash (no quotes) produces an error that says something along the the lines of that not being authorized. I would LOVE for my phone to be forced into a spot where I could use blankflash and go from there. Anyway, here's the getvar, if you guys have any suggestions, that would be great.
C:\Users\zacha>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY2249JTJC
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 3D66704C
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 353311080795291
(bootloader) meid:
(bootloader) date: 07-28-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3695
(bootloader) iccid: 89014103270252934039
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g0f8e904 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue May 28 02:06:00 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) git:xbl: git:xbl
(bootloader) gitmic: gitmic
(bootloader) git:rpm: git:rpm
(bootloader) git:tz: git:tz
(bootloader) git:hyp: git:hyp
(bootloader) git:devcfg: git:devcfg
(bootloader) git:cmnlib: git:cmnlib
(bootloader) git:cmnlib64: git:cmnlib64
(bootloader) git:keymaster: git:keymaster
(bootloader) git:storsec: git:storsec
(bootloader) gitrov: gitrov
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: att
(bootloader) current-slot:
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(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
all: listed above
finished. total time: 0.206s
Click to expand...
Click to collapse
Try Flash/rescue option in
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Another note is that both att and tmo models are xt 1789-04, so the if your phone is telling you it's an att then there is no way to unlock the bootloader.
Sent from my moto z4 using XDA Labs
sd_shadow said:
Try Flash/rescue option in
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Click to expand...
Click to collapse
Tried this multiple times but my phone can't get past fastboot so I can't check the USB debugging or even have the phone detected by the LMSA. when i manually tell the program that it's an xt-1789-04, it will get as far as cmd: getvar:serialno before saying it can't match the product with the model number.
I'm Having the Problem "Your Device is Corrupt, It can not be trusted and it does not boot"
And Not able to unlock bootloader
Showing Error like this
Check"Allow OEM Unlock" in Developer Options
Anyone???
Who help me!!!!!!!
Same
So I followed the standard instructions for this process and successfully unlocked the bootloader for my phone.
I followed these instructions, starting with the process for getting a phone unbricked because I'd already been stuck in a bootloop from following some other instructions. I also seem to have issues using fastboot at all. It behaves differently when issuing the same command. GetVar All cannot retrieve all variables succesfully.
PS C:\Users\enewt\Downloads\adb_fastboot_binaries_Motorola_Z2_Force_XT1789-05> .\fastboot getvar all (bootloader) slo: not found (bootloader) slot-suffi: not found (bootloader) kernel: uefi (bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420 (bootloader) product: nash (bootloader) board: nash (bootloader) secure: yes (bootloader) hwrev: PVT (bootloader) radio: NA_UMTS (bootloader) storage-type: UFS (bootloader) emmc: N/A (bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200 (bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12 (bootloader) cpu: MSM8998 2.1 (0) (bootloader) serialno: ZY224TL8V5
Anyway it seems to work better on archlinux, so here's the output from that:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224TL8V5
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 3F57D9A7
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: not zero
(bootloader) meid:
(bootloader) date: 03-25-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku: XT1789-04
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3852
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-7/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.9.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g2c64ab8 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Apr 20 09:21:37 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180420
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180420
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180420
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
I'm currently trying to exploit the QCOM diagnostic port utilities discussed in droidsavvy.com/unbrick-qualcomm-mobiles/ but I'm worried since I can't really get it to show up and I don't think EDL mode is working properly.
One weird thing is that I was actually able to get it to boot by using fastboot boot on a boot img. and instead of saying it was corrupt it actually made it to "Pixel has encountered an error" infinite crash loop. Seemed useless.
Summary: OEM unlock is disabled, need to enable it by booting and changing dev, settings. Cannot boot to change dev. settings as "corrupt and cannnot be trusted." Note that before locking the bootloader, it booted just fine, just had no baseband. Since OEM is now locked, I fear this is insurmountable but I haven't given up yet. I just don't understand why having the bootloader locked is the reason why I can't boot, but it's also why I can't flash to stock. From the bootloader, all other boot options, recovery, factory, QCOM all take me to the "your device is corrupt blah blah" dead-end. Quirks-- I think I put the wrong firmware on it, which is why I am able to boot with the image from the 05 firmware folder, but I get the Pixel Setup has stopped loop forever. This one is fun since it actually does seem to let me get to a black "desktop screen" and I can use the flashlight, bluetooth possibly, and tap around at a blank screen. The boot img from firmware 04 can't get past the TMO splash.
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?
Hi good day, i flashed pixelExperience UNOFFICIAL ROM last week but i found a bug that wifi kept disconnecting so I wanted to return back to stock so I did the process to go back to stock, and everything was fine until i decided to relock the bootloader, the phone got stuck at a screen that said "Operating system not valid this device wont boot" <--- it was something like that, i dont remember so I inmediately went to fastboot mode and try to reflash the rom but everything I tried to do didn't work because it kept asking me that my bootloader needed to be unlock by going to system usb debugging etc, but how would I do that if the phone was already stuck at fastboot, then i thought I don't know twhy I got the stupid idea that running "fastboot erase all" command would help me, so yes I ran that command and guess what the phone got much worse than it already was
now i can't do anything I've searched on a lot of forums and nothing seems to work I heard that using a blankflash would help me the thing is no matter the command i run it will always sends me back to fastboot mode I tried moto rescue and didn't work as well I've heard that EDL mode but phone keeps going to fastboot or maybe I'm doing something wrong, please help me!!!!
this is what fastboot getvar all shows
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-odessa_retail-e69c40c38d-220105
(bootloader) product: odessa
(bootloader) board: odessa
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRLAP
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB MICRON MT128GASAO4U21 FV=0106 WB=0
(bootloader) ram: 4GB MICRON LP4 DIE=32Gb M5-M8=FF 06 00 18
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: ZY22CRQG7F
(bootloader) cid: 0x0032
(bootloader) channelid: 0x03
(bootloader) uid: D2DE5AB3
(bootloader) token: inactive
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 355537115810642
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 06-29-2021
(bootloader) sku: XT2087-1
(bootloader) carrier_sku: XT2087-1
(bootloader) battid: SB18C98040
(bootloader) battery-voltage: 3914
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: amxmx
(bootloader) ro.build.fingerprint[0]: motorola/odessa_retail/odessa:11/R
(bootloader) ro.build.fingerprint[1]: PAS31.Q2-59-17-4-3-2/37446:user/re
(bootloader) ro.build.fingerprint[2]: lease-keys
(bootloader) ro.build.version.qcom: LA.UM.9.1.r1-09100-SMxxx0.0
(bootloader) version-baseband: M7150_22.31.04.72R ODESSA_BRLAP_CUST
(bootloader) kernel.version[0]: Linux version 4.14.190-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 J
(bootloader) kernel.version[4]: an 5 04:57:51 CST 2022
(bootloader) git:xbl: MBM-3.0-odessa_retail-ce4c20166-220105
(bootloader) git:xbl_config: MBM-3.0-odessa_retail-ce4c20166-220105
(bootloader) git:aop: MBM-3.0-odessa_retail-9817cf3-220105
(bootloader) git:tz: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:hyp: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:devcfg: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:cmnlib: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:keymaster: MBM-3.0-odessa_retail-db27bc4-220105
(bootloader) git:storsec: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) gitrov: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:abl: MBM-3.0-odessa_retail-e69c40c38d-220105
(bootloader) git:uefisecapp: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D02302
(bootloader) primary-display: txd_ft8756_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.041s
Edgar Pione said:
Hi good day, i flashed pixelExperience UNOFFICIAL ROM last week but i found a bug that wifi kept disconnecting so I wanted to return back to stock so I did the process to go back to stock, and everything was fine until i decided to relock the bootloader, the phone got stuck at a screen that said "Operating system not valid this device wont boot" <--- it was something like that, i dont remember so I inmediately went to fastboot mode and try to reflash the rom but everything I tried to do didn't work because it kept asking me that my bootloader needed to be unlock by going to system usb debugging etc, but how would I do that if the phone was already stuck at fastboot, then i thought I don't know twhy I got the stupid idea that running "fastboot erase all" command would help me, so yes I ran that command and guess what the phone got much worse than it already was
now i can't do anything I've searched on a lot of forums and nothing seems to work I heard that using a blankflash would help me the thing is no matter the command i run it will always sends me back to fastboot mode I tried moto rescue and didn't work as well I've heard that EDL mode but phone keeps going to fastboot or maybe I'm doing something wrong, please help me!!!!
this is what fastboot getvar all shows
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-odessa_retail-e69c40c38d-220105
(bootloader) product: odessa
(bootloader) board: odessa
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRLAP
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB MICRON MT128GASAO4U21 FV=0106 WB=0
(bootloader) ram: 4GB MICRON LP4 DIE=32Gb M5-M8=FF 06 00 18
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: ZY22CRQG7F
(bootloader) cid: 0x0032
(bootloader) channelid: 0x03
(bootloader) uid: D2DE5AB3
(bootloader) token: inactive
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 355537115810642
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 06-29-2021
(bootloader) sku: XT2087-1
(bootloader) carrier_sku: XT2087-1
(bootloader) battid: SB18C98040
(bootloader) battery-voltage: 3914
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: amxmx
(bootloader) ro.build.fingerprint[0]: motorola/odessa_retail/odessa:11/R
(bootloader) ro.build.fingerprint[1]: PAS31.Q2-59-17-4-3-2/37446:user/re
(bootloader) ro.build.fingerprint[2]: lease-keys
(bootloader) ro.build.version.qcom: LA.UM.9.1.r1-09100-SMxxx0.0
(bootloader) version-baseband: M7150_22.31.04.72R ODESSA_BRLAP_CUST
(bootloader) kernel.version[0]: Linux version 4.14.190-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 J
(bootloader) kernel.version[4]: an 5 04:57:51 CST 2022
(bootloader) git:xbl: MBM-3.0-odessa_retail-ce4c20166-220105
(bootloader) git:xbl_config: MBM-3.0-odessa_retail-ce4c20166-220105
(bootloader) git:aop: MBM-3.0-odessa_retail-9817cf3-220105
(bootloader) git:tz: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:hyp: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:devcfg: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:cmnlib: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:keymaster: MBM-3.0-odessa_retail-db27bc4-220105
(bootloader) git:storsec: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) gitrov: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:abl: MBM-3.0-odessa_retail-e69c40c38d-220105
(bootloader) git:uefisecapp: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D02302
(bootloader) primary-display: txd_ft8756_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.041s
Click to expand...
Click to collapse
How to boot into EDL Mode