Message from @sum
Discord ID: 455498266591887361
I hate doing factory resets but what I can do
Sounds easoer ro fix than my böank problem was
Needed actual chip-debug stuff to force chip to boot on fastboot where on i could flash stuff for it
It was fun headache to fiddle around with direct HW link
jesus christ
how the fuck do you manage to fuck a phone that bad
Thank gods for the dev. Backdoors on chips. Cant permabrick stuff these days
Also fuck me I'm still not out of the shit sewer yet
It was quite easy.. Just some boot-firmware customization and , instead of .
`Failed to mount data invalid argument`
`fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img`
I only did this so how did the filesystem get fucked up this badly
Took data encryption keys with you
Should /data be f2fs
Or ext4
Ext4 safe bet
f2fs on some systems work but....
There we go now I can pull the log
Let's see of sideload will work too
`mount: failed to mount /dev/block/bootdevice/by-name/userdata at /data: Invalid argument
mount: failed to mount /dev/block/bootdevice/by-name/userdata at /data: Invalid argument`
Yeah broken keys
Based motorola/lenovo
So wait phone fucked?
Erase userdata
Erase userdata
From fastboot?
Rip all his filea and non backuped content
Yeas probly only way if rescue does not let mount data
O shit
I think we got something
I formated /cache to ext4 from auto
Wiped nearly everything
And it seems to be doing something
But damn, as much as you want to hate botnet google, at least the auto backup of shit is welcome
When it works
I still take manual contact backups yearly
Oh shit baby, no red messages saying error
This might go somewhere
<:GWtogaPagChomp:384871972229742592>