yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7a] eng.stk:
blu_spark_r34 (A14)

New build is up!

Build is for 7a/lynx 14.0.0 (UQ1A.240105.004, Jan 2024), no support for 7/Pro.

If you're running verity/verification OFF, for easy flashing and install logging, Kernel Flasher is recommended.

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.

Download config: HERE

If you're running verity/verification ON (stock default behavior), you need to flash kernel via fastboot (refer to instructions on 1st post).

Changelog:

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

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

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 7a] crissband:
can I flash it to a13 custom ROM?

Sent from Pixel 7a using ReLabs
[Google Pixel 7a] eng.stk:
Nope, it's for A14.

Sent from Pixel 6 using ReLabs
[Google Pixel 7a] crissband:
thanks for the quick reply

Sent from Pixel 7a using ReLabs
[Google Pixel 7a] rycardinho:
I just installed this kernel.. I'm using the stock 14, Jan. I think I can't use the Google wallet. Anyway to fix it? Work around? Does it break the Google wallet? Battery seems to be awesome. I'm not rooted.
[Google Pixel 7a] eng.stk:
After you unlock the bootloader your device is no longer certified and all that stuff will not work.

Doesn't matter if you're rooted, flashed a kernel or not.

To workaround you will need to root with Magisk and use stuff like Play Integrity Fix. There's plenty of info xda about this stuff, search is you friend.

Nope.
[Google Pixel 7a] eng.stk:
blu_spark_r37 (A14)

New build is up!

Build is for 7a/lynx 14.0.0 (UQ1A.240205.002, Feb 2024), no support for 7/Pro.

If you're running verity/verification OFF, for easy flashing and install logging, Kernel Flasher is recommended.

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.

Download config: HERE

If you're running verity/verification ON (stock default behavior), you need to flash kernel via fastboot (refer to instructions on 1st post).

Changelog:

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

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

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 7a] eng.stk:
blu_spark_r41 (A14)

New build is up!

Build is for 7a/lynx 14.0.0 (AP1A.240305.019.A1, Mar 2024), no support for 7/Pro.

Should work on latest ROMs with QPR2, but also QPR1 (LOS 21 tested).

If you're running verity/verification OFF, for easy flashing and install logging, Kernel Flasher is recommended.

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.

Download config: HERE

If you're running verity/verification ON (stock default behavior), you need to flash kernel via fastboot (refer to instructions on 1st post).

Changelog:

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

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

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 7a] nabhse90:
Flashing this Kernel has bricked my phone twice now. I've used EX Kernel Manager and bootloops. Am I in the wrong or is there another recommended method to flash? I've flashed another kernel the same way and it's only BlueSpark that does this.
[Google Pixel 7a] eng.stk:
Use a modern kernel flash app like Kernel Flasher which I recommend in every release post and has support for new partition layout. Or just use fastboot flashing.

If you're with verity enabled, fastboot method will be your only option.

All is detailed in OP.
[Google Pixel 7a] nabhse90:
Will try, thanks
[Google Pixel 7a] eng.stk:
blu_spark_r45 (A14)

New build is up!

Build is for 7a/lynx 14.0.0 (AP1A.240405.002, Apr 2024), no support for 7/Pro.

Should work on latest ROMs with QPR2, but also QPR1 (LOS 21 tested).

If you're running verity/verification OFF, for easy flashing and install logging, Kernel Flasher is recommended.

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.

Download config: HERE

If you're running verity/verification ON (stock default behavior), you need to flash kernel via fastboot (refer to instructions on 1st post).

Changelog:

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

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

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 7a] Sefyron:
Thank you for your work my pixel 7a running buttery smooth with this kernel on stock rom
[Google Pixel 7a] RAZINARES:
Working perfectly on Stock ROM with aPatch. ✨
[Google Pixel 7a] Raj Pandiyan:
I have paired it with Cr on my 7a. Working amazing... Thanks dev @eng.stk
[Google Pixel 7a] eng.stk:
blu_spark_r46 (A14)

New build is up!

Build is for 7a/lynx 14.0.0 (AP1A.240405.002, Apr 2024), no support for 7/Pro.

Should work on latest ROMs with QPR2, but also QPR1 (LOS 21 tested).

If you're running verity/verification OFF, for easy flashing and install logging, Kernel Flasher is recommended.

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.

Download config: HERE

If you're running verity/verification ON (stock default behavior), you need to flash kernel via fastboot (refer to instructions on 1st post).

Changelog:

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

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

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 7a] eng.stk:
blu_spark_r53 (A14)

New build is up!

Build is for 7a/lynx 14.0.0 (AP1A.240505.005, May 2024), no support for 7/Pro.

Kernel zip flashing works with verity/verification ON setups (thanks to @tbalden for the idea and @capntrips for the testing and make it happen).

I decided to ship with KernelSU, Magisk is no longer needed for root setups.

For easy flashing and install logging, Kernel Flasher is recommended.

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.

Download config: HERE

If you're running verity/verification ON (stock default behavior) works the same as verity/verification OFF. You can use zip to flash or via fastboot (refer to instructions on 1st post).

Due to changes to the installer, boot SPL is now updated to match current release (stock behavior). Kernel zip checks this before flashing, but fastboot mode doesn't.

Be careful if you try to flash an earlier SPL patched boot, it will bootloop on reboot.

Changelog:

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

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

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 7a] eng.stk:
blu_spark_r58 (A14)

New build is up!

Build is for 7a/lynx 14.0.0 (AP2A.240605.024, Jun 2024), no support for 7/Pro.

For easy flashing and install logging, Kernel Flasher is recommended.

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.

Download config: HERE

If you're running verity/verification ON (stock default behavior) works the same as verity/verification OFF. You can use zip to flash or via fastboot (refer to instructions on 1st post).

Due to changes to the installer, boot SPL is now updated to match current release (default stock behavior). Kernel zip checks this before flashing, but fastboot mode doesn't.

Be careful if you try to flash an earlier SPL patched boot in stock ROM for instance, it may bootloop on reboot.

Changelog:

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

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

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 7a] wael2:
`Unsupported Android security patch level.`

May 5, 2024
[Google Pixel 7a] RAZINARES:
The latest version is for june security patch , use r53 version

Sent from Pixel 7a using ReLabs
[Google Pixel 7a] eng.stk:
blu_spark_r60 (A14)

New build is up!

Build is for 7a/lynx 14.0.0 (AP2A.240705.004, Jul 2024), no support for 7/Pro.

For easy flashing and install logging, Kernel Flasher is recommended.

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.

Download config: HERE

If you're running verity/verification ON (stock default behavior) works the same as verity/verification OFF. You can use zip to flash or via fastboot (refer to instructions on 1st post).

Due to changes to the installer, boot SPL is now updated to match current release (default stock behavior). Kernel zip checks this before flashing, but fastboot mode doesn't.

Be careful if you try to flash an earlier SPL patched boot in stock ROM for instance, it may bootloop on reboot.

Changelog:

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

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

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 7a] emonkhan826:
This kernel support stock pixel 7 pro july update?
[Google Pixel 7a] eng.stk:
Nope.
[Google Pixel 7a] Klappp:
What's the procedure for updating the system and kernel because right now I'm on June's update and my phone says that there are no more updates. Is it because I have custom kernel installed?
[Galaxy S III Q&A, Help & Troubleshooting] ozenbora9:
I need the kernel that I can overclock the most.
[Google Pixel 6] arsradu:
Hi guys,

I was just wondering if there's a Nothing OS ROM for Pixel devices, just like there's a Pixel Experience ROM for Nothing devices.

Also, did anyone manage to run any of the Nothing Launcher versions currently available? All I get is crashes. The only version that works for me was 1.0.2. So not the original 1.0.0, not later versions. ONLY 1.0.2. But that's an old version. And while it's functional, it lacks features from the newer versions.

I was just wondering if anyone managed to get this working on a non Nothing Phone device and how.

Thank you so much!
[Realme GT Neo 3] arkzok:
So everything was going well. I finally managed to unlock bootloader, I flashed patched boot.img. Everything was working perfect, with the latest updates. Then, out of curiosity I decided to check how well does "Reboot to Recovery" function in Magisk work. Pressed it, my phone powered off. Nothing was happening. I tried to turn it back on by simply holding the power button - nothing. Power button + vol- -> nothing. Power button + vol+ -> Hurray! It showed the logo! It's fine! Orange State: your device will boot in five seconds. Five seconds pass -> it powers off again. I tried to connect it to my computer, it's not in fastboot, it's actually powered off. Tried connecting while in Orange State -> still nothing. I even tried to hold vol- and vol+ buttons while connecting it to my computer, and I actually got "OPLUS preloader connected" notifcation, but then it disconnected and could never connect this way again. Does anyone have any idea what can I do?
[Android Head-Units] mountainhawk82:
Hello,

My Android 12 head unit is performing excellently, except for one issue. The problem lies with my 2015 Mazda CX-5's steering wheel voice button, which won't summon Siri.

I've managed to program the button via canbus settings, and it does work. A single click successfully summons the built-in AI assistant (Toppal Ai). However, when in wireless CarPlay (haven’t tried wired connection), holding the voice button doesn't summon Siri; nothing happens. I can summon Siri via "Hey Siri" or by holding down the home button on the screen, but my preference is for the button to work, if possible.

I've searched extensively for a solution, even watching every "how to set up Zlink properly" video, but none of them demonstrate Siri being summoned by the steering wheel button.

I'm wondering if it's not possible to summon Siri via a long press of the voice button on the steering wheel. I'm a bit frustrated because this issue is preventing an otherwise perfect experience. Thank you in advance for any help or insights you can provide.
[Android Head-Units] mountainhawk82:
Bump!
[Magisk] arkzok:
So everything was going well. I finally managed to unlock bootloader, I flashed patched boot.img. Everything was working perfect, with the latest updates. Then, out of curiosity I decided to check how well does "Reboot to Recovery" function in Magisk work. Pressed it, my phone powered off. Nothing was happening. I tried to turn it back on by simply holding the power button - nothing. Power button + vol- -> nothing. Power button + vol+ -> Hurray! It showed the logo! It's fine! Orange State: your device will boot in five seconds. Five seconds pass -> it powers off again. I tried to connect it to my computer, it's not in fastboot, it's actually powered off. Tried connecting while in Orange State -> still nothing. I even tried to hold vol- and vol+ buttons while connecting it to my computer, and I actually got "OPLUS preloader connected" notifcation, but then it disconnected and could never connect this way again. Does anyone have any idea what can I do?
[Magisk] Barni25:
HI, i used to unbrick my hard bricked xiaomi redmi note 9 seven times, with this guide.

i skiped the 4th step, and it still worked for me beacuse my phone was full charged and i didn't have time to wait like 4 hours.

here is what is diferent for you:

2nd step: from here download the rom with the region you want(prefered to download the same)

7nd step: from here download the usb driver for SP FlashTool and download the mtk driver here, install both

you should be ready, it is almost the same process

I take no responsibility, I don't know if it works

don't ask me for drivers if these doesn't work
[Magisk] arkzok:
thank you, but i tried this and it can't help with my phone, i will send it to customer service
[Xiaomi Mix Fold 3] ShadyGame:
Hello,

During some search, i found this thread:

Guide to Unlock Additional LTE bands in Mido(India Specific)

Hi Folks, When in Xiaomi launched Redmi Note 4(Mido) in India, at that time Jio was one supporting 4G all over India, hence to cut cost on Licensing Xiaomi approached to Cut LTE band Support in Mido. It launched with support of Band 3, 5 & 40...

xdaforums.com

or this one:

Enable all available LTE-features on your Qualcomm device - MT-TECH.FI

This instruction helps you to enable all LTE-features on your Qualcomm devices like 1024QAM DL and 256QAM UL. Some features only supported only with SDX52 and SDX55 modems. Before continuing, I remind you these changes could end your device warranty. Be careful because this can make your device...

mt-tech.fi

does anyone know if this work in our device?

My phone is not rooted so i wasnt been able to try it
[Xiaomi Mix Fold 3] nmhusa:
Guide how to unlock bands and 5G on 700mhz

Hello. 5G network is comming soon . I make today method for unlock 5G on 700mhz for this device . Problematic is only icon od network because 5G network is visible as 4G (have only 4G icon , but work in 5G mode , speedtest say the same) . Unlock...

xdaforums.com

That post has 5g band unlocking
[Xiaomi Mix Fold 3] knives of ice:
I hope someone will try this. I've never seen 5G on mint/tmobile
[Xiaomi Mix Fold 3] thref23:
I'm on Mint.

Turn wifi off and make a phone call - your status bar will show 5G. At least, does for me.

I eventually realized that it shows LTE when I have 5G, and 5G when I have LTE.
[Xiaomi Mix Fold 3] knives of ice:
you are right it does do that, which is different than the fold 2. atrocious speeds regardless. nowhere close to what my wife's pixel gets on true 5g.

I am thinking of goign to the tmobile store to see if i get better reception/speeds as I read mint doesn't get to use all of tmobile's bands. not sure if it will matter or not but my mint contract is up in a few weeks so might as well try
[Xiaomi Mix Fold 3] thref23:
I had a Find N previously, same bands, tested speeds against employees at a T-Mo kiosk once. They were getting 200 down, I was getting like 30, same sims. Basically, we are missing the mmWave bands (fastest) and band 71 (most coverage in some locations) and, obviously, we can't take full advantage of aggregation.

That said, my "LTE" speeds on the Mix Fold are as good or better than on my Find N. In many if most locations I pull between 50-100, some locations are a bit worse others are a bit better. It's fine with me, personally. We do have band 41, which is the best blend of coverage and speed in many locations, I believe.

Ofc it'd be awesome if we could unlock more bands, I don't think it's possible but would love to be proven wrong.
[Xiaomi Mix Fold 3] knives of ice:
yeah...I would be totally happy with those speeds. I just wonder if it actually would be better on real tmobile instead of just using their towers with Mint. From what you posted it seems highly unlikely it would be any better
[Xiaomi Mix Fold 3] thref23:
Anyways, I installed LTE discovery to get more insight here. It does show NR NSA as "network override type," and it disappears if I switch to "LTE preferred" from "5G preferred." Interestingly, if I switch to LTE preferred, the status bar still shows LTE and not 5G as I would have guessed.

My understanding is that most phones display the 5G icon in the status bar when connected to NR/NSA - but NSA is actually an LTE connection coupled with an aggregated 5G band. So the LTE icon is not technically inaccurate. Google tells me that Band 71 is typically responsible for T-Mo's NR SA (standalone), but we don't have that band, so this all makes sense. (edit another possible issue is that, as of last year, T-Mo MVNOs such as Mint did not support NR SA, and I don't think this has changed)

I can't really confirm that my phone connects to 5G because LTE discovery (as well as the settings menu) displays "n/a" regarding the 5g band and signal strength, but from what I gather Android doesn't necessarily have an API to report those things. (edit Network Signal Guru confirms band 41, although the app is pretty annoying)

I'm still not sure why the icon switches to 5G on a phone call, but a little bit of research tells me that voice over NR (5G) is now a thing. So, we likely have VoNR, and maybe there is no aggregation when we are on a phone call.

I should stop caring, since my data speeds are really solid.
[Xiaomi Mix Fold 3] thref23:
Maybe an answer for you on this - Mint supports all the same bands as T-Mobile, but from what I can tell, it does not support NR SA (standalone 5G). NR SA is supposed to be (situationally) faster than NR NSA, which we get with Mint. It is effectively pure 5G, whereas NR NSA (which is still considered 5G) relies on LTE aggregated with a 5G band, or something.

T-Mo and Metro support standalone 5G, if you do get around to trying a T-Mo sim, I would be curious to know the results.

Though, I've also seen threads where T-Mo users complain that LTE coverage near them is much better than the 5G coverage, so SA can also backfire.
[Xiaomi Mix Fold 3] Prydateer:
I need band 20 for my provider. Anyone knows if the band unlocking will work for the Fold 3?
[General Questions and Answers] KeinName_exe:
Hi, i work in a small phone refurbisching Company and every time we must setup the Samsung phones to test them of all Theater functionalities. now i use a one Click Tool that Uses usb debugging in the *#0#* Interface from Samsung phones which was Programmed for frp unlocking.. ma question: is there any Tool Like that where i can Connect more that one Samsung phone at the same time and setup them with one Click? with the Tool which i use i Must Connect every Single Smartphone After and After…
[General Questions and Answers] xXx yYy:
Use a ADB-compatible powered USB hub to connect several Android phones with computer via ADB.

Once ADB is enabled on all of the Android phones, you can connect them to your computer using a USB cable. You can then use the ADB command line to interact with your Android phones.
[General Questions and Answers] KeinName_exe:
The Problem is i only can choose one from the phones… so i Must Write the Code for the First phone than press enter than for the second… i want to run the command on severeal phones at the same time. Is this possible?
[General Questions and Answers] xXx yYy:
Why don't carefully read? I clearly said "... connect several Android phones with computer via ADB". To clarify: Connect simultaneously.
[General Questions and Answers] KeinName_exe:
Okay, the Problem is the Programm i use requires to select a device from a List… ist Not this Programm what i use but it requires the Same… to choose a Port
[General Questions and Answers] xXx yYy:
OMG. Why not simply become familiar with adb devices command?

USB 2.0 hubs: can have up to 7 downstream ports.

USB 3.0 hubs: can have up to 15 downstream ports.

If 1 android device is connected then 1 device will be listed after running adb devices command

If 7 devices are connected then 7 devices will be listed after running adb devices command

If 15 devices are connected then 15 devices will be listed after running adb devices command
[General Questions and Answers] KeinName_exe:
I would use adb commands but it is an complicated program i think. I Must go to the *#0*# menu on the devices.. than the Programm sends a usb debugging Message and After 5 seconds i am at the Home Screen. If you can Tell me the commands for this process i would use it daily but I cant find it out by myself :(
[General Questions and Answers] xXx yYy:
IMO ADB is the easiest thing in the world. :)

You have to create a Windows batch script that applies an ADB command to multiple connected devices, e.g.

@echo off

REM Get a list of all connected devices
FOR /F "delims=" %%A IN ('adb devices') DO (

REM Apply the ADB command to the device
adb -s %%A %1

)
EXIT

where %1 should get replaced with the ADB command that you want to apply to all devices.
[General Questions and Answers] KeinName_exe:
Yes i know how i can create such a file the Problem is i dont know the adb command which the program sends to the phone. It has no log so i cant See what Commands the Programm Users in the background
[General Questions and Answers] KeinName_exe:
if I run the programm just this cmd windows popped up but it uses some commands for the program only. so i cant easily copy them and but them in a batch file or no?

View attachment 6023532
[General Questions and Answers] KeinName_exe:
Hi, i use a frp tool to setup samsung smartphones as fast as possible. not because tehre are frp locked but i need to skip the whole set-up process because it takes much time. i work in a small company and we need to check every device before sell or purchase them and to set-up every samsung smartphone by myself it just takes to much time. I want to use a third-party programm anymore because it uses just a few adb commands. the problem is this: the programm uses an exploit to enable the usb-debugging and adb mode in the samsung test menu (*#0*#). so the samsung is listed as an adb device after the exploit and i can run normally adb comments. my questions it how can i enable this mode by myself with a command without using the programm? id the adb mode is enabled i can continue the setup with a few adb comment lines but first it must be in the adb mode... i just loaded up the video file if you dont understand what i excactly want. thanks for your help ;)