[KERNEL][L][STOCK][5.1.1]intersectRaven's Kernel - 20151018_20XX

[TimmyUK]

Followed all your steps and they all executed fine (format was successful, etc.) but TWRP refuses to mount /cache, even after a reboot. Doesn't appear under mounts, either.
And trying to boot the system, I get the boot animation for a good 20 minutes then gave up...
Changed it back to ext4 and it booted straight back up no issues...

Running the latest multi (not wifi.) kernel and v3.1 of the Urbane ROM.

Doesn't seem to like F2FS for me - nevermind!
Was only experimenting!

Try using adb shell whilst the watch is active rather than TWRP, I think I gave up on TWRP too for that very reason. Sorry my blurb wasn't specific, I was amazed I got it to work through experimentation

Edit:
Pretty sure I converted one without mounting either!

 

[intersectRaven]

Try using adb shell whilst the watch is active rather than TWRP, I think I gave up on TWRP too for that very reason. Sorry my blurb wasn't specific, I was amazed I got it to work through experimentation

Edit:
Pretty sure I converted one without mounting either!

TWRP doesn't support F2FS on our device so this is expected. First boot takes a while so be patient. Also, put it somewhere cold. [emoji14]

Sent from my MI 4i using Tapatalk

 

[jordirpz]

Please, can someone make a step by step guide for f2fs suport??

 

[bombadier]

Where is the changelog as I checked Github and cannot seem to find any development activity ?

 

[pablo11]

Thanks for the new kernel today @intersectRaven

 

[lion567]

TWRP doesn't support F2FS on our device so this is expected.

I've repacked "official" twrp-2.8.7.0-lenok.img with 20151015_15XX kernel (zImage). I've also put mkfs.f2fs in /sbin in ramdisk and changed this line in /etc/recovery.fstab (set filesystem type for /cache to auto)

/cache  auto  /dev/block/platform/msm_sdcc.1/by-name/cache

Thus after flashing this repacked image
twrp-2.8.7.0-lenok_f2fs_20151015_15.img
(SHA1: 0671ddcc194351a6b7ae2536a62a8f2dc2b5b412 ),
TWRP support mounting f2fs formatted /cache either from adb shell without parameters or from TWRP GUI.

BTW I've also changed [ro.build.fingerprint] in default.prop to stock value

ro.build.fingerprint=lge/lenok/lenok:5.1.1/LCA44B/2166028:user/release-keys

thus getprop("ro.build.fingerprint") check in next OTA update should succeded.

 

[Megaflop666]

I've repacked "official" twrp-2.8.7.0-lenok.img with 20151015_15XX kernel (zImage). I've also put mkfs.f2fs in /sbin in ramdisk and changed this line in /etc/recovery.fstab (set filesystem type for /cache to auto)

/cache  auto  /dev/block/platform/msm_sdcc.1/by-name/cache

Thus after flashing this repacked image
twrp-2.8.7.0-lenok_f2fs_20151015_15.img
(SHA1: 0671ddcc194351a6b7ae2536a62a8f2dc2b5b412 ),
TWRP support mounting f2fs formatted /cache either from adb shell without parameters or from TWRP GUI.

BTW I've also changed [ro.build.fingerprint] in default.prop to stock value

ro.build.fingerprint=lge/lenok/lenok:5.1.1/LCA44B/2166028:user/release-keys

thus getprop("ro.build.fingerprint") check in next OTA update should succeded.

works great and the twrp gui seems to fit the screen better now. Thank you.

 

[Rebel2k]

Flashed the latest 20151020 multi kernel and everything is OK so far! Thanks a lot!

 

[pablo11]

Thanks for the new kernel today @intersectRaven
What's new mate?

 

[Rebel2k]

Yes, thanks a lot. Can we flash safely?

 

[bombadier]

Yes, thanks a lot. Can we flash safely?

I have just flashed the dual.boot.img and watch has successfully booted

 

[pablo11]

I have just flashed the dual.boot.img and watch has successfully booted

Same here.

 

[Megaflop666]

Mine took off into orbit.

 

[jordirpz]

+1

 

[bombadier]

Something went wrong buddy if your watch ended up in orbit

Tapatyping fae the Bacon

 

[Rebel2k]

Yep, I flashed it too (multi for me) and everything is OK so far!

 

[starbase64]

Hi,

i also had these problems and here is my solution.

1. flash rom (via adb)
2. flash kernel (via adb)
3. flash stock recovery
4. factory reset in stock recovery

now boots up...

regards

starbase64

 

[pablo11]

Hi,

i also had these problems and here is my solution.

1. flash rom (via adb)
2. flash kernel (via adb)
3. flash stock recovery
4. factory reset in stock recovery

now boots up...

regards

starbase64

Hey @starbase64,
Long time no speak
What problem are you talking about? Ending up in orbit?

 

[starbase64]

@pablo11

boot loop after kernel flashing...

 

[pablo11]

@pablo11

boot loop after kernel flashing...

Oh, ok. I have never had this issue ....