Database Develop

[Q] root help bricked phone

did the RegawMOD root and rebooted phone now its bricked help!!

Define what you mean by "bricked"
Sent from my Android using Tapatalk

rooted phone, fine, restarted and stuck on htc screen pulled battery tried to put in recovery mode and its stuck on htc screen

did u make an ndroid bc if so u can just go back i do it all the time lol

no i didnt know how without root and rom manager wouldnt install

any advice???

is there a way i can still make a back up or am i going to have to unbrick the device?

tom2tone said:
rooted phone, fine, restarted and stuck on htc screen pulled battery tried to put in recovery mode and its stuck on htc screen
Click to expand...
Click to collapse
Well, I can tell you that if it turns on, it's not bricked.
As for a fix, look at oostah's thread : here to find out how to run the RUU via fastboot (.. Should be in that thread)
After you get the ruu to run, you'll be back to stock. Then you can try to root again.
Sent from my Android using Tapatalk

didnt find it

...ok
then read through this thread > here
get the zip in this thread > here
Sent from my Android using Tapatalk

will it erase my contacts cuz i didnt know how to save them???

tom2tone said:
will it erase my contacts cuz i didnt know how to save them???
Click to expand...
Click to collapse
it returns it completely back to stock. so yes, if they're not synced with google.
Sign into your gmail account and view your contacts > located right below the GMAIL icon on the left side. if they were synced then they'll all be there...if they're not then that makes this situation a little more difficult
Do you have adb installed? I'm not particularly familiar with the Regaw rooting tool, so I'm not sure if it's required
Sent from my Android using Tapatalk

no damn it wont even connect to the computer

Did you check to see if your contacts are backed up on google or not?
And you never said if you have adb or not...
Does booting into the bootloader work? VOL DOWN + POWER
As I see it, you have 2 options:
1) regardless of whether your contacts are backed up or not, you can try the RUU zip/fastboot method I posted previously. if it works, you'll at least have a working phone
2) if your phone is new, you can bring it into your service provider (sprint) and see what they can do
**note** with the 2nd option, I'm not sure whether they'll be able to tell if you're rooted/tried to root or not. Someone else would have to chime in for that.
Sent from my Android using Tapatalk
Edit: if you do have adb, you can have your phone connected to the computer and run "adb logcat" to see if it's actually doing something while it's hanging on the HTC screen

no google or adb can you help me do the logcat plz b4 i go back to stock?

Go here for information on how to install/setup adb > LINK
After it's set up, just boot your phone normally, have it connected to your computer and do the "adb logcat" command - just like you'll do "adb devices" on the adb link I gave you.
You'll be able to see if things are loading, or if it's just sitting there doing nothing.
Sent from my Android using Tapatalk

it wont connect my phone to my computer??????

cant get my pc to find phone

tom2tone said:
cant get my pc to find phone
Click to expand...
Click to collapse
:x what OS are you running? arch, ubu, win7, mac, etc.
if its win7 did you get the necessary drivers for it? > LINK/ get the 32bit or 64bit for the machine you have. Then try adb devices again.
Sent from my Android using Tapatalk

the drivers didnt work it still wont find the pc

Stuck in sideload

EDIT FOR THOSE WHO MAY HAVE THIS ISSUE:
If you have accidentally entered sideload mode from CWM, there are 2 ways to get out of it.
1) - the fastest way - flash a rom from it (.zip format eg KA04 xperia revolution etc)
2) - the easiest (but potentially very slow if you have a full battery) - let your battery run empty, the phone will power down when it goes flat. Put it on charge and leave it for a while (it will take a while to get enough charge to be able to boot again so be patient)
If you are going to flash a rom you will need to do some house keeping. I was having big issues with sideload mode as my computer wasn't recognizing the phone properly, and sideload commands were not working. The phone was essentially not responding to any ADB commands or the sideload flash command.
This all turned out to be from left over drivers from my galaxy s 2. For what ever reason, rooting, installing custom recovery, adb, bootloader unlocking and flashtool all work flawlessly with my driver set up, but sideload mode did not like it at all.
I over came the issue by using a computer which had a fresh installation of windows 7, which therefore had no previous drivers for any devices besides that of the PC itself. It worked first time and was very easy.
The steps for flashing a .zip in sideload mode:
- Ideally have a .zip of the ROM you were on. If you are on a stock rom, try to find a rom based on the same version of your stock from and it should be fine. You probably won't need to wipe data/factory reset (I haven't had to wipe going from AUS stock 350 - NL 434 - KA04 xperia revlolution)
- Have drivers configured perfectly
- Have ADB working
- Put the rom .zip in your ADB directory (It would be a good idea to name it update.zip or rom.zip for ease of use.)
- Open file explorer and go to your ADB directory, hold down shift, right-click and select open command window here
enter "adb devices"
- Your device should be listed. If all the drivers are set up properly, is should also list as being in sideload mode
- Type "adb sideload <filename of update.zip>" without quotation marks or < >
- Let it finish. When it's done your device should now be working fine or at least out of sideload mode
- Wipe cache and dalvik cache if you feel it's necessary
I am not sure how this will work for locked bootloaders as mine is unlocked therefore cannot comment on the experience. I suspect that if you flash xperia revolution, it should work as it is compatible with locked bootloaders. It should fail and abort the installation near the end though. This is normal, just wipe cache and dalvik cache and it should work.
In the worst case scenario, you should now be able to access flash-mode to flash a stock rom with flashtool. You shouldn't need to do this though.
Original post:
So I intelligently selected install zip from sideload instead of sd card. Now I am stuck in side load mode, and no amount of button combinations for any period of time are working to hard reset the device. And since the Z has no removable battery I cant just pull that out to shut it off. It doesn't seem to like taking any commands from adb, does anyone have any advice?

DreadPirateDan said:
So I intelligently selected install zip from sideload instead of sd card. Now I am stuck in side load mode, and no amount of button combinations for any period of time are working to hard reset the device. And since the Z has no removable battery I cant just pull that out to shut it off. It doesn't seem to like taking any commands from adb, does anyone have any advice?
Click to expand...
Click to collapse
You can try SEUS:
http://www.sonymobile.com/global-en/tools/update-service/
not sure if it will help but it couldn't hurt to try it out. If all goes well seus will reinstall your device back to original

Odp: Stuck in sideload
adb reboot recovery
check that command
Sent from my GT-S6500D using xda premium

FlooDnl said:
You can try SEUS:
http://www.sonymobile.com/global-en/tools/update-service/
not sure if it will help but it couldn't hurt to try it out. If all goes well seus will reinstall your device back to original
Click to expand...
Click to collapse
I'll give it a crack
UPDATE: It's not letting me go past the connect stage unfortunately

yeah the adb commands are throwing up the error :
"error: closed"
ie;
adb reboot
error: closed
adb usb
error: closed
adb sideload xx.zip
gives me the whole help message.
adb get-state
unknown
very frustrating.

Odp: Stuck in sideload
put power of 8 sec.
Sent from my GT-S6500D using xda premium

Holding the power button for over 30 seconds didn't turn it of, nor did power + vol up, power + vol down, power + vol up & vol down, or vol up + vol down. This sucks lol. Really don't want to have to resort to just leaving it till the battery dies

DreadPirateDan said:
Holding the power button for over 30 seconds didn't turn it of, nor did power + vol up, power + vol down, power + vol up & vol down, or vol up + vol down. This sucks lol. Really don't want to have to resort to just leaving it till the battery dies
Click to expand...
Click to collapse
This worried me a little with purchasing this phone with non removable battery. Tried the hard reset mentioned in the manual to be more relaxed, but was sure that a lock could occur that nothing would work except battery run down, seen it on other devices previously. Now it seems confirmed

danw_oz said:
This worried me a little with purchasing this phone with non removable battery. Tried the hard reset mentioned in the manual to be more relaxed, but was sure that a lock could occur that nothing would work except battery run down, seen it on other devices previously. Now it seems confirmed
Click to expand...
Click to collapse
It's certainly looking that way, I just pull out my gf's old vista laptop (considered it may be a windows 7 or 64bit issue) but it's the exact same story there. I'm currently booting up my old/her new laptop which just recently got a fresh win7 install. Nothing at all adroid related has ever been on it since then so if it doesn't work still on that I can essentially rule out that it's a driver or os issue
UPDATE: Ok looks like the old/new/fresh laptop is doing the trick! When I type adb devices, this time it is listing the z as being sideload, instead of host (what it said on the other 2 laptops). So allthough reboot commands still come back as error, I was able to start sideloading cm10.1 zip.
AH just checked on it and it's done! I am out of the terrible menu. Now to try rebooting system.. hopefully I haven't made things worse .
CM logo is swirling away.. good start.
And now it's booted to CM . Thank god that is over!
Hopefully if anyone else falls into a similar trap this thread might help them. There must have been some sort of conflicting drivers messing with my adb set-up. Funny that I was able to root and unlock the bootloader completely hassle free in the same setup though
So to anyone having similar issues and doesn't have the option to pull out the battery - try a fresh pc that hasn't had any android devices installed to it.
And a big thanks to those that tried to help me up to this point much appreciated. :victory:

DreadPirateDan said:
It's certainly looking that way, I just pull out my gf's old vista laptop (considered it may be a windows 7 or 64bit issue) but it's the exact same story there. I'm currently booting up my old/her new laptop which just recently got a fresh win7 install. Nothing at all adroid related has ever been on it since then so if it doesn't work still on that I can essentially rule out that it's a driver or os issue
UPDATE: Ok looks like the old/new/fresh laptop is doing the trick! When I type adb devices, this time it is listing the z as being sideload, instead of host (what it said on the other 2 laptops). So allthough reboot commands still come back as error, I was able to start sideloading cm10.1 zip.
AH just checked on it and it's done! I am out of the terrible menu. Now to try rebooting system.. hopefully I haven't made things worse .
CM logo is swirling away.. good start.
And now it's booted to CM . Thank god that is over!
Hopefully if anyone else falls into a similar trap this thread might help them. There must have been some sort of conflicting drivers messing with my adb set-up. Funny that I was able to root and unlock the bootloader completely hassle free in the same setup though
So to anyone having similar issues and doesn't have the option to pull out the battery - try a fresh pc that hasn't had any android devices installed to it.
And a big thanks to those that tried to help me up to this point much appreciated. :victory:
Click to expand...
Click to collapse
I really didn't get it could you please help me more ! I have the same problem but I have no idea how to fix this I made a big mistake

Tell me if I'm wrong, but...
Dumiftw said:
I really didn't get it could you please help me more ! I have the same problem but I have no idea how to fix this I made a big mistake
Click to expand...
Click to collapse
I believe DreadPirateDan was saying:
Have a computer with adb installed. It has had an Android device connect to it before. It wouldn't recognise the device.
Have a second computer with adb installed. It has had an Android device connect to it before. It wouldn't recognise the device.
Have a third without adb installed.
Installed adb.
Attached device, which invoked device driver installation.
Started using adb and it was recognised, allowing reinitialisation of the device.
Maybe?
If you don't have that many computers, try a fresh virtual machine (VirtualBox and Ubuntu don't cost money if you don't have the licenses for VMware and Windows).

Yes what Johbremat said is correct. My bad I haven't checked xda for a few days otherwise I would have posted sooner! I hope you managed to solve your problem :fingers-crossed:
I edited the first post so if anyone else runs into this there is hopefully more clear instructions on how to get out of it. Let me know if there is anything I said incorrectly (I was going from memory pretty much), or if you don't understand something I have said and I will offer my assistance when I can and/or edit the post.

Hi, I just had this problem while putting Cyanogenmod on my Nexus10. I don't know if it will work on the Xperia but even when adb sideload update.zip was getting error: closed I was still able to do adb reboot recovery to get out of it. Also my error: closed problems went away when I used CWM to format my sdcard (kind of extreme, I know).

How do push a file via TWRP on this phone?

well, I did something stupid and wiped everything, including the 2 zip files needed to flash the KK rom for Tmobile..
my twrp is working fine; is there a easy way to transfer the 2 zip files back onto my phone via twrp?
thanks!

Does adb work in or twrp? If so it's just
Adb push ZIPNAME /sdcard
Sent from my LG-D959 using Tapatalk

I dont know; there is an adb sideload command in twrp, but it doesnt seem to do anything; Plus I am not sure if my phone is connected via adb..
I know I have the right lg drivers on my computer, but when I run any adb command, the phone doesnt respond.

Honestly I think what you need to do is restart and just lgflash JB then you can just access your sdcard
Sent from my LG-D959 using Tapatalk

This is where external storage comes in handy
Sent from my LG-D959 using Tapatalk

you can say that again; this is the first phone that I have had in a long time without an sd card, and it was "mental muscle memory" that made me wipe everything..
Now, my phone is viewed as an F340k, since that's what the twrp on this phone is based on, so I wonder if I would have a problem using lg flash...this is a tmobile phone, but it might "think" its an f340k..
If I can flash the drivers for a f340 on my computer, then I might be able to adb sideload via twrp..otherwise I am not sure what will happen.
I have been leaving my phone just sit in recovery, as I dont know what would happen if I shut if off, and rebooted to system..
Hope its not brick city for me..

Well try to go to download mode and flash stock. You should be able to get back into recovery again if needed.
Sent from my LG-D959 using Tapatalk

wase4711 said:
you can say that again; this is the first phone that I have had in a long time without an sd card, and it was "mental muscle memory" that made me wipe everything..
Now, my phone is viewed as an F340k, since that's what the twrp on this phone is based on, so I wonder if I would have a problem using lg flash...this is a tmobile phone, but it might "think" its an f340k..
If I can flash the drivers for a f340 on my computer, then I might be able to adb sideload via twrp..otherwise I am not sure what will happen.
I have been leaving my phone just sit in recovery, as I dont know what would happen if I shut if off, and rebooted to system..
Hope its not brick city for me..
Click to expand...
Click to collapse
How did you make out? I have been trying to figure out what drivers I need for adb to recognize my phone in twrp. Hope you recovered

Got to adb sideload. Swipe to enable. Open up a command promp on computer and type adb sideload then place your zip file here and hit enter
Sent from my LG-LS980 using XDA Premium 4 mobile app

PattyNYC said:
How did you make out? I have been trying to figure out what drivers I need for adb to recognize my phone in twrp. Hope you recovered
Click to expand...
Click to collapse
Thanks, still can't get the phone to be recognized by the computer..
justinswidebody said:
Got to adb sideload. Swipe to enable. Open up a command promp on computer and type adb sideload then place your zip file here and hit enter
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have been trying that; the problem is, that my phone now "thinks" its a f340k, and not a d959
I have been trying to install drivers so my win 8.1 machine can "see" the phone, so I can run adb sideload, but for some reason, I cant get it to "see" the phone in ADB..I keep getting a message in the command prompt, "device not found"
.I have downloaded drivers that "should" work, but its a WHQL win driver from LG, and it doesnt seem to have the proper drivers to enable my computer to "see" the phone in ADB..
Not a happy camper right now..

Maybe a usb otg would work if you put the rom.zip on the flash drive. There is an option to mount USB-OTG

PattyNYC said:
Maybe a usb otg would work if you put the rom.zip on the flash drive. There is an option to mount USB-OTG
Click to expand...
Click to collapse
I dont think that would help because my phone isn't being "seen" by my computer, while in twrp recovery
If I could just find the f340k driver by itself, without the WHQL "bundle", I think I could get it to recognize the phone, and then transfer files on to it..
I've looked everywhere, and cant seem to find that driver by itself anywhere..

Not sure but it worked on the similar G2 http://forum.xda-developers.com/showthread.php?t=2492911 sorry just read further in that thread and you may be right. sorry

I can get into download mode, but I cant get the lg flash tool to see the phone either...any suggestions at this point?
thanks
EDIT:
How can I boot to recovery at this point?
When I hold power and down, I get a screen with all Chinese writing on it, and my IEMI code on the bottom of the page..Power and up gets me the same thing..

another guess. I know with windows 7 the only way I could use fastboot was with the pdanet drivers otherwise my phone wouldn't connect to the pc. http://www.theandroidsoul.com/android-drivers-adb-and-fastboot-android-phones-tablets/

thanks, but the computer still doesnt see the phone..
do you know how I can get the phone into recovery at this point?
TWRP should still be on it, but I cant get i to boot into twrp.

wase4711 said:
Thanks, still can't get the phone to be recognized by the computer..
I have been trying that; the problem is, that my phone now "thinks" its a f340k, and not a d959
I have been trying to install drivers so my win 8.1 machine can "see" the phone, so I can run adb sideload, but for some reason, I cant get it to "see" the phone in ADB..I keep getting a message in the command prompt, "device not found"
.I have downloaded drivers that "should" work, but its a WHQL win driver from LG, and it doesnt seem to have the proper drivers to enable my computer to "see" the phone in ADB..
Not a happy camper right now..
Click to expand...
Click to collapse
Just flash the kdz files that is gona be the only way to fix that.

D-FUSE said:
Just flash the kdz files that is gona be the only way to fix that.
Click to expand...
Click to collapse
I've been trying all day to do just that, but my phone isnt being seen by my computer..
I think the problem is that my phone is a d959 tmo, but, the freedomflex recovery installed,(twrp) has changed my phone to a f340k, and I cant get any drivers to recognize the phone, so without that, I can't do anything with it..
Since the last working thing was TWRP recovery, is there a way for me to boot into twrp at this point?
All I can do is get in download mode, or another mode which shows all Chinese text/language on it, with my IEMI code on the bottom of the page..
Otherwise, I will have to ebay this thing, and hope someone with more dev skills than me can restore it somehow..
thanks!

wase4711 said:
I've been trying all day to do just that, but my phone isnt being seen by my computer..
I think the problem is that my phone is a d959 tmo, but, the freedomflex recovery installed,(twrp) has changed my phone to a f340k, and I cant get any drivers to recognize the phone, so without that, I can't do anything with it..
Since the last working thing was TWRP recovery, is there a way for me to boot into twrp at this point?
All I can do is get in download mode, or another mode which shows all Chinese text/language on it, with my IEMI code on the bottom of the page..
thanks!
Click to expand...
Click to collapse
Are turning off your antivirus and editing the host file
Sent from my LG-D959 using Tapatalk
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
D-FUSE said:
Are turning off your antivirus and editing the host file
Sent from my LG-D959 using Tapatalk
Click to expand...
Click to collapse
Have you tried a different port
Sent from my LG-D959 using Tapatalk

Or different computer all together. The aboot and recovery shouldn't mess up your drivers
Sent from my LG-D959 using Tapatalk

Side Loading OTA Update help

I’m a noob when it comes to android adb but I'm an IT guy so what the hell I want 5.1.
I am following some directions on line on how to side load the OTA update seems easy, just a few commands and it should work. Here is what I'm doing and where I'm getting stuck any help?
Loaded Android SDK
Enabled Dev options, USB Debugging and OEM Unlock.
adb Devices - shows my device
adb reboot bootloader – restarts into the bootloader.
Select Recover Mode
Hold Power button, then press once the Volume Up button. To get Recovery Mode
This is where I get stuck, I'm reading I need to send the command “adb sideload <filename of update.zip>” but at this point ADB no longer sees my nexus 6? Nothing happens when I run this command and nothing is reported when I run ADB Devices?
Now I'm thinking drivers but I loaded the drivers? Can someone point me in the right direction?
I'm trying on a Windows 8 PC
Also when I'm looking at the device manager everything shows up fine until i enter the recover. At this point nothing shows up in device manager and when i resead the USB cable nothing happens no sound like im disconnecting something and reconnecting it, not device manager refresh, weird.
update! got it working.
So it turns out the device manager dose not show anything until you get into adb sideload options then the wrong driver is loaded and i had to manual pick Android adb driver. once i did this i was able to side load the ota update and now on 5.1.

You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.

tom1226 said:
You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.
Click to expand...
Click to collapse
Thanks you are right you have to be in the adb sideload options for the phone to show up in device manager and at this point it was not seeing the right driver, once i picked android adb driver i was able to update Thanks!

Awesome, glad it worked out for you!

Stuck at loading screen when booting

I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.

cjsill9473 said:
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
Click to expand...
Click to collapse
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?

That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
ktmom said:
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
Click to expand...
Click to collapse

cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
Click to expand...
Click to collapse
Do you have an otg cable? Does that work?

I do but I don't have one on me currently. I am currently at work but will be home in about 2 hours.
ktmom said:
Do you have an otg cable? Does that work?
Click to expand...
Click to collapse

cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
Click to expand...
Click to collapse
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".

You are correct, device does show up when type in fastboot devices. Guess that is what I get when trying to do this while I am at work and haven't messed with this type of stuff in months. I really appreciate the fast response on this and my derp moment. Now to try and side load the OTA to see if I can bring my phone back to life. Looks like I just need to go into custom recovery and select "Apply Update from ADB" and hopefully I'll be in business.
jj14 said:
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
Click to expand...
Click to collapse

Well at this point I was able to side load the OTA DP5 build and its doing the same thing. Trying a factory reset now to see if that will make a difference but if not looks like I am going to have to go out and get me a new phone till I can get this one fixed or RMA'ed. Just stuck at the loading animation.
Edit: Factory restore finally brought it back to life. Thank you again for the quick help and assistance on this!