i recently uninstalled touchwiz launcher and enabled upsm on echoe 29.1 s5 and i odin'ed to stock after not being able to exit upsm in hopes my problems woulld be resolved. when i booted up my phone for the first time i, had force close from android media and contacts storage and they wouldn't stop. any ideas?
Reinstall the rom with a clean wipe. Clear cache/dalvic cache and data, and reinstall rom
bamige1 said:
Reinstall the rom with a clean wipe. Clear cache/dalvic cache and data, and reinstall rom
Click to expand...
Click to collapse
thanks!!
went into stock recovery and wiped data and cache and it worked after
Awesome Mate, Glad to help you get your phone working again. Went through many boot loops myself installing roms.
Related
Installed the bloat free rom after wiping all my data, cache, dalvik etc... When I rebooted post ROM flash, all my stuff was still there...
Is ROM manager actually working?
Nope a lot of people are getting the same issues, me included.
Same issue here. I'm gonna have to go back to stock no root just to get rid of my data.
woot, it works now! flash cwr 2.3 if you haven't already and that will fix wiping data/cache.
ok i attempted to install BAMF Remix v1.6. is there a way to confirm that this was flashed properly? i still have bloatware like blockbuster etc. i think i missed something along the way.
is it possible i just did a factory reset?
thanks
markkal123 said:
ok i attempted to install BAMF Remix v1.6. is there a way to confirm that this was flashed properly? i still have bloatware like blockbuster etc. i think i missed something along the way.
is it possible i just did a factory reset?
thanks
Click to expand...
Click to collapse
How did you flash it? Did you do it through ROM Manager? Did you wipe data and cache? Something's not quite right, the bloatware should be gone.
i am having the same issue. are you also missing stuff like the notification power control widget?
io flashed mine from cwm and wiped everything.
phatjames167 said:
i am having the same issue. are you also missing stuff like the notification power control widget?
io flashed mine from cwm and wiped everything.
Click to expand...
Click to collapse
Hmm. Count me in on this one too then: http://forum.xda-developers.com/showthread.php?t=1069980
count me in as part of the galactically stupid. (worse than nube)
go to here http://forum.xda-developers.com/showthread.php?t=1027804
download and install
BAMF Remix v1.6:http://tinyurl.com/3wkpmh3
MD5: CF461768DBC8A729CB7D28B97D5B8717
download and install
BAMF Remix Patch 1.6.2: http://tinyurl.com/3ntawj6
MD5: d45d597d42d40ca31319786cfb9450dc
i was only installing BAMF Remix Patch 1.6.2 not realinzing it is only a patch to BAMF Remix v1.6!!!
i booted into ClockworkMod
everything now appears to be as expected for the ROM
thanks for your help.
it looks like this worked. when it first boots though the wallpaper is black with a red streak but then changes to the default wallpaper from stock. is that normal?
That got me closer to everything being 100%. I installed Remix 1.6 and 1.6.2 and I noticed changes like the battery indicator and the market being black (very nice, btw), but I still have bloat & the notification bar is missing. Wiped Dalvic Cache both times, wiped data fully when I installed the main BAMF 1.6 at the start of this.
aerojad said:
That got me closer to everything being 100%. I installed Remix 1.6 and 1.6.2 and I noticed changes like the battery indicator and the market being black (very nice, btw), but I still have bloat & the notification bar is missing. Wiped Dalvic Cache both times, wiped data fully when I installed the main BAMF 1.6 at the start of this.
Click to expand...
Click to collapse
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
devindpotts said:
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
Click to expand...
Click to collapse
I did the install through the ROM manager, so I'm hoping your solution works out. I'll give it a try this evening. Thanks for the suggestion!
aerojad said:
I did the install through the ROM manager, so I'm hoping your solution works out. I'll give it a try this evening. Thanks for the suggestion!
Click to expand...
Click to collapse
Actually I just looked and 1.6.3 is an entire rom instead of a patch so you can skip flashing 1.6. And just flash 1.6.3 after wiping data/cache/davlik cache.
devindpotts said:
Actually I just looked and 1.6.3 is an entire rom instead of a patch so you can skip flashing 1.6. And just flash 1.6.3 after wiping data/cache/davlik cache.
Click to expand...
Click to collapse
Thank you very much, your suggestions were exactly what I was looking for. Now have that full BAMF Remix experience
aerojad said:
Thank you very much, your suggestions were exactly what I was looking for. Now have that full BAMF Remix experience
Click to expand...
Click to collapse
Not a problem at all, enjoy.
devindpotts said:
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
Click to expand...
Click to collapse
I had the same issue and this worked for me. I just reflashed 1.6.3 directly from CWR (after wiping everything 3x) and everything worked correctly (notification widget, etc.)
thanks for the help
I am glad I found this, I had this same issue and it was driving me nuts. I'm reinstalling now and hopefully everything just comes out perfect.
I am adding this to my list of why I don't like RM.
Have flashed my S2 a few times, and happy with XXKI4, and also rooted using the CF-Root method.
However, seem to be getting a few Force Close errors here and there.
Market sometimes force closes when im not even using it, And if i go to Settings-Location+Security-Find my mobile, both Sim change alert, and remote controls throw up a com.android.settings Force Close.
I have wiped cache, dalvik cache, and fixed permissions using CMW recovery.
Any ideas chaps?
Thanks.
Would a Hard reset maybe solve this?
mk2vr6 said:
Have flashed my S2 a few times, and happy with XXKI4, and also rooted using the CF-Root method.
However, seem to be getting a few Force Close errors here and there.
Market sometimes force closes when im not even using it, And if i go to Settings-Location+Security-Find my mobile, both Sim change alert, and remote controls throw up a com.android.settings Force Close.
I have wiped cache, dalvik cache, and fixed permissions using CMW recovery.
Any ideas chaps?
Thanks.
Click to expand...
Click to collapse
Would be my first impression too.
Just do a complete system / nandroid backup in recovery mode (or by using the CWM Manager app).
Then Boot into recovery mode and do a factory reset.
Then reboot into recovery again, wipe cache partition and Dalvik cache too.
Then reboot the phone.
If that does not help, then you may have to flash the ROM (and afterwards CF-Root kernel) again.
Please remember to backup before and wiping cache(s) after flashing.
That will prevent most common FCs.
Good luck !
I had the same problem on my galaxy note, happened when i disabled the samsungservice.apk under system/app (was trying to remove Samsung bloat)
Put back the samsungservice.apk there and no more forced closes for the find my phone settings
Hello all,
Sorry that i have to post this out of the thread as i cannot post on the development thread for this rom.
I have a Samsung S2 which is rooted. With the release of Foxhound Revolver Ocelot, i tried upgrading from the previous release Foxhound sniper wolf. However i had this issues with the upgrade. I then also tried fresh install but too had problems, i tried for more than 10 times so this is roughly what i gotten
Steps for Upgrading
1. Went into recovery mode and Wipe cache and also wipe dalvik cache
2. Installed from External SD card, Aroma launcher ran and choose siyah kernel and Touchwiz S3 and choose custom install where I chose all applications.
3. Installed ok, phone rebooted and then ran the upgrade applications.
Upgrading symptoms.
a. Either it hang at the boot rom page. Force reboot and it run upgrade applications again
b. When it booted up again, i got an error android.phone not responding and i had to reboot since nothing will be displayed (black screen with notification). Tried fixing permissions in the recover mode didnt work.
c. a few times even when i chose Touchwiz launcher during installing, when it managed to boot up it gave me Apex launcher. When this happen it was very buggy (no input)
I then decided to try a fresh install
Steps Fresh install
1. Boot into recovery mode and factory reset , wipe cache and dalvik cache
2. Install rom and choose siyah, touchwiz s3 as default launcher then installed all software from custom installation and reboot to the wizard process
3. Once after wizard mode reboot and wipe cache and dalvik cache
Fresh install issues
a. It hangs at the end of wizard setup and cannot proceed once the setup is done. When the happens wipe cache and dalvik cache doesnt do anything to help. (meaning if the phone fails at setup wizard i have to repeat the install process. but before that i need to wipe the internal storage)
b. Once i wipe the internal storage, installation and going to the setup wizard is good. Touchwiz launcher also works perfectly. However i am faced with another issue. I am using Mybackuppro to back my data and apks. I did attempt to install superuser and make sure in extweats my phone was rooted before continuing..
What happen is that I can restore my sms/mms/contacts/ but if i reboot the sms icon will disappear and then be re-recreated again (funny symptom)
For mybackup pro app data + apks restore, i can restore only apps but not data. If i try that the phone will reboot. I wrote to the mybackuppro developer but they told me it had something to do with the ROM, not their software.
So at the moment i am not able to use the new rom due to the above problems and i am back on sniper wolf rom..i can only use the new rom if i dont want to port my apk data over, something which i am not willing to do n ow. Was wondering if anyone faced the same issues and managed to work through these problems and can offer some advice?
Thank you.
Hello,
i'm having the same issue. I did a fresh install following all the steps, but the rom freezes after i setup my google account. Then, it reboots and the launcher seems to don't work. I tried with touchwhizz as default, nova launcher and even apex launcher. I just can't get this rom working.
Thank you for this awesome rom anyway, sniper wolf is fantastic. But if anyone knows how to solve this please help me.
Sorry for my English.
ok i had download odin, and flashed everything went great, it reset and just hung on the boot logo for like 5 min, then installed TWRP and flashed Superuser and wiped cache and dalvik and then rebooted, same thing it will not get past the att boot logo, i do not have kies installed but i do have the usb drives. could that be and issues?
Bradl79 said:
ok i had download odin, and flashed everything went great, it reset and just hung on the boot logo for like 5 min, then installed TWRP and flashed Superuser and wiped cache and dalvik and then rebooted, same thing it will not get past the att boot logo, i do not have kies installed but i do have the usb drives. could that be and issues?
Click to expand...
Click to collapse
If you used Odin kies wouldn't be involved. I had similar problem. I did a complete wipe (both caches, system and data) then installed via Odin again. Now all is good.
Sent from my SAMSUNG-SGH-I717 using xda premium
thank you, that worked.
if anyone has this problem again save yourself some time. reboot into recovery and factory reset. Worked for me.
440bro said:
if anyone has this problem again save yourself some time. reboot into recovery and factory reset. Worked for me.
Click to expand...
Click to collapse
also rebooted into stock recovery and factory resetted. FInally booted, give it some time (likke 5-10 minutes) after the ATT logo freeze, Its probably building the bloatware cache.
Keep in mind installing this rom is a change of rom base and not just a little tweek -- all the wipes we usually do and backups of everything should be done to ensure a clean install.
It is a nice stock rom, and I was shocked at the amount of at&t bloat included.
chrisrotolo said:
also rebooted into stock recovery and factory resetted. FInally booted, give it some time (likke 5-10 minutes) after the ATT logo freeze, Its probably building the bloatware cache.
Click to expand...
Click to collapse
Lololol bloatware cache
It's building the dalvik cache, just like every Rom does when you wipe dalvik cache, or factory reset as dalvik is on the data partition.
AT&T are just freaking amateurs, they didn't make the boot animation loop at all... so once it's done and is building the cache. It appears to have just stopped there.