Related
I flashed to the newest SyndicateFrozen and it worked great until I started using the Browser. It locked up and I had to pull the battery. Same results with Dolphin Mini, DolphinHD, and the new Firefox. Anybody know if I missed something on the Syndicate page? Right now I'm going back to the Samsung distributed EB13 until I can find more information about this.
atomiksnowman said:
I flashed to the newest SyndicateFrozen and it worked great until I started using the Browser. It locked up and I had to pull the battery. Same results with Dolphin Mini, DolphinHD, and the new Firefox. Anybody know if I missed something on the Syndicate page? Right now I'm going back to the Samsung distributed EB13 until I can find more information about this.
Click to expand...
Click to collapse
That happend to me like 3 times... but not on dolphin browser HD.
Sent from my SPH-D700 using XDA App
atomiksnowman said:
I flashed to the newest SyndicateFrozen and it worked great until I started using the Browser. It locked up and I had to pull the battery. Same results with Dolphin Mini, DolphinHD, and the new Firefox. Anybody know if I missed something on the Syndicate page? Right now I'm going back to the Samsung distributed EB13 until I can find more information about this.
Click to expand...
Click to collapse
Have you tried clearing your cache, sometimes doing this helps. If not redoing the odin to EC05 has worked for me with other issues like force close.
deano0714 said:
That happend to me like 3 times... but not on dolphin browser HD.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I ended up using Samsung's EB13 update to get back to stock Froyo. Then installed CWM 2.5 with oneclick and restored my backup from after I had installed Syndicate Frozen (it's been a very slow day at work, I have time to mess around) and it seems to work with all browsers now. Essentially the only difference is I kept it from upgrading to EXT4.
I ran some benchmarks, which were quite underwhelming (seeing as when I was running DK28 they were well over this)
Quadrant: 1032
Linpack: 13.92
Smartbench 2010: 1093/2462 (also well under the 1ghz for stock Epic 4g 2.2)
If you get freezes regularly in anything at all, read the message that has been posted many times about using an alternate kernel. You can also try VisionKernel in lieu of the one linked clearly throughout the thread and in the second post under Changelog.
I should have included in the original post that I did a lot of searching throughout the thread and tried loading the Twilight_Zone kernel as recommended. After that my phone wouldn't load. I tried reloading the original modem with ODIN and nothing. I tried restoring to various backup points and just decided a fresh start was fine with me.
I hadn't seen anything about Visor Kernal. I'll give that a shot another day, but for today I'm wiped out on monkeying with this thing. I'm just glad I have a stable phone at the end of the day.
I should also note what I've done since.
I used Samsung's tool to get back to stock Froyo. Then used one click root to get CWM 2.5 back on there and restored the backup that I had made AFTER installing the Syndicate Frozen ROM. That was on accident, I had a lot of backups on there and wasn't sure which one was which. It loaded up perfectly fine. So I'm running Syndicate Frozen, but without CWM3 (and I suppose without EXT4 filesystem). And it works fine right now.
atomiksnowman said:
I should also note what I've done since.
I used Samsung's tool to get back to stock Froyo. Then used one click root to get CWM 2.5 back on there and restored the backup that I had made AFTER installing the Syndicate Frozen ROM. That was on accident, I had a lot of backups on there and wasn't sure which one was which. It loaded up perfectly fine. So I'm running Syndicate Frozen, but without CWM3 (and I suppose without EXT4 filesystem). And it works fine right now.
Click to expand...
Click to collapse
That's not a recommended configuration in the slightest.
I had the same problems even with the other kernel. I finally went to Bonsai 4.0 with EC05 and I have not had my phone freeze.
Its nice.
for me it happened in dolphin hd hasnt yet in stock browser
atomiksnowman said:
I should also note what I've done since.
I used Samsung's tool to get back to stock Froyo. Then used one click root to get CWM 2.5 back on there and restored the backup that I had made AFTER installing the Syndicate Frozen ROM. That was on accident, I had a lot of backups on there and wasn't sure which one was which. It loaded up perfectly fine. So I'm running Syndicate Frozen, but without CWM3 (and I suppose without EXT4 filesystem). And it works fine right now.
Click to expand...
Click to collapse
So.. A eb13 modem and a ext4 backup running on stock file system...
I predict big problems on the horizon
tmspyder said:
So.. A eb13 modem and a ext4 backup running on stock file system...
I predict big problems on the horizon
Click to expand...
Click to collapse
Everything worked perfectly until I tried to pair Bluetooth. Then she froze. I couldn't get it to fail any other way than with bluetooth. Fun experiment, though. I though I had a backup from before using CWM to convert to EXT4, but that isn't the case. I'm now running EB13 on CWM3 (which converted to EXT4, but no problems in the 12 hours I've given it).
My main reason for starting this Q&A post was to point out that I had tried the ROM and its recommend fixes that I could find in what I consider a reasonable amount of time/searching so that the developer might catch it and look into it if he/she so desired.
I want to note that I don't feel entitled to anyone's hard work other than my own. I'm perfectly happy following all instructions and finding that for me it didn't work. I might get a little miffed if I brick the phone but Samsung has made a product that remains quite resilient after all the modding real developers do, and the torture we tinkerers do. So to k0nane especially, thanks for the hard work. I'll keep reading through the forum and maybe try what Badbeats suggested with Bonsai 4.0 some time next week when I'm not so busy at work.
Seriously, you developers are amazing.
I had flashed SRF 1.1.0 and was running it with no issues. I tried the Vision kernel and got random lockups mostly after being plugged in and unused for awhile (maybe an hour or so). I flashed back to the Twighlight Kernel and it's been solid as a rock.
Being that I've only owned the phone a few weeks and have flashed/restored it at least a dozen times, I feel confident that it's running stable at this point. Once you mess it up a few times, you'll learn pretty quickly
I loaded the syndacite rom about 2 weeks ago and i love it. Yesterday i started gettign this error. "twlauncher has stopped unexpectedly". I try to force close it over and over again and even a reboot doesn't work. I reboot twice and it appears a few times then i'm able to use my phone again. Anyone know what the problem is? I used the syndacite fully loaded rom.
Clear data for the launcher in Settings > Applications.
k0nane said:
Clear data for the launcher in Settings > Applications.
Click to expand...
Click to collapse
I went there but i don't see a clear data option. Can you explain a little bit further to me? thanks!
howufiga said:
I went there but i don't see a clear data option. Can you explain a little bit further to me? thanks!
Click to expand...
Click to collapse
Settings > Applications > Manage Applications > TWLauncher (or TouchWiz Launcher, or com.samsung.twlauncher) > Clear Data
k0nane said:
Settings > Applications > Manage Applications > TWLauncher (or TouchWiz Launcher, or com.samsung.twlauncher) > Clear Data
Click to expand...
Click to collapse
I can't even get to settings. I can only pull down the the menu with the WIFI and GPS settings. any tips on how to get into settings? I keep on getting twlauncher has stopped over and over again.
If you can't open settings, try going into CWM > Advanced, and fixing permissions. Can also clear caches, and if that doesn’t work, reflash the ROM.
Actually, just curious. What happens when you try to go into settings? Does the menu come up to enter settings, does it FC when you open?
i couldn't open applications. Everytime I tried in between hitting force close it would just flash then come back and reload over and over again. I had the bright idea of pulling the battery and then it wouldn't boot at all. Had to reflash the ROM. Now need to reinstall all my apps. lol
howufiga said:
i couldn't open applications. Everytime I tried in between hitting force close it would just flash then come back and reload over and over again. I had the bright idea of pulling the battery and then it wouldn't boot at all. Had to reflash the ROM. Now need to reinstall all my apps. lol
Click to expand...
Click to collapse
If this happens in the future, hold down the search key and say something to search for, this should take you to the browser. Search for and download launcherpro, zeam, or another launcher you don't already have. After it installs, hit home and choose the new launcher, then you can clear data for touchwiz. This happened to me when I had one homescreen on touchwiz and it was full, and an app tried to automatically add a shortcut.
Sent from my always stock, EC05 Epic 4G
howufiga said:
i couldn't open applications. Everytime I tried in between hitting force close it would just flash then come back and reload over and over again. I had the bright idea of pulling the battery and then it wouldn't boot at all. Had to reflash the ROM. Now need to reinstall all my apps. lol
Click to expand...
Click to collapse
It sounds like a bad reflash though. I've had that, where it FCs so repeatedly that I can't do anything at all. When you have it all set the way you want, make a CWM Nandroid backup, and then restore that backup to turn journaling back on... then battery pulls won't affect you.
You made my day!
zanderman112 said:
If this happens in the future, hold down the search key and say something to search for, this should take you to the browser. Search for and download launcherpro, zeam, or another launcher you don't already have. After it installs, hit home and choose the new launcher, then you can clear data for touchwiz. This happened to me when I had one homescreen on touchwiz and it was full, and an app tried to automatically add a shortcut.
Click to expand...
Click to collapse
What a simple and elegant solution! This error showed up for me last night, and then completely ruined my morning. After searching countless forums and finding nothing but overly technical instructions containing so much jargon I had to search forums to figure out what the instructions meant....I nearly threw my phone up against the wall. Just before I was about to restore to factory settings, I found this thread and these instructions worked PERFECTLY!!! I am not a gadget guy and had a Sanyo Katana that was held together with tape until a month ago, so this solution was right up my alley! I actually registered on this site simply to say thanks. Hopefully the Thanks button will show up after I make this post so I can hit it until my finger blisters.
Props here as well
k0nane said:
Settings > Applications > Manage Applications > TWLauncher (or TouchWiz Launcher, or com.samsung.twlauncher) > Clear Data
Click to expand...
Click to collapse
Thanks to k0nane as well. Once I got LauncherPro to download with zanderman's intructions this helped me clear and reload touchwiz.
LdoFoSho said:
What a simple and elegant solution! This error showed up for me last night, and then completely ruined my morning. After searching countless forums and finding nothing but overly technical instructions containing so much jargon I had to search forums to figure out what the instructions meant....I nearly threw my phone up against the wall. Just before I was about to restore to factory settings, I found this thread and these instructions worked PERFECTLY!!! I am not a gadget guy and had a Sanyo Katana that was held together with tape until a month ago, so this solution was right up my alley! I actually registered on this site simply to say thanks. Hopefully the Thanks button will show up after I make this post so I can hit it until my finger blisters.
Click to expand...
Click to collapse
No problem! I forgot about this.
Please click both links below and vote: http://picketfenceblogs.com/vote/3616
http://apps.facebook.com/gerberphotosearch/entry/935/amber.aspx
Oh God bless you, zanderman112. I thought I was going to have to reset my mom's new phone after I finally finished setting it up and she just started getting used to it.
Red Jenny said:
Oh God bless you, zanderman112. I thought I was going to have to reset my mom's new phone after I finally finished setting it up and she just started getting used to it.
Click to expand...
Click to collapse
Thank you. Now, you can also try market.android.com to wirelessly install apps.
Sent from my Samsung Legendary 4G, a Universe UTES Phone, running "two. two"
Sorry to drag up an old thread, but I can't find any help on this thru searches, so here goes:
Does SynFro 1.1.0 clash with CWM5?
My Epic been on Bonsai 4.0.1 (CWM 3.0.0.6, ext4, golauncherex) for a long time. I used Rom manager to update CWM to 5, and to flash the ROM Syndicate Fro_fully loaded 1.1.0 . Seemed to run fine at 1st (hr or so) then while DL'ing a goLauncherex from market, the system froze. after battery pull and reboot, I had constant FC's. Booting into recovery from Rom manager lead to a generic Android recovery system (instead of CWM).
Powered off, 3 fingered into CWM, which suddenly had reverted to v3.0.0.6 . Tried to restore Bonsai, but only got error msgs ("syste.img not found. skipping restore of /system" same with data, android_secure, cache, sd-ext, etc. )
Had to triple wipe (data,cache, dalvik), reflash my bonsai rom and re-update CWM to 5 to get back to a normal functioning phone.
If the issue here seems to be conflicts between older roms clashing with newer CWM versions, is there a way to check which ROMs require which CWM?
thanks for your time.
Epiclectic said:
Sorry to drag up an old thread, but I can't find any help on this thru searches, so here goes:
Does SynFro 1.1.0 clash with CWM5?
My Epic been on Bonsai 4.0.1 (CWM 3.0.0.6, ext4, golauncherex) for a long time. I used Rom manager to update CWM to 5, and to flash the ROM Syndicate Fro_fully loaded 1.1.0 . Seemed to run fine at 1st (hr or so) then while DL'ing a goLauncherex from market, the system froze. after battery pull and reboot, I had constant FC's. Booting into recovery from Rom manager lead to a generic Android recovery system (instead of CWM).
Powered off, 3 fingered into CWM, which suddenly had reverted to v3.0.0.6 . Tried to restore Bonsai, but only got error msgs ("syste.img not found. skipping restore of /system" same with data, android_secure, cache, sd-ext, etc. )
Had to triple wipe (data,cache, dalvik), reflash my bonsai rom and re-update CWM to 5 to get back to a normal functioning phone.
If the issue here seems to be conflicts between older roms clashing with newer CWM versions, is there a way to check which ROMs require which CWM?
thanks for your time.
Click to expand...
Click to collapse
Gonna try to help.
Both SFR and bonsai are oollldddd roms. SFR froze up because it isn't journaled. I highly recommend using ODIN to get to stock EC05, then update to EL30. Then use qbking77s "How to root Samsung epic 4g gingerbread" video to get CWM and root.
CWM 5 can flash any Rom, but those roms in particular are so old and buggy.
Sent from something with a Ｋモ尺れモㄥ.
Epiclectic said:
Sorry to drag up an old thread, but I can't find any help on this thru searches, so here goes:
Does SynFro 1.1.0 clash with CWM5?
My Epic been on Bonsai 4.0.1 (CWM 3.0.0.6, ext4, golauncherex) for a long time. I used Rom manager to update CWM to 5, and to flash the ROM Syndicate Fro_fully loaded 1.1.0 . Seemed to run fine at 1st (hr or so) then while DL'ing a goLauncherex from market, the system froze. after battery pull and reboot, I had constant FC's. Booting into recovery from Rom manager lead to a generic Android recovery system (instead of CWM).
Powered off, 3 fingered into CWM, which suddenly had reverted to v3.0.0.6 . Tried to restore Bonsai, but only got error msgs ("syste.img not found. skipping restore of /system" same with data, android_secure, cache, sd-ext, etc. )
Had to triple wipe (data,cache, dalvik), reflash my bonsai rom and re-update CWM to 5 to get back to a normal functioning phone.
If the issue here seems to be conflicts between older roms clashing with newer CWM versions, is there a way to check which ROMs require which CWM?
thanks for your time.
Click to expand...
Click to collapse
I've got you man.
What you need to do is direct your attention to this thread right here by DRockstar: RECOVERY] ClockworkMod 5.0.2.7 BML Officially supported by ROM Manager
What you had done wrong was you installed through Rom Manager, which is a temporary flash ontop of CWM 3, it in itsellf is not CWM 5 installed. Within that thread you've a choice of an update zip of CWM 5 or a Odin tar, CWM zip is preferrable. But otherwise you should be fine. The zip from within that thread is more final.
AproSamurai said:
I've got you man.
What you had done wrong was you installed through Rom Manager, which is a temporary flash ontop of CWM 3, it in itsellf is not CWM 5 installed. Within that thread you've a choice of an update zip of CWM 5 or a Odin tar, CWM zip is preferrable. But otherwise you should be fine. The zip from within that thread is more final.
Click to expand...
Click to collapse
Ok, I got the real CWM5 zip, flashed, now all roads lead to CWM5, so that part is fine. And I stopped trying those olds ROMs , tried to flash SynIce.
My Epic runs Bonsai4.0.1, I did the triple wipe and then flashed the rom (from CWM5) but I get the following:
SYN Ice Logo
"Take a shower, pick an outfit, put on some smell good, call my crew.."
then the yellow bar freezes about 15% into its progress. it eventually kicks back out to CWM. no msgs or errors to share. I dont have access to Odin (or a PC) and Heimdall wont recognize my epic....any1 having similar probs? is it my kernel? I see suggestions sometimes to use Odin to switch from "EC05" to "EL30"...i thought flashing the ROMs changed your base ROM (DK28, EL13, etc) to the one it needed....is that not the case?
Epiclectic said:
Ok, I got the real CWM5 zip, flashed, now all roads lead to CWM5, so that part is fine. And I stopped trying those olds ROMs , tried to flash SynIce.
My Epic runs Bonsai4.0.1, I did the triple wipe and then flashed the rom (from CWM5) but I get the following:
SYN Ice Logo
"Take a shower, pick an outfit, put on some smell good, call my crew.."
then the yellow bar freezes about 15% into its progress. it eventually kicks back out to CWM. no msgs or errors to share. I dont have access to Odin (or a PC) and Heimdall wont recognize my epic....any1 having similar probs? is it my kernel? I see suggestions sometimes to use Odin to switch from "EC05" to "EL30"...i thought flashing the ROMs changed your base ROM (DK28, EL13, etc) to the one it needed....is that not the case?
Click to expand...
Click to collapse
Never heard of synice... I would really suggest odining to ec05 just to clean up the phone and then root and flash... just cleaner that way... btw where did you find that rom...
Sent from my SPH-D700 using Tapatalk
flastnoles11 said:
Never heard of synice... I would really suggest odining to ec05 just to clean up the phone and then root and flash... just cleaner that way... btw where did you find that rom...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Dude really SynIce is SRF lol wow how did that not click.
So I I've had 2 different recoveries so far that have worked fine.. both came from Rogue though. One was from the 1.5 kernel (Hitman) which installed CWM Touch recovery, the other came with the normal recoveries based off CW 5.0.2.7. They were working fine until I installed Calkulin's Rom(2.8.1). Not sure if they're just incompatible or what, but when I go to recovery it shows the background image of the recovery but none of the options show up. It shows for about half a second and then it goes back to the original boot screen, then to the 2nd screen and turns on. So it basically skips right through the recovery and reboots. Do I need a new Rom or can I fix this? I really like the battery life and visuals of Calkulin's Rom and would love to be able to keep it.
EDIT: One more thing.. Since I installed the ROM, I've been getting market error 492. It doesn't allow me to install anything in the market..
I haven't tried a full wipe yet, so I guess I'll try that and then see how that works with the recovery and Rom..
I did the same thing to my phone this week, and I'm running Blazer, so i'm sure it has nothing to do with either ROM.
Not sure how I caused it but with so many folks running both without this error, I'm guessing that your issue (like mine was) was probably some how self induced.
I flashed back to stock and started over, and things have been working great. Might be worth a shot flashing back, or restore a backup and start fresh.
Haven't seen the market error before. I'm sure someone here has
Good Luck
If you got it off here, could you show me which stock you flashed..?
Everything you need is in the Epic 4G Touch Android Development section
Here is the post I used from Sfhub
http://forum.xda-developers.com/showthread.php?t=1433101
Watch the videos by Qbking77 They walk you thru everything step by step. (I hear his video intro rif every time I close my eyes now so you've been warned) Makes it super easy.
I would read everything you can and watch the videos before you get in too deep. I've had this phone since December, and just flashed my 1st ROM this week cause I've been reading up, and learning all I could before I jumped in the pool.
Well I've done all this with 2 phones before but I've never had this happen.. normally I just get the Rom and I'm good to go..
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
premo1 said:
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
Click to expand...
Click to collapse
Try booting while holding the volume up and power button.
If that does not work, flash recovery from rom manager, and that should get you into recovery to flash whatever kernel/recovery u want.
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
premo1 said:
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
Click to expand...
Click to collapse
Good Luck.
Recovery and market are now working Thank you Adanorm!
Glad your back up and running
My browser constantly crashes and I can't for the life of me figure out why, so I am turning to you guys for help with my first post. Here's what's up:
Within one minute of opening my browser, but often within a few seconds of browsing, the browser will crash. No dialog or anything, it just suddenly closes. Sometimes it will restore itself when I reopen it, sometimes not.
This has happened across multiple roms, including cm10(which I am on now) AOKP, Frostyjb etc. I've used all the wiping options in CWR including formating /sdcard but nothing has helped. I can't find anybody with a similar problem. Any ideas?
You didn't tell us which browser. Use a different one.
kaixo24 said:
My browser constantly crashes and I can't for the life of me figure out why, so I am turning to you guys for help with my first post. Here's what's up:
Within one minute of opening my browser, but often within a few seconds of browsing, the browser will crash. No dialog or anything, it just suddenly closes. Sometimes it will restore itself when I reopen it, sometimes not.
This has happened across multiple roms, including cm10(which I am on now) AOKP, Frostyjb etc. I've used all the wiping options in CWR including formating /sdcard but nothing has helped. I can't find anybody with a similar problem. Any ideas?
Click to expand...
Click to collapse
Goto: settings / apps / browser /
Clear the cache and data and if it says: un-install update try that too
boot in to recovery and wipe davik and cache and fix permissions
Worth a shot :/
WarlockW said:
Goto: settings / apps / browser /
Clear the cache and data and if it says: un-install update try that too
boot in to recovery and wipe davik and cache and fix permissions
Worth a shot :/
Click to expand...
Click to collapse
Tried all that before and tried it again just now. Seems to be a bit better for a minutes (no crashes) but within 5 minutes it starts crashing upon loading my homepage etc. It's strange because crashes of this nature never happened to me even when running highly experimental ROMs on my old Atrix 4g. Is it possible that there are some configuration files (say host files or something) that are not wiped by the factory reset in CWM and are tripping things up? I think I will try flashing a stock image using Odin (which should wipe everything on the phone, correct?) and see if that fixes things.
And I am talking about the stock browser. It's the best (usually) for me and I'm sure it shouldn't be acting like this. Chrome and firefox crash even on stable stock builds so I can't really tell from them, lol.
Flashing stock with odin would be my next suggestion.
But also, after your next flash, don't install anything. Go straight to the browser after boot and see how it acts.
Can you verify it happens on any network? 3G/4G or any wifi?
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Flashing stock with odin would be my next suggestion.
But also, after your next flash, don't install anything. Go straight to the browser after boot and see how it acts.
Can you verify it happens on any network? 3G/4G or any wifi?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help and sorry to bring this topic back up, but my phone is really driving me crazy. For the past week I have experimented with Odin flashing the stock firmware on to my phone (both ICS and the recent JB) as well as constant factory resetting, but nothing changes the behavior. Using an alternative browser like Firefox (it sure has improved) results in a more stable experience, but things that use the default browser like gmail and (I think) Facebook still crash all the time. Also, the unlock screen often is unresponsive upon waking the phone, which is shortly followed by a reboot.
This behavior happens even if I do a factory reset, flash the stock firmware and boot up straight to the browser without signing in to my Google account or doing anything else. It happens irrespective of the network I am using.
I know we aren't supposed to use the repartition feature in Odin, but is there a safe way to do it or otherwise wipe everything off the internal memory leaving only the download mode so I can really start from a clean slate? I really want to rule out any software problem. The thing is, I'm getting a Nexus 4 and want to sell my sIII (it's still in mint condition) but I can't ethically do it knowing that my phone is somewhat borked. please help!!
I bought my phone new in box off of Ebay because I wanted the blue color. What a mistake. Samsung and T-Mobile are rebuffing any warranty requests I make (I didn't trip the flash counter) because I don't have a receipt. It would seem strange that this is a hardware problem as everything else works fine, but could I be wrong?. Only the default browser and apps that use it exhibit this behavior. Anybody have any ideas on what is going on??
kaixo24 said:
Thanks for your help and sorry to bring this topic back up, but my phone is really driving me crazy. For the past week I have experimented with Odin flashing the stock firmware on to my phone (both ICS and the recent JB) as well as constant factory resetting, but nothing changes the behavior. Using an alternative browser like Firefox (it sure has improved) results in a more stable experience, but things that use the default browser like gmail and (I think) Facebook still crash all the time. Also, the unlock screen often is unresponsive upon waking the phone, which is shortly followed by a reboot.
This behavior happens even if I do a factory reset, flash the stock firmware and boot up straight to the browser without signing in to my Google account or doing anything else. It happens irrespective of the network I am using.
I know we aren't supposed to use the repartition feature in Odin, but is there a safe way to do it or otherwise wipe everything off the internal memory leaving only the download mode so I can really start from a clean slate? I really want to rule out any software problem. The thing is, I'm getting a Nexus 4 and want to sell my sIII (it's still in mint condition) but I can't ethically do it knowing that my phone is somewhat borked. please help!!
Click to expand...
Click to collapse
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
eternalcold said:
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
Click to expand...
Click to collapse
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
BWolf56 said:
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
Click to expand...
Click to collapse
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
eternalcold said:
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
Click to expand...
Click to collapse
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
BWolf56 said:
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
Click to expand...
Click to collapse
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
eternalcold said:
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
Click to expand...
Click to collapse
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
BWolf56 said:
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
Click to expand...
Click to collapse
Alright, i'll flash that one, i'll post to here when it's finished. Thanks!
Did you check your IMEI?
xBeerdroiDx said:
Did you check your IMEI?
Click to expand...
Click to collapse
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
eternalcold said:
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
Click to expand...
Click to collapse
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
BWolf56 said:
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
Click to expand...
Click to collapse
Understood, I wont mess with them.
I really just want to understand a couple things.
1. Why did the ROM I installed before work for everyone else except me? and i followed the instructions.
and 2. after flashing to stock, how am I unable to fix this?
mainly to just learn what went wrong.
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
hednik said:
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
Click to expand...
Click to collapse
Thanks,
Is there any way to repair it?
Alright, so....
I think i have figured out what the issue was. Or by random chance got it fixed.
I was going to try to install the Synergy Rom. And while going through the custom setup, i noticed "Install AOSP Messaging" and "Install TW Messaging"
I chose the TW messaging, and went through the rest of the installer.
For some reason i kept hanging at the "Samsung Galaxy S3" logo, and it would not boot.
(Honestly, i've used custom roms since the HTC Touch Pro 2, and i've NEVER had such issues. And i personally think the TP2 was way more difficult lol)
So I ONCE AGAIN flashed to stock. and randomly the messaging works!
I only can guess that even when flashing the stock rom, it doesnt change something regarding the messaging app. I'm not sure. All i know is that i'm on stock again and everything is working. I highly doubt i'm going to try another custom rom for a while until i have a full understanding of what happened.
But in case anyone else was having this problem, i hope this helped.