Develop Bugs

[ROM+TWRP][taido][7.1.x][UNOFFICIAL] Lineage Android Distribution for Moto E3

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
WHAT WORKS
Boot
WiFi
Hotspot
Audio
RIL
Bluetooth
Sensors
FM
Camera
SDCard
GPS
KNOWN ISSUES
Video recording
VoLTE [Don't expect it to be working anytime soon]
SELinux Enforcing
!!! BUG REPORTS WITHOUT LOGS WILL BE IGNORED !!!
Android: adb logcat
Radio: adb logcat -b radio
Kernel: adb shell dmesg
Full Bugreport: Developer Menu -> Bugreport
HOW TO INSTALL LINEAGEOS
- Download the LineageOS zip(s). (see Downloads)
- Download the TWRP Image. (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Unlock bootloader and install TWRP from downloads.
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- IMPORTANT: Do a Factory Reset. (Wipe data & cache)
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
DOWNLOADS
LineageOS:
https://www.androidfilehost.com/?w=files&flid=203899
TWRP:
https://www.androidfilehost.com/?w=files&flid=203904
Google Apps:
OpenGApps (recommended: arm, 7.1.1, nano)
SOURCECODE
Device tree: https://github.com/ashwinr64/android_device_motorola_taido
Kernel: https://github.com/ashwinr64/android_kernel_motorola_mt6735
Vendor: https://github.com/ashwinr64/android_vendor_motorola_taido
HOW TO CONTRIBUTE
Use our code review system to send patches: https://review.lineageos.org
SUPPORT ME
Do you like my work? Consider donating me some beer!
​
XDA:DevDB Information
LineageOS for taido, ROM for the Moto E3
Contributors
ashwin007
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Version Information
Status: Testing
Created 2017-08-03
Last Updated 2017-08-03

Changelogs
-> Build 1 [04-08-2017]
* Initial Public Release
* Merged upstream 3.18.63 kernel.
* Switched to XZ kernel compression and enabled -O2 flag.
* Widevine has been fixed, so DRM contents are playable.
-> Build 2 [16-08-2017]
* Synced with Lineage
* Merged upstream 3.18.65 kernel
* Hotspot fixed
* Added support for F2FS

Thanks a lot!

And the development starts again

Dear @ashwin007,
I'm so glad [emoji1] to see that you are working on taido.
I appreciate your brilliant work.
All the best

A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?

Not installing.
Code 7 error

bubba1601 said:
Not installing.
Code 7 error
Click to expand...
Click to collapse
use TWRP given by Ashwin, also check weather u did factory reset....
also follow the instructions....

spykarzzz said:
use TWRP given by Ashwin, also check weather u did factory reset....
also follow the instructions....
Click to expand...
Click to collapse
My Friend, I've been flashing Roms on various devices for more than three years.......
So I have done a factory reset, as I'm using another lineage OS version on my E3.
I followed all instructions.
So the TWRP version I'm using must be the issue, its the Dr framazone version 3.0.0.2, I can't flash the new twrp image in the twrp I'm using.
I'll have to try in fast boot mode through the PC.

U need deckers TWRP to flash dis particular Rom....Try this only!!!

One request, can you please add double tap 2 wake feature in the kernel?

spykarzzz said:
U need deckers TWRP to flash dis particular Rom....Try this only!!!
Click to expand...
Click to collapse
Yes, I know and understand that.
As I said in my previous comment, I cannot flash the newer twrp image through the version of twrp I'm using.
I've have now managed to flash the twrp image via fast boot and have this ROM up and running.
Unfortunately I've ran into many problems not seen in the other lineage OS ROM that I've been using for the last week.
1. Guest user was activated after initial set up, meaning I could not change any settings.
2. I cannot access my external SD card.
So important files to me are inaccessible?
3. No photographs taken using the camera are being saved, they just disappear from the gallery into thin air.
4. My service provider doesn't list in networks or the signal indicator (O2 UK) instead my device shows "23410"
Its at this point I confess to running this rom on my XT1700 and NOT a XT1706 (My device is in fact a European spec standard Motorola E3, but running E3 power firmware and renamed in system to a E3 power XT1706 - this was flashed by Motorola themselves during a repair as they claimed I had to pay for XT1700 firmwares, so E3 Power firmware was flashed by them.
Although I appreciate Ashwins efforts and i appreciate this is a testing version, I cannot use this ROM as I'm now also in trouble with my employer for not having photographic evidence of my work today (My E3 is used as my work device, and taking photos of my finished work is a requirement of my employment)
I have to now move to another ROM for this reason until these issues can be fixed and photos taken with the camera will be saved and stay saved.
Sorry.

Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me

aman4512 said:
A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?
Click to expand...
Click to collapse
Bro do this....
U have to go to fastboot mode....
Then enter fastboot format userdata....
Then fastboot flash recovery.img
Then dont go to recovery let ur phone start....
Then enable usb debug & oem unlock in phone after rebooting...
Again switch of ur phone...
Now goto fastboot mode....
Type fastboot flash recovery .img
Now go to recovery and flash the rom file
It ll work 100%

solkarsalman said:
Bro do this....
U have to go to fastboot mode....
Then enter fastboot format userdata....
Then fastboot flash recovery.img
Then dont go to recovery let ur phone start....
Then enable usb debug & oem unlock in phone after rebooting...
Again switch of ur phone...
Now goto fastboot mode....
Type fastboot flash recovery .img
Now go to recovery and flash the rom file
It ll work 100%
Click to expand...
Click to collapse
Thanks, but I had solved the problem. The thing is my phone wasn't booting at all after flashing TWRP. Tried many version. It was some issue with the phone's boot.img (some Lenovo phone has a similar issue, K4 power I think). I flashed a stock ROM and after flashing TWRP, I flashed SuperSU, since it patches boot.img. That worked, after which I wiped /system, /data, /cache and flashed Lineage.

bjyadav4 said:
Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me
Click to expand...
Click to collapse
Read the comments above you own
Don't install it, I had major issues.
Read previous comments before posting.

bubba1601 said:
Yes, I know and understand that.
As I said in my previous comment, I cannot flash the newer twrp image through the version of twrp I'm using.
I've have now managed to flash the twrp image via fast boot and have this ROM up and running.
Unfortunately I've ran into many problems not seen in the other lineage OS ROM that I've been using for the last week.
1. Guest user was activated after initial set up, meaning I could not change any settings.
2. I cannot access my external SD card.
So important files to me are inaccessible?
3. No photographs taken using the camera are being saved, they just disappear from the gallery into thin air.
4. My service provider doesn't list in networks or the signal indicator (O2 UK) instead my device shows "23410"
Its at this point I confess to running this rom on my XT1700 and NOT a XT1706 (My device is in fact a European spec standard Motorola E3, but running E3 power firmware and renamed in system to a E3 power XT1706 - this was flashed by Motorola themselves during a repair as they claimed I had to pay for XT1700 firmwares, so E3 Power firmware was flashed by them.
Although I appreciate Ashwins efforts and i appreciate this is a testing version, I cannot use this ROM as I'm now also in trouble with my employer for not having photographic evidence of my work today (My E3 is used as my work device, and taking photos of my finished work is a requirement of my employment)
I have to now move to another ROM for this reason until these issues can be fixed and photos taken with the camera will be saved and stay saved.
Sorry.
Click to expand...
Click to collapse
I didn't face any of the above issues on my Moto E3 Power. Camera is working fine and photos are also saving.
SD card is also accessible.
---------- Post added at 07:34 AM ---------- Previous post was at 07:30 AM ----------
bjyadav4 said:
Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me
Click to expand...
Click to collapse
Camera is working properly.
If you do this
Thanks, but I had solved the problem. The thing is my phone wasn't booting at all after flashing TWRP. Tried many version. It was some issue with the phone's boot.img (some Lenovo phone has a similar issue, K4 power I think). I flashed a stock ROM and after flashing TWRP, I flashed SuperSU, since it patches boot.img. That worked, after which I wiped /system, /data, /cache and flashed Lineage.
Click to expand...
Click to collapse
then storage problem will also be solved.

aman4512 said:
A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?
Click to expand...
Click to collapse
Is this the actual screenshot? Because the developer has mentioned that LTE is not working but the screenshot shows LTE in the notification bar.

ranjithgn said:
Is this the actual screenshot? Because the developer has mentioned that LTE is not working but the screenshot shows LTE in the notification bar.
Click to expand...
Click to collapse
LTE works, VoLTE doesn't.

precedentbrute said:
I didn't face any of the above issues on my Moto E3 Power. Camera is working fine and photos are also saving.
SD card is also accessible.
---------- Post added at 07:34 AM ---------- Previous post was at 07:30 AM ----------
Camera is working properly.
If you do this
then storage problem will also be solved.
Click to expand...
Click to collapse
Thank you for your feedback, although I can't share your optimism or your confidence.
I've now reflashed this rom three times.
I cannot access external storage.
Photos disappear from the gallery, and now all my Google apps keep force closing - I'm using the recommendation of Google apps, open gapps nano arm.
Remember just because it's all good for you doesn't necessarily mean it's good for others, as I've seen so many times in these forums.
Regards.

[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][AICP][14.0][dragon] -> 20190213 (DISCONTINUED)

DISCONTINUED
Sorry .. due to limited time I have stopped this ROM.
Pls find the last downloads here ..
https://androidfilehost.com/?w=files&flid=289293
Thanks for understanding ..
Android Ice Cold Project - Pie
aicp_dragon_p-14.0-UNOFFICIAL-20190213.zip
Known issues:
- Encryption seems not 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 aicp_dragon_p-14.0-UNOFFICIAL-20190213.zip
4. Install Opengapps (arm64)
5. install Magisk.zip
6. Reboot into system ..
- The ROM does contain it's own vendor.img !
SOURCES:
https://github.com/followmsi/manifests/tree/dragon-aicp-14.0
Enjoy ..

Just playing with the AICP sources for Pie and made a dragon build too ..
Let's test another Android ROM on our lovely dragon device ..
Cheers

followmsi said:
Just playing with the AICP sources for Pie and made a dragon build too ..
Let's test another Android ROM on our lovely dragon device ..
Cheers
Click to expand...
Click to collapse
First boot very fast about 40 seconds but few seconds after end of the setup process, the tablet start to freeze so violently that the device was unusable, nothing respond...
I press the reboot button, the tablet reboot after 30 seconds of freeze.
After reboot everthing seem to work just fine !
Good work, thanks

I'm running into some of the same issues as the other Pie threads:
Lockscreen issues. What worked for me was going into TWRP --> File Manager --> data --> system and deleting the lockscreen file, then booting back up, going into settings -after- initial setup and creating my pin/pattern there.
Encryption - I haven't tried this yet. I'm going to finish my install, make a backup, then see what happens.
Other than that it seems fine.

CharFalco said:
I'm running into some of the same issues as the other Pie threads:
Lockscreen issues. What worked for me was going into TWRP --> File Manager --> data --> system and deleting the lockscreen file, then booting back up, going into settings -after- initial setup and creating my pin/pattern there.
Encryption - I haven't tried this yet. I'm going to finish my install, make a backup, then see what happens.
Other than that it seems fine.
Click to expand...
Click to collapse
Thanks for feedback ..
Like you said .. same problems on all Pie ROMs.
As we use same device/kernel/vendor sources for all ROMs.
For this reason we should have the same/similar problems
Known issues:
- Encryption seems not work - and has not been fully tested. -> Pls do not encrypt your data partition yet.
- Screen Unlock: If you set Pattern or Password the Screen unlock does not work correctly.
(Workaround: 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.)
Updated OP now .. hope the workaround works on AICP too.
Cheers

I feel a bit silly asking such a narrow question, but I couldn't find the answer on the AICP site.
Does AICP provide the ability to add a distinct, separate last app button? That's my favorite feature ever.
(This is not a feature request, like "please add XYZ." I'm just asking if it's already there.)
Thanks

I think this is probably my favorite of all the ROMs you've sent us. Do you have a Patreon or something, followmsi?

February 2019 - the final AICP ROM
aicp_dragon_p-14.0-UNOFFICIAL-20190213.zip
Changes:
- Google security updates -> February 2019
- Google kernel updates -> February 2019
- Latest AICP changes for Pie
The ROM does contain it's own vendor.img !
Enjoy

DISCONTINUED
Sorry .. due to limited time I have stopped this ROM.
Pls find the last downloads here ..
https://androidfilehost.com/?w=files&flid=289293
Thanks for understanding ..

I realise this has been discontinued but after rebooting my Pixel C today it now won't boot up again.
It loads the AICP logo then the animation of the logo almost finishes but leaves a bit of it on screen and just gets stuck in a loop of showing the remaining part of the logo and flashing the lock screen briefly.
I'm not sure what my options are for recovery... I'd rather not have to start over again as it's probably only been a couple of months before I had to start fresh on this device.

[RECOVERY][Unofficial][amami] TWRP 3.4.0

Finally there is a TWRP capable of decrypting /data on android versions > nougat.
Big thanks @NeoArian
I haven't tested everything in detail as I mostly focused on decryption. If you experience issues or can confirm something working that's not green in the table down below, please share.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Status
List template by TWRP
Code:
[B]Blocking checks[/B]
- [COLOR="green"]Correct screen/recovery size[/COLOR]
- [COLOR="green"]Working Touch, screen[/COLOR]
- [COLOR="green"]Backup to internal/microSD[/COLOR]
- Restore from internal/microSD
- [COLOR="green"]reboot to system[/COLOR]
- [COLOR="green"]ADB[/COLOR]
[B]Medium checks[/B]
- update.zip sideload
- [COLOR="green"]UI colors (red/blue inversions)[/COLOR]
- [COLOR="green"]Screen goes off (and on :))[/COLOR]
- F2FS/EXT4 Support, exFAT/NTFS where supported
- [COLOR="green"]all important partitions listed in mount/backup lists[/COLOR]
- backup/restore to/from external (USB-OTG) storage
- backup/restore to/from adb
- [COLOR="green"]decrypt /data[/COLOR]
- Correct date
[B]Minor checks[/B]
- MTP export
- [COLOR="green"]reboot to bootloader[/COLOR]
- [COLOR="green"]reboot to recovery[/COLOR]
- [COLOR="green"]poweroff[/COLOR]
- [COLOR="green"]battery level[/COLOR]
- [COLOR="green"]temperature[/COLOR]
- encrypted backups
- [COLOR="green"]input devices via USB (USB-OTG) - keyboard, mouse[/COLOR]
- USB mass storage export
- [COLOR="green"]set brightness[/COLOR]
- [COLOR="green"]vibrate[/COLOR]
- [COLOR="green"]screenshot[/COLOR]
Limitations
Following limitations are known:
none
Click to expand...
Click to collapse
prerequisites
For reboot to recovery from your android system (and OTA updates) your ROM needs the following patches 1, 2 and 3. Following ROM's currently support this:
AICP 14
AICP 15
LineageOS 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
For correct time inside TWRP your ROM needs the following patch. Following ROM's currently support this:
AICP 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
Download
SourceForge
AndroidFileHost
Click to expand...
Click to collapse
How to build
https://github.com/115ek/manifest#build-twrp
Click to expand...
Click to collapse
XDA:DevDB Information
[RECOVERY][Unofficial][amami] TWRP 3.4.0, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
115ek, NeoArian
Source Code: https://github.com/115ek/twrp_device_sony_amami
Version Information
Status: Beta
Created 2019-08-25
Last Updated 2020-08-22

Changelog
15.09.2020 3.4.0-1
again: fix non working OTA update in rare cases (rebooting to recovery and stucking there unable to install update automatically)
22.08.2020 3.4.0-0
latest TWRP changes
29.02.2020 3.3.1-0.4
display sony bootlogo at boot
show version number
remove TWRP app
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
05.09.2019 3.3.1-0.2
enable reboot to bootloader (fastboot mode) (you have to connect the phone via usb BEFORE rebooting)
25.08.2019 3.3.1-0.1
decrease size
allow decryption in any case of patchlevel value
25.08.2019 3.3.1-0
initial release

Reserved

Backup to microSD seems to be working fine (haven't restored anything yet):good:

I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0

115ek said:
I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0
Click to expand...
Click to collapse
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!

bananabytes said:
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!
Click to expand...
Click to collapse
What command did you use?
Code:
fastboot flash recovery
or
Code:
fastboot flash FOTAKernel
Do you have the newest bootloader installed? So can you boot directly into recovery with VOL down and power pressed (with 3.2.3 version where flashing was successful)?
Or do you use the method with pressing VOL down when the LED lights up?
EDIT:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
What version of fastboot are you using?
I'm using fastboot installed from the packetmanager with
Code:
apt install fastboot
.
Code:
fastboot --version
gives fastboot version 1:8.1.0+r23-5~18.04.
This would mean 27.0.0 or 27.0.1 according to this scheme. I don't know why they are using different naming schema
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).

115ek said:
What command did you use?.
Click to expand...
Click to collapse
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
115ek said:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
...
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).
Click to expand...
Click to collapse
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.

bananabytes said:
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.
Click to expand...
Click to collapse
Can you please verify that you also fail with the fastboot binary from here
It's also 29.0.2 and it works fine for me.

I have tried this version with LOS 16 and it worked well. Some things to improve
boot to fastboot is not possible
backup and restore of boot is not possible
good catch with encryption, I have give it up :good:

Micha_Btz said:
boot to fastboot is not possible
Click to expand...
Click to collapse
Well, I actually didn't know this was possible in earlier versions. However it should work now --> see the changelog
You have to connect usb cable before rebooting to bootloader, otherwise it won't work and just reboot the system.
Micha_Btz said:
backup and restore of boot is not possible
Click to expand...
Click to collapse
I can't confirm that. What exactly was the problem for you? Backing up or restoring? Did you got any errors?

Have had a look yesterday, Backup and restore of boot is possible (don't now what happends)

@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.

tramp20 said:
@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.
Click to expand...
Click to collapse
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again. And for me this works fine. However it takes some seconds (there's a wrong time at the beginning).

115ek said:
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again.
Click to expand...
Click to collapse
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now

Generic question re: encrypting this device
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?

tramp20 said:
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now
Click to expand...
Click to collapse
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
So everyone flashing this image should have the same functionality (in theory). As it works for me (and some others) I'm just wondering.
lm089 said:
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?
Click to expand...
Click to collapse
The behaviour is totally expected as amami uses the deprecated full disk encryption (FDE). Most likely your oneplus 6 is using file based encryption (FBE). That's the reason it can boot to your lockscreen because some files necessary for booting aren't encrypted (or not encrypted using your password...). To boot a device with fully encrypted /data you have to decrypt it first. If you're interested in details have a look here.
The other thing sounds a bit strange. However I don't know if it's possible to remove the FDE completely. Maybe the device just sets a default password then?
Concerning your question:
What definitely should work is taking a backup in TWRP (of course need to decrypt /data before), then format /data and restore the backup. Anyhow - I didn't test such a case so far.

115ek said:
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
Click to expand...
Click to collapse
Flashing stock ROM was the only way that all older TWRP could read the correct date again after trying your twrp version.
I will try to get a log if I have enough time.
So the recovery.img = twrp.img or at least a part of it?
Thank you.

New update:
As I had problems with installing OTA updates (especially with /data encrypted, but not limited to) on LineageOS 16.0 I came up with a fix.
Download Currently only on sourceforge - android filehost is buggy at the moment...
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
Edit:
As reminder for me / interested guys: This commit breaks the OTA updating in some cases (when mmap isn't sufficient). The buildflag
Code:
-D_FILE_OFFSET_BITS=64
doesn't work as intended on my setup. Maybe I missed something.

tramp20 said:
@115ek,
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
Click to expand...
Click to collapse
Have the same time/date problem with twrp-3.3.1-0.3-amami.img
recovery.log >> https://pastebin.com/rBdHAmz2
Also does not reboot into the recovery from system (AICP 14), just shutdown and then power+volume down works.

[13.0][GSI][ROM][ CURTANA | JOYEUSE | EXCALIBUR][AOSP+GAPPS][25/6/23]

{
"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:
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is this?
An AOSP based ROM, with gapps included and gesture support (pocket, hand wave, pickup).
Based on Android 13.0
Tested on Redmi Note 9S (curtana global) on both vendor miui 12 and miui 13
1. If you want to root then copy the stock boot from the latest stock rom into internal and use magisk to patch it, then flash the patched boot in bootloader (fastboot flash boot patched_boot.img)
2. I will try to provide monthly patch updates and fixes as needed, don't ask for ETAs... I usually aim for the 5th of each month or whenever Google releases their patches
3. If you are coming from a previous version, I highly recommend clean flashing, otherwise you will probably have issues
Bugs:
On Android 12 vendor the boot is a bit longer
I don't see any other issues, please report real issues, not feature requests from MIUI or other roms.
Getting fastbootd drivers working on windows:
1. Download these drivers and unzip
2. follow the instructions here to install the unsigned drivers
3. select the windows inf
Steps:
Please follow these steps closely!
For new installs:
1. Unlock bootloader
2. Download vbmeta from here and flash it in fastboot like this:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_note9s.img (IF YOU DONT DO THIS STEP, VOLTE AND OK GOOGLE WONT WORK!)
3. In bootloader enter: 'fastboot reboot fastboot'
4. After we reboot you will see 'fastbootd', enter 'fastboot flash system system.img' (extract the system.img and put it in the folder you're in
5. enter 'fastboot reboot recovery'
6. select format userdata
7. then select reboot to system
To upgrade from previous versions:
1. Reboot to fastbootd (adb reboot fastboot from inside android or fastboot reboot fastboot from bootloader)
2. After we reboot you will see 'fastbootd', enter 'fastboot flash system system.img' (extract the system.img and put it in the folder you're in
3. Reboot
There is now a toggle to add SuperSU on boot in Phh Settings > Misc:
Just enable it and reboot. (Keep in mind it breaks safteynet, if you need to use a banking app, disable it from settings and reboot)
Downloads:
Latest ROM
@phhusson for his work on GSI (donate to this man, he works on dozens of devices), he worked closely with me to get everything working!
Thanks to Peter Cai for getting Bluetooth stack working with a2dp on Android 13! He worked very hard on it and deserves full credit
Enjoy!
P.S.
I am not going to add any custom features from other roms so please don't comment about that!
Source: https://github.com/aosp-tissot
Phh source:Link
XDA:DevDB Information
[GSI][ROM][ CURTANA | JOYEUSE | EXCALIBUR][13.0][AOSP+GAPPS][29/08/22], ROM for the Redmi Note 9 Pro
Contributors
sooti, phhusson, peter cai
Source Code: https://github.com/aosp-tissot
ROM OS Version: Android 13
ROM Kernel: Linux 4.x
ROM Firmware Required: Treble
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2022-08-29
Created 2022-08-29
Last Updated 2022-08-29​

Change Log:
25/5/23:
* Latest trebledroid patches
* Fixed bug that caused safteynet to fail
* Added a patch that allows the device name to be shown to google store but still pass safteynet
4/5/23:
* Fixed bt calls not working
* Latest trebledroid patches
* May Google security patch
13/4/23:
* April security patch
* Latest trebledroid (phh) patches
21/3/23:
* Fixed Auto brightness not working
15/3/23:
* March security patch
9/2/23:
* Feb Security patch
* Latest Phh commits
* Fixed safteynet again
9/1/23:
* Jan security patch
25/12/22:
* Smaller gapps that are more inline with stock pixel
* Smaller image size which should help it work on smaller partitions of other devices
* Fixed IMS not working
* Fixed other props not loading at boot causing voip distortion in calls
* Fixed safteynet not passing when not rooted
11/12/22:
* Dec security patch
09/11/22:
* Merged latest phh and trebledroid patches
* November security patch
05/10/22:
* October google security patch
* Added a ton of fixes for other devices (mi a1 and other non xiaomi devices)
* Fixed xiaomi settings not showing up in treble settings
13/09/22
* Fix netflix not showing up in store (clean google play service & play store data if you are running the previous version, it might take a few minutes to show up)
* Made a better fix for Google hotword not working (Device model will show up properly now instead)
* September security patch
* Fixed permissions issue with GMS that caused crashes
* Updated some outdated prebuilt gapps
30/8/22:
* Fixed overlay to fit our punch hole correctly
* Removed the notch when in landscape

Xxxx

no vendor included...?
plz advise in op that what vendor to use.

vwong said:
no vendor included...?
plz advise in op that what vendor to use.
Click to expand...
Click to collapse
Huh? it's a GSI... you use stock vendor... read the post...

Added a new build:
Fixed the punch hole location and landscape notch showing up

I mentioned in the Android 12 last version that Google pay updated to google wallet and no longer works with contactless payments etc. I did a 'fresh' install of this, in the recovery I removed userdata and such on this device when flashing this new Android 13 version. I believe it's failing safetynet check as Netflix and such isn't showing on google play and when trying to add bank card it's still stating that this device "may be rooted or running uncertified software" I haven't turned on superSU and I haven't attempted to put magisk on this at all or patch the boot image.

McguyverZero said:
I mentioned in the Android 12 last version that Google pay updated to google wallet and no longer works with contactless payments etc. I did a 'fresh' install of this, in the recovery I removed userdata and such on this device when flashing this new Android 13 version. I believe it's failing safetynet check as Netflix and such isn't showing on google play and when trying to add bank card it's still stating that this device "may be rooted or running uncertified software" I haven't turned on superSU and I haven't attempted to put magisk on this at all or patch the boot image.
Click to expand...
Click to collapse
Can you run safteynet check? Are you using magisk? On mine it's all working , a12 vendor fails since google doesn't recognize it as certified but I put 11 vendor props to fix it

sooti said:
Can you run safteynet check? Are you using magisk? On mine it's all working , a12 vendor fails since google doesn't recognize it as certified but I put 11 vendor props to fix it
Click to expand...
Click to collapse
No Magisk at all, what's the best way to do a safetynet check?
I tried a couple safetynet apps and they all return that it is passing with no errors. Yet Netflix still isn't an app that appears in the google play store and trying to add my bank card for contactless payment when it connects to bank still returns the same problem with the uncertified software.

McguyverZero said:
No Magisk at all, what's the best way to do a safetynet check?
I tried a couple safetynet apps and they all return that it is passing with no errors. Yet Netflix still isn't an app that appears in the google play store and trying to add my bank card for contactless payment when it connects to bank still returns the same problem with the uncertified software.
Click to expand...
Click to collapse
I'm not sure sorry... if it passes it passes... sometimes netflix takes time to show up in the store... try clearing your google play store and google services data and try again... on my end everything works

sooti said:
I'm not sure sorry... if it passes it passes... sometimes netflix takes time to show up in the store... try clearing your google play store and google services data and try again... on my end everything works
Click to expand...
Click to collapse
I have been jumping in hoops, I'm not fully sure what Is going on. I keep a document of things as I've been going along so I can revert etc. I tried reflashing this again and same issue with the contactless, so I figured I would try fastboot recovery ROM from MIUI and tried 12.5.8 as that was what I OTA'd to but it was erroring with unable to parse 'super' I tried a few different roms and flashing tools, someone stated it was an issue with the fastboot etc. I just tried flashing 12.5.4 (my previous version) onto it and it's going on now as we speak 'successfully'. No idea what is going on with this 12.5.8. (The odd thing is, the update put it on to 12.5.8.0 (RJZEUXM) which was the version I have and was trying to recovery with.
Unrelated and I know it isn't 'necessary' for this but I came across a TWRP for this device? I didn't think it had TWRP support as their main website doesn't list it under devices. I didn't touch it but I was just curious.
Oh also another further question: IF we were to try Magisk is it still dependant on specific version? Thanks.

McguyverZero said:
I have been jumping in hoops, I'm not fully sure what Is going on. I keep a document of things as I've been going along so I can revert etc. I tried reflashing this again and same issue with the contactless, so I figured I would try fastboot recovery ROM from MIUI and tried 12.5.8 as that was what I OTA'd to but it was erroring with unable to parse 'super' I tried a few different roms and flashing tools, someone stated it was an issue with the fastboot etc. I just tried flashing 12.5.4 (my previous version) onto it and it's going on now as we speak 'successfully'. No idea what is going on with this 12.5.8. (The odd thing is, the update put it on to 12.5.8.0 (RJZEUXM) which was the version I have and was trying to recovery with.
Unrelated and I know it isn't 'necessary' for this but I came across a TWRP for this device? I didn't think it had TWRP support as their main website doesn't list it under devices. I didn't touch it but I was just curious.
Oh also another further question: IF we were to try Magisk is it still dependant on specific version? Thanks.
Click to expand...
Click to collapse
No, magisk works fine, just make sure to use the universal safteynet patch module to pass safteynet with magisk

sooti said:
No, magisk works fine, just make sure to use the universal safteynet patch module to pass safteynet with magisk
Click to expand...
Click to collapse
After flashing this CFW on here again it's still not working with Gpay/wallet. Safetynet passes all fine but still no netflix. I tried patching boot for magisk and redo-ing to test if anything was different, After putting the safetynet on and such it passed everything except for an "!" next to "CTS Profile Matched" but the Gpay/wallet still won't allow, Netflix still no longer there and I see Disney+ also hidden now.
I'm unsure what further to try to get Gpay working, which is annoying but not the end.

Random apps are closing themselves and most importantly my "Waze" app is refreshing itself every 10 seconds making it impossible to use.

McguyverZero said:
Random apps are closing themselves and most importantly my "Waze" app is refreshing itself every 10 seconds making it impossible to use.
Click to expand...
Click to collapse
What device are you using? curtana works fine... sounds like somethings wrong with your flashing... please provide full model details and how you flashed everything

I have Xiaomi Redmi Note 9 Pro ('Global' I THINK) codename: Joyeuse. From 12.1 I used MiFlash to flash 12.5.4.0 Stable.(RJZEUXM) to my device, I then did an OTA update pushing it to 12.5.8.0 (RJZEUXM). I put the device into fastboot (vol down + power) then using platform tools 33.r3, I did the vbmeta flash, then "fastboot reboot fastboot" to go into fastbootD to then flash the system.img provided from the google drive link in OP (dated 30/08/22), I reboot into recovery via fastboot and select the "Wipe data" function, once it is complete I reboot and then begin to setup the phone without copying any data or backups from google drive/cloud.

McguyverZero said:
I have Xiaomi Redmi Note 9 Pro ('Global' I THINK) codename: Joyeuse. From 12.1 I used MiFlash to flash 12.5.4.0 Stable.(RJZEUXM) to my device, I then did an OTA update pushing it to 12.5.8.0 (RJZEUXM). I put the device into fastboot (vol down + power) then using platform tools 33.r3, I did the vbmeta flash, then "fastboot reboot fastboot" to go into fastbootD to then flash the system.img provided from the google drive link in OP (dated 30/08/22), I reboot into recovery via fastboot and select the "Wipe data" function, once it is complete I reboot and then begin to setup the phone without copying any data or backups from google drive/cloud.
Click to expand...
Click to collapse
I'd suggest trying android 11 vendor... That should def work.. but as i said i dont have your issues.. ill try tp push a fix soon

sooti said:
I'd suggest trying android 11 vendor... That should def work.. but as i said i dont have your issues.. ill try tp push a fix soon
Click to expand...
Click to collapse
Just some additional notes as I saw there was a MIUI 13.0.1 available, Attempted to fastboot into MIUI V13.0.1.0.SJZMIXM (global), errored during super and would only bootloop, 12.5.4 or 12.5.8 wouldn't flash with miflash anymore. Worked around this by flashing Orangefox Recovery to flash Orangefox zip followed then by the V13.0.1.0.SJZEUXM ROM itself successfully.
I then decided to try out Pixel Experience as I haven't used it in years.
Pixel Experience uses it's own recovery, flashed the recovery using fastboot, wiped the data through the recovery and then patched the Pixel Experience ROM itself. Google pay seems to be working albeit I have to verify my card with my bank manually right now so hopefully that goes okay (waiting on a response right now)
As a sidenote netflix appears fine in my google play store.
So I'm unsure where the discrepency is, my apologies on posting so much but hopefully some of these help to find the issue to help myself or others in future. Thank you for all the hard work you put into this too

McguyverZero said:
Just some additional notes as I saw there was a MIUI 13.0.1 available, Attempted to fastboot into MIUI V13.0.1.0.SJZMIXM (global), errored during super and would only bootloop, 12.5.4 or 12.5.8 wouldn't flash with miflash anymore. Worked around this by flashing Orangefox Recovery to flash Orangefox zip followed then by the V13.0.1.0.SJZEUXM ROM itself successfully.
I then decided to try out Pixel Experience as I haven't used it in years.
Pixel Experience uses it's own recovery, flashed the recovery using fastboot, wiped the data through the recovery and then patched the Pixel Experience ROM itself. Google pay seems to be working albeit I have to verify my card with my bank manually right now so hopefully that goes okay (waiting on a response right now)
As a sidenote netflix appears fine in my google play store.
So I'm unsure where the discrepency is, my apologies on posting so much but hopefully some of these help to find the issue to help myself or others in future. Thank you for all the hard work you put into this too
Click to expand...
Click to collapse
OK hopefully I fixed the issue and the build that will be uploaded soon will include the following:
* Fix netflix not showing up in store (clean google play service & play store data if you are running the previous version, it might take a few minutes to show up)
* Made a better fix for Google hotword not working (Device model will show up properly now instead)
* September security patch
* Fixed permissions issue with GMS that caused crashes
* Updated some outdated prebuilt gapps
EDIT: Build is being uploaded now

I'm install android 13 GSI Rom in my Samsung Galaxy A70 can't boot direct reboot phone to download mode, Official android 13 AOSP GSI ROM have no issue in my phone boot and working well, but we don't have write permission on AOSP official ROM.