mysql – InnoDB ibdata1 corrupted, innodb_force_recover does not work

I think I've checked all the messages on the internet.
Thing is my myqq (MariaDB) will not appear and, after many tests, I have seen it due to the InnoDB files.

I've tried with different innodb_force_recover and also with mysqld_safe, also with online tools and with every tut I've found.

I'm pretty desperate at this point, so any kind of help is welcome.

The record that matters is this:

2018-11-27 15:00:16 140309240685120 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to inherited due to the small size of the buffer pool. To use backspace, increase the buffers group to at least 20 MB

2018-11-27 15:00:16 140309240685120 [Note] InnoDB: use of mutual exclusion to ref count the pages of the buffers group
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: InnoDB memory heap is disabled
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Mutexes and rw_locks use GCC atomic components
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: GCC builtin __atomic_thread_fence () is used for the memory barrier
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: compressed tables use zlib 1.2.8
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using native Linux AIO
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using SSE crc32 instructions
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Initializing the group of buffers, size = 128.0M
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Complete initialization of the buffers group
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: The highest supported file format is Barracuda.
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: The registration sequence number 1154517884 in the ibdata file does not match the registration sequence number 1345427345 in the ib_log files!
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Restoring possible data pages half-written from the double-write buffer …
InnoDB: corruption of the directory of the page: infimum not indicated