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?
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?
Hi folks.
So after a sleepless night and a lot of guessing and clicking around with no luck, I finally decided to ask for help.
The story:
Yesterday, I decided to open up my lovely N4 to perform the thermal pad mod (that can be found on these forums), as it was going really hot around the CPU at time and it seemed like a good solution.
Now, I'm no stranger to disassembling microelectronics without breaking them (few weeks ago, I successfully resoldered a broken power button in my old T989 that I've been using before N4).
What couldn't let me sleep at night:
And here is where the problem emerged. After re-assembling my sweet little phone (yes, i did it perfectly right), I tried to boot up and all i could see was an endless and really annoying bootloop, but as the device booted up, I did not worry much. While doing some research, I read that there's people experiencing bootloops with 4.3, so I thought that after disconnecting the battery, it just might've had happened on its own (I was using stock 4.3 with faux kernel before the nightmare started)
At this point, I booted into recovery and tried to flash the rom over, but unfortunately nothing positive happened. Then I tried factory reset and flashing different roms, also with no luck. This is when things started to get really frustrating, as no matter what I flashed, the bootloop was (and is) still there. But then I tries to restore a backup that I did right after getting my N4, back in November, and it WORKED. Why do i still have a problem then? Because it was 4.1 and OTA was giving me error every time I wanted to flash the update, so I kept flashing till i get some results. And then one of the N4 toolkits wiped my entire internal memory and I ended up with only being able to use sideload. Then I tried ALL of the N4 toolkits that can be found in here, to wipe everything and bring my phone back to everything stock, but the bootloader is locked so it cant do it, and it cant unlock it because I cant boot into the system.
Conclusion:
The phone works fine, and it proved it. But no matter what I try to flash (other than the old backup), the persistent bootloop is still there smiling at me like an a****le.
Any ideas?
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.
Hi guys,
So I had been using my Moto X Pure (3 months approx) and it had been perfectly fine. Except just a couple of days ago while I was on snapchat the phone suddenly shut down. While I tried to restart the phone it got stuck on the boot screen and didn't go past that. I initially tried to wipe cache partition & factory reset but nothing happened, it was still getting stuck on the boot screen.
My phone is unrooted and I haven't tried experimenting with the kernel or anything, mind you.
I left it alone for a couple of days and it started to boot up again, it was working perfectly, no issues whatsoever. But just yesterday the same situation occurred yet again :/ not while I was using snapchat but I unlocked the phone but the screen didn't turn on and it restarted by itself and got stuck onto boot screen again.
Is this an issue with the software or the hardware?
I talked to Motorola and they said they will issue a replacement phone, but I live overseas so it could be a hassle. Should I just send it in for replacement or try and reinstall the rom using factory image?
Thanks guys, really appreciate your help
could try reinstalling the factory image but if you havent messed with anything on the phone maybe its a hardware issue... i dont know
If the bootloader is still locked, i would definitely go through the replacement hassle. Should have no issues whatever after only 3 months and 100% stock.
DejektedZ76 said:
Hi guys,
So I had been using my Moto X Pure (3 months approx) and it had been perfectly fine. Except just a couple of days ago while I was on snapchat the phone suddenly shut down. While I tried to restart the phone it got stuck on the boot screen and didn't go past that. I initially tried to wipe cache partition & factory reset but nothing happened, it was still getting stuck on the boot screen.
My phone is unrooted and I haven't tried experimenting with the kernel or anything, mind you.
I left it alone for a couple of days and it started to boot up again, it was working perfectly, no issues whatsoever. But just yesterday the same situation occurred yet again :/ not while I was using snapchat but I unlocked the phone but the screen didn't turn on and it restarted by itself and got stuck onto boot screen again.
Is this an issue with the software or the hardware?
I talked to Motorola and they said they will issue a replacement phone, but I live overseas so it could be a hassle. Should I just send it in for replacement or try and reinstall the rom using factory image?
Thanks guys, really appreciate your help
Click to expand...
Click to collapse
Have you tried a simple factory reset? Basically a data wipe?
Sent from my One using XDA-Developers mobile app
bmeek said:
Have you tried a simple factory reset? Basically a data wipe?
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, tried a factory wipe and cleared cache but didn't seem to work.
DejektedZ76 said:
Yes, tried a factory wipe and cleared cache but didn't seem to work.
Click to expand...
Click to collapse
Yeah - I haven't heard of stock unrooted phones getting their system image corrupted such that a reset doesn't get back to proper "stock". Maybe a botched OTA, but if you've got that warranty option, probably be wise to take it.
I don't know this phone and Motorola well enough to say that unlocking your bootloader and starting from scratch, as I would be sorely tempted to do in your situation, won't void your warranty option.
Sent from my One using Tapatalk
I have a SMG870A that will not stop rebooting no matter what I do. The phone was on PK7 and has ran flawlessly for the past 3 months I've had it. Phone one day reboot and never booted up again, just bootlooped. After wiping cache/wiping data, I've had no luck. I tried reflashing the pk7 stock image from sd card, the image flashes, restarts like normal but reboots half way through the splash screen. So then I tried to Odin the phone back to OF3, no luck either. I get a pass on Odin but when then splash screen comes up, it reboots. I have a brand new battery in it, and I am not sure what else could be causing this. I have very good knowledge on flashing, as I've been doing it since the S3's came out. But this device actually has me stumped. Any help would be much appreciated!
Thanks