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
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?
hello, i have a question
i had a galaxy S and i remember that to pass from cyanogen to stock sammy, was obligate to flash ( before) the stock rom and then restore backups
In the s3 is the same? or the passage is like other roms?
Any help guys?
Define backup. Nandroid? You should not have to but it cannot hurt.
erto90 said:
Any help guys?
Click to expand...
Click to collapse
Usualy if you want to go from stock to CM9 you place CM9 rom and gapps on the internal sd card. Wipe cache and dalcik cache, data/factory reset, format system and then flash both zip files straight in a row without rebooting.
Go from CM9 to stock, reset the flash counter with Triangle Away and wipe and format as above. Go in downloadmode and flash stock rom with Odin.
If this is what you mean.
If you restore a nandroid backup you are still rooted and not have clean stock.
but if i restore a nandroid over a cm10 ( obv after a full wipe), will it works? oe i always need to reflash a stock rom?
It will work mate. No worries
Sent from my GT-I9300 using xda app-developers app
Hey guyz
I flashed siyah kernel
Then I tried dual boot wid sammy jb (1st ROM) and cm10.1 as second.
However I wasnt able to boot to second ROM and I had just black screen
Then I removed 2nd ROM
And tried to boot into primary
But got a bootloop.
Then i wiped cache dalvik cache and partition cache.. Still no luck
Then I restored nandroid.
No luck
Then I flashed stock ROM wid odin
Still no luck
What am I missing.. M new to Samsung..
doctor_droid said:
Hey guyz
I flashed siyah kernel
Then I tried dual boot wid sammy jb (1st ROM) and cm10.1 as second.
However I wasnt able to boot to second ROM and I had just black screen
Then I removed 2nd ROM
And tried to boot into primary
But got a bootloop.
Then i wiped cache dalvik cache and partition cache.. Still no luck
Then I restored nandroid.
No luck
Then I flashed stock ROM wid odin
Still no luck
What am I missing.. M new to Samsung..
Click to expand...
Click to collapse
What ur missing for now is a little commonsense to Read before doing anything silly
1)U should be aware (if not get it now), that u cannot Dual boot Stock Samsung JB4.1.2 or Roms based on it, unless they are modified.
2) Siyah doesn't support Rom's like CM10.1 which is based on Android 4.2.2 properly.
3) Dual boot not wrk'ng with JB 4.1.2 (stock samsung/and roms based on it) is due to the reason that they use 'Preload partition' which is required as 'Secondary rom-partition' for Dual boot .
4) which is the reason why u werent able to boot CM10.1 in the firsrt place and could'nt restore/boot back the stock JB (reason being the data in the preload/secondary rom partition being deleted)
5) now start afresh by installing/flashing a stock JB rom via ODIN.
He he he I read siyah doesn't support jb dual boot still was stupid enough to try :/ ...
And as I mentioned...flash stock still doesn't let it boot... I see Samsung and then boot loop
Sent from my GT-I9100 using Tapatalk 2
doctor_droid said:
He he he I read siyah doesn't support jb dual boot still was stupid enough to try :/ ...
And as I mentioned...flash stock still doesn't let it boot... I see Samsung and then boot loop
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
try flashing a custom kernel like 'Philz' from Odin, then enter its recovery and do full wipe including 'Preload',after that try flashing either a stock rom from odin or a Stock based custom rom like 'Neat rom' or 'Alliance Rom' from philz recovery and see
Sun90 said:
try flashing a custom kernel like 'Philz' from Odin, then enter its recovery and do full wipe including 'Preload',after that try flashing either a stock rom from odin or a Stock based custom rom like 'Neat rom' or 'Alliance Rom' from philz recovery and see
Click to expand...
Click to collapse
Sure will try and let u knw...currently m able to boot official cm and enjoying it... bt having poor battery
Sent from my GT-I9100 using Tapatalk 2
Sun90 said:
try flashing a custom kernel like 'Philz' from Odin, then enter its recovery and do full wipe including 'Preload',after that try flashing either a stock rom from odin or a Stock based custom rom like 'Neat rom' or 'Alliance Rom' from philz recovery and see
Click to expand...
Click to collapse
okay i flashed philz kernel ... formated /wiped data ,dalvik,system,cache preload, ... flashed neat rom.. success... then i tried flashing stock rom.. got a bootloop after seeing samsung logo...
i can restore nandroid of cm10.1
bt restoring nandroid of pure stock gives bootloop.
Sounds like your problem is to do with the /preload folder. To restore a stock nandroid, you also have to restore the preload folder associated with that backup. Search on xda for hawkerpaul's backup and restore scripts for preload, and read his OP on how to use them. That should get you sorted. As you wouldn't have already backed it up from the sound of things, you might not have any luck restoring that exact stock backup, and may have to reflash. If you need to extract data from the nandroid, titanium backup can extract data from a nandroid.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
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
guys im trying to fix my friends phone whici is samsung galaxy s2, heres what he did, he was on cynogen mod and then directly went to another rom without changing the bootloader and then he change it again to kitkat rom hoping it would fix things now what i did was first fix the bootloader cause im trying to restore its backup which is the original os 4.1.2 i was able to enter cwm which is 6.0.2.7 now i was able to restore the backup but still on bootloop. any tips?
rarela1234 said:
guys im trying to fix my friends phone whici is samsung galaxy s2, heres what he did, he was on cynogen mod and then directly went to another rom without changing the bootloader and then he change it again to kitkat rom hoping it would fix things now what i did was first fix the bootloader cause im trying to restore its backup which is the original os 4.1.2 i was able to enter cwm which is 6.0.2.7 now i was able to restore the backup but still on bootloop. any tips?
Click to expand...
Click to collapse
Wipe data
Sent from my GT-I9100 using xda premium
Flash stock sammy rom with odin.
If wiping data doesnt work, try flashing kernel. If that doesn't work, flash stock 4.1.2 via odin
Sent from my SGH-I317 using XDA Premium 4 mobile app
i just installed the stock firmware which is 4.1.2 and then tried wipe but theres a message in the system recovery says failed to mount /efs? any clue? thanks in advance.
flash latest philz kernel from here http://forum.xda-developers.com/showthread.php?t=1877270 ,boot to recovery,then restore your efs backup from there(you should have one in your external sd)
Sent from my blazing fast Note 2, running MIUI 5x and pleasantly surprised by it.
just installed philz kernel and went to recovery im searching for restoring the efs but cant find it though. still on bootloop.
i think this phone has other problem already tried 3 different stock firmware for this phone and then go to recovery wipe still on bootloop. tried installing kernel from philz its desame but only thing i noticed is every time i installed a new rom and go to recovery is says failed to mount efs. can it be one of the reason why its on boot loop? and also my friend didnt back up his efs thats why i think this is happening.
do you have a nandroid backup of any previous rom?
yup he has nandroid backup which has on the stock rom but i doubt cause when i installed the stocked rom then installed philz cwm which was 6.0.2.7 i was able to restore the back up but its still on bootloop so i dont know if the cwm is the ones not compatible or the rom.
after you restore your backup do a factory reset in cwm.
now i tried what you said and its showing md5 mismatch when i try to restore.
could be a corrupted backup.did you tried factory reset on your current rom?
argghh im on the blink on giving up on this phone already tried different methods.............
assuming you're now on stock 4.1.2,i suggest you to flash dorimanx 8.43 kernel,,if it doesnt boot,reboot to recovery,do a factory reset.If that doesnt help,try to restore nandroid from this cwm.Of course before restoring do a factory reset and format system and preload partitions.
ayt will try this now!!!
still no luck not working T_T..
you mean you can't restore your backup?And dont forget to wipe cache and dalvik cache when doing factory reset.As for efs,did you looked for it in internal sd too,in clockwork folder?It can be either in tar.gz,img.gz or zip formats.It's stuck at boot probably because of corrupted efs partition.If I remember well,you can restore efs partition from nandroid backup in philz touch cwm.
Have you done a stock samsung rom install usin odin? That should get you back to sqaure 1. If your backup is currupt it will never work.
Sent from my SGH-I317 using XDA Premium 4 mobile app