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
Related
So I was running Enomther's 1.8.1 which was one of my favorite builds yet. When Froyo was released I switched to Modaco's Froyo online kitchen build, and then being impressed but missing my trackball colors, and tweeks I switched back to Enomther's 1.9.2.
My three questions are:
1)How do you backup your home screens? It's so annoying to reset them up which takes me an hour at least everytime I switch roms. I figured out how to back up my apps which Linda App Manager does perfectly.
2)When I went from Enomther's 1.8.1 to Madaco's Froyo it also updated my radio, so when I went back 1.9.2 did that reset my radio back to the original? Or keep the Froyo?
3)I know I can do a Nandroid backup but that doesn't restore between roms does it? It reapplies the previous rom right?
Thanks for the help!
Homotechual said:
So I was running Enomther's 1.8.1 which was one of my favorite builds yet. When Froyo was released I switched to Modaco's Froyo online kitchen build, and then being impressed but missing my trackball colors, and tweeks I switched back to Enomther's 1.9.2.
My three questions are:
1)How do you backup your home screens? It's so annoying to reset them up which takes me an hour at least everytime I switch roms. I figured out how to back up my apps which Linda App Manager does perfectly.
2)When I went from Enomther's 1.8.1 to Madaco's Froyo it also updated my radio, so when I went back 1.9.2 did that reset my radio back to the original? Or keep the Froyo?
3)I know I can do a Nandroid backup but that doesn't restore between roms does it? It reapplies the previous rom right?
Thanks for the help!
Click to expand...
Click to collapse
This should be in Q&A. This has nothing to do with development.
Any help would be appriciated.
Homotechual said:
My three questions are:
1)How do you backup your home screens? It's so annoying to reset them up which takes me an hour at least everytime I switch roms. I figured out how to back up my apps which Linda App Manager does perfectly.
2)When I went from Enomther's 1.8.1 to Madaco's Froyo it also updated my radio, so when I went back 1.9.2 did that reset my radio back to the original? Or keep the Froyo?
3)I know I can do a Nandroid backup but that doesn't restore between roms does it? It reapplies the previous rom right?
Click to expand...
Click to collapse
1 - There are multiple backup programs available on the market. Backup for Root Users has an option to backup the home screen and other things. Basically it just moves the .db files and puts them back, which can be done manually if you know where to look.
2 - Nandroid does not backup the radio.
3 - Restore what? Nandroid wipes and reapplies the previous restore point.
A couple of days ago I was running:
* I9000XWJM8 firmware
* JH2 modem
* Xcaliburinhand I9000 v1.3 Voodoo kernel
* Tayutama Edition v1.1 Lite ROM
Then I decided to try the leaked Froyo, followed by COG 2.2
Before I left my I9000 configuration, I used ROM manager to do a backup.
After I finished with testing Froyo, I decided to go back to my previous configuration, so I one clicked back to JF6, and then restored my saved rom.
I was surprised to find that neither my JH2 modem nor my Xcaliburinhand kernel restored, it appears that only the I9000 rom restored.
I had thought, incorrectly it would seem, that using rom backup would do a complete backup of my phone, but now I think it only backs up the rom part (I guess that is why it is so named).
Does anyone know of an app that actually does a complete snapshot backup of the phone? Like a disk image or ghost utility on a Windows PC does? SOmething I can make a complete backup?
Thanks in advance!
1st and only bump on this. Hoping someone has an answer...
I don't believe that what your asking is possible...
Although, that's probably BS because everything that is possible was once declared impossible. So really, I don't know. It could probably be done, the question is though, who is going to dedicate the time to pursuing it?
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...
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.
Alright, I have been reading the forums, wikis, Q&As and stickies for a few days and I am getting ready to start playing with my cappy. I have a few unresolved questions which, for a non-noob will take a snap.
I am currently running 2.2 i897uckb1 on the Samsung-SGH-I897. It is rooted and unlocked. I purchased the phone in this state. The only major modification that I have made is the One Click Lag Fix (which worked awesomely). Here are my noobish questions:
1) I am running 2.2 and so I must have the bootloaders for 2.2 installed, is this correct?
2) The only reason to ever change the bootloaders, or flash with a rom that includes bootloaders, is to go from a 2.2 rom to a 2.3 rom. Is that correct?
3) What is the REAL advantage of moving to 2.3 roms? Will this change my life or am I likely to see just as neat stuff on the 2.2 roms?
4) Should I undo the One Click Lag Fix before monkeying with roms?
5) People always recommend flashing to stock before flashing to a custom rom. This is one of those things that seems to be taken for granted, what stock is. I can only assume that stock is the vanilla 2.1 rom that came with the phone when shipped. Is this correct and is this step really neccessary, as it seems a bit tedious to do before trying out a bunch of roms?
Thanks in advance!
1) Not necessary, but no way to know till you flash a GB and see if it works (I recommend just flash them t be sure).
2) In your case yes. People with older phones changed to GB bootloaders for the 3 button fix. Keep in mind that GB bootloaders are backwards compatible with froyo and eclair, they also work on AOSP.
3) Its just the next thing. I saw way better battery life on GB than I ever did on froyo (but thats a matter of opinion). Only negative is on gingerbread I saw little bit of a drop on fps. IMO if you are willing to take the risk of flashing bootloaders give it a go and try it, else you can go back to froyo.
4) Yes remove lag fix if you ever flash anything.
5)This is a so so thing. If you have ClockworkMod then most of the times doing a factory reset+ cache clear+ Dalvik cache wipe will do the same thing as flash to stock. In the off chance it doesn't "flash to stock" can be achieved by flashing any "stock" or leak "stock" in the site. You should always prefer ones with out bootloaders to be safe.
Thanks a bunch for the reply. Gald that I had almost everything right. Time to play!