Works with:
- Xiaomi Redmi 9
- Xiaomi Redmi 9 Prime
Build Date:
2020/11/13
Android Version:
QP1A.190711.020
Display ID:
dandelion-userdebug 10 QP1A.190711.020 440 test-keys
Build Fingerprint:
Redmi/dandelion/dandelion:10/QP1A.190711.020/440:userdebug/test-keys
Security Patch:
2020-03-05
Radio/Modem/Baseband Version:
MOLY.LR12A.R3.MP.V98.P49
Download:
https://www.mediafire.com/file/3w00...V016-Q-0918_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_V98_P49_2020_06_28_11_09.xz
md1_dbginfo=DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V98_P49_2020_06_30_17_53.xz
md1_mddbmeta=MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V98_P49.EDB
md1_mddbmetaodb=MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V98_P49.XML.GZ
md1_mddb=MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V98_P49.EDB
Prop.default:
Code:
ro.build.version.incremental=20
ro.vendor.build.version.incremental=20
ro.odm.build.version.incremental=20
ro.build.version.security_patch=2019-12-05
ro.vendor.build.security_patch=2019-12-05
ro.build.display.id=AL2615-lancelot-V016-Q-0918
ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp2-V1.9.1_huaqin.q0mp1.k69v1.64_P17
ro.product.system.device=lancelot
ro.product.system.model=lancelot
ro.product.system.name=lancelot
ro.build.product=lancelot
ro.product.board=lancelot
ro.product.vendor.device=lancelot
ro.product.vendor.model=lancelot
ro.product.vendor.name=lancelot
ro.product.odm.device=lancelot
ro.product.odm.model=lancelot
ro.product.odm.name=lancelot
ro.product.product.device=lancelot
ro.product.product.model=lancelot
ro.product.product.name=lancelot
ro.build.flavor=lancelot-userdebug
ro.build.description=lancelot-userdebug 10 QP1A.190711.020 20 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/lancelot/lancelot:10/QP1A.190711.020/20:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/lancelot/lancelot:10/QP1A.190711.020/20:userdebug/test-keys
ro.bootimage.build.fingerprint=Redmi/lancelot/lancelot:10/QP1A.190711.020/20:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/lancelot/lancelot:10/QP1A.190711.020/20:userdebug/test-keys
ro.product.build.fingerprint=Redmi/lancelot/lancelot:10/QP1A.190711.020/20: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=Fri Sep 18 22:19:19 CST 2020
ro.build.date=Fri Sep 18 22:19:19 CST 2020
ro.vendor.build.date=Fri Sep 18 22:19:19 CST 2020
ro.bootimage.build.date=Fri Sep 18 22:19:19 CST 2020
ro.odm.build.date=Fri Sep 18 22:19:19 CST 2020
ro.product.build.date=Fri Sep 18 22:19:19 CST 2020
MD5 hashes:
Code:
APDB_MT6768_S01__W2006 -> 7177e8c1bb17e5fd98f0e6723799c50d
boot-debug.img -> 4554a3ae2c6e29a48b2550f2a9ba0059
boot.img -> 8b017ceb0d1fb8cfba84edb3d075a3da
cache.img -> 6972e40cf2fab817af657638ef074d44
Checksum.ini -> 27f0bde03463632c322fc0afb67c446c
crclist.txt -> f23ab0e10114086a411a3bdd36c2e935
cust.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V98_P14_2020_04_02_09_21_1_ulwctg_n -> b98ee0dd6410d951a97dc06195ba83e8
dtb.img -> bfe051e750bab9942d3509be26852f76
dtbo-verified.img -> cb8f212deca67eac25064b736e6ab722
dtbo.img -> cb8f212deca67eac25064b736e6ab722
efuse.img -> 421f2cead0fbea555680b96136555941
exaid.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
flash_all.bat -> 2e9b6766c41f291f6ed47c28cf476396
flash_all.sh -> 2fbbf3a1ad0556f5750da749007fbfb5
flash_all_except_data_storage.bat -> b3eae922880d6de2ef1ccbbbe04eb491
flash_all_except_data_storage.sh -> 046f69b79cef396dfeb3fa16a6e0a702
flash_all_lock.bat -> 118f2f4a04889d5b56cc0a4d9ae1148e
flash_all_lock.sh -> 7b905c508c810a28cfbcfbb51ee718eb
flash_gen_md5_list.py -> dd670ee88280d308473a7aff355b975d
hat_extract.py -> cbf07a5e8389476f4ed71e34dcbd7591
hat_flash.sh -> fa3bdd091388cdb3fff69421cf4187cd
lk-verified.img -> 3f7bccf0ce4e391845c4c4d807a21f0a
lk.img -> 3f7bccf0ce4e391845c4c4d807a21f0a
logo.bin -> d8701054eb8587fec3c7827d44361385
md1arm7.img -> a0453e723dc84255940d7791740d06db
md1img-verified.img -> e3980a4c60a54bdf58e09e1172659d1a
md1img.img -> e3980a4c60a54bdf58e09e1172659d1a
md3img.img -> 9a9c185e3f6234103e5949716b9962d2
MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V98_P14_1_ulwctg_n.XML.GZ -> 376361df52cddd8e2d8127c009ad9a97
MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V98_P14_1_ulwctg_n.EDB -> 762c8ba299c76dde214394d8e7e3fc7e
MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V98_P14_1_ulwctg_n.EDB -> a5757c7b6acf3e52ce051d731f1e11ab
MT6768_Android_scatter.txt -> 49ccb3ee5ebcd5a1da213f6e6a97f6e0
preloader.img -> f8518bd0ea6b1e141f44a6ef0ef8a999
preloader_emmc.img -> f8518bd0ea6b1e141f44a6ef0ef8a999
preloader_lancelot.bin -> 06f72184cadcbe4b23c858a533aab1c3
preloader_ufs.img -> a567cfe99bcf994eb1a4450be29e9d46
product.img -> 9670aa56e5c8c2b3df3738840c29d8b6
ramdisk-debug.img -> e983139c5a4a17f856b48a9168462246
ramdisk-recovery.img -> 9d154bc54802d9bb300460d47e466678
ramdisk.img -> b280f1a76fd113fa4a2819c131bd5a4b
recovery.img -> 2aeb935e9e4ebfdf8a5f24a6afe84a2c
scp-verified.img -> 3173d15281606ed65d30125786df26a8
scp.img -> 3173d15281606ed65d30125786df26a8
secro.img -> 096587b863e1252d67b1b8307291db09
sparsecrclist.txt -> 18c229554165f5ab08760f77a8cb7171
spmfw-verified.img -> 3c1ea62d3b90ba09910b21b5967177be
spmfw.img -> 3c1ea62d3b90ba09910b21b5967177be
sspm-verified.img -> e298071c20c2cb4e2d3a82bf11232953
sspm.img -> e298071c20c2cb4e2d3a82bf11232953
super.img -> 108f18840dc902c7caaade3219b703b9
super_empty.img -> a6d56d7a12d989bf31511d866449291d
system.img -> b222d039308ba3ed86259418836e987c
tee-verified.img -> 18cf1db4268682f26f621b22dcdb2e55
tee.img -> 18cf1db4268682f26f621b22dcdb2e55
userdata.img -> f587cb8342ac2e4b081d2655d71c8913
vbmeta.img -> 33424ed5ce956942dbc935ab54ff4cc5
vbmeta_system.img -> 7450f65dc4afef75b2d25c24d20ff077
vbmeta_vendor.img -> 66bd3b645785e28e4046394d66a46e0e
vendor.img -> 1b11032ffa59c02c2c97f911d508f4a3
after updating to lancelot_global_images_V12.5.3.0.RJCMIXM_20211017.0000.00_11.0_global
i can no longer make this eng rom works every time i flash it the phone goes in erasing boot loop until I go back to the latest global rom
coliotte said:
after updating to lancelot_global_images_V12.5.3.0.RJCMIXM_20211017.0000.00_11.0_global
i can no longer make this eng rom works every time i flash it the phone goes in erasing boot loop until I go back to the latest global rom
Click to expand...
Click to collapse
Engineering rom and stock rom has different partitions tables.
So, if you are in one and want to flash another, you need to flash partition table again.
This can be done flashing the rom using spflashtool.
i flashed using spflash tool and Ultimate Multi Tool - MTK and nck tool
flash normal but boot loop after this same eng from used to work but after update it become boot looping.
unlocking the bootloader didn't help eather
do you have J19-AL2615-lancelot-V016-Q-0918 ?
am not sure but I think this is a new version am not sure how to solve this I haven't seen someone with this problem yet
coliotte said:
i flashed using spflash tool and Ultimate Multi Tool - MTK and nck tool
flash normal but boot loop after this same eng from used to work but after update it become boot looping.
unlocking the bootloader didn't help eather
do you have J19-AL2615-lancelot-V016-Q-0918 ?
am not sure but I think this is a new version am not sure how to solve this I haven't seen someone with this problem yet
Click to expand...
Click to collapse
You may need to format data.
For anyone with a Redmi 9, I finally flashed the ENG rom after days of trying with the attached files:
Related
hey everyone,
i have an odd problem with my moto z . as i mentiond in title i didn't get any updates so i can't get nougat 7.1.1 and my security level patch i kinda too old as you will see in photos
i have tried doing both soft reset -reset factory setting- and a hard reset but nothing changes still unable to get any updates nether security updates of android updates
here is my phone channel and build version and security level and other stuff in this photo
Try remove SIM Card, reboot and search for Updates in Your WLAN/WiFi witout a SIM Card.
Tou can use this tool https://forum.xda-developers.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039 to download the OTA's to your computer, then use adb sideload on Motorola's Recovery (OEM) to manually update, no need to root or unlock bootloader if you stick with oficial updates.
I just did something similar on my Z, here is overall the path, version wise
Code:
Version:
Blur_Version.NPL25.86.30
Android 7.0.0 initial
================================================================
Version :
NPLS25.86.30-5.griffin.retail.en.US
Display Version :
NPLS25.86-30-5
Android Security updates up until Feb 1st 2017
================================================================
Version :
Blur_Version.25.211.8.NPLS25.86.30-8.retail.en.US
Display Version :
NPLS25.86-30-8
Android Security updates up until March 1st 2017
===============================================================
Version :
Blur_Version.25.221.12.griffin.retail.en.US
Display Version :
NPLS25.86-30-12
Android Security updates up until April 1st 2017
================================================================
Version :
Blur_Version.26.51.19.griffin.retail.en.US
Display Version :
NPL26.118-20
Highlights of this update include:
Android™ 7.1.1 Nougat.
Android security updates up to 1 July 2017.
================================================================
Version :
Blur_Version.26.201.1.griffin.retail.en.US
Display Version :
NPLS26.118-20-1
Android security updates up to 1 August 2017.
================================================================
Version :
Blur_Version.26.211.5.griffin.retail.en.US
Display Version :
NPL26.118-20-5
Android security updates up to 1 September 2017.
Boot-up stability improvement.
Moto 360 stability improvement.
================================================================
Version :
Blur_Version.26.221.3.griffin.retail.en.US
Display Version :
NPLS26.118-20-5-3
Android security updates up to 1 October 2017.
To get to Blur_Version.NPL25.86.30 you can also use the steps at this thread: https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
Good luck!
ztryfe said:
Tou can use this tool https://forum.xda-developers.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039 to download the OTA's to your computer, then use adb sideload on Motorola's Recovery (OEM) to manually update, no need to root or unlock bootloader if you stick with oficial updates.
I just did something similar on my Z, here is overall the path, version wise
Code:
Version:
Blur_Version.NPL25.86.30
Android 7.0.0 initial
================================================================
Version :
NPLS25.86.30-5.griffin.retail.en.US
Display Version :
NPLS25.86-30-5
Android Security updates up until Feb 1st 2017
================================================================
Version :
Blur_Version.25.211.8.NPLS25.86.30-8.retail.en.US
Display Version :
NPLS25.86-30-8
Android Security updates up until March 1st 2017
===============================================================
Version :
Blur_Version.25.221.12.griffin.retail.en.US
Display Version :
NPLS25.86-30-12
Android Security updates up until April 1st 2017
================================================================
Version :
Blur_Version.26.51.19.griffin.retail.en.US
Display Version :
NPL26.118-20
Highlights of this update include:
Android™ 7.1.1 Nougat.
Android security updates up to 1 July 2017.
================================================================
Version :
Blur_Version.26.201.1.griffin.retail.en.US
Display Version :
NPLS26.118-20-1
Android security updates up to 1 August 2017.
================================================================
Version :
Blur_Version.26.211.5.griffin.retail.en.US
Display Version :
NPL26.118-20-5
Android security updates up to 1 September 2017.
Boot-up stability improvement.
Moto 360 stability improvement.
================================================================
Version :
Blur_Version.26.221.3.griffin.retail.en.US
Display Version :
NPLS26.118-20-5-3
Android security updates up to 1 October 2017.
To get to Blur_Version.NPL25.86.30 you can also use the steps at this thread: https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
Good luck!
Click to expand...
Click to collapse
I have a similar problem, I have not received the update to Android 7.1, I have a Moto Z xt1650-03 With the company at&t Mexico, Can I do this procedure without problems? https forum.xda-developers.com/mot...oto-z-t3640298
These are the data of my phone:
Software Chanel: attmx
Android patch security level: April 1, 2017
Baseband Version: M8996_1239.53.01.126R SRS
Kernel Version: [email protected] #1
Thundercats mar 30 03:09:48 CDT 2017
Build Number: NPLS25.86-30-12
mohmyo said:
hey everyone,
i have an odd problem with my moto z . as i mentiond in title i didn't get any updates so i can't get nougat 7.1.1 and my security level patch i kinda too old as you will see in photos
i have tried doing both soft reset -reset factory setting- and a hard reset but nothing changes still unable to get any updates nether security updates of android updates
here is my phone channel and build version and security level and other stuff in this photo
Click to expand...
Click to collapse
Flash your rom again using this commands
fastboot devices
************************
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
*************************
fastboot reboot
Einar1 said:
I have a similar problem, I have not received the update to Android 7.1, I have a Moto Z xt1650-03 With the company at&t Mexico, Can I do this procedure without problems? https forum.xda-developers.com/mot...oto-z-t3640298
These are the data of my phone:
Software Chanel: attmx
Android patch security level: April 1, 2017
Baseband Version: M8996_1239.53.01.126R SRS
Kernel Version: [email protected] #1
Thundercats mar 30 03:09:48 CDT 2017
Build Number: NPLS25.86-30-12
Click to expand...
Click to collapse
Hey, I am on the same channel, you can follow these version numbers and get the OTA's from the first link to sideload them, it should be safe, just understand what you're doing and go at it one by one, restarting in between.
Buena suerte
Hiya folks! I'm trying to play with the firmware files for the P30 Pro, and have hit a roadblock. While I've gotten to extract the system.img (and all the other .img images) from update.app, I'm not able to mount or extract it using any of the usual tools because they are using EROFS file system.
I'm using Ubuntu 18.04 LTS, but haven't been able to spend much time on figuring out how to mount or access EROFS file systems yet. Has anyone gotten this figured out already? Any help will be great, thanks!
It started with that question, leading to finding the solution to mount the system.img, building mkfs.erofs and trying out a system.img etc.
I do not intend to work much on this, at least for quite a while owing to RL situations. In case anyone wants to build on this, please go ahead - everything I've used has a git that is linked appropriately
ph03n!x said:
In case anyone's looking to mount the erofs images from the stock firmware, here's what you have to do -
Download and extract UPDATE.APP from the firmware zip, and use splitupdate binary/ perl script or Huawei Update Extractor. (I have linked to the tools I have tried or used in the past)
Use simg2img to convert the system.img (or product.img or vendor.img) to raw format. simg2img is a part of android fsutils
Code:
sudo apt install android-tools-fsutils
You will need a linux box or VM with Kernel 5.x running (erofs support is added from 4.20, but I am running 5.x) - mount the raw image using
Code:
sudo mount -t erofs -o loop system.ext4.img /home/test/mnt/try2
(The "-t erofs" is optional - will work just fine with sudo mount -o loop system.ext4.img /home/test/mnt/try2)
You will get the erofs image mounted in the folder you've specified, and you can browse through it
Note that erofs images are not meant to be editable. If you want to modify the system.img, extract it's content and create a new system.img using the mkfs.erofs binary (I had linked to the source code). You'll of course need an unlocked bootloader to flash (or boot) the modified image
Click to expand...
Click to collapse
For building mkfs.erofs, here's what you need to do (mine is a Ubuntu 19.04 machine)
Code:
git clone https://kernel.googlesource.com/pub/scm/linux/kernel/git/xiang/erofs-utils.git -b dev
./autogen.sh
./configure
make
You will have the output in the mkfs/ folder.
More details from this post -
ph03n!x said:
@oslo83 I have attached the mkfs.erofs binary using this git source to the first post.
Please go through the README for this - I built this binary for the x64 architecture, and for lz4-1.9.0
The command options are -
Code:
mkfs.erofs 0.1
usage: [options] FILE DIRECTORY
Generate erofs image from DIRECTORY to FILE, and [options] are:
-zX[,Y] X=compressor (Y=compression level, optional)
-d# set output message level to # (maximum 9)
Note that the system.img that comes within UPDATE.APP is a root file system - here is a structure.
Code:
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodem
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodemnvm
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodemnvmbkp
drwxr-xr-x. 2 root root 0 Aug 7 2018 acct
lrw-r--r--. 1 root root 11 Aug 7 2018 bin -> /system/bin
lrw-r--r--. 1 root root 50 Aug 7 2018 bugreports -> /data/user_de/0/com.android.shell/files/bugreports
drwxrwx---. 2 ph03n1x 2001 0 Aug 7 2018 cache
lrw-r--r--. 1 root root 13 Aug 7 2018 charger -> /sbin/charger
dr-xr-xr-x. 2 root root 0 Aug 7 2018 config
drwxr-xr-x. 2 root root 0 Aug 7 2018 cust
lrw-r--r--. 1 root root 17 Aug 7 2018 d -> /sys/kernel/debug
drwxrwx--x. 2 ph03n1x ph03n1x 0 Aug 7 2018 data
drwxrwx--x. 2 ph03n1x ph03n1x 0 Aug 7 2018 data_old
lrw-------. 1 root root 23 Aug 7 2018 default.prop -> system/etc/prop.default
drwxr-xr-x. 2 root root 0 Aug 7 2018 dev
drwxr-xr-x. 2 root root 35 Aug 7 2018 dload
drwxr-xr-x. 2 root root 0 Aug 7 2018 eng
lrw-r--r--. 1 root root 11 Aug 7 2018 etc -> /system/etc
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1024m
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1280m
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1536m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram2240m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram256m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram4096m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram512m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram768m
-?????????? ? ? ? ? ? init
-rwxr-x---. 1 root 2000 1717 Aug 7 2018 init.environ.rc
-?????????? ? ? ? ? ? init.rc
-?????????? ? ? ? ? ? init.usb.configfs.rc
-?????????? ? ? ? ? ? init.usb.rc
-rwxr-x---. 1 root 2000 580 Aug 7 2018 init.zygote32.rc
-rwxr-x---. 1 root 2000 1042 Aug 7 2018 init.zygote64_32.rc
lrw-r--r--. 1 root root 8 Aug 7 2018 log -> /splash2
drwxr-xr-x. 2 root ph03n1x 0 Aug 7 2018 mnt
drwxr-xr-x. 2 root root 0 Aug 7 2018 modem_log
drwxr-xr-x. 2 root root 0 Aug 7 2018 odm
drwxr-xr-x. 2 root root 0 Aug 7 2018 oem
drwxr-xr-x. 6 root root 71 Aug 7 2018 patch
drwxr-xr-x. 2 root root 0 Aug 7 2018 patch_hw
drwxr-xr-x. 2 root root 0 Aug 7 2018 preload
drwxr-xr-x. 2 root root 0 Aug 7 2018 proc
drwxr-xr-x. 2 root root 0 Aug 7 2018 product
drwxr-xr-x. 2 root root 47 Aug 7 2018 res
-rw-r--r--. 1 root root 32 Aug 7 2018 resetFactory.cfg
drwxr-xr-x. 2 root root 0 Aug 7 2018 root
drwxr-x---. 2 root 2000 183 Aug 7 2018 sbin
lrw-r--r--. 1 root root 21 Aug 7 2018 sdcard -> /storage/self/primary
drwxr-xr-x. 2 root root 0 Aug 7 2018 sec_storage
drwxr-xr-x. 2 root root 0 Aug 7 2018 splash2
drwxr-x--x. 2 root 1028 0 Aug 7 2018 storage
drwxr-xr-x. 2 root root 0 Aug 7 2018 sys
drwxr-xr-x. 23 root root 478 Aug 7 2018 system
-?????????? ? ? ? ? ? ueventd.rc
drwxr-xr-x. 2 root 2000 0 Aug 7 2018 vendor
-rw-r--r--. 1 root root 524 Aug 7 2018 verity_key
drwxr-xr-x. 2 root root 0 Aug 7 2018 version
It would be good if you spend time with the system.img, vendor.img, product.img and understand how the structures are inter-linked. Happy hunting!
Click to expand...
Click to collapse
ph03n!x said:
Hiya folks! I'm trying to play with the firmware files for the P30 Pro, and have hit a roadblock. While I've gotten to extract the system.img (and all the other .img images) from update.app, I'm not able to mount or extract it using any of the usual tools because they are using EROFS file system.
I'm using Ubuntu 18.04 LTS, but haven't been able to spend much time on figuring out how to mount or access EROFS file systems yet. Has anyone gotten this figured out already? Any help will be great, thanks!
Click to expand...
Click to collapse
Current tools aren't working with EROFS, we will need new ones, compatible with EROFS.
Update as of today -
I have cloned erofs-utils git and have compiled mkfs for creating EROFS images. Will work on it whenever I have time to see if I can get an img to mount...
UPDATE 2 - SUCCESS!
In case anyone's looking to mount the erofs images from the stock firmware, here's what you have to do -
Download and extract UPDATE.APP from the firmware zip, and use splitupdate binary/ perl script or Huawei Update Extractor. (I have linked to the tools I have tried or used in the past)
Use simg2img to convert the system.img (or product.img or vendor.img) to raw format. simg2img is a part of android fsutils
Code:
sudo apt install android-tools-fsutils
You will need a linux box or VM with Kernel 5.x running (erofs support is added from 4.20, but I am running 5.x) - mount the raw image using
Code:
sudo mount -t erofs -o loop system.ext4.img /home/test/mnt/try2
(The "-t erofs" is optional - will work just fine with sudo mount -o loop system.ext4.img /home/test/mnt/try2)
You will get the erofs image mounted in the folder you've specified, and you can browse through it
Note that erofs images are not meant to be editable. If you want to modify the system.img, extract it's content and create a new system.img using the mkfs.erofs binary (I had linked to the source code). You'll of course need an unlocked bootloader to flash (or boot) the modified image
ph03n!x said:
Update as of today -
I have cloned erofs-utils git and have compiled mkfs for creating EROFS images. Will work on it whenever I have time to see if I can get an img to mount...
Click to expand...
Click to collapse
Have a look (read) here - > https://zhuanlan.zhihu.com/p/60617375
Pretoriano80 said:
Have a look (read) here - > https://zhuanlan.zhihu.com/p/60617375
Click to expand...
Click to collapse
I had come across that link earlier, but that is for compiling mkfs for arm/ arm64...
Got what I needed, mission accomplished
So have you actually modified system and packaged it back up as erofs and booted it?
freeza said:
So have you actually modified system and packaged it back up as erofs and booted it?
Click to expand...
Click to collapse
I do not have an unlocked bootloader yet - I have gotten as far as editing and recreating the EROFS image. One of these days I'll get the bootloader unlocked too :good:
ph03n!x said:
I do not have an unlocked bootloader yet - I have gotten as far as editing and recreating the EROFS image. One of these days I'll get the bootloader unlocked too :good:
Click to expand...
Click to collapse
Be careful with this kind of stuff after unlocking, Huawei devices are tricky as hell. Afaik Magisk already support EroFS, so it might be better to use that.
Of course,that's if you don't want to create some kind of custom rom, based on stock.
Pretoriano80 said:
Be careful with this kind of stuff after unlocking, Huawei devices are tricky as hell. Afaik Magisk already support EroFS, so it might be better to use that.
Of course,that's if you don't want to create some kind of custom rom, based on stock.
Click to expand...
Click to collapse
That is why I have two active phones, plus a few more right from the legendary HD2 to fall back on... what fun is it if you don't experiment with the flashy new hardware?!
I don't know when I will make credible progress on anything at all now though - am relocating to a different country shortly - to the home of Huawei
Hey! Congratulations and thank you for the time and effort you spent on this.
Also, It's awesome to see another LEO user! Mine died a while back, but that was the modders heaven!
I've got an unlocked device and rooted using Magisk.
Root Explorer or any other root tools available today cannot read the system partition. It shows as free space is 0 MB.
Actually, I can see the content inside /system but I cannot move anything to it - Like patching the hosts file.
Any clue on how to achieve that?
JazonX said:
Hey! Congratulations and thank you for the time and effort you spent on this.
Also, It's awesome to see another LEO user! Mine died a while back, but that was the modders heaven!
I've got an unlocked device and rooted using Magisk.
Root Explorer or any other root tools available today cannot read the system partition. It shows as free space is 0 MB.
Actually, I can see the content inside /system but I cannot move anything to it - Like patching the hosts file.
Any clue on how to achieve that?
Click to expand...
Click to collapse
You can't! You must use Magisk for that.
Pretoriano80 said:
You can't! You must use Magisk for that.
Click to expand...
Click to collapse
Hi Pretoriano,
Nice to see you on dead land. Remember those days when I was using Mate 10 Pro. Anyways let's move on and please guide us how to use magisk to push something in to system or remove / replace.
I'm rooted and looted on P30 Pro:laugh:
Thanks in advance,
goldybewon
goldybewon said:
Hi Pretoriano,
Nice to see you on dead land. Remember those days when I was using Mate 10 Pro. Anyways let's move on and please guide us how to use magisk to push something in to system or remove / replace.
I'm rooted and looted on P30 Pro:laugh:
Thanks in advance,
goldybewon
Click to expand...
Click to collapse
Just read Magisk documentation, it's easy to build yourself simple modules. Also you can get some examples from available modules.
JazonX said:
Actually, I can see the content inside /system but I cannot move anything to it - Like patching the hosts file.
Any clue on how to achieve that?
Click to expand...
Click to collapse
Pretoriano80 said:
You can't! You must use Magisk for that.
Click to expand...
Click to collapse
Yes, Pretoriano80 is right - EROFS by design is not meant to be modified. While I might take sometime later on to create a modified system.img, it'll be just an academic exercise - Magisk can easily add/ replace the contents of /system during boot, making system.img mods passe :angel:
@oslo83 I have attached the mkfs.erofs binary using this git source to the first post.
Please go through the README for this - I built this binary for the x64 architecture, and for lz4-1.9.0
The command options are -
Code:
mkfs.erofs 0.1
usage: [options] FILE DIRECTORY
Generate erofs image from DIRECTORY to FILE, and [options] are:
-zX[,Y] X=compressor (Y=compression level, optional)
-d# set output message level to # (maximum 9)
Note that the system.img that comes within UPDATE.APP is a root file system - here is a structure.
Code:
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodem
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodemnvm
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodemnvmbkp
drwxr-xr-x. 2 root root 0 Aug 7 2018 acct
lrw-r--r--. 1 root root 11 Aug 7 2018 bin -> /system/bin
lrw-r--r--. 1 root root 50 Aug 7 2018 bugreports -> /data/user_de/0/com.android.shell/files/bugreports
drwxrwx---. 2 ph03n1x 2001 0 Aug 7 2018 cache
lrw-r--r--. 1 root root 13 Aug 7 2018 charger -> /sbin/charger
dr-xr-xr-x. 2 root root 0 Aug 7 2018 config
drwxr-xr-x. 2 root root 0 Aug 7 2018 cust
lrw-r--r--. 1 root root 17 Aug 7 2018 d -> /sys/kernel/debug
drwxrwx--x. 2 ph03n1x ph03n1x 0 Aug 7 2018 data
drwxrwx--x. 2 ph03n1x ph03n1x 0 Aug 7 2018 data_old
lrw-------. 1 root root 23 Aug 7 2018 default.prop -> system/etc/prop.default
drwxr-xr-x. 2 root root 0 Aug 7 2018 dev
drwxr-xr-x. 2 root root 35 Aug 7 2018 dload
drwxr-xr-x. 2 root root 0 Aug 7 2018 eng
lrw-r--r--. 1 root root 11 Aug 7 2018 etc -> /system/etc
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1024m
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1280m
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1536m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram2240m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram256m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram4096m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram512m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram768m
-?????????? ? ? ? ? ? init
-rwxr-x---. 1 root 2000 1717 Aug 7 2018 init.environ.rc
-?????????? ? ? ? ? ? init.rc
-?????????? ? ? ? ? ? init.usb.configfs.rc
-?????????? ? ? ? ? ? init.usb.rc
-rwxr-x---. 1 root 2000 580 Aug 7 2018 init.zygote32.rc
-rwxr-x---. 1 root 2000 1042 Aug 7 2018 init.zygote64_32.rc
lrw-r--r--. 1 root root 8 Aug 7 2018 log -> /splash2
drwxr-xr-x. 2 root ph03n1x 0 Aug 7 2018 mnt
drwxr-xr-x. 2 root root 0 Aug 7 2018 modem_log
drwxr-xr-x. 2 root root 0 Aug 7 2018 odm
drwxr-xr-x. 2 root root 0 Aug 7 2018 oem
drwxr-xr-x. 6 root root 71 Aug 7 2018 patch
drwxr-xr-x. 2 root root 0 Aug 7 2018 patch_hw
drwxr-xr-x. 2 root root 0 Aug 7 2018 preload
drwxr-xr-x. 2 root root 0 Aug 7 2018 proc
drwxr-xr-x. 2 root root 0 Aug 7 2018 product
drwxr-xr-x. 2 root root 47 Aug 7 2018 res
-rw-r--r--. 1 root root 32 Aug 7 2018 resetFactory.cfg
drwxr-xr-x. 2 root root 0 Aug 7 2018 root
drwxr-x---. 2 root 2000 183 Aug 7 2018 sbin
lrw-r--r--. 1 root root 21 Aug 7 2018 sdcard -> /storage/self/primary
drwxr-xr-x. 2 root root 0 Aug 7 2018 sec_storage
drwxr-xr-x. 2 root root 0 Aug 7 2018 splash2
drwxr-x--x. 2 root 1028 0 Aug 7 2018 storage
drwxr-xr-x. 2 root root 0 Aug 7 2018 sys
drwxr-xr-x. 23 root root 478 Aug 7 2018 system
-?????????? ? ? ? ? ? ueventd.rc
drwxr-xr-x. 2 root 2000 0 Aug 7 2018 vendor
-rw-r--r--. 1 root root 524 Aug 7 2018 verity_key
drwxr-xr-x. 2 root root 0 Aug 7 2018 version
It would be good if you spend time with the system.img, vendor.img, product.img and understand how the structures are inter-linked. Happy hunting!
@ph03n!x
Is it possible to compile/assemble such software piece for Windows, or its unrealistical? There's millions of examples to explore ext4 images, but 0 about erofs.
I mean, we see sources. in C... i guess it should be still possible to translate it to something portable in Python or simply compile some component on Windows
dimon222 said:
@ph03n!x
Is it possible to compile/assemble such software piece for Windows, or its unrealistical? There's millions of examples to explore ext4 images, but 0 about erofs.
I mean, we see sources. in C... i guess it should be still possible to translate it to something portable in Python or simply compile some component on Windows
Click to expand...
Click to collapse
I will explore this when I find time.. relocating between countries at the moment. That said, please do not hold your breath - I'm more comfortable with Linux than with Windows. But I'll still give it a shot!
https://forum.xda-developers.com/mate-20-pro/help/emui-9-1-partition-rw-t3947916/post80059824
Thanks @ante0 for his mkfs.erofs arm build.
How do you convert system.img to raw img? System partion is erofs can you tell the trick clearly? With method... Plz
Has anyone tried this with WSL v2? Curious to see if it works.
Works with:
- Xiaomi POCO C3
- Xiaomi Redmi 9C
- Xiaomi Redmi 9C NFC
Build Date:
2020/11/19
Android Version:
QP1A.190711.020
Display ID:
angelica-userdebug 10 QP1A.190711.020 484 test-keys
Build Fingerprint:
Redmi/angelica/angelica:10/QP1A.190711.020/484:userdebug/test-keys
Security Patch:
2020-03-05
Radio/Modem/Baseband Version:
MOLY.LR12A.R3.MP.V107.5.P4
Download:
https://www.mediafire.com/file/w4vs...neering_484_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_MT6765_MOLY_LR12A_R3_MP_V107_5_P4_2020_05_08_15_56.xz
md1_dbginfo=DbgInfo_LR12A.R3.MP_LCSH_Q0MP1_MT6765_SP_MOLY_LR12A_R3_MP_V107_5_P4_2020_10_30_17_09.xz
md1_mddbmeta=MDDB.META_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.EDB
md1_mddbmetaodb=MDDB.META.ODB_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.XML.GZ
md1_mddb=MDDB_InfoCustomAppSrcP_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.EDB
Prop.default:
Code:
ro.build.version.incremental=484
ro.vendor.build.version.incremental=484
ro.odm.build.version.incremental=484
ro.build.version.security_patch=2020-03-05
ro.vendor.build.security_patch=2020-03-05
ro.build.display.id=angelica-userdebug 10 QP1A.190711.020 484 test-keys
ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp3-V1.4_lcsh.q0mp1.k62v1.64.bsp_P4
ro.product.system.device=angelica
ro.product.system.model=angelica
ro.product.system.name=angelica
ro.build.product=angelica
ro.product.board=angelica
ro.product.vendor.device=angelica
ro.product.vendor.model=angelica
ro.product.vendor.name=angelica
ro.product.odm.device=angelica
ro.product.odm.model=angelica
ro.product.odm.name=angelica
ro.product.product.device=angelica
ro.product.product.model=angelica
ro.product.product.name=angelica
ro.build.flavor=angelica-userdebug
ro.build.description=angelica-userdebug 10 QP1A.190711.020 484 test-keys
ro.board.platform=mt6765
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/angelica/angelica:10/QP1A.190711.020/484:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/angelica/angelica:10/QP1A.190711.020/484:userdebug/test-keys
ro.bootimage.build.fingerprint=Redmi/angelica/angelica:10/QP1A.190711.020/484:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/angelica/angelica:10/QP1A.190711.020/484:userdebug/test-keys
ro.product.build.fingerprint=Redmi/angelica/angelica:10/QP1A.190711.020/484: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=Thu Nov 19 00:20:49 CST 2020
ro.build.date=Thu Nov 19 00:20:49 CST 2020
ro.vendor.build.date=Thu Nov 19 00:20:49 CST 2020
ro.bootimage.build.date=Thu Nov 19 00:20:49 CST 2020
ro.odm.build.date=Thu Nov 19 00:20:49 CST 2020
ro.product.build.date=Thu Nov 19 00:20:49 CST 2020
MD5 hashes:
Code:
ADPT_20201119-022241_0.log -> af419a58194cc06d36a38a8053c60b0a
android-info.txt -> a2e30dbe30b036fe2f2da4728c50da34
APDB_MT6765_S01__W2015 -> 5358ccefe1fda7f456f3a568ec4b04d5
APDB_MT6765_S01__W2015_ENUM -> fbe5f23b8bc20d1bce7be6200a0731a1
apex -> d41d8cd98f00b204e9800998ecf8427e
arm11_path.txt -> e0fff7b6c16354d672c6df5beb73635f
boot-debug.img -> f8c67d0a50ce7f5a32f76690881a5652
boot.img -> 08b8329446f1d9a916c9dfa327a2c4e2
build.prop -> 9e16fa94f827c0961eb1ae26d09399fa
build_fingerprint.txt -> 5abf0a64b22a54c8bae9b7844067e888
build_thumbprint.txt -> 4df3c90452d25e672f5d105b52353797
cache.img -> 14f8eee266f1e4e09298ffd7564f7490
Checksum.ini -> 9486db622499e5a22812c74039763580
clean_steps.mk -> 30f988afe6140fd1afb0a19ed9b53da4
content_cert_sig.bin_hash.tmp -> acd3d8a4dfc44c0266f96f3482552ecf
CT865_factory_1_0.zip -> 1a8d2920eee999ef3b014c46adb61137
cust.img -> 09e9b617296df53b0716255c86d01c53
dexpreopt.config -> 3bd2bfa98738f4798fcc97be5ba41e74
dtb.img -> 8cae5478f4627f3dd5f27f7d970db7e5
dtbo-verified.img -> 599646e7a4bec2ddf53205f9142a769b
dtbo.img -> 9c45c9d8cb33173ad92ae2030f5b06e8
dummy.bin -> 6811c482ead27c0b1165ecfbe996c2b4
efuse.img -> 22e70283687ccca929e3f6d117c5fc34
flash_all.bat -> 24fa9f257fae3afd491535eed61787cd
fs_image.tar.gz.mbn.img -> 633b9aac7f2d2e81c0dc595d2a644d80
init -> 0c3c9ae3511888e757583690d46e8068
installed-files-product.json -> 57fdb0849ad188efd21c5478b4a2ab53
installed-files-product.txt -> f5ec1bad7fa1dba550a7edde9e8acb19
installed-files-ramdisk-debug.json -> 12fb22e79d25d59659f5e9ff1c7e13c4
installed-files-ramdisk-debug.txt -> 2b7375b11e0b15c08ea73fef68932b41
installed-files-ramdisk.json -> 8a7ab1d04d038fc3a8478378d5118d75
installed-files-ramdisk.txt -> 42f4aedb8144ddc25f082c2d7e1d5f1d
installed-files-recovery.json -> 961ebfc9bae732bbf8629a985d0f01d2
installed-files-recovery.txt -> 319b89a9a3203d9260b48fd216f9f13c
installed-files-root.json -> e2017cd6f1befb266cb137f306b0a6eb
installed-files-root.txt -> 40d211d2878ac2e27d1d93878dff8a41
installed-files-vendor.json -> 6be216de6e09fd926daa2f3643745ab1
installed-files-vendor.txt -> 9d4a7dd86d346e92756f7a971c6d3f15
installed-files.json -> c9ed71d95a77bccc43d52c8611b03968
installed-files.txt -> f1e06245106be3cc07b1c0e0264b0a2a
kernel -> 81bc84380ce37a9dbfb3fd5e728a90d1
LCSH_Q0MP1_MT6765_SP_PCB01_MT6765_S00_1_lwg_n.elf -> 1262030a6e6a69a54bf4964a7712a142
lk-verified.img -> b7d5e7b225fbd2c793bc138965fb6749
lk.img -> 1cb3667e581e1623ea0491b24e2dc365
logo-verified.bin -> 95925abd3a933e709770736abc7bb469
logo.bin -> 535bfd42ca7ef019d44c6ae64104633e
md1arm7-verified.img -> 6fb4b893db805c8a1e28b7bdb05dc689
md1arm7.img -> a0453e723dc84255940d7791740d06db
md1img-verified.img -> 1245636b84df0b3bd8b92e70cb665c79
md1img.img -> 867fa4249ea527bfd8208d2dd8794b29
md3img.img -> 9a9c185e3f6234103e5949716b9962d2
md5.txt -> a9064c5f147d81b3e97fdaddcc694959
MDDB_InfoCustomAppSrcP_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4_1_ulwctg_n.EDB -> 166fa9937371e654e91e022554f73765
module-info.json -> af3da4a16cf5a2807bb756b005c86b59
MT6765_Android_scatter.txt -> bb35c38b368cba3cb8412fcf7f87ae7e
PGPT -> 20bedc49348b16cdc20be09c4f32245c
preloader.bin -> ded6d9e4ee9c78fcc4431b03c044c515
preloader.img -> 321c28c429b9e775374132c6f2e394f3
preloader_angelica.bin -> ded6d9e4ee9c78fcc4431b03c044c515
preloader_angelica_signed.bin -> c54e168ccdf259623cbdb225a961f354
preloader_emmc.img -> 321c28c429b9e775374132c6f2e394f3
preloader_k65v1_64_bsp.bin -> c54e168ccdf259623cbdb225a961f354
preloader_ufs.img -> 7c233fd64a63ad906df7bd44ebbebe60
previous_build_config.mk -> 719267d360015f315698ae68c36ea08a
product -> d41d8cd98f00b204e9800998ecf8427e
product.img -> 00484d1d7c50850b4e884fd878a0e9ed
ramdisk-debug.img -> b6b0d0eb85d103beb8a437997e830026
ramdisk-recovery.img -> 0b09c6ef20a969884e2a69bbdf3a8715
ramdisk.img -> 34287bcd26aba8383de52d055ae3620b
recovery -> d41d8cd98f00b204e9800998ecf8427e
recovery.id -> 8ccbb57f3431bb57a8be9dec7eaa7252
recovery.img -> eb11468c4f639d0f2ba49290f4f28679
scp-verified.img -> cb8c196962ba474df347154baafeee63
scp.img -> 5f3763151352d37efec598443bc8a52f
secro.img -> 096587b863e1252d67b1b8307291db09
sig_size.txt -> 7a600b6f266737e2830a101876dd3561
spmfw-verified.img -> 22e5a5a016129ed5786127664900ee3b
spmfw.img -> 66cf26550d6650dd65f5f3865948bdf2
sspm-verified.img -> 164f3ef783323299cb5244949a560e87
sspm.img -> b281a508c22190047eed1af202bd5520
super.img -> 38e15bcfdd2d42cb211d1e9cd804a066
super_empty.img -> f911a1089119bd6f6a56919deb7bb9e8
system -> d41d8cd98f00b204e9800998ecf8427e
system.img -> cc48fbaee410e878c74ed10bc825b5c2
TARGET.txt -> 748150f0c3bbf2fa4dcc3346e73099f5
tee-verified.img -> 41f6595b21e6d3adbb8ca88e39c2f1e6
tee.img -> 2da6bfb5fa75119c984579b6fbe2e752
userdata.img -> b308f4d258cc086ea10d0c64dfcca17f
vbmeta.img -> 88e06152ae5ed02a0aefed78e2ab6049
vbmeta_system.img -> c8fbf3859cef073136d596fa978c7797
vbmeta_vendor.img -> d2241e965215b0410a2118ffd9222990
vendor -> d41d8cd98f00b204e9800998ecf8427e
vendor.img -> 86850a18f6d35bae45677d40b367e8c3
HOLA, disculpe mi ignorancia,. pero cual es ese archivo de dispersión adjunto ?????
es un poco engorroso esto, y no entiendo.,
espero su pronta respuesta.
PARA QUE SIRVE ESTA ROM DE INGENIERIA, Y COMO SE INSTALA POR FAVOR.
jasann said:
HOLA, disculpe mi ignorancia,. pero cual es ese archivo de dispersión adjunto ?????
es un poco engorroso esto, y no entiendo.,
espero su pronta respuesta.
Click to expand...
Click to collapse
English only, please.
What is it for? And essentially, what it exactly is?
XdaInsiderAndDev said:
What is it for? And essentially, what it exactly is?
Click to expand...
Click to collapse
This is a rom with low security.
You can do everything your creativity allows.
VD171 said:
This is a rom with low security.
You can do everything your creativity allows.
Click to expand...
Click to collapse
Wait a sec, so it is MIUI or AOSP or what?
XdaInsiderAndDev said:
Wait a sec, so it is MIUI or AOSP or what?
Click to expand...
Click to collapse
Official MIUI leaked by developer team.
VD171 said:
Official MIUI leaked by developer team.
Click to expand...
Click to collapse
So it's a Low-Security MIUI version?
XdaInsiderAndDev said:
So it's a Low-Security MIUI version?
Click to expand...
Click to collapse
Exactly.
You can use meta mode on ENGINEERING rom too, so you can write IMEI, bluetooth MAC, wifi MAC...
VD171 said:
Exactly.
You can use meta mode on ENGINEERING rom too, so you can write IMEI, bluetooth MAC, wifi MAC...
Click to expand...
Click to collapse
Oh ok so for developers this is great
XdaInsiderAndDev said:
Oh ok so for developers this is great
Click to expand...
Click to collapse
Yes, perfect.
it works 1000000000%...my phone back from the dead after flashing with this rom
Faith1 said:
it works 1000000000%...my phone back from the dead after flashing with this rom
Click to expand...
Click to collapse
Good work, my friend.
Enjoy
Thanks for this, will it work on Poco C31 (Angelicainin) already on 12.5.1 rom?
manojmat29 said:
Thanks for this, will it work on Poco C31 (Angelicainin) already on 12.5.1 rom?
Click to expand...
Click to collapse
I'm not sure, I'm sorry.
VD171 said:
Good work, my friend.
Enjoy
Click to expand...
Click to collapse
Works on redmi 9 Activ (cattail)??
Angelica and cattail have the same looks and processors and custom ROMs generally work on BOTH of them so.....I hope it works
Benjamin B C H said:
Works on redmi 9 Activ (cattail)??
Angelica and cattail have the same looks and processors and custom ROMs generally work on BOTH of them so.....I hope it works
Click to expand...
Click to collapse
Probably, no.
It works for Angelica devices only.
VD171 said:
Probably, no.
It works for Angelica devices only.
Click to expand...
Click to collapse
I tried it
It did work on cattail
But any ideas on how to get back IMEI on Redmi 9C?? Devices doesn't boot to META mode even while using ENG firmware
Hello.
I'm from poland and few weeks ago i bought Huawei P30 Pro 8/256 GB.
The phone is from german distribution, but it never reached local operator (T-Mobile).
It was originally packed and sealed, guaranty ended last year.
I wonder if it is possible to update my device. Right now the system version is 9.1.0.156 (WEC891E3R1P5).
Is it possible to switch software version to one, that will enable updates?
Code:
Version Info:
- Bootloader Version:
Chipset-atlanta9.1.0.(00RW)_FASTBOOT
- Kernel Compiling Time:
1# SMP PREEMPT Tue Apr 30 02:58:03 CST 2019
- AP Version: System:
System 9.1.0.040(01VQ)
- AP Compiling Time:
Fri Apr 26 13:50:48 CST 2019
- CP Version:
21C20B360S000C000(balong)
- CP Compiling Time:
Apr 30 2019, 03:21:03(balong)
- Parameter Version:
CVersion: C432 DVersion:CUST
- System Component Version:
System 9.1.0.040(P.19042602.GENERIC_A15_GLOBAL_FULL_DPI480_EXT4)
- Vendor Component Version:
Chipset-atlanta 9.1.0(P.19042901.global)
- Cust Component Version:
Cust-OVS 9.0.0.1(P.EROFS)
- Product Component Version:
Product-VOG 9.1.0(P)
- Version Component Version:
Version-VOG-L29-891002 9.1.0(P.19031601)
- Base Software Version:
VOG-LGRP2-OVS 9.1.0.156
- Cust Software Version:
VOG-L29-CUST 9.1.0.3(WEC891)
- Preload Software Version:
VOG-L29-PRELOAD 9.1.0.5(WEC891R1)
Mam ten sam problem. Cos zrobiles ?
Mod translation via GT: I have the same problem. Did you do something?
Hi, after a security update my phone got stucked on bootloop and I'm trying to flash the stock ROM throw an SD card but I get this error :
( E3003: Can't install this package (Thu Jan 3 20:40:27 CEST 2019) over newer build (Thu Jan 2 19:59:28 UTC 2020)
so I tried to edit the update script to match the data and I tried to delete this whole line
(!less_than_int(1546519227, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Thu Jan 3 20:40:27 CST 2019) over newer build (" + getprop("ro.build.date") + ").");
but I get signature verification failed. and Ideas?
My phone isn't rooted and the bootloader isn't unlocked so idk if I'll ever get the phone again. thanks