Nexus 4 Won''t pass Google Screen - Nexus 4 Q&A, Help & Troubleshooting

My N4 doesn't seem to pass the Google Screen. I flashed a new rom because for some reason I stopped receiving messages but could make phone calls. I was on PAC now I tried to flash Revolt 4.4 but now it will not pass the Google Screen. Also, I am on twrp if that helps. I have used normal wipe. then advanced wiping the system,cache,data. Anyone know how to fix this?
-Thanks !

ImHereToSaveTheDay said:
My N4 doesn't seem to pass the Google Screen. I flashed a new rom because for some reason I stopped receiving messages but could make phone calls. I was on PAC now I tried to flash Revolt 4.4 but now it will not pass the Google Screen. Also, I am on twrp if that helps. I have used normal wipe. then advanced wiping the system,cache,data. Anyone know how to fix this?
-Thanks !
Click to expand...
Click to collapse
When you say normal wipe, do you mean wipe data/factory reset? If you haven't tried that, try it then flash a new ROM and then gapps. If your problem still persists then you would probably have to revert to stock ROM (factory image)

You may have gotten a bad download of the ROM, or some other problem with the zip. If you still have the zip of your last ROM (always a good idea until you know the new one boots), then try flashing it. If not, as suggested above, revert to stock and start over.
Sent from an N4 blessed with AOKP and sanctified by Faux123!

22sl22 said:
When you say normal wipe, do you mean wipe data/factory reset? If you haven't tried that, try it then flash a new ROM and then gapps. If your problem still persists then you would probably have to revert to stock ROM (factory image)
Click to expand...
Click to collapse
With factory image will my phone be completly erased?
And I mean with when you go to twrp recvoery the normal wipe. Not Factory Reset the standard wipe data and cache.

Fixed it.
Kind of bummed out right now. It seems TWRP recovery was bugged somehow. It didn't let me wipe anything at all. even when it said it did which is odd. I had to perform a factory reset. I'm glad about the phone now booting up. Just a little bummed out all those pics I took on the 4th of July are gone.

Related

EVO Constant Reboot

Whenever i flash a new ROM, my phone keeps rebooting. Any ideas?
Thanks
At what point does it reboot?
Sent via the Sprint HTC EVO
Try clearing your cache, data, etc. and yank the battery, wait 30 seconds, put it back in.
What ROMs and kernels have you tried?
Constant reboot happens when exiting recovery mode after flashing a new ROM.
I have tried several ROMS. Only one that works is fresh ROMS.
What method is the best way to ensure cache is deleted?
through your recovery. you should always wipe before you flash
data/cache/dalvik all three options
Yo, I'm having the same problems.
Sent from my EVOo
Constant reboot fixed by factory reset for me.
Sent from my PC36100
Will give the Factory Reset a try.
Thanks
Just tried it. Didn't work.
Clear ALL cache and data from your recovery: Dalvik cache, /data, and regular cache. Also try removing your SD card (worth a shot).
Did Factory Reset
Rebooted
Flashed Damage Control ROM
Rebooting over and over...
im not rooted at all and this same thing is happening to me itll get up to the 4g sign then reboot again.. have to wait until thursday to get my replacement ughhhhhhhh =(
Arie McD said:
Did Factory Reset
Rebooted
Flashed Damage Control ROM
Rebooting over and over...
Click to expand...
Click to collapse
This just happened to me also. Did you also root with the Unrevoked Evo 2 app? That's that I did, and it's the only thing I think might be causing the problem.

Help! Stuck on "Starting Applications" during boot!

My issue is this -- my phone will be running fine for days, even weeks, and will then spontaneously reboot. The phone will then get stuck on the Android "Starting Applications" step and never get any further. I've attempted to wipe cache and Dalvik, and even gone so far as to re-flash the ROM I happen to be running at the time.
This has happened to me at least a half dozen times, and it's starting to frustrate me. I've had this issue with at least 4 different ROMS, including CM 10.1, PA, AOKP, and at least one mixed feature ROM. The only solution I've found at this point is to do a factory reset and system wipe and start from scratch.
Any suggestions on what I might try next time? I'm really at a loss.
dont wipe or clear data after you flash a rom. flash rom and if it installs correctly then clear the cache and thats it. then let it reboot
i used to get stuck in that same screen, but thats because i was clearing data after i had flashed a rom. hopefully that helps
Had this issue. Do a stock flash with the toolkit
Sent from my Nexus 4 @1.67 GHz on Stock 4.2.2
go to recovery, do a factory data reset.

[Q] Paranoid Android 3.15 rebooting several times a day Nexus 4

I have a Nexus 4 running PA 3.15, I love PA, but I get random reboots every few hours.
I rooted this phone and the only thing I flashed was PA. So it was a clean install. I tried factory resetting the phone and doing another clean install and the rebooting still exists.
I am not using an custom kernel, maybe flashing one would help my situation. I am at a crossroads, because PA and it's pie feature are amazing, but the rebooting is making me want to leave.
Any ideas on how to fix it?
Download it one more time then gapps. Wipe everything, flash PA, flash gapps wipe cache, wipe dalvik cache. It must work. Other apps install manually.
If it's using superuser, try disabling it and use supersu instead.
i found some apps hate superuser and strange stuff happens.
I will try using supersu and see what happens. Thanks.
trentgillham said:
I will try using supersu and see what happens. Thanks.
Click to expand...
Click to collapse
I am still having this problem despite clean install. did anyone find a definitive answer. thanks
jadsru1 said:
I am still having this problem despite clean install. did anyone find a definitive answer. thanks
Click to expand...
Click to collapse
I was also having the same problem, my phone sometimes get really hot and it keeps on rebooting. I tried flashing the stock ROM, new kernel everything I could but the problem still persisted. So I called up Google Customer care, as soon as I told them overheating and rebooting, they transferred my call to RMA and they replaced my phone. My phone was 5 months old and recently many people are having this problem, so its better to get it replaced. Before sending it, reflash the phone with Stock ROM and lock the bootloader. You should be fine

Cyanogen Nightlies require me to factory reset everytime

I've got Cyanogen 11.2 Nightlies and I've been having issues with various apps, etc. So I keep updating the nightlies and what winds up happening is that it will get stuck on the Samsung screen with the unlocked padlock pretty much forever. In order for me to get around this I have to factory reset and re-install the latest nightly and GAPPs.
What are my options here? Am I missing something that I need to do?
Please let me know if you need anymore information to better assist me.
Regards,
inxile.
assume you are on an i337 att
first thing i would do is a fresh flash--too many dirty flashes can give issues--what recovery are you on?
if twrp, and I prefer 2.5.0.2, go thru advanced wipe and manually wipe system/data/caches 3x. don't do any resets/formats.
when you first boot into rom let it settle then reboot then set up phone
on the apps you can go into recovery and wipe caches and fix permissions
if still no luck, try backing up to pc and then reformatting internal card

[Q] com.android.phone Crahes (VZW G2 - CM11 03/08 Snapshot)

Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
EtherBoo said:
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
Click to expand...
Click to collapse
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
xxxrichievxxx said:
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
Click to expand...
Click to collapse
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
EtherBoo said:
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
Click to expand...
Click to collapse
Yeah it can be such a pain, I flashed nightlies when they sounded like they fixed an important issue (it'd be every other day) and I flashed clean all the time. Now im just going to stick to CM11 M4 until the next milestone.
try changin network type to GLOBAL.

Categories

Resources