4 ms·

The QR code you scan is stored in app's db, you can use generic scanner to get the code and save it on paper or another encrypted DB or extract them from the Go

The QR code you scan is stored in app's db, you can use generic scanner to get the code and save it on paper or another encrypted DB or extract them from the Google Auth app SQL DB - if you have root access.

AdmiralAsshat 7y ago
Good luck getting root access on a US Snapdragon Samsung phone. IIRC, they physically damage themselves in some way if they detect that they've been rooted, which then caps the battery from ever going beyond 70 or 80%.
- nrclark 7y ago
  I'm interested to read more about this, do you have a source for it? That seems like it would be just asking for a world of warranty returns and support nightmares for whatever company built it into their phones.
  - AdmiralAsshat 7y ago
    Here's the only quick source I could find about the battery being capped while rooted: https://www.xda-developers.com/sampwnd-root-galaxy-s8-snapdragon/ https://www.xda-developers.com/sampwnd-root-galaxy-s8-snapdr... I'm pretty sure this was implemented across their phones after the Galaxy Note 7 debacle. I think the idea was that anyone who tried to root their devices and avoid Samsung remotely deactivating them would at least be prevented from charging the battery to full, which could cause the battery swelling/overheating/fire-catching problem. I'll have to do more digging on the quote I remember about Samsung phones physically blowing a circuit somewhere if they detect they've been rooted.
    - XMPPwocky 7y ago
      > I'll have to do more digging on the quote I remember about Samsung phones physically blowing a circuit somewhere if they detect they've been rooted. This sounds like the ODIN QFuse. These aren't really particularly dramatic- they're tiny, microscopic "fuses", designed to blow cleanly and easily. Most devices have plenty of them- used to lock the devices down after manufacturing.
      - Wowfunhappy 7y ago
        Blowing one of those fuses because a device thinks it has been rooted is pretty extreme though, no? (If this is in fact happening.)
    - nrclark 7y ago
      To follow up on this (in case you see ever see this comment) - I don't think that the linked article suggests that rooting the phone -permanently- damages anything. To me, that reads more like "the phone's bootloader checks to see whether it's booting a signed kernel. If not, it tells the battery controller to limit charging capacity until the next boot." In this particular case, it was probably a safety thing on that particular phone. I bet that Samsung pushed it in a firmware update because of their "batteries catch fire" issue, which was fixed with some patches to the kernel driver. Chances are this was intended to make sure that somebody running an unsigned/homebrew kernel (which might or might not have the patched charge-controller drivers) wouldn't be able to make their battery catch fire.
- NikolaeVarius 7y ago
  Source
- deleted 7y ago
  [deleted]
arsome 7y ago
TitaniumBackup does the job quite nicely if you're rooted, transferred codes through 4+ phones so far.

AdmiralAsshat 7y ago

Good luck getting root access on a US Snapdragon Samsung phone. IIRC, they physically damage themselves in some way if they detect that they've been rooted, which then caps the battery from ever going beyond 70 or 80%.

nrclark 7y ago
I'm interested to read more about this, do you have a source for it? That seems like it would be just asking for a world of warranty returns and support nightmares for whatever company built it into their phones.
- AdmiralAsshat 7y ago
  Here's the only quick source I could find about the battery being capped while rooted: https://www.xda-developers.com/sampwnd-root-galaxy-s8-snapdragon/ https://www.xda-developers.com/sampwnd-root-galaxy-s8-snapdr... I'm pretty sure this was implemented across their phones after the Galaxy Note 7 debacle. I think the idea was that anyone who tried to root their devices and avoid Samsung remotely deactivating them would at least be prevented from charging the battery to full, which could cause the battery swelling/overheating/fire-catching problem. I'll have to do more digging on the quote I remember about Samsung phones physically blowing a circuit somewhere if they detect they've been rooted.
  - XMPPwocky 7y ago
    > I'll have to do more digging on the quote I remember about Samsung phones physically blowing a circuit somewhere if they detect they've been rooted. This sounds like the ODIN QFuse. These aren't really particularly dramatic- they're tiny, microscopic "fuses", designed to blow cleanly and easily. Most devices have plenty of them- used to lock the devices down after manufacturing.
    - Wowfunhappy 7y ago
      Blowing one of those fuses because a device thinks it has been rooted is pretty extreme though, no? (If this is in fact happening.)
  - nrclark 7y ago
    To follow up on this (in case you see ever see this comment) - I don't think that the linked article suggests that rooting the phone -permanently- damages anything. To me, that reads more like "the phone's bootloader checks to see whether it's booting a signed kernel. If not, it tells the battery controller to limit charging capacity until the next boot." In this particular case, it was probably a safety thing on that particular phone. I bet that Samsung pushed it in a firmware update because of their "batteries catch fire" issue, which was fixed with some patches to the kernel driver. Chances are this was intended to make sure that somebody running an unsigned/homebrew kernel (which might or might not have the patched charge-controller drivers) wouldn't be able to make their battery catch fire.
NikolaeVarius 7y ago
Source
deleted 7y ago
[deleted]

arsome 7y ago

TitaniumBackup does the job quite nicely if you're rooted, transferred codes through 4+ phones so far.