[Q] CWM restore not working - Samsung Galaxy S (4G Model)

So I've been flashing several roms back and forth, including GB through CWM. Then I reflashed to KD1 using Odin, and now I would like to restore my system to the way it was before all the flashes. I did make a restore, I can select it through CWM, it says it restores OK but upon rebooting, it's stuck on the boot screen (galaxy s 4g exclusively...).
What could be wrong?

Im having to same problem im wondering if it has something to do with the license. If you go to device settings mine is telling me no valid license
Sent from my SGH-T959V using XDA App

Try clearing your cache and factory reset after restoring, then reboot.

Well what I did is flash back to KD1, then did an advance restore of only the data, and that fixed it. Didn't try any of the other options in advance restore, as I have all my data back now.

check your mounts before restoring.

Related

[Q] Epic 4G Stuck on Boot

Hi, I'm a complete noob at this so help is appreciated. I rooted my Epic 4G and have been playing around with custom ROMs. I flashed the Quantum ROM manually using clockworkMod v2.5.1.0, and the phone wouldn't get any service and took FOREVER to scan media on the SD card so I tried to restore to a previous backup also made manually. It seemed to restore ok, but when trying to boot it would get stuck on the screen with "Samsung" in large white text and the website "www . samsungmobile . com" (without spaces) directly below it.
I tried wiping the cache, and then a factory reset with clockworkmod to no effect. Every time I try to restore to backup I get the following:
Checking MD5 sums...
Restoring system...
Restoring data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring cache...
sd-ext.img not found. Skipping restore of /sd-ext/..
Restore complete!
I then select reboot system now, which results in the same screen. I hear the usual boot music play, but the screen never changes. Please help a confused newbie!!!
Follow the process in this post to restore to stock...
http://forum.xda-developers.com/showthread.php?t=773032
This would seem to be the best path if clockwork isn't getting you anywhere.
from there I would re-root and then apply the recovery
Jedi Master Jesus said:
Hi, I'm a complete noob at this so help is appreciated. I rooted my Epic 4G and have been playing around with custom ROMs. I flashed the Quantum ROM manually using clockworkMod v2.5.1.0, and the phone wouldn't get any service and took FOREVER to scan media on the SD card so I tried to restore to a previous backup also made manually. It seemed to restore ok, but when trying to boot it would get stuck on the screen with "Samsung" in large white text and the website "www . samsungmobile . com" (without spaces) directly below it.
I tried wiping the cache, and then a factory reset with clockworkmod to no effect. Every time I try to restore to backup I get the following:
Checking MD5 sums...
Restoring system...
Restoring data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring cache...
sd-ext.img not found. Skipping restore of /sd-ext/..
Restore complete!
I then select reboot system now, which results in the same screen. I hear the usual boot music play, but the screen never changes. Please help a confused newbie!!!
Click to expand...
Click to collapse
When you're flashing the new 2.2 roms, you need to make sure you have also flash the appropriate modem as well using odin. With Quantum rom, you will need to flash the DK17 modem in order to get your phone to work properly. Instructions on how to odin DK17 modem can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=849753
Additionally, when trying to restore your phone, I would suggest doing a full wipe. I was having similar issues restoring a back-up, and it would hang-up on the samsung screen. Wiping seemed to fix this problem.
Thanks for the help! I used Odin to restore my phone to stock and it's been working since. I appreciate the help.

Can't do a factory reset

I updated to 2.2 last weekend and I have been playing with it for a while but now I want to do a full Factory reset. So I go to Settings/Privacy and select factory reset and select ok. Then the phone reboots. Goes into a recovery mode. And it says in alternating red and yellow text.
Formatting FOTA
Formatting FOTA failed.
Formatting data
Data wipe failed.
Formatting cache
Failed
Formatting DBDATA
Failed.
Any ideas why this is happening. I don't have a computer and I just want to go back to stock. So if someone could point me in the right direction I would greatly appreciate it.
Sent from my Mesmerize using XDA App
If you want to return to true stock (2.1), you will need to do an Odin flash using a computer. Performing a data wipe/factory reset will only remove any apps, syncs, and settings you have added, and will revert you to the default state of whatever rom you last flashed.
As for why your phone won't let you perform a factory reset, your guess is as good as mine. Perhaps you could try performing the wipe directly from recovery.
Also, if you have a nandroid backup of your former session, you should be able to revert to that by restoring the backup, but make sure to flash a compatible 2.1 kernel as well.
go to this page
HTML:
http://forum.xda-developers.com/showthread.php?t=881064
it has some instructions on how to get your phone back to stock 2.2 Froyo. That is the only solution I can think of.

MikRom Bootlooping on evo shift - HELP!!

This just started yesterday and i cant stop it. My phone reboots and says that memory is nearly full, then goes into a bootloop. I cant stop it long enough to back up texts, phone contacts and call log which is REALLY important; is there a way to back that up through recovery?
i'm really desperate here!
Edit: I can get the phone working through a format, but i need to be able to get contacts and sms backed up
Alternitavely, is there a way to run a clockword mod backup on an android emulator on my comp, so i can back up my important stuff?
what you should try doing is putting your sd card directly into your computer and delete stuff you don't need to get back so memory and then once you do that out it back into your phone
i cleared up the memory, internal and external. the stupid ROM is still broken
if its just the rom go to a different one and redownload mikrom later to make sure nothing happened in the initial download
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
From The Hacker Manifesto:
I made a discovery today. I found a computer. Wait a second, this is cool. It does what I want it to. If it makes a mistake, it's because I screwed it up. Not because it doesn't like me... Or feels threatened by me.. Or thinks I'm a smart ass.. Or doesn't like teaching and shouldn't be here...
Click to expand...
Click to collapse
I love it sooooo the rom isnt stupid, the team of developers supporting it are amazing and you should setup adb and get a logcat, also you should nandroid before you flash so in case it goes wrong you can flash back, like insurance but you actually get something from this without paying..
if you did nandroid boot into bootloader and select recovery (hold volume down and power on use volume button to highlight recovery and power button to select)
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
I managed to get some apps removed, its no longer giving me the memory-full error, but its still bootlooping a minute or so after loading. going to try the cache and davlik wipes, then a another install....
JKILO said:
From The Hacker Manifesto:
Click to expand...
Click to collapse
thanks I always do a nandroid backup before doing a format; doesnt help. I can load the clean rom just fine, but when i restore, it goes into bootloop again....
sparksco said:
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
Click to expand...
Click to collapse
ok, ill try this.
Also, how do i set up an sd-ext to automatically backup texts and call history etc to it?
crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
did not work - goes back to bootloop. how do i install ADB?
Jedman67 said:
did not work - goes back to bootloop. how do i install ADB?
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html
Beginner's Guide to Installing the SDK and Getting Started with ADB
If nothing else, like Jkilo said, provide a logcat and maybe someone could take a look.
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
VICODAN said:
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
Click to expand...
Click to collapse
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Jedman67 said:
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Click to expand...
Click to collapse
OK
0) Run a backup with titanium backup.
1) First of all go to clockwork -> mounts storage -> FORMAT /SYSTEM.
2) Wipe /cache, wipe dalvik, wipe/data, factory reset, repartition sd card.
3) Redownload the rom or try a proven ROM like UKE or CM7-255. If AOSP MAKE SURE TO FLASH GAPPS.
NO NEED TO RUU.
4) DO NOT RESTORE YOUR BACK UP. See how stable the phone runs.
5) If the phone is still unstable try a different battery.
6) Do not flash a custom kernel.
i formatted my backup SD card, and copied the essential data to it, and i have it running in the phone now. it seems to be running fine so far, i suspect the other SD may have gotten corrupt or physically damaged
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
Here's the 2.2 RUU zip http://forum.xda-developers.com/showthread.php?t=971550 Just put it on the root of sd, boot in hboot and let it do its thing.
Or you can run the RUU exe, just download and run from your pc. It's pretty self explanatory http://forum.xda-developers.com/showthread.php?t=1335068
Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
The problem is you didn't format /system.
Redownload the Rom. Then follow THIS GUIDE when you flash.
VICODAN said:
The problem is you didn't format /system.
Click to expand...
Click to collapse
Exactly 10 char
---------- Post added at 12:34 AM ---------- Previous post was at 12:31 AM ----------
prboy1969 said:
Redownload the Rom. Then follow THIS GUIDE when you flash.
Click to expand...
Click to collapse
Yeah that guide is great for flashing sense roms since "most" sense roms don't format/wipe the system partition correctly. Aosp roms you just do a data facotry wipe and everything installs just fine

Having a ton of backup/restore issues.

I am having some serious issues with my phone today. What exactly is the point of formatting system, data, and cache after you wipe? What is the advantage and what happens if you just wipe and not format? I have never had issues making backups and restoring them until I started having to format before flashing these new JB roms. I have noticed that any backup I make (even ones that I have successfully restored without issue numerous times) completely stop working after I format my phone. Phone has bricked three times today.
This morning I had to bust out ODIN again and flash the Root66 (stock root) to fix the phone. Annoying, but no big deal. After I'm done I made a backup of the stock root. No issues. Then I go into recovery and factory wipe, wipe cache, and wipe dalvik. Did that twice. Then formatted system, data, and cache twice too. Flash the TasteOfBeans rom...installs no problem. Working great. Spent about two hours setting my phone up the way I used to have it. Boot into recovery and make a backup of this rom since I have set it up. About an hour goes by and I need to use my GPS so I boot into recovery and attempt to restore the stock root backup I made just this afternoon and it fails. Why the hell is it failing? Then I go to reboot system so I can at least get back into the JB rom and it just get stuck on the samsung boot logo (my boot loader is unlocked).
I had these exact same order of events occur with JellyWiz last night. I'm pretty over the whole format system, data, cache after wiping because this is the only new thing I have been doing and its cause me to bust out ODIN about three times in two days and all my backups are failing.
VERY frustrating...
To make it even worse after my most recent run in of failed restores and stuck on boot, I just ran odin again flashing the same Root 66 that I have been using to solve my issues all day and now its stuck in the Verizon 4G LTE boot.
So, even after using ODIN the phone is stuck in the Verizon 4G LTE bootloop. I flashed the Stock Root 66.
After I gave up on that, I decided to completely unroot the phone and start from scratch so I flashed the stock unrooted zip in ODIN. Same result...cant get past the Verizon boot screen. What is happening? Is my phone completely screwed or is it fixable?
Alright, perhaps you should try odin flashing the phone back to complete stock. No Root66, just factory firmware.
yosterwp said:
Alright, perhaps you should try odin flashing the phone back to complete stock. No Root66, just factory firmware.
Click to expand...
Click to collapse
1+
Odin the stock Verizon ROM.
During first reboot after Odin, sometimes the phone will hang. Pull out the battery. Count to 10. Put the battery back and hopefully the phone should boot.
....just double check all the proper boxes are checked and unchecked in Odin. PDA only.....
Sent from a SYNERGIZED GalaxySIII

CWM reboots during restore!

Okay so I backed up my rom fine. When I went to restore it, CWM would get a little ways through restoring data and reboot the phone. What the hell?
Running stock rom and the latest version of CWM.
Sent from my SCH-I535 using Tapatalk
This is happening to me, as well, and it renders the restored phone inoperable as it seems to fail and reboot during the data restore. Wiping the data altogether and thereby starting fresh is the only way to get it to boot. Not Happy.
put your phone in download mode and try reflashing the cwm with the latest one: 6.0.4.3 via odin.

Categories

Resources