Related
My coworker is not able to OTA update her completely stock (never rooted/modded) Facinate to 2.2, but when she goes to System Updates->Check New, there is a pop up that says "Please Wait" that stays on the screen for a while, then just goes away and nothing happens.
Also, if you go to System Updates->Status, it says "Server Unavailable" Code: 500.
The only thing I can think of is that Verizon is only letting particular regions update at a time to prevent the server from bogging down. Any ideas?
Verizon seems to be having network issues since 2am. Even if you have a data connection, they probably offlines the OTA servers until the problem is resolved.
http://community.vzw.com/t5/4G-Disc...TE-outage-ETA-for-repair-and-other/m-p/513354
She is on stock DI01, and we downloaded the Verizon official ED01, but it says that it cannot find EA28. So, we downloaded EA28 official zip, and now it says that it cannot install because it needs DL09. Sooooo, should we now look for DL09? There has got to be a more simple way...
I'd leave her at stock and just be patient. Verizon's system will come back.
still down
I am having the same issue, even tried the DL09 no luck
I've had the same issues since the day the update came out but I had ODIN'd EB01 and then ODIN'd back to Dl09 and tried everything but got the server unavailable issue. I gave up and just flashed the ED01 update.zip.
After a lot of trying different things and giving up, an awesome dude posted the solution here: http://forum.xda-developers.com/showpost.php?p=13313409&postcount=12 . I followed the steps and it worked like a charm.
If it helps, my wife's stock, never rooted fascinate had the exact same problem, and using whosdaman's awesome post, I used the stock recovery to manually install froyo- it's still completely stock, and worked like a charm:
http://forum.xda-developers.com/showthread.php?t=1044230
artvandelay440 said:
If it helps, my wife's stock, never rooted fascinate had the exact same problem, and using whosdaman's awesome post, I used the stock recovery to manually install froyo- it's still completely stock, and worked like a charm:
http://forum.xda-developers.com/showthread.php?t=1044230
Click to expand...
Click to collapse
This method is well known, but the OP was asking about OTA.
Been looking for a solution for the past 12 hours and have not found any.
Bought a stock i777 with 2.3.4, flashed with SGH-I777_ClockworkMod-Recovery_5.0.2.3 and a stock 2.3.5 AT&T ROM. After ANY kernel is flashed, I seem to lose WiFi capability. I have 5 wireless points near my house and it just gets stuck on "Scanning" and then the WiFi turns off. No points are even listed!
Currently running CW 5.0.2.3 kernel, 2.3.5 AT&T stock ROM, UCKJ1 baseband, kernel 2.6.35.7.
TL-DR - Flashed and lost wifi ability.
Which 2.3.5 ATT stock rom is this that you're referring to? Have a link to where you got it from?
I believe I got it from here: androidadvices.com/update-samsung-galaxy-s2-i777-gingerbread-235-firmware/
Did it work initially when you went to 2.3.5? You said you've tried some different kernels, at what point did you notice the wifi broke?
I even reflashed using kernel + non-rooted system package located in this thread: http://forum.xda-developers.com/showthread.php?t=1286432
Still no WiFi showing. Just says "scanning" then the wifi shuts off.
Update: Flashed Entropy512's stock package + nonrooted with no luck. No wifi. Flashed zetamax kernel after. Still no wifi.
Showed at that time: version 2.3.4, 1777UCKH7 baseband, 2.6.35.7_ZedomaxStockKernel.
Flashed again with a I777UCKJ1 2.3.5 ODIN package that I know will fix the WiFi. It shows version 2.3.5, 1777UCKJ1 baseband, 2.6.35.7 kernel.
Seems like if I flash ANYTHING else besides this the wifi stops working on me.
Solved problems for myself.
Completely unrooted, reflashed ATTGalaxyS2Unroot_SGH-i777.tar. This brought me back to the original AT&T firmware that came with the phone. I then flashed SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar and subsequently used SuperOneClick 2.2 to root.
WiFi seems to be working fine now. I am now running a stock 2.3.4 ROM, UCKJ1, kernel 2.6.35.7...Clockworks version.
If anyone else is having the same issue this should help.
Thanks for the updates. Sounds like a frustrating battle. Glad all is well.
Sent from my páhhōniē
rpesta said:
Solved problems for myself.
Completely unrooted, reflashed ATTGalaxyS2Unroot_SGH-i777.tar. This brought me back to the original AT&T firmware that came with the phone. I then flashed SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar and subsequently used SuperOneClick 2.2 to root.
WiFi seems to be working fine now. I am now running a stock 2.3.4 ROM, UCKJ1, kernel 2.6.35.7...Clockworks version.
If anyone else is having the same issue this should help.
Click to expand...
Click to collapse
Hrrrrm Having the same issues and the only way I could manage wifi to get back on was going to 2.3.5 which had it's own set of issues. I tried following your steps but one thing I noticed you said you were running UCKJ1 but isn't that 2.3.5? When I flash the exact same files I am still stuck without working wifi
Still noobing it up here - hopefully I can either stumble upon a fix like you did or spot someone else's that matches my issues...
Avoid that androidadvices.com **** - Half the time they link to firmware that isn't even for the device it claims it is, carrying a high risk of a hardbrick.
I only experienced this when I was trying to upgrade kernels using the SHOstock ROM. I get no wifi with siyah and can't send MMS with Entropy's kernel. That's the only time I've had those issues. Maybe you had a bad download? Glad you got it fixed though.
Just to clarify, those kernels work great with most other ROMS I've tried them on.
Sent from my SAMSUNG-SGH-I777 using XDA App
Had the same problem
I had this problem (with wifi, not mms) after rooting from 2.3.6. I eventually flashed Zedomax's kernel using mobile odin and wifi functionality was restored.
I still haven't moved on from there, but probably will sometime this week.
Jank4AU said:
I only experienced this when I was trying to upgrade kernels using the SHOstock ROM. I get no wifi with siyah and can't send MMS with Entropy's kernel. That's the only time I've had those issues. Maybe you had a bad download? Glad you got it fixed though.
Just to clarify, those kernels work great with most other ROMS I've tried them on.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Weird, I cannot think of anything that would cause MMS to fail - what sort of errors?
It's happened to me several times after I flash a kernel. when I attempt to send an mms it just hangs and says sending but it never goes out. Could it be a conflict as I have Chomp set as my primary messaging app? Although if that were the case it should be able to send from one or the other but it doesn't. Can't remember for sure but I believe that I may have flashed the kernel cleaning script beforehand in each instance. The only way I've been able to fix it is to reinstall everything starting with the ROM. I'm sure it's user error.
As info, steps I took to try to fix before I restored:
1) reflash kernel
2) flash radio again
3) tried all 5 radios released (not a radio problem I'm guessing)
4) wipe dalvik and reflash kernel
5) run kernel cleaning script and reflash kernel
No dice, it was bizarre. Is this even the sort of event that you could get an error log from? There was no FC or any error message, you know? If it happens again what can I provide you that would help...can I do a logcat or whatever? ;-)
By the way,I could receive mms, just not send.
Sent from my SAMSUNG-SGH-I777 using XDA App
I have no wifi but I'm looking for the ATTGalaxyS2Unroot_SGH-i777.tar and I can't find any link, can you point me there? thanks
AMATHEU said:
I have no wifi but I'm looking for the ATTGalaxyS2Unroot_SGH-i777.tar and I can't find any link, can you point me there? thanks
Click to expand...
Click to collapse
Here you go. It is a sticky in the development threads
http://forum.xda-developers.com/showthread.php?t=1286432
AMATHEU said:
I have no wifi but I'm looking for the ATTGalaxyS2Unroot_SGH-i777.tar and I can't find any link, can you point me there? thanks
Click to expand...
Click to collapse
galaxys2root.com's kangs are not supported here...
A proper supported package was linked in the post above.
Factory Data Reset restored wi-fi
I was on UCKK6 (2.3.6) and rooted by flashing Entropy512's Return/Unbrick to Stock (2c)
http://forum.xda-developers.com/showthread.php?p=18576627
and lost wi-fi (scanning then wi-fi shuts off).
Since I was reverting from UCKK6 back to UCKH7, I had to do a factory data reset
(Menu > Settings > Privacy > Factory Data Reset)
based on the info in this thread:
http://forum.xda-developers.com/showthread.php?t=1286432
I got wi-fi back once I did the Factory Data Reset.
I'm having the same problem
Giant noob here =(
Could someone post step by step instructions on how to unroot so that I can restore my wifi?
For example, if in fact doing the factory data reset as described in the post above me is the correct course of action... is there a way to do a backup before so that I do not lose all my apps and stuff?
Thanks
RocketOptics said:
I was on UCKK6 (2.3.6) and rooted by flashing Entropy512's Return/Unbrick to Stock (2c)
http://forum.xda-developers.com/showthread.php?p=18576627
and lost wi-fi (scanning then wi-fi shuts off).
Since I was reverting from UCKK6 back to UCKH7, I had to do a factory data reset
(Menu > Settings > Privacy > Factory Data Reset)
based on the info in this thread:
http://forum.xda-developers.com/showthread.php?t=1286432
I got wi-fi back once I did the Factory Data Reset.
Click to expand...
Click to collapse
Was having problem with WiFi on my T-Mobile SGS2 where it was seem like it was turning on, then try to start scanning for networks then would automatically turn off...I was pulling me hair out reflashing it with different ROMs, and Radios, and doing a "Factory Data Reset" from inside the main Settings screen fixed the problem...thanks a lot guy!
ok, so i unlocked and rooted my rezound, everything was working 100%, then i start flashing diferent roms and it was conecting to wifi with no problems, however when i flashed ( or tried to flash ) a new kernel ( dont remember which one ) wifi stoped working for me, it scans but doesnt pick up any network. i went back to stock kernel and nothing, re-locked device and installed verizon factory Ruu for the rezound and Wifi still doesnt work. Im going crazy here please help, maybe im flashing the kernel wrong but re-locking and restoring to factory Ruu should have fixed it
I was also having the same issue and tried reinstalling kernals and nandroids. I was loading the kernal through Amon Ra interface directly and no matter what I did I still had issues. Sooo, I revised my recovery process and found that dummy me can't read instruction correctly. The issue was resolved after I did a factory reset on the rom (Ineffablis v1.0) then I followed the instructions for installing the kernal (I'm using the SmartassV2 kernal from dsb9938; flash from SD, then flashmethis file and finally through HBOOT, it's a process ok?), rebooted and I was able to get WiFi working again. I've had this issue whenever one of the additions I was trying did strange things to my phone and have sucessfully restored WiFi (about 10 times for this occurance). I've also had to do a hard reset (pulled the battery) and follow the process to get back to functioning. Hope this helps.
i locked the phone again, and ran the rezound stock Ruu and did factory reset, still not picking up any networks. the wifi doesnt give and error it scans and everything, but for some reason it just doesnt pickup any networks
If you read the complete directions when flashing a rom... They state you will need to flash the wifi module after a fresh install. So just flash the kernel over again and you will have wifi working.
Thanks a lot, finally got it working
Sent from my HTC REZOUND using xda premium
I'm having the same problem where my rezound won't find any networks. My bluetooth won't turn on either. How were you able to fix it?
thanks,
ron
Edit
Mods, I'd have liked to have posted this as a reply to Andybones' thread, but I'm under 10 posts, so please move as needed.
So, I got my Rezound from eBay and figured I'd root it and update it.
Went through the HTC Unlock Bootloader process.
Setup Perm Root
Installed Amon Ra Recovery 3.1.3
Allowed OTA to take place to get to 2.01.605.11.
Went into Amon Ra and had it install superuser and su.
Figured it was an eBay phone and should be wiped clean, so from bootloader did a Factory Reset
After it rebooted a few times, phone came up and "Wifi Error". Everything else working perfectly- 3g, 4g, voice, bluetooth... just no WiFi. Unable to stop or start it in settings GUI.
Hunted online for "WiFi Error" and Rezound and found a few posts asking about clearing cache and dalvik; another few were referencing Kernel and/or module installs.
Cleared cache and dalvik to no avail.
Searched for 2.01.605.11 Kernel and found Andybones post. Installed the Kernel and Wifi was working with everything else again.
So the question-- now that it is fixed and working-- what the heck happened to have broken my WiFi for that duration? Was it when I did the Factory Reset that I somehow screwed up my Wifi Kernel Module? If so, how? Did Factory Reset install some older module or Kernel? Or, was there something broken in my OTA? I saw mention of one other person whose WiFi was broken after OTA to 2.01.605.11-- he also resolved by using the Andybones post to install the Kernel.
Unfortunately, after seeing that the WiFi wasn't working, I didn't think to check what Settings showed for my Kernel, or to try checking mass storage for file dates or versions-- I know those could probably have helped in ascertaining what occurred.
Anybody else experience WiFi broken after OTA?
Thanks in advance!
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
feralicious said:
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
Click to expand...
Click to collapse
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
andybones said:
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
Click to expand...
Click to collapse
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
feralicious said:
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
i had this problem a few times...the last two times i think it was because i had wifi tether on then stupidly i turned on verizon tether app and so wifi and verizon mobile hotspot/wifi tether stopped working and kept giving an error message...i had to flash a version of incredikernel i had laying on my card and everything worked fine..kind of wierd but whatever lol and once i believed it just happened out of nowhere so i just reflashed everything..that time wiping and flashing the rom all over again worked but all other times i needed to flash a kernel. i believe i was running clean rom all those times and once happened on ICS i think..running the latest clean rom 1.6.5 and havent had those issues yet( knock on wood)
feralicious said:
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
Click to expand...
Click to collapse
That's what I'd have thought, too. I am/was completely stock and my update was OTA. Didn't touch any 3rd party kernels or ROMs. I want to make sure phone works as intended before considering messing with other ROMs/Kernels.
EDIT: Found this older thread which is very similar -- mods can probably close mine or migrate the posts over to the older one since my query resembles what SquireSCA experienced.
feralicious said:
Are you willing to factory reset again?
Click to expand...
Click to collapse
Yeah, tempted to give it a shot after doing an Amon Ra backup to see if it was the factory reset that did me in. I can head back to the Andybones kernel thread to recover again if needed. Probably not going to test it right away though. Still settling in with the phone.
One variable that I didn't consider-- when I did my OTA-- I did not re-lock the bootloader prior. Any possibility of correlation?
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
I have a nand of my phone from right after I did my OTA without relocking. When I get around to doing my fresh installs I will restore that and check it to see if I have the same issue. I'll probably do it when I get back home later tonight. I'll post back afterwards to let you know.
So I just restored my nand from when I went back to stock recovery, ROM and kernel (all 1.x) and then accepted OTA. wifi was broken until I flashed the new 2.x stock kernel. That was from when I got the OTA without relocking the phone. I meant to check what the kernel said before I flashed the 2.x stock one but forgot. Argh... now I want to go back to Ineff and do this again to check it.
EDIT: Well, I went back to my stock OTA nand again and the kernel shows as dsb. So I can't replicate what I did earlier since I had flashed the stock kernel before getting the OTA and I guess the nand doesn't back up/restore the kernel.
I don't know what condition wifi was in when I made the nand since I didn't know to check and I just made that as a safety copy and went back to Ineffabilis right away.
I did flash the stock 2.x kernel to get wifi working on stock OTA, then restored my Ineffabilis nand and again, the only way to get my wifi back was to flash the dsb kernel. The stock rooted kernel that came with Ineffabilis didn't do it. Gonna go post on the dsb forum and see what they say. Also, tomorrow I'm going to run the RUU and factory reset and try to get this thing totally clean and see if I can use a different kernel than dsb. Ineff was just updated to 2.x so perhaps flashing the new ROM will break the chains.
feralicious said:
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
Click to expand...
Click to collapse
Soooo... I was reading some of the ICS threads and getting really curious about installing. Saw a post by someone mentioning they're on baseband 0.95.00.1118r. Went to check mine, and I'm on 0.95.00.1017_2r . Checked the Verizon site and OTA 2.01.605.11 provides 0.95.00.1118r . Did some more digging to figure out how I got left behind using the official OTA and came upon this post:
Baseband does not update without a re-lock first.
EDIT: found plan of attack via http://forum.xda-developers.com/showthread.php?t=1467329 and will give it a shot this evening.
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
EmerikL said:
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
Click to expand...
Click to collapse
Thanks!
Off-topic: Any alternatives to using Filefactory or Dev-host to download the RUU? Has anyone done a sniff during the OTAs to see what URL is used to download the RUU? Does VZW restrict what IPs/MACs can download the updates? Or do they use a proprietary protocol? Or are the updates strictly via their CDMA/LTE, without WiFi?
Mission accomplished-- I now have radio 0.95.00.1118r on my 2.01.605.11.
I did follow the http://forum.xda-developers.com/showthread.php?t=1467329 directions, and I'm posting the commands used for future ref in case needed again:
1) downloaded vigorOTAStockRooted.zip after midnight pacific time (download didn't die) and then copied it to the sdcard.
2) {boot into Amon Ra} adb reboot recovery
a. backup everything
b. install vigorOTAStockRooted.zip
3) {install drops the ph98img.zip file on external sdcard-- but it won't install with unlocked bootloader. need to lock the bootloader} fastboot oem lock
4) {installation finished up, let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
5) {go into bootloader} adb reboot bootloader
6) {get token to submit to htcdev.com; once displayed, plop in the token, and wait for email} fastboot oem get_identifier_token
7) {once email with token received, flash it} fastboot flash unlocktoken Unlock_code.bin
8) {let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
9) {reboot into bootloader to install Amon Ra Recovery} adb reboot bootloader
10) {install Amon Ra} fastboot flash recovery recovery-ra-vigor-3.14-gnm.img
11) {enter recovery - from HTC bootloader, go to recovery} select menu item to go to recovery
12) {restore} from Amon Ra recovery, restore the backup from step 2a and then reboot
Sup,
So, I flashed mutliple custom ROM's when I got this device like any other crack-flasher would but I then realised I much prefer it to be running stock with root access until an AOSP ROM comes along.
So I came from Omega 4.0 to stock LE8 in the UK, ever since I've flashed this stock ROM (Which is odexed) I keep getting the message "Sorry, messaging has unfortunately stopped" every time I open the app. I've tried wiping data/cache/dalvik and flashing in Odin again, same issues. I then went back to another custom ROM (HyperGalaxy) then went back to stock to test, still the same.
I have also tested an inverted AOSP 4.0.4 Mms app which worked on Omega, but didn't work on stock (Got the same message)
Data of the Messaging app has been wiped, i've disabled the app, rebooted, enabled again, still the same issues.
I've searched and I found 2 other threads with the same thing, but noone has been helpful enough yet.
It seems like the phone still thinks its running a Deodexed ROM but I need to get it back to full working order since I need to text something.
Any help is appreciated.
Try a factory reset...
Mopral said:
Try a factory reset...
Click to expand...
Click to collapse
Probably didn't make it clear enough, I did that already. 3 times to be exact.
i have the same issue. Need help.
i get this message with multiple apps.
all of them are standard run of the mill things like browser, messages, video player. My phone is only a week old and completely stock
some real bugs in this phone still that need sorting asap. poor effort by samsung really
Same issue here, has anyone found a fix for it yet?
I only encounter this in hyper x rom. So far so good in omega
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
nbhadusia said:
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
Click to expand...
Click to collapse
i got this everytime i clear cache and or wipe data from recovery before flashing new fw's.
so never wipe anything before flashing. if u already wiped, then flash it all over again and it will be all ok