Database Users

I've totally bricked my Essential: no A/B partitions?

After a nice long session of getting my phone to root and installing my first custom ROM, I was sad to see after booting successfully, there was no touch.
I thought, "oh well" and tried to flash back to stock. This is where I think I made a critical error. I tried flashing the stock OTA, Fastboot files, and the BACK_TO_STOCK files from the XDA thread. Nothing worked and I tried to change my slot, only to get the message "Fastboot: error: Device does not support slots." Additionally, when I try to flash-all from the fastboot files, it tells me i basically have no partitions. I do still have twrp though so all is not lost and I can boot into the bootloader.

tonafish12 said:
After a nice long session of getting my phone to root and installing my first custom ROM, I was sad to see after booting successfully, there was no touch.
I thought, "oh well" and tried to flash back to stock. This is where I think I made a critical error. I tried flashing the stock OTA, Fastboot files, and the BACK_TO_STOCK files from the XDA thread. Nothing worked and I tried to change my slot, only to get the message "Fastboot: error: Device does not support slots." Additionally, when I try to flash-all from the fastboot files, it tells me i basically have no partitions. I do still have twrp though so all is not lost and I can boot into the bootloader.
Click to expand...
Click to collapse
lol, your not totally bricked, sounds like you have a fastboot driver thats old

I had this problem too when I was trying to get TWRP + Magisk + EX kernel working.
I found that my Essential phone is pretty picky with what commands it accepts. Maybe this is due to a silent bootloader update, maybe not. A lot of commands work only if you spam them.
What Fastboot do you have?

aer0zer0 said:
lol, your not totally bricked, sounds like you have a fastboot driver thats old
Click to expand...
Click to collapse
I'm having the same issue as the OP so I grabbed the latest driver from essential (I was using an older release) but it hasn't made a difference.
Is there a known way to verify the partition structure on this device? For both slots

bavarianblessed said:
I'm having the same issue as the OP so I grabbed the latest driver from essential (I was using an older release) but it hasn't made a difference.
Is there a known way to verify the partition structure on this device? For both slots
Click to expand...
Click to collapse
You want to use the driver included in essential windows driver.exe on their website. The Google ones are a little goofy.
Can you do *fastboot --version* (that's minus minus version) and send the output?

Also try a different USB cable from the one that came with the phone, if you were using that one. Mine doesn't respond properly with that one, but a USB-A to USB-C cable from Anker that I bought works fine.

aer0zer0 said:
You want to use the driver included in essential windows driver.exe on their website. The Google ones are a little goofy.
Can you do *fastboot --version* (that's minus minus version) and send the output?
Click to expand...
Click to collapse
Yep, here is the version info. With some of the errors I was getting trying to flash it I grabbed the latest from Google
Code:
C:\ADB\PH1-Images-PPR1.181005.034>fastboot --version
fastboot version 28.0.1-4986621
Installed as C:\ADB\PH1-Images-PPR1.181005.034\fastboot.exe
dsip said:
Also try a different USB cable from the one that came with the phone, if you were using that one. Mine doesn't respond properly with that one, but a USB-A to USB-C cable from Anker that I bought works fine.
Click to expand...
Click to collapse
Yeah I've tried an Ankar and a Samsung so far. I've had better luck with another cable in the past though so going to try and find it.
EDIT
This is so odd. If I try to run this command a few times it finally takes?
Code:
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
all:
Finished. Total time: 0.000s
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
all:
Finished. Total time: 0.000s
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
(bootloader) version:0.5
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4192
(bootloader) version-baseband:2.0.c4-M2.0.3
(bootloader) version-bootloader:mata-84f7cce
(bootloader) variant:SPRINT
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1987357000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x100000000
(bootloader) has-slot:nvdef:yes
(bootloader) has-slot:dsp:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:abl:yes
(bootloader) has-slot:mdtp:yes
(bootloader) has-slot:mdtpsecapp:yes
(bootloader) has-slot:bluetooth:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:_b
(bootloader) slot-retry-count:_b:1
(bootloader) slot-unbootable:_b:no
(bootloader) slot-successful:_b:no
(bootloader) slot-retry-count:_a:7
(bootloader) slot-unbootable:_a:no
(bootloader) slot-successful:_a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:PM1#############
(bootloader) product:Mata
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
all:
Finished. Total time: 0.249s

bavarianblessed said:
Yep, here is the version info. With some of the errors I was getting trying to flash it I grabbed the latest from Google
Yeah I've tried an Ankar and a Samsung so far. I've had better luck with another cable in the past though so going to try and find it.
EDIT
This is so odd. If I try to run this command a few times it finally takes?
Click to expand...
Click to collapse
Do you have essentials windows driver executable installed?

aer0zer0 said:
Do you have essentials windows driver executable installed?
Click to expand...
Click to collapse
Yeah I have it installed. It was the cable! For real I would have thought the Samsung GS9 OEM cable would be high quality enough.
Anyway thanks for the help.

bavarianblessed said:
EDIT
This is so odd. If I try to run this command a few times it finally takes?
Code:
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
all:
Finished. Total time: 0.000s
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
all:
Finished. Total time: 0.000s
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
(bootloader) version:0.5
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4192
(bootloader) version-baseband:2.0.c4-M2.0.3
(bootloader) version-bootloader:mata-84f7cce
(bootloader) variant:SPRINT
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1987357000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x100000000
(bootloader) has-slot:nvdef:yes
(bootloader) has-slot:dsp:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:abl:yes
(bootloader) has-slot:mdtp:yes
(bootloader) has-slot:mdtpsecapp:yes
(bootloader) has-slot:bluetooth:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:_b
(bootloader) slot-retry-count:_b:1
(bootloader) slot-unbootable:_b:no
(bootloader) slot-successful:_b:no
(bootloader) slot-retry-count:_a:7
(bootloader) slot-unbootable:_a:no
(bootloader) slot-successful:_a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:PM1#############
(bootloader) product:Mata
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
all:
Finished. Total time: 0.249s
Click to expand...
Click to collapse
That seems to be a normal thing with Essential devices to be honest, I've had 2 and both have been lets say slow and picky at accepting some ADB/Fastboot commands. On the OPENAM variant it was even more of a problem (no idea why), but the white OPENUS replacement I have now hasn't been too much of an issue. I've not had to specify everytime I'm in Fastboot which slot I want to flash to specifically, for example...
At least its not like we have plenty of Pie ROMs to flash over and over, so ultimately its not that much of an issue.

CamoGeko said:
EDIT
This is so odd. If I try to run this command a few times it finally takes?
That seems to be a normal thing with Essential devices to be honest, I've had 2 and both have been lets say slow and picky at accepting some ADB/Fastboot commands. On the OPENAM variant it was even more of a problem (no idea why), but the white OPENUS replacement I have now hasn't been too much of an issue. I've not had to specify everytime I'm in Fastboot which slot I want to flash to specifically, for example...
At least its not like we have plenty of Pie ROMs to flash over and over, so ultimately its not that much of an issue.
Click to expand...
Click to collapse
It just gets corrupted easily. I found formatting fixes it.either with twrp, or the verity disabler by zackptg.then flash the whole current stock firmware and start over. They got some issues internally with easy corruption it seems

CamoGeko said:
That seems to be a normal thing with Essential devices to be honest, I've had 2 and both have been lets say slow and picky at accepting some ADB/Fastboot commands. On the OPENAM variant it was even more of a problem (no idea why), but the white OPENUS replacement I have now hasn't been too much of an issue. I've not had to specify everytime I'm in Fastboot which slot I want to flash to specifically, for example...
At least its not like we have plenty of Pie ROMs to flash over and over, so ultimately its not that much of an issue.
Click to expand...
Click to collapse
Actually in my case it was just the cable. Using the known good cable that command will work every single time as well as any others I try. Mine is a white SPRINT variant.
For the record this is the cable that I'm using

Try fastboot flashing Google's Offical GSI?

MY FRIENDS, HELP ME:NOKIA 4.2 Panther - my A and b slots are gone, Nokia flash tool says current slot invalid, Adb also :
current-slot: INVALID
finished. total time: 0.002s
here is what I have:
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3946070
(bootloader) variant:QRD eMMC
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) logical-block-size:0x200
(bootloader) erase-block-size:0x200
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1ff00000
(bootloader) slot-count:2
(bootloader) current-slot:INVALID
(bootloader) slot-retry-count:b:7
(bootloader) slot-success:b:No
(bootloader) slot-active:b:No
(bootloader) slot-unbootable:b:No
(bootloader) slot-retry-count:a:0
(bootloader) slot-success:a:No
(bootloader) slot-active:a:No
(bootloader) slot-unbootable:a:Yes
(bootloader) has-slot:userdata: No
(bootloader) has-slot:demoapp: No
(bootloader) has-slot:elabel: No
(bootloader) has-slot:wt_log: No
(bootloader) has-slot:logdump: No
(bootloader) has-slot:dpo: No
(bootloader) has-slot:msadp: No
(bootloader) has-slot:apdp: No
(bootloader) has-slot:custom: Yes
(bootloader) has-slot:keymaster: Yes
(bootloader) has-slot:cmnlib64: Yes
(bootloader) has-slot:cmnlib: Yes
(bootloader) has-slot:mcfg: No
(bootloader) has-slot:syscfg: No
(bootloader) has-slot:mdtp: Yes
(bootloader) has-slot:dip: No
(bootloader) has-slot:mota: No
(bootloader) has-slot:limits: No
(bootloader) has-slotem: No
(bootloader) has-slot:config: No
(bootloader) has-slot:keystore: No
(bootloader) has-slot:misc: No
(bootloader) has-slotersist: No
(bootloader) has-slot:vendor: Yes
(bootloader) has-slot:system: Yes
(bootloader) has-slot:devinfo: No
(bootloader) has-slot:boot: Yes
(bootloader) has-slot:vbmeta: Yes
(bootloader) has-slot:dtbo: Yes
(bootloader) has-slot:aboot: Yes
(bootloader) has-sloticture: Yes
(bootloader) has-slot:splash: Yes
(bootloader) has-slot:sec: No
(bootloader) has-slot:fsg: No
(bootloader) has-slotDR: No
(bootloader) has-slot:modemst2: No
(bootloader) has-slot:modemst1: No
(bootloader) has-slot:dsp: Yes
(bootloader) has-slot:devcfg: Yes
(bootloader) has-slot:tz: Yes
(bootloader) has-slot:rpm: Yes
(bootloader) has-slot:sbl1: Yes
(bootloader) has-slot:ssd: No
(bootloader) has-slot:fsc: No
(bootloader) has-slot:modem: Yes
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x527679e00
(bootloader) partition-type:demoapp:raw
(bootloader) partition-size:demoapp: 0x4000000
(bootloader) partition-type:elabel:raw
(bootloader) partition-size:elabel: 0x500000
(bootloader) partition-type:wt_log:raw
(bootloader) partition-size:wt_log: 0x4000000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:custom_b:raw
(bootloader) partition-size:custom_b: 0x3200000
(bootloader) partition-type:custom_a:raw
(bootloader) partition-size:custom_a: 0x3200000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x100000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x100000
(bootloader) partition-type:cmnlib64_b:raw
(bootloader) partition-size:cmnlib64_b: 0x100000
(bootloader) partition-type:cmnlib64_a:raw
(bootloader) partition-size:cmnlib64_a: 0x100000
(bootloader) partition-type:cmnlib_b:raw
(bootloader) partition-size:cmnlib_b: 0x100000
(bootloader) partition-type:cmnlib_a:raw
(bootloader) partition-size:cmnlib_a: 0x100000
(bootloader) partition-type:mcfg:raw
(bootloader) partition-size:mcfg: 0x400000
(bootloader) partition-type:syscfg:raw
(bootloader) partition-size:syscfg: 0x80000
(bootloader) partition-type:mdtp_b:raw
(bootloader) partition-size:mdtp_b: 0x2000000
(bootloader) partition-type:mdtp_a:raw
(bootloader) partition-size:mdtp_a: 0x2000000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:mota:raw
(bootloader) partition-size:mota: 0x80000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-typeem:raw
(bootloader) partition-sizeem: 0x4000000
(bootloader) partition-type:config:raw
(bootloader) partition-size:config: 0x8000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-size:vendor_b: 0x28000000
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-size:vendor_a: 0x28000000
(bootloader) partition-type:system_b:raw
(bootloader) partition-size:system_b: 0xc0000000
(bootloader) partition-type:system_a:raw
(bootloader) partition-size:system_a: 0xc0000000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x100000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x4000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x4000000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b: 0x10000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a: 0x10000
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-size:dtbo_b: 0x800000
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-size:dtbo_a: 0x800000
(bootloader) partition-type:aboot_b:raw
(bootloader) partition-size:aboot_b: 0x400000
(bootloader) partition-type:aboot_a:raw
(bootloader) partition-size:aboot_a: 0x400000
(bootloader) partition-typeicture_b:raw
(bootloader) partition-sizeicture_b: 0x600000
(bootloader) partition-typeicture_a:raw
(bootloader) partition-sizeicture_a: 0x600000
(bootloader) partition-type:splash_b:raw
(bootloader) partition-size:splash_b: 0x600000
(bootloader) partition-type:splash_a:raw
(bootloader) partition-size:splash_a: 0x600000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0xa00000
(bootloader) partition-typeDR:raw
(bootloader) partition-sizeDR: 0x8000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x400000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x400000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x1000000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x1000000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x40000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x40000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x200000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x200000
(bootloader) partition-type:rpm_b:raw
(bootloader) partition-size:rpm_b: 0x80000
(bootloader) partition-type:rpm_a:raw
(bootloader) partition-size:rpm_a: 0x80000
(bootloader) partition-type:sbl1_b:raw
(bootloader) partition-size:sbl1_b: 0x80000
(bootloader) partition-type:sbl1_a:raw
(bootloader) partition-size:sbl1_a: 0x80000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0x5400000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0x5400000
(bootloader) hw-revision:10000
(bootloader) pcb_sn:4931806751002093
(bootloader) serialno:4T89571EA1932701086
(bootloader) kernel:lk
(bootloader) productanther
(bootloader) productid:4T89571EA1932701086
(bootloader) MEID:00000000000000
(bootloader) IMEI1:352900100148118
(bootloader) IMEI0:352900100148100
(bootloader) proof:1
all:
finished. total time: 0.805s
WHAT TO DO? THERE NO CHANCE TO ACTIVATE ANY SLOT AND FLASH TO ACTIVE SLOT AS SLOTS ARE INVALID. HELP PLEASE

Moto G7 (Soft brick?)

Hi Guys, i have a moto g7 1962-4.
After flashed the lineage os rom, and installed wrong modules, i decided to install the Havoc Os, after that, my cellphone's restarted on the fastboot(secure) screen.
The oem_turns to lock, says oem_lock
and, i can't flash roms.
The error on start: failed to initialize partition table.
No Bootable A/B Slot, and failed to boot Linux, falling back to the fastboot.
here is my bootloader informations:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-a5c9d71-190801
(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
i can't flash nothing, Its giving me, ex:
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.037s
Remote Failure.
Can someone help me? please angelllllllllllllss

Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.

WoKoschekk said:
Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.
Click to expand...
Click to collapse
and the fastboot details? its like, corrupted?

WoKoschekk said:
Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.
Click to expand...
Click to collapse
Dont Work, Remove Error

Are you able to boot into TWRP via "fastboot boot twrp.img" ? Is there any fastboot command executable on your device?
Can you enter the stock recovery?

WoKoschekk said:
Are you able to boot into TWRP via "fastboot boot twrp.img" ? Is there any fastboot command executable on your device?
Can you enter the stock recovery?
Click to expand...
Click to collapse
Nope, i cant go to the Stock Recovery, and the fastboot boot twrp.img dont work.

if you can't run the following commands then maybe you will need a blankflash...
Just use the gpt.bin and bootloader.img files from your stock rom:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader

Or try RSDlite or any Motorola repair software...

WoKoschekk said:
if you can't run the following commands then maybe you will need a blankflash...
Just use the gpt.bin and bootloader.img files from your stock rom:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Gpt and bootloader don't installs, the remote error its back.

WoKoschekk said:
Or try RSDlite or any Motorola repair software...
Click to expand...
Click to collapse
i tried, the RSD, and not recognize the phone.

So, you can't do anything... I guess the only chance to fix your phone is a blank flash.
I'm sorry but I don't know how to do that.
It would be better for you to use the search function.
Good luck!!

GordinhoBr said:
Hi Guys, i have a moto g7 1962-4.
After flashed the lineage os rom, and installed wrong modules, i decided to install the Havoc Os, after that, my cellphone's restarted on the fastboot(secure) screen.
The oem_turns to lock, says oem_lock
and, i can't flash roms.
The error on start: failed to initialize partition table.
No Bootable A/B Slot, and failed to boot Linux, falling back to the fastboot.
here is my bootloader informations:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-a5c9d71-190801
(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
i can't flash nothing, Its giving me, ex:
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.037s
Remote Failure.
Can someone help me? please angelllllllllllllss
Click to expand...
Click to collapse
Got the same here brow. I've tried everything without success. I took the cell phone in the authorized service and they charged me incredible 840 reais to fix (the phone already costs 899 new in the store). In the G7 plus forum there is a topic talking about Blank Flash. I tried to do it but I need the singleimage.bin file for the G7 model, since there the file is for G7 plus and it doesn't fit. I didn't find this file anywhere on the internet so I tried to build mine. apparently needs to extract the booloader.img file and create from the extracted files the singleimage.bin file with a program called star. For now, assists cannot recover. I already put mue G7 in the drawer and bought an a50, because I believe that in a few months this blank flash file will appear on the internet and solve our case. anyway, good luck! and any news please let me know here! I will do the same.

diegovmsouza said:
Got the same here brow. I've tried everything without success. I took the cell phone in the authorized service and they charged me incredible 840 reais to fix (the phone already costs 899 new in the store). In the G7 plus forum there is a topic talking about Blank Flash. I tried to do it but I need the singleimage.bin file for the G7 model, since there the file is for G7 plus and it doesn't fit. I didn't find this file anywhere on the internet so I tried to build mine. apparently needs to extract the booloader.img file and create from the extracted files the singleimage.bin file with a program called star. For now, assists cannot recover. I already put mue G7 in the drawer and bought an a50, because I believe that in a few months this blank flash file will appear on the internet and solve our case. anyway, good luck! and any news please let me know here! I will do the same.
Click to expand...
Click to collapse
send me you phone number.

Do you have access to Fastboot mode, right?

River blankflash is available on Tel$gram

HueyT said:
River blankflash is available on Tel$gram
Click to expand...
Click to collapse
On what now?

iamcubeman said:
On what now?
Click to expand...
Click to collapse
Telegram

HELP Moto G4 Play CID error

My moto g4 play had hardbrick and I recovered it and it only lets me flash gpt bootloader logo fsg and modem the rest gives me error of preflash validation failed but even with gpt I get imei and serial no but I do not have cid since before brick this it damage with a bad flashing by adb shell dd if even with the brick I can enter qualcomm mode, flashing sbl1 with gpt.bin restart and the computer recognizes it attached my getvar all:
(bootloader) has-slotartition: not found
(bootloader) is-logicalartition: not found
Sending 'partition' (32 KB) OKAY [ 0.094s]
Writing 'partition' (bootloader) This may take a
few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.515s]
Finished. Total time: 0.780s
C:\Users\suwog>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-81.12(*)
(bootloader) product: harpia
(bootloader) board: harpia
(bootloader) secure: yes
(bootloader) hwrev: 0x81B0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Samsung REV=08 PRV=0D TYPE=57
(bootloader) ram: 2GB Samsung S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: ZY223RXJQW
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: 5A9D2C2100000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 268435456
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 354138073943532
(bootloader) meid:
(bootloader) date: 12-04-2016
(bootloader) sku: XT1601
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon May 28 8:28:15 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/harpia/harpia:7.1.1/NPIS2
(bootloader) ro.build.fingerprint[1]: 6.48-43-2/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.26.241.3.harpia.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.2.9-01810-8x16.0
(bootloader) version-baseband[0]: M8916_20250112.18.05.45.01R HARPIA_LAT
(bootloader) version-baseband[1]: AM_CUST
(bootloader) kernel.version[0]: Linux version 3.10.107-6.90-g853fd69-dir
(bootloader) kernel.version[1]: ty ([email protected]) (gcc version 7.1.1 20
(bootloader) kernel.version[2]: 170614 (crosstool-NG crosstool-ng-1.23.0
(bootloader) kernel.version[3]: -90-g81327dd9 - Linaro GCC 7.1-2017.07~d
(bootloader) kernel.version[4]: ev) ) #23 SMP PREEMPT Thu Jul 13 16:35:4
(bootloader) kernel.version[5]: 5 UTC 2017
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: git=MBM-NG-V81.12-0-g5f9a108
(bootloader) tz.git: git=MBM-NG-V81.12-0-gcf5b5ba
(bootloader) hyp.git: git=MBM-NG-V81.12-0-gcf5b5ba
(bootloader) aboot.git: git=MBM-NG-V81.12-0-gf9417da
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (75)
(bootloader) ro.carrier: tefmx
all: listed above

Help needed moto G5 plus - stuck in fastboot menu? cant flash?

I have spent the last 12 hours trying to fix this. I am tech savvy but have never flashed a cellphone before, hence I dunno if I am doing something wrong. And apologies if my terms aren't correct. please correct me when I am wrong.
Phone is a moto G5 plus XT1681 (according to imei), one day it powered to fastboot (see image 1) and what ever I try to press, I get an error. (see image 2)
I followed and tried many guides. but especially this one
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
when I try to run the first line of the script I get the following error.
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
If I keep advancing in the code I get the same error than this guy
Bricked MOTO G5(XT1676) stucked at fastboot menu
hELLO.. I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from...
forum.xda-developers.com
the phone is detectable with command "fastboot devices"
Despite running this, the phone still stays "oem_locked" like in the images
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot oem unlock
(bootloader) feature disabled
OKAY [ 0.017s]
Finished. Total time: 0.018s
I tried also installing TWRP and I get this error (because maybe that bypasses a locked bootloader?)
"(bootloader) Preflash validation failed
FAILED (remote failure)¨
And here is the log for what I learned that you always ask for
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: ca31f0ad
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 423FF92E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(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: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(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.175s
QUESTIONS
Am I just confusing rom because of firmware or country?
is all of this because my bootloader seems locked?
do I just need to get to recovery mode first?
I just want the phone to work, don't care for the data inside.
Other people that seem to be stuck with the same problem
https://forum.xda-developers.com/t/...-question-noob-friendly.3963645/post-85232253
THANKS IN ADVANCE AND SORRY FOR THE LONG POST I WANTED TO GIVE ALL MY INFORMATION AND RESEARCH

Same problem here.

soft brick after flash attempt on redmi note 7 (twrp recovery fail)

Hi there,
I hope there are some experts present that are willing to help me because I think i messed up. After my redmi note 7 was unable to connect with 3G or 4G networks for over a month and even a factory reset didnt fix it, I was thinking about flashing a new custom rom like lineage or similar (the only solution that seems to have fixed these connection issues for some people)
I knew that in some redmi phones the bootloder is locked but I couldn't remember if i unlocked it a few years ago already. "fastboot oem device-info" command gave this message
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.048s]
finished. total time: 0.054s
so in my opinion i was all set up, but the next step is where everything turned sour. I downloaded the twrp recovery.img file for redmi note 7 (lavender) from their official website and followed the guide until:
5. Flash recovery onto your device (replace <recovery_filename> with the actual filename!):
fastboot flash recovery <recovery_filename>.img
Click to expand...
Click to collapse
after my command "fastboot flash recovery twrp.img" I got the message "flashing successfull OKAY" followed by a "too many open files in system" error. Since then I can't boot my phone anymore except into the fastboot screen. Recovery menu doesn't boot either. The Device is still recognized by my pc while in fastboot but the only command that seems to work now is "fastboot devices" which shows the phone.
Is there any way to revive the phone without doing some circuit board surgery or am I out of luck?

Hi it seems like a few more commands are still working "getvar all" gave me this log file. No idea if it helps
(bootloader) crc:1
(bootloader) anti:4
(bootloader) DP:0x0
(bootloader) token:VQEBIgEQhgkJViwWK+EoHYAEQhxzOgMIbGF2ZW5kZXICBMighLI=
(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:10000
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4238
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x56FBF7E00
(bootloader) partition-type:cust:raw
(bootloader) partition-size:cust: 0x34000000
(bootloader) partition-type:vendor:raw
(bootloader) partition-size:vendor: 0x80000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xE0000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:recovery:raw
(bootloader) partition-size:recovery: 0x4000000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0xC000000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-typeersistbak:raw
(bootloader) partition-sizeersistbak: 0x2000000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x4000000
(bootloader) partition-type:dtbobak:raw
(bootloader) partition-size:dtbobak: 0x800000
(bootloader) partition-type:dtbo:raw
(bootloader) partition-size:dtbo: 0x800000
(bootloader) partition-type:bk2:raw
(bootloader) partition-size:bk2: 0x1000000
(bootloader) partition-type:mdtp:raw
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:bk1:raw
(bootloader) partition-size:bk1: 0x1800000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x800000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x800000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x800000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x800000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-type:xblbak:raw
(bootloader) partition-size:xblbak: 0x380000
(bootloader) partition-type:xbl:raw
(bootloader) partition-size:xbl: 0x380000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:bluetooth:raw
(bootloader) partition-size:bluetooth: 0x100000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x100000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x100000
(bootloader) partition-type:mdtpsecappbak:raw
(bootloader) partition-size:mdtpsecappbak: 0x400000
(bootloader) partition-type:mdtpsecapp:raw
(bootloader) partition-size:mdtpsecapp: 0x400000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x400000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x400000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x100000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x100000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:ablbak:raw
(bootloader) partition-size:ablbak: 0x100000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x100000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x100000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x100000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x100000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x100000
(bootloader) partition-typemicbak:raw
(bootloader) partition-sizemicbak: 0x80000
(bootloader) partition-typemic:raw
(bootloader) partition-sizemic: 0x80000
(bootloader) partition-type:hypbak:raw
(bootloader) partition-size:hypbak: 0x80000
(bootloader) partition-type:hyp:raw
(bootloader) partition-size:hyp: 0x80000
(bootloader) partition-type:rpmbak:raw
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:storsecbak:raw
(bootloader) partition-size:storsecbak: 0x20000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:vbmetabak:raw
(bootloader) partition-size:vbmetabak: 0x10000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x5000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x8000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x2000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:switch:raw
(bootloader) partition-size:switch: 0x2000
(bootloader) secure:yes
(bootloader) serialno:87e1ca97
(bootloader) product:lavender
(bootloader) max-download-size:402653184
(bootloader) kernel:uefi
all:
finished. total time: 0.557s
Click to expand...
Click to collapse

Check if this tool helps you revive your device back to normal state
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
www.xiaomitool.com
Tavero said:
Hi it seems like a few more commands are still working "getvar all" gave me this log file. No idea if it helps
Click to expand...
Click to collapse

mvikrant97 said:
Check if this tool helps you revive your device back to normal state
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
www.xiaomitool.com
Click to expand...
Click to collapse
Thanks,
But during flashing I got this error:
Fastboot flash all failed, exit code: 1, output: Missmaching image and device
What img do i have to pick? there my model is M1901F7G
Do you know a recovery.img that is actually working? Official TWRP and orange fox are both not working.

Tavero said:
Thanks,
But during flashing I got this error:
Fastboot flash all failed, exit code: 1, output: Missmaching image and device
What img do i have to pick? there my model is M1901F7G
Do you know a recovery.img that is actually working? Official TWRP and orange fox are both not working.
Click to expand...
Click to collapse
I will get back to you on this tomorrow.

I figured I try XiaMiTool again and found the correct image in that list (I think) which was actually called lavender Redmi note 7 (not redmi 7)
I got a different error though:
Fastboot flash all failed, exit code: 1, output: "Flash xbl error"

Tavero said:
I figured I try XiaMiTool again and found the correct image in that list (I think) which was actually called lavender Redmi note 7 (not redmi 7)
I got a different error though:
Fastboot flash all failed, exit code: 1, output: "Flash xbl error"
Click to expand...
Click to collapse
I have a tool called unlock tool which can flash your device in edl mode.
I can flash your device if it is Lavender. I have access to auth flash your device.

mvikrant97 said:
I have a tool called unlock tool which can flash your device in edl mode.
View attachment 5918089
I can flash your device if it is Lavender. I have access to auth flash your device.
View attachment 5918093
Click to expand...
Click to collapse
Hi there,
Well I am out of ideas. No matter what kind of recovery images i tried to flash, Im always getting the same error "too many open files in system"
If you think your method could be successfull I can try it. I really dont know what else i can do.

Tavero said:
Hi there,
Well I am out of ideas. No matter what kind of recovery images i tried to flash, Im always getting the same error "too many open files in system"
If you think your method could be successfull I can try it. I really dont know what else i can do.
Click to expand...
Click to collapse
Please follow this post and let me know if it works and then I'll help you out.
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing Modified by Zesuga Features: Free auth bypass (EDL Mobile) No need credit balance or activation Free unlock EDL Auth device and flash Only need to boot the device in EDL mode What's new...
forum.xda-developers.com