nujackk said:

Another question, can we use custom kernel Whie locked? Using FKM.

You can use kernel managers, because they don't modify anything, just issue commands, but you can't replace kernel on a locked bootloader. Nor can you replace recovery.

Edit: More specifically: In my view, Franko's tweaks are outdated, no longer applicable to modern processors, and even when they were, degraded performance.

optimumpro said:

You can use kernel managers, because they don't modify anything, just issuing commands, but you can't replace kernel on a locked bootloader. Nor can you replace recovery.

OK Thanks

update is borked, Keeps failing at 47%

nujackk said:

update is borked, Keeps failing at 47%

What does it say? PC screen stopping at 47% is normal. You should read what your phone screen says.

Sorry, was getting phone working again. But on the phone it would say fail with error 7 twice and once said error 1 , only would say reading error in terminal.
I eventually got it to install via ROMInstaller. So I have it up and rnning at this point. Phone is hot but may just have been the extended boot time after the install. I let it settle and see how things are.
It may have just been me, If no one esle complains.

mine is failing at 47% phone says error appllying update: 7 {errorcode: : kInstalldevicesopenerror}
E:error in /sidelaod/package.zip {status 1}

Beard1020 said:

mine is failing at 47% phone says error appllying update: 7 {errorcode: : kInstalldevicesopenerror}
E:error in /sidelaod/package.zip {status 1}

Try with TWRP.

nujackk said:

Sorry, was getting phone working again. But on the phone it would say fail with error 7 twice and once said error 1 , only would say reading error in terminal.
I eventually got it to install via ROMInstaller. So I have it up and rnning at this point. Phone is hot but may just have been the extended boot time after the install. I let it settle and see how things are.
It may have just been me, If no one esle complains.

How's the latest update?

There could be 2 reasons for install error. Corrupt download from AFH, as when I was uploading, it took longer than usual; or increased system image size.

Increased system is highly unlikely, because recovery would have said so - something like 'image larger than actual partition size'. Also, you wouldn't be able to install with other methods, if size was an issue.

I'll probably end up re-uploading the rom.

optimumpro said:

How's the latest update?

There could be 2 reasons for install error. Corrupt download from AFH, as when I was uploading, it took longer than usual; or increased system image size.

Increased system is highly unlikely, because recovery would have said so - something like 'image larger than actual partition size'. Also, you wouldn't be able to install with other methods, if size was an issue.

I'll probably end up re-uploading the rom.

Click to expand...

Yeah took about 10mins on the initial boot.
Had to reinstall Gapps. But other then that so far so good. Haven't really been able to play with it much today. Getting work done in my attic

nujackk said:

Yeah took about 10mins on the initial boot.
Had to reinstall Gapps. But other then that so far so good. Haven't really been able to play with it much today. Getting work done in my attic

Have you tried larger Gapps?

optimumpro said:

Have you tried larger Gapps?

No just nikapps core, trying to stay as minimal as possible. Originally wanted to use microg but had problemsb getting nanodroid installed

nujackk said:

No just nikapps core, trying to stay as minimal as possible. Originally wanted to use microg but had problemsb getting nanodroid installed

Could you link that Rom installer you used?