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.
Related
Hi, any help resolving this would be really appreciated. I have updated my Nexus 4 to Android 4.3 by installing through CWM. The upgrade worked fine however I cannot flash the SuperSU zip afterwards. I am using the experimental version released specifically for 4.3 however I just get the message: unable to open 'file', installation aborted (bad). I have tried to redownload in case it was a corrupt zip but I just get the same result. I have also tried reflashing 4.3 but this doesn't make a difference either.The old SuperSU is still installed but states that it has no binaries if I try to open it.
Sorry if this has been covered elsewhere but I have been searching all evening for a solution.
Sam
shardy said:
Hi, any help resolving this would be really appreciated. I have updated my Nexus 4 to Android 4.3 by installing through CWM. The upgrade worked fine however I cannot flash the SuperSU zip afterwards. I am using the experimental version released specifically for 4.3 however I just get the message: unable to open 'file', installation aborted (bad). I have tried to redownload in case it was a corrupt zip but I just get the same result. I have also tried reflashing 4.3 but this doesn't make a difference either.The old SuperSU is still installed but states that it has no binaries if I try to open it.
Sorry if this has been covered elsewhere but I have been searching all evening for a solution.
Sam
Click to expand...
Click to collapse
Did you try flashing the latest supersu? I've flashed this one https://www.dropbox.com/s/p97y9pn4tie9iyi/UPDATE-SuperSU-v1.43.zip pressed "go back" when recovery asked to fix recovery or something like that and it works just fine
Ah, The version I have is 1.41 not 1.43, although I guess I downloaded from an older post in the blog. Thank you, hopefully that will work.
Sent from my Nexus 4 using xda app-developers app
Unfortunately this still hasn't worked, I have tried v1.43 of SuperSU, still failes. I have also changed my recovery from CWM to TWRP but this also fails to flash SuperSU v1.43 with the same error. Any other suggestions?
I think I have resolved this now, I had to sideload the SuperSU file on instead, so far so good.
Thanks.
shardy said:
I think I have resolved this now, I had to sideload the SuperSU file on instead, so far so good.
Thanks.
Click to expand...
Click to collapse
I have the same issue. I also notice root explorer can't look inside zip files. It seems like whatever custom recoveries and other apps use to extract zip files is busted/removed after our 4.3 update. Is this a busybox issue? Side loading might use extraction tools on the computer instead?
I resolved this too. It turned out the super SU zip file I had grabbed for 1.43 wasn't the normal CWM/TWRP recovery package. When I looked at the zip file on my computer I noticed it contained another compressed file. I waited a few days root-less and then noticed that super SU 1.51 had been released. I used this file and it worked like it should have the first time. This package looks like the normal recovery flashable file, with the manifest and directory structure it should have. So either I grabbed the wrong file or there was a moment in time when the chainfire's site was dishing out bad files.
Glad it's working now, root is restored.
shardy said:
I think I have resolved this now, I had to sideload the SuperSU file on instead, so far so good.
Thanks.
Click to expand...
Click to collapse
Can you elaborate, as to what exactly you did to restore the root?
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
https://drive.google.com/file/d/0B3W1wsYle4wla29SRjgzSlBfVm8/view?usp=drivesdk
I just got the phone (OnePlus 5). I have rooted it and installed twrp. I couldnt update due to signature verification error. I was told to flash the zip with twrp, and I did. Now it has been running for hours but the bar hasnt moved. Can anyone help me?
PowerOfDerp said:
https://drive.google.com/file/d/0B3W1wsYle4wla29SRjgzSlBfVm8/view?usp=drivesdk
I just got the phone (OnePlus 5). I have rooted it and installed twrp. I couldnt update due to signature verification error. I was told to flash the zip with twrp, and I did. Now it has been running for hours but the bar hasnt moved. Can anyone help me?
Click to expand...
Click to collapse
Did you wipe before you flash?
You need to flash the full ROM zip, not just the OTA zip.
Pwnycorn said:
You need to flash the full ROM zip, not just the OTA zip.
Click to expand...
Click to collapse
Ok, its my first time flashing an ota, so bare with me. I got the file from here. First of all, how do I get out of this state? And if thats not the full ROM, where can I get it?
PowerOfDerp said:
Ok, its my first time flashing an ota, so bare with me. I got the file from here. First of all, how do I get out of this state? And if thats not the full ROM, where can I get it?
Click to expand...
Click to collapse
Well, I've never flashed one either. This is my first OnePlus device.
The link you posted is the official one for downloads and the size of the full ROM I understood is 1.5 - 2GB. So it seems you do have the right file.
You could flash the stock recovery img with TWRP - it can be obtained from the same link - and flash the OTA zip with that.
During the flashing process of the OTA you would've lost TWRP anyway, so it's not a big loss.
Pwnycorn said:
Well, I've never flashed one either. This is my first OnePlus device.
The link you posted is the official one for downloads and the size of the full ROM I understood is 1.5 - 2GB. So it seems you do have the right file.
You could flash the stock recovery img with TWRP - it can be obtained from the same link - and flash the OTA zip with that.
During the flashing process of the OTA you would've lost TWRP anyway, so it's not a big loss.
Click to expand...
Click to collapse
ok, but should i just try and shut down the device?
Hello,
today i wanted to update my *rooted* WAS-LX1 to B182, so i downloaded the update.zip and tried to flash it with FlashFire.
Then my phone booted in Error Mode. So i tried to boot in Fastboot mode, and it worked. So i flashed TWRP and now i want to install Stock firmware again, but i don't know which file i should flash. I've got 3 files called update.zip, update_data_full_public.zip and update_full_WASL21A_hw_eu.zip.
I hope you can help me.
Zillinda
Zillinda said:
Hello,
today i wanted to update my *rooted* WAS-LX1 to B182, so i downloaded the update.zip and tried to flash it with FlashFire.
Then my phone booted in Error Mode. So i tried to boot in Fastboot mode, and it worked. So i flashed TWRP and now i want to install Stock firmware again, but i don't know which file i should flash. I've got 3 files called update.zip, update_data_full_public.zip and update_full_WASL21A_hw_eu.zip.
I hope you can help me.
Zillinda
Click to expand...
Click to collapse
To update my rooted phone to B182 I had to download the full package (2.3gb, including update.zip and update_full_WASL21A_hw_eu.zip). I was not successfull in updating via TWRP. I updated via the official system menu so I don't know how exactly it was applied. According to other guides (http://www.stechguide.com/tag/was-lx1c432b182/ for example) it should be update.zip first and update_full_WASL21A_hw_eu.zip second, without a reboot. Let us know how it worked out...
garris_bibop said:
To update my rooted phone to B182 I had to download the full package (2.3gb, including update.zip and update_full_WASL21A_hw_eu.zip). I was not successfull in updating via TWRP. I updated via the official system menu so I don't know how exactly it was applied. According to other guides (http://www.stechguide.com/tag/was-lx1c432b182/ for example) it should be update.zip first and update_full_WASL21A_hw_eu.zip second, without a reboot. Let us know how it worked out...
Click to expand...
Click to collapse
Unfortunately it didn't work. The only thing i can do is boot in the TWRP recovery. Is there a way to flash the stock rom with fastboot?
Zillinda said:
Unfortunately it didn't work. The only thing i can do is boot in the TWRP recovery. Is there a way to flash the stock rom with fastboot?
Click to expand...
Click to collapse
I only tried flashing the update via sideload and recovery and it didn't work (http://rootmygalaxy.net/flash-ota-firmware-updates-using-adb-fastboot-commands/). Maybe you are lucky. Problem is, I'm quite new to this stuff, hopefully someone else can help out.
Can someone please provide us with a link for the stock recovery?
kazzot17 said:
Can someone please provide us with a link for the stock recovery?
Click to expand...
Click to collapse
https://mega.nz/#!V3AwUI6K!mcqlNCwcyE71MroUZuP9w-bNDhgt3MGzz0svgHUY8Ow
By the way, i solved the problem. I downloaded HuaweiUpdateExtractor for extracting the .img files from the update.app and i flashed them with fastboot.
Nice, congrats
Hello,
I got the error " error installing zip file " while a try to flash oos 11.1.2.2.
I try sideload instead by it Failed instantly. I tried to format data and wipe without any change. I also tried to boot other version of TWRP (I currently use a custom version of TWRP 3.6.0), but I always got a Crash Dump error.
I was able to install rom with this version of TWRP before and I have wanted to install PixelExperience but I have forgotten to flash oos 11.1.2.2 before and i think is that witch broken TWRP.
I also tried to reinstall TWRP.
Any ideas on this?
wiiznokes2 said:
Hello,
I got the error " error installing zip file " while a try to flash oos 11.1.2.2.
I try sideload instead by it Failed instantly. I tried to format data and wipe without any change. I also tried to boot other version of TWRP (I currently use a custom version of TWRP 3.6.0), but I always got a Crash Dump error.
I was able to install rom with this version of TWRP before and I have wanted to install PixelExperience but I have forgotten to flash oos 11.1.2.2 before and i think is that witch broken TWRP.
I also tried to reinstall TWRP.
Any ideas on this?
Click to expand...
Click to collapse
I had that error before from a bad copy of oos. I would download it again and copy to USB again if that's what you're using. Also use this twrp to fastboot boot it works I actually just had to do it a min ago.
Brettroth said:
I had that error before from a bad copy of oos. I would download it again and copy to USB again if that's what you're using. Also use this twrp to fastboot boot it works I actually just had to do it a min ago.
Click to expand...
Click to collapse
Thank you, I will try that. Can you send me a link of oos that I should install, I'm not sure if it's that one https://www.oneplus.com/fr/support/softwareupgrade/details?code=PM1574156215016 .
Also, shoud I use "flash current TWRP" before flashing the ROM?
wiiznokes2 said:
Thank you, I will try that. Can you send me a link of oos that I should install, I'm not sure if it's that one https://www.oneplus.com/fr/support/softwareupgrade/details?code=PM1574156215016 .
Also, shoud I use "flash current TWRP" before flashing the ROM?
Click to expand...
Click to collapse
Yeah definitely flash current twrp first. The oos you used is not the latest I'll just upload it. The latest and last ever update from OnePlus is 11.1.2.2
Brettroth said:
Yeah definitely flash current twrp first. The oos you used is not the latest I'll just upload it. The latest and last ever update from OnePlus is 11.1.2.2
Click to expand...
Click to collapse
That worked, thank a lot!
wiiznokes2 said:
That worked, thank a lot!
Click to expand...
Click to collapse
You're welcome