Database Users

[Q] E: Error in /sdcard/update.zip (Status 6)

Hi guys,
i just tried to make my own update.zip.
The files inside are like this:
Code:
META-INF/
-com/
-google/
-android/
update-binary
updater-script
system/
-app/
Gallery3D.apk
I took update-binary and updater-script from another update.zip.
Then i modified updater-script to this:
Code:
show_progress 0.1 0
delete SYSTEM:app/Gallery.apk
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
Unfortunately it doesn't work. This is what i get if i try to apply the .zip:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/update.zip
(Status 6)
Installation aborted.
I just don't get it. Why isn't it working?

luckybk said:
Hi guys,
i just tried to make my own update.zip.
The files inside are like this:
Code:
META-INF/
-com/
-google/
-android/
update-binary
updater-script
system/
-app/
Gallery3D.apk
I took update-binary and updater-script from another update.zip.
Then i modified updater-script to this:
Code:
show_progress 0.1 0
delete SYSTEM:app/Gallery.apk
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
Unfortunately it doesn't work. This is what i get if i try to apply the .zip:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/update.zip
(Status 6)
Installation aborted.
I just don't get it. Why isn't it working?
Click to expand...
Click to collapse
The syntax you're using if for an "update-script" not an "updateR-script"
Off the top of my head! This should work as an updateR-script...
Code:
show_progress(0.900000, 3);
mount("yaffs2", "MTD", "system", "/system");
delete("/system/app/Gallery.apk");
package_extract_dir("system", "/system");
set_perm(0, 0, 0644, "/system/app/Gallery.apk");
show_progress(0.100000, 1);
unmount("/system");

I ran into this same issue when trying to roll my own zips. I tried both syntaxes without luck. I had to abandon my work for the time being. If I can find it, I'll see about posting up here for reference. I couldn't even get a ONE LINER to work.

Read my sig, look up my Gallery3D mod, it has update-script and updater-script variants.

Phoenix84118 said:
I ran into this same issue when trying to roll my own zips. I tried both syntaxes without luck. I had to abandon my work for the time being. If I can find it, I'll see about posting up here for reference. I couldn't even get a ONE LINER to work.
Click to expand...
Click to collapse
In that case you have the wrong binary included...
Just try a:
Code:
ui_print("Hello world!");
line...

djmcnz said:
The syntax you're using if for an "update-script" not an "updateR-script"
Off the top of my head! This should work as an updateR-script...
Code:
show_progress(0.900000, 3);
mount("yaffs2", "MTD", "system", "/system");
delete("/system/app/Gallery.apk");
package_extract_dir("system", "/system");
set_perm(0, 0, 0644, "/system/app/Gallery.apk");
show_progress(0.100000, 1);
unmount("/system");
Click to expand...
Click to collapse
yeah but my friend except the progress code all the rests i'll do them but i see the same error what can i do in that case?? PLZ help!

paok96 said:
yeah but my friend except the progress code all the rests i'll do them but i see the same error what can i do in that case?? PLZ help!
Click to expand...
Click to collapse
Status 6 is a syntax problem... you need to find it!
Do not use Windows Notepad
Make sure there is a <cr> (carriage return/enter) at the end of the file...

Update Script Zenfone Selfie

Hi,
I try to create a way to flash the rom stock of ZD551KL , creating an update script modified with system.img and boot.img when flashing TWRP with the zip file , recording occurs normally, but when I restart the device does not enter the system , what can this happening already are several unsuccessful attempts ....
the steps that follow:
-Reboot to TWRP
-Full Wipe (Dalvik/system/cache/data)
My script update:
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(" ");

Hi,
You should extract system.img so, it would have folders and files like these before zipped:
META-INF
data (optional)
system
boot.img
ifwi.zip
Just copying system.img won't work, because firmware isn't same like kernel (you need to extract everything out).
Sent from my ASUS_Z00AD

krasCGQ said:
Hi,
You should extract system.img so, it would have folders and files like these before zipped:
META-INF
data (optional)
system
boot.img
ifwi.zip
Just copying system.img won't work, because firmware isn't same like kernel (you need to extract everything out).
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
This example is for the Zenfone 2, the ROM of the structure of Zenfone selfie is different , to use the system decompressed already have to create the symlink / set_metadata , that part I do not have much experience

[Guide][Xiaomi][MSM8956] Port Redmi Note 3 ROMs To Mi Max

In my previous guide i explained How to port hydrogen ROMs to helium, and in this simple guide i'll show you guys How to port ROMs from kenzo as it's the same SoC like hydrogen (MSM8956) let's start !
You'll need some tools:
- ROM kitchen, i prefer superr's kitchen. :good:
- Boot image Extractor, you can use Android Image Kitchen
- Any text editor, Notepad++ is good choice for windows users.
Part 0: Preparing:
0- Get any Redmi Note 3 ROM (kenzo), you can find many in XDA or 4PDA
1- Open superr's kitchen and create new project, then copy kenzo ROM to project folder and Extract zip using kitchen (option 4). [when it asks for perm type choose sparse_dat]
2- Copy boot.img to Android Image Kitchen folder and run unpackimg.sh / unpackimg.bat (You can also drag and drop boot to unpackimg.bat if you're using windows).
Part 1: System files:
there's many differences between hydrogen and kenzo, like audio, camera and fingerprint, so you'll need to copy these files to "system" folder in kitchen.
File list
Then you have to edit build.prop replace kenzo with hydrogen and copy lines in hydrogen one like "fpc"
You can get this files from any working hydrogen ROM or from my Github Repo Here
Part 2: Editing Boot.img :
After unpacking kenzo boot.img using Android Image Kitchen You'll need to copy hydrogen zImage and edit somefiles:
* i prefer editing the following files even you can just copy it from hydrogen boot.img *
- Copy hydrogen zImage to "split_img" and make sure it's renamed as "boot.img-zImage"
- edit default.prop, change kenzo to hydrogen
- edit init.qcom.rc, you should use any compare program, like diff / meld / beyondcompare to check what code is in hydrogen and not in kenzo like
Line 204:216
Code:
# LED
chmod 0666 /sys/class/leds/led:torch_0/brightness
chmod 0666 /sys/class/leds/led:torch_1/brightness
chmod 0666 /sys/class/leds/led:switch/brightness
chown system system /sys/class/leds/red/blink
chown system system /sys/class/leds/green/blink
chown system system /sys/class/leds/blue/blink
chown system system /sys/class/leds/red/led_time
chown system system /sys/class/leds/green/led_time
chown system system /sys/class/leds/blue/led_time
on post-fs
start qseecomd
line 352:376
Code:
# Mark the copy complete flag to not completed
write /data/misc/radio/copy_complete 0
chown radio radio /data/misc/radio/copy_complete
chmod 0660 /data/misc/radio/copy_complete
# File flags for prebuilt ril db file
write /data/misc/radio/prebuilt_db_support 1
chown radio radio /data/misc/radio/prebuilt_db_support
chmod 0400 /data/misc/radio/prebuilt_db_support
write /data/misc/radio/db_check_done 0
chown radio radio /data/misc/radio/db_check_done
chmod 0660 /data/misc/radio/db_check_done
# Fingerprint
mkdir /data/fpc 0770 system system
mkdir /data/fpc/s 0770 system system
mkdir /data/tombstones 0771 system system
mkdir /tombstones/modem 0771 system system
mkdir /tombstones/lpass 0771 system system
mkdir /tombstones/wcnss 0771 system system
mkdir /tombstones/dsps 0771 system system
mkdir /persist/data/sfs 0700 system system
mkdir /persist/data/tz 0700 system system
mkdir /data/misc/dts 0770 media audio
mkdir /data/misc/audio_pp 0771 media audio
And
Code:
# Bring up all cores online
write /sys/devices/system/cpu/cpu1/online 1
write /sys/devices/system/cpu/cpu2/online 1
write /sys/devices/system/cpu/cpu3/online 1
write /sys/devices/system/cpu/cpu4/online 1
write /sys/devices/system/cpu/cpu5/online 1
To:
Code:
# Bring up all cores online
write /sys/devices/system/cpu/cpu1/online 1
write /sys/devices/system/cpu/cpu2/online 1
write /sys/devices/system/cpu/cpu3/online 1
write /sys/devices/system/cpu/cpu4/online 1
write /sys/devices/system/cpu/cpu5/online 1
write /sys/devices/system/cpu/cpu6/online 1
write /sys/devices/system/cpu/cpu7/online 1
Line 823:861
Code:
service fingerprintd /system/bin/fingerprintd
class late_start
user system
group drmrpc input system
socket fpce stream 0660 system system
writepid /dev/cpuset/system-background/tasks
service imsqmidaemon /system/bin/imsqmidaemon
class main
user system
socket ims_qmid stream 0660 system radio
group radio log diag
service imsdatadaemon /system/bin/imsdatadaemon
class main
user system
socket ims_datad stream 0660 system radio
group system wifi radio inet log diag
disabled
on property:sys.ims.QMI_DAEMON_STATUS=1
start imsdatadaemon
service ims_rtp_daemon /system/bin/ims_rtp_daemon
class main
user system
socket ims_rtpd stream 0660 system radio
group radio diag inet log
disabled
service imscmservice /system/bin/imscmservice
class main
user system
group radio diag inet log
disabled
on property:sys.ims.DATA_DAEMON_STATUS=1
start ims_rtp_daemon
start imscmservice
- Edit init.rc
Change
Code:
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
To
Code:
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/green/blink
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/blue/blink
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
- Edit init.qcom.sh
Add this line after start_sensors
Code:
start_copying_prebuilt_qcril_db
And this line at the end of file
Code:
chown radio:radio /data/misc/radio/copy_complete
- then Repack boot and copy image-new.img to superr's kitchen project folder then rename it to boot.img
You can get these files from any hydrogen boot.img
Part 3: Finalizing :
Now you've finished porting kenzo ROM to hydrogen, but you need to repack ROM into zip to be able to use it.
- Open superr's kitchen, choose 8) ROM Tools Menu then 7) Build Menu and finally 1) Build full ROM Zip
- Wait till it finishes (when it asks for sign zip press "y") then you'll have to edit META-INF/com/google/android/updater-script inside ROM Zip, so open ROM zip and head to META-INF/com/google/android/ to open updater-script file using text editor then change script to:
Code:
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");
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", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
And Congratulations You've finished porting kenzo ROM to your hydrogen
Special Thanks:
SuperR. for his great kitchen
osm0sis for amazing image tools script
iBotPeaches for apktool
@nijel8 for helium device tree
@Davehimself for helium vendor
@Ahmed Hady & @androidlover5842 my great friends & helpers
And me for typing this guide :good:

Reversed 1

Reversed 2

yshalsager said:
In my previous guide
Click to expand...
Click to collapse
Can u plz port sailfish os of kenzo for MiMAX hydrogen please?
https://forum.xda-developers.com/redmi-note-3/development/rom-sailfish-os-2-0-5-6-kenzo-t3571258/

afridi.shahriar said:
Can u plz port sailfish os of kenzo for MiMAX hydrogen please?
https://forum.xda-developers.com/redmi-note-3/development/rom-sailfish-os-2-0-5-6-kenzo-t3571258/
Click to expand...
Click to collapse
I think it can't be ported. Need to built from sources

yshalsager said:
I think it can't be ported. Need to built from sources
Click to expand...
Click to collapse
Then leave it

yshalsager said:
I think it can't be ported. Need to built from sources
Click to expand...
Click to collapse
Can u port nubia or funtouch os for kenzo or tell me name of device from which I can try to port these ui

Criston said:
Can u port nubia or funtouch os for kenzo or tell me name of device from which I can try to port these ui
Click to expand...
Click to collapse
I don't have kenzo, try with any MSM8956 device or MSM8976

What if rom does not contain some files in the system folder?

psbankar said:
What if rom does not contain some files in the system folder?
Click to expand...
Click to collapse
Forget it

yshalsager said:
I don't have kenzo, try with any MSM8956 device or MSM8976
Click to expand...
Click to collapse
Devices Based On MSM8976 Can Be used R U Sure though the difference is only core base

Criston said:
Devices Based On MSM8976 Can Be used R U Sure though the difference is only core base
Click to expand...
Click to collapse
Yes. As we can port from helium

can similarly kenzo roms can be ported to leeco le with sd652 ??

ankk98 said:
can similarly kenzo roms can be ported to leeco le with sd652 ??
Click to expand...
Click to collapse
yes

yshalsager said:
yes
Click to expand...
Click to collapse
i am a beginner
can u plz explain how this port can work? i mean both devices have different soc?
I want to try it by porting some oreo kenzo rom to leeco le 2 with msm8976

ankk98 said:
i am a beginner
can u plz explain how this port can work? i mean both devices have different soc?
I want to try it by porting some oreo kenzo rom to leeco le 2 with msm8976
Click to expand...
Click to collapse
Follow the guide and take files from your stock/working rom to kenzo rom

Part 3: Finalizing :
Now you've finished porting hydrogen ROM to helium, but you need to repack ROM into zip to be able to use it.
I dont get it, porting rom from hydrogen to helium?

raymondsanusi said:
Part 3: Finalizing :
Now you've finished porting hydrogen ROM to helium, but you need to repack ROM into zip to be able to use it.
I dont get it, porting rom from hydrogen to helium?
Click to expand...
Click to collapse
lol, sorry i was typo mistake
You can port from H2 to He but follow my another guide.

Is this guide can be used for porting Oreo roms?

Hello @yshalsager the file of hydrogen you have uploaded on GitHub are from which MIUI version?

[Concept] OEM Image flasher [AOSP on the Go]

I make it short. Actually are Xperia Devices unable to run AOSP without using fastboot to flash the OEM Images from SONY. I wanted to create a empty ZIP containing a Updater Script who flashes the OEM Images after placing them into the ZIP. The Problem is that i was unable to find the OEM Partition. Is anyone aware of it? I'm searching for the "/dev/block/platform/*/by-name/" to use a command like this "package_extract_file("boot.img", file_getprop("/tmp/config", "boot"));"
And for the People who are wondering why the ZIP has to be empty. There are two Reasons. First, all Devices need own Images, besides that they are getting updated from Time to Time.
The second thing is the Legal Stuff. SONY added a Agreement before You can download the Images. Every User has to accept that, otherwise would we get trouble with them.
Just to clear that out already. Hope we can quickly make the flashing more handy for the Future!
And Dear Moderators, pls don't move this Thread. It will be edited and extended after creating the ZIP to share it right here!

Why not just add /oem flash image to ota-zip (or twrp?)?
Miustone said:
I make it short. Actually are Xperia Devices unable to run AOSP without using fastboot to flash the OEM Images from SONY....
And Dear Moderators, pls don't move this Thread. It will be edited and extended after creating the ZIP to share it right here!
Click to expand...
Click to collapse
{make otapackage} works 100% on xz1 Xperiadev natural aosp; it even comes with an odd aosp/recovery embedded : thus better to FIRST make clean +make bootimage and save it to avoid final embedded recovery. The /vendor img is also included in the ota zip.
If you want to add addon.d support check my Los15 "extracted" https://forum.xda-developers.com/an...zip-custom-t3173316/post76455910#post76455910
Than just repack the final ota zip package with them (including Los15 update-binary).
If you want WidevineDRM L3 (check XZ1 attached txt) you need to add specifics drm/vendors in /vendor prior to build; alternatively for Magisk users, you can instead repack them in final ota zip, but they will only be active after Magisk install. Source https://github.com/DirtyUnicorns/an...3d1555c#diff-daceb2a2ce86bd2430773e29f2b3db5e
To avoid Firebase analytics in Webview , I also suggest using Lineage15 pre-pack 66 version (arm64) https://github.com/LineageOS/android_external_chromium-webview/tree/lineage-15.1/prebuilt
Don't forget MicroG patches https://forum.xda-developers.com/showpost.php?p=75320072&postcount=4319 ...
Code:
[SIZE="1"][I]'bolded is added'[/I]
getprop("ro.product.device") == "poplar" || abort("E3004: This package is for \"poplar\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Sony/aosp_g8341/poplar:8.1.0/OPM2.171019.029/nn04300157:userdebug/dev-keys");
[B]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");
unmount("/system");
[/B]show_progress(0.650000, 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.");
[B]mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
[/B]
show_progress(0.100000, 0);
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
[B]mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/vendor", "/vendor", "");
package_extract_dir("vendor", "/vendor");
unmount("/vendor");
[/B]show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
[/SIZE]
EDIT @Miustone , aosp xperiadev mostly use /odm instead of /oem for /dev/block/bootdevice/by-name/oem (sda63 on xz1), but fastboot always -> oem
(1000Thx @jerpelea )

Clean android ROMs?

Hey
thinking about buying that phone
but I hate MIUI
is there clean android roms for that phone?
how about updates to the roms over time?

Right now we have LineageOS and Paranoid Android, both in Beta stage.
Development is slow.
I'm using Havoc OS (built for the Redmi K20 Pro, I made it work in this device tho).

Schnedi said:
Right now we have LineageOS and Paranoid Android, both in Beta stage.
Development is slow.
I'm using Havoc OS (built for the Redmi K20 Pro, I made it work in this device tho).
Click to expand...
Click to collapse
Hello,
Can you tell how you managed to port rom on MI 9T? Because I used your guide but TWRP still tells me it's a rom for Raphael device

isman77 said:
Hello,
Can you tell how you managed to port rom on MI 9T? Because I used your guide but TWRP still tells me it's a rom for Raphael device
Click to expand...
Click to collapse
Hi.
It's very easy to do.
• Download the ROM
• Uncompress it to get this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
• Delete the 2 files hightlighted red
• Open the one highlighted green
• Delete the first 2 lines
Code:
[COLOR="DarkRed"]assert(getprop("ro.product.device") == "raphael" || getprop("ro.build.product") == "raphael" || abort("E3004: This package is for device: raphael; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: Xiaomi/raphael/raphael:9/PKQ1.181121.001/V10.3.16.0.PFKCNXM:user/release-keys");[/COLOR]
ifelse(is_mounted("/system_root"), unmount("/system_root"));
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);
.......................................
.....................
.........
• Save
• Compress all the files and folders
Installation
• Boot to TWRP
• Format data (after this, move the files to your phone or use an USB OTG)
• Restart TWRP
• Install the ROM
• Factory reset
• Restart TWRP
• Install GApps
• Install Magisk
• Reboot to system

Schnedi said:
Hi.
It's very easy to do.
• Download the ROM
• Uncompress it to get this
• Delete the 2 files hightlighted red
• Open the one highlighted green
• Delete the first 2 lines
Code:
[COLOR="DarkRed"]assert(getprop("ro.product.device") == "raphael" || getprop("ro.build.product") == "raphael" || abort("E3004: This package is for device: raphael; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: Xiaomi/raphael/raphael:9/PKQ1.181121.001/V10.3.16.0.PFKCNXM:user/release-keys");[/COLOR]
ifelse(is_mounted("/system_root"), unmount("/system_root"));
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);
.......................................
.....................
.........
• Save
• Compress all the files and folders
Installation
• Boot to TWRP
• Format data (after this, move the files to your phone or use an USB OTG)
• Restart TWRP
• Install the ROM
• Factory reset
• Restart TWRP
• Install GApps
• Install Magisk
• Reboot to system
Click to expand...
Click to collapse
I can do this with EVERY rom from the Pro variant ?

FroZine said:
I can do this with EVERY rom from the Pro variant ?
Click to expand...
Click to collapse
Yes, I've tried Havoc, Evolution, Pixel Experience and AOSIP.
Unfortunately, if the kernel has an extra feature (DT2W for example) we won't have it.
Kernel is inside the boot.img and if we flash it, the phone will go into a bootloop.

Schnedi said:
Hi.
It's very easy to do.
• Download the ROM
• Uncompress it to get this
• Delete the 2 files hightlighted red
• Open the one highlighted green
• Delete the first 2 lines
Code:
[COLOR="DarkRed"]assert(getprop("ro.product.device") == "raphael" || getprop("ro.build.product") == "raphael" || abort("E3004: This package is for device: raphael; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: Xiaomi/raphael/raphael:9/PKQ1.181121.001/V10.3.16.0.PFKCNXM:user/release-keys");[/COLOR]
ifelse(is_mounted("/system_root"), unmount("/system_root"));
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);
.......................................
.....................
.........
• Save
• Compress all the files and folders
Installation
• Boot to TWRP
• Format data (after this, move the files to your phone or use an USB OTG)
• Restart TWRP
• Install the ROM
• Factory reset
• Restart TWRP
• Install GApps
• Install Magisk
• Reboot to system
Click to expand...
Click to collapse
can you post a link with you'r zip of the rom? for a noob like me in this materie. thxs
Verstuurd vanaf mijn Mi 9T met Tapatalk
---------- Post added at 11:06 AM ---------- Previous post was at 10:55 AM ----------
lets try it by myzelf[emoji3577]
Verstuurd vanaf mijn Mi 9T met Tapatalk

Is it really necessary to format data ?

do i deleted al this lines that yoy show in you file?
Verstuurd vanaf mijn Mi 9T met Tapatalk

beaverhead said:
do i deleted al this lines that yoy show in you file?
Verstuurd vanaf mijn Mi 9T met Tapatalk
Click to expand...
Click to collapse
delete these:
assert(getprop("ro.product.device") == "raphael" || getprop("ro.build.product") == "raphael" || abort("E3004: This package is for device: raphael; this device is " + getprop("ro.product.device") + ".");
ui_print("Target: Xiaomi/raphael/raphael:9/PKQ1.181121.001/V10.3.16.0.PFKCNXM:user/release-keys");
(The first 2 lines)

Schnedi said:
Hi.
It's very easy to do.
• Download the ROM
• Uncompress it to get this
• Delete the 2 files hightlighted red
• Open the one highlighted green
• Delete the first 2 lines
Code:
[COLOR="DarkRed"]assert(getprop("ro.product.device") == "raphael" || getprop("ro.build.product") == "raphael" || abort("E3004: This package is for device: raphael; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: Xiaomi/raphael/raphael:9/PKQ1.181121.001/V10.3.16.0.PFKCNXM:user/release-keys");[/COLOR]
ifelse(is_mounted("/system_root"), unmount("/system_root"));
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);
.......................................
.....................
.........
• Save
• Compress all the files and folders
Installation
• Boot to TWRP
• Format data (after this, move the files to your phone or use an USB OTG)
• Restart TWRP
• Install the ROM
• Factory reset
• Restart TWRP
• Install GApps
• Install Magisk
• Reboot to system
Click to expand...
Click to collapse
Thanks for the great tip, I really appreciate Havoc. I immediately tried the installation, but unfortunately I ended up in a bootloop (at the start of Havoc). My old installation was Global Stable 10.3.11, I used the Russian TWRP. The reinstallation of the Global Stable worked without any problems.
What else could I do to install the Havoc?

limuc said:
Thanks for the great tip, I really appreciate Havoc. I immediately tried the installation, but unfortunately I ended up in a bootloop (at the start of Havoc). My old installation was Global Stable 10.3.11, I used the Russian TWRP. The reinstallation of the Global Stable worked without any problems.
What else could I do to install the Havoc?
Click to expand...
Click to collapse
You flashed 10.3.11 zip rom from twrp after flashig havoc?

limuc said:
Thanks for the great tip, I really appreciate Havoc. I immediately tried the installation, but unfortunately I ended up in a bootloop (at the start of Havoc). My old installation was Global Stable 10.3.11, I used the Russian TWRP. The reinstallation of the Global Stable worked without any problems.
What else could I do to install the Havoc?
Click to expand...
Click to collapse
I think could be caused by SeLinux, try flashing thos file https://androidfilehost.com/?fid=6006931924117886495 after flashing everything else.

epicblue8 said:
You flashed 10.3.11 zip rom from twrp after flashig havoc?
Click to expand...
Click to collapse
Yes, exactly! With wipe and format data, after install, I reboot to recovery, then magisk, then reboot to recovery, then start system.

Schnedi said:
I think could be caused by SeLinux, try flashing thos file https://androidfilehost.com/?fid=6006931924117886495 after flashing everything else.
Click to expand...
Click to collapse
Thanks, that was a great idea! The installation worked fine, but Magisk reports 'cts profile false'. Gpay can't be set up with Paypal either (it worked with the old 'Stable').
When restarting, Havoc reports that the vendor does not match the system, but still starts.
And the BEST: I now have a K20 pro....

Schnedi said:
Right now we have LineageOS and Paranoid Android, both in Beta stage.
Development is slow.
I'm using Havoc OS (built for the Redmi K20 Pro, I made it work in this device tho).
Click to expand...
Click to collapse
And does everything work? the camera and Fingerprint reader?