Database Develop

[RECOVERY] ufoFFICIAL TWRP 3.1.1-0 & MultiROM33v27 (adb/authorized)

(Download 2016-12-16 TWRP 3.0.3 : https://www.androidfilehost.com/?fid=673368273298921729)
Check attached 'install'.zip (to be flashed via cwm or twrp) file, for a more recent edition of twrp3.1.0-0 !
Built with Omnirom 6 repo, from unmodified bootable /TeamWin branch 7.1 (f2fs-tools v1.4)
More news: https://github.com/omnirom/android_bootable_recovery/commits/android-7.1

[EXP] Multirom33 TWRP3.1.1 +TrampolineV27 +MultiROMMgr.apk with No-Kexec work-around
Credits ( @mkasick ) @Tasssadar https://forum.xda-developers.com/showthread.php?t=2104706
p880 ( @Adam77Root ) @Demetris @fritzcola https://forum.xda-developers.com/optimus-4x-hd/orig-development/mod-multirom-v32-t3116422
Source https://github.com/Tasssadar/device_asus_grouper
https://github.com/P880-dev/android_kernel_lge_x3/commit/de499e8fd657925a74015f62229c5165620f127a
Complete manual : https://forum.xda-developers.com/showthread.php?t=2011403<--donations' thread
DOWNLOAD FILES : https://www.androidfilehost.com/?w=files&flid=146943​
twrpMR3.0.3 sources : https://github.com/multirom-htc/Team-Win-Recovery-Project/commits/android-7.1-mrom
Roms kick-flip are auto-explanatory...
-for 2ndRoms, twrp3__MR33v27 simulates a clean virtual format/data at every new creation (without wiping your internal medias & files !)
-multirom' Trampoline works with all recoveries (cwm&twrp) and provides a stand-by interface (added in your primary installed kernel), with all reboot options, and authorized adb (shell ls /mrom_bin /realdata ...)
-all your roms can be matched with dedicated onboot script.sh https://github.com/Tasssadar/multirom/wiki/run-on-boot-scripts
-attached Cyospak7-2016.zip is a kexec-ed compatible (any)kernel with: cm12 aosp5 aosp6 aosp7
Due to pressPOWER/till1stVIBER trick for 2nd/roms/non_shared_boot.img , p880 will likely NOT be official for MultiROM Manager app
NEW triple EDITION with No-Kexec work-around (boot.img shuv-it)
-20170517 twrp3.1.1(f2fs1.7) img MultiROM : //github.com/multirom-dev/Team-Win-Recovery-Project/commits/android-7.1-mrom
-20170701 Multi-boot zip menu ://github.com/multirom-dev/multirom/commits/master
-MultiROMMgr apk ://github.com/AdrianDC/MultiROMMgr/commits/master
TIP for hard buttons: using one nail to light click isn't as destructive as "fat" fingerprint pressure !
Kernel GPL

f2fs [WIP]
wip (kernel & mount_options*3fstab...)
DOWNLOAD exp f2fs 1.7: X-twrp3_1_0-20170308-f2fs1_7-ufoFLASH-p880.img
TWRPpost#1 are built with (2015-03-04omni6=aosp7=cm12.1)f2fs-tools v1.4.1 & adb authorized
(cm11 uses older 2013-10-25v1.2)
-official p880 recoveries twrp3.0.2/cwm6.0.5 do not include f2fs support
-unmodified p880 recoveries (from source) do not include specific p880 cold boot to recovery : always ext4
-aosp7 & omni7 are using same old f2fs than cm12 : 1.4
-"setup-recovery" is an arbitrary sh designation for one action/phrase to skip p880 cold boot : echo "boot-recovery" | /sbin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
- @laufersteppenwolf twrp2.7.1 was compiled with an added tool fibmap.f2fs, probably to countercheck the specific p880 cold boot (ext4)
-all recoveries can not mount any partition if p880 specific mmcblk0p5 is not void/wiped by postrecoveryboot.sh
- @alfsamsung cm13 doesn't support f2fs for now
So once again, IMHO, Multirom Trampoline is best universal solution to specific p880 cold boot : it provides a stand by menu (linux primary kernel) where you can reboot to bootloader directly (or primary/2nd roms...), and "warm reboot to recovery" option...
I believe that twrp' sources & missing fstab2, have nothing wrong , the origin is the non-standard (secure?) cold boot for p880: all other Tegra3 devices have hybrid ext4/f2fs OK(asusTF700 with official twrp). The best will be to find @laufersteppenwolf twrp2.7.1 repo; the worst is to use cwm editions.
Click to expand...
Click to collapse
with tool like 3CtoolboxFree you can trim/clean etc ; within 3C/terminal/SUticked : type "setup-recovery" then aosp6/7 reboot will get you to twrp & f2fsOK..
3C can behave intrusive, but you can use it static : greenify + autostarts
Finally remember that depending twrp_romVersion and mount/flag used for format/f2fs, can give minor changes (?) : aosp6/7 omni6/7 and cm12 are on "old" regular =1.4.1 ;
Code:
I:operation_start: 'Change File System'
Formatting Cache using mkfs.f2fs...
F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-10-18) [modified by Motorola to reserve space]
Info: Trim is disabled
Info: sector size = 512
Info: total sectors = 786432 (in 512 bytes)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.1.10-CM ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Sun Jan 15 23:58:55 CET 2017"
Info: format successful
I:mkfs.f2fs -t 0 /dev/block/mmcblk0p4 process ended with RC=0
Done.
I:Recreating /cache/recovery DATA.cpp folder.
Nameless3 =1.5
Only cm13 =1.6.1 and cm14.1 =1.7 include more options : defrag ....
Code:
I:operation_start: 'Change File System'
Formatting Cache using mkfs.f2fs...
F2FS-tools: mkfs.f2fs Ver: 1.6.1 (2016-03-22) [modified by Motorola to reserve space]
Info: Debug level = 0
Info: Label =
Info: Segments per section = 1
Info: Sections per zone = 1
Info: Trim is disabled
Info: sector size = 512
Info: total sectors = 786432 (384 MB)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.1.10-aosp67 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Sun Jan 15 00:32:53 CET 2017"
Info: Overprovision ratio = 10.000%
Info: Overprovision segments = 43 (GC reserved = 28)
Info: format successful
I:mkfs.f2fs -t 0 /dev/block/mmcblk0p4 process ended with RC=0
Done.
I:Recreating /cache/recovery folder.
When you format via twrp run the save_log option and check the end.
Click to expand...
Click to collapse
(Thx to @Phil_Smith @kessaras for pre-testing)
What: /sys/fs/f2fs/<disk>/gc_max_sleep_time
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the maximun sleep time for gc_thread. Time
is in milliseconds.
What: /sys/fs/f2fs/<disk>/gc_min_sleep_time
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the minimum sleep time for gc_thread. Time
is in milliseconds.
What: /sys/fs/f2fs/<disk>/gc_no_gc_sleep_time
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the default sleep time for gc_thread. Time
is in milliseconds.
What: /sys/fs/f2fs/<disk>/gc_idle
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the victim selection policy for garbage collection.
What: /sys/fs/f2fs/<disk>/reclaim_segments
Date: October 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the issue rate of segment discard commands.
What: /sys/fs/f2fs/<disk>/ipu_policy
Date: November 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the in-place-update policy.
What: /sys/fs/f2fs/<disk>/min_ipu_util
Date: November 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the FS utilization condition for the in-place-update
policies.
What: /sys/fs/f2fs/<disk>/min_fsync_blocks
Date: September 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the dirty page count condition for the in-place-update
policies.
What: /sys/fs/f2fs/<disk>/max_small_discards
Date: November 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the issue rate of small discard commands.
What: /sys/fs/f2fs/<disk>/max_victim_search
Date: January 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the number of trials to find a victim segment.
What: /sys/fs/f2fs/<disk>/dir_level
Date: March 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the directory level for large directory.
What: /sys/fs/f2fs/<disk>/ram_thresh
Date: March 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the memory footprint used by f2fs.
What: /sys/fs/f2fs/<disk>/trim_sections
Date: February 2015
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the trimming rate in batch mode.

what still WIP ??

Salman Al-Badgail said:
what still WIP ??
Click to expand...
Click to collapse
Was about to ask the same thing, if I remembered correctly I have seen a recovery released by OP supporting f2fs...... but anyway keep up the good work.

b886b said:
@oF2pks do U mean that with twrp 3.0.3 on your AFH, we will be able to flash AOSP 7 rom, gapps and supersu consecutively without the need to reboot recovery in between like that in cwm????
Click to expand...
Click to collapse
Salman Al-Badgail said:
what still WIP ??
Click to expand...
Click to collapse
First, just want to be sure everything works clear with ext4, for aosp6/7 + opengapps without any error/miss; then I'll upload a recoveryTWRP303.zip for CWM's users to easy install.
WIP: concerning f2fs, apparently there is an issue on cold boot to recovery and f2fs/data returns to ext4 (?!), also I did not try f2fs myself since I'm using Multirom with hidden 2nd Roms: I will soon (after I proceed my backups & AsusTF700->f2fs).
The p880-dev/X3/fs/f2fs is 2015Feb update (much better then AsusTF700!): "Controls the trimming rate in batch mode"; and I'm not sure on best mount options flags.
IMHO, most relevant will be to get fstab' [boot.img(1) + recovery.img(*3)]=4 in par for real testing, on this latest Omnirom based recovery303 ( the CM based 303 looks less accurate).

screen flickers
oF2pks said:
Download : https://www.androidfilehost.com/?fid=673368273298921729
Click to expand...
Click to collapse
Is it just me screen flickers when you press the navigation keys at the bottom?
Even worse is TWRP2.8.6_multirom_p880_20150523.img.
While the screen is perfectly stable in twrp-3.0.2-0-p880.img.

Sparkling! edition (ie wip)
Indeed, like twrpMR2.8.6, screen has some hiccups overlays, but works 100% OK.
Comparing to official twrp 3.0.2, both 2.8.6 & 3.0.3 don't load right framebuffer=3 ; I hope @fritzcola tell us more, also hard to get exact device tree (omni br. ?) from master @Dees_Troy .
Anyway it's remind which twrp being in use (versus nice official); also I remember an assertion on lightweight (? with possible lzma/ramdisk).
Code:
TWRP 3.0.2 graphics OKofficial[/U][/B]
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP 3.0.2-0 on Thu Dec 29 14:55:25 2016
(pid 136)
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/platform/tegra-udc.0/gadget/lun0/file'
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:Got max brightness 255 from '/sys/class/leds/lcd-backlight/max_brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
I:LANG: en
[B]Starting the UI...Skipping adf graphics -- not present in build tree
Skipping drm graphics -- not present in build tree[/B]
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
setting GGL_PIXEL_FORMAT_RGBA_8888
[B]double buffered
[U]framebuffer: 3 (720 x 1280)[/U] #####instead of 0->flickering (?)######
Using fbdev graphics.[/B]

I initially voted for data + cache in f2fs, but after several testing I found that the cache does not need to be trimmed regularly so I suspect that only data in f2fs can have improve the performance of our device. I have tested for several cycles using the app fstrim for several weeks and it definitely helps in the way our phone performs, after fstrim our device is more snappy and the sluggish feel after long time usage has significantly decreased. However, whenever I run fstrim it always says that cache does not need to be trimmed so I believe the performance boost is due to the trimming of data partition which leads me to believe that the culprit of our sluggish performance was due to the cramming up of data partition. So I think data in f2fs would be enough.

2017 22 Jan update post#1 [.ZIP] attached
Thx to TeamWin, twrp 3.0.3 is a wip "live" edition for now : https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Soon or later TeamWin will push official p880 (non flickering) thread; while waiting, I will frequently update post#1 from latest github, with a :
-cwm compatible zip
-aosp7 OK with queueing list' zip
-f2fs-tools version1.4.1 (=aosp7=cm12.1)
-adb authorized
-(sparkling edition...)

[twrp 3.0.3] MultiROM : back in blue ! (2016-12-16)
@ze7zez , @juantech , @b886b
Thx to @fizbanrapper (github), no more twrp shove-it for roms kickflips : just focus on aosp7/cyospak7 on primary and flash (upRight burger) your favourites on 2nd (cm11/12/13 aosp6 lgJB omni4 beanstalk4...).
Download 3.0.3 (f2fs1.4.1) : https://www.androidfilehost.com/?fid=817550096634741392
Cyospak7 anykernel is compatible with aosp6 (15~20mn install/2ndRom !), and includes iodak fstab2 f2fs switch. I'll try to upgrade cm13 (only multiboots lgJB for now) with latest kexec soon; cm12.1/Nameless2 are already compatible.
Don't forget to flash the trigger MultiROM trampoline AND pressPOWER/till1stVIBER trick for 2nd/roms/non_shared_boot.img (specific to old p880 boot on/off process).
SuperSu.zip flash can be tricky, due to 2*reboot (via MultiROM): try 2.78sr5.zip+AppUpgrade2.79.apk, with aosp6 on 2nd. Xposed flash works fine.
Until now, basic rule was to flash highest android version on primary.
You tell me...

Hey oF2pks,
Does this recovery flash android 7 without any errors or problems.?
I will flash aosp 7.1 by csk1jw
Thnx

dave2609 said:
Hey oF2pks,
Does this recovery flash android 7 without any errors or problems.?
I will flash aosp 7.1 by csk1jw
Thnx
Click to expand...
Click to collapse
Yes indeed, latest twrp3.0.3 build is 2017-01-27 (MultiROM included), but on very new first install, you should always follow OP recommendations : until now @csk1jw is still on cwm6.0.4.5 & OpenGapps stock/WebView; you can still swap cwm/twrp recoveries later, but backups/nandroid are not compatible. Personally I prefer latest twrp3.0.3 and @Deltadroid modular Gapps packages.

Okay thnx,
But how to install aosp 7 by csk1jw
With this recovery?
Just normal procedure?

TWRP MultiROM 2017-02-20 & f2fs 1.6.1
New twrp-MultiROM-20170220 is now built with LineageOs13, f2fs-tools Ver: 1.6.1 (2016-03-22) & adb authorized
https://github.com/nkk71/Team-Win-Recovery-Project/commits/android-7.1-mrom
You can still download regular f2fs_Ver1.4.1 (aosp6/7 cm12.1) in post 1&2.

oF2pks said:
New twrp-MultiROM-20170220 is now built with Omni7.1.1, f2fs-tools Ver: 1.7.0 (2016-07-28) & adb authorized
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
You can still download regular f2fs_Ver1.4.1 (aosp6/7 cm12.1) in post 1&2.
Click to expand...
Click to collapse
Almost success! :good:
The interface in this version flickers occasionally.
But still flickers after the entry mode log.
Nevertheless, it should be a warning for people with photosensitive epilepsy.

red error 7 primary
oF2pks said:
New twrp-MultiROM-20170220 is now built with LineageOs13, f2fs-tools Ver: 1.6.1 (2016-03-22) & adb authorized
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
You can still download regular f2fs_Ver1.4.1 (aosp6/7 cm12.1) in post 1&2.
Click to expand...
Click to collapse
ze7zez said:
Almost success! :good:
The interface in this version flickers occasionally.
But still flickers after the entry mode log.
Nevertheless, it should be a warning for people with photosensitive epilepsy.
Click to expand...
Click to collapse
(One more miss,) sorry for that , I removed this untimely build which was buggy ; I wanted to upload another one (Lineage f2fs1.6.1) but error 7 was always back on aosp/primary: after multiple tests on my ok lucky last build twrp303MR2017-01-27.img (regular omni6 and f2fs 1.4), I noticed that switching from aosp6 to aosp7 on primary, could bring error7/system back on 3# zip flash. In this case, follow:
-wipe /system/data/cache (if error mount/system do => hard/keys cold reboot to recovery and repeat wipes)
-repair /system+/data+/cache
then you can flash up to ten zip consecutive+reboot in one action. (don't forget Cyospak7-2016 for MultiROM)
ALL THIS won't tamper your personal data & secondary roms.
I don't get how old cwm 6.0.4 can handle this (maybe e2fsk auto on fresh install?).
Also I didn't find a solution to get @alfsamsung / @iodak cm13 pass file system f2fs check on boot strange that both guys quit xda at same 2016-11-16 ?!)

oF2pks said:
...
Check attached 'install'.zip (to be flashed via cwm or twrp) file, for a more recent edition of twrp3.1.0-0 !
Built with Omnirom 6 repo, from unmodified bootable /TeamWin branch 7.1 (f2fs-tools v1.4)
More news: https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Click to expand...
Click to collapse
New twrp 3.1.0 2017 03 07, check post#1 attached zip

oF2pks said:
New twrp 3.1.0 2017 03 07, check post#1 attached zip
Click to expand...
Click to collapse
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention

f2fs 1.7 post#3 (adb/authorized)
For futur? roms only : post#3 updated with unmodified 2017-03-08 TWRP 3.1.0 and f2fs 1.7 (Omnirom7.1) (adb/authorized).
https://github.com/omnirom/android_external_f2fs-tools

[EvolutionX (3.5) Erfan GSIs] [Android 10 ]

New v3.5 port from Oneplus 6 https://forum.xda-developers.com/showpost.php?p=81186001&postcount=6
port from Redmi 4A https://forum.xda-developers.com/showpost.php?p=81186219&postcount=7
From Base Firmware : EvolutionX_3.3_violet-10.0-20191112-1125-OFFICIAL.zip
Raw Image Size: 2.86 GiB
Thank to TeamGSI
======================
Download:
GSI : https://drive.google.com/drive/folders/1-7N6Z9NUb-9ut8Zz8M51FAwUC11AKTaa
File Name : EvolutionX-Aonly-10-20191119-GSI.img-1621.z7 (extracted before flashing)
TWRP : https://mega.nz/#!sHoXlaDK!ZIfuRrtl7IGsruGMIWDrbvudKgxcYdiEd-6iQS2YFNg
File Name : TWRP-20191001-3.3.1.0-clover.img
Vendor & boot : Pie ( Treble ) https://mega.nz/#!xaolTKoS!pdfjw02cw3dImfB4vlyXwINALQUewQ5lJBBjSUDKxcM
File Name : vendor_197.zip
Latest Official Clover Firmware https://mega.nz/#!QDplSYab!mrB5f8875VghQHfrrGvid4iJICMopkq3anZCipLWzqo
File Name : fw_clover_miui_MIPAD4_9.8.29_6647b25a58_8.1.zip
Erfan tools : https://mega.nz/#!xXpViC4Y!UsRgGMYNtiaLvfdXSuzamfaxsM_FOs-9xrZrPu5QCP8
File Name : allzygotefix2.zip
Phh Magisk : Magisk-v20.2-b29f0ca4-phh.zip
https://mega.nz/#!tKxngSaD!jdDHi4-QFMX2bNgQVPi50ZrpovbNRuD61aAeIt02lCI
GMS : https://mega.nz/#!cOhmgIoY!cTYxxYpc36tMl0QnndRcaPUDQ6BpO7tG0yiPQ2i7QXo
=================
Step
-wipe--Format Data
-wipe--Advanced wipe---Dalvik , Cache , Data , System , Vendor
-Option wipe--Advanced wipe---tick Data menu----Repair or change file System-----Change File System and select F2FS
-flash Firmware
-flash Vendor
-flash GSI as System Image
-flash allzygotefix2.zip (for A-only GSI when work with Android 10)
-Reboot to System
Don't worry about " Android System error message , its only one warning --we will fix at the end.
click "OK"
-Setting menu --Display---Smallest width = set to 540 dp or more than that , Icon shape = up to you
-Setting menu --Evolution settings---enable Users and Logout ( Multi user )
Don't forgotten to setup SD Card ===(Support exFAT) for me use as removable.
-Setting menu -- About phone ===changes device name from POCO F1 to anything you like or Mipad4
==============
-Flash Magisk (phh Magisk) https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
-Reboot--update it if need
-Magisk manager --install belows modules from here ---> https://github.com/ElderDrivers/EdXposed
1. Magisk-riru-core-v19.5.zip ( save)
2. Magisk-EdXposed-YAHFA-v0.4.6.0_beta.....xxxx.zip
-Reboot
-install Edxposed Manager.apk
open it set active status
-Reboot by granted Magisk super user permission
-Add & activated eXposed modle--com.cofface..ivader
=======================================
-install updated GMS ( Google Services)
-Reboot
-Setup and login your google account
Now your Play Protect is certified. and all green Safetynet check success.
======================================
-Check your FingerPrint.
-Check your BlueTooth
-Check your Mobile Data ( VoTLE )
-Check your Auto rotate
-Your Camera
All working
=========================
Fix error " Android System: your vendor image does not match the system......."
-edit (system/vendor----> bulid prop)
change line " ro.vendor.build.fingerprint = xxx to ro.build.fingerprint=xxx
and/or
-edit (system ---> bulid prop)
change " ro.treble.enabled=true" to " ro.treble.enabled=false"
- reboot
=========================
Viper4Android FX from magisk'repo
v.2.7.1.0
-install with Magisk manager
-reboot and open program-- follow suggestion from screen
==========================
Supported Youtube Vanced.
++++++++++++++++++++++++++++++++++++++++++++++++++
GCAM
https://www.celsoazevedo.com/files/android/google-camera/dev-parrot043/#apk1213
+++++++++++++++++++++++++++++++++++++++++++++++++

New & Update from ExpressLuke GSI ( compiled from source)
=============================
ROM Name: Evolution X 3.3 ( EvolutionX_3.3_ARM64A-10.0-20191202-0048-UNOFFICIAL.img)
ROM Version: 10
ROM Security Patch: 5 November 2019
Architecture: ARM64
Partition Layout: A
GSI Patch Base: phh v204
Built in GApps?: Yes
Changelog: https://pastebin.com/raw/0SwBzV6e
MEGA: Download
( https://mega.nz/#!QJkF3KxY!-trp3Q9NJDqtKoTddxeg3yn-bu6JU_6XuokZs-ri7B4)
SourceForge: Download
(https://sourceforge.net/projects/ex...191202-0048-UNOFFICIAL.img.xz/download)Google
Drive: Download (https://drive.google.com/a/turbox.uk/uc?id=1U0Nhpow2IMXUTV_ZQIfC9JAEocPc3Qik&export=download)
####Please use magisk-phh
Note !!!!!!
1. you must flash "Permissiver_v5.zip" cause GSI image not included. ( if not will Boot Fastboot Mode )
2. No need to install new update GMS apk.
3. Default Camera not working. use GCAM instead
4. Chrome crash.
-----> Please test wifi speed. mine very low 30 Mbit/Sec
-----> Evolution setting--->Power menu --->ERROR

EVOLUTIONX 3.4 (Recommended)
Download A-Only: Google Drive (https://drive.google.com/uc?export=download&id=16_3QYEeq8DnLI92xQvY6u4hSNpZ4-sYj)
File name: EvolutionX-Aonly-10-20191210-ErfanGSI.img.gz
Information:
Android Version: 10
Brand: Xiaomi
Model: MI 8
Codename: dipper
Build Type: aosp_dipper-user
Build Number: QQ1A.191205.011
Incremental: eng.DarkAn.20191207.000600
Tags: test-keys
Security Patch: 2019-12-05
Fingerprint: Xiaomi/dipper/dipper:8.1.0/OPM1.171019.011/V9.5.5.0.OEAMIFA:user/release-keys
Description: dipper-user 8.1.0 OPM1.171019.011 V9.5.5.0.OEAMIFA release-keys
Raw Image Size: 2.60 GiB

Many thanks for your contributions to our device!
it works great , everything works except the auto rotate, is always in vertical

UPDATE EvolutionX v3.5
Information:
Android Version: 10
Brand: OnePlus
Model: ONEPLUS A6003
Codename: OnePlus6
Build Type: aosp_enchilada-userdebug
Build Number: QQ1B.191205.011
Incremental: eng.bliss.20191212.000302
Tags: test-keys
Security Patch: 2019-12-05
Fingerprint: OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys
Description: OnePlus6-user 8.1.0 OPM1.171019.011 273 release-keys
Raw Image Size: 2.81 GiB
====================================
Download A-Only: Google Drive (https://drive.google.com/uc?export=download&id=13OJZ6ABa5zLMdCGAGaW3nuNczGV8VAuE)
<<<<<<<< Not boot with my vendor for mipad >>>>>>>>>>>>>

Update EvolutionX 3.5
Information:
Android Version: 10
Brand: Xiaomi
Model: Redmi 4A
Codename: rolex
Build Type: aosp_rolex-userdebug
Build Number: QQ1B.191205.011
Incremental: eng.ubuntu.20191212.104649
Tags: test-keys
Security Patch: 2019-12-05
Fingerprint: Xiaomi/rolex/rolex:7.1.2/N2G47H/V9.2.6.0.NCCMIEK:user/release-keys
Description: rolex-user 7.1.2 N2G47H V9.2.6.0.NCCMIEK release-keys
Raw Image Size: 2.35 GiB
=====================================
Download A-Only: Google Drive (https://drive.google.com/uc?export=download&id=1jxyN2uiNo8rk2o4az6r8BR3nfqxqHfF6)
Bug: Evolution setting---power menu (crash) but can use advanced boot with power button.

I tried several times and always get the same problem : the autorotate not works,
I installed other Roms and in every rom I have the same probem with the autorotate
I also tried the roms from https://forum.xda-developers.com/mi-pad-4 and is the same, Im afraid my autorotate die...
I tried the sensors app in google play and says all my sensors not works...
Any idea to try to solve giroscopie?
I tried various roms and I think this one works very well :
https://forum.xda-developers.com/mi-pad-4/development/rom-lineageos-17-0-t3989187

Fix error " Android System: your vendor image does not match the system......."
-edit (system/vendor----> bulid prop)
change line " ro.vendor.build.fingerprint = xxx to ro.build.fingerprint=xxx
and/or
-edit (system ---> bulid prop)
change " ro.treble.enabled=true" to " ro.treble.enabled=false"
- reboot
Click to expand...
Click to collapse
Everything works fine except the error every bootup is not fixed. I cannot find "ro.vendor.build.fingerprint" in build prop. I managed to set this "ro.treble.enabled=false". However, the error persists.
Also, how do I prevent the screen from turning off when I close the flip cover?

Development [UNOFFICIAL] LineageOS 19

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.0, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's working:
RIL (Calls, SMS, Data)
IMS
Fingerprint
Wi-Fi
Bluetooth
Bluetooth Audio
Camera
Audio
Sensors
Flash
GPS
DAC
Vibration
Wifi Hotspot
Display out
Wireless display
Selinux enforcing
What's not working:
a2dp offload
Flashing Instructions:
Go to the first (pre) release in the downloads, and download the boot.img, vendor_boot.img, dtbo.img and copy-partitions-20220222.zip
Reboot to bootloader (adb reboot bootloader or hold vol- and power when the phone is off)
Code:
fastboot flash boot boot.img
Code:
fastboot flash vendor_boot vendor_boot.img
Code:
fastboot flash dtbo dtbo.img
Use volume keys and power to reboot to recovery, or use
Code:
fastboot reboot recovery
If you dont have both slots populated, nows your chance:
a) Enable adb sideload
b) Flash the copy partitions script:
Code:
adb sideload copy-partitions-20220222.zip
Enable adb sideload and flash LineageOS:
Code:
adb sideload lineage-19.1-20220327-UNOFFICIAL-pstar.zip
- replace zip name if needed -
Reboot to recovery: Advanced -> Reboot recovery
(Optional) Flash Gapps/Magisk:
a) Enable adb sideload and:
Code:
adb sideload gapps.zip
(similar for magisk)
Factory reset/format data
Reboot system
Profit
Edge 20 Pro Telegram group
Downloads:
pstar releases here: github
Sources:
Device Tree pstar: pstar
Device Tree sm8250-common: sm8250-common
Kernel: sm8250
Vendor: motorola
lineage-19.1 branches
XDA:DevDB Information
LineageOS for the Motorola Edge 20 Pro, ROM for the Motorola Edge 20 Pro
Contributors
SGCMarkus
Source Code: https://github.com/LineageOS
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
ROM Firmware Required: 11
Based On: LineageOS
Version Information
Status: Stable

Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless). Also dump /dev/block/bootdevice/by-name/pstore and attach that
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelogs
Release 27.03.2022 (LOS19)
- First public release

Reserved

nice work

Thanks for your work. I'll give it a try this evening.

LOS 19.1 works fine. I use MGC 8.1.101 as camera app. Battery drain is ok.

Thanks for the great work, it works nice and stable.

Any chance of this ROM getting an update?

SGCMarkus said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.0, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's working:
RIL (Calls, SMS, Data)
IMS
Fingerprint
Wi-Fi
Bluetooth
Bluetooth Audio
Camera
Audio
Sensors
Flash
GPS
DAC
Vibration
Wifi Hotspot
Display out
Wireless display
Selinux enforcing
What's not working:
a2dp offload
Flashing Instructions:
Go to the first (pre) release in the downloads, and download the boot.img, vendor_boot.img, dtbo.img and copy-partitions-20220222.zip
Reboot to bootloader (adb reboot bootloader or hold vol- and power when the phone is off)
Code:
fastboot flash boot boot.img
Code:
fastboot flash vendor_boot vendor_boot.img
Code:
fastboot flash dtbo dtbo.img
Use volume keys and power to reboot to recovery, or use
Code:
fastboot reboot recovery
If you dont have both slots populated, nows your chance:
a) Enable adb sideload
b) Flash the copy partitions script:
Code:
adb sideload copy-partitions-20220222.zip
Enable adb sideload and flash LineageOS:
Code:
adb sideload lineage-19.1-20220327-UNOFFICIAL-pstar.zip
- replace zip name if needed -
Reboot to recovery: Advanced -> Reboot recovery
(Optional) Flash Gapps/Magisk:
a) Enable adb sideload and:
Code:
adb sideload gapps.zip
(similar for magisk)
Factory reset/format data
Reboot system
Profit
Edge 20 Pro Telegram group
Downloads:
pstar releases here: github
Sources:
Device Tree pstar: pstar
Device Tree sm8250-common: sm8250-common
Kernel: sm8250
Vendor: motorola
lineage-19.1 branches
XDA:DevDB Information
LineageOS for the Motorola Edge 20 Pro, ROM for the Motorola Edge 20 Pro
Contributors
SGCMarkus
Source Code: https://github.com/LineageOS
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
ROM Firmware Required: 11
Based On: LineageOS
Version Information
Status: Stable
Click to expand...
Click to collapse
how to download all files
SGCMarkus said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.0, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's working:
RIL (Calls, SMS, Data)
IMS
Fingerprint
Wi-Fi
Bluetooth
Bluetooth Audio
Camera
Audio
Sensors
Flash
GPS
DAC
Vibration
Wifi Hotspot
Display out
Wireless display
Selinux enforcing
What's not working:
a2dp offload
Flashing Instructions:
Go to the first (pre) release in the downloads, and download the boot.img, vendor_boot.img, dtbo.img and copy-partitions-20220222.zip
Reboot to bootloader (adb reboot bootloader or hold vol- and power when the phone is off)
Code:
fastboot flash boot boot.img
Code:
fastboot flash vendor_boot vendor_boot.img
Code:
fastboot flash dtbo dtbo.img
Use volume keys and power to reboot to recovery, or use
Code:
fastboot reboot recovery
If you dont have both slots populated, nows your chance:
a) Enable adb sideload
b) Flash the copy partitions script:
Code:
adb sideload copy-partitions-20220222.zip
Enable adb sideload and flash LineageOS:
Code:
adb sideload lineage-19.1-20220327-UNOFFICIAL-pstar.zip
- replace zip name if needed -
Reboot to recovery: Advanced -> Reboot recovery
(Optional) Flash Gapps/Magisk:
a) Enable adb sideload and:
Code:
adb sideload gapps.zip
(similar for magisk)
Factory reset/format data
Reboot system
Profit
Edge 20 Pro Telegram group
Downloads:
pstar releases here: github
Sources:
Device Tree pstar: pstar
Device Tree sm8250-common: sm8250-common
Kernel: sm8250
Vendor: motorola
lineage-19.1 branches
XDA:DevDB Information
LineageOS for the Motorola Edge 20 Pro, ROM for the Motorola Edge 20 Pro
Contributors
SGCMarkus
Source Code: https://github.com/LineageOS
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
ROM Firmware Required: 11
Based On: LineageOS
Version Information
Status: Stable
Click to expand...
Click to collapse
how to download all files Except LineageOS

monsmons262626 said:
how to download all files Except LineageOS
Click to expand...
Click to collapse
Release pstar (Motorola Edge 20 Pro) initial release · SGCMarkus/Lineage-OTA
Lineage OS 19 for Motorola Edge 20 Pro Flashing instructions: Reboot to bootloader (adb reboot bootloader or hold vol- and power when the phone is off) fastboot flash boot boot.img fastboot flash ...
github.com

ilia3367 said:
Release pstar (Motorola Edge 20 Pro) initial release · SGCMarkus/Lineage-OTA
Lineage OS 19 for Motorola Edge 20 Pro Flashing instructions: Reboot to bootloader (adb reboot bootloader or hold vol- and power when the phone is off) fastboot flash boot boot.img fastboot flash ...
github.com
Click to expand...
Click to collapse
thank alot but may phone now is deadboot because icant see this replay huhu i flash lineageos not to sideload mode
i try to via twrp after that deadboot my phone huhu

monsmons262626 said:
thank alot but may phone now is deadboot because icant see this replay huhu i flash lineageos not to sideload mode
i try to via twrp after that deadboot my phone huhu
Click to expand...
Click to collapse
with "deadboot" you mean its going into edl/9008?
You probably didnt copy slot a to b (as written in the instructions)
TWRP *shouldnt* (never tried it) be the problem though.

SGCMarkus said:
TWRP *shouldnt* (never tried it) be the problem though.
Click to expand...
Click to collapse
TWRP on Android 12 doesn't work...

SGCMarkus said:
with "deadboot" you mean its going into edl/9008?
You probably didnt copy slot a to b (as written in the instructions)
TWRP *shouldnt* (never tried it) be the problem though.
Click to expand...
Click to collapse
sorry i cant read all instruction
yes my phone is into edl/9008
i try blank-flash.bat but nor working
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.016] ...cpu.id = 195 (0xc3)
[ 0.016] ...cpu.sn = 1399562115 (0x536b9f83)
[ 0.016] Opening singleimage
[ 0.125] Loading package
[ 0.219] ...filename = pkg.xml
[ 0.234] Loading programmer
[ 0.266] ...filename = programmer.elf
[ 0.266] Sending programmer
[ 0.317] ReadFile() failed, GetLastError()=0
[ 0.557] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.557] ERROR: sahara_download()->general error
[ 0.557] Check qboot_log.txt for more details
[ 0.557] Total time: 0.557s
FAILED: qb_flash_singleimage()->sahara_download()->general error

ilia3367 said:
TWRP on Android 12 doesn't work...
Click to expand...
Click to collapse
working but not this files

ilia3367 said:
TWRP on Android 12 doesn't work...
Click to expand...
Click to collapse
with that i meant it shouldnt have a problem to flash LOS, for anything else... no guarantee.
monsmons262626 said:
sorry i cant read all instruction
yes my phone is into edl/9008
i try blank-flash.bat but nor working
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.016] ...cpu.id = 195 (0xc3)
[ 0.016] ...cpu.sn = 1399562115 (0x536b9f83)
[ 0.016] Opening singleimage
[ 0.125] Loading package
[ 0.219] ...filename = pkg.xml
[ 0.234] Loading programmer
[ 0.266] ...filename = programmer.elf
[ 0.266] Sending programmer
[ 0.317] ReadFile() failed, GetLastError()=0
[ 0.557] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.557] ERROR: sahara_download()->general error
[ 0.557] Check qboot_log.txt for more details
[ 0.557] Total time: 0.557s
FAILED: qb_flash_singleimage()->sahara_download()->general error
Click to expand...
Click to collapse
Not too familiar with what motorolas blank flash does, but i suppose it only flashes 1 slot? and might not reset slots.
What you could do is dump all of slot a in qfil or with bkerler's edl python script, and then flash them to slot b (aka what the copy partitions zip does, which you should have flashed, if you read the instructions...).
But if you ever had an OTA that *shouldnt* be necessary actually, and at this point its unlikely the phone is that fresh it never OTA'd.

SGCMarkus said:
with that i meant it shouldnt have a problem to flash LOS, for anything else... no guarantee.
Not too familiar with what motorolas blank flash does, but i suppose it only flashes 1 slot? and might not reset slots.
What you could do is dump all of slot a in qfil or with bkerler's edl python script, and then flash them to slot b (aka what the copy partitions zip does, which you should have flashed, if you read the instructions...).
But if you ever had an OTA that *shouldnt* be necessary actually, and at this point its unlikely the phone is that fresh it never OTA'd.
Click to expand...
Click to collapse
Sir how to make prog emmc Firehouse .mbn for Motorola edge 20 pro

Does someone know when an official build wil come out?

Nearly perfect!
The only issue I found it is that the search button configuration isn't working.
PS: My edge s pro becomes edge 20 pro after flashing this rom.

[ROM-EXPERIMENT][FASTBOOT][Clamor's repartition] LineageOS 18.1 Android GO with GMS

HTML:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Here is something i wanted to try for a long time. A full package of GMS (Google Mobile Services) Android GO for Nexus 4.
This package includes all Android GO apps that come preinstalled on those phones plus some extra apps that only come with 2GB phones.
Other than that, everyting is the same as in regular LineageOS builds.
Only for Clamor's repartition (needs a /vendor partition).
IMPORTANT: You need to repartiton your device using Clamor's repartitioning script from HERE
Works:
- WiFi
- Bluetooth
- RIL
- Camera
- GPS
- Sensors
- Audio
- NFC
Doesn't work:
- L1 Widevine DRM
- Slimport
Flashing Instruction:
1. Backup all your data (Important).
2. Install fastboot. Here is a guide if you need: https://www.xda-developers.com/install-adb-windows-macos-linux/
3. Download ROM. Reboot phone to fastboot mode. Connect your phone to computer.
4. Open your command line or terminal, cd to directory where you put the ROM.
5. Perform a following command to flash the ROM:
fastboot -w -S 512M update image-mako-lineage-18.1-go-20220801-UNOFFICIAL-fastboot-signed.zip
Click to expand...
Click to collapse
WARNING: This will wipe all user data from phone but it is required if you flashing it first time.
For further updates wiping data is not required and you can remove -w from command line so it'll be:
fastboot -S 512M update image-mako-lineage-18.1-go-20220801-UNOFFICIAL-fastboot-signed.zip
Click to expand...
Click to collapse
Phone will reboot automatically. After first setup give phone some time to update all preinstalled Google apps.
Download: https://drive.google.com/drive/folders/1H3VHwpaRmv43styxZBRU1M9dLEin-UdC
Sources:
Device: https://github.com/voron00/android_device_lge_mako
Kernel: https://github.com/voron00/android_kernel_lge_mako
Vendor: https://github.com/voron00/proprietary_vendor_lge
Credits:
- LineageOS team.
- Google.
- @Ziyan for his great work on camera and other things.
- @Clamor repartitioning script.
- If i forgot someone, please tell me.
Contributors
voron00
Source Code: https://github.com/LineageOS

awesome. after handling clamors repartitioning, it seems to have installed fine so far, first boot takes its time of course
Now it booted and is updating the Apps. Appears to work and feels rather fluent for a recent OS.
i'm really curious about it... so thank you very much!

Is a wipe also needed if I come from your latest June 18.1 Go from here? There was no update for some time over there so I'm interested in this one but am NOT willing to wipe again. There were too many versions I jumped in and after some time abandoned getting updates. No longer interested in setting up the phone from scratch 2-3 times a year.

AraldoL said:
Is a wipe also needed if I come from your latest June 18.1 Go from here? There was no update for some time over there so I'm interested in this one but am NOT willing to wipe again. There were too many versions I jumped in and after some time abandoned getting updates. No longer interested in setting up the phone from scratch 2-3 times a year.
Click to expand...
Click to collapse
It's not abandoned, i just need to find some time to actually build it. Maybe even today.

That sounds great, thank you very much! Btw with the abandoned ones I meant the ones from EricLev, and before the official CyanogenMod and LineageOS for mako.

I tried to download the build linked in #1 but GDrive says the file is in the owner trash.

mcgyver83 said:
I tried to download the build linked in #1 but GDrive says the file is in the owner trash.
Click to expand...
Click to collapse
gms - Google Drive
drive.google.com

Hi!
Just wanted to say thank you again for this ROM.
Runs absolutely nice, pretty fast compared to others, and I do not miss a thing! Though I only use it for music playback ...

I tried to flash via fastboot the last image but I have this issue:
Code:
fastboot -S 512M update image-mako-lineage-18.1-go-20220831-UNOFFICIAL-fastboot-signed.zip
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.07
Serial Number........: xxxxx (fake number added by me)
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.002s]
Snapshot cancel FAILED (remote: 'unknown command')
fastboot: error: Command failed
Model: MMC 016G92 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.2MB 524kB sbl1
3 68.2MB 68.7MB 524kB sbl2
4 68.7MB 70.8MB 2097kB sbl3
5 70.8MB 71.3MB 524kB tz
6 71.3MB 94.4MB 23.1MB boot
7 94.4MB 117MB 23.1MB recovery
8 117MB 118MB 799kB m9kefs1
9 118MB 119MB 799kB m9kefs2
10 119MB 120MB 799kB m9kefs3
11 120MB 121MB 524kB rpm
12 121MB 121MB 524kB aboot
13 121MB 122MB 524kB sbl2b
14 122MB 124MB 2097kB sbl3b
15 124MB 124MB 524kB abootb
16 124MB 125MB 524kB rpmb
17 125MB 125MB 524kB tzb
18 125MB 126MB 524kB metadata
19 126MB 143MB 16.8MB misc
20 143MB 159MB 16.8MB ext4 persist
21 159MB 1732MB 1573MB ext4 system
22 1732MB 1994MB 262MB ext4 vendor
23 1994MB 2099MB 105MB ext4 cache
26 2099MB 15.8GB 13.7GB ext4 userdata
24 15.8GB 15.8GB 524kB DDR
25 15.8GB 15.8GB 507kB grow

mcgyver83 said:
I tried to flash via fastboot the last image but I have this issue:
Code:
fastboot -S 512M update image-mako-lineage-18.1-go-20220831-UNOFFICIAL-fastboot-signed.zip
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.07
Serial Number........: xxxxx (fake number added by me)
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.002s]
Snapshot cancel FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
Try with latest fastboot version from here: https://developer.android.com/studio/releases/platform-tools

voron00 said:
Try with latest fastboot version from here: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I will try. Just to share I'm using this fastboot version sin 2020 to play custom roms for many devices but never had problems.
Maybe the repartition step I did was not good?
This evening I will try with updated fastboot.

voron00 said:
Try with latest fastboot version from here: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Many thanks, updating adb/fastboot solved my issue!
Many many thanks!

Thanks! Just revived my mako for this. Still this old device don't wanna die.

Tried to flash:
Code:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1472467416 bytes
error: update package missing system.img
Any fix?

image-mako-lineage-18.1-go-20221018-UNOFFICIAL-fastboot-signed.zip (R_asb_2022-10)

voron00 said:
image-mako-lineage-18.1-go-20221018-UNOFFICIAL-fastboot-signed.zip (R_asb_2022-10)
Click to expand...
Click to collapse
This, and also the one in the link above fail to install thanks to a package missing apparently. I have no idea what this does so it could be as simple as me adding a blank file? Not sure. But I'm on a Pemtium M laptop w 2GB RAM so really can't tinker much.
[email protected]:~/Downloads$ fastboot -w -S 512M update image-mako-lineage-18.1-go-20221018-UNOFFICIAL-fastboot-signed.zip-20221225T062808Z-001.zip
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.07
Serial Number........: 02583b3a5310af35
--------------------------------------------
archive does not contain 'android-info.txt'
fastboot: error: could not read android-info.txt

Android 13 build instructions

We are happy to announce that we now have launched AOSP build instructions for Android 13!
The Xperia Open Source Project (Xperia Open Devices) is an initiative created to guide the developers step-by-step on how to build AOSP for their unlocked Xperia devices. Our instructions will show you how to prepare your environment, how to download all the necessary tools, and how to download and configure the code before you can build AOSP images and flash them on your own device.
New AOSP build instructions for Android 13 | Developer World
developer.sony.com

I was wondering if someone has some (successfull) experience on building AOSP for Android 13 and flashing it to the Xperia 1 II?
Also the build guide mentions flashing the vendor (OEM) image to the device at step 7. This image is available for various android versions and devices, but not for Android13 (https://developer.sony.com/develop/open-devices/downloads/software-binaries). So how would this work for the EDO (1 II) where kernel 4.19 (27 July) Android12 is the latest.
Trying myself:
building was successful
1. [fixed i guess] question on what vendor image to choose; found some other answers from jerpelea that a12 can be used.
2. [fixed i guess] flashing not so much; flashing system gives the error 'No such partition.' Has to do with super partitions. Entered fastbootd with the command fastboot reboot fastboot.
3 [ fixed ] flashall from fastbootd says:
Checking 'product' FAILED
Device product is 'pdx203'.
Update requires 'XQ-AT51'.
fixed with fastboot --force flashall command.
4 [ in progress ] Xperia 1 II now boots into Android13 BUT stuck on bootanimation. Can adb in device though....things keep crashing in a loop
AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
Call to getInstalledModules before metadata loaded
any help is appreciated