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.
Related
TL;DR: I have flashed the stock 4.2.1 image through fastboot, and yet my n7 wifi still reboots continuously at the google screen with the little unlocked lock.
Background: I have had the device for about 3 months, no real problems with it before this. I was reading yesterday night and i fell asleep, and thus instead of being on my desk all night the device was under a blanket. When i woke up, I opened the cover and found it on the google screen with the lock. It was warm, but not incredibly so. I thought it was weird that it had rebooted and apparently frozen, but i held down the power to turn it off. when i turned it back on, it started the google screen, then went black, then started the google screen again. Seems like there may be some sort of a kernel issue that is keeping it from booting. The next thing i did was to go into recovery (had CWM at this point, and it was rooted as well but that's a moot point if i can't get into the system.) and i did a backup, then wiped data and did a restore from the backup that i had just made. after rebooting, it made it all the way into the system, and seemed ok. I set it down, and a few moments later it turned off and started doing the loopy google screen thing again. Next, I went into recovery and wiped data/factory reset, and tried to boot up. no luck, still looping. Next, i grabbed the 4.0 toolkit from the dev section and tried to flash the stock recovery from that, but it was proving troublesome so i just downloaded the image myself and fastbooted then replaced cwm with the stock recovery, wiped everything, and flashed the 4.2.1 image. that should have worked, from what i understand, but no, still being loopy. I re-wiped and flashed, tried 4.1.2 instead, that didn't work, and i re-did 4.2.1. after flashing 4.2.1 and then leaving it boot looping for a little while, i noticed that it sometimes made it into the boot animation and then the animation froze and it rebooted and looped more. after a few more tries, powering it off, leaving it for a few min, and powering it on again, it booted all the way to the welcome screen to pick a language and then froze. some number of loops later, it made it all the way to picking a wifi network and froze. I have yet to make it past that point. Thinking it may help, i fastbooted CWM onto the device, so i have a more capable recovery now. I am now going to look into pushing a non stock rom to the device to see if that will help at all.
Any ideas on what on earth could have caused this? Was it just that the device was a little warmer than usual for a while?
Any ideas on how i can fix this? Much appreciated!
Lastly, should i consider looking at sending it back to google? I didn't think there was anything wrong with the hardware, but i'm not sure.
Thanks!
Update: After leaving the system repeating it's loopy boot thing for about 45 min, it seems to have finally booted into the system, and has yet to reboot again. I have no idea why this happened in the first case, nor why this finally worked in the end, but so far it seems ok.
More: Ok, so it still seems to be looping a lot. I have no idea why still. I'm having trouble getting it to boot back into the system, so hopefully something helps fix this.
Ok, so a day later it seems to have settled down such that there's very little looping on the google logo screen any more; now it just tends to randomly reboot when in use. this is quite frustrating, but seems more similar to what others have reported to be the case with 4.2.1. oddly, i never had these reboot issues before it decided to fail the first time, so i'm not sure if this is just because ii'm on 4.2.1. I may look at flashing back to 4.1.2 and staying there, i suppose it can't hurt. does anyone else have any ideas as to what could be going on?
I've spent close to most a work day now searching for an answer but am stumped.
I'm on MDL.
Downloade and flashed latest version of Goldeneye. Works great. After a bit, went to reboot phone.
Phone stuck @ boot screen ("Samsung" w/ unlocked lock below).
pull battery, same screen.
Wipe/reflash - all is well. Then re-boot, and stuck at same screen.
I have tried restoring multiple Nandroids and loaded 2 differnet roms. All with same result.
Also tried wiping data and restoring ESF backup and restoring my first rooted stock backup.
Same issue. works great till I reboot. Obviously somehting isn't sticking.
Any ideas? I hope I gave enough info
what recovery are you using?
So I rooted my phone long ago when it was new just to get wifi teather which worked great and has been ever since. I never installed the AT&T update that it kept asking me to do because I did not want to lose root and the teather ability. I recently installed CWM Touch Req0very because I wanted to try a new ROM. This worked fine and I can get into CWM now. I completed a backup using CWM, thankfully. I then tried to load the LiquidSmooth ROM for this phone. Before doing so I used CWM to complete a factory reset, cache wipe, and dalvik cache. I then chose the LS zip file and it loaded and appeared to be successful. I then rebooted and got the Samsung unlock padlock image for a few seconds and then the screen went dark and the power LED turned blue. I let it sit for a few minutes but nothing changed. I pulled the battery and rebooted but got the same. I then went back into CWM and restored my backup which took my phone right back to where it was, very thankful for that. What did I do wrong and how can I get the ROM to install properly?
I tried to reinstall the ROM and when it booted it got further. It went past the LS splash screen and then started pulsing the LS ying yang type logo. It did this for about 10 minutes so I pulled the battery and tried again which it just repeated the same process. I pulled the battery and restored my backup again. Nothing seems to work as easily as the hours and hours of videos and pages I've researched. Why does this seem to work so easily for everyone else?
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
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.