[ROM][UNOFFICIAL][LineageOS][19.1][dragon] -> 2023-01-11 (DISCONTINUED)

[ROM][UNOFFICIAL][LineageOS][19.1][dragon] -> 2023-01-11 (DISCONTINUED) - Pixel C Android Development

{
"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 19.1
Android 12
lineage-19.1-20230111-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- Camera is not working yet.
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- As it looks like Widevine L1 has been revoked by end of August 2020.
- Maybe more issues ..
Installation:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions !
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (25.2)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Enjoy 12
Android 11
lineage-18.1-20220216-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (21.x)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Upgrade from previous lineage-18.x builds:
1. Boot into TWRP
2. Install ROM.zip
3. Re-Install Magisk 21.x
4. Wipe CACHE and DAVLIK
5. Reboot into system
Enjoy 11
Android 10
lineage-17.1-20201211-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.
system-as-root (SAR)
For gapps installation issues and more information ..
Pls read first .. https://forum.xda-developers.com/showpost.php?p=80693701&postcount=1350
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (20.x+)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Upgrade from previous lineage-17.1 builds:
1. Boot into TWRP
2. Install ROM.zip
3. Wipe CACHE and DAVLIK
4. Reboot into system
- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)
Enjoy TEN
Android Pie
lineage-16.0-20191017-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- Encryption seems not to work - and has not been tested. -> Pls do not encrypt your data partition yet !
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip to remove pattern/pin or password.
Installation:
1. Boot into TWRP (latest available version)
2. Wipe system, cache, dalvik and data partitions ! ( If you have encrypted /data partition - pls "format" /data via TWRP first ! )
3. Install lineage-16.0-201Yxxyy-UNOFFICIAL-dragon.zip
4. Install Opengapps
5. install Magisk.zip (tested with 18.x)
6. Reboot into system ..
- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)
And big thanks to @NYCHitman1 (Dirty Unicorn) !
Without his work the Android Pie project would not have been possible !
I have uploaded the last official Lineage Oreo build to androidfilehost.com ..
lineage-15.1-20200221-nightly-dragon-signed.zip - -> DISCONTINUED
SOURCES:
https://github.com/followmsi/manifests/tree/dragon-lineage-18.1
DOWNLOADS:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
https://androidfilehost.com/?w=files&flid=289293
Enjoy LineageOS on your Pixel C .. [/B]

RESERVED

Here you are ..

TWRP loop for me. Installs with no errors but won't boot into the os
I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.
Tried wiping again and flashing back to aosp and having the same issue.
Any thoughts?
edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today

minieod said:
TWRP loop for me. Installs with no errors but won't boot into the os
I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.
Tried wiping again and flashing back to aosp and having the same issue.
Any thoughts?
edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today
Click to expand...
Click to collapse
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.
EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..

Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy

followmsi said:
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy [/QUOT
Is the nav bar laid out like stock
Click to expand...
Click to collapse

followmsi said:
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.
EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..
Click to expand...
Click to collapse
Hey follow
Yep did all of that. Formatted system, flashed boot.img, and no issues with mtp prior to the boot loops.
I went ahead and did a complete userdata reset and am sampling the O DP1 now ..I'm sure it'll work fine when (if) I come back to 7.x

Officialness
Thanks for building this. Hoping to try it out this weekend.
I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.

gaufres said:
Thanks for building this. Hoping to try it out this weekend.
I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.
Click to expand...
Click to collapse
You are not the first asking me this question ..
Here some more information ..
https://wiki.lineageos.org/submitting_device.html
Who is the maintainer ? .. me
- Changing vendor stuff .. monthly
- Applying kernel patches .. monthly
- Applying possible device tree patches and changes .. monthly
- Etc.
Here is the manifest for LOS ..
https://github.com/followmsi/manifests/tree/dragon-lineageos-cm-14.1
Also for the people who like to build their own verison
- As you may see we are removing 2 LOS repos today, due to build errors.
- This needs to be fixed on code level first - commited on LOS github.
- The stock google vendor.img needs to be integrated into the LOS Installer
Still not clear how this is done for "official" lineageos .. also from legal point of view.
Actually I need to get information here ... How is this done for other ROMs having a dedicated vendor.img ?
- The missing integrated kernel building was impemented a few minutes before
https://github.com/followmsi/androi...mmit/316a7e0e87b191bcf11b8de55778ddec83fac2f8
https://github.com/followmsi/android_kernel_tegra/commit/3e3e24c41db74693efc2fc74efaf6286b1c06013
You see there a few issues left ..
The ROM works perfectly but its not ready to be official yet.
Don't want to force and push a go live now .. No need to rush !
Hope you have a better understanding now ..
Cheers

Reuben_skelz92 said:
followmsi said:
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy [/QUOT
Is the nav bar laid out like stock
Click to expand...
Click to collapse
No !
The OMS version is the same like lineageOS but including OMS - to be ready to install substratum .. etc.
Made a version for Nexus 10 as well .. it seems to work fine.
Just have installed the ROM .. works fine - but did no special customizations or anything else.
Hope this helps ..
Click to expand...
Click to collapse

Debugging bootloop
followmsi said:
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
Click to expand...
Click to collapse
Unfortunately this is also bootlooping for me. I've tried the steps above.
How can I help debug this? I was not able to use logcat. Does logcat work for you?

gaufres said:
Unfortunately this is also bootlooping for me. I've tried the steps above.
How can I help debug this? I was not able to use logcat. Does logcat work for you?
Click to expand...
Click to collapse
You did flash boot.img via fastboot ?
The ROM installation had no errors ?
What version of bootloader are you using .. .50 for 7.1.2 ?
Do you see the LOS logo (boot animation) when you boot-loop ?
Are you able to make a md5 hash ..Or similar to compare ?
File corrupt ?
Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.
I am testing several ROMs and kernels in the last days .. no problems at all.
EDIT:
Which version of TWRP ?
EDIT2:
For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)

Re: Debugging bootloop
followmsi said:
You did flash boot.img via fastboot ?
Click to expand...
Click to collapse
Yes. No errors.
followmsi said:
The ROM installation had no errors ?
Click to expand...
Click to collapse
None.
followmsi said:
What version of bootloader are you using .. .50 for 7.1.2 ?
Click to expand...
Click to collapse
I think so. Version 7900.50.0 from n2g47d.
followmsi said:
Do you see the LOS logo (boot animation) when you boot-loop ?
Click to expand...
Click to collapse
It doesn't get that far.
I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.
But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).
followmsi said:
Are you able to make a md5 hash ..Or similar to compare ?
Click to expand...
Click to collapse
The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash
Code:
d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902
The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash
Code:
cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931
followmsi said:
Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.
Click to expand...
Click to collapse
I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!
followmsi said:
I am testing several ROMs and kernels in the last days .. no problems at all.
Click to expand...
Click to collapse
Good. Weird.
followmsi said:
Which version of TWRP ?
Click to expand...
Click to collapse
Your build of 3.1.0-0.
followmsi said:
For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)
Click to expand...
Click to collapse
Thanks for the explanation. So it might be boot.img given the boot sequence I described above?

I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.
Now that I've got it running (OMS variant) it's great.

gaufres said:
Yes. No errors.
None.
I think so. Version 7900.50.0 from n2g47d.
It doesn't get that far.
I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.
But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).
The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash
Code:
d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902
The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash
Code:
cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931
I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!
Good. Weird.
Your build of 3.1.0-0.
Thanks for the explanation. So it might be boot.img given the boot sequence I described above?
Click to expand...
Click to collapse
[HashChecker]
[File]/storage/emulated/0/download/lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip
[MD5]C79F1066186FF36C55643E264B3647E2
[SHA1]4DDD0A811FE22359D745335AA563023E95E808D3
[SHA256]D124B4048F096317F593FA5DBF313CEAEBBDDD4352F0422276A86FD5F6707902
At least the sha256 matches
Good bootloader
Good TWRP version ..
Do you install supersu at last step of your installation procedure ?
After you did install the ROM in TWRP, pls install supersu.zip (2.79 -sr3) as last step.
It will boot twice for the first time .. but then it should boot normally.

badwiring said:
I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.
Now that I've got it running (OMS variant) it's great.
Click to expand...
Click to collapse
The SetupWizard is related to gapps .. the beans version seems to run perfectly.
Opengapps seems still to have issues on certain devices.
Will check supersu topic ..
Thanks for the feedback !

badwiring said:
I always get the TWRP bootloop if I boot before installing SuperSU.
Click to expand...
Click to collapse
followmsi said:
Do you install supersu at last step of your installation procedure ?
Click to expand...
Click to collapse
Thanks both. That's it.
No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK

gaufres said:
Thanks both. That's it.
No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK
Click to expand...
Click to collapse
Cool !
Found the issues as well ..
It's related to DM-verity .. even some config is missing.
Or the overwrite of build_fingerprint is related.
Need to investigate ..
Both supersu and magisk are removing the DM-verity checks in ramdisk.(boot.img)
As I always install supersu, I never realized.
Just compiling a new version .. changed the sources.
https://github.com/followmsi/androi...mmit/aae5804e75f4133ec82253cf6b2afbe39e46a56a
Removing DM-verity from fstab .. should solve this issue, also without supersu.
At later stage we can enable again, if it's working fine.
Thanks for your help testing ..
Cheers

New release ..
lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip
Changes:
- Integrated kernel compiling - using DU branch
- disabled DM-verity -> should fix proper booting even without supersu/magisk.
- General LineageOS changes -> fresh repo sync from today .. https://download.lineageos.org/
Installation:
1. Boot into TWRP
3. Install lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip
4. install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system ..
- The ROM installer will keep your existing gapps installation.
- If you had SuperSu installed before you need to install it again - as we overwrite the boot.img completely.
A new OMS version will come later ..
Enjoy ..

Related

[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!

[ROM][UNOFFICIAL][gts4lvwifi][9] LineageOS 16.0

-- bit more friendly stock -> lineage instructions --
1. Unlock the bootloader
- Connect to WiFi network
- Enable OEM Unlock in developer options
- Turn off the tablet
- Boot to download mode manually by plugging in USB and holding all the buttons for few seconds
- Follow instructions on the screen
2. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
3. Flash custom VBMeta image ( https://dl.twrp.me/gts4lvwifi/vbmeta.tar.html ) in Odin ( use AP slot )
4. After flashing VBMeta, boot to stock. It'll likely ask you to wipe data, if so do that
5. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
6. Now you can flash TWRP ( https://dl.twrp.me/gts4lvwifi ) in Odin ( use AP slot once again ), for convenience you can hold volume up while flashing it so that you boot to recovery right after it's flashed
7. Install Lineage × whatever else you need ( gapps, addon-su, ... )
8. Format data
9. Reboot ( make sure to not install TWRP app when TWRP asks you to )
---
Also Odin download for those who can't find it on their own https://build.nethunter.com/samsung-tools/Odin_3.13.1.zip
( sha1sum 1057496afa34bfdf7e77caf0b99207dca77fcb2d )

Damn @LuK1337 you're all over this thing. About to install (well, at least try to) TWRP using terminal, then I'll do this.
Perfect timing, too. I just did the whole 'prepare for imminent disaster' thing so I could do some extreme debloating/deleting of stuff I don't want on my tablet.
I'll report my experience here.

Wow! Great work!

TiTiB said:
Damn @LuK1337 you're all over this thing. About to install (well, at least try to) TWRP using terminal, then I'll do this.
Perfect timing, too. I just did the whole 'prepare for imminent disaster' thing so I could do some extreme debloating/deleting of stuff I don't want on my tablet.
I'll report my experience here.
Click to expand...
Click to collapse
Install twrp with odin..
1st recovery
2nd vbmeta
Vbmeta's install failed a few times for me, just reboot back to bootloader if you get stuck on getting connection, then try vbmeta again.
That also depends on what firmware your on, June firmware was a easy on installing recovery and using key combo go to recovery, just worked.
Latest update, Juli needs vbmeta to be flashed, otherwise you (might} get an error about non compatible vbmeta installed atm you use the key combos to boot to recovery from bootloader.

RagingHarry said:
Install twrp with odin..
1st recovery
2nd vbmeta
Vbmeta's install failed a few times for me, just reboot back to bootloader if you get stuck on getting connection, then try vbmeta again.
That also depends on what firmware your on, June firmware was a easy on installing recovery and using key combo go to recovery, just worked.
Latest update, Juli needs vbmeta to be flashed, otherwise you (might} get an error about non compatible vbmeta installed atm you use the key combos to boot to recovery from bootloader.
Click to expand...
Click to collapse
1. flash vbmeta from twrp website
2. boot stock; it'll ask you to wipe data, do that.
4. make sure to connect to wifi on stock and that oem unlocking is selected
5. flash recovery, keep holding vol up while flashing
7. sideload lineage × gapps
8. wipe data
10. reboot
11. profit?

For the needed files incase of twrp https://twrp.me/samsung/samsunggalaxytabs5ewifi.html

Ok, so I'm on latest Samsung fw, root and twrp. Just wipe, flash rom, and gapps? Thanks.

suzook said:
Ok, so I'm on latest Samsung fw, root and twrp. Just wipe, flash rom, and gapps? Thanks.
Click to expand...
Click to collapse
There is more info here atm then the moment I 1st flashed a few days ago.
You can do it, read, let it sync to your brain, and just do..
Follow @LuK1337 steps, saves you some unnecessary steps I did getting there..

RagingHarry said:
There is more info here atm then the moment I 1st flashed a few days ago.
You can do it, read, let it sync to your brain, and just do..
Follow @LuK1337 steps, saves you some unnecessary steps I did getting there..
Click to expand...
Click to collapse
Can I flash magisk? Or the provided su for lineage?

I wiped, flashed rom, flashed gaps. it never boots. I see the lineage boot image, but it never completely boots. Any ideas?

Not sure how I got so messed up, but here I am. Not able to power off. PC knows something is hooked up, but 'adb devices' not showing anything. Device Manager shows yellow triangle for Android Phone>Android ADB Interface.
Looking for info on the internets, but no luck yet. Anyways, I'll check back here in a couple hours.
EDIT: More info.
Had TWRP installed.
Currently no key combos working, just goes to Samsung splash screen, then back to screenshot.

Welp. Guess I'm buying this thing tomorrow.

TiTiB said:
Not sure how I got so messed up, but here I am. Not able to power off. PC knows something is hooked up, but 'adb devices' not showing anything. Device Manager shows yellow triangle for Android Phone>Android ADB Interface.
Looking for info on the internets, but no luck yet. Anyways, I'll check back here in a couple hours.
EDIT: More info.
Had TWRP installed.
Currently no key combos working, just goes to Samsung splash screen, then back to screenshot.
Click to expand...
Click to collapse
Did you flash vbmeta from TWRP website? Also you shouldn't be using adb driver in this mode.
suzook said:
I wiped, flashed rom, flashed gaps. it never boots. I see the lineage boot image, but it never completely boots. Any ideas?
Click to expand...
Click to collapse
Wipe/format data? Oh also you can try to wipe system and install lineage × gapps again but this time make sure to NOT install twrp app.

hi
first i flash vbmeta (odin)
2-falsh recovery (odin)
3-flash lineage without gapps
after restart i get boot loop any solution?

jawadabomehsen said:
hi
first i flash vbmeta (odin)
2-falsh recovery (odin)
3-flash lineage without gapps
after restart i get boot loop any solution?
Click to expand...
Click to collapse
Did you install twrp app? If so, wipe system, install lineage again and don't install twrp app this time.
Did you wipe data?

no i didnt install twrp app
---------- Post added at 11:06 AM ---------- Previous post was at 11:02 AM ----------
yes i wipe data

LuK1337 said:
Did you flash vbmeta from TWRP website? Also you shouldn't be using adb driver in this mode.
Wipe/format data? Oh also you can try to wipe system and install lineage × gapps again but this time make sure to NOT install twrp app.
Click to expand...
Click to collapse
I will try wiping system this time. and yea, I dont install twrp app. I will update later. Thanks.
Nope. Same thing. I get the lineage animation for a few minutes, then it just reboots. I let this happen a few times. Arm 64 gapps, correct??

jawadabomehsen said:
no i didnt install twrp app
---------- Post added at 11:06 AM ---------- Previous post was at 11:02 AM ----------
yes i wipe data
Click to expand...
Click to collapse
Add me on hangouts or discord?
( see my signature )

So far, its running awesome! Thanks!

[TWRP][ TWRP 3.3.1-3 Huawei MediaPad M3 Lite ]

{
"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.3.1-3 For Huawei MediaPad M3 Lite 8/10
The new TWRP 3.3.1-3 is required only for Android Q
Officially Supported Devices :
Huawei MediaPad M3 Lite 10 : ( code name Bach ) : BAH-AL00/BAH-L01/BAH-L09/BAH-W09
Huawei MediaPad M3 Lite 8 : ( code name Chopin ) : CPN-AL00/CPN-L0J/CPN-L09/CPN-W09

Instructions :
1. This new TWRP must be installed ONLY on your device running LOS 17.1 with TWRP 3.3.1-0 !
2. flash TWRP recovery using the following command : "fastboot flash recovery twrp-3.3.1-3.img"
3. reboot to recovery ( please check this info after TWRP was installed - and before take any actions )
Downloads :
twrp-3.3.1-2.img
twrp-3.3.1-3.img
Working/ Not working :
- adb shell & mtp
- wipe, backup & restore
- USB-OTG ( need to reboot device to be able to use USB-OTG )
- install Android 10 ROMs
- install GApps Android 10
- FBE /data decrypt support working !
Source :
kernel source : https://github.com/Huawei-Dev/android_kernel_huawei_bach
Credit :
TeamWin - TWRP
LuK1337 for his help !
Mention :
We need this new update of TWRP 3.3.1-3 in order to be able to install GApps on Android 10 & encrypt/decrypt your device !
There is no reason to update TWRP - if you don' use custom ROMs based Android 10 !
Best regards !

Reserved
*** reserved ***

Can't do anything with TWRP
Some help would be greatly appreciated, I have unlocked my mediapad m3 8.0 lite, flashed twrp 3.1.1-1 but when booting into twrp it just sits on the flash screen. Any help?

Roswellien said:
Some help would be greatly appreciated, I have unlocked my mediapad m3 8.0 lite, flashed twrp 3.1.1-1 but when booting into twrp it just sits on the flash screen. Any help?
Click to expand...
Click to collapse
Please, can you install twrp 3.2.0 ? And check to see if you have the same issue ...

surdu_petru said:
Please, can you install twrp 3.2.0 ? And check to see if you have the same issue ...
Click to expand...
Click to collapse
Installed 3.2.0, worked as expected, attempted to directly update to 3.3.1-1, issue returned. Went back to 3.2.0, worked again, flashed 3.3.1-0, issue came back. At a loss at this point. Is there something I am missing here?

Roswellien said:
Installed 3.2.0, worked as expected, attempted to directly update to 3.3.1-1, issue returned. Went back to 3.2.0, worked again, flashed 3.3.1-0, issue came back. At a loss at this point. Is there something I am missing here?
Click to expand...
Click to collapse
Yes, only 3.2.0 it's working with stock Huawei Rom. If you want to use the new twrp, please install LOS 16.0 in twrp 3.2.0 and from now you can update twrp without issues.

No luck.
surdu_petru said:
Yes, only 3.2.0 it's working with stock Huawei Rom. If you want to use the new twrp, please install LOS 16.0 in twrp 3.2.0 and from now you can update twrp without issues.
Click to expand...
Click to collapse
Got 3.2.0 installed and working. Wiped and flashed LOS 16.0, stuck in boot loop. Repeated and boot loop again. I've never had this many problems flashing ROMs before. And like an idiot I was in such a rush I didn't backup first. Gonna see if I can sideload a different room and get it running.
When I use the wipe in 3.2.0 there's a whole bunch of things in /data it fails to wipe saying access denied. Any ideas?
---------- Post added at 02:34 AM ---------- Previous post was at 02:21 AM ----------
Roswellien said:
Got 3.2.0 installed and working. Wiped and flashed LOS 16.0, stuck in boot loop. Repeated and boot loop again. I've never had this many problems flashing ROMs before. And like an idiot I was in such a rush I didn't backup first. Gonna see if I can sideload a different room and get it running.
When I use the wipe in 3.2.0 there's a whole bunch of things in /data it fails to wipe saying access denied. Any ideas?
Click to expand...
Click to collapse
Strike that. Did the wipe again when I got home. Didn't error out, flashed again and booted fine. Looks like I'm all good! Thanks everyone!

Update to 3.3.1-2 !
Hello !
There is a new update of TWRP to 3.3.1-2 !
Only minor updated, including new kernel for Android 10 & syncing with the last code source of TWRP to improve stability
Also was fixed FBE encryption !

4. flash TWRP recovery using the following command : "fastboot flash recovery twrp-3.3.1-1.img"
Click to expand...
Click to collapse
Hello
Any manual for regular people how and where to do this? I don't understand where and how type this command.
Instruction is not clear

Because your manual is useless I tried google and found Multi-Tool 8. I flashed img through it. If I tried load in TWRP device is stuck on this screen and nothing more
@surdu_petru, if you want donations then write usable manuals for real life regular people.
Yesterday I got unknown device and installed TWRP & Custom in 10 ninutes. Your manuals are not help at all. I spent hour+ and get nothing.
Looks like my device boots everytime in this TWRP now.
I donated your work even without using it. But no I'm so disappointed (
I made same with twrp_3.2.0-0. It works. Again 3.3.1-2 - nothing. Add notice about stock firmware to 1st message in topic. Time is killed (

pasha4ur said:
Because your manual is useless I tried google and found Multi-Tool 8. I flashed img through it. If I tried load in TWRP device is stuck on this screen and nothing more
@surdu_petru, if you want donations then write usable manuals for real life regular people.
Yesterday I got unknown device and installed TWRP & Custom in 10 ninutes. Your manuals are not help at all. I spent hour+ and get nothing.
Looks like my device boots everytime in this TWRP now.
I donated your work even without using it. But no I'm so disappointed (
I made same with twrp_3.2.0-0. It works. Again 3.3.1-2 - nothing. Add notice about stock firmware to 1st message in topic. Time is killed (
Click to expand...
Click to collapse
Hello !
Please do not panic ... the problem is that you didn't read everything or maybe you didn't understand everything like it should !
So, your device is still in Android N, because you are on stock ... so you need to use ONLY TWRP 3.2.0.0 !
Now, if you want to use LOS , you need to flash LOS 16.0 on this TWRP 3.2.0, and after that you are able to update TWRP/LOS as you like !
Good luck !
Warning !
Please be very carefully before to flash LOS 16.0 into TWRP 3.2.0 because there is no viable solutions to return to Huawei Stock Firmware !
Photo camera still not working and also the battery does not seem to hold as much as in stock ( maybe you can read some feedback of other users on LOS 17.1 or Pixel Experience) ... if these are not an impediment to you, than you can start format data into twrp-3.2.0 in order to decrypt /data, reboot device into twrp from twrp in order to be able to use data as twrp already recommend and flash LOS 16.0 ! Later you can update TWRP to the last version and install some Android 10 Custom ROMs !
If you want after all this to return to stock, then this is a problem because I already tried without success ... so, that's why this "warning!"

So, your device is still in Android N, because you are on stock ... so you need to use ONLY TWRP 3.2.0.0 !
Click to expand...
Click to collapse
Please be very carefully before to flash LOS 16.0 into TWRP 3.2.0 because there is no viable solutions to return to Huawei Stock Firmware !
Click to expand...
Click to collapse
You should write this in 1st message in topic. Not on 2nd page.
Don't worry. My device is already dead in bootloop.
I will look for a service center or buy a new tablet after removing the quarantine in my country.
Great job! (

pasha4ur said:
You should write this in 1st message in topic. Not on 2nd page.
Don't worry. My device is already dead in bootloop.
I will look for a service center or buy a new tablet after removing the quarantine in my country.
Great job! (
Click to expand...
Click to collapse
How is already dead ?? I see that you have installed LOS17.1, right ? ... So, I guess you re device it's ok !

So, I guess you re device it's ok !
Click to expand...
Click to collapse
After running encryption function it's in bootloop

Fix Data Partition Size !!!
Hello !
I will explain here how the partition /data should be resized in order to be able to Encrypt device on any custom ROM based Android 10 !
From the total of data size, we need to reserve 32768 bytes for encryption stuff.
First, your device should be running Android 10 with TWRP 3.3.1-2 installed ( if you are here, I guess this is already done - what follows is not for Android Pie or for another version of TWRP )
Connect USB cable and type : ( it doesn't matter if you are now on TWRP or a custom ROM based Android 10, btw, make sure you have already enabled "Android debugging" if you're not on TWRP )
adb reboot bootloader
Click to expand...
Click to collapse
You're now on bootloader mode, here only fastboot commands are allowed !
Determine total size of /data partition by typing this command :
fastboot getvar partition-size:userdata
Click to expand...
Click to collapse
Because there are three versions of data storage size : 16GB, 32GB & 64GB - the response to the above command will vary depending on the capacity of your device !
Something like this you'll see after above command :
partition-size:userdata: 0x5xxxxxxxx
finished. total time: 0.002s
Click to expand...
Click to collapse
Let's assign a name to this value, to make it easier to explain what to do next:
I'll call "sectors" the value "0x5xxxxxxxx" which means the total size of your data partition !
If you have any questions so far, then it's time to ask for help, before going any further: because we'll perform some operations with "sectors", and you should already understand what "sectors" mean ... basicly it's a value equale with the total size of youre data partition returned by fastboot !
How we actually interpret this generic number "0x5xxxxxxxx" :
The "xxxxxxxx" from "0x5xxxxxxxx" it's a base number 16 ( hexa) - and is made up of digits from 0 to 9 and also from letters from a to f !
This is just a random example in response to the above command :
partition-size:userdata: 0x5fb03abe0
finished. total time: 0.002s
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Convert "sectors" from hex to decimal using any converter online hex-to-decimal !
"sectors" it'll be now a number made up of digits from 0 to 9 !
Subtract now from "sectors", 32768 .... something like this : "new_sectors" = "sectors" - 32768
The new sectors "new_sectors" will be smaller by 32768 than the one convert from hex to decimal !
Now, this last value ("new_sectors") must be divided to 512 : "new_new_sectors" = "new_sectors" : 512
Let's go back to the "sectors", so we'll rename "new_new_sectors" to "sectors" , so the final value of "sectors" will be smaller by 32768 than the one convert from hex to decimal and also divided to 512 !
Finally, we can summarize all the above operations to this one :
"sectors" = (hex-to-dec(0x5xxxxxxxx) - 32768) : 512
Click to expand...
Click to collapse
As soon as you have the final value and everything went clarity, we need to format data under twrp with this final value of "sectors" !
Reboot device from bootloader mode :
fastboot reboot
Click to expand...
Click to collapse
Reboot device to TWRP :
adb reboot recovery
Click to expand...
Click to collapse
Warning : all data will be lose because we need to format /data :
In order to reformat data Unmount data & type those commands :
Unmount data : check "Mount" & under "Select Partitions to Mount:" deselect/uncheck "Data" !
adb shell
mkfs.f2fs /dev/block/mmcblk0p62 "sectors"
Click to expand...
Click to collapse
Instead "sectors" you"ll must introduce the value of "sectors" which is a number made up of digits from 0 to 9 !
Reboot your device again to TWRP in order to be able to use /data !
reboot recovery
Click to expand...
Click to collapse
That's ALL ... you can now install the new TWRP 3.3.1-3 ( please check OP for download ) with /data decrypt support and also the new LOS 17.1 ( released ) where you'll be able to Encrypt tablet without issues !
Warning :
Starting from now you should never format data again into TWRP in this way : Wipe -> Format Data !
This operation will remove "data" encrypt/decrypt support and your device will not be able to be encrypted under any custom ROMs Android 10 !

surdu_petru said:
Yes, only 3.2.0 it's working with stock Huawei Rom. [...]
Click to expand...
Click to collapse
Hi there,
Could anyone please point me at the right direction to download TWRP 3.2.0 for Huawei MediaPad M3 Lite ? It seems I can't find it anywehre :/
Thank you very much.

Oum said:
Hi there,
Could anyone please point me at the right direction to download TWRP 3.2.0 for Huawei MediaPad M3 Lite ? It seems I can't find it anywehre :/
Thank you very much.
Click to expand...
Click to collapse
Where else could TWRP 3.2.0 be if not in TWRP 3.2.0 thread ... logical, right ??

Roswellien said:
Some help would be greatly appreciated, I have unlocked my mediapad m3 8.0 lite, flashed twrp 3.1.1-1 but when booting into twrp it just sits on the flash screen. Any help?
Click to expand...
Click to collapse
The same thing's happened to me, but "twrp_3.2.0-0.img" worked on my device but the app does not recognize the recovery image (PixelExperience-10.0-HuaweiMediaPadM3Lite_2020-03-15.zip) which I copied it onto external SD card such as /sdcard/download folder.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
surdu_petru said:
TWRP - 3.3.1-3 For Huawei MediaPad M3 Lite 8/10
The new TWRP 3.3.1-3 is required only for Android Q
Officially Supported Devices :
Huawei MediaPad M3 Lite 10 : ( code name Bach ) : BAH-AL00/BAH-L01/BAH-L09/BAH-W09
Huawei MediaPad M3 Lite 8 : ( code name Chopin ) : CPN-AL00/CPN-L0J/CPN-L09/CPN-W09

Instructions :
1. unlock bootloader
3. unlock OEM on Developer options
3. enter on bootloader mode :
( switch off your device then keep pressed volume down key when plug to USB cable )
4. flash TWRP recovery using the following command : "fastboot flash recovery twrp-3.3.1-3.img"
5. reboot to recovery ( please check this info after TWRP was installed - and before take any actions )
Downloads :
twrp-3.3.1-2.img
twrp-3.3.1-3.img
Working/ Not working :
- adb shell & mtp
- wipe, backup & restore
- USB-OTG ( need to reboot device to be able to use USB-OTG )
- install Android 10 ROMs
- install GApps Android 10
- FBE /data decrypt support working !
Source :
kernel source : https://github.com/Huawei-Dev/android_kernel_huawei_bach
Credit :
TeamWin - TWRP
LuK1337 for his help !
Mention :
We need this new update of TWRP 3.3.1-3 in order to be able to install GApps on Android 10 & encrypt/decrypt your device !
There is no reason to update TWRP - if you don' use custom ROMs based Android 10 !
Best regards !
Click to expand...
Click to collapse
I cannot flash PixelExperience-10.0-HuaweiMediaPadM3Lite_2020-03-15.zip by TWRP 3.2.0.0. Do I need to flash LOS16.0 onto my device first and then update TWRP to 3.3.1.3 and then flash PixelExperience-10.0-HuaweiMediaPadM3Lite_2020-03-15.zip???

Hi guys i have no idea where i went wrong. When flashing TWRP, this message always comes up: "necessary to unlock frp! Navigate to settings> developer op)". Can you help me??

mc_simon88 said:
Hi guys i have no idea where i went wrong. When flashing TWRP, this message always comes up: "necessary to unlock frp! Navigate to settings> developer op)". Can you help me??
Click to expand...
Click to collapse
Yes, go to Settings->Developer settings->OEM unlock !

[Fluid OS][Android 11] Guide to install Fluid OS on Huawei Honor 6X

POST - v3
(This number will increase every time the post is updated.)What's new in v3?
Added procedure in a new spoiler to install the base EMUI 8 for hi6250 devices as using the EMUI 8 we get with our device is causing some errors and bugs. Thanks to @Kentoto2021 and @VarianWrynn for testing and reporting this problem.
Spoiler: Version Changelog
What's new in v2?
Updated the thread with newly found bugs in "What isn't working" section.
Made small changes to thread.
What's new in v1?
Took a lot of time to collect the infinity stones.
Took even longer to make Mr. Thanos snap this thread to existence.
What's new in v0?
LoL Who knows?
This ROM is none of my work. I just tested it and provided appropriate procedure and fixes to errors(Found nothing yet).
Thanks a ton to @Hami_Do for making this possible. Original Post : link.
Thanks to Huawei for making their phones nearly unbrickable .
Thanks again to Huawei for making more than one device with hi6250 chipset.
Thanks a lot to @Djiban for helping me and testing different procedures, fixes and ROMs.
Follow this thread only if you know what you're doing. I'm not responsibe for any damage or thermonuclear wars .
Read the post completely and understand it before doing anything ATLEAST FOR THE SAKE OF MANKIND .
This thread is best viewed in PC and is Noob Friendly.
Spoiler: Requirements
Requirements:
Huawei Honor 6X (Unlocked Bootloader. If not, follow this post (using PotatoNV) or YouTube video.
EMUI 8 (If not, you could follow this guide, direct file : link).
GSI from link.
TWRP from attachments or link or any other TWRP recovery compatible with Honor 6X EMUI 8.
Gapps(Optional, I used pico OpenGapps).
stock recovery (available in attachments).
Time.
PC.
ADB and Fastboot.
Patience.
Human Brain.
ALL IN ONE GUIDE : Check it out here. It contains every thing in detail all the way from bricked device -> EMUI 2 -> EMUI 5 -> EMUI 8 -> AOSP 10. Thanks to @lmaohelp for his effort and describing everything in detail.
Useful Information :
What is OpenGapps? Check it out at OpenGapps.org!
What is ARM64? it is a 64 bit operating system/platform.
What isn't working :
Usb Notification (Options will be greyed out. To transfer files, go to Developer Options > Default USB configuration > set it to File Transfer).
Dual sim is buggy. Single sim works perfectly. Thanks to @Loopeez for reporting it.
What's Working :
Everything.
*Tell me if something isn't working.
***If you have a bricked device/messed up somewhere during the process and unable to figure out what to do, follow this guide by @lmaohelp .***
Spoiler: Installing base EMUI 8 for hi6250 devices.
This was already described in a separate thread which describes the process to get back to EMUI 8 from custom ROMs. You can find it here.
Just follow the procedure in that thread. You need not even flash the frp unlock thing. After that, follow the process described in this thread.
It's recommended to be on original EMUI 8 before installing base EMUI 8 for hi6250. Follow the process linked in requirements to install EMUI 8 first then follow this spoiler.
Procedure :
Make sure your device is running stock EMUI 8.
Extract downloaded image using some xz extractor(7zip can also do this), copy it to pc.
Reboot your device to TWRP.
Format the data partition {Wipe > Format data > type "yes"}
Flash fstab.hi6250b.zip from attachments
Check if your device is detected by adb using
Code:
adb devices
.
Move the img file using adb to device
Code:
adb push -p *img-name*.img /sdcard/
(the img file must be in adb directory).
(Optional, only if you want gapps) Move Gapps in the same manner
Code:
adb push -p *gapps-name*.zip /sdcard/
(the zip file must be in adb directory).
Install img as system image {Install > Install Image > Select > Choose system image > Swipe➡}.
(Optional, only if you want gapps) Unmount and Remount system partition as writable. Go to wipe > advanced wipe > Choose system > resize > Swipe➡.
Flash gapps.
Flash stock recovery. Push it with adb using
Code:
adb push -p stock_recovery_ramdisk.img /sdcard/
and flash it with twrp as "Recovery" after choosing install image.
Disconnect your device from PC and reboot to recovery(stock one).
Clear cache partition and perform a factory reset(You'll get an error during factory reset but you have to do it) (your device will bootloop if wiped with twrp itself).
Reboot, Cross your fingers and wait.
>Booting is quite different in android 11 ROMs on our device. You'll see the "Your device has been unlocked" screen for more time than usual. Then, you'll see the boot animation (for very short time on subsequent boots) and the device will boot to ROM. So, be patient. (This isn't the case with ROMs upto android 10)
>Face Unlock is working perfectly
Spoiler: Additionals
Additionals:
>Its better to charge your device to atleast 70% before doing anything as you'll have ample of time to recover it if you messed up something. If not, you can still charge your device in eRecovery mode and twrp but i found some issues like heating up and slow charging.
>Don't forget to set ringtone, notification and other sounds from settings after booting.
Spoiler: Updates
Updates :
Nothing yet...
Happy Flashing !
{
"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"
}

RESERVED

Thx for keep looking for the best andorid 11 rom for Honor 6X. Installed it, no issue so far, testing it as a 2nd daily device. Let you know...
Below is my installation procedure using a microsdcard, quite the same as post #1 apart of that.
- on a micro SD card, download:
https://forum.xda-developers.com/attachments/twrp-img.5326857/
https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/fstab.hi6250b.zip/download
https://forum.xda-developers.com/attachments/stock_recovery_ramdisk-img.5321325
FluidOS-1.1-Rum-R-Hi6250-emui8.img extracted with 7zip from https://mega.nz/#!jWQWEJ7Z!cd2S5oy2g8IdUuw5PfQEkSadslojBpFgB6ltUNOpc-w
OPTIONAL: pico gapps from https://sourceforge.net/projects/opengapps/files/arm64/test/20210110/
- insert the micro SD card in your usb debugging enabled Honor 6X (with EMUI 8 or custom rom installed over EMUI8), and connect it to a PC with adb & fastboot
- in adb, "adb reboot bootloader"
- in fastboot, "fastboot flash recovery_ramdisk TWRP.img"
- in fastboot, "fastboot reboot"
- after reboot completed, "adb reboot recovery"
- disconnect the honor 6x from the PC
- in TWRP recovery, Format the data partition {Wipe > Format data > type "yes"}
- in TWRP recovery, flash fstab.hi6250b.zip
- in TWRP Recovery, flash FluidOS-1.1-Rum-R-Hi6250-emui8.img {Install > Install Image > Select > Choose system image > Swipe}
- OPTIONNAL IF GAPPS WANTED: in TWRP recovery, Mount system partition (Mount > check system and unckeck read only OR reboot in recovery).And
resize system (Go to wipe > advanced wipe > Choose system > repair > resize). Then install open_gapps-arm64-11.0-pico-XXXXXXX.zip.
- in TWRP Recovery Flash STOCK_RECOVERY_RAMDISK.img {Install > Install Image > Select > Choose recovery image > Swipe}
- in TWRP recovery, reboot to recovery (even if TWRP says no OS installed)
- in Stock recovery, wipe cache and factory reset (error is normal)
- in Stock recovery, reboot and wait
Click to expand...
Click to collapse

Rom is very nice so far , no issue yet!!!!

Djiban said:
Rom is very nice so far , no issue yet!!!!
Click to expand...
Click to collapse
Same with me.

Hello, do you know how can I factory reset in the Huawei ERecovery step at the end ?
I try to do it so but it keep reboot my phone to TWRP recovery, it's like I can't wipe data/factory reset my phone from the stock recovery.
Maybe TWRP is bloking it ? Should I disable something in the TWRP settings ?
Between thanks for yours work !

Kentoto2021 said:
Hello, do you know how can I factory reset in the Huawei ERecovery step at the end ?
I try to do it so but it keep reboot my phone to TWRP recovery, it's like I can't wipe data/factory reset my phone from the stock recovery.
Maybe TWRP is bloking it ? Should I disable something in the TWRP settings ?
Between thanks for yours work !
Click to expand...
Click to collapse
Your mistake is that your using stock erecovery.
You have to use stock recovery. Meaning flashing the stock recovery provided in post 1 over the twrp recovery :
- in TWRP Recovery Flash STOCK_RECOVERY_RAMDISK.img {Install > Install Image > Select > Choose recovery image > Swipe}
- in TWRP recovery, reboot to recovery (even if TWRP says no OS installed)
- in Stock recovery, wipe cache and factory reset (error is normal)
- in Stock recovery, reboot and wait

Yep thanks, I forget to choose Recovery when I flash the stock recovery ramdisk, so my twrp install it on the last choice that it's system image
To resolve my problem I reinstall my previous system (EMUI 8 for honor 6x) and this time I wipe the david cache, system, cache ... after format the data partition
And I didn't install any OpenGAPPS and it works fine !
A little empty, but I will try without Google services to see if it sweet to me, it saved a lot of battery so that's nice !
Again, I thank you all of you for your amazing work thank you very much my honor 6x can still live haha
Edit : no it's too painfull without google services haha

Kentoto2021 said:
Yep thanks, I forget to choose Recovery when I flash the stock recovery ramdisk, so my twrp install it on the last choice that it's system image
To resolve my problem I reinstall my previous system (EMUI 8 for honor 6x) and this time I wipe the david cache, system, cache ... after format the data partition
And I didn't install any OpenGAPPS and it works fine !
A little empty, but I will try without Google services to see if it sweet to me, it saved a lot of battery so that's nice !
Again, I thank you all of you for your amazing work thank you very much my honor 6x can still live haha
Click to expand...
Click to collapse
Perform a factory reset after flashing gapps too.
Flashing gapps without factory reset crashed chromium based browsers on AOSP 10. This might not be the case with this rom but better do it.

Kentoto2021 said:
Yep thanks, I forget to choose Recovery when I flash the stock recovery ramdisk, so my twrp install it on the last choice that it's system image
To resolve my problem I reinstall my previous system (EMUI 8 for honor 6x) and this time I wipe the david cache, system, cache ... after format the data partition
And I didn't install any OpenGAPPS and it works fine !
A little empty, but I will try without Google services to see if it sweet to me, it saved a lot of battery so that's nice !
Again, I thank you all of you for your amazing work thank you very much my honor 6x can still live haha
Edit : no it's too painfull without google services haha
Click to expand...
Click to collapse
Android without Google services is more and more easy.
Aurora market is a good choice.
I have also some workaround for'GPS localisation and so....

Nevertheless, gapps working fine for me, no device lag cause of it ! All services active and working

Djiban said:
Nvertheless, gapps working fine for me, no device lag cause of it ! All services active and working
Click to expand...
Click to collapse
Same with me. And the power menu controls are just AWESOME.

Dang, I cannot go past installing Huawei USB COM driver to unlock my device (

jottect said:
Dang, I cannot go past installing Huawei USB COM driver to unlock my device (
Click to expand...
Click to collapse
? Didn't get you... Did you mean bootloader unlock? If yes, follow @lmaohelp 's guide mentioned in post 1. He described it very clearly.

Venkata Lochan Nune said:
? Didn't get you... Did you mean bootloader unlock? If yes, follow @lmaohelp 's guide mentioned in post 1. He described it very clearly.
Click to expand...
Click to collapse
Yes, it's clear, read the posts, watched YT video, but one of the steps is installing Huawei USB COM driver to replace the SER driver, and I already tried on 2 computers, Windows 10 (updated) fails to install that driver, and without it, PotatoNV won't 'see' the device.

Venkata Lochan Nune said:
Same with me. And the power menu controls are just AWESOME.
View attachment 5337621
Click to expand...
Click to collapse
Oooh how did you get that ?
I only have this :
Is it Gapps ? I use the nano one

Kentoto2021 said:
Is it Gapps ? I use the nano one
Click to expand...
Click to collapse
Nope, there's an app on play store called "power menu controls" download that. And the other, you could use Tasker(also an app from play store) to create your custom controls like the ones I did for screen rotation.

jottect said:
Yes, it's clear, read the posts, watched YT video, but one of the steps is installing Huawei USB COM driver to replace the SER driver, and I already tried on 2 computers, Windows 10 (updated) fails to install that driver, and without it, PotatoNV won't 'see' the device.
Click to expand...
Click to collapse
what's the procedure you followed to install drivers?
Unzip the attached file, and choose "DriverSetup.exe" and that's it. uninstall these drivers after installing the rom using "DriverUninstall.exe" for mtp to work. The process will ask for reboot in some language(i think Chinese) after uninstalling but it isn't needed.
*These are also the fastboot drivers(but the name in attachments is testpoint drivers).

Kentoto2021 said:
Edit : no it's too painfull without google services haha
Click to expand...
Click to collapse
Indeed! I once tried using AOSP 10 with floss services and without Google ones but yeah it didn't last even a day... lol I flashed gapps within 5 hrs.

Venkata Lochan Nune said:
what's the procedure you followed to install drivers?
Unzip the attached file, and choose "DriverSetup.exe" and that's it. uninstall these drivers after installing the rom using "DriverUninstall.exe" for mtp to work. The process will ask for reboot in some language(i think Chinese) after uninstalling but it isn't needed.
*These are also the fastboot drivers(but the name in attachments is testpoint drivers).
Click to expand...
Click to collapse
Thanks a million! It worked., I just unlocked the bootloader, I did not have these drivers.
Now onto next steps... may take a while, I'm old and slow
Well, did not go too far... when trying to flash twrp (as per this guide:
), I'm getting an error:
fastboot flash recovery_ramdisk twrp.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24466 KB)...
OKAY [ 0.642s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished.
Ideas?
P.S. I also tried
fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (24466 KB)...
OKAY [ 0.642s]
writing 'recovery'...
FAILED (remote: image verification error)

[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 GuideClean 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...).

Develop Bugs

welcome