Related
sorry for my bad english,i am chinese
items needed:
blu_spark twrp(people says it is better than official twrp.less bug,somehow i cant fully restore a backup in official twrp,get bootloop or error 255,i have not try to use this twrp to do a full restore yet,maybe official twrp will work for you)
i am using
twrp-3.2.3-x_blu_spark_v9.85_op6.img
twrp-3.2.3-x_blu_spark_v9.85_op6.zip
download link
blu_spark twrp:
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
unbrick tool:
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
los
from lineage-15.1-20180819_185755-UNOFFICIAL-enchilada.zip
to lineage-16.0-20180913_083011-UNOFFICIAL-enchilada.zip
https://forum.xda-developers.com/oneplus-6/development/rom-lineageos-16-0-t3839750
step:
0 already in a working los 15.1 rom
1 remove screen lock(maybe not necessary)
2 backup data partition in twrp(dont need other partion unless you will go back to los 15.1),then copy to a computer,you need to copy other files manualy to a computer for example: photos
3 use unbrick tool to install oneplus rom (nothing bad will happen using this,this way is cleaner,the real reason i use it is because when i installed open beta 3,some serious bug happened,i cant boot into official twrp,i get qualcomm crashdump mode instead and i get device is currupted where it should say bootloader is unlocked),maybe you can skip step 3 and 4 if you are lucky
4 oem unlock
5 download open beta 2 rom to your computer
6 fastboot boot twrp.img
7 wipe then install open beta 2 rom+twrp(twrp says no OS installed when chose reboot ,but it is fine)
8 i booted into open beta 2 rom just to make sure it works,maybe not necessary
9 reboot into twrp ,wipe then install los 16.0+twrp
10 reboot into twrp (twrp says no OS installed when chose reboot ,but it is fine)
11 intall opengapps+magisk
12 boot into los to make sure it works
13 reboot into twrp
14 restore data partition (dont need manually wipe before this)
15 wipe dalvik/art cache(maybe not necessary)
16 boot into system(may take 4 minutes)
i used for a few hours,works fine,no serious bug,dont need to login apps.if you have errors,plz follow this guide precisely,it works for me at least,and i tried this method twice,it works
tip:you can use adb to copy mutiple files or folder at the same time, for example
adb push "F:\oneplus twrp ubrick\lineage-16.0-20180913_083011-UNOFFICIAL-enchilada.zip" "F:\oneplus twrp ubrick\open_gapps-arm64-9.0-nano-20180915.zip" "F:\oneplus twrp ubrick\twrp ob3\twrp-3.2.3-x_blu_spark_v9.85_op6.zip" "F:\oneplus twrp ubrick\Magisk-v17.1.zip" /sdcard/
adb push "F:\oneplus twrp ubrick\TWRP" /sdcard/
bugs i discovered,these bug exist even using normal clean install method(dont keep app data ),this restore method is fine
using opengapps nano or stock
dont have adaptive battery and adaptive brightness(the google AI version),cant copy text in recent view,but have digital wellbeing
privacy guard not working,force close,other appops apps like appopsx not working
Thank you for posting this guide. I have a couple edits/notes.
After you use the unbrick tool, you'll need to use the version of TWRP here, and not the blu-spark version: https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Once OB2 is installed, you need the blu-spark version.
Step 7 needs to be repeated. OB2 must be installed twice to cover both A and B slots.
I had trouble finding the Qualcomm drivers, but eventually found something that didn't seem to be bundled with some other software and *also* worked on 64-bit Windows. Some of the links out there are designed for Windows Vista.
0xScott said:
Thank you for posting this guide. I have a couple edits/notes.
After you use the unbrick tool, you'll need to use the version of TWRP here, and not the blu-spark version: https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Once OB2 is installed, you need the blu-spark version.
Step 7 needs to be repeated. OB2 must be installed twice to cover both A and B slots.
I had trouble finding the Qualcomm drivers, but eventually found something that didn't seem to be bundled with some other software and *also* worked on 64-bit Windows. Some of the links out there are designed for Windows Vista.
Click to expand...
Click to collapse
Somehow I only used one twrp,it works for me,I think when you install OnePlus rom in twrp,it has two steps,I think it automatically install in both slots
You may get some battery issus after using this install method,it will automatically fixed in a few days,it seems battery need to adjust
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?
Requirements:
- Stock Clean Firmware: https://mirrors.lolinet.com/firmware/moto/troika/official//
- TWRP: https://forum.xda-developers.com/one-vision/how-to/twrp-3-3-1-0-root-updated-kane-troika-t4102839
- GSI ROM (arm64, A/B versions): https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
- Permissiver_V5 Flashable Zip: https://androidfilehost.com/?fid=6006931924117940902
- Google Play Services APK - Whenever you boot into a GSI the first thing you should do is install the Google Play Services APK. Installing it will clear the "System Updating..." notification and you will be able to login to your Google account.
Google Play Services for Android 9 GSI: https://www.apkmirror.com/apk/googl...-24-13-100400-316577029-android-apk-download/
Google Play Services for Android 10 GSI: https://www.apkmirror.com/apk/googl...-24-13-120400-316577029-android-apk-download/
Instructions:
- Flash Stock firmware
- Wipe system and data in TWRP
- Reboot to bootloader
- Run the following command in the command line:
Code:
fastboot flash system [yourGSI.img]
- While still in fastboot mode run:
Code:
fastboot -w
- Reboot to TWRP and flash Permissiver_V5 zip file
- Reboot to the system
Notes:
Look at the size of the downloaded GSI.img file (Not the zip file), If it's larger than 3GB you won't be able to flash it because the system partition is limited to 3GB)
Permissiver_V5 is required for some GSI to successfully boot, some of GSIs might work without it but if you don't flash it and the GSI doesn't boot that might be the main problem.
GSI ROMs might have some bugs, the most known bug at least on One Vision and maybe Action is the Bluetooth Freeze Bug that might happen when you try to play music over Bluetooth. Be prepared for anything.
Not every GSI will successfully boot. Some of them might not boot but don't worry as there are a lot of GSIs for you to try on.
Same procedure works for both One Action and One Vision
FAQ:
Do I need to flash GAPPS after I install an GSI?
No. Flashing GAPPS is an optional step, most of the GSIs might already come with GAPPS installed and all you have to do to enjoy your ROM is to install the Google Play Services apk mentioned in my post.
You must install GAPPS if the GSI you're using doesn't have the Google Play Store app and you want to install any apps from the Play Store, but even then there are alternatives to install Play Store apps even without installing any GAPPS package
After installing a GSI my phone it's stuck in a bootloop, what do I do?
The main reason for your android not booting up is that some vendors enforce SELinux which stops GSIs from booting and the fix for that is by flashing the Permissiver_V5 zip file to be able to boot into GSI.
But if you can't boot even after you flashed Permissiver_V5, you either downloaded the wrong GSI or the GSI isn't compatible with your device so you have to find another GSI to flash. Remember that not every GSI can successfully boot.
The X GSI has the Y problem! How do I fix it?
Even after your GSI finished booting there's no guarantee that everything will work as it should. The best thing you can do is to find support on google, or if the creator of the GSI has provided any contact links (Email, Telegram, etc) you can contact him and ask him if there's a fix for your problem or not.
hey good write up snoop! do you know if anybody has tried making an overlay for one action/vision? all the system images that work have a few overlay related bugs for me
Overlay Fix For All Gsi roms by samkh666
Display cutout fix,nfc fix,autobrightness fix
Go my orginal post for more info
Orginal post
Trying to follow these instructions, why is it that when I try to flash permissiver_v5.zip via TWRP I get "New image larger than boot partition. Aborting..."? TWRP version is 3.6.2. GSI is LeOS 19.1.
Interestingly, I don't get this error if I flash permissiver_v5.zip before I flash the TWRP installer (that is, while in the temporary TWRP boot session, but before flashing TWRP into the boot partition). Doing it this way doesn't fix the bootloop problem though.
This thread will contain the magisk patched boot.img that i use on my oneplus 7t device running lineageos 18.1.
Ill be putting up two boot images on every new lineageos builds, the first one will be the magisk patched image, the other one will be the default bootimage (incase anyone wants to roll back).
Disclaimer:
I will not be held responsible for any bricked devices, you can follow the flashing instructions directly from topjohnwu, the patched bootimage only contains magisk.
Installation Instructions:
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
Reboot and enjoy.
The above instructions are for devices with lineageOs recovery, for other recoveries you would have to figure it out on your own. If i move to other recoveries ill update the installation instructions here.
Download links will be available below in the comments
[16/01/22] lineage-18.1-20220116 patched boot images
[09/01/22] lineage-18.1-20220109 patched boot images
[02/01/22] lineage-18.1-20220102 patched boot images
[26/12/21] lineage-18.1-20211226 patched boot images
[19/12/21] lineage-18.1-20211219 patched boot images
[12/12/21] lineage-18.1-20211212 patched boot images
[05/12/21] lineage-18.1-20211205 patched boot images
[28/11/21] lineage-18.1-20211128 patched boot images
[21/11/21] lineage-18.1-20211121 patched boot images
[14/11/21] lineage-18.1-20211114 patched boot images
[07/11/21] lineage-18.1-20211107 patched boot images
[31/10/21] lineage-18.1-20211031 patched boot images
Reserved
Thanks bro
intp.pisces said:
Thanks bro
Click to expand...
Click to collapse
You're Welcome , hope you found it useful.
Backstab319 said:
[31/10/21] lineage-18.1-20211031 patched boot images
Click to expand...
Click to collapse
I have read in the thread that magisk can be installed via adb sideload
And while updating lineage OS, we have to tick magisk to install on inactive slot before booting.
But I am confused about magisk patched boot image.
What is the method to install it?
sandeep_kumar said:
I have read in the thread that magisk can be installed via adb sideload
And while updating lineage OS, we have to tick magisk to install on inactive slot before booting.
But I am confused about magisk patched boot image.
What is the method to install it?
Click to expand...
Click to collapse
Hi, i would recommend installing the update from the native updater, that takes care of most of the things for you out of the box.
After you install the update keep the patched bootimage in a directory that's easily accessible on your pc. Then follow the below instructions (Make sure your device is connected via adb),
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
And you are done, once booted up you will see that magisk root status is back and all your previously installed magisk modules and xposed modules work as before the update.
Thanks
I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!
NoSauce said:
I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!
Click to expand...
Click to collapse
Magisk canary removed magisk hide and the list of modules. Stick with magisk v23 stable to get magisk hide and module list.
NoSauce said:
I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!
Click to expand...
Click to collapse
Hi, the boot.img is the stock boot image, if you want to get magisk 20.3 stable you will have to flash the file named something like "magisk_patched-2300". I have kept the stock boot image as just a last resort for anyone who faces any difficulty with magisk to roll back easily.
You can have the file installed before the flashing and once you are done with flashing the magisk status will be enabled. Personally i dont install the app, after flashing on the first boot you will get a prompt to place a shortcut icon of magisk on your homescreen, which is much better for magisk hide detection.
This is the stable build boot image patch, for canary you will have to patch the image yourself, as i dont use canary for stability purpose.
Backstab319 said:
Hi, the boot.img is the stock boot image, if you want to get magisk 20.3 stable you will have to flash the file named something like "magisk_patched-2300". I have kept the stock boot image as just a last resort for anyone who faces any difficulty with magisk to roll back easily.
You can have the file installed before the flashing and once you are done with flashing the magisk status will be enabled. Personally i dont install the app, after flashing on the first boot you will get a prompt to place a shortcut icon of magisk on your homescreen, which is much better for magisk hide detection.
This is the stable build boot image patch, for canary you will have to patch the image yourself, as i dont use canary for stability purpose.
Click to expand...
Click to collapse
Thank you @HueyT and @Backstab319 for your help. I was able to successfully install Magisk using the .apk version posted in the github repo (link in my original post).
@Backstab319 just to clarify, the boot.img that you include in your links, you say, are of the "stock boot image". By this, do you mean the...
1. boot.img from the OOS Firmware installed before installing LineageOS
OR
2. boot.img from the LineageOS nightly?
I assume it's 2, correct? The boot.img being patched in Magisk manager is the one from the LineageOS being installed, correct?
Thank you.
NoSauce said:
Thank you @HueyT and @Backstab319 for your help. I was able to successfully install Magisk using the .apk version posted in the github repo (link in my original post).
@Backstab319 just to clarify, the boot.img that you include in your links, you say, are of the "stock boot image". By this, do you mean the...
1. boot.img from the OOS Firmware installed before installing LineageOS
OR
2. boot.img from the LineageOS nightly?
I assume it's 2, correct? The boot.img being patched in Magisk manager is the one from the LineageOS being installed, correct?
Thank you.
Click to expand...
Click to collapse
Yes, its the boot.img extracted from each of the lineageOS nightly release.
The latest magisk 24.1 seems to break everything that it is known for except root status. Safteynet fails, zigisk and denylist do not work. External modules cannot be installed. So am gonna stay with 23.0 for now, the latest images will be uploaded in this weekend.
Backstab319 said:
The latest magisk 24.1 seems to break everything that it is known for except root status. Safteynet fails, zigisk and denylist do not work. External modules cannot be installed. So am gonna stay with 23.0 for now, the latest images will be uploaded in this weekend.
Click to expand...
Click to collapse
Yes. Better to switch to Magisk 24.1 after everything gets fixed. For now V23 has no issues.
flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated
Backstab319 said:
This thread will contain the magisk patched boot.img that i use on my oneplus 7t device running lineageos 18.1.
Ill be putting up two boot images on every new lineageos builds, the first one will be the magisk patched image, the other one will be the default bootimage (incase anyone wants to roll back).
Disclaimer:
I will not be held responsible for any bricked devices, you can follow the flashing instructions directly from topjohnwu, the patched bootimage only contains magisk.
Installation Instructions:
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
Reboot and enjoy.
The above instructions are for devices with lineageOs recovery, for other recoveries you would have to figure it out on your own. If i move to other recoveries ill update the installation instructions here.
Download links will be available below in the comments
Click to expand...
Click to collapse
flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated
barcia99 said:
flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated
Click to expand...
Click to collapse
Yeah, the command is correct.
Which magisk version are you having the issue with?
I had similar issue with magisk 24.1 so i rolled back to 23.
Backstab319 said:
Yeah, the command is correct.
Which magisk version are you having the issue with?
I had similar issue with magisk 24.1 so i rolled back to 23.
Click to expand...
Click to collapse
first tried 24 but had problem so now on the 23 rollback and it's been going for 15 minutes. should i have flashed magisk first then lineage? also one question where it say's "And reboot the device by "fastboot reboot" do i just hit reboot into system from fastboot mode?
barcia99 said:
first tried 24 but had problem so now on the 23 rollback and it's been going for 15 minutes. should i have flashed magisk first then lineage? also one question where it say's "And reboot the device by "fastboot reboot" do i just hit reboot into system from fastboot mode?
Click to expand...
Click to collapse
Oh, i had the same scenario. Tried installing 24.1 didn't work, tried rolling back to 23. But sadly rolling back from 24 to 23 caused bootloop for me as well. I ended up flashing the rom again (fresh) and then it started working.
{
"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)