Related
I am sorry if this was answered before, but I have tried to search and couldnt find anything..
I have a Samsung Vibrant, of course, and had flashed Trigger 3.2. It was working great until applications started to fail such as the web browser. The applications will start but never actually run. So I tried to restore my nandroid backup, but after doing that, everytime I try to reboot my phone it stays stuck on the lock screen with "Searching" on the top right corner. Im assuming it is searching for the network, but it wont let me unlock the phone. I flashed Trigger again and it worked fine. I try restoring and Im stuck again. I also tried to factory reset and it still does the same thing.
has anyone else encountered this and know how to fix it?
Just odin back to stock with dl mode
Sent from my SGH-T959 using XDA Premium App
Factory reset from Recovery and re-flash Trigger again this time wiping cache, dalvik and fixing permissions after the flash. Now when restoring make sure to check APPS ONLY.
Abu-7abash said:
Factory reset from Recovery and re-flash Trigger again this time wiping cache, dalvik and fixing permissions after the flash. Now when restoring make sure to check APPS ONLY.
Click to expand...
Click to collapse
This is all correct. It is likely when restoring you are restoring old system data
thanks for the help! If I did this, would I still be able to flash back to stock or will I have to use Odin for that?
Abu-7abash said:
Factory reset from Recovery and re-flash Trigger again this time wiping cache, dalvik and fixing permissions after the flash. Now when restoring make sure to check APPS ONLY.
Click to expand...
Click to collapse
You have to remember when you Nandroid it doesnt flash the kernel back so you either need a flashable rom that has a stock kernel or odin back.
the above is correct make sure you do that!
Last night, I installed TW 4.5/TW Manager. I did a ClockworkMod backup first. I decided to restore it.
However, after restoration, the phone is in a factory state. Save for my lock pattern, which it remembered, the phone is in first-run setup mode, all my home screen layouts are gone, all my apps are not in the aop drawer except those the G2 ships with. Contents of the virtual SD card like photos are still there.
I tried restoring my only other CWM backup (a November backup that previously *restored ok* to undo a MIUI test, for example), but this, too, now boots in to the same state.
What has gone wrong here?
And is there any way of getting back the system that I assume/d is/was in the CWM backup files?
If I can't guarantee I can restore a CWM backup, it makes the world a very scary place to be.
Did you wipe before restoring? Sound to me you did not.
1. Full wipe
2. Restore again.
If that does not work, wipe again and use advanced restore.
Don't use rom manager but do everything manually from the recovery.
Wipe what?
You mean, choose Wipe Data and/or Wipe Cache?
Lennyz1988 said:
Did you wipe before restoring? Sound to me you did not.
1. Full wipe
2. Restore again.
If that does not work, wipe again and use advanced restore.
Don't use rom manager but do everything manually from the recovery.
Click to expand...
Click to collapse
Wiped data, Wiped cache, Restored backup - still doesn't retrieve the actual backup.
Now wiped again. In Advanced Restore, what should I do?
Lennyz1988 said:
Did you wipe before restoring? Sound to me you did not.
1. Full wipe
2. Restore again.
If that does not work, wipe again and use advanced restore.
Don't use rom manager but do everything manually from the recovery.
Click to expand...
Click to collapse
Restore the boot, system, data.
Lennyz1988 said:
Restore the boot, system, data.
Click to expand...
Click to collapse
This doesn't work either.
I had the same trouble early last month; even after a restore it was pretty much factory settings and I had to put everything back myself.
It was very irritating as I'd taken the precaution of making a backup but it still didn't work. I've pretty much recovered everything I needed to since then, though.
What excactly did you do prior to the restoring? Did you flash a new rom? If yes, what was your previous rom? Or is TW4.5 an app of some kind?
Lennyz1988 said:
What excactly did you do prior to the restoring? Did you flash a new rom? If yes, what was your previous rom? Or is TW4.5 an app of some kind?
Click to expand...
Click to collapse
I did this... http://forum.xda-developers.com/showthread.php?t=1365605
That is...
Installed TouchWiz 4.5, a modified TouchWiz launcher (left it alongside TouchWiz, set no default - home button press asked for confirmation of home screen each time)
TW4.5 comes with the TW4Manager app for controlling settings.
I downloaded the Suava theme for use with TW 4.5.
Before any of that, I made a CWM backup. Then I did the above. Now the backup (and even a backup which restored perfectly a month ago) will not restore to anything but factory new state.
And you are not getting an error message of any kind? How long does it take to restore? What is the size of the backup?
Lennyz1988 said:
And you are not getting an error message of any kind?
Click to expand...
Click to collapse
None.
Lennyz1988 said:
How long does it take to restore?
Click to expand...
Click to collapse
Seven minutes
Lennyz1988 said:
What is the size of the backup?
Click to expand...
Click to collapse
972Mb
The last thing I can think of is flashing an old stock rom and then rooting it with CF-Root. Then you have an older version of CWM.
A stock rom like KE2. Then try to restore.
If that does not work find a rom which has the latest CMW. Version 5 I believe. Then try restoring it.
Lennyz1988 said:
The last thing I can think of is flashing an old stock rom and then rooting it with CF-Root. Then you have an older version of CWM.
A stock rom like KE2. Then try to restore.
Click to expand...
Click to collapse
Hmm, are you talking about kernel?
If I'm correctly reading my rough notes from my rooting and tinkering, then my original kernel was KF3, I rooted in mid-October with an insecure equivalent (KF3) (CF-Root method), but quickly upgraded through Kies... I now have kernel XWKI4 (baseband XXKI1, build KI4).
So I moved from 2.3.3 to 2.3.4.
BUT - the backup and restore I did with CWM under the current system as recently as two weeks ago in November worked fine.
Lennyz1988 said:
If that does not work find a rom which has the latest CMW. Version 5 I believe. Then try restoring it.
Click to expand...
Click to collapse
So, you're saying there - you think a newer version of CWM might have eliminated a bug or something?
Might I find any FURTHER problems by changing the ROM and trying to restore?
Thanks for your help.
ClockworkMod - merry effing Christmas.
I really don't know. But I think it's worth the effort determining of your CWM is still functioning properly.
You can also try just flashing the KI4 CF-root kernel, then boot in recovery and then try to restore.
Make sure you have important stuff backuped of course
If you can boot to working phone backup data and copy clockwork mod folder to PC .
Then try posted below . boots to working phone root it with CWM and root copy clockwork folder back then try restore nandroid backup .#
Clean Slate for those that balls up the firmware .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
JJElgan, thanks,
So let me clarify what you're essentially suggesting...
Store my ClockworkMod safely on the PC
Wipe cache, data, system and SD card in Recovery Mode
"Install correct firmware"
Then put the backup file back and try restoring
What do you mean by "correct firmware"?...
I currently have Baseband XXKI1, Kernel XWKI4, Build XWKI4. That is the firmware with which I made the backup. (I guess that's KI4?)
But the firmware I originally rooted with CWM was PDA: KF3, PHONE: KE7, CSC: KD1 (XEU). (I guess that was KF3?)
What's the aim of this here and what's the source of the info?
Thanks very much.
JJEgan said:
If you can boot to working phone backup data and copy clockwork mod folder to PC .
Then try posted below . boots to working phone root it with CWM and root copy clockwork folder back then try restore nandroid backup .#
Clean Slate for those that balls up the firmware .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
Click to expand...
Click to collapse
You dont need to wipe before restoring. Just a quick note
Sent from my GT-I9100 using xda premium
CdTDroiD said:
You dont need to wipe before restoring. Just a quick note
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Ever?
How about after?
And how about in the advice the previous correspondent gave, to reinstall kernel/firmware?
Hey, don't know what happened but since few days my dialer is very slow. It takes approx. 15 seconds to start calling since I press call button in the contact. I cannot reinstall system, because it is time-consuming, I am waiting for ICS but in meantime I need to fix this issue
In other dialers it is alike - example exDialer.
I've got Gingerbread 2.3.6, stock.
Cheers.
menu / settings / applications / manage app / all / Dialer -> clear data
You say you're stock, but rooted? If rooted, try installing another dialer or modded one. Also, if you have CWM Recovery, clear cahe and dalvik.
Edit: You could also re-flash the stock ROM without wipe
Actually, reinstalling has newer been faster.
First, disable USB debugging and connect to pc/kies and make backup of msg, logs, notes...
Second, install titanium backup and back yours data+apps, it is one click process...
After that you are safe to factory reset your phone/install new rom..
Then you restore backup from kies (phone will reboot), install titanium backup and make one click restore for all applications+data...
Done!
Sent from my GT-I9100 using XDA App
I cleared but didn't help.
Yes I am rooted, installed next dialer and it is same - long waiting, I noticed during waiting lag CPU is working at 1200 Mhz - dunno why...
I have CWM Recovery but frankly I touched this only when I was rooting and installing 2.3.6 over 2.3.3. I do not know what dalvik is
Reflashing stock you mean system on system? It would be third system-on-system - I guess it would be too much
Burgscheinkerkdeiktraast said:
I cleared but didn't help.
Yes I am rooted, installed next dialer and it is same - long waiting, I noticed during waiting lag CPU is working at 1200 Mhz - dunno why...
I have CWM Recovery but frankly I touched this only when I was rooting and installing 2.3.6 over 2.3.3. I do not know what dalvik is
Reflashing stock you mean system on system? It would be third system-on-system - I guess it would be too much
Click to expand...
Click to collapse
Backup your data and factory reset.
Just re-flash your ROM. If stock use ROM download and instructions here:
[ROM+Guide]Official i9100 Firmwares KG, KH, KI, KJ, KK1/2/5, KL1/2/3, LA2 Download
If your running custom ROM, boot into CWM recovery and factory reset, wipe cache, go to advanced and wipe dalvik, and immediately flash custom rom.zip file from sdcard.
I upgraded 2.3.6 XXILA from 14.01.2012. Problem is gone
Thanks for help!
BTW, Google should check this issue out, it shouldn't have happened.
Edit ----deleted
Hi.
Met a problem with my GT-I9300. When I shut the phone off it just reboots. The phone was rooted and running a custom rom when this started. Now I have unrooted with mobile Odin and flashed a official firmware but the problem persists.
I have even tried a battery pull. When battery is inserted again the phone remains off til I push the powerbutton. But when I try to turn it off after this it just reboots again.
Anyone else had this? Tips on what to do?
I've never had any luck fixing this problem. I always had to wipe and flash. However, as a temporary fix, you can power off from recovery.
Sent from my GT-I9300 using Tapatalk
can I ask what you are doing when you turn it off?
Sent from the asylum
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
basse10000 said:
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
Click to expand...
Click to collapse
If the phone was totally cleaned formatted sd card and stock firmware installed then its a hardware problem .
But my guess is it as not totally clean .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
I have now tried to wipe and format sys/data/cach/sd in cwm. Flashed stock firmware via odin. Still same issue. Guess its hardware.
Thanks anyway.
This may sound strange, but is this the clock problem the Desire HD had.
In time settings, uncheck the auto update.
Change time & date to something random.
Power off and pull the battery before it reboots.
Give it a min, power up, reselect auto update and reboot.
Should be good to go. If its the same problem that is.
Sent from the App that Time Forgot.
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
r0uzic said:
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
Click to expand...
Click to collapse
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Solved
I solved it by flashing a later official firmware - XXALF6.
Darkrider82 said:
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Click to expand...
Click to collapse
basse10000 said:
I solved it by flashing a later official firmware - XXALF6.
Click to expand...
Click to collapse
Thanks, I'll try twice methods
Update: It's rare, but has returned to work normal and I doing nothing
Hello,
i found a solution for that problem. You will lose some sd card files.
go to settings-storage-others (or other) and mark all files. Then delete them an go to downloadmode to reflash you firmware. Reboot and the problem is missing.
hello,
After installing NeatROM 6.4, I am not able to restore the CWM backup of Jelly Bean 4.1.2.
A CWM restore of the Cyanogenmod 10.1.3, works fine though.
When restoring the JB backup, I get a boot loop on the logo.
Even after doing a wipe data/factory reset and wipe Dalvik cache, still the bootloop.
It was possible to flash the stock ROM (both ICS and JB), so phone is back to normal.
Just want to know if anybody came across this issue and what might be the cause if it and how can one resolve it.
Many thanks for your help.
regards,
neptune3nl said:
hello,
After installing NeatROM 6.4, I am not able to restore the CWM backup of Jelly Bean 4.1.2.
A CWM restore of the Cyanogenmod 10.1.3, works fine though.
When restoring the JB backup, I get a boot loop on the logo.
Even after doing a wipe data/factory reset and wipe Dalvik cache, still the bootloop.
It was possible to flash the stock ROM (both ICS and JB), so phone is back to normal.
Just want to know if anybody came across this issue and what might be the cause if it and how can one resolve it.
Many thanks for your help.
regards,
Click to expand...
Click to collapse
Backups don't always work. The best way to restore stock is to download the stock rom for your region from sammobile.com or one of the other sites with stock firmware and flash it via odin.
noppy22 said:
Backups don't always work. The best way to restore stock is to download the stock rom for your region from sammobile.com or one of the other sites with stock firmware and flash it via odin.
Click to expand...
Click to collapse
OK. That could make sense. But I restored the JB Backup several times, before I installed NeatROM.
Could it be that a directory was changed / deleted / overwritten during the installation of NeatROM, thus giving me the bootloop?
neptune3nl said:
OK. That could make sense. But I restored the JB Backup several times, before I installed NeatROM.
Could it be that a directory was changed / deleted / overwritten during the installation of NeatROM, thus giving me the bootloop?
Click to expand...
Click to collapse
I'm not sure what could have happened, but I always have a copy of the stock rom in .tar.md5 format so if I get into trouble I can always go into download mode and rescue my phone with odin......
I found this out the hard way on my S2 as well......
It turns out that CWM doesn't backup the Preload partition.....so when you try to restore the nandroid it simply won't work.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F