This kernel image is based on stock using the FreeXperia ramdisk method of loading stock and recovery. It also includes the new FOTA partition trick by Dees_Troy for easy updates in the future to TWRP.

Only this kernel (or other modded ones) has the logics implemented to load an external recovery from the FOTAkernel partition, right? Provided this is true, flashing another kernel or another ROM might overwrite this kernel and leaves the device without an accessible recovery, given the "new" kernel has no included recovery, correct?

Quote:

Originally Posted by lilstevie

If you open goomanager and in the menu select the option "Install OpenRecoveryScript" that should update the FOTAKernel partition with official TWRP.

So the TWRP build on goo, loadble via goomanager, gets loaded onto the FOTAkernel partition on our devices? This basically let's us update the recovery independently from the kernel? Awesome!

Quote:

Originally Posted by Notopic1

But keep ketting a grey triangle even after factory reset.
Also keep loosing recovery.

Me too, yesterday evening. Unfortunately this didn't work:

Quote:

Originally Posted by gregbradley

let it be, leave if for a while and let it reboot.

I kept losing the modified kernel and thus the device booted with the SONY logo instead of the FXP boot logo and then either bootlooped or hang at the triangle screen, not doing anything obvious or visible. All I did was flash the deodexed JB build via TWRP, AFAIK that has no kernel included so it should't touch the kernel.

Quote:

Originally Posted by Notopic1

But now the triangle is on for about 20 min and nothing is hapening.

Had the same problem. I reckon it's TWRP damaging partitions or so. Right before or while the device refused to go through with the boot and kept hanging at the triangle screen, TWRP would log errors related to mounting /sdcard and such. I reckon TWRP either damages the partition right away (no unmount, unclean unmount, ...) or causes something similar which appears when switching back and forth between CM and stock, permission problems on the internal storage. It seems wiping internal storage gets rid of the triangle and let's the device boot. Very inconvenient though, having to wipe /sdcard after doing a simple zip flash operation.
I replaced TWRP with your CWM by flashing the .zip provided by the OP. I'll see if I can provoke the triangle again, but later, I'm at work and don't have my flashing equipment at hand...

Quote:

Originally Posted by Notopic1

Volume Down button, when logo apears.

Volume-...? Entering the recovery is Volume+ on my device while the FXP bootlogo is displayed... Same as always since I got the device running a recovery.

Only this kernel (or other modded ones) has the logics implemented to load an external recovery from the FOTAkernel partition, right? Provided this is true, flashing another kernel or another ROM might overwrite this kernel and leaves the device without an accessible recovery, given the "new" kernel has no included recovery, correct?

No, once you flash another kernel, or rom that includes another kernel this is replaced with whatever the new kernel is using. At present this is the only JB stock kernel to use this trick, anything that has been based on freexperia work (AFAIK AKOP, Paranoid Android, and CM thus far) support the same trick. Most custom kernels include some form of recovery trick.

Quote:

Originally Posted by schaggo

So the TWRP build on goo, loadble via goomanager, gets loaded onto the FOTAkernel partition on our devices? This basically let's us update the recovery independently from the kernel? Awesome!

Yes, Dees_Troy designed the solution for this very reason.

Quote:

Originally Posted by schaggo

I kept losing the modified kernel and thus the device booted with the SONY logo instead of the FXP boot logo and then either bootlooped or hang at the triangle screen, not doing anything obvious or visible. All I did was flash the deodexed JB build via TWRP, AFAIK that has no kernel included so it should't touch the kernel.

It is pretty much guarenteed that the deodexed JB build you are flashing does include a kernel. There is quite simply no other possible way that you could lose the FXP boot logo.

Quote:

Originally Posted by schaggo

Had the same problem. I reckon it's TWRP damaging partitions or so. Right before or while the device refused to go through with the boot and kept hanging at the triangle screen, TWRP would log errors related to mounting /sdcard and such. I reckon TWRP either damages the partition right away (no unmount, unclean unmount, ...) or causes something similar which appears when switching back and forth between CM and stock, permission problems on the internal storage.

There were reports of this happening on the JB leak by doomlord himself, I don't believe it is related to twrp as the leak was running entirely stock at that time.

Quote:

Originally Posted by schaggo

Volume-...? Entering the recovery is Volume+ on my device while the FXP bootlogo is displayed... Same as always since I got the device running a recovery.

This is correct the script detects a volume-up keypress to enter recovery.

It is pretty much guarenteed that the deodexed JB build you are flashing does include a kernel. There is quite simply no other possible way that you could lose the FXP boot logo.

My suspicion as well. I'll try to reproduce it once I get home, can't afford to have a bootlooping device at work
Where does the logo come from btw? Is it already part of the kernel or part of the bootloader? That would imply you using a modified bootloader.
The following/later animation (colour swoosh) is part of the ROM, I know that.

My suspicion as well. I'll try to reproduce it once I get home, can't afford to have a bootlooping device at work
Where does the logo come from btw? Is it already part of the kernel or part of the bootloader? That would imply you using a modified bootloader.
The following/later animation (colour swoosh) is part of the ROM, I know that.

My suspicion as well. I'll try to reproduce it once I get home, can't afford to have a bootlooping device at work
Where does the logo come from btw? Is it already part of the kernel or part of the bootloader? That would imply you using a modified bootloader.
The following/later animation (colour swoosh) is part of the ROM, I know that.

I can confirm that the rooted deodexed JB does indeed contain the stock kernel. I did it for convenience for locked bootloaders and also for UB because at the time DooMLorD's kernel was the only one with recovery but didn't have Wi-Fi. I didn't know it screwed up TWRP, I'll re-upload the version without kernel and put this information in the OP

There is some bug in TWRP. After some research, I found that factory reset in TWRP causes problems. I needed to do factory reset and install my rom.After booting the rom, I restored some data and restarted.
I got the triangle running for a long time. So I hard restarted to twrp and tried to mount data and cache without luck. Even in the log, there was written that data and cache could not be mounted.
I did this whole process maybe 4 times and then installed CWM. Did factory reset, booted, restarted a few times, restored some data, restarted and there was no problem anymore.
Maybe something with make_ext4_fs? And I did not try to reinstall TWRP, maybe this would also help...

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer?