Database Info

[Q] Can't update ClockworkMod for Mesmerize

I have a samsung mesmerize and i jsut updated it into froyo, im new to doing this kind of stuff and I haev tried to update Clockworkmod using ODIN. But everytime i do it and start my phone up again i'm stuck in airplane mode and cant get out of it. Is there another step i'm supposed to do after using ODIN that i'm missing? Any help would be greatly appreciated.

Blier2488 said:
I have a samsung mesmerize and i jsut updated it into froyo, im new to doing this kind of stuff and I haev tried to update Clockworkmod using ODIN. But everytime i do it and start my phone up again i'm stuck in airplane mode and cant get out of it. Is there another step i'm supposed to do after using ODIN that i'm missing? Any help would be greatly appreciated.
Click to expand...
Click to collapse
never heard of odin (im still kinda new), but have you tried rom manager from the market? thats how i updated my clockwork recovery to 3.0.0.7, the newest one. it upgrades clockworkrecovery, flashes roms, and backups roms, and theres a paid and free version (with ads). thats what i used. tell me if this works.

CODISDABOMB said:
never heard of odin (im still kinda new), but have you tried rom manager from the market? thats how i updated my clockwork recovery to 3.0.0.7, the newest one. it upgrades clockworkrecovery, flashes roms, and backups roms, and theres a paid and free version (with ads). thats what i used. tell me if this works.
Click to expand...
Click to collapse
Yes i have rom manager but still not 100% on how it works. Would i save the update i downloaded to my sdcard and then use rom manager to open it and update clockworkrecovery?

Blier2488 said:
Yes i have rom manager but still not 100% on how it works. Would i save the update i downloaded to my sdcard and then use rom manager to open it and update clockworkrecovery?
Click to expand...
Click to collapse
to fix anything clockwork scroll to the very bottom of the app, then click flash alternate recovery. Then when its done then click all clockworkmod recoveries right below it, then select 3.0.0.5, and that should fix most/all problems with clockwork anyone has, and give you the newest update. and to get to recovery easier just use mikfroyo v4.4 like i am. when you hold the power button just click options under power off, and click recovery, and it'll open clockworkmod.
note: i did this while i wrote it to double check it still works after i updated it.
and this is all done on my htc evo.

Can't install any custom roms any longer

I am lost.
I had FireFly 2.05 on my SGS (ATT US version) and was going to update to 2.1. I followed the procedure as I aways do; ODIN 1 click to stock rom, master clear, copy update.zip and rom file and reboot into recovery. This time however I get the following error
E:Can't symlink /system/xbin/su SYSTEM:bin/su
E:Failure at line 14
I checked some notes on this and found out that it might be a currupt file. So I re-downloaded FireFly2.1 again and transfered the file to the internal SD card. The outcome was the same.
Then I copied the original 2.05 version back which I know was fine and I still get the same error. Even after a full stock 1-click and master clear the above error will not go away.
Is my internal SD card messed up? Or am I missing something else?
It's running stock right now and all seems to work fine, but I cannot stand all the bloatware and other crap ATT puts on the phone and really want to try FireFly2.1.
Any help is greatly appreciated.
Thanks.

Did you flash clockwork recovery

Did you root the phone after you flashed back to stock?
Sent from my SAMSUNG-SGH-I897 using XDA App

Agree with DaveyBB - sounds like you are not rooted.
Sent from my SAMSUNG-SGH-I897 using XDA App

You do not need to root on stock just flash clockwork with update zip

The update.zip i use is the current clockwork recovery.
I boot into the stock e2 recovery, then apply cw recovery and update the rom. Never had to root stock before when i update via cw recovery.
I will try to root stock first this time and then apply rom via recovery.
Thx
Sent from my SAMSUNG-SGH-I897 using XDA App

anosis said:
The update.zip i use is the current clockwork recovery.
I boot into the stock e2 recovery, then apply cw recovery and update the rom. Never had to root stock before when i update via cw recovery.
I will try to root stock first this time and then apply rom via recovery.
Thx
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
To install clockwork select reinstall packages twice

The issue is not with cw recovery. I am already in it, but the error that i get is after i click "yes apply this zip"... The script starts to format the system, data, datadata, etc. And then this error shows up after files ate copied
Sent from my SAMSUNG-SGH-I897 using XDA App

Have you tried re download of rom package?

My only guess is that clockwork and the rom are not working well. I would try downloading a different clockwork
Sent from my SAMSUNG-SGH-I897 using XDA App

mcord11758 said:
Have you tried re download of rom package?
Click to expand...
Click to collapse
Done that too.
So just to reiterate...
I had FireFly2.05 running and many other cooked Android 2.1 and 2.2 roms before this. I follow the instrution of the cooks to the 't' on how to update to the newest rom and never had any issue.
This time I downloaded FireFly2.1 and also Phoenix4.5 from the respective cooks and followed the instructions as usual. The issues does not show up until the 'copy files' part of the script is running (formating of the filesystem already passed).
All I can imagine are these:
1) The transfer from the PC to the Phone is corrupt (ruled out the download from the net as even the existing FireFly2.05 rom no longer loads)
2) The internal SD card is messes up
3) There is some configuration change I am not aware off that prevents the install of the cooked rom.

Maybe try to reformat sd through clockwork

Problem solved, kind of.
My desktop PC, which I always use to transfer the files is somehow responsible for the error I get in CWM recovery. I ended up using my laptop to transfer the ROM to the phone and it worked again.
Something is messing up the USB transfer? That seems very odd but I am glad it's not the phone that caused the issue.
If I find out what the issue is with my Desktop I will post again just in case this rather rare issue might happen to someone else.

anosis said:
Done that too.
So just to reiterate...
I had FireFly2.05 running and many other cooked Android 2.1 and 2.2 roms before this. I follow the instrution of the cooks to the 't' on how to update to the newest rom and never had any issue.
This time I downloaded FireFly2.1 and also Phoenix4.5 from the respective cooks and followed the instructions as usual. The issues does not show up until the 'copy files' part of the script is running (formating of the filesystem already passed).
All I can imagine are these:
1) The transfer from the PC to the Phone is corrupt (ruled out the download from the net as even the existing FireFly2.05 rom no longer loads)
2) The internal SD card is messes up
3) There is some configuration change I am not aware off that prevents the install of the cooked rom.
Click to expand...
Click to collapse
One Question:
What method are you using to enter recovery method when you attempt to flash the rom? And what color is your recovery menu (should be green)?
(Don't go into recovery via rom manager. Try entering recovery via your advanced power menu)

bames said:
One Question:
What method are you using to enter recovery method when you attempt to flash the rom? And what color is your recovery menu (should be green)?
(Don't go into recovery via rom manager. Try entering recovery via your advanced power menu)
Click to expand...
Click to collapse
I don't think he's getting into Clockwork via ROM Manager, as he's said multiple times he's using the CWM update.zip; reinstalling packages in 2e recovery to get to CWM.
He's also said he doesn't believe this to be an issue with Clockwork (and I don't either). And I'm also pretty sure we're not dealing with newbie mistakes of Android Recovery vs. Clockwork Recovery.

any chance you're leaving your usb plugged into your cappy while you're trying to flash it?

Problems restoring backup with clockwork

Everytime I try and restore a backup from cwm the phone reboots to the first mytouch boot screen and just stays there. Is there something I'm missing on how to restore a backup? I'm using cwm 3.0.0.5, I make a backup, then when I want to restore it, I wipe data and cache and hit restore backup. Once it's finished, I reboot the phone, then it just sits on the boot screen until I eventually decide to pull the battery.

j21blackjack said:
Everytime I try and restore a backup from cwm the phone reboots to the first mytouch boot screen and just stays there. Is there something I'm missing on how to restore a backup? I'm using cwm 3.0.0.5, I make a backup, then when I want to restore it, I wipe data and cache and hit restore backup. Once it's finished, I reboot the phone, then it just sits on the boot screen until I eventually decide to pull the battery.
Click to expand...
Click to collapse
Clockwork Recovery 3.0.0.5 will work only with 2.3 (gingerbread ROMs).
Since the stock ROM is 2.2.1 you need to use recovery image 2.x.
you are in luck though. re-Flash CM7 download Clockwork ROM Manager scroll to the bottom "All clockwork recoveries" and flash the highest 2.x version they have. Then you can restore your back up without problems.

Thanks, I actually found that exact answer about 10 minutes after I posted this. I did just that, flashed cm7 then flashed cwm 2.x. I wanted to try cm7 anyway, but after an hour just trying to get the market to work, I decided to just go back to good old iced glacier.
Sent from my HTC Glacier using XDA App

j21blackjack said:
Thanks, I actually found that exact answer about 10 minutes after I posted this. I did just that, flashed cm7 then flashed cwm 2.x. I wanted to try cm7 anyway, but after an hour just trying to get the market to work, I decided to just go back to good old iced glacier.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I bet you didn't flash gapps or the newer version of it. That's why you couldn't get the market to work.
Sent from my CM7 HTC Glacier using XDA App

coupetastic-droid said:
I bet you didn't flash gapps or the newer version of it. That's why you couldn't get the market to work.
Sent from my CM7 HTC Glacier using XDA App
Click to expand...
Click to collapse
I have no idea what I did, but eventually I got it all worked out. I'm now a very happy cm7 rc1 user with a 1.84GHz smartass kernel.

j21blackjack said:
I have no idea what I did, but eventually I got it all worked out. I'm now a very happy cm7 rc1 user with a 1.84GHz smartass kernel.
Click to expand...
Click to collapse
Glad it worked out for you, but you (and others who may have this problem) could save yourselves a lot of this by downloading TrueBlue's zip (from development sub-forum) and flash it. It has cwm 3.0.0.6 plus stock TMO recovery.
With CM 3.0.0.6 recovery (thanks to Option94 for that), you can backup/restore both Android 2.2.x (CM6) and 2.3.x (CM7). TrueBlue's thread OP gives you instructions on how to use it.
It is a modified ROM Manager that "disguises" cwm's 3.0.0.6 and the stock Recovery as cwm 3.0.0.5 and 2.5.1.4 respectively.
PS - if you use it - don't forget to "thank" him (and Option94 also).
UPdate - if you subsequently update ROM Manager, it does not wipe out the above scheme with the disguised cwm's - it still works the same (at least through ROM Manager 3.0.1.0).

gaww said:
Glad it worked out for you, but you (and others who may have this problem) could save yourselves a lot of this by downloading TrueBlue's zip (from development sub-forum) and flash it. It has cwm 3.0.0.6 plus stock TMO recovery.
With CM 3.0.0.6 recovery (thanks to Option94 for that), you can backup/restore both Android 2.2.x (CM6) and 2.3.x (CM7). TrueBlue's thread OP gives you instructions on how to use it.
It is a modified ROM Manager that "disguises" cwm's 3.0.0.6 and the stock Recovery as cwm 3.0.0.5 and 2.5.1.4 respectively.
PS - if you use it - don't forget to "thank" him (and Option94 also).
Click to expand...
Click to collapse
Did that yesterday, it works great.

Thats awesome news, I was just about to post the question about the 3.0.0.6 backwards compatibility with nandroid backups.. Thanks!

i have the same issue.i flashed CM7.its installed,now i go into ROM manager and scroll down and select "All ClockworkMod Recoveries" (2.5.1.4) but get "an error accured while flashing your recovery"?
what did i do wrong?am i missing some thing?
i also wanted to know how i install GAPPS while i have CM7 installed? thanks for any help

MTSDAN said:
i have the same issue.i flashed CM7.its installed,now i go into ROM manager and scroll down and select "All ClockworkMod Recoveries" (2.5.1.4) but get "an error accured while flashing your recovery"?
what did i do wrong?am i missing some thing?
i also wanted to know how i install GAPPS while i have CM7 installed? thanks for any help
Click to expand...
Click to collapse
ok i installed GAPPS ..but still having issues with the Clock work recovery

MTSDAN said:
i have the same issue.i flashed CM7.its installed,now i go into ROM manager and scroll down and select "All ClockworkMod Recoveries" (2.5.1.4) but get "an error accured while flashing your recovery"?
what did i do wrong?am i missing some thing?
i also wanted to know how i install GAPPS while i have CM7 installed? thanks for any help
Click to expand...
Click to collapse
Ignore all those BS. Go in Market and download Rom Manager 3.0.1.0 and then flash the latest 3.0.0.5 (orange) recovery image. Then place the GAPP anywhere in your SDCard long as you know where it is. Reboot it in to recovery but selecting it from Rom Manager and then when its booted select Install zip from SDCard> Choose zip from SDCard.
Flash the GApp.zip and be done. Just remember when you flash NB via full wipe you have to flash GApp.zip everytime but if you just mount new NB on top of old one then DO NOT flash GApp.zip again as it will still be on your device as it ment to be installed once in that case.

BlackSHELF said:
Ignore all those BS. Go in Market and download Rom Manager 3.0.1.0 and then flash the latest 3.0.0.5 (orange) recovery image. Then place the GAPP anywhere in your SDCard long as you know where it is. Reboot it in to recovery but selecting it from Rom Manager and then when its booted select Install zip from SDCard> Choose zip from SDCard.
Flash the GApp.zip and be done. Just remember when you flash NB via full wipe you have to flash GApp.zip everytime but if you just mount new NB on top of old one then DO NOT flash GApp.zip again as it will still be on your device as it ment to be installed once in that case.
Click to expand...
Click to collapse
thanks got gapps installed just fine but im having trouble with the rom manager im trying to install the laterClockwork recoveries (2.x)..but i keep getting an error

MTSDAN said:
thanks got gapps installed just fine but im having trouble with the rom manager im trying to install the laterClockwork recoveries (2.x)..but i keep getting an error
Click to expand...
Click to collapse
No you didn't do what I said then. Go to Market> Rom Manager (3.0.1.0)> Download/Install. Then run Rom Manager and flash 3.0.0.5(latest not 2.5.1.2/2.5.1.4). If you use 3.0.0.5 you don't have to worry about 3.x(orange) or 2.x(green) as you can run 2.2/2.3 based without changing it.
3.0.0.5 < not Rom Manager its Recovery.
3.0.1.0 < ver of Rom Manager with 3.0.0.5 Recovery frame.
Problem is for people who don't know it get confusing as 3.0.0.5 could mean Recovery and Rom Manager. As normally other software specify and have different type of scheme for framework and software but in this case they both share same number so it gets little confusing.

ok i installed 3.0.1.0 rom manager from market so now i should have no issues when restoring 2.2.1 roms or 2.3 roms?thanks for the help man im coming from a Vibrant that was lost/stolen..that vibrant was so easy to root lol.thanks again

MTSDAN said:
ok i installed 3.0.1.0 rom manager from market so now i should have no issues when restoring 2.2.1 roms or 2.3 roms?thanks for the help man im coming from a Vibrant that was lost/stolen..that vibrant was so easy to root lol.thanks again
Click to expand...
Click to collapse
Well if you flashed 3.0.0.5 Recovery then no you won't have to worry about Green(2.x EXT3) or Orange(3.x EXT4) as you can flash both.

Cant update ROM. What am I doing wrong

I have a NS unlocked and rooted. I have ROM Manager, busybox etc. I followed all the instructions but I can't update ROMs or the 2.3.3 update or CM7 nothing. Each time it starts to unpack or whatever it gets about 1/3 the way and aborts. Something about verifying signatures or something.
Very frustrating.
Thanx in advance
I Love The Smell Of Burnt Rubber Anytime

try to download the ROM again
sounds like the zip file is corrupted

What version Clockwork Recovery are you using? Try reverting back to a older version or something.
Verify the ROM's MD5 Hash using HashTab (Google it)

I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime

hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
what's the latest clockwork recovery? did you try 3.0.0.5?

Ya. The new ver is 3.0.2.4
I Love The Smell Of Burnt Rubber Anytime

hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
Hmm... It sounds like clockwork isn't properly installed. ROM Manager should take you directly to clockwork recovery without you having to do anything.

the problem you are facing is that you are still on stock rom. so even if you flash clockwork recovery and then reboot to recovery, you'll always end up going to the stock recovery. this is a new feature implemented by google.
what you should do is...
1) go to bootloader
2)flash the clockwork recovery using fastboot
3)DO NOT reboot the phone or quit bootloader. immediately after flashing the rec. using fastboot, just enter recovery (through bootloader)
4)flash you new rom
just for u to have an idea. the recovery should be orange in colour.
option 2.
you also have the option of using a file manager with moun/root functions such as root explorer and rename the recovery script in etc folder but i guess step 1 is much easier for now.

OK I played alot today and this is what happened.
After fixing permissions and flashing the new CWM and wiping data/cache it finally worked. Unfortunately titanium and my backup didnt bring everything over. So I went back and forth between stock and CM7 several times but I just couldnt get all my stuff back in CM7. So I thought Id try the 2.3.3 update but not wiping stuff. That didnt work. Then I tried one more time with CM7 but not wiping. I couldnt get pastthe little CM7 droid on the skateboard. So went back to stock for now. Ill have more time on Sat to give things another try.
At least I can get in it now.
Any ideas/thoughts/
Thanks and sorry for the long post.

[Q] Help with Rom Manager

Sorry for the noob questions but I can't seem to find a specific answer to my problem.
I am trying to create a backup of my stock Touchwiz ICS 4.0.4 using Rom manager premium v.5.0.2.1 so that I can flash CM10 to my Verizon S3. I have flashed the "ClockworkMod Recovery".
Current Recovery: ClockworkMod 6.0.1.2
Latest Recovery: ClockworkMod 6.0.1.2
Now when I try to "Backup Current ROM" my phone boots into a menu. I was under the impression that it should begin creating a Nandroid backup when I did this. It boots into Android system recovery <3e>
Word for word this is what I get
Volume up/down to move highlight:
Power button to select.
Reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition apply update from cache
_______________________________________________
# MANUAL MODE #
--Applying Multi-CSC...
Applied the CSC-code : VZW
Succesfully applied multi-CSC
From there I didn't see an obvious Create backup type of option so I chose "Reboot system now" which then booted up normally. In Rom manger there is no file under Manage and Restore backups. Do I need to choose a different option in the boot menu. I could manually make a nandroid backup I think, but I'm not sure if it would work properly since I flashed the ClockworkMod Recovery.
Sorry, I am very new to this!

How did you flash your recovery? Was it through rom manager or through ez recovery?
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

Yeah you have the stock android recovery. (3e) Try using the "EZ-recovery for VZW Galaxy S3" app from the play store. I have always heard ROM manager can be kind of buggy.

JBO1018 said:
Yeah you have the stock android recovery. (3e) Try using the "EZ-recovery for VZW Galaxy S3" app from the play store. I have always heard ROM manager can be kind of buggy.
Click to expand...
Click to collapse
No, not at all, Rom manager works fine, but only if you flashed your recovery through it. If you used ez recovery, rom manager does not know that it has cwm recovery on it and will not operate correctly. Flash recovery through rom manager and it will work correctly. EZ is a foundation app intended to simplify recovery without rom manager. Not good if you know what your doing.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

annoyingduck said:
No, not at all, Rom manager works fine, but only if you flashed your recovery through it. If you used ez recovery, rom manager does not know that it has cwm recovery on it and will not operate correctly. Flash recovery through rom manager and it will work correctly. EZ is a foundation app intended to simplify recovery without rom manager. Not good if you know what your doing.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
Click to expand...
Click to collapse
He said he did use ROM manager to flash recovery and that it says he has CWM installed. Yet from his descripton when his phone reboots into recovery he is getting Android recovery 3e. (stock recovery) So something isnt working right. That's why I suggested ez recovery and mentioned ROM manager has been notoriously unreliable in the past for me and many other I know. It may work fine for this phone. I just, out of habit, tend to stay away from it.

JBO1018 said:
He said he did use ROM manager to flash recovery and that it says he has CWM installed. Yet from his descripton when his phone reboots into recovery he is getting Android recovery 3e. (stock recovery) So something isnt working right. That's why I suggested ez recovery and mentioned ROM manager has been notoriously unreliable in the past for me and many other I know. It may work fine for this phone. I just, out of habit, tend to stay away from it.
Click to expand...
Click to collapse
Good call!

I didn't see any mention of how he flashed his recovery, just assumed it was not through rom manager due to the issues he's having.
My experience with ez recovery made rom manager (an app I like alot) not work correctly. As soon as I re flashed through rom manager, all was well. Not knocking ez, just trying to get his rom manager app working for him.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

I am having the same problem. I flashed mine through Rom Manager also. It worked on the first reboot in recovery and has worked one other time in touch. Here's my thread. - http://forum.xda-developers.com/showthread.php?p=32795611#post32795611
Solutions?
If I install ez Recovery, how will that effect CWM?

I'm running the premium version of rom manager. Are you guys running the free version? I can't imagine why your having these issues, could it be related?
I originally used ez to install cwm 6.0.1.2, then used rom manager to flash the touch version of 6.0.1.2. Have not had these issues.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

annoyingduck said:
I'm running the premium version of rom manager. Are you guys running the free version? I can't imagine why your having these issues, could it be related?
I originally used ez to install cwm 6.0.1.2, then used rom manager to flash the touch version of 6.0.1.2. Have not had these issues.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
Click to expand...
Click to collapse
I got premium, I thought the same cause mine wont let me download roms either. It tells me to upgrade to the latest version.
Should we maybe uninstall and try a different install method, such as yours. Would there be any consequences?

I don't see any issues with that. To get touch through RM, there are 2 ways. One is in app purchase (don't do this, it's a one time, one use add on. Does not stay if you install a different recovery. Kind of a scam). The other is in RM you can link directly to cwm site and dl the apk for free. Just be sure you get the one for our phone, the site page is a little weird to navigate. Then you have it forever.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

This might be your problem, see if you gave the file mentioned in the last post and delete it.
http://forum.xda-developers.com/showthread.php?p=32346811
Sent from my S3 running Eclipse 2.1

kintwofan said:
This might be your problem, see if you gave the file mentioned in the last post and delete it.
http://forum.xda-developers.com/showthread.php?p=32346811
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
What file? Im still noob confused about all of this. S-P-E-L-L it out. Can I just go ahead and do ez now or do I need to do anything to RM
Thanks for your help, its greatly appreciated.

travis.bridges10 said:
What file? Im still noob confused about all of this. S-P-E-L-L it out. Can I just go ahead and do ez now or do I need to do anything to RM
Thanks for your help, its greatly appreciated.
Click to expand...
Click to collapse
Just try ez recovery first and see if it works, its in the play store. If it doesn't I'll try to find the exact path of the file. I'm not stock so its hard I'll have to search for it
Sent from my S3 running Eclipse 2.1

kintwofan said:
Just try ez recovery first and see if it works, its in the play store. If it doesn't I'll try to find the exact path of the file. I'm not stock so its hard I'll have to search for it
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
It worked the first time I rebooted from RM, then I tried to enter manual recovery and it went to android recovery, then I tried RM reboot to recovery and it went into android recovery. Do I need to back it up before I reboot? It seems like the reboot in recovery right after a flash works, but then looses it after reboot.
I still have the problem also of it not allowing me to download roms, says I need to upgrade to latest version.

travis.bridges10 said:
It worked the first time I rebooted from RM, then I tried to enter manual recovery and it went to android recovery, then I tried RM reboot to recovery and it went into android recovery. Do I need to back it up before I reboot? It seems like the reboot in recovery right after a flash works, but then looses it after reboot.
I still have the problem also of it not allowing me to download roms, says I need to upgrade to latest version.
Click to expand...
Click to collapse
Then that file needs deleted. I'll try to find it.
But the easiest fix would be to download whatever ROM you want directly from the forum. Use Ez recovery and in that first boot into recovery flash the ROM you downloaded following the instructions in the ROMs post.
Sent from my S3 running Eclipse 2.1

kintwofan said:
Then that file needs deleted. I'll try to find it.
But the easiest fix would be to download whatever ROM you want directly from the forum. Use Ez recovery and in that first boot into recovery flash the ROM you downloaded following the instructions in the ROMs post.
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
ok... Thats probably what ill do then. I have to do some more reading on flashing roms... I dont want anymore problems. I got three more questions for you since youve been so helpful.
1. Any idea why its not letting me get into the download ROMS in RM. Saying I need to upgrade to the latest version of RM
2. Im sure I could find the answer to this but Ill ask since I got you here. I just went through over the last few days adding a lot of customizations, like nova, widgets, widgetlocker, tasker, etc. When I do flash a new rom whats the most efficient way to transfer apps, settings, designs, etc
3. If I was to keep the stock ROM what happens with VZW OTA updates. Doesnt it mess things up. This last update has messed everything up for GS3's and I bet the next will have even more "restrictions"
Thanks again

travis.bridges10 said:
ok... Thats probably what ill do then. I have to do some more reading on flashing roms... I dont want anymore problems. I got two more questions for you since youve been so helpful.
1. Any idea why its not letting me get into the download ROMS in RM. Saying I need to upgrade to the latest version of RM
2. Im sure I could find the answer to this but Ill ask since I got you here. I just went through over the last few days adding a lot of customizations, like nova, widgets, widgetlocker, tasker, etc. When I do flash a new rom whats the most efficient way to transfer apps, settings, designs, etc
Thanks again
Click to expand...
Click to collapse
1. I don't use RM so can't be much help there.
2. I personally use titanium backup to back up and restore user apps. I don't recommend restoring system settings.
Sent from my S3 running Eclipse 2.1
---------- Post added at 09:02 PM ---------- Previous post was at 08:52 PM ----------
One either thing make sure you backup your imie...there's a guide in the development section.
Sent from my S3 running Eclipse 2.1

I figured it out earlier. When you do the first reboot the recovery menu gives you the option to disable stock recovery from flashing. Select it and it's been working fine since.
Sent from my SCH-I535 using xda app-developers app

travis.bridges10 said:
I figured it out earlier. When you do the first reboot the recovery menu gives you the option to disable stock recovery from flashing. Select it and it's been working fine since.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Good. I don't remember seeing that option, but I've been rooted for a while.
Sent from my S3 running Eclipse 2.1