I don't know exactly what caused the issue. Maybe some recent apps since that was all that I had installed. I was running the latest AOKP ICS 4-28-12 and Siyah 3.1x. I forget the exact kernal number but it wasn't the version that I read about phone bricking (R6?).
So I wake up this morning and unlock my screen and there are popups for everything force closing. Not just foreground running apps but everything including background running apps. Every time an app autorestarts in the background the force close error msg pops up again. It was running fine just 6 hours prior since I was using it before bed.
Reboot. Same issue. CMW Recovery. Wipe cache/dalvik. Reflash AOKP and GApps. Reboot. Same force closing issue. WTF. Attach USB to comp and try to move a different ROM to my Internal SD but no dice. Comp isnt recognizing phone now. [email protected]#K! Reboot into download mode. All the ROMS I downloaded are ZIP format instead of TAR format. So this time my dumb self uses Odin to reflash the TAR file I used to root my phone. After this I realize "that TAR doesn't have a ROM attached to it."
So now I can only boot into download mode. Can't load CMW. Sadly I had to leave for work and I'm without my phone until I get home at midnight. I FEEL SO DISCONNECTED! ='(
Will a simple file conversion program be sufficient to convert ZIP to TAR so I can use ODIN to flash them later? Or will I have to follow the unbrick instructions to return to stock and then start over? And after reading about that one version of Siyah bricking phones I think I'm going to leave the NEAK kernal that comes with AOKP.
Thanks for your assistance!
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
I found this on the i9100 forums, instructive. Instead of installing a stock samsung firmware and kernel, just download a rooted package (maybe go back to Gingerbread for i777) then go from there.
http://forum.xda-developers.com/showthread.php?t=1457458
I'm interested to know how this recovery works for you, keep us posted! Best luck!
Any idea what would randomly cause the issue of mass force closures so I can prevent this from occuring again?
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
dmnall said:
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
Click to expand...
Click to collapse
I didn't do a factory wipe. I'm thinking I'll just do a factory wipe for any new rom installs. It's a little more work but if it helps prevent this sort of error I'll do it. And after reading about the bricking with that one version of Siyah I'm going to wait a couple weeks before any new installs to make sure other people have tested it first.
creepyncrawly said:
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
Click to expand...
Click to collapse
Well the first attempt didnt work using kernel + rooted UCKH7. Odin did everything it was supposed to but the phone locks at the initial Galaxy S II I-9100 ! screen. =(
Second attempt using I777_UCKH7_OCD_Root_No_BL and I'm able to get past the Galaxy S II I-9100 screen and the original AT&T boot animation shows but after the boot animation it just continuously reboots. ='(
Third attempt I tried Kernel + cache + rooted UCKK6 and after the reboot it actually rebooted into recovery mode. I thought that was a good sign so I reboot the phone normally and same issue as above. I try to reboot into recovery mode (Vol + - and pwr) again but it doesn't come up now. ='(
Forth attempt I tried Kernel + cache + rooted UCKK6 again. It reboots into recovery mode and I select the Factory Wipe option and reboot. There's a long delay after the AT&T boot animation and finally my phone starts up as if it was stock.
What a freakin nightmare! I was so worried my phone was a goner. None of the other ROMs I tried gave the option of booting into recovery mode which would have saved me so much time. Only the stock one did. The factory wipe was the key. So I'm definitely saving that file for safe keeping.
Thank you all for your suggestions and assistance. It's much appreciated.
This entire thread could have been avoided. By wiping completely. What is a complete wipe? Well, its the /system , /cache, /data, and /dalvik partition. Each of which are easily wiped in cwm in under 30 seconds. Flashing the kernel cleaning script doesn't hurt. Keep in mind these are your phones people it wouldn't hurt to do some research.
Sent from my SGH-I777 using Tapatalk 2
Hi everyone, i show you my problem, yesterday i was installing the ics leak rom from T-mobile, at first time installation proceding fine, but multimedia apps didn't works, i tryed to re-flash by doing a second flash of update.zip by the recovery, but now the razr didn't start, he show only the logo M, after a black screen. I can go to the Flashboot, recovery the boot option.
I tried the Wipe cache, Wipe Data/Factory reset but nothing working.
I think that reflash via RSDlite or FlashlT with a ICS rom, the leak will solve this problem ?
Can everyone help me with this big problem ?
Thanks
There's an Thread in General section about saving a bricked Device after the Leak. I'm to lazy to post the Link now
I am selling my old galaxy s due to having a new phone and I have made it freeze when it boots.
It was flashed onto myICS when I was using it and before handing It over I wanted to wipe everything so it was clean for the new owner. I did this in the phone options and then also in recovery mode to make sure, but after rebooting it is just stuck at the galaxy s boot loader.
I tried flash another Rom onto it and the same thing happened even though odin said it was successful.
I'm not sure what to do now as I am scared of truly bricking the phone so I am asking what should I do to get it up and running again?
Thanks
hmm
it should work after reflashing and whiping data/cash in recovery mode
No luck with it.
I tried wipe data and reboot and had no luck. Then tried reflashing, wiping data and still no luck.
Do you think it might be something with the kernal thatI had installed with the myICS rom, not being compatable with the rom I was flashing to?
steph1389 said:
No luck with it.
I tried wipe data and reboot and had no luck. Then tried reflashing, wiping data and still no luck.
Do you think it might be something with the kernal thatI had installed with the myICS rom, not being compatable with the rom I was flashing to?
Click to expand...
Click to collapse
Didn't you format partitions before flashing? Have you tried doing a fully clean install?
did u try to flash a stock rom via odin
I'm on the US wifi 10.1
I was flashing the UK ICS stock odin image but got stuck on the glowing samsung logo.
I read to fix this, you have to wipe data/cache via stock recovery.
What I didn't know that this would erase everything.
I thought it was like wiping via CWM.
Does anyone know a way to recover any files?
I've been doing research for quite awhile now without luck.
Hi.
I followed the advice in the http://forum.xda-developers.com/showthread.php?p=34744118#post34744118 thread. I used the Noob proof method.
My phone was already rooted.
I have a i9300 and was under android 4.1.1 before using the method.
After having done the reset in Odin, I encounter a bootloop. I've tried reinstalling the ROM several times in vain.
As it wasn't specified in the tutorial, I didn't do any cache and dalvik cache wipe and delete. The phone doesn't boot into CWM mode for me to do it now (unless i've missed a step for this)...
Any advice?