Hi guys.
Been trying to figure this our for hours.
I flashed AOSPxXx-ICS-20121111 on my phone but not it runs brutally slow. It takes a like 30 seconds to launch apps.
I followed this steps.
booted to cwm
wiped user data
wiped cache
wiped dalvik cache
install rom
rebooted
let it sit for 10+ mins
What am I doing wrong?
Thanks
Wipe all of the above, plus the system partition.
I cant confirm that the new rom wipes the system partition for you, but if not, then you dirty flashed.
that will cause all kinds of trouble.
Also, did you add any mods like a new kernel ?
I ultimately suggest a new full wipe, and flash. and even a new download of the rom to ensure a clean build.
Sometimes they arrive all borked up....g
Rewipe reflash nd if persist reboot a couple times sometimes it can be slow after aa flash give a couple of reboots nd itll snap too
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
What else did you flash? Theme, modem,??
Just wipe and re flash. Don't restore apps, get them from the market.
All I did was flash a new rom, nothing else. I will try again =)
ok i finally got it to work. used odin and restored ics 4.0.4 =)
Related
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
Hello..
I had a new Note I717 and rooted it. The new ICS would work fine initially but then gradually a program or 2 or 3 or 4 ... would start crashing/not open/Phone freezing. So I tried a new ICS and after initially working fine, the same thing would happen. After this happening with 3 different ICS ROMS that were supposedly stable, I decided to go back to my original saved ROM on CWM and Gingerbread and have a working phone.. then that started the same thing happening to where I cant even open settings as that crashes upon opening.
I am thinking it must be some underlying code that has been corrupted. I am conscious to wipe both cache including the davlik cache and previous version before installing anything yet this keeps happening.
Any suggestions?
Reflash your rom but before you flash it. Wipe data, wipe cache, wipe dalvik cache and also format system. It's under mount and storage in recovery. When you have done that flash your rom.
When you're booted if you use any app like titanium backup, just restore the app ONLY NO DATA.
This has worked for me maybe it will for you
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
so ive had a bunch of issues with this, but now everything seems to be running smooth, except my wifi. i cant get it to turn on after wiping caches, re flashing both rom and kernal, everything. i dont know what to do next, plz help someone
ixi_devo_ixi said:
so ive had a bunch of issues with this, but now everything seems to be running smooth, except my wifi. i cant get it to turn on after wiping caches, re flashing both rom and kernal, everything. i dont know what to do next, plz help someone
Click to expand...
Click to collapse
I flashed the new Viper 2.0 and I am having the same problem. I came from Elegancia ROM, flashed the kernel for viper then did factory reset, cache and dalvik wipe for 2.0 independently before full wiping in the ROM. Everything else seemed to work but I remember at the set up screen there wasn't an option to install Wi-Fi.
I tried flashing the ROM again on top of the newly installed viper 2.0 but still the Wi-Fi just says it's turning on.
Going to start over again with full wipe to see if it works this time.
Edit: shouldn't have said everything else worked because didn't do full test. Just got install failed message and next screen said install successful where the reboot system, wipe buttons are. Does boot and go through motions but no radio it seems. MD5 checked out for both kernel and ROM. Starting over with new downloads.
effezie said:
I flashed the new Viper 2.0 and I am having the same problem. I came from Elegancia ROM, flashed the kernel for viper then did factory reset, cache and dalvik wipe for 2.0 independently before full wiping in the ROM. Everything else seemed to work but I remember at the set up screen there wasn't an option to install Wi-Fi.
I tried flashing the ROM again on top of the newly installed viper 2.0 but still the Wi-Fi just says it's turning on.
Going to start over again with full wipe to see if it works this time.
Edit: shouldn't have said everything else worked because didn't do full test. Just got install failed message and next screen said install successful where the reboot system, wipe buttons are. Does boot and go through motions but no radio it seems. MD5 checked out for both kernel and ROM. Starting over with new downloads.
Click to expand...
Click to collapse
Ok so here was my soultion after msgn turge, the kernal in the ZIP folder is ****ed up, u need to go to post 2 in the thread (nice bold red note cause of me haha) get that kernal. Now when I went to flash, I usually use fastboot flash bootimg boot.img
For what ever reason I got many errors until I did full wipe, caches and all, and before I let it try to boot I caught it into boot loader .
To flash it sucessful I had to use fastboot flash boot boot.img. very subtle difference from the other one... But made all the difference.
Full working here, clean smooth. WiFi on.
ixi_devo_ixi said:
Ok so here was my soultion after msgn turge, the kernal in the ZIP folder is ****ed up, u need to go to post 2 in the thread (nice bold red note cause of me haha) get that kernal. Now when I went to flash, I usually use fastboot flash bootimg boot.img
For what ever reason I got many errors until I did full wipe, caches and all, and before I let it try to boot I caught it into boot loader .
To flash it sucessful I had to use fastboot flash boot boot.img. very subtle difference from the other one... But made all the difference.
Full working here, clean smooth. WiFi on.
Click to expand...
Click to collapse
My problem was how I flashed the kernel. As soon as I started over I saw what was wrong with my preperation. Glad your up and running.
I am at a lose for what to do here.
I re installed peach sunrise on my Rooted Samsung Exhibit 2 to sell.
Did everything I had done before, but this time it is stuck in boot loop.
I've wiped cache, rom, dalvik, cache/dalvik, and data as someone told me to do.
Then re installed the rom.
Restart it up and bam boot look once again.
I've done this a million times..
HELP ME!
Perhaps I'm just doing it wrong? I haven't a clue. Anyone know how to fix this right now?
It can't be this hard..
Download the stock rom of your phone, wipe your whole phone, flash the stock rom via odin on pc while your device is connected to it.
Once installed wipe all your caches and restart the phone.
Now install the custom rom you wanted.
I hope this helps!
Sincerely,
Rareme.
Sent from my GT-I9300 using xda app-developers app
So, i have been happily using my sgs 3 for just less than a year and after having flashed quite a few roms, i decided that i should simply go back to stock android, which i did...
So i flashed my all time favorite (xxemg4, which is basically android 4.1.2) just like any other time...
But this time i decided that i should do a factory reset, which i did after i flashed the original rom, cwm recovery and boeffla kernel... So far so good. I wipe everything and proceed to boot the device. Everything is going according to plan. Then i decide that i want to take a selfie. But, my s3 doesnt want to... Camera failed, and camera app exits...
I told my self that its the first boot this is to be expected... So i rebooted... The result? Zip. Nada.
I wiped cache, the app's data, dalvik cache, nothing worked... what do i do now? Factory reset once again?
I even tried flashing a camera mod which i know that it works( i have tried it before, but this time nothing happened)
Help would be reaaaally appreciated
Mokiwipeout said:
So, i have been happily using my sgs 3 for just less than a year and after having flashed quite a few roms, i decided that i should simply go back to stock android, which i did...
So i flashed my all time favorite (xxemg4, which is basically android 4.1.2) just like any other time...
But this time i decided that i should do a factory reset, which i did after i flashed the original rom, cwm recovery and boeffla kernel... So far so good. I wipe everything and proceed to boot the device. Everything is going according to plan. Then i decide that i want to take a selfie. But, my s3 doesnt want to... Camera failed, and camera app exits...
I told my self that its the first boot this is to be expected... So i rebooted... The result? Zip. Nada.
I wiped cache, the app's data, dalvik cache, nothing worked... what do i do now? Factory reset once again?
I even tried flashing a camera mod which i know that it works( i have tried it before, but this time nothing happened)
Help would be reaaaally appreciated
Click to expand...
Click to collapse
Did you flash the correct boeffla for stock roms?
Go to recovery delete /system /data /preload /cache and delvik cache. Use odin and reflash stock, factory reset then try from there.
It was definitely the correct kernel... now regarding the factory reset, i will need some time to get my backups up once again
On a side note if I try to use the camera, it makes some kind of sound, as if it is working, which it has never done before