Develop Bugs

[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.

[Q] Zip flashing problems

Hi all,
I'm trying to replace the font on bubor's CM11 ROM by means of flashing one on of the ZIPs available at http://forum.xda-developers.com/goo...-fontster-betas-flashable-font-packs-t2513985
I am using bubor's TWRP v2.7.1.
The problem I first encountered when trying to flash a font was the error message "Error executing updater binary" and thus the flashing "Failed". Based on the advice at http://forum.xda-developers.com/showthread.php?t=2290009 , I figured it would probably be a good idea to replace the update-binary with the one found in my ROM's ZIP, so I did that.
However, the ZIP still doesn't flash. Although I no longer get the "Error executing updater binary" message, now TWRP simply tells me "Error flashing zip" without offering me any explanation.
Please can you help with this, and apologies for the noob question. I have tried installing the ZIP from both internal and external SD. My SD's are swapped - could that have something to do with it?

- downlaoded http://www.mediafire.com/download/40x5qm44a24p0dg/CantarellFontPack.zip
- downlaoded http://dualhoki.vim.hu/bubor/dev/keyboard-light.zip
- replace update-binary ( copy from keyboard-light.zip)
- install
no error.
Would you be more detailed what did you use with what, please.

bubor said:
- downlaoded /CantarellFontPack.zip
- downlaoded keyboard-light.zip
- replace update-binary ( copy from keyboard-light.zip)
- install
no error.
Would you be more detailed what did you use with what, please.
Click to expand...
Click to collapse
I'm sorry for not being detailed enough.
I tried following your steps but unfortunately the flashing still failed. I eventually got it to work after a combination of actions, but I think the most crucial one was changing the write permissions of the \system\fonts folder from "drwxr-xr-x" to "drwxrwxrwx".
Thanks for your efforts in any case, I really appreciate all the work you're doing.

[DEV][Rom][5.1.1] e700h stock deodexed

I'm not a developer but I'm building a deodexed version of the e700h stock 5.1.1
This is my first rom and I'm using SuperR's Kitchen for linux which can almost do all the Job
After creating an initial flashable zip and trying to flash it using TWRP by nepalbiraj
When flashing, I got an error that the installer cannot mount /dev/block/bootdevice/by-name/system as its not available or not found
Please find attached META-INF files
if anyone can check the updater script and tell me where the mistake is
thank a lot

META-INF files
Files re-attached due to upload error

Can anyone help me with some options that I still not aware of ?

Try this! https://drive.google.com/file/d/0B_8xPQyhA4WxNFk1SWlpYjEtVFU/view?usp=docslist_api

hashiesh said:
Can anyone help me with some options that I still not aware of ?
Click to expand...
Click to collapse
hashiesh use the mmcblk for mounting the partitions. It would be dev/block/mmcblk

was it a successfull one
Did u succeed in deodex process
if yes please send me the meta inf files
thanks

Instead of trying to flash by-name, try:
dd if=/PATH/to/your/img of=/dev/block/mmcblk0p16 (boot partition)
mmcblk0p17 (recovery partition)
Double check that I have the partitions correct. At a terminal emulator: ls -aln /dev/block/platform/7824900.Which/by-name

{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.