yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] X-thunder:
year, you are right. I got the offical kernel.

Seconds ago I flashed the official twrp which is not booting at all.

Now I flashed an older modified twrp file. Works again like a charm.

On the other hand this means there is a bug in the blu_spark recovery.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Sure.

Hence I said it may not work with ext4.

It's by design, OOS 4.0 is using f2fs by default and my only target is a proper f2fs recovery.

There's no bug, it's by design like said above.

f2fs is default on OOS 4.0 and should continue on next releases, you should just make the jump (backup your stuff before ofc).

People that cleanflashed/factoru reseted on OOS 4.0 install got f2fs by default.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nope, you can use as it is.

dm-verity is a warning from the bootloader, having source or not makes no difference.

It's no biggy, just a 5sec nag.
[OnePlus 3 & 3T Cross Device Development] andyman_187:
can we use .28 TWRP to flash this or better using fastboot? Is there even a difference?
[OnePlus 3 & 3T Cross Device Development] frikakwa:
Flashify it. ?
[OnePlus 3 & 3T Cross Device Development] andyman_187:
Again, any difference from a good old fastboot flash? I've always been wary about flashing recovery through recovery or other methods other than fastboot.
[OnePlus 3 & 3T Cross Device Development] LELBOT:
Proper Procedure for installing OOS 4.0 without any dm verity errors and f2fs.

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

Here are the Proper Instructions to Install Oxygen OS 4.0 without DM - Verity Error and F2FS -

For Unlocked Bootloader + TWRP + Rooted users (Having any Rom installed before) -

Requisites -

Backup All your internal Storage Data - Sync all Google Stuff - backup all Messages or stuff.

Downloads -

Oxygen OS Official OTA Full Zip - http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip

Official Recovery ( Oxygen OS ) - https://www.androidfilehost.com/?fid=24591000424943319

TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308

SuperSU 2.79 Stable - https://www.androidfilehost.com/?fid=385035244224405910

Custom Rom Based on OOS ( Choose any) - Freedom OS - https://xdaforums.com/one...s-1-0-t3409348

Experience Rom - https://xdaforums.com/one...-v1-0-t3522259

Hyper Stock - https://xdaforums.com/one...stock-t3521946

Procedure -

1.) As mentioned, BACKUP EVERYTHING.

2.) Flash stock oxygen recovery though fastboot or in twrp.

3.) Boot to stock recovery, sideload Official 4.0 ota via adb.

4.) Reboot and dont set up device ( not necessary ) enable developer settings and usb debugging.

5.) Flash TWRP .23 NOT .28 (.28 is bugged with decryption and f2fs errors)

6.) Boot to twrp, wipe /data to f2fs and /system and /cache to ext4.

7.) As wiping everything, copy any custom oxygen os build and supesu 2.79

8.) Flash any custom oxygen os build ( all these 3 builds flashes supersu itself, so no need to flash supersu, buy keep it for further later use.)

9.) Reboot, Setup and copy all ur stuff.

This method will surely get u a Rooted, decrypted, f2fs /data partition Oxygen Os 4.0.

For Stock/Twrp Recovery, Encrypted/Decrytped, Locked/Unlocked Bootloader, Unrooted Users (Those who dont want to root or decyrpt) -

1.) Backup is necessary as internal storage will be wiped, its a one time process as for now every Oneplus update will be f2fs /data compatible.

2.) ADB sideload 4.0 ota.

3.) Reboot and dont set up device ( not necessary )

4.) Go to backup and reset in settings, do a factory reset with internal storage ( This will wipe everything, BACKUP NEEDED )

5.) Let the process complete and check /data partition via DiskInfo app.

6.) If it isnt, do a factory reset again via stock recovery.

7.) If nothing helps, follow first method.

I cant guarantee this will work, but many users have reported this as working.

I think this will be sufficient
[OnePlus 3 & 3T Cross Device Development] cet90:
is this kernel compatible with OOS 4.0?
[OnePlus 3 & 3T Cross Device Development] rOck4n:
Nope, kernel source needs to be released first, and nobody knows when it's gonna happen.
[OnePlus 3 & 3T Cross Device Development] ungeeked:
This recovery is a bit slower to load than twrp-28 for me. Anyone else?
[OnePlus 3 & 3T Cross Device Development] nmlssit:
eng.stk doing more for the OP3/t Community than TWRP team, praise him. ?
[OnePlus 3 & 3T Cross Device Development] Chaplan:
I wonder if OnePlus was aware of that when they gave away devices to Devs that don't contribute with half the work [MENTION=3873953]eng.stk[/MENTION] does for OP3/3T devices.

Yeah, they must be...
[OnePlus 3 & 3T Cross Device Development] Lownita:
That sounds unnecessarily complicated. So it would mean that flashing stock OTA via stock recovery would get rid of dm-verity warning, even if you'd flash anything you want and switch to twrp afterwards. How would that be possible with the bootloader staying the same?
[OnePlus 3 & 3T Cross Device Development] KingBeike:
Sucessfully encrypted f2fs storage and decrypted with your v11 twrp :) thank You so much, finally Feeling Safe again :)!!!
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Seems like i have to bite the bullet and make a jump to f2fs now. Thanks for the updated recovery OP.
[OnePlus 3 & 3T Cross Device Development] habylab:
Anyone know if the touchscreen latency fix is included in 4.0, or can we flash it?
[OnePlus 3 & 3T Cross Device Development] NeoMustain:
Your links to Oxygen OS Official OTA Full Zip and stock recovery are a bit messed up.
[OnePlus 3 & 3T Cross Device Development] Simone98RC:
What firmware are you running?

---------- Post added 07-01-2017 at 00:00 ---------- Previous post was 06-01-2017 at 23:40 ----------

[MENTION=3873953]eng.stk[/MENTION] what difference between TWRP 3.0.2-0 and 3.0.2-1 based recovery?

Why latest TWRP is based on 3.0.2-0 instead of 3.0.2-1?

Thanks in advance for clarification :good:
[OnePlus 3 & 3T Cross Device Development] Chabola:
[MENTION=3873953]eng.stk[/MENTION] Im on official oxygen is 3.2.8 with latest unified blu_spark and using latest kernel auditor. I changed the CPU governor from blu_active to interactive and changed the CPU frequencies but everytime I reboot the phone it gets reset. Any thoughts on how to fix? I ensured to select apply on boot and even cleared cache but it still happens.
[OnePlus 3 & 3T Cross Device Development] LELBOT:
Links Updated
[OnePlus 3 & 3T Cross Device Development] null0seven:
OoS v.4, Nugat, have by default F2FS data partition. At least if you clean flash.

You can flash recovery by: Fastboot, Flashify or any flashing software, or by twrp (like the official site say).

Thanks enk_stk for all youre recoveries. They help A LOT. Awesome work.
[OnePlus 3 & 3T Cross Device Development] KingBeike:
Stock Nougat . 4.0 ...No custom rom
[OnePlus 3 & 3T Cross Device Development] damnation333:
Thank you so much. I've sent you a donation! :)
[OnePlus 3 & 3T Cross Device Development] :
Thank you very much. Works like a charm!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Can we stop with the OT?

THanks.

3.0.2-X based. On v11 case it's 3.0.3 based, except from packing the TWRP app inside.

I remove lot's of cruft from TWRP, add some upstream and other yet gerrit stuff, build improvements and other blu goodies inside.

This one is made from my OP3/T unified branch.

N latency seems a little better than any MM ROM.

No need for that.

Try giving a higher timeout when applying it on boot.

Always worked fine.

Thanks for the support mate :good:
[OnePlus 3 & 3T Cross Device Development] habylab:
Looks like you've tried to reply to my comment, but it's gone weird! Nevermind.

Thanks for your hard work :)
[OnePlus 3 & 3T Cross Device Development] Simone98RC:
[MENTION=3873953]eng.stk[/MENTION] just another question: can you confirm that TWRP v11 supports f2fs decryption on Open Beta 10?

Thanks much for answering
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Try and let us know.
[OnePlus 3 & 3T Cross Device Development] raven6681:
the phone does not enter the recovery after I flashed the stock one. Stock OOS 4.0
[OnePlus 3 & 3T Cross Device Development] Simone98RC:
Confirmed that Open Beta 10 decryption works with latest TWRP v11.

Thanks much :good:
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Anyone brave enough to test if this TWRP is working with OOS 4.0.1?
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
Been working for hours on my end. F2FS and 4.0.1
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Cripted and PIN at boot too? That's my main concern.
[OnePlus 3 & 3T Cross Device Development] Klobal:
Working fine on my end.
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Thanks!
[OnePlus 3 & 3T Cross Device Development] Re¢o:
[MENTION=3873953]eng.stk[/MENTION] I have a problem when I Flash your Recovery I can boot in it but when I reboot my device ( I'm on oos 4.0.1 ) and then booting into recovery TWRP is erased and the Stock Recovery have replaced it . Thanks for helping :)
[OnePlus 3 & 3T Cross Device Development] mysky911:
I am on ext4 with FreedomOS 1.7 (OOS3.2.8) and ofcoz powered with blu_sp★rk r25 unified:D.

zero error!!... Thanks [MENTION=3873953]eng.stk[/MENTION]! How you make it to access encrypted Data partition without prompting for password on this version??!!! Love it too much! ;)
[OnePlus 3 & 3T Cross Device Development] pramathesh:
Can I install the kernel on experience Rom v 7.0 with F2FS
[OnePlus 3 & 3T Cross Device Development] SHOTTZZ99:
So I'm on oxygen os 4.0.1, F2FS for data partition and stock recovery. I would like to root it and still would like my data encrypted, is this still possible with the new twrp?

I do not want to decrypt my internal storage
[OnePlus 3 & 3T Cross Device Development] Facebooook:
Working fine...without pin/ password issue..

I am on v11 twrp and decryted OS 4.0 with root.
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
I'm still encrypted, think you should be fine to flash this twrp and SuperSu
[OnePlus 3 & 3T Cross Device Development] SHOTTZZ99:
Just flashed twrp and SuperSU and it works. No DM Verity error.

Thanks
[OnePlus 3 & 3T Cross Device Development] abhibnl:
So apparently this still does not decrypt data on ext4 partition but that's fine considering the OP already mentioned that earlier and it's not even updated for ext4. But i somehow managed to get 4.0.1 + root working by this on ext4 encrypted. So i am really good for a while. All i have to do now is to wait for an updated TWRP recovery which can support ext4 file system. Thanks OP! I hope you will make an updated twrp recovery someday.
[OnePlus 3 & 3T Cross Device Development] Explorer23:
From his previous posts I highly doubt he has any interests in ext4 any more.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
True that! Hopes are high from official TWRP team
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Latest official TWRP release was in August, good luck
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Lol! True that. Ext4 users are in the hands of God. Lol
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Ok guys enough of TWRP talk already.

We already know what works and how, no support means no thread cluttering.

Let's move on.
[OnePlus 3 & 3T Cross Device Development] finallau:
Any change log for TWRP v11 or may I know where is the original thread for TWRP blu spark?
[OnePlus 3 & 3T Cross Device Development] Kiranb212:
try searching just couple pages.. :svetius:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Not kernel related, but I'm been watching lot's of people with battery going down fast, lot's of heat, apps crash in OOS 4.0/4.0.1, so here goes: I bet 90% of you guys are using SuperSU SR1or SR2.

I had a couple of that symptoms in a couple devices: cpus locked to max freq, too much heat, etc.

Most people see this using facebook.

We have tested in 3 or 4 phones and uninstalling FB worked on some but not in all.

Only using stable SuperSU 2.79 instead of the SR builds fixed it. In all the tested devices we could use facebook and all the junk normally and no more issues.

It's easy to jump on OnePlus, but I don't see all that bad stuff on N ( except source taking 100 years to be posted).

Hope it helps.
[OnePlus 3 & 3T Cross Device Development] AssToast:
Why not just use magisk? It's easier to bypass safetynet with magisk anyway without all the suhide stuff.

I don't really see any advantage to using SuperSU other than if you want to use chainfire's apps.
[OnePlus 3 & 3T Cross Device Development] rkrohan:
I use Phh's superuser and still have that problem.
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
Concerning SuperSU and f2fs here is perhaps the solution

https://xdaforums.com/showthread.php?p=70492947

Arter is a well known dev and found issues with f2fs sources and commits.

Kernels must include some modification to handle properly the virtual ext4 disk created by SuperSU systemless in a f2fs environment.
[OnePlus 3 & 3T Cross Device Development] NevaX1:
FreedomOS already include the stable variant of supersu and some users complain about that too, so I don't think it's coming from there.

We need to keep in mind, the Facebook apps are whitelisted on the kernel ramdisk. Removing them can maybe help a little bit I guess.

I'll give it a try as soon as I can.

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk

EDIT : It's now fixed, check attachement.

http://cloud.tapatalk.com/s/5875df7d664f1/IMG_20170111_083131.jpg?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
That has nothing to do with the discussion at hand.

Well I don't use that and I don't know if similar changes were made.

Also I don't want to start a discussion about root here, it's just a tip that can help out a bit.

Yeah it's a nice testing and discovery.

The first A issues we don't have it because we (and stock kernel) use the Linux 3.18 base and not any of the backports like 4.8 and so forth used on CM and Official OP3 TWRP.

So, we currently don't have any issue with f2fs, SuperSU and the likes. The SuperSU tip I posted is purely app related.

When I tested f2fs data inlining (that is not default on OOS) I encountered the same B issue, people most will remember it like the infamous "WhatsApp" derp with f2fs.

Like I said at the time, I suspected it was garbage collection no being properly triggered at the time and this confirms it (but it not an issue with our current implementation).

f2fs backports have issues like this and others from time to time, I even encountered several over the years on 3.4 adn 3.10 branches in other devices, so I kind of scraped merging from the f2fs backports in sake of stability.

One of the most troublesome (in past I and others had in moto devices) was backwards compatibility, meaning if f2fs revision was upgraded, people that needed to go back to stock kernel with lower revision had to format their data partition again.

For what I can gather, after upgrading to a ROM with the 4.10 backports, extensions and structure will be upgraded and probably kernels without those 2 compatibility commits will not work (and maybe some data can be even lost when inodes start being processed).

[MENTION=4898097]arter97[/MENTION] did you test using the device coming from an upstreamed 4.10 kernel to OOS 4.0 without full format of the partition?

While I can merge the couple patches on blu_spark and my TWRP for all around compatibility, I'm not all that comfortable with this if people can't go to stock without full data formats.

What's your take on this?

Yeah sure, I don't know if other bugs are present in the ROM, the only ones I got was this (in both several 3 and 3T devices) and the only fix for the cpu locking (and ofc the heat from this happening) was using SuperSU 2.79 instead of the SR ones.

I gather it was the N modifications CF made in this releases, we had similar stuff when going to LP and MM, SuperSU developement has improvements and regressions lie everything else.

For instance, doesn't mean that facebook hadn't an issue itself, but with SuperSU 2.79 SR2 it locked the cpus and with SuperSU 2.79 it didn't (I went back and forth and could replicate this easily).

Also in some devices I saw the cpus locked and don't even had FB or anything related installed.

Only going with SuperSU 2.79 fixed it for good.

This is just a tip to help out less aware users, I don't really pretend to start a big discussion on this.

I found this thread and post there too so people can gather info https://xdaforums.com/oneplus-3/how-to/huge-battery-drain-oos4-t3531313/page2
[OnePlus 3 & 3T Cross Device Development] mrmcshagbag:
Just in case anyone is wondering if r25 works on open beta 7 it does and flawlessly. I can use Snapchat without force closes. Previous versions caused forced closes for me. Blazing fast! Keep up the good work!! ?
[OnePlus 3 & 3T Cross Device Development] AssToast:
It works with nougat?
[OnePlus 3 & 3T Cross Device Development] dante_nfs:
For god sake please search, search is your friend.

No it's not. OOS 4 source is not released yet.
[OnePlus 3 & 3T Cross Device Development] AssToast:
He said it works with open beta 7. I thought ob7 is nougat. Geez, at least read what I'm replying to.
[OnePlus 3 & 3T Cross Device Development] theduke7:
i have a question, is it possible to encrypt the phone while having root and the new TWRP? i mean encrypt from the phone OOS? onn 4.0.1 and f2fs!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Not particular towards you, but I need to get this out of my system.

I'm so tired of people asking "Is it nougat compatible" all over the forum.

People need to start acting proactive and go ask OnePlus to release the sources instead of the usual spoon feeding, waiting others to do all the job for you.

I don't see anybody posting on social media and so on asking OnePlus to release the sources.

Instead of keep all day long watching bikini girls on the interwebs, make OnePlus know (in a respectful way) that you need the sources released and that's one of the main reasons you bought this phone.

Yes.
[OnePlus 3 & 3T Cross Device Development] nmlssit:
We did here: https://forums.oneplus.net/threads/kernel-sources-for-nougat.482993/

One from OP even replied to my question "what does it mean giving bad code on a stable release", a bit non-sense to me since it means they will not drop source until code is perfect.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Sure that's better than nothing, but I mean mainsteam media and social networks, not a niche forum.

That answer is just nonsense: are they shipping defective sw to costumers on purpose?

What needs to be done is pushing whatever ships with the device and push the fixes needed as we go along, like everyone else does.

Probably what is happening is they figuring out what they can hide/leave out of the kernel sources and push half done stuff like they did several times on 3/3T updates (a very recent one on the 3T: broken gestures since launch and missing drivers on tree https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/issues/24).

Only time kernel source is shipped nicely is at the new device launch, to create all the "we are a community aware brand" hype and even then things were half done in the 3 and the 3T. From then on, is just a constant fight to get things properly done.

And all this for what? There's absolutely no disadvantage for them to push the kernel sources at least a few days after OTAs.
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Well I asked Carl on twitter once, but if it's just me it's like pissing in the ocean lol.

We need to be many and we need to involve big Android communities like XDA, AndroidPolice, AndroidCentral etc

I am sure we can organize something to change this situation.
[OnePlus 3 & 3T Cross Device Development] dante_nfs:
[MENTION=3873953]eng.stk[/MENTION] what you think is the best dev friendly device if we not consider oneplus?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Honestly looking at the Android scene nowadays... none lol

Long live the Nexus.

Yeah... well I'm not inciting a riot against OnePlus, but make them aware of our concerns in a respectful way.

This situation could be easily solved by them and we all would be happy.
[OnePlus 3 & 3T Cross Device Development] dante_nfs:
[MENTION=3873953]eng.stk[/MENTION] well that was funny :D not even pixel is now a day dev friendly?what a shame(sorry for being off topic I will not continue this subject )
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Nah not a riot, it's more like making them aware we did not buy an iPhone lol
[OnePlus 3 & 3T Cross Device Development] Chaplan:
#WhyNoKernelSourcesYetOnePlus
[OnePlus 3 & 3T Cross Device Development] xanthrax:
Because in India hasn`t been pushed the latest OTA ... until everyone will get , 100% , no sources will be available so we need another hashtag GetIndiaIntoOTA
[OnePlus 3 & 3T Cross Device Development] Chaplan:
All OnePlus Indians have already sideloaded or OTA updated via VPN. Just look into YouTube. Lame excuse that one.
[OnePlus 3 & 3T Cross Device Development] xanthrax:
This is true and my point as well ... that`s NOT my excuse , that`s Oneplus`s excuse but I`m sure you got it right

lol
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Those are just excuses. Doesn't really matter if 100 people or 1000000 people got the OTA.

Push OTA, push the source. Push OTA, push the source.

Not push 10 OTAs and push the source when feel like it.

Hyping about being "developer friendly" without respecting GPL is not acceptable.

But honestly, judging by how this went and how it's going, don't count on anything changing really

They sure improved sw distribution with better and faster OTAs, the beta program (again being non GPL compliant, no sources whatsoever) an doing better git commits comentaries so at least we developers know to which OTA the code refers to. But they have yet a long way to go.

I will think alot when choosing my next device because I need to tinker with things.

For a regular OEM phone it's OK.
[OnePlus 3 & 3T Cross Device Development] xanthrax:
Yup... True Blue mate, at least this piece of hardware is snappy enough but definitely developer annoyingly

Sent from my Darkside of Oneplus 3T
[OnePlus 3 & 3T Cross Device Development] Chaplan:
I got it right, of course it is not your excuse.

I am waiting for one plus to come up with an answer on Twitter for the question I made yesterday.

#WhyNoKernelSourcesYetOnePlus is live and living in Miami... Not really Miami but on Twitter at least.

:good:
[OnePlus 3 & 3T Cross Device Development] nmlssit:
I asked to the italian support on twitter, they said they need to finish rollout first and 4.0.2 is coming next week.

Not dropping sources until rollout end + one new OTA a week = never releasing source because a new OTA is dropped before the previous can finish? lmaowtf.
[OnePlus 3 & 3T Cross Device Development] :
Thank you for this lovely beautiful kernel [MENTION=3873953]eng.stk[/MENTION] :good:

Sure i can feel right away this phone is now so much smoother, cooler, faster, compared to the stock kernel. :cowboy:

Now lets back to the hot topic, sorry for interrupting! :silly:
[OnePlus 3 & 3T Cross Device Development] angelmakumbe:
[MENTION=3873953]eng.stk[/MENTION] I cannot save to the PC the backup file boot.emmc.win with the latest recovery .11
[OnePlus 3 & 3T Cross Device Development] nestoor23:
deleted
[OnePlus 3 & 3T Cross Device Development] ALEX37330:
how can i instal it on aicp ? i try with change filesystem but it doesn t work my data was not erase why ? and after phone boot on twrp and i can t boot system
[OnePlus 3 & 3T Cross Device Development] eng.stk:
twrp-3.0.3-x_blu_spark_v12-op3

All right crew!

Here's an updated TWRP 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=22583

No mirrors allowed.
[OnePlus 3 & 3T Cross Device Development] gillim74:
still bootloops to twrp on aosp roms