Related
TL;DR: I have flashed the stock 4.2.1 image through fastboot, and yet my n7 wifi still reboots continuously at the google screen with the little unlocked lock.
Background: I have had the device for about 3 months, no real problems with it before this. I was reading yesterday night and i fell asleep, and thus instead of being on my desk all night the device was under a blanket. When i woke up, I opened the cover and found it on the google screen with the lock. It was warm, but not incredibly so. I thought it was weird that it had rebooted and apparently frozen, but i held down the power to turn it off. when i turned it back on, it started the google screen, then went black, then started the google screen again. Seems like there may be some sort of a kernel issue that is keeping it from booting. The next thing i did was to go into recovery (had CWM at this point, and it was rooted as well but that's a moot point if i can't get into the system.) and i did a backup, then wiped data and did a restore from the backup that i had just made. after rebooting, it made it all the way into the system, and seemed ok. I set it down, and a few moments later it turned off and started doing the loopy google screen thing again. Next, I went into recovery and wiped data/factory reset, and tried to boot up. no luck, still looping. Next, i grabbed the 4.0 toolkit from the dev section and tried to flash the stock recovery from that, but it was proving troublesome so i just downloaded the image myself and fastbooted then replaced cwm with the stock recovery, wiped everything, and flashed the 4.2.1 image. that should have worked, from what i understand, but no, still being loopy. I re-wiped and flashed, tried 4.1.2 instead, that didn't work, and i re-did 4.2.1. after flashing 4.2.1 and then leaving it boot looping for a little while, i noticed that it sometimes made it into the boot animation and then the animation froze and it rebooted and looped more. after a few more tries, powering it off, leaving it for a few min, and powering it on again, it booted all the way to the welcome screen to pick a language and then froze. some number of loops later, it made it all the way to picking a wifi network and froze. I have yet to make it past that point. Thinking it may help, i fastbooted CWM onto the device, so i have a more capable recovery now. I am now going to look into pushing a non stock rom to the device to see if that will help at all.
Any ideas on what on earth could have caused this? Was it just that the device was a little warmer than usual for a while?
Any ideas on how i can fix this? Much appreciated!
Lastly, should i consider looking at sending it back to google? I didn't think there was anything wrong with the hardware, but i'm not sure.
Thanks!
Update: After leaving the system repeating it's loopy boot thing for about 45 min, it seems to have finally booted into the system, and has yet to reboot again. I have no idea why this happened in the first case, nor why this finally worked in the end, but so far it seems ok.
More: Ok, so it still seems to be looping a lot. I have no idea why still. I'm having trouble getting it to boot back into the system, so hopefully something helps fix this.
Ok, so a day later it seems to have settled down such that there's very little looping on the google logo screen any more; now it just tends to randomly reboot when in use. this is quite frustrating, but seems more similar to what others have reported to be the case with 4.2.1. oddly, i never had these reboot issues before it decided to fail the first time, so i'm not sure if this is just because ii'm on 4.2.1. I may look at flashing back to 4.1.2 and staying there, i suppose it can't hurt. does anyone else have any ideas as to what could be going on?
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
avpatel said:
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
Click to expand...
Click to collapse
The exact same thing happened to me, i finally flashed 4.2.2. it booted, but then my IMEI disappeared and i couldnt make any calls. It was completely random. It is possible that the same thing is happening to you. If that is the case, the only fix I know is to change the board.
if you can flash CWM or TWRP, try wiping the system files and then flashing a rom to see what happens.
What do you mean change the board?
And for the rest of the suggestions I'd really appreciate a bit of an explanation - I'm not terribly experienced with messing with Android;
Well I did some research and I flashed TWRP, wiped system and data. I then flashed 4.4.4, but it didn't boot. I'll try to turn it on again tomorrow.
^^On stock 4.2.2, does your phone have an imei number? If not, you will need to send the phone to LG for repair.
avpatel said:
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
Click to expand...
Click to collapse
Did you wipe the system cache and dalvik cache BEFORE AND AFTER flashing a zip?
I've seen many instances of an unsucessful boot becuase the cache wasn't cleared AFTER flashing the zip.
If it still doesn't work I'd recommend you to redownload the system zip from the factory image site.
I have a T-Mo Note 4 and after updating to Jellybean about month and half ago, my phone randomly started rebooting and sometimes being stuck in the reboot loop. If I take the battery out and put it back in, it would get out of the loop sometimes. I noticed it happens when phone is looking for GPS signal or if an app freezes. I've tried wiping cache partition previously as well as doing factory reset and phone would still keep restarting at random times. I got the phone replaced by T-Mobile under the warranty and few weeks later, same thing happened.
Is there a fix for this? Phone is stock and not rooted.
Good day everyone.
I lost my cellphone, so I started using this Nexus 4 that my brother had left, I factory reset it, then started using it, an update came up, around 18MB i guess?
anyways, it worked great for the first 2 weeks, then due to low battery, got turned off, I turned it on and it got stuck at the Boot, restarted a few times and it worked.
same thing happened again, until it started getting stuck at bootloop.
tried factory reset through recovery, it worked once, but then again, once I restarted the phone, it'd be bootlooping.
so I tried flashing the Phone, to 5.0 from 5.1, thinking, it'd solve the issue but it didn't.
Now, the cellphone, is i guess, bricked or something? I'm new to all these.
any solutions?
TL;DR
Flashed Nexus 4 - Stops at Bootloop, no matter I try to factoy reset it, or flash it or anything.
is there any chance it'd be fixed or is the phone done?
I installed 8.1 last week. Everything was working smoothly. Was trying magisk youtube mod. Screwed something up. Phone went into bootloops. Reinstalled everything .Wiped data. Now my phone reboots randomly. Everything stock .Rooted with Magisk. Mainly it happens whenever i launch a new app(An app which was not launched before). After few tries, the app opens up and doesnt' result in reboot.
Any ideas what could it be ?
You should of wiped system and cache also might be your problem. Also if you where using any substratum themes remove then manually as well. Not sure if they would cause reboots.
coolsid8 said:
I installed 8.1 last week. Everything was working smoothly. Was trying magisk youtube mod. Screwed something up. Phone went into bootloops. Reinstalled everything .Wiped data. Now my phone reboots randomly. Everything stock .Rooted with Magisk. Mainly it happens whenever i launch a new app(An app which was not launched before). After few tries, the app opens up and doesnt' result in reboot.
Any ideas what could it be ?
Click to expand...
Click to collapse
FC's are one thing but random reboots are a completely different animal. I would completely wipe the phone and apply the latest factory image using flash-all.bat. If that doesn't fix it you may have a hardware issue (eg. degraded battery).
Wiping caches helped
I'm running SUPERXE-8.1.0-OPP5.005_v1.5.1.
My 6P was going crazy, restarting every 5 minutes or so. It rebooted so quickly it felt like a soft restart, so I thought powering off and rebooting to recovery using the power + down volume to clear the cache in TWRP would help.
Cleared system and Dalvik and powered down. Full reboot and (for now) it feels much happier and hasn't spontaneously restarted yet. That was about 15 hours ago.
Hope I didn't just Jynx myself, but I think it helped...
I've flashed the final 8.1 images to upgrade my 8.0 unmodified system. Now I've random reboots, usually when I've leave home to go to work or vice versa. Something related to wifi, that I'm connecto on both my work and home?
Same here I had to factory reset I'm having a feeling it's going to happen again. I am on factory, rooted with magisk. I always use SuperSU not saying that is what it is however it did happen when I got home from work and just kept rebooting before I could unlock.