Develop Bugs

[RECOVERY][ROOT]TWRP 3.1.1-1 Samsung Galaxy J7 MAX 2017 SM-G615F

Unofficial release -TWRP recovery for the Galaxy J7 Max 2017 - SM-G615F MEDIATEK MT6757
{
"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"
}
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE2: THIS DEVICE USES DM-VERITY, ANY CHANGES TO THE SYSTEM PARTITION COULD CAUSE THE DEVICE TO BOOTLOOP. IT MAY BE NECESSARY TO FLASH THE BOOT IMAGE PATCH BELOW.
NOTE: ON ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-g615f_26817
To Root:
Flash the latest Magisk release with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption, dm-verity and mount internal storage (/data) :
1. Boot to Twrp
2. Format the Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install Magisk
5. Reboot
TWRP DEVICE Tree: https://github.com/ashyx/TWRP_Samsung_j7maxlte
Kernel source: https://github.com/ashyx/KERNEL_j7maxlte
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

NOTE: I built this months ago, but forgot to post it up!
.

Great work @ashyx can you please share device tree

I Tested the recovery on my J7 Max and it's working perfectly after flashing the "Boot image patch : no-verity-no-encrypt_ashyx".
one thing i want to tell that the recovery bootlooped(Rebooting the system or Shutting down and again powering on boots into Twrp) the first time i booted it but after flashing Magisk 14.0 and the "no-verity-no-encrypt" patch it works fine.
I've attached the recovery and kernel logs.
Also add a Warning for users to backup their data as i lost all my data after flashing (
and
Thank you for building a TWRP for my device
If you have free time can you please try to build LineageOS for J7 Max

Can you please share the device tree ?

Rumorbox33 said:
Can you please share the device tree ?
Click to expand...
Click to collapse
Yes when I have the opportunity, but be aware twrp device trees are no good for building LineageOS or other custom OS systems.

Thank you for replying.
i just want to study it, upload whenever you have the time

Samsung j700h

[email protected] said:
Samsung j700h
Click to expand...
Click to collapse
No

ashyx said:
Unofficial release -TWRP recovery for the Galaxy J7 Max 2017 - SM-G615F MEDIATEK MT6757
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE2: THIS DEVICE USES DM-VERITY, ANY CHANGES TO THE SYSTEM PARTITION COULD CAUSE THE DEVICE TO BOOTLOOP. IT MAY BE NECESSARY TO FLASH THE BOOT IMAGE PATCH BELOW.
NOTE: ON ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-g615f_26817
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption, dm-verity and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Please post your source code This have been up for roughly a month And we need em....Thank you good sir for your hard work

Hi since j7 plus has same chipset.. Can we use this also? Thanks

ashyx said:
No
Click to expand...
Click to collapse
@ashyx Please read PMs.

TheMadScientist said:
@ashyx Please read PMs.
Click to expand...
Click to collapse
I'm guessing you're asking me to post the kernel source as I'm sure you're aware that TWRP device trees are not subject to any license as they are merely config files?
TWRP source code is freely available from their GITHUB.
However I shall endeavour to post the kernel source and device tree.

ashyx said:
I'm guessing you're asking me to post the kernel source as I'm sure you're aware that TWRP device trees are not subject to any license as they are merely config files?
TWRP source code is freely available from their GITHUB.
However I shall endeavour to post the kernel source and device tree.
Click to expand...
Click to collapse
Thank you and disregard any PMS and such all have been reversed

https://imgur.com/a/LHpfm
I did everything said amd everything worked fine and flawlessly. I wanted to spoof in pokemon go by changing an app to system app after rooting and installing magisk bt it gives the error as shown in pic. please help. i m a total noob. i think this was cause i formatted data partition bt i thought it was part of root process. was that necessasry for me do i.e format data partition? Can nybody tell me why i cant move app to system and what can be done? plsssss
Edit: is it beacause the system is not mounted? How to mount a system using twrp? And what does mounting a system actually mean ?

Yuaan rai said:
https://imgur.com/a/LHpfm
I did everything said amd everything worked fine and flawlessly. I wanted to spoof in pokemon go by changing an app to system app after rooting and installing magisk bt it gives the error as shown in pic. please help. i m a total noob. i think this was cause i formatted data partition bt i thought it was part of root process. was that necessasry for me do i.e format data partition? Can nybody tell me why i cant move app to system and what can be done? plsssss
Edit: is it beacause the system is not mounted? How to mount a system using twrp? And what does mounting a system actually mean ?
Click to expand...
Click to collapse
You can use any file manager with root support to move the apk to /system/app

Rumorbox33 said:
You can use any file manager with root support to move the apk to /system/app
Click to expand...
Click to collapse
Used every app and file manager but to no avail. Finally used twrp itself and boom the problem was solved. Thnks anyway.

Any custom roms for samsung j7 max sm-g615f ??
Plez help

Hey I am using samsumg galaxy j7 2015 model which rooted and have twrp recovery in it so I want to add kernel into it so can you give the file and the method to do so and also the best rom for my device

Hey, i built TWRP 3.2.1-1 for this device including some fixes such as pixel format and many more, will you update the thread if i give you the twrp and device trees or i have to make another thread ?

[RECOVERY][UNOFFICIAL_MOD][DECRYPTION][UPDATED-02-01-2019] TWRP 3.2.3-4 for nitrogen

SUPPORTS ALL TYPES OF USERDATA DECRYPTION FOR BOTH OREO AND PIE ROMS - PASSWORD, DEFAULT_PASSWORD, PATTERN, PIN!!!
SUPPORTS BOTH FULL AND INCREMENTAL OTA UPDATE PACKAGES AUTOMATIC INSTALL!!!​​
Sharing my unofficial TWRP recovery mod for nitrogen which I have started about 2 years ago for hydrogen/helium. For more details visit https://forum.xda-developers.com/mi-max/development/recovery-twrp-3-0-2-2-hydrogen-helium-t3512981...
This is and will be work in progress with fixes and reasonable features to be added.
Download:
(02-01-2019)twrp_v323-4_nitrogen_nijel8-MOD.img​
To install:
- USB connect device to PC
- reboot to fastboot
- open Command prompt/Terminal in the folder with the recovery image and run these commands line by line:
Code:
fastboot flash recovery (XX-XX-XXXX)twrp_v323-X_nitrogen_nijel8-MOD.img
fastboot boot (XX-XX-XXXX)twrp_v323-X_nitrogen_nijel8-MOD.img
or just flash the image with TWRP selecting recovery partition
- reboot from the fresh recovery - it'll take few seconds... let it do its magic to survive MIUI stock recovery replace at system boot. This will happen whenever you install any new ROM.
Done... This TWRP will not go anywhere, /system is untouched so you can get MIUI OTAs, no need to root if you don't want to, no need to flash anything else, MIUI boots just fine having no idea about the recovery, everybody's happy...
NOTES:
ROM install:
- skip wiping Data even if switching different ROMs. Do dirty install, see how it runs, if no problems, great... you saved yourself from doing the initial
setup. If having issues then wipe Data and see how it goes...
- You do not need to wipe/format/factory reset anything before install(see above), especially System and Vendor.
- Do not install any patches like lazyflasher, sound or whatever mods, root-on-system etc that are altering System or Vendor partitions on stock MIUI without installing Magisk first or system will not boot!!!
MIUI OTA Install:
- Let MIUI download update and press "Reboot" when prompted
- Device will reboot to TWRP and start installing it.
- If device reboots to system automatically - all good, update successful
- If device does not reboot you should see some error in red
- Just flash the zip package in Internal storage -> downloaded_rom folder and reboot to system
- Done - you just got your OTA
Decryption:
If MIUI asks for decription password after reboot from TWRP don't panic!
You will most likely never see this but as anything in this live sh*t happens. I for example have seen this only once in hundreds of TWRP and MIUI flashings and reboots to system and it happen after reboot from MIUI OTA testing. Did I mentioned I never do clean installs? Why bother wiping if no post-install issues, right...
Anyway... here is how to get back to normal without loosing any data:
- Reboot back to recovery by pressing and holding POWER + VOLUME UP buttons
- Run Data backup in TWRP
- USB connect device to computer and copy all personal data you don't wanna loose from Internal storage to computer
- DO NOT FORGET TO COPY THE DATA BACKUP YOU JUST MADE FROM TWRP/BACKUPS/XXXXXX TO COMPUTER TOO!!!
- Click Wipe -> Format data -> type yes -> [ENTER]
- Reboot to MIUI and let it encrypt the device. You will see Setup new device wizard when its done
- Reboot back to recovery by pressing and holding POWER + VOLUME UP buttons
- Copy back all your personal data including the recent Data backup from computer to Internal storage -> TWRP/BACKUPS/XXXXXX
- Reboot recovery so TWRP can detect the Data backup you copied
- Restore Data backup and reboot to MIUI
- Done - MIUI should boot without complaining and all your data is intact... even your old lockscreen password and fingerprints should work
Backup/restore:
- normal backup includes Data only, you can always flash what you are running currently to restore boot, system and vendor
- if you have modified boot,system or vendor post install you can back them up to keep your changes
- You do not need to wipe/format/factory reset anything before restore... restore does that for you
Some observations during my extended decryption testing with China and Global MIUIs 8.1 and 9.0, EU MIUIs, MIUIPro, etc:
- Downgrading to ROM with lower security patch level brakes encryption in Android but not in TWRP so just boot back to recovery, backup your data to safe location, format data, restore data back and you are good to go...
- Some times switching back and forth passwords types(pin, pattern etc...) brakes encryption and you loose your data, no way back!!! This is ROM fault and not TWRP. Crypto footer just gets corrupted from Android... I have taken good measures for this not to happen in my TWRP so don't blame recovery if that happens to you...​
Changelog:
[02-01-2019
- hide navbar during running operarions
- more userdata decryption reliability improvements
- Mi bunny is terrified loosing recovery control
- sync with latest Omnirom android-9.0 sources
[01-28-2019
- fix decryption with good user password on next retry if wrong password was entered before that
- improve TWRP persist
- sync with latest Omnirom android-9.0 sources
[01-09-2019
- fix system boot after restoring regular file-for-file backup on ext4 file systems(System and Vendor) - now any backup type works for any partition of any ROM
- sync with latest Omnirom android-9.0 sources
[01-07-2019
- fix installing incremental OTA patching boot - this will start working properly after your first full ROM install with new recovery(boot.img flash)
- fix loading settings from /persist if decryption fails
- made sure we always keep current settings copy on /persist
- remove excessive save settings calls
- some minor improvements
- sync with latest Omnirom android-9.0 sources
[01-05-2019
- fix incremental OTA update automatic install
- sync with latest Omnirom android-9.0 sources
[01-04-2019
- new much smaller Pie kernel built from source with LineageOS 16.0
- much smaller recovery image(see above)
- sync with latest Omnirom android-9.0 sources
[12-29-2018
- improved decrypt routine
- some minor fixes and improvements
- sync with latest Omnirom android-9.0 sources
12-28-2018
- much improved and reliable decryption routine for preventing crypto footer corruption and loosing all your data - this update is highly recomended
- fix Android 9.0 userdata decryption with custom user set password, pin or pattern
- more reliable format data routine for crypto footer support
- disable useless and sometime buggy reboot check for system size(No OS installed msg)
- sync with latest Omnirom android-9.0 sources
12-27-2018
- migrate to Android-9.0 for android tree and TWRP sources
- switch to MIUI Pie prebuilt kernel
- speed up userdata decryption
- fix userdata decryption for Android-9.0 with default password only. At this time userdata decryption wit user set password is not supported! Working on it...
- sync with latest Omnirom android-9.0 sources
11-25-2018
- fix survival routine hang/bootloop after openrecoveryscript execution(OTA)
- improved decryption handling
11-23-2018
- fix userdata decryption - no more inaccessible userdata in TWRP
- fix vendor missing from partitions to restore list in some cases
- fix TWRP bootloop trying to apply survive magic in some cases
- finaly fix crypto footer for F2FS partition formating(tested and working!!! - you can format userdata in TWRP without any system boot issues now)
- skip survive magic for good ROMs to speed up reboot
- translatable and more user friendly survive system boot screen - If you want to help translate and PM me these strings:"
Code:
<!-- Survive system boot strings -->
<string name="survive_line1">Checking if TWRP will survive system boot!</string>
<string name="survive_line2">Please, wait...</string>
- sync with latest Omnirom android-8.1 TWRP sources
11-12-2018
- fix TWRP system boot survive - no need to flash anything to prevent stock recovery reflash at MIUI boot
- fix crypto footer for F2FS partition format - need no more fastboot format userdata for system boot with forced encription enabled(needs testing)
- fix error when creating ext2, ext3, or ext4 filesystem in some cases(needs testing)
- some minor fixes and optimizations
- kernel compiled from source at build time
- build with latest Lineage OS 15.1 sources
- sync with latest Omnirom android-8.1 TWRP sources
Github sources:
NITROGEN TWRP device tree
TWRP Mod repo
Kernel source
Thank you:
TeamWin for the initial device tree!
Omnirom/TeamWin for the TWRP source code!
@topjohnwu for the magiskboot source code!

Yes, You finally stepped in.

you save my life thankyou sir. unlocked bootloader today as i waited for 720 hrs. as i known i can skip by 9001 mode i just wait the official unlock to play safe. missed you so much since max1 thankyou sir

Just noticed on 4PDA forum there is a bug when you try restore vendor is missing from the list of available partitions at first... Well, it's not a bug... It's something I had to add for hydrogen...
Yeah, I know exactly what you guys are talking about... Back in the days when I was trying to bring treble to Max1 I added some code to detect in the fly if vendor partition is available on the running device so I can hide it in UI if ROM was Nougat or show it if was treblelized. I forgot about it and now it causes inconvenience on Max3. Will get it fixed in the next release.
Thaks for the reminder 4PDA guys...

nijel8 said:
Just noticed on 4PDA forum there is a bug when you try restore vendor is missing from the list of available partitions at first... Well, it's not a bug... It's something I had to add for hydrogen...
Yeah, I know exactly what you guys are talking about... Back in the days when I was trying to bring treble to Max1 I added some code to detect in the fly if vendor partition is available on the running device so I can hide it in UI if ROM was Nougat or show it if was treblelized. I forgot about it and now it causes inconvenience on Max3. Will get it fixed in the next release.
Thaks for the reminder 4PDA guys...
Click to expand...
Click to collapse
I hope that you are able to create an un-official build of LineageOS for Mi Max 3
I thank you for your time for creating this un-offical twrp build as its faster than the official one
have a great week!

Going to keep an eye on this.
300 hours left for my Mi Max 3, will flash this when I unlock.
What's different between this and official TWRP may I ask?

omer919 said:
I hope that you are able to create an un-official build of LineageOS for Mi Max 3
I thank you for your time for creating this un-offical twrp build as its faster than the official one
have a great week!
Click to expand...
Click to collapse
Don't know if it's faster but should be more bugs free...
AsadP2013 said:
...
What's different between this and official TWRP may I ask?
Click to expand...
Click to collapse
Read first post and changelog, then click the link for more info and read the looong changelog there as well.
But if I have to summarize the dev is listening and every bug terminated right away...
Oh... and the most important thing... Dev has the device and runs on it only what he builds himself... You get what the dev gets and he hates it when something's not working as intended.
Hope this helps...

nijel8 said:
Don't know if it's faster but should be more bugs free...
Read first post and changelog, then click the link for more info and read the looong changelog there as well.
But if I have to summarize the dev is listening and every bug terminated right away...
Click to expand...
Click to collapse
Thanks, no I have had a look but in short, what would you say?
Do you reckon that it has more features and is capable of doing slightly more?
Basically, should I use this TWRP over official as I'm a modder/tweaker?
Or should I flash it for the sake of it providing more than official?

Ohh Sir @nijel8 I've tried, but incremental OTA updates does not installable with this rec.
(Or I am making a mistake.)

JulianJenner said:
Ohh Sir @nijel8 I've tried, but incremental OTA updates does not installable with this rec.
(Or I am making a mistake.)
Click to expand...
Click to collapse
More specifics, please, recovery.log. What not installable means?
The only reason OTA would not install is if the updater-script checks boot partition checksum. Can you post its content?
I would test it myself but I am away from home right now...

Thx. I am back to miui with chinese PC suite (full clean install)
I will try again. When I have time again.
I've found on baidu a new TWRP a lot of settings and partition backup
http://www.mediafire.com/file/04xqp...-1030-XIAOMI_MAX3-CN-wzsx150-fastboot.7z/file
{
"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"
}
小米MIX标准版4GB128GB银色MIUI10中国开发者8.11.13

JulianJenner said:
Thx. I am back to miui with chinese PC suite (full clean install)
I will try again. When I have time again.
I've found on baidu a new TWRP a lot of settings and partition backup
http://www.mediafire.com/file/04xqp...-1030-XIAOMI_MAX3-CN-wzsx150-fastboot.7z/file
View attachment 4642012
View attachment 4642013
View attachment 4642014
View attachment 4642015
小米MIX标准版4GB128GB银色MIUI10中国开发者8.11.13
Click to expand...
Click to collapse
One thing I should've mentioned... Since recovery hardware decryption is not fixed yet after OTA update.zip is downloaded you have to move it to nonencrypted accessable location like external SD Card or OTG reboot to recovery and flash it manually.
Another thing I should mention is although decryption with default passwords is not working decryption with user password should work. Don't ask me how to switch from default to user password encryption... I am not familiar with MIUI.

I just testing. No problem.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.11.13

nijel8 said:
One thing I should've mentioned... Since recovery hardware decryption is not fixed yet after OTA update.zip is downloaded you have to move it to nonencrypted accessable location like external SD Card or OTG reboot to recovery and flash it manually.
Another thing I should mention is although decryption with default passwords is not working decryption with user password should work. Don't ask me how to switch from default to user password encryption... I am not familiar with MIUI.
Click to expand...
Click to collapse
I think, there is not the encryption/decryption is the bigger problem.
Max3 MIUI ROMs contains a scrip, that it rewrite MiRecovery, but this action occurs across boot. Earlier rewriting supervened after system installing/flashing. So far, we could have avoided this with Lazyflasher or something. At the moment, we install TWRP versions in vain, because after successfully TWRP install, MIUI system immediately restore MiRecovery at rebooting.

In Mi Max 1 I solved the problem of recovering stock recovery by deleting the file "Recovery from boot.p" in the system directory. You must do this before the first start of the system.

Guys, you have system verify in the kernel on Oreo so LazyFlasher doesn't work on Oreo and deleting files in system causes bootloop. The new approach for disabling recovery replace is to patch rc scripts in boot image. That's how this recovery does it.
Edit: BTW vendor is verified as well so modifying anything in that partition causes bootloop as well...

nijel8 said:
Guys, you have system verify in the kernel on Oreo so LazyFlasher doesn't work on Oreo and deleting files in system causes bootloop. The new approach for disabling recovery replace is to patch rc scripts in boot image. That's how this recovery does it.
Edit: BTW vendor is verified as well so modifying anything in that partition causes bootloop as well...
Click to expand...
Click to collapse
"nice" new security items...

Installed the recovery today. It went well. When I tried to boot to the system afterward it started running OpenRecoveryScript 'checking if TWRP will survive system boot!'. It has been over 2 hours. Is this normal? If Any way to stop it? Rebooting doesn't stop it.
EDIT: Figured it out. Didn't have writer permissions for /data. Had to reformat it. After that it went ok.

lowfat said:
Installed the recovery today. It went well. When I tried to boot to the system afterward it started running OpenRecoveryScript 'checking if TWRP will survive system boot!'. It has been over 2 hours. Is this normal? If Any way to stop it? Rebooting doesn't stop it.
EDIT: Figured it out. Didn't have writer permissions for /data. Had to reformat it. After that it went ok.
Click to expand...
Click to collapse
Doesn't sound right. /data should not affect that. Post any recovery related log you find in /cache, please...

Thanks for the recovery mod. I think that a translation into Russian will eventually be added. I am also grateful to nijel8 for his work!

Development [RECOVERY] [UNOFFICIAL] TWRP-3.5.1 [20210702]

{
"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"
}
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
FEATURES AND FIXES:
No need to reboot TWRP after flashing ROM, to flash gapps or any other zips. All zips you flash after a ROM will automatically go to the new slot.​
No need to flash TWRP everytime after flashing a ROM. TWRP automatically flashes itself after a zip (Controllable via a toggle)​
Supports Hentai OS encrypted devices​
Supports flashing MIUI zips​
Supports Vibration​
Supports wiping data without wrecking encryption. ​
BUGS:
On encrypted devices, if u unmount and remount /data, it will show garbage files in storage. This is because of metadata encryption and to fix it, reboot recovery.
SUPPORTS AND TESTED ON:
Mi11x (aliothin)
UNSUPPORTED (BUT MAY WORK):
Poco F3, Redmi K40 (alioth)
FLASHING INSTRUCTIONS:
Boot into attached boot.img using the following command:
Code:
fastboot boot twrp-aliothin.img
Once booted, go to Advanced -> Press "Flash current booted TWRP"
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
CREDITS:
@Nebrassy for original TWRP and device tree. I also repurposed some of his commits from gerrit.
SOURCE CODE:
Kernel (Prebuilt): https://github.com/ArrowOS-Devices/android_kernel_xiaomi_alioth
DOWNLOADS:
https://drive.google.com/file/d/1oY5WxfXYPRLumCcaPPFGuq9OhtB3CM_X/view?usp=sharing
MD5:- 0909f61c83ce9876843dabba5bf1247e
TELEGRAM GROUP LINKS:
https://t.me/PocoF3GlobalOfficial
https://t.me/pocoF3GlobalUpdates

Reserved

Reserved

ayy pro <3

Yay Yahoo

Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."

I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...

vasishath said:
Great work.
Click to expand...
Click to collapse

blinoff82 said:
Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."
Click to expand...
Click to collapse
Twrp reflashes itself after every zip flash, hence it removes magisk, you can uncheck inject twrp option to flash tho.

@vasishath
Hello,
First of all thank you for developing a version of TWRP.
I have a little problem with this one: failed to mount: system_root, vendor, odm
Unable to find partition for path storage
I can't install TWRP ...
I'm on the weekly xiaomi.eu
Here are the issues I'm currently having with your version of TWRP.

Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot

Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
John Wu recommands direct install from magisk app

vasishath said:
John Wu recommands direct install from magisk app
Click to expand...
Click to collapse
TWRP not installed after installing custom ROM. Please check.

deif102 said:
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot
Click to expand...
Click to collapse
To much work, when i can simply flash it in twrp after i flash the rom, it was that easy in past times...
But can i uncheck inject before flashing and then check it again and flash current booted TWRP as in the beggining?

Which rom did u flash ?
blinoff82 said:
TWRP not installed after installing custom ROM. Please check
Click to expand...
Click to collapse

vasishath said:
Which rom did u flash ?
Click to expand...
Click to collapse
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)

blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..

NE0HP said:
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..
Click to expand...
Click to collapse
Of course this toggle was turned on before flashing (by default).

blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
It appears to me that the ramdisk-files.sha256sum file was removed after u flashed the ROM. That caused the TWRP flashing to fail. Does your ROM's zip modify the current running ramdisk in anyway ?

Will future Miui builds now be using this version of twrp? if this is the case i wont need to flash it right now.

Development [Recovery] [A325x] [Stable-ish, Unofficial] TWRP 3.7.0_12.1 - Galaxy A32 4G

{
"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"
}
Code:
#include <not_my_phone.h>
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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 Recovery
* 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.
*/
TWRP 3.7.0_12.1 - Samsung Galaxy A32 4G​
Current Status: Stable-ish
Supported Models:
SM-A325F: tested by @Long266 .
SM-A325M: tested by @Melky777 .
SM-A325N: not tested.
Bugs known so far:
TWRP cannot decrypt userdata if you set lockscreen. (one said it works, other it doesn't, so idk I'll just leave it here, YMMV)
Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
USB-OTG
<!> There can be many more bugs unknown to me and testers. Report as soon as you face problem.
<!> PSA: I don't have the device to verify some of these bugs.
Download:
TWRP (3.7.0): https://github.com/almondnguyen/twr...a32-20230208/TWRP-3.7.0_12.1-a32-20230208.tar
Samsung USB Driver: https://developer.samsung.com/mobile/android-usb-driver.html
Odin (3.14.4): https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
Disable VBMeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
(Optional) Root using Magisk: https://github.com/topjohnwu/Magisk/releases/
Install:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
Go back, go to Developer Settings.
Turn on OEM unlock toggle.
Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
Your device will boot into download mode with a warning. Accept it.
Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
‎
When it reboots to OS, finish setting up your device.
Double check to make sure OEM Unlock is still ON.
‎ ‎
 
Preparing for the installation:
Download everything above onto your PC.
Install Samsung USB Driver.
Open Odin.
Connect your phone to your PC. There should be a COM entry on the top.
Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
‎  
 
Installing:
Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: TWRP TAR file.
Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have TWRP up and running now.
‎  
 
Post-Installation:
MUST: Trigger Multi-disabler.
In TWRP, go to Advanced > Terminal.
Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
Run multidisabler again.
Go to main screen. go to Wipe > Format Data, type yes then swipe.
Reboot to Recovery. Now you can do other stuff.
 
Should: Backup all vital partitions:
In TWRP, go to Backup
Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, Ofox and the likes)
Download the tar recovery image, then extract it to get recovery.img
Copy it to phone, then reboot to TWRP (Combo is Power + Volume-up)
Go: Install > Install image > select recovery.img file > select Recovery
Swipe to confirm flashing.
If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
GSI and related stuff:
GSI should be directly flashable now. Big credit to @Long266
Install TWRP, do all the instructions.
Download a GSI. Phh's is a good start.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
If downloaded a compressed file (the extension is not .IMG; e.g: `gsi.img.gz` ), extract it to get an IMG file. Copy the IMG file to your phone.
Reboot into TWRP.
Tap Install > Install Image > Select your GSI .img file.
Select System Image, then flash.
If previously you were on stock, Wipe > Format data.
Reboot System.
Profit.
Source codes:
Kernel: https://github.com/long266/android_kernel_samsung_a32/tree/s
TWRP device: https://github.com/almondnguyen/twrp_device_samsung_a32/tree/twrp-12.1
Credits:
Devs involved in the making and maintaining of TWRP, twrpdtgen, Magisk and base software.
All the Testers.
@Long266 as tester, collab-dev.
@ianmacd for multidisabler.
@afaneh92 for a32x base tree and MTK-Samsung multidisabler.
@dronkit and @Mighty_Rearranger for Magisk-IMEI fix on MTK devices.
@klfld for GSI installation guide.
Older Release(s):
TWRP 3.6.2_12.1-20220703: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/tag/TWRP-3.6.2_12.1-a32-20220703
TWRP 3.6.2_12.1-20220528: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/twrp-3.6.2_12.1/
TWRP 3.6.1_11: https://github.com/almondnguyen/android_OTA/releases/TWRP-3.6.1_11-a32-B20220324
Footer Infos:
Status: Beta
Current Stable Version: 3.7.0_12.1
Created: 2022-03-24
Last Updated: 2022-07-03

chmod 550 /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI must run on OS, not TWRP, since TWRP cannot mount /mnt

I can't install large IMG files to internal memory? For example a gsi?

Melky777 said:
I can't install large IMG files to internal memory? For example a gsi?
Click to expand...
Click to collapse
I should clarify that I don't own the device and all the testing was/is done by @Long266 .
These specific questions should be inquired to him instead (on his thread here: https://forum.xda-developers.com/t/...hawk-recovery-project-3-1-2021-03-24.4420469/ ).
Anyways, the bug that you are mentioning means that you can't flash images FROM internal SD card. GSI and image stuff should be flashable from other places like external SD or cache. Zip files are so far working as intended (as is they are flashable from anywhere).
To be fair, there could be flaws in his testing methodology and you should try it yourself.

Thanks Bro
I will owe the test of the A325M. I have no SD card at the moment.

Build 2022-03-25 changes:
Add backup entry for NVRAM, so in case Magisk messes up you still have a working copy intact.
Fix flashing image causing file size exceeded limit.

Updated TWRP Link, previously pointing to dead end.

It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
can u send recovery.log ?

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
just skip NULL errors

How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?

YellowSM said:
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
Click to expand...
Click to collapse
You can use the "install Image" under TWRP.
From the <!> For more info part, download .img file instead, copy it to your phone. Then go to TWRP > Install > Install Image > select TWRP img > select Recovery to flash.
If you've done, Post-installation steps are unnecessary to do again.
edit: upgrade section added to main post.

How to deactive KC Client and
Knox Enrollment Service?

Hi, I wanted to try a GSI with this, is it safe to try it? Thanks for developing this TWRP, I can help with testing too.

Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.

klfld said:
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
Click to expand...
Click to collapse
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22

Long266 said:
can u send recovery.log ?
Click to expand...
Click to collapse
On the same day I removed the twrp and blocked the bootloader.

Melky777 said:
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Click to expand...
Click to collapse
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
To flash the GSI you have to rename the .img file to system.img, put it in the same location than the zip and flash the zip. I have the scripts inside the zip to check if it didnt do anything weird and the source code seems safe, tried two GSIs today.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
For file transfer i'm using ADB with this tool, it's even faster than MTP somehow Python ADB File Explorer
EDIT: Uploaded vendor.img with the overlay for this device, ill push the changes to github later.
Download here: vendor.img

klfld said:
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
Click to expand...
Click to collapse
Very good job!!!
Makes a topic, I think I'm not the only one who wants to install a GSI.

[ROM][UNOFFICIAL][UNIFIED] VoltageOS v2.2 [Android 13][January 23th, 2023]

{
"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"
}
VoltageOS 13.0 | Tiramisu for Mi A2 Lite (daisy)​
ABOUT
Greetings, interested users! You have reached the gateway of a simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences, with just the right dab of customizations. Be it requiring safetynet for banking or payment apps to receiving the latest security patches from Google as soon as they're released, we've got you covered. It doesn't end there. Sit back, relax and let the system theme your device according to your preferences with Monet support. Step in and begin your journey with Voltage OS.
Features
Pure AOSP
Latest Security Patches
Google Monet
SafetyNet
More info: HERE
Telegram Voltage: Group
If you like our work you can buy us a cup of coffee
*TogoFire Maintainer Daisy
*PIX: [email protected]
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOAD:
VoltageOS 2.2 230123: CLICK HERE
SHA256: 3c21e3f7c2b8c6f90f8c7388e0a481c6e842f313d2dfd04c5f6c6e5fcda18385
Gapps $hit Package (Recommended): LiteGapps | Microg | MindTheGapps
Recovery: HERE
If you use instagram or any $hit like facebook, use this: LINK
Installation Guide​Clean Flash
1) If you are coming from any MiuiROM, GSI, or any other PortROM, edl miflash from firmware 10.0.18.0 or 11.x.x is mandatory.
2) Edl firmware 11.x.xx or 10.x.xx (install firmware via miflash if needed)
3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs).
4) Reboot to recovery
5) Boot to Recoovery
6) Format Data--Yes
7) Reboot to recovery
8) Wipe data, system, dalvik cache, internal storage.
9) Install ROM
10) Install TWRP
12) Reboot to recovery
13) Install LiteGapps (optional)
16) Install Magisk (optional)
17) Reboot to system
Dirty Flash
1) Backup Everything (Most Important)
2) Download ROM
3) Boot to TWRP (Power and vol+; or Advanced Restart > Recovery)
4) Backup Data partition (optional)
5) Install the 'update' ROM
6) Install TWRP ZIP (optional)
7) Then reboot to recovery. (Note: in current recovery the slot changes by itself, no longer need to change manually)
8) Install GApps that you've used to installed, and Magisk.
9) Wipe dalvik and reboot
10) Reboot to system
GUIDE FULL
Link​
ROM Source: https://github.com/VoltageOS
Source: Kernel & Device & Vendor
Support Links:​TogoFireWork Channel
TogoFireWork Group
McQuaidLab
XDA:DevDB Information
ROM OS Version: Android 13.0 | Tiramisu
ROM Kernel: Linux 4.9.X
ROM Firmware Required: 10.0.18, 11.0.04, 11.0.16 or greater
Based On: AOSP

reserved!

reserved...!!!

@TogoFire
Hi mate. Thanks for your efforts. I'm on SyberiaOS A13 version. Do i still need to flash firmware or can i install directly from recovery with format data system etc.? Thanks.

dr.bahaeddin said:
@TogoFire
Hi mate. Thanks for your efforts. I'm on SyberiaOS A13 version. Do i still need to flash firmware or can i install directly from recovert with format data system etc.? Thanks.
Click to expand...
Click to collapse
Being firmware greater than or equal to 10.0.18, it's fine. If it's coming from a Lupe rom, then just go straight to install the rom

Is this pre-overclocked? What are the clocks?

ortizjammet said:
Is this pre-overclocked? What are the clocks?
Click to expand...
Click to collapse
McQuaid Lab
McQuaid Lab Kernel: https://t.me/McQuaidKernel Download & Changelog: LINK Kernel Source If you like our work you can buy us a cup of coffee *TogoFire Maintainer *PIX: [email protected] Orangefox old OrangeFox Recovery Project...
forum.xda-developers.com

It will be helpful is guys share your experience about this rom...

New update!
Small important fixes made.
Changelog of the last commits: IMG | DT
Enjoy!

@TogoFire thanks again for the update. I wonder how can i enable Google auto fill? Apps dont recognize my saved singin infos.

dr.bahaeddin said:
@TogoFire thanks again for the update. I wonder how can i enable Google auto fill? Apps dont recognize my saved singin infos.
Click to expand...
Click to collapse
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this.

TogoFire said:
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this
Click to expand...
Click to collapse
TogoFire said:
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this.
Click to expand...
Click to collapse
If you are so focused on security, why is your ROM UNofficial?
Will it become OFFICIAL in the near future so that it is also suitable as a daily driver?

cappuccini said:
If you are so focused on security, why is your ROM UNofficial?
Will it become OFFICIAL in the near future so that it is also suitable as a daily driver?
Click to expand...
Click to collapse
Since when does it have to be official to be safe?
There are so many roms whether official or not that aren't good, so this has no relevance.
The trees are opensource, by the way.
I'm not a buildbot. So my builds are decent.
I already keep Official Xtended. It's enough for me. I don't have time to keep two official ROMs.

TogoFire said:
Since when does it have to be official to be safe?
There are so many roms whether official or not that aren't good, so this has no relevance.
The trees are opensource, by the way.
I'm not a buildbot. So my builds are decent.
I already keep Official Xtended. It's enough for me. I don't have time to keep two official ROMs.
Click to expand...
Click to collapse
...I'm sure all is as you write, however, I think it is wrong to equate Official and UNofficial. For OFFICIAL ROMs there are rules, which among other things also serve the security of the users, and not every user can read and check a source code...
Thank you for your statement and your certainly also very good work!

cappuccini said:
...I'm sure all is as you write, however, I think it is wrong to equate Official and UNofficial. For OFFICIAL ROMs there are rules, which among other things also serve the security of the users, and not every user can read and check a source code...
Thank you for your statement and your certainly also very good work!
Click to expand...
Click to collapse
Np.
These rules are useless to tell you the truth. I maintain Xtended Official, so I have an idea of how it works. It's like I told you. Being decent construction, it doesn't have any problems.
The only thing they require is that you know how to cherry-pick, know how to author commits, and have built at least one unofficial rom of theirs, and have at least a notion of how to fix bugs, and respect colleagues. They will look at your history and see how you behave. These rules will not prevent a buildbot.

TogoFire said:
Np.
These rules are useless to tell you the truth. I maintain Xtended Official, so I have an idea of how it works. It's like I told you. Being decent construction, it doesn't have any problems.
The only thing they require is that you know how to cherry-pick, know how to author commits, and have built at least one unofficial rom of theirs, and have at least a notion of how to fix bugs, and respect colleagues. They will look at your history and see how you behave. These rules will not prevent a buildbot.
Click to expand...
Click to collapse
...the requirements of the individual ROMs seem to differ a lot, with LOS for example they are supposed to be significantly higher.
what about the XDA rules? These also have to be complied with in an official ROM. what about banking apps and other security-critical apps in case of damage? Metadata is stored with every login. Even the proprietary messenger WhatsApp registers a custom ROM and refuses support.
In a Samsung thread a maintainer wrote that the unofficial ROM is only for testing.... A very difficult topic for me, ultimately everyone must decide for themselves who they trust.
Thanks for the insight into the world of developers and best regards

Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...

norva said:
Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...
Click to expand...
Click to collapse
...this installation guide has been very helpful to me:
[DEPRECATED] Detailed Installation Guide for Custom Roms (Mi A2 Lite - Daisy)
Heya, This is a guide aimed on helping you to switch to a custom rom from the stock firmware. For any questions, feel free to join our Telegram groups. PREREQUISITES 1) Stock rom recommended by the maintainer of the rom that you want to flash...
forum.xda-developers.com
P.S. I am currently testing MSM Xtended v4 with LiteGapps core, there were no problems during installation.

norva said:
Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...
Click to expand...
Click to collapse
Can it be that you have installed GApps for Android 12? This ROM is Android 13...

SOLVED! YEAH! Took me hours but finally got it!
So either the new stock rom (daisy_global_images_V11.0.21.0.QDLMIXM_10.0) did it or it is related to the installation with adb sideload or from SD card which caused my issue (I finally simply copy the installation zip files through USB while TWRP is active on the phone and gives access to the memory from computer, and installed them using the dedicated button (no adb sideload)).
Time to test now
@cappuccini : yeah I read this guide and had the android 13 gapps version (but you are right, it took me a while to understand it was the folder 33 on sourceforge...).