yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] frikakwa:
Working fine on OP3 with 4.0.1... Still long for reaching TWRP menu but... Working fine.

Thanks for your support mate.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Go ask OnePlus for N source so people can improve stuff.

It's faster but it will alwys use more time than ext4 based crypt.

ROMs also take a little more time to boot on f2fs because of file check and so on.
[OnePlus 3 & 3T Cross Device Development] gillim74:
Yeah my bad bro after i wrote that i realized it was for mm roms.ill just use yarplin for now till you are abke to beast out a n one.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r27 unified

All right crew!

New build is up. Wicked!

I added latest f2fs upstream, all is fine for me but use with caution.

Also added a couple general and security fixes. Hopefully this will be the last MM build before N.

Keep in mind: I will give no active support for custom ROMs or OB. Meaning, if using anything besides stable OOS don't bother posting about it.

I am only interested on debugging stuff in stable OOS (with logs and reproducible steps to replicate the issue).

Don't spam this thread with CM or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.

Also don't go spam and bug reporting on ROM threads if using this.

If you like my work, donations are always welcome (but not mandatory).

Don't forget to hit thanks, it's free ;)
[OnePlus 3 & 3T Cross Device Development] humzaahmed155:
Just to be precise, this is the same case for Magisk users too, right?
[OnePlus 3 & 3T Cross Device Development] Prattham:
I'm on twrp . 28 but it happened on . 23 as well

I'm on stock oos 3.2.8 and when i backup it via twrp then flash some roms and restore my backup when i reboot my system ui does not work properly everytime i restore

Like status bar remains hidden buttons don't work except home button and like that

Doesn't matter what rom i backup either be stock rom or cm based or oos based

Happens the same

Any idea?
[OnePlus 3 & 3T Cross Device Development] Chabola:
+1

Happened to me last night after I flashed the latest

kernel
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Thanks for the update brother. Still no support for ext4 storage on N oos I presume? It's not a request post, I understand you won't provide support or work for ext4 bugs.
[OnePlus 3 & 3T Cross Device Development] tsoureki:
I flashed latest recovery v12 and now i can't flash anything (update process error 7).

Furthermore, i can't flash any other recovery (doesn't boot)

Any help?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Fastboot is your friend
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nothing to do with kernel or recovery.
[OnePlus 3 & 3T Cross Device Development] tsoureki:
I have Oneplus 3. After flash twrp v12 everytime i want to flash a file it gives me error "error installing zip file, this package is for device Oneplus 3. Your device is Oneplus 3t"!! :crying:
[OnePlus 3 & 3T Cross Device Development] gigatex:
Same here
[OnePlus 3 & 3T Cross Device Development] Dieppy:
No issue here
[OnePlus 3 & 3T Cross Device Development] habylab:
Thank you for the new TWRP.

Last root based question: has anyone had luck just flashing back to he latest stable version? I see people in the SuperSu thread saying they've had issues.
[OnePlus 3 & 3T Cross Device Development] tsoureki:
Here is a screenshot of my issue with twrp v12. Can't flash anything. Not recognize my device.. :(
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
check the zip file you are flashing why are there 2. zip extensions? correct that and try again.
[OnePlus 3 & 3T Cross Device Development] jocaboss:
Worked perfectly for me. OOS 4.0 over OB10 with twrp v11 by eng.stk
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You can start by using the correct recovery I linked on the v12 release post, which is on this thread downloads.

You 're probably flashing the one from 3T thread.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Guys I'm pulling r27 and twrp v12.

I encountered a couple data corruption situations, specially a rather troublesome one (for some people that want to use a lower revision of f2fs, let's say in stock kernel).

I will be keeping the f2fs present on OOS until further notice.

I recommend you backup your working system and put it on PC, USB or similar.
[OnePlus 3 & 3T Cross Device Development] mysky911:
i am using r27 and twrp v12 on OOS 3.2.8. Should we reflash to twrp v11 and r25?

[MENTION=3873953]eng.stk[/MENTION] Can I ask a stupid question here? Do we need to format Data partition with latest version of f2fs if our Kernel/Recovery upgraded to newer versions of f2fs?:confused:
[OnePlus 3 & 3T Cross Device Development] habylab:
Yeah I'd like to know this too.
[OnePlus 3 & 3T Cross Device Development] immi803:
[MENTION=3873953]eng.stk[/MENTION]

As you gonna pull back r27 and v12, reverted back to r25 cause stuck and emergency reboot happens, tried every way to work again r25 but had to revert to r27 to make phone functional, ooo3.2.8

Any help would be appreciated
[OnePlus 3 & 3T Cross Device Development] CroW_D:
So now i have a problem i was on the latest twrp release from you (v12) flashed a new update from my rom and it boots up fine but then freeze on the welcome screen, i flashed back then the older twrp release from you (v11) and now everytime i try to boot to recovery i got a black screen and my pc say QHUSB_BULK as device. I have accses to fastboot so what should i do now i have no running system installed and my backups are all gone. Please help someone !

All fixed now :)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I recommend backup to pc and format partition before going to r25

Don't use twrp v12.
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
I flashed v12 recovery before it was pulled. I attempted to reflash v11 and it will not boot into the recovery. I see the splash screen but then black screen and the LED come on white. Then I'm forced to reboot. I attempted to flash v11 with v12 first then I fast booted it. Any ideas or help?
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Did you try fastboot erase recovery and then flashing v11?

Let us know if this works, I need to revert back too.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I just flashed via twrp and worked normal.

But you need to erase(format) your data before reboot (if using f2fs, ext4 not affected). So backup before.

THat's probably recovery panic becaus eof th ef2fs upstream stuff.
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
I am on f2fs. So I need to format data and re fastboot recovery v11 to be back in business? I can't access recovery though.
[OnePlus 3 & 3T Cross Device Development] tsoureki:
Same here. I am on v12, flash v11, format data, but not boot to recovery.. :(
[OnePlus 3 & 3T Cross Device Development] theduke7:
Read the warning late I guess, I used v11 and it had miner slow issue , v12 made the internal storage unusable ,

For this shaving issues, flashing another version from TWRP itself won't work and will cause issues and loops, fastboot instead, I fastbooted .28 and all works will

---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------

Fastboot .28
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
Link? Also, would I be OK using this with f2fs system?
[OnePlus 3 & 3T Cross Device Development] tsoureki:
28 just not boot. The only recovery that boot is v12. Nothing else..
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
28 wouldn't boot for me either. Anyone have a copy of v12 do I can have a functioning recovery again?
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Wut? We need to completely erase the phone cause recovery? I got it right?
[OnePlus 3 & 3T Cross Device Development] theduke7:
v12 is the problem 28 boots fine and it used to boot before both v11 and v12, make sure you fastboot it not flash it from within old TWRP.

boot to recovery itself 1st then wipe internal storage... (and check if your data is decrypted and f2fs, if not make it so) then reboot to system...worked for me the 1st time with no issues,

Here's a link to 28
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
Yeah I found 28 and flashed via flashify. I get TWRP splash and then blackness with white LED. Nothing more. I also attempted to fastboot. Unencrypted f2fs data partition.
[OnePlus 3 & 3T Cross Device Development] theduke7:
flashify is like flashing from twrp it wont work, but if you also tried fastboot and didn't work so your best pet is to fastboot stock recovery first (or erase recovery from fastboot) then fastboot 28 again... for me as i said worked when v11 failed ...i wonder why it causes such an issue flashing over it
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
I will have another go at it right now. Thanks. Yeah, not sure what the issue is. Hope someone is able to get to the bottom of it.
[OnePlus 3 & 3T Cross Device Development] jocaboss:
What is the real problem with twrp v12? It's working normally for me
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
Could someone PM me a link to v12. I just want to see if it works. Really dislike not having a working recovery.
[OnePlus 3 & 3T Cross Device Development] jocaboss:
Sorry
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
Thank you so much! This booted up without a problem. I tried every other recovery and method of flashing every recovery. This is all that worked. Not sure why.
[OnePlus 3 & 3T Cross Device Development] habylab:
Wait, can this be fixed? Or are all of us on v12 of TWRP going to need to wipe data using v11?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
No mirrors allowed! Respect the dev ;)
[OnePlus 3 & 3T Cross Device Development] jocaboss:
Sorry! I didn't know that! Mirror removed!
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Perhaps to fully disable the link on Dropbox would be the best course of action... Just a heads up.
[OnePlus 3 & 3T Cross Device Development] kipue:
I'm not 100% sure, but I think people with probs have a mix of f2fs file system+encrypted storage.

If you don't use f2fs, it does not matter.

Anyone else can confirm?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
So much confusion goes here, just read people.

r27 had the f2fs 4.10 backports, which I didn't found completly stable. So I reverted them.

Even worse, it will render broken any lower f2fs revision (like in previous -and next - blu_spark, other custom kernels and stock), resulting in all kind of data corruption and so on.

I got it because I use stock kernel to compare and trouble shoot stuff sometimes.

And makes no sense to me having something not retro compatible with stock kernel to gain pretty much nothing.

So be aware, if you use recoverys/ROMs with kernels with this on, you will encounter this situation in the future probably.

You guys with TWRP v12 don't have any issue with data on stock ROM OOS 4/4.0.1?

That would be a first to me, since I could replicate it in OOS 4, OOS 3.5 and OOS 3.2.8.

The twrp v12 was taken down also because it also has the said f2fs changes. For going to other twrp you can use fastboot as any other recovery ( you may need to format data in fastboot also to get it to boot).

Don't clutter the thread with unnecessary stuff.
[OnePlus 3 & 3T Cross Device Development] jocaboss:
Done

---------- Post added at 02:37 PM ---------- Previous post was at 02:35 PM ----------

I'm with twrp v12 with f2fs data but not encrypted and no problem to me at this time. I've made a backup yesterday and flashed 1 mod and worked good.
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
Please delete
[OnePlus 3 & 3T Cross Device Development] fapste:
[MENTION=3873953]eng.stk[/MENTION] can you port EAS to your kernel? Is it difficult to port it?
[OnePlus 3 & 3T Cross Device Development] habylab:
Thanks for the update.

To put it simply: I am on 4.0.1, with v12 of your TWRP. Am I safe to flash v11 or another recovery, or do I have to wipe data?

I see you say it will render lower revisions corrupt, but I haven't had that, and I am not experiencing any issues.
[OnePlus 3 & 3T Cross Device Development] nmlssit:
I have no issues too, but people are experiencing bootloops in simply reverting to another version of twrp. Do what eng.stk wrote and format data in fastboot.
[OnePlus 3 & 3T Cross Device Development] xanthrax:
[MENTION=5285184]LELBOT[/MENTION]

the supersu link contains adware, please remove it or fix it ASAP
[OnePlus 3 & 3T Cross Device Development] habylab:
Ah brilliant. I can't see how TWRP can cause issues to the data partition if I haven't formatted data with it. But maybe that's my lack of information.

It's a shame it has come to another clean wipe. I may backup my phone, wait another revision of OOS and for sources, see if the issue is fixed.
[OnePlus 3 & 3T Cross Device Development] jocaboss:
Guys just flash the last 3.0.3 oficial twrp from today
[OnePlus 3 & 3T Cross Device Development] marf28101995:
This thread is for kernel development related post and not for TWRP discussion like the dev said so many times ! Move on guys links is removed they just have to read now.

Back on topic
[OnePlus 3 & 3T Cross Device Development] LELBOT:
New guide updated

Links Updated

NEW GUIDE UPDATED - https://xdaforums.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757 ( By - [MENTION=7974614]dbabaev21[/MENTION] )

Also new official twrp has been updated for f2fs and decryption probs, so time for update.

Sorry for the offtopic.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Already been discussed mate.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r28 hybrid

All right crew!

New build is up. Wicked!

Hopefully this will be the really really the last MM build before N.

Keep in mind if you're on F2fS and flashed blu_spark r27 and/or TWRP v12, you probably will encounter data corruption and trouble booting up when upgrading.

If this the case, backup your stuff to PC and format your data partition.

Keep in mind: I will give no active support for custom ROMs or OB. Meaning, if using anything besides stable OOS don't bother posting about it.

I am only interested on debugging stuff in stable OOS (with logs and reproducible steps to replicate the issue).

Don't spam this thread with CM or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.

Also don't go spam and bug reporting on ROM threads if using this.

Here's an updated TWRP blu_spark v14 with all the blu_spark goodies inside:

No support will be given, if your cat get's on fire you're on your own.

Also don't clutter the kernel thread, just sharing, not really after any feedback.

Go get it: https://xdaforums.com/devdb/project/dl/?id=22667

If you like my work, donations are always welcome (but not mandatory).

Don't forget to hit thanks, it's free ;)
[OnePlus 3 & 3T Cross Device Development] cdonald:
[MENTION=3873953]eng.stk[/MENTION] Just curious, will your v14 TWRP list the build product as "OnePlus3" and not "oneplus3", as the official TWRP does? It causes error 7 when flashing Roms based on OOS that are looking for the former, but TWRP lists it as the latter. Or, at least, that's how I understand what's happening.

Sent from my ONEPLUS A3000
[OnePlus 3 & 3T Cross Device Development] eng.stk:
OOS ROMs check for ro.display.series=OnePlus 3 & ro.build.product=OnePlus3 so mine is fine.

What ROM are you using?
[OnePlus 3 & 3T Cross Device Development] cdonald:
I'm on FreedomOS 2.1.1, which is basically just OOS 4.0.1 with some extras. The ROM installs fine on your recovery and I only get the error code 7 when I'm on the "official" TWRP. It seems the official version has the build.product listed as "oneplus3", causing the install to fail.

In any case, thanks for the new recovery. Seems to be working great so far.

Sent from my ONEPLUS A3000
[OnePlus 3 & 3T Cross Device Development] Chris.nl:
Thnx! I've successfully used TWRP blu_spark v14 to dirtyflash 4.0.1 -> 4.0.2. :good:
[OnePlus 3 & 3T Cross Device Development] Berlino:
[MENTION=3873953]eng.stk[/MENTION]

Thanks for updating so quick...dash is now working on OOS latest build with your great kernel.
[OnePlus 3 & 3T Cross Device Development] k1ngp1n.:
I'm currently on 3.2.2 stock no root!

What steps to follow to get this kernel

working ?
[OnePlus 3 & 3T Cross Device Development] Berlino:
Well at first you'll need to unlock your bootloader and fastboot flash one of the twrp recoveries, then flash SuperSU in twrp and blu_spark r73 for OOS.
[OnePlus 3 & 3T Cross Device Development] k1ngp1n.:
TY!
[OnePlus 3 & 3T Cross Device Development] proag:
He doesn't need to flash SuperSu.
[OnePlus 3 & 3T Cross Device Development] ebautista:
Is Dash working in custom rom also?
[OnePlus 3 & 3T Cross Device Development] Berlino:
Yep, you're right...no need for SuperSU/root, but for me it is essential. :)
[OnePlus 3 & 3T Cross Device Development] Flamehell:
[MENTION=3873953]eng.stk[/MENTION] Bro,this last build is amazing...my phone is flying...tnx!
[OnePlus 3 & 3T Cross Device Development] k1ngp1n.:
With this Custom Kernel no SuperSU I'll get OTA ?
[OnePlus 3 & 3T Cross Device Development] madsponge26:
Dash Charge?!

Brooom!

Kernel Updated..

Fast..
[OnePlus 3 & 3T Cross Device Development] Roulianooo:
So for those who have updated , whisch Rom do you have and is Dash working ? :)
[OnePlus 3 & 3T Cross Device Development] Rossyyy:
Does this kernel mean dash will work with CM?
[OnePlus 3 & 3T Cross Device Development] Neuz:
+1

Tapatalked from my OP3.
[OnePlus 3 & 3T Cross Device Development] lammpat:
thread title clearly says OSS 3.2.x but to be double sure...I am on stock oxygenos 3.2.2(unlocked bootloader and rooted)... can I flash this kernel without any extra steps or do I need to flash ROM>KERNEL>SU as mentioned by the OP? Thanks in Advance :)
[OnePlus 3 & 3T Cross Device Development] tofuboi01:
If you are stock and rooted already then flash the kernel zip, but if you have another kernel flashed on your OOS, then flash rom first then SuperSU and kernel.

Make a backup of your boot and system (or even full backup) in TWRP if you want to return to stock.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Kernel support is all merged.

If the custom ROM have the DASH binaries should work.

If you're stock rooted just flash the OOS blu_spark zip
[OnePlus 3 & 3T Cross Device Development] lammpat:
Hey [MENTION=3873953]eng.stk[/MENTION] great to hear from you directly...honored... thank you very much! :)
[OnePlus 3 & 3T Cross Device Development] liver20:
Then, if i flash last nightly 28 July with your Kernel, have i DASH CHARGING working ?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Kernel wise it's all done.

There's no if, don't bring ROM stuff to my thread please.

Go ask on your ROM thread about ROM questions.

No prob, here to help... sometimes ;p
[OnePlus 3 & 3T Cross Device Development] IlD4nX:
I have a strange issue with sRGB: with stock kernel, once set it up, after reboot it stays, while with this kernel I have to re-set again from developer option. Does it happens to others ?
[OnePlus 3 & 3T Cross Device Development] buckofive:
I have the same problem with OOS 4.0.2 based ROMS and the 3.0.3-x blu-spark v14 recovery. Does the kernel only support OOS 3.2.* based ROMS?

It seems that flashing the kernel zip is modifying the twrp recovery RAM disk. I tried this with flashes of Freedom OS CE 2.2.2 and Experience ROM v9 with no luck last night.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Does the title of the thread says it supports N ROMs? There are no sources for N kernel support. Let's say this 10001 times, since 10000 isn't enough .

No, the kernel zip doesn't modify anything in recovery (which btw works fine for both MM and N ROMs flashing), that's non sense.

Now let's keep the thread clean of OT.
[OnePlus 3 & 3T Cross Device Development] buckofive:
I apologize - I had misread your post from yesterday saying it was the "Hopefully this will be the really really the last MM build before N." and in my eagerness to flash the kernel got it mixed up. Sorry that I ended up being the 10001st person to end up in flashing folly.

But at least I did a lot of testing of your new recovery which is working fabulously. I used it to flash with both EXT4 and F2FS and with the N roms and it went off without a hitch. Thanks for your hard work and sorry to have bothered you with an OT post.
[OnePlus 3 & 3T Cross Device Development] nmlssit:
https://github.com/OnePlusOSS/android_vendor_qcom_thulium/commits/oneplus/QC8996_N

It was about damn time!
[OnePlus 3 & 3T Cross Device Development] neildalal:
OnePlus source release started.

https://github.com/OnePlusOSS/android_vendor_qcom_thulium/commits/oneplus/QC8996_N

Edit: Sorry guess I'm late to the party
[OnePlus 3 & 3T Cross Device Development] dante_nfs:
waiting for your magic [MENTION=3873953]eng.stk[/MENTION]
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Yeah, seems like source is unified for both devices, blu_spark always one step ahead ;)

Also from a quick look, seems like they upstreamed f2fs, maybe it can end the fs duality he have atm.

I will start cracking it wgen I have the time, stay tuned!
[OnePlus 3 & 3T Cross Device Development] abalam:
Tha man, tha man[emoji106] [emoji106] [emoji106] [emoji106]
[OnePlus 3 & 3T Cross Device Development] mysky911:
Oh no! Oneplus3 will fly once again with Blusparked Nougat!!! :good:

:cowboy:
[OnePlus 3 & 3T Cross Device Development] squrl:
I'm having a problem with the modified TWRP, any setting I modify (24h clock display, timezone, etc.) won't survive reboot. Everything gets reverted to default. Anyone else facing the same issue?
[OnePlus 3 & 3T Cross Device Development] madsponge26:
The time has come eng.stk!
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Currently on OOS 3.2.8 , Data formated as f2fs, with latest modified TWRP v14 installed. I have PIN on boot. On TWRP initial screen i get Brightness and 24 Clock disabled.

After i type the PIN and TWRP decrypts it I get my settings back.

Check if you are on the V14 of modified TWRP. And if you have Data formated to f2fs, OP has stated that it's targeted for that filesystem.
[OnePlus 3 & 3T Cross Device Development] squrl:
That makes sense as the TWRP config file resides on data partition that is encrypted before PIN is entered, I understand that. I'm using a PIN too, except in my case, all the changes in settings I've made are gone even after successfully decrypting /data.

And yes, I'm on v14 of eng.stk's TWRP and my /data partition is formatted as f2fs.
[OnePlus 3 & 3T Cross Device Development] Riku Azhurlar:
Am I the only one happy OnePlus finally started releasing code? The kernels up at least don't know about any of the other stuff but hey that means I can finally get a custom kernel that works
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Soon...
[OnePlus 3 & 3T Cross Device Development] fuukinguy:
Doooode, can't wait... ?
[OnePlus 3 & 3T Cross Device Development] tssphysicsboi:
Can't wait to use N. Need this kernel to use Android pay. <3
[OnePlus 3 & 3T Cross Device Development] mysky911:
OMG... am i still dreaming??? so fast?! :D
[OnePlus 3 & 3T Cross Device Development] AssToast:
You can just use Magisk for AndroidPay
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r32 unified

All right crew!

New build is up. Wicked!

Keep in mind: I will give no active support for custom ROMs or OB. Meaning, if using anything besides stable OOS don't bother posting about it.

I am only interested on debugging stuff in stable OOS (with logs and reproducible steps to replicate the issue).

Don't spam this thread with CM or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.

Also don't go spam and bug reporting on ROM threads if using this.

If you like my work, donations are always welcome (but not mandatory).

Don't forget to hit thanks, it's free ;)
[OnePlus 3 & 3T Cross Device Development] AcidNoteZ:
So r32 is not for N right?
[OnePlus 3 & 3T Cross Device Development] agayabag:
Yes it is, for N
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
Well the title says OOS 4.0* so I'd say it should work on N