Hey guys, I continually get this error message upon manually forcing my phone into recovery. I'm on UCLF5 ICS OBJECTION from btw with the latest version of cwm. I would appreciate some help with regard to what exactly it means and how I can fix it.
Also my phone won't shut down properly. The lights on the bottom buttons stay on and I have to manually force it to reboot like I do to get it into recovery. The shortcuts in the rom aren't working for me.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
tmb993 said:
Hey guys, I continually get this error message upon manually forcing my phone into recovery. I'm on UCLF5 ICS OBJECTION from btw with the latest version of cwm. I would appreciate some help with regard to what exactly it means and how I can fix it.
Also my phone won't shut down properly. The lights on the bottom buttons stay on and I have to manually force it to reboot like I do to get it into recovery. The shortcuts in the rom aren't working for me.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I would put it into download mode and run odin or the Off ics to redo/repack your folders, then put CWM back on....idk
Just putting some ideas in, maybe the guru's will jump in on the thread...
Before nuking it like that... try going to mounts and storage and formatting cache
Although I'm not even sure that error is anything to worry about honestly...but i don't do nandroids personally so Idk for sure.
And Joe....stop quoting the op, please?
Does this error have anything to do with the CWM version being used? Its calling for the external sd card isn't it?
No it's calling on the /cache partition which is in the phone...
But it could be the cwm version, it's looking for a recovery log that it can't open.
I can't do anything with the cache. Its like it doesn't even recognize it. I noticed this when I went to throw another rom on and clear out my caches and it would just freeze. I left it for a half hour once just for the heck of it but it didn't do anything. I had to reboot the phone into recovery again.
Sent from my SAMSUNG-SGH-I717 using xda premium
And I have the latest version of cmw installed.
Sent from my SAMSUNG-SGH-I717 using xda premium
What will "fix permissions" do?
I would downgrade cwm, I've been using brawway's touch version since he released his latest, without issue and i think that was in April or may
And fixing permissions, makes the permissions of all apps and .jars be what they should be.
Example: apps in /system/app need rw-r-r permissions, sometimes pasting some of those in will not set them correctly, and if you're doing a bunch at a time is a real pain to go through individually and change them, so that option makes sure everything everywhere matches the permissions needed. So, not applicable in this case.
Well I managed to get another rom on anyway so I don't think its big deal now. I think I might just leave my phone alone now
The collectives 4.04 aocp rom is pretty freaking sweet lol.
Sent from my SAMSUNG-SGH-I717 using xda premium
studacris said:
And fixing permissions, makes the permissions of all apps and .jars be what they should be.
Click to expand...
Click to collapse
Thanks for the explanation.
What is the equivalent of the chkdisk dos command to make the android system rebuild the directory structure? Can you do that through a terminal emulator?
i dunno if there is one other than just reflashing
So basically just flash a new cwm over the one I have now?
Sent from my SAMSUNG-SGH-I717 using xda premium
Yes
this is the version I've been using for months
If u could get it to boot. And manually set permissions for android.policy.jar that would fix the shutdown issue.
silver03wrx said:
If u could get it to boot. And manually set permissions for android.policy.jar that would fix the shutdown issue.
Click to expand...
Click to collapse
Thanks, I decided to switched roms and the problem went away completely. So thats one down
studacris said:
Yes
this is the version I've been using for months
Click to expand...
Click to collapse
Awesome. Ok, last question. I'm assuming I can just load this onto my phone via Odin like I did my original version of cmw?
Sent from my SAMSUNG-SGH-I717 using xda premium
Yeah, That or there is also a .zip that can be flashed from your current version of cwm.
If doing it that way after it flashes go to advanced option and reboot recovery, then once in the new one, clear caches and see if that fixes the issue.
Or, just use Odin then boot into recovery and wipe, either way is up to you, but seeing as how it's cwm that's the issue, i might lean towards using Odin myself... Just note that will increase your flash counter iirc, if you care.
studacris said:
Yeah, That or there is also a .zip that can be flashed from your current version of cwm.
If doing it that way after it flashes go to advanced option and reboot recovery, then once in the new one, clear caches and see if that fixes the issue.
Or, just use Odin then boot into recovery and wipe, either way is up to you, but seeing as how it's cwm that's the issue, i might mean towards using Odin myself... Just note that will increase your flash counter iirc, if you care.
Click to expand...
Click to collapse
Ok great. Thanks guys!
Sent from my SAMSUNG-SGH-I717 using xda premium
Samsung SCHi717 OnlyOne Goldie SMS error
Has anyone else ran into the issue of the stock SMS notifications not going away? When I get a txt message, regardless of how many, it always says I have an unread message. This happened with OnlyOne HYFR and then With Goldie also. Is this a known issue, or is there a way I can just quickly correct this?
Also, I can't find anything that says how to diable the scrolling wallpapers. I wanted static wallpapers for each home/menu screen.
Any advice is appreciated.
-Bugz
bugzinc said:
Has anyone else ran into the issue of the stock SMS notifications not going away? When I get a txt message, regardless of how many, it always says I have an unread message. This happened with OnlyOne HYFR and then With Goldie also. Is this a known issue, or is there a way I can just quickly correct this?
Also, I can't find anything that says how to diable the scrolling wallpapers. I wanted static wallpapers for each home/menu screen.
Any advice is appreciated.
-Bugz
Click to expand...
Click to collapse
Wrong thread.
Sent from my SAMSUNG-SGH-I717 using xda premium
Related
When trying to switch to a different rom, even after factory reseting and clearing all the cache. Parts of the old ROM consist such as the notification tray colors on the pull down. I dont understand because ive cleared it all
You might have to wipe and start again. I had that problem yesterday.
Sent from my ADR6400L using XDA App
David522d said:
When trying to switch to a different rom, even after factory reseting and clearing all the cache. Parts of the old ROM consist such as the notification tray colors on the pull down. I dont understand because ive cleared it all
Click to expand...
Click to collapse
If all you are clearing is the cache, and not wiping data/cache/davlik, that is your problem right there...
Ive cleared them all 3 times now and still getting the same problem.
David522d said:
Ive cleared them all 3 times now and still getting the same problem.
Click to expand...
Click to collapse
You've gotta be doing something wrong then. Never had this problem before.
What could I be doing wrong. This is getting frustrating
Sent from my ADR6400L using XDA App
You may have to do a full factory reset
FishyChips said:
You may have to do a full factory reset
Click to expand...
Click to collapse
HOW?
Can someone please help
I just tried factory reseting from the phone menu itself no luck. I feel like this ROM is glued to my phone regardless how many times i try to kill it.
WHATS THE DEALLLLLLLLLLLLLLL
David522d said:
I just tried factory reseting from the phone menu itself no luck. I feel like this ROM is glued to my phone regardless how many times i try to kill it.
WHATS THE DEALLLLLLLLLLLLLLL
Click to expand...
Click to collapse
When all else fails, follow unroot steps to return to stock and restart the process. Something you're doing doesn't seem to be adding up.
nerozehl said:
When all else fails, follow unroot steps to return to stock and restart the process. Something you're doing doesn't seem to be adding up.
Click to expand...
Click to collapse
I feel losing root wont gain anything more then re rooting.
Its 1 thing the notification colors in the pull down.
What ROM are you trying to flash, and what recovery are you using? The most reliable is arguably the Clockworkmod version...
Sent from my HTC Desire using XDA App
techtechnique said:
What ROM are you trying to flash, and what recovery are you using? The most reliable is arguably the Clockworkmod version...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I'm running BAMF 1.5 remix, I want to flash BAMF Stripped. Ive been using recovery to flash my roms. I dont know how to use clockwork
David522d said:
I'm running BAMF 1.5 remix, I want to flash BAMF Stripped. Ive been using recovery to flash my roms. I dont know how to use clockwork
Click to expand...
Click to collapse
Returning to stock is a good way to resolve this issue.
So guess what, you can change the color inside the rom settings
Oh thanks for the help
Are you using ROM manager to flash roms or doing it manually? if your not you should try rom manager it has an option that lets you wipe all data before flashing the new rom. i use it and ive never had any problems
David522d said:
I'm running BAMF 1.5 remix, I want to flash BAMF Stripped. Ive been using recovery to flash my roms. I dont know how to use clockwork
Click to expand...
Click to collapse
If you search this forum or Google 'unrevoked', you'll easily find a complete guide and walkthrough on how to root your phone, which'll (as part of the process) load clockworkmod boot recovery.
The next time you reboot, hold the volume down key, which takes you into your boot screen, and use the vol up and down keys to select 'recovery', and press the power button.
From there, wiping your cache partitions and doing a full factory wipe is very straightforward.
That's the easiest way to fully flatten your phone before installing a new ROM.
Edit - the process might differ a bit for your model phone, but the principle will be the same...
Sent from my HTC Desire using XDA App
Ok so I tried to install the simply stock 2.3.5 yesterday and when it was going through I got some ladies voice who kept repeating the same line over and over. 'converting cache partition. Not enough space on partition' and kept boot looping that over and over. Could not do anything with it after that except DL mode and odin back to stock. Could some one please take a look at this rom and give me some instructions for it because the ones that were in the thread weren't all that specific. Also could someone give me the best root for this phone because the one I used may have been the cause.
Also there is a fixer file for this rom that apparently addresses some problems it has... How would I go about installing that zip?
Sent from my SGH-T959 using XDA App
Bumb
Has anyone ever even used this rom before? -.-
Sent from my SGH-T959 using XDA App
(sorry to the other thread owner as I didn't realize I was in the i9300 forum when I posted my reply asking for similar help)
*** this is a repost from the post I made on androidcentral, with a suggestion made by dmmarck over there ***
Ok, yes it seems I made a mistake and I'm new to this, so apologies. But I tried going in and changing build.prop (specifically ro.camera.sound.forced=0 to get the camera to go quiet when the phone was set to silent) and when I rewrote the file into the system, I ended up with a phone that won't go past the 'Samsung Galaxy SIII' screen into the Sprint boot. I searched around and found that my SBF might be trashed, but at this point I'm unsure as to how to get it reloaded properly.
I am able to get into the recovery (up volume, home button, power button), and may have made a further mistake by formatting the /system. Unfortunately, I didn't make a backup using that utility until AFTER the build.prop problem, so even though I tried to recover using the recovery I made (after the problem), it is understandably not working.
Am I totally screwed or is there a way to get me back? Any help is greatly appreciated.
// dmmarck and paul627g over on androidcentral think if I can get a good samaritan to help me by posting a nandroid backup of their stock L710 setup, I should be able to recover without issues, would anyone here be able to help me?
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1727171
bizdady said:
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1727171
Click to expand...
Click to collapse
Yes! Thank you for pointing me there, I found that a little bit ago and tried it a couple of times, unfortunately, the bootloader doesn't seem to be broken, so this didn't help me.
I really wish Samsung had the OEM ROM out!
Just found this!! Someone please tell me this will fix things?? And how do I use the file? (am downloading it now, slow download)
http://thedroidguy.com/2012/06/samsung-releases-source-code-for-sprint-cdma-galaxy-s-iii/
dhham said:
Just found this!! Someone please tell me this will fix things?? And how do I use the file? (am downloading it now, slow download)
http://thedroidguy.com/2012/06/samsung-releases-source-code-for-sprint-cdma-galaxy-s-iii/
Click to expand...
Click to collapse
You won't be able to do anything with it if you're not a dev, calm down Roms will be available soon
Sent from my SPH-D700 using XDA Premium App
masaidjet said:
You won't be able to do anything with it if you're not a dev, calm down Roms will be available soon
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
hey now, I appreciate what it takes to get to a fix, but I am in a bit of a pickle with this being my only phone and I am new to Android, so what may be a fix is still an exciting bit of news.
I appreciate that this is not the same as an OEM ROM now (with help from here and from android central), so I'm learning. I also understand that this is a problem that I caused by not doing my basic backups as I would any other software work, so please don't misunderstand and think that I am not understanding of what the timeline realistically will be to get to a fix.
Can't you edit the prop build on your recovery and flash it back?
bizdady said:
Can't you edit the prop build on your recovery and flash it back?
Click to expand...
Click to collapse
quite possibly, but the recovery was made from the messed up/non-working version, so I'm not sure if that works or not... any thoughts?
I have a solution for you. Ask someone who has a GS3 to make a nandroid, copy it to your sd card and flash it. Viola you should have everything back to normal.
*warning*
Some might deny your request because certain personal information being stored in a nandroid such as gmail accounts, contacts,passwords, ect.
Sent from my SPH-D700 using XDA Premium App
masaidjet said:
I have a solution for you. Ask someone who has a GS3 to make a nandroid, copy it to your sd card and flash it. Viola you should have everything back to normal.
*warning*
Some might deny your request because certain personal information being stored in a nandroid such as gmail accounts, contacts,passwords, ect.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Yes! Thanks! This is the route that we're moving forward on in the androidcentral forums. We're thinking a FACTORY RESET/CACHE/DALVIK WIPE usin CWM will help to remove personal info as best as possible for any kind soul who does this.
I'm pretty sure someone will help you. I would have if i had a gs3(waiting for local stores to get them). I hope everything go well for you.
Come to think of it, couldn't you just factory reset your phone and it will be stock again?
Sent from my SPH-D700 using XDA Premium App
masaidjet said:
I'm pretty sure someone will help you. I would have if i had a gs3(waiting for local stores to get them). I hope everything go well for you.
Come to think of it, couldn't you just factory reset your phone and it will be stock again?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
thanks! actually, I have no way to factory reset unfortunately...
By going into stock recovery mode you can factory reset it. It's the same steps to get into CWM.
And if all else fail, root your phone using the odin method by getting into download mode, you'll have CWM recovery and you can factory reset using that.
Sent from my SPH-D700 using XDA Premium App
masaidjet said:
By going into stock recovery mode you can factory reset it. It's the same steps to get into CWM.
And if all else fail, root your phone using the odin method by getting into download mode, you'll have CWM recovery and you can factory reset using that.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
hmm, I think I'm missing something because I don't have the factory recovery now that CWM is installed (or am I incorrect here?). And I'm not sure if I can get back to the factory reset options now in the state that I'm in.
As far as the odin method, I am already rooted, I'm not sure how I can use CWM recovery to factory reset at that point..
Apologies again as I am new to android and trying to learn! I appreciate you're help!
Yes, you don't have stock recovery because you're rooted. And if you're able to get into CWM you should be able to get your phone back to normal.
In CWM there's a option to wipe data(factory reset), but wiping data to cure your problem is experimental meaning idk what might happen when/if you do.
Sent from my SPH-D700 using XDA Premium App
masaidjet said:
Yes, you don't have stock recovery because you're rooted. And if you're able to get into CWM you should be able to get your phone back to normal.
In CWM there's a option to wipe data(factory reset), but wiping data to cure your problem is experimental meaning idk what might happen when/if you do.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Ok, just tried that (wipe data/factory reset), same behavior unfortunately...
How about unrooting ?
Using this method
http://www.epiccm.org/2012/06/team-epics-un-root-from-recovery.html?m=1
then going to stock recovery.
Before doing any of this first try using the nandroid somebody might provide for you.
Sent from my SPH-D700 using XDA Premium App
Well if he factory reset and erased the system he has no ROM to reset back to?
Hopefully a stock ROM is upped soon.
Sucks i don't have my phone yet else i would send you a nand backup of a clean install
bizdady said:
Well if he factory reset and erased the system he has no ROM to reset back to?
Hopefully a stock ROM is upped soon.
Sucks i don't have my phone yet else i would send you a nand backup of a clean install
Click to expand...
Click to collapse
I didn't know that, but wouldn't the system boot.img mskip provided for those who bricked help ?
Sent from my SPH-D700 using XDA Premium App
masaidjet said:
I didn't know that, but wouldn't the system boot.img mskip provided for those who bricked help ?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I would think so.
K I'm using boot manager to install a cm9 Rom and it keeps failing at creating boot.img. I don't know what I'm doing wrong since I've herd of others installing cm9 roms sucessfully using boot manager. Maybe it's something in my settings? Tried making a thread at init2winit forums but have not gotten any response over there. Anyone here willing to help me out? I would greatly appreciate it.
Sent from my ADR6425LVW using Tapatalk 2
that usually means you dont have enough space
Thanks for the advice. I did check my SD storage and it said that I only had 1.16GBs left. So I thought that this could be true I suppose. So I switched to int. Storage as the install location(which I have 9.67GBs available on) and its causing my phone to lock up and freeze. Happened right at the part "extracting Rom please wait..." Weird...
Sent from my ADR6425LVW using Tapatalk 2
boot manager doesnt surport rexound officially，maybe thats the final answer. i encounterred the same issue too，but when i reinstall the app，it works just fine.
Sent from my ADR6425LVW using xda premium
anubis2k3 said:
Thanks for the advice. I did check my SD storage and it said that I only had 1.16GBs left. So I thought that this could be true I suppose. So I switched to int. Storage as the install location(which I have 9.67GBs available on) and its causing my phone to lock up and freeze. Happened right at the part "extracting Rom please wait..." Weird...
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Remember to disable logging in Superuser. That also causes some major issues. Just open superuser hit settings icon, and where it says logging set it to off. You should have much better luck that way
Cool, I will try that. I've uninstalled and reinstalled multiple times, with no luck. I'm interested though. What do you guys have setup in settings?
Sent from my ADR6425LVW using Tapatalk 2
live2die said:
boot manager doesnt surport rexound officially，maybe thats the final answer. i encounterred the same issue too，but when i reinstall the app，it works just fine.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
The Rezound is supported by bootmanager.
I've never been able to get boot manager to work correctly since I've started using it back on my dinc2. Had issues installing some roms on that phone too. Which is why I think my problem may be the settings I am using. Is there specific settings I need to use for the rezound?
EDIT: After I changed the settings SU I tried again at work and it froze still and even rebooted during the install.
Sent from my ADR6425LVW using Tapatalk 2
Ok, so I finally got cm9 roms to install correctly and now when I try to boot to them it just shows the splash screen for a couple seconds and my display turns off and it never boots. I've tried with kang and paranoid with the same results. I've tried going into recovery and manually flashing the update zip for rom 1, didnt work. Can't think of what could be the problem....
Sent from a galaxy far..far..away....
anubis2k3 said:
Ok, so I finally got cm9 roms to install correctly and now when I try to boot to them it just shows the splash screen for a couple seconds and my display turns off and it never boots. I've tried with kang and paranoid with the same results. I've tried going into recovery and manually flashing the update zip for rom 1, didnt work. Can't think of what could be the problem....
Sent from a galaxy far..far..away....
Click to expand...
Click to collapse
Doesnt look like anyone has asked you this, but are you S-Off?? You need to be S-off for this to work. Also make sure when installing you wipe system/data/cache. You should be able to use the ext.4/2 either one will work. I use the ext.4 since it installs faster....alot faster.
dalvear88 said:
Doesnt look like anyone has asked you this, but are you S-Off?? You need to be S-off for this to work. Also make sure when installing you wipe system/data/cache. You should be able to use the ext.4/2 either one will work. I use the ext.4 since it installs faster....alot faster.
Click to expand...
Click to collapse
He can be HTC unlocked and s-on it will still work bootmanager still hasn't updated since the rezound got s-off... His problem sound like the boot.img does not have the right kernel installed or something
Sent from my Dinc... I mean Rezound
yojoe600 said:
He can be HTC unlocked and s-on it will still work bootmanager still hasn't updated since the rezound got s-off... His problem sound like the boot.img does not have the right kernel installed or something
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
only mentioning that because in the instructions for the app. If he doesnt have to be S-Off then thats strange. Only thing i could suggest after that would be redownload ROM and check MD5
dalvear88 said:
only mentioning that because in the instructions for the app. If he doesnt have to be S-Off then thats strange. Only thing i could suggest after that would be redownload ROM and check MD5
Click to expand...
Click to collapse
i understand... he could probably do a dirty install of the same rom over top and make sure it has a boot.img in the zip that is not in any of the folders
"Process system isnt responding. Do you want to close it?
wait report ok
I get this message ALOT on all the JB roms out there now; it happens after a reboot/restart, and if I click ok, things seem to work normally after a few seconds...
Anyone else seeing this alot? Anyone figure out a way to stop it?
thanks!
Wipe data, cache and dalvik.
Sent from my SAMSUNG-SGH-I717 using xda premium
johnrippa said:
Wipe data, cache and dalvik.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
wiping data will mean you have to reinstall your rom
I've wiped cache/dalvik numerous times, and it still happens
and, when I flash new rom, i factory reset, wipe data/cache/dalvik, and run darkstar system wipe, and it still happens
First try fixing permissions from within your recovery.
_____________________
Black Star VIII
ZPaul2Fresh8 said:
First try fixing permissions from within your recovery.
_____________________
Black Star VIII
Click to expand...
Click to collapse
did that many many times, and it doesnt help
wase4711 said:
did that many many times, and it doesnt help
Click to expand...
Click to collapse
Did you restore apps from titanium backup? If so that may be it.
_____________________
Black Star VIII
Me too
Hello,
this problem happens to me too for a few day now.
System not responding at every boot, but everything seems normal.
when i flash a new nightlie and it reboots, i do not get this message. But after i reboot again it reapears.
after a search i found this, there: http://www.modaco.com/topic/359832-devrom152-cyanogenmod-101-android-422/
its for zte blade
[DEV][ROM][15.2.] CyanogenMod 10.1 (Android 4.2.2)
"11.2.2013 changelog:
reverted commits (1,2) that caused 'Process system isn't responding' issue on every reboot"
(the comits have something to do with the new FM stuff in the rom)
Maybe someone want to have a look at it?
I can not post in the official CM10.1-galaxysmtd thread yet.
Greeting, Strainhunter
Problem gone (i hope)
strainhunter said:
Hello,
this problem happens to me too for a few day now.
System not responding at every boot, but everything seems normal.
when i flash a new nightlie and it reboots, i do not get this message. But after i reboot again it reapears.
after a search i found this, there: http://www.modaco.com/topic/359832-devrom152-cyanogenmod-101-android-422/
its for zte blade
[DEV][ROM][15.2.] CyanogenMod 10.1 (Android 4.2.2)
"11.2.2013 changelog:
reverted commits (1,2) that caused 'Process system isn't responding' issue on every reboot"
(the comits have something to do with the new FM stuff in the rom)
Maybe someone want to have a look at it?
I can not post in the official CM10.1-galaxysmtd thread yet.
Greeting, Strainhunter
Click to expand...
Click to collapse
Hello Again,
The problem is gone for me i found out that it has something to do either with the Theme i was using, or/and the Launcher. Because i first switched my Launcher (Nova Launcher) to the Stock one (Trebuchet) (merely just because i did not know how i should fix that problem) then at the after the first reboot with stock launcher the problem was gone, but came back after i rebooted again. So i changed my Theme (JellyBeanExtreme) and the problem did not appear again "knockin´3x on wood^^"
Maybe this can help someone who had or will have this problem.
Greetings,
Strainhunter
wase4711 said:
wiping data will mean you have to reinstall your rom
I've wiped cache/dalvik numerous times, and it still happens
and, when I flash new rom, i factory reset, wipe data/cache/dalvik, and run darkstar system wipe, and it still happens
Click to expand...
Click to collapse
Eh, nope. That would be if you wiped your system. Wiping data will take away all your apps and customizations, but will leave the ROM intact (remember: "ROM" = "Read-Only Memory").
IMO if you want to start anew as a first level troubleshoot, it's much easier to wipe cache/dalvik/SYSTEM, then reflash your ROM and GAPPS. This has solved my problems about 90% of the time, especially when I've installed a mod my phone doesn't like, or done something stupid while messing around in /system/.
CPA Poke said:
Eh, nope. That would be if you wiped your system. Wiping data will take away all your apps and customizations, but will leave the ROM intact (remember: "ROM" = "Read-Only Memory").
IMO if you want to start anew as a first level troubleshoot, it's much easier to wipe cache/dalvik/SYSTEM, then reflash your ROM and GAPPS. This has solved my problems about 90% of the time, especially when I've installed a mod my phone doesn't like, or done something stupid while messing around in /system/.
Click to expand...
Click to collapse
Does that leave your apps and data in place? Never thought of that
Sent from my SGH-I717 using XDA Premium HD app
did u install the walkman app for the note?
I had the same problem. I uninstalled Nova launcher but it was still giving me the same error.
I uninstalled Cobalt theme for CM 10 and that fixed it. Hopefully it gets updated to 10.1, I like the theme.
Sent from my SAMSUNG-SGH-I717 using xda premium
briand.mooreg said:
I had the same problem. I uninstalled Nova launcher but it was still giving me the same error.
I uninstalled Cobalt theme for CM 10 and that fixed it. Hopefully it gets updated to 10.1, I like the theme.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
i was also getting this error using Jamies 10.1 rom.....found out it went away when i stoppped trying to use a theme. im using the TouchWiz launcher and no theme and no more error.
so if any one is using a theme and getting this error stop using a theme and see if that helps....
jrea77 said:
i was also getting this error using Jamies 10.1 rom.....found out it went away when i stoppped trying to use a theme. im using the TouchWiz launcher and no theme and no more error.
so if any one is using a theme and getting this error stop using a theme and see if that helps....
Click to expand...
Click to collapse
It is absolutely the themes that do this. However, from what I read up on it there is literally nothing actually going wrong with the device except for a teeny couple of extra seconds on boot up (which can supposedly be rectified by hitting "Wait" instead of "Stop" or whatever it says.
Actually, I even remember them saying that the mere fact that you're getting the error message means that it's installed correctly.. Something about the stock framework not liking being modified.
CPA Poke said:
It is absolutely the themes that do this. However, from what I read up on it there is literally nothing actually going wrong with the device except for a teeny couple of extra seconds on boot up (which can supposedly be rectified by hitting "Wait" instead of "Stop" or whatever it says.
Actually, I even remember them saying that the mere fact that you're getting the error message means that it's installed correctly.. Something about the stock framework not liking being modified.
Click to expand...
Click to collapse
ya...i noticed nothing was really wrong while getting the error, it just bug me that i was getting that little pop up window. i would hit "wait" or "cancel" and it didnt seem to make a difference, it would go away and that was it. once in a while it would pop back up when getting a text or call, before i could answer the call i had to click it to make it go away to be able to answer. so i decided not to use the theme and not worry about that error.....so would it be any theme or just some themes? maybe ill try other themes and see what happens.....