[Q] XCOM:EU will not launch past initial loading screen - Nexus 4 Q&A, Help & Troubleshooting

Hi, I'm Nyshan and I've been having a bit of a problem with XCOM:EU. I recently purchased it from the Google play store after looking through several forums and seeing that my device (Nexus 4) was compatible. I then proceeded to download it to my (at the time) rooted, 4.3 OS on Franco Kernel. To my dismay the game refused to launch. So I did the only rational thing and unrooted my device while also backing up XCOM. I then reinstalled XCOM after the unrooted and to my absolute disgust found the game still would not load up. I then proceeded to update my phone to the latest OS (4.4.2, still unrooted with a locked boot loader, mind you) in the waning hope that it might fix my problem. Obviously, it didn't. So now, I come here as an absolute last resort.
For ease of access:
Nexus 4
Currently Stock (4.4.2)
Unrooted, Boot loader locked
Any help would be appreciated.
Thanks,
Nyshan
P.S. I made this on my phone, so I apologize for the block of text. Also the search bar refuses to function without disappearing every time I try to use it, so sorry if this was an already resolved issue.
Has anyone else had this problem?
I've got 90+ views and 0 replies, someone say something, please!

Related

Issues with play store and "TalkBack" from google

Just want to say Hi to all who contribute to this forum, which had helped me so much over the years of searching for a better experience with my electronic devices
This is more a heads up than a question so I'll keep it brief. Last couple of days, I had issues buying apps from playstore, but no issue downloading free apps. Whenever I tried to buy something I was receiving a message that my order cannot be completed. Yesterday I finally decided to flash a custom rom and after unlocking my device, I had to flash the stock rom again, since my device stuck in boot loop. When everything was restored on stock rom, I updated manually "TalkBack" and "Chrome" and the issue repeated. I flashed one more time and this time didn't performed update to "TalkBack" from google. Now everything is fine with purchasing. Does anyone else noticed same thing?

I goofed, and I don't know how I did it

Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...
Think I figured it out
Well after writing this, for my own personal sense of masochism and an overall morbid curiosity, I kept reading, and figured out how to get the phone to actually boot into proper recovery mode (as in NOT Odin), and was able to get a ROM back on the phone, as I didn't care for any of the nandroids I had there. As I am not sure that anyone actually viewed this before I resolved my own issue much less had a chance to respond, it's not appropriate to thank anyone for solving my own problem, except for the poster of the thing that I read which led to my resolution, but I will throw out a blanket thank you to all those that take the time to develop, write, and help others solve the stupid stuff, it is appreciated, at least by this Ohioan, who sometimes manages to get in over his head!
dsly4425 said:
Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...
Click to expand...
Click to collapse

[Q] Spontaneous bootloop on certain stock roms

Hello all,
This is yet another bootloop story, although I haven't found anything quite like it yet, hence the idea to post it here for reference and in case some of you have interesting ideas to explore...
This is gonna be a bit long, but TL;DR: After my phone got "spontaneously" stuck into a bootloop, I find that only the stock 4.2.2 rom works, and no other.
So, tuesday I get back home with an empty battery and a Nexus 4 (running latest OTA) that has switched itself of after a day of somehow intense usage. No worries, I plug the AC adapter, let it charge for a bit and switch it back on. Booting seems a bit long, but I have to take care of a few home chores so I let it do its thing before coming back to it a few hours later. Only to find it still displaying the animated nexus logo. After a few switch off/switch on cycles, I understand its pretty stuck and I need to be more radical about it. So I enter the bootloader menu, and OEM unlock the phone (I had never needed to do that) hoping the full wipe associated with that will clear things up.
Well, it didn't. So I guess I'll need to flash a stock rom, and so I do. Since 4.4 is available on Google's stock roms page I try that, the animated logo changes but the end result is the same. So I try again with the latest JB (4.3) and still the same result. I get more than a bit frustrated but it's late and I need some sleep.
The next day, I call Google's warranty desk in France. They tell me that since the phone fell a few month ago, they cannot take it under the warranty program, and so I have to ask LG. Knowing there's no reasoning that will get me past the clerk that answered the phone I hang up after saying I'll get back to them via snail mail. Which I'll probably do soon, because I'm very disappointed with the way that warranty desk works.
Once at work, everytime I have a few spare minutes, I try to reflash with a new tool just in case it does more than automate what I did manually (nexus root toolkit being the one I tried most). It doesn't change a thing and my phone is still a nice animated paperweight.
I don't know why I ended up trying that, but I finally tried flashing the original 4.2.2 rom, and lo and behold, my phone finally got to the SIM code screen ! Everything worked nice after that, so once back at home, I go for the offered OTA upgrade to 4.3. Well, guess what, back to paperweight. Before reflashing 4.2.2, I took the time to flash CWM and activate adb by modifying /system/build.prop in the 4.3 image. This showed a recurrent problem with "system_server" segfaulting at launch (and it might have been caused by hal_sensors_get_list not returning anything, I have no clue). Trying the same on 4.4 yielded the same result.
Back to 4.2.2 and everything works fine, but I get nagged by the OTA notification, and more than that I'm wondering if there's any hope I might understand and fix the problem with my phone.
So, ladies and gentlemen, any clue that would help me is very welcome !
I plan to try a CM rom this week-end to see if it has the same problems as the stock one, but I have little confidence it doesn't. My guess is I have a hardware problem that's non-critical except it triggers a bug in 4.3+...
Thanks for reading !
--
Alain Perry
Same case, mi phone is totally stock and stuck on logo
KRT16S: no luck
I only had the time to try KRT16S this week-end, and this latest update doesn't change a thing. Same symptoms. So I guess I'm stuck on JB 4.2 for the coming week...

[HELP] Navigation Buttons Missing & Other Errors

Hello XDA community, I'm panicking a bit and am new to this whole smartphone thing.
So, yesterday I got an LG G2 and spent the majority of the day downloading apps and whatnot. Today I asked some friends and got the phone rooted, installed Xposed and some Modules, and decided to give flashing a new Kernel a try.
I have the LG G2 VS980 (Verizon) and flashed Dorimanx's v6.8 kernel successfully after making a Backup in TWRP.
Upon going back to basic usage, I realized the Navigation Buttons were gone. All of them. I tried swiping up and down and all around, thinking that maybe the Xposed Tweaks may have done something to them, but nothing made them appear. Also, the default Weather Widget failed to load, originally attempting to load and then defaulting to a "Failed to load widget" generic window. I went to google the issue when I got a "LG Keyboard Failed to load" error.
I immediately went and restored my backup, but the issues were still present. I tried multiple Factory Hard Resets through TWRP and even attempted Flashing an older version of Dorimanx's kernel (before anyone asks, yes I was using the VS980 version), nothing helped. In my latest desperation attempt, I used TWRP to reformat the partitions, so now my backup is gone.
Now I'm stuck, because I can't get through the VZW Setup Wizard since I apparently can't connect to the Backup Assistant network (which apparently has something to do with EFS? I'm not really sure), can't skip it without Navigation buttons, and can't access Wifi without the keyboard to type in the password to my home network. I've been avidly googling for the past 2-3 hours, but no one seems to have my exact issues. Currently, I'm following this guide to return to complete stock, and hopefully if the problem persists I can return the phone under warranty.
Can anyone offer me some help/advice in the meantime? I'm really curious as to what happened and of course I'm panicking due to potentially losing a phone after 1 day (the salesperson kept pushing their insurance on me as well, which I denied repeatedly). After the restore and then factory reset, the phone should be fully stock (the settings support this, showing the original kernel/build/everything) yet the errors persist.
Many thanks in advance!
EDIT: Here's some more detailed info:
Android version: 4.4.2
Baseband version VS98024A...
Kernel version: 3.4.0-perf
SirZer0 said:
Can anyone offer me some help/advice in the meantime? I'm really curious as to what happened and of course I'm panicking due to potentially losing a phone after 1 day (the salesperson kept pushing their insurance on me as well, which I denied repeatedly). After the restore and then factory reset, the phone should be fully stock (the settings support this, showing the original kernel/build/everything) yet the errors persist.
Many thanks in advance!
EDIT: Here's some more detailed info:
Android version: 4.4.2
Baseband version VS98024A...
Kernel version: 3.4.0-perf
Click to expand...
Click to collapse
Returning to stock will solve any software problems you might have. I understand why you had issues with xposed, I get them too sometimes. Its always best to flash your kernel first and then do your mods.

Starting Android

Hi Everyone,
I have been on a rooted Android 10 build for the past 2 years, but found the battery was starting to drain quickly, so decided to upgrade to the latest version 11.
I have rooted phones many times, however im a bit stummped.
Initially when i rooted by flashing with Odin, my patched AP file, it would boot loop the start screen, however today i have got further and it boots to "android starting", but after 3 hours it hasnt moved from that point. I cant imagine this is normal\expected? I have tried to reflash a few times and wiped\factory reset before hand, using the main CSC instead of home_csc, but still the same result.
Any ideas? Am i missing something?
Cheers!
If anyone wants to reply with a potential fix for others, then please do, however for now i have managed to obtain root using a method someone else did on XDA.
Basically, i managed to install and run TWRP, then flashed a kernel in that. Now have an up to date phone with root.
Thanks for anyone who looks at this however.

Categories

Resources