i downgraded from a custom rom(maxicetdroid 1.3) to stock 351 and i was successful. but i m having some problems. the market is the old version and is not updating. i tried to install an .apk file that i downloaded from the internet. but when i try and install it it just shows 'installing' on the screen and it doesnot install. did a factory reset as well but of no use. i m also not able to install anything from the market.
can anyone please help..
thnx...
If your recovery is still stock, download the 360 update package from the wiki and install it. It sounds as if your installation is messed up.
Strephon Alkhalikoi said:
If your recovery is still stock, download the 360 update package from the wiki and install it. It sounds as if your installation is messed up.
Click to expand...
Click to collapse
okay.. thnx... i ll try doing that..
Related
Hello - I'm new to clockwork. I am running Eugene's Ginger Clone ROM, rooted, and undid OCLF.
I downloaded ROM manager from the Market and installed. I noticed I now have an update.zip file on the internal SD. I rebooted into recovery - but when I click reinstall packages, I get this error:
Finding Update Package
Opening Update Package
Verifying Update Package
E: failed to verify whole-file signature
E: signature verification failed
Installation Aborted
What am I doing wrong? I am DYING to get Nero v2 flashed!
Any help is much appreciated!!
Thanks,
fF
on ROM MANAGER did you press FLASH CLOCK WORK RECOVERY? its the first option. YOU MUST HAVE THAT.
if it still doesn't work, on TITANIUM BACKUP, press menu, and click CREATE UPDATE.ZIP and it'll re-do it, but u'll need to re-flash clockwork recovery.
xriderx66 said:
on ROM MANAGER did you press FLASH CLOCK WORK RECOVERY? its the first option. YOU MUST HAVE THAT.
if it still doesn't work, on TITANIUM BACKUP, press menu, and click CREATE UPDATE.ZIP and it'll re-do it, but u'll need to re-flash clockwork recovery.
Click to expand...
Click to collapse
I did Flash Clockwork before the error as Galaxy S Vibrant. I flashed again same error.
I went ti Titanium, created update.zip and reflashed clockwork. Still getting the same error.
Any other ideas - or can I get an update.zip that's known working?
Thanks!
fF
try re-downloading the ROM and try again..
funkyfungus said:
I did Flash Clockwork before the error as Galaxy S Vibrant. I flashed again same error.
I went ti Titanium, created update.zip and reflashed clockwork. Still getting the same error.
Any other ideas - or can I get an update.zip that's known working?
Thanks!
fF
Click to expand...
Click to collapse
IDK how to fix this besides ODIN back to stock, and then re-flash it.
I SUGGEST you just do odin because it'll erase everything and it might be a small bug in your system doing this.
I even tried older versions of clockwork. I don't think redownloading the ROM would help because I can't even get CW to start.
Strange damn thing.
I guess I'll odin back to stock.
Thanks
funkyfungus said:
I even tried older versions of clockwork. I don't think redownloading the ROM would help because I can't even get CW to start.
Strange damn thing.
I guess I'll odin back to stock.
Thanks
Click to expand...
Click to collapse
yeah it happens sometimes, and you need to ODIN once in a while so your ROMS ghosts don't stay back and haunt your newer roms.
Good Luck on it working.
Odin'ed back and had to reset phone. Bone stock and re-installed Clockwork. Did the reinstall packages and it rebooted this time and looks hung on Installing Multi-CSC. I guess that takes a while? Babysitting...
fF
same here
Yes I'm having the exact same problem. I'm running nero beta 3 and I'm getting the can't verify signature error with clockwork. I've read elsewhere that this has something to do with having 3E recovery vs. 2E recovery, but I'm not entirely sure what that means. It sounds like we need to Odin back to a stock version to fix this problem, but can anyone tell us which one? Can someone provide a stock version that has the CWM with 2E? Or a better solution? It would be much appreciated, and thanks to funky for starting this thread.
I odin'ed back to T959UVJFD.tar
That wasn't enough so I wiped all user data via recovery mode. Re-installed Rom Manager - and now I'm on Nero v2.
I figured out the Installing Multi-CSC issue by reinstalling packages again.
Some things just take time I guess.
Thanks for the help guys!
fF
Moved of: Samsung Vibrant > Vibrant General
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
i tried to install with clockwork the gharmony 2.2 mod but i got a weird error about some file that couldnt be installed and now i cant boot and im stuck in the gtablet boot screen! i made a recovery image prior but i dont know how to use it. can ayneone help me out?
update - i am restoring it from the recovery image. however, to install the new ROM, i tried using this guide
http://forum.xda-developers.com/showthread.php?t=865245
the tnt gharmony was obtained from
http://www.slatedroid.com/topic/15441-rom-g-harmony-gingerbread-233-with-honeycomb-elementsupdated-46-g-tabletzpad-t2/
i got some weird error i dont remember the name of. does anyone have any suggestions? it was like error 3 and some system file didnt install or something?
thanks so much
Sounds like time for an nvflash.
http://forum.xda-developers.com/showthread.php?t=861950
Then get clockwork back on it and restore your image (if it works). If not, you'll be back to stock and can then go install a rom.
thanks for the quick response to my post - but check out the update that i just figured out
update - i am restoring it from the recovery image. however, to install the new ROM, i tried using this guide
http://forum.xda-developers.com/showthread.php?t=865245
the tnt gharmony was obtained from
http://www.slatedroid.com/topic/154...honeycomb-elementsupdated-46-g-tabletzpad-t2/
i got some weird error i dont remember the name of. does anyone have any suggestions? it was like error 3 and some system file didnt install or something?
thanks so much
anyone have any insight on the gharmony install error?
Ask the dev of the rom
I have tried to Root my Vibrant on the UVKB5 update for a while now.
One Touch Root, says "no space on device", yet declares the phone rooted (su commands do not work).
Applications that require root, though, do work the su binary is always outdated and cannot be updated because "cannot find installed su binary".
This was found when I tried to boot into Clockwork Mod but only ended up in recovery mode - I downloaded the e3 fix that told me "the system cannot find the path specified. temp root failed! install cannot continue." All Try agains and Reboot and Try Agains result in the same answer.
I don't want to go back to JFD because I've done it before with a CyanogenMod with SGSII and everything crashed.
But if I did go to JFD, could I install CyanogenMod 7 the same? (the instructions assume I have the UVKB5 update)
Help.... please?!
Thanks!
i believe CM is like miui...as in the way of flashing it on the vibrant. u can either flash it from eclair 2.1 or froyo 2.2. as long as u can boot into recovery. but if u flash it from 2.1 u might have to pull out the battery then reflash from the new recovery since it bootloops...hope that helps.. i actually read how to install it..have u tried flashing project v which is a uvkb5?? then CM??that could be an easier way since project v is already rooted.
Sent from my Vibrant
I kinda wanna just install cyanogenmod...
all u have to do is this
1) root
2) install rom manager (free) from market
3) install cwm from rom manager
4) click reboot in recovery from rom manager(it will ask for root access)
5) reinstall package(u may have to repeat this step twice
6) put a custom rom of ur choice CM7 or miui
7) install it ....THAT'S IT....
deziguy420 said:
all u have to do is this
1) root
2) install rom manager (free) from market
3) install cwm from rom manager
4) click reboot in recovery from rom manager(it will ask for root access)
5) reinstall package(u may have to repeat this step twice
6) put a custom rom of ur choice CM7 or miui
7) install it ....THAT'S IT....
Click to expand...
Click to collapse
Did you even read my original post.
My phone is only half rooted. Clockwork won't open and the e3 fix can't find root.
I know what to do, I was reading the instructions.
Have you tried to update your Superuser app in the market? If you download it and install the update you might get a parse error or something that says it can't update the binaries. Scroll down in the market link for Superuser and there is an Update Fixer. Install and run that and then rerun/update the Superuser app.
Sounds like your binaries are out of date. This shoud fix it. Might also want to go to settings>manage apps>Superuser and clear cache/data. Once you update the SU, you'll have to re-grant permission anyways so clearing data shouldn't be an issue.
If that fails try to re-root is with Option A here http://forum.xda-developers.com/showthread.php?t=849028 There are two options here. Choose before you start.
A: Download this update.zip file to root your phone. You plan to install Rom Manager to flash CWR and a new ROM later.
Woodrube said:
Have you tried to update your Superuser app in the market? If you download it and install the update you might get a parse error or something that says it can't update the binaries. Scroll down in the market link for Superuser and there is an Update Fixer. Install and run that and then rerun/update the Superuser app.
Sounds like your binaries are out of date. This shoud fix it. Might also want to go to settings>manage apps>Superuser and clear cache/data. Once you update the SU, you'll have to re-grant permission anyways so clearing data shouldn't be an issue.
If that fails try to re-root is with Option A here http://forum.xda-developers.com/showthread.php?t=849028 There are two options here. Choose before you start.
A: Download this update.zip file to root your phone. You plan to install Rom Manager to flash CWR and a new ROM later.
Click to expand...
Click to collapse
That is not the problem. Installed Update Fixer. Signatures are "OK!". Force, just force closes the app.
A: I can't flash through CWR, as mentioned in my OP.
Looks like I'm going to have to start over again and just ODIN through this..
savbers said:
Applications that require root, though, do work the su binary is always outdated and cannot be updated because "cannot find installed su binary
Click to expand...
Click to collapse
I did read your OP and it says this. If you update your SU then the binaries will update too with the fixer. The you can download CWR from the market, reinstall it, grant SU permission and flash away. Try going into settings>manage apps>superuser and clear cache/data. If you are only half rooted as you say, then first thing to do us get full root back, eh? Good luck.
Woodrube said:
I did read your OP and it says this. If you update your SU then the binaries will update too with the fixer. The you can download CWR from the market, reinstall it, grant SU permission and flash away. Try going into settings>manage apps>superuser and clear cache/data. If you are only half rooted as you say, then first thing to do us get full root back, eh? Good luck.
Click to expand...
Click to collapse
Thanks for all the help, but in the end I did man up and went back to stock JFD and now Cyanogen mod runs amazingly. And the MMS that didn't use to work on my phone -does!
Google Apps didn't install properly and I had to re-install the rom 'cause i was impatient.
Love it now though... and google thinks I have a nexus s. ^^
I have Galaxy note 1 i717D from Telus canada. it was giving me some troubles so i decided to download stock firmware from this link
http://androidromupdate.com/2013/05...elly-bean-upgrade-on-telus-galaxy-note-i717d/
Everything went okay but after restart its showing me these errors
https://share.htc.com/3mq2dJEj7
Could anybody please let me know what is this and how can i go from here. I tried wipe device, wipe cache but all are coming back with red error lines.
I took out the battery to restart it its showing me android sign with ball spinning in its tummy
Thanks
Update your recovery to TWRP 2.5.
rangercaptain said:
Update your recovery to TWRP 2.5.
Click to expand...
Click to collapse
Could you please let me know how can i do this, I am trying to find it myself too but if anycase you have tried please let me know, Do i need to do it even when I am trying to do stock recovery ?
I don't see what installing TWRP 2.5 has anything to do with this install. OP is installing stock ROM with odin which means stock recovery.
You should be using Odin to do the install as instructed in the link. I don't understand why the stock recovery is even showing after a restart or why the you would toggle it after a flash.
Agoattamer said:
I don't see what installing TWRP 2.5 has anything to do with this install. OP is installing stock ROM with odin which means stock recovery.
Click to expand...
Click to collapse
Let me draw you a picture. Flash TWRP with Odin. Let it root the phone. Use TWRP to flash the rom, stock or custom.
Installing stock anything doesn't mean stock recovery. Odin is used when phone is in download mode.
But the ROM he is flashing is a stock.tar. That can only be flashed with odin. Custom recovery has nothing to do with it and will not help him achieve what he is wanting to do. OP has even mentioned he wants stock recovery. What he is doing in stock recovery after flashing the ROM with Odin has me baffled.
I don't know why "Install TWRP" is the answer to all problems on this forum. Running the updated CWM has suited me just fine and has been able to flash any ROM I wanted to try.
Update: It works fine if you update twrp before flashing your ROM.
artrex654 said:
I have rooted my phone using stumproot and have also installed Illusion custom rom... However I cant install Gapps. Every time I try it fails in status 7. I dont know what that means or what to do although I've tried 3 different Gapps packages. If anyone can help before I decide to flash back to stock that would be great.
Click to expand...
Click to collapse
do you have the newest twrp installed? shouldnt matter, i used to run illusion off 2.8.0, but its the only thing i can think of.
TWRP crashes when I install it