When i picked up my charge i also got the desk cradle with the extra battery. Yesterday at work i was listening to music and drained the battery pretty quickly so i swapped in the extra battery. Once i rebooted i started getting a bunch of FC's. I'm getting ones for Google Services Framework, messaging, android.processes.acore and one or two others i can't remember. I reflashed GC and still get the errors. Anyone have any idea why this would happen after swapping batteries and how to fix this?
Sent from my SCH-I510 using XDA App
It just happens sometimes. Ill have to do this once every 3 months or so. Hope you made a backup...If you have the EXT4 formatter saved then just mount all in CWM, wipe all user data, dalvik, cache, etc. Then run EXT4 formatter, then flash GC. If you don't have it, you have to restock with the EE4 Odin and PIT, then reflash GC.
Sent from my Droid Charge running GummyFroyo 1.9.1
Happened to me a week or so ago, huge pain because I hadn't backed up in a while but it took me about a day or two to get all my apps back in order. In all honesty though it was one of the most annoying things that could happen. Had to redownload a ton of my apps and all the apps I had backed up were outdated(like ColorNote, I lost like 4 notes because it was an old backup). Happened totally out of the blue, I just rebooted the phone because apps weren't installing and I got spammed with FCloses. Not even a factory reset/cache/Dalvcache worked I had to flash the .pit/ee4factory.md5 to get my phone working again. PAIN IN TEH ASH.
Well son of a batch of cookies. That was my last resort but i suppose i will give that a shot this evening and report back to ya.
Sent from my SCH-I510 using XDA App
I finally got around to restoring my phone using the EE4 ODIN. I had no idea it was going to take over an hour to do, lol. Anyway, the flash completed and passed so I unplugged the USB cable, pulled the battery, but now I can't get the phone to turn on. Is there something else that I screwed up?
Lockett said:
I finally got around to restoring my phone using the EE4 ODIN. I had no idea it was going to take over an hour to do, lol. Anyway, the flash completed and passed so I unplugged the USB cable, pulled the battery, but now I can't get the phone to turn on. Is there something else that I screwed up?
Click to expand...
Click to collapse
It should have not taken an hour. If you flashed without the battery try flashing again with the battery in.
Also make sure you are using the PDA button.. not phone. Flash will show pass if you use phone but it will not boot.
Sent from my SCH-I510 using XDA App
Yep that was the mistake i made. I was in a rush to get my phone back up and running before i went to sleep that i accidently used the phone option. I reflashed using PDA and all is well. Now i just have to reroot.
Sent from my SCH-I510 using XDA App
I dont know if you were rooted and on a rom already but for future ref., when this happened to me I just went into CWR, fixed permissions, wiped cache and dalvik, rebooted and bam the FClosing stopped. my wifes phone on the other hand I had to just go into CWR and flash the rom over again and it cleared the problem rather than going through ODIN.
jrock7885 said:
I dont know if you were rooted and on a rom already but for future ref., when this happened to me I just went into CWR, fixed permissions, wiped cache and dalvik, rebooted and bam the FClosing stopped. my wifes phone on the other hand I had to just go into CWR and flash the rom over again and it cleared the problem rather than going through ODIN.
Click to expand...
Click to collapse
I was rooted and running GC 1.9.1. I went into CWR and tried wiping just the cache and dalvik as well as flashing the rom again and I couldn't get the FC's to stop. Thanks for the info, I'll keep this in mind next time this happens.
I was on GC 1.9 when my mega galore of FC's started happening too, my end result was a replacement phone from Verizon... I really don't know what happened or why. It just randomly happened under normal use.
Wow, that kinda sucks. They didn't say anything about the phone being rooted? They gave me hell for trading my rooted D2G for my charge.
Lockett said:
Wow, that kinda sucks. They didn't say anything about the phone being rooted? They gave me hell for trading my rooted D2G for my charge.
Click to expand...
Click to collapse
No because I flashed a bone stock ED1 with no root and nothing at all on the phone, I even had a blank 2GB SD Card in it.
Same happened to me. Yesterday I just clicked on camera and got a force close, then froze. Pulled battery, then everything was force closing. Only thing that would function was browser. Flashed everything, wiped data, you name it. Nothing has worked for me.
Happy! said:
Same happened to me. Yesterday I just clicked on camera and got a force close, then froze. Pulled battery, then everything was force closing. Only thing that would function was browser. Flashed everything, wiped data, you name it. Nothing has worked for me.
Click to expand...
Click to collapse
Just do what I said.
Sent from my Droid Charge running GummyFroyo 1.9.1
Did the rom you were running have journaling turned off by default?? If so, any improper shutdown will result in data corruption.
Sent from my SPH-D700 using xda premium
And I second clearing the cache and dalvik.
Sent from my SPH-D700 using xda premium
nismology said:
And I second clearing the cache and dalvik.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
When I had this problem clearing cache and dalvik didn't help at all.
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
When I had this problem clearing cache and dalvik didn't help at all.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
It depends on the level of data corruption I suppose. As an aside, roms should really be released with journaling enable or at least have that option. The slight speed increase is not worth the hassle IMO.
Sent from my SPH-D700 using xda premium
When it happened to me one the first things I tried was wiping cache and nothing worked. If you follow kv's advice and that doesn't work then the only other method would be to odin back to stock and start fresh. I did have one fc for android.processes.acore but I can't remember what I did to cause or replicate it. The only thing I'm having trouble with now that I rerooted the phone is that I cannot get back into CWR. I flashed the latest version and was able to get in to flash gc and everything else but now when I try to get in it locks up on the samsung logo.
EDIT: I wasn't able to get past the Samsung logo no matter what I tried. I ended up having to odin back and start fresh....again.
Sent from my SCH-I510 using XDA App
nismology said:
It depends on the level of data corruption I suppose. As an aside, roms should really be released with journaling enable or at least have that option. The slight speed increase is not worth the hassle IMO.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Is there any way to re-enable it?
Related
I have had Hienz 57 running for about a month now and it seems to be running really slow. Even while doing the smallest things like typing it will be a couple letters behind. Anyone have any ideas. I have cleaned all the app caches and deleted what I don't use any more but still slow.
1fast72 said:
I have had Hienz 57 running for about a month now and it seems to be running really slow. Even while doing the smallest things like typing it will be a couple letters behind. Anyone have any ideas. I have cleaned all the app caches and deleted what I don't use any more but still slow.
Click to expand...
Click to collapse
Rebooting usually fixes this for me
Sent from my SCH-I500 using XDA App
That sometimes works but I was kinda looking for a more permenent solution. Would wiping the cache or dalvik possibly help?
1fast72 said:
That sometimes works but I was kinda looking for a more permenent solution. Would wiping the cache or dalvik possibly help?
Click to expand...
Click to collapse
you got voodoo enabled. what are your settings like...maybe you just need to re-odin then reflash the ROM and stuff...sometimes phones just need a fresh start
^Agreed. I can't count the times if done that. Mostly after I have went through five or so kernels but none the less it can't hurt and I haven't done it yet and regretted it.
Tap-a-Talked
There's a formatting utility here:
http://forum.xda-developers.com/showthread.php?t=1090127
I used the ext4 (voodoo) version and it worked great. I know they mean nothing, but I was getting 1500-1600 Quadrant scores before I ran it (still with voodoo), and I'm getting 1700-1800 now.
Sent from my Kangbanged Mesmerize
edit: This does wipe everything, so run your backups beforehand if you decide to try it.
That's the one I used today and it is freakin sweet. An excellant tool.
Tap-a-Talked
Yes I have voodoo enabled. I have not changed any voltage settings yet. When you say to re-odin are you saying to flash back to stock ec10 and then reflash the hienz 57? Still learning the terminology. I did go from the voodoo kernel to hienz without a fresh start. I also didn't wipe the data but for the first few weeks it ran awesome. I have also had a few half reboots. Like it would go to the android logo but not all the way to the samsung logo
defenestrado said:
There's a formatting utility here:
http://forum.xda-developers.com/showthread.php?t=1090127
I used the ext4 (voodoo) version and it worked great. I know they mean nothing, but I was getting 1500-1600 Quadrant scores before I ran it (still with voodoo), and I'm getting 1700-1800 now.
Sent from my Kangbanged Mesmerize
edit: This does wipe everything, so run your backups beforehand if you decide to try it.
Click to expand...
Click to collapse
+1 works great
Thinking of trying this but did you have the cwm 3 or just the 2.5.x? Also can I just flash the H57 zip and be back up and working?
Ran the utility and worked great. Have more memory too so the tons have been staying behind a little. Phone is much smoother and faster.
Sent from my SCH-I500 using XDA App
Normally i have zero issues with lag, however as of late I've had some slight issues with lag as well, even with lagfix enabled - to remedy it I simply enabled the 1120 overclock step and it's been fast ever since (and not too bad on the battery)
I just happened to be browsing the Sd card since I just dl the newest H57 and noticed that after formatting I dont have the android secure folder. Is this a problem or will it create a new one?
Sent from my SCH-I500 using XDA App
so unfortunately i just dropped my phone and now whenever i try to open mu sms app i just get a force close. anyone have any ideas what i should do? i'm not home so i havent really tried anything yet.
Sent from my SCH-I510 using XDA App
Restart.
Sent from my Droid Charge running GummyFroyo 1.9.1
so far ive restarted, takem battery and sim out and ive also reapplied gummy 1.9x update
Sent from my SCH-I510 using XDA App
Hope you made a backup of everything. Have fun reflashing either use Ext4 Formatter and flash GC in CWM or depart and restock with Odin.
Sent from my Droid Charge running GummyFroyo 1.9.1
haha yeah thats what im gonna try when i get home ill report after
Sent from my SCH-I510 using XDA App
You can try wiping the dalvik cache and cache partition. This is the first thing I do when I get FC's and it works half the time.
I flashed stock froyo ee4 from the charge kit thread and got stuck in a bootloop. Then I flashed the gummy rom that is in that thread and the messaging still didn't work. hmm
Did you try going back to stock with the PIT file and all?
Are you talking about this thread? http://forum.xda-developers.com/showthread.php?t=1111486 I tried flashing with the PIT and the ed2 rom but it said the md5 was invalid on the rom. Then I redownloaded it and the same thing happened. I'm in the process of downloading the other rom he posted but its taking forever. Is the PIT file only useable with those two he posted?
Edit: I was able to flash the stock froyo ee4 in the chargekit thread and the messaging force close is still happening.
Try this one. http://forum.xda-developers.com/showthread.php?t=1172182&highlight=ee4+stock
hazard209 said:
Try this one. http://forum.xda-developers.com/showthread.php?t=1172182&highlight=ee4+stock
Click to expand...
Click to collapse
That worked! Thanks man, I was getting a little worried here haha.
No problem. Glad you got it working.
I recieved the OTA update for the G2x to the latest v21y firmware and Gingerbread 2.3.4 OS. Everything seems to have gone fine, except that now in Google Play apps it gives me the following error when trying to install or update *any* app:
'Error downloading "xxx". There is insufficient space on the device.'
Of course, I have an additional 8 GB micro SD card that is almost totally empty, and the internal phone storage has 3.2 GB available. The phone memory lists 0.94 GB available as well.
I followed the usual advice of clear data / clear cache for both Google Play and Download Manager. I unmounted/mounted both phone and SD cards. I turned off the phone, pulled the battery for a bit, took out the external SD card, put the battery back in, and booted back up. I rebooted a bunch of times. I put the external SD card back in. I cleared off extra crud from phone storage via a file manager, and I cleared caches on all installed apps.
This has never happened before, and directly after the update it has happened 100% of the time I have tried.
Any ideas? Is this happening to anyone else who got the update? (I'm completely on stock, btw, still not out of warranty.)
Clear market apparently cache/data
Sent from my LG-P999 using xda premium
kwes1020 said:
Clear market apparently cache/data
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
mikefarny said:
I followed the usual advice of clear data / clear cache for both Google Play and Download Manager.
Click to expand...
Click to collapse
Isn't that it? Is there something more that constitutes clearing market cache/data?
mikefarny said:
Isn't that it? Is there something more that constitutes clearing market cache/data?
Click to expand...
Click to collapse
Oh reading fails me sometimes. Try wiping cache and dalvik in cwm maybe.
Sent from my LG-P999 using xda premium
kwes1020 said:
Oh reading fails me sometimes. Try wiping cache and dalvik in cwm maybe.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Does that require rooting? I haven't installed CWM yet, as I was holding off on all the experimentation until my year was up.
If there's no other usual thing to try, if T-mo doesn't come back with a reasonable response I suppose that's the next step.
mikefarny said:
Does that require rooting? I haven't installed CWM yet, as I was holding off on all the experimentation until my year was up.
If there's no other usual thing to try, if T-mo doesn't come back with a reasonable response I suppose that's the next step.
Click to expand...
Click to collapse
No it requires Nvflashing cwm. But that will ruin your "warranty" on a end of life phone
Sent from my Galaxy Nexus using xda premium
Or a factory reset beofre rooting, although if you factory reset might as well root the phone lol.
Sent from my LG-P999 using xda premium
mt3g said:
Or a factory reset beofre rooting, although if you factory reset might as well root the phone lol.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
You can factory reset without root. That's what T-Mobile will tell you to do anyways. I've went through six g2x in the past two weeks...that's their answer to everything lol
Sent from my Galaxy Nexus using xda premium
I'm aware of that, just saying that's an option.
Sent from my LG-P999 using xda premium
mt3g said:
I'm aware of that, just saying that's an option.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I root everything I get on day one. Nothing stock and limiting my user options appeals to me. You can always revert to stock or if you hard brick no one could tell anyways.
Sent from my Galaxy Nexus using xda premium
So a factory reset fixed it. I didn't have to wipe the phone and external SD, and so I'm just reinstalling apps and setting up a few of them. This was a good time for some spring cleaning anyway, I suppose.
It was probably some stupid permissions thing, but without root I can't even fix that.
mikefarny said:
So a factory reset fixed it. I didn't have to wipe the phone and external SD, and so I'm just reinstalling apps and setting up a few of them. This was a good time for some spring cleaning anyway, I suppose.
It was probably some stupid permissions thing, but without root I can't even fix that.
Click to expand...
Click to collapse
U got the ota? Nandroid it, and send it to kwes
Sent from my LG-P999 using XDA
What is this update supposed to accomplish anyway? I'm rooted and trying ROMS pretty much every week (since no ICS rom works for me as a daily driver). Should I / can I do the update to 21y?
V21y 2.3.4 Rooted Touch Key lights
so everything else works fine when it comes to rooted app root request, but for some reason when a touch key light app request permisson it can do the job of adjusting the touchkey brightness, however the screen becomes very unresponsive, to the point where you cant slide left and right... I have run out of ideas as to why this is? has anyone else experienced this? I like to be able to turn that brightness down
Yesterday my Droid Charge running Tweaked 3.2 would not boot, it would get past the samsung logo and start the boot animation and then turn off. Booting into recovery, several things were not mounting, was not able to wipe Dalvik cahce, only regular cache.
When I try to ODIN back to stock with PIT, it always fails on movinand.bin
I used Samsung PSTLite as well with the same result, failing on movinand.bin
I have tried flashing to ED1 and EP4.
I can flash ROMS such as Tweaked that do not have movinand.bin, but the phone does not start up at all afterwards.
Download mode still works.
What can I do??
LethalMonk6 said:
Yesterday my Droid Charge running Tweaked 3.2 would not boot, it would get past the samsung logo and start the boot animation and then turn off. Booting into recovery, several things were not mounting, was not able to wipe Dalvik cahce, only regular cache.
When I try to ODIN back to stock with PIT, it always fails on movinand.bin
I used Samsung PSTLite as well with the same result, failing on movinand.bin
I have tried flashing to ED1 and EP4.
I can flash ROMS such as Tweaked that do not have movinand.bin, but the phone does not start up at all afterwards.
Download mode still works.
What can I do??
Click to expand...
Click to collapse
Have you tried a data wipe/factory reset via cwm?
Sent from my XT907 using xda app-developers app
Yes, I can flash and boot into CWM, but wiping factory data does not do anything, it also shows multiple "error mounting such and such" messages
jco23 said:
Have you tried a data wipe/factory reset via cwm?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Try to re-PIT only.
Sent from my SCH-I510 using xda premium
What am I supposed to do after re PIT'ing? (which I have done, sucessfully)
Then flash any ROM, probably a stock one. Make sure the MD5 is good. Tell us your exact process for Odin-ing something.
Sent from my SCH-I510 using xda premium
This is what I have been doing the whole time, same result.
I know my process for ODIN'ing to be correct, battery in, SD card out, PDA checked only.
Its something other than that, I've flashed return to stock many times in ODIN before...
Is there something else I can do besides simply ODIN'ing, as I've said, I've tried ODIN and PST Lite, both failing at movinand.bin
When flashing straight to for example Tweaked, it works fine, as there is no movinand.bin
At this point, it does not even show the samsung logo anymore, the screen just quickly flashes for a moment and then turns off. Download Mode is still working though. Recovery does not boot either.
Correction, CWM does boot, but none of the partitions are mountable.
Umm, The same exact thing happen to me couple of weeks ago, I got tons of error about mounting. I know I am not helping, but I gonna say my case anyway. I tried PIT (repartition) several times, didn't work! It was random! it worked one time, and I was able to flash the pit, but when I tried to flash the EP4D didn't work! I only was able to get to the home 2 times and got tons of force-closing warnings. I have insurance, so I got a replacement. I hope you are covered as well! Just wanted to share
A fail at movinand indicates a corruption at a hardware level. I've actually pulled mine out of death (had the same issue once upon a time) just by spamming PST over and over again but I seem to be the only one who had ever succeeded in that. You're probably going to have to end up getting a new device but hey, they won't be able to tell you rooted.
Sent from my SCH-I510 using xda premium
kvswim said:
A fail at movinand indicates a corruption at a hardware level. I've actually pulled mine out of death (had the same issue once upon a time) just by spamming PST over and over again but I seem to be the only one who had ever succeeded in that. You're probably going to have to end up getting a new device but hey, they won't be able to tell you rooted.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
At this point it won't even matter. My phone broke like this and I got it switched in on the last day of warranty (luckily), and that was in August.
one last check:
have you tried using a different USB cord/USB port/different computer? I, along with many others, have experienced issues when flashing via odin with a bad cord/port (even though it had worked before). when I switched cords, it worked. but this mostly happens when the computer/ODIN fails to recognize the phone.
also, I did not remove the SD card in any of my flashings. I think once, I did remove the battery just to get the phone into download mode.
oh, and another option could be the kernel/partition/boot animation you were last on. I would recommend to try to make sure you are on RFS with stock FP5 before flashing anything.
but i suspect kvswim is probably right.
hope this helps.
ok, thanks for the help guys. I'm quite sure I dont even have a warranty on my phone, so that sucks. Might try to go into Verizon and see what happens anyway.
Do you think its worth sending it to MobileTechVideos for them to debrick, or is this outside of what they do, since it still can go into Download mode...
LethalMonk6 said:
ok, thanks for the help guys. I'm quite sure I dont even have a warranty on my phone, so that sucks. Might try to go into Verizon and see what happens anyway.
Click to expand...
Click to collapse
The phone comes with a 1 year warranty.
Sent from my SCH-I510 using Tapatalk 2
Hey Guys - I am out of ideas and think my run with the charge might be coming to an end.
My phone is running FP8 stock ROM, rooted, with some apps frozen using TiBu. I have not issues with this set up since the update was pushed. I used tweak for a year or so, then went back to stock for FP8.
A few days ago my phone started to act weird. Widgets were not updating, apps randomly force closing. It was annoying but still usable. I decided to do a factory reset and then everything hit the fan. When I boot up the phone every app on my phone force closes and it is not usable. The "Setup Wizard" also force closes so I can not even get past that.
I have tried flashing other ROMs including Eclipse, tweaked, EP4 with pit, etc.The flash is successful but the force closes persist. I have also tried wiping data through stock recovery and CWM, but I do not think it works. I still see force close errors when the phone boots of apps that should have been wiped (twitter,TiBu, etc.). Anything else I can try? Pretty desperate as it looks like this thing might be toast.
Cliffs
Phone acting weird, reset data multiple times and everything force closes. Phone is not usable at all.
Tried wiping data but does not seem to work, downloaded apps still force close
Flashed different ROMS (both stock w/ pit and custom)
Still force closing. Help?
If the force closes are persisting even though data is wiped, you may have something nasty sticking around through dirty flashes (assuming you're flashing over the old). Make sure you clear all caches and if that doesn't work, it's a shot in the dark but you may want to try formatting the system partition through CWM and then reinstalling FP8 or whatever custom ROM you want. Whatever you do have backups ready...
Sent from my Barnes & Noble Nook Tablet using xda premium
dejello said:
If the force closes are persisting even though data is wiped, you may have something nasty sticking around through dirty flashes (assuming you're flashing over the old). Make sure you clear all caches and if that doesn't work, it's a shot in the dark but you may want to try formatting the system partition through CWM and then reinstalling FP8 or whatever custom ROM you want. Whatever you do have backups ready...
Sent from my Barnes & Noble Nook Tablet using xda premium
Click to expand...
Click to collapse
Thanks for the idea. I am pretty sure I have already tried this but through CWM I will clear cache, davlik cache, data, and format system then try a flash of stock with .pit
Like you said, it seems like whatever is causing this is still sticking around even after all this clearing/flashing. Is there any way to clear these things through adb? Or would getting a log be worth my time?
If all else fails try odin.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
If all else fails try odin.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I have tried flashing ROMS (stock and custom) through ODIN and to no avail. I am able to flash but it still does not overwrite the corrupted data. I still get force close errors for downloaded apps that should have been erased/over written. Even formatted my SD card just to be sure and didn't help.
Seems like my only option may be to somehow find and delete the data through ADB. Clearing through CVM and stock recovery is not doing anything. Problem is I do not know where this old/bad data is!
SamsungPST?
Sent from my SCH-I510 using xda premium
kvswim said:
SamsungPST?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Never heard of PST when you posted that. Good idea, but I just tried a few flashes and the effect was no different than ODIN/CWM
This problem keeps getting weirder. So sometimes I am able to get through into the phone (even though I get force close pop ups every 2 seconds). I was able to uninstall most of the apps causing the FCs (not all because some are the system apps).
However, everytime the phone reboots the apps come back! Where in the hell are they being cached/stored to just magically re-appear after data wipes/flashes/un-installs. Seems like I have all these corrupted apps that I can not get rid of. Through terminal emulator I cleared data, and davlik but didn't help.
Have you pulled your sd card and sim then checked if it would boot. Also wipe internal sd from stock recovery
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Have you pulled your sd card and sim then checked if it would boot. Also wipe internal sd from stock recovery
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Yea, eventually I can get it to boot but the phone is not usable with all the force closing. The option to clear internal SD only seems to be available for the older ROMS, but I flashed ED1 and cleared it. No luck.
Think I may just be out of ideas on this one...
Pray to jeebus, might be your last option
Sent from my SCH-I510 using xda premium
Have you gone into Settings, Accounts & Sync and turned everything off? If you are back to stock then this could be the cause of restore of the apps. You are using the full EP4 odin - rom, kernel and radios - correct?
Sent from my SCH-I510 using xda app-developers app
Reilly1812 said:
Have you gone into Settings, Accounts & Sync and turned everything off? If you are back to stock then this could be the cause of restore of the apps. You are using the full EP4 odin - rom, kernel and radios - correct?
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Yep I have turned them off. My settings also get reset however when I clear data, reboot, re flash etc.
Good question about the full EP4 ODIN. I have been using the ones from imnuts website, and have also tried the CWM packages from kvswim's thread in the development section. Tried Eclipse Beta 2 & EP4,EE4,ED1, FP8 stock. I also tried the CM10 ROM just to see if the change to ext file system would do anything. Not sure if any of them are labled as having rom,kernal and radios, but I would imagine at least a few of them are.
No matter what I do, I get outsmarted and all my corruped apps, settings and force closes remain.
I think you can skip activation after flashing ep4 and still get the ota's to get to fp1, fp5 and finally fp8. once there try activation, etc. Keep it purely stock no root. still fc's? IMHO your phone storage is hosed.
Sent from my SCH-I510 using xda app-developers app
Reilly1812 said:
I think you can skip activation after flashing ep4 and still get the ota's to get to fp1, fp5 and finally fp8. once there try activation, etc. Keep it purely stock no root. still fc's? IMHO your phone storage is hosed.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I was thinking it was a hardware failure to
Sent from my SGH-T889 using xda app-developers app
Reilly1812 said:
I think you can skip activation after flashing ep4 and still get the ota's to get to fp1, fp5 and finally fp8. once there try activation, etc. Keep it purely stock no root. still fc's? IMHO your phone storage is hosed.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
To skip activation - on the setup screen click on the Emergency Dial button. Once at the dialer, dial:
*#TESTMODE (or *#83786633)
That will "enable the soft keys", making it so you can then hit home to get to the launcher without activating.
dwitherell said:
To skip activation - on the setup screen click on the Emergency Dial button. Once at the dialer, dial:
*#TESTMODE (or *#83786633)
That will "enable the soft keys", making it so you can then hit home to get to the launcher without activating.
Click to expand...
Click to collapse
Pretty cool! Didn't know I could do that. However once getting past that just about every app continues to force close including tw launcher.
Being that old apps & settings will continue to be restored after doing everything possible to get rid of them it must be a hardware issue.
Oh well, I will keep the phone around for the hell of it but guess it's time I look into something new.