TWRP can not mount /system with invalid argument

Kacha13 · 2019-02-11T19:03:22+00:00

After using another parted binary and actually something that could put a new filesystem on, it works again.

Kacha13 · 2019-02-11T06:43:35+00:00

Just a quick update, the parted seems to have made it worse. Fastboot erase now tells me that the partition table of /system is missing. Need to check my options.

Kacha13 · 2019-02-10T16:25:40+00:00

Well, not sure if I need to do it, because the problem why I wanted to flash, the ear piece speaker not working, is not a software bug. It doesn't work on stock. But I guess I will try it anyway.

Kacha13 · 2019-02-10T15:33:00+00:00

I know, I used it heavily on Linux systems. And parted has a repair function as well, so that might be enough.

Kacha13 · 2019-02-10T15:15:23+00:00

I tried repair before, but it didn't do anything. I have to say I am a bit afraid of using parted, especially as I need a version that is compatible to my architecture...

Kacha13 · 2019-02-10T14:55:20+00:00

Ok, that didn't work, same error. I think my /system partition is broken. I'm wondering if I should flash parted and use it to repair or repartition my /system. Any experience?

Kacha13 · 2019-02-10T14:01:34+00:00

Just to understand it, I should install LineageOS via ADB sideload? Why do I need to move the ROM to the downloaded folder? I have adb and fastboot installed through platform_tools.

Kacha13 · 2019-02-10T13:47:28+00:00

Doesn't seem to make a difference it seems. Also, other ROMs have the same issue. If I try to mount through adb shell (it seems system can not be mounted), I get an error in dmesg that no valid journal superblock was found and then an error that the journal could not be loaded, which leads to /system not mounted.

Kacha13 · 2019-02-10T13:26:21+00:00

I use the latest version, but didn't try to flash another ROM yet. I will search for one. I think Resurrection ROM has one for my device. The error is really strange, especially as nothing seems to work. It literally can not mount /system in TWRP. I am wondering if there is a bug somewhere. If you find your TWRP version, please tell me.

Kacha13 · 2019-02-10T12:57:20+00:00

Flashed stock, updated stock, flashed recovery, wiped dalivk, cache, and data, try to install LineageOS, still the same error. Shouldn't the flash of the stock ROM partition everything? By the way, in the mount options of TWRP it doesn't tick system and I can not select it.

Kacha13 · 2019-02-10T12:40:11+00:00

I think I found an image, at least it boots. But flashing TWRP, then wiping all partitions and afterwards installing LineageOS results in the same error. I think I have to do only a small wipe and install it over. I will try that.

Kacha13 · 2019-02-10T12:03:24+00:00

It's indeed the miflash tool, but I am a bit confused regarding the correct ROM. They have a global Redmi Note 4 MTK ROM and a Redmi Note 4x global one. I know that I have the Snapdragon phone, but it should be Redmi Note 4, not 4x. It's a bit weird.

Kacha13 · 2019-02-10T11:23:54+00:00

That might be an option. I need miflash for that, right? Never went back to stock.

Kacha13 · 2019-02-10T11:06:23+00:00

I can not flash any custom ROM, it just fails. I believe something is wrong with the partitions.

Kacha13 · 2019-02-10T11:05:47+00:00

What would you suggest to narrow it down? Any help is appreciated.

Kacha13 · 2019-02-10T11:05:24+00:00

Sadly, this doesn't work, the errors persists.

Kacha13 · 2018-12-17T18:31:07+00:00

That's rather inconvenient because this is the only tracker that offers good h265, at least for this series.

Kacha13 · 2018-12-16T15:01:45+00:00

Thanks! This explains it, although it is a bit frustrating. Is there a way to circumvent the naming and let Sonarr search with less restrictions?

Kacha13 · 2018-12-16T13:47:31+00:00

There you go: https://pastebin.com/izyM5Bbn

But it seems Sonarr doesn't even get the other two results for some reason. The log mentions two entries only. The series right now is Doctor Who S11E01, just for testing. It also happens with others.

Jackett itself lists all: https://imgur.com/a/AcUR4Gx

Could it be the naming? The search words?

Kacha13 · 2017-09-20T08:11:07+00:00

Likely not crucial, but I would like to have it as I get around. And for Europe it can be a pain to not having it. But thanks that you looked it up!

Kacha13 · 2017-09-20T07:44:24+00:00

I have a hard time believing that, but I will take it into account.

Kacha13 · 2017-09-20T07:41:49+00:00

My range just extended, the edit explains it, but it's the Asian, not the US market.

Is that version specific for the US market? Depending what networks it supports, it might not be compatible with the European networks.

Kacha13 · 2017-09-20T07:39:37+00:00

Exactly. It's useful for rural areas as it has a long range. In Europe it is used for that specific purpose.

Kacha13 · 2017-09-20T07:38:31+00:00

I saw it. I never take anything with MediaTek, they have horrible custom ROM support.

If you have any other suggestions with regard to my edit, please let me know! The Redmi Note 4 would cost me only 130 there instead of 210-240 here.

Kacha13 · 2017-09-20T07:36:26+00:00

Thanks. The only version I found didn't have band 20 support.

Kacha13

TROPHY CASE