I have .ZIP files appearing on my Android 11 phone on their own. I don't know why they're there, and I don't know where they're coming from. Their located under Google, Download cache. 24 files named as follows: soda-en-US-v1001-1.zip All file names are the same except for the number at the end. All files are 50.05mb. If I try to open them, it says "unable to open archive. File is either corrupt or an unsupported format." I didn't create these files, nor have I downloaded anything. Why are these files being created on their own?

I am running Android 12 on a Realme 8 phone. Recently, I've downloaded some Google Takeout backup files I created at the Google Takeout site , to my Android device. Here are some screenshots. However, as the attached images demonstrate, I was unable to open the files on my Android device. How can I open them on Android directly?

I have a backup of my old phone in my computer, in a folder called phone_backup it contains the usual folders: - Airdroid - Alarms - Android - Audiobooks - AuthenticatorPlus - Books - DCIM - Documents - doubleTwist - Download - MEGA - Movies - Music - Neobackup - Notifications - Pictures - Podcasts I have zipped the contents of phone_backup and transferred to the sdcard of my new phone. If I open, in Windows, phone_backup or phone_backup.zip and check the Download folder I see the same I have on my old phone, however, when I do unzip phone_backup.zip everything seems to work until I get the error unzip: couldn't create file Download/Videos: Is a directory And if I do find Download/ -maxdepth 1 -type d I get: - Download/ - Download/Videos - Download/WhatsApp - Download/Airdroid - Download/Alarms - Download/Android - Download/PowerTube For some reason it's decompressing the root inside the Downloads folder?

redwood:/sdcard $ ls -lah Videos/ Download/Videos/
Download/Videos:
total 3.0K
drwxrws--- 2 u0_a402 media_rw 3.3K 2023-12-01 21:50 work

Videos:
total 3.0K
drwxrws--- 2 u0_a402 media_rw 3.3K 2023-12-02 09:02 work

same content too. Why could this happen??

I have a J7 elte. When I want to sideload a zip file with adb from the phone's default boot loader the bootloader raises error Signature Verification Failed whole-file. How can I disable this verification in my phone's default bootloader?

I created the image with the following commands

dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard/modem.img
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/aboot.img

Now, I want to create a flashable zip to flash these images to another copy of the device. 1) Do I need to format the partition before I write the raw image in the first place? 2) Is this script okay if I assume no formatting is needed?

ui_print("Updating modem.img ...");
   write_raw_image("aboot.img", "/dev/block/mmcblk0p5");
   write_raw_image("modem.img", "/dev/block/mmcblk0p1");
   ui_print("Finished!");
   ui_print();

If it needs formating, I use the Partition Table app to identify the partitions. It shows for /dev/block/mmcblk0p1 mount point and filesystem type ("vfat") but for /dev/block/mmcblk0p5 this info is absent. 3) How do I know the filesystem type "EMMC" or "MTD" or what?

Is there a way to password protect a zip file with 7-zip on a pc, then unzip the file on android (while requiring the password), and essentially use it on either pc or android? I tried with es explorer, as well as fz explorer, and I'm not seeing any of the needed functionality. Any help/suggestions much appreciated.

In PC you can choose more than one separate zip files and extract to "zipname" folder all by selecting at once, how can I do the same in Android. I've tried ES file explorer, Z Archiver etc but they all seem to work only for multipart zip files and not for multiple separate zips.

so yes: today i was trying to test my own zip (yes, twrp) but when i tried it thrown me error

process ended with ERROR:255

installing zip file '/emmc/recovery.zip'

is it because i messed up that zip, i dont have many space on phone or another thing? my device is lg l65 d280n and zip is there : https://drive.google.com/file/d/1GbHeXDbs1Dh9G-FPw82hNJY9kc03hOBb/view?usp=drivesdk . PS: i know that here is a few similar questions but no, i dont have that second error "createtarfork()" but yes - i have cyanogenmod 14 which is nearby lineage, which is buggy as i heard.

I was zipping a file on the memory card, but the process of zipping hangs, then the whole Android phone hangs, and I had to remove the battery. Now the memory card is not visible, I tried it on any other phone and there is the same problem.

My question is related to the repackaging of a mobile app. This app uses v1 signing scheme and I did the following: I fetched the apk file from the playstore using adb and I signed with my keystore using apksigner. Now, when I launch this app on my smartphone, it is showing the following exception. I took the original apk, I change the format to *.zip and unzipped it, and then again, converted back to apk and I applied zipalign on the apk. The apk gets successfully installed on the smartphone but when I launch this app, I am getting the following exception. In this scenario, I didn't modify any file. In the past, I have done this same process for few app's apk and the app is running successfully. If you observe the above two exception's image, the 1st three lines are same. My doubt is: - Irrespective of the signature change, we are getting the same exception (atleast the 1st three lines). What can be the reasons regarding the same? (Also, I have used the zipalign for the proper alignment) - Which type of framework this app is using such that even without changing the source code, the app is getting crashed? Any help/inputs regarding this domain is highly appreciated.

I have recently started running Android-x86 version 6.0-RC1 on my iMac, and I am considering making it on of my several daily drivers. There is one major issue however that is casting some doubt: I cannot seem to find a way to install flashable zip files. I have looked into a custom recovery, however apparently the directory structure of Android-x86 is too different from that of its mobile-device counterpart to run or even install one directly. I have attempted to use Chainfire's FlashFire, however it unsurprisingly does not work for similar reasons to the last method. I've read on a very short conversation in the XDA-Developers forum discussing this topic that a recovery would be relatively unnecessary because "you could simply use a lightweight Linux distro as a recovery". I am assuming from the wording that you would do this by booting a small Linux distro on the same machine, mounting the main image for Android-x86, extracting the flashable zip and running the install script contained within, however I am entirely unsure as to whether or not this method would work in practice, as I cannot find any more info on it. I need the ability to flash a flashable zip file as it is the only way as of current aside from using a custom recovery to install the Xposed framework on android, upon which I rely heavily for everything from personal conveniences to more manually configurable security functions to ease of development. Given Android-x86's inherent compatibility with virtually anything compiled to run on an Intel Atom or Celeron based android device the lack of Xposed is the one factor stopping me from being able to attempt custom ROM development, as well as starting to port several already under development projects that have been until now exclusive to BSD/Debian distros over to rooted Intel based android devices.
UPDATE: I've managed to mount the Android-x86 fs from a live GParted CD, and chroot to it, but when running flash-script.sh it starts the installer, and output the following error log: ****************************** Xposed framework installer zip ****************************** -Mounting /system and /vendor read-write /tmp/META-INF/com/google/android/flash-script.sh: can't create /dev/null: No such file or directory /tmp/META-INF/com/google/android/flash-script.sh: can't create /dev/null: No such file or directory /tmp/META-INF/com/google/android/flash-script.sh: mount: not found /tmp/META-INF/com/google/android/flash-script.sh: can't create /dev/null: No such file or directory -Checking Environment /tmp/META-INF/com/google/android/flash-script.sh: head: not found /tmp/META-INF/com/google/android/flash-script.sh: sed: not found /tmp/META-INF/com/google/android/flash-script.sh: cut: not found *Continues till line 121* Xposed version: ! Wrong platform: arm ! This file is for: ! Please download the correct package ! for your platform/ROM Now I'm assuming the reason this happened is that the Linux version I'm using is too lightweight and doesn't include the required programmes, however that does not explain the fact that the error log reports the system as ARM and claims the x86 version is incorrect for my platform given that I'm running a copy of Android-x86, so if anyone has insight, please supply!

I've been trying to open a .zip file on my Android device, and whenever I try it tells me the same thing over and over again: > Extract exception, please check files What does this mean? I went through all my files, and then when I try to extract the .zip file again, it gives me an empty folder and says that same message. Can someone please help? What am I doing wrong?

TWRP provides an option on boot for "Zip signature verification". Is that option part of Android ROM packaging and would LineageOS support it? For me, that option does Checking for Digest file... Skipping Digest check: no Digest file found verifying zip signature... Zip signature verification failed! Error installing zip file '/data/lineageos_updates/lineage-nightly-n1awifi-signed.zip' Updating partition details... ...done I ask this because this ROM was download with the OTA update from LineageOS, and when it failed I download a new ROM from the website and it also failed.

I bought a new Lyf ls-5010 on 15 Aug 2016 . in it all setting of picture camera browser are set to internal 4gb it shows no space while capture photo or download something. No I inserted a 32 GB Samsung sd card . but no options to move data from internal memory to SD card. And to change default storage internal to SD card. I bought a 32gb card it only show 28.80 GB space.

According to this Blog post , Google has added a Security Metadata on top of an APK to verify that it was originally distributed by Google Play. More specifically it adds APK Signing Block to the APK file. I have some questions regarding this: (1) How did Google insert this the metadata into APK signing block of the APK and how it verifies that metadata on the phone (technically)? I guess it is possible to create custom content in this signing block? Let's say I want to distribute some APK privately in my company, when the user installs that APK then I can figure out if the APK belongs to our company or not, just like Google did with their apps in Play Store. (2) If all developers use App Signing by Google Play , then does the mentioned security metadata above become unnecessary? Because Google can just simply verify the certificate inside each APK instead. My apologies for the shallow understanding. Any comments are highly appreciated!

After spending a few hours on annoying file management apps and the various archival apps. I can't find a quick way to do this. Most of these are built like users are supposed to use them for the PC. The quick PC extraction of Right Click "Extract All / Here" is pipe dream on android. How can i go about to do this? Can I find or force an application to extract everything it finds at a certain location and extract it where it is. I looked for some solution that automatically extracts archives upon download, but thats convoluted even on PC (but at least doable - do a command line and if you want trigger it by a folder monitor change). Couldn't make any headway on android for sure. How would you go about easing your time with archives on android. Dumping them all in one place is fine by me so long as I don't have to go through annoying managers for every single archive i get.

TWRP is fine. I have lineage-15.1-20180415-UNOFFICIAL-cedric.zip in the Downloads folder on the 'phone. On attempting to flash this, TWRP fails with: "Updater process ended with ERROR: 255". Advice elsewhere suggested unzipping the package, then removing the first 2 lines of file at META_INF>Com>Google>Android>UpdaterScript. These refer to the 'Cedric' device name - but I have no real idea what they mean..... I did this, but as I'm on a mac, could not follow the instructions relating to re-creating the archive as they were Windows specific ('Add to rar' was suggested). So I tried straight zip archiving. Attempting to flash the archive thus created, TWRP now fails with : "Invalid zip file format!". Would be grateful for advice on how to create the appropriate file format using a mac. I have an app called 'Keka', which offers as options 7z, Zip, Tar, Gzip, Bzip2. Are any of these appropriate? Thank you!

Please try to understand this question carefully before marking this as duplicate. Do the Android OS has inbuilt support for .zip and .rar files ? I am not asking about any third-party software, because I know that there is a difference between OS support and software support. I am asking this because I have found bootanimation.zip and shutdownanimation.zip files inside /system/media/ folder.

In the custom recovery TWRP, what does the option "zip file signature verification" do? How do I know if it should be checked when installing something?

Hello There Everyone!, To clarify the title... Is there a way to change, modify, convert, etc... an App Installer (.apk) to a Flashable Installer (.zip). I'm not referring to just creating a zip to simply copy the apk file to its desired directory but, to either install the app as a new app and/or upgrade an existing one in the same/similar fashion as would an apk itself would be installed. I tried to search around and the results aren't specific to what I'm asking and reflects the copying of the apk file rather than the installing of it. I hope that I had explained this okay via text... :-) Thank you very much for your time and understanding with this question! ~Ibuprophen