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.
Related
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.
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:
After flashing a new version of CM11, i found myself in a loop upon startup where many of the core applications of android stopped working. When i reverted back to the old version that worked(I didn't have a backup saved but rather i flashed the older nightly of the rom again), I noticed that my home button, lock screen, and notification bar/toggle screen wasn't working any more. I looked into it and looked at my apps, and saw an unnamed app with the description "com.android.keyguard". upon looking this process up, i found out that when people disabled this process their home button, lock screen, and notification bar stopped working (coincidental eh?), and decided that this was the source of the problem.
Is there any way to load on a new, fresh version of "com.android.keyguard" or should i just do a factory reset? I would prefer to save my local data, but if i must do it in order to have a phone that does anything useful, i obviously will.
If I need to do a factory reset, what is the cleanest and smartest method of doing so? I know titanium backup can cause a lot of problems (and in this case i'm worried it will duplicate com.android.keyguard), but I assume there is some sort of method that makes a factory reset while retaining the bulk of user data very easy. am i correct?
Do a full wipe and flash again, check the md5 of your download.
Only use titanium for use apps, never system apps or settings. There is no easier way to change rom.
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Jahid4 said:
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Click to expand...
Click to collapse
Flash back to stock and start over.
Beamed in by telepathy.
Hey all
So after a botched Cyanogenmod install on my AT&T GS3, I am having some issues with the stock ROM. Here's what happened: I tried to install CM using the windows installer, everything went well until the end and then I got a prompt on the phone prior to it rebooting "Root access lost, fix? Yes/No". Regardless of choice, phone would always boot back to stock ROM. Asked for some advice on the CM forum and was told KNOX was the issue. I then rooted the phone using Towelroot, and then installed Super SU. Super SU when opened for the first time said KNOX was installed, did I want to disable it, I chose YES. Re-tried CM installer, same issue, just boots back to stock ROM.
At this point I gave up and just re-installed all my apps and settings, synched my Google account etc. Since then I can no longer download anything from any Google app, it just says "Download failed". So Gmail attachments, links, Chrome etc. nothing downloads. Although stock Internet downloads are fine. Swiftkey now errors saying "Cannot save language pack" then crashes, Swype keyboard keeps on re-enabling itself after I turn it off, and apps that worked fine before are crashing like crazy.
Last night I performed a wipe/factory reset after starting in recovery mode. This did not help. I also noticed that recovery mode boot screen is Cyanogenmod boot screen still, so guessing factory reset is not exactly a full factory reset and it just wipes data/cache etc.
Seems to me like some kind of permissions issue. I downloaded Root Explorer and had a poke around. Permissions look fine (read/write etc.) on Downloads folder. Only thing that looked odd was there are 3 different file system areas so 3 different downloads folders (ie sdcard0/0/Downloads, storage/0/downloads and storage/legacy/downloads). Not sure if that is normal.
Just want to put it back to how it was. Any suggestions what to do next?
Cheers.
I upgraded from a rooted 4.4.2 using muniz instructions last night and using the DeOdexed ROM, and then used his batch DeBloater on Extreme to remove all the crap. The upgrade wiped my phone (not a bad thing, I wanted to start fresh), so I'm at a fresh starting point other than what is mentioned above. Thanks muniz btw, you're awesome.
From here I wanted to turn on Phone encryption, as an extra security measure. Encrypting the external SD card went fine, but encrypting the phone did not... It displayed the little encrypting android screen for a few seconds and then went black, button presses did nothing. After waiting over an hour I pulled the battery and restarted. I got informed that the encryption failed and the phone would be restored to factory default. No biggy, just back where I was an hour ago.
So the question is, before I try this all over again, does the encryption work with this custom ROM and debloated? Is there anything special I can do or might be doing wrong? And will this interfere with root or anything else I may want to install in the future?
Does anyone use the built in encryption with their android?
BeanBagKing said:
Does anyone use the built in encryption with their android?
Click to expand...
Click to collapse
You need to disable superuser, reboot phone, enable the encryption and then re-root. I did this and everything was working fine until one of my kids entered my pin wrong a few times in a row and the phone did a factory reset... I upgraded to OC1 rather than go through all the trouble again.