Recover hard-bricked Max Lumi 2

[richard.black]

Okay, I figured part of the problem, there are logical partitions like userdata, cache, metadata but there aren't formatted (say, in ext4 format). That's why even android recovery can't mount them and thus the No such file or directory errors.
Do you know about those formatting options and also the procedure?
Another parition is /misc, do you know any more?
I think it can be found at /dev/block/bootdevice/by-name

PS:I'm almost sure there's nothing wrong with my super partition. The blue light stays after booting up, which wasn't the case for the last month.

PPS: If the device only supports 1 "active slot", the _b partitions should have the data duplicate of _a?

[Renate]

You have a gazillion partitions. Half of them are not a formatted filesystems. They only hold one file. Most of those are ELF files, like xbl, abl, cmnlib, modem... Many are even empty, all zeroes. misc is just raw unstructured flash memory.

There are only four logical partitions, system, system_ext, product, vendor. They are in the physical partition super which is not a "real" filesystem like ext4.

cache is a tmpfs, it's only using RAM for storage which is why the contents disappear when you reboot.

Since "splash" is not used, I used it recently to debug a custom recovery by just writing text to it like one big file. Unlike cache, after crashing and reset the contents are still there.

You didn't mention the blue light before. Are you sure that it is supposed to be on when it's happy?

[richard.black]

You have a gazillion partitions. Half of them are not a formatted filesystems. They only hold one file. Most of those are ELF files, like xbl, abl, cmnlib, modem... Many are even empty, all zeroes. misc is just raw unstructured flash memory.

There are only four logical partitions, system, system_ext, product, vendor. They are in the physical partition super which is not a "real" filesystem like ext4.

cache is a tmpfs, it's only using RAM for storage which is why the contents disappear when you reboot.

Since "splash" is not used, I used it recently to debug a custom recovery by just writing text to it like one big file. Unlike cache, after crashing and reset the contents are still there.

Ok then,

You didn't mention the blue light before. Are you sure that it is supposed to be on when it's happy?

I think so, because the blue led light on power stays on the entire time the device is running, properly. For the last month, there was no led.

[richard.black]

Okay then, what do you think these errors mean when I use Factory reset/wipe data:

E: Failed to clear BCB message: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
E: Failed to WriteUpdateInProgress: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
failed to stat /dev/block/bootdevice/by-name/misc
-- Wiping data
E: [libfs_mgr]Skipping mounting '/dev/block/bootdevice/by-name/metadata’
E: [libfs_mgr]Failed to open '/dev/block/bootdevice/by-name/metadata’: No such file or directory
E: [libfs_mgr]Failed to mount /metadata; formatting: No such file or directory
E: [libfs_mgr]fs_mgr_do_format: Format /dev/block/bootdevice/by-name/metadata as 'ext4’

E: [libfs_mgr]Cannot open block device: No such file or directory

E: [libfs_mgr]lFailed to format /metadata: No such file or directory

E: Cannot mount /metadata/ota

E: format_volume: failed to open /dev/block/bootdevice/by-name/userdata: No such file or directory

Formatting /metadata...

E: /system/bin/mke2fs failed with status 1

E: format_volume: Failed to make ext4 on /dev/block/bootdevice/by-name/metadata: Success

Data wipe failed.

E: Failed to WriteUpdateInProgress: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory

[Renate]

Posting clash.

[Renate]

Originally Posted by richard.black

E: format_volume: Failed to make ext4 on /dev/block/bootdevice/by-name/metadata: Success

Oh, that makes lots of sense.

So, use EDL and pull a copy of metadata

You can check it too:

7zip l metadata

[richard.black]

Uhh...

[Renate]

Sometimes I have this dream where I actually have internet.

Oh, and the download failed.

Ok, it looks reasonably sane to me:

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
1969-12-31 17:24:49 D....                            lost+found
1969-12-31 17:25:01 D....                            vold
1969-12-31 17:25:01 D....                            password_slots
2024-09-10 04:05:49 D....                            bootstat
2024-09-10 04:04:40 D....                            ota
1969-12-31 17:25:01 D....                            apex
1969-12-31 17:25:01 D....                            staged-install
1969-12-31 17:25:01 D....                            gsi
1969-12-31 17:25:01 D....                            vold\metadata_encryption
2024-09-10 04:05:49 .....           10         8192  bootstat\persist.sys.boot.reason
1969-12-31 17:25:01 D....                            ota\snapshots
1969-12-31 17:25:01 D....                            apex\sessions
1969-12-31 18:22:22 D....                            gsi\dsu
1969-12-31 17:25:01 D....                            gsi\ota
1969-12-31 17:25:01 D....                            gsi\remount
1969-12-31 18:22:22 D....                            gsi\dsu\avb
1969-12-31 17:25:01 D....                            vold\metadata_encryption\key
1969-12-31 17:25:01 .....            1         8192  vold\metadata_encryption\key\version
1969-12-31 17:25:01 .....        16384        20480  vold\metadata_encryption\key\secdiscardable
1969-12-31 17:25:01 .....           10         8192  vold\metadata_encryption\key\stretching
1969-12-31 17:25:01 .....          214         8192  vold\metadata_encryption\key\keymaster_key_blob
1969-12-31 17:25:01 .....          220         8192  vold\metadata_encryption\key\encrypted_key
1969-12-31 18:22:22 .....         1032         8192  gsi\dsu\avb\s-gsi.avbpubkey
1969-12-31 18:22:22 .....         1032         8192  gsi\dsu\avb\r-gsi.avbpubkey
1969-12-31 18:22:22 .....         1032         8192  gsi\dsu\avb\q-gsi.avbpubkey
1969-12-31 17:24:49 .....      4194304      4194304  [SYS]\Journal
------------------- ----- ------------ ------------  ------------------------
2024-09-10 04:05:49            4214239      4280320  10 files, 16 folders

[richard.black]

Sometimes I have this dream where I actually have internet.

I can only imagine...
Sometimes, I wonder about you and other people who are always on forums. Posting on a forums is a new experience for me. How interesting your life must be?

Also, what should I do next?

[Renate]

Originally Posted by richard.black

How interesting your life must be?

I try to mix it up. Yesterday I tried to stay off the internet. I hiked for two hours and practised guitar a good chunk of the day. Occasionally I even get to read a book on my Go6. 400 pages in on Gulag, Anne Applebaum.

You're not going forward anywhere until you can manage to get ADB working on something. Is recovery showing ADB unauthorized now? Did you post me recovery already? I forget.

[richard.black]

My life is pretty boring. Everyone expects me to just study and that's all I do, study and nothing more.

You're not going forward anywhere until you can manage to get ADB working on something. Is recovery showing ADB unauthorized now? Did you post me recovery already? I forget.

Only ADB sideload command works.

.\adb.exe devices
List of devices attached
XXXXXXXX        sideload
.\adb.exe get-state
sideload

the only other command that works is get-serialno.

Is recovery showing ADB unauthorized now?

Yes, adb is unauthorized.
Recovery looks loke this:

Android Recovery
ONYX/BOOX/BOOX
11/RKQ1.210614.002/200
userdebug/release-keys
Use volume up/down and power.
WARNING: Previous installation has failed.
  You device may fail to boot if you reboot or power off now.
-----
Reboot system now
Reboot to bootloader
Enter fastboot
Apply update from ADB // adb sideload works here, not adb
Apply update from SD card
Wipe data/factory reset
Mount /system
View recovery logs
Run graphics test
Run locale test
 Power off
-----

[Renate]

I've never used sideload. Does that give you all the mount errors you were showing?

[richard.black]

I've never used sideload. Does that give you all the mount errors you were showing?

No,
When I use adb sideload, error status 1,

E: Error in /sideload/package.zip (status 1)
Install from ADB complete with status 1.
Installation aborted.

When I use Factory Reset/Wipe Data,

E: Failed to clear BCB message: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
E: Failed to WriteUpdateInProgress: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
failed to stat /dev/block/bootdevice/by-name/misc
-- Wiping data
E: [libfs_mgr]Skipping mounting '/dev/block/bootdevice/by-name/metadata’
E: [libfs_mgr]Failed to open '/dev/block/bootdevice/by-name/metadata’: No such file or directory
E: [libfs_mgr]Failed to mount /metadata; formatting: No such file or directory
E: [libfs_mgr]fs_mgr_do_format: Format /dev/block/bootdevice/by-name/metadata as 'ext4’

E: [libfs_mgr]Cannot open block device: No such file or directory

E: [libfs_mgr]Failed to format /metadata: No such file or directory

E: Cannot mount /metadata/ota

E: format_volume: failed to open /dev/block/bootdevice/by-name/userdata: No such file or directory

Formatting /metadata...

E: /system/bin/mke2fs failed with status 1

E: format_volume: Failed to make ext4 on /dev/block/bootdevice/by-name/metadata: Success

Data wipe failed.

E: Failed to WriteUpdateInProgress: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory

[Renate]

I don't know why your recovery is so broken. Did you ever send the updated recovery image to me? Please zip.

[richard.black]

Hey, here is my recovery:
https://send.vis.ee/download/db4de09...RY-2zca6u_FocA