![\"Unlock](\"https:\/\/www.newsbeep.com\/us\/wp-content\/uploads\/2025\/10\/Unlock-Bootloader.jpg\"\/ "\\"Unlock")
<\/p>\n<\/p>\n
C. Scott Brown \/ Android Authority<\/p>\n
TL;DR<\/p>\n
Unlocking your phone\u2019s bootloader has long meant the risk of losing access to certain software features.
\nIn support documents, Google now confirms that Gemini Nano does not work on devices with unlocked bootloaders.<\/p>\n
If you consider yourself any kind of Android enthusiast, at some point along the line you\u2019ve probably pushed your phone a little beyond what normal users do with it. Maybe that means accessing Developer Options<\/a>, acquiring root<\/a>, or unlocking your handset\u2019s bootloader<\/a>. And while those can be powerful tools, taking your phone in this direction also means accepting the risk that you might break a few things along the way. Today we\u2019re shining a spotlight on one in particular: losing access to Gemini Nano<\/a>.<\/p>\n Don\u2019t want to miss the best from Android Authority?<\/p>\n This compact version of Gemini is exactly as useful as it is because it\u2019s optimized enough to actually run locally on our phones. But while Google lets us run Gemini Nano on mainstream Android devices, don\u2019t expect Gemini Nano to play nicely if you start fiddling with your phone, as AssembleDebug<\/a> discusses today on his blog.<\/p>\n If you\u2019ve already been playing around with Gemini Nano on a handset you use for development, this is probably nothing new to you. That said, we always like it when we can see a Google policy clearly spelled out, and that\u2019s exactly what we\u2019re now getting by way of the documentation for ML Kit\u2019s GenAI Summarization API<\/a>. There, Google explains why you might see a \u201cFEATURE_NOT_FOUND\u201d message:<\/p>\n Note that if the device\u2019s bootloader is unlocked, you\u2019ll also see this error\u2014this API does not support devices with unlocked bootloaders.<\/p>\n Phones have been intentionally disabling certain functionality when they detect an unlocked bootloader<\/a> for ages \u2014 presumably to interfere with debugging and limiting what a potential adversary could learn about the software. A decade back, for instance, Sony<\/a> was disabling some of its camera post-processing on Xperia phones with unlocked bootloaders.<\/p>\n As a result, there\u2019s nothing super controversial about the fact that Google\u2019s doing this with Gemini Nano, and by this point, if you were going to be affected by this restriction, you\u2019ve probably already run up across it. But for those of us who are maybe more curious about the inner workings of Android than necessarily compelled to try messing with it all for ourselves: Consider yourself informed.<\/p>\n![\"google](\"https:\/\/www.newsbeep.com\/us\/wp-content\/uploads\/2025\/09\/google_preferred_source_badge_light@2x.png\"\/ "\\"google"){kind=icon}
![\"google](\"https:\/\/www.newsbeep.com\/us\/wp-content\/uploads\/2025\/09\/google_preferred_source_badge_dark@2x.png\"\/ "\\"google"){kind=icon}
<\/a><\/p>\n