Database Users

[Q] Status 7 errors (Nexus 10) after installing Lollipop.

Dear xda-developers (Sorry for my possible bad Englisch),
Can you help me with de following problem. After installing Lollipop my Nexus 10 was "death". By adb sideloader i was able to install Lollipop or the old KitKat but both with de following status 7 errors;
By installing the old KitKat;
Package expects build fingerprint of google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys of google/mantaray/manta:4.4/KRT160/907817:user/release-keys; this device has google/mantaray/manta:4.4.4/KTU84P/1227136:user/release-keys.
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
By installing the new Lollipop;
Creating parents of system/app/KoreanIME/KoreanIME.apk failed, error No space left on device
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
I have already done de following options in de recovery menu;
- Wipe data / Factory reset
- Wipe Cache partition
Can you help me solve this problem?

Bram van den Ham said:
Dear xda-developers (Sorry for my possible bad Englisch),
Can you help me with de following problem. After installing Lollipop my Nexus 10 was "death". By adb sideloader i was able to install Lollipop or the old KitKat but both with de following status 7 errors;
By installing the old KitKat;
Package expects build fingerprint of google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys of google/mantaray/manta:4.4/KRT160/907817:user/release-keys; this device has google/mantaray/manta:4.4.4/KTU84P/1227136:user/release-keys.
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
By installing the new Lollipop;
Creating parents of system/app/KoreanIME/KoreanIME.apk failed, error No space left on device
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
I have already done de following options in de recovery menu;
- Wipe data / Factory reset
- Wipe Cache partition
Can you help me solve this problem?
Click to expand...
Click to collapse
What rom were you trying to install?
1/ to install 4.3 remove from the updater-script the part checking the fingerprints.
2/ for lollipop, it doesnt format your current system partition but flash the image over it. Probably lollipop size + your former partition content exceded its size?
3/ you can use Google's factory image through fastboot to flash any android version.

Khaon said:
What rom were you trying to install?
1/ to install 4.3 remove from the updater-script the part checking the fingerprints.
2/ for lollipop, it doesnt format your current system partition but flash the image over it. Probably lollipop size + your former partition content exceded its size?
3/ you can use Google's factory image through fastboot to flash any android version.
Click to expand...
Click to collapse
Dear Khaon,
Is this the right instruction for option 3 to solve my problem?
http://forum.xda-developers.com/show...&postcount=134
The problem with this instruction is that i have installed Android SDK (Stand alone tools), but "flash-all.bat" is missing in the folder "sdk/platform-tools" (point 9).
Or do you have an better instruction?
Thanks for your respons.

Bram van den Ham said:
Dear Khaon,
Is this the right instruction for option 3 to solve my problem?
http://forum.xda-developers.com/show...&postcount=134
The problem with this instruction is that i have installed Android SDK (Stand alone tools), but "flash-all.bat" is missing in the folder "sdk/platform-tools" (point 9).
Or do you have an better instruction?
Thanks for your respons.
Click to expand...
Click to collapse
I am on my phone atm. But Google nexus factory images.
You will find an official link and all instructions to flash.
The bat is located into the archive you will download. So download, decompress '. Run flash all with device connected into bootloader.
Watch out data cache will be erased. Also the while device will be erased if you don't have unlocked your bootloader
Sent from my Xiaomi MI2s

Khaon said:
I am on my phone atm. But Google nexus factory images.
You will find an official link and all instructions to flash.
The bat is located into the archive you will download. So download, decompress '. Run flash all with device connected into bootloader.
Watch out data cache will be erased. Also the while device will be erased if you don't have unlocked your bootloader
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
Thanks Khaon,
Is now possible to run "flash-all.bat". But it stops with the following message in the prompt;
error: cannot load 'bootloader-manta-mantamf01.img'
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for device >
Can you help me also with this problem?

Bram van den Ham said:
Thanks Khaon,
Is now possible to run "flash-all.bat". But it stops with the following message in the prompt;
error: cannot load 'bootloader-manta-mantamf01.img'
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for device >
Can you help me also with this problem?
Click to expand...
Click to collapse
Hi Khaon,
The problem is solved! The files were not unzipped right!
Lollipop is running!
Thanks for helping me!

Bram van den Ham said:
Hi Khaon,
The problem is solved! The files were not unzipped right!
Lollipop is running!
Thanks for helping me!
Click to expand...
Click to collapse
Good!
Sent from my nexus 10

GT-i9505 "Update Signature Verification Failed" Restoring ADB Backup

RE: "Update Signature Verification Failed"
I've searched and read the other topics.. One person responded to someone else's question that there are "hundreds of answers on this", yet only 2-3 topics with the correct subject. None mention the topic that held the magic solution, and topics discuss other issues being the cause...
PROBLEM:
In Android System Recovery mode on KOT49H...... and attempting to recover an ".ab" backup made via command prompt on the computer with ADB from 2012 I used with a Sony Tablet S...
Using the command prompt, the restore completes after only a minute or so, and then the phone thinks the restore was successful... Tried cmd command prompt method both via Android and Recovery methods.
Size is 416 MB (436,330,412 Bytes) or 426 MB in Windows 8. Device has lots of free space - over 2GB.
I've also tried Sideloading the restore in Recovery mode.
C:\Users\User\AppData\Local\Android\android-sdk\platform-tools>adb sideload Samsung.S4.v442.2015.05.01.Backup.ab
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
C:\Users\User\AppData\Local\Android\android-sdk\platform-tools>adb restore Samsung.S4.v442.2015.05.01.Backup.ab
Now unlock your device and confirm the restore operation.
< then nothing! >
Click to expand...
Click to collapse
The backup has resided on my PC since done via ADB the whole time, plus attempted recovery via 2 x USB cables. 1 x Premium USB 2M cable plus 1 x Cheap 1M USB cable. hmmm...
??? Ideas? The .ab file backup is from 8 months ago on the SAME OS version and system.
Help! Can anyone share their .ab backup from a Samsung Galaxy S4 GT-i9505??? e.g. I9505XXUGNH6? (OPS?)
Thank you!

Why is this in dev forum?

And weirdly trending?
Sent from my GT-I9505 using Tapatalk

Update Signature Verification Failed | Restoring ADB Backup on v4.4.2 GT-i9505

RE: "Update Signature Verification Failed"
I've searched and read the other topics.. One person responded to someone else's question that there are "hundreds of answers on this", yet only 2-3 topics with a related subject and posts. None that say they found the solution mention the topic that held the magic solution, and topics discuss other issues being the cause which don't match my scenario...
PROBLEM:
In Android System Recovery mode on KOT49H...... and attempting to recover an ".ab" backup made via command prompt on the computer with ADB from 2012 I used with a Sony Tablet S...
Using the command prompt, the restore completes after only a minute or so, and then the phone thinks the restore was successful... Tried cmd command prompt method both via Android and Recovery.
Size is 416 MB (436,330,412 Bytes) or 426 MB in Windows. Device has lots of free space - over 2GB.
I've tried Sideloading the restore in Recovery mode.
C:\Users\User\AppData\Local\Android\android-sdk\platform-tools>adb sideload Samsung.S4.v442.2015.05.01.Backup.ab
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
C:\Users\User\AppData\Local\Android\android-sdk\platform-tools>adb restore Samsung.S4.v442.2015.05.01.Backup.ab
Now unlock your device and confirm the restore operation.
< click button on device to continue >
< then nothing! >
Click to expand...
Click to collapse
The backup has resided on my PC since it was created via ADB. Is it a USB-related problem? I have attempted recovery via 2 x USB cables: 1 x Premium USB 2M cable plus 1 x Cheap 1M USB cable. hmmm...
??? Ideas? The '.ab' file backup is from 8 months ago on the SAME OS version and system. It is a stock ROM.
Help! Can anyone share their '.ab' backup from a Samsung Galaxy S4 GT-i9505??? e.g. I9505XXUGNH6? (OPS?)
Thank you!

Normally you can just flash the backup with a custom recovery like TWRP.
I don't have any experience in making and restoring backups with the method you used. You could try to see if you can flash it with TWRP.
Why don't you just flash a stock rom with Odin? Are there files in the backup you need? If so, then you can just extract the files you need on your pc.
e.g. http://forum.xda-developers.com/showthread.php?t=2011811

Problem flashig new roms: TWRP unable to mount Data/media/twrp/.twrps

Hello everybody!
To defeat planned obsolescence of my Zenfone 3 (ZE520KL) I've decided to root it and install an alternative ROM.
With much difficulty at the end I achive root it but I've a problem flashing roms.
- Unloked OK
- To flash and fix TWRP I used Magistik (without it TWRP starded only when phone was connected to pc)
Now Root Checker says my phone is rooter, Magistik is correctly installed and TWRP seems ok. So I felt in 90% of my challenge!
But…
When I try to flash a ROM in TWRP lots of red line appear…
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details…
...done
Unable to mount storage
Successfully decrypted with default password.
Updating partition details
…..done
Unable to mount storage
Failed to mount '/data? (Invalid Argumetn)
Full SELinux support is present.
Unable to mount /data/media/twrp/.twrps
MTP Enabled
Installing zip file '/external_sd/PixelExperience_zenfone3_-9.0-20190823-1844-UNOFFICIAL.zip'
Checking for MD5 file…
Skipping MD5 check: no MD5 file found
Warnink: No file_context
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
Error installing zip file '/external_sd/PixelExperience_zenfone3_-9.0-20190823-1844-UNOFFICIAL.zip'
Updating partition details…
...done
Unable to mount storage
Click to expand...
Click to collapse
The same thing happens with Lineage OS
In addition if I try to save the log I can't find it in the storage of the phone (really I don't know where it should be).
Maybe the Recovery [treble] proposed by Giovix92 can solve my problem?
Any other suggestion?
Thanks a lot to everybody!

twin-s said:
Hello everybody!
To defeat planned obsolescence of my Zenfone 3 (ZE520KL) I've decided to root it and install an alternative ROM.
With much difficulty at the end I achive root it but I've a problem flashing roms.
- Unloked OK
- To flash and fix TWRP I used Magistik (without it TWRP starded only when phone was connected to pc)
Now Root Checker says my phone is rooter, Magistik is correctly installed and TWRP seems ok. So I felt in 90% of my challenge!
But…
When I try to flash a ROM in TWRP lots of red line appear…
The same thing happens with Lineage OS
In addition if I try to save the log I can't find it in the storage of the phone (really I don't know where it should be).
Maybe the Recovery [treble] proposed by Giovix92 can solve my problem?
Any other suggestion?
Thanks a lot to everybody!
Click to expand...
Click to collapse
Might be due to encrypted partition.
Try
Code:
fastboot format userdata
in fastboot mode.
This will, as you might expect, wipe all your data. So be sure to backup first.
Also, the flashing error
Code:
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
is from incompatible TWRP and ROM version. Are you using the latest TWRP?
As a last resort for the flashing error, try this https://forum.xda-developers.com/showthread.php?t=2522762

vaanish said:
Might be due to encrypted partition.
Try
Code:
fastboot format userdata
in fastboot mode.
This will, as you might expect, wipe all your data. So be sure to backup first.
Also, the flashing error
Code:
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
is from incompatible TWRP and ROM version. Are you using the latest TWRP?
As a last resort for the flashing error, try this https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Thank you vaanish!
I solved flashing an older versione of TWRP. The 3.3.1.
Now all is right!

Unable to sideload LineageOS 19.1 to my LG G6

Hi! I'm currently trying to revive an LG G6 that I had lying around and was pleasantly suprised that there are recent builds of LineageOS available for the device.
Steps I took:
Download latest build (lineage-19.1-20230529-nightly-h870-signed.zip), boot.img and recovery.img
Installed boot image via `fastboot flash boot boot.img`
Installed recovery via `fastboot flash recovery recovery.img`
Reboot via `fastboot reboot`
Boot into recovery (via Vol Down + Power, Release Power, press power againg)
In Lineage Recovery, choose Apply update and Apply from ADB
Sideload image via `adb sideload .\lineage-19.1-20230529-nightly-h870-signed.zip`
Upload starts but stops at ~47%
Error message shown on phone:
Code:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 39,4 s (result 0):
Installing update...
Comparing TZ versions:
Max TZ version: TZ.BF.4.0.1-1865684
assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1"
E:Error in /sideload/package.zip (status 1)
Does anybody have an idea what could be the problem here? I had an older version of LineageOS installed on the device (bootloader is still unlocked), but I completely wiped the device prior to trying to install the latest version.
Thanks!

Hackysack said:
Hi! I'm currently trying to revive an LG G6 that I had lying around and was pleasantly suprised that there are recent builds of LineageOS available for the device.
Steps I took:
Download latest build (lineage-19.1-20230529-nightly-h870-signed.zip), boot.img and recovery.img
Installed boot image via `fastboot flash boot boot.img`
Installed recovery via `fastboot flash recovery recovery.img`
Reboot via `fastboot reboot`
Boot into recovery (via Vol Down + Power, Release Power, press power againg)
In Lineage Recovery, choose Apply update and Apply from ADB
Sideload image via `adb sideload .\lineage-19.1-20230529-nightly-h870-signed.zip`
Upload starts but stops at ~47%
Error message shown on phone:
Code:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 39,4 s (result 0):
Installing update...
Comparing TZ versions:
Max TZ version: TZ.BF.4.0.1-1865684
assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1"
E:Error in /sideload/package.zip (status 1)
Does anybody have an idea what could be the problem here? I had an older version of LineageOS installed on the device (bootloader is still unlocked), but I completely wiped the device prior to trying to install the latest version.
Thanks!
Click to expand...
Click to collapse
Look's like someone else had the same exact problem: link, and the corresponding solution: link. Hope this helps!
(I found this solution by searching: "assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1" ")

ethical_haquer said:
Look's like someone else had the same exact problem: link, and the corresponding solution: link. Hope this helps!
(I found this solution by searching: "assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1" ")
Click to expand...
Click to collapse
Hi,
thanks for you reply.
I'm not 100% sure about the terminology: Does bootstack mean kdz file?
If that is the case, I already tried to apply it to the device, but neither LGUP or LGFlashTool did work for me... On top there are so many versions floating around that I'm unsure which of the flashing tools is the right one to use on Windows 11. Do you happen to know where I should look for the latest version of one of these tools? (Besides googling, which as mentioned I already tried )

Hackysack said:
Hi,
thanks for you reply.
I'm not 100% sure about the terminology: Does bootstack mean kdz file?
If that is the case, I already tried to apply it to the device, but neither LGUP or LGFlashTool did work for me... On top there are so many versions floating around that I'm unsure which of the flashing tools is the right one to use on Windows 11. Do you happen to know where I should look for the latest version of one of these tools? (Besides googling, which as mentioned I already tried )
Click to expand...
Click to collapse
I honestly don't know, as I only have a Samsung. If you search for the same thing I did in that thread I linked to there were a few more results, you could check those: link.