Database Develop

[Q] Does ROM Manager back up the ENTIRE phone?

Silly noob-like question, but I wanted to make sure before I continued messing with my phone.
Does ROM Manager back up EVERYTHING on the phone? For example, I backup my rom. Move the backup file onto my pc. Then I screw around with roms, lag fixes, etc. and totally screw it up. If I "restore" the backup made by ROM Manager, will all my apps, settings, desktop, data files, etc be exactly as they were before I started screwing around?
Or, would I need to use Odin to load the same ROM as that which was backed up and then run Rom Manager Restore?
Thanks!

Yes it does
Sent from my SAMSUNG-SGH-I897 using XDA App

Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.

Deca4 said:
Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.
Click to expand...
Click to collapse
Actually I am trying to figure out the same thing. I made a backup before I started messing around with lag fixes, different roms and so forth. Then the other day I tried to restore a rom it didn't work. Eventually I soft bricked the phone and had to make the USB Jig to get it working again. Needless to say I am very intrigued with what exactly Rom Manager does backup and its limitations but I can't seem to find it anywhere. I am thinking the reason my backup was screwed up was because of a lag fix, only problem is I can't remember what lag fix I had on it when I did the initial recovery.

Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.

diablo009 said:
Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.
Click to expand...
Click to collapse
Interesting, it would makes sense in what you are saying. My error that I go was when I went from my original JH7 backup, installed a rom based on JH6 and then tried to install my original backup. I might have to try JH6 roms and see if I can restore to them easily or not. I will have to wait for Micro USB cables to come in as I don't have a spare since I used my only cable to make the JIG.

The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.

I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App

peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
This is what I have read about it as well

Voodoo
There is also a different version of CWM Recovery (what Rom Manager uses to back things up) for the voodoo lag fix.

tnerb123 said:
I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It works. I backed up and restored a few variants of Froyo ROMs.

peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
How do I backup these? Is there any way?

If Ron Manager does backup the kernel and modem why would so many people have problems restoring back to different Roms? This is why I am so puzzled with this software.
Sent from my SAMSUNG-SGH-I897 using XDA App

Rom Manager can backup EFS folder ??
i lost my imei and the only backup that i have its from Ron Manager

Absolutely it does there!

Maybe I'm old fashioned, but best bet is backup from recovery. Saves everything down to browser login data. Can't go wrong with a full backup! I make one every time I flash just about anything.
Sent from my SGH-I897 using xda app-developers app

Rom Manager vs CWM Recovery
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:

dobi3 said:
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:
Click to expand...
Click to collapse
Agreed!
Sent from my SGH-I897 using xda app-developers app

[Q] on flashing rom to rooted phone

Hi all, I'm going to not try and sound too noobish, but after reading for hours I still have a couple questions. I have a Moto Droid with 2.2 Froyo that I just rooted. I use Rom Manager last night to put on Cyanogen but when it booted I had lost all apps, contacts, market so I reverted back to stock. I just got titanium backup pro which I read should load all my apps/contacts etc once I load Cyanogen? I just want to make sure I'm running the programs in the correct order.
One other issue I have is that I am currently using Setcpu to overclock to the max it's allowing which is 800 megahertz. Do I need to uninstall this before I load Cyanogen? Because I know that it is going to max me out at 600 unless I load another Kernal to go higher which I would like to do, which is another thing I was looking for instructions to do but having difficulty at least for my model.
I've found some P3 kernals, I'm not sure if theyre compatible with Cyanogen or how I would know which one to get though.
Any help is appreciated, I'm new to the rom stuff but learn fast.

oh man, I was hoping someone would know

anyone? please?

Allright well I've figured out which P3 kernel I am going to use. My latest issue is when I install Cyanogen, all my apps except for Rom Manager and Terminal Emulator are gone. Now I backed up everything with Titanium, but that is gone as well. It seems like a catch 22 to try and restore your apps and the restoring app itself is gone. Any ideas?

Go download titanium from the marketplace and reinstall. Your apps will then be able to be restored. I run cm 6.1 RC4 and use the P3droid 250/1100 MHz kernel. You'll also want to install setCPU from the marketplace to set the cpu speed profiles. Good luck! You'll really dig it once you have everything dialed in.
----
Sent From My AI using my own mediocre intelligence.

Hey Maxnicks, maybe you know the answer to this one as well:
I've only been using CM since 6.0 and I want to finally update it to 6.1 but just a few questions. As far as updating goes, do you have to wipe your data in Rom Manager like you would do going from stock to CM? 2nd, when you update, do you lose all your apps like you do going from stock to a new rom? I used titanium backup before to restore after 6.0, but this time I'm going to update the rom through Rom Manager so it's a little different. Last,I have the P3 Kernal overclocked, will this stay at my current settings or do I need to reinstall it after 6.1 is on there. Sorry for the questions but I tried googling and not much exists comparing CM update vs installing it over stock.

First make a back up of current rom in rom manager in case want/have to flash back. When updating same rom, might be able to get away without wiping, try without if any trouble with 6.1 flash back to previous then try a wipe. On kernel you will have to go into recovery to flash back to the p3 as all roms come with one, usually top out at 600/800 or so. Once flash new rom with gapps all apps should download thru market. I currently am running 6.1 with p3 125-1100 kernel with no problems other than usual launcher re-draw. Good luck
Sent from my Droid using XDA App

[Q] Phone Force Closes, Just Flashed Cog 3.01

Hey guys,
I'm brand new to this stuff, and I've searched the forums to the best of my abilities and I don't see a fix yet.
I just flashed the new Cognition ROM and used Titanium Backup to "restore all apps with data". During this process, it went through my apps one by one, and asked me if I wanted to install them or cancel and not install them. I picked and chose which apps I wanted to keep and which to discard. As an aside, the apps in question were things like games/puzzles for my kid to play with, and games and such that I had downloaded from the Market to try out but forgot to uninstall.
So, after everything was restored, I started to test stuff out, and everything works...except incoming calls. I get the "The process com.android.phone has stopped unexpectedly. please try again. force close"
Is there any fix for this besides going back to stock and retrying the new ROM? If there is a solution to this a link to the thread would be greatly appreciated.

Thanks for posting this, I am having the same problem. Any help would be appreciated.
Also, what is the best way to go back to stock?
Rogers I-896

This is for rogers i896 2.2
http://forum.xda-developers.com/showthread.php?t=905042
This is for AT&T i897 2.1
http://forum.xda-developers.com/showthread.php?t=731989

mattio781 said:
This is for rogers i896 2.2
http://forum.xda-developers.com/showthread.php?t=905042
This is for AT&T i897 2.1
http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
So I use ODIN to go back to completely stock and try the ROM again, but use the "restore missing apps with data" option?

You should click restore missing apps + data. That should fix it
Sent from my phone

Maybe I'm just picky or don't trust TiBu completely, but I always restore my apps individually. Never had a problem. I've been back and forth between Cognition and darkys ROMs and (of course) stock on my AT&T Cappy.

Yup restore back to stock... and if you had issues with doing a TiBu restore with "Apps and Data" I would recommend just using "Apps Only" option in TiBu.
BUT... I would test the ROM out before doing the restore to ensure it's not a ROM issue first.

If you do not wish to go back to stock, there were quite a few suggestions in the Cog 3.0x thread on this issue. A few people in that thread simply had a bad flash. One just needed to do a good solid reboot to fix it. Another suggestion was to clear the dalvik and cache using ClockWorkMod Recovery (red version). Lastly, lots of people FC'ing with the phone process were experiencing problems due to the ogg files in phone.apk being compressed when they should not be (reportedly) and was fixed by disabling the "Call Status Tone" in settings/call settings/all calls/call status tone. One of these could be your problem.
If you wish to just try again the simple way, it would probably be your best bet to Odin back to stock, do the master clear (it seems to be a topic of debate if this is the best thing to do, but it is mentioned in a few different tutorials), and flash again. Then TiBu to restore your apps+data (as mentioned... no system data, just app data) again.
If you wish to try to fix the problem, one place to start might be a fixed phone.apk in the Cog 3.0x thread in the Development section for Captivate. It is posted by Andrewk_77 somewhere between page 85 and 90, I think (sorry, I've been trying to keep up with the reading of that thread for days in order to head off any problems I may run into with Cog 3 and it's kinda blurring together). Otherwise you'll have to try to search out other solutions in that thread.
Edit:
Found that post:
http://forum.xda-developers.com/showpost.php?p=10685612&postcount=861
I know that they don't seem to be describing the exact same problem, but might be worth a shot.

I reflashed Cog 3.02, didn't use TiBu to restore anything, just set it up myself again. Phone works fine now.
Though I do have a question about flashing back to stock: would I just put the stock ROM (in this case Rogers 2.2) onto the SD, and flash it using CWM? Or do I need to use ODIN, in which case I would get the AT&T ROM? Thanks for helping a newbie out.

A few questions regarding Nookie Froyo

I have everything the way I like it currently with the stock ROM. Apps, widgets and other customized things
1. Is it possible to backup everything, then restore everything to the 2.2 ROM using Ti Backup? Restore all apps, widgets, wallpaper, etc?
2. Flashing the ROM to internal eMMC, can the NC be restored to stock via the 8x reboot method?
That's all I'm wondering for now, I'm sure there will be more.

Widgets cannot be restored due to a system limitation. Second, speaking from firsthand experience you don't want to take information backed up on 2.1 and restore it to 2.2. I did that with my evo and I thought the phone was dying...everything was force closing and I had to reflash the rom. It was probably my restoring of the system settings(idiot move) that caused the problems but I wouldn't take any chances.

Yea, just me being lazy...
What about the notification bar? I like that is on the bottom. Can that be changed on a vanilla Froyo install?

bump..........

Hmmm...to get the notification bar on the bottom will probably take some hella coding but it can be done. Obviously B&N did it, also Acer does it on their Liquid ROMs (http://forum.xda-developers.com/showthread.php?t=903470) but don't count on it being done here.
EDIT: That link I posted was just an example. DO NOT flash it on your nook.

we dont really bump your own posts here...

[Q] moving from 2.2 roms back to 2.1

I have seen a few people mention the need to flash a 2.1 sbf when wanting to change from a froyo rom back to an eclair rom. I had been using various 2.2 roms (mostly shadowmod and APAC) but had strange issues with my screen changing funky colours so I just restored my original 2.1 from the nandroid I made before I applied any custom roms.
Am I going to run into any problems with files hanging around and screwing things up doing it this way?

Lleviathan said:
I have seen a few people mention the need to flash a 2.1 sbf when wanting to change from a froyo rom back to an eclair rom. I had been using various 2.2 roms (mostly shadowmod and APAC) but had strange issues with my screen changing funky colours so I just restored my original 2.1 from the nandroid I made before I applied any custom roms.
Am I going to run into any problems with files hanging around and screwing things up doing it this way?
Click to expand...
Click to collapse
No problems at all, a nandroid backup is like a ghost or acronis disk image, it fully restore the device to the exact state it was at the moment of the nandroid backup.

Perfect, many thanks.

Those funky colors are from the DSI erros, but the new CM7 ROM has an option to avoid those DSI errors and the new Miui ROM has it buildin. So if you want to use GB then I recommend those ROMs