Question Unbrick Moto G10 - 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?

Related

Moto Z2 Play hard-brick

Hi everybody.
I ask for any help to restore my smartphone.
The problem is:
That I accidentally uploaded someone else's backup, the "cid" section. Now I have a cid: 0xDEAD
An interesting case, after this recovery the bootloader locked. Status:
securestate: oem_locked
*verity-state: enforcing
And I can not unlock it He writes an error, I think it's because of the frp section that changes the last byte to 01. After setting the checkbox in the setting - for the developer - the factory unlock.
D: \ ADB> fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) validate header error: 55
(bootloader) 3A15880808988261 #
(bootloader) 5A5932323442425A5642004D6F746F205A320000 #
(bootloader) 9D6169D0A91A800175B1EDA6CADAE6D3FB144F98 #
(bootloader) 09FAAB8E000000000000000000000000
OKAY [0.103s]
finished. total time: 0.104s
D: \ ADB> fastboot oem unlock XBZQPOSESK3KL7XQRRFT
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) feature disabled
OKAY [0.007s]
finished. total time: 0.008s
I watched a lot of articles and videos on the web. And I found an interesting video, where on Moto x the 2nd generation. In this situation, the bootloader was unlocked, unlocked, i.e. after flashing and starting the phone, oem_unlocked has already been indicated on the screen. I wonder if it's possible to do this on Z2 play?
https://www.youtube.com/watch?v=aYjzD9WZum0
I was trying to flash a full firmware. I can download all the parts of the firmware, except: system, boot, recovery. oem.img
In recovery I also can not get, only fastboot.
When flashing different versions of the bootloader, the file names change when prompting fastboot getvar all. So the bootloader loads well. But I have on my smartphone's screen:
Start up failed:
Your device did not start up succeessfuly.
Use the sofrware Repair Assistent on your computer to repair your device.
Connect yor device to your omputer to get the Software Repair Assistant.
When loading bootloader.img
-keys-cid50_retru \ Windows> fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot: bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB) ...
OKAY [0.178s]
writing 'bootloader' ...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [0.550s]
finished. total time: 0.730s
All is well.
.
But here's an example of boot.img
-keys-cid50_retru \ Windows> fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot: boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB) ...
OKAY [0.514s]
writing 'boot' ...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.726s
If you look at the smartphone's screen in bootlaoder logs - Failed to verify hab image boot.
Here's what fastboot shows: getvar all:
D:\ADB>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C7
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY224BBZVB
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 1E28AD1500000000000000000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 351888080892816
(bootloader) meid:
(bootloader) date: 07-25-2017
(bootloader) sku: XT1710-09
(bootloader) battid: SNN5985A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/albus/albus:7.1.1/NPS26.1
(bootloader) ro.build.fingerprint[1]: 18-19/19:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.51.19.albus.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953P_23.33.07.34R ALBUS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g3b78496-0000
(bootloader) kernel.version[1]: 5-ge5590f6 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Fri Jun 30 23:09:12 CDT 20
(bootloader) kernel.version[4]: 17
(bootloader) sbl1.git: git=MBM-NG-VC0.C7-0-ge9cd975
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) devcfg.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) keymaster.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) cmnlib.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) prov.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.C7-0-gb6d4956
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.134s
I will be glad to any help. I can check any action on my smartphone.

Help!!! T mobile moto z2 force - boot/bootloader problems

So prior to this I did unlock the bootloader and rooted it, and had TWRP installed. I flashed a stock rom (NASH_NPXS26.122-68-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) and after the reboot this is the error I keep receiving and no I cannot reboot into recovery or anything but fastboot mode. Any suggestions why this happened and if I can do anything to restore the original OS? By the way, it won't even let me unlock the bootloader anymore..I am about to give up. Thanks in advance for any input on this matter!
Here's some info that I get in Command Prompt through adb/fastboot
C:\fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-171208
(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: ZY224BC8FR
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 26D3CF6A
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from charger boot mode
(bootloader) imei: 356503080380945
(bootloader) meid:
(bootloader) date: 07-25-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4114
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:7.1.1/NPX
(bootloader) ro.build.fingerprint[1]: S26.122-68-4/8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.226.8.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.7.r1-09300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.21-perf-gcdf0207 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 2015012
(bootloader) kernel.version[2]: 3 (prerelease) (GCC) ) #1 SMP PREEMPT Th
(bootloader) kernel.version[3]: u Nov 2 09:10:45 CDT 2017
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.164s
GET OEM UNLOCK DATA
C:\fastboot>fastboot oem unlock data
...
(bootloader) ***************************************
(bootloader) WARNING: This command erases user data!
(bootloader) Please re-run this command to confirm.
(bootloader) ***************************************
OKAY [ 0.025s]
finished. total time: 0.026s
C:\fastboot>fastboot oem unlock data
...
(bootloader) warranty void fuse fail
OKAY [ 0.263s]
finished. total time: 0.264s
[
Why would you use a nougat flash all when you have the Oreo bootloader. You need to go into download move and blank flash now. It's your only hope and I don't know if you can with a locked bootloader

BootLoading Stuck

Im trying to get back to stock, but somehow I'm stuck on the boot G loading, I can access fastboot and stock recovery. Im coming from Kirisakura+AquariOS 9
- I have the lastest platform-tools r28.0.2
- I tried Ota (crosshatch-ota-pq2a.190405.003-8dbfa1fe) flash with sideload, when it finished it says "Total xfer: 2.00x" but when I reboot it stay in the boot G loading.
- I tried factory flash but it didn't work it said this...
Code:
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable not found)
--------------------------------------------
Bootloader Version...: xxxx
Baseband Version.....: xxxx
Serial Number........: xxxxx
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.356s
Help please.
This is the fastboot getvar all
Code:
(bootloader) product:crosshatch
(bootloader) serialno:xxxxxxx
(bootloader) variant:MSM USF
(bootloader) max-download-size:0x10000000
(bootloader) slot-suffixes:_a,_b
(bootloader) version-bootloader:b1c1-0.1-5343672
(bootloader) version-baseband:g845-00017-xxxx-B-5xxxx43
(bootloader) secure-boot:PRODUCTION
(bootloader) secure:yes
(bootloader) hw-revision:MP1.0
(bootloader) slot-count:2
(bootloader) current-slot:b
(bootloader) unlocked:yes
(bootloader) nos-production:yes
(bootloader) off-mode-charge:1
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) battery-voltage:4148
(bootloader) battery-soc-ok:yes
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd:0x2000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc:0x100000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore:0x80000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp:0x80000
(bootloader) partition-type:system_a:raw
(bootloader) partition-size:system_a:0xB0000000
(bootloader) partition-type:system_b:raw
(bootloader) partition-size:system_b:0xB0000000
(bootloader) partition-type:product_a:raw
(bootloader) partition-size:product_a:0x12C00000
(bootloader) partition-type:product_b:raw
(bootloader) partition-size:product_b:0x12C00000
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-size:vendor_a:0x30000000
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-size:vendor_b:0x30000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a:0x4000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b:0x4000000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a:0x5000000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b:0x5000000
(bootloader) partition-type:apdp_a:raw
(bootloader) partition-size:apdp_a:0x40000
(bootloader) partition-type:apdp_b:raw
(bootloader) partition-size:apdp_b:0x40000
(bootloader) partition-type:msadp_a:raw
(bootloader) partition-size:msadp_a:0x40000
(bootloader) partition-type:msadp_b:raw
(bootloader) partition-size:msadp_b:0x40000
(bootloader) partition-type:klog:raw
(bootloader) partition-size:klog:0x400000
(bootloader) partition-type:metadata:raw
(bootloader) partition-size:metadata:0x1000000
(bootloader) partition-type:userdata:raw
(bootloader) partition-size:userdata:0xCE4FFB000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a:0x380000
(bootloader) partition-type:xbl_config_a:raw
(bootloader) partition-size:xbl_config_a:0x20000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b:0x380000
(bootloader) partition-type:xbl_config_b:raw
(bootloader) partition-size:xbl_config_b:0x20000
(bootloader) partition-type:ALIGN_TO_128K_1:raw
(bootloader) partition-size:ALIGN_TO_128K_1:0x1A000
(bootloader) partition-type:cdt:raw
(bootloader) partition-size:cdt:0x20000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr:0x100000
(bootloader) partition-type:modemcal:raw
(bootloader) partition-size:modemcal:0x200000
(bootloader) partition-type:uefivar:raw
(bootloader) partition-size:uefivar:0x100000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec:0x4000
(bootloader) partition-type:aop_a:raw
(bootloader) partition-size:aop_a:0x80000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a:0x200000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a:0x80000
(bootloader) partition-type:abl_a:raw
(bootloader) partition-size:abl_a:0x200000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a:0x80000
(bootloader) partition-type:cmnlib_a:raw
(bootloader) partition-size:cmnlib_a:0x80000
(bootloader) partition-type:cmnlib64_a:raw
(bootloader) partition-size:cmnlib64_a:0x80000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a:0x20000
(bootloader) partition-type:qupfw_a:raw
(bootloader) partition-size:qupfw_a:0x10000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a:0x10000
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-size:dtbo_a:0x800000
(bootloader) partition-type:storsec_a:raw
(bootloader) partition-size:storsec_a:0x20000
(bootloader) partition-type:aop_b:raw
(bootloader) partition-size:aop_b:0x80000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b:0x200000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b:0x80000
(bootloader) partition-type:abl_b:raw
(bootloader) partition-size:abl_b:0x200000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b:0x80000
(bootloader) partition-type:cmnlib_b:raw
(bootloader) partition-size:cmnlib_b:0x80000
(bootloader) partition-type:cmnlib64_b:raw
(bootloader) partition-size:cmnlib64_b:0x80000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b:0x20000
(bootloader) partition-type:qupfw_b:raw
(bootloader) partition-size:qupfw_b:0x10000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b:0x10000
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-size:dtbo_b:0x800000
(bootloader) partition-type:storsec_b:raw
(bootloader) partition-size:storsec_b:0x20000
(bootloader) partition-type:ALIGN_TO_128K_2:raw
(bootloader) partition-size:ALIGN_TO_128K_2:0x1A000
(bootloader) partition-type:persist:raw
(bootloader) partition-size:persist:0x2800000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1:0x200000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2:0x200000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg:0x200000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc:0x20000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo:0x1000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip:0x100000
(bootloader) partition-type:spunvm:raw
(bootloader) partition-size:spunvm:0x800000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits:0x1000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv:0x100000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs:0x800000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti:0x200000
(bootloader) partition-type:ImageFv:raw
(bootloader) partition-size:ImageFv:0x200000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash:0x4000
all:
finished. total time: 0.601s
EDIT: I can install the AquariOS 9, but when it boot up, it says. "Your vendor image does not match the system. Please flash the PQ3A. 190505.002 vendor image for your device.
Have you tried manually flashing all the images in the factory image individually?
Code:
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then flash the other images inside the ZIP file.
Yes not all the images because when I tried to flash system said something about the size and didnt do anything
Edit: Maybe it has to do with the partitions but idk what steps should I do.
onlykhaz said:
Yes not all the images because when I tried to flash system said something about the size and didnt do anything
Edit: Maybe it has to do with the partitions but idk what steps should I do.
Click to expand...
Click to collapse
try flashing boot.img to boot A and B
lucky_strike33 said:
try flashing boot.img to boot A and B
Click to expand...
Click to collapse
Only boot? I dont think boot.img is the problem are the rest of the imgs. If I flash a & b might be dangerous right?
onlykhaz said:
Only boot? I dont think boot.img is the problem are the rest of the imgs. If I flash a & b might be dangerous right?
Click to expand...
Click to collapse
You should try this tool.
https://forum.xda-developers.com/pi...ool-crosshatchdb-one-pixel-3-xl-tool-t3864644
lucky_strike33 said:
You should try this tool.
https://forum.xda-developers.com/pi...ool-crosshatchdb-one-pixel-3-xl-tool-t3864644
Click to expand...
Click to collapse
Finally I'm home to test this. But I find something weird.
It says Bonito, like for Pixel 3a XL
{
"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"
}
onlykhaz said:
Finally I'm home to test this. But I find something weird.
It says Bonito, like for Pixel 3a XL
Click to expand...
Click to collapse
Did you download the wrong firmware?
onlykhaz said:
Im trying to get back to stock, but somehow I'm stuck on the boot G loading, I can access fastboot and stock recovery. Im coming from Kirisakura+AquariOS 9
Click to expand...
Click to collapse
You flashed the OTA. Download and flash the full image, and leave the -w flag in place. As advised earlier, flashing boot.img to both partitions will not harm your device. It is a step commonly used to recover from bootloop, especially coming from a custom ROM/kernel.

XT1952-2 dont get to bootloader and no android robot

I've got a moto g7 play and someday it get this screen. I try to flash any blankflash, but it still waiting for devices.
When I hold power button + volume down it restart and back to the first screen. Never get to bootloader and never show the android robot or menu on the right of screen.
Another curious fact is that SKU is erased to zero, so the Rescue and Smart Assistant never find the correct firmware. So, when I enter Fastboot devices comand, it shows only 3d6dd0dc fastboot.
The code on screen is this:
Product/Variant: channel 000000000000000 32GB PVTA
FV=0000000000000001
I will atach two pictures of all my screen.
Dont know what to do more. Any idea?
{
"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"
}
cant attach images. The message on the screen says:
Start Up Failed:
Your device didnt star 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.
Ap Fastboot flash Mode (secure)
Fastboot Reason: Volume down key pressed
USB Connected
failed to validate boot image
ERROS: Failed to pass validation, backup to fastboot
Boot up failed
second screen
AP Fastboot Flash Mode (Secure)
BL: MBM 2.1 channel retail 6bae60c 19018
Baseband:
Product/Variant: channel 000000000000000 32GB PVTA
Serial Number: 3ddd0dc
CPU: SDM632
eMMC: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
DRAM:2GB SAMSUNG LP3 DIE=8GB M5=01 M6=06 M7=00 M8=1F
Console [Null]: null
Tools Mode Config: Enabled
Battery: OK
oem_locked
Transfer Mode: USB Connected
What does getvar all say
Code:
fastboot getvar all
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
What does getvar all say
Code:
fastboot getvar all
Click to expand...
Click to collapse
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-channel_retail-6bae60c-190618
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVTA
(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: 3d6dd0dc
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 3F66644E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(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-6bae60c-190618
(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
finished. total time: 0.030s
Edu Furin said:
I've got a moto g7 play and someday it get this screen. I try to flash any blankflash, but it still waiting for devices.
When I hold power button + volume down it restart and back to the first screen. Never get to bootloader and never show the android robot or menu on the right of screen.
Another curious fact is that SKU is erased to zero, so the Rescue and Smart Assistant never find the correct firmware. So, when I enter Fastboot devices comand, it shows only 3d6dd0dc fastboot.
The code on screen is this:
Product/Variant: channel 000000000000000 32GB PVTA
FV=0000000000000001
I will atach two pictures of all my screen.
Dont know what to do more. Any idea?
Click to expand...
Click to collapse
Did you try flashing something before it did this happened?
sd_shadow said:
Did you try flashing something before it did this happened?
Click to expand...
Click to collapse
no, It happened someday after charging, when I flash the cmd shows a lot of "Remote Failure" and "Invalid Image", "Validation failure".
The blankflash keep waiting for device and the Device Manager shows "Motorola Adb Interface"
Don't know what to try...
Edu Furin said:
no, It happened someday after charging, when I flash the cmd shows a lot of "Remote Failure" and "Invalid Image", "Validation failure".
Click to expand...
Click to collapse
Ok
The blankflash keep waiting for device and the Device Manager shows "Motorola Adb Interface"
Don't know what to try...
Click to expand...
Click to collapse
Blankflash only works if device is in EDL mode.
Sent from my ali using XDA Labs
---------- Post added at 02:07 AM ---------- Previous post was at 02:04 AM ----------
Did you ever unlock the bootloader?
Sent from my ali using XDA Labs
Did you ever unlock the bootloader?
Click to expand...
Click to collapse
no, I never did anything on it. Just tryed after it happens, but anything have worked
Edu Furin said:
no, I never did anything on it. Just tryed after it happens, but anything have worked
Click to expand...
Click to collapse
I believe your only option is RSD Lite
You will need a Windows 7 pc.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Did you do try flashing something before it did this?
Click to expand...
Click to collapse
Hmm. I'll try it and back to tell what happened. Thanks a lot for your attention.
Edu Furin said:
Hmm. I'll try it and back to tell what happened. Thanks a lot for your attention.
Click to expand...
Click to collapse
Did it work?

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

Categories

Resources