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] 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?

[ROM[[GPE][4.4.4][m7spr][m7wls] Pixel Perfect GPE Beta 1

Hey guys!
So, I got sick of not having a simple, stock, GPE ROM comparable with my device!
I knew a little about porting roms from the UL to the Sprint variant of the HTC One, as per the almost complete port of the L Preview from it's current state to our radio (Thanks @manups4e !!! You probably helped me directly the most, although I can't count out @sykopompos @ANDR01DN00B ( hate typing that username) or @tiny4579)
As for actual work on this, I want to thank @artur0588 for the TWRP-ready version of GPE!
Features:
Code:
De-odexed
Zipaligned
Pre-rooted
Busybox
Sprint kernel tweaks
Sprint proprietary binaries (From http://forum.xda-developers.com/showthread.php?t=2371960)
Otherwise TOTALLY STOCK GOOGLE PLAY EDDITION
Kernel from http://forum.xda-developers.com/showthread.php?t=2371960
XDA:DevDB Information
[ROM[[GPE][4.4.4][m7spr][m7wls] Pixel Perfect GPE Beta 1, ROM for the Sprint HTC One
Contributors
ajbiz11, artur0588, manups4e
ROM OS Version: 4.4.x KitKat
Based On: Google Play Edition
Version Information
Status: Testing
Created 2014-10-11
Last Updated 2014-10-11

Downloads:
REMINDER: I POST THESE RIGHT BEFORE I TEST THEM! AS OF THE MOMENT THEY'RE POSTED, THEY'RE UNTESTED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Beta 1 - Build 1: https://mega.co.nz/#!tZ9mjJYY!mbdARE_2Gw4E6RRESM7PTRQ50HW4ur37s1nC63gIWuc THIS HAS A BROKEN UPDATER SCRIPT! I NEED TO FIGURE OUT WHAT I BROKE, BUT THE SYSTEM AND KERNEL SHOULD WORK
Beta 1 - Build 2 https://mega.co.nz/#!5E000YQa!2z2j8vwXTr9GNMxOkveaJw4s-nPo76RGHOIQM0wdwQg - I think I fixed the issues with the updater-script and update-binary Edit: NOPE

Reserved

Last one! I swear!~

Well, there appears to be an issue with the updater binary, so I'll have to sort that out

Can't wait to try this once you get the update binary and script sorted out!
Sent from my HTCONE using Tapatalk

My username is the most unique out of all XDA!!! Good luck with this project, but unfortunately I don't have a Sprint/Verizon variant, so I cannot test and I am not of any help to you.
Cheers.

Are you using the right binary and have it set up right in meta-inf?
Sent from my LG-D851

sykopompos said:
Are you using the right binary and have it set up right in meta-inf?
Sent from my LG-D851
Click to expand...
Click to collapse
Well, I used my kitchen to rebuild my edify script, so perhaps it broke everything

ajbiz11 said:
Well, I used my kitchen to rebuild my edify script, so perhaps it broke everything
Click to expand...
Click to collapse
I'll download it and fox your updater script for you in a bit
Sent from my LG-D851

Try replacing the updater-binary with the one from one of my L builds and then pull the recovery log if it doesn't go. It looks like it is using the newer style binary
Sent from my LG-D851

sykopompos said:
Try replacing the updater-binary with the one from one of my L builds and then pull the recovery log if it doesn't go. It looks like it is using the newer style binary
Sent from my LG-D851
Click to expand...
Click to collapse
Will do

sykopompos said:
Try replacing the updater-binary with the one from one of my L builds and then pull the recovery log if it doesn't go. It looks like it is using the newer style binary
Sent from my LG-D851
Click to expand...
Click to collapse
Well
Here's the error with the new bianary (same as old iirc)
Code:
Installing '/sdcard/gpe/gpe.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
line 4 col 28: syntax error, unexpected STRING, expecting $end
1 parse errors
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/gpe/gpe.zip'
Setting performance mode OFF.
Error flashing zip '/sdcard/gpe/gpe.zip'
Updating partition details...

ajbiz11 said:
Well
Here's the error with the new bianary (same as old iirc)
Code:
Installing '/sdcard/gpe/gpe.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
line 4 col 28: syntax error, unexpected STRING, expecting $end
1 parse errors
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/gpe/gpe.zip'
Setting performance mode OFF.
Error flashing zip '/sdcard/gpe/gpe.zip'
Updating partition details...
Click to expand...
Click to collapse
Well that is much more informative. You need a file_contexts file (it is in the boot IMG) then fix the syntax error on line 4
Sent from my LG-D851

sykopompos said:
Well that is much more informative. You need a file_contexts file (it is in the boot IMG) then fix the syntax error on line 4
Sent from my LG-D851
Click to expand...
Click to collapse
Oh how did I miss the file_contexts

The funny part is the syntax error wasn't on line 4
it was line 3 making line 4 look wrong
Code:
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p37");
mount("ext4", "EMMC", "/dev/block/mmcblk0p37", "/system"); "0 /system/
package_extract_dir("system", "/system");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
I imagine it should look more like this, no @sykopompos?
Code:
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p37");
mount("ext4", "EMMC", "/dev/block/mmcblk0p37", "/system");
package_extract_dir("system", "/system");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");

The "0" marks it mounted as root, it looks like the syntax might be missing quotes though
Sent from my LG-D851

sykopompos said:
The "0" marks it mounted as root, it looks like the syntax might be missing quotes though
Sent from my LG-D851
Click to expand...
Click to collapse
Well, if you get a chance to look, https://mega.co.nz/#!VEM3gZhR!Fjv8YIbvsozo_QeCxl7oji4uPdxOynXewnDwYS9McQA here is the script (before the removal I made)
Or the zip is in the 2nd post

ajbiz11 said:
Well, if you get a chance to look, https://mega.co.nz/#!VEM3gZhR!Fjv8YIbvsozo_QeCxl7oji4uPdxOynXewnDwYS9McQA here is the script (before the removal I made)
Or the zip is in the 2nd post
Click to expand...
Click to collapse
I had already downloaded it but I can't test it because I don't have the device
Sent from my LG-D851

sykopompos said:
I had already downloaded it but I can't test it because I don't have the device
Sent from my LG-D851
Click to expand...
Click to collapse
I was referring more to if you saw syntax errors
I'll take another crack at it tomorrow

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

p20 pro unlocked bootloader with Lineage os 16.0

UPDATE: Please read my last message as that is where i am now. stuck on ERROR 7 while trying to sideload Latest Lineage Rom in twrp 3.3.0.2
hello People of Xda i have a question i just bought a p20 pro with unlocked bootloader and it is running los 16.0 long story short i bought this phone with unlocked bootloader and how it is now
p20 pro
Serial Number: LCL0218320009805 (its a CLT-09 apearently)
Build Number: lineage_charlotte-userdebug 9 PQ3A. 190705.003 e6b2c9a74b witch is the lineage-16.0-20190722-nightly-charlotte- i think
sha256
but i have a few questions i just wanna install magisk on it but i read there are a few restrictions that i couldnt just flash trough twrp but i have to sideload and flash apps because of encryption or something i dont fully understand that.
so what i want done sideloaded open gapps that worked and then rebooted everything worked fine.
p20 pro
Serial Number: LCL0218320009805 (its a CLT-09 apearently)
Build Number: lineage_charlotte-userdebug 9 PQ3A. 190705.003 e6b2c9a74b witch is the lineage-16.0-20190722-nightly-charlotte- i think
sha256
if i press Volume up + Power when phone is off it boots me to Erecovery but when i use this tool https://forum.xda-developers.com/hu...l-one-driversunlocktwrpfactory-t3779416/page5 And click Reboot Recovery while android is running it reboots me into Twrp 3.3.1-0 but i dont know whatbuild official or an unoffical. i tried to make a backup in twrp but it says can not create /data/media/0/TWRP Folder (required key not available) failed to make backup folder.
So i looked at the folders but when i look into my /sdcard it shows 10 maps with names like (2XtndypQA4RQ0dCtNechaB) and (BvZw1HkIUW5LDKk4BJgNSB) and 8 more so the guy told me i should sideload the open gapps and magisk trough that ALL in One Tool but when i do it says the same error as when i want to make a backup
it also says Failed to mount /system_root aprearently this is the encryption that i can`t turn off off on the phone.
on all my other rooted phones its not this much of a hassle and i dont want to break anything by doing something that I cant undo I`d rather ask some experienced people.
EDIT:UPDATE
I lost my Twrp because i sideloaded magisk 19.3 and flashing latest offical twrp to recovery didn`t work. i think because of magisk somehow.
This Guide says https://www.xda-developers.com/how-to-root-the-huawei-p20-pro-and-install-magisk/ i have to do that but its for CL29 and i do own a CL29 but the bootloader is locked on that device thats why i bought a second p20 pro xD so maby someone can kick me in the right direction on how to go on from this or had experience doing this. or is that guide outdated and can i just install magisk now
so what i dont know if i should do is
A: Rebrand the phone to CLT-29 to install that boot img for magisk (i dont know if that removes the unlocked bootloader) depends on what method i use i think? and if i need to downgrade first
B:downgrade back to a 8.1 stock rom first but i dont know my what my stock firmware is and firmware checker doesnt work because of los 16.0
C:i just want magisk but i dont know for sure if i can just flash magisk on my current build and still be able to hide root in magisk because apearently that is a problem (something with decrypting in Twpr)
D: i dont know if i can just not flash stuff on this twpr build or if its perfectly fine on the unofficial build i think he used https://forum.xda-developers.com/hu...awei-p20-pro-charlotte-l29c432b131-8-t3809964 this twpr build
honestly im finding it allot of info to take in and im lost on what to do now as i didnt root the phone myself and didnt really know what happened and what i can and cannot do safely.
I don`t know what information is outdated for my latest build and and im comming into the P20 scene fairly late can someone give me a hint on what to look out for trying Magisk and twrp to work on my build.
i just dont wanna lose my boot loader unlock or full brick the device and i feel im so close xD

ok it starts to make more sense now i think im on a official twrp 3.3.1-0 that does not decrypt my files thats why i got all these wierd folders
I don`t think I need to rebrand i can just go back to 8.1 maby with this guide ? https://www.getdroidtips.com/downgrade-huawei-p20-pro-android-pie-oreo/#Instructions (doesn't remove bootloader unlock right?)
and then install https://forum.xda-develop...ery-twrp-3-2-1-0-t3769917 so im decrypted and the wipe system and data should work normally right? and i can just start flashing trough twrp like i normally do because this all throws me off a little
and then i can install a modded boot image to make magisk work that works both on cl29 and my c09
i found a site that has my stock rom i need https://www.allrom.ir/2018/04/04/رام-فارسی-اندروید-8-0-هوآوی-پی-20-پرو-clt-l29-l09/
thats the firmware i need its the same as in the 8.1.0.106 (C185) for CLT_L29 / L09 the only problem is they sell it for 1500$ and im far from being that rich ;p
All help tips and tricks would be greatly apreciated if you need more info im more then willing to provide i dont wanna give up on my phone i know it`s possible somehow!
Screenshots:
Root Checker Safteynet check and About Phone >
https://ibb.co/XDZSFXh https://i.ibb.co/yFzp8Fz/Screenshot-20190724-082956-Root-Checker.png https://ibb.co/0mHG6Gp

Okay After i got everything working and know how to get Magisk working i need to fix my google play services so i thought lets reflash the lineage 16.0 latest rom and Mind The Gapps but everytime i try to sideload the Rom trough Twrp i get Updater process ended with ERROR: 7
or ' /sideload/package.zip
E3000:this package expects the value " _a" for "ro.
boot.slot_suffix";
im using adb push lineage-16.0-20190723-nightly-charlotte-signed.zip /tmp/ and i tried adb sideload lineage-16.0-20190723-nightly-charlotte-signed.zip
any tips?
tried to wipe system and cache before flashing but now i ended up with no OS on my phone xD my gawd twrp Works and Bootloader works so i should be good.
do i need to remove lines from the updater script of the lineage-16.0-20190723-nightly-charlotte-signed.zip ?
Luk said 'boot.img'; 'slot_suffix'. so i looked them up and it should be line 4 and 25 so do i remove those whole lines of code that i selected in red?
This is the code:
1. assert(getprop("ro.product.device") == "charlotte" || getprop("ro.build.product") == "charlotte" ||
2. getprop("ro.product.device") == "kirin970" || getprop("ro.build.product") == "kirin970" || abort("E3004: This package is for device: charlotte,kirin970; this device is " + getprop("ro.product.device") + ".");
3. assert(huawei.verify_vendor_build_id("P") == "1");
4. getprop("ro.boot.slot_suffix") == "_a" || abort("E3000: This package expects the value "_a" for "ro.boot.slot_suffix"; this has value "" + getprop("ro.boot.slot_suffix") + "".");
ui_print("Target: Huawei/lineage_charlotte/charlotte:9/PQ3A.190705.003/e6b2c9a74b:userdebug/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup", "/system/system");
unmount("/system");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
run_program("/sbin/e2fsck", "-fy", "/dev/block/bootdevice/by-name/system");
run_program("/tmp/install/bin/resize2fs_static", "/dev/block/bootdevice/by-name/system");
run_program("/sbin/e2fsck", "-fy", "/dev/block/bootdevice/by-name/system");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore", "/system/system");
unmount("/system");
show_progress(0.050000, 5);
25. package_extract_file("boot.img", "/dev/block/bootdevice/by-name/kernel");
show_progress(0.200000, 10);
set_progress(1.000000);

#Last Post Everything works now and im happy Thanks to Luk who gave me a nudge in the right direction. Luk said 'boot.img'; 'slot_suffix' I said thank you ;'p
Im gonna leave this post so others can learn from my mistakes.... If you have any questions about any of the things in my thread go ahead im basicly Pro now ;P