So i rebooted my phone today, because screen didn't shut of when in call, but after reboot, phone is stuck at 4 color dots. I tried all bunch of stuff, but to summarize, i did wipe everything with fastboot and flashed stock 4.4.2 and 4.4.0 with fastboot/toolkit/flash-all.bat....and while every flash seems to finish ok, i still can't boot device (i waited 30 minutes on 4 color dots)
Any idea what the problem could be?
tnx
teva said:
So i rebooted my phone today, because screen didn't shut of when in call, but after reboot, phone is stuck at 4 color dots. I tried all bunch of stuff, but to summarize, i did wipe everything with fastboot and flashed stock 4.4.2 and 4.4.0 with fastboot/toolkit/flash-all.bat....and while every flash seems to finish ok, i still can't boot device (i waited 30 minutes on 4 color dots)
Any idea what the problem could be?
tnx
Click to expand...
Click to collapse
When you said you wiped everything, did that include the system partition as well?
Sent from my Nexus 7 (2013)
Yes...everything cleared, with toolkit and manually with fastboot.
Funny thing...i just tried flashing stock 4.2.2 and everything went ok. Phone booted to OS and after some poking around i did OTA to 4.3. Now, i'm stuck again at X boot screen. I read some users have this problem, but i just don't understand why this happens on "empty/cleared" phone.
Try to mess arround with some app that changes screen values, like brightness, saturation, etc. Fauxclock has this feature and supports presets, such as Franco.kernel app.
I know one member that could run 4.2.2 but nothing higher because his imei was blank. Does your phone have a valid imei #?
teva said:
Yes...everything cleared, with toolkit and manually with fastboot.
Funny thing...i just tried flashing stock 4.2.2 and everything went ok. Phone booted to OS and after some poking around i did OTA to 4.3. Now, i'm stuck again at X boot screen. I read some users have this problem, but i just don't understand why this happens on "empty/cleared" phone.
Click to expand...
Click to collapse
Sounds a lot like the same problem I'm having here...
http://forum.xda-developers.com/showthread.php?t=2590357
teva said:
So i rebooted my phone today, because screen didn't shut of when in call, but after reboot, phone is stuck at 4 color dots. I tried all bunch of stuff, but to summarize, i did wipe everything with fastboot and flashed stock 4.4.2 and 4.4.0 with fastboot/toolkit/flash-all.bat....and while every flash seems to finish ok, i still can't boot device (i waited 30 minutes on 4 color dots)
Any idea what the problem could be?
tnx
Click to expand...
Click to collapse
When I flashed 4.3, I couldn't get past the "X" boot screen. I wiped cache using recovery, it worked for me.
Try this guide
http://forum.xda-developers.com/showthread.php?t=2010312
Related
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
thebullfrog said:
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
Click to expand...
Click to collapse
You might try and flash the stock kernel which should not allow any under/over clocking or under/over volting. Otherwise flash back to stock using the manual way here http://forum.xda-developers.com/showthread.php?t=1907796 or download the Nexus 7 toolkit and use it to do the same.
Try WugFresh's Nexus Root Toolkit. It has an option to go back to stock if you're soft-bricked.
Well I just did a factory restore/wipe (because Im SO looking forward to setting everything up again...) and it made zero difference. I'll try the stock kernel if someone could point me in the right direction to find a copy of it.
NVM found it. I'll give it a shot.
Ummmm okay then. I had my N7 turned off while looking for a solution to this fiasco. I picked it up so I could flash the stock kernel, and it had turned itself back on. Not only that, but it was fully booted up. Granted it's back to the initial setup after doing a factory restore, but there we go. It automagically fixed itself. Now to spend a couple hours putting everything back how it was. Yay.
Protip children: Always. Be. Nandroiding.
I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????
contactfornitish said:
I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????
Click to expand...
Click to collapse
doing a system wipe (factory reset) when you update from 4.2 tp 4.3..? also just reminding you 4.3 based roms need new radio and bootloader update.. but that radio also works with 4.2..
Same problem
contactfornitish said:
I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????
Click to expand...
Click to collapse
I am having the same problem, it sucks
the radio doesnt work, i think, because the IMEI is unknown, well at least on my N4
Antonio0 said:
I am having the same problem, it sucks
the radio doesnt work, i think, because the IMEI is unknown, well at least on my N4
Click to expand...
Click to collapse
You are doing something wrong, its pretty hard to brick a nexus. What recovery do you have installed? have you tried using ADB or even a toolkit?
i dont think i have a solution
smoka206 said:
You are doing something wrong, its pretty hard to brick a nexus. What recovery do you have installed? have you tried using ADB or even a toolkit?
Click to expand...
Click to collapse
So I've heard that its hard to brick, but my phone isn't bricked, far from it, because I can use it it boots and everything (I'm on 4.2.2) and I'm replying to you from it now, but I'm on my homes WiFi because the phone doesn't read my Sim card, or at least that what I initially thought, but after some research I found out that its my lack of IMEI that's causing the problem. Even when I go into settings and about phone and look in there, both baseband and IMEI say "unknown" but when I boot into fastboot its a all there.
Regarding your question about adb and toolkits and my recovery
1.) I've tried adb as well as fast boot and wugfreshes toolkit to try and solve the problem
2.)I am completely stock 4.2.2, and that includes the recovery.
PS I used to be rooted and that was it, but after I had gotten stuck in a bootloop I flashed 4.2.2 and that got the phone out of Tue loop but now the IMEI and baseband is 'unknown' rendering my phone essentially an iPod type of device
Antonio0 said:
So I've heard that its hard to brick, but my phone isn't bricked, far from it, because I can use it it boots and everything (I'm on 4.2.2) and I'm replying to you from it now, but I'm on my homes WiFi because the phone doesn't read my Sim card, or at least that what I initially thought, but after some research I found out that its my lack of IMEI that's causing the problem. Even when I go into settings and about phone and look in there, both baseband and IMEI say "unknown" but when I boot into fastboot its a all there.
Regarding your question about adb and toolkits and my recovery
1.) I've tried adb as well as fast boot and wugfreshes toolkit to try and solve the problem
2.)I am completely stock 4.2.2, and that includes the recovery.
PS I used to be rooted and that was it, but after I had gotten stuck in a bootloop I flashed 4.2.2 and that got the phone out of Tue loop but now the IMEI and baseband is 'unknown' rendering my phone essentially an iPod type of device
Click to expand...
Click to collapse
i have the same problem too.. can someone help please??
try this http://forum.xda-developers.com/showthread.php?t=2347060
http://forum.xda-developers.com/showthread.php?t=2453364
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.
Hello,
I appreciate there are a huge number of similar questions on this forum, but I have read a lot of them and cannot find a solution to the problem I have with my wife's Nexus 4. Hoping someone will be able to help...
Standard Nexus 4 8GB, running 4.3 OTA on Vodafone UK. Not rooted, unlocked, hacked or anything.
Yesterday it failed to make calls or pick up a network, so my wife shut it down and restarted it; since then it would not get past the X boot logo.
Tried the factory reset / cache wipe steps, many times to no avail.
Let the battery run down overnight, no change this morning.
Sideloaded the OTA from 4.3. to 4.4, accepted the code but would not boot, initially stuck at "Starting Apps" after optimising apps, then after reset stuck at 4.4 Circles logo.
Installed 4.4.2 via fastboot, after unlocked the bootloader, again installed OK but would not boot, as above.
Re-installed 4.3 via fastboot, as above, will not boot.
Now currently gone back to 4.4.2 factory image, still will not boot - sits on the circles boot logo for ever.
I am sure I have tried several different iterations to the above, the furthest I have got it "Starting Apps" screen, most common is X or Circles.
Anything else I can try before giving up?
Thanks in advance.
meepm33p said:
Hello,
I appreciate there are a huge number of similar questions on this forum, but I have read a lot of them and cannot find a solution to the problem I have with my wife's Nexus 4. Hoping someone will be able to help...
Standard Nexus 4 8GB, running 4.3 OTA on Vodafone UK. Not rooted, unlocked, hacked or anything.
Yesterday it failed to make calls or pick up a network, so my wife shut it down and restarted it; since then it would not get past the X boot logo.
Tried the factory reset / cache wipe steps, many times to no avail.
Let the battery run down overnight, no change this morning.
Sideloaded the OTA from 4.3. to 4.4, accepted the code but would not boot, initially stuck at "Starting Apps" after optimising apps, then after reset stuck at 4.4 Circles logo.
Installed 4.4.2 via fastboot, after unlocked the bootloader, again installed OK but would not boot, as above.
Re-installed 4.3 via fastboot, as above, will not boot.
Now currently gone back to 4.4.2 factory image, still will not boot - sits on the circles boot logo for ever.
I am sure I have tried several different iterations to the above, the furthest I have got it "Starting Apps" screen, most common is X or Circles.
Anything else I can try before giving up?
Thanks in advance.
Click to expand...
Click to collapse
Hmm heard of such issues in the past where nexus wont boot with 4.3 or 4.4 !! I dont know the exact reason of the problem but what I do know is a solution for the same !!
Download the Factory Image for 4.2 Jelly Bean and fastboot the same !! Mostly youll get back your phone in the working state albeit without being able to upgrade to 4.3 or 4.4 !! Have a good day ahead !! :good:
Hi,
Thanks for the reply - I have just reloaded 4.2.2 from scratch and it is working. I then tried the OTA 4.3 upgrade and it failed, as before "starting apps" for ever, reset never boots.
Returning to 4.2.2 worked again.
What is strange is that this handset worked with 4.3 for 3 or 4 weeks before the restart yesterday...
I also tried 4.3 with .48 radio but that still failed to boot.
Hopefully someone else has a clever idea or some information around how/why this occurs, as beyond there being an underlying hardware fault (all sensors seem with androsensor) it is not logical.
Thanks.
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.