Make sure the option “Mount system partition read-only” in the Mount menu is checked before installing, if you want to be able to OTA later.
Note: When flashing full stock images, that include sbl1 or aboot, make sure both slots have a working fastboot before flashing. And never flash both slots without first testing on one.
Disclaimer: I do not (yet) own an FP3 myself.
Thanks to everyone who donated to help me get an FP3 If you like my work and want to help me to continue working on the FP3, please consider donating to me, to help me buy one: PayPal.Me
Path = /home/####/Downloads/twrp-3.3.1-0_k4y0z-20200131-01-fp3(1).zip
Open WARNING: Can not open the file as [zip] archive
Type = gzip
There are data after the end of archive
Offset = 2048
Physical Size = 10569656
Tail Size = 18683976
Headers Size = 10
Streams = 1
I wondered how you generated these sparse images
the images are compressed using brotlin, but the extracted data is still a binary. there’s a script in META-INF/com/google/android/ that includes commands for TWRP, but there’s also an executable. I thought it might be something to unpack or patch, but when I called
things started getting weird.
– that’s the help strings from tune2fs. but I also found e2label, quote, bzip2, there’s a whole busybox in there?
but then things start getting esoteric:
Modern provide" alt="borders.
Many artistspoweredperformfictiontype ofmedicalticketsopposedCouncilwitnessjusticeGeorge Belgium...</a>twitternotablywaitingwarfare Other rankingphrasesmentionsurvivescholar</p>
Countryignoredloss ofjust asGeorgiastrange<head><stopped1']);
severalbecomesselect wedding00.htmlmonarchoff theteacherhighly biologylife ofor evenrise of»plusonehunting(thoughDouglasjoiningcirclesFor theAncientVietnamvehiclesuch ascrystalvalue =Windowsenjoyeda smallassumed<a id="foreign All rihow theDisplayretiredhoweverhidden;battlesseekingcabinetwas notlook atconductget theJanuaryhappensturninga:hoverOnline French lackingtypicalextractenemieseven ifgeneratdecidedare not/searchbeliefs-image:locatedstatic.login">convertviolententeredfirst">circuitFinlandchemistshe was10px;">as suchdivided</span>will beline ofa greatmystery/index.fallingdue to railwaycollegemonsterdescentit withnuclearJewish protestBritishflowerspredictreformsbutton who waslectureinstantsuicidegenericperiodsmarketsSocial fishingcombinegraphicwinners<br /><by the NaturalPrivacycookiesoutcomeresolveSwedishbrieflyPersianso muchCenturydepictscolumnshousingscriptsnext tobearingmappingrevisedjQuery(-width:title">tooltipSectiondesignsTurkishyounger.match(})();
color:#ul id="possessrollingphysicsfailingexecutecontestlink toDefault<br />
@k4y0z , what the heck am I looking at? Did I take the wrong pill and got stuck in the rabbit hole?
Edit: the weirdness comes from googles brotli code, which includes a dictionary of random hardcoded weirdness that contains all these strings in C# code. brotli is of course needed to unpack the packed sparse images.
I tested installing the images yesterday with the current TWRP.
It’s probably better to let it boot up once before doing any other modifications like installing TWRP or magisk.
If it freezes at “Fairphone” Try doing the factory-reset through stock recovery.
I have answered in the other thread about the creation of the brotli-images.
the update-binary is taken from a ROM-build for another device, it should be fairly universal and is what actually executes the commands in the updater-script.
corrupted was what the phone told me. With a timer that it shutdown in 30seconds. I flashed the stockrom but the Message about my corrupt phone persists. (i find this horrifing and missleading)
Then i noticed the start in the right upper corner so i hit the power button. it booted back to stock.
Then i did what pigpig told me. the message is gone now.
i made sucsessfully a backup with twrp (the new one) with the tip you gave me yesterday. system-image instead of system. I can now easyly go back to the state it was before trying the update to 0110 wich saves a lot of time configuring.
I’m not sure what exactly causes this message, It doesn’t always appear and can be reset.
But If I understand you right, your phone booted fine after flashing 110 and confirming the corruption message?
No thats what i mean with missleading. I thought i destroyed the partition table or something. After flashing back 105 the message did not disapear. At this point i realized that i can confirm it and the boot continues.