Got the new i727 from Rogers. First time Android user, come from the BB world.
Want to back up my stock ROM. Installed paid version of Rom Toolbox. Went to the Manage ROM section, and it told me I had to have ROM Manager.
Downloaded the free version of ROM manager, and it told me I had to have ClockworkMod installed, and asked if I wanted to install it.
Said YES, and it took me to a group of phones, not the SGS2 LTE. So I cancelled.
So three questions:
1. When I buy Rom Toolbox, why do I have to then get ROM Manager?
2. What is ClockworkMod?
3. Which phone do I select that will work on my Rogers Samsung Galaxy S2, and will that finally allow me to back up my stock ROM.
Thanks
Harry Fine
I'm not familiar with ROM Toolbox, nor do I know why you would use it. I'm not much of a fan of ROM Manager, either, but it does work. Install it, and select the T-Mobile SGS2 to get CWM installed. You can then take a Nandroid backup.
That said, backups of untouched stock ROMs are much less needed when there's already an Odin TAR out.
What does it mean to "take a nandroid" backup?
Got it. Installed CWM and did the ROM backup, now have a Nandroid backup, also copied to PC. I'm assuming if I've done this correctly, I can now re-install the stock ROM if I had to.
Once I have a nandroid backup that is known to be good, is there any situation (other than hardware) that would prevent me from un-bricking my phone by simply installing a known good ROM?
As long as you have a backup and are able to access CWM...flash away
Sent from my SGH-I727R using XDA App
And where is CWM? Is it on the ROM itself, or on the boot sector? If the ROM is bad, or boot sector becomes corrupted, how do you access CWM?
And even if you can't access CWM - in other words, if you can't get past the Samsung logo - you can always return to stock with Odin.
basically as long as you can boot to either download mode or recovery you're safe.
Sent from my SGH-I727R using XDA App
Related
Could ROM Manager fake Flash Clockworkmod recovery be responsible for bricking phones on LG update? Let me explain what I mean - Lots of people, like myself, installed ROM Manager and its CWM because we did not know it's not real Flash. Then We switched to "real" CWM. Now the question is when we do normal stock recovery in order to get official GB update, does this CWM of ROM manager still remains in the phone? If so, could it be that it contributed to the troubles updating through LG tool? How can I make sure I removed it from the phone?
Thanks!
Yes. Many people have confirmed that not having the stock recovery on the device is a road to Bricksville. Even though you are fake flashed there is code inserted somewhere to redirect to the fake flash, and the recovery images for flash (normally installed every boot) have been deleted or renamed. You should flash stock recovery with NVFlasher to make sure you are back at a clean stock recovery before using the LG Update tool.
Thanks but what I mean is that AFTER I realized it's fake flash I installed "real" CWM. So when I do stock on this "real", does CWM rom manager still remains in the phone and how can I remove it?
post deleted by poster
so I am a little confused I used CWM to make a backup before I did anything to my phone. And I was already on the 2.3.3 lg update. So if I restore that I should be back to stock and CWM should still be there right? But lets say LG comes out with another update (Doubtful) and I want to use it I should use the NVflash to reture the phone to stock? if I use NVflash will that put me back on froyo 2.2.2 or GB 2.3.3?
Also I used rom manager to make a backup of the rom I was on which was the stock rooted so is that fake or what the hell is fake? is it the first option in rom manager the CWM recovery? is it the same if I use CWM stock recovery? in cwn itself? Oh I am so confused someone help me
ROM Manager cannot flash directly to the phone so it "fake flashes" CWM recovery. It only installs a few files to the system so that when you run recovery the stock recovery runs an "upate" and that launches CWM recovery from your SD card. Just return the phone to GB 2.3.3 stock and be happy with it. If you restore using CWM it will remain there, so you should use NVFlash to restore stock recovery also.
jboxer said:
ROM Manager cannot flash directly to the phone so it "fake flashes" CWM recovery. It only installs a few files to the system so that when you run recovery the stock recovery runs an "upate" and that launches CWM recovery from your SD card. Just return the phone to GB 2.3.3 stock and be happy with it. If you restore using CWM it will remain there, so you should use NVFlash to restore stock recovery also.
Click to expand...
Click to collapse
I have BOTH - CWM AND CWM through the ROM Manager. So if use NV Flash to go to stock, is the CWM from ROM manager still in the phone and how can I remove it?
Thanks!
so what I am getting out of this is rom manager is crap and dont use it. If you just use CWM to do your flashing and backups and recoverys you should be ok.
Charlie
mojorisin7178 said:
so what I am getting out of this is rom manager is crap and dont use it. If you just use CWM to do your flashing and backups and recoverys you should be ok.
Charlie
Click to expand...
Click to collapse
Thanks but my questions are:
1. If I go to stock using NV Flasher, is ROM Manager's CWM still going to be in the phone, since I have BOTH?
2. Can it BRICK my phone if I do the LG update then?
3. How can I make sure I removed BOTH - NV Flash CWM AND ROM Manager CWM?
I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.
CZ Eddie said:
I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.
Click to expand...
Click to collapse
I dont know what ALOT of investment is.......but what i think happened here is this<<
You were on Gingerbread right, Infused v2.x.x and you made a Nandroid(thats fine)
u installed miUi and didnt have the luck you wanted...Thats fine
You went back to stock, and rooted and modded the Recovery so you could restore your nandroid....Thats fine
But if you went back to stock(Froyo Right) and try to load up a Gringerbread Nandroid on top it shouldnt work. Nandroids only back up the ROM not the Kernel......so you were in a sense trying to run a Gingerbread Rom on a Stock Froyo Kernel......
Go into CWM flash your Kernel, or use odin and flash a Ginger Kernel then go into CWM and RESTORE.
Happy FLashing
Didn't know that! That may explain a lot of my ROM frustrations.
I'll try this and report back.
Off to go find a suitable kernel....
I really should get my post count up so I can get past this horrible 10 post restriction.
Did you try initiating the flash through CWM or through ROM Manager? Honestly I don't prefer to do any work via ROM Manager, I always have more luck going through CWM and starting a flash from there. Kernel is the first place I'd start but you should also Factory Wipe and Cache Wipe each time you move between ROMs, sometimes you get very lucky and don't need to, most times you bork your phone, and if you're nandroiding back from a backup wiping before you restore is good practice just to make sure you don't leave anything behind from your old ROM.
I installed a gingerbread kernel:
http://forum.xda-developers.com/showthread.php?t=1212485
Version 1.1.
But it didn't work out.
So now I'm fighting with trying to get a stock Infused V2 ROM on there.
No luck yet. Once I do, I'll try the recovery again.
Btw, I'm using CWM for everything.
Go to mounts and storage in clockwork recovery then select format system then do your nand restore ...
Sent from my Samsung Infuse 4G - 1.6ghz
Wow, I was totally making some rookie (which I am) Android mistakes today.
Every time I tried to restore the backup image, I was doing it in CWM by selecting "install .zip from SD card". When I SHOULD have been using the "backup/restore" function.
I'm up & running again. All original apps/settings are restored. Great!
Now to start breaking things again, since I know how to restore from backup now.
Hi all. My first post. I decided a couple weeks ago I wanted to root my G2x and started lurking here and reading up on the process. I Had Gingerbread installed so used One-Click NvFlasher to flash CWM 4.0.1.5 to my phone and then rooted the phone using a zip found in another thread. It was my first time rooting and I'm happy to say everything went fine.
I was playing around with ROM Manager and also installed CWM using it but decided until I have more time to spend checking out/installing ROMs I'm gonna stick with stock so I uninstalled it.
My questions are: do I now have two versions of CWM on my phone? Which version did ROM Manager install? If I boot into recover which one is loading, the one I installed with NvFlasher or the ROM Manager-installed one? And how do remove the one ROM Manager put there? I'd rather stick with just the one I installed using NvFlasher.
From what I understand, the ROM manager app doesn't really flash CWM on our phones, it fakes it. So, you've only got installed what you did through NVFlash.
dustinscottmiller said:
From what I understand, the ROM manager app doesn't really flash CWM on our phones, it fakes it. So, you've only got installed what you did through NVFlash.
Click to expand...
Click to collapse
Yeah, I read about the fake flashing in the NvFlasher thread but didn't know what it meant fully. Seems like it means that you can only boot into the fake flashed one using ROM Manager. Other than that I wasn't sure what the implications of the fake flash were.
There's a clockwork mod folder on my phone's sdcard (internal - I don't use an external one). Is that the fake flash or the NvFlash one? I'd love to delete that folder if it's the ROM Manager one.
The "Clockworkmod" folder on your SD card is where the ROMs are backed up regardless of which version of Clockworkmod you used so don't delete that folder. The difference is when you boot into recovery using power + volume down you use the Clockworkmod Recovery on the phone's recovery partition you flashed with NVFlash. When you "reboot into recovery" using ROM Manager you boot into the so-called "fake flashed" version of Clockwordmod and it is not loaded from the physicial recovery partition on the phone; but from an image kept elsewhere in your phone's NAND memory. Don't worry about those images as leaving them won't harm anything and won't interfer with any OTA udpates if you are on a rooted stock rom. To get rid of it you simply want to uninstall ROM Manager from your device and then delete the "udpate.zip" file you will find in the root of the internal sd card. It is that update.zip that ROM Manager uses to trick recovery into loading the recovery images it stored elsewhere on your device. Now when you want to go into Clockworkmod Recovery just boot into recovery using power + volume down or the Reboot 2X app in the Market (link below). When the app says your device is not supported ignore it and press the back key (do not press the exit button) and then you can use that app to reboot into the real Clockworkmod Recovery without having to hold the buttons on the phone.
https://market.android.com/details?...wsMSwxLDEsImNvbS5tYXhpc21hLmxnbzJ4cmVib290Il0.
Thanks, jboxer. I'd already uninstalled ROM Manager and just now deleted the update.zip. It seems like with CWM already flashed via NvFlasher I can backup my stock ROM and install any other ROM I can download so I don't really need ROM Manager unless I'm looking for something with an interface.
dmj2012 said:
Thanks, jboxer. I'd already uninstalled ROM Manager and just now deleted the update.zip. It seems like with CWM already flashed via NvFlasher I can backup my stock ROM and install any other ROM I can download so I don't really need ROM Manager unless I'm looking for something with an interface.
Click to expand...
Click to collapse
You don't want ROM Manager, period, on our phone. It doesn't run recovery from the actual recovery partition and if you are borked you don't have a usable recovery to fix your phone unless you flashed with NV Flash anyway. I also don't like the way ROM Manger "boots" into recovery. It is actually invoking the stock recovery (or whatever recovery you may have flashed with NV Flash) and that then runs the update.zip file on the root of your internal sd. Since stock recovery is set to factory reset your phone when you invoke recovery, I worry that if the upate.zip got messed up you might wind up factory resetting your phone. I tried ROM Manager (which doesn't work until you use NV Flash at least once anyway) and booted from it into recovery once. It was scary enough for me I immediately uninstalled it and got rid of its bogus update.zip.
jboxer said:
You don't want ROM Manager, period, on our phone. It doesn't run recovery from the actual recovery partition and if you are borked you don't have a usable recovery to fix your phone unless you flashed with NV Flash anyway. I also don't like the way ROM Manger "boots" into recovery. It is actually invoking the stock recovery (or whatever recovery you may have flashed with NV Flash) and that then runs the update.zip file on the root of your internal sd. Since stock recovery is set to factory reset your phone when you invoke recovery, I worry that if the upate.zip got messed up you might wind up factory resetting your phone. I tried ROM Manager (which doesn't work until you use NV Flash at least once anyway) and booted from it into recovery once. It was scary enough for me I immediately uninstalled it and got rid of its bogus update.zip.
Click to expand...
Click to collapse
Yeah, when I played with ROM Manager I really didn't like it, which is why I uninstalled it after playing around with it for five or ten minutes.
At this point I'm running stock GB on my phone, and I used Titanium Backup to remove the bloat (NOVA demo, T-mobile Mall and TV,) and the phone is running nice and smoothly. I'm a little confused about one thing though: Titanium backup is to backup apps/settings for this ROM, right? Whereas if I want to backup the ROM itself before putting CM7 on my phone I do that by booting into CWM and choosing the backup/restore option. Is my thinking here correct?
dmj2012 said:
Yeah, when I played with ROM Manager I really didn't like it, which is why I uninstalled it after playing around with it for five or ten minutes.
At this point I'm running stock GB on my phone, and I used Titanium Backup to remove the bloat (NOVA demo, T-mobile Mall and TV,) and the phone is running nice and smoothly. I'm a little confused about one thing though: Titanium backup is to backup apps/settings for this ROM, right? Whereas if I want to backup the ROM itself before putting CM7 on my phone I do that by booting into CWM and choosing the backup/restore option. Is my thinking here correct?
Click to expand...
Click to collapse
Yes, but you should not have used Titanium Backup to remove bloat. That defeats one of the purposes of keeping the rom stock. Once the bloat is removed you can not get future OTA updates, if any. They will download but the install will fail as it checks for all original files have remained untouched. There are apps that can freeze bloat and when you get an OTA you unfreeze them so you can apply the OTA update. To backup the ROM you must go into Clockworkmod Recovery. Also I recomment other apps such as Astro for backing up apk files. In my experience, Titanium Backup just makes a mess of everything and usually the restores fail.
jboxer said:
Yes, but you should not have used Titanium Backup to remove bloat. That defeats one of the purposes of keeping the rom stock. Once the bloat is removed you can not get future OTA updates, if any. They will download but the install will fail as it checks for all original files have remained untouched. There are apps that can freeze bloat and when you get an OTA you unfreeze them so you can apply the OTA update. To backup the ROM you must go into Clockworkmod Recovery. Also I recomment other apps such as Astro for backing up apk files. In my experience, Titanium Backup just makes a mess of everything and usually the restores fail.
Click to expand...
Click to collapse
My phone's never been able to connect to the servers for an ota update anyway. I'm not sure but maybe this is because I installed Gingerbread using LG's desktop app rather than waiting for t-mobile to push the update to me. In any cas, I am planning to flash a custom rom soon. Been thinking CM7 but that's just because it's the only once I know much about. I'm gonna start researching how to install it.
If I ever want to go back to stock after flashing a custom rom there are stock roms available for download, right?
Also what exactly does freezing an app do? I noticed Titanium can do it but is there another app I should look at for freezing an app?
Sent from my LG-P999 using XDA App
dmj2012 said:
Also what exactly does freezing an app do? I noticed Titanium can do it but is there another app I should look at for freezing an app?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Freezing an app makes it invisible to the system without deleting it. OTA updates requires that no system files have been deleted or changed. You can defrost them at any time and the system can see them again. It is a much preferred method over deleting for many reasons. Titanium Backup uses a different freeze method than other apps, and some other apps can freeze some programs that Titanium Backup cannot freeze, such as Amazon MP3. I use Bloat Freezer and some people I know use App Quarantine. They are free versions of both on the Android Market.
dmj2012 said:
Also what exactly does freezing an app do? I noticed Titanium can do it but is there another app I should look at for freezing an app?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Anttek App Manager (free) from the market can freeze anything. Also has a couple of other nice features.
Hey I backed up my original gb before I did anything to the phone so as long as I restore that nandroid I will be fine to get updates right?
ROM Manager works fine even if you NVFlash a recovery.
jcbofkc said:
Anttek App Manager (free) from the market can freeze anything. Also has a couple of other nice features.
Click to expand...
Click to collapse
Thanks man. I love this app. Very useful and a nice, clean layout. Sticking with this for my freezing needs.
dmj2012 said:
Also what exactly does freezing an app do? I noticed Titanium can do it but is there another app I should look at for freezing an app?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
When you freeze an app it acts for all intensive purpose just like it was removed (ROM will not see it, market won't see it, and any apps that rely on it won't see it either) but its still there.
Advantage to removing an app: frees up space
Disadvantage: harder it get it back, can cause problems, fc's
I have found that freezing is the way ta go..
I use mybackup pro from market works great and very easy to navigate
Sent from my LG-P999 using xda premium
Ok hi everyone, pretty new to the Inspire, although not to Androids and ROM flashing. Actually I'm a bit of an addict. Anyway I'm successfully rooted, so far have run CM7, MIUI, and currently Revolution. So here are the questions I have come up with so far, and haven't seen this asked as I've been poking through the threads past couple of weeks.
1. ROM Manager, it was a must on my prior phones, and I have the premium version, but is it usable on the Inspire? I noticed right away that the Ace Hack kit automagically installed Clockwork recovery, is it OK to update CWM from within ROM Manager? Is there anything in there for us? My most recent phone was the Droid Charge, and you would seriously mess up your phone if you did that. They don't seem to have CWM official support.
2. I noticed that my latest ROM, Revolution, brought with it a different recovery 4EXT (or is it EXT4?) ASSUMING that the answer to question 1 is yes, can I flash CWM over it? From ROM Manager? Not that this flavor of recovery seems to have anything wrong with it, but most ROMS specifically mention "flash in CWM" so I don't want to mess things up from the get go the next time I flash something.
Appreciate any input folks
Sent from my HTC Inspire 4G using Tapatalk
Quick and dirty answer-Yes.
Rom manager is very useful on the inspire. Also using the premium version, and it's the only way to fly. And as to the 4EXT recovery, it changes how the files are saved. Wouldn't worry about flashing it, as it works just as well as the stock version of recovery.
One thing I like about the 4EXT Recovery Control app is that it lets you verify the md5 checksum of your rom backups. I'm not sure if the premium version of ROM Manager does that, but the free version didn't. Or if it did, I never saw that option. Before I started using 4EXT, there were a couple of times where I went to restore a backup and CWM would say the MD5 didn't match. Having already wiped data before attempting to restore, I was stuck flashing a fresh ROM and starting from scratch. Now with 4EXT Recovery Control I can check the md5 of my backup before I boot into recovery and be sure that the restore will work.
I have looked really hard to find the answer to this, but I couldn't find it.
I have a HTC EVO Shift, which was already flashed to Boost Mobile before I bought it.
After looking at the Boot Animations and apps, I realized the phone was also running the MikShifted-G ROM.
I have been using the phone for some time now, but after I found that my phone was not getting the upgrade to ICS, I decided that I wanted to switch ROMs, especially ones that were ICS and stuff.
I followed many tutorials and I have done the following:
-I have rooted my phone.
-I have installed ROM Manager, and I have gotten ClockWorkMod to work.
-I backed up my data with the backup option.
Here are the questions I have:
-It says on most ROMS to "wipe everything." If I choose to Factory Reset/Wipe All in ClockWorkMod, will that un-flash my phone back to Sprint? I do not want to factory reset if my phone will not run on Boost Mobile, hence it is a lot cheaper.
-If I install another ROM and decide to go back to the ROM my phone used to have, does installing ROM Manager again on the new ROM allow me to use the backup I made to go back to how my phone used to be?
Thanks,
Sarcasticphoenix
I can't say for sure but doing a full wipe and flashing a ROM shouldn't have any affect on your phone working with boost. Search the EVO threads, I'm sure you'll find a lot of people on boost flashing various ROMs and kernels.
As far as actually flashing the ROM, you should get familiar with using recovery manually, not just relying on ROM manager to do everything for you. Here's a nice guide on how to flash ROMs http://forum.xda-developers.com/showthread.php?t=1266885. Be sure to make a nandroid backup before flashing any ROM (If you already made a backup using ROM manager it can be restored either via recovery or the ROM manager app.)
Also consider using Dread 7 Us's modified recovery. Based off Clockwork Mod but with some great differences: super wipe where you can choose which partitions to wipe and do it multiple times automatically(much less tedious than Clockword Mod's wipe each once method) and it also removes the ton of 'NO's' you have to scroll through to confirm an action in Clockwork Mod and others upgrades I don't recall.
http://forum.xda-developers.com/sho...RECOVERY] CW-Enhanced [v1.1b] Updated 5/22/12
Flash it just like Clockwork Mod but do a nandroid before just in case. Make sure to also flash the updated one as the first version had MD5 check issues.
roms
if i put a rom into my phone and do a backup... can i go back to rooted stock and put another rom and i i dont like it restore to the other rom?
tello2323 said:
if i put a rom into my phone and do a backup... can i go back to rooted stock and put another rom and i i dont like it restore to the other rom?
Click to expand...
Click to collapse
As long as you have s-off nandroid restore will work fine. As far as the roms it depends on if the roms have the boost mobile apn's in them or not. A.F.A.I.K. CM7 roms and variants have the most apn support. Might want to do a search on google if cm7 supports boost or not.