[UNOFFICIAL] AOSiP 9.0 Pizza (by Dark98) - Moto G7 Power ROMs, Kernels, Recoveries, & Other D

{
"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"
}
Android Open Source illusion Project​ About us:
AOSIP is a quality custom rom based purely on GOOGLE AOSP source since 6.0 release. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
ROM built by Dark98
Code:
[B][CENTER] **** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! **** [/CENTER][/B]
Instructions:
Remove your Google account.
Flash latest firmware with the set of commands attached.
"Fastboot boot" TWRP/OrangeFOX, flash copypartitions.zip and flash ROM.
Boot system
Optional: boot TWRP/OFOX after the first boot, and flash recovery installer/Magisk/GApps
Downloads:
ROM: AOSiP-9.0-Pizza-ocean-20200218.zip
GAPPS: OpenGApps
Known Issues:
VOIP calls don't work properly.
Some battery drain that'll get fixed in the next build.
You tell me.
Reporting bugs:
Grab a logcat right after the problem has occurred (please include at least a few pages of the log, not just the last few lines, unless you know what you're doing). Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
Join our Telegram group for more cool stuff (OrangeFOX, more ROMs, help, guides, etc.): Click here
Version Information
ROM OS Version: 9.x Pie
Status: Stable
Source code: https://github.com/AOSiP
Kernel: https://github.com/LineageOS/android_kernel_motorola_sdm632
Created: 2020-02-17
Last Updated: 2020-02-18

i installed this rom its been pretty solid phone boots up fast is what i like the most I don't think the battery drain is as bad as the OP made it sound. I had a little trouble installing with his installing rules cause you have to erase user data before you boot up the rom for it to boot right. I suggest installing with no sd card in the phone (sd cards have giving many issues if not compatible and set up to you phone.) so i used sideload to install any rom on this phone not just this one.
HERE IS WHAT I DO
Extract stock ROM to ADB folder and follow these steps from the command prompt
restart phone to bootloader and type these commands on your computer must have ADB AND FASTBOOT INSTALLED i suggest using linux
fastboot set_active a
fastboot reboot-bootloader
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Let phone bootup into the set up screen then restart the phone in to bootloader again
now you want to boot in twrp by typing this in the bootloader and i renamed my twrp file to twrp.img
fastboot boot twrp.img
then i sideloaded the partition ab file ( partition-ab.zip must be in adb folder)
adb sideload copy-partitions.zip
make sure you reboot to the b partition before you reboot to bootloader
restarted bootloader
fastboot boot twrp.img
adb sideload (name of ROM) (ROM must be in ADB folder)
restart to bootloader then type these commands other wise the phone will be stuck on the loading screen
fastboot erase userdata
fastboot reboot
start phone
if you want to install twrp or orangefox now is the time
you can install open gapps and magisk if you like

Bump for AOSiP! I've been using this February pie build now for a few days and it has ran great. When I initially installed I formatted data then flashed copy partitions AB zip then reboot bootloader, booted orange via fastboot, wiped then flashed rom, rebooted bootloader, booted orange fox recovery via fastboot, flashed gapps, rebooted system. I believe I ended up doing a erase userdata with fastboot afterwards and it booted fine and I went and flashed magisk for root a bit later after I was all setup.. I haven't yet tweaked doze how I normally do in a more aggressive way and I haven't made any other adjustments that i normally do but I will now so I'll be able to compare more on how battery is for me on my device after I do some of my usual tweaks but haven't noticed any abnormal drainage thus far but haven't been studying it much either... I say that in reference to the op known issues battery drain.. AOSiP has always been a favorite of mine. I hope this rom stays and/or it's cousin Derpfest becomes a thing at some point. ? Would definitely be awesome! I appreciate you building this rom and sharing with us all!! :good::good:
Everyone stay safe where ever you are located. I hope nobody gets this crud going around. I may attempt to compile some things from Gcloud. Going to look more into that..

Related

[10] [GSI] crDroid [ARM64-A/AB] [Experimental]

{
"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: I am not responsible for any damage you made to your device.
You have been warned!
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today.
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Screenshots:
https://crdroid.net
Note: some specific features maybe be missing due to the generic nature of GSIs.
Flashing Instructions:
Pre-installation:
Open bootloader
SHRP, OrangeFox or TWRP working recovery
Gapps: Download from here
Magisk 20.3 or newer for root (after first boot): Download from here - More info
First time installation:
The basic steps for flashing a GSI are:
1. Download the GSI file and uncompress the .7z archive
2. Uninstall Magisk if it was previously installed, by using its uninstaller and reboot the phone
3. Wipe Data, Dalvik, and Cache partitions
4. Flash the GSI to system partition, GApps, and maybe specific files for your phone (see post 2)
5. Boot and perform a minimal setup (enabling USB Debugging as a suggestion)
6. Reboot into recovery and flash Magisk
7. Reboot and enjoy!
There is more detailed information on GSI and how to flash it on phhusson’s wiki and in his thread here on xda. Also vince31fr brings useful info and workarounds.
Update installation:
1. Download the GSI file and uncompress the .7z archive to get the .img file
2. (Optional) Uninstall Magisk if it was previously installed, by using its uninstaller and reboot the phone
3. Wipe Dalvik and Cache partitions
4. Flash the GSI (.img file) to system partition, GApps, and maybe specific files for your phone (see post 2)
5. Boot and perform a minimal setup (enabling USB Debugging as a suggestion)
6. If you uninstall Magisk (step 2), reboot into recovery and flash Magisk
7. Reboot and enjoy!
Sources:
ROM: https://github.com/crdroidandroid
Patches: https://github.com/phhusson/treble_experimentations/releases
Known issues:
Camera
Download:
ROM: https://androidfilehost.com
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help crDroid Team pay their server costs
Issues and workarounds:
1. Check your phone compatibility with Treble before following these instructions.
2. Generally, smart charging feature (Settings > Battery > Smart Charging) does not work on Treble. You can have the same functionality using Battery Charge Limit app.
3. Can't flash Gapps due to error 70 (insufficient storage space available in System partition)? In TWRP, just go to Wipe menu > Advanced Wipe > check System partition > Partition options > Resize FS. Then flash Gapps again. In other recoveries, the steps are similar.
4. To get Viper4Android working on GSI ROMs, please, thank here or the Magisk modules.
5. For RAW support on cameras: Settings > Phh Treble Settings > Misc features > and select Expose Aux cameras (Qualcomm) if possible.
6. You may need to flash the vbmeta.img file specific for your device (firmware) before you first boot the GSI. Discover your actual slot: check in TWRP reboot options or in fastboot mode: fastboot getvar current-slot. Then run in the same slot you're flashing the GSI image:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
7. If you lose Wi-Fi and/or Bluetooth, you should flash the dtbo.img file specific for your device (firmware). Discover your actual slot: check in TWRP reboot options or in fastboot mode: fastboot getvar current-slot. Then run in the same slot you're flashing the GSI image:
For A/B devices, run:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
For A-only devices, run:
fastboot flash dtbo dtbo.img
8. Additional files as Permissiver v5 and DM-verity, forced encryption, and disc quota disabler must be needed to boot.
Bugs?
vytska69 said:
Bugs?
Click to expand...
Click to collapse
You tell me. I've tested on just one phone.
Does not see the sim card. No 3g / 4g. Redmi Note 8 pro.
Technical said:
You tell me. I've tested on just one phone.
Click to expand...
Click to collapse
Perfect on top of LOS171 base on Moto g7 River xt1962-1 and VZW (CDMA). Great job, thanks
numser said:
Does not see the sim card. No 3g / 4g. Redmi Note 8 pro.
Click to expand...
Click to collapse
Thanks for testing it.
Probably you need to flash dtbo.img that comes with your firmware package in your active slot:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
Please, let me know and I'll update post 2.
HueyT said:
Perfect on top of LOS171 base on Moto g7 River xt1962-1 and VZW (CDMA). Great job, thanks
Click to expand...
Click to collapse
Thank you for testing. Please, let me know if something goes wrong with sensors (the most delicate part of building gsi's imho).
Brightness and auto brightness dont work in Samsung J7 Pro (J730)
Gheartxz2017 said:
Brightness and auto brightness dont work in Samsung J7 Pro (J730)
Click to expand...
Click to collapse
Thank you for testing and reporting. I was expecting this due to failure to apply 0043-Add-samsung-light-2.patch from phh...
Is there any app that can help you by-passing it? Like https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite or https://play.google.com/store/apps/details?id=com.velis.auto.brightness
Technical said:
Thanks for testing it.
Probably you need to flash dtbo.img that comes with your firmware package in your active slot:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
Please, let me know and I'll update post 2.
Click to expand...
Click to collapse
Temporarily CFW. I will definitely check it out. Thank. :good:
Technical said:
Issues and workarounds:
6. On A/B devices, you may need to flash a vbmeta.img file specific for your device before you first boot the GSI.
must be needed to boot.
Click to expand...
Click to collapse
Hello.
how to flash vbmeta.img please ? thanks
skeeter92 said:
Hello.
how to flash vbmeta.img please ? thanks
Click to expand...
Click to collapse
1. Open bootloader and custom recovery are mandatory (see OP).
2. Download the latest (official) firmware for your device. Extract the vbmeta.img file and put into your adb/fastboot folder.
3. Go to fastboot mode and from command line, flash vbmeta.img:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Technical said:
Thanks for testing it.
Probably you need to flash dtbo.img that comes with your firmware package in your active slot:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
Please, let me know and I'll update post 2.
Click to expand...
Click to collapse
fastboot flash dtbo dtbo.img if so?
perfect and all is well on Moto G7 plus XT-1965-2...... I flashed gsi over stock 10....then flashed permissiver 4, then my device specific Twrp installer..... reboot repaired file system in advanced wipe to add space for gapps no issue... booted canary magisk....
numser said:
fastboot flash dtbo dtbo.img if so?
Click to expand...
Click to collapse
Yeah, if your device is A-only (not A/B partition).
Technical said:
Thank you for testing and reporting. I was expecting this due to failure to apply 0043-Add-samsung-light-2.patch from phh...
Is there any app that can help you by-passing it? Like https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite or https://play.google.com/store/apps/details?id=com.velis.auto.brightness
Click to expand...
Click to collapse
Thanks brightness works fine ..... but now camera and flashlight isn't available in last build
numser said:
fastboot flash dtbo dtbo.img if so?
Click to expand...
Click to collapse
I think so.
May i know for samsung note10 plus the vbmeta.img is flash on which partition?? Tks
orbital_71 said:
May i know for samsung note10 plus the vbmeta.img is flash on which partition?? Tks
Click to expand...
Click to collapse
The same partition you're flashing the GSI (system.img). You can check in TWRP which is the actual slot you're using.
Also in bootloader, you can run:
fastboot getvar current-slot

CrDroid 7.x for lake

{
"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
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
-> Boot twrp \(or reboot to twrp\)
-> Flash copy-partitions-AB.zip
-> Choose Wipe, Format data (type "yes")
-> Flash ROM.zip
-> Flash twrp.zip
-> Reboot
If you want GApps & Magisk, after you've booted once, then reboot to twrp and also do..
-> Choose Wipe, Format data (type "yes")
-> Flash GApps.zip
-> Flash Magisk.zip
-> Reboot && Profit
Reboot
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel url
Download:
ROM SourceForge>
Known issues:
Visit official website @ crDroid.net
crDroid Lake Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
VtrManfredini said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
-> Boot twrp \(or reboot to twrp\)
-> Flash copy-partitions-AB.zip
-> Choose Wipe, Format data (type "yes")
-> Flash ROM.zip
-> Flash twrp.zip
-> Reboot
If you want GApps & Magisk, after you've booted once, then reboot to twrp and also do..
-> Choose Wipe, Format data (type "yes")
-> Flash GApps.zip
-> Flash Magisk.zip
-> Reboot && Profit
Reboot
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel url
Download:
ROM SourceForge>
Known issues:
Visit official website @ crDroid.net
crDroid Lake Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Click to expand...
Click to collapse
ty
Great work of Vitor and others.
I rely on crdroid 6/7 on my XT1685's, so happy to see it been ported to XT1965
PBRP is also a nice embellished alternative to TWRP. Not sure if I should flash TWRP 3.5 again or stick with this unofficial PBRP 3.0 . It works fine anyway.
I am grateful as always to all devs involved in making an effort to make such as smooth ROM available.
Highly recommended for people with XT1965.
Thanx heaps !
VtrManfredini said:
Flashing Instructions:​
-> Boot twrp \(or reboot to twrp\)
-> Flash copy-partitions-AB.zip
-> Choose Wipe, Format data (type "yes")
-> Flash ROM.zip
-> Flash twrp.zip
-> Reboot
Click to expand...
Click to collapse
Where do I find the files listed:
copy-partitions-AB.zip (is it https://forum.xda-developers.com/t/twrp-for-moto-g7-river.3921365/ ?)
ROM.zip: is this "crDroidAndroid-11.0-20210913-lake-v7.10.zip"?
twrp.zip: is this "twrp-installer-3.5.2_9-0-lake.zip"
Isn't copy-partitions-AB only for the Moto G7 and NOT the G7 Plus?
I'm used to loading TWRP and then flashing:
crDroidAndroid-11.0-20210913-lake-v7.10.zip
NikGapps-core-arm64-11-20210918-signed.zip
Magisk-v23.zip
I'm doing this on a new phone.
Is the process different now?
Are these the steps I should use?
Unlock the bootloader
Install TWRP
Reboot to TWRP
Install crDroid
Reboot to TWRP
Install NikGapps and Magisk
Reboot to TWRP
Wipe Dalvick and Cache
Boot to System
jockovonred said:
Where do I find the files listed:
copy-partitions-AB.zip (is it https://forum.xda-developers.com/t/twrp-for-moto-g7-river.3921365/ ?)
ROM.zip: is this "crDroidAndroid-11.0-20210913-lake-v7.10.zip"?
twrp.zip: is this "twrp-installer-3.5.2_9-0-lake.zip"
Isn't copy-partitions-AB only for the Moto G7 and NOT the G7 Plus?
I'm used to loading TWRP and then flashing:
crDroidAndroid-11.0-20210913-lake-v7.10.zip
NikGapps-core-arm64-11-20210918-signed.zip
Magisk-v23.zip
I'm doing this on a new phone.
Is the process different now?
Are these the steps I should use?
Unlock the bootloader
Install TWRP
Reboot to TWRP
Install crDroid
Reboot to TWRP
Install NikGapps and Magisk
Reboot to TWRP
Wipe Dalvick and Cache
Boot to System
Click to expand...
Click to collapse
I'll update the rom and post as well, with more detailed instructions
VtrManfredini said:
I'll update the rom and post as well, with more detailed instructions
Click to expand...
Click to collapse
Do you have an update? I picked up the XT1965-T and am ready to unlock, root, flash crDroid.
Here are the steps I've used and it has worked quite well. It comes with the usual caveats of do this at your own risk.
Record phone information:
-> open cmd prompt for platform-tools folder
-> mkdir MoreInfo
-> boot into bootloader (hold power and volume down, then power and volume up but don't hold)
-> connect phone to PC
-> fastboot devices (should return serialno result for phone)
-> fastboot --version > MoreInfo\fastboot_version.txt
-> fastboot getvar all 2> MoreInfo\fastboot_getvar_all.txt
-> fastboot oem hw 2> MoreInfo\fastboot_oem_hw.txt
-> fastboot oem partition 2> MoreInfo\fastboot_oem_partition.txt
-> fastboot oem get_unlock_data 2> MoreInfo\fastboot_oem_get_unlock_data.txt
Backup EFS and partitions:
-> Boot into Bootloader
-> fastboot boot <twrp>.img
-> nandroid backup
at a minimum:
efs
modem
system
data
mount system, backup build.prop to zfiles\backup
(I was able to backup ALL the partitions)
-> copy backups off phone to storage either via PC or OTG/USB flash drive
INFO
adb devices (should start adb and return serialno result for phone)
adb shell "ls -la /dev/block/by-name/" > MoreInfo\block_partitions.txt
adb shell "ls -al /dev/block/platform", use result in next query
adb shell "ls -al /dev/block/platform/soc", use result in next query
adb shell "ls -la /dev/block/platform/soc/c0c4000.sdhci/by-name/" > MoreInfo\soc_partitions.txt
adb shell "cat /proc/mounts" > MoreInfo\mounts.txt
adb shell "df" > MoreInfo\df.txt
MISCELLANEOUS
adb shell "cat default.prop" > MoreInfo\default.prop
adb shell "cat /proc/cpuinfo" > MoreInfo\cpuinfo.txt
adb shell "cat /proc/meminfo" > MoreInfo\meminfo.txt
adb shell "cat /proc/partitions" > MoreInfo\partitions.txt
adb shell "cat /sdcard/zfiles/backup/build.prop" > MoreInfo\build.prop
BACKUP
adb shell "dd if=/dev/block/mmcblk0p57 of=/sdcard/logo_a.img bs=4096"
adb shell "dd if=/dev/block/mmcblk0p58 of=/sdcard/logo_b.img bs=4096"
adb shell "dd if=/dev/block/mmcblk0p45 of=/sdcard/boot_a.img bs=4096"
adb shell "dd if=/dev/block/mmcblk0p46 of=/sdcard/boot_b.img bs=4096"
adb shell "dd if=/dev/block/mmcblk0p68 of=/sdcard/system_a.img bs=4096"
adb shell "dd if=/dev/block/mmcblk0p69 of=/sdcard/system_b.img bs=4096"
modemst1 -> /dev/block/mmcblk0p34
modemst2 -> /dev/block/mmcblk0p35
adb shell "dd if=/dev/block/mmcblk0p34 of=/sdcard/efs1.img bs=4096"
adb shell "dd if=/dev/block/mmcblk0p35 of=/sdcard/efs2.img bs=4096"
Unlock the bootloader. (This is only done one time.)
-> Steps: https://forum.xda-developers.com/t/guide-unlock-your-g7-bootloader.3906858/
Install ROM:
-> Boot into Bootloader
-> fastboot boot <twrp>.img
- - OR - - -
-> Boot into TWRP Recovery (if already installed)
-> Flash <copy-partitions.zip
-> Flash modified boot logo (I modified the file to load it via TWRP)
- - OR - - -
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
-> Choose Wipe, Format data (type "yes")
-> Flash <ROM>.zip
-> Flash <twrp>.zip
-> Reboot into Recovery
-> Reboot into System
-> Reboot into Recovery
-> Flash <GApps>.zip, NikGapps Core (or OpenGapps Nano)
-> Flash <Magisk>.zip (or apk as it works too)
-> Reboot into System
Pass SafetyNet:
-> Open Magisk and update it
-> To pass SafetyNet, enable MagiskHide in Magisk
-> in MagiskHide, ensure Google Play servies is enabled
-> Test SafetyNet
If any issues, flash stock image of choice:
-> flashfile.bat
- - OR - - -
-> use LMSA (Rescue and Smart Assistant)
I have successfully flashed the following stock images without issue -
Lolinet:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
LAKE_RETAIL_10_QPWS30.61-21-18-7-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1965-T_LAKE_RETLA_10_QPWS30.61-21-18-7-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1965-T_LAKE_RETLA_10_QPWS30.61-21-18-7-10_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
LMSA:
LAKE_QPWS30.61_21_18_7_12_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
* * FILES * *
TWRP:
Download TWRP for lake
Download TWRP Open Recovery for lake
dl.twrp.me
twrp-3.5.2_9-0-lake.img
twrp-installer-3.5.2_9-0-lake.zip
copy-partitions from
either from XDA:
While on Slot_A Flash copypartitions.zip??
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip" I cant find the copypartitions.zip please help thanks
forum.xda-developers.com
or
TWRP for Moto G7 (river)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
copy-partitions-AB.zip (androidfilehost)
(info: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/)
or from lineageOS:
Install LineageOS on lake | LineageOS Wiki
wiki.lineageos.org
copy-partitions-20210323_1922.zip
modified boot logo:
[Bootlogo] Modded Bootlogo from unlocked bootloader!!!
FOR MOTO G7 PLUS ONLY!!! Hello, everyone. I modified the original logo.bin file of the Moto G7 Plus for those who want to unlock the bootloader and take the screen of "unlocked bootloader ". Just use the command: fastboot flash logo...
forum.xda-developers.com
crDroid:
crDroid.net - Download crDroid for supported devices
official crDroid ROM website
crdroid.net
crDroidAndroid-11.0-20211016-lake-v7.11.zip
NikGapps:
NikGapps - Browse /Releases/NikGapps-R/18-Oct-2021 at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net
NikGapps-full-arm64-11-20211018-signed.zip
Magisk:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Magisk-v23.0.apk (no need to rename to Magisk-v23.0.zip)
flashfile.bat:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
jockovonred said:
Here are the steps I've used and it has worked quite well. It comes with the usual caveats of do this at your own risk.
Click to expand...
Click to collapse
I appreciate you have created this extensive list of steps
Albeit I don't need the instructions myself , since I am already running crDroid11 7.11, I will keep it in my notes if I ever get my hands on another G7+.
Thanks for your efforts.
Is there any chance we can have an update with the December 2021 security patches?
Also, is there any chance we can have a "double tap to wake" feature, like the G5+?
jockovonred said:
Also, is there any chance we can have a "double tap to wake" feature, like the G5+?
Click to expand...
Click to collapse
I totally agree this is a true missing feature in crdroid 7 for lake, which was available in crdroid 6 for potter !
Happy new year! I am looking forward to continued updates for this ROM. If there's a way I can contribute, let me know.
Hello,
Any plans on updating this ROM? Even just a security patch update would be nice. Thanks for all the hard work.
How does the Moto G5 Plus get security updates on CrDroid, but Moto G7 Plus does not?
jockovonred said:
How does the Moto G5 Plus get security updates on CrDroid, but Moto G7 Plus does not?
Click to expand...
Click to collapse
Different people maintaining those two devices.
Hi! How's battery and stability? Did you guys notice any bugs? I'm thinking of flashing this ROM on my gf's G7.
Thanks!
jockovonred said:
Here are the steps I've used and it has worked quite well. It comes with the usual caveats of do this at your own risk.
Install ROM:
.
.
.
-> Reboot into System
-> Reboot into Recovery
Click to expand...
Click to collapse
How to "Reboot into Recovery" while in the System?
proza said:
How to "Reboot into Recovery" while in the System?
Click to expand...
Click to collapse
With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
Video:
The instructions indicate booting into System.
Then booting into Recovery following the usual process.
This means powering off the device after booting into System, and then entering Recovery.
Hence the wording "Reboot".
Also with TWRP installed, select Recovery in the power settings when in System:
-> Hold power button
-> Select Power, then Restart, then Recovery
jockovonred said:
With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
Click to expand...
Click to collapse
With the phone powered off, how to boot into bootloader?
proza said:
With the phone powered off, how to boot into bootloader?
Click to expand...
Click to collapse
Vol- + Power into Bootloader. From there select Recovery, etc...
The GPS location does not work, how to fix it?

[ROM] [OFFICIAL] [STABLE] [R] DotOS 5.2.1 [MOTO X4 - PAYTON] [23/11/2021]

View attachment 5438975
" #DroidOnTime "
ROM Version: 5.2.1
Device: PAYTON
Maintainer: AADITYAZEO
Build Status: OFFICIAL
View attachment 5438991​
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.​
Click to expand...
Click to collapse
"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration."
View attachment 5438997
dotOS is an Android ROM that focuses on performance, stability, and User Experience. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get the most out of your device.....
View attachment 5438999
CLEAN FLASH/First Time Installation :
01. Download the ROM, Firmware and GApps from the links above.
02. If you're coming from Oreo Flash the PIE Firmware (Factory Image or Firmware ONLY) for your device.
03. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
04. Create backup. i.e. EFS
## YOU ONLY NEED THIS STEP ONCE.. When updating Firmware's ##
05.At this point Flash "Copy Partitions Zip" In TWRP "SLOT A"
06. Flash the ROM and TWRP installer.
07. Choose Reboot -> Recovery
08. Install GApps & Magisk.
09. Reboot -> Bootloader
10. fastboot -w
11. Reboot and Enjoy.
*Note-1: Slots, ROMS install to opposite (inactive) slot
If you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"
*Note-2: Firmware's
* Recommended to install to "Slot A" unless you have PIE firmware fully installed on "Slot B" (you can achieve this with Firmware ONLY Links or copypartitions.zip ran from Slot A after a full stock update)
DIRTY FLASH :
1.Download the latest build.
2.Reboot to recovery.
3.Flash the latest build along with the twrp.
4.reboot to recovery. (very Important)*
5.flash optional packages like gapps and magisk.
6.Wipe Cache.
7.Reboot.
Note: If upgrading from 5.0.* to 5.1.* a clean flash is required.
Note: GApps only has to be flashed once whereas Magisk/Su is to be flashed every time you Dirty Flash the OTA Update.
View attachment 5439003
CLICK ME
View attachment 5439005
COMPLETE CHANGELOG : https://changelogs.droidontime.com/
View attachment 5439007
AOSP
Lineage OS
Pixel Experience
Dirty Unicorns
Project Lighthouse
And all other open-source Devs/Teams.
View attachment 5439009
Mohan CM - Founder/Core Developer
Iacob Ionut - UI, UX Developer/ Core Developer
Sipun Kumar - Developer/Maintainer
Special thanks:
Manish Bajpai - Web Developer
Important Links
If you liked our Project, please consider supporting us. - Donate - https://www.paypal.me/MOHANCM
Donate to device maintainer. - Donate - https://www.paypal.me/jackvortexhd
dot OS source
dotOS-Device Sources
{
"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"
}
Telegram Group
Telegram Channel
Website
Downloads page
REPORTING BUGS !
As soon as the problem occurs, take a LOGCAT!
for more READ THIS
and do not forget to send it to us
View attachment 5439011
Contributors: AadityaZeo
Source Code: https://github.com/DotOS
GitHub : - https://github.com/aadityazeo
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Current Stable Version: v5.2.1
Stable Release Date: 23-11-2021​
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Same problem be my.
Randy Power said:
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Click to expand...
Click to collapse
Which Verison of twrp you're using?
Aaditya ZeO said:
Which Verison of twrp you're using?
Click to expand...
Click to collapse
twrp-3.6.0_9-0-payton
I've also tried installing dot without installing twrp. When I do this, booting to system gives me the booting animation (3 colored circles that look like two planets circling the sun). But it gets stuck there. One time, I waited for several hours, enjoying the planets animation.
Randy Power said:
twrp-3.6.0_9-0-payton
I've also tried installing dot without installing twrp. When I do this, boring to system gives me the booting animation (3 colored circles that look like two planets circling the sun). But it gets stuck there. One time, I waited for several hours, enjoying the planets animation.
Click to expand...
Click to collapse
There're quite few things which you need to remember.
1st
2nd
If you were stuck on boot logo, you should perform fastboot - w in bootloader.
3rd - as per your comment u want vanilla edition. So i suggest u to stick with two 3.5xxx (latest prior to version 3.6xx) and follow the steps as stated below
a) completely wipe the phone
b) rom + twrp
c) reboot to recovery
d) wipe data in twrp
e) reboot to system.
This should work as I've also installed vanilla Verison with same process.
Thank you very much, @Aaditya ZeO. I will try again with those steps when I get back to my x4 today.
If i want to install the gapps version, should I use twrp 3.6 instead of 3.5?
Randy Power said:
Thank you very much, @Aaditya ZeO. I will try again with those steps when I get back to my x4 today.
If i want to install the gapps version, should I use twrp 3.6 instead of 3.5?
Click to expand...
Click to collapse
I don't think it matters, I've use twrp 3.2 and 3.6 to install gapps and had no issues in either case.
I appreciate the suggestions. I think I've tried everything, including installing twrp 3.5.xxx, but I still get the same result.
If I clean install dot and fastwipe -w , I still get the spinning planets.
If I clean install dot, install twrp 3.5 or 3.6, and fastwipe -w, a "reboot system" always brings up twrp again.
In case it matters, my device is payton XT1900-1 32GB P4.
Randy Power said:
I appreciate the suggestions. I think I've tried everything, including installing twrp 3.5.xxx, but I still get the same result.
If I clean install dot and fastwipe -w , I still get the spinning planets.
If I clean install dot, install twrp 3.5 or 3.6, and fastwipe -w, a "reboot system" always brings up twrp again.
In case it matters, my device is payton XT1900-1 32GB P4.
Click to expand...
Click to collapse
Can you try to install gapps version for once?
I just did this:
fastboot boot twrp
completely wipe the phone
install rom 5.2.1 (dotOS-R-v5.2.1-payton-GAPPS-20211123-1226.zip)
install twrp (twrp-installer-3.5.2_9-0-payton.zip)
reboot to bootloader
fastboot boot twrp (in retrospect, I could have rebooted to twrp without fastboot)
wipe data in twrp
format data in twrp
reboot to bootloader; fastwipe -w
reboot to system.
Result: Spinning planets (boot animation).
I'll try again with the above, except step 5-6 reboot directly to twrp.
By the way, is this the expected result of "fastboot -w" on the x4?
Code:
>fastboot -w
Erasing 'userdata' OKAY [ 0.322s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
After the above, I formatted data from twrp. It completed without errors, so I rebooted to system.
Result: Still stuck on spinning planets.
Randy Power said:
I just did this:
fastboot boot twrp
completely wipe the phone
install rom 5.2.1 (dotOS-R-v5.2.1-payton-GAPPS-20211123-1226.zip)
install twrp (twrp-installer-3.5.2_9-0-payton.zip)
reboot to bootloader
fastboot boot twrp (in retrospect, I could have rebooted to twrp without fastboot)
wipe data in twrp
format data in twrp
reboot to bootloader; fastwipe -w
reboot to system.
Result: Spinning planets (boot animation).
I'll try again with the above, except step 5-6 reboot directly to twrp.
By the way, is this the expected result of "fastboot -w" on the x4?
Code:
>fastboot -w
Erasing 'userdata' OKAY [ 0.322s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
nope this shouldn't be the output after the fastboot -w.
Aaditya ZeO said:
nope this shouldn't be the output after the fastboot -w.
Click to expand...
Click to collapse
I appreciate that. I've tried many combinations of formatting data in TWRP, which seems to work. Resizing the partition and fsck on the partition work fine, all in TWRP. I can even copy files from /externalsd to /sdcard, and the fs survives a reboot.
However, fastboot -w always fails (error shown above), and booting the system gives spinning planets animation forever.
I'd be grateful for pointers on fixing the fastboot -w problem, if that is what's needed.
Hello
I installed dotOS 5.2.1 and when it's time to enter the PIN code it says that the sim card is locked. Tried both PIN and PUK, but none works. What should I do?
OK, so I solved it by basically following these instructions:
However, I now have a new problem. If I power off the phone while the USB charger is connected, it restarts the phone instead. And if it's powered off and I connect the charger, it turns itself on. This didn't happen with Android 9. How can I fix it? I do not want my phone to switch itself on when charging.
Randy Power said:
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Click to expand...
Click to collapse
Are you flashing to the appropriate slot?
For those having problems with the phone rebooting after a few seconds after upgrading from an Android 9 rom:
You might need to upgrade the modem firmware. That happened to me while upgrading from Lineage 16.0 to Lineage 18.1. After investigating a bit, I figured out the problem happened when connecting to the mobile network or (sometimes) wifi.
This is (roughly) how I solved the problem:
- flash your choice of recovery/system (not needed if already done - if you do this later your updated firmware might be overwritten)
- download the latest payton stock rom from lolinet's obsolete phones archive
- unzip and cd to unzipped folder
- connect phone and reboot to bootloader
- make sure you have fastboot and run the following commands (adapt to your OS as needed):
mfastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot erase carrier
fastboot erase userdata (I did it after backing up my data, but I think it was not necessary)
fastboot erase ddr
fastboot reboot
- have fun!
Notes:
- you might just flash a subset of the binaries above, I flashed what I thought was needed. The original reddit thread mentioned only NON-HLOS.bin and fsg.bin
- after having tried many things I ended up with dotOS 5.2.1 and will try it for a while
References
- this reddit comment
- Method 2 at rootmygalaxy
rodrigopitanga said:
Are you flashing to the appropriate slot?
Click to expand...
Click to collapse
I think yes. It's been a few weeks now, so my memory on the details is fuzzy. But I'm familiar with the A/B monkey business, copy partitions, etc. And flashing lineage worked out successfully. Thank you for the reply.
Does adoptable storage work?

Development [RECOVERY][12][UNOFFICIAL] OrangeFox-R11.1_A12.1

OrangeFox Recovery Project
{
"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:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
OrangeFox is FREE SOFTWARE
Information
Status: unofficial Beta
Android 12 only
Version: R11.1_1
Release Date: 11th October 2022
Updated: February 2023
Maintainer: @CFKod
Sources
Device Tree: https://github.com/forforksake/recovery_device_motorola_kyoto
Kernel: Prebuilt
Downloads:
onedrive
github releases
Installation:
This is an A/B device, it does not have a recovery partition
It also does not allow fastboot boot command
Only option is this case it to fastboot flash boot ofox.img from bootloader, then select recovery mode, once booted into recovery, flash your stock boot image followed by flashing the ofox.zip (to install the recovery to ramdisk)
Code:
fastboot flash boot ofox.img
Select recovery mode from the bootloader menu
Once ofox has loaded
install your stock boot.img to boot parition
Install ofox.zip
Reboot to bootloader and then select recovery mode
You are now in Orangefox recovery
Install magisk from files menu included
https://wiki.orangefox.tech/en/guides/installing_orangefox
Documentation (FAQ):
https://wiki.orangefox.tech/en/guides
Source changelog:
https://wiki.orangefox.tech/changelog
Unlocked Bootloader required
Moto unlocking site
vbmeta flags
From bootloader, Flash vbmeta from your firmware zip using two important flags
(--disable-verification --disable-verity)
Code:
fastboot flash vbmeta --disable-verification --disable-verity vbmeta.img
Torch not yet working and in order to fit into the devices small boot image AAPT has also been removed.
XDA : DevDB Information
OrangeFox Recovery Project, Tool/Utility for Kyoto
(Tested on Motorola Edge 20 lite 5G)
Contributors
@CFKod
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* Maintainer @CFKod
ADB sideload not working with the img, it terminates sideloads with the following error: Failed to unmount vendor
The image is purely to allow you to flash your own stock boot image... Then install orange fox recovery ramdisk over your stock boot by flashing the zip
Unlocked Bootloader required
Moto unlocking site
vbmeta flags
From bootloader, Flash vbmeta from your firmware zip
using two important args
--disable-verification --disable-verity
Makefile:
fastboot flash vbmeta --disable-verification --disable-verity vbmeta.img
Thanks!
installation
From unlocked BL with patched vbmeta,
Fastboot flash boot ofox.img
Select recovery mode in bootloader > boot into ofox recovery
install your stock A12 boot.img **do not reboot**
flash release zip _this simply installs recovery ramdisk_.
flash magisk.zip if required
CFKod said:
installation
From unlocked BL with patched vbmeta,
Fastboot flash boot ofox.img
Select recovery mode in bootloader > boot into ofox recovery
install your stock A12 boot.img **do not reboot**
flash release zip _this simply installs recovery ramdisk_.
flash magisk.zip if required
Click to expand...
Click to collapse
i cant neither boot or flash the recovery
i have magisk installed anf i have ramdisk. what is wrong here??? thx for help
hmmm, now i 'm getting error E3004: this package is for kyoto. this device not supported
update: i'm now able to flash orangefox.img, but when i boot to recovery ,instead it reboots bootloader :\
freakologik said:
update: i'm now able to flash orangefox.img, but when i boot to recovery ,instead it reboots bootloader :\
Click to expand...
Click to collapse
Sorry for the delay
I have now resolved that issue
Please see the ofox Img...
This will allow you to boot recovery
Then install stock
Followed by ofox zip
ofox
Folder
1drv.ms
freakologik said:
i cant neither boot or flash the recovery
View attachment 5729847
i have magisk installed anf i have ramdisk. what is wrong here??? thx for help we
Click to expand...
Click to collapse
freakologik said:
i cant neither boot or flash the recovery
View attachment 5729847
i have magisk installed anf i have ramdisk. what is wrong here??? thx for help
Click to expand...
Click to collapse
Wait..
The device doesn't have a recovery partition and it also doesn't allow us to fastboot boot
It only allows us to fastboot flash boot boot.img
I tried to make that clear on the release download
I will update the main thread
CFKod said:
Wait..
The device doesn't have a recovery partition and it also doesn't allow us to fastboot boot
It only allows us to fastboot flash boot boot.img
I tried to make that clear on the release download
I will update the main thread
Click to expand...
Click to collapse
yeah in the meantime i've understand it
i try install now
thanks for your work and time
freakologik said:
yeah in the meantime i've understand it
i try install now
thanks for your work and time
Click to expand...
Click to collapse
Thanks, I overly panicked haha.
If you are on telegram
Feel free to message me directly
@cardiffian
it's working,finally!!!
a question : to use the recovery can i never use pin/fingerprint? it's not clear for me
freakologik said:
it's working,finally!!!
a question : to use the recovery can i never use pin/fingerprint? it's not clear for me
Click to expand...
Click to collapse
Fantastic news
Well, try rebooting to android,
Create the lockscreen protection again;
Reboot to OrangeFox
Decrypt... Fingers crossed
So I successfully decrypted user data on my first beta dated 03-10-22
Used it perfectly for quite a few days.
I've added a folder to onedrive as 03102022 with the zip, feel free to try it if you can't get anywhere with user decryption in current build.
However, I have since had to make some build tweaks to try and improve what we had... Testing backup restore etc...
Now Userdata decryption only works for me when lockscreen pin is removed...
I'm correcting some annoyances and mount errors in the logs... And reverting some of the changes I have since made. So will let you know once I have uploaded.
Also some excellent advice on the ofox wiki - I have format /data already to test the feature, so perhaps my next step is fastboot - w and start a fresh
https://wiki.orangefox.tech/en/guides/encryption
Only tested on a 12
Unfortunately I no longer have a working kyoto device
Smashed the LCD for a 2nd time.
I can access the device itself via adb, so I get to mess around with phonesploit / metasploit framework without any worry if I break it
I can't see the lcds for these things becoming cheap and widely available for a while, so for now it joins the graveyard of android devices in mydrawer
Purchased a pixel 6a
@CFKod
How to upload these Recovery?
Thank you in advance.
I need help in my thread, do you know how to do it?
Questions about firmware
Hi. I want to change the software channel from pluspl to RETEU. How to do it? Anyone help? Thanks in advance, best regards.
forum.xda-developers.com
.

Development Paranoid Android Topaz Beta 1 - Redmi Note 10

{
"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"
}
We are very excited to announce Paranoid Android Topaz, based on Android 13.
On the first launch, you’ll notice a clean setup with beautiful wallpapers from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app from the PlayStore.
Our builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
We kindly ask all of you that are in a position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate on the link below:
Donate
Device-specific issues
* You tell us
Requirements
Make sure you've latest platform tools for Android.
Make sure you've MIUI Global Firmware version V14.0.3.0 flashed before flashing the ROM.
Download
You can always get our builds from our website Paranoid Android website
Note: Custom kernels and Custom recoveries are NOT supported and GMS is included!
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them. For more detailed information please have a look at the second post of this thread of each build changelog on the website.
Instructions (Firmware flashing)
Download recommended firmware zip
Extract it
Boot to bootloader
Open a terminal / command prompt in firmware-update directory and execute the following commands to flash the firmware:
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash imagefv_a imagefv.img
fastboot flash imagefv_b imagefv.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash uefisecapp_a uefisecapp.img
fastboot flash uefisecapp_b uefisecapp.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
Instructions (Recovery package)
Boot to bootloader
Download the recovery zip from here and run the following command:
fastboot update recovery-AOSPA-*.zip
Reboot to recovery with the following command:
fastboot reboot recovery
Select Wipe data/factory reset & confirm
Go back and select Apply update from ADB, and execute the following command:
adb sideload aospa-topaz-*.zip
After installation complete, Reboot to system.
Instructions (Fastboot package)
Boot to bootloader
Execute this to flash the ROM:
fastboot update --skip-reboot aospa-topaz-*-image.zip
Reboot to recovery with the following command:
fastboot reboot recovery
Select Wipe data/factory reset & confirm
Go back and reboot system.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Redmi Note 10 Community (Telegram)
Device Tree
Kernel Tree
Vendor Tree
Cheers and #StayParanoid!
Changelog for Topaz Beta 1:
- Initial beta release.
- Build kernel fully with GCC.
- Utilize most AOSPA components such as adreno, audio, av, bt, charging, display, dsprpcd, gps, init, keymaster, media, overlay, perf, telephony, usb, vibrator, wfd, wlan.
- Drop PowerOffAlarm.apk as our device has issues with the PowerOffAlarm feature.
- Transition to AOSP BT stack.
- Update GPS stack to LA.UM.9.1.r1-12900-SMxxx0.0.
- Upgrade drm to v1.4.
- Drop DisplayFeatures.
- Implement AOSP HBM (Auto-HBM that works via Auto-Brightness).
- Configure overlay for Automated DC-Dimming.
- Configure color modes overlays.
- Fixup padding.
- Fix device MAC Address handling.
- Make AoD enter doze.
- Fix ST2W/DT2W on AoD.
- Bring back CarrierConfig overlay.
- Import WFD stack from LA.UM.9.1.r1-12900-SMxxx0.0 to fix WFD.
- Import cnss-daemon from stock to fix 5GHz detection.
- Drop FM as it is mostly redundant.
- Configure QTI Bservice for optimal memory management.
- Update blobs from MIUI V14.0.3.0.SKGMIXM.
- Cleanup tree.
Kernel:
- Allow setting brightness up to 4095 for AOSP HBM.
Reserved #1
Cool
Yeah! <3
Attention​For windows user, you could use Platform Tools r31.0.3
It doesn't matter if you would to use r33 tho
You will encounter error : ANDROID_PRODUCT_OUT not set if you use latest version of r34.0.0
Dont forget to use proper Usb Driver for Android Bootloader Interface
Waxaranai said:
Cool
Click to expand...
Click to collapse
Cool
Nice

			
				
thank you
Donpablo0271 said:
Attention:
For windows user, you could use Platform Tools r31.0.3
You will encounter some error if you use latest version of r34.0.0
Click to expand...
Click to collapse
I have to flash tomorrow (waiting to unlock the bootloader).
I have platform tools r33.0.1 and r33.0.3
Do I absolutely have to use r31.0.3?
carlos974 said:
I have to flash tomorrow (waiting to unlock the bootloader).
I have platform tools r33.0.1 and r33.0.3
Do I absolutely have to use r31.0.3?
Click to expand...
Click to collapse
No you can use r33. The problem lies with r34.
cyberknight777 said:
No you can use r33. The problem lies with r34.
Click to expand...
Click to collapse
Thank you!
By the way to flash the firmware can I copy paste the commands from OP in cmd (the firmware files will be in the platform-tools directory)
carlos974 said:
Thank you!
By the way to flash the firmware can I copy paste the commands from OP in cmd (the firmware files will be in the platform-tools directory)
Click to expand...
Click to collapse
Yeah sure you can do that
I am sorry for noob questions, but which file should I download from the website? One is name "Recovery Option" and the other is "Fastboot Option". And in the instructions, how am I supposed to replicate the steps mentioned in "Instructions (Firmware flashing)"?
@ciberknight777
I unlocked my redmi note 10 this morning.
I flashed the firmware, the rom.
All went well.
I restarted the rom works fine.
But when the phone goes to sleep, I press the power button to wake it up, the screen appears but I can't unlock by sliding my finger on the unlocked canedas (I didn't put any lock)
WalinAhmed said:
I am sorry for noob questions, but which file should I download from the website? One is name "Recovery Option" and the other is "Fastboot Option". And in the instructions, how am I supposed to replicate the steps mentioned in "Instructions (Firmware flashing)"?
Click to expand...
Click to collapse
The choice is yours, you can choose whether to follow recovery option or fastboot option. Instructions are provided respectively.
As for firmware flashing, do what it says? You obviously need windows/Linux with cmd prompt / linux terminal to do so.
carlos974 said:
@ciberknight777
I unlocked my redmi note 10 this morning.
I flashed the firmware, the rom.
All went well.
I restarted the rom works fine.
But when the phone goes to sleep, I press the power button to wake it up, the screen appears but I can't unlock by sliding my finger on the unlocked canedas (I didn't put any lock)
Click to expand...
Click to collapse
What is "canedas" and I can't reprod this nor have I seen such issues being reported. I'd take it this is probably some rare AOSP meme. If you can reprod, provide logs for it. That said it's highly possible that it isn't device specific so yeah.
cyberknight777 said:
What is "canedas" and I can't reprod this nor have I seen such issues being reported. I'd take it this is probably some rare AOSP meme. If you can reprod, provide logs for it. That said it's highly possible that it isn't device specific so yeah.
Click to expand...
Click to collapse
Typo "padlock"
I changed a year ago already the broken screen by another screen not amoled but TFT
carlos974 said:
Typo "padlock"
I changed a year ago already the broken screen by another screen not amoled but TFT
Click to expand...
Click to collapse
Then it's your screen issue

Categories

Resources