mipay-extract
mipay-extract copied to clipboard
linusyang92
error when extracting apps from CEPHEUS v9.3.22 (mi9)
BTW, is there any software can be used to manually extract apps from the .img files? Thanks!
--> rom: CEPHEUS v9.3.22
Scanning the drive for archives: 1 file, 2678999087 bytes (2555 MiB)
Extracting archive: ../miui_CEPHEUS_9.3.22_c63654cc2f_9.0.zip
Path = ../miui_CEPHEUS_9.3.22_c63654cc2f_9.0.zip Type = zip Physical Size = 2678999087 Comment = signed by SignApk
Everything is Ok
Files: 2 Size: 2024834027 Compressed: 2678999087 sdat2img binary - version: 1.0
Android Nougat 7.x / Oreo 8.x detected!
←[Kextracting |################################| 100% ←[?25hDone! Output image: miui-CEPHEUS-9.3.22-system.img --> image extracted: miui-CEPHEUS-9.3.22-system.img --> copying apps ----> copying Mipay... ----> copying NextPay... ----> copying TSMClient... ----> copying UPTsmService... grep: system/build.prop: No such file or directory
ERROR: No more files system/app
System ERROR: Unknown error -2147024872 --> deodexing Mipay... ----> classes: basename: missing operand Try 'basename --help' for more information. Can't find file: system/app/Mipay/oat/arm64/Mipay.odex/ --> abort --> clean deodex Press any key to continue . . .
May be miui10 or Mi9 starts the structure change in img. My forked has been modified. But my MI9 has not been received, so I haven't tested it yet.
May be miui10 or Mi9 starts the structure change in img. My forked has been modified. But my MI9 has not been received, so I haven't tested it yet.
Thanks for the info. I will test your forked soon.
mabloshi's version works, with some modification: The former path of "/system/app" in MIUI has been switched to "/system/system/app", and the "/system/framework" to "/system/system/framework", change the path in update-binary files seems to work for mine.
However, the file "system/vendor/etc/fstab.qcom" has been located in" /vendor/etc/fstab.qcom", and the encryption had been modified as "fileencryption=ice", whereas the /data partition is not encrypted after a wipe of /data partition and reboot. Maybe the encryption setting changed?
@ranio Thank you very much for testing. I got the phone in the afternoon and I also tested it. Encryption is now enabled by default. ~~but you need to set the screen lock~~ /data has encrypted, but /data/media/0 or /sccard has not encrypted.
Under TWRP, you can try
$adb shell
cepheus:/ # ls /data/app/
9Kh1XDKsv5uwuYvf5jEQ+uL1xRN _MIDN7Hb2jTjIGdqRFYInG6DgkihlCexg/ _eTfJ+2wIE+ffYKSaaN6USeybShGcHizl/ _uPUXKX7UVSP51dBUYPtMFo+Tl2MkNEK5/
_+i7DL,fOPsFOTN4BuCtbrQXCDDrDsGbF/ _MSup9j5oFSjv,ikA9ZlrYUWAMiam+TI0/ _g48IDgcatD6hbHuWDr126DWnuAaS3slS/
@maboloshi Thanks for your feedback. Screen lock has been enabled on my phone, I just checked the path /data/app, it has been encrypted. Could you please check whether the path "/data/media/0" or "/sccard"(the same one as previous) has been encrypted on yours, which was not on my phone.
update: According to the metadata encryption,
Metadata encryption can only be set up when the data partition is first formatted. As a result, this feature is only for new devices; this is not something an OTA should change.
So just after formatting of the data partition under TWRP, the metadata encryption works (if it doesn't work, try it again).
@ranio The official Miui version has encrypted /data and /sdcard. The EU version has encrypted
/data, but has not encrypted for /media/0 or /sccard.
@linusyang92 Thanks for the update, it works. @maboloshi After a test on my Mi9, the xiaomi.eu supports encryption for /sdcard, however, as mentioned above, it needs a thorough formation of the data partition after flashing the extracted apps.
cleaner-fix mi9 eroor
.\cleaner-fix.bat
--> rom: MI9 v9.4.11
7-Zip [32] 15.14 : Copyright (c) 1999-2015 Igor Pavlov : 2015-12-31
p7zip Version 15.14.1 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,32 bits,16 CPUs AMD Ryzen 7 1700 Eight-Core Processor (800F11),ASM,AES-NI)
Scanning the drive for archives:
1 file, 2386267489 bytes (2276 MiB)
Extracting archive: ../xiaomi.eu_multi_MI9_9.4.11_v10-9-v2.zip
--
Path = ../xiaomi.eu_multi_MI9_9.4.11_v10-9-v2.zip
Type = zip
Physical Size = 2386267489
Comment = signed by SignApk
Everything is Ok
Files: 2
Size: 1405596791
Compressed: 2386267489
sdat2img binary - version: 1.0
Android Nougat 7.x / Oreo 8.x detected!
extracting |################################| 100%
Done! Output image: miuieu-MI9-9.4.11-system.img
--> image extracted: miuieu-MI9-9.4.11-system.img
--> copying apps
----> copying Calendar...
----> copying SecurityCenter...
grep: system/build.prop: No such file or directory
ERROR: No more files
system/priv-app
System ERROR:
Unknown error -2147024872
grep: system/build.prop: No such file or directory
ERROR: No more files
system/priv-app
System ERROR:
Unknown error -2147024872
--> packaging flashable zip
--> done
--> all done
@hcwhan Try the latest version. I don't own a Mi 9, thus cannot test if the generated zip actually works. But the detection in the installer script should work in theory, which dynamically tests if the device has /system/app or /system/system/app and extracts files correspondingly.
Same kind of error occured when I try @maboloshi forked ver with Mi5 ROM. New to this, do not know what to do, any help please?
--> rom: MI5Global v8.11.22
--> image extracted: miui-MI5Global-8.11.22-system.img
--> copying apps
----> copying Mipay...
----> copying NextPay...
----> copying TSMClient...
----> copying UPTsmService...
ERROR: No more files
system/app
System ERROR:
Unknown error -2147024872
--> deodexing Mipay...
----> classes:
basename: missing operand
Try 'basename --help' for more information.
Can't find file: system/app/Mipay/oat/arm64/Mipay.odex/
--> abort
--> clean deodex
