[Q] Problem restoring rom via clockworkmod recovery - Galaxy S I9000 Q&A, Help & Troubleshooting

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?

Related

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?

[Q] unable to restore from CWM

So I got following problem:
I was on Slim 3.2, did a cwm backup and wanted to upgrade to 3.3.
Probably it was a bad download or something, because I got stuck at the boot animation.
After I wanted to restore my backup I didnt even get into recovery, so I did a clean install with odin on 2.3.6.
Then I flashed cm9 to try restoring my data again, same problem.
I tried to restore my data several times, from cm9, from slim 3.2, but every time I get stuck on boot animation. Once I even let it sit for 40 minutes.
While restoring everything seems fine. Checking MD5 sums, erasing boot before restore, restoring boot image, system, data, datadata.
But then it says that .android_secure.img wasn't found, so it just skipped that and completed the restoration.
Reboot and stuck on boot anim.
Anyway to fix that? I'd be really gratefull if I got my app data back
flash darky xxjvu-re through odin heres a video showing a guide it not jvu its 10.2 re,same thing this will restore your phone ie get it working again
http://www.youtube.com/user/puggereduk
What to do when I got Darkys Rom on my phone?
Darky install the latest kernel, and then restore..
I think your problem is solved
Flashed Darky with Odin, flashed semaphore1.0 to get a more recent cwm and then restored my backup.
Now, every time I start my phone I get to cwm. If I choose reboot I get into cwm again.
What do now?

Galaxy Ace don't start after restoring

Hello,
My Galaxy Ace don't boot after restoring the backup I did, that is what I've done to screw it up:
I installed Cyanogenmod 7.2. Phone was working without problems.
Because I want to unlock it I tried to restore backup to get the original rom. I got an error: Can't restore system.
Tried to start the phone. Don't work, "SAMSUNG" appears on the screen but after a while screen became black, then "SAMSUNG" appears again, then black, ...
Tried to wipe all and install Cyanogenmod again.
No error but phone don't boot, just "SAMSUNG" on the screen, then black, then "SAMSUNG", ...
What can I do?
I've found several guides to unbrick aces but I would prefer don't touch anything if not sure.
did you tried to flash your phone via odin? if not do that
download your region firmware from sammobiles.com
unzip it to get a .tar.md5 file
put your ace in downloading mode.
start odin in your pc and connect your phone.
tick the one package option.
select the cooper.ops
select your downloaded firmware file (.tar.md5)
and click start.
wait for odin to display pass.
if your phone is still in bootloop after the flashing is done..
then reboot to recovery and give a wipe data/factory restore
i had this bootloop problem sometimes but a data wipe works fine
You can't restore a stock rom backup directly from a custom rom installation. The use different file systems (that's why system wasn't restored)
Flash a stock rom with Odin (to convert your file system to stock), root it, install cwm recovery and restore your backup. Works wonders.
Thank you guys, phone back to life.
I just use odin like @deAthbLisS told me and phone started again.
After that:
Unlock the phone.
Install cyanogenmod again.
(I had some trouble here because cm zip file was corrupt due to a memory card problem, I had to use a card from other phone)
Now it's all ok.
I really appreciate your help, thanks

[Q] Brick and can't restore

Hello everyone!
I just installed CM9 by the clockworkMod method (after doing a backup of my former official ROM) and it worked great exept I forgot to save my contacts...
So I did another backup of the CM9 and tried to restore the previous ROM, so I would be able to save my contacts and restore the CM9 again.
BUT the restore didn't go well and my phone crashed...
Now I can access both download mod and Clockwork recovery mod, I can see my 2 backups in clockwork recovery mod but when I try, I have the following message:
"data.img not found. Skipping ...
datadata.img not found. Skipping...
[ and it's going on for a few lines...]
Restore complete!"
but it's way too fast (couple seconds) and when I try to reboot I'm stuck on samsung logo.
I tried some solution to unbrick I9000 but nothing worked and I'm kind of desperate after some hours trying to fix it^^
I have clockwork recoverymod v 2.5.1.2 if that's any help.
What can I do to repair my phone?
CM9 use CWM 6.x if I'm not mistaken. If your backup was created with CWM 5.x or other version, please try flash the same CWM version first before you restore your backup.
If still fail, mount the storage via CWM and copy clockworkmod folder from your phone into your computer, you can check what file is missing/etc.
Hey
Or ur can downgrade and root (like 2.3.6 link given below)
then restore from recovery and save ur contacts...
Thanks for your answers. I finally get to re-flash CM9 and back up my contacts by another way.

[Q] CWM won't backup

Hi
My CWM won't backup anymore, what i do is: I just select back-up, from rom-manager or in CWM, and it does everything it is supposed to do while backuping. Then, when its finished and i reboot, there is a backup, but its only around 30 mb, And when i try to restore it, it says MD5 keys don't match.
Since I want to flash P.A.C. man i kinda really really want this to work.
Any suggestions or sollutions??
Did you try to re-flash recovery? If this does not work I would recommend NV Restore (an ICS stock maybe???)
in rom manager, flash older recovery (5.0.2.0) not the newest. .
boot to cwm, backup... it should work (i had the same issue a few times and older recovery fixed it)

Categories

Resources