Back & Menu buttons not working, nor keyboard - Verizon Samsung Galaxy S 4

I'm really hoping someone can help me. My back and menu buttons stopped working today, and I'm pretty sure it has to do with a failed Swype install.
I'm running AOKP 4.4.2 (1/25 build) on my VZW Galaxy S4 (jfltevzw). The phone has been running great, but I can't stand the new kitkat keyboard. I decided to try Swype again, after dumping it a few years back.
I installed the free Swype (which obnoxiously comes with Dragon also), but I couldn't get past step two (select default keyboard). The wizard just wouldn't progress further. I went into the menu to try switch manually, but I trying to type would just bring up the installer again. I tried switching back to the stock keyboard via Settings>Language, but nothing would happen when I tried to type. The only thing I could do was reboot.
When I booted back up, the menu and back buttons would no longer work. I tried clearing dalvik and cache, resetting permissions, reinstalling AOKP and Gapps, and so on and so forth. I'm backing everything up to do a hard wipe, but I'm not holding my breath.
Has anyone seen this problem before? Is it failing during the Swype install just coincidence? I can't see how it could be....

After a hard-reset / factory wipe, everything is working again.
I will not be installing Swype on AOKP/KitKat again, hehe.

Related

"Unfortunately, Settings has stopped." Solution?

I have a problem that I cannot seem to figure out.
I recently rooted my Samsung GS2 I7777: http://forum.xda-developers.com/showthread.php?p=36191155#post36191155 Whether or not that is relevant, I am not sure.
When I click "Settings>More..." the screen goes black and after a minute I receive the following error:
"Unfortunately, Settings has stopped."
This only happens clicking "more..." The rest of Settings is fine. I believe this part of Settings has to do with USB, correct?
I Googled around and found no solutions. I figured something had been corrupted recently and the easiest solution would be a factory reset since I have not done much with the phone. I unrooted and I made backups and went ahead.
After the reset was complete, the problem persisted. I did not reinstall my backups or sync with my Google account. I tried a factory reset + cache wipe via Android System Recovery E3, but the result was the same. I have tried resetting four times now, but still Settings does not work despite the seemingly fresh state of the phone. I did not install any roms, if that matters.
How can this be? And how can I completely revert back to stock or get my Settings working again?
Edit: Seems to be the same problem here: http://forum.xda-developers.com/showthread.php?t=1862040
ideas?
Edit: went ahead and installed a rom. all is good.

[Q] DSC 2.0/2.3 Start system keep crashing and I cant access the ROM

Hey guys!
Im a first time rooter but somehow managed to root my Dell, flash Streakmod on it and install the DSC 2.0 ROM and then upgrade it to 2.3.
My problem is that the moment I unlock the screen after rebooting the phone I get a wall of notifications telling me that googlewhateversystem stopped working along with other applications. It seems that somewhow the whole introduction part of the phone went to ****.
Help?
Did you do both resets for DSC, namely Option 1 from the main menu and the reset option in StreakMod?
Strephon Alkhalikoi said:
Did you do both resets for DSC, namely Option 1 from the main menu and the reset option in StreakMod?
Click to expand...
Click to collapse
Yes. I installed DSC and after that made a factory reset, wipe cache, wipe dalvik etc... then I rebooted and did another factory reset on the dell standard recovery.
EDIT: I restored a backup and installed DSC again but this time I didnt do a factory reset and just wiped the cache. I managed to get on the phone but now I get constant notifications that android.phone has crashed. Any ideas?
EDIT2: I removed my sim card and restarted the phone. Everything works fine now. Seems like the Rom doesnt like my simcard. Well I guess I wont use it then. The keyboard is way to small anyway. I just wish that there would be a good ROM for me to use.
Pardon my english im from germany
It's odd that you're having such issues. I use DSC myself and have not had any problems using it. In fact, switching back to DSC solved a pair of annoyances that appear in the CM7 ROMs for the Streak: no camera zoom and the dialpad buttons being too small. If you're willing to put up with those annoyances, try using CM7 with _n0p_'s Phoenix kernel or one of the CM7 derivatives like Longhorn. Just be aware that other than DSC none of the Gingerbread ROMs are being actively maintained.
I honestly dont know what the problem is myself... I flashed it with ams and dps and then the recovery, installed the zip, wiped everything, fixed permissions and rebooted.
I tried this several times and everytime it has these crashes that make it unable to use the phone. Also after restoring my backup after the install the buttons on the bottom of the phones flash every minute or so.
Geez... why does it have to be so complicated xD?
EDIT: I decided to take a deep breath and try the whole procedure again. Flashed the phone, installed the zip, installed the update, wiped everything, rebooted, after the boot waited 10 mins and voila! It works like a charm!
If you Strephon now would be able to tell me how to change the keyboard to the default one then I'll gladly give you my thanks!
If you mean the Swype Keyboard...
Settings > Language & Keyboard. Make sure Swype is checked. Tap OK on any popups that appear and exit settings.
When you go to type something, e.g. a response to this post, press and hold the input area (the spot where you type). The menu that pops up should have an option labeled "Input Method". Tap on Input Method to change keyboards.
No I mean the standard big fat keyboard from the original Dell Streak 5 Rom. The DSC one is way to small for my fingers to type fast AND accurate.
The "big fat keyboard" is the Swype keyboard. The only other option is the default Android keyboard, with much smaller keys.

[Q] Help Can't Get Stock Working

So I've been running KitKat via CM11 nightlies for quite a while now and about every other week the I lose signal and have to reflash stock. I Use Razr Utility (http://www.droidrzr.com/index.php/t...-verizon-droid-razr-and-droid-razr-maxx-only/) to flash stock, get signal, reroot, and reinstall SafeStrap. Have done it I think like 80 times or so now.
Today when I did it, when I pressed start at the Setup Wizard it said "Preparing may take a few minutes ... blah blah" then it reboots. I rebooted and tried again, over and over it won't get past the language selection, and if I leave it alone for a few minutes w/o pressing anything it will reboot on its own still; it continually reboots over and over. Also I am no longer getting service back on a fresh stock flash. I have tried 1.8/1.82/newest of RAZR Utility, all received the same result. So I tried House of Moto with 2 different VZW firmwares (2 newest JB) and still same result.
I was able to get root w/o having to mess with Smart Actions and then use ADB w/ su and PM to disable all the setupwizard BS so I could install SS and get back to CM11. (Setup Wizard is locked and no way to bypass, even tried build.prop tweaks to turn it off and nothing) Now on CM11 it is liking to randomly reboot whenever it feels like it too; that is if it even boots back into CM11 after rebooting, sometimes it makes it all the way to CM11, sometimes it doesn't.
Does anyone know WTF is going on with my device and how to fix it. I'm going to try and get a new SIM tomorrow and see my SIM fried or something (though I never received the "No SIM" error). I'm honestly about to chuck this phone through the friggin wall....
Update: Was finally able to get CM11 to stop rebooting, upgraded to newest nightly and wiped Dalvik & Cache, and Fix Permissions. Signal has sort of come back, it goes in and out; very finicky.
Update 2: Service is completely gone and can't get it back now.

[Q] Stuck on HTC bootup screen, even though phone is actually booted up to homescreen

Hi all, hoping to get some help. I rooted my phone the other week and was using viperrom. I had no problems whatsoever, no glitches that I could remember. That is, until I decided to trade my m8 with a friends Note 3. I factory reset it and give it to her, I left the viperrom on because she didn't mind but then the glitches started to happen. The onscreen bottom 3 buttons disappeared for her (home, back,etc.), So I reset it again but the problem persists. I searched for an at&t stock rom and sideloaded that after master resetting, wiping the dalvik cache and all that... now a different problem popped up. It hangs at the HTC logo for what seems like forever, but then I noticed the volume up and down make a noise as if the phone is loaded up. I pressed the power button a few times and eventually the screen turned on and I could see the home screen. This happens every time I restart the phone and I have tried reinstalling the stock rom a few times. I am now in the process of trying a different stock rom.. the first was odexed and this new one is deodexed, I dont know if that makes a difference in my situation but does anyone know what could be causing this? Any help would be appreciated.
Nvm, after a few more master resets it seems to have sorted itself out... not sure what it was but its gone now.
If its the latest version of Viper, based on 2.22 software, you need to update the firmware package, otherwise the long boot times will continue.
Details here: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592

Of how WiFi won't turn on and I don't know that I'm doing - Galaxy Grand 2 G7105

I got my hands on a Galaxy Grand 2 sm-g7105. Performed a factory reset from device and the system worked nicely enough. A particular third party app I wanted to use wouldn't load so I kept tweaking.
I rooted and set up a CWM recovery with Odin, then considered going with Resurrection Remix. I made a backup with CWM, wiped the device and set it up. It looked great but 'audioFX.apk' or something along those lines kept crashing every 30 seconds or so. It didn't cause me any problem besides the annoying crash notification, so i figured I could just remove the apk and be done with it. To my dismay, then the notification then piled up non-stop and the system become unusable.
I went and restored the backup on CWM. Then I'd get error notifications for this and that stopping working (basically the apps present on the backup that weren't on the stock rom), so I figured the backup was useless. Another mistake, I guess.
Performed another wipe, deleted the backup for space. Tried removing every piece of bloatware I could find before unrooting (I wanted to do that). Finally everything seemed to roll... except I deleted some important apk, SecDownloadManager I've come to believe, and at that point the Play Store couldn't update a thing, it got stuck on 'Downloading'.
So I did another wipe, just to find out that didn't restore the missing apks. Got my hands on a stock rom for my model (a different build than my origibal one, but to hell with it... right?). I got that working work Odin, but to my surprise that didn't seem to completely restore the apk mess, and I got a ton of crash apl notifications and even after logging on Google the play store didn't let me in to try and see if apps could update.
Finally, I found what is supposed to be the device's original rom. Odin'd it all the way. Everything seems to be where it belongs, but I cannot really check 'cause... NOW THE ****ING WI-FI WON'T TURN ON. It's not like it doesn't connect to my network, it just won't activate. I press the switch, or goes back off.
I tried rebooting, taking out the battery for some seconds, performing a factory reset from within the system, wiping from CWM, dialing *#0011# to access service mode and deactivating power-saving mode. Nothing works.
HELP, please.
I'd be happy if the WiFi just worked, but knowing why the hell a stock rom should give any headache or what I'm doing wrong for it to go so wrong might be a step towards the solution.
PS: I'm writing this as I recall, so the details might not be completely spot-on, but the broader problems were those.

Categories

Resources