Database Users

Lollipop Android 5.1.1 for HTC Desire HD

{
"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"
}
----------------------------------------------------
IMPORTANT: I AM NOT RESPONSIBLE. IF YOU BRICKED YOUR PHONE!
BASIC COMPUTER SKILLS - REQUIRED!
-------------------------------------------------------
NOTE: First boot it takes a lot of time, you just have to be patient.:fingers-crossed:
Worked- perfectly, nice & smooth!
1 . More life for battery and same work for all application and system. That's wonderful :victory:
BUGS
Not detected! If someone finds, just post on this thread, please
Kernel source:
. github.com/OpenDesireProject/android_kernel_htc_msm7x30
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
DOWNLOAD [UNOFFICIAL] Android 5.1.1 for HTC Desire HD
DOWNLOAD GAPPS 5.1.1
Installation instructions:
1. Download [UNOFFICIAL] Android 5.1.1 Cyanogenmod
2. Download gapps
3. Put the files on SD card
4. Reboot to recovery
5. Do a factory reset (wipe data/factory reset)
6. Flash cm-12.1-20150509-UNOFFICIAL-ace
7. Flash gapps zip
8. Remember to flash boot.img via fastboot if you have S-ON
9. Reboot and enjoy
----------------------------------------------------------------------------------------------------
IMPORTANT: IF YOU SEE (error 7 or 0) or something else when try to install the system!
You have to update your recovery img !!!
LINK RECOVERY IMG: TWRP-ace-2.8.1.2
INSTRUCTION TO UPGRADE YOUR recovery.img
1. USE: Ubuntu 12 or 14 - 64bit
2. Install Android SDK platform tools if you do not have it. The Ubuntu SDK is available for Ubuntu 14.04 (Trusty) onwards!
3.
HTML:
1. $ sudo add-apt-repository ppa:ubuntu-sdk-team/ppa
2. $ sudo apt-get update && sudo apt-get install ubuntu-sdk
3. $ sudo apt-get update && sudo apt-get dist-upgrade
4. Reboot to bootloader, open your terminal and navigate to the location of your boot.img and type:
5.
HTML:
fastboot flash recovery YOUR.img
-------------------------------------------------------------------
OR: sudo apt-get install android-tools-adb android-tools-fastboot
HTML:
1. adb reboot bootloader
2. fastboot devices
3. fastboot flash recovery YOUR.img
Just click on "Thanks" button if you want, it is not hard, Enjoy

Download now? Tank You good morning
Inviato dal mio Desire HD utilizzando Tapatalk

jack.ba.so said:
Download now? Tank You good morning
Inviato dal mio Desire HD utilizzando Tapatalk
Click to expand...
Click to collapse
You welcome

HI, really smooth and great Rom.
It works on my old device. Only one problem have been occured. I lost my GPS. I tested it with a GPS-Test App, but it wasn't seeing any satelits ...
Other functions like bluetooth, or WLAN or mobile-LAN working very fine.
Unfurtunal, new Android, on an old device so smooth ...
Great work!!!

Hi
So glad to hear that this old man is receiving new updates.
Would you please add a mirror link?
Thanks

Kaif_and_Kaif said:
HI, really smooth and great Rom.
It works on my old device. Only one problem have been occured. I lost my GPS. I tested it with a GPS-Test App, but it wasn't seeing any satelits ...
Other functions like bluetooth, or WLAN or mobile-LAN working very fine.
Unfurtunal, new Android, on an old device so smooth ...
Great work!!!
Click to expand...
Click to collapse
Try to install some external software, for your GPS
thx for your report

mhdprz said:
Hi
So glad to hear that this old man is receiving new updates.
Would you please add a mirror link?
Thanks
Click to expand...
Click to collapse
Hi
No need from mirror, i will upload the new version after update
tnx for your report

ROM Stability!
Is it stable enough to use???

iamSMR said:
Is it stable enough to use???
Click to expand...
Click to collapse
You should be glad, that someone cares about this old phone
By the way, the telephone worked perfectly with this os
tnx for your report.

Flashing the recovery
Hi
I wanted to flash the recovery ( cause I already have 4ext which does not seem to work) so I tried flashing via fastboot but I can't make a zip file which contains android-info.txt
Can anyone please make me one so I'll be able to flash TWRP unofficial recovery?

fix question
Can you fix.the link i cant download the file.....
And question if i install on my phone would be able to install apps that requires 4.0 up os?

nittoy said:
Can you fix.the link i cant download the file.....
Click to expand...
Click to collapse
Dunno why it isn't actually a 'link'. But just 'cut n paste' the text into your browser. Works for me.
nittoy said:
... And question if i install on my phone would be able to install apps that requires 4.0 up os?
Click to expand...
Click to collapse
Not installed yet myself but the clue is in '4.0 and up ' ......

this is what happens
this is what happens
see attachement

nittoy said:
this is what happens
see attachement
Click to expand...
Click to collapse
Well I successfully downloaded the ROM at the time I was sending my previous reply. To be fair though, I had to input the capcha text a couple of times before it downloaded. Never got an error though, it just asked for another capcha .....

dvhttn said:
Well I successfully downloaded the ROM at the time I was sending my previous reply. To be fair though, I had to input the capcha text a couple of times before it downloaded. Never got an error though, it just asked for another capcha .....
Click to expand...
Click to collapse
do you know where can i get my boot.img?

nittoy said:
do you know where can i get my boot.img?
Click to expand...
Click to collapse
Nope, sorry. Never had to use this method as I went s-off many many moons ago!

when i am flash the recovery image from fastboot it says
sending 'recovery' (7264 KB)...
OKAY [ 8.182s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 8.186s
what is the solution ?

suliman lbabidi said:
when i am flash the recovery image from fastboot it says
sending 'recovery' (7264 KB)...
OKAY [ 8.182s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 8.186s
what is the solution ?
Click to expand...
Click to collapse
And what about your S-OFF? Sorry for my bad english..

nittoy said:
this is what happens
see attachement
Click to expand...
Click to collapse
Hi just click on this
if you don't know what to do
Good explanation for download of that OS "dvhttn" & /etc
thx for your report

Hey guys!
Its been a long time since I've flashed a ROM, but I saw this and wanted to try out Lollipop ^^
I can't remember though, do you need to have a clean formatted SD Card to put the files on when you want to flash?
Thanks in advance!

BootLoop no rom no twrp no adb

Hi guys,
I have installed the Nexus ADB driver and at some point the USB port said that failed to install driver whenever i was trying to connect the phone, figured out that there was need of a driver USB3.0 named Renesas
I've managed to install TWRP 2.7 and at somepoint phone crashed and at that point i've used a script to install a root that seems deleted my TWRP , now the phone is in a boot loop.
I have no rom installed - debugging mode cannot be activated
I have no custom bootloader installed - so i cannot run a rom installer from SD card
I can sometimes run the Phone in Recovery Mode , but it's very hard to get it there by the -&power buttons
I cannot connect it to pc because adb devices brings no output.
Now MTP failed to be installed.
I want to get it connected with ADB so I can try to re-flash the phone
Please help me to do something with it , i just want to get it work, no matter what mode or what rom to be installed , a basic one to make it work .

Hi Guys,
Finally managed to connect to P8 via PC with fastboot, i can flash new system , says that it's finished but after this still the error persists , it says that error 11 : no boot
something like this. I've tried to flash the TWRP again , still not working. If i try to do fastboot erase system it says :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.005s
Any advices?
PS: The solution to connect it was to uninstall all drivers and install them back + minimal fastboot and MTP drivers from microsoft

This is what I've managed to do so far , it says successful but still not working :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.0
.2-0-grace.img
target reported max download size of 471859200 bytes
sending 'recovery' (26212 KB)...
OKAY [ 0.880s]
writing 'recovery'...
OKAY [ 0.415s]
finished. total time: 1.298s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system CM121.zip
target reported max download size of 471859200 bytes
sending 'system' (371456 KB)...
OKAY [ 12.361s]
writing 'system'...
OKAY [ 5.761s]
finished. total time: 18.126s
C:\Program Files (x86)\Minimal ADB and Fastboot>
{
"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"
}

Hello Guys,
I've managed to re-install the stock firmware after trying to flash many others ,i've been on the official website of Huawei and downloaded HUAWEI_P8 lite_Firmware_ALE-L21_Andriod 6.0_EMUI 4.0_C185B525_Middle East%26Africa_Channel-Others , with this one worked, but still the custom recovery is not flashed, i've tried to flash TWRP and CWM
At this point i've managed to make it work, so futhernow i'm kind of afraid to do more :d to be honest.
Please advise if you have any ideas , if not i will let it like this as it works now, but if in the future it will happen again to do the weird things with share screening and other settings perhaps i'll try to flash it again.
Waiting forward for replies.
Best Regards,

Unable to flash TWRP 2

I am also unable to flash TWRP. My issue is different. I had previously flashed TWRP and rooted. I had some issues sending and recieving MMS, so I decided to flash stock firmware and start over. After flashing firmware, I tried to use Root Junkys batch script to re-root the phone. It said no device found. ADB was turned on in developer options. I was also able to flash the logo.bin to get rid of the unlocked bootloader warning. I was able to fastboot boot in TWRP and I restored my backup. However, when I try to flash TWRP, I get an error stating: unknown partition 'C:\Users\steve\Desktop\Moto G4 Plus Fastboot\twrp-3.0.2-0-athene.img'
error: cannot determine image filename for 'C:\Users\steve\Desktop\Moto G4 Plus Fastboot\twrp-3.0.2-0-athene.img'
Any help would be appreciated.

Which command did you use? Did you try pasting the file in the same directory as that of ADB and fastboot and then performing the operation without adding the full directory?

Seems that there's something wrong with your drivers. Same issue was faced by one guy at the Facebook group and the following solved it:
1. Uninstall the drivers you are currently using.
2. Get these latest drivers:
a) Moto drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
b) Fastboot and ADB Drivers: https://www.androidfilehost.com/?fid=745425885120698566
3.) Reboot Windows.
4.) Connect your phone in bootloader/fastboot mode and check if the drivers are working well by opening a command window in the folder where adb & fastboot binaries are present (Shift+Right Click empty area) and type in this:
Code:
fastboot devices
If this returns the device serial number then you're good to go.
5.) Close the command window and download the recovery (Latest is n2) from here:
https://moto.shreps.fr/?dir=Moto G4 (athene)/recovery
6.) Paste the file in the adb/fastboot folder we accessed in step 3.
7.) Open command window there and type:
Code:
fastboot flash recovery filename.extension
Usually it is twrp-3.0.3-n2-athene_shreps.img .
This should return OKAY.
8.) Now navigate to the recovery on the phone using volume keys and choose to Allow Modifications & Always.
9.) Reboot to System and again Reboot to Recovery to confirm the recovery works.
Sent from Google Chrome on Lord Tywin's Windows-PC.

@zeomal could you help in this?
One guy's facing this:
{
"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"
}
I remember someone mentioned something about forcing drivers' singning or something similar on Windows, but I'm unable to find that post.
Sent from Lord Tywin's athene (xt1643)

tywinlannister said:
@zeomal could you help in this?
One guy's facing this:
I remember someone mentioned something about forcing drivers' singning or something similar on Windows, but I'm unable to find that post.
Sent from Lord Tywin's athene (xt1643)
Click to expand...
Click to collapse
Try installing Google's own ADB and Fastboot. Maybe driver signing isn't required for that. I have no information on how to disable it, you'll have to force that.

zeomal said:
Try installing Google's own ADB and Fastboot. Maybe driver signing isn't required for that. I have no information on how to disable it, you'll have to force that.
Click to expand...
Click to collapse
Oh thanks though.. I figured it out myself. In both the cases (mine and the OP) fastboot version was old.

I tried again following the above instructions and exact same result. I can fastboot boot into TWRP to backup, restore, flash etc.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img"
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.485s]
booting...
OKAY [ 0.269s]
finished. total time: 0.769s
When I try to flash it won't work and I get following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash "C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img"
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
unknown partition 'C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img'
error: cannot determine image filename for 'C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img'
I am able to connect via ADB and fastboot and I have a working version of TWRP. I can't figure it out. Should I have relocked the bootloader and then unlocked again after restoring stock firmware?

MisterSteve said:
I tried again following the above instructions and exact same result. I can fastboot boot into TWRP to backup, restore, flash etc.
-snip-
When I try to flash it won't work and I get following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash "C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img"
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
unknown partition ''C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img
error: cannot determine image filename for 'C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img'
I am able to connect via ADB and fastboot and I have a working version of TWRP. I can't figure it out. Should I have relocked the bootloader and then unlocked again after restoring stock firmware?
Click to expand...
Click to collapse
You're missing the recovery destination or image type in your flashing command. Try 'fastboot flash recovery C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img'
Also, since your twrp file is in your ADB folder, you could also use the command: 'fastboot flash recovery twrp-3.0.3-n2-athene_shreps.img'
Both commands to be used without the quotation marks.

echo92 said:
You're missing the recovery destination or image type in your flashing command. Try 'fastboot flash recovery C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img'
Also, since your twrp file is in your ADB folder, you could also use the command: 'fastboot flash recovery twrp-3.0.3-n2-athene_shreps.img'
Both commands to be used without the quotation marks.
Click to expand...
Click to collapse
So to clarify, instead of this command:
fastboot flash C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img'
I should have put the word recovery like this:
fastboot flash recovery C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img'
I ended up getting it to flash using Root Junkys script, which was telling me no device found, but flashed it anyway.

MisterSteve said:
So to clarify, instead of this command:
fastboot flash C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img'
I should have put the word recovery like this:
fastboot flash recovery C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.0.3-n2-athene_shreps.img'
I ended up getting it to flash using Root Junkys script, which was telling me no device found, but flashed it anyway.
Click to expand...
Click to collapse
Yup, that's the correct command - as I understand it, you need to tell what type of image file you're flashing (whether it's boot or recovery, for instance). At least you got it flashed, how recent are the Root Junkys scripts? I had a quick look and they seem to be from 2014? Might explain the no device found - does your device show up if you use the command: 'adb devices' ?

echo92 said:
Yup, that's the correct command - as I understand it, you need to tell what type of image file you're flashing (whether it's boot or recovery, for instance). At least you got it flashed, how recent are the Root Junkys scripts? I had a quick look and they seem to be from 2014? Might explain the no device found - does your device show up if you use the command: 'adb devices' ?
Click to expand...
Click to collapse
I didn't try adb devices in the RJ script, only when I opened up a command window to flash on my own. His script was on his Moto G4 page from 2016, but may have been repurposed from a script for another device.
Thank you all for your help. Lesson to be learned: when you are rusty, slow down and re-read carefully.

[Resolved] LON-L29 - Cannot install opengapps + FRPlock problem

Hello there,
I have a problem, my Huawei Mate 9 Pro (C636) device does not install OpenGApps when I do, although no error messages appear in TWRP (3.2.1-0)
I have in the logs the installation of the different applications that are running. But during the OS boot (Lineage OS 15.1 OpenKirin) I don't have any of the applications (I tried the pico, nano, and super versions of opengapps).
In addition to this concern, since the last re-installation of my lineageOS firmware, I have the FRPLock option which is activated in my bootloader that I can't uninstall, which prevents me from reinstalling my OS.
How to disable it knowing that I can't reactivate the "OEM Unlock" option in the developer options because, according to android, the OEM lock is already disabled.
Thanks to all those who will try to help me, I have not found anyone else in the same case as me, I get stuck.
{
"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"
}
---
Edit : I've just remove my os, I got no OS and FRP Lock
Can you help me to rollback to the right OS ?
>fastboot getvar rescue_version
rescue_version: rescue0.6
Finished. Total time: 0.066s
> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: LON-L29C636B233
Finished. Total time: 0.004s
Click to expand...
Click to collapse
---
EDIT 2 : I've try to reinstall the update with `Multi-Tool 8`
I've download the 3 updates files from `firmware finder` :
LON-L29C636B378 (8.0.0.378)
LON-L29CC636B378 (8.0.0.378)
--------------------------------------
FullOTA-MF
--------------------------------------
2.97 GB
--------------------------------------
From hi cloud : full/update.zip
From hi cloud : full/public/update_data_full_public.zip
From hi cloud : /full/LON-L29_hw_spcseas/update_full_LON-L29_hw_spcseas.zip
Click to expand...
Click to collapse
But I can't install them via adb or fastboot, how can I install them ?
The update fail when I extract theses files one by one in dload folder of my USB stick.
Can you Help me please ?

Shiishii said:
Hello there,
I have a problem, my Huawei Mate 9 Pro (C636) device does not install OpenGApps when I do, although no error messages appear in TWRP (3.2.1-0)
I have in the logs the installation of the different applications that are running. But during the OS boot (Lineage OS 15.1 OpenKirin) I don't have any of the applications (I tried the pico, nano, and super versions of opengapps).
In addition to this concern, since the last re-installation of my lineageOS firmware, I have the FRPLock option which is activated in my bootloader that I can't uninstall, which prevents me from reinstalling my OS.
How to disable it knowing that I can't reactivate the "OEM Unlock" option in the developer options because, according to android, the OEM lock is already disabled.
Thanks to all those who will try to help me, I have not found anyone else in the same case as me, I get stuck.
---
Edit : I've just remove my os, I got no OS and FRP Lock
Can you help me to rollback to the right OS ?
---
EDIT 2 : I've try to reinstall the update with `Multi-Tool 8`
I've download the 3 updates files from `firmware finder` :
But I can't install them via adb or fastboot, how can I install them ?
The update fail when I extract theses files one by one in dload folder of my USB stick.
Can you Help me please ?
Click to expand...
Click to collapse
I finally succeeded on my own ^^
I'm so happy.
Here the solution to fix it :
To solve the problem if others are in the same situation, I have performed an update via e-Recovery but using the Wifi sharing of my PC. On the connection sharing network card of my PC, I put the DNS given by the "Multi-Tool 8" software via the firmware finder, I took the latest firmware from my smartphone and I launched the search on e-recovery in Wifi.
After long waits, it restarted

[GUIDE] [UPDATED METHOD] COLOR OS12 Root 8T

This is the easiest way to root the Color os 12 for oneplus 8t
use this at ur own risk
Must be on unlocked bootloader mode
Firstly Download the attached file
extract it to anywhere
Reboot ur phone into booloader
Just open the Root Fixed.exe file (some of the antivirus are detecting this file as a virus.actually its not a virus, antivirus are detecting this as a virus because of the exe file of rooting,root files will detect as a virus. So before extracting turn off your antivirus)
and enjoy rooting
Done now u can install Magisk Apk ..download it from google
Thanks me
Note: FOD will not work on unlocked bootloader
But there is a workaround flash this in magisk and Fod will be fixed

Reserved

Is FOD working?

taanh1412 said:
Is FOD working?
Click to expand...
Click to collapse
No found a workaround

taanh1412 said:
Is FOD working?
Click to expand...
Click to collapse
sabeehp said:
No
Click to expand...
Click to collapse
FOD is working fine on COS12.
IF you're facing any issue.
check this out,
Release v1.2 · wuxianlin/ColorOSMagisk
What's Changed Replace prop statically by @MlgmXyysd in #6 Full Changelog: v1.1...v1.2
github.com

link is gone?

sabeehp said:
This is the easiest way to root the Color os 12 for oneplus 8t
use this at ur own risk
Must be on unlocked bootloader mode
Firstly Download this files Oneplus 8t Color os 12 root
extract it to anywhere
Reboot ur phone into booloader
Just open the Root.exe file
and enjoy rooting
Done now u can install Magisk Apk ..download it from google
Thanks me
Note: FOD will not work on unlocked bootloader
But there is a workaround flash this in magisk and Fod will be fixed
Click to expand...
Click to collapse
Link died bro

Anticolick said:
Link died bro
Click to expand...
Click to collapse
Link fixed

marreke said:
link is gone?
Click to expand...
Click to collapse
Link fixed

Finger print not working after root any fix

yogesh1970 said:
Finger print not working after root any fix
Click to expand...
Click to collapse
Release v1.2 · wuxianlin/ColorOSMagisk
What's Changed Replace prop statically by @MlgmXyysd in #6 Full Changelog: v1.1...v1.2
github.com
flash this via magisk
(before asking question pls read the full thread there is the way to fix FOD)

sabeehp said:
Release v1.2 · wuxianlin/ColorOSMagisk
What's Changed Replace prop statically by @MlgmXyysd in #6 Full Changelog: v1.1...v1.2
github.com
flash this via magisk
(before asking question pls read the full thread there is the way to fix FOD)
Click to expand...
Click to collapse
Oh thanks mate . ...... U r awesome . M confused in the meaning of FOD. Thanksssssssss

sabeehp said:
This is the easiest way to root the Color os 12 for oneplus 8t
use this at ur own risk
Must be on unlocked bootloader mode
Firstly Download this files Oneplus 8t Color os 12 root
extract it to anywhere
Reboot ur phone into booloader
Just open the Root.exe file
and enjoy rooting
Done now u can install Magisk Apk ..download it from google
Thanks me
Note: FOD will not work on unlocked bootloader
But there is a workaround flash this in magisk and Fod will be fixed
Click to expand...
Click to collapse
hey, the root.exe is not working, it says its using an unlicesed compiler and when you press a key it closes, what commands should I use?

Mcordcc said:
hey, the root.exe is not working, it says its using an unlicesed compiler and when you press a key it closes, what commands should I use?
Click to expand...
Click to collapse
its perfectly working for me..please attach a screenshot

{
"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"
}
windows defender also throws it as a trojan and blocks the exe, have to allow it on device to use it. i just flashed the images with fastboot with the following order (in case someone needs it)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot flash boot boot.img
Click to expand...
Click to collapse

Mcordcc said:
View attachment 5476795
windows defender also throws it as a trojan and blocks the exe, have to allow it on device to use it. i just flashed the images with fastboot with the following order (in case someone needs it)
Click to expand...
Click to collapse
it is because of windows defender..disable windows defender, then try

sabeehp said:
it is because of windows defender..disable windows defender, then try
Click to expand...
Click to collapse
still does it. i got it working with fastboot, maybe doing a CMD would be better, but thanks anyway for the help!

Mcordcc said:
still does it. i got it working with fastboot, maybe doing a CMD would be better, but thanks anyway for the help!
Click to expand...
Click to collapse
Your issue Fixed, File updated. Thanks for reporting

this will also works with CBT 2

dead link