New working xposed may be find here
http://forum.xda-developers.com/zenfone-2-laser/general/wroking-xposed-ze550kl-t3247915
XDA and We are not responsible for any loss, do it on your own risk.
Hit thanks, if it helps you.
here's my log.. I can't install xpose.. it will reboot when installing xposed but after reboot it is said failed after I press a key.. here's the log
' Connecting ZenFone 2 Laser
'
'
'
'
' Remounting system
'
'
Press any key to continue . . .
'
'
' Pushing files
'
'
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/updater-script -> /sdcard/tmp2/META-INF/com/google/android/updater-script
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/update-binary -> /sdcard/tmp2/META-INF/com/google/android/update-binary
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/flash-script.sh -> /sdcard/tmp2/META-INF/com/google/android/flash-script.sh
push: assets/xposed-sdk21-arm64/META-INF/MANIFEST.MF -> /sdcard/tmp2/META-INF/MANIFEST.MF
push: assets/xposed-sdk21-arm64/META-INF/CERT.SF -> /sdcard/tmp2/META-INF/CERT.SF
push: assets/xposed-sdk21-arm64/META-INF/CERT.RSA -> /sdcard/tmp2/META-INF/CERT.RSA
push: assets/xposed-sdk21-arm64/system/bin/patchoat -> /sdcard/tmp2/system/bin/patchoat
push: assets/xposed-sdk21-arm64/system/bin/oatdump -> /sdcard/tmp2/system/bin/oatdump
push: assets/xposed-sdk21-arm64/system/bin/dex2oat -> /sdcard/tmp2/system/bin/dex2oat
push: assets/xposed-sdk21-arm64/system/bin/app_process64_xposed -> /sdcard/tmp2/system/bin/app_process64_xposed
push: assets/xposed-sdk21-arm64/system/bin/app_process32_xposed -> /sdcard/tmp2/system/bin/app_process32_xposed
push: assets/xposed-sdk21-arm64/system/framework/XposedBridge.jar -> /sdcard/tmp2/system/framework/XposedBridge.jar
push: assets/xposed-sdk21-arm64/system/lib/libxposed_art.so -> /sdcard/tmp2/system/lib/libxposed_art.so
push: assets/xposed-sdk21-arm64/system/lib/libsigchain.so -> /sdcard/tmp2/system/lib/libsigchain.so
push: assets/xposed-sdk21-arm64/system/lib/libart.so -> /sdcard/tmp2/system/lib/libart.so
push: assets/xposed-sdk21-arm64/system/lib/libart-compiler.so -> /sdcard/tmp2/system/lib/libart-compiler.so
push: assets/xposed-sdk21-arm64/system/lib64/libxposed_art.so -> /sdcard/tmp2/system/lib64/libxposed_art.so
push: assets/xposed-sdk21-arm64/system/lib64/libsigchain.so -> /sdcard/tmp2/system/lib64/libsigchain.so
push: assets/xposed-sdk21-arm64/system/lib64/libart.so -> /sdcard/tmp2/system/lib64/libart.so
push: assets/xposed-sdk21-arm64/system/lib64/libart-disassembler.so -> /sdcard/tmp2/system/lib64/libart-disassembler.so
push: assets/xposed-sdk21-arm64/system/xposed.prop -> /sdcard/tmp2/system/xposed.prop
push: assets/xposed-sdk21-arm64/flash-script.sh -> /sdcard/tmp2/flash-script.sh
22 files pushed. 0 files skipped.
4632 KB/s (12807304 bytes in 2.700s)
Press any key to continue . . .
'
'
' Installing Xposed
'
'
******************************
Xposed framework installer zip
******************************
- Mounting /system and /vendor read-write
- Checking environment
Xposed version: 75
- Placing files
Press any key to continue . . .
' Let phone reboot first, then press any key
Press any key to continue . . .
'
'
' Removing files
'
'
Press any key to continue . . .
'
'
' Installing Xposed Installer ..
'
'
6125 KB/s (626521 bytes in 0.099s)
pkg: /data/local/tmp/XposedInstaller_3.0_alpha4.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Click to expand...
Click to collapse
oke I flashed again and here's the problem on xposed.. if I reboot that the android upgrading will continue and after that the above log will occur
' Installing Xposed
'
'
******************************
Xposed framework installer zip
******************************
- Mounting /system and /vendor read-write
- Checking environment
Xposed version: 75
- Placing files
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "gzip"; caused by library "libsigchain.so" not found
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "chown"; caused by library "libsigchain.so" not found
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "chmod"; caused by library "libsigchain.so" not found
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "cp"; caused by library "libsigchain.so" not found
- Done
Press any key to continue . . .
' Let phone reboot first, then press any key
Press any key to continue . . .
Click to expand...
Click to collapse
EDIT:
Got it working now.. I dunno how it just said success on xposed installer hope other do not experience this.. Thank you for this
first time you got error because there was xposed framework installed already.
please make sure there is no xposed installed before starting process.
About warning
just ignore that, it s common.
which modules are working?
i had gravity box,Xinternal sd and few others and after rebooting i am stuck at asus screen.
' Pushing files
'
'
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/updater-script -> /s
dcard/tmp2/META-INF/com/google/android/updater-script
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/update-binary -> /sd
card/tmp2/META-INF/com/google/android/update-binary
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/flash-script.sh -> /
sdcard/tmp2/META-INF/com/google/android/flash-script.sh
push: assets/xposed-sdk21-arm64/META-INF/MANIFEST.MF -> /sdcard/tmp2/META-INF/MA
NIFEST.MF
push: assets/xposed-sdk21-arm64/META-INF/CERT.SF -> /sdcard/tmp2/META-INF/CERT.S
F
push: assets/xposed-sdk21-arm64/META-INF/CERT.RSA -> /sdcard/tmp2/META-INF/CERT.
RSA
push: assets/xposed-sdk21-arm64/system/bin/patchoat -> /sdcard/tmp2/system/bin/p
atchoat
push: assets/xposed-sdk21-arm64/system/bin/oatdump -> /sdcard/tmp2/system/bin/oa
tdump
push: assets/xposed-sdk21-arm64/system/bin/dex2oat -> /sdcard/tmp2/system/bin/de
x2oat
push: assets/xposed-sdk21-arm64/system/bin/app_process64_xposed -> /sdcard/tmp2/
system/bin/app_process64_xposed
push: assets/xposed-sdk21-arm64/system/bin/app_process32_xposed -> /sdcard/tmp2/
system/bin/app_process32_xposed
push: assets/xposed-sdk21-arm64/system/framework/XposedBridge.jar -> /sdcard/tmp
2/system/framework/XposedBridge.jar
push: assets/xposed-sdk21-arm64/system/lib/libxposed_art.so -> /sdcard/tmp2/syst
em/lib/libxposed_art.so
push: assets/xposed-sdk21-arm64/system/lib/libsigchain.so -> /sdcard/tmp2/system
/lib/libsigchain.so
push: assets/xposed-sdk21-arm64/system/lib/libart.so -> /sdcard/tmp2/system/lib/
libart.so
push: assets/xposed-sdk21-arm64/system/lib/libart-compiler.so -> /sdcard/tmp2/sy
stem/lib/libart-compiler.so
push: assets/xposed-sdk21-arm64/system/lib64/libxposed_art.so -> /sdcard/tmp2/sy
stem/lib64/libxposed_art.so
push: assets/xposed-sdk21-arm64/system/lib64/libsigchain.so -> /sdcard/tmp2/syst
em/lib64/libsigchain.so
push: assets/xposed-sdk21-arm64/system/lib64/libart.so -> /sdcard/tmp2/system/li
b64/libart.so
push: assets/xposed-sdk21-arm64/system/lib64/libart-disassembler.so -> /sdcard/t
mp2/system/lib64/libart-disassembler.so
push: assets/xposed-sdk21-arm64/system/xposed.prop (1).txt -> /sdcard/tmp2/syste
m/xposed.prop (1).txt
push: assets/xposed-sdk21-arm64/system/xposed.prop -> /sdcard/tmp2/system/xposed
.prop
push: assets/xposed-sdk21-arm64/flash-script.sh -> /sdcard/tmp2/flash-script.sh
23 files pushed. 0 files skipped.
3677 KB/s (12807304 bytes in 3.400s)
Press any key to continue . . .
'
'
' Installing Xposed
'
'
******************************
Xposed framework installer zip
******************************
- Mounting /system and /vendor read-write
- Checking environment
Xposed version:
! Wrong platform: arm64
! This file is for:
! Please download the correct package
! for your platform/ROM!
Press any key to continue . . .
' Let phone reboot first, then press any key
Press any key to continue . . .
'
'
' Removing files
'
'
override rwxrwxrwx root:root for '/system/tmp'?
---------- Post added at 10:45 AM ---------- Previous post was at 10:41 AM ----------
What to do...?
---------- Post added at 11:33 AM ---------- Previous post was at 10:45 AM ----------
' Pushing files
'
'
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/updater-script -> /s
dcard/tmp2/META-INF/com/google/android/updater-script
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/update-binary -> /sd
card/tmp2/META-INF/com/google/android/update-binary
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/flash-script.sh -> /
sdcard/tmp2/META-INF/com/google/android/flash-script.sh
push: assets/xposed-sdk21-arm64/META-INF/MANIFEST.MF -> /sdcard/tmp2/META-INF/MA
NIFEST.MF
push: assets/xposed-sdk21-arm64/META-INF/CERT.SF -> /sdcard/tmp2/META-INF/CERT.S
F
push: assets/xposed-sdk21-arm64/META-INF/CERT.RSA -> /sdcard/tmp2/META-INF/CERT.
RSA
push: assets/xposed-sdk21-arm64/system/bin/patchoat -> /sdcard/tmp2/system/bin/p
atchoat
push: assets/xposed-sdk21-arm64/system/bin/oatdump -> /sdcard/tmp2/system/bin/oa
tdump
push: assets/xposed-sdk21-arm64/system/bin/dex2oat -> /sdcard/tmp2/system/bin/de
x2oat
push: assets/xposed-sdk21-arm64/system/bin/app_process64_xposed -> /sdcard/tmp2/
system/bin/app_process64_xposed
push: assets/xposed-sdk21-arm64/system/bin/app_process32_xposed -> /sdcard/tmp2/
system/bin/app_process32_xposed
push: assets/xposed-sdk21-arm64/system/framework/XposedBridge.jar -> /sdcard/tmp
2/system/framework/XposedBridge.jar
push: assets/xposed-sdk21-arm64/system/lib/libxposed_art.so -> /sdcard/tmp2/syst
em/lib/libxposed_art.so
push: assets/xposed-sdk21-arm64/system/lib/libsigchain.so -> /sdcard/tmp2/system
/lib/libsigchain.so
push: assets/xposed-sdk21-arm64/system/lib/libart.so -> /sdcard/tmp2/system/lib/
libart.so
push: assets/xposed-sdk21-arm64/system/lib/libart-compiler.so -> /sdcard/tmp2/sy
stem/lib/libart-compiler.so
push: assets/xposed-sdk21-arm64/system/lib64/libxposed_art.so -> /sdcard/tmp2/sy
stem/lib64/libxposed_art.so
push: assets/xposed-sdk21-arm64/system/lib64/libsigchain.so -> /sdcard/tmp2/syst
em/lib64/libsigchain.so
push: assets/xposed-sdk21-arm64/system/lib64/libart.so -> /sdcard/tmp2/system/li
b64/libart.so
push: assets/xposed-sdk21-arm64/system/lib64/libart-disassembler.so -> /sdcard/t
mp2/system/lib64/libart-disassembler.so
push: assets/xposed-sdk21-arm64/system/xposed.prop (1).txt -> /sdcard/tmp2/syste
m/xposed.prop (1).txt
push: assets/xposed-sdk21-arm64/system/xposed.prop -> /sdcard/tmp2/system/xposed
.prop
push: assets/xposed-sdk21-arm64/flash-script.sh -> /sdcard/tmp2/flash-script.sh
23 files pushed. 0 files skipped.
3677 KB/s (12807304 bytes in 3.400s)
Press any key to continue . . .
'
'
' Installing Xposed
'
'
******************************
Xposed framework installer zip
******************************
- Mounting /system and /vendor read-write
- Checking environment
Xposed version:
! Wrong platform: arm64
! This file is for:
! Please download the correct package
! for your platform/ROM!
Press any key to continue . . .
' Let phone reboot first, then press any key
Press any key to continue . . .
'
'
' Removing files
'
'
override rwxrwxrwx root:root for '/system/tmp'?
---------- Post added at 10:45 AM ---------- Previous post was at 10:41 AM ----------
What to do...?
make sure you have busybox installed in your phone, allow root permission to adb.
if tried any other version previously then please uninstall.
if you are still getting error then wipe data/factory reset
wipe cache partition.
install supersu apk
install busybox
allow root access to busy box, adb shell
then click 1.bat & let process complete.
IronMan_in said:
which modules are working?
i had gravity box,Xinternal sd and few others and after rebooting i am stuck at asus screen.
Click to expand...
Click to collapse
tested on
gravity box LP
youtube ad remover
advance reboot menu +
I do this only and that also of 2 times after flashing full rom again.
Got This working with zenfone selfie slim rooted rom
list of module that i currently use
- Gravitybox LP
- Greenify
- Lucky Patcher
- Spotify AVRCP
- SpotifySkip
- Youtube
- YouTube AdAway
- YouTube Background Playback
I got this error now how to download feamework?
{
"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"
}
Why not work with a Stock Rom 1:13 Zenfone Selfie ZD551KL?
Mandrakerj said:
Why not work with a Stock Rom 1:13 Zenfone Selfie ZD551KL?
Click to expand...
Click to collapse
At present we are unable to figure out what s going wrong with that.
We can not test as we dont have that model, we have only ze550kl & working well while testing & using.
I update thread title after getting positive feedback from users regarding working on slim version.
rajlko said:
At present we are unable to figure out what s going wrong with that.
We can not test as we dont have that model, we have only ze550kl & working well while testing & using.
I update thread title after getting positive feedback from users regarding working on slim version.
Click to expand...
Click to collapse
Ok fine friend ..
waiting
not working
ZE550KL_WW_1.15.40.639 not working with this version
BTiwari said:
ZE550KL_WW_1.15.40.639 not working with this version
Click to expand...
Click to collapse
If you're running the rooted version of WW_1.15.40.639 by @shakalaca then you'll notice there's a xposed_patch file and an associated xposed_patch.README file that he included with the pre-rooted ROM image. Follow the instructions in that file and maybe you'll get it to work? (I haven't tried it yet, so I'm not sure).
@rajlko started a new thread for installing xposed on WW_1.15.40.639. Have you tried that?
xyberz09 said:
If you're running the rooted version of WW_1.15.40.639 by @shakalaca then you'll notice there's a xposed_patch file and an associated xposed_patch.README file that he included with the pre-rooted ROM image. Follow the instructions in that file and maybe you'll get it to work? (I haven't tried it yet, so I'm not sure).
@rajlko started a new thread for installing xposed on WW_1.15.40.639. Have you tried that?
Click to expand...
Click to collapse
how to apply that patch i have try it but no luck
BTiwari said:
how to apply that patch i have try it but no luck
Click to expand...
Click to collapse
Try installing Xposed Framework by following the instructions on @rajlko's new thread: http://forum.xda-developers.com/zenfone-2-laser/general/wroking-xposed-ze550kl-t3247915
If that doesn't work, you'll need to download xdelta and apply the patch on the unzipped system.img file from the pre-rooted image. The command you need to run is this:
Code:
xdelta3 -d -s system.img xposed_patch system_xposed.img
After the command completes, you'll see a new file called system_xposed.img and you'll need to flash it using the following command:
Code:
fastboot flash system system_xposed.img
NOTE: I haven't tried any of this. I'm simply reiterating the instructions from the README file. If this doesn't work, you'll probably have to contact @shakalaca about the issue.
If some one having issue regarding xposed,then first run remove xposed framework, let that finished, if there is any xposed apk install remove that, restart your your mobile, start procedure from begining.
Hi people,
I would like to collect some dev info for the M2 which may help in future development efforts - maybe tweak the official ROMs to be less idiotic, or develop new ROMs, apps, etc.
If any of you can contribute info similar to what I have shown below, it would be greatly appreciated. I will collate and analyze the info from your replies and add it to these first couple of posts so that it serves as the main repo of this dev info.
*** DISCLAIMER *** Please do not attempt to collect any info from your device if you are not confident about or familiar with how to root your device or how to use shell commands in a root terminal shell. Any and all damage you may cause to your device in the pursuit of gathering this information is solely your responsibility and I will be neither responsible nor accountable for any such damage.
Still reading? Good. I commend your enthusiasm :good:
Guide: Block Device/Partition Information
Introduction
Here are some links explaining what Android partitions are and what they do. While some of the info in the links refers to other devices or has been superseded by changes to Android since the article was written, the basic information itself holds good:
http://www.all-things-android.com/content/review-android-partition-layout
http://donandroid.com/android-partitions-sdcard-boot-recovery-cache-data-system-misc-1043
https://sites.google.com/site/tomsgt123/adb-fastboot/understanding-android
This information is important because:
It will help us to map the contents of the official UPDATE.APP to the proper locations on the ROM Storage where they must be flashed.
It will help the developers of the Huawei Update Extractor tool to create an extractor profile specific for our M2 8.0 or 10.0 devices.
EDIT: I have actually already done this for the M2-802L, see my post on the Huawei Update extractor tool thread. Now we just need to wait for worstenbrood to integrate it into a new release of the Extractor.
It will help in the development of new ROMs.
How to get the partition info on your device
Prerequisites:
Your device needs to be rooted.
You need to be able to get a root shell terminal on your phone, either using adb or using a terminal emulator app like "Termux" or "Terminal Emulator for Android". If you're going to be using a Terminal Emulator app on your phone, you'll find that the Hacker's Keyboard app will make your life much much easier when dealing with shells on the phone (ever tried to type any control character sequence at all, like CTRL+C, using all those cute fancy soft keyboards on the play store?)
You need to know how to use a terminal emulator and be comfortable with using shell commands (see Disclaimer above).
Method
Using ADB to get a root shell on your phone:
Ensure that you have the drivers for the phone installed on the computer. If not,
For Windows: just install the HiSuite app from Huawei to get the drivers. You can uninstall HiSuite immediately after it's installed (it's a useless piece of dreck, only useful for the drivers it installs) but the drivers will remain installed.
For Linux: The Android SDK for Linux should give you the generic ADB drivers. Then see this webpage for setting a proper USB device ID for Huawei devices in case you have issues. I have not yet tested this for myself, BTW.
Ensure that you have adb on your computer. If not,
For Windows: you can grab it from the Unlock guide thread.
For Linux: The Android SDK for Linux should have given you this already. If not, something is very very wrong with your universe.
Ensure that your phone is rooted. Follow the above-linked guide if you need to only if you are confident about being able to perform what's required and don't mind voiding your warranty and risking permanent damage to your phone and sanity. If your phone is not rooted, this is not going to work.
Connect your phone to the computer via USB.
Open up a command prompt. On Windows, this involves typing "cmd" in the search bar. On Linux, fire up the terminal app of your choice. I recommend gnome-terminal. Then navigate to the directory where the adb executable is located.
Check whether your device is recognized by adb. Type the following command:
Code:
adb devices
Your output should look something like this (the device ID in the output below will be particular to your phone):
Code:
List of devices attached
AAA0A1234567890 device
If your output doesn't look like the above, you may have a problem with the setup, and subsequent steps may not work. But we'll see.
Obtain a shell into your phone from adb:
Code:
adb shell
This should return a prompt into a shell on your phone which looks something like this:
Code:
[email protected]:/ $
Now convert that plain old shell into a root shell (you are rooted by now, aren't you?):
Code:
su
You should now be in a root shell, as evidenced by the following output (notice that the $ in the previous output changed to #):
Code:
[email protected]:/ #
Using a Terminal Emulator app on the phone to get a root shell:
Fire up the terminal emulator app on your phone (see the "Prerequisites" section above for a couple of suggestions on good terminal emulators I've personally used).
Type the following to get into a root shell in the terminal:
Code:
su
You should now be in a root shell, as evidenced by your prompt changing from $ to #.
Now we actually get to business! If you successfully got a root shell, it's time to issue the command to get the device partitions and their mappings! Type the following command exactly as shown (the cleverer folk can simple copy-paste it):
Code:
ls -l /dev/block/platform/hi_mci.0/by-name | tr -s ' ' | cut -d' ' -f6-8 > /storage/sdcard0/mypartitions.txt
The above command should put a list of partitions and their mappings into a text file called mypartitions.txt on the root directory of your phone's internal SD card mountpoint (if you want it put on your external SD card mountpoint, replace /storage/sdcard0/mypartitions.txt in the command with this: /storage/sdcard1/mypartitions.txt and you should find it placed accordingly).
The file mypartitions.txt can now be transferred from your phone to your computer via USB (or you can open it directly on your phone using a text editor) and add the info to a reply here.
Good luck!
Information on individual devices
Block Device/Partition Information for individual devices
Mediapad M2 8.0 (M2-802L)
Block Device/Partitions
Code:
vrl -> /dev/block/mmcblk0p1
vrl_backup -> /dev/block/mmcblk0p2
mcuimage -> /dev/block/mmcblk0p3
reserved0 -> /dev/block/mmcblk0p4
fastboot -> /dev/block/mmcblk0p5
modemnvm_factory -> /dev/block/mmcblk0p6
nvme -> /dev/block/mmcblk0p7
oeminfo -> /dev/block/mmcblk0p8
splash -> /dev/block/mmcblk0p9
modemnvm_backup -> /dev/block/mmcblk0p10
modemnvm_img -> /dev/block/mmcblk0p11
modemnvm_system -> /dev/block/mmcblk0p12
securetystorage -> /dev/block/mmcblk0p13
3rdmodemnvm -> /dev/block/mmcblk0p14
3rdmodemnvmback -> /dev/block/mmcblk0p15
reserved1 -> /dev/block/mmcblk0p16
modem_om -> /dev/block/mmcblk0p17
splash2 -> /dev/block/mmcblk0p18
misc -> /dev/block/mmcblk0p19
modemnvm_update -> /dev/block/mmcblk0p20
recovery2 -> /dev/block/mmcblk0p21
reserved2 -> /dev/block/mmcblk0p22
teeos -> /dev/block/mmcblk0p23
trustfirmware -> /dev/block/mmcblk0p24
sensorhub -> /dev/block/mmcblk0p25
hifi -> /dev/block/mmcblk0p26
boot -> /dev/block/mmcblk0p27
recovery -> /dev/block/mmcblk0p28
dtimage -> /dev/block/mmcblk0p29
modem -> /dev/block/mmcblk0p30
modem_dsp -> /dev/block/mmcblk0p31
dfx -> /dev/block/mmcblk0p32
3rdmodem -> /dev/block/mmcblk0p33
cache -> /dev/block/mmcblk0p34
hisitest0 -> /dev/block/mmcblk0p35
hisitest1 -> /dev/block/mmcblk0p36
hisitest2 -> /dev/block/mmcblk0p37
system -> /dev/block/mmcblk0p38
cust -> /dev/block/mmcblk0p39
userdata -> /dev/block/mmcblk0p40
CPU Info (gathered by CPU-Z)
Code:
CPUs : 8
SoCs : 1
CPU 0 : AArch64 Processor rev 3 (aarch64)
Name : HiSilicon Kirin 930
CPUs : 8
Core set 0 : ARM Cortex-A53
Core set 0 Nb Cores : 4
Core set 0 Max Clock : 2016 MHz
Core set 0 Impl.id : 0x41
Core set 0 Arch.id : 0x8
Core set 0 Var.id : 0
Core set 0 Part.id : 0xd03
Core set 0 Rev.id : 3
Core set 0 Revision : r0p3
Core set 1 : ARM Cortex-A53
Core set 1 NbCores : 4
Core set 1 Max Clock : 1516 MHz
Core set 1 Part.id : 0xd03
Arch : 4x ARM Cortex-A53 @2.02 GHz+4x ARM Cortex-A53 @1.52 GHz
Codename :
Process : 28 nm
GPU Vendor : ARM
GPU Renderer : Mali-T624
Model : HUAWEI M2-802L (M2)
Manufacturer : HUAWEI
Board : mozart
Hardware : hi3635
Android Ver. : 5.1.1
Kernel Arch. : armv7l
Battery capacity : 4650
--- CPUInfos ---
abi : armeabi-v7a
abi2 : armeabi
supported abis : [arm64-v8a, armeabi-v7a, armeabi]
supported 32-bit abis : [armeabi-v7a, armeabi]
supported 64-bit abis : [arm64-v8a]
Processor : AArch64 Processor rev 3 (aarch64)
processor : 0
processor : 1
processor : 2
processor : 3
processor : 4
processor : 5
processor : 6
processor : 7
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 wp half thumb fastmult vfp edsp neon vfpv3 tlsi vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 3
Hardware : Hisilicon Kirin 930
--- Debug Infos ---
16=667000000
17=120000000
18=0
19=120000000 240000000 360000000 400000000 667000000 800000000
20=cluster0=42
21=cluster1=25
22=gpu=37
23=modem=44
24=ddr=82
25=system_h=34
26=system_l=15
27=flash_led=29
28=charger=34
29=pa_0=30
30=Battery=29000
56=cluster0=41
57=cluster1=25
58=gpu=37
59=modem=44
60=ddr=82
clock 0=1516800
clock2 0=151600
clock 1=1516800
clock2 1=151600
clock 2=1516800
clock2 2=151600
clock 3=1516800
clock2 3=151600
clock 4=2016000
clock2 4=201600
clock 5=2016000
clock2 5=201600
clock 6=2016000
clock2 6=201600
clock 7=2016000
clock2 7=201600
Reserved
Reserved
Reserved 2
Version 2Works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Build Date:
2020/05/13
Android Version:
QP1A.190711.020
Display ID:
AL2522-Merlin-V039-Q-0513
Build Fingerprint:
Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
Security Patch:
2019/12/05
Radio/Modem/Baseband Version:
MOLY.LR12A.R3.MP.V94.3
Kernel Version:
4.14.141-gf3c3c7a
Wed May 13 12:49:46 CST 2020
Download:
https://www.mediafire.com/file/02xo...V039-Q-0513_QP1A.190711.020_by-VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
How to flash it?
Use any scatter file specific for MERLIN.
Radio/Modem/Baseband properties:
Code:
md1_dbginfodsp=DbgInfo_DSP_MT6768_MOLY_LR12A_R3_MP_V94_3_2019_12_31_16_23.xz
md1_dbginfo=DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_03_26_19_19.xz
md1_mddbmeta=MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB
md1_mddbmetaodb=MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.XML.GZ
md1_mddb=MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB
Prop.default:
Code:
ro.build.version.incremental=258
ro.odm.build.version.incremental=258
ro.vendor.build.version.incremental=258
ro.build.version.security_patch=2019-12-05
ro.vendor.build.security_patch=2019-12-05
ro.build.display.id=AL2522-Merlin-V039-Q-0513
ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp2-V1.4_huaqin.q0mp1.k69v1.64_P1
ro.build.product=merlin
ro.product.board=merlin
ro.product.odm.device=merlin
ro.product.odm.model=merlin
ro.product.odm.name=merlin
ro.product.product.device=merlin
ro.product.product.model=merlin
ro.product.product.name=merlin
ro.product.system.device=merlin
ro.product.system.model=merlin
ro.product.system.name=merlin
ro.product.vendor.device=merlin
ro.product.vendor.model=merlin
ro.product.vendor.name=merlin
ro.build.flavor=merlin-userdebug
ro.build.description=merlin-userdebug 10 QP1A.190711.020 258 test-keys
ro.board.platform=mt6768
ro.build.id=QP1A.190711.020
ro.odm.build.id=QP1A.190711.020
ro.product.build.id=QP1A.190711.020
ro.system.build.id=QP1A.190711.020
ro.vendor.build.id=QP1A.190711.020
ro.bootimage.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.product.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.system.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.build.tags=test-keys
ro.odm.build.tags=test-keys
ro.system.build.tags=test-keys
ro.vendor.build.tags=test-keys
ro.build.type=userdebug
ro.odm.build.type=userdebug
ro.system.build.type=userdebug
ro.vendor.build.type=userdebug
ro.bootimage.build.date=Wed May 13 12:41:51 CST 2020
ro.build.date=Wed May 13 12:41:51 CST 2020
ro.odm.build.date=Wed May 13 12:41:51 CST 2020
ro.product.build.date=Wed May 13 12:41:51 CST 2020
ro.system.build.date=Wed May 13 12:41:51 CST 2020
ro.vendor.build.date=Wed May 13 12:41:51 CST 2020
MD5 hashes:
Code:
APDB_MT6768_S01__W1953 -> 3adfe0c4e41828cd51ed783da774bd08
boot-debug.img -> e9dfb7dde67795157a871bc14b490054
boot.img -> d6e19a30d85a27379d91072665ad43c9
cache.img -> c40c137a18a26980d406d4ef0ccd7e61
cust.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_03_26_19_19_1_ulwctg_n -> b5bf654ddaacfd61e78c131f721974af
dtb.img -> ec4b37b164f1bd9ce6f2b1b911ac0872
dtbo-verified.img -> 9b0fa19089a0310325b88eebc8e41ae7
dtbo.img -> 9b0fa19089a0310325b88eebc8e41ae7
efuse.img -> 421f2cead0fbea555680b96136555941
exaid.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
lk-verified.img -> 0ba475d8c216b2613815b59e3db8da2b
lk.img -> 0ba475d8c216b2613815b59e3db8da2b
logo.bin -> 257508aa9cdeb690e4a4ed038c91ff76
md1arm7.img -> a0453e723dc84255940d7791740d06db
md1img-verified.img -> 27cd78644df092ade4ca03799dc3c2a3
md1img.img -> 27cd78644df092ade4ca03799dc3c2a3
md3img.img -> 9a9c185e3f6234103e5949716b9962d2
MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.XML.GZ -> 4e040508c1878706a428c54ef0844e0f
MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> 7c1ecfd4e3d626957b6655f107824649
MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> b24757bd125ad435bd2d26575b5c1d75
MT6768_Android_scatter.txt -> 0a8f16b2276ee9c37337a3937f71a7c8
preloader.img -> dbc21da31860042674fab69d07444e95
preloader_emmc.img -> dbc21da31860042674fab69d07444e95
preloader_merlin.bin -> bc7ebc0c2ca06b0d99856d595949e215
preloader_ufs.img -> 29ef0e631a45bf14555fd6b7adb7a7bf
product.img -> 7ec4f1ffd2b49d7c5b4f1bb5d3ba0dc6
ramdisk-debug.img -> b6048055b240d3c9f6933544b86416b5
ramdisk-recovery.img -> 77de275ef543e46bbedfd53b7e36f945
ramdisk.img -> 545ec84cf25662d1e4f4cf7e496fa56e
recovery.img -> 6362f1beb617572680f3fc91640d3767
scp-verified.img -> 2cac6177dc7eec82421cb3f4a2776aff
scp.img -> 2cac6177dc7eec82421cb3f4a2776aff
secro.img -> 096587b863e1252d67b1b8307291db09
spmfw-verified.img -> 40345cc1edec88bcd510fa62eac01739
spmfw.img -> 40345cc1edec88bcd510fa62eac01739
sspm-verified.img -> 0ceaf392e89bf70c9a52a5c91cc75865
sspm.img -> 0ceaf392e89bf70c9a52a5c91cc75865
super.img -> d3a61d5292e4584bb3932abb7d6984bf
super_empty.img -> a6d56d7a12d989bf31511d866449291d
system.img -> 1a191b461d47c0a7bf8ce08d3c09001e
tee-verified.img -> 4f2fdf78d5be3a5de0154c46af69d476
tee.img -> 4f2fdf78d5be3a5de0154c46af69d476
userdata.img -> 802561cd4739f2f0aae7a51890a5866f
vbmeta.img -> 31da88d4a00b99b36081f859f17f808a
vbmeta_system.img -> a6b560b53a42c98fba204f2b69e70fd7
vbmeta_vendor.img -> 86fae46d211bdedcb49bd08e901d4d3f
vendor.img -> e609cb6a9d7ae103a64d9fe856d4edae
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
What's different in V2 and the one which was posted earlier?
Communos said:
What's different in V2 and the one which was posted earlier?
Click to expand...
Click to collapse
Its funny how VD171 never mention about the difference of this v2 to the old one
What is engineering firmware?
Bharath kota said:
What is engineering firmware?
Click to expand...
Click to collapse
A ROM with few or minor security patches.
Essentialy for doing things not allowed in released firmwares.
Sorry, what is the password?, I can't find
eric_new_master said:
Sorry, what is the password?, I can't find
Click to expand...
Click to collapse
On the attachment "PASSWORD_by_VD171.txt".
VD171 said:
On the attachment "PASSWORD_by_VD171.txt".
Click to expand...
Click to collapse
the thing is that now winrar doesnt let us open files inside an archive without a password so we cant access it now. i just guessed it and it
worked. lol
Kaustubh Mishra said:
the thing is that now winrar doesnt let us open files inside an archive without a password so we cant access it now. i just guessed it and it
worked. lol
Click to expand...
Click to collapse
and i didnt see the attachment too. lol im a fool
Kaustubh Mishra said:
and i didnt see the attachment too. lol im a fool
Click to expand...
Click to collapse
The file is attached on the thread:
https://forum.xda-developers.com/attachments/password_by_vd171-txt.5249247/
Volte not working for Merlin Redmi note 9 ( Indian user).
Volte option is available in setting menu. But volte not working.
Works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Build Date:
2020/09/20
Android Version:
QP1A.190711.020
Display ID:
AL2522-Merlin-V044-Q-0920
Build Fingerprint:
Redmi/merlin/merlin:10/QP1A.190711.020/17:userdebug/test-keys
Security Patch:
2019-12-05
Radio/Modem/Baseband Version:
MOLY.LR12A.R3.MP.V94.3
Download:
https://www.mediafire.com/file/4nky...V044-Q-0920_QP1A.190711.020_by-VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
How to flash it?
Use the attached scatter file.
Radio/Modem/Baseband properties:
Code:
md1_dbginfodsp=DbgInfo_DSP_MT6768_MOLY_LR12A_R3_MP_V94_3_2019_12_31_16_23.xz
md1_dbginfo=DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_08_12_17_38.xz
md1_mddbmeta=MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB
md1_mddbmetaodb=MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.XML.GZ
md1_mddb=MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB
Prop.default:
Code:
ro.build.version.incremental=17
ro.vendor.build.version.incremental=17
ro.odm.build.version.incremental=17
ro.build.version.security_patch=2019-12-05
ro.vendor.build.security_patch=2019-12-05
ro.build.display.id=AL2522-Merlin-V044-Q-0920
ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp2-V1.4_huaqin.q0mp1.k69v1.64_P1
ro.product.system.device=merlin
ro.product.system.model=merlin
ro.product.system.name=merlin
ro.build.product=merlin
ro.product.board=merlin
ro.product.vendor.device=merlin
ro.product.vendor.model=merlin
ro.product.vendor.name=merlin
ro.product.odm.device=merlin
ro.product.odm.model=merlin
ro.product.odm.name=merlin
ro.product.product.device=merlin
ro.product.product.model=merlin
ro.product.product.name=merlin
ro.build.flavor=merlin-userdebug
ro.build.description=merlin-userdebug 10 QP1A.190711.020 17 test-keys
ro.board.platform=mt6768
ro.system.build.id=QP1A.190711.020
ro.build.id=QP1A.190711.020
ro.vendor.build.id=QP1A.190711.020
ro.odm.build.id=QP1A.190711.020
ro.product.build.id=QP1A.190711.020
ro.system.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/17:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/17:userdebug/test-keys
ro.bootimage.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/17:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/17:userdebug/test-keys
ro.product.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/17:userdebug/test-keys
ro.system.build.tags=test-keys
ro.build.tags=test-keys
ro.vendor.build.tags=test-keys
ro.odm.build.tags=test-keys
ro.system.build.type=userdebug
ro.build.type=userdebug
ro.vendor.build.type=userdebug
ro.odm.build.type=userdebug
ro.system.build.date=Sun Sep 20 21:42:19 CST 2020
ro.build.date=Sun Sep 20 21:42:19 CST 2020
ro.vendor.build.date=Sun Sep 20 21:42:19 CST 2020
ro.bootimage.build.date=Sun Sep 20 21:42:19 CST 2020
ro.odm.build.date=Sun Sep 20 21:42:19 CST 2020
ro.product.build.date=Sun Sep 20 21:42:19 CST 2020
MD5 hashes:
Code:
APDB_MT6768_S01__W1953 -> 3adfe0c4e41828cd51ed783da774bd08
boot-debug.img -> d83c79ff64413cee79261a019598843b
boot.img -> cf47a73562cfd84a7337b37637eb8cef
cache.img -> 3cf2afe595f5bce984fe128b0c7ffad7
Checksum.ini -> d7d0d34a198008b9e6fb0c05ae541473
crclist.txt -> 92dd74d56feaecf23e79df4f48f84d5b
cust.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_08_12_17_38_1_ulwctg_n -> e0403cc778e00cb658cd02b609ab07c2
dtb.img -> ec4b37b164f1bd9ce6f2b1b911ac0872
dtbo-verified.img -> 5ca7b2b8dbbcd5e8239fc86b9e7b5d19
dtbo.img -> 5ca7b2b8dbbcd5e8239fc86b9e7b5d19
efuse.img -> 421f2cead0fbea555680b96136555941
exaid.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
flash_all.bat -> a4c24e0551a1386f6e51f36d2d6bdc59
flash_all.sh -> dc8d312852f0a8ac1eb19bbf1aa548b4
flash_all_except_data_storage.bat -> b87fa122acd47a2c56f395d827279e85
flash_all_except_data_storage.sh -> 31d39c3cca6c4cc9d1faada57df05631
flash_all_lock.bat -> 4f72649c336b7851456dd195b054553d
flash_all_lock.sh -> ddc1c485c8ae8bdd3b7aa6c25f4aec68
flash_gen_md5_list.py -> dd670ee88280d308473a7aff355b975d
hat_extract.py -> cbf07a5e8389476f4ed71e34dcbd7591
hat_flash.sh -> fa3bdd091388cdb3fff69421cf4187cd
lk-verified.img -> fb9cf4a240ebca771322c8c8b1cbee0f
lk.img -> fb9cf4a240ebca771322c8c8b1cbee0f
logo.bin -> e5d5093b5d3c4a194717d286ae40b440
md1arm7.img -> a0453e723dc84255940d7791740d06db
md1img-verified.img -> 5d366d0581c6b7b6cee7c571994a9ed3
md1img.img -> 5d366d0581c6b7b6cee7c571994a9ed3
md3img.img -> 9a9c185e3f6234103e5949716b9962d2
MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.XML.GZ -> e6a7041c231f66869b7f99e4cb059047
MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> 90f2b755306720c9a027f847940aadab
MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> c70b510b9b27f5cce9d26c7e8330fe01
MT6768_Android_scatter.txt -> 0a8f16b2276ee9c37337a3937f71a7c8
preloader.img -> ff20fc3953e5118120a86453e7ae8f94
preloader_emmc.img -> ff20fc3953e5118120a86453e7ae8f94
preloader_merlin.bin -> d2c78e614adf75b98b2b6de74dfb4675
preloader_ufs.img -> 75476892bff904450c5ae508b2eb77f7
product.img -> 70caf1a9a02a51c7d9ab82da995179b3
ramdisk-debug.img -> b6048055b240d3c9f6933544b86416b5
ramdisk-recovery.img -> 2b548447b982a6479c337248cb107923
ramdisk.img -> 545ec84cf25662d1e4f4cf7e496fa56e
recovery.img -> f3d00ee3de8ba4598318c3a80fdbad63
scp-verified.img -> 59c5f50b8c122a4ee24d02a24aa61c24
scp.img -> 59c5f50b8c122a4ee24d02a24aa61c24
secro.img -> 096587b863e1252d67b1b8307291db09
sparsecrclist.txt -> f86c5c6014c64c10f2dc46e5c83cab8e
spmfw-verified.img -> e35bd811230ff7766be8eb25e6c5be75
spmfw.img -> e35bd811230ff7766be8eb25e6c5be75
sspm-verified.img -> 92c771de8cf02d3f0b9f43ae53518218
sspm.img -> 92c771de8cf02d3f0b9f43ae53518218
super.img -> 6afd5e925807b8a2c42c9cbc731972ff
super_empty.img -> a6d56d7a12d989bf31511d866449291d
system.img -> 08c18ce6844b539e4ac3317195c0485b
tee-verified.img -> 56721dfff0af3f502b5bbb8d9d0006c1
tee.img -> 56721dfff0af3f502b5bbb8d9d0006c1
userdata.img -> 0a3dc9f623c1206749ad1093bfa44081
vbmeta.img -> 5003b40cb64cfcd77b9f85fc2cc8f478
vbmeta_system.img -> f67c111ba47702b2e81cd366fa169bec
vbmeta_vendor.img -> 69e70abba51250749258e53e3f6d681d
vendor.img -> 39af156489f31da6b1d2243e5daa6973
Please can someone help me because I flashed this eng rom on my bootloader unlocked redmi Merlin with IMEI null issue, after flashing the phone stays in miui logo for ever. I have tried the versions of engineering rom available both here and halabtech site. The version of the current stock firmware on my device was V12.5.4. Please any help as to get the IMEI number of the phone back.
What is the difference between v1, v2 and v3?
Is there anything that specific one should be used?