I installed unofficial CM 11 on my SGS2 yesterday and wanted to switch back to Wanamlite JB 4.1.2 after experimenting with KK 4.4. But encountered bootloop after flashing JB 4.1.2.
Should I be doing something specific when reverting back to JB 4.1.2 from KK 4.4?
striker76 said:
I installed unofficial CM 11 on my SGS2 yesterday and wanted to switch back to Wanamlite JB 4.1.2 after experimenting with KK 4.4. But encountered bootloop after flashing JB 4.1.2.
Should I be doing something specific when reverting back to JB 4.1.2 from KK 4.4?
Click to expand...
Click to collapse
You need to wipe your cache and data, have you done that? It's easy to forget :/
Dakura said:
You need to wipe your cache and data, have you done that? It's easy to forget :/
Click to expand...
Click to collapse
I did. I wiped cache and data and got bootloop. Do I need to flash an older version of CWM recovery when I switched back to JB 4.1.2?
Did you do a nandroid backup before you installed kitKat on your phone? If you did then try restoring it to go back to your old rom.
heywheelie said:
Did you do a nandroid backup before you installed kitKat on your phone? If you did then try restoring it to go back to your old rom.
Click to expand...
Click to collapse
Unfortunately I didn't do a nandroid backup.
striker76 said:
I installed unofficial CM 11 on my SGS2 yesterday and wanted to switch back to Wanamlite JB 4.1.2 after experimenting with KK 4.4. But encountered bootloop after flashing JB 4.1.2.
Should I be doing something specific when reverting back to JB 4.1.2 from KK 4.4?
Click to expand...
Click to collapse
format /system (advanced menu)
perform factory reset
install rom
again perform factory reset
reboot.
It should boot then.
Nikhil said:
flash /system (advanced menu)
perform factory reset
install rom
again perform factory reset
reboot.
It should boot then.
Click to expand...
Click to collapse
Worked like a charm! The trick is to format /system! Thanks!
Related
I recently rooted my s3 i9300 and was planning to flash CM10 to it.
In the install instruction it states the following: "Make sure you run stock ICS rom. We won't care if you didn't and your Wi-Fi isn't working."
I am currently running 4.1.1 JB, so my question if I should go back to ics and how. Or can i just flash CM10 over my stock 4.1.1?
kwadwoo said:
I recently rooted my s3 i9300 and was planning to flash CM10 to it.
In the install instruction it states the following: "Make sure you run stock ICS rom. We won't care if you didn't and your Wi-Fi isn't working."
I am currently running 4.1.1 JB, so my question if I should go back to ics and how. Or can i just flash CM10 over my stock 4.1.1?
Click to expand...
Click to collapse
No, don't worry about that. You don't need to go back to ICS.. Just download the latest version of CM10 from here. And flash it via CWM.
But first
Take a backup of your current rom using cwm (Just in case you don't like CM 10 and wanna go back to how your phone was)
dibyajyoti said:
No, don't worry about that. You don't need to go back to ICS..
But first
Take a backup of your current rom using cwm (Just in case you don't like CM 10 and wanna go back to how your phone was)
Click to expand...
Click to collapse
Thank you very much!
Do you recommend I do a factory reset via cwm as well?
kwadwoo said:
Thank you very much!
Do you recommend I do a factory reset via cwm as well?
Click to expand...
Click to collapse
Yes, that is always advisable when installing roms.
PS: Download Google Apps for CM 10
Wipe data/factory reset
Wipe Cache Partition
Advanced > Wipe Dalvik Cache
Install CM10 Zip
Install Google Apps via CWM right after flashing CM10
In that order
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
My SamSung S2 up rom Stock 4.1.2 via odin or cook rom base 4.1.2 via CMW is bootlooped logo S2 I wipped all before and after uprom. And i up 2.3.6 or 4.0.3 or stock rom > 4.2 is not bootloop. i want up Wanna lite 4.1.2 rom, how to fix bootloop? Thanks you very much, sorry for my bad english.
P/S: When i change Mobile Networks to GSM only is Not Service, i can call when change Mobile Networks to 3G with poor network.i tried modems.
Flash Philz kernel first. Reboot in Recovery and flash Wanam Lite.
PS: what is 'up'?
Donnie Sins said:
Flash Philz kernel first. Reboot in Recovery and flash Wanam Lite.
PS: what is 'up'?
Click to expand...
Click to collapse
Yes, it is still boot loop, i flash form Wannalite 4.0.3 via Philz to Wannalite base 4.1.2, Stock rom 4.1.2 also bootloop.
You can try to do a full wipe, install Wanam (not Wanna) Lite.
Then reboot into Recovery, flash Philz kernel and reboot system.
Did you try to flash another custom rom by the way?
Donnie Sins said:
You can try to do a full wipe, install Wanam (not Wanna) Lite.
Then reboot into Recovery, flash Philz kernel and reboot system.
Did you try to flash another custom rom by the way?
Click to expand...
Click to collapse
Yes, i flashed stock 4.0.3, many Custom rom 4.2 or 4.3 it ok. but when i flash custom rom base 4.1.2 is bootloop even stock 4.1.2 still boot loop.
I Flash stock 4.0.3 -> Flashed Kernel Philz -> Do Wipe -> FLash Custom rom base 4.1.2 -> Do Wipe -> Bootloop
Tinhte1989 said:
I Flash stock 4.0.3 -> Flashed Kernel Philz -> Do Wipe -> FLash Custom rom base 4.1.2 -> Do Wipe -> Bootloop
Click to expand...
Click to collapse
After flashing a rom, you shouldn't do another wipe. In that case you erase the rom you've just flashed, and there is nothing to boot up.
Donnie Sins said:
After flashing a rom, you shouldn't do another wipe. In that case you erase the rom you've just flashed, and there is nothing to boot up.
Click to expand...
Click to collapse
It still bootloop. i did not wipe after flashed
blueforever89 said:
It still bootloop. i did not wipe after flashed
Click to expand...
Click to collapse
Last thing that comes up in my mind is: flash the rom. After it, reboot into Recovery, DON'T wipe and reflash the rom, reboot.
Not really sure if this is making any difference, but maybe it is
Edit: I just saw you're a different person.. What's up with that?
Donnie Sins said:
Last thing that comes up in my mind is: flash the rom. After it, reboot into Recovery, DON'T wipe and reflash the rom, reboot.
Not really sure if this is making any difference, but maybe it is
Edit: I just saw you're a different person.. What's up with that?
Click to expand...
Click to collapse
i tried, not solve !
1 account log from gmail, 1 account xda :fingers-crossed:
blueforever89 said:
i tried, not solve !
1 account log from gmail, 1 account xda :fingers-crossed:
Click to expand...
Click to collapse
Sorry, I've no idea... Good luck anyway:thumbup:
Donnie Sins said:
Sorry, I've no idea... Good luck anyway:thumbup:
Click to expand...
Click to collapse
i don't know why i can't Flash rom base 4.1.2 JB!
Thanks for your help!
Any idea? Please Help me,
Redownload everything again... then check md5 sum if its correct..if its a mismatch it will be a bootloop
Then flash latest philz in download mode
Go to cwm
Wipe data
Wipe dalvik
Wipe cache
Flash neat rom (juzt a suggestion to use a rom wid preload content)
Reboot...
doctor_droid said:
Redownload everything again... then check md5 sum if its correct..if its a mismatch it will be a bootloop
Then flash latest philz in download mode
Go to cwm
Wipe data
Wipe dalvik
Wipe cache
Flash neat rom (juzt a suggestion to use a rom wid preload content)
Reboot...
Click to expand...
Click to collapse
I flashed I9100XWLSW_NeatROM_Lite_v4.8.zip rom with Same MD5 Sum. But not getting out Bootloop Android Neatrom, i tried many stock 4.1.2, or cook like wamma lite, Neat base 4.1.2. all is getting bootloop. Other rom not Base 4.1.2 is ok. I can't understand.
Have Any Idead?
Help Needed !!
Recently I unrooted my alerady rooted I9100 and installed stock ROM,after few days again I rooted it and installed
custom ROM but now whenever I go to install stock base ROM like S4 for I9100 , NoteII mini etc...
it gets stuck on the samsung logo (earlier they were working ok), but this doesnt happen with other ROM's like CM,Carbon etc...
Can anyone suggest any solution or what I must have done wrong.
Thanks in Advance
abhiwildfire said:
Help Needed !!
Recently I unrooted my alerady rooted I9100 and installed stock ROM,after few days again I rooted it and installed
custom ROM but now whenever I go to install stock base ROM like S4 for I9100 , NoteII mini etc...
it gets stuck on the samsung logo (earlier they were working ok), but this doesnt happen with other ROM's like CM,Carbon etc...
Can anyone suggest any solution or what I must have done wrong.
Thanks in Advance
Click to expand...
Click to collapse
Always do Wipe data Factory restore and wipe cache before going to Stock rom to Cm10 or any custom rom.
Jeetu said:
Always do Wipe data Factory restore and wipe cache before going to Stock rom to Cm10 or any custom rom.
Click to expand...
Click to collapse
Yep I also did format/system along with the wipes but no luck is it due to recent changes to cwm's like when I was on stock I had rooted with Philz (touch) and then when I tried to install other stock base I was on other CWM (non touch)
basically I am very new in this flashing world...
abhiwildfire said:
Yep I also did format/system along with the wipes but no luck is it due to recent changes to cwm's like when I was on stock I had rooted with Philz (touch) and then when I tried to install other stock base I was on other CWM (non touch)
basically I am very new in this flashing world...
Click to expand...
Click to collapse
have the latest cwm installed and wipe data, cache and dalvik cache before flashing an entirely new rom
No certainly cwm has nothin to do with it
Check for corupt file
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