[GUIDE] EROFS - Mounting/ Accessing/ Creating system.img - Huawei P30 Pro Guides, News, & Discussion

[GUIDE] EROFS - Mounting/ Accessing/ Creating system.img - Huawei P30 Pro Guides, News, & Discussion

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.

Related

Why do latest Android Security Update firmwares have old file dates?

I'm not a noob, but I am confused about something that I think should be simple:
Monthly Android Security Updates
I apparently have to install these manually, since OTA updates fail supposedly because I run a rooted phone w/ custom bootloader/recovery.
Google has been making it a point to release security patches every month:
http://source.android.com/security/bulletin/index.html
March 2016's is here:
http://source.android.com/security/bulletin/2016-03-01.html
On that page they say:
"The Nexus firmware images have also been released to the Google Developer site.", with a link to:
https://developers.google.com/android/nexus/images
I download firmware for my Nexus5 Hammerhead MMB29K:
https://dl.google.com/dl/android/aosp/hammerhead-mmb29k-factory-1943f0f5.tgz
I unzip that file and list the contents:
Code:
Pvs-MacBook-Pro:hammerhead-mmb29k pv$ ls -la
total 1218408
[email protected] 8 pv staff 272 Nov 18 15:44 .
drwx------+ 28 pv staff 952 Mar 9 10:55 ..
[email protected] 1 pv staff 3195188 Nov 18 15:44 bootloader-hammerhead-hhz12k.img
[email protected] 1 pv staff 974 Nov 18 15:44 flash-all.bat
[email protected] 1 pv staff 845 Nov 18 15:44 flash-all.sh
[email protected] 1 pv staff 798 Nov 18 15:44 flash-base.sh
[email protected] 1 pv staff 574092301 Nov 18 15:44 image-hammerhead-mmb29k.zip
[email protected] 1 pv staff 46515712 Nov 18 15:44 radio-hammerhead-m8974a-2.0.50.2.28.img
Pvs-MacBook-Pro:hammerhead-mmb29k pv$
So, my question is:
Why does Google say that the March 2016 Security Updates Nexus devices are available for download, but the files themselves are dated November 2015?
This begs more questions:
Are the March 2016 Android Security Patch Levels really in the 6.0.1 November 2015 dated files?
If not, then why does Google say that I can get the March 2016 updates for my Nexus 5 from the firmware download page?
How do I non-OTA update my Nexus5 to the latest Security Patch?
Thanks!
Pv

Why do latest Android Security Update firmwares have old file dates?

I am confused about something that I think should be simple:
Monthly Android Security Updates
I apparently have to install these manually, since OTA updates fail supposedly because I run a rooted phone w/ custom bootloader/recovery.
Google has been making it a point to release security patches every month:
http://source.android.com/security/bulletin/index.html
March 2016's is here:
http://source.android.com/security/bulletin/2016-03-01.html
On that page they say:
"The Nexus firmware images have also been released to the Google Developer site.", with a link to:
https://developers.google.com/android/nexus/images
I download firmware for my Nexus5 Hammerhead MMB29K:
https://dl.google.com/dl/android/aosp/hammerhead-mmb29k-factory-1943f0f5.tgz
I unzip that file and list the contents:
Code:
Pvs-MacBook-Pro:hammerhead-mmb29k pv$ ls -la
total 1218408
[email protected] 8 pv staff 272 Nov 18 15:44 .
drwx------+ 28 pv staff 952 Mar 9 10:55 ..
[email protected] 1 pv staff 3195188 Nov 18 15:44 bootloader-hammerhead-hhz12k.img
[email protected] 1 pv staff 974 Nov 18 15:44 flash-all.bat
[email protected] 1 pv staff 845 Nov 18 15:44 flash-all.sh
[email protected] 1 pv staff 798 Nov 18 15:44 flash-base.sh
[email protected] 1 pv staff 574092301 Nov 18 15:44 image-hammerhead-mmb29k.zip
[email protected] 1 pv staff 46515712 Nov 18 15:44 radio-hammerhead-m8974a-2.0.50.2.28.img
Pvs-MacBook-Pro:hammerhead-mmb29k pv$
So, my question is:
Why does Google say that the March 2016 Security Updates Nexus devices are available for download, but the files themselves are dated November 2015?
This begs more questions:
Are the March 2016 Android Security Patch Levels really in the 6.0.1 November 2015 dated files?
If not, then why does Google say that I can get the March 2016 updates for my Nexus 5 from the firmware download page?
How do I non-OTA update my Nexus5 to the latest Security Patch?
Thanks!
Pv

Ping! Seriously, no one bites on this one?

I'll answer my own question: The answer is even lamer than I thought.
The download link that the monthly security bulletin(s) point you to is a download to the original [aka: "old"] system image.
As I pointed out, the March [now April] 2016 link for a recent Security Update for my Nexus 5 sends me to the download for the November Nexus 5 System Image.
I install that image, and soon after booting it prompts me to install the January 2016 Security Update.
Here is where it gets lame...
Soon after rebooting after the January 2016 SU it prompts me to install the February 2016 SU.
Soon after rebooting after the February 2016 SU it prompts me to install the March 2016 SU.
Soon after rebooting after the March 2016 SU it prompts me to install the April 2016 SU.
I'm seeing a [lame] pattern here.
How annoying!
Can't they just update the system image w/ the latest Security Update?
Or, provide me with a SU with all of the previous SUs?
I repeat: Lame!
Pv

[CLOSED][ROM][G950F][7.0] * GoogleWiz (nougat) * extreme debloat [20/01/2018]

I would like to share my work. This is the first time that I post a ROM on XDA, please keep that in mind.
***
{
"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"
}
Wiz ***
This is an extremely debloated Samsung rom with absolutely minimal Samsung functionality. The basic ROM apps (dialer, messaging, contacts) are from Google. Only for Galaxy S8 international equinox (SM-950F). Personally I very much like the Samsung phones/hardware but I am not so fond of the software and bloatware. I also prefer to use a ROM which just has what I use. If you want Samsung stuff ... use another ROM !!!
Name
Originally I called this ROM "minirom" until pvillasuso used the term "wizgoogle" in this (https://forum.xda-developers.com/ga...me-debloat-t3730681/post75271202#post75271202) post. So I decided to call it "GoogleWiz"
Features
The ROM contains (only) the following Samsung applications:
- Base: NRD90M.G950FXXU1AQL5
- Settings (you can't get rid of this unfortunately)
- Gallery (because of its integration with Camera)
- Camera (because it uses all hardware capabilities)
- minimal lockscreen
- Always On Display (Samsung - personally I like this feature a lot)
- Fingerprint & iris scanning for security
- Blue light filter
Others:
- Nova as launcher (https://play.google.com/store/apps/details?id=com.teslacoilsw.launcher); IMHO still the BEST launcher out there
- Swiftkey as (only) keyboard (https://play.google.com/store/apps/details?id=com.touchtype.swiftkey)
- Rooted with Magisk (see https://forum.xda-developers.com/apps/magisk)
- Magisk manager (see https://forum.xda-developers.com/apps/magisk)
- Latest Google Play services/store
- Bixby key is mapped to Nova "home"
- Google dialer (as of v2)
- Google contacts (as of v2)
- Google messaging (as of v2)
- Google clock
- Google calendar
- Google calculator
- optimized build.prop
- based on December 2017 security update from Samsung (AQL5)
- huge CscFeature list (in system/csc/feature.xml)
- huge SEC_FLOATING_FEATURE list (see system/etc/floating_feature.xml)
- Google pixel boot animation (I don't like the Samsung one)
ROM does not contain country specific CSCs. All settings are generic. To be clear again: there is no other Samsung stuff: no Samsung account, no Samsung appstore, no Samsung Themestore, no Samsung device manager, no Samsung calendar, no KNOX, no Samsung XYZ ... Technically it is possible to even remove the Gallery from the ROM but I left it in due to its integration with Samsung's camera (removed in v3). Everything else (file manager, browser, maps, ...) you can download from the Google Play store. Your choice.
Before installing this ROM, please make sure that "OEM unlock" is enabled in your developer settings (if you don't understand what this means then probably this ROM is not for you). ROM is reasonably small (less than 1 GB). Install from TWRP (wipe system, data, cache, dalvik). Other devs, please feel free to (re)use this for your own work ... I am not asking anything from anybody, no donation, no thanks, no beer ... you don't even have to mention that you (re)use this. If you download the standard Google stuff from the play store (Gmail, Google+, Drive, ...) then you should have a phone very close to a Google Pixel. Choice is up to you. I will try to support questions / feedback but I have a busy job and cannot spend all my free time on this. If people do like it though, I will update using Samsung's monthly security updates (that is something which I do for myself anyway). I use this as my own personal daily driver (all the rest coming from the Google Play store). I will not answer questions such as "Can you please add Samsung feature X,Y,Z" ... I have deliberately removed them. If you want Samsung, go and use a Samsung ROM. There are instructions further down on how to create your own variant of the ROM so you can do this yourself if you want to add stuff. I will not answer PMs (don't have time to look at them). I have attached also a bash script (as .txt file). This is the script which I personally use to generate the ROM starting from a standard Samsung system.img. If you are a DEV, you can study this to see how I create this ROM. Again, feel free to (re)use.
Disclaimer
The usual disclaimers apply: no warranty, installing this will trip KNOX, install at your own risk, ... I am not responsible for soft or hard bricks. Your phone must have TWRP to install this ROM.
Performance
If you want slightly faster performance, enable the developer settings and then set the animation speeds to 0 (zero). Also enable GPU 2D hardware rendering. The first boot will take time (a few minutes) as all apk files will be run through the dex2oat compiler.
Download (multiple versions): https://www.androidfilehost.com/?w=files&flid=239365
v0 (2018-01-05):
- initial release
v1 (2018-01-06):
- fix lag starting up settings
- fix lag in settings for lockscreen/security
- included SimSettingsMgr
- included MTP
v2 (2018-01-20):
- Google dialer (https://play.google.com/store/apps/details?id=com.google.android.dialer)
- Google contacts (https://play.google.com/store/apps/details?id=com.google.android.contacts)
- Google messaging (https://play.google.com/store/apps/details?id=com.google.android.apps.messaging)
- AOSP gallery
- removed Samsung contacts
- removed Samsung dialer
- removed Samsung messaging
- removed Samsung gallery
- updated to latest Magisk
- updated to latest PlayStore & Play Services
- updated to latest SwiftKey
v3 (2018-01-27):
- fix annoying message when Google dialer starts
- fix problem with NFC payment
- updated Google play store and services
- updated to latest Samsung AOD
- updated to latest Swiftkey
- Samsung gallery is back (better integration with Camera)
- updated Google dialer, messaging, contacts to latest versions
- Magisk 15.3 and Magisk manager 5.5.5
v4 (2018-01-31):
- fix crash in cameraserver
- integrated Google clock (alarm tone can be selected from Google clock) (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
- left a bit more notifications and ringtones
- integrated SmartFittingService (but it does not seem to do much)
- integrated old (but very good) calculator (goes way back from Cyanogen)
- integrated Iris Scanner (please test as I do not use this myself)
- Arabic language support
v5 (2018-02-02):
- fix icons in statusbar not being displayed properly
- removed SmartFittingService (no use)
- replaced calculator with Google calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
- updated keyboard to latest SwiftKey version
- updated Google dialer to latest version
- integrated Google calendar in ROM
- updated Play store to latest version
v6 (2018-02-03):
- latest Samsung S8 kernel (Jan 6)
- remove Samsung inCallUI (/system/priv-app/SamsungInCallUI)
- adapted the padding in the statusbar
- ROM installation now creates /data/system/users/0/settings_secure.xml to use Google dialer InCallUI as default (not a very nice solution but I do not see a better one)
v7 (2018-02-04):
- fix problem with missing call notifications in Google dialer
v8 (2018-02-05):
- fix problem of not being able to add an account (Settings > Accounts > Add Account)
- fix problem of mobile hotspot / tethering not present in settings
v9 (2018-02-06):
- added ~50 alarm tones for Google clock
v10 (2018-02-09):
- fixes for Gallery albums
v11 (2018-02-10):
- fix emoji in SwiftKey keyboard
- updated to latest Google Play Store and Google Play Services
Display resolution
Please set display resolution in settings to largest size !!! Settings > Display > Screen resolution > WQHD+. After a fresh install the screen resolution may be RESET on the second boot. If that happens, just set it back to WQHD+ and it will work fine as of that time.
Theming
- install Substratum (https://play.google.com/store/apps/details?id=projekt.substratum)
- install sungstratum (https://play.google.com/store/apps/details?id=projekt.sungstratum)
- install a samsung compatible substratum theme (e.g. https://play.google.com/store/apps/details?id=com.brit.swiftblack.layers)
Other stuff
If you want heart rate monitor / stress monitor: install SHealth (https://play.google.com/store/apps/details?id=com.sec.android.app.shealth) from the play store.
Known bugs / issues
- Magisk's Safenet check fails (but Magisk hiding is working)
- Max battery saving mode is not working (due to emergency stuff removed from ROM)
- Device encryption will not work (as it relies on Samsung KNOX which has been fully removed)
- Samsung Pay will not work (as it relies on Samsung KNOX which has been fully removed)
- Android for work will not function
Adblocking
If you would like to have adblocking (everywhere: browser, apps) do the following:
> adb shell
# su
# hl
The "hl" command will replace the hosts file with a huge (> 200000) hosts which refer to IP address 0.0.0.0; this will make ads go away in your browser and applications. No ad-blocking app is required.
Building a variant of this ROM
Instructions (for linux) on how to build your own variant of this rom are in:
https://forum.xda-developers.com/showpost.php?p=75185320&postcount=57
(sorry, no script for Windows ... I don't use Windows ... but the linux script should be easy to adapt into a windows script)
Screenshots
Screenshots in attach. Note: the black screenshots are taken after Subtratum theming and with my personal home screen configuration (so this is not the default if you install the ROM). The default has white applications.
Credits
topjohnwu for Magisk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
ASSAYYED for the updater-script (https://forum.xda-developers.com/ch...-android-roms-editor-assayyedkitchen-t3410545)
osm0sis for his script which allowed me to set the Google dialer as default (https://github.com/opengapps/opengapps/issues/301)
BSDgeek_Jake for the fantastic adblock hosts file MoaAB (https://forum.xda-developers.com/showthread.php?t=1916098)
jayantraj for the pixel boot animation (https://forum.xda-developers.com/ga...-google-pixel-boot-animation-samsung-t3528179)

XDA requires the source.
Can you share it?
Thanks

Sorry, what do you mean with "source" precisely?
thanks

batuzai04123 said:
XDA requires the source.
Can you share it?
Thanks
Click to expand...
Click to collapse
foobar66 said:
Sorry, what do you mean with "source" precisely?
thanks
Click to expand...
Click to collapse
Stock based roms do not require source code.... All looks good here

I just flashed your rom and what can I say.. Awesome rom so far so good! Im gonna test a lit bit more to see but is very stable ive been using for 4 hours and is very fluid and I dont like samsung apps so dont bother me at all. but there is only one thing I want you to know, since you debloat your rom, and delete com.samsung.faceservice and another apk called face, the setting app takes like 3 to 4 seconds to open up, and that is because those apk are missing. Im telling you that because Im a fan of debloating and I tried one time to delete those apps and happpend that. so if you could just please to fix that lag of setting Ill appreciate that nice rom!! keep it up!

torhect said:
I just flashed your rom and what can I say.. Awesome rom so far so good! Im gonna test a lit bit more to see but is very stable ive been using for 4 hours and is very fluid and I dont like samsung apps so dont bother me at all. but there is only one thing I want you to know, since you debloat your rom, and delete com.samsung.faceservice and another apk called face, the setting app takes like 3 to 4 seconds to open up, and that is because those apk are missing. Im telling you that because Im a fan of debloating and I tried one time to delete those apps and happpend that. so if you could just please to fix that lag of setting Ill appreciate that nice rom!! keep it up!
Click to expand...
Click to collapse
You are right, I noticed it too.
"Settings" app launched at about 2-3 seconds slower on me.
"Lock screen and security" window takes 3-4 seconds to load up.
Not of a big deal, but it would be better if Settings could be launched quicker.
Magisk's Safenet check fails also. Im not sure why. I clean flash this rom and everything is stock.
Also, the width covers the whole edge of the screen, making Timer, Notifications "broken" on every corner of the screen.
---------- Post added at 06:07 AM ---------- Previous post was at 05:52 AM ----------
Sim Card manager is force closing.
Love this debloated rom, but i think you could check on the issues we previously posted, including this sim card manager force closing. thank you.
rm -rf system/app/SimSettingMgr
You removed this system app , I think you've removed some essential system apps that's causing performance drop
and force close issues.
MTP Via usb cable doesn't work, Windows can't detect the phone via cable, even adb isn't working.

Looks good , thanks @ foobar66 !
Gonna wait ( for the coming "fixes" regarding the last comments ) to try it
This is what I was looking for , a really minimal samsung ROM
Cheers

batuzai04123 said:
You are right, I noticed it too.
"Settings" app launched at about 2-3 seconds slower on me.
"Lock screen and security" window takes 3-4 seconds to load up.
Not of a big deal, but it would be better if Settings could be launched quicker.
Magisk's Safenet check fails also. Im not sure why. I clean flash this rom and everything is stock.
Also, the width covers the whole edge of the screen, making Timer, Notifications "broken" on every corner of the screen.
---------- Post added at 06:07 AM ---------- Previous post was at 05:52 AM ----------
Sim Card manager is force closing.
Love this debloated rom, but i think you could check on the issues we previously posted, including this sim card manager force closing. thank you.
rm -rf system/app/SimSettingMgr
You removed this system app , I think you've removed some essential system apps that's causing performance drop
and force close issues.
MTP Via usb cable doesn't work, Windows can't detect the phone via cable, even adb isn't working.
Click to expand...
Click to collapse
Maybe the devolper should consider those tips in a next update also when i.want to reboot it take some time to reboot... Dont know why

Have u deleted Samsung Task Manager and all those which are there by default? I mean Samsung SPCM, which u can also see on Priv-app folder on most ROMs.
Thanks and regards

Hi all, thanks for the feedback. I am currently uploading v1 to AndroidFilehost. As soon as the upload is completed, I will update the OP with the link.
v1 (2018-01-06):
- fix lag starting up settings
- fix lag in settings for lockscreen/security
- included SimSettingsMgr
- included MTP
Personally I do not use MTP. I always upload files to my phone using ADB. So someone should test this.
ADB does work for me (on Linux), obviously you have to enable USB debugging in developer's settings (and on Linux you need proper UDEV configuration for ADB).
Also, note that I only have a Linux box. I do not use Windows. So I cannot test anything on Windows.
Please also set resolution of display to WQHD.
OP is updated. Safetynet check bug is still there. I have no idea right now why this fails.

miguelang611 said:
Have u deleted Samsung Task Manager and all those which are there by default? I mean Samsung SPCM, which u can also see on Priv-app folder on most ROMs.
Thanks and regards
Click to expand...
Click to collapse
Yes, this is not in the ROM.

For info:
Files in system/app:
Code:
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 Bluetooth/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 CaptivePortalLogin/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 CertInstaller/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 DownloadProviderUi/
16 -rw-r--r--. 1 philip philip 13021 Dec 31 2008 FFFFFFFF000000000000000000000001.drbin
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 FilterProvider/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GoogleCalendarSyncAdapter/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GoogleContactsSyncAdapter/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 GoogleExtShared/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 KeyChain/
4 drwxr-xr-x. 2 philip philip 4096 Dec 31 2008 mcRegistry/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyGoogleTTS/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyKeyboard/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyWebViewGoogle/
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 NfcNci/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SimSettingMgr/
Files in system/priv-app:
Code:
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 AODService_v25/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 BioFaceService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 BlockedNumberProvider/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 BlueLightFilter/
4 drwxr-xr-x. 4 philip philip 4096 Dec 13 13:45 DefaultContainerService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 DocumentsUI/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 ExternalStorageProvider/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 FaceService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 FingerprintService2/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 FusedLocation/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 GoogleExtServices/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GoogleLoginService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GoogleOneTimeInitializer/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 GooglePackageInstaller/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GoogleServicesFramework/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GPUDriver-S8MaliG71_70/
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 HealthService/
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 Messaging_SEP81/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 MmsService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 MsgCommService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 MtpApplication/
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 MtpDocumentsProvider/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyGooglePlayServices/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyGooglePlayStore/
4 drwxr-xr-x 2 philip philip 4096 Jan 2 18:29 MyLauncher/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyMagisk/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 OmaCP/
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 PhotoStudio_WQHD_Dream/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SamsungCamera7/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SamsungContactsStable/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SamsungInCallUI/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SamsungVideoPlayer2016/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecCalendarProvider_NOTSTICKER/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecContactsProvider/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecDownloadProvider/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecGallery2015/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecIrisService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecMediaProvider/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 SecSettings2/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 SecSettingsProvider2/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecSetupWizard2015/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 SecTelephonyProvider_Epic/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 SettingsReceiver/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SetupWizard/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 Shell/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 ShootingModeProvider2/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 smartfaceservice/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 SystemUI/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 Telecom/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 TeleService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 VpnDialogs/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 WallpaperCropper2/

v1 uploaded; see OP for description.
https://www.androidfilehost.com/?w=files&flid=239365

Thank you very much for sharing this rom. I have one question, apart of security updates, will it be possible to make this rom once oreo final rom is released?

Yes, I will try when the final Oreo comes out (probably middle/end of January).

Downloading , thanks @foobar66
Cant wait to customize and try this out
Cheers

Adblocking:
If you would like to have adblocking do the following:
> adb shell
# su
# hl
The "hl" command will replace the hosts file with a huge (> 200000) hosts which refer to IP address 0.0.0.0; this will make ads go away in your browser and applications.

Dear foobar66. I am waiting for such kind of firmware very long time... But it is a pity this firmware doesn't match for s8+..
Could You help with launching this rom on S8+ for FD version.
And second thing. Could You add screen mirroring to your firmware. We have modern device and mirroring on modern TV is very useful thing
TYVM

Andrunya1978 said:
Dear foobar66. I am waiting for such kind of firmware very long time... But it is a pity this firmware doesn't match for s8+..
Could You help with launching this rom on S8+ for FD version.
And second thing. Could You add screen mirroring to your firmware. We have modern device and mirroring on modern TV is very useful thing
TYVM
Click to expand...
Click to collapse
I don't have an S8+ so I can't test anything.
I can explain how to do a build (if you're familiar with linux).

I haven't linux. Please do it. I can test.
And what about screen mirroring?

[V2][ENGINEERING][ROM][OFFICIAL] OFFICIAL Engineering Firmware for LANCELOT (Redmi 9 / Redmi 9 Prime)

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:

can't install older package over newer one, Nokia 5

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

Better Mobile App

welcome