What's up! We have some bad
The Pixel 10 devices (excluding the 10a) are getting a bootloader update in one of the future Android releases that increments the anti-rollback version for the bootloader.
This means that, after upgrading, you won't be able to downgrade to a lower version of Android. You might need to sideload a full OTA image again to avoid bricking in certain situations.
By the way, we're working on Pixel 11 leaks and a chemical element (13), stay tuned!
The Pixel 10 devices (excluding the 10a) are getting a bootloader update in one of the future Android releases that increments the anti-rollback version for the bootloader.
This means that, after upgrading, you won't be able to downgrade to a lower version of Android. You might need to sideload a full OTA image again to avoid bricking in certain situations.
❤59😢40🔥7😁6😱6
Mystic Leaks
👀✨
Let's play a game.
If this post reaches 500 likes within the next 2 hours, we will drop ALOS wallpapers today
If this post reaches 500 likes within the next 2 hours, we will drop ALOS wallpapers today
❤312👍122🤡29🔥16👎10
Mystic Leaks
Let's play a game. If this post reaches 500 likes within the next 2 hours, we will drop ALOS wallpapers today
AluminiumOS_Wallpapers_MysticLeaks.zip
130.9 MB
❤87🔥25👍2👎2
This isn't a leak, but...
BREAKING: Nekogram is secretly sending your phone numbers to the developer
The backdoor is hidden in the http://Extra.java
file, which differs from the template uploaded to the repository. The obfuscated code sends data as an inline request to the @nekonotificationbot, leaving no trace.
More info about the backdoor: https://github.com/Nekogram/Nekogram/issues/336 (locked by Nekogram devs)
To validate this, we made a PoC: an LSPosed module that replaces the bot ID and username to ours so all requests are going to it. That way, we confirmed that the phone numbers are being collected. Every. Login.
The PoC is available here: https://github.com/RomashkaTea/nekogram-proof-of-logging
What should you do?
1. Report the app on Play Store: https://play.google.com/store/apps/details?id=tw.nekomimi.nekogram
2. Report the repository on GitHub: https://github.com/Nekogram/Nekogram
3. Delete the app and stop using unofficial Telegram clients
BREAKING: Nekogram is secretly sending your phone numbers to the developer
The backdoor is hidden in the http://Extra.java
file, which differs from the template uploaded to the repository. The obfuscated code sends data as an inline request to the @nekonotificationbot, leaving no trace.
More info about the backdoor: https://github.com/Nekogram/Nekogram/issues/336 (locked by Nekogram devs)
To validate this, we made a PoC: an LSPosed module that replaces the bot ID and username to ours so all requests are going to it. That way, we confirmed that the phone numbers are being collected. Every. Login.
The PoC is available here: https://github.com/RomashkaTea/nekogram-proof-of-logging
What should you do?
1. Report the app on Play Store: https://play.google.com/store/apps/details?id=tw.nekomimi.nekogram
2. Report the repository on GitHub: https://github.com/Nekogram/Nekogram
3. Delete the app and stop using unofficial Telegram clients
😱188❤27👍17😢8👎4
Mystic Leaks
This isn't a leak, but... BREAKING: Nekogram is secretly sending your phone numbers to the developer The backdoor is hidden in the http://Extra.java file, which differs from the template uploaded to the repository. The obfuscated code sends data as an inline…
The Nekogram devs have admitted this!
🤡284😱13😢7👍5👎5
Hey.. It’s been too long actually..
We know we promised you something, and here we’re starting with the full-quality Pixel 11 Pro Fold wallpapers, including dark and animated versions:
• Midnight - Lunar Tides
• Pine - Tidal Swirl
Let us know what you think in the comment section!
We know we promised you something, and here we’re starting with the full-quality Pixel 11 Pro Fold wallpapers, including dark and animated versions:
• Midnight - Lunar Tides
• Pine - Tidal Swirl
Let us know what you think in the comment section!
❤87🔥25👍5😁1
Hey! We've been hinting at these for a while now... but it's time to drop the nuke ☢️🔥
Here, you'll find all the information we are currently aware of regarding the upcoming Pixel 11 (P26) lineup, including some news that might surprise you 👀
Without any further ado, let's jump into it:
━━━
📋 General P26 (Pixel 2026) Infos:
🔹 SoC — Tensor G6 (Malibu)
└ Built on TSMC N2 node
• 1× ARM C1-Ultra @ 4.11 GHz
• 4× ARM C1-Pro @ 3.38 GHz
• 2× ARM C1-Pro @ 2.65 GHz
🔹 GSC — Titan M3 (Epic)
🔹 GPU — PowerVR C-Series CXTP-48-1536
🔹 Modem — MediaTek M90 (MT6986D)
🔹 New TPU — Codename: Santafe
🔹 New GXP — Codename: Metis
━━━
📱 Pixel 11 (Cubs):
🔸 SKUs: GPQQ7 (MMW) / GUJ0N (ROW) / GV9X7 (JPN)
🔸 Colors: BLK (Black), GRN (Green), PNK (Pink), PPL (Purple)
🔸 RAM: 8 (?) / 12 GB
🔸 Display: 6.3" OLED, 1080×2424, 60–120 Hz, 240 Hz PWM, up to 2000 nits (HDR), up to 3100 nits (peak brightness)
🔸 Battery: 4840 mAh (minimal capacity)
🔸 Camera: New main — sensor: chemosh, lens: vesta — very likely 50 MP!
━━━
📱 Pixel 11 Pro (Grizzly):
🔸 SKUs: G7SWN (MMW) / GM45K (ROW) / G9W5D (JPN)
🔸 RAM: 12 / 16 GB (two different SKUs)
🔸 Display: 6.3" OLED, 1280×2856, 1–120 Hz, 240 Hz PWM, up to 2450 nits (HDR), up to 3600 nits (peak brightness)
🔸 Battery: 4707 mAh (minimal capacity)
🔸 Camera: New main (bastet / vesta) + new telephoto (barghest / chonky)
━━━
📱 Pixel 11 Pro XL (Kodiak):
🔸 SKUs: GBC0H (MMW) / G4HCD (ROW) / GER5L (JP)
🔸 RAM: 12 / 16 GB (two different SKUs)
🔸 Display: 6.8" OLED, 1344×2992, 1–120 Hz, 240 Hz PWM, up to 2450 nits (HDR), up to 3600 nits (peak brightness)
🔸 Battery: 5000 mAh (minimal capacity)
🔸 Camera: New main (bastet / vesta) + new telephoto (barghest / chonky)
━━━
📱 Pixel 11 Pro Fold (Yogi):
🔸 SKUs: GZDQ6 (MMW) / GM2SN (JPN)
🔸 RAM: 12 / 16 GB
🔸 Inner Display: 2076×2160 OLED, 1–120 Hz, up to 2050 nits (HDR), up to 3500 nits (peak brightness)
🔸 Outer Display: 1080×2342 OLED, 60–120 Hz, up to 2450 nits (HDR), up to 3600 nits (peak brightness)
🔸 Battery: 4658 mAh (minimal capacity)
🔸 Camera: New main (chemosh) lens
━━━
✨ And... one more thing! Or two, perhaps...
1️⃣ Both the 11 Pro and the Pro XL, as well as the 11 Pro Fold, won't feature a thermometer (RIP 🥀). Instead, all of them will spot an RGB LED array in the camera bar — somewhat similar to Nothing's Glyph, but smaller.
2️⃣ Despite previous claims, Project Toscana (IR Face Unlock) likely won't debut on the P26 lineup, as it's simply still not ready for release.
P.S: The attached image is AI Generated, but it resembles the actual look of the Pixel 11 Pro's back cover
Do you think Google cooked with this one? Or is it below your expectations?
Let us know down below!
Here, you'll find all the information we are currently aware of regarding the upcoming Pixel 11 (P26) lineup, including some news that might surprise you 👀
Without any further ado, let's jump into it:
━━━
📋 General P26 (Pixel 2026) Infos:
🔹 SoC — Tensor G6 (Malibu)
└ Built on TSMC N2 node
• 1× ARM C1-Ultra @ 4.11 GHz
• 4× ARM C1-Pro @ 3.38 GHz
• 2× ARM C1-Pro @ 2.65 GHz
🔹 GSC — Titan M3 (Epic)
🔹 GPU — PowerVR C-Series CXTP-48-1536
🔹 Modem — MediaTek M90 (MT6986D)
🔹 New TPU — Codename: Santafe
🔹 New GXP — Codename: Metis
━━━
📱 Pixel 11 (Cubs):
🔸 SKUs: GPQQ7 (MMW) / GUJ0N (ROW) / GV9X7 (JPN)
🔸 Colors: BLK (Black), GRN (Green), PNK (Pink), PPL (Purple)
🔸 RAM: 8 (?) / 12 GB
🔸 Display: 6.3" OLED, 1080×2424, 60–120 Hz, 240 Hz PWM, up to 2000 nits (HDR), up to 3100 nits (peak brightness)
🔸 Battery: 4840 mAh (minimal capacity)
🔸 Camera: New main — sensor: chemosh, lens: vesta — very likely 50 MP!
━━━
📱 Pixel 11 Pro (Grizzly):
🔸 SKUs: G7SWN (MMW) / GM45K (ROW) / G9W5D (JPN)
🔸 RAM: 12 / 16 GB (two different SKUs)
🔸 Display: 6.3" OLED, 1280×2856, 1–120 Hz, 240 Hz PWM, up to 2450 nits (HDR), up to 3600 nits (peak brightness)
🔸 Battery: 4707 mAh (minimal capacity)
🔸 Camera: New main (bastet / vesta) + new telephoto (barghest / chonky)
━━━
📱 Pixel 11 Pro XL (Kodiak):
🔸 SKUs: GBC0H (MMW) / G4HCD (ROW) / GER5L (JP)
🔸 RAM: 12 / 16 GB (two different SKUs)
🔸 Display: 6.8" OLED, 1344×2992, 1–120 Hz, 240 Hz PWM, up to 2450 nits (HDR), up to 3600 nits (peak brightness)
🔸 Battery: 5000 mAh (minimal capacity)
🔸 Camera: New main (bastet / vesta) + new telephoto (barghest / chonky)
━━━
📱 Pixel 11 Pro Fold (Yogi):
🔸 SKUs: GZDQ6 (MMW) / GM2SN (JPN)
🔸 RAM: 12 / 16 GB
🔸 Inner Display: 2076×2160 OLED, 1–120 Hz, up to 2050 nits (HDR), up to 3500 nits (peak brightness)
🔸 Outer Display: 1080×2342 OLED, 60–120 Hz, up to 2450 nits (HDR), up to 3600 nits (peak brightness)
🔸 Battery: 4658 mAh (minimal capacity)
🔸 Camera: New main (chemosh) lens
━━━
✨ And... one more thing! Or two, perhaps...
1️⃣ Both the 11 Pro and the Pro XL, as well as the 11 Pro Fold, won't feature a thermometer (RIP 🥀). Instead, all of them will spot an RGB LED array in the camera bar — somewhat similar to Nothing's Glyph, but smaller.
2️⃣ Despite previous claims, Project Toscana (IR Face Unlock) likely won't debut on the P26 lineup, as it's simply still not ready for release.
P.S: The attached image is AI Generated, but it resembles the actual look of the Pixel 11 Pro's back cover
Do you think Google cooked with this one? Or is it below your expectations?
Let us know down below!
👍89🔥42👎31❤28😁4
Mystic Leaks
What's up! We have some bad news for you... The Pixel 10 devices (excluding the 10a) are getting a bootloader update in one of the future Android releases that increments the anti-rollback version for the bootloader. This means that, after upgrading, you…
Hey.. we need to talk..
The May 2026 update has been released today! As we’ve leaked before, this update includes a bootloader update for the Pixel 10 series that increments the anti-rollback counter, preventing from downgrading to a vulnerable version of the bootloader.
While we’re out here warning you, there’s a big brick issue that Google refuses to address publicly: b/507968853
As many of you developers know, once a Pixel enters one of these recovery modes:
Pixel ROM Recovery (Pixel 6-8 series)
Pixel BL1 Recovery (Pixel 9 series)
Pixel DBL Recovery (Pixel 10+ series)
The Pixel becomes a paperweight.
We know that Googlers have an internal tool (go/flash/tools/pixel/rom_recovery) and signed recovery images (signed/signed-recovery.zip) to recover a device from such mode.
However, external users don’t have them. Every complaint about that on the Issue Tracker gets a Won’t Fix or a Duplicate of x status.
The primary issue (b/402455330) hasn’t gotten an answer from Google since April 2025.
The continued silence makes it look like the company doesn’t care about its users. The problem has been raised for years. Yet there’s still no public statement.
Everything's changed when a developer (JoshuaDoes) has released a tool called tensor-usbdl that can work with a device stuck in Pixel ROM Recovery mode.
The catch?
- Currently, the tool only has the leaked recovery signed images for the Pixel 7 / Pixel 7 Pro and the Pixel 8 / 8 Pro.
- The Pixel 8 images only work if you have never updated your phone to the May 2025 update. If you did, well you’re locked out for now.
The fact that an independent developer made such a tool proves that Google could do something about this but they won’t, meanwhile no one we know of has taken advantage of it to break the device security.
What do you think about this? Have you ever bricked a Pixel? Let us know in the comment section!
By the way regarding the leaks, we know and we're dropping another bomb soon so stay tuned
The May 2026 update has been released today! As we’ve leaked before, this update includes a bootloader update for the Pixel 10 series that increments the anti-rollback counter, preventing from downgrading to a vulnerable version of the bootloader.
While we’re out here warning you, there’s a big brick issue that Google refuses to address publicly: b/507968853
As many of you developers know, once a Pixel enters one of these recovery modes:
Pixel ROM Recovery (Pixel 6-8 series)
Pixel BL1 Recovery (Pixel 9 series)
Pixel DBL Recovery (Pixel 10+ series)
The Pixel becomes a paperweight.
We know that Googlers have an internal tool (go/flash/tools/pixel/rom_recovery) and signed recovery images (signed/signed-recovery.zip) to recover a device from such mode.
However, external users don’t have them. Every complaint about that on the Issue Tracker gets a Won’t Fix or a Duplicate of x status.
The primary issue (b/402455330) hasn’t gotten an answer from Google since April 2025.
The continued silence makes it look like the company doesn’t care about its users. The problem has been raised for years. Yet there’s still no public statement.
Everything's changed when a developer (JoshuaDoes) has released a tool called tensor-usbdl that can work with a device stuck in Pixel ROM Recovery mode.
The catch?
- Currently, the tool only has the leaked recovery signed images for the Pixel 7 / Pixel 7 Pro and the Pixel 8 / 8 Pro.
- The Pixel 8 images only work if you have never updated your phone to the May 2025 update. If you did, well you’re locked out for now.
The fact that an independent developer made such a tool proves that Google could do something about this but they won’t, meanwhile no one we know of has taken advantage of it to break the device security.
What do you think about this? Have you ever bricked a Pixel? Let us know in the comment section!
❤94😢25😱16👍12🎉3
Media is too big
VIEW IN TELEGRAM
Oh my... Google finally listened 😭🙏
Well, we are just as shocked as you are, and honestly, we can't believe it either... but Google is finally adopting a long-requested feature from its user base.
We are talking about the ability to remove and customize the infamous Google Search Bar on the home screen.
Previous hints of this feature were already discovered in the Android 17 QPR1 Beta 2 code, but today we are showcasing how it has actually been implemented and what it will look like in the QPR1 stable release.
By accessing the home screen settings, you'll be greeted by a new "Search bar settings" sub-menu, which will let you disable or enable the feature. When enabled, you'll be able to completely customize the look of the bar, from the hue and saturation to the shortcut.
For a visual reference, we've attached a short video clip.
What do you think about this new addition?
Does it meaningfully improve your Pixel user experience or is it just a small gimmick?
Let us know down below!
Well, we are just as shocked as you are, and honestly, we can't believe it either... but Google is finally adopting a long-requested feature from its user base.
We are talking about the ability to remove and customize the infamous Google Search Bar on the home screen.
Previous hints of this feature were already discovered in the Android 17 QPR1 Beta 2 code, but today we are showcasing how it has actually been implemented and what it will look like in the QPR1 stable release.
By accessing the home screen settings, you'll be greeted by a new "Search bar settings" sub-menu, which will let you disable or enable the feature. When enabled, you'll be able to completely customize the look of the bar, from the hue and saturation to the shortcut.
For a visual reference, we've attached a short video clip.
What do you think about this new addition?
Does it meaningfully improve your Pixel user experience or is it just a small gimmick?
Let us know down below!
❤191🎉50🔥13👍10👏7
With big screens comes great expectations... maybe? 💻✨
Ahead of today's Google IO 2026 event, the overall expectations are quite high. So far, all we can do is wait a little longer and see what Google’s got up its sleeve.
But based on previous statements and rumors, Big G might finally give us a first glimpse of its upcoming Desktop OS, the one set to replace ChromeOS (possibly as early as late 2026): AluminiumOS, also known as Android Desktop.
As we've promised a while back, we have some juicy informations for you, and now we're here to deliver: By clicking right here, you can take a look at how the OS is going to look like... and yes, this is all running on a MacBook Pro through UTM... ironic, isn't it?
Now, let’s be honest: Google’s ALOS is no secret. It’s essentially plain Android, but with most of the desktop-experience quirks you’d expect, including:
•Desktop folders
•Virtual desktops
•An optimized Quick Settings & notifications panel
•Touchpad & keyboard gestures and shortcuts
•Certain optimized apps (like the task manager)
•A solid ecosystem between your laptop and mobile devices, including Apple ones, through "Link to iOS"
However... here comes the delusional part:
As of now, that’s pretty much it. The current state of ALOS feels closer to a slightly pimped version of Samsung DeX than to an actual desktop-class OS, with its biggest shortcomings being the absolutely non-existent selection of mouse & keyboard optimized apps (even most of the Google apps you see are just web versions wrapped in a window!), plus the limited hardware it’ll run on (cause let's be honest, Snapdragon X chips aren't nearly as good as Apple's M series)
Still, we’re keeping our fingers crossed for some good news from Google this evening
Do you think ALOS has a bright future ahead? Or is it destined for the infamous "Killed by Google" graveyard sooner rather than later?
Let us know down below!
Ahead of today's Google IO 2026 event, the overall expectations are quite high. So far, all we can do is wait a little longer and see what Google’s got up its sleeve.
But based on previous statements and rumors, Big G might finally give us a first glimpse of its upcoming Desktop OS, the one set to replace ChromeOS (possibly as early as late 2026): AluminiumOS, also known as Android Desktop.
As we've promised a while back, we have some juicy informations for you, and now we're here to deliver: By clicking right here, you can take a look at how the OS is going to look like... and yes, this is all running on a MacBook Pro through UTM... ironic, isn't it?
Now, let’s be honest: Google’s ALOS is no secret. It’s essentially plain Android, but with most of the desktop-experience quirks you’d expect, including:
•Desktop folders
•Virtual desktops
•An optimized Quick Settings & notifications panel
•Touchpad & keyboard gestures and shortcuts
•Certain optimized apps (like the task manager)
•A solid ecosystem between your laptop and mobile devices, including Apple ones, through "Link to iOS"
However... here comes the delusional part:
As of now, that’s pretty much it. The current state of ALOS feels closer to a slightly pimped version of Samsung DeX than to an actual desktop-class OS, with its biggest shortcomings being the absolutely non-existent selection of mouse & keyboard optimized apps (even most of the Google apps you see are just web versions wrapped in a window!), plus the limited hardware it’ll run on (cause let's be honest, Snapdragon X chips aren't nearly as good as Apple's M series)
Still, we’re keeping our fingers crossed for some good news from Google this evening
Do you think ALOS has a bright future ahead? Or is it destined for the infamous "Killed by Google" graveyard sooner rather than later?
Let us know down below!
❤100🔥22👍13🤡3👎1