Hello, I've been unable to flash Pac Rom build 03/03/14 in BWM as it says there's an error in opening the zip file. But, I can flash and boot the previous Pac Rom without problems.... So, any suggsetion?
X3EME said:
Hello, I've been unable to flash Pac Rom build 03/03/14 in BWM as it says there's an error in opening the zip file. But, I can flash and boot the previous Pac Rom without problems.... So, any suggsetion?
Click to expand...
Click to collapse
It is probably a bad download. try re-downloading the zip
Alright, noticed there is a build 04/03/14. will test that now
Edit: Nope, still won't flash.... I've redownloaded it as you suggest but to no avail I guess
X3EME said:
Alright, noticed there is a build 04/03/14. will test that now
Edit: Nope, still won't flash.... I've redownloaded it as you suggest but to no avail I guess
Click to expand...
Click to collapse
write down the error code and google it. but in this case it usually caused by bad zip file
Related
I'm having problems installing any of the franco kernel through twrp 2.6 the latest twrp anyways when I install the zip file it fails. I'm running 9/4 pac also though i don't think that would have anything to do with it failing i tried the 182 and 178 i believe also the jj ones to any help thanks. Oh also i saw the iso files i believe but thought they had to be zipped to install through recovery so maybe that way would work however you install them with the iso thanks again
spriteboost said:
I'm having problems installing any of the franco kernel through twrp 2.6 the latest twrp anyways when I install the zip file it fails. I'm running 9/4 pac also though i don't think that would have anything to do with it failing i tried the 182 and 178 i believe also the jj ones to any help thanks. Oh also i saw the iso files i believe but thought they had to be zipped to install through recovery so maybe that way would work however you install them with the iso thanks again
Click to expand...
Click to collapse
iso files.. for a kernel? what did you actually download? its not a kernel for sure.
simms22 said:
iso files.. for a kernel? what did you actually download? its not a kernel for sure.
Click to expand...
Click to collapse
sorry not iso. I didn't download the img file and meant img file. I only downloaded the zip file from http://forum.xda-developers.com/showthread.php?t=2002782 I first thought it was my recovery was out of date so updated twrp which got me nothing and took forever because goomanager didn't do it so had to use nexus root tool kitv1.7.2 finally got that updated and still the zip file fails also tried the lte zip from http://forum.xda-developers.com/showthread.php?t=2358931 to have lte when and if it ever rolls out in my area but that ones not important plus i think pac's rom has it automatically in it because when i dialed *#*#4636#*#* lte is an option.
Anyways the problems with the zip file when i install it or try to that is it fails with 182 the jj file to and the 178 and jj file don't know what i'm doing wrong and it my mistake again img not iso.
spriteboost said:
sorry not iso. I didn't download the img file and meant img file. I only downloaded the zip file from http://forum.xda-developers.com/showthread.php?t=2002782 I first thought it was my recovery was out of date so updated twrp which got me nothing and took forever because goomanager didn't do it so had to use nexus root tool kitv1.7.2 finally got that updated and still the zip file fails also tried the lte zip from http://forum.xda-developers.com/showthread.php?t=2358931 to have lte when and if it ever rolls out in my area but that ones not important plus i think pac's rom has it automatically in it because when i dialed *#*#4636#*#* lte is an option.
Anyways the problems with the zip file when i install it or try to that is it fails with 182 the jj file to and the 178 and jj file don't know what i'm doing wrong and it my mistake again img not iso.
Click to expand...
Click to collapse
you cant flash img files via recovery.. you either flash it via fastboot or through apps that flash it via fasrboot/terminal for you.
simms22 said:
you cant flash img files via recovery.. you either flash it via fastboot or through apps that flash it via fasrboot/terminal for you.
Click to expand...
Click to collapse
Thanks tried flashing the img file with franco's kernel updater and got a bootloop idk why this is impossible for my phone right now my kernels 3.4.0-perf-g0b3e615 do i have to uninstall it first somehow?
also when i try installing it through twrp it says zip verification fail :-\
spriteboost said:
Thanks tried flashing the img file with franco's kernel updater and got a bootloop idk why this is impossible for my phone right now my kernels 3.4.0-perf-g0b3e615 do i have to uninstall it first somehow?
also when i try installing it through twrp it says zip verification fail :-\
Click to expand...
Click to collapse
I have the same issue with my nexus 4. Installed jelly bam, then had to update tarp to 2.6, yet it still won't flash any version of Franco kernel. Yes they are zip files and from the Dev directly. It gives me zip verification failed so I toggled verify zip signature and it said success. I wipe cache again and reboot. Now I am stuck with with the white Google logo. So I just reinstall jelly bam to get back to a working kernel. I have yet to flash cm to see if a different recovery works, or if it's a problem with the kernel or even jelly bam
SOLVED
I changed the recovery from twrp to cwm and then flashed it. cwm said it worked, but when i wiped cache and rebooted, im still stuck on the white google logo. Looking at your kernel, im assuming you too have jelly bam installed.
It seems you have to manually install it. Download the img file you want off here (use jss versions if you are on jellybam 10.2+)
go to fastboot mode
fastboot flash boot kernel_name.img
this seems to have worked for me. why it has to be this way; i have no idea.
why do you wipe cache? try without wiping!
Gesendet von meinem Nexus 4 mit Tapatalk 4
Its just a habit. Can that actually be the issue? Also I did not check, but maybe the reason it said "success" was because file signature verification was off. Twrp said it worked when I turned it off, so that could be why cwm said successful too
Sent from my Nexus 4 using XDA Premium 4 mobile app
I'm trying to upgrade to the latest twrp but can't seem to flash it.
I've downloaded the .zip but when ibflash with current twrp 2.7.0 it tells me it can't open the zip?
I've also tried flashing with flashify to no avail? Any help?
Valiceemo said:
I'm trying to upgrade to the latest twrp but can't seem to flash it.
I've downloaded the .zip but when ibflash with current twrp 2.7.0 it tells me it can't open the zip?
I've also tried flashing with flashify to no avail? Any help?
Click to expand...
Click to collapse
i would redownload the zip and check that the file size is correct. if it's a corrupted download it wont flash. happened to me several times.
kbkang said:
i would redownload the zip and check that the file size is correct. if it's a corrupted download it wont flash. happened to me several times.
Click to expand...
Click to collapse
Thanks. Got it done now. Must have been a dodgy download. Took several attempts to get it too D/L properly.
Thanks
Valiceemo said:
Thanks. Got it done now. Must have been a dodgy download. Took several attempts to get it too D/L properly.
Thanks
Click to expand...
Click to collapse
while i was testing stuff i found....
from 4.2.2 using different way (some tool) to get recovery (not autorec) i could update to official twrp 2.8.x.x.
using 4.4.2 using autorec cant update to official twrp 2.8.x.x.
but can update to the custom 2.8.x.x availabe here with f2fs version.
Hi all, I have 3 S5 models with the same problem (M, F and FD) and I have been running cm nightlies in these devices, but I am unable to update the rom by clicking update now after the download, the device will just boot to the recovery and I have to manually pick the right file, sometimes it just work (at random) but most of the time I have to pick the file, my guess is that I have the wrong recovery, I tried Philz and I am now running TWRP, which do you recommend?
TWRP should be able to automatically install ROM updates. Also Questions don't go in the General section
serdasteclas said:
Hi all, I have 3 S5 models with the same problem (M, F and FD) and I have been running cm nightlies in these devices, but I am unable to update the rom by clicking update now after the download, the device will just boot to the recovery and I have to manually pick the right file, sometimes it just work (at random) but most of the time I have to pick the file, my guess is that I have the wrong recovery, I tried Philz and I am now running TWRP, which do you recommend?
Click to expand...
Click to collapse
you could try deelting the old updates, if it only has one file to pick from and it picks it everytime theres ur problem
aliyangohar4 said:
TWRP should be able to automatically install ROM updates. Also Questions don't go in the General section
Click to expand...
Click to collapse
TWRP should be able to automatically install ROM updates. Also Questions don't go in the General section
Click to expand...
Click to collapse
Sorry, I'll move this as soon as I find out how, maybe my problem is the version.
-PiLoT- said:
you could try deelting the old updates, if it only has one file to pick from and it picks it everytime theres ur problem
Click to expand...
Click to collapse
Even if I delete all the other files it doesn't reboot and installs automatically as it should
Is it working now?
aliyangohar4 said:
Is it working now?
Click to expand...
Click to collapse
I installed TWRP manager and updated TWRP to 2.8.6.0 but the problem persist, when I am installing the file I can see an error:
E:Zip file is corrupt!
E:Error installing zip file '@/cache/recovery/block.map'
serdasteclas said:
I installed TWRP manager and updated TWRP to 2.8.6.0 but the problem persist, when I am installing the file I can see an error:
E:Zip file is corrupt!
E:Error installing zip file '@/cache/recovery/block.map'
Click to expand...
Click to collapse
That's not a TWRP issue
I've been trying to re-ROM my phone from CM11 to CM12.1, but I keep getting:
error executing updater binary in zip
Click to expand...
Click to collapse
From what I've seen recommended is to wipe the phone, which I have with TWRP and I keep getting their error when I try to install the new ROM.
That error leads me to believe the rom is not made for the phone or the zip file is corrupted.
audit13 said:
That error leads me to believe the rom is not made for the phone or the zip file is corrupted.
Click to expand...
Click to collapse
I"ve been trying this with a few different updated ROMs. As for the ROM not being for the phone, it is unlikely since it is unified. I'd post the link, but the forum won't let me yet.
The recovery is TWRP 2.8.7.1 or newer?
Examine the updater script in the ROM to make sure your phone meet's the requirements.
audit13 said:
The recovery is TWRP 2.8.7.1 or newer?
Examine the updater script in the ROM to make sure your phone meet's the requirements.
Click to expand...
Click to collapse
I have 2.8.0.1. I'll upgrade and see if that works.
audit13 said:
The recovery is TWRP 2.8.7.1 or newer?
Examine the updater script in the ROM to make sure your phone meet's the requirements.
Click to expand...
Click to collapse
Upgraded to 3.0.0.0 and still having the same issue. Wiped cache/dalvik, did a Factory Reset in TWRP as well, tried to flash again, and I'm still getting the same error message:
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/ROM/cm-12.1-20160302-NIGHTLY-hlte.zip'
Click to expand...
Click to collapse
Since the updater script error is still appearing, it sounds like the phone is not compatible with the ROM.
What is the exact model of the phone?
audit13 said:
Since the updater script error is still appearing, it sounds like the phone is not compatible with the ROM.
What is the exact model of the phone?
Click to expand...
Click to collapse
Samsung Galaxy Note 3 (T-Mobile, US).
Isn't this for the sm-n900t: https://download.cyanogenmod.org/?device=hltetmo ?
audit13 said:
Isn't this for the sm-n900t: https://download.cyanogenmod.org/?device=hltetmo ?
Click to expand...
Click to collapse
I was using the hlte one (Unified version) since that worked with CM11. I am now booting up my Note 3 with CM12-1. Thank you! :highfive:
Glad it worked.
Btw, the T-Mobile forum is here: http://forum.xda-developers.com/note-3-tmobile
I'm Stock rooted latest twrp, but can install aosp based Roms, well it lets me install the Roms but no gapps package works none of them.
Forgot the error something about modified image needed.
Just trying to install an aosp based ROM not sure what's going on.
Sent from my Nexus 6P using Tapatalk
humdrum2009 said:
I'm Stock rooted latest twrp, but can install aosp based Roms, well it lets me install the Roms but no gapps package works none of them.
Forgot the error something about modified image needed.
Just trying to install an aosp based ROM not sure what's going on.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you can get an exact copy of the error message and post it here it'll help us figure out whats going on (hopefully). Also, What version of twrp are you using?
humdrum2009 said:
I'm Stock rooted latest twrp, but can install aosp based Roms, well it lets me install the Roms but no gapps package works none of them.
Forgot the error something about modified image needed.
Just trying to install an aosp based ROM not sure what's going on.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Having root has nothing to do with the ability to flash ROMs, you might be a bit confused about that. You need to provide more information too please:
1. What ROMs have you tried?
2. Exactly what gapps have you tried?
3. Are you making sure you flash the correct corresponding vendor image to go with the ROM build?
4. Exactly what error(s) are you getting?
Messgaes on failure
when i reboot i get your system cant be checked for corruption,please lock boot loader.
after twrp starts i try and flash dirty unicorn,i think i am missing a step
error says
update process ended with error 7
error installing zip file /sdcard/DU_TBO_GAPPS_3.1 ZIP
Okay dirty unicorn boots with the message flash updated vendor image.
humdrum2009 said:
when i reboot i get your system cant be checked for corruption,please lock boot loader.
after twrp starts i try and flash dirty unicorn,i think i am missing a step
error says
update process ended with error 7
error installing zip file /sdcard/DU_TBO_GAPPS_3.1 ZIP
Okay dirty unicorn boots with the message flash updated vendor image.
Click to expand...
Click to collapse
if someone could point me to the vendor images i can fla**** in fastboot latest updated build
humdrum2009 said:
if someone could point me to the vendor images i can fla**** in fastboot latest updated build
Click to expand...
Click to collapse
Here: https://www.androidfilehost.com/?w=files&flid=49333
Thanks to BeansTown106
Werid couldn't flash vendor image in fastboot ,neither with adb or wugfresh
I just went back to stock rooted for the time being. That link you provided if dead 404. I found it elsewhere on XDA going to try dirty u again in a few minutes wish me luck lol.
Sent from my Nexus 6P using Tapatalk