[E 2015 Q&A, Help & Troubleshooting] Nsomnia:
I had a, basically dead other than it will show up in USBdeview under some drivers including as of currenbt, the offical Motor adb/fastboot driver, surnia (moto e lte) for a while and loved it, rooted and such. The screen got broken at the top but still totally fine until I did something in a drunken state and it wouldnt power up. I put this to its finiky usb port and the charger at the time.

Fast forward to today I got a new S9 (dumb buy, gonna sell and get a oneplus instead but anyway) but wanna get any data I had (was big into crypto before it got big when usingf this device and titaniumbackup backup files I have found show some apps were used for wallets and the doable mobile mining back in the day).

A couple months ago I could get the backlight to light up and thats it, sometimes the power LED would flash intermittely and i bleive it stayed on for ~5 seconds a few times.

I got frustrated and carefully fried the screen off under heat and the internals are well built but you can see rust and thus likely water damage.

Now my computer and especailly android/rooting skills these days are very weak compared to 2018 when it finally died due to a stroke but 3 years later to the day I finally got my rig formatted and running again and drivers installed and it will show up in that developer device manager tool as fastboot surnia S - Mot Composite ADB interface. I think for a while with only my Samsung drivers installed and trying random generic ADB drivers I had it showing up as active on some general adb driver.

adb commands do nothing. They pick up my emulators and s9 fine but not it. With fastboot however I get print outs such as TA3970065Y as a device and one of the "first steps" to doing a bricked surnia reviival with some oem i forget now command that Ives een in guides too lead to this which I take as nothing there.

"(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 3A85790366719783#54413339373030
(bootloader) 363559004D6F746F4532280000#DF28
(bootloader) 85FE6C9F6E17DF0E3C9DB6A1E28AC55
(bootloader) 96786#65060B0400000000000000000
(bootloader) 0000000
OKAY [ 0.241s]
finished. total time: 0.242s
"

/

Any tips or next steps or hail maries? Its not a HUGE loss but as I regain more of my brains memory and go through my google history during when my brain was swelling im finding more and more forgotten wallets, communities, old software, accounsts all sorts of things and I know this phone was what I used exclusively other than my PC which im still scouring for clues to my near zero memory of the 2016 year but based on the titanium backup data from it I have as well as some old posts and google history data and urls I'd love to see whats on it at the moment to save if possible.

Everything else will just be a process with google history archives and my slow brain recovery but this old thing is really getting to me now what mysteries it might hold and with the power LED working, it going into recovery mode (I assume, no working screen and its pulled off now anyway but based on watching the device show up and such)

Blah blah blah, where could I start if anywhere, or am I better off going entry by entry in my 100gb of google server data i pulled from that time frame of raw data and links with little index.

Thanks (I'm excited to get rid of my fake chinese phone (not even gonna bother doing a mediatek all in one root) I got for free and my S9 and grab a new OnePlus, I wish i had the brain to buy one when I bought the s9 thinking you could still root samsung devices butr my last one was a S4, things have changed)