Hey guys! I'm having a problem with restoring the back up via CWM. My fascinate is running DL30 froyo and now I want to go back to EA28 (previously backed up EA28 via nandroid). What happens is I don't have any problem restoring the back up file(EA28). Then after restoring process is completed, the phone stucks on the SAMSUNG logo(I hear the booting sounds though, typical). Well I don't know what I'm doing wrong. Could it because I'm trying to restore a different kernel or so? Let me know guys! Thank you!
Related
Earlier I rooted my phone and flashed it with Bionix Fusion. All went well and it was working just fine. Although after looking through the new rom I remembered I forgot to save my contacts.... I followed the instructions on installing bionix and I created a nandroid backup. Somebody who similarly forgot to save his contacts said to restore the backup sync the contacts to google and then flash the rom over again.
My issue is that I tried to flash my backup and now its been stuck on the Vibrant screen for the past 10 minutes. What went wrong?
please help and ty for your time
well because I couldnt get the nandroid backup to restore correctly I ended up just going back and flashing the bionix fusion rom again and its booting up just fine. Unfortunately I feel that I just lost all my contacts. Anybody have any ideas? Did my nandroid backup just get corrupt somehow? Is there anyways i can somehow get my contacts from the backup?
Whoever posted that must have meant that you should make a backup before flashing any rom. If yiu did that, you could have went back to that backup with all you contacts intact. Its too late now, hopefully google synced most of your contacts.
Sent from my SGH-T959
If you are running Voodoo lagfix, you have to disable the lagfix BEFORE restoring
i did do the backup before flashing. But i guess it just got screwed up somehow. I've never used any lagfixes either
Which version did you flash? I'm going to guess you used one that did not have a stock kernel (JAC/KK)... you would have to flash the stock kernel before restoring a nandroid backup from JI6 or JFD since IT has a stock kernel. The nandroid does not replace the kernel, hence why it would hang at the Vibrant screen.
s15274n said:
Which version did you flash? I'm going to guess you used one that did not have a stock kernel (JAC/KK)... you would have to flash the stock kernel before restoring a nandroid backup from JI6 or JFD since IT has a stock kernel. The nandroid does not replace the kernel, hence why it would hang at the Vibrant screen.
Click to expand...
Click to collapse
Do you mean oden when you say "flash the stock kernel"?
So i factory reset my phone (on stock), made a nandroid backup, then flashed one of bionix's roms. a couple days later i want to try another rom so i went into rom manager and chose to restore and picked the backup that i made earlier while on stock. It completed the restore process and went back to the clockworkmod recovery screen, then i chose reboot. now the phone sticks at the vibrant screen, but makes the bootup sound. weird huh? do i have to use odin? or is there somehow i can still restore using clockworkmod. i am able to still get into recovery btw . if the only way to fix is thru odin, can someone link a current post with instructions? thanks peeps.
BTW i was on JI6 when backing up, and i read fusion 1.1 runs on JI2 so......help?
Feel free anyone to correct me since I'm also fairly new at this, but it sounds like you may have soft bricked your phone. The way I understand it is that you needed to flash back to a stock kernel before restoring your stock ROM backup.
Getting back to a stock kernel can be done by either flashing a ROM that uses/applies it (they usually state what kernel they're using), or just flashing the stock kernel yourself, which can be downloaded here: http://forum.xda-developers.com/showthread.php?t=733792
Anyway, here is a thread that explains ODIN: http://forum.xda-developers.com/showthread.php?t=810130
Good luck! I fear I'll be in your shoes at some point, so hopefully I helped a little.
This is my second time trying to restore a backup using clockwork and it just hangs on the vibrant screen. The first time I forgot to disable voodoo so that was the problem then, but this time I was on obsidian froyo rom and had issues where I was not able to get any data reception (3g/edge) so I figured to try and got back to stock to see if that solved the issue but no I'm stuck on vibrant screen. It went through the process of restoring then rebooting but it got suck. I am very frustrated because I can't never get it to work so what is the point of backing up stuff. I will be using odin again to restore and not use backups anymore. Just wanted to vent as I am very frustrated about this. If there is some out there that could shed some light as to why I keep getting stuck on the vibrant screen I would appreciate it.
Will be getting a replacement phone from my date issue, and yes my voice still works just not data part.
Sent from my T-Mobile G1 using XDA App
Froyo has a differnt kernel than eclair. You were trying to restore an eclair build, but you did not flash the stock eclair kernel first.
s15274n said:
Froyo has a differnt kernel than eclair. You were trying to restore an eclair build, but you did not flash the stock eclair kernel first.
Click to expand...
Click to collapse
what eclair kernel can i use for the future???
i odin back to JFD and my 3g/edge is working again i wonder why i lost it?
Probably the easiest thing to do would have been to flash a new custom rom with the kernel included, like Fusion/Bionix.
You could have flashed the stock kernel and then restored a JI6 nandroid too though I imagine. I've not tried yet. The stock kernel can be found in my signature or in the development section. I have a copy on my internal memory just in case.
So i'm pretty noob with all this stuff but i finally decided to try flashing my phone and, in the end, ended up with a "bricked" (or the extent a vibrant can be bricked) phone. Thanks in advance for the advice.
what i did
I followed the flashing guide in the sticky post "** GUIDE - TIPS - TRICKS ** Last Update 12/03/10 ** READ BEFORE ASKING" and everything worked great. I downloaded Rom manager, made a nandroid backup of my stock rom, flashed it with bionix fusion and everything worked great. I didn't do the titanium backup and there was an app that i needed to use the next day so on the way to work, i decided to restore back to the stock thinking that i could go back for the day, use the apps that i needed and when i got home got home, back up my apps with titanium back up and restore again back to the bionix fusion. So i did that. I went to rom manager and I first backed up my bionix fusion rom and then tried to recover my stock rom. When the phone restarted, it didn't go past the vibrant/samsung screen.
The question...
what went wrong? based on some reading i think it has something to do with the kernel but i'm not really sure.
but the real question is, how do i avoid from this happening again? did i do the recovery wrong? what's the best way to unbrick my phone back to stock without losing any data on the phone. is it possible????
at this point, i can go into download mode. what should be my next move?
Thank you again if you can provide any insight.
*edit*
So looking at some posts, I looks like I need to flash the stock kernel. can anyone tell me how to flash just the kernel using odin? I've never used it and I can't seem to find anything on flashing just the kernel. Thank you.
Problem SOLVED!
ok. not completely solved T_T.
What i've done.
I've flashed back to stock vibrant firmware and that works fine. When i try to restore my nandroid backup, and it reboots, I get stuck back to the same place i was. I made two nandroid backups and tried them both but neither of them work. am i doing it wrong? I have even re-rooted my vibrant and downloaded rom manager again and tried it through there and still get the problem. have tried it about 4 times now with no luck.
Again, any help is appreciated.
Nandroid doesnt replace the kernal
Sent from my SGH-T959 using XDA App
Exactly, nandroid doesn't replace the kernel. If you want to run a nandroid restore, you have to either flash the rom the nandroid was created on, then restore (safest imho), or flash a compatible kernel for the rom from which your nandroid was created, then run your nandroid restore.
Sent from my Vibrant running Macnut R13 w/JK6 Modem and Black Froyo
Pretty sure this was in the sticky too
I tried finding someone with my particular problem but I couldn't so I apologize in advance if this has been posted before.
I tried out MIUI V5 today and I cannot restore back to my SC2.9 Voodoo.
When it boots everything and it's brother force closes over and over again.
I noticed that this is a problem people get when trying to restore back to a NON Voodoo rom.
But as far as I can tell the MIUI v5 runs on a Voodoo kernel and I was trying to restore back to a Voodoo rom.
Any help is greatly appreciated.
finakechi said:
I tried finding someone with my particular problem but I couldn't so I apologize in advance if this has been posted before.
I tried out MIUI V5 today and I cannot restore back to my SC2.9 Voodoo.
When it boots everything and it's brother force closes over and over again.
I noticed that this is a problem people get when trying to restore back to a NON Voodoo rom.
But as far as I can tell the MIUI v5 runs on a Voodoo kernel and I was trying to restore back to a Voodoo rom.
Any help is greatly appreciated.
Click to expand...
Click to collapse
What is the status of your phone at this moment? is it still in FC hell or did you go back to MIUI without FC?
MIUI does indeed have a voodoo kernel. Make sure the super clean rom you are flashing IS INDEED VOODOO. are you flashing a nandroid backup to restore to SC 2.9? Nandroid backups ignore voodoo from what i vaguely remember (I never use nandroid backup, maybe im wrong), so maybe that is your problem.
However if you are 100% sure your SC rom is voodoo and is not being flashed through nandroid, your problem is probably that you need to wipe data/cache/dalvik-cache before you flash superclean.
I was restoring a backup, which I am assuming was that problem. I just wiped and installed. *sigh* Thank you though