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.
Related
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 XDA, just a long time stalker who has finally given up trying to find his solution on already posted items (I think 10 hours of trail and error means I'm not gonna catch what I'm failing to see...)
When I first got my galaxy s4 I downloaded KangaBean and it was on 4.2.2 I believe. Today I decided I should upgrade to 4.4.2 since I've only been hearing good things about it, and I wanted the slight updates that came with it.
Well, I have a AT&T s4, sgh-i337 that was on CWM 6 when I tried updating to another ROM, the first one I tried was GOOGLE EDITION 4.4.2 BY DANVDH. Did a wipe, cache, dalvik, format system, flashed it, flashed loki doki, said no to re-root/root fix prompt that followed, then I came to the yellow triangle, I thought that was odd, believed I missed something.
So, I downloaded TWRP 2.5.0.2 like the thread suggested, tried again, no luck. Then I tried Unoffical Carbon KitKat, which just caused the "Samsung Custom" logo to stay on indefinitely (I let it sit for 40 minutes before giving up.) After 2 failed ROMs, I tried KangaKat, updated version of KangaBean, so it should be just dandy right? Narp, same luck. This one boots, then reboots into recovery.
At this point I considered myself to be stupid in some way so obvious that I would die before I noticed it. So, then I just flashed the stock firmware thats like 2.5 gb through odin, re-rooted and installed CWM 6.0.4.4 LOKI'd and tried to flash KangaKat, being confident it would work this time, again I got boot to the logo and then reboot into recovery.
At this point I attempted the other 2 ROMs again, multiple times.
After some sobbing, I re-did the stock firmware, tried again, failed again.
My sadness turned into rage, I just destroyed one of my micro sd to usb-s because it was being annoying and I was annoyed, I took a picture and got over it.
I tried a 3rd time with the re-flashing stock firmware and tried with twrp again, no cigar.
Now, after MANY hours and MANY false hopes... I shall be using my blackberry and hoping to return to android soon, if somebody can help me figure out what I'm missing. Many thanks ahead!
Did you do lokidoki after?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Did you doa hard reboot clear the cache and davlik after it got stuck on the lock screen ? It seems odd that it would just not boot up at all. I was about to wonder if maybe it was the CM kernel bug that will keep it from booting past the initial screen but you tried aGE rom so...
Hello,
New to xda-developer forum, but was hoping I could get some help.
I have a Droid Razr M, that has had the boot loader unlocked, but not rooted anymore, after getting an update prior to kitkat. If I remember correctly I was able to get previous updates with no issues with the boot loader unlocked. Today I heard that kitkat was out for my device, so I went into settings to check for a system update and I was offered to update to 4.4.2 (Kitkat). So I went ahead and did it.
However, the problems lies now that It is stick in a boot loop, with the "WARNING BOOTLOADER UNLOCKED" message that I always got after unlocking it. I noticed after the update the boot was taking a really like time, but then I noticed it would **** off and god right back to that same message. Knew something wasn't right, Itll shut down and reboot the that screen multiple times. I first tried clearing the cache partition. Nothing. Tried resetting/wiping, that also didnt fix it.
Some help would be greatly appreciated here.
If you need more information I can try my best.
Thank you!
So I just flashed back to stock 4.0.4 ROM with RDS Lite. Trying the OTA Kitkat update again, and now its just stuck at a black screen. I had it plugged into the charger as it was updating so its not dead. I cannot get it to reboot.
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.
Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
MATTHEWLONG said:
Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
Click to expand...
Click to collapse
This has been an ongoing thing with the 6P and 5X, there are multiple threads on this bootlopop issue some recoverable, some not. Check this out see if it helps..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page5
Thanks for the support, I will take a look.
I've read too many threads about 7.1 and the beta program causing boot loops and bricks....this is ridiculous!
Do you have a nandroid on hand? If so, try restoring it and see if that works.
I have only boot looped twice with this phone. Each time I went into TWRP and did a full wipe (everything except internal storage). I completed the full wipe three times consecutively. After the third wipe I boot into fastboot and flash the latest stock images from Google. Reboot.
Let the phone sit for 10-15 minutes then boot back into fastboot to flash custom recovery (TWRP). Then boot into recovery to flash SuperSU. Reboot. Let phone sit for another fifteen before continuing with setup.
I know wiping the device three times probably doesn't do anything extra than wiping once before flashing but it's what I've always done and what's always worked for me.