Good morning,
Just a question about what is contained in a Nandroid backup, specifically the kernel. Does a backup contain the kernel?
I ran Cleanrom for ages and recently upgraded to Hyperdrive r15 and have tried both the stock and Ktoonz kernel but have random reboots on both. I've tried reflashing a few times, always wiping everything, but I always end up with some funny problem.
At this time, I just want to get back to stock or my old Cleanrom back up, but wasn't sure if either of those kernels would work with Cleanrom or if my old Nandroid would contain what I had in the past.
Thanks in advance,
I think random reboots are a known issue with 4.3.
If you're not sure if your nandroid backup contains the kernel, it would probably be easiest to clean-flash Cleanrom and then restore your nandroid over it.
Yeah, I've been doing a lot of reading and it seems it's common, but not everyone has the problem.
If I looked into the nandroid, is there a way to see if it was backed up? Just curious.
I've reflashed Hyperdrive again just to see if I could get it to run smooth on my phone, it's nice to have the fast charge ability on the kernel.
Thanks,
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'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
Just wondering but does anyone else have issues with the new CWM 3.X.X whatever? I can't make backups of anything it errors out on backing up boot image. Then when I try to restore any of my old backups when CWM did work it says MD5 mismatch, those were made with 2.5.X or whatever the prior one was.
Anyone know of any fixes?
So no one else is having issues? Just me?
I have the same issue so I hope you get an answer soon....
also having the same issue.
cant make new backups on CWM3
backups made with 2.5.x wont restore
IIRC to flash restores from 2.5.x you have to have the 2.5.x cwm installed. I dont believe you can restore if you are on 3.0.x and want to flash a back up on 2.5.x.
Edit: Just made a back up since I hadn't had one of MIUIWIZ. All worked fine.
Maybe post what your running and maybe we can see if its a similar issue with other people running similar things.
I'm on comm rom 1.3. Haven't flashed anything else along with it. Just haven't been able to make a backup with CWM 3.x. Never had problems with CWM 2.5...
It didn't matter what I was running, any kernel, any rom, it just refused to backup. In fact nothing seemed to work at all. I've tried several different CWM versions etc.
Although it seems apparent I'm not the only one. I can understand the whole can't restore from 2.5.x but I can't make any backups at all on 3.x.x which makes it absolutely useless.
I finally just went back to pre 3.xx CWM so I could back up stuff. Never could get CWM 3.xx to back up.
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