Related
JUST FOR FUN...no more no less...
Proud to present my first compiled build of crDROID 8.1.0 :cyclops:
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. We're mainly based on LineageOS so use custom kernels compatible with them!
Features:
Click for feature list : https://github.com/crdroidandroid/crdroid_features/blob/8.1/README.mkdn
Always take a proper backup of your running device !
Upgrading from earlier version of crDroid: The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
Installation:
0. unlocked, suited twrp, oreo bootstack of your choice...you know the drill
1. Copy crDroid zip, 8.1.0 gapps zip and Combifix v3.1 to your device
2. Boot into twrp recovery
3. Wipe cache, system, & data (or just cache & system for a dirty flash) or wipe including vendor (treble, format data)
4. Flash ROM
5. Flash gapps
5a Reboot and setup phone
6. Flash Magisk 18.0 and MagiskHidePropsConfig in 1 take with CombiFix3.1 to pass SafetyNet
7. Reboot and enjoy !
Build : A2017X crDROID 8.1.0
GAPPS: https://opengapps.org/
Magisk : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
KERNEL SOURCE: https://github.com/LineageOS/android_kernel_zte_msm8996
XDAevDB Information : crDroid 8.1.0, ROM for Axon7
Contributors
@raystef66
Credits to :
@kevte89!
@SaintZ93
@king1990
Source Code: https://github.com/crdroidandroid
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.18.x
ROM Firmware Required: Unlocked Bootloader, Latest TWRP Recovery
Based On: LineageOS device, vendor, kernel
Version Information : 8.1.0 v4.7.2
Status: Pure & Stable
Sec, Patches : 2018-12-05
Created : 2019.01.26
Last Updated : 2019.01.26
reserved
Thanks!
Thanks, Downloading in progress (;
New rom,still no working dolby atmos
Good work
Predatorhaze said:
New rom,still no working dolby atmos
Click to expand...
Click to collapse
Mi-mi-mi-mi
tron1 said:
Mi-mi-mi-mi
Click to expand...
Click to collapse
mi mi mi it is.No one will use this.
Axon 7 without dolby is mi mi
Predatorhaze said:
mi mi mi it is.No one will use this.
Axon 7 without dolby is mi mi
Click to expand...
Click to collapse
This is a new creation just for you. It's a pronounced slow and quiet mi.
Predatorhaze said:
mi mi mi it is.No one will use this.
Axon 7 without dolby is mi mi
Click to expand...
Click to collapse
Boo hoo, complain complain. Thats all you ever do. Dont be ruining roms and kernels with your negativity... Why dont you learn to dev and fix dolby yourself. Prove us wrong.
Predatorhaze said:
New rom,still no working dolby atmos
Click to expand...
Click to collapse
This is not a discussion thread to solve her Dolby problem. It's about Raystef66 of his crdroid Rome, build Dolby yourself or wait for the time to come...
is this supported by OMS??
Really great work. Thanks so much for this.
Just one question...
Is the fix you posted for passing Safety Net still working?
Flashed both via the Aroma installer and just passed the basic integrity.
Druboo666 said:
is this supported by OMS??
Click to expand...
Click to collapse
Tested like Substratum - pitch black theme f.e. and it's working nicely
[armitage] said:
Really great work. Thanks so much for this.
Just one question...
Is the fix you posted for passing Safety Net still working.
Flashed both via the Aroma installer and just passed the basic integrity.
Click to expand...
Click to collapse
Thnx !
It should and I tested it on this rom too with success.
Use the combifix v3.1 after you have succesfully flashed ROM zip+gapps. Reboot into twrp and run the combifix and flash Magisk 18.0 AND the safetynet fix in one take. Reboot and done
Basically did that except for the reboot after flashing rom zip and gapps.
I know that I could uninstall magisk to flash it again, but should I now uninstall the Safety Net fix as well and just flash it again?
Would that do any good?
[armitage] said:
Basically did that except for the reboot after flashing rom zip and gapps.
I know that I could uninstall magisk to flash it again, but should I now uninstall the Safety Net fix as well and just flash it again?
Would that do any good?
Click to expand...
Click to collapse
Yeah, you should flash rom+gapps in one take, boot into rom and reboot for Magisk18+fix.
If you see MagiskHidePropsConfig in modules, just untick and delete, reboot into twrp, mount system and vendor, run the Combifix again and just tap the Safeynet Fix and reboot.
I did it multiple times and there was no problem at all.
So try it again. If a no go uninstall Magisk, reboot into twrp, mount system and vendor, run Combi and flash magisk18 and SN fix in one take and reboot.
MagiskHide Props Config didn't work for me but module named SafetyPatch works fine.
raystef66 said:
Yeah, you should flash rom+gapps in one take, boot into rom and reboot for Magisk18+fix.
If you see MagiskHidePropsConfig in modules, just untick and delete, reboot into twrp, mount system and vendor, run the Combifix again and just tap the Safeynet Fix and reboot.
I did it multiple times and there was no problem at all.
So try it again. If a no go uninstall Magisk, reboot into twrp, mount system and vendor, run Combi and flash magisk18 and SN fix in one take and reboot.
Click to expand...
Click to collapse
Thanks so much for the help.
Went back into recovery, mounted system and vendor and flashed the fix again. before it didn't appear in modules now it does and both checks are fine.
Thanks again.
Predatorhaze said:
mi mi mi it is.No one will use this.
Axon 7 without dolby is mi mi
Click to expand...
Click to collapse
Do not be so ungrateful. The Dev will certainly do its best to fix the problem in the future. Just be glad that the Axon 7 still enjoys such a right to exist.
But btw i will test this thing.
deleted
Hello guys,
I made an update in TWRP and installed Havoc 2.4 to try it. After 1 hour I restored my backup and changed back to MIUI. I couldn't log in, so I cleaned the keyfiles to set a new pin.
I reflashed new Beta (25.4 MIUI - Xiaomi.eu) ROM and Magisk but root does not apply on my device... What is wrong? Seems that it's not possible to root anymore... Its does not give me any fails when installing the magisk 18.1 zip in TWRP...
thanks in advance
Have you tried a simple reboot? Usually it takes a reboot more to apply.
no it's not that. now its always booting into twrp when I try to flash magisk
makmak001 said:
no it's not that. now its always booting into twrp when I try to flash magisk
Click to expand...
Click to collapse
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
I fixed it by wiping data... now its working
tsongming said:
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
Click to expand...
Click to collapse
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Sent from my Xiaomi MI 8 using XDA Labs
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Here you can see that I have root and latest update
Sent from my Xiaomi MI 8 using XDA Labs
tsongming said:
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Click to expand...
Click to collapse
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
slave2007 said:
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
Click to expand...
Click to collapse
I no longer use Viper because my phone has 1 speaker and for me Ainur Sauren works pretty well for all sounds.
For listening to music I have the Pro version of Power amp which has every wanted option such as dynamic compression, dynamic EQ, convolution reverb, limiting , tag editing, visualizations etc, I bought it 5 years ago for $3. Best 3 bucks that I ever spent!
Seriously, I can't recommend Poweramp highly enough, its worth its weight in gold.
Sent from my Xiaomi MI 8 using XDA Labs
when i try to install it i get bootloop and when it installs i get a error that i need to update or reinstall and modules wont work or install but when it updates or reinstall i get a bootloop and then i get pushed into recovery, i installed magisk and patched the boot.img file same error.
what i tryed
1- flashed magisk zip from twrp
2-flashed magisk patched boot with fastboot
3-flashed magisk patched boot and wiped data it crashes some times and works sometime but with out modules and i get error i need to update.
4-flashed EU rom and did the same steps same error
i have
K20pro 10.3.3 global
tried miui eu 10.3.3
the fix
used orange fox recovery with the 19.4 magisk and it worked for me i downloaded it from https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647
1- you need a otg with a flash memory.
2-install orange fox recovery .
3-wipe data cash and devcash internal storage .
4-from the settings mount system and vendor.
5-then install the magisk 19.4 clear cash and reboot now it works fine for me.
when i first rooted global rom on Mi9t pro i flashed magisk 19.3 and it boot back to twrp then i went to advanced wipe and format data reboot and all is good did you try that.
yeah it wont run modules
shono22 said:
yeah it wont run modules
Click to expand...
Click to collapse
the reason for bootloop often is not formating data thats why i asked iff you tried that after flashing magisk.
sam00561 said:
the reason for bootloop often is not formating data thats why i asked iff you tried that after flashing magisk.
Click to expand...
Click to collapse
i get requires additional setup
your device needs additional setup for magisk to work properly.it will download magisk setup zip, do you want to proceed now?
when i press yes i get a bootloop issue
and if dont i cant run modules
when i try to install modules i get update to the latest magisk its up to date 19.3 and 7.3.2
when you get the bootloop issue after flashing the modules go into twrp and go to advanced wipe then format data i think this is possibly the issue. But backup internal storage to laptop or somewhere before doing this step.
sam00561 said:
when you get the bootloop issue after flashing the modules go into twrp and go to advanced wipe then format data i think this is possibly the issue. But backup internal storage to laptop or somewhere before doing this step.
Click to expand...
Click to collapse
it wont let me flash them in the first place like magisk is not installed on my device but i can use root the root work fine but i cant install modules
Have you tried any other version of magisk? Which version are you using and are you on the magisk manager latest version. Perhaps try magisk 19.4
sam00561 said:
Have you tried any other version of magisk? Which version are you using and are you on the magisk manager latest version. Perhaps try magisk 19.4
Click to expand...
Click to collapse
Where did you get Magisk from? Are you downloading from the official Magisk github site?
Yes
I have the same problem. I'm on 9T Pro Global on a K20 Pro Raphael. Installed TWRP and Flashed Magisk. Then wipe advanced Davisk and DATA. I installed Magisk manager but cannot install modules... I'm on latest version... It says requires additional setup but sends me to TWRP and I have to restart system all over again.
test 19.4 same issue need to update to make it work
used orange fox recovery with the 19.4 magisk and it worked for me i downloaded it from https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647
1- you need a otg with a flash memory.
2-install orange fox recovery .
3-wipe data cash and devcash internal storage .
4-from the settings mount system and vendor.
5-then install the magisk 19.4 clear cash and reboot now it works fine for me.
I'm glad you guys found a fix I was on miui global mi9t Pro and I used twrp from Marino installed magisk 19.3 that's it I was rooted and I had no issue installing modules I had about 7 of them installed. Good luck anyway orange fix supposed to be a good recovery.
sam00561 said:
I'm glad you guys found a fix I was on miui global mi9t Pro and I used twrp from Marino installed magisk 19.3 that's it I was rooted and I had no issue installing modules I had about 7 of them installed. Good luck anyway orange fix supposed to be a good recovery.
Click to expand...
Click to collapse
Is your phone k20 pro china then you just installed the global rom?'
narugan26 said:
Is your phone k20 pro china then you just installed the global rom?'
Click to expand...
Click to collapse
mine is Mi9 T pro european global rom
sam00561 said:
mine is Mi9 T pro european global rom
Click to expand...
Click to collapse
Ok sir thank you. Where did you get that twrp marino?
narugan26 said:
Ok sir thank you. Where did you get that twrp marino?
Click to expand...
Click to collapse
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
I flashed twrp recovery 3.3.1.0 raphael official. Then I went and flashed the global miui rom, so far everything is correct, then I flashed magisk 20.4 zip and it gave me error 1. I wanted to flash the uninstaller and it gave me error 1. Someone could help me to solve this.
I have the Mi 9T pro
Miui 11 global stable rom
With Android 10 Q
Unlock bootloader
Hi, I've been trying to root my phone for a while now. I tried installing twrp mauronofrio and orange fox, but when I flash the magisk zip, it enters in some kind of bootloop, but it takes me to the recovery again. I've tried uninstalling magisk, so it will make my phone work again, but then I have to install the recovery again. So, anyone knows why I can't flash magisk nor keep the recovery?
Thanks
Hey, which ROM have you tried to install it on?
can't root it!
Hi
same problem with me, i've tried for 3 days so far.
Stock EEA Rom Android 10, MIUI 11 (and tried with MIUI 10 android 9), Unlocked.
i tried:
1-Flash stock rom.
2-Flash recovery
3-Flash magisk
4-flash Disable_Dm-Verity_10.20.2019.zip
>> Bootloop.
and tried:
1-Flash stock rom.
2-Flash recovery
3-flash Disable_Dm-Verity_10.20.2019.zip
4-Flash magisk
5-flash Disable_Dm-Verity_10.20.2019.zip again.
>> Same result.
Also:
i tried:
1-Flash stock rom.
2-Flash recovery
3-Flash magisk
4-flash Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip
5- wipe Data parition.
>> Its worked! nut without Encyption!!
i tried to downgrade to Global stock rom (Android 9, MIUI 10)
same result.
Stock EEA Rom Android 10, MIUI 11
have problem with magisk 20.1 try magisk 19.4 or change to xiaomi.eu 11 it much better with call recording and mfs and u can root it with 20.1 magisk
i tried this stock rom before same issue with me
Does work with magisk 19.4?
I'm thinking of rooting my Mi 9t pro.
Neleks90 said:
Does work with magisk 19.4?
I'm thinking of rooting my Mi 9t pro.
Click to expand...
Click to collapse
I will try after few min's, will write any update!
mkaraz1994 said:
I will try after few min's, will write any update!
Click to expand...
Click to collapse
Thanks. I'm so curious whether flashing magisk 19.4 will work or not.
Neleks90 said:
Thanks. I'm so curious whether flashing magisk 19.4 will work or not.
Click to expand...
Click to collapse
I'm so sorry, but doesn't works!
i tried with Android 9, and Android 10 same result bootloop!!
so i'm going to install xiamoi.eu verisons and try!
Can you tell me how recovered from bootloop?
What did you do to make your phone workig again?
Neleks90 said:
Can you tell me how recovered from bootloop?
What did you do to make your phone workig again?
Click to expand...
Click to collapse
when i've bootloop i uninstall magisk by its uninstall.zip, or re-flash stock rom by MiFlash tools or by Orange/TWRP recovery, almost i've tried everything in the forum to get rooted by no any way rooted it!
but Finally rooted!
with xiamoi.eu rom!
Thanks to @Antidote03
mkaraz1994 said:
when i've bootloop i uninstall magisk by its uninstall.zip, or re-flash stock rom by MiFlash tools or by Orange/TWRP recovery, almost i've tried everything in the forum to get rooted by no any way rooted it!
but Finally rooted!
with xiamoi.eu rom!
Thanks to @Antidote03
Click to expand...
Click to collapse
Great happy to hear that.
Could you please tell me which version you use now?
You only flashed xiaomi.ec rom and magisk?
Xiaomi.eu rom via twrp root with magisk =gg
Great.
Which version you have installed? Could you please tell me to know which to download.?
As far as I can see you haven't formatted your data! You need to format your data before rebooting to system!
Neleks90 said:
Great.
Which version you have installed? Could you please tell me to know which to download.?
Click to expand...
Click to collapse
latest version, i do this steps:
wipe data, cache, d-cache
flashing the rom by TWRP
reboot, setup my phone
reboot to recovery flash magisk 20.1 zip
reboot to phone and installed magisk manager!
All its done!
FallenJedi said:
As far as I can see you haven't formatted your data! You need to format your data before rebooting to system!
Click to expand...
Click to collapse
if you re-read my post will see the another, after i foramt the data its will work yeah, but without encryption!
so did you've rooted K20 pro/Mi 9T pro with stock rom by magisk and its done with encryption?
I installed lineage os 18.1 on my redmi 8, whenever I try to boot into the system it redirects me to twrp. What do I do?
ArthurNobody said:
I installed lineage os 18.1 on my redmi 8, whenever I try to boot into the system it redirects me to twrp. What do I do?
Click to expand...
Click to collapse
which los did you install? usually when it redirects to twrp something was skipped. did you format data? was the flashing successful?
fonzacus said:
which los did you install? usually when it redirects to twrp something was skipped. did you format data? was the flashing successful?
Click to expand...
Click to collapse
I have the same problem, i did format data and the flash was successful, also internal storage has just a bunch of folders with corrupted names after the flashing
aale01 said:
I have the same problem, i did format data and the flash was successful, also internal storage has just a bunch of folders with corrupted names after the flashing
Click to expand...
Click to collapse
id suggest not installing any a9 or a10 roms (aside from miui mods) as their trees are unstable, a11 has good support most of the time. los a11 was also very buggy from the start
[ROM][11.0][UNOFFICIAL][LineageOS 18.1] for Redmi 8(olive)
would like to share my device tree from scratch from 0 to hero for redmi 8 olive i left developing that phone for a while 2day sharing my device tree for lineage 18.1 along with the rom . rom based on latest miui vendor prebuilt Your warranty...
forum.xda-developers.com
there are plenty more stable alternatives now
encrypted (random names) are usually due to an unsupported
recovery on a12. in a normal boot they should work just fine
Xiaomi protect their device from custom rom or custom recovery and some time device go to hardbrick and stock on fastboot mode
So every time you want to install a custom rom after successful to install(dirty flash better) the rom first go beck to twrp menu and format system and dalvik cache then go to install>install image>select twrp img file>install
Then go to reboot>reboot to recovery
Then reboot to system
Hi,
I got the same problem with my samsung S9.
lineage allready worked fine. But then i decided to install the gapps and therefore i had to swipe the rom (according to a video). Whatever. So afterall i had nothing on the phone and had to install lineage again.
The first time then in odin i forgot to click away the check at "automatic recovery". I don´t know if that was my mistake.
Anyway, i repeated Odin, twrp and the installing of lineage. And allways when i reboot it after installing, lineage shows its surface and i can type in my pin. 1 or two seconds. And then a window "reboot into fabrique settings" appears and its rebooting back into twrp again.
What could that be?