Filefactory 504 gateway time out11/11/2023 ![]() ![]() Vodafone France - VODAFONE-FR-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7 - Available on Request ![]() Retail France - RETAIL-FR_FALCON_KLB20.9-1.10-1.24-1.1_cid7 - Available on Request Vodafone UK - VODAFONE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7 - Available on Request Retail EU (SIM-Locked) - RETAIL-EU-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7 - Available on Request Telus Canada - TELUS-CA_FALCON_KXB20.9-1.10-1.9_cid14 - Available on Request Google Play Edition - GPE_XT1032_KOT49H.M004 - Available on Request What else am I missing, about unusability from flashing boot/system and not touching the bootloader/recovery partitions? ![]() kernel) and system, where else could a problem occur? Another assumption is that partition sizes of 5.1 are not dramatically different in size than 4.4.4, but that can be verified by comparing gpt.bin of 4.4.4. Once aboot hands over control to boot (i.e. So the issue should not be the locked/unlocked status of the bootloader. the 4.4.4 aboot should be able to read the 5.1 signed image of boot/system. I am making an assumption that the locked aboot can accept signed images with mototola key for boot/system images, across versions i.e. Based on forum posts, my understanding of the boot process is that locked aboot (which houses fastboot) looks for signed images for boot/system or signed images of recovery. I would like to understand the source of the un-usability. Although it may have low monetary value, it does have sentimental value for me :good: It just works! No issues whatsoever other than not able to run 5.0 apps.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |