TWRP cant decrypt CM13 partitions (Android 6.0.1) ? - Android Q&A, Help & Troubleshooting

** UPDATE 2016-09-28 ** Android 6.01 enables support for HW_Crypto in Snapdragon 800+ phones, which requires recompiled TWRP.
-----------------------------------------------------------
Hi, can anybody clarify whether TWRP is meant to be able to decrypt CM13 (Android 6.0.1) EXT4 partitions ?
According to TWRP 3.0.2.0 it should support encryption but this version was released a while ago.
When I enter my encryption pin in TWRP it gives a "password failed" error.
I finally got CM13 encryption all setup and now I find I cant do an upgrade because CM updater reboots to recovery which then cant decrypt to write the updates.
So if it DOESN'T support encryption, how the heck do people upgrade their encrypted CM installs ? Is there a better recovery than TWRP ?

Digian said:
Hi, can anybody clarify whether TWRP is meant to be able to decrypt CM13 (Android 6.0.1) EXT4 partitions ?
According to TWRP 3.0.2.0 it should support encryption but this version was released a while ago. I never tried it with an old Android 5 rom.
When I enter my encryption pin in TWRP it gives a "password failed" error.
I finally got CM13 encryption all setup and now I find I cant do an upgrade because CM updater reboots to recovery which then cant decrypt to write the updates.
So if it DOESN'T support encryption, how the heck do people upgrade their encrypted CM installs ? Is there a better recovery than TWRP ?
Click to expand...
Click to collapse
What phone are you using?
Sent from my GT-S7580 using Tapatalk

DodoGTA said:
What phone are you using?
Click to expand...
Click to collapse
Galaxy s4 LTE-A (i9506) aka "ks01lte".

Ok so it turns out Snapdragon 800 phones have hardware encryption module which is not compiled in TWRP.
You can see my thread here for more info, if anyone can help re-compile TWRP for i9506 to add the required dependency for HW_CRYPTO, i will tip some $$
# HW CRYPTO - TWRP needs to be compiled with these flags (there may be other tweaks required, im not sure)
TARGET_HW_DISK_ENCRYPTION := true
TARGET_KEYMASTER_WAIT_FOR_QSEE := true
http://forum.xda-developers.com/gal...wrp-mount-encrypted-partition-recent-t3468989
Note this problem affects many phones, snapdragon 800, 801, 808 and probably other CPUs with HW crypto.
Nexus 5 | MSM8974 Snapdragon 800 | hardware keystore
LG G4 & LG G4 H815 | MSM8992 Snapdragon 808 | can't find quickly
Sony Xperia Z3 Compact | MSM8974AC Snapdragon 801 | hardware keystore
Sony Z1 Compact | MSM8974 Snapdragon 800 | hardware keystore
Sony Xperia Z3 | MSM8974AC Snapdragon 801 | hardware keystore
1+1 | MSM8974AC Snapdragon 801 | hardware keystore
Galaxy s4 i9506 (msm8974) | Snapdragon 800 | hardware keystore

Related

[AOSP 8.1] [2019-03-06] Phh-Treble

WARNING: You'll most probably loose ALL your data, and might break your phone. Please use with extreme caution!
The goal of this ROM is to provide full Treble-compatible hardware support, and nothing else.
This means that hardware which DON'T have Treble API won't be supported, like Essential's external camera.
No feature will be added. This will ease forward porting to new Android versions, which is the very goal of Project Treble
My hope is that other ROM developers will use this ROM as a basis to construct more advanced ROM.
For a list of supported devices, consult and fill https://github.com/phhusson/treble_experimentations/wiki
How to flash:
Follow instructions available at https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Changelog
v29 (2019-03-06):
- March security patch
- Fix MT6739 incoming SMS and mobile data
v27 (2019-01-08):
- January security patch
- arm32_binder64 variant
- Minor stuff
v25 (2018-09-07)
- September security patch
- [Mi 6X/Mi Pad 4] Fix backlight
- [Mi Mix 2S] Disable fingerprint button behaviour
- [Galaxy S9/Note 9]
- Fix (some) MTK incoming call
- Fix a2dp on some devices
- Fix boot on some devices
v23 (2018-08-07):
- August security patch
- Fixes tethering on some Qualcomm devices (Thanks @notsyncing)
- Enable Ambient Display for everyone
- Add an off-computer flasher (first step towards OTA)
- Fixes MTP
- Fixes fingerprint on Moto devices
- Change Huawei quick charge based on device (Thanks @Dil3mm4 )
- Fixes camera on Moto devices
- Fix notches height for some devices (Thanks @tadiT7)
v22 (2018-07-03):
- July security patches
- Fixes Samsung Galaxy S9 fingerprint enrollment
- Fix in-call audio for Pixel 2
- Disable night mode on some MTK for which it is very slow
- Fix wifi tethering on some configurations
v21 (2018-06-27):
- [OnePlus 6] Fix booting on A slot
- [OnePlus 6] Fix userdata filesystem size
- [OnePlus 6] Include a framework-res overlay (fixes auto backlight, improve battery-life, ...)
- Fix status bar height for notches on various devices (Thanks @tadiT7)
- [Samsung Galaxy S9 Qualcomm] Fix backlight
- Fix webview in Android Go variant
- Fix audio jack for some devices
- Fix H264 encoding on Huawei (Thanks @OldDroid)
- Fix backlight on some SDM845 devices (Xiaomi Mi Mix 2S, Xiaomi Mi8)
v20 (2018-06-07):
- June Android security patch level
- New experimental FLOSS variant (check sources for list of apps)
- [OnePlus6] Fixes backlight
- [OnePlus6] Partial support for DnD slider
- Fixes bug on some A/B devices where device would stop booting after several success
v19 (2018-06-03):
- Huawei fast charge (Thanks @flex1911 and @OldDroid)
- Fix MTK TrustKernel TEE (those devices will need to factory reset!)
- Support 32bits Android 8.0 devices
- Rewrite Security Patch Level for Android 8.1 devices, and A/B devices as well. Should fix boot for some devices.
- Enable GPU profiling on Huawei devices to fix UI glitches
- Fixed Modded Google Camera installation
- Use round icons
- Enable doze
- New Android Go variant
- On Huawei devices add "Swipe fingerprint for notifications" option
- Releases are now compressed with xz. Uncompress before flashing.
v18 (2018-05-14):
- Update to Android Security Patch level 2018-05-01
- Disable HW keystore on mediatek devices using trustedkernel, until it is fixed
- Re-enable Huawei navigation keys (Thanks @LuK1337 and OpenKirin team)
- Fixes android build version/security patch level (might lead to stuck on bootanimation some devices)
- Enable NightMode for everyone
- Enable automatic backlight with Huawei Mate 9 settings on Huawei devices
- Remove unnecessary warning on boot (if you still get it, it means it is useful, to tell me!)
- Include android.system.net.netd, fixes data connection for several Qualcomm devices
v17: (2018-04-24)
- Fixes multimedia from SDCard
- Fixes in-call audio for Qualcomm devices
- Fixes in-call earpiece/speaker for Foxconn/Qualcomm devices (Razer Phone, Sharp Aquos S2, ...)
- Fixes signal level for Huawei devices (Thanks to OpenKirin team)
- Fixes boot on some A-only devices (HTC U11+, Xperia XZ1 at least)
- Report vendor's security patch level instead of framework security patch level
- Fix fsck for f2fs (Thanks @flex1911 and @LuK1337)
v16: (2018-04-05)
- Fixes MTP access to sdcard
- v15 was missing graphical glitches fix. Applied it again.
- Resize /system to maximum size on first boot
v15: (2018-04-03)
- Update to 2018-04-01 security patches
- Fixes FAT sdcards
- Fixes some USB-C headphones on some devices
- Fix Essential PH-1 boot
v14: (2018-03-26)
- Fixes Galaxy S9(+) backlight control
v13: (2018-03-23)
- Disable Android's fake touches, which made unlocking hard
- Fixes Galaxy S9 boot and WiFi
- Make system.img back to 1.5GB
- Disable again adb auth, to help debugging
v12: (2018-03-05)
- Updated to security patch 2018-03-01
- Various stability, behind-the scene, changes
- Fixes camera on MTK devices
- Support ARM32 devices
- Supports HW button backlight
v11: (2018-02-20):
- Fixes bluetooth on Kirin 970 devices (Thanks @LuK1337)
- Fixes sdcard on Huawei devices
- Includes nfc-nci.conf, should fix NFC on some devices
- Show real Android version (Thanks @LuK1337)
- Enable ADB authentification
v10: (2018-02-18)
- Android 8.1 !
- Includes versioned vndk, so devices running both 8.1 and 8.0 should work
v9: (2018/01/15)
- Include the compositing fixes for Kirin 970
- Crude support for Huawei fingerprint gestures (click = home, left = back, right = voice assistant, up = quick settings, down = notifications, long press = recent apps)
v8: (2018/01/14)
- Huawei compositing fixes (fixes various graphical glitches)
- Various su SELinux fixes
v7: (2017/12/30)
- Fixes various regressions (APNs, A/B, vanilla, fingerprint ...)
- Fixes dev/input requirement (not useful to any real-life product yet, afaik)
- Fixes some not-installable applications from Play Store
- Fixed substratum in phh's superuser
v6: (2017/12/19)
- Major code clean-up. Please report regressions
- Fixes random reboot on Huawei devices
- Optionally includes SU (you need to install phh's SuperUser from F-Droid/Play Store)
v5: (2017/12/14)
- Fixes FDE decryption (SystemUI was crashing in loop)
- Use a real list of APNs
- Include Chrome and Gboard (fixes IME crash when trying to input a symbol)
- Fixes SEPolicy for Hardware Overlay Picker (should fix crash of Hardware Overlay Picker on startup)
v4: (2017/12/10)
- Fixes sdcard in MTP
- Fixes Dual-SIM
- Includes hardware-specific overlays:
- Enable 4G selection in networks
- Bigger status bar on Essential PH-1
- Enable navigation bar on HTC U11+
v3: (2017/12/04)
- Fixes sdcard in MTP build fail, so will be fixed in next release
- New variant including gapps
v2: (2017/11/26)
- Fix wifi tethering
- Fix F2FS userdata
- Fix sdcard
- Fix fingerprint (Huawei)
Download:
https://github.com/phhusson/treble_experimentations/releases/download/v29
Want to chat about this project? Go to Freenode IRC, #phh-treble.
IRC: irc://irc.freenode.net/#phh-treble
WebIRC: http://webchat.freenode.net/?channels=#phh-treble&uio=d4
Matrix: #freenode_#phh-treble:matrix.org
Other chatrooms:
Telegram https://t.me/phhtreble
Thanks @MishaalRahman and @Exelios for the huge kickstart help
Thanks to all my donators:
- @Exelios
- @fargonaz
- @VictorM86
- @howdid
- @heatfire
- @ohwarumbloss
- @RexGoogolplex
- @abhas.abhia
- @Emoclaw
- @Sebianoti
- @DocRambone
- @egandt
- @Blackbird1997
- @Burakki
- @josdehaes
- @TheUndertaker21
Thanks to the following companies:
- Huawei, for a Huawei View 10
- Blackview, for a Blackview A20
PS: Yes the name sucks, but I'm clueless about a name
How to know if your phone is supported:
- Does your OEM provides a stock Oreo ROM?
No ===> Your phone is not supported
- Run Treble Check on stock Oreo ROM. Does it say Treble is supported?
No ===> Your phone is not supported
If all answers are yes, then your phone MIGHT be supported.
Test it, and report the result!
Build script available at https://github.com/phhusson/treble_experimentations/blob/master/build.sh
Current status:
Over-all:
Xperia XZ1:
- Broken camera (because of Sony's DRM)
Huawei Mate 9 Pro and Honor 9:
- Fingerprint sensor should have "home" behaviour
- software keys should be disabled
Known end-user problems (WON'T BE FIXED in this ROM):
- No exfat
Known mess:
- A-only should use https://android-review.googlesource.com/q/hashtag:"non-ab-boot-gsi"+(status:open OR status:merged) instead of dm-verity hacks
- the dm-verity work-around is also needed on A/B, so other patches are missing, for some other reason
- On A/B devices, this system.img effectively transforms the device into a userdebug build. This means adb root works!
adb root should work on A-only later too, though it requires that the OEM includes https://android-review.googlesource.com/q/topic:move-adbd-to-system+(status:open+OR+status:merged)
This can probably be worked-around by moving adbd inside a /system/etc/init/xxx.rc
- ADB auth is totally disabled at the moment on A/B, this is bad, but useful for debugging.
- Huawei (for instance Mate 9) doesn't declare android.hardware.fingerprint. This ROM does it for them, but this need to be better implemented
- SuperSU and Magisk screws with SELinux policy. DO NOT USE SuperSU OR Magisk WITH THIS ROM
Great work guys, indeed revolutionary work, Congrats
Can there be support for the LG optimous g pro
Leone/kyleproxx said:
Can there be support for the LG optimous g pro
Click to expand...
Click to collapse
That phone was released in 2013, so it's unlikely.
Support for Xiaomi Redmi Note 4 (mido), is it possible?
Following the project.
weldone @phhusson.
will this rom support oneplus5 later on?
jef_00 said:
will this rom support oneplus5 later on?
Click to expand...
Click to collapse
OnePlus said they won't support Treble, so no.
You can try to complain to them, since all they do is because for good PR.
phhusson said:
OnePlus said they won't support Treble, so no.
You can try to complain to them, since all they do is because for good PR.
Click to expand...
Click to collapse
thanks for you answer mate
Wonderful work you're doing here! Would you mind explaining what is the A/B only versions? What do those letters mean? Are there means of reverting back from your experimental build to stock Oreo?
Swan Princess said:
Wonderful work you're doing here! Would you mind explaining what is the A/B only versions? What do those letters mean? Are there means of reverting back from your experimental build to stock Oreo?
Click to expand...
Click to collapse
A/B refers to the new partitioning system on the Pixel and Essential devices. It has one active slot and a backup slot for all parts of the system, so you'll have a boot_a and boot_b, system_a and system_b, and so on. Most devices still use a singular slot system, so unless you have a pixel or essential phone, you would flash the normal O build. Also, the steps on how to flashing back to stock are usually device specific, but you should be able to restore your stock O build by just reflashing the stock system.IMG from your device and wiping in fastboot.
IH8TouchWiz said:
A/B refers to the new partitioning system on the Pixel and Essential devices. It has one active slot and a backup slot for all parts of the system, so you'll have a boot_a and boot_b, system_a and system_b, and so on. Most devices still use a singular slot system, so unless you have a pixel or essential phone, you would flash the normal O build. Also, the steps on how to flashing back to stock are usually device specific, but you should be able to restore your stock O build by just reflashing the stock system.IMG from your device and wiping in fastboot.
Click to expand...
Click to collapse
Oh, thank you for explaining that to me! I have a Mate 9 and I seem to enjoy living on the bleeding edge, at the same time I'm dependent on WiFi tethering for my net. So may try it and see how it works at least. Would love to see if we get any opportunities to fiddle with the camera processing and GPS subsystems, as those are my hobbies.
Swan Princess said:
Wonderful work you're doing here! Would you mind explaining what is the A/B only versions? What do those letters mean? Are there means of reverting back from your experimental build to stock Oreo?
Click to expand...
Click to collapse
Well A/B is the new partitioning scheme where all firmware partition exist twice, and the bootloader switches from one to the other when updating. This is also called seamless updates.
To revert back to stock... Well flash stock?
interesting project, I've a question..are there any chance to run this project on device like P8 Lite 2015 (Kirin620) and P8 Lite 2017 (kirin655) since both are arm64? and also System A/B must be enabled on that device? thanks in advance
haky 86 said:
interesting project, I've a question..are there any chance to run this project on device like P8 Lite 2015 (Kirin620) and P8 Lite 2017 (kirin655) since both are arm64? and also System A/B must be enabled on that device? thanks in advance
Click to expand...
Click to collapse
Unless they are officially updated to Oreo and supports Treble (very unlikely), then no.
PresidentMcCain said:
Unless they are officially updated to Oreo and supports Treble (very unlikely), then no.
Click to expand...
Click to collapse
Only P8 Lite 2017 will get Android Oreo soon reported by many websites, but not sure if can handle Treble project.
I can try Port for Mido (Redmi Note 4/X)?

Technicolor UZW4030WNH

I have this STB (Technicolor UZW4030WNH) and would like to root it. I've read countless resources in this subforum, but found nothing so far that applies to my model (which has a S905D chip). So, some specs of it are the following:
Broadcast | DVB-T/T2, IPTV
Manufacturer | Technicolor
UI & Launcher | Zappware
Code name | UZW4030WNH (Pearl A)
Android TV | 7.1.1
SoC | Amlogic S905D
CPU | Quad-core 1.5 GHz (ARM Cortex-A53)
GPU | ARM Mali-450 MP3
RAM | 2GB
Storage | 8GB
Certifications | Wi-Fi - Bluetooth - EU Declaration of Conformity - Netflix 4K
Click to expand...
Click to collapse
Any help, or guidance would be greatly appreciated. TIA.
EDIT: BTW, I've seen that @Ricky Divjakovski has quite some time to log in here. Anyone knows if the dude is OK?
I am also interested in this device. Did you manage to make any progress?
I interesting too! I can't even boot to fastboot mode. When I try from adb it's stuck in logo and don't do anything.

[Hisense L695 Pureshot+] Possible update to Android 8.0 OREO with custom ROM

Hi,
I was trying to find a way to update my Hisense L695 Pureshot+ from current Android version 5.0.2 Lollipop
Hisense L695 - L695W - Pureshot+ specs :
CPU : Qualcomm Snapdragon 415 MSM8929, 2015, 64 bit, octa-core, 28 nm,
GPU : Qualcomm Adreno 306 GPU - Dedicated Graphics Mamory 0.25MB
RAM : 2 GiB RAM - LPDDR3 SDRAM - 667 MHz
ROM : 16 GB ROM - eMMC 4.5
Display : Res. 720x1280 , pixel density 267 PPI
Other datails refer to :
Hisense Pureshot+ TD-LTE Dual SIM | Device Specs | PhoneDB
Specs: 2015 Sep 9, Android, Qualcomm Snapdragon 415 MSM8929, 2015, 64 bit, octa-core, 28 nm, Qualcomm Adreno 306 GPU, 2 GiB RAM, 16 GB ROM, 5.5 inch, 720x1280, Color IPS TFT LCD display, Dual standby, GPS, 13.0 MP camera, 5.0 MP sec. cam, L sensor, 2500 mAh battery
phonedb.net
I found this website claiming that is possible to install a custom ROM Lineage OS 15 Oreo on Hisense Pureshot+
Download Custom ROM Hisense PureShot+ Lineage OS 15 Oreo
Download Custom ROM Hisense PureShot+ Lineage OS 15 Oreo by Cakrajiya Sirait
dianariyanto.com
"Install custom rom Lineage OS 15.0 OREO for Hisense PureShot+ based on Samsung S7 edge Oreo Custom ROM (port by metacarpalpuss xda-developer)."
Also, the links posted by the author of the above site are not working, specifically the ones related to
los15_hisense-pureshot-plus_beta.zip
gapps15_hisense-pureshot-plus_nano.zip
I don't know how reliable is this site, that's why I would like to check first with xda members.
if anyone has tried this path before, please let me know
Thank you

Size of image is larger than the target device in TWRP

Hi, I am trying to flash a system image in TWRP.
When i try flashing the system.img to the System Image partiton i get this error:
Code:
Size of image is larger than target device
How can i solve this error? I tried the resize partition option on the system partition but seems that it doesn't help.
The phone is a Huawei P Smart (FIG-LX1).
you could shrink the file. give more information about partition layout and the file you are trying to flash.
Code:
259 4 2367488 mmcblk0p52
aIecxs said:
you could shrink the file. give more information about partition layout and the file you are trying to flash.
Code:
259 4 2367488 mmcblk0p52
Click to expand...
Click to collapse
How do I shrink it? And how do i give you more info about the partiton? The file is a system image of a custom rom for my phone.
found your device meanwhile. this is information you could provide from beginning. spreading information over multiple threads is bad attitude
https://forum.xda-developers.com/t/...ei-p-smart-2018-fig-lx1.4535331/post-87922363
how about link to rom you're trying to flash? how big is the file size?
useless double posts
https://forum.xda-developers.com/t/...e-cannot-flash-images-to-file-systems.4535981
https://forum.xda-developers.com/t/...led-remote-sparse-flash-write-failure.4536295
aIecxs said:
found your device meanwhile. this is information you could provide from beginning. spreading information over multiple threads is bad attitude
https://forum.xda-developers.com/t/...ei-p-smart-2018-fig-lx1.4535331/post-87922363
how about link to rom you're trying to flash? how big is the file size?
useless double posts
https://forum.xda-developers.com/t/...e-cannot-flash-images-to-file-systems.4535981
https://forum.xda-developers.com/t/...led-remote-sparse-flash-write-failure.4536295
Click to expand...
Click to collapse
The ROM name is Kangvip, the image size is 3,153,712,956 bytes (3GB). I have downloaded it from here: https://mega.nz/file/QHZAHBbA#V4MaeY5BXMCQo3wOXVcRNcr8qckKsGRanqEdAG-Z41M
(i have got this link from a youtube video, i dont know if i can post the link of it)
well that's too large 700 mb in compressed state is probably even larger when unsparsed with simg2img. you can repartition emmc storage but that is dangerous. I strongly recommend not to try, because in case you brick you might lose fastboot
download partitioning tools here (attachments)
https://forum.xda-developers.com/t/3712171
Tutorial
https://iwf1.com/how-to-re-partitio...-all-options-included-change-size-fs-type-etc
aIecxs said:
well that's too large 700 mb in compressed state is probably even larger when unsparsed with simg2img. you can repartition emmc storage but that is dangerous. I strongly recommend not to try, because in case you brick you might lose fastboot
download partitioning tools here (attachments)
https://forum.xda-developers.com/t/3712171
Tutorial
https://iwf1.com/how-to-re-partitio...-all-options-included-change-size-fs-type-etc
Click to expand...
Click to collapse
But is that tool to do the repartition?
the "tool" is a binary called parted
in case you make any typo the device becomes unrecoverable immediately​
do you really think that unknown obviously incompatible ROM is worth it wasting your Huawei P Smart?
aIecxs said:
the "tool" is a binary called parted
in case you make any typo the device becomes unrecoverable immediately
Click to expand...
Click to collapse
But you told me to not do that
aIecxs said:
the "tool" is a binary called parted
in case you make any typo the device becomes unrecoverable immediately
do you really think that unknown obviously incompatible ROM is worth it wasting your Huawei P Smart?
Click to expand...
Click to collapse
Yes i understand, i will try another ROM and tell you the result
this device support GSI A-only arm64
https://github.com/phhusson/treble_experimentations/wiki/Huawei-P-Smart
[DISCONTINUED][GSI][10] LineageOS 17.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 16.0 GSIs I've been making since March 2019. If you clicked in here, I bet you know what LineageOS is already, but just to fill the blank: LineageOS is a free, community built...
forum.xda-developers.com
try this
https://sourceforge.net/projects/an...1-20210808-UNOFFICIAL-treble_arm64_avS.img.xz
Code:
{arm|a64|arm64}_{a|b}{v|g}{N|S}-{vndklite|secure|personal}
| | | | |
| | | | vndklite: For VNDKLite devices,
| | | | or for read-writeable /system on regular devices
| | | | secure: Superuser removed and system props spoofed,
| | | | for better chances of passing SafetyNet
| | | | personal: With personal mods, for reference
| | | |
| | | N: No Superuser
| | | S: *Built* with PHH Superuser (app needed)
| | | (Z): *Built* with eremitein's Dynamic Superuser (not offered here)
| | |
| | v: Vanilla, i.e. no GAPPS
| | g: With regular GAPPS
| | o: With Android Go GAPPS
| | (f): With built-in MicroG and FLOSS replacements of GAPPS (not offered here)
| |
| a: "A-only", i.e. system-as-system (deprecated since Android 12)
| b: "AB", i.e. system-as-root
|
arm: ARM 32-bit (deprecated since Android 12)
a64: ARM 32-bit with 64-bit binder
arm64: ARM 64-bit
aIecxs said:
this device support GSI A-only arm64
https://github.com/phhusson/treble_experimentations/wiki/Huawei-P-Smart
Click to expand...
Click to collapse
Is it a ROM?
Unofficial LineageOS 17 GSI released for Project Treble compatible devices
You can now get LineageOS 17, based on Android 10, on any Project Treble compatible device thanks to this unofficial LineageOS 17 GSI release.
www.xda-developers.com
How to flash a Generic System Image (GSI) on Project Treble supported devices
So your device supports Project Treble, what does that mean for you? It means you can flash a Generic System Image such as LineageOS or Resurrection Remix! Enjoy AOSP-based custom ROMs! Here's a guide on how to install these ROMs.
www.xda-developers.com
aIecxs said:
Unofficial LineageOS 17 GSI released for Project Treble compatible devices
You can now get LineageOS 17, based on Android 10, on any Project Treble compatible device thanks to this unofficial LineageOS 17 GSI release.
www.xda-developers.com
How to flash a Generic System Image (GSI) on Project Treble supported devices
So your device supports Project Treble, what does that mean for you? It means you can flash a Generic System Image such as LineageOS or Resurrection Remix! Enjoy AOSP-based custom ROMs! Here's a guide on how to install these ROMs.
www.xda-developers.com
Click to expand...
Click to collapse
Yes i understand, I will try to flash them and tell you what happens.
don't forget full TWRP backup to PC
DSU Sideloader for gaining temporary/permanent root, testing GSI's or installing GSI's Semi-permanently, pulling boot image, AND making your backups
Hello, I just wanted to post this as an answer to many questions regarding not being able to use DSU to install a GSI for testing or gaining root. The DSU install in developer options is NOT what we are using for installing GSI's temporarily for...
forum.xda-developers.com
Huawei Partition Kit - Enlarge system partition
Huawei Partition Kit This kit allows you to enlarge/reduce (2Go->5Go) the system partition on a Huawei kirin 65x, 960 or 970 phone. You can do it from a Huawei android 9 rom, a Lineage 18.1, 19.1, 20, or an AOSP 11,12 or 13. The kit reinstalls...
forum.xda-developers.com

Asus Zenfone 6/6Z - 5G Unlock, Video Call/ViLTe - Use in 2023

In 2023, this device is still capable of 5G and video call over cellular network. So What are the things can we do now ?
Capable Features :
Processor : Snapdragon 855
Cellular Modem-RF
Modem Name: Qualcomm® Snapdragon™ X24 LTE modem, Qualcomm® Snapdragon™ X50 Modem-RF System, Qualcomm® QTM052 5G mmWave antenna module
Peak Download Speed: Up to 2 Gbps
Peak Upload Speed: Up to 316 Mbps
Check Details on Official Website Click here
Operating System We are having right now are:
Stock Rom : Available Android 11 Last Update was on - 06/08/2021 - Version 18.0610.2106.156 Click here
Custom Rom : Available Android 13
1. Bliss Rom - Last Update on - 12-1-2023 version 16.3 Click here
2. Omni Rom - Last Update on - 15-1-2023 Version Omni13 Click here
discussion and updates
testing is on
CORE iT said:
In 2023, this device is still capable of 5G and video call over cellular network. So What are the things can we do now ?
Capable Features :
Processor : Snapdragon 855
Cellular Modem-RF
Modem Name: Qualcomm® Snapdragon™ X24 LTE modem, Qualcomm® Snapdragon™ X50 Modem-RF System, Qualcomm® QTM052 5G mmWave antenna module
Peak Download Speed: Up to 2 Gbps
Peak Upload Speed: Up to 316 Mbps
Check Details on Official Website Click here
Operating System We are having right now are:
Stock Rom : Available Android 11 Last Update was on - 06/08/2021 - Version 18.0610.2106.156 Click here
Custom Rom : Available Android 13
1. Bliss Rom - Last Update on - 12-1-2023 version 16.3 Click here
2. Omni Rom - Last Update on - 15-1-2023 Version Omni13 Click here
discussion and updates
testing is on
Click to expand...
Click to collapse
Hi there!
Good to have some info here.
Thing is that despite being on the latest A13 version of Omnirom, I cannot even get the VoLTE service working properly, though.
Yes that's why I am currently testing on stock Android 11 baseband version to work properly . Will update further soon.
Can Any one provide me a carrier_policy.xml of Oneplus 7 Pro 5G
CORE iT said:
Can Any one provide me a carrier_policy.xml of Oneplus 7 Pro 5G
Click to expand...
Click to collapse
Perhaps we could try to address such kind request in Oneplus 7 Pro forum?

Categories

Resources