Related
Hey Guys,
I am facing a very strange issue with my N4. On Friday Night, I kept my phone for charging overnight and it was working as usual. on Saturday morning, I noticed that the phone was unresponsive and was showing a blinking red light. Tried to charge via various means but it was of no use. Finally went to a LG service centre were they could revive the phone but it was stuck in a bootloop. He suggested me that he will downgrade from KK 4.4.2 to JB 4.3 but still the phone was stuck in bootloop.
LG guy said that he doesn't have answer why this is happening. He said change the motherboard that will fix it. That is a very costly option which I cannot take. and he mentioned that there are tools online which will help it work but as an authorized service centre place he can't do it.
So here's what I did after reading several blogs, videos and but got stuck in the same place.
1. Booted in Bootloader mode, flashed stock JB 4.3 using Wugfresh Nexus Toolkit selecting the option Softbrick / Phone in bootloop.- Result : Stuck at Bootloop.
2. Flashed CWM Touch via fastboot, Went to the CWM recovery, Cleared the dalvik cache, Data, User data, Cache, Reflashed a Stock JB 4.3 - Result : Stuck at Bootloop.
3. Flashed KK 4.4.2 , again using the Wugfresh Nexus Toolkit - Result : Stuck at Bootloop.
I tried searching google for bootloops due to motherboard issues just to be clear from my side. The solution what LG guy gave sounded like I have no idea, lets replace the entire thing. Which i am pretty sure is not the correct method.
What my phone can do at this moment is:
1. boot into bootloader.
2. Communicate with the PC using Fastboot.
I know Nexus 4 is a developer phone and easy to recover from brick status due to its intended purpose. Please advise what else can I do to revive my Nexus 4 and let me know in case I haven't done any thing which can restore this thing back to normal.
Thanks and Cheers,
Sid
siddhu2411 said:
Hey Guys,
I am facing a very strange issue with my N4. On Friday Night, I kept my phone for charging overnight and it was working as usual. on Saturday morning, I noticed that the phone was unresponsive and was showing a blinking red light. Tried to charge via various means but it was of no use. Finally went to a LG service centre were they could revive the phone but it was stuck in a bootloop. He suggested me that he will downgrade from KK 4.4.2 to JB 4.3 but still the phone was stuck in bootloop.
LG guy said that he doesn't have answer why this is happening. He said change the motherboard that will fix it. That is a very costly option which I cannot take. and he mentioned that there are tools online which will help it work but as an authorized service centre place he can't do it.
So here's what I did after reading several blogs, videos and but got stuck in the same place.
1. Booted in Bootloader mode, flashed stock JB 4.3 using Wugfresh Nexus Toolkit selecting the option Softbrick / Phone in bootloop.- Result : Stuck at Bootloop.
2. Flashed CWM Touch via fastboot, Went to the CWM recovery, Cleared the dalvik cache, Data, User data, Cache, Reflashed a Stock JB 4.3 - Result : Stuck at Bootloop.
3. Flashed KK 4.4.2 , again using the Wugfresh Nexus Toolkit - Result : Stuck at Bootloop.
I tried searching google for bootloops due to motherboard issues just to be clear from my side. The solution what LG guy gave sounded like I have no idea, lets replace the entire thing. Which i am pretty sure is not the correct method.
What my phone can do at this moment is:
1. boot into bootloader.
2. Communicate with the PC using Fastboot.
I know Nexus 4 is a developer phone and easy to recover from brick status due to its intended purpose. Please advise what else can I do to revive my Nexus 4 and let me know in case I haven't done any thing which can restore this thing back to normal.
Thanks and Cheers,
Sid
Click to expand...
Click to collapse
Try not using a toolkit, and doing it manually instead:
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
abaaaabbbb63 said:
Try not using a toolkit, and doing it manually instead:
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
Thank you abaaaabbbb63, I did find that post and performed the steps and now i can boot into android JB 4.2.2
But here's the thing the battery icon is showing an exclamation mark and mentioning that it is not charging. and second it seems that i am not receiving any mobile signal.
Could this mean my battery is faulty and replacing it may allow me to use the mobile signal.
siddhu2411 said:
Thank you abaaaabbbb63, I did find that post and performed the steps and now i can boot into android JB 4.2.2
But here's the thing the battery icon is showing an exclamation mark and mentioning that it is not charging. and second it seems that i am not receiving any mobile signal.
Could this mean my battery is faulty and replacing it may allow me to use the mobile signal.
Click to expand...
Click to collapse
Flash the KitKat factory image. That might solve the mobile signal issue.
The battery one, if not solved my the kitkat image, might be a hardware fault.
abaaaabbbb63 said:
Flash the KitKat factory image. That might solve the mobile signal issue.
The battery one, if not solved my the kitkat image, might be a hardware fault.
Click to expand...
Click to collapse
So chances that the Motherboard is screwed?
siddhu2411 said:
So chances that the Motherboard is screwed?
Click to expand...
Click to collapse
Or the battery itself. If the motherboard was busted, then the phone wouldn't have booted.
siddhu2411 said:
Thank you abaaaabbbb63, I did find that post and performed the steps and now i can boot into android JB 4.2.2
But here's the thing the battery icon is showing an exclamation mark and mentioning that it is not charging. and second it seems that i am not receiving any mobile signal.
Could this mean my battery is faulty and replacing it may allow me to use the mobile signal.
Click to expand...
Click to collapse
Did you get this fixed? Were you able to upgrade beyond 4.2.2?
My Nexus is currently bootlooping if I try and upgrade beyond 4.2.2 - though my battery seems fine. I'm wondering if there's some similar problem though.
Hi folks,
I'm having some issues with my Nexus 7 as it's stuck in a boot loop on KitKat. It's still under warranty and it's unrooted. I'm at the point of sending it back but I just wanted to check if there were any suggestions coming from helpful folks around here. It's only a couple of months old but it's a refurbished device that I got on the cheap.
A factory reset with only the default Google apps on it still initiates the boot loop. However when I manage to restart it in safe mode it seems to be stable. I've read some account of battery connections being the cause but if this was the case then I would think that it would still restart in safe mode.
So if there anything else I can try or should I just go ahead and return it?
Better go for a replacement...
Sent from my SM-N9005
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
Last week I was minding my own business, doing usual stuff on my phone and the device spontaneously rebooted into a bootloop at the Google logo. So I think "OK, no problem... I can try wiping cache/dalvik or at worst I have a recent nandroid backup" and proceed to reboot into recovery... except that it still hangs on the Google logo. Stuck at work I did a bunch of googling and found one other user who had the same thing happen recently.
When I got home I tried to fastboot flash TWRP again... but alas was still stuck at the Google logo. Next was a full flash of Google stock images, but that did nothing either... so I relocked the bootloader and had my provider (TELUS) send it in for warranty repair. I just had it returned with the repair stating the main board was replaced.
I have noticed a few users posting about being stuck on the Google logo and this concerns me a bit, as it almost seems like there may be some inherent hardware flaw causing the issue.
So I'm throwing the questions out there: Has anyone else had similar problems and is this something we should start to be concerned with?
You're not alone buddy. I'm in the same boat. Have sent mine for repair yesterday.
Thats discouraging news. How long have you guys owned the phone? Did you buy it new?
I love my 6p but if enough of these units are defective they should probably be recalled. Hard to gauge if its an anomaly or a serious issue. Hope for the former...
I think I may have the same problem. My phone wont boot past the logo at all. IDK what to do at all.
I have the same problem, stuck on the google logo, I already wiped the cache partition and nothing, did a factory reset and nothing, what else can I do??
KLit75 said:
Thats discouraging news. How long have you guys owned the phone? Did you buy it new?
I love my 6p but if enough of these units are defective they should probably be recalled. Hard to gauge if its an anomaly or a serious issue. Hope for the former...
Click to expand...
Click to collapse
7 months...
Sent from my Nexus 4 using Tapatalk
---------- Post added at 09:51 AM ---------- Previous post was at 09:48 AM ----------
hgil said:
I have the same problem, stuck on the google logo, I already wiped the cache partition and nothing, did a factory reset and nothing, what else can I do??
Click to expand...
Click to collapse
Check if you can boot twrp. If you're not successful send the phone for repair. No option available to recover from this king of hard brick yet.
Weird thing is anything and everything is doable in fastboot. Moment you try to boot OS or recovery, gets stuck indefinitely in Google logo and reboot.
Sent from my Nexus 4 using Tapatalk
this exact thing literally just happened to me on Thursday. I was fully stock never unlocked the bootloader or anything. phone suddenly started looping, tried wiping cache, doing factory reset, finally went nuclear and unlocked the bootloader and flashed system images. nothing worked. warranty replacement is enroute.
I bought it on release day.
Old issue with Nexus devices. Has been going on since Nexus 5
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
I got the phone new from TELUS at the end of December, so about 6mo before I had the issue... Thankfully fastboot still worked so I could return to stock and relock the bootloader before warranty claim...
Starting to wish I had done the insurance option if these things are failing after 6mo and I'm on a 2yr contract
sunseb said:
I got the phone new from TELUS at the end of December, so about 6mo before I had the issue... Thankfully fastboot still worked so I could return to stock and relock the bootloader before warranty claim...
Starting to wish I had done the insurance option if these things are failing after 6mo and I'm on a 2yr contract
Click to expand...
Click to collapse
Did they give a new/refurb or was it they changed motherboard/memory chip?
Sent from my Nexus 4 using Tapatalk
Was my original exterior, the dings were still on the corners so it was just motherboard replacement
sunseb said:
Was my original exterior, the dings were still on the corners so it was just motherboard replacement
Click to expand...
Click to collapse
Thanks. Just was curious on what I could expect.
Sent from my Nexus 4 using Tapatalk
I'm also having this issue, but I get stuck at the boot animation instead.
I have Nexus 6P, Stock Android 6.0.1 July, SuperSu v2.74, franco kernel r23, Xposed v85. Everything was running fine when suddenly the phone rebooted and got stuck in boot. I reboot into recovery, deleted the /data/data/de.robv.android.xposed.installer/conf/modules.xml, flashed xposed unistaller zip, cleared cache and rebooted. Still stuck in boot. I reboot into bootloader, flash boot, system, vendor image of July factory image and reboot. Still get stuck at boot. This is happening for the third time to me. Happened in May, in June and now in July. Only thing that works is restoring a nandroid and then again flashing the latest factory image. But that way, I lose days / weeks of data, depending on when that last nandroid was created.
That really sucks, but doesn't sound like a hardware failure from my understanding... I lost ALL my data when I had to send it in, since my failure resulted in no access to the internal memory... Lost a few pictures which was a real bummer, but lesson learned and now I'll be backing up my memory more frequently and also setting up cloud backup for photos
bagarwa said:
I'm also having this issue, but I get stuck at the boot animation instead.
I have Nexus 6P, Stock Android 6.0.1 July, SuperSu v2.74, franco kernel r23, Xposed v85. Everything was running fine when suddenly the phone rebooted and got stuck in boot. I reboot into recovery, deleted the /data/data/de.robv.android.xposed.installer/conf/modules.xml, flashed xposed unistaller zip, cleared cache and rebooted. Still stuck in boot. I reboot into bootloader, flash boot, system, vendor image of July factory image and reboot. Still get stuck at boot. This is happening for the third time to me. Happened in May, in June and now in July. Only thing that works is restoring a nandroid and then again flashing the latest factory image. But that way, I lose days / weeks of data, depending on when that last nandroid was created.
Click to expand...
Click to collapse
It's likely a software failure. When you flash via fastboot, do you reboot back to bootloader after flashing radio and bootloader? If not then that's likely what's causing the fast boot method to fail for you. The first time after I did a complete fastboot flash of the software I fell asleep and woke up in the morning to my 6p still at the boot screen. When I re-traced my steps I found out that my mistake was not properly rebooting after flashing radio image, then doing another reboot after flashing bootloader.
Got my device back. Same exterior. Was told that motherboard was changed. I could notice that from fastboot.
eMMC changed from Samsung to Toshiba
DRAM changed from Hynix to Samsung.
My device joins this list. Gonna send it for repair tomorrow and hoping it is covered under warranty.
Additional update. I know I missed the bigger scheme that changed. My IMEI.
Just curious what happens if I restore my previous efs partition backup after backing up current.
Sent from my Nexus 6P using Tapatalk
update: My phone came back in 5 days. Mainboard failure. Replaced in Warranty!! New IMEI!!
Sent from my AO5510 using Tapatalk
sunseb said:
Last week I was minding my own business, doing usual stuff on my phone and the device spontaneously rebooted into a bootloop at the Google logo. So I think "OK, no problem... I can try wiping cache/dalvik or at worst I have a recent nandroid backup" and proceed to reboot into recovery... except that it still hangs on the Google logo. Stuck at work I did a bunch of googling and found one other user who had the same thing happen recently.
When I got home I tried to fastboot flash TWRP again... but alas was still stuck at the Google logo. Next was a full flash of Google stock images, but that did nothing either... so I relocked the bootloader and had my provider (TELUS) send it in for warranty repair. I just had it returned with the repair stating the main board was replaced.
I have noticed a few users posting about being stuck on the Google logo and this concerns me a bit, as it almost seems like there may be some inherent hardware flaw causing the issue.
So I'm throwing the questions out there: Has anyone else had similar problems and is this something we should start to be concerned with?
Click to expand...
Click to collapse
my phone randomly locked up, then rebooted today. But when it rebooted it was stuck with the white google logo flashing. I can get into the bootloader mode, but from there, choosing recovery or anything else gets back into the white google bootloop. I called service and they're sending me a replacement. Phone was stock with a locked bootloader.
Hi.
I've had numerous nexus phones and generally dont have many issues however randomly today my phone entered a bootloop. I decided to completely flash stock firmware (how i normally solve issues but no matter what I do it just continues to bootloop.
I can get into Fastboot but thats it.
Any ideas or experience of this anyone?
Thanks in advance
Gave up in the end, couldn't fix it.
google replacing under warranty
Just had to do the same thing last week. Using Uber Partner app and when I accepted a "call" phone crashed and began bootlooping. Tried fastbooting stock image but ended with "Phone is Corrupt" message and continuous boot loop before replacing under warranty. I was running August update Benzo ROM. Never experienced anything like this before and I've been flashing for 5 years now. Sorry about your device, the new one in the mail will make it all better best phone ever!
Oh god... I think my device is doing the same thing.... I've tried flashing stock through fastboot twice now. Still saying my device is corrupt. Even tried a different cable, and redownloading the firmware.
Stretlow said:
Gave up in the end, couldn't fix it.
google replacing under warranty
Click to expand...
Click to collapse
This happened to me too the same day out of nowhere. Google sent me a refurb. Battery in this replacement seems much better. I couldn't even get into the recovery.
Sent from my Nexus 6P using Tapatalk