hi i rooted my nexus 6p a couple hours ago and everything went fine. i'm am running the latest android 7.0 through the beta program. i was looking a different apps to see what i could do now. so i downloaded layers and a few overlays. i was trying different overlays. the first 2 reboots went fine then i tried a third. this time the reboot never finished. i can boot into to fastboot made but that's it. i try a rebooted from there and doing a factory reset in the recovery mode, but nothing is working, i'm still stuck in a boot loop. PLEASE HELP ME. i am new to all this and i went from being extremely excited to really sad.
debbymc28 said:
hi i rooted my nexus 6p a couple hours ago and everything went fine. i'm am running the latest android 7.0 through the beta program. i was looking a different apps to see what i could do now. so i downloaded layers and a few overlays. i was trying different overlays. the first 2 reboots went fine then i tried a third. this time the reboot never finished. i can boot into to fastboot made but that's it. i try a rebooted from there and doing a factory reset in the recovery mode, but nothing is working, i'm still stuck in a boot loop. PLEASE HELP ME. i am new to all this and i went from being extremely excited to really sad.[/QUOTE
Exactly same here, I cannot boot to recovery mode or anything. Its either switched off or just shows google on screen.
Click to expand...
Click to collapse
It's an ongoing thing.
Try here: http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page4
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.
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.
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.
So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt