Ok I just got my S3, straight out of the box I booted into odin and successfully followed these instructions to get root http://forum.xda-developers.com/showthread.php?t=1756885 rebooted and started setting up my phone. It automatically started restoring all my apps then I went on and used titanium to restore my k9 mail and a few other apps (no system data or sms app data or anything like that). After I rebooted a messaged appeared " Unfortunately, Messaging has stopped" cleared the cache, fixed permissions, cleared cache and data of the messaging app. Nothing worked. Reset factory. As soon as the phone booted to the setup screen the messaging app error was already there. Back to Odin and reloaded the rooted tar file (I'm using the full stock, rooted version) and I still get the error when I turn the phone on! How can that be?
Exact same problem
jasondhsd said:
Ok I just got my S3, straight out of the box I booted into odin and successfully followed these instructions to get root http://forum.xda-developers.com/showthread.php?t=1756885 rebooted and started setting up my phone. It automatically started restoring all my apps then I went on and used titanium to restore my k9 mail and a few other apps (no system data or sms app data or anything like that). After I rebooted a messaged appeared " Unfortunately, Messaging has stopped" cleared the cache, fixed permissions, cleared cache and data of the messaging app. Nothing worked. Reset factory. As soon as the phone booted to the setup screen the messaging app error was already there. Back to Odin and reloaded the rooted tar file (I'm using the full stock, rooted version) and I still get the error when I turn the phone on! How can that be?
Click to expand...
Click to collapse
My SIII is doing the exact same thing. Verizon 32 gb rooted stock I am returning and they are shipping me a new one on the 14 day no worry guarantee.
Mine SIII also get a busy signal when trying to make a call an phone wont call out or receive calls I am reading where this is happening to a lot of them.
TheSurgeon said:
My SIII is doing the exact same thing. Verizon 32 gb rooted stock I am returning and they are shipping me a new one on the 14 day no worry guarantee.
Mine SIII also get a busy signal when trying to make a call an phone wont call out or receive calls I am reading where this is happening to a lot of them.
Click to expand...
Click to collapse
Hi I found another thread that had a solution, didn't think it would work but it did. I can't find the thread or I'd give him credit.
Basically, boot into odin and flash this (verizon stock unrooted) h**p://samsung-updates.com/get/2114/Samsung_Firmware_SCH-I535_VZW_I535VRALF2_Android_4_0_4.html after its done let it boot and then restart and go back into odin and reflash the rooted image. It's odd but it worked and all my apps and data remained(but backup just in case).
Factory reset guys. You are writing system files over existing system files. Factory reset. Factory reset. Factory reset
Sent from my SCH-I535 using xda app-developers app
das7982 said:
Factory reset guys. You are writing system files over existing system files. Factory reset. Factory reset. Factory reset
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Factory reset didn't work, first thing I tried...did it twice, nor did reflashing the rooted image, fixing permissions, clearing caches, etc. After the factory reset and reloading the rooted image, the error would appear on the language selection screen when first being setup. Reloading the stock non-rooted image and then reflashing the rooted image was the only thing that fixed it.
jasondhsd said:
Hi I found another thread that had a solution, didn't think it would work but it did. I can't find the thread or I'd give him credit.
Basically, boot into odin and flash this (verizon stock unrooted) h**p://samsung-updates.com/get/2114/Samsung_Firmware_SCH-I535_VZW_I535VRALF2_Android_4_0_4.html after its done let it boot and then restart and go back into odin and reflash the rooted image. It's odd but it worked and all my apps and data remained(but backup just in case).
Click to expand...
Click to collapse
Your my hero! This worked perfect. Now everything is as I want it. Once you validate you should make a new topic in development with the subject being the error message and Samsung Galaxy SIII this way all the people with this problem can easily impliment the solution.
Also you were correct. None of my data was lost.
:good::good:
Related
PLEASE HELP!!
I installed the Alpha-X ICS ROM for Evo 3D. The problem that I'm facing is that it keeps re-booting to "No Service" state.
I've already tried toggling the "Airplane" mode method - the moment I turn Airplane mode off, the status bar shows that I'm connected to Sprint but within a second starts rebooting (showing the ICS start up screen animation) and goes in a loop for 5-6 times and then ends up back with "No Service" state.
Please help as I really like this ROM. I am a newbie here, hence XDA doesn't allow me to post directly to the Alpha-X thread.
[email protected] said:
PLEASE HELP!!
I installed the Alpha-X ICS ROM for Evo 3D. The problem that I'm facing is that it keeps re-booting to "No Service" state.
I've already tried toggling the "Airplane" mode method - the moment I turn Airplane mode off, the status bar shows that I'm connected to Sprint but within a second starts rebooting (showing the ICS start up screen animation) and goes in a loop for 5-6 times and then ends up back with "No Service" state.
Please help as I really like this ROM. I am a newbie here, hence XDA doesn't allow me to post directly to the Alpha-X thread.
Click to expand...
Click to collapse
Hello,
How did you flash this ROM? Are you on HBoot 1.5?
If so, you will need to re-flash this ROM using Fastboot (PM Me if you cant find the instructions)
Yes, I'm on HBoot 1.5 and flashed it using Flash GUI.
I was earlier using ClearROM.
Update: I guess, i realized the problem - during the first time I had flashed this ROM, I had cleared all data & cache 9basically factory reset). It had worked fine.
Once in, I used Titanium backup to restore all my app data (including system data)... I guess that system data is causing this issue. I re-did the entire process (factory reset & flash) and now it's working fine.
I'll go ahead and try restoring only user app this time and update back.
This just proves my "Noob"ness, I guess
[email protected] said:
Update: I guess, i realized the problem - during the first time I had flashed this ROM, I had cleared all data & cache 9basically factory reset). It had worked fine.
Once in, I used Titanium backup to restore all my app data (including system data)... I guess that system data is causing this issue. I re-did the entire process (factory reset & flash) and now it's working fine.
I'll go ahead and try restoring only user app this time and update back.
This just proves my "Noob"ness, I guess
Click to expand...
Click to collapse
I just wrote a post about this lol. Yes, it is only the system spp/data that will cause the issues. You shouldn't have problems restoring all of your user apps and data. I am running ALPHA X with all of my apps and data restored through TB with zero problems.
Bamba1260 said:
I just wrote a post about this lol. Yes, it is only the system spp/data that will cause the issues. You shouldn't have problems restoring all of your user apps and data. I am running ALPHA X with all of my apps and data restored through TB with zero problems.
Click to expand...
Click to collapse
im going to try this to solve my problems i have been having with my phone... you will be getting lots of thanks if it works lol
[email protected] said:
Update: I guess, i realized the problem - during the first time I had flashed this ROM, I had cleared all data & cache 9basically factory reset). It had worked fine.
Once in, I used Titanium backup to restore all my app data (including system data)... I guess that system data is causing this issue. I re-did the entire process (factory reset & flash) and now it's working fine.
I'll go ahead and try restoring only user app this time and update back.
This just proves my "Noob"ness, I guess
Click to expand...
Click to collapse
LOL....restoring system data can cause all sorts of hell for you as Bamba1260's already pointed out and you've already figured out the hard way, and there's nothing wrong with being a "noob" either, but keep in mind if you're looking for a stable and fully functioning phone or prone to freaking out when something goes wrong.....this is after all an ALPHA (experimental / for testing and bug reporting purposes only) rom. Indeed it is a very good alpha state rom, but things are likely to and should be expected to go wrong with it periodically.
hockeyfamily737 said:
LOL....restoring system data can cause all sorts of hell for you as Bamba1260's already pointed out and you've already figured out the hard way, and there's nothing wrong with being a "noob" either, but keep in mind if you're looking for a stable and fully functioning phone or prone to freaking out when something goes wrong.....this is after all an ALPHA (experimental / for testing and bug reporting purposes only) rom. Indeed it is a very good alpha state rom, but things are likely to and should be expected to go wrong with it periodically.
Click to expand...
Click to collapse
Yeah.. that's one more thing I did realize.. but was so enamored by the ICS ROM that I wanted to "taste" it one way or other..
Anyway, since I'm not done with my first 10 posts, I will have to post this bug(?) here for everybody's FYI that the GPS doesn't seem to work with this ROM.
So, know before you jump...
P.S. I still love this ROM - one of the smoothest that I've tried.
For some reason, anytime I attempt to copy/cut whatever app im in crashes. When I long press to copy, I never get the context to complete the action. This only started happening after rooting my phone yesterday Anything I can do to fix this?
via Galaxy S III
Well, was unable to figure out the problem so this is what I ended up doing:
First of all, I rooted via mrRobinsons method and installed cwm as he instructed as well. I'm running CWM 5.5.0.4 IIRC
I did a nandroid and then did a factory reset, wiped cache, wiped dalvik cache and then I flashed Jirv311's stock/rooted/deodexed AT&T rom.
After rebooting I went into the browser to confirm it was working right, and it was. So I rebooted into recovery and went to advanced restore and restored data. After rebooting I went into the browser to confirm it was still working...it wasn't So I flashed the rom from above again, tested it, working right. This time I just installed the apps I wanted one by one from the market via my pc. After they all installed I checked to make sure it was working right, it was, and it's been working right ever since.
I was disappointed with the LFB performance etc so today I tried flashing back to LF2.
Process I followed was this:
1) Directly from LFB, I fashed LF2 tar with Odin without wipe
Problem faced: "android.process.acore has stopped unexpectedly" and "contacts has stopped". Phone remained in a hung state with these messages popping up continuously and totally unusable.
2) Went back to CWM, wiped cache and dalvik cache, rebooted
Problem faced: Still same as above
3) Flashed back to LFB to make phone usable, took full Titanium backup. Then went back to CWM, wiped data (factory reset). Flashed LF2 again with Odin. Worked fine for a bit, then restored Titanium backup to get my apps and settings. Rebooted.
Problem faced: Still same as above.
4) Restored nandroid backup I had of LFB.
Problem faced: None, all working but I am still on LFB and back where I started.
Is there a way to go back to LF2 and keep my apps and data?
Any help will be appreciated and thanked.
Did you restore System apps? You can only use Titanium for non-system apps, since it will otherwise cause these issues.
d4fseeker said:
Did you restore System apps? You can only use Titanium for non-system apps, since it will otherwise cause these issues.
Click to expand...
Click to collapse
Restored only user apps + data.
Could you try installing the apps one at a time until you find the issue?
Titanium shows 294 items.
I don't think I have the patience to install them one by one.
There's another MAJOR problem I'm facing now after doing the nandroid restore.
When I'm on a call, THE OTHER PERSON CAN'T HEAR ME!!
I'll try flashing the ROM again through Odin and see if that solves this issue. If it doesn't, I have no clue how to proceed from there.
Sent from my GT-I9300 using Tapatalk 2
You probably have LFB modem with known problem .
Solutions mess for hours or wipe phone flash clean rom .
jje
Did you have Samsung or Google, or third party app restore settings?
The fact that LFB introduced new settings that it attempts to restore on an rom without these options may cause issues.
OK, this is getting weirder.
I wiped phone clean, then flashed LFB because of above problem. Restored user apps+data with Titanium.
Phone was working fine, until someone called just now. The screen went black and I could hear the ringtone but name wasn't shown. After sometime I got a pop-up message "com.android.phone stopped working". And I couldn't see who called as it wasn't logged either.
Now it gets weirder.
I tried to replicate this issue by calling from my landline and another mobile but it worked perfectly for the 5-10 times I tried. Then I tried another different mobile and the problem occurs again!!! And this is when I have flashed LFB after clean wipe (in CWM) and not restored system apps.......!
Please HELP!! I am getting desperate now!
Lennyuk said:
Did you have Samsung or Google, or third party app restore settings?
The fact that LFB introduced new settings that it attempts to restore on an rom without these options may cause issues.
Click to expand...
Click to collapse
Could this explain the above problem?? Where do I disable it? I haven't enabled anything that's not on by default.
JJEgan said:
You probably have LFB modem with known problem .
Solutions mess for hours or wipe phone flash clean rom .
jje
Click to expand...
Click to collapse
I did a clean wipe and I'm getting a different issue! Pls help!
g4rvd4 said:
OK, this is getting weirder.
I wiped phone clean, then flashed LFB because of above problem. Restored user apps+data with Titanium.
Phone was working fine, until someone called just now. The screen went black and I could hear the ringtone but name wasn't shown. After sometime I got a pop-up message "com.android.phone stopped working". And I couldn't see who called as it wasn't logged either.
Now it gets weirder.
I tried to replicate this issue by calling from my landline and another mobile but it worked perfectly for the 5-10 times I tried. Then I tried another different mobile and the problem occurs again!!! And this is when I have flashed LFB after clean wipe (in CWM) and not restored system apps.......!
Please HELP!! I am getting desperate now!
Try and flash lfb again could just be a bad flash something like this happened to me today
if i helped say thanks
Click to expand...
Click to collapse
g4rvd4 said:
I was disappointed with the LFB performance etc so today I tried flashing back to LF2.
Process I followed was this:
1) Directly from LFB, I fashed LF2 tar with Odin without wipe
Problem faced: "android.process.acore has stopped unexpectedly" and "contacts has stopped". Phone remained in a hung state with these messages popping up continuously and totally unusable.
2) Went back to CWM, wiped cache and dalvik cache, rebooted
Problem faced: Still same as above
3) Flashed back to LFB to make phone usable, took full Titanium backup. Then went back to CWM, wiped data (factory reset). Flashed LF2 again with Odin. Worked fine for a bit, then restored Titanium backup to get my apps and settings. Rebooted.
Problem faced: Still same as above.
4) Restored nandroid backup I had of LFB.
Problem faced: None, all working but I am still on LFB and back where I started.
Is there a way to go back to LF2 and keep my apps and data?
Any help will be appreciated and thanked.
Click to expand...
Click to collapse
Your answer is in number one "contacts has stopped". Don't restore your [CONTACTS/CALLS] in Titanium backup. I have had this same problem before. I hope that helped.
I know there are many forums addressing this problem but mines is a bit different, I know the common solution is App Info > Clear Data but this doesn't help. Neither does a force stop, reset or a clearing of settings cache.
I resolved to needing to do a data wipe, however I received this message, "failed to stat /data/date/com.android.defcontainer/cache" and nothing wiped. I started the phone to the exact same home screen and apps, but I had lost wifi settings and such, and can't open settings to set up wifi yet again.
I contemplated reflashing CM through the installer but wasn't sure if the failed to stat problem would interfere and potentially brick.
Any help would be much appreciated, cheers.
Flash the latest stock firmware for your country with Odin, factory reset in recovery before first boot.
boomboomer said:
Flash the latest stock firmware for your country with Odin, factory reset in recovery before first boot.
Click to expand...
Click to collapse
I read online that downgrading from 4.4 (CM) to Stock 4.3 would hard brick the device, is there any merit to this?
No, if you use the right firmware and do it properly there is no more risk than with a normal flash.
Problems with all roms SM-T210
Hi!
This problem is driving me crazy!
I have a similar problem!
I have Samsung Galaxy Tab SM-T210
For a long time I used RocketTab rom. I decided to try out new Android 4.4.2 Rom.
I started to get an error "Unfortunately settings has stopped" when I tried to open settings. I also got another application errors.
Now, it does not matter what rom I install, i get application has stopped error.
Even the RocketTab rom.
I flashed original stock rom via Odin, same problem.
I tried CWM and TWRP recovery.
I wiped dalvik cache, system, cache, Data, internal storage.
After flashing a new rom via odin or recovery, same problem.
I don't understand how it's possible that after deleting everything, I still get the same error.
Sometimes when I open settings, instead of getting an error, tablet restarts.
Tablet was 100% working before flashing Android 4.2.2
Any ideas?
Thanks guys
Why are you asking in the i9300 forum?
boomboomer said:
Why are you asking in the i9300 forum?
Click to expand...
Click to collapse
Because the problem seems to be very similar.
Point taken!
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
gilbnx said:
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
Click to expand...
Click to collapse
This happened to me. I had to do a factory reset.
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
elesbb said:
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
Click to expand...
Click to collapse
Thanks elesbb, I saw your message just now but I have my phone working already since few hours ago after a 2nd stock reflashing. If I have the same issues as before - I will use chainfire's update SU.
What I did find is that once I enable accessibility (to apps like Tasker, and an LG bluetooth headphone I have (so it could announce notifications) the phone becomes unstable; it just went through 2 boot loops but eventually recovered... Hopefully it will stay stable.
Gil.