Related
Hey everyone,
So this is my last ditch effort to attempt to save my device. I would really prefer not to perform another warranty exchange given that I am not under insurance, but I'm afraid I have no choice.
My phone was rooted and I was using Darkside without issues, as I had been for the past two weeks. I am always careful when I flash roms and I made sure to follow every possible protocol. That's the background information.
My battery life was running at approximately 6 percent yesterday and I sent a text message as normal, and it was stuck at sending. I tried turning wireless data off from the toggles in the pull-down and it was unresponsive. When I went to Wireless Network in the settings option, my phone rebooted. Once it started up again, my service would not come back, and the phone would continually bootloop once it got past the traditional "media scanner running", etc. My window of opportunity to do anything was really slim.
I charged my phone to see if it made a difference, but it didn't. Tried with my SIM card removed and it still bootlooped. I was able to get to CWM from the advanced power menu before it rebooted again and I fixed permissions and cleared cache and dalvik. Now the phone wouldn't even get past the boot animation before rebooting.
I put the phone into download mode and reverted back to stock using Odin. The phone now got past the boot animation in stock mode, but was unable to find service and after about 10 seconds fell into the same bootloop pattern. I tried removing the SD card but that didn't help either. Using Odin again, I reflashed recovery, followed by root and tried reinstalling a rom through CWM (I have only used regular CWM, not the touch version) with a superwipe to ensure a clean flash. Once again, it wouldn't make it past the boot animation before bootlooping. I reverted back to stock using Odin, and this is where I stand.
I have tried all traditional methods to salvage the phone and, for the life of me, I cannot understand what happened. The only thing I notice is that regardless of how long the phone stays on before rebooting, it is never able to find service. It's like the radio or modem broke and the phone has no other choice but to restart forever. But reflashing the stock UVKL1 should also reflash the proper modem and radio, right?
Has this ever happened to anyone? Any suggestions (aside from the typical reverting to stock) as to how I might be able to stop it? I searched but haven't been able to find a situation quite like this one. Thanks in advance for your help.
Really sorry to hear about your problem. Assuming the 2.3.6 stock image you flashed via Odin is the one provided by Przekret and that that didn't work, then I'd try one or both of these two longshots to try to clear possible corruption problems in either the kernel or modem spaces:
For each of the following wipe cache and Dalvik cache in CWM before flashing and again wipe Dalvik afterwards and also fix permissions:
1) Format system (do this 3x) under mounts & storage in CWM. Flash the standalone Darkside kernel X v1 final immediately after flashing, e.g., the current Darkside rom. (You'll need to wipe data, too, if not coming from a Darkside rom. Do not do any Superwipe - neither the standalone version nor using a flag.)
2) Flash the KID modem (do this 3x). Both Odin- and CWM-flashable versions are available. (You can always flash back to KL1 if the problem is fixed.)
Hope this is clear. It's late! These are both things that have helped get my phone out of troubles, though not as bad as yours. Good luck!
Sent from my SGH-T989 using XDA App
Also if u used the one from przekret then I'm almost positive that Odin package flashes the new radio too. If memory serves me right. Op let us know what happened
Thanks for your help. Unfortunately, nothing has worked. I'm on the phone with T-Mobile, I see no other solution but to get it exchanged under warranty and it's not getting here until March 15th, according to the representative. I suppose I'll just use a replacement phone in the meantime. It's just really weird and frustrating... I could understand a bad flash or something similar, but I followed every step accurately as I always have and everything was working just fine until it randomly decided to die without warning.
Well since you're getting another one anyways I would continue trying to fix this one, just in case you come up with a solution and for another worst case scenario for your new phone.
Powered by the SGSII....
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
shehrammajid said:
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Forgive me for asking, but what is the EFS folder?
I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?
I don't think it's permanent maybe a bad zip? Did you check MD5 checksum before you flash? And did you full wipe?
Sorry, I don't think I made myself clear. I do have a damaged touch screen nothing to do with the rom. There is a section of the touch screen that just doesn't work. It is this part that sits exactly where the start button is. It is a shame these start screens don't rotate or the start button was slightly bigger.
So if I could skip this fisr language selection screen I would probably be ok for using the rest of the rom.
I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).
foxx1337 said:
I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).
Click to expand...
Click to collapse
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.
Skunkworx said:
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.
Click to expand...
Click to collapse
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."
bananagranola said:
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."
Click to expand...
Click to collapse
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?
Skunkworx said:
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?
Click to expand...
Click to collapse
Yes there is. You can use the "adb shell input keyevent <event_code>" command.
You'll probably want to send the DPAD_CENTER command to click that button. I think its event code is 23. Try typing "adb shell input keyevent 23".
Try the code for KEYCODE_ENTER as well.. its 66.
There is a whole list of keyevents at this link:
http://developer.android.com/reference/android/view/KeyEvent.html
Just lookup the "Constant Value" in the description of whatever KEYCODE_xxx you're trying to simulate and use that constant value as the event_code for the command.
I've tried simulating the DPAD_LEFT and DPAD_RIGHT keypress and they're working like a charm
---------- Post added at 04:34 PM ---------- Previous post was at 04:14 PM ----------
Yup. I've tried working with these Keycodes and they work fine.
Use event_codes 19 for UP, 20 for DOWN, 21 for LEFT, 22 for RIGHT to navigate to whatever button you need to press and then use 23 for pressing that button.
Should solve your problem.
Skunkworx said:
I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?
Click to expand...
Click to collapse
Hi, did you flash Gapps as well? I've moved from ARHD (which has the configuration start screen) to JellyTime and never got the language or any other configuration start screen (which I'm glad to get rid of). I always full wiped, clean flashed just the ROM, then booted into the OS for the first time to check it out. No Gapps and no language/configuration screen - it would always go straight to the lock screen where I would just swipe to the right and it would ask me to choose either the Nova or Trebuchet launcher. I'd then rebooted into recovery again and flashed Gapps. Hope this helps.
if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Skunkworx said:
if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
For moving SMS, I'd suggest this app : https://play.google.com/store/apps/...mNvbS5yaXRlc2hzYWh1LlNNU0JhY2t1cFJlc3RvcmUiXQ..
And as far as flashing the updates of JellyTime are concerned... It is recommended to always full wipe but you might get away with flashing the update over the previous version without a wipe. In some updates the author of the ROM explicitly says that full wipe is needed... in those cases you must. In other cases you can flash the ROM without the wipe which will keep your apps and data intact. However, it would still be better to wipe your cache and dalvik cache atleast.
Using Titanium Backup is not recommended at all when you're switching between different Android versions.. however I personally think it works ok when used between updates of the same ROM.
Skunkworx said:
Divche: Thanks, that did the trick perfectly.
Click to expand...
Click to collapse
I never encountered the config screen, so it was more of a guess based on what I did, so I'm glad it helped!
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom.
Click to expand...
Click to collapse
I also had all my contacts as phone contacts too. I chose to convert my contacts (and my calendar as well) to google for ease of syncing later on, so I have no tried and tested suggestions on how to maintain them as phone contacts. What I did was let HTC Sync synchronise with Outlook (I created a new PST file for this, then specified it in HTC Sync), then used GO Contact Sync Mod (sorry I can't post links yet) to sync it with my gmail account.
If you really wanted to leave as phone contacts, you could try Titanium Backup - but since your phone contacts are saved as system data it's a bad idea - so I'd recommend against it. If you're backing up your nandroid for ARHD, you could always try TiBu and let us know how it went - I think it was labeled Dialer Storage - filter to system data and just look through all the green-colored items for something that says "CONTACTS" or "PEOPLE".
However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
+1 to what if4!ct0r said regarding wiping before flashing.
There will always be some system settings that you will have to re-enter manually if you customize them a lot even when updating builds of the same ROM (probably because these are the system items that you shouldn't be restoring). These will depend on the ROM, but for me and JellyTime, the ones I had to redo were developer, lock screen, system/status bar, sound, display, language, as well as ringtone/sound notifications for alarms, messaging and calendar. Also you'll have to manually set up your widgets again - typically ones that require you to configure it as you place it.
As for TiBu not being recommended - personally I didn't have a problem with it when moving over to JellyTime. I actually purchased the Pro version just for this and for flashing new JellyTime builds. There are two things to consider when restoring via TiBu: 1) system data; and 2) app and app data.
System data: The main concern here is, when changing to a completely different ROM, do NOT restore any system data (unless you're aware whether it was updated in the new build or just experimenting). Even when you're updating to a new build of the same ROM, you should at least avoid restoring the red-coloured items and just stick to green and yellow items that may contain useful data such as contacts, sms, call logs, saved wifi access points, bookmarks, etc.
App and app data: I personally think it's ok to restore your apps themselves, but you could always record a list of what you had and download them manually again just to be safe - not a big deal unless you have over a hundred apps. When switching ROMs, try to avoid restoring the app's data unless you really wanted/needed it for certain apps - in that case, be conservative with what you choose. I'm not a programmer or developer, so I don't know how this would affect your system/app if switching to a ROM with a different Android version. Restoring app data between builds of the same ROM should be fine, as I've done it between all my JellyTime flashes with no issue even when it updated to Android 4.1.2.
Tip: after flashing the ROM, and doing your typical post-ROM-flash stuff (like fixing permissions, rebooting, wiping cache+dalvik, flashing Gapps, etc), and you've tested it and are happy with its stability, download TiBu again (or if you had the apk stored somewhere after you purchased it, just install it manually), boot to recovery and make a nandroid of the new ROM as it stands: nice and clean before any apps are installed. This way you've got a recovery option without having to go through the hassle of re-flashing the ROM build again, setting it up, etc if all you did was stuff up while experimenting with restoring data on TiBu.
As always, make a nandroid backup before flashing. As I mentioned, if you're initially happy with the ROM, I recommended also doing one after you flash while the system is fresh and clean. Sorry if this post is a bit wordy, but I thought more info would help, as it helped me in the past.
Skunkworx said:
So I am looking for a soloution ... to move my sms messages over.
Click to expand...
Click to collapse
if4ct0r said:
For moving SMS, I'd suggest this app...
Click to expand...
Click to collapse
+1 for SMS Backup & Restore; I also used it, but keep in mind AFAIK it doesn't save MMS. I also used Call Logs Backup & Restore, in case you're interested in backing this up too. But since I started using TiBu, I don't need either of these apps any more.
Maybe changing the digitizer could help asd
Sent from my Galaxy Nexus using xda app-developers app
So I'm having a problem I can't seem to fix.
I'm rooted, have been running the stock everything but with a few tweaks and some bloat removed. Everything works great but I am hoping to improve battery life. So I researched a few ROMs and pick a couple to try. I can flash them just fine with no problems, get all my apps back and set up with no problems. and I can use the phone all day just like normal.
Now the problem: if ever I have to restart for some reason, or even after I make a nandroid back up, when it restarts and boots up I eventually get several messages where processes are one by one stopping. until the phone is useless and froze up.
So it goes through 10 or more of these:
Unfortunately, the process android.process.media has stopped
Unfortunately, the process android.process.phone has stopped
etc, etc,etc
I have tried everything I could find on here to fix, but it seems all fixes are for a single process failing. This happens to me on all Roms I have tried, but I am just wanting to run Sonic. Even if I restore the nandroid I get the messages. If I factory reset or restore my kid-of-stock backup I am fine. If I start over and reflash a clean Rom I can set up and use but as soon as I restart it happens again. Sometimes when restarting I get a message about android updating but can't figure out how to stop that from happening.
Thanks in advance for any help!!! This is very annoying.
Are you doing full wipes and factory reset? If you are doing this between each flash then it sounds like you are restoring bad data into your apps.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Try re-flashing the latest Gapps and seeing if that will help.
It has done when I've had the same problem before.
edfunkycold said:
Are you doing full wipes and factory reset? If you are doing this between each flash then it sounds like you are restoring bad data into your apps.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I thought the same thing so I tried without putting back in any apps. And still happened. And if I flash Sonic with TB it does it right away when I get booted up for some reason.
KidCarter93 said:
Try re-flashing the latest Gapps and seeing if that will help.
It has done when I've had the same problem before.
Click to expand...
Click to collapse
Thanks, I'll try to find the latest Gapps now and report back if it helps out. But I'm not real familiar with the Gapps part so it may take some searching to figure out what theya re for Sonic Rom if it matters the rom.
This is the reason why I do not do any backup.. Most stuff on my phone is not important enought to require a back up.. If I have issues, I just reinstall the rom and my apps from the market.. I have only reinstalled my current rom once, and that is because I was not able to change my current prl...
Jorgy11 said:
So I'm having a problem I can't seem to fix.
I'm rooted, have been running the stock everything but with a few tweaks and some bloat removed. Everything works great but I am hoping to improve battery life. So I researched a few ROMs and pick a couple to try. I can flash them just fine with no problems, get all my apps back and set up with no problems. and I can use the phone all day just like normal.
Now the problem: if ever I have to restart for some reason, or even after I make a nandroid back up, when it restarts and boots up I eventually get several messages where processes are one by one stopping. until the phone is useless and froze up.
So it goes through 10 or more of these:
Unfortunately, the process android.process.media has stopped
Unfortunately, the process android.process.phone has stopped
etc, etc,etc
I have tried everything I could find on here to fix, but it seems all fixes are for a single process failing. This happens to me on all Roms I have tried, but I am just wanting to run Sonic. Even if I restore the nandroid I get the messages. If I factory reset or restore my kid-of-stock backup I am fine. If I start over and reflash a clean Rom I can set up and use but as soon as I restart it happens again. Sometimes when restarting I get a message about android updating but can't figure out how to stop that from happening.
Thanks in advance for any help!!! This is very annoying.
Click to expand...
Click to collapse
Sounds like you need to do a FULL Wipe before you Flash. Also make sure your Downloading the Rom over WiFi, or Hardline.
prboy1969 said:
Sounds like you need to do a FULL Wipe before you Flash. Also make sure your Downloading the Rom over WiFi, or Hardline.
Click to expand...
Click to collapse
I have been doing a full factory reset, wipe system, wipe cach and dalvic. I downloaded the Roms onto my computer and transferred them to sd card. It happens for all ROMs except the stock backup I made.
Jorgy11 said:
I have been doing a full factory reset, wipe system, wipe cach and dalvic. I downloaded the Roms onto my computer and transferred them to sd card. It happens for all ROMs except the stock backup I made.
Click to expand...
Click to collapse
Do not restore anything with TB whatsoever and I can assure you it will work. There is corrupt data somewhere.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Jorgy11 said:
I have been doing a full factory reset, wipe system, wipe cach and dalvic. I downloaded the Roms onto my computer and transferred them to sd card. It happens for all ROMs except the stock backup I made.
Click to expand...
Click to collapse
The process I use for Flashing Roms is the same one I've always used. It's the one that's in my Sig. I'll also relink, in case your on the mobile. I have used it for a very long time now. It avoids a lot of the hassles of a bad flash.
http://forum.xda-developers.com/showthread.php?p=17647821
Thank You All
Thank you all for your help!!!
So far I have managed to flash the rom and reboot several times with no issues.
I have only had this GS3 for a week now and I feel I can finally play with some roms and see what I like. I usually find one I like and stick with it. On my EVO Shift I used the same rom for 2 years.
Here is what I did for anyone that may have same problem:
Wiped everything, per-normal.
Loaded ROM.
Loaded a few of the apps I wanted to keep some settings for (like GO Launcher and Handcent) using Rom Toolboxes App manager.
I then rebooted to see if I had any problems... none.
Used Rom Toolbox to install just the apps and no data for my other 50+ apps I wanted to keep.
Made Nandroid backup, which forced reboot... no problems.
Installed Titanium Backup, this is where I was nervous because I thought it might be that app causing problems with asking about new ID and such. Installed just 2 apps that I wanted to keep data for that Rom Toolbox for whatever reason didn't have, maybe I didn't have a recent backup. 2 apps were Tasker and GO Bookmark widget. When asked to change ID I selected "later" and after restoring 2 apps I imediatly deleted TB.
Reboot to see if I got errors... none
Setup all settings and tweaks I wanted.
Made Nandroid backup... no issues yet
I then deleted all TB backups I had on SD card figuring one was the culprit.
I am still nervous to re install TB but at least as of now I have a working nandroid to revert to so after a couple days I will reuse it.
As of now I have had no issues what so ever... and I can tell battery life on this Sonic rom is much better.
Glad your all sorted out . I do not think that Titanium Backup the App itself is was causing the issues. Although I do recognize somethings that could. Restoring GoLauncher with settings Data could cause issues. Especially from one Rom to the next. Hopefully your not trying to restore the Data settings you had on the Shift. Also with Handcent, I would not restore settings across different Roms.
TEAM MiK
MikROMs Since 3/13/11
com.android.phone has stopped
Jorgy11 said:
So I'm having a problem I can't seem to fix.
I'm rooted, have been running the stock everything but with a few tweaks and some bloat removed. Everything works great but I am hoping to improve battery life. So I researched a few ROMs and pick a couple to try. I can flash them just fine with no problems, get all my apps back and set up with no problems. and I can use the phone all day just like normal.
Now the problem: if ever I have to restart for some reason, or even after I make a nandroid back up, when it restarts and boots up I eventually get several messages where processes are one by one stopping. until the phone is useless and froze up.
So it goes through 10 or more of these:
Unfortunately, the process android.process.media has stopped
Unfortunately, the process android.process.phone has stopped
etc, etc,etc
I have tried everything I could find on here to fix, but it seems all fixes are for a single process failing. This happens to me on all Roms I have tried, but I am just wanting to run Sonic. Even if I restore the nandroid I get the messages. If I factory reset or restore my kid-of-stock backup I am fine. If I start over and reflash a clean Rom I can set up and use but as soon as I restart it happens again. Sometimes when restarting I get a message about android updating but can't figure out how to stop that from happening.
Thanks in advance for any help!!! This is very annoying.
Click to expand...
Click to collapse
I had the exact same problem with a reoccurring message that would flash on and off every second or so. I did both a data restart then a reboot of the android software by pushing the down volume button then holding the power button. When the LG logo appeared I released both buttons and followed the instructions for an android factory reboot. Apparently it is the SIM card. The android com.android.phone communicates with the SIM card and allows calls and texts to be sent and received using the android software. My SIM card got damaged somehow and could not receive the call from the android app com.android.phone. I had to buy a new SIM card for ten dollars and had my stored files on the SIM moved to the new one and no more problems. Telus and Bell move the files to the new SIM for free i'm sure other major service providers offer the same free service.
@pokey2000 Thanks for that info. But this is the Sprint S3 section. And the user you are replying to has a Sprint S3. Sprint phones are Cdma and do not have a removable sim card.
His issues where resolved 6 months ago. This is the second thread you bring back up that is old and dead. Please look at and read the thread. Before bringing dead topics back up.
Remember search is your best friend, Have a great day!
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.
I have been having this annoying problem since day 1 and cannot get an answer to it. Even google has failed me. So, whenever I choose app defaults (like launcher or different sms app, etc) they stick as defaults until I reboot. When I reboot, it asks me again for each one. I have this same problem whether I am rooted or not, have had it with stock roms, etc. Why is this happening? It is very frustrating.
Wow... no one else is having this problem? Should I return it for exchange? It seems like a software glitch, but a factory reset doesn't fix it.
Still having this issue. Is no one else having it? Are there file permissions I can check? Is there a file not properly getting saved which holds defaults? I hate having to constantly remind my phone which apps to use for what.
What Rom are you on ? Are you doing a Clean Install ?
prboy1969 said:
What Rom are you on ? Are you doing a Clean Install ?
Click to expand...
Click to collapse
As I stated in the OP, on every ROM, rooted or not. I have done a wipe with every ROM I have used. Even occurs when I do a factory reset with a stock rom. Fix permissions does not help either.
I have a sneaking suspicion that there is no such thing as a full factory reset.
edufur said:
As I stated in the OP, on every ROM, rooted or not. I have done a wipe with every ROM I have used. Even occurs when I do a factory reset with a stock rom. Fix permissions does not help either.
I have a sneaking suspicion that there is no such thing as a full factory reset.
Click to expand...
Click to collapse
Did you try wiping /system prior to flashing the various ROMs? Typically when someone does a factory reset, it means they are clearing /data and the caches. It sounds to me like something is messed up in your /system partition, which might be persistent across ROMs.
topherk said:
Did you try wiping /system prior to flashing the various ROMs? Typically when someone does a factory reset, it means they are clearing /data and the caches. It sounds to me like something is messed up in your /system partition, which might be persistent across ROMs.
Click to expand...
Click to collapse
Yes... full wipe before each rom... and full wipes after factory resets.
does anyone know which file is responsible for storing app defaults? I'd like to take a look and see if it is getting overwritten, or what the deal might be. This is an annoying problem. Having to keep selecting my video player, launcher, etc.
edufur said:
Yes... full wipe before each rom... and full wipes after factory resets.
Click to expand...
Click to collapse
By " Full Wipes " . Do you mean you wiped System, Data, Cache, Dalvik, and a Factory Reset ?
prboy1969 said:
By " Full Wipes " . Do you mean you wiped System, Data, Cache, Dalvik, and a Factory Reset ?
Click to expand...
Click to collapse
Yes... e-v-e-r-y-t-h-i-n-g
I have fully wiped (yes all of it) prior to a stock rom install... and factory reset plus fully wiped (yes all of it) after a stock rom install.
yes... wiped to the point of losing ALL- ALL--ALL data. I have taken this thing down clean.
I have one-clicked, standard odin'd, kies, dialer pad reset, recovery mode reset, settings reset....
Every time... I am able to get back to stock clean... but nothing is resolving to the point where app defaults will start behaving. They arent behaving.
I lose them after every reboot.
app defaults not sticking on reboot
I am also having this problem on my Sprint SGS3 (not rooted).
Can you post a Screen Shot of the Pop Up you see when the issue occurs ?
prboy1969 said:
Can you post a Screen Shot of the Pop Up you see when the issue occurs ?
Click to expand...
Click to collapse
I don't understand why you need that. KnishKnosh understands what the issue is. Are you not understanding what I am describing?
Surely you have seen this phenomenon before. Whenever there are multiple apps to accomplish a task (i.e. browsing, launching, texting, etc), it will ask you which app you want to use. You then choose an app and tell it to always use it or to use it just once. What I am saying is that even when I choose "always," it only sticks until I reboot.... then it asks again. This is not normal behavior.
I have the same issue as well Edufur, So you're not alone.
Usually my problem is Home Launchers not sticking on reboot.
And coincidentally its all the home launcher apps i paid for pro excluding Holo Launcher and Nova.
Apex Pro, LauncherPro+, ADWLauncher Ex are the ones for me that always resets its default status for being home.
There's a lot of people that has this problem and there hasn't been a fix for it.
Its more like a Device Compatibility issue for certain applications to me then anything else.
Because my friends LG OG doesn't have these issues.
edufur said:
I don't understand why you need that. KnishKnosh understands what the issue is. Are you not understanding what I am describing?
Surely you have seen this phenomenon before. Whenever there are multiple apps to accomplish a task (i.e. browsing, launching, texting, etc), it will ask you which app you want to use. You then choose an app and tell it to always use it or to use it just once. What I am saying is that even when I choose "always," it only sticks until I reboot.... then it asks again. This is not normal behavior.
Click to expand...
Click to collapse
I want to see your issue resolved. That is why I am asking all the questions, and for more information. I do not have the Device in front of me. So I must ask questions in order to help track down the issue. Yes I have seen the issue before. Spark91 brings up an interesting question. Are you using the Stock TW Launcher, or a different one ?
i uploaded scrernshot. hope it helps. thanks.
First thing is please edit that pic . So you Tap Always and after a Reboot it just asks again ? Has it always been that way ? You mentioned it was only on certain Launchers. Does it do the same thing on the TouchWiz Launcher ?
prboy1969 said:
First thing is please edit that pic . So you Tap Always and after a Reboot it just asks again ? Has it always been that way ? You mentioned it was only on certain Launchers. Does it do the same thing on the TouchWiz Launcher ?
Click to expand...
Click to collapse
So it looks like he is experiencing the same thing as me. Yes, that is what happens. And even when I click "Always," it only sticks until the next reboot... and then it happens again. Yes, it has been like this ever since I bought the device (and even before rooting). Yes... it continues to be a problem even after factory resets / multiple wipes / all ROMS / full clears (including internal storage)... yes FULL wipes... before and after flashing new roms, stock roms, all of it. Sorry... but I am trying to be as clear as I can on this because it seems like people keep asking the same basic questions. No one seems to have a clue about this problem... it is nice to know though, that I am not alone with this problem.
So it looks like this problem even exists for other Galaxy products. I never realized this before but my GF has the Epic 4G Touch (galaxy s2) and it has the same issue. How is it that this isn't a big concern for people?
edufur said:
So it looks like this problem even exists for other Galaxy products. I never realized this before but my GF has the Epic 4G Touch (galaxy s2) and it has the same issue. How is it that this isn't a big concern for people?
Click to expand...
Click to collapse
Because it sticks for everyone else. Like me.