Database Develop

Unofficial LineageOS 14.1 for ZE552KL and ZE520KL

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is a continuation of the work by Shakalaca. Currently not much will be different. It does have however the latest security Patches. I will be splitting my time between CM 14.1 and Lineage 15. If you have questions please ask. The Z017 should work with both versions, I am running the Z012(KE552KL) and it seems okay.
Prerequisites:
TWRP
Unlock Bootloader
What Works?
- No Major Issues
What's broken ?
You tell me
Download Links
ROM:
https://drive.google.com/drive/folders/0B9R9sRY5L3uiM055Z3ZYeF9MXzA?usp=sharing
TWRP:
https://drive.google.com/drive/folders/0B9R9sRY5L3uidzNmTmpzSWthMTQ
GAPPS:
http://opengapps.org/
Special Thanks @anhenrique @shakalaca
Source Code:
https://github.com/LineageOS-Zenfone3
XDA:DevDB Information
LineageOS 14.1 for ZE552KL and ZE520KL, ROM for the Asus ZenFone 3
Contributors
basenode, basenode
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Beta
Created 2017-08-31
Last Updated 2017-08-30

Changelog:
Aug 30 2017:
- Build Using Latest CM14.1 Sources (Android 7.1.2)
- Includes August Security Updates

I'll try it out sir. Considering I sat across from you for two days while you were dinkin around with it

Nice man Hope you can fix 60fps record bug

Is it 7.1.2?

sontranngoc said:
Is it 7.1.2?
Click to expand...
Click to collapse
Yes it is.

[email protected]
basenode said:
Yes it is.
Click to expand...
Click to collapse
Thank you. I'm installing. But why I cannot install a zip file from internal memory, it has no choice (I can do that with Xperia Z). I have to install by adb sideload instead.

sontranngoc said:
[email protected]
Thank you. I'm installing. But why I cannot install a zip file from internal memory, it has no choice (I can do that with Xperia Z). I have to install by adb sideload instead.
Click to expand...
Click to collapse
What Recovery are you using? I have TWRP and when I select install and navigate to /sdcard/ I am able to flash from internal

Can you insert ViperOS / ResurrectionRemix functions? How to lock the power menu and block fast access, both with the screen locked? This helps a lot when the cell phone is lost or stolen.

kiq1702 said:
Can you insert ViperOS / ResurrectionRemix functions? How to lock the power menu and block fast access, both with the screen locked? This helps a lot when the cell phone is lost or stolen.
Click to expand...
Click to collapse
I would like to keep this rom as stick as possible. I am open to Updating the existing ViperOS Rom for this device. I am one person so it might be difficult for me to support too many roms especially considering my personal desire to see oreo on this device. I will take a look @ Viper and see what I can do.

basenode said:
What Recovery are you using? I have TWRP and when I select install and navigate to /sdcard/ I am able to flash from internal
Click to expand...
Click to collapse
I cannot boot to TWRP:
fastboot flash recovery twrp-3.1.0-0-Z012-20170408-N.img
target reported max download size of 536870912 bytes
sending 'recovery' (21080 KB)...
OKAY [ 0.697s]
writing 'recovery'...
OKAY [ 0.135s]
finished. total time: 0.838s
...
..
fastboot reboot
rebooting...
finished. total time: 0.016s
After this command, the phone start normally, not into TWRP
---------- Post added at 01:54 PM ---------- Previous post was at 01:42 PM ----------
basenode said:
What Recovery are you using? I have TWRP and when I select install and navigate to /sdcard/ I am able to flash from internal
Click to expand...
Click to collapse
I can boot into TWRP, but after wipe cache, system, dalvik, i install the zip file, it shows the error:
Can't install this package on top of incompatible data
Updater process ended with ERROR: 7
Error installing file 'zip ......'

sontranngoc said:
I cannot boot to TWRP:
fastboot flash recovery twrp-3.1.0-0-Z012-20170408-N.img
target reported max download size of 536870912 bytes
sending 'recovery' (21080 KB)...
OKAY [ 0.697s]
writing 'recovery'...
OKAY [ 0.135s]
finished. total time: 0.838s
...
..
fastboot reboot
rebooting...
finished. total time: 0.016s
After this command, the phone start normally, not into TWRP
---------- Post added at 01:54 PM ---------- Previous post was at 01:42 PM ----------
I can boot into TWRP, but after wipe cache, system, dalvik, i install the zip file, it shows the error:
Can't install this package on top of incompatible data
Updater process ended with ERROR: 7
Error installing file 'zip ......'
Click to expand...
Click to collapse
Hi!
This will solve your problem.:
1- Open the ROM with Winrar;
2- Go to: META-INF -> com -> google -> android;
3- Run the "updater-script" file with Notepad ++;
4- Delete the first 1 line, save and update the file in ROM;
Update your TWRP from main Zenfone 3 folder: https://mega.nz/#F!kl8lmKRL!ZbLvz1b4YgLMr_n09vRrTA (twrp-3.1.1-0-Z017-20170826.img)

ToDream said:
Hi!
This will solve your problem.:
1- Open the ROM with Winrar;
2- Go to: META-INF -> com -> google -> android;
3- Run the "updater-script" file with Notepad ++;
4- Delete the first 1 line, save and update the file in ROM;
Update your TWRP from main Zenfone 3 folder: https://mega.nz/#F!kl8lmKRL!ZbLvz1b4YgLMr_n09vRrTA (twrp-3.1.1-0-Z017-20170826.img)
Click to expand...
Click to collapse
Thanks. I have installed successfully.
We have to remove 2 BELOW RED LINE, NOT FIRST 1 LINE:
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
The first line will check for products, I saw that line already included Z017 and Z012, it's not a problem.

sontranngoc said:
Thanks. I have installed successfully.
We have to remove 2 BELOW RED LINE, NOT FIRST 1 LINE:
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
The first line will check for products, I saw that line already included Z017 and Z012, it's not a problem.
Click to expand...
Click to collapse
Actually it depends on the program that you will use to edit, using Notepad ++ you delete only this line of verification.
Follows attached

RobinRo said:
Nice man Hope you can fix 60fps record bug
Click to expand...
Click to collapse
@kyle_l88 and I are working on it but I can't make and promises

Battery Issues
Hi, I am having a lot of battery drain from LineageOS. "LineageOS System" is taking 27% and "Android OS" is taking up 24%. I have battery optimization on for everything possible, and I have battery saving kick in at 25%. My location services are on battery saving, and Bluetooth and WiFi are off. I probably have a screen on time for 1 to 2 hours, so I should end the day with a lot more than I have. Also, double tap to wake isn't working for me as well.

So far everything seems pretty great. Had a couple force close issues. The camera certainly doesn't support 60FPS recording on 1080p yet. But i am working on that part of the code. Otherwise there seems to be few, if any, issues. High five! :good:

jyao6429 said:
Hi, I am having a lot of battery drain from LineageOS. "LineageOS System" is taking 27% and "Android OS" is taking up 24%. I have battery optimization on for everything possible, and I have battery saving kick in at 25%. My location services are on battery saving, and Bluetooth and WiFi are off. I probably have a screen on time for 1 to 2 hours, so I should end the day with a lot more than I have. Also, double tap to wake isn't working for me as well.
Click to expand...
Click to collapse
I am running it on a test device and and looking at the battery life. I'll leave it on tonight also to see how it does. I don't think this version has doubletap to wake. I know there is double tap on statusbar for sleep.
I added an issue here for tracking: https://github.com/LineageOS-Zenfone3/android_device_asus_Z017/issues/2

jyao6429 said:
Hi, I am having a lot of battery drain from LineageOS. "LineageOS System" is taking 27% and "Android OS" is taking up 24%. I have battery optimization on for everything possible, and I have battery saving kick in at 25%. My location services are on battery saving, and Bluetooth and WiFi are off. I probably have a screen on time for 1 to 2 hours, so I should end the day with a lot more than I have. Also, double tap to wake isn't working for me as well.
Click to expand...
Click to collapse
Did you wipe everything before installing or dirty flash over the shakalaca ROM?

basenode said:
Did you wipe everything before installing or dirty flash over the shakalaca ROM?
Click to expand...
Click to collapse
No, I did not wipe it. This problem was also present in the most recent ROM from shakalaca if that helps.

[Recovery][P20/Pro][Unofficial]TWRP 3.2.1-0 [18/04/2018]

Disclaimer​This software comes with no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation​
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_clt_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features​
Internal storage decryption = working (if it pin/password, pattern fails then try by removing them (password, pin, pattern, fingerprint) from Android before booting to TWRP.
MTP and OTG connection = working
Backup&Restore = working
Note: This was tested only by few P20 Pro owners,so if you test it,please report back!There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9 forum.
Credits
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
Download links
twrp_clt_0.1.img - Decryption support (you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk not available for backup./vendor not available for backup (use /vendor_image instead)

Glad to see this. Any chance of sources or a pull request on my device tree to get decryption working?

hum.. it seem that decryption working great.
See :
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working

Yes. I was just asking for sources or a pull request on my Github repository. IMHO the decryption method used would be useful for anybody interested in ROM/Recovery development - and also required to comply with XDA licensing / GPL requirements.

a1Pha said:
Yes. I was just asking for sources or a pull request on my Github repository. IMHO the decryption method used would be useful for anybody interested in ROM/Recovery development - and also required to comply with XDA licensing / GPL requirements.
Click to expand...
Click to collapse
This is not based 100% from sources, i have another version with working decryption, which is based on open source tree, bur it's not ready yet, just private testing.
This is not breaking any GPL/XDA rule, because it's using just a dummy kernel, not compiled or modified by me! ?

Pretoriano80 said:
This is not based 100% from sources, i have another version with working decryption, which is based on open source tree, bur it's not ready yet, just private testing.
This is not breaking any GPL/XDA rule, because it's using just a dummy kernel, not compiled or modified by me! ?
Click to expand...
Click to collapse
Thanks for clarification. Would you mind sharing some details via PM with me? I'd be glad to improve my repo

a1Pha said:
Thanks for clarification. Would you mind sharing some details via PM with me? I'd be glad to improve my repo
Click to expand...
Click to collapse
Yes, no problem! Also have a look at my Github (pretoriano80). My goal is also to make a fully open source version. ?

Quote: Note: This was tested only by few P20 Pro owners,so if you test it,please report back!
Hi Pretoriano80, Hi All,
Great job ! Just installed... I confirm that it works on my CLT-L29 8.1.0.106(C432)
Internal storage decryption, MTP and usb OTG connection, Backup& Restore (incl /vendor_image) : All working !
Many thanks & Cheers

CLT-L09 (C782) all is working as it should, successful backup and mount of my 1tb hard drive.
Absolutely fantastic work
Thanks :good:

Well this is very positive.
Less than 2 calendar weeks from release to TWRP release.
I think we can possibly have pretty high expectations for development on the P20 Pro.

Hey im getting this when I attempt to run the fastboot flash recovery command:
C:\Users\andre\Desktop\twrp>fastboot flash recovery_ramdisk twrp_clt_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.151s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.171s
Can anyone advise please?

andrewglass3 said:
Hey im getting this when I attempt to run the fastboot flash recovery command:
C:\Users\andre\Desktop\twrp>fastboot flash recovery_ramdisk twrp_clt_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.151s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.171s
Can anyone advise please?
Click to expand...
Click to collapse
You have to unlock bootloader first!

Pretoriano80 said:
You have to unlock bootloader first!
Click to expand...
Click to collapse
Yep - I forgot that step - had the code but missed it out lol - Im an idiot lol

whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)

virtyx said:
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
Click to expand...
Click to collapse
Have you made sure that the Google Pay app is selected in the Magisk Hide list in the app? It doesn't tick automatically like it used to with Android Pay. You should pass safetynet with Magisk installed. Also, after flashing TWRP still passes safetynet too.

virtyx said:
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
Click to expand...
Click to collapse
TWRP has nothing to do with SafetyNet! Maybe you installed a firmware which didn't passed Google check yet.

Is this what I actually need to do to root my P20 Pro?
I unlock the bootloader, flash the twrp recovery, then install supersu.zip via twrp recovery and I'm done, right?
Or is there something else I left out?
Thank you very much so far!

m00h said:
Is this what I actually need to do to root my P20 Pro?
I unlock the bootloader, flash the twrp recovery, then install supersu.zip via twrp recovery and I'm done, right?
Or is there something else I left out?
Thank you very much so far!
Click to expand...
Click to collapse
Try Magisk instead of SuperSU. It has better support for Oreo than the latter.
BTW anyone here tried flashing Magisk to root the device?

DJBhardwaj said:
Try Magisk instead of SuperSU. It has better support for Oreo than the latter.
BTW anyone here tried flashing Magisk to root the device?
Click to expand...
Click to collapse
I did on the other TWRP thread, worked fine.

The page for getting an unlock code seems to 404 for me. Is this happening for anyone else too?

Cannot reboot to TWRP from system or perform OTA updates

Hello all,
I am pretty sure my problem has nothing to do with Carbon ROM, but one of the symptom I have is the unability to perform OTA update from CR-6.1, I ask for help here instead of on the ROM thread in case someone experienced the same :
- I used TWRP to flash CR-6.1 on a Z3C with TWRP. I unlocked the bootloader and flashed the recovery using fastboot (fastboot flash recovery xxx.img).
- CR-6.1 was properly flashed, boots without issues, but then if I try to reboot on recovery from here (using the power menu), the phone just reboots, and won't go to TWRP. Then it seems logical that when it tries to reboot on recovery to perform the OTA update it fails, since it just reboots to CR.
- My only was to access recovery is to press the down volume button while powering it up : It boots to TWRP successfully
- But then, if I try to manually flash the .zip file downloaded by the OTA, I get an error message (error 7): The devicename does not match, TWRP (official release 3.0.2-1) detects the phone as "". Note that with unofficial release 3.2.3-0 found here I get no error 7 message : The manual flash is successful.
I checked other posts here on XDA, one solution would be to just modify the device name in the .zip, then it works but I wonder if all these are not a symptom of an incorrect TWRP flash as recovery. I tried to reflash it from TWRP, unfortunately, it only proposes me to flash to boot. Flash to recovery is not available.
Thanks for your help!
Lionel

I'm dealing with this exact problem on my wife's phone. I've made progress though. First up, boot into bootloader, "adb reboot booloader", then boot into recovery, making sure you have a suitable twrp image on your desktop, "fastboot boot twrp-3.2.3.img". Now you're in TWRP, which is where I now am. I'm going to wipe the recovery partition, boot back into the bootloader and flash recovery. Let's see how that goes.
---------- Post added at 11:29 AM ---------- Previous post was at 10:59 AM ----------
Ignore the above, got it working. It seems that the version of CarbonRom is playing funny for some reason. Here's the recipe to fix things:
- On the phone, check and download the latest CarbonRom. Don't flash it.
- Run "adb reboot bootloader"
- Run "fastboot boot twrp-3.2.3.img"
- In TWRP, install the latest CarbonROM from sdcard/CarbonDelta
- Reboot
- Reboot back into bootloader, "adb reboot bootloader"
- Flash recovery, "fastboot flash recovery twrp-3.2.3.img"
- Run "fastboot reboot"
Everything is back the way it should be.

Good Morning,
I am the dev of the LineageOS 16 builds for this device and i have been working on a new TWRP tree. Therefore i have found some things according to you problem.
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this binary to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923

NeoArian said:
Good Morning,
I am the dev of the LineageOS 16 builds for this device and i have been working on a new TWRP tree. Therefore i have found some things according to you problem.
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this binary to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse
Hi NeoArian,
I've been away for a while and have just gotten back to playing with the z3c. I still have problems but that may just be my misunderstanding of things.
When the phone is in the bootloader, I update FOTAKernel thus:
Code:
fastboot flash FOTAKernel twrp-3.3.1-0.3-z3c.img
target didn't report max-download-size
Sending 'FOTAKernel' (13264 KB)...
OKAY [ 0.419s]
Writing 'FOTAKernel'...
OKAY [ 0.885s]
Finished. Total time: 1.322s
And update recovery too:
Code:
fastboot flash recovery twrp-3.3.1-0.3-z3c.img
target didn't report max-download-size
Sending 'recovery' (13264 KB)...
OKAY [ 0.421s]
Writing 'recovery'...
OKAY [ 0.878s]
Finished. Total time: 1.318s
Yet I'm unable to boot into recovery.
From the bootloader, I this is what I see if I try boot directly into recovery:
Code:
fastboot boot twrp-3.3.1-0.3-z3c.img
Downloading 'boot.img'
OKAY [ 0.419s]
booting
FAILED (remote: dtb not found)
Finished. Total time: 0.499s
I've read through quite a bit of the forum notes but still am no wiser. I do however much admire your work and that of others and the time you spend helping others.

Fudgemond said:
Hi NeoArian,
I've been away for a while and have just gotten back to playing with the z3c. I still have problems but that may just be my misunderstanding of things.
When the phone is in the bootloader, I update FOTAKernel thus:
Code:
fastboot flash FOTAKernel twrp-3.3.1-0.3-z3c.img
target didn't report max-download-size
Sending 'FOTAKernel' (13264 KB)...
OKAY [ 0.419s]
Writing 'FOTAKernel'...
OKAY [ 0.885s]
Finished. Total time: 1.322s
Click to expand...
Click to collapse
I now think this isn't correct. Work I've done on another phone (Xperia Z) suggests that unpacking CarbonROM and extracting the boot.img is what I should flash to FOTAboot. Something to try.

Did you manage to get twrp to work again? I want to move away from CR6.1 to LOS16 or 17 (just to give it a try), but I'm stuck now.

Development [ROM] LiteE RN10S Global 1.2

Hey guys, i present you one of my biggest projects so far:
LiteE RN10S Global!!!
This is probably the first MIUI mod for this device, althought it might not be the FIRST ROM, it's the FIRST MIUI MOD without that oversharpening effect. Keeping color schemes and everything working!
FEATURES:
Heavily Debloated
MIUI Dialer, contacts and messages (still uses google dialer for calling)
Removed a ton of tracers
Bootanimation from MIUI 12.5
Uses the chinese variant of Security Center and Miui Gallery
Mi Wallpaper with super wallpaper options
Voice Changer
Chinese Alpha Launcher
High-end icon animations
Genom Kernel by rama982 (on telegram)
and most importantly:
NO OVERSHARPENING!!! (don't worry i didn't delete PQ)
BUGS:
Mirror app doesn't work.
You tell me.
FIXES:
Reverted the MiuiAod for more stability
Added the Backup app back
Added the Mi Sound app back.
NOTES:
First boot may be laggy, don't worry, just set it up, and reboot.
CREDITS:
myst33d (on tg), for helping me a lot.
rama982 (on tg), for genom kernel.
@el0xren, for telling me about the app permissions.
And everyone else.
DOWNLOAD LINK:
Google Drive
Others will come soon.
KERNEL SOURCE: Here
ok but, how do we flash it?
REQUIREMENTS:
1. Unlocked bootloader.
2. Fastboot Drivers.
3. A brain.
Step by step:
1. Download the ROM, after it's done, extract it.
2. Rename the folder "LiteE". Nothing else.
3. Put your phone into fastboot mode, and execute the .sh (if you're on linux) or .bat (if you're on windows).
4. Wait until it finishes flashing, it will automatically reboot and close.
5. You're done!
ESPERIMENTAL:
There might be a way to flash this Mod without losing data. However this is not tested.
You need to already have MIUI Global 12.5.14 installed.
1. Same steps from before, but this time, execute the "flasher_no_userdata_md_udc" file.
Telegram Chats:
Support Group: https://t.me/LiteEDevelopmentGroup
Channel: https://t.me/LiteEDevelopmentChannel
​

Changelog:
- 1.3:
Working Mi Dialer with call recorder
New charging animation
Deodexed
Fixed flasher issue
I forgot
- 1.2.5:
Changelog in telegram
- 1.2:
MIUI Dialer, contacts and messages (still uses google dialer for calling)
Bootanimation from MIUI 12.5
Uses the chinese variant of Security Center and Miui Gallery
Chinese Alpha Launcher
High-end icon animations
- 1.1:
Never published on XDA
Added the vbmeta patcher in flasher script (this fixes that cannot boot into userspace error)
Changed boot sound and boot animation from Redmi Note 9T
MIUI Launcher Mod by Sipollo (removed)
High-end icon animations
Chinese version of Search (removed)
App Vault from MIUI 13 (removed)
Uses the chinese version of Mi Calendar (removed)
- 1.0:
Initial release

Wow nice., Hoping for more upcoming custom rom for our handset. Thanks

J6idot said:
Hey guys, i present you one of my biggest projects so far:
LiteE RN10S Global!!!
This is probably the first MIUI mod for this device, althought it might not be the FIRST ROM, it's the FIRST MIUI MOD without that oversharpening effect. Keeping color schemes and everything working!
FEATURES:
Heavily Debloated
Removed a ton of tracers
More colorful bootanimation
Uses the chinese variant of File Explorer, Security Center and Miui Gallery
Mi Wallpaper with super wallpaper options
Custom MiuiAod with "always on" function
Voice Changer
Genom Kernel by rama982 (on telegram)
and most importantly:
NO OVERSHARPENING!!! (don't worry i didn't delete PQ)
BUGS:
I have no idea how to test the Voice Changer function. Could anyone try this?
You tell me.
NOTES:
First boot may be laggy, don't worry, just set it up, and reboot.
CREDITS:
myst33d (on tg), for helping me a lot.
rama982 (on tg), for genom kernel.
@el0xren, for telling me about the app permissions.
And everyone else.
DOWNLOAD LINK:
Google Drive
Others will come soon.
KERNEL SOURCE: Here
ok but, how do we flash it?
REQUIREMENTS:
1. Unlocked bootloader.
2. Fastboot Drivers.
3. A brain.
Step by step:
1. Download the ROM, after it's done, extract it.
2. Rename the folder "LiteE". Nothing else.
3. Put your phone into fastboot mode, and execute the .sh (if you're on linux) or .bat (if you're on windows).
4. Wait until it finishes flashing, it will automatically reboot and close.
5. You're done!
ESPERIMENTAL:
There might be a way to flash this Mod without losing data. However this is not tested.
You need to already have MIUI Global 12.5.14 installed.
1. Same steps from before, but this time, execute the "flasher_no_userdata_md_udc" file.
Telegram Chats:
Support Group: not yet
Channel: https://t.me/LiteEDevelopmentChannel
​
Click to expand...
Click to collapse
big big work

Wow, Great work. Thanks. But is genome karnel stable?

Awesome work, might try it later

IamAlaminislam said:
Wow, Great work. Thanks. But is genome karnel stable?
Click to expand...
Click to collapse
yep

I can't seem to find the telegram channel for the genome karnel. Want to know the change log..

Can this work as a daily driver ROM? If anyone can post screenshots?
I had lost all hopes and already was planning to sell my 4 month old note10s.
If this can work as a daily driver ROM, I would keep the otherwise awesome device.

GildroY said:
Can this work as a daily driver ROM? If anyone can post screenshots?
I had lost all hopes and already was planning to sell my 4 month old note10s.
If this can work as a daily driver ROM, I would keep the otherwise awesome device.
Click to expand...
Click to collapse
why not? rom works perfectly fine

J6idot said:
why not? rom works perfectly fine
Click to expand...
Click to collapse
Thanks. Will try it out tonight

J6idot said:
why not? rom works perfectly fine
Click to expand...
Click to collapse
Getting the following error:
Code:
~/mnt/crucial/data/Phone/Note 10s/LiteE$ ./flasher.sh
product: secret
Step 1
Sending 'boot_a' (34128 KB) OKAY [ 1.233s]
Writing 'boot_a' OKAY [ 0.125s]
Finished. Total time: 1.371s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/21 (131064 KB) OKAY [ 3.708s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
There was a problem flashing the system.img.
Stuck into fastboot mode post this error.
Has anyone faced this issue?

GildroY said:
Getting the following error:
Code:
~/mnt/crucial/data/Phone/Note 10s/LiteE$ ./flasher.sh
product: secret
Step 1
Sending 'boot_a' (34128 KB) OKAY [ 1.233s]
Writing 'boot_a' OKAY [ 0.125s]
Finished. Total time: 1.371s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/21 (131064 KB) OKAY [ 3.708s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
There was a problem flashing the system.img.
Stuck into fastboot mode post this error.
Has anyone faced this issue?
Click to expand...
Click to collapse
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.

J6idot said:
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.
Click to expand...
Click to collapse
Will try again tonight post work. Many thanks.
J6idot said:
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.
Click to expand...
Click to collapse
Worked like a charm!!
Thanks a ton.

In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.

angel495 said:
In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.
Click to expand...
Click to collapse
yes yes, i already know about that green screen problem. The reason this happens is because of the custom MiuiAod. I will revert this in the next build.
And no, i'm not going to add miui dialer

J6idot said:
yes yes, i already know about that green screen problem. The reason this happens is because of the custom MiuiAod. I will revert this in the next build.
And no, i'm not going to add miui dialer
Click to expand...
Click to collapse
Iam flash your rom over Indonesian where be miui phone and etc., And they stop working. I need call record and working aod. Can we solve this issue? And on stock rom phone does not go in to the deep sleep, then screen is off, cpu continue work on low frequency... How about this rom? (can see a battery chart?)

angel495 said:
Iam flash your rom over Indonesian where be miui phone and etc., And they stop working. I need call record and working aod. Can we solve this issue? And on stock rom phone does not go in to the deep sleep, then screen is off, cpu continue work on low frequency... How about this rom? (can see a battery chart?)
Click to expand...
Click to collapse
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.

J6idot said:
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.
Click to expand...
Click to collapse
Can you get advise about make a change for in system and vendor folder (its write protect)... I am try edit a build.prop file, but then i save changes file just gone and i need make a reflash.

angel495 said:
In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.
Click to expand...
Click to collapse
J6idot said:
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.
Click to expand...
Click to collapse
For call recording you can use axet's call recorder. It's available on fdroid and is working fine so far, for me, with this rom.

[RECOVERY] [m8qlul] [Stable] TWRP 3.7.0_9-0 for HTC One M8s

TWRP 3.7.0_9-0 for HTC One M8s
This recovery is still under development. I am not responsible for bricked phones etc.
Download link : https://github.com/Olricccc/android_device_htc_m8qlul_twrp/releases
New Version 1.0
* Fixed wrong device props. Now it should flash roms without a problem.
What's working​* Backup to internal/microSD
* Restore from internal/microSD
* ADB
* Backup/restore to/from external (USB-OTG) storage
* Backup/restore to/from adb
* Input devices via USB (USB-OTG)
* Set brightness
* Vibrate
* Screenshot
What's not working​* Encrypted backups
Source : https://github.com/Olricccc/android_device_htc_m8qlul_twrp
Kernel: Linux 3.10.x
Latest Build Version: Stable

Hi!
I wanted to give this recovery a shot, but there are no releases on the github page.
Could you make it public again?
Thank you in advance!
Sam

I updated the link. Sorry about that.

I'm trying to install it but I get this error:
C:\Windows\System32>fastboot flash recovery C:\twrp.img
error: write_sparse_skip_chunk: don't care size 8574976 is not a multiple of the block size 4096
Sending sparse 'recovery' 1/2 (16380 KB) error: write_sparse_skip_chunk: don't care size 8574976 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 8574976 is not a multiple of the block size 4096
OKAY [ 1.547s]
Writing 'recovery' FAILED (remote: 'image error! (BootMagic check fail)')
fastboot: error: Command failed
Do you know what is wrong?
Thanks!

Sorry for late reply. Try to flash with HTC fastboot. Normal fastboot causes errors, idk why. You can download it from htcdev.com . Choose unlock bootloader then choose your device and continue. Then go to step 4. You should see the download links.

You know what. Just download the attachment. Put the file to your platform-tools directory, then you're ready to go.

Thank you! With this fastboot it worked perfectly!
I have tried to flash your custom rom as well, but it lands me in a bootloop.
Are there special instructions I'm missing?
I'm wiping the dalvik and cache, then installing the rom, wiping again when asked, and then reboot.
Thanks in advance!

I have been trying to install both the lineages 16 and the android ice cold project 13.1 by the way.

Did you wiped your system, data and internal storage? It could result with bootloop if you didn't wiped everything. Wipe them all then try to install the rom. You don't need to wipe dalvik/cache after installation. At least, i don't wipe it. And im sure you were probably using the latest stock rom, but be sure that you were using 2.21.401.1 before the installation.
And please ask your questions about rom in the rom thread. This thread should be used only for recovery.