Database Users

Impossible to flash latest MIUI 2.11.30

Hi All,
I'm trying to flash the latest MIUI 2.11.30 to my Galaxy SIII int without success.
I'd like to not install the chinese stock as requested on the MIUI site so I'm asking if someone was able to flash it from recovery on another rom.
Now I'm on Omega 3.33 with TWRP recovery but I also tried with Paranoid 2.54 and CWM touch without success.
I always get this error message:
Code:
assert failed: getprop("ro.product.device") == "~truncated
getprop("ro.build.product") == "m0" || ge~truncated
E:Error in "zip file path" (status 7)
Error flashing zip "zip file path"
Anyone knows a possible solution?
Thank you very much!
Bye.

Try altering the install script in the zip file to say "galaxys3" instead of "m0".
Sent from my GT-I9300 using Tapatalk 2

Theshawty said:
Try altering the install script in the zip file to say "galaxys3" instead of "m0".
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the advice, no luck with that but I solved it removing this assert statement:
Code:
assert(getprop("ro.product.device") == "m0" ||
getprop("ro.build.product") == "m0" || getprop("ro.product.device") == "m0" || getprop("ro.build.product") == "m0");
from this file inside the zip:
META-INF\com\google\android\updater-script
Thanks again for the advice, I took a look around and I saw that. :good:
Bye!

Now that it's solved, Thread closed.

[Q] Super Su Fix

hello guys ... i want the super SU fix because it doesn't have the Binary installed and it doesn't want to install help needed plz

here is it http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip

mohamedrashad said:
here is it http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Click to expand...
Click to collapse
Thanks ... is it a flashable .zip ??
Sent from my GT-S5360 using XDA Free mobile app

Omar El- Hussien said:
Thanks ... is it a flashable .zip ??
Sent from my GT-S5360 using XDA Free mobile app
Click to expand...
Click to collapse
no
thats a zip from chainfire
extract zip
pull su inside arm folder
n superuser it self
create a folder
system/app/superuser apk
/xbin/su
zip ur folder
sign with zipsigner.apk
then extract that zip again
under meta-inf u can found
com/google/android/update binary
under binary u must make a updater-script file
open it and follow this code
Code:
show_progress(0.1, 0);
mount("rfs", "EMMC", "/dev/block/stl9", "/system");
show_progress(0.500000, 0);
ui_print("");
run_program("/tmp/busybox", "mount", "/system");
ui_print("");
ui_print("");
ui_print("Initializing");
ui_print("");
ui_print("Please Wait");
ui_print("");
ui_print("");
delete("/system/app/Superuser.apk");
delete("/system/xbin/su");
package_extract_dir("system", "/system");
show_progress(0.200000, 0);
show_progress(0.200000, 10);
ui_print("Setting Permissions");
set_perm_recursive(0, 0, 0755, 0644, "/system/app");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su","/system/bin/su");
show_progress(0.100000, 0);
ui_print("Finish");
ui_print("");
ui_print("");
unmount("/system");
ZIP again n sign using zipsigner apk
flash under cwm
or u can google it if u bored

or you could just flash my zip in cwm with system mounted
uninstall any superuser/supersu you have first
http://d-h.st/kFt

Minions_Army said:
no
thats a zip from chainfire
extract zip
pull su inside arm folder
n superuser it self
create a folder
system/app/superuser apk
/xbin/su
zip ur folder
sign with zipsigner.apk
then extract that zip again
under meta-inf u can found
com/google/android/update binary
under binary u must make a updater-script file
open it and follow this code
Code:
show_progress(0.1, 0);
mount("rfs", "EMMC", "/dev/block/stl9", "/system");
show_progress(0.500000, 0);
ui_print("");
run_program("/tmp/busybox", "mount", "/system");
ui_print("");
ui_print("");
ui_print("Initializing");
ui_print("");
ui_print("Please Wait");
ui_print("");
ui_print("");
delete("/system/app/Superuser.apk");
delete("/system/xbin/su");
package_extract_dir("system", "/system");
show_progress(0.200000, 0);
show_progress(0.200000, 10);
ui_print("Setting Permissions");
set_perm_recursive(0, 0, 0755, 0644, "/system/app");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su","/system/bin/su");
show_progress(0.100000, 0);
ui_print("Finish");
ui_print("");
ui_print("");
unmount("/system");
ZIP again n sign using zipsigner apk
flash under cwm
or u can google it if u bored
Click to expand...
Click to collapse
Hey this is universal I flashed it numerous times successfully
Sent from my GT-S5360 using Tapatalk 2

why not use the newest versions?

marcussmith2626 said:
or you could just flash my zip in cwm with system mounted
uninstall any superuser/supersu you have first
http://d-h.st/kFt
Click to expand...
Click to collapse
the only problem with your flashable .zip file is that you must un-install any other APK super user or super su ... and here comes the problem ... you cant delete it by system \ app \...etc Root explorer doesnt have root permission ... also same problem with the Link2Sd .... so i think you must add an un-installer on your zip file

-CALIBAN666- said:
why not use the newest versions?
Click to expand...
Click to collapse
its not related to an update i tried that alot ....

Omar El- Hussien said:
the only problem with your flashable .zip file is that you must un-install any other APK super user or super su ... and here comes the problem ... you cant delete it by system \ app \...etc Root explorer doesnt have root permission ... also same problem with the Link2Sd .... so i think you must add an un-installer on your zip file
Click to expand...
Click to collapse
You can just flash it and remove duplicate apps after if you want - shouldn't be a problem
Or add a line to delete the name of the superuser/supersu app in the updater script

Unsupported bootloader for Blisspoprom 4.0 - T530

Hello everyone!
After finally figuring out how to boot into TWRP on the norwegian version of this device, I was crazy with exitement about flashing blisspoprom, but I get this error message:
This package supports bootloader (s) T530XXU1B0D8, T530NUUEU1B0E5; this device has bootloader T530XXU1B0G2
I have flashed a lot of devices, but I haven't really looked into bootloaders., as I've never encountered this problem before.
Is it possible to replace the bootloader on my device at all? Or are there version of the ROM out there that supports my bootloader?
N00b questions, indeed, but it's proven quite hard to find information on google searches on this subject, and everything I've found seems to be device specific. I tried to flash stock with bootloader update checked in Odin, but that didnæt change the bootloader number...

Open the rom file in 7zip or WinRar, go to META-INF/com/Google/Android and open the updater-script with notepad++. Delete the first line of the updater-script (it should have the word "assert" in it ". Save it and now try flashing the rom

thisisapoorusernamechoice said:
Open the rom file in 7zip or WinRar, go to META-INF/com/Google/Android and open the updater-script with notepad++. Delete the first line of the updater-script (it should have the word "assert" in it ". Save it and now try flashing the rom
Click to expand...
Click to collapse
Thank you sir! Much appreciated.
I got the file open in Notepad, would it be awfully blunt of me to ask you how much of this I need to delete? There's two lines starting with "assert" so I thought It would be safest to ask.
"assert(getprop("ro.product.device") == "matissewifi" || getprop("ro.build.product") == "matissewifi" || abort("This package is for device: matissewifi; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "T530XXU1BOD8" || getprop("ro.bootloader") == "T530NUUEU1BOE5" || abort("This package supports bootloader(s): T530XXU1BOD8, T530NUUEU1BOE5; this device has bootloader " + getprop("ro.bootloader") + ".");
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
....

MadBigMadBoatMan said:
Thank you sir! Much appreciated.
I got the file open in Notepad, would it be awfully blunt of me to ask you how much of this I need to delete? There's two lines starting with "assert" so I thought It would be safest to ask.
"assert(getprop("ro.product.device") == "matissewifi" || getprop("ro.build.product") == "matissewifi" || abort("This package is for device: matissewifi; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "T530XXU1BOD8" || getprop("ro.bootloader") == "T530NUUEU1BOE5" || abort("This package supports bootloader(s): T530XXU1BOD8, T530NUUEU1BOE5; this device has bootloader " + getprop("ro.bootloader") + ".");
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
....
Click to expand...
Click to collapse
Delete the following:
"assert(getprop("ro.product.device") == "matissewifi" || getprop("ro.build.product") == "matissewifi" || abort("This package is for device: matissewifi; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "T530XXU1BOD8" || getprop("ro.bootloader") == "T530NUUEU1BOE5" || abort("This package supports bootloader(s): T530XXU1BOD8, T530NUUEU1BOE5; this device has bootloader " + getprop("ro.bootloader") + ".");
Click to expand...
Click to collapse
Leave everything beginning with package_extract_dir("install", '/tmp/install");
Also just making sure, you are using the latest version of BlissPop, correct? Located here, you want the one named BlissPop-v4.0.1-matissewifi-UNOFFICIAL-20150917-1958.zip (note you want the one dated 20150917, not the one dated 20150912).
Also I'd recommend using notepad++ rather than regular notepad, idk if that's absolutely necessary, just a recommendation

thisisapoorusernamechoice said:
Delete the following:
Leave everything beginning with package_extract_dir("install", '/tmp/install");
Also just making sure, you are using the latest version of BlissPop, correct? Located here, you want the one named BlissPop-v4.0.1-matissewifi-UNOFFICIAL-20150917-1958.zip (note you want the one dated 20150917, not the one dated 20150912).
Also I'd recommend using notepad++ rather than regular notepad, idk if that's absolutely necessary, just a recommendation
Click to expand...
Click to collapse
Flashing!
4.0 for now, didn't want to wait for another download. I'll try 4.0.1 if there's any hithches. And, regular notepad seems to have done the trick, I hadn't heard of ++ before but I'll check it out.

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

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

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

kccat6 twrp fails upgrade to 15.1 updater-script issues

Folks.
I am sure this has been fixed before but I cannot find it using Google-fu or XDA searches.
I have a S5 G901f running Lineage OS 14.1 [14.1-20180615-NIGHTLY-kccat6]
I want to upgrade to 15 so I downloaded the nightly image file from here: hxxxps://download.lineageos.org/kccat6
I got the Feb 15 and Feb 8 versions just to make sure.
lineage-15.1-20190215-nightly-kccat6-signed.zip
lineage-15.1-20190206-nightly-kccat6-signed.zip
They fail on TWRP twrp-3.2.3-0-kccat6.img with Error Code 7, because my phone fails to report any device at all, it reports as null. [Note there is also a non fatal error reporting no Digest file found but I believe that's not the issue.
So I edited the update-script to remove the device check: vis
I removed this totally:
assert(getprop("ro.product.device") == "kccat6xx" || getprop("ro.build.product") == "kccat6xx" ||
getprop("ro.product.device") == "kccat6" || getprop("ro.build.product") == "kccat6" || abort("E3004: This package is for device: kccat6xx,kccat6; this device is " + getprop("ro.product.device") + ".");
ui_print("Target: samsung/kccat6xx/kccat6:6.0.1/MMB29M/G901FXXS1CPLA:user/release-keys");
Click to expand...
Click to collapse
But then TWRP fails with Error 6, which is almost certainly to do with this line later in update-script:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
Click to expand...
Click to collapse
and then I guess this one would fail:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
Click to expand...
Click to collapse
So, boys and girls, how do I edit the updater-script to make it work, or is there a variant TWRP that I can use which somehow fixes this?
Your kind advice is very welcome, and if I have posted incorrectly, please steer me aright..