yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] ZaneZam:
:) i'm just delivering this one:

hi [MENTION=4320310]JMS74[/MENTION],

yes i experienced the same problem on my OnePlus One COS13.1 system (last time just yesterday) .btw u have COS13.1 installed not CM13.1, right? *g*. the "problem" seems to be that supersu (for whatever reason) restores a backup of the previously used kernel (for me it was the previous boeffla version) and installes itself into this one again. u even can follow the steps in the install log in recovery. so now my method to get rid of the problem was to first flash the stock rom over again and then the new boeffla kernel version and finally then supersu = problem solved. i cant explain why that happens as had no time to investigate yet.
[ONE Original Android Development] SnOOpeRa:
Yeah , I had this problem too , its something from the supersu side install script , when flashed over restores backup of the last kernel used , in my case restores boeffla beta 1 when flashed beta 2 yesterday, i fixed it for me in that way --> extract boot.img from the s254 fastboot zip , then flash it in twrp , then flash boeffla and then supersu - works without problems. Kernel works perfectly and have the usb choose opion on connect ;)
[ONE Original Android Development] JMS74:
Yeah its COS13.1, not CM13.1, sorry for that.

Thanks will do that

Enviado do meu A0001 através de Tapatalk

---------- Post added at 12:05 PM ---------- Previous post was at 12:04 PM ----------

Thanks, that seems a great solution, but it's more piratical for me to just flash stock rom again.

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] andip71:
Hi all,

minor updates again for CM13 and COS13.1.

I decided to remove the zip signature from the flashable zip as it turns out to cause trouble for many recovery versions.

As it, at the same time, provides absolutely zero advantage (everone can unpack the zip, change content, zip and sign it again with the test keys out in the web - so there is anyway no security the zip was not touched since I released it), so why causing trouble for nothing...

COS13.1 -- Version

5.2-beta3

18.07.2015

Note: This kernel version runs best on COS13.1 firmware ZNH2KAS254

Change: Removed zip signature to be more compatible with certain recoveries

(do not forget to configure your recovery to bypass signature checks;

when flashing the kernel out of Boeffla-Config's TWRP screen, this is done automatically temporarily for Boeffla-Kernel zips)

Change: Build script improvements

CM13 -- Version 5.2-beta2

18.07.2016

Update: Updated with latest official CM kernel commits as of 18.07.16, 8am CET

Change: Removed zip signature to be more compatible with certain recoveries

(do not forget to configure your recovery to bypass signature checks;

when flashing the kernel out of Boeffla-Config's TWRP screen, this is done automatically temporarily for Boeffla-Kernel zips)

Change: Build script improvements

Enjoy

Andi
[ONE Original Android Development] GabrielSousa:
CM13.0 - Stable:	5.1 dont boot (bootloop) on recurrection rom... is just me ?
[ONE Original Android Development] andip71:
No, it is everyone who uses stable version on RR.

RR is not compatible with stable version. I think this has been mentioned already 20x in this thread.

RR is not 100% compatible to CM.

Use newest beta.

Andi
[ONE Original Android Development] GabrielSousa:
13.1 or 13.0 ?
[ONE Original Android Development] Crazy_Oni:
13.1 = COS

13 = CM

So what is your question? [emoji1]

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[ONE Original Android Development] kryshnakishore:
Use cm13 beta 2....it works well on RR ROM
[ONE Original Android Development] kryshnakishore:
1. Lord can u increase ac charging current to 2100mah, it charges in 90 minutes{ 0 - 100%}, I prefer default value only.but keeping an extra option t might be useful when we need

2. Option to hide tabs
[ONE Original Android Development] andip71:
To 1: it does not use 2100 based on my research

To 2: why that?

Andi
[ONE Original Android Development] DjDiabolik:
I have try to install the latest 5.2beta3 over 5.2beta1 on my OPO whit latest cos13.1.......... i have:

1) Upgrade config app to 2.3.5

2) Click on "Action"

3) Tap on "Load & Flash/store kernel"

4) Tap on "Test" button

5) Wait the download finish and tap "Yes"

At this point i see my OPO restart.... and load the TWRP........... the .zip it's correctly flashed....

I can see:

Installing zip file '/sdcard/boeffla-kernel-data/cm-kernel.zip'

Skipping MD5:no md5 file found

Flashing Boeffla-Kernel 5.2beta3-COS13.1-bacon-anykernel

I see the checking compatibility and below:

Installing kernel....

Installing over existing boeffla anykernel.......

Copyins modules....

And i can read:

Finished, please reboot.

After this i cann see and RED text says:

E:Unrecognized script command: 'Stop'

And again in write:

Setting 'tw_signed_zip_verify' to '0'

Done processing script file

MTP Enable

At this point i thinks i need to reflash the supersu zip right ? I have do this for reobtain the root access....... and i have restart my OPO...................

All it's completed.......... but on Config APP apparently the 5.2beta3 it's not installed........ i can continue to see i have again the 5.2beta1 installed........ it's normal ?
[ONE Original Android Development] andip71:
Supersu problem.

It sometimes restores an old kernel. Don't ask me why.

I don't use supersu on cos.

Apparently with supersu you need to flash manually. First cos stock kernel, then Boeffla, then supersu.

With internal superuser of cm instead supersu, this hassle is now required.

Andi
[ONE Original Android Development] DjDiabolik:
mmmmmmmmmmmmmmmm..... and you thinks you can fix this in future ?

Otherwise for moment i have to do the upgrade my kernel manually............

*EDIT*

I need to found the ZNH2KAS254 cos stock kernel first :)
[ONE Original Android Development] ZaneZam:
unlikely as this is a feature from supersu. i had some minutes during building unofficial stuff and found info's about the problem

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post67205573#post67205573

apparently its just a matter of the flash order. supersu installer restores to a "untouched" (previous backup) image if u try to flash

it on top of kernel with a already modified ramdisk so we should try to flash stock kernel->supersu->boeffla kernel ;)
[ONE Original Android Development] andip71:
No. This is how supersu works.

Yes, I don't like it too.

But I anyways don't use supersu on cos, but internal root.

However, I just have an idea... Have to look into it tomorrow. Maybe we can cheat supersu.

Andi
[ONE Original Android Development] DjDiabolik:
mmmmmmmmmmmm... i tryed to do this:

1) extract the boot.img from "cm-13.1-ZNH2KAS254-bacon-signed-9fbe6186fd.zip"

2) i have replaced the boot.img inside "Stock.Kernel.ZNH2KAS1KN.recovery.zip" with this newly extracted

3) Named this to "Stock.Kernel.ZNH2KAS254.recovery.zip" and i have copyed this on my OPO

4) I have also copyed on my OPO the "boeffla-kernel-5.2-beta3-COS13.1-bacon-anykernel.recovery" and the latest supersu zip files.

I have reboot my OPO on TWRP...... and i'm did:

1) Flash the stock kernel successfully

2) Flash the supersu zip whitout any error

3) Flash the 5.2beta3 boeffla zip

4) Reboot to system.........

When COS it's start........ i obtain an error from Config-app says to me my Phone has no root access............. at this point i have did this:

1) Restart to TWRP

2) Reflash the supersu zip for re-obtain the root access.

3) Reboot to system

When COS it's completely booted (and no error this time) i have launch the config-app but i continue to see the kernel it's in 5.2beta1 and not 5.2beta3 and root access it's correctly granted this time.

Strange or i'm commits some errors during flash operation ?
[ONE Original Android Development] anagramgenius:
You can flash the boot.img in TWRP itself and no need of a zip file. Delete this file if exists /data/stock_boot_.img.gz. (don't forget this step)

Flash stock boot.img=>boeffla kernel=>supersu
[ONE Original Android Development] kryshnakishore:
I am RR ROM, dnt mind check his kernal, it goes upto 2100 mah which is quite speed in charging. When I set 2000 on ur kernal it's taking 3hrs to full charge. But on RR kernal setting 2100 makes 90mins to full charge

2.in kernal config app tabs to hide like overview, Governor, cpu.......
[ONE Original Android Development] chenrp:
Check your calculations again. You must be mistaken.

I do think we can check max charging current again!
[ONE Original Android Development] kryshnakishore:
That's OK I am not at all worried. Hiding tabs in config-app is sensible
[ONE Original Android Development] andip71:
First flash Stock kernel, then Boeffla, then supersu.

Not how you did it.

If you insist on supersu still, although it is not my recommendation.

I will try something out today. I might be able to achieve you don't have to flash supersu again after a kernel update then...

Then the update would b just as simple as flashing the new kernel and that's it.

Andi
[ONE Original Android Development] andip71:
Sorry to be reluctant. But as much as I don't like a custom rom as much I am not taking anything from a custom roms kernel.

If torturing the battery is what is most important for you, I recommend you use RR kernel. I am more interested to ensure battery life span is long than pushing the charge times to a minimum. Especially as the battery is not exchangeable. Safety first is what I prefer.

Apart from the fact I have doubts on your figures, a 100 mA increase cannot half loading times.

Andi
[ONE Original Android Development] kryshnakishore:
I just used RR as reference, Idk much about kernal coding but I used to get 90min full charge with that kernal. Yes I dnt give workload to my phone, just thought to have that in case of needy. That's OK I will stick with boeffla-kernel.
[ONE Original Android Development] Klobal:
See the attached picture showing the charging current and time with boeffla kernel (stock charging settings).
[ONE Original Android Development] kryshnakishore:
Great thank u.. I will never point 2100 again & I dnt need 2100 on daily usuage

Only for u : install RR ROM, set charging current to 2100 in kernal auditor & report me
[ONE Original Android Development] andip71:
COS-Guys,

I have great news.

My idea from yesterday seems to work. This means, if you insist of using still SuperSu for rooting COS, it will be very simple in future to do kernel updates.

Currently you have to do:

- flash stock kernel again

- flash new boeffla

- flash supersu

Any other sequence would trigger SuperSu (stupidly) to restore back the older kernel.

In future, when you just want to upgrade Boeffla, you do:

- flash boeffla -> done

SuperSu should then still work without the need of reflashing it again.

I am currently doing some extensive testing, if all goes well I will release beta4 which has this trick built in already.

Fingers crossed

Andi
[ONE Original Android Development] andip71:
COS13.1 kernel update is out!

From this version onwards, updating Boeffla-Kernel to a new version is much simpler when you are using supersu already.

The way of flashing COS13.1 stock kernel, then boeffla, then supersu is not required anymore. Just flash the new Boeffla kernel beta and you are done.

Please see change log below.

And if you are on (what I recommend heavily) internal CM superuser, all remains as before. Also just flash Boeffla kernel over and you are good.

In short this also means: You can use load&flash functionality fully again to update the COS kernel, regardless of your root method.

Version

5.2-beta4

19.07.2015

Note: This kernel version runs best on COS13.1 firmware ZNH2KAS254

Change: Improved compatibility to SuperSu

This change addresses a design flaw in latest SuperSu versions, which restore an older kernel when flashed on an existing custom kernel again.

Now it is very simple - when you are on Boeffla-Kernel with SuperSu as root solution already - just flash the new Boeffla-Kernel version over and that's it.

You do not have to flash SuperSu after a Boeffla-Kernel upgrade anymore, as the kernel installer leaves SuperSu intact now by a trick.

Enjoy

Andi
[ONE Original Android Development] DjDiabolik:
Testing immediatelly on my opo......wait some minutes and i can give some feedback :)
[ONE Original Android Development] suaverc118:
Go into privacy settings and see if you have start at boot off. If you do, then that will happen
[ONE Original Android Development] DjDiabolik:
OOOOHHH YEAHH :) Great work [MENTION=947981]Lord Boeffla[/MENTION] the 5.2beta4 working and it's been flashed whitout any problems directly from config app (the script executed on TWRP it's fantastic) !

I have immediatelly reboot whitout re-flash the supersu zip and YEAH! Roots access it's been still whitout any problems...................

If it's possible you can add a command on script for restart automatically to System after flash complete ? For example add a pause of 5 seconds after flash complete and after that from twrp reboot directly to system..........
[ONE Original Android Development] andip71:
I do not understand...

My phone automatically boots after the flash in recovery. It never stops?!?

How exactly did you flash, by load&flash or via the TWRP screen? (if via TWRP screen, make sure you have not checked the checkbox preventing a restart)

Andi
[ONE Original Android Development] DjDiabolik:
Wait. I know that I explained bad what i did exactly :)

Via Load&Flash..... i did:

1) Tap on "Test" Button

2) After download tap on "YES"

At this point my OPO it's been restart and i can see the twrp started and flashing the 5.2beta4 correctly. At this point the twrp it's back to main menu (and i have reboot to system manually).

It's some option on twrp for enable the autoreboot ?

*EDIT*

Ah i use the twrp 3.0.2-3 tugapower....not the official but i thinks it's irrilevant right ?
[ONE Original Android Development] andip71:
I dont know the tugapower recovery. I am using official latest recovery.

And here after flashing the kernel, exactly as you said, reboots into the system after it.

That is pretty much all I can say. Maybe in tugapower the openrecoveryscript handling is changed, dunno. You would need to do a test with official TWRP.

Andi
[ONE Original Android Development] Grobie13:
No problem here with Tugapower recovery, it reboots after flashing as it should.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
This is good to know. Well, maybe then there is a configuration option in that recovery to ask not to restart? I have no idea, just thoughts.

Andi
[ONE Original Android Development] DjDiabolik:
Otherwise it's not a big problems :). Indeed, it's not a problems because i need only to restart manually :)

The important things it's the flash operation successfully whitout any problems and root still whitout any problems... thanks for found this ways :)

Otherwise i use the tugapower recovery because whit that it's possible to backup the EFS partition.....and because whit that and whit ever older version like 2.8.x it's alway possible to flash the modem instead the official release :)

mmmmmmmmmmm... i thinks at this point i need to activate some feature on my twrp :) If you have some idea what every suggestion it's be accepted :)
[ONE Original Android Development] Renosh:
Once you flash Boeffla kernel your EFS partition is backed up in the sdcard. Just go to Boeffla folder on your phone. It's nice having that feature in a recovery but its not necessary to do a backup everytime. Just copy a copy of your EFS to your PC and maybe to your Google Drive folder and forget about it
[ONE Original Android Development] chenrp:
Any way of increasing the LED brightness?
[ONE Original Android Development] Promez:
Hey guys someone tried the kernel on Dirty unicorns?

Thanks!

EDIT: So far is working great! :D going to test
[ONE Original Android Development] andip71:
Cannot be made brighter anymore. This is already the maximum possible without burning the led.

Andi
[ONE Original Android Development] chenrp:
thanks.

i wonder why...
[ONE Original Android Development] andip71:
What do you wonder?

The LED can only be driven up to a specific voltage. Anything more would kill it.

This is very normal for electronic parts.

Andi
[ONE Original Android Development] chenrp:
i am electrical engineer.

do you have the specification of the LED and the voltage the kernel delivers?
[ONE Original Android Development] atulclassic:
prior to MM update LED was much more brighter when used as a flashlight but nowadays its brightness has reduced almost 30-40%..so there must be some issue or commit for that
[ONE Original Android Development] andip71:
I dont have the specification, I could look the voltage it up in the kernel drivers.

But I have no time for that these days + I would anyways not increase the voltage for safety reasons.

Not on my side, LED is not darker or brighter than before with COS13.1.

Andi
[ONE Original Android Development] hellcat50:
i know you can increase the led via simple build.prop editing, but would not recommended it because the led gets hot after 1 minute while with normal settings you can easily use it +10 minutes without heat
[ONE Original Android Development] DjDiabolik:
Great info......i try to remember that next time i need to make a nandroid :)
[ONE Original Android Development] kryshnakishore:
I did not get it. Can u explain again. What does EFS.tar.gz do?
[ONE Original Android Development] andip71:
It is a copy of your EFS partition, i.e. the partition where your IMEI information etc. is stored.

When you lose that partition, your phone is an unrecoverable brick (although there are voices saying, EFS partition backup is not required on Qualcomm devices, but I am not sure myself).

Andi
[ONE Original Android Development] Renosh:
Its a zip file that has the modem (2 files) you'll need to flash to restore your EFS if anything happens, like if you lose your IMEI randomly. It's happened to me once that I restored a TWRP backup and lost my IMEI number.
[ONE Original Android Development] kryshnakishore:
Oh got it, thank u for sharing valuable info
[ONE Original Android Development] Renosh:
I wouldn't say unrecoverable considering I lost my IMEI on this phone without a backup but still recovered it. There's a guide in great guide in general section.

I also lost the IMEI for my girlfriend's Note 2 when I Odin flashed some firmware. Had to use some commands to get it out of some test mode and took it to some guy that gave me a random IMEI (illegal) and its working perfectly now.

Phones were completely unusable without IMEI though. Either wouldn't go past boot logo or bootlooped constantly with no phone functions available.
[ONE Original Android Development] hellcat50:
- message deleted because off-topic :) -
[ONE Original Android Development] Renosh:
Normally its to stop blacklisted phones by carriers (lost/stolen and reported) from being used and can land you a couple years in jail.

This depends on each country's individual laws of course, but I know it's illegal in my country.

People that have committed a crime can also be tracked using the IMEI of a handset if it's not blocked and they use your/their phone and this serial number is known by authorities.

Changing the IMEI circumvents these checks that could be done to frustrate and find thieves and other unscrupulous individuals, so laws were changed to make it illegal to reprogram the IMEI.
[ONE Original Android Development] hellcat50:
ok, thanks for the answer :good:
[ONE Original Android Development] dxlevel81:
Hi. Im trying to install this on cos13.1 full rom rooted from another thread but when i flashed the root access is gone. And when i flash super su now boeffla kernel is gone. Any help?
[ONE Original Android Development] andip71:
It was explained many times already:

When you use supersu (which I do not recommend on COS):

- Flash COS13.1 stock kernel

- Flash Boeffla

- Flash supersu

- Done.

When you use internal CM root:

- Flash COS13.1 stock kernel

- Flash Boeffla

- Flash internal superuser enabler script I provide

- Done.

For updating Boeffla-Kernel to a new version, only flash Boeffla, nothing else, no supersu which is stupid enough to restore previous kernels in this case.

Andi
[ONE Original Android Development] shamru:
Hi dxleve181, I have the same issue, did you able to solve it. I did exactly what is mentioned by Lord Boeffla still the issue is same
[ONE Original Android Development] BlazeGarden:
I'm also having the same issue even when following the boeffla instructions. I think it started happening with 5.2Beta4. Before it was working fine with 5.1. Will install that one and report back.
[ONE Original Android Development] BlazeGarden:
I'm still having the issue with 5.1 probably something changed with the latest CM13 nightly 07/29 which is causing this behavior.
[ONE Original Android Development] andip71:
Then I would have it as well.

But all is fine here.

Why do you guys not follow my recommendataion and dump supersu on CM and COS roms? I never have trouble with internal superuser.

Andi
[ONE Original Android Development] BlazeGarden:
I didn't know it was a recommendation not to use SuperSU? As you left instructions on how to install it. But if best practice is to use built in then this is noted. Definitely something is causing the difference between our installation. Was just trying to find out what. Will keep tinkering around perhaps I will find what's causing it and report back.
[ONE Original Android Development] andip71:
Well, it is my personal recommendation, not a general one.

But I figured out, I am running CM and COS better with internal superuser than supersu (which causes lots of troubles over and over again since Android MM).

But it is also a matter of taste, as internal superuser displays a hash when an app runs with elevated user rights. Which is something a few people get annoyed about.

And yeah, I keep on recommending that again and again in all my kernel threads (apart from Samsung Stock and OOS, where you clearly need supersu).

Andi
[ONE Original Android Development] MMWolverine:
Well imo, it certainly comes down to personal taste or better yet, depends on the type of user. I followed your advice and tried the internal su on a cleanly installed COS. Starting with the hash in statusbar (which annoys me a lot just to disable it with an extra Xposed mod), I've never seen any noticeable advantages over chainfire's SU. Phone was equally stable, only good thing was an easier updating of your kernel. But I never had problems re-flashing SuperSU and now that you've brilliantly bridged that obstacle, things are even smoother.

I mentioned "type of user", because there are a few things that depend solely on SuperSU, like systemless Xposed (which will apparently bypass SafetyNet and make Android Pay finally work). Also after flashing A.R.I.S.E. Sound System you can get the "internal memory problem" popup with internal su. Those are just some examples, if you can live without them, follow Andi's advice. ;)
[ONE Original Android Development] lammpat:
I always wanted to use internal super user, but in stock COS 13.1 I cant find it in developer options...is it there? :eek:
[ONE Original Android Development] Renosh:
Go to Boeffla's site and go to test kernel download. He's provided a zip in that folder to enable internal superuser
[ONE Original Android Development] aojc1992:
Sorry to ask an outdated question, but I can't find info regarding it.

For CM11S + boeffla kernel, is there a function to set backlight keys (Touch key LED settings) on hardware key touch instead of screen touch like CM12.1 / CM13? In the app the option to do so is not there
[ONE Original Android Development] Pablo.x:
Available under screen options on boeffla config, at the end of the page.

Enviado desde mi OnePlus One.
[ONE Original Android Development] hellcat50:
since this kernel went anykernel, i can now use this kernel on almost all rom's. this feels so :good: great work andi
[ONE Original Android Development] aojc1992:
It doesnt have under CM11S, I double checked. Pls dont give inaccurate replies if youre not sure. Tq.