Database Users

Please help! Nexus 10 stuck on google X during failed root :(

Hey guys
I tried the one-click root toolkit for mac from android rootz.
Something apparently has gone wrong during the root and I got some error messages and it didn't proceed. Next thing I know the nexus is stuck on google X logo and that's it. It won't load. I tried to recover through the recovery mode a couple of times but now I get the red warning sign when I go into recovery mode. This is only the second day I've had the nexus for. I feel like crying. Please Help

When the red sign appears press the volup down buttons and power button randomly until you get into recovery then factory reset

My 7 and 10 both did that. Just hold power until it turns off, then boot a recovery, wipe everything except system and reboot. It'll come up ok.
Sent from my Nexus 10 using Tapatalk HD

I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.

scooterbaga said:
I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.
Click to expand...
Click to collapse
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04

bg1906 said:
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04
Click to expand...
Click to collapse
Thanks for the info. My situation wasn't quite the same as my CWM was the real issue, which wouldn't run long enough to allow for the factory reset boot-loop solution. Kept at it and managed to get CWM to finish the individual formats/resets one at a time.
With a now bootable device, I'm off to replace the recovery... Thanks again.

[Q] Nexus 10 Bricked :/

Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.

Hyflex said:
Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.
Click to expand...
Click to collapse
Reboot holding Power and both volume buttons and you should be able to get to recovery

brees75 said:
Reboot holding Power and both volume buttons and you should be able to get to recovery
Click to expand...
Click to collapse
I'm on the xda-devs irc at the moment and we've got so far... but still its messed up.
- Recovery is dead (can't get into it atm, orange triangle guy every time)
- Flashed stock via fastboot and unrooted, but on reboot I get the triangle guy.
- I can boot into unsecure roms (temporary)
- I can boot into temporary recoverys, clearing cache works but davlik cache and factory reset doesn't work both say "failed"
I'm currently awaiting the guy whos been helping me get back from the shops.

From what I remember you need to either install something or run a command after "oem unlock" for security reasons. Android wont let you boot back into the OS until you have wiped all the data after the unlock.

The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD

Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!

altimax98 said:
The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
The pressing 3 buttons at once; cycling to recovery... method wasnt working because there was no recovery accessable what so ever and temporary recoveries weren't working.
That's what a few guys in IRC said too about the toolkits haha
Thankfully some guy by the name of YellowGTO spent some time helping me out and we finally got there in the end, he's awesome and extremely patient
jlvlawrence said:
Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!
Click to expand...
Click to collapse
Okay, updates for everyone just incase someone else gets the problem.
- Factory Images via fastboot flashed fine but never stuck, just kept returning me to triangle dude.
- Fix permissions, did nothing
- Restoring stock recovery did nothing, I still couldn't get to a recovery.
- Temporary recoveries only had limited functionality.
I decided to unlock an already unlocked phone again
I flashed stock, Ran file permissions
Used the temporary recovery to clear the cache/davlik (previously didn't work)
I re-rooted, Installed TWRP 2.4.4.0, this finally stuck.
I double checked that it had stuck by booting the system, rebooting into recovery, powering device of and powering it on to Android. It was all working perfectly.
I then made my backup and put a custom rom and kernel on, it's working lovely now.
It seems that somewhere during the oem unlock it messed up some partitions or something resulting in recoveries and flashing not to work/stick.

Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD

altimax98 said:
Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That's the thing, the recovery wasn't available in any way shape or form and temporary recoveries wouldn't wipe the cache... the oem unlock went wrong somehow even though it had full power, wasn't interrupted or anything.
I'm glad it's all working now, I thought the device was completely dead at one stage.

I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well

anazei said:
I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well
Click to expand...
Click to collapse
I think you are right and that was his problem..... The toolkit actually told him how to handle this ... but who reads all the that text anyway

[Q] Rooted Razr M stuck in Motorola Screen

My razr m was rooted and running the 4.1.1 system with Safe Strap installed. A few days ago, the 4.1.2 ota update came and of course, unrooted it. I re-rooted it using Motochopper and reinstalled Safe Strap. My trouble began when I flashed a custom ROM on the device. After booting back up after flashing the ROM, I checked the "about phone" in my settings and the device was back in 4.1.1. The device then upgraded again to 4.1.2. Immediately after this, I was stuck in a boot loop. I have tried RSD Lite, Droid Razr Utilities (both ICS & JB utilities) and I'm still stuck in the Red Motorola logo boot. It will boot into the red M logo, then I get the Safe Strap screen (I cannot activate it) then black screen. When I hold power & volume up & down it will simply go back to the red motorola screen.
Can anyone provide additional information as to what I should do next? I'm hoping the phone is not bricked.

estimator1960 said:
My razr m was rooted and running the 4.1.1 system with Safe Strap installed. A few days ago, the 4.1.2 ota update came and of course, unrooted it. I re-rooted it using Motochopper and reinstalled Safe Strap. My trouble began when I flashed a custom ROM on the device. After booting back up after flashing the ROM, I checked the "about phone" in my settings and the device was back in 4.1.1. The device then upgraded again to 4.1.2. Immediately after this, I was stuck in a boot loop. I have tried RSD Lite, Droid Razr Utilities (both ICS & JB utilities) and I'm still stuck in the Red Motorola logo boot. It will boot into the red M logo, then I get the Safe Strap screen (I cannot activate it) then black screen. When I hold power & volume up & down it will simply go back to the red motorola screen.
Can anyone provide additional information as to what I should do next? I'm hoping the phone is not bricked.
Click to expand...
Click to collapse
Can you get into ap fastboot?
Sent from my XT907 using Tapatalk 2
---------- Post added at 02:36 PM ---------- Previous post was at 02:32 PM ----------
Read this
http://forum.xda-developers.com/showthread.php?t=2260305
Sent from my XT907 using Tapatalk 2

brandon71 said:
Can you get into ap fastboot?
Sent from my XT907 using Tapatalk 2
---------- Post added at 02:36 PM ---------- Previous post was at 02:32 PM ----------
Read this
http://forum.xda-developers.com/showthread.php?t=2260305
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I can get into AP Fastboot. I get into Fastboot, plug into computer using the Motorola USB cable for my device. Load Droid Razr Utility 1.20 and followed instructions. I use choice #1 and I get a message saying, "Error, cannont read image" The device then reboots and goes back to the red Motorola logo. Could this be a Windows 7 issue? Should I try this on my laptop at home running Vista?

estimator1960 said:
Yes, I can get into AP Fastboot. I get into Fastboot, plug into computer using the Motorola USB cable for my device. Load Droid Razr Utility 1.20 and followed instructions. I use choice #1 and I get a message saying, "Error, cannont read image" The device then reboots and goes back to the red Motorola logo. Could this be a Windows 7 issue? Should I try this on my laptop at home running Vista?
Click to expand...
Click to collapse
You know, I had an issue like that using the 1.10 tool. I basically put the phone in fastboot, opened RSD lite from the 1.10 tool folder, picked the image I wanted (4.1.2 should also be in the tool folder), and then plugged in the phone. That process allowed me to flash.

Make sure your driver's are up to date and if your on the 4.1.1 kernel use 1.10 and if your on 4.1.2 use the 1.20 utility
Sent from my XT907 using Tapatalk 2

brandon71 said:
Make sure your driver's are up to date and if your on the 4.1.1 kernel use 1.10 and if your on 4.1.2 use the 1.20 utility
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
None of that worked. Drivers are up to date and I tried 1.20 utility. Fastbook screen says "battery ok" I tried opening RSD from the utility tool folder and flashing the VZ stock ROM...nothing seems to work.

estimator1960 said:
None of that worked. Drivers are up to date and I tried 1.20 utility. Fastbook screen says "battery ok" I tried opening RSD from the utility tool folder and flashing the VZ stock ROM...nothing seems to work.
Click to expand...
Click to collapse
I probably should've mentioned that this is a company phone and I've gotten my replacement Razr already. I would, however, like to erase this old device or do something to it so's Verizon wouldn't know what I done to it. Is this possible?

brandon71 said:
Make sure your driver's are up to date and if your on the 4.1.1 kernel use 1.10 and if your on 4.1.2 use the 1.20 utility
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Matt's Utility fixed it. The problem I was having was Windows 7. At work, my pc runs Windows 7 64. The utility would not work on that pc. Today is Saturday and I'm on my laptop at home running Vista. Matt's utility unbricked it and restored my boot image. I would like to thank you for helping me, Brandon.
Chris:good:

estimator1960 said:
Matt's Utility fixed it. The problem I was having was Windows 7. At work, my pc runs Windows 7 64. The utility would not work on that pc. Today is Saturday and I'm on my laptop at home running Vista. Matt's utility unbricked it and restored my boot image. I would like to thank you for helping me, Brandon.
Chris:good:
Click to expand...
Click to collapse
Np man but I'm using windows 7 64 bit and it works fine
Sent from my XT907 using Tapatalk 2

brandon71 said:
Np man but I'm using windows 7 64 bit and it works fine
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Hmmm...then I think the problem was that my work pc runs off of a company server and I do not have administrative priviledges. My work pc will not root my phone using Motochopper, either, but I re-rooted my device at home on the laptop with Motochopper.
At any rate, thanks again!

You can flash mannually, using fastboot, open the .xml file, you can see the command.
i.e: fastboot flash boot boot.img
like this, follow the order of the xml file, after all you flashed, you can reboot
estimator1960 said:
My razr m was rooted and running the 4.1.1 system with Safe Strap installed. A few days ago, the 4.1.2 ota update came and of course, unrooted it. I re-rooted it using Motochopper and reinstalled Safe Strap. My trouble began when I flashed a custom ROM on the device. After booting back up after flashing the ROM, I checked the "about phone" in my settings and the device was back in 4.1.1. The device then upgraded again to 4.1.2. Immediately after this, I was stuck in a boot loop. I have tried RSD Lite, Droid Razr Utilities (both ICS & JB utilities) and I'm still stuck in the Red Motorola logo boot. It will boot into the red M logo, then I get the Safe Strap screen (I cannot activate it) then black screen. When I hold power & volume up & down it will simply go back to the red motorola screen.
Can anyone provide additional information as to what I should do next? I'm hoping the phone is not bricked.
Click to expand...
Click to collapse

Same problem
estimator1960 said:
Hmmm...then I think the problem was that my work pc runs off of a company server and I do not have administrative priviledges. My work pc will not root my phone using Motochopper, either, but I re-rooted my device at home on the laptop with Motochopper.
At any rate, thanks again!
Click to expand...
Click to collapse
Hi, I am expriencing the same problem but I am not as exprienced as the original post. What is the next step one does after clicking the power button when I high light AP fastbboot( In my case it went back to moto logo and then the boot screen again)
Thanks

Ebiforever said:
Hi, I am expriencing the same problem but I am not as exprienced as the original post. What is the next step one does after clicking the power button when I high light AP fastbboot( In my case it went back to moto logo and then the boot screen again)
Thanks
Click to expand...
Click to collapse
It's tricky; you have to be really fast at it. Hold down the power button AND the Volume Up/Down at the same time until you see the boot screen. Scroll down to AP Fastboot and hit the Power button again...again...this has to all be down very quickly...and it took my several tries to get to this screen. I'm assuming you are stuck in a boot loop right? And you need to flash the stock ROM back?

estimator1960 said:
It's tricky; you have to be really fast at it. Hold down the power button AND the Volume Up/Down at the same time until you see the boot screen. Scroll down to AP Fastboot and hit the Power button again...again...this has to all be down very quickly...and it took my several tries to get to this screen. I'm assuming you are stuck in a boot loop right? And you need to flash the stock ROM back?
Click to expand...
Click to collapse
Actually, once you're in the fastboot menu and you've used volume down to choose the option you want, you just press volume up and it will boot into that option.

Re
estimator1960 said:
It's tricky; you have to be really fast at it. Hold down the power button AND the Volume Up/Down at the same time until you see the boot screen. Scroll down to AP Fastboot and hit the Power button again...again...this has to all be down very quickly...and it took my several tries to get to this screen. I'm assuming you are stuck in a boot loop right? And you need to flash the stock ROM back?
Click to expand...
Click to collapse
Hi, I was able to get the start up menu, i used the down key to slect the AP fastboot then pressed the power button but it restrted back to the boot loop. AM I doing some thing right and also what are the next steps after strating fast boot?
Thanks
---------- Post added at 01:18 PM ---------- Previous post was at 01:17 PM ----------
RikRong said:
Actually, once you're in the fastboot menu and you've used volume down to choose the option you want, you just press volume up and it will boot into that option.
Click to expand...
Click to collapse
So I do not press the power button when the AP fastboot is selected and instead I press the volume up button?

Ebiforever said:
Hi, I was able to get the start up menu, i used the down key to slect the AP fastboot then pressed the power button but it restrted back to the boot loop. AM I doing some thing right and also what are the next steps after strating fast boot?
Thanks
---------- Post added at 01:18 PM ---------- Previous post was at 01:17 PM ----------
So I do not press the power button when the AP fastboot is selected and instead I press the volume up button?
Click to expand...
Click to collapse
Yes, right! After you're in AP Fastboot, make sure sure it says, "Battery OK" you cannot run the utility with a drained battery. Here's the utility link for Razr M running JB 4.1.2.
http://forum.xda-developers.com/showthread.php?t=2249773
Once you're in AP Fastboot and it says, "Battery OK" then plug in your USB cable connecting your device with your PC. Follow directions listed in the link I posted.
Good luck!

Thanks
estimator1960 said:
Yes, right! After you're in AP Fastboot, make sure sure it says, "Battery OK" you cannot run the utility with a drained battery. Here's the utility link for Razr M running JB 4.1.2.
http://forum.xda-developers.com/showthread.php?t=2249773
Once you're in AP Fastboot and it says, "Battery OK" then plug in your USB cable connecting your device with your PC. Follow directions listed in the link I posted.
Good luck!
Click to expand...
Click to collapse
Hi, It worked like a charm, after I follow your steps it still didnt work, I just had to go back to the fast boot menu and go to factory reset. Everything is working now. Thanks

Need Help! Possible brick after flashing recovery.

Hi all, just got my Moto X Pure this morning. I received the update to Marshmallow and began using the toolkit to unlock the bootloader, flash the recovery, and finally flash SuperSU. Everything was fine until flashing SuperSU onto the device. Now my device stays in the infinite Motorola logo of death, and any attempt to enter fastboot or recovery fails.
I'll get the "Unlocked Bootloader" warning but never enter it, and any attempt at entering recovery will just loop back to either a black screen, the logo loop, or the warning message. Was able to do commands until this point, but now that the phone wont enter fastboot or recovery I can't even use the RTS tool or try manually restoring the phone. Have I just made my brand new device a paperweight?! :crying:

Press and hold Power /volume down with the cable not plugged in..... You doing that.
Sent from my XT1575 using Tapatalk

shoman94 said:
Press and hold Power /volume down with the cable not plugged in..... You doing that.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Yeah, that finally solved the issue by holding down power alone before the bootloader unlock screen, with the device not plugged in as you said, the entire device would be off for 2 seconds, which was enough time to finally enter the bootloader and apply the RTS tool's .bat file.
From there I made a Nandroid backup of stock in case another issue arises, but now I'm running the soak test build of Marshmallow, rooted and with Xposed all working as they should.
Thanks for your help!

Bootloop and cannot boot into recovery

Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.

Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode

met911 said:
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
Click to expand...
Click to collapse
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.

met911 said:
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
Click to expand...
Click to collapse
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.

met911 said:
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
Click to expand...
Click to collapse
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. i left it as you mentioned and it went into bootloop. Even the one time i managed to get it in recovery mode and made factory reset and wipe cache partition. I did not get it to be detected by ADB as debugging was not enabled in the setting menu.
This recovery mode is really useless if you cannot start the phone. Its supposed to be RECOVERY mode but its completely useless.
Previously, you could just unlock the bootloader and flash new image. Now it must be enabled in the setting in a phone that does not even work.

The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
You are asking the same questions again. YES, download mode is disabled.
after the first command, it tells me "locked device to enable ramdump"
I tried adb sideload but did not work because its not enabled in the phone settings as i already mentioned before.

I apologize for asking the same questions. I got confused on which thread I was posting in. I have been trying to help someone else with the same issue.
Sent from my Nexus 6 using XDA-Developers mobile app

Adb sideload won't work in bootloader mode, only in recovery. The only thing that will work in bootloader mode is fastboot but seeing as the bootloader is locked (with no way to unlock it) you can't use fastboot. If you can't get into recovery there's nothing you can do except send the phone for repair.

But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.

met911 said:
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
Click to expand...
Click to collapse
I'm not sure what you mean by new security, this has been standard fare for some time now. I'm sure if your phone was stolen you'd be thanking this security feature because it'd mean that the thief couldn't possibly access your data.
People in the know usually go into the settings menu and tick the "allow oem unlocking" box even if they don't plan on unlocking the bootloader at that time, there's a slight security risk but it's insurance against situations like this.
And what you're saying isn't entirely true; even if the OS fails the phone can usually still boot into recovery which would mean being able to revive it via adb sideload. What you're experiencing is relatively unusual, not being able to boot into the recovery as well as the OS means you're basically screwed.
If there's anything to take away from this it's that electronic devices fail sometimes. If you can handle the security risk it's worth ticking that box in the settings menu, or even completely unlocking the bootloader, to give yourself some insurance against these rare situations.

Same problem
met911 said:
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Click to expand...
Click to collapse
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me

ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.

ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
uodii said:
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
Click to expand...
Click to collapse
You both might want to take a read of http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921 - it has many people who have experienced the issue you both have. tl;dr - you'll probably need to contact goog/huwaei for a replacement.

Had the exactly same issue the day before yesterday, tried every possible way to flash different versions of images, none worked. My warranty expired 2 weeks ago, so both google and huawei told me that I am on my own for this.

Wow.. I feel for you all. I've had the exact same thing happen some weeks ago, phone freezing, then reboot, then couple of days later bootloop, then able to flash and reinstall, then after one final bootloop with the phone unable to 'take' the flashing through recovery, etc, etc. I've been playing with xda since the days of Froyo and that was the first time I had to send a phone back under warranty.
I was just about to try to manually rebuild the whole partition system at the block level but I'm glad I could send it for repairs. You might have a chance if you go as low as that. Good luck
* edit * I got the TWRP to stick by flashing it in Fastboot a couple of times in a row at that time, then I was adapting a Linux guide on reformatting and repairing drives partitions and all that through an adb shell.I did not get it to work yet before sending it, though.