<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Google Pixel Has Been Beaten! in Get Support</title>
    <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Google-Pixel-Has-Been-Beaten/m-p/80873#M31079</link>
    <description>&lt;P&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/4837"&gt;@imm1304﻿&lt;/a&gt;&amp;nbsp;only 2 confirmed incompatibilities are for Pokemon Go and Google Pay&lt;/P&gt;&lt;P&gt;Everything else seems to work&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 30 Oct 2016 20:09:55 GMT</pubDate>
    <dc:creator>kav2001c</dc:creator>
    <dc:date>2016-10-30T20:09:55Z</dc:date>
    <item>
      <title>Google Pixel Has Been Beaten!</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Google-Pixel-Has-Been-Beaten/m-p/80667#M31077</link>
      <description>&lt;P&gt;Ok so maybe from other thread I was too pessimistic. A very loyal fanbase worked hard on doing what many thought could not be done.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://twitter.com/ChainfireXDA/status/791748015925161984" target="_blank" rel="noopener"&gt;https://twitter.com/ChainfireXDA/status/791748015925161984&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just remember messing with Verizon bootloader will most likely void any warranty through Verizon&amp;nbsp;&lt;IMG id="catwink" class="emoticon emoticon-catwink" src="https://productioncommunity.publicmobile.ca/i/smilies/16x16_cat-wink.png" alt="Cat Wink" title="Cat Wink" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="http://theroot.ninja/dePixel8" target="_blank" rel="noopener"&gt;http://theroot.ninja/dePixel8&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pix" style="width: 300px;"&gt;&lt;img src="https://productioncommunity.publicmobile.ca/t5/image/serverpage/image-id/2601i8BCDCFBF21326A6C/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Pix" alt="Pix" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 18:05:18 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/Google-Pixel-Has-Been-Beaten/m-p/80667#M31077</guid>
      <dc:creator>kav2001c</dc:creator>
      <dc:date>2022-01-04T18:05:18Z</dc:date>
    </item>
    <item>
      <title>Re: Google Pixel Has Been Beaten!</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Google-Pixel-Has-Been-Beaten/m-p/80670#M31078</link>
      <description>&lt;P&gt;This is great news. &amp;nbsp;Its systemless root so we can make it play nice with Google Safetynet too. &amp;nbsp;&lt;/P&gt;&lt;P&gt;Great phone, but as a true PM'er, I will look out for a great deal before I buy it &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 30 Oct 2016 15:34:33 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/Google-Pixel-Has-Been-Beaten/m-p/80670#M31078</guid>
      <dc:creator>imm1304</dc:creator>
      <dc:date>2016-10-30T15:34:33Z</dc:date>
    </item>
    <item>
      <title>Re: Google Pixel Has Been Beaten!</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Google-Pixel-Has-Been-Beaten/m-p/80873#M31079</link>
      <description>&lt;P&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/4837"&gt;@imm1304﻿&lt;/a&gt;&amp;nbsp;only 2 confirmed incompatibilities are for Pokemon Go and Google Pay&lt;/P&gt;&lt;P&gt;Everything else seems to work&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 30 Oct 2016 20:09:55 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/Google-Pixel-Has-Been-Beaten/m-p/80873#M31079</guid>
      <dc:creator>kav2001c</dc:creator>
      <dc:date>2016-10-30T20:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: Google Pixel Has Been Beaten!</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Google-Pixel-Has-Been-Beaten/m-p/80929#M31080</link>
      <description>&lt;P&gt;&lt;U&gt;&lt;A href="http://www.xda-developers.com/" target="_self"&gt;XDA Developers&lt;/A&gt;&lt;/U&gt; has been the authority since long before smartphones, lol, but welcome to the club!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No device is ever "impossible" to root. &amp;nbsp;No lockout or tamperproofing is ever "impossible" to circumvent or neutralize. &amp;nbsp;No encryption method is ever "impossible" to break.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It does take some time to decipher all the JTAG boundaries and spoof opcodes, to bypass lockout or DRM circuitry on the mainboard, to successfully interface embedded SMD logic/storage chips with external debugger/programmer hardwares, or to just crunch and brute all the hard number permutations on a bunch of computers. &amp;nbsp;In absolute worst-case situations, the software can be extracted (and duplicated, then modified) by methodically exposing and examining the nano-scale circuit lithography under extreme magnification. &amp;nbsp;(Note that expert hackers can exploit all the same approaches and tools that are used by teardown engineers and by forensic data recovery experts.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And many consumer devices simply aren't popular, capable, or interesting enough to motivate such time-consuming efforts.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fortunately for us, there's always serious hacker prestige attached to the first person(s) able to thoroughly pwn a new device, especially whenever an "evil faceless profit-grubbing corporation" throws down the gauntlet by proudly boasting their new DRM technology (whatever it is) is somehow "completely secure and ultimately, utterly unbreakable".&lt;/P&gt;</description>
      <pubDate>Sun, 30 Oct 2016 23:27:45 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/Google-Pixel-Has-Been-Beaten/m-p/80929#M31080</guid>
      <dc:creator>Korth</dc:creator>
      <dc:date>2016-10-30T23:27:45Z</dc:date>
    </item>
    <item>
      <title>Re: Google Pixel Has Been Beaten!</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Google-Pixel-Has-Been-Beaten/m-p/80995#M31081</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/2265"&gt;@kav2001c&lt;/a&gt; wrote:&lt;BR /&gt;&lt;P&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/4837"&gt;@imm1304&lt;/a&gt;&amp;nbsp;only 2 confirmed incompatibilities are for Pokemon Go and Google Pay&lt;/P&gt;&lt;P&gt;Everything else seems to work&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yeah, bloody Pokemon GO has made it insanely annoying for those of who want to root for the added power it gives.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Oct 2016 02:48:50 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/Google-Pixel-Has-Been-Beaten/m-p/80995#M31081</guid>
      <dc:creator>WearySky</dc:creator>
      <dc:date>2016-10-31T02:48:50Z</dc:date>
    </item>
  </channel>
</rss>

