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.
Related
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 had zero problems when rooting and flashing my G1, but now with my Vibrant I am not sure what I did.
A few excellent stickies at the top but I seem to not be making any progress.
Here are the steps I took.
I had a stock Vibrant running 2.1
I downloaded ROM Manager, installed clockwork mod.
Did a backup of my current system ( was I supposed to do a clockwork AND nandroid?)
Downloaded and successfully installed a ROM called Blackhole 1.0
it runs ok but didn't give me the option to switch from 3G to EDGE data, and then I couldn't get internet access at all so i decided to restore my original stock vibrant system.
So I rebooted into recovery, selected restore (my phone won't go into recovery anymore for some reason) and waited, it took a while, then I rebooted (forgot to wipe), but it just got stuck on the Vibrant screen. So I booted into recovery mode again and wiped just user data not cache and rebooted, same thing stuck at Vibrant.
Now i keep hearing about something called ODIN, what I can tell it is some kind of flasher program for ROMS, nobody seems to give any kind of link or anything, is it greymarket or something?
So where am I now? I think the excellent noob guide needs to be updated a bit more.
My phone can get into download mode (whatever it is for i don't know) but it won't get into recovery mode anymore.
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=771111
i think what happened to you is you flashed a 2.2 ROM then tried to revert back to 2.1 without doing the proper downgrading steps i.e. you did not flash a 2.1 kernel first.
but since you can get to download mode.. just flash stock JFD or JI6 through ODIN and you should be good.
good luck
Once you get back to stock don't give up on the 2.2 toms. Try axura or nero. They might have a few minor bugs but its way better then stock 2.1.
Powered by Axura with a dash of Voodoo
I have done the samething as you, coming from a nexus one it seemed easier to flash roms without worrying about downgrading kernels or what not. Recently I was on Nero froyo and flashed to a different rom, and tried to revert back but ended up stuck at the vibrant screen. Think it has something to do with voodoo lag.
Anyways I had to use Odin with the no brick froyo off ebproductions. Ran that and uploaded clockwork, reinstalled voodoo lag fix and was able to nandroid back to my Nero set up. Somewhat of a pain but once you've done it, no need to worry about bricking
xtone said:
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=771111
i think what happened to you is you flashed a 2.2 ROM then tried to revert back to 2.1 without doing the proper downgrading steps i.e. you did not flash a 2.1 kernel first.
but since you can get to download mode.. just flash stock JFD or JI6 through ODIN and you should be good.
good luck
Click to expand...
Click to collapse
So the steps that are in this page?
http://forum.xda-developers.com/showthread.php?t=734475
GreggoryD502 said:
Once you get back to stock don't give up on the 2.2 toms. Try axura or nero. They might have a few minor bugs but its way better then stock 2.1.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
Well as long as I can use Odin if I f-up royally like above then I might give it a shot.
Need to read about downgrading kernals or whatever. Might just wait for Cyanogen 6.1
Just so you know, the backup utility in Rom Manager (clockwork) is really just shortcut to a nandroid backup.
The way I have things set up for backups, and this is just for my personal convenience, is as follows...
I have a stock JFD ODIN rom to flash in case anything goes wrong. (A lot of people here will tell you to flash this whenever flashing a new rom. It is safer, and cleaner to do it this way, but not absolutely necessary)
I make a nandroid of my last stable rom (I only keep one at a time cause the files are huge) and keep a backup of that on my PC.
I backup all my apps and a few other things (call logs, bookmarks, sms) through Titanium backup. If you get the pro version, you can load it up after flashing a new rom and have it automatically restore all your apps in one click (system settings can be dangerous to restore when going from rom to rom, so be careful with those.) I also keep a backup of this on my PC.
I will also occasionally backup both of the sd cards to the PC.
Maybe overkill, but you probably wont ever lose anything forever.
thegreatcity said:
Just so you know, the backup utility in Rom Manager (clockwork) is really just shortcut to a nandroid backup.
The way I have things set up for backups, and this is just for my personal convenience, is as follows...
I have a stock JFD ODIN rom to flash in case anything goes wrong. (A lot of people here will tell you to flash this whenever flashing a new rom. It is safer, and cleaner to do it this way, but not absolutely necessary)
I make a nandroid of my last stable rom (I only keep one at a time cause the files are huge) and keep a backup of that on my PC.
I backup all my apps and a few other things (call logs, bookmarks, sms) through Titanium backup. If you get the pro version, you can load it up after flashing a new rom and have it automatically restore all your apps in one click (system settings can be dangerous to restore when going from rom to rom, so be careful with those.) I also keep a backup of this on my PC.
I will also occasionally backup both of the sd cards to the PC.
Maybe overkill, but you probably wont ever lose anything forever.
Click to expand...
Click to collapse
OK I will just do the long way from now on. I use this phone on AT&T, I was worried that I flushed $500 down the toilet but ever since i modded my first phone way back in the day i've been addicted.
Running Odin and my phone is in download mode, about to flash this b**ch.
wish me luck.
I flashed Odin on my phone to revert to stock. Re-Rooted it but now I can't flash Clockworkmod. Please help D:
use the update.zip posted here. You want B.
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
dhartman977 said:
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
Click to expand...
Click to collapse
i have had the same thing happen every time i try and backup. I'm wondering if it has anything to do with the newer recovery b.c when i had 2.5 i had no issues with it. Anybody have an answer for this?
I was in the same boat as you: rooted and bloat frozen via TB since the first week, and just added the modified kernel with CWM 3 earlier this past week. Haven't had any problems with it. I used Heimdall to flash CWM and the kernel. Now I'm running Evil Fascination with the LG Alternate Launcher. Tried ComRom but didn't care for it, though the default wallpaper was very pretty.
Back to the point, after I flashed the kernel and CWM I restarted the phone, let it boot, then rebooted into recovery to backup, instead of unplugging it and immediately booting Recovery.
Honestly, you've made it this far, you want to get a new ROM, I say download one and follow the directions (read them three times top-to-bottom) before flashing, and you should be good.
Yeah - I think Evil is where I want to end up until CM7 is fully functional (just spent all morning reading the CM7 waiting room thread).
Unfortunately, I'm apprehensive about flashing a new ROM until I can get a good backup image. I'm not sure why I'm getting the erroneous date on the backups. I could certainly be doing something wrong; just not sure what (if anything).
Maybe I need to use a different CWM? 2.5.1 and 3.0.2.8. don't seem to have worked for me. Also, If I understand what eulipion2 said, I have already fully booted, then powered down and rebooted into CWM to do a backup. 3.0.2.8 fails and 2.5.1 gives be incorrect dates.
Going to do a few hours of reading on CWM, I guess!
I'm using the first kernel listed in this thread from times_infinity. I initially flashed ComRom, didn't like it, kept this recovery, and flashed EF. Works great so far.
Give the Nandroid a go with this Recovery and see if it works for you.
hey i figured out how to get the back up to work. you have to enable voodoo and then it will work
Hey guys. Thanks for the suggestions. Tried the CWM 3 link from above, still no dice. I suspect I may need to have a voodoo kernel installed to actually enable the voodoo and try the backup again. Makes sense I guess.
Getting frustrated.
Success! Flashed a voodoo kernel, and was able to get (what appears to be) a successful nandroid backup with 3.0.2.8 (red). Never did get 2.5.1 (yellow) working. Strange, but irrelevant. CM7 build 7 is looking like it's ready for a test drive.
Hey guys,
Wanted to get a sure answer.
Whats the safest way to restore back to the stock firmware fro CM10 (or any rom in general).
There are two answers that i seem to have come across.
Answer 1:
Just download the stock firmware. Extract tar. Load onto PDA, check auto reset the flash reset and then start. Boom done! Everything reverts to stock, modem, firmware, kernel, etc.
Answer 2:
YOU MUST first flash stock kernel. So flash that first via odin then open odin again and flash the rom. If you don't flash the stock kernel first and then just flash the stock firmware, you'll have some issues.
As you can see, both are a bit contradicting. Whats the right method?
You missed one.
Make a nandroid of your stock ROM. then once you're done checking out CM or whatever else, just restore that. A lot less headache.
Docavelli said:
You missed one.
Make a nandroid of your stock ROM. then once you're done checking out CM or whatever else, just restore that. A lot less headache.
Click to expand...
Click to collapse
Yep, nandroid is much much faster. In fact I went to lunch today and restored my CM10 nandroid to show a friend. 10 minutes later I was back to my Samsung ROM. Its much easier than flashing stock, then re-rooting, then loading all your apps and data back on.
I had heard that nandroid restores between stock/CM9/CM10 were causing bugs, or something of the sort.
If it really is working that easily, I might have to give these CM9/CM10 builds a try. I just didn't want to play around with it for a bit and then be forced to set up my stock configuration all again, because I do have a need for a certain level of stability.
Edit: Ah, I was thinking of our Verizon version however. I think it might require an Odin flash back to stock, then you can restore a stock nandroid backup.
While I can't guarantee you won't have problems, I can say that I haven't had any issues while restoring nandroids.
*your experience may differ.
XDA Mobile
What version of CWM or TWRP is working fine for nandroid backup and restore, specially for Tmo version?
Sent from my SGH-T999
Is this possible? The full details are I had my phone stolen, and got a new one with android 4.0.4 on it. I have on my computer a copy of my latest backup of my old cognition gingerbread rom. Can I just use CWM to recover to my old rom, or do i need to first downgrade to a gingerbread rom, and then recover?
Thankyou very much for assistance
Edit: Also, I don't actually want to use the old rom, I just need the contacts it saved, afterwards I'll wipe everything and install a clean ICS mod. In case there's any way of doing this without having to revert
You'll probably need to restore the backup with a version of CWM close to the one the backup was made with, you can often have problems restoring if you're using a CWM version a lot (say 12 mths or more) newer than the one you made the backup with.
So I'd probably go GB/with a rooted GB kernel first, restore the backup & go from there. I mean, it could work first try with an ICS kernel that's running a recent CWM build, but there's a fair chance it won't.
Edit - And be really careful with stock 4.0.4, don't do a wipe while you're running that.
Wow. I just... wow.
Ok, so I did the stupid thing and just tried to restore my old backup without doing proper downgrading first and it ended up soft bricking my machine, couldn't get recovery mode up, but I got into download mode. So I downloaded my country's stock gingerbread rom from samsung's site and flashed it with odin just to see what happens, and somehow my old rom was working again, and I have all my contacts and data. saved everything up to google, upgraded to ICS, import.
Everything went better than expected.
Thanks for the help
Told you Important thing is you managed to fix it yourself without asking silly questions in Q&A. Not many people seem to be able to do that these days.
Well done. I'm glad you got it sorted
Edit -You're welcome