Hi all,
today I tried to install a new version 4.3 based (AvatarROM)... and all was fine, the new ROM was started correctly.
Then I would like to came back to my previous backupped ROM (4.1.2 OptimusROM), so with Recovery I restored previous version (after wipe ALL).
But when the restored was finished, the phone started to LOOPING in boot intro animation.
Now, I'm not able to restore any 4.1.2 based ROM (new installation also) because when I try to reboot then LOOPING starts.
I' tried also to take a Fix Permission and clean internal SD, but nothing changes.
Any help pleaseeee?
Factory reset and Format system before you flash nandroid bkup. 4.3 and 4.1.2 systems are clashing
I9100/I9300
andrewwright said:
Factory reset and Format system before you flash nandroid bkup. 4.3 and 4.1.2 systems are clashing
I9100/I9300
Click to expand...
Click to collapse
Solved, but after multiple Format and reset... don't know why!!
Thanks :good:
Glad you sorted it mate. Just remember that going bk to a nandroid bkup you have to format system to stop it clashing with the old "4.1.2" system.
I9100/I9300
Related
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?
I flashed a zip on recovery (Note 2 gallery) on stock JB and ended up in a bootloop. That's fine i reflashed the ROM but still ends up in a bootloop. Everything starts then goes to Android is upgrading (installing apps) then back to samsung logo..Now my question is: is there a quick fix for this or should i just wipe?i have some pics i didnt save will the wipe procedure erase the pics as well?
I'm runing a nandroid back up maybe i can extract the pictures from it?
thanks
skivnit said:
I flashed a zip on recovery (Note 2 gallery) on stock JB and ended up in a bootloop. That's fine i reflashed the ROM but still ends up in a bootloop. Everything starts then goes to Android is upgrading (installing apps) then back to samsung logo..Now my question is: is there a quick fix for this or should i just wipe?i have some pics i didnt save will the wipe procedure erase the pics as well?
I'm runing a nandroid back up maybe i can extract the pictures from it?
thanks
Click to expand...
Click to collapse
Have you tried wiping delvice cache? And formatting the system folder and reinstalling? From cmw
Sent from my Jelly GT-I9300 using XDA App
i did wipe de cache but did not format the system..does that wipe the internal sd card?
tried it didnt work...any help plz?
Recovery mounts and storage .
FORMAT cache system date preload .
Flash stock rom via Odin .
Or try Nandroid recovery after format if Nandroid is on EXT SD card .
jje
thanks JJ but i already wiped now i just want to restore data see if that works out or if it wiill be stuck on bootloop again
Hello guys!
Today i installed ClockworkMod Touch recovery and installed SuperNexus 2.0 Build 4 Rom , the whole process took less than 5 minutes. But before i installed SuperNexus i did a "Nandroid?" backup which went fine and took lots of space xD Anyway i proceeded with SuperNexus and it installed fine and played with the rom for a few hours ... i decided to restore the backup so my whatsapp and all that stuff comes back .. i didnt know that it'll restore system too! Ofcourse the phone went on a bootloop so i went to CWM and wiped data/factory reset and the phone booted with Stock 4.1.2 and the phone is kinda slow at the first boot ... now i dont really know what to do :/ The nandroid backup is large and im afraid the SuperNexus rom wont fit and it'll cause errors n all xD Im really stuck at this point , should i repeat installing SuperNexus?
EDIT: I cleared 4.6GB of space , what to do next?
the backup restore shouldn't have caused a bootloop, that's weird.
it restores everything - system and data. so if you want to keep the data when switching ROMs, use Titanium backup or something if the sort. try restoring again. if it fails, try a custom restore of /data
Glebun said:
the backup restore shouldn't have caused a bootloop, that's weird.
it restores everything - system and data. so if you want to keep the data when switching ROMs, use Titanium backup or something if the sort. try restoring again. if it fails, try a custom restore of /data
Click to expand...
Click to collapse
Im not sure if its a bootloop , it keeps restarting boot animation after 1min , i fixed it anyway by wipe data/factory reset option thru recovery and its on stock now booting fine , Shall i flash SuperNexus again normally ? Other than wipe data/factory reset is there anything else to do ?
I mean, if you don't care about your data being lost - then sure
Yeah no probs , contacts on sim and pic's and movies on sd card , Ill just have to redownload my games and all Ill charge my phone then proceed , thanks One more question. Since I installed SuperNexus before does it have system files that I need to delete? Or wipe data/factory reset will cover it?
Sent from my GT-I9300 using xda app-developers app
no, a data wipe will do.
Success Thanks for the help xD I learned a lesson Ill use titanium backup from now on
Hello everyone, I hope you can help me on this one since I'm already panicking.:
I have a Galaxy S3 international version, with Android 4.2.2, rooted, Philz recovery.
Wanted to flash a custom ROM, backed up EFS folder and data. Only thing missing was doing a NANDROID backup. Did the NANDROID backup to sdcard and rebooted....and now device won't start; it's stuck on the "SAMSUNG" logo. , WHAT THE HELL DID I WRONG?
I haven't formated anything or handled any system folders or anything. Just went , like in previous android phones, to recovery, made backup and rebooted. Any ideas? many thanks!
rhrs1987 said:
Hello everyone, I hope you can help me on this one since I'm already panicking.:
I have a Galaxy S3 international version, with Android 4.2.2, rooted, Philz recovery.
Wanted to flash a custom ROM, backed up EFS folder and data. Only thing missing was doing a NANDROID backup. Did the NANDROID backup to sdcard and rebooted....and now device won't start; it's stuck on the "SAMSUNG" logo. , WHAT THE HELL DID I WRONG?
I haven't formated anything or handled any system folders or anything. Just went , like in previous android phones, to recovery, made backup and rebooted. Any ideas? many thanks!
Click to expand...
Click to collapse
If its stuck in a bootloop factory reset and wipe cache in recovery.If that does not work install your backup and lastly if that doesn't work flash stock with odin.
Always remember the first thing to try whenever you are stuck in a bootloop is to factory reset wipe cache in recovery.
tallman43 said:
If its stuck in a bootloop factory reset and wipe cache in recovery.If that does not work install your backup and lastly if that doesn't work flash stock with odin.
Always remember the first thing to try whenever you are stuck in a bootloop is to factory reset wipe cache in recovery.
Click to expand...
Click to collapse
I did a full wipe and cache wipe and everything back to normal. What puzzles me is what was it that put the phone in a bootloop?
rhrs1987 said:
I did a full wipe and cache wipe and everything back to normal. What puzzles me is what was it that put the phone in a bootloop?
Click to expand...
Click to collapse
Good question but unfortunately I've not got a definite answer for you.Some times it is files leftover from a flash but no matter how experienced you are at flashing, bootloops are just one of those things you have to get used to.[emoji1]
tallman43 said:
Good question but unfortunately I've not got a definite answer for you.Some times it is files leftover from a flash but no matter how experienced you are at flashing, bootloops are just one of those things you have to get used to.[emoji1]
Click to expand...
Click to collapse
Indeed have to get used to it... many thanks for response tallman43
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