Renate

Thanks for trying. Unfortunately it tries to save that in a directory called "logs". If that directory does not exist already it just loses its mind. Also, the C:\Program Files...

Using Python and preserving your sanity are conflicting goals.

FWIW, SDX75 is also SDX_PINNACLES. There are three loaders here that might work if you aren't Secure Boot: ``` lenovo_motorola/0000000002e80000_467f3020c4cc788d_fhprg.bin samsung/0000000000020000_467f3020c4cc788d_fhprg.bin zte/0000000000030000_467f3020c4cc788d_fhprg.bin ```

Apparently the software won't let you do even an `rs` without a "partition table". Does adding `--memory=nand` make a difference? UBI/MTD/NAND doesn't have GPT partition tables, it has volume tables.

There's the streaming protocol, but there is also the normal Firehose protocol too. I presume that this is NAND and Secure Boot is not enabled?

I tried reading that log but it was so boring it put me to sleep. Fortunately Reader's Digest had the condensed version for impatient people like me: ``` TX: 0d0000000c00000001000000...

``` HELLORSP Mode=3 EXECUTEREQ SERIALNUMREAD EXECUTEDATA EXECUTEREQ MSMHWIDREAD EXECUTEDATA EXECUTEREQ OEMPKHASHREAD EXECUTEDATA SWITCHMODE HELLORSP Mode=0 Raw data 64 bytes Raw data 952 bytes Raw data 4096 bytes Raw data 3288...

I believe that NAND volume table offset was always speced in terms of erase blocks with 10 as common. That's 640 sectors with the usual 4k pages and 64 pages...

Thanks for those dumps. I looked at various code I had for UBI. One simple utility didn't presume at all where the volume table was. It simply watched out for...

What loader did you use? If you use some verbose command you can get the 532 bytes of extended CSD and we can see if your eMMC is healthy.