Database Develop

[Q] Problem restoring rom via clockworkmod recovery

Ok, in short I can't restore my rom after flashing Cyanogenmod 7 RC1. If I try to recover the phone remain locked in recovery mode.
That's the full story anyway:
Had a Galaxy S with Android 2.3.3 (Italy) rooted with CF-root
Made a backup with clockworkmod (no problem)
Made data/app backup with titanium backup (no problem)
Flashed Cyanogenmod 7 RC1 (no problem)
Restore Titaniun backup, have all my app back but had the first problem. None of my data has been restored, contacts, sms, calls... nothing. Why I ask?
Found that I can't access my sd card, read about the downgrade to froyo. Ok, time to restore to my original rom.
Made a restore of my nandroid backup, via rom manager.
BANG, phone hang up at boot on Galaxy S initial logo.
Ok, don't panic, restored an Eclair 2.1-u1 Rom via odin/download mode. Build XWJM7, Base XXJM3 (I read Flashing Eclair is safer)
Tried to update Android via Kies, but I get a message that my version cannot be upgraded.
Rooted Eclair via oneclickroot, installed rom manager/clockworkmod and tried again to restore my rom backup.
The restore seems to go Ok but the phone is stucked in recovery mode (2e). I get the Galaxy S logo for a few second, then logo disappear and reappear an phone go in recovery mode saying:
installing multi-csc
can't access to /system/csc/itv/system/
successfully applied multi-csc.
There is no way to go on, if I choose update.zip, phone go to clockworkmod recovery. Tried to restore an older backup, same result.
Now I'm again on Eclair.
So is there a way to have my original rom back via clockworkmod? Or I have to flash original CSC/MODEM/CODE via odin?
Thanks for helping.

I think your best choice is to flash from odin in download mode with a clean stock rom with re-partition to start again on a good base.

I made some other test.
Extracted the .img from cwm backup. The boot.img file is corrupted on both backup, file are identical so I though there's a problem backing up bootloader on my phone with cwm.
So I tried to recover all but boot. When I reboot (from eclair, cwm 2.5.1.2) in recovery mode I always get to android recovery 2e. As before if I select update.zip (and update is not present) system get me to cwm recovery. I select advanced restore and system ecc. but get the same problem the before: I get stucked in android recovery.
So again I flash via odin this time to gingerbread, rooted with cf-root, launch cwm manager tried for the last time to recover my damned backup.
And UA-TA! has my phone restored.
Any one has I idea why I was able to restore my rom (and app/data) only AFTER I restored my rom in another way?

I also made backup but it was giving error when i try to restor it

dadyal said:
I also made backup but it was giving error when i try to restor it
Click to expand...
Click to collapse
What error do you get?

Restoring from nandroid

I tried restoring from a nandroid backup I made and after the restore, I could only get as far as the i9000 boot screen. I went into recovery to try and flash a ROM, but CMW recovery could not mount my partitions (partitions got messed up by nandroid?) The only quick way I could think of was to use odin and refalsh and repartition.
I restored my nandroid from within CWM recovery. Is there something I am missing in the restore process? Obviously something went wrong.

asicman said:
I tried restoring from a nandroid backup I made and after the restore, I could only get as far as the i9000 boot screen. I went into recovery to try and flash a ROM, but CMW recovery could not mount my partitions (partitions got messed up by nandroid?) The only quick way I could think of was to use odin and refalsh and repartition.
I restored my nandroid from within CWM recovery. Is there something I am missing in the restore process? Obviously something went wrong.
Click to expand...
Click to collapse
Hey man, sounds like you tried to restore one system over another,
Forexample, stock over cm7? and that messes up the partitions as you see!
Try to install the rom you are trying to restore before you start restoring!
Should work then!
Hope this helps

I did indeed try to restore a ROM which was very different from the installed ROM. I will keep your suggestion in mind the next time I do a restore.

Just to confirm : yes, you need to flash the base ROM you're trying to restore.
I played with ICS over the weekend and got back by flashing a stock - well stock+ - JVZ and restoring nandroid.

Did the same thing, stupid as I am,
the big problem is that none of the computers I've tried with is detecting my phone right now.
I get in to CWM but and to download mode but that ain't helping me since i can't use Odin to flash back to stock rom.
Any ideas?

LG optimus 2x bootloop after failed cyanogen mod

Hello!
Today, i decided to install cyanogemmod on my 2x. So i downloaded ROM manager and downloaded cyanogenmod. everything went fine until i was going to boot for the first time. I got into a bootloop. so i tried taking out the battery and all that stuff but it still would't work. So i tried to recover the phone. I recovered it to a month old backup (I could not find the one i made in ROM manager before i installed cyanogenmod) The recovery went fine. But, when i rebooted it got into a loop on the lg logo! (the one without the loading bar) it would just load the lg logo, be there for like 10sec, then it would do the same. I tried recovering one more time, but it didn't work. The same thing happend. What should i do? :S Should i wipe data/factory reset?
EDIT: My phone was on android 2.3.4 before i download cyanogenmod.
BTW before i installed cyanogenmod, i forgot to clear cache and data. I was in a hurry so i did't notice the screen popping up, I automatically pressed "ok" without selecting anything.
Thanks for the help
- Kashif

Different partitions... Look for something called backtoext3 in the dev section (or somewhere else) The problem is that when you flash a custom rom like CM you convert your filesystem to EXT4, while stock is EXT3.
So basically what you have to do is:
1) Reboot into recovery
2) Wipe everything
3) Flash Backtoext3 zip
4) Restore Nandroid.
This should work. this will take you back to stock.

So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)

kashi169 said:
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
Click to expand...
Click to collapse
Yes
Flashing backtoext3 is just flashing the zip file you put on the sd card. (and then install zip from SD ) an then restore your nandroid stock backup and you're back on stock.
But you said you wanted to try CM right? In that case, wipe everything (factory reset/data + cache + dalvik) and then flash the CM7 rom and you have CM! Don't worry about backtoext3, your partitions are already on EXT4, because of your prior CM flash.

Ohh! Thanks Can you send the files for cm (2.3.4)? I've found some, but im not sure if my phone is compitable with them :S im really afraid to mess something up again

My. Signature. (CM7 temasek's KANG = the best CM7 at the moment )

I did everything and i got into a bootloop at the skating andriod screen again

OK, restored my phone back... Now it wont connect to the network and the battery has a question mark inside it. It also says the battery level is 999% heelp

Nvm, got my phone back to normal still dont understand why cm wont work...

You need cwm5 to flash cm.

I have a G2x, which is basically the same phone. But anyway, I would recommend nvflashing CWM and not getting it from ROM Manager.

CWM 5.0.2.0 will do just fine, but it is indeed old...
Anyway, are you sure you waited long enough on the CM boot screen? The first boot might take a couple of minutes. (4 or 5)

Stuck at Boot

So today my phone was on and everything was fine, then while I was charging it, went away from it a few minutes then came back it was on the boot menu. It now can not get past the boot menu ever.
I have ClockWork Mod recovery installed, and CM7.1 stable.
I did a "backup" via the ClockWork Mod Recovery of the system.
I am also quite tempted to get the CM9 RC2 installed. But screw it if it any kind of unstable. CM7.1 stable is unstable enough.
What should I do? I would prefer it if I did not lose all my stuff (like app notes etc).
Can I like just put my phone into Download Mode, place the CM9 RC2 on the root folder, then do the good old
cyanogenmodWiki Full Update Guide method via recovery
without losing anything?

tottycs said:
So today my phone was on and everything was fine, then while I was charging it, went away from it a few minutes then came back it was on the boot menu. It now can not get past the boot menu ever.
I have ClockWork Mod recovery installed, and CM7.1 stable.
I did a "backup" via the ClockWork Mod Recovery of the system.
I am also quite tempted to get the CM9 RC2 installed. But screw it if it any kind of unstable. CM7.1 stable is unstable enough.
What should I do? I would prefer it if I did not lose all my stuff (like app notes etc).
Can I like just put my phone into Download Mode, place the CM9 RC2 on the root folder, then do the good old
cyanogenmodWiki Full Update Guide method via recovery
without losing anything?
Click to expand...
Click to collapse
If you have done a "backup" from CWM before the failure just restore that.
From CWM menu try to do a dalvic and cache clean up. also clear init.d and nstool settings and try to reboot
If you want to be more adventurus and loose your contacts, sms, settings...and other stuff from CWM do full wipe and cache and dalvic and then install your favorite rom.

I tried to installthe Gnexus port rom jr03l 4.1.1 rc 10. I was on TAJB'S Jellybean rom with devil kernel. I tried to install the rom as per the instructions given. I did a nandroid backup of the current rom before attempting to do so. The flash failed as the phone rebooted into recovery after a few minutes. I tried to restore from my nandroid backup. That failed too and it came up with a message of "no free space". I rebooted the phone and the phone automatically tried to flash the gnexus port rom again. It failed rebooted and got stuck on the devil kernel screen.
After about 20 mins, i took the battery out and rebooted into recovery. I really dont know where to go from here. I need to backup my efs folder too somehow.
I have a flash zip of the gnexus port rom, the tajb rom and a cm9 nightly in my internal sd card. I also have a nandroid backup of my cm9 rom.
Any help will be greatlyy appreciated!!!
Please help me.

Hey
Just flash any firmware (Official is preferred)..root it and do a restore of the backup u have..
Done

Hey do a factory reset then try to restore your backup
Sent from my Awesome I9000 using Slim Bean

[Solved] Note stuck in bootloop after nandroid restore

SOS!
Was running the note on ParanoidAndroid v 0.5. Everything was fine. I had gotten PA v0.5 by flashing stock GB, used CF-Root with CWM to root the phone and get custom recovery. After this flashed PA 0.5 onto the Note. No kernels etc have been changed. Before flashing PA 0.5 i had taken a nandroid backup of the stock rooted GB with CWM recovery.
Fast forward to today..
I wanted to take something off my old nandroid backup so i rebooted into recovery took a backup of the current setup.. Backup successful.. After this i rebooted into recovery and restored the old nandroid backup.. This was also successful.. I booted into the phone, exported the data that i wanted and used the restore option available in the CWM recovery application that comes as part of the CF-Root package.. The phone rebooted into recovery.. Was at verfiying MD5 stage.. And then suddenly everything goes blank and the phone went into a boot loop.. It just stays at the screen where It says Galaxy Note GT-N7000.. Tried rebooting into download/recovery etc.. Nothing works.. Just coming back to the same splash screen..
I have not wiped the note on any unsafe kernel.. I'm sure about that.. Please help!:crying:

Try to boot into stock recovery and use pc-odin to flash a stock GB

Try to get in download mode....and please flash gb rom.
I would suggest pre-rooted gb rom.
And if you cant get in download mode or in recovery mode....then it is soft brick.....
Sent from my GT-N7000 using xda app-developers app

actually try wipingcache and dalvik first from safe kernel recovery.
after that if the nandroid you restore is ics and kernel is cm or aokp you need to flash an ics kernel inbetween.
Make sure to fkash when restoring pa you have same kernel you made nandroid with.

First things first, thanks to all of you for your replies.. I backtracked on my steps and i had done *some* mistake with the steps that i followed..
People who want to know the result: Problem solved! Yay!
Here's what i had done..
I went back to GB nandroid backup from a 5.5.x.x CWM based recovery (worked fine - as expected)
The GB nandroid backup had a 5.3.x.x CWM based recovery. So my mistake was trying to restore a backup, which was taken with a newer CWM based recovery, using the older 5.3.x.x recovery.. This is where it failed..
Luckily i somehow got into download mode, flashed stock GB and rooted it using the zergrush exploit, flashed CF-Root kernel with a CWM based recovery, booted into it, flashed PA v0.5.
Then after this, rebooted into recovery of PA v0.5 and restored the nandroid backup of PA v0.5..
Voila! It worked :victory: