Related
I rooted and installed a few different ROMs (some didn't take) on my brother's phone, and they seem to work fine until the phone is turned off or the battery runs out. Then the phone freaks out when he restarts, it keeps Force Closing a bunch of different processes and he can't use and will end up having to wipe again. We've done factory wipes, formatted system, cache, dalvik cache when we install ROMs and we keep running into this problem. Any suggestions? I think his battery may need to be replaced, I heard a rumor that it may cause issues, but is there anything else to try? Thanks in advance.
They are the right ROMs for his phone?
OverDosed 4g Slide
Best Porting Team > S.W.a.R.M
chairhome said:
I rooted and installed a few different ROMs (some didn't take) on my brother's phone, and they seem to work fine until the phone is turned off or the battery runs out. Then the phone freaks out when he restarts, it keeps Force Closing a bunch of different processes and he can't use and will end up having to wipe again. We've done factory wipes, formatted system, cache, dalvik cache when we install ROMs and we keep running into this problem. Any suggestions? I think his battery may need to be replaced, I heard a rumor that it may cause issues, but is there anything else to try? Thanks in advance.
Click to expand...
Click to collapse
Under "advanced" in recovery select "set permissions". Something else MAY be going on like you said but most unexplainable force closes come from the permissions somehow getting scrambled.
Good Luck!
K7Cobb said:
They are the right ROMs for his phone?
OverDosed 4g Slide
Best Porting Team > S.W.a.R.M
Click to expand...
Click to collapse
Definitely. They are myTouch 4G Slide ROMs.
WeekendsR2Short said:
Under "advanced" in recovery select "set permissions". Something else MAY be going on like you said but most unexplainable force closes come from the permissions somehow getting scrambled.
Good Luck!
Click to expand...
Click to collapse
I think we tried that, but if it happens again, we'll try again.
Another thing you could try is to install the stock rom then try installing the rom of your choice. Sometimes phones need that type of clear.
Nas Escobar said:
Another thing you could try is to install the stock rom then try installing the rom of your choice. Sometimes phones need that type of clear.
Click to expand...
Click to collapse
I couldn't find a stock ROM that would work. Tried the RUU method and it didn't work.
I wanted to post this in the BAKED thread in the developer section but I don't have enough poststo do it there, so hopefully someone here can help.
I just flashed crespo BlackBean 7 (BAKED) ROM (on my Nexus S) and inverted gapps. It seems to have installed properly but whenever I reboot I get a message that several processes have stopped such as YouTube and GMail, and when I go in to system settings -> storage I get a message saying "Unfortunately, Settings has stopped". I get that message every time consistently. I've tried re-flashing the ROM but to no avail. When I installed the ROM I wiped "Dalvik cache", wiped "Battery Stats" and wiped "Cache partition".
It appears I've not done something or done something wrong, so if anyone here can help I'd appreciate it.
Did you full wipe before installing the rom? That means factory reset/data wipe.
polobunny said:
Did you full wipe before installing the rom? That means factory reset/data wipe.
Click to expand...
Click to collapse
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?
volan1 said:
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?
Click to expand...
Click to collapse
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.
volan1 said:
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.
Click to expand...
Click to collapse
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S
anshumandash said:
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S
Click to expand...
Click to collapse
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?
volan1 said:
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?
Click to expand...
Click to collapse
There isn't any boot issue with the ROM. If you decide to try this ROM again, try to do a clean install.
Boot into recovery, do a factory wipe, go to advanced & wipe dalvik cache, go to mounts & format /systems. Flash ROM & gapps, reboot.
Sent from my Nexus S using xda app-developers app
Hi all. I've had an issue for a few weeks now. I have apps that are constanly locking up and force closing on my phone. I'm currently running Jelly Beans 11 with a rooted and unlocked GS3.
All different apps force close: gmail, play store, kik messenger, system processes. It seems it's not centralized to gapps for instance.
I've installed Beans 5, 6, 8, 9 once. 10 about 2 times, and version 11 i think 3 times. Each time I do a delvik cache wipe, a cache wipe, and a factory reset via CWM. Some times even the initial setup wizard will lock up after first boot.
I've tried flashing different modems as well, and i'm currently on the newest verizon one, the K3.
If anyone has any information on how to fix this it would be much appreciated. Even a full phone wipe or something... I'm going to try clean rom and CM 4.2 tonight.
In a seperate issue, that may or may not be related:
I'm currently in iraq and i'm using the world phone exploit to get cell service and data here in Baghdad. It used to work great, but now the data connection will be connected, but no data will upload or download for long periods of time. For example i could send a kik message while connected to EDGE network, but it might take an hour for it to actually send. It didn't used to do this...
All things considered i'm wondering if I actually physically damaged the phone somehow...
If I haven't provided enough information, please let me know and i'll be happy to reply.
Ok, i tried CM 4.2 and there weren't any lockups. But i couldn't keep the rom, doesn't seem to be any way to get cell service. it won't let me change the band to global.
Going to try clean rom now.
Clean rom works fine as well...
So why would Jelly Beans ROM, that's worked fine for quite a while for me, through various versions of ICS and JB, to suddenly cause apps to force close and general instability?
I've checked MD5's and they're correct...
I think i still need a few more posts before i can post in the dev section as well.
Any help is appreciated, thanks
Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
+1
fixing permissions is a must after a flash/restore.
ok i'll try installing beans again and using fix permissions afterwards.
Thanks
still not working
Ok, i've tried fixing permissions and i'm still having problems. Gapps has stopped working... System UI has stopped working... I followed the above posts exactly.
Any other suggestions?
Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
gapps was the term that the phone said when it crashed. But no i'm not flashing the gapps, they're included on most of the roms like Jelly Beans 11. I've had a few different gapps force close, like the store and gmail. but i've also had the system ui and kik force close.
Sorry man, it's beyond my knowledge. Never had a bunch of apps stop working that fixing permissions or a clean install didn't fix.
Sent from my SCH-I535 using xda app-developers app
How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.
SlimSnoopOS said:
How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.
Click to expand...
Click to collapse
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?
Icewolf69 said:
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?
Click to expand...
Click to collapse
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.
SlimSnoopOS said:
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.
Click to expand...
Click to collapse
I just did a fresh install of 10, including cache, delvik, factory reset, system partition, and after first boot i went back and fixed permissions. I'm still getting force closes. media service, google play, etc. I don't have many apps on it yet to see what else will force close since i'm not using titanium backup to restore anything. Everything is fresh and coming from the play store...
I should be hitting 10 posts soon so i'll be able to try and post in the beans thread, or the dev section. But any other ideas would be appreciated. Thanks.
I also seem to be getting a lot of "invalid file" and "file couldn't be downloaded" when i try to install apps from the store. Not sure what this means
Beans 12 came out today and I tried installing that and i'm getting the same issue.
Tomorrow i'm going to do a full wipe to stock verizon image. and go through the unlock and root motions unless someone has any more ideas.
Thank you for the help so far, i appreciate it.
I did a complete stock OTA flash last night to verizon's jelly bean, and went through the root and unlock process again. flashed beans 12, and i'm still getting the same error.
I'm on beans 6 right now and it's working great. Going to try changing a few settings in 12 to see if it works and then maybe see if 10 works.
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
That's pretty much it
Unfortunately that's pretty much it. Your phone information should eventually stick (dunno why, but it does eventually) but if it doesn't then try another clean install. (btw have you made a backup of your imei, that might help a little as well.) I've had this problem many times and these work for me pretty much every time.
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
IamMark70 said:
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
Click to expand...
Click to collapse
ive been having this issue when i tired both roms so i ended up on cleanrom and then went over to beans for now due to it been base off of clean rom and having the asop look and feel of a aosp rom and the features of touchwiz and the stabilizability of it
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
IamMark70 said:
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
Click to expand...
Click to collapse
yep its pretty good rom i like it. im kinda having a issue with my picture messages though but probably had a dirty flash when i chose the aosp mms. if you like touchwiz also check out cleanrom its a great stock rom best stable rom and pretty great battery life as well and beans rom i think is based off clean well your welcome hope you enjoy the beans rom aslo i had issues with the sim card to so your not alone
IamMark70 said:
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
Click to expand...
Click to collapse
I downloaded Liquid Smooth 2.4, and it finally addressed the issue of the activation screen popping up after every reboot. So I'm extremely happy and loving the ROM!
I run chameleon os custom rom on Samsung infuse 4g. Superuser by Clockworkmod got binded/imbedded into rom. Was working fine, then out of nowhere got disabled under superuser settings and will not change back. I select apps only and all other choices but as soon as I select it, it switches back to disable. Google play no longer shows it as an app that I have downloaded so I can't get updates. I have tried installing it again both by just downloading it and by disabling it under app management and downloading it, but both ways when I open it tries to downloading binaries and fails. Same thing happens with any other superuser I try to download. I cannot get it to work. Please help. I no longer want chameleon as my rom because of too many issues with it constantly rebooting and internet only working sometimes. i want to try another rom but can't with superuser not working. Here is my phone info:
> Model #
> SGH-I997
>
> Android
> 4.2.2
>
> Baseband version
> I997UCLB3
>
> Kernel version
> 2.6.35.7-I997UCLB3-CL9997492-g431d68f
>
> CPU
> ARMv7 Processor rev2 (v71)
>
> ChameleonOS version
> 0.7-20130426-unofficial-infuse4g
>
> Build date
> Fri Apr26 16:05:35 AST 2013
>
> Build number
> cos_infuse4g-userdebug 4.2.2JDQ39
> Cng.andros11.20130426 test-keys
robertmlangdon2 said:
I run chameleon os custom rom on Samsung infuse 4g. Superuser by Clockworkmod got binded/imbedded into rom. Was working fine, then out of nowhere got disabled under superuser settings and will not change back. I select apps only and all other choices but as soon as I select it, it switches back to disable. Google play no longer shows it as an app that I have downloaded so I can't get updates. I have tried installing it again both by just downloading it and by disabling it under app management and downloading it, but both ways when I open it tries to downloading binaries and fails. Same thing happens with any other superuser I try to download. I cannot get it to work. Please help. I no longer want chameleon as my rom because of too many issues with it constantly rebooting and internet only working sometimes. i want to try another rom but can't with superuser not working.
Click to expand...
Click to collapse
You mean to say you cannot boot into CWM recovery and flash a different ROM? Interesting. I have an HTC, and the steps to rooting it are in a different order... that after unlocking the bootloader, you install CWM, and then optionally root the stock ROM with the SuperUser package (those who don't do the last step are usually flashing a ROM instead of mucking around for another second with the stock OS).
SU shouldn't be needed for custom recovery. But maybe Chameleon does something weird like not give you a custom recovery you can boot into? If that's the case, you could pop the device into download mode and go back to stock with Odin, effectively starting from scratch.
still need help, thank you.
I am starting to believe more than before that the actual problem is that somehow my phone got unrooted. How do I set my phone in download mode and use Odin? I usually wipe the cache, install the rom, install gapps, wipe cache partition, and wipe dalvik cache. I have never flashed a rom before. Or even better what is the best way to root my phone again now that I am using chameleon? I believe if I can do that it will fix my problems and I can install cyanfox (the latest rom I have downloaded). Do I use super one click? That is what I think I used before but now that I am not using stock rom I don't know what to use.
robertmlangdon2 said:
I am starting to believe more than before that the actual problem is that somehow my phone got unrooted. How do I set my phone in download mode and use Odin? I usually wipe the cache, install the rom, install gapps, wipe cache partition, and wipe dalvik cache. I have never flashed a rom before. Or even better what is the best way to root my phone again now that I am using chameleon? I believe if I can do that it will fix my problems and I can install cyanfox (the latest rom I have downloaded). Do I use super one click? That is what I think I used before but now that I am not using stock rom I don't know what to use.
Click to expand...
Click to collapse
If you are unable to get into ClockWorkMod recovery (hold Vol-Up+Vol-Dn keys while pressing Pwr button) and have it do anything (so your wipe, install, gapps, dalvik - that process would be called flashing). Then I would Odin back to stock.
For this, you would need to get into download mode. IIRC (just sold my Infuse), it is (with the device fully turned off) hold both volume buttons in while inserting the micro usb cable (that is subsequently inserted into your PC). The ODIN program comes with the download packages (hopefully), so extract the whole package, and run that.
Odin should pick up the phone in the first column as "COMX" (e.g. "COM5"). You are good to flash. To the right, there are PHONE and PDA buttons, click on each, and select the corresponding file (that was also in the package) for each (so PHONE will have something like PHONE.tgz.md5). Once both files are loaded, make sure re-partition is UN-checked, and press Start (or Go, or whatever the action word is). This will take a few minutes, but the COMX column should highlight green with "SUCCESS" in the end.
That's all there is to it. The reason why I'm shying away from SuperOneClick is that it was designed for stock gingerbread/froyo, so it has the potential of breaking something. Hope this helps.
EDIT:
Alternatively, you could try pushing su to the device with adb (depends on how you lost root):
Code:
adb shell mount -o rw,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
adb push su /system/xbin/
adb shell chmod 06755 /system/xbin/su
... with this file (extracted).
Source (with mount point changed)
new problem
I am now running cyanfox which runs android 4.4 and Google.process.gapps has stopped keeps popping up. To get rid of it I have to do a factory reset but after a few days it always comes back. I have Googled the problem and tried numerous things to try to fix it but everything only works temporary. What should I do besides get another phone? I can't afford that right now.
robertmlangdon2 said:
I am now running cyanfox which runs android 4.4 and Google.process.gapps has stopped keeps popping up. To get rid of it I have to do a factory reset but after a few days it always comes back. I have Googled the problem and tried numerous things to try to fix it but everything only works temporary. What should I do besides get another phone? I can't afford that right now.
Click to expand...
Click to collapse
I wouldn;t suggest another phoen is things are working well genrally. The problem could lie in the GApps package or the ROM itself. I use the PA Gapps package. If you are having rouble with that one, try from a different date. Just wipe dlavik in between to prevent any nastyness.
If it still persists, try another ROM, like Carbon.
tried installing the new gapps
So far, so good but I won't know for sure for a few days. I'll keep you up to date. Thank you
what version of android is carbon?
Do you have the link for carbon rom for Samsung infuse 4g? And what version of android is it? My phone runs better with those gapps but I am still getting the same problems. I will give it a try but if carbon doesn't work I am definitely going to have to just get another phone. So far I'm. 0-2 on custom roms for this phone. I thought cyanfox would of worked cause I got it off of xda, which really makes me think this phone has some sort of hardware problem but carbon has been around longer. So maybe it will work better.
Carbon is on XDA as well too, and it is based on CM 11 / Android 4.4 Kitkat:
http://forum.xda-developers.com/showthread.php?t=2137800
Hope this works for you... :fingers-crossed:
problems solved
It appears it was definitely a problem with the ROM. Phone has been operating 100% better. :victory: My cache needs to be cleared frequently and some minor problems with the Facebook back but when isn't there problems with Facebook lol. But as soon as I clean out the cache from my apps, everything is running like new again. I greatly appreciate your help. I can't thank you enough.
Was working great then more problems
Joel,
Carbon was running great for me but then all of a sudden android.process.acore has stopped kept popping up along with all sort of other things stopping then eventually GApps not working again. I have erased my contacts, Erased Media, unchecked all my Syncs, I have tried all sorts of other Gapps packages and even another ROM (cyanogen 11) and they work to begin with then the same problems keep coming back. Is it because I went from Gingerbread right to Kitkat? My phone hasn't worked for about a week now with me trying all different ways to fix it. Do I need to install Ice Cream Sandwich then Jellybean before going to Kitkat or do I just need to try even more GApps? I used to install new ROMs all the time but android has changed so much over the last couple years and when i had to get rid of my old phone and went back to my Infuse 4g the old ROM was just completely outdated and now I can't seem to get this right. The phone itself is still a great phone and I don't understand why I am having these issues. I factory reset, wipe cache, wipe dalvik, install new ROM, install GApps, wipe cache again, and wipe dalvik again. I usually don't wipe the cache or the dalvik until after the ROM and GApps install but just lately have been doing the extra wipe just in-case because nothing else is working. But that has failed too. You have been a great help so far and I can't seem to fix this on my own, so again I turn to you for help. Please help me figure this out.
robertmlangdon2 said:
Is it because I went from Gingerbread right to Kitkat?
Click to expand...
Click to collapse
It's possible. I mentioned this before somewhere, but this could be the after-effect of a small /datadata partition, which having a separate partition is standard in a KitKat ROM (at least for this phone). When it fills up, there's no telling what happens.
Both BeanStalk and CM11 have /datadata partition alternatives (the separate partition has been abandoned) built in. You may want to try one of those:
http://forum.xda-developers.com/showpost.php?p=55574460&postcount=3801
http://forum.xda-developers.com/showpost.php?p=56604749&postcount=593
Unfortunately I couldn't find something similar for Carbon.
Thank you!!!!!!
I hate to count my chickens before they're hatched but I truly believe that was the problem. Even Facebook works now. But I thought I had it fixed before then just under a week and it completely messed up and I couldn't even get it to work for a day after that. But it works now. I can't thank you enough. If you ever come across one for Carbon ROM please let me know. This is a good ROM but I liked Carbon better. Again, thank you Joel. :good::good:
Help!!!!!!!!!!!!!!!!!!!!!!!
Sorry to bother you again Joel but I have a major problem again and I dont even know wht happenned. You have helped me through evrything so far and I couldn't be more thankful. There may be nothing you can do to help me, I don't know. I was using my phone as A Wifi Hotspot when out of know where as soon as i got on facebook on my tablet my phone rebooted on it's own into Clockworkmod recovery. when I reboot it, it goes right back into recovery, it wont read the internal sd card and it wont install any zip off any inserted sd card(it reads them but wont install anything, it always pops up with android guy on his back with a red X and a generic error). it lets me erase cache but won't erase delvik cache or format anything, the screen just flashes and it pops back a screen. I dont think the phone overheated because it wasnt hot to the touch at all. I was only using it as a wifi hotspot for about 30 minutes when it happenned. i had used it as a hotspot many times before with no problems and i dont know how it woud be a virus when i wasnt on any abnormal sites. Any help you can give me would be greatly appreciated. Thank you in advance.
Help!!!!!!!!!!!!!!!!!!!!!!!
Sorry to bother you again Joel but I have a major problem again and I dont even know wht happenned. You have helped me through everything so far and I couldn't be more thankful. The phone might be fried and there may be nothing you can do to help me, I don't know. I was using my phone as A Wifi Hotspot when out of know where as soon as i got on facebook on my tablet my phone rebooted on it's own into Clockworkmod recovery. when I reboot it, it goes right back into recovery, it wont read the internal sd card and it wont install any zip off any inserted sd card(it reads them but wont install anything, it always pops up with android guy on his back with a red X and a generic error). it lets me erase cache but won't erase delvik cache or format anything, the screen just flashes and it pops back a screen. I dont think the phone overheated because it wasnt hot to the touch at all. I was only using it as a wifi hotspot for about 30 minutes when it happenned. i had used it as a hotspot many times before with no problems and i dont know how it woud be a virus when i wasnt on any abnormal sites. Any help you can give me would be greatly appreciated. Thank you in advance.
If you can get into Download Mode, I would Odin back to stock. Are you AT&T or Rogers? There are a couple recent threads in this forum with download links, although people have been having difficulties with finding the AT&T variety.
Unfortunately, that's all I can recommend. Good luck.
we'll see how this works out
I just checked and it will go into download mode. So I guess I just need to find the AT&T thread of Oden and hopefully that works. I have never done it that way before but I read your previous response much earlier in this thread on how to do it and it sounds pretty simple so hopefully I can do it. If you can find a link to the at&t version before me it would definitely help but I will see what I can find.
robertmlangdon2 said:
I just checked and it will go into download mode. So I guess I just need to find the AT&T thread of Oden and hopefully that works. I have never done it that way before but I read your previous response much earlier in this thread on how to do it and it sounds pretty simple so hopefully I can do it. If you can find a link to the at&t version before me it would definitely help but I will see what I can find.
Click to expand...
Click to collapse
Looks like you are all set for the files then.
I just PM'ed everyone who I've recommended those packages in the past. Hopefully I get a bite.
found a thread but need your help
I found a thread with links but with what is written on this thread I am confused. The thread link is
http://forum.xda-developers.com/showthread.php?t=1613523
I'm not sure what to download and if anything needs to be changed after downloading it or if this link is a waste of my time. I was hoping you could help. Thanks.
robertmlangdon2 said:
I found a thread with links but with what is written on this thread I am confused. The thread link is
http://forum.xda-developers.com/showthread.php?t=1613523
I'm not sure what to download and if anything needs to be changed after downloading it or if this link is a waste of my time. I was hoping you could help. Thanks.
Click to expand...
Click to collapse
I would recommend Option D for what you need, but AFAIK, the links on this page are dead.
If you go to the last page though, there is a link for Option C, which would work for your needs. Hope this helps.