Database Develop

[Q] Sprint update bricked my phone. More details in post, need some desperate help.

Hi guys so this is a little embarrassing but I'm fairly certain sprint update has bricked my phone. Sprint pushed the update to 4.4 2 nights ago for me and everything was going fine. My phone is rooted and custom recovery so I slapped on the stock recovery to process the update. The update starts off fine and dandy until about halfway through the dreaded red triangle/exclamation mark popped up. I instantly cursed and watched as my phone entered into an infinite boot loop. I thought it might have worked at first because the lock screen popped up, but when you unlock the phone the white htc logo is still there and the phone reboots after 10 seconds. So after making sure something went astronomically wrong with the update, I went into the boot loader and adb pushed twrp back onto the phone. the update somehow updated my hboot to 1.55 so my s-off is now s-on and I have no wawy to tell if the kernal for the phone is functioning. My only guess to this matter is that the boot sector for the phone is corrupt, but I tried to restore the stock twrp backup i have, and nothing. It boots, the lockscreen unlocks, but it still reboots. Now it was unlocked long enough for me to get into settings and see that it wiped ALL of my phones id info. All the meid, meie, carrier, everything is blank. So it seems that the phone crashed somewhere in the update where it was in the process of wiping things? I then tried to flash a completely different rom on there to see how that went. I first tried viperone 5.0.0 then the newer 5.8.0 and neither would boot (waited 1 hour each to make sure). Then I tried arhd 61 and again, no boot. So I'm not quite sure where to go from here. My stock backups aren't working at restoring, new rom flash isnt working, I can't take it into sprint to check on it since its rooted, I can't update the kernel due to s-on (correct me if im wrong). I'm smart enough to know when I'm out of my depth and I'm clearly trying to tread water in the middle of the ocean in this instance. So please if someone could give me a hand I would appreciate it so much.

xanex18 said:
Hi guys so this is a little embarrassing but I'm fairly certain sprint update has bricked my phone. Sprint pushed the update to 4.4 2 nights ago for me and everything was going fine. My phone is rooted and custom recovery so I slapped on the stock recovery to process the update. The update starts off fine and dandy until about halfway through the dreaded red triangle/exclamation mark popped up. I instantly cursed and watched as my phone entered into an infinite boot loop. I thought it might have worked at first because the lock screen popped up, but when you unlock the phone the white htc logo is still there and the phone reboots after 10 seconds. So after making sure something went astronomically wrong with the update, I went into the boot loader and adb pushed twrp back onto the phone. the update somehow updated my hboot to 1.55 so my s-off is now s-on and I have no wawy to tell if the kernal for the phone is functioning. My only guess to this matter is that the boot sector for the phone is corrupt, but I tried to restore the stock twrp backup i have, and nothing. It boots, the lockscreen unlocks, but it still reboots. Now it was unlocked long enough for me to get into settings and see that it wiped ALL of my phones id info. All the meid, meie, carrier, everything is blank. So it seems that the phone crashed somewhere in the update where it was in the process of wiping things? I then tried to flash a completely different rom on there to see how that went. I first tried viperone 5.0.0 then the newer 5.8.0 and neither would boot (waited 1 hour each to make sure). Then I tried arhd 61 and again, no boot. So I'm not quite sure where to go from here. My stock backups aren't working at restoring, new rom flash isnt working, I can't take it into sprint to check on it since its rooted, I can't update the kernel due to s-on (correct me if im wrong). I'm smart enough to know when I'm out of my depth and I'm clearly trying to tread water in the middle of the ocean in this instance. So please if someone could give me a hand I would appreciate it so much.
Click to expand...
Click to collapse
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk

Bairdog35 said:
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I will Definitely check it out. I was hesitant to try an RUU because all the ones I was looking at were talking about flashing modded kernels and needing s-off and such. But I will definitly try it and update if it works.

Bairdog35 said:
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Alright mate, I'm gunna need a mailing address to send my first born son to. You are a god send with that link. It worked perfectly

xanex18 said:
Alright mate, I'm gunna need a mailing address to send my first born son to. You are a god send with that link. It worked perfectly
Click to expand...
Click to collapse
I'm glad it worked ?
Sent from my HTCONE using Tapatalk

Unlocking bl without wipe

Basically what the title says. Is it possible. Also if not will it wipe my sd card. Internal obviously to save some smart arse! The nexusunlckr app on playstore don't support the 6.
Thanks
Sent from my Nexus 6 using Tapatalk

Mr_S said:
Basically what the title says. Is it possible. Also if not will it wipe my sd card. Internal obviously to save some smart arse! The nexusunlckr app on playstore don't support the 6.
Thanks
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It will factory reset and wipe data but should leave internal sd intact.

Mr_S said:
Basically what the title says. Is it possible. Also if not will it wipe my sd card. Internal obviously to save some smart arse! The nexusunlckr app on playstore don't support the 6.
Thanks
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
not possible. aa soon as you unlock the bootloader, itll delete everything thats in your storage. everything.
---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------
prdog1 said:
It will factory reset and wipe data but should leave internal sd intact.
Click to expand...
Click to collapse
not true. as soon as you unlock the bootloader, itll wipe every single bit of your storage, and even warns you before you press yes.

simms22 said:
not possible. aa soon as you unlock the bootloader, itll delete everything thats in your storage. everything.
---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------
not true. as soon as you unlock the bootloader, itll wipe every single bit of your storage, and even warns you before you press yes.
Click to expand...
Click to collapse
Been so long couldn't remember if actually wiped storage or just user data.

oh, the n6 doesnt have a sd slot, so cant wipe it. but it does wipe all of your storage. no ifs, ands, or buts..
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
prdog1 said:
Been so long couldn't remember if actually wiped storage or just user data.
Click to expand...
Click to collapse
thats usually one of my problems, doing stuff so long ago that i forget. but this one i dont forget, since every one of my nexus has to go through it, once.

simms22 said:
oh, the n6 doesnt have a sd slot, so cant wipe it. but it does wipe all of your storage. no ifs, ands, or buts..
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
thats usually one of my problems, doing stuff so long ago that i forget. but this one i dont forget, since every one of my nexus has to go through it, once.
Click to expand...
Click to collapse
N9 does it on relock also. Not sure about N6. Never relocked it. Lol

prdog1 said:
N9 does it on relock also. Not sure about N6. Never relocked it. Lol
Click to expand...
Click to collapse
i think the n6 does it on relock as well, but ive also never ever relocked a bootloader.

simms22 said:
i think the n6 does it on relock as well, but ive also never ever relocked a bootloader.
Click to expand...
Click to collapse
Yup, it wipes the device (N6) when locking the BL too

Mr_S! I had to deal with this too. I simply copied the files on my n6 to pc, unlocked and moved everything back to the phone when I couldn't find a way to unlock the BL without wiping.
Please don't feel stalked, but if I remember correctly, this has to be the third, if not fourth device we share. Anyway, nice to see you
Gesendet von meinem Nexus 6 mit Tapatalk

nitrous² said:
Mr_S! I had to deal with this too. I simply copied the files on my n6 to pc, unlocked and moved everything back to the phone when I couldn't find a way to unlock the BL without wiping.
Please don't feel stalked, but if I remember correctly, this has to be the third, if not fourth device we share. Anyway, nice to see you
Gesendet von meinem Nexus 6 mit Tapatalk
Click to expand...
Click to collapse
Wow! My friend from the one x days! Hello[emoji1] never managed to s-off that thing lol. Anyway thats what im thinking of doing. Another thing. I used to flash custom roms to get the latest version of android but courtesy of the mrs ive now got a 6. However there are some things i miss ie. Customisable toggles, hold back to kill, percent in clock ect so in peoples opinions is it worth it weighing up the pros and cons.... Are there any con's?
Ps i know there's apps what can do what i desire
Sent from my Nexus 6 using Tapatalk

Mr_S said:
Wow! My friend from the one x days! Hello[emoji1] never managed to s-off that thing lol. Anyway thats what im thinking of doing. Another thing. I used to flash custom roms to get the latest version of android but courtesy of the mrs ive now got a 6. However there are some things i miss ie. Customisable toggles, hold back to kill, percent in clock ect so in peoples opinions is it worth it weighing up the pros and cons.... Are there any con's?
Ps i know there's apps what can do what i desire
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
On the software side, I miss the One-Handed-Mode from Samsung sometimes as it made it very easy to deal with the big screen. Other than that, there are no cons as it's just what I wanted all the time but couldn't afford. On the hardware side though, coming from years of quality Samsung AMOLED panels, there's the outdated and disappointing AMOLED screen with weird colors and burn ins. But I can live with that. At least I don't have to deal with s-off and TouchCrap and stuff :laugh: If I'd make a list, the pros would outweigh significantly.
Sorry for going OT here =)

My thread mate feel free no ot here!
Btw. What cons have you noticed on custom over stock? Anyone else care to pipe up. For example on exynos chips cause they don't release drivers for gps ect some ROMs would gps issues.
Sent from my Nexus 6 using Tapatalk

I really can't tell you since I'm on CM since day 1. But from what I hear and saw on my N5, there's no real difference performance wise. I think at this time it all comes down to extending Android rather than improving performance. Sure there's the encryption thing on the N6 but I'm fine with that. I tried using it decrypted for a couple of days but there's absolutely NO impact on everyday usage/performance I could notice. And I have to tell you, I'm on CyanogenMod only because of the Theme Engine and App Permissions (Xprivacy isn't nearly as convenient).
To sum it up; No critical cons, wait, no cons at all I can think of using a custom ROM.

Mr_S said:
Wow! My friend from the one x days! Hello[emoji1] never managed to s-off that thing lol. Anyway thats what im thinking of doing. Another thing. I used to flash custom roms to get the latest version of android but courtesy of the mrs ive now got a 6. However there are some things i miss ie. Customisable toggles, hold back to kill, percent in clock ect so in peoples opinions is it worth it weighing up the pros and cons.... Are there any con's?
Ps i know there's apps what can do what i desire
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you know what you`re doing and what you want rooting has no downside* imo, it opens doors to many options and features and enhances the look and performance of the phone. There i said it
* Warranty on devices may regionaly be rejected if the phone is turned in for service/repair with root privileges and/or custom software.

@Mr_S have you unlocked your BL already? I can't relock the BL. Whenever I try to relock the BL I get this error message
Code:
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 0.012s
Turns out I have to type
Code:
fastboot oem lock begin
first, then flash a factory image and end the process with
Code:
fastboot oem lock
However that doesn't work as upon finishing flashing BL and radio .imgs, the updater script tells me that system.img is missing, press any key to exit. The process aborts. Ending this process with
Code:
fastboot oem lock
gives out the same error message as above. Flashing the factory image manually and it's the same all over again. Now I'm desperate for a solution.

No not yet so can't help you mate
Sent from my Nexus 6 using Tapatalk

Any Help/Ideas would be appreciated

Ok so I have a stock, rooted, unlocked but encrypted Nexus 6. Last night it took a bad fall. The glass only cracked in one spot, however the LCD is cracked in several areas. Turning the phone on resulted in a black display. it flickers a few small bars of convoluted color, then goes black. The phone was still on and with launch everywhere I could still "Ok Google..." to do a few things.
Now, like the total idiot I am, for some damn reason I turned the phone off after getting off the phone with Asurion. And because of encryption and the screen being unresponsive (black display) I can't enter the damn screen pattern to unlock it, so I can't boot it up to drag and drop files or use adb to wipe the phone.
Does anyone have any suggestions to where I can somehow either access my files or at the very least wipe the phone? Most of my info that was on the phone is backed up to Googles servers. The are few items that aren't, that I hope I can get, but if I can't, I need to make sure are wiped. Can I enter fastboot without the pattern unlock? Or should I look into someone to repair the screen to at least get it turned on and functional to do what I need?
Thanks in advance!

Phaded said:
Can I enter fastboot without the pattern unlock?
Click to expand...
Click to collapse
If memory serves me right, you can run fastboot commands without having to enter the pattern/pin.

jj14 said:
If memory serves me right, you can run fastboot commands without having to enter the pattern/pin.
Click to expand...
Click to collapse
OK thanks. I will try that when I get home and just flash the factory image to wipe. thanks!

Hmm... from Google support pages:
If your device is running Android 5.1 or higher: Your device is protected to prevent other people from using it if it's been reset to factory settings. To ensure that it's really you doing the reset, you'll need to enter a Google username and password associated with the device after factory reset. If you don't have this information, you won't be able to finish the setup process and use the device at all after factory reset.
Does this mean even if I wipe it, the phone won't be usable for anyone?? they can't refurbish the phone because the phone will need my google info??

Eh screw it... Just gonna send it into Motorola

Phaded said:
Hmm... from Google support pages:
If your device is running Android 5.1 or higher: Your device is protected to prevent other people from using it if it's been reset to factory settings. To ensure that it's really you doing the reset, you'll need to enter a Google username and password associated with the device after factory reset. If you don't have this information, you won't be able to finish the setup process and use the device at all after factory reset.
Does this mean even if I wipe it, the phone won't be usable for anyone?? they can't refurbish the phone because the phone will need my google info??
Click to expand...
Click to collapse
yup, mean even after you wipe it, lets say 100 times, itll still ask you for your password. its security, there would be no point if you could wipe it away. but, there is a way to get rid of it, by flashing the 5.0 or 5.0.1 factory images.

simms22 said:
yup, mean even after you wipe it, lets say 100 times, itll still ask you for your password. its security, there would be no point if you could wipe it away. but, there is a way to get rid of it, by flashing the 5.0 or 5.0.1 factory images.
Click to expand...
Click to collapse
oh so if i flash an older factory image that didn't have that security feature it'll work? thanks.

Phaded said:
oh so if i flash an older factory image that didn't have that security feature it'll work? thanks.
Click to expand...
Click to collapse
yes, as long as your bootloader is unlocked. those images didn't have the security yet.

Phaded said:
they can't refurbish the phone because the phone will need my google info??
Click to expand...
Click to collapse
Hate to say this, but that's their problem You can bet that Google/Motorola will know how to get around it
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
simms22 said:
yes, as long as your bootloader is unlocked. those images didn't have the security yet.
Click to expand...
Click to collapse
Wasn't there some issue with downgrading the bootloader causing problems? Or am I confusing with some other device?

jj14 said:
Hate to say this, but that's their problem You can bet that Google/Motorola will know how to get around it
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
Wasn't there some issue with downgrading the bootloader causing problems? Or am I confusing with some other device?
Click to expand...
Click to collapse
It's my understanding, but I am new to the N6 so correct me if I am wrong, you can downgrade the 5.0 or 5.0.1 factory img as long as you don't downgrade to 71.05 bootloader.

byrdcfmma said:
It's my understanding, but I am new to the N6 so correct me if I am wrong, you can downgrade the 5.0 or 5.0.1 factory img as long as you don't downgrade to 71.05 bootloader.
Click to expand...
Click to collapse
that sounds about right. Just wanted to make sure op didn't flash all images in the factory image

jj14 said:
that sounds about right. Just wanted to make sure op didn't flash all images in the factory image
Click to expand...
Click to collapse
Maybe someone with more exp can give the exact process. I assume you are looking for a img with no bootloader, recovery, and radio like these http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 but older img's
I just got my N6 yesterday, and been reading my a$$ off so I don't mess anything up. So far I have unlocked the bootloader, rooted and installed TWRP.

byrdcfmma said:
Maybe someone with more exp can give the exact process. I assume you are looking for a img with no bootloader, recovery, and radio like these http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 but older img's
I just got my N6 yesterday, and been reading my a$$ off so I don't mess anything up. So far I have unlocked the bootloader, rooted and installed TWRP.
Click to expand...
Click to collapse
One can always go to the google developer images site (developers.google.com/android/nexus/images) and download the image they need. Unzip the downloaded file, and unzip the resulting file. In that, you'll find yet some img files, and yet another zip file that will contain the rest of the img files. Choose which one you want, and flash away

Ok so I was able to get it so the lock screen pattern is gone.
At this point I'm about to do insurance claim.
I want to pull my data (pics etc) off.
I have twrp installed and can get into recovery. Adb devices results in showing my device.
Adb/USB debugging isn't active when booted normally as I flashed new system
Tried using a tool to pull using adb, but no data gets pulled
Anyone have a method for pulling my data off? It's set to charge mode by default so it doesn't show in windows explorer.
Thanks
Sent from my Nexus 6 using XDA Free mobile app

I'm currently in the exact same predicament. Let me know how it goes.

Phaded said:
Ok so I was able to get it so the lock screen pattern is gone.
At this point I'm about to do insurance claim.
I want to pull my data (pics etc) off.
I have twrp installed and can get into recovery. Adb devices results in showing my device.
Adb/USB debugging isn't active when booted normally as I flashed new system
Tried using a tool to pull using adb, but no data gets pulled
Anyone have a method for pulling my data off? It's set to charge mode by default so it doesn't show in windows explorer.
Thanks
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Use adb pull from booted into recovery.

danarama said:
Use adb pull from booted into recovery.
Click to expand...
Click to collapse
Do you happen to know what path I would enter to pull from? I have to specify the target correct? I tried using an adb recovery tool, but when it went to /sdcard it said that path didn't exist.
I believe right now I flashed a 5.0 image (pre forced encryption?)
Sent from my Nexus 6 using XDA Free mobile app

This is the tool I tried to use:
http://forum.xda-developers.com/showthread.php?t=2339530
Sent from my Nexus 6 using XDA Free mobile app

Phaded said:
Do you happen to know what path I would enter to pull from? I have to specify the target correct? I tried using an adb recovery tool, but when it went to /sdcard it said that path didn't exist.
I believe right now I flashed a 5.0 image (pre forced encryption?)
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Is it lollipop?
You need to mount data or sdcard first.
this should work
Code:
adb shell
mount /data
exit
adb pull /data/media/0/* c:\users\phaded\desktop\mybackup\
I've made some assumptions above.

danarama said:
Is it lollipop?
You need to mount data or sdcard first.
this should work
Code:
adb shell
mount /data
exit
adb pull /data/media/0/* c:\users\phaded\desktop\mybackup\
I've made some assumptions above.
Click to expand...
Click to collapse
Yes it's lollipop, just an earlier version of it that didn't have the pattern lock (or whatever security) prompt at boot. I think 5.0.1.
I'm not rooted, does that matter for adb shell in recovery?
/data/media/0/ is my whole sd card correct? Is there a command that will show my directory in that path so I can cherry pick the folders to extract?
Sent from my Nexus 6 using XDA Free mobile app

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.

List of OTA update versions?

Does one of these exist? I know for the original Droid there's a wiki on this site that has all of the known Verizon build numbers.
I just bought a used Droid 3 on eBay and managed to semi-brick it by trying to flash an older revision to it, since they aren't very obvious from the names. If someone has a list of all of the various updates, that would be great.
The only two I have are:
VRZ_XT862_5.5.1_84_D3G-55_1FF_01.xml.zip
VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip
Both of those fail flashing and as such I'm stuck in the bootloader. Need to find a newer one to flash in RSD Lite...
Thanks

drfsupercenter said:
Does one of these exist? I know for the original Droid there's a wiki on this site that has all of the known Verizon build numbers.
I just bought a used Droid 3 on eBay and managed to semi-brick it by trying to flash an older revision to it, since they aren't very obvious from the names. If someone has a list of all of the various updates, that would be great.
The only two I have are:
VRZ_XT862_5.5.1_84_D3G-55_1FF_01.xml.zip
VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip
Both of those fail flashing and as such I'm stuck in the bootloader. Need to find a newer one to flash in RSD Lite...
Thanks
Click to expand...
Click to collapse
should be listed in the index
http://forum.xda-developers.com/showthread.php?t=3114734
[INDEX] Motorola Droid 3 & Helpful Information (2015)
Sent from my XT1060 using XDA Labs

sd_shadow said:
should be listed in the index
http://forum.xda-developers.com/showthread.php?t=3114734
[INDEX] Motorola Droid 3 & Helpful Information (2015)
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
According to that, VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip is the newest for Verizon. I have that one already and it refuses to flash.
The phone said Verizon Wireless before I attempted to flash it, so what's going on? Somehow I think that post is incomplete.

drfsupercenter said:
According to that, VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip is the newest for Verizon. I have that one already and it refuses to flash.
The phone said Verizon Wireless before I attempted to flash it, so what's going on? Somehow I think that post is incomplete.
Click to expand...
Click to collapse
that is the newest available
Sent from my XT1060 using XDA Labs

Oh, that's strange, it seems to boot up correctly now even though RSD Lite said flashing failed about 6 steps in. I guess because neither of the two was able to flash correctly, anything after step 6 didn't get overwritten in the first place.
And I see here it's on 5.7.906
Would it work to try to flash one of the newer builds from a different carrier or will that permabrick me? I'm not used to this locked bootloader crap so I really don't know what I can and can't do.
Edit: Actually, if I try to power it on normally it gives me "AP Flashboot Fast Mode (S) (Flash Failure)"
But if I hold the two volume keys to get into that menu, and I scroll down to BP Tools, then it boots up normally.

drfsupercenter said:
Oh, that's strange, it seems to boot up correctly now even though RSD Lite said flashing failed about 6 steps in. I guess because neither of the two was able to flash correctly, anything after step 6 didn't get overwritten in the first place.
And I see here it's on 5.7.906
Would it work to try to flash one of the newer builds from a different carrier or will that permabrick me? I'm not used to this locked bootloader crap so I really don't know what I can and can't do.
Edit: Actually, if I try to power it on normally it gives me "AP Flashboot Fast Mode (S) (Flash Failure)"
But if I hold the two volume keys to get into that menu, and I scroll down to BP Tools, then it boots up normally.
Click to expand...
Click to collapse
try the 906 flash tool
Sent from my XT1060 using XDA Labs
---------- Post added at 08:02 PM ---------- Previous post was at 08:00 PM ----------
ovelayers one click sbf exe
Sent from my XT1060 using XDA Labs

Oh, I'm an idiot.
Turns out it was just a bad USB cable. That's what I get for buying 50-cent cables from China
I used my Motorola branded one and it worked fine. Got it back working again.
I AM curious about crossflashing other carriers' ROMs to the phone though, would that brick it? I'm not actually trying to use this for phone service, more like just a wi-fi enabled toy, same with my other Droids. So it doesn't matter if it connects to Verizon anymore or not.

drfsupercenter said:
Oh, I'm an idiot.
Turns out it was just a bad USB cable. That's what I get for buying 50-cent cables from China
I used my Motorola branded one and it worked fine. Got it back working again.
I AM curious about crossflashing other carriers' ROMs to the phone though, would that brick it? I'm not actually trying to use this for phone service, more like just a wi-fi enabled toy, same with my other Droids. So it doesn't matter if it connects to Verizon anymore or not.
Click to expand...
Click to collapse
the Chinese one works, getting back to Verizon version is a little tricky though
Sent from my KFFOWI using XDA Labs

sd_shadow said:
the Chinese one works, getting back to Verizon version is a little tricky though
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Can you explain what you mean by that? Tricky how?

drfsupercenter said:
Can you explain what you mean by that? Tricky how?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2222966
Sent from my KFFOWI using XDA Labs