Upgraded to 7.1, next day phone restarted, boot loop at google logo. Able to get into fastboot power + down, none of the options are working, just keeps rebooting. Tried recover mode but just loops.
Tried fast boot, but unable to flash due to locked bootloader. I saw another thread with twp but not sure if im using this.
If it's bricked, time to get a new phone, or does google rma?
thanks for any help
The first thing you should do is unlock the bootloader, here is the guide its pretty simple.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Once ghe bootloader is unlocked i would suggest using the same guide to flash the factory image. That should fix ghe problem.
hassanabid94 said:
The first thing you should do is unlock the bootloader, here is the guide its pretty simple.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Once ghe bootloader is unlocked i would suggest using the same guide to flash the factory image. That should fix ghe problem.
Click to expand...
Click to collapse
Thanks, i've been trying to figure out how to unlock bootloader to get in, lets see if i can get it going, thanks !
hassanabid94 said:
The first thing you should do is unlock the bootloader, here is the guide its pretty simple.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Once ghe bootloader is unlocked i would suggest using the same guide to flash the factory image. That should fix ghe problem.
Click to expand...
Click to collapse
I can't unlock because i keep getting FAILED (remote: oem unlock is not allowed)
I can't get into dev mode to allow it to be unlocked.
Can you get in to the stock recovery Like once you ara at the bootloader screen use your volume down button to select recovery and then press power button to select ghe recovery option, once you are in hhe recobery try doing a factory reset/wipe user data and reboot, see if that helps
Ohhh man.... Sounds like the same symptoms a ton of other users had including myself.
I ended up doing an rma as nothing i tried worked. Just kept getting the warning screen and Google screen.
Good luck man
dadoc04 said:
Ohhh man.... Sounds like the same symptoms a ton of other users had including myself.
I ended up doing an rma as nothing i tried worked. Just kept getting the warning screen and Google screen.
Good luck man
Click to expand...
Click to collapse
rma?
srisurya95 said:
rma?
Click to expand...
Click to collapse
Warranty exchange
hassanabid94 said:
Can you get in to the stock recovery Like once you ara at the bootloader screen use your volume down button to select recovery and then press power button to select ghe recovery option, once you are in hhe recobery try doing a factory reset/wipe user data and reboot, see if that helps
Click to expand...
Click to collapse
Unfortunately not, everything just boot loops, only thing i can get is bar codes lol.
dadoc04 said:
Ohhh man.... Sounds like the same symptoms a ton of other users had including myself.
I ended up doing an rma as nothing i tried worked. Just kept getting the warning screen and Google screen.
Good luck man
Click to expand...
Click to collapse
I contacted google, wasn't sure if this was covered under warranty due to it being beta. I hope they do replace it, or I guess ill be getting pixel.
Related
I just got my Nexus one, but I cant start it it just keep rebooting when the four colord logo appears. I have tried to clear the storage but no luck. Really need som serious help here!
Thanks/ Viiddee
had the same problem. went back to recovery mode and used 'wipe' for all partitions (earlier i had done it only for the first on the list).
reinstalled CM from the SD card and all was well this time.
hope this helps you.
Yes krumbs is right you need to do a wipe upfront flashing the rom.
Without I also had the booting loop.
Maybe therefore in the installation instructions there's the point do a wipe ;-)
Sometimes we should read a little better, to prevent such problems.
Did you flash a rom? Or it's looping out of the box?
Carloswithac said:
Did you flash a rom? Or it's looping out of the box?
Click to expand...
Click to collapse
it looped out of the box.. and since i am new with android i need some help with this recovery wipe thing!? I got into fastboot mode and found recovery but when i did that i just got the android logo with a ! . And since it was like this out of the box I dont feel like try rooting it..
Oh didn't notice that you wrote that this booting loop is right out of box...
Let them change it, that's what I would do in that case.
yes it was.. the thing is that i live in sweden and it will cost me alot if i have to send it back.. so is there anything eles I can try? If I unlock the bootloader can reverse the unlock so that the warranty still works?
thanks in advance/ V
No, you can't relock the bootloader. Turn off the phone... restart by holding the volume down key. Scroll down to wipe/factory reset and hit power to confirm. Should reboot automatically. If this doesn't work, you have no choice but to get it replaced. HTC normally pays for the shipping... and since this is Dead on Arrival, they shouldn't have a problem sending you a new phone.
uansari1 said:
No, you can't relock the bootloader. Turn off the phone... restart by holding the volume down key. Scroll down to wipe/factory reset and hit power to confirm. Should reboot automatically. If this doesn't work, you have no choice but to get it replaced. HTC normally pays for the shipping... and since this is Dead on Arrival, they shouldn't have a problem sending you a new phone.
Click to expand...
Click to collapse
Ok. anyone having the experience of returning a nexus from any other country then UK or US?
/ V
Was having issues with my Nexus 7(2013) this morning, rebooted the device and now it gets stuck at the "Google" loading screen.
I can get into the Fastboot loader. I was able to unlock the bootloader.. I have LOCK STATE - unlocked and the unlocked lock showing up on the "Google" boot screen.
I am UNABLE to get into Recovery mode.. either by selecting "Recovery mode" in Fastboot or holding the power and vol up buttons. It just sits on the "Google" boot screen.
I have downloaded and installed the SkipSoft Android Toolkit(mskip).. very nice toolkit BTW. But no matter what I do I'm unable to start the tablet up normally or get into a Recovery mode of any kind.
I have tried to flash TWRP. I have tried to flash the stock ROM. Nothing, still sits at the Google boot screen. Since flashing the stock ROM its been 30 min and still just says "Google".
I'm open to any ideas or anything that you can think of.
Still have TWRP and fastboot access? If so, use the command line fastboot the img using
"fastboot boot <filename>.img"
Reply back; do you get to recovery?
Snuzzo said:
Still have TWRP and fastboot access? If so, use the command line fastboot the img using
"fastboot boot <filename>.img"
Reply back; do you get to recovery?
Click to expand...
Click to collapse
No.. I do not get into recovery of any kind. Stock or TWRP after loading it.. just sits at the Google screen.
Quick question; what were your partition setups like? F2fs? Ext4?
Snuzzo said:
Quick question; what were your partition setups like? F2fs? Ext4?
Click to expand...
Click to collapse
No idea.. it should be whatever it is stock. Before today I never rooted, flashed or did anything to this device.
FDokinawa said:
No idea.. it should be whatever it is stock. Before today I never rooted, flashed or did anything to this device.
Click to expand...
Click to collapse
Answers all of my questions. I know myself I won't be able to help. All I can say is to try relocking and then unlocking again.
Snuzzo said:
Answers all of my questions. I know myself I won't be able to help. All I can say is to try relocking and then unlocking again.
Click to expand...
Click to collapse
Thanks for the help.. will give it a shot.
FDokinawa said:
Thanks for the help.. will give it a shot.
Click to expand...
Click to collapse
What that should do is wipe internal, could have some corruption there. Try doing the command line fastboot of the recovery.img again. Those are the only few things I can think of short from exercising your warranty.
Snuzzo said:
What that should do is wipe internal, could have some corruption there. Try doing the command line fastboot of the recovery.img again. Those are the only few things I can think of short from exercising your warranty.
Click to expand...
Click to collapse
Dont think I can use the warranty.. bought it used(1 hour old) from a friend for $100.. he got it and then decided he didnt like the aspect ratio. His loss, my gain. Until now.. lol
I'll keep hacking at it.. thanks again.
Anytime! You're welcome!
So the original issue I was having was that the screen was not responding to touches. Was unable to slide the unlock button on the screen.
I was able to "Boot to Custom/Stock Recovery without Permanently Flashing it" via SkipSoft Toolkit.. and had TWRP load up. But like before it was not responding to touches.
Starting to think this thing is totally borked.. =/
I'm able to get into TWRP now.. but sits on boot animation screen now. one step forward. Going to try and reload the stock ROM again and see if that helps.
That seemed to work.. at the Welcome screen.
So if anyone else runs into something like this..
Issues:
Flakey touch screen
Stuck on Google bootup screen
Eventually stuck boot loop animation
Get SkipSoft Android Toolkit, donate a couple bucks and keep flashing anything and everything you can. Sorry I can't give you a specific order that works. I would say try the 'ALLINONE'(#8) option first and then download and flash the stock ROM. I did several things in the toolkit a few times over and over. Hopefully I'm good now, if not I will update.
Have you tried reflashing recovery via fastboot?
Exact thing happend to my n4.
Sent from my N⁴ using Android Lollipop by @Sykopompus running Unleased kernel by @DeFcOni
Good evening XDA,
I've got a Nexus 6p (obviously), and can't get it to boot. Unfortunately, I don't know the exact history as to how it's in this state.
I've tried everything I can think of and read every guide/steps/forums I can find that relates to my situation.
I can get to the bootloader and issue Fastboot commands. I've got adb/fastoot/drivers installed via the sdk/platform tools, and drivers are up to date as far as I can tell.
-I'm using the OEM cable attached to my computer (Surface Pro3, Windows 10)
-I can unlock/re-lock the bootloader as I wish.
-I've tried WugFresh toolkit, flash factory + unroot. All completes, but phones continues to loop even after leaving it for an hour+.
-I've tried Heisenbergs guide for manually flashing stock google images via fastboot to no avail. Tried several different google images. Everything completes, but it still just loops.
-I can get all fastboot commands to complete with no errors, but the phone just simply bootloops at the google logo, or if I leave bootloader unlocked it loops with the orange triangle & google logo. I have left it looping for at least an hour+, but it doesn't finish:crying:
-Stock recovery or a fastboot flashed trwp recovery simply won't boot, it just goes to the google logo and loops, I don't get the dead android w/triangle. "Recovery" in the bootloader selections is RED, if that means anything. Tried fastboot commands to boot recovery, but just sends it to the google logo and loops.
-Adb commands don't work, only fastboot commands.
-During flashing a google stock image with fastboot, the only thing that stands out is "max download of ####### reached", or something similar, but it still completes.....?
Seems to me that I've got a true brick (first ), and just need to send it in for repair.
Any help would be greatly appreciated. TIA.
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
TnT_ said:
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
Click to expand...
Click to collapse
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Dhickory said:
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Click to expand...
Click to collapse
Does all the data in the bootloader look fine? The storage size etc?
TnT_ said:
Does all the data in the bootloader look fine? The storage size etc?
Click to expand...
Click to collapse
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Dhickory said:
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Click to expand...
Click to collapse
Usually with board failure - that I saw in other threads - there are missing fields. My phone had a little glitchyness after I accidentally flashed the userdata.img - which caused my 128gb to become 32gb, which I found amusing - Other than that, I don't know. I'm sure others would reply.
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Dhickory said:
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Click to expand...
Click to collapse
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Jammol said:
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the link, and I've been reading the "Let's figure out this brick together" thread. The link you posted requires ADB commands to work to fix the EFS partition, but I can only run fastboot commands. ADB nor Recovery work on my device. Still reading...
Woohoo! Huawei replaced the phone, no questions asked. I think the saving grace was being able to flash stock images, and relock the bootloader. May be helpful to anyone else in this situation that can only run fastboot commands, and no recovery.
A couple days ago, my volume buttons were not working so I thought a quick restart would fix it. But when I restarted it, it went into bootloader. Its stuck on the 'Restart bootloader' option and I can't select it with my power button nor can I select other options with my volume keys. I try and hold down the power button and it restarts into bootloader again. I booted into recovery and tried to restore it with a nandroid I made that had everything stock but that didn't work. I also did a factory reset, but every time I try to boot into system it goes to bootloader instead. The only problem I can think of was that I held my phone when my hands were wet so maybe water went inside? I'm tempted to get rice to get the water out but I want to be certain that this is the result of water damage. If it helps, I had TWRP and a very early version of Lineage OS on the device before it happened.
TheGentleShark said:
A couple days ago, my volume buttons were not working so I thought a quick restart would fix it. But when I restarted it, it went into bootloader. Its stuck on the 'Restart bootloader' option and I can't select it with my power button nor can I select other options with my volume keys. I try and hold down the power button and it restarts into bootloader again. I booted into recovery and tried to restore it with a nandroid I made that had everything stock but that didn't work. I also did a factory reset, but every time I try to boot into system it goes to bootloader instead. The only problem I can think of was that I held my phone when my hands were wet so maybe water went inside? I'm tempted to get rice to get the water out but I want to be certain that this is the result of water damage. If it helps, I had TWRP and a very early version of Lineage OS on the device before it happened.
Click to expand...
Click to collapse
Hi... How did you manage to boot into recovery without the volume rocker?
Have you tried a simple:
fastboot format cache
fastboot format userdata
fastboot reboot
From bootloader?
Is your bootloader unlocked? If yes, try loading a factory image from Google if none of the above work.
5.1 said:
Hi... How did you manage to boot into recovery without the volume rocker?
Have you tried a simple:
fastboot format cache
fastboot format userdata
fastboot reboot
From bootloader?
Is your bootloader unlocked? If yes, try loading a factory image from Google if none of the above work.
Click to expand...
Click to collapse
I used 'fastboot boot recovery.img' to get to recovery. I tried to format the cache and userdata again, but still didn't normally boot. I also tried flashing the stock images from Google's website but still it won't boot.
TheGentleShark said:
I used 'fastboot boot recovery.img' to get to recovery. I tried to format the cache and userdata again, but still didn't normally boot. I also tried flashing the stock images from Google's website but still it won't boot.
Click to expand...
Click to collapse
I never seen this before. If you type fastboot reboot, it reboots directly into bootloader, right? I first thought avout the bootloop issue many currently report. But if you can boot a recovery.img or if your phone only reboot into bootloader, I think this scenario can be excluded.
Hmm you said you touched you phone with your hand wet?!
Could it be the moisture that oxidized the volume down contact inside of the phone? I don't have another idea. Wait for other people to chime in. Hopefully it's another (easy to solve) issue which I am unaware of.
Good luck.
5.1 said:
I never seen this before. If you type fastboot reboot, it reboots directly into bootloader, right? I first thought avout the bootloop issue many currently report. But if you can boot a recovery.img or if your phone only reboot into bootloader, I think this scenario can be excluded.
Hmm you said you touched you phone with your hand wet?!
Could it be the moisture that oxidized the volume down contact inside of the phone? I don't have another idea. Wait for other people to chime in. Hopefully it's another (easy to solve) issue which I am unaware of.
Good luck.
Click to expand...
Click to collapse
Ah well. Thanks anyways.
TheGentleShark said:
Ah well. Thanks anyways.
Click to expand...
Click to collapse
Did factory image flash without error?
Last try: did you try pressing power button till it reboots?
Good luck...
5.1 said:
Did factory image flash without error?
Last try: did you try pressing power button till it reboots?
Good luck...
Click to expand...
Click to collapse
No error came up when I flashed it and holding power button at bootloader restarts the phone back into bootloader. I might just stick it into some rice and use my old Nexus for now unless another solution presents itself.
Hi TheGentleShark, did you manage to resolve this? Stuck in a similar situation
WRDD said:
Hi TheGentleShark, did you manage to resolve this? Stuck in a similar situation
Click to expand...
Click to collapse
Hi. In order to get the attention of @TheGentleShark you should either reply directly to one of his posts, or put an ampersand in front of his name so he gets a notification. Otherwise he will never know (or see) your question. Hopefully he has some useful feedback for you.
WRDD said:
Hi TheGentleShark, did you manage to resolve this? Stuck in a similar situation
Click to expand...
Click to collapse
Sorry for late reply, but I did manage to get if fixed. I sent it back to my phone company to get fixed since it was still under warranty (even though its rooted with unlocked bootloader). Though, they didn't really tell me what went wrong. I assumed it was a hardware problem (a piece of rice was stuck in the speaker hole and was impossible to remove but was gone when I got the phone back).
hi guys,
so the nexus 6p i had got the oreo ota update and after a couple of day it restarted and since then stuck on google logo(bootloop).
it only goes to fastboot mode,
download mode is disabled,
recovery is not there of any kind, meaning i cant boot to recovery mode.
every things gone on it can i do something to get it back, oem unlocking was not turned on in it. developer option was never turned on. bootloader is also locked.
i am in a big trouble guys please help me if there is a way.
alijaved154 said:
hi guys,
so the nexus 6p i had got the oreo ota update and after a couple of day it restarted and since then stuck on google logo(bootloop).
it only goes to fastboot mode,
download mode is disabled,
recovery is not there of any kind, meaning i cant boot to recovery mode.
every things gone on it can i do something to get it back, oem unlocking was not turned on in it. developer option was never turned on. bootloader is also locked.
i am in a big trouble guys please help me if there is a way.
Click to expand...
Click to collapse
Tried factory reset and reboot?
tropical cactus said:
Tried factory reset and reboot?
Click to expand...
Click to collapse
as i mentioned there is no recovery mode on it. its red and i cant boot to it. it returns back to fast boot mode dude
alijaved154 said:
as i mentioned there is no recovery mode on it. its red and i cant boot to it. it returns back to fast boot mode dude
Click to expand...
Click to collapse
You can select factory reset by pressing the volume button . Factory reset will come up. Select by pressing power button and press again to wipe.
tropical cactus said:
You can select factory reset by pressing the volume button . Factory reset will come up. Select and wipe.
Click to expand...
Click to collapse
in fastboot only the options are:
start
barcodes
recovery
bootloader
alijaved154 said:
in fastboot only the options are:
start
barcodes
recovery
bootloader
Click to expand...
Click to collapse
I have factory reset as an option. Not sure why you don't.
tropical cactus said:
I have factory reset as an option. Not sure why you don't.
Click to expand...
Click to collapse
in fastboot? i dont have it i dont know what hapoened to it
alijaved154 said:
in fastboot? i dont have it i dont know what hapoened to it
Click to expand...
Click to collapse
Try reboot bootloader and scroll through options again.
tropical cactus said:
Try reboot bootloader and scroll through options again.
Click to expand...
Click to collapse
comes back to the same screen but will still try today
alijaved154 said:
comes back to the same screen but will still try today
Click to expand...
Click to collapse
Very strange, unless it only shows up if you enable developer options before.
Same problem after update
Exactly same problem after update, no way to factory reset phone, developer option was unlocked
Erroras said:
Exactly same problem after update, no way to factory reset phone, developer option was unlocked
Click to expand...
Click to collapse
you are not alone...?
Same issue on one I have my hands on. This could get interesting.
From fastboot can anything be pushed/flashed like a previous actually functional firmware? Is there other specific software to do so? Only got my hands on the defective non functional device today but I'm planning and scheming a fix if possible.
One thing is really interesting. Why only after this update???? Why not after update from 6 to 7 then 7 to 7.1 and after 7.1 to 8.0. I think Google or Huawei is cheating us and forcing us to buy Google pixel.
I also have this issue (I'm using a nexus 5x, but this thread is the closest to my issue I've found), but it came incrementally. First, I started getting reboots every 20m or so, while doing normal phone things (reading, mostly). Then it started getting into bootloops that were 2-3 boots long, and would then work normally for the 20m mentioned above. I tried a factory reset, but it just got worse, and now either reboots on the Google logo or during the Android animation. My fastboot menu only has the regular "Start" as green. The only other options are Restart Bootloader, in red, and Recovery mode, also in red. Power off is there, obviously, but that's it. It started happening yesterday, and worsened to its current point within only a few hours.
Well. I have just joined the club. What is going on with that?
Happened to me today and I was using the latest build of SuperXE 6P.
Guys! lol
1. Dev options in ROM is same old. Settings/about and tap build 10 times to see count down to developer. Back to settings. In there for OEM unlock
2. Factory reset can be done any number of ways.
a. In ROM. Settings/backup and reset/factory reset.
b. From anywhere, hold power+volume down until you see the bootloader. There are 2 possible screens in there. One of them has factory reset. Beware! From here it will likely wipe your sdcard!
c. From recovery. You can get there from bootloader. You can also flash an up to date recovery image from bootloader.
The rest of your recovery process should be provided by the ROM thread by which you will get your choice of ROM.
Make sure you have access to a PC with adb. You will likely need to flash a vendor image
My device is only recognized in fastboot mode. No ADB, no recovery. Tried to uninstall and manually install latest USB drivers, it didn't work. My Nexus is now just stucked in a bootloop. I even tried to flash factory images to no avail. Really don't know what to do...
FYI I have no screen in bootloader allowing me to factory reset: only Start/Reboot/Reboot bootloader/Barcodes, as others stated above.