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.
Recently I just sent my phone to warranty for my S-pen,samsung changed my board and sorts things out.
When i got my Phone back i restored my twrp back up, nightmare happens afterthat,bootloop all the time apps force close,.systemui has stop. I tried flashing stock ROM,format my phone,wiping all data and cache and even my SD card.
I went back to samsung today and my warranty is over they checked thgs out and said that its my battery problem,should I get a new battery or is there anyway to sort my bootloop problems? I just got my phone for one year and i cant afford a new one. pls help out
Hi, thank you for using XDA Assist. I would flash your stock firmware with odin and then not restore your nandroid. I'm going to move your thread here, http://forum.xda-developers.com/galaxy-note-3/help where experts on your device can help you.
Good luck and welcome to XDA.
Hi,
I recently rooted my nexus 7 and flashed TWRP recovery. One day I got into the recovery and started playing with it. By mistake, I erased my OS. I then came to know to know that i could fix it by flashing a custom ROM. I installed a custom rom successfully. I then wanted to go to stock. While flashing the stock OS, it got stuck in bootloop. It was too late so I thought to flash it the next day. On the next day, when i tried to switch it on, it did not start. I kept it overnight for charging but it was of no use. Then i went to the Asus service center, and i came to know that there was a motherboard problem. I did a little research on google and came to know that to earn money they told it was a motherboard problem. Many people had fixed it by unplugging the battery and replugging it back. I tried that, but it was of no use. I did not play with the bootloader. But now I think that it could be hard bricked.But I am not sure. So any idea whether it is hard bricked or really is the motherboard spoiled or what??
Thanks in advance
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
so i been at my computer for HOURS and having major issues with TWRP not wonting to boot right, yes i am trying to install a later version of TWRP but everywhere i look a no go i even tried TWRP 3.4.0-1
so since everything has changed what is new out there, what are the new ways to get TWRP to work on this phone, what have i missed ever since i have been gone.
i re did the whole phone that i am back at stock vs99513A, no root nothing.
has anyone even rooted OREO 20C B or A if so where (no i didn't google cause after this post im getting off, tired of figuring out why TWRP sucks right now)
sorry to sound stressed, a lot has been going on and its been hard for me to get back into the game to help others, already sucks to see the method i did is so out of date and a lot has changed :'(