Hi guys i have a small probleme with my nexus s
I installed NSCollab 4 days ago it was fine but yesterday i got lots of error when i launch application like titanium backup or facebook
So i tried too uninstall NSCollab so i flashed stock rom with odin facebook and titanium backup work well i tried too flash a custom firmware i tried NSCollab - CyanogenMod 7 but still the errors appear
I don't know what to d
Did you perform a cache/full wipe when switching between the different ROMs?
Yes i did still not working
What error messages are you getting and what version of NSCollab are you attempting to install??
i got FC error i m installing NSColla 1.0.20
Related
i flashed cm 7.0.2 with Google apps(GAPPS), Stock ROM,iceandfire v1.1 with (gapps) and something wierd is happening in SuperAOSP 6.4 bootanimation is changed to android after first time installing i even tried with stock recovery GRI40-2.3.3-rooted but market is not installing ?
I am wiping the rom properly i as it is i had this same F*****g problem in my nexus one also lol and now it is bricked dead trash and i bought nexus s so i wouldn't have this problem but again this same **** started. So how do i out of box it
should i odin it ??
I have the same issue but for Desire HD... have deleted my copy of gapps and redownloaded it, trying to install it now..
also tried the updated nightly #57 I think and still the same issue... my phone is useless without gapps..
lol i just flashed market u also try flashing
http://forum.xda-developers.com/showthread.php?t=1029001
installed new rom from rom manager and now i get a continual android.process.media. i had cyanogen mod 7.0.0 stable. installed the old rom to no avail. i have tried various roms and nothing. where is the error?
Firstly don't use rom manager, you are much better off booting in recovery and flashing manually. Rom manager has been known in some cases to cause issues
Secondly make sure you wipe system/data/cache when moving from one rom to another.
Thirdly if doing neither of the above helps, re download the rom. You may have got a bad download.
HEY NOOB, WATCH THIS
OHH, BOOBIES
Hey guys,
My phone keeps rebooting and says that I have blank SD card after I installed new roms. At first I thought the rom caused it but then when I installed a different rom even stock rom, the problem is still there. Is it because of a bad root?
Thanks
Hmm no that doesnt seems like a root problem.
1.- What ROM you installed when it all started?
2.- Did you installed a new Modem, Kernel or another kind of mod? Some ROMS are only compatible with 1 kernel e.g MIUI
3.-You tried this:
http://forum.xda-developers.com/showthread.php?t=1116251&highlight=stock
or
http://forum.xda-developers.com/showthread.php?t=1092021&highlight=stock
And still got problems?
keep on getting a message flashed up on my tab2 which reads:
unfortunatly the process android.process.acore has stopped.
any idea what i can do to stop this?
i had a bit of a nightmare last week and had to restore stock firmware but installed 5113 rom onto a 5110 tab,all was running good but i decided to install the right 5110 rom onto it.
all ran well thru odin and it all passed.after rebooting the update ran thru and it started up with the unfortunate messages.
any idea on what i can do to sort this?
ROM is just unstable, switching to another ROM should solve your problems.
Okay, so ...
I was using CM11 the last avaliable build and I had no problem with it.
Yesterday I've decided to preview the new ALPHA CM12 so I flashed it and played with it for some time.
Because of bugs I've flashed back CM11 based ROM but this time it was ParanoidAndroid BETA5.
The ROM is perfect but there is no way to start Viber anymore. After installing and opening the app it goes in to crash loop (Unfortunately, Viber has stopped). And that goes all the way until I force close it.
Then I wiped data and cache again and installed CM11. The problem was still there ?! Can't understand the "logic" ?!
Then I was tired and decided to try it with stock rom. Downloaded ODIN and flashed stock. Viber wokred perfectly. Why?
Why I can use it anymore on custom rom?! The problem started when I flashed CM12 and flashed back CM11.
Any help?
I had the same problem on CM11 but only on latest version of viber (5.1)
I downgraded to an earlier version (5.0.2) and everything works fine. I just need to make sure that viber doesn't update on its own
Viber have new update and now no problem with FC.