ok so i downloaded the grevious flexx rom and tried to flash in recovery i got the philz recovery btw and it tells me (bad) install
i first downloaded in the computer tranfered it still (bad) then i downloaded itfrom myphone andonce again(bad) what can i do??!?!?
quick fix
felix787 said:
ok so i downloaded the grevious flexx rom and tried to flash in recovery i got the philz recovery btw and it tells me (bad) install
i first downloaded in the computer tranfered it still (bad) then i downloaded itfrom myphone andonce again(bad) what can i do??!?!?
Click to expand...
Click to collapse
" So what i would recommend you do, is clean install the offical lg g2 software and then try again. delete all the old files from your phone and laptop and re-downlode and then try re-installing. It should work. I had the same issue with cyanagynmod. Works fine now.
felix787 said:
ok so i downloaded the grevious flexx rom and tried to flash in recovery i got the philz recovery btw and it tells me (bad) install
i first downloaded in the computer tranfered it still (bad) then i downloaded itfrom myphone andonce again(bad) what can i do??!?!?
Click to expand...
Click to collapse
the file is corrupt. maybe its just your internet. if you download it on your phone make sure the screen stays on, deep sleep messes with wifi. redownload it and try again. otherwise the developer released a bad zip and either pick an older version or wait for a new one. in the mean time restore to the backup that LITERALLY EVERY MOD/ROM/GUIDE told you to make.
Related
i go into recovery from rom manager to flash a ROM or a kernel but i keep getting an error saying installation aborted with an open android and a red triangle.
Possibly a bad download. Try checking the MD5 Sum.
Sent from my R800i using xda premium
Can be also an incompatibility with CWM recovery. If you re-download and have problems again, try chaning your recovery.
I unrooted ,locked the boot loader and again rooted installed the twrp recovery still I get the same error .... Even when I download busybox form market it does not install it says I'm not rooted . But i am able to flash kernels but not roms ..
Are you sure that the rom is zipped well?
I can give you answers on how to solve your problem , visit this link .
http://www.neopeek.com/viewtopic.php?t=7281
Skyღ said:
Are you sure that the rom is zipped well?
I can give you answers on how to solve your problem , visit this link .
http://www.neopeek.com/viewtopic.php?t=7281
Click to expand...
Click to collapse
I was wondering if it was zipped well, cause CWM rom signature is disabled, so I tried zipping with WinRAR instead of 7zip but to no avail.
Does the fact that I had to OVERWRITE files in order to modify the updater script change something ? If I understand correctly from the thread you pointed to, META INF lists the files the zip should contain. Since I had to overwrite some, I guess it's normal that install fails, right ?
Damnit! All because I cant get the ray to self identify as ST18i or ST18a but instead I dont know why it says it's a ST18..
This happened to me once, because I wiped my sd card. To bypass this, I erased the first line of the build prop in the rom, so cwm (or twrp) will not check if the device is compatible with the rom.
Clockworkmod
kkmindfreak10 said:
i go into recovery from rom manager to flash a ROM or a kernel but i keep getting an error saying installation aborted with an open android and a red triangle.
Click to expand...
Click to collapse
Try to update or install the last clockworkmod with rom manager. that happen to me with the tmo s3 firts time i root it and install the clockworkmod 5.0.3 then i updated to 6.0.3...... and good to go.
hope work for you
!JORGE! said:
Try to update or install the last clockworkmod with rom manager. that happen to me with the tmo s3 firts time i root it and install the clockworkmod 5.0.3 then i updated to 6.0.3...... and good to go.
hope work for you
Click to expand...
Click to collapse
Having the same problem as him but mine is 6.0.5.0
Hi Guys:
I have a doubt.
I had installed cm9 rc2 on a nexus s i9023 then i used a backup to revert to stock ics 4.04 and received the OTA update.
But when it was about to install i got the following message
Install untrusted package-----> this was in the upper part of the screen
THIS CAN BE UNDONE------->
CLOCKwordkmod recovery v6.0.0.7
finding update package
opening update package
verifying update package
E:failed to verify whole-file package signature
E: siganture verification failed
After that i choose to go ahead an the update installed
It also asked me to disable recovery !
is the unsigned package cmw 6... or am i wrong and i have installed a no official rom?
Help me to clarify was going on !
I could bar wrong, but you may have signature verification enabled within CWM. And also, you are given the option to keep CWM upon flashing the official update.
Sent from my A500
DefinitiveX said:
I could bar wrong, but you may have signature verification enabled within CWM. And also, you are given the option to keep CWM upon flashing the official update.
Sent from my A500
Click to expand...
Click to collapse
i have check an signature verification is disable in cwm but i think that the update when throw stock recovery (android guy in the background) that's why i think that the package that the message refres is cmw, but my question is why? What does have to do cwm with the update if the stock recovery was working?
Did you use stock recovery to flash? If so, my opinion on stock recovery isn't good. Lol.
Sent from my A500
Thanks man !
DefinitiveX said:
Did you use stock recovery to flash? If so, my opinion on stock recovery isn't good. Lol.
Sent from my A500
Click to expand...
Click to collapse
Double check !, CMW Recovery was used !
Check twice with OTA and manually updating with the update file place in sd card
Same result !
Guess it happens because of CMW Recovery as you alreday told me , maybe CWM does not recognize the signature or something !
Guess learn something new today !
Thanks man !
xxalv01xx said:
Double check !, CMW Recovery was used !
Check twice with OTA and manually updating with the update file place in sd card
Same result !
Guess it happens because of CMW Recovery as you alreday told me , maybe CWM does not recognize the signature or something !
Guess learn something new today !
Thanks man !
Click to expand...
Click to collapse
Get the same verification error, so how did you finally proceed to intall the OTA-update?
xxalv01xx said:
Double check !, CMW Recovery was used !
Check twice with OTA and manually updating with the update file place in sd card
Same result !
Guess it happens because of CMW Recovery as you alreday told me , maybe CWM does not recognize the signature or something !
Guess learn something new today !
Thanks man !
Click to expand...
Click to collapse
Another thing I would recommend would be reflashing CWM.
Sent from my Nexus S using xda app-developers app
MrEasy666 said:
Get the same verification error, so how did you finally proceed to intall the OTA-update?
Click to expand...
Click to collapse
Just select the option to install it besides it is not verified !
Don't remember the exact message, but the idea is the select the to install it anyway !
xxalv01xx said:
Just select the option to install it besides it is not verified !
Don't remember the exact message, but the idea is the select the to install it anyway !
Click to expand...
Click to collapse
Yes, just selected "install from zip" and selected the OTA-update in CWMR and this worked.
recently i flashed stock rom,then cwm........and finally rooted my phone
but after restarting phone......superuser is not working.......it was already present when i booted the phone....so yeah rooting was successful !
when i try to run TB it got stucked on asking root digits....superuser doesnt poped up.....
also cant update binary.....tried installing supersu...but it also didnt work.........
so what can i do to get root access .........!!!!
flash any recovery like cwm / twrap
download this file : Rooting_SGAP
Flash via recovery...
j.posarekar70 said:
flash any recovery like cwm / twrap
download this file : Rooting_SGAP
Flash via recovery...
Click to expand...
Click to collapse
thanks.......:good:
beastwolf said:
recently i flashed stock rom,then cwm........and finally rooted my phone
but after restarting phone......superuser is not working.......it was already present when i booted the phone....so yeah rooting was successful !
when i try to run TB it got stucked on asking root digits....superuser doesnt poped up.....
also cant update binary.....tried installing supersu...but it also didnt work.........
so what can i do to get root access .........!!!!
Click to expand...
Click to collapse
This problem happened to me and i flashed the superuser zip file again and i solved the problem
Hello,
I just unlocked my bootloader...installed CWM 6.0.4.5.....installed SU (verified root) and attempted to flash CM11
I pushed the rom.zip to /sdcard/
I also pushed gapps to the same directory
I tried to install CM from within CWM and I got "E:Can't open /data/media/cm-11-20140205-NIGHTLY-hammerhead.zip (bad) Installation aborted."
I tried to install gapps as well, just to see....and I get the same error.
What am I doing wrong?
I also tried dropping the files straight to the phone from within windows, and then running them from CWM..same error.
I also attempted to sideload CM11...and I get "E:Can't open /tmp/update.zip (bad) Installation aborted."
I have been running custom roms since the G1....(G2...Nexus 4....Galaxy series phones) this is the first time that i've hit a roadblock like this from all directions.
Any advice would be awesome, thank you
losballatopg said:
Hello,
I just unlocked my bootloader...installed CWM 6.0.4.5.....installed SU (verified root) and attempted to flash CM11
I pushed the rom.zip to /sdcard/
I also pushed gapps to the same directory
I tried to install CM from within CWM and I got "E:Can't open /data/media/cm-11-20140205-NIGHTLY-hammerhead.zip (bad) Installation aborted."
I tried to install gapps as well, just to see....and I get the same error.
What am I doing wrong?
I also tried dropping the files straight to the phone from within windows, and then running them from CWM..same error.
I also attempted to sideload CM11...and I get "E:Can't open /tmp/update.zip (bad) Installation aborted."
I have been running custom roms since the G1....(G2...Nexus 4....Galaxy series phones) this is the first time that i've hit a roadblock like this from all directions.
Any advice would be awesome, thank you
Click to expand...
Click to collapse
Flash Philz touch recovery or TWRP and try to flash the rom again bro. Or redownload the rom again, maybe a bad download.
gee2012 said:
Flash Philz touch recovery or TWRP and try to flash the rom again bro. Or redownload the rom again, maybe a bad download.
Click to expand...
Click to collapse
Same thing in TWRP only it says "E:unable to open zip file. Error flashing zip "/sdcard/cm-11-......."
losballatopg said:
Same thing in TWRP only it says "E:unable to open zip file. Error flashing zip "/sdcard/cm-11-......."
Click to expand...
Click to collapse
Turn off the antivirus on your pc temporarily and re-download the rom and gapps and flash them again. Hope it works now.
gee2012 said:
Turn off the antivirus on your pc temporarily and re-download the rom and gapps and flash them.
Click to expand...
Click to collapse
I don't use antivirus....
losballatopg said:
I don't use antivirus....
Click to expand...
Click to collapse
Oke, have you tried downloading the rom and gapps again and flash them?
gee2012 said:
Oke, have you tried downloading the rom and gapps again and flash them?
Click to expand...
Click to collapse
Yes, I have also tried flashing other versions of CM11 (snapshot...other nightlies...)
losballatopg said:
Yes, I have also tried flashing other versions of CM11 (snapshot...other nightlies...)
Click to expand...
Click to collapse
Can you flash anything else in recovery besides the CM rom or do all installations abort?
gee2012 said:
Can you flash anything else in recovery besides the CM rom or do all installations abort?
Click to expand...
Click to collapse
As I said..I tried to flash Gapps...just to see if it flashed...it didn't. Gave me the same error. Would you suggest I attempt to flash something else?
losballatopg said:
As I said..I tried to flash Gapps...just to see if it flashed...it didn't. Gave me the same error. Would you suggest I attempt to flash something else?
Click to expand...
Click to collapse
Didn't you flash supersu to root in cwm?
That most have flashed
jd1639 said:
Didn't you flash supersu to root in cwm?
That most have flashed
Click to expand...
Click to collapse
Oh, yeah..I should probably correct that...I did not manually flash SuperSU.
Upon restarting my phone from CWM at some point it asked me if I wanted to protect root, and install SU.
When I loaded up android, I verified that SuperSU had been installed, and ran an app that requires root to verify.
losballatopg said:
Oh, yeah..I should probably correct that...I did not manually flash SuperSU.
Upon restarting my phone from CWM at some point it asked me if I wanted to protect root, and install SU.
When I loaded up android, I verified that SuperSU had been installed, and ran an app that requires root to verify.
Click to expand...
Click to collapse
I would fastboot flash the recovery again. Cwm or twrp. Might try twrp this time
jd1639 said:
I would fastboot flash the recovery again. Cwm or twrp. Might try twrp this time
Click to expand...
Click to collapse
Yeah...I tried multiple versions already. CWM 6.0.4.4/6.0.4.5 TWRP 2.6.....didn't change anything
I'm downloading the CM11 and Gapps files from another computer now..
thank you for the help btw
losballatopg said:
Yeah...I tried multiple versions already. CWM 6.0.4.4/6.0.4.5 TWRP 2.6.....didn't change anything
I'm downloading the CM11 and Gapps files from another computer now..
thank you for the help btw
Click to expand...
Click to collapse
Np, sorry I should have read the entire thread more carefully.
AHA! I have successfully sideloaded CM and Gapps on another computer.
However...attempting to install it via "install from zip" was still giving me the same error
losballatopg said:
hmm...now when I try to sideload i get....
"restarting adbd....
finding update package.....
opening update package....
installing update....."
then it never advances past that.
Should it confirm the update? should it say anything else?
Click to expand...
Click to collapse
It should compete, but it takes a long time. Did you give it at least 10 minutes?
The Screenshot is below. I got stuck in the H2OS 2.0 so I flash the cos12 to save it from bricking. Then I flash the TWRP. When I wanted to flash a CM13,the problem in the screenshot occurred. Need some Help here.
Help,PLZ
I don't have another phone.I gotta fix this as soon as possible in case I don't miss any important phone calls. plz. Somebody gives me a hand.
The problem is that you're not installing the TWRP flashable rom.
See that the zip file of the CM13 build you tried to install is called cm13......bacon-signed-fastboot......zip. So you're trying to install a fastboot rom with a custom recovery, instead of trying to install a custom rom for a custom recovery. That's why TWRP doesn't found any meta-inf folder.
When downloading the rom in the official web be sure to download the one compatible with custom recoveries.
mustang_ssc said:
The problem is that you're not installing the TWRP flashable rom.
See that the zip file of the CM13 build you tried to install is called cm13......bacon-signed-fastboot......zip. So you're trying to install a fastboot rom with a custom recovery, instead of trying to install a custom rom for a custom recovery. That's why TWRP doesn't found any meta-inf folder.
When downloading the rom in the official web be sure to download the one compatible with custom recoveries.
Click to expand...
Click to collapse
Okay,Thanks. But when I tried another ROM (NucleaRom-V2.1.4-BETA[7.0]-bacon-20161011-0245.zip) ,I failed again. It occurred error 7. The TWRP is universal in many ROMs,right?I used to installed many with it successfully.However, I failed again and again this time.
SimonYJB said:
Okay,Thanks. But when I tried another ROM (NucleaRom-V2.1.4-BETA[7.0]-bacon-20161011-0245.zip) ,I failed again. It occurred error 7. The TWRP is universal in many ROMs,right?I used to installed many with it successfully.However, I failed again and again this time.
Click to expand...
Click to collapse
The 7 error use to happen when you get a bad download and there is missing data. You can compare the md5 of the rom to check if there are missing data or simply download it again, or try another rom.
Also i suggest you to use the latest TugaPower TWRP.
mustang_ssc said:
The 7 error use to happen when you get a bad download and there is missing data. You can compare the md5 of the rom to check if there are missing data or simply download it again, or try another rom.
Also i suggest you to use the latest TugaPower TWRP.
Click to expand...
Click to collapse
Actually,I'm using the latest TeamWin - TWRP. Here is the screenshot. I downloaded the cm13 official but it didn't work too. Could you give a guide to get a Tugapower TWRP? Maybe it will work with the TugaPower TWRP.
SimonYJB said:
Actually,I'm using the latest TeamWin - TWRP. Here is the screenshot. I downloaded the cm13 official but it didn't work too. Could you give a guide to get a Tugapower TWRP? Maybe it will work with the TugaPower TWRP.
Click to expand...
Click to collapse
Did you do wipes (system, data, cache and dalvik cache) before flashing the roms?
mustang_ssc said:
Did you do wipes (system, data, cache and dalvik cache) before flashing the roms?
Click to expand...
Click to collapse
yea,of course. This problem began at my last ROM(H2OS V2.0.1). Is it the main reason? Before that ROM ,everything goes well.
SimonYJB said:
yea,of course. This problem began at my last ROM(H2OS V2.0.1). Is it the main reason? Before that ROM ,everything goes well.
Click to expand...
Click to collapse
Well, honestly i don't know.
I would suggest you to check if the files you have downloaded are not corrupted in case the computer where you're downloading the roms is corrupt them, i experienced that case. So you can check md5 following this guide: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/113984-what-md5-how-use-verify-your-download.html
And the TWRP i suggested you is here: http://forum.xda-developers.com/oneplus-one/development/unofficial-twrp-3-0-x-tugapower-t3398366. You can install it though fastboot or try with the current recovery you have.
mustang_ssc said:
Well, honestly i don't know.
I would suggest you to check if the files you have downloaded are not corrupted in case the computer where you're downloading the roms is corrupt them, i experienced that case. So you can check md5 following this guide: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/113984-what-md5-how-use-verify-your-download.html
And the TWRP i suggested you is here: http://forum.xda-developers.com/oneplus-one/development/unofficial-twrp-3-0-x-tugapower-t3398366. You can install it though fastboot or try with the current recovery you have.
Click to expand...
Click to collapse
Thank you very much. I really appreciate it. I'll try as you say.Hope the issues can be solved.:good: