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.
Related
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.
I tried to install a custom boot animation and wound up having to use CWM recovery to get out of weird looping behavior. I'm not sure exactly what the restore function wipes (for instance, my Vegan ROM was still installed).
Since that episode I've been seeing more Forced Closures than before. I wonder if I need to repartition again. What values should I see if am or am not partitioned 2048/0 and where would I look for those? Thanks.
Surely someone can tell me what to look for as an indicator.
I promise to stop calling you "Shirley."
Rick,
I don't think it's personal -- there just is not a place you can look and see your
partitioning.
If you were boot looping, used CWM to stop it, repartitioned 2048/0 and are running
smoothly now I wouldn't worry about it.
Rev
EDIT: On further thought, I think if I were having glitches (like the FCs), I would
reflash back to stock, install CWM and clean up and reset as needed, and make
darn sure everything was working and exactly right -- and then go my way from
there. But that's just the way I work.
Thanks, Rev.
Thing is, I did not repartition (or, rather, re-repartition) after recovery. Have I necessarily reverted, due to CWM recovery, to the unreliable stock partition (bearing in mind that the device wasn't totally wiped; the Vegan ROM was still in place)?
EDIT: I understand that reflashing to stock and starting over will address any issue. I'm just trying to learn.
Rick,
If you boot into recovery using power/volume + and you get CWM you are still in
ClockWorkMod and have not reverted to stock recovery.
I understand you are trying to learn. I just don't like "flaky" anything so I "make sure"!
Rev
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.
Ok, first of I was wondering what odin and the jb bootloaders do?
Im running baked blackbean 6 jb4.12 with the new devil kernel...followed instructions to a t, odined to stock eho3 pit, gb bootloaders, worked for a bit perfectly n got stuck in a bootloop from hell, although I think my bit animation may have caused it. So back to Odin, stock, ect, but didn't do the gb bootloaders, n all works fine, seems a bit slower and the splash screen from the kernel no longer shows up, and room control will no longer boot into recovery
Can I odin the bootloaders after the rom is already installed or do I need to start from scratch? If I do start from scratch will a nandroid still work with the new bootloaders installed?
Onto titanium backup, I have all user only apps backed up and created an update.zip file with them..No system data at all...if I have the update zip can I delete all the backups n just use that? Save memory on the sd I'm assuming you just flash it as an update in recovery as opposed to a reg zip? Then all my apps should be back?...
I'm really out of date with the fassy last thing I had was skunkworks aokp m6...and I never flashed any bootloaders, just started from stock, and this update zip thing is new to me...just trying to get it all stable for my son...I've also noticed when I go to the homescreen it takes a while to show anything n I have it kept in memory, don't think bootloaders would affect that though correct?
One last thing...if I keep the stock kernel I get an md5 error when I try to do a backup...but once I switch it to devil it's fine...anyone else have this? That was with and without bootloaders...but all in all the gb bootloaders are the main thing I want to find out about being I've never used them before....
Thanks!
Sent from my blackened liquid galaxy
I've actually always flashed the GB bootloaders separately with Odin after the ROM/Kernel was installed (twice in total) and never had a problem.
I tried the update.zip with TiBu once and it didn't work... never tried it again. I'm just sticking to the regular method.
Bootloaders have no effect after you boot so no, that wouldn't cause your home screen issue.
Not sure about the md5 thing as I don't do nandroids.
Hope this helped
The update.zip that you create is just titanium backup, not your apps. When you flash it, it allows you to run tibu and install your apps without signing into google. You'll still need the folder with all your app backups.
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,