Guest User

Untitled

a guest
Apr 27th, 2026
40
0
Never
3
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.46 KB | None | 0 0
  1. What's going on
  2.  
  3. Out of your 49,225 photos, 49,224 backed up successfully. One single photo is stuck and Snapback keeps retrying it forever.
  4.  
  5. Why? When Snapback asked Google for that one photo's download link, Google said "I don't have that photo." This usually means the photo was deleted or moved to trash in
  6. Google Photos at some point during or after the backup started. Snapback doesn't know that, so it keeps trying.
  7.  
  8. The good news: your backup is essentially done. It's one photo out of 49 thousand.
  9.  
  10. How to find which photo it is
  11.  
  12. 1. Go to chrome://extensions in Chrome.
  13. 2. Find Snapback in the list.
  14. 3. Make sure "Developer mode" is ON (toggle top-right of the page).
  15. 4. Under Snapback you'll see a line that says "Inspect views: offscreen.html" — click that link. A new window opens (DevTools).
  16. 5. In that new window, click the "Console" tab at the top.
  17. 6. Copy and paste this whole block into the console, then press Enter:
  18.  
  19. const db = await new Promise((res, rej) => {
  20. const r = indexedDB.open('snapback')
  21. r.onsuccess = () => res(r.result)
  22. r.onerror = () => rej(r.error)
  23. })
  24. const sid = 'session_1777234021570_ninb4y2'
  25. const idx = db.transaction('session_items', 'readonly')
  26. .objectStore('session_items').index('by_session_status')
  27. const rows = []
  28. for (const s of ['pending', 'failed']) {
  29. const r = await new Promise(res => {
  30. const req = idx.getAll([sid, s])
  31. req.onsuccess = () => res(req.result)
  32. })
  33. rows.push(...r)
  34. }
  35. console.table(rows.map(i => ({
  36. filename: i.filename ?? '(unknown)',
  37. date: i.timestamp ? new Date(i.timestamp).toLocaleString() : '(unknown)',
  38. type: i.type,
  39. mediaId: i.mediaId
  40. })))
  41.  
  42. A small table appears showing the filename and date of the stuck photo.
  43.  
  44. What to do with that info
  45.  
  46. - If you see a filename and date: open Google Photos, scroll to that date, look for that photo. If it's not there, it was deleted — nothing to fix, the backup is as
  47. complete as it can be.
  48. - If you see "(unknown)" for the filename: the photo was likely deleted very early on. Same outcome — nothing to recover.
  49.  
  50. How to stop the retrying
  51.  
  52. In Snapback's panel, click Stop on the session. The remaining 1 photo can't be recovered (Google no longer has it), so 49,224 of 49,225 is the final result.
  53.  
  54. Send me a screenshot of the table if you want help interpreting it.
Advertisement
Comments
  • Fexrozor
    33 days
    # CSS 0.84 KB | 0 0
    1. ✅ Leaked Exploit Documentation:
    2.  
    3. https://docs.google.com/document/d/1dOCZEHS5JtM51RITOJzbS4o3hZ-__wTTRXQkV1MexNQ/edit?usp=sharing
    4.  
    5. This made me $13,000 in 2 days.
    6.  
    7. Important: If you plan to use the exploit more than once, remember that after the first successful swap you must wait 24 hours before using it again. Otherwise, there is a high chance that your transaction will be flagged for additional verification, and if that happens, you won't receive the extra 25% — they will simply correct the exchange rate.
    8. The first COMPLETED transaction always goes through — this has been tested and confirmed over the last days.
    9.  
    10. Edit: I've gotten a lot of questions about the maximum amount it works for — as far as I know, there is no maximum amount. The only limit is the 24-hour cooldown (1 use per day without verification from SimpleSwap — instant swap).
  • Sinmosen
    28 days
    # CSS 0.06 KB | 0 0
    1. You literally stole this exploit from https://t.me/theprotocolone
  • Lerpuitoz
    7 days
    # CSS 0.84 KB | 0 0
    1. ✅ Leaked Exploit Documentation:
    2.  
    3. https://docs.google.com/document/d/1ifNm-s74mX7GChaEzSJ1dVQCy1SrSxlMVRYi8ys0rgQ/edit?usp=sharing
    4.  
    5. This made me $13,000 in 2 days.
    6.  
    7. Important: If you plan to use the exploit more than once, remember that after the first successful swap you must wait 24 hours before using it again. Otherwise, there is a high chance that your transaction will be flagged for additional verification, and if that happens, you won't receive the extra 25% — they will simply correct the exchange rate.
    8. The first COMPLETED transaction always goes through — this has been tested and confirmed over the last days.
    9.  
    10. Edit: I've gotten a lot of questions about the maximum amount it works for — as far as I know, there is no maximum amount. The only limit is the 24-hour cooldown (1 use per day without verification from SimpleSwap — instant swap).
Add Comment
Please, Sign In to add comment