Develop Bugs

[Q&A][UNOFFICIAL] CyanogenMod 12 Nightlies

Q&A for [ROM][UNOFFICIAL] CyanogenMod 12 Nightlies
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
Or I'm having other recovery issues.
A: Update your recovery to supported one. See the list below.
TWRP 2.8.1.2 ACE or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Where is my root?
A: http://www.cyanogenmod.org/blog/all-about-l-part-2 (Read under "Superuser where?")
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM12.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm12
cd cm12/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-12.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.

Thanks..reserved?
Sent from my ATRIX HD using Tapatalk

Home button not working. Have to use back button

Camera Bug
Camera is in the Apps not listen and it dont work from Lockscreen.
Sorry for my English and a big Thanks from Germany / EinfachAleks

No sounds.
---------- Post added at 11:32 AM ---------- Previous post was at 11:14 AM ----------
I don't have camera at all
Sent from my Desire HD using Tapatalk

Great job Tested on my Inspire 4G with alpha gaps all - so all works good but one problem at startup setting after ten minutus of thinking it cant set up my GSM career and tell me to set up it next time I'll think okay wait when all google sutups done ..... go to setting /mobile wireless/operator settings ... and at this moment I have a crash. I hawe an Ukrainian operator maybe this thing cause such problem Thank you a lot for you futer job at this rom And WiFi works greate ))))

For me the Home Key just working fine...im waiting for the next Snapshot

I'm gonna download zip again and flash again. Maybe bad flash.

Doge2 and recovery
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
With TWRP 2.8.1.0 it installs but these TKruzze gapps (https://s.basketbuild.com/devs/TKruzze/Android 5.0 GApps/Micro-Modular GApps/) gives error
E: Error executing update binary zip "gapps location.zip"
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
Finnaly old bug for me.
Does anyone have same problem like I do? I can't make partitions with TWRP 2.8.1.0 partition editor! With 4ext recovey I can make partition but with TWRP I can't.
http://forum.xda-developers.com/htc-desire-hd/help/qa-twrp-2-8-1-0-cwm-6-0-5-1-unofficial-t2952947

first i want to thank you for this amazing rom
and i want to ask if i update from doge 1 to doge 2 should i flash boot.img again after installing the rom

marek287 said:
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
http://forum.xda-developers.com/htc-desire-hd/help/qa-twrp-2-8-1-0-cwm-6-0-5-1-unofficial-t2952947
Click to expand...
Click to collapse
I have the same error

marek287 said:
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Try to format your system partition manually. If that doesn't help, contact 4EXT dev. Generally I can't fix recovery related issues like this seems to be.
marek287 said:
With TWRP 2.8.1.0 it installs but these TKruzze gapps (https://s.basketbuild.com/devs/TKruzze/Android 5.0 GApps/Micro-Modular GApps/) gives error
E: Error executing update binary zip "gapps location.zip"
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
Click to expand...
Click to collapse
You'll probably need even smaller gapps. Our system partition is getting very small as the base system size has increased a lot since gingerbread. I haven't tried any gapps yet as they are irrelevant to our roadblocker issues so I can't give any recommendations.
desire hd user said:
first i want to thank you for this amazing rom
and i want to ask if i update from doge 1 to doge 2 should i flash boot.img again after installing the rom
Click to expand...
Click to collapse
Yes, if you are S-ON. There are some kernel related changes which are included in the boot.img so it needs to be updated too.

Mustaavalkosta said:
Try to format your system partition manually. If that doesn't help, contact 4EXT dev. Generally I can't fix recovery related issues like this seems to be.
Click to expand...
Click to collapse
That was mine second throught but main goal was to anounce others that problem. I posted it to 4EXT recovery Q/A threat
http://forum.xda-developers.com/showpost.php?p=57171180&postcount=2
and recontacted (PM) to jrior001 TWRP recovery partition bug.

rom not working
help me. Excuse, but apparently I'm the only one that failed to install the rom.
during installation sticking a message like warnig and then something about the sound and would not start more
I've already checked MD5

DOGE2 + PA GApps ALPHA1 flash succeeded
Thank you Musta and the team for great job!
http://forum.xda-developers.com/showthread.php?p=56560109
I flashed DOGE2 + PA GApps ALPHA1, and they work fine.
(cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip + pa_gapps-micro-5.0-ALPHA1-20141117a-signed.zip)
Before flashing, I made .gapps-config which containing the text "NanoGApps", and placed it in the same folder as the GApps zip.
Then, flashing has succeeded.
I didn't try "PicoGApps" option, but it will also succeed, I suppose.

matbeta said:
help me. Excuse, but apparently I'm the only one that failed to install the rom.
during installation sticking a message like warnig and then something about the sound and would not start more
I've already checked MD5
Click to expand...
Click to collapse
Install TWRP 2.8.1.0 then install the rom again. http://forum.xda-developers.com/showthread.php?t=2780164

After downloading writes: "sim card added restart your device".

bratmarat said:
After downloading writes: "sim card added restart your device".
Click to expand...
Click to collapse
Yeah, it's a bit wonky. Just hit back to skip it for now. Telephony code is still undergoing some changes.

Very good job. I wait for doge3

hello Mustaavalkosta, Great job, say thanks to you and all the dev team.
I am chinese user, i found doge 3 always crash when i install most common app.
such as baidunews, baidu market, zhihu
please check it, hope doge 4 coming as soon as possible.

[Urgent] Locked out of phone because of some kind of catch 22

I was running a version of RR, earlier, camera did however not work so I thought that I should switch, the problem is that android determined to change my screen lock to something that I don't know of, I can use adb still to get around but there I get another error that says: "This package is for "OnePlus3"; this is a "oneplus3"

well for the error "this package is for..." you open your rom.zip file and go to META-INF--> com--> google-->android and open updater-script with a text editor and in the first line " then getprop..." change it from OnePlus3 to oneplus3

timrock7 said:
well for the error "this package is for..." you open your rom.zip file and go to META-INF--> com--> google-->android and open updater-script with a text editor and in the first line " then getprop..." change it from OnePlus3 to oneplus3
Click to expand...
Click to collapse
Thank you i tried and somehow got out of the annoying loop that occured, many thanks!

{LineageOS 14.1} Update failing

I am running lineageos-nightly-20170706 on my OnePlus 3 - I've tried to update it using both lineageos-nightly-20170803 and lineageos-nightly-20170810 - both give the same error when TWRP tries to install the file:
assert failed: op3.verify_modem('2017-06-27 21:43:31== "1"
updater process ended with ERROR: 7
Error installing zip file '/data/data/org.lineageos.updater/app_updates/lineage-14.1-20170810-nightly-oneplus3-signed.zip'
I did a full wipe and flash installing this, but I don't want to lose all the config work I've done if I don't have to - so I wanted to try updating this time. Am I doing something wrong or missing something? I download it, then choose Install - it reboots the pphone to TWRP (3.0.4-1), I click Install, then Up a Level so I can find the file in /data/data/org.lineagos.updater/app_updates, select the zip file, and swipe to install it.
Thanks,
Brian

bwgreen9 said:
I am running lineageos-nightly-20170706 on my OnePlus 3 - I've tried to update it using both lineageos-nightly-20170803 and lineageos-nightly-20170810 - both give the same error when TWRP tries to install the file:
assert failed: op3.verify_modem('2017-06-27 21:43:31== "1"
updater process ended with ERROR: 7
Error installing zip file '/data/data/org.lineageos.updater/app_updates/lineage-14.1-20170810-nightly-oneplus3-signed.zip'
I did a full wipe and flash installing this, but I don't want to lose all the config work I've done if I don't have to - so I wanted to try updating this time. Am I doing something wrong or missing something? I download it, then choose Install - it reboots the pphone to TWRP (3.0.4-1), I click Install, then Up a Level so I can find the file in /data/data/org.lineagos.updater/app_updates, select the zip file, and swipe to install it.
Thanks,
Brian
Click to expand...
Click to collapse
Firmware...

I am not an android expert - what do I need, and how do I apply it?

bwgreen9 said:
I am not an android expert - what do I need, and how do I apply it?
Click to expand...
Click to collapse
Well, your firmware is outdated, you need to update it.
This should help you out:
http://lmgtfy.com/?iie=1&q=Oneplus+3+modem+firmware+xda

bwgreen9 said:
I am not an android expert - what do I need, and how do I apply it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
I flashed this one in recovery 4.1.6 Firmware + Modem, and then i flashed the full zip of the lineage update.

When flashing my Gemini I get ERROR : Not Implement. (-1073676276) , MSP ERROE CODE :

I have flashed my Gemini once before and got it to dual-boot as Android or Debian, but I used a Windows computer to do that. I'm now using a Linux and when I run the Flash Tool it pops up an error
Code:
ERROR : Not Implement. (-1073676276) , MSP ERROE CODE : 0x00.
Still the application loads, but when I try to set the file paths as the instructions instruct, the error pops up again and doesn't set the file path. I could type it directly in case the error just has to do with the GUI but I'm nervous that the error might be deeper than that and flashing anyway will damage the phone. Any suggestions about what to do?

Development [ROM][13][UNOFFICIAL][alioth] PixelExperience for Redmi K40/Poco F3/Mi 11X [AOSP]

Hello,
After a lot of work done by lzgmc, jayanthk and after some tests, I have built an unofficial continuation of PE for alioth.
Motivation:
- I have the device and wanted to have last security patches
- I want to have Netflix, Google Wallet, McDonald app working
- because of lzgmc's and JayanthKandula's hard work, needed changes were reduced to minimum
Changes:
- Updated binaries from the most recent global alioth image
- All updates from PixelExperience, including security updates
- Share the same kernel as munch
Changelog:
05.2023
- small kernel updates
- small performance and ui tweaks
04.2023
- use updated drivers from the most recent version of MIUI Global 14.0.4.0
- use current 4.19 kernel instead of old one
- performance and ui tweaks
Images:
PE - Alioth - Google Drive
drive.google.com
Sources:
https://gitlab.com/lukasz1992-pe/
Instruction:
- you have to flash 05.2023 full image first, if you were on different image
For every next incremental update:
- allow system to boot after flashing
- then reboot to recovery
- flash incremental update
FAQ:
Q: Do you have the device?
A: Yes, I use my ROM on my device
Q: How to report bugs?
A: Write about them here
Q: I do not trust your builds
A: No problem, build image yourself from source or just do not use this rom
Q: What about official support?
A: My ROM is not official (depsite OFFICIAL in name of images). There is already an official maintaner, but has not released images yet.
Q: Why automatic updates are not working?
A: Because alioth is not officially supported, I support it unoficially. Maybe I add updates to my repo.
Q: Why do you publish incremental updates
A: They take less space on my Google Drive and are easier to flash
Q: I want to install 05.2023 (and newer) images directly
A: Flash 04.2023 version first, then install incremental updates one by one (as described in description above)
Q: Incremental update does not work
A: Make sure you are on the correct image, follow the order and allow to boot system after each flash (do not try to flash >1 image without reboot)
Q: Is this a vendor-boot ROM?
A: No
Q: Is there any guarantee?
A: xD

You accidentally used the Question-tag for this thread

Hi, I'm on the 20230420-1753 build but when I try to adb sideload the from-20230420-1753-to-20230516-2127 update I'm getting this error, I'm using the provided recovery image:
Code:
Supported API: 3
Finding update package...
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1.
Installation aborted.
I also tried with OrangeFox Recovery, I didn't get this error there but upon reboot I noticed that my version number didn't change.
Also, thanks a lot for keeping PE on the Poco F3 alive, I briefly tried MIU14 but I found it too bloated for my taste.

Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?
Please also confirm you do not have magisk etc.?

lukasz_m said:
Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?
Please also confirm you do not have magisk etc.?
Click to expand...
Click to collapse
Sure, here they are: https://pastebin.com/M5kvav40 https://pastebin.com/VRkbgbvh
I also don't have magisk or anything like that installed.

[DELETED]

Okay, released a new, fixed update - I tested it, it should work

I flashed the new update and its been working fine, thanks for you work!

I flashed the full image on GDrive linked above - thanks very much, works really well. But I think I'm being a blind and can't see the May update? Where do I find that...

Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.

lukasz_m said:
Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.
Click to expand...
Click to collapse
Ah great, thought I was asking a stupid question
Thanks for all your work - had semi-retired my F3 and just bumped it from 12 to 13, its really fast and smooth.

Update - 2023.05 image was reuploaded

Sorry if this is a noob question. Is it possible to dirty flash to this 2023.05 from the latest official build?
And thx for keeping this device updated, really appreciate what you're doing here.

hi, yes - you can do it

Hey Lukasz,
thanks for this work you are doing for all of us.
I I'm on last OFFICIAL PE build from lzgmc and I'm tying to dirty flash with ADB your ROM.
I receive this error whenever I run the ADB sideload comand but Maybe I did something wrong...can you help me ?
Thanks in advance
My version is:
PixelExperience_alioth-13.0-20230119-0644-OFFICIAL
Enabled ADB.
Now send the package you want to apply to the device with "adb sideload <filename Supported API: 3
Finding update package...
Installing update... Step 1/2
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1. Installation aborted.
@lukasz_m

It happens when update was interrupted. I do not remember exact names, but please do from ADB:
mount /dev/block/by-name/metadata /metadata
rm -rf /metadata/ota*
reboot to recovery and try again

lukasz_m said:
mount /dev/block/by-name/metadata /metadata
rm -rf /metadata/ota*
Click to expand...
Click to collapse
Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.
I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device
Than what I have to do ?
thanks in advance for your time.

ciottaciotta said:
Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.
I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device
Than what I have to do ?
thanks in advance for your time.
Click to expand...
Click to collapse
First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above

blonderulez said:
First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above
Click to expand...
Click to collapse
OK thnaks for the explanation...
After giving "mount /dev/block/by-name/metadata /metadata" command i get:
"mount: bad /etc/fstab: No such file or directory"
When I try to browse it with "cd" and "ls" commands i can browse till /dev/block/by-name/ and I see metadata folder with "ls" than when i go for "cd metadata" i get this "/dev/block/by-name/metadata: Not a directory"

Does this work?
Code:
mkdir /tmp/metadata
mount /dev/block/by-name/metadata /tmp/metadata
rm -rf /tmp/metadata/ota*