I'm trying to flash gingertazz and recovery said cannot open file(bad) I removed android secure folder with supermanager and did a nand backup. When I went to flash rom I get the error. I placed the rom and gapps in SD card. I have never had issues flashing rom's before! What did I do wrong?
It could just be a bad download. I would suggest downloading from a different file host than the one you used previously. Then try flashing again and see if it works this time.
I went and downloaded it from Hotfile and the MD5sum I'm getting is:
1041c8ad2b4cdddf4845e79bc9efa0f2
Does that match yours? I haven't tried flashing it since I'm working on some things but if yours is different, then one of us has a corrupted file.
That worked thanks! To bad its pretty much the same rom that I had already
Related
So excuse me in advanced and I've been searching pretty extensively to no avail.
I have an HD2 and a samsung vibrant, I've rooted the vibrant using one click root. I put on ROM manager and downloaded eugenes eclair build, put the vibrant9.zip on the micro SD card and went into rom manager to install it, it then says "no such file or directory" and then eventually does nothing. I've tried flashing other builds and also tried flashing the stock kernel, all with the same results.
I know I'm just missing something stupid, and apologize if its painfully obvious. I just need a couple you genuises to help me fix it
tl;dr rooted phone wont flash rom "no such file or directory..." ?
You need to put the file on the phones internal storage not the sdcard.
If you put spaces in the name of your backup file in ROM Manager you will get a Md5sum error when restoring your backup.
To fix, boot back into your current ROM and using Root Explorer or an equivalent file manager, remove the spaces and try again under recovery. Should work now, unless you truly have a corrupted file....
Also I do not recommend Rom Manager on the SGS2. A lot of people complain about bad backups and problems with flashing or restoring!
There have been problems with some roms and Rom Manager because the CWM recovery that Rom Monager "flashes" is not a real recovery. It is only an update.zip file placed on the internal SD card of the phone. The real CWM is the one that is combined with your kernal.
However, for those flashing CM7 nightlies, it is still a useful tool as it makes downloading and flashing new updates almost a one click and fool proof exercise. Importantly, Rom Manager makes sure that the files (including restoring your backups) are not corrupted or incomplete through the MD5sum check. Not sure if real CWM kernals do the same so I like to use Rom Manager to make sure nothing goes wrong.
For those having difficulty booting into proper recovery from Rom Manager, there is a free app called Quick Reboot which works well.
Sorry but I need some help. When upgrading roms a few times, no problems ever occurred. CWM always worked smoothly. Now, I have the Resurrection Remix 1.0 Pro installed and was attempting to upgrade to Resurrection Remix 1.2 AOKP. I see that when running CWM I only had to choice to access the "download" folder on the scard. When attempting to install the Remix 1.2 rom, I always end up with an e signature fail. I tried several times but had the same results. I had to reboot and stay with Remix 1.0 until someone can help me get the upgraded rom installed. I wiped all the data and reset, and don't know what else to do.
Please help!!
OK, not sure the procedure you made... but might also be that some files you got were corrupted. Check to see they all are fine before going ahead with this way to install:
Do a full wipe(factory reset+cache+dalvik cache)
Install the Main ROM
Install Siyah-v3.0.1-CWM.zip
Reboot
Do the initial setup of things
Go back to CWM and install navigation button fix
Reboot
Then go back to CWM and install app themes (there are some bugs, but if you want the black themes, then install classic first, then black)
Reboot
Some people have other issues after, but see how this goes.
I would change the DPI settings to 184 or 210 for everything to work fine from market apps.
*if have more problems, just reply here.
Is the file on an external SD?
It's wherever you put it, though some files will only flash properly from external SD.
I think it's the internal sd
felixg123 said:
Is the file on an external SD?
Click to expand...
Click to collapse
At first I thought I had the files on the external sd card, but when rebooting in recovery with CWM it looked like it was only allowing me to access the download folder on the internal sd card.
Thanks for any suggestions.
cyberboob said:
It's wherever you put it, though some files will only flash properly from external SD.
Click to expand...
Click to collapse
The CWM that came with the remix 1.0 pro rom is that weird one that seems to have to boot from the other little app. Do you recall this is the CWM zip file that was added to the files to download for the remix 1.0 pro rom. It doesn't appear to have the same flexibility that the CWM had that came with my previously used rom...remix 9.4
Any comments??
With 1.0 its 3e (stock recovery) so you have to put cwm.zip in your external SD or your cache then flash it through 3e. Now you have cwm. If its the one from westcrip its touch so don't use the volume buttons.. actually touch the screen.
Hopefully that helps.
Sent from my GT-I9100 using XDA
Does the same thing... but it's a touch version.
There is a newer 1.3 version out now for Resurrection Remix with far simpler installing procedure... and people have reported most bugs fixed now (maybe a couple remain to be found).
cyberboob said:
Does the same thing... but it's a touch version.
There is a newer 1.3 version out now for Resurrection Remix with far simpler installing procedure... and people have reported most bugs fixed now (maybe a couple remain to be found).
Click to expand...
Click to collapse
Now, I'm really scratching my head. When I try installing the 1.3 rom it begins ....but returns this message and then aborts.
E: failed to verify whole-life signature
E: signature verification failed
I re downloaded the rom 1.3 to make sure it wasn't corrupt, and it did the same thing. Then I downloaded remix 1.2 just to see if this would install properly. I got the same result with the failed signature coming up in red and then it aborts. So something is not allowing me to change roms?? At present I have remix 1.0 installed.
Please I need some assistance figuring this out. I don't know what to do now?
Thanks in advance
Check if your current rom is having any beta releases of siyah 3.0, if so then it would be the cause, download cf root, or any latest version of custom kernel in tar format and flash it via Odin, now enter cwm and flash the new rom, you would be good to go
#*posted on the move *#
Works fine ....but is there a GPS problem?
I got the darn thing installed. Thanks. I was able to install the CWM......one that worked properly and the remix 1.3 got installed without a hitch. One problem I'm noticing the the GPS taking a whole bunch of time trying to locate sats. Is there is gps fix ??
Thanks
go to the Emergency FAQ for 1.3 (in my sig)
Hello!
I am currently using The Collective's Seraphim Mesosphere Kang build from the thread in Development from a few weeks ago. The current build is called "Remix", I've downloaded it and installed it via CWM recovery just like I did for my old version, wiped all data and caches, but when I go to install the .zip from sdcard, it fails when opening and aborts installation.
I've tried this twice, once downloading the zip over WiFi and once over 3g in case the zip got corrupted and neither works. The moment it tries to open, it fails.
What am I missing here? Is there and issue with the ROM/zip? Should I try transferring the zip via cable instead of downloading it wirelessly?
Thanks!
Astriaal said:
Hello!
I am currently using The Collective's Seraphim Mesosphere Kang build from the thread in Development from a few weeks ago. The current build is called "Remix", I've downloaded it and installed it via CWM recovery just like I did for my old version, wiped all data and caches, but when I go to install the .zip from sdcard, it fails when opening and aborts installation.
I've tried this twice, once downloading the zip over WiFi and once over 3g in case the zip got corrupted and neither works. The moment it tries to open, it fails.
What am I missing here? Is there and issue with the ROM/zip? Should I try transferring the zip via cable instead of downloading it wirelessly?
Thanks!
Click to expand...
Click to collapse
That's what I would try...sound's like a corrupt file...I have flashed over and over and no problem...if you have the file on your PC...just for a test...unzip it to a folder with 7zip or whatever you use...usually this will tell you if a file or a folder in the zip is corrupt...if it test good, try using your cable to transfer...good luck!
Sent from my Note running Seraphim Remix Green Edition
Astriaal said:
Hello!
I am currently using The Collective's Seraphim Mesosphere Kang build from the thread in Development from a few weeks ago. The current build is called "Remix", I've downloaded it and installed it via CWM recovery just like I did for my old version, wiped all data and caches, but when I go to install the .zip from sdcard, it fails when opening and aborts installation.
I've tried this twice, once downloading the zip over WiFi and once over 3g in case the zip got corrupted and neither works. The moment it tries to open, it fails.
What am I missing here? Is there and issue with the ROM/zip? Should I try transferring the zip via cable instead of downloading it wirelessly?
Thanks!
Click to expand...
Click to collapse
as mentioned, sounds like possibly a corrupt file
i would download on wifi, then transfer by cable
actually, i would do the md5 hash check to make sure the file is unaltered before transferring
Looks like you guys were right! I downloaded it onto my computer first, then transferred via cable, and it installed totally fine.
The weird thing is that I downloaded the Remix .zip from the same wireless AP, for both the computer and directly onto the phone. Yet only the one on the computer actually worked.
I'm not sure if it was just unlucky and downloaded directly to the phone caused dropped packets/corrupted the data and the computer simply has a better connection or what.
In any case - glad I'm all sorted and up to do now!
Thanks!
After upgrade from 2.5 to 2.6 twrp i seemed to have lost my backups from my sd card.
after install 2.6 through Goo (which seemed to go fine) and wanted to restore a backup which worked fine in 2.5....twrp sees nothing anymore.
I had to unbrick, it seemed after the bootloop i got after the install of 2.6...recovered from that but now no backup seen by twrp.
Rom manager sees the backup files but won't restore them cuz it's missing the MD5....
Is there a way to go back to 2.5 twrp?
I seriously searched for this problem for almost a full day now and gave up....
Any suggestions will be soooo welcome!
Thank you, but keep in mind please that i'm not a developer...just a (somewhat ignorant maybe?) user..
ps: all this cuz i saw update to 4.3 from verizon and it wouldn't let me update. Then i saw the advice on here to never uta and flash a rom which i really would like to do but i have not tried to flash any rom yet, which, if possible solves all my problems...heh.
in twrp i tried all within my brainpower, like MD5 verify uncheck, mount...you name it...lost now..
solved!
Taa Daaaa..solved.
Copied backup file with explorer to root of Twrp/backup folder and it took now.....
Quite strange but i'm not complaining..
I'll leave this question up for now so others who may have experienced same problem can try this.
Restore works again so now i can start fiddling with Roms...lol...almost seems like looking for trouble, doesn't it?