Database Develop

[FlashPatch] IncDoes flash-patch [v0.2] Nov-12th

BETA~
"Before you download please read 2nd post"
This is the first stage of flash-patch development, this will be used to get AOSP/Vanilla builds onto our INC's in an easy suitable way that fits us all. No more rebuilding or packing a whole new zip
I will be updating the patch as we get more fixes. v0.1 is released and you can grab them below.
Download AOSP FlashPatch v0.2:
http://ziggy471.com/incredibledoes/AOSP-FP-v0.2-signed.zip
Click to expand...
Click to collapse
What the patch does:
- flashes INC's necessary system files
- flashes INC's boot.img
What to come:
- Sense ROM support
Click to expand...
Click to collapse
How to install:
- download flash-patch (posted above)
- download an AOSP/Vanilla rom
- full wipe required
- flash the AOSP/Vanilla ROM but DO NOT REBOOT after install
- flash the patch over the AOSP/Vanilla ROM
- now reboot
That's pretty much it for now, later I will clean up the install and add more fixes to it... Please report back the ROM tested and/or if it failed.
ID
Click to expand...
Click to collapse

OKAY, this is a beta form flash-patch. This Patch will flash over any AOSP/Vanilla build "IF" the update/r-script is not asked to read the board of your device...?!
EXAMPLE:
- CyanogenMod builds have a getprop in the script which will not let you flash. If the script has something like this:
Code:
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
then the installation will fail because the board does not match.. you can simply edit these your selves by editing the update/r-script...
BEFORE:
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
AFTER:
assert(getprop("ro.product.device") == "inc" || getprop("ro.build.product") == "inc" || getprop("ro.product.board") == "inc");
Click to expand...
Click to collapse
You can test out AOSP/Vanilla ROMS from any device like Droid, Desire, EVO, Nexus etc... as long as the script does not require the 'getprop' then you should be fine.
PLEASE NOTE: No telling on which roms are supported, only way to find out is to look around the forums and give it a flash... If tested and worked please post ROM/Developer so I can update OP.
"HOW TO EDIT update/r-script" 2 different ways~
NOTE: There is 2 different scripts "update-script" and "updater-script" you will see that I write "update/r-script" because there of the two different scripts. Updater-script comes with an "updater-binary" I never edit the binary so you can leave it alone... just edit the update or updater-script.
Click to expand...
Click to collapse
1- unzip the downloaded ROM
2- open folder META-INF >> com >> google >> android >> update/r-script
3- Open the update/r-script using an xml reader (For WINDOWS use notepad++) (For LINUX use gedit) or something similar...
4- Change the getprop "<device>" to getprop "inc"
5- save and replace the old update/r-script with the one you just saved
6- sign .zip and flash (If I remember correctly Clockwork recovery does not need a signed update.zip so signing the .zip is not required)
Click to expand...
Click to collapse
1 easy step:
This is the easiest way to edit the update/r-script... Completely remove the "assert getprop"
~EXAMPLE from CyanogenMod for N1~
Before:
ui_print("Welcome to CyanogenMod-6.1.0-RC1-N1!");
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
assert(getprop("ro.bootloader") == "0.33.2012" ||
getprop("ro.bootloader") == "0.33.0012" ||
getprop("ro.bootloader") == "0.35.2017" ||
getprop("ro.bootloader") == "0.35.0017");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
show_progress(0.500000, 0);
format("MTD", "system");
mount("MTD", "system", "/system");
show_progress(0.500000, 40);
Click to expand...
Click to collapse
After:
ui_print("Welcome to CyanogenMod-6.1.0-RC1-N1!");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
show_progress(0.500000, 0);
format("MTD", "system");
mount("MTD", "system", "/system");
show_progress(0.500000, 40);
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you want to learn how to sign .zips follow this thread>>> http://forum.xda-developers.com/showthread.php?t=537937

0.2:
- fixed data
- cleaned install
- audio fixed
- build.prop edits
- tethering now works
0.1:
- initial release

you know, I just started using ShadowROM and am loving it! I finally found a great AOSP rom that works wonderfully for me exactly how I want it. I really thought that I was going to stop flashing roms every day finally because I found an AOSP that I love! And then BAM, I read this thread and my choices of roms to try and test just grew 10 times larger....Thank You ID, really...Thanks >0.
Haha, no just kidding. This patch is awesome, I can't wait to start finding and testing out ROMS for other devices. Way to go ID!

Yay! Just what I have been waiting for! This stuff pretty much opens up a whole new world of tinkering for us! Thanks ID!!!
2 questions before I screw up my night:
1. given that its supposedly hard to sign files if you just have macs... would toggling signature verification in ClockworkMod do away with the need to sign the file? **** delete ****
2. If I do create a nandroid of the ROM after flashpatching it, will it be restorable as normal or do I have to flashpatch it everytime i.e. does the flashpatch get embedded in the nandroid?
Thanks
EDIT: Just noticed Q1 answered in OP

khanam said:
Yay! Just what I have been waiting for! This stuff pretty much opens up a whole new world of tinkering for us! Thanks ID!!!
2 questions before I screw up my night:
1. given that its supposedly hard to sign files if you just have macs... would toggling signature verification in ClockworkMod do away with the need to sign the file? **** delete ****
2. If I do create a nandroid of the ROM after flashpatching it, will it be restorable as normal or do I have to flashpatch it everytime i.e. does the flashpatch get embedded in the nandroid?
Thanks
EDIT: Just noticed Q1 answered in OP
Click to expand...
Click to collapse
clockworkmod recovery.img Im pretty sure it does not need a signed.zip but if you use amon_ra then you need to sign the .zip
Q2: Nandroid will restore as normal, no need to re-apply the patch.

well, i thought i edited my getprop stuff but cyanogen 6.1 from nexusone failed due to getprop bootloader =0.33.2012 and a few others...

you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu

Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.

touchpro247 said:
Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.
Click to expand...
Click to collapse
dx has that ninjablur BS
this is only for aosp roms.

touchpro247 said:
Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.
Click to expand...
Click to collapse
Apparently I have stayed in the Inc area too much as I was just wondering if there are kitchens like their used to be for WinMo...

es0tericcha0s said:
dx has that ninjablur BS
this is only for aosp roms.
Click to expand...
Click to collapse
Ok, I'll just add the files needed to port it then. Thanks!

es0tericcha0s said:
you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu
Click to expand...
Click to collapse
Thanks!
So, obviously, Cyanogenmod for the Nexus works. Just removed the assert from the update/r script for both the bootloader and the device. Once that was fixed
1. install rom
2. run Inc's zip
3. ziggy kernel
4. Gapps
rebooted and running.
Not sure why, but wifi isn't working with it and I've tried the Kernels recommended in the Inc Cyanogen thread.

I got lithium mod to work using patch. Thank you.
Sent from my ADR6300 using XDA App

es0tericcha0s said:
you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu
Click to expand...
Click to collapse
oh wow! thanks man!

I get error 6 in clockwork recovery. I deleted the assert. When I opened update binary it wasn't in English just symbols so I didn't no what to edit. The error report say bad line on 62. Idk lituimmod ended up not working.
Sent from my ADR6300 using XDA App

papi92 said:
I get error 6 in clockwork recovery. I deleted the assert. When I opened update binary it wasn't in English just symbols so I didn't no what to edit. The error report say bad line on 62. Idk lituimmod ended up not working.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Just leave the binary alone...
ID

I didn't touch the binary and It still wouldn't install I get the same error.
Sent from my ADR6300 using XDA App

updated 2nd post with two ways to edit the script...

papi92 said:
I didn't touch the binary and It still wouldn't install I get the same error.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
reboot recovery

[Q] Can't flash apps from CWM

So, i'm having this issue with flashing apps such as superuser and cerberus on my Optimus 2x.
At first i just thought it might be an issue with the update itself (Only tried superuser at first) but now i wanted to check out cerberus, and it exhibits the same behaviour.
Basically it just says something like opening and installing update, then it goes "Error in <path to file> (Status: 0) installation failed" or something like that, and that is basically all there is to it.
CWM is version 4.4.0.7
CWM Recovery is version 5.0.2.0
And yes, i know i can just manually put it in /system/app if i want to, just really would want the convenience of automatically updating su and perhaps Cerberus, if i stick with that, everytime i flash a new nightly.

Let me guess, you're using a stock based ROM and ROM Manager to install them?
If so, then you'll want to either change your recovery to an 'internal' one, or boot to recovery and install them yourself.

Rusty! said:
Let me guess, you're using a stock based ROM and ROM Manager to install them?
If so, then you'll want to either change your recovery to an 'internal' one, or boot to recovery and install them yourself.
Click to expand...
Click to collapse
Thanks for your help, if by stock you mean LG-based rom, then no, i use CM7 currently on Nightly 148. Edit: Additionally i'm using VorkKernel (the one from the 21st) if that has any bearing on the issue.
It doesn't matter if i install from ROM Manager og Recovery, the result is the same, i'm not sure what you mean with an internal recovery, i just installed the one that CWM installed for me.

Also tried the new update for CWM that were supposed to fix 10% of install issues or something like that, still no luck though

If you're on CM7 then you don't want an internal recovery, unless you don't have an external SD card.

Rusty! said:
If you're on CM7 then you don't want an internal recovery, unless you don't have an external SD card.
Click to expand...
Click to collapse
I tried installing your recovery for external sd cards, still the same error, and yeah i do have an external sd card.

When did it start happening? It must have worked at some point as you have CM installed.

Rusty! said:
When did it start happening? It must have worked at some point as you have CM installed.
Click to expand...
Click to collapse
It only happens for apps (For example Superuser and Cerberus) CM flashes just fine, so does my kernel.

Well that's just bizarre then, if one thing works, they all should
If you go to advanced in recovery you get an options to display the log, might be worth doing that after it's failed at installing.

Rusty! said:
Well that's just bizarre then, if one thing works, they all should
If you go to advanced in recovery you get an options to display the log, might be worth doing that after it's failed at installing.
Click to expand...
Click to collapse
Well it starts up saying "Checking for extendedcommand" then "Skipping execution of extendedcommand. file not found"
Then it goes back to just showing the same log from the installation saying that there is an error in the file (status 0)
And nothing else.

Error status 0, I missed that, it means a problem with the updater-script.
Now, how old are these .zips? If they're not too new, they could use Amend scripts (instead of Edify that you need on CWM v3+), and you'll get that error. You can ignore the extended command bit, that's OK.

Rusty! said:
Error status 0, I missed that, it means a problem with the updater-script.
Now, how old are these .zips? If they're not too new, they could use Amend scripts (instead of Edify that you need on CWM v3+), and you'll get that error. You can ignore the extended command bit, that's OK.
Click to expand...
Click to collapse
The zips were downloaded today, superuser 3.0 can't be more than a few days old, don't know about cerberus though, the archive timestamp indicates 2008, but that doesn't make sense.

Rusty! said:
Error status 0, I missed that, it means a problem with the updater-script.
Now, how old are these .zips? If they're not too new, they could use Amend scripts (instead of Edify that you need on CWM v3+), and you'll get that error. You can ignore the extended command bit, that's OK.
Click to expand...
Click to collapse
Edit: Oops was meant to be an edit.
If it makes any difference here are their update scripts:
Cerberus:
Code:
show_progress(1.000000, 0);
ui_print("Mounting /system");
run_program("/sbin/busybox", "mount", "/system");
set_progress(0.125000);
ui_print("Mounting /data");
run_program("/sbin/busybox", "mount", "/data");
set_progress(0.250000);
ui_print("Deleting old APK from /system");
delete("/system/app/Cerberus.apk");
set_progress(0.375000);
ui_print("Deleting old APK from /data");
delete("/data/app/com.lsdroid.cerberus.apk");
delete("/data/app/com.lsdroid.cerberus-1.apk");
delete("/data/app/com.lsdroid.cerberus-2.apk");
set_progress(0.500000);
ui_print("Extracting files to /system");
package_extract_dir("system", "/system");
set_progress(0.625000);
ui_print("Unmounting /data");
unmount("/data");
set_progress(0.750000);
ui_print("Unmounting /system");
unmount("/system");
set_progress(0.875000);
ui_print("Installation complete!");
set_progress(1.000000);
Superuser:
Code:
ui_print("***********************************************");
ui_print(" Superuser 3.0 for Android 2.0-3.2");
ui_print("***********************************************");
show_progress(1.000000, 0);
ui_print(" Mounting SYSTEM...");
run_program("/sbin/busybox", "mount", "/system");
set_progress(0.100000);
ui_print(" Deleting SYSTEM:bin/su...");
delete("/system/bin/su");
set_progress(0.200000);
ui_print(" Deleting SYSTEM:xbin/su...");
delete("/system/xbin/su");
set_progress(0.300000);
ui_print(" Extracting files to SYSTEM...");
package_extract_dir("system", "/system");
set_progress(0.400000);
ui_print(" Setting SYSTEM:bin/su permissions to 6755...");
set_perm(0, 0, 6755, "/system/bin/su");
set_progress(0.500000);
ui_print(" Creating SYSTEM:xbin/su symbolic link...");
symlink("/system/bin/su", "/system/xbin/su");
set_progress(0.600000);
ui_print(" Unmounting SYSTEM...");
unmount("/system");
set_progress(0.900000);
ui_print("Install complete. Enjoy!");
set_progress(1.000000);

They're Edify scripts, so nothing wrong there. That's confusing.

Anyone else dares enter the fray?

Same issue here for cerberus, although on a different device (galaxy note, notecore v10.2, cleanote v4).
Has anyone found a solution for this?

Extract the updater-binary from your rom and replace the ones in the app zips.
Sent from my LG-P990 using xda app-developers app

Try disabling the Toggle Signature to disabled in CWM...
Sent from my LG-P999 using Tapatalk 2

[Q] problems in building rom

hey i m trying to learn to build a custom rom.
i m using dxida's kitchen for dat purpose
on building d rom n flashing it using cwm i get an error "error:status 7 mount() requires 4 args"
i found this in updater-script
Code:
mount("MTD", "system", "/system");
so i tried to updater scripts from another roms from development section
Code:
mount("rfs", "EMMC", "/dev/block/stl9", "/system");
but den my phone gets into bootloop
wat shld be d issue??
thanks in adv

Then You probably soft-bricked it

Yeah ...you've soft bricked it

andy_android said:
hey i m trying to learn to build a custom rom.
i m using dxida's kitchen for dat purpose
on building d rom n flashing it using cwm i get an error "error:status 7 mount() requires 4 args"
i found this in updater-script
Code:
mount("MTD", "system", "/system");
so i tried to updater scripts from another roms from development section
Code:
mount("rfs", "EMMC", "/dev/block/stl9", "/system");
but den my phone gets into bootloop
wat shld be d issue??
thanks in adv
Click to expand...
Click to collapse
Try to reflash the Firmware, altrough you will Lost everything

yeah i got dat one
but wat i want to knw is how to get d error??
logcat???

toterkeks said:
Try to reflash the Firmware, altrough you will Lost everything
Click to expand...
Click to collapse
what do u mean by lost everything???
i was able to revert back to stock

andy_android said:
hey i m trying to learn to build a custom rom.
i m using dxida's kitchen for dat purpose
on building d rom n flashing it using cwm i get an error "error:status 7 mount() requires 4 args"
i found this in updater-script
Code:
mount("MTD", "system", "/system");
Click to expand...
Click to collapse
Here the binary is telling you it needs 4 arguments (args) and you are only giving it 3 (1. "MTD", 2. "system" and 3. "/system") which is why you were getting the error. If it had of worked, I'm not sure what it would have done because MTD is the wrong partition type for our phone. You have to be a bit careful here because there is the possibility of hard-bricking your phone doing things like that. I think the kitchen does tell you somewhere that you need to edit the script if your phone doesn't have a YAFFS based filesystem.
andy_android said:
so i tried to updater scripts from another roms from development section
Code:
mount("rfs", "EMMC", "/dev/block/stl9", "/system");
but den my phone gets into bootloop
wat shld be d issue??
thanks in adv
Click to expand...
Click to collapse
This second one that you have used is correct so I can only assume it's another part of the script that's causing the problem. To be 100% sure you can also remove the mount command altogether and just use the menu options in CWM to make sure /system is mounted before flashing the ROM.
Also did you wipe data/cache before flashing the ROM?

Need help unpacking and repacking boot.img

Hey guys I'm working on a bigger problem but part of it is that I need to unpack and repack the boot.img.
I've tried it with abootimg and unmkbootimg, but in both cases the phone won't boot anymore after flashing the new boot.img, even if I've made absolutely no changes.
I'm on 6.0 (BR).
Would really appreciate it if anyone could help me out!

90180360 said:
Hey guys I'm working on a bigger problem but part of it is that I need to unpack and repack the boot.img.
I've tried it with abootimg and unmkbootimg, but in both cases the phone won't boot anymore after flashing the new boot.img, even if I've made absolutely no changes.
I'm on 6.0 (BR).
Would really appreciate it if anyone could help me out!
Click to expand...
Click to collapse
https://github.com/xiaolu/mkbootimg_tools if you are on Linux.

LuK1337 said:
https://github.com/xiaolu/mkbootimg_tools if you are on Linux.
Click to expand...
Click to collapse
Thanks a lot man!
Simply unpacking the boot.img, repacking and flashing works now!
What I noticed that while it provides me with both the compressed and decompressed ramdisk, it uses the compressed ramdisk when repacking. As I'd like to make changes to the ramdisk, what tools should I use compress?

90180360 said:
Thanks a lot man!
Simply unpacking the boot.img, repacking and flashing works now!
What I noticed that while it provides me with both the compressed and decompressed ramdisk, it uses the compressed ramdisk when repacking. As I'd like to make changes to the ramdisk, what tools should I use compress?
Click to expand...
Click to collapse
Just modify the extracted one, it'll compress it again and use it for boot.img creation.

LuK1337 said:
Just modify the extracted one, it'll compress it again and use it for boot.img creation.
Click to expand...
Click to collapse
Thanks man, you're a legend!
So what I'm actually trying to do is add a module to the kernel. What I did now is add its hash to module_hashes, which fixed the permissions issue.
Unfortunately, when I try to add it now, I get
Code:
[email protected]_udstv:/sdcard # insmod xt_HL.ko
insmod: failed to load xt_HL.ko: Exec format error
dmesg reveals
Code:
xt_HL: disagrees about version of symbol module_layout
As said, I'm on 6.0 stock (BR). To compile the module, I used the 5.0.2 source using "msm8226_defconfig".
It was probably very naive of me to think that this could actually work? I'm sorry this is all very new to me.

90180360 said:
Thanks man, you're a legend!
So what I'm actually trying to do is add a module to the kernel. What I did now is add its hash to module_hashes, which fixed the permissions issue.
Unfortunately, when I try to add it now, I get
Code:
[email protected]_udstv:/sdcard # insmod xt_HL.ko
insmod: failed to load xt_HL.ko: Exec format error
dmesg reveals
Code:
xt_HL: disagrees about version of symbol module_layout
As said, I'm on 6.0 stock (BR). To compile the module, I used the 5.0.2 source using "msm8226_defconfig".
It was probably very naive of me to think that this could actually work? I'm sorry this is all very new to me.
Click to expand...
Click to collapse
Rebuilt zImage and rest of modules and it /should/ work.
btw: http://unix.stackexchange.com/quest...sagrees-about-version-of-symbol-module-layout

I'm sorry that I have to bother you again.
LuK1337 said:
Rebuilt zImage and rest of modules and it /should/ work.
Click to expand...
Click to collapse
I compiled my new module together with the kernel and the other modules. When I replace the kernel file of the unpacked boot.img and then repackage and flash, I get thrown into recovery when trying to boot.
Did I misunderstand or is this what you were suggesting?
LuK1337 said:
btw: http://unix.stackexchange.com/quest...sagrees-about-version-of-symbol-module-layout
Click to expand...
Click to collapse
If I understand correctly, I should try to extract the Module.symvers file from the kernel and then use this to compile the new module? I've tried following this article.
When using extract-symvers, I get the following error:
Code:
$ python2 ./extract-symvers.py -B 0x00008000 kernel
Traceback (most recent call last):
File "./extract-symvers.py", line 139, in <module>
main()
File "./extract-symvers.py", line 135, in main
for s, crc, t in kernel.symbols():
File "./extract-symvers.py", line 101, in symbols
symsearch = self.scan_symsearch()
File "./extract-symvers.py", line 89, in scan_symsearch
unused = self.read_uint(off)
File "./extract-symvers.py", line 61, in read_uint
return struct.unpack(self.endian + 'I', self.kernel[offset:offset + 4])[0]
struct.error: unpack requires a string argument of length 4
This is the content of img_info:
Code:
kernel=kernel
ramdisk=ramdisk
dt=dt.img
page_size=2048
kernel_size=6902872
ramdisk_size=947793
dtb_size=1751040
base_addr=0x00000000
kernel_offset=0x00008000
ramdisk_offset=0x01000000
tags_offset=0x00000100
cmd_line='console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags movablecore=160M'
board=""
format=gzip

90180360 said:
I'm sorry that I have to bother you again.
I compiled my new module together with the kernel and the other modules. When I replace the kernel file of the unpacked boot.img and then repackage and flash, I get thrown into recovery when trying to boot.
Did I misunderstand or is this what you were suggesting?
If I understand correctly, I should try to extract the Module.symvers file from the kernel and then use this to compile the new module? I've tried following this article.
When using extract-symvers, I get the following error:
Code:
$ python2 ./extract-symvers.py -B 0x00008000 kernel
Traceback (most recent call last):
File "./extract-symvers.py", line 139, in <module>
main()
File "./extract-symvers.py", line 135, in main
for s, crc, t in kernel.symbols():
File "./extract-symvers.py", line 101, in symbols
symsearch = self.scan_symsearch()
File "./extract-symvers.py", line 89, in scan_symsearch
unused = self.read_uint(off)
File "./extract-symvers.py", line 61, in read_uint
return struct.unpack(self.endian + 'I', self.kernel[offset:offset + 4])[0]
struct.error: unpack requires a string argument of length 4
This is the content of img_info:
Code:
kernel=kernel
ramdisk=ramdisk
dt=dt.img
page_size=2048
kernel_size=6902872
ramdisk_size=947793
dtb_size=1751040
base_addr=0x00000000
kernel_offset=0x00008000
ramdisk_offset=0x01000000
tags_offset=0x00000100
cmd_line='console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags movablecore=160M'
board=""
format=gzip
Click to expand...
Click to collapse
Which file are you replacing zImage with?
Sent from my Moto G 2014 LTE using Tapatalk

LuK1337 said:
Which file are you replacing zImage with?
Click to expand...
Click to collapse
When unpacking boot.img, I get a "kernel" file. I replaced this with the "zImage" file which I compiled.

90180360 said:
When unpacking boot.img, I get a "kernel" file. I replaced this with the "zImage" file which I compiled.
Click to expand...
Click to collapse
Try arch/arm/boot/compressed/vmlinux.

LuK1337 said:
Try arch/arm/boot/compressed/vmlinux.
Click to expand...
Click to collapse
If I use this file as kernel, it kicks me right back to the bootloader when I try to boot after flashing the new boot.img.

BTW, I've also tried to manually decompress the kernel by stripping everything before "1f 8b 08" (gzip file signature), but unfortunately this didn't provide a valid archive file.

Alternatively, does anyone know which ROMs have the xt_HL.ko module ("TTL" target support) enabled?

Would it be easier to add this module if I was running CyanogenMod or could it even be officially added?

90180360 said:
Would it be easier to add this module if I was running CyanogenMod or could it even be officially added?
Click to expand...
Click to collapse
CM has disabled modules so you'd have to =y it. I doubt we'll enable it officially..
Sent from my Moto G 2014 LTE using Tapatalk

[ALL VARIANTS] Restore back to stock firmware

Few people asked me how to go back to stock from CM so here's a guide.
NOTE: I tested it only on ZE551KL and TWRP me & luca released.
Instructions :
Download back2stock package.
Download firmware for your device: https://asus.kremowka.xyz.
Extract ASUS firmware and put boot.img, system.new.dat, system.patch.dat, system.transfer.list, file_contexts from it inside of back2stock.zip package.
Flash back2stock.zip in TWRP.
Do a factory reset.

ZE550KL
V1.17.40.1234 (WW) : http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1234-user.zip

eugineprakash said:
ZE550KL
V1.17.40.1234 (WW) : http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1234-user.zip
Click to expand...
Click to collapse
Added.
Sent from my ASUS_Z00TD using Tapatalk

Very helpful for our guys getting error 7 like situation on flashing stock package via twrp

Work to ZE500KL ?

Crasim said:
Work to ZE500KL ?
Click to expand...
Click to collapse
I have no clue if ZE500KL TWRP supports /dev/block/bootimage symlink. If it does it'll work for sure.
Sent from my ASUS_Z00TD using Tapatalk

has anyone found the V1.17.40.1234 (WW) firmware for the ze551kl?
i received the update yesterday on the phone but can't find the d/l anywhere.

beenkenobee said:
has anyone found the V1.17.40.1234 (WW) firmware for the ze551kl?
i received the update yesterday on the phone but can't find the d/l anywhere.
Click to expand...
Click to collapse
Added to OP.

Thanks for posting this procedure. However, after I followed your directions, my phone is stuck on the ASUS screen. The screen is animated but it appears to be stuck after 20+ minutes. Any tips?

thadirector said:
Thanks for posting this procedure. However, after I followed your directions, my phone is stuck on the ASUS screen. The screen is animated but it appears to be stuck after 20+ minutes. Any tips?
Click to expand...
Click to collapse
Did you factory reset?
Sent from my ASUS_Z00TD using Tapatalk

LuK1337 said:
Did you factory reset?
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
Yes I did. Still got the same results.

thadirector said:
Yes I did. Still got the same results.
Click to expand...
Click to collapse
That's weird. Are you sure you added all required files (especially file_contexts)?
BTW what is your model name? Have you tried older firmware files?

LuK1337 said:
That's weird. Are you sure you added all required files (especially file_contexts)?
BTW what is your model name? Have you tried older firmware files?
Click to expand...
Click to collapse
I added all of the files as per the directions. Additionally, I am using the ZE551KL model. I only tried using the V1.16.40.763 (WW) version of the firmware. I will try another version and report back on how it works. Thanks for the suggestion and the help.

LuK1337 said:
That's weird. Are you sure you added all required files (especially file_contexts)?
BTW what is your model name? Have you tried older firmware files?
Click to expand...
Click to collapse
" **** of the galaxy ," if this method were that simple , create custom rom from the stock firmware , it would be extremely simple , I believe you can go further and overcome with the update script

zezinhocrack said:
" **** of the galaxy ," if this method were that simple , create custom rom from the stock firmware , it would be extremely simple , I believe you can go further and overcome with the update script
Click to expand...
Click to collapse
Umm, there's no reason of making it any different. If you want you could use sdat2img.py to generate system.img and just dd it but there's no point.
Sent from my ASUS_Z00TD using Tapatalk

LuK1337 said:
Umm, there's no reason of making it any different. If you want you could use sdat2img.py to generate system.img and just dd it but there's no point.
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
I tested this method , so does what the user @ thadirector reports , the device is frozen in the asus logo and the system does not start , the last alternative is left and flashing system folder decompress, but I have no skills to create symlink / set_metadata

zezinhocrack said:
I tested this method , so does what the user @ thadirector reports , the device is frozen in the asus logo and the system does not start , the last alternative is left and flashing system folder decompress, but I have no skills to create symlink / set_metadata
Click to expand...
Click to collapse
Join #titandev @ freenode. I'll try to help ya.
Sent from my ASUS_Z00TD using Tapatalk

LuK1337 said:
Umm, there's no reason of making it any different. If you want you could use sdat2img.py to generate system.img and just dd it but there's no point.
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
See if you can help :
using your script or below , in both system is recorded very quickly , noting that the stock version with some app removed reaches 3GB unzipped, the TWRP makes every step of recording without mistakes and do the flash suspersu , the TWRP informs that the system is without su installed, yet the machine after restart is frozen in asus logo
Other script i have tested
ui_print("--> ZD551KL Z00T-WW-1.15.40.1238");
ui_print("--> ****************************");
ui_print("--> Mounting system");
set_progress(0.02);
unmount("/system");
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
ui_print("--> Formating system");
delete_recursive("/system");
ui_print("--> Install New System...");
package_extract_file("system.img", "/dev/block/bootdevice/by-name/system");
ui_print("--> Flashing kernel...");
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
unmount("/system");
ui_print(" ");
ui_print("Finished");
ui_print(" ");

zezinhocrack said:
See if you can help :
using your script or below , in both system is recorded very quickly , noting that the stock version with some app removed reaches 3GB unzipped, the TWRP makes every step of recording without mistakes and do the flash suspersu , the TWRP informs that the system is without su installed, yet the machine after restart is frozen in asus logo
Other script i have tested
ui_print("--> ZD551KL Z00T-WW-1.15.40.1238");
ui_print("--> ****************************");
ui_print("--> Mounting system");
set_progress(0.02);
unmount("/system");
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
ui_print("--> Formating system");
delete_recursive("/system");
ui_print("--> Install New System...");
package_extract_file("system.img", "/dev/block/bootdevice/by-name/system");
ui_print("--> Flashing kernel...");
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
unmount("/system");
ui_print(" ");
ui_print("Finished");
ui_print(" ");
Click to expand...
Click to collapse
I don't really care what other script did you use. Just join IRC so I can actually help you.
EDIT: I don't see you on IRC 30 mins later so have fun figuring it out yourself. Good luck.

Hello, I tried to flash in ze551kl, put the files in the root directory, I flashed the back to stock zip file, wipe data, caché, dalvik caché and start again in cm 13. I see that you say format factory system, do I from cm13 or from twrp?
Sorry for my English, hope you could understand...