Ok peeps, completed S-off successfully and have Revolutionary CWM v4.0.1.4 as my recovery. Almost there and when I went to install su-2.3.6.3-efgh-signed.zip for ROOT, I received the following:
Installing: /sdcard/su-.3.6.2-efgh-signed.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/su-2.3.6.3-efgh-signed.zip
(bad)
Installation aborted.
Can anyone shed some light to my current situation? Thank you in advance.
I had the same thing happen the first time that I tried. I just retried and it we through the second time. If it doesn't work when you retry, try deleting it from your sd card, then redownloading it, and try it all over. you might have gotten an incomplete file
You have a good one you could send me in case that is the problem?
Sent from my PG86100 using XDA App
youre alright bro, just flash this one and you'll be all set...http://dl.dropbox.com/u/36719158/su-2.3.6.3-efgh-signed.zip
Odds are you had one that wasnt properly signed, youre 98% done!
Related
Ok, i have rooted my htc hero and im using the latest recovery 1.5.2. I am trying to flash a rom file but i keep getting the error message "E: cant open /sdcard/update.zip (bad)
As far as im aware i am doing everything right and i have tried it on two different sd cards but no luck, has anyone else come across this problem??
You help is much appreciated!!
karlconn said:
Ok, i have rooted my htc hero and im using the latest recovery 1.5.2. I am trying to flash a rom file but i keep getting the error message "E: cant open /sdcard/update.zip (bad)
As far as im aware i am doing everything right and i have tried it on two different sd cards but no luck, has anyone else come across this problem??
You help is much appreciated!!
Click to expand...
Click to collapse
i get this message for a corrupted zipfile. redownload, copy to zip and make sure you do a proper unmount on your pc.
okay i had Rom Manager installed on my HTC Eris because i liked how easy it was to use on my DROID. My first BRICK came while in Clockwork recovery for eris. I had an error saying something like E: boot.img failure or something to do with the boot image. i proceeded to fastbot and attempt to update with original PB000IMG.zip. system failed to write as well as boot. After powering down the phone(i received a brick) no recovery no power indicator
my second came also while using clockwork recovery.im not accusing clockwork recovery of bricking my phone ( im lying DO NOT USE CLOCKWORK RECOVERY) but i am letting you know i lost two phones using it.
this time this is the result after flashing.
--installing: sdcard:update 2.1.zip
finding update package...
opening update package...installing update..
Delete files..
delete files..
formatting system..
copying files...
E: cant symlink /system/bin/cat
E:Failure at line 11:
symlink toolbox SYSTEM:bin/cat
installation aborted
so if anyone has any brick experiences please add to this post your experience along with detail of your process to get there
im guessing no ones had this problem before?
Re: E: cant symlink
I had this problem on clock work recovery and wasn't able to fix it had to get a me new phone
-------------------------------------
Sent via the XDA Tapatalk App
ok thanks i think im going to just sell the phone instead of trying to fix it, my MOTO Droid will be here tommorow :.
did verizon attempt to fix or did you just accept it as a loss?
bigslanki said:
ok thanks i think im going to just sell the phone instead of trying to fix it, my MOTO Droid will be here tommorow :.
did verizon attempt to fix or did you just accept it as a loss?
Click to expand...
Click to collapse
well I tried flashing the root rom see if that would work, when I did the system and boot.img failed to get flashed so when it tried to reboot it never turned back on at all.
I called them told them it wouldn't turn on and they sent me a new one.
ok thanks i think im going to just sell the phone instead of trying to fix it, my MOTO Droid will be here tommorow :.
did verizon attempt to fix or
Click to expand...
Click to collapse
well I tried flashing the root rom see if that would work, when I did the system and boot.img failed to get flashed so when it tried to reboot it never turned back on at all.
I called them told them it wouldn't turn on and they sent me a new one.
Click to expand...
Click to collapse
Yep that's way happened with my first Eris. ... I'm on BACK TO Droid now as you can see. Going to limit my flashing for now on.
-------------------------------------
Sent via the XDA Tapatalk App
bigslanki said:
okay i had Rom Manager installed on my HTC Eris because i liked how easy it was to use on my DROID. My first BRICK came while in Clockwork recovery for eris. I had an error saying something like E: boot.img failure or something to do with the boot image. i proceeded to fastbot and attempt to update with original PB000IMG.zip. system failed to write as well as boot. After powering down the phone(i received a brick) no recovery no power indicator
my second came also while using clockwork recovery.im not accusing clockwork recovery of bricking my phone ( im lying DO NOT USE CLOCKWORK RECOVERY) but i am letting you know i lost two phones using it.
this time this is the result after flashing.
--installing: sdcard:update 2.1.zip
finding update package...
opening update package...installing update..
Delete files..
delete files..
formatting system..
copying files...
E: cant symlink /system/bin/cat
E:Failure at line 11:
symlink toolbox SYSTEM:bin/cat
installation aborted
so if anyone has any brick experiences please add to this post your experience along with detail of your process to get there
Click to expand...
Click to collapse
You over reacted
jetmclean said:
You over reacted
Click to expand...
Click to collapse
You bumped an old thread
jetmclean said:
You over reacted
Click to expand...
Click to collapse
how so? stating my experience and providing details for other users?
Old news......
EDIT: New problem I am using this root method:http://forum.xda-developers.com/showthread.php?t=1046855 However, no matter how many times I attempt to perform step 9, it keeps giving me the exclamation point. Any ideas?
The only way I could get root was to use super one click. Version 1.7 worked for me on two fascinates.
Sent from my SCH-I500 using XDA App
Were those two running 2.2.1? ED01?
I am pretty sure that with the latest kernals from stock you won't be able to get a root to stick.
No matter what after running any root method, you'd have reboot back to recovery and flash some kind of kernal in order for it to stick.
If you plan on putting a rom on your phone, just follow my stickied guide in this forum and flash that rom in place of the kangbang community rom I linked to... or just flash your kernal of choice to keep the stock experience with root.
Well, the problem that I'm having is that when I attempt to apply the "update.zip" file, I get a progress bar for a fraction of a second and then the exclamation point with the droid guy next to it.
I get this:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification failed
Installation aborted.
EDIT: Just realized the "update.zip" file was missing. But now I get this:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Looks like I wont figure it out today (too tired to think straight)
spartan.062 said:
Well, the problem that I'm having is that when I attempt to apply the "update.zip" file, I get a progress bar for a fraction of a second and then the exclamation point with the droid guy next to it.
I get this:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification failed
Installation aborted.
EDIT: Just realized the "update.zip" file was missing. But now I get this:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Looks like I wont figure it out today (too tired to think straight)
Click to expand...
Click to collapse
Sometimes I download multiple files at one time. For instance, to get the ED01 modem I downloaded the 2 update.zip's from adrynalyne's thread. The second update.zip had a "(2)" at the end of it. Erase that. On your PC the files needs to only say "update", not "update.zip". The phone adds a ".zip" to each file. Make sure you are doing that.
Sent from a depraved XDA junkie and flashaholic
superchunkwii said:
I am pretty sure that with the latest kernals from stock you won't be able to get a root to stick.
No matter what after running any root method, you'd have reboot back to recovery and flash some kind of kernal in order for it to stick.
If you plan on putting a rom on your phone, just follow my stickied guide in this forum and flash that rom in place of the kangbang community rom I linked to... or just flash your kernal of choice to keep the stock experience with root.
Click to expand...
Click to collapse
This isn't true. You are thinking about installing CWM recovery, that gets overwritten with the stock recovery by the stock kernels. I've used this method on many of the stock builds including ED01: http://forum.androidcentral.com/ver...d-post-1-before-posting-forum.html#post699944
I know of a VERY simple root method. If you want to know it, hit me back. It seems to me that no one is using it but it is posted in these forums.
Sent from a depraved XDA junkie and flashaholic
What method is that kidserious?
spartan.062 said:
Ok... Every time that I attempt the adb root, I get this in the command prompt:
'adb' is not recognized as an internal or external command, operable program or batch file
Click to expand...
Click to collapse
Are you on stock 2.2?
spartan.062 said:
What method is that kidserious?
Click to expand...
Click to collapse
Click on this and then once you are there download linked file. Then place it on your SD card. Let me know when you have done that.
http://forum.xda-developers.com/showthread.php?t=1045048
Yep. And I am still somewhat confused when it comes to flashing a kernel. And I already have the su file, however, when I try to apply the update to get to CWM, It won't take the update. I'll try adding .zip to the end of the name.
spartan.062 said:
Yep. And what was that method you were mentioning?
Click to expand...
Click to collapse
Yes, but I see you have had problems with this method already. Are you able to get odin properly set up on your PC? I mean have you been able to flash anything via odin? Did you see my link in my above post? And don't worry about a kernel just yet. Lets get this taken care of first.
Yeah, it said that it was successful. But the update.zip WILL NOT apply no matter what I do.
spartan.062 said:
Yeah, it said that it was successful. But the update.zip WILL NOT apply no matter what I do.
Click to expand...
Click to collapse
Did you see a Green "Pass" when it finished in odin? And when you put the battery back in were you unplugged first? You may know this but you cannot allow the phone to boot normally before booting into recovery. Try using this recovery instead: http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5
Flash that the same way in Odin?
spartan.062 said:
Flash that the same way in Odin?
Click to expand...
Click to collapse
Yes, but boot into recovery FIRST before the phone turns on normally. Not trying to sound condescending but do you understand what I am saying about booting into recovery first?
Yeah I understand. Ok I got the voodoo lady's voice. Now I have the red CWM menu.
spartan.062 said:
Yeah I understand.
Click to expand...
Click to collapse
The way it always works for me is I don't even boot into the blue recovery, it boots straight into red. Let me know what happens.
spartan.062 said:
Yeah I understand. Ok I got the voodoo lady's voice. Now I have the red CWM menu.
Click to expand...
Click to collapse
GOOD! With that menu find the superuser root package from nemesis2all on your SD card and install it. Let me know what happens.
Keep in mind that I'm brand new at this so please don't just say "do this ____" and expect me to know what you're talking about .
I finally was able to root my new fascinate and flashed CWM. The ROM installation guide says if you're already rooted with CWM installed to simply reboot into recovery, wipe everything and flash. Only problem is, when I boot into recovery I am getting this error message.
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Can anyone tell me step by step what I need to do to solve this? Also I was assuming the camera button would work as the 'OK' or 'enter' button but it does nothing. Is one of the soft buttons used along with the volume rocker to select choices in recovery? I have some experience hacking my og Droid but this fascinate stuff is all greek to me.
With the help of google I think I figured out what was wrong, needed to flash something from odin to get it to work beforehand.
http://www.mydroidworld.com/forums/fascinate/4786-how-flash-clockwork-recovery-fascinate.html
Rebooting now, will let you all know if it worked.
I have definitely messed something up.. after flashing CWMRecovery.tar (used PDA, not phone) my phone just stays in a bootloop now. I can get into stock recovery but reboot now and the apply option do nothing but throw out error messages. I'm pretty sure it's hosed so I'm going through the steps to flash it through odin back to stock. Can anyone explain to me what exactly I did wrong here?
It may help if you give details... what rom did you flash? What kernel? This could help us help you.
Sent from my SCH-I500 using XDA App
Shakes The AssClown said:
It may help if you give details... what rom did you flash? What kernel? This could help us help you.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I second this, from previous personal experiences with this it sounds like something has gone wrong with your odin/flashing or you may be using old/outdated/corrupt files.. if you could tell us what you are odin-ing/flashing and exactly how you're doing it we can give you specific answers
tapatalked from my KangBanged Fascinate
followed the root step by step. I have S-off, and SU installed... but when i go to install certain roms, I get this.
--install / sdcard ...
finding update package..
opening update package...
E:cant open /tmp/sideload/package.zip
(bad)
not sure whats up with that, someone said its cause I dont have SU, but I followed the root process exact, so what else does this mean? and how can I get other these roms to work -
this rom is Viper 1.2
Did you flash a su zip?
Sent from my PG86100 using XDA Premium App
Try the latest twrp 1.0.2 I had the same problem as you, and I redid the recovery tonight, and the problem is gone, for me, at least on the one rom I flashed tonight. I tried cwm yesterday and got an error with that recovery too, but it was a different error, but I am sure it meant the same thing.
Another way around it is to just do a reboot. Your system wont be there so reboot into bootloader and go back into recovery. This worked yesterday for me....
yes neopolotin75 , I did flash the SU file, signed and unsigned....
and yes B-Mod, got 1.0.2 installed, and also again did the signed and unsigned, wiped everything, formatted everything, and still no go....
not sure what the heck. maybe take my phone back to stock, and start over...
thanks anyhow...
disconnect the cable from the phone.....
FIGURED IT OUT - i got my file from mega upload, 2 times..... along with some of the other roms, and they always gave that error...
I now got viper 1.2 from hostfile. it is installing, after comparing the files, mega upload said it was good, but was missing about 2 megs of data.
hope this will help anyone else who gets this error, just try different sites for your roms as they seem to be getting hit hard with lots of downloads.
I had the same issue. If you re-apply the ZIP a second time it works without an error message.
goodluck69 said:
I had the same issue. If you re-apply the ZIP a second time it works without an error message.
Click to expand...
Click to collapse
Sometimes. If it's a status 0, 1, or 2 that is usually accurate. Just reboot back into recovery and it works. But if it says "bad", the .zip is corrupt and it needs to be redownloaded.