slot-bootable invalid? - Moto E5 Questions & Answers

Hi!
i have put 10+ hours scouring with google trying to find an answer but no luck
a friend just wants his important pictures off this moto e5 that started going in a bootloop
first bought a new e5 and replaced the old motherboard into it ( shorted power switch )
which allowed to boot into a black screen asking to enter password to start android
put his password in, says Starting android . . . then reboots into a dim Moto boot screen that keeps shutting on and off indefinately
tried LMSA flashing the firmware (had stock firmware, locked ) but did not solve the problem ( used fastboot to flash, to prevent loss of userdata ) getvar seems to confirm flashing was succesful, as the version changed to what LMSA downloaded
here is getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.C2
(bootloader) product: nora
(bootloader) board: nora
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 10
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZL522CJDL8
(bootloader) cid: 0x000F
(bootloader) channelid: 0x8c
(bootloader) uid: 8AAA5BDC00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354132092918369
(bootloader) meid:
(bootloader) date: 01-12-2019
(bootloader) sku: XT1920DL
(bootloader) carrier_sku: XT1920DL
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/nora_trac/nora:8.1.0/OPPS
(bootloader) ro.build.fingerprint[1]: 28.44-26-17-14/ddb17:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.341.16.nora_trac.
(bootloader) ro.build.version.full[1]: tracfone.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08300-89xx.0
(bootloader) version-baseband: M8920_35.27.11.78R NORA_TRACFONE_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g7f59b2e4b062
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.8
(bootloader) kernel.version[2]: (GCC) ) #1 SMP PREEMPT Thu Apr 30 11:39:
(bootloader) kernel.version[3]: 39 CDT 2020
(bootloader) sbl1.git: git=MBM-NG-VB9.C2-0-gd1298dd
(bootloader) rpm.git: git=37ff2d71-dirty
(bootloader) tz.git: git=7716735586
(bootloader) devcfg.git: git=7716735586
(bootloader) keymaster.git: git=7716735586
(bootloader) cmnlib.git: git=7716735586
(bootloader) cmnlib64.git: git=7716735586
(bootloader) prov.git: git=7716735586
(bootloader) aboot.git: git=MBM-NG-VB9.C2-0-g82759fa
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tracfone
(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
im thinking the problem is lying in those INVALID notes at the bottom there but do not know enough fastboot commands to figure out a fix
do not care about getting the phone to work at all so only help will be from being able to access userdata one way or another
it is stock locked unrooted etc
hope that is helpful for helping
much appreciated!
maka

encryption is hardware-backed, one can't replace motherboard like this.

Related

Motorola One Lite (X 1941-4) fastboot brick

Start Up Failed:
Your device didn't start up successfully.
...
Blocked into fastboot - Bootloader logs after wrong firmware adb flashing.
Flashed the android 10 update via lenovo moto smart assistant, it worked, after that it wouldn't recognise my phone, had the boot message "Your device has failed verification and may not work properly" and I tried to get rid of it plus that android 10 looked laggy in comparison with android 9, so i tried to flash the lastest android 9 rom so I bricked my phone. Tried to flash the android 10 rom available here and every rom I found for my phone. My bootloader is locked, i cannot unlock it bc i forgot to unlock oem and I'm stuck with the bricked phone. Tried to flash via RSD Lite, didn't recognise, flashed via adb, via Moto Flash Tool, tried everything. I know it could be blankflashed via EDL Mode, but I cannot get it in EDL mode, i don't have an EDL cable, i can't pin or i don't know how to short-circuit the pinpoint and don't have the tools to disassemble the phone. Please help me, I bought this phone like a week ago and I bricked it in the third day. Thank you very much!
Info form fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-c30fda1-200130
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY326936FS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 01EF607800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 359548095218017
(bootloader) meid:
(bootloader) date: 06-18-2019
(bootloader) sku: XT1941-4
(bootloader) carrier_sku: XT1941-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 31 11:14:27 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:10/QPK30
(bootloader) ro.build.fingerprint[1]: .54-22/6add:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.r1-02600-89xx.0
(bootloader) version-baseband: M8953_37.155.02.28R DEEN_APACDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.124-perf-gb0c3168-dir
(bootloader) kernel.version[1]: ty ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .9.x 20150123 (prerelease) (GCC) ) #1 SM
(bootloader) kernel.version[3]: P PREEMPT Thu Jan 30 10:24:24 CST 2020
(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-deen_retail-c30fda1-200130
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.180s
Thank you!

SIM Card not detected (IMEI Detected) -- (XT1925-6)

Like title says, both custom rom and stock rom both show no SIM card. This happened after I flashed the unofficial LineageOS 16.0 custom rom and Magisk to my device. To fix this problem, I followed steps from this guide to return to stock, using the the most recent link to get a stock rom from that guide. This did not fix the problem, and I decided to instead flash TWRP again and boot into a 64 bit custom rom, this time Resurrection Remix v8.6.1, with Magisk and GApps, and this did not fix the problem either. What makes this different than other posts is that I still have a IMEI showing; other people do not. I honestly don't know how to fix this, if someone who knows more than me could help me that would be amazing, as the phone is unusable as a daily driver as I cannot text or call.
getvar all is in first comment.
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-a49aaf1-200210
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: ZY323R9SH5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 0E9F269F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351849095641358
(bootloader) meid:
(bootloader) date: 08-23-2019
(bootloader) sku: XT1925-6
(bootloader) carrier_sku: XT1925-6
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Oct 4 19:16:23 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:9/PPSS29.118-15-1
(bootloader) ro.build.fingerprint[1]: 1-9/34527:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.261.12.ali.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M450_21.29.10.88R ALI_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g2af0cec (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Mon Feb 10 13:05:19 CST 2020
(bootloader) sbl1.git: MBM-2.1-ali_retail-5e07748-200210
(bootloader) rpm.git: MBM-2.1-ali_retail-218e5af-200210
(bootloader) tz.git: MBM-2.1-ali_retail-e220b21-200210
(bootloader) devcfg.git: MBM-2.1-ali_retail-e220b21-200210
(bootloader) keymaster.git: MBM-2.1-ali_retail-e220b21-200210
(bootloader) cmnlib.git: MBM-2.1-ali_retail-e220b21-200210
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-e220b21-200210
(bootloader) prov.git: MBM-2.1-ali_retail-e220b21-200210
(bootloader) aboot.git: MBM-2.1-ali_retail-a49aaf1-200210
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: retus
(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.528s
Try to wipe carrier, modemst1 and modemst2 from adb.
This should solve your problem on stock.

lost imei number XT1921-1

tried changing my rom and lost my imei/ wifi/ ect.but could still get into my phone. tried fixing it and somehow cant access even recovery mode now. onlly the boot loader. it also reads bad key error and my base band is not found ( not sure what that means). please see attached photos
ghettozo said:
tried changing my rom and lost my imei/ wifi/ ect.but could still get into my phone. tried fixing it and somehow cant access even recovery mode now. onlly the boot loader. it also reads bad key error and my base band is not found ( not sure what that means). please see attached photos
Click to expand...
Click to collapse
when i type getvar all u get this
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BE.43
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: ZY322RBWLD
(bootloader) cid: 0x0032
(bootloader) channelid: 0x81
(bootloader) uid: 7053A6DC00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351839090672631
(bootloader) meid:
(bootloader) date: 05-22-2018
(bootloader) sku: XT1921-1
(bootloader) carrier_sku: XT1921-1
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_t_f/james_f:8.0.0/O
(bootloader) ro.build.fingerprint[1]: CP27.91-51-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5480efb-0001
(bootloader) kernel.version[1]: 6-gd2768b6 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 20 10:36:48 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VBE.43-0-geb7a3e0
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=c928765-dirty
(bootloader) devcfg.git: git=c928765-dirty
(bootloader) keymaster.git: git=c928765
(bootloader) cmnlib.git: git=c928765
(bootloader) cmnlib64.git: git=c928765
(bootloader) prov.git: git=c928765-dirty
(bootloader) aboot.git: git=MBM-NG-VBE.43-0-g32616d4
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: bwaca
(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.533s

[HELP] Phone bricked

Greetings, I'm recurring to this community since I'm kinda desperate (and a bit hopeless) with my phone. So, I was trying to move from Pixel Experience 10 to PE 11, and the process got stucked in twrp, so foolish me, restarted the phone thinking I was gonna be able to start over. So I find myself with no os on my phone and I can't make it start in anyway.
I tried:
- Rescue and Smart Assistant (the only time it worked, after 4 hours, I don't know if reached the 100% completation, throw an error, didn't took note since I thought the cable got moved and tried to start again, with no luck)
- Using flashboot with the files I got from the stock .zip
- locking bootloader (with no success)
I was able to get different results, in one time, apparently worked but got the "invalid key" when trying to launch. In the phone I got error like "failed to load kernel". I'm still able to enter flashboot, so I don't know how bricked my phone is.
I'm far from being experienced, I was searching old posts but, like I said, I'm not being able to get my phone to work. Hope someone can help me.
Results from fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: xxxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1a
(bootloader) uid: xxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: (is here but I covered)
(bootloader) meid:
(bootloader) date: 12-08-2017
(bootloader) sku: XT1800
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jan 4 8:45:47 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_52.61.07.98R SANDERS_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(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 Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=d95e83f
(bootloader) devcfg.git: git=d95e83f
(bootloader) keymaster.git: git=d95e83f
(bootloader) cmnlib.git: git=d95e83f
(bootloader) cmnlib64.git: git=d95e83f
(bootloader) prov.git: git=d95e83f
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retar
(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.176s

Motorola bricked my G6

So I did the usual process, fastboot, got the code, sent it to motorola, got the email with the new code, unlocked, flashed twrp, etc.
I wanted to stop the phone from showing the stupid message it always does on boot so I relocked the bootloader.
Now its saying my device has "failed verification" which tells me motorola sent me a bad code. The phone refuses to boot. The kicker is that fastboot locked ANYWAY, so now I can't even use the windows utility to rescue the phone.
Is there anything I can do to get this usable or is it just landfill fodder now?
EDIT:: also I can't unlock the bootloader again due to "invalid boot state"
getvar output below:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: [REDACTED]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: EFA9BC5A00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [REDACTED]
(bootloader) meid:
(bootloader) date: 07-29-2018
(bootloader) sku: XT1925-6
(bootloader) carrier_sku: XT1925-6
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 23 18: 5: 1 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:9/PPS29.118-15-11
(bootloader) ro.build.fingerprint[1]: -16/3afd9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.4.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M450_23.31.10.89R ALI_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g19723945513
(bootloader) kernel.version[1]: 7-04290-gfb8faa3398e9 ([email protected]
(bootloader) kernel.version[2]: 71) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[3]: ase) (GCC) ) #1 SMP PREEMPT Thu Apr 23 1
(bootloader) kernel.version[4]: 1:51:22 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ali_retail-5e077487fa-200423
(bootloader) rpm.git: MBM-2.1-ali_retail-218e5afd-200423
(bootloader) tz.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) devcfg.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) keymaster.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) prov.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) aboot.git: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(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.073s
Nevermind. I was able to run fastboot flashing unlock and now I can boot into lineage. It was 5 am when I was trying to do this and I was in a rush.

Categories

Resources