Conversation
Notices
-
>do literally nothing
>chinkphone reboots and starts bootlooping while ocmpainning about "red state"
- † top dog :pedomustdie: likes this.
- nyanide :nyancat_rainbow::nyancat_body::nyancat_face: repeated this.
-
@mint >should have bought a cat s22
Tbh i have no idea about russian bands
-
Somehow bootloader relocked itself.
-
It was literally in my pocket at the time.
-
That happened to my Samsung 32 bit phone. All junk.
-
@cjd I still have subscription to some Indian MTK dumping/flashing tool, so hopefully I could extrace data from there. Have to wait until I get home, though.
-
By the way, by some nondiscernable reason MTK'd preloader drivers don't work if you have VT-x enabled.
-
Dumping 220 gigs of userdata in hopes it wasn't overwritten (I think it shouldn't, the phone was just bootlooping because of unsigned boot partition and when flashing stock one, because of modified /system).
-
Userdata dumped but file(1) doesn't see it as a an ext4/f2fs/whatever partition, a bit concerning.
-
>flash latest stock firmware
>try to reunlock bootloader
>it forces me to create some account then complains that said account isn't old enough
:heyface:
-
Won't be surprised if that's the reason it got relocked, either timebomb or backdoor that won't let me do things. 4pda claims grace period is two weeks but flashing older firmware I had laying around would take like 20 minutes.
-
Yep, that worked. Still I'd like to have updated vendor/modem partitions in case there's some bugs or vulns fixed.
-
Reflashing firmware locks the bootloader again but not if you do it via fastboot instead of preloader. Flashed recovery, kernel, Lineage GSI, all that jazz, everything works. Now to see if restoring userdata partition would work, that means writing those 200 gigs back.
-
@slipgate Tecno. Used to let you do that immediately, still does if you flash the older ROM.
-
@mint >grace period is two weeks
Grorious Xiaomi?
-
Went to sleep doing that, and sadly it looks like the phone doesn't accept the what's left of the old userdata partition. Lost around 400 images from 4chins and however many hours I'd need to restore my programs/modules/etc.
-
@mint That shit sucks
-
Looking at hexdump of freshly formatted userdata, it looks like the same kind of gibberish. Need to poke around boot.img to figure out what the fuck it's doing, maybe not all hope's lost unless I've managed to overwrite partition that holds the keys.
-
I think it's in /metadata; thankfully I've dumped that one.
-
Same results after reflashing metadata as they were after flashing userdata. I think I'm on a good lead, just need to wait two more hours for userdata to flash again.
-
@p Running unlocked bootloader usually prevents OTA updates, plus I was runnig a custom ROM that has no such functionality.
-
@mint OTA spyware from Xi or the CIA.
-
@mint Caught the rest of the thread. Makes sense.
Sure the storage medium is okay? Or maybe just a heat thing.
-
@p It should be, after flashing the whole system everything works fine, but I'd like to get my data back. Don't know if it's a backdoor or just chink jank, leaning towards the latter.
-
@mint The things get warm enough and they start flaking, but if you were able to dump it without it spewing I/O errors, it's probably fine.
-
@p I don't think it ever get warm enough to be uncomfortable to hold. Also UFS storage used in modern phones is generally more reliable then eMMC or NAND.
-
@p F2FS, but it's using some weird Android encryption (it's device-mapper underneath but I don't think anyone bothered figuring out how to extract keys to mount it on a PC).
-
@mint What is the filesystem the data's on?
-
@p I did dump the userdata partition, it just isn't accepted when booting because the keys are stored elsewhere. There's a block-level encryption and a file-based encryption on top of it, no idea why. Anyway, turns out restoring both userdata and metadata made it finally boot with all my info intact.
-
@mint So the odds of actual data-recovery are slim? I mean, you can dump the image, right? (It is too late for this for now, but if you've got ssh access to it, it's good to have /usr/local/bin/dnsmasq-announce do something that, somewhere down the chain of events, ends up executing an rsync when your phone arrives on wifi after being offline a while. I had something like that for my N900 and later my HP Veer.)
-
@mint Nice. Mysterious but nice. I am currently trying to get Pleroma to tell the new uploader something other than `{:error, {:options, {:sslv3, {:versions, [:"tlsv1.2", :"tlsv1.1", :tlsv1, :sslv3]}}}}` without breaking FSE. Apparently there are not just adapters, which are designed to make an API fit the application's internal structure, but there is a helper (which is Rails/PHP talk for "adapter") for the adapter, the AdapterHelper. It adapts the adapter. It is an adapter adapter.
† top dog :pedomustdie:
cjd
slipgate
pistolero
All ０７６萌ＳＮＳ content and data are available under the