Develop Bugs

Zip signature error - only when flashing kernels

I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?

barrack1 said:
I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?
Click to expand...
Click to collapse
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything

presetz said:
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything
Click to expand...
Click to collapse
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.

barrack1 said:
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.
Click to expand...
Click to collapse
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO

presetz said:
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO
Click to expand...
Click to collapse
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP

barrack1 said:
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP
Click to expand...
Click to collapse
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?

presetz said:
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?
Click to expand...
Click to collapse
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.

barrack1 said:
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.
Click to expand...
Click to collapse
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...

presetz said:
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...
Click to expand...
Click to collapse
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).

barrack1 said:
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).
Click to expand...
Click to collapse
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.

presetz said:
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.
Click to expand...
Click to collapse
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?

barrack1 said:
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?
Click to expand...
Click to collapse
sorry my mistaken, thought that my problem was the same with yours with no changed kernel after flashin custom kernel while back at cm12
and no, i didnt need to flashed boot.img first before custom kernel ever since cm12.1 clean install

Nexus 7 Only boots on 5.0 or Higher - Lower firmware than that bootloops -flo

So for installing older ROMs I wanted to flash the jellybean factory image and "update" it using the a rom but when I tried it after unlocking the bootloader, I installed 4.3, 4.4, and 4.4.4 none of which worked. So I was wondering what is wrong with the device. (By not working I mean not even bootlooping just on the "Google" screen). Then after a 100 tries I got an idea to install 5.0 and it worked, phew! But still I am quite disappointed I can't install older firmwares. I did get this device like 3 days ago, so it might have a different hardware revision or something, I also noticed it has something called "secure boot" which didn't sound good to me. Hopefully you guys can clarify what is wrong. Thanks!

Did you flash the bootloader image as well as the boot and system.img? It's different between 4.x and 5.x.
If you did then I don't know.. run fastboot format cache after flashing the images it can fix things sometimes. Nothing more should be needed. Secure boot has nothing to do with it. That's on mine bought in '13.
Why would you want to flash JB to "update it using the a rom?" Not really clear.
Do you mean take all the ots? That's probably a bad idea just flash the latest image. If you mean you want to flash a custom rom just flash twrp then flash whatever rom you want doesn't matter what was previously on it but you'll need the right bootloader.
If you just want to check out all the versions you should be able to easily with just the bootloader, boot and system images from the factory image zip. Unless it's something to do with that new batch that popped up earlier this year (I think?).

Trying Something Different
Ok I reinstalled latest 6.0, now I see another problem after flashing custom recovery (TWRP) I see mounting errors for example " E:Unable to mount '/system' " even though I can still boot into android fine. (I can't mount anything, I was hoping to at least have a custom recovery.) Anyway hope you can help me out, I am probably doing a dumb mistake.

Fixed!
googleiscoul said:
Ok I reinstalled latest 6.0, now I see another problem after flashing custom recovery (TWRP) I see mounting errors for example " E:Unable to mount '/system' " even though I can still boot into android fine. (I can't mount anything, I was hoping to at least have a custom recovery.) Anyway hope you can help me out, I am probably doing a dumb mistake.
Click to expand...
Click to collapse
Ok cool fixed my recovery problem with this post - http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562

Nexus 5x in google logo. Cannot flash factory image

I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.

eNVy said:
I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.
Click to expand...
Click to collapse
post a screenshot from cmd here to see the error you get from fastboot...

kopfik said:
post a screenshot from cmd here to see the error you get from fastboot...
Click to expand...
Click to collapse
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.

eNVy said:
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.
Click to expand...
Click to collapse
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)

kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Shouldn't you be using the latest twrp 2.8.7.2? Ive had issues flashing roms without using the latest version. You could also have issues with older versions of twrp and encryption. Id suggest wiping data from twrp and then flashing the factory image from bootloader.
Sent from my Nexus 5X using Tapatalk

Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp

I think to be able to really do anything you need to get into bootloader and have fastboot recognize the device. Make sure the files from 6.01 are all correct and you're flashing in the right order. Follow the guide item #8 http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 If you can get the system.img and vendor.img flashed and then lock the bootloader it will wipe everything to factory, internal storage included. If you do that you must have stock recovery.img flashed as well. If downloading system.img hangs reboot and try it again.

kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Sorry, I was using v.2.8.7.2.

mnehring said:
Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp
Click to expand...
Click to collapse
I got it to work. I just had to change the USB port.
Why don't you try a different USB port or a different cable. Or even try on a different computer.

TWRP stuck on splash screen for a miute then reboots back to the TWRP splash screen

No matter how many resets I just can't boot into my recovery or the OS. If I try to reboot the system all that happens is the TWRP splash screen pops up, hangs there for a while, reboots to the splash screen again and repeats. Is this a brick? The most I can do is get into fastboot mode. Please, any advice would be very much appreciated. I feel like a total dipstick. The ROM I'm on is Resurrection Remix official N and the TWRP version is 3.1.1-0. This combo was never an issue before.

showofdeth said:
No matter how many resets I just can't boot into my recovery or the OS. If I try to reboot the system all that happens is the TWRP splash screen pops up, hangs there for a while, reboots to the splash screen again and repeats. Is this a brick? The most I can do is get into fastboot mode. Please, any advice would be very much appreciated. I feel like a total dipstick. The ROM I'm on is Resurrection Remix official N and the TWRP version is 3.1.1-0. This combo was never an issue before.
Click to expand...
Click to collapse
Use the unbrick guide method 2. Make sure you follow ALL steps otherwise it will not work..
Feel free to ask any questions!

First, go in FastBoot mode & reflash recovery from PC.

null0seven said:
First, go in FastBoot mode & reflash recovery from PC.
Click to expand...
Click to collapse
Tried that using different TWRP versions but it didn't work. My issue still persisted.

Puddi_Puddin said:
Use the unbrick guide method 2. Make sure you follow ALL steps otherwise it will not work..
Feel free to ask any questions!
Click to expand...
Click to collapse
Thanks but that that seemed a bit daunting so after MUCH searching I found a thread with a very simple fix. In fastboot type the command "fastboot format cache" and "fastboot format user data". I lost all my stuff but I'm up and running again.
However, I have a new issue. "system" is taking up 29gb of space. What's that about?

showofdeth said:
Thanks but that that seemed a bit daunting so after MUCH searching I found a thread with a very simple fix. In fastboot type the command "fastboot format cache" and "fastboot format user data". I lost all my data but I'm up and running again.
However, I have a new issue. "system" is taking up 29gb of space. What's that about?
Click to expand...
Click to collapse
Try the latest OOS 4.2.5.. It had some fixes

Puddi_Puddin said:
Try the latest OOS 4.2.5.. It had some fixes
Click to expand...
Click to collapse
I like OOS and all but I like the customisation of RR more. Cheers though.

You did even better. Now you have a Clean phone, because you wipe it all.
It's from your rom. I'm on Oos 4.1.5. Look at mine.

null0seven said:
You did even better. Now you have a Clean phone, because you wipe it all.
It's from your rom. I'm on Oos 4.1.5. Look at mine.
Click to expand...
Click to collapse
Can you install oos through TWRP? Maybe as recommended it may fix my storage issue.

How else ?
Never did Fastboot sideload.
I instal any rom ONLY in TWRP.

showofdeth said:
No matter how many resets I just can't boot into my recovery or the OS. If I try to reboot the system all that happens is the TWRP splash screen pops up, hangs there for a while, reboots to the splash screen again and repeats. Is this a brick? The most I can do is get into fastboot mode. Please, any advice would be very much appreciated. I feel like a total dipstick. The ROM I'm on is Resurrection Remix official N and the TWRP version is 3.1.1-0. This combo was never an issue before.
Click to expand...
Click to collapse
showofdeth said:
Tried that using different TWRP versions but it didn't work. My issue still persisted.
Click to expand...
Click to collapse
At this point I'm sure it's a firmware related issue.
Download and install latest one here: https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Stable or Open Beta, doesn't matter.
Then... what TWRP have you tried? For custom roms is highly recommended the blu_spark variant.
Because the stock TWRP is good only for OOS-based firmware, with other configurations it may not boot up at all.
showofdeth said:
Thanks but that that seemed a bit daunting so after MUCH searching I found a thread with a very simple fix. In fastboot type the command "fastboot format cache" and "fastboot format user data". I lost all my stuff but I'm up and running again.
However, I have a new issue. "system" is taking up 29gb of space. What's that about?
Click to expand...
Click to collapse
What have you done? ?
Two theories:
1) You've done encryption via custom rom.
2) After formatting /data via fastboot commands, you've not installed and booted up once latest OOS rom.
Until doing that, device will read 25 GB of free space, both in recovery and system.
I don't know the reason of that trouble.
So you have to:
1) Install latest OOS firmware (via TWRP / adb sideload);
2) Bootup once the system: be sure to choose a pattern required at bootup, for the rest skip wizard as fast as possible;
3) Install latest TWRP blu_spark via fastboot command;
4) From recovery, wipe everything and flash Resurrection Remix.
Tell me if you solve ?

Simone98RC said:
At this point I'm sure it's a firmware related issue.
Download and install latest one here: https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Stable or Open Beta, doesn't matter.
Then... what TWRP have you tried? For custom roms is highly recommended the blu_spark variant.
Because the stock TWRP is good only for OOS-based firmware, with other configurations it may not boot up at all.
What have you done?
Two theories:
1) You've done encryption via custom rom.
2) After formatting /data via fastboot commands, you've not installed and booted up once latest OOS rom.
Until doing that, device will read 25 GB of free space, both in recovery and system.
I don't know the reason of that trouble.
So you have to:
1) Install latest OOS firmware (via TWRP / adb sideload);
2) Bootup once the system: be sure to choose a pattern required at bootup, for the rest skip wizard as fast as possible;
3) Install latest TWRP blu_spark via fastboot command;
4) From recovery, wipe everything and flash Resurrection Remix.
Tell me if you solve
Click to expand...
Click to collapse
I've fixed everything. Flashed a OOS based ROM then did a factory wipe in TWRP and then installed a new RR ROM. Panic over. Sorted.

Installed twrp, but can't get into it

I did the following
1. Downgraded to V30b-EUR-XXX with LGUP. Went smooth.
2. Rooted phone sucessfully with kingroot.
3. Got a shell with "adb shell"
4. "su"
5. Filled the recovery-partition with zeros from /dev/zero with dd
6. Installed twrp3.2.3-0 with dd on recovery-partition
When I boot into Marshmallow, all is fine. When I boot into recovery, I'm informed about a necessary factory reset. I say "Yes" both times, then the LG Logo and some tiny text is displayed and afterwards the screen goes dark. The LED is blinking blue and red; the only way out of this is to remove the battery.
If I do a factory reset from within marshmallow, the result is the same.
What can I do now? Should I flash a stock recovery with dd? But where to get it? Or should I flash an older version of twrp?

Hello,
Last time when I downgraded, I also rooted with KingRoot, but I installed the "Flashify" full version, ( on the ROM of course ) and I flashed the twrp with the flashify as "recovery". This is working.

NetDog75 said:
Hello,
Last time when I downgraded, I also rooted with KingRoot, but I installed the "Flashify" full version, ( on the ROM of course ) and I flashed the twrp with the flashify as "recovery". This is working.
Click to expand...
Click to collapse
Excuse me, but I'm not able to decipher that. What is flashify? What means "on the ROM of course"? Can you give more information please.

- flashify is an application.
- on the ROM = when the phone booted and the operation system is working, you can use your phone... example for phone calls. As you wrote: "boot into Marshmallow"
So, downgrade again, and boot into Marshmallow, use the kingroot, than install the flashify application. You can flash the twrp with the mentioned Flashify application, than reboot to recovery.

NetDog75 said:
- flashify is an application.
- on the ROM = when the phone booted and the operation system is working, you can use your phone... example for phone calls. As you wrote: "boot into Marshmallow"
So, downgrade again, and boot into Marshmallow, use the kingroot, than install the flashify application. You can flash the twrp with the mentioned Flashify application, than reboot to recovery.
Click to expand...
Click to collapse
Don't had to downgrade, because I was in V30b. Got root, installed flashify and flashed twrp - the first time 3.2.3, then 2.8.0. Same result as before.
From what version of android did you install what version of twrp?

Hi,
I use the twrp3.2.3 and no problem.
I'm not expert, I just can recommend some steps...
Maybe good idea to flash again the stock ROM. You can find here on the forum many step by step guide for this. ( tools and steps )
It seems your phone recovery partition is not OK....
I have no more idea...

@theuving, why did you decide to zero out the recovery partition? I don't know but that may be part of the problem. Since you were connected via adb was it not possible to use fastboot? Flashing the recovery via that should(?) have also worked.
If the recovery partition is messed up you might have to start over. Not sure though as I haven't experienced that problem.
ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy

marcdw said:
@theuving, why did you decide to zero out the recovery partition? I don't know but that may be part of the problem. S
Click to expand...
Click to collapse
It's the same partition where I flashed twrp, so the zeros are already overwritten with something else ...
Seriously: Zeroing the partition before writing to it was mentioned in a thread about the installation of a "bumped" recovery.

NetDog75 said:
Hi,
I use the twrp3.2.3 and no problem.
Click to expand...
Click to collapse
OK, that is the version I used also. What android version was installed when you flashed the recovery? Mine is stock V30b.

Hi,
I'm not sure, because I changed to 8.1 (oreo).
Maybe V30N.....

I am having the same problem. There is no "unlock bootloader" in the developer options, and adb reboot bootloader just starts into android again. I might have to reflash the stock firmware, but nowhere in the install instructions for twrp does it say that you first have to unlock the bootloader, and nowhere does it even mention that there might not be such an option. This is genuinely strange.