I tried to flash xposed so many times but it didn't work. I have Samsung Galaxy S5 marshmallow 6.0.1 ARMv7.
And while downloading the .zip file i found another file .asc which idk what is it for (I'm new to rooting, xposed and all of this) so i start to wonder if this small file has something to do with the installation.
I tried to flash the .zip file with TWRP.
Any help will be much appreciated
I installed without it, no problem. I think it's just to verify the integrity of the download, but I'm not certain. I too would like to know this.
It's just a fingerprint file, not needed except if you are unsure if the zip file downloaded correctly.
Related
Issue... my wifi is not working. I tried every solution when it comes to wifi and some. I tried different ROMS and still no dice. I came across this WIFI Fix file that is a zip file and wanted to try and install it. Since I have no WIFI I cant use ROM Manager to install.
I dont know if you can use ADB to install a zip file? I know you can probably do it for a .apk file, but not a zip? Correct me if I'm wrong.
I tried renaming the file to update and using recovery to flash it but it runs then aborts.
Any programs I can use to flash this file to see if it works?
Thanks.
you simply put it in OpenRecovery/Updates/ folder and then apply the update.
It's in the same folder where you put your custom rom that you want to install, and you install it the same way as you do for custom roms, just that you choose the WIFI Fix.zip instead of the custom rom obivously.
I've got a phone that may or may not be totally frakked due to careless build.prop modding and have been asked to try and recover it without wiping, OS flashing, or any other methods that could potentially lead to a wipe. ADB is a no-go, but I've got CWM access. I've never needed to make a CWM-flashable *.zip before, so I never learned how. I'm crunched for time and could really just use a break. Could somebody please put this build.prop into a CWM-flashable *.zip for me?
i new user, how i can upload my build prop
I would be extremely grateful!
Thanks in advance!
i must get 10 post.. jeez..
Hi, try to use Aroma File Manager. With it you can copy your new build.prop to the appropriate location.
To use the file manager, simply download it to your computer, copy it onto your phone through recovery and then when you are in recovery go for flash zip and choose the file you downloaded.
Hi Everyone!
I followed the instructions to upgrade to Nougat from MM, this includes a file named update_data_full_hw_la.zip
http://ministryofsolutions.com/2017/01/huawei-p9-plus-vie-l29-nougat-b354-latin-america.html
The step that I cant seem to install this file, I tried:
Renaming file to update.zip and try to apply it through forced update (DIDNT WORK)
Extract all the content into dload folder (DIDNT WORK)
The content has an UPDATE.APP file and multiple folders. The forced update goes really fast and does not seem to install anything.
The ROM itself does not have many apps so I guess this zip should have everything else that is missing from the ROM but I cant seem to install it properly.
Any help on this? How am I supposed to install it?
jeinnerabdel said:
Hi Everyone!
I followed the instructions to upgrade to Nougat from MM, this includes a file named update_data_full_hw_la.zip
http://ministryofsolutions.com/2017/01/huawei-p9-plus-vie-l29-nougat-b354-latin-america.html
The step that I cant seem to install this file, I tried:
Renaming file to update.zip and try to apply it through forced update (DIDNT WORK)
Extract all the content into dload folder (DIDNT WORK)
The content has an UPDATE.APP file and multiple folders. The forced update goes really fast and does not seem to install anything.
The ROM itself does not have many apps so I guess this zip should have everything else that is missing from the ROM but I cant seem to install it properly.
Any help on this? How am I supposed to install it?
Click to expand...
Click to collapse
try the alternative method:
Alternative Method
Remove update files from your phone, if you have copied before
Download Huawei updater from This Link
Download latest Hisuite from official huawei website
Open huawei update, tick in custom rom, in custom rom version type VIE-L29C605B354
In Custom rom URL copy this link http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1257/g104/v71996/f1/
Then tick custome port, don’t change it.
now connect your phone with pc and make sure Hisuite recognize and connected properly. then just open Hisuite menu and change network settings as shown in image below.
Easy-Nougat-Update-2.png
Then in hisuite click check for update
it should start downloading and installing firmware
Thanks, but that method won't work as the ROM itself was already applied, therefore, HiSuite returns a message saying that I'm on the most updated version.
The file m trying to apply should contain apps like the calculator, Bluetooth, compass, etc. These apps are not part of the ROM but they come on a separate zip file.
The issue seems to be that apps are not compatible with the Nougat ROM already installed.
Any other thoughts?
If any of you has an update zip containing all remaining apps, please share!
The problem u are facing could be 2. Cust and oeminfo but fitting the package and /of rom. And the two packages need to be installed immediately with starting with the hw update, after that the normal one. Tell me which version and cust we are talking about?
I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
eliotargy said:
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Can anyone advise me further?
Click to expand...
Click to collapse
Usually the file is corrupted if the file comes from an incomplete download. Try downloading a new file before a retry
Snowby123 said:
Usually the file is corrupted if the file comes from an incomplete download. Try downloading a new file before a retry
Click to expand...
Click to collapse
My other implied question was: Did I do everything right?
eliotargy said:
I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
Click to expand...
Click to collapse
search for lz4 on either xda or google.
( you need to unpack it)
eliotargy said:
I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
Click to expand...
Click to collapse
Hey friend, did you manage to accomplish this? Do you still trip the knox this way? I am just about to try it on a brand new Note 9, with no previous Samsung rooting experience.
Thanks
Why are you trying to patch? Please follow my guide for rooting the N9600.
christis said:
Hey friend, did you manage to accomplish this? Do you still trip the knox this way? I am just about to try it on a brand new Note 9, with no previous Samsung rooting experience.
Thanks
Click to expand...
Click to collapse
No luck. Also no response to my post.
zxzxzxzxzxzxzxzxzx said:
Why are you trying to patch? Please follow my guide for rooting the N9600.
Click to expand...
Click to collapse
Where is your guide?
Again, where is your guide that you speak of?
eliotargy said:
No luck. Also no response to my post.
Click to expand...
Click to collapse
I see. In the meantime I have managed to succeed. Rooted an N960F/D with patching the boot image. I know the N9600 is a different beast, but this is NOT a root guide!!!!!!!!.
For step #5, Winrar is no good. You have to use lz4, but is a pain. Personally I used a special version of 7z which includes lz4 codec and is easier and very usefull in all the steps. The link is
https://github.com/mcmilk/7-Zip-zstd/releases (choose x64 or x86 depending on your Windows version).
After this, I cannot remember the exact steps. As far as I can racall, I think I patched it with Magisk (follow the Magisk guide) first, and then I had to retrieve the patched image and compress it again (to .tar???) with the same version of 7z.
7z itself can fully replace Winrar in the whole process. In the initial firmware zip file extraction, in the extraction of the AP md5 file (no renaming necessary), in lz4 extraction of the boot file, and finally in the patched img file compression back to tar. One for all tool (use the 7zFM (file manager) shortcut and the Add or Extract buttons).
And to answer my own question: Finallly, in order to install the final patched boot image via Odin, the bootloader HAS to be unlocked, so Knox is tripped anyway. No problem for me though, since I managed to run SHealth, Gpay and Spay (the latter via the phone - watch (Gear S) connection though, not as a stand-alone). And I ensured that where I live, it is not going to affect my warranty as long as is a hardware problem.
CAUTION: That was for N960F/D and is NOT a root guide anyway.
christis said:
I see. In the meantime I have managed to succeed. Rooted an N960F/D with patching the boot image. I know the N9600 is a different beast, but this is NOT a root guide!!!!!!!!.
For step #5, Winrar is no good. You have to use lz4, but is a pain. Personally I used a special version of 7z which includes lz4 codec and is easier and very usefull in all the steps. The link is
https://github.com/mcmilk/7-Zip-zstd/releases (choose x64 or x86 depending on your Windows version).
After this, I cannot remember the exact steps. As far as I can racall, I think I patched it with Magisk (follow the Magisk guide) first, and then I had to retrieve the patched image and compress it again (to .tar???) with the same version of 7z.
7z itself can fully replace Winrar in the whole process. In the initial firmware zip file extraction, in the extraction of the AP md5 file (no renaming necessary), in lz4 extraction of the boot file, and finally in the patched img file compression back to tar. One for all tool (use the 7zFM (file manager) shortcut and the Add or Extract buttons).
And to answer my own question: Finallly, in order to install the final patched boot image via Odin, the bootloader HAS to be unlocked, so Knox is tripped anyway. No problem for me though, since I managed to run SHealth, Gpay and Spay (the latter via the phone - watch (Gear S) connection though, not as a stand-alone). And I ensured that where I live, it is not going to affect my warranty as long as is a hardware problem.
CAUTION: That was for N960F/D and is NOT a root guide anyway.
Click to expand...
Click to collapse
Mine falls at patching with Magisk. N9600.
Hello,
I'm trying to create my own Magisk module based on working modules and referencing the module instructions. Before getting too far, I wanted to make sure that the compression process worked correctly.
So, I downloaded a .zip module from the Magisk app (e.g. Wifi5ghzdisabler), moved .zip to my Ubuntu 20.04 PC using Google Drive, extracted the .zip (using Extract Here in Files context menu), compressed the module folder back to a .zip file (using Compress... in Files context menu) and then moved the new .zip back to the phone using Google Drive. No changes to any files were made. Then, I tried to install it from storage in the Magisk app (v23.0) on a OnePlus Nord N100 running Android 10, but I encountered the following error.
Installation Failed!
- Copying zip to temp directory
! Unzip error
Is this a compression issue or a permissions issue on the phone? I'm probably missing something simple. Thanks in advance.
DanHoliday said:
Hello,
I'm trying to create my own Magisk module based on working modules and referencing the module instructions. Before getting too far, I wanted to make sure that the compression process worked correctly.
So, I downloaded a .zip module from the Magisk app (e.g. Wifi5ghzdisabler), moved .zip to my Ubuntu 20.04 PC using Google Drive, extracted the .zip (using Extract Here in Files context menu), compressed the module folder back to a .zip file (using Compress... in Files context menu) and then moved the new .zip back to the phone using Google Drive. No changes to any files were made. Then, I tried to install it from storage in the Magisk app (v23.0) on a OnePlus Nord N100 running Android 10, but I encountered the following error.
Installation Failed!
- Copying zip to temp directory
! Unzip error
Is this a compression issue or a permissions issue on the phone? I'm probably missing something simple. Thanks in advance.
Click to expand...
Click to collapse
You should upload your zip.
Thanks for the reply.
I've attached the original WiFi5GhzDisabler-v1(1).zip module downloaded from inside the Magisk app.
I've also attached WiFi5GhzDisabler-v1(1)-re-compressed.zip after downloading, extracting and re-compressing the original module it as described in my first post. I didn't make any changes to the files/folders themselves. I did notice they are different sizes (6.1KB original versus 8.6KB re-compressed).
I'm trying to learn more about the correct compression process/tool for these modules. I searched the forum and found a thread with a similar issue. Basically, the OP shared a .zip file that didn't work and another member did something and uploaded a "fixed" version with minimal insight into how it was done.
[HELP] This zip is not a Magisk Module
I would assume there isn't anything wrong with the files in the original module since it was probably reviewed before it was hosted in the Magisk app. It is also strange that the .zip file downloaded from the github repos for various modules don't work for me either, but that may be a separate issue.
Any ideas? The instructions do not include how to compress the module.
Take a close look at the original zip again, and compare it to the one you recompressed. You've put all the files in a directory inside the zip, in comparison to putting them directly in the root of the zip...
There's your problem.
Didgeridoohan said:
You've put all the files in a directory inside the zip, in comparison to putting them directly in the root of the zip...
There's your problem.
Click to expand...
Click to collapse
You're exactly right. I was incorrectly zipping the module folder itself rather than the files inside the folder. As you correctly pointed out, this creates a folder inside the zip that adds an extra layer between the files and the root of the zip.
Wow, what a simple mistake. With your help, the recompressed module installs fine now. I was able to install my own module too!
Thank you so much for your help. My issue has been resolved.