Nexus 6 stuck - Google logo/Unlocked symbol - Nexus 6 Q&A, Help & Troubleshooting

Hi,
So I flashed a stock rom 6.0.1 from google website using a standard procedure, the device booted for the first time, signed in and set up. Then when I restarted the device, it is not stuck on google screen with bootloader unlocked.
Can anyone help me how to fix this?

SonyXperiaS said:
Hi,
So I flashed a stock rom 6.0.1 from google website using a standard procedure, the device booted for the first time, signed in and set up. Then when I restarted the device, it is not stuck on google screen with bootloader unlocked.
Can anyone help me how to fix this?
Click to expand...
Click to collapse
Old post, I'm guessing you've moved on, but...
What ROM was on the device before you flashed the 6.0? The boatloader updates with stock ROMs. I there is a 7 bootloader, it may interfere with the boot of a 6 ROM.
If you are unsure, you should always go with the newest stock release.

SonyXperiaS said:
Hi,
So I flashed a stock rom 6.0.1 from google website using a standard procedure, the device booted for the first time, signed in and set up. Then when I restarted the device, it is not stuck on google screen with bootloader unlocked.
Can anyone help me how to fix this?
Click to expand...
Click to collapse
I would try clearing the caches and/or userdata before manually installing the system partition again.
1.) Reboot to the bootloader. (reboot and press and hold the volume down button until booted)
2.) plug-in the usb cable
3.) Open your terminal and type:
Erase cache
Code:
fastboot erase cache
Erase dalvic-cache
Code:
fastboot erase dalvic-cache
Erase userdata
Code:
fastboot -w

Related

[Q] How do I fix this

I tried to install a Viper rom (the latest one) but it kept saying error and when I went back to reboot it said that my phone might be unrooted and there was a button that said FIX and a button that said No, reboot and another one that said go back. Through hesitation, I clicked go back on accident and it rebooted. I don't know why but it got stuck on bootloop. Now I stopped the boot loop by holding down the power button and the down volume key at the same time to go back to the bootloader. Now, my problem is, how can I fix everything? I can't boot back to recovery because it goes on a boot loop and I can't factory reset either. I tried using HTC One All in one toolkit but it doesn't recognize my device. It keeps saying "Error: device not found" but my phone clearly says Fastboot USB. I need help ASAP
MySlimey said:
I tried to install a Viper rom (the latest one) but it kept saying error and when I went back to reboot it said that my phone might be unrooted and there was a button that said FIX and a button that said No, reboot and another one that said go back. Through hesitation, I clicked go back on accident and it rebooted. I don't know why but it got stuck on bootloop. Now I stopped the boot loop by holding down the power button and the down volume key at the same time to go back to the bootloader. Now, my problem is, how can I fix everything? I can't boot back to recovery because it goes on a boot loop and I can't factory reset either. I tried using HTC One All in one toolkit but it doesn't recognize my device. It keeps saying "Error: device not found" but my phone clearly says Fastboot USB. I need help ASAP
Click to expand...
Click to collapse
First of all, don't use a toolkit. They rob you of the understanding you need to fix problems like this.
- You should be able to use fastboot to boot recovery. Can you?
- Did fastboot/USB connection ever work for you? How about adb?
- If you get fastboot working (drivers?), you can clear the cache with "fastboot format cache".
- If you can't boot recovery to do the other steps (factory reset and wiping the dalvik cache), you have bigger problems. But I think these steps CAN be done from the bootloader. Maybe not all of them--I'm not sure what will work and what won't, as far as various combinations of "fastboot erase dalvik / fastboot format userdata / fastboot erase userdata", etc.
- First, focus on booting recovery. Get fastboot working and clear the cache if you need to.
- Note that IF you can factory reset through fastboot (I'm not sure you can), it will wipe /sdcard as well.
adb doesn't recognize my device. I don't know why. I can't boot to recovery either.
Same problem
Hi mate i got the same problem as you
this is my thread
http://forum.xda-developers.com/showthread.php?t=2738505
I did the same thing like you.
Adb only works within a working os or in recovery.
If you PC is not recognizing fastboot/adb drivers, install them from here
http://koush.com/post/universal-adb-driver
and also read here
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Once setup enter bootloader
fastboot flash recovery your recovery.img
fastboot erase cache
fastboot reboot-bootloader
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
Adb only works within a working os or in recovery.
If you PC is not recognizing fastboot/adb drivers, install them from here
http://koush.com/post/universal-adb-driver
and also read here
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Once setup enter bootloader
fastboot flash recovery your recovery.img
fastboot erase cache
fastboot reboot-bootloader
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll try installing it and if it all works, you get a thanks from me
EDIT: THIS WORKED FOR ME. THANK YOU SO MUCH I CAN NOT THANK YOU ENOUGH <3 If anyone has this problem, do what this guy said
MySlimey said:
I'll try installing it and if it all works, you get a thanks from me
EDIT: THIS WORKED FOR ME. THANK YOU SO MUCH I CAN NOT THANK YOU ENOUGH <3 If anyone has this problem, do what this guy said
Click to expand...
Click to collapse
Your welcome. Glad you now have a working phone
Sent from my HTC One using XDA Premium 4 mobile app

[Q] Stuck on Bootloader and Google splash

So I seem to have made the mistake of formatting data - don't ask me why, I wasn't thinking. Now I cannot get past the bootloader or the Google splash screen. On Windows BTW.
Things I've attempted:
ADB and Fastboot - When I ran the command to unlock, it said I already was. :good:
CF's root - Rooted
Wug's toolkit - Tried returning back to stock img, but says ADB device was not found. Step 1 was to enable USB debugging, but I cannot boot into the ROM so that is a no-go. I am using the original OEM cord. I've tried using another USB port as well... nothing.
If I am missing something, please let me know. The drivers should be good to go since I upgraded them 2 days ago.
Update: Dowloaded TWRP and installed via Fastboot. Restarted bootloader, booted into recovery, and the TWRP splash screen popped up. Shortly after that, the Google screen came up and is hung.
I found this thread http://forum.xda-developers.com/nexus-6/help/help-nexus-6-stuck-bootloader-t2949817. When I type fastboot devices, it shows my device's serial number.
Are you sure you didn't delete data? Formatting should not cause that issue. You can flash the stock userdata.img back and stock boot.img
Sent from my Nexus 6 using XDA Free mobile app
or, while in twrp, adb push/sideload a rom(and gapps) to your phone and flash it in twrp recovery.

[Q] Nexus 6 Stock recovery issue

So I'm restoring my old Nexus 6 that is being sent back for RMA and I encountered an issue. I have flashed things so many times I should remember how to fix this, but I haven't encountered it since my Nexus 7. I flashed all of the images and wiped the userdata as per the usual order. Everything boots fine until I lock the BL. When I re-locked the BL and restart the phone it goes to wipe its self and encrypt. The issue is that the stock recovery which it boots into during this process just has a android with a hexagonal floating blue orb in his chest and sits there for what seems like indefinitely. Its been sitting like that for a hour or so now and when I check what its doing using the "hold power press and release vol up" it says formatting data. I also tried booting into the stock recovery via the BL menu and its doing the same thing. I tried both 5.0 and 5.01 images with the same result. The last time I did this I didn't encounter this issue. I just want to make sure it boots normally so I can send it back in. If I unlock the BL it boots just fine after I format userdata and cache, but it won't go past the above mentioned state when I lock it.
This is what I did as far as fastboot flashing goes (LRX21O) the 5.0 stock rom:
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot oem lock
fastboot reboot
I'll try to re-download both images to see if maybe something changed but its odd because I have done this so many times its second nature. I think the issue lies with the encryption because I was unencrypted before and maybe it just takes forever.
Edit: after 2+ hours of it sitting there the phone finally booted. I thought it would never go past that screen but I guess encryption just takes forever.
Pilz said:
So I'm restoring my old Nexus 6 that is being sent back for RMA and I encountered an issue. I have flashed things so many times I should remember how to fix this, but I haven't encountered it since my Nexus 7. I flashed all of the images and wiped the userdata as per the usual order. Everything boots fine until I lock the BL. When I re-locked the BL and restart the phone it goes to wipe its self and encrypt. The issue is that the stock recovery which it boots into during this process just has a android with a hexagonal floating blue orb in his chest and sits there for what seems like indefinitely. Its been sitting like that for a hour or so now and when I check what its doing using the "hold power press and release vol up" it says formatting data. I also tried booting into the stock recovery via the BL menu and its doing the same thing. I tried both 5.0 and 5.01 images with the same result. The last time I did this I didn't encounter this issue. I just want to make sure it boots normally so I can send it back in. If I unlock the BL it boots just fine after I format userdata and cache, but it won't go past the above mentioned state when I lock it.
This is what I did as far as fastboot flashing goes (LRX21O) the 5.0 stock rom:
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot oem lock
fastboot reboot
I'll try to re-download both images to see if maybe something changed but its odd because I have done this so many times its second nature. I think the issue lies with the encryption because I was unencrypted before and maybe it just takes forever.
Edit: after 2+ hours of it sitting there the phone finally booted. I thought it would never go past that screen but I guess encryption just takes forever.
Click to expand...
Click to collapse
After all of this, did you test the recovery? I've been having the same issue today, but my recovery still isn't coming up. Every time I try, I still get the dead android with the triangle in the belly, but I am booted up and running.

NO OS installed.... Cant mount

So im stuck with my nexus with no OS... after flashing pure shamu it booted to just a password box... I input my password and it said i had corrupt data. I hit reset... wiped phone... all files GONE... Now what do i do. I cant mount to put recovery on.... I cant do anyting with this phoen right now... anyone had this happen... If so what steps to remedy?
Sounds like you need to try and fastboot the original google files, nuke and repave....
flash the stock img then start again
Flashing stock as we speak... was hoping another optino.... but after years of doing this I kinda know better... live and learn
hell
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
asphalte7 said:
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
Click to expand...
Click to collapse
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Evolution_Freak said:
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
asphalte7 said:
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
Click to expand...
Click to collapse
Should be able to boot twrp now.
but i have to unlock first ... my device is locked
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
you cant unlock it without booting up and enabling allow oem unlocking in the developer options
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
If you can boot to TWRP recovery, then you can ADB push a ROM to recovery and boot it.
Edit: Sorry, I missed the fact that TWRP had been deleted too.
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Evolution_Freak said:
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Click to expand...
Click to collapse
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
Or, if you are still in fastboot, issue this command > fastboot reboot recovery
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
asphalte7 said:
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
Click to expand...
Click to collapse
Then I'm afraid you may be stuck. A RMA may be in your future if no one else can offer a solution.
simms22 said:
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
Click to expand...
Click to collapse
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
asphalte7 said:
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
Click to expand...
Click to collapse
flashing twrp..
fastboot flash recovery recoveryname.img
and flashing a factory img is done while the phone is in its bootloader. there are instruction how here on xda. but to be honest, i dont know if that will work. where did you buy your n6 from btw?

[Q] Boot loop after OTA update

I got a message saying that an update is availible and i tried to download and install it but it failed two different times so i gave up. Now after several power cycles due to normal use my razr i is stuck in a boot loop (static red moto symbol then boot animation with intel inside repeating).I got the phone into fastboot mode and then I downloaded and installed rsd-lite and all motorola drivers. 2 different computers that ive tried rsd lite does not detect the phone however fastboot does. Factory option just resumes the boot loop. I dont know how to procede from here?
Edit: Phone is locked bootloader unrooted
Okay i guess this thread can be left incase anyone else gets in my position. I was able to fix my phone as fastboot was able to detect. i simply typed
Code:
fastboot -w reboot
and it wiped my userdata and cache and allowed the phone to boot.
megamit said:
Okay i guess this thread can be left incase anyone else gets in my position. I was able to fix my phone as fastboot was able to detect. i simply typed
Code:
fastboot -w reboot
and it wiped my userdata and cache and allowed the phone to boot.
Click to expand...
Click to collapse
It really works!
Thank you!

Categories

Resources