Develop Bugs

[Q] Problems to install cm7

Hi,
I'm having problems to install cm7 port. First of all, i would like to thanks Alquez by the great job he's done in this port.
And now, my problem. When i try to install cm7 from recovery, and after wipe data, cache and all, i select install from zip, and when start the proces i obtain this error message:
I've checked the zip md5sum, and i don't obtain the same result indicated by Alquez. I tried downloading the file several times, even downloading it from the different available servers, and I always get the same md5, being different to that indicated by Alquez.
I don't know what to do. Can anyone, that have the correct file, upload it to another server?. Or i'm doing anything wrong?
Thank you very much.

the error message
Sorry,
The error message is:
Installing update.....
assert failed: getprop("ro.product.device")=="marvel" ||getprop("ro.build.product")=="marvel" || getprop(ro.product.board") =="marvel"
E: Error in /sdcard..../update-cm-7.2.0.RC0....zip (Status 7)

What version of CWM do you use? Make sure you are using the version that alquez posted on development section
Sent from my A953

The md5sum of the current version (2011-12-16) doesn't match.
$ md5sum -c update-cm-7.2.0-RC0-marvel-KANG-signed.zip.md5
update-cm-7.2.0-RC0-marvel-KANG-signed.zip: FAILED
md5sum: WARNING: 1 computed checksum did NOT match

I'm using CWM version 3.2.0.1_xda.cn.
I'll try to install ClockworkMod Recovery v.5.0.2.6 and i'll try to flash CM7 port again.
Thanks for replies. I'll post the results of this try.

Problem solved
OK,
Finally I've could install CM7 on my wildfire s. The problem was at the CWM i was using.
I've installed the new version (5.0...) and the problem was solved.
Thank you all.
Sorry if my english is not very good.

[MOD] DSIXDA kitchen Support for One X

Hi All,
I have create template to be used with DSIXDA kitchen. Hopefully you will find it useful.
Just rename the file to endeavoru and then place the file in tools\edify_defs and use all the kitchen power without manual editing

theintelligent said:
Hi All,
I have create template to be used with DSIXDA kitchen. Hopefully you will find it useful.
Just rename the file to endeavoru and then place the file in tools\edify_defs and use all the kitchen power without manual editing
Click to expand...
Click to collapse
This is the thing I wanted thanks
Sent from my HTC One X using xda app-developers app

thank you a lot!

did you need to change the update binary our update script in /update_files/ folder to ?
can you attach that correct files to please?
because i still get errors when flashing rom :\
thanks

ruizit0 said:
did you need to change the update binary our update script in /update_files/ folder to ?
can you attach that correct files to please?
because i still get errors when flashing rom :\
thanks
Click to expand...
Click to collapse
You don't need to do anything, just let the kitchen build the update-script, convert it to updater-script + its binary during ROM building.

theintelligent said:
Hi All,
I have create template to be used with DSIXDA kitchen. Hopefully you will find it useful.
Just rename the file to endeavoru and then place the file in tools\edify_defs and use all the kitchen power without manual editing
Click to expand...
Click to collapse
So just remove the extension and we can build a working rom for HTC One X?
Since it says no ROM support on the kitchen page.
Thx for your effort!

Yes you are right

Rom wont flash for some reason - getting status 0 error. Kitchin faq says thats from having update instead of updater script, but i do have updater and binary. Any ideas?
Ta.

backfromthestorm said:
Rom wont flash for some reason - getting status 0 error. Kitchin faq says thats from having update instead of updater script, but i do have updater and binary. Any ideas?
Ta.
Click to expand...
Click to collapse
When building the rom you have to choose Edify or updater script.

theintelligent said:
When building the rom you have to choose Edify or updater script.
Click to expand...
Click to collapse
Yeah I know, I did that, the problem was the file extension was left on the file, strange I deleted it, but set the extensions to visable in windows and there it was still on there.
So all sorted. Thanks.

Thank you this is very usefull!
For those who use DSIXDA kitchen, check out my thread here

i dont know what im doing wrong here.. im getting this error
E: Error in /sdcard/Arquivo/roms/MIUI_X/MIUI_X_2.9.21_RC1.zip
(Status 6)
Installation aborted.
ill descrive my steps
1. Copyed endeavoru (without .txt extension) to tools/edify_defs/
2. Extracted ROM and converted updater-script to update-script like kitchen recomends
3. Made my changes
4. Builded ROM in interactive mode (1) in kitchen
5. Kitchen converted automaticaly to updater-script
6. Selected option "Proceed: updater-script and update-binary will be moved to the ZIP file.."
7. sign, copy to phone, etc
and when i go to flash it, i got that error ...
i tryed the l3inky pack above, but with no sucess to .. :|
EDIT:
btw i founded this on changelog
Version 0.190 (March 26, 2012):
Change end-of-line characters in update(r)-script to proper format when building ROM. This gets done in case a noob modified the file with non-Unix compliant editor. Prevents 'Status 6' error when flashing ROM in custom recovery.
so ..its suposed to be fixed my error .. but its not fixed .. and the more strange i didnt edited any file (update / updater / etc)
weird

ruizit0 said:
i dont know what im doing wrong here.. im getting this error
E: Error in /sdcard/Arquivo/roms/MIUI_X/MIUI_X_2.9.21_RC1.zip
(Status 6)
Installation aborted.
ill descrive my steps
1. Copyed endeavoru (without .txt extension) to tools/edify_defs/
2. Extracted ROM and converted updater-script to update-script like kitchen recomends
3. Made my changes
4. Builded ROM in interactive mode (1) in kitchen
5. Kitchen converted automaticaly to updater-script
6. Selected option "Proceed: updater-script and update-binary will be moved to the ZIP file.."
7. sign, copy to phone, etc
and when i go to flash it, i got that error ...
i tryed the l3inky pack above, but with no sucess to .. :|
EDIT:
btw i founded this on changelog
Version 0.190 (March 26, 2012):
Change end-of-line characters in update(r)-script to proper format when building ROM. This gets done in case a noob modified the file with non-Unix compliant editor. Prevents 'Status 6' error when flashing ROM in custom recovery.
so ..its suposed to be fixed my error .. but its not fixed .. and the more strange i didnt edited any file (update / updater / etc)
weird
Click to expand...
Click to collapse
Please post the recovery.log

theintelligent said:
Please post the recovery.log
Click to expand...
Click to collapse
hi!
the part of flashing
Code:
-- Installing: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
Finding update package...
I:Update location: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
Opening update package...
Installing update...
line 4 col 20: syntax error, unexpected STRING, expecting $end
1 parse errors
E:Error in /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
(Status 6)
Installation aborted.
and here's the full log
https://www.dropbox.com/s/f5b97a4tt2rlbqu/recovery.log
and here's the updater-script created by the kitchen
https://www.dropbox.com/s/7h8wl5a5vizen08/updater-script

Take That 0 Out Of Line 4 Of updater Script.

ruizit0 said:
i dont know what im doing wrong here.. im getting this error
E: Error in /sdcard/Arquivo/roms/MIUI_X/MIUI_X_2.9.21_RC1.zip
(Status 6)
Installation aborted.
ill descrive my steps
1. Copyed endeavoru (without .txt extension) to tools/edify_defs/
2. Extracted ROM and converted updater-script to update-script like kitchen recomends
3. Made my changes
4. Builded ROM in interactive mode (1) in kitchen
5. Kitchen converted automaticaly to updater-script
6. Selected option "Proceed: updater-script and update-binary will be moved to the ZIP file.."
7. sign, copy to phone, etc
and when i go to flash it, i got that error ...
i tryed the l3inky pack above, but with no sucess to .. :|
EDIT:
btw i founded this on changelog
Version 0.190 (March 26, 2012):
Change end-of-line characters in update(r)-script to proper format when building ROM. This gets done in case a noob modified the file with non-Unix compliant editor. Prevents 'Status 6' error when flashing ROM in custom recovery.
so ..its suposed to be fixed my error .. but its not fixed .. and the more strange i didnt edited any file (update / updater / etc)
weird
Click to expand...
Click to collapse
ruizit0 said:
hi!
the part of flashing
Code:
-- Installing: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
Finding update package...
I:Update location: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
Opening update package...
Installing update...
line 4 col 20: syntax error, unexpected STRING, expecting $end
1 parse errors
E:Error in /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
(Status 6)
Installation aborted.
and here's the full log
https://www.dropbox.com/s/f5b97a4tt2rlbqu/recovery.log
and here's the updater-script created by the kitchen
https://www.dropbox.com/s/7h8wl5a5vizen08/updater-script
Click to expand...
Click to collapse
Fixed the updater-script (just removed the 0 as mentioned on the above post)

theintelligent said:
Fixed the updater-script (just removed the 0 as mentioned on the above post)
Click to expand...
Click to collapse
thanks for the reply..
removing only the 0 i got another error (status 7)
Code:
-- Installing: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092612_125439_C1.zip
Finding update package...
I:Update location: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092612_125439_C1.zip
Opening update package...
Installing update...
script aborted: format() expects 4 args, got 3
format() expects 4 args, got 3
E:Error in /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092612_125439_C1.zip
(Status 7)
Installation aborted.
so i oppened the original updater to check and i see some diferences ...
kitchen converted updater
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p12");
original updater
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p12", "0");
i removed the 0 like we talked in previous post, and chaged that line to the same as original updater and now it works
so its supposed to be a kitchen bug ?
the strange thing is that in previous users are reporting sucessefull cooking and flashing ... so why my kitchen isnt converting properly to updater script ?
i got the last kitchen 0.202 and the enderarvou file in place..
i already tryed to change update-binary in /update_files/ but its the same
now .. i know i can change mannualy the updater script before building the rom .. but i want to make it work like its supposed to work ...
can be my system configuration ? OS / cygwin / java ?
thanks

Ok!
Problem solved thanks to "backfromthestorm" hint!!
The problem is the Kitchen update to updater conversion.
The kitchen doesnt make correctly the conversion.
So the solution is:
not give any script to kitchen for conversion, remove META-INF folder from original zip and let kitchen create a fresh updater..

Hello
I keep getting an error ( status 0 ) even after edifying it . I chose edify in the kitchen and while flashing i get the error . Any help please what to do ?
Maybe the problem is when making the rom because it says signing update.zip . Any idea anyone ??

skywalker1162 said:
Hello
I keep getting an error ( status 0 ) even after edifying it . I chose edify in the kitchen and while flashing i get the error . Any help please what to do ?
Maybe the problem is when making the rom because it says signing update.zip . Any idea anyone ??
Click to expand...
Click to collapse
Did you read the FAQ?
What device? What version of kitchen? What did you modify? Etc.

[Q] flashing F4k's kernel

o/
Trying to flash F4k's awesome kernel here http://forum.xda-developers.com/showthread.php?t=2636890
(I'd post there but it won't let me before I have 10 posts).
I'm using ROM manager: Install ROM from SD card - I select the zip from my SD card - confirm.
However, it doesn't seem to work. What seems to happen is that wlan configuration files (system/etc/firmware/wlan/prima/) do flash, but kernel remains unchanged. Options - About Device says that kernel version is 3.4.0-1266356 which is what my Mini came with.
As a result I end up with old kernel and broken wlan.
Recovery does report that "some operations fail". Attaching recovery.log
Halp? Am I doing this wrong? Should I apply the .zip using some other tools?
Thanks!
[edit] attachment is invisible (yet?) so here's an alternative copy of recovery.log: https://www.dropbox.com/s/7g2378naa4bhbdy/recovery.log

sysKin said:
o/
Trying to flash F4k's awesome kernel here http://forum.xda-developers.com/showthread.php?t=2636890
(I'd post there but it won't let me before I have 10 posts).
I'm using ROM manager: Install ROM from SD card - I select the zip from my SD card - confirm.
However, it doesn't seem to work. What seems to happen is that wlan configuration files (system/etc/firmware/wlan/prima/) do flash, but kernel remains unchanged. Options - About Device says that kernel version is 3.4.0-1266356 which is what my Mini came with.
As a result I end up with old kernel and broken wlan.
Recovery does report that "some operations fail". Attaching recovery.log
Halp? Am I doing this wrong? Should I apply the .zip using some other tools?
Thanks!
[edit] attachment is invisible (yet?) so here's an alternative copy of recovery.log: https://www.dropbox.com/s/7g2378naa4bhbdy/recovery.log
Click to expand...
Click to collapse
What ROM are you using?
Installation is suppose to be simple with CWM:
1. Boot to CWM
2. Wipe cache and dalvik cache
3. Install kernel ZIP (do not extract the zip or modifiy it)
4. Reboot.

TNCS said:
What ROM are you using?
Click to expand...
Click to collapse
Stock.
By which I mean I9195TDVUAMH1, the stock for Australian I9195T.
Should be fine, right? Or did I misunderstand?
TNCS said:
Installation is suppose to be simple with CWM:
1. Boot to CWM
2. Wipe cache and dalvik cache
3. Install kernel ZIP (do not extract the zip or modifiy it)
4. Reboot.
Click to expand...
Click to collapse
Yup, that's effectively the same thing I did (only I used ROM Manager app to avoid pressing volume down button lol). Fails on the same assert and produces that same recovery.log as I've shared.
minzip: Can't create containing directory for "/system/etc/init.d/90hardlimit": Not a directory
set_perm: chown of /system/etc/init.d/90hardlimit to 0 0 failed: Not a directory
set_perm: chmod of /system/etc/init.d/90hardlimit to 755 failed: Not a directory
script aborted: set_perm: some changes failed
Click to expand...
Click to collapse
Looking at this, should the script mkdir /system/etc/init.d? Or should I simply do it beforehand? It's not there on my stock filesystem.

sysKin said:
Stock.
By which I mean I9195TDVUAMH1, the stock for Australian I9195T.
Should be fine, right? Or did I misunderstand?
Yup, that's effectively the same thing I did (only I used ROM Manager app to avoid pressing volume down button lol). Fails on the same assert and produces that same recovery.log as I've shared.
Looking at this, should the script mkdir /system/etc/init.d? Or should I simply do it beforehand? It's not there on my stock filesystem.
Click to expand...
Click to collapse
I assume you have rooted your phone.. I have no idea why it does that, I think you should redirect the quuestion at F4k's post for stock ROM.

TNCS said:
I assume you have rooted your phone.. I have no idea why it does that, I think you should redirect the quuestion at F4k's post for stock ROM.
Click to expand...
Click to collapse
Thanks for your help TNCS. Five more posts and I'll be able to post in that thread
In the meantime I hope F4k doesn't mind a private message.

Ubuntu Touch for Samsung Galaxy Tab 10.1 Edition 2014 SM-P605

Hi,
i have install TWRP v2.8.0.0. I have several zip file install. Durin the Installation i see the following error messages. For example, I installed the following file over the TWRP Install Button.
Code:
quantal-preinstalled-phablet-armhf.zip
and
Code:
quantal-preinstalled-armel+manta.zip
Code:
Updating partition details...
E:error opening '/data/ubuntu/dev/rmai11'
E:error: Not a directory
E:error opening !/data/ubuntu/dev/ram9'
E:error: Not a directory
. . .
I have no answer to the error messages.
Can you help me?
Advance many thanks for your support.
Love greeting of
Stefan Harbich

Hello everyone,
shame that still nobody has reported. I have indeed managed to install TWRP v.2.8.0.0, but I have the Android OS 4.2.2 somehow uninstalled when the wipe command. Now I have no OS on my tablet. Well, all for over a week. I just tested a Flash Boot ZIP file to the Android version 4.2.2 Least again, to be able to install on TWRP. Different ZIP's from the XDA developers could not be installed. Either because the zip could not be installed or the possible Ubuntu Toch Version.
I would be very happy if one of you could adopt my problem, because I have not been as conscientiously as you.
Advance for your support and warm Dankf
Kind regards Stefan Harbich

I have the same problem. I've tried to install Ubuntu on Samsung S3 and now in TWRP - whatever I do (install, backup..) - these errors accur
Btw, everything works, but there are about 30 lines of errors like this about missing directories.
Any ideas?

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*