[Q] Rooting Vibrant after using Kies Mini Update - Vibrant Q&A, Help & Troubleshooting

I apologize in advance if I have missed a solution to my problem in the forums.
My phone was rooted prior to using Kies Mini to update my Vibrant.
After I updated my phone using Kies Mini I noticed that I could not use Titanium Backup. I then booted the phone into recovery mode and selected reinstall packages. The update.zip was placed in the root directory. I received an error message that stated the file could not be used because it was not signed.
I did some research & found that I needed to install /use 3e recovery update. After installing 3e recovery update, reinstall packages completed without any error messages. I then tried to run Titanium BackUp & BusyBox Installer and received a message that stated the program could not be run because the phone was not rooted.
Model number: SGH-T959
Firmware version:2.2
Baseband version: T959UVKB5
Kernel version: 2.6.32.9
Build number: FROYO.UVKB5

just odin back to stock 2.1 and then root from 2.1 as its easier to root with 2.1 then 2.2. Use the update package to root, reinstall packages twice then recovery will turn from blue to green. The eclair guide to root

movieaddict said:
just odin back to stock 2.1 and then root from 2.1 as its easier to root with 2.1 then 2.2. Use the update package to root, reinstall packages twice then recovery will turn from blue to green. The eclair guide to root
Click to expand...
Click to collapse
I prefer this method also. If you want options, check my noob root guide, signature... Xda app may not show it.

Thanks for the info.....
Thanks for the information. I'll give it a try this weekend hopefully.

Thanks for the help guys
I followed the steps provided & they did get my phone back to 2.1. I then rooted my phone & ran the Kies mini update. This updated my phone to 2.2, but removed root privileges.
I then ran the 3e recovery installer. This allowed me to reinstall the packages using the update.zip. I booted into recovery mode & ran "reinstall packages" two times. I then ran BusyBox installer and Titanium Back Up and other programs. They were all granted root access.
If I had booted into recovery mode one more time at the start I would have noticed the phone had been rooted.
Thanks to movieaddict and s15274n for informing me on how to flash the phone using Odin. This information will come in handy when I decide to flash a custom ROM.

Related

[Q] HELP: I cannot get vibrant to boot into CWM

I have successfully been able to root and install everything on my Mytouch4G just fine, however, when I tried to install my wife's Vibrant, I am stuck. Here is what I have done:
1) I rooted successfully using superoneclickv1.9.1
2) I installed ROM Manager and also downloaded the Auxora ROM to get ready to install
3) When I flash CWM recovery, it says current and latest recover is 2.5.1.2 (concern here that my mytouch says 3.0.2.4 - do different phones install differently with CWM?). When I look at all CWM recoveries I also notice there is two seemingly more current versions available 2.5.1.3 and 2.5.1.4. I have left it at .2 but wondering why all the versions.
4) When I reboot into recovery, I always get the stock recovery and have not been able to get CWM recovery so I am unable to flash my Auxora ROM. I ran update packages numerous times, and get a signature verification error. I have tried a recovery 3e patch that does not work either. I also gave a try at downloading and SDK, but received temp root errors (phone is already rooted).
After reading many posts, I cannot seem to get a direct answer on what I should do to get CWM to actually boot properly, so I can flash a ROM. Someone said to flash the stock JDK rom, but if I can't boot into recovery, how can I flash anything.
Any help would be greatly appreciated.
You need to get a program for your pc called odin to get back to stock. you can find that and instructions on how to use it if you search for the daily updated vibrant bible its GREAT
http://forum.xda-developers.com/showthread.php?t=849028
going to stock eclair heres a a great guide
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Every once n a while I haft do the install packages thing twice before it gives me clockwork green
. Hope this helps.. o n btw u should look at some of the other roms in the bible before u try auxora
yes u should go back to stock eclair for every rom, in my opinion. Then after that do the 3 button combo and install packages and u will have to do it twice and then the green screen will kick in and ready to rock a new rom.
i hope this helps
What is your current firmware?
I see you posted over in the "NOOB GUIDE" thread, you should really try to root using the method posted there and not any one click root apps.
This should be the root method everyone uses:http://forum.xda-developers.com/showthread.php?t=723479
After root your phone recovery should be blue. Choose "reinstall packages" gives you green recovery(this may need to be repeated multiple times to work possibly including flashing CwMRecovery with ROM manager. I recently did it 5 times b4 i got green recovery)Once you access green recovery chose "apply sdcard:update.zip" go into advanced and choose "reboot recovery" This should give you red recovery. Do a nandroid backup and flash away. Good luck!
Another option you could do is to download SGS kernel flasher from the market and flash a voodoo injected kernel with that app. Then when you boot into recovery you will have red voodoo recovery and you can flash away.
Odin to stock the best way to flash a new rom
Sent from my SGH-T959 using XDA Premium App
jman531 said:
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Click to expand...
Click to collapse
The stock 2.2 that Samsung distributed with their Kies tool has a recovery that checks signatures. Everything earlier does not check signatures. So either use something earlier to get CWM running, or use a ROM that doesn't have the stock 2.2 recovery in the first place, or mod your recovery using the method described in http://forum.xda-developers.com/showthread.php?t=833423
Using Odin to go back to stock Eclair between your flashes of modded roms has the benefit of taking care of this, and also can clear up left over bits and pieces that may interfere with the proper function of your new ROM.
ok, i followed the instructions and am back to eclair, however, whenever I install packages, it just reboots the phone, not even back into stock recovery. I use the 3 key method and get into recovery, run install packages, and the phone just boots back up...its like it isn't running the update.zip file...
UPD: When i load rom manager and try to reboot into recovery, it says the application superuser permissions has stopped unexpectedly and keeps force closing now....titanium backup wont run now either, my root permissions seem whacked after going back to eclair?
UPD2: I followed instructions to unroot and reroot here: http://forum.xda-developers.com/showthread.php?t=739300
It removed superuser, then added it back again, but I still get the unexpected error and it appears my root is not in place. I am back to eclair, and now need a certain way to get my root fixed, so I can try and flash CWM recovery. Without root working, it is not letting me. My wife hates me now for doing this to her phone, so those of you that are married, I would appreciate your assistance to get back on her good side...before Mother's day...please? =)
Ok, thanks for all the help, however, I am really back where I started. I can only get stock recovery, and for the life of me, cannot get CW recovery to load. I used ODIN to go back to eclair on the vibrant, have a good root on the phone now, and no matter how many times i reinstall packages i cannot get clockworkmod recovery to load, ever. Any more thoughts out there?
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
thanks...It is rooted, but not sure about busybox...the stock recovery is 2e now since I went back to eclair, so not sure i should follow that link as it talks about modifying 3e and making it backwards compatable. I did use that process before I went back to eclair, and it didn't work for me. I have uninstalled rom manager, and reinstalled...and it is different in that it shows a flashed recovery 2.5.1.2, and never asks me for my phone type anymore...it used to ask me and i had to select vibrant....is the recovery supposed to be 2.5.1.2? when I show all recoveries it lists .1, .2, .3, .4 so wondering if I should use .3 or .4...why does it stay at .2?
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
OK>>> I GOT IT... Thanks to everyone who helped...Here is what was needed:
1) Install ODIN, install back to eclair
2) uninstall ROM Manager, reinstall
3) I needed to select the 2.5.1.2 recovery from the list again (this was important as it somehow knew of the previous load, but files were missing, or something was just wrong.) It finally loaded properly, and asked for phone type again, so selected vibrant
4) I rebooted into recovery, and instead of install packages, i rebooted once, as starkiller suggested
5) After reboot, went back into recovery from rom manager, and this time installed updates, and it showed that it replaced the recovery with CWM.
6) It rebooted into stock recovery however, so I once again selected install updates, and it went right into CWM recovery, and now I am flashing happy!!!
Thanks again everyone...this was soooooo different than my mytouch4g!
If you have the Kies update of Froyo, the 3e mod will sometimes not work. I've gotten to CWM though , but its best to downgrade then flash a ROM from there.
I just wanted to bump this thread because it really helped me.
I've messed around with numerous android phones, and I've never had thie issues I've had with this phone getting into recovery to flash ROMs
Thank you!

No CWR on Samsung Vibrant

Hi,
I'm currently using Samsung Vibrant (t-mo version) running Firmware 2.2, Baseband version T959UVKB5, Kernel 2.6.32.9.
My problem is I can never boot into ClockWorks Recovery. I've CWR's update.zip downloaded using ROM Manager. Rooted the phone using SuperOneClick.
When I boot into recovery and select apply update.zip, it gives me an error half way thruogh about verification failed.
So I replaced Android Recovery 3e, with another Android Recovery 3e which skips the verification. It installs fine but restarts back in Android's recovery. On rebooting I get a phone with everything back to default!
What am I doing wrong?
Thanks.
PS: I want to upgrade to CM7. which I had at one point but reverted because my bluetooth failed to connect to my headset.
Are you reinstalling packages twice?
Honestly, why not just odin to jfd and rather than boot and flash cwr, just use the update.zip in the noob guide.
I'd encourage checking that route (noob guide is in my signature).
I'm certain we could find a way for yours to work, but if you are going to try a new rom, using ODIN may benefit you anyway. It will not format your internal or external.
cant get or find cwr for samsung vib s.. been looking all night
go to the noob guide.
I am on Samsung Vibrant Froyo 2.2 T959UVKB5.
I have seen your post and it provides 2 update.zip files for JFD.
I do not want to install custom ROM, I just want to root the phone.
will that update.zip work on my phone?
If all you're doing is rooting just for the root apps and not for a custom rom you should use zip A. However the easiest method for you to root would be superoneclick root. Look it up, it will have you rooted with the click of a button (hence the name)... The only thing is that it may stir up your anti-virus, even though it is safe...
Sent from my SGH-T959 (Samsung Vibrant)
Thanks you!

Running into a Problem

ok ... so after flashing back to 2.1 using "eris flashback," when i try to go into recovery all i get is a picture of an eris with a red triangle and ! .... not sure if i soft bricked my phone or something else .. before trying to flash i did re-root my phone using 1 step eris root ... in need of help and would be grateful to try any suggestions .. thanks!
duccicucci said:
ok ... so after flashing back to 2.1 using "eris flashback," when i try to go into recovery all i get is a picture of an eris with a red triangle and ! .... not sure if i soft bricked my phone or something else .. before trying to flash i did re-root my phone using 1 step eris root ... in need of help and would be grateful to try any suggestions .. thanks!
Click to expand...
Click to collapse
... If you used flashback ROM then you need to reroot and reinstall the bootloader.
If you go back to the Flashback fourm where you got the flashback you will see it says "
Please Note: THE RECOVERY BOOT PARTITION IS REPLACED BY THE MATCHING VERSION OF THE STOCK RECOVERY PARTITION (V2: March 2011 OTA; V1: July 2010 OTA) in this ROM. This means that you will need to re-root your phone if you use this ROM, should you later decide that you want to restore a different ROM." http://forum.xda-developers.com/showthread.php?t=792026
To fix:
1 Download j-case's recently modded 1-click root app modded by scary alien. You can get this from the following link and scroll to Scenario 5. This will also install amon-ra recovery that Scary alien modified for track-ball optional.... yes.. it's goofy trackball friendly
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
2. Be sure you have the setting checked to allow 3rd party apps to be installed in Settings>applications, copy the 1-click to your sd card and using astro or another file manager install the app and run it.
3. Reboot into your freshly installed recovery and flash your favorite ROM and enjoy having no more 3g data drops.
computerfreek said:
... If you used flashback ROM then you need to reroot and reinstall the bootloader.
If you go back to the Flashback fourm where you got the flashback you will see it says "
Please Note: THE RECOVERY BOOT PARTITION IS REPLACED BY THE MATCHING VERSION OF THE STOCK RECOVERY PARTITION (V2: March 2011 OTA; V1: July 2010 OTA) in this ROM. This means that you will need to re-root your phone if you use this ROM, should you later decide that you want to restore a different ROM." http://forum.xda-developers.com/showthread.php?t=792026
To fix:
1 Download j-case's recently modded 1-click root app modded by scary alien. You can get this from the following link and scroll to Scenario 5. This will also install amon-ra recovery that Scary alien modified for track-ball optional.... yes.. it's goofy trackball friendly
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
2. Be sure you have the setting checked to allow 3rd party apps to be installed in Settings>applications, copy the 1-click to your sd card and using astro or another file manager install the app and run it.
3. Reboot into your freshly installed recovery and flash your favorite ROM and enjoy having no more 3g data drops.
Click to expand...
Click to collapse
Ditto on what computerfreek told you.
The graphic with the triangle and the red exclamation point is the splash screen of the HTC stock recovery - it is exactly what you would expect to see after flashing the "FlashBack21" ROM... the purpose of which is to return a phone to a stock condition... just as it plainly states in that ROM's thread.
If you need further convincing, press Vol-up+End after you see that "triangle & red exclamation point" graphic, and you will see the STOCK <2e> recovery menu.
If you want to run the completely stock final HTC release for the Eris, while leaving the custom recovery in place, then flash the March2011_OTA_Reference ROM, i.e.
http://forum.xda-developers.com/showthread.php?t=984274
You would do his after re-rooting your phone (re-installing a custom recovery) as computerfreek describes.
bftb0
PS kinda hard to believe this thread was necessary.

[Q] Issues with CWR

I am new to modding my vibrant (phone is rooted but that's all) but looking to flash a new ROM. I dl'd rom manager and installed cwr. When I reboot into recovery mode via rommanager or manually doing it,I do not get the prompt to backup. Only options I get are to reboot system, reinstall packages, delete all user data, delete cache data, and format internal sd-card. Anyone know how to fix this? I just updated to 2.2 froyo UVKB5 kernel 2.6.32.9 if that helps.
looks like you have stock recovery.
try reinstall packages, might take a couple times..
or install CWM via replacing update.zip
What he said, yeah.
So just delete the current update.zip file on my phone and replace it with a new one? Any links to download the update.zip file?
Sometimes you have to Reinstall Packages twice for it to go from regular recovery to CWR. If you flash a custom ROM though, most have a custom recovery built in.
If you have to replace the update.zip (which I don't think that you do), this worked for me the first time I rooted.
http://forum.xda-developers.com/showthread.php?t=849028
How to Root.
I am rooted, but I want to back everything up so that way if I do not like the new custom rom I can go back. I tried reinstalling the update.zip file from the link but s till have the same issue. Any other solutions besides going back to stock and going from there? And if I did go back to stock, would I lose everything?
I backed up using Titanium Backup, is that the same as going into recovery mode and backing up?
Re-download recovery using ROM Manager, then repeat. Worked when I had a similar issue.
Tried that several times. I also reuploaded the update file and reinstalled the package several times. Still no luck so I think I might go back to stock using Odin.
Then DL Eugenes froyo don't brick ROM with the 2e recovery update in it, then re-install packages, maybe twice and you'll have the green recovery menu your seeking
Googled Eugene's DL and I do not feel to confident with it. Is it supposed to fix the issue with getting into recovery mode?
So I went back to stock last night using Odin, upgraded to 2.2, and rooted using Superoneclick. Phone's back up and running but faster than the first time I upgraded to 2.2. I still have the issue getting into the proper recover to install the zip file. I've read that deleting Slacker helped some people, assuming it freed up space on the System ROM. My system ROM was full until I started to delete some apps. I now have 20.7 MB free. Could not enough System ROM space be the issue?
I am now also getting a "Fail" attempt when I try and update su saying that it failed to find currently installed su binary. Any advice on fixing this?
TIA!!!
it would probably be easier to just odin back to stock jfd and then flash a deodexed kb5 build thats rooted with SU already in it from here in the forums.
http://forum.xda-developers.com/showthread.php?t=1036193&highlight=deodexed
If you flashed kb5 from kies or odin and don't want to reinstall the rom then you will need to flash a modified 3e recovery because you probably are not quite rooted and won't be able to use CWM until you flash the modified 3e recovery...
http://forum.xda-developers.com/showthread.php?t=833423
You might want to check out the AIO vibrant toolbox (pinned topic in the development thread) it will give you big easy buttons and instructions to flash back to jfd and root and flash a new rom if you need to... It comes with Odin so you can wander into the install folder and fire up Odin to flash the modified 3e recovery if you decide to go that route too.
If I flash a deodexed kb5 will i still be able to flash a custom rom?

[Q] Cannot install Cyanogen... Confused with all the infos!!

I know it's been adressed many times in different ways, but the info I found yet is not clear so I need a little help! I am trying to install the latest stable Cyanogen mod, using Gingerbread 2.3.7.
I have a Galaxy SII from Bell that I rooted and unlocked when I got it last november. It came on 2.3.3 and I flashed an official 2.3.4 on it, mainly to improve the battery life (and it worked). I did that using Odin and it went well.
Now I try to install Cyanogen mod through ClockworkMod ROM manager, I download and launch the install from ROM manager but on restart the install fails because of the classic 3E recovery message that says the whole signature cannot be verified.
I was having doubts if my phone was even rooted, but since it is still unlocked and software like Titanium backup runs fine, I guess that confirms it!! I am not sure what route to take from here...
Right now here are the phone details...
GT-i9100 on 2.3.4, FW I9100XXKG2, Kernet 2.6.35.7-I9100XXKG2-CL375027 [email protected] #2
I'll appreciate any help!!!!!!
JFChamp said:
Now I try to install Cyanogen mod through ClockworkMod ROM manager, I download and launch the install from ROM manager but on restart the install fails because of the classic 3E recovery message that says the whole signature cannot be verified.
|Question = Q&A
Looks like you are yet another that has not followed the instructions and flashed a cwm and root kernel .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
OR are not following the instructions posted .
First time flashing CyanogenMod 7 to the Samsung Galaxy S II, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Clockwork mod recovery see
NEW HERE
http://forum.xda-developers.com/showthread.php?t=1134290
The instructions work as i have just installed by following the instructions in reply to an exact same post .
jje
Click to expand...
Click to collapse
Thanks jje... The instructions did work! Tough I tought I had bricked my phone at one point, on the final restart it would get stuck at the Samsung logon screen, but I forced it back in recovery, re-flashed from the zip and then it booted in CyanogenMod!!!
I really appreciate your reply

Categories

Resources