Database Develop

Confused about FRF72

<<Reposted from QA, couldn't move the post myself>>
I'm confused with FRF72, why is it only 2MB?! That is very small. Is this meant to patch the earlier FRF50 which I have running right now?
Even if it is/or isn't a patch, has anyone tried to run the ROM ZIP WITHOUT WIPING so to save from having to restore Titanium backup? I can't be bothered with the whole process until the weekend is over, unless I can upgrade without wiping. Please let me knwo if any of you have attempted to do that and have you succeeded? Thanks.
When I upgraded 2.1 to 2.2 and was curious, I didn't wipe and the 2.2 successfully booted, and everything all the settings and apps were intact, but it was force closing every single time I tried to run any app, so after that, I wiped, and then it was fine.
I don't want to go through that whole process again though, this time being its 2.2 older beta to newer beta, so it might work without a wipe right?

if u dont wipe u will be stuck in a boot loop. i did a nandroid and then flashed it only to land in the loop. then i wiped and flashed and all was well. thank goodness for nandroid

[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]Nexus 1 not returning to Factory Reset

I have been trying for the past 3 days to return my N1 to the stock program. I have unlocked the phone and i was enjoying rooting for the past 8 months. I installed many different builds like Modaco, LeoGingerbread, Rodrigues MIUI, MicroMod Gingerbread and then Cyanogen Mod 7 (build 36), that is when it started to have tons of force close and the programs would stop running.
I always cleared the phone before i installed a new build.
I decided to return the phone back to the original factory settings and start fresh but it is giving me some problems.
I have used many different version of the PASSIMG files on XDA but i always get an issue with an Android program stopping unexpectedly.
At first it was the Settings that did not work, i fixed that.
Now it is the Calendar AND Market who keep force closing.
I have been trying for the past 3 days looking for a solution but i have come to the end of my patience.....
If ANYONE has a solution, i would love to hear from you.
Right now i am just thinking of getting a new phone but i love my Nexus 1
This is the first phone i ever rooted so my knowledge of rooting is limited to the 8 months of installing different builds. I never created a program or modified any.
Thanks
Phone status right now
Canada
Nexus 1
Bell Network
HBOOT: 0.33.0012
Radio: 4.04.00.03_2
Dec 17 2009,13:05:23
Firmware: 2.1 Update1
Baseband: 32.26.0024U_4.04.00.03_2
Kernel version: 2.6.29-01117-g4bc62c2
Build number: EPF30

I am going to take a stab in the dark here...are you by chance using ClockWorkMod recovery? If so did you upgrade to 3.0.0.5? Assuming this is correct you are in the same boat as I was...your not going to like it but if you are first go back to 2.5.1.4 or older. Next you will need to format your entire SD card and repartition it, then do a restore. That should work. Hopefully you have backups of your SD card contents... If a restore doesn't work still then you may need to format and partition again and do a fresh install. I lost a lot of sleep the other night trying to figure out WTF happened. It seems that something it 3.0.0.5 changes the SD-EXT and cannot be repaired without a format. I was mad enough about the whole situation that I have ditched CWM and am now running RA.

Galloway said:
I am going to take a stab in the dark here...are you by chance using ClockWorkMod recovery? If so did you upgrade to 3.0.0.5? Assuming this is correct you are in the same boat as I was...your not going to like it but if you are first go back to 2.5.1.4 or older. Next you will need to format your entire SD card and repartition it, then do a restore. That should work. Hopefully you have backups of your SD card contents... If a restore doesn't work still then you may need to format and partition again and do a fresh install. I lost a lot of sleep the other night trying to figure out WTF happened. It seems that something it 3.0.0.5 changes the SD-EXT and cannot be repaired without a format. I was mad enough about the whole situation that I have ditched CWM and am now running RA.
Click to expand...
Click to collapse
I sis upgrade to the ClockWorkMod 3.0.0.7 and that is when the problem all started.
I downgraded to the 2.5.4 version and i was able to install the CyanogenMod 36 and then it really went all bad.
I was so frustrated that it was not working that i formated (and i did back it up) my SD card. Then i did what i said and i am still having issues.....
Where did you get and how did you install RA? I was used to the CWM and i really liked it until they upgraded to version 3.
Thanks

Look in Developer section.
Take your SD card out, reformat it in Windows, then put it back and repartition for EXT, if you're using old Apps2SD (/A2SD/Apps2EXT).
Wipe everything.
Install any ROM.
Enjoy.

[Q] Never Successfully Restored a Nandroid

Sorry if this has been asked before but I have searched and didn't find any answers.
I have never been able to restore a nandroid backup on the Galaxy S. I go through the restore procedure in recovery and everything seems to restore correctly, no errors reported, says restore successful, but when the phone boots up from recovery it hangs on the boot screen.
I've tried with lots of different roms/kernels. I've wiped thoroughly before restoring. I'm even trying to restore from the same version, i.e. JVH or JVP, always the same result. I'm not trying to restore between cm7/samsung roms or froyo/gingerbread or even different versions. An example is, I was on Darky 10.1re. I did a nandroid. I tried a few other roms (F1, GingerReal, Tweaky), tried to nand back to Darky's, appears to restore without problems until the reboot where it hangs on boot screen. Also tried to restore to nadroids of the above roms with the same results.
Can anyone tell me where I'm going wrong, I'm sure I'm missing something really obvious as nobody else seems to be having trouble with backups.
Thanks.

I could imagine it would be hard to point out what the exact problem is, unless someone has experienced this issue before. Which I haven't, sorry. Not on my SGS, nor on my SGS2. But it sounds like a compatibility problem to me. You say you've never been able to restore, have you had the same problem with Darky ROMs prior to 10.x, perhaps 9.5? Have you used Darky's Dark Core kernel along with it?

The same thing is happening to me. Used to nandroid restore on froyo and never had a problem. The last 2 times that I tried to restore (with Ginger 2.3.3 and 2.3.4) I had problems, both times with Criskelo´s rom and Darkcore Kernel. The restore begins normally but suddenly stops and there is no way to revert the semi-brick other than odin. BTW, I never use lagfix.

Used nandroid backup and restore successfully on gingerbread on both speedmod and galaxian kernels
Sent using geek power

I have same problem and i ended using nandorid backup which is very usefull.
I think this started at beginning of Gingerbread kernels using.

bitmaster2000 said:
I could imagine it would be hard to point out what the exact problem is, unless someone has experienced this issue before. Which I haven't, sorry. Not on my SGS, nor on my SGS2. But it sounds like a compatibility problem to me. You say you've never been able to restore, have you had the same problem with Darky ROMs prior to 10.x, perhaps 9.5? Have you used Darky's Dark Core kernel along with it?
Click to expand...
Click to collapse
Thanks for your suggestions. The first rom I installed after buying my Galaxy S was the current Darky one at the time, v10 rc something. Didn't try the older ones. At first I always used the Dark Core kernel, even with other roms. Still couldn't restore.
I've also tried a mixture of roms/kernels since then with no luck with the nandroid.
Could it be something to do with the recovery? I noticed different roms/kernels install a different recovery. Maybe it's only possible to restore using the same recovery as was used to take the backup? But if this was the case, surely other people would be having the same problem?
Thanks.

eggshaped said:
Thanks for your suggestions. The first rom I installed after buying my Galaxy S was the current Darky one at the time, v10 rc something. Didn't try the older ones. At first I always used the Dark Core kernel, even with other roms. Still couldn't restore.
I've also tried a mixture of roms/kernels since then with no luck with the nandroid.
Could it be something to do with the recovery? I noticed different roms/kernels install a different recovery. Maybe it's only possible to restore using the same recovery as was used to take the backup? But if this was the case, surely other people would be having the same problem?
Thanks.
Click to expand...
Click to collapse
Darky kernel had a restore problem once but they solved it now.
"Changelog 2.5:
Fixed Nandroid Restore through CWM" from darky forum.

yken said:
Darky kernel had a restore problem once but they solved it now.
"Changelog 2.5:
Fixed Nandroid Restore through CWM" from darky forum.
Click to expand...
Click to collapse
Yes I remember reading about that. That's what I put it down to in the beginning, but now it's been fixed and it still doesn't work for me. Not even with other kernels.
Well, it's not the end of the world I suppose. Just makes me more reluctant to try different roms as I'm too lazy to go through the whole odin/flashing/restoring process every time lol.
Thanks for your suggestions guys

With Dark Core kernel 2.7.x and 2.8 i have the same problems when i'm on rfs, backup function is ok but restore doesn't work. With ext4 conversion enabled backup and restore work as they should.

I've found a solution, just in case anyone else is having the same problem this is how I got around it.
I downloaded and installing the latest cwm using Rom Manager, so any backups are taken on 3.0.0.5. When changing roms I had to download and install the same recovery with Rom Manager and restore using the same 3.0.0.5. For some reason it only works when using rom manager. If I try to restore manually in recovery it doesn't work. If I try to restore with any other recovery version it doesn't work. So for me my nandroid backups only restore between the exact same recovery versions.
Sounds fairly obvious now, after thinking about it lol, but this has been giving me a major headache for weeks now.

CM10 Helly Bean V10 -- Bootloop!

Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!

Worse than I thought!
So It's worse than I thought... I gave up and re-flashed slim (ICS)... and the same problem still exists... boots up, looks normal, can't touch anything.... eventually it reboots....
Suggestions?
Would ODIN flash do anything different? I9000 bootloaders?
ScruffMcG said:
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Click to expand...
Click to collapse

sorry I'm just going to post twice so I can post to development...

yeah... 10char

What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
Slimmed Down V10 by cbalt
Wipe Data/Factory Reset/Wipe Dalvik
Flash http://www.mediafire.com/?9p212pempybwnj3
Then Flash http://www.mediafire.com/download.php?bdjabcmobz6aw6k
Then Fix Permissions
Then Reboot
Click to expand...
Click to collapse
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!

So you think w/bootloaders will help?
I have flashed every odin w/o bootloaders that I have access too and all get me stuck at ATT bootscreen....
Little hesitant to reflash my bootloaders since I was/am already on GB bootloaders, but if it might help I may have to do it...
I actually was on that JB version (but with the normal gapps b/c I wanted google now...)... now I'm on no version of anything hahah
takeoutttt said:
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
Click to expand...
Click to collapse

I met a problem. I do not know wether or not it is common. The phone will reboot by itself sometimes.
Do you have the same problem?

same here
seems as though many of the problems experienced by one are shared by the other
this is logical as they share many common points including the same partition and both jellybean derivations
I was having issues... accelerometer and audio issues.
All came out right as rain after flashing back to stock and reflashing
ScruffMcG said:
yeah... 10char
Click to expand...
Click to collapse