Related
hi guys, I have an error that i couldnt find a solution by searching in this forum:
i had a full, stock OLYFR_U4_4.1.83 image SBF'd, rooted it, WIFI&tether enabled and sideloading enabled. Also I believe HDMI mirror AND/OR used the Webtop Mod that doesnt require the docking bay. my problem is now, that i get the OTA update to 4.5.91 (about 161 MB), but at reboot-install i get the error
error in /cache/blur_version.4.1.83.MB860.ATT.en.US.zip
status 7
install aborted
I did the WebTop Restore Mod and I *BELIEVE* its put back to "stock"but I am not 100% sure.
can somebody please point me in the right direction to fix this so OTA can be applied ? In addition are there certain things to be considered that I have used the GingerBreak Mod for Root access before the OTA upgrade to 4.5.91 ?
thx-a-thon
cheers
@
imhaving the same issue! Help please!
If I am not mistaken you cannot pull and apply the OTA via the Software update function if you have modified anything in the /system directory. I had a problem because I changed by bootanimation, which got me in a boot loop when trying to install the update. I ended up unlocking via pudding and flashing the 2.3.4 update... You could also update via MSU (Motorola Software Update) via the Motorola Support site..
Edit: Are you using Stock recovery to try to install the update?
Im getting the same error, i think it's because i messed with the bootanimation.zip to remove the default at&t logo... How do I restore that damn logo?
The name of the file which the install/update fails on is in the error. Replace it with the stock apk and you'll be good. It helps to know what mods modified what system file apk's so you can reverse the changes. dockservice.apk, the odex files and portalapp.apk all stopped me from updating OTA; but once I restored factory apk's in the system app path I was good to go.
http://forum.xda-developers.com/showthread.php?t=1163342&page=1
use that .zip to extract any files that you modified. I don't know if that will work but you can try.
It will work as long as all the modified apks are replaced and it is made easier by the fact the ota update tells you which apk or odex file is failing the install.
Sent from my MB860 using Tapatalk
Hello,
I'm using nougat custom rom on my device, (CM/LOS based ) - i.e it is already installed.
I wish to edit the framework.jar internal dex files - AFTER/POST installation of the rom.
I know I can & how to edit the dex & jar, I already made it.
note: I wish to make those change POST rom compiling, since i'm not a rom dev nor know how to compile a rom ( nor need/want to waste time to know how ).
i.e the changes I want to make are to bin/compiled framework.jar that is already installed on the phone.
My problem is that after I replace the orig framework.jar (/system/framework/framework.jar) with the modded one, I get bootloop with errors like:
Code:
Failed to open dex file from oat file. File: /system/framework/framework.jar:classes2.dex Error: Failure to verify dex file '/system/framework/framework.jar:classes2.dex': Bad checksum (0c7053f1, expected 282a531b)
Code:
Could not create image space with image file '/system/framework/boot.art'.
Attempting to fall back to imageless running.
Error was:
Failed to generate image '/data/dalvik-cache/arm/[email protected]@boot.art':
Failed execv(/system/bin/dex2oat --image=/data/dalvik-cache/arm/[email protected]@boot.art --dex-file=/system/framework/core-oj.jar --dex-file=/system/framework/core-libart.jar --dex-file=/system/framework/conscrypt.jar --dex-file=/system/framework/okhttp.jar --dex-file=/system/framework/core-junit.jar --dex-file=/system/framework/bouncycastle.jar --dex-file=/system/framework/ext.jar --dex-file=/system/framework/framework.jar --dex-file=/system/framework/telephony-common.jar --dex-file=/system/framework/voip-common.jar --dex-file=/system/framework/ims-common.jar --dex-file=/system/framework/apache-xml.jar --dex-file=/system/framework/org.apache.http.legacy.boot.jar --dex-file=/system/framework/telephony-ext.jar --dex-file=/system/framework/org.dirtyunicorns.utils.jar --dex-file=/system/framework/telephon
Attempted image: /system/framework/boot.art
after I upload the modded jar I made sure it got 644 permissions & I wipe dalvik&cache from recovery.
I even tried the above + wiping "/data/dalvik-cache/arm/[email protected]@boot.art" - but still got bootloop...
I know i'm really close to success... but I know i'm missing something...
I think that [email protected]@boot.art isn't "regenerate" when I wipe dalvik&cache or when I wipe it manually.
I think also it have something to do with build.prop values like "dalvik.vm.dexopt-data-only=1" or "dalvik.vm.dexopt-flags=m=v,o=y"
if I could only bypass the checksum... everything I guess would work.
I hope someone can help me ( or tell me which sub-forum in xda can help me with this Q ).\
edit:
I understand now that because I hex edit the classes.dex of framework.jar I get that "checksum error" because I should *somehow* "re-calculate" the checksum for that dex file.
I wonder how to do that, without decompiling &recompiling the dex.... anyone ?
I'll appreciate any help,
Thanks.
I posted this a while ago in the [sm-a320fl][7.0][firmware] thread. Now in a new thread, so everybody will find it.
I'm not responsible for any damage. My phone was not branded.
This tutorial is only for SM-A320FL, also known as Galaxy A3!
Make sure you read the whole tutorial before doing anything.
Make a backup of your data. You need to make a factory reset!
Also read the additional information in the separated threads! Knox will be tripped after that, so you can't use it any more. And no more Warranty!
You can find a Android 7 version with the latest security patch with google or just use the linked one. Make sure the CSC is correct for your country/language.
1. Download the following stuff:
Android 7 A320FLXXU1BQH7_A320FLOXA1BQH7_A320FLXXU1BQG6.zip thx to tys0n
Latest Odin3
twrp_3.1.1-1_sm-a320f_11917 thx to ashyx
[*]Boot image patch no-verity-no-encrypt_ashyx thx to ashyx
[*][UNOFFICIAL] Material Design Xposed Installer [09/09/17] thx to DVDandroid
Xposed Installer 3.1.5 thx to rovo89
Magisk thx to topjohnwu
2. Flash Android 7 via Odin. There are enough tutorials on how to do that. Basicly unzip the Android 7 zip file and assign the AP_... file to the AP slot, the BL_... file to the BL slot and so on.
2.a Unlock OEM: Settings -> Developer Options -> OEM unlocking More Information
3. Flash TWRP via Odin; Thread with additional informations
Instructions summary:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst holding POWER + HOME.
You should now see TWRP recovery.
Click to expand...
Click to collapse
4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System.
4. Format Data in TWRP. To do that click on Wipe -> Format Data in TWRP. After that all your data is lost! Reboot to System.
5. Copy the Xposed Installer APK file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP.
6. Copy the Magisk ZIP file to your SD card and install it via TWRP. Reboot to System.
7. Open the Magisk Manager and enable root access via SuperUser within the Manager.
8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed.
8. Open Xposed Installer and install the latest Xposed framework. Follow the steps displayed.
9. Now you should have root access, Magisk and Xposed up and running.
Quotes and additional information:
[RECOVERY][ROOT][TWRP 3.1.1-1] Galaxy A3 - SM-A320F/FL/Y (2017) by ashyx
[*][UNOFFICIAL] Material Design Xposed Installer [09/09/17] by DVDandroid
[2017.9.6] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
[*][2017.9.9][Magisk][SDK 21-25] Xposed v87.3 - Universal Systemless Compatibility by topjohnwu
[OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo by rovo89
---------- Post added at 11:22 AM ---------- Previous post was at 11:07 AM ----------
khanvict90 said:
Any body else have lag with the patern unlock screen ?
Click to expand...
Click to collapse
I had the same problem and it drove me crazy. It appeared every time after I rooted my phone with the old "flash the SuperUser.zip via TWRP" method.
After I rooted my phone via Magisk (Tutorial above), there is no more annoying lag. :good:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
simple_s said:
8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed.
Click to expand...
Click to collapse
Anyway, I face the lockscreen lag even if I use Magisk to root my phone. So, sadly no luck for me...
Thanks for the tutorial.
I have two questions.
1. is it needed to use the Xposed installer by DVDandroid, or does the official one do the same job when using Xposed Magisk module?
2. I read you end in a bootloop when using the Magisk way on the Superman ROM thread for S7
https://forum.xda-developers.com/showpost.php?p=74048136&postcount=11120
answer here
https://forum.xda-developers.com/showpost.php?p=74054639&postcount=11125
does this also happen with A320FL? I installed Xposed in system because of that and have no problems.
y2klol said:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
Click to expand...
Click to collapse
Please read the tutorial! You need SDK 24 if you are on Android 7.
Pat750 said:
Thanks for the tutorial.
I have two questions.
1. is it needed to use the Xposed installer by DVDandroid, or does the official one do the same job when using Xposed Magisk module?
Click to expand...
Click to collapse
I didn't try that. Maybe it will work.
Pat750 said:
2. I read you end in a bootloop when using the Magisk way on the Superman ROM thread for S7
https://forum.xda-developers.com/showpost.php?p=74048136&postcount=11120
answer here
https://forum.xda-developers.com/showpost.php?p=74054639&postcount=11125
does this also happen with A320FL? I installed Xposed in system because of that and have no problems.
Click to expand...
Click to collapse
In my opinion it will do the same thing and get stuck in a boot loop. Didn't try it.
simple_s said:
Please read the tutorial! You need SDK 24 if you are on Android 7.
In my message I stated that I tried both sdk24 and sdk25 neither worked. I only posted the error message for sdk25 but it was the same for 24.
Click to expand...
Click to collapse
y2klol said:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
Click to expand...
Click to collapse
y2klol said:
In my message I stated that I tried both sdk24 and sdk25 neither worked. I only posted the error message for sdk25 but it was the same for 24.
Click to expand...
Click to collapse
In your original post you wrote SDK25 twice. So it is not obvious you meant SDK24 and SDK25.
I'm sorry that it didn't work for you. Did you use all the files in the tutorial? What phone do you have and what Android 7 version?
Is it normal that the system takes a while to boot after flashing no verity no encrypt?
Should i hard reset? It is been like 5 mins
ii_Troy said:
Is it normal that the system takes a while to boot after flashing no verity no encrypt?
Should i hard reset? It is been like 5 mins
Click to expand...
Click to collapse
I had the same issue - turns out I missed the formatting step in TWRP.
Before flashing no verity, go to Wipe > Format Data Partition (I cant remember the exact wording)
simple_s said:
In your original post you wrote SDK25 twice. So it is not obvious you meant SDK24 and SDK25.
I'm sorry that it didn't work for you. Did you use all the files in the tutorial? What phone do you have and what Android 7 version?
Click to expand...
Click to collapse
Oh yes, I did. My apologies. It's A5 (2017) and the firmware is A520FXXS2BQJ1 - Galaxy A5 SM-A520F OPS Australia (Optus). Do I have to use the one posted? What is that?
y2klol said:
Oh yes, I did. My apologies. It's A5 (2017) and the firmware is A520FXXS2BQJ1 - Galaxy A5 SM-A520F OPS Australia (Optus). Do I have to use the one posted? What is that?
Click to expand...
Click to collapse
I only tried this tutorial on an A3. Especially the firmware and the TWRP are specialised for the A3. I think the A5 has also quite a different hardware.
Maybe someone in this thread can help you. They root A5:
A5 Root
All works great on my Galaxy A320FL, thanks !!
atlantix1 said:
Anyway, I face the lockscreen lag even if I use Magisk to root my phone. So, sadly no luck for me...
Click to expand...
Click to collapse
its because you fllashed no verify no encrypt this zip should only be flash when you root with super su ...
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Hi there.
I found something interesting by accident.
Maybe it is not necessary to install the Xposed Framework via Magisk.
Just use the Magisk Manager as a Super SU replacement and install the Xposed Framework (latest version is 89) directly via the new Xposed Installer (latest version is 3.1.5).
Official Xposed by rovo89
It seems that the phone is running a little bit smoother.
Also it seems that the boot patch is causing some problems.
Maybe the whole tutorial needs to be overlooked. But unfortunately I have now time right now.
nekos95 said:
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Click to expand...
Click to collapse
Sorry to hear that. Maybe you can write a new and better one.
simple_s said:
Sorry to hear that. Maybe you can write a new and better one.
Click to expand...
Click to collapse
i kinda just did ... insteed of being ironic you should fix what you did wrong here , you might not realising this but not everyone here has experience to figure things out by himself and your tutorial is causing issues .
nekos95 said:
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Click to expand...
Click to collapse
Sorry I have to replay again. I had just a few minutes this morning.
At point 5 I clearly wrote that you have to install the apk!
At point 8 it should be clear that you have to follow the instructions from Xposed. Everybody knows that and has nothing to do with the basic tutorial.
nekos95 said:
i kinda just did ... insteed of being ironic you should fix what you did wrong here , you might not realising this but not everyone here has experience to figure things out by himself and your tutorial is causing issues .
Click to expand...
Click to collapse
Xposed, Root and what not is nothing for beginners. I clearly mentioned that you have to read a lot of stuff. This is not for beginners. Instead of whining and telling me how to do stuff, just write your own thread. Link everything and mention resources. Not everything in this world is baby save. You have to educate yourself!
I overlooked the whole tutorial. I think it is better now and baby save.
Hello,
I cannot get this to work.
Flashing Android 7.0 works
Installing TWRP works
Installing the xposed apk works
but after flashing the magisk zip file i get the message "verification failed" when trying to boot
How can i fix this?
Edit: I managed to fix it. I had to format after install TWRP
BananaOctopus said:
Hello,
I cannot get this to work.
Flashing Android 7.0 works
Installing TWRP works
Installing the xposed apk works
but after flashing the magisk zip file i get the message "verification failed" when trying to boot
How can i fix this?
Edit: I managed to fix it. I had to format after install TWRP
Click to expand...
Click to collapse
Thank you for your help. I updated my phone to the newest Android 7 version today. I had the same problem and solved it with your method. So I implemented this step into the tutorial.
Hi all, I would really appreciate some help in understanding the instructions on installing Magisk root, from this thread: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 I have already unlocked the bootloader and have highlighted the parts I'm confused about in red:
H. Get HWOTA8_Mate10 Package - I downloaded this.
Magisk
A. Install Magisk by running magisk/magisk.bat and follow instructions. - This I'm stuck on. How do I run magisk.bat. Do I simply have to have the phone connected to PC, and then click the magisk.bat file that is in the HWOTA8 package? Does the phone have to be in fastboot mode. is an adb command involved etc?
B. Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure. Do I do this after Magisk is installed? So I install Magisk manager apk, then I install this module?
THANKS SO MUCH!
A. You need to have the phone connected to the PC in fastboot. You might need the drivers fix, it can be found in the thread. Just run the bat and follow the instructions.
B. Put the zip in your phone after rooting with Magisk, open the Magisk manager app, slide right go to modules and install the zip. Voil
Safe0716 said:
A. You need to have the phone connected to the PC in fastboot. You might need the drivers fix, it can be found in the thread. Just run the bat and follow the instructions.
B. Put the zip in your phone after rooting with Magisk, open the Magisk manager app, slide right go to modules and install the zip. Voil
Click to expand...
Click to collapse
Thanks a ton Safe0716! I just ran the bat now and believe it was successful. I can see the Magisk manager app has been automatically installed (do I need to install something on top of this?).
I have also loaded the zip file onto internal memory, but before I install that zip as a Magisk module, can I ask what the purpose of that zip is?
The instruction says "Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure" . The way its written makes it sound like the zip will cause it to result in safetynet failure (for some reason) - or is the purpose of the zip to PREVENT safetynet failure?
Thanks again!
shadders said:
Thanks a ton Safe0716! I just ran the bat now and believe it was successful. I can see the Magisk manager app has been automatically installed (do I need to install something on top of this?).
I have also loaded the zip file onto internal memory, but before I install that zip as a Magisk module, can I ask what the purpose of that zip is?
The instruction says "Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure" . The way its written makes it sound like the zip will cause it to result in safetynet failure (for some reason) - or is the purpose of the zip to PREVENT safetynet failure?
Thanks again!
Click to expand...
Click to collapse
It's meant to prevent safetynet failure. Without flashing this zip you won't be able to hide root for some apps, let's say you won't be able to use snapchat, netflix etc...
shadders said:
Thanks a ton Safe0716! I just ran the bat now and believe it was successful. I can see the Magisk manager app has been automatically installed (do I need to install something on top of this?).
I have also loaded the zip file onto internal memory, but before I install that zip as a Magisk module, can I ask what the purpose of that zip is?
The instruction says "Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure" . The way its written makes it sound like the zip will cause it to result in safetynet failure (for some reason) - or is the purpose of the zip to PREVENT safetynet failure?
Thanks again!
Click to expand...
Click to collapse
It adds checks that Magisk doesn't check for. Basically Huaweis own props. So it "prevents" failure. It doesn't force safetynet to say OK even though it would fail otherwise, it just adds props to check for that otherwise would make safetynet fail.
And to add to your questions, all bats by mankindtw tell you what to do when you run them, in case you want to use HWOTA8 in the future to update or rebrand.
Safe0716 said:
It's meant to prevent safetynet failure. Without flashing this zip you won't be able to hide root for some apps, let's say you won't be able to use snapchat, netflix etc...
Click to expand...
Click to collapse
Thanks for helping me out Safe0716 I appreciate it I installed the zip and it seems to pass SafetyNet so I'm all set with root (the process was a lot more involved than previous phones I've had but its finally done). Its just a shame that we can't go further and install xposed on this phone!
shadders said:
Thanks for helping me out Safe0716 I appreciate it I installed the zip and it seems to pass SafetyNet so I'm all set with root (the process was a lot more involved than previous phones I've had but its finally done). Its just a shame that we can't go further and install xposed on this phone!
Click to expand...
Click to collapse
Yeah unfortunately it isn't working yet, but I'm sure somebody will figure it out !
ante0 said:
It adds checks that Magisk doesn't check for. Basically Huaweis own props. So it "prevents" failure. It doesn't force safetynet to say OK even though it would fail otherwise, it just adds props to check for that otherwise would make safetynet fail.
And to add to your questions, all bats by mankindtw tell you what to do when you run them, in case you want to use HWOTA8 in the future to update or rebrand.
Click to expand...
Click to collapse
Thanks for that info, I now have a better understanding. And ah in terms the bats, yes I saw when I clicked on it that it did indeed have helpful instructions! But I assumed there was certain things I had to do before running it, e.g. fastboot mode, and so was scared to click on it!
Should be helpful in the future. Now that I am rooted with Magisk, does that mean I can no longer accept OTAs and updates will have to go through HWOTA8? If so, will updating through HWOTA8 wipe the system, or preserve user data? Thanks!
shadders said:
Thanks for that info, I now have a better understanding. And ah in terms the bats, yes I saw when I clicked on it that it did indeed have helpful instructions! But I assumed there was certain things I had to do before running it, e.g. fastboot mode, and so was scared to click on it!
Should be helpful in the future. Now that I am rooted with Magisk, does that mean I can no longer accept OTAs and updates will have to go through HWOTA8? If so, will updating through HWOTA8 wipe the system, or preserve user data? Thanks!
Click to expand...
Click to collapse
I haven't received any yet... But I tend to update as soon as an update is pushed to http://pro-teammt.ru/firmware-database/
which is long before it's actually pushed to the public (long being 2 weeks+).
Userdata is preserved when you update FullOTA updates and bootloader remains unlocked. So you just need to reflash Magisk after it's done updating.
Magisk data (modules) is kept too as that's kept in /data/
Hey guys
I tried to change the ROM from my chinese Mi Box to the US version with a guide
But I made something wrong and ended up in the stock-recovery
luckily I was able to update the Box from the recovery with a update.zip (which is for the MDZ-19-AB US version)
Everything worked fine, but I was greedy and wanted to update with the same procedure to Android TV 8.0 and I soft-bricked the device but I can still get into the recovery
I tried to go back to Android TV 7.0 with the update.zip but the update checks if ("ro.product.device") is equal to "once" which was "once" but after the 8.0 update is somehow empty
I even tried tho unbrick it with a guide and the USB burning tool but that doesnt work either
I tried to take the update.zip remove the check form the updater-script and zip it and even sign it (with multiple different tools) but I am unable to get it working (either "footer is wrong" or "failed to verify whole-file signature" error comes up)
TL/DR: Can someone take the update.zip remove the check for the device in the updater script(first line), zip and sign it properly so I can update it with the stock-recovery?
it seems like I am unable to do it myself
please PM me if you can help I'n not allowed to add outside-links :crying:
remo_94 said:
Hey guys
I tried to change the ROM from my chinese Mi Box to the US version with a guide
But I made something wrong and ended up in the stock-recovery
luckily I was able to update the Box from the recovery with a update.zip (which is for the MDZ-19-AB US version)
Everything worked fine, but I was greedy and wanted to update with the same procedure to Android TV 8.0 and I soft-bricked the device but I can still get into the recovery
I tried to go back to Android TV 7.0 with the update.zip but the update checks if ("ro.product.device") is equal to "once" which was "once" but after the 8.0 update is somehow empty
I even tried tho unbrick it with a guide and the USB burning tool but that doesnt work either
I tried to take the update.zip remove the check form the updater-script and zip it and even sign it (with multiple different tools) but I am unable to get it working (either "footer is wrong" or "failed to verify whole-file signature" error comes up)
TL/DR: Can someone take the update.zip remove the check for the device in the updater script(first line), zip and sign it properly so I can update it with the stock-recovery?
it seems like I am unable to do it myself
please PM me if you can help I'n not allowed to add outside-links :crying:
Click to expand...
Click to collapse
that would be nice if anyone actually had the keys needed to sign it to pass verification lol
remo_94 said:
Hey guys :crying:
Click to expand...
Click to collapse
Hey, you can extract the updater-script from the package, edit it, then repack it to the same zip(preserving the signature)
Ricky Divjakovski said:
Hey, you can extract the updater-script from the package, edit it, then repack it to the same zip(preserving the signature)
Click to expand...
Click to collapse
wouldnt that break the whole file signature?
elliwigy said:
wouldnt that break the whole file signature?
Click to expand...
Click to collapse
Pretty sure it doesnt aslong as you repack with the update method, same way your able to mod certain apps inside/system preserving the signature
But.. im pretty sure ive got amlogics keys somewhere though
Ricky Divjakovski said:
Pretty sure it doesnt aslong as you repack with the update method, same way your able to mod certain apps inside/system preserving the signature
But.. im pretty sure ive got amlogics keys somewhere though
Click to expand...
Click to collapse
I guess with the "update method" you mean just edit the file in the archive without extracting and repacking.
I tried with WinRAR and 7-zip, I tried editing it inside the archive and saving the changes, I tried extracting editing and repacking it, I even edited the MANIFEST.MF to the new SHA-1 value of the update-script but I only get "failed to verify whole-file signature"
I thought it was enough if I sign my update.zip with the Android testkeys isn't that possible?
remo_94 said:
I guess with the "update method" you mean just edit the file in the archive without extracting and repacking.
I tried with WinRAR and 7-zip, I tried editing it inside the archive and saving the changes, I tried extracting editing and repacking it, I even edited the MANIFEST.MF to the new SHA-1 value of the update-script but I only get "failed to verify whole-file signature"
I thought it was enough if I sign my update.zip with the Android testkeys isn't that possible?
Click to expand...
Click to collapse
Ill look more into it tonight