Since I promised ill patch ramdisk of P20 (versions) ill try live up to it my promise. Please do note that this is untested since currently I don't own nor any device of P20 line
Installation instructions.
Download the zip for your device and unpack it to your computer.
Boot your phone into bootloader (volume down and plug in cable)
Type: fastboot flash ramdisk yourpatchedboot.img
Reboot!? Proofit!?
Edit: if you have issues with Magisk and safetynet read
secXces_debaki said:
Like i wrote on p20 pro forum @LastStandingDroid you should include that here too..
After flashing the patched ramdisk they should install magisk over magisk manager again to pass safteynet and install modules.
Click to expand...
Click to collapse
Downloads:
EML-L29
https://mega.nz/#!gPBCCCyI!HOCiXH2Zrl84l01PT99U_ElMMuC_JukjgS47DZGkqPQ
Eml-l09?
https://mega.nz/#!dOoAnaIS!MMw2QFp_JNegVG0g95RrVm_AmqDpvtO-wGQX1LLkmYs
EML-TL00/AL00 8.1.0.106
https://mega.nz/#!hKQXgCKT!C2tObO92jyuYBvrVrPeOIfWHSkpVeUCtIgjfuhENaCo
EML-L29 working
EML-L09 untested
EML-AL00/TL-00 untested
Everyone should be pre rooted though
Sent from my DUK-L09 using Tapatalk
will test EML-TL00/AL00 8.1.0.106 tomorrow,thks~!
Thanks!
I'm going to test it on the p20.
Ladies and gentlemen soon a twrp will be hopefully released for P20 pro (tested) and should hopefully work on P20 which will have decryption support.
Don't believe me?
I'm talking to the developer who built it so stay tuned you'll eventually see it
{
"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"
}
Sent from my DUK-L09 using Tapatalk
quick question, does the bootloader have to be unlocked to flash magisk?
Samueldanny said:
quick question, does the bootloader have to be unlocked to flash magisk?
Click to expand...
Click to collapse
Yes
LastStandingDroid said:
Since I promised ill patch ramdisk of P20 (versions) ill try live up to it my promise. Please do note that this is untested since currently I don't own nor any device of P20 line
Installation instructions.
Download the zip for your device and unpack it to your computer.
Boot your phone into bootloader (volume down and plug in cable)
Type: fastboot flash ramdisk yourpatchedboot.img
Reboot!? Proofit!?
Click to expand...
Click to collapse
Hello!
First and foremost, massive thank you for your work.
Second: it, unfortunately, doesn't work for me on my EML-L29TWRP (or I just messed up something). I followed the flash trough Fastboot command, installed magisk manager app but there is no supersu available like on your screenshots I have unlocked my bootloader properly ( get all warnings how my phone cant be trusted).
I just need superSU to remove retail demo app but if necessary I'm willing to debug software.
Also, I have screen captures to show my issue but because I am a new user I cant share them.
LastStandingDroid said:
Ladies and gentlemen soon a twrp will be hopefully released for P20 pro (tested) and should hopefully work on P20 which will have decryption support.
Don't believe me?
I'm talking to the developer who built it so stay tuned you'll eventually see it
View attachment 4476320View attachment 4476321
Click to expand...
Click to collapse
This is a good news. We all wait for this famous twrp, so if it is almost operational it's really an excellent news.
Foglito said:
Hello!
First and foremost, massive thank you for your work.
Second: it, unfortunately, doesn't work for me on my EML-L29TWRP (or I just messed up something). I followed the flash trough Fastboot command, installed magisk manager app but there is no supersu available like on your screenshots I have unlocked my bootloader properly ( get all warnings how my phone cant be trusted).
I just need superSU to remove retail demo app but if necessary I'm willing to debug software.
Also, I have screen captures to show my issue but because I am a new user I cant share them.
Click to expand...
Click to collapse
Which file did you flash
If anyone needs help or has questions
You can join
https://t.me/joinchat/EzNJoUnSYrj_M7CnVvzNKg
I'll be more available at telegram than tapatalk/xda
Sent from my DUK-L09 using Tapatalk
fanfan7110 said:
This is a good news. We all wait for this famous twrp, so if it is almost operational it's really an excellent news.
Click to expand...
Click to collapse
Only downside for now is you can only decrypt if you have no password set. Though
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Only downside for now is you can only decrypt if you have no password set. Though
Click to expand...
Click to collapse
You might want to tell the builder to check the commit from TWRP for Pixel 2. February security patch causing that decryption problem when user have password set. But it has been fixed since march by DeesTroy.
Saftynet is being tripped.
I have L29
otonieru said:
You might want to tell the builder to check the commit from TWRP for Pixel 2. February security patch causing that decryption problem when user have password set. But it has been fixed since march by DeesTroy.
Click to expand...
Click to collapse
I've forwarded this thanks for the info [emoji16]
Sent from my DUK-L09 using Tapatalk
Samueldanny said:
Saftynet is being tripped.
I have L29
Click to expand...
Click to collapse
Interesting. This could be though due to demo unit possibly. Since it most likely isn't going to pass safetynet I can't tell
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Interesting. This could be though due to demo unit possibly. Since it most likely isn't going to pass safetynet I can't tell
Click to expand...
Click to collapse
I'm also unable to install modules.
Samueldanny said:
I'm also unable to install modules.
Click to expand...
Click to collapse
Please do join https://t.me/joinchat/EzNJoUnSYrj_M7CnVvzNKg for better assistance.
Tapatalk gives me tons of updates so can't keep track
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Only downside for now is you can only decrypt if you have no password set. Though
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
On a other side, it's not a big problem. It's simple to remove security password, install twrp and root, and then, put again the security with password.
That was what we had to do with the OnePlus 5T at the beginning of the first versions of TWRP.
we hope that a functional and downloadable version will be available soon
On the other hand if huawei could allow to download a ROM Stock, it would still be safer in case of bad flashing or brick phone. But can we hope that soon, not sure.
Like i wrote on p20 pro forum @LastStandingDroid you should include that here too..
After flashing the patched ramdisk they should install magisk over magisk manager again to pass safteynet and install modules.
secXces_debaki said:
Like i wrote on p20 pro forum @LastStandingDroid you should include that here too..
After flashing the patched ramdisk they should install magisk over magisk manager again to pass safteynet and install modules.
Click to expand...
Click to collapse
Oh yah didn't knew that was needed until a hour ago or two. Have had little time busy spending time with family.
Sent from my DUK-L09 using Tapatalk
Related
{
"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"
}
It have been about 2 years, I finally get a U11 plus to make TWRP device tree with working decrypt function.
Source: https://github.com/sabpprook/android_device_htc_ocm
Please download latest TWRP build in following link.
[Android 8.0]
twrp-3.3.1-0-ocm_171001.img
twrp-3.3.1-0-ocm_171201.img
twrp-3.3.1-0-ocm_180601.img
twrp-3.3.1-0-ocm_180901.img
twrp-3.3.1-0-ocm_181001.img
twrp-3.3.1-0-ocm_181101.img
[Android 9.0]
PS. watch out the last 6 digits at the filename, it must equal to your system's android patch level. e.g. 2017-12-01 (Dec, 2017) = 171201, otherwise TWRP will not decrypt data partition.
PS2. U11+ already get Android Pie update, but this update will break data decrypt function in TWRP recovery.
@nkk71, thanks all the works you've done for us.
Thank you very much!
https://i.imgur.com/71t8xrY.png
https://i.imgur.com/qebNB0C.png
https://i.imgur.com/ubxYZsN.png
https://i.imgur.com/gsbaG2K.png
https://i.imgur.com/xIW8llN.png
https://i.imgur.com/Fzrdhwt.png
Awesome!!
yay. now to get more dev support behind this!
excellent! Please, try to put up a github repo for it, if not already
Hopefully it works fine.
If HTC rolls out kernel sources, I might try some blind development, as I don't have the device, but wanna support it.
Should you need to unlock the official htcdev before they can put?
mapleshadow said:
Should you need to unlock the official htcdev before they can put?
Click to expand...
Click to collapse
Yes, unlock then you can boot it.
Thanks for this! Going to try and get it up and running later today - Need to unlock the BL first.
Thanks for this however it doesn't seem to work for me. I've unlocked the bootloader, rebooted into bootloader mode via adb (adb reboot bootloader), tried to boot the twrp image (fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img) and all I get is a black screen even though the commands seem to work at first:
fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
OKAY [ 10.112s]
finished. total time: 11.006s
Click to expand...
Click to collapse
Any idea what's going on?
aurelienlux said:
Thanks for this however it doesn't seem to work for me. I've unlocked the bootloader, rebooted into bootloader mode via adb (adb reboot bootloader), tried to boot the twrp image (fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img) and all I get is a black screen even though the commands seem to work at first:
Any idea what's going on?
Click to expand...
Click to collapse
Did you flash the custom recovery ..?
P.S. Nothing of linked below worked out?
http://featuresunlocker.com/root-install-twrp-recovery-htc-u11/
Yet sent from my amazing silver U11
jauhien said:
Did you flash the custom recovery ..?
P.S. Nothing of linked below worked out?
Yet sent from my amazing silver U11
Click to expand...
Click to collapse
I didn't flash since I wanted to test it out before using the fastboot boot command recommended in the original post. However this does not seem to work. I wanted to get twrp running so I could use magisk for root
Went ahead and flashed it anyway and I'm happy to report that it worked and did not brick my device. So I still don't know why it won't let me fastboot boot but at least TWRP is now installed.
aurelienlux said:
Went ahead and flashed it anyway and I'm happy to report that it worked and did not brick my device. So I still don't know why it won't let me fastboot boot but at least TWRP is now installed.
Click to expand...
Click to collapse
Be aware that you're now lacking the ability to ota update if you cannot get ahold of a stock recovery.
That's why booting only and making a backup of stock recovery boot and full system partition, is highly recommended.
tbalden said:
Be aware that you're now lacking the ability to ota update if you cannot get ahold of a stock recovery.
That's why booting only and making a backup of stock recovery boot and full system partition, is highly recommended.
Click to expand...
Click to collapse
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
I'll share it here if people are interested. It's version 1.05.400.13 which is the latest version for the Hong Kong version
aurelienlux said:
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
Click to expand...
Click to collapse
OK, that's very professional. :good:
Just others be aware that you should make sure you have a way backwards.
aurelienlux said:
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
I'll share it here if people are interested. It's version 1.05.400.13 which is the latest version for the Hong Kong version
Click to expand...
Click to collapse
That would be fantastic and very good of you if you could share it. Many thanks!
@nkk71 Any idea of decryption problem?
Seems "/firmware" not symlink and "/vendor/bin/qseecom" sepolicy not set correctly
sabpprook said:
@nkk71 Any idea of decryption problem?
Seems "/firmware" not symlink and "/vendor/bin/qseecom" sepolicy not set correctly
View attachment 4342230
Click to expand...
Click to collapse
Looks like you're building in android 7.1 for Oreo decrypt, won't work without the needed sepolicy changes and plat/non_plat contexts, please check the current gerrit updates for the standard HTC U11:
TWRP vold_decrypt patch: https://gerrit.omnirom.org/c/26652/
EDIT2: U11 Oreo decrypt device tree changes needed for a 7.1 build: https://gerrit.twrp.me/c/2756/
If you end up with decryption successful, but it doesn't actually mount /data, then you may even need an updated kernel https://gerrit.twrp.me/c/2761/
which is what we needed. EDIT: Obviously that's a U11 kernel update not a U11+ one, so don't try to use that kernel
Some things will still get changed. I also recommend you build in real DEBUG mode, the straces have much more info than a log or dmesg. by using TW_CRYPTO_SYSTEM_VOLD_DEBUG := true
Prot02018 said:
That would be fantastic and very good of you if you could share it. Many thanks!
Click to expand...
Click to collapse
There you go: https://drive.google.com/open?id=1nkzK_wbSgC6HSlOsNqOc79f94p7v_3wz
That's version 1.05.400.13. I managed to decrypt it successfully using the latest RUU Decryption Tool on Windows. I have a decrypted boot.img and system.img but I haven't yet uploaded those to my drive.
Waiting for your Good news.
[SOLVED] How to apply OTA update with TWRP & Magisk root? Apply latest Factory image
I have Xiaomi Mi Mix 2 with TWRP & latest Magisk 14.0 and Magisk Manager 5.4.3. Running MIUI 9.1 Global Stable 9.1.1.0. It is working great! I was just notified of an OTA update 9.1.2.0 from Xiaomi. How do I apply it without losing data & root? Thanks!
Edit - [SOLVED] see this post https://forum.xda-developers.com/showpost.php?p=74706923&postcount=8
Same question here, I am on Global beta 7.11.6 and want to Update to 7.12.1 but Update doesnt work because twrp is installed as recovery?
Normally for an OTA to be installed it needs the stock recovery otherwise it will fail during checks. So you would have to flash stock recovery and then you could take or flash OTA then you would have to re-root and flash TWRP
Sent from my [device_name] using XDA-Developers Legacy app
jr313 said:
Normally for an OTA to be installed it needs the stock recovery otherwise it will fail during checks. So you would have to flash stock recovery and then you could take or flash OTA then you would have to re-root and flash TWRP
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
OK. Thanks. So best would be to wait until factory image of 9.1.2.0 is available and flash it over the top of current via TWRP?
I'm remembering a tool from when I had Nexus 5 called FlashFire. Wonder if that would work?
colorado_al said:
OK. Thanks. So best would be to wait until factory image of 9.1.2.0 is available and flash it over the top of current via TWRP?
I'm remembering a tool from when I had Nexus 5 called FlashFire. Wonder if that would work?
Click to expand...
Click to collapse
Yeah you could do that or wait for one of the developer to update their factory rom to flash over top. I just checked out the flash fire app and it gave a warning about Xiaomi devices not tested to use caution if you want to try
Sent from my [device_name] using XDA-Developers Legacy app
jr313 said:
Yeah you could do that or wait for one of the developer to update their factory rom to flash over top. I just checked out the flash fire app and it gave a warning about Xiaomi devices not tested to use caution if you want to try
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Looks like global ROM is available here:
http://en.miui.com/download-334.html
Version: V9.1.2.0.NDEMIEI (MIUI9)
Has anyone a stock recovery for me please?
OK. I found this and it worked great!
https://dhananjaytech.com/flash-sto...evice-using-twrp-recovery-or-fastboot-method/
Thanks to Chinmay Dhumal for the tutorial which you can see here:
https://youtu.be/oUUzxYHV_ac
DL the latest stock ROM from here:
http://en.miui.com/download-334.html
DL lazyflasher-no-verity-opt-encrypt.zip by clicking on the download arrow on the top right here:
https://drive.google.com/file/d/0ByWEieei-0nyMTR4R0dxWk9BTms/view
DL Magisk from here:
http://magiskmanager.com/Magisk/Magisk-v14.0.zip
Copy all 3 to your storage on your phone.
Boot into TWRP by powering off your phone and then holding volume up and power until MI splashscreen appears
Then navigate to Wipe and click Advanced wipe.
Check Cache and Davlik/ART Cache and wipe them
Then back out to the main TWRP screen and choose Install
Then flash the new ROM that you downloaded from Xiaomi MIUI page
Then flash Magisk (Or SuperSU if that is what you use)
Then flash lazyflasher-no-verity-opt-encrypt.zip
Then reboot to system
{
"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"
}
In new update notification page, from top right ... I choose download update, the next morning it automatically reboot into twrp and wait my password for decryption , then the new update was applied.
Sent from my Mi MIX 2 using Tapatalk 2
capcase said:
In new update notification page, from top right ... I choose download update, the next morning it automatically reboot into twrp and wait my password for decryption , then the new update was applied
Click to expand...
Click to collapse
Did you keep root? And now your device says 9.1.2.0?
9.1.2, it seems I lost root
Sent from my Mi MIX 2 using Tapatalk 2
capcase said:
9.1.2, it seems I lost root
Sent from my Mi MIX 2 using Tapatalk 2
Click to expand...
Click to collapse
Very interesting.
I'm surprised that the OTA installed on a rooted device with TWRP recovery. That will usually not work.
Thanks!
capcase said:
In new update notification page, from top right ... I choose download update, the next morning it automatically reboot into twrp and wait my password for decryption , then the new update was applied.
Sent from my Mi MIX 2 using Tapatalk 2
Click to expand...
Click to collapse
and what is the password? is the Xiaomi account one?
brainvision said:
and what is the password? is the Xiaomi account one?
Click to expand...
Click to collapse
Whatever you use to login to your phone
colorado_al said:
Whatever you use to login to your phone
Click to expand...
Click to collapse
Mmm.. so the one of the Xiaomi account?
Inviato dal mio Mi MIX 2 utilizzando Tapatalk
brainvision said:
Mmm.. so the one of the Xiaomi account?
Inviato dal mio Mi MIX 2 utilizzando Tapatalk
Click to expand...
Click to collapse
No, the password used to unlock your phone after one normal boot, so of course not one schema.
If you have Schema, you must change Schema system by password system...
El Philou said:
No, the password used to unlock your phone after one normal boot, so of course not one schema.
If you have Schema, you must change Schema system by password system...
Click to expand...
Click to collapse
Thanks for your reply. Now I know it was obvious but if you consider that this is my first Xiaomi device you'll understand my question.
Would you please link me something relevant about how to start modding in mix 2 that is not in OP right now? It would really help me.. I know it's possible to find many guides by googling but you know, something suggested by an expert user is always better than the first one found online
Thanks a lot! [emoji106]
Inviato dal mio Mi MIX 2 utilizzando Tapatalk
colorado_al said:
OK. I found this and it worked great!
https://dhananjaytech.com/flash-sto...evice-using-twrp-recovery-or-fastboot-method/
Thanks to Chinmay Dhumal for the tutorial which you can see here:
https://youtu.be/oUUzxYHV_ac
DL the latest stock ROM from here:
http://en.miui.com/download-334.html
DL lazyflasher-no-verity-opt-encrypt.zip by clicking on the download arrow on the top right here:
https://drive.google.com/file/d/0ByWEieei-0nyMTR4R0dxWk9BTms/view
DL Magisk from here:
http://******************/Magisk/Magisk-v14.0.zip
Copy all 3 to your storage on your phone.
Boot into TWRP by powering off your phone and then holding volume up and power until MI splashscreen appears
Then navigate to Wipe and click Advanced wipe.
Check Cache and Davlik/ART Cache and wipe them
Then back out to the main TWRP screen and choose Install
Then flash the new ROM that you downloaded from Xiaomi MIUI page
Then flash Magisk (Or SuperSU if that is what you use)
Then flash lazyflasher-no-verity-opt-encrypt.zip
Then reboot to system
Click to expand...
Click to collapse
New Magisk is here for latest ver:
magiskmanager(dot)com
HI,
I have a redmi5+ rooted. I use luckypatcher (i applied some patchs to some apps) and i have installed once BusyBox (didn't do anything in special).
I want to know if it is secure to flash the full update?
PS: how do I confirm if the system files and vendor are ok to proceed?
Thanks
Thanks for this guide.
This is the Pixel 2 XL's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Cant wait to try it
Toejam1998 said:
Cant wait to try it
Click to expand...
Click to collapse
Tell me if it's work for you
I'll wait for a few others as well
Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly
does this do the critical unlock as well?
razgriz1234 said:
does this do the critical unlock as well?
Click to expand...
Click to collapse
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
mauronofrio said:
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
Click to expand...
Click to collapse
ok cool thanks for the quick reply
razgriz1234 said:
ok cool thanks for the quick reply
Click to expand...
Click to collapse
I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
jaythenut said:
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
Click to expand...
Click to collapse
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
mauronofrio said:
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
Click to expand...
Click to collapse
Yes mate
jaythenut said:
Yes mate
Click to expand...
Click to collapse
People like to see feedback and in this thread this is the first
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
I think way early on it was established we can't have it unencrypted once the OS install it's completed, unless something changed or I got it wrong. Lol
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
mauronofrio said:
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
Click to expand...
Click to collapse
Grazie.
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
dricacho said:
I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
I think it too, but i don't know why.
dricacho said:
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
mauronofrio said:
I think it too, but i don't know why.
Click to expand...
Click to collapse
The device is very expensive, has dual partitions, has gotten a lot of bad press, and not near as Dev friendly as some others. Having said that, there are about 5 custom roms, root, exposed, substratum, and various launcher and active edge mods. So it's not like we're hurting too bad ??
Moderator Information
Always be caution when you flash files. Be sure to understand how to backup and rescure yoru device in case of flash failure or something happened. It is the general rule for every flash lover.
Click to expand...
Click to collapse
Color OS 12 CBT 1
Android 12
Only for OnePlus 8 PRO
Spoiler: MSM tools for all 1+ version, please use only for your version IN...
Unbrick/Msm tools for Oneplus Smartphones – Complete Collection
Unbrick/Msm tools can restore any Oneplus smartphone to factory image/Stock OS. In the post, we will be adding all the Unbrick/Msm tools for all the Oneplus smartphones and the list will keep updating whenever Oneplus launches a new Smartphone. Join Techibee Telegram Channel Join Now WhatsApp...
techibee.in
Spoiler: Fingerprint Fix
Just installing ColorOSMagisk-v1.2 module and reboot device.
微博
随时随地发现新鲜事！微博带你欣赏世界上每一个精彩瞬间，了解每一个幕后故事。分享你想表达的，让全世界都能听到你的心声！
m.weibo.cn
Spoiler: Color OS 12
1. Backuped your persist before flashing!
OnePlus 8P how to quickly falsh into ColorOS 12
First you download the MSM Tool of Hydrogen OS
Link: https://yun.daxiaamu.c…8C%85%E6%B0%A211.0.4.4
After the flashing is complete, download Hydrogen OS 11.0.13.13
Select local upgrade, select the downloaded package, and perform OTA upgrade
Link: https://yun.daxiaamu.c…ro/%E6%B0%A211.0.13.13
Then download ColorOS 12 CBT 1
Select local upgrade, select the downloaded package, and perform OTA upgrade
OnePlus 8Pro ColorOS 12 CBT 1
link： https://otaafsc-cost.h…555_e253ead2c7ae5e.zip
Restart the phone after installing 100%
Spoiler: Root
- Unlock Bootloader
- Download and extract ColorOS-12_ROOT_8Pro.zip
- Reboot to bootloader
- Run coloroot.bat
- Done
Spoiler: Sim FIX
If You just booted into ColorOS 12 on 8 Pro and have no signal or other sim issues..
Extract the zip and run simfix.bat from fastboot
SimFix_OnePlus8Pro_ColorOS12
https://mega.nz/file/I…Lzi3cliDjvf0U1BxvlE_og
Spoiler: 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"
}
Downloading right now. Any screenshots?
xtcislove said:
Downloading right now. Any screenshots?
Click to expand...
Click to collapse
Added a screenshot to the first topic.
I have not installed it yet, describe pls your experience later.
zloynavseh said:
Added a screenshot to the first topic.
I have not installed it yet, describe pls your experience later.
Click to expand...
Click to collapse
First things first: Thanks for your work.
Everything is working fine but its too much beta to test it as a daily driver.
What i have to say is, i like the new ui overall BUT the OOS11 UI is so much cleaner an i prefer it over any other ui.
-On first boot the numbers to enter my sim code where to big and i couldnt reach the enter key, a reboot fixed it.
No playstore preinstalled.
-Root is working fine
-USB debugging, pc connection has some problems
-Overall it feels good
-It looks and feels clean but i prefer oos look and feel
-Fingerprint animation is awesome
Going back to OOS11 in 10 minutes, you might have some questions first?
More screenshots
xtcislove said:
More screenshots
Click to expand...
Click to collapse
Thx, can you delete part of screenshots with you phone number, ore just smear over it.
Did you check safetynet and GPAY? Is fingerprint works fine?
Oh nice!!! @zloynavseh
I just saw the sim fix. (Last time I test got no-sim error too.)
zloynavseh said:
Thx, can you delete part of screenshots with you phone number, ore just smear over it.
Did you check safetynet and GPAY? Is fingerprint works fine?
Click to expand...
Click to collapse
Yeah thanks didnt saw the number there.
Didnt checked safetynet but gpay was working fine. Fingerprint was working as good as in oos11.
xtcislove said:
First things first: Thanks for your work.
Everything is working fine but its too much beta to test it as a daily driver.
What i have to say is, i like the new ui overall BUT the OOS11 UI is so much cleaner an i prefer it over any other ui.
-On first boot the numbers to enter my sim code where to big and i couldnt reach the enter key, a reboot fixed it.
No playstore preinstalled.
-Root is working fine
-USB debugging, pc connection has some problems
-Overall it feels good
-It looks and feels clean but i prefer oos look and feel
-Fingerprint animation is awesome
Going back to OOS11 in 10 minutes, you might have some questions first?
Click to expand...
Click to collapse
i wasn't able to get root working, could you give a quick instruction?
conquistadore.11 said:
i wasn't able to get root working, could you give a quick instruction?
Click to expand...
Click to collapse
-Unlock Bootloader
-Download and extract ColorOS-12_ROOT_8Pro.zip from first post.
-Reboot to bootloader
-Run coloroot.bat
Done.
What are the chances of this build getting an OTA update since it is a closed beta one?
gsser said:
What are the chances of this build getting an OTA update since it is a closed beta one?
Click to expand...
Click to collapse
Chance more than colorOS 11. Open beta will staring Q1'22.
I'm currently on OOS 11.0.9.9 and directly flashed the CBT through local upgrade. Everything is working fine except fingerprint. All my apps are retained no issues like data loss, no chinese bloatware.
manojkumarn said:
I'm currently on OOS 11.0.9.9 and directly flashed the CBT through local upgrade. Everything is working fine except fingerprint. All my apps are retained no issues like data loss, no chinese bloatware.
Click to expand...
Click to collapse
Did you backuped your persist before flashing? If you didn't do it, I have bad news for you, you will have great difficulty in restoring it! Try to load backup.
zloynavseh said:
Did you backuped your persist before flashing? If you didn't do it, I have bad news for you, you will have great difficulty in restoring it! Try to load backup.
Click to expand...
Click to collapse
Same problem here. I have the persist.img backed up from OOS but replacing data and engineermode folders didn't seem to help
The region are Chinese,, ( on settings, or Europe ?).
conquistadore.11 said:
Same problem here. I have the persist.img backed up from OOS but replacing data and engineermode folders didn't seem to help
Click to expand...
Click to collapse
Did you unblock your Bootloader? Sometimes it's happening when you unblock it.
zloynavseh said:
Did you unblock your Bootloader? Sometimes it's happening when you unblock it.
Click to expand...
Click to collapse
yeah it's unlocked atm. should i re-lock and try again?
xtcislove said:
More screenshots
Click to expand...
Click to collapse
大侠阿木云盘 | 一加手机官方ROM下载
OLAINDEX,Another OneDrive Directory Index
yun.daxiaamu.com
conquistadore.11 said:
yeah it's unlocked atm. should i re-lock and try again?
Click to expand...
Click to collapse
1. Change to Hydrogen OS via MSM, check fingerprint, if it broken resolve via backup persist. Then update Hydrogen.
2. Flashing via MSM Color OS 12 again
{
"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"
}
isn't it yet to be sold and aquired?
more_than_hater said:
isn't it yet to be sold and aquired?
Click to expand...
Click to collapse
I believe it is out in China already
JPower123 said:
I believe it is out in China already
Click to expand...
Click to collapse
Yes, it is out in China and launching on Feb 7 here in India! I'm interested in this phone...
Wasim_Bu said:
Yes, it is out in China and launching on Feb 7 here in India! I'm interested in this phone...
Click to expand...
Click to collapse
What about USA? EU?
luckychukiye said:
What about USA? EU?
Click to expand...
Click to collapse
Pretty sure it's also Feb 7 for USA, not sure about EU, but probs same
I am also waiting for India, to install OOS.
What is kernelSU? I'm wondering if Magisk works on it, it SHOULD being that it's just a patched boot image. But I'm curious to know
H4X0R46 said:
What is kernelSU? I'm wondering if Magisk works on it, it SHOULD being that it's just a patched boot image. But I'm curious to know
Click to expand...
Click to collapse
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
luckychukiye said:
What about USA? EU?
Click to expand...
Click to collapse
It's launching on Feb 7th for USA and UK!
huangsijun17 said:
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
A new root solution? Does Magisk not work on the OnePlus 11 or are they both viable options? I'm confused now.
H4X0R46 said:
A new root solution? Does Magisk not work on the OnePlus 11 or are they both viable options? I'm confused now.
Click to expand...
Click to collapse
A new root solution, can run with Magisk at the same time.
Because when I just got the phone, there was no TWRP and ZIP flashing package. I'm having a hard time installing Magisk directly. But after I gave Magisk Manager Root permission with KernelSU, I installed Magisk directly.
huangsijun17 said:
A new root solution, can run with Magisk at the same time.
Because when I just got the phone, there was no TWRP and ZIP flashing package. I'm having a hard time installing Magisk directly. But after I gave Magisk Manager Root permission with KernelSU, I installed Magisk directly.
Click to expand...
Click to collapse
When you root with magisk. You need to unlock the bootloader. Then install magisk manager app. Pull your stock boit.img from stock firmware and put it on phone. Open magisk manager and select install then patch boot.img . Then copy the generated image magisk patched image to computer adb folder. Then reboot phone to fastboot. On computer type fastboot boot (name of patched boot.img).img phone will reboot and have root. Go back to magisk and select direct install then reboot.
toolhas4degrees said:
When you root with magisk. You need to unlock the bootloader. Then install magisk manager app. Pull your stock boit.img from stock firmware and put it on phone. Open magisk manager and select install then patch boot.img . Then copy the generated image magisk patched image to computer adb folder. Then reboot phone to fastboot. On computer type fastboot boot (name of patched boot.img).img phone will reboot and have root. Go back to magisk and select direct install then reboot.
Click to expand...
Click to collapse
No. I never exported boot.img or boot_init.img from my phone. There is also no unpacking payload.bin to extract them. After installing KernelSU and KernalSU Manager, I use KernelSU to give Magisk Manager a root privilege. Magisk Manager will automatically install Magisk.
In addition, Magisk needs to patch boot_init.img in devices pre-installed with Android 13, and the flash command is also fastboot flash boot_inti boot_init.img.
huangsijun17 said:
View attachment 5804063
Click to expand...
Click to collapse
Hi,
can you pleaaase try this app if it works with root or no??
CIB Egypt Mobile Banking - Apps on Google Play
The CIB Mobile Banking app is designed to meet all your banking needs.
play.google.com
loshabih said:
Hi,
can you pleaaase try this app if it works with root or no??
CIB Egypt Mobile Banking - Apps on Google Play
The CIB Mobile Banking app is designed to meet all your banking needs.
play.google.com
Click to expand...
Click to collapse
Three interfaces: GKI supported, GKI not supported and already installed. In addition, for devices that do not support GKI, it is also possible to compile the kernel yourself.
huangsijun17 said:
View attachment 5811645
View attachment 5811647View attachment 5811651
Three interfaces: GKI supported, GKI not supported and already installed. In addition, for devices that do not support GKI, it is also possible to compile the kernel yourself.
Click to expand...
Click to collapse
thanks for your reply,
my main question was if you have kernelSU can you try the app that i mentioned and see if it works or no?
other question can you share any tutorial how to build GKI kernel ?
loshabih said:
thanks for your reply,
my main question was if you have kernelSU can you try the app that i mentioned and see if it works or no?
other question can you share any tutorial how to build GKI kernel ?
Click to expand...
Click to collapse
I installed Magisk and KernelSU at the same time, so I can't test the APP for you. But in theory, KernelSU uses a whitelist system, and unauthorized software cannot detect the existence of the su file.
loshabih said:
thanks for your reply,
my main question was if you have kernelSU can you try the app that i mentioned and see if it works or no?
other question can you share any tutorial how to build GKI kernel ?
Click to expand...
Click to collapse
For devices that support GKI 2.0, you can directly download the corresponding version of boot.img from Github Action to flash in.
huangsijun17 said:
I installed Magisk and KernelSU at the same time, so I can't test the APP for you. But in theory, KernelSU uses a whitelist system, and unauthorized software cannot detect the existence of the su file.
Click to expand...
Click to collapse
can you lock the bootloader while you have kernelSU? as the app is checking the bootloader status?