i need help. heidmall can't open large files for example my system.img (2367450528 byte)
I recompile heidmail with -D_FILE_OFFSET_BITS=64
now it can open my system.img
but i got new error:
ERROR: Failed to confirm end of file transfer sequence!
I know that there is patch for this error.
do anybody have this patch?
I downloaded latest sources but still have this error
I don't have 64 bit pc to flash...
please help me
Related
So, I'm unable to unpack the boot.img successfully. Tried alot of tools, either it would give me an error or it would unpack but the zImage would be empty and the ramdisk would be corrupted. It would report a page size of over 530000 and the address would be wrong. My phone is a G531F.
Any help?
I'm taking my first stab at developing and have successfully built AOSP from source (aosp_angler-userdebug). The boot.img and system.img flash fine over fastboot, however, the .zip created from:
Code:
$ make updatepackage
passes an error in TWRP when I try to flash it. Something to the effect of:
Code:
Installing zip from '/path/to/file.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Invalid zip file formHey guys, I've looked around the forum and have done much Google-ing to try and resolve this.
at!
Updating partition details...
...done
After doing some Google-ing and re-reading the AOSP instructions many times, I guessed that my META-INF folder was missing since I couldn't find it anywhere in my source tree nor output directory. So, I tried:
Code:
$ make dist
then
$ ./build/tools/releasetools/ota_from_target_files output_path/target_files.zip
That did produce an ota_update.zip, but when I tried to flash in TWPR it yielded the same error. This is with N4F260 vendor and android-7.1.1_r14 source branch. Any suggestions would be greatly appreciated!
Hi Folks,
I am new to rooting and struggling with a problem. I have an old zenfone 5(ASUS_T00J) model. I am using custom rom BlurOS found in the below thread:
https://forum.xda-developers.com/zenfone-5/development/rom-bluros-version-1-0-zenfone-5-t3619058
I am trying to flash Magisk from TWRP recovery but it's failing with below error:
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Invalid Block device on '/dev/block/zram0
none
swap
defaults
zramsize=67108864
', 'swap', 36
Updating partition details..
...done
Full SELinux support is present.
MTP Enabled
Installing '/sdcard/Download/Magisk-v20.4(20400).zip'..
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
**********************
Magisk 20.4 Installer
**********************
- Mounting /system
- Target Image: /dev/block/by-name/boot
- Device platform: x86
- Constructing environment
- Adding addon.d survival script
E: Error executing updater binary in zip '/sdcard/download/Magisk-v20.4(20400).zip'[/QUOTE]
Error flashing zip '/sdcard/download/Magisk-v20.4(20400).zip'
Updating partition details...
...done
Updatrer Scripts are in below Google Drive Location:
https://drive.google.com/file/d/1SdtXdgB-iCB1X5PL3OCsZLrcUT6WlRzX/view?usp=sharing (Updater Script)
https://drive.google.com/file/d/1X2lupRfMUj-n5pRx2c0h0NQHUvfOXJAP/view?usp=sharing (Updater Binary)
Steps followed by me:
1. Installed latest Magisk manager from GitHub
2. Downloaded the latest zip file prompted by Manager
3. Reboot in TWRP recovery
4. Flashed the newly downloaded zip file
Appologies in advance if this is not the right forum or I have violated any guidelines. Let me know if you need any more details from my side. Thanks in advance.
Update
The issue still remains. Tried to find solutions online. Below methods were suggested. Since, I am new to this, might have tried something silly in the process.
Method 1:
Flash the Rom boot image via TWRP
Result: Did not prompt to provide any partition but Failed with error 'No Partition selected for flashing'. Updated the TWRP to 3.2.3 and tried the same thing again. This time prompted for a partition but no option was available that I could provide there and failed with the same error.
Method 2:
Patching the Boot image of my ROM through magisk patch
Result: Extracted the boot image for BlurOS Custom rom and tried to patch it through magisk Manager. Installation failed with 'Unable to repack boot image'.
Since I updated the TWRP, tried to flash the magisk zip file hoping for some other error (at least). It failed with below error message:
Installing zip file '/sdcard/Download/Magisk-v20.4.zip'
Checking for digest file...
Skipping Digest check: No digest file found
*************************
Magisk 20.4 Installer
*************************
- Mounting /system
! Unable to detect target image
- Unmounting partitions
Updater process ends with error: 1
Error Installing zip file
Updating partition details...
... done
Kindly let me know if you guys have any pointers. Any leads will be appreciated.
Magisk is unable to patch x86 boot.img's, so you have to use "android image kitchen"
Magisk patches Ramdisk file so you have to do:
move x86 ramdisk to ARM boot.img
Patch it via magisk
move patched ramdisk back to x86 boot.img
You can try boot.img's that I made for RR and Lineage in my thread. They are pre-patched with magisk 20.4
Anyways, is BlurOS better than lineage or RR ?
Hi all,
Is there a tool that can unpack system.img for the Pixel 4 (that actually works..) ?
What I want is to create a system.img that will have the following change:
Replace the below apex zip file:
`/system/apex/com.android.runtime.release.apex`
to an extracted version of it:
`/system/apex/com.android.runtime.release`
I've tried most of the online tools and tutorials with no luck.
So I unzip the ` flame-qd1a.190821.007` factory image, and then unzip the `image-flame-qd1a.190821.007` within in.
This gives me many .img files, including system.img, system_other.img, and super_empty.img.
I guess in some phones super.img had included the system.img, but that's not the case with `flame`.
imjtool can extract the `system.img` using:
Code:
imjtool system.img extract
With the below warning:
Warning: system.img is likely truncated or still compressed
Sparse image v1.0 detected, 196053 blocks of 4096 bytes
196053 blocks of 4096 bytes compressed into 15 chunks (1% compressed)
Click to expand...
Click to collapse
Then `extract/image.img` cannot be further recognized by the tool:
Code:
imjtool extracted/image.img
extracted/image.img is not a recognized image. Sorry
Click to expand...
Click to collapse
I've also tried simg2img to convert a sparse android img to a normal one,
but then mounting failed, in both Linux and mac.
Paschalis said:
Hi all,
Is there a tool that can unpack system.img for the Pixel 4 (that actually works..) ?
What I want is to create a system.img that will have the following change:
Replace the below apex zip file:
`/system/apex/com.android.runtime.release.apex`
to an extracted version of it:
`/system/apex/com.android.runtime.release`
I've tried most of the online tools and tutorials with no luck.
So I unzip the ` flame-qd1a.190821.007` factory image, and then unzip the `image-flame-qd1a.190821.007` within in.
This gives me many .img files, including system.img, system_other.img, and super_empty.img.
I guess in some phones super.img had included the system.img, but that's not the case with `flame`.
imjtool can extract the `system.img` using:
Code:
imjtool system.img extract
With the below warning:
Then `extract/image.img` cannot be further recognized by the tool:
Code:
imjtool extracted/image.img
I've also tried simg2img to convert a sparse android img to a normal one,
but then mounting failed, in both Linux and mac.
Click to expand...
Click to collapse
I use SuperR Kitchen
It unpacks everything. You must then use Apktool or third party software (ticklemyandroid) to decompile and recompile apks for editing. I don't have a way to edit a .apex file.
Here is the file in question. Just rename it by taking off the .zip. only way I could upload it.
https://www.androidfilehost.com/?fid=8889791610682898672
The full Android SDK. But it's definitely not a beginner friendly process. If you have to ask how to do it then you probably shouldn't try it until you learn more. ?
Hi,
I am trying to install the latest Lineage version on my Samsung Nexus 10 via twrp, but so far it always immediately fails with
Error E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-17.1-20220318-UNOFFICIAL-manta.zip'
I tried wiping the entire system, cache and all and I tried both the adb push method and sideloading adb and they all produce the exact same error.
This is my first time doing this type of thing, so any help would be greatly appreciated.
P.S. I am currently running Windows 10, but could boot into a Linux Live Medium if that would be useful.
Edit: I was following this tutorial for the setup.
I'm facing exactly the same issue here with the installation of `lineage-17.1-20220919-UNOFFICIAL-manta.zip` file.
I'm currently on the latest original Google Android ROM flashed with `image-mantaray-lmy49j.zip` and want to update the system to the lineage OS as above.
I'm using TWRP v3.6.2_9.
What I did:
- uploaded `lineage-17.1-20220919-UNOFFICIAL-manta.zip` to `/sdcard` location;
- wiped out `dalvik-cache` and `cache` partitions;
- tried to install `lineage-17.1-20220919-UNOFFICIAL-manta.zip` as a single installation file;
Got this error. Here is an output from recovery.log:
Code:
Installing zip file '/sdcard/lineage-17.1-20220919-UNOFFICIAL-manta.zip'
Unmounting System...
I:Update binary zip
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
No path given to file labeling backend
selinux_android_file_context: Error getting file context handle (No such file or directory)
Warning: No file_contextsTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keysTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keys
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 2 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 4 args
Backup/restore is not possible. Partition is probably empty
Patching system image unconditionally...
performing update
blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/4dd6bf24fbba9cc76c352f5c4cfaed0074be0244
535756800 bytes free on /cache (0 needed)
/cache/recovery/last_command doesn't exist.
erasing 3367 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,225950,228864,229947,230400]
new data receiver is still available after executing all commands.
Patching system image unconditionally...script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/sdcard/lineage-17.1-20220919-UNOFFICIAL-manta.zip'
Does anyone have any clue on what could be wrong here and why it fails?
unpack zip remove lines, then pack zip and try again. voilla
or utube eroor 7
I'd the same problem with twrp but does did successfully for version 16 installation. I tried the above listed way but failed again. Same thing happened even I unchecked the system in twrp before flashing again. Need expert to help fix the issue. Appreciate in advanced!
Cpluo said:
I'd the same problem with twrp but does did successfully for version 16 installation. I tried the above listed way but failed again. Same thing happened even I unchecked the system in twrp before flashing again. Need expert to help fix the issue. Appreciate in advanced!
Click to expand...
Click to collapse
Not enough space on /system. Resize the partition. After 17.1 is running for me. https://www.hovatek.com/forum/thread-32750.html
Thanks a lot Daniel! I will try your way.