Hello, Here is my little story, i hope you can help me:
I was testing ROMs and having fun doing this, but i have an issue. At first i had this config:
Mobile : Samsung galaxy S2 - I9100
Base band : I9100XXMS2
Rom : Jelly bean 4.1.2 I9100XWLSW
Kernel : Siyah v6.0 beta5+
I did a nandroid backup using CWM 6.x and then stored the backup on external SD.
I then flashed cyanogenmod, latest nightly from 24/06/2013. Then i did wipe data/wipe cache.
Cyano was working, no issue. I decided to go backup to the stock rom (because i was only testing cyanogen, i dont want to stay with it). So i go back into CWM and do "restore" and then choose my jelly bean backup. Restore is sucessfull!
But after the boot, i'm now stucked in a bootloop at the moment of the samsung animation logo.
I tried another thing, did the wipe data/cache and THEN restore the jelly bean backup. I had the same result: BOOTLOOP.
Do you have any idea what's going on?
I have to mention that i did lots of backup/restore with CWM without issue.
Another thing to mention, i've reseted the flash counter with triangle away during the evening (i dont think there is a link, but i prefer mention it).
Also, i tried to restore the nandroid backup of cyanogenmod (i did one backup for this rom as well), and it's restoring well, so it's not bricked.
Thank you for your help!
Jellybean firmwares use a partition called preload.....I'd say with certainty that cwm didn’t backup this partition.....you have to enable the option before you make the nandroid.....
Without the preload backup, any firmware restore will bootloop.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Hi keith have deleted that post. Lol far to slow. Have you seen that thread for firmware in cwm format. Iv read it and its good but I cant find it now if you cone across it could you pm me a link. Many thanks and have a good day.:thumbup:
I vaguely remember reading something about that too......
I'll have to have another look. ..
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Dont put yourself out mate just if you come across it :thumbup:
I am also in this situation, I made a backup of stock ROM using Philz recovery. Then did a wipe to install new rom. Flashed new westcrip RR zip. Played with it (still on it now...) Then decided I want to go back. Wiped EVERYTHING (data,cache,delvik & fixed permissions.)
Retored backup successfully.
Boot loop.
So now I've had to reflash the RR zip so I can write this!
There is a way round this but it involves being at my computer and I'm out. ..
1.download the official stock firmware from sammobile again (unless u have it already) .
2.Put firmware and latest cwm/philz recovery zip on you phone.
3.Flash firmware with mobile odin (enable everroot).
4.Then goto stock recovery & flash cwm.
5.Then in that recovery find 'advanced restore', then you have the ability to only flash the DATA from your 'bootlooping' backup!
I will probably end up doing this but I'm not home so I'm still looking for a possible way to avoid this long method.
Holla back if anyone finds a quick way...
Sent from my GT-I9100 using XDA Premium HD app
keithross39 said:
Jellybean firmwares use a partition called preload.....I'd say with certainty that cwm didn’t backup this partition.....you have to enable the option before you make the nandroid.....
Without the preload backup, any firmware restore will bootloop.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
Hello keithross39 and ty for your help.
Are you sure there is an option related to this into CWM? I've never seen this. And i wonder why i have this problem now although i restored jelly bean with sucess in the past? It's weird.
match_stick said:
I am also in this situation, I made a backup of stock ROM using Philz recovery. Then did a wipe to install new rom. Flashed new westcrip RR zip. Played with it (still on it now...) Then decided I want to go back. Wiped EVERYTHING (data,cache,delvik & fixed permissions.)
Retored backup successfully.
Boot loop.
So now I've had to reflash the RR zip so I can write this!
There is a way round this but it involves being at my computer and I'm out. ..
1.download the official stock firmware from sammobile again (unless u have it already) .
2.Put firmware and latest cwm/philz recovery zip on you phone.
3.Flash firmware with mobile odin (enable everroot).
4.Then goto stock recovery & flash cwm.
5.Then in that recovery find 'advanced restore', then you have the ability to only flash the DATA from your 'bootlooping' backup!
I will probably end up doing this but I'm not home so I'm still looking for a possible way to avoid this long method.
Holla back if anyone finds a quick way...
Sent from my GT-I9100 using XDA Premium HD app
Click to expand...
Click to collapse
hello match_stick, ty for your help as well,
I still wonder how to troubleshoot this issue, it's common issue , i've google many things about this.
I dont understand why you have to do all those things, (which i dont want to do), to restore a simple backup, it's supposed to be reliable. I fear nothing's reliable in Android world...
Definitely the 'preload problem'.
I've found the setting by flashing Philz stock kernel (still bootloop). It's inside:
PhilZ Touch 5 CWM Base version: 6.0.3.2
Philz settings=>Custom backup & restore=>Misc Nandroid Settings=> and then tick "Include/preload"
I did the backup with Siyah CWM, and it didnt ask me about this at the backup moment, so i dont know if it's saving this partition automatically/transparently.
I will try now.
Try it out and let me know you break the boot loop!
Sent from my GT-I9100 using XDA Premium HD app
match_stick said:
Try it out and let me know you break the boot loop!
Sent from my GT-I9100 using XDA Premium HD app
Click to expand...
Click to collapse
Bad news, it didn't work. During the advanced restore i saw a message "the preload partition was not saved into this backup"....So i guess the nandroid i did didnt include it automatically! I wonder why. I will try to restore another Jelly bean backup i have on my HDD.
In the meantime i tried to restore an old ICS 4.0.4 nandroid backup and it's ok with this one.
The problematic nandroid backup was done with JB+Siyah 6 beta5+ and it's associated CWM recovery. Is there any special backup settings to tell it to backup the Preload partition? I've never enable/disable such a thing...
EDIT: in the meantime i've read this:http://forum.xda-developers.com/showthread.php?t=2099292&nocache=1
Conclusion, CWM from Siyah is broken for jelly bean. Philz CWM is ok for jelly bean.
As i understand Cyanogen overwrite my /preload partition that was not backed up by CWM from Siyah. This is really bad. Now i'm kinda ****ed.
I have to find a working CWM nandroid done with Philz CWM, then i can restore it properly with Philz CWM. Then i can backup the /preload partition using the cwm script from [email protected] Then i can restore it and remove the bootloop maybe?
God knows....
Sent from my GT-I9100 using XDA Premium HD app
---------- Post added at 04:06 PM ---------- Previous post was at 03:32 PM ----------
I used Philz and I'm still boot loop...
Sent from my GT-I9100 using XDA Premium HD app
In philz you have to set the option to save preload. Why because more phone models dont use preload. Philz isnt just working on i9100. Cwm from dori and siyah dont restore or bk up preload even if you save on philz and restore on cwm 6. Whatever I Was on dori. But you can save with hawkerpauls bkup preload and restore scripts. Reason why you other jb nandroids are restore is because there not using preload.
---------- Post added at 04:24 PM ---------- Previous post was at 04:18 PM ----------
So if no preload was made when nandroid was made on either with siyah dori or philz you will get boot loop. If you did bkup preload and have problems format data system cache and preload. Then wipe dalv cache in advanced restore nand wipe cache and dalv cache and reboot. Still problem wipe/factory reset but nit on or going to any were near ics 4.0.4 :thumbup:
Keith I found it that thread :thumbup:
andrewwright said:
In philz you have to set the option to save preload. Why because more phone models dont use preload. Philz isnt just working on i9100. Cwm from dori and siyah dont restore or bk up preload even if you save on philz and restore on cwm 6. Whatever I Was on dori. But you can save with hawkerpauls bkup preload and restore scripts. Reason why you other jb nandroids are restore is because there not using preload.
---------- Post added at 04:24 PM ---------- Previous post was at 04:18 PM ----------
So if no preload was made when nandroid was made on either with siyah dori or philz you will get boot loop. If you did bkup preload and have problems format data system cache and preload. Then wipe dalv cache in advanced restore nand wipe cache and dalv cache and reboot. Still problem wipe/factory reset but nit on or going to any were near ics 4.0.4 :thumbup:
Keith I found it that thread :thumbup:
Click to expand...
Click to collapse
Questions:
1)Where can i get the package for CWM 6.0.3.2 that is included into Philz, but i want it as standalone! I saw it exists only for galaxy s4, will the package from S4 work on S2?
2)I've tried tons of things to restore the CWM nandroid (the one from backed up with Siyah CWM WITHOUT /preload), with no luck. Finally i used the solution gave by match_stick member (ty dude):
I did the wipes, i flash stock ROM, and went into CWM and advanced restore, restore DATA partition.
What will happen if i just restore DATA without restoring /System? What is exactly into /system?
int0x13 said:
Questions:
1)Where can i get the package for CWM 6.0.3.2 that is included into Philz, but i want it as standalone! I saw it exists only for galaxy s4, will the package from S4 work on S2?
2)I've tried tons of things to restore the CWM nandroid (the one from backed up with Siyah CWM WITHOUT /preload), with no luck. Finally i used the solution gave by match_stick member (ty dude):
I did the wipes, i flash stock ROM, and went into CWM and advanced restore, restore DATA partition.
What will happen if i just restore DATA without restoring /System? What is exactly into /system?
Click to expand...
Click to collapse
I am not sure about the standalone version for that particular version but standalone recovery is available just keep searching harder.
If you just restore /data you're restoring only the apps you installed, /system contains all the core files which makes the OS function. /preload acts as an extension for /system partition, as /system for the S2 is too small to hold all the necessary system files, therefore absence of /preload in a nandroid can cause a bootloop.
Try using the apps "Nandroid Manager" and "Online Nandroid Backup" both by the same developer, these app's will make the life of noobs as well as flashaholics easier, and yeah the backup script of Online Nandroid Backup takes backup of all the usual default cwm partitions and also includes /preload and /efs also.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
I am not sure about the standalone version for that particular version but standalone recovery is available just keep searching harder.
If you just restore /data you're restoring only the apps you installed, /system contains all the core files which makes the OS function. /preload acts as an extension for /system partition, as /system for the S2 is too small to hold all the necessary system files, therefore absence of /preload in a nandroid can cause a bootloop.
Try using the apps "Nandroid Manager" and "Online Nandroid Backup" both by the same developer, these app's will make the life of noobs as well as flashaholics easier, and yeah the backup script of Online Nandroid Backup takes backup of all the usual default cwm partitions and also includes /preload and /efs also.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Ok. /system is read only partition. So if i install the stock ROM /system should be the same than the /system i had from my nandroid backup, is it right? So if i install the stock and rom and do advanced restore and select the /data partition, it should be the same than restoring the entire nandroid backup. Right or wrong? That's what i did and it's working. Install the stock rom didnt restore the /preload partition, but maybe it's creating one with default parameter. Anyway, not restoring /preload doesn't seem to be an issue with /data restore.
About CWM 6.0.3.2 standalone package,i found this:
http://forum.xda-developers.com/showthread.php?t=2201860
I ask about that CWM version, because i know only the latest version customized by Philz supports the /preload backup (as non default option). As Philz say it's the only recovery that is supporting full JB migration/restore.
Thanks .. Now will always remember to keep Include Preload checked before Nandroid
match_stick said:
I am also in this situation, I made a backup of stock ROM using Philz recovery. Then did a wipe to install new rom. Flashed new westcrip RR zip. Played with it (still on it now...) Then decided I want to go back. Wiped EVERYTHING (data,cache,delvik & fixed permissions.)
Retored backup successfully.
Boot loop.
So now I've had to reflash the RR zip so I can write this!
There is a way round this but it involves being at my computer and I'm out. ..
1.download the official stock firmware from sammobile again (unless u have it already) .
2.Put firmware and latest cwm/philz recovery zip on you phone.
3.Flash firmware with mobile odin (enable everroot).
4.Then goto stock recovery & flash cwm.
5.Then in that recovery find 'advanced restore', then you have the ability to only flash the DATA from your 'bootlooping' backup!
I will probably end up doing this but I'm not home so I'm still looking for a possible way to avoid this long method.
Holla back if anyone finds a quick way...
Sent from my GT-I9100 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks this Helped!!
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?
story: I was running the original android 4.0.3 everything was ok until I tried to instal busybox and somehow I lost the root so I said why I dont upgrade to the latest version and that what I did but the version I installed (4.0.4 nordic countries) have problems with Bluetooth , camera and video player so I want to downgrade to an older version
Q : is it okay to downgrade
if not I think I can wait for JB if samsung is going to release that any time soon
aminov said:
story: I was running the original android 4.0.3 everything was ok until I tried to instal busybox and somehow I lost the root so I said why I dont upgrade to the latest version and that what I did but the version I installed (4.0.4 nordic countries) have problems with Bluetooth , camera and video player so I want to downgrade to an older version
Q : is it okay to downgrade
if not I think I can wait for JB if samsung is going to release that any time soon
Click to expand...
Click to collapse
Yes, of course it's possible, otherwise people would be stuck if they update and don't like what they flashed.
Sent from the Matrix
thank you for your fast reply
Sent from my GT-I9100 using xda app-developers app
If your having all those issues your probably flashing an incompatible rom or kernel version.
Go to sammoble.com, grab your stock 4.0.4 rom, flash it in ODIN, flash Siyak kernel and then reboot into recovery and wipe data/factory reset.
TheATHEiST said:
If your having all those issues your probably flashing an incompatible rom or kernel version.
Go to sammoble.com, grab your stock 4.0.4 rom, flash it in ODIN, flash Siyak kernel and then reboot into recovery and wipe data/factory reset.
Click to expand...
Click to collapse
but i dont want to wipe so im going back to the older version
How do i know the compatible rom/kernel version my kernel i9100XWLPG
aminov said:
but i dont want to wipe so im going back to the older version
How do i know the compatible rom/kernel version my kernel i9100XWLPG
Click to expand...
Click to collapse
Why not? Surely you made backups of apps/appdata or even a nandroid backup before installing new rom?
If you made app/app data backup simply restore after wiping/flashing new rom.
If you made a nandroid backup simply use app extractor to extract/install apps/appdata to new rom.
You can also backup/restore SMS with SMS Backup from store and your contacts will auto sync when you enter googole account.
If you go back and forth between roms you will keep on running into issues. Plus flashing stock roms in ODIN wipes your apps/app data anyway so its not as if using the wipe data/factory reset in CWM is going to lose your apps as you will have already lost them.
TheATHEiST said:
Why not? Surely you made backups of apps/appdata or even a nandroid backup before installing new rom?
If you made app/app data backup simply restore after wiping/flashing new rom.
If you made a nandroid backup simply use app extractor to extract/install apps/appdata to new rom.
You can also backup/restore SMS with SMS Backup from store and your contacts will auto sync when you enter googole account.
If you go back and forth between roms you will keep on running into issues. Plus flashing stock roms in ODIN wipes your apps/app data anyway so its not as if using the wipe data/factory reset in CWM is going to lose your apps as you will have already lost them.
Click to expand...
Click to collapse
i did a nandroid but ODIN didnt wipe anything what app u recommend me to backup with titanium backup??
aminov said:
i did a nandroid but ODIN didnt wipe anything what app u recommend me to backup with titanium backup??
Click to expand...
Click to collapse
What he meant was that if you flash a rom with Odin, you don't have to do the wipes manually through CWM again.
TB is a good app (and the most used by people as far as I know) to back up your USER apps (don't back up system apps). After flashing you can restore them, even with your app data included.
Sent from the Matrix
Donnie Sins said:
What he meant was that if you flash a rom with Odin, you don't have to do the wipes manually through CWM again.
TB is a good app (and the most used by people as far as I know) to back up your USER apps (don't back up system apps). After flashing you can restore them, even with your app data included.
Sent from the Matrix
Click to expand...
Click to collapse
the problems i was having is because i didn't wipe thnx anyway
Hello guys. I am currently using Slimbean RC1 and I made a backup of my rooted stock 4.0.4 with Siyah kernel so that when I restore my backup anytime in future then will not have any super brick risks. But I have a confusion. Do I need to do a full wipe in CWM before restoring backup? Or it will wipe automatically?
Sent from my GT-I9100 using xda premium
I flashed Pacman ROM but before i did i made i made a nandroid backup of my current ROM jellybam 6.6.0 with CWM touch. The ROM did not work so i decided to restore with the backup. However it always gets stuck at data and then says cant restore /data. Please Help
Hassaan.W said:
I flashed Pacman ROM but before i did i made i made a nandroid backup of my current ROM jellybam 6.6.0 with CWM touch. The ROM did not work so i decided to restore with the backup. However it always gets stuck at data and then says cant restore /data. Please Help
Click to expand...
Click to collapse
Restore without data first .
jje
R: [Q] Can't restore /data
Maybe ure using an olther recovery version. i remember i had a restore always go wrong cause something was a bit off in md5 checksum or something was keeping it from restoring anyway, as soon as i updated thru rom manager (or you can get philz recovery) i discovered recovery was theN capable of ignoring error and complete restore.
Sent from my GT-I9300 using xda app-developers app
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
tetakpatak said:
Please quote my post and copy&paste whole text into some help thread for your phone, it is better idea as we are now getting off topic here. I'll try to help you there.
Format /system is done in recovery mode under "mount and storage" then after that you can restore your nandroid if it is done with the same recovery you use now. If you're on PhilZ 6, it usually can restore also CWM 6 backups.
Click to expand...
Click to collapse
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Click to expand...
Click to collapse
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
tetakpatak said:
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
Click to expand...
Click to collapse
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it? .
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it?
Click to expand...
Click to collapse
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
tetakpatak said:
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
Click to expand...
Click to collapse
Thanks for helping, but I ended up downloading the stock rom and flashing it. Everything was normal. Then I installed cm10.2 so everything's great now. Thanks!
Sent from my Nexus 4 using xda app-developers app
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
tetakpatak said:
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
Click to expand...
Click to collapse
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Sent from my Nexus 4 using xda app-developers app
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
keithross39 said:
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
6.0.4.5 is compatible? I think so ......
Sent from my Nexus 4 using xda app-developers app
I've always read....not.....
In any case, probably best not to risk it......
6.0.4.7 is DEFINITELY KK compatible.... and it'd take a couple of seconds to flash.........
Sent from my Infected KitKat bar.....
AndroidReborn said:
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Click to expand...
Click to collapse
Yes, mate, CWM 6.0.4.5 is capable of flashing KitKat.
It is usually always the same:
download your ROM zip and compatible Gapps
check in the phone (or PC) if the zips are corrupted through download (if they open after clicking them, they are fine)
move the zips to the folder you will flash it from (if you use PC to flash zips with ADB sideload, put them in the sdk/platform-tools folder)
make nandroid backup of your presently used ROM
wipe data/factory reset
wipe cache
wipe dalvik cache (advanced)
format /system (under mount and storage)
flash ROM.zip
flash Gapps
reboot
It is in general always good to read in the development thread of the ROM you attend to flash in the opening post which Gapps are recommended, or if there is some unusual order of flashing (sometimes, developers recommend reboot system after flashing ROM, and after that going to recovery and flash Gapps zip.
Some KitKat ROMs struggle with root access by using Superuser, so SuperSU should be flashed. If SuperSU app from Play Store gives errors by updating binary, you should uninstall SuperSU app then, find in the Chainfire's thread the compatible UPDATE-SuperSu.zip (version for your phone), flash its zip in the recovery, install SuperSU app, update binary (either "normal" or "through CWM/TWRP")