i have a sony xperia xz premium device and i want to update to android 10 i downloaded the update file from the sony site how can i install please help thanks.
And why are you posting here?i have a sony xperia xz premium device and i want to update to android 10 i downloaded the update file from the sony site how can i install please help thanks.
Sony Xperia XZ Premiumi have a sony xperia xz premium device and i want to update to android 10 i downloaded the update file from the sony site how can i install please help thanks.
This is not a general help desk, go start a thread in the Q&A forum or the forum for your device.how to install sony xperia xz premium android 10 update isitorum published sony update file please help.
English, please.Ben yeniyim ve ingilizcem çok iyi değil üzgünüm
News to me. I had fixed it a little while back for 21402+, but I guess it needs something new again. Can you provide a log of the breakage? I'll take a look.The latest (22.x) version of Magisk no longer supports the A/B Retention Script, which I have been happily using for a year or so, whenever I want to upgrade the OS on my A/B device (OnePlus 7Pro - GM-1917).
I am not upgrading Magisk from 21.4 to the latest 22.x because of this.
But at some point, I'll probably want to upgrade to the later version of Magisk, so i am wondering what steps I can take manually -- if possible -- to emulate the very helpful functionality of the A/B Retention Script under Magisk 22.x.
Or am I simply out of luck?
Oh, I'm sorry. I was just going by the Magisk update log where it said that the A/B Retention script is not supported, so I didn't even try to upgrade Magisk and check it out. But I will check now and get back to you.News to me. I had fixed it a little while back for 21402+, but I guess it needs something new again. Can you provide a log of the breakage? I'll take a look.![]()
News to me. I had fixed it a little while back for 21402+, but I guess it needs something new again. Can you provide a log of the breakage? I'll take a look.![]()
Oh, I'm sorry. I was just going by the Magisk update log where it said that the A/B Retention script is not supported, so I didn't even try to upgrade Magisk and check it out. But I will check now and get back to you.
Ah, that's not what it says; I believe you're referring to the Magisk Install to Inactive Slot (after OTA) option being unavailable on specifically Virtual A/B devices since it's a different verification process for the new slot which occurs after the reboot and we don't know how to work around it currently.Oh, I'm sorry. I was just going by the Magisk update log where it said that the A/B Retention script is not supported, so I didn't even try to upgrade Magisk and check it out. But I will check now and get back to you.
Oh, I've never learned what a "virtual" A/B device is, and that message about it confused me. I guess it must differ somehow from the way my OnePlus 7Pro A/B device is architected.Ah, that's not what it says; I believe it's referring to the Magisk Install to Inactive Slot (after OTA) option being unavailable on specifically Virtual A/B devices since it's a different verification process for the new slot which occurs after the reboot and we don't know how to work around it currently.
@osm0sis I decide to downgrade magisk to 20.4 & there's no problem with symlink. But on 21.x to 22.x I should nolink it.Well I'm really not sure then, I guess your device just has something that conflicts within xbin. My advice would be to uninstall, then use the advanced options file to skip symlink creation during an install by running this command beforehand:
`echo NOLINKS > /data/.busybox-ndk`
That's super weird. I have no such issues on my devices.@osm0sis I decide to downgrade magisk to 20.4 & there's no problem with symlink. But on 21.x to 22.x I should nolink it.
Yup that's it. Anything else I could provide (boot.img probably), since the boot log won't help much, I had taken it many times & the result was the same as I posted here ?That's super weird. I have no such issues on my devices.![]()
Well arguably it's something related to a change in Magisk on your device, rather than my module or my installer, since the symlinks should be the same regardless since they're in xbin.Yup that's it. Anything else I could provide (boot.img probably), since the boot log won't help much, I had taken it many times & the result was the same as I posted here ?
Magisk path is the same for both, they're in /sbin. Differences are in /sbin/.magisk/mirror, on v20.4 it has folders named system, data & vendor while on v22.0 it adds / includes folders cache, persist & sepolicy.rules. For sepolicy.rules folder I saw it linked to modules folder.Well arguably it's something related to a change in Magisk on your device, rather than my module or my installer, since the symlinks should be the same regardless since they're in xbin.
Can you give me the output of `su -c magisk --path` on 20.4 plus the list of symlinks in the busybox module, and then the same on 22.0?
I attached both.They're just whatever the zip reported when it failed. It shouldn't flash "*.zip" though, that's weird. I've never seen that before.
Can you show me the contents of the directory? And the zip? You should try enabling verbose and logging to see what's going on with the flashing as well, and show me that.
I use to build and flash a LOT of custom ROMs for my previous phones. I found that a LOT (but not all) of the customisations were stored in the android settings. As such, I built the saving off of these settngs, and the generation of a script to reinstate them into my app TeMeFI. You can find these functions underForgive me if this is OT (and feel free to delete this post if it is). But since lots of helpful tools and utiltities are discussed in this thread, I'm guessing that perhaps someone here would be knowledgeable about my question:
I do a lot of testing of different ROMs on my OnePlus 7Pro. Once I get a new ROM set up, I go through a time-consuming and annoying procedure of resetting a lot of the basic Settings to values that I prefer. I'm wondering: is there a utility that will allow me to save a collection of Settings into some sort of file that I can push to my device with a newly flashed ROM, and another utility (or perhaps the same one with a different option) which I can use to install this group of saved settings onto the device, all at once?
Thank you in advance for any thoughts or suggestions.
Current State>Settings>*
NB: All the script code is available from the app.No, you should probably wait for me to push the stripped release builds to the Magisk module repo.excuse my lack of knowledge; is this good for 'magisk install'? i'm on your 'busybox for android ndk' 1.31.1(13123).
# also this
home=~;
magisk=$home/Magisk;
bold() { echo -e "\033[1m"[email protected]"\033[0m"; }
cd "$home";
case $1 in
help) echo "bbox-bundle.sh [verbose] [nocopy]"; exit 1;;
verbose) stdout=/dev/stdout; shift;;
*) zipflag=-q; stdout=/dev/null;;
esac;
rm -f Busybox-*-ALL*.zip UPDATE-Busybox.Installer.*-ALL-signed.zip 2>/dev/null;
ver=$(ls | grep ^busybox- | cut -d- -f2);
if [ -f AIK-build/mobile/arm/busybox -a "$1" != "nocopy" ]; then
bold "- Copying new Busybox $ver builds ...";
cd AIK-build/mobile;
for i in *; do
cp -fp $i/busybox $magisk/UPDATE-Busybox.Installer.*-ALL/busybox-$i;
done;
cd "$home";
fi;
if [ -f android/git/ndk-box-kitchen/libs/armeabi-v7a/busybox -a "$1" != "nocopy" ]; then
bold "- Copying new Busybox $ver SELinux builds ...";
cd android/git/ndk-box-kitchen/libs;
for i in *; do
case $i in
armeabi-v7a) out=arm;;
arm64-v8a) out=arm64;;
*) out=$i;;
esac;
cp -fp $i/busybox $magisk/UPDATE-Busybox.Installer.*-ALL/busybox-$out-selinux;
done;
cd "$home";
fi;
modver=$(grep -o "^version=.*$" $magisk/UPDATE-Busybox.Installer.*-ALL/module.prop | cut -d= -f2);
modcode=$(grep -o "^versionCode=.*$" $magisk/UPDATE-Busybox.Installer.*-ALL/module.prop | cut -d= -f2);
if [ "$ver" == "$modver" ]; then
newmodver="$modver";
newmodcode="$((modcode + 1))";
iteration=1;
else
newmodver="$ver";
newmodcode="${ver//.}0";
fi;
if [ "$iteration" ]; then
echo -ne "\033[1m\n*** Update Magisk module version code ($modcode -> $newmodcode) (y/n)? \033[0m";
read n; echo;
case $n in
Y|y) ;;
*) skipmodprop=1;;
esac;
fi;
if [ ! "$skipmodprop" ]; then
sed -i -e "s/version=.*/version=$newmodver/" -e "s/versionCode=.*/versionCode=$newmodcode/" $magisk/UPDATE-Busybox.Installer.*-ALL/module.prop;
fi;
bold "- Packing \"Busybox-$ver-ALL.zip\" ...";
cd $magisk/UPDATE-Busybox.Installer.*-ALL;
zip -9 -x .git -r $zipflag "$home"/Busybox-$ver-ALL.zip *;
curdir=$(basename $PWD);
cd ..;
if [ "$curdir" != "UPDATE-Busybox.Installer.v$ver-ALL" ]; then
mv UPDATE-Busybox.Installer.*-ALL UPDATE-Busybox.Installer.v$ver-ALL;
fi;
cd "$home";
bold "- Signing as \"UPDATE-Busybox.Installer.v$ver-ALL-signed.zip\" ...";
java -jar zipsigner-*.jar Busybox-$ver-ALL.zip Busybox-$ver-ALL-signed.zip;
mv -f Busybox-$ver-ALL-signed.zip UPDATE-Busybox.Installer.v$ver-ALL-signed.zip 2>/dev/null;
rm -f Busybox-*-ALL.zip /tmp/signAPK*.tmp 2>/dev/null;