[KERNEL][F8131/F8132] AndroPlusKernel v26

[sdugoten]

This happened with my z4 too and here's what i did:
Enter twrp -> wipe -> advance wipe -> select data -> repair or change file system -> repair file system.
Reboot and the problem solved.

I wonder if you do the repair file system, would that erase anything that I need to backup first? Thx

 

[tapppple]

I wonder if you do the repair file system, would that erase anything that I need to backup first? Thx

Nothing lost,but a backup is always recommended.

 

[pcyfff]

Thanks a lot!

 

[bluesky1126]

TWRP 3.1.1-0 dora Bug Report

The list of enabled ethernet driver is here (***=y is enabled one)
I only enabled drivers which was enabled on older Xperia's stock kernel.
https://github.com/AndroPlus-org/an...onfigs/diffconfig/common_diffconfig#L202-L222

Thanks a lot for your reply!!!

By the way, I've flashed the latest TWRP for dora from the official website today.
updating from 3.0.2-4, it boots up much faster and the Restore function is now working.
The only problem I met is that the touch screen freezes every time I enter it. I have to lock my screen and unlock it again to solve it. Well it's not a big problem, no need to fix it immidiately, just telling you that it occurs.

 

[deboopi2]

Since I cannot upgrade yet to 41.2.A.2.223 I upgraded my xp to 39.2.A.0.442 but then I have to use v22 of the kernel.
But when I start my phone I cannot see the orange dot anymore and I cannot get into twrp recovery.
So I went back to v21 of the kernel and then I see the orange dot but pressing volume up key makes my phone reboot.
I tried this with twrp 3.0.3 and 3.1.0 both with the same result.
Anybody an idea what's happening, since flashtool does not yet support 41.2.A.2.223 I cannot try that version in combination with the correct version of the kernel.
Btw, I used Sony's emma tool to install 39.2.A.0.442 but I think this should not make any difference.

 

[NiTeurmy]

Since I cannot upgrade yet to 41.2.A.2.223 I upgraded my xp to 39.2.A.0.442 but then I have to use v22 of the kernel.
But when I start my phone I cannot see the orange dot anymore and I cannot get into twrp recovery.
So I went back to v21 of the kernel and then I see the orange dot but pressing volume up key makes my phone reboot.
I tried this with twrp 3.0.3 and 3.1.0 both with the same result.
Anybody an idea what's happening, since flashtool does not yet support 41.2.A.2.223 I cannot try that version in combination with the correct version of the kernel.
Btw, I used Sony's emma tool to install 39.2.A.0.442 but I think this should not make any difference.

If you use the last version of flashtool and change te 39.fsc file to 41.fsc (Use a copy) you can upgrade to 41.2.a.2.223 with no problems (Multiple users did this).
The file can be found in: C:\Users"USERNAME"\.flashTool\devices\F81XX

BTW I use v25 of this kernel because v26 keeps restarting my phone.

 

[deboopi2]

If you use the last version of flashtool and change te 39.fsc file to 41.fsc (Use a copy) you can upgrade to 41.2.a.2.223 with no problems (Multiple users did this).
The file can be found in: C:\Users"USERNAME"\.flashTool\devices\F81XX

BTW I use v25 of this kernel because v26 keeps restarting my phone.

I already heard about copying the 39.fsc file and I created a bundle for 41.XXX with such a fle.
But when I flaash the created FTF file the process goes very quickly and in the end nothing is flashed.
There used to be a thread with a detailed explanation on how to use flashtool for flashing a rom for the x performance, this thread seems to be gone. It's been a while since I last used flashtool and I don't know what checkboxes to tick, so I didn't tick any of them (I included a printscreen from my flashtool) So maybe I have to select some checkboxes but I don't know what one(s). It is odd the flashing process went so quickly. This has happened before when I was using the version not adapted for nougat and I tried to flash a nougat rom but this was an error in flashtool itself later fixed by Androxyde with version 0.9.23.2.

So any advice on how to continue?

 

[Beetle84]

@deboopi2

open flashtool, select firmware to flash, then unzip and copy this to .flashtool/devices/F81XX and THEN click the flash button.

 

[deboopi2]

I already heard about copying the 39.fsc file and I created a bundle for 41.XXX with such a fle.
But when I flaash the created FTF file the process goes very quickly and in the end nothing is flashed.
There used to be a thread with a detailed explanation on how to use flashtool for flashing a rom for the x performance, this thread seems to be gone. It's been a while since I last used flashtool and I don't know what checkboxes to tick, so I didn't tick any of them (I included a printscreen from my flashtool) So maybe I have to select some checkboxes but I don't know what one(s). It is odd the flashing process went so quickly. This has happened before when I was using the version not adapted for nougat and I tried to flash a nougat rom but this was an error in flashtool itself later fixed by Androxyde with version 0.9.23.2.

So any advice on how to continue?

At least one problem is solved, I read the documentation on kernel v22 and now I know how to enter the recovery. Something you tell everybody else but don't do yourself

 

[Beetle84]

At least one problem is solved, I read the documentation on kernel v22 and now I know how to enter the recovery. Something you tell everybody else but don't do yourself

Did you try the .fsc file I uploaded? Its an XZ .fsc but is compatible with XP.

 

[deboopi2]

Did you try the .fsc file I uploaded? Its an XZ .fsc but is compatible with XP.

Do I need to build the ftf file with this file or do I need to build without fsc and then copy this file just before starting the flash?

 

[Beetle84]

Do I need to build the ftf file with this file or do I need to build without fsc and then copy this file just before starting the flash?

You dont need to build an .ftf everytime . If you have a 41.X ftf already, just load flashtool first and then copy the .fsc to the right folder, flashtool will delete it at every start. Good luck.

 

[deboopi2]

You dont need to build an .ftf everytime . If you have a 41.X ftf already, just load flashtool first and then copy the .fsc to the right folder, flashtool will delete it at every start. Good luck.

Finally it's ok, the default.fsc didn't help but recompiling the ftf file without a 41.ftf file and making sure the 41.ftf is in the devices library before flashing did the trick.

Thanks a lot

---------- Post added at 02:48 PM ---------- Previous post was at 02:27 PM ----------

Finally I could upgrade to Android rel 7.1.1.
Does the problem of kernel v22 remain? At least on my phone it does running v25 of the kernel.

NOTE: Keypress on boot is broken now. Please use official way (power down -> press power + volume minus -> when logo appears, release only power and hold volume minus)

 

[bluesky1126]

[/COLOR]Finally I could upgrade to Android rel 7.1.1.
Does the problem of kernel v22 remain? At least on my phone it does running v25 of the kernel.

NOTE: Keypress on boot is broken now. Please use official way (power down -> press power + volume minus -> when logo appears, release only power and hold volume minus)

I'm using v26 and I can boot into recovery either by using the official TWRP app or by (power down -> press power + vol minus -> when vibrates, I can just release both buttons)
I'm not sure what the "broken keypress" means.

 

[deboopi2]

I'm using v26 and I can boot into recovery either by using the official TWRP app or by (power down -> press power + vol minus -> when vibrates, I can just release both buttons)
I'm not sure what the "broken keypress" means.

The third option is that when booting an orange dot appears in the led next to the speaker, then you can press volume several times to get into twrp

 

[asiaon123]

Any updates supporting 41.2.A.7.8?

Any updates supporting 41.2.A.7.8?

 

[deboopi2]

Is it possible to set selinux kernel to permissive with this kernel?

 

[Araib93]

Is it possible to set selinux kernel to permissive with this kernel?

There is an amazing tool @AdrianDC made, you can check it out here. You can give it a shot, I'm sure it will work

 

[deboopi2]

There is an amazing tool @AdrianDC made, you can check it out here. You can give it a shot, I'm sure it will work

I tried a Selinux toggler app to set it to permissive. According to that app the kernel is already in permissive mode.
I need permissive mode to install the Viper4android driver but it still does not work, I still get the driver install failed: i/O error.
This should be caused by having the kernel not in permissive mode.

 

[Araib93]

I tried a Selinux toggler app to set it to permissive. According to that app the kernel is already in permissive mode.
I need permissive mode to install the Viper4android driver but it still does not work, I still get the driver install failed: i/O error.
This should be caused by having the kernel not in permissive mode.

selinux toggler app???
dude the link I shared is a flashable zip and works just fine, no app needed. Just flash that using TWRP and you are good to go, unlike apps which set kernel to permissive after boot, this zip makes kernel permissive on boot (not after boot... idk if it makes much sense, I am bad with words) JUST TRY IT !