Database Develop

[RECOVERY] ClockworkMod Recovery for Vibrant (FINAL! SAFE!)

First things first, if you flashed a previous version of Clockwork Recovery using Odin, FLASH BACK TO A STOCK KERNEL using this Odin package:
http://koush.tandtgaming.com//test/kernel-vibrant-stock.tar.md5
This recovery is *very* safe to use. It does NOT flash your kernel; it is a completely uninvasive recovery method.
How it works: The recovery is packaged as an update.zip that you run from STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original, unmodified, stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork.
HOWEVER, if you use ROM Manager, all of the recovery installation and management instructions are done for you!
Installation instructions:
Download ROM Manager from the Market.
Flash Recovery.
Choose Vibrant as your phone.
Accept the Superuser prompt.
On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
Watch the backup go!
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!

Failed the first time. Left me in the stock recovery menu and gave a recovery error when clockwork first started. Flashed again and tried to backup a second time. Looks like it worked perfect! Now we need some froyo!
Sent from my SGH-T959 using XDA App

youneek said:
Failed the first time. Left me in the stock recovery menu and gave a recovery error when clockwork first started. Flashed again and tried to backup a second time. Looks like it worked perfect! Now we need some froyo!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes! That is expected! The very first boot WILL FAIL, the recovery needs a kick start to complete installation.

little tip
after I downloaded Rom Manager and had it download the recovery for my Vibrant.
After the success message I waited nothing happened so you may have to select to manually reboot into the recovery, then select "reinstall packages" to finish the installation.

I don't see Vibrant in ROM manager. Do I need to buy premium or am I doin somethin wrong

metalfan78 said:
I don't see Vibrant in ROM manager. Do I need to buy premium or am I doin somethin wrong
Click to expand...
Click to collapse
he either took it down and is gonna release it later or something... just wait..

I don't even see "Vibrant" in that list
Nevermind....see above

lp894 said:
I don't even see "Vibrant" in that list
Click to expand...
Click to collapse
Vibrant is listed. "Galaxy S Vibrant". Make sure you are on wifi. Some carriers cache web pages.

Sweet I can't wait to have a real recovery

Koush said:
Vibrant is listed. "Galaxy S Vibrant". Make sure you are on wifi. Some carriers cache web pages.
Click to expand...
Click to collapse
I can confirm I used Wifi and have already completed my first backup using Clockwork
thanks Koush.. buying the prem version to show my support!

Bummer I guess ill have to wait until I can find a hotspot

I downloaded the clockwork Rom Manager premium and I press the pFlash Recovery button. But I don't see Vibrant in the list either.

Please make sure you guys are on wifi. T-Mobile is caching your webpages and serving you older versions.

when i flash the recovery.. and reboot it goes to the stock recovery i hit reinstall packages then it goes to clockwork.. but after that if i reboot it goes back to stock... hmm thats odd..

ElChibo said:
when i flash the recovery.. and reboot it goes to the stock recovery i hit reinstall packages then it goes to clockwork.. but after that if i reboot it goes back to stock... hmm thats odd..
Click to expand...
Click to collapse
That's how it is supposed to work. Recovery is not replaced permanently. It's safer that way. Just reinstall packages to get into clockwork. Or use ROM Manager to have it handle everything automatically.

metalfan78 said:
Bummer I guess ill have to wait until I can find a hotspot
Click to expand...
Click to collapse
No, you don't have to. Just go into your browser, go to menu-->more-->settings-->clear chache and that will get you going

Koush said:
That's how it is supposed to work. Recovery is not replaced permanently. It's safer that way. Just reinstall packages to get into clockwork. Or use ROM Manager to have it handle everything automatically.
Click to expand...
Click to collapse
ok i get it now... ive been used to always having Amon-RA recovery on my phone when ever i boot to it.. so what your saying is everytime your gonna flash a custom rom this is gonna have to take place?

ElChibo said:
ok i get it now... ive been used to always having Amon-RA recovery on my phone when ever i boot to it.. so what your saying is everytime your gonna flash a custom rom this is gonna have to take place?
Click to expand...
Click to collapse
If flashing manually, yes. Just flash using ROM Manager though, and it will handle that all for you automatically.
I can't permanently replace the recovery until the kernel source and whatnot is released for the Vibrant.

Hells yeah!!! Will someone PLEASE put a shipped firmware out now? Like the T959UVJFD. I appreciate the life saving effort from MS_Guru, but t959uvje8 is not jiving with me and my 3g and/or wifi...

Amazing work! Excellent idea for a 100% safe recovery! Kudos!!
Sent from my SGH-T959 using XDA App

[Update] - ClockWorkMod v2.5.0.4 Released

Grab it here:
General: http://koush.tandtgaming.com/recoveries/
Direct Link: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.4-inc.img
Use unrEVOked v3.1 to flash custom recoveries (at your own risk, of course)
1) Download
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.4-inc.img
2) DO NOT PLUG IN YOUR PHONE
3) Run unrEVOked v3.1
4) Under FILE choose CUSTOM RECOVERY
5) Point to the img file
6) Plug in your phone

Updated, no issues. Thanks!

Thanks. I updated without issue.

is it better than the old?
Sent from my Incredible using XDA App

jdkoreclipse said:
is it better than the old?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Yes.. it's 0.0.0.3 times better than the old!

If you rooted with unrevoked 3.0 can you just use that with this image?
Sent from my Droid Incredible using the XDA App

Flashed to 2.5.0.4 no problem. But ROM Manager still indicates 2.5.0.1 is installed.
So how do I get ROM Manager to indicate the right recovery version?
UPDATE: Just after I posted this...I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?

i don't really see a point in updating since it already works for me now...

rom manager reports the older version for me, but booting into recovery it is reporting the newest .4 version

Lexus One said:
Flashed to 2.5.0.4 no problem. But ROM Manager still indicates 2.5.0.1 is installed.
So how do I get ROM Manager to indicate the right recovery version?
UPDATE: Just after I posted this...I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
Click to expand...
Click to collapse
ROM Manager cannot flash recovery because NAND is still locked. Only through the unrevoked tool does NAND temporarily unlock in order to flash clockwork. So if you followed the steps correctly using the unrevoked tool then you have the correct version. Booting into recovery (I think you can't boot through ROM Manager, boot manually or via boot loader) should show the updated version.

Lexus One said:
I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
Click to expand...
Click to collapse
Boot into recovery via ROM Manager. Note the version. Then boot into recovery "manually" (hold volume down while powering on). Note the version again. Notice anything different?

elborak said:
Boot into recovery via ROM Manager. Note the version. Then boot into recovery "manually" (hold volume down while powering on). Note the version again. Notice anything different?
Click to expand...
Click to collapse
recovery by ROM Manager I get 2.5.0.1
recovery by vdown & Pon I get 2.5.0.4
Thanks, now I'm confused even more. Why are they different? And when I go back into ROM Manager it still reports 2.5.0.1. So my original question still stands: How do I get ROM Manager to display the correct version of recovery which is really 2.5.0.4? Even more...why does the recovery manager report 2.5.0.1 when booting into recovery via ROM Manager? This is reallyyyy strange!

I answered your question two posts back...

s197 said:
I answered your question two posts back...
Click to expand...
Click to collapse
Thanks for responding. I understand. But that doesn't answer my question about how to get ROM Manager to report the correct version. Do you know the answer to this?
What is even more confusing is when I boot into ClockworkMod recovery from the ROM Manager and the version of ClockworkMod Recovery is reported on screen as 2.5.0.1 when it is really 2.5.0.4....this just blows me away! It is like ROM Manager is substituting its own version number into the newer version of recovery.

Lexus One said:
Thanks for responding. I understand. But that doesn't answer my question about how to get ROM Manager to report the correct version. Do you know the answer to this?
What is even more confusing is when I boot into ClockworkMod recovery from the ROM Manager and the version of ClockworkMod Recovery is reported on screen as 2.5.0.1 when it is really 2.5.0.4....this just blows me away! It is like ROM Manager is substituting its own version number into the newer version of recovery.
Click to expand...
Click to collapse
If i understand this correctly: The version that ROM Manager reports and boots into is actually a virtual version. This is because, due to the fact that NAND isn't unlocked yet ROM manager can't actually write to it, So when it is "flashing the recovery" it really is only flashing a "virtual recovery". This is why you could on some phones have an older version of recovery flashed and ROM manager would report a newer version that is available.
In short to answer your question, you can't get ROM manager to report the newer version until rom manager has that newer version in it's list, which it currently does not. And even when it is in the list it makes no difference anyway, because unless you boot into recovery using the power button and volume button, the recovery that you boot into will be a virtual one anyway.... so it really makes no difference what ROM Manager is reporting.
And if i am incorrect in my understanding then, disregard all of this but i remember another post with all this in it.

obsidianblackhawk said:
<snip> And if i am incorrect in my understanding then, disregard all of this but i remember another post with all this in it.
Click to expand...
Click to collapse
Thanks. I appreciate your feedback on this. It would explain why I am seeing a different version for the ROM Manager. What I still don't understand is why ROM Manager misleads you into thinking you are booting to the recovery partition. I mean, why even have an option in the program to "Reboot into Recovery" if you are really NOT booting into the recovery partition, but rather a virtual recovery. So, what would happen if you tried to use the virtual recovery as opposed to the real recovery (which in this case is a different version)? Anyone know, or have tried it?

Lexus One said:
Thanks. I appreciate your feedback on this. It would explain why I am seeing a different version for the ROM Manager. What I still don't understand is why ROM Manager misleads you into thinking you are booting to the recovery partition. I mean, why even have an option in the program to "Reboot into Recovery" if you are really NOT booting into the recovery partition, but rather a virtual recovery. So, what would happen if you tried to use the virtual recovery as opposed to the real recovery (which in this case is a different version)? Anyone know, or have tried it?
Click to expand...
Click to collapse
other than flashing a new recovery, the recovery that rom manager boots into works exactly the same as the "real one" in fact i don;t do it the "hard way" any more.

This is probably a dumb question but do I open the img file after I plug in the phone?

Lexus One said:
how to get ROM Manager to report the correct version.
Click to expand...
Click to collapse
Easiest way is this:
1) Uninstall ROM Manager.
2) Reinstall ROM Manager.
ROM Manager will now display no version, as opposed to the wrong version.
And then...
Never again use the "Flash ClockworkMod Recovery" command in ROM Manager. If you want to update recovery, use the unrevoked flasher with the custom recovery option.

Changes?...

Ginger-Root Resource Thread: How-To + Issues + Fixes

Ok so I have successfully rooted my phone after updating to Gingerbread. However, I had a few issues and had to read through a bunch of different posts to get there. So I'm bored and decided to consolidate everything into one.
If anyone has any other issues or fixes post them here and I will update the OP.
Credit goes to mtmichaelson and all those who helped get this working
http://androidinvasion.us/forum/index.php/topic,77.0.html
Here it is:
1. ROOT PROCESS
A. Get back to Stock:
-download the stock Zv4 ROM zip from here and put it on your external SD card- http://forum.xda-developers.com/showthread.php?t=1326893
-Back up all your apps in titanium (important: USER apps only, no data or system apps)
NOTE: It has been reported that restoring apps and data in titanium may cause some issues coming from Froyo to Gingerbread. I backed up my user apps only for easy re-install and NO data or system apps. It worked without a problem.
-MAKE SURE YOU HAVE 4G ENABLED
-boot into recovery (CWM)
-backup?
-factory reset
-select "install ZIP from SD card" in CWM, and install the stock ZIP from the link
-re-bootyour phone (you will have to re-activate it as well)
-install revo toolkit from here if it was wiped with the system reset - http://forum.xda-developers.com/showthread.php?t=1144951
-press "install recovery" and then !!!Revo Stock!!! to go back to stock recovery and wait for it to complete
B. Update to Zv6 then Zv7 (Gingerbread)
-manually search for the update and install it (this will install the v6 update)
-once that installs, manually search again to install the gingerbread update
NOTE: Some people still can't get gingerbread. Verizon has not finished rolling the update out to everyone yet.
Now here is where it gets a little dicey...
C. Rooting Your Gingerbread Phone
-pick up the rooting package from mtmichaelson here - http://forum.xda-developers.com/showthread.php?t=1326509
-follow the instructions he has on that page to obtain root
-Two issues arose for me from this point on.
2. ISSUES
A. Drivers Issue
-The first issue was that some people, including myself, couldn't download the esteem drivers.
-Some people were able to get the drivers from this page to work - http://androidnerds.net/2011/10/08/lg-esteem-oneclickroot-now-ready/.
-I was not able to get my computer to recognize my phone using the above drivers either. I would run the root command from the downloaded package and it would get stuck at "running daemon something something".
-What I did was manually uninstall the LG drivers from my computer and deleted everything "LG related"
-Then I got the drivers from the LG website at this link - http://www.lgforum.com/resources
-Scroll down to the Verizon section and download the "LG_VZW_UNITED..." drivers.
-Your phone should be recognized using the drivers from one of these links.
B. Superuser/Root access Issue - NOTE: this should be fixed now with mtmichaelson's newest root method found here - http://forum.xda-developers.com/showthread.php?t=1326509
-The second issue that came up was that the previous superuser app I had installed stayed on my phone after the updates, even though I lost root.
-The root command from the LG Esteem page would think I had root, but I actually didn't get root access.
-Apparently this issue came up on the Esteem previously and someone wrote a fix for it here - http://androidforums.com/esteem-all...-w-superuser-3-0-6-binary-3-0-3-download.html. It will uninstall the old superuser and install the new version.
3. INSTALL CWM RECOVERY
-mtmichaelson's new rooting package should automatically install CWM recovery on your phone now.
Old method:
-To get CWM back on your phone it's the same process as before the update. Get the Revo Toolkit from thecubed here and follow the instructions - http://forum.xda-developers.com/showthread.php?t=1144951
-There is sometimes an issue where the recovery does not install correctly and gives a fatal error. If this happened, make sure you have version 1.17.1 of busybox installed at system/bin. This worked for me and I got it installed correctly.
...And you should have root after trying a combination of the above. Hope this helped.
-If you have READ through this and still have any issues you can get more personalized help on the IRC channel here.
-Again I did not help with any of this, I'm just consolidating info. If you want to thank someone, thank mtmichaelson and everyone else who helped figure all this out.
-I will keep updating this as new issues arise.

Thank you for compiling this information, it is a useful reference for people to have. I know that the drivers issue took me quite a while to work out even though it is pretty simple. Hopefully this helps others to get rooted with much less trouble.

Quick question using that stock ROM will it completely unroot me?
Also a bit confused with me running revolt does that mess up me just flashing that and it has the stock boot image.
I've Revolted have you?? Sent via tapatalk plugin.

i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...

xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
Hey guys, I have a new package for root for those having problems. I need testers though. If you can come on irc in about 20 minutes. It has the drivers in it also.
Sent from my VS910 4G using xda premium

xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file

Haro912 said:
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Click to expand...
Click to collapse
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.

xjli said:
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
Click to expand...
Click to collapse
Got it. I guess the first release of revo toolkit didn't have the flash stock recovery option. Can't wait to finally have gb on this thing..

Still reboots to cwm... it won't flash stock recovery. Any ideas?

xjli said:
Still reboots to cwm... it won't flash stock recovery. Any ideas?
Click to expand...
Click to collapse
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium

mtmichaelson said:
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
It doesn't..still says 4.0.0.2... how long should it take to 'install?'

OP updated for the new packages from mtmichaelson

xjli said:
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
Click to expand...
Click to collapse
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.

jrf28 said:
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
Click to expand...
Click to collapse
Righto. Only slow 3g in my silo of an office :-/ ill let it go for a while.

Just reinstalled busybox... got it!

The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...

borborpa said:
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
Click to expand...
Click to collapse
It looks like it's a common problem. I haven't installed the ROM yet but mt's new gingervolt rom is supposed to make CWM stick - http://forum.xda-developers.com/showthread.php?t=1326542

Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?

i_t_n said:
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
Click to expand...
Click to collapse
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine

Haro912 said:
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Click to expand...
Click to collapse
Awesome, thank you for the quick reply. Another stupid question that i'm sure is answered somewhere on here, but what exactly will I lose when flashing a ROM, and what will I be able to restore back with a backup?

[Q] Flashin two clockworkmods

So I just rooted and flashed cm7 using this post:
http://forum.xda-developers.com/showthread.php?t=1337105
Now, it installed rom manager on my phone and also, this method flashed Revolutionary clockwork mod on my phone. the version is: 4.0.1.4
Now in rom manager, I want to use the back up option etc and for that it says I need to flash clockwork mod.
My question is, would it do any damage if I were to flash clockwork mod from rom manager although I have it installed already?
Thanks in advance

jhon101 said:
So I just rooted and flashed cm7 using this post:
http://forum.xda-developers.com/showthread.php?t=1337105
Now, it installed rom manager on my phone and also, this method flashed Revolutionary clockwork mod on my phone. the version is: 4.0.1.4
Now in rom manager, I want to use the back up option etc and for that it says I need to flash clockwork mod.
My question is, would it do any damage if I were to flash clockwork mod from rom manager although I have it installed already?
Thanks in advance
Click to expand...
Click to collapse
If you update CWM using ROM Manager, it should overwrite the Revolutionary CWM version with the latest version.

Are you sure? I tried it, takes a really long while
Sent from my Incredible S using XDA App

jhon101 said:
Are you sure? I tried it, takes a really long while
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
He's got 485 thanks, I think he knows what he's talking about.

tpbklake said:
If you update CWM using ROM Manager, it should overwrite the Revolutionary CWM version with the latest version.
Click to expand...
Click to collapse
I tried doing it. It just hangs. I mean the display doesn't turn on and that's it. I waited for about 5 minutes. Nothing happened. Although when I popped out the battery and put it back in, it worked okay but the version of CWM is the same. The one from Revolutionary as I mentioned above!

jhon101 said:
I tried doing it. It just hangs. I mean the display doesn't turn on and that's it. I waited for about 5 minutes. Nothing happened. Although when I popped out the battery and put it back in, it worked okay but the version of CWM is the same. The one from Revolutionary as I mentioned above!
Click to expand...
Click to collapse
Ok then just flash the latest CWM recovery from FASTBOOT USB mode using the command:
fastboot flash recovery recovery.img
Also you can just boot into recovery and perform a backup without using ROM Manager.

Thanks a lot man! Really! Couldn't thank you enough. Got it done!

[Q] Can't flash my Clockworkmod recovery to latest version in Rom Manager

Hi guys,
I have a GT7300 3g/wifi galaxy tab 8.9 which is rooted and has the CyanogenMod 9 ICS installed as the OS.
When I manually boot up into Clockworkmod it shows the 5.5.0.4 version, however when I'm in Rom Manager it shows the version as 4.0.0.4 and whenever I try to flash the recovery in Rom Manager it doesn't update and stays at 4.0.0.4. Any idea as how to get Rom Manager to update to the latest version 5.5.0.4?
I've tried manually installing the .zip from SD card as well in, it updates fine and shows the 5.5.0.4 version when I manually boot up, however when I'm in Rom Manager it only show 4.0.0.4
Thanks in advance.

swiftyy said:
Hi guys,
I have a GT7300 3g/wifi galaxy tab 8.9 which is rooted and has the CyanogenMod 9 ICS installed as the OS.
When I manually boot up into Clockworkmod it shows the 5.5.0.4 version, however when I'm in Rom Manager it shows the version as 4.0.0.4 and whenever I try to flash the recovery in Rom Manager it doesn't update and stays at 4.0.0.4. Any idea as how to get Rom Manager to update to the latest version 5.5.0.4?
I've tried manually installing the .zip from SD card as well in, it updates fine and shows the 5.5.0.4 version when I manually boot up, however when I'm in Rom Manager it only show 4.0.0.4
Thanks in advance.
Click to expand...
Click to collapse
Don't use Rom Manager, it doesn't work correctly on gt8.9. Many users have bricked their tabs using it.

poisike said:
Don't use Rom Manager, it doesn't work correctly on gt8.9. Many users have bricked their tabs using it.
Click to expand...
Click to collapse
Thanks poisike. So do everything manually and go by the version in recovery mode correct?

swiftyy said:
Thanks poisike. So do everything manually and go by the version in recovery mode correct?
Click to expand...
Click to collapse
Why do you want to update, the one you have doesn't work? As far as i know there is only two versions available for gt8.9 and you have the latest one.

swiftyy said:
Thanks poisike. So do everything manually and go by the version in recovery mode correct?
Click to expand...
Click to collapse
You can still use ROM Manager, just don't flash CWM through it. It should still work.
I've used it a few times to install ROMs, but it's just as easy to do it through CWMR, just a couple extra clicks...

Poisike, I had problems trying to update my GT8.9 so when I saw the error in the version number I thought that might be the reason why it didn't update correctly.
Thanks jhhoffma, I won't flash using rom manager from now on then. I have manually updated and everything is OK now.
Thanks guys