Related
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.
*
*/
Introduction
This thread is dedicated to newbies and rooting, so if you're familiar with the whole procedure, you're done
Just ask questions about every step and you'll receive help!
Downloads
TWRP Installer ZIP and TWRP IMG for Android 9/10: https://forum.xda-developers.com/oneplus-7/development/recovery-unofficial-twrp-recovery-t3932943
TWRP for Android 11(including instructions, thank's to @Nebrassy ): https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
TWRP Installer ZIP = For example twrp-3.4.0-10-guacamole-unified-installer-mauronofrio.zip
TWRP IMG = For example twrp-3.4.0-10--guacamole-unified-Q-mauronofrio.img
Check for Pie or Q TWRP IMG! If you have Android Pie, choose Pie TWRP IMG, if you have Android Q, choose Q TWRP IMG.
The TWRP Installer ZIP works on Android Pie(9)/Q(10)
Magisk ZIP: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hints
If you need to update TWRP or Magisk, always keep older versions of both in hand(Magisk canary or beta may have issues)
Remove your lockscreen protection which also removes encryption to prebvent mounting issues within TWRP
Before proceeding
Your Windows PC should already recognized your device with the USB cable
Use an USB cable provided with the phone
Make sure your Windows Explorer is set up to have file extensions enabled to avoid file name issues
This process will FORMAT/WIPE/DELETE your internal storage and every file of your phone, so please back it off your device at first!
Also keep a boot.img from your current system in place if anything went wrong so you can flash it via fastboot, see "Rooting without TWRP" for how to get it.
Rooting with TWRP (Android 9/10)
Steps for unlocked bootloader with TWRP AND Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP installer ZIP" and "Magisk ZIP" to the phones internal storage.
5. Copy the "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP installer ZIP" from your phones storage from step 4.
13. Hit "install" and navigate to the "TWRP installer ZIP" file and select it for installation(dont boot the system now!).
14. Go back and flash "Magisk ZIP" the same way as for TWRP Zip otherwise your device will not boot!
15. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP and Magisk:highfive:
Steps for unlocked bootloader with TWRP WITHOUT Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP IMG" to the phones internal storage.
5. Copy the latest "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP IMG" from your phones storage from step 4
13. Navigate to advanced menu within TWRP, click on "Install Recovery Ramdisk" and select the "TWRP IMG". This will patch the boot image which does Magisk otherwise.
14. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP:highfive:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting without TWRP (Android 9/10/11)
Also useful to get stock recovery and kernel --> Recovery is within boot.img on A/B devices like OP7
Refer here for unlocking the bootloader.
1. Download the payload dumper tool to your PC from here and extract it
2. Download the FULL OxygenOS Rom zip(The version your phone is running) and extract the payload.bin
3. Put payload.bin to "payload_input" folder o the extracted tool
4. Run payload_dumper.exe from the tool's folder
5. Extracted img files are in "payload_output" folder
6. Now you have your own boot.img for your Rom
7. Copy it to your phone
8. Patch the boot.img with Magisk directly on your device: Magisk Manager App -> hit install after your Magisk version -> hit "Select and Patch a file"
9. Copy the patched boot.img (it should be in the Download folder of your device named something like "magisk_patched-22100_bjjRn.img") back to your PC
10. Reboot your device to fastboot
11. Flash the patched magisk_patched-22100_bjjRn.img
Code:
fastboot flash boot_a magisk_patched-22100_bjjRn.img
fastboot flash boot_b magisk_patched-22100_bjjRn.img
12. Reboot your device. Now you have your phone rooted without the need of TWRP (Check with Magisk Manager App)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update your rooted OxygenOS (Android 9/10)Steps for UPDATE OxygenOS via OTA and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
3. Go to Android settings -> system -> system update and hit "Download & Install Now", don't reboot yet!
4. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
5. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit "install to inactive slot"
6. Reboot your device
7. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via OTA and you keep TWRP and Root:highfive:
Steps for UPDATE OxygenOS via local upgrade and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Download the full rom zip file and place it into the root folder of your storage(/storage/emulated/0)
3. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
4. Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, don't reboot yet!
5. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
6. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version ->hit "install to inactive slot"
7. Reboot your device
8. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via local upgrade and you keep TWRP and Root:highfive:
If you have any issues, just feel free to ask!
@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.
Kollachi said:
@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.
Click to expand...
Click to collapse
I made it a little bit more clear, thanks, that's an common issue across several devices and requested often enough
Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel
AxelM said:
Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel
Click to expand...
Click to collapse
There's something different after unlocking the bootloader(which is the same). Twrp and magisk installation is different due to treble.
For EFS you can backup with twrp or local terminal
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=512
Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?
Camack said:
Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?
Click to expand...
Click to collapse
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard
strongst said:
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard
Click to expand...
Click to collapse
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?
Camack said:
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?
Click to expand...
Click to collapse
You need to do all steps. I recommend to flash the custom kernel when you've sucessfully booted the device at first.
Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well
murti52 said:
Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well
Click to expand...
Click to collapse
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
strongst said:
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.
murti52 said:
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.
Click to expand...
Click to collapse
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.
strongst said:
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.
Click to expand...
Click to collapse
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.
murti52 said:
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.
Click to expand...
Click to collapse
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
strongst said:
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
Click to expand...
Click to collapse
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?
murti52 said:
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?
Click to expand...
Click to collapse
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.
strongst said:
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.
Click to expand...
Click to collapse
Then there must be some issue with my flashing sequence. Btw, The service centre repaired the issue and i have rooted it and using bluespark with stock rom. I'll give the zip another try later on when a new update comes. Thanks for the help
I believe the default file system is ext4, is there any benefits changing it to f2fs?
Jacckz said:
I believe the default file system is ext4, is there any benefits changing it to f2fs?
Click to expand...
Click to collapse
A good and quick overview and comparison with oneplus 7 pro https://sparrowsnews.com/2019/08/13/difference-between-f2fs-and-ext4-file-system/
I'm trying to install the OpenGapps package for LineageOS 16 on my new Oneplus 7 Pro, but have a problem installing it.
First I tried the "open_gapps-arm64-9.0-micro-20190827.zip" package, but it told me its the wrong platform. Is it not arm64?
Second I tried to install the "open_gapps-arm-9.0-micro-20190827.zip", but gives me an error 70, saying I do not have enough space.
Maybe someone have a solution for this?
Thanks
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
oryanh said:
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Click to expand...
Click to collapse
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
cbadk said:
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
Click to expand...
Click to collapse
Format data in twrp then try boot again should work
liam_davenport said:
Format data in twrp then try boot again should work
Click to expand...
Click to collapse
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
cbadk said:
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
Click to expand...
Click to collapse
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
liam_davenport said:
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
Click to expand...
Click to collapse
Have not wiped the System and Vendor partition after I installed Lineage... It boots just fine... just not if I install Open GApps....
Tried MindTheGapps latest version, but still no luck.
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
cbadk said:
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
Click to expand...
Click to collapse
I am facing the same A/B slot problem with my Moto Z2.
After setp 5), did you let the lineage OS fist then reboot into recovery, or did you go straight to the lineage recovery?
Thank you so much for this. I finally fot it sorted. I did find that sometimes you have to ubplug the USB cable and plug it in again to be recognised, but I got it going. Goodby Google!!!!
I am using Gentoo Linux with adb to do this.
What is GSI?
GSI stands for Generic System Image and will allow you to install an alternative ROM on your Galaxy A20?
No longer will we be restricted to the Samsung ROM.
These ones worked for me. If they don't work for you, go to the list of all GSIs. There are plenty to choose from. Select arm64 ab files.
Q GSIs
1. AOSP 10
https://github.com/phhusson/treble_experimentations/releases
2. Pixel Experience, EvolutionX & Havoc
https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
3. Crdroid
https://sourceforge.net/projects/amber-gsi/files/crDroid v6.1/crDroidAndroid-10.0-20200104--v6.1-arm64-ab-vanilla.img.xz/download
Custom Android 10 boot screens
https://forum.xda-developers.com/galaxy-a20/themes/a20-custom-splash-screen-android-10-gsi-t4019693
List of all GSIs
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
physwizz collection
A collection of guides, kernels and ROMs. Guides Complete Guide to the A20 GSIs for the A20 Quick Root and TWRP for the A20 Making my First Kernel for the A20 A20 Rooting Guide Making Your Own ROM Making Your Own Version of QwizzROM-a20...
forum.xda-developers.com
Before you Start
1. Make sure your phone is rooted
For A20: https://forum.xda-developers.com/galaxy-a20/how-to/root-samsung-galaxy-a20-rooting-guide-t3954872
For A30: https://forum.xda-developers.com/galaxy-a30/how-to/root-galaxy-a30-magisk-canary-relaese-t3936481
2. Install TWRP and remove data encryption.
For A20: https://forum.xda-developers.com/ga...p-samsung-galaxy-a20-custom-recovery-t3955271
For A30: https://forum.xda-developers.com/galaxy-a30/development/recovery-twrp-galaxy-a30-t3968085
Quick root and TWRP together for the A20: https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
3. Backup only 3 parts: boot, data & system (not system image) onto external SD or usb-otg. If something goes wrong you should be able to restore the phone using TWRP.
4. Also use SMS Backup and Restore so you don't lose your messages or calls.
5. Make sure your Ext SD card is Fat32. I've noticed that GSIs don't recognise ExFat.
Android 10 (Q)
1. Installation
1. Begin with stock ROM
2. Reboot into TWRP ( then mount product - system - vendor)
Back boot data and system
3. Wipe both caches, data & system
4. Install GSI
5. Flash Magisk and physwizz GSI kernel from here https://forum.xda-developers.com/t/kernel-physwizz-kernel-for-the-galaxy-a20.4180107/
6. Reboot.
2. Installing GApps
Some GSIs come with GApps. If you're doesn't and you want to have GApps, then use this method.
a.-Resize system partition so you can install OpenGAPPS, go to wipe, advanced wipe, select system, select repair or change file system and select resize file system. If you get error 1 unmount and mount the system partition and try again
b. Install GApps
3. Fixing Navbar
As soon as you boot up. Run Magisk and install this module.
View attachment navbar-enabler.zip
4. Android 10 Backup
Backup Data only (EvolutionX and Havoc 3.0 will do boot/data/system backup and restore),
5. Android 10 Restore
1. Reinstall GSI (a - h above)
2. Restore Data
3. Install GApps (if needed)
Reboot
To Access larger SD cards
Unzip the file below
Use TWRP file manager to copy this file to
/system/system/bin
Tap on to file
Press chmod755
Reboot system
Android 11 (R)
wIP
Some interesting links.
https://forum.xda-developers.com/showpost.php?p=80177833&postcount=199
phhusson treble releases
https://github.com/phhusson/treble_experimentations/releases
GSIs for A50
https://forum.xda-developers.com/galaxy-a50/how-to/guide-guide-how-to-flash-gsi-t3934005/page1
AOSP GSIs
https://source.android.com/setup/build/gsi
GSI for the A70
https://forum.xda-developers.com/galaxy-a70/how-to/gsi-testing-thread-t3956230
List of all GSIs
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Project Treble
https://forum.xda-developers.com/project-treble
Lolinet mirror
https://mirrors.lolinet.com/firmware/gsi/
Only this one for install? I Will Search another gsi
alexHdz said:
Only this one for install? I Will Search another gsi
Click to expand...
Click to collapse
It looks like this one comes with GApps and su built in.
physwizz said:
It looks like this one comes with GApps and su built in.
Click to expand...
Click to collapse
WiFi not working I guess
alexHdz said:
WiFi not working I guess
Click to expand...
Click to collapse
I thought that problem was only for Android 10
I tried to install GSI today but it didn't work.
Had to do a factory reset.
physwizz said:
Possible Installation Instructions (they will become more precise as more information becomes available)
1. Make sure your A20 is rooted (https://forum.xda-developers.com/showpost.php?p=80021195&postcount=4)
2. Backup with Titanium Backup
3. Install TWRP
https://forum.xda-developers.com/showpost.php?p=80028118&postcount=2
4. Backup system onto external SD or usb-otg (exclude data)
5. Install GSI from TWRP.
a. Download the desired GSI (it MUST be A/B_arm64 Variant)
-One GSI can be found here (https://forum.xda-developers.com/showpost.php?p=80177833&postcount=199)
b. unpack it if it wasn't in .IMG format
c. Go to TWRP , Install , Install IMAGE
d. Pick your GSI and select SYSTEM IMAGE
e. Reboot to TWRP Recovery
f. Flash "GSI_Fix_boot.zip"
View attachment 4815497
If you can't get TWRP you may need to install via Odin.
I'm not sure of any of this at the moment.
Click to expand...
Click to collapse
Hi guys! I try to install android 10 gsi, however when I go into twrp mode not recognizing the rom img what can it be?
I rooted and twrp A205G
physwizz said:
Possible Installation Instructions (they will become more precise as more information becomes available)
1. Make sure your A20 is rooted (https://forum.xda-developers.com/showpost.php?p=80021195&postcount=4)
2. Backup with Titanium Backup
3. Install TWRP
https://forum.xda-developers.com/showpost.php?p=80028118&postcount=2
4. Backup system onto external SD or usb-otg (exclude data)
5. Install GSI from TWRP.
a. Download the desired GSI (it MUST be A/B_arm64 Variant)
-One GSI can be found here (https://forum.xda-developers.com/showpost.php?p=80177833&postcount=199)
b. unpack it if it wasn't in .IMG format
c. Go to TWRP , Install , Install IMAGE
d. Pick your GSI and select SYSTEM IMAGE
e. Reboot to TWRP Recovery
f. Flash "GSI_Fix_boot.zip"
View attachment 4815497
If you can't get TWRP you may need to install via Odin.
I'm not sure of any of this at the moment.
Click to expand...
Click to collapse
i tried install any GSI on my A205F , but it's keeps bootloop , any suggestions to fix ?
hwp_2804 said:
i tried install any GSI on my A205F , but it's keeps bootloop , any suggestions to fix ?
Click to expand...
Click to collapse
I have the same problem on 205yn.
which method did you use to install twrp. there are some 205f users having trouble installing twrp
physwizz said:
I have the same problem on 205yn.
which method did you use to install twrp. there are some 205f users having trouble installing twrp
Click to expand...
Click to collapse
i use methods 1 and 2 , both also the same
twrp is working , but my internal storage seems like corrupted .
hwp_2804 said:
i use methods 1 and 2 , both also the same
twrp is working , but my internal storage seems like corrupted .
Click to expand...
Click to collapse
So method 1 have you the same result as method 2
Can you backup with either method?
Method 1
For the SM-A205YN
Download the A205YN custom recovery from here
https://forum.xda-developers.com/sho...&postcount=169
No need to patch it. Just flash it with Flashify.
If this first method works for a different version, please let me know.
Method 2
For the SM-A205G,
Download the composite recovery from here.
https://forum.xda-developers.com/sho...&postcount=198
Install to ap slot using Odin.
I haven't tested this yet so be wary. I'm going to try it today.
Format data (this is NOT the same as Wipe data) (In TWRP: Wipe -> Format Data)
Reboot back into recovery
Install GSI from TWRP. : Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
Flash "GSI_Fix_boot.zip"View attachment GSI_Fix_boot.zip
Flash this zipView attachment Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Reboot
That didn't work.
Reinstalling now ?
physwizz said:
I haven't tested this yet so be wary. I'm going to try it today.
Format data (this is NOT the same as Wipe data) (In TWRP: Wipe -> Format Data)
Reboot back into recovery
Install GSI from TWRP. : Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
Flash "GSI_Fix_boot.zip"View attachment 4815771
Flash this zipView attachment 4815767
Reboot
That didn't work.
Reinstalling now
Click to expand...
Click to collapse
Try this:
Links donwload:
ROM: Android 10 GSI Treble (A-Only):
https:// enrt.eu/ FpMD
FixZygote V2 and Permissiver v5
https://androidfilehost.com/?w=files&flid=279429
Instalation:
1- Into TWRP mode
2- Wipe/ advanced wipe/ system. data and cache
3-Install/ select internal storage/ search rom image and install
4-Install/ FixZygote and Permissiver v5
5-reboot
PS: I haven't tested it yet on A205G as my twrp doesn't recognize any img rom!
Theus01 said:
Try this:
Links donwload:
ROM: Android 10 GSI Treble (A-Only):
https:// enrt.eu/ FpMD
FixZygote V2 and Permissiver v5
https://androidfilehost.com/?w=files&flid=279429
Instalation:
1- Into TWRP mode
2- Wipe/ advanced wipe/ system. data and cache
3-Install/ select internal storage/ search rom image and install
4-Install/ FixZygote and Permissiver v5
5-reboot
PS: I haven't tested it yet on A205G as my twrp doesn't recognize any img rom!
Click to expand...
Click to collapse
How did you install your TWRP?
physwizz said:
How did you install your TWRP?
Click to expand...
Click to collapse
I rooted for magisk and twrp used method 2 of the post!
Theus01 said:
I rooted for magisk and twrp used method 2 of the post!
Click to expand...
Click to collapse
I just changed method 2
physwizz said:
I just changed method 2
Click to expand...
Click to collapse
I did the twrp process again by the new method 2 but still the same error, the internal storage is having problems it does not appear the folders or files! and to install a GSI rom it must be the internal memory because the SD card does not work!
Theus01 said:
I did the twrp process again by the new method 2 but still the same error, the internal storage is having problems it does not appear the folders or files! and to install a GSI rom it must be the internal memory because the SD card does not work!
Click to expand...
Click to collapse
did you go to mount and mount everything
Hi, I am new to custom ROM's and Rooting my device. And i hope you can help me with my Problem. I have a OnePlus A6003
What i tried so far:
Before i tried installing CustomROM's my device was on OOS 10.3.0
Then i needed to use the "twrp-3.3.1-16-enchilada-Q-mauronofrio.img" to get into TWRP
in TWRP i followed the Instructions from the LinageOS site:
Now tap Wipe.
Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
Return to the previous menu and tap Advanced Wipe, then select the System partition and then Swipe to Wipe.
Sideload the LineageOS .zip package:
On the device, select “Advanced”, “ADB Sideload”, then swipe to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip
(Optionally): If you want to install any additional add-ons, run adb reboot sideload, then adb sideload filename.zip those packages in sequence.
info_outline
Note: If you want Google Apps on your device, you must follow this step before booting into LineageOS for the first time!
(Optional): Root your device by installing LineageOS’ AddonSU, (use the arm64 package) or by using any other method you prefer.
Once you have installed everything successfully, run ‘adb reboot’.
Click to expand...
Click to collapse
I was sure this wasn't the right way cause after i rebooted the device i couldn't get to LinageOS.
After that i could get the "twrp-installer-3.3.1-2-enchilada.zip" (The official version from the TWRP site to work)
Flashed LinageOS the proper way (that's what i thought, lol) through install in TWRP
after that i had the same problem i could boot one time into LinageOS and that was it.
Current State of the Phone:
Bootloader unlocked (check)
Recovery Mode starts LinageOS Recovery
Fastboot is working fine
TWRP is not installed
What i am basically trying to do is:
Install a Privacy Focused ROM (open for Suggestions but i think LinageOS is good)
Root with Magisk
Flash NanoDroid Packages
Flash AFWall+
Flash AdAway
Some questions that i have
Do i need the customized TWRP because my phone did originally run OOS 10.3.0?
Whats the proper way to install a ROM on this device and Root it afterwards with Magisk?
{
"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/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (Download from here)
(OPTIONAL)GApps (Download from here)
First time installation:
Make sure you are running Android 13 firmware
Flash vendor_boot.img and boot.img to install crDroid recovery using fastboot
Reboot to recovery
Press "Apply update"
Press "Apply from ADB"
Use
Code:
adb sideload
on your PC to flash the crDroid zip
Update installation:
Can be done via OTA using the built in updater in Settings
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/LineageOS/android_kernel_google_redbull
Download:
ROM https://crdroid.net/redfin
Changelog: https://crdroid.net/redfin/9#changelog
Known issues:
You tell me
Visit official website @ crDroid.net
Support chat on Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Please note that this ROM is 64 bit only!
Like the Pixel 7 you cannot install legacy 32 bit applications. For most people this is fine, and brings several benefits. However, if you require older 32 bit applications (like Flappy Bird) please do not install this ROM.
For more information, read this Android Developers Blog post: https://android-developers.googleblog.com/2022/10/64-bit-only-devices.html
Reserved
Thanks, I've been waiting for this version.
Hi,
I tried this ROM and had some problems installing it to make Magisk work and also the Google Apps.
The exact problems are in the body text of the spoiler.
Spoiler: My problems with the installation of the ROM
I tried this ROM on my p5 and had some trouble getting it to work with Magisk and Gapps.
Previously I was on the Evolution ROM (https://forum.xda-developers.com/t/...lution-x-7-2-unbound-tp1a-221005-002.4501629/) before I made the switch to CRDOID.
The aforementioned ROM is at the November 2022 security patch level with Android 13, and CRDROID with build date 2022-12-25 is based on the December 2022 security patch level.
The info is important because I could not boot the patched boot.img with Magisk with the November patch level. It just got stuck at the google logo.
After my phone was at the December level, I was able to flash the patched boot image with Magisk, as well as the vendor_boot image without the phone getting stuck in the google logo. Because if it's stuck in the google logo, you can't even boot into recovery to install the ROM.
And the patched boot image with Magisk is needed immediately, because without it I could flash the Mind The Gapps, but after booting into the Android OS they were not findable. Only with the patched boot image were the Google Apps available in the Android OS after flashing of mind the gapps. Other Gapps variations like LiteGapps, NikGapps or BiTGApps didn't install in the first place.
To identify that Magisk was present in the boot image, I had to manually install the Magisk app and in it I could see that the boot image was patched. As well as the Google Apps.
In the next step, I was able to log into the Play Store, but then I got a persistent message that I was offline in the Play Store and could not use it.
To fix this, I booted back into recovery, did a factory reset, and after booting, the Google installation setup came up, which I did, and then I could use the Play Store.
In the next step I wanted to install Magisk modules, installed a few, like the Universal Safetynet Patch and LSPOSED via Zygisk and restarted the phone.
After restarting, the phone ran for a minute and crashed completely. This happened until I removed all Magisk modules (disabling them also crashed the phone). As soon as a magisk module is installed and activated on reboot, the phone crashes after a minute. So far I have no idea what the problem is, so I currently have no modules installed and the phone works.
What I noticed is that the app com.android.hbmsvmanager drains some battery even with the ROM. In the Evolution ROM I had accordingly provided a tutorial on how to disable the app to kill the battery guzzler.
[ROM][13][UNOFFICIAL][redfin] Evolution-X | 7.3-Vengeance |TD1A.221105.001
I am not affiliated with the official Evolution-X team. link to kernel source: https://github.com/HubertVonJass/vendor_google_redfin_13 my other repos for the device and vendor are there as well. downloads...
forum.xda-developers.com
If you still want to install the ROM on your phone after reading the Wall of Text, and you are coming from another ROM, follow these steps.
ROM Issues with this appraoch: You can't use magisk modules. If you use them the phone crashes unless you removed all of the installed modules.
Prerequisites
Spoiler
Patch the boot image from the first post with magisk. Without magisk, you can install the Google Apps, but you will not be able to see them in the Android OS and thus will not be able to use them.
If you don't want Google Apps or magisk, you can skip this step.
In short, install the Magisk App, copy the file boot.img on your phone via usb cable. In magisk click on install, select a file -> choose the boot.img. Afterwards copy the patched magisk image from your Downloads Folder to your PC.
Check your Android security patch status in the current ROM. It is necessary that you have the same patch level as the current build version of CRDROID (Build 2022-12-25 = December 2022 Security Patch).
To do this, open the Settings app. Under Phone -> Android Version -> Security Patch Level.
So when there are future ROM updates from CRDROID, make sure you patch your device to the same security level (easiest to install the Google Factory Image for the patch level) and then install the CRDROID ROM.
If you don't want to use magisk or Google Apps you can skip this step.
Backup your data from the phone (if you have root, use Swift Backup to backup all app data). The best way is to copy your data to your PC.
Backup all folders and files in the first step, but leave out the Android folder for now, as the copy process will be interrupted when copying the Android folder. Then, in the backup directory, create the Android folder and the data, media and obb folders inside it.
You should be able to copy the media and obb folders to your PC without any problems. For the data folder, I recommend skipping any folders that contain android or google as these are the problematic folders. You can then backup these folders once you have backed up the rest. For the problematic folders, I would recommend ignoring them, but if you still need them, copy them over one by one."
If you don't have a backup and want to start from scratch, you can skip this step. But you will lose all your data if you haven't backed it up to a cloud service or somewhere else, so be warned.
If the device is based on the security level like CRDROID or you don't need magisk and Google Apps, you can skip this step.
If your device is not based on the security level of the CRDROID version, you will have to update your phone to that version first.
Download the Google Stock ROM, based on the security state:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
13.0.0 (TQ1A.221205.011, Dec 2022) for CRDROID Build 2022-12-25.
Download the current adb tools for your PC OS:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Extract the downloaded Factory image zip file. Copy all the adb tools files for your OS inside the extracted folder.
Boot your phone into fastboot. Reboot your phone and then hold power + volume down while the phone reboots. Connect your phone to your PC while it is in fastboot mode.
Execute the flash-all.bat / flash-all.sh (regarding your PC OS). With this the entire phone gets updated to the needed security patch and all your data on the phone got wiped.
InstallationAfter all the prerequisites are done, we come to the ROM installation.
Spoiler
Download all the files from the first post [(if you don't already have them) vendor_boot image, Rom zip file and mind the gapps for Android 13 in arm64]. Move them all to the folder where the adb files are already located.
Move the patched magisk boot image to this folder
Reboot your phone to fastboot mode, connect your phone to your pc while it is in fastboot mode.
execute the following commands
Bash:
fastboot flash boot <magisk_boot image name> --slot all
fastboot flash vendor_boot vendor_boot.img --slot all
After both files got installed on your phone navigate the fastboot menu with the volume keys to the point recovery and click the power button to navigate into it.
In recovery mode go to "factory reset" -> "Format data/factory reset" after the click the entire phone data got wiped.
In recovery mode go to Apply Update -> "Apply from ADB"
On your PC execute the following Commands:
Bash:
adb sideload <crDroidAndroid-13.0 zip file>
After an succesfully ROM installation reboot the phone into ANDROID OS.
Go trough the First setup and skip most of the parts.
Reboot your phone again into recovery mode. You can hold the power button -> Restart -> Recovery to go into it.
In Recovery mode go to Apply Update -> "Apply from ADB"
Connect your phone to your PC and execute the command:
Bash:
adb sideload <MindTheGapps-13.0.0-arm64 zip file>
Afterwards reboot phone again into Android OS and validate that the play Store Icon is available and reboot again into recovery mode. if not install the magisk app https://github.com/topjohnwu/Magisk/releases/ and check if magisk is installed. if it is installed on your phone and the mind the gapps installation was successfull, I don't know why it didn't worked.
Inside the recovery mode go to factory reset and execute again an data Format
Afterwards restart phone again and now you should be able to execute the google install setup. Go trough all steps.
Afterwards install the magisk app and validate that it is installed and check if the play store is working.
After the Installation
Spoiler
Copy your backupped files from your PC and reinstall all the needed apps or use swift backup (when you have an swift backup backup) to restore all the needed apps.
You can try to install magisk modules and hope that your phone won't crash after you rebooted it.
Raz0Rfail said:
Hi,
I tried this ROM and had some problems installing it to make Magisk work and also the Google Apps.
The exact problems are in the body text of the spoiler.
Spoiler: My problems with the installation of the ROM
I tried this ROM on my p5 and had some trouble getting it to work with Magisk and Gapps.
Previously I was on the Evolution ROM (https://forum.xda-developers.com/t/...lution-x-7-2-unbound-tp1a-221005-002.4501629/) before I made the switch to CRDOID.
The aforementioned ROM is at the November 2022 security patch level with Android 13, and CRDROID with build date 2022-12-25 is based on the December 2022 security patch level.
The info is important because I could not boot the patched boot.img with Magisk with the November patch level. It just got stuck at the google logo.
After my phone was at the December level, I was able to flash the patched boot image with Magisk, as well as the vendor_boot image without the phone getting stuck in the google logo. Because if it's stuck in the google logo, you can't even boot into recovery to install the ROM.
And the patched boot image with Magisk is needed immediately, because without it I could flash the Mind The Gapps, but after booting into the Android OS they were not findable. Only with the patched boot image were the Google Apps available in the Android OS after flashing of mind the gapps. Other Gapps variations like LiteGapps, NikGapps or BiTGApps didn't install in the first place.
To identify that Magisk was present in the boot image, I had to manually install the Magisk app and in it I could see that the boot image was patched. As well as the Google Apps.
In the next step, I was able to log into the Play Store, but then I got a persistent message that I was offline in the Play Store and could not use it.
To fix this, I booted back into recovery, did a factory reset, and after booting, the Google installation setup came up, which I did, and then I could use the Play Store.
In the next step I wanted to install Magisk modules, installed a few, like the Universal Safetynet Patch and LSPOSED via Zygisk and restarted the phone.
After restarting, the phone ran for a minute and crashed completely. This happened until I removed all Magisk modules (disabling them also crashed the phone). As soon as a magisk module is installed and activated on reboot, the phone crashes after a minute. So far I have no idea what the problem is, so I currently have no modules installed and the phone works.
What I noticed is that the app com.android.hbmsvmanager drains some battery even with the ROM. In the Evolution ROM I had accordingly provided a tutorial on how to disable the app to kill the battery guzzler.
[ROM][13][UNOFFICIAL][redfin] Evolution-X | 7.3-Vengeance |TD1A.221105.001
I am not affiliated with the official Evolution-X team. link to kernel source: https://github.com/HubertVonJass/vendor_google_redfin_13 my other repos for the device and vendor are there as well. downloads...
forum.xda-developers.com
If you still want to install the ROM on your phone after reading the Wall of Text, and you are coming from another ROM, follow these steps.
ROM Issues with this appraoch: You can't use magisk modules. If you use them the phone crashes unless you removed all of the installed modules.
Prerequisites
Spoiler
Patch the boot image from the first post with magisk. Without magisk, you can install the Google Apps, but you will not be able to see them in the Android OS and thus will not be able to use them.
If you don't want Google Apps or magisk, you can skip this step.
In short, install the Magisk App, copy the file boot.img on your phone via usb cable. In magisk click on install, select a file -> choose the boot.img. Afterwards copy the patched magisk image from your Downloads Folder to your PC.
Check your Android security patch status in the current ROM. It is necessary that you have the same patch level as the current build version of CRDROID (Build 2022-12-25 = December 2022 Security Patch).
To do this, open the Settings app. Under Phone -> Android Version -> Security Patch Level.
So when there are future ROM updates from CRDROID, make sure you patch your device to the same security level (easiest to install the Google Factory Image for the patch level) and then install the CRDROID ROM.
If you don't want to use magisk or Google Apps you can skip this step.
Backup your data from the phone (if you have root, use Swift Backup to backup all app data). The best way is to copy your data to your PC.
Backup all folders and files in the first step, but leave out the Android folder for now, as the copy process will be interrupted when copying the Android folder. Then, in the backup directory, create the Android folder and the data, media and obb folders inside it.
You should be able to copy the media and obb folders to your PC without any problems. For the data folder, I recommend skipping any folders that contain android or google as these are the problematic folders. You can then backup these folders once you have backed up the rest. For the problematic folders, I would recommend ignoring them, but if you still need them, copy them over one by one."
If you don't have a backup and want to start from scratch, you can skip this step. But you will lose all your data if you haven't backed it up to a cloud service or somewhere else, so be warned.
If the device is based on the security level like CRDROID or you don't need magisk and Google Apps, you can skip this step.
If your device is not based on the security level of the CRDROID version, you will have to update your phone to that version first.
Download the Google Stock ROM, based on the security state:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
13.0.0 (TQ1A.221205.011, Dec 2022) for CRDROID Build 2022-12-25.
Download the current adb tools for your PC OS:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Extract the downloaded Factory image zip file. Copy all the adb tools files for your OS inside the extracted folder.
Boot your phone into fastboot. Reboot your phone and then hold power + volume down while the phone reboots. Connect your phone to your PC while it is in fastboot mode.
Execute the flash-all.bat / flash-all.sh (regarding your PC OS). With this the entire phone gets updated to the needed security patch and all your data on the phone got wiped.
InstallationAfter all the prerequisites are done, we come to the ROM installation.
Spoiler
Download all the files from the first post [(if you don't already have them) vendor_boot image, Rom zip file and mind the gapps for Android 13 in arm64]. Move them all to the folder where the adb files are already located.
Move the patched magisk boot image to this folder
Reboot your phone to fastboot mode, connect your phone to your pc while it is in fastboot mode.
execute the following commands
Bash:
fastboot flash boot <magisk_boot image name> --slot all
fastboot flash vendor_boot vendor_boot.img --slot all
After both files got installed on your phone navigate the fastboot menu with the volume keys to the point recovery and click the power button to navigate into it.
In recovery mode go to "factory reset" -> "Format data/factory reset" after the click the entire phone data got wiped.
In recovery mode go to Apply Update -> "Apply from ADB"
On your PC execute the following Commands:
Bash:
adb sideload <crDroidAndroid-13.0 zip file>
After an succesfully ROM installation reboot the phone into ANDROID OS.
Go trough the First setup and skip most of the parts.
Reboot your phone again into recovery mode. You can hold the power button -> Restart -> Recovery to go into it.
In Recovery mode go to Apply Update -> "Apply from ADB"
Connect your phone to your PC and execute the command:
Bash:
adb sideload <MindTheGapps-13.0.0-arm64 zip file>
Afterwards reboot phone again into Android OS and validate that the play Store Icon is available and reboot again into recovery mode. if not install the magisk app https://github.com/topjohnwu/Magisk/releases/ and check if magisk is installed. if it is installed on your phone and the mind the gapps installation was successfull, I don't know why it didn't worked.
Inside the recovery mode go to factory reset and execute again an data Format
Afterwards restart phone again and now you should be able to execute the google install setup. Go trough all steps.
Afterwards install the magisk app and validate that it is installed and check if the play store is working.
After the Installation
Spoiler
Copy your backupped files from your PC and reinstall all the needed apps or use swift backup (when you have an swift backup backup) to restore all the needed apps.
You can try to install magisk modules and hope that your phone won't crash after you rebooted it.
Click to expand...
Click to collapse
Thanks for the info. Was about to make a jump tonight, guess i need to postphone since this my only device.
saxmydix,This is my only Device as well. But with enough time and a good backup and you are good to go .
Raz0Rfail said:
saxmydix,This is my only Device as well. But with enough time and a good backup and you are good to go .
Click to expand...
Click to collapse
I need to use root and the modules tho. You think this related to 64 bit only ?
saxmydix said:
I need to use root and the modules tho. You think this related to 64 bit only ?
Click to expand...
Click to collapse
I think I found the reason why my phone crashed after installing Magisk modules.
I installed the "Magisk bootloop protector" module and installed it directly into the boot image. After re-flashing the patched boot image with Magisk and installing all the other modules I used before and skipping the bootloop protector module, the phone has not crashed in the last few hours.
I also installed 5 lsposed modules and so far the phone works without crashing.
I have tested it out after I wrote the long wall of text at 03:39 am.
Thanks.
Raz0Rfail said:
Hi,
I tried this ROM and had some problems installing it to make Magisk work and also the Google Apps.
The exact problems are in the body text of the spoiler.
Spoiler: My problems with the installation of the ROM
I tried this ROM on my p5 and had some trouble getting it to work with Magisk and Gapps.
Previously I was on the Evolution ROM (https://forum.xda-developers.com/t/...lution-x-7-2-unbound-tp1a-221005-002.4501629/) before I made the switch to CRDOID.
The aforementioned ROM is at the November 2022 security patch level with Android 13, and CRDROID with build date 2022-12-25 is based on the December 2022 security patch level.
The info is important because I could not boot the patched boot.img with Magisk with the November patch level. It just got stuck at the google logo.
After my phone was at the December level, I was able to flash the patched boot image with Magisk, as well as the vendor_boot image without the phone getting stuck in the google logo. Because if it's stuck in the google logo, you can't even boot into recovery to install the ROM.
And the patched boot image with Magisk is needed immediately, because without it I could flash the Mind The Gapps, but after booting into the Android OS they were not findable. Only with the patched boot image were the Google Apps available in the Android OS after flashing of mind the gapps. Other Gapps variations like LiteGapps, NikGapps or BiTGApps didn't install in the first place.
To identify that Magisk was present in the boot image, I had to manually install the Magisk app and in it I could see that the boot image was patched. As well as the Google Apps.
In the next step, I was able to log into the Play Store, but then I got a persistent message that I was offline in the Play Store and could not use it.
To fix this, I booted back into recovery, did a factory reset, and after booting, the Google installation setup came up, which I did, and then I could use the Play Store.
In the next step I wanted to install Magisk modules, installed a few, like the Universal Safetynet Patch and LSPOSED via Zygisk and restarted the phone.
After restarting, the phone ran for a minute and crashed completely. This happened until I removed all Magisk modules (disabling them also crashed the phone). As soon as a magisk module is installed and activated on reboot, the phone crashes after a minute. So far I have no idea what the problem is, so I currently have no modules installed and the phone works.
What I noticed is that the app com.android.hbmsvmanager drains some battery even with the ROM. In the Evolution ROM I had accordingly provided a tutorial on how to disable the app to kill the battery guzzler.
[ROM][13][UNOFFICIAL][redfin] Evolution-X | 7.3-Vengeance |TD1A.221105.001
I am not affiliated with the official Evolution-X team. link to kernel source: https://github.com/HubertVonJass/vendor_google_redfin_13 my other repos for the device and vendor are there as well. downloads...
forum.xda-developers.com
If you still want to install the ROM on your phone after reading the Wall of Text, and you are coming from another ROM, follow these steps.
ROM Issues with this appraoch: You can't use magisk modules. If you use them the phone crashes unless you removed all of the installed modules.
Prerequisites
Spoiler
Patch the boot image from the first post with magisk. Without magisk, you can install the Google Apps, but you will not be able to see them in the Android OS and thus will not be able to use them.
If you don't want Google Apps or magisk, you can skip this step.
In short, install the Magisk App, copy the file boot.img on your phone via usb cable. In magisk click on install, select a file -> choose the boot.img. Afterwards copy the patched magisk image from your Downloads Folder to your PC.
Check your Android security patch status in the current ROM. It is necessary that you have the same patch level as the current build version of CRDROID (Build 2022-12-25 = December 2022 Security Patch).
To do this, open the Settings app. Under Phone -> Android Version -> Security Patch Level.
So when there are future ROM updates from CRDROID, make sure you patch your device to the same security level (easiest to install the Google Factory Image for the patch level) and then install the CRDROID ROM.
If you don't want to use magisk or Google Apps you can skip this step.
Backup your data from the phone (if you have root, use Swift Backup to backup all app data). The best way is to copy your data to your PC.
Backup all folders and files in the first step, but leave out the Android folder for now, as the copy process will be interrupted when copying the Android folder. Then, in the backup directory, create the Android folder and the data, media and obb folders inside it.
You should be able to copy the media and obb folders to your PC without any problems. For the data folder, I recommend skipping any folders that contain android or google as these are the problematic folders. You can then backup these folders once you have backed up the rest. For the problematic folders, I would recommend ignoring them, but if you still need them, copy them over one by one."
If you don't have a backup and want to start from scratch, you can skip this step. But you will lose all your data if you haven't backed it up to a cloud service or somewhere else, so be warned.
If the device is based on the security level like CRDROID or you don't need magisk and Google Apps, you can skip this step.
If your device is not based on the security level of the CRDROID version, you will have to update your phone to that version first.
Download the Google Stock ROM, based on the security state:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
13.0.0 (TQ1A.221205.011, Dec 2022) for CRDROID Build 2022-12-25.
Download the current adb tools for your PC OS:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Extract the downloaded Factory image zip file. Copy all the adb tools files for your OS inside the extracted folder.
Boot your phone into fastboot. Reboot your phone and then hold power + volume down while the phone reboots. Connect your phone to your PC while it is in fastboot mode.
Execute the flash-all.bat / flash-all.sh (regarding your PC OS). With this the entire phone gets updated to the needed security patch and all your data on the phone got wiped.
InstallationAfter all the prerequisites are done, we come to the ROM installation.
Spoiler
Download all the files from the first post [(if you don't already have them) vendor_boot image, Rom zip file and mind the gapps for Android 13 in arm64]. Move them all to the folder where the adb files are already located.
Move the patched magisk boot image to this folder
Reboot your phone to fastboot mode, connect your phone to your pc while it is in fastboot mode.
execute the following commands
Bash:
fastboot flash boot <magisk_boot image name> --slot all
fastboot flash vendor_boot vendor_boot.img --slot all
After both files got installed on your phone navigate the fastboot menu with the volume keys to the point recovery and click the power button to navigate into it.
In recovery mode go to "factory reset" -> "Format data/factory reset" after the click the entire phone data got wiped.
In recovery mode go to Apply Update -> "Apply from ADB"
On your PC execute the following Commands:
Bash:
adb sideload <crDroidAndroid-13.0 zip file>
After an succesfully ROM installation reboot the phone into ANDROID OS.
Go trough the First setup and skip most of the parts.
Reboot your phone again into recovery mode. You can hold the power button -> Restart -> Recovery to go into it.
In Recovery mode go to Apply Update -> "Apply from ADB"
Connect your phone to your PC and execute the command:
Bash:
adb sideload <MindTheGapps-13.0.0-arm64 zip file>
Afterwards reboot phone again into Android OS and validate that the play Store Icon is available and reboot again into recovery mode. if not install the magisk app https://github.com/topjohnwu/Magisk/releases/ and check if magisk is installed. if it is installed on your phone and the mind the gapps installation was successfull, I don't know why it didn't worked.
Inside the recovery mode go to factory reset and execute again an data Format
Afterwards restart phone again and now you should be able to execute the google install setup. Go trough all steps.
Afterwards install the magisk app and validate that it is installed and check if the play store is working.
After the Installation
Spoiler
Copy your backupped files from your PC and reinstall all the needed apps or use swift backup (when you have an swift backup backup) to restore all the needed apps.
You can try to install magisk modules and hope that your phone won't crash after you rebooted it.
Click to expand...
Click to collapse
wow Thank you for the detail.
Now I got to know why lineage OS shows play store offline when I install it.
I may try it after a few later.
Ian getting this error every time I try to install could help me and tell what ism doing wrong I can install the boot but the vendor boot fails and side loading the rim fails ism on stable 13
hunfatal said:
Thanks.
Click to expand...
Click to collapse
And thank you for all the work on V7 and V8
mike9976 said:
Ian getting this error every time I try to install could help me and tell what ism doing wrong I can install the boot but the vendor boot fails and side loading the rim fails ism on stable 13
Click to expand...
Click to collapse
Check if the adb Version matches this version or higher:
execute in command line: adb.exe version
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
If it's lower download the latest adb tools.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Secondary check if you have adb drivers installed for google devices. If you haven't install them before you need them to install.
If you don't know if there are installed download this:
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
extract the usb_driver folder from it and on the .inf file do an rightclick and click on install. Afterwards reconnect your phone while it is in fastboot mode.
Raz0Rfail said:
Check if the adb Version matches this version or higher:
execute in command line: adb.exe version
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
If it's lower download the latest adb tools.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Secondary check if you have adb drivers installed for google devices. If you haven't install them before you need them to install.
If you don't know if there are installed download this:
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
extract the usb_driver folder from it and on the .inf file do an rightclick and click on install. Afterwards reconnect your phone while it is in fastboot mode.
Click to expand...
Click to collapse
Thx I'll try that
I'll keep an eye on it but so far I didn't managed to install both root and gapp. Still a huge thanks to @00p513 and @Raz0Rfail for providing and experience/method sharing!
Looking forward to giving this a go!
eSIM is not working for me also I can't install gapps. I installed the magisk boot.img and also magisk app, flashed the image 2 times and also factory reseted a few times. tried different combinations - not working.
OttoUsualConsumer said:
eSIM is not working for me also I can't install gapps. I installed the magisk boot.img and also magisk app, flashed the image 2 times and also factory reseted a few times. tried different combinations - not working.
Click to expand...
Click to collapse
I can't say something regarding eSIM as I don't use it.
hmm did it say in magisk app that magisk is installed not the app?
If not flash the boot partition with the magisk_patched img file.
If you did it already. I recomend an dirty flash of the Rom in the recovery. reboot the phone into Android OS. Go back to the recovery and install magisk the gapps again.
If it didn't helped, do an factory reset and do the entire Installation process again as I described.
Hello all. I am aware of the eSIM and Google Apps issues and will investigate why MindTheGapps is failing to install. As far as I can tell, the lack of eSIM is due to Google Play Services not being present, however I have been unable to get an eSIM until today.
If I install the eSIM on the previous ROM, and then enable DSDS in the phone developer menu, it sometimes works, however this is a far from perfect solution.
I will keep everyone posted in this forum and the support chat on Telegram (the pizza cafe)