Database Develop

Droid bionic JB FXZ help!

So I tried to install JB from recovery and it said successful but then it was stuck in a bootloop at the droid eye. I cleaned the cache and some other things and it still didn't work. Then I made it worse by trying a second time to install JB from my SD card and it failed. Now I just get a black screen after the moto symbol. So I am trying to use RSD lite 6.1.4(Newest version?) and the JB FXZ from "h ttp://sbf.droid-developers.org/cdma_targa/list.php" to flash it but it is failing and saying "Failed flashing process. 5/24 oem fb_mode_set -> Phone returned FAIL" Any ideas of how to get past this? Thanks!

Dirtdawg57 said:
So I tried to install JB from recovery and it said successful but then it was stuck in a bootloop at the droid eye. I cleaned the cache and some other things and it still didn't work. Then I made it worse by trying a second time to install JB from my SD card and it failed. Now I just get a black screen after the moto symbol. So I am trying to use RSD lite 6.1.4(Newest version?) and the JB FXZ from "h ttp://sbf.droid-developers.org/cdma_targa/list.php" to flash it but it is failing and saying "Failed flashing process. 5/24 oem fb_mode_set -> Phone returned FAIL" Any ideas of how to get past this? Thanks!
Click to expand...
Click to collapse
Take the CDT file and the BOOT.IMG from the JB FXZ and overwrite the same files in an ICS (246) FXZ. It probably won't work, but you should be able to reach your recovery. If you have the JB update on your SD card just install it from there and you should be good to go.

Dirtdawg57 said:
So I tried to install JB from recovery and it said successful but then it was stuck in a bootloop at the droid eye. I cleaned the cache and some other things and it still didn't work. Then I made it worse by trying a second time to install JB from my SD card and it failed. Now I just get a black screen after the moto symbol. So I am trying to use RSD lite 6.1.4(Newest version?) and the JB FXZ from "h ttp://sbf.droid-developers.org/cdma_targa/list.php" to flash it but it is failing and saying "Failed flashing process. 5/24 oem fb_mode_set -> Phone returned FAIL" Any ideas of how to get past this? Thanks!
Click to expand...
Click to collapse
1. open the file : cdma_targa_9.8.2O-72_VZW-22_cfc
2. remove the line : <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />
3. Save
4. Try flash use RSD

mc_akiong said:
1. open the file : cdma_targa_9.8.2O-72_VZW-22_cfc
2. remove the line : <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />
3. Save
4. Try flash use RSD
Click to expand...
Click to collapse
I found this method last night on a RAZR forum. I just opened the file up in notepad and removed those 2 lines and RSD worked great! I was so excited because I had just had it up at Verizon and they had said the phone was dead. Thanks for your responses!

Dirtdawg57 said:
I found this method last night on a RAZR forum. I just opened the file up in notepad and removed those 2 lines and RSD worked great! I was so excited because I had just had it up at Verizon and they had said the phone was dead. Thanks for your responses!
Click to expand...
Click to collapse
Yeah always go to the HoB for this stuff Samuri will have your back
Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2

Obsidian... said:
Yeah always go to the HoB for this stuff Samuri will have your back
Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Sir i did this exactly as stated, and still i get the fail at 5... am I to remove from the first to the second part?

saved my life(bionic)
mc_akiong said:
1. open the file : cdma_targa_9.8.2O-72_VZW-22_cfc
2. remove the line : <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />
3. Save
4. Try flash use RSD
Click to expand...
Click to collapse
i've never had problems using an FXZ until i was trying to unlock my bionic for use on ATT/TMO and things went awry, and this just save my bionic from being a tinker toy....

Here's another person that had the same issue with the boot loop after sbf_flash update. He resolved the issue after wiping the data and cache in recovery. Hope that helps...someone; even if it may come a little late for you
facelessuser said:
A note to people who try and do the SBF. Wipe your data and cache in recovery if you have a boot loop after flashing. I have verified this method works, but I had to wipe my data and cache afterwards to get past an infinite boot loop.
Click to expand...
Click to collapse

Thanks
mc_akiong said:
1. open the file : cdma_targa_9.8.2O-72_VZW-22_cfc
2. remove the line : <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />
3. Save
4. Try flash use RSD
Click to expand...
Click to collapse
Led me down the right path. Ended up having to decompress, edit file then create new zip. Never would have thought of it if i hadn't seen your post.

im having the same issue i believe but the sbf goes through but the phone still is stuck in some boot loop.

Dirtdawg57 said:
So I tried to install JB from recovery and it said successful but then it was stuck in a bootloop at the droid eye. I cleaned the cache and some other things and it still didn't work. Then I made it worse by trying a second time to install JB from my SD card and it failed. Now I just get a black screen after the moto symbol. So I am trying to use RSD lite 6.1.4(Newest version?) and the JB FXZ from "h ttp://sbf.droid-developers.org/cdma_targa/list.php" to flash it but it is failing and saying "Failed flashing process. 5/24 oem fb_mode_set -> Phone returned FAIL" Any ideas of how to get past this? Thanks!
Click to expand...
Click to collapse
mc_akiong said:
1. open the file : cdma_targa_9.8.2O-72_VZW-22_cfc
2. remove the line : <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />
3. Save
4. Try flash use RSD
Click to expand...
Click to collapse
I know this is a pretty old thread and the last post was somewhere around two years ago, but I just thought I post something that I been pulling my hair about for a few days. I live in Cambodia located in the southeast part of Asia. But that isn't relevant to what I'm am gonna talk about. I tried many different sites looking for ways to flash my xt975. and every post was different. The gem problem that I had facing with the flash was that there were errors that would occurred when I had flashed them. One of them being steps 5/24 oem fb_mode_set -> Phone returned FAIL. This was solved by a suggestion by mc_akiong who have further the steps for my process or unbricking my phone via RSD Lite. It successfully pass that part until steps 10/21 where an error occurred that "10/22 flash lbl "lbl" -> Phone returned FAIL.. I searched everywhere on the net to figure out how to fix this problem and could not find a solution after countless hours of reading threads that didn't help pertaining to the issue I was facing. Then It had occurred to me that maybe if I try and edit the cdma_targa_9.8.2O-72_VZW-22_cfc file and edit it's properties like mc_akiong had suggest this may bypass the error. It was try this or search and waste more hours than I needed. I edit the file using wordpad since it aligns all the text properly in the manner their were scripted. I search for the line "<step operation="flash" partition="lbl" filename="lbl" MD5="60377be478e282124139a07d86ae2b80" />" and completely delete it from the script. After doing this I save it and ran RSD Lite. With fingers crossed it work and now my phone is fully operational. I have also left a image of the line that highlight what you should edit, but remember if you have problems with step 5/24 do the edit suggested above by mc_akiong and also edit this if you are facing this problem with the lbl error. I hope that this is helpful...BTW this is also my first post :highfive:

SPheDaGhost said:
I know this is a pretty old thread and the last post was somewhere around two years ago, but I just thought I post something that I been pulling my hair about for a few days. I live in Cambodia located in the southeast part of Asia. But that isn't relevant to what I'm am gonna talk about. I tried many different sites looking for ways to flash my xt975. and every post was different. The gem problem that I had facing with the flash was that there were errors that would occurred when I had flashed them. One of them being steps 5/24 oem fb_mode_set -> Phone returned FAIL. This was solved by a suggestion by mc_akiong who have further the steps for my process or unbricking my phone via RSD Lite. It successfully pass that part until steps 10/21 where an error occurred that "10/22 flash lbl "lbl" -> Phone returned FAIL.. I searched everywhere on the net to figure out how to fix this problem and could not find a solution after countless hours of reading threads that didn't help pertaining to the issue I was facing. Then It had occurred to me that maybe if I try and edit the cdma_targa_9.8.2O-72_VZW-22_cfc file and edit it's properties like mc_akiong had suggest this may bypass the error. It was try this or search and waste more hours than I needed. I edit the file using wordpad since it aligns all the text properly in the manner their were scripted. I search for the line "<step operation="flash" partition="lbl" filename="lbl" MD5="60377be478e282124139a07d86ae2b80" />" and completely delete it from the script. After doing this I save it and ran RSD Lite. With fingers crossed it work and now my phone is fully operational. I have also left a image of the line that highlight what you should edit, but remember if you have problems with step 5/24 do the edit suggested above by mc_akiong and also edit this if you are facing this problem with the lbl error. I hope that this is helpful...BTW this is also my first post :highfive:
Click to expand...
Click to collapse
Thank you so much for taking the time to note this. I ran into the same issue and solved it because of you. Just know that what info you took your time to give and learn many of us wouldn't have had the patience or time to get that ourselves. Again....thank you!!!

DROID BIONIC bricked after root and bootstrap.apk
droid bionic bricked after bootstap. now i am installing j.b firmware via rsd lite 6.1.6 its keep flashing system.img about 1:.30m mins somebody tell me how long does it take to finish complete setup??????????????

john-ammu said:
droid bionic bricked after bootstap. now i am installing j.b firmware via rsd lite 6.1.6 its keep flashing system.img about 1:.30m mins somebody tell me how long does it take to finish complete setup??????????????
Click to expand...
Click to collapse
Three years to reply back, but I didn't take me that long to flash probably 5-10 mins probably less it was so long ago ?
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
Deeshizzle said:
Thank you so much for taking the time to note this. I ran into the same issue and solved it because of you. Just know that what info you took your time to give and learn many of us wouldn't have had the patience or time to get that ourselves. Again....thank you!!!
Click to expand...
Click to collapse
No problem, I'm glad I could help someone with the issue, and address it as clearly as I could.

Stock Images/recovery

Hello all,
I just purchased a Moto Atrix HD and have already gotten it nice and rooted and unlocked and I'm planning on flashing a ROM very soon as well as perhaps doing some development of my own for the community. I've never done any work for Motorola devices in the past because of the locked bootloaders and how easy it is to hard-brick the device. However, since we have unlocked bootloaders, it changes things for us a lot. My question is whether a stock image which could be flashed via the bootloader/fastboot commands exists and where I could get that from if it does. Also, does anyone know of a way to boot directly to the bootloader from 'off'? That's also an important piece of information to have if I have a soft brick. I realize these are fairly selfish requests of a developer but you have to realize that I'm not made of money and while the Atrix HD isn't my main device, I'm still a college student and money doesn't seem to grow on trees I appreciate any leads that anyone can give me or information that you can provide!
Cheers!

We do have firmwares that can be flashed in fast boot. I cannot link them now, but if you Google "atrix HD sbf" it should give you each one on the first or second link. It will have some for Mex, some for ATT, and some for Bell. Get the latest one for your carrier (I believe Mex and ATT have same radio but Mex has less bloat).
And to boot directly into bootloader (fastboot), hold vol down and power.
Sent from my MB886 using xda app-developers app

penser said:
We do have firmwares that can be flashed in fast boot. I cannot link them now, but if you Google "atrix HD sbf" it should give you each one on the first or second link. It will have some for Mex, some for ATT, and some for Bell. Get the latest one for your carrier (I believe Mex and ATT have same radio but Mex has less bloat).
And to boot directly into bootloader (fastboot), hold vol down and power.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Thanks! I found an awesome site with every sbf since the beginning of time. Now, would the best way to flash one of these images (.xml?) be through rsd lite?

sparkplugDev said:
Thanks! I found an awesome site with every sbf since the beginning of time. Now, would the best way to flash one of these images (.xml?) be through rsd lite?
Click to expand...
Click to collapse
You could either do that (but I recommend Myth Tools over RSD, never used RSD myself), or manually flash it because I've always had problems flashing with Myth. To install with Myth Tools, just put the *.xml.zip into the "*\Myth Tools - AHD\firmwares" folder and flash it using Myth, simple as that. To flash it manually, extract the zip anywhere (I use 7z and use the "extract to \zipfoldernamehere\" option to keep everything neat) and open the XML in notepad++ (I prefer ++ over regular notepad) and you'll see a big block of stuff in the middle with lines such as "<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="F36E6FB37E6BD0066FAF56688603DDD0" />". You'll need to start with the one posted above, don't bother with the "getvar max-download-size", run the commands as "fastboot [step operation] [partition] [filename]". Whatever is in quotes after each of the above, put that in the command so it looks like "fastboot flash partition fpt_main0.bin".

I recomend RSD Lite 6.1.
Checkout my post here:
http://forum.xda-developers.com/showthread.php?p=44459868
Sent from my Atrix HD

RSD Lite problem when returning to stock

I have been trying for a while now to flash the stock VZW 4.4.2 firmware with RSD Lite. I have deleted the "<step operation="getvar" var="max-download-size" />" line from the XML file. However, when I get it going with flashing stuff, I still see a "getvar max-download-size" before every operation, and once it gets to system.img, it will only download the "max" of 805,306,368 bytes, instead of the entire file.
I have done all this twice before and had no problems, so I have no idea what is going on this time. It is probably something stupid, but any help would be appreciated.

Which version of Android are you currently running?

ShaneRitz said:
I have been trying for a while now to flash the stock VZW 4.4.2 firmware with RSD Lite. I have deleted the "<step operation="getvar" var="max-download-size" />" line from the XML file. However, when I get it going with flashing stuff, I still see a "getvar max-download-size" before every operation, and once it gets to system.img, it will only download the "max" of 805,306,368 bytes, instead of the entire file.
I have done all this twice before and had no problems, so I have no idea what is going on this time. It is probably something stupid, but any help would be appreciated.
Click to expand...
Click to collapse
Yep, just flashed it yesterday exactly the way you did, and that appears appears on the phone's screen, but you need to wait and it should finish flashing without any problems.

Bootloader unlocking theory

Agimax recently discovered a way into fast boot mode
Agimax said:
Ok, so i've been able to nuke my LAF partition and get into Fastboot mode. This gives access to all fastboot commands, but removes ability to use Download Mode. I am on ZV6 / UltraPOP. Once you backup your laf partition, you can reboot like you would for download mode but goes to fastboot. You can restore LAF partition from the backup you make and get back access to download mode.
I tried to see if our bootloader will unlock like the way they do it in the T-Mobile forums by checking the OEM Unlock in the developer menu, then booting to Fastboot and running 'Fastboot.exe oem unlock', but unfortunately it will not work. The phone does not recognize the unlock command like it does for the T-Mobile versions. See screenshots. I'm still working on this. Keep in mind, if you do something wrong, you will NOT have the ability to TOT without the download mode until you restore the LAF back to the phone!
Instructions: (only try if you are an advanced tester!)
1.) Backup your LAF partition command from ADB
* copy this in a safe place before nuking your LAF partition. Like on a flashdrive or computer.
Code:
dd if=/dev/block/bootdevice/by-name/laf of=/sdcard/laf.img
2.) Nuke your LAF partition command from ADB
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf
* now you can boot into fastboot mode by booting like you would into download mode (up-volume and power on with usb plugged in)
Note: Once you are in fastboot mode, you must update the drivers on your computer by opening device manager and clicking on the ADB device and updating driver over internet. Reboot back into fastboot mode and commands will work.
To restore your LAF partition command from ADB
Code:
'dd of=/dev/block/bootdevice/by-name/laf if=/sdcard/laf.img'
* you may also restore the laf partition from fastboot if you wish, but they are different commands
My thoughts are -if we were able to Nuke the LAF partition on 6.0 M, we would be able to copy the partitions from the phone we would need to make rooted system images and also modem and kernel. This should allow us to copy partitions to a phone running 5.1 and switch between by just flashing the 3 partitions back and forth.
Click to expand...
Click to collapse
Im wondering if we can get the unlock files from one of the other models and hexing out the unlock bin from imei numbers and zeros, maybe we can unlock our device by replacing them with our imei and serial number??

Who knows. I'm not a developer so maybe someone can try it. There's just not enough attention from developers for this device.

LaughingCarrot said:
Who knows. I'm not a developer so maybe someone can try it. There's just not enough attention from developers for this device.
Click to expand...
Click to collapse
That is some constructive feedback...

jaxbierley said:
That is some constructive feedback...
Click to expand...
Click to collapse
Just throwing something in to make conversation is all.

sorry to bothering you meaby would be better if you post all your unlock bootloader ideas on lg4 general forum...http://forum.xda-developers.com/g4/general where are more people to see it.

Awesomeslayerg said:
Agimax recently discovered a way into fast boot mode
Im wondering if we can get the unlock files from one of the other models and hexing out the unlock bin from imei numbers and zeros, maybe we can unlock our device by replacing them with our imei and serial number??
Click to expand...
Click to collapse
it's safe to nuke recovery and get the same result....so if anything does wrong you still have download mode!!!!

Any idea yet why the command "fastboot flashing unlock" is not recognized? It seems no commands are recognized...

thetruejay20 said:
Any idea yet why the command "fastboot flashing unlock" is not recognized? It seems no commands are recognized...
Click to expand...
Click to collapse
Its killing me not having fastboot. i have backed up all my bootloader partitions and have been skimming through trying to get my device id no. I have a random unlock.bin but that dont help none realy. All it doez is give me the hex adresse that are modified. But there diffrent on every one. From what it get is that the bootloader aint no more locked than any other. The partitions that the boooader resides in are what the issue is. they are encrypted i guess with a 256 bit security. From what i have read the unlock.bin decrypts the partitions so oem unlock can be applied. Now if im wrong or been misinformed please somone correct me.

TheMadScientist420 said:
Its killing me not having fastboot. i have backed up all my bootloader partitions and have been skimming through trying to get my device id no. I have a random unlock.bin but that dont help none realy. All it doez is give me the hex adresse that are modified. But there diffrent on every one. From what it get is that the bootloader aint no more locked than any other. The partitions that the boooader resides in are what the issue is. they are encrypted i guess with a 256 bit security. From what i have read the unlock.bin decrypts the partitions so oem unlock can be applied. Now if im wrong or been misinformed please somone correct me.
Click to expand...
Click to collapse
Yes I spent hours reading up on it yesterday, you're pretty much right on.

thetruejay20 said:
Yes I spent hours reading up on it yesterday, you're pretty much right on.
Click to expand...
Click to collapse
Now i found a tool windroid toolkit check it out i atempt to use the tool and it attemps to reboot me to fastboot i guess to attempt to get me identifier key but ofcoarse the phone just reboots. I guess i need to nuke my laf and try to see if i can get that key from my own device. My prob is im not to good with dd comands im rusty been a while. I have a backup of my laf cant find the post that shows me how to nuke and restore when im done testing is the instructions at top rite on doing it
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
Im assuming that the toolkit prob uses a diffrent algorothim than g4 does to do unlocks but it asks what type of phone i click g4 never asks for a sub model
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
And this is y lg needs to unlock them here we go trying extremes because of them.
---------- Post added at 12:33 PM ---------- Previous post was at 12:01 PM ----------
I guess we need to figure out how sprint lcked us out of fastboot. Thats the first step im back on it im at work rite now. So i aint got my comput near me.

TheMadScientist420 said:
I guess we need to figure out how sprint lcked us out of fastboot. Thats the first step im back on it im at work rite now. So i aint got my comput near me.
Click to expand...
Click to collapse
God speed to you man. I would love to pitch in, but I have no clie on how to crack a bootloader. Is there anything anywhere that I can learn from?

Quickdraw996 said:
God speed to you man. I would love to pitch in, but I have no clie on how to crack a bootloader. Is there anything anywhere that I can learn from?
Click to expand...
Click to collapse
I have been readin up on old lg bootloaders i use to to a lotta nes roms hack which is differ of coarse but. They do hex edit to mod them. Biggest think is craking the 256 bit encryption. Only thing i ask of any of u is read and inform me too we can hopefully figure this out. I aint no dev but anything is possible the solution is sometimes the dumbest thing rite in front of u. Were looking so deep that it might be rite in front of our faces. I. Need to get to fastboot without nuking my laf partition i need it working. Trying to figure how sprint locked us out of fast boot

TheMadScientist420 said:
I have been readin up on old lg bootloaders i use to to a lotta nes roms hack which is differ of coarse but. They do hex edit to mod them. Biggest think is craking the 256 bit encryption. Only thing i ask of any of u is read and inform me too we can hopefully figure this out. I aint no dev but anything is possible the solution is sometimes the dumbest thing rite in front of u. Were looking so deep that it might be rite in front of our faces. I. Need to get to fastboot without nuking my laf partition i need it working. Trying to figure how sprint locked us out of fast boot
Click to expand...
Click to collapse
Well I nuked my recovery partition to get into fastboot mode, but no fastboot commands are recognized in fastboot mode.
---------- Post added at 03:57 PM ---------- Previous post was at 03:52 PM ----------
TheMadScientist420 said:
Now i found a tool windroid toolkit check it out i atempt to use the tool and it attemps to reboot me to fastboot i guess to attempt to get me identifier key but ofcoarse the phone just reboots. I guess i need to nuke my laf and try to see if i can get that key from my own device. My prob is im not to good with dd comands im rusty been a while. I have a backup of my laf cant find the post that shows me how to nuke and restore when im done testing is the instructions at top rite on doing it
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
Im assuming that the toolkit prob uses a diffrent algorothim than g4 does to do unlocks but it asks what type of phone i click g4 never asks for a sub model
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
And this is y lg needs to unlock them here we go trying extremes because of them.
---------- Post added at 12:33 PM ---------- Previous post was at 12:01 PM ----------
I guess we need to figure out how sprint lcked us out of fastboot. Thats the first step im back on it im at work rite now. So i aint got my comput near me.
Click to expand...
Click to collapse
I checked out that windroid toolkit, and the only supported LG G4 devices is the H815. But definitely a good find!

Stock rom without root or unlock only can enter bootloader

My nexus 6 using stock rom and update to the latest version thru OTA, without root or unlock bootloader. Yesterday it suddenly reboot and only allow to boot into bootloader. Cannot select recovery or factory mode, check the bootloader log show failed to validate the boot image or recovery image.
I've read many threads and try many methods to unloock the bootloader and flash the factory image but failed.
Anyone can help to get the nexus 6 back, thanks so much.

Probably going to have to do an RMA, you can't use any of the recovery options (fastboot, custom recoveries) with a locked bootloader, that is the whole point of it being locked.

Since we're now suggesting RMA, I have to ask...
Have you tried in the bootloader screen "fastboot oem unlock"?
Maybe you have, but your problem description is really pretty vague.
scryan, not trying to tread on your toes, and I may be completely wrong (about to fall asleep) but isn't the whole point of "fastboot oem unlock" that it runs in bootloader specifically to unlock it?

dahawthorne said:
Since we're now suggesting RMA, I have to ask...
Have you tried in the bootloader screen "fastboot oem unlock"?
justMaybe you have, but your problem description is really pretty vague.
scryan, not trying to tread on your toes, and I may be completely wrong (about to fall asleep) but isn't the whole point of "fastboot oem unlock" that it runs in bootloader specifically to unlock it?
Click to expand...
Click to collapse
I am sorry as this is my 1st post here. My Nexus 6 was not rooted and even not enable "usb debug" or "oem unlock" setting.
I've already tried "fastboot oem unlock" and failed. I've also tried "fastboot flashing unloock", it said ok but restart the bootloader and it still show locked.
I've also tried the Nexus Root Tools too to unlock or flash the factory image, recovery image or boot to twrp but all failed too.

Then you have no choice but to request a RMA. To be able to unlock the bootloader so you can then flash a stock ROM, you have to enable Developer Options, then in Developer Options enable both USB Debugging and OEM Unlock.

Have you tried the hardbrick tread? Not sure if this will work with locked bootloaders. http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:06 PM ---------- Previous post was at 08:50 PM ----------
Have you tried fastboot reboot-recovery to enter recovery? With or without the "-", I forget the proper form. With locked bootloaders I don't think u can flash anything from recovery. Plus it may be a hardware issue not necessarily software related.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
But if you can enter recovery maybe you can factory reset and at least get it to boot!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:07 PM ----------
What version of fastboot are you using, old fastboot may not work properly.
Sent from my Nexus 6 using Tapatalk

Jnewell05 said:
Have you tried the hardbrick tread? Not sure if this will work with locked bootloaders. http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:06 PM ---------- Previous post was at 08:50 PM ----------
Have you tried fastboot reboot-recovery to enter recovery? With or without the "-", I forget the proper form. With locked bootloaders I don't think u can flash anything from recovery. Plus it may be a hardware issue not necessarily software related.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
But if you can enter recovery maybe you can factory reset and at least get it to boot!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:07 PM ----------
What version of fastboot are you using, old fastboot may not work properly.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thx so much for your reply, I've tried the hard-brick thread but can't install the qualcomm driver.
I plan to contact the Google see whether it can help me since I am in HK and my Nexus 6 is not directly bought from HK Google.
It really quite depress me since I do nothing with the phone, I do not flash any custom rom, do not root or unlock bootloader, just normal use it then suddenly crashed .... >_<

this exact same thing happened to my wife's phone just a month ago... and the sad thing is the phone was just bought new for only 2 months or so. never installed any custom roms, never rooted, etc. and now i wish that i did so that i could have at least turned ON that option in Developers Option to "allow OEM Unlock" and if i did, it should've been an easy fix.
i never had this kind of issue before thats why i thought there is nothing important to turn on in the Developers Option. they should've made that information more available and even point it out on the Update but they didn't which sucks.
i also tried to contact Motorola US but since im not in the US, even though the phone is bought in the US via Ebay, they weren't able to help and sent me to another Motorola site for my region. i'm trying it now and i still cant go through the site...
it's really depressing when this kind of things happen... i hope in the future there would be some kind of fix for this. i heard if we can get a signed System that we could flash into the phone then there's a chance it could work but as of now, i keep checking for information about this and hoping someone came up with something...
hope this thing won't happen to anyone else and if you got a Nexus 6, make sure to turn On "Allow OEM Unlock" on your phone.

quinceyr said:
this exact same thing happened to my wife's phone just a month ago... and the sad thing is the phone was just bought new for only 2 months or so. never installed any custom roms, never rooted, etc. and now i wish that i did so that i could have at least turned ON that option in Developers Option to "allow OEM Unlock" and if i did, it should've been an easy fix.
i never had this kind of issue before thats why i thought there is nothing important to turn on in the Developers Option. they should've made that information more available and even point it out on the Update but they didn't which sucks.
i also tried to contact Motorola US but since im not in the US, even though the phone is bought in the US via Ebay, they weren't able to help and sent me to another Motorola site for my region. i'm trying it now and i still cant go through the site...
it's really depressing when this kind of things happen... i hope in the future there would be some kind of fix for this. i heard if we can get a signed System that we could flash into the phone then there's a chance it could work but as of now, i keep checking for information about this and hoping someone came up with something...
hope this thing won't happen to anyone else and if you got a Nexus 6, make sure to turn On "Allow OEM Unlock" on your phone.
Click to expand...
Click to collapse
Hi, quinceyr, I've just tried the below thread and restore my Nexus 6 back and only draw back is updated to Android N preview version. I've tested for a while seems work fine and will keep monitor for a period.
http://forum.xda-developers.com/nexus-6/help/command-device-corrupt-update-t3362317/page2
Hope your Nexus 6 will recover back.