I have sat at my table for 3 hours trying to get this set up right. I rooted my phone (at least i think so) through super one click. I rebooted as rageagainstthecage. Everything went fine for that, my phone was instantly faster.
Then when i installed ROM Manager Premium, i went searching for a cool ROM, i came across a Bionix ROM. I transfered files like xda told me to and whenever i got to reboot and install them it just tells me this:
E: Can't Open/cache/recovery/command
--Install from sdcard--
Finding update package
Opening update package
Verifying update package
E:signature verification failed
Installation aborted.
Can anybody tell me what i did wrong? I am a huge noob so I might not know all of the terms with this process. Any help would be greatly appreciated.
bro u r not doing anything wrong....here try these methods
http://forum.xda-developers.com/showthread.php?t=1052991
Related
Hi all, I have a problem that I am struggling to find an answer for.
When ever I try to do a back up using ROM Manager I get :-
opening update package...
verifying update package...
E:failed to verify whole-life signature
E: signature verification failed
Installation aborted
When I first got my phone I rushed into rooting it and flashing it without really knowing in my head what I was doing but just following instructions off the net. The rom I installed was :-
lite'ning rom v6.1 xxkh3
I also installed kernal '2.6.35.11-ninphetamine-2.0.5+ [email protected]#', as I believe this was the correct one at the time.
My baseband version is 'I9100xxkh3' (If needed)
From the research I have done I think it is the kernel that is causing the problem as I have read you need a compatible cwm kernel and I'm guessing this isn't???
I'm wanting to flash a newer ROM now but as I'm more clued up(but even more confused) I want to create a back up first but as I can't I'm stuck with this ROM.
Can any one help me here regards what kernel I need? If that is the suspected problem??
Thanks
Mark
Your rom manager is causing a lot of problems as most roms do not work very well with it.
If you are rooted you can use cwm to make a back up.
the kernal is not causing the problem as you can mix and match kernal with out any problems.
Stop using rom manager, just boot into recovery if you want to install/backup roms and wipe phone.
^^ +100
I've only used Rom Manager twice. First time to to a backup, broke pretty much everything. No recovery & bootloop. Obvious incompatibility issue at the time between it & CW Recovery. Until recently was doing everything thru recovery. Tried flashing a kernel this week thru Rom Manager again & it worked just fine.
Obviously you're having problems with it, so rather than tempt fate, I'd stick with Peachpuff's most excellent suggestion of doing everything thru recovery rather than risk causing yourself unnecessary grief.
Thanks cosmic blue!!
Followed your instructions and worked first time.
I confirmed this by going into rom manager and it now shows a back up.
I always thought Rom manager and cwm was the same thing but now I know.
Is Rom manager still something worth installing though? Or is it just a reliability?
Thanks again all those that helped.
Mark
I would uninstall RM & just use CWM, as suggested earlier. You might want to install Mobile Odin (Market), in case at some point you need to flash another kernel that includes CWM.
Sent by Tapatalk from my rotary phone, using sparks.
Your welcome
Rom manager is not worth installing as there are other ways of doing the same functions of rom manager.
using cwm, titantium back up and root explorer will do the same job as a rom manager.
titantiuam baclk up and root explorer are free apps on the market there are also paid versions of the apps which are upgrades.
try the free versions, if you like them then buy the pro versions.
Hello everyone, just got a handme down Samsung Galaxy S Vibrant (STOCK with 2.2 froydo). I was able to root no problem and then decided to try out a custome Rom. So after some research i went with DarkyRom 10.2 (the last version on their site). Got rom manager and did everything that is was suppose to but when rebooting i get this:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
WHY? It will not go into Clockwork Mod Recovery. So after hours of failed attempts and research online including going into /system folder and replacing restore file... nada. Then i flashed to 2.1 via suggestion from YouTube and then find out Rom Manager isn't available for 2.1. So i use kies to flash back to stock and here i am at square 1 again. I would greatly appreicate an answer to why this is happening or suggestions around it because that t-moblie song when then phone turns on and off are killing me. Thank you for your time
Step 1 - uninstall Kies. It will do more harm than good.
Step 2 - The Darky ROM from their website is for I9000 phones - not the T959 Vibrant. You should have flashed a port of the Darky ROM.
If you can get into Download mode I would try to set the phone to stock with repartition checked - Stock 2.1 (JFD) or try Stock 2.2 (KB5).
Here is the link for the KB5 Stock:
http://forum.xda-developers.com/showthread.php?t=1674519
Ive used the 1-click Heimdall twice now and it worked fine.
or try the AIO Toolbox:
http://forum.xda-developers.com/showthread.php?t=954509
I'm shy on sleep but you may want look into Eugene's Froyo that does not brick - YouTube may also have a video if going back to stock JFD or KB5 doesnt work.
Thank you VERY much...
Will be testing out her shortly. Sir you are a gentleman and a scholar
Everything is working great now!! I ended up using Odin with the 512.pit and the UVKB5_Deodexed_Stock_Voodoo_odin.tar.md5 provided.. boots into clock work recovery mode and Rom Manager working GREAT!! Thanks again sir!
I'm very sorry if this isn't in the right spot. I've looked around a bit, and used the search engine, and I haven't been able to find anywhere that I think this belongs. Anyway, here's my problem.
Ok, so here's what happened. I was looking at my build.prop settings in rom toolbox. Out of curiosity, I changed lcd density from 240 to 160 just to see what it would look like. I planned on changing it right back immediately but Touchwiz kept force closing.
I then tried restoring my phone back to factory, but my recovery no longer works. I know how important it is to give as much detail as possible so here's the ENTIRE output from after rebooting into recovery, clearing user data, clearing cache, and then reinstall packages...
#MANUAL MODE#
--Applying Multi-CSC
Installing Multi-CSC
--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
I had previously tried installing ClockworkMod Recovery ( through Rom Manager ) and thought it had failed because when I rebooted, it took me into the stock Samsung Recovery Utilities. Now I'm thinking that it may not have actually failed, and that I had to select 'reinstall packages' and that would have finished the ClockworkMod recovery install. I'm now thinking that the failure to verify whole-file signature is happening because I no longer have root due to clearing user data, and clearing cache. I may be wrong, idk.
I know how to reset the build.prop lcd density setting to fix that issue, but I have to wait for my aunt to get her computer back to root again. She's currently having it fixed, and I have no other access to a computer.
What I'm asking for help with is to either get my recovery utilities to be functional again in case I ever need to do a hard reset, or get ClockworkMod installed. Whatever is safer is the route I want to go.
I'm kind of thinking that ClockworkMod not fully installing itself is stopping the recovery from functioning like normal. The reason I think that is because I've restored my phone to factory stock many times. The sdcard was NOT in the phone those times and now it's trying to use 'update.zip' from the root of the sdcard when I select reinsall packages. Kind of like ClockworkMod recovery is partially installed, enough to try to use itself instead of the stock recovery, but not enough to be a working recovery.
As I said above, I'd really like to have a working recovery on this phone. I'm actually homeless at the moment, and I have absolutely no money to buy a new phone. Shiiit, I have to bum money from customers at a shopping center every single time I want to eat even. This phone is basically the only thing that keeps me sane. Being homeless is REALLY, REALLY boring as you can imagine. This phone makes it much more tolerable.
Sorry for the length of the post. If there's any other details that may aid in fixing this, let me know and I'll post them. I'm pretty sure I've provided all the detail possible though.
Ok, I typed that up while I was away from wifi, and decided to do a little more research before posting. I'm seeing that I was right about the ClockworkMod recovery not being fully installed. I didn't do the last step of rebooting and then reinstalling packages originally. Now. I'm wondering if the signature verification is failing because I no longer have root access or if it's something else. If that's it, I'm going to finish the installation once my aunt gets her computer back unless there's some way I can get it to reverse the partial ClockworkMod install.
Again, I'm sorry if this is in the wrong place, and for the length. Thanks in advance for any help you can provide.
Let me just start out by saying I'm a nube with limited skills. I have a Samsung Showcase SCH-S950C for Straightalk. I was sitting around on saturday and decided I would figure out how to root my phone because I had nothing better to do. I followed the instructions in a forum on this site and was able to root with no issues. After that I of course then decided to try my hand in flashing a custom rom to the phone (cyanogenmod) and this is where i went wrong. After flashing the rom I booted the phone and now the rom won't load and is stuck saying, "Unfortunately, setup wizard had stopped" and "Unfortunately, the process android.process.acore has stopped." The only menu I can get into is the sound menue via the volume key.
The next step I took was to reboot the phone back into CWM to see what I could do. Upon loading I was faced with the below errors.
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Tried wiping the cache, factory reset and wiping dalvik and am unable to do so. It won't mount the cache, data or datadata. I then tried to put it back to stock via instructions for flashing a recovery mod for the phone and that did not take because I cant wipe it. From what I read i need to repartition the phone to fix this issue but I do not know how and honestly not even sure exactly what that means. As I said to start Im a nube. I also noticed in USB mode it says i now have 4 custom binarys on the phone and Im sure that is not helping things.
This is the point I stopped so as not to completely FUBAR the phone, if I have not already done so. If anyone can point me in the write direction on how to proceed I would greatly appreciate the help.
Look for odin and some related rom of your phone. Flash again. Normally problem would be fixed.
Sent from my XT901 using xda app-developers app
Probably non-useful information
I know nothing about the Showcase, so please accept this information for instructional purposes only.
I had zero experience with anything Android related until September. I successfully used old flip style or otherwise non-smart phones, so never had any experience with any version of Android (or any iOS either for that matter). My brother-in-law had given my parents a Fascinate that he replaced with a Note. It sat around their house until I picked it up and decided to see what I could do with it. I found this guide to be exceptionally helpful:
http://forum.xda-developers.com/showthread.php?t=1238070
Whereas I don't know if any of this information is relevant to your Showcase, the operational theory may relate. The phone that I was given was already rooted so I used the instructions in the guide to use Odin to return the phone to stock, then update to a Jellybean ROM. I learned a great deal working through the process a couple times, and have since been given a first gen Kindle Fire, an LG Ally, and a Droid Charge that I had enough confidence to work with, and successfully rooted and flashed each.
I have rooted the phone and every time I go to install aokp or another rom to see if it works, I always get e: signature verification failure. I have read post and followed tutorials from this forum with no luck. I followed this post http://forum.xda-developers.com/showthread.php?t=1739426%20. The rogers file fails but the at&t one will install. It still fails when I try to put an os on the phone. It was not backed up so I can't even get it back to a point where I can use it right now. Its been 4 hours now and any suggestion on how to fix this would greatly be appreciated. Samsung S3 with Rogers.