yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 & 6T Cross Device Development] eng.stk:
blu_spark extras v9.101 (Pie only)

All right crew!

Here's an updated TWRP with all the blu_spark goodies inside and fully synced with TWRP Android-9.0 branch (including more recent upstream than official TWRP) and some specific device fixes.

Fully synced with TWRP 3.3.1+, name changing to reflect base 9.version, full compatible with Pie stuff.

To use the img, fastboot boot the img and then install recovery from within TWRP (go to Advanced -> Install Recovery Ramdisk -> Select TWRP img). It will install to both slots.

There's an all new blu_spark exclusive AK3 powered twrp installer zip, flash as always (experimental, use with caution).

Delete your twrp settings or else issues may arise if coming from other version besides blu_spark.

twrp-3.3.1-x_blu_spark_v9.101_op6

Wakelock blocker info and example script

I'm just sharing my personal mods since people asked, meaning no support will be given (don't bother post about it).

If your cat get's on fire you're on your own ;p

No mirrors please

If you like my work, donations are always welcome.

Don't forget to hit thanks and rate the thread nicely, it's free ;)
[OnePlus 6 & 6T Cross Device Development] Pseudonym:
If old bluspark TWRP (9.96) already installed no need to fasboot boot? Just flash from within TWRP?
[OnePlus 6 & 6T Cross Device Development] eng.stk:
Fastboot boot new version and install from there (different from flashing an image). Seems pretty obvious.
[OnePlus 6 & 6T Cross Device Development] iPsychoGeek:
Any reason to not include zip version of TWRP?

Отправлено с моего ONEPLUS A6000 через Tapatalk
[OnePlus 6 & 6T Cross Device Development] lm089:
just updated as described above (fastboot boot xxx, then install from new temp recovery image).

Result is that now boot partition seems to be completely replaced by twrp.img: everytime I try to reboot into system I end up in recovery. Lucky me I did a Nandroid before I started all this which right now I'm trying to recover. Hopefully I can boot up my phone after that.

(Q: had it been sufficient to just recover the boot partition from the Nandroid?)

UPDATE: darn, am having a bootloop now, always end up in bootloader. And trying to again run "fastboot boot twrp*.img" gives me an error "FAILED (remote: Failed to load/authenticate boot image: Load Error)"

Anything I can do other than downloading and installing stock ROM image?
[OnePlus 6 & 6T Cross Device Development] eng.stk:
blu_spark r87 release (pie unified)

All right crew!

New build is up, smoothy smooth baby :highfive:

This kernel is unified, good on OP6/6T.

Also checkout latest recommended blu_spark extras with blu_twrp v9.101 (Pie support).

This is only for Pie ROMs! (with Pie based kernels also in case of custom ROMs)

blu_spark_r87 release

Keep in mind: I will give no active support for custom ROMs (including OOS based ones).

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

Don't spam this thread with LOS 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.

No mirrors please

If you like my work, donations are always welcome.

Don't forget to hit thanks and rate the thread nicely, it's free :)
[OnePlus 6 & 6T Cross Device Development] eng.stk:
TWRP already have a installer on the img, subsquent updates can use that feature also.

No need for an extra zip and extra work for me.

You probably flashed the img directly either on twrp or fastboot, probably to boot partition.

Flash your stock boot.mig and follow the instructions to isntall twrp correctly.

It's expected to people know around A/B twrp stuff and newest official updates and how to deal with them.
[OnePlus 6 & 6T Cross Device Development] dobi3:
New twrp-3.3.1-x_blu_spark_v9.101_op6.img All working fine here :good:
[OnePlus 6 & 6T Cross Device Development] lm089:
Hm - here's what I did:

1. removed any security settings / set security to none

2. booted into recovery (V 3.3.0 blu_spark) and did a full backup

3. set twrep settings to standard

4. booted into bootloader

5. from windows pc's cmd issued 'fastboot boot twrp-3.3.0-x_blu_spark_v.9.101_ip6.img' >> phone booted into new recovery

6. went to advanced > install recovery ramdisk >> twrp-3.3.0-x_blu_spark_v.9.101_ip6.img located in /sdcard/install/twrp/

7. just to see whether everything went well rebooted into recovery (>> success)

8. from recovery tried to boot into system >> that's here the problems started

So I'll try to get a stock boot.img from OnePlus, hopefully no probs. But where did I go wrong?
[OnePlus 6 & 6T Cross Device Development] -earth-:
Happend to me too.

I switched to install image, and install Recovery Ramdisk. Thats the fault!

Do it this way, how in the description:

go to Advanced -> Install Recovery Ramdisk -> Select TWRP img
[OnePlus 6 & 6T Cross Device Development] lm089:
But that's (what I think) I did. But mayby my thumb slipped to the wrong button?
[OnePlus 6 & 6T Cross Device Development] AdrianM:
I've just done the right steps as well, and got into a recovery bootloop.

Then I went to Advanced - Fix recovery bootloop and that allowed me to boot back into the system.
[OnePlus 6 & 6T Cross Device Development] bohemist:
I followed the instructions on installing the new TWRP but got a Recovery Bootloop. And, I noticed there is also an option to Fix Recovery Bootloop.

I did it and it fixed the recovery bootloop and successfully boot to system.

Reboot to recovery (TWRP) again and flash Magisk. Success :good:

[MENTION=3873953]eng.stk[/MENTION] I also notice there's an option "Install Kernel". Is this through this way on installing or updating blu_spark kernel or the same old way of flashing it?
[OnePlus 6 & 6T Cross Device Development] eng.stk:
No, nothing to do with blu_spark kernel, that's all recovery.

Yeah if people have magisk installed they need to flash it before reboot or else it will reboot to recovery. Liek it always was with TWRP.

That Fix recovery bootloop just removes Magisk remants before reboot so there's no bootloop.

fastboot boot recovery, install twrp (read release post), install root, install blu_spark, reboot. Easy peasy.

kernel zip is needed like always.
[OnePlus 6 & 6T Cross Device Development] bohemist:
Everything is perfect now :good::)
[OnePlus 6 & 6T Cross Device Development] spikerspike97:
Is it mandatory to boot into the new recovery? Can`t I just go into the current recovery and flash the img to update?
[OnePlus 6 & 6T Cross Device Development] kryshnakishore:
Latest image file without zip version seems confusing.. Can someone recap the steps how to install latest version, it would be very helpful to the most users I guess
[OnePlus 6 & 6T Cross Device Development] lm089:
Oh dear, completely had forgotten about Magisk...

Hope my old brain will remember next time :laugh:
[OnePlus 6 & 6T Cross Device Development] manudhomra:
The new way to install the recovery seems to be complicated, in case someone flashing custom roms then he has to connect the phone to pc Everytime whenever updating the rim in order to keep the recovery???? What will be flashing and updating process with this img twrp???

Before treble we used to flash like below:

Flash rom

flash twrp.img to recovery partition

Flash magisk

Reboot.

After treble:

Flash rom

Flash recovery zip

Reboot recovery

Flash magisk

Boot system

Can anyone please suggest new flashing procedure??? And can we flash the latest img file from inside the recovery after flashing ROMs??
[OnePlus 6 & 6T Cross Device Development] AdrianM:
Initially I thought the same thing.

But, after a bit of thinking, I assume that after you've flashed the ROM, you go back to 'Advanced - Install recovery ramdisk' and you do that again. That way you'd have the recovery back. It's instead of flashing the zip.

I haven't tried it, so maybe someone can say if it's right or not.
[OnePlus 6 & 6T Cross Device Development] manudhomra:
Yeah, that's what I'm thinking as well. Hope to get some comments from recovery author. .
[OnePlus 6 & 6T Cross Device Development] Blackcrx:
I have been using this kernel for some time now and I don't think the baked in settings get applied.

I have working magisk and root already but every time I flash a new build the Governor always stays at schedutil and not Blu schedutil. I checked the settings in kernel auditor, Franco app, ex kernel app and they all show the same. None of these apps are set to apply on boot. I've even tried uninstalling all the kernel apps, reboot to install twrp, reinstall kernel app and settings are same as before.

Can someone please post the default baked settings so I can manually copy it?

Thanks in advance.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I tried doing just that, and it seemed to work fine. I had v9.100 installed on the phone already and was trying to flash back to OOS 9.0.5 in preparation for switching custom ROMs, so started by doing a fastboot boot of the .img file, then I flashed the OOS zip (which goes to other slot), then did the Advanced > Install Recovery Ramdisk thing and selected the v9.101 .img file from internal storage, rebooted to recovery, and it came up to the other slot with v9.101 recovery from the handset (no fastboot required at that point). Repeated to make sure it was on both slots, no problems.
[OnePlus 6 & 6T Cross Device Development] iElvis:
Look, guys, this isn't (or shouldn't) be hard if you understand how things work on this phone. No need for fastboot or any rigamarole.

-reboot recovery

-install>install image>select twrp file>install recovery ramdisk

-reboot recovery

-flash magisk and kernel

-reboot system

Done.
[OnePlus 6 & 6T Cross Device Development] kryshnakishore:
This is wrong it will boot loop guys dnt follow this
[OnePlus 6 & 6T Cross Device Development] blaspheme000:
That is the correct way to do it tho unless you are using custom rom/decrypted oos.
[OnePlus 6 & 6T Cross Device Development] bohemist:
Have you tried it yourself using a version of TWRP prior to the latest posted by [MENTION=3873953]eng.stk[/MENTION] with no bootloop issues at all?
[OnePlus 6 & 6T Cross Device Development] manudhomra:
What will be the way if someone is using custom rom???
[OnePlus 6 & 6T Cross Device Development] iElvis:
Yes, I posted that right after doing it. But I am on 9.0.5 so that caveat mentioned earlier is valid. Follow the instructions for your rom if you're not on OOS.
[OnePlus 6 & 6T Cross Device Development] storytellerz:
Hi, anyone has the zip file for the latest blu_twrp?
[OnePlus 6 & 6T Cross Device Development] Geoz:
Just flash the .img from twrp
[OnePlus 6 & 6T Cross Device Development] gorilla p:
I just confirmed how it's done. I'm running OOS 9.0.5

Make sure you are on latest previous recovery 9.1.0 so you have the features needed to complete this.

Reboot to recovery

Advanced>Flash Recovery Ramdisk>Flash Blutwrp image

Flash Magisk like normal

Reboot to system.
[OnePlus 6 & 6T Cross Device Development] Pseudonym:
So if you want to dirty flash these are the steps?

Reboot to recovery

Flash ROM

Advanced > Flash Recovery Ramdisk > Flash bluspark img

Reboot to recovery

Flash Magisk

Flash Kernel

Reboot

Pls confirm thanks
[OnePlus 6 & 6T Cross Device Development] scloss84:
So if we dirty flash, we would have lost previous recovery, do we flash 9.1.0 zip file first, then reboot to recovery -> advanced.... and the rest?

May I also request for a detailed instruction, many thanks in advance.
[OnePlus 6 & 6T Cross Device Development] eng.stk:
Guys enough of this already, this is not a TWRP support thread.

Instructions are in release post, read and follow. I already posted some tips, is not rocket science.

https://xdaforums.com/showpost.php?p=79624522&postcount=1910

Don't flash the img directly or you'll be having issues with decryption after. THe install procedure is in release post.

If you're rooted don't forget to flash Magisk before reboot. Kernel zip is always last.

All basic recovery how to for AB devices since always.

If you don't know your basics, read and search until you do. Otherwise stay put.

Now let's get on topic.
[OnePlus 6 & 6T Cross Device Development] DennySPB:
May be someone needed.... flashable zip version of 101

Mod edit: Link removed!

As the developer declares in the OP mirror download links are not allowed:
[OnePlus 6 & 6T Cross Device Development] nokia5700black:
before remove "repack" can you make normal zip?
[OnePlus 6 & 6T Cross Device Development] yldlj:
The thing is now we need a pc to update OOS or just updating twrp. Maybe you can start a different thread for twrp?
[OnePlus 6 & 6T Cross Device Development] eng.stk:
Nope, it's only one time. After that you can use the updated recovery img (when for instance I push v9.102) and install it from TWRP.

For OTAs it's the same like always: flash full OTA zip and install the img with new method while on TWRP, before reboot to recovery to install the rest of your extras.

Pretty much basic stuff. What you people discuss on OTAs and recovery threads?

BTW this is the new official TWRP install system, zips are going bye bye.

6 thread: all derpage all complains.

6T thread: no derpage no complains.

Conclusion: T models are better :laugh:

Now seriously guys let's move on please.
[OnePlus 6 & 6T Cross Device Development] Mar-cel:
Is this Kernel fully compatible with Open Beta`s ?
[OnePlus 6 & 6T Cross Device Development] -Deco-:
That's a yes and no - that is, it may work an a certain OB version and not another, you will have to try it for yourself.

Should it not work, since reflash OOS and you'll be fine.
[OnePlus 6 & 6T Cross Device Development] eng.stk:
^^^ this

Should work fine in the latest, 6T guys say so.
[OnePlus 6 & 6T Cross Device Development] nokia5700black:
If I update my rom not from TWRP, but from system update in background?

twrp.zip I can flash before first reboot in ex kernel manager or magisk manager, than flash magisk in inactive slot after ota.

now i cant save twrp after ota rom install not from twrp without pc.

use phone with A/B for sitting and flashing in twrp 5-10 min on black/blue screen and 2 reboots (for gapps/magisk after changing slot) or native fast background intstall and 1 fast reboot?)

also many custom roms backup gapps only from their udpater, not from twrp...
[OnePlus 6 & 6T Cross Device Development] eng.stk:
First world problems. You don't even need twrp then.

iirc there's a magisk zip module to keep recovery in otas.

Don't really care how you use your phone, I know how I want to use mine.

By now, this is just becoming annoying.

Sent from my blu_spark'd Oneplus 6
[OnePlus 6 & 6T Cross Device Development] -Deco-:
Most probably not - if the ROM is updated out with TWRP, then the update script for applying system updates will be initialised - this means that it will patch the boot image and get rid of TWRP unless the custom ROM specifically has blu's TWRP version downloaded and applied during the patching of the boot image, you will either end up with no TWRP being installed, or a different TWRP variant (if one is used).

It should be standard practice regardless of it being a custom ROM or kernel to patch updates with TWRP, due to A/B partitioning - should TWRP not be flashed on a system update, you can simply fastboot the TWRP .img file (elevate the partition and flash) like you would during normal installations.
[OnePlus 6 & 6T Cross Device Development] nokia5700black:
or just flash any normal twrp.zip in magisk like module, than flash magisk in inactive slot (2 clicks in manager) lol without pc.

it's offtop for this thread. let's stop it. we have seen what author wanna.

also zip's will be uploaded at another forum)
[OnePlus 6 & 6T Cross Device Development] yldlj:
Thanks for the explanation. I think alot of people just thaught you need to boot the. Img everytime. :good:
[OnePlus 6 & 6T Cross Device Development] Meepaco:
Getting idle drain after flashing TWRP wrong -> use the fix recovery bootloop feature -> flashing magisk-> flash kernal.

Would it be recommended to dirty flash OOS, twrp, magisk-, kernal, etc?
[OnePlus 6 & 6T Cross Device Development] hdotzlaw:
Viper4Android FX problem

Hi,

I was unable to get Viper4Android FX 2.7.1.0 to work with r87 on my OnePlus 6 OOS 9.05. V4A does not process the audio. I tried uninstalling / reinstalling Magisk / kernel from scratch twice and both times “Processing No”.

Reverting back to r84 everything works as it should.

??
[OnePlus 6 & 6T Cross Device Development] Aashay:
Anyone experience device heating up more than usual? I've played pubg for hours but the device never heated up so much today I played only for 30 mins and it's already too hot. Even while charging it heats up. Any reason behind it you guys are awake of? Any solutions? I'm on OxygenOs 9.0.5 with latest blu spark and magisk.
[OnePlus 6 & 6T Cross Device Development] eng.stk:
Yeah have your system the most clean possible when upgrading stuff.

In whst build are you on? Half the people probably don't even saw my ketnel release post lost on the middle of all the twrp noise.

Unless you have some wonky mods running I doubt anything related to any of the above.

Check out if you have any service/app eating up cpu or any wakelock derping out.

Kernel doesn't knows or care about any of that userspace stuff...

See the above. Also checkout adrenoboost leveld, it activated to enhance 3d gaming.

But had no effect in normal phone usage, charging etc

You probably have something locking up your cpu at high freqs and thus heat.

For instance, a couple weeks ago I had a simple light 2d game that made a weird audio wakelock , that kept stuff awake in background.

Sent from my blu_spark'd Oneplus
[OnePlus 6 & 6T Cross Device Development] Aashay:
I haven't messed around with any of the kernel settings. I'm using it as it was out of the box. I have just blocked a few basic wakelocks from EX Manager.
[OnePlus 6 & 6T Cross Device Development] Meepaco:
Reflashing seemed to not have helped (everything including mods), Found these *alarms*, would they be cause of my drains?
[OnePlus 6 & 6T Cross Device Development] spartan268:
None of them really stick out. I would check partial wakelocks if you're looking for a battery drain.
[OnePlus 6 & 6T Cross Device Development] Arno_Nymus:
I hope someone can help me or could tell me where I'm able to gain help!

I've just tried everything to install latest OB plus latest twrp and kernel of blu_spark.

If I install it, everything seems ok until I try to implement latest magisk into my flash routine.

If I do so I'll end in a bootloop to recovery.

What did I do wrong?

This is what I did:

- Flashed latest OB19

- Flashed IMG of latest TWRP via new feature to do so

- Reboot into just flashed recovery

- Flashed Magisk

- Flashed Kernel

- Reboot into system

--> Bootloop back to Recovery

If I skip flashing Magisk everything is fine.

When I use the 'fix recovery bootloop' feature I'm able to boot to system, but magisk isn't installed.

If I reboot back to recovery and flash magisk I'll end in a bootloop again till I use the fix again.

It seems there's no solution for me to flash latest stuff with working magisk.

Would be great if someone could help me with this or could link me a page where I coul receive support for this problem. (Couldn't find any by myself..)

I know that you won't give support to OB-Users, [MENTION=3873953]eng.stk[/MENTION] and I'm very okay with it!

But maybe here's someone reading this who are also on OB and got a solution - so please, please, please don't delete my inquiry! ?
[OnePlus 6 & 6T Cross Device Development] eng.stk:
Flash magisk again and kernel.

Try bootloop fix on twrp also.

Sent from my blu_spark'd Oneplus
[OnePlus 6 & 6T Cross Device Development] xpakage:
Also try using in TWRP the Magisk module uninstaller. You can Google it or read about it here - https://magiskroot.net/uninstall-magisk-module-twrp/

This works if you have a module which is not compatible with the update and is getting loaded after you flash Magisk, which creates a recovery loop.
[OnePlus 6 & 6T Cross Device Development] Arno_Nymus:
[MENTION=3873953]eng.stk[/MENTION] [MENTION=3090042]xpakage[/MENTION]

Thanks a lot to you both!

Now it worked!

Tried it several times to reflash magisk after fixing the bootloop via twrp.

After using the unistaller it worked finally.

Seems I had a incompatible mod which caused those reboots!

Now it's up to me to figure out which one caused them. ?

Thanks a lot again! ?
[OnePlus 6 & 6T Cross Device Development] Dude_Virus:
I had the same issue, enable compatibility mode. It looks to be a V4A issues than the kernel because I encountered the same issue with older kernel version.
[OnePlus 6 & 6T Cross Device Development] hotzlaw:
Viper4Android FX problem

Thanks for the tip, I could give this a try; having used V4A on many different phones over the years I realize that it can be tricky to install.

I installed r78 yesterday in order to test some things and V4A 2.7.1.0 is working without having to turn on compatibility mode or installing the Audio Compatibility module .

V4A 2.7.1.0 did stop working when I upgraded from r84 to r87, but I guess if the kernel can have nothing to do with it then there must be some other reason.

Since 2.7.1.0 was released only mid of May this year (rewrite in Kotlin) I hadn't been using it with previous versions of the kernel - I had been using what is now known as V4A "Legacy".

I saw that V4A 2.7.1.0 was updated yesterday, we'll see.
[OnePlus 6 & 6T Cross Device Development] -Deco-:
This is probably due to CPU frequency locking - when there's a conflict with the ramdisk, the scheduler becomes unable to downscale it's frequencies. It is normal for the device to heat during charging - if you charge the phone on a heat-conductive surface, for example a pillow, which will trap the heat and not allow it to dissipate from the phone. This is given since you're attempting to charge your phone when it is already hot, and not when it is cool. There is nothing you can do about this except give it time to cool down (don't use it).

Another note, a phone is not a computer - you're attempting to play a GPU bound game which generates immense amounts of heat whilst combining that with charging an aluminium battery, generating additional heat. Temper your expectations, this isn't a kernel problem, but a problem on what you expect to achieve with the phone.
[OnePlus 6 & 6T Cross Device Development] Aashay:
Do you not read what I sent? Didn't I mention that the phone DIDN'T USE TO GET SO HOT even while playing the game for hours? For my phone to not heat up so much isn't something I'm expecting out of no where it didn't happen in the past which is why I expect it to not happen.
[OnePlus 6 & 6T Cross Device Development] ac3theone:
I'm getting faster drain on the latest kernal as well. No mods just rooted stockb with kernal
[OnePlus 6 & 6T Cross Device Development] eng.stk:
Can't replicate, all normal here.
[OnePlus 6 & 6T Cross Device Development] eng.stk:
blu_spark extras v9.101 (Pie only)

"eng.stk, why you no give twrp installer kernal dev sir?"

Fear not, I decided to make it even better. Introducing xda first AK3 TWRP installer, with slim and faster install times, blu_spark style.

Big shouts to [MENTION=4544860]osm0sis[/MENTION] for being the usual mate:highfive: AnyKernel3 all the things :victory:

Upload to the usual place.

PS: keep in mind this is experimental, your cat can get on fire ;p
[OnePlus 6 & 6T Cross Device Development] SloppyBeef:
Thanks for all your great work eng.stk!
[OnePlus 6 & 6T Cross Device Development] Macusercom:
Does the latest 3.3.0 v9.101 TWRP support the May 2019 security patch in OOS 9.0.6?
[OnePlus 6 & 6T Cross Device Development] -Deco-:
Yes it will work fine with OOS 9.0.6, I've just updated it there.

The process is slightly different however, that being:

Flash the OOS 9.0.6 zip file.

Go back to the main TWRP menu (do not reboot the system), use the arrows.

Advanced - flash recovery ramdisk.

Choose the TWRP image.

Reboot to recovery.

Back again to the main menu.

Install - ZIP file - Magisk v19.2.

Reboot system, and you will retain TWRP with the latest OOS update.