{
"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?
Related
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 completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* 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.
*
*/
Features:
- Seems is working all except vibration
- Android Q Support
- Android 11 Decryption
Install guide (Reccomended):
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Other Install guide (More articulated but fully functional):
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
{
"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"
}
8. Choose the recoveryimgfilename.img
9. Swipe to install
OLD Install guide (Much more articulated but perfectly functional):
1. Follow this guide to root your device: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205
2. Flash the TWRP installer like a magisk module
3. Flashing the TWRP installer you will lose the root, so you will need to flash magisk again from magisk manager before reboot the device or you can reboot the device and flash magisk in twrp
HOW TO UPDATE a ROM and KEEP TWRP and ROOT:
Before all Disable all magisk modules for boths methods
- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk;
- Reboot.
If you want you can also update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- Menu/modules/+ button/select the twrp installer.zip and flash it;
- Always in Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
BugReport:
Please all, when you got a problem, bootloop, error in twrp, unable to do something, please be sure you have followed the guides properly and when you write here you have problem just follow this guidelines for the bugreport:
- Write what rom and version you have actually;
- Write which device you have, gm1910, gm1913, gm1917, gm1915, gm1920, gm1911.
- Write which twrp you are using (Unofficial, Officia and the version);
- If you got an error in the twrp flashing a zip, after got the error make a log using this command : "cat /tmp/recovery.log" or if you are using adb with "adb shell cat /tmp/recovery.log". Copy the output in a text file and send me it.
- Write what are you trying to do;
- Write how you flash the twrp and magisk, just write what you do.
If you don't give me this infos i can't help you.
If something doesn't work, don't just complain, but try to get the problem resolved by giving all the information you have.
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
India Fake Partition Deleter by mauronofrio
Official Builds
TWRP 3.4.0-10 Unified Unofficial Q by mauronofrio
TWRP 3.4.0-10 Unified Unofficial Installer by mauronofrio
TWRP 3.4.0-0 Unified Unofficial Q by mauronofrio
TWRP 3.4.0-0 Unified Unofficial Installer by mauronofrio
Spoiler: Show old builds
TWRP 3.3.1-79 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-79 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-79 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-76 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-76 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-76 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-75 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-75 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-75 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-74 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-65 Unified Unofficial by mauronofrio
TWRP 3.3.1-65 Unified Unofficial Installer by mauronofrio[
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_oneplus_guacamoleb_TWRP
https://github.com/mauronofrio/android_device_oneplus_guacamole_unified_TWRP
Android Pie IMG: https://gitlab.com/HolyAngel/op7
Android Q IMG: Precompiled stock one
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
Thanks to @HolyAngel for the kernel
Created 2019-05-23
Have where test this? I get my OP7 today and need root.
mauronofrio said:
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 completely theme-able. You can change just about every aspect of the look and feel.
Features:
-Seems is working
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
8. Choose the recoveryimgfilename.img
9. Swipe to install
Other Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Install guide:
Actually seems "fastboot boot twrp.img" is not working so we need to use another guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Now you should check which slot are you using with this command "fastboot getvar current-slot"
5. Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
6. Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
7. Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
8. First thing go in reboot menu and restore the old active slot
9. Now you can flash the installer (Actually you can do it using sideload, start sideload server from twrp advanced menu and from pc use this command "adb sideload twrpinstaller.zip")
If you are already rooted, you can skip all and directly flash the installer like a magisk module. Always remember that after you flashed the installer you will be unrooted.
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
TWRP 3.3.1-2 Unofficial by mauronofrio
TWRP 3.3.1-2 Unofficial Installer by mauronofrio
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_oneplus_guacamoleb_TWRP
https://gitlab.com/HolyAngel/op7
Donations:
Credits:
Thanks to @HolyAngel for the kernel
Created 2019-05-23
Click to expand...
Click to collapse
great! very useful! :good:
Hot-Proton said:
Have where test this? I get my OP7 today and need root.
Click to expand...
Click to collapse
I made the twrp for.oneplus 7 pro, they have a common kernel so the twrp is really similar, it should work without problems
recovery works but anyone got the stock recovery ?
Dragonlord07 said:
recovery works but anyone got the stock recovery ?
Click to expand...
Click to collapse
Stock recovery is in stock boot.img, flash the stock boot.img to restore the stock recovery
mauronofrio said:
Stock recovery is in stock boot.img, flash the stock boot.img to restore the stock recovery
Click to expand...
Click to collapse
i probably sound stupid but where is the stock boot.img???
Dragonlord07 said:
i probably sound stupid but where is the stock boot.img???
Click to expand...
Click to collapse
`boot.img` can be obtained from the stock ROM I guess. Extract the zip file to find it. Currently it's unavailable I think. You can search for it or check OnePlus website.
There is no stock rom for download now. I get my 7 non-pro now and test twrp. Why are there three install guides?
I can confirm that the recovery is working. I managed to flash it and use it to install Magisk. Thank you!
I found I could flash this version of TWRP and then flash the Magisk zip no problem. Magisk works fine. However, the Magisk uninstaller fails with "Unable to mount partitions" when trying to flash it in TWRP.
Ok, before push this twrp as official one, i want you test the stock rom flashing. For magisk uninstaller it's better if it gave you an error. If you want to unroot you should use the stock boot.img
I can't find the stock boot.img for standard Oneplus 7 but need to uninstall magisk via TWRP. I'm currently stuck in a bootloop to TWRP recovery after an OTA update. Any advice?
readysound said:
I can't find the stock boot.img for standard Oneplus 7 but need to uninstall magisk via TWRP. I'm currently stuck in a bootloop to TWRP recovery after an OTA update. Any advice?
Click to expand...
Click to collapse
Flash again magisk and the bootloop will stop
Thanks - that sorted it after "fastboot flash boot twrp-3.3.1-1.img" on the patched slot. If you need me to test anything give me a shout. Thanks for all of your work btw!
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
With my 6T, selecting Uninstall / Restore Images in Magisk would work for patching OTA updates to other slot. Now I get "Stock backup does not exist" both before the OTA and after.
readysound said:
Thanks - that sorted it after "fastboot flash boot twrp-3.3.1-1.img" on the patched slot. If you need me to test anything give me a shout. Thanks for all of your work btw!
Click to expand...
Click to collapse
You should not use "fastboot flash boot " command but "fastboot boot " command. The first one will flash the twrp in the boot partition, the second one will only.boot the twrp for one time.
Thanks a lot!
mauronofrio said:
You should not use "fastboot flash boot " command but "fastboot boot " command. The first one will flash the twrp in the boot partition, the second one will only.boot the twrp for one time.
Click to expand...
Click to collapse
Just an update, when performing a "fastboot boot twrp-3.3.1-1.img" command in the bootloader I get the following error (and TWRP doesn't boot) :
Sending 'boot.img' (56016 KB) OKAY [ 1.787s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm currently trying to get slot A to boot (slot B received the OTA update and I want to revert). Switching to slot A I am having the same recovery boot loop. Flashing magisk again via ADB doesn't resolve this.
readysound said:
Just an update, when performing a "fastboot boot twrp-3.3.1-1.img" command in the bootloader I get the following error (and TWRP doesn't boot) :
Sending 'boot.img' (56016 KB) OKAY [ 1.787s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm currently trying to get slot A to boot (slot B received the OTA update and I want to revert). Switching to slot A I am having the same recovery boot loop. Flashing magisk again via ADB doesn't resolve this.
Click to expand...
Click to collapse
If fastboot.boot.command doesn't work you should use the old guide, it happened also on the op7 pro, recently they included again the fastboot boot command
Can I boot thi recovery temporarily just to install magisk and not flash the installer so that I can keep the stock recovery?
{
"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
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?
{
"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
*
* 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 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.
*/
Introduction
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
TWRP version: 3.6.0_11
For device: gta4lwifi
Device tree: https://github.com/pazos/android_device_samsung_gta4lwifi
Maintainer/Authors build: paziusss
Known limitations
FBE encrypted storage (Internal Data) not able to be decrypted in TWRP.
Changelog
2021-12-08:
Added: exfat support
Added: mass storage support
Fixed: USB composition rules
Supressed audit messages in logcat
Misc changes (see device tree for details)
2021-12-05: Initial release
Motivation and credits.
AFAICT there're two TWRP builds on xda for the SM-T500, made by ragarcia87 and agreenbhm
The main motivation for Yet Another TWRP build was getting fastboot working, so we can follow official instructions to flash GSI builds on our devices.
Credits to u/agreenbhm for the device tree: https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Credits to u/ragarcia87 for the thread, which I used as a template for this one
Installation Instructions
Spoiler
From computer:
Download Odin Flashable Tar from bellow
Put tablet into Odin Download Mode
Flash Blank vbmeta via Userdata
Flash Odin Flashable Tar via AP
From TWRP:
Download recovery.img from below
Copy recovery.img to device
Install > Install Image > recovery.img to Recovery
Reboot > Recovery
Flashing system/vendor/product/odm partitions
Spoiler
Logical partitions are read only from TWRP. If you want to flash them you'll need to reboot in fastbootd.
Boot in TWRP
Go to reboot and select fastboot.
Wait until you see a TWRP dialog saying "entered in fastboot"
Once you flashed all desired partitions reboot to recovery
In recovery wipe -> format data.
Notes on GSI flashing:
/product partition is unused in GSI builds. You can flash an empty image to gain 1GB for other logical partitions.
/system partition will be resized to the size of the GSI image you're flashing.
Thanks for migrating this to Android 11! One issue I'm seeing is that I can't mount the Micro SD card.
Also, the link for your device tree seems to be broken. Could you please update?
Hi Magendanz. Thanks for your feedback.
I have no issues mounting the MicroSD card. Do you have some logs?
Updated DT link!
About the device tree: I'm having trouble pushing the changes to github because my slow connection. Will see if I got them pushed somehow. If not I will revert blobs to agreenbhm version.
Magendanz said:
Thanks for migrating this to Android 11! One issue I'm seeing is that I can't mount the Micro SD card.
Also, the link for your device tree seems to be broken. Could you please update?
Click to expand...
Click to collapse
paziusss said:
I have no issues mounting the MicroSD card. Do you have some logs?
Click to expand...
Click to collapse
Here's the log...
Hi!
Indeed, I didn't test with exfat. Should be fixed soon. Also adb sideload don't work in the version attached.
I will make the changes ASAP and give a better commit history in device tree
Hi. Device tree updated with support for exfat and ADB sideload fixed.
Will upload the binaries in a few hours!
Thanks for bringing a nicer TWRP for GSI loading to our devices. I flashed this with no issues, but I am really struggling to get my device to boot any GSI. I am sure it is something that I am doing wrong on my end, since I have not messed with Samsung devices or any GSI installations before. Is there a change to have a more in-depth guide written up on installing a GSI on our device, or is there one already available that has similar instructions? I am planning on starting from scratch once I get home, and would like to have all of my ducks in a row before attempting again.
stompysan said:
Thanks for bringing a nicer TWRP for GSI loading to our devices. I flashed this with no issues, but I am really struggling to get my device to boot any GSI. I am sure it is something that I am doing wrong on my end, since I have not messed with Samsung devices or any GSI installations before. Is there a change to have a more in-depth guide written up on installing a GSI on our device, or is there one already available that has similar instructions? I am planning on starting from scratch once I get home, and would like to have all of my ducks in a row before attempting again.
Click to expand...
Click to collapse
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Hi. I've updated recovery binaries and added a changelog.
Please report the issues you find.
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
Will it work with Pixel Experience?
EdwardTCM said:
Will it work with Pixel Experience?
Click to expand...
Click to collapse
I didn't try. Install instructions are the same for all GSI roms. You can get a big list of GSIs in https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Some roms are bigger than stock, so you'll need to delete/wipe your product partition first. OP has instructions about it. I personally prefeer to flash an empty product.img instead of deleting the logical partition, to avoid TWRP warnings trying (and failing) to mount the partition.
paziusss said:
I didn't try. Install instructions are the same for all GSI roms. You can get a big list of GSIs in https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Some roms are bigger than stock, so you'll need to delete/wipe your product partition first. OP has instructions about it. I personally prefeer to flash an empty product.img instead of deleting the logical partition, to avoid TWRP warnings trying (and failing) to mount the partition.
Click to expand...
Click to collapse
Alright Thanks
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
I flashed phhusson's GSI rom but my galaxy tab a7 keeps boot looping
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
I'm trying to flash the ROM I downloaded but I keep getting Sparse errors and when it finishes I get this FAILED (remote: Operation not permitted)
Edit: Maybe this is happening because of the ROM being A only
EdwardTCM said:
I flashed phhusson's GSI rom but my galaxy tab a7 keeps boot looping
Click to expand...
Click to collapse
You need one of the ARM64 AB variants. No matter if it is vanilla, floss or gapps.
thank you for twrp and fastboot but i noticed that most gsi images are bugy no brightness or randemly rebooting
paziusss said:
You need one of the ARM64 AB variants. No matter if it is vanilla, floss or gapps.
Click to expand...
Click to collapse
OOOH I thought it was A Only
EdwardTCM said:
I'm trying to flash the ROM I downloaded but I keep getting Sparse errors and when it finishes I get this FAILED (remote: Operation not permitted)
Click to expand...
Click to collapse
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
To anyone who wants to try the Pixel Experience rom
USE A/B NOT A ONLY
EdwardTCM said:
To anyone who wants to try the Pixel Experience rom
USE A/B NOT A ONLY
Click to expand...
Click to collapse
Btw the wifi doesn't work
One Issue when downgrading to TWRP 3.5 is that it will boot loop
{
"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
AttentionFor 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