{
"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.
Related
TWRP
This project provides the TWRP recovery for for the Sony Xperia XZ1 Compact (lilac).
{
"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"
}
FEATURES
File-Based Encryption (FBE) support
EXT4 support
F2FS support
EXFAT support
Provides unzip
Additional languages
This recovery will use the security patch level from the system partition to decrypt data. It should not be tied to a security patch level anymore.
DOWNLOAD
Make sure you download the .img and corresponding .asc.txt file (see INTEGRITY)!
You can always find the latest version of the recovery HERE.
INTEGRETY
The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.
How do you do that?
Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
Download the recovery.img and recovery.img.asc.txt file
Rename the recovery.img.asc.txt file to recovery.img.asc
Verfiy the signature using the following command:
Code:
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.asc
A good tutorial is: How to verify signatures for packages from the Tor Project.
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
XDA:DevDB Information
recovery_twrp_sony_lilac, Tool/Utility for the Sony Xperia XZ1 Compact
Contributors
modpunk, Dees_Troy
Source Code: https://github.com/cryptomilk/android_device_sony_lilac
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-09-16
Created 2017-11-18
Last Updated 2019-09-16
Nice work!
What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?
Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51
4rz0 said:
What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?
Click to expand...
Click to collapse
RTFM!
aikon96 said:
Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51
Click to expand...
Click to collapse
No, I need to create one for November. Will do that soon.
modpunk said:
RTFM!
Click to expand...
Click to collapse
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?
4rz0 said:
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?
Click to expand...
Click to collapse
There is no limitation in flashing. However there is no LOS you can flash yet ...
works perferct! thank you :good:
I got an XZ1. Any chance to get TWRP for it (for testing)?
Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img
TWRP
modpunk said:
Could someone please test
Click to expand...
Click to collapse
ok. I'll test it
modpunk said:
Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img
Click to expand...
Click to collapse
I will indeed test too juhuuu...
it flashes okay via fastboot, and twrp is also working. except for format option under wipe, when typing 'continue' it seems like it doesn't show the inputs, only the last letter 'e'
anyway after i flashed the twrp, i booted it up, and mounted everything except for otg. and then of course i flashed magisk.zip (latest v14) and it also succeeded
but then when i reboot from twrp, it stucks at sony logo, meaning default bootanimation doesn't kick in, and i patiently waited for like 10-15 min
so i assume it's not working. i even tried with a userdebug and regular user build 47.1.A.5.51
now i will try just to boot the twrp without flashing it and then flash magisk.zip while it's booted up via fastboot to see if it boots up normally
a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.
modpunk said:
a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.
Click to expand...
Click to collapse
A: it does not ask for password upon bootup so i guess it's not encrypted in that way
B attached here
C is there any specific logcat you want, like error or fatal level etc.
Question just to be clear: do we have to update twrp for evry new securitypatch?
To decrypt the /data partion on a stock ROM, yes you do.
Hi modpunk,
Ur a true star...****
I just want to ask a couple of question's.
Does the bootloader have to be unlocked in order to flash this....?
I have had a Z3 Compact and got it rooted with bootloader locked and also a Z5 Compact using munjen setup.
Install TWRP on it Flashed SuperSU using TWRP was best thing i did.
Do you have a step by step guide how to flash this. I would love to test it for you.
When you flash is it using munjen flashtool...?
Thanks Sham
UPDATE
TRWP is working actually, just figured out that it's magisk that get the phone not to boot, bith 14 and 14.5
and latest supersu both the xperia one and the regular one v.2.82 fails, give error "unzip fail, no proper recovery etc."
Now for fun i will load it up with userdebug firmware and see if i can make it manually root with the "angela" method
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 ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
step 1: Unlock BL
step 2: Flash TWRP and format data
step 3 Flash ROM, Gapps and Magisk
step 4 Reboot
step 5 Done
Update installation:
step 1 Flash ROM
step 2 Reboot
Do not wipe anything
Download:
Galaxy S9: Download
Galaxy S9 Plus (UNTESTED): Download
Known issues:
voLTE, Samsung proprietary apps, Screen Mirroring
Visit official website @ crDroid.net
crDroid S9/+/Note 9 Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Credits go to:
The crDroid team: Website Github
Synt4x93: Github @Synt4x.93
Lineage os team: Website Github
Big thanks to DeinMathelehrer for helping me get everything up and running: Github @hisoka_simp
Epic! I'l try this on my star2lte and let you know.
CustomOsLover said:
Epic! I'l try this on my star2lte and let you know.
Click to expand...
Click to collapse
So, I'm waiting for 5 mins now. It doesn't boot for now
Nice it's working, hope you continue to work on custom Roms
CustomOsLover said:
So, I'm waiting for 5 mins now. It doesn't boot for now
Click to expand...
Click to collapse
UPDATE: it's working now. Might had some problems with my GAPPs
CustomOsLover said:
Epic! I'l try this on my star2lte and let you know.
Click to expand...
Click to collapse
Thankyou!
I've been using this for a day now and I gotta admit, it's so smooth and reliable for now, nothing to argue about! I absolutely love this rom! Thanks for creating this for the S9(+) Hope we'll get more ROMs like this
CustomOsLover said:
I've been using this for a day now and I gotta admit, it's so smooth and reliable for now, nothing to argue about! I absolutely love this rom! Thanks for creating this for the S9(+) Hope we'll get more ROMs like this
Click to expand...
Click to collapse
Perfect thank you so much. I am glad it works. I need a screenshot of it working though to get the dev's approval. His rules not mine. So just dm me a screenshot in xda of it working please, so I can get it validated. (Screenshot of About Phone > Android Version in settings would be best)
Also a word of warning, I may be unable to create a rom for crdroid S (android 12), as I have no idea how to make rom sources. I just know how to compile roms with preexisting sources. So unless someone builds android 12 lineage os or something for the s9 and s9 plus, then the road may end here for this rom unless someone else picks it up.
hisoka_simp said:
Nice it's working, hope you continue to work on custom Roms
Click to expand...
Click to collapse
Thanks for ur help. I might, but I also have a lot of other things to do.
CustomOsLover said:
UPDATE: it's working now. Might had some problems with my GAPPs
Click to expand...
Click to collapse
Yah, sry I don't use gapps, I try to avoid them as much as possible. So I didnt test that.
Linusrg1 said:
Perfect thank you so much. I am glad it works. I need a screenshot of it working though to get the dev's approval. His rules not mine. So just dm me a screenshot in xda of it working please, so I can get it validated. (Screenshot of About Phone > Android Version in settings would be best)
Also a word of warning, I may be unable to create a rom for crdroid S (android 12), as I have no idea how to make rom sources. I just know how to compile roms with preexisting sources. So unless someone builds android 12 lineage os or something for the s9 and s9 plus, then the road may end here for this rom unless someone else picks it up.
Click to expand...
Click to collapse
Here you go:
CustomOsLover said:
Here you go:View attachment 5312933
Click to expand...
Click to collapse
thankyou
@Linusrg1 I'm currently on crDroid 7.2, on the S9; can I update to 7.6 just by flashing the rom through twrp? Will that create any side effects maybe? Like losing data and such? I cba to make a backup as it's very high in size.
kidi said:
@Linusrg1 I'm currently on crDroid 7.2, on the S9; can I update to 7.6 just by flashing the rom through twrp? Will that create any side effects maybe? Like losing data and such? I cba to make a backup as it's very high in size.
Click to expand...
Click to collapse
Thats what I did and it worked fine. If not make a data backup then start off clean.
Linusrg1 said:
Thats what I did and it worked fine. If not make a data backup then start off clean.
Click to expand...
Click to collapse
I mean you sure it won't mess up with magisk manager and tasker? Since I'm just flashing the rom itself and not re-rooting?
EDIT: I've lost root, and it messed up with google apps, as in they were force closing. I've patched the boot.img for magisk to work again as in to re-gain root, and flashed google apps .zip, it seems ok for now. Also it seems it takes a second for the animation to pass through and to be able to enter the pin code on the lock screen after swiping, why's that?
kidi said:
I mean you sure it won't mess up with magisk manager and tasker? Since I'm just flashing the rom itself and not re-rooting?
EDIT: I've lost root, and it messed up with google apps, as in they were force closing. I've patched the boot.img for magisk to work again as in to re-gain root, and flashed google apps .zip, it seems ok for now. Also it seems it takes a second for the animation to pass through and to be able to enter the pin code on the lock screen after swiping, why's that?
Click to expand...
Click to collapse
Because you need to wipe system data cache and dalvik cache flash the rom and then flash data again.
Linusrg1 said:
Because you need to wipe system data cache and dalvik cache flash the rom and then flash data again.
Click to expand...
Click to collapse
It's all okay now, except I found the culprit to the 1-second delay for the animation to step in to enter the pin; when you set up face unlock, that bug appears. When you don't use face unlock but just pin/fingerprint combo, it doesn't have that delay when you swipe on the lock screen to enter pin.
I have the SM-960F/DS version of starlte, which I believe has the Exynos chipset, while the American version has the SnapDragon. Does anyone know if this ROM will have any issues on the SM-960F/DS or does the chipset not matter for the ROM?
DangerousDays said:
I have the SM-960F/DS version of starlte, which I believe has the Exynos chipset, while the American version has the SnapDragon. Does anyone know if this ROM will have any issues on the SM-960F/DS or does the chipset not matter for the ROM?
Click to expand...
Click to collapse
well, for starters, Snapdragon models mostly can't unlock the bootloader. But yes, the exynos models with the latest bootloader (you can install dev base first and then flash this, if you're uncertain) should run this with no problem.
lordsolrac2 said:
well, for starters, Snapdragon models mostly can't unlock the bootloader. But yes, the exynos models with the latest bootloader (you can install dev base first and then flash this, if you're uncertain) should run this with no problem.
Click to expand...
Click to collapse
Sorry, I am somewhat new to the custom ROM scene. Can you explain to me how to check if I have the latest bootloader, what is the dev base and where I can get 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"
}
What is this?PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the deviceBased on Android 12What works?Pretty much everything.Known issuesYou tell meDON'T FLASH GAPPS, THEY'RE ALREADY INCLUDEDDonateHereTranslationHelp with project translationStay tunedOur blogDownload Link for OnePlus 9 ProROMRecovery (Boot.img)Device Chat
INSTRUCTIONSMake sure you are on latest OOS 11 (11.2.10.10)Reboot to bootloaderFlash the provided boot.imgReboot to recoveryFormat data in the recoveryADB sideload PixelROM.zipReboot
Android OS version: 12
Security patch level: FEB 2022
Kernel Source code: Link
Trees Sources :
8350-common
Lemonadep
Source code : https://github.com/PixelExperience
ROM Developer: YouLop09
Special thanks to:Chandu, Edward, Karthik, vjs pranav.
Finally. Hope this goes official. Nice job!
Need to have Bootloader unlocked or not.
Thank u so match
dariodamico said:
Need to have Bootloader unlocked or not.
Thank u so match
Click to expand...
Click to collapse
Yes, you need to have it unlocked
Wow this is incredible!
But i am noob in the new style of flashing custom roms, when i saw a videotutorial i will flash it
adrisanfe said:
Wow this is incredible!
But i am noob in the new style of flashing custom roms, when i saw a videotutorial i will flash it
Click to expand...
Click to collapse
You must be on A11 OOS or any custom rom A11 OR A12. Doesn't matter.
Steps what I did and how I install the rom and root.
Steps:
1. Go to bootloader and use following cmd: fastboot flash boot filename.img (provided by the developer in the 1post recovery.img)
2. Go to option in bootloader and use volume key to choose the reboot to recovery.
3. Once you are in recovery, go to factory format and click factory format data wipe. It will wipe you internal and external storage with formatting data meaning you will lose everything.
4. Go to Apply Update and use following cmd: adb sideload romname.zip and click entre, it will take 10 to 12 mins depending.
5. Once install successfully reboot to system and enjoy the rom.
Steps for root what I used instead of using payload and extracting boot.img. Easy steps root successful.
1. Once you are booted into system successfully and stepup everything as you would.
2. Go to bootloader by holding down volume down and power button. You will enter bootloader menu.
3. You CANNOT root your phone with given recovery in the first post. So, what I did I use the recovery img from DrepFest rom, it's build for A12 it should be safe to use. TWRP is compatible with A12 as of right now.
4. Go to bootloader use cmd: fastboot flash boot DrespFest recovery.img and click enter and reboot to recovery.
5. Now you will entre DrespFest recovery A12.
6. Go to Apply update and use following cmd: adb sideload rootfilename.zip (it's magisk 23). It will root your phone with Magisk 23, but you can update Magisk 24.1 manually without issues.
I have attached Magiosk 23. It can be sideload through recovery of LOS recovery or DrespFest recovery.
Enjoy rom and root.
Congrats brother! Looks good!
Any chances to non-gapps build?
Will try this later, congrats!
Is there anyway to get call recording in this ROM . Thanks
dariodamico said:
Is there anyway to get call recording in this ROM . Thanks
Click to expand...
Click to collapse
not for now
Will it work if I dirty flash from Drespfest A12 to PixelExperience?
vipinpvarghese said:
Will it work if I dirty flash from Drespfest A12 to PixelExperience?
Click to expand...
Click to collapse
Yes
Warrkill said:
Any chances to non-gapps build?
Click to expand...
Click to collapse
No, Pixel Experience always have gapps.
Any chance to non pro ,just OnePlus 9
xarcom said:
Any chance to non pro ,just OnePlus 9
Click to expand...
Click to collapse
soon
ROM looks great, UI is beautiful. Unfortunately, it drains my battery drastically it might be time for a phone upgrade.
pls help I'm having error with ads Sideload gives me "failed to find updated binary META-INf" pls help
edit: sorted it out, Safari extracting the zip file right after the download of the rom and recompiling it gives error so I used chrome to dl and it is going all good
Tried this this morning for a short time, runs really well and feels amazing however once I turned off wifi I could not get it to turn back on.
Whenever I tried it would crash the system and ask to close the ui.
Reverted back to stock before I had to take to go to work
kevrae said:
Tried this this morning for a short time, runs really well and feels amazing however once I turned off wifi I could not get it to turn back on.
Whenever I tried it would crash the system and ask to close the ui.
Reverted back to stock before I had to take to go to work
Click to expand...
Click to collapse
Just a little off-topic, there is a tutorial somewhere of how to go back to stock?
Now that the entire kernel source is released, is anyone working on building a custom recovery and rom for this device? I was looking at building orange fox recovery for it but I couldn't find how to make it with android 13 decryption support.
gwenmillett said:
Now that the entire kernel source is released, is anyone working on building a custom recovery and rom for this device? I was looking at building orange fox recovery for it but I couldn't find how to make it with android 13 decryption support.
Click to expand...
Click to collapse
You build, I'll try.. I'm decrypted with r/w permissions already. Used dfe neo and RO2RW by leegar, termux method and flashed super.img with fastboot.. Seeing as how we don't have recovery yet
{
"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"
}
JWnSC said:
You build, I'll try.. I'm decrypted with r/w permissions already. Used dfe neo and RO2RW by leegar, termux method and flashed super.img with fastboot.. Seeing as how we don't have recovery yetView attachment 5889613
Click to expand...
Click to collapse
May be you can try this https://github.com/BigfootACA/device_nubia_nx729j/releases
vadizzi said:
May be you can try this https://github.com/BigfootACA/device_nubia_nx729j/releases
Click to expand...
Click to collapse
Tried "fastboot boot twrp.img" blackscreen after logo...
Edit: my mistake it worked
i wroted this and it works but very strange. i use fastboot flash recovery ...img; recovery_a ...img and recovery_b ...img. I havent much enthusiasm on twrp so i droped it. You can flash it if worth offcourse
vadizzi said:
i wroted this and it works but very strange. i use fastboot flash recovery ...img; recovery_a ...img and recovery_b ...img. I havent much enthusiasm on twrp so i droped it. You can flash it if worth offcourse
Click to expand...
Click to collapse
Ohh ok. This phone is a little different from my last one op9p..recovery was inside ramdisk..so usually I would boot twrp.img and flash recovery to ramdisk..
I tried fastboot boot twrp.img..it switched to slot b..so I had to set active back to slot a..my mistake
I'll try your method and report back. Thanks!
vadizzi said:
i wroted this and it works but very strange. i use fastboot flash recovery ...img; recovery_a ...img and recovery_b ...img. I havent much enthusiasm on twrp so i droped it. You can flash it if worth offcourse
Click to expand...
Click to collapse
Yeah it worked! Default language is Chinese
It's reading internal storage( decrypted ofc).. Little laggy but usable.. Do you need logs or anything? I'll mess with it a little bit later today.
JWnSC said:
It's reading internal storage( decrypted ofc).. Little laggy but usable.. Do you need logs or anything? I'll mess with it a little bit later today.
Click to expand...
Click to collapse
no i just show it to you. Developer needs i think
vadizzi said:
no i just show it to you. Developer needs i think
Click to expand...
Click to collapse
Thanks! If he post in development section more users can post logs, test, ect ..I didn't even know this existed for our device. Does he have telegram group or something?
JWnSC said:
Thanks! If he post in development section more users can post logs, test, ect ..I didn't even know this existed for our device. Does he have telegram group or something?
Click to expand...
Click to collapse
I've just been browsing github and don't know any information
JWnSC said:
It's reading internal storage( decrypted ofc).. Little laggy but usable.. Do you need logs or anything? I'll mess with it a little bit later today.
Click to expand...
Click to collapse
Hello. Installed your TWRP, but the internal memory is not displayed and there is no active OTG. Did you do something wrong ?
batargin said:
Hello. Installed your TWRP, but the internal memory is not displayed and there is no active OTG. Did you do something wrong ?
Click to expand...
Click to collapse
This isn't my twrp.. I'm already decrypted, so I just test it. I could read internal storage on mine. Your probably still encrypted, so it wouldn't work for you.
JWnSC said:
This isn't my twrp.. I'm already decrypted, so I just test it. I could read internal storage on mine. Your probably still encrypted, so it wouldn't work for you.
Click to expand...
Click to collapse
I realized that you are testing, and I just have no one to turn to for help but you. How can I decrypt it? I just got the device today.
6.49 GB file on MEGA
mega.nz
MIUI 14 Rom you can try it we need some help to install.
ibestmoder said:
6.49 GB file on MEGA
mega.nz
MIUI 14 Rom you can try it we need some help to install.
Click to expand...
Click to collapse
Extract the file to a directory then put your phone in bootloader, connect your phone then go to the directory you extract and click on 8pro****.bat (*** for some chinese character). Your phone will then boot after it is done. However this is not a free rom you can run it for 30 minutes and you will have hard time to get back to stock rom since this rom modify the stock rom partitions.
[email protected] said:
Extract the file to a directory then put your phone in bootloader, connect your phone the go to the directory you extract and click on 8pro****.bat (*** for some chinese character). Your phone will then boot after it is done. However this is not a free rom you can run it for 30 minutes and you will have hard time to get back to stock rom since this rom modify the stock rom partitios.
Click to expand...
Click to collapse
I going to buy it from the maker he going do some changing to English with full support
Have someone tried that miui 14 rom? Are there any screenshots or something about what happens after 30 minutes? Might be possible to just remove that restrictions, but unless there's an easy way to revert back to stock (EDL or something), don't think it makes sense to flash it. Better wait for someone to build a proper CAF/CLO ROM (i.e. Paranoid Android)
aaa.bbb111222 said:
Have someone tried that miui 14 rom? Are there any screenshots or something about what happens after 30 minutes? Might be possible to just remove that restrictions, but unless there's an easy way to revert back to stock (EDL or something), don't think it makes sense to flash it. Better wait for someone to build a proper CAF/CLO ROM (i.e. Paranoid Android)
Click to expand...
Click to collapse
Rom is from chinese dev made out chinese 2.26. you need to pay 4 dollars to unlock it. I im Private with hem going to fix the rom for us
ibestmoder said:
Rom is from chinese dev made out chinese 2.26. you need to pay 4 dollars to unlock it. I im Private with hem going to fix the rom for us
Click to expand...
Click to collapse
It's MIUI, there's nothing that could fix that
That's not the point tho. Gonna assume no one yet tried flashing it (so the potential drawbacks not including 30 minutes lifetime are unknown. Should be always possible to remove that from ROM anyway). And we still don't have any way to unbrick, ZTE doesn't want to give us the flash tool for bs reasons.